Most clubs jump to solutions before they understand the challenge. This one-pager is the thinking behind our Problem-Framing Engine: frame it, map where you are, then pick the method that actually fits.
Decide what kind of challenge this is. Clear, complicated, complex, or chaotic — each calls for a completely different response from your club.
Locate yourself: Discover, Define, Develop, or Deliver. Are you still in the problem space with fans, or the solution space with your team?
Pick one method that fits the frame and stage — then commit to one concrete next step, not five competing priorities.
Clubs often build apps fans don't open. JTBD asks: what progress are supporters actually trying to make? Build for that job, not the one you assumed.
Write the press release for the finished solution before building anything — it forces agreement on who benefits and how. Surface board disagreement now, on paper, where it's cheap.
Empathise, define, ideate, prototype, test — for problems where you don't yet understand what fans truly need. Reframe before you try to solve.
Most sports technology projects fail not because the team built badly — but because they built the wrong thing. Lean finds that out in weeks, not after a six-figure build.
A 3–5 day sprint to map, sketch, decide, prototype, and test with real supporters — fast. Best when you need evidence before a budget decision.
Technology bolted onto a badly framed problem is expensive noise — especially in sport, where budgets are tight and trust from fans is hard to rebuild.
A Data Vanguards diagnostic ranks your opportunities and names the first thing worth building — in one focused session.