Lean Design is focused on rapid iteration and problem based design. Ultimately, we are trying to solve problems for the users. This framework can help.
Ideas are usually disguised as feature requests and have hidden assumptions.
“We need a search box for reason/sub-reason”
This assumes all the reasons make sense and that we just need to give the tech easier access to them.
Instead, break requests into problem statements that can be solved individually:
Tech’s are having difficulty matching the customer problem with an available reason.
Tech’s are having difficulty finding existing reasons.
Form a Hypothesis
If we do this thing we think we’ll get this result.
A hypothesis is a design that addresses an issue and can be validated:
By adding a search box to the reason panel, we think we’ll decrease the amount of time spent on selecting a reason.
We only care about validating the hypothesis. This requires identifying how we will measure it. As long as it's quantifiable and accurately measures the activity we are attempting to impact, it is right.
Ways We Can Measure Results (For this example):
Total amount of time spent interacting with the reason module. Can be measured using events sent to mix panel.
Iteration allows for constant improvement. The faster you can see the results of a feature in a live environment, the quicker you can identify areas of improvement.