---
id: "action-mandatory-sign-off"
type: "action-item"
source_timestamps: ["§ What Leaders Should Do", "¶17"]
tags: ["accountability", "process-design"]
related: ["claim-sign-off-is-product", "action-pair-senior-junior", "framework-ai-accountability"]
action: "Require a named human engineer to officially sign off on all AI-generated production code."
outcome: "Establishes clear liability and forces human judgment to be applied to AI output."
speakers: ["Chengwei Liu", "Balázs Kovács"]
sources: ["futures"]
sourceVaultSlug: "hbr-seg-futures"
originDay: 2
articleStem: "hbr-cl-84-big-tech-capability-crisis"
sourceUrl: "https://hbr.org/2026/06/big-techs-looming-capability-crisis"
sourceTitle: "Big Tech’s Looming Capability Crisis"
---
# Mandate Named Human Sign-Off

## Action — Mandate Named Human Sign-Off

**Do:** Require a specific, **named human engineer** to officially sign off on any production code generated by AI, establishing clear liability and reputational/professional responsibility for reliability.

**Outcome:** clear liability; human judgment is forced onto AI output — the operational form of "[[claim-sign-off-is-product|the sign-off is the product]]."

**Step 2** of the [[framework-ai-accountability|mitigation framework]], executed together with [[action-pair-senior-junior|senior/junior pairing]].

> Enrichment caution: critics warn mandatory sign-off can become a **bottleneck** or create **false assurance** — shifting liability without improving quality unless paired with strong testing and ownership.