為您的 Microsoft 團隊採納定義結果與成功Define outcomes and success for your Microsoft Teams adoption

針對您現代化的每個商務案例或服務,請務必定義您的企業成功外觀。For every business scenario or service you modernize, it is critical to define what success looks like for your business. 當您在前一階段中進行對應時,您會收集初始案例的相關資訊。You will have gathered that information for your initial scenarios as you mapped them in your prior phase. 在您針對比例實現進行準備時,您必須重新進行,並展開這些重要的成功準則。As you prepare for your scale implementation, you will need to revisit and expand these important success criteria.

以下是對應準則的建議策略。What follows is a recommended strategy for mapping these criteria. 此步驟有許多有效的方法。There are many valid approaches to this step. 您可以遵循我們的指南,或遵循您可能正在使用的 Microsoft 合作夥伴指南。You can follow our guide or follow the guide of the Microsoft partner you may be working with. 無論您選擇哪一種方法,都要確定您的服務的技術實施及貴組織的整體目標支援您的商業成果。Whatever method you choose, make sure that your business outcomes are supported by the technical implementation of your services and overall objectives of your organization.

有四種類型的結果可為您的企業設定優先順序。There are four categories of outcomes that can be prioritized for your business. 它們相互關聯,並形成個別員工將體驗的現代化與數位轉換基礎。They are interconnected and form the foundation of the modernization and digital transformation that individual employees will experience.

說明四個結果類別的圖表

每個類別中的結果範例如下:Example of outcomes in each category are:

  • 組織性Organizational

    • 文化轉換Cultural transformation
    • 員工保留Employee retention
    • 人才收購Talent acquisition
    • 社交活動Social engagement
    • 操作靈活性Operational agility
  • 文化Cultural

    • 員工觀點Employee sentiment
    • 員工建議Employee recommendations
    • 客戶意見反應Customer feedback
    • 革新性測量 (例如,想法論壇發佈、hackathons、產品創新預訂) Innovation measures (for example, idea forum contributions, hackathons, product innovation engagements)
  • Tangible

    • 客戶經驗影響 (較快的服務、減少服務事件、客戶參照/忠誠度計畫參與) Customer experience impacts (faster service, reduction in service incidents, customer referral/loyalty program participation)
    • 成本節約Cost savings
    • 收入產生Revenue generation
    • 資料安全性Data security
    • 處理常式簡化Process simplification
    • 停用舊版系統Retirement of legacy systems
  • Individual

    • 使用所需的工具Use of desired tools
    • 員工士氣Employee morale
    • 員工生產力Employee productivity
    • 員工參與Employee engagement
    • 想法產生Idea generation

一般來說,您應該考慮使用這些方法來匯總,以這種方式為貴公司建立變更商:In general, you should think of these measures aggregating to create a change quotient for your company in this manner:

由個別觀點分割的有形量值 = 變更商

選取服務啟用戰略Select a service enablement strategy

團隊是一種 transformative 技術,所以根據貴組織的規模與現有的技術,您可能會採用不同的方法。Teams is a transformative technology, so depending on the size of your organization and your existing technologies, you may take different approaches. 請考慮下列戰略:Consider these strategies:

團隊優先Teams First 團隊核心Teams Core 團隊變大Teams Go Big 並排 SkypeSkype Side by Side 移轉Migration
與小組領導雲端部署Lead cloud deployment with Teams 團隊領導共同作業案例Lead collaboration scenario enablement with Teams 團隊和組織範圍團隊中的所有員工All employees on Teams and organization-wide teams 啟用團隊和商務用 SkypeEnable Teams and Skype for Business 從商務用 Skype 將使用者遷移至團隊Migrate users from Skype for Business to Teams
-適用于新的或低使用量 Microsoft 365 或 Office 365 客戶- Applicable to new or low usage Microsoft 365 or Office 365 customers
-在客戶特定案例中靠團隊打頭陣- Lead with Teams in customer-specific scenario
-針對 Microsoft 365 或 Office 365 醒目提示整合的使用者經驗及加速的價值- Highlight integrated user experience and accelerated time to value for Microsoft 365 or Office 365
-配合規劃工作負載來避免串列實現- Conduct planning workload enablement together to avoid serial implementation
-啟用團隊以及 OneDrive 和 SharePoint Online- Enable Teams along with OneDrive and SharePoint Online
-使用 Microsoft Stream 建立公司內部網路以共用新聞資源和影片- Create a company intranet to share news resources and video with Microsoft Stream
更好地搭配Better together:
TeamsTeams
SharePointSharePoint
YammerYammer
PlannerPlanner
PowerAppsPowerApps
-針對低於5000座位的客戶 (目前的限制) - For customers with less than 5000 seats (current limitation)
-啟用跨組織與一個團隊共同作業- Enable cross organization collaboration with one team for all
- (度假要求、員工調查、管理參與等作業自動化常見工作) - Automate common tasks (vacation requests, employee surveys, executive engagement)
-使用團隊核心戰術來加速共同作業- Use Teams Core tactics to accelerate collaboration
-根據所需大小和功能集醒目提示會議案例指引- Highlight meeting scenario guidance based on size and feature set required
-使用商務用 Skype 進行企業通話、互通性及混合式案例- Use Skype for Business for enterprise calling, interoperability, and hybrid scenarios
-使用公用藍圖進行功能規劃。- Use public roadmap for capability planning.
-規劃從商務用 Skype 移至團隊,方法是建立客戶的服務戰略藍圖- Plan move to Teams from Skype for Business by creating service strategy roadmap for the customer
-附加至功能版本排程- Attach to feature release schedule
-建議包含並排和小組核心,以簡化轉場- Recommend including Side by Side and Teams Core to ease transition

