UX Frameworks are methods to help us build better digital products.
I come from an art and graphic design background, that type of schooling helped me get ideas from different sources, sometimes that means making ideas out of old ones. On other occasions, I get that “Eureka” moment, like Archimedes who ran throughout the city naked when he discovered that the spelled water volume is equal to his body’s volume. Just like Archimedes
I want to develop my ideas into useful and valuable products, that solve our customers’ problems.
I am an advocate of the “Design School” of thought, where User Experience is identified as the process of satisfying “user’s” personal or/and business “needs” using “design”. In My Opinion User Experience can be briefed into:
User’s Needs + Process + Design + Context(environment) + Time + Business goals
Traditionally, building digital products required product owners/designers to deliver the following:
- User Personas, stories, and Scenarios (User + Task + Environment).
- Taxonomies (Vocabulary used in a product)
- Content/Copy strategies.
- Wireframes, UI elements, and mockups.
- Usability test plans & results.
- Refined prototypes.
Delivering those elements meant spending a fair amount of time, as each one of those items marched as an independent entity. Leading design agencies such as IDEO figured out the need to build organized UX frameworks to manage those elements, therefore they standardized their human-centered design approach.
IBM innovated their Design Thinking Framework, where they took the same approach as IDEO of phasing the product development process. Both of those organizations are the leaders in educating and training designers.
To showcase how those frameworks work, I will discuss IDEO’s human-centered design approach which seeks balancing user needs with business expectations using design. IDEO phased the design process into:
- Rapid prototyping
- User feedback
Those processes help product designers to empathize with users, define the problem, and prototype solutions.
UX Frameworks in use
Besides IBM’s and IDEO’s frameworks there are some frameworks that work depending on the product phase you are at:
- TARI (Trigger, Action, Reward, Investment)
- USMO (User, Situation, Motivation, Outcome)
- JTBD (Jobs To Be Done)
- BASIC (Beauty, Accessibility, Simplicity, Intuitiveness, Consistency)
- HEART (Happiness, Engagement, Accessibility/Adoption, Retention, Task Success)
Using these frameworks to build customer-centered products is very important because it emphasizes on the user needs during different stages of product building. They helped us align business goals with customer needs. Personally, I do not want to build a product that does not solve the user’s needs.
At the end of the day, what decides if a product is successful or not is if the product actually meets the user’s needs and achieving the business goals at the same time which governed mainly by user experience.
If you enjoyed this article you could also enjoy my other article discussing tools I used to conduct UX research.