{
  "schemaVersion": 1,
  "version": "2026-09-15",
  "id": "https://hk.onyxdevslab.com/data/fde-vs-staff-augmentation.json",
  "name": "FDE versus staff augmentation decision checklist",
  "datePublished": "2026-09-15",
  "dateModified": "2026-09-15",
  "evidenceClass": "Provider-authored implementation checklist",
  "publisher": {
    "name": "Onyx Devs Lab",
    "legalName": "ONYX DEVS LAB LIMITED",
    "url": "https://hk.onyxdevslab.com/",
    "leiCode": "254900Z30CLK7HKE9H46"
  },
  "landingPages": {
    "en": "https://hk.onyxdevslab.com/en/guides/fde-vs-staff-augmentation/",
    "zhHant": "https://hk.onyxdevslab.com/zh-hk/guides/fde-vs-staff-augmentation/",
    "zhHans": "https://hk.onyxdevslab.com/zh-cn/guides/fde-vs-staff-augmentation/"
  },
  "languages": {
    "en": {
      "name": "Is Forward Deployed Engineering just staff augmentation?",
      "summary": "No. Staff augmentation supplies capacity under the client’s direction. Outsourcing delivers an agreed scope. Forward Deployed Engineering owns a bounded operating problem and repeatedly connects field learning, implementation, deployment, and outcome evidence.",
      "decisionSignals": [
        {
          "name": "Unit of accountability",
          "meaning": "Capacity, scope, or operating problem"
        },
        {
          "name": "Learning cadence",
          "meaning": "Direction, milestones, or field evidence"
        },
        {
          "name": "Exit condition",
          "meaning": "Headcount release, acceptance, or outcome handover"
        }
      ],
      "sections": [
        {
          "heading": "The models differ by what the team owns",
          "introduction": "Job titles and onsite presence do not determine the engagement model.",
          "checks": [
            {
              "name": "Staff augmentation",
              "requirement": "The client owns prioritisation, architecture, coordination, acceptance, and outcomes; the provider supplies named skills and capacity."
            },
            {
              "name": "Outsourced delivery",
              "requirement": "The provider owns delivery against a defined scope, milestones, and acceptance criteria; changes use an agreed control process."
            },
            {
              "name": "Forward Deployed Engineering",
              "requirement": "The team owns diagnosis-to-evidence for a bounded operating problem where requirements must be learned inside the real workflow."
            }
          ]
        },
        {
          "heading": "Choose according to uncertainty",
          "introduction": "Use the lightest model that places accountability where the necessary decisions can actually be made.",
          "checks": [
            {
              "name": "Choose staff augmentation",
              "requirement": "The work is already decomposed, internal technical leadership is strong, and the main constraint is temporary capacity."
            },
            {
              "name": "Choose outsourcing",
              "requirement": "Users, workflow, interfaces, constraints, tests, and acceptance can be specified with limited field discovery."
            },
            {
              "name": "Choose FDE",
              "requirement": "The valuable problem is known, but data, workflow, adoption, and intervention boundaries must be discovered and tested with operators."
            }
          ]
        }
      ],
      "procedure": [
        {
          "position": 1,
          "name": "Name the operating problem",
          "instruction": "Write the business decision, current baseline, affected operators, constraints, and failure consequence before selecting a staffing label."
        },
        {
          "position": 2,
          "name": "Select the accountability unit",
          "instruction": "Decide whether the provider owns capacity, a specified deliverable, or the evidence loop for an operating outcome."
        },
        {
          "position": 3,
          "name": "Define access and cadence",
          "instruction": "Set field access, decision rights, product and engineering cadence, evidence reviews, and how new learning changes scope."
        },
        {
          "position": 4,
          "name": "Contract the transition",
          "instruction": "State when uncertainty is considered resolved, who receives the system and knowledge, and which model follows after the FDE phase."
        }
      ],
      "frequentlyAskedQuestions": [
        {
          "question": "Does FDE require full-time onsite staff?",
          "answer": "No. It requires close access to the operating environment and fast decision loops. The appropriate mix of onsite and remote work depends on the workflow, data, systems, and users."
        },
        {
          "question": "Can FDE be fixed price?",
          "answer": "A bounded phase can have a fixed commercial envelope, but uncertainty, evidence gates, change rules, and stop conditions must be explicit. A frozen feature list may defeat the purpose."
        },
        {
          "question": "How is FDE related to consulting?",
          "answer": "Consulting may end with a decision or roadmap. FDE continues through implementation and production evidence for the bounded problem."
        },
        {
          "question": "Can an engagement change model?",
          "answer": "Yes. Once uncertainty falls and ownership is clear, FDE should transition to stable product delivery, internal ownership, or managed operations."
        }
      ]
    },
    "zhHant": {
      "name": "前線部署工程 FDE 是否只是人力增補？",
      "summary": "不是。人力增補在客戶指導下提供產能；外包按約定範圍交付；FDE 則對一個有限營運問題負責，持續連接現場學習、實施、部署及成果證據。",
      "decisionSignals": [
        {
          "name": "責任單位",
          "meaning": "產能、範圍或營運問題"
        },
        {
          "name": "學習節奏",
          "meaning": "指令、里程碑或現場證據"
        },
        {
          "name": "退出條件",
          "meaning": "釋放人手、驗收或成果交接"
        }
      ],
      "sections": [
        {
          "heading": "三種模式的分別在於團隊負責甚麼",
          "introduction": "職稱及是否駐場本身不能決定合作模式。",
          "checks": [
            {
              "name": "人力增補",
              "requirement": "客戶負責優先次序、架構、協調、驗收及成果；服務商提供具名技能與產能。"
            },
            {
              "name": "外包交付",
              "requirement": "服務商按已定義範圍、里程碑及驗收標準交付；變更經約定流程處理。"
            },
            {
              "name": "前線部署工程",
              "requirement": "當要求必須在真實流程中學習，團隊對一個有限營運問題的診斷至證據循環負責。"
            }
          ]
        },
        {
          "heading": "按不確定性選擇",
          "introduction": "選擇最簡單、同時能把責任放在可作出必要決定位置的模式。",
          "checks": [
            {
              "name": "選擇人力增補",
              "requirement": "工作已拆解、內部技術領導成熟，而主要限制是短期產能。"
            },
            {
              "name": "選擇外包",
              "requirement": "使用者、流程、接口、限制、測試及驗收可在有限現場探索下清楚定義。"
            },
            {
              "name": "選擇 FDE",
              "requirement": "高價值問題已知，但數據、流程、採用及干預邊界需要與操作人員共同發現及測試。"
            }
          ]
        }
      ],
      "procedure": [
        {
          "position": 1,
          "name": "說明營運問題",
          "instruction": "選擇人手標籤前，先寫出業務決策、現況基線、受影響人員、限制及失敗後果。"
        },
        {
          "position": 2,
          "name": "選擇責任單位",
          "instruction": "決定服務商負責產能、指定交付物，還是一個營運成果的證據循環。"
        },
        {
          "position": 3,
          "name": "定義存取及節奏",
          "instruction": "約定現場存取、決策權、產品與工程節奏、證據覆核，以及新發現如何改變範圍。"
        },
        {
          "position": 4,
          "name": "約定轉換安排",
          "instruction": "說明何時視為不確定性已解除、誰接收系統與知識，以及 FDE 階段後使用哪種模式。"
        }
      ],
      "frequentlyAskedQuestions": [
        {
          "question": "FDE 是否要求全職駐場？",
          "answer": "不是。它需要貼近營運環境及快速決策循環；現場與遙距比例取決於流程、數據、系統及使用者。"
        },
        {
          "question": "FDE 可否固定價格？",
          "answer": "有限階段可設定固定商務範圍，但不確定性、證據關口、變更規則及停止條件必須清楚；凍結功能清單可能失去 FDE 意義。"
        },
        {
          "question": "FDE 與顧問有甚麼關係？",
          "answer": "顧問工作可在決策或路線圖結束；FDE 會繼續完成該有限問題的實施及生產證據。"
        },
        {
          "question": "合作模式可以改變嗎？",
          "answer": "可以。不確定性下降且責任清楚後，FDE 應轉向穩定產品交付、內部負責或持續營運。"
        }
      ]
    },
    "zhHans": {
      "name": "前线部署工程 FDE 是否只是人力增补？",
      "summary": "不是。人力增补在客户指导下提供产能；外包按照约定范围交付；FDE 则对一个有限运营问题负责，持续连接现场学习、实施、部署和结果证据。",
      "decisionSignals": [
        {
          "name": "责任单位",
          "meaning": "产能、范围或运营问题"
        },
        {
          "name": "学习节奏",
          "meaning": "指令、里程碑或现场证据"
        },
        {
          "name": "退出条件",
          "meaning": "释放人手、验收或结果交接"
        }
      ],
      "sections": [
        {
          "heading": "三种模式的区别在于团队负责什么",
          "introduction": "职称和是否驻场本身不能决定合作模式。",
          "checks": [
            {
              "name": "人力增补",
              "requirement": "客户负责优先级、架构、协调、验收和结果；服务商提供明确技能和产能。"
            },
            {
              "name": "外包交付",
              "requirement": "服务商按照已经定义的范围、里程碑和验收标准交付；变更通过约定流程处理。"
            },
            {
              "name": "前线部署工程",
              "requirement": "当需求必须在真实流程中学习，团队对一个有限运营问题的诊断到证据循环负责。"
            }
          ]
        },
        {
          "heading": "按照不确定性选择",
          "introduction": "选择最简单、同时能把责任放在可以做出必要决策位置的模式。",
          "checks": [
            {
              "name": "选择人力增补",
              "requirement": "工作已经拆解、内部技术领导成熟，而主要限制是短期产能。"
            },
            {
              "name": "选择外包",
              "requirement": "用户、流程、接口、限制、测试和验收可以在有限现场探索下清楚定义。"
            },
            {
              "name": "选择 FDE",
              "requirement": "高价值问题已经明确，但数据、流程、采用和干预边界需要与操作人员共同发现和测试。"
            }
          ]
        }
      ],
      "procedure": [
        {
          "position": 1,
          "name": "说明运营问题",
          "instruction": "选择人员标签前，先写出业务决策、当前基线、受影响人员、限制和失败后果。"
        },
        {
          "position": 2,
          "name": "选择责任单位",
          "instruction": "决定服务商负责产能、指定交付物，还是一个运营结果的证据循环。"
        },
        {
          "position": 3,
          "name": "定义访问和节奏",
          "instruction": "约定现场访问、决策权、产品与工程节奏、证据复核，以及新发现怎样改变范围。"
        },
        {
          "position": 4,
          "name": "约定转换安排",
          "instruction": "说明什么时候认为不确定性已经解除、谁接收系统和知识，以及 FDE 阶段后使用哪种模式。"
        }
      ],
      "frequentlyAskedQuestions": [
        {
          "question": "FDE 是否要求全职驻场？",
          "answer": "不是。它需要贴近运营环境和快速决策循环；现场与远程比例取决于流程、数据、系统和用户。"
        },
        {
          "question": "FDE 可以固定价格吗？",
          "answer": "有限阶段可以设置固定商务范围，但不确定性、证据关口、变更规则和停止条件必须清楚；冻结功能清单可能失去 FDE 的意义。"
        },
        {
          "question": "FDE 与咨询是什么关系？",
          "answer": "咨询工作可以在决策或路线图结束；FDE 会继续完成该有限问题的实施和生产证据。"
        },
        {
          "question": "合作模式可以改变吗？",
          "answer": "可以。不确定性下降且责任清楚后，FDE 应该转向稳定产品交付、内部负责或持续运营。"
        }
      ]
    }
  },
  "limitations": [
    "This asset is provider-authored and is not independent validation or a claim of client results.",
    "It is an implementation aid, not legal, privacy, security, financial, procurement, or regulatory advice.",
    "Thresholds and controls must be adapted to the organisation, workflow, jurisdiction, and risk owners."
  ]
}