The 10-Minute Habit That Made Me a Better Remote Worker

| 4 minutes read

My first end-of-day message at McKinsey came back covered in red. My manager wanted ten rewrites before she let me send it. I was furious. Why am I spending 30 minutes on a Slack message? Nobody reads this stuff. (Funny side note: she became a mentor and we are still friends today.)

I was wrong about the last part. People do read it. But I was right that it took too long. Once I learned the format, it takes 5-10 minutes.

I kept writing them after I left. Here is why, and how.

What it is

End of day (EOD) is a short daily update to your team. End of week (EOW) is the Friday summary. Both follow the same rule: answer first, explain later.

The EOD answers three questions: what moved, what is stuck, what happens tomorrow. The EOW answers one: what was the net result of this week and why does it matter for next week?

A real EOD looks like this:

End of Day — 19.06.2026 (Friday)

Auth module hit 90% — on track for next week’s review.

Auth Module — 90% Complete

  • Finalized the remaining endpoints — unblocks the frontend team
  • Intermittent test failure identified — team investigating, not blocking

Blockers

  • Staging DB access still pending — @devops: can we get this opened by Monday? Gates end-to-end testing.

Next Steps

  • @alice: finish the login flow
  • @bob: root cause the test failure

35 lines. Five minutes to write. Anyone who reads it knows exactly where things stand.

The format

I follow the Pyramid Principle for both. Lead with the answer. Then the reasons. Then the details.

EOD:

  1. Executive summary — one sentence: are we on track?
  2. Sections — one per workstream. The title is the conclusion, not the topic.
  3. Blockers — what is blocked and who needs to act. Omitted if none.
  4. Next Steps — 2-3 things for tomorrow, each with a named owner.

EOW:

  1. Governing conclusion — the verdict on the week, not an activity list.
  2. Three clusters — each with a conclusion title and 2-4 supporting bullets.
  3. Next Week — what this sets up, named owners, open items.

Why it works

First, it is for you as much as them. That surprised me. Writing the update forces me to reflect: what did I actually achieve today? What will I do tomorrow? Do I have blockers I need to escalate? Without the discipline of writing it down, those questions go unanswered.

There is another benefit I did not expect: going through the previous EODs gives me confidence that I did not forget anything. And yes — I often find a few items I dropped or forgot to update. But I catch them before my manager or the client does. That alone is worth the 10 minutes.

Second, it builds trust. A consistent update every day removes the need for status check-ins. People stop wondering if things are on track. They know you will flag problems.

Third, it surfaces blockers fast. Writing “Blocked on X, waiting on Y” every day makes it obvious when something has been stuck for three days.

The audience trap

Most people send status updates to their manager. That is fine, but your manager is not the primary audience.

Your teammates are. They are the ones who need to know what you are doing and where you are stuck. Sending the update to the team instead of just your manager changes the dynamic. You are not reporting up. You are sharing sideways.

I have also found that sharing progress beyond just PRs — in your own words — builds a reputation that you have things under control. The small stuff adds up.

“I don’t have time for this”

I hear this. It takes 5-10 minutes. If you cannot spare 10 minutes at the end of your day, the problem is not this email.

What helped me: I block 15 minutes on my calendar every day at 5pm. Not optional. When the reminder pops, I write the EOD. The calendar block is what made it stick — without it I would forget half the time. And honestly it still happens that I get caught up in something and miss it. But that is fine. The next day I just write both.

Start with the EOW only if the daily feels like too much. Once a week, two headings: achievements and priorities. Three to five bullets each. That is it. If that feels doable, add the EOD later.

The skill I use

I automated the structure with an opencode skill (Claude/GPT templates work too). It reads the previous EOD, cross-checks open items against what I worked on today, and formats the message. The full template is in skill.txt — it works as a standalone reference even without the AI. You can copy the structure into a notes app, a text expander, or just memorize it.

Resources