Make uncertainty visible
A request for a new website often combines several needs: unclear content, slow processes, product information that is difficult to manage, or missing connections to older systems. The first task is to separate these problems. This makes it clear which needs a visual redesign can address and where a process or software change is required.
Base decisions on evidence
We assess existing content, user questions and available usage data together. Where evidence is missing, we record an assumption to investigate through an interview, a sample task or a small prototype. Each item in the priority list should state its purpose, who it serves and how it will be assessed.
Preparing for discovery
- Share your current website and the three main things you want to change.
- Identify who needs to contribute to decisions from content, sales, operations and technology.
- Explain fixed dates, existing systems and known constraints.
The structure defined during discovery informs our UX/UI design and technical architecture decisions. We can discuss the initial scope together.