
What critical thinking is, and what it is not
How it differs from logical and creative thinking
Its role in analysing a system you are part of
Objectivity, rationality and reasoning from evidence
Deduction, induction and abduction
What separates a strong argument from a weak one
Building an argument that survives challenge
Recognising errors in reasoning, including your own
What cognitive biases are
Confirmation bias, anchoring and framing
How they decide which cause you find before you start looking
Practical techniques for reducing their effect
Separating fact from opinion
Verifying accuracy
Primary against secondary sources
Fact-checking as an everyday management skill
OODA, Cynefin and cost-benefit
Using analysis and argument to choose
Managing risk and uncertainty
Cases from business and from ordinary life
Applying it inside a business
Using it in negotiation and communication
Its connection to creativity and innovation
Building your own development plan for it
What a troubleshooter is, and how the role differs from crisis management
"Problem" against "trouble", and when this approach is the right one
The four steps: localise, find the cause, propose, implement
Balancing speed with system thinking, and the beginner's mistake of treating symptoms
Getting from symptoms to substance with 5W1H
Packaging a problem into a clear request with SCQA
Logic trees and MECE so nothing is missed
Cause and goal trees, and checking the boundaries of the task
Five whys as the simplest root extractor
The Ishikawa diagram and its cause categories
Confirming a cause is real rather than a neat story
False roots, and the danger of stopping too early
The 80/20 rule and finding the vital few
The Pareto chart
Process mapping and the theory of constraints
Prioritising by impact against cost, with a decision matrix
Brainstorming done properly, and the anti-rules
SCAMPER and the six thinking hats
Barriers to creativity and how to remove them
Screening ideas quickly against criteria
The ideal final result, and the search for hidden resources
Formulating a contradiction and resolving it without compromise
Altshuller's forty principles with business examples
When TRIZ beats brainstorming and when it does not
Paradoxical questions for problems that look hopeless
Psychological inertia, and how to break the pattern
Morphological analysis and the focal object method
When to bring in advanced techniques, and how to combine them
Acting as moderator: neutrality and focus on the goal
The script for a session: analysis, ideas, choice, plan
Handling domination, conflict and idle discussion
Nominal group technique, Delphi and online whiteboards
Profitability: breaking down revenue and cost to find the dip
SWOT and the strategic questions
Lean and Six Sigma for speed and defects
The 7S model for organisational diagnosis, and change frameworks for implementing
The map of methods, from root cause analysis to TRIZ and Lean
Why there is no single technique that always works
A personal development plan across analysis, creativity and pressure
Reputation, confidentiality and responsibility to whoever hired you
Who should own the description
What describing a process actually gives you
What a process 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 the process 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
Who is responsible for the shape of an organisation
The design process itself
The five steps of organisational design
What problem you are actually solving, stated plainly
Strategic priorities and the star model
The symptoms that say the structure is wrong
Setting the goal, and the six drivers of design
Using the six drivers to choose
Organisational archetypes
Whether a matrix is the answer
The three types of matrix structure
Designing for operational management
Operating models and levels of management
Matrix management, networks and boundaries
Diagnostic indicators, and how power distributes in a matrix
Designing the leadership structure
Defining top-level accountability
The leadership cascade and organisational levels
Span of control, and making good staffing decisions
Developing the implementation plan
All at once or in phases
Whether a pilot is worth it
Managing the transition and launching new workflows
This course contains the use of artificial intelligence.
If a problem keeps coming back after you solve it, you are not solving it. You are removing a symptom that the system regenerates on schedule.
Why the fix never holds
The pattern is always the same. Something goes wrong, somebody finds a cause that sounds right, a fix is applied, and everyone moves on. Four months later it happens again, usually to a different team, and it is treated as a new incident. I have signed off on that fix more than once. What I eventually learned is that the cause I found was the first plausible one, not the real one, and the structure and the process that produced it were never touched.
What this course actually covers
Five blocks, from how you think to how you intervene. First, critical thinking: what makes an argument strong, which biases decide what cause you find before you start looking, and the decision models for acting under uncertainty. Second, problems without a known answer: framing with 5W1H and SCQA, breaking them down with MECE, five whys and Ishikawa for the root, Pareto and the theory of constraints for where the damage sits, TRIZ for contradictions that will not compromise, and how to run all of it with a group. Third, the system as flows: describing a process in BPMN until the break point is visible to everyone. Fourth, the system as structure: the six design drivers, archetypes and matrices, the leadership layer, and how to run a transition. Fifth, intervening: diagnosis, choosing the level of intervention, delivering it, and measuring whether it worked, including return on investment.
A note on the examples
Fourteen of the thirty-eight lessons use people-side examples — hiring and onboarding processes, interventions at individual and team level. The apparatus does not depend on that. BPMN, RACI, cause-effect diagrams, the Kirkpatrick model and the balanced scorecard behave identically whatever the process contains. I am telling you now rather than letting you discover it in lesson twenty-one.
Who is teaching this
I am Mike Pritula. 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 frameworks: MECE, 5W1H, SCQA, five whys, Ishikawa, Pareto, TRIZ, BPMN, the six design drivers, Kirkpatrick
Real organisational cases, including Wargaming and ArcelorMittal
Where to start
Take a problem your company has fixed at least twice. Write down the cause you accepted each time. If both answers describe something a person did rather than something the system arranged, you already have your first case for this course. Enrol now and start today.