“Cross-Team Metrics Studio’s definition cards are now pinned in our Notion. Sales and CS finally agree what ‘activated account’ means for the weekly forecast. I still wish Module 5 had more SQL examples for warehouse joins.”
Reviews
Notes from people who had to make two teams share a number
Attribution styles vary because feedback arrives that way — some named, some first-name only, some anonymous by industry.
“Tom from Manchester here. The handoff checklist from Shared Grid cut our Slack threads about ‘which export is current’ roughly in half. Not glamorous — just quieter Mondays.”
Solid facilitation. The ownership matrix forced us to admit marketing never owned campaign ROI end-to-end. Progress felt real; the homework volume in week three was heavier than the syllabus suggested.
“We used the reconciliation ritual from the Coordination page workshop with our warehouse team. It exposed a timestamp timezone bug we had blamed on ‘process’. That alone justified the seat cost for me.”
Case note: regional retailer, two fulfilment centres
A GB retailer enrolled four people under Command Table after finance and warehouse KPIs diverged for three consecutive months. During the mapping day they discovered “on-time dispatch” was measured from pick-complete in one site and from carrier scan in the other.
After publishing a single definition card and a twice-weekly reconciliation note, the dispute moved from board packs into a controlled exception list. They did not unify BI tools — they unified the meaning of one metric first.
Case note: public-sector programme office
A programme office joined Shared Grid to align reporting between delivery partners. The mild reservation from their sponsor: live workshops assume participants can speak candidly about data quality. One partner stayed quiet until the async definition exercise, which is when the gaps surfaced.
Outcome: a shared glossary of twelve terms and a clearer escalation path when partner extracts disagree by more than an agreed tolerance.