TMI Community // Build in public

Show your work: a calmer way to run a tiny SaaS

I replaced five dashboards with one weekly operating note. Here is the format, the signals it tracks, and the quiet decisions that made the biggest difference to a small distributed team.

OF

Omar Farooq

Indie maker

Jan 29, 2026//6 min read

For most of last year, our team had more dashboards than decisions. Every metric was technically useful, but the volume made it hard to see what deserved attention now and what could wait until next week.

We replaced the collection with a single operating note: three customer signals, one reliability signal, one commercial question, and a short list of decisions. The note is written every Friday and read before Monday planning.

The most valuable change was not the format itself. It was the permission to leave numbers unexplained until we had enough context to act. Calm operations are not passive; they are selective.

“A smaller surface for attention creates a larger surface for good work.”

Discussion (16 Replies)

SA

Sara Ahmed

Design Technologist

Apr 02, 2026

The idea of making the review ritual small enough to repeat is the part I am taking away. Security guidance is only useful when it survives a busy development sprint.

LM

Leo Martins

Cloud Architect

Apr 03, 2026

Would love to see the threat-model template you used. We have been trying to keep it close to the pull request without making the PR unreadable.

AK

Ayesha Khan

Product Engineer

Apr 04, 2026

The key is to record the architectural decision and the residual risk clearly, rather than producing a 30-page static specification.