I am often wrong
Boris Cherny’s Blog
Opinion — commentary, not a factual news event.
The author describes an iterative process for product building that repeatedly redefines the problem and approach when new information appears, acknowledging they are often wrong during execution. The note says the process is implemented “many tries” for complicated problems. This changes teams’ expectations toward real-time feedback, clearer problem/approach definition, and updating assumptions as new data arrives.
Why it matters
Product work benefits from a repeatable loop: gather information, define the problem, choose a simple approach, set a goal, and act quickly. New evidence should send the team back through the loop, so changing direction is healthy when it reflects updated beliefs rather than unclear thinking.