Using constraints to move from understanding to action

There’s a subtle shift that changes how teams respond to limitations.

Instead of asking, “How do we work around this constraint?” Ask, “What does this constraint tell us about what matters?”

That second question changes the conversation. It forces prioritisation, surfaces hidden preferences and exposes which initiatives are truly strategic and which are comfort projects.

For example:

- A tight budget can sharpen focus on core value rather than peripheral features.
- Regulatory friction can clarify where risk tolerance actually sits.
- Capacity limits can reveal which initiatives are genuinely essential.

In my experience, constraints become powerful when they are made explicit and treated as design inputs rather than irritations. I explored this idea more fully in “Turning Constraints Into Catalysts” where I describe how embracing limitations can actually accelerate flow rather than stall it.

It’s about moving from resentment to curiosity - and how curiosity can change the quality of decisions.