Customer self-study

How we use How We Win, on our own team

We don\u2019t have fifty case studies yet. We have one. But it is us \u2014 the people building the product \u2014 running it on our own week every week. Here is the honest version of what that looks like.

1

team running the product

3

touchpoints per week

10 min

average Monday plan

100%

Friday reviews closed out

The setup

We are a small team of builders. We run one weekly plan, one mid-week check, and one Friday review. All three touchpoints happen in How We Win, because of course they do \u2014 it would be odd to ship the product and then run the team in a Google Doc.

The real test of this product was when we stopped maintaining two parallel systems \u2014 a Notion doc for \u201cour real work\u201d and How We Win for \u201cdogfooding.\u201d Once we consolidated, we felt every sharp edge in the product within a week.

\u2014 Enrique, founder

What the week looks like

Monday plan

Fifteen minutes. The team focus for the week is written as one sentence. Two or three team goals serve it. Tasks get claimed. The plan is done when everyone has a clear answer to "what am I doing this week and why."

Wednesday check-in

Async. Each of us updates our tasks and goals: moved, stuck, or done. If something is stuck, we say what would unstick it. I read the page in five minutes and unblock on the spot.

Friday review

Async, then closed out live. Each person fills the three-line review template (shipped, didn\u2019t, roll to next week). I write the team wrap-up paragraph. That paragraph is what Monday starts from.

What we have learned running our own product

Three things, in order of how much they surprised me:

  1. Rollover being automatic is the single most important feature. The moment it stopped being manual, the rhythm stopped slipping. This is the thing that kills Notion standup templates at ten people.
  2. Weekly focus as a sentence beats weekly focus as a theme. "This week is about signup reliability" beats "Reliability sprint week." Specific beats thematic.
  3. The team wrap-up paragraph is for the team lead, not the team. Writing it forces you to synthesise. Most weeks that synthesis is the most useful thing I do as a founder.

What we would change

Two things we know about from the inside:

  • Monday plans get written too late on busy weeks. We are exploring a soft nudge on Sunday evening to the team lead only.
  • Wednesday check-ins are still text-heavy. A one-click status (on track / moved / stuck) is on the roadmap.

This page is kept honest. Whenever we ship something because we felt its absence ourselves, it shows up here.

Run the same rhythm with your team

Set up in under ten minutes. Free to start, no credit card required.