When people hear the word “constraints,” they usually imagine limitations.
Rules. Restrictions. Bureaucracy. Someone telling you “No.”
But constraints are not always oppressive. Some constraints enable movement.
A jazz musician improvises inside musical structure. A poet writes within a form. A soccer field has boundaries so the game can exist. Even language itself is a constraint system that makes meaning possible.
Without enabling constraints, systems often collapse into ambiguity, friction, or endless decision-making.
In organizational systems, this shows up constantly. Teams reinvent the same thing repeatedly because nothing stabilizes shared understanding. Meetings drift because no one knows how decisions are made. Projects become emotionally exhausting because people must renegotiate every interaction from scratch.
Strong enabling constraints reduce unnecessary cognitive load while increasing adaptive capacity.
Knowledge Flow depends on this balance.
Too much rigidity suffocates learning.
Too little structure dissolves coherence.
The goal is not control.
The goal is creating conditions where intelligence can emerge.
1. Identify a recurring friction point
Choose an experience that feels unnecessarily difficult, repetitive, draining, or chaotic.
Some examples:
- meetings that go in circles
- unclear ownership
- too many communication channels
- repeated misunderstandings
- difficulty starting creative work
- lack of trust in decision-making
- constant context switching
- “everything is urgent” environments
Describe:
- What keeps happening?
- What impact does it have?
- What work becomes harder because of it?
- What emotional patterns arise?
- What compensating behaviors have emerged?
Try not to jump immediately into solutions.
2. Look for missing structure
Now ask yourself:
What constraint is missing?
Not:
“How do we force people to behave differently?”
But:
“What stabilizing structure might make wiser behavior easier?”
Examples:
- a shared vocabulary
- explicit decision ownership
- quieter collaboration space
- response-time expectations
- meeting facilitation rules
- templates
- visible workflows
- lightweight rituals
- boundaries around work-in-progress
- clear escalation paths
- dedicated reflection time
Remember: enabling constraints should reduce friction while supporting adaptability.
If the structure creates fear, rigidity, or performative compliance, it is probably functioning as control rather than enablement.
3. Design one enabling constraint
Create a small experiment.
Keep it lightweight.
The goal is not designing a perfect governance system. The goal is noticing how structure shapes behavior.
Describe:
- What constraint are you introducing?
- What does it enable?
- What friction is it trying to reduce?
- What behavior is it encouraging?
- What tradeoffs might emerge?
- How will you know if it helped?
Examples:
- “No solutions in the first 15 minutes of discussion.”
- “Every initiative must identify a primary decision-maker.”
- “Questions go in writing before meetings.”
- “Shared definitions are captured when terms become ambiguous.”
- “One afternoon per week with no internal meetings.”
4. Observe the system response
Try your enabling constraint for a week or two.
Notice:
- What changed?
- What resisted the change?
- What became easier?
- What became harder?
- What unexpected behaviors emerged?
- Did the system adapt around the constraint?
- Did new possibilities appear?
Most importantly:
Did the constraint increase knowledge flow?
Did it help people:
- notice more clearly?
- coordinate more effectively?
- make better sense of situations?
- reduce unnecessary friction?
- generate stronger outcomes?
Or did it create new distortions?
Consider This
Describe a time when structure made something easier, more creative, or more humane.
Then describe a time when structure became oppressive or limiting.
What made the difference?
Where is the boundary between enabling and controlling?
And who gets to decide?
