菜单
Shift from rigid roles (PM, Designer, Engineer) towards a model where individuals use AI to bridge skill gaps, enabling smaller and flatter teams. Use in early-stage startups or innovation units where speed is critical.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when designing AI agent products, defining roadmaps for agentic workflows, or evaluating how to evolve AI from passive tool to proactive partner in software development
Use when designing AI agents or chatbots, when raw model outputs feel like a black box, or when building natural language interfaces that need structure and trust
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
View yourself as an entity with infinite dimensions rather than a single good/bad identity. Strengths and weaknesses are often the same trait in different contexts. Use during performance reviews or when receiving tough feedback.
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
| name | Builder Operating Model |
| description | Shift from rigid roles (PM, Designer, Engineer) towards a model where individuals use AI to bridge skill gaps, enabling smaller and flatter teams. Use in early-stage startups or innovation units where speed is critical. |
"We need to dissolve the boundaries of these traditional roles and call ourselves builders." — Julie Zhuo
A shift away from rigid titles (PM, Engineer, Designer) towards a model where individuals use AI to bridge skill gaps. This allows for smaller, flatter teams where engineers might define product requirements and designers might prototype code.
Don't say "I need a PM for this"; ask "Can I use AI to help me define the requirements?"
Use tools (like ChatGPT/Cursor) to raise your competency in adjacent fields from 0% to 70%.
Remove middle-management layers. A team of two "builders" can now do what a squad of 5 used to do.
Use AI not just to do the work, but to teach you the why behind the work (customized curriculum).
TRADITIONAL BUILDER MODEL
┌────────────────┐ ┌────────────────┐
│ PM │ │ │
├────────────────┤ │ BUILDER │
│ Designer │ ───────► │ (uses AI) │
├────────────────┤ │ │
│ Engineer │ └────────────────┘
└────────────────┘
5 people 2 people
3 handoffs 0 handoffs
STEP 1: Audit Current Handoffs
└── How many people touch a feature before shipping?
└── Where does context get lost?
STEP 2: Identify AI-Bridgeable Gaps
└── Engineer can't write PRD? → AI assists
└── Designer can't code prototype? → AI assists
STEP 3: Restructure Teams
└── Reduce from squad to 2-3 builders
└── Each person owns end-to-end
STEP 4: Invest in AI Fluency
└── Train team to use AI for adjacent skills
└── Celebrate cross-functional contributions
❌ Thinking everyone must be an expert at everything (specialists still needed for complexity)
❌ Using AI only for execution, not for learning
❌ Removing specialists prematurely for truly complex domains
At Sundial, they often don't hire dedicated Product Managers. Engineers are expected to own the "what" and "why" of what they build, using AI to help draft requirements or analyze data if needed.
Source: Julie Zhuo, Lenny's Podcast