ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/docs/examples/WDS-Presentation/docs/2-trigger-map/04-Felix-the-Full-Stack.md

12 KiB
Raw Blame History

Felix the Full-Stack - Developer Persona

Tertiary target - Benefits from better specs and logical design

Felix the Full-Stack

Priority: TERTIARY 💻
Role in Flywheel: Benefits from WDS specs → Spreads word about better collaboration
Created: December 27, 2025

Profile Summary

Full-stack developer with straight career path who loves structure and respects designers because he's terrible at "GUIs - who even calls it that anymore?"

Felix represents developers who benefit from designer's leadership through better specifications. He's not the primary WDS audience, but he needs to know it makes his life easier and appreciate when designers use it.

Background

Career Path

Education: Studied software engineering - solid technical foundation

Career Trajectory:

  • Made internship in a big company
  • Has been a developer his whole life
  • Straight career path, employed throughout
  • No wandering or exploring - found his calling early

Current Role: Full-stack developer on a product team

Professional Identity: Confident in his technical skills, knows what he's good at (and what he's not)

Professional Profile

Technical Approach

What He Loves:

  • Structure and organization
  • BMad Method framework - the documentation and structure appeal to him
  • Clear, logical specifications
  • Having a good spec to work from
  • When things make sense and fit together

What He Hates:

  • Writing documentation (even though he loves having it)
  • UI/GUI work - "who even calls it that anymore?"
  • Being forced to make design decisions
  • Guessing what the designer actually meant

Work Philosophy:

  • "Just give me a good spec and I'm happy to do my magic on the dev side"
  • "If it also looks good, that makes me happy"
  • Enjoys the craft of development when he can focus on it

Current Situation

Work Environment

