The success or failure of a digital project depends more on the process than on the design itself. It starts with a well-defined brief and an honest plan. The right questions are asked early on. By the time the project moves into the build phase, the critical thinking has already been completed.
That is the thinking behind our web design process, refined over 25+ years running digital projects for Queensland businesses, government and enterprise. This post walks through our six stages and explains why each one exists.
Why Process Matters More Than People Admit
You have probably worked with an agency that talked a good game and then disappeared into a black box for six weeks. Vague updates. Surprise invoices. A reveal that misses the mark. Process is what stops that from happening.
Our process is not a sales tool. It is a working document we use on every project, refined over hundreds of jobs, with real outputs at every stage that the client signs off on. That discipline is what protects budgets, timelines and outcomes.
It also protects the relationship. When everyone knows what comes next and what is expected of them, the work stays calm. Questions get asked early. Decisions get made by the right people. Nothing has to be unpicked at the end.
What Is the Mettro Web Design Process?
The Mettro web design process is a six-stage workflow that takes a digital project from initial conversation through to long-term support. It works by defining clear outputs at every stage, with sign-off required before progressing, so there is no ambiguity about where the project is at any moment.
The six stages are Brief and Brainstorm, Analyse and Plan, Design and Development, User Acceptance Testing, Go-live and Delivery, and Monitor and Maintain. Each one has a specific job to do.
Stage One: Brief and Brainstorm
Your project starts with a proper conversation. Not a sales pitch, not a discovery call dressed up as a workshop. A real session where we get into the details of your business, your goals, your customers and the systems you already have running.
The output of this stage is a project brief that includes goals, KPIs, key stakeholders, milestones and timeframe, and a clear set of next-step recommendations. By the end of it, both sides know what the project actually is and what success looks like.
What we are after here is intel. You and your team know more about your business than we ever will. The brief and brainstorm is how we surface that knowledge and put it to work.
Bring whatever helps. Mood boards, examples of sites you like, sketches on the back of an envelope. The more we can see of how you picture the result, the faster we can get aligned on direction. There is no wrong way to come to this meeting prepared.
Stage Two: Analyse, Diagnose, Plan and Report
The second stage is where the thinking happens. We take everything from the brief and put it through proper business analysis. That means reviewing your existing content, your technology, your customer journey and your stakeholder feedback. Where staff engagement sessions are useful, we run them. The goal is to understand what is working and what is not.
The output is a Blueprint document. It specifies the design and development phases in detail, including:
- Workshop summary, key findings and synopsis of outcomes
- Wireframes and top-level navigation workflows
- Content management specification covering platform, user roles, workflows, forms, security and key functionality
- All other technical and development requirements
The Blueprint is the contract for what gets built. If it is in there, we build it. If it is not, it is a variation. This is the document that prevents scope drift, which is the single biggest reason digital projects blow out in cost and time.
This is also why we want you involved early, not just at the reveal. Get in deep with the Blueprint. Push back on anything that does not feel right, ask for changes, and tell us what we have missed.
Stage Three: Design and Development
Only once the Blueprint is signed off do we start building. Design moves from moodboard to overarching concepts to full, detailed interfaces. Development runs alongside it. We work iteratively, with regular check-ins, so you can see progress and flag anything that needs adjusting while it is still cheap to adjust.
A note on flexibility. Our process is structured, but it is not rigid. The structure exists so that flexibility is possible without chaos. When you ask for a change, we can tell you exactly what it affects and what it costs, because we know where the project is at any moment.
We do not offer fixed prices on most projects. The reason is honesty. Digital work has too many variables, and a fixed price either inflates the quote to cover risk or forces compromises later when something unexpected comes up. We quote based on the real scope and flag variations as they arise.
Stage Four: User Acceptance Testing
Before anything goes live, it gets tested. We test the solution across the browsers and devices specified in the Blueprint, and we check every piece of functionality against the brief. Once we are confident it is working, we hand it to you for User Acceptance Testing.
UAT is your turn to put the solution through its paces. Read every word of the content. Click every link. Submit every form. Look at it on every device you said you wanted it to work on. This is your final sign-off, and it is a critical milestone in our process.
We treat UAT as a controlled phase, not a free-for-all. Feedback is collated, prioritised and addressed in a structured way. That is how you avoid the common mess of feedback arriving in scattered emails from five different stakeholders the week before launch.
Stage Five: Go-live and Delivery
Launch day is the visible part of the project, but the real work happens in the lead-up. We coordinate hosting, backups, failover, monitoring, DNS, redirects and everything else that has to be ready before the switch flips.
Then we hand the keys over. Handover and training are one of the most important things we do, because a beautifully built site is useless to a team that cannot manage it. We provide detailed handover documentation. By the time we finish, your team is in control of the solution we built.
Stage Six: Monitor and Maintain
A website is not a finished object. It is a system that needs looking after, the same way any business-critical software does. Plugins need updating. Browsers change. Content goes stale. Security patches come out. Site statistics need someone to read them and act on what they show.
You have two options for this stage. You can take it on yourselves, which works fine if you have the in-house capacity and discipline. Or you can use our support and maintenance service, which gives you a senior team on call, ad-hoc and pre-packaged monthly support, and someone keeping an eye on the site so problems get caught before they become outages.
Neglecting this stage is the single most common way good websites turn into bad ones over time. Pick whichever path suits your business, but pick one.
What This Means for You
A good process is honest. Honest with you, and honest with ourselves, about what a project takes. When you work with us, you will know what stage you are in, what the output of that stage is, and what comes next. You will not be guessing or chasing for updates.
That is the version of agency work we have built across 25+ years. The truth is, we love this work, and we love watching it pay off for the businesses we do it with. When our clients win, we win, and that is the part that keeps us coming back to it every day.
Talk to us about your project.
