Read time: 5 minutes

Hey Subscriber First Name

Around 2014, I was delivering major track works and losing sleep over the paperwork. We had a big delivery review coming up and the documentation wasn't where it needed to be. The process side of the job, the part every textbook says has to be right, was the thing keeping me awake.

The delivery team were relaxed. They cared about the work. What they didn't care about was the paperwork I was sweating over, because they knew the actual work would land and the process would, mostly, sort itself out.

I remember the penny dropping. They were carrying the work through experience, steering around the things that genuinely needed attention, while I treated every fault as if it had the same weight. They weren't careless. They knew which problems the outcome could absorb.

That distinction has stayed with me ever since.

There's no such thing as a clean project. There's only the dysfunction you've learnt to work around, and the dysfunction you haven't.

The textbook version of delivery is orderly. The plan is accurate, information moves cleanly, ownership sits in the right box. Real work rarely behaves that well. It turns up with optimistic dates, awkward conversations, and important decisions being carried by people whose names barely appear anywhere official.

And yet outcomes still land. They land because teams build a working relationship with the dysfunction. They learn where the floor dips, which door sticks, which noise means trouble. The mess becomes familiar enough to move through without anyone pretending it's disappeared.

Not all of it matters equally. Some problems the work can carry. The team understands them, someone is steering around them, and removing them completely would cost more than it's worth. Others threaten the outcome, often before anyone official notices. Telling those two apart is most of the job, because every hour spent tidying the first kind is an hour taken from the second.

The difference isn't how untidy something looks. Late paperwork can make plenty of noise and still leave the work safe to deliver, as long as someone knows what's missing and can get it back. A quiet assumption about access, resources or a decision nobody has actually made can look fine on a report and still bring the whole thing down. The mess you can see and the thing that can hurt you are rarely the same.

So which dysfunctions keep turning up?

The first is the plan itself. Plans are useful, but they're usually a hopeful account of a future nobody has reached. Kahneman and Lovallo described the planning fallacy, and Bent Flyvbjerg's book How Big Things Get Done keeps finding the same underlying habit across thousands of projects: we plan from inside our own project, using what we hope will happen, and pay too little attention to how similar work actually went.

You won't plan your way out of this, so work with it. A plan is still worth having because it gives everyone a shared route. Just treat it as a best guess and check it against something that already happened. If similar work took twelve weeks last time, an eight-week plan needs a real reason. Then keep changing it as things change. If the dates have survived every setback untouched, they are being defended rather than managed, and the plan has stopped telling you where the work actually is.

The second is the speed of bad news. Rosen and Tesser called this the MUM effect in their 1970 research: people are more hesitant to pass on bad news than good news. Most of us don't need a study to recognise the feeling. A difficult message gets softened on its way up because nobody wants to be the person who changes the mood in the room. By the time the truth arrives it's usually expensive, and the small concern someone noticed on Tuesday becomes the issue everyone discusses on Friday, with less room to act.

You won't stop people softening bad news, so make it cheap to bring you. Thank whoever tells you, especially when it's inconvenient, because your first reaction sets the price of every warning after it. Ask where the work might go wrong rather than what people are holding back, so nobody has to own up to anything. And notice how long it's been since someone told you something you didn't want to hear. If it's been a while, that's rarely because nothing is wrong.

The third is the work that lives off the chart. Every formal plan has an unofficial layer underneath it, made up of the people who remember the assumption everyone forgot, chase the thing nobody realised was connected, and know who to call when the usual route closes. That's what the delivery team understood in 2014. The real ownership was living in their judgement.

That informal layer keeps a lot of projects moving, so the answer isn't more process. It's knowing who is actually holding what. Ask who really carries each important risk, not whose name is on the document. Write that name down and give them the authority to act. Once it's openly theirs, they can bring it to you instead of quietly working around it.

None of this gives you a clean project. The plan will still wobble, bad news will still be uncomfortable, and some of the work will always depend on judgement no process can capture. What you're aiming for is a project where the problems you know about get carried along without quietly turning into something worse.

Early in my career I thought doing this well meant fixing every visible flaw. That review taught me something more useful. You can stop polishing every rough edge and put that attention where the damage would be worst. The standard stays just as high. You're only being honest about what the work actually depends on.

Making it happen means getting better at telling those apart. Live with the problems that won't stop the work. Raise the ones that will, early.

MAKING IT HAPPEN: Your Weekly Strategy

This week, spend fifteen minutes on one piece of work.

Write down the three dysfunctions everyone is already working around. For each one, name who carries it and what would tell you it has stopped being something you can live with. Then ask the team: "If this goes wrong, where do you think it starts?"

You aren't trying to tidy the whole project. You're agreeing which ones you can live with and where the team needs to step in.

CHEAT SHEETS

The free cheat sheet library is here. I'll keep adding to it. Save the link and grab whatever helps.

Share this with someone who keeps the work moving even when the process looks untidy.

bilaljamil.com | Newsletter archive

Hit reply and tell me which dysfunction your team has learnt to carry. I read every one.

Have a great week and speak soon,

Bilal