Test-driven methodology in product design | by Michael Gearon | Medium
Test-driven development or TDD is a methodology on improving the delivery from concept to deployment in the most efficient way. There’re plenty of buzzwords out there at the moment but strip it all back we are just trying to find a way develop software in the most agile way.
Taking the TDD methodology we are going to modify the name a tad and change it to test-driven product design but still very much on the same lines.
TDPD Life Cycle
First of all, what is TDD?
Test-Driven Development (TDD) is a process for developers to write the test cases for features before coding and building the feature. You breakdown all of the actions a user will take from start to finish. By following this test first approach a developer understands what they are building for and focuses on the product requirements.
What is TDPD?
Similarly to the TDD approach, for test-driven product design the idea is to test first. At the start of any project everyone has their own ideas, hypothesis and theories on what will improve the UX of the website or app.
The only way to objectively decide on what is the best approach is to ask the customer. In a test-driven product design world we’d have the following stages:
Outcomes, assumptions and hypothesis
Design and prototyping
Create the minimal viable product for testing
Research & learning
Repeat the cycle
Outcomes, assumptions and hypothesis
The first part of the cycle is the hypothesis, this should be a clear vision of what we are trying to achieve. It shouldn’t be a wishy-washy statement like “we want to create a new landing page” instead set some clear goals such as “we want to improve click through rates on our landing pages by improving the mobile experience”. The key to this part is minimal documentation, you want to get your ideas out to the customers as soon as possible
July 27, 2022 at 10:22:05 PM UTC
- permalink
-
-
https://michaelgearon.medium.com/test-driven-product-design-982be674b7ca