One of the most valuable lessons I learned working in public-sector design is that constraints are rarely optional.
Teams are faced with constraints from multiple sources:
- Policy constraints
- Security constraints
- Procurement requirements
- Legacy systems
- Budget limitations
- Organizational politics
At first, those realities can feel suffocating for teams trying to create meaningful change.
Over time, though, I realized the best teams approach constraints differently.
They treat constraints as design material.
That shift matters because it changes how teams think about possibility. Once organizations internalize limitations deeply enough, they stop looking for alternatives entirely. Constraints stop being boundaries to work within and start becoming assumptions nobody questions.
That is the moment when innovation begins shrinking.
Teams start optimizing for what feels safest instead of what might actually improve outcomes. Risk tolerance disappears. Solutions become incremental. Curiosity gives way to caution.
During my time at 18F, one phrase we occasionally used internally was “bureaucracy hackers.” The idea was not about bypassing rules irresponsibly. It was about understanding systems deeply enough to identify where flexibility, creativity, and collaboration could still exist inside complex environments.
That mindset changed how we approached problems. Instead of immediately asking:
“Why can’t this be done?”
We started asking:
“What part of this can still be done?”
That small shift matters more than people realize.
Innovation inside constrained environments often comes from reframing the problem instead of waiting for ideal conditions to appear.
I’ve seen this repeatedly in user research and delivery work.
Sometimes security restrictions limit access to users directly. Other times the tools the team would prefer to use are unavailable due to terms of the contract. It could also simply be that technical limitations prevent standard approaches entirely.
In those moments, teams have a choice. They can either treat the limitation as the end of the process or adapt creatively while still protecting the intent behind the work.
If remote card sorting tools are unavailable, can another collaborative platform be adapted instead?
If direct user access is limited, can subject matter experts or proxy users help validate assumptions?
If a process feels immovable, can policy experts become collaborators instead of blockers?
Some of the best progress I’ve seen came from bringing policy, security, or procurement stakeholders into the problem-solving process earlier instead of treating them like barriers to work around. It’s easy to forget that most of the time, they were navigating constraints too.
Once the conversation shifted from:
“How do we bypass this?”
to:
“How do we solve this together?”
better paths usually started appearing.
The goal is not preserving methodology perfectly.
The goal is preserving learning.
A recent example of this involved a researcher on one of my teams navigating security protocols that prevented users from directly accessing a prototype. Most standard approaches failed, but the test was still important for the future direction of the work.
Instead of abandoning the session, the researcher adapted. They shared their screen, acted as the “computer,” and had the participant instruct them on what to click while continuing normal think-aloud protocol.
The methodology changed. The learning did not.
This is where I think design becomes especially valuable inside large organizations. Different situations require different approaches, even when the underlying goal remains the same.
Good designers are often systems thinkers as much as interface thinkers. They look for movement within complexity. They identify friction points, organizational incentives, hidden assumptions, and opportunities for alignment that others may overlook.
Constraints, paradoxically, often sharpen creativity.
Without constraints, teams sometimes drift toward abstraction or endless exploration. Constraints force prioritization, clarity, and intentional tradeoffs.
The danger is not constraints themselves. The danger is internalizing them so deeply that teams stop imagining alternatives entirely.
That is when scarcity becomes cultural instead of situational.
The best teams I’ve worked with remained optimistic without becoming unrealistic. They acknowledged limitations honestly while still maintaining curiosity about what might still be possible within them.
That balance matters, especially in environments where meaningful change requires patience, adaptability, and sustained collaboration over time.
Innovation rarely emerges from perfect conditions.
More often, it comes from teams willing to stay curious long enough to find movement inside imperfect systems.