Breaking Down Silos Between Platform and Product Teams
summary
Atlassian identifies survey feedback showing planning, prioritization and communication as the top developer pain, then builds a campaign-driven system that scopes targets using the Compass catalog, measures compliance with an asset readiness rules engine, and pushes staged interventions (PR annotations, JIRA backlogs, eventual deployment blocks). Adoption doubles adherence and targeting rises to ~100% for engaged teams; small fixes drop from six months to under 14 days. The platform now automates some code changes and plans multi-year rollout and safety guardrails.
AI-written summary · about
chapters (5)
- 0:00Identifying the developer productivity communication chasm
- 8:00Establishing the engineering health flywheel and campaigns
- 16:30Integrating campaigns into the team's operational rhythm
- 23:00Defining the asset readiness rules engine and interventions
- 27:35Progress results and future multi-year program goals
related talks
22mThe challenges of Platform teams
43mCase study: Managing a complex engineering project
58mDeveloper Joy – How great teams get s%*t done
34mBuilding a Culture For Developer Productivity
17mHow Atlassian Unlocks High-Velocity Teams with Jira
48mDeveloper Joy – How Great Teams Get s%*t Done
43mPlatform as a Product: Mindset, milestones, metrics
42mDeveloper Joy: How great teams get s%*t done