Back to Details

mvp-architect

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

MVP Architect - Minimum Viable Product Scoping

MVP架构师 - 最小可行产品范围界定

Overview

概述

Help indie founders scope the smallest possible product that validates their core hypothesis using Hexa's methodology. Get to market in 3 months or less.
Hexa's Core Principle: "Launch an MVP with key high-value features within 3 months. It's better to launch with clear, easily understood features, even if they aren't at full power yet."
帮助独立创业者使用Hexa方法界定能够验证其核心假设的最小化产品，在3个月或更短时间内推向市场。
Hexa核心原则： "在3个月内推出具备关键高价值功能的MVP。即使功能尚未完全成熟，推出清晰易懂的功能也比追求完美更重要。"

When This Activates

触发场景

  • "What should my MVP include"
  • "Help me scope my MVP"
  • "What features do I need"
  • "What to build first"
  • "Been building for months, haven't launched"
  • "我的MVP应该包含什么"
  • "帮我界定我的MVP范围"
  • "我需要哪些功能"
  • "优先开发什么"
  • "已经开发了几个月，还没推出"

Hexa's 7 Principles

Hexa的7项原则

  1. Dig Beyond User Requests — Root needs, not surface wants
  2. Combat Confirmation Bias — Challenge assumptions
  3. Partner with Design Partners Early — Build with real users
  4. Prioritize Adaptable Milestones — 6-month goals, 2-week sprints
  5. Sketch Before Designing — Keep ugly until validated
  6. Build Around Dry Elements — Only include stable features
  7. Stress-Test Architecture — Database design affects everything
  1. 挖掘用户需求本质 — 关注根本需求，而非表面诉求
  2. 避免确认偏差 — 挑战固有假设
  3. 尽早与设计合作伙伴协作 — 与真实用户共同构建
  4. 优先设定可调整的里程碑 — 6个月目标，2周冲刺周期
  5. 先草图再设计 — 在验证前保持低成本原型
  6. 围绕稳定元素构建 — 仅包含稳定功能
  7. 压力测试架构 — 数据库设计影响全局

Quick Workflow

快速工作流程

Step 1: Problem Clarity Check

步骤1：问题清晰度检查

  • 10+ customer interviews?
  • One-sentence problem?
  • 3-5 design partners?
  • 完成10次以上客户访谈？
  • 能用一句话描述核心问题？
  • 拥有3-5位设计合作伙伴？

Step 2: Core Hypothesis

步骤2：核心假设

We believe that [customer] has a problem with [pain point].
We believe that [solution] will solve this.
We will know we're right when [success metric].
We believe that [customer] has a problem with [pain point].
We believe that [solution] will solve this.
We will know we're right when [success metric].

Step 3: Feature Prioritization

步骤3：功能优先级排序

For each feature ask:
  • Tests core hypothesis? → Keep
  • Users explicitly asked? → Maybe
  • Critical path? → Keep
  • Can do manually? → Don't build
Target: 3-5 features maximum.
针对每个功能，思考：
  • 是否验证核心假设？ → 保留
  • 用户明确提出该需求？ → 可考虑
  • 是否属于用户使用的关键路径？ → 保留
  • 能否通过手动方式实现？ → 不构建
目标：最多3-5个功能。

Step 4: Dry Elements Test

步骤4：稳定元素测试

Only build features that remained stable through ALL design partner feedback.
仅构建在所有设计合作伙伴反馈中始终保持稳定的功能。

Step 5: User Journey (3-4 Screens)

步骤5：用户旅程（3-4个界面）

  • How do users sign up?
  • First action?
  • Core value delivery?
  • Success confirmation?
  • 用户如何注册？
  • 首次操作是什么？
  • 核心价值如何传递给用户？
  • 如何确认用户获得了价值？

Anti-Scope Creep Checklist

防止范围蔓延检查清单

Before adding ANY feature:
  1. Does this test our core hypothesis? → If no, cut it
  2. Have 3+ design partners asked? → If no, defer it
  3. Can we launch without this? → If yes, defer it
  4. Can we do this manually first? → If yes, don't build it
  5. Will this delay launch by >3 days? → If yes, cut it
在添加任何功能前，请确认：
  1. 该功能是否用于验证我们的核心假设？ → 若否，移除
  2. 有3位以上设计合作伙伴提出该需求吗？ → 若否，推迟开发
  3. 没有该功能我们能否推出产品？ → 若是，推迟开发
  4. 我们能否先通过手动方式实现该功能？ → 若是，不构建
  5. 该功能会导致产品推出延迟超过3天吗？ → 若是，移除

The "Launch in 2 Weeks" Test

“2周内推出”测试

If you HAD to launch in 2 weeks, what would you cut? Whatever you'd cut... cut it now. That's your real MVP.
如果必须在2周内推出产品，你会砍掉哪些内容？ 所有你打算砍掉的内容...现在就砍掉。那才是你真正的MVP。

Integration

集成功能

  • idea-validator
    - Validate before scoping
  • startup-icp-definer
    - Define who you're building for
  • fullstack-workspace-init
    - Set up codebase
  • brand-architect
    - Name and position product
For complete hypothesis framework, feature prioritization matrix, dry elements identification, screen mapping, technical architecture checklist, timeline templates, and output format, see: 
references/full-guide.md
  • idea-validator
    - 范围界定前先验证想法
  • startup-icp-definer
    - 明确目标用户群体
  • fullstack-workspace-init
    - 搭建代码库
  • brand-architect
    - 产品命名与定位
如需完整的假设框架、功能优先级矩阵、稳定元素识别方法、界面映射、技术架构检查清单、时间线模板及输出格式，请参阅： 
references/full-guide.md