Context

As the use of scenario-based tasks expanded, the portfolio grew rapidly in size and complexity across multiple administrations. At the same time, requirements, blueprints, and program priorities continued to evolve.

Planning and delivery were happening in parallel, creating challenges in coordination, alignment, and execution across teams.

Role & Scope

I stepped into a portfolio-level role, supporting delivery of 60+ scenario-based tasks and configurable math component applications across multiple administrations.

Responsibilities included:

• acting as primary point of contact for SBT production
• recruiting, onboarding, and supporting a growing team
• managing intake, negotiation, and alignment of evolving requirements
• coordinating across federal clients and cross-contract stakeholders
• supporting delivery across engineering vendors, content teams, QA, and data teams

Approach

Rather than introducing rigid structure, I focused on stabilizing delivery while scaling both the portfolio and the team:

• Managed shifting requirements and program changes while maintaining forward progress
• Supported team growth by aligning roles, responsibilities, and workflows in an evolving environment
• Clarified scope and expectations across teams to reduce ambiguity during development
• Coordinated distributed teams across contracts, ensuring alignment despite differing constraints
• Maintained integrity of implementations, including interoperability, API alignment, and telemetry outputs
• Supported the team through rapid growth, helping scale capacity while maintaining delivery continuity

This work required balancing flexibility and control, enabling teams to adapt while still delivering consistent, production-ready outputs.

Results

• Delivered 75+ interactive applications at national scale across multiple administrations
• Scaled the production team from ~3 to 7.5 FTE, increasing capacity during a period of rapid growth
• Enabled teams to operate effectively under continuously evolving requirements
• Improved alignment across stakeholders, reducing delivery friction and rework
• Maintained consistency in system integration, scoring logic, and telemetry data across implementations
• Stabilized a complex, multi-team delivery environment during a period of rapid growth

Key Takeaway

Effective delivery at scale is not always about imposing structure and vision, it is also growing a functional team and creating enough alignment and clarity for cross-functional teams to move forward, even when the system itself is still evolving.