I created this to help explain the important steps on both sides of “build,” and I tried to keep it brief and jargon-free to avoid scaring off partners, stakeholders, and colleagues who were unfamiliar with all that goes into building even the simplest of websites.
I also created this as a reminder to myself of the things you cannot skip, no matter how small or ostensibly simple the request.
The phases are useful-to-me ways of breaking down the web design process to get a sense of sequencing. Also, it helps to note spots where it's important to get buy-in or consensus from partners, users, or other stakeholders.
For each phase, I've summarized goals, a few questions, important activities, and deliverables. Below the line, I've listed templates, resources, other tools that can help dive deeper or document what you learned, and what you need to keep in mind in order to stay on track to build an accessible website.
Orange is for templates, yellow is for resources and articles I've found useful.
Discovery should define the problem and set the project up for success.
Make sure you document assumptions, define the project team, and get to know the content you're working with.
What is success? Who are our audiences? Who will do the work?
Before you wrap up the discovery process, make sure the project team has discussed:
And the client and project sponsor have approved:
Strategy and planning gives shape to the site.
Aim for a clear map of how the information should be organized and what types of content it should support. This will help define a realistic timeline.
Where will the site live? When and how will the project get done?
Before you move on, make sure the project team (especially the designer and developer) have reviewed:
And the client and project sponsor have approved:
Design, content and development often overlap. The wireframes become designs, the page tables fill up with real content and the code provides the long-term framework.
Communication is crucial to make sure everyone has what they need to stay on-track.
Before you move on, make sure the project team and client contact have reviewed:
And the client and project sponsor have approved:
Make sure everyone's on board, alert any stakeholders whose workflows may be disrupted and make sure your launch plan is in place.
Once you're ready, it's time to go live.
Before you go live, make sure everyone is aware of:
Launch is just the beginning: now it's time to learn to take care of the site, update content and keep improving it.
This includes measuring success, keeping content up-to-date, repairing any lingering issues and responding to user feedback.
* This is not an agile process. This is not an ideal process. This process probably only makes any sense at all for informational websites, and none at all for more complex web applications.