{"id":7077,"date":"2023-09-07T09:01:53","date_gmt":"2023-09-07T16:01:53","guid":{"rendered":"https:\/\/www.microsoft.com\/insidetrack\/blog\/?p=7077"},"modified":"2023-09-07T09:41:58","modified_gmt":"2023-09-07T16:41:58","slug":"digital-transformation-through-mastery-of-the-microsoft-employee-experience","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/insidetrack\/blog\/digital-transformation-through-mastery-of-the-microsoft-employee-experience\/","title":{"rendered":"Digital transformation through mastery of the Microsoft employee experience"},"content":{"rendered":"
Digital transformation is an important topic for most organizations, and we\u2019re often asked to share the specific steps that we have taken to transform the Microsoft employee experience in Microsoft Digital Employee Experience, the organization that powers, protects, and transforms Microsoft. This series highlights how we accomplished this internally across two key pillars of the digital transformation journey: empowering employees and transforming operations.<\/p>\n
At the heart of this transformation is an obsession with the Microsoft employee experience.<\/p>\n In our view, the employee experience is a nexus where personal needs and employee needs are both met. When this is great, employees are highly satisfied with the experience and are very productive. The activities that hit the mark on this range from generic experiences applicable to all employees\u2014like finding available meeting rooms, searching for internal information, or understanding their benefits\u2014to more role-specific experiences, like manager insights to support their teams or loading sales data into a CRM system.<\/p>\n The employee experience isn\u2019t limited to day-to-day activities; it\u2019s considered throughout the employee\u2019s lifecycle: from onboarding and internal role changes through to retirement.<\/p>\n A keystone to empowering employees in how they do their jobs is to understand what employees need by identifying their top challenges and successfully meeting their needs. Before our digital transformation advanced in earnest, we would make changes without fully understanding whether they met our employees’ needs and we often wouldn’t do enough to help them adapt to the changes. This was met with limited success.<\/p>\n Getting to a better place required a change in mindset, as shared by Microsoft CEO Satya Nadella: \u201cAs a culture, we are moving from a group of people who know it all to a group of people who want to learn it all.\u201d To learn it all, we began establishing listening mechanisms to learn from our employees, recognizing that as technologies advance, employee expectations of their devices and experiences advance as well, with increasing expectations that both work seamlessly to enable them to do their best work.<\/p>\n [Read the second blog in the series on how Microsoft is transforming the company’s employee experience by listening to employee signals<\/a>. Read the third blog in the series on how investment prioritization is driving the transformation of Microsoft\u2019s employee experience.<\/a> <\/em>Learn how Microsoft Digital is reinventing the employee experience at Microsoft.<\/em><\/a>]<\/em><\/p>\n When we started down the path of understanding our employees\u2019 needs, we realized we had to develop a comprehensive set of employee signals first. To us, signals are indicators of employee satisfaction with the tool or service. Examples of signal sources include employee survey data, direct interviews with employees or leaders, and product usage data (we\u2019ll explore these sources in greater detail in a moment). Our strategy relied on some signal sources that were already in place, but to meet our goals, we expanded our sources to ensure we listened to all employees.<\/p>\n Being a global enterprise, we had to consider our many cohorts of employees\u2014all countries and regions; all roles, including individual contributors, managers, and leaders; the locations of all workers, including remote, in-office, and hybrid. We needed to make sure we didn\u2019t exclude picking up signals from any group.<\/p>\n We used existing data trends to understand our employees without disrupting them (such as telemetry and usage data). This informed an initial indication of where pain points or adoption blockers might be.<\/p>\n We also needed to hear directly from our employees to confirm or alter those initial impressions, so we established several proactive mechanisms to gather feedback. The following diagram shows an example of some of the signal types used to gather this data. We will explore some of those listening signals more here.<\/p>\n We gather proactive signals preemptively, and they\u2019re critical in helping us understand what our employees think. Here are several ways we proactively gather those signals and some of the expected outcomes we have for them:<\/p>\n Reactive signals come from employees sharing their feedback and needs either directly or indirectly through their interactions with tools, and are a source of direct evidence of how they actually use a product or service:<\/p>\n By evaluating reactive and proactive signals, we can connect what employees say<\/em> with how employees act<\/em>. Consider this example. Last year, more than 40 percent of support calls for our primary sales system were related to access or login issues. This amount of volume alone had significant productivity, satisfaction, and operating cost implications. And the volume of these reported issues was growing.<\/p>\n At first glance, it may seem that this was a simple access issue. But it was through analysis of additional proactive and reactive signals\u2014like business reviews and social channels\u2014that we saw the challenge was beyond just these access issues. It wasn\u2019t just a technical issue; it really was a training issue. Without that deeper analysis, we would have addressed the wrong problem.<\/p>\n In the subsequent articles that comprise this series, we will share the steps we took to change our approach by listening to our employees and demonstrating how we addressed some of their biggest pain points. Here\u2019s what you can expect in each article:<\/p>\n Digital transformation at Microsoft will continue as our business evolves and emerging technologies like AI and machine learning offer new avenues to accelerate that change. What won\u2019t change is our foundational commitment to learn, grow, and obsess about not only our customers but also our employees. We\u2019re excited to show you how.<\/p>\n Digital transformation is an important topic for most organizations, and we\u2019re often asked to share the specific steps that we have taken to transform the Microsoft employee experience in Microsoft Digital Employee Experience, the organization that powers, protects, and transforms Microsoft. This series highlights how we accomplished this internally across two key pillars of the […]<\/p>\n","protected":false},"author":104,"featured_media":7080,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_hide_featured_on_single":false,"_show_featured_caption_on_single":true,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[596,137,89,597,599,593,598,592,595,594],"coauthors":[591,590],"class_list":["post-7077","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-analysis","tag-change-management","tag-digital-transformation","tag-employee-experience","tag-feedback","tag-listening","tag-prioritization","tag-prosci","tag-research","tag-signals","program-microsoft-digital-perspectives","m-blog-post"],"yoast_head":"\nStrategies for capturing employee signals<\/h2>\n
Proactive employee signals<\/h2>\n
\n
Reactive employee signals<\/h2>\n
\n
Connecting what employees said with how employees acted<\/h2>\n
Building on the foundation<\/h2>\n
\n
<\/p>\n
\n