Mastery
A bit better every day.
Learning becomes structure, on both levels. Competence is a fact, not a feeling, and decision scope grows with demonstrated capability.
Inside the letter M
Mastery has two sides that belong together. The learning organisation: shared competence levels, knowledge that stays when people leave, and learning loops that turn mistakes into improvements. And the learning person: everyone grows along a visible path, and career means a growing scope of impact, not a climb in the hierarchy. The company only learns as fast as its people, and people only grow as far as the structure lets them. Small daily improvements compound. That is the answer to mediocrity, for the individual and in the company.
The trap
Most companies talk about development and have a training budget that nobody draws on. What is missing is the shared language for what good actually means, and the mechanism that turns the learning of an individual into the knowledge of the company. Two woodcutters: whoever never sharpens the saw fells fewer trees.
Mechanics
- 01The Mastery Steward sets the frame: competence levels with evidence criteria, the rule for how levels translate into decision competence, paths including expert careers.
- 02The skill matrix: competence belongs to the person, the level applies per competence (Developing, Established, Mastery). The Core Job translates levels into decision rights. The grading is ratified by S.
- 03Knowledge communities and learning loops: reviews turn into improvements, artefacts and secured knowledge. The platform for that is delivered by I.
- 04The learning chain from the other side: A demands that learning happens, M delivers the how. And M assesses no performance; it delivers competence facts.
Rooted in research
Each source with a short sentence on what it actually says.
- Senge (1990), The Learning Organisation
Companies that learn faster than their environment win. Systems thinking, shared mental models and team learning turn the insight of individuals into the capability of the company.
What this does not settle: abstract; translating it into daily practice is craft.
- Ericsson (1993), Deliberate Practice
Expertise comes from targeted, effortful practice with fast feedback, at the limit of one's ability. Hours alone are not enough.
What this does not settle: practice explains only part of performance; how large that part is depends heavily on the field.
- Buckingham & Clifton (2001), Strengths
Durable performance comes from building on strengths, not from grinding down weaknesses.
What this does not settle: the instruments for it are proprietary; the principle is broader than any tool.
- Dweck (2006), Growth Mindset
Whoever understands ability as trainable deals better with difficult tasks and setbacks.
What this does not settle: in large replications the effect is small; take it as a stance, not as a lever.
- Note: FLAIMS-specific constructs such as Steward, Anchor Core Job, Core Job, Joblet, FlowCoach, Gravity Decision Model and the learning chain are developments of the model out of practice, not cited research.
In practice
Your development path is visible and the company learns with you. Competence is no longer a gut feeling, and your decision scope grows with what you can demonstrably do.