Turning Constraints Into Catalysts
Why embracing limitations is the first step toward faster flow
Every organization wants to move faster. Deliver change quicker. Respond to shifting markets with more agility. But there’s a truth we often avoid:
All organizations operate within constraints.
Time. Budget. Legacy systems. Regulatory requirements. Skill gaps. Cultural inertia. These aren’t signs that something is broken. They’re the reality of operating in a complex world.
The challenge isn’t whether constraints exist. It’s how we relate to them. Too often, constraints are treated as blockers. Reasons we can’t act. Excuses for stagnation. But what if we reframed them?
In A Beautiful Constraint, Adam Morgan and Mark Barden introduce a powerful mindset shift:
“A constraint should not be seen as the enemy of creativity, but as its co-pilot.”
Flow doesn't come from ignoring constraints; it comes from working with them. Working creatively within constraints, rather than trying to escape them, can be achieved by developing practices like:
“We can if…” thinking
Propelling questions
Breaking path dependence
These practices reframe constraints from a reason to stop into a reason to think differently. Fast-moving organizations aren’t the ones with fewer constraints.
They’re the ones who treat constraints as design conditions, not deal-breakers.
They do this by asking:
What’s the real limitation?
What’s the opportunity within this constraint?
What would need to be true for a better option?
Try this:
Pick a frustratingly slow or misaligned part of your org. Ask:
What constraints shape this behaviour?
Which are real? Which are assumed?
What’s one “We can if…” statement to explore?
Let that be your first step into constraint-driven design for flow.
'We can if...' thinking
You’ve probably heard it in a workshop or team retrospective:
“We can’t do that because…”
Over time, these “Can’t Because” statements become invisible rules. They block flow, not because they’re true, but because they go unchallenged. "We can if" statements don’t deny the constraint, they work with it. Instead of “We can’t move this team closer to the customer” stating “We can if we embed support temporarily” or “if we shadow for two weeks” turns a blocker into a bridge.
Accelerating flow can often start with small reframes. "We can if" statements can be used as a team unlock when teams are stuck in inherited constraints, decision loops are slow or unclear, or boundaries feel brittle but untouchable.
To help develop "we can if " thinking, next time you hear a “We can’t because…” statement, ask:
What would need to be true?
Is there a version we can* try?*
Can we reframe it as “We can if…”?
Common prompt structures might include:
“We can if we change the sequence”
“We can if we involve someone new”
“We can if we do less”
“We can if we rethink the metric”
The flow accelerator can often come from within the constraint.
Breaking Path Dependence
More often than not, the real blockers to flow aren’t people or tools, they’re decisions we made years ago, choices we’ve outgrown but never revisited. That’s path dependence: when historical decisions quietly limit today’s options. Examples of this may be teams shaped by old tech or product lines, risk-averse approval loops, or legacy incentives that no longer align with outcomes
The cost of inherited structure
The cost of inherited structure and other defaults can be slow delivery, blurred ownership, misaligned goals and decision bottlenecks. Because they’re familiar, they go unchallenged.
Clues can include statements such as:
“That’s just how it’s always been.”
“It’s too hard to change.”
“We tried before and gave up.”
These can be treated as invitations to rethink, using techniques to break path dependence. These include
1. Surface the original constraint
Every legacy structure was designed for a reason. Before discarding it, ask:
What was this structure, process, or boundary originally trying to solve?
Often, it was a rational choice for a past context: compliance, scale, or skill gaps. By surfacing that original constraint, you can assess whether it’s still valid or has quietly become obsolete.
2. Name the assumption
Path dependence often hides behind unquestioned assumptions. Bring them into the open:
What are we assuming can't change?
What are we taking for granted?
For example: “This team must own the whole platform” might mask an outdated belief about risk or ownership. Naming the assumption creates space to challenge it.
3. Challenge the sequence
Many organizational patterns are not inherently wrong — they’re just locked in outdated sequences. Try asking:
Does this still need to happen in this order?
What happens if we reverse it, overlap it, or collapse it?
Resequencing can reduce delays, rework, or unnecessary coordination—even without changing who does the work.
4. Ask a propelling question
A propelling question reframes the problem by holding both the ambition and the constraint in view:
How might we [bold ambition] despite [limiting constraint]?
For example:
How might we reduce lead time despite relying on a shared platform?
This forces creative thinking beyond business-as-usual and opens the door to feasible, incremental changes.
5. Make a small bet
Don’t try to solve everything at once. Instead, test a lightweight structural change:
What’s the smallest shift we can try that might improve flow?
This could be experimenting with new team boundaries, introducing a temporary enabling role, or removing one approval step. Small bets reduce risk while building learning and momentum.
Flow needs intentional structure, not inherited ones. It requires awareness of today’s constraints, small, testable changes and the courage to challenge path dependence.
Propelling Questions
Sometimes we don’t need more data. We need a better question. That’s the power of the propelling question.
From A Beautiful Constraint:
How might we [bold ambition] despite [real constraint]?
Examples:
How might we deliver faster despite fewer devs?
How might we reduce handoffs without new teams?
These questions force creative thinking, because the usual answers won’t work. They can unlock flow by stretching team thinking, turning blockers into options and breaking assumption loops.
Some examples might include:
How might we reduce approval loops despite regulatory needs?
How might we realign boundaries without full reorgs?
How might we improve feedback without more meetings?
Propelling questions frame better problems and lead to better structure.
To use propelling questions effectively:
1. Identify a source of friction
2. Name the bold outcome
3. Acknowledge the constraint
4. Frame your question
5. Explore “We can if…” options
Constraint-driven practices in motion
When embraced intentionally, constraints can unlock better team design, faster decisions, and more aligned structures. Designing within limits isn’t compromise, it’s capability, and combined with creative action it can drive lasting change.
“We can if…” → fuels small bets
Propelling questions → frame better decisions
Breaking path dependence → reveals outdated design
Transformer mindset → encourages ownership and creativity
Bringing Constraint-Based Thinking Into Your Organization
In my work with product and technology leaders, I’ve found that the most effective way to enable faster flow of value isn’t to fight constraints, it’s to reframe them.
Whether we’re exploring new team boundaries, tackling delivery bottlenecks, or redesigning platform capabilities, I use techniques like “We can if…” thinking, propelling questions, and small bets to help teams uncover hidden opportunities and make confident, incremental changes that improve flow without triggering disruption.
If your organization is feeling the weight of legacy decisions, structural friction, or competing priorities, constraint-based thinking might be the shift you need.
Need help getting started?
I offer strategy sessions, facilitated workshops, and ongoing support to help teams detect constraints, reframe options, and make practical, flow-focused decisions that stick.
Feel free to book a conversation or connect on LinkedIn to explore how we can apply this thinking in your context.
Let’s turn your constraints into catalysts.
