Revive the lost art of site maps in minutes with easy-to-use prompts and uxGPT SIte Maps

Usability CountsUsability Counts

I miss site maps. 

No one really does them anymore, which sounds like a Yogi Berra quote.

You might think site maps are old school, but for truly knowledgeable and experienced designers, they’re a secret weapon, especially for us information architects. Site maps give you a bird’s-eye view of the entire project. 

I like them because it’s like having a map before a road trip; you can see where everything is and plan your journey without missing any important stops.

They also help keep everyone on the same page — literally. When you’re working with developers, stakeholders, and content creators, having a clear site map means fewer misunderstandings and smoother communication. It’s all about creating a shared vision where everyone can see the same patterns, and they’re wonderful alignment tools if everyone understands the format.

ChatGPT is rather good at creating them and thinking about some details that were time-consuming before, so get a sense of what you need and what could be missing and can add it to yours. There really isn’t much to the actions needed for an application — it’s called CRUD for a reason — so let’s get started with site mapping.

Start wide

Starting with a simple prompt is a solid way to kick off the process because it sets a clear, focused goal right from the get-go. It’s broad enough to give you creative freedom but specific enough to keep you on track and give you an idea of how other products are structured because very few systems are original today.

This kind of prompt encourages a very high level approach, allowing you to dive into the details and think about the user experience. It’s a great starting point that balances high-level planning with the need to consider specific user actions and page types in future prompts.

Let’s start.

Prompt

Create a site map for a customer relationship management system.

Refine

That first prompt was a good start, but now we want to add more structure, and here’s how to do it. Asking for a numbered list sets up a logical, easy-to-follow format that can also act like a checklist. Additionally, it’s helpful to include actions like creating (labeled as new), deleting, updating, and viewing, as these are fundamental interactions users will need when managing their information.

Plus, the focus on multiple levels of detail means nothing gets overlooked, making it perfect for a thorough and user-friendly site map.

Let’s refine.

Prompt

Create a site map as a numbered list for a customer relationship management system that is multiple levels deep in detail. Include the actions of creating (labels as new), deleting, updating, and viewing.

Refine more

Now let’s add more detail to help categorize the content. 

I recommend labeling page types as list, detail, form, report, and confirmation modals to help categorize the content. This makes it easier to visualize the user journey and design accordingly, and it gives structure to system-wide patterns that we can reuse. This is not only when talking to the developers but also when thinking about what components to use from the design system.

Additionally, suggesting page titles not only aids in clarity but also provides a head start in the wireframing process, ensuring consistency in how we are naming elements within the system.

Try out this prompt as an example.

Prompt

Create a site map as a numbered list for a customer relationship management system that is multiple levels deep in detail. Include the actions of creating (labeled as new), deleting, updating, and viewing. Label the page types as a list page, a detail page, a form page, a report page, and a confirmation modal, the last specifically for deleting. Suggest page titles for each.

Refine even more

Now we can go all out with the following context.

Roles and responsibilities: Specifying different user roles such as Administrator, Manager, and User, along with their respective permissions, ensures that the system is built with security in mind. Attaching them to the site gives even more context.

Integrations: Integrations with third-party applications like email, calendar, and social media ensure seamless connectivity, which is a must for modern, efficient workflows in business-to-business systems. I would include this kind of system in the prompt.

Alerts and Notifications: These actions ensure that users remain aware of critical events, enhancing the system’s responsiveness and user engagement, and should be considered in the information architecture.

Overall, this prompt sets a solid foundation that most designers don’t consider when designing the site map. It covers functional, security, and usability aspects, which are vital for creating a well-rounded, user-centric application. This is about as detailed as a checklist that you’re going to need when getting started.

It may seem long and overly detailed, but try it — it’s fun.

Prompt

Create a site map as a numbered list for every element of a customer relationship management system that is multiple levels deep in detail. Include the actions of creating (labeled as new), deleting, updating, and viewing. Label the page types as a list page, a detail page, a form page, a report page, and a confirmation modal, the last specifically for deleting. Suggest page titles for each. Specify different user roles (e.g., Administrator, Manager, User) and their permissions for each action and page type. Include pages for integrations with third-party applications (e.g., email, calendar, social media) and specify any dashboard or analytics views required. Highlight any required notifications or alerts related to actions.

Try out this Custom GPT — uxGPT Site Maps

Don’t want to do the work yourself? Not a problem. I’ve done a lot of the legwork for you.

Try this custom GPT at uxGPT Site Maps.

The post Revive the lost art of site maps in minutes with easy-to-use prompts and uxGPT SIte Maps appeared first on Usability Counts.