Discover: Τhe Foundation for 58:Hours Sprints
Why the real work begins days before the sprint actually starts
From the outside, 58:hours – our proprietary three-day sprint – could pass for just another workshop. It’s anything but.
Most people think it begins on Day 1: the right people arrive, Post-its hit the wall, the clock starts ticking. But what most teams never see is that the most successful sprints don’t start in the room. They start weeks earlier.
Teams that deliver breakthrough work during a sprint aren’t trying to define the problem under pressure. That heavy lifting happens in a pre-work stage we call Discover that forces the organisation to be honest.
Its job is simple but unforgiving: understand the real problem, align on success, identify who needs to be involved, and set the purpose with absolute clarity. Discover allows room to actually solve the problem during those 58 hours.
Get it wrong, and you spend three days running in circles.
Get it right, and the sprint becomes a launchpad.
These are three Discover techniques we use to expose misalignment before it becomes a (really expensive) problem:
1. We have a problem-framing session
The heartbeat of Discover is a problem-framing session with every key stakeholder in the room. This is often the first time people realise they’ve been working on completely different problems.
The session itself is virtual, never longer than two hours, and can take three different forms depending on where the challenge sits:
For big, complex challenges with multiple layers
When different stakeholders have fundamentally different perspectives, we run a comprehensive 90–120 minute session. Everyone shares their view using structured frameworks (the 5Ws: who, what, where, when, why). We clarify the business need, explore who’s affected, synthesise themes through clustering and dot-voting, then co-create a problem statement everyone can stand behind.
For early-stage alignment when time is tight
When the challenge is still vague and needs quick scoping, we run a lightning session in 60–75 minutes. Silent brainstorming ensures balanced input, and everyone writes individually before we cluster and vote. No open debates. It’s a structured progression from scattered concerns to a single, reframed problem statement.
For operational challenges where causes are hidden
When the problem exists but no one understands why, we run a root cause and stakeholder analysis over 75–90 minutes. We map who’s involved, dig through iterative “5 Whys” questioning, trace the impact ladder, and combine everything into a statement that reflects both causes and stakeholders.
What surfaces across all three formats:
The assumptions everyone’s been carrying but never voiced
The symptoms teams have mistaken for root causes
The political and emotional weight behind each version of the story
The contradictions quietly sabotaging every decision.
2) We form a basic assumption during a Day Zero Solution
Before we interview a single stakeholder or analyse a single dataset, we run a Day Zero Solution: an internal session (ideally in person) that can last from a couple of hours up to a full day. It revolves around asking one provocative question: If we had to solve this tomorrow with what we know right now, what would we build?
Why this feels counterintuitive (and why it works): Most discovery processes start from zero and slowly build toward an answer. A Day Zero Solution flips the script. It gives teams permission to be wrong early, which is exactly how you get to right faster. By sketching a solution early, we force ourselves to surface the blind spots, the disagreements, and the assumptions that usually slow teams down. We get misalignment out of the way before the sprint even starts.
A Day Zero Solution also gives us an early read on the strategic tensions we will need to navigate once the sprint begins. When you try to design a defensible direction with incomplete information, you expose the trade-offs that matter. You see where the market pulls one way and the organisation pulls another. You understand whether the challenge ahead is about capability, clarity, or internal alignment.
3) We maximise the tools at hand
In our earlier piece, we talked a lot about the power of our expert network inside the sprint room: specialists dropping in at the right moment to elevate the work.
What we did not talk about is how we also lean on that same network during our discovery. We involve them early to challenge assumptions, spot blind spots, and help us see around corners. Their input, even in 30-minute doses, changes the questions we ask and the data we go after.
Alongside these experts, there’s a broader toolkit we dial up or down depending on the project:
Stakeholder interviews to reveal the tensions, incentives, and fears that shape how problems actually behave inside organisations. This uncovers where the organisational chart is blocking execution, where competing KPIs are creating internal friction, and where “resistance to change” is actually rational self-preservation because the incentive structure hasn’t changed. These insights determine whether a solution will be adopted or quietly sabotaged.
Listening sessions are semi-structured group conversations that show how teams talk about the challenge when hierarchy isn’t watching. They reveal the gap between what people say in formal meetings and what they believe in hallway conversations, often indicating where strategy is quietly dying.
Shadowing and on-site visits strip away assumptions. You see whether approved processes actually work in practice. Most organisations have massive amounts of workaround behaviour: good people compensating for broken systems that leadership doesn’t know are broken, revealing where the real problems live.
We use AI as the project’s living memory. It processes strategy decks, interviews, market reports, transcripts, consumer research and competitor activity in minutes, finding the patterns humans miss when they are too close to the work.
Synthetic personas are where things get interesting. Instead of waiting months for new research, we generate data-backed personas built from the organisation’s own materials: behavioural patterns, customer feedback, market signals, cultural shifts. They are grounded projections that allow teams to explore:
• How different stakeholders or customers might react to a solution
• What invisible needs or frustrations could shape adoption
• Where the opportunity space is wider (or narrower) than expected
• Which motivations are consistent across markets and which are not
Data and journey analysis reveal where the problem appears in real processes and customer interactions. Once mapped, patterns become impossible to ignore.
Pulses and surveys supply signals across teams or markets to quantify sentiment and expose emotional misalignment. They reveal whether people actually believe in the direction. Whether customers feel what the organisation thinks they feel. Whether the problem being solved is the problem people would pay to have solved. Sentiment is strategy. If people don’t believe, execution crumbles.
We rarely use everything at once and instead choose the right mix for the given problem. The goal is to reach a grounded, aligned point of view in 2–3 weeks, not to produce a research binder that no one reads.
What comes next
In the coming piece, we’ll move through the five Ds during the actual sprint: how we work with teams to Download what they know, Define the right questions, Dream up possibilities, Decide on direction, and Deliver a working prototype – all within 58 hours.
We’ll then explore Deploy, where we close the sprint properly through reflecting on what happened, capturing what was learned, and planning what happens next.
Meanwhile, for those who prefer a visual deep-dive, check out the 58 Micro-mentary Series: short episodes where our Co-Founder and Managing Partner Giorgos Vareloglou shares how this methodology actually came together.
Stay tuned.
Love this! Thanks for sharing the details!🍀