Two years ago our team ran on adrenaline. Monday planning bled into Tuesday, standups stretched to forty minutes, and every Friday someone spent two hours writing a status update nobody read. We were shipping, but we were exhausted.
This guide is the system we built to get out of that storm. It is simple on purpose: three waves every week, protected focus time, and one honest review on Friday.
Wave one: commit
Monday morning is for choosing, not doing. Each person commits to two or three outcomes for the week. Outcomes, not tasks: "customers can export invoices" instead of "work on export".
- Keep commitments small enough to finish by Thursday.
- Check capacity before you commit. Time off and on call duty count.
- Write the outcome so someone outside the team understands it.
Wave two: build
Tuesday through Thursday belong to deep work. We protect two Focus Tides a day, each about ninety minutes, and we treat them like meetings with our most important customer.
Focus time is not a perk. It is the production line of a product team.
During a Focus Tide, chat goes quiet and calendars show the block as busy. If something is truly urgent, people call. In two years, almost nothing has been truly urgent.
A tiny automation that helps
// Mawimbi rule: pause notifications during focus
when focus.started:
slack.status = "In a Focus Tide"
slack.snooze(minutes = focus.length)Wave three: reflect
Friday afternoon is for looking back. A short Tide Review answers four questions: what shipped, what slipped, what we learned, and how we feel. It takes ten minutes to write and two minutes to read.
- Celebrate one win per person, out loud.
- Name blockers without blame.
- Carry over unfinished outcomes on purpose, not by default.
- Seed next week with one sentence each.
Start this week
You do not need new software to try this. A shared doc with three headings works fine for the first month. When it starts to creak, that is when a tool like Mawimbi earns its place.