Does Discovery Really Matter?
Post Statistics
This post has 1313 words.
This post has 8459 characters.
This post will take about 6 minute(s) to read.
Does the discovery process really add value to any project or endeavor? Every project has a 50/50 chance of success or failure. Truth is most projects will fail for one of several reasons around engagement and people’s interpretation of the purpose of the change proposal which is being delivered through the project. People engagement in any project comes before processes and technologies.
Discovery usually serves as a phase for helping ‘everyone” involved in the project to start on one page. Getting this in place is the most important aspect of any successful project. It is a vital part of an initiation phase of any worthwhile project and it is very important to a successful delivery.
What is a Project Anyway?
There are several definitions of what a project is, keeping it simple, let’s use this common and simple definition.
A project is defined as an individual or collaborative enterprise that is carefully planned to achieve a particular aim.
and
It’s a temporary endeavor undertaken to create a unique product, service or result – PMI
A good project must be well planned, be collaborative (somewhat) and must achieve at least one particular aim. Another reality is that we have projects every day. You go to work, some attend University or school, we get married, we have kids, we plan for our kid’s future, we get new jobs and attend interviews. All this could be considered projects. Basically, we are all project managers in so many capacities.
Would you ever embark on a project without counting the cost, planning for change and engagement, assessing the resources it would impact and take to achieve good results? Nope!!
The usual project life cycle starts with project initiation as the first step of any successful project. I somewhat disagree with that because one cannot initiate something that has not been discovered or known confidently.
Project discovery is a process of gathering information about a project to help people involved understand its vision, goals, and scope.
The discovery phase of any project is the most important aspect of any change initiative. Without input from the end user, most projects will deliver change that is not a reflection of the solutions that will benefit the stakeholders in the project.

A ‘Discovery Phase‘ is defined somewhat as an intensive research period that is undertaken at the very start of a digital project, often by a mixture of people such as Business Analysts, User Researchers, UX Designers, Architects, and a host of others.
Throughout the Discovery phase, the discovery team seeks to understand from the stakeholders
- What the business wants to achieve (desired state)
- What exists today, in terms of systems, culture, behaviors, pain points, tools, processes (current state)
- What we need to know, do, change, compare and understand to get the organization to the desired state (gaps)
The Discovery process is used to align all stakeholders on the vision for the process and what an ideal end state looks like.
As the cross functionally skilled team move through the Discovery phase, some documentation is produced to capture all the key findings along with any follow-up actions that need to be further explored/answered.
Such documentation which is usually a business case document typically provides answers to key questions such as:
- Who is involved in the current project? And what are their roles / responsibilities?
- What are the business processes and organizational design?
- What are the potential risks identified and what are their impacts?
- What is the project vision and objectives?
- What requirements are we looking to deliver against as prioritized?
- Who are the other external stakeholders and what is their role/responsibilities?
Documenting these findings helps to align all project stakeholders both within the client and agency around what the scope of the project is and what the desired end goal looks like.
Great Discovery Reduces Uncertainty by 99.99999%.
Efficient Discovery helps us see a broad view of possibilities and gaps
Focussed Discovery helps us prepare for opportunities
Proactive Discovery enables making accurate decisions based on evidence rather than assumptions,
Enhances better scope definition and goals of the project and thus get a more precise estimate,
It ensures a high return on investment in the development,
Discovery creates a user-centered experience and helps eliminate the need for making costly changes on advanced development stages,
We can gain a better development/acquisition insight thanks to consultation with cross-functional experts on the project.
Key possibilities exposed by the discovery phase listed here are:
- Discovery phases help to provide purpose and direction to the project team and align all members around a shared vision. Not only that, they also help to highlight any potential roadblocks and risks that could hit and impact the project in the life of the project
- Discovery phase helps the team understand the best fit strategy to suit the present architecture or where a new one is being implemented, show how the parts all fit together to provide a customer-centered product
Waterfall methodology, Agile Framework or a Bit of both
It doesn’t matter what delivery path you follow, the discovery phase is still needed to create visibility on the path to success. While the Waterfall Methodology works for some projects, the Agile Framework delivers more impacting results while reducing risk. Truth is that most delivery styles incorporate a mixed methodology of Waterfall and Agile. A Discovery phase can be integrated into both Waterfall and Agile Discovery process can be easily incorporated into both waterfall and agile themed projects
In Waterfall projects, the Discovery Phase happens at the very start of the project and can typically run for 2 weeks and upwards depending on the size of the project, the number of interdependent systems and the areas/stakeholders/users which need to be explored.
In Agile projects, the Discovery Phase is continuously implemented in an MVP fashion reflecting the release plan/product vision. It is usually shorter than the Waterfall methodology, more impacting, relevant, and usually continuous to the end of the project.
Now What?
Whatever project you are running, managing or thinking of implementing, you need to understand completely if possible 1000% what the needs and goals of your project are. I run a small website design business and never start until my client fills a website design template. I ask them all sorts of ridiculous and nice to have questions to understand as fully as possible what the immediate and future goals of the project website are. Looking back I understand why I had failed in some past website design projects where the discovery of the intention of my client is.
Please do not underestimate the power of a discovery phase in every project. It is very important and vital to the success of any successful project
About Me
Digital (Agile) Business Analyst / Agile Delivery Consultant & Mentor
Delivering digital transformations/ Building agile teams / software / WebServices / Cloud Native SAAS applications / Data Migration and Test Managment Strategy
Presently a resident of London with a knack for learning, collaboration and working with happy team members to deliver value. I am an agile enthusiast who believes in continuous learning and growing!!
“Transformation, People Building and Education of leadership’
Over the years I have been engaged in enterprise transformation projects usually with multiple workstreams, (robotic) process automation to improve customer engagement, enabling teams via agile delivery strategies (product ownership and scrum master roles). I have helped and enabled delivery teams to understand the need for a product vision and understanding of the release plan to enable incremental value addition to the customer journey and service design across financial services, private business, and the public sector. Get in touch if you need my services