All frameworks and cheat sheets

Reference table

Four ways to validate requirements compared

Email sign-off, workshops, manual interviews and Koji

Table comparing email sign-off, workshops, manual interviews and Koji for validating requirements on candour, follow-up, reach and analysis effort.
How four ways of validating requirements compare

A comparison for business analysts choosing how to check a requirements draft against stakeholders. It sets email sign-off, workshops, manual interviews and Koji side by side on candour, follow-up, consistency, reach, tallying, evidence and effort. Costs are left out because they vary and are often not public.

Where this appears

What's in this reference table

Email sign-offWorkshopManual interviewsKoji
CandourEasy to say yes and move onLoudest voice leadsGood, one person at a timeEach person answers alone
Follow-up on a noRarelyIf time allowsYes, by the interviewerUp to 3 follow-ups per question
Same wording for allYesYesVaries by interviewerYes, one guide
Reaching 20 peopleNo schedulingWeeks of calendarsWeeks of calendarsAnswer when free
Tally per requirementBy handBy handBy hand from notesCounts in the report
Quotes behind a verdictEmail commentsMeeting notesInterview notesLinked to supporting responses
Analysis effortChase and collateFacilitate and write upHours per interviewAI analysis per interview

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/requirements-validation-methods-comparison-table"><img src="https://www.koji.so/visuals/requirements-validation-methods-comparison-table/requirements-validation-methods-comparison-table.png" alt="Table comparing email sign-off, workshops, manual interviews and Koji for validating requirements on candour, follow-up, reach and analysis effort." width="1200" height="931" /></a>
<p>Source: <a href="https://www.koji.so/visuals/requirements-validation-methods-comparison-table">Four ways to validate requirements compared</a>, Koji</p>