---
# System prepended metadata

title: Well Designed-Book Summary
tags: [Example to use]

---


# Well Designed-Book Summary



### Behavioural Insight
> Observing human behavior in real time is the key to arriving at a product innovation that will drive engagement. This is different from observing or hearing about human behavior in retrospect, in general, or in hypothetical. You aren’t conducting interviews or focus groups, which tend to discuss what people might do, ought to do, or typically do. Instead, you are watching what people actually do.

# Design Strategy

A “design strategy” is a long-term plan that’s focused on **how best to tame technology.** The playbook for your design strategy describes a path toward realizing the **value proposition of padawan.**

In this case our product strategy describes a test wallet  that trains, empowers  people to interact with bitcoin and know it's WHY, WHAT and HOW of the technology.

:::info
Design strategy is a form of storytelling. It is a set of stories that progresses as your products and services progress, and illustrates the value proposition you're offering.
:::

A design strategy takes three artifacts—an emotional value proposition, a concept map, and a product road map—and combines them into a single tool. 

## Value proposition
A value proposition is a promise to produce value for a customer. The promise is communicated to customers comprehensively; it’s both explicit in the value line and also implicit in the design decisions that define and shape the product.

To understand your value proposition, ask—and answer—this ***value question***: 
- what can someone do ***after*** using or acquiring your product that he/she couldn’t do ***before*** using or acquiring your product?
	- ==**Answer:** Emma now knows what & why bitcoin. She can find her way to get answers for any doubts she has about bitcoin. She can now confidently explain to people how to use a bitoin wallet.==

### Emotional value proposition
To begin to understand the **emotional connection between a product and a person**, think about feelings, aspirations, desires, and dreams. Ask this ==revised question:== 
- what can someone ==feel after== using or acquiring your product that he couldn’t ==feel before== using or acquiring your product?
	- Answer: Visual Answer-meme that shows the before and the after.
		-  Straight Forward answer: Feels confident(Empowered) after using Padawan wallet.
 >**Joe’s value proposition is stated like this:**
*After using LiveWell, people can better track the way they feel throughout the day and connect those feelings to events or activities in their lives.*
**Joe’s emotional value proposition is stated like this:**
*After using LiveWell, people will feel more connected with their body rhythms and will feel more in control of their mental health.*
###### tags: `Example to use`


### Developing a Product Stance
Product stance is the attitude your product takes, its personality. Stance is manufactured and designed, and from a particular product stance flow features, functions, language, imagery, and other formal design qualities.

It can evolve from an existing brand language, or it can be created from scratch. Product stance can evolve from an understanding of users, from an understanding of market, or from the attitude and approach of an individual designer. ==Product stance is about feelings.==

 ...you frame the relationship between a person and your product as a *dialogue* rather than a *monologue.*

>Padawan wants to be supportive, human-like, warm, dependable, empowering and eduacative.

Translating these traits into emotional requirements:
* Padawan Wallet will converse with the user in chatty, natural, conversational language. 
* Padawan Wallet will anticipate where users have doubt on bitcoin and find way to explain in simple clear term with analogy.
* Padawan Wallet will always be affirming.

**Master Yoda Personality(you can explore other Jedis too):** 
Peace, wisdom, the Force, the light, his students succeeding, his friends, animals, nature, hope, Jedi.


## Frame & Play(Define and Ideate)

**Here are insights i identified based on my research:**
1. People have doubts about bitcoin as a result of it's complexity.
4. Hard to make the transtion between fiat and bitcoin.
5. People need to feel related to others who use BTC.
6. Tense Onboarding
7. Complexity of the backup Process.  Why? how can it be simplified without compromising security
8. Transaction fees, Address validation

**The Goal/solution to each of these can be:**

#### 1. People have doubts about bitcoin as a result of it's complexity.
- Goal: Explaining bitcoin. 
Some interactions that support the goal of *explaining bitcoin* includes:
	* 	Read about the bitcoin in plain and simple language.
	* 	Use real world analogies to explain complexities.
	*	Discuss complexities with other people.
	* 	Feel in control.
	
	
#### 2. Hard to make the transtion between fiat and bitcoin.
- Goal: How to get into the bitcoin sphere using fiat  
Some interactions that support the goal of *How to get into the bitcoin sphere using fiat:
 	* Suggest exchanges and wallet services.
	* A simple explaination(with illustration) of the user flow of how an exchange is done and how it is to be transfer to a wallet.

#### 3. People need to feel related to others who use BTC.
- Goal: Be that friend  
Some interactions that support the goal of *Being that friend* includes:
	* Changing the scary Bitcoin narrative that makes users afraid and almost in a mindset that they will make a mistake. 
	* Make user feel welcome. Make onboarding exciting(like a friend visiting home)
	* Suggest where to find answers by recommeding communitites.
	
	
#### 4. Tense Onboarding
- Goal: Calm Users down. Encourage User!  
Some interactions that support the goal of *Calming Users down* includes:
	* Be  their no fan 1 
	* You’ve done it before! You can do it again. Remind them that they’ve done all of this incredible stuff before, so this time will be no different.
	* Yes your feelings are valid. Bitcoin is hard to understand, that's why i'm here for you, I gotchu.
		
	
#### 5. Complexity of the backup Process. Why? how can it be simplified without compromising security
- Goal: Show backup in a useful and timely manner  
Some interactions that support the goal of *explaining bitcoin* includes:
	* Explain the backup process, lead users through the exercise/tutorial of a  backup 
	* Make user feel welcome. Make onboarding exciting just
	* Suggest where to find answers by recommeding communitites.
	

#### 6.Transaction fees, Address validation
- Goal: Inform/Educate users about transaction fees and how to validate address  
Some interactions that support the goal of *Inform/Educate users about transaction fees and how to validate address* includes:
	* Communicate this intrinsic usability feature(Checksum Validation) of Bitcoin to many users. 
	* Explain transaction fee and how they can see it.
	
	
	
what are real life analogies to all this above and how were they solved. Then steal the ideas liberally and repurpose them in the new context
 
**Next, think about a comparable and analogous situation that has nothing to do with health care. In what other situations are all of these qualities true?**

 - Remember to [do something] each day.
 - Feel confident of progress being made.
 - Check in with a professional occasionally.
 - Read about [the situation] in plain language.
 - Discuss complexities with other people.
 - Feel in control.
 
# Sketches 
![](https://i.imgur.com/s0RoqsK.png)
*example for use in case study- From linkedin learning, sketching for ux designers.*

# Crafting out the Product details - Product Vision