Chong Lee Hoon · VP Engineering · Edtech · SMB · 78 employees
The two biggest gaps are the absence of an evidenced shared AI tooling and prompt standard across squads, signalled by the CRM tag 'Cross-squad inconsistency', and the lack of baseline adoption, throughput, and defect data in the discovery record. The highest-leverage 90-day move is a first 2-day cohort for up to 35 engineers that leaves behind a shared Cursor/Claude Code rules repository, an AI-assisted PR-review checklist with agent guardrails, and a pre/post dashboard for adoption and cycle time. That directly addresses cross-squad inconsistency before phasing additional cohorts across the 78-person org.
The discovery context lists no Cursor, Claude Code, Copilot, MCP, IDE-rule, or secrets-handling inventory, so Day 1 cannot assume a common stack. The score is at_risk because the only concrete signal is the 'Cross-squad inconsistency' tag, not evidence of a standard editor and agent setup.
The CRM tag 'Cross-squad inconsistency' is the only workflow signal, and no AI PR-review, testing, prompt-hygiene, or agent-guardrail practice is recorded. Day 2 is therefore only partially applicable until a common practice baseline is established, which places this at_risk.
The VP Engineering is the named contact and a discovery call occurred yesterday, which is a concrete engagement signal. Culture lands in watch rather than healthy because only one leadership contact is visible and no workflow-change or blast-radius tolerance is documented.
The supplied context contains no cycle-time, PRs/dev/week, time-to-merge, or deploy-frequency baseline, so the workshop gap cannot yet be quantified. It scores at_risk because the 'Cross-squad inconsistency' tag suggests uneven throughput across squads.
No daily or weekly AI usage, licence utilization, or sub-team distribution is supplied, despite the org having 78 employees and a cross-squad inconsistency tag. Adoption is at_risk because the workshop cannot target champions or lagging squads without that baseline.
The CRM shows commercial health at 68/100 but no defect rate, escaped bugs, time-to-feature, or developer satisfaction data. Outcomes land at_risk because quality and satisfaction cannot be tied to AI use yet, and cross-squad inconsistency implies uneven output quality.
No proposals yet. The AI writes one from the readiness check.