The FLAIMS Framework
A new operating system for the organisation of tomorrow. Six pillars on one foundation: functions that belong apart are kept apart. And AI is part of the structure from the start.
The foundation: functional decoupling
Most companies mix things in the same role that get in each other's way: the manager coaches you and decides on your pay. The project lead is accountable for the outcome and writes the rules themselves. The CEO designs the system and reviews it as well. That creates role conflict, and role conflict has been one of the best documented drivers of stress and poor performance since Kahn 1964. FLAIMS pulls these functions apart: designing, owning, supporting and reviewing sit in separate jobs. That is the foundation, and it is the reason why high performance and high wellbeing come from the same structure in FLAIMS.
Six letters, six questions.
What each letter does, in short. Click a pillar for mechanics, evidence and practice.
A complete system, not a toolbox.
Each pillar solves one structural problem. Together, they form FLAIMS.
Flow
Personal flow, information flow, delivery flow.
Explore the pillar →Leadership
Whoever assesses cannot coach.
Explore the pillar →Accountability
Always a name. Always the system first.
Explore the pillar →Intelligence (Human-Centered AI)
AI prepares. People decide.
Explore the pillar →Mastery
A bit better every day.
Explore the pillar →Segmentation of Power
Power made visible, weighed, reviewable.
Explore the pillar →Six pillars, one job architecture.
The pillars say what a company has to get right. The job architecture says who holds it. The same system, described twice: once as principle, once as structure.
- One Steward per pillar. The Steward sets the frame and has no management power.
- Below the Steward, Anchor Core Jobs that structure the field and implement it themselves.
- Below that, Core Jobs, each with full outcome accountability, and Joblets that support them.
- Every Core Job owes its accountability directly to governance, no matter how deep it sits.
Three stages of adoption
Stage 1, Foundation
Separate the functions, give every outcome a name, make the most important numbers visible to everyone.
Stage 2, Rhythm
Design flow, deploy FlowCoaches, put governance on numbers instead of gut feeling.
Stage 3, the whole model
Six Stewards, Anchor Core Jobs, Core Jobs, Joblets. All six letters as one system.
Practice first, then the evidence.
Every pillar emerged from insights from the field, paired with the research that explains those insights. The Evidence section shows which source supports which part of the model and what it does not prove. Every building block is proven; the model as a whole is new, but it consists of existing best practices and is informed by research.
See the cognitive biases FLAIMS protects against →- 01Self-Determination TheoryDeci & Ryan, 1985
Autonomy, competence and relatedness as the three needs that drive sustainable motivation.
- 02Flow State TheoryCsikszentmihalyi, 1990
The cognitive state where skill, attention and challenge align, and people work at their best.
- 03Psychological SafetyEdmondson, 1999
Teams learn faster when people can speak up about mistakes and unfinished ideas without losing status.
- 04Deliberate PracticeEricsson, 1993
Expertise comes from focused practice with fast feedback at the edge of current ability.
- 05Conway's LawConway, 1968
The systems an organisation builds mirror its communication structure.
- 06Dunbar's NumberDunbar, 1992
Natural group-size thresholds (≈5, 15, 50, 150) at which trust and coordination shift.
- 07Level 5 LeadershipCollins, 2001
Durable great companies are led with personal humility and professional will.
- 08Human-Centered AIShneiderman, 2022
High machine automation and high human control are not a contradiction.
- 09Systems ThinkingSenge, 1990
Recurring problems usually have structural causes, not personal ones.