Product Ideas From Engineering Friction

TL;DR

Good product ideas often start as repeated friction. If the same problem interrupts good work every week, it may deserve a tool, a workflow, or a better default.

Friction Is a Signal

Not every annoyance should become a product. Some problems are rare, personal, or solved well enough by existing tools. But repeated friction is worth paying attention to.

In engineering teams, friction often shows up as repeated explanations, manual checks, unclear ownership, fragile deployment steps, or knowledge trapped inside one person's memory.

Write the Problem Before the Solution

When I notice friction, I try to write the problem in plain language before imagining the product:

• Who feels this problem?
• When does it happen?
• What do they do today?
• What is the cost of ignoring it?
• What would make the next step easier?

This keeps the idea grounded. A product is only useful if it improves a real moment.

Start Smaller Than an App

The first version can be a checklist, a script, a dashboard, a template, or a documented workflow. If that small solution keeps being useful, the product shape becomes clearer.

This approach also reduces ego. The goal is not to build a big thing. The goal is to remove enough friction that people can do better work.

Conclusion

Product thinking does not always start with a market map. Sometimes it starts with noticing the third time a team loses energy to the same tiny problem.