以下是我們針對大多數客戶組織的建議。The following are our recommendations for most customer organizations. 不過,也有例外狀況。However, there are exceptions. 若要針對此處未提及的任何案例取得指導方針,請在我們的推動採用群體中提出您的問題,或與 FastTrack 小組或 Microsoft 合作夥伴網路取得聯繫。To get guidance for any scenario not covered here, ask your questions in our Driving Adoption community or reach out to the FastTrack team or Microsoft partner network.

  • 選擇 [團隊優先] 或 [團隊核心]:大多陣列織都在 Microsoft 技術中擁有現有投資。Choose Teams First or Teams Core: Most organizations have an existing investment in Microsoft technology. 您可能一次啟用一個以上的工作負荷,例如 Exchange Online、商務用 OneDrive 或 SharePoint。You may be enabling more than one workload at a time, such as Exchange Online, OneDrive for Business, or SharePoint. 在這些情況下,選取 [團隊優先] 或 [團隊核心] 是明智的選擇。In these cases, selecting Teams First or Teams Core is a wise choice. 它可讓您的使用者使用增強的小組共同作業體驗。It will enable your users to get used to the enhanced collaboration experience of Teams. 然後,您的共同作業專案小組可以計畫推出其他功能,以及他們成功所需的訓練與支援。Your collaboration project team can then plan to roll out additional capabilities and the training and support required for them to be successful.

  • 選擇 [團隊最大 的功能]:在新的 Microsoft 365 或 Office 365 客戶組織中,通常最好將小組最大限度地減少學習新技術所造成的變更 fatigue。Choose Teams Go Big: In new Microsoft 365 or Office 365 customer organizations it is often best to take a Teams Go Big approach to minimize the change fatigue caused by learning new technology multiple times. 您可以為核心共同作業和會議、SharePoint、OneDrive、Planner 及其他工作負載提供最大的好處,讓員工能在小組部署的內容中瞭解這些專案。You'll get the greatest benefit by enabling Teams for both core collaboration and meetings, SharePoint, OneDrive, Planner, and other workloads, and allowing your employees to learn about them in the context of your Teams deployment.

    團隊也是最大的,也就是那些想要簡化員工溝通與接洽之1000員工的最佳支援策略。Teams Go Big is also the preferred enablement strategy for organizations under 1,000 employees who want to simplify their employee communication and engagement. 使用組織範圍的小組可以讓人員共同查看任何裝置上的一般工作與計畫。Using the organization-wide team can bring people together to review common tasks and initiatives on any device.

  • 選擇 [ 並排]:適用于使用商務用 Skype 進行音訊會議、會議室裝置支援或雲端語音功能的組織,我們建議您執行團隊和 Skype,以讓您的員工掌握核心共同作業功能,同時從商務用 skype 開始規劃您的公司。Choose Side by Side: For organizations that are using Skype for Business for audio conferencing, support for conference room devices, or cloud voice capabilities, we recommend running Teams and Skype side by side to familiarize your employees with the core collaboration features, while planning your migration off of Skype for Business at a time that is convenient for your company. 請注意,並排執行這兩個用戶端可能會對使用哪個工具造成使用者混淆,因此我們建議您在採用歷程中將此階段保持簡短。Note that running both clients side by side can introduce user confusion about which tool to use, so we recommend keeping this phase in your adoption journey short.

  • 選擇 [遷移]:從商務用 Skype 遷移至團隊從技術角度來看,還有其他元件,但使用者採納歷程與團隊成為大型實現的元件一樣。Choose Migration: Migrating from Skype for Business to Teams has additional components from a technical perspective, but the user adoption journey has the same components as a Teams Go Big implementation. 此外,您還會針對團隊會議經驗和介面、新的持續聊天行為,以及與商務用 Skype 不同的其他體驗的其他元素進行教育。In addition, you will be educating people about the Teams meeting experience and interface, the new persistent chat behavior, and other elements of the experience that are different from Skype for Business.

