Design Thinking ( 303105152)

UNIT- 3
RAHUL MOUD
Assistant Professor
Dept of AI&DS
 CHAPTER-3

Testing the Solution, Problem Solving Mindset

Why is this unit required?
• This presentation will explore a successful testing approach, demonstrate
the process of gathering and responding to user feedback, and provide an
overview of a problem-solving mindset.
What is Testing?
● Testing, in a general sense, refers to the process of evaluating a
system or component to determine whether it meets specified
requirements or to identify differences between expected and
actual results.
● Testing is a fundamental part of various fields such as software
development, engineering, manufacturing, and product design.
● It helps ensure quality, reliability, and performance of the
product or system being tested.
Types Of Testing:
Testing can be categorized into various types, each serving a specific
purpose. Some common types of testing include:
□ Functional Testing: Evaluating the functions or features of the
system to ensure they behave as expected.
□ Non-Functional Testing: Assessing aspects such as performance,
reliability, usability, and security of the system.
□ Manual Testing: Testing performed by human testers who
execute test cases manually without using automated tools.
□ Automated Testing: Testing conducted with the help of
automated tools and scripts to improve efficiency &
repeatability.
Types Of Testing:
□ Black Box Testing: Testing the system without knowledge of its
internal structure or implementation details, focusing on inputs
and outputs.
□ White Box Testing: Examining the internal structure and code of
the system to ensure thorough coverage of all pathways.
□ Regression Testing: Re-testing the system to ensure that recent
changes or modifications have not adversely affected existing
functionality.
□ User Acceptance Testing (UAT): Testing conducted by end-users
to validate whether the system meets their requirements and
expectations.
Define the steps of a successful testing approach

1. Identify Objectives - what you aim / goal to achieve through testing.

2. Develop Test Plan - Create a detailed plan outlining test cases, timelines,
resources, and success criteria.
3. Prepare Testing Environment - Set up a controlled environment with all
necessary tools and resources.
4. Execute Tests - Conduct the tests as planned and document any issues or
discrepancies.
5. Document Results - Record the outcomes of each test case & start
preparation of result.
6. Analyze Results - Evaluate the data to identify patterns, issues, or areas of
improvement.
Define the steps of a successful testing approach

7. Refine Solution - Make necessary adjustments based on the analysis and

