Principles
Core principles
These are the design constraints that keep the framework from collapsing into generic matrix management, transparency theater, or vague language about agility. They are principles, not slogans.
In the draft, adaptability, transparency, equity, and continuous learning are not side programs. They are operating assumptions. The principles below translate that argument into working rules for how commitments are seen, assigned, judged, and improved.
Make work legible
If a commitment cannot be seen, it cannot be staffed, improved, or rewarded fairly. Delivery work, maintenance, coordination, and support all need to be named clearly enough that people can act on them without guesswork.
Separate contribution from title
Titles may still help with craft identity, pay bands, or external clarity, but they cannot be the main lens for assigning work or reading value. Contribution has to travel wider than the org chart.
Let structure follow the task
Stable teams still matter, but they are not the default answer to every priority. Use the lightest structure that can carry the work without losing accountability, continuity, or context.
Keep stewardship explicit
Autonomy is not the same as ambiguity. Every commitment still needs clear decision rights, a review rhythm, and a path for escalation when priorities or tradeoffs conflict.
Make invisible work count
Documentation, mentoring, handoff coordination, onboarding, and repair work keep the system alive. The model treats that labor as visible, distributable, and rewardable rather than as background effort quietly absorbed by whoever is most reliable.
Build learning into the work
Learning should happen through stretch tasks, teaching, documented decisions, and safe-to-fail experiments. If growth depends only on separate programs, the system is not actually designed to learn.
Tensions to manage
The principles create productive friction.
A serious implementation does not pretend these tradeoffs disappear. It keeps them visible enough to manage instead of hiding them behind slogans.
That friction is a feature, not a flaw. Any model that promises pure autonomy, perfect stability, or zero coordination cost is usually hiding who absorbs the tradeoff when reality gets messy. Someone still carries the load. The question is whether the system makes that visible.
The goal is not to eliminate tension. It is to make it governable. When leaders and teams can see where reliability constrains freedom, where expertise limits fluidity, and where change threatens coherence, they can make better decisions without pretending the conflict is solved once and for all.
- Ask which side of the tradeoff is currently dominating by habit rather than by design.
- Look for the people or tasks that absorb the hidden cost when the balance slips.
- Treat the tension as an operating condition to manage, not a contradiction to deny.
Freedom and reliability
People need room to choose and grow, but the organization still needs dependable coverage, clean handoffs, and recovery paths for core work.
Specialization and fluidity
Deep craft matters. The goal is not universal generalism. The goal is to widen access to work when needed without pretending expertise is interchangeable.
Autonomy and stewardship
Choice works only when there are explicit constraints, review points, and shared agreement about what cannot be dropped or delayed.
Adaptation and coherence
Crews can form and dissolve around changing work, but the wider system still needs memory, standards, documentation, and continuity.
How to use this page
Use the principles as evaluation criteria.
If a proposed implementation makes work harder to read, hides decision logic, weakens stewardship, or pushes maintenance and support work back into the shadows, it is drifting away from the framework even if the vocabulary still sounds right.
The test is not whether a team uses the right words. It is whether the operating rules create more clarity, more fairness, better learning loops, and stronger trust under pressure.