Liking: Why We Say Yes to People We Like skill

People prefer to say yes to individuals they know and like.

by wondelai·MIT license·★ 2,235 Stars on the repo·GitHub ↗

Use now

Files of Liking: Why We Say Yes to People We Like

wondelai/main1 file
liking.md
Show the full text276 lines

Liking: Why We Say Yes to People We Like

People prefer to say yes to individuals they know and like. This seemingly obvious principle has profound implications for product design, brand building, and marketing. Liking isn't just about being pleasant; it's a systematic set of factors that can be deliberately designed into every customer interaction.

This reference covers the six factors of liking, brand voice and personality guidelines, rapport-building in digital products, personalization strategies, the halo effect in visual design, community building, and detailed tone guidelines with before/after examples.

The Six Factors of Liking

1. Physical Attractiveness (The Halo Effect)

Mechanism: Attractive people (and by extension, attractive products and websites) are automatically assumed to be smarter, more competent, and more trustworthy. This is the "halo effect," where one positive trait colors our perception of everything else.

Application to digital products:

Element Low Liking High Liking
Visual design Cluttered, dated, inconsistent Clean, modern, polished
Photography Generic stock photos Custom, high-quality imagery
Typography System fonts, poor hierarchy Thoughtful type selection and spacing
Animations Janky or absent Smooth, purposeful micro-interactions
Color Clashing or dull Harmonious, intentional palette

Key insight: First impressions form in 50 milliseconds. Visual attractiveness is the fastest path to initial liking, and it colors every subsequent interaction.

2. Similarity

Mechanism: We like people who are like us, who share our values, background, interests, or circumstances. Similarity creates an unconscious sense of kinship and trust.

Application strategies:

Similarity Type Implementation Example
Demographic Show diverse team that mirrors audience Team page with people who look like users
Experiential Share origin stories that resonate "We were frustrated founders too"
Values State values explicitly and live them "We believe in privacy. Here's our code."
Language Use the words your audience uses Developer tool using developer jargon appropriately
Aesthetic Design for cultural context Different visual styles for different markets

Copywriting for similarity:

  • "We built this because we had the same problem"
  • "As a [identity], you know that [shared experience]"
  • "We're founders building for founders"
  • Mirror the audience's vocabulary, tone, and communication style
3. Compliments

Mechanism: We like people who say nice things about us, even when we suspect the compliments are not entirely sincere. Flattery works because we want to believe good things about ourselves.

Application strategies:

Context Compliment Effect
Onboarding "Great choice! You clearly value [quality]" Validates the decision to sign up
Feature use "Nice work! You're ahead of 80% of new users" Encourages continued engagement
Purchase "Excellent taste. This is our most popular [item]" Reinforces the buying decision
Content "You're clearly someone who takes [topic] seriously" Validates the reader's identity
Support "That's a really smart question" Makes the user feel valued

Rules for effective compliments:

  • Tie the compliment to something the user actually did (not just flattery)
  • Be specific rather than generic ("Your project setup is really thorough" > "Great job!")
  • Don't overdo it; one well-placed compliment is more powerful than constant praise
  • Make it about their quality, not your product ("You have great taste" > "Our product is great")
4. Cooperation

Mechanism: We like people who work with us toward shared goals. Cooperation signals that we are on the same team, creating a collaborative bond that increases trust and liking.

Application strategies:

Context Cooperation Signal Example
Product framing "We" language "Let's build your first project together"
Support Problem-solving partnership "Let me help you figure this out"
Feature design Co-creation tools User feedback boards, feature voting
Pricing Flexible, fair pricing "Pick what works for you"
Updates Shared roadmap "Here's what we're building next, based on your feedback"
5. Familiarity

Mechanism: Repeated, positive exposure increases liking. We prefer things we've seen before, even if we don't consciously remember seeing them. This is the "mere exposure effect."

Application strategies:

Channel Familiarity Builder Frequency
Email Consistent newsletter with recognizable format Weekly
Social media Regular posts with consistent visual identity Daily
Retargeting Display ads with brand elements (not hard sell) Controlled frequency
Content Blog posts, podcasts with consistent voice Weekly
Product Consistent UI patterns and brand experience Every interaction

Key insight: Familiarity requires consistency. Changing your brand voice, visual identity, or messaging frequently prevents familiarity from building. The most liked brands are the most consistent.

