1. Information Gathering is not to be underestimated
The information gathering phase relies on client input to fill in gaps. You don't need to have all the answers, but be ready to discuss user goals, business objectives, site features, pain points, and comparable websites. This preparation greatly benefits the project.
2. Sitemap Focuses on Pages, Not Content
A sitemap outlines your website's pages, not the content within them. Avoid overloading the sitemap with details about individual page elements. For example, decisions about integrating features like contact forms or search bars belong in the wireframing UX phase, after the overall page structure is defined.
3. Naming Menu Items
Menu labels should be consistent and intuitive for your audience. For example, labels like "Members," "Public," and "Volunteers" are cohesive, while "Council Meetings" is too specific and disrupts the flow. Keep labels broad and relatable to enhance navigation.
4. Consider Backend Usability
When defining requirements, think about both front-end functionality and backend usability. It's essential to ensure the administrative side is easy to manage. Discuss these aspects with your web development team early on to avoid last-minute changes.
5. Involve Stakeholders Wisely
Involve stakeholders heavily during the initial stages for input and information gathering. After that, consult them mainly during key milestones, such as wireframes, creative briefs, mockups, and site reviews, to prevent bottlenecks and streamline the process.
Related Blogs
How to Create Your First SitemapIs it Time To Redesign Your Website?
Alex
Senior Project Manager
Alex has over 10 years of experience managing digital projects with a background in Psychology and Web Design.