Skip to main content

A question beats a guess

When the plan is unclear, ask the person who decides. A wrong guess costs more than a question.

Written by Jack Meyers

No plan is complete. Something always comes up during the build that the plan didn't say. What happens next decides whether the right thing ships.

Guesses ship

A person who builds usually notices a gap, and asks. A coding agent doesn't. It picks something reasonable, and keeps going. That guess becomes part of the product, and nobody on the product side ever chose it.

A quiet guess about a product question is the real problem. The product lead never got to decide.

Ask instead

When the plan doesn't answer a product question, ask the product lead. A question takes a few minutes. A wrong guess can take days to find and fix, or it can reach customers.

This applies to technical questions too, but differently: how to build it is the builder's call. Ask the product lead only about what the product does, and what people see.

How Grove does this

  • Builders raise threads. A builder or their coding agent raises a thread on the project. The thread goes to the product lead's Queue. See Ask the product lead instead of guessing.

  • The coding agent checks with its builder first. It tells the builder what it wants to ask, and doesn't post over their head.

  • Grove asks too. When Grove isn't sure what you mean, it asks one short question, instead of making a change you didn't want.

  • Grove checks plans for open questions. Before a project is ready, Grove looks for questions a builder would have to ask before they could start.

Related articles

Did this answer your question?