re-test if required.
8. Review and Validate - Conduct a thorough review and validate that all
objectives have been met.
9. Report Findings - Compile a detailed report summarizing the testing
activities, results, and conclusions.
10. Iterate if Necessary- Repeat the testing process with the refined solution if
significant issues are found.
- These steps help ensure that the solution is robust, reliable, and meets the
intended objectives.
How to test a prototype efficiently?
Testing a prototype efficiently involves a strategic approach that
maximizes the effectiveness of the testing process while minimizing time
and resources.
Here are some steps to help you test a prototype efficiently:
□ Define Clear Objectives: Clearly define the goals and objectives of the
testing process. Understand what aspects of the prototype you want
to evaluate, such as functionality, usability, design, or performance.
□ Prioritize Testing Areas: Identify the most critical aspects of the
prototype that need to be tested first. Focus on areas that are
essential for the core functionality or user experience of the product.
How to test a prototype efficiently?
□ Create Test Scenarios and Cases: Develop a set of test scenarios and
cases that cover various use cases and functionalities of the
prototype. Ensure that the test cases are comprehensive yet
manageable, focusing on both typical and edge-case scenarios.
□ Use Testing Techniques Strategically: Choose appropriate testing
techniques based on the nature of the prototype and the objectives of
testing. This could include manual testing, automated testing,
exploratory testing, usability testing, or any other relevant techniques.
□ Leverage Prototyping Tools: Utilize prototyping tools that offer
features for testing and gathering feedback directly within the
prototype itself. This can streamline the testing process and facilitate
collaboration among stakeholders.
How to test a prototype efficiently?
□ Involve Stakeholders Early: Engage stakeholders, including designers,
developers, product managers, and end-users, in the testing process
from the early stages. Their input and feedback can help identify issues
early on and guide iterative improvements.
□ Iterate Based on Feedback: Continuously collect feedback from testers
and stakeholders throughout the testing process. Use this feedback to
iteratively improve the prototype, addressing any issues or
shortcomings identified during testing.
□ Balance Depth and Coverage: Strike a balance between depth and
coverage in testing. Aim to achieve sufficient coverage of different
features and functionalities while ensuring thorough testing of critical
areas.
How to test a prototype efficiently?
□ Utilize Automation Where Possible: Automate repetitive and
time-consuming testing tasks wherever feasible. Automated testing
tools can help increase efficiency and consistency in testing, especially
for regression testing and performance testing.
□ Monitor and Track Progress: Keep track of testing progress, including
test execution, defects identified, and their resolution status. Use
metrics and reports to monitor the effectiveness of the testing process
and make data-driven decisions.
□ Document Findings and Recommendations: Document the findings,
observations, and recommendations resulting from testing. This
documentation serves as a valuable reference for future iterations and
can help communicate insights to stakeholders.
Design a Test sequences:
Test preparation :
□ The best way to start is to define clear-cut learning goals or
hypotheses that we want to test:
○ What do we want to learn?
○ What do we want to test?
○ whom do we want to conduct the test, and where?
□ In the end, the test should show what parts of an idea we should
keep, what we should change, and what we should discard.
□ Before embarking on the actual test series with various users, an
initial test with one person should be carried out to exclude any
errors.
Conducting the test with potential users:
Conducting tests to identify user needs is crucial for designing
products or services that truly meet the needs of your target
audience. Here's a step-by-step guide on how to conduct such tests:
□ Define Your Objectives: Clearly outline what you want to
achieve with the test. Are you looking to understand user pain
points, preferences, behaviors, or expectations? Knowing your
objectives will guide the entire testing process.
□ Identify Your Target Audience: Determine who your users are or
will be. This could involve creating user personas representing
different segments of your target audience based on
demographics, behaviors, and goals.
Conducting the test with potential users:
□ Choose the Right Methodology: There are various methodologies for
testing user needs, including surveys, interviews, usability testing, focus
groups, and contextual inquiries. Choose the one(s) that best align with
your objectives, timeline, and resources.
□ Develop Test Materials: Depending on the chosen methodology,
prepare the necessary materials such as interview scripts, survey
questions, prototypes, or scenarios for usability testing.
□ Recruit Participants: Recruit participants who represent your target
audience. Consider factors like age, gender, occupation, and experience
with similar products or services.
□ Conduct the Test: Carry out the test according to your chosen
methodology. Ensure that participants understand the purpose of the
test and feel comfortable providing feedback.
A/B Testing with the Prototype:
□ One possibility of quantitative testing is to carry out an A/B
comparison. It is especially suitable for simple prototypes and
allows us to test two different versions of a landing page.
□ In the case of a Web site, the titles and descriptions of the offers,
the text volume, style, promotion offers, length of forms, and boxes
can be examined in an A/B test.
□ To achieve relevant test results, it is important for both versions to
be tested concurrently or in tandem and within a predefined,
appropriate time period.
□ The final measurement and evaluation as to which version was
more successful in the test and which one will be used in the real
world must be done on the basis of clearly predefined criteria.
Online Testing :
Online Testing :
□ An extremely simple and effective way of taking many users’
feedback into account is the use of a Web-based tool.
□ Recently, various Software-as-a-Service solutions have evolved,
with which affordable, efficient and Web-based feedback can be
obtained.
□ One great advantage of such a tool is that additional questions can
be asked and there is a great deal of leeway in terms of the makeup
of the community surveyed.
□ The segmentation ensures that the feedback matches the needs
optimally.
□ A tool-supported approach for testing feedback allows you to
obtain structured feedback quickly and easily.
What is the process of gathering feedback of user?
gathering user feedback is not a one-time event but an iterative process
that should be integrated into your product development cycle. Regularly
soliciting and acting upon user feedback can lead to a more user-centric
and successful product.
□ Choose Feedback Methods: Select appropriate methods for gathering
feedback. This could include surveys, interviews, usability tests, focus
groups, feedback forms within the product, social media monitoring,
etc.
□ Design Feedback Instruments: Develop well-designed surveys,
interview guides, or test scenarios to gather relevant feedback. Ensure
that questions are clear, concise, and focused on your objectives.
What is the process of gathering feedback of user?
□ Collect Data: Implement your chosen feedback methods and collect data
from users. Be mindful of user privacy and data protection regulations.
□ Analyze Feedback: Once you have collected the data, analyze it
systematically to identify patterns, trends, and key insights. Look for
common themes and areas of consensus among users.
□ Prioritize Findings: Prioritize the feedback based on its impact on the
product and the feasibility of implementation. Identify low-hanging fruits
as well as more complex issues that may require further investigation.
□ Implement Changes: Use the insights gathered from user feedback to
inform product improvements. Collaborate with relevant teams (e.g.,
design, development, marketing) to implement changes effectively.
What is the process of gathering feedback of user?
□ Iterate: User feedback should be an ongoing process throughout the
product lifecycle. Continuously gather feedback, make improvements,
and iterate based on user needs and market trends.
□ Communicate Updates: Keep users informed about the changes you've
made based on their feedback. Transparency builds trust and
demonstrates your commitment to user satisfaction.
What is the process of gathering and responding feedback of user?
1) Define the problem:
2) User research:
3) Feedback collection:
4) Analysis:
5) Prototype:
6) Feedback:
7) Final design:
8) Implementation:
9) Launch:
How to document the feedback:
Documenting user feedback is essential for keeping track of insights, identifying
trends, and ensuring that feedback is acted upon effectively. Here's how you
can document user feedback effectively:
□ Create a Feedback Repository: Establish a central location where all user
feedback will be stored and organized. This could be a spreadsheet, a
dedicated feedback management tool, a CRM system, or even a shared
document.
□ Capture Feedback Details: Record all relevant details of the feedback,
including the source (e.g., survey, interview, support ticket), date, user
demographics (if applicable), and the specific feedback provided.
□ Categorize Feedback: Group similar feedback together to identify common
themes or issues. Use categories or tags to organize feedback by topic (e.g.,
usability, feature requests, bugs).
How to document the feedback:
□ Prioritize Feedback: Assign priority levels to each piece of feedback based on
factors such as the severity of the issue, the number of users affected, and
the potential impact on the product.
□ Provide Context: Include any additional context or background information
related to the feedback. This could include screenshots, user quotes, or
descriptions of the user's workflow or experience.
□ Quantify Feedback: Where possible, quantify the feedback by tracking
metrics such as the frequency of occurrence, the percentage of users
affected, or the severity of the issue.
□ Track Status and Resolution: Document the status of each piece of feedback
(e.g., open, in progress, resolved) and track the actions taken to address it.
Include details of any updates, fixes, or improvements made in response to
the feedback.
How to document the feedback:
□ Share Insights: Regularly review and analyze the feedback to identify trends,
patterns, and actionable insights. Share these insights with relevant
stakeholders, such as product managers, designers, and developers.
□ Communicate Changes: Keep users informed about the changes made in
response to their feedback. Provide updates through release notes, blog
posts, or direct communication channels.
□ Iterate and Improve: Continuously refine your feedback documentation
process based on user needs and internal feedback. Solicit input from team
members to identify areas for improvement and implement changes
accordingly.
HOW MIGHT WE...conduct and document experiments in a structured way?
□ During the early phases of the innovation process, we frequently test several
assumptions concurrently and learn on several levels.
□ However, we recommend that you reflect before each test on what exactly
you would like to learn and what the key question is.
□ In the early phases of the innovation process, the prototypes are normally
very simple. Often, several variables are tested at the same time.
□ For the testing in later project stages, other types of experiments with
customers (e.g., online tests, A/B testing, etc.) can be conducted.
□ Here we usually focus on a single test variable or assumption.
□ It is of great importance that all tests/experiments be well defined.
□ Documentation helps when tracing decisions later or showing an investor
the success of an MVP (Minimum Viable Product).
HOW MIGHT WE...conduct and document experiments in a structured way?
□ A simple experiment grid helps to structure the experiments and can be
used to document the learning progress.
□ We want to learn as quickly and cost-effectively as possible; this is why we
think about how the test (or the experiment) could be conducted in half the
time and with half the resources.
□ The “experiment grid” helps define and document the tests/experiments:
□ In a next step, we define what we want to measure and which data should
be collected. Then, we determine the criterion that shows whether we are
on the right (or wrong) track. Finally, we carry out the experiment and
document our learnings, such as with photos or videos.
□ At the end, we note the insights gained, the conclusions drawn, and what
measures we will undertake.
□ The tests/experiments must be well documented.
HOW MIGHT WE...conduct and document experiments in a structured way?

