The short version
- You do not want a dashboard of activity. You want an answer to a specific question, usually about one piece of work, usually right now.
- Status meetings and weekly reports answer the wrong question. They tell you what happened, not where something stands.
- The version that does not feel intrusive is the one where the person decides what the record says. They write it, you read it.
- If your team feels watched, it is because the information flows without their involvement. Keep them in the loop and the same information is fine.
Every manager of a distributed team runs into the same tension. You need to know where things stand, because you are accountable for them. Asking constantly makes you the person who asks constantly, and that changes how people work in ways you will not enjoy.
"I do not want a report every Friday. I want to know, on Tuesday afternoon, whether the client migration is going to land."
The question you are actually asking
Notice how specific that is. One piece of work, one moment, one answer. Not a view of everything and not a measure of effort.
This is why activity dashboards disappoint. They answer "how much is happening", which you did not ask, and they do it by counting things that are easy to count. What you wanted was a sentence: it is nearly done, the blocker cleared yesterday, it lands Thursday.
Start from the question. Write down the five questions you find yourself wanting answered in a typical week. Almost all of them will be about the state of a specific thing, and almost none will be about how busy anyone is.
Why weekly reports do not answer it
Three reasons, all structural.
- Timing. Written Friday, read Monday, needed Tuesday. Status ages badly.
- Format. A report is written to sound like progress, so it lists what was done. What was done is not where it stands.
- Cost. Everyone spends thirty to forty minutes writing them for an audience of one, and the audience skims. The people writing know this, which is why the quality drops after a month.
The same problems apply to the standup, which is the meeting version of the same artifact. See replacing the status meeting while keeping the status.
Who writes the record decides how it feels
Here is the whole distinction between visibility and the thing your team will resent.
If information about someone's work reaches you without passing through them, it feels like being observed, regardless of your intentions, and people respond by managing their appearance rather than their work. If the person writes what the record says, reviews it, and knows exactly what a colleague or manager will see, it is just communication, and it costs nothing emotionally.
Same information. Entirely different experience. So build any arrangement so that the person is the author, not the subject.
The practical version is short. The person writes a brief at the end of their day: what moved, what is open, what is blocked, what is next. Four lines. They decide what it says. You read it when you need it rather than receiving it as a report.
What to read instead of asking
This is what StandIn is built for, and it is deliberately narrow. The daily brief takes about ninety seconds because most of it is drafted from work that already happened, and the person confirms or corrects it before anything is visible. When you have a question, you ask and get an answer from that brief, in their words, with a source under it. It never guesses. If the answer is not in what they wrote, it says so and names who to ask, rather than inferring something plausible.
That last property is what makes it usable as a management tool. An answer you cannot trace is worse than no answer, because you will act on it. An answer with a source under it, written by the person, is something you can take to a client. See how it works and what it will not do.
The effect on your week is that the five questions get answered on Tuesday afternoon, when you have them, without a meeting and without anyone being asked to report.
What the one to one is then for
When status stops being the content of the one to one, the half hour gets a lot better. It becomes about the things that genuinely need a conversation: what is hard, what they want next, what you are getting wrong, decisions that are stuck.
Most managers who make this change report the same thing, which is that they now know more about the work and more about the person, and are asking about neither in the meeting. See status reports executives actually read.
Common Questions
Will my team see this as checking up on them?
Ask them to write the brief for the colleague in the other time zone, not for you, because that is the primary reader and it is true. Visibility for you is a side effect of a record built for the team.
What if someone writes nothing?
Treat it as a signal rather than a compliance issue. People stop writing when they are stuck, overloaded, or when the thing they would have to write is uncomfortable. All three are worth a conversation, and none is worth a reminder email.
Is this not just a status report with extra steps?
The difference is the direction. A report is written for a manager on a schedule. A brief is written for whoever needs it next, read on demand, and is usually four lines rather than a page.
How does this work for contractors or agencies?
Better than with most reporting, because the daily brief gives you current state without a weekly call, and because the source under each answer means you can check rather than take it on faith.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.