Ask someone on a distributed team what they’d change about how their work is set up. Not the people, not the tools, the structure of how the work holds together. Most of them answer in about three seconds.
The speed of that answer reminds me that people working at a distance from their teammates and customers often run a “director’s cut” of their work in their head. They observe the work as well as do the work.
This means the problems, the speedbumps, the points of friction are well known territory.
The thing that’s so ripe for change is sitting right there, fully formed, waiting for someone to ask the question.
Why the answer comes so fast
A senior engineer says: “I’d make it so a decision we already settled doesn’t get reopened every time someone new joins.” A team lead says: “I’d make it so I’m not the only person who can say where the project actually stands.” A contributor says: “I’d write the handoff down once instead of re-explaining it on four separate calls.”
So the change gets named in three seconds, and a year later it’s still there.
What they’re describing is the design of the work, and they can describe it exactly.
Why naming it changes nothing
Naming the problem and changing how the work is designed are two different jobs. The first takes three seconds. The second has no owner.
Look at the engineer’s answer. Making a settled decision stay settled means recording it with its reasoning and the conditions that would justify revisiting it, so the next capable person who arrives meets a decision and its rationale instead of an opening to relitigate. That’s real work. It’s also no one’s assignment. It isn’t on a roadmap. Nothing triggers it.
It competes for attention every week against the engineering delivery work that has deadlines, and it loses every week, reasonably, one week at a time.
This is why the three-second answer survives for a year. The work to fix the problem isn’t “owned” and unowned work (maybe) comes after all owned work is completed. Has that happened recently in your experience?
Why the felt sense needs language
The need for work redesign arrives as a feeling before it takes on the concreteness of a plan. “I’d make decisions stay made” is true and it is not yet actionable. Which decisions. Recorded where. Retrievable by whom. Held against what test before they legitimately show up for (re)discussion.
The distance between “I’d make decisions hold” and the fix is where the change gets stuck. The feeling is correct. It just can’t be acted on until it’s specific enough to build. Most people never get the chance to make it specific, because no conversation in their week addresses it.
That translation, from the felt answer to the exact change, is comparatively small on its own. It’s also what turns a complaint you’ve had for a year into something you can do about it.
The thing you’d change first is real, and it’s probably right. It stays undone because nothing in how the work is designed makes it happen.
The diagnostic asks you the question, then turns your three-second answer into language precise enough to act on. You go in with what you already know. You come out with a clear picture of what you’re dealing with and what to do about it. Choose Your Diagnostic