Rules-to-Ownership Learning Ladder
Mandate the floor, then help people discover why better practices work
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 98%
Siemiatkowski separates the operating floor from genuine adoption. Leaders first identify the small number of behaviors they consider fundamental and make those boundaries clear. Above that floor, they should avoid assuming that a mandate creates learning. Instead, demonstrate the practice, let people experience it, provoke observation and reflection, and ask teams to make the insight their own. Local managers then decide how the principle applies and must explain their reasoning rather than hiding behind a policy written at the top. Finally, the organization needs a mechanism for exceptions and feedback, because a rule that never returns for challenge can become an excuse to stop thinking. The mechanism moves from boundary to experience to reflection to local ownership. Siemiatkowski says he has not fully solved this balance, so the framework should be treated as his evolving leadership model rather than a finished system.
Origin
Siemiatkowski developed this view after Klarna encouraged daily stand-ups and weekly retros but saw only about half of teams follow them. He contrasts meaningful adoption with box-checking and draws on a Toyota factory observation exercise in which managers learned by watching work rather than receiving answers.
Core principles
- 01A practice performed only to satisfy a rule can lose its purpose
- 02Some foundational behaviors still need clear boundaries
- 03People learn more deeply by doing and observing than by receiving instructions
- 04Managers should explain local decisions rather than hide behind headquarters
- 05Healthy exceptions show that people continue to think
How to run it
- 1
Define the operating floor
Identify the few practices without which the shared endeavor cannot work. State them as boundaries and connect each one to its purpose.
Pro tip Use the soccer-team test: reserve mandates for behaviors as foundational as showing up to train.
Watch out If everything is mandatory, teams will optimize for compliance rather than understanding.
- 2
Show useful practice
Demonstrate what the behavior looks like when it is helping the work, not merely when its formal steps have been completed.
Pro tip Contrast an engaged stand-up that removes blockers with one performed only to check a box.
Watch out Naming a ritual does not communicate the outcome it is meant to create.
- 3
Create direct experience
Give people an opportunity to try, observe, and learn from the practice themselves. Use questions and exposure to the work rather than supplying every conclusion.
Pro tip Ask what they noticed and what changed instead of immediately telling them what they should have seen.
Watch out An exercise without a real connection to the work can become another ritual.
- 4
Require local reasoning
Let the team closest to the situation decide how the principle applies and require its manager to explain the choice.
Pro tip Ask why the team's arrangement advances its work under its actual constraints.
Watch out Delegation without accountability can turn autonomy into avoidance.
- 5
Keep exceptions thinkable
Provide a route to challenge a rule when it does not fit a particular person or situation. Feed credible exceptions back into policy review.
Pro tip Treat a well-reasoned exception as evidence about the system, not automatic disobedience.
Watch out Exceptions still need reasoning; they are not a blanket release from shared standards.
In the wild
Klarna told teams to use practices including daily stand-ups and weekly retros after leaders found them productive. Siemiatkowski says internal data showed only about half of teams following the practices. He uses the gap to question whether enforcement would create engaged problem-solving or merely meetings that satisfy a rule.
→ The adoption gap became evidence for distinguishing mandatory form from internalized purpose.
Siemiatkowski recounts an example from The Toyota Way in which senior managers stood inside a circle on a factory floor and observed production. When their observations were inadequate, the teacher sent them back for another day rather than giving them the answer.
→ The managers had to develop their own ability to see the work and its problems.
Common mistakes
Mandating the ritual, not the result
Teams can perform a stand-up or retrospective without engaging with the problems the practice is meant to solve.
Writing one rule for every context
A policy from the top may fit poorly across different offices, teams, and individual circumstances.
Using policy to avoid judgment
Managers weaken the culture when their only explanation for a local choice is that senior management said so.
Is it for you?
Best for
It is best for leaders scaling working practices across teams that operate in different contexts.
Not ideal for
It is not ideal for legal, safety, or security requirements whose minimum controls cannot be treated as optional experiments.
From the transcript
“we learn by doing uh by doing things ourselves”
“how do I intrigue you? How do I challenge you to develop that insight for yourself”
“rules can never be an excuse for not thinking for yourself”
From the episode
Klarna Founder: From $0 to $46 Billion: Sebastian Siemiatkowski