
In this lecture you put two ways of measuring the same everyday process side by side, get the four criteria that decide which one belongs on your dashboard.
This course is built from six disciplines: operations management, the metric catalogue, workforce analytics, the scoring sheet, goal setting and how a data-first company decides.
A dictionary for reading lectures recorded on workforce data as your own operational numbers
Three questions to ask after every lecture
A short self-diagnostic that shows which sections to watch first
Download the Everyday Number Check and fill it in for one process that runs every day.
Why a business needs this once it passes fifty people
How it differs from project management
The areas it owns
Typical mistakes and false expectations
What a process is and what it is not
End-to-end thinking, and value to the business
Mapping the key processes
Minimum sufficient regulation, and the cost of over-documenting
Why metrics do not work in most companies
Input, output and outcome as three different things
Leading against lagging
Metric owners, dashboards, and avoiding analytics for its own sake
Where a company loses time, money and focus
Bottlenecks and system constraints
Queues, downtime and context switching
Quick wins, and when automation is genuinely needed
Why teams fail to connect with each other
Cross-functional processes and the friction between them
Weekly, monthly and quarterly rhythms
How to keep meetings from becoming empty formalities
Why order keeps breaking down
Operations during growth and scaling
Resistance, sabotage and inertia
Prioritising change, and when to stabilise rather than rebuild
The toolkit, and what each part is for
Process and workflow systems
When a spreadsheet beats a corporate platform
Typical automation mistakes, and designing the target system
Who comes into operations, and from where
How to prove its value to the business
Return on operational management
Career tracks and a personal roadmap
The role metrics play in managing anything
Where they typically come from, and what you need to read them
Types of metric and types of analysis
The stages of analysis, and moving from a metric to a decision
The key indicators for a funnel
Service level agreements, and what they change
Funnel analysis using the metrics
Calculating the cost of a slow process, and building the case
Linking these indicators to business performance
The tools for measuring them
Preparing a report and an action plan
Ready-made questionnaires, and pulse measurement
How to obtain data from the market
Assessing competitiveness
Evaluating whether a bonus system works
Calculating the review percentage, and preparing the budget
Which indicators show whether capability is growing
Measuring performance without gaming it
Connecting development spend to a result
How to calculate churn properly
Analysing it by segment, and forecasting it
Finding the real causes through regression analysis
Exit conversations and retention surveys as data sources
Exporting from any system, whatever shape it comes in
Cleaning duplicates, blanks and formats with a model
Building one dictionary of metrics so the terms stop drifting
Producing a single reference file ready for any analysis
A descriptive portrait of the organisation in fifteen minutes
Breakdowns by unit, level and location
Pivots and charts built through the model rather than by hand
Top-line rates and funnel figures
Moving from what happened to why it happened
Finding anomalies by manager, unit, level and tenure
Identifying gaps where you pay above or below market
The question, sub-query, slice pattern
Building an explainable risk score
Forecasting the quarter by unit
Calculating the budget and capacity implications
Explaining every forecast, with no black box
Turning four deliverables into one board-ready deck
Building it without manual copy-paste
Speaking to leadership in the language of money rather than metrics
Defending each conclusion in front of a sceptical audience
What a scorecard is, and how it differs from a checklist
Cognitive bias, and why most decisions are made almost immediately
The halo effect, cloning and gut feeling
The formula for what a wrong decision costs
The structure, and how the parts connect
A thirty-minute meeting that gathers all the requirements
Separating must-have from nice-to-have
Behavioural indicators, and a five-point anchored scale
Where the scorecard sits in the process
RACI: who creates, who evaluates, who decides
Training people in thirty minutes, and answering the objections
Quality and calibration metrics, and the return calculation
The four things the method actually does
Its history, and how it started at Intel
The basic principles
What it is not
The cycle itself
The format a goal has to be written in
Synchronising goals between levels without a cascade of paperwork
Training the managers first
Training everybody else
Running the first goal-setting meeting
This course contains the use of artificial intelligence.
Most companies have metrics and make decisions without them. The dashboard exists, the report goes out on Monday, the figures update on schedule, and nothing changes.
Nobody agreed in advance what a given number would make you do
That is the whole failure, and it is almost never a tooling problem or a data quality problem. A metric that has no decision attached to it becomes a ritual: people look at it, discuss it briefly, and carry on exactly as before. Worse, it crowds out attention — a weekly review spent reading twenty numbers that change nothing is a weekly review not spent on the one that would. So the first skill in operational analytics is not building a chart. It is telling apart a metric that has an owner and a consequence from a metric that merely exists, and retiring the second kind.
What this course covers
Thirty-eight lessons. The operating frame first: why an operations function appears past fifty people, mapping processes without over-documenting them, input against output against outcome indicators, leading and lagging, metric owners and accountability, avoiding analytics for its own sake, where a week actually disappears into queues and context switching, operating rhythms that keep meetings from becoming formalities, and when a spreadsheet beats a platform. Then the metric catalogue: where metrics come from, types of analysis, the stages of reading one, funnel indicators and service levels, engagement measures tied to business performance, market data and competitiveness, budget calculations, development indicators, churn by segment, and finding real causes through regression. Then the path from a raw export to a board deck: cleaning and validating data, one dictionary of metrics so terms stop drifting, a descriptive portrait in fifteen minutes, pivots built through a model rather than by hand, diagnosis by slicing across manager, unit, level and tenure, pay gap detection, an explainable risk score, a quarterly forecast with no black box, and a presentation that speaks in money rather than in metrics. Then decisions instead of impressions: cognitive bias, the halo effect, the cost of a wrong decision, behavioural indicators, a five-point anchored scale, RACI, and calibration between assessors. Then connecting metrics to goals: the planning cycle, the format a goal must be written in, synchronisation between levels, running and closing a cycle, five company cases including Preply and iDeals, tooling, and the contentious link between goals and pay. Finally how a company built on data actually decides: algorithms in selection, structured interviews, committee consensus, errors of the first and second kind, autonomy against control, an internal marketplace for roles, twenty per cent time, and forecasting with machine learning.
Five of the six blocks use workforce data, and there is a reason
The examples are headcount, churn, cost per hire and pay gaps rather than throughput and defect rates. The machinery does not care: a metric owner, the input-output-outcome split, data cleaning, anomaly hunting across slices, an explainable risk score, an anchored scale and assessor calibration are data work rather than an industry method. There is also a practical advantage, and it is why the analysis block is built on this data specifically — workforce datasets are small and complete, so a single course can walk the entire path from a raw export to a board presentation without drowning in preparation. With most operational data that walk-through would take three times as long and teach less. The operations block is about the function itself and carries no industry.
Who is teaching this
I am Mike. I built the people system at Preply as it became a unicorn, and I have worked at Wargaming, iDeals and Alfa-Bank. More than 1.6 million students have enrolled in my courses across 185 countries, and over 150,000 specialists have gone through my programmes. I hold PHRi and SHRM-CP certifications and represent HRCI in more than ten countries.
What is included
Lifetime access to all 38 lessons
Active instructor support in the Q&A section
A Udemy Certificate of Completion
Working material: the input-output-outcome metric set, the metric dictionary, the data cleaning sequence, the question-sub-query-slice pattern, the explainable risk score, the anchored five-point scale, the RACI for decisions, and the goal-setting format
The whole path from a raw export to a board deck, shown end to end
Where to start
Open your own dashboard and pick one number. Write down what you would do differently if it moved ten per cent in either direction. If the answer is blank for most of them, that is the finding. Enrol now and start today.