vs UX Design vs Design Thinking Design Process at Triveous 1 What can you do with it? Problems you can solve Common Mistakes you can avoid Agri-Tech Case Study 2 Design Process Understand Define Ideate Prototype Test 3
For Startups Soham is the Founding Partner at Triveous and brings over 14 years of experience in building and servicing products across sectors like finance, entertainment, education, healthcare among others. He is also a Lead Anchor Mentor at the “Google For Startups” accelerator program where he has mentored startups from across the world on their design and product strategy. https://www.linkedin.com/in/sohammondal/ https://twitter.com/s0h4m About Associations
state-of-the-art micro ATM (any Kirana store owner can act as an ATM teller using their mobile phone) and POS solutions for the underbanked sections of India. EnParadigm and Google Worked with Enparadigm on multiple offline first apps in the insurance and education space. Worked with Google on multiple initiatives in the User Experience and Android Application space. About
profit backed by Google and Tata Trusts. Worked on designing and developing an offline first application to generate livelihood for over 80,000 women in 300,000 villages across India. Worked with IDEO on a design framework for new internet users. Google Research and WHO Worked with Novopay on multiple financial applications impacting millions of users across India. Worked on state of multiple state-of-the- art products in health, creator economy, recruitment and agri-tech. Worked with Google AI on an product used for clinical research Worked with WHO team members across 4 timezones on a dashboard for readiness intelligence and awareness.
the market, ecosystem, stakeholders or product Define Analyse the data, define pain points and needs, artefacts like persona or jobs-to-be- done Process
direction to the solution Prototype Prototype solutions, fail fast, iterate quickly Test Test with stakeholders, fail fast, iterate quickly Design Process at Triveous Solution Domain Process
Not talking to users quickly enough, early enough or frequently enough 04 Not Defining Users/Jobs-to-be-done/Needs Not defining the opportunity, users and their needs/jobs 03 Not Understanding Stakeholders/Market/Ecosystem Have a limited understanding of the market, ecosystem and the various stakeholder 02
that assist in the direction of the startup/product 06 Measurement: Too little or too much Not measuring at all or measuring too little or too much. 05
share assumptions and risks early in the startup journey. 07 Delay Validation of Assumptions and Risks Validate these Assumptions and Risks as easily and quickly as possible 08
Cycle 08 Delay Validation of Assumptions and Risks 05 Measurement: Too little or too much 01 Not Understanding The Problem 07 Not Defining Assumptions and Risks 02 Not Understanding Stakeholders/ Market/ Ecosystem 03 Not Defining Users/Jobs- to-be-done/ Needs 06 Analysis: Not analysing data properly
the product 02 Not Understanding Stakeholders/ Market/ Ecosystem 03 Not Defining Users/Jobs- to-be-done/ Needs 04 Not Talking to Users/Proper Feedback Cycle 01 Not Understanding The Problem
the market, ecosystem, stakeholders or product Define Analyse the data, define pain points and needs, artefacts like persona or jobs-to-be- done Process
you to understand what your users actually need and how the market is like - Good research informs your product, and the fact that it comes early in the design process will save you a lot of resources(time and money) down the road - Plus, with solid research, selling your ideas to stakeholders will be a lot easier. DETAILS 07 Not Defining Assumptions and Risks 08 Delay Validation of Assumptions and Risks 02 Not Understanding Stakeholders/ Market/ Ecosystem 01 Not Understanding The Problem Understand
- Who are your competitors? - Who are the important stakeholders? 01. Qualitative Research - What do users need? - What are their goals and aspirations? - What are the challenges users face? 02. Quantitative Research - How to confirm or reject certain hypotheses? - Statistical analysis of data 03. Understand
app’s purpose isn’t always readily apparent. Activation: Primary goal of onboarding Before they achieve action, users are - Trying out the product - Understanding the value proposition, features - Determining if it is a good fit for them Activation is the point at which users "get your product and its value proposition" Complexity: Users will abandon the signup flow if it becomes overwhelming. Assistance: Asking for help isn’t always easy. Language: Is this app or its content relevant to me Understand
action in the product 02 Feel Feel happy, confident, connected 03 Believe Believe the product is relevant to me 04 Activation or a Revelation Activation is when people get the value proposition of your app - Understanding value proposition - Relevance to the user Activation Steps Understand
the market, ecosystem, stakeholders or product Define Analyse the data, define pain points and needs, artefacts like persona or jobs-to-be- done Process
Not Understanding Stakeholders/ Market/ Ecosystem 01 Not Understanding The Problem 03 Not Defining Users/Jobs- to-be-done/ Needs 05 Measurement: Too little or too much 08 Delay Validation of Assumptions and Risks
direction to the solution Prototype Prototype solutions, fail fast, iterate quickly Test Test with stakeholders, fail fast, iterate quickly Design Process at Triveous Solution Domain Process
the design space. Scamper Question problems through action verbs (“Substitute”, “Combine”, “Adapt”, “Modify”, “Put to another use”, “Eliminate”, “Reverse”) to produce solutions. Crowdstorming Target audiences generate and validate ideas through feedback (e.g., social media) to provide valuable solution insights. Crazy 8s Force people to come up with 8 ideas in 8 mins Mindmapping Use this graphical technique to connect ideas to problems’ major and minor qualities. Brainstorming Build good ideas from each other’s wild ideas, can be done individually or in groups
direction to the solution Prototype Prototype solutions, fail fast, iterate quickly Test Test with stakeholders, fail fast, iterate quickly Design Process at Triveous Solution Domain Process
the market, ecosystem, stakeholders or product Define Analyse the data, define pain points and needs, artefacts like persona or jobs-to-be- done Process
direction to the solution Prototype Prototype solutions, fail fast, iterate quickly Test Test with stakeholders, fail fast, iterate quickly Design Process at Triveous Solution Domain Process
Cycle 08 Delay Validation of Assumptions and Risks 05 Measurement: Too little or too much 01 Not Understanding The Problem 07 Not Defining Assumptions and Risks 02 Not Understanding Stakeholders/ Market/ Ecosystem 03 Not Defining Users/Jobs- to-be-done/ Needs 06 Analysis: Not analysing data properly
soham
hiro93n
lynteo
designer_no_pon
klemens
xtone
payatsusan213
hjmkth
shotamatsuo
keroyama
saka2jp
kenichiota0711
centou
dougneiner
tammyeverts
aleyda
panda_program
stephaniewalter
mclloyd
codingconduct
keithpitt
skipperchong
marketingsoph
.png){kind=avatar}
helenjbeal
![Connect With Soham Email [email protected] https://triveous.com/ Social https://www.linkedin.com/in/sohammondal/ https://twitter.com/s0h4m Details](https://files.speakerdeck.com/presentations/fa7f2b2554894f2e9e9bb3304ecc86f3/slide_68.jpg){kind=link}