The “My Teams” series is damaged in to the following groups. Click someone to begin to see the full listing of articles for the reason that category:
John’s intellectual curiosities and passions are only for driving the adoption of cloud services in large US federal organizations. He’s a delivery architect with hands-on expertise and experience on service adoption, Microsoft Teams, and SharePoint Online. Partly ten of the series, we’ll discuss John’s insights on adoption, challenges facing organizations intending to deploy Teams, and experience-driven recommendations.
Name: John S. Moh
Location: Fairfax, Virginia
Current Role: Principal Consultant, Microsoft Services
A word that best describes the way you work: Strangely enough
Mobile phone of preference: iPhone XS Max
Computer of preference: Dell Precision 7510
To obtain began, please inform us just a little regarding your background the way you reached where you stand today.
Jumping over from Avanade at the begining of 2005, I began being an Enterprise Strategy Consultant in Microsoft Services within the Washington Electricity Area. My wish to be more technical then brought me to accomplish the Exchange “Ranger” program (Microsoft Certified Master), landing me on probably the most politically and technically challenging projects within the Public Sector. Eventually, my wish to be globally impactful brought me to Redmond where I shipped Xbox Live like a Senior Program Manager.
Today, I’m during the Electricity Area focusing on service adoption, Microsoft Teams, and SharePoint Online methods to create cookbooks of RSPIs (Reusable Solutions for Productivity and Innovation – pronounced “recipes”). My work could be summarized within this statement: Focus this is not on use, however the effectiveness of cloud services!
How can you engage large federal agencies to appear beyond “trendy terms” and comprehend the true worth of “adoption?”
Because adoption is really a trending subject and term, let’s “quick format” our understanding and obtain on a single page. “Delete” everything you’ve learned about adoption and begin fresh using the Microsoft Service Adoption Specialist course and certification ?! Service Adoption is Microsoft’s response to the issue our customers, partners, and we’ve been asking: How can we drive consumption and adoption of Office 365?
Within this course, the reply is split into six critical elements:
- Business development
- Business acumen
- Technical competence
- Marketing and communications
- Portfolio management
- Leadership capacity
Service adoption is dependant on Microsoft’s research and it is a “how they are driving adoption of Microsoft services inside your org” framework in the Office 365 Engineering Team. Everybody (engineering, marketing, the area, and the remainder of Microsoft) is calibrating for this framework today.
I’ve been interested in technology adoption for any very lengthy time, intentionally taking adoption-focused engagements to achieve real-world experience. Service adoption is when I define adoption as it requires Microsoft cloud services in large federal organizations.
Do you know the top two challenges to effective Microsoft Teams deployments large federal agencies are facing?
Working together culture. We typically use email for all things in large federal organizations, and Outlook continues to be the hub for working together till Microsoft Teams came around lately. Don’t misunderstand me, I still love email (and also have spent a large amount of my career centered on it), however with Teams, email gets to be more valuable, not less. Teams isn’t a substitute for email it isn’t an or, but an and.
Microsoft Teams can improve working together and mission effectiveness with conversations instead of emails and channels instead of file folders, but we have to hinge its release with service adoption. Otherwise, you will see users “fighting using the tool” instead of seeing it as being a helpful tool. “The greatest issue I see across all customers applying Teams is they do not have anybody within their organization focused on Service Adoption.” I’m co-signing this statement from Rima’s publish ?!
Technical Competence. Driving adoption of Microsoft Teams requires technical competence, which requirement amplifies in GCC (Government Community Clouds) where technical abilities featuring aren’t the same as commercial. For instance, we do not have bots. We do not have Flow and PowerApps (yet). We did just get Planner, though, and Stream is originating! Consequently, technical competence—the understanding needed to use a particular technology to some business/mission problem to offer the preferred outcome—is essential-have for anybody driving Teams adoption in large federal organizations. You must realise what’s possible in GCC and hang expectations accordingly. Otherwise, you’ll frustrate users.
How can you suggest agencies exceed finish-user training to make sure a effective Microsoft Teams deployment?
I’ve got a couple of suggestions! For instance, agencies should begin with the finish in your mind and concentrate on small victory laps, splitting governance, and showing greater than telling. But when I needed to select one, it might be this: shift learning and support left. Such as the shift left method of software testing, sturdy moving learning and support motions as near to the user as you possibly can. Microsoft Teams issues are mainly about learning (understanding) versus support (breaking/fixing). So, a peer-to-peer support model is a superb fit. We’ve used a “player-coach*” example effectively previously:
- A person-coach is definitely an embedded “player” (member) and “coach” (owner) of the Microsoft Teams instance.
- He/she’s dedicated to taking part in “train-the-trainer” onboarding, and continuing learning occasions using the Microsoft Teams release team.
- Most significantly, a person-coach would like for everyone other people of his/her team because the first degree of escalation for learning and support.
Recommendations that player-coaches accelerate resolution occasions for users, simplify support escalation processes (reducing overhead), and reduce support costs while maximizing the service adoption experience. I suggest shifting left for just about any large federal organizations about to release Microsoft Teams.
*Note: The word “player-coach” is simply an example and might not be a healthy for the organization’s culture. Be inclusive and develop an example that matches your context!
What’s your very best time-saving shortcut in Microsoft Teams?
You will find a lot of to select one, but allow me to practice what we should preach and demonstrate instead of let you know:
How can you think cloud services, like Microsoft Teams, can change the face area of technology deployments?
Within my field, the way forward for cloud services will pivot on the caliber of the adoption experience. As far as we’ve got the technology has been commoditized, we have to purchase increasing the service adoption (people) experience. For this finish, we’ll possibly see new roles within the future… perhaps a CSAO “Chief Service Adoption Officer” ?.