I have been using the “jobs to be done” framework to assess how critical specific tasks are for the stakeholders.
Usually a successful outcome of the process leads me to identifying a set of environmental/situational triggers that cause a lot of adrenaline/anxiety/fear in the subject I am interviewing.
Once you have identified that triggers, the easy thing to do is to build the metaphorical button (your solution) subjects can press on to alleviate their anxiety/fear and in the process release some dopamine.
Based on past experiences building out GetData.IO, the simpler the button (ideally a BIG RED one saying PRESS HERE) the better.
This lessens the level of cognitive load and time required to trigger off some dopamine in their brain. It’s also very conducive for habit forming purposes.
From a technical stand point, simpler solutions are cheaper to build and less of a nightmare to maintain. It means you don’t have to pay a tonif money to hire a rockstar engineer and can easily find a regular (or even entry level) engineer to deliver the solution. It also means scaling up your engineering team becomes easier later on as the recruitment criteria does not need to be as strict.
Some related materials you might want to consult:
- Pavlov’s Dog, Ivan Pavlov
- Hooked, Nir Eyal
- The Fogg Model, BJ Fogg
- The nature of technology, Brian Author
- The buyer personas, Adele Revella