Light coordination through existing channels
Minimal overhead, but execution stays uneven with no office accountable for integration.
The operating problem
What leadership was facing.
Microsoft was maturing System Center Mobile Device Manager 2008 through live enterprise deployments rather than lab validation alone. Across thirty customer environments and three deployment cycles, software, devices, partner services, communications, and customer feedback all had to move in step — across product development, field sales, marketing, mobile operators, device makers, and integration partners. Pilot activity existed; operating control did not.
Options on the table
The decision, framed honestly.
Reduce to a small showcase set
Simpler coordination, but narrows deployment learning and weakens the release-maturity mechanism.
Lightweight PMO across the full pilot motion
One governing layer for execution, reporting, communications, feedback capture, and dependency management.
What I put in place
The structure behind the outcome.
- Established the planning and execution framework and program handbook for the full pilot motion
- Administered program portal access, software availability, and communication channels
- Coordinated partner recruitment, service alignment, and customer feedback intake across successive iterations
- Maintained engagement status, newsletters, reporting flow, and conference cadences for leadership visibility
- Directed a five-person vendor team handling partner engagement, feedback mechanics, and device logistics
What changed
The operating difference.
Software, devices, services, communications, and feedback ran through one repeatable rhythm. Defect and capability signal flowed reliably into successive builds, and leadership gained a live control surface for progress, blockers, and next actions instead of reconstructing status from scattered tools.
Why it mattered
The executive read.
The product was being matured through live enterprise use, which requires an operating model, not just partner support and customer participation. The governing layer made a complex, partner-led pilot ecosystem usable for release maturity.
Related operating proof:
Partner ecosystem governance route
Launch readiness review
Continue