bd495be965
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 12s
- Sidebar: dynamic brand-accent colors, brainstorm section restyled - AI chat general: popup panel with expand/collapse, hides when contextual AI open - AI chat contextual: tabs reordered (Actions first), X close button, height fix - Settings: all tabs restyled, 6 new color presets (sage, terracotta, iron, etc.) - Global color cleanup: emerald/orange hardcoded → brand-accent dynamic - Brainstorm page: orange → brand-accent throughout - PageEntry animation component added to key pages - Floating AI button: bg-brand-accent instead of hardcoded black - i18n: all 15 locales updated with new AI/billing keys - Billing: freemium quota tracking, BYOK, stripe subscription scaffolding - Admin: integrated into new design - AGENTS.md + CLAUDE.md project rules added
160 lines
4.0 KiB
Markdown
160 lines
4.0 KiB
Markdown
# Badass Users Principles
|
|
|
|
**Kathy Sierra's framework for user-centered content**
|
|
|
|
---
|
|
|
|
## Core Philosophy
|
|
|
|
> "Users don't care about your product. They care about being awesome at what your product helps them do."
|
|
|
|
**The Insight:** Don't make a better product. Make a better USER.
|
|
|
|
---
|
|
|
|
## The Five Key Principles
|
|
|
|
### 1. Make Them Better, Not Your Product Better
|
|
|
|
**Focus on THEIR capability, not your features**
|
|
|
|
**Bad (product-focused):**
|
|
- "Our AI analyzes 10,000 beauty sources"
|
|
- "We send weekly emails with 5 trends"
|
|
- "Our platform has been trusted since 2018"
|
|
|
|
**Good (capability-focused):**
|
|
- "You'll spot trends before your competitors"
|
|
- "You'll always have something new to talk about with clients"
|
|
- "You'll feel confident when clients ask about the latest looks"
|
|
|
|
**Frame:** "You'll be able to..." not "Our product has..."
|
|
|
|
---
|
|
|
|
### 2. Show The Transformation
|
|
|
|
**From: Current state → To: Badass state**
|
|
|
|
**Make the path visible:**
|
|
- Where they are (current state: struggling, uncertain)
|
|
- Where they're going (badass state: capable, confident)
|
|
- That the path is real and achievable
|
|
|
|
**Examples:**
|
|
- Specific numbers: "60 seconds per trend" (concrete, not vague)
|
|
- Social proof: "2,000 stylists already there" (others did it)
|
|
- Quick win: "Try it on your next client" (immediate application)
|
|
|
|
---
|
|
|
|
### 3. Create "Aha Moments"
|
|
|
|
**Insights that shift perspective and build confidence**
|
|
|
|
**Not just understanding—perspective shift:**
|
|
|
|
**Examples:**
|
|
- "Oh! I don't need to follow 100 accounts—I just need THIS digest!"
|
|
- "Oh! This is about my CLIENT'S reactions, not just knowing trends!"
|
|
- "Oh! 60 seconds is all I need—I thought it would take hours!"
|
|
|
|
**Characteristics:**
|
|
- Specific insight (not vague "understanding")
|
|
- Removes a barrier or misconception
|
|
- Unlocks confidence to act
|
|
- Memorable and quotable
|
|
|
|
---
|
|
|
|
### 4. Reduce Cognitive Load
|
|
|
|
**Don't make them think unnecessarily**
|
|
|
|
**Strategies:**
|
|
- Too many choices? → Reduce options or guide selection
|
|
- Too much jargon? → Use plain language
|
|
- Too many steps? → Break down or simplify
|
|
- Unclear what to do? → Make next step obvious
|
|
|
|
**Cognitive load reduction often means cutting 30-40% of planned content**
|
|
|
|
**Remove:**
|
|
- Unnecessary decisions
|
|
- Complex explanations
|
|
- Industry jargon
|
|
- Multiple CTAs
|
|
- Non-essential features
|
|
|
|
---
|
|
|
|
### 5. Focus on Skills, Not Tools
|
|
|
|
**What skill or capability are we helping them develop?**
|
|
|
|
**Not (tool-focused):**
|
|
- "Using our platform"
|
|
- "Receiving emails"
|
|
- "Accessing our database"
|
|
|
|
**But (skill-focused):**
|
|
- "Staying current effortlessly"
|
|
- "Impressing your clients"
|
|
- "Becoming the local authority"
|
|
|
|
**The tool is the vehicle, the skill is what matters**
|
|
|
|
---
|
|
|
|
## Application Framework
|
|
|
|
**For each piece of content, ask:**
|
|
|
|
1. **Does this make THEM feel capable?** (not us look good)
|
|
2. **Does it show transformation?** (current → badass with visible path)
|
|
3. **Does it create an "aha moment"?** (perspective shift that unlocks confidence)
|
|
4. **Does it reduce cognitive load?** (or add unnecessary complexity)
|
|
5. **Does it focus on skills gained?** (not just tools used)
|
|
|
|
---
|
|
|
|
## Common Mistakes
|
|
|
|
**Mistake #1: Feature Focus**
|
|
- Talking about product capabilities instead of user capabilities
|
|
- "We have..." instead of "You'll be able to..."
|
|
|
|
**Mistake #2: Vague Transformation**
|
|
- Aspirational marketing fluff without concrete path
|
|
- No specifics on how transformation happens
|
|
|
|
**Mistake #3: No Aha Moment**
|
|
- Just explaining features
|
|
- Missing the key insight that shifts perspective
|
|
|
|
**Mistake #4: Cognitive Overload**
|
|
- Trying to say everything
|
|
- Multiple options without guidance
|
|
- Complex language
|
|
|
|
**Mistake #5: Tool Obsession**
|
|
- Focusing on using the product
|
|
- Missing the skill they're actually developing
|
|
|
|
---
|
|
|
|
## Key Quotes
|
|
|
|
**On Product vs. User:**
|
|
> "Nobody cares about your product. They care about being badass at what your product helps them do."
|
|
|
|
**On Transformation:**
|
|
> "Make the user awesome, not your product awesome."
|
|
|
|
**On Skills:**
|
|
> "People want to be great photographers, not great at using Photoshop."
|
|
|
|
---
|
|
|
|
_Badass Users principles reference for Step 4 - Empowerment Frame_
|