Stakeholder discovery
Discuss the business goals, audiences, internal publishing needs, and approval responsibilities.
Resolve the website brief before committing to the build.
Norml runs website discovery to define priorities, content needs, platform constraints, and responsibilities before design and development begin.
Book a callA project can be ready for discovery before it is ready for design.
Your team knows the website needs work but has not agreed the scope.
Several stakeholders need different things from the same website.
Integrations or content migration could affect the build.
You need a documented brief to compare implementation options.
What our website discovery services include.
Discovery combines stakeholder sessions with a review of the current website and available evidence. We identify decisions, dependencies, and unresolved questions, then prepare a brief that can guide the delivery team.
Website review
Inspect representative pages, content, navigation, available analytics, and key conversion paths.
Technical constraints
Review the CMS, hosting, connected systems, data ownership, and likely migration requirements.
Scope definition
Describe the proposed page set, functional requirements, exclusions, dependencies, and acceptance criteria.
Website discovery deliverables.
The agreed scope identifies which of these deliverables your project needs.
- 01
A discovery findings document.
- 02
A prioritized requirements list.
- 03
A proposed page and content inventory.
- 04
A record of technical dependencies.
- 05
A delivery brief with open decisions.
Our process
How our website discovery process works.
Gather existing material
Review the website, analytics access, product material, and known requirements.
[ 01 ]
Explore the requirements
Discuss user needs and operational constraints with the relevant stakeholders.
[ 02 ]
Define the project
Document the recommended scope and distinguish requirements from optional additions.
[ 03 ]
Prepare the handover
Review decisions together and identify what the next phase needs to start.
[ 04 ]Website discovery questions.
Can discovery be a standalone engagement?
Yes. The brief can guide a later project with Norml or another delivery team.
Does discovery include a finished design?
It defines the requirements and direction. Detailed page design is a separate stage.
What if we already have a detailed brief?
We can review that brief, focus on unresolved dependencies, and avoid repeating completed research.
Will you quote the build during discovery?
The resulting scope supports a separate implementation estimate. Discovery itself does not establish an approved build price or delivery date.
See how this work fits into our website strategy service.