Loading Gridfused0%
Back to Blog
Business|Analysis|November 16, 2026

How Do You Find Out What’s Broken in Your App?

Start with what your customer is trying to do, then follow what happens until you can see where the problem begins.

João Dezembro · 5 min

More in Business

A customer tells you that something is wrong with your app. Maybe they cannot finish a task, or they come back later and the information they entered is gone. You ask for help and hear different explanations about what needs to be fixed, even though you are still trying to understand what happened.

Before agreeing to more work, I would start with the task the customer was trying to complete and follow it from the beginning. You may not be able to find the cause yourself, but you can collect the details someone needs to investigate it and ask questions that help you understand what they find.

Start with the task that failed

Imagine your app lets customers create an account and save information they want to return to later. One customer says they entered their details and saved them, but the information was gone when they signed in again. From their point of view, the app lost what they had entered, and they may now have to do that work a second time.

Start by asking the customer what they did and what they saw before leaving the app. Did they receive a confirmation that the information was saved, and were they using the same account when they returned? If you can safely try those steps with a test account and test information, go through them yourself and note where your result differs from what you expected.

Suppose your test works and the information is still there when you sign back in. That does not resolve the customer’s problem, but it gives you a reason to look for a difference between their attempt and yours. Perhaps they were using another account, or the problem only happens under conditions you have not tried yet. The details they can share about their experience may help someone repeat it.

If the information disappears in your test too, you have something more specific to show the person investigating. You can explain the steps you followed and what happened after you returned, so they do not have to begin with only a description that the app is broken.

Check what happens to the information

At this point, there is still more than one possible explanation. The information may not have been saved, or it may be there but not showing when the customer returns. Those situations can look identical on the screen, even though the work needed to fix them could be different.

Ask the person reviewing the app to follow the same task and explain what they find. If they can show that the information is saved correctly and the problem is in how it is displayed, they can look at that part of the app. If it was never saved, they need to find out why and whether the same issue affects other information customers enter. Until someone checks, either explanation is still a possibility.

To investigate, the person helping you may need access to the app, the code and the place where information is stored. Depending on how the app was built, there may also be another service involved. If you do not know where those things are or who controls the accounts, start with the person or team that built or currently manages the app.

Agree on what access is needed and how it will be removed after the review. Where possible, use a test account and test information instead of sharing customer data that is not needed. If an account is unavailable, ask what the reviewer can still check and which parts of the answer will have to wait.

Ask for findings you can understand

When the review is finished, you should be able to understand what was checked and what the team found. In this example, you want to know whether the information was saved, why the customer could not see it again and whether the same issue can affect anyone else. The team may not have all those answers yet, but it should be able to tell you what it has confirmed and what still needs to be investigated.

If the review identifies a risk involving customer information, make sure you understand what needs attention and how it will be assessed. Looking into one failed task can reveal a concern, but it does not by itself establish that every part of the app is secure.

Use the findings to decide what to fix

What you do next depends on those findings. If the team can show that the information is saved correctly and the problem is limited to displaying it, you can discuss fixing that part and testing the customer’s task again. Ask what the work will include and what the customer should be able to do when it is finished.

If information is not being saved properly in several important parts of the app, a change to one screen may not address the whole problem. The team may need to investigate more of how the app handles information before it can propose a reliable fix. That could lead to a larger piece of work, but you do not need to agree to rebuilding everything before you know what is affected and what can stay.

Before work begins, make sure the proposal explains the problem it is meant to solve, what is included and how you will check the result. For the account example, you could test that a customer can save their information, leave the app and find it again when they return, while also checking any other part the team says was affected.

If the review has not yet explained why the information disappears, agree on the next investigation first. Once you understand what the team knows and what remains uncertain, you can decide what work to approve without having to guess at the solution.

João Dezembro

João Dezembro

Founder & Managing Director

Founder of Gridfused Technologies. Software architect and engineering leader focused on building reliable products, systems, and AI-enabled operations.

November 16, 2026

5 min

Filed under

Categories