All work
Case study

Teams for Education during the 2020 remote-learning surge

Customer feedback operations while Teams for Education grew from about 7 million to more than 100 million monthly active users during school closures.

Period
2020 to 2021
Organization
Microsoft Education Engineering, World Wide Engagement team
My role
Program manager (vendor)

Context

When schools closed in 2020, Teams for Education grew from about 7 million to more than 100 million monthly active users in a very short time. I joined Microsoft Education Engineering in April 2020 as a program manager on the World Wide Engagement team and stayed for 19 months.

The problem

Critical bugs affected remote learning for whole countries at once. Educators needed features urgently, and engineering needed to know which bugs and requests mattered most across very different education systems.

What I did

  • Operated 24/7 shifts with the team to capture, triage and route customer feedback to engineering.
  • Built the systems that separated critical bugs and features from the rest, so engineering received data-driven priorities: what to ship, what to fix first, where to scale.
  • Kept direct communication with key education customers through the crisis.

What the team and the product did

Engineering scaled and stabilized the platform and the product teams shipped the features educators were asking for. My part was the feedback loop and the priorities it produced.

Scale and outcome

  • Teams for Education went from about 7 million to more than 100 million monthly active users.
  • The platform stayed usable through the most critical period of remote learning: educators could teach and students could learn.

What it means for a district

In a crisis, the loop between your IT team and the vendor matters more than the feature list. Have the feedback channel in place before you need it, and make your reports specific: tenant, scenario, number of users affected, what you have already tried.

Evidence

Last reviewed October 27, 2026.