Product-Engineering Quick Estimation Process
Situation
Articulated position on providing quick, low-confidence estimates for Product prioritization. Engineering should provide 20% confidence SWAGs on demand so Product can do early prioritization - these are not commitments engineering can be held to. Distinguished between committing to work without a design (bad) vs providing a quick guess marked as such (good).
Reasoning
Values enabling Product to prioritize without creating false commitments from Engineering. Want to move organization toward move fast, adapt as we go vs wait until full clarity. The org needs to learn the difference between a SWAG for prioritization vs a commitment. Balancing Justins valid concern (dont commit without design) with Products valid need (rough estimates to prioritize).
Additional Context
Response to Bjorn/Brady concern about Justins pushback on a request. Justin and Brady subsequently met to align. Goal is getting Product and Engineering working better on planning and prioritizing together.
People Involved
Justin Haynes, Max Spevack, Bjorn Hovland, Brady Dibble
Source
reflection
AI Confidence
82%
Related Context
slack
What Ive committed to product is that we would do a much better job of turning around quick, low confidence estimates when requested so that Product could do early prioritization. These are not estimates that engineering can be held to.
Outcome
Partially successful - slow adoption of the process
Recorded on January 12, 2026
Decision ID: 8370c8a7-acf0-45e5-acc2-e3a7ec2fbeb1