docs: update all documentation and add AI tooling configs
- Rewrite README.md with current architecture, features and stack - Update docs/API.md with all current endpoints (corporate, BI, client 360) - Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL - Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente) - Add docs/INDEX.md documentation index - Add PROJETO.md comprehensive project reference - Add BI-CCC-Implementation-Guide.md - Include AI agent configs (.claude, .agents, .gemini, _bmad) - Add netbird VPN configuration - Add status report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,159 @@
|
||||
# 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_
|
||||
Reference in New Issue
Block a user