By Adi David
The debate over hybrid work is rarely just about where people sit. It’s a proxy for a deeper organizational question: how much autonomy should employees have over how they do their work, and how much structure does the organization need to function well? Remote days offer flexibility and control; in-office expectations offer consistency and connection. Neither is inherently the healthier choice. What matters is whether the balance between them actually fits the organization and the people in it.
We see this tension constantly in our organizational-improvement work with nonprofits, government agencies, and mission-driven businesses, and it tends to surface most clearly at moments of growth. A nonprofit that scales from one program to three often keeps running on the informal, autonomy-heavy norms that work when the whole team fits around one table. As new staff join, gaps start to appear because no one ever defined who decides what. A newly launched program can drift the opposite way just as easily, with layers of process and sign-off built in before anyone has learned what the work actually requires, leaving staff spending more energy navigating the structure than delivering the program itself. Neither happens because leadership got it wrong. It happens because the right balance for an organization at one size or stage often isn’t the right balance for the next.
Two Forces, Both Necessary
Autonomy is the ability to shape how, when, and sometimes what you work on and is one of the most consistent predictors of intrinsic motivation and wellbeing in organizational psychology. Self-Determination Theory identifies it as one of three basic psychological needs, alongside competence and relatedness. When people feel a sense of ownership over their work, they’re more engaged, more resilient to stress, and more likely to stay.
Structure, meanwhile, gets a bad reputation it doesn’t fully deserve. Clear processes, defined decision rights, and consistent expectations aren’t the enemy of wellbeing, they’re often what makes autonomy usable. Structure tells people where the boundaries are, so they can move freely within them. Without it, autonomy turns into ambiguity, and ambiguity is a well-documented source of stress, not empowerment.
The research on this is called “bounded autonomy” or “autonomy within structure” and it is the finding that people do their best, most motivated work when they have real discretion over how they accomplish something, paired with clarity about what success looks like and where the hard limits are.
Why Organizations Tend to Overcorrect
Most organizations don’t land on this balance naturally. They tend to drift toward one end or the other, often for understandable reasons.
Mission-driven organizations often over-index on autonomy. Staff join because they believe in the work, and leadership trusts that belief to carry a lot of weight. The result is well-intentioned under-structuring: talented, committed people doing valuable work without the scaffolding to do it sustainably.
Highly regulated or bureaucratic organizations tend to overcorrect the other way. Process exists for good reasons: consistency, accountability, compliance. But when process becomes an end in itself rather than a means to an outcome, it can squeeze out the autonomy that even highly structured roles need to stay motivating. Skilled, mission-driven staff end up following procedure with little room to exercise judgment, and disengagement follows, not because the work isn’t meaningful, but because there’s no space left to do it their own way.
Neither is a matter of poor judgment. Both are the natural result of leaning fully into one priority until the other fades.
What Getting It Right Looks Like
The organizations that manage this well tend to share a common approach: they use structure to clarify outcomes, not to control methods. Clear goals, clear decision rights, clear boundaries, and then genuine latitude in how people get there.
In practice, this might look like:
- Defining what a successful outcome looks like, and leaving the how open to the person doing the work
- Being explicit about where the real boundaries are (budget authority, approval requirements, compliance limits) so autonomy doesn’t quietly become guesswork
- Revisiting structure as roles and programs evolve, rather than treating it as something set once and forgotten
- Distinguishing between structure that protects people (clarity, consistency, and fairness) and structure that mainly protects process for its own sakeÂ
That last distinction is worth sitting with. Not all structure is created equal. Some of it exists to support the people doing the work. Some of it exists because it always has. The first kind is worth strengthening. The second kind is usually worth questioning.
Where This Shows Up in Our Work
There’s no universal ratio of autonomy to structure that works for every organization. It depends on the complexity of the work, the maturity of the team, and the environment the organization operates in. A newer program with less-established processes may need more scaffolding to run consistently; a seasoned team delivering mature, well-understood work may need far less. An organization operating under heavy regulatory or funder requirements has different structural needs than one with more flexibility in how it defines success. The goal isn’t to find the “right” amount of structure in the abstract, it’s to find the amount that lets your specific people do their best work sustainably.
This is why our organizational improvement work rarely starts with a template. We begin with a needs assessment and stakeholder engagement process that looks at what’s actually working and what isn’t inside a specific organization, surfacing the places where staff are left guessing because structure is missing, and the places where process has calcified into something that limits good people from doing good work. From there, business process redesign and program design build on what we find, rather than importing a standard model. Change is tested iteratively and built with buy-in from staff along the way, because the right balance of autonomy and structure isn’t something we determine at a desk, it’s something we uncover in partnership with the people who will actually work within it, and it looks different for a growing nonprofit, an established municipal agency, or a program navigating new funder expectations.
A Question Worth Asking
The next time your organization is evaluating a process, a role, or a program, it’s worth asking a simple question: is this structure protecting our people, or is it protecting the process itself? The answer usually points to exactly where the balance needs to shift.
