What Teams Need Before They Can Work Differently

Dana, a program director at a 70-person workforce nonprofit, read a case study about a peer organization that had flattened its management structure and moved to self-managed teams. Turnover dropped. Staff satisfaction climbed. Productivity actually went up.

She brought it back to her leadership team and within a month every department was told to run weekly retros, cut a layer of sign-off, and start making decisions “closer to the work.”

Four months later: save for meeting names, not much changed.

Managers still routed every exception through their supervisor, because the supervisor was still the one who’d catch it if something went wrong. Two departments slowly stopped doing the retros. A third kept them on the calendar, but nothing discussed in them ever changed anything, so people stopped saying anything real.

What happened?

The tactic arrived looking like a done deal

A specific practice—agile stand-ups, 360 peer reviews, self-managed teams—usually shows up already proven. Someone else tried it; it has a name and a track record. When the tactic and the strategic question arrive at the same time, pulling them apart in the moment is genuinely hard (especially with a board asking what’s new this quarter). Three questions can help separate them before anything gets put in play:

1. Does this fit how our culture actually works (versus how we describe it in the handbook)? A tactic built for a flat, informal culture behaves very differently inside a place with twenty years of “check with your supervisor first” baked into it.
2. What stage are we at, compared to where the case study was when they started? Many culture-focused approaches assume people already trust each other, already understand the org’s priorities, and already have practice making shared calls. Do an external audit: what do you know about the broader context of the case study you’re trying to model after? If the case study you’re borrowing from had all of that in place before they started and you don’t, you’re not doing what they did; you’re doing the version of it that’s still missing the groundwork, and you’re handing everyone the keys before the driver’s training.
3. Is this a starting move, or a later one? Sometimes someone else’s step three can serve as your step one, but you need to be informed on whether it’s a reasonable choice. Conduct an internal audit: understanding where the point-in-time application sits will matter for how (and when) you try to implement for your team. (This is also why tactics should not be employed absent a coherent strategy.)

The culture wasn’t properly defined or primed

Staff rarely pushes back on a new approach outright. An early adopter or two usually tries the new behavior and the org’s existing structure either backs her up, or it quietly undoes it. Imagine a case manager holds off looping in her supervisor the way the new approach asked her to. If that goes fine, she’ll probably do it again. But if her supervisor still asks why he wasn’t consulted, or she gets a note in her next review about “not following the chain,” the message lands whether anyone verbalizes it or not: the old way is still what gets rewarded. Multiplied by a hundred small decisions a week, the momentum and will to chart a new path both die quickly. Without foundational work around identifying and naming implicit norms, established rhythms will resist a new pattern trying to take shape.

And to add complexity, a mid-sized organization isn’t just one culture. It’s often several, under one umbrella. Case managers, finance, leadership each organically develop their own MOs and unwritten rules, so a tactic that lands well in one part of the building can flop or backfire outright in another for no reason other than the conditions underneath are different. By trying to roll one practice out everywhere on the same Monday, you’re pretending that those differences don’t exist. Perhaps paradoxically, knowing, understanding, and honoring the subcultures is a much more effective way to both enact change and pursue cohesion across the whole organization.

The change prioritized lines over loops

Big companies often have a whole function for this exact problem: someone whose job is to slow a new idea down long enough to ask if it fits, if the org’s ready, if it’s being sequenced right. Mid-size nonprofits and public agencies almost never have that person; usually, the one who read the case study and got excited is the same one who makes payroll, runs the programs, and reports to the board. It’s nobody’s job to poke holes in the idea before it ships, so no “fit-check” happens before adoption happens (or tries to), wholesale. Most standard change management advice doesn’t help much here either, because it’s built like a recipe: step one, then step two, step three…until the whole process is checked off. While in theory that feels tidy and approachable, linear solutions for non-linear realities are bound to frustrate and fail. In practice, finance decisions shape what case managers can promise clients, which shapes what leadership hears in a board meeting, which shapes what finance decides next. Pull one thread and something tugs three departments over, creating unintended consequences unless the approach at the outset was designed to surface and account for them.

The instinct to fix this is to segment: build a plan tailored for finance, one for case managers, one for leadership, each tailored to that group’s version of the change. Sometimes that helps, but segmenting the plan doesn’t segment the organization or solve for the holistic problem at hand. While it does attempt to meet differentiated needs, all three groups are still tangled up in the same loops underneath. Split the plan into three clean lanes and you can end up with three teams more walled off from each other than before you started, each now moving on its own tailored timeline and further from the other two than when the whole mess at least ran through the same meetings.

A plan built like a hallway—walk in one end, come out changed on the other—can look great on paper and still fall apart by the next all-hands. Real change moves the way everything else in an organization does: several things happening at once, reinforcing or undercutting each other, with no clear point where you get to say “step one is finished; moving on.”