FAQs

Support can cover fixes, measurement and improvements after launch. We define the tasks, coverage and way of working together in the scope proposal.

We review the affected task, its impact and the agreed coverage before defining the next change.

We can discuss fixes and new features as your team identifies needs. We define priorities and the scope of each change together in the proposal.

Describe the steps, the result and what you expected instead. Include the affected screen and device so we can discuss the correction.

Explain who is affected and which task is blocked or made harder. We use that impact to discuss the order and scope of fixes.

Try the task that exposed the problem and describe the result. We define the review steps for the correction in the scope proposal.

Start with what you need to learn about a task, such as where people stop. We define the relevant observations in the scope proposal.

Connect each measurement to a decision your team needs to make. We discuss the available information and the work needed to observe it.

Evidence can help distinguish a confusing step from an infrequent request. We review it with your team before defining the next support change.

Describe the task you want to make easier and what users do now. That example helps us define the proposed enhancement.

We discuss whether the existing flow can serve the need or whether a different capability is required. The proposal defines the chosen scope.

Choose a specific step and explain the intended result. We define the work and how to review it together in a scope proposal.