Definition
A Decision Card is a structured decision artifact generated by a Support Operational Intelligence layer. It packages what an executive or operations owner needs to evaluate a next action 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 — proposed owner role and deadline
- Confidence — how strongly the evidence supports the call
When a recommendation is selected, OpenOS can convert it into a managed task with a named assignee and status. Approval controls apply to supported governed workflows.
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 SOI category.
What a Decision Card is not
- Not a dashboard widget — it frames an owner role and a deadline
- Not yet a standalone workflow record — a selected action becomes managed work through task conversion
- 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. Proposed owner role: CTO / Engineering lead · Deadline: 72 hours. Tags: today · high confidence. Action: convert to task.
That pattern — issue, impact, proposed owner role, deadline, and next action — is what leadership sees first on Executive Home.
