Back to team
Manager view
Flow & Bottlenecks
Where AI Engineering's capacity is going versus where the goals weight — plus the blockers slowing the highest-value work.
High-severity blockers
2
Medium blockers
1
Misallocation alerts
2
Capacity vs. goal weight
This week Goal weight (where it should go) Capacity (where it actually goes)
Harden the agent platformOver-invested +8 pts
Goal weight50%
Capacity58%
Accelerate onboardingUnder-invested -17 pts
Goal weight35%
Capacity18%
Decommission legacy reportingOver-invested +9 pts
Goal weight15%
Capacity24%
Bottlenecks
3 blockersReview latency on !412
MediumTop-goal security MR waiting on a 2nd approval for 3h+; blocks FLOW-231.
Decision latency blocking FLOW-204
HighMariam blocked 2 days on a backend schema call nobody has made.
No e2e automation
High6h/release of manual QA; !407 is the first automated flow.
Misallocation alerts
24% of capacity is on legacy reporting (0.15 weight) while onboarding (0.35 weight) gets only 18%.
Mariam's week is 53% coordination + admin — well above the IC rubric expectation.
Recommended actions
1
Make the schema decision unblocking FLOW-204 today.
2
Shift Mariam off the rename + manual reporting onto onboarding.
3
Make !407 a required check to retire manual regression.