6. Association

Mechanism: We like things associated with other things we already like. This is why product placement works, why celebrities endorse products, and why brands sponsor events.

Application strategies:

Association Type Implementation Example
Positive emotions Associate product with good feelings Lifestyle imagery, aspirational content
Success Connect to successful outcomes "Used by companies that grew 10x"
Innovation Associate with cutting-edge tech "AI-powered", integration with trendy tools
Causes Support causes your audience cares about "1% of revenue goes to [cause]"
Aesthetic Visual association with premium brands Apple-like minimalism, luxury design cues

Brand Voice and Personality Guidelines

Defining Your Brand Personality

Use this framework to define a consistent brand voice:

Dimension Spectrum Example Brands
Formal <-> Casual Choose where you sit Formal: McKinsey. Casual: Mailchimp
Serious <-> Playful Match audience expectations Serious: Stripe. Playful: Slack
Expert <-> Approachable Balance credibility and warmth Expert: IBM. Approachable: Basecamp
Corporate <-> Human How institutional do you sound? Corporate: Oracle. Human: Buffer
Voice Attributes Template

Define three core voice attributes with descriptions:

Example for a SaaS product:

Attribute Description Do Don't
Clear Simple language, short sentences "Send invoices in 2 clicks" "Utilize our invoicing facilitation module"
Warm Friendly, supportive, encouraging "Nice work! You're all set." "Configuration complete."
Confident Direct, assured, opinionated "The best way to do X is..." "You might want to consider perhaps..."

Rapport-Building in Digital Products

Onboarding Rapport Sequence
Step Rapport Technique Example
1 Personal greeting "Hey [Name], welcome!"
2 Acknowledge their choice "Great choice joining us" (compliment)
3 Show understanding "We know [their problem] can be frustrating" (similarity)
4 Offer help "We're here to help you every step" (cooperation)
5 Celebrate first win "You did it! First [action] complete" (compliment)
Support Rapport Patterns
Situation Low Rapport Response High Rapport Response
Bug report "We'll look into it." "I completely understand how frustrating that must be. I'm personally looking into this right now."
Feature request "Added to our backlog." "That's a really smart idea. I can see exactly how that would help you. Let me share this with our product team."
Confusion "Please read the documentation." "That feature can be confusing at first. Let me walk you through it step by step."
Complaint "We apologize for the inconvenience." "You're absolutely right to be frustrated. Here's what we're doing about it, and here's what I can do for you right now."

Personalization Strategies

Levels of Personalization
Level Data Required Example Liking Impact
Name First name "Hey Sarah" Low-moderate
Segment Industry, role, company size "Tips for SaaS marketers" Moderate
Behavioral Usage data, browsing history "Since you use X feature a lot, try Y" High
Contextual Time, location, device "Good morning! Start your Monday with..." Moderate
Predictive ML-based preferences "We think you'll love this new feature" High
Personalization Best Practices
  • Use the person's name sparingly (overuse feels robotic, not personal)
  • Reference their actual behavior, not just their data profile
  • Personalize the experience, not just the salutation
  • Respect privacy boundaries; don't reveal creepy levels of tracking
  • Allow users to control personalization settings

Visual Design and the Halo Effect

Design Elements That Increase Liking
Element Principle Implementation
Rounded corners Softness signals friendliness Use border-radius on cards, buttons, images
Warm colors Warm tones feel approachable Accent colors in warm spectrum (orange, coral)
White space Breathing room feels calm and premium Generous padding and margins
Illustrations Custom illustrations feel human Hand-drawn or unique illustration style
Micro-animations Delight through subtle motion Button hover effects, loading animations
Real photography Real people feel authentic Team photos, customer photos
The Halo Effect in Practice

