Stage 3 — Automation Flow
Stark Industries PMO · 4 automations across 2 boards4 automations connect the tiers. Only #3 (deadline breach) can be built now — it depends solely on the Evaluation Deadline date column and Status, both available today. Automations #1 and #2 depend on the Completeness Score formula (Stage 5); #4 depends on Connect Boards (Stage 6).
Portfolio Board — PM Strategic View
| Type | Column |
|---|---|
| Text | Project name |
| Text | Requestor / Department |
| Long Text | Business problem |
| Status | Incomplete / Pending Review / Approved / Rejected |
| People | Assigned PM |
| Date | Evaluation Deadline |
| Progress | SLA Progress |
| Timeline | Timeline |
| AI | AI Summary · deferred |
| Formula | Completeness Score · deferred |
| Connect | Connected Execution Board · deferred |
Execution Board — Tactical, Sprint 1 & Sprint 2
| Type | Column |
|---|---|
| Text | Task name |
| People | Assigned to |
| Status | To Do / In Progress / Blocked / Done |
| Date | Due date |
| Dropdown | Sprint (1, 2, 3) |
| Connect | Connected portfolio item · deferred |
The Automation Flow
flowchart TD
FORM[" Form Submission\ncreates Intake Board item"]
COMPLETE{" Completeness Score\n≥ threshold?\nStage 5"}
APPROVE[" Status → Approved"]
DEADLINE{" Evaluation Deadline\narrives?"}
BREACH{"Status ≠ Approved\nor Rejected?"}
FORM --> COMPLETE
COMPLETE -->|"Yes · Auto 1"| PENDING["Status → Pending Review\nset Deadline = TODAY()+5\nnotify Assigned PM\nStage 5"]
COMPLETE -->|"No · Auto 2"| INCOMPLETE["Status → Incomplete\nnotify requestor\nStage 5"]
PENDING --> DEADLINE
DEADLINE -->|"Yes · Auto 3"| BREACH
BREACH -->|"Yes"| NOTIFY[" Notify PM + Pepper\nSLA breach alert\nBUILD NOW"]
PENDING --> APPROVE
APPROVE -->|"Auto 4"| EXEC["Create Execution Board\nfrom template\nlink via Connect Boards\nnotify PM\nStage 6"]
NOTIFY:::liveNode
PENDING:::futureNode
INCOMPLETE:::futureNode
EXEC:::futureNode
COMPLETE:::futureNode
FORM:::formNode
DEADLINE:::decisionNode
BREACH:::decisionNode
APPROVE:::decisionNode
classDef liveNode stroke:#0E7C6E,stroke-width:2px
classDef futureNode stroke:#8C7E6E,stroke-dasharray:6 4,color:#8C7E6E
classDef formNode stroke:#4F46E5,stroke-width:2px
classDef decisionNode stroke:#C23A30,stroke-width:1.5px
The one automation to build now:When Evaluation Deadline arrives AND Status ≠ Approved/Rejected → notify Assigned PM + Pepper.
This is the SLA breach notification — the "watch it fire" moment for the live demo. The other 3 automations depend on the Completeness Score formula (Stage 5) and Connect Boards (Stage 6). Explaining why they're gated on those columns demonstrates architectural thinking — you don't wire automations against columns that don't exist yet.