Bring the source material for the decision you need to make: a set of customer reports, a specification, a release change list, or proposed designs. Driver organizes that material and compares it with the code so reviewers can check the reasoning.
- Assess customer impact from Jira reports: count distinct accounts in a defined ticket set and separate confirmed failures from possible exposure.
- How complete is this feature against the spec?: produce a requirement table with implementation evidence, test coverage, and release gaps.
- What shipped, in words customers understand: turn verified release changes into notes about customer-visible behavior.
- Compare implementation options: examine dependencies, compatibility, and unresolved assumptions before the team chooses a design.