FAQs

Tell us which task you want to improve and who uses it. We define the first scope together in the scope proposal.

If you already use a tool, tell us which one; if not, an idea is enough. We review what to keep and define the changes together in the scope proposal.

We focus on the task that matters first to your team. Features and review points are defined together in the scope proposal.

Walk us through a real task from its starting point to its result. Include the tools, people and steps that make it difficult today.

Describe the person who does the task and anyone who depends on its result. Their needs help define what the product should solve first.

Explain what should become easier and what would show that the task is working better. We use that goal to discuss the initial scope.

A prototype helps you try proposed screens and the steps between them before development. We define which flow to explore in the scope proposal.

Point to the step that feels unclear and explain what you expected to do there. Feedback about the task helps refine the proposed flow.

Trying the flow helps us discuss confusing steps while the design is still being shaped. It gives the team something concrete to review.

A stage gives you working progress to try and discuss. We define the features and review points for each stage in the scope proposal.

Describe the task you tried, what happened and what you expected. That example gives us a concrete basis for discussing the next change.

We compare the requested change with the agreed task and current stage. The scope proposal defines the work to include.

It can show which steps people complete easily and where they need help. We discuss that evidence when choosing improvements.

Describe the task, the difficulty and the result people need. We compare that feedback with usage evidence and define the change in a proposal.

Reviewing it helps us see whether the changed step serves the intended task. We define what to observe together in the scope proposal.