
Who is responsible for the shape of an organisation
The design process itself
The five steps of organisational design
Why a structure is a claim about authority rather than a description of it
What problem the structure was built to solve
Strategic priorities and the star model
The symptoms that lead companies to a matrix
Setting the goal, and the six drivers of design
Using the six drivers to understand the choice that was made
Organisational archetypes
Whether a matrix is a solution or a source of permanent friction
The three types, and what each does to who can decide what
Designing for operational management
Operating models and levels of management
Matrix management, networks and boundaries
The diagnostic indicators, and where authority actually ends up
Designing the leadership layer
Defining top-level accountability, and the options for it
The leadership cascade, and where it breaks in a matrix
Span of control, and what it says about a manager's real attention
Developing the implementation plan
All at once or in phases
Whether a pilot is worth it
Managing the transition, which is when informal authority decides everything
What separates a redesign from a reorganisation announcement
The skills the work requires
How the project team operates, and who has to be on it
Wargaming and Vega
Parallel
Corum and ArcelorMittal
What transfers between them and what does not
The four superpowers of the method
Where it came from and how it was born at Intel
The basic principles
Why it matters more in a matrix than anywhere else
The planning cycle
The format that separates an objective from a key result
Synchronising goals across teams that do not report to each other
Where the format usually goes wrong
Training the management layer first
Training everyone else
Running the first joint goal-setting meeting
What to expect from an imperfect first cycle
The agenda for a regular cross-team goal meeting
Using one-to-ones to support delivery you do not control
Updating goals mid-cycle without losing meaning
Keeping goals visible between reviews
Debriefing on the results
Presenting outcomes across functions
Capturing lessons learned
Feeding them into the next cycle
How this works at Google and Intel
MyFitnessPal
Preply and iDeals, from the inside
What transfers between companies and what does not
Dedicated platforms
Universal systems with goal-tracking functions
What to look for before buying anything
When a spreadsheet is still the right answer
Linking goals to performance review
The relationship with 360 assessment
Whether to link goals to pay, and the consequences in a matrix
Connecting goals to learning and development
What delegation is and what it does to effectiveness
The psychological barriers and the myths behind them
Formulating a task so it can actually be handed over
The Eisenhower matrix, and how not delegating becomes stress
The steps from choosing a task to checking it
The RACI model for assigning responsibility clearly
Tools for tracking what you handed over
Giving constructive feedback on it, and the common mistakes
Using delegation as a coaching tool
The GROW model applied to it
Balancing task difficulty against skill level
Using goals to hand over something strategic
How handing over work frees time for the work only you can do
Concentration techniques in this context
Automating the routine part instead of delegating it
Tracking what you handed over without hovering
What a role profile actually contains
Which sections belong in it
Why an organisation needs them, and why a matrix needs them more
What job analysis is, and who should write the profile
Interviewing the people who hold the role
Interviewing the manager, who will describe it differently
Questionnaires for collecting information
Observation, and how the profile fits the process system
What a competency is, precisely
What competencies add to a role profile
How to research them rather than assume them
How to describe them so two managers read them the same way
An overview of existing competency libraries
Ready-made role descriptions
How to use existing material without inheriting its assumptions
Building a scorecard from the profile
Building a career ladder on it
Building a development plan
Deriving goals and indicators, which is where dual reporting gets resolved
This course contains the use of artificial intelligence.
A matrix is a structure where someone has two managers with different priorities and no mechanism for reconciling them. It does not survive on people being good at getting along.
Why it goes wrong so predictably
Both managers are reasonable. Both have real priorities. Neither has agreed with the other what happens when those priorities collide, so the person in the middle resolves it — usually by pleasing whoever asked most recently, or whoever is more senior, or whoever they are more afraid of. Nobody designed that decision rule and everybody lives with it. I have been the person in the middle and I have been one of the two managers, and the failure looked identical from both positions: nothing had been written down.
What this course actually covers
Seven blocks, built on the four things a matrix actually runs on. First, the construction itself: the three types of matrix, how power distributes inside each, where accountability separates from authority, span of control, and how a matrix gets introduced or changed. Second, shared goals in place of a shared manager — eight lessons on aligning several functions on one set of objectives with named owners, running the quarterly cycle, and connecting it to review and reward. Third, who decides what: the RACI model and the six levels of delegation. Fourth, what a role actually owns when two people direct it, and how to write that so both managers read it the same way. Fifth, negotiating rather than instructing, including objection handling and closing. Sixth, facilitating the meeting where two functions want opposite things. Seventh, open conflict — escalation, prevention and mediation.
A note on two of the blocks
Nine of the forty-three lessons come from a people-management frame: delegation is taught using employee examples, and the role profile as an instrument of the people function. The apparatus is exactly what a matrix needs — RACI, the levels of delegation, describing responsibility as observable action, and linking a role to its goals. Only the examples come from one department.
Who is teaching this
I am Mike Pritula. I built the people system at Preply as it became a unicorn, working across a matrix through its fastest 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 43 lessons
Active instructor support in the Q&A section
A Udemy Certificate of Completion
Working material: the six design drivers, the three matrix types, the goal cycle, RACI, the six levels of delegation, role profiles and scorecards, the conflict resolution algorithm
Real organisational cases, including Wargaming and ArcelorMittal
Where to start
Write down the last time two of your priorities were in direct conflict, and who decided which one won. If the answer is that you decided quietly and told nobody, that is the gap this course closes. Enrol now and start today.