> For the complete documentation index, see [llms.txt](https://www.thinkinglikeyouruser.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.thinkinglikeyouruser.com/evaluating-where-you-are.md). # Evaluating where you are Now that you have thought about your user, you can adopt their perspective as you evaluate the tool as it exists today. Especially consider the user's initial experience with the tool, as it is critical for usability yet often the most challenging to get right. While the methods below are particularly effective and engaging when done collaboratively, you can also perform them on your own. ## Content overview A Content overview involves using a spreadsheet or document to map out where documentation or text appears in the interface. Use this process to identify redundancy and flag potential mismatches in language, labeling, hierarchy, and priority. Consider what information your user needs and the most logical sequence in which to present it. Avoid overwhelming users with details until they need it. While reviewing an entire interface can be time-consuming, focusing on a small section makes the task manageable. ## Heuristic evaluation Heuristic evaluation involves assessing a tool against standard design best practices, known as "heuristics." [Heuristic Evaluation for Scientific Software](https://github.com/cass-community/heuristics-for-scisoft/) provides a helpful list of relevant guidelines. Begin by reviewing the heuristics, then select a short, 5-minute task that your target user would typically perform. Walk through the task from the user's perspective, noting any areas where the interface doesn’t align with the heuristics. ## Competitive analysis Analyzing other interfaces can reveal helpful design conventions and inspire ways to improve your existing design. Adhere to established norms unless you have a compelling reason to depart from them. ### Three types of tools to evaluate **1. Direct competitors or similar tools:** Evaluating tools that are similar to yours helps you gather design ideas and identify opportunities to improve upon existing solutions in your field. **2. Domain-specific tools:** Reviewing tools in your specific field helps you understand standard paradigms and conventions—both scientific and in general. **3. Analogous tools outside of science:** Examining tools that share core functional concepts (such as searching, mapping, or editing) can help you think creatively and discover novel ways to guide users and structure information. ## Basic Visual Design and Design Systems While UX extends beyond visual appeal, an attractive interface can enhance perceived usability (see the [Aesthetic-Usability Effect](https://en.wikipedia.org/wiki/Aesthetic%E2%80%93usability_effect)). It is worthwhile to conduct a quick audit of your site, especially the landing page, to resolve simple issues, such as inconsistent navigation bars or text links that should be styled as buttons. If an issue or solution requires deeper consideration, save it for it’s own project. Your interface could be well designed enough that you may find nothing that needs changing. Another way to enhance visual appeal is by adopting a basic design system. A design system establishes guidelines for the interface's appearance (see [this article on design systems](https://bssw.io/blog_posts/design-systems-to-help-amplify-development-of-usable-scientific-software-interfaces) for more details). In the context of Thinking like your users, this means maintaining consistent colors, typography, font sizing, and visual alignment across elements. Again, your interface could be well designed enough that you may find nothing that needs changing. Selecting colors, fonts, and font sizes can be time-consuming. You can adopt your institution's or department's standards, which often include typography and secondary colors. Additionally, institutional communications or branding teams may be available to assist you. **Avoid spending too much time on this step. It’s best to select a functional palette, verify they are color-blind accessible, and proceed.** {% hint style="info" %} AI note (August 2026): Some UX practitioners have found it useful to have AI review and suggest guidelines, including picking accessible colors. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.thinkinglikeyouruser.com/evaluating-where-you-are.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.