Discovery & Strategy
Build the right thing before you build the thing right
The most expensive mistake in digital is building something nobody wants. Discovery is how we make sure that never happens to you — research, workshops and a strategy you can act on, with or without us.
What you get
- Stakeholder workshops — get everyone's version of the goal on the table, then align on one.
- User research & interviews — evidence about what your users actually need.
- Competitor & market analysis — know the landscape before you enter it.
- Product roadmap — a prioritised, phased plan — MVP first, gold-plating later.
- Scope & estimate — a clear picture of cost and timeline before you commit.
- Prototype validation — test the riskiest assumptions cheaply, before the build.
Research-grade rigour
We've run discovery alongside Monash University researchers — the same evidence-first approach goes into every project, whatever the size.
A plan you own
Everything we produce is yours. Take the roadmap and build with us, or take it anywhere else — it's designed to stand on its own.
Do you need it?
Do you need discovery first?
Not every project does. If you already know your users, your goal and your version one, a long discovery phase is money better spent on design. If you don't, building first means betting the budget on guesses. Answer five questions for an honest first read.
The discovery check
- Mostly yes: you may be ready to move into design.
- A couple of gaps: a short discovery sprint would pay off.
- Mostly unknowns, or high stakes: start with discovery.
How discovery works
Good discovery goes wide before it goes narrow, twice. First you open up the problem: who has it, how they cope today, what the business needs. Then you narrow down to the one problem worth solving. Then you open up again with ideas and prototypes, and narrow down to what gets built. Designers call this the Double Diamond. On TeaTime, our aged-care project, we ran it in full.
The Double Diamond, as we ran it on TeaTime
- 1. DiscoverUser research in real care centres.
- 2. DefineResearch turned into insights. It found three distinct users: administrators, care staff and families.
- 3. DevelopIdeas and prototypes. One interface couldn't serve all three well, so TeaTime became three connected apps.
- 4. DeliverBuild and launch on the App Store and Google Play.
That "three apps, not one" decision came straight out of discovery, and it's the kind of call that's cheap to make on paper and very expensive to make after launch. The results:
TeaTime's usability score on the System Usability Scale (SUS)
more family members converting
care-centre engagement
From what users said to what we built
Discovery isn't a report that sits in a drawer. On Hydration Hero, every pain point from our user interviews turned into a feature.
Hydration Hero: insight to feature
| What users told us | What we built |
|---|---|
| Current apps lack personalisation | An avatar users personalise themselves |
| Tracking methods are boring | Interactive, fun drink logging |
| Other apps don't allow customised drinks | Custom drinks, and how they make you feel |
| Incentives help build a habit | Streaks and rewarding badges |
| It's easier when others are involved | Challenges with friends |
Discovery in our other work
- SleepSync: with Monash University and Sleep Health Systems, the project began with a full research phase into shift workers' real schedules, constraints and habits before a single screen was designed. The research deck covers the audience, the evidence base and the design direction.
- bFocused: competitor research, user interviews, surveys and personas, then a prioritisation matrix to decide which features a beta needed, because time to launch was limited.
Questions people ask us
What is a discovery sprint?
It's a focused burst of research, workshops and quick prototype testing aimed at your riskiest assumptions. The goal is a clear, prioritised plan, so you know what to build first before you commit to a full build.
Do I own what you produce?
Yes. Everything we produce is yours. Take the roadmap and build with us, or take it anywhere else. It's designed to stand on its own.
Could discovery tell me not to build it?
It could, and that's part of its value. If your idea has a problem, you'll hear it from us early, with a suggestion for what to do instead.
I already have designs. Do I still need discovery?
Not always. If the designs are based on real user research and a clear goal, you may only need a quick check of the riskiest assumptions. If they're based on guesses, testing them with users first is far cheaper than building them.
Read next
Got an idea that needs pressure-testing?
A discovery sprint is the cheapest insurance you can buy for a digital product. Let's talk it through.
Start a project →