Feedback Capture grid:

PROBLEM SOLVING MINDSET
Understanding problem statements:
Understanding problem statements is essential for effective
problem-solving and decision-making in various domains, including
business, technology, and academia. A problem statement defines the issue
or challenge that needs to be addressed and serves as a guide for
developing solutions.

By understanding problem statements effectively, individuals and

organizations can develop informed strategies, make evidence-based
decisions, and implement effective solutions that address the root causes
of problems and drive meaningful outcomes.
PROBLEM SOLVING MINDSET
Understanding problem statements:
Recapping Design Principles
A. Balance:
B. Movement:
C. Proportion or scale:
D. Alignment:
E. Contrast:
F. Emphasis:
G. Repetition/Pattern:
H. Unity:
Design thinking tool-sets:
- Take the best and reinvest the rest: To optimize your Design Thinking tool
set, focus on selecting the most effective and versatile tools while
remaining open to experimentation and adaptation.
a) Building an innovation brand:
b) Rallying people around real problems:
c) Harnessing the energy of early adopters:
d) Relation to Early Wins:
e) Get out of the way:
Design thinking tool-sets:
Formulating approaches to Solutions
Applications of Design Thinking: Case Study
1. Apple – iPhone (Application of Design Thinking):
- Empathy with Users:
- Innovative Ideation:
- Prototype Iteration:
- Attention to Detail:
- Outcomes:
2. Oral-B - Electric Tooth brush (Application of Design Thinking):
- User-Centric Design:
- Innovative Features:
- Prototype Testing:
- Accessible Design:
- Outcomes:
Applications of Design Thinking: Case Study
3. Uber Eats - Food Delivery Platform (Application of Design Thinking):
- Understanding User Needs:
- Streamlined Ordering Process:
- Efficient Delivery Network:
- Continuous Improvement:
- Outcome:

- In each of these case studies, Design Thinking principles have played a

pivotal role in understanding user needs, generating innovative solutions,
iterating on prototypes, and delivering products and services that provide value
and delight to users.
References

https://en.wikipedia.org/wiki/Public_domain
https://www.copyrightlaws.com/what-is-the-public-domain/
https://sourceforge.net/
https://www.apache.org/
www.paruluniversity.ac.in