> 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/making-a-design.md).

# Making a Design

Thinking like your user and applying that thinking to an interface design.

## Before making a design: Choosing a tool

There are two main trade-offs when choosing a tool to make a design. The first is time: the more realistic a design feels, the longer it takes to create. The second is user perception. Lower-fidelity designs often elicit more candid feedback because users feel the concept is still rough and easy to change. Conversely, if users think you spent a significant amount of time on a design, they may hesitate to tell you it does not work for them.

{% hint style="info" %}
AI notes (August 2026): Previously, developing an interface took longer than creating a prototype, making software development the most expensive part of implementation. With AI, the time needed to build an idea is rapidly decreasing, bringing it on par with lower-fidelity prototyping tools. Nevertheless, you may still choose to use lower-fidelity prototyping tools or prompt AI to generate low-fidelity prototypes, especially when testing concepts with users.
{% endhint %}

For your First design, choose tools you already know. These might include presentation software like Microsoft PowerPoint or Google Slides, design software like Adobe Illustrator, or drawing software like Apple Pages. Two other purpose-built tools worth considering are [Balsamiq](https://balsamiq.com/) (for low-fidelity designs) and [Figma](https://www.figma.com/) (for high-fidelity designs). You may already have free access to them through your institution or an academic license.

Paper prototypes are another historically popular low-fidelity medium, which typically have a quick, scribbled look. Some designers prefer paper prototypes because tactile work can boost brainstorming. However, others find it inconvenient that they cannot be saved or shared digitally without scanning them first. Choose whichever medium works best for you.

## Make (multiple) designs

Your first idea is rarely your best idea. Although it can be hard to look past an initial concept, forcing yourself to explore alternatives will help you come to the strongest solution. Ideally, collaborate with others and spend at least twice as much time developing alternate ideas as you did on the original design. You may find it useful to leverage established interface pattern libraries for scientific software, such as [STRUDEL](https://strudel.science/), which features design best practices and reusable software components.

{% hint style="info" %}
AI notes (August 2026): For smaller tasks, AI can help generate design ideas. Frame your prompt around the specific goal you want to achieve, such as clarifying button labels or refining navigation controls.
{% 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/making-a-design.md?ask=<question>&goal=<endgoal>
```

`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.