Eight ways work gets stuck.
Most businesses have a few.

Most of the work that ends up on your desk isn’t hard because it’s complicated. It’s hard in a handful of familiar ways.

After watching a lot of people walk me through their week, I’ve started using the same eight names for them. They’re the names I use in my Walkthrough reports, and they’re here so you can recognize them before we ever talk.

Book a free Walkthrough

A pitch-free hour. A written report within three business days. Yours to keep.

A process usually has more than one, and that’s normal. None of these are about someone doing their job badly. They describe how the work is set up, not the people keeping it going. The scenes are composites, and the names are made up.

It runs on remembering

Steps happen because someone remembers to do them, not because anything prompts them.

A new client signs, and somebody knows what that means: a welcome email, a shared folder, a kickoff invite, a note to billing, a check-in two weeks later. Nothing asks for any of it. It works right up until that person is busy, on vacation, or has eleven other things to remember that week.

You’ll notice

  • Reminders to yourself: sticky notes, flagged emails, calendar holds used as a to-do list
  • “I just know to…”
  • Things slip in busy weeks, not quiet ones

What usually helps

Move the remembering into the process. Sometimes that’s an automatic follow-up or a trigger between tools you already have. Sometimes it’s a checklist that starts itself. The point isn’t to take judgment away from people. It’s to stop spending their judgment on recall.

The same information, typed twice

Information gets moved between tools by hand.

An order comes in through one system and gets retyped into another. A client’s new address gets updated in the CRM, then in invoicing, then in the shared spreadsheet, if someone remembers. Each copy takes a minute. Together they take a surprising share of someone’s week, and every one is a chance for two places to disagree.

You’ll notice

  • Regular exports and imports
  • Copy and paste between tabs
  • “I update it in both places”
  • Small mismatches nobody can explain

What usually helps

Connect the tools you already have before adding another. Often the fix is picking one place where the information starts and letting everything else read from it.

Nobody trusts the numbers

People double-check the system because it’s been wrong before.

The dashboard says one thing, so someone pulls the raw figures to make sure. The report goes out only after a person has gone through it line by line. Nobody decided to work this way. The system was wrong once, at a bad moment, and checking became part of the job.

You’ll notice

  • A spreadsheet kept open “just in case”
  • Manual reconciliation before anything goes out
  • “Let me confirm that and get back to you”
  • More than one version of the same number

What usually helps

Fix where the numbers come from, not how they’re displayed. Another dashboard built on untrusted data just gives people one more thing to check. Once there’s a source people believe, the checking tends to stop on its own.

Assembled by hand

Something gets rebuilt from scratch every time, from pieces scattered across several places.

Friday afternoon, someone opens five tabs and starts pulling numbers into a report that looks almost exactly like last week’s. The report is useful. Making it is the problem: the same hours, every week, to produce something the business already had the ingredients for.

You’ll notice

  • “It takes an afternoon to pull together”
  • Reports with the same structure every time
  • The report is late whenever the person who makes it is out
  • People asking “is this current?”

What usually helps

Build it once so it keeps itself up to date. Craft & Communicate’s client reporting involved finding performance numbers by hand. I built them a client-facing platform with live data, and it’s now something the agency offers its customers.

Already seeing your week in here?

You don’t need to read all eight first. Bring one example of the work to a free Walkthrough, and you and I will work out which of these it is.

Book a free Walkthrough

Waiting on a reply

Work stops at handoffs, approvals, and questions between people.

Every step is quick. The waiting between steps isn’t. A proposal sits until someone signs off. A client’s question sits until the one person who knows the answer sees it. A task is done, but nobody downstream has heard. Much of the time isn’t spent working at all; the work is waiting to be noticed.

You’ll notice

  • Chasing: “Just following up on…”
  • Meetings that exist mainly to find out where things are
  • “I’m waiting on…” as a common answer
  • Work that moves fast once it finally moves

What usually helps

Make ownership and status visible, and cut the handoffs that don’t need to exist. Sometimes that’s software. Often it’s agreeing who decides what, and making it obvious where each piece of work is.

Only one person knows how

Part of the business depends on one person’s knowledge.

Dana knows how the quarterly filing works, which client needs their invoice formatted differently, and why that one integration breaks on the first of the month. Dana is great. Dana also can’t take a real vacation, and if Dana ever leaves, a lot of that knowledge leaves too.

You’ll notice

  • “Ask Dana”
  • Nobody can cover when that person is out
  • No documentation, or documentation only that person understands
  • New hires shadow instead of learning the work

What usually helps

Get the knowledge out of one head and into the work. Write it down, share it with a second person, or build it into the system so nobody has to carry it around. This isn’t about making anyone replaceable. It’s about letting the person who knows everything take a week off.

Waiting on your yes

Decisions come to you by default, not because they need you.

You’re cc’d on everything. Small calls wait for you: a refund, a schedule change, a discount for a longtime client. Nobody’s sure they’re allowed to make them. Your team isn’t unwilling. They just don’t have a clear line between “decide this” and “check with me,” so it all lands on your desk. This is often the plainest answer to “why does everything come back to you?”

You’ll notice

  • Approvals pile up when you’re busy
  • Capable people hesitate on things they could handle
  • You answer the same kind of question again and again
  • Work slows down when you travel

What usually helps

This is usually a process change more than a software change: clear decision rules, limits people can act within, and a short list of what genuinely needs you. Software can help hold those lines later.

The workaround became the process

Someone built a workaround to cover a gap, and now the business depends on it.

The booking tool couldn’t handle the way you actually schedule, so someone started a shared spreadsheet. That was three years ago. Now the spreadsheet holds information the booking tool never will, new hires learn it first, and it has a name. Nobody’s quite sure what would happen if it disappeared.

You’ll notice

  • It has a name: “the Monday sheet,” “Jen’s tracker”
  • “We do it this way because the system can’t…”
  • New people learn the workaround before the tool
  • The person who built it is the only one who can fix it

What usually helps

Decide on purpose: make the workaround official, or fix the gap it was covering. A workaround is often the best thinking anyone has done about how the work should go, and someone built it because they cared. Sometimes the right move is to take their design seriously and build it properly.

Recognize a few?

Most processes that keep coming back to you have two or three of these at once. Knowing which to fix first is the hard part, and that’s what the Walkthrough is for.

You spend about an hour walking me through the work. Within three business days you get a written report: what’s happening, what I’d recommend, and where I’d start. It’s free, and it’s yours to keep.

Book a free Walkthrough