whiteport-design-studio 0.1.0

package/docs/models/models-guide.md

@@ -0,0 +1,297 @@
+# Strategic Design Models
+
+Foundational frameworks from thought leaders that inform WDS methodology.
+
+---
+
+## What This Folder Contains
+
+**Models** are external frameworks created by industry pioneers. These are NOT Whiteport inventions - they're time-tested approaches we've adapted and integrated into our methods.
+
+Each model includes:
+- What it is and why it matters
+- Full attribution to original creators
+- Source materials (books, articles, videos)
+- How WDS methods harness it
+- Practical examples and applications
+
+---
+
+## Available Models
+
+### [Customer Awareness Cycle](./customer-awareness-cycle.md)
+
+**By:** Eugene Schwartz (1966)  
+**Core Idea:** Meet users where they are in their awareness journey (Unaware → Problem Aware → Solution Aware → Product Aware → Most Aware)
+
+**Applied in WDS:**
+- Scenario definition (where user starts/ends)
+- Content strategy (matching depth to awareness)
+- Messaging hierarchy
+
+**When to Use:** Positioning content, defining scenario goals, structuring communication
+
+---
+
+### [Impact/Effect Mapping](./impact-effect-mapping.md)
+
+**By:** Mijo Balic & Ingrid Domingues (inUse), popularized by Gojko Adzic  
+**Core Idea:** Visual strategic planning connecting business goals → actors → behavioral impacts → deliverables
+
+**Applied in WDS:**
+- Trigger Mapping (Whiteport's enhanced adaptation)
+- Value Trigger Chains (lightweight version)
+- Strategic alignment from why to what
+
+**When to Use:** Strategic planning, feature prioritization, aligning team on goals
+
+---
+
+### [Golden Circle](./golden-circle.md)
+
+**By:** Simon Sinek (2009)  
+**Core Idea:** Inspire action by communicating WHY → HOW → WHAT (inside-out), not outside-in
+
+**Applied in WDS:**
+- Product Brief discovery conversations
+- Messaging hierarchy and positioning
+- Stakeholder alignment
+- Content structure
+
+**When to Use:** Defining product purpose, structuring communication, conducting discovery
+
+---
+
+### [SMART Method](./smart-goals-model.md)
+
+**By:** George T. Doran (1981)  
+**Core Idea:** A framework for expressing measurable, achievable objectives using five criteria: Specific, Measurable, Achievable, Relevant, and Time-bound.
+
+**Applied in WDS:**  
+Used in Trigger Mapping Workshop 1 to transform vision (visionary statements) into strategic objectives. Ensures business objectives are measurable and trackable.
+
+**When to use it:** When defining strategic objectives that need to be measurable and actionable.
+
+**Reference:** [SMART Method Reference](smart-goals-model.md)
+
+---
+
+### [Action Mapping](./action-mapping.md)
+
+**By:** Cathy Moore (2008+)  
+**Core Idea:** Focus on what people DO (actions), not what they KNOW (information). Design practice, not presentations.
+
+**Applied in WDS:**
+- Scenario design (action-oriented)
+- Onboarding flows (guided practice)
+- Help documentation (task-focused)
+- Component specifications (enabling action)
+
+**When to Use:** Designing scenarios, onboarding, help systems, any behavior change context
+
+---
+
+### [Kathy Sierra Badass Users](./kathy-sierra-badass-users.md)
+
+**By:** Kathy Sierra (2000s-2015)
+**Core Idea:** Don't make a better product. Make users better at what they want to do. Focus on user capability.
+
+**Applied in WDS:**
+- Component design (making users feel capable)
+- Microcopy (building confidence, not just informing)
+- Interaction patterns (reducing cognitive load)
+- Success/error messaging (celebrating/guiding)
+
+**When to Use:** Any design decision - always ask "Does this make the user feel capable?"
+
+---
+
+### [Getting Things Done (GTD)](./gtd-getting-things-done.md)
+
+**By:** David Allen (2001)
+**Core Idea:** Your mind is for having ideas, not holding them. Capture everything, then process and act systematically.
+
+**Applied in WDS:**
+- **2-Minute Rule:** If it takes < 2 minutes, do it now (don't plan trivial tasks)
+- Agent Dialogs as capture system (externalize all ideas)
+- Change Requests as "Someday/Maybe" list
+- Session Start Protocol as weekly review concept
+
+**When to Use:** Deciding whether to plan or act, managing task complexity, avoiding planning overhead
+
+---
+
+## Models vs. Methods
+
+### Models (This Folder)
+
+**What:** External frameworks from thought leaders  
+**Purpose:** Foundational knowledge  
+**Attribution:** Full credit to original creators  
+**Content:** What it is, why it matters, how to use it  
+**Location:** `docs/models/`
+
+### Methods (Method Folder)
+
+**What:** Whiteport's instruments and processes  
+**Purpose:** Practical application  
+**Attribution:** Derived from models (with credit)  
+**Content:** Step-by-step how-to, integration into WDS  
+**Location:** `docs/method/`
+
+**Example:**
+- **Model:** Impact/Effect Mapping (Adzic/inUse)
+- **Method:** Trigger Mapping (Whiteport's adaptation)
+
+---
+
+## How These Models Work Together
+
+### In Product Discovery
+
+**Golden Circle** → Structure discovery conversations (WHY → HOW → WHAT)  
+**Impact/Effect Mapping** → Map strategic connections  
+**Customer Awareness** → Position target users
+
+**Result:** Product Brief with purpose, strategy, and positioning
+
+### In Trigger Mapping
+
+**Impact/Effect Mapping** → Core structure (Goals → Users → Impacts)  
+**Customer Awareness** → Add awareness positioning  
+**Golden Circle** → Understand user's WHY (driving forces)
+
+**Result:** Trigger Map connecting business goals to user psychology
+
+### In Scenario Design
+
+**Action Mapping** → Focus on what users DO  
+**Customer Awareness** → Define awareness progression  
+**Kathy Sierra** → Make users feel capable
+
+**Result:** Scenarios that change behavior and build confidence
+
+### In Component Design
+
+**Kathy Sierra** → User capability focus  
+**Action Mapping** → Enable action, not just display  
+**Customer Awareness** → Match content depth to user
+
+**Result:** Components that make users feel awesome
+
+---
+
+## Using These Models
+
+### 1. Learn the Model
+
+Read the model guide to understand:
+- Core concepts
+- Why it was created
+- How it works
+
+### 2. See WDS Application
+
+Each model guide shows how Whiteport methods harness it. Follow those links to see practical integration.
+
+### 3. Apply in Your Work
+
+Use the templates and examples to apply the model in your projects.
+
+### 4. Combine Multiple Models
+
+Most powerful when used together. Each model addresses different aspects of strategic design.
+
+---
+
+## Recommended Reading Order
+
+### For Beginners
+
+1. **Golden Circle** - Easiest to grasp, immediately applicable
+2. **Customer Awareness Cycle** - Changes how you see content
+3. **Action Mapping** - Shifts focus to behavior
+4. **Kathy Sierra Principles** - Deepens UX thinking
+5. **Impact/Effect Mapping** - Strategic planning foundation
+
+### For Strategic Planning
+
+1. **Impact/Effect Mapping** - Core strategic framework
+2. **Golden Circle** - Purpose and communication
+3. **Customer Awareness Cycle** - User positioning
+
+### For UX Design
+
+1. **Kathy Sierra Principles** - User capability focus
+2. **Action Mapping** - Behavior over information
+3. **Customer Awareness Cycle** - Content depth matching
+
+### For Content Creation
+
+1. **Customer Awareness Cycle** - Positioning content
+2. **Golden Circle** - Structure and hierarchy
+3. **Kathy Sierra Principles** - Building confidence
+
+---
+
+## Attribution and Gratitude
+
+These models represent decades of insight from brilliant thinkers who've shaped how we approach design and strategy:
+
+- **Eugene Schwartz** - Understanding awareness and positioning
+- **Mijo Balic & Ingrid Domingues** - Connecting goals to user behavior
+- **Gojko Adzic** - Making strategic planning accessible
+- **Simon Sinek** - Teaching us to start with WHY
+- **David Allen** - Systematic productivity and the 2-minute rule
+- **George T. Doran** - Creating measurable, achievable objectives
+- **Cathy Moore** - Focusing on action over information
+- **Kathy Sierra** - Championing user capability
+
+**Whiteport stands on the shoulders of giants. We're grateful for their contributions to the field.**
+
+---
+
+## Contributing to This Collection
+
+Have a model you think should be included? Consider these criteria:
+
+**Inclusion Criteria:**
+- External (not created by Whiteport)
+- Well-documented by original creator
+- Time-tested (proven over years)
+- Applicable to strategic design
+- Influences WDS methodology
+- Proper attribution possible
+
+**Doesn't Include:**
+- Whiteport-created methods (those go in `method/`)
+- Temporary trends or fads
+- Frameworks without clear attribution
+- Overly niche or specialized concepts
+
+---
+
+## External Resources
+
+Want to dive deeper? Each model guide includes books, articles, videos, and websites from the original creators. Start there for comprehensive understanding.
+
+**Quick Links:**
+- [ImpactMapping.org](https://www.impactmapping.org) - Impact Mapping resources
+- [Blog.Cathy-Moore.com](https://blog.cathy-moore.com) - Action Mapping blog
+- [SimonSinek.com](https://simonsinek.com) - Golden Circle resources
+- Eugene Schwartz's "Breakthrough Advertising" (book)
+- Kathy Sierra's "Badass: Making Users Awesome" (book)
+
+---
+
+## Related Documentation
+
+- **[WDS Method Guides](../method/)** - How Whiteport applies these models
+- **[Learn WDS Course](../learn-wds/)** - Step-by-step learning path
+- **[Examples](../examples/)** - See models in action
+- **[Getting Started](../getting-started/)** - Quick start with WDS
+
+---
+
+*Strategic Design Models - Standing on the shoulders of giants.*
+

package/docs/models/smart-goals-model.md

@@ -0,0 +1,294 @@
+# SMART Method Reference
+
+**A framework for expressing measurable, achievable objectives**
+
+---
+
+## Overview
+
+The SMART method is a widely-used framework for transforming vague ambitions into concrete, actionable objectives. Originally attributed to George T. Doran's 1981 paper "There's a S.M.A.R.T. Way to Write Management's Goals and Objectives," this approach has become a standard in business planning, project management, and strategic design.
+
+In WDS, strategic objectives are expressed using the SMART method, providing measurable evidence that your vision (visionary statements) is being realized.
+
+---
+
+## The SMART Criteria
+
+Each objective should meet all five criteria:
+
+### S - Specific
+
+**What it means:**
+- Clear and unambiguous
+- Answers who, what, where, when, why
+- No room for interpretation
+
+**Bad example:** "Increase user engagement"  
+**Good example:** "Increase daily active users in the mobile app"
+
+**Why it matters:** Specific goals give clear direction and prevent confusion about what success looks like.
+
+### M - Measurable
+
+**What it means:**
+- Quantifiable with numbers or clear milestones
+- Progress can be tracked objectively
+- You can answer "how much?" or "how many?"
+
+**Bad example:** "Improve customer satisfaction"  
+**Good example:** "Achieve an NPS score of 50 or higher"
+
+**Why it matters:** If you can't measure it, you can't manage it or prove you've achieved it.
+
+### A - Achievable
+
+**What it means:**
+- Realistic given your resources and constraints
+- Challenging but not impossible
+- Within your team's capability
+
+**Bad example:** "Become the #1 app in the world in 30 days" (with a team of 2)  
+**Good example:** "Reach top 10 in our category in the App Store within 6 months"
+
+**Why it matters:** Unachievable goals demoralize teams. Achievable goals motivate action.
+
+### R - Relevant
+
+**What it means:**
+- Aligned with broader business objectives
+- Matters to your organization's success
+- Worth the investment of time and resources
+
+**Bad example:** "Get 1 million Twitter followers" (when your customers aren't on Twitter)  
+**Good example:** "Build an email list of 10,000 qualified leads in our target market"
+
+**Why it matters:** Irrelevant goals waste resources on metrics that don't drive business success.
+
+### T - Time-bound
+
+**What it means:**
+- Has a clear deadline or timeframe
+- Creates urgency and accountability
+- Enables progress tracking
+
+**Bad example:** "Increase revenue eventually"  
+**Good example:** "Increase monthly recurring revenue to $50K by Q4 2024"
+
+**Why it matters:** Without deadlines, goals become wishes. Timeframes create commitment and enable planning.
+
+---
+
+## SMART in WDS Workflow
+
+### Vision to Objectives Flow
+
+In WDS Trigger Mapping (Workshop 1: Business Goals), you work through this progression:
+
+**1. Start with Vision (Soft Goals)**
+- Aspirational and motivational
+- Example: "Make remote work sustainable and healthy"
+
+**2. Ask "What Will We Observe?"**
+- Bridge from vision to measurable reality
+- "When this vision is realized, what will we see in the world?"
+
+**3. Define SMART Objectives (Hard Goals)**
+- Transform observations into SMART format
+- Example: "Achieve 5,000 active teams by Q4 2024"
+
+### Why Both Levels Matter
+
+**Vision (Soft Goals):**
+- Provides motivation and direction
+- Easy to set, hard to measure
+- Inspires the team
+
+**SMART Objectives (Hard Goals):**
+- Provides accountability and tracking
+- Harder to set, easy to measure
+- Proves progress
+
+**Together:** You get both inspiration and accountability.
+
+---
+
+## Generic Examples
+
+### Example 1: SaaS Product
+
+**Vision:** "Be the top-of-mind solution for team collaboration"
+
+**Bridging Question:** "When we're top-of-mind, what will we observe?"
+
+**SMART Objectives:**
+- **S**pecific: Increase paid team subscriptions
+- **M**easurable: Reach 10,000 paid teams
+- **A**chievable: Based on current growth rate and market size
+- **R**elevant: Directly supports revenue and market position goals
+- **T**ime-bound: By Q4 2024
+
+**Result:** "Reach 10,000 paid team subscriptions by Q4 2024"
+
+### Example 2: Mobile App
+
+**Vision:** "Fastest growing health app in our category"
+
+**Bridging Question:** "What would prove we're the fastest growing?"
+
+**SMART Objectives:**
+- **S**pecific: Daily active users in the health & fitness category
+- **M**easurable: 100,000 daily active users
+- **A**chievable: Based on current trajectory and marketing budget
+- **R**elevant: Growth directly supports market leadership goal
+- **T**ime-bound: Within 6 months of launch
+
+**Result:** "Achieve 100,000 daily active users within 6 months of launch"
+
+### Example 3: E-commerce Platform
+
+**Vision:** "Most trusted marketplace for sustainable products"
+
+**Bridging Question:** "How would we measure trust?"
+
+**SMART Objectives:**
+- **S**pecific: Customer retention and repeat purchase rate
+- **M**easurable: 70% of customers make repeat purchase within 90 days
+- **A**chievable: Industry average is 40%, we're targeting above average
+- **R**elevant: Repeat purchases indicate trust and satisfaction
+- **T**ime-bound: Achieve by end of fiscal year
+
+**Result:** "Achieve 70% repeat purchase rate within 90 days by end of fiscal year"
+
+---
+
+## Common Mistakes
+
+### Mistake 1: Vague Objectives
+
+**Problem:** "Improve user experience"  
+**Why it fails:** Not specific or measurable  
+**Fix:** "Increase average session time from 5 to 8 minutes by Q3"
+
+### Mistake 2: No Numbers
+
+**Problem:** "Get more customers"  
+**Why it fails:** Not measurable  
+**Fix:** "Acquire 1,000 new paying customers by end of quarter"
+
+### Mistake 3: Unrealistic Targets
+
+**Problem:** "Become profitable in 2 weeks" (for a startup)  
+**Why it fails:** Not achievable  
+**Fix:** "Reach break-even point within 18 months"
+
+### Mistake 4: Irrelevant Metrics
+
+**Problem:** "Get 100,000 Instagram followers" (for B2B enterprise software)  
+**Why it fails:** Not relevant to business goals  
+**Fix:** "Generate 500 qualified enterprise leads through LinkedIn"
+
+### Mistake 5: No Deadline
+
+**Problem:** "Increase revenue someday"  
+**Why it fails:** Not time-bound  
+**Fix:** "Increase MRR from $20K to $50K by December 31, 2024"
+
+---
+
+## Testing Your SMART Objectives
+
+Ask these questions for each objective:
+
+**Specific:**
+- Can everyone on the team explain what this means?
+- Is there any ambiguity about what we're trying to achieve?
+
+**Measurable:**
+- Can we track progress with a number or clear milestone?
+- Will we know definitively when we've achieved this?
+
+**Achievable:**
+- Given our resources, is this realistic?
+- Have similar organizations achieved similar goals?
+
+**Relevant:**
+- Does this directly support our vision and business goals?
+- Is this worth the investment of time and resources?
+
+**Time-bound:**
+- Is there a specific deadline?
+- Can we create a timeline for progress milestones?
+
+---
+
+## SMART Objectives in Trigger Mapping
+
+Once you have SMART objectives from Workshop 1, they become the foundation for:
+
+**Workshop 2: Target Groups**
+- Which user groups can help you achieve these objectives?
+
+**Workshop 3: Driving Forces**
+- What psychological drivers would motivate those groups to act?
+
+**Workshop 4: Prioritization**
+- Which groups and drivers have highest impact on objectives?
+
+**Workshop 5: Feature Impact**
+- Which features best support achieving these objectives?
+
+**The chain:** SMART objectives → Target groups → Psychological drivers → Prioritized features
+
+---
+
+## Historical Context
+
+### Origins
+
+**George T. Doran** first published the SMART criteria in the November 1981 issue of *Management Review* in his article "There's a S.M.A.R.T. Way to Write Management's Goals and Objectives."
+
+### Evolution
+
+Over time, various interpretations have emerged:
+- **A** has been interpreted as Attainable, Assignable, or Action-oriented
+- **R** has been interpreted as Realistic, Results-oriented, or Resourced
+- **T** has been interpreted as Timely, Time-based, or Trackable
+
+The core principle remains: goals should be clear, measurable, and actionable.
+
+### Modern Application
+
+SMART goals are now standard practice in:
+- Business strategy and planning
+- Project management (Agile, Scrum)
+- Personal development
+- Marketing and sales
+- Product development
+- Strategic design (like WDS)
+
+---
+
+## Further Reading
+
+**Original Source:**
+- Doran, G. T. (1981). "There's a S.M.A.R.T. Way to Write Management's Goals and Objectives." *Management Review*, Vol. 70, Issue 11, pp. 35-36.
+
+**Related WDS Resources:**
+- [Phase 2: Trigger Mapping Guide](../method/phase-2-trigger-mapping-guide.md)
+- [Module 05: Trigger Mapping](../learn-wds/module-05-trigger-mapping/module-05-overview.md)
+- [Lesson 3: The Five Workshops](../learn-wds/module-05-trigger-mapping/lesson-03-five-workshops.md)
+
+---
+
+## Key Takeaways
+
+✅ **SMART = Specific, Measurable, Achievable, Relevant, Time-bound**  
+✅ **Transforms vague ambitions into concrete objectives**  
+✅ **In WDS: Vision (soft goals) + SMART Objectives (hard goals)**  
+✅ **Bridge question: "What will we observe when vision is realized?"**  
+✅ **Foundation for all strategic decisions in Trigger Mapping**  
+✅ **Created by George T. Doran in 1981, now industry standard**
+
+---
+
+*Part of the WDS Models & Frameworks collection*