Definition
A Decision Card is a structured, governed decision produced by an Enterprise Operational Intelligence layer. It packages everything an executive or operations owner needs to act without reconciling twelve systems:
- Issue — what requires a decision
- Evidence — supporting signals and assumptions
- Business impact — why it matters now
- Recommendation — the proposed next action
- Accountability — named owner and due date
- Confidence — how strongly the evidence supports the call
- Status — new, assigned, in progress, closed
Critical actions can require human approval before AI agents execute against the stack.
Why the unit of work must be a decision
Reports and tickets describe work. They do not force closure of the executive question: what should happen next, and who owns it? Decision Cards close that gap. They appear in Executive Home as part of a one-minute decision brief, scoped to each leadership role.
Learn how Decision Cards fit the platform in platform capabilities and the broader EOI category.
What a Decision Card is not
- Not a dashboard widget — it requires an owner and a due date
- Not an unread notification — status is tracked as managed work
- Not an unsupervised agent action — governance and confidence travel with the recommendation
- Not a BI report — it is present-tense and action-oriented
Example pattern
Example (illustrative): Email workflow reliability containment — decide whether to freeze changes on a failing resolution workflow until failure behavior is explained. Business impact: protects automation reliability. Accountability: CTO / Engineering lead · 72 hours. Tags: today · high confidence. Action: Assign.
That pattern — issue, impact, owner, assign — is what leadership sees first on Executive Home.
