How to elicit Software Requirements (a DIY guide)

Product & Role
UX Designer for client portal Saas — process on reducing risks associated with software requirements
Challenges
Clients (and Sales) failing to understand why Discovery efforts are needed.
Achievements
Finding out fast (one meeting vs one week) if stakeholders have budget for Discovery efforts.
Challenge
Clients building a product for the first time fail to understand why a Requirement stage is their best insurance against multiple types of risks, so they usually ask the software company to cover costs for any Discovery efforts.
Solution
Six slides explaining risks, the discovery process, outcomes, timelines, activities and costs. The big idea: these efforts are best insurance against risks. For clients lacking a budget, the presentation includes a brief guide on how to DIY.

Step 1/3 — projects risks and the best process to reduce them

Step 2/3 — Who+What+When (clarifying key users, their goals and how to achieve them)

Step 3/3 — sketch all interactions and test them with a workshop

Achievements

Translating the complex process of eliciting requirements into a simple 3-step process. Encouraging prospects and stakeholders to empathize with their users when writing requirements. Finding out immediately if prospects are willing to pay to reduce future risks.

Work

Opinion

What the gorilla video tells us about what we choose to perceive

Stop explaining UX to 5-year olds

AI, confabulating and consciouesness

Why Agile stories work for all your teams

Get out of UX / UX everything

AI, confabulating and consciouesness

Why Agile stories work for all your teams

Stop explaining UX to 5-year olds

Contact

Let’s make a better world for your clients experience and your business outcomes. Write me at  contact at mariusgrigore.com to get in touch.