In a remote team, accountability is a visible record. If I cannot see who owns a task, what done means, and when it was last checked, nobody is accountable. We are just hoping in sync.
I build alone, and most of the people I build with I have never met in person. Rootmail is mine, solo since June. The coordination I do happens in public issue threads on repos I do not own. This week a fix I suggested in one of those threads landed as a merged pull request. I never met the maintainer. The thread was the whole working relationship: the problem stated, the fix tried, the merge as the proof. When the record is clear, I do not need to ask for status. When it is not, no meeting fixes it.
Here is what I keep in the record.
One owner, named next to the task. "The team owns it" means nobody owns it. A task with a name next to it gets done or gets asked about. A task with a group next to it waits.
Done means a check passed. A bug counts as fixed when the exact steps that broke it stop breaking it. A feature counts as done when the test that proves it passes. I write the check next to the task, in the same place, so anyone can run it without asking me what done means.
The board is the meeting. I write status down: what shipped, what broke, what is next. Three lines, async, where anyone can read them. A meeting is for the one thing the record cannot settle, not for reading the record out loud.
Decisions live where the work lives. If a decision is made on a call and never written down, it was not made. I put it in the issue, the doc, the thread. The next person looks there first.
Wins and misses both go in the record. A missed deadline with the reason written next to it teaches something. A missed deadline nobody mentions teaches people to hide misses.
I go first. My own progress is visible before I ask anyone else for theirs. I publish what shipped, what broke, and what is next, in the same shape every time. The standard is what I do, not what I ask for.
What is the one check that would tell you, without asking anyone, whether your team's work is actually moving? Name the check, not the tool.
Next in this series: On to the next phase.
Top comments (0)