Why this project exists
It began with a simple observation in South London: people wanted to move outdoors, yet most advice was either too intense or too vague. We started documenting small, repeatable practices that fit ordinary city schedules.
Three decisions that shaped our approach
- We removed performance-first language and focused on consistency.
- We replaced rigid templates with adaptable route notes.
- We treat weather and public-space constraints as design inputs, not disruptions.
How decisions are made
Weekly review calls include route leaders, a scheduling coordinator, and one participant representative. Changes are accepted only when they genuinely simplify use for newcomers.
Inputs we use
- Route accessibility notes
- Participant time windows
- Surface and weather constraints
Inputs we avoid
- Trend-based pressure metrics
- Competitive ranking systems
- Unverifiable wellness promises
What we learned from winter sessions
Attendance drops when sessions start too early. We now publish two time options and a contingency note by 08:00.
How we communicate limits
Every programme note includes what it does not cover. That prevents misunderstanding and sets realistic expectations from the outset.
Working style
We prefer plain language over slogans. If a line sounds like advertising copy, it does not stay on the page.
Local notes from participants
“I can fit this around my commute, which is why I kept at it.”
“No one tried to upsell me; they simply explained options.”