Microsoft Events
A clearer system helps great teams move faster.
- Context
- Microsoft Events Sponsorship
Context
Context
As Microsoft’s event sponsorship programs grew, so did the creative work required to support them. Deliverables crossed multiple teams, vendors, channels, and approval processes.
The team needed more than the capacity to produce more creative. Everyone needed to see what was happening, what needed attention, and who was responsible.
My role
My role
I designed the operating model and helped put it in place: intake, prioritization, production, approvals, and delivery in one shared view.
I stayed close through adoption, shaping the system around how the team actually worked rather than asking the team to work around the system.
The approach
The approach
Start with how the work actually moves. Where do requests come in? Where do decisions stall or responsibility become unclear?
Build around that: one intake path, visible priorities, and clear ownership through production, approval, and delivery.
The result
The result
The growing team had one shared view of the work. They could see what was happening, what needed attention, and who owned it.
The workload didn’t disappear. The uncertainty became easier to manage.
