Case study

Scaling BSE Project Throughput by ~300%

How we tripled what the Business Systems Engineering org could ship without adding headcount — by fixing the operating model, not the people.

300%+
Project throughput increase
90%
Reporting prep reduction
0
Headcount added
3
Engineers grown into senior roles

Problem

When I stepped into the Engineering Manager role, the Business Systems Engineering org was delivering a fraction of its potential. Initiatives sat in flight for months, work-in-progress was piling up across the team, and stakeholder trust was eroding. We were not understaffed — we were over-committed and under-coordinated.

Context

Three globally distributed teams supporting Finance, Fulfillment, Customer Support, and Catalog. Highly cross-functional surface area, multiple competing roadmaps, and a long backlog of half-finished projects with no clear owner or finish line.

What changed

  • Capped concurrent initiatives per team and forced sequential delivery on top priorities.
  • Rebuilt the intake and prioritization process with stakeholders so the team only said yes to work that mapped to a measurable outcome.
  • Introduced a clear operating cadence: weekly delivery sync, monthly business review, and a rolling 90-day roadmap.
  • Pushed lifecycle ownership down to project leads so engineers could own initiatives end-to-end without me as a bottleneck.
  • Built lifecycle dashboards in Asana so anyone could answer 'what's in flight, what's blocked, what's done' without a meeting.

Systems introduced

  • Asana-based lifecycle dashboards (status, owner, target date, blocker)
  • Project Lead framework to grow mid-level engineers into delivery owners
  • Standing async business reviews replacing ad-hoc status update meetings
  • WIP limits at the team level enforced through the planning cadence

Measurable impact

  • 300%+ — Project throughput increase
  • 90% — Reporting prep reduction
  • 0 — Headcount added
  • 3 — Engineers grown into senior roles

Lessons learned

  • Throughput problems are almost always operating-model problems, not effort problems.
  • Visibility is leverage — the dashboard that shows truth is worth more than the meeting that explains it.
  • Mid-level engineers will rise to ownership if you give them the frame and the air cover.
Tools & systems
AsanaNotionSlackGoogle SheetsLooker
Related writing
More case studies