5 min read

The work your project plan can’t see

The work your project plan can’t see
I bet you didn't know it took 40 Slack messages, a phone call, and 2 meetings to figure this one out.

It’s 10:17 on a Tuesday, and you’re trying to figure out whether a design is approved.

In Slack, the designer says she’s ready to hand it off. In an email you weren’t copied on until this morning, the client asks to see one more option. And in yesterday’s Zoom, someone said, “I think we’re good,” which apparently meant three different things to the four people on the call. Meanwhile, the developer has a window to start this afternoon and wants to know whether to use it.

So you pull up the Zoom transcript and run it through Claude. You ask it to find where the client approved the design and show you the exact exchange in case you missed something. It takes you right back to “I think we’re good.” You read the lines around it. Someone says, “Great,” and the conversation moves on to the launch date. That’s as close as anyone got to a decision.

You catch the account lead between meetings, check with the designer, and send the client the question you wish someone had asked on Zoom. “Are you happy for us to start building the layout while we work on another headline?” The client writes back, “Yes, the layout is good. We just want another headline option.” You tell the developer what’s ready to build and agree on a time for the designer to send the new copy.

In the project plan, the task goes from “In review” to “Ready for development.” One little, significant change. Naturally, it took the better part of an hour.

The work between the updates

That hour came in pieces. You stopped what you were doing to read the client’s email, checked the transcript, and went back to Slack to see who was around. While you waited for someone to get back to you, you tried to pick up whatever you were doing at 10:16. Then the reply came in, and you had to get your head back into the design conversation. By lunch, you’ve opened the same spreadsheet three times, and you still owe someone a budget update.

There’s also the frustration of being the person everyone asks for an answer when everyone has a different piece of it. The designer heard approval. The client thought they’d asked for a small revision. The developer just wants to know whether to start. You can see how each person got there, which makes it hard to be mad at anyone in particular. But you’re still a little mad.

Claude saved you some digging, thanks to call transcripts and simple prompts. But you still had to figure out what each person meant, get a clear answer, and get it back to the people who needed it. Do that a few times in a morning and it’s easy to see why a day with very little to show in the project plan can feel like a full week of work.

Keep the work moving

On a remote team, some of this comes with the territory. People will talk in Slack, make requests over email, and say things on Zoom that sound more definitive in the moment than they do when you read them back. You can spend a lot of time trying to reconstruct the whole conversation. I’d start with the person who’s waiting to do something. What do they need to know, who can give them an answer, and how much time do you have to get it?

Ask the question you actually need answered. “Any update on design?” is easy to send and easy to put off answering. Try “Can we start building the layout while you review the headline? Our developer has time this afternoon if we can confirm by noon.” The client knows what you’re asking, when you need an answer, and what their answer makes possible. If you’re using AI to check whether someone already answered it, ask for the exact exchange and read a few lines on either side. Five minutes with the transcript can help you ask a much better question.

Find the part that can move. One open question can make a whole task look blocked. Ask the people doing the work what they can start with the information they have and what they’d have to redo if the answer changes. In this case, the developer can build the layout while the designer works on the headline. On another project, the headline might affect the whole layout. The people doing the work can usually tell you in a minute whether starting now will save time or cost them time tomorrow.

Put the decision where people will look for it later. Once you have an answer, write it down where the team goes to pick up the work. “Layout approved. Dev can start today. Jamie will send the revised headline by noon Wednesday.” Share that same update with the people who were part of the conversation. Otherwise, someone will find Monday’s “I think we’re good” on Thursday and ask whether the design is approved. Again.

Show what moved because of your work

I know how easy it is to get to Friday, look back at a week full of conversations, and think, What the hell did I actually get done? I can remember the bigger things I shipped. It takes me longer to remember the ten-minute conversation that kept someone from spending half a day building the wrong thing. By Friday, that conversation feels like a small part of Tuesday. To the person who got to use that half day, it mattered.

That’s worth remembering when you write a status report or sit down with your manager. I’d write “Confirmed the layout approval so development could start on schedule while the headline was still in review.” That gives people a clearer picture of what you did and why it mattered. The same approach works when you’re still waiting on something. “We need a decision by Thursday to keep our Friday build slot” gives someone enough context to help you get an answer.

And if you spend that same hour untangling approvals every Tuesday, bring it to the retro. The client might assume that saying “looks good” on Zoom is enough, while your team is waiting for an email nobody knows they’re supposed to send. You can agree on what approval sounds like, who confirms it, and where it goes. Saving yourself that hour next Tuesday counts as good project management, too.

Before you send your next status update, pick one task that moved this week and finish this sentence: “Because we _____, the team was able to _____.” It might be the most useful line in the whole update.


T L ; D R – On a remote project, moving one task forward can mean piecing together Slack, email, and a Zoom transcript just to find out who agreed to what. Ask the question that gets someone unstuck, write the decision where the team can find it, and use your status update to show what the team could do because of it.