Executive decision inbox: separating status from decisions
The CEO's inbox: 200 emails, 15 Slack threads, three dashboards. Everything reads "urgent." None is an explicit decision—mostly status with misleading subject lines. The week passes in reactive mode; strategic choices wait until "after quarterly."
WKFGo's MCP tool decision_inbox is an executive decision inbox: a prioritized queue of items requiring human decisions—raised by a background monitor when signals cross thresholds, or manually via add_decision_item. Each item carries evidence; the standard loop is brief → debate → simulate → resolve.
Leaders are not starving for status—they starve for structured choice with named owners, deadlines, and a record they can revisit next month.
Symptoms and cost of decision overload
| Symptom | Cost |
|---|---|
| Every email marked urgent | Strategic items defer indefinitely |
| Status dressed as decisions | Meetings discuss facts, never commit |
| Same scope debate every sprint | No record_decision trail |
| Officers disagree in sidebar | CEO hears averaged compromise, not resolution |
| Post-decision amnesia | "Why did we cut Payments epic?" unanswerable |
The cost is not inbox volume—it is decision latency. Releases slip while the org re-debates options that should have been modeled once with simulate_scenario and closed with resolve_decision_item.
Inbox vs notification flood
| Notification | Decision inbox item |
|---|---|
| "Task X overdue" | "Cut scope or delay release? Evidence: 12 overdue critical tasks" |
| FYI digest | Decision with owner and deadline |
| Slack ping | Ranked priority queue |
| Passive read | Action: resolve_decision_item |
WKFGo list_notifications handles awareness. decision_inbox handles commitment. Executive Digest delivers one consolidated notification per monitor cycle—not N pings per officer concern.
Five-step decision loop framework
Step 1: Orient with decision_inbox
Morning or pre-meeting: call decision_inbox—read the top item. If multiple candidates compete, trust the tool's priority ordering unless you have explicit strategic override.
Step 2: Gather evidence with executive_brief
For the top item: executive_brief with the right role (e.g., coo for delivery, cfo for burn). Read FACTS and diagnosis—accept dataGaps honestly. Do not debate before evidence.
Step 3: Model options with simulate_scenario
Before committing, run at least two scenarios:
delay_releasecut_scopeadd_peoplefreeze_project
Output spans five dimensions with confidence and assumptions—compare futures side by side in a wiki table.
Step 4: Debate and resolve
CEO resolves board.tensions when officers disagree. Call resolve_decision_item with owner and timing. Deferred decisions are valid—crowded inbox is not failure; unowned items are.
Step 5: Calibrate with trend
Next week's executive_brief includes trend: did the last decision move its target metric? Was the forecast accurate? This is organizational learning—not blame.
Weekly leadership cadence
Monday, 20 minutes: Top three inbox items—assign an owner each.
Wednesday: simulate_scenario for blocked items still open.
Friday: Resolve plus record_decision for audit trail. Search history with search_decisions when revisiting past tradeoffs.
Anti-patterns
- Using the inbox as a status dump—only items needing decisions belong here.
- Skipping simulate—blind commits to scope cuts without modeling tradeoffs.
- Resolving without owner or timing—decisions without accountability evaporate.
decision_inboxfor CEO only—COO and CFO items need role-specific lenses.- Announcing in Slack before
resolve_decision_item—teams hear decisions before they are logged.
WKFGo tools in the decision loop
decision_inbox— prioritized queueadd_decision_item— manual raise for cross-project tradeoffsexecutive_brief— role-specific evidencesimulate_scenario— what-if before commitresolve_decision_item— close with auto-logrecord_decision,search_decisions,log_decision— history and activity trailportfolio_overview— multi-project orientation for CEO/dashboard,/reports,/projects/:id/finance— UI fallback without MCP
FeatureAccess restricts leadership tools—convention alone does not protect finance-sensitive items.
Sample decision-only meeting (30 minutes)
0–5: Read inbox top item aloud
5–15: executive_brief evidence—no interruptions
15–22: simulate_scenario options compared
22–28: Debate—CEO resolves tension
28–30: resolve_decision_item plus owner confirm
Status discussion forbidden—redirect to async board and my_day posts.
FAQ — executive decision inbox
Who adds items?
Automatic background monitor when thresholds cross, plus PM manual raise via add_decision_item for strategic forks.
What about permissions?
FeatureAccess applies—the same rules as the web app. Forbidden tools mean fix the role, not bypass with a shared admin key.
Does the inbox replace meetings?
No—it feeds meeting agendas with evidence. Exception-only sync remains for cross-team blockers.
What happens after resolve?
Next brief's trend shows calibration. Use search_decisions to answer "why did we decide that?" six months later.
Measuring progress without fake benchmarks
Track observable behaviour over four to six weeks: percentage of assigned tasks touched weekly, status meeting duration, blocker age on cards, and decisions logged in wiki or decision_inbox. If metrics stall after tooling changes, fix board hygiene and permission policy before adding more software.
Permission discipline across UI, chatbot, and MCP
WKFGo resolves identity through JWT or personal wk_ keys and applies FeatureAccess on every tool call. Test with a contractor account before org-wide rollout. Forbidden responses mean permissions work—do not bypass with shared admin tokens.
Next step
Open decision_inbox before your next leadership meeting. Work the top item through brief → simulate → resolve once. One completed loop teaches the team more than a quarter of status theater.