StratOps — the spec

An internal tool for teams that need a single place to log strategic decisions, assign ownership, drive action, and track whether outcomes actually land. Built for Salome's internal team — people who are already making strategic calls and need a structured system to follow through, not another place to dump ideas.

---

Decisions locked

---

The core loop

1. A team member logs a strategic decision with full rationale — what was decided, why, and what context drove it.
2. Owners are assigned to the decision and to each action item that flows from it, each with a clear deadline.
3. Action items surface in the owner's daily dashboard, sorted by urgency and status.
4. Owners record a progress check-in against each action — blocked, in progress, or done — with a short status note.
5. When an action resolves, outcomes are recorded: what actually happened versus what was intended.
6. The decision log updates automatically to reflect live status, giving the full team a real-time read on where every strategic thread stands.

---

v1 scope

Decision Log with Rationale Capture — A structured form for logging each strategic decision: the decision statement, the reasoning behind it, alternatives considered, and the date it was made. Lives on the Decision Log screen.

Owner Assignment and Accountability — Each decision and each action item has one named owner pulled from the team roster. The ownership field is mandatory; nothing ships without an owner. Lives on the Decision Detail screen.

Action Item Tracking with Deadlines — Decisions decompose into discrete action items, each with an owner, a due date, and a status field. Overdue items surface with a visual flag. Lives on the Action Board screen.

Progress Check-ins and Status Updates — Owners submit a lightweight daily or ad-hoc check-in against their actions: current status, any blockers, and a one-line note. Timestamped and appended to the action's history. Lives on the Action Detail screen.

Outcome Recording and Result Tracking — When an action or decision closes, the owner records the actual result against the original intent. This closes the loop and populates the outcome history on the Decision Log. Lives on the Decision Detail and Action Detail screens.

---

Deliberately later

• Lessons learned templates and export — v2, once there is enough closed-decision history to make retrospectives meaningful.
• Timeline view of all active strategies — v2, after the data model has enough entries to justify the complexity of a visual calendar layer.
• Comment threads for team alignment — v2, once the core check-in habit is established; adding discussion too early risks replacing structured updates with unstructured chat.

---

Data model sketch

• decisions — id, title, rationale, alternatives_considered, owner_id, status, created_at, closed_at
• actions — id, decision_id, title, owner_id, due_date, status, created_at
• check_ins — id, action_id, author_id, status_flag, note, created_at
• outcomes — id, decision_id, action_id, intended_result, actual_result, recorded_by, recorded_at
• users — id, name, email, role, active
• attachments — id, entity_type, entity_id, file_url, uploaded_by, uploaded_at

---

Screens

• Dashboard — Each user's daily view: their open actions, upcoming deadlines, and any overdue items flagged at the top.
• Decision Log — Full list of all strategic decisions, filterable by status and owner, with outcome state visible at a glance.
• Decision Detail — Single decision view: rationale, linked actions, owner, status history, and recorded outcome.
• Action Board — All action items across decisions, sortable by due date, owner, and status; primary workspace for daily tracking.
• Action Detail — Single action view: owner, deadline, full check-in history, and outcome entry form.
• New Decision Form — Structured intake for logging a new decision with rationale, initial actions, and owner assignments.
• Team Roster — Manage the internal user list; assign roles; view accountability load per person.

---

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the product with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screen list are ready to act on without further clarification.
• Keep it as the single source of truth while you build, so every feature decision and prioritisation call stays anchored to what was agreed here.