針對每個啟用戰略,與您的技術就緒小組密切合作,以確保您的環境能提供良好的員工體驗。For each enablement strategy, it's essential to work closely with your technical readiness team to ensure that your environment will deliver a great employee experience.

代表決策點的圖示 決策:選取最能支援 Microsoft 團隊商業結果的支援戰略,且可由您的技術實施小組啟用。Decision: Select an enablement strategy that will best support your business outcomes for Microsoft Teams and that can be enabled by your technical implementation team. 這是 IT 領導、計畫管理主管及使用者採納專家之間的共同決策。This is a joint decision between IT leadership, program management leads, and user adoption specialists. 這個決定通常是與組織中 Microsoft 團隊或共同作業服務的最終成功擁有者有關的主管股東。This decision often rests with the executive stakeholder who is the ultimate success owner for Microsoft Teams or collaboration services in your organization.

最佳做法:啟用戰略可適合您的專案或部門實施排程的指定階段。Best Practice: Enablement strategies can be appropriate for a given phase of your project or divisional implementation schedule. 使用主要角色和它們的需求來進行選擇。Use key personas and their needs to make selections. 與您的技術實施小組密切合作,以確保您的使用者具備高品質的體驗。Work closely with your technical implementation team to ensure a high-quality experience for your users.

與干係人接洽Engage stakeholders

溝通與管理期望是成功變更專案中的主要元素。Communication and managing expectations are key elements in a successful change project. 定期向您的專案關係人及貴組織中的其他人通報您的整體願景及您的目標,是非常重要的。It's important to regularly communicate your overall vision and your progress toward that goal to your stakeholders and others in your organization.

代表決策點的圖示 決策:請決定您的律動與與您的專案關係人進行通訊的方法,與您的公司文化。Decision: Decide your rhythm and method for communicating with your stakeholders in alignment with your company culture. 在您的組織中,將您的通訊目標設定為各種不同的交往等級和興趣。Target your communications to the various levels of engagement and interest across your organization.

選項:若要建立有關您專案之資訊的持續知識庫,請考慮在 SharePoint 通訊網站中使用新聞頁面。Option: To create an ongoing knowledge base of information about your project, consider using news pages in your SharePoint communication site. 您的 [資訊] 頁面庫 (與您規劃小組相關聯之 SharePoint 網站中的網站頁面) 可以公開,讓他們可以與所有感興趣的方共用。Your news page library (site pages in the SharePoint site associated with your planning team) can be made public so they can be shared with all interested parties.

拓展您的實施團隊Expand your implementation team

在大型組織中,您應該嘗試在廣泛的啟用階段中加入許多不同的角色。In a large organization you should try to incorporate many different roles in your broad enablement phase. 這可能包括其他業務贊助商、IT 支援人員、您的擁護者社區中的其他成員,以及在某些情況下正式變更管理或訓練人員。This may include additional business sponsors, IT support staff, additional members in your champion community, and in some cases formal change management or training personnel. 下圖顯示的是大型的採用小組,可讓您進行職責分隔。The illustration below shows a large scale adoption team that allows for a separation of duties.

大型企業採用小組模型的圖例

在較小的組織中,一或多個角色可能由單一個體所執行,但所需的技能保持不變。In a smaller organization one or more of these roles might be performed by a single individual, but the skills required remain the same. 在成功的變更專案中,技術、溝通及訓練技巧都很重要。Technical, communication and training skills are important in a successful change project.

展開您的管理與資訊管理原則Expand your governance and information management policies

一旦您已選取您的啟用戰略,您就可以隨時在階段1中重新討論並調整您所做的管理決策。Once you've selected your enablement strategy you'll be ready to revisit and scale governance decisions you made in Phase 1. 從「 管理快速入門」 重新取得決議1到6,以將這些原則與將使用團隊的商務使用者對齊。Revisit decisions 1 through 6 from the Governance quick start to expand these policies in alignment with the business users who will be using Teams.

小組層次Team level 範圍/用途Scope/purpose 標準成員資格Standard membership Duration
等級1Level 1 分部或公司單位的權威性小組The authoritative team for a division or business unit 通常僅限於此分部/單元的正式成員Usually restricted to official members of this division/unit 在 perpetuity 中,只要該部門存在 (例如,IT 部門、人力資源、行銷) In perpetuity for as long as the division exists (for example, IT department, Human Resources, Marketing)
層級2Level 2 具有較小範圍的專案、服務或方案小組Project, service, or initiative teams with a smaller scope 通常跨組織且可能包含來賓Normally cross-organizational and may include guests 只要處理該專案或服務,就能完成For as long as that project or service is being worked on
層級3Level 3 時間點專案Point in time projects 含個別範圍的小型緊密高階小組;可能包含來賓Small tight knit team with individual scope; may include guests 在核心交付專案中受短期的生命週期限制Short lifecycle tied to core deliverable

