A High Integrity Commitment (HIC) is a rare, explicitly labeled date-based commitment on an outcome-based roadmap, reserved for large initiatives or work with cross-team dependencies. Dates aren't inherently incompatible with outcome-based planning — they exist as HICs rather than as the default expectation.
An HIC is only legitimate when two conditions hold:
Mark true date commitments with an explicit "HIC:" tag on the roadmap so stakeholders can tell it apart from an ordinary feature candidate. Contrast with the fixed-timeline antipattern in Roadmap Antipattern Taxonomy, where a date is promised before discovery and scope is dictated top-down. Related: Commit to Time Frames, Not Fixed Dates.
An HIC is only legitimate when the direction of commitment is inverted from ordinary practice: leadership may fix the date, but it is the team — not leadership — who determines and commits to the scope that fits inside it, and only after feasibility work has already been done. Hickman: 'You have to earn it though right, it doesn't come for free, you have to earn that' — an HIC is earned through prior validation and feasibility work, not granted as a starting assumption.
Not everyone needs to agree with a decision, but everyone must commit to executing it fully once it's made — silent or passive disagreement after the fact breaks the commitment. This is the operational counterpart to Product Democracy: Consensus Decision-Making as Anti-Pattern: alignment means everyone understood the plan and had a voice to challenge it, not that everyone agreed with the outcome.
"Aligning people means everybody understands what we're doing... It does not mean that everybody agrees with it." — Blagoja Golubovski