Every product needs a test it can fail. Ours is a run club.
A run club, meaning one slightly overcommitted person who organises Sunday runs for thirty people, does the admin on their phone during lunch, and has never once thought of themselves as someone who ships software. If an app for your club is something that person can make and keep, the product works.
The test is simple. Can that person, on a Tuesday lunch break, end up with a real app on their club’s phones before Sunday’s run? A proper app with an icon, one that opens to this week’s run and a button that says they’re coming.
Why the bar is that high
Because the alternative tools all fail the same person. The group chat buries the plan. The shared spreadsheet is nobody’s favourite app. The web page builder produces a page, and a page does not sit on a home screen or tap someone on the shoulder when the meeting point changes.
A club lives on its members’ phones. So the bar is a phone bar.
What passing looks like
Tuesday, 1:04pm: they claim the community template, name it after the club, pick a colour to match the vests. 1:07pm: the app is alive and they are signed into it in the browser. 1:10pm: it is installing on their own Android phone from a link. That evening the link goes in the chat with “humour me”, and phones around the city start growing a new icon.
Sunday morning, someone posts that the meeting point moved to the other car park, and it lands inside everyone’s app, live. Attendance stops being archaeology.
The parts we sweat so they never see them
Under that little story there is a database being minted in about a minute, an install link that always serves the newest build, sign-in that just works, and live updates arriving in the app while it is open. The captain never learns any of those words, which is the entire job. Complexity they can feel is complexity we failed to hide.
If you run a club of any kind, the test is yours to run too. It is free, and Sunday is coming either way.