Waifinding
Stark Industries PMO · built on monday.com · guided by a Waifinder that knew the platform first. Seven stages, one connected build.
Consultative Discovery
Read Pepper's assignment email — intake, SLA tracking, executive dashboard.
Surfaced 4 implicit problems she didn't name: requests need screening before the SLA clock starts; SLA breach must notify, not just silently expire; executives and PMs need different views of the same data; vague requests create all downstream problems.
Drew the 4-tier architecture before touching the platform.
Platform Waifinder
monday.com was a new platform for me, so I scraped help docs and developer references to build a KB.
Built a copilot (Waifinder) tied to the KB.
Used the Waifinder to confirm platform capabilities and advise on design decisions at each stage.
Board Structure
Created 3 boards: Intake, Portfolio (Status pipeline), Execution (Sprint-based groups).
Structural contrast is deliberate — Portfolio uses Status pipeline, Execution uses Sprint groups.
Satisfies the assignment's "structured differently" requirement by design, not by accident.
Intake Flow
Built public intake form — 8 fields, all required for submission.
On submission: item lands on Intake Board, AI Summary and AI Completeness fire automatically.
If AI Completeness detects the submission lacks enough info, the automation emails the requestor: the AI's specific feedback, their original text quoted, and a link to the form. They resubmit as a new item — platform-native. Original stays Incomplete.
Automations
Wired 5 automations: AI completeness routing, field completeness routing, SLA breach notification, PM assignment, Execution Board creation on approval.
When there is an SLA breach — Evaluation Deadline arrives, no decision, PM and Pepper notified immediately.
Formula columns can't trigger automations directly — workaround: "When item created" trigger with a condition that reads the formula value.
Executive Dashboard
4 widgets: Portfolio Health (pie), SLA Compliance (number), Active Projects (table), Department Load (bar).
Live data connections to boards eliminate manual PowerPoint updates.
Dashboard updates automatically as items move through the pipeline.
AI / Formula Separation
Two distinct layers: AI handles fuzzy (summarization, completeness judgment), formula handles deterministic (field fill check).
Platform fluency: formula columns can't trigger automations, "When item created" + condition check is the workaround.
Connected Architecture
Linked all 3 tiers: Intake → Portfolio (triage), Portfolio → Execution (work assignment).
Mirror columns feed Status and Due Date back up — PMs see trajectory without clicking through.
Deliberate separation: executives see trajectory, not micro-detail — sprint tasks stay local.
AESOP Transformation OS
Any monday.com build — not just this one — executed via API calls and the monday.com MCP, orchestrated through AESOP.
AESOP automates the full pipeline: Discover → Design → Build → Deploy, with human-in-the-loop intervention only at critical decision gates.
The design purpose: monday.com as a target platform within AESOP — any team, any use case, same API-driven consultative+guided-build loop, repeatable at scale.