When users find a product visually appealing, they automatically rate it as:

  • Easier to use (even when it isn't)
  • More trustworthy
  • More reliable
  • More innovative
  • Higher quality

This means design investment directly impacts perceived product quality and user trust, independent of actual functionality.

Community Building as Liking

Community Types by Liking Factor
Community Type Primary Liking Factor Example
User forums Similarity + familiarity Notion community, Figma forums
Slack/Discord groups Cooperation + familiarity dbt community Slack
User conferences Similarity + association Salesforce Dreamforce
Ambassador programs Compliments + cooperation Product Hunt Makers
Open source Cooperation + similarity React, Kubernetes communities
Community-Driven Liking Tactics
  1. Facilitate connections: Help users find others like them
  2. Celebrate members: Highlight community achievements regularly
  3. Co-create: Let community members shape the product roadmap
  4. Shared rituals: Create recurring events (weekly calls, monthly challenges)
  5. Inside language: Develop terminology that bonds members ("makers", "builders", "tribe")

Tone Guidelines: Before and After Examples

Error Messages
Before (Low Liking) After (High Liking)
"Error 403: Forbidden" "Oops, you don't have access to this page. Need access? Ask your team admin."
"Invalid input" "That doesn't look quite right. Email addresses usually look like [email protected]"
"Payment failed" "Your payment didn't go through. This usually happens when the card details need updating. Want to try again?"
"Session expired" "You've been away for a while. Let's get you back in."
Empty States
Before (Low Liking) After (High Liking)
"No data" "Nothing here yet. Create your first project to get started."
"No results found" "We couldn't find anything for that search. Try different keywords or browse our categories."
"Inbox empty" "All caught up! No new messages. Time for a coffee break."
Notifications
Before (Low Liking) After (High Liking)
"Your subscription expires in 3 days" "Heads up: your plan renews in 3 days. Everything's looking good on your end."
"Complete your profile" "A quick tip: teams with complete profiles get 40% more responses. Want to add a photo?"
"New feature available" "Something new you might like: we just launched [feature] based on feedback from people like you."
Upgrade Prompts
Before (Low Liking) After (High Liking)
"Upgrade to Pro to access this feature" "This feature is part of our Pro plan. Want to see if it's a good fit?"
"You've reached your free limit" "Wow, you've been busy! You've used all your free credits this month. Upgrade for unlimited access."
"Buy now" "Ready to level up?"

Liking Audit Checklist

  • Is our brand voice consistent across all touchpoints?
  • Do we use "we" language that signals cooperation?
  • Are error messages friendly and helpful (not robotic)?
  • Does our visual design create a positive first impression?
  • Are we personalizing interactions beyond just using names?
  • Do our team pages show real people with real personalities?
  • Are support interactions warm, empathetic, and helpful?
  • Is our community creating genuine connections among users?
  • Are we celebrating user achievements and milestones?
  • Would a new user feel welcomed and valued within their first 5 minutes?

Key Takeaways

  1. Liking is not one thing but six factors that can all be designed for independently
  2. Visual design creates the first and fastest impression; invest in it disproportionately
  3. Similarity is the most powerful factor in digital contexts; mirror your audience's language, values, and identity
  4. Personalization should feel helpful, not surveillance-like; reference behavior, not data
  5. Consistency builds familiarity, which builds liking; don't reinvent your brand constantly
  6. Community is the ultimate liking machine; it creates similarity, familiarity, cooperation, and association simultaneously
  7. Every interaction is an opportunity to build or erode liking; audit every touchpoint
1# Liking: Why We Say Yes to People We Like
2 
3People prefer to say yes to individuals they know and like. This seemingly obvious principle has profound implications for product design, brand building, and marketing. Liking isn't just about being pleasant; it's a systematic set of factors that can be deliberately designed into every customer interaction.
4 
5This reference covers the six factors of liking, brand voice and personality guidelines, rapport-building in digital products, personalization strategies, the halo effect in visual design, community building, and detailed tone guidelines with before/after examples.
6 
7## The Six Factors of Liking
8 
9### 1. Physical Attractiveness (The Halo Effect)
10 
11**Mechanism**: Attractive people (and by extension, attractive products and websites) are automatically assumed to be smarter, more competent, and more trustworthy. This is the "halo effect," where one positive trait colors our perception of everything else.
12 
13**Application to digital products:**
14 
15| Element | Low Liking | High Liking |
16|---------|-----------|-------------|
17| **Visual design** | Cluttered, dated, inconsistent | Clean, modern, polished |
18| **Photography** | Generic stock photos | Custom, high-quality imagery |
19| **Typography** | System fonts, poor hierarchy | Thoughtful type selection and spacing |
20| **Animations** | Janky or absent | Smooth, purposeful micro-interactions |
21| **Color** | Clashing or dull | Harmonious, intentional palette |
22 
23**Key insight**: First impressions form in 50 milliseconds. Visual attractiveness is the fastest path to initial liking, and it colors every subsequent interaction.
24 
25### 2. Similarity
26 
27**Mechanism**: We like people who are like us, who share our values, background, interests, or circumstances. Similarity creates an unconscious sense of kinship and trust.
28 
29**Application strategies:**
30 
31| Similarity Type | Implementation | Example |
32|----------------|---------------|---------|
33| **Demographic** | Show diverse team that mirrors audience | Team page with people who look like users |
34| **Experiential** | Share origin stories that resonate | "We were frustrated founders too" |
35| **Values** | State values explicitly and live them | "We believe in privacy. Here's our code." |
36| **Language** | Use the words your audience uses | Developer tool using developer jargon appropriately |
37| **Aesthetic** | Design for cultural context | Different visual styles for different markets |
38 
39**Copywriting for similarity:**
40- "We built this because we had the same problem"
41- "As a [identity], you know that [shared experience]"
42- "We're founders building for founders"
43- Mirror the audience's vocabulary, tone, and communication style
44 
45### 3. Compliments
46 
47**Mechanism**: We like people who say nice things about us, even when we suspect the compliments are not entirely sincere. Flattery works because we want to believe good things about ourselves.
48 
49**Application strategies:**
50 
51| Context | Compliment | Effect |
52|---------|-----------|--------|
53| **Onboarding** | "Great choice! You clearly value [quality]" | Validates the decision to sign up |
54| **Feature use** | "Nice work! You're ahead of 80% of new users" | Encourages continued engagement |
55| **Purchase** | "Excellent taste. This is our most popular [item]" | Reinforces the buying decision |
56| **Content** | "You're clearly someone who takes [topic] seriously" | Validates the reader's identity |
57| **Support** | "That's a really smart question" | Makes the user feel valued |
58 
59**Rules for effective compliments:**
60- Tie the compliment to something the user actually did (not just flattery)
61- Be specific rather than generic ("Your project setup is really thorough" > "Great job!")
62- Don't overdo it; one well-placed compliment is more powerful than constant praise
63- Make it about their quality, not your product ("You have great taste" > "Our product is great")
64 
65### 4. Cooperation
66 
67**Mechanism**: We like people who work with us toward shared goals. Cooperation signals that we are on the same team, creating a collaborative bond that increases trust and liking.
68 
69**Application strategies:**
70 
71| Context | Cooperation Signal | Example |
72|---------|-------------------|---------|
73| **Product framing** | "We" language | "Let's build your first project together" |
74| **Support** | Problem-solving partnership | "Let me help you figure this out" |
75| **Feature design** | Co-creation tools | User feedback boards, feature voting |
76| **Pricing** | Flexible, fair pricing | "Pick what works for you" |
77| **Updates** | Shared roadmap | "Here's what we're building next, based on your feedback" |
78 
79### 5. Familiarity
80 
81**Mechanism**: Repeated, positive exposure increases liking. We prefer things we've seen before, even if we don't consciously remember seeing them. This is the "mere exposure effect."
82 
83**Application strategies:**
84 
85| Channel | Familiarity Builder | Frequency |
86|---------|-------------------|-----------|
87| **Email** | Consistent newsletter with recognizable format | Weekly |
88| **Social media** | Regular posts with consistent visual identity | Daily |
89| **Retargeting** | Display ads with brand elements (not hard sell) | Controlled frequency |
90| **Content** | Blog posts, podcasts with consistent voice | Weekly |
91| **Product** | Consistent UI patterns and brand experience | Every interaction |
92 
93**Key insight**: Familiarity requires consistency. Changing your brand voice, visual identity, or messaging frequently prevents familiarity from building. The most liked brands are the most consistent.
94 
95### 6. Association
96 
97**Mechanism**: We like things associated with other things we already like. This is why product placement works, why celebrities endorse products, and why brands sponsor events.
98 
99**Application strategies:**
100 
101| Association Type | Implementation | Example |
102|-----------------|---------------|---------|
103| **Positive emotions** | Associate product with good feelings | Lifestyle imagery, aspirational content |
104| **Success** | Connect to successful outcomes | "Used by companies that grew 10x" |
105| **Innovation** | Associate with cutting-edge tech | "AI-powered", integration with trendy tools |
106| **Causes** | Support causes your audience cares about | "1% of revenue goes to [cause]" |
107| **Aesthetic** | Visual association with premium brands | Apple-like minimalism, luxury design cues |
108 
109## Brand Voice and Personality Guidelines
110 
111### Defining Your Brand Personality
112 
113Use this framework to define a consistent brand voice:
114 
115| Dimension | Spectrum | Example Brands |
116|-----------|---------|---------------|
117| **Formal <-> Casual** | Choose where you sit | Formal: McKinsey. Casual: Mailchimp |
118| **Serious <-> Playful** | Match audience expectations | Serious: Stripe. Playful: Slack |
119| **Expert <-> Approachable** | Balance credibility and warmth | Expert: IBM. Approachable: Basecamp |
120| **Corporate <-> Human** | How institutional do you sound? | Corporate: Oracle. Human: Buffer |
121 
122### Voice Attributes Template
123 
124Define three core voice attributes with descriptions:
125 
126**Example for a SaaS product:**
127 
128| Attribute | Description | Do | Don't |
129|-----------|------------|----|----|
130| **Clear** | Simple language, short sentences | "Send invoices in 2 clicks" | "Utilize our invoicing facilitation module" |
131| **Warm** | Friendly, supportive, encouraging | "Nice work! You're all set." | "Configuration complete." |
132| **Confident** | Direct, assured, opinionated | "The best way to do X is..." | "You might want to consider perhaps..." |
133 
134## Rapport-Building in Digital Products
135 
136### Onboarding Rapport Sequence
137 
138| Step | Rapport Technique | Example |
139|------|------------------|---------|
140| 1 | **Personal greeting** | "Hey [Name], welcome!" |
141| 2 | **Acknowledge their choice** | "Great choice joining us" (compliment) |
142| 3 | **Show understanding** | "We know [their problem] can be frustrating" (similarity) |
143| 4 | **Offer help** | "We're here to help you every step" (cooperation) |
144| 5 | **Celebrate first win** | "You did it! First [action] complete" (compliment) |
145 
146### Support Rapport Patterns
147 
148| Situation | Low Rapport Response | High Rapport Response |
149|-----------|---------------------|----------------------|
150| **Bug report** | "We'll look into it." | "I completely understand how frustrating that must be. I'm personally looking into this right now." |
151| **Feature request** | "Added to our backlog." | "That's a really smart idea. I can see exactly how that would help you. Let me share this with our product team." |
152| **Confusion** | "Please read the documentation." | "That feature can be confusing at first. Let me walk you through it step by step." |
153| **Complaint** | "We apologize for the inconvenience." | "You're absolutely right to be frustrated. Here's what we're doing about it, and here's what I can do for you right now." |
154 
155## Personalization Strategies
156 
157### Levels of Personalization
158 
159| Level | Data Required | Example | Liking Impact |
160|-------|-------------|---------|--------------|
161| **Name** | First name | "Hey Sarah" | Low-moderate |
162| **Segment** | Industry, role, company size | "Tips for SaaS marketers" | Moderate |
163| **Behavioral** | Usage data, browsing history | "Since you use X feature a lot, try Y" | High |
164| **Contextual** | Time, location, device | "Good morning! Start your Monday with..." | Moderate |
165| **Predictive** | ML-based preferences | "We think you'll love this new feature" | High |
166 
167### Personalization Best Practices
168 
169- Use the person's name sparingly (overuse feels robotic, not personal)
170- Reference their actual behavior, not just their data profile
171- Personalize the experience, not just the salutation
172- Respect privacy boundaries; don't reveal creepy levels of tracking
173- Allow users to control personalization settings
174 
175## Visual Design and the Halo Effect
176 
177### Design Elements That Increase Liking
178 
179| Element | Principle | Implementation |
180|---------|-----------|---------------|
181| **Rounded corners** | Softness signals friendliness | Use border-radius on cards, buttons, images |
182| **Warm colors** | Warm tones feel approachable | Accent colors in warm spectrum (orange, coral) |
183| **White space** | Breathing room feels calm and premium | Generous padding and margins |
184| **Illustrations** | Custom illustrations feel human | Hand-drawn or unique illustration style |
185| **Micro-animations** | Delight through subtle motion | Button hover effects, loading animations |
186| **Real photography** | Real people feel authentic | Team photos, customer photos |
187 
188### The Halo Effect in Practice
189 
190When users find a product visually appealing, they automatically rate it as:
191- Easier to use (even when it isn't)
192- More trustworthy
193- More reliable
194- More innovative
195- Higher quality
196 
197This means design investment directly impacts perceived product quality and user trust, independent of actual functionality.
198 
199## Community Building as Liking
200 
201### Community Types by Liking Factor
202 
203| Community Type | Primary Liking Factor | Example |
204|---------------|----------------------|---------|
205| **User forums** | Similarity + familiarity | Notion community, Figma forums |
206| **Slack/Discord groups** | Cooperation + familiarity | dbt community Slack |
207| **User conferences** | Similarity + association | Salesforce Dreamforce |
208| **Ambassador programs** | Compliments + cooperation | Product Hunt Makers |
209| **Open source** | Cooperation + similarity | React, Kubernetes communities |
210 
211### Community-Driven Liking Tactics
212 
2131. **Facilitate connections**: Help users find others like them
2142. **Celebrate members**: Highlight community achievements regularly
2153. **Co-create**: Let community members shape the product roadmap
2164. **Shared rituals**: Create recurring events (weekly calls, monthly challenges)
2175. **Inside language**: Develop terminology that bonds members ("makers", "builders", "tribe")
218 
219## Tone Guidelines: Before and After Examples
220 
221### Error Messages
222 
223| Before (Low Liking) | After (High Liking) |
224|---------------------|---------------------|
225| "Error 403: Forbidden" | "Oops, you don't have access to this page. Need access? Ask your team admin." |
226| "Invalid input" | "That doesn't look quite right. Email addresses usually look like [email protected]" |
227| "Payment failed" | "Your payment didn't go through. This usually happens when the card details need updating. Want to try again?" |
228| "Session expired" | "You've been away for a while. Let's get you back in." |
229 
230### Empty States
231 
232| Before (Low Liking) | After (High Liking) |
233|---------------------|---------------------|
234| "No data" | "Nothing here yet. Create your first project to get started." |
235| "No results found" | "We couldn't find anything for that search. Try different keywords or browse our categories." |
236| "Inbox empty" | "All caught up! No new messages. Time for a coffee break." |
237 
238### Notifications
239 
240| Before (Low Liking) | After (High Liking) |
241|---------------------|---------------------|
242| "Your subscription expires in 3 days" | "Heads up: your plan renews in 3 days. Everything's looking good on your end." |
243| "Complete your profile" | "A quick tip: teams with complete profiles get 40% more responses. Want to add a photo?" |
244| "New feature available" | "Something new you might like: we just launched [feature] based on feedback from people like you." |
245 
246### Upgrade Prompts
247 
248| Before (Low Liking) | After (High Liking) |
249|---------------------|---------------------|
250| "Upgrade to Pro to access this feature" | "This feature is part of our Pro plan. Want to see if it's a good fit?" |
251| "You've reached your free limit" | "Wow, you've been busy! You've used all your free credits this month. Upgrade for unlimited access." |
252| "Buy now" | "Ready to level up?" |
253 
254## Liking Audit Checklist
255 
256- [ ] Is our brand voice consistent across all touchpoints?
257- [ ] Do we use "we" language that signals cooperation?
258- [ ] Are error messages friendly and helpful (not robotic)?
259- [ ] Does our visual design create a positive first impression?
260- [ ] Are we personalizing interactions beyond just using names?
261- [ ] Do our team pages show real people with real personalities?
262- [ ] Are support interactions warm, empathetic, and helpful?
263- [ ] Is our community creating genuine connections among users?
264- [ ] Are we celebrating user achievements and milestones?
265- [ ] Would a new user feel welcomed and valued within their first 5 minutes?
266 
267## Key Takeaways
268 
2691. Liking is not one thing but six factors that can all be designed for independently
2702. Visual design creates the first and fastest impression; invest in it disproportionately
2713. Similarity is the most powerful factor in digital contexts; mirror your audience's language, values, and identity
2724. Personalization should feel helpful, not surveillance-like; reference behavior, not data
2735. Consistency builds familiarity, which builds liking; don't reinvent your brand constantly
2746. Community is the ultimate liking machine; it creates similarity, familiarity, cooperation, and association simultaneously
2757. Every interaction is an opportunity to build or erode liking; audit every touchpoint
276 

Discussion