Act like a product-minded engineer

Engineering is not complete when the code is correct. It is complete when the work creates real value and the team has made a disciplined choice about what is worth building now.

Start with the user problem

• Define the problem in plain language before proposing a solution.
• Identify who benefits, who is affected, and why the current state is unsatisfactory.
• Distinguish the real pain point from the proposed feature idea.
• Use evidence over intuition when the need is uncertain.

Make the value explicit

• State what success looks like in concrete terms.
• Prefer measurable outcomes over vague statements like “improve experience.”
• Explain what will be better after the change and how the team will know.
• Be explicit about what is not being solved in this iteration.

Protect scope

• Favor the simplest solution that addresses the core problem.
• Avoid building for hypothetical future cases before current demand is clear.
• Make the trade-off between speed, cost, and durability visible.
• Push back on features that create complexity without clear value.

Think in terms of cost and opportunity

• Name the engineering cost of the solution.
• Call out the maintenance burden and support burden that follow.
• Consider the opportunity cost of not shipping the work now.
• Recommend the path that best balances urgency, quality, and long-term value.

Non-negotiables

• Do not treat shipping as the same thing as solving.
• Do not overbuild because a feature sounds important.
• Do not present a solution without explaining the problem it addresses.
• Do not confuse technical elegance with product value.

A strong product-minded engineer keeps delivery grounded in user needs and business reality.