小組階層的資源調配與管理最佳做法範例:Example team level provisioning and management best practices:

小組層次Team level 誰建立?Who creates? Lavels 和保留Lavels and retention 考量Considerations
階層 1-部門Level 1 - Divisional 該群組的 IT 或擁護者將其命名為適當的名稱IT or champion for that group to name it properly 已套用標準保留原則及1年更新原則的機密Confidential with standard retention policy applied and 1 year renewal policy 您可以考慮這樣做,就像保留功能變數名稱一樣。Think of this like reserving a domain name. 您想要控制分割團隊的命名方式,以及包含哪些專案。You want control of how division teams are named and what's included. 在新增其他使用者之前,請先設計小組。Design the team before adding additional users.
層級 2-專案/服務Level 2 - Project/service 專案擁有者或擁護者Project owner or champion 機密或高度機密(視內容而定)。Confidential or highly confidential depending on content. 可能會有保留原則。May have a retention policy. 6個月續約。6 month renewal. 建立之前,請先考慮在您正在處理的專案或服務邊界以外。Before creating this, think just beyond the boundary of the project or service you are working on. 要將其他團隊的強制結合起來,是否有更多的意義?Would it make more sense to combine forces with another team? 您可以在處理相同的專案或服務時,最大限度地減少個別使用者必須造訪的小組數。Make every effort to minimize the number of teams individual users have to visit when working on the same project or service.
第3層-小型隨選項目小組Level 3 – Small on-demand project team 組織中的任何人Anyone in the organization 含標準保留與6個月續約的一般標籤。General label with standard retention and 6 month renewal. 可能會包含命名慣例 (前置詞/尾碼) May include naming convention (prefix/suffix) 自助需求團隊。Self-service on demand teams. Frictionless 提供]。Frictionless provisioning. 這些可讓小型專案團隊順利共同共同作業及溝通,想要透過公司提供的服務立即取得價值。These facilitate smooth collaboration and communications for small project teams looking to get immediate value from company provided services.

簡化商務活動Streamline business engagement

在 Microsoft 團隊中,驅動數位轉換和使用的重要部分是與您的營業單位合作,瞭解他們的需求、機遇和困難。An essential part of driving digital transformation and usage in Microsoft Teams is working with your business units to understand what needs, opportunities, and difficulties they have. 與傳統的 IT 與業務交談類似,您的重點應該視需要而定。While similar to the traditional IT to business conversation, your focus should be on what is needed. 請聆聽,然後再移至技術需求。Listen before moving to technical requirements. 在許多情況下,小組中的 [外框] 功能將會符合貴組織的需求。In many cases, out of the box features in Teams will meet the needs of your organization.

最佳做法:在考慮開發自訂方案之前,請確定貴組織已完全使用 Microsoft 365 或 Office 365 的全新功能。Best practice: Before you consider developing a custom solution, be sure that your organization is fully using the out-of-the-box capabilities of Microsoft 365 or Office 365. 自訂方案開發對於您的 IT 和支援部門而言,永遠都是長期成本。Custom solution development always incurs long term cost for your IT and support departments.

採取下列步驟,簡化您的工作與業務單位的合作。Take the following steps to streamline your work with business units. 認識到在超大型大型企業中,這個程式可能會在您第一次大型部署 Microsoft 團隊後持續很長的時間:Recognize that in very large, multi-national corporations this process may continue long after your first large scale deployment of Microsoft Teams:

  1. 在吸引主管人員深入瞭解及對齊前,與業務單元中的重要影響者見面。Meet with key influencers within a business unit before engaging the executive to gain insight and alignment.
  2. 瞭解其目前適用于常見案例 (電子郵件、SharePoint、Yammer 及其他產品) 的解決方案。Understand their current solutions for common scenarios (email, SharePoint, Yammer, and other products).
  3. 在縮放時,選取對應高影響、低/中難度的案例,即可開始小型Start small by selecting scenarios that map to high impact, low/medium difficulty as you scale,
  4. 捕獲意見反應,並使用業務單元知識開發擁護者以支援轉場。Capture feedback and develop champions with business unit knowledge to support the transition,
  5. 設定每月檢查點以討論進度,以及排定其他專案的待辦事項的優先順序。Set up monthly check points to discuss progress and prioritize the backlog of additional projects.

代表下一個步驟的圖示 優化意見反應與報告An icon representing the next step Next: Optimize feedback and reporting