The Workshop
A method helps us make better decisions. Understanding, strategy, building and refinement give the project a shared direction without turning it into a rigid chain of steps.
Get to know your business, your audience and what a useful outcome looks like.
Bring the priorities into focus and give the content a clear, practical structure.
Turn that direction into thoughtful design and a website made to fit.
See how the work is used and keep improving the things that matter.
The Workshop
What problem should the website solve? For whom? What content exists and what decisions are already made? These questions shape the brief.
Reviews compare the work with the goals. Collected feedback and clear priorities help avoid changes of direction that have not been discussed.
Handover does not end our understanding of the project. Real use, available data and new needs can define the next improvements.
Before we begin
Answers about The Workshop and the decisions around it.
Because structure and design should respond to a real problem. Understanding the business, audience and priorities avoids starting with visuals disconnected from purpose.
Goals, audience, content, constraints and approval criteria. Missing materials and open decisions should also be visible.
The four phases are a framework, not a rigid sequence. An SEO review and a new ecommerce site need different activities while sharing understanding and priorities.
The timing is agreed in the project schedule. Before layouts are proposed, the materials and decisions needed to make them meaningful are clarified.
It helps to collect comments in one shared place and connect them with goals and pages. Approval responsibility and included revisions should be defined first.
A change can be discussed with its effect on work, cost and schedule. Refinement should be distinguished from a change in scope.
Dependencies should be explicit in the schedule. A phase can be reorganised, but handover also depends on necessary materials and approvals.
By comparing usefulness, observed problems, resources and dependencies. Priority does not necessarily mean the most visible change or the longest list.
Checks are defined for the project: content, navigation, functionality and device behaviour. Completed checks and any remaining ones should be clear.
Start with real use and available data, connecting changes with a problem or opportunity. The next phase needs a dedicated agreement.
Bring the idea, the question, or the part that isn’t quite working. Let’s find a thoughtful way forward.