Team Dynamics:

  • Works with designers (respects them because he's not good at visual stuff)
  • Loves working with creative people even though he doesn't understand them
  • Perfect situation: Designer does "the poetry," he does the "magic on dev side"

Technology Stack:

  • Full-stack capabilities
  • Comfortable with modern tools and frameworks
  • AI relationship: Complicated (see below)

The AI Relationship

Love-Hate with AI Code

What He Loves About AI:

  • Handles tedious tasks he dislikes
  • Takes care of boilerplate and repetitive work
  • Can generate UI code (which he hates writing)
  • Speeds up development on grunt work

What He Hates About AI:

  • The code quality isn't always good
  • Can't release AI code without checking it meticulously first
  • Has to review everything carefully
  • Creates new kind of work: AI code auditing

The Contradiction:

  • Can't argue against using AI (too many benefits)
  • But doesn't completely trust it
  • Interested in AI technology, skeptical of AI code
  • Pragmatic acceptance with careful oversight

Psychological Profile

Personality & Motivations

Core Traits:

  • Logical, systematic thinker
  • Appreciates structure and clarity
  • Respects expertise (even in domains he doesn't understand)
  • Pragmatic and practical
  • Takes pride in clean, working code

Relationship with Design:

  • Respects designers because he knows his limitations
  • Doesn't understand their creative process but trusts it
  • Appreciates when they think logically
  • Frustrated when they don't

Work Satisfaction:

  • Enlightened when work is clean and logical
  • Frustrated when things don't make sense
  • Happy when specification is good
  • Irritated when forced to guess or fill gaps

Driving Forces

✅ Top 3 Positive Drivers (What He Wants)

1. Clear, logical specifications that make his life easier

  • Complete specs with all the details
  • Logical flow and structure
  • No ambiguity or guessing required
  • Everything thought through before handoff
  • WDS Promise: Structured methodology produces complete, logical specs

2. Designers who think things through before handing off

  • Consideration for implementation
  • Understanding of what's possible/difficult
  • Thinking about edge cases
  • Respecting the complexity of development
  • WDS Promise: WDS trains designers to think systematically and completely

3. Work that enlightens his day (not creates problems)

  • Clean handoffs
  • Specifications that work
  • Collaboration that flows
  • Feeling smart and capable, not confused
  • WDS Promise: Better designer-developer collaboration

❌ Top 3 Negative Drivers (What He Fears)

1. Illogical designs creating cascading headaches

  • Design decisions that don't make technical sense
  • Every logical mistake becomes his problem to solve
  • Inconsistencies that create bugs
  • Having to fix design problems in code
  • WDS Answer: Systematic methodology catches logical errors early

2. Vague specs forcing him to guess designer's intent

  • Incomplete specifications
  • Having to make design decisions himself
  • Not knowing what the designer actually wanted
  • Rework because he guessed wrong
  • WDS Answer: Complete specifications from structured process

3. Being forced to do UI work he's terrible at

  • Making visual design decisions
  • Working on "GUIs"
  • Tasks outside his expertise
  • Feeling incompetent at forced design work
  • WDS Answer: Clear designer-developer roles and responsibilities

What Felix Needs from Designers

The Perfect Designer Collaboration

In Felix's Ideal World:

  1. Designer does "the poetry" (the creative, visual, user-focused thinking)
  2. Designer provides complete, logical specifications
  3. Designer has thought through edge cases and technical implications
  4. Felix does his "magic" on the dev side (clean, working code)
  5. Result looks good AND works well
  6. Everyone stays in their lane and respects each other's expertise

What Makes Felix Happy:

  • Specifications that anticipate questions
  • Designs that respect technical constraints
  • Clear communication about priorities
  • Designer who enlightens his day instead of creating problems

What Makes Felix Frustrated:

  • Having to guess what designer meant
  • Logical inconsistencies in design
  • Being asked to "make it look good" without guidance
  • Design decisions dumped on him

Role in Strategic Triangle

STINA (Designer)
Strategic Leader
Shoulders complexity
      │
      │ Creates specs for
      ▼
FELIX (Developer)
Gets logical specs
Life gets easier
      │
      │ Delivers quality for
      ▼
 LARS (Entrepreneur)
 Gets business value
 Trusts the process
      │
      │ Hires/values
      └──────────────► STINA
                      (Loop closes)

Felix's Role:

  • Receives better specifications from WDS-trained designers
  • Delivers higher quality because specs are complete and logical
  • Spreads word to other developers about better collaboration
  • Creates positive feedback about WDS approach

How Felix Discovers WDS Value

The Recognition Path

Phase 1: Experience the Difference

  • Works with designer who uses WDS
  • Notices specifications are more complete
  • Finds fewer logical gaps and ambiguities
  • Realizes his work is flowing better

Phase 2: Recognition

  • "This is so much better than usual"
  • Asks designer what changed
  • Learns about WDS methodology
  • Connects better specs to WDS approach

Phase 3: Appreciation

  • Actively appreciates WDS-trained designers
  • Provides positive feedback
  • Mentions to other developers
  • Becomes advocate for hiring WDS designers

Phase 4: Word of Mouth

  • Tells other devs about better collaboration
  • Recommends WDS approach to designers he works with
  • Becomes part of testimonials/case studies
  • Creates pull for WDS from dev side

What Felix Needs to Know About WDS

The Message for Developers

Primary Message: "WDS-trained designers will make your life easier. They think systematically, provide complete specs, and understand the importance of logical consistency."

Key Points Felix Cares About:

  1. Better Specifications

    • Complete, logical, thought-through
    • Fewer gaps and ambiguities
    • Clear edge case handling

  2. Systematic Thinking

    • Designers trained to think through implications
    • Logical consistency built into methodology
    • Structure that aligns with developer mindset

  3. BMad Integration

    • WDS integrates with BMad Method (which he already loves)
    • Documentation and structure he appreciates
    • Shared framework for team collaboration

  4. Respect for Roles

    • Clear designer-developer responsibilities
    • Designer stays in design lane, dev in dev lane
    • Mutual respect for expertise

Impact on Business Goals

Felix's Role in Success Metrics:

Primary Goal (50 Evangelists):

  • Provides positive feedback that validates designer's WDS journey
  • Developer appreciation motivates designers to continue

Secondary Goals (WDS Adoption):

  • Becomes one of 100 developers benefiting from WDS
  • Spreads word about better collaboration to dev community

Tertiary Goals (Community Opportunities):

  • Provides testimonials from developer perspective
  • Case studies show developer satisfaction
  • Attracts more developers to projects using WDS

The Unspoken Benefit

WDS Makes Felix's Job Better (Without Him Needing to Learn It)

The Beautiful Thing:

  • Felix doesn't need to learn WDS
  • Felix doesn't need to change his workflow
  • Felix just benefits from better specifications
  • His life gets easier without extra effort

The Side Effect:

  • Happy developers tell other developers
  • Dev community becomes advocates for WDS designers
  • Creates market demand from bottom-up
  • Makes WDS designers more valuable

The Irony:

  • Felix loves structure (BMad Method)
  • WDS gives him that structure through designer
  • He gets the benefit of methodology without the learning curve
  • Perfect situation for someone who loves structure but hates documentation

Interface with WDS (Optional)

If Felix Gets Curious

Some developers might get interested in WDS agents for simple UI tasks. For Felix:

Potential Interest:

  • WDS agents for quick UI mockups
  • When forced to do interface work, agents could help
  • Structured approach might appeal to his love of systems

Likely Approach:

  • Cautious, like his approach to AI code
  • Interested but skeptical
  • Would try for simple UI tasks when desperate
  • Still prefers working with skilled designer

Not Primary Focus:

  • Felix is tertiary target
  • Main benefit is receiving better specs
  • Any direct WDS use is bonus, not goal

Related Documents

Visual Representation - Image Generation Prompt

Prompt Used:

"Professional portrait of a 29-year-old male software developer with mixed British-South Asian heritage (Indian or Pakistani and UK), warm medium skin tone, short neat dark hair, wearing developer hoodie and t-shirt, sitting at dual-monitor setup with code visible on screens, focused and concentrated expression with slight smile of satisfaction, soft indirect lighting from monitors and desk lamp, shallow depth of field, modern tech office or home office background with coffee cup and tech accessories visible, photorealistic style, slightly cooler color temperature matching tech environment, 4K quality, environmental tech portrait"

Back to Trigger Map