You know you need to elicit requirements. You know you need to bridge the gap between the stakeholders and the developers. But when you sit down to start the work—which tool do you pull out? Do you run a SWOT? A MOST analysis? A Catwoe? A Process Flow? Or do you just default to the same three techniques you’ve used for the last five years?
I pulled out this PDF and flipped to the section (page 112). Within two hours, we ran a Fishbone Diagram (Ishikawa) workshop followed by a Pareto Analysis. You know you need to elicit requirements
Let me paint you a picture. Last year, a fintech client was six weeks behind schedule. The developers were building features the business didn't ask for, and the business was demanding reports the database couldn't handle. Do you run a SWOT
Includes: Printable templates, 123 technique cards, and a 30-day implementation challenge. What is the ONE technique you use more than any other? And what is one technique you wish you were better at? Let me know below! A Process Flow