Launching Windows Phone for Developers
Project type: Developer platform launch
Role: Content Publishing Manager
Focus: Developer documentation, code samples, web experience, content strategy, publishing operations, and cross-team leadership
Timeline: 2009-2011
OPPORTUNITY
Windows Phone 7 represented a major reset of Microsoft’s mobile developer platform. Developers needed more than API reference material. They needed a clear path for getting started, practical code samples, design guidance, publishing support, and a more cohesive experience across the SDK, Visual Studio, MSDN, and App Hub.
The challenge was to build that experience while the platform itself was still evolving. Content was spread across teams such as Silverlight, XNA, Marketplace, application platform, and developer tools, creating a risk of duplication and confusion. The goal was to give developers one authoritative experience that made the new platform feel approachable, complete, and ready for application development.
Role
I led the Windows Phone developer content team and the strategy for the platform’s documentation and web experience. I was responsible for the documentation plan, release schedules, content coordination, team leadership, and alignment across engineering and partner organizations.
My work included coordinating content across Silverlight, XNA, Marketplace, App Hub, Visual Studio, and other Microsoft teams; defining the developer learning experience; reducing outdated and duplicated content; supporting localized documentation; and helping ensure that developers could find authoritative guidance both online and inside the development tools.
I also helped establish the operating model needed to support the platform after launch, including site management, partner coordination, content rationalization, and continuous publishing across multiple product releases.
APPROACH
We treated documentation as part of the developer product experience rather than as a separate publishing deliverable.
The team organized the content around the tasks developers needed to complete: getting started, understanding the platform, designing the user experience, working with APIs, using code samples, testing applications, meeting certification requirements, and publishing to the marketplace.
We published multiple prerelease versions so developers and partners could use the guidance before the final product shipped. We also coordinated the launch and ongoing operation of App Hub, created developer resource pages, established a content partnership council, and worked across Microsoft to reduce fragmentation between App Hub and MSDN.
After the initial Windows Phone 7 launch, customer feedback shaped the strategy for Windows Phone 7.5 (mango). We concentrated investment in four areas developers were asking for most: UX design, certification guidance, walkthroughs, and code samples.
RESULTS
The team shipped the initial Windows Phone developer documentation through several prerelease milestones and the final public launch. Early developer feedback indicated that the platform was easier to get started with, and the documentation became part of the broader developer adoption story.
For Mango, the revised strategy produced a 250% increase in code samples and a 300% increase in developer walkthroughs. The documentation generated approximately six million page views and received an average rating of 3.7 out of 5.
The broader delivery included 52 code samples, 40 tutorials, 10 podcasts, and two books. The team also created a continuous publishing plan that supported overlapping releases rather than treating documentation as a one-time launch activity.
The work helped create a more coordinated developer experience across documentation, samples, web resources, and marketplace publishing, while building stronger relationships among teams that had previously delivered content independently.
LESSONS LEARNED
This project reinforced that developers evaluate a platform partly by how quickly they can become productive with it. Accurate API reference is essential, but it is not enough. Developers also need a clear starting point, real examples, practical walkthroughs, consistent navigation, and confidence that the guidance will continue to improve after launch.
It also showed the importance of treating developer content as a cross-company product. No single team owned the complete experience, so success depended on shared priorities, clear decision-making, strong partnerships, and the willingness to resolve duplication between organizations.
Finally, publishing early and listening to developer feedback materially improved the work. The strongest gains came when the team shifted investment toward the formats and topics developers were actively requesting.
RIP Windows Phone. It was an innovative platform with a distinctive user experience, but even a strong product can struggle when the surrounding ecosystem never reaches the scale needed to sustain it.