
In this lecture you draw the five steps of one flow you own, add the time each step takes and the time it waits, and see which handover gives way first when the volume doubles.
This course is built from five disciplines: the operating seat of a company, process description, the operations function, organisational design and capacity planning.
The map of the course
A dictionary for reading lectures from other fields as operations work
Three questions to ask after every lecture
A self-diagnostic that shows which sections to watch first
Download the Scaling Flow Map and fill in one line after each lecture.
What the research says about the role
The key competencies it requires
The core tools the role runs on
An operational efficiency checklist for a business
How to run a strategy session
The tools for assembling a strategy
The seven levels of strategy and how each is developed
SWOT and PESTEL, and a one-page plan everyone understands
The three core elements of corporate culture
Describing culture, and the tools for doing it
Ten ways to embed it into daily work
Describing desirable and undesirable behaviour, and the rules for changing culture
The essence of the method and what it requires
Five differences from management by objectives
Systems for tracking goals
A painless first launch, and linking goals to performance review
What processes are and why they exist
Who should describe them, and how to organise the project
The format for describing them, and what you get as output
Embedding the description into reality, and the automation tools
The types of structure available
Creating a matrix structure
Five drivers of structural choice
A diagnostic tool, and network structures for horizontal links
The four project stages and five processes
The project plan template
The business case template
The communications plan, and the network diagram
How finances are actually managed operationally
Increasing available cash, and cash flow management
Managing sales effectively from the operating seat
Budgeting, forecasting and monthly reporting
Managing the technology function
Facilities, administration and the operations unit
The legal function and procurement
Internal and external communications, and risk
Setting hiring up properly
Implementing an onboarding system
Five conditions for effective team performance
The accountability table, and the audit checklist
Who should own the description
What describing a process actually gives you
What a description consists of
Which processes to describe first, and which to leave alone
How processes are described internationally
Which methodology fits which situation
Using flowcharts properly
A simple BPMN diagram, and analysing what it shows
The description models available
Templates
The software worth using
A worked example using online tools
The actual output of the exercise
Implementing the described process rather than filing it
Evaluating how it performs afterwards
Adjusting it once reality disagrees
Describing an onboarding process end to end
Describing a hiring process
Describing a training and a performance process
Describing an exit process, and what each one exposes
Forming the project team and choosing the processes
Preparing the concept and defending it to leadership
Launching the project
Reporting, closing and monitoring afterwards
Why operations becomes a role once a company passes fifty people
How it differs from project management and from the chief operating role
The key areas of responsibility
Typical mistakes and false expectations about the role
What a process is and what it is not
End-to-end thinking and value for the business
Mapping the key processes
Where formalisation is needed and where it becomes bureaucracy
Why metrics do not work in most companies
Input, output and outcome indicators
Leading and lagging metrics
Metric owners, dashboards, and avoiding analytics for its own sake
Where a company loses time, money and focus
Bottlenecks and system constraints
Queues, idle time and context switching
Quick wins, standardisation, and when automation is genuinely needed
Why teams fail to connect with each other
Cross-functional processes and the friction between them
Operational meetings and status updates
Weekly, monthly and quarterly rhythms that stay useful
Why order keeps breaking down as a company grows
Operations during scaling specifically
Managing change through processes
Resistance and inertia, and when to stabilise instead of rebuild
The tools an operations function actually needs
Process and workflow systems
Metrics, dashboards and data sources
When a spreadsheet beats a corporate system, and the automation mistakes
Who comes into this work and from where
Operations as a strategic role rather than an administrative one
Demonstrating value to the business, and the return on it
The career track, and a personal roadmap
This course contains the use of artificial intelligence.
Companies do not break during growth because there is more work. They break because the way of running thirty people stops working at a hundred and fifty, and nobody notices the day it stopped.
What that looks like from inside
Decisions that used to happen in a corridor now need a meeting. Something that one person held in their head is now four people's job and nobody owns the seams. Output stops rising in proportion to headcount, so more people get hired, which makes the coordination problem worse. Everyone is working harder and the company is slower. I have been in a company that doubled twice and the second doubling was much worse than the first, because we scaled the team and not the way it was run.
What this course actually covers
Five blocks, in the order things break. First, ten lessons from the operating seat: the role, strategy, culture as a delivery instrument, the goal system, processes, structure, projects, finances, infrastructure and people management — the whole surface of running a company operationally. Second, describing processes properly: methodology, BPMN, tooling, worked examples and how to run a mapping project. Third, the operations function itself — why it appears once a company passes fifty people, input-output-outcome metrics, bottlenecks, queues, context switching, and the operating rhythms that keep teams synchronised. Fourth, the shape of the organisation: the six design drivers, matrix structures, the leadership cascade, span of control, and running the transition without stopping the work. Fifth, capacity: demand forecasting, workload norming, gap analysis and optimisation.
A note on the material
Some lessons inside the operating and capacity blocks deal with hiring, onboarding and headcount. That is not a detour — in a company built on knowledge work, capacity is people, and the operating layer is where headcount decisions actually get made. The frameworks throughout are general: BPMN, the design drivers, span of control, gap analysis and full-time equivalent arithmetic behave the same in any industry.
Who is teaching this
I am Mike. I built the people system at Preply as it became a unicorn, through exactly this kind of growth, 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 operational efficiency checklist, BPMN mapping, the metric hierarchy, the six design drivers, span of control, demand forecasting and gap analysis
Real organisational cases, including Wargaming and ArcelorMittal
Where to start
Name one decision that used to take a conversation and now takes a meeting. That is the first place your operating model stopped fitting the company. Enrol now and start today.