FY20 Solution Taxonomy Microsoft Confidential

Transcript:FY20 Solution Taxonomy Microsoft Confidential:
FY20 Solution Taxonomy Microsoft Confidential File: aka.ms/FY20Taxonomy Table of Content Taxonomy Design Principles Business Goals One company, one language. Define a common language across OCP, M&O, BG, Services, ATU, STU & CSU leveraged for processes/assets with a clearly defined cross-company taxonomy Simplify & Clarify. Simplify and clarify the GTM, build-with and sell-with taxonomy language that resonates with customers, partner and MSFT internal audiences Continuity. Define a clear path to migrate the current model and solution classification, across process/assets/tools, without disrupting or overloading our execution Actionability. Ensure a level of taxonomy that enables high level ecosystem analysis, as well as depth for insights and local mobilization Taxonomy Guiding Principles Supports Industry, Solution Area and Category ongoing business strategy Agile, evergreen approach Reflect the optimal customer experience across storefronts Managed through cross-org governance Simple and clear – less is more Enables other audiences to easily align and adopt Consistent Taxonomy across all Systems Capacity Planning and Partner Enablement Customer Engagement Business Planning and Execution Sales Enablement Three layers architecture based on Solution Area, Priority Scenario and Technical Scenario. When looking at solutions for a given priority scenario, it is important to select the proper technical scenarios that will determine what the partner, or Microsoft Services, is delivering within the selected scenario. This is also the level where any capabilities view should be plugged. Requirement: Mandatory to select one Priority scenario and Technical Scenario for a new engagement. Three layers architecture based on Industry, Vertical and Industry Solution Category. Partner solutions are categorized against Solution Categories within a specific Vertical. Priority Scenarios are comprised of several Industry Solution Categories. They represent the prioritized DT business conversations based on industry trends. Requirement: Select an Industry Solution Category for a new engagement with clear industry focus (Optional). Solution Area Modern Workplace Biz Apps Azure Industry Taxonomy Structure and Definitions Priority Scenario n Solution Area Priority Scenario 1 Industry Vertical n Vertical 1 Vertical 2 Priority Scenario 1 Industry Solution Category n Technical Scenarios n Priority Scenario 2 Priority Scenario 2 Industry Solution Category 1 Industry Solution Category 2 Industry Solution Category 3 Industry Solution Category 4 Technical Scenarios 1 Taxonomy Definitions SA and Industry Summary FY20 Solution Area Taxonomy Priority Growth Modern Workplace Business Applications Azure FY20 Industry Priority Scenarios, IPS Enterprise Commercial Enterprise Commercial Public Sector Notes: Renamed Industry in FY20 New Vertical in FY20 L1: Industry (8) FY20 Industry Solution Categories, ISC (1