Understand is where we do user research. The goal is to understand the people that will use the product. We gather information about the context of the product’s use, the motivations that will lead users to the product, and many other socio-economic details.
This information allows us to build a design specifically for them. We start off by defining the user's personas, their requirements from the system, and any limitations they might face. With this understanding, we are able to constantly evaluate our designs against the user's needs.
Understand is where we do user research: defining personas and system requirements.
Build is where we design and build solutions based on our understanding of user data. We start off with wireframes to allow us to focus on the experience and make sure that the user’s goals are met first. Visuals (color, typography, textures, images) come after.
Building in this way ensures that we’re staying true to the user needs outlined in the previous stage. Depending on where the product is in its lifecycle, this stage can involve different parties: UX designers to think through user flows, visual designers to build wireframes and mockups, and engineers to make those come to life.
Build is where we design and build solutions based on our understanding of user data.
Throughout the product’s lifecycle, we Measure what we’ve built. We do that through user testing, leveraging different tools that give insight into product usage, and maintaining a continuous feedback loop with the users.
We test with real users to evaluate their understanding of the product, their current pain points, and how effectively they use the system. There’s a variety of testing services that scale as the product grows and iterates: stakeholder and user interviews, prototype testing, user acceptance testing, and continuous usability testing are a few examples.
Measure is where get feedback and test to see the usage and effect the solution has on the users.
Next we Learn from the data collected through user testing. This allows the users to guide our decisions on what core features to prioritize and ensures we’re making data-based business decisions about what to do next.
Comprehensive debriefs allow us to track the record of user issues and what they want out of the products. Once we’ve taken the time to learn, we start the process over again.
We learn from what we've measured and use the data to make informed decisions about what to do next.
Understand is where we do user research. The goal is to understand the people that will use the product. We gather information about the context of the product’s use, the motivations that will lead users to the product, and many other socio-economic details.
This information allows us to build a design specifically for them. We start off by defining the user's personas, their requirements from the system, and any limitations they might face. With this understanding, we are able to constantly evaluate our designs against the user's needs.
Understand is where we do user research: defining personas and system requirements.