CHARACTERISTICS OF GOOD SOLUTIONS
What the goals are?
In design thinking, these characteristics of a good solution apply, no matter what your particular situation or set of users. A good solution:
What the goals are?
In design thinking, these characteristics of a good solution apply, no matter what your particular situation or set of users. A good solution:
- Has a purpose: You always start with a problem that needs solving and you arrive at the solution using the design thinking process. You are not using design thinking to figure out who may benefit from solution you already have. In other words, design thinking isn't meant to work backward from solution to problem.
- Is useful: The solution fulfills its intended purpose.
- Is understandable: A good solution should be easy to understand or learn. Or, the work to learn the solution should be worth the effort.
- Is honest: A good solution does not promise more than it provides.
- Is sustainable: A good solution does not adversely affect the environment, nor does it require resources (whether material or personnel) in a way that can't be maintained over time.
- Is long-lasting: Make sure the work you put into the design thinking process is worth it. Provide a solution that does not break often or deteriorate quickly.
- Fits to the context: A good solution makes sense for the location it is used in, the people who use it, and the function it was meant to perform.
- Is compelling: It should resonate with the user by making them feel confident when they use it. They should want to use your solution.
- Is simple: The solution should include only those elements necessary for fulfilling the rest of the criteria in this list.
Qualities Needed in Design Thinking
CREATING A DESIGN BRIEFYour goal for the research stage should be to emerge with a clear problem definition. Some companies ask their design teams to create a design brief.
A design brief is a document that summarizes all user requirements following an extensive research stage and provides a thorough description of the problem the team is being asked to solve. Design briefs are useful for team members and stakeholders and can be adjusted over the life of the project to reflect new understandings.
Design briefs generally contain the following elements...
The brief is often used as a set of criteria to evaluate solutions as they are being developed. It can also be used after a solution is achieved to determine how the project met schedule, budget, and other expectations.
Whether you create a design brief or not, you should at least have multiple sources of data for each of the bulleted items in the list we shared above.
Strong research provides support for the important work to come. The reframing of the problem definition and creation of the design brief is critical, as it directs the next stage of teamwork, ideation and synthesis. Ideation that is based on an inaccurate or misleading problem definition will result in solution choices that are not in line with stakeholders' interests. Join us next week to learn about the ideation stage.
A design brief is a document that summarizes all user requirements following an extensive research stage and provides a thorough description of the problem the team is being asked to solve. Design briefs are useful for team members and stakeholders and can be adjusted over the life of the project to reflect new understandings.
Design briefs generally contain the following elements...
- A summary of the research that includes, but is not limited to:
- User characteristics
- User needs and desires
- User context
- Any user personas that you have developed
- Technology possibilities and feasibility
- Business options and viability
- Inspirational and competitive benchmarking
- A reframed problem definition
- The scope and deliverables of the project, including:
- Requirements for functionality, aesthetics, and what will be appealing to users
- Project timeline
- Budget
- Other business requirements, such as existing or future product-line needs
The brief is often used as a set of criteria to evaluate solutions as they are being developed. It can also be used after a solution is achieved to determine how the project met schedule, budget, and other expectations.
Whether you create a design brief or not, you should at least have multiple sources of data for each of the bulleted items in the list we shared above.
Strong research provides support for the important work to come. The reframing of the problem definition and creation of the design brief is critical, as it directs the next stage of teamwork, ideation and synthesis. Ideation that is based on an inaccurate or misleading problem definition will result in solution choices that are not in line with stakeholders' interests. Join us next week to learn about the ideation stage.
Concepts need to always fit at least 2 of these circles. Ideally, they should be in a balance in all three areas of this Venn diagram.
6 Tips for Prototyping a Service
1. Identify the steps that matter
What are the most important milestones in the journey? It’s not realistic to make a series of moves and be always right at everything all the time, so it’s critical to identify those points in the project (or product) to focus on and nail it. This a good method to stay on target and keep priorities in the right order of importance. How to pinpoint the elements that matter?
- Understand and Empathize on what’s important to the End-Users, in the daily use of the product or service.
- Simulate real situations or spend time and observe users while utilizing the product/service, understanding what excites or annoys them. Take cues from the ways people are handling your product/service.
- What Personas(*) are you prioritizing as hypothetical ideal users?
- Be Critical, distinguish between what's realistic and what is aspirational and focus on what's possible in the version 1.0 and postpone the development op aspirational-but-not-possible options, which may just need to be developed over time in the version 2.0 .
2. Be aware of early indicators
Simply, making rough mock-ups to achieve specific small goals is a good start. Hints that something is not ideal now but can definitely improve later is essential to progress towards a final result, yet staying on budget with prototyping development. Always, document every step of the process and gather evidence to substantiate your scope.
3. Tap the creative human potential
Rely on the instincts and insights of the people. Direct observation of users in the act of handling the product is key to verify the product /service really works.
4. Use time-based logic
Imagine and simulate the entire arc of the user experience over time. Try to visualize every possible aspect of the use of your product/service in any condition.
5. Involve the user in the design process
Make as many users among friends and family, to participate and give inputs. Initial Low Fidelity prototypes can be extremely helpful so the user can contribute with some feedback, instrumental to the design. Ask people to think about all the kinds of interactions they can play with.
6. Use constraints to think out of the box
Push beyond the ordinary, default use of your product/service. Assume non designated or habitual users of your product. What about if the user is a disabled person or just an elder or a child.