4 steps to solve problems like a product manager ⚙️ 💡

Do you keep missing project deadlines or losing money, no matter how hard you try to fix things?

When something goes wrong with a product — like unhappy users or team misunderstandings — it's easy to pick a quick, easy fix.

But quick fixes only work for a short time. They don't stop the problem from coming back.

To build a great product, you need to find a solution that lasts.

Here are 4 steps product managers (PMs) use to solve problems for good.

Before you can fix a problem, you need to understand its parts.

Every product issue has three pieces:

1. Symptom: where you first notice something is wrong. (Example: Users close your app after 3 minutes.)

2. Real reason or root cause: the hidden cause of the trouble. (Example: The text on the screen is too confusing.)

3. Category: Is it a problem with the user (they get confused), the plan (unclear goals), or doing the work (team misunderstandings or software bugs)?

Why does this matter?

If you only fix the symptom, the problem will keep coming back because you didn't fix the real reason.

To find the root cause, do not guess. Start at the symptom and ask "Why?" five times.

Let’s look at a scenario: 60% of users close your app within 3 minutes of downloading it.

Start with the symptom: Users are closing the app early.

1. Why are users closing the app after 3 minutes? They look at the welcome screen and leave.

2. Why do they leave? They do not understand what the app does.

3. Why don't they understand it? The screen text uses confusing industry words.

4. Why is the text difficult? The team wrote it quickly without a guide.

5. Why is there no guide? We skipped making a guide to meet a launch deadline.

What's the root cause? A missing strategy (no writing guide) due to a rushed timeline. 🎯

Now that you know the root cause, you need a two-solution approach:

• Quick fix: A fast solution to stop the trouble today.

• Permanent fix: A long-term solution so the problem never happens again.

How to find and balance both solutions?

1. Think of fixes (quick and permanent) with your team that only target the real reason.

2. Select only the solutions that fit your current timeline and budget

3. Apply the quick fix immediately and add the permanent fix into the next few weeks of team tasks so it isn’t forgotten.

Quiz

Let's revisit the scenario from "Find the Real Reason" above:

• Problem: 60% of users close your app within 3 minutes of downloading it.

• Root cause: a missing strategy (no writing guide) due to a rushed timeline

What's the best way to handle this situation like a product manager?

A. Replace the confusing words with simple text written by the PM alone today.

B. Run a week of user research to find out exactly which words are unclear.

C. Have a writer fix the current text today, and schedule time next week to build a team writing guide.

D. Cancel all upcoming feature work for a month to build a massive guide.

After you launch your solutions, check the data to prove they actually worked.

Track these four questions:

1. Did the numbers you use to measure success improve? Did the percentage of users leaving drop below 60%?

2. Did the fix break something else? Did changing the text accidentally break the app's layout?

3. Is the team's internal workflow better? Is the team writing faster now that they have a guide?

4. Are customer complaints about this issue going down?

Product management is a loop, not a straight line.

If your data didn't improve, start reviewing the problem pieces and try ag

Practice these steps on a problem in your own life or project today: