Too Risky to Skip Discovery

You'd think by now we'd have evolved past the "Hey, let's get a dev team and build [insert vague product idea here]" strategy. Sounds so 2010, doesn't it? Yet, here we are, occasionally slipping into old habits.?

Why do we do it? Probably because there's something irresistible about diving headfirst into a new project. It's thrilling, it's adventurous, and it has the power to drive a team's curiosity and motivation.??

And it is dangerous.?

Skipping the Discovery Phase can lead to misaligned goals, wasted resources, and, frankly, solutions in search of problems rather than the other way around.

(Note! If you don’t have time for everything we have to say about Discovery Phase, scroll down for a checklist.)

What is the Discovery Phase in Layman's Terms?

Discovery Phase is a reality check — the first step to making sure the project hits the mark and delivers real value.

It's about asking the tough questions: What exactly are we making? Who's it for? What problems are we solving? And importantly, what could go wrong?

The process requires talking to everyone involved, from the execs to the end-users, and looking at what the market's doing.?

Why Consider an External Team for Discovery?

You don’t have to outsource the Discovery Phase. But it might be a smart move.

Think of it like this: some people argue against therapy, saying they can just ask themselves "how does this make me feel?" and save a bundle. But a good therapist is paid to spot patterns and ask the hard questions you'd likely avoid.?

We all have blind spots.?

It's similar when we're evaluating a project's potential.?

Being deeply invested, both morally and financially, makes you and your in-house team prone to bias. It's human nature to overlook problems when you're too close to the situation.?

External teams come without those blinders. They can see the red flags you might miss and provide a clear, unbiased assessment of whether the project is really worth pursuing.

Do you have to stick with the same team for the entire project later? Absolutely not.?

Here is what our Delivery Director Bruce Mason says about it:

“Discovery phase is not a commitment to a delivery phase. There is nothing wrong with choosing different companies for Discovery and Delivery. The only wrong move is to skip Discovery altogether”?

Let’s see how this phase of your project works and who makes it work.

Key Artifacts & Roles: The Discovery Phase Essentials

Project brief. The what, why, and how of our project: objectives, scope, and key deliverables. Involved: Project Managers and Lead Developers.

Stakeholder analysis. Who has a stake in the project? This helps us understand everyone's expectations and concerns. Involved: Business Analyst, User Experience Researcher, and Product Owner.

Market analysis. What’s out there? It shows how your idea stacks up against the competition. Involved: Marketing Specialists.

Risk assessment. What are the potential roadblocks and hiccups? Think of it as your project's insurance policy. Involved: Business analyst, Tech Lead

Requirement specification. A detailed list of project requirements, including functional, non-functional, and technical specifications. Involved: Tech Leads Business Analyst

Resource plan. An overview of the resources needed for the project, including personnel, technology, and budget. Involved: Everyone working on the project pitches in.?

Timeline outline. What is the rough sketch of the “when?” It's not set in stone, but it gives you a ballpark for planning. Involved: Project Manager, Business Analyst.

Do you really need ALL of these people? Would be nice, but not necessarily.?

Real-world Discovery Phase projects are normally more economical in staff than this. However, the skill sets of hired experts should be rather diverse.?

The same principle applies for other phases to come. You need a smart balance.??

“In the outsourcing-based model, the SMEs and the product owner will likely be on the client’s side. The product owner will, on behalf of the client, define priorities and values and state what the product needs.?

However, if the product is domain-based, the outsourcing team can provide product guidance based on regulatory requirements and the current situation.”

Bruce Mason

Timing of the Discovery Phase: The Honest Breakdown

On average, we're looking at 2 to 6 weeks. The duration hinges on the project's complexity and scale.

For a straightforward project, expect closer to 2 weeks. This covers the essentials: defining the scope, stakeholder interviews, and initial risk assessment.?

For more intricate projects, especially those breaking new ground or with multiple stakeholders, it can stretch to 6 weeks. This extra time allows for deeper market analysis, comprehensive risk evaluation, and more detailed planning.

Bottom line: It's a short-term investment for long-term clarity. We're not wasting time; we're saving it down the road along with your budget.

The Discovery Phase Checklist

Use this snapshot checklist before kicking off delivery to confirm all Discovery Phase bases covered.?

Alignment

? Stakeholders share common understanding of issues

? Priorities & key requirements agreed by all

? Measures of success defined for qualitative goals

Knowledge

? Background research done thoroughly

? Competitive positioning gaps confirmed

? Target users & their needs deeply understood

Requirements

? All business, data & functionality needs detailed

? Technical complexity & limitations discovered

? Infrastructure & integration abilities mapped

Solution Scoping

? Multiple approaches researched

? Highest potential option modeled

? Envisioned architecture validated as feasible

Estimations

? Effort calculated via prototyping or comparable data ? Staffing requirements and timeline approximated

? Essential risks flagged? & mitigation options outlined

Approvals

? Proposed roadmap satisfies objectives

? Top stakeholders confirm solution worthwhile

? Official go-ahead obtained to commence build phase

All checks green? You're cleared for a good Build phase start.

Got some yellow flags? Revisit Discovery analysis in those areas.

See any red flags? Pause until big gaps are addressed.

The key is fixing the major issues before moving forward.

The discovery phase is essential, but rarely one-size-fits-all. What does an ideal process look like for YOUR product goals??

If you're gearing up for your next project, we invite you to a brief, no-strings-attached consultation to map out the timeline and milestones.?

Author: Bruce Mason        

Delivery Director in QArea         

Explore the latest in tech on our blog for more insights: https://qarea.com/blog