Product planning at ShipBob
01 / 04 · Understand
Understand how your product works today.
Ask a product question in your own words. Driver follows the relevant code across your systems to explain current behavior, business rules, and dependencies, with sources you can review.
02 / 04 · Evaluate
Check your assumptions against evidence.
Check whether a product assumption matches how your software behaves. Combine Driver’s findings with evidence from the tools connected to your assistant to understand what is supported and what still needs an answer.
03 / 04 · Define
Write requirements grounded in actual behavior.
Use the findings to define desired behavior and acceptance criteria. Keep product decisions explicit and supporting evidence close, so your team can agree on what should change.
04 / 04 · Plan
Give engineering the context behind the request.
Share the proposed requirements, source evidence, and open decisions in an engineering handoff. Give engineers the context behind the request so they can assess and plan the work.