The best product decisions we have seen came from engineers who deeply understood the user problem they were solving. Not from PMs writing specs, not from designers creating flows — from engineers who asked "but why does the user actually need this?" and refused to accept a vague answer.

The False Divide Between Engineering and Product

Most companies treat product management and engineering as separate disciplines with a handoff in between. This is a mistake. When engineers are only responsible for "how" and not "why," you get technically correct implementations of the wrong thing. The best products are built by engineers who own both questions.

What Engineers Already Know

Engineers have a massive advantage in product thinking that is rarely leveraged: they know what is possible and what is hard. A PM might spec a feature that looks simple on a whiteboard but requires six months of infrastructure work. An engineer knows this immediately and can propose an alternative that delivers 80% of the value in 20% of the time.

The most valuable thing an engineer can say in a product meeting is not "that will take three months." It is "here is a simpler version that solves the same user problem."

How to Develop Product Thinking

Spend time with users. Not in user research sessions with one-way mirrors — actually watch people use the product you built. The gap between what you built and how people actually use it will teach you more about product thinking than any framework or book.