Why It Keeps Landing on Your Desk

Move one of a diagnosis we are running live this week. Before you guess at why a problem keeps coming back, watch where the work stops.

The founder pulls up June's agenda to prep for July's meeting, and the same line item is sitting there. Third month in a row. Everyone in the room already has a theory about why.

You probably have your own version of that line item. The thing that keeps coming back.

Here's the whole idea in one line: stop asking why it happens. Go find the exact spot where the work sits and waits.

That spot is a real place. A desk it lands on. A name it waits for. A folder it goes into and doesn't come out of for three days. The work stops in the same place every time, and that place tells you more than any meeting will.

Most of us do the opposite. When something keeps coming back, we build a theory. We decide it's a motivation problem, or a tools problem, and we fix the thing we named. Then it comes back, because we fixed the explanation and never found the actual stuck point.

This week we're running a diagnosis the other way around, one move a day, on one firm. You get to watch it happen instead of reading the conclusion.

The firm we're diagnosing (a composite, on purpose)

One note before we start. The firm is a composite. We built it from the shape of problems service firms this size run into. It's not a real client, and nothing in it is a real quote or a real number. We made it about fifteen people, founder-led, doing project work for clients, because that's where these patterns show up most clearly. A firm that size is also small enough that the founder still feels every stall personally.

The thing that keeps landing on this founder's desk is the proposal that goes out to win new work. It's late again. It's been late, in some form, for months. The founder is sure they know why. So is everyone on the team. And they're all sure of slightly different things.

Watch where it stops

We don't ask why. We follow the proposal itself through the week and mark every place it waits.

It moves fine at the start. The senior associate who builds each proposal does that part on time, and could scope and price it too. Then it lands in one person's queue for a scoping and pricing sign-off. And it sits.

Not because that person is slow. That sign-off is the one task in their week with no fixed slot, no trigger, nothing forcing it to happen on a particular day. It only moves when somebody chases it. Nobody likes chasing this queue, so the chase comes late, and the work comes late. When we traced it, more than one proposal was parked there, and the associate who wrote them was waiting right along with them.

That's the stop. One handoff, one role, one sign-off with no home in anyone's week.

Look at the chasing for a second. Nobody designed it. It's a workaround, the firm routing around a gap it has never named out loud. Workarounds like that are diagnosis you already paid for. Go collect it.

Notice what we didn't do. We didn't ask the team what was wrong. Ask, and you get explanations, and explanations arrive pre-sorted by who feels responsible and who doesn't. The work has no such loyalties. It stops where it stops, every time. Trust the stop.

The comfortable version

There's a more comfortable story available, and it's the one this founder has been telling. The team needs to care more. The team needs to move faster. The next hire will fix it. Stories like that are easy to keep because they live in the future and spread the blame thin. The uncomfortable version is specific, and it's sitting in one queue right now.

The loud explanation is rarely the one holding things up. The real one is usually quieter, more boring, and a little embarrassing, because it's often something the founder set up themselves and never came back to.

We're not naming this firm's real constraint today. We've only done move one of five: watch where the work stops. Tomorrow we separate what the team is sure is wrong from what is actually stuck. Those turn out to be two different things.

How to run the same trace (one hour, this week)

For a lot of project-based firms, mid-July is a lull. The first-half scramble is over and the fall rush hasn't started. If that's your calendar right now, this is the week the trace is actually possible.

You don't need to watch anyone. Here's the whole hour:

1. Pick the thing that keeps coming back late.
2. Take the last three times it was late. Rebuild each one from the record you already have: the email thread, the file history, the task comments.
3. For every handoff, write down two timestamps. When the work arrived in someone's queue, and when it was next touched.
4. Add up the hours anyone actually worked on it. Maybe six. Then count the calendar days since it started. Maybe twenty-eight.
5. The gap between those two numbers isn't work. It's waiting. Find the longest wait. If it shows up in two of the three runs, that's your stop.

Most late deliverables aren't slow work. They're short work standing in a long line.

If you're the one who still signs off on the thing that keeps slipping, you already know which problem we mean.

You don't need us for this move. You need a recurring problem, an hour, and the willingness to follow the work instead of the story you tell about it. Find the thing that keeps landing on your desk. Then go watch where it stops.

This week's diagnosis, one move a day: watch where the work stops · JSX0 · JSX1 · JSX2 · JSX3

Continue the series

This is part 1 of a 5-part series on Watch the Diagnosis. The full arc:

• Monday: Why It Keeps Landing on Your Desk (this post)
• Tuesday: The Complaint Is Not the Constraint (coming Tuesday)
• Wednesday: The Cheapest Question That Could Prove You Wrong (coming Wednesday)
• Thursday: The One Thing That Moves Everything Else (coming Thursday)
• Friday: The Recommendation, and the Honest Option to Do Nothing (coming Friday)

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.