Organizational Flow — Appendix
Principles
Not rules — observations, developed across the chapters of this book and gathered here for reference. Each one is argued for in full where it's tagged; this page is the index, not a replacement for reading the chapters. Where a theme doesn't have a chapter yet, its principles are listed all the same — they're waiting on the writing, not on the thinking.
Part I · Organizational Principles
- Technology is rarely the bottleneck. Friction is.
- Flow over friction.
- Flow is an organizational capability.
- Flow has a human dependency.
Part II · Ownership
- Ownership before governance.
- Governance grows where ownership is unclear.
- Ownership isn't about control. It's about accountability.
- Ownership creates progress when it's taken.
- Clear ownership is one of the strongest predictors of an organization's ability to adapt.
Part II · People
- Contribution creates flow.
- People create the conditions for each other's success.
- Trust grows when people consistently help others move.
- Organizations are different. Interdependence isn't.
- People own. AI amplifies. Organizations learn.
- AI should amplify capability — not replace accountability.
Information
Chapter coming
- Information should move.
- Information creates value when it's shared.
- Information should be captured once and used many times.
- Copying and reconciling information creates friction.
Decisions
Chapter coming
- Decisions create momentum.
- Slow decisions slow organizations.
- A good decision made early beats a perfect decision made too late.
Execution
Chapter coming
- Execution is where strategy learns.
- Strategy is a hypothesis until it's executed.
- Execution creates learning.
Learning
Chapter coming
- Experience is automatic. Learning is a choice.
- Organizations learn through execution.
- Learning compounds over time.
Part II · Capabilities
- Capabilities endure.
- Technology enables capabilities. It doesn't define them.
- Organizations create value through capabilities — not technology.
Architecture
Chapter coming
- Architecture should make organizations easier to change.
- Architecture creates the conditions for adaptation.
- Architecture exists to improve flow.
- Architecture is cultivation.
- Architecture is about conditions, not control.
Leadership
Chapter coming
- Leaders create conditions. People create flow.
- Expectations create responsibility.
- Leadership is about cultivating, not controlling.
Part I · Gardening Organizations
- Cultivate, don't control.
- Organizations should be designed to learn.
- Organizations are gardens, not machines.
- Change is a capability, not a project.