Company Context

Atlassian is evaluating how to scale engineering delivery for Jira Cloud Enterprise. You are the Engineering Manager for a platform area that owns workflow automation, permissions, and admin integrations used by large customers. Demand from enterprise accounts has increased after strong sales of Atlassian Cloud migrations, but delivery predictability has worsened: roadmap slippage is affecting customer commitments, and senior leadership wants a clear recommendation on whether the team should invest primarily in process changes or hire more engineers over the next two quarters.

Strategic Situation

Your org currently has 24 engineers, 3 engineering leads, 1 product manager, and 1 designer across 3 squads. The team supports both roadmap delivery and operational work. Over the last 2 quarters, average cycle time for roadmap epics increased from 6.5 weeks to 9.0 weeks, and committed roadmap completion fell from 82% to 61%. The VP of Engineering has approved budget for either a targeted process improvement program or up to 6 additional engineers, but not both at full scale this fiscal half. The decision matters now because Atlassian has $4.8M in expansion ARR tied to enterprise customers expecting key admin and automation capabilities within 6 months.

Data Points

Additional operating data:

• Average PR review turnaround: 2.8 days
• Cross-team dependency delays affect 41% of roadmap epics
• Sev-2+ incidents consume 11 engineer-weeks per quarter
• Attrition is low at 5% annualized, so backfill pressure is limited
• Benchmark from a similar Atlassian org: process redesign reduced unplanned work by 8-12 percentage points within 2 quarters

Deliverables

1. Assess whether the primary bottleneck is insufficient headcount, inefficient process, or a combination of both.
2. Quantify the likely impact of investing in process changes versus hiring up to 6 engineers over the next 6 months.
3. Recommend one strategy for this planning cycle, with a clear rationale tied to delivery, cost, and customer impact.
4. Outline how you would sequence the decision if you believe a phased approach is best.
5. Identify the key risks, assumptions, and metrics you would monitor in Jira and Atlassian Analytics.

Constraints

• You have a 6-month decision window tied to enterprise delivery commitments.
• Budget allows either the full process program or up to 6 hires this half, with only limited flexibility for a hybrid approach.
• Hiring market is competitive; expected offer acceptance rate is 65%.
• You cannot materially reduce support obligations for existing enterprise customers during the period.