Six practical tools for a stronger UX design process.

Start with the decision, then choose the tool

A design tool is useful when it helps answer a question. Before opening a canvas, write down the decision you need to make: what people are trying to do, where a journey becomes confusing, or which idea deserves a prototype. These six tools are practical documents and activities. You can use them in a notebook, a shared document or your preferred design software.

1. An interview guide

Write questions about a recent real experience instead of asking whether someone likes your proposed feature. Ask what they were trying to do, what happened next and what they did when something went wrong. Keep space for follow-up questions.

For a service-booking example, ask: ‘Tell me about the last time you booked a laundry service.’ Record the person's account separately from your interpretation. A complaint is evidence to investigate; it is not automatically a feature request.

2. A task flow

Draw the steps needed to complete one job, including the decisions and recovery paths. Start with a clear trigger and end with an observable result. ‘Choose a service → add an address → review the order → confirm’ is more useful than a list of screen names.

Add the awkward branches: an unavailable service, an invalid address or an interrupted payment. These branches reveal missing requirements before visual polish makes the flow look complete.

3. A wireframe

Use a low-detail layout to decide what information belongs together and what action should stand out. Give buttons realistic labels and put real-length text in the layout. Avoid spending the first iteration selecting shadows or decorative icons.

Try two arrangements for the same task. Compare them against the job the page must support, rather than choosing the version that looks busier or more impressive.

4. A prototype

Connect only the screens needed to test your current question. If the question is whether the order summary is understandable, prototype the route to that summary and the confirmation step. You do not need to simulate every part of the app.

Include a relevant failure state. Decide what the person can change, what remains saved and how they can recover. A prototype that only demonstrates the happy path leaves important decisions unanswered.

5. A usability task

Give a person a goal without describing the exact controls to use. ‘Book laundry collection for tomorrow at your home’ leaves room to observe their choices; ‘Tap Laundry, then tap Next’ only checks whether they follow instructions.

Observe where they pause, what they expect to happen and whether they can explain the result. Separate an observed problem from a suggested fix, then choose the smallest change worth testing next.

6. A decision log

Record the question, the evidence available, the choice made and the uncertainty that remains. Include a short reason for an important tradeoff. This keeps a later review from becoming a debate based only on memory.

A useful entry might read: ‘We kept address confirmation before payment because the service depends on the collection location. We still need to test the flow with saved addresses.’ The example documents reasoning without pretending the design has already produced a measured outcome.

Try it on one small journey

Choose a task such as booking a service or recovering an account. Make a one-page interview guide, a task flow with one failure branch and two rough wireframes. Build a small prototype, write a goal-based task and record the decision you would revisit after testing. The value comes from connecting the evidence to the next choice.