Why Do Microsoft Technology Evangelists use StepShot?

Why Do Microsoft TechnologyEvangelists use StepShot? 

Why Do Microsoft Technology Evangelists use StepShot? 

Microsoft Developers’ Experience Team (DX) in Central and Eastern Europe is a 15-year old organization that works with the vendor’s developer ecosystem partners. Also previously known as Developer and Platform Evangelism (DPE) group. Microsoft created DPE in 2001 with a goal of getting software developers excited about – and see the opportunity in – building apps on the Microsoft platform with Microsoft’s tools.

THE PRODUCTIVITY BOOST IN USER GUIDES CREATION IS NOTICED. ON AVERAGE THE USER GUIDES CONSIST OF 30-40 STEPS AND IT TAKES ONLY 2-4 HOURS TO CREATE ONE. STEPSHOT IS USED ON A WEEKLY BASIS.

The biggest value of StepShot personally for me is that I don’t have to switch between different contexts. The product allows me to stay focused on the workflow I am documenting.

Alexander Belotserkovskiy
Technical Evangelist: Cloud,

Executive Summary

DX is a team whose focus cuts across many different Microsoft product and services groups, and its engineers are tasked with knowing just about everything the company is doing. That explains why team members are called Technical Evangelists.

Technical Evangelists are heavily involved in various technical projects including content creation, technical engagement with key partners, startups, enterprise customers. Most platform technologies around Cloud are covered, mainly in early adoption phase to help in early migration, development, deployment and architecture.

For successfully meeting their goals, Developer Outreach Team share their knowledge via articulate, effective, and audience-appropriate presentations/demonstrations with technically oriented content at various events to both small and large audiences. Content is also aimed at conveying compelling and convincing case for Microsoft technologies.

How Product Helped

Those who decided to ease the pain of manual creation of extensive technical user guides have got across StepShot. The information about the product got quickly spread by word of a mouth among the DX team.

The old usual approach of getting things done with Word, PrtSc and Paint could have taken half of the day. With StepShot, user guides are created twice quicker now.

Technology Evangelists especially value the possibility of staying focused on the workflow which is documented. StepShot’s core functionality allows to create instructions and user manuals with no interruptions from the actual process. It just follows Technology Evangelists going through the software workflows and captures them in the sequence of screenshots.

Challenges

Technology Evangelists daily deal with developers, system admins and other technically savvy guys who use Microsoft products in their work. Responsible for their experience, the DX team often shows demos, explaining complex and new features to the broad community of developers. Discussions and demos are also the ways of interaction with Microsoft partners.

The obvious biggest challenge when dealing with developers is that Technology Evangelists often need to repeat the same information over and over again. Thus, the most popular topics are covered either in videos or user-guides. Among the main disadvantages of videos as compared to user guides are the huge video traffic, video processing and set-up, no possibility to edit the final version and others.

When it comes to the user guides creation within DX team, there is no strict and official standard about the format of the final material. So, any approach in creation of guides is applicable – be it just copy & paste of a screenshot in Word or the usage of a tool for the creation of step-by- step user guides.

Results and Benefits

StepShot has been tested within the organization for several months. And now it is used in the DX team in Central and Eastern Europe team on a corporate level.

The productivity boost in user guides creation is noticed. On average the user guides consist of 30-40 steps and it takes only 2-4 hours to create one. StepShot is used on a weekly basis.

Great results and time saved within the DX team can provide the use case for StepShot implementation within Microsoft documentation department to handle software implementation and releases documentation.