The Practice
Designing Conditions for Organizations to Feel Alive
There's a particular kind of stuckness that shows up in mission-driven organizations. Every part is working. The team is talented. The mission is clear. The programs are solid. And yet something isn't quite landing. Decisions take longer than they should. Strategy plans don't match how the work actually gets done. New hires solve pressing problems, but create new ones. Leadership is busy, yet the organization feels heavy and slow. This isn't a people problem. It's a systems problem. And it usually can't be solved by working harder inside the parts as they currently exist.
It may be time to take a step back to look at the big picture as a practical lens for seeing where the parts connect, where they don't, and where the patterns underneath the daily problems are actually being generated. The work is less about adding new structure and more about strengthening the connective tissue between the parts, so the organization can move with intention rather than reaction.
The Operating Principles
Portray the whole before the parts. Most operational problems get solved at the level they appear. A systems thinker looks first at the level the problem is being generated. Sometimes that means the obvious fix is the right one. Oftentimes, it means the obvious fix would have made things worse.
Identify the patterns underneath the problems. Organizations don't usually have a thousand different problems. They have a few structural patterns producing a thousand different symptoms. The practice uses systems thinking to trace symptoms back to their source and name what's actually going on.
Design for relationships, not just functions. Every org chart describes roles. Almost none describe how those roles actually relate to each other. It’s not about restructuring an entire system for its own sake. It's about making sure the connective tissue between the parts is designed to carry the weight of the mission.
Build infrastructure that holds vision. Operational infrastructure exists to serve the mission, not to administrate it. As organizations grow, this connection is easy to lose. This work keeps the connection between infrastructure and purpose intact, designing operations that prioritize long-term vision rather than substitute for it.
Know what to leave alone. Not every problem needs a solution. Some systems are already self-correcting and intervention would make them worse. Some inefficiencies are protecting something else. The practice holds enough of the whole picture to differentiate between a problem that needs attention and one that needs leaving alone.
To go deeper, read about the framework of aliveness or who’s behind the practice