🚩Tactical Memo 087: Orphaned Work Dies

In partnership with

Welcome to Tactical Memo: Tactical advice for managers running teams, projects, and operations in the AI era. Read by 18,000+ leaders at Amazon, Deloitte, and Google. If someone forwarded this to you, join our free community here.

Want to get the most out of ChatGPT?

ChatGPT is a superpower if you know how to use it correctly.

Discover how HubSpot's guide to AI can elevate both your productivity and creativity to get more things done.

Learn to automate tasks, enhance decision-making, and foster innovation with the power of AI.

Download the free guide

Before We Get Started…

I'm running three free lightning lessons over the next few weeks. Each one is 30 minutes, live on Zoom, and built around prompts you can use the same day.

48-Hour Project Launch
Friday, Aug 21 at 12:00 PM EDT
Most projects lose two to three weeks between "you're assigned" and "we've launched." I'll walk the exact 48-hour system: brain dump to working charter to kickoff to launch summary, with the prompt used at each checkpoint.
Register link

Cut Scope Creep
Friday, Sep 4 at 12:00 PM EDT
In one project I'll show you, 23 "small" asks became 380 hours, $147K, and 3 slipped weeks. You'll leave with an AI-built Conversation Plan: the impact math, the reframe, your opening line, and a guardrail stakeholders will actually use.
Register link

Stakeholder Reporting
Wednesday, Sep 9 at 12:00 PM EDT
If you write the same status update four times a week (exec, client, team, boss), this one is for you. One prompt turns a ten-minute brain dump into all four drafts in about 30 seconds.
Register link

All three are free. Pick one or grab all three.

For years I had a problem I couldn't name.

Things fell through. A task nobody clearly owned. A follow-up that lived in the group chat and belonged to no one. Every time one blew up, everyone was surprised, because everyone assumed someone else had it.

I blamed talent. I blamed workload. The honest answer is that I let work float, and floating work fails quietly until the day it fails loudly.

So I made one rule. Every outcome gets an owner, and the owner is a name. Not a team. Not a channel. If a task can't tell me whose it is in one sentence, it's an orphan. Orphans die.

I call it the No-Orphan Rule. Here is how I run it.

1/ End every meeting with the same six words

Who owns this, and by when. I say it out loud before anyone closes a laptop, for every action that came up in the room. It feels repetitive by week two. I do it anyway, because the meeting is where ownership is cheapest to assign and most expensive to skip. The day I started closing meetings this way, the dropped balls basically stopped.

2/ Put one name on every outcome

When someone says "marketing has it," I stop and ask who on marketing. A team owning something means nobody owns it, because every person on that team is free to assume it's someone else's job. So I write a single name next to every deliverable, even when a whole group will do the work. One name can be asked a question. A team can only be surprised.

3/ Run the one-sentence test weekly

Once a week I read my project list and try to say, for each item, "this is Sam's, due Friday." If I can't finish that sentence, I've found an orphan. I don't investigate how it happened. I assign it that day, before it has time to blow up. Finding orphans early is boring. Finding them late is a fire drill with an audience.

4/ Sweep the group chat every Friday

The most dangerous requests live in channels. Someone asks for a follow-up in a thread, three people react with a thumbs up, and everyone logs off believing it's handled. So every Friday I scroll the week's threads looking for asks that never landed on a person. I've caught client commitments this way that would have died quietly. A thumbs up is not an owner.

5/ Transfer ownership in writing

Vacations, reorgs, and "can you take this" hallway asks are where orphans breed. So when work changes hands, the transfer goes in writing: the item, the new name, the date. The old owner stays on the hook until the new owner confirms in the thread. Silence is not a handoff.

6/ Attach a date to every name

A name without a date is half an orphan. Somebody owns it, but it can float forever, and floating work rots. So the answer to "who owns this" is never complete until I hear a day I can put on a calendar. Not "soon." Not "this sprint." When the answer is Friday, Friday becomes the day I find out whether the plan was real.

7/ Ask "who is we" out loud

The most common answer I get is "we've got it." I used to accept that, because pushing back felt like distrust. It was actually me avoiding an awkward five seconds, and it cost me weeks of cleanup. Now I ask, in front of everyone, "who is we?" The room goes quiet for a beat, then a name appears. That beat of silence is the rule doing its job.

Insider Tip: My team didn't get more talented the month the dropped balls stopped. The work simply stopped floating. If your team keeps surprising you with things nobody caught, look for orphans before you blame talent.

Do This Now: This week, end one meeting with "who owns this, and by when." Say it out loud. You'll feel the room change.

Free Library of Cheat Sheets👇

I put together a bundle of my top playbooks and cheat sheets for people who want to think sharper, lead better, and navigate the real career rules most people only learn the hard way → Grab it here for free.

Until next time,

Justin Bateh, PhD
Founder and Editor
Tactical Memo