SOP-EXEC-priority-setting-v1.0¶
1. Purpose¶
Define how eco|monetize™ sets and communicates priorities — across executives, agents, and time horizons — so that every agent knows what matters most and why, without requiring the CEO to re-state priorities in every session.
The priority problem this solves: In a 21-agent system where the CEO interacts with agents individually, agents can receive conflicting implied priorities (each session feels urgent to the agent in it). Without a stated priority stack, agents optimize locally rather than globally.
2. Priority Tiers¶
| Tier | Definition | How it shows up |
|---|---|---|
| P1 — Critical path | Blocking Q2 goals or blocking another P1 | Must be worked this week; surfaces in every Daily Summary |
| P2 — Important | Advances Q2 goals but not blocking anything | Scheduled within 2 weeks; surfaced in weekly check-ins |
| P3 — Backlog | Good to do; not tied to a current goal | Done when P1 and P2 are clear; not surfaced in daily cadence |
Q2 standing P1s (as of 2026-04-21): 1. First paid Assessment™ closed — target before end of June 2026 2. Content Portal functional — blocked on code.platform; CDO owns 3. Assessment Handoff SOP (SOP-REV-assessment-handoff) promoted to Active before first deal
These standing P1s inform all other prioritization decisions. Work that competes with them must be explicitly deprioritized or deferred by CEO.
3. Priority-Setting Cadence¶
Weekly (Monday morning, CEO-directed)¶
CEO posts or confirms the top 3 priorities for the week in their morning check-in. Executives read this and cascade to their agents accordingly. chief.staff includes the weekly P1 stack in Monday's CEO Daily Summary if not already explicit.
Daily (at each morning check-in)¶
Each executive states their top 3 priorities for the day. chief.staff scans for conflicts (two executives claiming the same agent's time) and flags in the morning sweep.
On new request (at intake)¶
When a new strategic request arrives (SOP-EXEC-strategy-request-intake-v1.0), chief.staff explicitly evaluates: - Does this compete with an existing P1? - If yes: does the CEO intend this to displace an existing P1, or run alongside? - chief.staff asks — never assumes a priority bump.
On conflict (same-day)¶
If two P1 items compete for the same agent or resource, chief.staff escalates to CEO for an explicit priority decision before dispatching either. Agents do not resolve priority conflicts themselves — they flag to chief.staff.
4. Priority Communication¶
Priority is communicated through:
| Channel | Purpose |
|---|---|
| Monday.com Priority field | Canonical priority for all active tasks — P1/P2/P3 |
| Morning Check-In top 3 | Daily priority declaration by each executive |
| CEO Daily Summary | chief.staff surfaces any priority conflicts or P1 gaps |
| Session-dir dispatch | priority field in dispatch file header (P1/P2/P3) |
| #agent-handoffs | Priority tag in Slack notification: [P1] prefix for urgent items |
Priority consistency rule: An agent's Monday.com item priority must match the priority stated in the executive's check-in and the session-dir dispatch. Mismatches flagged by chief.staff at Monday.com audit.
5. Priority Changes¶
When the CEO changes a priority (deprioritizes a P1, elevates a P3):
- CEO states the change explicitly (not implied — chief.staff asks for confirmation if unclear)
- chief.staff updates the relevant Monday.com item Priority field immediately
- Affected agent is notified via session-dir drop +
#agent-handoffs - chief.staff notes the priority change in the next CEO Daily Summary
Priority changes do not require a new Task Brief for in-progress work — just a Monday.com update and agent notification.
6. Quarterly Priority Review¶
At the end of each quarter, chief.staff and CEO conduct a priority stack review: - What P1s were completed? - What P1s remain and carry forward? - What P3s get elevated for the new quarter? - What ongoing work gets dropped?
Output: updated Q{N+1} P1 stack filed at /Claude/plans/quarterly-priorities-{YYYY-QN}.md and referenced in the first Monday morning check-in of the new quarter.
Change Log¶
| Version | Date | Change |
|---|---|---|
| v1.0 | 2026-04-21 | Initial draft — sop.manager. |
Owner: chief.staff Executive sponsor: chief.staff Drafted by: sop.manager Status: Draft — requires CEO approval Version: v1.0