Product

How to tell a System One task from a System Two task

If the possible answers can be written down before you ask, the task repeats at volume, and nobody needs a written reason, a fast decision model can do it. Everything else needs a language model or a person. Here is the rule, with three features walked through it.

How to keep a spec alive after the build

Every spec is accurate on the day the software is released and wrong within a quarter. The fix is to make the spec the source of automated checks, so the software cannot disagree with it without anyone noticing.

How to decide if a feature needs a human in the loop

Most teams answer this based on how they feel, then discover the rule in an incident review. Four questions decide it properly, and only one of them is about accuracy.

Why scope creep happens and how to stop it

Scope creep is rarely about laziness or bad discipline. It is about unclear goals and a fear of saying no. Here is how to keep scope under control and still accept good ideas.

Why your MVP should do less than you think

Every feature you add before launch delays the day you learn whether the product works. The discipline of cutting is what gets you the answer faster, so your first version should do one thing well.

How to run a product discovery sprint before you build

Before you commit months to building, spend a week removing your biggest unknown cheaply. Define the question, prototype the risky part, test it with real users, then decide.

How to price a SaaS product without overthinking it

Most founders price their software from their own costs, then set the number too low and never change it again. Price on the value the customer gets, start higher than feels comfortable, and treat pricing as something you keep adjusting.

Five ways to hire the right product manager

The right product manager changes the direction of a team. The wrong one quietly slows everything down.