Start here.
Review the app by trying an agreed task. Describe what you did, what happened, what you expected and why the difference matters. Keep feedback in one shared place, separate problems from new requests, and agree which decisions need attention next. After a change, try the task again before calling the issue resolved.
- An example of unfinished work tells your developer more than a general request to make the app easier.
- Explain the problem before deciding which button or screen should solve it.
- Agree the next action for each important comment and check the result together.
What should you try during a review?
Imagine a business having an app built to manage customer orders. An office colleague enters an order, and another person prepares it. This is a fictional planning example.
Before opening the latest version, agree what is ready to review. A developer may be asking about one part of the work rather than presenting a finished app. Ask which tasks you can try and which parts are still incomplete.
Follow one order from entry through preparation. Include a correction, such as changing a quantity after saving. Ask the people who do each part of the job to try it themselves, rather than only watching a demonstration.
Use made-up records in a practice area your supplier has confirmed is safe. Check whether any action could send a message or affect real work. Keep customer details out of screenshots and recordings shared for feedback.
How do you explain what feels wrong?
“The order screen is confusing” describes a reaction. Add the moment that caused it: “I changed the quantity, saved the order and returned to the preparation list. That list still showed the old quantity. I could not tell which one the next person would use.”
That gives your developer a sequence to investigate and a business consequence to understand. Include the practice record, the steps you took and the result you expected. A screenshot can help show where you were; a short recording may help with a problem that only appears after several steps.
Say how often you saw the problem without guessing about its cause. “It happened on this order after I changed the quantity” is useful even if you cannot make it happen again. Your developer can ask for more information.
You can suggest a solution, but explain the need behind it. “Add a red warning” might be one answer. The underlying need is for the person preparing the order to notice a changed quantity. Leave room to discuss other ways to make that clear.
Is this a problem, an unanswered question or a new request?
Different comments need different conversations. Something may fail to do what you agreed, work as planned but prove difficult to use, or reveal a decision nobody has made yet. You may also discover a useful capability that was never included.
In our example, an order failing to save needs investigation. Uncertainty about who can change an order needs a business decision. Asking the app to predict next month’s orders introduces a different job. Putting all three under “fixes” leaves the next step unclear.
Ask your supplier to compare the comment with the agreed task and scope. Discuss whether it needs investigation, clarification, a correction or a separate estimate. Agree any effect on price or timing before assuming the change is included.
Do not discard a concern just because it was unexpected. If the agreed design cannot support an essential part of the work, explain that consequence and review the plan together. The useful outcome is a clear decision about what happens next.
Which feedback should get attention first?
Describe the consequence rather than marking every comment urgent. Could the wrong order be prepared? Is someone unable to finish an ordinary task? Does a label take a moment to understand, or could it lead to a costly misunderstanding?
For each important issue, note who is affected, when it occurs and whether there is a reasonable temporary way to finish the work. A workaround that requires a manager to repair every order deserves discussion before the app is used widely.
Agree priorities with the people responsible for the project. A colour preference and a confusing instruction may look equally small on screen, but their effect on the job can be very different. Explain that effect so your supplier can discuss the effort and options.
Keep new ideas visible in a separate later list. That lets you acknowledge them without continually changing what the current release is meant to accomplish. Revisit them when you can consider their value alongside the work still outstanding.
How do you keep comments from getting lost?
Agree one shared place for feedback. It might be a document or a list your supplier already uses. Each item needs enough context to understand it, someone responsible for the next action and a visible decision. A conversation in a meeting can be useful; record what you agreed afterwards.
Choose a business contact to bring together conflicting comments. If one colleague wants orders grouped by customer and another wants them grouped by preparation date, find out which job each is doing. Give the supplier a decision or a clear question to explore, rather than two unexplained instructions.
When a change is ready, try the original example again. In our fictional order app, change the quantity and check what the person preparing the order sees. Ask someone in that role whether the result gives them what they need.
Record whether the issue is resolved or what remains unclear. Finish the review by agreeing what you will check next and when a response is needed. Specific feedback is useful because it leads to a decision you can both understand and a result you can check.
Bring these notes to the next review.
You do not need technical language. A short account of what happened and the business decision it affects is a useful starting point.
- The job
- Who was using the app, and what were they trying to finish?
- The example
- Which safe practice record, steps and result show the problem?
- The consequence
- What could someone miss, misunderstand or be unable to complete?
- The next check
- Who will respond, what is agreed, and how will you check the result?
Planning something with a similar workflow?
Discuss your project with usA couple of common questions.
Do we need to tell the developer how to fix each problem?
Explain the job, what happened and what the person needs to be able to do. Share any suggestion you have, but ask the developer to explain the available options and tradeoffs. You can judge the proposed result without choosing the technical approach.
What if staff disagree about the feedback?
Ask each person to show the task behind their request. They may be doing different jobs or working with different kinds of orders. Let the person responsible for the business process resolve a genuine policy choice, and ask the supplier to explore options where one approach may not fit both tasks.