47 entries across 3 role holders · 6 years of institutional memory
AI tooling pilot — Microsoft Copilot rollout notes
Copilot deployed to delivery leads in Q1 2024. Productivity in sprint planning meetings reduced from 90 min average to 38 min. Key insight: Copilot performs poorly on legacy Jira data pre-2021 due to inconsistent ticket tagging. Recommend tagging hygiene sprint before expanding rollout.
Escalation path formalised for C-suite delivery blocks
After two projects stalled at VP approval stage in 2022, a formal escalation protocol was agreed with the CTO. Any delivery block lasting >5 business days without resolution escalates automatically to the weekly exec stand-up. Template in SharePoint: "Delivery Escalation — Standard Form v2."
Q3 sprint freeze policy introduced after failed release
A major release failed in August 2023 due to a vendor dependency change during the summer hiring period. Policy introduced: no new sprint starts between 15 July and 31 August unless signed off by Head of EA. Saved estimated 3 delivery incidents in following year.
Jira–SAP sync breaks on month-end close
Discovered during Q2 2020 audit: the Jira–SAP integration silently fails during month-end batch processing (last 2 business days of each month). Workaround: pause all automated status syncs from the 27th–2nd and run manual reconciliation. IT have acknowledged but not prioritised a fix. Still active as of 2024.
Azure enterprise contract renegotiated — key terms won
2019 renewal achieved a 22% cost reduction by bundling compute and storage commitments. The key leverage point was a competing AWS quote shared with Microsoft's enterprise team. Contact at Microsoft: Enterprise Account team, not the standard renewal portal. Next renewal due 2025 — start negotiations in Q2, not Q4.
Cross-functional delivery model adopted — stakeholder map created
Moved from project-team silos to a cross-functional squad model in 2021. Each squad includes a business analyst, a delivery lead, a tech lead, and a product owner. The stakeholder map template (Miro board, shared in the role context folder) reduces new squad setup time from ~3 weeks to ~4 days.
AI-assisted risk flagging — delivery dashboard prompt set
A custom GPT-4 prompt set was developed to parse weekly delivery status reports and flag projects at risk of milestone slippage. Catches ~73% of at-risk projects 2 weeks earlier than manual review. Prompt library stored in the role memory context folder — do not modify without testing against the Q3 2023 incident dataset.
AI-generated handoff document · Head of Enterprise Delivery · Meridian Group · Demo only
Meridian Group · Generated from 47 memory entries · 6 years of role history
This role sits at the intersection of technology strategy and operational delivery. You are the primary escalation point for all enterprise-scale delivery programmes and own the relationship between the CTO office and business-unit heads during programme execution.
You will inherit a delivery model built by three previous holders over six years. The cross-functional squad model introduced in 2021 is the backbone of how work gets done — understand it deeply before proposing changes.
How AI has improved this role — and what it means for your organisation
Who benefits from the AI-enabled efficiency gain?
Currently: Meridian Group captures the output. The role holder's contribution is not formally recognised or measured.
Should AI-driven improvement influence career progression?
No policy exists at Meridian. The 34% uplift is not part of the role holder's performance review framework.
What happens when this role holder leaves?
Without RolegacyAI: AI prompt library, tooling configuration, and calibration knowledge leaves with them. Estimated re-learning cost: 3–4 months.
Is the AI improvement visible to leadership?
No. There is no metric in the current reporting framework that captures AI-enabled efficiency at the role level.
RolegacyAI is building the independent report. Start a conversation or become a design partner.