Select and Implement a Social Media Management Platform

  • Buy Link or Shortcode: {j2store}554|cart{/j2store}
  • member rating overall impact: N/A
  • member rating average dollars saved: N/A
  • member rating average days saved: N/A
  • Parent Category Name: Marketing Solutions
  • Parent Category Link: /marketing-solutions
  • The proliferation of social media networks, customer data, and use cases has made ad hoc social media management challenging.
  • Many organizations struggle with shadow IT when it comes to technology enablement for social media; SMMP fragmentation leads to increased costs and no uniformity in enterprise social media management capabilities.

Our Advice

Critical Insight

  • SMMP selection must be driven by your overall customer experience management strategy; link your SMMP selection to your organization’s CXM framework.
  • Shadow IT will dominate if IT does not step in. Even more so than other areas, SMMP selection is rife with shadow IT.
  • Ensure strong points of integration between SMMP and other software such as CRM. SMMPs can contribute to a unified, 360-degree customer view.

Impact and Result

  • The value proposition of SMMPs revolves around enhancing the effectiveness and efficiency of social media. Using an SMMP to manage social media is considerably more cost effective than ad hoc (manual) management.
  • IT must partner with other departments (e.g. Marketing) to successfully evaluate, select, and implement an SMMP. Before selecting an SMMP, the organization must have a solid overall strategy for leveraging social media in place. If IT does not work as a trusted advisor to the business, shadow IT in social media management will be rampant.

Select and Implement a Social Media Management Platform Research & Tools

Start here – read the Executive Brief

Read our concise Executive Brief to find out why you should implement an SMMP, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

Besides the small introduction, subscribers and consulting clients within this management domain have access to:

1. Develop a technology enablement approach

Conduct a maturity assessment to determine whether a dedicated SMMP is right for your organization.

  • Select and Implement a Social Media Management Platform – Phase 1: Develop a Technology Enablement Approach for Social Media
  • Social Media Maturity Assessment Tool
  • Social Media Opportunity Assessment Tool
  • SMMP Use-Case Fit Assessment Tool

2. Select an SMMP

Use the Vendor Landscape findings and project guidance to develop requirements for your SMMP RFP, and evaluate and shortlist vendors based on your expressed requirements.

  • Select and Implement a Social Media Management Platform – Phase 2: Select an SMMP
  • SMMP Vendor Shortlist & Detailed Feature Analysis Tool
  • SMMP Vendor Demo Script
  • SMMP RFP Template
  • SMMP RFP Evaluation and Scoring Tool
  • Vendor Response Template

3. Review implementation considerations

Even a solution that is a perfect fit for an organization will fail to generate value if it is not properly implemented or measured. Conduct the necessary planning before implementing your SMMP.

  • Select and Implement a Social Media Management Platform – Phase 3: Review Implementation Considerations
  • Social Media Steering Committee Charter Template
[infographic]

Workshop: Select and Implement a Social Media Management Platform

Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

1 Launch Your SMMP Selection Project

The Purpose

Discuss the general project overview for the SMMP selection.

Key Benefits Achieved

Determine your organization’s readiness for SMMP.

Activities

1.1 Identify organizational fit for the technology.

1.2 Evaluate social media opportunities within your organization.

1.3 Determine the best use-case scenario for your organization.

Outputs

Organizational maturity assessment

SMMP use-case fit assessment

2 Plan Your Procurement and Implementation Process

The Purpose

Plan the procurement and implementation of the SMMP.

Key Benefits Achieved

Select an SMMP.

Review implementation considerations.

Activities

2.1 Review use-case scenario results, identify use-case alignment

2.2 Review the SMMP Vendor Landscape vendor profiles and performance.

2.3 Create a custom vendor shortlist and investigate additional vendors for exploration in the marketplace.

2.4 Meet with the project manager to discuss results and action items.

Outputs

Vendor shortlist

SMMP RFP

Vendor evaluations

Selection of an SMMP

Framework for SMMP deployment and integration

Further reading

Select and Implement a Social Media Management Platform

Rein in social media by choosing a management platform that’s right for you.

ANALYST PERSPECTIVE

Enterprise use of social media for customer interaction has exploded. Select the right management platform to maximize the value of your social initiatives.

Social media has rapidly become a ubiquitous channel for customer interaction. Organizations are using social media for use cases from targeted advertising, to sales prospecting, to proactive customer service. However, the growing footprint of social media initiatives – and the constant proliferation of new social networks – has created significant complexity in effectively capturing the value of social.

Organizations that are serious about social manage this complexity by leveraging dedicated social media management platforms. These platforms provide comprehensive capabilities for managing multiple social media networks, creating engagement and response workflows, and providing robust social analytics. Selecting a best-fit SMMP allows for standardized, enterprise-wide capabilities for managing all aspects of social media.

This report will help you define your requirements for social media management and select a vendor that is best fit for your needs, as well as review critical implementation considerations such as CRM integration and security.

Ben Dickie
Research Director, Enterprise Applications
Info-Tech Research Group

Executive summary

Situation

  • Social media has reached maturity as a proven, effective channel for customer interaction across multiple use cases, from customer analytics to proactive customer service.
  • Organizations are looking to IT to provide leadership with social media technology enablement and integration with other enterprise systems.

Complication

  • The proliferation of social media networks, customer data, and use cases has made ad hoc social media management challenging.
  • Many organizations struggle with shadow IT when it comes to technology enablement for social media; SMMP fragmentation leads to increased costs and no uniformity in enterprise social media management capabilities.

Resolution

  • Social media management platforms (SMMPs) reduce complexity and increase the results of enterprise social media initiatives. SMMPs integrate with a variety of different social media services, including Facebook, Twitter, LinkedIn, and YouTube. The platforms offer a variety of tools for managing social media, including account management, in-band response and engagement, and social monitoring and analytics.
  • The value proposition of SMMPs revolves around enhancing the effectiveness and efficiency of social media. Using an SMMP to manage social media is considerably more cost effective than ad hoc (manual) management.
  • IT must partner with other departments (e.g. Marketing) to successfully evaluate, select, and implement an SMMP. Before selecting an SMMP, the organization must have a solid overall strategy for leveraging social media in place. If IT does not work as a trusted advisor to the business, shadow IT in social media management will be rampant.

Info-Tech Insight

  1. SMMP selection must be driven by your overall customer experience management strategy: link your SMMP selection to your organization’s CXM framework.
  2. Shadow IT will dominate if IT does not step in: even more so than other areas, SMMP selection is rife with shadow IT.
  3. Ensure strong points of integration between SMMP and other software such as customer relationship management (CRM). SMMPs can contribute to a unified, 360-degree customer view.

Framing the SMMP selection and implementation project

This Research Is Designed For:
  • IT directors advising the business on how to improve the effectiveness and efficiency of social media campaigns through technology.
  • IT professionals involved in evaluating, selecting, and deploying an SMMP.
  • Business analysts tasked with collection and analysis of SMMP business requirements.
This Research Will Help You:
  • Clearly link your business requirements to SMMP selection criteria.
  • Select an SMMP vendor that meets your organization’s needs across marketing, sales, and customer service use cases.
  • Adopt standard operating procedures for SMMP deployment that address issues such as platform security and CRM integration.
This Research Will Also Assist:
  • Executive-level stakeholders in the following roles:
    • Vice-president of Sales, Marketing, or Customer Service.
    • Business unit managers tasked with ensuring strong end-user adoption of an SMMP.
This Research Will Help Them
  • Understand what’s new in the SMMP market.
  • Evaluate SMMP vendors and products for your enterprise needs.
  • Determine which products are most appropriate for particular use cases and scenarios.

Social media management platforms augment social capabilities within a broader customer experience ecosystem

Customer Experience Management (CXM)

'Customer Relationship Management Platform' surrounded by supporting capabilities, one of which is highlighted, 'Social Media Management Platform'.

Social Media Management Platforms are one piece of the overall customer experience management ecosystem, alongside tools such as CRM platforms and adjacent point solutions for sales, marketing, and customer service. Review Info-Tech’s CXM blueprint to build a complete, end-to-end customer interaction solution portfolio that encompasses SMMP alongside other critical components. The CXM blueprint also allows you to develop strategic requirements for SMMP based on customer personas and external market analysis.

SMMPs reduce complexity and increase the effectiveness of enterprise social media programs

  • SMMPs are solutions (typically cloud based) that offer a host of features for effectively monitoring the social cloud and managing your organization’s presence in the social cloud. SMMPs give businesses the tools they need to run social campaigns in a timely and cost-effective manner.
  • The typical SMMP integrates with two or more social media services (e.g. Facebook, Twitter) via the services’ API or a dedicated connector. SMMPs are not simply a revised “interface layer” for a single social media service. They provide layers for advanced management and analytics across multiple services.
  • The unique value of SMMPs comes from their ability to manage and track multiple social media services. Aggregating and managing data from multiple services gives businesses a much more holistic view of their organization’s social initiatives and reputation in the social cloud.
Diagram with 'End Users (e.g. marketing managers)' at the top and social platforms like Facebook and Twitter at the bottom; in between them are 'SMMPs’: 'Account & Campaign Management', 'Social Engagement', and 'Social Monitoring/Analytics'.
SMMPs mediate interactions between end users and the social cloud.

Info-Tech Best Practice

The increasing complexity of social media, coupled with the rising importance of social channels, has led to a market for formal management platforms. Organizations with an active presence in social media (i.e. multiple services or pages) should strongly consider selecting and deploying an SMMP.

Failing to rein in social media initiatives leads to more work, uninformed decisions, and diminishing returns

  • The growth of social media services has made manually updating pages and feeds an ineffective and time-consuming process. The challenge is magnified when multiple brands, product lines, or geographic subsidiaries are involved.
    • Use the advanced account management features of an SMMP to reduce the amount of time spent updating social media services.
  • Engaging customers through social channels can be a delicate task – high volumes of social content can easily overwhelm marketing and service representatives, leading to missed selling opportunities and unacceptable service windows.
    • Use the in-band engagement capabilities of an SMMP to create an orderly queue for social interactions.
  • Consumer activity in the social cloud has been increasing exponentially. As the volume of content grows, separating the signal from the noise becomes increasingly difficult.
    • Use the advanced social analytics of an SMMP to ensure critical consumer insights are not overlooked.
Ad Hoc Management vs. SMMPs:
What’s the difference?

Ad Hoc Social Media Management

Social media initiatives are managed directly through the services themselves. For example, a marketing professional would log in to multiple corporate Twitter accounts to post the same content for a promotional campaign.

Social Media Management Platform

Social media initiatives are managed through a third-party software platform. For example, a marketing professional would update all social account simultaneously with just a couple clicks. SMMPs also provide cross-service social analytics – highly valuable for decision makers!

Info-Tech Best Practice

Effectively managing a social media campaign is not a straightforward exercise. If you have (or plan to have) a large social media footprint, now is the time to procure formal software tools for social media management. Continuing to manage social media in an ad hoc manner is sapping time and money.

Review the critical success factors for SMMP across the project lifecycle, from planning to post-implementation

Info-Tech Insight

Executive management support is crucial. The number one overall critical success factor for an SMMP strategy is top management support. This emphasizes the importance of sales, service, and marketing and prudent corporate strategic alignment. A strategic objective in SMMP projects is to position top management as an enabler rather than a barrier.

Planning Implementation Post-Implementation Overall
1 Appropriate Selection Project Management Top Management Support Top Management Support
2 Clear Project Goals Top Management Support Project Management Appropriate Selection
3 Top Management Support Training Training Project Management
4 Business Mission and Vision Effective Communication Effective Communication Training
5 Project Management Supplier Supports Appropriate Selection Clear Project Goals

(Source: Information Systems Frontiers)

Dell uses a dedicated social media management platform to power a comprehensive social command center

CASE STUDY

Industry: High-Tech | Source: Dell
With a truly global customer base, Dell gets about 22,000 mentions on the social web daily, and does not sit idly by. Having established a physical Social Media Command Center powered by Salesforce’s Social Studio, Dell was one of the companies that pioneered the command center concept for social response.

The SMMP carries out the following activities:

  • Tracking mentions of Dell in the social cloud
  • Sentiment analysis
  • Connecting customers who need assistance with experts who can help them
  • Social media training
  • Maintenance of standards for social media interactions
  • Spreading best social media practices across the organization

Today the company claims impressive results, including:

  • “Resolution rate” of 99% customer satisfaction
  • Boosting its customer reach with the same number of employees
  • One third of Dell’s former critics are now fans

Logo for Dell.

Tools:
  • Salesforce Social Studio
  • Three rows of monitors offering instant insights into customer sentiment, share of voice, and geography.
Staff:
  • The center started with five people; today it is staffed by a team of 15 interacting with customers in 11 languages.
  • Dell values human interaction; the center is not running on autopilot, and any ambiguous activity is analyzed (and dealt with) manually on an individual basis.

Follow Info-Tech’s methodology for selection and implementation of enterprise applications

Prior to embarking on the vendor selection stage, ensure you have set the right building blocks and completed the necessary prerequisites.

Diagram with 'Enterprise Applications' at the center surrounded by a cycle of 'conceptual', 'consensus', 'concrete', and 'continuous'. The outer circle has three categories with three actions each, 'Governance and Optimization: Process Optimization, Support/ Maintenance, Transition to Operations', 'Strategy and Alignment: Foundation, Assessment, Strategy/ Business Case', and 'Implementation: System Implementation, Business Process Management, Select and Implement'. Follow Info-Tech’s enterprise applications program that covers the application lifecycle from the strategy stage, through selection and implementation, and up to governance and optimization.

The implementation and execution stage entails the following steps:

  1. Define the business case.
  2. Gather and analyze requirements.
  3. Build the RFP.
  4. Conduct detailed vendor evaluations.
  5. Finalize vendor selection.
  6. Review implementation considerations.

Info-Tech Insight

A critical preceding task to selecting a social media management platform is ensuring a strategy is in place for enterprise social media usage. Use our social media strategy blueprint to ensure the foundational elements are in place prior to proceeding with platform selection.

Use this blueprint to support your SMMP selection and implementation

Launch the SMMP Project and Collect Requirements — Phase 1

Benefits — Use the project steps and activity instructions outlined in this blueprint to streamline your selection process and implementation planning. Save time and money, and improve the impact of your SMMP selection by leveraging Info-Tech’s research and project steps.

Select Your SMMP Solution — Phase 2

Use Info-Tech’s SMMP Vendor Landscape contained in Phase 2 of this project to support your vendor reviews and selection. Refer to the use-case performance results to identify vendors that align with the requirements and solution needs identified by your earlier project findings.

Get Ready for Your SMMP Implementation — Phase 3

Info-Tech Insight — Not everyone’s connection and integration needs are the same. Understand your own business’s integration environment and the unique technical and functional requirements that accompany them to create criteria and select a best-fit SMMP solution.

Use Info-Tech’s use-case scenario approach to select a best-fit solution for your business needs

Readiness

Determine where you are right now and where your organization needs to go with a social media strategy.

Three stages eventually leading to shapes in a house, 'Distributed Stage', 'Loosely Coupled Stage', and 'Command Center Stage'.
Use-Case Assessment

Identify the best-fit use-case scenario to determine requirements that best align with your strategy.

Three blocks labelled 'Social Listening & Analytics', 'Social Customer Care', and 'Social Publishing & Campaign Management'.
Selection

Approach vendor selection through a use-case centric lens to balance the need for different social capabilities.

Logos for vendors including Adobe, Hootsuite, CISION, and more.

Info-Tech walks you through the following steps to help you to successfully select and implement your SMMP

Steps of this blueprint represented by circles of varying colors and sizes, labelled by text of different sizes.

Locate your starting point in the research based on the current stage of your project.

Legend for the diagram above: lines represent Major Milestones, size of circles represent Low or High effort, size of text represents Average or Greater importance, and color of the circles represents the phase.

Info-Tech offers various levels of support to best suit your needs

DIY Toolkit

Guided Implementation

Workshop

Consulting

"Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful." "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track." "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place." "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

Diagnostics and consistent frameworks used throughout all four options

Select and Implement a Social Media Management Platform – project overview

1. Develop a Technology Enablement Approach 2. Select an SMMP 3. Review Implementation Considerations
Supporting Tool icon

Best-Practice Toolkit

1.1 Determine if a dedicated SMMP is right for your organization

  • Social Media Maturity Assessment Tool
  • Social Media Opportunity Assessment Tool

1.2 Use an SMMP to enable marketing, sales, and service use cases

  • SMMP Use-Case Fit Assessment Tool

2.1 SMMP Vendor Landscape

  • CRM Suite Evaluation and RFP Scoring Tool

2.2 Select your SMMP

  • SMMP Vendor Demo Script Template
  • SMMP RFP Template

3.1 Establish best practices for SMMP implementation

  • Social Media Steering Committee

3.2 Assess the measured value from the project

Guided Implementations

  • Identify organizational fit for the technology.
  • Evaluate social media opportunities within your organization.
  • Evaluate which SMMP use-case scenario is best fit for your organization
  • Discuss the use-case fit assessment results and the Vendor Landscape.
  • Review contract.
  • Determine what is the right governance structure to overlook the SMMP implementation.
  • Identify the right deployment model for your organization.
  • Identify key performance indicators for business units using an SMMP.
Associated Activity icon

Onsite Workshop

Module 1:
Launch Your SMMP Selection Project
Module 2:
Plan Your Procurement and Implementation Process
Phase 1 Outcome:
  • Social Media Maturity Assessment
  • SMMP Use-Case Assessment
Phase 2 Outcome:
  • Selection of an SMMP
Phase 3 Outcome:
  • A plan for implementing the selected SMMP

SMMP selection and implementation workshop overview

Associated Activity icon Contact your account representative or email Workshops@InfoTech.com for more information.

Day 1

Preparation

Day 2

Workshop Day

Day 3

Workshop Day

Day 4

Workshop Day

Day 5

Working Session

Workshop Preparation
  • Facilitator meets with the project manager and reviews the current project plans and IT landscape of the organization.
  • A review of scheduled meetings and engaged IT and business staff is performed.
Morning Itinerary
  • Conduct activities from Develop a technology enablement approach for social media phase, including social media maturity and readiness assessment.
  • Conduct overview of the market landscape, trends, and vendors.
Afternoon Itinerary
  • Interview business stakeholders.
  • Prioritize SMMP requirements.
Morning Itinerary
  • Perform a use-case scenario assessment.
Afternoon Itinerary
  • Review use-case scenario results; identify use-case alignment.
  • Review the SMMP Vendor Landscape vendor profiles and performance.
Morning Itinerary
  • Continue review of SMMP Vendor Landscape results and use-case performance results.
Afternoon Itinerary
  • Create a custom vendor shortlist.
  • Investigate additional vendors for exploration in the market.
Workshop Debrief
  • Meet with project manager to discuss results and action items.
  • Wrap up outstanding items from workshop.
(Post-Engagement): Procurement Support
  • The facilitator will support the project team to outline the RFP contents and evaluation framework.
  • Planning of vendor demo script. Input: solution requirements and use-case results.
Example of a light blue slide. The light blue slides at the end of each section highlight the key activities and exercises that will be completed during the engagement with our analyst team.

Use these icons to help direct you as you navigate this research

Use these icons to help guide you through each step of the blueprint and direct you to content related to the recommended activities.

A small monochrome icon of a wrench and screwdriver creating an X.

This icon denotes a slide where a supporting Info-Tech tool or template will help you perform the activity or step associated with the slide. Refer to the supporting tool or template to get the best results and proceed to the next step of the project.

A small monochrome icon depicting a person in front of a blank slide.

This icon denotes a slide with an associated activity. The activity can be performed either as part of your project or with the support of Info-Tech team members who will come onsite to facilitate a workshop for your organization.

A small monochrome icon depicting a descending bar graph.

This icon denotes a slide that pertains directly to the Info-Tech vendor profiles on marketing management technology. Use these slides to support and guide your evaluation of the MMS vendors included in the research.

Select and Implement a Social Media Management Platform

PHASE 1

Develop a Technology Enablement Approach for Social Media

Phase 1: Develop a technology enablement approach for social media

Steps of this blueprint represented by circles of varying colors and sizes, labelled by text of different sizes. Only Phase 1 is highlighted.
Estimated Timeline: 1-3 Months

Info-Tech Insight

Before an SMMP can be selected, the organization must have a strategy in place for enterprise social media. Implementing an SMMP before developing a social media strategy would be akin to buying a mattress without knowing the size of the bed frame.

Major Milestones Reached
  • Project launch
  • Completion of requirements gathering and documentation

Key Activities Completed

  • Readiness assessment
  • Project plan / timeline
  • Stakeholder buy-in
  • Technical assessment
  • Functional assessment

Outcomes from This Phase

Social Media Maturity Assessment

Phase 1 outline

Associated Activity icon Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

Guided Implementation 1: Develop a technology enablement approach for social media

Proposed Time to Completion: 2 weeks
Step 1.1: Determine if a dedicated SMMP is right for your organization Step 1.2: Use an SMMP to enable marketing, sales, and service use cases
Start with an analyst kick-off call:
  • Assess your readiness for the SMMP project.
  • Evaluate social media opportunities within your organization.
Review findings with analyst:
  • Discuss how an SMMP can assist with marketing, sales, and customer service.
  • Evaluate which SMMP use case scenario is best fit for your organization.
Then complete these activities…
  • Assess your social media maturity.
  • Inventory social media networks to be supported by the SMMP.
Then complete these activities…
  • Assess best-fit use-case scenario.
  • Build the metrics inventory.
With these tools & templates:
  • Social Media Maturity Assessment Tool
  • Social Media Opportunity Assessment Tool
With these tools & templates:
  • SMMP Use-Case Fit Assessment Tool
Phase 1 Results & Insights:
  • Social Media Maturity Assessment
  • SMMP Use-Case Assessment

Phase 1, Step 1: Determine if a dedicated SMMP is right for your organization

1.1

1.2

Determine if a dedicated SMMP is right for your organization Use an SMMP to enable marketing, sales, and service use cases

This step will walk you through the following activities:

  • Assess where your organization sits on the social media maturity curve.
  • Inventory the current social media networks that must be supported by the SMMP.
  • Go/no-go assessment on SMMP.

This step involves the following participants:

  • Digital Marketing Executive
  • Digital Strategy Executive
  • Business stakeholders

Outcomes of this step

  • Social media maturity assessment
  • Inventory of enterprise social media
  • SMMP Go/no-go decision

Before selecting an SMMP, start with the fundamentals: build a comprehensive strategy for enterprise social media

Why build a social media strategy?

  • Social media is neither a fad nor a phenomenon; it is simply another tool in the business process. Social channels do not necessitate a radical departure from the organization’s existing customer interaction strategy. Rather, social media should be added to your channel mix and integrated within the existing CRM strategy.
  • Social media allows organizations to form direct and indirect connections through the Friend-of-a-Friend (FOAF) model, which increases the credibility of the information in the eyes of the consumer.
  • Social media enables organizations to share, connect, and engage consumers in an environment where they are comfortable. Having a social media presence is rapidly becoming a pre-requisite for successful business-to-consumer enterprises.

Important considerations for an enterprise social media strategy:

  • Determine how social media will complement existing customer interaction goals.
  • Assess which social media opportunities exist for your organization.
  • Consider the specific goals you want to achieve using social channels and pick your services accordingly.
  • Not all social media services (e.g. Facebook, Twitter, LinkedIn) are equal. Consider which services will be most effective for goal achievement.
For more information on developing a strategy for enterprise social media, please refer to Info-Tech’s research on Social Media.

Implement a social media strategy by determining where you are right now and where your organization needs to go

Organizations pass through three main stages of social media maturity: distributed, loosely coupled, and command center. As you move along the maturity scale, the business significance of the social media program increases. Refer to Info-Tech’s Implement a Social Media Program for guidance on how to execute an ongoing social media program.
The y-axis 'Business Significance'.

Distributed Stage

Shapes labelled 'Sales', 'Customer Service', and 'Marketing'.

  • Open-source or low-cost solutions are implemented informally by individual depts. for specific projects.
  • Solutions are deployed to fulfill a particular function without an organizational vision. The danger of this stage is lack of consistent customer experience and wasted resources.

Loosely Coupled Stage

Same shapes with the addition of 'PR' and surrounded by a dotted-line house.

  • More point solutions are implemented across the organization. There is a formal cross-departmental effort to integrate some point solutions.
  • Risks include failing to put together an effective steering committee and not including IT in the decision-making process.

Command Center Stage

Same shapes with a solid line house.

  • There’s enterprise-level steering committee with representation from all areas: execution of social programs is handled by a fully resourced physical (or virtual) center.
  • Risks include improper resource allocation and lack of end-user training.
The x-axis 'Maturity Stages'.
Optimal stages for SMMP purchase

Assess where your organization sits on the social media maturity curve

Associated Activity icon 1.1.1 30 Minutes

INPUT: Social media initiatives, Current status

OUTPUT: Current State Maturity Assessment

MATERIALS: Whiteboard, Markers, Sticky notes

PARTICIPANTS: Digital Strategy Executive, Business stakeholders

Before you can move to an objective assessment of your social media program’s maturity, take an inventory of your current efforts across different departments (e.g. Marketing, PR, Sales, and Customer Service). Document the results in the Social Media Maturity Assessment Tool to determine your social media readiness score.

Department Social Media Initiative(s) Current Status
Marketing Branded Facebook page with updates and promotions Stalled: insufficient resources
Sales LinkedIn prospecting campaign for lead generation, qualification, and warm open Active: however, new reps are poorly trained on LinkedIn prospect best practices
Customer Service Twitter support initiative: mentions of our brand are paired with sentiment analysis to determine who is having problems and to reach out and offer support Active: program has been highly successful to date
HR Recruitment campaign through LinkedIn and Branch Out Stalled: insufficient technology support for identifying leading candidates
Product Development Defect tracking for future product iterations using social media Partially active: Tracked, but no feedback loop present
Social Media Maturity Level Distributed

Determine your organization’s social media maturity with Info-Tech’s Maturity Assessment Tool

Supporting Tool icon 1.1 Social Media Maturity Assessment Tool

Assessing where you fit on the social media maturity continuum is critical for setting the future direction of your social media program. We’ll work through a short tool that assesses the current state of your social media program, then discuss the results.

Info-Tech’s Social Media Maturity Assessment Tool will help you determine your company’s level of maturity and recommend steps to move to the next level or optimize the status quo of your current efforts.

INFO-TECH TOOL Sample of the Social Media Current State Assessment.

The social cloud is a dominant point of interaction: integrate social channels with existing customer interaction channels

  • Instead of thinking of customers as an island, think of them interacting with each other and with organizations in the social cloud. As a result, the social cloud itself becomes a point of interaction, not just individual customers.
  • The social cloud is accessible with services like social networks (e.g. Facebook) and micro-blogs (Twitter).
  • Previous lessons learned from the integration of Web 1.0 e-channels should be leveraged as organizations add the social media channel into their overall customer interaction framework:
    • Do not design exclusively around a single channel. Design hybrid-channel solutions that include social channels.
    • Balance customer segment goals and attributes, product and service goals and attributes, and channel capabilities.
The 'Web 2.0 Customer Interaction Framework' with 'Social Cloud' above, connected to the below through 'Conversations & Information'. Below are two categories with their components interconnected, 'Communication Channels: Face to Face, Phone, E-mail, Web, and Social Media' and 'Customer Experience Management: Marketing, Sales, and Service'.

Info-Tech Best Practice

Don’t believe that social channel integration will require an entire rebuild of your CXM strategy. Social channels are just new interaction channels that need to be integrated – as you’ve done in the past with Web 1.0 e-channels.

Understand the different types of social media services and how they link to social media strategy and SMMP selection

Before adopting an SMMP, it’s important to understand the underlying services they manage. Social media services facilitate the creation and dissemination of user-generated content, and can be grouped according to their purpose and functionality:
  • Social Networking: Social networking services use the Friend-of-a-Friend model to allow users to communicate with their personal networks. Users can share a wide variety of information and media with one another. Social networking sites include Facebook and LinkedIn.
  • Blogging: Blogs are websites that allow users to upload text and media entries, typically displayed in reverse-chronological order. Prominent blogging services include Blogger and WordPress.
  • Micro-Blogging: Micro-blogging is similar to blogging, with the exception that written content is limited to a set number of characters. Twitter, the most popular service, allows users to post messages up to 140 characters.
  • Social Multimedia: Social multimedia sites provide an easy way for users to upload and share multimedia content (e.g. pictures, video) with both their personal contacts as well as the wider community. YouTube is extremely popular for video sharing, while Instagram is a popular option for sharing photos and short videos.

Info-Tech Best Practice

In many cases, services do not fit discretely within each category. With minor exceptions, creating an account on a social media service is free, making use of these services extremely cost effective. If your organization makes extensive use of a particular service, ensure it is supported by your SMMP vendor.

Four categories of social media company logos: 'Social multimedia', 'Micro-blogging', 'Blogging', and 'Social Networking'.

Inventory the current social media networks that must be supported by the SMMP

Associated Activity icon 1.1.2

INPUT: Social media services

OUTPUT: Inventory of enterprise social media

MATERIALS: Whiteboard, Markers

PARTICIPANTS: Project team

  1. List all existing social media networks used by your organization.
  2. For each network, enumerate all the accounts that are being used for organizational objectives.
  3. Identify the line of business that administers and manages each service.
Network Use Case Account Ownership
Facebook
  • Branding
  • Marketing
  • Social Monitoring
  • Facebook recruitment
  • Corporate Communications
  • Marketing
Twitter
  • Social monitoring
  • Customer response
  • Corporate
  • Customer Service
... ... ...

An explosion of social media services and functionality has made effectively managing social interactions a complex task

  • Effectively managing social channels is an increasingly complicated task. Proliferation of social media services and rapid end-user uptake has made launching social interactions a challenge for small and large organizations.
  • Using multiple social media services can be a nightmare for account management (particularly when each brand or product line has its own set of social accounts).
  • The volume of data generated by the social cloud has also created barriers for successfully responding in-band to social stakeholders (social engagement), and for carrying out social analytics.
  • There are two methods for managing social media: ad hoc management and platform-based management.
    • Ad hoc social media management is accomplished using the built-in functionality and administrative controls of each social media service. It is appropriate for small organizations with a very limited scope for social media interaction, but poses difficulties once “critical mass” has been reached.
Comparison of 'Ad Hoc Management' with each social media platform managed directly by the user and 'Platform-Based Management' with social platforms managed by a 'SMMP' which is managed by the user.
Ad hoc management results in a number of social media touch points. SMMPs serve as a single go-to point for all social media initiatives

Info-Tech Best Practice

Managing social media is becoming increasingly difficult to do through ad hoc methods, particularly for larger organizations and those with multiple brand portfolios. Ad hoc management is best suited for small organizations with an institutional client base who only need a bare bones social media presence.

Select social media services that will achieve your specific objectives – and look for SMMPs that integrate with them

What areas are different social media services helpful in?
Domain Opportunity Consumer Social Networks (Facebook) Micro-Blogging (Twitter) Professional Social Networks (LinkedIn) Consumer Video Sharing Networks (YouTube)
Marketing Building Positive Brand Image Green circle 'Proven Useful'. Green circle 'Proven Useful'. Dark Blue circle 'Potentially Useful'.
Increase Mind Share Green circle 'Proven Useful'. Green circle 'Proven Useful'. Dark Blue circle 'Potentially Useful'.
Gaining Customer Insights Green circle 'Proven Useful'. Green circle 'Proven Useful'. Green circle 'Proven Useful'. Dark Blue circle 'Potentially Useful'.
Sales Gaining Sales Insights Dark Blue circle 'Potentially Useful'. Green circle 'Proven Useful'. Dark Blue circle 'Potentially Useful'.
Increase Revenue Dark Blue circle 'Potentially Useful'. Green circle 'Proven Useful'. Dark Blue circle 'Potentially Useful'.
Customer Acquisition Green circle 'Proven Useful'. Green circle 'Proven Useful'. Green circle 'Proven Useful'.
Service Customer Satisfaction Green circle 'Proven Useful'. Green circle 'Proven Useful'. Green circle 'Proven Useful'. Green circle 'Proven Useful'.
Increase Customer Retention Green circle 'Proven Useful'. Green circle 'Proven Useful'. Dark Blue circle 'Potentially Useful'.
Reducing Cost of Service Dark Blue circle 'Potentially Useful'. Dark Blue circle 'Potentially Useful'. Dark Blue circle 'Potentially Useful'. Green circle 'Proven Useful'.

Green circle 'Proven Useful'. Proven Useful*

Dark Blue circle 'Potentially Useful'. Potentially Useful

*Proven useful by Info-Tech statistical analysis carried out on a cross-section of real-world implementations.

Social media is invaluable for marketing, sales, and customer service. Some social media services have a higher degree of efficacy than others for certain functions. Be sure to take this into account when developing a social media strategy.

Info-Tech Best Practice

Different social media services are more effective than others for different goals. For example, YouTube is useful as an avenue for marketing campaigns, but it’s of substantially less use for sales functions like lead generation. The services you select while planning your social media strategy must reflect concrete goals.

Ad hoc social media management results in manual, resource-intensive processes that are challenging to measure

  • Most organizations that have pursued social media initiatives have done so in an ad hoc fashion rather than outlining a formal strategy and deploying software solutions (e.g. SMMP).
  • Social media is often a component of Customer Experience Management (CXM); Info-Tech’s research shows many organizations are handling CRM without a strategy in place, too.
  • Social media management platforms reduce the resource-intensive processes required for ongoing social media involvement and keep projects on track by providing reporting metrics.
Social media and CRM are often being done without a defined strategy in place.

Four-square matrix titled 'Strategy' presenting percentages with y-axis 'CRM', x-axis 'Social Media', both having two sections 'Ad hoc' and 'Defined'.
Source: Info-Tech Survey, N=64

Many processes related to social media are being done manually, despite the existence of SMMPs.

Four-square matrix titled 'technology' presenting percentages with y-axis 'CRM', x-axis 'Social Media', both having two sections 'Ad hoc' and 'Defined'.

“When we started our social media campaign, it took 34 man-hours a week. An SMMP that streamlines these efforts is absolutely an asset.” (Edie May, Johnson & Johnson Insurance Company)

SMMPs provide functionality for robust account management, in-band customer response, and social monitoring/analytics

  • Features such as unified account management and social engagement capabilities boost the efficiency of social campaigns. These features reduce duplication of effort (e.g. manually posting the same content to multiple services). Leverage account management functionality and in-band response to “do more with less.”
  • Features such as comprehensive monitoring of the social cloud and advanced social analytics (i.e. sentiment analysis, trends and follower demographics) allow organizations to more effectively use social media. These features empower organizations with the information they need to make informed decisions around messaging and brand positioning. Use social analytics to zero in on your most important brand advocates.

The value proposition of SMMPs revolves around enhancing the effectiveness and efficiency of social media initiatives.

Three primary use cases for social media management:

Social Listening & Analytics — Monitor and analyze a variety of social media services: provide demographic analysis, frequency analysis, sentiment analysis, and content-centric analysis.

Social Publishing & Campaign Management — Executing marketing campaigns through social channels (e.g. Facebook pages).

Social Customer Care — Track customer conversations and provide the ability to respond in-platform to social interactions.

Info-Tech Best Practice

SMMPs are a technology platform, but this alone is insufficient to execute a social media program. Organization and process must be integrated as well. See Info-Tech’s research on developing a social media strategy for a step-by-step guide on how to optimize your internal organization and processes.

Social analytics vary: balance requirements among monitoring goals and social presence/property management

Segment your requirements around common SMMP vendor product design points. Current market capabilities vary between two primary feature categories: social cloud monitoring and social presence and property management.

Cloud-Centric

Social Monitoring

Content-Centric

Social cloud monitoring enables:
  • Brand and product monitoring
  • Reputation monitoring
  • Proactive identification of service opportunities
  • Competitive intelligence
Social presence and property management enables:
  • Monitor and manage discussions on your social properties (e.g. Twitter feeds, Facebook Pages, YouTube channels)
  • Execute marketing campaigns within your social properties

Social Analytics

Social analytics provide insights to both dimensions of social media monitoring.

Some firms only need social cloud monitoring, some need to monitor their own social media properties, and others will need to do both. Some vendors do both while other vendors excel in only one feature dimension. If you are NOT prepared to act on results from social cloud monitoring, then don’t expand your reach into the social cloud for no reason. You can always add cloud monitoring services later. Likewise, if you only need to monitor the cloud and have no or few of your own social properties, don’t buy advanced management and engagement features.

Use social analytics to gain the most value from your SMMP

Research indicates successful organizations employ both social cloud monitoring and management of their own properties with analytical tools to enhance both or do one or the other well. Few vendors excel at both larger feature categories. But the market is segmented into vendors that organizations should be prepared to buy more than one product from to satisfy all requirements. However, we expect feature convergence over the next 1–3 years, resulting in more comprehensive vendor offerings.

Most sought social media analytics capabilities

Bar Chart of SM analytics capabilities, the most sought after being 'Demographic analysis', 'Geographic analysis', 'Semantic analysis', 'Automated identification of subject and content', and 'Predictive modeling'.
(Source: The State of Social Media Analytics (2016))

Value driven from social analytics comes in the form of:
  • Improved customer service
  • Increased revenue
  • Uncovered insights for better targeted marketing
  • A more personalized customer experience offered
Social analytics is integral to the success of the SMMP – take advantage of this functionality!

Cost/Benefit Scenario: A mid-sized consumer products company wins big by adopting an SMMP

The following example shows how an SMMP at a mid-sized consumer products firm brought in $36 000 a year.

Before: Manual Social Media Management

  • Account management: a senior marketing manager was responsible for updating all twenty of the firm’s social media pages and feeds. This activity consumed approximately 20% of her time. Her annual salary was $80,000. Allocated cost: $16,000 per year.
  • In-band response: Customer service representatives manually tracked service requests originating from social channels. Due to the use of multiple Twitter feeds, several customers were inadvertently ignored and subsequently defected to competitors. Lost annual revenue due to customer defections: $10,000.
  • Social analytics: Analytics were conducted in a crude, ad hoc fashion using scant data available from the services themselves. No useful insights were discovered. Gains from social insights: $0.

Ad hoc management is costing this organization $26,000 a year.

After: Social Media Management Platform

  • Account management: Centralized account controls for rapidly managing several social media services meant the amount of time spent updating social media was cut 75%. Allocated cost savings: $12,000 per year.
  • In-band response: Using an SMMP provided customer service representatives with a console for quickly and effectively responding to customer service issues. Service window times were significantly reduced, resulting in increased customer retention. Revenue no longer lost due to defections: $10,000.
  • Social analytics: The product development group used keyword-based monitoring to assist with designing a successful new product. Social feedback noticeably boosted sales. Gains from social insights: $20,000
  • Cost of SMMP: $6,000 per year.

The net annual benefit of adopting an SMMP is $36,000.

Go with an SMMP if your organization needs a heavy social presence; stick with ad hoc management if it doesn’t

The value proposition of acquiring an SMMP does not resonate the same for all organizations: in some cases, it is more cost effective to forego an SMMP and stick with ad hoc social media management.

Follow these guidelines for determining if an SMMP is a natural fit for your organization.

Go with an SMMP if…

  • Your organization already has a large social footprint: you manage multiple feeds/pages on three or more social media services.
  • Your organization’s primary activity is B2C marketing; your target consumers are social media savvy. Example: consumer packaged goods.
  • The volume of marketing, sales and service inquiries received over social channels has seen a sharp increase in the last 12 months.
  • Your firm or industry is the topic of widespread discussion in the social cloud.

Stick with ad hoc management if…

  • Regulatory compliance prohibits the extensive use of social media in your organization.
  • Your organization is focused on a small number of institutional clients with well-defined organizational buying behaviors.
  • Your target market is antipathetic towards using social channels to interact with your organization.
  • Your organization is in a market space where only a bare-bones social media presence is seen as a necessity (for example, only a basic informational Facebook page is maintained).

Info-Tech Best Practice

Using an SMMP is definitively superior to ad hoc social media management for those organizations with multiple brands and product portfolios (e.g. consumer packaged goods). Ad hoc management is best for small organizations with an institutional client base who only need a bare bones social media presence.

Assess which social media opportunities exist for your organization with Info-Tech’s tool

Supporting Tool icon 1.2 Social Media Opportunity Assessment Tool

Use Info-Tech’s Social Media Opportunity Assessment Tool to determine, based on your unique criteria, where social media opportunities exist for your organization in marketing, sales, and service.

Info-Tech Best Practice

  1. Remember that departmental goals will overlap; gaining customer insight is valuable to marketing, sales, and customer service.
  2. The social media benefits you can expect to achieve will evolve as your processes mature.
  3. Often, organizations jump into social media because they feel they have to. Use this assessment to identify early on what your drivers should be.
Sample of the Social Media Opportunity Assessment Tool.

Go/no-go assessment on SMMP

Associated Activity icon 1.1.3

INPUT: Social Media Opportunity Questionnaire

OUTPUT: SMMP go/no-go decision

MATERIALS: Whiteboard, Opportunity Assessment Tool

PARTICIPANTS: Digital Strategy Executive, Business stakeholders

Identify whether an SMMP will help you achieve your goals in sales, marketing, and customer service.

  1. Complete the questionnaire in the Social Media Opportunity Assessment Tool. Ensure all relevant stakeholders are present to answer questions pertaining to their business area.
  2. Evaluate the results to better understand whether your organization has the opportunity to achieve each established goal in marketing, sales, and customer service with an SMMP or you are not likely to benefit from investing in a social media management solution.

Phase 1, Step 2: Use an SMMP to enable marketing, sales, and service use cases

1.1

1.2

Determine if a dedicated SMMP is right for your organization Use an SMMP to enable marketing, sales, and service use cases

This step will walk you through the following activities:

  • Profile and rank your top use cases for social media management
  • Build the metrics inventory

This step involves the following participants:

  • Project Manager
  • Project Team

Outcomes of this step

  • Use case suitability
  • SMMP metrics inventory

SMMPs equip front-line sales staff with the tools they need for effective social lead generation

  • Content-centric social analytics allow sales staff to see click-through details for content posted on social networks. In many cases, these leads are warm and ready for immediate follow-up.
  • A software development firm uses an SMMP to post a whitepaper promoting its product to multiple social networks.
    • The whitepaper is subsequently downloaded by a number of potential prospects.
    • Content-centric analytics within the SMMP link the otherwise-anonymous downloads to named social media accounts.
    • Leads assigned to specific account managers, who use existing CRM software to pinpoint contact information and follow-up in a timely manner.
  • Organizations that intend to use their SMMP for sales purposes should ensure their vendor of choice offers integration with LinkedIn. LinkedIn is the business formal of social networks, and is the network with the greatest proven efficacy from a sales perspective.

Using an SMMP to assist the sales process can…

  • Increase the number of leads generated through social channels as a result of social sharing.
  • Increase the quality of leads generated through social channels by examining influence scores.
  • Increase prospecting efficiency by finding social leads faster.
  • Keep account managers in touch with prospects and clients through social media.

Info-Tech Best Practice

Social media is on the rise in sales organizations. Savvy companies are using social channels at all points in the sales process, from prospecting to account management. Organizations using social channels for sales will want an SMMP to manage the volume of information and provide content-centric analytics.

Incorporate social media into marketing workflows to gain customer insights, promote your brand, and address concerns

While most marketing departments have used social media to some extent, few are using it to its full potential. Identify marketing workflows that can be enhanced through the use of social channel integration.
  • Large organizations must define separate workflows for each stakeholder organization if marketing’s duties are divided by company division, brand, or product lines.
  • Inquiries stemming from marketing campaigns and advertising must be handled by social media teams. For example, if a recent campaign sparks customer questions on the company’s Facebook page, be ready to respond!
  • Social media can be used to detect issues that may indicate product defects, provided defect tracking is not already incorporated into customer service workflows. If defect tracking is part of customer service processes, then such issues should be routed to the customer service organization.
  • If social listening is employed, in addition to monitoring the company's own social properties, marketing teams may elect to receive notices of major trends concerning the company's products or those of competitors.
Word jumble of different sized buzz words around 'Brand Building'.

I’m typically using my social media team as a proactive marketing team in the social space, whereas I’m using my consumer relations team as a reactive marketing and a reactive consumer relations taskforce. So a little bit different perspective.” (Greg Brickl, IT Director, Organic Valley)

SMMPs allow marketers to satisfy all of their needs with one solution

  • Have a marketing manager jointly responsible for the selection of an SMMP to realize higher overall success. This will significantly improve customer acquisition approval and competitive intelligence, as well as the overall SMMP success.
  • The marketing manager should be involved in fleshing out the business requirements of the SMMP in order to select the most appropriate solution.
  • Once selected, the SMMP has multiple benefits for marketing professionals. One pivotal benefit of SMMPs for marketing is the capability for centralized account management. Multiple social pages and feeds can be rapidly managed at pre-determined times, through an easy-to-use dashboard delivered from one source.
  • Centralized account management is especially pertinent for organizations with a wide geographic client base, as they can manage wide social media campaigns within multiple time zones, delivering their messaging appropriately. (e.g. contests, product launches, etc.)
Bar Chart comparing 'Average Success Scores' of different goals based on whether the 'Marketing Manager [was] Responsible' or not. Scores are always higher when they were.
(Source: Info-Tech Research Group N = 37)

Info-Tech Best Practice

Managing multiple social media accounts on an ad hoc basis is time consuming and costs money. Lower costs and get the best results out of your social media campaigns by involving the marketing team in the SMMP selection process and knowing their functional requirements.

Leverage SMMPs to proactively identify and respond to customer service issues occurring in the social cloud

  • SMMPs are an invaluable tool in customer service organizations. In-band response capabilities allow customer service representatives to quickly and effectively address customer service issues – either reactively or proactively.
  • Reactive customer service can be provided through SMMPs by providing response capabilities for private messages or public mentions (e.g. “@AcmeCo” on Twitter). Many SMMPs provide a queue of social media messages directed at the organization, and also give the ability to assign specific messages to an individual service representative or product expert. Responding to a high-volume of reactive social media requests can be time consuming without an SMMP.
  • Proactive customer service uses the ability of SMMPs to monitor the social cloud for specific keywords in order to identify customers having issues. Forward-thinking companies actively monitor the social cloud for customer service opportunities, to protect and improve their image.
Illustration of reactive service where the customer initiates the process and then receives service.
Reactive service is customer-initiated.

Illustration of proactive service with a complaint through Twitter monitored by an SMMP allowing an associate to provide a 'Proactive Resolution'.
SMMPs enable organizations to monitor the social cloud for service opportunities and provide proactive service in-band.

Info-Tech Best Practice

Historically, customer service has been “reactive” (i.e. customer initiated) and solely between the customer and supplier. Social media forces proactive service interactions between customer, supplier, and the entire social cloud. Using an SMMP significantly improves reactive and proactive service. The ability to integrate with customer service applications is essential.

Customer service is a vital department to realize value from leveraging an SMMP

Info-Tech’s research shows that the more departments get involved with social media implementation, the higher the success score (calculated based on respondents’ report of the positive impact of social media on business objectives). On average, each additional department involved in social media programs increases the overall social media success score by 5%. For example, organizations that leveraged social media within the customer service department, achieved a higher success score than those that did not.

The message is clear: encourage broad participation in coordinated social media efforts to realize business goals.

Line graph comparing 'Social Media Success Score' with the 'Number of Departments Involved'. The line trends upward on both axes.
(Source: Info-Tech Research Group N=65)
Bar chart comparing 'Social Media Success Scores' if 'Customer Service Involvement' was Yes or No. 'Yes' has a higher score.

Our research indicates that the most important stakeholder to ensure steering committee success is Customer Service. This has a major impact on CRM integration requirements – more on this later.

SMMPs are indispensable for allowing PR managers to keep tabs on the firm and its brands

  • Public relations is devoted to relationship management; as such, it is critical for savvy PR departments to have a social media presence.
  • SMMPs empower PR professionals with the ability to track the sentiment of what is said about their organization. Leverage keyword searches and heuristic analysis to proactively mitigate threats and capitalize on positive opportunities. For example, sentiment analysis can be used to identify detractors making false claims over social channels. These claims can then be countered by the Public Relations team.
  • Sentiment analysis can be especially important to the PR professional through change and crisis management situations. These tools allow an organization to track the flow of information, as well as the balance of positive and negative postings and their influence on others in the social cloud.
  • Social analytics provided by SMMPs also serve as a goldmine for competitive intelligence about rival firms and their products.

Benefits of Sentiment Analysis for PR

  • Take the pulse of public perception of your brands (and competitors).
  • Mitigate negative comments being made and respond immediately.
  • Identify industry and consumer thought leaders to follow on social networks.

Illustration of sentiment analysis.
Use sentiment analysis to monitor the social cloud.

Info-Tech Best Practice

Leaving negative statements unaddressed can cause harm to an organization’s reputation. Use an SMMP to track what is being said about your organization; take advantage of response capabilities to quickly respond and mitigate PR risk.

SMMPs for recruiting is an emerging talent recruitment technique and will lead to stronger candidates

  • Social media provides more direct connections between employer and applicant. It’s faster and more flexible than traditional e-channels.
  • SMMPs should be deployed to the HR silo to aid with recruiting top-quality candidates. Account management functionality can dramatically reduce the amount of time HR managers spend synchronizing content between various social media services.
  • In-band response capabilities flag relevant social conversations and allow HR managers to rapidly respond to prospective employee inquiries. Rapid response over social channels gives candidates a positive impression of the organization.
  • Analytics give HR managers insight into hiring trends and the job market at large – sentiment analysis is useful for gauging not just candidate interests, but also anonymous employee engagement.

A social media campaign managed via SMMP can…

  • Increase the size of the applicant pool by “fishing where the fish are.”
  • Increase the quality of applicants by using monitoring to create targeted recruitment materials.
  • Increase recruiting efficiency by having a well-managed, standing presence on popular social media sites – new recruiting campaigns require less “awareness generation” time.
  • Allow HR/recruiters to be more in-touch with hiring trends via social analytics.
Horizontal bar chart of social media platforms that recruiters use. LinkedIn is at the top with 87%. Only 4% of recruiters are NOT using social media for recruitment, while 50% of recruiters plan to increase their investment in SMR in the coming year. (Source: Jobvite, 2015)

Collapse your drivers for SMMP and link them to Info-Tech’s Vendor Landscape use cases

Vendor Profiles icon

USE CASES

Social Listening and Analytics

What It Looks Like
Functionality for capturing, aggregating, and analyzing social media content in order to create actionable customer or competitive insights.

How It Works
Social listening and analytics includes features such as sentiment and contextual analysis, workflow moderation, and data visualization.

Social Publishing and Campaign Management

What It Looks Like
Functionality for publishing content to multiple networks or accounts simultaneously, and managing social media campaigns in-depth (e.g. social property management and post scheduling).

How It Works
Social publishing and campaign management include features such as campaign execution, social post integration, social asset management, and post time optimization.

Social Customer Care

What It Looks Like
Functionality for management of the social customer service queue as well as tools for expedient resolution of customer issues.

How It Works
Social customer care use case primarily relies on strong social moderation and workflow management.

Identify the organizational drivers for social media management – whether it is recruiting, public relations, customer service, marketing, or sales – and align them with the most applicable use case.

Profile and rank your top use cases for social media management using the Use-Case Fit Assessment Tool

Associated Activity icon 1.2.1 1 Hour

INPUT: Project Manager, Core project team

OUTPUT: Use-case suitability

MATERIALS: Whiteboard, Markers

PARTICIPANTS: Project Manager, Core project team

  1. Download your own version of the tool and complete the questionnaire on tab 2, Assessment.
    • Use the information gathered from your assessments and initial project scoping to respond to the prompts to identify the business and IT requirements for the tool.
    • Answer the prompts for each statement from a range of strongly disagree to strongly agree.
  2. Review the outcomes on tab 3, Results.
    • This tab provides a qualitative measure assessing the strength of your fit against the industry use-case scenarios.
  3. If not completed as a team, debrief the results and implications to your core project team.

Use the SMMP Use-Case Fit Assessment Tool to identify which areas you should focus on

Supporting Tool icon 1.3 Use Case Fit Assessment Tool
Use the Use-Case Fit Assessment Tool to understand how your unique requirements map into a specific SMMP use case.

This tool will assess your answers and determine your relative fit against the use-case scenarios.

Fit will be assessed as “Weak,” “Moderate,” or “Strong.”

Consider the common pitfalls, which were mentioned earlier, that can cause IT projects to fail. Plan and take clear steps to avoid or mitigate these concerns.

Note: These use-case scenarios are not mutually exclusive. Your organization can align with one or more scenarios based on your answers. If your organization shows close alignment to multiple scenarios, consider focusing on finding a more robust solution and concentrate your review on vendors that performed strongly in those scenarios or meet the critical requirements for each.

INFO-TECH DELIVERABLE

Sample of the SMMP Use-Case Fit Assessment Tool.

Identify the marketing, sales, and customer service metrics that you will target for improvement using an SMMP

Create measurable S.M.A.R.T. goals for the project.

Consider the following questions when building your SMMP metrics:
  1. What are the top marketing objectives for your company? For example, is building initial awareness or driving repeat customers more important?
  2. What are the corresponding social media goals for this business objective?
  3. What are some of the metrics that could be used to determine if business and social media objectives are being attained?
Use Case Sample Metric Descriptions Target Metric
Social Listening and Analytics Use a listening tool to flag all mentions of our brands or company on social Increase in mentions with neutral or positive sentiment, decrease in mentions with negative sentiment
Social Publishing and Campaign Management Launch a viral video campaign showcasing product attributes to drive increased YT traffic Net increase in unaided customer recall
Social Customer Care Create brand-specific social media pages to increase customer sentiment for individual brand extensions Net increase in positive customer sentiment (i.e. as tracked by an SMMP)

Build the metrics inventory

Associated Activity icon 1.2.2 45 Minutes

INPUT: Marketing, sales, and customer service objectives

OUTPUT: Metrics inventory

MATERIALS: Whiteboard, Markers

PARTICIPANTS: Project Manager, Core project team

  1. Identify the top marketing, sales, and customer service objectives for your company? For example, is building initial awareness or driving repeat customers more important?
  2. What are the corresponding social media goals for each business objective?
  3. What are some of the metrics that could be used to determine if business and social media objectives are being attained?
Marketing/PR Objectives Social Media Goals Goal Attainment Metrics
E.g. build a positive brand image
  • Create brand-specific social media pages to increase customer sentiment for individual brand extensions
Net increase in positive customer sentiment (i.e. as tracked by an SMMP)
E.g. increase customer mind share
  • Launch a viral video campaign showcasing product attributes to drive increased YT traffic
Net increase in unaided customer recall
E.g. monitor public mentions
  • Use a listening tool to flag all mentions of our brands or company on social
Increase in mentions with neutral or positive sentiment, decrease in mentions with negative sentiment

If you want additional support, have our analysts guide you through this phase as part of an Info-Tech Workshop Associated Activity icon

Book a workshop with our Info-Tech analysts:

Photo of an Info-Tech analyst.
  • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
  • Info-Tech analyst will join you and your team onsite at your location or welcome you to Info-Tech's historic Toronto office to participate in an innovative onsite workshop.
  • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

The following are sample activities that will be conducted by Info-Tech analysts with your team:

1.1.1

Sample of activity 1.1.1 'Assess where your organization sits on the social media maturity curve'. Assess your organization’s social media maturity

An Info-Tech analyst will facilitate a discussion to assess the maturity of your organization’s social media program and take an inventory of your current efforts across different departments (e.g. Marketing, PR, Sales, and Customer Service).

1.1.2

Sample of activity 1.1.2 'Inventory the current social media networks that must be supported by SMMP'. Inventory your current social media networks

The analyst will facilitate an exercise to catalog all social media networks used in the organization.

If you want additional support, have our analysts guide you through this phase as part of an Info-Tech Workshop Associated Activity icon

Book a workshop with our Info-Tech analysts:

1.1.3

Sample of activity 1.1.3 'Go/no-go assessment on SMMP'. Go/no go assessment on SMMP

Based on the maturity assessment, the analyst will help identify whether an SMMP will help you achieve your goals in sales, marketing, and customer service.

1.2.1

Sample of activity 1.2.1 'Profile and rank your top use cases for social media management using the Use Case Fit Assessment Tool'. Rank your top use cases for social media management

An analyst will facilitate the exercise to answer a series of questions in order to determine best-fit scenario for social media management for your organization.

1.2.2

Sample of activity 1.2.2 'Build the metrics inventory'. Build the metrics inventory

An analyst will lead a whiteboarding exercise to brainstorm and generate metrics for your organization’s social media goals.

Select and Implement a Social Media Management Platform

PHASE 2

Select an SMMP

This phase also includes Info-Tech’s SMMP Vendor Landscape Title icon for vendor slides.

Phase 2: Select an SMMP

Steps of this blueprint represented by circles of varying colors and sizes, labelled by text of different sizes. Only Phase 2 is highlighted.
Estimated Timeline: 1-3 Months

Info-Tech Insight

Taking a use-case-centric approach to vendor selection allows you to balance the need for different social capabilities between analytics, campaign management and execution, and customer service.

Major Milestones Reached
  • Vendor Selection
  • Finalized and Approved Contract

Key Activities Completed

  • RFP Process
  • Vendor Evaluations
  • Vendor Selection
  • Contract Negotiation

Outcomes from This Phase

The completed procurement of an SMMP solution.

  • Selected SMMP solution
  • Negotiated and finalized contract

Phase 2 outline

Associated Activity icon Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

Guided Implementation 2: Select an SMMP

Proposed Time to Completion: 4 weeks
Step 2.1: Analyze and shortlist SMMP vendors Step 2.2: Evaluate vendor responses
Start with an analyst kick-off call:
  • Evaluate the SMMP marketspace.
  • Re-evaluate best-fit use case.
Review findings with analyst:
  • Determine your SMMP procurement strategy.
  • Reach out to SMMP vendors.
Then complete these activities…
  • Review vendor profiles and analysis.
  • Create your own evaluation framework and shortlisting criteria.
Then complete these activities…
  • Prioritize your requirements.
  • Create an RFP for SMMP procurement.
  • Evaluate vendor responses.
  • Set up product demonstrations.
With these tools & templates:
  • SMMP Vendor Landscape (included here)
  • SMMP Vendor Shortlist Tool
With these tools & templates:
  • SMMP RFP Template
  • SMMP Vendor Demo Script Template
  • SMMP Evaluation and RFP Scoring Tool
Phase 1 Results & Insights:
  • Finalize vendor and product selection

Phase 2, Step 1: Analyze and shortlist vendors in the space

2.1

2.2

Analyze and shortlist vendors in the space Select your SMMP solution

This step will walk you through the following activities:

  • Review vendor landscape methodology
  • Shortlist SMMP vendors

This step involves the following participants:

  • Core team
  • Representative stakeholders from Digital Marketing, Sales, and IT

The SMMP Vendor Landscape includes the following sections:

VENDOR LANDSCAPE

Info-Tech's Methodology

Vendor title icon.

Vendor Landscape use-case scenarios are evaluated based on weightings of features and vendor/product considerations

Vendor Profiles icon

Use cases were scored around the features from the general scoring identified as being relevant to the functional considerations and drivers for each scenario.

Calculation Overview
Advanced Features Score X Vendor Multiplier = Vendor Performance for Each Scenario
Pie Chart of Product and Vendor Weightings.
Product and Vendor Weightings
Pie Chart of Advanced Features Weightings.
Advanced Features Weightings

Please note that both advanced feature scores and vendor multipliers are based on the specific weightings calibrated for each scenario.

Vendor performance for each use-case scenario is documented in a weighted bar graph

Vendor Profiles icon
Sample of the 'Vendor performance for the use-case scenario' slide. Vendor Performance

Vendors qualify and rank in each use-case scenario based on their relative placement and scoring for the scenario.

Vendor Ranking

Champion: The top vendor scored in the scenario

Leaders: The vendors who placed second and third in the scenario

Players: Additional vendors who qualified for the scenarios based on their scoring

Sample of the 'Value Index for the use case scenario' slide. Value ScoreTM

Each use-case scenario also includes a Value Index that identifies the Value Score for a vendor relative to their price point. This additional framework is meant to help price-conscious organizations identify vendors who provide the best “bang for the buck.”

VENDOR LANDSCAPE

Review the SMMP Vendor Evaluation

Vendor title icon.

SMMP market overview

Vendor Profiles icon

How It Got Here

  • The SMMP market was created in response to the exploding popularity of social media and the realization that it can be harnessed for a wide variety of enterprise purposes (from consumer intelligence to marketing campaigns and customer service).
  • As the number of social media services has expanded, and as the volume of content generated via social networks has ballooned, it became increasingly difficult to mine insights and manage social campaigns. A number of vendors (mostly start-ups) began offering platforms that attempted to streamline and harness social media processes.
  • As usage of social media expanded beyond just the marketing and PR function, being able to successfully scale a social strategy to a large number of customer care and sales interactions became paramount: SMMPs filled a niche by offering large-scale response and workflow management capabilities.

Where It’s Going

  • The market is segmented into two broad camps: SMMPs focused on social listening and analytics, and SMMPs focused on social engagement. Although the two have begun to converge, there continues to be a clear junction in the market between the two, with a surprising lack of vendors that are equally adept at both sides.
  • With the rise of SMMPs, the expectation was that CRM vendors would offer feature sets similar to those of standalone SMMPS. However, CRM vendors have been slow in incorporating the functionality directly into their products. While some major vendors have made ground in this direction in the last year, organizations that are serious about social will still need a best-of-breed SMMP.
  • Other major trends include using application integration to build a 360-degree view of the customer, workflow automation, and competitive benchmarking.

Info-Tech Insight

As the market evolves, capabilities that were once cutting edge become default and new functionality becomes differentiating. Supporting multiple social media services and accounts has become a Table Stakes capability and should no longer be used to differentiate solutions. Instead focus on an SMMP’s social listening, campaign management, and customer care to help you find a solution that best fits your requirements.

Review Info-Tech’s Vendor Landscape of the SMMP market to identify vendors that meet your requirements

Vendors Evaluated

Various logos of the vendors who were evaluated.

Each vendor in this landscape was evaluated based on their features, product considerations, and vendor considerations. Each vendor was profiled using these evaluations and, based on their performance, qualified and placed in specific use-case scenarios.

These vendors were included due to consideration of their market share, mind share, and platform coverage

Vendor Profiles icon

Vendors included in this report provide a comprehensive, innovative, and functional solution for integrating applications and automating their messaging.

Included in this Vendor Landscape:

Adobe: Adobe Social is a key pillar of Adobe’s ecosystem that is heavily focused on social analytics and engagement.

Hootsuite: A freemium player with strong engagement and collaboration tools, particularly well suited for SMBs.

Salesforce: Social Studio is a leading social media management solution and is a key channel of Salesforce Marketing Cloud.

Sendible: A fairly new entrant to the social media management space, Sendible offers robust campaign management capability that is well suited for agencies and SMBs.

Sprinklr: A leading solution that focuses on social customer care, offering strong ability to prioritize, route, and categorize high-volume social messaging.

Sprout Social: A great choice for mid-sized companies looking to provide robust social engagement and customer care.

Sysomos: Their MAP and Heartbeat products offer customers in-depth analysis of a wide array of social channels.

Viralheat (Cision): Now a Cision product, Viralheat is an excellent option for analytics, social response workflow management, and in-band social engagement.

Table Stakes represent the minimum standard; without these, a product doesn’t even get reviewed

Vendor Profiles icon

The Table Stakes

Feature: What it is:
Multiple Services Supported The ability to mange or analyze at least two or more social media services.
Multiple Accounts Supported The ability to manage or analyze content from at least two or more social media accounts.
Basic Engagement The ability to post status updates to multiple social media sites.
Basic Analytics The ability to display inbound feeds and summary info from multiple social media sites.

What does this mean?

The products assessed in this Vendor Landscape meet, at the very least, the requirements outlined as Table Stakes.

Many of the vendors go above and beyond the outlined Table Stakes, some even do so in multiple categories. This section aims to highlight the products’ capabilities in excess of the criteria listed here.

Info-Tech Insight

If Table Stakes are all you need from your SMMP solution, the only true differentiator for the organization is price. Otherwise, dig deeper to find the best price to value for your needs.

Advanced Features are the capabilities that allow for granular differentiation of market players and use-case performance

Vendor Profiles icon

Scoring Methodology

Info-Tech scored each vendor’s features on a cumulative four-point scale. Zero points are awarded to features that are deemed absent or unsatisfactory, one point is assigned to features that are partially present, two points are assigned to features that require an extra purchase in the vendor’s product portfolio or through a third party, three points are assigned to features that are fully present and native to the solution, and four points are assigned to the best-of-breed native feature.

For an explanation of how Advanced Features are determined, see Information Presentation – Feature Ranks (Stoplights) in the Appendix.

Feature: What we looked for:
Social Media Channel Integration - Inbound Ability to monitor social media services, such as Facebook, Twitter, LinkedIn, YouTube, and more.
Social Media Channel Integration - Outbound Ability to publish to social media services such as Facebook, Twitter, LinkedIn, YouTube, and more.
Social Response Management Ability to respond in-band to social media posts.
Social Moderation and Workflow Management Ability to create end-to-end routing and escalation workflows from social content.
Campaign Execution Ability to manage social and media assets: tools for social campaign execution, reporting, and analytics.
Social Post Archival Ability to archive social posts and platform activity to create an audit trail.
Trend Analysis Ability to monitor trends and traffic on multiple social media sites.
Sentiment Analysis Ability to analyze and uncover insights from attitudes and opinions expressed on social media.
Contextual Analysis Ability to use NLP, deep learning and semantic analysis to extract meaning from social posts.
Social Asset Management Ability to access visual asset library with access permissions and expiry dates to be used on social media.
Post Time Optimization Ability to optimize social media posts by maximizing the level of interaction and awareness around the posts.
Dashboards and Visualization Ability to visualize data and create analytics dashboards.

Vendor scoring focused on overall product attributes and vendor performance in the market

Vendor Profiles icon

Scoring Methodology

Info-Tech Research Group scored each vendor’s overall product attributes, capabilities, and market performance.

Features are scored individually as mentioned in the previous slide. The scores are then modified by the individual scores of the vendor across the product and vendor performance features.

Usability, overall affordability of the product, and the technical features of the product are considered, and scored on a five-point scale. The score for each vendor will fall between worst and best in class.

The vendor’s performance in the market is evaluated across four dimensions on a five-point scale. Where the vendor places on the scale is determined by factual information, industry position, and information provided by customer references and/or available from public sources.

Product Evaluation Features

Usability The end-user and administrative interfaces are intuitive and offer streamlined workflow.
Affordability Implementing and operating the solution is affordable given the technology.
Architecture Multiple deployment options, platform support, and integration capabilities are available.

Vendor Evaluation Features

Viability Vendor is profitable, knowledgeable, and will be around for the long term.
Focus Vendor is committed to the space and has a future product and portfolio roadmap.
Reach Vendor offers global coverage and is able to sell and provide post-sales support.
Sales Vendor channel partnering, sales strategies, and process allow for flexible product acquisition.

Balance individual strengths to find the best fit for your enterprise

Vendor Profiles icon

A list of vendors with ratings for their 'Product: Overall, Usability, Affordability, and Architecture' and their 'Vendor: Overall, Viability, Focus, Reach, and Sales'. It uses a quarters rating system where 4 quarters of a circle is Exemplary and 0 quarters is Poor.

For an explanation of how the Info-Tech Harvey Balls are calculated, see Information Presentation – Criteria Scores (Harvey Balls) in the Appendix.

Balance individual strengths to find the best fit for your enterprise

Vendor Profiles icon

A list of vendors with ratings for their 'Evaluated Features'. Rating system uses Color coding with green being 'Feature is fully present...' and red being 'Feature is absent', and if a star is in the green then 'Feature is best in its class'.

For an explanation of how Advanced Features are determined, see Information Presentation – Feature Ranks (Stoplights) in the Appendix.

Vendor title icon.

USE CASE 1

Social Listening and Analytics

Seeking functionality for capturing, aggregating, and analyzing social media content in order to create actionable customer or competitive insights.

Feature weightings for the social listening and analytics use-case scenario

Vendor Profiles icon

Core Features

Sentiment Analysis Uncovering attitudes and opinions expressed on social media is important for generating actionable customer insights.
Dashboards and Visualization Capturing and aggregating social media insights is ineffective without proper data visualization and analysis.
Trend Analysis The ability to monitor trends across multiple social media services is integral for effective social listening.
Contextual Analysis Understanding and analyzing language and visual content on social media is important for generating actionable customer insights.

Additional Features

Social Media Channel Integration – Inbound

Social Moderation and Workflow Management

Social Post Archival

Feature Weightings

Pie chart of feature weightings.

Vendor considerations for the social listening and analytics use-case scenario

Vendor Profiles icon

Product Evaluation Features

Usability A clean and intuitive user interface is important for users to fully leverage the benefits of an SMMP.
Affordability Affordability is an important consideration as the price of SMMPs can vary significantly depending on the breadth and depth of capability offered.
Architecture SMMP is more valuable to organizations when it can integrate well with their applications, such as CRM and marketing automation software.

Vendor Evaluation Features

Viability Vendor viability is critical for long-term stability of an application portfolio.
Focus The vendor is committed to the space and has a future product and portfolio roadmap.
Reach Companies with processes that cross organizational and geographic boundaries require effective and available support.
Sales Vendors need to demonstrate flexibility in terms of industry and technology partnerships to meet evolving customer needs.

Pie chart for Product and Vendor Evaluation Features.

Vendor performance for the social listening and analytics use-case scenario

Vendor Profiles icon
Champion badge.

Champions for this use case:

Salesforce: Salesforce Social Studio offers excellent trend and in-depth contextual analysis and is among the best vendors in presenting visually appealing and interactive dashboards.
Leader badge.

Leaders for this use case:

Sysomos: Sysomos MAP and Heartbeat are great offerings for conducting social media health checks using in-depth contextual analytics.

Adobe: Adobe Social is a great choice for digital marketers that need in-depth sentiment and longitudinal analysis of social data – particularly when managing social alongside other digital channels.

Best Overall Value badge.

Best Overall Value Award

Sysomos: A strong analytics capability offered in Sysomos MAP and Heartbeat at a relatively low cost places Sysomos as the best bang for your buck in this use case.

Players in the social listening and analytics scenario

  • Sprinklr
  • Hootsuite
  • Sprout Social

Vendor performance for the social listening and analytics use-case scenario

Vendor Profiles icon

Stacked bar chart comparing vendors' use-case performance in multiple areas of 'Social Listening and Analytics'.

Value Index for the social listening and analytics scenario

Vendor Profiles icon
What is a Value Score?

The Value Score indexes each vendor’s product offering and business strength relative to its price point. It does not indicate vendor ranking.

Vendors that score high offer more bang-for-the-buck (e.g. features, usability, stability) than the average vendor, while the inverse is true for those that score lower.

Price-conscious enterprises may wish to give the Value Score more consideration than those who are more focused on specific vendor/product attributes.

On a relative basis, Sysomos maintained the highest Info-Tech Value ScoreTM of the vendor group for this use-case scenario. Vendors were indexed against Sysomos’ performance to provide a complete, relative view of their product offerings.

Bar chart of vendors' Value Scores in social listening and analytics. Sysomos has the highest and the Average Score is 66.8.

For an explanation of how price is determined, see Information Presentation – Price Evaluation in the Appendix.

For an explanation of how the Info-Tech Value Index is calculated, see Information Presentation – Value Index in the Appendix.

Vendor title icon.

USE CASE 2

Social Publishing and Campaign Management

Seeking functionality for publishing content to multiple networks or accounts simultaneously, and managing social media campaigns in-depth (e.g. social property management and post scheduling).

Feature weightings for the social publishing and campaign management use-case scenario

Vendor Profiles icon

Core Features

Campaign Execution The ability to manage multiple social media services simultaneously is integral for carrying out social media campaigns.
Social Response Management Creating response workflows is equally important to publishing capability for managing social campaigns.

Additional Features

Social Media Channel Integration – Outbound

Social Moderation and Workflow Management

Social Post Archival

Social Asset Management

Post Time Optimization

Social Media Channel Integration – Inbound

Trend Analysis

Sentiment Analysis

Dashboards and Visualization

Feature Weightings

Pie chart of feature weightings.

Vendor considerations for the social publishing and campaign management use-case scenario

Vendor Profiles icon

Product Evaluation Features

Usability A clean and intuitive user interface is important for users to fully leverage the benefits of an SMMP.
Affordability Affordability is an important consideration as the price of SMMPs can vary significantly depending on the breadth and depth of capability offered.
Architecture SMMP is more valuable to organizations when it can integrate well with their applications, such as CRM and marketing automation software.

Vendor Evaluation Features

Viability Vendor viability is critical for long-term stability of an application portfolio.
Focus The vendor is committed to the space and has a future product and portfolio roadmap.
Reach Companies with processes that cross organizational and geographic boundaries require effective and available support.
Sales Vendors need to demonstrate flexibility in terms of industry and technology partnerships to meet evolving customer needs.

Pie chart of Product and Vendor Evaluation Features.

Vendor performance for the social publishing and campaign management use-case scenario

Vendor Profiles icon

Champion badge.

Champions for this use case:

Adobe: Adobe has the best social campaign execution capability in the market, enabling marketers to manage and auto-track multiple campaigns. It also offers a strong asset management feature that allows users to leverage Marketing Cloud content.
Leader badge.

Leaders for this use case:

Salesforce: SFDC has built a social marketing juggernaut, offering top-notch response workflows and campaign execution capability.

Hootsuite: Hootsuite has good response capabilities backed up by a strong team collaboration feature set. It offers simplified cross-platform posting and post-time optimization capabilities.

Best Overall Value badge.

Best Overall Value Award

Sendible: Sendible offers the best value for your money in this use case with good response workflows and publishing capability.

Players in the social publishing and campaign management scenario

  • Sprout Social
  • Sprinklr
  • Sendible

Vendor performance for the social publishing and campaign management use-case scenario

Vendor Profiles icon

Stacked bar chart comparing vendors' use-case performance in multiple areas of 'Social publishing and campaign management'.

Value Index for the social publishing and campaign management scenario

Vendor Profiles icon

What is a Value Score?

The Value Score indexes each vendor’s product offering and business strength relative to its price point. It does not indicate vendor ranking.

Vendors that score high offer more bang-for-the-buck (e.g. features, usability, stability) than the average vendor, while the inverse is true for those that score lower.

Price-conscious enterprises may wish to give the Value Score more consideration than those who are more focused on specific vendor/product attributes.

On a relative basis, Sendible maintained the highest Info-Tech Value ScoreTM of the vendor group for this use-case scenario. Vendors were indexed against Sendible’s performance to provide a complete, relative view of their product offerings.

Bar chart of vendors' Value Scores in social publishing and campaign management. Sendible has the highest and the Average Score is 72.9.

For an explanation of how Price is determined, see Information Presentation – Price Evaluation in the Appendix.

For an explanation of how the Info-Tech Value Index is calculated, see Information Presentation – Value Index in the Appendix.

Vendor title icon.

USE CASE 3

Social Customer Care

Seeking functionality for management of the social customer service queue as well as tools for expedient resolution of customer issues.

Feature weightings for the social customer care use-case scenario

Vendor Profiles icon

Core Features

Social Moderation and Workflow Management Creating escalation workflows is important for triaging customer service, managing the social customer service queue and offering expedient resolution to customer complaints.

Additional Features

Social Media Channel Integration – Outbound

Social Moderation and Workflow Management

Social Response Management

Social Post Archival

Sentiment Analysis

Dashboards and Visualization

Campaign Execution

Trend Analysis

Post Time Optimization

Feature Weightings

Pie chart with Feature Weightings.

Vendor considerations for the social customer case use-case scenario

Vendor Profiles icon

Product Evaluation Features

Usability A clean and intuitive user interface is important for users to fully leverage the benefits of an SMMP.
Affordability Affordability is an important consideration as the price of SMMPs can vary significantly depending on the breadth and depth of capability offered.
Architecture SMMP is more valuable to organizations when it can integrate well with their applications, such as CRM and marketing automation software.

Vendor Evaluation Features

Viability Vendor viability is critical for long-term stability of an application portfolio.
Focus The vendor is committed to the space and has a future product and portfolio roadmap.
Reach Companies with processes that cross organizational and geographic boundaries require effective and available support.
Sales Vendors need to demonstrate flexibility in terms of industry and technology partnerships to meet evolving customer needs.

Pie chart with Product and Vendor Evaluation Features.

Vendor performance for the social customer care use-case scenario

Vendor Profiles icon

Champion badge.

Champions for this use case:

Salesforce: Salesforce offers exceptional end-to-end social customer care capability with strong response escalation workflows.
Leader badge.

Leaders for this use case:

Sprinklr: Sprinklr’s offering gives users high flexibility to configure escalation workflows and role-based permissions for managing the social customer service queue.

Hootsuite: Hootsuite’s strength lies in the breadth of social networks that the platform supports in offering expedient resolution to customer complaints.

Best Overall Value badge.

Best Overall Value Award

Sysomos: Sysomos is the best bang for your buck in this use case, offering essential response and workflow capabilities.

Players in the social listening and analytics scenario

  • Sendible
  • Sysomos
  • Viralheat (Cision)

Vendor performance for the social customer care use-case scenario

Vendor Profiles icon

Stacked bar chart comparing vendors' use-case performance in multiple areas of 'Social customer care'.

Value Index for the social customer care scenario

Vendor Profiles icon

What is a Value Score?

The Value Score indexes each vendor’s product offering and business strength relative to its price point. It does not indicate vendor ranking.

Vendors that score high offer more bang-for-the-buck (e.g. features, usability, stability) than the average vendor, while the inverse is true for those that score lower.

Price-conscious enterprises may wish to give the Value Score more consideration than those who are more focused on specific vendor/product attributes.

On a relative basis, Sendible maintained the highest Info-Tech Value ScoreTM of the vendor group for this use-case scenario. Vendors were indexed against Sendible’s performance to provide a complete, relative view of their product offerings.

Bar chart of vendors' Value Scores in social customer care. Sysomos has the highest and the Average Score is 79.6.

For an explanation of how Price is determined, see Information Presentation – Price Evaluation in the Appendix.

For an explanation of how the Info-Tech Value Index is calculated, see Information Presentation – Value Index in the Appendix.

VENDOR LANDSCAPE

Vendor Profiles and Scoring

Vendor title icon.

Use the information in the SMMP Vendor Landscape analysis to streamline your own vendor analysis process

Vendor Profiles icon

This section of the Vendor Landscape includes the profiles and scoring for each vendor against the evaluation framework previously outlined.

Sample of the SMMP Vendor Landscape analysis. Vendor Profiles
  • Include an overview for each company.
  • Identify the strengths and weaknesses of the product and vendor.
  • Identify the three-year TCO of the vendor’s solution (based on a ten-tiered model).
Sample of the Vendor Landscape profiles slide.
Vendor Scoring

Use the Harvey Ball scoring of vendor and product considerations to assess alignment with your own requirements.

Review the use-case scenarios relevant to your organization’s Use-Case Fit Assessment results to identify a vendor’s fit to your organization's SMMP needs. (See the following slide for further clarification on the use-case assessment scoring process.)

Review the stoplight scoring of advanced features to identify the functional capabilities of vendors.

Sample of the Vendor Scoring slide.

Adobe Social is a powerhouse for digital marketers, with extremely well-developed analytics capabilities

Vendor Profiles icon
Product Adobe Social
Employees 15,000+
Headquarters San Jose, CA
Website Adobe.com
Founded 1982
Presence NASDAQ: ADBE

Logo for Adobe.

3 year TCO for this solution falls into pricing tier 8 between $500,000 and $1,000,000.

Pricing tier for Adobe, tier 8.
Pricing provided by vendor

OVERVIEW
  • Adobe Social is a strong offering included within the broader Adobe Marketing Cloud. The product is tightly focused on social analytics and social campaign execution. It’s particularly well-suited to dedicated digital marketers or social specialists.
STRENGTHS
  • Adobe Social provides broad capabilities across social analytics and social campaign management; its integration with Adobe Analytics is a strong selling point for organizations that need a complete, end-to-end solution.
  • It boasts great archiving capabilities (up to 7 years for outbound posts), meeting the needs of compliance-centric organizations and providing for strong longitudinal analysis capabilities.
CHALLENGES
  • The product plays well with the rest of the Adobe Marketing Cloud, but the list of third-party CRM and CSM integrations is shorter than some other players in the market.
  • While the product is unsurprisingly geared towards marketers, organizations that want a scalable platform for customer service use cases will need to augment the product due to its focus on campaigns and analytics – service-related workflow and automation capabilities are not a core focus for the company.

Adobe Social

Vendor Profiles icon
'Product' and 'Vendor' scores for Adobe. Overall product is 3/4; overall vendor is 4/4.
'Scenario Performance' awards and 'Value Index' in the three previous scenarios. Adobe earned 'Leader' in Social Listening & Analytics and 'Champion' in Social Publishing & Campaign Management.
Info-Tech Recommends

Adobe Social provides impressive features, especially for companies that position social media within a larger digital marketing strategy. Organizations that need powerful social analytics or social campaign execution capability should have Adobe on their shortlist, though the product may be an overbuy for social customer care use cases.

Scores for Adobe's individual features, color-coded as they were previously.

Hootsuite is a capable vendor that offers a flexible solution for monitoring many different social media services

Vendor Profiles icon
Product Hootsuite
Employees 800
Headquarters Vancouver, BC
Website Hootsuite.com
Founded 2007
Presence Privately held

Logo for Hootsuite.

3 year TCO for this solution falls into pricing tier 6, between $100,000 and $250,000.

Pricing tier for Hootsuite, tier 6.
Pricing derived from public information

OVERVIEW
  • In the past, Hootsuite worked on the freemium model by providing basic social account management features. The company has since expanded its offering and put a strong focus on enterprise feature sets, such as collaboration and workflow management.
STRENGTHS
  • Hootsuite is extremely easy to use, having one of the most straightforward interfaces of vendors evaluated.
  • It has extensive monitoring capabilities for a wide variety of social networks as well as related services, which are supported through an app store built into the Hootsuite platform.
  • The product provides a comprehensive model for team-based collaboration and workflow management, demonstrated through nice cross-posting and post-time optimization capabilities.
CHALLENGES
  • Hootsuite’s reporting and analytics capabilities are relatively basic, particularly when contrasted with more analytics-focused vendors in the market.
  • Running cross-channel campaigns is challenging without integration with third-party applications.

Hootsuite

Vendor Profiles icon
'Product' and 'Vendor' scores for Hootsuite. Overall product is 3/4; overall vendor is 4/4.
'Scenario Performance' awards and 'Value Index' in the three previous scenarios. Hootsuite earned 5th out of 6 in Social Listening & Analytics, 'Leader' in Social Publishing & Campaign Management, and 'Leader' in Social Customer Care.
Info-Tech Recommends

The free version of Hootsuite is useful for getting your feet wet with social management. The paid version is a great SMMP for monitoring and engaging your own social properties with good account and team management at an affordable price. This makes it ideal for SMBs. However, organizations that need deep social analytics may want to look elsewhere.

Scores for Hootsuite's individual features, color-coded as they were previously.

Salesforce Marketing Cloud continues to be a Cadillac solution; it’s a robust platform with a host of features

Vendor Profiles icon
Product Salesforce Social Studio
Employees 24,000+
Headquarters San Francisco, CA
Website Salesforce.com
Founded 1999
Presence NASDAQ: CRM

Logo for Salesforce.

3 year TCO for this solution falls into pricing tier 7, between $250,000 and $500,000

Pricing tier for Salesforce, tier 7.
Pricing provided by vendor

OVERVIEW
  • Social Studio is a powerful solution fueled by Salesforce’s savvy acquisitions in the marketing automation and social media management marketspace. The product has rapidly matured and is adept at both marketing and customer service use cases.
STRENGTHS
  • Salesforce continues to excel as one of the best SMMP vendors in terms of balancing inbound analytics and outbound engagement. The recent addition of Salesforce Einstein to the platform bolsters deep learning capabilities and enhances the product’s value proposition to those that want a tool for robust customer intelligence.
  • Salesforce’s integration of Marketing Cloud, with its Sales and Service Clouds, also creates a good 360-degree customer view.
CHALLENGES
  • Salesforce’s broad and deep feature set comes at a premium: the solution is priced materially higher than many other vendors. Before you consider Marketing Cloud, it’s important to evaluate which social media capabilities you want to develop: if you only need basic response workflows or dashboard-level analytics, purchasing Marketing Cloud runs the risk of overbuying.
  • In part due to its price point and market focus, Marketing Cloud is more suited to enterprise use cases than SMB use cases.

Salesforce

Vendor Profiles icon
'Product' and 'Vendor' scores for  . Overall product is 3/4; overall vendor is 4/4.
'Scenario Performance' awards and 'Value Index' in the three previous scenarios. Salesforce earned 'Champion' in Social Listening & Analytics, 'Leader' in Social Publishing & Campaign Management, and 'Champion' in Social Customer Care.
Info-Tech Recommends

Social Studio in Salesforce Marketing Cloud remains a leading solution. Organizations that need to blend processes across the enterprise that rely on social listening, deep analytics, and customer engagement should have the product on their shortlist. However, companies with more basic needs may be off-put by the solution’s price point.

Scores for 's individual features, color-coded as they were previously.

Sendible offers multiple social media management capabilities for SMBs and agencies

Vendor Profiles icon
Product Sendible
Employees 27
Headquarters London, UK
Website Sendible.com
Founded 2009
Presence Privately held

Logo for Sendible.

3 year TCO for this solution falls into pricing tier 4, between $25,000 and $50,000

Pricing tier for Sendible, tier 4.
Pricing derived from public information

OVERVIEW
  • Founded in 2009, Sendible is a rising player in the SMMP market. Sendible is primarily focused on the SMB space. A growing segment of its client base is digital marketing agencies and franchise companies.
STRENGTHS
  • Sendible’s user interface is very intuitive and user friendly.
  • The product offers the ability to manage multiple social accounts simultaneously as well as schedule posts to multiple groups on different social networks, making Sendible a strong choice for social engagement and customer care.
  • Its affordability is strong given its feature set, making it an attractive option for organizations that are budget conscious.
CHALLENGES
  • Sendible remains a smaller vendor in the market – its list of channel partners lags behind larger incumbents.
  • Sendible’s contextual and visual content analytics are lacking vis-à-vis more analytics-centric vendors.

Sendible

Vendor Profiles icon
'Product' and 'Vendor' scores for Sendible. Overall product is 3/4; overall vendor is 4/4.
'Scenario Performance' awards and 'Value Index' in the three previous scenarios. Sendible earned 6th out of 6 and 'Best Overall Value' in Social Publishing & Campaign Management and 4th out of 6 in Social Customer Care.
Info-Tech Recommends

Sendible offers a viable solution for small and mid-market companies, as well as social agencies with a focus on customer engagement for marketing and customer service use cases. However, organizations that need deep social analytics may want to look elsewhere.

Scores for Sendible's individual features, color-coded as they were previously.

Sprinklr

Vendor Profiles icon
Product Sprinklr
Employees 1,100
Headquarters New York, NY
Website Sprinklr.com
Founded 2009
Presence Privately held

Logo for Sprinklr.

Pricing tier for Sprinklr, tier 6.
Pricing derived from public information

OVERVIEW
  • Sprinklr has risen rapidly as a best-of-breed player in the social media management market. It markets a solution geared towards multiple use cases, from customer intelligence and analytics to service-centric response management.
STRENGTHS
  • Sprinklr’s breadth of capabilities are impressive: the vendor has maintained a strong focus on social-specific functionality. As a result of this market focus, they have invested prudently in advanced social analytics and moderation workflow capabilities.
  • Sprinklr’s user experience design and data visualization capabilities are top-notch, making it a solution that’s easy for end users and decision makers to get up and running with quickly.
CHALLENGES
  • Relative to other players in the market, the breadth and scope of Sprinklr’s integrations with other customer experience management solutions is limited.
  • Based on its feature set and price point, Sprinklr is best suited for mid-to-large organizations. SMBs run the risk of an overbuy situation.

Sprinklr

Vendor Profiles icon

'Product' and 'Vendor' scores for Sprinklr. Overall product is 3/4; overall vendor is 3/4.
'Scenario Performance' awards and 'Value Index' in the three previous scenarios. Sprinklr earned 4th out of 6 in Social Listening & Analytics, 5th out of 6 in Social Publishing & Campaign Management, and 'Leader' in Social Customer Care.
Info-Tech Recommends

Sprinklr is a strong choice for small and mid-market organizations offering breadth of social media management capabilities that covers social analytics, engagement, and customer service.

Scores for Sprinklr's individual features, color-coded as they were previously.

Sprout Social provides small-to-medium enterprises with robust social response capabilities at a reasonable price

Vendor Profiles icon
Product Sprout Social
Employees 200+
Headquarters Chicago, IL
Website Sproutsocial.com
Founded 2010
Presence Privately held

Logo for Sprout Social.

3 year TCO for this solution falls into pricing tier 6, between $100,000 and $250,000

Pricing tier for Sprout Social, tier 6.
Pricing derived from public information

OVERVIEW
  • Sprout Social has built out its enterprise capabilities over the last several years. It offers strong feature sets for account management, social monitoring and analytics, and customer care – it particularly excels at the latter.
STRENGTHS
  • Sprout’s unified inbox and response management features are some of the most intuitive we’ve seen. This makes it a natural option for providing customer service via social channels.
  • Sprout Social is priced competitively in relation to other vendors.
  • The product provides strong social asset management capabilities where users can set content permissions and expiration dates, and limit access.
CHALLENGES
  • Deep contextual analysis is lacking: the solution clearly falls more to the engagement side of the spectrum, and is particularly suited for social customer service.
  • Sprout Social has a limited number of technology partners for integrations with applications such as CRM and marketing automation software.
  • It still has a predominantly North American market focus.

Sprout Social

Vendor Profiles icon
'Product' and 'Vendor' scores for Sprout Social. Overall product is 3/4; overall vendor is 3/4.
'Scenario Performance' awards and 'Value Index' in the three previous scenarios. Sprout Social earned 6th out of 6 in Social Listening & Analytics and 4th out of 6 in Social Publishing & Campaign Management.
Info-Tech Recommends

Sprout Social’s easy-to-understand benchmarking and dashboards, paired with strong response management, make it a great choice for mid-sized enterprises concerned with social engagement. However, organizations that want to do deep social analytics will need to augment the solution.

Scores for Sprout Social's individual features, color-coded as they were previously.

Sysomos’ prime feature is its hardy analytics built atop a plethora of inbound social channels

Vendor Profiles icon

Product Sysomos MAP and Heartbeat
Employees 200+
Headquarters Toronto, ON
Website Sysomos.com
Founded 2007
Presence Privately held

Logo for Sysomos.

3 year TCO for this solution falls into pricing tier 4, between $25,000 and $50,000

Pricing tier for Sysomos, tier 4.
Pricing derived from public information

OVERVIEW
  • Sysomos began life as a project at the University of Toronto prior to its acquisition by Marketwire in 2010.
  • It split from Marketwire in 2015 and redesigned its product to focus on social monitoring, analysis, and engagement.

STRENGTHS

  • MAP and Heartbeat offer extensive contextual and sentiment analytics, consolidating findings through a spam-filtering process that parses out a lot of the “noise” inherent in social media data.
  • The solution provides an unlimited number of profiles, enabling more opportunities for collaboration.
  • It provides workflow summaries, documenting the actions of staff and providing an audit trail through the entire process.

CHALLENGES

  • Sysomos has introduced a publishing tool for social campaigns. However, its outbound capabilities continue to lag, and there are currently no tools for asset management.
  • Sysomos’ application integration stack is limited relative to other vendors.

Sysomos

Vendor Profiles icon
'Product' and 'Vendor' scores for Sysomos. Overall product is 3/4; overall vendor is 3/4.
'Scenario Performance' awards and 'Value Index' in the three previous scenarios. Sysomos earned 'Leader' and 'Best Overall Value' in Social Listening & Analytics and 5th out of 6 as well as 'Best Overall Value' in Social Customer Care.
Info-Tech Recommends

Sysomos’ broad array of good features has made it a frequent challenger to Marketing Cloud on analytics-centric SMMP evaluation shortlists. Enterprise-scale customers specifically interested in social listening and analytics, rather than customer engagement and campaign execution, will definitely want to take a look.

Scores for Sysomos's individual features, color-coded as they were previously.

Viralheat offers a clean analysis of an organization’s social media activity and has beefed up response workflows

Vendor Profiles icon

Product Viralheat
Employees 1,200
Headquarters Chicago, IL
Website Cision.com
Founded 2015
Presence Privately held

Logo for Cision (Viralheat).

3 year TCO for this solution falls into pricing tier 6, between $100,000 and $250,000

Pricing tier for Cision (Viralheat), tier 6.
Pricing derived from public information

OVERVIEW
  • Viralheat has been in the social media market since 2009. It provides tools for analytics and in-band social engagement.
  • The company was acquired by Cision in 2015, a Chicago-based public relations technology company.

STRENGTHS

  • Viralheat offers robust workflow management capabilities for social response and is particularly useful for customer service.
  • The product has strong post time optimization capability through its ViralPost scheduling feature.
  • Cision’s acquisition of Viralheat makes the product a great choice for third-party social media management, namely public relations and digital marketing agencies.

CHALLENGES

  • Viralheat remains a smaller vendor in the market – its list of channel partners lags behind larger incumbents.
  • Contextual and sentiment analysis are lacking relative to other vendors.

Cision (Viralheat)

Vendor Profiles icon
'Product' and 'Vendor' scores for Cision (Viralheat). Overall product is 3/4; overall vendor is 2/4.
'Scenario Performance' awards and 'Value Index' in the three previous scenarios. Cision (Viralheat) earned  in Social Listening & Analytics,  in Social Publishing & Campaign Management, and  in Social Customer Care.
Info-Tech Recommends

Cision has upped its game in terms of social workflow and response management and it monitors an above-average number of services. It is a steadfast tool for brands that are primarily interested in outbound customer engagement for marketing and customer service use cases.

Scores for Cision (Viralheat)'s individual features, color-coded as they were previously.

Use the SMMP Vendor Shortlist Tool to customize the vendor analysis for your organization

Vendor Profiles icon SMMP Vendor Shortlist & Detailed Feature Analysis Tool

Instructions

  1. Eliminate misaligned vendors with knock-out criteria
    Use the SMMP Vendor Shortlist &am; Detailed Feature Analysis Tool to eliminate vendors based on specific knock-out criteria on tab 2, Knock-Out Criteria.
  2. Create your own evaluation framework
    Tailor the vendor evaluation to include your own product and vendor considerations on tab 3, Weightings. Identify the significance of advanced features for your own procurement on a scale of Mandatory, Optional, and Not Required on tab 4, Detailed Feature Analysis.
  3. Review the results of your customized evaluation
    Review your custom vendor shortlist on tab 5, Results.
This evaluation uses both functional and architectural considerations to eliminate vendors.

Knock-Out Criteria

COTS vs. Open Source
Deployment Models

Sample of the SMMP Vender Shortlist & Detailed Feature Analysis Tool tab 5, Results.
Sample Vendor Shortlist from tab 5, Results

Interpreting the Results
Your custom shortlist will rank vendors that passed the initial knock-out criteria based on their overall score.
The shortlist will provide broken-down scoring, as well as a custom value index based on the framework set in the tool.

Phase 2, Step 2: Select your SMMP solution

2.1

2.2

Analyze and shortlist vendors in the space Select your SMMP solution

This step will walk you through the following activities:

  • Prioritize your solution requirements.
  • Create an RFP to submit to vendors.
  • Solicit and review vendor proposals.
  • Conduct onsite vendor demonstrations.
  • Select the right solution.

This step involves the following participants:

  • Core Project Team
  • Procurement Manager
  • Representative Stakeholders from Digital Marketing, Sales, and IT

Outcomes of this step:

  • SMMP Selection Strategy

Determine your SMMP procurement strategy

Critical Points and Checks in Your Procurement
  • Follow your own organization’s procurement procedures to ensure that you adhere to your organization’s policies.
  • Based on your organization’s policies, identify if you are going to conduct a private or public RFP process.
    • If your RFP will contain sensitive information, use a private RFP process that is directed to specific vendors in order to protect the proprietary practices of your business.

Info-Tech Insight

If you are still not sure of a vendor’s capabilities, we recommend sending an RFI before proceeding with an RFP.

INFO-TECH OPPORTUNITY

If your organization lacks a clear procurement process, refer to Info-Tech's Optimize IT Procurement research to help construct a formal process for selecting application technology.

Info-Tech’s 15-Step Procurement Process

Use Info-Tech's procurement process to ensure that your SMMP selection is properly planned and executed.

  1. Initiate procurement.
  2. Select procurement manager.
  3. Prepare for procurement; check that prerequisites are met.
  4. Select appropriate procurement vehicle.
  5. Assemble procurement teams.
  6. Create procurement project plan.
  7. Identify and notify vendors about procurement.
  8. Configure procurement process.
  9. Gather requirements.
  10. Prioritize requirements.
  11. Build the procurement documentation package.
  12. Issue the procurement.
  13. Evaluate proposals.
  14. Recommend a vendor.
  15. Present to management.

Much of your procurement process should already be outlined from your charter and initial project structuring.
In this stage of the process, focus on the successful completion of steps 7-15.

Prioritize your solution requirements based on your business, architecture, and performance needs

Associated Activity icon

INPUT: Requirements Workbook and requirements gathering findings

OUTPUT: Full documentation of requirements for the RFP and solution evaluation process

Completed in Section 3

  1. Identify Your Requirements
    Use the findings being collected in the Requirements Workbook and related materials to define clear requirements around your organization’s desired SMMP.
  2. Prioritize Your Requirements
    • Identify the significance of each requirement for your solution evaluation.
    • Identify features and requirements as mandatory, important, or optional.
    • Control the number of mandatory requirements you document. Too many mandatory requirements could create an unrealistic framework for evaluating solutions.
  3. Create a Requirements Package
    • Consolidate your identified requirements into one list, removing redundancies and conflicts.
    • Categorize the requirements based on their priority and nature.
    • Use this requirements package as you evaluate vendors and create your RFP for shortlisted vendors.

Info-Tech Insight

No solution will meet 100% of your requirements. Control the number of mandatory requirements you place in your procurement process to ensure that vendors that are the best fit for your organization are not eliminated unnecessarily.

Create an RFP to submit to vendors

Supporting Tool icon Request for Proposal Template
Associated Activity icon Activity: Interpreting the Results

INPUT: Requirements package, Organization’s procurement procedures

OUTPUT: RFP

MATERIALS: Whiteboard and markers

PARTICIPANTS: Project manager, Core project team

Leverage Info-Tech’s SMMP RFP Template to convey your desired suite requirements to vendors and outline the proposal and procurement steps set by your organization.

Build Your RFP
  1. Outline the organization's procurement instructions for vendors (Sections 1, 3, and 5).
  2. Input the requirements package created in Activity 5.2 into your RFP (Section 4).
  3. Create a scenario overview to provide vendors an opportunity to give an estimated price.

Approval Process

Each organization has a unique procurement process; follow your own organization’s process as you submit your RFPs to vendors.

  1. Ensure compliance with your organization's standards and gain approval for submitting your RFP.

Info-Tech RFP
Table of Contents

  1. Statement of Work
  2. General Information
  3. Proposal Preparation Instructions
  4. Scope of Work, Specifications, and Requirements
  5. Vendor Qualifications and References
  6. Budget and Estimated Pricing
  7. Vendor Certification

Standardize the potential responses from vendors and streamline your evaluation with a response template

Supporting Tool icon Vendor Response Template
Sample of the Vendor Response Template. Adjust the scope and content of the Vendor Response Template to fit your SMMP procurement process and vendor requirements.

Section

Why is this section important?

About the Vendor This is where the vendor will describe itself and prove its organizational viability.
Understanding of the Challenge Demonstrates that understanding of the problem is the first step in being able to provide a solution.
Methodology Shows that there is a proven methodology to approach and solve the challenge.
Proposed Solution Describes how the vendor will address the challenge. This is a very important section as it articulates what you will receive from the vendor as a solution.
Project Management, Plan, and Timeline Provides an overview of the project management methodology, phases of the project, what will be delivered, and when.
Vendor Qualifications Provides evidence of prior experience with delivering similar projects for similar clients.
References Provides contact information for individuals/organizations for which the vendor has worked and who can vouch for the experience and success of working with this vendor.
Value Added Services Remember, this could lead to a long-term relationship. It’s not only about what you need now, but also what you may need in the future.
Requirements Confirmation from the vendor as to which requirements it can meet and how it will meet them.

Evaluate the RFPs you receive within a clear scoring process

Supporting Tool icon SMMP RFP Evaluation and Scoring Tool
Steps to follow: 'Review, Evaluate, Shortlist, Brief, Select' with the first 3 highlighted.

Associated Activity icon Activity

Build a fair evaluation framework that evaluates vendor solutions against a set criteria rather than relative comparisons.

INSTRUCTIONS

  1. Have members of the SMMP evaluation team review the RFP responses given by vendors.
  2. Input vendor solution information into the SMMP RFP Evaluation and Scoring Tool.
  3. Analyze the vendors against your identified evaluation framework.
  4. Identify vendors with whom you wish to arrange vendor briefings.
  5. Contact vendors and arranging briefings.
How to use this tool
  • Review the feature list and select where each feature is mandatory, desirable, or not applicable.
  • Select if each feature has been met by the vendor RFP response.
  • Enter the costing information provided by each vendor.
  • Determine the relative importance of the features, architecture, and support.
Tool Output
  • Costing
  • Overall score
  • Evaluation notes and comments

Vendor product demonstration

Vendor Profiles icon Demo Script Template

Demo

Invite vendors to come onsite to demonstrate the product and to answer questions. Use a demo script to help identify how a vendor’s solution will fit your organization’s particular business capability needs.
Make sure the solution will work for your business

Provide the vendor with some usage patterns for the SMMP tool in preparation for the vendor demo.

Provide the following information to vendors in your script:

  • Usage for different groups.
  • SMMP usage and [business analytics] usage.
  • The requirements for administration.
How to challenge the vendors in the demo
  • Change visualization/presentation.
  • Change the underlying data.
  • Add additional datasets to the artifacts.
  • Collaboration capabilities.
  • Perform an investigation in terms of finding BI objects and identifying previous changes, and examine the audit trail.
Sample of the SMMP Demo Script Template
SMMP Demo Script Template

INFO-TECH ACTIVITY

INPUT: Requirements package, Use-case results

OUTPUT: Onsite demo

  1. Create a demo script that will be sent to vendors that outlines SMMP usage patterns from your organization.
  2. Construct the demo script with your SMMP evaluation team, providing both prompts for the vendor to display the capabilities and some sample data for the vendor to model.

Use vendor RFPs and demos to select the SMMP that best fits your organization’s needs

Supporting Tool icon Suite Evaluation and Scoring Tool: Tab 5, Overall Score

Don’t just choose the vendor who gave the best presentation. Instead, select the vendor who meets your functional requirements and organizational needs.

Category Weight Vendor 1 Vendor 2 Vendor 3 Vendor 4
SMMP Features 60% 75% 80% 80% 90%
Architecture 25% 55% 60% 90% 90%
Support 15% 10% 70% 60% 95%
Total Score 100% 60% 74% 80% 91%
Use your objective evaluation to select a vendor to recommend to management for procurement. Arrow from 'Vendor 4' to post script.

Don’t automatically decide to go with the highest score; validate that the vendor is someone you can envision working with for the long term.

  • Select a vendor based not only on their evaluation performance, but also on your belief that you could form a lasting and supportive relationship with them.
  • Integration needs are dynamic, not static. Find an SMMP tool and vendor that have strong capabilities and will fit with the application and integration plans of the business.
  • In many cases, you will require professional services together with your SMMP purchase to make sure you have some guidance in the initial development and your own staff are trained properly.

Following the identification of your selected suite, submit your recommendation to the organization’s management or evaluation team for final approval.

If you want additional support, have our analysts guide you through this phase as part of an Info-Tech Workshop Associated Activity icon

Book a workshop with our Info-Tech analysts:

Photo of an Info-Tech analyst.
  • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
  • Info-Tech analyst will join you and your team onsite at your location or welcome you to Info-Tech's historic Toronto office to participate in an innovative onsite workshop.
  • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

The following are sample activities that will be conducted by Info-Tech analysts with your team:

Sample of 'Create an RFP to submit to vendors' slide with 'Request for Proposal Template'. Create an RFP for SMMP procurement

Our Info-Tech analyst will walk you through the RFP preparation to ensure the SMMP requirements are articulated clearly to vendors in this space.

Sample of 'Vendor product demonstration' slide with 'Demo Script Template'. Create SMMP demo scripts

An analyst will walk you through the demo script preparation to guide the SMMP product demonstrations and briefings offered by vendors. The analyst will ensure the demo script addresses key requirements documented earlier in the process.

Select and Implement a Social Media Management Platform

PHASE 3

Review Implementation Considerations

Phase 3: Review implementation considerations

Steps of this blueprint represented by circles of varying colors and sizes, labelled by text of different sizes. Only Phase 3 is highlighted.
Estimated Timeline:

Info-Tech Insight

Even a solution that is a perfect fit for an organization will fail to generate value if it is not properly implemented or measured. Conduct the necessary planning before implementing your SMMP.

Major Milestones Reached
  • Plan for implementation and expected go-live date

Key Activities Completed

  • SMMP Implementation Plan
  • Governance Plan
  • Change Control Methods

Outcomes from This Phase

Plans for implementing the selected SMMP tool.

Phase 3 outline

Associated Activity icon Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

Guided Implementation 3: Review Implementation Considerations

Proposed Time to Completion: 2 weeks
Step 3.1: Establish best practices for SMMP implementation Step 3.2: Assess the measured value from the project
Start with an analyst kick-off call:
  • Determine the right governance structure to overlook the SMMP implementation.
  • Identify integrations with other applications.
  • Establish an ongoing maintenance plan.
  • Assess the different deployment models.
Review findings with analyst:
  • Determine the key performance indicators for each department using the SMMP
  • Identify key performance indicators for business units using an SMMP
Then complete these activities…
  • Establish a governance structure for social media.
  • Specify data linkages with CRM.
  • Identify risks and mitigation strategies
  • Determine the right deployment model for your organization.
Then complete these activities…
  • Identify key performance indicators for business units using an SMMP
With these tools & templates:
  • Social Media Steering Committee
Phase 3 Results & Insights:
  • Implementation Plan
  • SMMP KPIs

Phase 3, Step 1: Establish best practices for SMMP implementation

3.1

3.2

Establish best practices for SMMP implementation Assess the measured value from the project

This step will walk you through the following activities:

  • Establish a governance structure for social media management.
  • Specify the data linkages you will need between your CRM platform and SMMP.

This step involves the following participants:

  • Core Project Team

Outcomes of this step

  • Social Media Steering Committee Charter
  • SMMP data migration Inventory
  • Determination of the deployment model that works best for your organization
  • Deployment Model

Follow these steps for effective SMMP implementation

What to Consider

  • Creating an overall social media strategy is the critical first step in implementing an SMMP.
  • Selecting an SMMP involves gathering business requirements, then translating those requirements into specific selection criteria. Know exactly what your business needs are to ensure the right SMMP is selected.
  • Implement the platform with an eye toward creating business value: establish points of integration with the existing CRM solution, establish ongoing maintenance policies, select the right deployment model, and train end users around role-based objectives.
Arrow pointing down.

Plan

  • Develop a strategy for customer interaction
  • Develop a formal strategy for social media
  • Determine business requirements
Arrow pointing down.

Create RFP

  • Translate into functional requirements
  • Determine evaluation criteria
Arrow pointing down.

Evaluate

  • Evaluate vendors against criteria
  • Shortlist vendors
  • Perform in-depth vendor review

Implement

  • Integrate with existing CRM ecosystem (if applicable)
  • Establish ongoing maintenance policies
  • Map deployment to organizational models
  • Train end-users and establish acceptable use policies
  • Designate an SMMP subject matter expert

Before deploying the SMMP, ensure the right social media governance structures are in place to oversee implementation

An SMMP is a tool, not a substitute, for adequate cross-departmental social media oversight. You must coordinate efforts across constituent stakeholders.

  • Successful organizations have permanent governance structures in place for managing social media. For example, mature companies leverage Social Media Steering Committees (SMSCs) to coordinate the social media initiatives of different business units and departments. Large organizations with highly complex needs may even make use of a physical command center.
  • Compared to traditional apps projects (like CRM or ERP), social media programs tend to start as grassroots initiatives. Marketing and Public Relations departments are the most likely to spearhead the initial push, often selecting their own tools without IT involvement or oversight. This causes application fragmentation and a proliferation of shadow IT.
  • This organic adoption contrasts with the top-down approach many IT leaders are accustomed to. Bottom-up growth can ensure rapid response to social media opportunities, but it also leads to insufficient coordination. A conscious effort should be made to mature your social media strategy beyond this disorganized initial state.
  • IT can help be a “cat herder” to shepherd departments into shared initiatives.

Info-Tech Best Practice

Before implementing the SMMP, go through the appropriate organizational governance structures to ensure they have input into the deployment. If a social media steering committee is not already in place, rolling out an SMMP is a great opportunity to get one going. See our research on social media program execution for more details.

Establish a governance structure for social media management

Associated Activity icon 3.1.1 60 minutes

INPUT: Project stakeholders, SMMP mandate

OUTPUT: Social Media Governance Structure

MATERIALS: Whiteboard, Markers

PARTICIPANTS: Project Manager, Core project team

  1. Describe the unique role that the governance team will play in social media management.
  2. Describe the overall purpose statement of the governance team.
  3. Define the roles and responsibilities of the governance team.
  4. Document the outcome in the Social Media Steering Committee Charter.

EXAMPLE

Executive Sponsorship
Social Media Steering Committee
VP Marketing VP Sales VP Customer Service VP Public Relations CIO/ IT Director
Marketing Dept. Sales Dept. Customer Service Dept. Public Relations Dept. IT Dept.

Use Info-Tech’s Social Media Steering Committee Charter Template to define roles and ensure value delivery

Supporting Tool icon 3.1

Leaders must ensure that the SMSC has a formal mandate with clear objectives, strong executive participation, and a commitment to meeting regularly. Create an SMSC Charter to formalize the committee governance capabilities.

Developing a Social Media Steering Committee Charter:
  • Outline the committee’s structure, composition, and responsibilities using the Info-Tech Social Media Steering Committee Charter Template.
  • This template also outlines the key tasks and responsibilities for the committee:
    • Providing strategic leadership for social media
    • Leading SMMP procurement efforts
    • Providing process integration
    • Governing social media initiatives
    • Ensuring open communications between departments with ownership of social media processes
  • Keep the completed charter on file and available to all committee members. Remember to periodically update the document as organizational priorities shift to ensure the charter remains relevant.

INFO-TECH DELIVERABLE

Sample of the Social Media Steering Committee Charter Template.

Integrate your social media management platform with CRM to strengthen the realization of social media goals

  • Linking social media to existing customer relationship management solutions can improve information accuracy, reduce manual effort and provide more in-depth customer insights.
    • Organizations Info-Tech surveyed, and who integrated their solutions, achieved more goals as a result.
  • Several major CRM vendors are now offering products that integrate with popular social networking services (either natively or by providing support for third-party add-ons).
    • For example, Salesforce.com now allows for native integration with Twitter, while an add-on available for Oracle gathers real-time information about prospects by pulling their extended information from publicly available LinkedIn profiles.
  • Some CRM vendors are acquiring established SMMPs outright.
    • For example, Salesforce.com acquired Radian6 for their clients that have advanced social media requirements.
Bar chart comparing the social media goal realization of organizations that integrated their SMMP and CRM technology and those that didn't.

Info-Tech Best Practice

CRM vendors still lag in out-of-the-box social features, making a separate SMMP purchase a given. For companies that have not formally integrated social media with CRM, IT should develop the business case in conjunction with the applicable business-side partner (e.g. Marketing, Sales, Service, PR, etc.).

Establish points of integration between SMMPs and CRM suites to gain a 360 degree view of the customer

  • Social media is a valuable tool from a standalone perspective, but its power is considerably magnified when it’s paired with the CRM suite.
  • Many SMMPs offer native integration with CRM platforms. IT should identify and enable these connectors to strengthen the business value of the platform.
  • An illustrated example of how an SMMP linked via CRM can provide proactive service while contributing to sales and marketing.
    An example of how an SMMP linked via CRM can provide proactive service while contributing to sales and marketing.
  • New channels do not mean they stand alone and do not need to be integrated into the rest of the customer interaction architecture.
  • Challenge SMMP vendors to demonstrate integration experience with CRM vendors and multimedia queue vendors.
  • Manual integration – adding resolved social inquiries yourself to a CRM system after closure – cannot scale given the rapid increase in customer inquiries originating in the social cloud. Integration with interaction management workflows is most desirable.

These tools are enabling sales, and they help us serve our customers better. And anything that does that, is a good investment on our part.” Chip Meyers, (Sales Operation Manager, Insource)

Info-Tech Best Practice

SMMPs are a necessary single-channel evolutionary step, just like there used to be email-only and web chat-only customer service options in the late 1990s. But they are temporary. SMMPs will eventually be subsumed into the larger marketing automation ecosystem. Only a few best of breed will survive in 10 years.

Specify the data linkages you will need between your CRM platform and SMMP

Associated Activity icon 3.1.2 1 hour

INPUT: SMMP data sources

OUTPUT: SMMP data migration inventory

MATERIALS: Whiteboard, Markers

PARTICIPANTS: Project Manager, Core project team

  1. Build a list of sources of information that you’ll need to integrate with your CRM tool.
  2. Identify:
    1. Data Source
    2. Integration Direction
    3. Data Type and Use Case
Data Source Migration/Integration Direction Data Type/Use Case
Social Platform Bidirectional Recent Social Posts
Customer Data Warehouse Bidirectional Contact Information, Cases, Tasks, Opportunities

Establish a plan for ongoing platform maintenance

  • Like other enterprise applications, the SMMP will require periodic upkeep. IT must develop and codify policies around ongoing platform maintenance.
  • Platform maintenance should touch on the following areas:
    • Account access and controls – periodically, access privileges for employees no longer with the organization should be purged.
    • Platform security – cloud-based platforms will be automatically updated by the vendor to plug security holes, but on-premises solutions must be periodically updated to ensure that there are no gaps in security.
    • Pruning of old or outdated material – pages (e.g. Facebook Groups, Events, and Twitter feeds) that are no longer in use should be pruned. For example, a management console for an event that was held two years ago is unnecessary. Remove it from the platform (and the relevant service) to cut down on clutter (and reduce costs for “per-topic” priced platforms.)
SMMP being fixed by a wrench.

IT: SMMP Maintenance Checklist

  • Account upkeep and pruning
  • Security, privacy, and access
  • Content upkeep and pruning

Info-Tech Best Practice

Even cloud-based platforms like SMMPs require a certain degree of maintenance around account controls, security, and content pruning. IT should assist the business units in carrying out periodic maintenance.

Social media is a powerful medium, but organizations must develop a prudent strategy for minimizing associated risks

Using an SMMP can help mitigate many of the risks associated with social media. Review the risk categories on the next several slides to determine which ones can be mitigated by effective utilization of a dedicated SMMP.

Risk Category Likelihood Risk(s) Suggested Mitigation Strategy
Privacy and Confidentiality High
  • Risk of inappropriate exchange of information between personal and business social networks (e.g. a personal account used for company business).
  • Abuse of privacy and confidentiality laws.
  • Whenever possible, implement separate social network accounts for business, and train your employees to avoid using personal accounts at work.
  • Have a policy in place for how to treat pre-existing accounts versus newly created ones for enterprise use.
  • Use the “unified sign-on” capabilities of an SMMP to prevent employees from directly accessing the underlying social media services.

Good governance means being proactive in mitigating the legal and compliance risks of your social media program

Risk Category Likelihood Risk(s) Suggested Mitigation Strategy
Trademark and Intellectual Property Medium
  • Copyrighted information could inappropriately be used for promotional and other business purposes (e.g. using a private user’s images in collateral).
  • Legal should conduct training to make sure the organization’s social media representatives only use information in the public domain, nothing privileged or confidential. This is particularly sensitive for Marketing and PR.
Control over Brand Image and Inappropriate Content Medium
  • Employees on social media channels may post something inappropriate to the nature of your business.
  • Employees can post something that compromises industry and/or ethical standards.
  • Use SMMP outbound filtering/post approval workflows to censor certain inappropriate keywords.
  • Select the team carefully and ensure they are fully trained on both official company policy and social media etiquette.
  • Ensure strong enforcement of Social Media AUPs: take a zero tolerance approach to flagrant abuses.

Security is a top-of-mind risk, though bandwidth is a low priority issue for most organizations

Risk Category Likelihood Risk(s) Suggested Mitigation Strategy
IT Security Medium Risk of employees downloading or being sent malware through social media services. Your clients are also exposed to this risk; this may undermine their trust of your brand.
  • Implement policies that outline appropriate precautions by employees, such as using effective passwords and not downloading unauthorized software.
  • Use web-filtering and anti-malware software that incorporates social media as a threat vector.
Bandwidth Low Increase in bandwidth needs to support social media efforts, particularly when using video social media such as YouTube.
  • Plan for any bandwidth requirements with IT network staff.
  • Most social media strategies shouldn’t have a material impact on bandwidth.

Poaching of client lists and increased costs are unlikely to occur, but address as a worst case scenario

Risk Category Likelihood Risk(s) Suggested Mitigation Strategy
Competitors Poaching Client Lists Low The ability for a competitor to view lists of clients that have joined your organization’s social media groups.
  • In a public social network, you cannot prevent this. Monitor your own brand as well as competitors’. If client secrecy must be maintained, then you should use a private social network (e.g. Jive, Lithium, private SharePoint site), not a public network.
Increased Cost of Servicing Customers Low Additional resources may be allocated to social media without seeing immediate ROI.
  • Augment existing customer service responsibilities with social media requests.
  • If a dedicated resource is not available, dedicate a specific amount of time per employee to be spent addressing customer concerns via social media.

Determine your top social media risks and develop an appropriate mitigation strategy that incorporates an SMMP

Associated Activity icon 3.1.3 20 minutes

INPUT: Risk assessment inventory

OUTPUT: Top social media risks and mitigation plan

MATERIALS: Whiteboard, Markers

PARTICIPANTS: Project Manager, Core project team

  1. Based on your unique business variables, which social media risk categories are most applicable to your organization? In what order?
  2. Summarize the top risks below and identify mitigation steps (which often involve effective use of a dedicated SMMP).
Rank Risk Category Mitigation Steps
High Confidentiality We have strong records retention requirements, so using a rules-based SMMP like SocialVolt is a must.
Medium Brand Image Ensure that only personnel who have undergone mandatory training can touch our social accounts via an SMMP.
Low Competitors’ Poaching Lists Migrate our Business Services division contacts onto LinkedIn – maintain no Facebook presence for these clients.

Determine the workflows that will be supported using your social media management platform

Determine when, where, and how social media services should be used to augment existing workflows across (and between) the business process domains. Establish escalation rules and decide whether workflows will be reactive or proactively.

  • Fine tune your efforts in each business process domain by matching social technologies to specific business workflows. This will clearly delineate where value is created by leveraging social media.
  • Common business process domains that should be targeted include marketing, sales, and customer service. Public relations, human resources, and analyst relations are other areas to consider for social process support.
  • For each business process domain, IT should assist with technology enablement and execution.
Target domains: 'Marketing', 'Sales', 'Customer Service', 'Public Relations', 'Human Resources'.

Info-Tech Best Practice

The social media governance team should have high-level supervision of process workflows. Ask to see reports from line managers on what steps they have taken to put process in place for reactive and proactive customer interactions, as well as escalations and channel switching. IT helps orchestrate these processes through knowledge and expertise with SMMP workflow capability.

There are three primary models for SMMP deployment: the agency model uses the SMMP as a third-party offering

There are three models for deploying an SMMP: agency, centralized, and distributed.

Agency Model
Visual of the Agency Model with the 'Social Cloud' attached to the 'SMMP' attached to the 'Agency (e.g. marketing or public relations agency)' attached to the 'Client Organization (Marketing, Sales, Service)'
  • In the agency model of SMMP deployment, the platform is managed on behalf of the organization by a third party – typically a marketing or public relations agency.
  • The agency serves as the primary touch point for the client organization: the client requests the types of market research it wants done, or the campaigns it wants managed. The agency uses its own SMMP(s) to execute the requests. Often, the SMMP’s results or dashboards will be rebranded by the agency.
  • Pros: The agency model is useful when large portions of marketing, service, or public relations are already being outsourced to a third-party provider. Going with an agency also splits the cost of more expensive SMMPs over multiple clients, and limits deployment costs.
  • Cons: The client organization has no direct control over the platform; going with an agency is not cost effective for firms with in-house marketing or PR capabilities.
  • Advice: Go with an agency-managed SMMP if you already use an agency for marketing or PR.

Select the centralized deployment model when SMMP functionality rests in the hands of a single department

Centralized Model
Visual of the Centralized Model with the 'Social Cloud' attached to the 'SMMP' attached to 'Marketing' attached to the 'Sales' and 'Service'
In this example, marketing owns and manages a single SMMP
  • In the centralized model, a single SMMP workspace is owned and operated predominantly by a single business unit or department. Unlike the agency model, the SMMP functionality is utilized in-house.
  • Information from the SMMP may occasionally be shared with other departments, but normally the platform is used almost exclusively by a single group in the company. Marketing or public relations are usually the groups that maintain ownership of the SMMP in the centralized model (with selection and deployment assistance from the IT department).
  • Pros: The centralized model provides small organizations with an in-house, dedicated SMMP without having to go through an agency. Having a single group own and manage the SMMP is considerably more cost effective than having SMMPs licensed to multiple business units in a small company.
  • Cons: If more and more departments start clamoring for control of SMMP resources, the centralized model will fail to meet the overall needs of the organization.
  • Advice: Small-to-medium enterprises with mid-sized topic or brand portfolios should use the centralized model.

Go with a distributed deployment if multiple business units require advanced SMMP functionality

Distributed Model
Visual of the Distributed Model with the 'Social Cloud' attached to two 'SMMPs', one attached to 'Marketing' and 'Sales', the other to 'Customer Service' and 'Public Relations'.
  • In the distributed model, multiple SMMPs (sometimes from different vendors) or multiple SMMP workspaces (from a single vendor) are deployed to several groups (e.g. multiple departments or brand portfolios) in the organization.
  • Pros: The distributed model is highly effective in large organizations with multiple departments or brands that each are interested in SMMP functionality. Having separate workspaces for each business group enables customizing workspaces to satisfy different goals of the different business groups.
  • Cons: The cost of deploying multiple SMMP workspaces can be prohibitive.
  • Advice: Go with the distributed model if your organization is large and has multiple relevant departments or product marketing groups, with differing social media goals.

Determine which deployment model works best for your organization

Associated Activity icon 3.1.4 1 Hour

INPUT: Deployment models

OUTPUT: Best fit deployment model

MATERIALS: Whiteboard, Markers

PARTICIPANTS: Project Manager, Core project team

  1. Assess and understand the three models of SMMP deployments: agency, centralized and distributed. Consider the pros and cons of each model.
  2. Understand how your organization manages enterprise social media. Consider the follow questions:
    • What is the size of your organization?
    • Who owns the management of social media in your organization?
    • Is social media managed in-house or outsourced to an agency?
    • What are the number of departments that use and rely on social media?
  3. Select the best deployment model for your organization.
Agency Model Centralized Model Distributed Model
Visual of the Agency Model with the 'Social Cloud' attached to the 'SMMP' attached to the 'Agency (e.g. marketing or public relations agency)' attached to the 'Client Organization (Marketing, Sales, Service)' Visual of the Centralized Model with the 'Social Cloud' attached to the 'SMMP' attached to 'Marketing' attached to the 'Sales' and 'Service' Visual of the Distributed Model with the 'Social Cloud' attached to two 'SMMPs', one attached to 'Marketing' and 'Sales', the other to 'Customer Service' and 'Public Relations'.

Create an SMMP training matrix based on social media roles

IT must assist the business by creating and executing a role-based training program. An SMMP expert in IT should lead training sessions for targeted groups of end users, training them only on the functions they require to perform their jobs.

Use the table below to help identify which roles should be trained on which SMMP features.

PR Professionals Marketing Brand, Product, and Channel Managers Customer Service Reps and Manager Product Development and Market Research IT Application Support
Account Management Circle indicating a positive field. Circle indicating a positive field. Circle indicating a positive field. Circle indicating a positive field. Circle indicating a positive field.
Response and Engagement Circle indicating a positive field. Circle indicating a positive field. Circle indicating a positive field.
Social Analytics and Data Mining Circle indicating a positive field. Circle indicating a positive field. Circle indicating a positive field.
Marketing Campaign Execution Circle indicating a positive field. Circle indicating a positive field.
Mobile Access Circle indicating a positive field. Circle indicating a positive field. Circle indicating a positive field.
Archiving Circle indicating a positive field.
CRM Integration Circle indicating a positive field.

Phase 3, Step 2: Track your metrics

3.1

3.2

Establish best practices for SMMP implementation Assess the measured value from the project

This step will walk you through the following activities:

  • Identify metrics and KPIs for business units using a dedicated SMMP

This step involves the following participants:

  • Core Project Team
  • Representative Stakeholders from Digital Marketing, Sales, and IT

Outcomes of this step

  • Key Performance Indicators

Know key performance indicators (KPIs) for each department that employs a dedicated social media management platform

Share of Voice
How often a brand is mentioned, relative to other brands competing in a defined market.

User Engagement
Quantity and quality of customer interactions with a brand or with each other, either on- or offline.

Campaign Success
Tracking reception of campaigns and leads brought in as a result.
Marketing KPIs Reach
Measurement of the size of market your brand advertisements and communications reach.

Impressions
The number of exposures your content, ad, or social post has to people in your target audience.

Cost per Point (CPP)
Cost to reach one percent of your organization’s audience.

Product Innovation
The quantity and quality of improvements, updates, and changes to existing products.

Time-to-Market
Time that passes between idea generation and the product being available to consumers.

Product Development KPIs

New Product Launches
A ratio of completely new product types released to brand extensions and improvements.

Cancelled Projects
Measure of quality of ideas generated and quality of idea assessment method.

Use social media metrics to complement your existing departmental KPIs – not usurp them

Cost per Lead
The average amount an organization spends to find leads.

Conversion Rate
How many sales are made in relation to the number of leads.

Quantity of Leads
How many sales leads are in the funnel at a given time.
Sales KPIs Average Cycle Time
Average length of time it takes leads to progress through the sales cycle.

Revenue by Lead
Total revenue divided by total number of leads.

Avg. Revenue per Rep
Total revenue divided by number of sales reps.

Time to Resolution
Average amount of time it takes for customers to get a response they are satisfied with.

First Contact Resolution
How often customer issues are resolved on the first contact.

Customer Service KPIs

Contact Frequency
The number of repeated interactions from the same customers.

Satisfaction Scores
Determined from customer feedback – either through surveys or gathered sporadically.

Social analytics don’t operate alone; merge social data with traditional data to gain the deepest insights

Employee Retention
The level of effort an organization exerts to maintain its current staff.

Employee Engagement
Rating of employee satisfaction overall or with a given aspect of the workplace.

Preferred Employer
A company where candidates would rather work over other companies.
Marketing KPIs Recruitment Cycle Time
Average length of time required to recruit a new employee.

Employee Productivity
A comparison of employee inputs (time, effort, etc.) and outputs (work).

Employee Referrals
The ratio of employee referrals that complete the recruitment process.

There are conversations going on behind your back, and if you're not participating in them, then you're either not perpetuating the positive conversation or not diffusing the negative. And that's irresponsible in today's business world.” (Lon Safko, Social Media Bible)

Identify key performance indicators for business units using an SMMP

Associated Activity icon 3.2.1 30 minutes

INPUT: Social media goals

OUTPUT: SMMP KPIs

MATERIALS: Whiteboard, Markers

PARTICIPANTS: Representative stakeholders from different business units

For each listed department, identify the social media goals and departmental key performance indicators to measure the impact of the SMMP.

DepartmentSocial Media GoalsKPI
Marketing
  • E.g. build a positive brand image
  • Net increase in brand recognition
Product Development
  • Launch a viral video campaign showcasing product attributes to drive increased YT traffic
  • Net increase in unaided customer recall
Sales
  • Enhance sales lead generation through social channels
  • Net increase in sales lead generation in the social media sales funnel
Customer Service
  • Produce more timely responses to customer enquiries and complaints
  • Reduced time to resolution
HR
  • Enhance social media recruitment channels
  • Number of LinkedIn recruitment

If you want additional support, have our analysts guide you through this phase as part of an Info-Tech Workshop Associated Activity icon

Book a workshop with our Info-Tech analysts:

Photo of an Info-Tech analyst.
  • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
  • Info-Tech analyst will join you and your team onsite at your location or welcome you to Info-Tech's historic Toronto office to participate in an innovative onsite workshop.
  • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

The following are sample activities that will be conducted by Info-Tech analysts with your team:

3.1.1

Sample of activity 3.1.1 'Establish a governance structure for social media management'. Establish a governance structure for social media management

Our Info-Tech analyst will walk you through the exercise of developing roles and responsibilities to govern your social media program.

3.1.2

Sample of activity 3.1.2 'Specify the data linkages you will need between your CRM platform and SMMP'. Specify the data linkages you will need between your CRM and SMMP

The analyst will help you identify the points of integration between the SMMP and your CRM platform.

If you want additional support, have our analysts guide you through this phase as part of an Info-Tech Workshop Associated Activity icon

Book a workshop with our Info-Tech analysts:

3.1.3

Sample of activity 3.1.3 'Determine your top social media risks and develop an appropriate mitigation strategy that incorporates an SMMP'. Determine your top social media risks

Our Info-Tech analyst will facilitate the discussion to identify the top risks associated with the SMMP and determine mitigation strategies for each risk.

3.1.4

Sample of activity 3.1.4 'Determine which deployment model works best for your organization'. Determine the best-fit deployment model

An analyst will demonstrate the different SMMP deployment models and assist in determining the most suitable model for your organization.

3.2.1

Sample of activity 3.2.1 'Identify key performance indicators for business units using an SMMP'. Identify departmental KPIs

An analyst will work with different stakeholders to determine the top social media goals for each department.

Appendices

Works Cited

Ashja, Mojtaba, Akram Hadizadeh, and Hamid Bidram. “Comparative Study of Large Information Systems’ CSFs During Their Life Cycle.” Information Systems Frontiers. September 8, 2013.

UBM. “The State of Social Media Analytics.” January, 2016.

Jobvite. “2015 Recruiter Nation Survey.” September, 2015.

Vendor Landscape Analysis Appendices

Vendor Landscape Methodology:
Overview

Info-Tech’s Vendor Landscapes are research materials that review a particular IT market space, evaluating the strengths and abilities of both the products available in that space, as well as the vendors of those products. These materials are created by a team of dedicated analysts operating under the direction of a senior subject matter expert over a period of several weeks.

Evaluations weigh selected vendors and their products (collectively “solutions”) on the following eight criteria to determine overall standing:

  • Features: The presence of advanced and market-differentiating capabilities.
  • User Interface: The intuitiveness, power, and integrated nature of administrative consoles and client software components.
  • Affordability: The three-year total cost of ownership of the solution; flexibility of the pricing and discounting structure.
  • Architecture: The degree of integration with the vendor’s other tools, flexibility of deployment, and breadth of platform applicability.
  • Viability: The stability of the company as measured by its history in the market, the size of its client base, and its percentage of growth.
  • Focus: The commitment to both the market space, as well as to the various sized clients (small, mid-sized, and enterprise clients).
  • Reach: The ability of the vendor to support its products on a global scale.
  • Sales: The structure of the sales process and the measure of the size of the vendor’s channel and industry partners.

Evaluated solutions within scenarios are visually represented by a Pathway to Success, based off a linear graph using above scoring methods:

  • Use-case scenarios are decided upon based on analyst expertise and experience with Info-Tech clients.
  • Use-case scenarios are defined through feature requirements, predetermined by analyst expertise.
  • Placement within scenario rankings consists of features being evaluated against the other scoring criteria.

Info-Tech’s Vendor Landscapes are researched and produced according to a strictly adhered to process that includes the following steps:

  • Vendor/product selection
  • Information gathering
  • Vendor/product scoring
  • Information presentation
  • Fact checking
  • Publication

This document outlines how each of these steps is conducted.

Vendor Landscape Methodology:
Vendor/Product Selection & Information Gathering

Info-Tech works closely with its client base to solicit guidance in terms of understanding the vendors with whom clients wish to work and the products that they wish evaluated; this demand pool forms the basis of the vendor selection process for Vendor Landscapes. Balancing this demand, Info-Tech also relies upon the deep subject matter expertise and market awareness of its Senior Analysts to ensure that appropriate solutions are included in the evaluation. As an aspect of that expertise and awareness, Info-Tech’s analysts may, at their discretion, determine the specific capabilities that are required of the products under evaluation, and include in the Vendor Landscape only those solutions that meet all specified requirements.

Information on vendors and products is gathered in a number of ways via a number of channels.

Initially, a request package is submitted to vendors to solicit information on a broad range of topics. The request package includes:

  • A detailed survey.
  • A pricing scenario (see Vendor Landscape Methodology: Price Evaluation and Pricing Scenario, below).
  • A request for reference clients.
  • A request for a briefing and, where applicable, guided product demonstration.

These request packages are distributed approximately eight weeks prior to the initiation of the actual research project to allow vendors ample time to consolidate the required information and schedule appropriate resources.

During the course of the research project, briefings and demonstrations are scheduled (generally for one hour each session, though more time is scheduled as required) to allow the analyst team to discuss the information provided in the survey, validate vendor claims, and gain direct exposure to the evaluated products. Additionally, an end-user survey is circulated to Info-Tech’s client base and vendor-supplied reference accounts are interviewed to solicit their feedback on their experiences with the evaluated solutions and with the vendors of those solutions.

These materials are supplemented by a thorough review of all product briefs, technical manuals, and publicly available marketing materials about the product, as well as about the vendor itself.

Refusal by a vendor to supply completed surveys or submit to participation in briefings and demonstrations does not eliminate a vendor from inclusion in the evaluation. Where analyst and client input has determined that a vendor belongs in a particular evaluation, it will be evaluated as best as possible based on publicly available materials only. As these materials are not as comprehensive as a survey, briefing, and demonstration, the possibility exists that the evaluation may not be as thorough or accurate. Since Info-Tech includes vendors regardless of vendor participation, it is always in the vendor’s best interest to participate fully.

All information is recorded and catalogued, as required, to facilitate scoring and for future reference.

Vendor Landscape Methodology:
Scoring

Once all information has been gathered and evaluated for all vendors and products, the analyst team moves to scoring. All scoring is performed at the same time so as to ensure as much consistency as possible. Each criterion is scored on a ten-point scale, though the manner of scoring for criteria differs slightly:

  • Features is scored via Cumulative Scoring.
  • Affordability is scored via Scalar Scoring.
  • All other criteria are scored via Base5 Scoring.

Cumulative Scoring is on a four-point scale. Zero points are awarded to features that are deemed absent or unsatisfactory, one point is assigned to features that are partially present, two points are assigned to features that require an extra purchase in the vendor’s product portfolio or through a third party, three points are assigned to features that are fully present and native to the solution, and four points are assigned to the best-of-breed native feature. The assigned points are summed and normalized to a value out of ten. For example, if a particular Vendor Landscape evaluates eight specific features in the Feature Criteria, the summed score out of eight for each evaluated product would be multiplied by 1.25 to yield a value out of ten to represent in a Harvey Ball format.

In Scalar Scoring, a score of ten is assigned to the lowest cost solution, and a score of one is assigned to the highest cost solution. All other solutions are assigned a mathematically-determined score based on their proximity to / distance from these two endpoints. For example, in an evaluation of three solutions, where the middle cost solution is closer to the low end of the pricing scale it will receive a higher score, and where it is closer to the high end of the pricing scale it will receive a lower score; depending on proximity to the high or low price it is entirely possible that it could receive either ten points (if it is very close to the lowest price) or one point (if it is very close to the highest price). Where pricing cannot be determined (vendor does not supply price and public sources do not exist), a score of 0 is automatically assigned.

In Base5 scoring a number of sub-criteria are specified for each criterion (for example, Longevity, Market Presence, and Financials are sub-criteria of the Viability criterion), and each one is scored on the following scale:

  • 5 - The product/vendor is exemplary in this area (nothing could be done to improve the status).
  • 4 - The product/vendor is good in this area (small changes could be made that would move things to the next level).
  • 3 - The product/vendor is adequate in this area (small changes would make it good, more significant changes required to be exemplary).
  • 2 - The product/vendor is poor in this area (this is a notable weakness and significant work is required).
  • 1 - The product/vendor fails in this area (this is a glaring oversight and a serious impediment to adoption).

The assigned points are summed and normalized to a value out of ten as explained in Cumulative Scoring above.

Scores out of ten, known as Raw scores, are transposed as is into Info-Tech’s Vendor Landscape Shortlist Tool, which automatically determines Vendor Landscape positioning (see Vendor Landscape Methodology: Information Presentation – Vendor Landscape, below), Criteria Score (see Vendor Landscape Methodology: Information Presentation – Criteria Score, below), and Value Index (see Vendor Landscape Methodology: Information Presentation – Value Index, below).

Vendor Landscape Methodology:
Information Presentation – Criteria Scores (Harvey Balls)

Info-Tech’s criteria scores are visual representations of the absolute score assigned to each individual criterion, as well as of the calculated overall vendor and product scores. The visual representation used is Harvey Balls.

Harvey Balls are calculated as follows:

  1. Raw scores are transposed into the Info-Tech Vendor Landscape Shortlist Tool (for information on how raw scores are determined, see Vendor Landscape Methodology: Scoring, above).
  2. Each individual criterion raw score is multiplied by a pre-assigned weighting factor for the Vendor Landscape in question. Weighting factors are determined prior to the evaluation process, based on the expertise of the Senior or Lead Research Analyst, to eliminate any possibility of bias. Weighting factors are expressed as a percentage, such that the sum of the weighting factors for the vendor criteria (Viability, Strategy, Reach, Channel) is 100%, and the sum of the product criteria (Features, Usability, Affordability, Architecture) is 100%.
  3. A sum-product of the weighted vendor criteria scores and of the weighted product criteria scores is calculated to yield an overall vendor score and an overall product score.
  4. Both overall vendor score / overall product score, as well as individual criterion raw scores are converted from a scale of one to ten to Harvey Ball scores on a scale of zero to four, where exceptional performance results in a score of four and poor performance results in a score of zero.
  5. Harvey Ball scores are converted to Harvey Balls as follows:
    • A score of four becomes a full Harvey Ball.
    • A score of three becomes a three-quarter full Harvey Ball.
    • A score of two becomes a half-full Harvey Ball.
    • A score of one becomes a one-quarter full Harvey Ball.
    • A score of zero becomes an empty Harvey Ball.
  6. Harvey Balls are plotted by solution in a chart where rows represent individual solutions and columns represent overall vendor / overall product, as well as individual criteria. Solutions are ordered in the chart alphabetically by vendor name.
Harvey Balls
Overall Harvey Balls represent weighted aggregates. Example of Harvey Balls with 'Overall' balls at the beginning of each category followed by 'Criteria' balls for individual raw scores. Criteria Harvey Balls represent individual raw scores.

Vendor Landscape Methodology:
Use-Case Scoring

Within each Vendor Landscape a set of use-case scenarios are created by the analysts by considering the different outcomes and purposes related to the technology being evaluated. To generate the custom use-case vendor performances, the feature and Harvey Ball scoring performed in the Vendor Landscapes are set with custom weighting configurations.

Calculations

Each product has a vendor multiplier calculated based on its weighted performance, considering the different criteria scored in the Harvey Ball evaluations.

To calculate each vendor’s performance, the advanced feature scores are multiplied against the weighting for the feature in the use-case scenario’s configuration.

The weighted advanced feature score is then multiplied against the vendor multiplier.

The sum of each vendor’s total weighted advanced features is calculated. This sum is used to identify the vendor’s qualification and relative rank within the use case.

Example pie charts.

Each use case’s feature weightings and vendor/product weighting configurations are displayed within the body of slide deck.

Use-Case Vendor Performance

Example stacked bar chart of use-case vendor performance.

Vendors who qualified for each use-case scenario are ranked from first to last in a weighted bar graph based on the features considered.

Vendor Landscape Methodology:
Information Presentation – Feature Ranks (Stoplights)

Advanced features are determined by analyst expertise, leveraging information gained from conversations with clients. Advanced features chosen as part of the evaluation are representative of what Info-Tech clients have indicated are of importance to their vendor solution. Advanced features are evaluated through a series of partial marks, dedicated to whether the solution performs all aspects of the Info-Tech definition of the feature and whether the feature is provided within the solution. Analysts hold the right to determine individual, unique scoring criteria for each evaluation. If a feature does not meet the criteria, Info-Tech holds the right to score the feature accordingly.

Use cases use features as a baseline of the inclusion and scoring criteria.

'Stoplight Legend' with green+star 'Feature category is present: best in class', green 'Feature category is present: strong', yellow 'Feature category is present: average', orange 'Feature category is partially present: weak', and red 'Feature category is absent or near-absent'.

Vendor Landscape Methodology:
Information Presentation – Value Index

Info-Tech’s Value Index is an indexed ranking of solution value per dollar as determined by the raw scores assigned to each criteria (for information on how raw scores are determined, see Vendor Landscape Methodology: Scoring, above).

Value scores are calculated as follows:

  1. The TCO Affordability criterion is removed from the Affordability score and the remaining product score criteria (Features, Usability, Architecture). Affordability scoring is adjusted with the TCO weighting distributed in proportion to the use case’s weighting for Affordability. Weighting is adjusted as to retain the same weightings relative to one another, while still summing to 100%.
  2. An adjusted multiplier is determined for each vendor using the recalculated Affordability scoring.
  3. The multiplier vendor score and vendor’s weighted feature score (based on the use-case scenario’s weightings), are summed. This sum is multiplied by the TCO raw score to yield an interim Value Score for each solution.
  4. All interim Value Scores are then indexed to the highest performing solution by dividing each interim Value Score by the highest interim Value Score. This results in a Value Score of 100 for the top solution and an indexed Value Score relative to the 100 for each alternate solution.
  5. Solutions are plotted according to Value Score, with the highest score plotted first, and all remaining scores plotted in descending numerical order.

Where pricing is not provided by the vendor and public sources of information cannot be found, an Affordability raw score of zero is assigned. Since multiplication by zero results in a product of zero, those solutions for which pricing cannot be determined receive a Value Score of zero. Since Info-Tech assigns a score of zero where pricing is not available, it is always in the vendor’s best interest to provide accurate and up-to-date pricing. In the event that insufficient pricing is available to accurately calculate a Value Index, Info-Tech will omit it from the Vendor Landscape.

Value Index

Vendors are arranged in order of Value Score. The Value Score each solution achieved is displayed, and so is the average score.

Example bar chart indicating the 'Value Score' vs the 'Average Score'.

Those solutions that are ranked as Champions are differentiated for point of reference.

Vendor Landscape Methodology:
Information Presentation – Price Evaluation: Mid-Market

Info-Tech’s Price Evaluation is a tiered representation of the three-year Total Cost of Ownership (TCO) of a proposed solution. Info-Tech uses this method of communicating pricing information to provide high-level budgetary guidance to its end-user clients while respecting the privacy of the vendors with whom it works. The solution TCO is calculated and then represented as belonging to one of ten pricing tiers.

Pricing tiers are as follows:

  1. Between $1 and $2,500
  2. Between $2,500 and $10,000
  3. Between $10,000 and $25,000
  4. Between $25,000 and $50,000
  5. Between $50,000 and $100,000
  6. Between $100,000 and $250,000
  7. Between $250,000 and $500,000
  8. Between $500,000 and $1,000,000
  9. Between $1,000,000 and $2,500,000
  10. Greater than $2,500,000

Where pricing is not provided, Info-Tech makes use of publicly available sources of information to determine a price. As these sources are not official price lists, the possibility exists that they may be inaccurate or outdated, and so the source of the pricing information is provided. Since Info-Tech publishes pricing information regardless of vendor participation, it is always in the vendor’s best interest to supply accurate and up to date information.

Info-Tech’s Price Evaluations are based on pre-defined pricing scenarios (see Product Pricing Scenario, below) to ensure a comparison that is as close as possible between evaluated solutions. Pricing scenarios describe a sample business and solicit guidance as to the appropriate product/service mix required to deliver the specified functionality, the list price for those tools/services, as well as three full years of maintenance and support.

Price Evaluation

Call-out bubble indicates within which price tier the three-year TCO for the solution falls, provides the brackets of that price tier, and links to the graphical representation.

Example price evaluation with a '3 year TCO...' statement, a visual gauge of bars, and a statement on the source of the information.

Scale along the bottom indicates that the graphic as a whole represents a price scale with a range of $1 to $2.5M+, while the notation indicates whether the pricing was supplied by the vendor or derived from public sources.

Vendor Landscape Methodology:
Information Presentation – Vendor Awards

At the conclusion of all analyses, Info-Tech presents awards to exceptional solutions in three distinct categories. Award presentation is discretionary; not all awards are extended subsequent to each Vendor Landscape and it is entirely possible, though unlikely, that no awards may be presented.

Awards categories are as follows:

  • Champion Awards are presented to the top performing solution in a particular use-case scenario. As a result, only one Champion Award is given for each use case, and the entire Vendor Landscape will have the same number of Champion Awards as the number of evaluated use cases.
  • Leader Awards are presented to top performing solutions for each use-case scenario. Depending on the use-case scenario and the number of solutions being evaluated, a variable number of leader awards will be given. This number is at the discretion of the analysts, but is generally placed at two, and given to the solutions ranking second and third respectively for the use case.
  • Best Overall Value Awards are presented to the solution for each use-case scenario that ranked the highest in the Info-Tech Value Index for each evaluated scenario (see Vendor Landscape Methodology: Information Presentation – Value Index, above). If insufficient pricing information is made available for the evaluated solutions, such that a Value Index cannot be calculated, no Best Overall Value Award will be presented. Only one Best Overall Value Award is available for each use-case scenario.

Vendor Awards for Use-Case Performance

Vendor Award: 'Champion'. Info-Tech’s Champion Award is presented to solutions that placed first in an use-case scenario within the Vendor Landscape.
Vendor Award: 'Leader'. Info-Tech Leader Award is given to solutions who placed in the top segment of a use-case scenario.
Vendor Award: 'Best Overall Value'. Info-Tech’s Best Overall Value Award is presented to the solution within each use-case scenario with the highest Value Index score.

Vendor Landscape Methodology:
Fact Check & Publication

Info-Tech takes the factual accuracy of its Vendor Landscapes, and indeed of all of its published content, very seriously. To ensure the utmost accuracy in its Vendor Landscapes, we invite all vendors of evaluated solutions (whether the vendor elected to provide a survey and/or participate in a briefing or not) to participate in a process of fact check.

Once the research project is complete and the materials are deemed to be in a publication ready state, excerpts of the material specific to each vendor’s solution are provided to the vendor. Info-Tech only provides material specific to the individual vendor’s solution for review encompassing the following:

  • All written review materials of the vendor and the vendor’s product that comprise the evaluated solution.
  • Info-Tech’s Criteria Scores / Harvey Balls detailing the individual and overall vendor / product scores assigned.
  • Info-Tech’s Feature Rank / stoplights detailing the individual feature scores of the evaluated product.
  • Info-Tech’s Raw Pricing for the vendor either as received from the vendor or as collected from publicly available sources.
  • Info-Tech’s Scenario ranking for all considered scenarios for the evaluated solution.

Info-Tech does not provide the following:

  • Info-Tech’s Vendor Landscape placement of the evaluated solution.
  • Info-Tech’s Value Score for the evaluated solution.
  • End-user feedback gathered during the research project.
  • Info-Tech’s overall recommendation in regard to the evaluated solution.

Info-Tech provides a one-week window for each vendor to provide written feedback. Feedback must be corroborated (be provided with supporting evidence), and where it does, feedback that addresses factual errors or omissions is adopted fully, while feedback that addresses opinions is taken under consideration. The assigned analyst team makes all appropriate edits and supplies an edited copy of the materials to the vendor within one week for final review.

Should a vendor still have concerns or objections at that time, they are invited to a conversation, initially via email, but as required and deemed appropriate by Info-Tech, subsequently via telephone, to ensure common understanding of the concerns. Where concerns relate to ongoing factual errors or omissions, they are corrected under the supervision of Info-Tech’s Vendor Relations personnel. Where concerns relate to ongoing differences of opinion, they are again taken under consideration with neither explicit not implicit indication of adoption.

Publication of materials is scheduled to occur within the six weeks following the completion of the research project, but does not occur until the fact check process has come to conclusion, and under no circumstances are “pre-publication” copies of any materials made available to any client.

Pricing Scenario

Info-Tech Research Group is providing each vendor with a common pricing scenario to enable normalized scoring of Affordability, calculation of Value Index rankings, and identification of the appropriate solution pricing tier as displayed on each vendor scorecard.

Vendors are asked to provide list costs for SMMP software licensing to address the needs of a reference organization described in the pricing scenario. Please price out the lowest possible 3-year total cost of ownership (TCO) including list prices for software and licensing fees to meet the requirements of the following scenario.

Three-year total acquisition costs will be normalized to produce the Affordability raw scores and calculate Value Index ratings for each solution.

The pricing scenario:

  • Enterprise Name: Imperial Products Incorporated
  • Enterprise Size: SMB
  • Enterprise Vertical: Consumer packaged goods
  • Total Number of Sites: Three office locations
  • Total Number of Employees: 500
  • Total Number SMMP End Users: 50
    • 20 dedicated CSRs who are handling all customer service issues routed to them
    • 5 PR managers who need the ability to monitor the social cloud
    • 24 brand portfolio managers – each portfolio has 5 products (25 total)
    • Each product has its own Facebook and Twitter presence
    • 1 HR manager (using social media for recruiting)
  • Total Number of IT Staff: 20
  • Operating System Environment: Windows 7
  • Functional Requirements and Additional Information: Imperial Products Incorporated is a mid-sized consumer packaged goods firm operating in the United States. The organization is currently looking to adopt a platform for social media monitoring and management. Functional requirements include the ability to monitor and publish to Facebook, Twitter, YouTube, and blogs. The platform must have the ability to display volume trends, show follower demographics, and conduct sentiment analysis. It must also provide tools for interacting in-platform with social contacts, provide workflow management capabilities, and offer the ability to manage specific social properties (e.g. Facebook Pages). Additional features that are desirable are the ability to archive social interactions, and a dedicated mobile application for one of the major smartphone/tablet operating systems (iOS, Android etc.).

Become a Strategic CIO

  • Buy Link or Shortcode: {j2store}80|cart{/j2store}
  • member rating overall impact: 9.5/10 Overall Impact
  • member rating average dollars saved: $10,000 Average $ Saved
  • member rating average days saved: 15 Average Days Saved
  • Parent Category Name: IT Strategy
  • Parent Category Link: /it-strategy
  • As a CIO, you are currently operating in a stable and trusted IT environment, but you would like to advance your role to strategic business partner.
  • CIOs are often overlooked as a strategic partner by their peers, and therefore face the challenge of proving they deserve a seat at the table.

Our Advice

Critical Insight

  • To become a strategic business partner, you must think and act as a business person that works in IT, rather than an IT person that works for the business.
  • Career advancement is not a solo effort. Building relationships with your executive business stakeholders will be critical to becoming a respected business partner.

Impact and Result

  • Create a personal development plan and stakeholder management strategy to accelerate your career and become a strategic business partner. For a CIO to be considered a strategic business partner, he or she must be able to:
    • Act as a business person that works in IT, rather than an IT person that works for the business. This involves meeting executive stakeholder expectations, facilitating innovation, and managing stakeholder relationships.
    • Align IT with the customer. This involves providing business stakeholders with information to support stronger decision making, keeping up with disruptive technologies, and constantly adapting to the ever-changing end-customer needs.
    • Manage talent and change. This involves performing strategic workforce planning, and being actively engaged in identifying opportunities to introduce change in your organization, suggesting ways to improve, and then acting on them.

Become a Strategic CIO Research & Tools

Start here – read the Executive Brief

Read our concise Executive Brief to find out why you should become a strategic CIO, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

Besides the small introduction, subscribers and consulting clients within this management domain have access to:

1. Launch

Analyze strategic CIO competencies and assess business stakeholder satisfaction with IT using Info-Tech's CIO Business Vision Diagnostic and CXO-CIO Alignment Program.

  • Become a Strategic CIO – Phase 1: Launch

2. Assess

Evaluate strategic CIO competencies and business stakeholder relationships.

  • Become a Strategic CIO – Phase 2: Assess
  • CIO Strategic Competency Evaluation Tool
  • CIO Stakeholder Power Map Template

3. Plan

Create a personal development plan and stakeholder management strategy.

  • Become a Strategic CIO – Phase 3: Plan
  • CIO Personal Development Plan
  • CIO Stakeholder Management Strategy Template

4. Execute

Develop a scorecard to track personal development initiatives.

  • Become a Strategic CIO – Phase 4: Execute
  • CIO Strategic Competency Scorecard
[infographic]

Workshop: Become a Strategic CIO

Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

1 Assess Competencies & Stakeholder Relationships

The Purpose

Gather and review information from business stakeholders.

Assess strategic CIO competencies and business stakeholder relationships.

Key Benefits Achieved

Gathered information to create a personal development plan and stakeholder management strategy.

Analyzed the information from diagnostics and determined the appropriate next steps.

Identified and prioritized strategic CIO competency gaps.

Evaluated the power, impact, and support of key business stakeholders.

Activities

1.1 Conduct CIO Business Vision diagnostic

1.2 Conduct CXO-CIO Alignment program

1.3 Assess CIO competencies

1.4 Assess business stakeholder relationships

Outputs

CIO Business Vision results

CXO-CIO Alignment Program results

CIO competency gaps

Executive Stakeholder Power Map

2 Take Control of Your Personal Development

The Purpose

Create a personal development plan and stakeholder management strategy.

Track your personal development and establish checkpoints to revise initiatives.

Key Benefits Achieved

Identified personal development and stakeholder engagement initiatives to bridge high priority competency gaps.

Identified key performance indicators and benchmarks/targets to track competency development.

Activities

2.1 Create a personal development plan

2.2 Create a stakeholder management strategy

2.3 Establish key performance indicators and benchmarks/targets

Outputs

Personal Development Plan

Stakeholder Management Strategy

Strategic CIO Competency Scorecard

Asset Management

  • Buy Link or Shortcode: {j2store}1|cart{/j2store}
  • Related Products: {j2store}1|crosssells{/j2store}
  • Up-Sell: {j2store}1|upsells{/j2store}
  • Download01-Title: Asset Management Executive Brief
  • Download-01: Visit Link
  • member rating overall impact: 9.1/10
  • member rating average dollars saved: $16,518
  • member rating average days saved: 19
  • Parent Category Name: Infra and Operations
  • Parent Category Link: /infra-and-operations
Asset management has a clear impact on the financials of your company. Clear insights are essential to keep your spending at the right level.

Asset Management

Exploit Disruptive Infrastructure Technology

  • Buy Link or Shortcode: {j2store}298|cart{/j2store}
  • member rating overall impact: N/A
  • member rating average dollars saved: N/A
  • member rating average days saved: N/A
  • Parent Category Name: Disruptive & Emerging Technologies
  • Parent Category Link: /disruptive-emerging-technologies
  • New technology can hit like a meteor. Not only disruptive to IT, technology provides opportunities for organization-wide advantage.
  • Your role is endangered. If you don’t prepare for the most disruptive technologies, you could be overshadowed. Don’t let the Chief Marketing Officer (CMO) set the technological innovation agenda
  • Predicting the future isn’t easy. Most IT leaders fail to realize how quickly technology increases in capability. Even for the tech savvy, predicting which specific technologies will become disruptive is difficult.
  • Communication is difficult when the sky is falling. Even forward-looking IT leaders struggle with convincing others to devote time and resources to monitoring technologies with a formal process.

Our Advice

Critical Insight

  • Establish the core working group, select a leader, and select a group of visionaries to help brainstorm emerging technologies.
  • Brainstorm about creating a better future, begin brainstorming an initial longlist.
  • Train the group to think like futurists.
  • Evaluate the shortlist.
  • Define your PoC list and schedule.
  • Finalize, present the plan to stakeholders and repeat.

Impact and Result

  • Create a disruptive technology working group.
  • Produce a longlist of disruptive technologies.
  • Evaluate the longlist to produce a shortlist of disruptive technologies.
  • Develop a plan for a proof-of-concept project for each shortlisted technology.

Exploit Disruptive Infrastructure Technology Research & Tools

Besides the small introduction, subscribers and consulting clients within this management domain have access to:

1. Exploit Disruptive Infrastructure Technology – A guide to help IT leaders make the most of disruptive impacts.

As a CIO, there is a need to move beyond day-to-day technology management with an ever-increasing need to forecast technology impacts. Not just from a technical perspective but to map out the technical understandings aligned to potential business impacts and improvements. Technology transformation and innovation is moving more quickly than ever before and as an innovation champion, the CIO or CTO should have foresight in specific technologies with the understanding of how the company could be disrupted in the near future.

  • Exploit Disruptive Infrastructure Technology – Phases 1-3

2. Disruptive Technology Exploitation Plan Template – A guide to develop the plan for exploiting disruptive technology.

The Disruptive Technology Exploitation Plan Template acts as an implementation plan for developing a long-term strategy for monitoring and implementing disruptive technologies.

  • Disruptive Technology Exploitation Plan Template

3. Disruptive Technology Look to the Past Tool – A tool to keep track of the missed technology disruption from previous opportunities.

The Disruptive Technology Look to the Past Tool will assist you to collect reasonability test notes when evaluating potential disruptive technologies.

  • Disruptive Technology Look to the Past Tool

4. Disruptive Technology Research Database Tool – A tool to keep track of the research conducted by members of the working group.

The Disruptive Technology Research Database Tool will help you to keep track of the independent research that is conducted by members of the disruptive technology exploitation working group.

  • Disruptive Technology Research Database Tool

5. Disruptive Technology Shortlisting Tool

The Disruptive Technology Shortlisting Tool will help you to codify the results of the disruptive technology working group's longlist winnowing process.

  • Disruptive Technology Shortlisting Tool

6. Disruptive Technology Value-Readiness and SWOT Analysis Tool – A tool to systematize notional evaluations of the value and readiness of potential disruptive technologies.

The Disruptive Technology Value Readiness & SWOT Analysis Tool will assist you to systematize notional evaluations of the value and readiness of potential disruptive technologies.

  • Disruptive Technology Value-Readiness and SWOT Analysis Tool

7. Proof of Concept Template – A handbook to serve as a reference when deciding how to proceed with your proposed solution.

The Proof of Concept Template will guide you through the creation of a minimum-viable proof-of-concept project.

  • Proof of Concept Template

8. Disruptive Technology Executive Presentation Template – A template to help you create a brief progress report presentation summarizing your project and program progress.

The Disruptive Technology Executive Presentation Template will assist you to present an overview of the disruptive technology process, outlining the value to your company.

  • Disruptive Technology Executive Presentation Template

Infographic

Workshop: Exploit Disruptive Infrastructure Technology

Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

1 Pre-work: Establish the Disruptive Tech Process

The Purpose

Discuss the general overview of the disruptive technology exploitation process.

Develop an initial disruptive technology exploitation plan.

Key Benefits Achieved

Stakeholders are on board, the project’s goals are outlined, and the working group is selected.

Activities

1.1 Get execs and stakeholders on board.

1.2 Review the process of analyzing disruptive tech.

1.3 Select members for the working group.

1.4 Choose a schedule and time commitment.

1.5 Select a group of visionaries.

Outputs

Initialized disruptive tech exploitation plan

Meeting agenda, schedule, and participants

2 Hold the Initial Meeting

The Purpose

Understand how disruption will affect the organization, and develop an initial list of technologies to explore.

Key Benefits Achieved

Knowledge of how to think like a futurist.

Understanding of organizational processes vulnerable to disruption.

Outline of potentially disruptive technologies.

Activities

2.1 Start the meeting with introductions.

2.2 Train the group to think like futurists.

2.3 Brainstorm about disruptive processes.

2.4 Brainstorm a longlist.

2.5 Research and brainstorm separate longlists.

Outputs

List of disruptive organizational processes

Initial longlist of disruptive tech

3 Create a Longlist and Assess Shortlist

The Purpose

Evaluate the specific value of longlisted technologies to the organization.

Key Benefits Achieved

Defined list of the disruptive technologies worth escalating to the proof of concept stage.

Activities

3.1 Converge the longlists developed by the team.

3.2 Narrow the longlist to a shortlist.

3.3 Assess readiness and value.

3.4 Perform a SWOT analysis.

Outputs

Finalized longlist of disruptive tech

Shortlist of disruptive tech

Value-readiness analysis

SWOT analysis

Candidate(s) for proof of concept charter

4 Create an Action Plan

The Purpose

Understand how the technologies in question will impact the organization.

Key Benefits Achieved

Understanding of the specific effects of the new technology on the business processes it is intended to disrupt.

Business case for the proof-of-concept project.

Activities

4.1 Build a problem canvas.

4.2 Identify affected business units.

4.3 Outline and map the business processes likely to be disrupted.

4.4 Map disrupted business processes.

4.5 Recognize how the new technology will impact business processes.

4.6 Make the case.

Outputs

Problem canvas

Map of business processes: current state

Map of disrupted business processes

Business case for each technology

Further reading

Analyst Perspective

The key is in anticipation.

“We all encounter unexpected changes and our responses are often determined by how we perceive and understand those changes. We react according to the unexpected occurrence. Business organizations are no different.

When a company faces a major technology disruption in its markets – one that could fundamentally change the business or impact its processes and technology – the way its management perceive and understand the disruption influences how they describe and plan for it. In other words, the way management sets the context of a disruption – the way they frame it – shapes the strategy they adopt. Technology leaders can vastly influence business strategy by adopting a proactive approach to understanding disruptive and innovative technologies by simply adopting a process to review and evaluate technology impacts to the company’s lines of business.”

This is a picture of Troy Cheeseman

Troy Cheeseman
Practice Lead, Infrastructure & Operations Research
Info-Tech Research Group

Executive Summary

Your Challenge

  • New technology can hit like a meteor. Not only disruptive to IT, technology provides opportunities for organization-wide advantage.
  • Your role is endangered. If you don’t prepare for the most disruptive technologies, you could be overshadowed. Don’t let the chief marketing officer (CMO) set the technological innovation agenda.

Common Obstacles

  • Predicting the future isn’t easy. Most IT leaders fail to realize how quickly technology increases in capability. Even for the tech savvy, predicting which specific technologies will become disruptive is difficult.
  • Communication is difficult when the sky is falling. Even forward-looking IT leaders struggle with convincing others to devote time and resources to monitoring technologies with a formal process.

Info-Tech’s Approach

  • Identify, resolve, and evaluate. Use an annual process as described in this blueprint: a formal evaluation of new technology that turns analysis into action.
  • Lead the analysis from IT. Establish a team to carry out the annual process as a cure for the causes of “airline magazine syndrome” and to prevent it from happening in the future.
  • Train your team on the patterns of progress, track technology over time in a central database, and read Info-Tech’s analysis of upcoming technology.
  • Create your KPIs. Establish your success indicators to create measurable value when presenting to your executive.
  • Produce a comprehensive proof-of-concept plan that will allow your company to minimize risk and maximize reward when engaging with new technology.

Info-Tech Insight

Proactively monitoring, evaluating, and exploiting disruptive tech isn’t optional.
This will protect your role, IT’s role, and the future of the organization.

A diverse working group maximizes the insight brought to bear.
An IT background is not a prerequisite.

The best technology is only the best when it brings immediate value.
Good technology might not be ready; ready technology might not be good.

Review

We help IT leaders make the most of disruptive impacts.

This research is designed for:

Target Audience: CIO, CTO, Head of Infrastructure

This research will help you:

  • Develop a process for anticipating, analyzing, and exploiting disruptive technology.
  • Communicate the business case for investing in disruptive technology.
  • Categorize emerging technologies to decide what to do with them.
  • Develop a plan for taking action to exploit the technology that will most affect your organization.

Problem statement:

As a CIO, there is a need to move beyond day-to-day technology management with an ever-increasing need to forecast technology impacts. Not just from a technical perspective but to map out the technical understandings aligned to potential business impacts and improvements. Technology transformation and innovation is moving more quickly than ever before and as an innovation champion, the CIO or CTO should have foresight in specific technologies with the understanding of how the company could be disrupted in the near future. Foresight + Current Technology + Business Understanding = Understanding the Business Disruption. This should be a repeatable process, not an exception or reactionary response.

Insight Summary

Establish the core working group, select a leader, and select a group of visionaries to help brainstorm emerging technologies.

The right team matters. A core working group will keep focus through the process and a leader will keep everyone accountable. Visionaries are out-of-the-box thinkers and once they understand how to think like a "futurists," they will drive the longlist and shortlist actions.

Train the group to think like futurists

To keep up with exponential technology growth you need to take a multi-threaded approach.

Brainstorm about creating a better future; begin brainstorming an initial longlist

Establish the longlist. The longlist helps create a holistic view of most technologies that could impact the business. Assigning values and quadrant scoring will shortlist the options and focus your PoC option.

Converge everyone’s longlists

Long to short...that's the short of it. Using SWOT, value readiness, and quadrant mapping review sessions will focus the longlist, creating a shortlist of potential POC candidates to review and consider.

Evaluate the shortlist

There is no such thing as a risk-free endeavor. Use a systematic process to ensure that the risks your organization takes have the potential to produce significant rewards.

Define your PoC list and schedule

Don’t be afraid to fail! Inevitably, some proof-of-concept projects will not benefit the organization. The projects that are successful will more than cover the costs of the failed projects. Roll out small scale and minimize losses.

Finalize, present the plan to stakeholders, and repeat!

Don't forget the C-suite. Effectively communicate and present the working group’s finding with a well-defined and succinct presentation. Start the process again!

This is a screenshot of the Thought map for Exploit disruptive infrastructure Technology.
  1. Identify
    • Establish the core working group and select a leader; select a group of visionaries
    • Train the group to think like futurists
    • Hold your initial meeting
  2. Resolve
  • Create and winnow a longlist
  • Assess and create the shortlist
  • Evaluate
    • Create process maps
    • Develop proof of concept charter
  • The Key Is in Anticipation!

    Use Info-Tech’s approach for analyzing disruptive technology in your own disruptive tech working group

    Phase 1: Identify Phase 2: Resolve Phase 3: Evaluate

    Phase Steps

    1. Establish the disruptive technology working group
    2. Think like a futurist (Training)
    3. Hold initial meeting or create an agenda for the meeting
    1. Create and winnow a longlist
    2. Assess shortlist
    1. Create process maps
    2. Develop proof of concept charter

    Phase Outcomes

    • Establish a team of subject matter experts that will evaluate new, emerging, and potentially disruptive technologies.
    • Establish a process for including visionaries from outside of the working group who will provide insight and direction.
    • Introduce the core working group members.
    • Gain a better understanding of how technology advances.
    • Brainstorm a list of organizational processes.
    • Brainstorm an initial longlist.
    • Finalized longlist
    • Finalized shortlist
    • Initial analysis of each technology on the shortlist
    • Finalized shortlist
    • Initial analysis of each technology on the shortlist
    • Business process maps before and after disruption
    • Proof of concept charter
    • Key performance indicators
    • Estimation of required resources
    • Executive presentation

    Four key challenges make it essential for you to become a champion for exploiting disruptive technology

    1. New technology can hit like a meteor. It doesn’t only disrupt IT; technology provides opportunities for organization-wide advantage.
    2. Your role is endangered. If you don’t prepare for the most disruptive technologies, you could be overshadowed. Don’t let the CMO rule technological innovation.
    3. Predicting the future isn’t easy. Most IT leaders fail to realize how quickly technology increases in capability. Even for the tech savvy, predicting which specific technologies will become disruptive is difficult.
    4. Communication is difficult when the sky is falling. Even forward-looking IT leaders struggle with convincing others to devote time and resources to monitoring emerging technologies with a formal process.

    “Look, you have never had this amount of opportunity for innovation. Don’t forget to capitalize on it. If you do not capitalize on it, you will go the way of the dinosaur.”
    – Dave Evans, Co-Founder and CTO, Stringify

    Technology can hit like a meteor

    “ By 2025:

    • 38.6 billion smart devices will be collecting, analyzing, and sharing data.
    • The web hosting services market is to reach $77.8 billion in 2025.
    • 70% of all tech spending is expected to go for cloud solutions.
    • There are 1.35 million tech startups.
    • Global AI market is expected to reach $89.8 billion.”

    – Nick Gabov

    IT Disruption

    Technology disrupts IT by:

    • Affecting the infrastructure and applications that IT needs to use internally.
    • Affecting the technology of end users that IT needs to support and deploy, especially for technologies with a consumer focus.
    • Allowing IT to run more efficiently and to increase the efficiency of other business units.
    • Example: The rise of the smartphone required many organizations to rethink endpoint devices.

    Business Disruption

    Technology disrupts the business by:

    • Affecting the viability of the business.
    • Affecting the business’ standing in relation to competitors that better deal with disruptive technology.
    • Affecting efficiency and business strategy. IT should have a role in technology-related business decisions.
    • Example: BlackBerry failed to anticipate the rise of the apps ecosystem. The company struggled as it was unable to react with competitive products.

    Senior IT leaders are expected to predict disruptions to IT and the business, while tending to today’s needs

    You are expected to be both a firefighter and a forecaster

    • Anticipating upcoming disruptions is part of your job, and you will be blamed if you fail to anticipate future business disruptions because you are focusing on the present.
    • However, keeping IT running smoothly is also part of your job, and you will be blamed if today’s IT environment breaks down because you are focusing on the future.

    You’re caught between the present and the future

    • You don’t have a process that anticipates future disruptions but runs alongside and integrates with operations in the present.
    • You can’t do it alone. Tending to both the present and the future will require a team that can help you keep the process running.

    Info-Tech Insight

    Be prepared when disruptions start coming down, even though it isn’t easy. Use this research to reduce the effort to a simple process that can be performed alongside everyday firefighting.

    Make disruptive tech analysis and exploitation part of your innovation agenda

    A scatter plot graph is depicted, plotting IT Innovative Leadership (X axis), and Satisfaction with IT(Y axis). IT innovative leadership explains 75% of variation in satisfaction with IT

    Organizations without high satisfaction with IT innovation leadership are only 20% likely to be highly satisfied with IT

    “You rarely see a real-world correlation of .86!”
    – Mike Battista, Staff Scientist, Cambridge Brain Sciences, PhD in Measurement

    There is a clear relationship between satisfaction with IT and the IT department’s innovation leadership.

    Prevent “airline magazine syndrome” by proactively analyzing disruptive technologies

    “The last thing the CIO needs is an executive saying ‘I don’t what it is or what it does…but I want two of them!”
    – Tim Lalonde

    Airline magazine syndrome happens to IT leaders caught between the business and IT. It usually occurs in this manner:

    1. While on a flight, a senior executive reads about an emerging technology that has exciting implications for the business in an airline magazine.
    2. The executive returns and approaches IT, demanding that action be taken to address the disruptive technology – and that it should have been (ideally) completed already.

    Without a Disruptive Technology Exploitation Plan:

    “I don’t know”

    With a Disruptive Technology Exploitation Plan:

    “Here in IT, we have already considered that technology and decided it was overhyped. Let me show you our analysis and invite you to join our working group.”

    OR

    “We have already considered that technology and have started testing it. Let me show you our testing lab and invite you to join our working group.”

    Info-Tech Insight

    Airline magazine syndrome is a symptom of a wider problem: poor CEO-CIO alignment. Solve this problem with improved communication and documentation. Info-Tech’s disruptive tech iterative process will make airline magazine syndrome a thing of the past!

    IT leaders who do not keep up with disruptive technology will find their roles diminished

    “Today’s CIO dominion is in a decaying orbit with CIOs in existential threat mode.”
    – Ken Magee

    Protect your role within IT

    • IT is threatened by disruptive technology:
      • Trends like cloud services, increased automation, and consumerization reduce the need for IT to be involved in every aspect of deploying and using technology.
      • In the long term, machines will replace even intellectually demanding IT jobs, such as infrastructure admin and high-level planning.
    • Protect your role in IT by:
      • Anticipating new technology that will disrupt the IT department and your place within it.
      • Defining new IT roles and responsibilities that accurately reflect the reality of technology today.
      • Having a process for the above that does not diminish your ability to keep up with everyday operations that remain a priority today.

    Protect your role against other departments

    • Your role in the business is threatened by disruptive technology:
      • The trends that make IT less involved with technology allow other executives – such as the CMO – to make IT investments.
      • As the CMO gains the power and data necessary to embrace new trends, the CIO and IT managers have less pull.
    • Protect your role in the business by:
      • Being the individual to consult about new technology. It isn’t just a power play; IT leaders should be the ones who know technology thoroughly.
      • Becoming an indispensable part of the entire business’ innovation strategy through proposing and executing a process for exploiting disruptive technology.

    IT leaders who do keep up have an opportunity to solidify their roles as experts and aggregators

    “The IT department plays a critical role in [innovation]. What they can do is identify a technology that potentially might introduce improvements to the organization, whether it be through efficiency, or through additional services to constituents.”
    – Michael Maguire, Management Consultant

    The contemporary CIO is a conductor, ensuring that IT works in harmony with the rest of the business.

    The new CIO is a conductor, not a musician. The CIO is taking on the role of a business engineer, working with other executives to enable business innovation.

    The new CIO is an expert and an aggregator. Conductor CIOs increasingly need to keep up on the latest technologies. They will rely on experts in each area and provide strategic synthesis to decide if, and how, developments are relevant in order to tune their IT infrastructure.

    The pace of technological advances makes progress difficult to predict

    “An analysis of the history of technology shows that technological change is exponential, contrary to the common-sense ‘intuitive linear’ view. So we won’t experience 100 years of progress in the 21st century – it will be more like 20,000 years of progress (at today’s rate).”
    – Ray Kurzweil

    Technology advances exponentially. Rather than improving by the same amount of capability each year, it multiplies in capability each year.

    Think like a futurist to anticipate technology before it goes mainstream.

    Exponential growth happens much faster than linear growth, especially when it hits the knee of the curve. Even those who acknowledge exponential growth underestimate how capabilities can improve.

    To predict new advances, turn innovation into a process

    “We spend 70 percent of our time on core search and ads. We spend 20 percent on adjacent businesses, ones related to the core businesses in some interesting way. Examples of that would be Google News, Google Earth, and Google Local. And then 10 percent of our time should be on things that are truly new.”
    – Eric Schmidt, Google

    • Don’t get caught in the trap of refining your core processes to the exclusion of innovation. You should always be looking for new processes to improve, new technology to pilot, and where possible, new businesses to get into.
    • Devote about 10% of your time and resources to exploring new technology: the potential rewards are huge.

    You and your team need to analyze technology every year to predict where it’s going.

    A bar graph is shown which depicts the proportion of technology use from 2018-2022. the included devices are: Tablets; PCs; TVs; Non-smartphones; Smartphones; M2M
    • Foundational technologies, such as computing power, storage, and networks, are improving exponentially.
    • Disruptive technologies are specific manifestations of foundational advancements. Advancements of greater magnitude give rise to more manifestations; therefore, there will be more disruptive technologies every year.
    • There is a lot of noise to cut through. Remember Google Glasses? As technology becomes ubiquitous and consumerization reigns, everybody is a technology expert. How do you decide which technologies to focus on?

    Protect IT and the business from disruption by implementing a simple, repeatable disruptive technology exploitation process

    “One of the most consistent patterns in business is the failure of leading companies to stay at the top of their industries when technologies or markets change […] Managers must beware of ignoring new technologies that can’t initially meet the needs of their mainstream customers.”
    – Joseph L. Bower and Clayton M. Christensen

    Challenge

    Solution

    New technology can hit like a meteor, but it doesn’t have to leave a crater:

    Use the annual process described in this blueprint to create a formal evaluation of new technology that turns analysis into action.

    Predicting the future isn’t easy, but it can be done:

    Lead the analysis from the office of the CIO. Establish a team to carry out the annual process as a cure for airline magazine syndrome.

    Your role is endangered, but you can survive:

    Train your team on the patterns of progress, track technology over time in a central database, and read Info-Tech’s analysis of upcoming technology.

    Communication is difficult when the sky is falling, so have a simple way to get the message across:

    Track metrics that communicate your progress, and summarize the results in a single, easy-to-read exploitation plan.

    Info-Tech Insight

    Use Info-Tech’s tools and templates, along with this storyboard, to walk you through creating and executing an exploitation process in six steps.

    Create measurable value by using Info-Tech’s process for evaluating the disruptive potential of technology

    This image contains a bar graph with the following Title: Which are the primary benefits you've either realized or expect to realize by deploying hyperconverged infrastructure in the near term.

    No business process is perfect.

    • Use Info-Tech’s Proof of Concept Template to create a disruptive technology proof of concept implementation plan.
    • Harness your company’s internal wisdom to systematically vet new technology. Engage only in calculated risk and maximize potential benefit.

    Info-Tech Insight

    Inevitably, some proof of concept projects will not benefit the organization. The projects that are successful will more than cover the costs of the failed projects. Roll out small scale and minimize losses.

    Establish your key performance indicators (KPIs)

    Key performance indicators allow for rigorous analysis, which generates insight into utilization by platform and consumption by business activity.

    • Brainstorm metrics that indicate when process improvement is actually taking place.
    • Have members of the group pitch KPIs; the facilitator should record each suggestion on a whiteboard.
    • Make sure to have everyone justify the inclusion of each metric: how does it relate to the improvement that the proof of concept project is intended to drive? How does it relate to the overall goals of the business?
    • Include a list of KPIs, along with a description and a target (ensuring that it aligns with SMART metrics).
    Key Performance Indicator Description Target Result

    Number of Longlist technologies

    Establish a range of Longlist technologies to evaluate 10-15
    Number of Shortlist technologies Establish a range of Shortlist technologies to evaluate 5-10
    number of "look to the past" likes/dislikes Minimum number of testing characteristics 6
    Number of POCs Total number of POCs Approved 3-5

    Communicate your plan with the Disruptive Technology Exploitation Plan Template

    Use the Disruptive Technology Exploitation Plan Template to summarize everything that the group does. Update the report continuously and use it to show others what is happening in the world of disruptive technology.

    Section Title Description
    1 Rationale and Summary of Exploitation Plan A summary of the current efforts that exist for exploring disruptive technology. A summary of the process for exploiting disruptive technology, the resources required, the team members, meeting schedules, and executive approval.
    2 Longlist of Potentially Disruptive Technologies A summary of the longlist of identified disruptive technologies that could affect the organization, shortened to six or less that have the largest potential impact based on Info-Tech’s Disruptive Technology Shortlisting Tool.
    3 Analysis of Shortlist Individually analyze each technology placed on the shortlist using Info-Tech’s Disruptive Technology Value-Readiness and SWOT Analysis Tool.
    4 Proof of Concept Plan Use the results from Section 3 to establish a plan for moving forward with the technologies on the shortlist. Determine the tasks required to implement the technologies and decide who will complete them and when.
    5 Hand-off Pass the project along to identified stakeholders with significant interest in its success. Continue to track metrics and prepare to repeat the disruptive technology exploitation process annually.

    Whether you need a process for exploiting disruptive technology, or an analysis of current trends, Info-Tech can help

    Two sets of research make up Info-Tech’s disruptive technology coverage:

    This image contains four screenshots from each of the following Info-Tech Blueprints: Exploit disruptive Infrastructure Technology; Infrastructure & operations priorities 2022

    This storyboard, and the associated tools and templates, will walk you through creating a disruptive technology working group of your own.

    Blueprint deliverables

    Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

    Key deliverable:

    Disruptive Technology Exploitation Plan Template

    The Disruptive Technology Exploitation Plan Template acts as an implementation plan for developing a long-term strategy for monitoring and implementing disruptive technologies.

    Proof of Concept Template

    The Proof of Concept Template will guide you through the creation of a minimum-viable proof-of-concept project.

    Executive Presentation

    The Disruptive Technology Executive Presentation Template will assist you to present an overview of the disruptive technology process, outlining the value to your company.

    Disruptive Technology Value Readiness & SWOT Analysis Tool

    The Disruptive Technology Value Readiness & SWOT Analysis Tool will assist you to systematize notional evaluations of the value and readiness of potential disruptive technologies.

    Disruptive Technology Research Database Tool

    The Disruptive Technology Research Database Tool will help you to keep track of the independent research that is conducted by members of the disruptive technology exploitation working group.

    Disruptive Technology Shortlisting Tool

    The Disruptive Technology Shortlisting Tool will help you to codify the results of the disruptive technology working group's longlist winnowing process.

    Disruptive Technology Look to the Past Tool

    The Disruptive Technology Look to the Past Tool will assist you to collect reasonability test notes when evaluating potential disruptive technologies.

    Info-Tech offers various levels of support to best suit your needs

    DIY Toolkit

    “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

    Guided Implementation

    “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”

    Workshop

    “We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”

    Consulting

    “Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

    Diagnostics and consistent frameworks used throughout all four options

    Guided Implementation

    What does a typical GI on this topic look like?

    Phase 1 Phase 2 Phase 3

    Call #1: Explore the need for a disruptive technology working group.

    Call #3: Review the agenda for the initial meeting.

    Call #5: Review how you’re brainstorming and your sources of information.

    Call #7: Review the final shortlist and assessment.

    Call #9: Review the progress of your team.

    Call #2: Review the team name, participants, and timeline.

    Call #4: Assess the results of the initial meeting.

    Call #6: Review the final longlist and begin narrowing it down.

    Call #8: Review the next steps.

    Call #10: Review the communication plan.

    A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

    A typical GI is 8 to 12 calls over the course of 4 to 6 months.

    Workshop Overview

    Contact your account representative for more information.
    workshops@infotech.com 1-888-670-8889

    Pre-Work Day 1 Day 2 Day 3 Day 4
    Establish the Disruptive Tech Process Hold Your Initial Meeting Create a Longlist and Assess Shortlist Create Process Maps Develop a Proof of Concept Charter

    Activities

    1.1.a Get executives and stakeholders on board.

    1.1.b Review the process of analyzing disruptive tech.

    1.1.c Select members for the working group.

    1.1.d Choose a schedule and time commitment.

    1.1.e Select a group of visionaries.

    1.2.a Start the meeting with introductions.

    1.2.b Train the group to think like futurists.

    1.2.c Brainstorm about disruptable processes.

    1.2.d Brainstorm a longlist.

    1.2.e Research and brainstorm separate longlists.

    2.1.a Converge the longlists developed by the team.

    2.2.b Narrow the longlist to a shortlist.

    2.2.c Assess readiness and value.

    2.2.d Perform a SWOT analysis.

    3.1.a Build a problem canvas.

    3.1.b Identify affected business units.

    3.1.c Outline and map the business processes likely to be disrupted.

    3.1.d Map disrupted business processes.

    3.1.e Recognize how the new technology will impact business processes.

    3.1.f Make the case.

    3.2.a Develop key performance indicators (KPIs).

    3.2.b Identify key success factors.

    3.2.c Outline project scope.

    3.2.d Identify responsible team.

    3.2.e Complete resource estimation.

    Deliverables

    1. Initialized Disruptive Tech Exploitation Plan
    1. List of Disruptable Organizational Processes
    2. Initial Longlist of Disruptive Tech
    1. Finalized Longlist of Disruptive Tech
    2. Shortlist of Disruptive Tech
    3. Value-Readiness Analysis
    4. SWOT Analysis
    5. Candidate(s) for Proof of Concept Charter
    1. Problem Canvas
    2. Map of Business Processes: Current State
    3. Map of Disrupted Business Processes
    4. Business Case for Each Technology
    1. Completed Proof of Concept Charter

    Exploit Disruptive Infrastructure Technology

    Disrupt or be disrupted.

    Identify

    Create your working group.

    PHASE 1

    Use Info-Tech’s approach for analyzing disruptive technology in your own disruptive tech working group

    1. Identify
      1. Establish the core working group and select a leader; select a group of visionaries
      2. Train the group to think like futurists
      3. Hold your initial meeting
    2. Resolve
      1. Create and winnow a longlist
      2. Assess and create the shortlist
    3. Evaluate
      1. Create process maps
      2. Develop proof of concept charter

    The Key Is in Anticipation!

    Phase 1: Identify

    Create your working group.

    Activities:

    Step 1.1: Establish the core working group and select a leader; select a group of visionaries
    Step 1.2: Train the group to think like futurists
    Step 1.3: Hold the initial meeting

    This step involves the following participants:

    IT Infrastructure Manager

    CIO or CTO

    Potential members and visionaries of the working group

    Outcomes of this step:

    • Establish a team of subject matter experts that will evaluate new, emerging, and potentially disruptive technologies.
    • Establish a process for including visionaries from outside of the working group who will provide insight and direction.
    • Introduce the core working group members.
    • Gain a better understanding of how technology advances.
    • Brainstorm a list of organizational processes.
    • Brainstorm an initial longlist.

    Step 1.1

    Establish the core working group and select a leader; select a group of visionaries.

    Activities:

    • Articulate the long- and short-term benefits and costs to the entire organization
    • Gain support by articulating the long- and short-term benefits and costs to the IT department
    • Gain commitment from key stakeholders and executives
    • Help stakeholders understand what goes into formally exploiting disruptive tech by reviewing this process
    • Establish the core working group and select a leader
    • Create a schedule with a time commitment appropriate to your organization’s size; it doesn’t need to take long
    • Select a group of visionaries external to IT to help the working group brainstorm disruptive technologies

    This step involves the following participants:

    • IT Infrastructure Manager
    • CIO or CTO
    • Potential members and visionaries of the working group

    Outcomes of this step

    • Establish a team of subject matter experts that will evaluate new, emerging, and potentially disruptive technologies.
    • Establish a process for including visionaries from outside of the working group that will provide insight and direction.

    1.1.A Articulate the long- and short-term benefits and costs to the entire organization

    A cost/benefit analysis will give stakeholders a picture of how disruptive technology could affect the business. Use the chart as a starting point and customize it based on your organization.

    Disruptive Technology Affects the Organization

    Benefits Costs

    Short Term

    • First-mover advantage from implementing new technology in the business before competitors – and before start-ups.
    • Better brand image as an organization focused on innovation.
    • Increased overall employee satisfaction by implementing new technology that increases employee capabilities or lowers effort.
    • Possibility of increased IT budget for integrating new technology.
    • Potential for employees to reject wide-scale use of unfamiliar technology.
    • Potential for technology to fail in the organization if it is not sufficiently tested.
    • Executive time required for making decisions about technology recommended by the team.

    Long Term

    • Increased internal business efficiencies from the integration of new technology (e.g. energy efficiency, fewer employees needed due to automation).
    • Better services or products for customers, resulting in increased long-term revenue.
    • Lowered costs of services or products and potential to grow market share.
    • Continued relevance of established organizations in a world changed by disruptive technologies.
    • Technology may not reach the capabilities initially expected, requiring waiting for increased value or readiness.
    • Potential for customers to reject new products resulting from technology.
    • Lack of focus on current core capabilities if technology is massively disruptive.

    1.1.B Gain support by articulating the long- and short-term benefits and costs to the IT department

    A cost/benefit analysis will give stakeholders a picture of how disruptive technology could affect the business. Use the chart as a starting point and customize it based on your organization.

    Disruptive Technology Affects IT

    BenefitsCosts

    Short Term

    • Perception of IT as a core component of business practices.
    • Increase IT’s capabilities to better serve employees (e.g. faster network speeds, better uptime, and storage and compute capacity that meet demands).
    • Cost for acquiring or implementing new technology and updating infrastructure to integrate with it.
    • Cost for training IT staff and end users on new IT technology and processes.
    • Minor costs for initial setup of disruptive technology exploitation process and time taken by members.

    Long Term

    • More efficient and powerful IT infrastructure that capitalizes on emerging trends at the right time.
    • Lower help desk load due to self-service and automation technology.
    • Increased satisfaction with IT due to implementation of improved enterprise technology and visible IT influence on improvements.
    • Increased end-user satisfaction with IT due to understanding and support of consumer technology that affects their lives.
    • New technology may result in lower need for specific IT roles. Cultural disruptions due to changing role of IT.
    • Perception of failure if technology is tested and never implemented.
    • Expectation that IT will continue to implement the newest technology available, even when it has been dismissed as not having value.

    1.1.C Gain commitment from key stakeholders and executives

    Gaining approval from executives and key stakeholders is the final obstacle. Ensure that you cover the following items to have the best chance for project approval.

    • Use a sample deck similar to this section for gaining buy-in, ensuring that you add/remove information to make it specific to your organization. Cover this section, including:
      • Who: Who will lead the team and who will be on it (working group)?
      • What: What resources will be required by the team (costs)?
      • Where/When: How often and where will the team meet (meeting schedule)?
      • Why: Why is there a need to exploit disruptive technology (benefits and examples)?
      • How: How is the team going to exploit disruptive technology (the process)?
    • Go through this blueprint prior to presenting the plan to stakeholders so that you have a strong understanding of the details behind each process and tool.
    • Frame the first iteration of the cycle as a pilot program. Use the completed results of the pilot to establish exploiting disruptive technology as a necessary company initiative.

    Insert the resources required by the disruptive tech exploitation team into Section 1.5 of the Disruptive Technology Exploitation Plan Template. Have executives sign-off on the project in Section 1.6.

    Disruption has undermined some of the most successful tech companies

    “The IT department plays a critical role in [innovation]. What they can do is identify a technology that potentially might introduce improvements to the organization, whether it be through efficiency or through additional services to constituents.”
    - Michael Maguire, Management Consultant

    VoIP’s transformative effects

    Disruptive technology:
    Voice over Internet Protocol (VoIP) is a modern means of making phone calls through the internet by sending voice packets using data, as opposed to the traditional circuit transmissions of the PSTN.

    Who won:
    Organizations that realized the cost savings that VoIP provided for businesses with a steady internet connection saved as much as 60% on telephony expenses. Even in the early stages, with a few more limitations, organizations were able to save a significant amount of money and the technology has continued to improve.

    Who lost?
    Telecom-related companies that failed to realize VoIP was a potential threat to their market, and organizations that lacked the ability to explore and implement the disruptive technology early.

    Digital photography — the new norm

    Disruptive technology:
    Digital photography refers to the storing of photographs in a digital format, as opposed to traditional photography, which exposes light to sensitive photographic film.

    Who won:
    Photography companies and new players that exploited the evolution of data storage and applied it to photography succeeded. Those that were able to balance providing traditional photography and exploiting and introducing digital photography, such as Nikon, left competitors behind. Smartphone manufacturers also benefited by integrating digital cameras.

    Who lost?
    Photography companies, such as Kodak, that failed to respond to the digital revolution found themselves outcompeted and insolvent.

    1.1.D Help stakeholders understand what goes into formally exploiting disruptive tech by reviewing this process

    There are five steps to formally exploiting disruptive technology, each with its own individual outputs and tools to take analysis to the next level.

    Step 1.2:
    Hold Initial Meeting

    Output:

    • Initial list of disruptable processes;
    • Initial longlist

    Step 2.1:

    Brainstorm Longlist

    Output:

    • Finalized longlist;
    • Shortlist

    Step 2.2:

    Assess Shortlist

    Output:

    • Final shortlist;
    • SWOT analysis;
    • Tech categorization

    Step 3.1:
    Create Process Maps

    Output:

    • Completed process maps

    Step 3.2:
    Develop a proof of concept charter

    Output:

    • Proof-of-concept template with KPIs

    Info-Tech Insight

    Before going to stakeholders, complete the entire blueprint to better understand the tools and outputs of the process.

    1.1.E Establish the core working group and select a leader

    • Selecting your core membership for the working group is a critical step to the group’s success. Ensure that you satisfy the following criteria:
      • This is a team of subject matter experts. They will be overseeing the learning and piloting of disruptive technologies. Their input will also be valuable for senior executives and for implementing these technologies.
      • Choose members that can take time away from firefighting tasks to dedicate time to meetings.
      • It may be necessary to reach outside of the organization now or in the future for expertise on certain technologies. Use Info-Tech as a source of information.
    Organization Size Working Group Size
    Small 02-Jan
    Medium 05-Mar
    Large 10-May
    • Once the team is established, you must decide who will lead the group. Ensure that you satisfy the following criteria:
      • A leader should be credible, creative, and savvy in both technology and business.
      • The leader should facilitate, acting as both an expert and an aggregator of the information gathered by the team.

    Choose a compelling name

    The working group needs a name. Be sure to select one with a positive connotation within your organization.

    Section 1.3 of the Disruptive Technology Exploitation Plan Template

    1.1.F Create a schedule with a time commitment appropriate to your organization’s size; it doesn’t need to take long

    Time the disruptive technology working group’s meetings to coincide and integrate with your organization’s strategic planning — at least annually.

    Size Meeting Frequency Time per Meeting Example Meeting Activities
    Small Annually One day A one-day meeting to run through phase 2 of the project (SWOT analysis and shortlist analysis).
    Medium Two days A two-day meeting to run through the project. The additional meeting involves phase 3 of this deck, developing a proof-of-concept plan.
    Large Two+ days Two meetings, each two days. Two days to create and winnow the longlist (phase 2), and two further days to develop a proof of concept plan.

    “Regardless of size, it’s incumbent upon every organization to have some familiarity of what’s happening over the next few years, [and to try] to anticipate what some of those trends may be. […] These trends are going to accelerate IT’s importance in terms of driving business strategy.”
    – Vern Brownell, CEO, D-Wave

    Section 1.4 of the Disruptive Technology Exploitation Plan Template

    1.1.G Select a group of visionaries external to IT to help the working group brainstorm disruptive technologies

    Selecting advisors for your group is an ongoing step, and the roster can change.

    Ensure that you satisfy the following criteria:

    • Look beyond IT to select a team representing several business units.
    • Check for self-professed “geeks” and fans of science fiction that may be happy to join.
    • Membership can be a reward for good performance.

    This group does not have to meet as regularly as the core working group. Input from external advisors can occur between meetings. You can also include them on every second or third iteration of the entire process.

    However, the more input you can get into the group, the more innovative it can become.

    “It is … important to develop design fictions based on engagement with directly or indirectly implicated publics and not to be designed by experts alone.”
    – Emmanuel Tsekleves, Senior Lecturer in Design Interactions, University of Lancaster

    Section 1.3 of the Disruptive Technology Exploitation Plan Template

    The following case study illustrates the innovative potential that is created when you include a diverse group of people

    INDUSTRY - Chip Manufacturing
    SOURCE - Clayton Christensen, Intel

    To achieve insight, you need to collaborate with people from outside of your department.

    Challenge

    • Headquartered in California, through the 1990s, Intel was the largest microprocessor chip manufacturer in the world, with revenue of $25 billion in 1997.
    • All was not perfect, however. Intel faced a challenge from Cyrix, a manufacturer of low-end chips. In 18 months, Cyrix’s share of the low-margin entry-level chip manufacturing business mushroomed from 10% to 70%.

    Solution

    • Troubled by the potential for significant disruption of the microprocessor market, Intel brought in external consultants to hold workshops to educate managers about disruptive innovation.
    • Managers would break into groups and discuss ways Intel could facilitate the disruption of its competitors. In one year, Intel hosted 18 workshops, and 2,000 managers went through the process.

    Results

    • Intel launched the Celeron chip to serve the lower end of the PC market and win market share back from Cyrix (which no longer exists as an independent company) and other competitors like AMD.
    • Within one year, Intel had captured 35% of the market.

    “[The models presented in the workshops] gave us a common language and a common way to frame the problem so that we could reach a consensus around a counterintuitive course of action.” – Andy Grove, then-CEO, Intel Corporation

    Phase 1: Identify

    Create your working group.

    Activities:

    Step 1.1: Establish the core working group and select a leader; select a group of visionaries
    Step 1.2: Train the group to think like futurists
    Step 1.3: Hold the initial meeting

    This step involves the following participants:

    • IT Infrastructure Manager
    • CIO or CTO
    • Potential members and visionaries of the working group

    Outcomes of this phase:

    • Establish a team of subject matter experts that will evaluate new, emerging, and potentially disruptive technologies.
    • Establish a process for including visionaries from outside of the working group who will provide insight and direction.
    • Introduce the core working group members.
    • Gain a better understanding of how technology advances.
    • Brainstorm a list of organizational processes.
    • Brainstorm an initial longlist.

    Step 1.2

    Train the group to think like futurists

    Activities:

    1. Look to the past to predict the future:
      • Step 1: Review the technology opportunities you missed
      • Step 2: Review and record what you liked about the tech
      • Step 3: Review and record your dislikes
      • Step 4: Record and test the reasonability
    2. Crash course on futurology principles
    3. Peek into the future

    This step involves the following participants:

    • IT Infrastructure Manager
    • CIO or CTO
    • Core working group members
    • Visionaries

    Outcomes of this step

    • Team members thinking like futurists
    • Better understanding of how technology advances
    • List of past examples and characteristics

    Info-Tech Insight

    Business buy-in is essential. Manage your business partners by providing a summary of the EDIT methodology and process. Validate the process value, which will allow you create a team of IT and business representatives.

    1.2 Train the group to think like futurists

    1 hour

    Ensure the team understands how technology advances and how they can identify patterns in upcoming technologies.

    1. Lead the group through a brainstorming session.
    2. Follow the next phases and steps.
    3. This session should be led by someone who can facilitate a thought-provoking discussion.
    4. This training deck finishes with a video.

    Input

    • Facilitated creativity
    • Training deck [following slides]

    Output

    • Inspiration
    • Anonymous ideas

    Materials

    • Futurist training “steps”
    • Pen and paper

    Participants

    • Core working group
    • Visionaries
    • Facilitator

    1.2.A Look to the past to predict the future

    30 minutes

    Step 1

    Step 2 Step 3 Step 4

    Review what you missed.

    What did you like?

    What did you dislike?

    Test the reasonability.

    Think about a time you missed a technical disruptive opportunity.

    Start with a list of technologies that changed your business and processes.

    Consider those specifically you could have identified with a repeatable process.

    What were the most impactful points about the technology?

    Define a list of “characteristics” you liked.

    Create a shortlist of items.

    Itemize the impact to process, people, and technology.

    Why did you pass on the tech?

    Define a list of “characteristics” you did not like.

    Create a shortlist of items.

    Itemize the impact to process, people, and technology.

    Avoid the “arm chair quarterback” view.

    Refer to the six positive and negative points.

    Check against your data points at the end of each phase.

    Record the list of missed opportunities

    Record 6 characteristics

    Record 6 characteristics

    Completed “Think like a Futurists” tool

    Use the Disruptive Technology Research Look to the Past Tool to record your output.

    Input

    • Facilitated creativity
    • Speaker’s notes

    Output

    • Inspiration
    • Anonymous ideas
    • Recorded missed opportunities
    • Recorded positive points
    • Recorded dislikes
    • Reasonability test list

    Materials

    • Futurist training “steps”
    • Pen and paper
    • “Look to the Past” tool

    Participants

    • Core working group
    • Visionaries
    • Facilitator

    Understand how the difference between linear and exponential growth will completely transform many organizations in the next decade

    “The last ten years have seen exponential growth in research on disruptive technologies and their impact on industries, supply chains, resources, training, education and employment markets … The debate is still open on who will be the winners and losers of future industries, but what is certain is that change has picked up pace and we are now in a new technology revolution whose impact is potentially greater than the industrial revolution.”
    – Gary L. Evans

    Exponential advancement will ensure that life in the next decade will be very different from life today.

    • Linear growth happens one step at a time.
    • The difference between linear and exponential is hard to notice, at first.
    • We are now at the knee of the curve.

    What about email?

    • Consider the amount of email you get daily
    • Double it
    • Triple it

    Exponential growth happens much faster than linear growth, especially when it hits the knee of the curve. Technology grows exponentially, and we are approaching the knee of the curve.

    This graph is adapted from research by Ray Kurzweil.

    Growth: Linear vs. Exponential

    This image contains a graph demonstrating examples of exponential and linear trends.

    1.2.B Crash course on futurology principles

    1 hour

    “An analysis of the history of technology shows that technological change is exponential, contrary to the common-sense ‘intuitive linear’ view. So we won’t experience 100 years of progress in the 21st century — it will be more like 20,000 years of progress (at today’s rate).”
    - Ray Kurzweil

    Review the differences between exponential and linear growth

    The pace of technological advances makes progress difficult to predict.

    Technology advances exponentially. Rather than improving by the same amount of capability each year, it multiplies in capability each year.

    Think like a futurist to anticipate technology before it goes mainstream.

    Exponential growth happens much faster than linear growth, especially when it hits the knee of the curve. Even those who acknowledge exponential growth underestimate how capabilities can improve.

    The following case study illustrates the rise of social media providers

    “There are 7.7 billion people in the world, with at least 3.5 billion of us online. This means social media platforms are used by one in three people in the world and more than two-thirds of all internet users.”
    – Esteban Ortiz-Ospina

    This graph depicts the trend of the number of people using social media platforms between 2005 and 2019

    The following case study illustrates the rapid growth of Machine to Machine (M2M) connections

    A bar graph is shown which depicts the proportion of technology use from 2018-2022. the included devices are: Tablets; PCs; TVs; Non-smartphones; Smartphones; M2M

    Ray Kurzweil’s Law of Accelerating Returns

    “Ray Kurzweil has been described as ‘the restless genius’ by The Wall Street Journal, and ‘the ultimate thinking machine’ by Forbes. He was ranked #8 among entrepreneurs in the United States by Inc Magazine, calling him the ‘rightful heir to Thomas Edison,’ and PBS included Ray as one of 16 ‘revolutionaries who made America,’ along with other inventors of the past two centuries.”
    Source: KurzweilAI.net

    Growth is linear?

    “Information technology is growing exponentially. That’s really my main thesis, and our intuition about the future is not exponential, it’s really linear. People think things will go at the current pace …1, 2, 3, 4, 5, and 30 steps later, you’re at 30.”

    Better IT strategy enables future business innovation

    “The reality of information technology like computers, like biological technologies now, is it goes exponentially … 2, 4, 8, 16. At step 30, you’re at a billion, and this is not an idle speculation about the future.” [emphasis added]

    “When I was a student at MIT, we all shared a computer that cost tens of millions of dollars. This computer [pulling his smartphone out of his pocket] is a million times cheaper, a thousand times more powerful — that’s a billion-fold increase in MIPS per dollar, bits per dollar… and we’ll do it again in 25 years.”
    Source: “IT growth and global change: A conversation with Ray Kurzweil,” McKinsey & Company

    1.2.C Peak into the future

    1 hour

    Leverage industry roundtables and trend reports to understand the art of the possible

    • Uncover important business and industry trends that can inform possibilities for technology disruption.
    • Market research is critical in identifying factors external to your organization and identifying technology innovation that will provide a competitive edge. It’s important to evaluate the impact each trend or opportunity will have in your organization and market.

    Visit Info-Tech’s Trends & Priorities Research Center

    Visit Info-Tech’s Industry Coverage Research to get started.

    Phase 1: Identify

    Create your working group

    Activities:

    Step 1.1: Establish the core working group and select a leader; select a group of visionaries
    Step 1.2: Train the group to think like futurists
    Step 1.3: Hold the initial meeting

    This step involves the following participants:

    • IT Infrastructure Manager
    • CIO or CTO
    • Potential members and visionaries of the working group

    Outcomes of this phase:

    • Establish a team of subject matter experts that will evaluate new, emerging, and potentially disruptive technologies.
    • Establish a process for including visionaries from outside of the working group who will provide insight and direction.
    • Introduce the core working group members.
    • Gain a better understanding of how technology advances.
    • Brainstorm a list of organizational processes.
    • Brainstorm an initial longlist.

    Info-Tech Insight

    Establish the longlist. The longlist help create a holistic view of most technologies that could impact the business. Assigning values and quadrant scoring will shortlist the options and focus your PoC option.

    Step 1.3

    Hold the initial meeting

    Activities:

    1. Create an agenda for the meeting
    2. Start the kick-off meeting with introductions and a recap
    3. Brainstorm about creating a better future
    4. Begin brainstorming an initial longlist
    5. Have team members develop separate longlists for their next meeting

    This step involves the following participants:

    • IT Infrastructure Manager
    • CIO or CTO
    • Core working group members
    • Visionaries

    Outcomes of this step

    • Introduce the core working group members
    • Gain a better understanding of how technology advances
    • Brainstorm a list of organizational processes
    • Brainstorm an initial longlist

    1.3.A Create an agenda for the meeting

    1 hour

    Kick-off this cycle of the disruptive technology process by welcoming your visionaries and introducing your core working group.

    The purpose of the initial meeting is to brainstorm where new technology will be the most disruptive within the organization. You’ll develop two longlists: one of business processes and one of disruptive technology. These longlists are in addition to the independent research your core working group will perform before Phase 2.

    • Find an outgoing facilitator. Sitting back will let you focus more on ideating, and an engaging presenter will help bring out ideas from your visionaries.
    • The training deck (see step 1.2c) includes presenting a video. We’ve included some of our top choices for you to choose from.
      • Feel free to find your own video or bring in a keynote speaker.
      • The object of the video is to get the group thinking about the future.
      • Customize the training deck as needed.
    • If a cycle has been completed, present your findings and all of the group’s completed deliverables in the first section.
    • This session is the only time you have with your visionaries. Get their ideas on what technologies will be disruptive to start forming a longlist.

    Info-Tech Insight

    The disruptive tech team is prestigious. If your organization is large enough or has the resources, consider having this meeting in an offsite location. This will drive excitement to join the working group if the opportunity arises and incentivize good work.

    Meeting Agenda (Sample)

    Time

    Activity

    8:00am-8:30am Introductions and previous meeting recap
    8:30am-9:30am Training deck
    9:30 AM-10:00am Brainstorming
    10:00am-10:15am Break
    10:15am-10:45am Develop good research techniques
    10:45am-12:00pm Begin compiling your longlist

    Info-Tech Insight

    The disruptive tech team is prestigious. If your organization is large enough or has the resources, consider having this meeting in an offsite location. This will drive excitement to join the working group if the opportunity arises and incentivize good work.

    1.3.B Start the kick-off meeting with introductions and a summary of what work has been done so far

    30 minutes

    1. Start the meeting off with an icebreaker activity. This isn’t an ordinary business meeting – or even group – so we recommend starting off with an activity that will emphasize this unique nature. To get the group in the right mindset, try this activity:
      1. Go around the group and have people present:
      2. Their names and roles
      3. Pose some or all of the following questions/prompts to the group:
        • “Tell me about something you have created.”
        • “Tell me about a time you created a process or program considered risky.”
        • “Tell me about a situation in which you had to come up with several new ideas in a hurry. Were they accepted? Were they successful?”
        • “Tell me about a time you took a risk.”
        • “Tell me about one of your greatest failures and what you learned from it.”
    2. Once everyone has been introduced, present any work that has already been completed.
      1. If you have already completed a cycle, give a summary of each technology that you investigated and the results from any piloting.
      2. If this is the first cycle for the working group, present the information decided in Step 1.1.

    Input

    • Disruptive technology exploitation plan

    Output

    • Networking
    • Brainstorming

    Materials

    • Meeting agenda

    Participants

    • Core working group
    • Visionaries
    • Facilitator

    1.3.C Brainstorm about creating a better future for the company, the stakeholders, and the employees

    30 minutes

    Three sticky notes are depicted, at the top of each note are the following titles: What can we do better; How can we make a better future; How can we continue being successful

    1. Have everyone put up at least two ideas for each chart paper.
    2. Go around the room and discuss their ideas. You may generate some new ideas here.

    These generated ideas are organizational processes that can be improved or disrupted with emerging technologies. This list will be referenced throughout Phases 2 and 3.

    Input

    • Inspiration
    • Anonymous ideas

    Output

    • List of processes

    Materials

    • Chart paper and markers
    • Pen and paper

    Participants

    • Core working group
    • Visionaries

    1.3.D Begin brainstorming a longlist of future technology, and discuss how these technologies will impact the business

    30 minutes

    • Use the Disruptive Technology Research Database Tool to organize technologies and ideas. Longstanding working groups can track technologies here over the course of several years, updating the tool between meetings.
    • Guide the discussion with the following questions, and make sure to focus on the processes generated from Step 1.2.d.

    Focus on

    The Technology

    • What is the technology and what does it do?
    • What processes can it support?

    Experts and Other Organizations

    • What are the vendors saying about the technology?
    • Are similar organizations implementing the technology?

    Your Organization

    • Is the technology ready for wide-scale distribution?
    • Can the technology be tested and implemented now?

    The Technology’s Value

    • Is there any indication of the cost of the technology?
    • How much value will the technology bring?

    Download the Disruptive Technology Database Tool

    Input

    • Inspiration
    • List of processes

    Output

    • Initial longlist

    Materials

    • Chart paper and markers
    • Pen and paper
    • Disruptive Technology Research Database Tool

    Participants

    • Core working group
    • Visionaries

    1.3.E Explore these sources to generate your disruptive technology longlist for the next meeting

    30 Minutes

    There are many sources of information on new and emerging technology. Explore as many sources as you can.

    Science fiction is a valid source of learning. It drives and is influenced by disruptive technology.

    “…the inventor of the first liquid-fuelled rocket … was inspired by H.G. Wells’ science fiction novel War of the Worlds (1898). More recent examples include the 3D gesture-based user interface used by Tom Cruise’s character in Minority Report (2002), which is found today in most touch screens and the motion sensing capability of Microsoft’s Kinect. Similarly, the tablet computer actually first appeared in Stanley Kubrick’s 2001: A Space Odyssey (1968) and the communicator – which we’ve come to refer today as the mobile phone – was first used by Captain Kirk in Star Trek (1966).”
    – Emmanuel Tsekleves, senior lecturer, University of Lancaster

    Right sources: blogs, tech news sites, tech magazines, the tech section of business sites, popular science books about technology, conferences, trade publications, and vendor announcements

    Quantity over quality: early research is not the time to dismiss ideas.

    Discuss with your peers: spark new and innovative ideas

    Insert a brief summary of how independent research is conducted in Section 2.1 of the Disruptive Technology Exploitation Plan Template.

    1.3.E (Cont.) Explore these sources to generate your disruptive technology longlist for the next meeting

    30 Minutes

    There are many sources of information on new and emerging technology. Use this list to kick-start your search.

    Connect with practitioners that are worth their weight in Reddit gold. Check out topic-based LinkedIn groups and subreddits such as r/sysadmin and r/tech. People experienced with technology frequent these groups.

    YouTube is for more than cat videos. Many vendors use YouTube for distributing their previous webinars. There are also videos showcasing various technologies that are uploaded by lecturers, geeks, researchers, and other technology enthusiasts.

    Test your reasonability. Check your “Think Like a Futurist” Tool

    Resolve

    Evaluate Disruptive Technologies

    PHASE 2

    Phase 2: Resolve

    Evaluate disrupted technologies

    Activities:

    Step 2.1: Create and Winnow a Longlist
    Step 2.2: Assess Shortlist

    Info-Tech Insight

    Long to short … that’s the short of it. Using SWOT, value readiness, and quadrant mapping review sessions will focus the longlist, creating a shortlist of potential PoC candidates to review and consider.

    This step involves the following participants:

    • Core working group
    • Infrastructure Management

    Outcomes of this step:

    • Finalized longlist
    • Finalized shortlist
    • Initial analysis of each technology on the shortlist

    Step 2.1

    Create and winnow a longlist

    Activities:

    1. Converge everyone’s longlists
    2. Narrow technologies from the longlist down to a shortlist using Info-Tech’s Disruptive Technology Shortlisting Tool
    3. Use the shortlisting tool to help participants visualize the potential
    4. Input the technologies on your longlist into the Disruptive Technology Shortlisting Tool to produce a shortlist

    This step involves the following participants:

    • Core working group members

    Outcomes of this step:

    • Finalized longlist
    • Finalized shortlist
    • Initial analysis of each technology on the shortlist

    2.1 Organize a meeting with the core working group to combine your longlists and create a shortlist

    1 hour

    Plan enough time to talk about each technology on the list. Each technology was included for a reason.

    • Start with the longlist. Review the longlist compiled at the initial meeting, and then have everyone present the lists that they independently researched.
    • Focus on the company’s context. Make sure that the working group analyzes these disruptive technologies in the context of the organization.
    • Start to compile the shortlist. Begin narrowing down the longlist by excluding technologies that are not relevant.

    Meeting Agenda (Sample)

    TimeActivity
    8:00am-9:30amConverge longlists
    9:30am-10:00amBreak
    10:00am-10:45amDiscuss tech in organizational context
    10:45am-11:15amBegin compiling the shortlist

    Disruptive Technology Exploitation Plan Template

    2.1.A Converge the longlists developed by your team

    90 minutes

    • Start with the longlist developed at the initial meeting. Write this list on the whiteboard.
    • If applicable, have a member present the longlist that was created in the last cycle. Remove technologies that:
      • Are no longer disruptive (e.g. have been implemented or rejected).
      • Have become foundational.
    • Eliminate redundancy: remove items that are very similar.
    • Have members “pitch” items on their lists:
      • Explain why their technologies will be disruptive (2-5 minutes maximum)
      • Add new technologies to the whiteboard
    • Record the following for metrics:
      • Each presented technology
      • Reasons the technology could be disruptive
      • Source of the information
    • Use Info-Tech’s Disruptive Technology Research Database Tool as a starting point.

    Insert the final longlist into Section 2.2 of your Disruptive Technology Exploitation Plan Template.

    Input

    • Longlist developed at first meeting
    • Independent research
    • Previous longlist

    Output

    • Finalized longlist

    Materials

    • Disruptive Technology Research Database Tool
    • Whiteboard and markers
    • Virtual whiteboard

    Participants

    • Core working group

    Review the list of processes that were brainstormed by the visionary group, and ask for input from others

    • IT innovation is most highly valued by the C-suite when it improves business processes, reduces costs, and improves core products and services.
    • By incorporating this insight into your working group’s analysis, you help to attract the attention of senior management and reinforce the group’s necessity.
    • Any input you can get from outside of IT will help your group understand how technology can be disruptive.
      • Visionaries consulted in Phase 1 are a great source for this insight.
    • The list of processes that they helped to brainstorm in Step 1.2 reflects processes that can be impacted by technology.
    • Info-Tech’s research has shown time and again that both CEOs and CIOs want IT to innovate around:
      • Improving business processes
      • Improving core products and services
      • Reducing costs

    Improved business processes

    80%

    Core product and service improvement

    48%

    Reduced costs

    48%

    Increased revenues

    23%

    Penetration into new markets

    21%

    N=364 CXOs & CIOs from the CEO-CIO Alignment Diagnostic Questions were asked on a 7-point scale of 1 = Not at all to 7 = Very strongly. Results are displayed as percentage of respondents selecting 6 or 7.

    Info-Tech Insight

    The disruptive tech team is prestigious. If your organization is large enough or has the resources, consider having this meeting in an offsite location. This will drive excitement to join the working group if the opportunity arises and incentivize good work.

    2.1.B Narrow technologies from the longlist down to a shortlist using Info-Tech’s Disruptive Technology Shortlisting Tool

    90 minutes

    To decide which technology has potential for your organization, have the working group or workshop participants evaluate each technology:

    1. Record each potentially disruptive technology in the longlist on a whiteboard.
    2. Making sure to carefully consider the meaning of the terms, have each member of the group evaluate each technology as “high” or “low” along each of the axes, innovation and transformation, on a piece of paper.
    3. The facilitator collects each piece of paper and inputs the results by technology into the Disruptive Technology Shortlisting Tool.
    Technology Innovation Transformation
    Conversational Commerce High High

    Insert the final shortlist into Section 2.2 of your Disruptive Technology Exploitation Plan Template.

    Input

    • Longlist
    • Futurist brainstorming

    Output

    • Shortlist

    Materials

    • Disruptive Technology Research Database Tool
    • Whiteboard and markers
    • Virtual whiteboard

    Participants

    • Core working group

    Disruptive technologies are innovative and transformational

    Innovation

    Transformation

    • Elements:
      • Creative solution to a problem that is relatively new on the scene.
      • It is different, counterintuitive, or insightful or has any combination of these qualities.
    • Questions to Ask:
      • How new is the technology?
      • How different is the technology?
      • Have you seen anything like it before? Is it counterintuitive?
      • Does it offer an insightful solution to a persistent problem?
    • Example:
      • The sharing economy: Today, simple platforms allow people to share rides and lodgings cheaply and have disrupted traditional services.
    • Elements:
      • Positive change to the business process.
      • Highly impactful: impacts a wide variety of roles in a company in a nontrivial way or impacts a smaller number of roles more significantly.
    • Questions to Ask:
      • Will this technology have a big impact on business operations?
      • Will it add substantial value? Will it change the structure of the company?
      • Will it impact a significant number of employees in the organization?
    • Example:
      • Flash memory improved storage technology incrementally by building on an existing foundation.

    Info-Tech Insight

    Technology can be transformational but not innovative. Not every new technology is disruptive. Even where technology has improved the efficiency of the business, if it does this in an incremental way, it might not be worth exploring using this storyboard.

    2.1.C Use the shortlisting tool to help participants visualize the potential

    1 hour

    Use the Disruptive Technology Shortlisting Tool, tabs 2 and 3.

    Assign quadrants

    • Input group members’ names and the entire longlist (up to 30 technologies) into tab 2 of the Disruptive Technology Shortlisting Tool.
    • On tab 3 of the Disruptive Technology Shortlisting Tool, input the quadrant number that corresponds to the innovation and transformation scores each participant has assigned to each technology.

    Note

    This is an assessment meant to serve as a guide. Use discretion when moving forward with a proof-of-concept project for any potentially disruptive technology.

    Participant Evaluation Quadrant
    High Innovation, High Transformation 1
    High Innovation, Low Transformation 2
    Low Innovation, Low Transformation 3
    Low Innovation, High Transformation 4

    four quadrants are depicted, labeled 1-4. The quadrants are coloured as follows: 1- green; 2- yellow; 3; red; 4; yellow

    2.1.D Use the Disruptive Technology Shortlisting Tool to produce a shortlist

    1 hour

    Use the Disruptive Technology Shortlisting Tool, tabs 3 and 4.

    Use the populated matrix and the discussion list to arrive at a shortlist of four to six potentially disruptive technologies.

    • The tool populates each quadrant based on how many votes it received in the voting exercise.
    • Technologies selected for a particular quadrant by a majority of participants are placed in the quadrant on the graph. Where there was no consensus, the technology is placed in the discussion list.
    • Technologies in the upper right quadrant – high transformation and high innovation – are more likely to be good candidates for a proof-of-concept project. Those in the bottom left are likely to be poor candidates, while those in the remaining quadrants are strong on one of the axes and are unlikely candidates for further systematic evaluation.

    This image contains a screenshot from tab 3 of the Disruptive Technology Shortlisting Tool.

    Input the results of the vote into tab 3 of the Disruptive Technology Shortlisting Tool.

    This image contains a screenshot from tab 4 of the Disruptive Technology Shortlisting Tool.

    View the results on tab 4.

    Phase 2: Resolve

    Evaluate disrupted technologies

    Activities:

    Step 2.1: Create and Winnow a Longlist
    Step 2.2:- Assess Shortlist

    This step involves the following participants:

    • Core working group
    • Infrastructure Management

    Outcomes of this step:

    • Finalized longlist
    • Finalized shortlist
    • Initial analysis of each technology on the shortlist

    Assess Shortlist

    Activities:

    1. Assess the value of each technology to your organization by breaking it down into quality and cost
    2. Investigate the overall readiness of the technologies on the shortlist
    3. Interpret each technology’s value score
    4. Conduct a SWOT analysis for each technology on the shortlist
    5. Use Info-Tech’s disruptive technology shortlist analysis to visualize the tool’s outputs
    6. Select the shortlisted technologies you would like to move forward with

    This step involves the following participants:

    • Core working group members
    • IT Management

    Outcomes of this step:

    • Finalized shortlist
    • Initial analysis of each technology on the shortlist

    2.2 Evaluate technologies based on their value and readiness, and conduct a SWOT analysis for each one

    Use the Disruptive Technology Value-Readiness and SWOT Analysis Tool

    • A technology monitor diagram prioritizes investment in technology by analyzing its readiness and value.
      • Readiness: how close the technology is to being practical and implementable in your industry and organization.
      • Value: how worthwhile the technology is, in terms of its quality and its cost.
    • Value and readiness questionnaires are included in the tool to help determine current and future values for each, and the next four slides explain the ratings further.
    • Categorize technology by its value-readiness score, and evaluate how much potential value each technology has and how soon your company can realize that value.
    • Use a SWOT analysis to qualitatively evaluate the potential that each technology has for your organization in each of the four categories (strengths, weaknesses, opportunities, and threats).

    The technology monitor diagram appears in tab 9 of the Disruptive Technology Value-Readiness and SWOT Analysis Tool

    This image depicts tab 9 of the Disruptive Technology Value-Readiness and SWOT Analysis Tool

    2.2.A Assess the value of each technology to your organization by breaking it down into quality and cost

    1 hour

    Update the Disruptive Technology Value-Readiness and SWOT Analysis Tool, tab 4.

    Populate the chart to produce a score for each technology’s overall value to the company conceptualized as the interaction of quality and cost.

    Overall Value

    Quality Cost

    Each technology, if it has a product associated with it, can be evaluated along eight dimensions of quality. Consider how well the product performs, its features, its reliability, its conformance, its durability, its serviceability, its aesthetics, and its perceived quality.

    IT budgets are broken down into capital and operating expenditures. A technology that requires a significant investment along either of these lines is unlikely to produce a positive return. Also consider how much time it will take to implement and operate each technology.

    The value assessment is part of the Disruptive Technology Value-Readiness and SWOT Analysis Tool

    This image contains a screenshot from tab 4 of the Disruptive Technology Value-Readiness and SWOT Analysis Tool.

    Info-Tech Insight

    Watch your costs: Technology that seems cheap at first can actually be expensive over time. Be sure to account for operational and opportunity costs as well.

    2.2.B Investigate the overall readiness of the technologies on the shortlist

    1 hour

    Update the Disruptive Technology Value-Readiness and SWOT Analysis Tool, tab 4.

    Overall Readiness

    Age

    How much time has the technology had to mature? Older technology is more likely to be ready for adoption.

    Venture Capital

    The amount of venture capital gathered by important firms in the space is an indicator of market faith.

    Market Size

    How big is the market for the technology? It is more difficult to break into a giant market than a niche market.

    Market Players

    Have any established vendors (Microsoft, Facebook, Google, etc.) thrown their weight behind the technology?

    Fragmentation

    A large number of small companies in the space indicates that the market has yet to reach equilibrium.

    The readiness assessment is part of the Disruptive Technology Value-Readiness and SWOT Analysis Tool

    This image contains a screenshot of the Readiness Scoring tab of the Disruptive Technology Value-Readiness and SWOT Analysis Tool.

    Use a variety of sources to populate the chart

    Google is your friend: search each shortlisted technology to find details about its development and important vendors.

    Websites like Crunchbase, VentureBeat, and Mashable are useful sources for information on the companies involved in a space and the amount of money they have each raised.

    2.2.C Interpret each technology’s value score

    1 hour

    Insert the result of the SWOT analysis into tab 7 of Info-Tech’s Disruptive Technology Value-Readiness and SWOT Analysis Tool.

    Visualize the results of the quality-cost analysis

    • Quality and cost are independently significant; it is essential to understand how each technology stacks up on the axes.
    • Use tab 6 of the Disruptive Technology Value-Readiness and SWOT Analysis Tool for an illustration of how quality and cost interact to produce each technology’s final position on the tech monitor graph.
    • Remember: the score is notional and reflects the values that you have assigned. Be sure to treat it accordingly.

    This image contains a screenshot of the Value Analysis tab of the Disruptive Technology Value-Readiness and SWOT Analysis Tool

    Green represents a technology that scores extremely high on one axis or the other, or quite high on both. These technologies are the best candidates for proof-of-concept projects from a value perspective.

    Red represents a technology that has scored very low on both axes. These technologies will be expensive, time consuming, and of poor quality.

    Yellow represents the fuzzy middle ground. These technologies score moderately on both axes. Be especially careful when considering the SWOT analysis of these technologies.

    2.2.D Conduct a SWOT analysis for each technology on the shortlist

    1 hour

    Use tab 6 of the Disruptive Technology Value-Readiness and SWOT Analysis Tool.

    A formal process for analyzing disruptive technology is the only way to ensure that it is taken seriously.

    Write each technology as a heading on a whiteboard. Spend 10-15 minutes on each technology conducting a SWOT analysis together.

    Consider four categories for each technology:

    • Strengths: Current uses of the technology or supporting technology and ways in which it helps your organization.
    • Weaknesses: Current limitations of the technology and challenges or barriers to adopting it in your organization.
    • Opportunities: Potential uses of the technology, especially as it advances or improves.
    • Threats: Potential negative disruptions resulting from the technology, especially as it advances or improves.

    The list of processes generated at the cycle’s initial meeting is a great source for opportunities and threats.

    Disruptive Technology Value-Readiness and SWOT Analysis Tool

    This image contains screenshots of the technology tab of the Disruptive Technology Value-Readiness and SWOT Analysis Tool.

    2.2.E Use Info-Tech’s disruptive technology shortlist analysis to visualize the tool’s outputs

    1 hour

    Disruptive Technology Value-Readiness and SWOT Analysis Tool, tab 9

    The tool’s final tab displays the results of the value-readiness analysis and the SWOT analysis in a single location.

    This image contains a screenshot from tab 9 of the Disruptive Technology Value-Readiness and SWOT Analysis Tool

    Insert the shortlist analysis report into Section 3 of your Disruptive Technology Exploitation Plan Template.

    2.2.F Select the shortlisted technologies you would like to move forward with

    1 hour

    Present your findings to the working group.

    • The Disruptive Technology Value-Readiness and SWOT Analysis Tool aggregates your inputs in an easy-to-read, consistent way.
    • Present the tool’s outputs to members of the core working group.
    • Explain the scoring and present the graphic to the group. Go over each technology’s strengths and weaknesses as well as the opportunities and threats it presents/poses to the organization.
    • Go through the proof-of-concept planning phase before striking any technologies from the list.

    This image contains a screenshot of the disruptive technology shortlist analysis from the Disruptive Technology Value-Readiness and SWOT Analysis Tool

    Info-Tech Insight

    A technology’s exceptional value and immediate usability make it the best. A technology can be promising and compelling, but it is unsuitable unless it can bring immediate and exceptional value to your organization. Don’t get caught up in the hype.

    Evaluate

    Create an Action Plan to Exploit Disruptive Technologies

    PHASE 3

    Phase 3: Evaluate

    Create an Action Plan to Exploit Disruptive Technologies

    Activities:

    Step 3.1: Create Process Maps
    Step 3.2: Develop Proof of Concept Charter

    This step involves the following participants:

    • Core working group
    • Infrastructure Management
    • Working group leader
    • CIO

    Outcomes of this step:

    • Business process maps before and after disruption
    • Proof of concept charter
    • Key performance indicators
    • Estimation of required resources

    Step 3.1

    Create Process Maps

    Activities:

    1. Creating a problem canvas by identifying stakeholders, jobs, pains, and gains
    2. Clarify the problem the proof-of-concept project will solve
    3. Identify jobs and stakeholders
    4. Outline how disruptive technology will solve the problem
    5. Map business processes
    6. Identify affected business units
    7. Outline and map the business processes likely to be disrupted
    8. Recognize how the new technology will impact business processes
    9. Make the case: Outline why the new business process is superior to the old

    This step involves the following participants:

    • Working group leader
    • CIO

    Outcomes of this step:

    • Business process maps before and after disruption

    3.1 Create an action plan to exploit disruptive technologies

    Clarify the problem in order to make the case. Fill in section 1.1 of Info-Tech’s Proof of Concept Template to clearly outline the problem each proof of concept is designed to solve.

    Establish roles and responsibilities. Use section 1.2 of the template to outline the roles and responsibilities that fall to each member of the team. Ensure that clear lines of authority are delineated and that the list of stakeholders is exhaustive: include the executives whose input will be required for project approval, all the way to the technicians on the frontline responsible for implementing it.

    Outline the solution to the problem. Demonstrate how each proof-of-concept project provides a solution to the problem outlined in section 1.1. Be sure to clarify what makes the particular technology under investigation a potential solution and record the results in section 1.3.

    This image contains a screenshot of the Proof of concept project template

    Use the Proof of Concept Project Template to track the information you gather throughout Phase 3.

    3.1.A Creating a problem canvas by identifying stakeholders, jobs, pains, and gains

    2 hours

    Instructions:

    1. On a whiteboard, draw the visual canvas supplied below.
    2. Select your issue area, and list jobs, pains, and gains in the associated sections.
    3. Record the pains, jobs, and gains in sections 1.1-1.3 of the Proof of Concept Template.

    Gains

    1. More revenue

    2. Job security

    3. ……

    Jobs

    1. Moving product

    2. Per sale value

    3. ……

    Pains

    1. Clunky website

    2. Bad site navigation

    3. ……

    Input

    • Inspiration
    • Anonymous ideas

    Output

    • List of processes

    Materials

    • Chart paper and markers
    • Pen and paper

    Participants

    • Core working group
    • Visionaries

    3.1.B Clarify the problem the proof-of-concept project will solve

    2 hours

    What is the problem?

    • Every technology is designed to solve a problem faced by somebody somewhere. For each technology that your team has decided to move forward with, identify and clearly state the problem it would solve.
    • A clear problem statement is a crucial part of a new technology’s business case. It is impossible to earn buy-in from the rest of the organization without demonstrating the necessity of a solution.
    • Perfection is impossible to achieve: during the course of their work, everyone encounters pain points. Identify those pain points to arrive at the problem that needs to be solved.

    Example:

    List of pains addressed by conversational commerce:

    • Search functions can be clunky and unresponsive.
    • Corporate websites can be difficult to navigate.
    • Customers are uncomfortable in unfamiliar internet environments.
    • Customers do not like waiting in a long queue to engage with customer service representatives when they have concerns.

    “If I were given one hour to solve a problem, I would spend 59 minutes defining the problem and one minute resolving it.”
    – Albert Einstein

    Input the results of this exercise into Section 1.1 of the Proof of Concept Template.

    3.1.C Identify jobs and stakeholders

    1 hour

    Jobs

    Job: Anything that the “customer” (the target of the solution) needs to get done but that is complicated by a pain.

    Examples:
    The job of the conversational commerce interface is to make selling products easier for the company.
    From the customer perspective, the job of the conversational interface is to make the act of purchasing a product simpler and easier.

    Stakeholders

    Stakeholder: Anyone who is impacted by the new technology and who will end up using, approving, or implementing it.

    Examples:
    The executive is responsible for changing the company’s direction and approving investment in a new sales platform.
    The IT team is responsible for implementing the new technology.
    Marketing will be responsible for selling the change to customers.
    Customers, the end users, will be the ones using the conversational commerce user interface.

    Input the results of this exercise into Section 1.2 of the Proof of Concept Template.

    Info-Tech Insight

    Process deconstruction reveals strengths and weaknesses. Promising technology should improve stakeholders’ abilities to do jobs.

    3.1.D Outline how disruptive technology will solve the problem

    1 hour

    How will the technology in question make jobs easier?

    • How will the disruptive technology you have elected to move forward with create gains for the organization?
    • First, identify the gains that are supposed to come with the project. Consider the benefits that the various stakeholders expect to derive from the jobs identified.
    • Second, make note of how the technology in question facilitates the gains you have noted. Be sure to articulate the exclusive features of the new technology that make it an improvement over the current state.

    Note: The goal of this exercise is to make the case for a particular technology. Sell it!

    Expected Gain: Increase in sales.

    Conversational Commerce’s Contribution: Customers are more likely to purchase products using interfaces they are comfortable with.

    Expected Gain: Decrease in costs.

    Conversational Commerce’s Contribution: Customers who are satisfied with the conversational interface are less likely to interact with live agents, saving labor costs.

    Input the results of this exercise into Section 1.3 of the Proof of Concept Template.

    3.1.E Map business processes

    1 hour

    Map the specific business processes the new technology will impact.

    • Disruptive technologies will impact a wide variety of business processes.
    • Map business processes to visualize what parts of your organization (departments, silos, divisions) will be impacted by the new technology, should it be adopted after the proof of concept.
    • Identify how the disruption will take place.
    • Demonstrate the value of each technology by including the results of the Disruptive Technology Value-Readiness and SWOT Analysis Tool with your process map.

    This image contains a screenshot of the Proof of concept project template

    Use the Proof of Concept Project Template to track the information you gather throughout Phase 3.

    3.1.F Identify affected business units

    30 minutes per technology

    Disruptive technology will impact business units.

    • Using the stakeholders identified earlier in the project, map each technology to the business units that will be affected.
    • Make your list exhaustive. While some technologies will have a limited impact on the business as a whole, others will have ripple effects throughout the organization.
    • Examine affected units at all scales: How will the technology impact operations at the team level? The department level? The division level?

    “The disruption is not just in the technology. Sometimes a good business model can be the disruptor.”
    – Jason Hong, Associate Professor, Carnegie Mellon

    Example:

    • Customer service teams: Conversational commerce will replace some of the duties of the customer service representative. They will have to reorganize to account for this development.
    • IT department: The IT department will be responsible for building/maintaining the conversational interface (or, more likely, they will be responsible for managing the contract with the vendor).
    • Sales analytics: New data from customers in natural language might provide a unique opportunity for the analytics team to develop new initiatives to drive sales growth.

    Input the results of this exercise into Section 2.1 of the Proof of Concept Template.

    3.1.G Outline and map the business processes likely to be disrupted

    15 minutes per technology

    Leverage the insights of the diverse working group.

    • Processes are designed to transform inputs into outputs. All business activities can be mapped into processes.
    • A process map illustrates the sequence of actions and decisions that transform an input into an output.
    • Effective mapping gives managers an “aerial” view of the company’s processes, making it easier to identify inefficiencies, reduce waste, and ultimately, streamline operations.
    • To identify business processes, have group members familiar with the affected business units identify how jobs are typically accomplished within those units.

    “To truly understand a business process, we need information from both the top-down and bottom-up points of view. Informants higher in the organizational hierarchy with a strategic focus are less likely to know process details or problems. But they might advocate and clearly articulate an end-to-end, customer-oriented philosophy that describes the process in an idealized form. Conversely, the salespeople, customer service representatives, order processors, shipping clerks, and others who actually carry out the processes will be experts about the processes, their associated documents, and problems or exception cases they encounter.”
    – Robert J. Glushko, Professor at UC Berkeley and Tim McGrath, Business Consultant

    Info-Tech Insight

    Opinions gathered from a group that reflect the process in question are far more likely to align with your organization’s reality. If you have any questions about a particular process, do not be afraid to go outside of the working group to ask someone who might know.

    3.1.G Outline and map the business processes likely to be disrupted (continued)

    15 minutes per technology

    Create a simple diagram of identified processes.

    • Use different shapes to identify different points in the process.
    • Rectangles represent actions, diamonds represent decisions.
    • On a whiteboard, map out the actions and decisions that take place to transform an input into an output.
    • Input the result into section 2.2 of the Proof of Concept Template.

    This image contains a screenshot of the Software Service Cross-Function Process tab from Edraw Visualization Solutions.

    Source: Edraw Visualization Solutions

    Example: simplified process map

    1. User: visits company website
    2. User: engages search function or browses links
    3. User: selects and purchases product from a menu
    4. Company: ships product to customer

    3.1.H Recognize how the new technology will impact business processes

    15 minutes per technology

    Using the information gleaned from the previous activities, develop a new process map that takes the new technology into account.

    Identify the new actions or decisions that the new technology will affect.

    User: visits company website; User: engages conversational; commerce platform; User: engages search function or browses links; User: makes a natural language query; User: selects and purchases product from a menu</p data-verified=

    User: selects and purchases product from a menu; Company: ships product to customer; Company: ships product to customer">

    Info-Tech Insight

    It’s ok to fail! The only way to know you’re getting close to the “knee of curve" is from multiple failed PoC tests. The more PoC options you have, the more likely it will be that you will have two to three successful results.

    3.1.I Make the case: Outline why the new business process is superior to the old

    15 minutes per technology

    Articulate the main benefits of the new process.

    • Using the revised process map, make the case for each new action.
    • Questions to consider: How does the new technology relieve end-user/customer pains? How does the new technology contribute to the streamlining of the business process? Who will benefit from the new action? What are the implications of those benefits?
    • Record the results of this exercise in section 2.4 of the Proof of Concept Template.

    This image contains an example of an outline comparing the benefits of new and the old business processes.

    Info-Tech Insight

    If you cannot articulate how a new technology will benefit a business process, reconsider moving forward with the proof-of-concept project.

    Phase 3: Evaluate

    Create an Action Plan to Exploit Disruptive Technologies

    Activities:

    Step 3.1: Create Process Maps
    Step 3.2: Develop Proof of Concept Charter

    Develop Proof of Concept Charter

    This step involves the following participants:

    • Core working group
    • Infrastructure Management
    • Working group leader
    • CIO

    Outcomes of this step:

    • Business process maps before and after disruption
    • Proof of concept charter
    • Key performance indicators
    • Estimation of required resources

    Step 3.2

    Develop Proof of Concept Charter

    Activities:

    1. Use SMART success metrics to define your objectives
    2. Develop key performance indicators (KPIs)
    3. Identify key success factors for the project
    4. Outline the project’s scope
    5. Identify the structure of the team responsible for the proof-of-concept project
    6. Estimate the resources required by the project
    7. Be aware of common IT project concerns
    8. Communicate your working group’s findings and successes to a wide audience
    9. Hand off the completed proof-of-concept project plan
    10. Disruption is constant: Repeat the evaluation process regularly to protect the business

    This step involves the following participants:

    • Working group leader
    • CIO

    Outcomes of this step:

    • Proof of concept charter
    • Key performance indicators
    • Estimation of required resources

    3.2 Develop a proof of concept charter

    Keep your proof of concept on track by defining five key dimensions.

    1. Objective: Giving an overview of the planned proof of concept will help to focus and clarify the rest of this section. What must the proof of concept achieve? Objectives should be: specific, measurable, attainable, relevant, and time bound. Outline and track key performance indicators.
    2. Key Success Factors: These are conditions that will positively impact the proof of concept’s success.
    3. Scope: High-level statement of scope. More specifically, state what is in scope and what is out of scope.
    4. Project Team: Identify the team’s structure, e.g. sponsors, subject-matter experts.
    5. Resource Estimation: Identify what resources (time, materials, space, tools, expertise, etc.) will be needed to build and socialize your prototype. How will they be secured?

    Input the results of this exercise into Section 3.0 of the Proof of Concept Template.

    3.2.A Use SMART success metrics to define your objectives

    Specific

    Measurable

    Actionable

    Realistic

    Time Bound

    Make sure the objective is clear and detailed.

    Objectives are measurable if there are specific metrics assigned to measure success. Metrics should be objective.

    Objectives become actionable when specific initiatives designed to achieve the objective are identified.

    Objectives must be achievable given your current resources or known available resources.

    An objective without a timeline can be put off indefinitely. Furthermore, measuring success is challenging without a timeline.

    Who, what, where, why?

    How will you measure the extent to which the goal is met?

    What is the action-oriented verb?

    Is this within my capabilities?

    By when: deadline, frequency?

    Examples:

    1. Increase in sales by $40,000 per month by the end of next quarter.
    2. Immediate increase in web traffic by 600 unique page views per day.
    3. Number of pilots approved per year.
    4. Number of successfully deployed solutions per year.

    Input the results of this exercise into Section 3.0 of the Proof of Concept Template.

    3.2.B Develop key performance indicators (KPIs)

    30 minutes per technology

    Key performance indicators allow for rigorous analysis, which generates insight into utilization by platform and consumption by business activity.

    • Use the process improvements identified in step 3.1 to brainstorm metrics that indicate when process improvement is actually taking place.
    • Have members of the group pitch KPIs; the facilitator should record each suggestion on a whiteboard.
    • Make sure to have everyone justify the inclusion of each metric: How does it relate to the improvement that the proof of concept project is intended to drive? How does it relate to the overall goals of the business?
    • Include a list of KPIs, along with a description and a target (ensuring that it aligns with SMART metrics) in section 3.1 of the Proof of Concept Template.

    “An estimated 70% of performance measurement systems fail after implementation. Carefully select your KPIs and avoid this trap!”
    Source: Collins et al. 2016

    Key Performance Indicator Description Target

    Result

    Conversion rate What percentage of customers who visit the site/open the conversational interface continue on to make a purchase? 40%
    Average order value

    How much does each customer spend per visit to the website?

    $212
    Repeat customer rate What percentage of customers have made more than one purchase over time? 65%
    Lifetime customer value Over the course of their interaction with the company, what is the typical value each customer brings? $1566

    Input the results of this exercise into Section 3.1 of the Proof of Concept Template.

    3.2.C Identify key success factors for the project

    30 minutes per technology

    Effective project management involves optimizing four key success factors (Clarke, 1999)

    • Communication: Communicate the expected changes to stakeholders, making sure that everyone who needs to know does know. Example: Make sure customer service representatives know their duties will be impacted by the conversational UI well before the proof-of-concept project begins.
    • Clarity: All involved in the project should be apprised of what the project is intended to accomplish and what the project is not intended to accomplish. Example: The conversational commerce project is not intended to be rolled out to the entire customer base all at once; it is not intended to disrupt normal online sales.
    • Compartmentalization: The working group should suggest some ways that the project can be broken down to facilitate its effective implementation. Example: Sales provides details of customers who might be amenable to a trial, IT secures a vendor, customer service writes a script.
    • Flexibility: The working group’s final output should not be treated as gospel. Ensure that the document can be altered to account for unexpected events. Example: The conversational commerce platform might drive sales of a particular product more than others, necessitating adjustments at the warehouse and shipping level.

    Input the results of this exercise into Section 3.0 of the Proof of Concept Template.

    3.2.D Outline the project’s scope

    10 minutes per technology

    Create a high-level outline of the project’s scope.

    • Questions to consider: Broadly speaking, what are the project’s goals? What is the desired future state? Where in the company will the project be rolled out? What are some of the company’s goals that the project is not designed to cover?
    • Be sure to avoid scope creep! Remember: The goal of the proof-of-concept project is to produce a minimum case for viability in a carefully defined area. Reserve a detailed accounting of costs and benefits for the post-proof-of-concept stage.
    • Example: The conversational user interface will only be rolled out in an e-commerce setting. Other business units (HR, for example) are beyond the scope of this particular project.

    “Although scope creep is not the only nemesis a project can have, it does tend to have the farthest reach. Without a properly defined project and/or allowing numerous changes along the way, a project can easily go over budget, miss the deadline, and wreak havoc on project success.”
    – University Alliance, Villanova University

    Input the results of this exercise into Section 3.0 of the Proof of Concept Template.

    3.2.E Identify the structure of the team responsible for the proof-of-concept project

    10 minutes per technology

    Brainstorm who will be involved in project implementation.

    • Refer back to the list of stakeholders identified in 3.1.a. Which stakeholders should be involved in implementing the proof-of-concept plan?
    • What business units do they represent?
    • Who should be accountable for the project? At a high level, sketch the roles of each of the participants. Who will be responsible for doing the work? Who will approve it? Who needs to be informed at every stage? Who are the company’s internal subject matter experts?

    Example

    Name/Title Role
    IT Manager Negotiate the contract for the software with vendor
    CMO Promote the conversational interface to customers

    Input the results of this exercise into Section 3.0 of the Proof of Concept Template.

    3.2.F Estimate the resources required by the project

    10 minutes per technology

    Time and Money

    • Recall: Costs can be operational, capital, or opportunity.
    • Revisit the Disruptive Technology Value-Readiness and SWOT Analysis Tool. Record the capital and operational expenses expected to be associated with each technology, and add detail where possible (use exact figures from particular vendors instead of percentages).
    • Write the names and titles of each expected participant in the project on a whiteboard. Next to each name, write the number of hours they are expected to devote to the project and include a rough estimate of the cost of their participation to the company. Use full-time employee equivalent (FTE measures) as a base.
    • Outline how other necessary resources (space, tools, expertise, etc.) will be secured.

    Example: Conversational Commerce

    • OpEx: $149/month + 2.9¢/transaction* (2,000 estimated transactions)
    • CapEx: $0!
    • IT Manager: 5 hours at $100/hour
    • IT Technician: 40 hours at $45/hour
    • CMO: 1 hour at $300/hour
    • Customer Service Representative: 10 hours at $35/hour
    • *Estimated total cost for a one-month proof-of-concept project: $3,157

    *This number is a sample taken from the vendor Rhombus

    Input the results of this exercise into Section 3.0 of the Proof of Concept Template.

    3.2.G Be aware of common IT project concerns

    Of projects that did not meet business expectations or were cancelled, how significant were the following issues?

    A bar graph is depicted, comparing small, medium, and large businesses for the following datasets: Over budget; Project failed to be delivered on time; Breach of scope; Low quality; Failed to deliver expected benefit or value

    This survey data did not specifically address innovation projects.

    • Disruptive technology projects will be under increased scrutiny in comparison to other projects.
    • Be sure to meet deadlines and stay within budget.
    • Be cognizant that your projects can go out of scope, and there will be projects that may have to be cancelled due to low quality. Remember: Even a failed test is a learning opportunity!

    Info-Tech’s CIO-CEO Alignment Survey, N=225

    Organization size was determined by the number of IT employees within the organization

    Small = 10 or fewer IT staff, medium = 11 to 25 IT staff, and large/enterprise = 26 or greater IT staff

    3.2.H Communicate your working group’s findings and successes to a wide audience

    Advertise the group’s successes and help prevent airline magazine syndrome from occurring.

    • Share your group’s results internally:
      • Run your own analysis by senior management and then share it across the organization.
      • Maintain a list of technologies that the working group has analyzed and solicit feedback from the wider organization.
      • Post summaries of the technologies in a publicly available repository. The C-suite may not read it right away, but it will be easy to provide when they ask.
      • If senior management has declined to proceed with a certain technology, avoid wasting time and resources on it. However, include notes about why the technology was rejected.
    • These postings will also act as an advertisement for the group. Use the garnered interest to attract visionaries for the next cycle.
    • These postings will help to reiterate the innovative value of the IT department and help bring you to the decision-making table.

    “Some CIOs will have to battle the bias that they belong in the back office and shouldn’t be included in product architecture planning. CIOs must ‘sell’ IT’s strength in information architecture.”
    – Chris Curran, Chief Technologist, PwC (Curran, 2014)

    Info-Tech Insight

    Cast a wide net. By sharing your results with as many people as possible within your organization, you’ll not only attract more attention to your working group, but you will also get more feedback and ideas.

    3.2.I Hand off the completed proof-of-concept project plan

    The proof of concept template is filled out – now what?

    • The core working group is responsible for producing a vision of the future and outlining new technology’s disruptive potential. The actual implementation of the proof of concept (purchasing the hardware, negotiating the SLA with the vendor) is beyond the working group’s responsibilities.
    • If the proof of concept goes ahead, the facilitator should block some time to evaluate the completed project against the key performance indicators identified in the initial plan.
    • A cure for airline magazine syndrome: Be prepared when executives ask about new technology. Present them with the results of the shortlist analysis and the proof-of-concept plan. A clear accounting of the value, readiness, strengths, weaknesses, opportunities, and threats posed by each technology, along with its impact on business processes, is an invaluable weapon against poor technology choices.

    Use section 3.2.b to identify the decision-making stakeholder who has the most to gain from a successful proof-of-concept project. Self-interest is a powerful motivator – the project is more likely to succeed in the hands of a passionate champion.

    Info-Tech Insight

    Set a date for the first meeting of the new iteration of the disruptive technology working group before the last meeting is done. Don’t risk pushing it back indefinitely.

    3.2.J Hand off the completed proof-of-concept project plan

    Record the results of the proof of concept. Keep track of what worked and what didn’t.

    Repeat the process regularly.

    • Finalize the proof of concept template, but don’t stop there: Keep your ear to the ground; follow tech developments using the sources identified in step 1.2.
    • Continue expanding the potential longlist with independent research: Be prepared to expand your longlist. Remember, the more technologies you have on the longlist, the more potential airline magazine syndrome cures you have access to.
    • Have the results of the previous session’s proof of concept plan on hand: At the start of each new iteration, conduct a review. What technologies were successful beyond the proof of concept phase? Which parts of the process worked? Which parts did not? How could they be improved?

    Info-Tech Insight

    The key is in anticipation. This is not a one-and-done exercise. Technology innovation operates at a faster pace than ever before, well below the Moores Law "18 month" timeline as an example. Success is in making EDIT a repeatable process.

    Related Info-Tech Research

    Define Your Digital Business Strategy
    After a major crisis, find your place in the digital economy.

    Develop a Project Portfolio Management Strategy
    Drive project throughput by throttling resource capacity.

    Adopt Design Thinking in Your Organization
    Innovation needs design thinking.

    Digital Maturity Improvement Service
    Prepare your organization for digital transformation – or risk falling behind.

    Research contributors and experts

    Nitin Babel

    Nitin Babel, Co-Founder, niki.ai

    Nitin Babel, MSc, co-created conversational commerce platform niki.ai in early 2015. Since then, the technology has been featured on the front page of the Economic Times, and has secured the backing of Ratan Tata, former chairman of the Tata Group, one of the largest companies in the world.

    Mark Hubbard

    Mark Hubbard, Senior Vice President, FirstOnSite

    Mark is the SVP for Information Technology in Canada with FirstOnSite, a full service disaster recovery and property restoration company. Mark has over 25 years of technology leadership guiding global organizations through the development of strategic and tactical plans to strengthen their technology platforms and implement business aligned technology strategies.

    Chris Green

    Chris Green, Enterprise Architect, Boston Private
    Chris is an IT architect with over 15 years’ experience designing, building, and implementing solutions. He is a results-driven leader and contributor, skilled in a broad set of methods, tools, and platforms. He is experienced with mobile, web, enterprise application integration, business process, and data design.

    Andrew Kope

    Andrew Kope, Head of Data Analytics
    Big Blue Bubble
    Andrew Kope, MSc, oversees a team that develops and maintains a user acquisition tracking solution and a real-time metrics dashboard. He also provides actionable recommendations to the executive leadership of Big Blue Bubble – one of Canada’s largest independent mobile game development studios.

    Jason Hong

    Jason Hong, Associate Professor, School of Computer Science, Human-Computer Interaction Institute, Carnegie Mellon University

    Jason Hong is a member of the faculty at Carnegie Mellon’s School of Computer Science. His research focus lies at the intersection of human-computer interaction, privacy and security, and systems. He is a New America National Cyber Security Fellow (2015-2017) and is widely published in academic and industry journals.

    Tim Lalonde

    Tim Lalonde, Vice President, Mid-Range

    Tim Lalonde is the VP of Technical Operations at Mid-Range. He works with leading-edge companies to be more competitive and effective in their industries. He specializes in developing business roadmaps leveraging technology that create and support change from within — with a focus on business process re-engineering, architecture and design, business case development and problem-solving. With over 30 years of experience in IT, Tim’s guiding principle remains simple: See a problem, fix a problem.

    Jon Mavor

    Jon Mavor, Co-Founder and CTO, Envelop VR
    Jon Mavor is a programmer and entrepreneur, whose past work includes writing the graphics engine for the PC game Total Annihilation. As Chief Technology Officer of Envelop VR, a virtual reality start-up focused on software for the enterprise, Jon has overseen the launch of Envelop for Windows’s first public beta.

    Dan Pitt

    Dan Pitt, President, Palo Alto Innovation Advisors
    Dan Pitt is a network architect who has extensive experience in both the academy and industry. Over the course of his career, Dan has served as Executive Director of the Open Networking Foundation, Dean of Engineering at Santa Clara University, Vice President of Technology and Academic Partnerships at Nortel, Vice President of the Architecture Lab at Bay Networks, and, currently, as President of Palo Alto Innovation Advisors, where he advises and serves as an executive for technology start-ups in the Palo Alto area and around the world.

    Courtney Smith

    Courtney Smith, Co-Founder, Executive Creative Director
    PureMatter

    Courtney Smith is an accomplished creative strategist, storyteller, writer, and designer. Under her leadership, PureMatter has earned hundreds of creative awards and been featured in the PRINT International Design Annual. Courtney has juried over 30 creative competitions, including Creativity International. She is an invited member of the Academy of Interactive and Visual Arts.

    Emmanuel Tsekleves

    Emmanuel Tsekleves, Senior Lecturer in Design Interactions, University of Lancaster
    Dr. Emmanuel Tsekleves is a senior lecturer and writer based out of the United Kingdom. Emmanuel designs interactions between people, places, and products by forging creative design methods along with digital technology. His design-led research in the areas of health, ageing, well-being, and defence has generated public interest and attracted media attention by the national press, such as the Daily Mail, Daily Mirror, The Times, the Daily Mail, Discovery News, and several other international online media outlets.

    Bibliography

    Airini Ab Rahman. “Emerging Technologies with Emerging Effects; A Review”. Universiti Teknologi Malaysia. PERINTIS eJournal, June 2017. Web.

    Anthony, Scott. “Kodak’s Downfall Wasn’t About Technology.” Harvard Business Review, 15 July 2016. Web.

    ARM. The Intelligent Flexible Cloud. 26 Feb. 2015. Web.

    Association of Computing Machinery. Communications of the ACM, n.d. Web.

    Barnett, Thomas. “Three Mobile Trends to Watch.” Cisco Blogs, 3 Feb. 2015. Web.

    Batelle, John. “The 70 Percent Solution.” CNN, 1 Dec 2005. Web.

    Booz Allen Hamilton. Managing Technological Change: 7 Ways to Talk Tech with Management, n.d. Web.

    Brynjolfsson, Erik, and Andrew McAfee. The Second Machine Age: Work, Progress, and Prosperity in a Time of Brilliant Technologies. W. W. Norton, 2014. Print.

    Christensen, Clayton M. “What is Disruptive Innovation?” Harvard Business Review, Dec 2015. Web.

    Christensen, Clayton M. and James Euchner. “Managing Disruption: An Interview With Clayton Christensen.” Research-Technology Management, 22 Dec 2015. vol. 54, no. 1. Web.

    Christensen, Clayton M., Rory McDonald, and Elizabeth J. Altman. “Disruptive Innovation: An Intellectual History and Directions for Future Research”. Wiley Online Library. Web.

    Christensen, Clayton M., Taddy Hall, Karen Dillon, and David S. Duncan. “Know Your Customers’ Jobs to be Done.” Harvard Business Review, Sept. 2016. Web.

    Cisco. “Cisco Annual Internet Report.” n.d. Web.

    Cisco. Cisco Visual Networking Index: Forecast and Methodology, 2014-2019, 27 May 2015. Web.

    Clark, Steven. “Elon Musk hopes SpaceX will send humans to Mars in 2024.” Spaceflight Now, 2 June 2016. Web.

    Clarke, Angela. “A practical use of key success factors to improve the effectiveness of project management,” International Journal of Project Management, June 1999 (17): 139-145.

    Collins, Andrew L., Patrick Hester, Barry Ezell, and John Horst. “An improvement selection methodology for key performance indicators.” Environmental Systems and Decisions, June 2016, 36 (2): 196-208.

    Computer Sciences Corporation. CSC Global CIO Survey: 2014-2015: CIOs Emerge as Disruptive Innovators: An Annual Barometer of Global CIOs’ Plans, Priorities, Threats, and Opportunities, 2014. Web.

    Constine, John. “Voice is Chat’s Next Battleground.” TechCrunch, 19 Sept. 2016. Web.

    Cressman, Daryl. “Disruptive Innovation and the Idea of Technology”. Maastricht University, June 2019. Web.

    Crown Prosecution Service. A Guide to Process Mapping and Improvement. n.d. Web.

    Curran, Chris. “The CIO’s Role in the Internet of Things.” PwC, 13 Mar. 2014. Web.

    Darbha, Sheta, Mike Shevenell, and Jason Normandin. “Impact of Software-Defined Networking on Infrastructure Management.” CA Technology Exchange, 4.3, Nov. 2013, pp. 33-43. Web.

    Denecken, Sven. Conquering Disruption Through Digital Transformation: Technologies, Leadership Strategies, and Best Practices to Create Opportunities for Innovation. SAP, 2014. Web.

    DHL Trend Research and Cisco Consulting Services. Internet of Things in Logistics: A Collaborative Report by DHL and Cisco on Implications and Use Cases for the Logistics Industry, 2015. Web.

    Dirican, Cüneyt. “The Impacts of Robotics, Artificial Intelligence on Business and Economics.” Procedia: Social and Behavioral Sciences, vol. 195, 2015, pp. 564-573. Web.

    Edraw Visualization Solutions. Examples of Flowcharts, Org Charts and More. “Cross-Function Flowchart Examples – Service Flowchart.”

    Emerson. Data Center 2025: Exploring the Possibilities, 2014. Web.

    Ericsson. Next-Generation Data Center Infrastructure, Feb. 2015. Web.

    Eurotech. Connecting M2M Applications to the Cloud to Bolster Hardware Sales, 2014. Web.

    Evans Gary, Llewellyn. “Disruptive Technology and the Board: The Tip of the Iceberg”. Economics and Business Review, n.d. Web.

    Evans Gary, Llewellyn. “Disruptive Technology and the Board: The Tip of the Iceberg”. Economics and Business Review, n.d. Web.

    Gage, Deborah. “The Venture Capital Secret: 3 Out of 4 Start-Ups Fail.” Wall Street Journal, 20 Sept. 2012. Web.

    Garvin, David A. “Competing on the Eight Dimensions of Quality.” Harvard Business Review, November 1987. Web.

    Gibbs, Colin. Augmented Reality in the Enterprise: Opportunities and Challenges. Gigaom Research, 26 Jan. 2015. Web.

    Glushko, Robert J. and Tim McGrath. Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services. MIT Press, 2005.

    Hadfield, Tom. “Facebook’s Messenger Bot Store could be the most important launch since the App Store.” TechCrunch, 17 March 2016. Web.

    Healey, Nic. “Microsoft's mixed reality vision: 80 million devices by 2020.” CNET, 1 June 2016. Web.

    Hewlett-Packard. Go Beyond Cost Reduction: Use Robotic Process Automation, Oct. 2015. Web.

    Hewlett-Packard. HP Composable Infrastructure: Bridging Traditional IT with the New Style of Business, June 2015. Web.

    Hewlett-Packard. HP Labs, n.d. Web.

    Hong, Jason. “Inside the Great Wall.” Communications of the ACM, 25 May 2016. Web.

    IBM Institute for Value. Your Cognitive Future: How Next-Gen Computing Changes the Way We Live and Work, 2015. Web.

    IBM. A New Way to Work: Futurist Insights to 2025 and Beyond, Jan. 2015. Web.

    Infinity. The Evolution of the Data Centre [sic], 2015. Web.

    Intel Corporation. Intel Annual Report, 1997. Web.

    Isaac, Mike. “Facebook Bets on Bots for its Messenger App.” New York Times, 12 April 2016. Web.

    ISACA. COBIT 5: Enabling Processes. ISACA, 2012. Print.

    K-12 Blueprint. “Planning a Proof of Concept.” 2014. Web.

    Kaushik Rukmini, Meenakshi. “The Impact of Pandemic COVID -19 in Workplace.” European Journal of Business Management and Research, May 2020. Web.

    Knight, Will. “Conversational Interfaces Powerful speech technology from China’s leading Internet company makes it much easier to use a smartphone.” MIT Technology Review, n.d. Web.

    Kostoff, Ronald N., Robert Boylan, and Gene R. Simons. “Disruptive Technology Roadmaps.” Technological Forecasting and Social Change, 2004. Vol. 71. Web.

    Kurzweil, Ray. “The Accelerating Power of Technology.” TED, Feb. 2005. Web.

    Kurzweil, Ray. Kurzweil: Accelerating Intelligence, 2015. Web.

    MacFarquhar, Larissa. “When Giants Fall: What Business Has Learned From Clayton Christensen,” New Yorker, 14 May 2012. Web.

    McClintock, Cat. “2016: The Year for Augmented Reality in the Enterprise.” PTC, n.d. Web.

    McKinsey & Company. IT Growth and Global Change: A Conversation with Ray Kurzweil. 29 Feb. 2012, YouTube. Web.

    Messina, Chris. “2016 Will be the Year of Conversational Commerce.” Medium, 19 Jan 2016. Web.

    Microsoft. Microsoft Research, n.d. Web.

    Miller, Ron. “Forget the Apple Watch, Think Drones in the Enterprise.” TechCrunch, 10 Sep. 2015. Web.

    Nokia Networks. FutureWorks [sic]: Teaching Networks to be Self-Aware: Technology Vision 2020. 2014. Web.

    Nokia Networks. Internet of Things. n.d. Web.

    O’Reilly, Charles, and Andrew J. M. Binns, “The Three Stages of Disruptive Innovation: Idea Generation, Incubation, and Scaling”. Sage Journals, n.d. Web.

    Pew Research Center. AI, Robotics, and the Future of Jobs: Experts Envision Automation and Intelligent Digital Agents Permeating Vast Areas of Our Work and Personal Lives by 2025, but they are Divided on Whether these Advances will Displace More Jobs than they Create. Aug. 2014. Web.

    Ramiller, Neil. “Airline Magazine Syndrome: Reading a Myth of Mismanagement.” Information Technology & People, Sept 2001. Print.

    Raymond James & Associates. The Internet of Things: A Study in Hype, Reality, Disruption, and Growth. 2014. Web.

    Richter, Felix. “No Growth in Sight for Global PC Market.” Statista, 14 March 2016. Web.

    Roy, Mekhala. “4 Examples of Digital Transformation Success in Business”. TechTarget, n.d. Web.

    Simon Weinreich, “How to Manage Disruptive Innovation - a conceptional methodology for value-oriented portfolio planning,” Sciencedirect. 31st CIRP Design Conference 2021.

    Spice Works. The Devices are Coming! How the “Internet of Things” will affect IT… and why resistance is futile. May 2014. Web.

    Spradlin, Dwayne. “Are You Solving the Right Problem?” Harvard Business Review, Sept. 2012. Web.

    Statista. “Number of smartphones sold to end users worldwide from 2007 to 2015 (in million units).” N.d. Web.

    Statista. “Worldwide tablet shipments from 2nd quarter 2010 to 2nd quarter 2016 (in million units).” N.d. Web.

    Sven Schimpf, “Disruptive Field Study; How Companies Identify, Evaluate, Develop and Implement Disruptive Technologies.” Fraunhofer Group for Innovation Research, 2020. Web.

    Tsekleves, Emmanuel. “Science fiction as fact: how desires drive discoveries.” The Guardian. 13 Aug. 2015. Web.

    Tsekleves, Emmanuel. “Science fiction as fact: how desires drive discoveries.” The Guardian, 13 Aug. 2015. Web.

    United States Department of Transportation. “National Motor Vehicle Crash Causation Survey: Report to Congress.” National Highway Traffic Safety Administration, July 2008. Web.

    United States Department of Transportation. “National Motor Vehicle Crash Causation Survey: Report to Congress.” National Highway Traffic Safety Administration, July 2008. Web.

    University Alliance (Villanova U). Managing Scope Creep in Project Management. N.d. Web.

    Vavoula, Giasemi N., and Mike Sharples. “Future Technology Workshop: A Collaborative Method for the Design of New Learning Technologies and Activities.” International Journal of Computer Supported Collaborative Learning, Dec 2007. Vol. 2 no. 4. Web.

    Walraven Pieter. “It’s Operating Systems Vs. Messaging Apps In The Battle For Tech’s Next Frontier.” TechCrunch, 11 Aug 2015. Web.

    Webb, Amy. “The Tech Trends You Can’t Ignore in 2015.” Harvard Business Review, 5 Jan. 2015. Web.

    Wenger, Albert. “The Great Bot Rush of 2015-16.” Continuations, 16 Dec 2015. Web.

    White, Chris. “IoT Tipping Point Propels Digital Experience Era.” Cisco Blogs, 12 Nov. 2014. Web.

    World Economic Forum and Accenture. Industrial Internet of Things: Unleashing the Potential of Connected Products and Services. 2015. Web.

    Yu Dan and Hang Chang Chieh, "A reflective review of disruptive innovation theory," PICMET '08 - 2008 Portland International Conference on Management of Engineering & Technology, 2008, pp. 402-414, doi: 10.1109/PICMET.2008.4599648.

    Build an Application Rationalization Framework

    • Buy Link or Shortcode: {j2store}173|cart{/j2store}
    • member rating overall impact: 9.2/10 Overall Impact
    • member rating average dollars saved: $39,942 Average $ Saved
    • member rating average days saved: 23 Average Days Saved
    • Parent Category Name: Architecture & Strategy
    • Parent Category Link: /architecture-and-strategy
    • Almost two-thirds of organizations report that they have too many or far too many applications due to sprawl from poorly managed portfolios, and application managers are spending too much time supporting non-critical applications and not enough time on their most vital ones.
    • The necessary pieces of rationalization are rarely in one place. You need to assemble the resources to collect vital rationalization criteria.
    • There is a lack of standard practices to define the business value that the applications in a portfolio provide, and without value rationalization, decisions are misaligned to business needs.

    Our Advice

    Critical Insight

    There is no “one size fits all.” Applying a rigid approach to rationalization with inflexible inputs can delay or prevent you from realizing value. Play to your strengths and build a framework that aligns to your goals and limitations.

    Impact and Result

    • Define the roles, responsibilities, and outputs for application rationalization within your application portfolio management practice.
    • Build a tailored application rationalization framework (ARF) aligned with your motivations, goals, and limitations.
    • Apply the various application assessments to produce the information that your dispositions will be based on.
    • Initiate an application portfolio roadmap that will showcase your rationalization decisions to key stakeholders.

    Build an Application Rationalization Framework Research & Tools

    Start here – read the Executive Brief

    Read our concise Executive Brief to find out why you should rationalize your applications and why you need a framework that is specific to your goals and limitations, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

    Besides the small introduction, subscribers and consulting clients within this management domain have access to:

    1. Lay your foundations

    Define the motivations, goals, and scope of your rationalization effort. Build the action plan and engagement tactics to roll out the rationalization activities.

    • Build an Application Rationalization Framework – Phase 1: Lay Your Foundations
    • Application Rationalization Tool

    2. Plan your application rationalization framework

    Understand the core assessments performed in application rationalizations. Define your application rationalization framework and degree of rigor in applying these assessments based on your goals and limitations.

    • Build an Application Rationalization Framework – Phase 2: Plan Your Application Rationalization Framework

    3. Test and adapt your application rationalization framework

    Test your application rationalization framework using Info-Tech’s tool set on your first iteration. Perform a retrospective and adapt your framework based on that experience and outcomes.

    • Build an Application Rationalization Framework – Phase 3: Test and Adapt Your Application Rationalization Framework
    • Application TCO Calculator
    • Value Calculator

    4. Initiate your roadmap

    Review, determine, and prioritize your dispositions to ensure they align to your goals. Initiate an application portfolio roadmap to showcase your rationalization decisions to key stakeholders.

    • Build an Application Rationalization Framework – Phase 4: Initiate Your Roadmap
    • Disposition Prioritization Tool
    [infographic]

    Workshop: Build an Application Rationalization Framework

    Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

    1 Lay Your Foundations

    The Purpose

    Define the goals, scope, roles, and responsibilities of your rationalization effort.

    Key Benefits Achieved

    Defined motivations, long and short-term goals, and metrics for your rationalization effort.

    Definition of application.

    Defined roles and responsibilities for your rationalization effort.

    Activities

    1.1 Define motivations and goals for rationalization.

    1.2 Define “application.”

    1.3 Identify team and responsivities.

    1.4 Adapt target dispositions.

    1.5 Initiate Application Rationalization Framework (ARF).

    Outputs

    Goals, motivations, and metrics for rationalizations

    Definition of “Application”

    Defined dispositions

    Defined core APM team and handoffs

    2 Assess Business Value

    The Purpose

    Review and adapt Info-Tech’s methodology and toolset.

    Assess business value of applications.

    Key Benefits Achieved

    Tailored application rationalization framework

    Defined business value drivers

    Business value scores for applications

    Activities

    2.1 Review Application Rationalization Tool.

    2.2 Review focused apps, capabilities, and areas of functionality overlap.

    2.3 Define business value drivers.

    2.4 Determine the value score of focused apps.

    Outputs

    Application Rationalization Tool

    List of functional overlaps

    Weighed business value drivers

    Value scores for focused application

    Value Calculator

    3 Gather Application Information

    The Purpose

    Continue to review and adapt Info-Tech’s methodology and toolset.

    Key Benefits Achieved

    Tailored application rationalization framework

    TCO values for applications

    Technical health review of applications

    Recommended dispositions for applications

    Activities

    3.1 Determine TCO for focused apps.

    3.2 Determine technical health of focused apps.

    3.3 Review APA.

    3.4 Review recommended dispositions.

    3.5 Perform retrospective of assessments and adapt ARF.

    Outputs

    TCO of focused applications

    TCO Calculator

    Technical health of focused apps

    Defined rationalization criteria

    Recommended disposition for focused apps

    4 Gather, Assess, and Select Dispositions

    The Purpose

    Review and perform high-level prioritization of dispositions.

    Build a roadmap for dispositions.

    Determine ongoing rationalization and application portfolio management activities.

    Key Benefits Achieved

    Application Portfolio Roadmap

    Prioritized Dispositions

    Activities

    4.1 Determine dispositions.

    4.2 Prioritize dispositions.

    4.3 Initiate portfolio roadmap.

    4.4 Build an action plan for next iterations and ongoing activities.

    4.5 Finalize ARF.

    Outputs

    Disposition Prioritization Tool

    Application portfolio roadmap

    Action plan for next iterations and ongoing activities

    Further reading

    Build an Application Rationalization Framework

    Manage your application portfolio to minimize risk and maximize value.

    Analyst Perspective

    "You're not rationalizing for the sake of IT, you’re rationalizing your apps to create better outcomes for the business and your customers. Consider what’s in it for delivery, operations, the business, and the customer." – Cole Cioran, Senior Director – Research, Application Delivery and Management

    Our understanding of the problem

    This Research Is Designed For:

    • Application portfolio managers, application portfolio management (APM) teams, or any application leaders who are tasked with making application portfolio decisions.
    • Application leaders looking to align their portfolios to the organization’s strategy.
    • Application leaders who need a process for rationalizing their applications.

    This Research Will Help You:

    • Measure the business value of your applications.
    • Rationalize your portfolio to determine the best disposition for each application.
    • Initiate a roadmap that will showcase the future of your applications.

    This Research Will Also Assist:

    • CIOs and other business leaders who need to understand the applications in their portfolio, the value they contribute to the business, and their strategic direction over a given timeline.
    • Steering committees and/or the PMO that needs to understand the process by which application dispositions are generated.

    This Research Will Help Them:

    • Build their reputation as an IT leader who drives the business forward.
    • Define the organization’s value statement in the context of IT and their applications.
    • Visualize the roadmap to the organization’s target application landscape.

    Executive Summary

    Situation

    • Almost two-thirds of organizations report that they have too many or far too many applications due to sprawl from poorly managed portfolios (Flexera, 2015).
    • Application managers are spending too much time supporting non-critical applications and not enough time on their most vital ones.
    • Application managers need their portfolios to be current and effective and evolve continuously to support the business or risk being marginalized.

    Complication

    • The necessary pieces of rationalization are rarely in one place. You need to assemble the resources to collect vital rationalization criteria.
    • There is a lack of standard practices to define the business value that the applications in a portfolio provide and, without value rationalization, decisions are misaligned to business needs.

    Resolution

    • Define the roles, responsibilities, and outputs for application rationalization within your application portfolio management (APM) and other related practices.
    • Build a tailored application rationalization framework (ARF) aligned with your motivations, goals, and limitations.
    • Apply the various application assessments to produce the information, which your dispositions will be based on, and adapt your ARF based on the experiences of your first iteration.
    • Review, determine, and prioritize your application dispositions to create a portfolio strategy aligned to your goals.
    • Initiate an application portfolio roadmap, which will showcase your rationalization decisions to key stakeholders.

    Info-Tech Insight

    There is no one size fits all.

    Applying a rigid approach with inflexible inputs can delay or prevent you from realizing value. Play to your strengths and build a framework that aligns to your goals and limitations.

    Business value must drive your decisions.

    Of the 11 vendor capabilities asked about by Info-Tech’s SoftwareReviews, “business value created” has the second highest relationship with overall software satisfaction.

    Take an iterative approach.

    Larger approaches take longer and are more likely to fail. Identify the applications that best address your strategic objectives, then: rationalize, learn, repeat.

    Info-Tech recommends a disciplined, step-by-step approach as outlined in our Application Portfolio Strategy Program

    Step 1 "No Knowledge": Define application capabilities and visualize lifecycle stages

    Application Discovery

    1. Build in Application Portfolio Management Principles.
    2. Conduct Application Alignment.
    3. Build Detailed Application Inventory

    Step 2 "No Strategy": Rationalize application portfolio and visualize strategic directions

    Application Rationalization

    1. Set Your Rationalization Framework
    2. Conduct Assessment & Assign Dispositions
    3. Create an Application Portfolio Roadmap

    Step 3 "No Plan": Build a product roadmap and visualize the detailed plan

    Detailed Disposition Planning

    1. Conduct an Impact Assessment
    2. Determine the Details of the Disposition
    3. Create Detailed Product Roadmaps

    This blueprint focuses on step 2 of Info-Tech's Application Portfolio Strategy Program. Our methodology assumes you have completed the following activities, which are outlined in Discover Your Applications.

    • Collected your full application inventory (including Shadow IT)
    • Aligned applications to business capabilities
    • Determined redundant applications
    • Identified appropriate subject matter experts (business and technical) for your applications

    Info-Tech's four-phase methodology

    Phase 1

    Lay Your Foundations

    • Define Motivations, Goals, and Scope
    • Iteration and Engagement Planning

    This phase is intended to establish the fundamentals in launching either a rationalization initiative or ongoing practice.

    Here we define goals, scope, and the involvement of various roles from both IT and the business.

    Phase 2

    Plan Your ARF

    • Establish Rationalization Inputs and Current Gaps

    This phase is intended to review a high-level approach to rationalization and determine which analyses are necessary and their appropriate level of depth.

    Here we produce an initial ARF and discuss any gaps in terms of the availability of necessary data points and additional collection methods that will need to be applied.

    Phase 3

    Test and Adapt Your ARF

    • Perform First Iteration Analysis
    • First Iteration Retrospective and Adaptation

    This phase is intended to put the ARF into action and adapt as necessary to ensure success in your organization.

    If appropriate, here we apply Info-Tech’s ARF and toolset and test it against a set of applications to determine how best to adapt these materials for your needs.

    Phase 4

    Initiate Your Roadmap

    • Prioritize and Roadmap Applications
    • Ongoing Rationalization and Roadmapping

    This phase is intended to capture results of rationalization and solidify your rationalization initiative or ongoing practice.

    Here we aim to inject your dispositions into an application portfolio roadmap and ensure ongoing governance of APM activities.

    There is an inconsistent understanding and ownership of the application portfolio

    What can I discover about my portfolio?

    Application portfolios are misunderstood.

    Portfolios are viewed as only supportive in nature. There is no strategy or process to evaluate application portfolios effectively. As a result, organizations build a roadmap with a lack of understanding of their portfolio.

    72% of organizations do not have an excellent understanding of the application portfolio (Capgemini).

    How can I improve my portfolio?

    Misalignment between Applications and Business Operations

    Applications fail to meet their intended function, resulting in duplication, a waste of resources, and a decrease in ROI. This makes it harder for IT to justify to the business the reasons to complete a roadmap.

    48% of organizations believe that there are more applications than the business requires (Capgemini).

    How can my portfolio help transform the business?

    IT's budget is to keep the lights on.

    The application portfolio is complex and pervasive and requires constant support from IT. This makes it increasingly difficult for IT to adopt or develop new strategies since its immediate goal will always be to fix what already exists. This causes large delays and breaks in the timeline to complete a roadmap.

    68% of IT directors have wasted time and money because they did not have better visibility of application roadmaps (ComputerWeekly).

    Roadmaps can be the solution, but stall when they lack the information needed for good decision making

    An application portfolio roadmap provides a visual representation of your application portfolio, is used to plan out the portfolio’s strategy over a given time frame, and assists management in key decisions. But…

    • You can’t change an app without knowing its backend.
    • You can't rationalize what you don't know.
    • You can’t confirm redundancies without knowing every app.
    • You can’t rationalize without the business perspective.

    A roadmap is meaningless if you haven’t done any analysis to understand the multiple perspectives on your applications.

    Application rationalization ensures roadmaps reflect what the business actually wants and needs

    Application rationalization is the practice of strategically identifying business applications across an organization to determine which applications should be kept, replaced, retired, or consolidated (TechTarget).

    Discover, Improve, and Transform Through Application Rationalization

    Your application rationalization effort increases the maturity of your roadmap efforts by increasing value to the business. Go beyond the discover phase – leverage application rationalization insights to reach the improve and transform phases.

    Strong Apps Are Key to Business Satisfaction

    79% of organizations with high application suite satisfaction believe that IT offers the organization a competitive edge over others in the industry. (Info-Tech Research Group, N=230)

    Info-Tech Insight

    Companies with an effective portfolio are twice as likely to report high-quality applications, four times as likely to report high proficiency in legacy apps management, and six times as likely to report strong business alignment.

    Rationalization comes at a justified cost

    Rationalization can reduce costs and drive innovation

    Projecting the ROI of application rationalization is difficult and dangerous when used as the only marker for success.

    However, rationalization, when done effectively, will help drop operational or maintenance costs of your applications as well as provide many more opportunities to add value to the business.

    A graph with Time on the X-axis and Cost on the Y axis. The graph compares cost before rationalization, where the cost of the existing portfolio is high, with cost after rationalization, where the cost of the existing portfolio is reduced. The graph demonstrates a decrease in overall portfolio spend after rationalization

    Organizations lack a strategic approach to application rationalization, leading to failure

    IT leaders strive to push the business forward but are stuck in a cycle of reaction where they manage short-term needs rather than strategic approaches.

    Why Is This the Case?

    Lack of Relevant Information

    Rationalization fails without appropriately detailed, accurate, and up-to-date information. You need to identify what information is available and assemble the teams to collect and analyze it.

    Failure to Align With Business Objectives

    Rationalization fails when you lack a clear list of strategic and collaborative priorities; priorities need to be both IT and non-IT related to align with the business objectives and provide value.

    IT Leaders Fails to Justify Projects

    Adhering to a rigid rationalization process can be complex and costly. Play to your strengths and build an ARF based on your goals and limitations.

    Info-Tech Insight

    Misaligned portfolio roadmaps are known to lead teams and projects into failure!
    Building an up-to-date portfolio roadmap that aligns business objectives to IT objectives will increase approval and help the business see the long-term value of roadmapping.

    Don’t start in the middle; ensure you have the basics down

    Application portfolio strategy practice maturity stages

    1. Discover Your Applications
    2. Improve
    3. Transform
    A graph with Rigor of APM Practice on the X-axis and Value to the Business on the Y-axis. The content of the graph is split into the 3 maturity stages, Discover, Improve, and Transform. With each step, the Value to the Business and Rigor of APM Practice increase.

    Disambiguate your systems and clarify your scope

    Define the items that make up your portfolio.

    Broad or unclear definitions of “application” can complicate the scope of rationalization. Take the time to define an application and come to a common understanding of the systems which will be the focus of your rationalization effort.

    Bundling systems under common banner or taking a product view of your applications and components can be an effective way to ensure you include your full collection of systems, without having to perform too many individual assessments.

    Scope

    Single... Capability enabled by... Whole...
    Digital Product + Service Digital Platform Platform Portfolio Customer Facing
    Product (one or more apps) Product Family Product Portfolio

    Application Application Architecture Application Portfolio Internal

    A graphic listing the following products: UI, Applications, Middleware, Data, and Infrastructure. A banner reading APIs runs through all products, and UI, Applications, and Middleware are bracketed off as Application

    Info-Tech’s framework can be applied to portfolios of apps, products, and their related capabilities or services.

    However you organize your tech stack, Info-Tech’s application rationalization framework can be applied.

    Understand the multiple lenses of application rationalization and include in your framework

    There are many lenses to view your applications. Rationalize your applications using all perspectives to assess your portfolio and determine the most beneficial course of action.

    Application Alignment - Architect Perspective

    How well does the entire portfolio align to your business capabilities?

    Are there overlaps or redundancies in your application features?

    Covered in Discover Your Applications.

    Business Value - CEO Perspective

    Is the application producing sufficient business value?

    Does it impact profitability, enable capabilities, or add any critical factor that fulfills the mission and vision?

    TCO - CIO Perspective

    What is the overall cost of the application?

    What is the projected cost as your organization grows? What is the cost to maintain the application?

    End User

    How does the end user perceive the application?

    What is the user experience?

    Do the features adequately support the intended functions?

    Is the application important or does it have high utilization?

    Technical Value - App Team Perspective

    What is the state of the backend of the application?

    Has the application maintained sufficient code quality? Is the application reliable? How does it fit into your application architecture?

    Each perspective requires its own analysis and is an area of criteria for rationalization.

    Apply the appropriate amount of rigor for your ARF based on your specific goals and limitations

    Ideally, the richer the data the better the results, but the reality is in-depth analysis is challenging and you’ll need to play to your strengths to be successful.

    Light-Weight Assessment

    App to capability alignment.

    Determine overlaps.

    Subjective 1-10 scale

    Subjective T-shirt size (high, med., low)

    End-user surveys

    Performance temperature check

    Thorough Analysis

    App to process alignment.

    Determine redundancies.

    Apply a value measurement framework.

    Projected TCO with traceability to ALM & financial records.

    Custom build interviews with multiple end users

    Tool and metric-based analysis

    There is no one-size-fits all rationalization. The primary goal of this blueprint is to help you determine the appropriate level of analysis given your motivations and goals for this effort as well as the limitations of resources, timeline, and accessible information.

    Rationalize and build your application portfolio strategy the right way to ensure success

    Big-Bang Approach

    • An attempt to assess the whole portfolio at once.
    • The result is information overload.
    • Information gathered is likely incomplete and/or inaccurate.
    • Tangible benefits are a long time away.

    Covert Approach

    • Information is collected behind the scenes and whenever information sources are available.
    • Assumptions about the business use of applications go unconfirmed.

    Corner-of-the-Desk Approach

    • No one is explicitly dedicated to building a strategy or APM practices.
    • Information is collected whenever the application team has time available.
    • Benefits are pushed out and value is lost.

    Iterative Approach

    • Carried out in phases, concentrating on individual business units or subsets of applications.
    • Priority areas are completed first.
    • The APM practice strengthens through experience.

    Sponsored Mandate Approach

    • The appropriate business stakeholders participate.
    • Rationalization is given project sponsors who champion the practice and communicate the benefits across the organization.

    Dedicated Approach

    • Rationalization and other APM activities are given a budget and formal agenda.
    • Roles and responsibilities are assigned to team members.

    Use Info-Tech’s Application Portfolio Assessment Diagnostic to add the end users’ perspective to your decision making

    Prior to Blueprint: Call 1-888-670-8889 to inquire about or request the Application Portfolio Assessment.

    Info-Tech Best Practice

    The approach in this blueprint has been designed in coordination with Info-Tech’s Application Portfolio Assessment (APA) Diagnostic. While it is not a prerequisite, your project will experience the best results and be completed much quicker by taking advantage of our diagnostic offering prior to initiating the activities in this blueprint.

    Use the program diagnostic to:

    • Assess the importance and satisfaction of enterprise applications.
    • Solicit feedback from your end users on applications being used.
    • Understand the strengths and weaknesses of your current applications.
    • Perform a high-level application rationalization initiative.

    Integrate diagnostic results to:

    • Target which applications to analyze in greater detail.
    • Expand on the initial application rationalization results with a more comprehensive and business-value-focused criteria.

    Use Info-Tech’s Application Rationalization Tool to determine and then visualize your application portfolio strategy

    At the center of this project is an Application Rationalization Tool that is used as a living document of your:

      1. Customizable Application Rationalization Framework

      2. Recommendation Dispositions

      3. Application Portfolio Roadmap (seen below)

    Use the step-by-step advice within this blueprint to rationalize your application portfolio and build a realistic and accurate application roadmap that drives business value.

    Central to our approach to application rationalization are industry-leading frameworks

    Info-Tech uses the APQC and COBIT5 frameworks for certain areas of this research. Contextualizing application rationalization within these frameworks clarifies its importance and role and ensures that our assessment tool is focused on key priority areas. The APQC and COBIT5 frameworks are used as a starting point for assessing application effectiveness within specific business capabilities of the different components of application rationalization.

    APQC is one of the world's leading proponents of business benchmarking, best practices, and knowledge management research.

    COBIT 5 is the leading framework for the governance and management of enterprise IT.

    In addition to industry-leading frameworks, our best-practice approach is enhanced by the insights and guidance from our analysts, industry experts, and our clients.

    Our peer network of over 33,000 happy clients proves the effectiveness of our research.

    Our team conducts 1,000+ hours of primary and secondary research to ensure that our approach is enhanced by best practices.

    A public utility organization is using Info-Tech’s approach for rationalization of its applications for reduced complexity

    Case Study

    Industry: Public Sector

    Source: Info-Tech Research Group

    Challenge

    • The public utility has a complex application portfolio, with a large number of applications custom-built that provide limited functionality to certain business groups.
    • The organization needed to move away from custom point solutions and adopt more hosted solutions to cater to larger audiences across business domains.
    • The organization required a comprehensive solution for the following:
      • Understanding how applications are being used by business users.
      • Unraveling the complexity of its application landscape using a formal rationalization process.

    Solution

    • The organization went through a rationalization process with Info-Tech in a four-day onsite engagement to determine the following:
      • Satisfaction level and quality evaluation of end users’ perception of application functionality.
      • Confirmation on what needs to be done with each application under assessment.
      • The level of impact the necessary changes required for a particular application would have on the greater app ecosystem.
      • Prioritization methodology for application roadmap implementation.

    Results

    • Info-Tech’s Application Portfolio Assessment Diagnostic report helped the public utility understand what applications users valued and found difficult to use.
    • The rationalization process gave insight into situations where functionality was duplicated across multiple applications and could be consolidated within one application.
    • The organization determined that its application portfolio was highly complex, and Info-Tech provided a good framework for more in-depth analysis.
    • The organization now has a rationalization process that it can take to other business domains.

    Achieve Digital Resilience by Managing Digital Risk

    • Buy Link or Shortcode: {j2store}375|cart{/j2store}
    • member rating overall impact: 9.0/10 Overall Impact
    • member rating average dollars saved: $123,999 Average $ Saved
    • member rating average days saved: 4 Average Days Saved
    • Parent Category Name: Governance, Risk & Compliance
    • Parent Category Link: /governance-risk-compliance

    Businesses are expected to balance achieving innovation through initiatives that transform the organization with effective risk management. While this is nothing new, added challenges arise due to:

    • An increasingly large vendor ecosystem within which to manage risk.
    • A fragmented approach to risk management that separates cyber and IT risk from enterprise risk.
    • A rapidly growing number of threat actors and a larger attack surface.

    Our Advice

    Critical Insight

    • All risks are digital risks.
    • Manage digital risk with a collaborative approach that supports digital transformation, ensures digital resilience, and distributes responsibility for digital risk management across the organization.

    Impact and Result

    Address digital risk to build digital resilience. In the process, you will drive transformation and maintain digital trust among your employees, end users, and consumers by:

    • Defining digital risk, including primary risk categories and prevalent risk factors.
    • Leveraging industry examples to help identify external risk considerations.
    • Building a digital risk profile, addressing core risk categories, and creating a correlating plan for digital risk management.

    Achieve Digital Resilience by Managing Digital Risk Research & Tools

    Start here – read the Executive Brief

    Risk does not exist in isolation and must extend beyond your cyber and IT teams. Read our concise Executive Brief to find out how to manage digital risk to help drive digital transformation and build your organization's digital resilience.

    Besides the small introduction, subscribers and consulting clients within this management domain have access to:

    1. Redefine digital risk and resilience

    Discover an overview of what digital risk is, learn how to assess risk factors for the five primary categories of digital risk, see several industry-specific scenarios, and explore how to plan for and mitigate identified risks.

    • Achieve Digital Resilience by Managing Digital Risk – Phases 1-2
    • Digital Risk Management Charter

    2. Build your digital risk profile

    Begin building the digital risk profile for your organization, identify where your key areas of risk exposure exist, and assign ownership and accountability among the organization’s business units.

    • Digital Risk Profile Tool
    • Digital Risk Management Executive Report
    [infographic]

    Workshop: Achieve Digital Resilience by Managing Digital Risk

    Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

    1 Scope and Define Digital Risk

    The Purpose

    Develop an understanding and standard definition of what digital risk is, who it impacts, and its relevance to the organization.

    Key Benefits Achieved

    Understand what digital risk means and how it differs from traditional enterprise or cybersecurity risk.

    Develop a definition of digital risk that recognizes the unique external and internal considerations of your organization.

    Activities

    1.1 Review the business context

    1.2 Review the current roles of enterprise, IT, and cyber risk management within the organization

    1.3 Define digital transformation and list transformation initiatives

    1.4 Define digital risk in the context of the organization

    1.5 Define digital resilience in the context of the organization

    Outputs

    Digital risk drivers

    Applicable definition of digital risk

    Applicable definition of digital resilience

    2 Make the Case for Digital Risk Management

    The Purpose

    Understand the roles digital risk management and your digital risk profile have in helping your organization achieve safe, transformative growth.

    Key Benefits Achieved

    An overview and understanding of digital risk categories and subsequent individual digital risk factors for the organization

    Industry considerations that highlight the importance of managing digital risk

    A structured approach to managing the categories of digital risk

    Activities

    2.1 Review and discuss industry case studies and industry examples of digital transformation and digital risk

    2.2 Revise the organization's list of digital transformation initiatives (past, current, and future)

    2.3 Begin to build your organization's Digital Risk Management Charter (with inputs from Module 1)

    2.4 Revise, customize, and complete a Digital Risk Management Charter for the organization

    Outputs

    Digital Risk Management Charter

    Industry-specific digital risks, factors, considerations, and scenarios

    The organization's digital risks mapped to its digital transformation initiatives

    3 Build Your Digital Risk Profile

    The Purpose

    Develop an initial digital risk profile that identifies the organization’s core areas of focus in managing digital risk.

    Key Benefits Achieved

    A unique digital risk profile for the organization

    Digital risk management initiatives that are mapped against the organization's current strategic initiatives and aligned to meet your digital resilience objectives and benchmarks

    Activities

    3.1 Review category control questions within the Digital Risk Profile Tool

    3.2 Complete all sections (tabs) within the Digital Risk Profile Tool

    3.3 Assess the results of your Digital Risk Profile Tool

    3.4 Discuss and assign initial weightings for ownership of digital risk among the organization's stakeholders

    Outputs

    Completion of all category tabs within the Digital Risk Profile Tool

    Initial stakeholder ownership assignments of digital risk categories

    4 Manage Your Digital Risk

    The Purpose

    Refine the digital risk management plan for the organization.

    Key Benefits Achieved

    A targeted, organization-specific approach to managing digital risk as a part of the organization's projects and initiatives on an ongoing basis

    An executive presentation that outlines digital risk management for your senior leadership team

    Activities

    4.1 Conduct brief information sessions with the relevant digital risk stakeholders identified in Module 3.

    4.2 Review and revise the organization's Digital Risk Profile as necessary, including adjusting weightings for the digital risk categories

    4.3 Begin to build an actionable digital risk management plan

    4.4 Present your findings to the organization's relevant risk leaders and executive team

    Outputs

    A finalized and assessed Digital Risk Profile Tool

    Stakeholder ownership for digital risk management

    A draft Digital Risk Management plan and Digital Risk Management Executive Report

    Develop a Security Awareness and Training Program That Empowers End Users

    • Buy Link or Shortcode: {j2store}370|cart{/j2store}
    • member rating overall impact: 9.4/10 Overall Impact
    • member rating average dollars saved: $12,075 Average $ Saved
    • member rating average days saved: 11 Average Days Saved
    • Parent Category Name: Security Strategy & Budgeting
    • Parent Category Link: /security-strategy-and-budgeting
    • The fast evolution of the cybersecurity landscape requires security training and awareness programs that are frequently updated and improved.
    • Security and awareness training programs often fail to engage end users. Lack of engagement can lead to low levels of knowledge retention.
    • Irrelevant or outdated training content does not properly prepare your end users to effectively defend the organization against security threats.

    Our Advice

    Critical Insight

    • One-time, annual training is no longer sufficient for creating an effective security awareness and training program.
    • By presenting security as a personal and individualized issue, you can make this new personal focus a driver for your organizational security awareness and training program.

    Impact and Result

    • Create a training program that delivers smaller amounts of information on a more frequent basis to minimize effort, reduce end-user training fatigue, and improve content relevance.
    • Evaluate and improve your security awareness and training program continuously to keep its content up-to-date. Leverage end-user feedback to ensure content remains relevant to those who receive it.

    Develop a Security Awareness and Training Program That Empowers End Users Research & Tools

    Start here – read the Executive Brief

    Read our concise Executive Brief to find out why you should develop a security awareness and training program that empowers end users, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

    Besides the small introduction, subscribers and consulting clients within this management domain have access to:

    1. Develop your training program

    Create or mature a security awareness and training program that is tailored to your organization.

    • Develop a Security Awareness and Training Program That Empowers End Users – Phase 1: Develop Your Training Program
    • Security Awareness and Training Program Development Tool
    • End-User Security Job Description Template
    • Training Materials – Physical Computer Security
    • Training Materials – Cyber Attacks
    • Training Materials – Incident Response
    • Training Materials – Mobile Security
    • Training Materials – Passwords
    • Training Materials – Phishing
    • Training Materials – Social Engineering
    • Training Materials – Web Usage
    • Security Awareness and Training Vendor Evaluation Tool
    • Security Awareness and Training Metrics Tool
    • End-User Security Knowledge Test Template
    • Security Training Campaign Development Tool

    2. Design an effective training delivery plan

    Explore methods of training delivery and select the most effective solutions.

    • Develop a Security Awareness and Training Program That Empowers End Users – Phase 2: Design an Effective Training Delivery Plan
    • Information Security Awareness and Training Policy
    • Security Awareness and Training Gamification Guide
    • Mock Spear Phishing Email Examples
    • Security Training Email Templates
    • Security Awareness and Training Module Builder and Training Schedule
    • Security Training Campaign Development Tool
    • Security Training Program Manual
    • Security Awareness and Training Feedback Template
    • Security Awareness Month Week 1: Staying in Touch
    • Security Awareness Month Week 2: Sharing Special Moments
    • Security Awareness Month Week 3: Working and Networking
    • Security Awareness Month Week 4: Families and Businesses
    [infographic]

    Workshop: Develop a Security Awareness and Training Program That Empowers End Users

    Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

    1 Outline the Plan for Long-term Program Improvement

    The Purpose

    Identify the maturity level of the existing security awareness and training program and set development goals.

    Establish program milestones and outline key initiatives for program development.

    Identify metrics to measure program effectiveness.

    Key Benefits Achieved

    Identified the gaps between the current maturity level of the security awareness and training program and future target states.

    Activities

    1.1 Create a program development plan.

    1.2 Investigate and select metrics to measure program effectiveness.

    1.3 Execute some low-hanging fruit initiatives for collecting metrics: e.g. create a knowledge test, feedback survey, or gamification guide.

    Outputs

    Customized development plan for program.

    Tool for tracking metrics.

    Customized knowledge quiz ready for distribution.

    Customized feedback survey for training.

    Gamification program outline.

    2 Identify and Assess Audience Groups and Security Training Topics

    The Purpose

    Determine the unique audience groups within your organization and evaluate their risks and vulnerabilities.

    Prioritize training topics and audience groups to effectively streamline program development.

    Key Benefits Achieved

    Created a comprehensive list of unique audience groups and the corresponding security training that each group should receive.

    Determined priority ratings for both audience groups and the security topics to be delivered.

    Activities

    2.1 Identify the unique audience groups within your organization and the threats they face.

    2.2 Determine the priority levels of the current security topics.

    2.3 Review audience groups and determine which topics need to be delivered to each group.

    Outputs

    Risk profile for each identified audience group.

    Priority scores for all training topics.

    List of relevant security topics for each identified audience group.

    3 Plan the Training Delivery

    The Purpose

    Identify all feasible delivery channels for security training within your organization.

    Build a vendor evaluation tool and shortlist or harvest materials for in-house content creation.

    Key Benefits Achieved

    List of all potential delivery mechanisms for security awareness and training.

    Built a vendor evaluation tool and discussed a vendor shortlist.

    Harvested a collection of free online materials for in-house training development.

    Activities

    3.1 Discuss potential delivery mechanisms for training, including the purchase and use of a vendor.

    3.2 If selecting a vendor, review vendor selection criteria and discuss potential vendor options.

    3.3 If creating content in-house, review and select available resources on the web.

    Outputs

    List of available delivery mechanisms for training.

    Vendor assessment tool and shortlist.

    Customized security training presentations.

    4 Create a Training Schedule for Content Deployment

    The Purpose

    Create a plan for deploying a pilot program to gather valuable feedback.

    Create an ongoing training schedule.

    Define the end users’ responsibilities towards security within the organization.

    Key Benefits Achieved

    Created a plan to deploy a pilot program.

    Created a schedule for training deployment.

    Defined role of end users in helping protect the organization against security threats.

    Activities

    4.1 Build training modules.

    4.2 Create an ongoing training schedule.

    4.3 Define and document your end users’ responsibilities towards their security.

    Outputs

    Documented modular structure to training content.

    Training schedule.

    Security job description template.

    End-user training policy.

    Create a Data Management Roadmap

    • Buy Link or Shortcode: {j2store}122|cart{/j2store}
    • member rating overall impact: 9.3/10 Overall Impact
    • member rating average dollars saved: $100,135 Average $ Saved
    • member rating average days saved: 36 Average Days Saved
    • Parent Category Name: Data Management
    • Parent Category Link: /data-management

    Data has quickly become one of the most valuable assets in any organization. But when it comes to strategically and effectively managing those data assets, many businesses find themselves playing catch-up. The stakes are high because ineffective data management practices can have serious consequences, from poor business decisions and missed revenue opportunities to critical cybersecurity risks.

    Successful management and consistent delivery of data assets requires collaboration between the business and IT and the right balance of technology, process, and resourcing solutions.

    Build an effective and collaborative data management practice

    Data management is not one-size-fits-all. Cut through the noise around data management and create a roadmap that is right for your organization:

    • Align data management plans with business requirements and strategic plans.
    • Create a collaborative plan that unites IT and the business in managing data assets.
    • Design a program that can scale and evolve over time.
    • Perform data strategy planning and incorporate data capabilities into your broader plans.
    • Identify gaps in current data services and the supporting environment and determine effective corrective actions.

    This blueprint will help you design a data management practice that builds capabilities to support your organization’s current use of data and its vision for the future.

    Create a Data Management Roadmap Research & Tools

    Besides the small introduction, subscribers and consulting clients within this management domain have access to:

    1. Create a Data Management Roadmap Storyboard – Use this deck to help you design a data management practice and turn data into a strategic enabler for the organization.

    Effective data delivery and management provides the business with new and improved opportunities to leverage data for business operations and decision making. This blueprint will help you design a data management practice that will help your team build capabilities that align to the business' current usage of data and its vision for the future.

    • Create a Data Management Roadmap – Phases 1-2

    2. Data Management Strategy Planning Tools – Use these tools to align with the business and lay the foundations for the success of your data management practice.

    Begin by using the interview guide to engage stakeholders to gain a thorough understanding of the business’ challenges with data, their strategic goals, and the opportunities for data to support their future plans. From there, these tools will help you identify the current and target capabilities for your data management practice, analyze gaps, and build your roadmap.

    • Data Strategy Planning Interview Guide
    • Data Management Assessment and Planning Tool
    • Data Management Project Charter Template

    3. Stakeholder Communication and Assessment Tools – Use these templates to develop a communication strategy that will convey the value of the data management project to the organization and meet the needs of key stakeholders.

    Strong messaging around the value and purpose of the data management practice is essential to ensure buy-in. Use these templates to build a business case for the project and socialize the idea of data management across the various levels of the organization while anticipating the impact on and reactions from key stakeholders.

    • Data Management Communication/Business Case Template
    • Project Stakeholder and Impact Assessment Tool

    4. Data Management Strategy Work Breakdown Structure Template – Use this template to maintain strong project management throughout your data management project.

    This customizable template will support an organized approach to designing a program that addresses the business’ current and evolving data management needs. Use it to plan and track your deliverables and outcomes related to each stage of the project.

    • Data Management Strategy Work Breakdown Structure Template

    5. Data Management Roadmap Tools – Use these templates to plan initiatives and create a data management roadmap presentation.

    Create a roadmap for your data management practice that aligns to your organization’s current needs for data and its vision for how it wants to use data over the next 3-5 years. The initiative tool guides you to identify and record all initiative components, from benefits to costs, while the roadmap template helps you create a presentation to share your project findings with your executive team and project sponsors.

    • Initiative Definition Tool
    • Data Management Roadmap Template

    6. Track and Measure Benefits Tool – Use this tool to monitor the project’s progress and impact.

    Benefits tracking enables you to measure the effectiveness of your project and make adjustments where necessary to realize expected benefits. This tool will help you track benefit metrics at regular intervals to report progress on goals and identify benefits that are not being realized so that you can take remedial action.

    • Track and Measure Benefits Tool

    Infographic

    Workshop: Create a Data Management Roadmap

    Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

    1 Develop Data Strategies

    The Purpose

    Understand the business’s vision for data and the role of the data management practice.

    Determine business requirements for data.

    Map business goals and strategic plans to create data strategies.

    Key Benefits Achieved

    Understanding of business’s vision for data

    Unified vision for data management (business and IT)

    Identification of the business’s data strategies

    Activities

    1.1 Establish business context for data management.

    1.2 Develop data management principles and scope.

    1.3 Develop conceptual data model (subject areas).

    1.4 Discuss strategic information needs for each subject area.

    1.5 Develop data strategies.

    1.6 Identify data management strategies and enablers.

    Outputs

    Practice vision

    Data management guiding principles

    High-level data requirements

    Data strategies for key data assets

    2 Assess Data Management Capabilities

    The Purpose

    Determine the current and target states of your data management practice.

    Key Benefits Achieved

    Clear understanding of current environment

    Activities

    2.1 Determine the role and scope of data management within the organization.

    2.2 Assess current data management capabilities.

    2.3 Set target data management capabilities.

    2.4 Identify performance gaps.

    Outputs

    Data management scope

    Data management capability assessment results

    3 Analyze Gaps and Develop Improvement Initiatives

    The Purpose

    Identify how to bridge the gaps between the organization’s current and target environments.

    Key Benefits Achieved

    Creation of key strategic plans for data management

    Activities

    3.1 Evaluate performance gaps.

    3.2 Identify improvement initiatives.

    3.3 Create preliminary improvement plans.

    Outputs

    Data management improvement initiatives

    4 Design Roadmap and Plan Implementation

    The Purpose

    Create a realistic and action-oriented plan for implementing and improving the capabilities for data management.

    Key Benefits Achieved

    Completion of a Data Management Roadmap

    Plan for how to implement the roadmap’s initiatives

    Activities

    4.1 Align data management initiatives to data strategies and business drivers.

    4.2 Identify dependencies and priorities

    4.3 Build a data management roadmap (short and long term)

    4.4 Create a communication plan

    Outputs

    Data management roadmap

    Action plan

    Communication plan

    Further reading

    Contents

    Executive Brief
    Analyst Perspective
    Executive Summary
    Phase 1: Build Business and User Context
    Phase 2: Assess Data Management and Build Your Roadmap
    Additional Support
    Related Research
    Bibliography

    Create a Data Management Roadmap

    Ensure the right capabilities to support your data strategy.

    EXECUTIVE BRIEF

    Analyst Perspective

    Establish a data management program to realize the data strategy vision and data-driven organization.

    Data is one of the most valuable organizational assets, and data management is the foundation – made up of plans, programs, and practices – that delivers, secures, and enhances the value of those assets.

    Digital transformation in how we do business and innovations like artificial intelligence and automation that deliver exciting experiences for our customers are all powered by readily available, trusted data. And there’s so much more of it.

    A data management roadmap designed for where you are in your business journey and what’s important to you provides tangible answers to “Where do we start?” and “What do we do?”

    This blueprint helps you build and enhance data management capabilities as well as identify the next steps for evaluating, strengthening, harmonizing, and optimizing these capabilities, aligned precisely with business objectives and data strategy.

    Andrea Malick
    Director, Research & Advisory, Data & Analytics Practice
    Info-Tech Research Group

    Frame the problem

    Who this research is for
    • Data management professionals looking to improve the organization’s ability to leverage data in value-added ways
    • Data governance managers and data analysts looking to improve the effectiveness and value of their organization’s data management practice
    This research will help you
    • Align data management plans with business requirements and strategic plans.
    • Create a collaborative plan that unites IT and the business in managing the organization’s data assets.
    • Design a data management program that can scale and evolve over time.
    This research will also assist
    • Business leaders creating plans to leverage data in their strategic planning and business processes
    • IT professionals looking to improve the environment that manages and delivers data
    This research will also help you
    • Perform data strategy planning and incorporate data capabilities and plans into your broader plans.
    • Identify gaps in current data services and the supporting environment and determine effective corrective actions.

    Executive Summary

    Your Challenge
    • The organizational appetite for data is increasing, with growing demands for data to better support business processes and inform decision making.
    • For data to be accessible and trustworthy for the business it must be effectively managed throughout its lifecycle.
    • With so much data circulating throughout our systems and a steady flow via user activity and business activities, it is imperative that we understand our data environment, focus our data services and oversight on what really matters, and work closely with business leads to ensure data is an integral part of the digital solution.
    Common Obstacles
    • Despite the growing focus on data, many organizations struggle to develop an effective strategy for managing their data assets.
    • Successful management and consistent delivery of data assets throughout their lifecycle requires the collaboration of the business and IT and the balance of technology, process, and resourcing solutions.
    • Employees are doing their best to just get things done with their own spreadsheets and familiar patterns of behavior. It takes leadership to pause those patterns and take a thoughtful enterprise and strategic approach to a more streamlined – and transformed – business data service.
    Info-Tech’s Approach
    • Incremental approach: Building a mature and optimized practice doesn’t occur overnight – it takes time and effort. Use this blueprint’s approach and roadmap results to support your organization in building a practice that prioritizes scope, increases the effectiveness of your data management practice, and improves your alignment with business data needs.
    • Build smart: Don’t do data management for data management’s sake; instead, align it to business requirements and the business’ vision for the organization’s data. Ensure initiatives and program investments best align to business priorities and support the organization in becoming more data driven and data centric.

    Info-Tech Insight

    Use value streams and business capabilities to develop a prioritized and practical data management plan that provides the highest business satisfaction in the shortest time.

    Full page illustration of the 'Create a Data Management Roadmap' using the image of a cargo ship labelled 'Data Management' moving in the direction of 'Business Strategy'. The caption at the top reads 'Data Management capabilities create new business value by augmenting data & optimizing it for analytics. Data is a digital imprint of organizational activities.'

    Data Management Capabilities

    A similar concept to the last one, with a ship moving toward 'Business Strategy', except the ship is cross-sectioned with different capabilities filling the interior of the silhouette. Below are different steps in data management 'Data Creation', 'Data Ingestion', 'Data Accumulation, 'Data Augmentation', 'Data Delivery', and 'Data Consumption'.

    Data is a business asset and needs to be treated like one

    Data management is an enabler of the business and therefore needs to be driven by business goals and objectives. For data to be a strategic asset of the business, the business and IT processes that support its delivery and management must be mature and clearly executed.

    Business Drivers
    1. Client Intimacy/Service Excellence
    2. Product and Service Innovations
    3. Operational Excellence
    4. Risk and Compliance Management
    Data Management Enablers
    • Data Governance
    • Data Strategy Planning
    • Data Architecture
    • Data Operations Management
    • Data Risk Management
    • Data Quality Management

    Industry spotlight: Risk management in the financial services sector

    REGULATORY
    COMPLIANCE

    Regulations are the #1 driver for risk management.

    US$11M:

    Fine incurred by a well-known Wall Street firm after using inaccurate data to execute short sales orders.
    “To successfully leverage customer data while maintaining compliance and transparency, the financial sector must adapt its current data management strategies to meet the needs of an ever-evolving digital landscape.” (Phoebe Fasulo, Security Scorecard, 2021)

    Industry spotlight: Operational excellence in the public sector

    GOVERNMENT
    TRANSPARENCY

    With frequent government scandals and corruption dominating the news, transparency to the public is quickly becoming a widely adopted practice at every level of government. Open government is the guiding principle that the public has access to the documents and proceedings of government to allow for effective public oversight. With growing regulations and pressure from the public, governments must adopt a comprehensive data management strategy to ensure they remain accountable to their rate payers, residents, businesses, and other constituents.

    1. Transparency Transparency is not just about access; it’s about sharing and reuse.
    2. Social and commercial value Everything from finding your local post office to building a search engine requires access to data.
    3. Participatory government Open data enables citizens to be more directly informed and involved in decision making.

    Industry spotlight: Operational excellence and client intimacy in major league sports

    SPORTS
    ANALYTICS

    A professional sports team is essentially a business that is looking for wins to maximize revenue. While they hope for a successful post-season, they also need strong quarterly results, just like you. Sports teams are renowned for adopting data-driven decision making across their organizations to do everything from improving player performance to optimizing tickets sales. At the end of the day, to enable analytics you must have top-notch information management.

    Team Performance Benefits
    1. Talent identification
    2. In-game decision making
    3. Injury reduction
    4. Athlete performance
    5. Bargaining agreement
    Team Performance Benefits
    1. Fan engagement
    2. Licensing
    3. Sports gambling
    (Deloitte Insights, 2020)
    Industry leaders cite data, and the insights they glean from it, as their means of standing apart from their competitors.

    Industry spotlight: Operational excellence and service delivery within manufacturing and supply chain services

    SUPPLY CHAIN
    EFFICIENCY

    Data offers key insights and opportunities when it comes to supply chain management. The supply chain is where the business strategy gets converted to operational service delivery of the business. Proper data management enables business processes to become more efficient, productive, and profitable through the greater availability of quality data and analysis.

    Fifty-seven percent of companies believe that supply chain management gives them a competitive advantage that enables them to further develop their business (FinancesOnline, 2021).

    Involving Data in Your Supply Chain

    25%

    Companies can reap a 25% increase in productivity, a 20% gain in space usage, and a 30% improvement in stock use efficiency if they use integrated order processing for their inventory system.

    36%

    Thirty-six percent of supply chain professionals say that one of the top drivers of their analytics initiatives is the optimization of inventory management to balance supply and demand.
    (Source: FinancesOnline, 2021)

    Industry spotlight: Intelligent product innovation and strong product portfolios differentiate consumer retailers and CPGs

    INFORMED PRODUCT
    DEVELOPMENT
    Consumer shopping habits and preferences are notoriously variable, making it a challenge to develop a well-received product. Information and insights into consumer trends, shopping preferences, and market analysis support the probability of a successful outcome.

    Maintaining a Product Portfolio
    What is selling? What is not selling?

    Product Development
    • Based on current consumer buying patterns, what will they buy next?
    • How will this product be received by consumers?
    • What characteristics do consumers find important?
    A combination of operational data and analytics data is required to accurately answer these questions.
    Internal Data
    • Organizational sales performance
    External Data
    • Competitor performance
    • Market analysis
    • Consumer trends and preferences
    Around 75% of ideas fail for organizational reasons – viability or feasibility or time to market issues. On the other hand, around 20% of product ideas fail due to user-related issues – not valuable or usable (Medium, 2020).

    Changes in business and technology are changing how organizations use and manage data

    The world moves a lot faster today

    Businesses of today operate in real time. To maintain a competitive edge, businesses must identify and respond quickly to opportunities and events.

    To effectively do this businesses must have accurate and up-to-date data at their fingertips.

    To support the new demands around data consumption, data velocity (pace in which data is captured, organized, and analyzed) must also accelerate.

    Data Management Implications
    • Strong integration capabilities
    • Intelligent and efficient systems
    • Embedded data quality management
    • Strong transparency into the history of data and its transformation

    Studies and projections show a clear case of how data and its usage will grow and evolve.

    Zettabyte Era

    64.2

    More Data

    The amount of data created, consumed, and stored globally is forecast to increase rapidly, reaching 64.2 zettabytes in 2020 and projected to grow to over 180 zettabyes in 2025 (Statista, 2021).

    Evolving Technologies

    $480B

    Cloud Proliferation

    Global end-user spending on public cloud services is expected to exceed $480 billion next year (Info-Tech, 2021).

    To differentiate and remain competitive in today’s marketplace, organizations are becoming more data-driven

    Pyramid with a blue tip. Sublevels from top down are labelled 'Analytical Companies', 'Analytical Aspirations', 'Localized Analytics', and 'Analytically Impaired'.

    Analytic Competitor

    “Given the unforgiving competitive landscape, organizations have to transform now, and correctly. Winning requires an outcome-focused analytics strategy.” (Ramya Srinivasan, Forbes, 2021)
    Data and the use of data analytics has become a centerpiece to effective modern business. Top-performing organizations across a variety of industries have been cited as using analytics five times more than lower performers (MIT Sloan).

    The strategic value of data

    Power intelligent and transformative organizational performance through leveraging data.

    Respond to industry disruptors

    Optimize the way you serve your stakeholders and customers

    Develop products and services to meet ever-evolving needs

    Manage operations and mitigate risk

    Harness the value of your data

    Despite investments in data initiatives, organizations are carrying high levels of data debt

    Data debt is the accumulated cost that is associated with the suboptimal governance of data assets in an enterprise, like technical debt.

    Data debt is a problem for 78% of organizations.

    40%

    of organizations say individuals within the business do not trust data insights.

    66%

    of organizations say a backlog of data debt is impacting new data management initiatives.

    33%

    of organizations are not able to get value from a new system or technology investment.

    30%

    of organizations are unable to become data-driven.

    (Source: Experian, 2020)

    The journey to being data-driven

    The journey to becoming a data-driven organization requires a pit stop at data enablement.

    The Data Economy

    Diagram of 'The Data Economy' with three points on an arrow. 'Data Disengaged: You have a low appetite for data and rarely use data for decision making.' 'Data Enabled: Technology, data architecture, and people and processes are optimized and supported by data governance.' 'Data Driven: You are differentiating and competing on data and analytics, described as a “data first” organization. You’re collaborating through data. Data is an asset.'

    Measure success to demonstrate tangible business value

    Put data management into the context of the business:
    • Tie the value of data management and its initiatives back to the business capabilities that are enabled.
    • Leverage the KPIs of those business capabilities to demonstrate tangible and measurable value. Use terms and language that will resonate with senior leadership.

    Don’t let measurement be an afterthought:

    Start substantiating early on how you are going to measure success as your data management program evolves.

    Build a right-sized roadmap

    Formulate an actionable roadmap that is right-sized to deliver value in your organization.

    Key considerations:
    • When building your data management roadmap, ensure you do so through an enterprise lens. Be cognizant of other initiatives that might be coming down the pipeline that may require you to align your data governance milestones accordingly.
    • Apart from doing your planning with consideration for other big projects or launches that might be in-flight and require the time and attention of your data management partners, also be mindful of the more routine yet still demanding initiatives.
    • When doing your roadmapping, consider factors like the organization’s fiscal cycle, typical or potential year-end demands, and monthly/quarterly reporting periods and audits. Initiatives such as these are likely to monopolize the time and focus of personnel key to delivering on your data management milestones
    Sample milestones:
    • Data Management Leadership & Org Structure Definition
      Define the home for data management, as approved by senior leadership.
    • Data Management Charter and Policies
      Create a charter for your program and build/refresh associated policies.
    • Data Culture Diagnostic
      Understand the organization’s current data culture, perception of data, value of data, and knowledge gaps.
    • Use Case Build and Prioritization
      Build a use case that is tied to business capabilities. Prioritize accordingly.
    • Business Data Glossary/Catalog
      Build and/or refresh the business’ glossary for addressing data definitions and standardization issues.
    • Tools & Technology
      Explore the tools and technology offering in the data management space that would serve as an enabler to the program (e.g. RFI, RFP).

    Insight summary

    Overarching insight

    Your organization’s value streams and the associated business capabilities require effectively managed data. Whether building customer service excellence or getting ahead of cyberattacks, a data management practice is the dependable mainstay supporting business operations and transformation.

    Insight 1

    Data – it’s your business.
    Data is a digital imprint of business activities. Data architecture and flows are reflective of the organizational business architecture. Take data management capabilities as seriously as other core business capabilities.

    Insight 2

    Take a data-oriented approach.
    Data management must be data-centric – with technology and functional enablement built around the data and its structure and flows. Maintain the data focus during project’s planning, delivery, and evaluation stages.

    Insight 3

    Get the business into the data business.
    Data is not “IT’s thing.” Just as a bank helps you properly allocate your money to achieve your financial goals, IT will help you implement data management to support your business goals, but the accountability for data resides with the business.

    Tactical insight

    Data management is the program and environment we build once we have direction, i.e. a data strategy, and we have formed an ongoing channel with the guiding voice of the business via data governance. Without an ultimate goal in a strategy or the real requirements of the business, what are we building data systems and processes for? We are used to tech buzz words and placing our hope in promising innovations like artificial intelligence. There are no shortcuts, but there are basic proven actions we can take to meet the digital revolution head on and let our data boost our journey.

    Key deliverable:

    Data Management Roadmap Template

    Use this template to guide you in translating your project's findings and outcomes into a presentation that can be shared with your executive team and project sponsors.

    Sample of the 'Data Management Roadmap Template' key deliverable.

    Blueprint deliverables

    Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

    Data Management Assessment and Planning Tool

    Use this tool to support your team in assessing and designing the capabilities and components of your organization's data management practice. Sample of the 'Data Management Assessment and Planning Tool' deliverable.

    Data Culture Diagnostic and Scorecard

    Sample of the 'Data Culture Diagnostic and Scorecard' deliverable.

    Leverage Info-Tech’s Data Culture Diagnostic to understand how your organization scores across 10 areas relating to data culture.

    Business Capability Map

    This template takes you through a business capability and value stream mapping to identify the data capabilities required to enable them. Sample of the 'Business Capability Map' deliverable.

    Measure the value of this blueprint

    Leverage this blueprint’s approach to ensure your data management initiatives align and support your key value streams and their business capabilities.
    • Aligning your data management program and its initiatives to your organization’s business capabilities is vital for tracing and demonstrating measurable business value for the program.
    • This alignment of data management with value streams and business capabilities enables you to use business-defined KPIs and demonstrate tangible value.

    Project outcome

    Metric

    Timely data delivery Time of data delivery to consumption
    Improved data quality Data quality scorecard metrics
    Data provenance transparency Time for data auditing (from report/dashboard to the source)
    New reporting and analytic capabilities Number of level 2 business capabilities implemented as solutions
    In Phase 1 of this blueprint, we will help you establish the business context, define your business drivers and KPIs, and understand your current data management capabilities and strengths.

    In Phase 2, we will help you develop a plan and a roadmap for addressing any gaps and improving the relevant data management capabilities so that data is well positioned to deliver on those defined business metrics.

    Info-Tech offers various levels of support to best suit your needs

    DIY Toolkit

    Guided Implementation

    Workshop

    Consulting

    "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful." "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track." "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place." "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

    Diagnostics and consistent frameworks used throughout all four options

    Create a Data Management Roadmap project overview

    1. Build Business Context and Drivers for the Data Management Program 2. Assess Data Management and Build Your Roadmap
    Best-Practice Toolkit

    1.1 Review the Data Management Framework

    1.2 Understand and Align to Business Drivers

    1.3 Build High-Value Use Cases

    1.4 Create a Vision

    2.1 Assess Data Management

    2.2 Build Your Data Management Roadmap

    2.3 Organize Business Data Domains

    Guided Implementation
    • Call 1
    • Call 2
    • Call 3
    • Call 4
    • Call 5
    • Call 6
    • Call 7
    • Call 8
    • Call 9
    Phase Outcomes
    • An understanding of the core components of an effective data management program
    • Your organization’s business capabilities and value streams
    • A business capability map for your organization
    • High-value use cases for data management
    • Vision and guiding principles for data management
    • An understanding of your organization’s current data management capabilities
    • Definition of target-state capabilities and gaps
    • Roadmap of priority data management initiatives
    • Business data domains and ownership

    Guided Implementation

    A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

    A typical GI is 8 to 12 calls over the course of 4 to 6 months.

    What does a typical GI on this topic look like?

    Phase 1

    Phase 2

    Call #1: Understand drivers, business context, and scope of data management at your organization. Learn about Info-Tech’s approach and resources.

    Call #2: Get a detailed overview of Info-Tech’s approach, framework, Data Culture Diagnostic, and blueprint.

    Call #3:Align your business capabilities with your data management capabilities. Begin to develop a use case framework.

    Call #4:Further discuss alignment of business capabilities to data management capabilities and use case framework.

    Call #5: Assess your current data management capabilities and data environment. Review your Data Culture Diagnostic Scorecard, if applicable.

    Call #6: Plan target state and corresponding initiatives.

    Call #7: Identify program risks and formulate a roadmap.

    Call #8: Identify and prioritize improvements. Define a RACI chart.

    Call #9: Summarize results and plan next steps.

    Workshop Overview

    Contact your account representative for more information.
    workshops@infotech.com1-888-670-8889
    Day 1 Day 2 Day 3 Day 4 Day 5
    Activities
    Understand and contextualize

    1.1 Review your data strategy.

    1.2 Learn data management capabilities.

    1.3 Discuss DM capabilities cross-dependencies and interactions.

    1.4 Develop high-value use cases.

    Assess current DM capabilities and set improvement targets

    2.1 Assess you current DM capabilities.

    2.2 Set targets for DM capabilities.

    Formulate and prioritize improvement initiatives

    3.1 Formulate core initiatives for DM capabilities improvement.

    3.2 Discuss dependencies across the initiatives and prioritize them.

    Plan for delivery dates and assign RACI

    4.1 Plan dates and assign RACI for the initiatives.

    4.2 Brainstorm initiatives to address gaps and enable business goals.

    Next steps and wrap-up (offsite)

    5.1 Complete in-progress deliverables from previous four days.

    5.2 Set up review time for workshop deliverables and to discuss next steps.

    Deliverables
    1. Understanding of the data management capabilities and their interactions and logical dependencies
    2. Use cases
    1. DM capability assessment results
    2. DM vision and guiding principles
    1. Prioritized DM capabilities improvement initiatives
    1. DM capabilities improvement roadmap
    2. Business data domains and ownership
    1. Workshop final report with key findings and recommendations

    Full page diagram of the 'Data & Analytics landscape'. Caption reads 'The key to landscaping your data environment lies in ensuring foundational disciplines are optimized in a way that recognizes the interdependency among the various disciplines.' Many foundational disciplines are color-coded to a legend determining whether its 'accountability sits with IT' or 'with the business; CDO'. An arrow labeled 'You Are Here' points to 'Data Management', which is coded in both colors meaning both IT and the business are accountable.

    What is data management and why is it needed?

    “Data management is the development, execution, and supervision of plans, policies, programs and practices that deliver, control, protect and enhance the value of data and information assets throughout their lifecycles.” (DAMA International, 2017)

    Achieving successful management and consistent delivery of data assets throughout their lifecycle requires the collaboration of the business and IT and the balance of technology, process, and resourcing solutions.

    Who:

    This research is designed for:
    • Data management heads and professionals looking to improve their organization’s ability to leverage data in value-added ways.
    • Data management and IT professionals looking to optimize the data environment, from creation and ingestion right through to consumption.

    Are your data management capabilities optimized to support your organization’s data use and demand?

    What is the current situation?

    Situation
    • The volume and variety of data are growing exponentially and show no sign of slowing down.
    • Business landscapes and models are evolving.
    • Users and stakeholders are becoming more and more data-centric, with maturing and demanding expectations.
    Complication
    • Organizations struggle to develop a comprehensive approach to optimizing data management.
    • In their efforts to keep pace with the demands for data, data management groups often adopt a piecemeal approach that includes turning to tools as a means to address the needs.
    • Data architecture, models, and designs fail to deliver real and measurable business impact and value. Technology ROI is not realized.
    Info-Tech Insight

    A data strategy should never be formulated disjointed from the business. Ensure the data strategy aligns with the business strategy and supports the business architecture.

    Info-Tech’s Data Management Framework

    What Is Data Management?

    Data management is the development, execution, and supervision of plans, policies, programs and practices that deliver, control, protect and enhance the value of data and information assets throughout their lifecycles.” (DAMA International, 2017)

    The three-tiered Data Management Framework, tiers are labelled 'Data Management Enablers', 'Information Dimensions', and 'Business Information'.

    Adapted from DAMA-DMBOK and Advanced Knowledge Innovations Global Solutions

    Info-Tech’s Approach

    Info-Tech’s Data Management Framework is designed to show how an organization’s business model sits as the foundation of its data management practice. Drawing from the requirements of the underpinning model, a practice is designed and maintained through the creation and application of the enablers and dimensions of data management.

    Build a data management practice that is centered on supporting the business and its use of key data assets

    Business Resources

    Data subject areas provide high-level views of the data assets that are used in business processes and enable an organization to perform its business functions.

    Classified by specific subjects, these groups reflect data elements that, when used effectively, are able to support analytical and operational use cases of data.

    This layer is representative of the delivery of the data assets and the business’ consumption of the data.

    Data is an integral business asset that exists across all areas of an organization

    Equation stating 'Trustworthy and Usable Data' plus 'Well-Designed and Executed Processes' equals 'Business Capabilities and Functions'.
    Data Management Framework with only the bottom tier highlighted.

    For a data management practice to be effective it ultimately must show how its capabilities and operations better support the business in accessing and leveraging its key data assets.*

    *This project focuses on building capabilities for data management. Leverage our data quality management research to support you in assessing the performance of this model.

    Information dimensions support the different types of data present within an organization’s environment

    Information Dimensions

    Components at the Information Dimensions layer manage the different types of data and information present with an environment.

    At this layer, data is managed based on its type and how the business is looking to use and access the data.

    Custom capabilities are developed at this level to support:

    • Structured data
    • Semi-structured data
    • Unstructured data
    The types, formats, and structure of the data are managed at this level using the data management enablers to support their successful execution and performance.
    Data Management Framework with only the middle tier highlighted.

    Build a data management practice with strong process capabilities

    Use these guiding principles to contextualize the purpose and value for each data management enabler.

    Data Management Framework with only the top tier highlighted.

    Data Management Enablers

    Info-Tech categorizes data management enablers as the processes that guide the management of the organization’s data assets and support the delivery.

    Govern and Direct

    • Ensures data management practices and processes follow the standards and policies outlined for them
    • Manages the executive oversight of the broader practice

    Align and Plan

    • Aligns data management plans to the business’ data requirements
    • Creates the plans to guide the design and execution of data management components

    Build, Acquire, Operate, Deliver, and Support

    • Executes the operations that manage data as it flows through the business environment
    • Manages the business’ risks in relation to its data assets and the level of security and access required

    Monitor and Improve

    • Analyzes the performance of data management components and the quality of business data
    • Creates and execute plans to improve the performance of the practice and the quality and use of data assets

    Use Info-Tech’s assessment framework to support your organization’s data management planning

    Info-Tech employs a consumer-driven approach to requirements gathering in order to support a data management practice. This will create a vision and strategic plan that will help to make data an enabler to the business as it looks to achieve its strategic objectives.

    Data Strategy Planning

    To support the project in building an accurate understanding of the organization’s data requirements and the role of data in its operations (current and future), the framework first guides organizations on a business and subject area assessment.

    By focusing on data usage and strategies for unique data subject areas, the project team will be better able to craft a data management practice with capabilities that will generate the greatest value and proactively handle evolving data requirements.

    Arrow pointing right.

    Data Management Assessment

    To support the design of a fit-for-purpose data management practice that aligns with the business’ data requirements this assessment will guide you in:

    • Determining the target capabilities for the different dimensions of data management.
    • Identifying the interaction dependencies and coordination efforts required to build a successful data management practice.

    Create a Data Management Roadmap

    Phase 1

    Build Business Context and Drivers for the Data Management Program

    Phase 1

    1.1 Review the Data Management Framework

    1.2 Understand and Align to Business Drivers

    1.3 Build High-Value Use Cases

    1.4 Create a Vision

    Phase 2

    2.1 Assess Data Management

    2.2 Build Your Data Management Roadmap

    2.3 Organize Business Data Domains

    This phase will walk you through the following activities:

    • Identify your business drivers and business capabilities.
    • Align data management capabilities with business goals.
    • Define scope and vision of the data management plan.
    • This phase involves the follow

    This phase involves the following participants:

    • Data Management Lead/Information Management Lead, CDO, Data Lead
    • Senior Business Leaders
    • Business SMEs
    • Data Owners, Records Managers, Regulatory Subject Matter Experts (e.g. Legal Counsel, Security)

    Step 1.1

    Review the Data Management Framework

    Activities

    1.1.1 Walk through the main parts of the best-practice Data Management Framework

    This step will guide you through the following activities:

    • Understand the main disciplines and makeup of a best-practice data management program.
    • Determine which data management capabilities are considered high priority by your organization.

    Outcomes of this step

    • A foundation for data management initiative planning that’s aligned with the organization’s business architecture: value streams, business capability map, and strategy map
    Build Business Context and Drivers
    Step 1.1 Step 1.2 Step 1.3 Step 1.4

    Full page diagram of the 'Data & Analytics landscape'. Caption reads 'The key to landscaping your data environment lies in ensuring foundational disciplines are optimized in a way that recognizes the interdependency among the various disciplines.' Many foundational disciplines are color-coded to a legend determining whether its 'accountability sits with IT' or 'with the business; CDO'. An arrow labeled 'You Are Here' points to 'Data Management', which is coded in both colors meaning both IT and the business are accountable.

    Full page illustration of the 'Create a Data Management Roadmap' using the image of a cargo ship labelled 'Data Management' moving in the direction of 'Business Strategy'. The caption at the top reads 'Data Management capabilities create new business value by augmenting data & optimizing it for analytics. Data is a digital imprint of organizational activities.'

    Data Management Capabilities

    A similar concept to the last one, with a ship moving toward 'Business Strategy', except the ship is cross-sectioned with different capabilities filling the interior of the silhouette. Below are different steps in data management 'Data Creation', 'Data Ingestion', 'Data Accumulation, 'Data Augmentation', 'Data Delivery', and 'Data Consumption'.

    Build a Robust & Comprehensive Data Strategy

    Business Strategy

    Organizational Goals & Objectives

    Business Drivers

    Industry Drivers

    Current Environment

    Data Management Capability Maturity Assessment

    Data Culture Diagnostic

    Regulatory and Compliance Requirements

    Data Strategy

    Organizational Drivers and Data Value

    Data Strategy Objectives & Guiding Principles

    Data Strategy Vision and Mission

    Data Strategy Roadmap

    People: Roles and Organizational Structure

    Data Culture & Data Literacy

    Data Management and Tools

    Risk and Feasibility

    Unlock the Value of Data

    Generate Game-Changing Insights

    Fuel Data-Driven Decision Making

    Innovate and Transform With Data

    Thrive and Differentiate With a Data-Driven Culture

    Elevate Organizational Data IQ

    Build a Foundation for Data Valuation

    What is a data strategy and why is it needed?

    • Your data strategy is the vehicle for ensuring data is poised to support your organization’s strategic objectives.
    • For any CDO or equivalent data leader, a robust and comprehensive data strategy is the number one tool in your toolkit for generating measurable business value from data.
    • The data strategy will serve as the mechanism for making high-quality, trusted, and well-governed data readily available and accessible to deliver on your organizational mandate.

    What is driving the need to formulate or refresh your organization’s data strategy?

    Who:

    This research is designed for:

    • Chief Data Officer (CDO) or equivalent
    • Head of Data
    • Chief Analytics Officer (CAO)
    • Head of Digital Transformation
    • CIO

    Info-Tech Insight

    A data strategy should never be formulated disjointed from the business. Ensure the data strategy aligns with the business strategy and supports the business architecture.

    Info-Tech’s Data Governance Framework

    Model of Info-Tech's Data Governance Framework titled 'Key to Data Enablement'. There are inputs, a main Data Governance cycle, and a selection of outputs. The inputs are 'Business Strategy' and 'Data Strategy' injected into the cycle via 'Strategic Goals & Objectives'. The cycle consists of 'Operating Model', 'Policies & Procedures', 'Data Literacy & Culture', 'Enterprise Projects & Services', 'Data Management', 'Data Privacy & Security', 'Data Leadership', and 'Data Ownership & Stewardship'. The latter two are part of 'Enterprise Governance's 'Oversight & Alignment' cycle. Outputs are 'Defined Data Accountability & Responsibility', 'Knowledge & Common Understanding of Data Assets', 'Trust & Confidence in Traceable Data', 'Improved Data ROI & Reduced Data Debt', and 'Support of Ethical Use of Data in a Data-Driven Culture'.

    What is data governance and why is it needed?

    • Data governance is an enabling framework of decision rights, responsibilities, and accountabilities for data assets across the enterprise.
    • It should deliver agreed-upon models that are conducive to your organization’s operating culture, where there is clarity on who can do what with which data and via what means.
    • It is the key enabler for bringing high-quality, trusted, secure, and discoverable data to the right users across your organization.
    • It promotes and drives responsible and ethical use and handling of data while helping to build and foster an organizational culture of data excellence.

    Do you feel there is a clear definition of data accountability and responsibility in your organization?

    Who:

    This research is designed for:

    • Chief Data Officer (CDO) or equivalent
    • Head of Data Governance, Lead Data Governance Officer
    • Head of Data
    • Head of Digital Transformation
    • CIO

    Info-Tech Insight

    Data governance should not sit as an island in your organization. It must continuously align with the organization’s enterprise governance function.

    A diagram titled 'Data Platform Selection - Make complex tasks simple by applying proven methodology to connect businesses to software' with five steps. '1. Formalize a Business Strategy', '2. Identify Platform Specific Considerations', '3. Execute Data Platform Architecture Selection', 'Select Software', 'Achieve Business Goals'.

    Info-Tech’s Data Platform Framework

    Data pipeline for versatile and scalable data delivery

    a diagram showing the path from 'Data Creation' to 'Data Accumulation', to 'Engineering & Augmentation', to 'Data Delivery'. Each step has a 'Fast Lane', 'Operational Lane', and 'Curated Lane'.

    What are the data platform and practice and why are they needed?

    • The data platform and practice are two parts of the data and analytics equation:
      • The practice is about the operating model for data; that is, how stakeholders work together to deliver business value on your data platform. These stakeholders are a combination of business and IT from across the organization.
      • The platform is a combination of the architectural components of the data and analytics landscape that come together to support the role the business plays day to day with respect to data.
    • Don’t jump directly into technology: use Info-Tech tools to solve and plan first.
    • Create a continuous roadmap to implement and evolve your data practice and platform.
    • Promote collaboration between the business and IT by clearly defining responsibilities.

    Does your data platform effectively serve your reporting and analytics capabilities?

    Who:

    This research is designed for:

    • Data and Information Leadership
    • Enterprise Information Architect
    • Data Architect
    • Data Engineer/Modeler

    Info-Tech Insight

    Info-Tech’s approach is driven by business goals and leverages standard data practice and platform patterns. This enables the implementation of critical and foundational data and analytics components first and subsequently facilitates the evolution and development of the practice and platform over time.

    Info-Tech’s Reporting and Analytics Framework

    Formulating an enterprise reporting and analytics strategy requires the business vision and strategies to first be substantiated. Any optimization to the data warehouse, integration, and source layers is in turn driven by the enterprise reporting and analytics strategy.
    A diagram of the 'Reporting and Analytics Framework' with 'Business vision/strategies' fed through four stages beginning with 'Business Intelligence: Reporting & Analytics Strategy', 'Data Warehouse: Data Warehouse/ Data Lake Strategy', 'Integration and Translation: Data Integration Strategy', 'Sources: Source Strategy (Content/Quality)'
    The current states of your integration and warehouse platforms determine what data can be used for BI and analytics.
    Your enterprise reporting and analytics strategy is driven by your organization’s vision and corporate strategy.

    What is reporting and analytics and why is it needed?

    • Reporting and analytics bridges the gap between an organization’s data assets and consumable information that facilitates insight generation and informed or evidence-based decision making.
    • The reporting and analytics strategy drives data warehouse and integration strategies and the data needs to support business decisions.
    • The reporting and analytics strategy ensures that the investment made in optimizing the data environment to support reporting and analytics is directly aligned with the organization’s needs and priorities and hence will deliver measurable business value.

    Do you have a strategy to enable self-serve analytics? What does your operating model look like? Have you an analytics CoE?

    Who:

    This research is designed for:

    • Head of BI and Analytics
    • CIO or Business Unit (BU) Leader looking to improve reporting and analytics
    • Applications Lead

    Info-Tech Insight

    Formulating an enterprise reporting and analytics strategy requires the business vision and strategies to first be substantiated. Any optimization to the data warehouse, integration, and source layer is in turn driven by the enterprise reporting and analytics strategy.

    Info-Tech’s Data Architecture Framework

    Info-Tech’s methodology:
      1. Prioritize your core business objectives and identify your business driver.
      2. Learn how business drivers apply to specific tiers of Info-Tech’s five-tier data architecture model.
      3. Determine the appropriate tactical pattern that addresses your most important requirements.
    Visual diagram of the first two parts of the methodology on the left. Objectives apply to the data architecture model, which appropriates tactical patterns, which leads to a focus.
      1. Select the areas of the five-tier architecture to focus on.
      2. Measure your current state.
      3. Set the targets of your desired optimized state.
      1. Roadmap your tactics.
      2. Manage and communicate change.
    Visual diagram of the third part of the methodology on the left. A roadmap of tactics leads to communicating change.

    What is data architecture and why is it needed?

    • Data architecture is the set of rules, policies, standards, and models that govern and define the type of data collected and how it is used, stored, managed, and integrated within the organization and its database systems.
    • In general, the primary objective of data architecture is the standardization of data for the benefit of the organization.

    Is your architecture optimized to sustainably deliver readily available and accessible data to users?

    Who:

    This research is designed for:

    • Data Architects or their equivalent
    • Enterprise Architects
    • Head of Data
    • CIO
    • Database Administrators

    Info-Tech Insight

    Data architecture is not just about models. Viewing data architecture as just technical data modeling can lead to a data environment that does not aptly serve or support the business. Identify your business’ priorities and adapt your data architecture to those needs.

    A diagram titled 'Build Your Data Quality Program'. '1. Data Quality & Data Culture Diagnostics Business Landscape Exercise', '2. Business Strategy & Use Cases', '3. Prioritize Use Cases With Poor Quality'. 'Info-Tech Insight: As data is ingested, integrated, and maintained in the various streams of the organization's system and application architecture, there are multiple points where the quality of the data can degrade.' A data flow diagram points out how 'Data quality issues can occur at any stage of the data flow', and that it is better to 'Fix data quality root causes here' during the 'Data Creation', 'Data Ingestion', and 'Data Accumulation & Engineering' stages in order 'to prevent expensive cures here' in the 'Data Delivery' and 'Reporting & Analytics' stages.

    What is data quality management and why is it needed?

    • Data is the foundation of decisions made at data-driven organizations.
    • Data quality management ensures that foundation is sustainably solid.
    • If there are problems with the organization’s underlying data, it can have a domino effect on many downstream business functions.
    • The transformational insights that executives are constantly seeking can be uncovered by a data quality practice that makes high-quality, trustworthy information readily available to the business users who need it.

    Do your users have an optimal level of trust and confidence in the quality of the organization’s data?

    Who:

    This research is designed for:

    • Chief Data Officer (CDO) or equivalent Head of Data
    • Chief Analytics Officer (CAO)
    • Head of Digital Transformation
    • CIO

    Info-Tech Insight

    Data quality suffers most at the point of entry. The resulting domino effect of error propagation makes these errors among the most costly forms of data quality errors. Fix data ingestion, whether through improving your application and database design or improving your data ingestion policy, and you will fix a majority of data quality issues.

    Info-Tech’s Enterprise Content Management Framework

    Drivers Governance Information Architecture Process Policy Systems Architecture
    Regulatory, Legal –›
    Efficiency, Cost-Effectiveness –›
    Customer Service –›
    User Experience –›
    • Establish decision-making committee
    • Define and formalize roles (RACI, charter)
    • Develop policies
    • Create business data glossary
    • Decide who approves documents in workflow
    • Operating models
    • Information categories (taxonomy)
    • Classifications, retention periods
    • Metadata (for findability and as tags in automated workflows)
    • Review and approval process, e.g. who approves
    • Process for admins to oversee performance of IM service
    • Process for capturing and classifying incoming documents
    • Audit trails and reporting process
    • Centralized index of data and records to be tracked and managed throughout their lifecycle
    • Data retention policy
    • E-signature policy
    • Email policy
    • Information management policies
    • Access/privacy rules
    • Understand the flow of content through multiple systems (e.g. email, repositories)
    • Define business and technical requirements to select a new content management platform/service
    • Improve integrations
    • Right-size solutions for use case (e.g. DAM)
    • Communication/Change Management
    • Data Literacy

    What is enterprise content management and why is it needed?

    “Enterprise Content Management is the systematic collection and organization of information that is to be used by a designated audience – business executives, customers, etc. Neither a single technology nor a methodology nor a process, it is a dynamic combination of strategies, methods and tools used to capture, manage, store, preserve and deliver information supporting key organizational processes through its entire lifecycle.” (AIIM, 2021)

    • Changing your ECM capabilities is about changing organizational behavior; take an all-hands-on-deck approach to make the most of information gathering, create a vested interest, and secure buy-in.
    • It promotes and drives responsible and ethical use and handling of content while helping to build and foster an organizational culture of information excellence.

    Who:

    This research is designed for:

    • Information Architect
    • Chief Data Officer (CDO)
    • Head of Data, Information Management
    • Records Management
    • CIO

    Info-Tech Insight

    ECM is critical to becoming a digital and modernized operation, where both structured data (such as sales reports) and unstructured content (such as customer sentiment in social media) are brought together for a 360-degree view of the customer or for a comprehensive legal discovery.

    Metadata management/Data cataloging

    Overview

    Metadata is structured information that describes, explains, locates, or otherwise makes it easier to retrieve, use, or manage an information resource. Metadata is often called data about data or information about information (NISO).

    Metadata management is the function that manages and maintains the technology and processes that creates, processes, and stores metadata created by business processes and data.

    90%

    The majority of data is unstructured information like text, video, audio, web server logs, social media, and more (MIT Sloan, 2021).
    As data becomes more unstructured, complex, and manipulated, the importance and value of metadata will grow exponentially and support improved:
    • Data consumption
    • Quality management
    • Risk management

    Value of Effective Metadata Management

    • Supports the traceability of data through an environment.
    • Creates standards and logging that enable information and data to be searchable and cataloged.
    • Metadata schemas enable easier transferring and distribution of data across different environments.
    Data about data: The true value of metadata and the management practices supporting it is its ability to provide deeper understanding and auditability to the data assets and processes of the business.
    Metadata supports the use of:
    Big Data
    Unstructured data
    Content and Documents
    Unstructured and semi-structured data
    Structured data
    Master, reference, etc.

    Critical Success Factors of Metadata Management

    • Consistent and documented data standards and definitions
    • Architectural planning for metadata
    • Incorporation of metadata into system design and the processing of data
    • Technology to support metadata creation, collection, storage, and reviews (metadata repository, meta marts, etc.)

    Info-Tech’s Data Integration Framework

    On one hand…

    Data has massive potential to bring insight to an organization when combined and analyzed in creative ways.

    On the other hand…

    It is difficult to bring data together from different sources to generate insights and prevent stale data.

    How can these two ideas be reconciled?

    Answer: Info-Tech’s Data Integration Onion Framework summarizes an organization’s data environment at a conceptual level and is used to design a common data-centric integration environment.

    A diagram of the 'Data Integration Onion Framework' with five layers: 'Enterprise Business Processes', 'Enterprise Analytics', 'Enterprise Integration', 'Enterprise Data Repositories', and 'Enterprise Data' at the center.
    Info-Tech’s Data Integration Onion Framework
    Data-centric integration is the solution you need to bring data together to break down data silos.

    What is data integration and why is it needed?

    • To get more value from their information, organizations are relying on increasingly more complex data sources. These diverse data sources have to be properly integrated to unlock the full potential of that data.
    • Integrating large volumes of data from the many varied sources in an organization has incredible potential to yield insights, but many organizations struggle with creating the right structure for that blending to take place, and that leads to the formation of data silos.
    • Data-centric integration capabilities can break down organizational silos. Once data silos are removed and all the information that is relevant to a given problem is available, problems with operational and transactional efficiencies can be solved, and value from business intelligence (BI) and analytics can be fully realized.

    Is your integration near real time and scalable?

    Who:

    This research is designed for:

    • Data Engineers
    • Business Analysts
    • Data Architects
    • Head of Data Management
    • Enterprise Architects

    Info-Tech Insight

    Every IT project requires data integration. Any change in the application and database ecosystem requires you to solve a data integration problem.

    Info-Tech’s Master Data Management Framework

    Master data management (MDM) “entails control over Master Data values and identifiers that enable consistent use, across systems, of the most accurate and timely data about essential business entities” (DAMA, 2017).

    The Data Management Framework from earlier with tier 2 item 'Reference and Master' highlighted.

    Fundamental objective of MDM: Enable the business to see one view of critical data elements across the organization.

    Phases of the MDM Framework. 'Phase 1: Build a Vision for MDM' entails a 'Readiness Assessment', then both 'Identify the Master Data Needs of the Business' and 'Create a Strategic Vision'. 'Phase 2: Create a Plan and Roadmap for the Organization’s MDM Program' entails 'Assess Current MDM Capabilities', then 'Initiative Planning', then 'Strategic Roadmap'.

    What is MDM and why is it needed?

    • Master data management (MDM) “entails control over Master Data values and identifiers that enable consistent use, across systems, of the most accurate and timely data about essential business entities” (DAMA, 2017).
    • The fundamental objective of MDM is to enable the business to see one view of critical data elements across the organization.
    • What is included in the scope of MDM?
      • Party data (employees, customers, etc.)
      • Product/service data
      • Financial data
      • Location data

    Is there traceability and visibility into your data’s lineage? Does your data pipeline facilitate that single view across the organization?

    Who:

    This research is designed for:

    • Chief Data Officer (CDO)
    • Head of Data Management, CIO
    • Data Architect
    • Head of Data Governance, Data Officer

    Info-Tech Insight

    Successful MDM requires a comprehensive approach. To be successfully planned, implemented, and maintained it must include effective capabilities in the critical processes and subpractices of data management.

    Data Modeling Framework

    • The framework consists of the business, enterprise, application, and implementation layers.
    • The Business Layer encodes real-world business concepts via the conceptual model.
    • The Enterprise Layer defines all enterprise data asset details and their relationships.
    • The Application Layer defines the data structures as used by a specific application.
    • The Implementation Layer defines the data models and artifacts for use by software tools.
    Data Modeling Framework with items from the 'Implementation Layer' contributing to items in the 'Application Layer' and 'Enterprise Layer' before turning into a 'Conceptual Model' in the 'Business Layer'.

    Model hierarchy

    • The Conceptual data model describes the organization from a business perspective.
    • The Message model is used to describe internal- and external-facing messages and is equivalent to the canonical model.
    • The Enterprise model depicts the whole organization and is divided into domains.
    • The Analytical model is built for specific business use cases.
    • Application models are application-specific operational models.
    Model hierarchy with items from the 'Implementation Layer' contributing to items in the 'Application Layer' and 'Enterprise Layer' before turning into a 'Conceptual Model' in the 'Business Layer'.

    Info-Tech Insight

    The Conceptual model acts as the root of all the models required and used by an organization.

    Data architecture and modeling processes

    A diagram moving from right to left through 5 phases: 'Business concepts defined and organized', 'Business concepts enriched with attribution', 'Physical view of the data, still vendor agnostic', 'The view being used by developers and business', and 'Manage the progression of your data assets'.

    Info-Tech Insight

    The Conceptual data model adds relationships to your business data glossary terms and is the first step of the modeling journey.

    Data operations

    Objectives of Data Operations Management

    • Implement and follow policies and procedures to manage data at each stage of its lifecycle.
    • Maintain the technology supporting the flow and delivery of data (applications, databases, systems, etc.).
    • Control the delivery of data within the system environment.

    Indicators of Successful Data Operations Management

    • Effective delivery of data assets to end users.
    • Successful maintenance and performance of the technical environment that collects, stores, delivers, and purges organizational data.
    'Data Lifecycle' with steps 'Create', 'Acquire', 'Store', 'Maintain', 'Use', and 'Archive/Destroy'.
    This data management enabler has a heavy focus on the management and performance of data systems and applications.
    It works closely with the organization’s technical architecture to support successful data delivery and lifecycle management (data warehouses, repositories, databases, networks, etc.).

    Step 1.2

    Understand and Align to Business Drivers

    Activities

    1.2.1 Define your value streams

    1.2.2 Identify your business capabilities

    1.2.3 Categorize your organization’s key business capabilities

    1.2.4 Develop a strategy map tied to data management

    This step will guide you through the following activities:

    • Leverage your organization’s existing business capability map or initiate the formulation of a business capability map.
    • Determine which business capabilities are considered high priority by your organization.
    • Map your organization’s strategic objectives to value streams and capabilities to communicate how objectives are realized with the support of data.

    Outcomes of this step

    • A foundation for data management initiative planning that’s aligned with the organization’s business architecture: value streams, business capability map, and strategy map

    Build Business Context and Drivers

    Step 1.1 Step 1.2 Step 1.3 Step 1.4

    Identifying value streams

    Value streams connect business goals to organization’s value realization activities. They enable an organization to create and capture value in the marketplace by engaging in a set of interconnected activities.
    There are several key questions to ask when endeavouring to identify value streams.

    Key Questions

    • Who are your customers?
    • What are the benefits we deliver to them?
    • How do we deliver those benefits?
    • How does the customer receive the benefits?

    1.2.1 Define value streams

    1-3 hours

    Input: Business strategy/goals, Financial statements, Info-Tech’s industry-specific business architecture

    Output: List of organization-specific value streams, Detailed value stream definition(s)

    Materials: Whiteboard/kanban board, Info-Tech’s Reference Architecture Template – contact your Account Representative for details, Other industry standard reference architecture models: BIZBOK, APQC, etc., Info-Tech’s Archimate models

    Participants: Enterprise/Business Architect, Business Analysts, Business Unit Leads, CIO, Departmental Executive & Senior managers

    Unify the organization’s perspective on how it creates value.

    1. Write a short description of the value stream that includes a statement about the value provided and a clear start and end for the value stream. Validate the accuracy of the descriptions with your key stakeholders.
    2. Consider:
      • How does the organization deliver those benefits?
      • How does the customer receive the benefits?
      • What is the scope of your value stream? What will trigger the stream to start and what will the final value be?
    3. Avoid:
      • Don’t start with a blank page. Use Info-Tech’s business architecture models for sample value streams.

    Contact your Account Representative for access to Info-Tech’s Reference Architecture Template

    Define or validate the organization’s value streams

    Value streams connect business goals to the organization’s value realization activities. These value realization activities, in turn, depend on data.

    If the organization does not have a business architecture function to conduct and guide Activity 1.2.1, you can leverage the following approach:

    • Meet with key stakeholders regarding this topic, then discuss and document your findings.
    • When trying to identify the right stakeholders, consider: Who are the decision makers and key influencers? Who will impact this piece of business architecture–related work? Who has the relevant skills, competencies, experience, and knowledge about the organization?
    • Engage with these stakeholders to define and validate how the organization creates value. Consider:
      • Who are your main stakeholders? This will depend on the industry in which you operate. For example, they could be customers, residents, citizens, constituents, students, patients.
      • What are your stakeholders looking to accomplish?
      • How does your organization’s products and/or services help them accomplish that?
      • What are the benefits your organization delivers to them and how does your organization deliver those benefits?
      • How do your stakeholders receive those benefits?

    Align data management to the organization’s value realization activities.

    Value streams enable the organization to create or capture value in the market in which it operates by engaging in a set of interconnected activities.

    Info-Tech Insight

    Your organization’s value streams and the associated business capabilities require effectively managed and governed data. Without this, you could face elevated operational costs, missed opportunities, eroded stakeholder satisfaction, negative impact to reputation and brand, and/or increased exposure to business risk.

    Example of value streams – Retail Banking

    Value streams connect business goals to the organization’s value realization activities.

    Example value stream descriptions for: Retail Banking

    Value streams enable the organization to create or capture value in the market in which it operates by engaging in a set of interconnected activities. Example Value Stream for Retail Banking with five value chains. 'Attract Customers: Retail banks design new products to fill gaps in their product portfolios by analyzing the market for changing customer needs and new competitor offerings or pricing; Pricing a product correctly through analysis and rate setting is a delicate balance and fundamental to a bank’s success.' 'Supply Loans and Mortgages and Credit Cards: Selecting lending criteria helps banks decide on the segment of customer they should take on and the degree of risk they are willing to accept.' 'Provide Core Banking Services: Servicing includes the day-to-day interactions with customers for onboarding, payments, adjustments, and offboarding through multiple banking channels; Customer retention and growing share of wallet are crucial capabilities in servicing that directly impact the growth and profitability of retail banks.' 'Offer Card Services: Card servicing involves quick turnarounds on card delivery and acceptance at a large number of merchants; Accurate billing and customizable spending alerts are crucial in ensuring that the customer understands their spending habits.' 'Grow Investments and Manage Wealth: Customer retention can be increased through effective wealth management and additional services that will increase the number of products owned by a customer.'

    For this value stream, download Info-Tech’s Industry Reference Architecture for Retail Banking.

    Example of value streams – Higher Education

    Value streams connect business goals to the organization’s value realization activities.

    Example value stream descriptions for: Higher Education

    Value streams enable the organization to create or capture value in the market in which it operates by engaging in a set of interconnected activities. Example Value Stream for Higher Education with five value chains. 'Shape Institutional Research: Institutional research provides direct benefits to both partners and faculty, ensuring efficient use of resources and compliance with ethical and methodological standards; This value stream involves all components of the research lifecycle, from planning and resourcing to delivery and commercialization.' 'Facilitate Curriculum Design: Curriculum design is the process by which learning content is designed and developed to achieve desired student outcomes; Curriculum management capabilities include curriculum planning, design and commercialization, curriculum assessment, and instruction management.' 'Design Student Support Services: Support services design and development provides a range of resources to assist students with academic success, such as accessibility, health and counseling, social services, housing, and academic skills development.' 'Manage Academic Administration: Academic administration involves the broad capabilities required to attract and enroll students in institutional programs; This value stream involves all components related to recruitment, enrollment, admissions, and retention management.' 'Deliver Student Services: Delivery of student services comes after curricular management, support services design, and academic administration. It comprises delivery of programs and services to enable student success; Program and service delivery capabilities include curriculum delivery, convocation management, and student and alumni support services.'

    For this value stream, download Info-Tech’s Industry Reference Architecture for Higher Education.

    Example of value streams – Local Government

    Value streams connect business goals to the organization’s value realization activities.

    Example value stream descriptions for: Local Government

    Value streams enable the organization to create or capture value in the market in which it operates by engaging in a set of interconnected activities. Example Value Stream for Local Government with five value chains. 'Sustain Land, Property, and the Environment: Local governments act as the stewards of the regional land and environment that are within their boundaries; Regional government bodies are responsible for ensuring that the natural environment is protected and sustained for future citizens in the form of parks and public land.' 'Facilitate Civic Engagement: Local governments engage with constituents to maintain a high quality of life through art, culture, and education.' 'Protect Local Health and Safety: Health concerns are managed by a local government through specialized campaigns and clinics; Emergency services are provided by the local authority to protect and react to health and safety concerns including police and firefighting services.' 'Grow the Economy: Economic growth is a cornerstone of a strong local government. Growth comes from flourishing industries, entrepreneurial success, high levels of employment, and income from tourism.' 'Provide Regional Infrastructure: Local governments ensure that infrastructure is built, maintained, and effective in meeting the needs of constituents. (Includes: electricity, water, sustainable energy sources, waste collection, transit, and local transportation.'

    For this value stream, download Info-Tech’s Industry Reference Architecture for Local Government.

    Example of value streams – Manufacturing

    Value streams connect business goals to the organization’s value realization activities.

    Example value stream descriptions for: Manufacturing

    Value streams enable the organization to create or capture value in the market in which it operates by engaging in a set of interconnected activities. Example Value Stream for Manufacturing with three value chains. 'Design Product: Manufacturers proactively analyze their respective markets for any new opportunities or threats; They design new products to serve changing customer needs or to rival any new offerings by competitors; A manufacturer’s success depends on its ability to develop a product that the market wants at the right price and quality level.' 'Produce Product: Optimizing production activities is an important capability for manufacturers. Raw materials and working inventories need to be managed effectively to minimize wastage and maximize the utilization of the production lines; Processes need to be refined continuously over time to remain competitive and the quality of the materials and final products needs to be strictly managed.' 'Sell Product: Once produced, manufacturers need to sell the products. This is done through distributors, retailers, and, in some cases, directly to the end consumer; After the sale, manufacturers typically have to deliver the product, provide customer care, and manage complaints; Manufacturers also randomly test their end products to ensure they meet quality requirements.'

    For this value stream, download Info-Tech’s Industry Reference Architecture for Manufacturing.

    Define the organization’s business capabilities in a business capability map

    A business capability defines what a business does to enable value creation. Business capabilities represent stable business functions and typically will have a defined business outcome.

    Business capabilities can be thought of as business terms defined using descriptive nouns such as “Marketing” or “Research and Development.”

    If your organization doesn’t already have a business capability map, you can leverage the following approach to build one. This initiative requires a good understanding of the business. By working with the right stakeholders, you can develop a business capability map that speaks a common language and accurately depicts your business.

    Working with the stakeholders as described in the slide entitled “Define or validate the organization’s value streams”:

    • Analyze the value streams to identify and describe the organization’s capabilities that support them.
    • Consider the objective of your value stream. (This can highlight which capabilities support which value stream.)
    • As you initiate your engagement with your stakeholders, don’t start a blank page. Leverage the examples on the next slides as a starting point for your business capability map.
    • When using these examples, consider: What are the activities that make up your particular business? Keep the ones that apply to your organization, remove the ones that don’t, and add any needed.

    Align data management to the organization’s value realization activities.

    Info-Tech Insight

    A business capability map can be thought of as a visual representation of your organization’s business capabilities and hence represents a view of what your data management program must support.

    For more information, refer to Info-Tech’s Document Your Business Architecture.

    1.2.2 Identify your business capabilities

    Input: List of confirmed value streams and their related business capabilities

    Output: Business capability map with value streams for your organization

    Materials: Your existing business capability map, Business Alignment worksheet provided in the Data Management Assessment and Planning Tool, Info-Tech’s Document Your Business Architecture blueprint

    Participants: Key business stakeholders, Data stewards, Data custodians, Data leads and administrators

    Confirm your organization's existing business capability map or initiate the formulation of a business capability map:

    • If you have an existing business capability map, meet with the relevant business owners/stakeholders to confirm that the content is accurate and up to date. Confirm the value streams (how your organization creates and captures value) and their business capabilities reflect the organization’s current business environment.
    • If you do not have an existing business capability map, complete this activity to initiate the formulation of a map (value streams and related business capabilities):
      1. Define the organization’s value streams. Meet with senior leadership and other key business stakeholders to define how your organization creates and captures value.
      2. Define the relevant business capabilities. Meet with senior leadership and other key business stakeholders to define the business capabilities.

    Note: A business capability defines what a business does to enable value creation. Business capabilities are business terms defined using nouns such as “Marketing” or “Research and Development.” They represent stable business functions, are unique and independent of one another, and typically will have a defined business outcome.

    Example business capability map – Retail Banking

    A business capability map can be thought of as a visual representation of your organization’s business capabilities and hence represents a view of what your data governance program must support.

    Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

    Info-Tech Tip: Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realization capabilities under discussion. This will help to build awareness and visibility of the data management program.

    Example business capability map for: Retail Banking

    Example business capability map for Retail Banking with value stream items as column headers, and rows 'Enabling', 'Shared', and 'Defining'.

    For this business capability map, download Info-Tech’s Industry Reference Architecture for Retail Banking.

    Example business capability map – Higher Education

    A business capability map can be thought of as a visual representation of your organization’s business capabilities and hence represents a view of what your data governance program must support.

    Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

    Info-Tech Tip: Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realization capabilities under discussion. This will help to build awareness and visibility of the data management program.

    Example business capability map for: Higher Education

    Example business capability map for Higher Education with value stream items as column headers, and rows 'Enabling', 'Shared', and 'Defining'.

    For this business capability map, download Info-Tech’s Industry Reference Architecture for Higher Education.

    Example business capability map – Local Government

    A business capability map can be thought of as a visual representation of your organization’s business capabilities and hence represents a view of what your data governance program must support.

    Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

    Info-Tech Tip: Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realization capabilities under discussion. This will help to build awareness and visibility of the data governance program.

    Example business capability map for: Local Government

    Example business capability map for Local Government with value stream items as column headers, and rows 'Enabling', 'Shared', and 'Defining'.

    For this business capability map, download Info-Tech’s Industry Reference Architecture for Local Government.

    Example business capability map – Manufacturing

    A business capability map can be thought of as a visual representation of your organization’s business capabilities and hence represents a view of what your data governance program must support.

    Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

    Info-Tech Tip: Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realization capabilities under discussion. This will help to build awareness and visibility of the data governance program.

    Example business capability map for: Manufacturing

    Example business capability map for Manufacturing with value stream items as column headers, and rows 'Enabling', 'Shared', and 'Defining'.

    For this business capability map, download Info-Tech’s Industry Reference Architecture for Manufacturing.

    Example business capability map – Retail

    A business capability map can be thought of as a visual representation of your organization’s business capabilities and hence represents a view of what your data governance program must support.

    Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

    Info-Tech Tip: Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realization capabilities under discussion. This will help to build awareness and visibility of the data governance program.

    Example business capability map for: Retail

    Example business capability map for Retail with value stream items as column headers, and rows 'Enabling', 'Shared', and 'Defining'.

    For this business capability map, download Info-Tech’s Industry Reference Architecture for Retail.

    1.2.3 Categorize your organization’s key capabilities

    Input: Strategic insight from senior business stakeholders on the business capabilities that drive value for the organization

    Output: Business capabilities categorized and prioritized (e.g. cost advantage creators, competitive advantage differentiators, high value/high risk) See next slide for an example

    Materials: Your existing business capability map or the business capability map derived in Activity 1.2.2

    Participants: Key business stakeholders, Data stewards, Data custodians, Data governance working group

    Determine which capabilities are considered high priority in your organization.

    1. Categorize or heatmap the organization’s key capabilities. Consult with senior and other key business stakeholders to categorize and prioritize the business’ capabilities. This will aid in ensuring your data governance future-state planning is aligned with the mandate of the business. One approach to prioritizing capabilities with business stakeholders is to examine them through the lens of cost advantage creators, competitive advantage differentiators, and/or by high value/high risk.
    2. Identify cost advantage creators. Focus on capabilities that drive a cost advantage for your organization. Highlight these capabilities and prioritize programs that support them.
    3. Identify competitive advantage differentiators. Focus on capabilities that give your organization an edge over rivals or other players in your industry.

    This categorization/prioritization exercise helps highlight prime areas of opportunity for building use cases, determining prioritization, and the overall optimization of data and data governance.

    For more information, refer to Info-Tech’s Document Your Business Architecture.

    Example of business capabilities categorization or heatmapping – Retail

    This exercise is useful in ensuring the data governance program is focused and aligned to support the priorities and direction of the business.

    • Depending on the mandate from the business, priority may be on developing cost advantage. Hence the capabilities that deliver efficiency gains are the ones considered to be cost advantage creators.
    • The business’ priority may be on maintaining or gaining a competitive advantage over its industry counterparts. Differentiation might be achieved in delivering unique or enhanced products, services, and/or experiences, and the focus will tend to be on the capabilities that are more end-stakeholder-facing (e.g. customer-, student-, patient,- and/or constituent-facing). These are the organization’s competitive advantage creators.

    Example: Retail

    Example business capability map for Retail with capabilities categorized into Cost Advantage Creators and Competitive Advantage creators via a legend. Value stream items as column headers, and rows 'Enabling', 'Shared', and 'Defining'.

    For this business capability map, download Info-Tech’s Industry Reference Architecture for Retail.

    1.2.4 Develop a strategy map tied to data management

    Input: Strategic objectives as outlined by the organization’s business strategy and confirmed by senior leaders

    Output: A strategy map that maps your organizational strategic objectives to value streams, business capabilities, and ultimately data programs

    Materials: Your existing business capability map or the one created in Activity 1.2.2, Business strategy (see next slide for an example)

    Participants: Key business stakeholders, Data stewards, Data custodians, Data governance working group

    Identify the strategic objectives for the business. Knowing the key strategic objectives will drive business–data governance alignment. It’s important to make sure the right strategic objectives of the organization have been identified and are well understood.

    1. Meet with senior business leaders and other relevant stakeholders to help identify and document the key strategic objectives for the business.
    2. Leverage their knowledge of the organization’s business strategy and strategic priorities to visually represent how these map to value streams, business capabilities, and ultimately data and data governance needs and initiatives. Tip: Your map is one way to visually communicate and link the business strategy to other levels of the organization.
    3. Confirm the strategy mapping with other relevant stakeholders.

    Example of a strategy map tied to data management

    • Strategic objectives are the outcomes the organization is looking to achieve.
    • Value streams enable an organization to create and capture value in the market through interconnected activities that support strategic objectives.
    • Business capabilities define what a business does to enable value creation in value streams.
    • Data capabilities and initiatives are descriptions of action items on the data and data governance roadmap that will enable one or multiple business capabilities in its desired target state.

    Info-Tech Tip: Start with the strategic objectives, then map the value streams that will ultimately drive them. Next, link the key capabilities that enable each value stream. Then map the data and data governance initiatives that support those capabilities. This process will help you prioritize the data initiatives that deliver the most value to the organization.

    Example: Retail

    Example of a strategy map tied to data management with diagram column headers 'Strategic Objectives' (are realized through...) 'Value Streams' (are enabled by...) 'Key Capabilities' (are driven by...) 'Data Capabilities and Initiatives'. Row headers are objectives and fields are composed of three examples of each column header.

    For this strategy map, download Info-Tech’s Industry Reference Architecture for Retail.

    Step 1.3

    Build High-Value Use Cases for Data Management

    Activities

    1.3.1 Build high-value use cases

    This step will guide you through the following activities:

    • Understand the main disciplines and makeup of a best-practice data management program.
    • Determine which data management capabilities are considered high priority by your organization.

    Outcomes of this step

    • A foundation for data management initiative planning that’s aligned with the organization’s business architecture: value streams, business capability map, and strategy map

    Build Business Context and Drivers

    Step 1.1 Step 1.2 Step 1.3 Step 1.4

    1.3.1 Build high-value use cases

    Input: Value streams and business capabilities as defined by business leaders, Business stakeholders’ subject area expertise, Data custodian systems, integration, and data knowledge

    Output: Use cases that articulate data-related challenges, needs, or opportunities that are tied to defined business capabilities and hence, if addressed, will deliver measurable value to the organization

    Materials: Your business capability map from Activity 1.2.2, Info-Tech’s Data Use Case Framework Template, Whiteboard or flip charts (or shared screen if working remotely), Markers/pens

    Participants: Key business stakeholders, Data stewards and business SMEs, Data custodians, Data leads and administrators

    This business needs gathering activity will highlight and create relevant use cases around data-related problems or opportunities that are clear and contained and, if addressed, will deliver value to the organization.

    1. Bring together key business stakeholders (data owner, stewards, SMEs) from a particular line of business as well the relevant data custodian(s) to build cases for their units. Leverage the business capability map you created for facilitating this act.
    2. Leverage Info-Tech’s Data Use Case Framework Template as seen on the next slide.
    3. Have the stakeholders move through each breakout session outlined in the use case worksheet. Use flip charts or a whiteboard to brainstorm and document their thoughts.
    4. Debrief and document results in the Data Use Case Framework Template.
    5. Repeat this exercise with as many lines of the business as possible, leveraging your business capability map to guide your progress and align with business value.

    Tip: Don’t conclude these use case discussions without substantiating what measures of success will be used to demonstrate the business value of the effort to produce the desired future state, as relevant to each particular use case.

    Download Info-Tech’s Data Use Case Framework Template

    Data use cases

    Sample Data

    The following is the list of use cases as articulated by key stakeholders at [Organization Name].

    The stakeholders see these as areas that are relevant and highly valuable for delivering strategic value to [Organization Name].

    Use Case 1: Customer/Student/Patient/Resident 360 View

    Use Case 2: Project/Department Financial Performance

    Use Case 3: Vendor Lifecycle Management

    Use Case 4: Project Risk Management

    Prioritization of use cases

    Example table for use case prioritization. Column headers are 'Use Case', 'Order of Priority', and 'Comments'. Fields are empty.

    Use case 1

    Sample Data

    Problem statement:

    • We are not realizing our full growth potential because we do not have a unified 360 view of our customers/clients/[name of external stakeholder].
    • This impacts: our cross-selling; upselling; talent acquisition and retention; quality of delivery; ability to identify and deliver the right products, markets, and services...

    If we could solve this:

    • We would be able to better prioritize and position ourselves to meet evolving customer needs.
    • We would be able to optimize the use of our limited resources.

    Use case 1: challenges, risks, and opportunities

    Sample Data

    1. What is the number one risk you need to alleviate?
      • Loss of potential revenue, whether from existing or net new customers.
        • How?
          • By not maximizing opportunities with customers or even by losing customers; by not understanding or addressing their greatest needs
          • By not being able to win potential new customers because we don’t understand their needs
    2. What is the number one opportunity you wish to see happen?
      • The ability to better understand and anticipate the needs of both existing and potential customers.
    3. What is the number one pain point you have when working with data?
      • I can’t do my job with confidence because it’s not based on comprehensive, sound, reliable data. My group spends significant time reconciling data sets with little time left for data use and analysis.
    4. What are your challenges in performing the activity today?
      • I cannot pull together customer data in a timely manner due to having a high level of dependence on specific individuals with institutional knowledge rather than having easy access to information.
      • It takes too much time and effort to pull together what we know about a customer.
      • The necessary data is not consolidated or readily/systematically available for consumption.
      • These challenges are heightened when dealing with customers across markets.

    Use case 1 (cont'd)

    Sample Data

    1. What does “amazing” look like if we solve this perfectly?
      • Employees have immediate, self-service access to necessary information, leading to better and more timely decisions. This results in stronger business and financial growth.
    2. What other business unit activities/processes will be impacted/improved if we solve this?
      • Marketing/bid and proposal, staffing, procurement, and contracting strategy
    3. What compliance/regulatory/policy concerns do we need to consider in any solution?
      • PII, GDPR, HIPAA, CCPA, etc.
    4. What measures of success/change should we use to prove the value of the effort (KPIs/ROI)?
      • Win rate, number of services per customer, gross profit, customer retention, customer satisfaction scores, brand awareness, and net promoter score
    5. What are the steps in the process/activity today?
      • Manual aggregation (i.e. pull data from systems into Excel), reliance on unwritten knowledge, seeking IT support, canned reports

    Use case 1 (cont'd)

    Sample Data

    1. What are the applications/systems used at each step?
      • Salesforce CRM, Excel, personal MS Access databases, SharePoint
    2. What data elements (domains) are involved, created, used, or transformed at each step?
      • Bid and proposal information, customer satisfaction, forecast data, list of products, corporate entity hierarchy, vendor information, key staffing, recent and relevant news, and competitor intelligence

    Use case worksheet

    Objective: This business needs gathering activity will help you highlight and create relevant use cases around data-related problems or opportunities. They should be clear and contained and, if addressed, will deliver value to the organization.

    1.

    What business capability (or capabilities) in your business area is this use case tied to?

    Examples: Demand Planning, Assortment Planning, Allocation & Replenishment, Fulfillment Planning, Customer Management
    2.

    What are your data-related challenges in performing this today?

    Use case worksheet (cont’d.)

    Objective: This business needs gathering activity will help you highlight and create relevant use cases around data-related problems or opportunities. They should be clear and contained and, if addressed, will deliver value to the organization.

    3.

    What are the steps in the process/activity today?

    4.

    What are the applications/systems used at each step today?

    5.

    What data domains are involved, created, used, or transformed at each step today?

    Use case worksheet (cont’d.)

    Objective: This business needs gathering activity will help you highlight and create relevant use cases around data-related problems or opportunities. They should be clear and contained and, if addressed, will deliver value to the organization.

    6.

    What does an ideal or improved state look like?

    7.

    What other business units, business capabilities, activities, or processes will be impacted and/or improved if this were to be solved?

    8.

    Who are the stakeholders impacted by these changes? Who needs to be consulted?

    9.

    What are the risks to the organization (business capability, revenue, reputation, customer loyalty, etc.) if this is not addressed?

    Use case worksheet (cont’d.)

    Objective: This business needs gathering activity will help you highlight and create relevant use cases around data-related problems or opportunities. They should be clear and contained and, if addressed, will deliver value to the organization.

    10.

    What compliance, regulatory, or policy concerns do we need to consider in any solution?

    11.

    What measures of success or change should we use to prove the value of the effort (KPIs/ROI)? What is the measurable business value of doing this?

    Use case worksheet (cont’d.)

    Objective: This business needs gathering activity will help you highlight and create relevant use cases around data-related problems or opportunities. They should be clear and contained and, if addressed, will deliver value to the organization.

    10.

    Conclusion: What are the data capabilities that need to be optimized, addressed, or improved to support or help realize the business capability (or capabilities) highlighted in this use case?

    (Tip: This will inform your future-state data capabilities optimization planning and roadmapping activities.)

    Data Management Workshop
    Use Case 1: Covid-19 Emergency Management

    [SAMPLE]

    Problem Statement

    Inability to provide insights to DPH due to inconsistent data, inaccurate reporting, missing governance, and unknown data sources resulting in decisions that impact citizens being made without accurate information.

    Challenges
    • Data is not suitable for analytics. It takes lot of effort to clean data.
    • Data intervals are not correct and other data quality issues.
    • The roles are not clearly defined.
    • Lack of communication between key stakeholders.
    • Inconsistent data/reporting/governance in the agencies. This has resulted in number of issues for Covid-19 emergency management. Not able to report accurately on number of cases, deaths, etc.
    • Data collection systems changed overtime (forms, etc.).
    • GIS has done all the reporting. However, why GIS is doing all the reporting is not clear. GIS provides critical information for location. Reason: GIS was ready with reporting solution ArcGIS.
    • Problem with data collection, consolidation, and providing hierarchical view.
    • Change in requirements, metrics – managing crisis by email and resulting in creating one dashboard after another. Not sure whether these dashboards being used.
    • There is a lot of manual intervention and repeated work.
    What Does Amazing Look Like?
    • One set of dashboards (or single dashboard) – too much time spend on measure development
    • Accurate and timely data
    • Automated data
    • Access to granular data (for researchers and other stakeholders)
    • Clear ownership of data and analytics
    • It would have been nice to have governance already prior to this crisis
    • Proper metrics to measure usage and value
    • Give more capabilities such as predictive analytics, etc.
    Related Processes/Impact
    • DPH
    • Schools
    • Business
    • Citizens
    • Resources & Funding
    • Data Integration & GIS
    • Data Management
    • Automated Data Quality
    Compliance
    • HIPAA, FERPA, CJIS, IRS
    • FEMA
    • State compliance requirement – data classification
    • CDC
    • Federal data-sharing agreements/restrictions
    Benefits/KPIs
    • Reduction in cases
    • Timely response to outbreak
    • Better use of resources
    • Economic impact
    • Educational benefits
    • Trust and satisfaction

    Data Management Workshop
    Use Case 1: Covid-19 Emergency Management

    [SAMPLE]

    Problem Statement

    Inability to provide insights to DPH due to inconsistent data, inaccurate reporting, missing governance, and unknown data sources resulting in decisions that impact citizens being made without accurate information.

    Current Steps in Process Activity (Systems)
    1. Collect data through Survey123 using ArcGIS (hospitals are managed to report by 11 am) – owned KYEM
    2. KYEM stores this information/data
    3. Deduplicate data (emergency preparedness group)
    4. Generate dashboard using ArcGIS
    5. Map to monitor status of the update
    6. Error correction using web portal (QAQC)
    7. Download Excel/CVS after all 97 hospital reports
    8. Sent to federal platform (White House, etc.)
    9. Generate reports for epidemiologist (done manually for public reporting)
    Data Flow diagram

    Data flow diagram.

    SystemsData Management Dimensions
    1. Data Governance
    2. Data Quality
    3. Data Integrity
    4. Data Integration
    1. Data Architecture
    2. Metadata
    3. Data Warehouse, Reporting & Analytics
    4. Data Security

    Data Management Workshop
    Use Case 1: Covid-19 Emergency Management

    [SAMPLE]

    Problem Statement

    Inability to provide insights to DPH due to inconsistent data, inaccurate reporting, missing governance, and unknown data sources resulting in decisions that impact citizens being made without accurate information.

    List Future Process Steps

    Prior to COVID-19 Emergency Response:

    • ArcGIS data integrated available in data warehouse/data lake.
    • KYEM data integrated and available in data warehouse/data lake.
    • CHFS data integrated and available in data warehouse/data lake.
    • Reporting standards and tools framework established.

    After COVID-19 Emergency Response:

    • Collect data through Survey123 using ArcGIS (hospitals are managed to report by 11 am) – owned KYEM.
    • Error correction using web portal (QAQC).
    • Generate reports/dashboard/files as per reporting/analytical requirements:
      • Federal reporting
      • COVID dashboards
      • Epidemiologist reports
      • Lab reporting
    Future Process and Data Flow

    Data flow diagram with future processes.

    Step 1.4

    Create a Vision and Guiding Principles for Data Management

    Activities

    1.4.1 Craft a vision

    1.4.2 Create guiding principles

    This step will guide you through the following activities:

    • Leverage your organization’s existing business capability map or initiate the formulation of a business capability map, guided by info-Tech’s approach.
    • Determine which business capabilities are considered high priority by your organization.
    • Map your organization’s strategic objectives to value streams and capabilities to communicate how objectives are realized with the support of data.

    Outcomes of this step

    • A foundation for data management initiative planning that’s aligned with the organization’s business architecture: value streams, business capability map, and strategy map

    Build Business Context and Drivers

    Step 1.1 Step 1.2 Step 1.3 Step 1.4

    1.4.1 Craft a vision

    Input: Organizational vision and mission statements, Stakeholder survey results and elicitation findings, Use cases, Business and data capability map

    Output: Vision and mission statements

    Materials: Markers and pens, Whiteboard, Online whiteboard, Vision samples and templates

    Participants: Key business stakeholders, Data managers, Data owners, Business leads and SMEs, Project team, Project sponsor

    Complete the vision statement to set the direction, the “why,” for the changes we’re making. The vision is a reference point that should galvanize everyone in the organization and set guardrails for technical and process decisions to follow.

    1. Bring together key business stakeholders (content owners, SMEs, and relevant IT custodians) to craft a data management vision statement.
    2. Start by brainstorming keywords, such as customer-focused, empower the business, service excellence, findable and manageable, protected, accessible, paperless.
    3. Highlight the keywords that resonate most with the group. Refer to example vision statements for ideas.

    Create a common data management vision that is consistently communicated to the organization

    A data management program should be an enterprise-wide initiative.

    • To create a strong vision for data management, there must be participation from the business and IT. A common vision will articulate the state the organization wishes to achieve and how it will reach that state. Visioning helps to develop long-term goals and direction.
    • Once the vision is established, it must be effectively communicated to everyone, especially those who are involved in creating, managing, disposing, or archiving data.
    • The data management program should be periodically refined. This will ensure the organization continues to incorporate best methods and practices as the organization grows and data needs evolve.
    Stock image of a megaphone with multiple icons pouring from its opening.

    Info-Tech Tips

    • Use information from the stakeholder interviews to derive business goals and objectives.
    • Work to integrate different opinions and perspectives into the overall vision for data management.
    • Brainstorm guiding principles for content and understand the overall value to the organization.

    Create compelling vision and mission statements for the organization’s future data management practice

    A vision represents the way your organization intends to be in the future.

    A clear vision statement helps align the entire organization to the same end goal.

    Your vision should be brief, concise, and inspirational; it is attempting to say a lot in a few words, so be very thoughtful and careful with the words you choose. Consider your strengths across departments – business and IT, the consumers of your services, and your current/future commitments to service quality.

    Remember that a vision statement is internally facing for other members of your company throughout the process.

    A mission expresses why you exist.

    While your vision is a declaration of where your organization aspires to be in the future, your mission statement should communicate the fundamental purpose of the data management practice.

    It identifies the function of the practice, what it produces, and its high-level goals that are linked to delivering timely, high-quality, relevant, and valuable data to business processes and end users. Consider if the practice is responsible for providing data for analytical and/or operational use cases.

    A mission statement should be a concise and clear statement of purpose for both internal and external stakeholders.

    “The Vision is the What, Where or Who you want the company to become. The Mission is the WHY the company exists, it is your purpose, passion or cause.” (Doug Meyer-Cuno, Forbes, 2021)

    Data Management Vision and Mission Statements: Draft

    Vision and mission statements crafted by the workshop participants. These statements are to be reviewed, refined into a single version, approved by members of the senior leadership team, and then communicated to the wider organization.

    Corporate

    Group 1

    Group 2

    Vision:
    Create and maintain an institution of world-class excellence.
    Vision: Vision:
    Mission:
    Foster an economic and financial environment conducive to sustainable economic growth and development.
    Mission: Mission:

    Information management framework

    The information management framework is a way to organize all the ECM program’s guidelines and artifacts

    Information management framework with 'Information Management Vision' above six principles. Below them are 'Information Management Policies' and 'Information Management Standards and Procedures.'

    The vision is a statement about the organization’s goals and provides a basis to guide decisions and rally employees toward a shared goal.

    The principles or themes communicate the organization’s priorities for its information management program.

    Policies are a set of official guidelines that determine a course of action. For example: Company is committed to safety for its employees.

    Procedures are a set of actions for doing something. For example: Company employees will wear protective gear while on the production floor.

    Craft your vision

    Use the insights you gathered from users and stakeholders to develop a vision statement
    • The beginning of a data management practice is a clear set of goals and key performance indicators (KPIs).
      A good set of goals takes time and input from senior leadership and stakeholders.
    • The data management program lead is selling a compelling vision of what is possible.
    • The vision also helps set the scope and expectations about what the data management program lead is and is not doing.
    • Be realistic about what you can do and how long it will take to see a difference.
    Table comparing the talk (mission statements, vision statements, and values) with the walk (strategies/goals, objectives, and tactical plans). Example vision statements:
    • The organization is dedicated to creating an enabling structure that helps the organization get the right information to the right people at the right time.
    • The organization is dedicated to creating a program that recognizes data as an asset, establishing a data-centric culture, and ensuring data quality and accessibility to achieve service excellence.
    The vision should be short, memorable, inspirational and draw a clear picture of what that future-state data management experience looks like.

    Is it modern and high end, with digital self-service?

    Is it a trusted and transparent steward of customer assets?

    1.4.2 Create guiding principles

    Input: Sample data management guiding principles, Stakeholder survey results and elicitation findings, Use cases, Business and data capability map

    Output: Data management guiding principles

    Materials: Markers and pens, Whiteboard, Online whiteboard, Guiding principles samples and templates

    Participants: Key business stakeholders, Data managers, Data owners, Business leads and SMEs, Project team, Project sponsor

    Draft a set of guiding principles that express your program’s values as a framework for decisions and actions and keep the data strategy alive.

    1. Bring together key business stakeholders (data owners, SMEs, and relevant IT custodians) to craft a set of data management guiding principles.
    2. Refer to industry sample guiding principles for data management.
    3. Discuss what’s important to stakeholders and owners, e.g. security, transparency, integrity. Good guiding principles address real challenges.
    4. A helpful tip: Craft principles as “We will…” statements for the problems you’ve identified.

    Twelve data management universal principles

    [SAMPLE]
    Principle Definitions
    Data Is Accessible Data is accessible across the organization based on individuals’ roles and privileges.
    Treat Data as an Asset Treat data as a most valuable foundation to make right decisions at the right time. Manage the data lifecycle across organization.
    Manage Data Define strategic enterprise data management that defines, integrates, and effectively retrieves data to generate accurate, consistent insights.
    Define Ownership & Stewardship Organizations should clearly appoint data owners and data stewards and ensure all team members understand their role in the company’s data management system.
    Use Metadata Use metadata to ensure data is properly managed by tacking how data has been collected, verified, reported, and analyzed.
    Single Source of Truth Ensure the master data maintenance across the organization.
    Ensure Data Quality Ensure data integrity though out the lifecycle of data by establishing a data quality management program.
    Data Is Secured Classify and maintain the sensitivity of the data.
    Maximize Data Use Extend the organization’s ability to make the most of its data.
    Empower the Users Foster data fluency and technical proficiency through training to maximize optimal business decision making.
    Share the Knowledge Share and publish the most valuable insights appropriately.
    Consistent Data Definitions Establish a business data glossary that defines consistent business definitions and usage of the data.

    Create a Data Management Roadmap

    Phase 2

    Assess Data Management and Build Your Roadmap

    Phase 1

    1.1 Review the Data Management Framework

    1.2 Understand and Align to Business Drivers

    1.3 Build High-Value Use Cases

    1.4 Create a Vision

    Phase 2

    2.1 Assess Data Management

    2.2 Build Your Data Management Roadmap

    2.3 Organize Business Data Domains

    This phase will walk you through the following activities:

    • Understand your current data management capabilities.
    • Define target-state capabilities required to achieve business goals and enable the data strategy.
    • Identify priority initiatives and planning timelines for data management improvements.

    This phase involves the following participants:

    • Data Management Lead/Information Management Lead, CDO, Data Lead
    • Senior Business Leaders
    • Business SMEs
    • Data owners, records managers, regulatory subject matter experts (e.g. legal counsel, security)

    Step 2.1

    Assess Your Data Management Capabilities

    Activities

    2.1.1 Define current state of data management capabilities

    2.1.2 Set target state and identify gaps

    This step will guide you through the following activities:

    • Assess the current state of your data management capabilities.
    • Define target-state capabilities required to achieve business goals and enable the data strategy.
    • Identify gaps and prioritize focus areas for improvement.

    Outcomes of this step

    • A prioritized set of improvement areas aligned with business value stream and drivers

    Assess Data Management and Build Your Roadmap

    Step 2.1 Step 2.2 Step 2.3

    Define current state

    The Data Management Assessment and Planning Tool will help you analyze your organization’s data requirements, identify data management strategies, and systematically develop a plan for your target data management practice.
    • Based on Info-Tech’s Data Management Framework, evaluate the current-state performance levels for your organization’s data management practice.
    • Use the CMMI maturity index to assign values 1 to 5 for each capability and enabler.

    A visualization of stairs numbered up from the bottom. Main headlines of each step are 'Initial and Reactive', 'Managed while developing DG capabilities', 'Defined DG capabilities', 'Quantitatively Managed by DG capabilities', and 'Optimized'.

    Sample of the 'Data Management Current State Assessment' form the Data Management Assessment and Planning Tool.

    2.1.1 Define current state

    Input: Stakeholder survey results and elicitation findings, Use cases, Business and data management capability map

    Output: Current-state data management capabilities

    Materials: Data Management Assessment and Planning Tool

    Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians

    Assign a maturity level value from 1 to 5 for each question in the assessment tool, organized into capabilities, e.g. Data Governance, Data Quality, Risk.

    1. Bring together key business stakeholders (data owners, SMEs, and relevant IT custodians) to assign current-state maturity levels in each question of the worksheet.
    2. Remember that there is more distance between levels 4 and 5 than there is between 1 and 2 – the distance between levels is not even throughout.
    3. To help assign values, think of the higher levels as representing cross-enterprise standardization, monitored for continuous improvement, formalized and standardized, while the lower levels mean applied within individual units, not formalized or tracked for performance.
    4. In tab 4, “Current State Assessment,” populate a current-state value for each item in the Data Management Capabilities worksheet.
    5. Once you’ve entered values in tab 4, a visual and summary report of the results will be generated on tab 5, “Current State Results.”

    2.1.2 Set target state and identify gaps

    Input: Stakeholder survey results and elicitation findings, Use cases, Business and data management capability map to identify priorities

    Output: Target-state data management capabilities, Gaps identification and analysis

    Materials: Data Management Assessment and Planning Tool

    Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians

    Assign a maturity level value from 1 to 5 for each question in the assessment tool, organized into capabilities, e.g., Data Governance, Data Quality, Risk.

    1. Bring together key business stakeholders (data owners, SMEs, and relevant IT custodians) to assign target-state maturity levels in each question of the worksheet.
    2. Remember that there is more distance between levels 4 and 5 than there is between 1 and 2 – the distance between levels is not even throughout.
    3. To help assign values, think of the higher levels as representing cross-enterprise standardization, monitored for continuous improvement, formalized and standardized, while the lower levels mean applied within individual units, not formalized or tracked for performance.
    4. In tab 6, “Target State & Gap Analysis,” enter maturity values in each item of the Capabilities worksheet in the Target State column.
    5. Once you’ve assigned both target-state and current-state values, the tool will generate a gap analysis chart on tab 7, “Gap Analysis Results,” where you can start to decide first- and second-line priorities.

    Step 2.2

    Build Your Data Management Roadmap

    Activities

    2.2.1 Describe gaps

    2.2.2 Define gap initiatives

    2.2.2 Build a data management roadmap

    This step will guide you through the following activities:

    • Identify and understand data management gaps.
    • Develop data management improvement initiatives.
    • Build a data management–prioritized roadmap.

    Outcomes of this step

    • A foundation for data management initiative planning that’s aligned with the organization’s business architecture: value streams, business capability map, and strategy map

    Assess Data Management and Build Your Roadmap

    Step 2.1 Step 2.2 Step 2.3

    2.2.1 Describe gaps

    Input: Target-state maturity level

    Output: Detail and context about gaps to lead planners to specific initiatives

    Materials: Data Management Assessment and Planning Tool

    Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians

    Based on the gaps result, describe the nature of the gap, which will lead to specific initiatives for the data management plan:

    1. In tab 6, “Target State & Gap Analysis,” the same tab where you entered your target-state maturity level, enter additional context about the nature and extent of each gap in the Gap Description column.
    2. Based on the best-practices framework we walked through in Phase 1, note the specific areas that are not fully developed in your organization; for example, we don’t have a model of our environment and its integrations, or there isn’t an established data quality practice with proactive monitoring and intervention.

    2.2.2 Define gap initiatives

    Input: Gaps analysis, Gaps descriptions

    Output: Data management initiatives

    Materials: Data Management Assessment and Planning Tool

    Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians

    Based on the gap analysis, start to define the data management initiatives that will close the gaps and help the organization achieve its target state.

    1. In tab 6, “Target State & Gap Analysis,” the same tab where you entered your target-state maturity level, note in the Gap Initiative column what actions you can take to address the gap for each item. For example, if we found through diagnostics and use cases that users didn’t understand the meaning of their data or reports, an initiative might be, “Build a standard enterprise business data catalog.”
    2. It’s an opportunity to brainstorm, to be creative, and think about possibilities. We’ll use the roadmap step to select initiatives from this list.
    3. There are things we can do right away to make a difference. Acknowledge the resources, talent, and leadership momentum you already have in your organization and leverage those to find activities that will work in your culture. For example, one company held a successful Data Day to socialize the roadmap and engage users.

    2.2.3 Build a data management roadmap

    Input: Gap initiatives, Target state and current-state assessment

    Output: Data management initiatives and roadmap

    Materials: Data Management Assessment and Planning Tool

    Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians

    Start to list tangible actions you will take to address gaps and achieve data objectives and business goals along with timelines and responsibility:

    1. With an understanding of your priority areas and specific gaps, and referring back to your use cases, draw up specific initiatives that you can track, measure, and align with your original goals.
    2. For example, in data governance, initiatives might include:
      • Assign data owners and stewards for all data assets.
      • Consolidate disparate business data catalogs.
      • Create a data governance charter or terms of reference.
    3. Alongside the initiatives, fill in other detail, especially who is responsible and timing (start and end dates). Assigning responsibility and some time markers will help to keep momentum alive and make the work projects real.

    Step 2.3

    Organize Business Data Domains

    Activities

    2.3.1 Define business data domains and assign owners

    This step will guide you through the following activities:

    • Identify business data domains that flow through and support the systems environment and business processes.
    • Define and organize business data domains with assigned owners, artifacts, and profiles.
    • Apply the domain map to building governance program.

    Outcomes of this step

    • Business data domain map with assigned owners and artifacts

    Assess Data Management and Build Your Roadmap

    Step 2.1 Step 2.2 Step 2.3

    2.3.1 Define business data domains

    Input: Target-state maturity level

    Output: Detail and context about gaps to lead planners to specific initiatives

    Materials: Data Management Assessment and Planning Tool

    Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians

    Identify the key data domains for each line of business, where the data resides, and the main contact or owner.

    1. We have an understanding of what the business wants to achieve, e.g. build customer loyalty or comply with privacy laws. But where is the data that can help us achieve that? What systems is that data moving and living in and who, if anyone, owns it?
    2. Define the main business data domains apart from what system it may be spread over. Use the worksheet on the next slide as an example.
    3. Examples of business data domains: Customer, Product, Vendor.
    4. Each domain should have owners and associated business processes. Assign data domain owners, application owners, and business process owners.

    Business and data domains

    [SAMPLE]

    Business Domain App/Data Domains Business Stewards Application Owners Business Owners
    Client Experience and Sales Tech Salesforce (Sales, Service, Experience Clouds), Mulesoft (integration point) (Any team inputting data into the system)
    Quality and Regulatory Salesforce
    Operations Salesforce, Salesforce Referrals, Excel spreadsheets, SharePoint
    Finance Workday, Sage 300 (AccPac), Salesforce, Moneris Finance
    Risk/Legal Network share drive/SharePoint
    Human Resources Workday, Network share drive/SharePoint HR team
    Corporate Sales Salesforce (Sales, Service, Health, Experience Clouds),
    Sales and Client Success Mitel, Outlook, PDF intake forms, Workday, Excel. Sales & Client Success Director, Marketing Director CIO, Sales & Client Success Director, Marketing Director

    Embrace the technology

    Make the available data governance tools and technology work for you:
    • Data catalog
    • Business data glossary
    • Data lineage
    • Metadata management
    While data governance tools and technologies are no panacea, leverage their automated and AI-enabled capabilities to augment your data governance program.
    Array of logos of tech companies whose products are used for this type of work: Informatica, Collibra, Tibco, Alation, Immuta, TopQuadrant, and SoftwareReviews.

    Additional Support

    If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech Workshop.
    Photo of an analyst.

    Contact your account representative for more information.
    workshops@infotech.com 1-888-670-8889

    To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.

    Info-Tech analysts will join you and your team at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.

    The following are sample activities that will be conducted by Info-Tech analysts with your team:
    Sample of the Data Governance Strategy Map slide from earlier.

    Build Your Business and User Context

    Work with your core team of stakeholders to build out your data management roadmap, aligning data management initiatives with business capabilities, value streams, and, ultimately, your strategic priorities.
    Sample of a 'Data Management Enablers' table.

    Formulate a Plan to Get to Your Target State

    Develop a data management future-state roadmap and plan based on an understanding of your current data governance capabilities, your operating environment, and the driving needs of your business.

    Related Info-Tech Research

    Stock image of people pointing to a tablet with a dashboard.

    Build a Robust and Comprehensive Data Strategy

    Key to building and fostering a data-driven culture.
    Sample of the 'Data & Analytics Landscape' slide from earlier.

    Understand the Data and Analytics Landscape

    Optimize your data and analytics environment.
    Stock image of co-workers looking at the same thing.

    Build a Data Pipeline for Reporting and Analytics

    Data architecture best practices to prepare data for reporting and analytics.

    Research Contributors

    Name Position Company
    Anne Marie Smith Board of Directors DAMA International
    Andy Neill Practice Lead, Data & Analytics Info-Tech Research Group
    Dirk Coetsee Research Director, Data & Analytics Info-Tech Research Group
    Graham Price Executive Advisor, Advisory Executive Services Info-Tech Research Group
    Igor Ikonnikov Research Director, Data & Analytics Info-Tech Research Group
    Jean Bujold Senior Workshop Delivery Director Info-Tech Research Group
    Mario Cantin Chief Data Strategist Prodago
    Martin Sykora Director NexJ Analytics
    Michael Blaha Author, Patterns of Data Modeling Consultant
    Rajesh Parab Research Director, Data & Analytics Info-Tech Research Group
    Ranjani Ranganathan Product Manager, Research – Workshop Delivery Info-Tech Research Group
    Reddy Doddipalli Senior Workshop Director Info-Tech Research Group

    Bibliography

    AIIM, “What is Enterprise Content Management (ECM)?” Intelligent Information Management Glossary, AIIM, 2021. Web.

    BABOK V3: A Guide to Business Analysis Body of Knowledge. IIBA, 2014. Web.

    Barton, Dominic, and David Court. "Three Keys To Building a Data-Driven Strategy." McKinsey and Company, 1 Mar. 2013. Web.

    Boston University Libraries. "Data Life Cycle » Research Data Management | Boston University." Research Data Management RSS. Boston University, n.d. Accessed Oct. 2015.

    Chang, Jenny. “97 Supply Chain Statistics You Must Know: 2020 / 2021 Market Share Analysis & Data.” FinancesOnline, 2021. Web.

    COBIT 5: Enabling Information. ISACA, 2013. Web.

    CSC (Computer Sciences Corporation), Big Data Infographic, 2012. Web.

    DAMA International. DAMA-DMBOK Guide. 1st ed., Technics Publications, 2009. Digital.

    DAMA International. “DAMA Guide to the Data Management Body of Knowledge (DAMA-DMBOK2 Guide).” 2nd ed., 2017. Accessed June 2017.

    Davenport, Thomas H. "Analytics in Sports: The New Science of Winning." International Institute for Analytics, 2014. Web.

    Department of Homeland Security. Enterprise Data Management Policy. Department of Homeland Security, 25 Aug. 2014. Web.

    Enterprise Data Management Data Governance Plan. US Federal Student Aid, Feb. 2007. Accessed Oct. 2015.

    Experian. “10 signs you are sitting on a pile of data debt.” Experian, 2020. Accessed 25 June 2021.

    Fasulo, Phoebe. “6 Data Management Trends in Financial Services.” SecurityScorecard, 3 June 2021. Web.

    Georgia DCH Medicaid Enterprise – Data Management Strategy. Georgia Department of Community Health, Feb. 2015. Accessed Oct. 2015.

    Hadavi, Cyrus. “Use Exponential Growth of Data to Improve Supply Chain Operations.” Forbes, 5 Oct. 2021. Web.

    Harbert, Tam. “Tapping the power of unstructured data.” MIT Sloan, 1 Feb. 2021. Web.

    Hoberman, Steve, and George McGeachie. Data Modeling Made Simple with PowerDesigner. Technics Pub, 2011. Print.

    “Information Management Strategy.” Information Management – Alberta. Service Alberta, Nov.-Dec. 2013. Web.

    Jackson, Brian, et al. “2021 Tech Trends.” Info-Tech Research Group, 2021. Web.

    Jarvis, David, et al. “The hyperquantified athlete: Technology, measurement, and the business of sports.” Deloitte Insights, 7 Dec. 2020. Web.

    Bibliography

    Johnson, Bruce. “Leveraging Subject Area Models.” EIMInsight Magazine, vol. 3, no. 4, April 2009. Accessed Sept. 2015.

    Lewis, Larry. "How to Use Big Data to Improve Supply Chain Visibility." Talking Logistics, 14 Sep. 2014. Web.

    McAfee, Andrew, and Erik Brynjolfsson. “Big Data: The Management Revolution,” Harvard Business Review, vol. 90, no. 10, 2012, pp. 60-68.

    Meyer-Cuno, Doug. “Is A Vision Statement Important?” Forbes, 24 Feb. 2021. Web.

    MIT. “Big Data: The Management Revolution.” MIT Center for Digital Business, 29 May 2014. Accessed April 2014.

    "Open Framework, Information Management Strategy & Collaborative Governance.” MIKE2 Methodology RSS, n.d. Accessed Aug. 2015.

    PwC. “Asset Management 2020: A Brave New World.” PwC, 2014. Accessed April 2014.

    Riley, Jenn. Understanding Metadata: What is Metadata, and What is it For: A Primer. NISO, 1 Jan. 2017. Web.

    Russom, Philip. "TDWI Best Practices Report: Managing Big Data." TDWI, 2013. Accessed Oct. 2015.

    Schneider, Joan, and Julie Hall. “Why Most Product Launches Fail.” Harvard Business Review, April 2011. Web.

    Sheridan, Kelly. "2015 Trends: The Growth of Information Governance | Insurance & Technology." InformationWeek. UBM Tech, 10 Dec. 2014. Accessed Nov. 2015.

    "Sports Business Analytics and Tickets: Case Studies from the Pros." SloanSportsConference. Live Analytics – Ticketmaster, Mar. 2013. Accessed Aug. 2015.

    Srinivasan, Ramya. “Three Analytics Breakthroughs That Will Define Business in 2021.” Forbes, 4 May 2021. Web.

    Statista. “Amount of data created, consumed, and stored 2010-2020.” Statista, June 2021. Web.

    “Understanding the future of operations: Accenture Global Operations Megatrends research.” Accenture Consulting, 2015. Web.

    Vardhan, Harsh. “Why So Many Product Ideas Fail?” Medium, 26, Sept. 2020. Web.

    Tactics to Retain IT Talent

    • Buy Link or Shortcode: {j2store}549|cart{/j2store}
    • member rating overall impact: N/A
    • member rating average dollars saved: N/A
    • member rating average days saved: N/A
    • Parent Category Name: Engage
    • Parent Category Link: /engage
    • Regrettable turnover is impacting organizational productivity and leading to significant costs associated with employee departures and the recruitment required to replace them.
    • Many organizations focus on increasing engagement to improve retention, but this approach doesn’t address the entire problem.

    Our Advice

    Critical Insight

    • Engagement surveys mask the volatility of the employee experience and hide the reason why individual employees leave. You must also talk to employees to understand the moments that matter and engage managers to understand turnover triggers.

    Impact and Result

    • Build the case for creating retention plans by leveraging employee data and feedback to identify the key reasons for turnover that need to be addressed.
    • Target employee segments and work with management to develop solutions to retain top talent.

    Tactics to Retain IT Talent Research & Tools

    Besides the small introduction, subscribers and consulting clients within this management domain have access to:

    1. Tactics to Retain IT Talent Storyboard – Use this storyboard to develop a targeted talent retention plan to retain top and core talent in the organization.

    Integrate data from exit surveys and interviews, engagement surveys, and stay interviews to understand the most commonly cited reasons for employee departure in order to select and prioritize tactics that improve retention. This blueprint will help you identify reasons for regrettable turnover, select solutions, and create an action plan.

    • Tactics to Retain IT Talent Storyboard

    2. Retention Plan Workbook – Capture key information in one place as you work through the process to assess and prioritize solutions.

    Use this tool to document and analyze turnover data to find suitable retention solutions.

    • Retention Plan Workbook

    3. Stay Interview Guide – Managers will use this guide to conduct regular stay interviews with employees to anticipate and address turnover triggers.

    The Stay Interview Guide helps managers conduct interviews with current employees, enabling the manager to understand the employee's current engagement level, satisfaction with current role and responsibilities, suggestions for potential improvements, and intent to stay with the organization.

    • Stay Interview Guide

    4. IT Retention Solutions Catalog – Use this catalog to select and prioritize retention solutions across the employee lifecycle.

    Review best-practice solutions to identify those that are most suitable to your organizational culture and employee needs. Use the IT Retention Solutions Catalog to explore a variety of methods to improve retention, understand their use cases, and determine stakeholder responsibilities.

    • IT Retention Solutions Catalog
    [infographic]

    Workshop: Tactics to Retain IT Talent

    Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

    1 Identify Reasons for Regrettable Turnover

    The Purpose

    Identify the main drivers of turnover at the organization.

    Key Benefits Achieved

    Find out what to explore during focus groups.

    Activities

    1.1 Review data to determine why employees join, stay, and leave.

    1.2 Identify common themes.

    1.3 Prepare for focus groups.

    Outputs

    List of common themes/pain points recorded in the Retention Plan Workbook.

    2 Conduct Focus Groups

    The Purpose

    Conduct focus groups to explore retention drivers.

    Key Benefits Achieved

    Explore identified themes.

    Activities

    2.1 Conduct four 1-hour focus groups with the employee segment(s) identified in the pre-workshop activities.

    2.2 Info-Tech facilitators independently analyze results of focus groups and group results by theme.

    Outputs

    Focus group feedback.

    Focus group feedback analyzed and organized by themes.

    3 Identify Needs and Retention Initiatives

    The Purpose

    Home in on employee needs that are a priority.

    Key Benefits Achieved

    A list of initiatives to address the identified needs

    Activities

    3.1 Create an empathy map to identify needs.

    3.2 Shortlist retention initiatives.

    Outputs

    Employee needs and shortlist of initiatives to address them.

    4 Prepare to Communicate and Launch

    The Purpose

    Prepare to launch your retention initiatives.

    Key Benefits Achieved

    A clear action plan for implementing your retention initiatives.

    Activities

    4.1 Select retention initiatives.

    4.2 Determine goals and metrics.

    4.3 Plan stakeholder communication.

    4.4 Build a high-level action plan.

    Outputs

    Finalized list of retention initiatives.

    Goals and associated metrics recorded in the Retention Plan Workbook.

    Further reading

    Tactics to Retain IT Talent

    Keep talent from walking out the door by discovering and addressing moments that matter and turnover triggers.

    Executive Summary

    Your Challenge

    Many organizations are facing an increase in voluntary turnover as low unemployment, a lack of skilled labor, and a rise in the number of vacant roles have given employees more employment choices.

    Common Obstacles

    Regrettable turnover is impacting organizational productivity and leading to significant costs associated with employee departures and the recruitment required to replace them.

    Many organizations tackle retention from an engagement perspective: Increase engagement to improve retention. This approach doesn't consider the whole problem.

    Info-Tech's Approach

    Build the case for creating retention plans by leveraging employee data and feedback to identify the key reasons for turnover that need to be addressed.

    Target employee segments and work with management to develop solutions to retain top talent.

    Info-Tech Insight

    Engagement surveys mask the volatility of the employee experience and hide the reason why individual employees leave. You must also talk to employees to understand the moments that matter and engage managers to understand turnover triggers.

    This research addresses regrettable turnover

    This is an image of a flow chart with three levels. The top level has only one box, labeled Turnover.  the Second level has 2 boxes, labeled Voluntary, and Involuntary.  The third level has two boxes under Voluntary, labeled Non-regrettable: The loss of employees that the organization did not wish to keep, e.g. low performers, and Regrettable:  The loss of employees that the organization wishes it could have kept.

    Low unemployment and rising voluntary turnover makes it critical to focus on retention

    As the economy continues to recover from the pandemic, unemployment continues to trend downward even with a looming recession. This leaves more job openings vacant, making it easier for employees to job hop.

    This image contains a graph of the US Employment rate between 2020 - 2022 from the US Bureau of Economic Analysis and Bureau of Labor Statistics (BLS), 2022, the percentage of individuals who change jobs every one to five years from 2022 Job Seeker Nation Study, Jobvite, 2022, and voluntary turnover rates from BLS, 2022

    With more employees voluntarily choosing to leave jobs, it is more important than ever for organizations to identify key employees they want to retain and put plans in place to keep them.

    Retention is a challenge for many organizations

    The number of HR professionals citing retention/turnover as a top workforce management challenge is increasing, and it is now the second highest recruiting priority ("2020 Recruiter Nation Survey," Jobvite, 2020).

    65% of employees believe they can find a better position elsewhere (Legaljobs, 2021). This is a challenge for organizations in that they need to find ways to ensure employees want to stay at the organization or they will lose them, which results in high turnover costs.

    Executives and IT are making retention and turnover – two sides of the same coin – a priority because they cost organizations money.

    • 87% of HR professionals cited retention/turnover as a critical and high priority for the next few years (TINYpulse, 2020).
    • $630B The cost of voluntary turnover in the US (Work Institute, 2020).
    • 66% of organizations consider employee retention to be important or very important to an organization (PayScale, 2019).

    Improving retention leads to broad-reaching organizational benefits

    Cost savings: the price of turnover as a percentage of salary

    • 33% Improving retention can result in significant cost savings. A recent study found turnover costs, on average, to be around a third of an employee's annual salary (SHRM, 2019).
    • 37.9% of employees leave their organization within the first year. Employees who leave within the first 90 days of being hired offer very little or no return on the investment made to hire them (Work Institute, 2020).

    Improved performance

    Employees with longer tenure have an increased understanding of an organization's policies and processes, which leads to increased productivity (Indeed, 2021).

    Prevents a ripple effect

    Turnover often ripples across a team or department, with employees following each other out of the organization (Mereo). Retaining even one individual can often have an impact across the organization.

    Transfer of knowledge

    Retaining key individuals allows them to pass it on to other employees through communities of practice, mentoring, or other knowledge-sharing activities.

    Info-Tech Insight

    Improving retention goes beyond cost savings: Employees who agree with the statement "I expect to be at this organization a year from now" are 71% more likely to put in extra hours and 32% more likely to accomplish more than what is expected of their role (McLean & Company Engagement Survey, 2021; N=77,170 and 97,326 respectively).

    However, the traditional engagement-focused approach to retention is not enough

    Employee engagement is a strong driver of retention, with only 25% of disengaged employees expecting to be at their organization a year from now compared to 92% of engaged employees (McLean & Company Engagement Survey, 2018-2021; N=117,307).

    Average employee Net Promoter Score (eNPS)

    This image contains a graph of the Average employee Net Promoter Score (eNPS)

    Individual employee Net Promoter Scores (eNPS)

    This image contains a graph of the Individual employee Net Promoter Scores (eNPS)

    However, engagement surveys mask the volatility of the employee experience and hide the reason why individual employees leave.

    This analysis of McLean & Company's engagement survey results shows that while an organization's average employee net promoter score (eNPS) stays relatively static, at an individual level there is a huge amount of volatility.

    This demonstrates the need for an approach that is more capable of responding to or identifying employees' in-the-moment needs, which an annual engagement survey doesn't support.

    Turnover triggers and moments that matter also have an impact on retention

    Retention needs to be monitored throughout the employee lifecycle. To address the variety of issues that can appear, consider three main paths to turnover:

    1. Employee engagement – areas of low engagement.
    2. Turnover triggers that can quickly lead to departures.
    3. Moments that matter in the employee experience (EX).

    Employee engagement

    Engagement drivers are strong predictors of turnover.

    Employees who are highly engaged are 3.6x more likely to believe they will be with the organization 12 months from now than disengaged employees (McLean & Company Engagement Survey, 2018-2021; N=117,307).

    Turnover triggers

    Turnover triggers are events that act as shocks or catalysts that quickly lead to an employee's departure.

    Turnover triggers are a cause for voluntary turnover more often than accumulated issues (Lee et al.).

    Moments that matter

    Employee experience is the employee's perception of the accumulation of moments that matter within their employee lifecycle.

    Retention rates increase from 21% to 44% when employees have positive experiences in the following categories: belonging, purpose, achievement, happiness, and vigor at work. (Workhuman, 2020).

    While managers do not directly impact turnover, they do influence the three main paths to turnover

    Research shows managers do not appear as one of the common reasons for employee turnover.

    Top five most common reasons employees leave an organization (McLean & Company, Exit Survey, 2018-2021; N=107 to 141 companies,14,870 to 19,431 responses).

    Turnover factorsRank
    Opportunities for career advancement1
    Satisfaction with my role and responsibilities2
    Base pay3
    Opportunities for career-related skill development4
    The degree to which my skills were used in my job5

    However, managers can still have a huge impact on the turnover of their team through each of the three main paths to turnover:

    Employee engagement

    Employees who believe their managers care about them as a person are 3.3x more likely to be engaged than those who do not (McLean & Company, 2021; N=105,186).

    Turnover triggers

    Managers who are involved with and aware of their staff can serve as an early warning system for triggers that lead to turnover too quickly to detect with data.

    Moments that matter

    Managers have a direct connection with each individual and can tailor the employee experience to meet the needs of the individuals who report to them.

    Gallup has found that 52% of exiting employees say their manager could have done something to prevent them from leaving (Gallup, 2019). Do not discount the power of managers in anticipating and preventing regrettable turnover.

    Addressing engagement, turnover triggers, and moments that matter is the key to retention

    This is an image of a flow chart with four levels. The top level has only one box, labeled Turnover.  the Second level has 2 boxes, labeled Voluntary, and Involuntary.  The third level has two boxes under Voluntary, labeled Non-regrettable, and Regrettable.  The fourth level has three boxes under Regrettable, labeled Employee Engagement, Turnover triggers, and Moments that matter

    Info-Tech Insight

    HR traditionally seeks to examine engagement levels when faced with retention challenges, but engagement is only a part of the full picture. You must also talk to employees to understand the moments that matter and engage managers to understand turnover triggers.

    Follow Info-Tech's two-step process to create a retention plan

    1. Identify Reasons for Regrettable Turnover

    2. Select Solutions and Create an Action Plan

    Step 1

    Identify Reasons for Regrettable Turnover

    After completing this step you will have:

    • Analyzed and documented why employees join, stay, and leave your organization.
    • Identified common themes and employee needs.
    • Conducted employee focus groups and prioritized employee needs.

    Step 1 focuses on analyzing existing data and validating it through focus groups

    Employee engagement

    Employee engagement and moments that matter are easily tracked by data. Validating employee feedback data by speaking and empathizing with employees helps to uncover moments that matter. This step focuses on analyzing existing data and validating it through focus groups.

    Engagement drivers such as compensation or working environment are strong predictors of turnover.
    Moments that matter
    Employee experience (EX) is the employee's perception of the accumulation of moments that matter with the organization.
    Turnover triggers
    Turnover triggers are events that act as shocks or catalysts that quickly lead to an employee's departure.

    Turnover triggers

    This step will not touch on turnover triggers. Instead, they will be discussed in step 2 in the context of the role of the manager in improving retention.

    Turnover triggers are events that act as shocks or catalysts that quickly lead to an employee's departure.

    Info-Tech Insight

    IT managers often have insights into where and why retention is an issue through their day-to-day work. Gathering detailed quantitative and qualitative data provides credibility to these insights and is key to building a business case for action. Keep an open mind and allow the data to inform your gut feeling, not the other way around.

    Gather data to better understand why employees join, stay, and leave

    Start to gather and examine additional data to accurately identify the reason(s) for high turnover. Begin to uncover the story behind why these employees join, stay, and leave your organization through themes and trends that emerge.

    Look for these icons throughout step 2.

    Join

    Why do candidates join your organization?

    Stay

    Why do employees stay with your organization?

    Leave

    Why do employees leave your organization?

    For more information on analysis, visualization, and storytelling with data, see Info-Tech's Start Making Data-Driven People Decisions blueprint.

    Employee feedback data to look at includes:

    Gather insights through:

    • Focus groups
    • Verbatim comments
    • Exit interviews
    • Using the employee value proposition (EVP) as a filter (does it resonate with the lived experience of employees?)

    Prepare to draw themes and trends from employee data throughout step 1.

    Uncover employee needs and reasons for turnover by analyzing employee feedback data.

    • Look for trends (e.g. new hires join for career opportunities and leave for the same reason, or most departments have strong work-life balance scores in engagement data).
    • Review if there are recurring issues being raised that may impact turnover.
    • Group feedback to highlight themes (e.g. lack of understanding of EVP).
    • Identify which key employee needs merit further investigation or information.

    This is an image showing how you can draw out themes and trends using employee data throughout step 1.

    Classify where key employee needs fall within the employee lifecycle diagram in tab 2 of the Retention Plan Workbook. This will be used in step 2 to pinpoint and prioritize solutions.

    Info-Tech Insight

    The employee lifecycle is a valuable way to analyze and organize engagement pain points, moments that matter, and turnover triggers. It ensures that you consider the entirety of an employee's tenure and the different factors that lead to turnover.

    Examine new hire data and begin to document emerging themes

    Join

    While conducting a high-level analysis of new hire data, look for these three key themes impacting retention:

    Issues or pain points that occurred during the hiring process.

    Reasons why employees joined your organization.

    The experience of their first 90 days. This can include their satisfaction with the onboarding process and their overall experience with the organization.

    Themes will help to identify areas of strength and weakness organization-wide and within key segments. Document in tab 3 of the Retention Plan Workbook.

    1. Start by isolating the top reasons employees joined your organization. Ask:
      • Do the reasons align with the benefits you associate with working at your organization?
      • How might this impact your EVP?
      • If you use a new hire survey, look at the results for the following questions:
      • For which of the following reasons did you apply to this organization?
      • For what reasons did you accept the job offer with this organization?
    2. then, examine other potential problem areas that may not be covered by your new hire survey, such as onboarding or the candidate experience during the hiring process.
      • If you conduct a new hire survey, look at the results in the following sections:
        • Candidate Experience
        • Acclimatization
        • Training and Development
        • Defining Performance Expectations

      Analyze engagement data to identify areas of strength that drive retention

      Employees who are engaged are 3.6x more likely to believe they will be with the organization 12 months from now (McLean & Company Engagement Survey, 2018-2021; N=117,307). Given the strength of this relationship, it is essential to identify areas of strength to maintain and leverage.

      1. Look at the highest-performing drivers in your organization's employee engagement survey and drivers that fall into the "leverage" and "maintain" quadrants of the priority matrix.
        • These drivers provide insight into what prompts broader groups of employees to stay.

      This is an image of a quadrant analysis, with the following quadrants in order from left to right, top to bottom.  Improve; Leverage; Evaluate; Maintain.

      1. Look into what efforts have been made to maintain programs, policies, and practices related to these drivers and ensure they are consistent across the entire organization.
      2. Document trends and themes related to engagement strengths in tab 2 of the Retention Plan Workbook.

      If you use Info-Tech's Engagement Survey, look in detail at what are classified as "Retention Drivers": total compensation, working environment, and work-life balance.

      Identify areas of weakness that drive turnover in your engagement data

      1. Look at the lowest-performing drivers in your organization's employee engagement survey and drivers that fall into the "improve" and "evaluate" quadrants of the priority matrix.
        • These drivers provide insight into what pushes employees to leave the organization.
      2. Delve into organizational efforts that have been made to address issues with the programs, policies, and practices related to these drivers. Are there any projects underway to improve them? What are the barriers preventing improvements?
      3. Document trends and themes related to engagement weaknesses in tab 2 of the Retention Plan Workbook.

      If you use a product other than Info-Tech's Engagement Survey, your results will look different. The key is to look at areas of weakness that emerge from the data.

      This is an image of a quadrant analysis, with the following quadrants in order from left to right, top to bottom.  Improve; Leverage; Evaluate; Maintain.

      If you use Info-Tech's Engagement Survey, look in detail at what are classified as "Retention Drivers": total compensation, working environment, and work-life balance.

      Mine exit surveys to develop an integrated, holistic understanding of why employees leave

      Conduct a high-level analysis of the data from your employee exit diagnostic. While analyzing this data, consider the following:

      • What are the trends and quantitative data about why employees leave your organization that may illuminate employee needs or issues at specific points throughout the employee lifecycle?
      • What are insights around your key segments? Data on key segments is easily sliced from exit survey results and can be used as a starting point for digging deeper into retention issues for specific groups.
      • Exit surveys are an excellent starting point. However, it is valuable to validate the data gathered from an exit survey using exit interviews.
      1. Isolate results for key segments of employees to target with retention initiatives (e.g. by age group or by department).
      2. Identify data trends or patterns over time; for example, that compensation factors have been increasing in importance.
      3. Document trends and themes taken from the exit survey results in tab 2 of the Retention Plan Workbook.

      If your organization conducts exit interviews, analyze the results alongside or in lieu of exit survey data.

      Compare new hire data with exit data to identify patterns and insights

      Determine if new hire expectations weren't met, prompting employees to leave your organization, to help identify where in the employee lifecycle issues driving turnover may be occurring.

      1. Look at your new hire data for the top reasons employees joined your organization.
        • McLean & Company's New Hire Survey database shows that the top three reasons candidates accept job offers on average are:
          1. Career opportunities
          2. Nature of the job
          3. Development opportunities
      2. Next, look at your exit data and the top reasons employees left your organization.
        1. McLean & Company's Exit Survey database shows that the top three reasons employees leave on average are:
          1. Opportunities for career advancement
          2. Base pay
          3. Satisfaction with my role and responsibilities
      3. Examine the results and ask:
        • Is there a link between why employees join and leave the organization?
        • Did they cite the same reasons for joining and for leaving?
        • What do the results say about what your employees do and do not value about working at your organization?
      4. Document the resulting insights in tab 2 of the Retention Plan Workbook.

      Example:

      A result where employees are leaving for the same reason they're joining the organization could signal a disconnect between your organization's employee value proposition and the lived experience.

      Revisit your employee value proposition to uncover misalignment

      Your employee value proposition (EVP), formal or informal, communicates the value your organization can offer to prospective employees.

      If your EVP is mismatched with the lived experience of your employees, new hires will be in for a surprise when they start their new job and find out it isn't what they were expecting.

      Forty-six percent of respondents who left a job within 90 days of starting cited a mismatch of expectations about their role ("Job Seeker Nation Study 2020," Jobvite, 2020).

      1. Use the EVP as a filter through which you look at all your employee feedback data. It will help identify misalignment between the promised and the lived experience.
      2. If you have EVP documentation, start there. If not, go to your careers page and put yourself in the shoes of a candidate. Ask what the four elements of an EVP look like for candidates:
        • Compensation and benefits
        • Day-to-day job elements
        • Working conditions
        • Organizational elements
      3. Next, compare this to your own day-to-day experiences. Does it differ drastically? Are there any contradictions with the lived experience at your organization? Are there misleading statements or promises?
      4. Document any insights or patterns you uncover in tab 2 of the Retention Plan Workbook.

      Conduct focus groups to examine themes

      Through focus groups, explore the themes you have uncovered with employees to discover employee needs that are not being met. Addressing these employee needs will be a key aspect of your retention plan.

      Identify employee groups who will participate in focus groups:

      • Incorporate diverse perspectives (e.g. employees, managers, supervisors).
      • Include employees from departments and demographics with strong and weak engagement for a full picture of how engagement impacts your employees.
      • Invite boomerang employees to learn why an individual might return to your organization after leaving.

      image contains two screenshots Mclean & Company's Standard Focus Group Guide.

      Customize Info-Tech's Standard Focus Group Guide based on the themes you have identified in tab 3 of the Retention Plan Workbook.

      The goal of the focus group is to learn from employees and use this information to design or modify a process, system, or other solution that impacts retention.

      Focus questions on the employees' personal experience from their perspective.

      Key things to remember:

      • It is vital for facilitators to be objective.
      • Keep an open mind; no feelings are wrong.
      • Beware of your own biases.
      • Be open and share the reason for conducting the focus groups.

      Info-Tech Insight

      Maintaining an open dialogue with employees will help flesh out the context behind the data you've gathered and allow you to keep in mind that retention is about people first and foremost.

      Empathize with employees to identify moments that matter

      Look for discrepancies between what employees are saying and doing.

      1. Say

      "What words or quotes did the employee use?"

      3.Think

      "What might the employee be thinking?"

      Record feelings and thoughts discussed, body language observed, tone of voice, and words used.

      Look for areas of negative emotion to determine the moments that matter that drive retention.

      2. Do

      "What actions or behavior did the employee demonstrate?"

      4. Feel

      "What might the employee be feeling?"

      Record them in tab 3 of the Retention Plan Workbook.

      5. Identify Needs

      "Needs are verbs (activities or desires), not nouns (solutions)"

      Synthesize focus group findings using Info-Tech's Empathy Map Template.

      6. Identify Insights

      "Ask yourself, why?"

      (Based on Stanford d.school Empathy Map Method)

      Distill employee needs into priority issues to address first

      Take employee needs revealed by your data and focus groups and prioritize three to five needs.

      Select a limited number of employee needs to develop solutions to ensure that the scope of the project is feasible and that the resources dedicated to this project are not stretched too thin. The remaining needs should not be ignored – act on them later.

      Share the needs you identify with stakeholders so they can support prioritization and so you can confirm their buy-in and approval where necessary.

      Ask yourself the following questions to determine your priority employee needs:

      • Which needs will have the greatest impact on turnover?
      • Which needs have the potential to be an easy fix or quick win?
      • Which themes or trends came up repeatedly in different data sources?
      • Which needs evoked particularly strong or negative emotions in the focus groups?

      This image contains screenshots of two table templates found in tab 5 of the Retention Plan Workbook

      In the Retention Plan Workbook, distill employee needs on tab 2 into three to five priorities on tab 5.

      Step 2

      Select Solutions and Create an Action Plan

      After completing this step, you will have:

      • Selected and prioritized solutions to address employee needs.
      • Created a plan to launch stay interviews.
      • Built an action plan to implement solutions.

      Select IT-owned solutions and implement people leader–driven initiatives

      Solutions

      First, select and prioritize solutions to address employee needs identified in the previous step. These solutions will address reasons for turnover that influence employee engagement and moments that matter.

      • Brainstorm solutions using the Retention Solutions Catalog as a starting point. Select a longlist of solutions to address your priority needs.
      • Prioritize the longlist of solutions into a manageable number to act on.

      People leaders

      Next, create a plan to launch stay interviews to increase managers' accountability in improving retention. Managers will be critical to solving issues stemming from turnover triggers.

      • Clarify the importance of harnessing the influence of people leaders in improving retention.
      • Discover what might cause individual employees to leave through stay interviews.
      • Increase trust in managers through training.

      Action plan

      Finally, create an action plan and present to senior leadership for approval.

      Look for these icons in the top right of slides in this step.

      Select solutions to employee needs, starting with the Retention Solutions Catalog

      Based on the priority needs you have identified, use the Retention Solutions Catalog to review best-practice solutions for pain points associated with each stage of the lifecycle.

      Use this tool as a starting point, adding to it and iterating based on your own experience and organizational culture and goals.

      This image contains three screenshots from Info-Tech's Retention Solutions Catalog.

      Use Info-Tech's Retention Solutions Catalog to start the brainstorming process and produce a shortlist of potential solutions that will be prioritized on the next slide.

      Info-Tech Insight

      Unless you have the good fortune of having only a few pain points, no single initiative will completely solve your retention issues. Combine one or two of these broad solutions with people-leader initiatives to ensure employee needs are addressed on an individual and an aggregate level.

      Prioritize solutions to be implemented

      Target efforts accordingly

      Quick wins are high-impact, low-effort initiatives that will build traction and credibility within the organization.

      Long-term initiatives require more time and need to be planned for accordingly but will still deliver a large impact. Review the planning horizon to determine how early these need to begin.

      Re-evaluate low-impact and low-effort initiatives and identify ones that either support other higher impact initiatives or have the highest impact to gain traction and credibility. Look for low-hanging fruit.

      Deprioritize initiatives that will take a high degree of effort to deliver lower-value results.

      When assessing the impact of potential solutions, consider:

      • How many critical segments or employees will this solution affect?
      • Is the employee need it addresses critical, or did the solution encompass several themes in the data you analyzed?
      • Will the success of this solution help build a case for further action?
      • Will the solution address multiple employee needs?

      Info-Tech Insight

      It's better to master a few initiatives than under-deliver on many. Start with a few solutions that will have a measurable impact to build the case for further action in the future.

      Solutions

      Low ImpactMedium ImpactLarge Impact
      Large EffortThis is an image of the used to help you prioritize solutions to be implemented.
      Medium Effort
      Low Effort

      Use tab 3 of the Retention Plan Workbook to prioritize your shortlist of solutions.

      Harness the influence of people leaders to improve employee retention

      Leaders at all levels have a huge impact on employees.

      Effective people leaders:

      • Manage work distribution.
      • Create a motivating work environment.
      • Provide development opportunities.
      • Ensure work is stimulating and challenging, but not overwhelming.
      • Provide clear, actionable feedback.
      • Recognize team member contributions.
      • Develop positive relationships with their teams.
      • Create a line of sight between what the employee is doing and what the organization's objectives are.

      Support leaders in recommitting to their role as people managers through Learning & Development initiatives with particular emphasis on coaching and building trust.

      For coaching training, see Info-Tech's Build a Better Manager: Team Essentials – Feedback and Coaching training deck.

      For more information on supporting managers to become better people leaders, see Info-Tech's Build a Better Manager: Manage Your People blueprint.

      "HR can't fix turnover. But leaders on the front line can."
      – Richard P. Finnegan, CEO, C-Suite Analytics

      Equip managers to conduct regular stay interviews to address turnover triggers

      Managers often have the most visibility into their employees' personal and work lives and have a key opportunity to anticipate and address turnover triggers.

      Stay interviews are an effective way of uncovering potential retention issues and allowing managers to act as an early warning system for turnover triggers.

      Examples of common turnover triggers and potential manager responses:

      • Moving, creating a long commute to the office.
        • Through stay interviews, a manager can learn that a long commute is an issue and can help find workarounds such as flexible/remote work options.
      • Not receiving an expected promotion.
        • A trusted manager can anticipate issues stemming from this, discuss why the decision was made, and plan development opportunities for future openings.

      Stay interview best practices

      1. Conducted by an employee's direct manager.
      2. Happen regularly as a part of an ongoing process.
      3. Based on the stay interview, managers produce a turnover forecast for each direct report.
        1. The method used by stay interview expert Richard P. Finnegan is simple: red for high risk, yellow for medium, and green for low.
      4. Provide managers with training and a rough script or list of questions to follow.
        1. Use and customize Info-Tech's Stay Interview Guide to provide a guide for managers on how to conduct a stay interview.
      5. Managers use the results to create an individualized retention action plan made up of concrete actions the manager and employee will take.

      Sources: Richard P. Finnegan, CEO, C-Suite Analytics; SHRM

      Build an action plan to implement the retention plan

      For each initiative identified, map out timelines and actions that need to be taken.

      When building actions and timelines:

      • Refer to the priority needs you identified in tab 4 of the Retention Plan Workbook and ensure they are addressed first.
      • Engage internal stakeholders who will be key to the development of the initiatives to ensure they have sufficient time to complete their deliverables.
        • For example, if you conduct manager training, Learning & Development needs to be involved in the development and launch of the program.
      • Include a date to revisit your baseline retention and engagement data in your project milestones.
      • Designate process owners for new processes such as stay interviews.

      Plan for stay interviews by determining:

      • Whether stay interviews will be a requirement for all employees.
      • How much flexibility managers will have with the process.
      • How you will communicate the stay interview approach to managers.
      • If manager training is required.
      • How managers should record stay interview data and how you will collect this data from them as a way to monitor retention issues.
        • For example, managers can share their turnover forecasts and action plans for each employee.

      Be clear about manager accountabilities for initiatives they will own, such as stay interviews. Plan to communicate the goals and timelines managers will be asked to meet, such as when they must conduct interviews or their responsibility to follow up on action items that come from interviews.

      Track project success to iterate and improve your solutions

      Analyze measurements

      • Regularly remeasure your engagement and retention levels to identify themes and trends that provide insights into program improvements.
      • For example, look at the difference in manager relationship score to see if training has had an impact, or look at changes in critical segment turnover to calculate cost savings.

      Revisit employee and manager feedback

      • After three to six months, conduct additional surveys or focus groups to determine the success of your initiatives and opportunities for improvement. Tweak the program, including stay interviews, based on manager and employee feedback.

      Iterate frequently

      • Revisit your initiatives every two or three years to determine if a refresh is necessary to meet changing organizational and employee needs and to update your goals and targets.

      Key insights

      Insight 1Insight 2Insight 3

      Retention and turnover are two sides of the same coin. You can't fix retention without first understanding turnover.

      Engagement surveys mask the volatility of the employee experience and hide the reason why individual employees leave. You must also talk to employees to understand the moments that matter and engage managers to understand turnover triggers.

      Improving retention isn't just about lowering turnover, it's about discovering what healthy retention looks like for your organization.

      Insight 4Insight 5Insight 6

      HR professionals often have insights into where and why retention is an issue. Gathering detailed employee feedback data through surveys and focus groups provides credibility to these insights and is key to building a case for action. Keep an open mind and allow the data to inform your gut feeling, not the other way around.

      Successful retention plans must be owned by both IT leaders and HR.

      IT leaders often have the most visibility into their employees' personal and work lives and have a key opportunity to anticipate and address turnover triggers.

      Stay interviews help managers anticipate potential retention issues on their teams.

      Workshop Overview

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889

      Info-Tech AnalystsPre-workPost-work
      Client Data Gathering and PlanningImplementation Supported Through Analyst Calls

      1.1 Discuss participants, logistics, overview of workshop activities

      1.2 Provide support to client for below activities through calls.

      2.1 Schedule follow-up calls to work through implementation of retention solutions based on identified needs.
      Client

      1.Gather results of engagement survey, new hire survey, exit survey, and any exit and stay interview feedback.

      2.Gather and analyze turnover data.

      3.Identify key employee segment(s) and identify and organize participants for focus groups.

      4.Complete cost of turnover analysis.

      5.Review turnover data and prioritize list of employee segments.

      1.Obtain senior leader approval to proceed with retention plan.

      2.Finalize and implement retention solutions.

      3.Prepare managers to conduct stay interviews.

      4.Communicate next steps to stakeholders.

      Workshop Overview

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889

      ActivitiesDay 1Day 2Day 3Day 4
      Assess Current StateConduct Focus GroupsIdentify Needs and Retention InitiativesPrepare to Communicate and Launch

      1.1 Review data to determine why employees join, stay, and leave.

      1.2 Identify common themes.

      1.3 Prepare for focus groups.

      2.1 Conduct four 1-hour focus groups with the employee segment(s) identified in the pre-workshop activities..

      2.2 Info-Tech facilitators independently analyze results of focus groups and group results by theme.

      3.1 Create an empathy map to identify needs

      3.2 Shortlist retention initiatives

      4.1 Select retention initiatives

      4.2 Determine goals and metrics

      4.3 Plan stakeholder communication4.4 Build a high-level action plan

      Deliverables

      1.List of common themes/pain points recorded in the Retention Plan Workbook

      2.Plan for focus groups documented in the Focus Group Guide

      1.Focus group feedback

      2.Focus group feedback analyzed and organized by themes

      1.Employee needs and shortlist of initiatives to address them1.Finalized list of retention initiatives

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

      Guided Implementation

      “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”

      Workshop

      “We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”

      Consulting

      “Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

      Diagnostics and consistent frameworks used throughout all four options

      Research Contributors and Experts

      Jeff Bonnell
      VP HR
      Info-Tech Research Group

      Phillip Kotanidis
      CHRO
      Michael Garron Hospital

      Michael McGuire
      Director, Organizational Development
      William Osler Health System

      Dr. Iris Ware
      Chief Learning Officer
      City of Detroit

      Richard P. Finnegan
      CEO
      C-Suite Analytics

      Dr. Thomas Lee
      Professor of Management
      University of Washington

      Jane Moughon
      Specialist in increasing profits, reducing turnover, and maximizing human potential in manufacturing companies

      Lisa Kaste
      Former HR Director
      Citco

      Piyush Mathur
      Head of Workforce Analytics
      Johnson & Johnson

      Gregory P. Smith
      CEO
      Chart Your Course

      Works Cited

      "17 Surprising Statistics about Employee Retention." TINYpulse, 8 Sept. 2020. Web.
      "2020 Job Seeker Nation Study." Jobvite, April 2020. Web.
      "2020 Recruiter Nation Survey." Jobvite, 2020. Web.
      "2020 Retention Report: Insights on 2019 Turnover Trends, Reasons, Costs, & Recommendations." Work Institute, 2020. Web.
      "25 Essential Productivity Statistics for 2021." TeamStage, 2021. Accessed 22 Jun. 2021.
      Agovino, Theresa. "To Have and to Hold." SHRM, 23 Feb. 2019. Web.
      "Civilian Unemployment Rate." Bureau of Labor Statistics, June 2020. Web.
      Foreman, Paul. "The domino effect of chief sales officer turnover on salespeople." Mereo, 19 July 2018. Web.
      "Gross Domestic Product." U.S. Bureau of Economic Analysis, 27 May 2021. Accessed 22 Jun. 2020.
      Kinne, Aaron. "Back to Basics: What is Employee Experience?" Workhuman, 27August 2020. Accessed 21 Jun. 2021.
      Lee, Thomas W, et al. "Managing employee retention and turnover with 21st century ideas." Organizational Dynamics, vol 47, no. 2, 2017, pp. 88-98. Web.
      Lee, Thomas W. and Terence R. Mitchell. "Control Turnover by Understanding its Causes." The Blackwell Handbook of Principles of Organizational Behaviour. 2017. Print.
      McFeely, Shane, and Ben Wigert. "This Fixable Problem Costs U.S. Businesses $1 Trillion." Gallup. 13 March 2019. Web.
      "Table 18. Annual Quit rates by Industry and Region Not Seasonally Adjusted." Bureau of Labor Statistics. June 2021. Web.
      "The 2019 Compensation Best Practices Report: Will They Stay or Will They Go? Employee Retention and Acquisition in an Uncertain Economy." PayScale. 2019. Web.
      Vuleta, Branka. "30 Troubling Employee Retention Statistics." Legaljobs. 1 Feb. 2021. Web.
      "What is a Tenured Employee? Top Benefits of Tenure and How to Stay Engaged as One." Indeed. 22 Feb. 2021. Accessed 22 Jun. 2021.

      Improve IT Team Effectiveness

      • Buy Link or Shortcode: {j2store}521|cart{/j2store}
      • member rating overall impact: 9.3/10 Overall Impact
      • member rating average dollars saved: $16,549 Average $ Saved
      • member rating average days saved: 5 Average Days Saved
      • Parent Category Name: Lead
      • Parent Category Link: /lead
      • Organizations rely on team-based work arrangements to provide organizational benefits and to help them better navigate the volatile, uncertain, complex, and ambiguous (VUCA) operating environment.
      • This is becoming more challenging in a hybrid model as interactions now rely less on casual encounters and now must become more intentional.
      • A high-performing team is more than productive. They are more resilient and able to recognize opportunities. They are proactive instead of reactive due to trust and a high level of communication and collaboration.
      • IT teams are more unique, which also provides unique challenges other teams don’t experience.

      Our Advice

      Critical Insight

      IT teams have:

      • Multiple disciplines that tend to operate in parallel versus within a sequence of events.
      • Multiple incumbent roles where people operate in parallel versus needing to share information to produce an outcome.
      • Multiple stakeholders who create a tension with competing priorities.

      Impact and Result

      Use Info-Tech’s phased approach to diagnose your team and use the IDEA model to drive team effectiveness.

      The IDEA model includes four factors to identify team challenges and focus on areas for improvement: identity, decision making, exchanges within the team, and atmosphere of team psychological safety.

      Improve IT Team Effectiveness Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Team Effectiveness Storyboard – A step-by-step document that walks you through how to properly assess your team’s effectiveness and activities that will identify solutions to overcome.

      The storyboard will walk you through three critical steps to assess, analyze, and build solutions to improve your team’s effectiveness.

    • Having your team members complete an assessment.
    • Reviewing and sharing the results.
    • Building a list of activities to select from based on the assessment results to ensure you target the problem you are facing.
      • Improve IT Team Effectiveness Storyboard – Phases 1-3

      2. The Team Effectiveness Survey – A tool that will determine what areas you are doing well in and where you can improve team relations and increase productivity.

      Each stage has a deliverable that will support your journey on increasing effectiveness starting with how to communicate to the assessment which will accumulate into a team charter and action plan.

      • IT Team Effectiveness Survey
      • IT Team Effectiveness Survey Tool

      3. Facilitation Guide – A collection of activities to select from and use with your team.

      The Facilitation Guide contains instructions to facilitating several activities aligned to each area of the IDEA Model to target your approach directly to your team’s results.

    • Determining roles and responsibilities on the team.
    • Creating a decision-making model that outlines levels of authority and who makes the decisions.
    • Assessing the team communications flow, which highlights the communication flow on the team and any bottlenecks.
    • Building a communication poster that articulates methods used to share different information within the team.
      • Improve IT Team Effectiveness Facilitation Guide
      • Identity – Responsibilities and Dependencies
      • Decision Making Accountability Workbook
      • Exchanges – Team Communications Flow
      • Exchanges – Communications Guide Poster Template
      • Atmosphere – SCARF Worksheet

      4. Action Plan – A template to help build your team action plan.

      The Action Plan Template captures next steps for the team on what they are committing to in order to build a more effective team.

      • Action Plan Template

      5. Team Charter – A template to create a charter for a work group or project team.

      A Team Charter captures the agreements your team makes with each other in terms of accepted behaviors and how they will communicate, make decisions, and create an environment that everyone feels safe contributing in.

      • IT Team Charter Template

      Infographic

      Workshop: Improve IT Team Effectiveness

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Assess the Team

      The Purpose

      Determine if proceeding is valuable.

      Key Benefits Achieved

      Set context for team members.

      Activities

      1.1 Review the business context.

      1.2 Identify IT team members to be included.

      1.3 Determine goals and objectives.

      1.4 Build execution plan and determine messaging.

      1.5 Complete IDEA Model assessment.

      Outputs

      Execution and communication plan

      IDEA Model assessment distributed

      2 Review Results and Action Plan

      The Purpose

      Review results to identify areas of strength and opportunity.

      Key Benefits Achieved

      As a team, discuss results and determine actions.

      Activities

      2.1 Debrief results with leadership team.

      2.2 Share results with team.

      2.3 Identify areas of focus.

      2.4 Identify IDEA Model activities to support objectives and explore areas of focus.

      Outputs

      IDEA assessment results

      Selection of specific activities to be facilitated

      3 Document and Measure

      The Purpose

      Review results to identify areas of strength and opportunity.

      Key Benefits Achieved

      build an action plan of solutions to incorporate into team norms.

      Activities

      3.1 Create team charter.

      3.2 Determine action plan for improvement.

      3.3 Determine metrics.

      3.4 Determine frequency of check-ins.

      Outputs

      Team Charter

      Action Plan

      Further reading

      Improve IT Team Effectiveness

      Implement the four critical factors required for all high-performing teams.

      Analyst Perspective

      All teams need to operate effectively; however, IT teams experience unique challenges.

      IT often struggles to move from an effective to a high-performing team due to the very nature of their work. They work across multiple disciplines and with multiple stakeholders.

      When operating across many disciplines it can become more difficult to identify the connections or points of interactions that define effective teams and separate them from being a working group or focus on their individual performance.

      IT employees also work in close partnership with multiple teams outside their IT domain, which can create confusion as to what team are they a primary member of. The tendency is to advocate for or on behalf of the team they primarily work with instead of bringing the IT mindset and alignment to IT roadmap and goals to serve their stakeholders.

      A Picture of Amanda Mathieson

      Amanda Mathieson
      Research Director, People & Leadership Practice
      Info-Tech Research Group

      Executive Summary

      The Challenge

      Organizations rely on team-based work arrangements to provide organizational benefits and better navigate the volatile, uncertain, complex, and ambiguous (VUCA) operating environment.

      This is becoming more challenging in a hybrid environment as interactions now rely less on casual encounters and must become more intentional.

      A high-performing team is more than productive. They are more resilient and able to recognize opportunities. They are proactive instead of reactive due to the trust and high level of communication and collaboration.

      Common Obstacles

      IT teams are more unique, which also provides unique challenges other teams don't experience:

      • Multiple disciplines that tend to operate in parallel versus within a sequence of events
      • Multiple incumbent roles where people operate in parallel versus needing to share information to produce an outcome
      • Multiple stakeholders that create a tension with competing priorities

      Info-Tech's Approach

      Use Info-Tech's phased approach to diagnose your team and use the IDEA model to drive team effectiveness.

      The IDEA model includes four factors to identify team challenges and focus on areas for improvement: identity, decision making, exchanges within the team, and atmosphere of team psychological safety.

      Info-Tech Insight

      IT teams often fail to reach their full potential because teamwork presents unique challenges and complexities due to the work they do across the organization and within their own group. Silos, not working together, and not sharing knowledge are all statements that indicate a problem. As a leader it's difficult to determine what to do first to navigate the different desires and personalities on a team.

      How this blueprint will help

      Assess, diagnose, and address issues to realize your team's full potential.

      This research helps IT support:

      • Work Teams: Operate under one organizational unit or function. Their membership is generally stable with well-defined roles.
      • Project Teams: Typically, are time-limited teams formed to produce a particular output or project. Their membership and expertise tend to vary over time.
      • Management or Leadership Teams: Provide direction and guidance to the organization and are accountable for overall performance. Membership is structured by the hierarchy of the organization and includes a diverse set of skills, experience, and expertise.

      Traditionally, organizations have tried to fix ineffective teams by focusing on these four issues: composition, leadership competencies, individual-level performance, and organizational barriers. While these factors are important, our research has shown it is beneficial to focus on the four factors of effective teams addressed in this blueprint first. Then, if additional improvement is needed, shift your focus to the traditional issue areas.

      Common obstacles

      These barriers make it difficult to address effectiveness for many IT teams:

      • Teams do not use one standard set of processes because they may have a wide variety of assignments requiring different sets of processes.
        Source: Freshworks
      • There are multiple disciplines within IT that require vastly different skill sets. Finding the connection points can be difficult when on the surface it seems like success doesn't require interconnectivity.
      • IT has many people in the same roles that act independently based on the stakeholder or internal customer they are serving. This can lead to duplication of effort if information and solutions aren't shared.
      • IT serves many parts of the organization that can bring competing priorities both across the groups they support and with the IT strategy and roadmap itself. Many IT leaders work directly in or for the business, which can see them associate with the internal client team more than their IT team – another layer of conflicting priorities.

      IT also experience challenges with maturity and data silos

      48%

      of IT respondents rate their team as low maturity.

      Maturity is defined by the value they provide the business, ranging from firefighting to innovative partner.

      Source: Info-Tech Research Group, Tech Trends, 2022

      20 Hours

      Data Silos: Teams waste more than 20 hours per month due to poor collaboration and communication.

      Source: Bloomfire, 2022

      Current realities require teams to operate effectively

      How High-Performing Teams Respond:

      Volatile: High degree of change happening at a rapid pace, making it difficult for organizations to respond effectively.

      Teams are more adaptable to change because they know how to take advantage of each others' diverse skills and experience.

      Uncertain: All possible outcomes are not known, and we cannot accurately assess the probability of outcomes that are known.

      Teams are better able to navigate uncertainty because they know how to work through complex challenges and feel trusted and empowered to change approach when needed.

      Complex: There are numerous risk factors, making it difficult to get a clear sense of what to do in any given situation.

      Teams can reduce complexity by working together to identify and plan to appropriately mitigate risk factors.

      Ambiguous: There is a lack of clarity with respect to the causes and consequences of events.

      Teams can reduce ambiguity through diverse situational knowledge, improving their ability to identify cause and effect.

      Teams struggle to realize their full potential

      Poor Communication

      To excel, teams must recognize and adapt to the unique communication styles and preferences of their members.

      To find the "just right" amount of communication for your team, communication and collaboration expectations should be set upfront.

      85% of tech workers don't feel comfortable speaking in meetings.
      Source: Hypercontext, 2022

      Decision Making

      Decision making is a key component of team effectiveness. Teams are often responsible for decisions without having proper authority.

      Establishing a team decision-making process becomes more complicated when appropriate decision-making processes vary according to the level of interdependency between team members and organizational culture.

      20% of respondents say their organization excels at decision making.
      Source: McKinsey, 2019

      Resolving Conflicts

      It is common for teams to avoid/ignore conflict – often out of fear. People fail to see how conflict can be healthy for teams if managed properly.

      Leaders assume mature adults will resolve conflicts on their own. This is not always the case as people involved in conflicts can lack an objective perspective due to charged emotions.

      56% of respondents prioritize restoring harmony in conflict and will push own needs aside.
      Source: Niagara Institute, 2022

      Teams with a shared purpose are more engaged and have higher performance

      Increased Engagement

      3.5x

      Having a shared team goal drives higher engagement. When individuals feel like part of a team working toward a shared goal, they are 3.5x more likely to be engaged.

      Source: McLean & Company, Employee Engagement Survey, IT respondents, 2023; N=5,427

      90%

      Engaged employees are stronger performers with 90% reporting they regularly accomplish more than what is expected.

      Source: McLean & Company, Employee Engagement Survey, IT respondents, 2023; N=4,363

      Effective and high-performing teams exchange information freely. They are clear on the purpose and goals of the organization, which enable empowerment.

      Info-Tech Insight

      Clear decision-making processes allow employees to focus on getting the work done versus navigating the system.

      Case Study

      Project Aristotle at Google – What makes a team effective at Google?

      INDUSTRY: Technology
      SOURCE: reWork

      Challenge

      Google wanted to clearly define what makes a team effective to drive a consistent meaning among its employees. The challenge was to determine more than quantitative measures, because more is not always better as it can just mean more mistakes to fix, and include the qualitative factors that bring some groups of people together better than others.

      Solution

      There was no pattern in the data it studied so Google stepped back and defined what a team is before embarking on defining effectiveness. There is a clear difference between a work group (a collection of people with little interdependence) and a team that is highly interdependent and relies on each other to share problems and learn from one another. Defining the different meanings took time and Google found that different levels of the organization were defining effectiveness differently.

      Results

      Google ended up with clear definitions that were co-created by all employees, which helped drive the meaning behind the behaviors. More importantly it was also able to define factors that had no bearing on effectiveness; one of which is very relevant in today's hybrid world – colocation.

      It was discovered that teams need to trust, have clarity around goals, have structure, and know the impact their work has.

      Overcoming barriers

      Teams often lack the skills or knowledge to increase effectiveness and performance.

      • Leaders struggle with team strife and ineffectiveness.
      • A leader's ability to connect with and engage team members is vital for driving desired outcomes. However, many team leads struggle to deal with low-performing or conflict-ridden teams.
      • Without adequate training on providing feedback, coaching, and managing difficult conversations, team leads often do not have the skills to positively affect team performance – and they do not appreciate the impact their actions have on desired outcomes.
      • Team leads often find it difficult to invest time and resources in addressing challenges when the team is working toward deadlines.
      • Team leads who are new to a management role within the organization often struggle to transition from independent contributor to leader – especially when they are tasked with managing team members who are former peers.
      • Some team leads believe that soliciting help will be viewed as a personal failure, so they are reluctant to seek support for team performance management from more-senior leaders.

      It's unrealistic to expect struggling teams to improve without outside help; if they were able to, they would have already done so.
      To improve, teams require:

      • A clearly defined team identity
      • A clearly defined decision-making paradigm
      • Consistently productive exchanges within the team
      • An atmosphere of psychological safety

      BUT these are the very things they are lacking when they're struggling.

      An image of Info-Tech's Insights for Improving IT Team Effectiveness.

      Improving team effectiveness

      Use the Info-Tech IDEA Model to assess and improve your team's effectiveness.

      Begin by assessing, recognizing, and addressing challenges in:

      • Identity – team goals, roles, responsibilities, and accountabilities
      • Decision-making paradigms and processes within the team.
      • Exchanges of information, motivation, and emotions between team members
      • Atmosphere of team psychological safety

      IDEA Model of Team Effectiveness

      Effective Team

      • Identity
      • Decisions
      • Exchanges
      • Atmosphere

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

      Guided Implementation

      “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”

      Workshop

      “We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”

      Consulting

      “Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

      Diagnostics and consistent frameworks used throughout all four options

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1: Assess the team Phase 2: Review results and action plan Phase 3: Document and measure

      Call #1: Scope requirements, objectives, and your specific challenges.
      Call #2: Prepare to assess your team(s) using the assessment tool.

      Call #3: Review the assessment results and plan next steps.
      Call #4: Review results with team and determine focus using IDEA model to identify activity based on results.
      Call #5: Complete activity to determine solutions to build your action plan.

      Call #6: Build out your team agreement.
      Call #7: Identify measures and frequency of check-ins to monitor progress.

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is 6 to 12 calls over the course of 4 to 6 months.

      Workshop Overview

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889

      Day 1
      (Half Day)

      Day 2

      Day 3

      Day 4

      Determine objectives and assess

      Review survey results

      Determine and conduct activities to increase effectiveness

      Bridge the gap and
      create the strategy

      Activities

      With Leader – 1 hour
      1.1 Review the business context.
      1.2 Identify IT team members to be included.
      1.3 Determine goals and objectives.
      1.4 Build execution plan and determine messaging.
      With Team – 90 minutes
      1.5 Share messaging, set context.
      1.6 Complete Team Effectiveness Survey.

      2.1 Debrief results with leadership team.
      2.2 Share results with team.
      2.3 Identify areas of focus.
      2.4 Identify IDEA Model activities to support objectives and explore areas of focus.

      3.1 Conduct IDEA Model Activities:

      • Identify – Clarify goals, roles, and responsibilities.
      • Decisions – Determine levels of authority; decision-making process.
      • Exchanges – Review information shared with communication methods and preferred styles of each team member.
      • Atmosphere – Create a psychologically safe environment.

      3.2 Record outcomes and actions.

      4.1 Create team charter or agreement.
      4.2 Identify metrics to measure progress.
      4.3 Identify risks.
      4.4 Determine frequency of check-ins to review progress.
      4.5 Check-in with sponsor.

      Deliverables

      1. Execution and communication plan
      2. Team Effectiveness Survey
      1. Assessment results
      2. IDEA Model team-building activities
      1. List of solutions to incorporate into team norms
      2. Action Plan
      1. Team Charter

      Phase 1

      Assess the team

      Phase 1

      Phase 2

      Phase 3

      1.1 Identify team members
      and behaviors to improve using IDEA Model
      1.2 Determine messaging including follow-up plan
      1.3 Send survey

      1.1 Review results with team
      1.2 Determine IDEA focus area(s)
      1.3 Conduct activity to determine solutions

      1.1 Document outcomes and actions
      1.2 Create team charter
      1.3 Identify metrics to show success
      1.4 Schedule check-in

      Improving team effectiveness

      Use the Info-Tech IDEA Model to assess and improve your team's effectiveness

      Begin by assessing, recognizing, and addressing challenges in:

      • Identity – team goals, roles, responsibilities, and accountabilities.
      • Decision-making paradigms and processes within the team.
      • Exchanges of information, motivation, and emotions between team members.
      • Atmosphere of team psychological safety.

      Effective Team

      • Identity
      • Decisions
      • Exchanges
      • Atmosphere

      Assess the shared understanding of team identity

      In addition to having a clear understanding of the team's goals and objectives, team members must also:

      • Understand their own and each other's roles, responsibilities, and accountabilities.
      • Recognize and appreciate the value of each team member.
      • Realize how their actions impact each others' work and the overall goals and objectives.
      • Understand that working in silos is considered a work group whereas a team coordinates activities, shares information, and supports each other to achieve their goals.

      Clear goals enable employees to link their contributions to overall success of the team. Those who feel their contributions are important to the success of the department are two times more likely to feel they are part of a team working toward a shared goal compared to those who don't (McLean & Company, Employee Engagement Survey, IT respondents, 2023; N=4,551).

      Goals matter in teamwork

      The goals and objectives of the team are the underlying reason for forming the team in the first place. Without a clear and agreed-upon goal, it is difficult for teams to understand the purpose of their work.

      Clear goals support creating clear roles and the contributions required for team success.

      Team Identity = Team goals and Objectives + Individual roles, responsibilities, and accountabilities

      Assess the shared understanding of decision making

      Decision making adds to the complexity of teamwork.
      Individual team members hold different information and opinions that need to be shared to make good decisions.
      Ambiguous decision-making processes can result in team members being unable to continue their work until they get clear direction.
      The most appropriate decision-making process depends on the type of team:

      • The higher the degree of interconnectivity in team members' work, the greater the need for a general consensus approach to decision making. However, if you opt for a general consensus approach, a backup decision-making method must be identified in the event consensus cannot be reached.
      • High-pressure and high-stakes environments tend to centralize decision making to make important decisions quickly.
      • Low-pressure and low-stakes environments are more likely to adopt consensus models.

      Spectrum of Decision Making

      General consensus between all team members.

      A single, final decision maker within the team.

      Ensure team members understand how decisions are made within the team. Ask:

      • Do team members recognize the importance of sharing information, opinions, and suggestions?
      • Do team members feel their voices are heard?
      • Must there be consensus between all team members?
      • Is there a single decision maker?

      Assess team exchanges by focusing on communication

      Evaluate exchanges within your team using two categories:

      These categories are related, but there is not always overlap. While some conflicts involve failures to successfully exchange information, conflict can also occur even when everyone is communicating successfully.

      Communication

      Managing Conflict

      Information, motivations, emotions

      Accepting and expressing diverse perspectives

      Resolving conflict (unified action through diverse perspectives)

      Transmission

      Reception
      (listening)

      Success is defined in terms of how well information, motivations, and emotions are transmitted and received as intended.

      Success is defined in terms of how well the team can move to united action through differences of opinion. Effective teams recognize that conflict can be healthy if managed effectively.

      Successful exchange behaviors

      • Shared understanding of how to motivate one another and how team members respond emotionally.
      • Team moving beyond conflict to united action.
      • Formalized processes used for resolving conflicts.
      • Platforms provided for expressing diverse or conflicting perspectives and opinions – and used in a constructive manner.
      • Use of agendas at meetings as well as clearly defined action items that reflect meeting outcomes.
      • Avoidance of language that is exclusive, such as jargon and inside jokes.

      Exchanges of information, emotion, and motivation

      When selecting a method of communication (for example, in-person versus email), consider how that method will impact the exchange of all three aspects – not just information.

      Downplaying the importance of emotional and motivational exchanges and focusing solely on information is very risky since emotional and motivational exchanges can impact human relationships and team psychological safety.

      • Information: data or opinions.
      • Emotions: feelings and evaluations about the data or opinions.
      • Motivations: what we feel like doing in response to the data or opinions.

      Communication affects the whole team

      Effects are not limited to the team members communicating directly:

      • How team members interact one on one transmits information and causes emotional and motivational responses in other group members not directly involved.
      • How the larger group receives information, emotions, and motivations will also impact how individuals relate to each other in group settings.

      Remember to watch the reactions and behavior of participants and observers when assessing how the team behaves.

      Managing conflict

      Identify how conflict management is embedded into team practices.

      • Resolving conflicts is difficult and uses up a lot of time and energy. This is especially true if the team needs to figure out what to do each and every time people disagree.
      • Teams that take the time to define conflict resolution processes upfront:
        • Demonstrate their commitment to resolving conflict in a healthy way.
        • Signal that diverse perspectives and opinions are valued, even if they spur disagreement sometimes.
        • Are ready for conflict when it arises – prepared to face it and thrive.

      Successfully communicating information, emotions, and motivations is not the same as managing conflict.

      Teams that are communicating well are more likely to uncover conflicting perspectives and opinions than teams that are not.

      Conflict is healthy and can be an important element of team success if it is managed.

      The team should have processes in place to resolve conflicts and move to united action.

      Assess the atmosphere

      Team psychological safety

      A team atmosphere that exists when all members feel confident that team members can do the following without suffering negative interpersonal consequences such as blame, shame, or exclusion:

      • Admit mistakes
      • Raise questions or concerns
      • Express dissenting views

      (Administrative Science Quarterly, 1999;
      The New York Times, 2016)

      What psychologically safe teams look like:

      • Open and learning-focused approach to error.
      • Effective conflict management within the team.
      • Emotional and relational awareness between team members.
      • Existence of work-appropriate interpersonal relationships between team members (i.e. beyond mere working relationships).

      (Administrative Science Quarterly, 1999;
      The New York Times, 2016)

      What "team psychological safety" is not:

      • A situation where all team members are friends.
        In some cases psychologically safe team atmospheres might be harder to create when team members are friends since they might be more reluctant to challenge or disagree with friends.
      • Merely trust. Being able to rely on people to honor their commitments is not the same as feeling comfortable admitting mistakes in front of them or disagreeing with them.

      "Psychological safety refers to an individual's perception of the consequences of taking an interpersonal risk or a belief that a team is safe for risk taking in the face of being seen as ignorant, incompetent, negative, or disruptive… They feel confident that no one on the team will embarrass or punish anyone else for admitting a mistake, asking a question, or offering a new idea."

      – re:Work

      Psychological safety

      The impact of psychological safety on team effectiveness

      Why does an atmosphere of team psychological safety matter?

      • Prevents groupthink.
        • People who do not feel safe to hold or express dissenting views gravitate to teams that think like they do, resulting in the well-known dangers of groupthink.
      • Encourages contribution and co-operation.
        • One study found that if team psychological safety is present, even people who tend to avoid teamwork will be more likely to contribute in team settings, thereby increasing the diversity of perspectives that can be drawn on (Journal of Organizational Culture, 2016).

      Creating psychological safety in a hybrid environment requires a deliberate approach to creating team connectedness.

      In the Info-Tech State of Hybrid Work in IT report autonomy and team connectedness present an interesting challenge in that higher levels of autonomy drove higher perceptions of lack of connectedness to the respondent's team. In a hybrid world, this means leaders need to be intentional in creating a safe team dynamic.

      47% of employees who experienced more control over their decisions related to where, when, and how they work than before the pandemic are feeling less connected to their teams.
      Source: Info-Tech, State of Hybrid Work in IT, 2022

      1.1 Prepare to launch the survey

      1-2 hours

      1. Review and record the objectives and outcomes that support your vision of a high-performing team:
        1. Why is this important to you?
        2. What reactions do you anticipate from the team?
      2. In your team meeting, share your vision of what a high-performing team looks like. Engage the team in a discussion:
        1. Ask how they work. Ask them to describe their best working team environment from a previous experience or an aspirational one.
        2. Option: Instruct them to write on sticky notes, one idea per note, and share. This approach will allow for theming of ideas.
      3. Introduce the survey as a way, together as a team, the current state can be assessed against the desired state discussed.
        1. Be clear that as the leader, you won't be completing the survey as you don't want to influence their perceptions of the team. As the leader, you hold authority, and therefore, experience the team differently. This is about them and their feedback.

      Input

      • Observations of team behavior
      • Clearly articulated goals for team cohesion

      Output

      • Speaking notes for introducing survey
      • Survey launch

      Materials

      • Whiteboard/flip charts
      • Sticky notes
      • IDEA Assessment

      Participants

      • Leader
      • Team Members

      Download the IT Team Effectiveness Survey

      1.2 Launch the survey

      1-2 hours

      1. Determine how the survey will be completed.
        1. Paper-based
          1. Email a copy of the Word document IT Team Effectiveness Survey for each person to complete individually.
          2. Identify one person to collect each survey and enter the results into the team effectiveness survey tool (tab 2. Data – Effectiveness Answers and tab 3. Data – Team Type Answers). This must be someone outside the team.
        2. Online direct input into Team Effectiveness Survey Tool
          1. Post the document in a shared folder.
          2. Instruct individuals to select one of the numbered columns and enter their information into tab 2. Data – Effectiveness Answers and tab 3. Data – Team Type Answers.
          3. To protect anonymity and keep results confidential, suggest each person opens document in "Cognito mode."
          4. Hide the Summary and Results tabs to avoid team members previewing them.

      Download the IT Team Effectiveness Survey Results Tool

      Paper-Based Cautions & Considerations

      • Heavily dependent on a trusted third party for genuine results
      • Can be time consuming to enter the results

      Online Direct Cautions & Considerations

      • Ensure that users keep to the same numbered column across both entry tabs
      • Seeing other team members' responses may influence others
      • Least amount of administration

      Phase 2

      Review Results and Action Plan

      Phase 1

      Phase 2

      Phase 3

      1.1 Identify team members
      and behaviors to improve using IDEA Model
      1.2 Determine messaging including follow-up plan
      1.3 Send survey

      1.1 Review results with team
      1.2 Determine IDEA focus area(s)
      1.3 Conduct activity to determine solutions

      1.1 Document outcomes and actions
      1.2 Create team charter
      1.3 Identify metrics to show success
      1.4 Schedule check-in

      This phase will walk you through the following activities:

      • Analyzing and debriefing the results to determine themes and patterns to come to a team consensus on what to focus on.
      • Facilitated activities to drive awareness, build co-created definitions of what an effective team looks like, and identify solutions the team can undertake to be more effective.

      This phase involves the following participants:

      • Leader of the team
      • All team members

      Deliverables:

      • A presentation that communicates the team assessment results
      • A plan for effectively delivering the assessment results

      Phase 2: Build a plan to review results and create an action plan

      Reviewing assessment results and creating an improvement action plan is best accomplished through a team meeting.

      Analyzing and preparing for the team meeting may be done by:

      • The person charged with team effectiveness (i.e. team coach).
      • For teams that are seriously struggling with team effectiveness, the coach should complete this step in its entirety.
      • The team coach and the team lead.
      • Truly effective teams are self-reliant. Begin upskilling team leads by involving team leads from the start.
      1. Analyze team assessment results
      2. Prepare to communicate results to the team
      3. Select team activities that will guide the identification of action items and next steps
      4. Facilitate the team meeting

      2.1 Analyze results

      Health Dials

      1. Once the results are final, review the Health Dials for each of the areas.
        1. For each area of the team's effectiveness
          • Red indicates a threat – this will derail the team and you will require an external person to help facilitate conversations.
            It would be recommended to contact us for additional guidance if this is one of your results.
          • Yellow is a growth opportunity.
          • Green is a strength and pay attention to where the dial is – deep into strength or just past the line?
        2. Think about these questions and record your initial reactions.
          1. What surprises you – either positively or negatively?
          2. What areas are as expected?
          3. What behaviors are demonstrated that support the results?

      Prioritize one to two factors for improvement by selecting those with:

      • The lowest overall score.
      • The highest variance in responses.
      • If psychological safety is low, be sure to prioritize this factor; it is the foundation of any effective team.

      An image of the Health dials for each area.

      2.2 Analyze results

      Alignment of Responses

      1. The alignment of responses area provides you with an overview of the range of responses from the team for each area.
        • The more variety in the bars indicates how differently each person is experiencing the team.
        • The more aligned the bars are the more shared the experiences.

      The flatter the bars are across the top, the more agreement there was. Factors that show significant differences in opinion should be discussed to diagnose what is causing the misalignment within your team.

      1. Recommendation is to look at high scores and the alignment and lower scores and the alignment to determine where you may want to focus.

      The alignment chart below shows varied responses; however, there are two distinct patterns. This will be an important area to review.
      Things to think about:

      • Are there new team members?
      • Has there been a leadership change?
      • Has there been a change that has impacted the team?
      An image showing the alignment of responses for Identity, Decisions; Exchange; and Atmosphere.

      2.3 Analyze results

      Team Characteristics and Stakes

      1. Team Characteristics. Use the Team Type Results tab in the IT Team Effectiveness Assessment Tool to identify how the team characterizes itself along the High-Low Scale. The closer the dark blue bar is to the right or left suggests to which degree the team views the characteristic.
        1. Interdependence highlights the team's view on how interconnected and dependent they are on each other to get work done. Think of examples where they should be sharing or collaborating, and they are not.
        2. Virtual describes the physicality of the team. This area has changed a lot since 2020; however, it's still important to note if the team shares the same understanding of work location. Are they thinking of team members in a different geography or referring to hybrid work?
        3. Decision making describes the scale of one decision maker or many. Where are most decisions made by on your team or who is making them?
        4. Stability refers to the degree to which the team stays the same – no membership change or turnover. It can be defined by length of time the group has been together. Looking at this will help understand alignment results. If alignment is varied, one might expect a less stable team.
      2. Stakes and Pressure
        1. Pressure refers to the conditions in which the team must work. How urgent are requests?
        2. Stakes refers to the degree of impact the work has. Will outputs impact safety, health, or a service?
        3. This category can be reviewed against decision making – high pressure, high stakes environments usually have a high concentration of authority. Low pressure, low stakes decisions can also be made either by one person as there is relatively no impact or with many as you have time to get many perspectives.
        4. This area informs what your decision-making protocols should look like.

      A bar graph for Team Characteristics, and a quadrant analysis for comparing Stakes and Pressure.

      2.4 Prepare for meeting

      1-2 hours

      1. Select a facilitator
        • The right person to facilitate the meeting and present the results is dependent upon the results themselves, the team lead's comfort level, and the root and degree of team dysfunction.
        • Typically, the team lead will facilitate and present the results. However, it will be more appropriate to have a member of the HR team or an external third party facilitate.
      2. Set the agenda (recommended sample to the right) that ensures:
        • Team members reflect on the results and discuss reaction to the results. (E.g. Are they surprised? Why/why not?)
        • Results are clearly understood and accepted by team members before moving on to activities.
        • The aim of the meeting is kept in mind. The purpose of the team meeting is to involve all team members in the creation of an effectiveness improvement plan.
      3. Customize the Facilitation Guide and activities in the Improve IT Team Effectiveness Facilitation Guide. (Activities are aligned with the four factors in the IDEA model.)
        • Identify a clear objective for each activity given the team assessment results. (E.g. What are the areas of improvement? What is the desired outcome of the activity?)
        • Review and select the activities that will best achieve the objectives.
        • Customize and prepare for chosen activities appropriately.
        • Obtain all necessary materials.
        • Practice by anticipating and preparing for questions, objectives, and what you will say and do.

      Facilitation Factors
      Select a third-party facilitator if:

      • The team lead is uncomfortable.
      • The leadership or organization is implicated in the team's dysfunction, a third party can be sought in place of HR.
      • Regardless of who facilitates, it is critical that the team lead understands the process and results and is comfortable answering any questions that arise.

      Agenda

      • Review the IDEA Model.
      • Discuss the assessment results.
      • Invite team members to reflect on the results and discuss reaction to the results.
      • Ensure results are clearly understood and accepted.
      • Examine team challenges and strengths through selected team activities.
      • Create a team charter and effectiveness improvement plan.

      Materials

      • IT Team Effectiveness Activities Facilitation Guide
      • IT Team Effectiveness Survey results

      Participants

      • Leader

      2.5 Run the meeting

      2-3 hours

      Facilitate the team meeting and agree on the team effectiveness improvement plan.

      Work with the team to brainstorm and agree on an action plan of continuous improvements.

      By creating an action plan together with the team, there is greater buy-in and commitment to the activities identified within the action plan.

      Don't forget to include timelines and task owners in the action plan – it isn't complete without them.

      Document final decisions in Info-Tech's Improve IT Team Effectiveness Action Plan Tool.

      Review activity Develop Team Charter in the Improve IT Team Effectiveness Facilitation Guide and conclude the team meeting by creating a team charter. With a team charter, teams can better understand:

      • Team objectives
      • Team membership and roles
      • Team ground rules

      Facilitation Factors

      Encourage and support participation from everyone.

      Be sure no one on the team dismisses anyone's thoughts or opinions – they present the opportunity for further discussion and deeper insight.

      Watch out for anything said or done during the activities that should be discussed in the activity debrief.

      Debrief after each activity, outlining any lessons learned, action items, and next steps.

      Agenda

      • Review the IDEA Model.
      • Discuss the assessment results.
      • Invite team members to reflect on the results and discuss reaction to the results.
      • Ensure results are clearly understood and accepted.
      • Examine team challenges and strengths through selected team activities.
      • Create a team charter and effectiveness improvement plan.

      Materials

      • IT Team Effectiveness Activities Facilitation Guide
      • Whiteboard/flip charts
      • Sticky notes
      • IT Team Effectiveness Survey results

      Participants

      • Leader
      • Team Members
      • Optional – External Facilitator

      Phase 3

      Document and measure

      Phase 1

      Phase 2

      Phase 3

      1.1 Identify team members
      and behaviors to improve using IDEA Model
      1.2 Determine messaging including follow-up plan
      1.3 Send survey

      1.1 Review results with team
      1.2 Determine IDEA focus area(s)
      1.3 Conduct activity to determine solutions

      1.1 Document outcomes and actions
      1.2 Create team charter
      1.3 Identify metrics to show success
      1.4 Schedule check-in

      This phase will walk you through the following activities:
      Building your team charter that will include:

      • Team vision, mission, and goals
      • Roles and responsibilities of each member
      • Decision-making responsibilities and process
      • How information will be shared and by whom
      • Ways to build psychological safety on the team

      This phase involves the following participants:

      • Leader of the team
      • All team members

      Document and agree to regular check-ins to reassess.

      As a team it will be important to drive your brainstormed solutions into an output that is co-created.

      • Agree to what actions can be implemented.
      • Capture agreed-to team goals, roles, responsibilities, and decision process into a team charter. Also include your communication protocol that articulates how information will be shared in future.
      1. Review suggestions and actions
      2. Capture in team charter
      3. Assign metrics to measure success and determine when to review
      4. Complete ongoing check-ins with team through team meeting and plan to reassess if agreed to

      Team Charter

      Never assume everyone "just knows."

      Set clear expectations for the team's interactions and behaviors.

      • Some teams call this a team agreement, team protocol, or ways of working. Determine the naming convention that works best for your team and culture.
      • This type of document saw a renewed popularity during COVID-19 as face-to-face interactions were more difficult, and as teams, news ways to work needed to be discovered, shared, and documented.
      • A co-created team charter is a critical component to onboarding new employees in the hybrid world.

      Info-Tech Insight – State of Hybrid Work in IT

      One contributor to the report shared the effort and intention around maintaining their culture during the pandemic. The team agreement created became a critical tool to enable conversations between leaders and their team – it was not a policy document.

      Team effectiveness is driven through thoughtful planned conversations. And it's a continued conversation.

      A screenshot of the IT Team Charter Template page

      Download the IT Team Charter Template

      Establish Baseline Metrics

      Baseline metrics will be improved through:

      Identify the impact that improved team effectiveness will have on the organization.
      Determine your baseline metrics to assess the success of your team interventions and demonstrate the impact to the rest of the organization using pre-determined goals and metrics.
      Share success stories through:

      • Newsletters or email announcements
      • Team meetings
      • Presentations to business partners or the organization

      Sample effectiveness improvement goal

      Sample Metric

      Increase employee engagement
      Increase overall employee engagement scores in the Employee Engagement survey by 5% by December 31, 2023.

      • Overall employee engagement

      Strengthen manager/employee relationships
      Increase manager driver scores in the Employee Engagement survey by 5% by December 31, 2023.

      • Employee engagement – manager driver
      • Employee engagement – senior leadership driver

      Reduce employee turnover (i.e. increase retention)
      Reduce voluntary turnover by 5% by December 31, 2023.

      • Voluntary turnover rate
      • Turnover by department or manager
      • Cost of turnover

      Increase organizational productivity
      Increase the value added by human capital by 5% by December 31, 2023.

      • Value added by human capital
      • Employee productivity
      • Human capital return on investment
      • Employee engagement

      Reassess team effectiveness

      Reassess and identify trends after they have worked on key focus areas for improvement.

      Track the team's progress by reassessing their effectiveness six to twelve months after the initial assessment.
      Identify if:

      • Team characteristics have changed.
      • Areas of team strengths are still a source of strength.
      • Areas for improvement have, in fact, improved.
      • There are opportunities for further improvement.

      As the team matures, priorities and areas of concern may shift; it is important to regularly reassess team effectiveness to ensure ongoing alignment and suitability.
      Note: It is not always necessary to conduct a full formal assessment; once teams become more effective and self-sufficient, informal check-ins by team leads will be sufficient.

      If you assess team effectiveness for multiple teams, you have the opportunity to identify trends:

      • Are there common challenges within teams?
      • If so, what are they?
      • How comfortable are teams with intervention?
      • How often is outside help required?

      Identifying these trends, initiatives, training, or tactics may be used to improve team effectiveness across the department – or even the organization.

      Teams are ultimately accountable for their own effectiveness.

      As teams mature, the team lead should become less involved in action planning. However, enabling truly effective teams takes significant time and resources from the team lead.

      Use the action plan created and agreed upon during the team meeting to hold teams accountable:

      • Ensure teams follow through on action items.
      • Ensure you are continuously assessing team effectiveness (formally or informally).

      The team coach should have a plan to transition into a supportive role by:

      • Providing teams with the knowledge, resources, and tools required to improve and sustain high effectiveness.
      • Providing team members and leads with a safe, open, and honest environment.
      • Stepping in as an objective third party when required.

      If the team continues to face barriers

      Other important information: If team effectiveness has not significantly improved, other interventions may be required that are beyond the scope of this project.

      The four factors outlined in the IDEA Model of team effectiveness are very important, but they are not the only things that have a positive or negative impact on teams. If attempts to improve the four factors have not resulted in the desired level of team effectiveness, evaluate other barriers:

      For organizational culture, ask if performance and reward programs do the following:

      • Value teamwork alongside individual achievement and competition
      • Provide incentives that promote a focus on individual performance over team performance
      • Reward or promote those who sabotage their teams

      For learning and development, ask:

      • Is team effectiveness included in our manager or leadership training?
      • Do we offer resources to employees seeking to improve their teamwork competencies?

      If an individual team member's or leader's performance is not meeting expectations, potential remedies include a performance improvement plan, reassignment, and termination of employment.

      These kinds of interventions are beyond the control of the team itself. In these cases, we recommend you consult with your HR department; HR professionals can be important advocates because they possess the knowledge, influence, and authority in the company to promote changes that support teamwork.

      Related Info-Tech Research

      Redesign Your IT Department

      • You could have the best IT employees in the world, but if they aren't structured well your organization will still fail in reaching its vision.
      • Increase the effectiveness of IT as a function.
      • Provide employees with clarity in their roles and responsibilities.

      Build an IT Employee Engagement Program

      • With the growing IT job market, turnover is a serious threat to IT's ability to deliver seamless value and continuously drive innovation.
      • Engagement initiatives are often seen as being HR's responsibility; however, IT leadership needs to take accountability for the retention and productivity of their employees in order to drive business value.

      Info-Tech Leadership Programs

      • Development of the leadership mind should never stop. This program will help IT leaders continue to craft their leadership competencies to navigate the ever-changing world in which we operate.
      • Actively delegate responsibilities and opportunities that engage and develop team members to build on current skills and prepare for the future.

      Research Contributors and Experts

      A picture of Carlene McCubbin

      Carlene McCubbin
      Practice Lead
      Info-Tech Research Group

      A picture of Nick Kozlo

      Nick Kozlo
      Senior Research Analyst
      Info-Tech Research Group

      A picture of Heather Leier-Murray

      Heather Leier-Murray
      Senior Research Analyst
      Info-Tech Research Group

      A picture of Stephen O'Conner

      Stephen O'Conner
      Executive Counselor
      Info-Tech Research Group

      A picture of Jane Kouptsova

      Jane Kouptsova
      Research Director
      Info-Tech Research Group

      Dr. Julie D. Judd, Ed.D.
      Chief Technology Officer
      Ventura County Office of Education

      Works Cited

      Aminov, I., A. DeSmet, and G. Jost. "Decision making in the age of urgency." McKinsey. April 2019. Accessed January 2023.
      Duhigg, Charles. "What Google Learned From Its Quest to Build the Perfect Team." The New York Times, 25 Feb. 2016. Accessed January 2023.
      Edmondson, Amy. "Psychological Safety and Learning Behavior in Work Teams." Administrative Science Quarterly, vol. 44, no. 2, June 1999, pp. 350-383.
      Gardner, Kate. "Julie Judd – Ventura County Office of Education." Toggle, 12 Sept. 2022. Accessed January 2023.
      Google People Operations. "Guide: Understand Team Effectiveness." reWork, n.d. Accessed February 2023.
      Harkins, Phil. "10 Leadership Techniques for Building High-Performing Teams." Linkage Inc., 2014. Accessed 10 April 2017.
      Heath, C. and D. Heath. Decision: How to make better choices in life and work. Random House, 2013, ISBN 9780307361141.
      Hill, Jon. "What is an Information Silo and How Can You Avoid It." Bloomfire, 23 March 2022. Accessed January 2023.
      "IT Team Management Software for Enhanced Productivity." Freshworks, n.d. Accessed January 2023.
      Jackson, Brian. "2022 Tech Trends." Info-Tech Research Group, 2022. Accessed December 2022.
      Kahneman, Daniel. Thinking fast and slow. Farrar, Straus and Giroux. 2011.
      Kouptsova, J., and A. Mathieson. "State of Hybrid Work in IT." Info-Tech Research Group, 2023. Accessed January 2023.
      Mayfield, Clifton, et al. "Psychological Collectivism and Team Effectiveness: Moderating Effects of Trust and Psychological Safety." Journal of Organizational Culture, Communications and Conflict, vol. 20, no. 1, Jan. 2016, pp. 78-94.
      Rock, David. "SCARF: A Brain-Based Model for Collaborating With and Influencing Others." NeuroLeadership Journal, 2008. Web.
      "The State of High Performing Teams in Tech Hypercontext." Hypercontext. 2022. Accessed November 2022.
      Weick, Carl, and Kathleen Sutcliff. Managing the unexpected. John Wiley & Sons, 2007.
      "Workplace Conflict Statistics: How we approach conflict at work." The Niagara Institute, August 2022. Accessed December 2022.

      Build a Data Warehouse

      • Buy Link or Shortcode: {j2store}200|cart{/j2store}
      • member rating overall impact: 8.7/10 Overall Impact
      • member rating average dollars saved: $94,499 Average $ Saved
      • member rating average days saved: 30 Average Days Saved
      • Parent Category Name: Big Data
      • Parent Category Link: /big-data
      • Relational data warehouses, although reliable, centralized repositories for corporate data, were not built to handle the speed and volume of data and analytics today.
      • IT is under immense pressure from business units to provide technology that will yield greater agility and insight.
      • While some organizations are benefitting from modernization technologies, the majority of IT departments are unfamiliar with the technologies and have not yet defined clear use cases.

      Our Advice

      Critical Insight

      • The vast majority of your corporate data is not being properly leveraged. Modernize the data warehouse to get value from the 80% of unstructured data that goes unused.
      • Avoid rip and replace. Develop a future state that complements your existing data warehouse with emerging technologies.
      • Be flexible in your roadmap. Create an implementation roadmap that’s incremental and adapts to changing business priorities.

      Impact and Result

      • Establish both the business and IT perspectives of today’s data warehouse environment.
      • Explore the art-of-the-possible. Don’t get stuck trying to gather technical requirements from business users who don’t know what they don’t know. Use Info-Tech’s interview guide to discuss the pains of the current environment, and more importantly, where stakeholders want to be in the future.
      • Build an internal knowledgebase with respect to emerging technologies. The technology landscape is constantly shifting and often difficult for IT staff to keep track of. Use Info-Tech’s Data Warehouse Modernization Technology Education Deck to ensure that IT is able to appropriately match the right tools to the business’ use cases.
      • Create a compelling business case to secure investment and support.

      Build a Data Warehouse Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should be looking to modernize the relational data warehouse, review Info-Tech’s framework for identifying modernization opportunities, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Assess the current data warehouse environment

      Review the business’ perception and architecture of the current data warehouse environment.

      • Drive Business Innovation With a Modernized Data Warehouse Environment – Phase 1: Assess the Current Data Warehouse Environment
      • Data Warehouse Maturity Assessment Tool

      2. Define modernization drivers

      Collaborate with business users to identify the strongest motivations for data warehouse modernization.

      • Drive Business Innovation With a Modernized Data Warehouse Environment – Phase 2: Define Modernization Drivers
      • Data Warehouse Modernization Stakeholder Interview Guide
      • Data Warehouse Modernization Technology Education Deck
      • Data Warehouse Modernization Initiative Building Tool

      3. Create the modernization future state

      Combine business ideas with modernization initiatives and create a roadmap.

      • Drive Business Innovation With a Modernized Data Warehouse Environment – Phase 3: Create the Modernization Future State
      • Data Warehouse Modernization Technology Architectural Template
      • Data Warehouse Modernization Deployment Plan
      [infographic]

      Workshop: Build a Data Warehouse

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Assess the Current Data Warehouse Environment

      The Purpose

      Discuss the general project overview for data warehouse modernization.

      Establish the business and IT perspectives of the current state.

      Key Benefits Achieved

      Holistic understanding of the current data warehouse.

      Business user engagement from the start of the project.

      Activities

      1.1 Review data warehouse project history.

      1.2 Evaluate data warehouse maturity.

      1.3 Draw architecture diagrams.

      1.4 Review supporting data management practices.

      Outputs

      Data warehouse maturity assessment

      Data architecture diagrams

      2 Explore Business Opportunities

      The Purpose

      Conduct a user workshop session to elicit the most pressing needs of business stakeholders.

      Key Benefits Achieved

      Modernization technology selection is directly informed by business drivers.

      In-depth IT understanding of the business pains and opportunities.

      Activities

      2.1 Review general trends and drivers in your industry.

      2.2 Identify primary business frustrations, opportunities, and risks.

      2.3 Identify business processes to target for modernization.

      2.4 Capture business ideas for the future state.

      Outputs

      Business ideas for modernization

      Defined strategic direction for data warehouse modernization

      3 Review the Technology Landscape

      The Purpose

      Educate IT staff on the most common technologies for data warehouse modernization.

      Key Benefits Achieved

      Improved ability for IT to match technology with business ideas.

      Activities

      3.1 Appoint Modernization Advisors.

      3.2 Hold an open education and discussion forum for modernization technologies.

      Outputs

      Modernization Advisors identified

      Modernization technology education deck

      4 Define Modernization Solutions

      The Purpose

      Consolidate business ideas into modernization initiatives.

      Key Benefits Achieved

      Refinement of the strategic direction for data warehouse modernization.

      Activities

      4.1 Match business ideas to technology solutions.

      4.2 Group similar ideas to create modernization initiatives.

      4.3 Create future-state architecture diagrams.

      Outputs

      Identified strategic direction for data warehouse modernization

      Defined modernization initiatives

      Future-state architecture for data warehouse

      5 Establish a Modernization Roadmap

      The Purpose

      Validate and build out initiatives with business users.

      Define benefits and costs to establish ROI.

      Identify enablers and barriers to modernization.

      Key Benefits Achieved

      Completion of materials for a compelling business case and roadmap.

      Activities

      5.1 Validate use cases with business users.

      5.2 Define initiative benefits.

      5.3 Identify enablers and barriers to modernization.

      5.4 Define preliminary activities for initiatives.

      5.5 Evaluate initiative costs.

      5.6 Determine overall ROI.

      Outputs

      Validated modernization initiatives

      Data warehouse modernization roadmap

      Implement Your Negotiation Strategy More Effectively

      • Buy Link or Shortcode: {j2store}225|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Vendor Management
      • Parent Category Link: /vendor-management
      • Forty-eight percent of CIOs believe their budgets are inadequate.
      • CIOs and IT departments are getting more involved with negotiations to reduce costs and risk.
      • Not all negotiators are created equal, and the gap between a skilled negotiator and an average negotiator is not always easy to identify objectively.
      • Skilled negotiators are in short supply.

      Our Advice

      Critical Insight

      • Preparation is critical for the success of your negotiation, but you cannot prepare for every eventuality.
      • Communication is the heart and soul of negotiations, but what is being “said” is only part of the picture.
      • Skilled negotiators separate themselves based on skillsets, and outcomes alone may not provide an accurate assessment of a negotiator.

      Impact and Result

      Addressing and managing critical negotiation elements helps:

      • Improve negotiation skills.
      • Implement your negotiation strategy more effectively.
      • Improve negotiation results.

      Implement Your Negotiation Strategy More Effectively Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should create and follow a scalable process for preparing to negotiate with vendors, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. During

      Throughout this phase, ten essential negotiation elements are identified and reviewed.

      • Implement Your Negotiation Strategy More Effectively – Phase 1: During
      • During Negotiations Tool
      [infographic]

      Workshop: Implement Your Negotiation Strategy More Effectively

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 12 Steps to Better Negotiation Preparation

      The Purpose

      Improve negotiation skills and outcomes.

      Understand how to use the Info-Tech During Negotiations Tool.

      Key Benefits Achieved

      A better understanding of the subtleties of the negotiation process and an identification of where the negotiation strategy can go awry.

      The During Negotiation Tool will be reviewed and configured for the customer’s environment (as applicable).

      Activities

      1.1 Manage six key items during the negotiation process.

      1.2 Set the right tone and environment for the negotiation.

      1.3 Focus on improving three categories of intangibles.

      1.4 Improve communication skills to improve negotiation skills.

      1.5 Customize your negotiation approach to interact with different personality traits and styles.

      1.6 Maximize the value of your discussions by focusing on seven components.

      1.7 Understand the value of impasses and deadlocks and how to work through them.

      1.8 Use concessions as part of your negotiation strategy.

      1.9 Identify and defeat common vendor negotiation ploys.

      1.10 Review progress and determine next steps.

      Outputs

      Sample negotiation ground rules

      Sample vendor negotiation ploys

      Sample discussion questions and evaluation matrix

      Re-Envision Enterprise Printing

      • Buy Link or Shortcode: {j2store}165|cart{/j2store}
      • member rating overall impact: 8.0/10 Overall Impact
      • member rating average dollars saved: $9,000 Average $ Saved
      • member rating average days saved: 2 Average Days Saved
      • Parent Category Name: End-User Computing Devices
      • Parent Category Link: /end-user-computing-devices
      • Enterprises may be overspending on printing, but this spend is often unknown and untracked.
      • You are locked into a traditional printer lease and outdated document management practices, hampering digital transformation.

      Our Advice

      Critical Insight

      Don’t just settle for printer consolidation: Seek to eliminate print and enlist your managed print services vendor to help you achieve that goal.

      Impact and Result

      • Identify reduction opportunities via a thorough inventory and requirements-gathering process, and educate others on the financial and non-financial benefits. Enforce reduced printing through policies.
      • Change your printing financial model to print as a service by building an RFP and scoring tool for managed print services that makes the vendor a partner in continuous innovation.
      • Leverage durable print management software to achieve vendor-agnostic governance and visibility.

      Re-Envision Enterprise Printing Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Re-Envision Enterprise Printing – A step-by-step document to help plan and execute a printer reduction project.

      This storyboard will help you plan the project, assess your current state and requirements, build a managed print services RFP and scoring process, and build continuous improvement of business processes into your operations.

      • Re-Envision Enterprise Printing – Phases 1-3

      2. Planning tools

      Use these templates and tools to plan the printer reduction project, document your inventory, assess current printer usage, and gather information on current and future requirements.

      • Enterprise Printing Project Charter
      • Enterprise Printing Roles and Responsibilities RACI Guide
      • Printer Reduction Tool
      • End-User Print Requirements Survey

      3. RFP tools

      Use these templates and tools to create an RFP for managed print services that can easily score and compare vendors.

      • Managed Print Services Vendor Assessment Questions
      • Managed Print Services RFP Vendor Proposal Scoring Tool
      • Managed Print Services RFP Template

      4. Printer policy

      Update the printer policy to express the new focus on reducing unsupported printer use.

      • Printer Policy Template

      Infographic

      Further reading

      Re-Envision Enterprise Printing

      Don't settle for printer consolidation; seek the elimination of print

      Analystperspective

      You're likely not in the printing business.
      Prepare your organization for the future by reducing print.

      Initiatives to reduce printers are often met with end-user resistance. Don't focus on the idea of taking something away from end users. Instead, focus on how print reduction fits into larger goals of business process improvement, and on opportunities to turn the vendor into a partner who drives business process improvement through ongoing innovation and print reduction.

      What are your true print use cases? Except in some legitimate use cases, printing often introduces friction and does not lead to efficiencies. Companies investing in digital transformation and document management initiatives must take a hard look at business processes still reliant on hard copies. Assess your current state to identify what the current print volume and costs are and where there are opportunities to consolidate and reduce.

      Change your financial model. The managed print services industry allows you to use a pay-as-you-go approach and right-size your print spend to the organization's needs. However, in order to do printing-as-a-service right, you will need to develop a good RFP and RFP evaluation process to make sure your needs are covered by the vendor, while also baking in assurances the vendor will partner with you for continuous print reduction.

      This is a picture of Emily Sugerman

      Emily Sugerman
      Research Analyst, Infrastructure & Operations
      Info-Tech Research Group

      Darin Stahl
      Principal Research Advisor, Infrastructure & Operations
      Info-Tech Research Group

      Executive summary

      Your Challenge

      IT directors and business operations managers face several challenges:

      • Too many known unknowns: Enterprises may be overspending on printing, but this spend is often unknown and untracked.
      • Opportunity costs: By locking into conventional printer leases and outdated document management, you are locking yourself out of the opportunity to improve business processes.

      Common Obstacles

      Printer reduction initiatives are stymied by:

      • End-user resistance: Though sometimes the use of paper remains necessary, end users often cling to paper processes out of concern about change.
      • Lack of governance: You lack insight into legitimate print use cases and lack full control over procurement of devices and consumables.
      • Overly generic RFP: Print requirements are not tailored to your organization, and your managed print services RFP does not ask enough of the vendor.

      Info-Tech's Approach

      Follow these steps to excise superfluous, costly printing:

      • Identify reduction opportunities via a thorough inventory and requirements-gathering process, and educate others on the financial and non-financial benefits. Enforce reduced printing through policies.
      • Change your printing financial model to print-as-a-service by building an RFP and scoring tool for managed print services that makes the vendor a partner in continuous innovation.
      • Leverage durable print management software to achieve vendor-agnostic governance and visibility.

      Info-Tech Insight

      Don't settle for printer consolidation: seek to eliminate print and enlist your managed print services vendor to help you achieve that goal.

      Your challenge

      This research is designed to help organizations that aim to reduce printing long term

      • Finally understand aggregate printing costs: Not surprisingly, printing has become a large hidden expense in IT. Enterprises may be overspending on printing, but this spend is often unknown and untracked. Printer consumables are purchased independently by each department, non-networked desktop printers are everywhere, and everyone seems to be printing in color.
      • Walk the walk when it comes to digital transformation: Outdated document management practices that rely on unnecessary printing are not the foundation upon which the organization can improve business processes.
      • Get out of the printing business: Hire a managed print provider and manage that vendor well.

      "There will be neither a V-shaped nor U-shaped recovery in demand for printing paper . . . We are braced for a long L-shaped decline."
      –Toru Nozawa, President, Nippon Paper Industries (qtd. in Nikkei Asia, 2020).

      Weight of paper and paperboard generated in the U.S.*

      This is an image of a graph plotting the total weight of paper and paperboard generated in the US, bu thousands of US tons.

      *Comprises nondurable goods (including office paper), containers, and packaging.

      **2020 data not available.

      Source: EPA, 2020.

      Common obstacles

      These barriers make this challenge difficult to address for many organizations:

      • Cost-saving opportunities are unclear: In most cases, nobody is accountable for controlling printing costs, so there's a lack of incentive to do so.
      • End-user attachment to paper-based processes: For end users who have been relying on paper processes, switching to a new way of working can feel like a big ask, particularly if an optimized alternative has not been provided and socialized.
      • Legitimate print use cases are undefined: Print does still have a role in some business processes (e.g. for regulatory reasons). However, these business processes have not been analyzed to determine which print use cases are still legitimate. The WFH experience during the COVID-19 pandemic demonstrated that many workflows that previously incorporated printing could be digitized. Indeed, the overall attachment to office paper is declining (see chart).
      • Immature RFP and RFP scoring methods: Outsourcing print to a managed service provider necessitates careful attention to RFP building and scoring. If your print requirements are not properly tailored to your organization and your managed print services RFP does not ask enough of the vendor, it will be harder to hold your vendor to account.

      How important is paper in your office?

      87% 77%

      Quocirca, a printer industry market research firm, found that the number of organizations for whom paper is "fairly or very important to their business" has dropped 10 percentage points between 2019 and 2021.

      Source: Quocirca, 2021.

      Info-Tech's approach

      Permanently change your company's print culture

      1. Plan your Project
      • Create your project charter, investigate end user printer behavior and reduction opportunities, gather requirements and calculate printer costs
    • Find the right managed print vendor
      • Protect yourself by building the right requirements into your RFP, evaluating candidates and negotiating from a strong position
    • Implement the new printer strategy
      • Identify printers to consolidate and eliminate, install them, and communicate updated printer policy
    • Operate
      • Track the usage metrics, service requests, and printing trends, support the printers and educate users to print wisely and sparingly
    • The Info-Tech difference:

      1. Use Info-Tech's tracking tools to finally track data on printer inventory and usage.
      2. Get to an RFP for managed print services faster through Info-Tech's requirement selection activity, and use Info-Tech's scoring tool template to more quickly compare candidates and identify frontrunners and knockouts.
      3. Use Info-Tech's guidance on print management software to decouple your need to govern the fleet from any specific vendor.

      Info-Tech's methodology for Re-Envision Enterprise Printing

      1. Strategy & planning 2. Vendor selection, evaluation, acquisition 3. Implementation & operation
      Phase steps
      1. Create project charter and assign roles
      2. Assess current state of enterprise print environments
      3. Gather current and future printer requirements
      1. Understand managed print services model
      2. Create RFP documents and score vendors
      3. Understand continuous innovation & print management software
      1. Modify printer policies
      2. Measure project success
      3. Training & adoption
      4. Plan persuasive communication
      5. Prepare for continuous improvement
      Phase outcomes
      • Documentation of project roles, scope, objectives, success metrics
      • Accurate printer inventory
      • Documentation of requirements based on end-user feedback, existing usage, and future goals
      • Finalized requirements
      • Completed RFP and vendor scoring tool
      • Managed print vendor selected, if necessary
      • Updated printer policies that reinforce print reduction focus
      • Assessment of project success

      Insight summary

      Keep an eye on the long-term goal of eliminating print

      Don't settle for printer consolidation: seek to eliminate print and enlist your managed print services vendor to help you achieve that goal.

      Persuading leaders is key

      Good metrics and visible improvement are important to strengthen executive support for a long-term printer reduction strategy.

      Tie printer reduction into business process improvement

      Achieve long-lasting reductions in print through document management and improved workflow processes.

      Maintain clarity on what types of printer use are and aren't supported by IT

      Modifying and enforcing printing policies can help reduce use of printers.

      Print management software allows for vendor-agnostic continuity

      Print management software should be vendor-agnostic and allow you to manage devices even if you change vendors or print services.

      Secure a better financial model from the provider

      Simply changing your managed print services pay model to "pay-per-click" can result in large cost savings.

      Blueprint deliverables

      Key deliverable:

      Managed Print Services RFP

      This blueprint's key deliverable is a completed RFP for enterprise managed print services, which feeds into a scoring tool that accelerates the requirements selection and vendor evaluation process.

      Managed Print Services Vendor Assessment Questions

      This is a screenshot from the Managed Print Services Vendor Assessment Questions

      Managed Print Services RFP Template

      This is a screenshot from the Managed Print Services RFP Template

      Managed Print Services RFP Vendor Proposal Scoring Tool

      This is a screenshot from the Managed Print Services RFP Vendor Proposal Scoring Tool

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

      Enterprise Printing Project Charter

      This is a screenshot from the Enterprise Printing Project Charter

      Document the parameters of the print reduction project, your goals, desired business benefits, metrics.

      Enterprise Printing Roles and Responsibilities RACI Guide

      This is a screenshot from the Enterprise Printing Project Charter

      Assign key tasks for the project across strategy & planning, vendor selection, implementation, and operation.

      Printer Policy

      This is a screenshot from the Printer Policy

      Start with a policy template that emphasizes reduction in print usage and adjust as needed for your organization.

      Printer Reduction Tool

      This is a screenshot from the Printer Reduction Tool

      Track the printer inventory and calculate total printing costs.

      End-User Print Requirements Survey

      This is a screenshot from the End-User Print Requirements Survey

      Base your requirements in end user needs and feedback.

      Blueprint benefits

      IT benefits

      • Make the project charter for printer reduction and estimate cost savings
      • Determine your organization's current printing costs, usage, and capabilities
      • Define your organization's printing requirements and select a solution
      • Develop a printer policy and implement the policy

      Business benefits

      • Understand the challenges involved in reducing printers
      • Understand the potential of this initiative to reduce costs
      • Accelerate existing plans for modernization of paper-based business processes by reducing printer usage
      • Contribute to organizational environmental sustainability targets

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful."

      Guided Implementation

      "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track."

      Workshop

      "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place."

      Consulting

      "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks used throughout all four options

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1 Phase 2 Phase 3

      Call #1: Scope requirements, objectives, and your specific challenges.

      Call #4: Review requirements.
      Weigh the benefits of managed print services.

      Call #6: Measure project success.

      Call #2: Review your printer inventory.
      Understand your current printing costs and usage.

      Call #5: Review completed scoring tool and RFP.

      Call #5: Review vendor responses to RFP.

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is 8 to 12 calls over the course of 4 to 6 months.

      Phase 1

      Strategy and Planning

      Strategy & planning

      Vendor selection, evaluation, acquisition

      Implementation & Operation

      1.1 Create project charter and assign roles

      1.2 Assess current state

      1.3 Gather requirements

      2.1 Understand managed print services model

      2.2 Create RFP materials

      2.3 Leverage print management software

      3.1 Modify printer policies

      3.2 Measure project success

      3.3 Training & adoption

      3.4 Plan communication

      3.5 Prepare for continuous improvement

      Re-Envision Enterprise Printing

      • This phase will walk you through the following activities:
      • Create a list of enterprise print roles and responsibilities
      • Create project charter
      • Inventory printer fleet and calculate printing costs
      • Examine current printing behavior and identify candidates for device elimination
      • Gather requirements, including through end user survey

      This phase involves the following participants:

      • IT director/CIO
      • Business operations manager
      • Project manager

      Step 1.1

      Create project charter and assign roles

      Outcomes of this step

      Completed Project Charter with RACI chart

      Phase 1: Strategy and Planning

      • Step 1.1 Create project charter and assign roles
      • Step 1.2 Assess current state
      • Step 1.3 Gather requirements

      This step involves the following participants:

      • IT director/CIO
      • Business operations manager
      • Project manager

      Activities in this step

      • Create a list of enterprise print roles and responsibilities
      • Create project charter

      1.1 Create project charter

      Use the project charter to clearly define the scope and avoid scope creep

      Identify project purpose

      • Why is the organization taking on this project? What are you trying to achieve?
      • What is the important background you need to document? How old is the fleet? What kinds of printer complaints do you get? What percentage of the IT budget does printing occupy?
      • What specific goals should this project achieve? What measurable financial and non-financial benefits do these goals achieve?

      Identify project scope

      • What functional requirements do you have?
      • What outputs are expected?
      • What constraints will affect this project?
      • What is out of scope for this project?

      What are the main roles and responsibilities?

      • Who is doing what for this project?

      How will you measure success?

      • What are the project's success metrics and KPIs?

      Enterprise Printing Project Charter

      This is a screenshot from the Enterprise Printing Project Charter

      Anticipate stakeholder resistance

      Getting management buy-in for printer reduction is often one of the biggest challenges of the project.

      Challenge Resolution
      Printer reduction is not typically high on the priority list of strategic IT initiatives. It is often a project that regularly gets deferred. The lack of an aggregate view of the total cost of printing in the environment could be one root cause, and what can't be measured usually isn't being managed. Educate and communicate the benefits of printer reduction to executives. In particular, spend time getting buy-in from the COO and/or CFO. Use Info-Tech's Printer Reduction Tool to show executives the waste that is currently being generated.
      Printers are a sensitive and therefore unpopular topic of discussion. Executives often see a trade-off: cost savings versus end-user satisfaction. Make a strong financial and non-financial case for the project. Show examples of other organizations that have successfully consolidated their printers.

      Info-Tech Insight

      If printer reduction is not driven and enforced from the top down, employees will find ways to work around your policies and changes. Do not attempt to undertake printer reduction initiatives without alerting executives. Ensure visible executive support to achieve higher cost savings.

      Align the printer reduction project to org goals to achieve buy-in

      A successful IT project demonstrates clear connections to business goals

      Which business and organizational goals and drivers are supported by IT's intention to transform its printing ecosystem? For example,

      Legislation: In 2009, the Washington House of Representatives passed a bill requiring state agencies to implement a plan to reduce paper consumption by 30% (State of Washington, 2009). The University of Washington cites this directive as one of the drivers for their plans to switch fully to electronic records by 2022 (University of Washington, n.d.).

      Health care modernization: Implementing electronic health records; reducing paper charts.

      Supply chain risk reduction: In 2021, an Ontario district school board experienced photocopier toner shortages and were forced to request schools to reduce printing and photocopying: "We have recommended to all locations that the use of printing be minimized as much as possible and priority given to the printing of sensitive and confidential documentation" (CBC, 2021).

      Identify overall organizational goals in the following places:

      • Company mission statements
      • Corporate website
      • Business strategy documents
      • Other IT strategy documents
      • Executives

      Document financial and non-financial benefits

      Financial benefits: Printer reduction can reduce your printing costs and improve printing capabilities.

      • Printer reduction creates a controlled print environment; poorly controlled print environments breed unnecessary costs.
      • Cost savings can be realized through:
        • Elimination of cost-efficient inkjet desktop printers.
        • Elimination of high-cost, inefficient, or underutilized printers.
        • Sharing of workshop printers between an optimal number of end users.
        • Replacing separate printers, scanners, copiers, and fax machines with. multi-function devices.
      • Cost savings can be achieved through a move to managed print services, if you negotiate the contract well and manage the vendor properly. The University of Washington estimated a 20-25% cost reduction under a managed print services model compared to the existing lease (University of Washington, "What is MPS").

      Non-financial benefits: Although the main motivation behind printer reduction is usually cost savings, there are also non-financial benefits to the project.

      • Printer reduction decreases physical space required for printers
      • Printer reduction meets employee and client environmental demands
        • Printer reduction can reduce the electricity and consumables used
        • Reduction in consumables means reduced hazardous waste from consumables and devices
      • Printer reduction can result in better printing capabilities
        • Moving to a managed print services model can provide you with better printing capabilities with higher availability

      Assign responsibility to track print device costs to IT

      Problem:
      Managers in many organizations wrongly assume that since IT manages the printer devices, they also already manage costs.

      However, end users typically order printer devices and supplies through the supplies/facilities department, bypassing any budget approval process, or through IT, which does not have any authority or incentive to restrict requests (when they're not measured against the controlling of printer costs).

      Organization-wide printer usage policies are rarely enforced with any strictness.

      Without systematic policy enforcement, end-user print behavior becomes frivolous and generates massive printing costs.

      Solution:
      Recommend all print device costs be allocated to IT.

      • Aggregate responsibility: Recommend that all printer costs be aggregated under IT's budget and tracked by IT staff.
      • Assign accountability: Although supplies may continually be procured by the organization's supplies/facilities department, IT should track monthly usage and costs by department.
      • Enforce policy: Empower IT with the ability to enforce a strict procurement policy that ensures all devices in the print environment are approved models under IT's control. This eliminates having unknown devices in the printer fleet and allows for economies of scale to be realized from purchasing standardized printing supplies.
      • Track metrics: IT should establish metrics to measure and control each department's printer usage and flat departments that exceed their acceptable usage amounts.

      Assign accountability for the initiative

      Someone needs to have accountability for both the printer reduction tasks and the ongoing operation tasks, or the initiative will quickly lose momentum.

      Customize Info-Tech's Enterprise Printing Roles and Responsibilities RACI Guide RACI chart to designate project roles and responsibilities to participants both inside and outside IT.

      These tasks fall under the categories of:

      • Strategy and planning
      • Vendor selection, evaluation, and acquisition
      • Implementation
      • Operate

      Assign a RACI: Remember the meaning of the different roles

      • Responsible (does the work on a day-to-day basis)
      • Accountable (reviews, signs off on, and is held accountable for outcomes)
      • Consulted (input is sought to feed into decision making)
      • Informed (is given notification of outcomes)

      As a best practice, no more than one person should be responsible or accountable for any given process. The same person can be both responsible and accountable for a given process, or it could be two different people.

      Avoid making someone accountable for a process if they do not have full visibility into the process for appropriate oversight, or do not have time to give the process sufficient attention.

      The Enterprise Printing Roles and Responsibilities RACI Guide can be used to organize and manage these tasks.

      This is a screenshot from the Enterprise Printing Roles and Responsibilities RACI Guide

      Define metrics to measure success

      Track your project success by developing and tracking success metrics

      Ensure your metrics relate both to business value and customer satisfaction. "Reduction of print" is a business metric, not an experience metric.

      Frame metrics around experience level agreements (XLAs) and experience level objectives (XLOs): What are the outcomes the customer wants to achieve and the benefits they want to achieve? Tie the net promoter score into the reporting from the IT service management system, since SLAs are still needed to tactically manage the achievement of the XLOs.

      Use the Metrics Development Workbook from Info-Tech's Develop Meaningful Service Metrics to define:

      • Relevant stakeholders
      • Their goals and pain points
      • The success criteria that must be met to achieve these goals
      • The key indicators that must be measured to achieve these goals from an IT perspective
      • What the appropriate IT metrics are, based on all of the above

      Metrics could include

      • User satisfaction
      • Print services net promoter model
      • Total printing costs
      • Printer availability (uptime)
      • Printer reliability (mean time between failures)
      • Total number of reported incidents
      • Mean time for vendor to respond and repair

      Info-Tech Insight:

      Good metrics and visible improvement are important to strengthen executive support for a long-term printer reduction strategy.

      Step 1.2

      Assess current state

      Outcomes of this step

      • Aggregate view of your printer usage and costs

      Strategy and Planning

      This step involves the following participants:

      • IT director/CIO
      • Business operations manager
      • Project manager

      Activities in this step

      • 1.2. Inventory your printer fleet: Office walk-around
      • 1.2 Inventory your printer fleet: Collect purchase receipts/statements/service records
      • 1.3 Calculate printing costs

      Create an aggregate view of your printer usage and costs

      Problem: Lack of visibility

      • Most organizations are unaware of the savings potential in reducing print due to a lack of data.
      • Additionally, organizations may have inappropriately sized devices for their workloads.
      • Often, nobody is responsible for managing the printers collectively, resulting in a lack of visibility into printing activity. Without this visibility, it is difficult to muster executive commitment and support for printer reduction efforts.
      • The first step to eliminating your printers is to inventory all the printers in the organization and look at an aggregate view of the costs. Without understanding the cost saving potential, management will likely continue to avoid printer changes due to the idea's unpopularity with end users.
      • Valid use cases for printers will likely still remain, but these use cases should be based on a requirements analysis.
      This is a screenshot from the Printer Reduction Tool. It includes the Printer Inventory, and a table with the following column headings: Device Type; Specific Device; Networked; Manufacturer; Model; Serial #; Office Location; Device Owner; # users Supported; Monthly Duty; Page Count to; Device Age; Remaining Useful; # Pages printer/month; % Utilization

      Create visibility through by following these steps:

      1. Office walk-around: Most organizations have no idea how many printers they have until they walk around the office and physically count them. This is especially true in cases where management is allowed to purchase personal printers and keep them at their desks. An office walk-around is often necessary to accurately capture all the printers in your inventory.
      2. Collect purchase receipts/statements/service records: Double-check your printer inventory by referring to purchase receipts, statements, and service records.
      3. Identify other sources of costs: Printer purchases only make up a small fraction of total printing costs. Operating costs typically account for 95% of total printer costs. Make sure to factor in paper, ink/toner, electricity, and maintenance costs.

      1.2.1 Inventory your printer fleet: part 1

      Office walk-around

      1. Methodically walk around the office and determine the following for each printer:
        • Device type
        • Make, model, serial number
        • Location
        • Number of users supported
        • Device owner
        • Type of users supported (department, employee position)
      2. Record printer details in Tab 1 of Info-Tech's Printer Reduction Tool. Collaborate with the accounting or purchasing department to determine the following for each printer recorded:
        • Purchase price/date
        • Monthly duty cycle
        • Estimated remaining useful life
        • Page count to date

      Input

      Output
      • Existing inventory lists
      • Visual observation
      • Inventory of office printers, including their printer details

      Materials

      Participants

      • Notepad
      • Pen
      • Printer Reduction Tool
      • IT director
      • IT staff

      Download the Printer Reduction Tool

      1.2.2 Inventory your printer fleet:
      part 2

      Collect purchase receipts/statements/service records

      1. Ask your purchasing manager for purchase receipts, statements, and service records relating to printing.
      2. For documents found, match the printer with your physical inventory. Add any printers found that were not captured in the physical inventory count. Record the following:
        1. Device type
        2. Make, model, serial number
        3. Location
        4. Number of users supported
        5. Device owner
        6. Type of users supported (department, employee position)
      3. 3. Collaborate with the accounting or purchasing department to determine the following for each printer recorded:
        1. Purchase price/date
        2. Monthly duty cycle
        3. Estimated remaining useful life
        4. Page count to date
      4. Enter the data in Tab 1 of the Printer Reduction Tool

      Input

      Output
      • Purchase receipts
      • Statements
      • Service records
      • Printer inventory cross-checked with paperwork

      Materials

      Participants

      • Printer inventory from previous activity
      • IT director
      • IT staff
      • Purchasing manager

      Download the Printer Reduction Tool

      1.2.3 Calculate your printing costs

      Collect purchase receipts/statements/service records

      • Collect invoices, receipts, and service records to sum up the costs of paper, ink or toner, and maintenance for each machine. Estimate electricity costs.
      • Record your costs in Tab 2 of the Printer Reduction Tool.
      • Review the costs per page and per user to look for particularly expensive printers and understand the main drivers of the cost.
      • Review your average monthly cost and annual cost per user. Do these costs surprise you?

      Input

      Output
      • Invoices, receipts, service records for
      • Cost per page and user
      • Average monthly and annual cost

      Materials

      Participants

      • Printer Reduction Tool
      • IT director
      • IT staff

      Step 1.3

      Gather printing requirements

      Outcomes of this step

      • Understanding of the organization's current printing behavior and habits
      • Identification of how industry context and digitization of business processes have impacted current and future requirements

      This step involves the following participants:

      • IT director
      • IT staff
      • Rest of organization

      Activities in this step

      • Examine current printing behavior and habits
      • Administer end-user survey
      • Identify current requirements
      • Identify future requirements

      Requirements Gathering Overview

      1. Identify opportunities to go paperless
        • Determine where business process automation is occurring
        • Align with environmental and sustainability campaigns
      2. Identify current requirements
        • Review the types of document being printed and the corresponding features needed
        • Administer end-user survey to understand user needs and current printer performance
      3. Identify future requirements
      • Identify future requirements to avoid prematurely refreshing your printer fleet
    • Examine industry-specific/ workflow printing
      • Some industries have specific printing requirements such as barcode printing accuracy. Examine your industry-specific printing requirements
    • Stop: Do not click "Print"

      The most effective way to achieve durable printing cost reduction is simply to print less.

      • Consolidating devices and removing cost-inefficient individual printers is a good first step to yielding savings.
      • However, more sustainable success is achieved by working with the printer vendor(s) and the business on continuous innovation via proposals and initiatives that combine hardware, software, and services.
      • Sustained print reduction depends on separate but related business process automation and digital innovation initiatives.

      Info-Tech Insight:

      Achieve long-lasting reductions in print through document management and improved workflow processes.

      Leverage Info-Tech research to support your business' digital transformation

      This is an image of the title page from Info-Tech's Define your Digital Business Strategy blueprint.

      Define how changes to enterprise printing fit into digital transformation plans

      Identify opportunities to go paperless

      The "paperless office" has been discussed since the 1970s. The IT director alone does not have authority to change business processes. Ensure the print reduction effort is tied to other strategies and initiatives around digital transformation. Working on analog pieces of paper is not digital and may be eroding digital transformation process.

      Leverage Info-Tech's Assert IT's Relevance During Digital Transformations to remind others that modernization of the enterprise print environment belongs to the discussion around increasing digitized support capabilities.

      1. Digital Marketing

      2. Digital Channels

      3. Digitized Support Capabilities

      4. Digitally Enabled Products

      5. Business Model Innovation

      Manage Websites

      E-Channel Operations

      Workforce Management

      Product Design

      Innovation Lab Management

      Brand Management

      Product Inventory Management

      Digital Workplace Management

      Portfolio Product Administration

      Data Sandbox Management

      SEO

      Interactive Help

      Document Management

      Product Performance Measurement

      Innovation Compensation Management

      Campaign Execution

      Party Authentication

      Eliminate business process friction caused by print

      Analyze workflows for where they are still using paper. Ask probing questions about where paper still adds value and where the business process is a candidate for paperless digital transformation

      • Is this piece of paper only being used to transfer information from one application to another?
      • What kind of digitalization efforts have happened in the business as a result of the COVID-19 pandemic? Which workflows have digitized on their own?
      • Where has e-signature been adopted?
      • Is this use of paper non-negotiable (e.g. an ER triage that requires a small printer for forms; the need for bank tellers to provide receipts to customers)?
      • Do we have compliance obligations that require us to retain a paper process?
      • What is getting printed? Who is printing the most? Identify if there are recurring system-generated reports being printed daily/weekly/quarterly that are adding to the volume. Are reports going directly from staff mailboxes to a recycling bin?
      • Does our print financial model incentivize the transformation of business processes, or does it reinforce old habits?
      • What services, software, and solutions for document management and business process analysis does our managed print services vendor offer? Can we involve the vendor in the business transformation conversation by including an innovation clause in the next contract (re)negotiation to push the vendor to offer proposals for projects that reduce print?

      Develop short-term and long-term print reduction strategies

      Short-term strategies

      • Consolidate the number of printers you have.
      • Determine whether to outsource printing to a managed services provider and make the move.
      • Enable print roaming and IT verification.
      • Require user-queued print jobs to be authenticated at a printer to prevent print jobs that are lost or not picked up.
      • Set up user quotas.
      • Provide usage records to business managers so they can understand the true cost of printing.
      • User quotas may create initial pushback, but they lead users to ask themselves whether a particular print job is necessary.
      • Renegotiate print service contracts.
      • Revisit contracts and shop around to ensure pricing is competitive.
      • Leverage size and centralization by consolidating to a single vendor, and use the printing needs of the entire enterprise to decrease pricing and limit future contractual obligations.
      • Train users on self-support.
      • Train users to remedy paper jams and move paper in and out of paper trays.

      Long-term strategies

      • Promote a paperless culture by convincing employees of its benefits (greater cost savings, better security, easier access, centralized repository, greener).
      • Educate users to use print area wisely.
      • Develop campaigns to promote black and white printing or a paperless culture.

      Info-Tech Insight:

      One-time consolidation initiatives leave money on the table. The extra savings results from changes in printing culture and end-user behavior.

      Examine current printing behavior and habits

      It's natural for printer usage and printing costs to vary based on office, department, and type of employee. Certain jobs simply require more printing than others.

      However, the printing culture within your organization likely also varies based on

      • office
      • department
      • type of employee

      Examine the printing behaviors of your employees based on these factors and determine whether their printing behavior aligns with the nature of their job.

      Excessive printing costs attributed to departments or groups of employees that don't require much printing for their jobs could indicate poor printing culture and potentially more employee pushback.

      Examine current printing behavior and habits, and identify candidates for elimination

      1. Go to Tab 3 of your Printer Reduction Tool ("Usage Dashboard Refresh"). Right-click each table and press "Refresh."
      2. Go to Tab 4 of your Printer Reduction Tool ("Usage Dashboard") to understand the following:
        1. Average printer utilization by department
        2. Pages printed per month by department
        3. Cost per user by department
      3. Take note of the outliers and expensive departments.
      4. Review printer inventory and printer use rates on Tab 5.
      5. Decide which printers are candidates for elimination and which require more research.
      6. If already working in a managed print services model, review the vendor's recommendations for printer elimination and consolidation.
      7. Mark printers that could be eliminated or consolidated.

      Input

      Output
      • Discussion
      • Understanding of expensive departments and other outliers

      Materials

      Participants

      • Printer Reduction Tool
      • IT director/ business operations
      • Business managers

      Administer end-user survey

      Understand end-user printing requirements and current printer performance through an end-user survey

      1. Customize Info-Tech's End-User Print Requirements Survey to help you understand your users' needs and the current performance of your printer fleet.
      2. Send the survey to all printer users in the organization.
      3. Collect the surveys and aggregate the requirements of users in each department.
      4. Record the survey results in the "Survey Results" tab.

      Input

      Output
      • End-user feedback
      • Identification of outliers and expensive departments

      Materials

      Participants

      • End-User Print Requirements Survey template
      • IT director
      • IT staff
      • Rest of organization

      Download the End-User Print Requirements Survey

      Info-Tech Insight:

      Use an end-user printer satisfaction survey before and after any reduction efforts or vendor implementation, both as a requirement-gathering user input and to measure/manage the vendor.

      Identify your current requirements

      Collect all the surveys and aggregate user requirements. Input the requirements into your Printer Reduction Tool.

      Discussion activity:

      • Review the requirements for each department and discuss:
      • What is this device being used for (e.g. internal documents, external documents, high-quality graphics/color)?
      • Based on its use case, what kinds of features are needed (e.g. color printing, scanning to email, stapling)?
      • Is this the right type of device for its purpose? Do we need this device, or can it be eliminated?
      • Based on its use case, what kinds of security features are needed (e.g. secure print release)?
      • Are there any compliance requirements that need to be satisfied (e.g. PCI, ITAR, HIPAA)?
      • Based on its use case, what's the criticality of uptime?
      • What is this device's place in the organization's workflow? What are its dependencies?
      • With which systems is the device compatible? Is it compatible with the newer operating system versions? If not, determine whether the device is a refresh candidate.

      Input

      Output
      • Survey results and department requirements
      • List of current requirements

      Materials

      Participants

      • N/A
      • IT director
      • IT staff

      Identify your future requirements

      Prepare your printer fleet for future needs to avoid premature printer refreshes.

      Discussion activity:

      • Review the current requirements for each department's printers and discuss whether the requirements will meet the department's printing needs over the next 10 years.
      • What is this device going to be used for in the next 10 years?
      • Will use of this device be reduced by plans to increase workflow digitization?
      • Based on its use case, what kinds of features are needed?
      • Is this the right type of device for its purpose?
      • Based on its use case, what kinds of security features are needed?
      • Based on its use case, what is the criticality of uptime?
      • Is this device's place in the organization's workflow going to change? What are its dependencies?
      • Reassess your current requirements and make any changes necessary to accommodate for future requirements.

      Input

      Output
      • Discussion
      • List of future requirements

      Materials

      Participants

      • N/A
      • IT director
      • IT staff

      Examine requirements specific to your industry and workflow

      Some common examples of industries with specific printing requirements:

      • Healthcare
        • Ability to comply with HIPAA requirements
        • High availability and reliability with on-demand support and quick response times
        • Built-in accounting software for billing purposes
        • Barcode printing for hospital wristbands
        • Fax requirements
      • Manufacturing
        • Barcoding technology
        • Ability to meet regulations such as FDA requirements for the pharmaceutical industry
        • Ability to integrate with ERP systems
      • Education
        • Password protection for sensitive student information
        • Test grading solutions
        • Paper tests for accessibility needs

      Phase 2

      Vendor Selection, Evaluation, Acquisition

      Strategy & planning

      Vendor selection, evaluation, acquisition

      Implementation & Operation

      1.1 Create project charter and assign roles

      1.2 Assess current state

      1.3 Gather requirements

      2.1 Understand managed print services model

      2.2 Create RFP materials

      2.3 Leverage print management software

      3.1 Modify printer policies

      3.2 Measure project success

      3.3 Training & adoption

      3.4 Plan communication

      3.5 Prepare for continuous improvement

      Re-Envision Enterprise Printing

      • This phase will walk you through the following activities:
      • Define managed print services RFP requirement questions
      • Create managed print services RFP and scoring tool
      • Score the RFP responses

      This phase involves the following participants:

      • IT director/CIO
      • Business operations manager
      • Project manager

      Change your financial model

      The managed print services industry allows you to use a pay-as-you-go approach and right-size your print spend to the organization's needs.

      Avoid being locked into a long lease where the organization pays a fixed monthly fee whether the printer runs or not.

      Instead, treat enterprise printing as a service, like the soda pop machine in the break room, where the vendor is paid when the device is used. If the vending machine is broken, the vendor is not paid until the technician restores it to operability. Printers can work the same way.

      By moving to a per click/page financial model, the vendor installs and supports the devices and is paid whenever a user prints. Though the organization pays more on a per-click/page basis compared to a lease, the vendor is incentivized to right-size the printer footprint to the organization, and the organization saves on monthly recurring lease costs and maintenance costs.

      Right-size commitments: If the organization remains on a lease instead of pay-per-click model, it should right-size the commitment if printing drops below a certain volume. In the agreement, include a business downturn clause that allows the organization to right-size and protect itself in the event of negative growth.

      Understand the managed print services model and its cost savings

      Outsourcing print services can monitor and balance your printers and optimize your fleet for efficiency. Managed print services are most appropriate for:

      • Organizations engaging in high-volume, high-quality print jobs with growing levels of output.
      • Organizations with many customer-facing print jobs.

      There are three main managed printing service models. Sometimes, an easy switch from a level pay model to a pay-per-click model can result in substantial savings:

      Level Pay

      • Flat rate per month based on estimates.
      • Attempts to flatten IT's budgeting so printing costs are consistent every month or every year (for budgeting purposes). At the end of the year, the amount of supplies used is added up and compared with the initial estimates and adjusted accordingly.
      • The customer pays the same predictable fee each month every year, even if you don't meet the maximum print quantity for the pay. Increased upcharge for quantities exceeding maximum print quantity.

      Base Plus Click

      • Fixed base payment (lease or rental) + pay-per-sheet for services.
      • In addition to the monthly recurring base cost, you pay for what you use. This contract may be executed with or without a minimum monthly page commitment. Page count through remote monitoring technologies is typically required.

      Pay Per Click

      • Payment is solely based on printing usage.
      • Printing costs will likely be the lowest with this option, but also the most variable.
      • This option requires a minimum monthly page commitment and/or minimum term.

      Info-Tech Insight:

      Vendors typically do not like the pay-per-click option and will steer businesses away from it. However, this option holds the vendor accountable for the availability and reliability of your printers, and Info-Tech generally recommends this option.

      Compare financials of each managed print services option

      Your printing costs with a pay-per-click model are most reflective of your actual printer usage. Level pay tends to be more expensive, where you need to pay for overages but don't benefit from printing less than the maximum allocated.

      See the below cost comparison example with level pay set at a maximum of 120,000 impressions per month. In the level pay model, the organization was paying for 120,000 sheets in the month it only used 60,000 impressions, whereas it would have been able to pay just for the 60,000 sheets in the pay-per-click model.

      This image contains tables with the column headings: Impressions per month; Total Cost; Average Cost per Impression; for each of the following categories: Level Pay; Base Plus Click; Pay Per Click

      Financial comparison case study

      This organization compared estimated costs over a 36-month period for the base-plus-click and pay-per-page models for Toshiba E Studio 3515 AC Digital Color Systems.

      Base-plus-click model

      Monthly recurring cost

      Avg. impressions per month

      Monthly cost

      Monthly cost

      "Net pay per click"

      Cost over 36-month period

      A fixed lease cost each month, with an additional per click/page charge

      $924.00

      12,000 (B&W)

      $0.02 (B&W)

      $1,164.00 (B&W)

      $0.097 (B&W)

      $41,904 (B&W)

      5,500 (Color)

      $0.09 (Color)

      $495.00 (Color)

      $0.090 (Color)

      $17,820 (Color)

      Base-plus-click model

      Monthly recurring cost

      Avg. impressions per month

      Monthly cost

      Monthly cost

      "Net pay per click"

      Cost over 36-month period

      No monthly lease cost, only per-image charges

      0.00

      12,000 (B&W)

      $0.06 (B&W)

      $720.00 (B&W)

      $0.060 (B&W)

      $25,920 (B&W)

      5,500 (Color)

      $0.12 (Color)

      $660.00 (Color)

      $0.120 (Color)

      $23,760 (Color)

      Results

      Though the per-image cost for each image is lower in the base-plus-click model, the added monthly recurring costs for the lease means the "net pay per click" is higher.

      Overall, the pay-per-page estimate saved $10,044 over a 36-month period for this device.

      Bake continuing innovation into your requirements

      Once you are in the operation phase, you will need to monitor and analyze trends in company printing in order to make recommendations for the future and to identify areas for possible savings and/or asset optimization.

      Avoid a scenario where the vendor drops the printer in your environment and returns only for repairs. Engage the vendor in this continuous innovation work:

      In the managed services agreement, include a proviso for continuous innovation where the vendor has a contractual obligation to continually look at the business process flow and bring yearly proposals to show innovation (e.g. cost reductions; opportunities to reduce print, which allows the vendor to propose document management services and record keeping services). Leverage vendors who are building up capabilities to transform business processes to help with the heavy lifting.

      Establish a vision for the relationship that goes beyond devices and toner. The vendor can make a commitment to continuous management and constant improvement, instead of installing the devices and leaving. Ideally, this produces a mutually beneficial situation: The client asks the vendor to sell them ways to mature and innovate the business processes, while the vendor retains the business and potentially sells new services. In order to retain your business, the vendor must continue to learn and know about your business.

      The metric of success for your organization is the simple reduction in printed copies overall. The vendor success metric would be proposals that may combine hardware, software, and services that provide cost-effective reductions in print through document management and workflow processes. The vendors should be keen to build this into the relationship since the services delivery has a higher margin for them.

      Sample requirement wording:

      "Continuing innovation: The contractor initiates at least one (1) project each year of the contract that shows leadership and innovation in solutions and services for print, document management, and electronic recordkeeping. Bidders must describe a sample project in their response, planning for an annual investment of approximately 50 consulting hours and $10,000 in hardware and/or software."

      Reward the vendor for performance instead of "punishing" them for service failures

      Problem: Printer downtime and poor service is causing friction with your managed service provider (MSP).

      MSPs often offer clients credit requests (service credits) for their service failures, which are applied to the previous month's monthly recurring charge. They are applied to the last month's MRC (monthly reoccurring charges) at the end of term and then the vendor pays out the residual.

      However, while common, service credits are not always perceived to be a strong incentive for the provider to continually focus on improvement of mean time to respond or mean time to repair.

      Solution: Turn your vendor into a true partner by including an "earn back" condition in the contract.

      • Engage the vendor as a true partner within a relationship based upon service credits.
      • Suggest that the vendor include a minor change to the non-performance processes within the final agreement: the vendor implements an "earn back" condition in the agreement.
      • Where a bank of service credits exists because of non-performance, if the provider exceeds the SLA performance metrics for a number of consecutive months (two is common), then a given number of prior credits received by the client are returned to the provider as a reward for improved performance.
      • This can be a useful mechanism to drive improved performance.

      Leverage enterprise print management software

      Printers are commoditized and can come and go, but print management software enables the governance, compliance, savings and visibility necessary for the transformation

      • Printer management solutions range from tools bundled with ink-jet printers that track consumables' status, to software suites that track data for thousands of print devices.
      • Typically, these solutions arrive in enterprises as part of larger managed services printing engagements, bundled with hardware, financing, maintenance, and "services."
      • Bundling print management software means that customers very rarely seek to acquire printing management software alone.
      • Owing to the level of customization (billing, reporting, quotas, accounts, etc.) switching print management software solutions is also rare. The work you put into this software will remain with IT regardless of your hardware.
      • Durability of print management software is also influenced by the hardware- and technology-agnostic nature of the solutions (e.g. swapping one vendor's devices for another does not trigger anything more than a configuration change in print management software.)

      Include enterprise print management requirements in the RFP

      Ask respondents to describe their managed services capabilities and an optional on-premises, financed solution with these high-level capabilities.

      Select the appropriate type of print management software

      Vendor-provided solutions are adequate control for small organizations with simple print environments

      • Suitable for small organizations (<100 users).
      • Software included with print devices can pool print jobs, secure access, and centralize job administration.
      • Dealing with complex sales channels for third-party vendors is likely a waste of resources.

      SMBs with greater print control needs can leverage mid-level solutions to manage behavior

      • Suitable for mid-size organizations (<500 users).
      • Mid-level software can track costs, generate reports, and centralize management.
      • Solutions start at $500 but require additional per-device costs.

      Full control solutions will only attract large organizations with a mature print strategy

      • Full control solutions tend to be suitable for large organizations (>500 users) with complex print environments and advanced needs.
      • Full control software allows for absolute enforcement of printing policies and full control of printing.
      • Expect to spend thousands for a tailored solution that will save time and guide cost savings.

      Enterprise print management software features

      The feature set for these tools is long and comprehensive. The feature list below is not exhaustive, as specific tools may have additional product capabilities.

      Print Management Software Features

      Hardware-neutral support of all major printer types and operating systems (e.g. direct IP to any IPP-enabled printer along with typical endpoint devices) Tracking of all printing activity by user, client account, printer, and document metadata
      Secure print on demand (Secure print controls: User Authenticated Print Release, Pull Printing) Granular print cost/charging, allowing costs to be assigned on a per-printer basis with advanced options to charge different amounts based on document type (e.g. color, grayscale or duplex), page size, user or group
      Managed and secured mobile printing (iOS/Android), BYOD, and guest printing DaaS/VDI print support
      Printer installation discovery/enablement, device inventory/management Auditing/reporting, print audit trail using document attributes to manage costs/savings, enforce security and compliance with regulations and policies
      Monitoring print devices, print queues, provide notification of conditions Watermarking and/or timestamping to ensure integrity and confidentially/classification of printed documents some solutions support micro font adding print date, time, user id and other metadata values discreetly to a page preventing data leakage
      Active Directory integration or synchronization with LDAP user accounts Per-user quotas or group account budgets
      Ability to govern default print settings policies (B&W, double-sided, no color, etc.)

      Get to the managed print services RFP quicker

      Jumpstart your requirements process using these tools and exercises

      Vendor Assessment Questions

      Use Info-Tech's catalog of commonly used questions and requirements in successful acquisition processes for managed print services. Ask the right questions to secure an agreement that meets your needs. If you are already in a contract with managed print services, take the opportunity of contract renewal to improve the contract and service.

      RFP Template and "Schedule 1" Attachment

      Add your finalized assessment questions into this table, which you will attach to your RFP. The vendor answers questions in this "Schedule 1" attachment and returns it to you.

      RFP Scoring Tool

      Aggregate the RFP responses into this scoring tool to identify the frontrunners and candidates for elimination. Since the vendors are asked to respond in a standard format, it is easier to bring together all the responses to create a complete view of your options.

      Define RFP requirement questions

      Include the right requirements for your organization, and avoid leaving out important requirements that might have been overlooked.

      1. Download the Managed Print Services Vendor Assessment Questions tool. Use this document as a "shopping list" to jumpstart an initial draft of the RFP and, more importantly, scoring requirements.
      2. Review the questions in the context of your near- and long-term printer outsourcing needs. Consider your environment, your requirements, and goals. Include other viewpoints from the RACI chart from Phase 1.
      3. Place an 'X' in the first column to retain the question. Edit the wording of the question if required, based on your organizational needs.
      4. Use the second column to indicate which section of the RFP to include the question in.

      Input

      Output
      • Requirements from Phase 1.3
      • Completed list of requirement questions

      Materials

      Participants

      • Managed Print Services Vendor Assessment Questions tool
      • IT director/business operations
      • Other roles from the RACI chart completed in Phase 1

      Download the Managed Print Services Vendor Assessment Questions tool

      Create RFP scoring tool and RFP

      1. Enter the requirements questions into the scoring tool on Tabs 2 and 4.
      2. Tab 2: Create scoring column for each vendor. You will paste in their responses here.
      3. Edit Tabs 3 and 4 so they align with what you want the vendor to see. Copy and paste Tab 3 and Tab 4 into a new document, which will serve as a "Schedule 1" attachment to the RFP package the vendor receives.
      4. Complete the RFP template. Describe your current state and current printer hardware (documented in the earlier current-state assessment). Explain the rules of how to respond and how to fill out the Schedule 1 document. Instruct each vendor to fill in their responses to each question along with any notes, and to reply with a zip file that includes the completed RFP package along with any marketing material needed to support their response.
      5. Send a copy of the RFP and Schedule 1 to each vendor under consideration.

      Input

      Output
      • Completed list of requirement questions from previous activity
      • RFP Scoring tool
      • Completed RFP and schedule 1 attachment

      Materials

      Participants

      • Managed Print Services RFP Vendor Proposal Scoring Tool
      • Managed Print Services RFP
      • IT director/business operations

      Download the Managed Print Services RFP Vendor Proposal Scoring Tool

      Download the Managed Print Services RFP template

      Score RFP responses

      1. When the responses are returned, copy and paste each vendor's results from Schedule 1 into Tab 2 of the main scoring tool.
      2. Evaluate each RFP response against the RFP criteria based on the scoring scale.
      3. Send the completed scoring tool to the CIO.
      4. Set up a meeting to discuss the scores and generate shortlist of vendors.
      5. Conduct further interviews with shortlisted vendors for due diligence, pricing, and negotiation discussions.
      6. Once a vendor is selected, review the SLAs and contract and develop a transition plan.

      Input

      Output
      • Completed Managed Print Services RFP Vendor Proposal Scoring Tool
      • Shortlist or final decision on vendor

      Materials

      Participants

      • N/A
      • IT director/business operations

      Info-Tech Insight:

      The responses from the low-scoring vendors still have value: these providers will likely provide ideas that you can then leverage with your frontrunner, even if their overall proposal did not score highly.

      Phase 3

      Implementation & Operation

      Strategy & planning

      Vendor selection, evaluation, acquisition

      Implementation & Operation

      1.1 Create project charter and assign roles

      1.2 Assess current state

      1.3 Gather requirements

      2.1 Understand managed print services model

      2.2 Create RFP materials

      2.3 Leverage print management software

      3.1 Modify printer policies

      3.2 Measure project success

      3.3 Training & adoption

      3.4 Plan communication

      3.5 Prepare for continuous improvement

      Re-Envision Enterprise Printing

      This phase will walk you through the following activities:

      • Update your enterprise printer policies
      • Readminister end-user survey to measure project success

      This phase involves the following participants:

      • IT director/CIO
      • Business operations manager
      • Project manager

      Modify your printer policies

      Review and modify Info-Tech's Printer Policy Template to support your print reduction goals

      Consider that your goal is to achieve printer reduction. Discuss with your team how strict it needs to be to truly reset behavior with printers. Many organizations struggle with policy enforcement. Firm language in the policy may be required to achieve this goal. For example,

      • IT only supports the printers acquired through the managed print service. Personal desktop printers are not supported by IT. Expense statements will not be accepted for non-supported printers.
      • Create a procurement policy where all device requests need justification and approval by department managers and IT. Have a debate over what the extreme exceptions would be. Legitimate exceptions must go through a review and approval process.
      • Restrict color printing to external or customer-facing use cases.
      • Encourage digital or electronic solutions in lieu of hard copies (e.g. e-signatures and approval workflows; scanning; use of integrated enterprise applications like SharePoint).
      This is a screenshot of the Printer Policy Page Template

      Download the Printer Policy template

      Readminister the end-user survey

      You have already run this survey during the requirements-gathering phase. Run it again to measure success.

      The survey was run once prior to the changes being implemented to establish a baseline of user satisfaction and to gain insights into additional requirements.

      Several months after the initial rollout (90 days is typical to let the dust settle), resurvey the end users and publish or report to the administration success metrics (the current costs vs. the actual costs prior to the change).

      User satisfaction survey can be used to manage the vendor, especially if the users are less happy after the vendor touched their environment. Use this feedback to hold the provider to account for improvement.

      Input

      Output
      • Previous survey results
      • Changes to baseline satisfaction metrics

      Materials

      Participants

      • End-user survey from Phase 1
      • IT director
      • IT staff
      • Rest of organization

      Measure project success

      Revisit the pre-project metrics and goals and compare with your current metrics

      • Identify printers to consolidate or eliminate.
      • Update asset management system (enter software and hardware serial numbers or identification tags into configuration management system).
      • Reallocate/install printers across the organization.
      • Develop ongoing printer usage and cost reports for each department.
      • Review the end-user survey and compare against baseline.
      • Operate, validate, and distribute usage metrics/chargeback to stakeholders.
      • Audit and report on environmental performance and sustainability performance to internal and external bodies, as required.
      • Write and manage knowledgebase articles.
      • Monitor and analyze trends in company printing in order to make recommendations for the future and to identify areas for possible savings and/or asset optimization.

      Metrics could include

      • User satisfaction
      • Print services net promoter model
      • Total printing costs
      • Printer availability (uptime)
      • Printer reliability (mean time between failures)
      • Total number of reported incidents
      • Mean time for vendor to respond and repair

      Support training and adoption

      Train users on self-support

      Prepare troubleshooting guides and step-by-step visual aid posters for the print areas that guide users to print, release, and find their print jobs and fix common incidents on their own. These may include:

      • The name of this printer location and the names of the others on that floor.
      • How to enter a PIN to release a print job.
      • How to fix a paper jam.
      • How to empty the paper tray.
      • How to log a service ticket if all other steps are exhausted.

      Educate users to use print area wisely

      • Inform users what to do if other print jobs appear to be left behind in the printer area.
      • Display guidelines on printer location alternatives in case of a long line.
      • Display suggestions on maximum recommended time to spend on a job in the event other users are waiting.

      Develop campaign to promote paperless culture

      Ensure business leadership and end users remain committed to thinking before they print.

      • Help your users avoid backsliding by soliciting feedback on the new printer areas.
      • Ensure timely escalation of service tickets to the vendor.
      • Support efforts by the business to seek out business process modernization opportunities whenever possible.

      Plan persuasive communication strategies

      Identify cost-saving opportunities and minimize complaints through persuasive communication

      Solicit the input of end users through surveys and review comments.

      Common complaints Response

      Consider the input of end users when making elimination and consolidation decisions and communicate IT's justification for each end user's argument to keep their desktop printers.

      "I don't trust network storage. I want physical copies." Explain the security and benefits of content management systems.
      "I use my desktop a lot. I need it." Explain the cost benefits of printing on cheaper network MFPs, especially if they print in large quantities.
      "I don't use it a lot, so it's not costly." It's a waste of money to maintain and power underused devices.
      "I need security and confidentiality." MFPs have biometric and password-release functions, which add an increased layer of security.
      "I need to be able to print from home." Print drivers and networked home printers can be insecure devices and attack vectors.
      "I don't have time to wait." Print jobs in queue can be released when users are at the device.
      "I don't want to walk that far." Tell the end user how many feet the device will be within (e.g. 50 feet). It is not usually very far.

      Implement a continual improvement plan to achieve long-term enterprise print goals

      Implement a continual improvement plan for enterprise printing:

      • Develop a vendor management plan:
        • In order to govern SLAs and manage the vendor, ensure that you can track printer-related tickets even if the device is now supported by managed print services.
        • Ensure that printer service tickets sent from the device to the vendor are also reconciled in your ITSM tool. Require the MSP to e-bond the ticket created within their own device and ticketing system back to you so you can track it in your own ITSM tool.
        • Every two months, validate service credits that can be returned to the vendor for exceeding SLA performance metrics.
        • Monitor the impact of their digital transformation strategies. Develop a cadence to review the vendor's suggestions for innovation opportunities.
      • Operate, validate, and distribute usage and experience metrics/chargeback to stakeholders.
      • Monitor and analyze trends in company printing.
      This is a graph which demonstrates the process of continual improvement through Standardization. It depicts a graph with Time as the X axis, and Quality Management as the Y axis. A grey circle with the words: ACT; PLAN; CHECK; DO, moving from the lower left part of the graph to the upper right, showing that standardization improves Quality Management.

      Summary of Accomplishment

      Problem Solved

      You have now re-envisioned your enterprise print environment by documenting your current printer inventory and current cost and usage. You also have hard inventory and usage data benchmarks that you can use to measure the success of future initiatives around digitalization, going paperless, and reducing print cost.

      You have also developed a plan to go to market and become a consumer of managed print services, rather than a provider yourself. You have established a reusable RFP and requirements framework to engage a managed print services vendor who will work with you to support your continuous improvement plans.

      Return to the deliverables and advice in this blueprint to reinforce the organization's message to end users on when, where, and how to print. Ideally, this project has helped you go beyond a printer refresh – but rather served as a means to change the printing culture at your organization.

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech workshop.

      Contact your account representative for more information

      workshops@infotech.com
      1-888-670-8889

      Bibliography

      Fernandes, Louella. "Quocirca Managed Services Print Market, 2021." Quocirca, 25 Mar. 2021. Accessed 12 Oct. 2021.

      McInnes, Angela. "No More Photocopies, No More Ink: Thames Valley Schools Run Out of Toner." CBC, 21 Oct. 2021. Web.

      "Paper and Paperboard: Material-Specific Data." EPA, 15 Dec. 2020. Accessed 15 Oct. 2021.

      State of Washington, House of Representatives. "State Agencies – Paper Conservation and Recycling." 61st Legislature, Substitute House Bill 2287, Passed 20 April 2009.

      Sugihara, Azusa. "Pandemic Shreds Office Paper Demand as Global Telework Unfolds." Nikkei Asia, 18 July 2020. Accessed 29 Sept. 2021.

      "Paper Reduction." University of Washington, n.d. Accessed 28 Oct. 2021.

      "What is MPS?" University of Washington, n.d. Accessed 16 Mar. 2022.

      Research contributors

      Jarrod Brumm
      Senior Digital Transformation Consultant

      Jacques Lirette
      President, Ditech Testing

      3 anonymous contributors

      Info-Tech Research Group Experts

      Allison Kinnaird, Research Director & Research Lead
      Frank Trovato, Research Director

      Plan Your Digital Transformation on a Page

      • Buy Link or Shortcode: {j2store}81|cart{/j2store}
      • member rating overall impact: 8.0/10 Overall Impact
      • member rating average dollars saved: $34,649 Average $ Saved
      • member rating average days saved: 20 Average Days Saved
      • Parent Category Name: IT Strategy
      • Parent Category Link: /it-strategy
      • Digital investments often under deliver on expectations of return, and there is no cohesive approach to managing the flow of capital into digital.
      • The focus of the business has historically been to survive technological disruption rather than to thrive in it.
      • Strategy is based mostly on opinion rather than an objective analysis of the outcomes customers want from the organization.
      • Digital is considered a buzzword – nobody has a clear understanding of what it is and what it means in the organization’s context.

      Our Advice

      Critical Insight

      • The purpose of going digital is getting one step closer to the customer. The mark of a digital organization lies in how they answer the question, “How does what we’re doing contribute to what the customer wants from us?”
      • The goal of digital strategy is digital enablement. An organization that is digitally enabled no longer needs a digital strategy, it’s just “the strategy.”

      Impact and Result

      • Focus strategy making on delivering the digital outcomes that customers want.
        • Leverage the talent, expertise, and perspectives within the organization to build a customer-centric digital strategy.
      • Design a balanced digital strategy that creates value across the five digital value pools:
        • Digital marketing, digital channels, digital products, digital supporting capabilities, and business model innovation.
      • Ask how disruption can be leveraged, or even become the disruptor.
        • Manage disruption through quick-win approaches and empowering staff to innovate.
      • Use a Digital Strategy-on-a-Page to spark the digital transformation.
        • Drive awareness and alignment on the digital vision and spark your organization’s imagination around digital.

      Plan Your Digital Transformation on a Page Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to understand how digital disruption is driving the need for transformation, and how Info-Tech’s methodology can help.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Scope the digital transformation

      Learn how to apply the Digital Value Pools thought model and scope strategy around them.

      • Plan Your Digital Transformation on a Page – Phase 1: Scope the Digital Transformation

      2. Design the digital future state vision

      Identify business imperatives, define digital outcomes, and define the strategy’s guiding principles.

      • Plan Your Digital Transformation on a Page – Phase 2: Design the Digital Future State Vision
      • Digital Strategy on a Page

      3. Define the digital roadmap

      Define, prioritize, and roadmap digital initiatives and plan contingencies.

      • Plan Your Digital Transformation on a Page – Phase 3: Define the Digital Roadmap

      4. Sustain digital transformation

      Create, polish, and socialize the Digital Strategy-on-a-Page.

      • Plan Your Digital Transformation on a Page – Phase 4: Sustain Digital Transformation
      [infographic]

      Workshop: Plan Your Digital Transformation on a Page

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Scope the Digital Transformation

      The Purpose

      Identify the need for and use of digital strategy and determine a realistic scope for the digital strategy.

      Key Benefits Achieved

      The digital strategy project is planned and scoped around a subset of the five digital value pools.

      Activities

      1.1 Introduction to digital strategy.

      1.2 Establish motivation for digital.

      1.3 Discuss in-flight digital investments.

      1.4 Define the scope of digital.

      1.5 Identify stakeholders.

      1.6 Perform discovery interviews.

      1.7 Select two value pools to focus day 2, 3, and 4 activities.

      Outputs

      Business model canvas

      Stakeholder power map

      Discovery interview results

      Two value pools for focus throughout the workshop

      2 Design the Digital Future State Vision

      The Purpose

      Create guiding principles to help define future digital initiatives. Generate the target state with the help of strategic goals.

      Key Benefits Achieved

      Establish the basis for planning out the initiatives needed to achieve the target state from the current state.

      Activities

      2.1 Identify digital imperatives.

      2.2 Define key digital outcomes.

      2.3 Create a digital investment thesis.

      2.4 Define digital guiding principles.

      Outputs

      Corporate strategy analysis, PESTLE analysis, documented operational pain points (value streams)

      Customer needs assessment (journey maps)

      Digital investment thesis

      Digital guiding principles

      3 Define the Digital Roadmap

      The Purpose

      Understand the gap between the current and target state. Create transition options and assessment against qualitative and quantitative metrics to generate a list of initiatives the organization will pursue to reach the target state. Build a roadmap to plan out when each transition initiative will be implemented.

      Key Benefits Achieved

      Finalize the initiatives the organization will use to achieve the target digital state. Create a roadmap to plan out the timing of each initiative and generate an easy-to-present document for digital strategy approval.

      Activities

      3.1 Identify initiatives to achieve digital outcomes.

      3.2 Align in-flight initiatives to digital initiatives.

      3.3 Prioritize digital initiatives.

      3.4 Document architecturally significant requirements for high-priority initiatives.

      Outputs

      Digital outcomes and KPIs

      Investment/value pool matrix

      Digital initiative prioritization

      Architecturally significant requirements for high-priority initiatives

      4 Define the Digital Roadmap

      The Purpose

      Plan your approach to socializing the digital strategy to help facilitate the cultural changes necessary for digital transformation.

      Key Benefits Achieved

      Plant the seed of digital and innovation to start making digital a part of the organization’s DNA.

      Activities

      4.1 Review and refine Digital Strategy on a Page.

      4.2 Assess company culture.

      4.3 Define high-level cultural changes needed for successful transformation.

      4.4 Define the role of the digital transformation team.

      4.5 Establish digital transformation team membership and desired outcomes.

      Outputs

      Digital Strategy on a Page

      Strategyzer Culture Map

      Digital transformation team charter

      Understand and Apply Internet-of-Things Use Cases to Drive Organizational Success

      • Buy Link or Shortcode: {j2store}535|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Customer Relationship Management
      • Parent Category Link: /customer-relationship-management
      • The Internet of Things (IoT) is a rapidly proliferating technology – connected devices have experienced unabated growth over the last ten years.
      • The business wants to capitalize on the IoT and move the needle forward for proactive customer service and operational efficiency.
      • Moreover, IT wants to maintain its reputation as forward-thinking, and the business wants to be innovative.

      Our Advice

      Critical Insight

      • Leverage Info-Tech’s comprehensive three-phase approach to IoT projects: understand the fundamentals of IoT capabilities, assess where the IoT will drive value within the organization, and present findings to stakeholders.
      • Conduct a foundational IoT discussion with stakeholders to level set expectations about the technology’s capabilities.
      • Determine your organization’s approach to the IoT in terms of both hardware and software.
      • Determine which use case your organization fits into: three of the use cases highlighted in this report include predictive customer service, smart offices, and supply chain applications.

      Impact and Result

      • Our methodology addresses the possible issues by using a case-study approach to demonstrate the “Art of the Possible” for the IoT.
      • With an understanding of the IoT, it is possible to find applicable use cases for this emerging technology and get a leg up on competitors.

      Understand and Apply Internet-of-Things Use Cases to Drive Organizational Success Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why your organization should care about the IoT’s potential to transform the service and the workplace, and how Info-Tech will support you as you identify and build your IoT use cases.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Understand core IoT use cases

      Analyze the scope of the IoT and the three most prominent enterprise use cases.

      • Understand and Apply Internet-of-Things Use Cases to Drive Organizational Success – Phase 1: Understand Core IoT Use Cases

      2. Build the business case for IoT applications

      Develop and prioritize use cases for the IoT using Info-Tech’s IoT Initiative Framework.

      • Understand and Apply Internet-of-Things Use Cases to Drive Organizational Success – Phase 2: Build the Business Case for IoT Initiatives

      3. Present IoT initiatives to stakeholders

      Present the IoT initiative to stakeholders and understand the way forward for the IoT initiative.

      • Understand and Apply Internet-of-Things Use Cases to Drive Organizational Success – Phase 3: Present IoT Initiatives to Stakeholders
      • Internet of Things Stakeholder Presentation Template
      [infographic]

      Capture and Market the ROI of Your VMO

      • Buy Link or Shortcode: {j2store}212|cart{/j2store}
      • member rating overall impact: 9.0/10 Overall Impact
      • member rating average dollars saved: $108,234 Average $ Saved
      • member rating average days saved: 9 Average Days Saved
      • Parent Category Name: Vendor Management
      • Parent Category Link: /vendor-management
      • All IT organizations are dependent on their vendors for technology products, services, and solutions to support critical business functions.
      • Measuring the impact of and establishing goals for the vendor management office (VMO) to maximize its effectiveness requires an objective and quantitative approach whenever possible.
      • Sharing the VMO’s impact internally is a balancing act between demonstrating value and self-promotion.

      Our Advice

      Critical Insight

      • The return on investment (ROI) calculation for your VMO must be customized. The ROI components selected must match your VMO ROI maturity, resources, and roadmap. There is no one-size-fits-all approach to calculating VMO ROI.
      • ROI contributions come from many areas and sources. To maximize the VMO’s ROI, look outside the traditional framework of savings and cost avoidance to vendor-facing interactions and the impact the VMO has on internal departments.

      Impact and Result

      • Quantifying the contributions of the VMO takes the guess work out of whether the VMO is performing adequately.
      • Taking a comprehensive approach to measuring the value created by the VMO and the ROI associated with it will help the organization appreciate the importance of the VMO.
      • Establishing goals for the VMO with the help of the executives and key stakeholders ensures that the VMO is supporting the needs of the entire organization.

      Capture and Market the ROI of Your VMO Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should calculate and market internally your VMO’s ROI, review Info-Tech’s methodology, and understand the ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Get organized

      Begin the process by identifying your VMO’s ROI maturity level and which calculation components are most appropriate for your situation.

      • Capture and Market the ROI of the VMO – Phase 1: Get Organized
      • VMO ROI Maturity Assessment Tool
      • VMO ROI Calculator and Tracker
      • VMO ROI Data Source Inventory and Evaluation Tool
      • VMO ROI Summary Template

      2. Establish baseline

      Set measurement baselines and goals for the next measurement cycle.

      • Capture and Market the ROI of the VMO – Phase 2: Establish Baseline
      • VMO ROI Baseline and Goals Tool

      3. Measure and monitor results

      Measure the VMO's ROI and value created by the VMO’s efforts and the overall internal satisfaction with the VMO.

      • Capture and Market the ROI of the VMO – Phase 3: Measure and Monitor Results
      • RFP Cost Estimator
      • Improvements in Working Capital Estimator
      • Risk Estimator
      • General Process Cost Estimator and Delta Estimator
      • VMO Internal Client Satisfaction Survey
      • Vendor Security Questionnaire
      • Value Creation Worksheet
      • Deal Summary Report Template

      4. Report results

      Report the results to key stakeholders and executives in a way that demonstrates the value added by the VMO to the entire organization.

      • Capture and Market the ROI of the VMO – Phase 4: Report Results
      • Internal Business Review Agenda Template
      • IT Spend Analytics
      • VMO ROI Reporting Worksheet
      • VMO ROI Stakeholder Report Template
      [infographic]

      Workshop: Capture and Market the ROI of Your VMO

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Get Organized

      The Purpose

      Determine how you will measure the VMO’s ROI.

      Key Benefits Achieved

      Focus your measurement on the appropriate activities.

      Activities

      1.1 Determine your VMO’s maturity level and identify applicable ROI measurement categories.

      1.2 Review and select the appropriate ROI formula components for each applicable measurement category.

      1.3 Compile a list of potential data sources, evaluate the viability of each data source selected, and assign data collection and analysis responsibilities.

      1.4 Communicate progress and proposed ROI formula components to executives and key stakeholders for feedback and/or approval/alignment.

      Outputs

      VMO ROI maturity level and first step of customizing the ROI formula components.

      Second and final step of customizing the ROI formula components…what will actually be measured.

      Viable data sources and assignments for team members.

      A progress report for key stakeholders and executives.

      2 Establish Baseline

      The Purpose

      Set baselines to measure created value against.

      Key Benefits Achieved

      ROI contributions cannot be objectively measured without baselines.

      Activities

      2.1 Gather baseline data.

      2.2 Calculate/set baselines.

      2.3 Set SMART goals.

      2.4 Communicate progress and proposed ROI formula components to executives and key stakeholders for feedback and/or approval/alignment.

      Outputs

      Data to use for calculating baselines.

      Baselines for measuring ROI contributions.

      Value creation goals for the next measurement cycle.

      An updated progress report for key stakeholders and executives.

      3 Measure and Monitor Results

      The Purpose

      Calculate the VMO’s ROI.

      Key Benefits Achieved

      An understanding of whether the VMO is paying for itself.

      Activities

      3.1 Assemble the data and calculate the VMO’s ROI.

      3.2 Organize the data for the reporting step.

      Outputs

      The VMO’s ROI expressed in terms of how many times it pays for itself (e.g. 1X, 3X, 5X).

      Determine which supporting data will be reported.

      4 Report Results

      The Purpose

      Report results to stakeholders.

      Key Benefits Achieved

      Stakeholders understand the value of the VMO.

      Activities

      4.1 Create a reporting template.

      4.2 Determine reporting frequency.

      4.3 Decide how the reports will be distributed or presented.

      4.4 Send out a draft report and update based on feedback.

      Outputs

      A template for reporting ROI and supporting data.

      A decision about quarterly or annual reports.

      A decision regarding email, video, and in-person presentation of the ROI reports.

      Final ROI reports.

      Create Stakeholder-Centric Architecture Governance

      • Buy Link or Shortcode: {j2store}583|cart{/j2store}
      • member rating overall impact: 8.0/10 Overall Impact
      • member rating average dollars saved: $3,099 Average $ Saved
      • member rating average days saved: 4 Average Days Saved
      • Parent Category Name: Strategy & Operating Model
      • Parent Category Link: /strategy-and-operating-model
      • Traditional enterprise architecture management (EAM) caters to only 10% – the IT people, and not to the remaining 90% of the organization.
      • EAM practices do not scale well with the agile way of working and are often perceived as "bottlenecks” or “restrictors of design freedom.”
      • The organization scale does not justify a full-fledged EAM with many committees, complex processes, and detailed EA artifacts.

      Our Advice

      Critical Insight

      Architecture is a competency, not a function. Project teams, including even business managers outside of IT, can assimilate “architectural thinking.”

      Impact and Result

      Increase business value through the dissemination of architectural thinking throughout the organization. Maturing your EAM practices beyond a certain point does not help.

      Create Stakeholder-Centric Architecture Governance Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Start here

      Improve benefits from your enterprise architecture efforts through the dissemination of architecture thinking throughout your organization.

      • Create Stakeholder-Centric Architecture Governance Storyboard
      [infographic]

      Leadership, Culture and Values

      • Buy Link or Shortcode: {j2store}34|cart{/j2store}
      • Related Products: {j2store}34|crosssells{/j2store}
      • member rating overall impact: 9.4/10
      • member rating average dollars saved: $912
      • member rating average days saved: 7
      • Parent Category Name: People and Resources
      • Parent Category Link: /people-and-resources

      The challenge

      • Your talent pool determines IT performance and stakeholder satisfaction. You need to retain talent and continually motivate them to go the extra mile.
      • The market for IT talent is growing, in the sense that talent has many more options these days. Turnover is a serious threat to IT's ability to deliver top-notch service to your company.
      • Engagement is more than HR's responsibility. IT leadership is accountable for the retention of top talent and the overall productivity of IT employees.

      Our advice

      Insight

      • Engagement goes both ways. Your initiatives must address a real need, and employees must actively seek the outcomes. Engagement is not a management edict.
      • Engagement is not about access to the latest perks and gadgets. You must address the right and challenging issues. Use a systematic approach to find what lives among the employees and address these.
      • Your impact on your employees is many times bigger than HR's. Leverage your power to lead your team to success and peak performance.

      Impact and results 

      • Our engagement diagnostic and other tools will help get to the root of disengagement in your team.
      • Our guidance helps you to avoid common errors and engagement program pitfalls. They allow you to take control of your own team's engagement.

      The roadmap

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      Get started

      Our concise executive brief shows you why engagement is critical to IT performance in your company. We'll show you our methodology and the ways we can help you in handling this.

      Measure your employee engagement

      You can use our full engagement surveys.

      • Improve Employee Engagement to Drive IT Performance – Phase 1: Measure Employee Engagement (ppt)
      • Engagement Strategy Record (doc)
      • Engagement Communication Template (doc)

      Analyze the results and brainstorm solutions

      Understand your employees' engagement drivers. Involve your team in brainstorming engagement initiatives.

      • Improve Employee Engagement to Drive IT Performance – Phase 2: Analyze Results and Ideate Solutions (ppt)
      • Engagement Survey Results Interpretation Guide (ppt)
      • Full Engagement Survey Focus Group Facilitation Guide (ppt)
      • Pulse Engagement Survey Focus Group Facilitation Guide (ppt)
      • Focus Group Facilitation Guide Driver Definitions (doc)
      • One-on-One Manager Meeting Worksheet (doc)

      Select and implement engagement initiatives

      Choose those initiatives that show the most promise with the most significant impact. Create your action plan and establish transparent and open, and ongoing communication with your team.

      • IT Knowledge Transfer Plan Template (xls)
      • IT Knowledge Identification Interview Guide Template (doc)

      Build your knowledge transfer roadmap

      Knowledge transfer is an ongoing effort. Prioritize and define your initiatives.

      • Improve Employee Engagement to Drive IT Performance – Phase 3: Select and Implement Engagement Initiatives (ppt)
      • Summary of Interdepartmental Engagement Initiatives (doc)
      • Engagement Progress One-Pager (ppt)

       

      Develop Your Value-First Business Process Automation Strategy

      • Buy Link or Shortcode: {j2store}236|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Optimization
      • Parent Category Link: /optimization

      Business process automation (BPA) has gained momentum, especially as pilots result in positive outcomes such as improved customer experience, efficiencies, and cost savings. Stakeholders want to invest more in BPA solutions and scale initial successes across different business and IT functions.

      But it’s critical to get it right and not fall into the hype so that the costs don’t outweigh the benefits.

      Ultimately, all BPA initiatives should align with a common vision.

      Build the right BPA strategy – smarter, not faster

      Organizations should adopt a methodical approach to growing their BPA, taking cost, talent availability, and goals into account.

      1. Recognize the true value of automation. Successful BPA improves more than cost savings and revenue generation. Employee satisfaction, organizational reputation, brand, and better-performing products and services are other sought-after benefits.
      2. Consider all relevant factors as you build a strategy. Take into account the impact BPA initiatives will have on users, risk and change appetites, customer satisfaction, and business priorities.
      3. Mature your practice as you scale your BPA technologies. Develop skills, resources, and governance practices as you scale your automation tools. Deploy BPA with quality in mind, then continuously monitor, review, and maintain the automation for success.
      4. Learn from your initial automations. Maximize what you learn from your minimum viable automations (MVA) and use that knowledge to build and scale your automation implementation across the organization.

      Develop Your Value-First Business Process Automation Strategy Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Business Process Automation Strategy Deck – A step-by-step document that walks you through how to position business process automation as a key capability and assess the organization’s readiness for its adoption.

      This blueprint helps you develop a strategy justify the scaling and maturing of your business process automation (BPA) practices and capabilities to fulfill your business priorities.

      • Develop Your Value-First Business Process Automation Strategy – Phases 1-4

      2. Business Process Automation Strategy Template – A template to help you build a clear and compelling strategy document for stakeholders.

      Document your business process automation strategy in the language your stakeholders understand. Tailor this document to fit your BPA objectives and initiatives.

      • Business Process Automation Strategy Template

      3. Business Process Automation Maturity Assessment Tool – A tool to help gauge the maturity of your BPA practice.

      Evaluate the maturity of the key capabilities of your BPA practice to determine its readiness to support complex and scaled BPA solutions.

      • Business Process Automation Maturity Assessment Tool

      Infographic

      Workshop: Develop Your Value-First Business Process Automation Strategy

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Understand the Context

      The Purpose

      Understand the business priorities and your stakeholders' needs that are driving your business process automation initiatives while abiding by the risk and change appetite of your organization.

      Key Benefits Achieved

      Translate business priorities to the context of business process automation.

      Arrive at a common definition of business value.

      Come to an understanding of the needs, concerns, and problems of BPA stakeholders.

      Discover organizational risk and change tolerance and appetite.

      Activities

      1.1 Set the Business Context

      1.2 Understand Your Stakeholder Needs

      1.3 Build Your Risk & Change Profile

      Outputs

      Business problem, priorities, and business value definition

      Customer and end-user assessment (e.g. personas, customer journey)

      Risk and change profile

      2 Define Your BPA Objectives and Opportunities

      The Purpose

      Set reasonable and achievable expectations for your BPA initiatives and practices, and select the right BPA opportunities to meet these expectations.

      Key Benefits Achieved

      Align BPA objectives and metrics to your business priorities.

      Create guiding principles that support your organization’s and team’s culture.

      Define a vision of your target-state BPA practice

      Create a list of BPA opportunities that will help build your practice and meet business priorities.

      Activities

      2.1 Define Your BPA Expectations

      2.2 List Your Guiding Principles

      2.3 Envision Your BPA Target State

      2.4 Build Your Opportunity Backlog

      Outputs

      BPA problem statement, objectives, and metrics

      BPA guiding principles

      Desired scaled BPA target state

      Prioritized BPA opportunities

      3 Assess Your BPA Maturity

      The Purpose

      Evaluate the current state of your BPA practice and its readiness to support scaled and complex BPA solutions.

      Key Benefits Achieved

      List key capabilities to implement and optimize to meet the target state of your BPA practice.

      Brainstorm solutions to address the gaps in your BPA capabilities.

      Activities

      3.1 Assess Your BPA Maturity

      Outputs

      BPA maturity assessment

      4 Roadmap Your BPA Initiatives

      The Purpose

      Identify high-priority key initiatives to support your BPA objectives and goals, and establish the starting point of your BPA strategy.

      Key Benefits Achieved

      Create an achievable roadmap of BPA initiatives designed to deliver good practices and valuable automations.

      Perform a risk assessment of your BPA initiatives and create mitigations for high-priority risks.

      Find the starting point in the development of your BPA strategy.

      Activities

      4.1 Roadmap Your BPA Initiatives

      4.2 Assess and Mitigate Your Risks

      4.3 Complete Your BPA Strategy

      Outputs

      List of BPA initiatives and roadmap

      BPA initiative risk assessment

      Initial draft of your BPA strategy

      M&A Runbook for Infrastructure and Operations

      • Buy Link or Shortcode: {j2store}60|cart{/j2store}
      • member rating overall impact: 9.0/10 Overall Impact
      • member rating average dollars saved: After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.
      • member rating average days saved: Read what our members are saying
      • Parent Category Name: Strategy and Organizational Design
      • Parent Category Link: /strategy-and-organizational-design
      • I&O is often the last to be informed of an impending M&A deal.
      • The business doesn’t understand the necessary requirements or timeline for integration.
      • It’s hard to prioritize when you’re buried under a mountain of work.
      • Documentation may be lacking or nonexistent, and members of the target organization may be uncooperative.

      Our Advice

      Critical Insight

      • Manage expectations. The business often expects integration in days or weeks, not months or years. You need to set them straight.
      • Open your checkbook and prepare to hire. Integration will require a temporary increase in resources.
      • Tackle organizational and cultural change. People are harder to integrate than technology. Culture change is the hardest part, and the integration plan should address it.

      Impact and Result

      • Tailor your approach based on the business objectives of the merger or acquisition.
      • Separate the must-haves from the nice-to-haves.
      • Ensure adequate personnel and budget.
      • Plan for the integration into normal operations.

      M&A Runbook for Infrastructure and Operations Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out how to partner with the business to conquer the challenges in your next merger or acquisition.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Establish goals

      Partner with the business to determine goals and establish high-level scope.

      • M&A Runbook for Infrastructure and Operations – Phase 1: Establish Goals
      • I&O M&A Project Napkin

      2. Conduct discovery

      Find out what the target organization’s I&O looks like.

      • M&A Runbook for Infrastructure and Operations – Phase 2: Conduct Discovery
      • I&O M&A Discovery Letter Template
      • I&O M&A Discovery Template
      • I&O M&A Workbook
      • I&O M&A Risk Assessment Tool

      3. Plan short-term integration

      Build a plan to achieve a day 1 MVP.

      • M&A Runbook for Infrastructure and Operations – Phase 3: Plan Short-Term Integration
      • I&O M&A Short-Term Integration Capacity Assessment Tool

      4. Map long-term integration

      Chart a roadmap for long-term integration.

      • M&A Runbook for Infrastructure and Operations – Phase 4: Map Long-Term Integration
      • I&O M&A Long-Term Integration Portfolio Planning Tool
      [infographic]

      Workshop: M&A Runbook for Infrastructure and Operations

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 High-Level Scope

      The Purpose

      Establish goals and conduct discovery.

      Key Benefits Achieved

      Alignment with business goals

      Documentation of target organization’s current state

      Activities

      0.1 Consult with stakeholders.

      0.2 Establish M&A business goals.

      0.3 Conduct target discovery.

      0.4 Document own environment.

      0.5 Clarify goals.

      Outputs

      Stakeholder communication plan

      M&A business goals

      I&O M&A Discovery Template

      Current state of organization

      2 Target Assessment

      The Purpose

      Assess risk and value of target organization.

      Key Benefits Achieved

      Accurate scope of I&O integration

      Risk mitigation plans

      Value realization strategies

      Activities

      1.1 Scope I&O M&A project.

      1.2 Assess risks.

      1.3 Assess value.

      Outputs

      I&O M&A Project Napkin

      Risk assessment

      Value assessment

      3 Day 1 Integration Project Plan

      The Purpose

      Establish day 1 integration project plan.

      Key Benefits Achieved

      Smoother day 1 integration

      Activities

      2.1 Determine Day 1 minimum viable operating model post M&A.

      2.2 Identify gaps.

      2.3 Build day 1 project plan.

      2.4 Estimate required resources.

      Outputs

      Day 1 project plan

      4 Long-Term Project Plan

      The Purpose

      Draw long-term integration roadmap.

      Key Benefits Achieved

      Improved alignment with M&A goals

      Greater realization of the deal’s value

      Activities

      3.1 Set long-term future state goals.

      3.2 Create a long-term project plan.

      3.3 Consult with business stakeholders on the long-term plan.

      Outputs

      Long-term integration project plan

      5 Change Management and Continual Improvement

      The Purpose

      Prepare for organization and culture change.

      Refine M&A I&O integration process.

      Key Benefits Achieved

      Smoother change management

      Improved M&A integration process

      Activities

      4.1 Complete a change management plan.

      4.2 Conduct a process post-mortem.

      Outputs

      Change management plan

      Process improvements action items

      Identify and Manage Operational Risk Impacts on Your Organization

      • Buy Link or Shortcode: {j2store}230|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Vendor Management
      • Parent Category Link: /vendor-management

      More than any other time, our world is changing. As a result, organizations – and their vendors – need to be able to adapt their plans to accommodate risk on an unprecedented level.

      A new threat will impact your organization's operations at some point. Make sure your plans are flexible enough to manage the inevitable consequences and that you understand where those threats may originate.

      Our Advice

      Critical Insight

      • Identifying and managing a vendor’s potential operational impact on your organization requires multiple people in the organization across several functions. Those people all need coaching on the potential changes in the market and how these changes may affect operations.
      • Organizational leadership is often taken unaware during crises, and their plans lack the flexibility to adjust to significant market upheavals.

      Impact and Result

      Vendor management practices educate organizations on the different potential risks from vendors in your market and suggest creative and alternative ways to avoid and help manage them.

      • Prioritize and classify your vendors with quantifiable, standardized rankings.
      • Prioritize focus on your high-risk vendors.
      • Standardize your processes for identifying and monitoring vendor risks to manage potential impacts with our Operational Risk Impact Tool.

      Identify and Manage Operational Risk Impacts on Your Organization Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Identify and Manage Operational Risk Impacts to Your Organization Storyboard – Use this research to better understand the negative impacts of vendor actions to your brand reputation.

      Use this research to identify and quantify the potential operational impacts caused by vendors. Utilize Info-Tech's approach to look at the operational impact from various perspectives to better prepare for issues that may arise.

      • Identify and Manage Operational Risk Impacts to Your Organization Storyboard

      2. Operational Risk Impact Tool – Use this tool to help identify and quantify the operational impacts of negative vendor actions.

      By playing the “what if” game and asking probing questions to draw out – or eliminate - possible negative outcomes, everyone involved adds their insight into parts of the organization to gather a comprehensive picture of potential impacts.

      • Operational Risk Impact Tool
      [infographic]

      Further reading

      Identify and Manage Operational Risk Impacts on Your Organization

      Understand internal and external vendor risks to avoid potential disaster.

      Analyst perspective

      Organizations need to be aware of the operational damage vendors may cause to plan around those impacts effectively.

      Frank Sewell

      Organizations must be mindful that operational risks come from internal and external vendor sources. Missing either component in the overall risk assessment can significantly impact day-to-day business processes that cost revenue, delay projects, and lead to customer dissatisfaction.

      Frank Sewell,

      Research Director, Vendor Management
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      More than any other time, our world is changing rapidly. As a result, organizations – and their vendors – need to be able to adapt their plans to accommodate risk on an unprecedented level.

      A new threat will impact your organization's operations at some point. Make sure your plans are flexible enough to manage the inevitable consequences and that you understand where those threats may originate.

      Common Obstacles

      Identifying and managing a vendor’s potential operational impact on your organization requires multiple people in the organization across several functions. Those people all need coaching on the potential changes in the market and how these changes may affect operations.

      Organizational leadership is often taken unaware during crises, and their plans lack the flexibility to adjust to significant market upheavals.

      Info-Tech's Approach

      Vendor management practices educate organizations on the different potential risks from vendors in your market and suggest creative and alternative ways to avoid and help manage them.

      Prioritize and classify your vendors with quantifiable, standardized rankings.

      Prioritize focus on your high-risk vendors.

      Standardize your processes for identifying and monitoring vendor risks to manage potential impacts with our Operational Risk Impact Tool.

      Info-Tech Insight

      Organizations must evolve their risk assessments to be more adaptive to respond to threats in the market. Ongoing monitoring of the vendors tied to company operations, and understanding where those vendors impact your operations, is imperative to avoiding disasters.

      Info-Tech’s multi-blueprint series on vendor risk assessment

      There are many individual components of vendor risk beyond cybersecurity.

      There are many components to vendor risk, including: Financial, Reputational, Operational, Strategic, Security, Regulatory & Compliance.

      This series will focus on the individual components of vendor risk and how vendor management practices can facilitate organizations’ understanding of those risks.

      Out of Scope:
      This series will not tackle risk governance, determining overall risk tolerance and appetite, or quantifying inherent risk.

      Operational risk impacts

      Potential losses to the organization due to incidents that affect operations.

      • In this blueprint we’ll explore operational risks, particularly from third-party vendors, and their impacts.
      • Identify potentially disruptive events to assess the overall impact on organizations and implement adaptive measures to identify, manage, and monitor vendor performance.
      Operational

      The world is constantly changing

      The IT market is constantly reacting to global influences. By anticipating changes, leaders can set expectations and work with their vendors to accommodate them.

      When the unexpected happens, being able to adapt quickly to new priorities ensures continued long-term business success.

      Below are some things no one expected to happen in the last few years:

      27%

      Businesses are changing their internal processes around TPRM in response to the Pandemic.

      70%

      Of organizations attribute a third-party breach to too much privileged access.

      85%

      Of breaches involved human factors (phishing, poor passwords, etc.).

      Assess internal and external operational risk impacts

      Due diligence and consistent monitoring are the keys to safeguarding your organization.

      Two sides of the Same Coin

      Internal

      • Poorly vetted supplemental staff
      • Bad system configurations
      • Lack of relevant skills
      • Poor vendor performance
      • Failure to follow established processes
      • Weak contractual accountability
      • Unsupportable or end-of-life system components

      External

      • Cyberattacks
      • Supply Chain Issues
      • Geopolitical Disruptions
      • Vendor Acquisitions
      • N-Party Non-Compliance
      • Vendor Fraud

      Operational risk is the risk of losses caused by flawed or failed processes, policies, systems, or events that disrupt business operations.

      - Wikipedia

      Internal operational risk

      Vendors operating within your secure perimeter can open your organization to substantial risk.

      Frequently monitor your internal process around vendor management to ensure safe operations.

      • Poorly vetted supplemental staff
      • Bad system configurations
      • Lack of relevant skills
      • Poor vendor performance
      • Failure to follow established processes
      • Weak contractual accountability
      • Unsupportable or end-of-life system components

      Info-Tech Insight

      You may have solid policies, but if your employees and vendors are not following them, they will not protect the organization.

      External operational risks

      • Cyberattacks
      • Supplier issues and geopolitical instability
      • Vendor acquisitions
      • N-party vendor non-compliance

      Identify and manage operational risks

      Poorly configured systems

      Failing to ensure that your vendor-supported systems are properly configured and that your vendors are meeting your IT change control and configuration standards is more commonplace than expected. Proper oversight and management of your support vendors are crucial to ensure they are meeting expectations in this regard.

      Failure to follow processes

      Most companies have policies and procedures around IT change and configuration control, security standards, risk management, vendor performance standards, etc. While having these processes is a good start, failure to perform continuous monitoring and management of these leads to increased risks of incidents.

      Supply chain disruptions

      Awareness of the supply chain's complications, and each organization's dependencies, are increasing for everyone. However, most organizations still do not understand the chain of n-party vendors that support their specific vendors or how interruptions in their supply chains could affect them. The 2022 Toyota shutdown due to Kojima is a perfect example of how one essential parts vendor could shut down your operations.

      What to look for

      Identify operational risk impacts

      • Does the vendor have a business continuity plan they will share for your review?
      • Is the vendor operating on old hardware that may be out of warranty or at end of life?
      • Is the vendor operating on older software or shareware that may lack the necessary patches?
      • Does the vendor self-audit, or do they use a vetted third-party audit firm to issue a SOC report annually?
      • Does the vendor have sufficient personnel in acceptable regions to support your operations?
      • Is the vendor willing to make concessions on contractual protections, or are they only offering “one-sided” agreements with “as-is” warranties?

      Operational risks

      Not knowing where your risks come from creates additional risks to operations.

      • Supply chain disruptions and global shortages.
        • Geopolitical disruptions and natural disasters have caused unprecedented interruptions to business. Do you know where your critical vendors are getting their supplies? Are you aware of their business continuity plans to accommodate for those interruptions?
      • Poor vendor performance.
        • Organizations need to understand where vendors are acting in their operations and manage the impact of replacing that vendor and cutting their losses rather than continuing to throw good money away after a bad performance.
      • Vendor acquisitions.
        • A lot of acquisition is going on in the market today. Large companies are buying competitors, imposing new terms on customers, or removing competing products from the market. Understand your options if a vendor is acquired by a company with which you do not wish to be in a relationship.

      It is important to identify where potential risks to your operations may come from to manage and potentially eliminate them from impacting your organization.

      Info-Tech Insight

      Most organizations realize that their vendors could operationally affect them if an incident occurs. Still, they fail to follow the chain of events that might arise from those incidents to understand the impact fully.

      Prepare your vendor risk management for success

      Due diligence will enable successful outcomes.

      1. Obtain top-level buy-in; it is critical to success.
      2. Build enterprise risk management (ERM) through incremental improvement.
      3. Focus initial efforts on the “big wins” to prove the process works.
      4. Use existing resources.
      5. Build on any risk management activities that already exist in the organization.
      6. Socialize ERM throughout the organization to gain additional buy‑in.
      7. Normalize the process long term with ongoing updates and continuing education for the organization.

      How to assess third-party operational risk

      1. Review Organizational Operations

        Understand the organization’s operational risks to prepare for the “what if” game exercise.
      2. Identify and Understand Potential Operational Risks

        Play the “what if” game with the right people at the table.
      3. Create a Risk Profile Packet for Leadership

        Pull all the information together in a presentation document.
      4. Validate the Risks

        Work with leadership to ensure that the proposed risks are in line with their thoughts.
      5. Plan to Manage the Risks

        Lower the overall risk potential by putting mitigations in place.
      6. Communicate the Plan

        It is important not only to have a plan but also to socialize it in the organization for awareness.
      7. Enact the Plan

        Once the plan is finalized and socialized, put it in place with continued monitoring for success.

      Insight summary

      Operational risk impacts often come from unexpected places and have unforeseen impacts. Knowing where your vendors place in critical business processes and those vendors' business continuity plans concerning your organization should be a priority for those who manage the vendors.

      Insight 1

      Organizations fail to plan for vendor acquisitions appropriately.

      Vendors routinely get acquired in the IT space. Does your organization have appropriate safeguards from inadvertently entering a negative relationship? Do you have plans around replacing critical vendors purchased in such a manner?

      Insight 2

      Organizations often fail to understand how they factor into a vendor’s business continuity plan.

      If one of your critical vendors goes down, do you know how they intend to re-establish business? Do you know how you factor into their priorities?

      Insight 3

      Organizations need to have a comprehensive understanding of how their vendor-managed systems integrate with Operations.

      Do you understand where in the business processes vendor-supported systems lie? Do you have contingencies around disruptions that account for those pieces missing from the process?

      Identifying operational vendor risk

      Who should be included in the discussion

      • While it is true that executive-level leadership defines the strategy for an organization, it is vital for those making decisions to make informed decisions.
      • Getting input from operational experts at your organization will enhance your organization's long-term potential for success.
      • Involving those who not only directly manage vendors but also understand your business processes will aid in determining the forward path for relationships with your current vendors and identifying new emerging potential partners.

      See the blueprint Build an IT Risk Management Program

      Review your operational plans for new risks on a regular basis.

      Keep in mind Risk = Likelihood x Impact (R=L*I).

      Impact (I) tends to remain the same, while Likelihood (L) is becoming closer to 100% as threat actors become more prevalent

      Managing vendor operational risk impacts

      What can we realistically do about the risks?

      • Review vendors’ business continuity plans and disaster recovery testing.
        • Understand your priority in their plans.
      • Institute proper contract lifecycle management.
        • Make sure to follow corporate due diligence and risk assessment policies and procedures.
        • Failure to do so consistently can be a recipe for disaster.
      • Develop IT governance and change control.
      • Introduce continual risk assessment to monitor the relevant vendor markets.
        • Regularly review your operational plans for new risks and evolving likelihoods.
        • Risk = Likelihood x Impact (R=L*I).
          • Impact (I) tends to remain the same and be well understood, while Likelihood (L) may often be considered 100%.
      • Be adaptable and allow for innovations that arise from the current needs.
        • Capture lessons learned from prior incidents to improve over time and adjust your plans accordingly.

      Organizations need to review their organizational risk plans, considering the placement of vendors in their operations.

      Pandemics, extreme weather, and wars that affect global supply chains are current realities, not unlikely scenarios.

      Ongoing improvement

      Incorporating lessons learned

      • Over time, despite everyone’s best observations and plans, incidents will catch us off guard.
      • When it happens, follow your incident response plans and act accordingly.
      • An essential step is to document what worked and what did not – collectively known as the “lessons learned.”
      • Use the lessons learned document to devise, incorporate, and enact a better risk management process.

      Sometimes disasters occur despite our best plans to manage them.

      When this happens, it is important to document the lessons learned and improve our plans going forward.

      The "what if" game

      1-3 hours

      Vendor management professionals are in an excellent position to help senior leadership identify and pull together resources across the organization to determine potential risks. By playing the "what if" game and asking probing questions to draw out – or eliminate – possible adverse outcomes, everyone involved adds their insight into parts of the organization to gather a comprehensive picture of potential impacts.

      • Break into smaller groups (or if too small, continue as a single group).
      • Use the Operational Risk Impact Tool to prompt discussion on potential risks. Keep this discussion flowing organically to explore all potentials but manage the overall process to keep the discussion pertinent and on track.
      • Collect the outputs and ask the subject matter experts (SMEs) for management options for each one in order to present a comprehensive risk strategy. You will use this to educate senior leadership so that they can make an informed decision to accept or reject the solution.

      Download the Operational Risk Impact Tool

      Input

      • List of identified potential risk scenarios scored by likelihood and operational impact
      • List of potential management of the scenarios to reduce the risk

      Output

      • Comprehensive operational risk profile on the specific vendor solution

      Materials

      • Whiteboard/flip charts
      • Operational Risk Impact Tool to help drive discussion

      Participants

      • Vendor Management – Coordinator
      • Organizational Leadership
      • Operations Experts (SMEs)
      • Legal/Compliance/Risk Manager

      High risk example from tool

      Sample Questions to Ask to Identify Impacts. Lists questions impact score, weight, question and comments or notes.

      Being overly reliant on a single talented individual can impose risk to your operations. Make sure you include resiliency in your skill sets for critical business practices.

      Impact score and level. Each score for impacts are unique to the organization.

      Low risk example from tool

      Sample Questions to Ask to Identify Impacts. Lists questions impact score, weight, question and comments or notes. Impact score and level. Each score for impacts are unique to the organization.

      Summary

      Seek to understand all aspects of your operations.

      • Organizations need to understand and map out where vendors are critical to their operations.
      • Those organizations that consistently follow their established risk assessment and due diligence processes will be better positioned to avoid disasters.
      • Bring the right people to the table to outline potential risks in the market and your organization.
      • Understand how your vendors prioritize your organization in their business continuity processes.
      • Incorporate “lessons learned” from prior incidents into your risk management process to build better plans for future issues.

      Organizations must evolve their operational risk assessments considering their vendor portfolio.

      Ongoing monitoring of the market and the vendors tied to company operations is imperative to avoiding disaster.

      Related Info-Tech Research

      Identify and Manage Financial Risk Impacts on Your Organization

      • Vendor management practices educate organizations on the different potential financial impacts that vendors may incur and suggest systems to help manage them.
      • Standardize your processes for identifying and monitoring vendor risks to manage financial impacts with our Financial Risk Impact Tool.

      Identify and Manage Reputational Risk Impacts on Your Organization

      • Vendor management practices educate organizations on the different potential risks to vendors in your market and suggest creative and alternative ways to avoid and help manage them.
      • Standardize your processes for identifying and monitoring vendor risks to manage potential impacts on your reputation and brand with our Reputational Risk Impact Tool.

      Identify and Manage Strategic Risk Impacts on Your Organization

      • Vendor management practices educate organizations on the different potential risks to vendors in your market and suggest creative and alternative ways to avoid and help manage them.
      • Standardize your processes for identifying and monitoring vendor risks to manage potential impacts on your strategic plan with our Strategic Risk Impact Tool.

      Bibliography

      “Weak Cybersecurity is taking a toll on Small Businesses.” Tripwire. August 7, 2022.

      SecureLink 2022 White Paper SL_Page_EA+PAM (rocketcdn.me)

      Member Poll March 2021 "Guide: Evolving Work Environments Impact of Covid-19 on Profile and Management of Third Parties.“ Shared Assessments. March 2021.

      “Operational Risk.” Wikipedia.

      Tonello, Matteo. “Strategic Risk Management: A Primer for Directors.” Harvard Law School Forum on Corporate Governance, August 23, 2012.

      Frigo, Mark L., and Richard J. Anderson. “Embracing Enterprise Risk Management: Practical Approaches for Getting Started.” COSO, 2011.

      Start Making Data-Driven People Decisions

      • Buy Link or Shortcode: {j2store}427|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Leadership Development Programs
      • Parent Category Link: /leadership-development-programs
      • Ninety-one percent of IT leaders believe that analytics is important for talent management but 59% use no workforce analytics at all, although those who use analytics are much more effective than those who don't.
      • The higher the level of analytics used, the higher the level of effectiveness of the department as a whole.

      Our Advice

      Critical Insight

      • You don't need advanced metrics and analytics to see a return on people data. Begin by getting a strong foundation in place and showing the ROI on a pilot project.
      • Complex analyses will never make up for inadequate data quality. Spend the time up front to audit and improve data quality if necessary, no matter which stage of analytics proficiency you are at.
      • Ensure you collect and analyze only data that is essential to your decision making. More is not better, and excess data can detract from the overall impact of analytics.

      Impact and Result

      • Build a small-scale foundational pilot, which will allow you to demonstrate feasibility, refine your costs estimate, and show the ROI on people analytics for your budgeting meeting.
      • Drive organizational change incrementally by identifying and communicating with the stakeholders for your people analytics pilot.
      • Choose basic analytics suitable for organizations of all sizes and understand the building blocks of data quality to support more further analytics down the line.

      Start Making Data-Driven People Decisions Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should strategically apply people analytics to your IT talent management.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Define the problem and apply the checklist

      From choosing the right data for the right problem to evaluating your progress toward data-driven people decisions, follow these steps to build your foundation to people analytics.

      • Start Making Data-Driven People Decisions – Phase 1: Define the Problem and Apply the Checklist
      • People Analytics Strategy Template
      • Talent Metrics Library
      [infographic]

      Create and Manage Enterprise Data Models

      • Buy Link or Shortcode: {j2store}340|cart{/j2store}
      • member rating overall impact: 9.2/10 Overall Impact
      • member rating average dollars saved: $7,263 Average $ Saved
      • member rating average days saved: 16 Average Days Saved
      • Parent Category Name: Data Management
      • Parent Category Link: /data-management
      • Business executives don’t understand the value of Conceptual and Logical Data Models and how they define their data assets.
      • Data, like mercury, is difficult to manage and contain.
      • IT needs to justify the time and cost of developing and maintaining Data Models.
      • Data as an asset is only perceived from a physical point of view, and the metadata that provides context and definition is often ignored.

      Our Advice

      Critical Insight

      • Data Models tell the story of the organization and its data in pictures to be used by a business as a tool to evolve the business capabilities and processes.
      • Data Architecture and Data Modeling have different purposes and should be represented as two distinct processes within the software development lifecycle (SDLC).
      • The Conceptual Model provides a quick win for both business and IT because it can convey abstract business concepts and thereby compartmentalize the problem space.

      Impact and Result

      • A Conceptual Model can be used to define the semantics and relationships for your analytical layer.
        • It provides a visual representation of your data in the semantics of business.
        • It acts as the anchor point for all data lineages.
        • It can be used by business users and IT for data warehouse and analytical planning.
        • It provides the taxonomies for data access profiles.
        • It acts as the basis for your Enterprise Logical and Message Models.

      Create and Manage Enterprise Data Models Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should create enterprise data models, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Setting the stage

      Prepare your environment for data architecture.

      • Enterprise Data Models

      2. Revisit your SDLC

      Revisit your SDLC to embed data architecture.

      • Enterprise Architecture Tool Selection

      3. Develop a Conceptual Model

      Create and maintain your Conceptual Data Model via an iterative process.

      4. Data Modeling Playbook

      View the main deliverable with sample models.

      • Data Modeling Playbook
      [infographic]

      Workshop: Create and Manage Enterprise Data Models

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Establish the Data Architecture Practice

      The Purpose

      Understand the context and goals of data architecture in your organization.

      Key Benefits Achieved

      A foundation for your data architecture practice.

      Activities

      1.1 Review the business context.

      1.2 Obtain business commitment and expectations for data architecture.

      1.3 Define data architecture as a discipline, its role, and the deliverables.

      1.4 Revisit your SDLC to embed data architecture.

      1.5 Modeling tool acquisition if required.

      Outputs

      Data Architecture vision and mission and governance.

      Revised SDLC to include data architecture.

      Staffing strategy.

      Data Architecture engagement protocol.

      Installed modeling tool.

      2 Business Architecture and Domain Modeling

      The Purpose

      Identify the concepts and domains that will inform your data models.

      Key Benefits Achieved

      Defined concepts for your data models.

      Activities

      2.1 Revisit business architecture output.

      2.2 Business domain selection.

      2.3 Identify business concepts.

      2.4 Organize and group of business concepts.

      2.5 Build the Business Data Glossary.

      Outputs

      List of defined and documented entities for the selected.

      Practice in the use of capability and business process models to identify key data concepts.

      Practice the domain modeling process of grouping and defining your bounded contexts.

      3 Harvesting Reference Models

      The Purpose

      Harvest reference models for your data architecture.

      Key Benefits Achieved

      Reference models selected.

      Activities

      3.1 Reference model selection.

      3.2 Exploring and searching the reference model.

      3.3 Harvesting strategies and maintaining linkage.

      3.4 Extending the conceptual and logical models.

      Outputs

      Established and practiced steps to extend the conceptual or logical model from the reference model while maintaining lineage.

      4 Harvesting Existing Data Artifacts

      The Purpose

      Gather more information to create your data models.

      Key Benefits Achieved

      Remaining steps and materials to build your data models.

      Activities

      4.1 Use your data inventory to select source models.

      4.2 Match semantics.

      4.3 Maintain lineage between BDG and existing sources.

      4.4 Select and harvest attributes.

      4.5 Define modeling standards.

      Outputs

      List of different methods to reverse engineer existing models.

      Practiced steps to extend the logical model from existing models.

      Report examples.

      5 Next Steps and Wrap-Up (offsite)

      The Purpose

      Wrap up the workshop and set your data models up for future success.

      Key Benefits Achieved

      Understanding of functions and processes that will use the data models.

      Activities

      5.1 Institutionalize data architecture practices, standards, and procedures.

      5.2 Exploit and extend the use of the Conceptual model in the organization.

      Outputs

      Data governance policies, standards, and procedures for data architecture.

      List of business function and processes that will utilize the Conceptual model.

      Application Maintenance

      • Buy Link or Shortcode: {j2store}30|cart{/j2store}
      • Related Products: {j2store}30|crosssells{/j2store}
      • member rating overall impact: 10.0/10
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Applications
      • Parent Category Link: /applications

      The challenge

      • If you work with application maintenance or operations teams that handle the "run" of your applications, you may find that the sheer volume and variety of requests create large backlogs.
      • Your business and product owners may want scrum or DevOps teams to work on new functionality rather than spend effort on lifecycle management.
      • Increasing complexity and increasing reliance on technology may create unrealistic expectations for your maintenance teams. Business applications must be available around the clock, and new feature roadmaps cannot be side-tracked by maintenance.

      Our advice

      Insight

      • Improving maintenance focus may mean doing less work but create more value. Your teams need to be realistic about what commitments they take—balance maintenance with business value and risk levels.
      • Treat maintenance the same as any other development practice. Use the same intake and prioritization practices. Uphold the same quality standards.

      Impact and results 

      • Justify the necessity of streamlined and regular maintenance. Understand each stakeholder's objectives and concerns, validate them against your staff's current state, processes, and technologies involved.
      • Maintenance and risk go hand in hand. And the business wants to move forward all the time as well. Strengthen your prioritization practice. Use a holistic view of the business and technical impacts, risks, urgencies across the maintenance needs and requests. That allows you to justify their respective positions in the overall development backlog. Identify opportunities to bring some requirements and features together.
      • Build a repeatable process with appropriate governance around it. Ensure that people know their roles and responsibilities and are held accountable.
      • Instill development best-practices into your maintenance processes.

      The roadmap

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      Get started.

      Read our executive brief to understand everyday struggles regarding application maintenance, the root causes, and our methodology to overcome these. We show you how we can support you.

      Understand your maintenance priorities

      Identify your stakeholders and understand their drivers.

      • Streamline Application Maintenance – Phase 1: Assess the Current Maintenance Landscape (ppt)
      • Application Maintenance Operating Model Template (doc)
      • Application Maintenance Resource Capacity Assessment (xls)
      • Application Maintenance Maturity Assessment (xls)

      Define and employ maintenance governance

      Identify the right level of governance appropriate to your company and business context for your application maintenance. That ensures that people uphold standards across maintenance practices.

      • Streamline Application Maintenance – Phase 2: Develop a Maintenance Release Schedule (ppt)

      Enhance your prioritization practices

      Most companies cannot do everything for all applications and systems. Build your maintenance triage and prioritization rules to safeguard your company, maximize business value generation and IT risks and requirements.

      • Streamline Application Maintenance – Phase 3: Optimize Maintenance Capabilities (ppt)

      Streamline your maintenance delivery

      Define quality standards in maintenance practices. Enforce these in alignment with the governance you have set up. Show a high degree of transparency and open discussions on development challenges.

      • Streamline Application Maintenance – Phase 4: Streamline Maintenance Delivery (ppt)
      • Application Maintenance Business Case Presentation Document (ppt)

       

       

      Domino – Maintain, Commit to, or Vacate?

      If you have a Domino/Notes footprint that is embedded within your business units and business processes and is taxing your support organization, you may have met resistance from the business and been asked to help the organization migrate away from the Lotus Notes platform. The Lotus Notes platform was long used by technology and businesses and a multipurpose solution that, over the years, became embedded within core business applications and processes.

      Our Advice

      Critical Insight

      For organizations that are struggling to understand their options for the Domino platform, the depth of business process usage is typically the biggest operational obstacle. Migrating off the Domino platform is a difficult option for most organizations due to business process and application complexity. In addition, migrating clients have to resolve the challenges with more than one replaceable solution.

      Impact and Result

      The most common tactic is for the organization to better understand their Domino migration options and adopt an application rationalization strategy for the Domino applications entrenched within the business. Options include retiring, replatforming, migrating, or staying with your Domino platform.

      Domino – Maintain, Commit to, or Vacate? Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Domino – Maintain, Commit to, or Vacate? – A brief deck that outlines key migration options for HCL Domino platforms.

      This blueprint will help you assess the fit, purpose, and price of Domino options; develop strategies for overcoming potential challenges; and determine the future of Domino for your organization.

      • Domino – Maintain, Commit to, or Vacate? Storyboard

      2. Application Rationalization Tool – A tool to understand your business-developed applications, their importance to business process, and the potential underlying financial impact.

      Use this tool to input the outcomes of your various application assessments.

      • Application Rationalization Tool

      Infographic

      Further reading

      Domino – Maintain, Commit to, or Vacate?

      Lotus Domino still lives, and you have options for migrating away from or remaining with the platform.

      Executive Summary

      Info-Tech Insight

      “HCL announced that they have somewhere in the region of 15,000 Domino customers worldwide, and also claimed that that number is growing. They also said that 42% of their customers are already on v11 of Domino, and that in the year or so since that version was released, it’s been downloaded 78,000 times. All of which suggests that the Domino platform is, in fact, alive and well.”
      – Nigel Cheshire in Team Studio

      Your Challenge

      You have a Domino/Notes footprint embedded within your business units and business processes. This is taxing your support organization; you are meeting resistance from the business, and you are now asked to help the organization migrate away from the Lotus Notes platform. The Lotus Notes platform was long used by technology and businesses as a multipurpose solution that, over the years, became embedded within core business applications and processes.

      Common Obstacles

      For organizations that are struggling to understand their options for the Domino platform, the depth of business process usage is typically the biggest operational obstacle. Migrating off the Domino platform is a difficult option for most organizations due to business process and application complexity. In addition, migrating clients have to resolve the challenges with more than one replaceable solution.

      Info-Tech Approach

      The most common tactic is for the organization to better understand their Domino migration options and adopt an application rationalization strategy for the Domino applications entrenched within the business. Options include retiring, replatforming, migrating, or staying with your Domino platform.

      Review

      Is “Lotus” Domino still alive?

      Problem statement

      The number of member engagements with customers regarding the Domino platform has, as you might imagine, dwindled in the past couple of years. While many members have exited the platform, there are still many members and organizations that have entered a long exit program, but with how embedded Domino is in business processes, the migration has slowed and been met with resistance. Some organizations had replatformed the applications but found that the replacement target state was inadequate and introduced friction because the new solution was not a low-code/business-user-driven environment. This resulted in returning the Domino platform to production and working through a strategy to maintain the environment.

      This research is designed for:

      • IT strategic direction decision-makers
      • IT managers responsible for an existing Domino platform
      • Organizations evaluating migration options for mission-critical applications running on Domino

      This research will help you:

      1. Evaluate migration options.
      2. Assess the fit and purpose.
      3. Consider strategies for overcoming potential challenges.
      4. Determine the future of this platform for your organization.

      The “everything may work” scenario

      Adopt and expand

      Believe it or not, Domino and Notes are still options to consider when determining a migration strategy. With HCL still committed to the platform, there are options organizations should seek to better understand rather than assuming SharePoint will solve all. In our research, we consider:

      Importance to current business processes

      • Importance of use
      • Complexity in migrations
      • Choosing a new platform

      Available tools to facilitate

      • Talent/access to skills
      • Economies of scale/lower cost at scale
      • Access to technology

      Info-Tech Insight

      With multiple options to consider, take the time to clearly understand the application rationalization process within your decision making.

      • Archive/retire
      • Application migration
      • Application replatform
      • Stay right where you are

      Eliminate your bias – consider the advantages

      “There is a lot of bias toward Domino; decisions are being made by individuals who know very little about Domino and more importantly, they do not know how it impacts business environment.”

      – Rob Salerno, Founder & CTO, Rivet Technology Partners

      Domino advantages include:

      Modern Cloud & Application

      • No-code/low-code technology

      Business-Managed Application

      • Business written and supported
      • Embrace the business support model
      • Enterprise class application

      Leverage the Application Taxonomy & Build

      • A rapid application development platform
      • Develop skill with HCL training

      HCL Domino is a supported and developed platform

      Why consider HCL?

      • Consider scheduling a Roadmap Session with HCL. This is an opportunity to leverage any value in the mission and brand of your organization to gain insights or support from HCL.
      • Existing Domino customers are not the only entities seeking certainty with the platform. Software solution providers that support enterprise IT infrastructure ecosystems (backup, for example) will also be seeking clarity for the future of the platform. HCL will be managing these relationships through the channel/partner management programs, but our observations indicate that Domino integrations are scarce.
      • HCL Domino should be well positioned feature-wise to support low-code/NoSQL demands for enterprises and citizen developers.

      Visualize Your Application Roadmap

      1. Focus on the application portfolio and crafting a roadmap for rationalization.
        • The process is intended to help you determine each application’s functional and technical adequacy for the business process that it supports.
      2. Document your findings on respective application capability heatmaps.
        • This drives your organization to a determination of application dispositions and provides a tool to output various dispositions for you as a roadmap.
      3. Sort the application portfolio into a disposition status (keep, replatform, retire, consolidate, etc.)
        • This information will be an input into any cloud migration or modernization as well as consolidation of the infrastructure, licenses, and support for them.

      Our external support perspective

      by Darin Stahl

      Member Feedback

      • Some members who have remaining Domino applications in production – while the retire, replatform, consolidate, or stay strategy is playing out – have concerns about the challenges with ongoing support and resources required for the platform. In those cases, some have engaged external services providers to augment staff or take over as managed services.
      • While there could be existing support resources (in house or on retainer), the member might consider approaching an external provider who could help backstop the single resource or even provide some help with the exit strategies. At this point, the conversation would be helpful in any case. One of our members engaged an external provider in a Statement of Work for IBM Domino Administration focused on one-time events, Tier 1/Tier 2 support, and custom ad hoc requests.
      • The augmentation with the managed services enabled the member to shift key internal resources to a focus on executing the exit strategies (replatform, retire, consolidate), since the business knowledge was key to that success.
      • The member also very aggressively governed the Domino environment support needs to truly technical issues/maintenance of known and supported functionality rather than coding new features (and increasing risk and cost in a migration down the road) – in short, freezing new features and functionality unless required for legal compliance or health and safety.
      • There obviously are other providers, but at this point Info-Tech no longer maintains a market view or scan of those related to Domino due to low member demand.

      Domino database assessments

      Consider the database.

      • Domino database assessments should be informed through the lens of a multi-value database, like jBase, or an object system.
      • The assessment of the databases, often led by relational database subject matter experts grounded in normalized databases, can be a struggle since Notes databases must be denormalized.
      Key/Value Column

      Use case: Heavily accessed, rarely updated, large amounts of data
      Data Model: Values are stored in a hash table of keys.
      Fast access to small data values, but querying is slow
      Processor friendly
      Based on amazon's Dynamo paper
      Example: Project Voldemort used by LinkedIn

      this is a Key/Value example

      Use case: High availability, multiple data centers
      Data Model: Storage blocks of data are contained in columns
      Handles size well
      Based on Google's BigTable
      Example: Hadoop/Hbase used by Facebook and Yahoo

      This is a Column Example
      Document Graph

      Use case: Rapid development, Web and programmer friendly
      Data Model: Stores documents made up of tagged elements. Uses Key/Value collections
      Better query abilities than Key/Value databases.
      Inspired by Lotus Notes.
      Example: CouchDB used by BBC

      This is a Document Example

      Use case: Best at dealing with complexity and relationships/networks
      Data model: Nodes and relationships.
      Data is processed quickly
      Inspired by Euler and graph theory
      Can easily evolve schemas
      Example: Neo4j

      This is a Graph Example

      Understand your options

      Archive/Retire

      Store the application data in a long-term repository with the means to locate and read it for regulatory and compliance purposes.

      Migrate

      Migrate to a new version of the application, facilitating the process of moving software applications from one computing environment to another.

      Replatform

      Replatforming is an option for transitioning an existing Domino application to a new modern platform (i.e. cloud) to leverage the benefits of a modern deployment model.

      Stay

      Review the current Domino platform roadmap and understand HCL’s support model. Keep the application within the Domino platform.

      Archive/retire

      Retire the application, storing the application data in a long-term repository.

      Abstract

      The most common approach is to build the required functionality in whatever new application/solution is selected, then archive the old data in PDFs and documents.

      Typically this involves archiving the data and leveraging Microsoft SharePoint and the new collaborative solutions, likely in conjunction with other software-as-a-service (SaaS) solutions.

      Advantages

      • Reduce support cost.
      • Consolidate applications.
      • Reduce risk.
      • Reduce compliance and security concerns.
      • Improve business processes.

      Considerations

      • Application transformation
      • eDiscovery costs
      • Legal implications
      • Compliance implications
      • Business process dependencies

      Info-Tech Insights

      Be aware of the costs associated with archiving. The more you archive, the more it will cost you.

      Application migration

      Migrate to a new version of the application

      Abstract

      An application migration is the managed process of migrating or moving applications (software) from one infrastructure environment to another.

      This can include migrating applications from one data center to another data center, from a data center to a cloud provider, or from a company’s on-premises system to a cloud provider’s infrastructure.

      Advantages

      • Reduce hardware costs.
      • Leverage cloud technologies.
      • Improve scalability.
      • Improve disaster recovery.
      • Improve application security.

      Considerations

      • Data extraction, starting from the document databases in NSF format and including security settings about users and groups granted to read and write single documents, which is a powerful feature of Lotus Domino documents.
      • File extraction, starting from the document databases in NSF format, which can contain attachments and RTF documents and embedded files.
      • Design of the final relational database structure; this activity should be carried out without taking into account the original structure of the data in Domino files or the data conversion and loading, from the extracted format to the final model.
      • Design and development of the target-state custom applications based on the new data model and the new selected development platform.

      Application replatform

      Transition an existing Domino application to a new modern platform

      Abstract

      This type of arrangement is typically part of an application migration or transformation. In this model, client can “replatform” the application into an off-premises hosted provider platform. This would yield many benefits of cloud but in a different scaling capacity as experienced with commodity workloads (e.g. Windows, Linux) and the associated application.

      Two challenges are particularly significant when migrating or replatforming Domino applications:

      • The application functionality/value must be reproduced/replaced with not one but many applications, either through custom coding or a commercial-off-the-shelf/SaaS solution.
      • Notes “databases” are not relational databases and will not migrate simply to an SQL database while retaining the same business value. Notes databases are essentially NoSQL repositories and are difficult to normalize.

      Advantages

      • Leverage cloud technologies.
      • Improve scalability.
      • Align to a SharePoint platform.
      • Improve disaster recovery.
      • Improve application security.

      Considerations

      • Application replatform resource effort
      • Network bandwidth
      • New platform terms and conditions
      • Secure connectivity and communication
      • New platform security and compliance
      • Degree of complexity

      Info-Tech Insights

      There is a difference between a migration and a replatform application strategy. Determine which solution aligns to the application requirements.

      Stay with HCL

      Stay with HCL, understanding its future commitment to the platform.

      Abstract

      Following the announced acquisition of IBM Domino and up until around December 2019, HCL had published no future roadmap for the platform. The public-facing information/website at the time stated that HCL acquired “the product family and key lab services to deliver professional services.” Again, there was no mention or emphasis on upcoming new features for the platform. The product offering on their website at the time stated that HCL would leverage its services expertise to advise clients and push applications into four buckets:

      1. Replatform
      2. Retire
      3. Move to cloud
      4. Modernize

      That public-facing messaging changed with release 11.0, which had references to IBM rebranded to HCL for the Notes and Domino product – along with fixes already inflight. More information can be found on HCL’s FAQ page.

      Advantages

      • Known environment
      • Domino is a supported platform
      • Domino is a developed platform
      • No-code/low-code optimization
      • Business developed applications
      • Rapid application framework

      This is the HCL Domino Logo

      Understand your tools

      Many tools are available to help evaluate or migrate your Domino Platform. Here are a few common tools for you to consider.

      Notes Archiving & Notes to SharePoint

      Summary of Vendor

      “SWING Software delivers content transformation and archiving software to over 1,000 organizations worldwide. Our solutions uniquely combine key collaborative platforms and standard document formats, making document production, publishing, and archiving processes more efficient.”*

      Tools

      Lotus Notes Data Migration and Archiving: Preserve historical data outside of Notes and Domino

      Lotus Note Migration: Replacing Lotus Notes. Boost your migration by detaching historical data from Lotus Notes and Domino.

      Headquarters

      Croatia

      Best fit

      • Application archive and retire
      • Migration to SharePoint

      This is an image of the SwingSoftware Logo

      * swingsoftware.com

      Domino Migration to SharePoint

      Summary of Vendor

      “Providing leading solutions, resources, and expertise to help your organization transform its collaborative environment.”*

      Tools

      Notes Domino Migration Solutions: Rivit’s industry-leading solutions and hardened migration practice will help you eliminate Notes Domino once and for all.

      Rivive Me: Migrate Notes Domino applications to an enterprise web application

      Headquarters

      Canada

      Best fit

      • Application Archive & Retire
      • Migration to SharePoint

      This is an image of the RiVit Logo

      * rivit.ca

      Lotus Notes to M365

      Summary of Vendor

      “More than 300 organizations across 40+ countries trust skybow to build no-code/no-compromise business applications & processes, and skybow’s community of customers, partners, and experts grows every day.”*

      Tools

      SkyBow Studio: The low-code platform fully integrated into Microsoft 365

      Headquarters:

      Switzerland

      Best fit

      • Application Archive & Retire
      • Migration to SharePoint

      This is an image of the SkyBow Logo

      * skybow.com | About skybow

      Notes to SharePoint Migration

      Summary of Vendor

      “CIMtrek is a global software company headquartered in the UK. Our mission is to develop user-friendly, cost-effective technology solutions and services to help companies modernize their HCL Domino/Notes® application landscape and support their legacy COBOL applications.”*

      Tools

      CIMtrek SharePoint Migrator: Reduce the time and cost of migrating your IBM® Lotus Notes® applications to Office 365, SharePoint online, and SharePoint on premises.

      Headquarters

      United Kingdom

      Best fit

      • Application replatform
      • Migration to SharePoint

      This is an image of the CIMtrek Logo

      * cimtrek.com | About CIMtrek

      Domino replatform/Rapid application selection framework

      Summary of Vendor

      “4WS.Platform is a rapid application development tool used to quickly create multi-channel applications including web and mobile applications.”*

      Tools

      4WS.Platform is available in two editions: Community and Enterprise.
      The Platform Enterprise Edition, allows access with an optional support pack.

      4WS.Platform’s technical support provides support services to the users through support contracts and agreements.

      The platform is a subscription support services for companies using the product which will allow customers to benefit from the knowledge of 4WS.Platform’s technical experts.

      Headquarters

      Italy

      Best fit

      • Application replatform

      This is an image of the 4WS PLATFORM Logo

      * 4wsplatform.org

      Activity

      Understand your Domino options

      Application Rationalization Exercise

      Info-Tech Insight

      Application rationalization is the perfect exercise to fully understand your business-developed applications, their importance to business process, and the potential underlying financial impact.

      This activity involves the following participants:

      • IT strategic direction decision-makers.
      • IT managers responsible for an existing Domino platform
      • Organizations evaluating platforms for mission-critical applications.

      Outcomes of this step:

      • Completed Application Rationalization Tool

      Application rationalization exercise

      Use this Application Rationalization Tool to input the outcomes of your various application assessments

      In the Application Entry tab:

      • Input your application inventory or subset of apps you intend to rationalize, along with some basic information for your apps.

      In the Business Value & TCO Comparison tab, determine rationalization priorities.

      • Input your business value scores and total cost of ownership (TCO) of applications.
      • Review the results of this analysis to determine which apps should require additional analysis and which dispositions should be prioritized.

      In the Disposition Selection tab:

      • Add to or adapt our list of dispositions as appropriate.

      In the Rationalization Inputs tab:

      • Add or adapt the disposition criteria of your application rationalization framework as appropriate.
      • Input the results of your various assessments for each application.

      In the Disposition Settings tab:

      • Add or adapt settings that generate recommended dispositions based on your rationalization inputs.

      In the Disposition Recommendations tab:

      • Review and compare the rationalization results and confirm if dispositions are appropriate for your strategy.

      In the Timeline Considerations tab:

      • Enter the estimated timeline for when you execute your dispositions.

      In the Portfolio Roadmap tab:

      • Review and present your roadmap and rationalization results.

      Follow the instructions to generate recommended dispositions and populate an application portfolio roadmap.

      This image depicts a scatter plot graph where the X axis is labeled Business Value, and the Y Axis is labeled Cost. On the graph, the following datapoints are displayed: SF; HRIS; ERP; ALM; B; A; C; ODP; SAS

      Info-Tech Insight

      Watch out for misleading scores that result from poorly designed criteria weightings.

      Related Info-Tech Research

      Build an Application Rationalization Framework

      Manage your application portfolio to minimize risk and maximize value.

      Embrace Business-Managed Applications

      Empower the business to implement their own applications with a trusted business-IT relationship.

      Satisfy Digital End Users With Low- and No-Code

      Extend IT, automation, and digital capabilities to the business with the right tools, good governance, and trusted organizational relationships.

      Maximize the Benefits from Enterprise Applications with a Center of Excellence

      Optimize your organization’s enterprise application capabilities with a refined and scalable methodology.

      Drive Successful Sourcing Outcomes With a Robust RFP Process

      Leverage your vendor sourcing process to get better results.

      Research Authors

      Darin Stahl, Principal Research Advisor, Info-Tech Research Group

      Darin Stahl, Principal Research Advisor,
      Info-Tech Research Group

      Darin is a Principal Research Advisor within the Infrastructure practice, leveraging 38+ years of experience. His areas of focus include IT operations management, service desk, infrastructure outsourcing, managed services, cloud infrastructure, DRP/BCP, printer management, managed print services, application performance monitoring, managed FTP, and non-commodity servers (zSeries, mainframe, IBM i, AIX, Power PC).

      Troy Cheeseman, Practice Lead, Info-Tech Research Group

      Troy Cheeseman, Practice Lead,
      Info-Tech Research Group

      Troy has over 24 years of experience and has championed large enterprise-wide technology transformation programs, remote/home office collaboration and remote work strategies, BCP, IT DRP, IT operations and expense management programs, international right placement initiatives, and large technology transformation initiatives (M&A). Additionally, he has deep experience working with IT solution providers and technology (cloud) startups.

      Research Contributors

      Rob Salerno, Founder & CTO, Rivit Technology Partners

      Rob Salerno, Founder & CTO, Rivit Technology Partners

      Rob is the Founder and Chief Technology Strategist for Rivit Technology Partners. Rivit is a system integrator that delivers unique IT solutions. Rivit is known for its REVIVE migration strategy which helps companies leave legacy platforms (such as Domino) or move between versions of software. Rivit is the developer of the DCOM Application Archiving solution.

      Bibliography

      Cheshire, Nigel. “Domino v12 Launch Keeps HCL Product Strategy On Track.” Team Studio, 19 July 2021. Web.

      “Is LowCode/NoCode the best platform for you?” Rivit Technology Partners, 15 July 2021. Web.

      McCracken, Harry. “Lotus: Farewell to a Once-Great Tech Brand.” TIME, 20 Nov. 2012. Web.

      Sharwood, Simon. “Lotus Notes refuses to die, again, as HCL debuts Domino 12.” The Register, 8 June 2021. Web.

      Woodie, Alex. “Domino 12 Comes to IBM i.” IT Jungle, 16 Aug. 2021. Web.

      IT Strategy

      • Buy Link or Shortcode: {j2store}20|cart{/j2store}
      • Related Products: {j2store}20|crosssells{/j2store}
      • Up-Sell: {j2store}20|upsells{/j2store}
      • member rating overall impact: 9.3/10
      • member rating average dollars saved: $105,465
      • member rating average days saved: 35
      • Parent Category Name: Strategy and Governance
      • Parent Category Link: strategy-and-governance
      Success depends on IT initiatives clearly aligned to business goals.

      Configuration management

      • Buy Link or Shortcode: {j2store}4|cart{/j2store}
      • Related Products: {j2store}4|crosssells{/j2store}
      • Up-Sell: {j2store}4|upsells{/j2store}
      • Download01-Title: Harness the power of Configuration Management Executive Brief
      • Download-01: Visit Link
      • member rating overall impact: 8.0/10
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Infra and Operations
      • Parent Category Link: /infra-and-operations
      Configuration management is all about being able to manage your assets within the support processes. That means to record what you need. Not less than that, and not more either.

      Asset Management, Configuration Management, Lifecycle Management

      Select and Implement an IT PPM Solution

      • Buy Link or Shortcode: {j2store}440|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $125,999 Average $ Saved
      • member rating average days saved: 29 Average Days Saved
      • Parent Category Name: Portfolio Management
      • Parent Category Link: /portfolio-management
      • The number of IT project resources and the quantity of IT projects and tasks can no longer be recorded, prioritized, and tracked using non-commercial project portfolio management (PPM) solutions.
      • Your organization has attained a moderate level of PPM maturity.
      • You have sufficient financial and technical resources to purchase a commercial PPM solution.
      • There is a wide variety of commercial PPM solutions; different kinds of PPM solutions are more appropriate for organizations of a certain size and a certain PPM maturity level than others.

      Our Advice

      Critical Insight

      • Implementations of PPM solutions are often unsuccessful resulting in wasted time and resources; failing to achieve sustainable adoption of the tool is a widespread pain point.
      • The costs of PPM solutions do not end after the implementation and subscription invoices are paid. Have realistic expectations about the time required to use and maintain PPM solutions to ensure success.
      • PPM solutions help PMOs serve the organization’s core decision makers. Success depends on improved service to these stakeholders.

      Impact and Result

      • Using Info-Tech’s Vendor Landscape and PPM solution use cases, you will be able to make sense of the diversity of PPM solutions available in today’s market and choose the most appropriate solution for your organization’s size and level of PPM maturity.
      • Info-Tech’s blueprint for a PPM solution selection and implementation project will provide you with a variety of tools and templates.
      • A carefully planned out and executed selection and implementation process will help ensure your organization can maximize the value of your project portfolio and will allow the PMO to improve portfolio stakeholder satisfaction.

      Select and Implement an IT PPM Solution Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should implement a commercial PPM solution, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Launch the PPM solution project and collect requirements

      Create a PPM solution selection and implementation project charter and gather your organizations business and technical requirements.

      • Select and Implement a PPM Solution – Phase 1: Launch the PPM Solution Project and Collect Requirements
      • PPM Solution Project Charter Template
      • PPM Implementation Work Breakdown Structure
      • PPM Solution Requirements Gathering Tool
      • PPM Solution Cost-of-Use Estimation Tool
      • PPM Solution RFP Template
      • PPM Solution Success Metrics Workbook
      • PPM Solution Use-Case Fit Assessment Tool

      2. Select a PPM solution

      Select the most appropriate PPM solution for your organization by using Info-Tech’s PPM solution Vendor Landscape and use cases to help you create a vendor shortlist, produce an RFP, and establish evaluation criteria for ranking your shortlisted solutions.

      • Select and Implement a PPM Solution – Phase 2: Select a PPM Solution
      • PPM Vendor Shortlist & Detailed Feature Analysis Tool
      • PPM Solution Vendor Response Template
      • PPM Solution Evaluation & RFP Scoring Tool
      • PPM Solution Vendor Demo Script

      3. Plan the PPM solution implementation

      Plan a PPM solution implementation that will result in long-term sustainable adoption of the tool and that will allow the PMO to meet the needs of core project portfolio stakeholders.

      • Select and Implement a PPM Solution – Phase 3: Plan the PPM Solution Implementation
      [infographic]

      Workshop: Select and Implement an IT PPM Solution

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Launch the PPM Solution Project and Gather Requirements

      The Purpose

      Create a PPM solution selection and implementation project charter.

      Gather the business and technical requirements for the PPM solution.

      Establish clear and measurable success criteria for your PPM solution project.

      Key Benefits Achieved

      Comprehensive project plan

      Comprehensive and organized record of the various PPM solution requirements

      A record of PPM solution project goals and criteria that can be used in the future to establish the success of the project

      Activities

      1.1 Brainstorm, refine, and prioritize your PPM solution needs

      1.2 Stakeholder identification exercise

      1.3 Project charter work session

      1.4 Requirements gathering work session

      1.5 PPM solution success metrics workbook session

      Outputs

      High-level outline of PPM solution requirements

      Stakeholder consultation plan

      A draft project charter and action plan to fill in project charter gaps

      A draft requirements workbook and action plan to fill in requirement gathering gaps

      A PPM project success metrics workbook that can be used during and after the project

      2 Select a PPM Solution

      The Purpose

      Identify the PPM solutions that are most appropriate for your organization’s size and level of PPM maturity.

      Create a PPM solution and vendor shortlist.

      Create a request for proposal (RFP).

      Create a PPM solution scoring and evaluation tool.

      Key Benefits Achieved

      Knowledge of the PPM solution market and the various features available

      An informed shortlist of PPM vendors

      An organized and focused method for evaluating the often long and complex responses to the RFP that vendors provide

      The groundwork for an informed and defensible selection of a PPM solution for your organization

      Activities

      2.1 Assess the size of your organization and the level of PPM maturity to select the most appropriate use case

      2.2 PPM solution requirements and criteria ranking activity

      2.3 An RFP working session

      2.4 Build an RFP evaluation tool

      Outputs

      Identification of the most appropriate use case in Info-Tech’s Vendor Landscape

      A refined and organized list of the core features that will be included in the RFP

      A draft RFP with an action plan to fill in any RFP gaps

      An Excel tool that can be used to compare and evaluate vendors’ responses to the RFP

      3 Prepare for the PPM Solution Implementation

      The Purpose

      To think ahead to the eventual implementation of the solution that will occur once the selection phase is completed

      Key Benefits Achieved

      An understanding of key insights and steps that will help avoid mistakes resulting in poor adoption or PPM solutions that end up producing little tangible value

      Activities

      3.1 Outline high-level implementation stages

      3.2 Organizational change management strategy session

      3.3 A PPM project success metrics planning session

      Outputs

      High-level implementation tasks and milestones

      A RACI chart for core implementation tasks

      A high-level PPM solution implementation organizational change management strategy

      A RACI chart for core organizational change management tasks related to the PPM solution implementation

      A PPM project success metrics schedule and plan

      Develop Infrastructure & Operations Policies and Procedures

      • Buy Link or Shortcode: {j2store}452|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: $46,324 Average $ Saved
      • member rating average days saved: 42 Average Days Saved
      • Parent Category Name: Operations Management
      • Parent Category Link: /i-and-o-process-management
      • Time and money are wasted dealing with mistakes or missteps that should have been addressed by procedures or policies.
      • Standard operating procedures are less effective without a policy to provide a clear mandate and direction.
      • Adhering to policies is rarely a priority, as compliance often feels like an impediment to getting work done.
      • Processes aren’t measured or audited to assess policy compliance, which makes enforcing the policies next to impossible.

      Our Advice

      Critical Insight

      • Document what you need to document and forget the rest. Always check to see if you can use a previously approved policy before you create a new one. You may only need to create new guidelines or standards rather than approve a new policy.

      Impact and Result

      • Start with a comprehensive policy framework to help you identify policy gaps. Prioritize and address those policy gaps.
      • Create effective policies that are reasonable, measurable, auditable, and enforceable.
      • Create and document procedures to support policy changes.

      Develop Infrastructure & Operations Policies and Procedures Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should change your approach to developing Infrastructure & Operations policies and procedures, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Identify policy and procedure gaps

      Create a prioritized action plan for documentation based on business need.

      • Develop Infrastructure & Operations Policies and Procedures – Phase 1: Identify Policy and Procedure Gaps

      2. Develop policies

      Adapt policy templates to meet your business requirements.

      • Develop Infrastructure & Operations Policies and Procedures – Phase 2: Develop Policies
      • Availability and Capacity Management Policy
      • Business Continuity Management Policy
      • Change Control – Freezes & Risk Evaluation Policy
      • Change Management Policy
      • Configuration Management Policy
      • Firewall Policy
      • Hardware Asset Management Policy
      • IT Triage and Support Policy
      • Release Management Policy
      • Software Asset Management Policy
      • System Maintenance Policy – NIST
      • Internet Acceptable Use Policy

      3. Document effective procedures

      Improve policy adherence and service effectiveness through procedure standardization and documentation.

      • Develop Infrastructure & Operations Policies and Procedures – Phase 3: Document Effective Procedures
      • Capacity Plan Template
      • Change Management Standard Operating Procedure
      • Configuration Management Standard Operation Procedures
      • Incident Management and Service Desk SOP
      • DRP Summary Template
      • Service Desk Standard Operating Procedure
      • HAM Standard Operating Procedures
      • SAM Standard Operating Procedures
      [infographic]

      Further reading

      Develop Infrastructure & Operations Policies and Procedures

      Document what you need to document and forget the rest.

      Table of contents

      Project Rationale

      Project Outlines

      • Phase 1: Identify Policy and Procedure Gaps
      • Phase 2: Develop Policies
      • Phase 3: Document Effective Procedures

      Bibliography

      ANALYST PERSPECTIVE

      Document what you need to document now and forget the rest.

      "Most IT organizations struggle to create and maintain effective policies and procedures, despite known improvements to consistency, compliance, knowledge transfer, and transparency.

      The numbers are staggering. Fully three-quarters of IT professionals believe their policies need improvement, and the same proportion of organizations don’t update procedures as required.

      At the same time, organizations that over-document and under-document perform equally poorly on key measures such as policy quality and policy adherence. Take a practical, step-by-step approach that prioritizes the documentation you need now. Leave the rest for later."

      (Andrew Sharp, Research Manager, Infrastructure & Operations Practice, Info-Tech Research Group)

      Our understanding of the problem

      This Research Is Designed For:

      • Infrastructure Managers
      • Chief Technology Officers
      • IT Security Managers

      This Research Will Help You:

      • Address policy gaps
      • Develop effective procedures and procedure documentation to support policy compliance

      This Research Will Also Assist:

      • Chief Information Officers
      • Enterprise Risk and Compliance Officers
      • Chief Human Resources Officers
      • Systems Administrators and Engineers

      This Research Will Help Them:

      • Understand the importance of a coherent approach to policy development
      • Understand the importance of Infrastructure & Operations policies
      • Support Infrastructure & Operations policy development and enforcement

      Info-Tech Best Practice

      This blueprint supports templates for key policies and procedures that help Infrastructure & Operations teams to govern and manage internal operations. For security policies, see the NIST SP 800-171 aligned Info-Tech blueprint, Develop and Deploy Security Policies.

      Executive Summary

      Situation

      • Time and money are wasted dealing with mistakes or missteps that should have been addressed by procedures or policies.
      • Standard operating procedures are less effective without a policy to provide a clear mandate and direction.

      Complication

      • Existing policies were written, approved, signed – and forgotten for years because no one has time to maintain them.
      • Adhering to policies is rarely a priority, as compliance often feels like an impediment to getting work done.
      • Processes aren’t measured or audited to assess policy compliance, which makes enforcing the policies next to impossible.

      Resolution

      • Start with a comprehensive policy framework to help you identify policy gaps. Prioritize and address those policy gaps.
      • Create effective policies that are reasonable, measurable, auditable, and enforceable.
      • Create and document procedures to support policy changes.

      Info-Tech Insight

      1. Document what you need to document and forget the rest.
        Always check if a previously approved policy exists before you create a new one. You may only need to create new guidelines or standards rather than approve a new policy.
      2. Support policies with documented procedures.
        Build procedures that embed policy adherence in daily operations. Find opportunities to automate policy adherence (e.g. removing local admin rights from user computers).

      What are policies, procedures, and processes?

      A policy is a governing document that states the long-term goals of the organization and in broad strokes outlines how they will be achieved (e.g. a Data Protection Policy).

      In the context of policies, a procedure is composed of the steps required to complete a task (e.g. a Backup and Restore Procedure). Procedures are informed by required standards and recommended guidelines. Processes, guidelines, and standards are three pillars that support the achievement of policy goals.

      A process is higher level than a procedure – a set of tasks that deliver on an organizational goal.

      Better policies and procedures reduce organizational risk and, by strengthening the ability to execute processes, enhance the organization’s ability to execute on its goals.

      Visualization of policies, procedures, and processes using pillars. Two separate structures, 'Policy A' and 'Policy B', are each held up by three pillars labelled 'Standards', 'Procedures', and 'Guidelines'. Two lines pass through the pillars of both structures and are each labelled 'Value-creating process'.

      Document to improve governance and operational processes

      Deliver value

      Build, deliver, and support Infrastructure assets in a consistent way, which ultimately reduces costs associated with downtime, errors, and rework. A good manual process is the foundation for a good automated process.

      Simplify Training

      Use documentation for knowledge transfer. Routine tasks can be delegated to less-experienced staff.

      Maintain compliance

      Comply with laws and regulations. Policies are often required for compliance, and formally documented and enforced policies help the organization maintain compliance by mandating required due diligence, risk reduction, and reporting activities.

      Provide transparency

      Build an open kitchen. Other areas of the organization may not understand how Infra & Ops works. Your documentation can provide the answer to the perennial question: “Why does that take so long?”

      Info-Tech Best Practice

      Governance goals must be supported with effective, well-aligned procedures and processes. Use Info-Tech’s research to support the key Infrastructure & Operations processes that enable your business to create value.

      Document what you need to document – and forget the rest

      Half of all organizations believe their policy suite is insufficient. (Info-Tech myPolicies Survey Data (N=59))

      Pie chart with three sections labelled 'Too Many Policies and Procedures 14%', 'Adequate Policies and Procedures 37%', 'Insufficient Policies and Procedures 49%'

      Too much documentation and a lack of documentation are both ineffective. (Info-Tech myPolicies Survey Data (N=59))

      Two bar charts labelled 'Policy Adherence' and 'Policy Quality' each with three bars representing 'Too Many Policies and Procedures', 'Insufficient Policies and Procedures', and 'Adequate Policies and Procedures'. The values shown are an average score out of 5. For Policy Adherence: Too Many is 2.4, Insufficient is 2.1, and Adequate is 3.2. For Policy Quality: Too Many is 2.9, Insufficient is 2.6, and Adequate is 4.1.

      77% of IT professionals believe their policies require improvement. (Kaspersky Lab)

      Presenting: A COBIT-aligned policy suite

      We’ve developed a suite of effective policy templates for every Infra & Ops manager based on Info-Tech’s IT Management & Governance Framework.

      Policy templates and the related aspects of Info-Tech's IT Management & Governance Framework

      Info-Tech Best Practice

      Look for these symbols as you work through the deck. Prioritize and focus on the policies you work on first based on the value of the policy to the enterprise and the existing gaps in your governance structure.

      Project outline

      Phases

      1. Identify policy and procedure gaps 2. Develop policies 3. Document effective procedures

      Steps

      • Review and right-size the existing policy set
      • Create an action plan to address policy gaps
      • Modify policy templates and gather feedback
      • Implement, enforce, measure, and maintain new policies
      • Scope and outline procedures
      • Document and maintain procedures

      Outcomes

      Action list of policy and procedure gaps New or updated Infrastructure & Operations policies Procedure documentation

      Use these icons to help direct you as you navigate this research

      Use these icons to help guide you through each step of the blueprint and direct you to content related to the recommended activities.

      A small monochrome icon of a wrench and screwdriver creating an X.

      This icon denotes a slide where a supporting Info-Tech tool or template will help you perform the activity or step associated with the slide. Refer to the supporting tool or template to get the best results and proceed to the next step of the project.

      A small monochrome icon depicting a person in front of a blank slide.

      This icon denotes a slide with an associated activity. The activity can be performed either as part of your project or with the support of Info-Tech team members, who will come onsite to facilitate a workshop for your organization.

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      Guided Implementation

      Workshop

      Consulting

      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful." "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track." "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place." "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks used throughout all four options

      Accelerate policy development with a Guided Implementation

      Your trusted advisor is just a call away.

      • Identify Policy and Procedure Gaps (Calls 1-2)
        Assess current policies, operational challenges, and gaps. Mitigate significant risks first.
      • Create and Review Policies (Calls 2-4)
        Modify and review policy templates with an Info-Tech analyst.
      • Create and Review Procedures (Calls 4-6)
        Workflow procedures, using templates wherever possible. Review documentation best practices.

      Contact Info-Tech to set up a Guided Implementation with a dedicated advisor who will walk you through every stage of your policy development project.

      Develop Infrastructure & Operations Policies and Procedures

      Phase 1

      Identify Policy and Procedure Gaps

      PHASE 1: Identify Policy and Procedure Gaps

      Step 1.1: Review and right-size the existing policy set

      This step will walk you through the following activities:

      • Identify gaps in your existing policy suite
      • Document challenges to core Infrastructure & Operations processes
      • Identify documentation that can close gaps
      • Prioritize your documentation effort

      This step involves the following participants:

      • Infrastructure & Operations Manager
      • Infrastructure Supervisors

      Results & Insights

      • Results: A review of the existing policy suite and identification of opportunities for improvement.
      • Insights: Not all gaps necessarily require a fresh policy. Repurpose, refresh, or supplement existing documentation wherever appropriate.

      Conduct a policy review

      Associated Activity icon 1(a) 30 minutes per policy

      You’ve got time to review your policy suite. Make the most of it.

      1. Start with organizational requirements.
        • What initiatives are on the go? What policies or procedures do you have a mandate to create?
      2. Weed out expired and dated policies.
        • Gather your existing policies. Identify when each one was published or last reviewed.
        • Decide whether to retire, merge, or update expired or obviously dated policy.
      3. Review policy statements.
        • Check that the organization is adequately supporting policy statements with SOPs, standards, and guidelines. Ensure role-related information is up to date.
      4. Document and bring any gaps forward to the next activity. If no action is required, indicate that you have completed a review and submit the findings for approval.

      But they just want one policy...

      A review of your policy suite is good practice, especially when it hasn’t been done for a while. Why?
      • Existing policies may address what you’re trying to do with a new policy. Using or modifying an existing policy avoids overlap and contradiction and saves you the effort required to create, communicate, approve, and maintain a new policy.
      • Review the suite to validate that you’re addressing the most important challenges first.

      Brainstorm improvements for core Infrastructure & Operations processes

      Associated Activity icon 1(b) 1 hour

      Supplement the list of gaps from your policy review with process challenges.

      1. Write out key Infra & Ops–related processes – one piece of flipchart paper per process. You can work through all of these processes or cherry-pick the processes you want to improve first.
      2. With participants, write out in point form how you currently execute on these processes (e.g. for Asset Management, you might be tagging hardware, tracking licenses, etc.)
      3. Work through a “Start – Stop – Continue” exercise. Ask participants: What should we start doing? What must we stop doing? What do we do currently that’s valuable and must continue? Write ideas on sticky notes.
      4. Once you’ve worked through the “Start – Stop – Continue” exercise for all processes, group similar suggestions for improvements.

      Asset Management: Manage hardware and software assets across their lifecycle to protect assets and manage costs.

      Availability and Capacity Management: Balance current and future availability, capacity, and performance needs with cost-to-serve.

      Business Continuity Management: Continue operation of critical business processes and IT services.

      Change Management: Deliver technical changes in a controlled manner.

      Configuration Management: Define and maintain relationships between technical components.

      Problem Management: Identify incident root cause.

      Operations Management: Coordinate operations.

      Release and Patch Management: Deliver updates and manage vulnerabilities in a controlled manner.

      Service Desk: Respond to user requests and all incidents.

      PHASE 1: Identify Policy and Procedure Gaps

      Step 1.2: Create an action plan to address policy gaps

      This step will walk you through the following activities:

      • Identify challenges and gaps that can be addressed via documentation
      • Prioritize high-value, high-risk gaps

      This step involves the following participants:

      • Infrastructure & Operations Manager
      • Infrastructure Supervisors

      Results & Insights

      • Results: An action plan to tackle policy and procedures gaps, aligned with business requirements and business value.
      • Insights: Not all documentation is equally valuable. Prioritize documentation that delivers value and mitigates risk.

      Support policies with procedures, standards, and guidelines

      Use a working definition for each type of document.

      Policy: Directives, rules, and mandates that support the overarching, long-term goals of the organization.

      • Standards: Prescriptive, uniform requirements.
      • Procedures: Specific, detailed, step-by-step instructions for completing a task.
      • Guidelines: Non-enforceable, recommended best practices.

      Info-Tech Best Practice

      Take advantage of your Info-Tech advisory membership by scheduling review sessions with an analyst. We provide high-level feedback to ensure your documentation is clear, concise, and consistent and aligns with the governance objectives you’ve identified.

      Answer the following questions to decide if governance documentation can help close gaps

      Associated Activity icon 1(c) 30 minutes

      Documentation supports knowledge sharing, process consistency, compliance, and transparency. Ask the following questions:

      1. What is the purpose of the documentation?
        Procedures support task completion. Policies set direction and manage organizational risk.
      2. Should it be enforceable?
        Policies and standards are enforceable; guidelines are not. Procedures are enforceable in that they should support policy enforcement.
      3. What is the scope?
        To document a task, create a procedure. Set overarching rules with policies. Use standards and guidelines to set detailed rules and best practices.
      4. What’s the expected cadence for updates?
        Policies should be revisited and revised less frequently than procedures.

      Info-Tech Best Practice

      Reinvent the wheel? I don’t think so!

      Always check to see if a gap can be addressed with existing tools before drafting a new policy

      • Is there an existing policy that could be supported with new or updated procedures, technical standards, or guidelines?
      • Is there a technical control you can deploy that would enforce the terms of an existing, approved policy?
      • It may be simpler to amend an existing policy instead of creating a new one.

      Some problems can’t be solved by better documentation (or by documentation alone). Consider additional strategies that address people, process, and technology.

      Tackle high-value, high-risk gaps first

      Associated Activity icon 1(d) 30 minutes

      Prioritize your documentation effort.

      1. List each proposed piece of documentation on the board.
      2. Assign a score to the risk posed to the business by the lack of documentation and to the expected benefit of completing the documentation. Use a scoring scale between 1 and 3 such as the one on the right.
      3. Prioritize documentation that mitigates risks and maximizes benefits.
      4. If you need to break ties, consider effort required to develop, implement, and enforce policies or procedures.

      Example Scoring Scale

      Score Business risk of missing documentation Business benefit of value of documentation

      1

      Low: Affects ad hoc activities or non-critical data. Low: Minimal impact.

      2

      Moderate: Impacts productivity or internal goodwill. Moderate: Required periodically; some cross-training opportunities.

      3

      High: Impacts revenue, safety, or external goodwill. High: Save time for common or ongoing processes; extensive improvement to training/knowledge transfer.

      Info-Tech Insight

      Documentation pulls resources away from other important programs and projects, so ultimately it must be a demonstrably higher priority than other work. This exercise is designed to align documentation efforts with business goals.

      Phase 1: Review accomplishments

      Policy pillars: Standards, Procedures, Guidelines

      Summary of Accomplishments

      • Identified gaps in the existing policy suite and identified pain points in existing Infra & Ops processes.
      • Developed a list of policies and procedures that can address existing gaps and prioritized the documentation effort.

      Develop Infrastructure & Operations Policies and Procedures

      Phase 2

      Develop Policies

      PHASE 2: Develop Policies

      Step 2.1: Modify policy templates and gather feedback

      This step will walk you through the following activities:

      • Modify policy templates

      This step involves the following participants:

      • Infrastructure & Operations Manager
      • Technical Writer

      Results & Insights

      • Results: Your own COBIT-aligned policies built by modifying Info-Tech templates.
      • Insights: Effective policies are easy to read and navigate.

      Write Good-er: Be Clear, Consistent, and Concise

      Effective policies adhere to the three Cs of documentation.

      1. Be clear. Make it as easy as possible for a user to learn how to comply with your policy.
      2. Be consistent. Write policies that complement each other, not contradict each other.
      3. Be concise. Make it as quick and easy as possible to read and understand your policy.

      Info-Tech Best Practice

      To download the full suite of templates all at once, click the “Download Research” button on the research landing page on the website.

      Use the three Cs: Be Clear

      Understanding makes compliance possible. Create policy with the goal of making compliance as easy as possible. Use positive, simple language to convey your intentions and rationale to your audience. Staff will make an effort adhere to your policy when they understand the need and are able to comply with the terms.

      1. Choose a skilled writer. Select a writer who can write clearly and succinctly.
      2. Default to simple language and define key terms. Define scope and key terms upfront. Avoid using technical terms outside of technical documentation; if they’re necessary be sure to define them as well.
      3. Use active, positive language. Where possible, tell people what they can do, not what they can’t.
      4. Keep the structure simple. Complicated documents are less likely to be understood and read. Use short sentences and paragraphs. Lists are a helpful way to summarize important information. Guide your reader through the document with appropriately named section headers, tables of contents, and numeration.
      5. Add a process for handling exceptions. Refer to procedures, standards, and guidelines documentation. Try to keep these links as static as possible. Also, refer to a process for handling exceptions.
      6. Manage the integrity of electronic documents. When published electronically, the policy should have restricted editing access or should be published in a non-editable format. Access to the procedure and policy storage database for employees should be read-only.

      Info-Tech Insight

      Highly effective policies are easy to navigate. Your policies should be “skimmable.” Very few people will fully read a policy before accepting it. Make it easy to navigate so the reader can easily find the policy statements that apply to them.

      Use the three Cs: Be Consistent

      Ensure that policies are aligned with other organizational policies and procedures. It detracts from compliance if different policies prescribe different behavior in the same situation. Moreover, your policies should reflect the corporate culture and other company standards. Use your policies to communicate rules and get employees aligned with how your company works.

      1. Use standard sentences and paragraphs. Policies are usually expressed in short, standard sentences. Lists should also be used when necessary or appropriate.
      2. Remember the three Ws. When writing a policy, always be sure to clearly state what the rule is, when it should be applied, and who needs to follow it. Policies should clearly define their scope of application and whether directives are mandatory or recommended.
      3. Use an outline format. Using a numbered or outline format will make a document easier to read and will make content easier to look up when referring back to the document at a later time.
      4. Avoid amendments. Avoid the use of information that is quickly outdated and requires regular amendment (e.g. names of people).
      5. Reference a set of supplementary documents. Codify your tactics outside of the policy document, but make reference to them within the text. This makes it easier to ensure consistency in the behavior prescribed by your policies.

      "One of the issues is the perception that policies are rules and regulations. Instead, your policies should be used to say ‘this is the way we do things around here.’" (Mike Hughes CISA CGEIT CRISC, Principal Director, Haines-Watts GRC)

      Use the three Cs: Be Concise

      Reading and understanding policies shouldn’t be challenging, and it shouldn’t significantly detract from productive time. Long policies are more difficult to read and understand, increasing the work required for employees to comply with them. Put it this way: How often do you read the Terms and Conditions of software you’ve installed before accepting them?

      1. Be direct. The quicker you get to the point, the easier it is for the reader to interpret and comply with your policy.
      2. Your policy is a rule, not a recipe. Your policy should outline what needs to be accomplished and why – your standards, guidelines, and SOPs address the how.
      3. Keep policies short. Nobody wants to read a huge policy book, so keep your policies short.
      4. Use additional documentation where needed. In addition to making consistency easier, this shortens the length of your policies, making them easier to read.
      5. Policy still too large? Modularize it. If you have an extremely large policy, it’s likely that it’s too widely scoped or that you’re including statements that should be part of procedure documentation. Consider breaking your policy into smaller, focused, more digestible documents.

      "If the policy’s too large, people aren’t going to read it. Why read something that doesn’t apply to me?" (Carole Fennelly, Owner and Principal, cFennelly Consulting)

      "I always try to strike a good balance between length and prescriptiveness when writing policy. Your policies … should be short and describe the problem and your approach to solving it. Below policies, you write standards, guidelines, and SOPs." (Michael Deskin, Policy and Technical Writer, Canadian Nuclear Safety Commission)

      Customize policy documents

      Associated Activity icon 2(a) 1-2 hours per policy

      Use the policies templates to support key Infrastructure & Operations programs.

      INPUT: List of prioritized policies

      OUTPUT: Written policy drafts ready for review

      Materials: Policy templates

      Participants: Policy writer, Signing authority

      No policy template will be a perfect fit for your organization. Use Info-Tech’s research to develop your organization’s program requirements. Customize the policy templates to support those requirements.

      1. Work through policies from highest to lowest priority as defined in Phase 1.
      2. Follow the instructions written in grey text to customize the policy. Follow the three Cs when you write your policy.
      3. When your draft is finished, prepare to request signoff from your signing authority by reviewing the draft with an Info-Tech analyst.
      4. Complete the highest ranked three or four draft policies. Review all these policies with relevant stakeholders and include all relevant signing authorities in the signoff process.
      5. Rinse and repeat. Iterate until all relevant polices are complete.

      Request, Incident, and Problem Management

      An effective, timely service desk correlates with higher overall end-user satisfaction across all other IT services. (Info-Tech Research Group, 2016 (N=25,998))

      An icon for the 'DSS02 Service Desk' template. An icon for the 'DSS03 Incident and Problem Management' template.

      Use the following template to create a policy that outlines the goals and mandate for your service and support organization:

      • IT Triage and Support Policy

      Support the program and associated policy statements using Info-Tech’s research:

      • Standardize the Service Desk
      • Incident and Problem Management
      • Design & Build a User-Facing Service Catalog

      Embrace Standardization

      • Outline the support and service mandate with the policy. Support the policy with the methodology in Info-Tech’s research.
      • Over time, organizations without standardized processes face confusion, redundancies, and cost overruns. Standardization avoids wasting energy and effort building new solutions to solved issues.
      • Standard processes for IT services define repeatable approaches to work and sandbox creative activities.
      • Create tickets for every task and categorize them using a standard classification system. Use the resulting data to support root-cause analysis and long-term trend management.
      • Create a single point of contact for users for all incidents and requests. Escalate and resolve tickets faster.
      • Empower end users and technicians with knowledge bases that help them solve problems without intervention.

      Change, Release, and Patch Management

      Slow turnaround, unauthorized changes, and change-related incidents are all too familiar to many managers.

      An icon for the 'BAI06 Change Management' template. An icon for the 'BAI07 Release Management' template.

      Use the following templates to create policies that define effective patch, release, and change management:

      • Change Management Policy
      • Release and Patch Management Policy
      • Change Control – Freezes & Risk Evaluation Policy

      Ensure the policy is supported by using the following Info-Tech research:

      • Optimize Change Management

      Embrace Change

      • IT system owners resist change management when they see it as slow and bureaucratic.
      • At the same time, an increasingly interlinked technical environment may cause issues to appear in unexpected places. Configuration management systems are often not kept up to date, so preventable conflicts get missed.
      • No process exists to support the identification and deployment of critical security patches. Tracking down users to find a maintenance window takes significant, dedicated effort and intervention from the management team.
      • Create a unified change management process that reduces risk and is balanced in its approach toward deploying changes, while also maintaining throughput of patches, fixes, enhancements, and innovation.

      IT Asset Management (ITAM)

      A proactive, dynamic ITAM program will pay dividends in support, contract management, appropriate provisioning, and more.

      An icon for the 'BAI09 Asset Management' template.

      Start by outlining the requirements for effective asset management:

      • Hardware Asset Management Policy
      • Software Asset Management Policy

      Support ITAM policies with the following Info-Tech research:

      • Implement IT Asset Management

      Leverage Asset Data

      • Create effective, directional policies for your asset management program that provide a mandate for action. Support the policies with robust procedures, capable staff, and right-fit technology solutions.
      • Poor management of assets generally leads to higher costs due to duplicated purchases, early replacement, loss, and so on.
      • Visibility into asset location and ownership improves security and accountability.
      • A centralized repository of asset data supports request fulfilment and incident management.
      • Asset management is an ongoing program, not a one-off project, and must be resourced accordingly. Organizations often implement an asset management program and let it stagnate.

      "Many of the large data breaches you hear about… nobody told the sysadmin the client data was on that server. So they weren’t protecting and monitoring it." (Carole Fennelly, Owner and Principal, cFennelly Consulting)

      Business Continuity Management (BCM)

      Streamline the traditional approach to make BCM practical and repeatable.

      An icon for the 'DSS04 DR and Business Continuity' template.

      Set the direction and requirements for effective BCM:

      • Business Continuity Management Policy

      Support the BCM policy with the following Info-Tech research:

      • Create a Right-Sized Disaster Recovery Plan
      • Develop a Business Continuity Plan

      Build Organizational Resilience

      • Evidence of disaster recovery and business continuity planning is increasingly required to comply with regulations, mitigate business risk, and meet customer demands.
      • IT leaders are often asked to take the lead on business continuity, but overall accountability for business continuity rests with the board of directors, and each business unit must create and maintain its business continuity plan.
      • Set an organizational mandate for BCM with the policy.
      • Divide the business continuity mandate into manageable parcels of work. Follow Info-Tech’s practical methodology to tackle key disaster recovery and business continuity planning activities one at a time.

      Info-Tech Best Practice

      Governance goals must be supported with effective, well-aligned procedures and processes. Use Info-Tech’s research to support the key Infrastructure & Operations processes that enable your business to create value.

      Availability, Capacity, and Operations Management

      What was old is new again. Use time-tested techniques to manage and plan cloud capacity and costs.

      An icon for the 'BAI04 Availability and Capacity Management' template. An icon for the 'DSS01 Operations Management' template. An icon for the 'BAI10 Configuration Management' template.

      Set the direction and requirements for effective availability and capacity management:

      • Availability and Capacity Management Policy
      • System Maintenance Policy – NIST

      Support the policy with the following Info-Tech research:

      • Develop an Availability and Capacity Management Plan
      • Improve IT Operations Management
      • Develop an IT Infrastructure Services Playbook

      Mature Service Delivery

      • Hybrid IT deployments – managing multiple locations, delivery models, and service providers – are the future of IT. Hybrid deployments significantly complicate capacity planning and operations management.
      • Effective operations management practices develop structured processes to automate activities and increase process consistency across the IT organization, ultimately improving IT efficiency.
      • Trying to add mature service delivery can feel like playing whack-a-mole. Systematically improve your service capabilities using the tactical, iterative approach outlined in Improve IT Operations Management.

      Enhance your overall security posture with a defensible, prescriptive policy suite

      Align your security policy suite with NIST Special Publication 800-171.

      Security policies support the organization’s larger security program. We’ve created a dedicated research blueprint and a set of templates that will help you build security policies around a robust framework.

      • Start with a security charter that aligns the security program with organizational objectives.
      • Prioritize security policies that address significant risks.
      • Work with technical and business stakeholders to adapt Info-Tech’s NIST SP 800-171–aligned policy templates (at right) to reflect your organizational objectives.

      A diagram listing all the different elements in a 'Security Charter': 'Access Control', 'Audit & Acc.', 'Awareness and Training', 'Config. Mgmt.', 'Identification and Auth.', 'Incident Response', 'Maintenance', 'Media Protection', 'Personnel Security', 'Physical Protection', 'Risk Assessment', 'Security Assessment', 'System and Comm. Protection', and 'System and Information Integrity'.

      Review and download Info-Tech's blueprint Develop and Deploy Security Policies.

      Info-Tech Best Practice

      Customize Info-Tech’s policy framework to align your policy suite to NIST SP 800-171. Given NIST’s requirements for the control of confidential information, organizations that align their policies to NIST standards will be in a strong governance position.

      PHASE 2: Develop Policies

      Step 2.2: Implement, enforce, measure, and maintain new policies

      This step will walk you through the following activities:

      • Gather stakeholder feedback
      • Identify preventive and detective controls
      • Identify required supports
      • Seek policy approval
      • Establish roles and responsibilities for policy maintenance

      This step involves the following participants:

      • Infrastructure & Operations Manager
      • Infrastructure Supervisors
      • Technical Writer
      • Policy Stakeholders

      Results & Insights

      • Results: Well-supported policies that have received signoff.
      • Insights: If you’re not prepared to enforce the policy, you might not actually need a policy. Use the policy statements as guidelines or standards, create and implement procedures, and build a culture of compliance. Once you can confidently execute on required controls, seek signoff.

      Gather feedback from users to assess the feasibility of the new policies

      Associated Activity icon 2(b) Review period: 1-2 weeks

      Once the policies are drafted, roundtable the drafts with stakeholders.

      INPUT: Draft policies

      OUTPUT: Reviewed policy drafts ready for approval

      Materials: Policy drafts

      Participants: Policy stakeholders

      1. Form a test group of users who will be affected by the policy in different ways. Keep the group to around five staff.
      2. Present new policies to the testers. Allow them to read the documents and attempt to comply with the new policies in their daily routines.
      3. Collect feedback from the group.
        • Consider using interviews, email surveys, chat channels, or group discussions.
        • Solicit ideas on how policy statements could be improved or streamlined.
      4. Make reasonable changes to the first draft of the policies before submitting them for approval. Policies will only be followed if they’re realistic and user friendly.

      Info-Tech Best Practice

      Allow staff the opportunity to provide input on policy development. Giving employees a say in policy development helps avoid obstacles down the road. This is especially true if you’re trying to change behavior rather than lock it in.

      Develop mechanisms for monitoring and enforcement

      Associated Activity icon 2(c) 20 minutes per policy

      Brainstorm preventive and detective controls.

      INPUT: Draft policies

      OUTPUT: Reviewed policy drafts ready for approval

      Materials: Policy drafts

      Participants: Policy stakeholders

      Preventive controls are designed to discourage or pre-empt policy breaches before they occur. Training, approvals processes, and segregation of duties are examples of preventive controls. (Ohio University)

      Detective controls help enforce the policy by identifying breaches after they occur. Forensic analysis and event log auditing are examples of detective controls. (Ohio University)

      Not all policies require the same level of enforcement. Policies that are required by law or regulation generally require stricter enforcement than policies that outline best practices or organizational values.

      Identify controls and enforcement mechanisms that are in line with policy requirements. Build control and enforcement into procedure documentation as needed.

      Suggestions:

      1. Have staff sign off on policies. Disclose any monitoring/surveillance.
      2. Ensure consequences match the severity of the infraction. Document infractions and ensure that enforcement is applied consistently across all infractions.
      3. Automatic controls shouldn’t get in the way of people’s ability to do their jobs. Test controls with users before you roll them out widely.

      Support the policy before seeking approval

      A policy is only as strong as its supporting pillars.

      Create Standards

      Standards are requirements that support policy adherence. Server builds and images, purchase approval criteria, and vulnerability severity definitions can all be examples of standards that improve policy adherence.

      Where reasonable, use automated controls to enforce standards. If you automate the control, consider how you’ll handle exceptions.

      Create Guidelines

      If no standards exist – or best practices can’t be monitored and enforced, as standards require – write guidelines to help users remain in compliance with the policy.

      Create Procedures: We’ll cover procedure development and documentation in Phase 3.

      Info-Tech Insight

      In general, failing to follow or strictly enforce a policy creates a risk for the business. If you’re not confident a policy will be followed or enforced, consider using policy statements as guidelines or standards as an interim measure as you update procedures and communicate and roll out changes that support adherence and enforcement.

      Seek approval and communicate the policy

      Policies ultimately need to be accepted by the business.

      • Once the drafts are completed, identify who is in charge of approving the policies.
      • Ensure all stakeholders understand the importance, context, and repercussions of the policies.
      • The approvals process is about appropriate oversight of the drafted policies. For example:
        • Do the policies satisfy compliance and regulatory requirements?
        • Do the policies work with the corporate culture?
        • Do the policies address the underlying need?

      If the draft is rejected:

      • Acquire feedback and make revisions.
      • Resubmit for approval.

      If the draft is approved:

      • Set the effective date and a review date.
      • Begin communication, training, and implementation.
      • Employees must know that there are new policies and understand the steps they must take to comply with the policies in their work.
      • Employees must be able to interpret, understand, and know how to act upon the information they find in the policies.
      • Employees must be informed on where to get help or ask questions and from whom to request policy exceptions.

      "A lot of board members and executive management teams… don’t understand the technology and the risks posed by it." (Carole Fennelly, Owner and Principal, cFennelly Consulting)

      Identify policy management roles and responsibilities

      Associated Activity icon 2(d) 30 minutes

      Discuss and assign roles and responsibilities for ongoing policy management.

      Role

      Responsibilities

      Executive sponsor

    • Supports the program at the highest levels of the business, as needed
    • Program lead

    • Leads the Infrastructure & Operations policy management program
    • Identifies and communicates status updates to the executive sponsor and the project team
    • Coordinates business demands and interviews and organizes stakeholders to identify requirements
    • Manages the work team and coordinates policy rollout
    • Policy writer

    • Authors and updates policies based on requirements
    • Coordinates with outsourced editor for completion of written documents
    • IT infrastructure SMEs

    • Provide technical insight into capabilities and limitations of infrastructure systems
    • Provide advice on possible controls that can aid policy rollout, monitoring, and enforcement
    • Legal expert

    • Provides legal advice on the policy’s legal terms and enforceability
    • "Whether at the level of a government, a department, or a sub-organization: technology and policy expertise complement one another and must be part of the conversation." (Peter Sheingold, Portfolio Manager, Cybersecurity, MITRE Corporation)

      Phase 2: Review accomplishments

      Effective Policies: Clear, Consistent, and Concise

      An icon for the 'DSS02 Service Desk' template.

      An icon for the 'DSS03 Incident and Problem Management' template.

      An icon for the 'BAI06 Change Management' template.

      An icon for the 'BAI07 Release Management' template.

      An icon for the 'BAI09 Asset Management' template.

      An icon for the 'DSS04 DR and Business Continuity' template.

      An icon for the 'BAI04 Availability and Capacity Management' template.

      An icon for the 'DSS01 Operations Management' template.

      An icon for the 'BAI10 Configuration Management' template.

      Summary of Accomplishments

      • Built priority policies based on templates aligned with the IT Management & Governance Framework and COBIT 5.
      • Reviewed controls and policy supports.
      • Assigned roles and responsibilities for ongoing policy maintenance.

      Develop Infrastructure & Operations Policies and Procedures

      Phase 3

      Document Effective Procedures

      PHASE 3: Document Effective Procedures

      Step 3.1: Scope and outline procedures

      This step will walk you through the following activities:

      • Prioritize SOP documentation
      • Draft workflows using a tabletop exercise
      • Modify templates, as applicable

      This step involves the following participants:

      • Infrastructure & Operations Manager
      • Technical Writer
      • Infrastructure Supervisors

      Results & Insights

      • Results: An action plan for SOP documentation and an outline of procedure workflows.
      • Insights: Don’t let tools get in the way of documentation – low-tech solutions are often the most effective way to build and analyze workflows.

      Prioritize your SOP documentation effort

      Associated Activity icon 3(a) 1-2 hours

      Build SOP documentation that gets used and doesn’t just check a box.

      1. Review the list of procedure gaps from Phase 1. Are any other procedures needed? Are some of the procedures now redundant?
      2. Establish the scope of the proposed procedures. Who are the stakeholders? What policies do they support?
      3. Run a basic prioritization exercise using a three-point scale. Higher scores mean greater risks or greater benefits. Score the risk of the undocumented procedure to the business (e.g. potential effect on data, productivity, goodwill, health and safety, or compliance). Score the benefit to the business of documenting the procedure (e.g. throughput improvements or knowledge transfer).
      4. Different procedures require different formats. Decide on one or more formats that can help you effectively document the procedure:
        • Flowcharts: Depict workflows and decision points. Provide an at-a-glance view that is easy to follow. Can be supported by checklists and diagrams where more detail is required.
        • Checklists: A reminder of what to do, rather than how to do it. Keep instructions brief.
        • Diagrams: Visualize objects, topologies, and connections for reference purposes.
        • Tables: Establish relationships between related categories.
        • Prose: Use full-text instructions where other documentation strategies are insufficient.

      Modify the following Info-Tech templates for larger SOPs

      Support these processes...

      ...with these blueprints...

      ...to create SOPs using these templates.

      An icon for the 'DSS04 DR and Business Continuity' template. Create a Right-Sized Disaster Recovery Plan DRP Summary
      An icon for the 'BAI09 Asset Management' template. Implement IT Asset Management HAM SOP and SAM SOP
      An icon for the 'BAI06 Change Management' template. An icon for the 'BAI07 Release Management' template. Optimize Change Management Change Management SOP
      An icon for the 'DSS02 Service Desk' template. An icon for the 'DSS03 Incident and Problem Management' template. Standardize the Service Desk Service Desk SOP

      Use tabletop planning or whiteboards to draft workflows

      Associated Activity icon 3(b) 30 minutes

      Tabletop planning is a paper-based exercise in which your team walks through a particular process and maps out what happens at each stage.

      OUTPUT: Steps in the current process for one SOP

      Materials: Tabletop, pen, and cue cards

      Participants: Process owners, SMEs

      1. For this exercise, choose one particular process to document.
      2. Document each step of the process on cue cards, which can be arranged on the table in sequence.
      3. Be sure to include task ownership in your steps.
      4. Map out the process as it currently happens – we’ll think about how to improve it later.
      5. Keep focused. Stay on task and on time.

      Example:

      • Step 3: PM reviews new defects daily
      • Step 4: PM assigns defects to tech leads
      • Step 5: Assigned resource updates status – frequency is based on ticket priority

      Info-Tech Insight

      Don’t get weighed down by tools. Relying on software or other technological tools can detract from the exercise. Use simple tools such as cue cards to record steps so that you can easily rearrange steps or insert steps based on input from the group.

      Collaborate to optimize the SOP

      Associated Activity icon 3(c) 30 minutes

      Review the tabletop exercise. What gaps exist in current processes?
      How can the processes be made better? What are the outputs and checkpoints?

      OUTPUT: Identify steps to optimize the SOP

      Materials: Tabletop, pen, and cue cards

      Participants: Process owners, SMEs

      Example:

      • Step 3: PM reviews new defects daily
      • NEW STEP: Schedule 10-minute daily defect reviews with PM and tech leads to evaluate ticket priority
      • Step 4: PM assigns defects to tech leads
      • Step 5: Assigned resource updates status – frequency is based on ticket priority
        • Step 5 Subprocess: Ticket status update
        • Step 5 Output: Ticket status moved to OPEN by assigned resource – acknowledges receipt by assigned resource

      A note on colors: Use white cards to record steps. Record gaps on yellow cards (e.g. a process step not documented) and risks on red cards (e.g. only one person knows how to execute a step) to highlight your gaps/to-dos and risks to be mitigated or accepted.

      If it’s necessary to clarify complex process flows during the exercise, you can also use green cards for decision diamonds, purple for document/report outputs, and blue for subprocesses.

      PHASE 3: Document Effective Procedures

      Step 3.2: Document effective procedures

      This step will walk you through the following activities:

      • Document workflows, checklists, and diagrams
      • Establish a cadence for document review and updates

      This step involves the following participants:

      • Infrastructure Manager
      • Technical Writer

      Results & Insights

      • Results: Improved SOP documentation and document management practices.
      • Insights: It’s possible to keep up with changes if you put the right cues and accountabilities in place. Include document review in project and change management procedures and hold staff accountable for completion.

      Document workflows with flowcharting software

      Suggestions for workflow documentation

      • Whether you draft the workflow on a whiteboard or using cue cards, the first iteration is usually messy. Clean up the flow as you document the results of the exercise.
      • Make the workflow as simple as possible and no simpler. Eliminate any decision points that aren’t strictly necessary to complete the procedure.
      • Use standard flowchart shapes (see next slide).
      • Use links to connect to related documentation.
      • Review the documented workflow with participants.

      Download the following workflow examples:

      Establish flowcharting standards

      If you don’t have existing flowchart standards, then keep it simple and stick to basic flowcharting conventions as described below.

      Basic flowcharting convention: a circle can be used for 'Start, End, and Connector'. Start, End, and Connector: Traditional flowcharting standards reserve this shape for connectors to other flowcharts or other points in the existing flowchart. Unified Modeling Language (UML) also uses the circle for start and end points.
      Basic flowcharting convention: a rounded rectangle can be used for 'Start and End'. Start and End: Traditional flowcharting standards use this for start and end. However, Info-Tech recommends using the circle shape to reduce the number of shapes and avoid confusion with other similar shapes.
      Basic flowcharting convention: a rectangle can be used for 'Process Step'. Process Step: Individual process steps or activities (e.g. create ticket or escalate ticket). If it’s a series of steps, then use the subprocess symbol and flowchart the subprocess separately.
      Basic flowcharting convention: a rectangle with double-line on the ends can be used for 'Subprocess'. Subprocess: A series of steps. For example, a critical incident SOP might reference a recovery process as one of the possible actions. Marking it as a subprocess, rather than listing each step within the critical incident SOP, streamlines the flowchart and avoids overlap with other flowcharts (e.g. the recovery process).
      Basic flowcharting convention: a diamond can be used for 'Decision'. Decision: Represents decision points, typically with Yes/No branches, but you could have other branches depending on the question (e.g. a “Priority?” question could branch into separate streams for Priority 1, 2, 3, 4, and 5 issues).
      Basic flowcharting convention: a rectangle with a wavy bottom can be used for 'Document/Report Output'. Document/Report Output: For example, the output from a backup process might include an error log.

      Support workflows with checklists and diagrams

      Diagrams

      • Diagrams are a visual representation of real-world phenomena and the connections between them.
      • Be sure to use standard shapes. Clearly label elements of the diagram. Use standard practices, including titles, dates, authorship, and versioning.
      • IT systems and interconnections are layered. Include physical, logical, protocol, and data flow connections.

      Examples:

      • XMPL Recovery Workflows
      • Workflow Library

      Checklists

      • Checklists are best used as short-form reminders on how to complete a particular task.
      • Remember the audience. If the process will be carried out by technical staff, there’s technical background material you won’t need to spell out in detail.

      Examples:

      • Employee Termination Process Checklist
      • XMPL Systems Recovery Playbook

      Establish a cadence for documentation review and maintenance

      Lock-in the work with strong document management practices.

      • Identify documentation requirements as part of project planning.
      • Require a manager or supervisor to review and approve SOPs.
      • Check documentation status as part of change management.
      • Hold staff accountable for documentation.

      "It isn’t unusual for us to see infrastructure or operations documentation that is wildly out of date. We’re talking months, even years. Often it was produced as one big effort and then not reliably maintained." (Gary Patterson, Consultant, Quorum Resources)

      Only a quarter of organizations update SOPs as needed

      A bar chart representing how often organizations update SOPs. Each option has two bars, one representing 'North America', the other representing 'Europe and Asia'. 'Never or rarely' is 11% in North America and 3% in Europe and Asia. 'Ad-hoc approach' is 38% in North America and 28% in Europe and Asia. 'For audits/annual reviews' is 33% in North America and 45% in Europe and Asia. 'As needed/via change management' is 18% in North America and 25% in Europe and Asia. Source: Info-Tech Research Group (N=104)

      Info-Tech Best Practice

      Use Info-Tech’s research Create Visual SOP Documents to further evaluate document management practices and toolsets.

      Phase 3: Review accomplishments

      Workflow documentation: Cue cards into flowcharts

      Summary of Accomplishments

      • Identified priority procedures for documentation activities.
      • Created procedure documentation in the appropriate format and level of granularity to support Infra & Ops policies.
      • Published and maintained procedure documentation.

      Research contributors and experts

      Carole Fennelly, Owner
      cFennelly Consulting

      Picture of Carole Fennelly, Owner, cFennelly Consulting.

      Carole Fennelly provides pragmatic cyber security expertise to help organizations bridge the gap between technical and business requirements. She authored the Center for Internet Security (CIS) Solaris and Red Hat benchmarks, which are used globally as configuration standards to secure IT systems. As a consultant, Carole has defined security strategies, and developed policies and procedures to implement them, at numerous Fortune 500 clients. Carole is a Certified Information Security Manager (CISM), Certified Security Compliance Specialist (CSCS), and Certified HIPAA Professional (CHP).

      Marko Diepold, IT Audit Manager
      audit2advise

      Picture of Marko Diepold, IT Audit Manager, audit2advise.

      Marko is an IT Audit Manager at audit2advise, where he delivers audit, risk advisory, and project management services. He has worked as a Security Officer, Quality Manager, and Consultant at some of Germany’s largest companies. He is a CISA and is ITIL v3 Intermediate and ITGCP certified.

      Research contributors and experts

      Martin Andenmatten, Founder & Managing Director
      Glenfis AG

      Picture of Martin Andenmatten, Founder and Managing Director, Glenfis AG.

      Martin is a digital transformation enabler who has been involved in various fields of IT for more than 30 years. At Glenfis, he leads large Governance and Service Management projects for various customers. Since 2002, he has been the course manager for ITIL® Foundation, ITIL® Service Management, and COBIT training. He has published two books on ISO 20000 and ITIL.

      Myles F. Suer, CIO Chat Facilitator
      CIO.com/Dell Boomi

      Picture of Myles F. Suer, CIO Chat Facilitator, CIO.com/Dell Boomi.

      Myles Suer, according to LeadTails, is the number 9 influencer of CIOs. He is also the facilitator for the CIOChat, which has executive-level participants from around the world in such industries as banking, insurance, education, and government. Myles is also the Industry Solutions Marketing Manager at Dell Boomi.

      Research contributors and experts

      Peter Sheingold, Portfolio Manager
      Cybersecurity, Homeland Security Center, The MITRE Corporation

      Picture of Peter Sheingold, Portfolio Manager, Cybersecurity, Homeland Security Center, The MITRE Corporation.

      Peter leads tasks that involve collaboration with the Department of Homeland Security (DHS) sponsors and MITRE colleagues and connect strategy, policy, organization, and technology. He brings a deep background in homeland security and strategic analysis to his work with DHS in the immigration, border security, and cyber mission spaces. Peter came to MITRE in 2005 but has worked with DHS from its inception.

      Robert D. Austin, Professor
      Ivey Business School

      Picture of Robert D. Austin, Professor, Ivey Business School.

      Dr. Austin is a professor of Information Systems at Ivey Business School and an affiliated faculty member at Harvard Medical School. Before his appointment at Ivey, he was a professor of Innovation and Digital Transformation at Copenhagen Business School, and, before that, a professor of Technology and Operations Management at the Harvard Business School.

      Research contributors and experts

      Ron Jones, Director of IT Infrastructure and Service Management
      DATA Communications

      Picture of Ron Jones, Director of IT Infrastructure and Service Management, DATA Communications.

      Ron is a senior IT leader with over 20 years of management experiences from engineering to IT Service Management and operations support. He is known for joining organizations and leading enhanced process efficiency and has improved software, hardware, infrastructure, and operations solution delivery and support. Ron has worked for global and Canadian firms including BlackBerry, DoubleClick, Cogeco, Infusion, Info-Tech Research Group, and Data Communications Management.

      Scott Genung, Executive Director of Networking, Infrastructure, and Service Operations
      University of Chicago

      Picture of Scott Genung, Executive Director of Networking, Infrastructure, and Service Operations, University of Chicago.

      Scott is an accomplished IT executive with 26 years of experience in technical and leadership roles. In his current role, Scott provides strategic leadership, vision, and oversight for an IT portfolio supporting 31,000 users consisting of services utilized by campuses located in North America, Asia, and Europe; oversees the University’s Command Center; and chairs the UC Cyberinfrastructure Alliance (UCCA), a group of research IT providers that collectively deliver services to the campus and partners.

      Research contributors and experts

      Steve Weil, CISSP, CISM, CRISC, Information Security Director, Cybersecurity Principal Consultant
      Point B

      Picture of Steve Weil, CISSP, CISM, CRISC, Information Security Director, Cybersecurity Principal Consultant, Point B.

      Steve has 20 years of experience in information security design, implementation, and assessment. He has provided information security services to a wide variety of organizations, including government agencies, hospitals, universities, small businesses, and large enterprises. With his background as a systems administrator, security consultant, security architect, and information security director, Steve has a strong understanding of both the strategic and tactical aspects of information security. Steve has significant hands-on experience with security controls, operating systems, and applications. Steve has a master's degree in Information Science from the University of Washington.

      Tony J. Read, Senior Program/Project Lead & Interim IT Executive
      Read & Associates

      Picture of Tony J. Read, Senior Program/Project Lead and Interim IT Executive, Read and Associates.

      Tony has over 25 years of international IT leadership experience, within high tech, computing, telecommunications, finance, banking, government, and retail industries. Throughout his career, Tony has led and successfully implemented key corporate initiatives, contributing millions of dollars to the top and bottom line. He established Read & Associates in 2002, an international IT management and program/project delivery consultancy practice whose aim is to provide IT value-based solutions, realizing stakeholder economic value and network advantage. These key concepts are presented in his new book: The IT Value Network: From IT Investment to Stakeholder Value, published by J. Wiley, NJ.

      Related Info-Tech research

      • Develop and Deploy Security Policies
      • Develop an Availability and Capacity Management Plan
      • Improve IT Operations Management
      • Develop an IT Infrastructure Services Playbook
      • Create a Right-Sized Disaster Recovery Plan
      • Develop a Business Continuity Plan
      • Implement IT Asset Management
      • Optimize Change Management
      • Standardize the Service Desk
      • Incident and Problem Management
      • Design & Build a User-Facing Service Catalog

      Bibliography

      “About Controls.” Ohio University, ND. Web. 2 Feb 2018.

      England, Rob. “How to implement ITIL for a client?” The IT Skeptic. Two Hills Ltd, 4 Feb. 2010. Web. 2018.

      “Global Corporate IT Security Risks: 2013.” Kaspersky Lab, May 2013. Web. 2018.

      “Information Security and Technology Policies.” City of Chicago, Department of Innovation and Technology, Oct. 2014. Web. 2018.

      ISACA. COBIT 5: Enabling Processes. International Systems Audit and Control Association. Rolling Meadows, IL.: 2012.

      “IT Policy & Governance.” NYC Information Technology & Telecommunications, ND. Web. 2018.

      King, Paula and Kent Wada. “IT Policy: An Essential Element of IT Infrastructure”. EDUCAUSE Review. May-June 2001. Web. 2018.

      Luebbe, Max. “Simplicity.” Site Reliability Engineering. O’Reilly Media. 2017. Web. 2018.

      Swartout, Shawn. “Risk assessment, acceptance, and exception with a process view.” ISACA Charlotte Chapter September Event, 2013. Web. 2018.

      “User Guide to Writing Policies.” Office of Policy and Efficiency, University of Colorado, ND. Web. 2018.

      “The Value of Policies and Procedures.” New Mexico Municipal League, ND. Web. 2018.

      Implement an IT Chargeback System

      • Buy Link or Shortcode: {j2store}71|cart{/j2store}
      • member rating overall impact: 8.0/10 Overall Impact
      • member rating average dollars saved: After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.
      • member rating average days saved: Read what our members are saying
      • Parent Category Name: Cost & Budget Management
      • Parent Category Link: /cost-and-budget-management
      • Business units voraciously consume IT services and don’t understand the actual costs of IT. This is due to lack of IT cost transparency and business stakeholder accountability for consumption of IT services.
      • Business units perceive IT costs as uncompetitive, resulting in shadow IT and a negative perception of IT.
      • Business executives have decided to implement an IT chargeback program and IT must ensure the program succeeds.

      Our Advice

      Critical Insight

      Price IT services so that business consumers find them meaningful, measurable, and manageable:

      • The business must understand what they are being charged for. If they can’t understand the value, you’ve chosen the wrong basis for charge.
      • Business units must be able to control and track their consumption levels, or they will feel powerless to control costs and you’ll never attain real buy-in.

      Impact and Result

      • Explain IT costs in ways that matter to the business. Instead of focusing on what IT pays for, discuss the value that IT brings to the business by defining IT services and how they serve business users.
      • Develop a chargeback model that brings transparency to the flow of IT costs through to business value. Demonstrate how a good chargeback model can bring about fair “pay-for-value” and “pay-for-what-you-use” pricing.
      • Communicate IT chargeback openly and manage change effectively. Business owners will want to know how their profit and loss statements will be affected by the new pricing model.

      Implement an IT Chargeback System Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should implement an IT chargeback program, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Launch

      Make the case for IT chargeback, then assess the financial maturity of the organization and identify a pathway to success. Create a chargeback governance model.

      • Implement IT Chargeback – Phase 1: Launch
      • IT Chargeback Kick-Off Presentation

      2. Define

      Develop a chargeback model, including identifying user-facing IT services, allocating IT costs to services, and setting up the chargeback program.

      • Implement IT Chargeback – Phase 2: Define
      • IT Chargeback Program Development & Management Tool

      3. Implement

      Communicate the rollout of the IT chargeback model and establish a process for recovering IT services costs from business units.

      • Implement IT Chargeback – Phase 3: Implement
      • IT Chargeback Communication Plan
      • IT Chargeback Rollout Presentation
      • IT Chargeback Financial Presentation

      4. Revise

      Gather and analyze feedback from business owners, making necessary modifications to the chargeback model and communicating the implications.

      • Implement IT Chargeback – Phase 4: Revise
      • IT Chargeback Change Communication Template
      [infographic]

      Workshop: Implement an IT Chargeback System

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Kick-Off IT Chargeback

      The Purpose

      Make the case for IT chargeback.

      Identify the current and target state of chargeback maturity.

      Establish a chargeback governance model.

      Key Benefits Achieved

      Investigated the benefits and challenges of implementing IT chargeback.

      Understanding of the reasons why traditional chargeback approaches fail.

      Identified the specific pathway to chargeback success.

      Activities

      1.1 Investigate the benefits and challenges of implementing IT chargeback

      1.2 Educate business owners and executives on IT chargeback

      1.3 Identify the current and target state of chargeback maturity

      1.4 Establish chargeback governance

      Outputs

      Defined IT chargeback mandate

      IT chargeback kick-off presentation

      Chargeback maturity assessment

      IT chargeback governance model

      2 Develop the Chargeback Model

      The Purpose

      Develop a chargeback model.

      Identify the customers and user-facing services.

      Allocate IT costs.

      Determine chargeable service units.

      Key Benefits Achieved

      Identified IT customers.

      Identified user-facing services and generated descriptions for them.

      Allocated IT costs to IT services.

      Identified meaningful, measurable, and manageable chargeback service units.

      Activities

      2.1 Identify user-facing services and generate descriptions

      2.2 Allocate costs to user-facing services

      2.3 Determine chargeable service units and pricing

      2.4 Track consumption

      2.5 Determine service charges

      Outputs

      High-level service catalog

      Chargeback model

      3 Communicate IT Chargeback

      The Purpose

      Communicate the implementation of IT chargeback.

      Establish a process for recovering the costs of IT services from business units.

      Share the financial results of the charge cycle with business owners.

      Key Benefits Achieved

      Managed the transition to charging and recovering the costs of IT services from business units.

      Communicated the implementation of IT chargeback and shared the financial results with business owners.

      Activities

      3.1 Create a communication plan

      3.2 Deliver a chargeback rollout presentation

      3.3 Establish a process for recovering IT costs from business units

      3.4 Share the financial results from the charge cycle with business owners

      Outputs

      IT chargeback communication plan

      IT chargeback rollout presentation

      IT service cost recovery process

      IT chargeback financial presentation

      4 Review the Chargeback Model

      The Purpose

      Gather and analyze feedback from business owners on the chargeback model.

      Make necessary modifications to the chargeback model and communicate implications.

      Key Benefits Achieved

      Gathered business stakeholder feedback on the chargeback model.

      Made necessary modifications to the chargeback model to increase satisfaction and accuracy.

      Managed changes by communicating the implications to business owners in a structured manner.

      Activities

      4.1 Address stakeholder pain points and highly disputed costs

      4.2 Update the chargeback model

      4.3 Communicate the chargeback model changes and implications to business units

      Outputs

      Revised chargeback model with business feedback, change log, and modifications

      Chargeback change communication

      Modernize and Transform Your End-User Computing Strategy

      • Buy Link or Shortcode: {j2store}308|cart{/j2store}
      • member rating overall impact: 9.6/10 Overall Impact
      • member rating average dollars saved: $34,982 Average $ Saved
      • member rating average days saved: 25 Average Days Saved
      • Parent Category Name: End-User Computing Strategy
      • Parent Category Link: /end-user-computing-strategy

      IT needs to answer these questions:

      • What types of computing devices, provisioning models, and operating systems should be offered to end users?
      • How will IT support devices?
      • What are the policies and governance surrounding how devices are used?
      • What actions are we taking and when?
      • How do end-user devices support larger corporate priorities and strategies?

      Your answers need to balance choice, risk, and cost.

      Our Advice

      Critical Insight

      • Even if a user has a prestigious tablet, if the apps aren’t built well, they can’t get support on it, or they can’t connect, then that device is useless. Focus on supportability, use cases, connection, and policy – and the device.

      Impact and Result

      • Identify desired benefits that align to IT and corporate priorities and strategies.
      • Perform a persona analysis.
      • Define a vision for end-user computing.
      • Define the standard device and app offerings.
      • Improve the supporting services surrounding devices.
      • Develop a roadmap for implementing your strategy.

      Modernize and Transform Your End-User Computing Strategy Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. End-User Computing Strategy Deck – A step-by-step document to walk you through end-user computing trends and processes to improve customer satisfaction.

      This storyboard will help you identify your goals, build standard offerings for users, define governance and policies around offerings, and develop a roadmap for your EUC program.

      • Modernize and Transform Your End-User Computing Strategy – Phases 1-3

      2. End-User Computing Strategy Template – A repository for your current-state and persona analysis to identify technology requirements for each user group.

      Use these templates to document your end-user computing strategy. Follow the guidelines in the blueprint and record activity results in the template. The findings will be presented to the management team.

      • End-User Computing Strategy Template
      • User Group Analysis Workbook

      3. End-User Computing Ideas Catalog and Standard Offering Guide – Templates that guide you to document the outcome from persona analysis to define standard offerings and policies.

      The Ideas Catalog introduces provisioning models, form factors, and supported operating systems. Use the Standard Offering Template to document provisioning models and define computing devices along with apps and peripherals according to the outcome of the user group analysis.

      • Standard End-User Entitlements and Offerings Template
      • End-User Computing Ideas Catalog

      4. End-User Computing Policies – Policies that establish requirements for end-user computing.

      Use these policy templates to communicate the purposes behind each end-user computing decision and establish company standards, guidelines, and procedures for the purchase of technologies. The policies will ensure purchasing, reimbursement, security, and remote wiping enforcements are consistent and in alignment with the company strategy.

      • Mobile Device Connectivity & Allowance Policy
      • Purchasing Policy
      • Mobile Device Reimbursement Agreement
      • Mobile Device Reimbursement Policy
      • BYOD Acceptable Use Policy
      • Mobile Device Remote Wipe Waiver Template
      • General Security – User Acceptable Use Policy
      • Device Entitlement Policy Template

      Infographic

      Workshop: Modernize and Transform Your End-User Computing Strategy

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Set the Direction

      The Purpose

      Dig into the current state and build user persona.

      Key Benefits Achieved

      Determine your challenges and strengths.

      Delineate user IT requirements.

      Activities

      1.1 Assess the current state of end-user computing.

      1.2 Perform SWOT analysis.

      1.3 Map benefits to stakeholder drivers and priorities.

      1.4 Identify user groups.

      1.5 Identify supporting technology.

      1.6 Identify opportunities to provide value.

      Outputs

      SWOT analysis of current state

      Goals cascade

      Persona analysis

      2 Define the Offering

      The Purpose

      Define your EUC vision and standard offerings.

      Key Benefits Achieved

      Brainstorm EUC vision and mission.

      Find out the standard offerings.

      Set the direction for end-user computing to support shift-left enablement.

      Activities

      2.1 Prioritize benefits.

      2.2 Craft a vision and mission statement.

      2.3 Identify goals.

      2.4 Define guiding principles for your strategy.

      2.5 Select a provisioning model for each persona.

      2.6 Define the standard device offerings.

      2.7 Document each persona's entitlements.

      Outputs

      Vision statement, mission statement, and guiding principles

      Goals and indicators

      End-user device entitlements standard

      3 Support the Offering

      The Purpose

      Outline supporting practices and define policies for each use case.

      Key Benefits Achieved

      Document supporting practices.

      Document EUC policies.

      Activities

      3.1 Define device management tools and approach.

      3.2 Identify groups involved in supporting practices.

      3.3 Identify opportunities to improve customer service.

      3.4 Define acceptable use.

      3.5 Define BYOD policies.

      3.6 Define procurement and entitlement policies.

      3.7 Define security policies.

      Outputs

      List of management tools for end-user computing

      Roles and responsibilities for maintaining the end-user computing environment

      Opportunities to improve customer service

      End-user computing policy templates

      4 Bridge the Gap and Create the Roadmap

      The Purpose

      Build a user migration roadmap.

      Key Benefits Achieved

      Make the project a reality by documenting initiatives and building a roadmap.

      Activities

      4.1 Identify the gaps in devices, user support, use cases, policy & governance, and fitness for use.

      4.2 Plan the deployment and user migration journey.

      4.3 Document initiatives in the roadmap.

      Outputs

      Initiatives mapped to practice areas

      User migration journey map

      Further reading

      Modernize and Transform Your End-User Computing Strategy

      Support the workforce of the future.

      EXECUTIVE BRIEF

      Analyst Perspective

      Focus beyond the device

      It’s easy to think that if we give end users nice devices, then they will be more engaged and they will be happy with IT. If only it were that easy.

      Info-Tech Research Group has surveyed over 119,000 people through its CIO Business Vision diagnostic. The results show that a good device is necessary but not enough for high satisfaction with IT. Once a user has a decent device, the other aspects of the user’s experience has a higher impact on their satisfaction with IT.

      After all, if a person is trying to run apps designed in the 1990s, if they are struggling to access resources through an underperforming VPN connection, or if they can’t get help when their devices and apps aren’t working, then it doesn’t matter that you gave them a state-of-the-art MacBook or Microsoft Surface.

      As you build out your end-user computing strategy to reflect the new reality of today’s workforce, ensure you focus on shifting user support left, modernizing apps to support how users need to work, and ensuring that your network and collaboration tools can support the increased demands. End-user computing teams need to focus beyond the device.

      Ken Weston, ITIL MP, PMP, Cert.APM, SMC

      Research Director, Infrastructure and Operations Info-Tech Research Group

      Mahmoud Ramin, PhD

      Senior Research Analyst, Infrastructure and Operations Info-Tech Research Group

      Executive Summary

      Your Challenge

      IT needs to answer these questions:

      • What types of computing devices, provisioning models, and operating systems (OSes) should be offered to end users?
      • How will IT support devices?
      • What are the policies and governance surrounding how devices are used?
      • What actions are we taking and when?
      • How do end-user devices support larger corporate priorities and strategies?

      Your answers need to balance choice, risk, and cost.

      Common Obstacles

      Management paradigms have shifted:

      • OSes, device management, and IT asset management (ITAM) practices have changed.
      • Users expect full capabilities on any personal device.
      • Virtual desktops are switching to the cloud.
      • Low-code/no-code platforms allow the business to manage their own apps or comanage with IT.
      • Work-from-anywhere is the default.
      • Users have higher customer service expectations.

      Take end-user computing beyond the OS.

      Info-Tech's Approach

      This blueprint will help you:

      • Identify desired benefits that align to IT and corporate priorities and strategies.
      • Perform a persona analysis.
      • Define a vision for end-user computing.
      • Define the standard device and app offerings.
      • Improve the supporting services surrounding devices.
      • Develop a roadmap for implementing your strategy.

      A good device is necessary for satisfaction with IT but it’s not enough.

      If a user has a prestigious tablet but the apps aren’t built well, they can’t get support on it, or they can’t connect to the internet, then that device is useless. Focus on supportability, use cases, connection, policy – and device.

      Your challenge

      This blueprint will help you build a strategy that answers these questions:

      • What types of computing devices should be offered to end users?
      • What provisioning models will be used?
      • What operating systems are supported?
      • How will IT support devices?
      • What are the policies and governance surrounding how devices are used?
      • What actions are we taking and when?
      • How do end-user devices support larger corporate priorities and strategies?

      Definition: End-User Computing (EUC)

      End-user computing (EUC) is the domain of information and technology that deals with the devices used by workers to do their jobs. EUC has five focus areas: devices, user support, use cases, policy & governance, and fitness for use.

      A good end-user computing strategy will effectively balance:

      User Choice

      Cost

      Risk

      The right balance will be unique for every organization.

      Strike the right balance

      The discussion is larger than desktop support

      If IT is an influencer, then you get to drive this conversation. If IT is not an influencer, then you need to support whatever option the business wants.

      Cost Risk Choice Result
      Higher Education High importance Low importance High importance Full BYOD for professors. Standardized offerings for administration.
      Software Development Firms Low importance Medium/High importance High importance Standardized offerings for developers. Virtual desktops for users on BYOD.
      Legal Firm Medium importance High importance Low importance Partners offered prestigious devices. Everyone else uses Windows PCs. Virtual desktops and apps for remote access.

      Healthcare

      High importance High importance Low importance Nurses, janitors, and other frontline staff use shared tablets. Doctors are provisioned their own tablet. Admin staff and doctors are provisioned virtual desktops to maintain security and compliance.
      Government High importance High importance Low importance Standardized PC offerings for all employees. MacBooks are provided with justification. Devices managed with Intune and ConfigMgr.

      Good devices are necessary for overall IT satisfaction

      BUT

      Good devices are not enough for high satisfaction

      A bad device can ruin a person’s satisfaction with IT

      Info-Tech’s CIO Business Vision has shown that when someone is dissatisfied with their device, their satisfaction with IT overall is only 40.92% on average.

      When a person is satisfied with their device, their average satisfaction increases by approximately 30 percentage points to 70.22%. (Info-Tech Research Group, CIO Business Vision, 2021; N=119,383)

      The image is a bar graph, with the Y-axis labelled Overall IT Satisfaction. There are two bars, one labelled Satisfied With Devices, which is at 70.22%, and the other labelled Dissatisfied With Devices, which is at 40.92%.

      Improvements in the service desk, business apps, networks and communication infrastructure, and IT policy all have a higher impact on increasing satisfaction.

      For every one-point increase in satisfaction in those areas, respondents’ overall satisfaction with IT increased by the respective percentage of a point. (Info-Tech Research Group, CIO Business Vision, 2021; N=119,409)

      The image shows a graphic of five arrows pointing upwards. They are labelled (from right to left): Devices--42.20%; IT Policy--45.90%; Network & Comms Infra--59.49%; Business Apps--63.89%; Service Desk--65.19%, 1.54 times the impact of devices.

      End-User Paradigms Have Shifted

      Take end-user computing beyond the device

      Operating System - OS

      Only Windows

      • More choices than ever before

      Endpoint Management System - UEM

      Group Policy & Client Management

      • Modern & Unified Endpoint Management

      Personal Devices - BYOD

      Limited to email on phones

      • Full capabilities on any device

      IT Asset Management - ITAM

      Hands-on with images

      • Zero-touch with provisioning packages

      Virtual Desktops - DaaS

      Virtual Desktop Infrastructure in the Data Center

      • Desktop-as-a-Service in the cloud

      Business-Managed Apps - BMA

      Performed by IT

      • Performed by the Business and IT

      Work-From-Anywhere - WFA

      Rare

      • Default

      Customer Satisfaction - C Sat

      Phone calls and transactional interactions

      • Self-serve & managing entire experience

      Don’t limit your focus to only Windows and Macs

      Android is the OS with the largest market share

      Users and IT have more choices than ever before

      Operating System - OS

      Only Windows

      • More choices than ever before

      Microsoft is still the dominant player in end-user computing, but Windows has only a fraction of the share it once had.

      IT needs to revisit their device management practices. Modern management tools such as unified endpoint management (UEM) tools are better suited than traditional client management tools (CMT) for a cross-platform world.

      IT must also revisit their application portfolios. Are business apps supported on Android and iOS or are they only supported on Windows? Is there an opportunity to offer more options to end users? Are end users already running apps and handling sensitive data on Android and iOS through software-as-a-service and bring-your-own-device (BYOD) capabilities in Office 365 and Google apps?

      The image shows a bar graph titled OS Market Share, 2011-2021. On the x-axis are OS names with a bar in blue representing their market share in 2011, and a bar in purple showing their market share in 2021. The data shown is as follows: Windows--85.98% (2011), 31.62% (2021); Android--1.22% (2011), 40.85% (2021); iOS--2.1% (2011), 16.42% (2021); Mac OS X--6.19% (2011); 6.8% (2021); Other--4.51% (2011), 4.31% (2021). Source: StatCounter Global Stats.

      OS market share is partly driven by the digital divide

      If someone must choose between a smartphone and a computer, they go with a smartphone

      IT can’t expect everyone to be fluent on Windows and Mac, have a computer at home, or even have home broadband.

      Of US adults aged 18-29:

      • 96% have a smartphone (the rest have cellphones).
      • Only 70% of US adults aged 18-29 have a home broadband connection.

      Further, only 59% of US adults making less than $30,000/year have a laptop or desktop. (“Mobile Technology” and “Digital Divide,” Pew Research, 2021.)

      Globally, people are likelier to have a cell subscription than they are to have access to broadband.

      The image is a bar graph, with a list of countries on the X-axis, with each having two bars: blue indicating Fixed Broadband Subscriptions per 100 people and purple indicating Mobile Cellular Subscriptions per 100 people. In all listed countries, the number of Mobile Cellular Subscriptions per 100 people is higher than Fixed Broadband Subscriptions. Source: The World Bank, 2020. Most recent data for USA mobile cellular subscriptions is from 2019.

      Embrace new device management paradigms

      Endpoint Management System - UEM

      Group Policy & Client Management

      • Modern & Unified Endpoint Management

      Evaluate enterprise mobility management and unified endpoint management to better support a remote-first, cross-platform reality.

      Client Management Tool (CMT)

      CMTs such as Microsoft Endpoint Configuration Manager (ConfigMgr, aka SCCM) can be used to distribute apps, apply patches, and enforce group policy.

      Enterprise Mobility Management (EMM)

      EMM tools allow you to manage multiple device platforms through mobile device management (MDM) protocols. These tools enforce security settings, allow you to push apps to managed devices, and monitor patch compliance through reporting.

      EMM tools often support mobile application management (MAM) and mobile content management (MCM). Most EMM tools can manage devices running Windows, Mac OS, iOS, and Android, although there are exceptions.

      Unified Endpoint Management (UEM)

      UEM solutions combine CMT and EMM for better control of remote computers running Windows or Macs. Examples include:

      • Windows devices comanaged by Intune and ConfigMgr.
      • Mac devices managed by Jamf Pro.
      • Mac devices comanaged by Jamf Pro and Intune.

      Most UEM tools can manage devices running Windows, Mac OS, iOS, and Android, allowing IT to manage all end-user devices from a unified tool set (although there are exceptions).

      Mobile Application Management (MAM)

      MAM provides the ability to package an app with security settings, distribute app updates, and enforce app updates. Some capabilities do not require apps to be enrolled in an EMM or UEM solution.

      Mobile Content Management (MCM)

      MCM tools distribute files to remote devices. Many MCM solutions allow for security settings to be applied, such as encrypting the files or prohibiting data from leaving the secure container. Examples include OneDrive, Box, and Citrix ShareFile.

      Adopt modern management with EMM and UEM – better toolsets for today’s state of EUC

      Sacrifice your Group Policy Objects to better manage Windows computers

      Windows Management Features Traditional CMT Hybrid UEM Cloud-Based EMM
      Group Policy ✔ Primary management approach ✔ Available alongside configuration service providers X Replaced by configuration service providers
      Manage remote devices without VPN X X
      No longer manage and maintain images X ✔ Images are still available ✔ Images replaced by provisioning packages
      Secure and support BYOD X (Certain tools may offer limited MDM capabilities)
      Support remote zero-touch provisioning X (Only available via PXE boot)
      App, patch, update deployments Via defined distribution points Via defined distribution points or MAM Via MAM

      IT asset management practices are shifting

      IT Asset Management - ITAM

      Hands-on with images

      • Zero-touch with provisioning packages

      Supply chain issues are making computers longer to procure, meaning users are waiting longer for computers (Cision, 2021). The resulting silicon chip shortage is expected to last until at least 2023 (Light Reading, 2021).

      IT departments are delaying purchases, delaying refreshes, and/or purchasing more to reserve devices before they need them.

      Remote work has increased by 159% over the past 12 years (NorthOne, 2021). New hires and existing users can’t always go into the office to get a new computer.

      IT departments are paying vendors to hold onto computers and then drop-ship them directly to the end user. The devices are provisioned using zero touch (e.g. Autopilot, Apple Device Manager, or another tool). Since zero-touch provisioning tools do not support images, teams have had to switch to provisioning packages.

      The pandemic saw an increase in spending on virtual desktops

      Virtual desktops offered powerful tools for supporting remote devices and personal computers without compromising sensitive data

      Virtual Desktops - DaaS

      Virtual Desktop Infrastructure in the Data Center

      • Desktop-as-a-Service in the cloud

      The pandemic helped cloud-based virtual desktop infrastructure (VDI)

      Citrix saw subscription revenue increase 71% year over year in 2020 (Citrix 2020 Annual Report, p. 4). VMware saw subscription and SaaS revenue increase 38% from January 2020 to 2021 – while on-premises licensing revenue decreased by 5% (VMware Annual Report 2021, p. 40).

      IT no longer needs to manage the underlying infrastructure

      Microsoft and AWS are offering desktops as a service (i.e. cloud-based virtual desktops). IT needs to manage only the device, not the underlying virtual desktop infrastructure. This is in addition to Citrix’s and VMware’s cloud offerings, where IT doesn’t need to manage the underlying infrastructure that supports VDI.

      Visit the blueprint Implement Desktop Virtualization and Transition to Everything as a Service to get started.

      Work-from-anywhere (WFA) is now the default

      COVID-19 forced this shift

      Work-From-Anywhere - WFA

      Rare

      • Default

      Be prepared to support a hybrid workforce, where people are sometimes working remotely and sometimes working in the office.

      • Device provisioning and deployment need to be rethought. In-person deployment is not always possible. IT should evaluate tools such as zero-touch provisioning.
      • Service desks need better monitoring and management tools. End-user experience management (EUEM) can allow you to better identify where network issues are occurring – in your data center, at the user’s house, in the cloud, or somewhere in between. Remote control tools can then allow your tier 1 to remediate issues on the user’s device.
      • Apps and devices need to be usable from anywhere. Environments that rely on desktops and on-premises apps need to be rearchitected for a remote-first workforce.
      • Users are living inside video conferencing tools. With the impact of the COVID-19 pandemic, there are about 145 million daily users of Microsoft Teams, almost twice the number of users in 2020 (MUO, 2021). Ensure they have the training and expertise to effectively use these tools.

      “More technical troubleshooting due to users working from home a lot more. It can be more difficult to talk users through fixes when they are off site if you cannot remotely assist so more emphasis on the communication skill which was already important.” (Service Desk Institute, 2021)

      Visit the Hybrid Workplace Research Center to better support a hybrid workforce.

      BYOD fully includes personal computers

      It’s no longer about whether IT will allow BYOD

      Stop pretending BYOD doesn’t happen

      Personal Devices - BYOD

      Limited to email on phones

      • Full capabilities on any device
      • BYOD (including BYOPC) is turned on by default. SaaS tools like Office 365 are built to be used on multiple devices, including multiple computers. Further, the pandemic saw 47% of organizations significantly increase their use of BYOD (Cybersecurity Insiders, 2021; N=271).
      • BYOD can boost productivity. When employees can use smartphones for work, they report that it increases their productivity by 34 percent (Samsung Insights, 2016).
      • BYOD is hard to support, so most organizations don’t. Only 22% of organizations provide full support for mobile devices, while 20% provide no support, 25% provide ad hoc support, and 26% provide limited support (Cybersecurity Insiders, 2021). If smartphones and tablets are heavily ingrained in business processes, then migrating to BYOD can overload the service desk.
      • Securely enable employees. Mobile application management (MAM), mobile content management (MCM), and Office 365 have gotten smarter at protecting corporate data.

      Action Item: Identify how IT can provide more support to personally owned computers, tablets, and smartphones.

      58% of working Americans say their work devices are “awful to work on." (PCMag, 2021)

      But only 22% of organizations provide full support to BYOD. (Cybersecurity Insiders, 2021)

      IT must either provide better devices or start fully supporting users on personal PCs.

      Build governance practices for low-code development platforms

      Managing 1,000 different apps built out on low-code business process management platforms is hard, but it’s not nearly as hard as managing 1,000 unique SaaS apps or access databases

      Business-Managed Apps - BMA

      Performed by IT

      • Performed by the Business and IT

      Pros - Opportunities

      • Offers DIY to users
      • Business can build them quickly
      • IT has central visibility
      • IT can focus on the platform

      Cons - Threats

      • Sensitive data can get exposed
      • Users may have issues with continuity and backup
      • Responding to platform changes will be potentially challenging
      • Support may be difficult after the app creator leaves

      Action Item: Build a governance framework that describes the roles and responsibilities involved in business-owned apps. Identify the user’s role and end-user computing’s role in supporting low-code apps.

      Visit the blueprint Embrace Business-Managed Apps to learn how to build a governance framework for low-code development platforms.

      Visit the Low-Code Business Process Management SoftwareReviews category to compare different platforms.

      Update your customer service practices

      End users expect self-service and help from tier 1

      Re-evaluate how you support both corporate-issued and personal-owned computers and mobile devices

      Customer Satisfaction - C Sat

      Phone calls and transactional interactions

      • Self-serve & managing entire experience

      Microsoft’s 2019 “Global State of Customer Service” report shows that people have high expectations:

      • 31% of people expect call agents to have a “deep understanding of the caller’s relationship with the company”
      • 11% expect self-service capabilities

      End users have the same expectations of IT, the service desk, and end-user computing teams:

      • Users expect any IT person with whom they are talking to have a deep understanding of their devices, apps, open tickets, and closed tickets.
      • Users expect tier 1 to be able to resolve their incidents and requests without escalating to tier 2 or tier 3 end-user computing specialists.

      Most Important Aspects of Customer Service

      Resolving issue in one interaction - 35%

      Knowledgeable agent - 31%

      Finding information myself - 11%

      Not repeating information - 20%

      (Microsoft, 2019)

      Desktop engineering needs to shift left

      Revisit what work can only be done by tier 2 and tier 3 teams

      Shifting left involves shifting resolution of incidents and service requests down from more costly resources to the first line of support and to end users themselves through self-service options

      • Tier 1 needs up-to-date information on the end users’ devices and open tickets.
      • Users should be able to request apps and download those apps through a self-service portal, a software catalog, or an app store.
      • Tier 1 needs to be empowered to remote wipe devices, see troubleshooting and diagnostics information, and resolve incidents without needing to escalate.

      Action Item: Apply shift-left enablement to train tier 1 agents on troubleshooting more incidents and fulfilling more service requests. Build top-notch self-service capabilities for end users.

      The image is a graphic titled Shift-Left Strategy. At the top, it lists Auto-Fix; User, Tier 1, Tier 2/3, and Vendor. On the left, it lists Metrics vertically: Cost, Time, Satisfaction. A bar displays how high or low the metric is based on the categories listed at the top.

      Work with your service desk on the blueprint Optimize the Service Desk with a Shift-Left Strategy.

      Windows 11 is coming

      Prepare to make the jump

      The sooner you start, the easier the migration will be

      • Begin planning hardware refreshes. Old computers that do not have a TPM 2.0 chip are not currently supported on Windows 11 (“Enable TPM 2.0,” Microsoft, 2021). If you have old computers that will not support the jump to Windows 11– especially given the supply chain disruptions and silicon chip shortages – it is time to consider computer upgrades.
      • The end of Windows 10 is coming. Windows 10’s retirement date is currently October 14, 2025 (“Windows 10 Home and Pro,” Microsoft, 2021). If you want to continue running Windows 10 on older computers beyond that time, you will need to pay for extended support or risk those computers being more easily breached.
      • Begin testing your apps internally. Run Windows 11 within IT and test whether your apps will work on Windows 11.
      • Pilot Windows 11 with IT-friendlies. Find users that are excited for Windows 11 and will not mind a bit of short-term pain.
      • What is your risk appetite? Risk-averse organizations will want to wait until Microsoft, DISA, and/or Center for Internet Security have published security configuration best practices.

      Info-Tech’s approach

      Master the ever-expanding puzzle of end-user computing

      User Group Analysis

      Supported Devices and Apps

      Fitness for Use

      Device Support

      The Info-Tech difference:

      1. Balance user choice, risk mitigation, and cost optimization. The right balance will be unique for every organization.
      2. Standardize the nonstandard. Anticipate your users’ needs by having power options and prestigious options ready to offer.
      3. Consider multiple personas when building your standards, training, and migrations. Early Adopters, Late Adopters, VIP Users, Road Warriors, and Hoarders – these five personas will exist in one form or another throughout your user groups.

      Modernize and Transform Your End-User Computing Strategy

      Focus on the Big Picture

      End-User Paradigms Have Shifted

      Take end-user computing beyond the device

      Operating System - OS

      Only Windows

      • More choices than ever before

      Endpoint Management System - UEM

      Group Policy & Client Management

      • Modern & Unified Endpoint Management

      Personal Devices - BYOD

      Limited to email on phones

      • Full capabilities on any device

      IT Asset Management - ITAM

      Hands-on with images

      • Zero-touch with provisioning packages

      Virtual Desktops - DaaS

      Virtual Desktop Infrastructure in the Data Center

      • Desktop-as-a-Service in the cloud

      Business-Managed Apps - BMA

      Performed by IT

      • Performed by the Business and IT

      Work-From-Anywhere - WFA

      Rare

      • Default

      Customer Satisfaction - C Sat

      Phone calls and transactional interactions

      • Self-serve & managing entire experience

      Don't just focus on the device!

      Improvements in the service desk, business apps, networks and communication infrastructure, and IT policy have a higher impact on increasing satisfaction.

      Impact of End-User Satisfaction of IT by Area Compared to Devices

      Devices (x1.0)

      IT Policy (x1.09)

      Network & Communications Infrastructure (x1.41)

      Business Apps (x1.51)

      Service Desk (x1.54)

      (Info-Tech Research Group, CIO Business Vision, 2021; n=119,409)

      Build your strategy with these components...

      End-User Group Analysis

      • Work location
      • Information interactions
      • Apps
      • Data and files
      • Business capabilities
      • Current offering
      • Pain points
      • Desired gains

      Supported Devices & Apps

      • Primary computing device offerings
      • Power computing device offering
      • Prestigious device offerings
      • Secondary computing device offerings
      • Provisioning models
      • Standard apps
      • Peripherals

      Device Support

      • Self-service
      • Service Desk
      • Specialists

      Fitness for Use

      • Organizational policies
      • Security policies

      Vision

      ...to answer these questions:

      1. What devices will people have?
      2. How will you support these devices?
      3. How will you govern these devices?

      Balance choice, risk, and cost

      The right balance will be unique for every organization. Get the balance right by aligning your strategy's goals to senior leadership’s most important priorities.

      • User choice
      • Risk
      • Cost

      + Standardize the non-standard

      Have a more prestigious option ready for users, such as VIPs, who want more than the usual offerings. This approach will help you to proactively anticipate your users' needs.

      +Consider multiple personas when building your standards, training, and migrations

      These five personas will exist in one form or another throughout your user groups.

      • Early Adopters
      • Late Adopters
      • VIP Users
      • Road Warriors
      • Hoarders

      Use our approach to answer these questions:

      What computers will people have?

      Types of computing devices

      • Power desktop
      • Power laptop
      • Desktop
      • Laptop
      • Virtual Desktop
      • Thin Client Device
      • Pro Tablet
      • Tablet
      • Smartphone

      Corporate-Issued Approaches

      • Kiosk – Shared, Single Purpose
      • Pooled – Shared, Multipurpose
      • Persistent – Individual
      • Personally Owned

      Supported Operating Systems

      • Windows
      • Mac
      • Chrome OS
      • Linux
      • iOS/iPad OS
      • Android

      How will you support these devices?

      Device Management

      • Manual
      • CMT
      • EMM
      • UEM
      • Pooled Virtual Desktop Manager

      Supporting Practices

      • Self-Service
      • Tier 1 Support
      • Specialist Support

      How will you govern these devices?

      Corporate Policies

      • Personal Use Allowed?
      • Management and Security Policies
      • Personal Device Use Allowed?
      • Supported Apps and Use Cases
      • Who Is Allowed to Purchase?
      • Prohibited Apps and Use Cases
      • Device Entitlement
      • Stipends and/or Reimbursement to Users

      Use our blueprint to improve your EUC practices

      1. Devices
        • Corporate-issued devices
        • Standard offerings
      2. User Support
        • Self-service
        • Tier 1 support
      3. Use Cases
        • Providing value
        • Business apps
      4. Policy & Governance
        • Personal device use
        • IT policy
      5. Fitness for Use
        • Securing devices
        • Patching

      Info-Tech’s methodology for end-user computing strategy

      1. Set the Direction 2. Define the Offering 3. Build the Roadmap
      Phase Steps

      1.1 Identify Desired Benefits

      1.2 Perform a User Group Analysis

      1.3 Define the Vision

      2.1 Define the Standard Offerings

      2.2 Outline Supporting Services

      2.3 Define Governance and Policies

      3.1 Develop Initiatives
      Phase Outcomes

      Current-State Assessment

      Goals Cascade

      User Group Assessment

      Vision Statement

      Mission Statement

      Guiding Principles

      Standard Offerings by User Group

      Device Management Model

      Technical Support Model

      Device Entitlement Policy

      Acceptable Use Policy

      Remote Wipe Policy & Waiver

      Personal Device Reimbursement Policy

      End-User Migration Journey Map

      Strategy and Roadmap

      Insight summary

      Once users are satisfied with devices, focus on the bigger picture

      If end users are dissatisfied with devices, they will also be dissatisfied with IT. But if you don’t also focus on apps and supportability, then giving users better devices will only marginally increase satisfaction with IT.

      Bring it back to stakeholder priorities

      Before you build your vision statement, make sure it resonates with the business by identifying senior leadership’s priorities and aligning your own goals to them.

      Balance choice, risk, and cost

      The balance of user choice, risk mitigation, and cost optimization is unique for each company. Get the balance right by aligning your strategy’s goals to senior leadership’s most important priorities.

      Communicate early and often with users

      Expect users to become anxious when you start targeting their devices. Address this anxiety by bringing them into the conversation early in the planning – they will see that their concerns are being addressed and may even feel a sense of ownership over the strategy.

      Standardize the nonstandard

      When users such as VIP users want more than the standard offering, have a more prestigious option available. This approach will help you to proactively anticipate your users’ needs.

      Consider multiple personas when building your standards, training, and migrations

      Early Adopters, Late Adopters, VIP Users, Road Warriors, and Hoarders – these five personas will exist in one form or another throughout your user groups.

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

      User Group Analysis Workbook

      Use these worksheets to guide your analysis.

      End-User Computing Ideas Catalog

      Compare options for your end-user computing environment.

      Standard End-User Entitlements and Offerings

      Define your supported offerings and publish this document in your service catalog.

      Policy Templates

      Use these templates as a starting point for addressing policy gaps.

      Key deliverable:

      End-User Computing Strategy

      Document your strategy using this boardroom-ready template.

      Blueprint benefits

      IT Benefits

      • Deliver immediate value to end users.
      • Provide the best service based on the user persona.
      • Provide better device coverage.
      • Use fewer tools to manage a less diverse but equally effective array of end-user computing devices.
      • Provide more managed devices that will help to limit risk.
      • Have better visibility into the end-user computing devices and apps.

      Business Benefits

      • Conduct corporate business under one broad strategy.
      • Provide support to IT for specific applications and devices.
      • Take advantage of more scalable economies for providing more advantageous technologies.
      • Experience less friction between end users and the business and higher end-user satisfaction.

      Measure the value of this blueprint

      Your end-user computing strategy is an investment

      Track the returns on your investment, even if those returns are soft benefits and not cost reductions

      User Satisfaction

      • Satisfaction with device
      • Satisfaction with business apps
      • Satisfaction with service desk timeliness
      • Satisfaction with service desk effectiveness
      • Satisfaction with IT Employee engagement

      Total Cost

      • Spend on each type of device
      • Cost of licenses for management tools, operating systems, and apps
      • Cost of support agreements # of support tickets per device per employee
      • Time spent supporting devices per tier or support team
      • Time spent per OS/app release

      Risk Mitigation

      • # of devices that are end-of-life
      • % of devices in compliance
      • # of unmanaged devices
      • # of devices that have not checked in to management tool

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful."

      Guided Implementation

      "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track."

      Workshop

      "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place."

      Consulting

      "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks are used throughout all four options.

      Guided Implementation

      What does a typical GI on this topic look like?

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is 8 to 10 calls over the course of 4 to 6 months.

      Phase 1: Set the Direction

      • Call #1: Review trends in end-user computing and discuss your current state.
      • Call #2: Perform a user group analysis.
      • Call #3: Identify desired benefits and map to stakeholder drivers.

      Phase 2: Define the Offering

      • Call #4: Define standard offerings.
      • Call #5: Select provisioning models.
      • Call #6: Outline supporting services and opportunities to shift end-user computing support left.
      • Call #7: Identify gaps in governance and policies.

      Phase 3: Build the Roadmap

      • Call #8: Develop initiatives.
      • Call #9: Plan migration and build roadmap.

      EUC Strategy Workshop Overview

      Contact your account representative for more information.

      workshops@infotech.com 1-888-670-8889

      Day 1 Day 2 Day 3 Day 4 Day 5
      Set the Direction Define the Offering Support the Offering Bridge the Gap and Create the Roadmap Next Steps and Wrap-Up (offsite)
      Activities

      1.1 Identify desired benefits.

      1.1.1 Assess the current state of end-user computing.

      1.1.2 Perform a SWOT analysis.

      1.1.3 Map benefits to stakeholder drivers and priorities.

      1.2 Analyze user groups.

      1.2.1 Identify user groups.

      1.2.2 Identify supporting technology.

      1.2.3 Record use cases.

      1.2.4 Identify opportunities to provide value.

      1.3 Define the vision.

      1.3.1 Prioritize benefits.

      1.3.2 Craft a vision and mission statement.

      1.3.3 Identify goals.

      1.3.4 Define guiding principles for your strategy.

      2.1 Define the standard offerings.

      2.1.1 Select a provisioning model for each persona.

      2.1.2 Define the standard device offerings.

      2.1.3 Document each personas’ entitlements.

      2.2 Outline supporting practices.

      2.2.1 Define device management tools and approach.

      2.2.2 Identify groups involved in supporting practices.

      2.2.4 Identify opportunities to improve customer service.

      2.3 Define policies. 2.3.1 Define acceptable use. 2.3.2 Define BYOD policies. 2.3.3 Define procurement and entitlement policies. 2.3.4 Define security policies.

      3.1 Develop initiatives.

      3.1.1 Identify the gaps in devices, user support, use cases, policy & governance, and fitness for use.

      3.1.2 Plan the deployment and user migration journey.

      3.1.3 Document initiatives in the roadmap .

      5.1 Complete in-progress deliverables from previous four days.

      5.2 Set up time to review workshop deliverables and discuss next steps

      Deliverables
      1. SWOT analysis of current state
      2. Goals cascade
      3. Persona analysis
      1. Vision statement, mission statement, and guiding principles
      2. Goals and indicators
      3. End-user device entitlements standard
      1. List of management tools for end-user computing
      2. Roles and responsibilities for maintaining the end-user computing environment
      3. Opportunities to improve customer service
      4. End-user computing policy templates
      1. Initiatives mapped to practice areas
      2. User’s migration journey map
      1. End-user computing strategy template
      2. End-user computing roadmap

      Phase 1

      Set the Direction

      Set the Direction

      1.1 Identify Desired Benefits

      1.2 Perform a User Group Analysis

      1.3 Define the Vision

      Define the Offering

      2.1 Define the Standard Offerings

      2.2 Outline Supporting Services

      2.3 Define Governance and Policies

      Build the Roadmap

      3.1 Develop Initiatives

      This phase will walk you through the following activities:

      • Current-state analysis
      • Goals cascade
      • Persona analysis

      This phase involves the following participants:

      • End-User Computing Team
      • IT Leadership

      Set a direction that will create value for IT, stakeholders, and end users

      Use your insights to build your strategy

      Start by downloading Info-Tech’s End-User Computing Strategy Template

      1. Perform a stop-start-continue exercise for how IT supports end-user devices.
      2. Perform a goals cascade to identify how the end-user computing strategy can align with and support senior leaders’ priorities and strategic objectives.
      3. Perform a user group analysis to identify what IT can do to provide additional value to end users.
      4. Use the results to define a vision for your end-user computing strategy and in-scope benefits.

      Download the End-User Computing Strategy Template.

      Step 1.1

      Identify Desired Benefits

      Activities

      1.1.1 Assess the current state of end-user computing

      1.1.2 Perform a SWOT analysis

      1.1.3 Map benefits to stakeholder drivers and priorities

      Optional: Identify current total cost of ownership

      This step requires the following inputs:

      • Current approach for end-user computing
      • List of strengths and weaknesses of the current approach

      This step involves the following participants:

      • CIO
      • End-User Computing Team
      • IT Leadership
      • End-User Computing Manager

      Outcomes of this step

      • Defined success metrics that are tied to business value
      • Vision statement, mission statement, and guiding principles

      Review your current state for each end-user computing practice

      1. Devices
        • Corporate-issued devices
        • Standard offerings
      2. User Support
        • Self-service
        • Tier 1 support
      3. Use Cases
        • Providing value
        • Business apps
      4. Policy & Governance
        • Personal device use
        • IT policy
      5. Fitness for Use
        • Securing devices
        • Patching

      1.1.1 Assess the current state of end-user computing

      Discuss IT’s strengths and challenges

      Review your success in responding to the trends highlighted in the executive brief.

      • Start by reviewing the trends in the executive brief. Identify which trends you would like to focus on.
      • Review the domains below. Discuss:
        • Your current approach
        • Strengths about this approach
        • Challenges faced with this approach
      • Document the results in the “Current-State Assessment” section of your End-User Computing Strategy.
      1. Devices
        • Corporate-issued devices
        • Standard offerings
      2. User Support
        • Self-service
        • Tier 1 support
      3. Use Cases
        • Providing value
        • Business apps
      4. Policy & Governance
        • Personal device use
        • IT policy
      5. Fitness for Use
        • Securing devices
        • Patching

      Download the End-User Computing Strategy Template.

      Consider these aspects of end-user computing in your assessment

      Devices: As shown in the executive brief, devices are necessary for satisfaction in IT. In your current-state assessment, outline the principal means by which users are provided with a desktop and computing.

      • Corporate-issued devices: Document the types of devices (e.g. laptops, desktops, smartphones) and operating systems that IT currently supports.
        • Strengths: Highlight user satisfaction with your current offerings by referencing recent relationship surveys.
        • Challenges: Document corporate-issued devices where stakeholders and users are not satisfied, platforms that stakeholders would like IT to support, etc.
      • Standard offerings: Name the high-level categories of devices that you offer to end users (e.g. standard device, power device).
        • Strengths: Outline steps that IT has taken to improve the portfolio of standard offerings and to communicate the offerings.
        • Challenges: Identify areas to improve the standard offerings.

      User support: Examine how the end-user computing team enables a high-quality customer service experience. Especially consider self-service and tier 1 support.

      • Self-service: Describe the current state of your self-service capabilities (e.g. name of the self-service portal, number of apps in the app store).
        • Strengths: Outline successes with your self-service capabilities (e.g. use of self-service tools, recently deployed tools, newly supported platforms).
        • Challenges: Identify gaps in self-service capabilities.
      • Tier 1 support: Document the number of end-user computing incidents and service requests that are resolved at tier 1 as well as the number of incidents and service requests that are resolvable without escalation.
        • Strengths: Identify technologies that make first contact resolution possible. Outline other items that support tier 1 resolution of end-user computing tickets, such as knowledgebase articles and training programs.
        • Challenges: Document areas in which tier 1 resolution of end-user computing tickets is not feasible.

      Considerations (cont’d.)

      Use cases: Reflect on how IT and end-user computing supports users’ most important use cases. Consider these aspects:

      • Providing value: Identify the number of user groups for which you have completed a user group analysis. Outline your major approaches for capturing feedback, such as relationship surveys.
        • Strengths: Document any successful initiatives around stakeholder relationships and requirements gathering. You can also highlight successful metrics, such as high satisfaction scores from a team, department, or division.
        • Challenges: Identify where there are dissatisfied stakeholders and gaps in product offerings and where additional work around value generation is required.
      • Business apps: Outline your major business apps and your approach to improvement for these apps. If you need assistance gathering feedback from end users and stakeholders, you can use Info-Tech’s Application Portfolio Assessment.
        • Strengths: Show the EUC team’s successes in supporting critical business apps (e.g. facilitating user acceptance testing, deploying via endpoint management tool).
        • Challenges: Name business apps that are not meeting stakeholder needs. Consider if end users are dissatisfied with an app, if IT is unable to adequately monitor and support a business app, etc.

      Policy and governance: Document the current state of policies governing the use of end-user computing devices, both corporate-issued and personally owned. Review Step 2.3 for a list of policy questions to address and for links to policy templates.

      • Personal device use: Explain which users are allowed to use personally owned devices, what use cases are supported, and which types of devices are supported. Also, highlight explicit prohibitions.
        • Strengths: Highlight major accomplishments with BYOD, utilization metrics, etc. Consider including any platforms or apps that support BYOD (e.g. Microsoft Office 365).
        • Challenges: Identify where there are gaps in your support for personal devices. Examples can include insufficient management tools, lack of feedback from end users on BYOD support, undefined policies and governance, and inadequate support for personal devices.

      Considerations (cont’d.)

      IT policies: List your current policy documents. Include policies that relate to end-user computing, such as security policy documents; acceptable use policy documents; purchasing policies; documents governing entitlements to computers, tablets, smartphones, and prestigious devices; and employee monitoring policy documents.

      • Strengths: Outline the effectiveness of these policies, user compliance to these policies, and your success in enforcing these policies.
      • Challenges: Identify where you have gaps in user compliance, gaps in enforcing policies, many exceptions to a policy, etc.

      Fitness for use: Reflect on your ability to secure users, enterprise data, and computers. Document your current capabilities to ensure devices are adequately secured and risks adequately mitigated.

      • Securing devices: Describe your current approach to implementing security baselines, protecting data, and ensuring compliance.
        • Strengths: Highlight your accomplishments with ensuring devices meet your security standards and are adequately managed.
        • Challenges: Identify areas that are not adequately protected, where IT does not have enough visibility, and devices on which IT cannot enforce security standards.
      • Patching: Describe your current approach to distributing OS patches, distributing app patches, and ensuring patch compliance.
        • Strengths: Outline steps that IT has taken to improve release and deployment practices (e.g. user acceptance testing, deployment rings).
        • Challenges: When is IT unable to push a patch to a device? Outline when devices cannot receive a patch, when IT is unable to ensure patches are installed, and when patches are disruptive to end users.

      1.1.2 Perform a SWOT analysis

      Summarize your current-state analysis

      To build a good strategy, you need to clearly understand the challenges you face and opportunities you can leverage.

      • Summarize IT’s strengths. These are positive aspects internal to IT.
      • Summarize IT’s challenge. What internal IT weakness should the strategy address?
      • Identify high-level opportunities. Summarize positive factors that are external to IT (e.g. within the larger organization, strong vendor relationships).
      • Document threats. What external factors present a risk to the strategy?

      Record your SWOT analysis in the “Current-State Assessment” section of your End-User Computing Strategy Template.

      Download the End-User Computing Strategy Template.

      1.1.3 Map benefits to stakeholder drivers and priorities

      Use a goals cascade to identify benefits that will resonate with the business

      Identify how end-user computing will support larger organizational strategies, drivers, and priorities

      1. Identify stakeholders. Focus on senior leaders – user groups will be addressed in Step 1.2.
      2. For each stakeholder, identify three to five drivers or strategic priorities. Use the drivers as a starting point to:
        1. Increase productivity
        2. Mitigate risks
        3. Optimize costs
      3. Map the benefits you brainstormed in Step 1.1 to the drivers. It’s okay to have benefits map to multiple drivers.
      4. Re-evaluate benefits that don’t map to any drivers. Consider removing them.
      Stakeholder Drivers and Strategic Priorities End-User Computing Benefits
      CEO Ensure service continuity with remote work
      • Customers can still be served by remote workers
      Respond to COVID-19 changes with agility
      • Workers can transition seamlessly between working remotely and working in the office
      Reduce unnecessary costs
      • Standardize computer models to reduce spend on devices
      COO Business continuity: being able to work from home
      • Workers can transition seamlessly between working remotely and working in the office

      Record this table on the “Goals Cascade” slide in the “Vision and Desired Benefits” section of your End-User Computing Strategy Template.

      Use the CEO-CIO Alignment Program to identify which business benefits are most important.

      Sample end-user computing benefits

      Business Goals End-User Computing Benefits
      Manage risk Controls are effectively enforced on remote devices Sensitive data is secured Devices and data are accounted for
      Ensure service continuity Business processes can still function with remote personnel Customers can still be served by remote workers Personnel can be productive from anywhere IT practices can still operate remotely
      Comply with external regulation Improved ability to demonstrate compliance
      Respond to change with agility Personnel can be productive from anywhere More business processes can be performed remotely
      Improve operational efficiency More efficient sales practices More efficient customer service practices Increased number of digitized business processes Increased use of IT and HR self-service tools
      Offer competitive products and services Increased customer satisfaction with online services Number of piloted new products
      Manage people Increased employee productivity Increased employee engagement Increased talent attraction Increased workforce retention
      Make data-driven decisions Increased workforce retention Improved understanding of customers Access to accurate data on services and spending Improved IT cost forecasting
      Improve customer experience Increased customer satisfaction with online services Ability to scale up capacity to meet increased demand Customers can still be served by remote workers Improved customer self-service options
      Maximize stakeholder value Transition to OpEx spend and reduce CapEx investments Access to accurate data on services and spending Improved IT cost forecasting

      Optional: Identify current total cost of ownership

      Be mindful of hidden costs, such as those associated with supporting multiple devices and maintaining a small fleet of corporate devices to ensure business continuity with BYOD.

      • Use the Hardware Asset Management Budgeting Tool to forecast spend on devices (and infrastructure) based on project needs and devices nearing end of life.
      • Use the Mobile Strategy TCO Calculator to estimate the total cost of all the different aspects of your mobile strategy, including:
        • Training
        • Management platforms
        • Custom app development
        • Travel and roaming
        • Stipends and taxes
        • Support
      • Revisit these calculators in Phase 2. Use the TCO calculator when considering different approaches to mobility and end-user computing.

      Insert the results into your End-User Computing Strategy Template.

      Download the HAM Budgeting Tool.

      Download the Mobile Strategy TCO Calculator.

      Step 1.2

      Perform a User Group Analysis

      Activities

      1.2.1 Organize roles based on how they work

      1.2.2 Organize users into groups

      1.2.3 Document the current offerings

      1.2.4 Brainstorm pain points and desired gains for each user group

      This step requires the following inputs:

      • List of roles and technologies
      • User feedback
      • List of personas

      This step involves the following participants:

      • End-User Computing Team
      • IT Leadership
      • End-User Computing Manager

      Outcomes of this step

      • List of user groups and use cases for each group
      • List of current offerings for each user group
      • Value analysis for each user group

      Gather the information you need

      Use the Application Portfolio Assessment to run a relationship survey.

      Dive deeper with the blueprint Improve Requirements Gathering.

      List of Roles and Technology

      Organization chart: Consult with HR or department leaders to provide a list of the different roles that exist in each department.

      Identity access management tools: You can consult tools like Active Directory, but only if the data is clean.

      Apps and devices used: Run a report from your endpoint management tool to see what devices and apps are used by one another. Supplement this report with a report from a network management tool to identify software as a service that are in use and/or consult with department leaders.

      User Feedback

      Relationship surveys: Tools like the End-User Application Satisfaction Diagnostic allow you to assess overall satisfaction with IT.

      Focus groups and interviews: Gather unstructured feedback from users about their apps and devices.

      User shadowing: Observe people as they use technology to identify improvement opportunities (e.g. shadow meetings, review video call recordings).

      Ticket data: Identify apps or systems that users submit the most incidents about as well as high-volume requests that could be automated.

      1.2.1 Organize roles based on how they work

      Start by organizing roles into categories based on where they work and how they interact with information.

      1. Define categories of where people work. Examples include:
        1. In office, at home, at client sites
        2. Stationary, sometimes mobile, always mobile
        3. Always in same location, sometimes in different locations, always in different locations within a site, mobile between sites
      2. Define categories of how people interact with information. Examples include:
        1. Reads information, reads and writes information, creates information
        2. Cases, projects, relationships
      3. Build a matrix. Use the location categories on one axis and the interaction categories on the other axis.
      4. Place unique job roles on the matrix. Review each functional group’s organizational chart. It is okay if you don’t fill every spot. See the diagram on this page for an example.
      Always Works in the Same Location Sometimes Works in Different Locations Always Works in Different Locations
      Predominantly Reads Information
      • Janitor
      • Receptionist
      • Receiving
      • Accounts Payable Clerk
      Reads and Writes Information
      • Sales Rep
      • Sales Manager
      • Director of Sales
      • Developer
      • Scrum Master
      • Customer Service Agent
      • CS Manager
      • Call Center Director
      • Accountant
      • Controller
      • HR Specialist
      • Business Analyst
      • VP, Sales
      • Product Manager
      • Project Manager
      • Director of Engineering
      • VP, HR
      • CFO
      • Director of PMO
      • Field Sales Rep
      • CEO
      • CIO
      • COO
      Predominantly Creates Information
      • External Consultants
      • Design
      • Marketing
      • Copywriting

      1.2.2 Organize users into groups

      Populate a user group worksheet for each in-scope group.

      1. Within each quadrant, group similar roles together into “User Groups.” Consider similarities such as:
        1. Applications they use
        2. Data and files with which they interact
        3. Business capabilities they support
      2. Document their high-level profile:
        1. Where they work
        2. Sensitivity of data they access
        3. Current device and app entitlements
      3. Document the resulting user groups. Record each user group on a separate worksheet in the User Group Analysis Workbook.

      Download the User Group Analysis Workbook.

      1.2.3 Document the current offerings

      For each user group, document:

      • Primary and secondary computing devices: Their most frequently used computing devices.
      • Acceptable use: Whether corporate-issued devices are personally enabled.
      • BYOD: Whether this persona is authorized to use their personal devices.
      • Standard equipment provided: Equipment that is offered to everyone in this persona.
      • Additional devices and equipment offered: Equipment that is offered to a subset of this user group. These items can include more prestigious computers, additional monitors, and office equipment for users allowed to work remotely. This category can include items that require approval from budget owners.
      • Top apps: What apps are most commonly used by this user group? What common nonstandard apps are used by this user group?

      Standardize the nonstandard

      When users such as VIP users want more than the standard offering, have a more prestigious option available. This approach will help you to proactively anticipate your users’ needs.

      1.2.4 Brainstorm pain points and desired gains for each user group

      Don’t focus only on their experiences with technology

      Reference the common personas listed on the next page to help you brainstorm additional pain points and desired gains.

      1. Brainstorm pain points. Answer these questions for each role:
        1. What do people find tedious about their day-to-day jobs?
        2. What takes the most effort for them to do?
        3. What about their current toolset makes this user frustrated?
        4. What makes working difficult? Consider their experiences working from a home office, attending meetings virtually or in person, and working in the office.
        5. What challenges does that role have with each process?
      2. Brainstorm desired gains from their technology. Answer these questions for each role:
        1. For your end-user computing vision to become a reality for this persona, what outcomes or benefits are required?
        2. What benefits will this persona expect an end-user computing strategy to have?
        3. What improvements does this role desire?
        4. What unexpected benefits or outcomes would surprise this role?
        5. What would make this role’s day-to-day easier?
        6. What location-specific benefits are there (e.g. outcomes specific to working in the office or at home)?

      Record each user group’s pain points and desired gains on their respective worksheet.

      For additional questions you can ask, visit this Strategyzer blog post by Alexander Osterwalder.

      Info-Tech Insight

      Identify out-of-scope benefits?

      If that desired gain is required for the vision to be achieved for a specific role, you have two options:

      • Bring the benefit in scope. Ensure your metrics are updated.
      • Bring this user group out of scope. End-user computing improvements will not be valuable to this role without that benefit.

      Forcing a user group to use an unsatisfactory tool will severely undermine your chance of success, especially in the project’s early stages.

      Consider these common personas when brainstorming challenges and desired gains

      What unique challenges will these personas face within each of your user groups? What improvements would each of these personas expect out of an end-user computing strategy?

      Early Adopters

      • Like trying new ways of working and using the latest technology.
      • Very comfortable solving their own issues.
      • Enjoy exploring and creating new ways of handling challenges.

      Late Adopters

      • Prefer consistent ways of working, be it tech or business processes.
      • React to tech issues with anxiety and need assistance to get issues fixed.

      VIP

      • Has a prestigious job and would like to use technology that communicates their status.
      • Does not like to resolve their own issues.

      Road Warriors

      • Always on the go, running between work meetings and appointments.
      • Value flexibility and want devices, apps, and tech support that can be used anywhere at any time.

      Hoarders

      • Want to keep all their devices, data, and apps.
      • Will stall when they need to migrate devices or uninstall apps and become unresponsive any time there is a risk of losing something.

      Step 1.3

      Define the Vision

      Activities

      1.3.1 Prioritize which benefits you want to achieve

      1.3.2 Identify how you will track performance

      1.3.3 Craft a vision statement that demonstrates what you’re trying to create

      1.3.4 Craft a mission statement for your end-user computing team

      1.3.5 Define guiding principles

      This step requires the following inputs:

      • Goals cascade
      • List of benefits
      • List of critical success factors (CSFs)

      This step involves the following participants:

      • End-User Computing Manager
      • CIO
      • Help Desk Manager
      • Infrastructure Manager

      Outcomes of this step

      • End-User computing KPIs and metrics
      • Vision statement
      • Mission statement

      1.3.1 Prioritize which benefits you want to achieve

      Use the MoSCoW sorting technique

      Select benefits that appear multiple times in the goals cascade from Activity 1.1.3 as well as your challenges from your current-state assessment.

      1. Record which benefits are “Must Haves.” Select benefits that are most important to your highest-priority stakeholders.
      2. Record which benefits are “Should Haves.” These benefits are important but not critical.
      3. Record which benefits are “Could Haves.” These are low-priority benefits.
      4. Record the remaining benefits under “Won’t Have.” These benefits are out-of-scope but can be revisited in the future.

      Record the output in your End-User Computing Strategy Template under “Benefit Prioritization” in the “Vision and Desired Benefits” section.

      Sample output:

      Must Have Should Have Could Have Won't Have
      • Customers can still be served by remote workers.
      • Easier to work in multiple locations.
      • More options for provisioning computers to new workers.
      • Improved patching and security compliance checking of remote devices.
      • Self-service app installs on Windows.
      • More consistent experience across all devices and platforms, including BYOD.
      • Improved visibility into and manageability of BYOD.
      • Ability for users to create their own low-code apps (e.g. in Microsoft Power Apps).
      • Improved guidelines for running hybrid/remote meetings.
      • BYOD support for workers handling sensitive data.
      • Support for any type of Android smartphone or tablet.

      1.3.2 Identify how you will track performance

      1. List each unique high-priority benefit from Activity 1.3.1 as a critical success factor (CSF).
      2. For each CSF, identify key performance indicators (KPIs) that you can use to track how well you’re progressing on the CSF.
        1. Articulate that KPI as a SMART goal (specific, measurable, achievable, realistic, and timebound).
      3. For each KPI, identify the metrics you will use to calculate it.
      4. Identify how and when you will:
        1. Capture the current state of these metrics.
        2. Update changes to the metrics.
        3. Re-evaluate the CSFs.
        4. Communicate the progress to the project team and to stakeholders.

      Record this information in your End-User Computing Strategy Template.

      Sample output:

      Critical Success Factor Key Performance Indicator Metrics
      Improve remote worker productivity Increase employee engagement by 10% in two years
      • McLean Employee Engagement Score
      • Gallup Q Score
      Integrate relevant information sources into one spot for sales Integrate three information sources that will be useful to sales in one year
      • # of sales-specific apps integrated into a dashboard, portal, or workspace
      • Sales satisfaction scores
      Reduce real-estate costs Reduce office space by 50% in two cities over three years
      • $ spent on office leases
      Securely deliver all apps, information, and data to any device, anywhere, at any time Build the apps and information sources into a digital workspace for three business processes over one year
      • # of business processes supported in the workspace

      1.3.3 Craft a vision statement that demonstrates what you’re trying to create

      The vision statement communicates a desired future state of the IT organization. The statement is expressed in the present tense. It seeks to articulate the desired role of IT and how IT will be perceived.

      Strong IT vision statements have the following characteristics:

      • Describes a desired future
      • Focuses on ends, not means
      • Communicates promise
      • Is:
        • Concise; no unnecessary words
        • Compelling
        • Achievable
        • Inspirational
        • Memorable

      Sample IT Vision Statements:

      • To support an exceptional employee experience by providing best-in-class end-user devices.
      • Securely enable access to corporate apps and data from anywhere, at any time, on any device.
      • Enable business and digital transformation through secure and powerful virtualization technology.
      • IT is a cohesive, proactive, and disciplined team that delivers innovative technology solutions while demonstrating a strong customer-oriented mindset.

      1.3.4 Craft a mission statement for your end-user computing team

      The IT mission statement specifies the function’s purpose or reason for being. The mission should guide each day’s activities and decisions. The mission statement should use simple and concise terminology and speak loudly and clearly, generating enthusiasm for the organization.

      Strong IT mission statements have the following characteristics:

      • Articulate the IT function’s purpose and reason for existence
      • Describe what the IT function does to achieve its vision
      • Define the customers of the IT function
      • Can be described as:
        • Compelling
        • Easy to grasp
        • Sharply focused
        • Inspirational
        • Memorable
        • Concise

      Sample IT Mission Statements:

      • To provide infrastructure, support, and innovation in the delivery of secure, enterprise-grade information technology products and services that enable and empower the workforce at [Company Name].
      • To help fulfill organizational goals, the IT department is committed to empowering business stakeholders with technology and services that facilitate effective processes, collaboration, and communication.
      • The mission of the information technology (IT) department is to build a solid, comprehensive technology infrastructure; to maintain an efficient, effective operations environment; and to deliver high-quality, timely services that support the business goals and objectives of [Company Name].
      • The IT group is customer-centered and driven by its commitment to management and staff. It oversees services in computing, telecommunications, networking, administrative computing, and technology training.

      1.3.5 Define guiding principles

      Select principles that align with your stakeholders’ goals and objectives

      Use these examples as a starting point:

      IT Principle Name IT Principle Statement
      1. Enterprise value focus We aim to provide maximum long-term benefits to the enterprise as a whole while optimizing total costs of ownership and risks.
      2. Fit for purpose We maintain capability levels and create solutions that are fit for purpose without over-engineering them.
      3. Simplicity We choose the simplest solutions and aim to reduce operational complexity of the enterprise.
      4. Reuse > buy > build We maximize reuse of existing assets. If we can’t reuse, we procure externally. As a last resort, we build custom solutions.
      5. Managed data We handle data creation, modification, and use enterprise-wide in compliance with our data governance policy.
      6. Controlled technical diversity We control the variety of technology platforms we use.
      7. Managed security We manage, support, and assist in the implementation of security enterprise-wide in collaboration with our security governance team.
      8. Compliance to laws and regulations We operate in compliance with all applicable laws and regulations.
      9. Innovation We seek innovative ways to use technology for business advantage.
      10. Customer centricity We deliver best experiences to our end users by aligning to customer service best practices.

      Phase 2

      Define the Offering

      Set the Direction

      1.1 Identify Desired Benefits

      1.2 Perform a User Group Analysis

      1.3 Define the Vision

      Define the Offering

      2.1 Define the Standard Offerings

      2.2 Outline Supporting Services

      2.3 Define Governance and Policies

      Build the Roadmap

      3.1 Develop Initiatives

      This phase will walk you through the following activities:

      • Defining standard device entitlements and provisioning models for end-user devices and equipment
      • Shifting end-user computing support left
      • Identifying policy gaps

      This phase involves the following participants:

      • End-User Computing Team
      • IT Leadership

      Step 2.1

      Define the Standard Offerings

      Activities

      2.1.1 Identify the provisioning models for each user group

      2.1.2 Define the standard device offerings

      2.1.3 Document each user group’s entitlements

      This step requires the following inputs:

      • Standard End-User Entitlements and Offerings Template
      • List of persona groups
      • Primary computing devices
      • Secondary computing devices
      • Supporting operating systems
      • Applications and office equipment

      This step involves the following participants:

      • End-User Computing Manager
      • CIO
      • Help Desk Manager
      • Infrastructure Manager

      Outcomes of this step

      • End-user device entitlements and offerings standard

      This step will walk you through defining standard offerings

      You will define the base offering for all users in each user group as well as additional items that users can request (but that require additional approvals).

      1. Primary Computing Device
        • The main device used by a worker to complete their job (e.g. laptop for knowledge workers, kiosk or shared tablet for frontline workers).
      2. Secondary Computing Devices
        • Additional devices that supports a worker (e.g. a smartphone, tablet, personal computer).
      3. Provisioning Models
        • Whether the equipment is corporate-issued versus personally owned and whether personal use of corporate resources is allowed.
      4. Apps
        • The software used by the worker. Apps can be locally installed, cloud-based (e.g. SaaS), and/or virtualized and running remotely.
      5. Peripherals
        • Additional equipment provisioned to the end user (e.g. monitors, docking station, mice, keyboards).

      There is always a challenge of determining who gets what and when

      The goal is balancing cost, risk, and employee engagement

      The right balance will be different for every organization

      • IT can’t always say no to new ideas from the business. For example, if the organization wants to adopt Macs, rather than resisting IT should focus on identifying how Macs can be safely implemented.
      • Smartphones may not be necessary for a job, but they can be a valid employee perk. Not every employee may be entitled to the perk. There may be resentment between employees of the same level if one of the employees has a corporate-issued, business-only phone for their job function.
      • The same laptop model may not work for everyone. Some employees may need more powerful computers. Some employees may want more prestigious devices. Other employees may require a suite of apps that is only available on non-Windows operating systems.

      Action Item: Provide a defined set of standard options to the business to proactively address different needs.

      A good end-user computing strategy will effectively balance:

      • User Choice
      • Risk
      • Cost

      Your standard offerings need to strike the right balance for your organization.

      Review the End-User Computing Ideas Catalog

      Compare pros and cons of computing devices and operating systems for better decision making

      The catalog provides information about choices in:

      • Provisioning models
      • Operating systems
      • Device form factors

      Review the catalog to learn about items that can help your organization to achieve the desired vision from Phase 1.

      As you review the catalog, think about these questions:

      • What primary and secondary devices can you provide?
      • What operating systems do these devices support?
      • What are the provisioning models you will use, considering each model’s weaknesses and strengths?
      • How can you more effectively balance user choice, risk, and cost?

      Download the End-User Computing Ideas Catalog.

      2.1.1 Identify the provisioning models for each user group

      1. Review the definitions in the End-User Computing Ideas Catalog.
      2. Build a table. List the major user groups along the top of the table and applications down the rows.
      3. Brainstorm provisioning models that will be used for primary and secondary devices for each persona group.
      4. Record your provisioning models in the Standard End-User Entitlements and Offerings Template.

      Download the End-User Computing Ideas Catalog.

      Download the Standard End-User Entitlements and Offerings Template.

      Persona Primary Computing Device Secondary Laptops or Computers Smartphone Tablet
      Sales COPE BYOD BYOD BYOD
      Field Sales CYOD BYOD COBO COBO
      Customer Service COBO None None None
      Knowledge Worker COPE BYOD BYOD BYOD
      App Dev CYOPED None CYOD CYOD
      VIP CYOPED CYOPED CYOPE BYOD

      Identify multiple device options

      Offer standard, power, and prestigious offerings

      Prioritize offering models and align them with your user groups.

      • Standard device: This offering will work for most end users.
      • Power device: This offering will provide additional RAM, processor speed, storage, etc., for users that require it. It is usually offered as an additional option that requires approval.
      • Prestigious device: This offering will be provided to VIP users.
      • Portable device: This offering is for employees within a user group that moves around more often than others. This type of offering is optional – consider having a separate user group for these users that get a more portable laptop as their standard device.

      Standardize the nonstandard

      When users such as VIP users want more than the standard offering, have a more prestigious option ready to offer. This approach will help you to proactively anticipate your users’ needs.

      Who approves?

      Generally, if it is a supported device, then the budget owner determines whether to allow the user to receive a more powerful or more prestigious device.

      This decision can be based on factors such as:

      • Business need – does the user need the device to do their job?
      • Perk or benefit – is the device being offered to the end user as a means of increasing their engagement?

      If IT gets this answer wrong, then it can result in shadow IT

      Document your answer in the Device Entitlement Policy Template.

      2.1.2 Define the standard device offerings

      Consider all devices and their supporting operating systems.

      1. On a flip chart or whiteboard, build a matrix of the supported form factors and operating systems.
      2. For each cell, document the supported vendor and device model.
      3. Identify where you will provide additional options.
      Windows Mac OS iOS Android
      Laptops Lenovo T15 Gen 2 MacBook Pro 14” N/A N/A
      Power Laptops Lenovo ThinkPad X1 Carbon MacBook Pro 16” N/A N/A
      Prestigious Laptops Lenovo ThinkPad X1 Yoga Gen 6 MacBook Pro 16” N/A N/A
      Tablets Microsoft Surface N/A iPad Pro Samsung Galaxy Tab
      Smartphones N/A N/A iPhone 13 Samsung Galaxy S21

      2.1.3 Document each user groups’ entitlements

      Not every persona needs to be entitled to every supported option

      Use the Standard End-User Entitlements and Offerings Template as a starting point.

      • Create a separate section in the document for each persona. Start by documenting the provisioning models for each type of device.
      • Record the standard offering provided to members of each persona as well as additional items that can be provided with approval. Record this information for:
        • Primary computing devices
        • Secondary computing devices
      • Optional: Document additional items that will be provided to members of each persona as well as additional items they can request, such as:
        • Apps
        • Office equipment

      Download the Standard End-User Entitlements and Offerings Template.

      Step 2.2

      Outline Supporting Services

      Activities

      2.2.1 Review device management tools and capabilities

      2.2.2 Identify common incidents and requests for devices

      2.2.3 Record how you want to shift resolution

      2.2.4 Define which IT groups are involved in supporting practices

      Define the Offering

      This step requires the following inputs:

      • Standard End-User Entitlements and Offerings Template
      • List of supporting devices
      • Common incidents and requests
      • List of supporting practices

      This step involves the following participants:

      • End-User Computing Manager
      • CIO
      • Help Desk Manager
      • Infrastructure Manager

      Outcomes of this step

      • List of IT groups who are involved in supporting devices
      • Responsibilities of each group for requests and incidents

      2.2.1 Review device management tools and capabilities

      Document the tools that you use to manage each OS and identify gaps

      If there are different approaches to managing the same OS (e.g. Windows devices that are co-managed versus Windows devices that are only managed by Intune), then list those approaches on separate rows.

      Provision Protect from loss/theft Deploy/update apps Backup & protect Protect from injections Complies with policies Track Decommission
      Windows 10 & 11 (co-managed) Autopilot Gap ConfigMgr Gap Windows Security ConfigMgr ConfigMgr Intune Intune and Autopilot
      Windows 10 & 11 (Intune) Autopilot Intune (remote wipe) Intune OneDrive for Business Windows Security Microsoft Advanced Threat Protection Intune Intune and Autopilot
      Mac OS Jamf Pro Intune (remote wipe) Jamf Pro OneDrive for Business Gap Jamf Pro Intune Jamf Pro

      Document the results on the “IT Management Tools” slide in the “IT Support” section of your End-User Computing Strategy Template.

      2.2.2 Identify common incidents and requests for devices

      Analyze your service desk ticket data. Look for the following information:

      • The most common incidents and service requests around end-user devices and business apps
      • Incident categories and service requests that almost always involve escalations

      Record the level at which these tickets can be resolved today. Ensure you include these groups:

      • Tier 0 (i.e. end-user self-service)
      • Tier 1 (i.e. user’s first point of contact at the service desk)
      • Desk-side support and field-support groups
      • End-user computing specialist teams (e.g. desktop engineering, mobile device management teams)
      • Other specialist teams (e.g. security, enterprise applications, DevOps)

      Record the desired state. For each incident and request, to where do you want to shift resolution?

      Record this chart on the “Current State of IT Support” slide in the “IT Support” section of your End-User Computing Strategy Template.

      Most Common Incidents & Requests Self-Service Service Desk Tier 1 Desk-Side or Field Support End-User Computing
      Connect/fix a printer X
      Web conferencing issue X
      Bluetooth issues X
      Outlook issues X
      Install standard app X
      Install app requiring approval X
      Install nonstandard app X
      Enroll personal iOS/Android device X
      Enroll personal Mac/Windows computer X
      Perform a factory reset on a lost or stolen device X
      Unenroll device X

      2.2.3 Record how you want to shift resolution

      Identify opportunities to improve self-service and first contact resolution.

      Starting with the chart you created in Activity 2.2.2, record the desired state. For each incident and request, to where do you want to shift resolution?

      • Identify quick wins. Where will it take low effort to shift resolution? Denote these items with a “QW” for quick win.
      • Identify high-value, high-effort shifts. Where do you want to prioritize shifting resolution? Base this decision on the desired benefits, guiding principles, and vision statement built in Phase 1. Denote these items with an “H” for high.
      • Identify low-value areas. Where would shifting provide low value to end users and/or would have low alignment to the benefits identified in Phase 1? Denote these items with an “L” for low.
      • Identify where no shift can occur. Some items cannot be shifted to self-service or to tier 1 due to governance considerations, security factors, or technical complexity. Denote these items with an “OoS” for out of scope.

      Use the “Opportunities to Provide Self-Service and Articles” and “Desired State” slides in the “IT Support” section of your End-User Computing Strategy Template to document quick wins and high-value, high-effort shifts.

      Most Common Incidents & Requests Self-Service Service Desk Tier 1 Desk-Side or Field Support End-User Computing
      Connect/fix a printer H QW X
      Web conferencing issue H X
      Bluetooth issues L X
      Outlook issues H H X
      Install standard app X
      Install app requiring approval H X
      Install nonstandard app OoS X
      Enroll personal iOS/Android device QW QW X
      Enroll personal Mac/Windows computer QW QW X
      Perform a factory reset on a lost or stolen device QW QW X
      Unenroll device QW QW X

      2.2.4 Define which IT groups are involved in supporting practices

      Repeat activities 2.2.2 and 2.2.3 with the following list of tasks

      IT Asset Management

      • Purchasing devices
      • Purchasing software licenses
      • Imaging devices
      • Deploying devices
      • Deploying software
      • Recovering devices
      • Recovering software

      Release Management

      • Testing patches
      • Testing app updates
      • Testing OS updates
      • User acceptance testing

      Managing Service Catalogs

      • Defining standard device offerings
      • Defining standard software offerings
      • Defining device and software entitlements
      • Updating published catalog entries

      Knowledge Management

      • Writing internal KB articles
      • Writing user-facing articles
      • Training specialists
      • Training service desk agents
      • Training users

      Portfolio Management

      • Prioritizing app upgrades or migrations
      • Prioritizing OS migrations
      • Prioritizing end-user computing projects

      Step 2.3

      Define Governance and Policies

      Activities

      2.3.1 Answer these organizational policy questions

      2.3.2 Answer these security policy questions

      Define the Offering

      This step requires the following inputs:

      • List of supporting devices
      • List of persona groups
      • List of use cases

      This step involves the following participants:

      • End-User Computing Manager
      • CIO
      • Help Desk Manager
      • Infrastructure Manager

      Outcomes of this step

      • End-user computing organizational and security policies

      Focus on organizational policies and enforcement

      Policies set expectations and limits for mobile employees

      Enforcement refers to settings on the devices, management and security tools, and process steps.

      • Policies define what should and should not be done with user-facing technology. These policies define expectations about user and IT behavior.
      • Enforcement ensures that policies are followed. User policies must often be enforced through human intervention, while technology policies are often enforced directly through infrastructure before any people get involved.

      Use the “Policies” section in the End-User Computing Strategy Template to document the answers in this section. Activities 2.3.2 and 2.3.3 present links to policy templates. Use these templates to help address any gaps in your current policy suite.

      2.3.1 Answer these organizational policy questions

      Identify if there are different expectations for certain user groups, where exceptions are allowed, and how these policies will be enforced.

      Entitlements

      • Who is entitled to receive and use prestigious computers?
      • Who is entitled to receive and use a smartphone?
      • What users are entitled to a stipend for personal device use?

      Personal Device Use

      • What use cases are supported and are not supported on personal devices?
      • What level of visibility and control does IT need over personal devices?

      Acceptable Use

      • Are people allowed to use corporate resources for personal use?
      • What are the guidelines around personal use?
      • Are users allowed to install personal apps on their corporate-issued computers and/or mobile devices?

      Purchasing and Reimbursement

      • Who is allowed to purchase devices? Apps?
      • When can users file a reimbursement request?

      Employee Monitoring

      • What user information is monitored?
      • When can that information be used and when can it not be used?

      Use the “Policies” section of the End-User Computing Strategy Template to document these answers.

      Identify organizational policy gaps

      Use these templates as a starting point

      Entitlements

      Download the Mobile Device Connectivity & Allowance Policy template.

      Purchasing & Reimbursement

      Download the Purchasing Policy template.

      Download the Mobile Device Reimbursement Policy template.

      Download the Mobile Device Reimbursement Agreement template.

      Acceptable Use

      Download the General Security – User Acceptable Use Policy template.

      Personal Device Use

      Download the BYOD Acceptable Use Policy template.

      Download the Mobile Device Remote Wipe Waiver template.

      Employee Monitoring

      Download the General Security – User Acceptable Use Policy template.

      Visit the Reduce and Manage Your Organization’s Insider Threat Risk blueprint to address this gap.

      2.3.2 Answer these security policy questions

      Identify if there are different expectations for certain user groups, where exceptions are allowed, and how these policies will be enforced.

      Use Cases

      • What data and use cases are subject to stricter security measures?
      • Are certain use cases or data prohibited on personal devices?
      • Are there restrictions around where certain use cases are performed and by whom?

      Patching

      • Are users expected to apply OS and app updates and patches? Or does IT automate patching?

      Physical Security

      • What does the user need to do to secure their equipment?
      • If a device is lost or stolen, who does the user contact to report the lost or stolen device?

      Cybersecurity

      • How will IT enforce security configuration baselines?
      • What does the user need to do (or not do) to secure their device?
      • Are certain users allowed to have local admin rights?
      • What happens when a device doesn’t comply with the required security configuration baseline?

      Use the “Policies” section of the End-User Computing Strategy Template to document these answers.

      Identify security policy gaps

      Use these templates as a starting point

      Use Cases

      Download the General Security – User Acceptable Use Policy template.

      Visit the Discover and Classify Your Data blueprint to address this gap.

      Patching

      Download the General Security – User Acceptable Use Policy template.

      Physical and Cyber Security

      Download the General Security – User Acceptable Use Policy template.

      Visit the Develop and Deploy Security Policies blueprint to address this gap.

      For help defining your own security configuration baselines for each operating system, reference best practice documentation such as:

      National Institute of Standards and Technology’s National Checklist Program.

      Center for Internet Security’s solutions.

      Microsoft’s security baseline settings for Windows 10 and 11 Configuration Service Providers.

      Phase 3

      Build the Roadmap

      Set the Direction

      1.1 Identify Desired Benefits

      1.2 Perform a User Group Analysis

      1.3 Define the Vision

      Define the Offering

      2.1 Define the Standard Offerings

      2.2 Outline Supporting Services

      2.3 Define Governance and Policies

      Build the Roadmap

      3.1 Develop Initiatives

      This phase will walk you through the following activities:

      • Defining initiatives for each EUC domain
      • Building a customer journey map for any end-user computing migrations
      • Building a roadmap for EUC initiatives

      This phase involves the following participants:

      • End-User Computing Team

      Step 3.1

      Develop Initiatives

      Activities

      3.1.1 Identify initiatives for each EUC practice

      3.1.2 Build out the user’s migration journey map

      3.1.3 Build out a list of initiatives

      Build the Roadmap

      This step requires the following inputs:

      • User group workbook
      • Migration initiatives

      This step involves the following participants:

      • Infrastructure Director
      • Head of End-User Computing
      • End-User Computing Team
      • Project Manager (if applicable)

      Outcomes of this step

      • End-user computing roadmap
      • Migration plan

      3.1.1 Identify the gaps in each EUC area

      Build a high-level profile of the changes you want to make

      For each of the five areas, build a profile for the changes you want to implement. Record:

      1. The owner of the area
      2. The objective that you want to accomplish
      3. The desired benefits from focusing on that area
      4. Any dependencies to the work
      5. Risks that can cause the objective and benefits to not be achieved

      Identify the initiatives involved in each area.

      Document these profiles and initiatives in the “Roadmap” section of your End-User Computing Strategy Template.

      1. Devices
        • Corporate-issued devices
        • Standard offerings
      2. User Support
        • Self-service
        • Tier 1 support
      3. Use Cases
        • Providing value
        • Business apps
      4. Policy & Governance
        • Personal device use
        • IT policy
      5. Fitness for Use
        • Securing devices
        • Patching

      Your initiatives may require a user migration

      Plan the user’s migration journey

      Consider each user group’s and each persona’s unique needs and challenges throughout the migration.

      1. Preparing to migrate: The user may need to schedule the migration with IT and back up files.
      2. Migrating: IT executes the migration (e.g. updates the OS, changes management tools).
      3. Getting assistance: When a user experiences an error during the migration, how will they get help from IT?
      4. Post-migration: How will IT and the user know that the migration was successful one week later?

      Understand the three migration approaches

      Online

      Users execute the migrate on their own (e.g. Microsoft’s consumer migration to Windows 10).

      In person

      Users come in person, select a device, and perform the migration with a specialist. If the device needs support, they return to the same place (e.g. buying a computer from a store).

      Hybrid

      Users select a device. When the device is ready, they can schedule time to pick up the device and perform the migration with a specialist (e.g. purchasing an iPhone in advance from Apple’s website with in-store pick-up).

      Be prepared to support remotely

      Migrations to the new tool may fail. IT should check in with the user to confirm that the device successfully made the migration.

      3.1.2 Build out the user’s migration journey map

      Contemplate a roadmap to plan for end-user computing initiatives

      • As a group, brainstorm migration initiatives.
      • For each of the four phases, identify:
        • User activities: actions we need the user to do
        • IT activities: actions and processes that IT will perform internally
        • User touchpoints with IT: how the user will interact with the IT group
        • Opportunities: ideas for how IT can provide additional value to the end user in this phase.
      • Use the example in the End-User Computing Strategy Template as a starting point.

      Download the End-User Computing Strategy Template.

      Embed requirements gathering throughout your roadmap

      Use a combination of surveys, focus groups, and interviews

      You’re doing more than eliciting opinions – you’re performing organizational change management.

      • Use surveys to profile the demand for specific requirements. When a project is announced, develop surveys to gauge what users consider must-have, should-have, and could-have requirements.
      • Interviews should be used with high-value targets. Those who receive one-on-one face time can help generate good requirements and allow for effective communication around requirements.
      • Focus groups are used to get input from multiple people in a similar role. This format allows you to ask a few open-ended questions to groups of about five people.

      The benefits of interviews and focus groups:

      • Foster direct engagement: IT is able to hear directly from stakeholders about what they are looking to do with a solution and the level of functionality that they expect from it.
      • Offer greater detail: With interviews, greater insight can be gained by leveraging information that traditional surveys wouldn’t uncover. Face-to-face interactions provide thorough answers and context that helps inform requirements.
      • Remove ambiguity: Face-to-face interactions allow opportunities to follow up on ambiguous answers. Clarify what stakeholders are looking for and expect in a project.
      • Enable stakeholder management: Interviews are a direct line of communication with project stakeholders. They provide input and insight and help to maintain alignment, plan next steps, and increase awareness within the IT organization.

      Activity instructions:

      1. Early requirements ideation: Identify who you want to interview through one-on-one meetings and focus groups.
      2. Requirements validation and prioritization: Identify which user groups you plan to survey and when.
      3. Usability testing: Plan to include usability testing during each phase. Build it into your release practices.

      3.1.3 Build out a list of initiatives

      Download a copy of the Roadmap Tool

      On tab “1. Setup”:

      • Update category 1 to be all the EUC areas (i.e. Devices, User Support).
      • Update category 2 and category 3 with meaningful items (e.g. operating system, device model, persona group).

      Use tab “2. Data Entry” to record your list of initiatives.

      • Each initiative should have its own row. Write a high-level summary under “Roadmap Item” and include more detail under “Description and Rationale.”
      • Enter each initiative’s effort, priority, and timeline for beginning. These are mandatory fields for tab “3. Roadmap” to work properly.

      Use tab “3. Roadmap” to visualize your data. You will have to press “Refresh All” under Data in the ribbon for the PivotChart to update.

      Copy the roadmap visual on tab “3. Roadmap” into your End-User Computing Strategy Template. You can also copy the list of initiatives over into the document.

      Download the Roadmap Tool.

      Summary of Accomplishment

      Problem Solved

      You built a strategy to improve the balance between user enablement, risk mitigation, and cost optimization. Throughout the blueprint, you identified opportunities to provide additional value to end users and stakeholders during these activities:

      • Goals cascade
      • User group analysis
      • Definition of standard device types and platforms
      • IT support shift-left analysis
      • Policy gap analysis
      • Roadmapping

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech workshop.

      Contact your account representative for more information.

      workshops@infotech.com

      1-888-670-8889

      Additional Support

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech Workshop.

      Contact your account representative for more information.

      workshops@infotech.com 1-888-670-8889

      To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.

      Info-Tech analysts will join you and your team at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      Identify User Groups

      Identify each user group based on the business processes, tasks, and applications they use.

      Define Standard Device Offerings

      Record your provisioning models for each user group and the primary and secondary devices, apps, and peripherals that each group receives.

      Related Info-Tech Research

      Simplify Remote Deployment With Zero-Touch Provisioning

      This project helps you align your zero-touch approach with stakeholder priorities and larger IT strategies. You will be able to build your zero-touch provisioning and patching plan from both the asset lifecycle and the end-user perspective to create a holistic approach that emphasizes customer service. Tailor deployment plans to more easily scope and resource deployment projects.

      Implement Hardware Asset Management

      This project will help you analyze the current state of your HAM program, define assets that will need to be managed, and build and involve the ITAM team from the beginning to help embed the change. It will also help you define standard policies, processes, and procedures for each stage of the hardware asset lifecycle, from procurement through to disposal.

      Govern Office 365

      This project will help you conduct a goals exercise and capability assessment for Office 365. You will be able to refine governance objectives, build out controls, formalize governance, build out one pagers, and finalize a communication plan.

      Research Contributors and Experts

      • Steve Fox, Deputy IT Director, Virginia State Corporation Commission
      • Mazen Joukhadar, TransForm Shared Service Organization
      • Nathan Schlaud, PMO Senior Director, RPC Inc.
      • Rebecca Mountjoy, Infrastructure Systems Manager, BlueScope Buildings
      • DJ Robins, Director of Information Technology, Mohawk MedBuy
      • Jason Jenkins, Tech. Specialist, Michal Baker Corp.
      • Brad Wells, IT Infrastructure Solutions Architect, London Police Service
      • Danelle Peddell, Director, Project Management Office, Emco Corporation
      • John Annand, Principal Research Director, Info-Tech Research Group
      • Allison Kinnaird, Research Director and Research Lead, Info-Tech Research Group
      • Sandi Conrad, Principal Research Director, Info-Tech Research Group
      • Andrew Kum-Seun, Senior Research Analyst, Info-Tech Research Group
      • Mark Tauschek, Vice President IT Infrastructure & Operations Research, Info-Tech Research Group

      A special thank-you to 6 anonymous contributors

      Bibliography

      “2020 Annual Report and Proxy.” Citrix, 2020. Accessed Oct. 2021.

      “2021 BYOD Security Report.” Cybersecurity Insiders, 2021. Web.

      Anderson, Arabella. “12 Remote Work Statistics to Know in 2022.” NorthOne, 2021. Accessed Oct. 2021.

      Bayes, Scarlett. “ITSM: 2021 & Beyond.” Service Desk Institute, 14 April 2021, p. 14. Web.

      Belton, Padraig. “Intel: Chip shortage will extend to at least 2023.” Light Reading, 22 Oct. 2021. Web.

      Beroe Inc. “Demand for PC Components Saw a Surge Due to COVID-19, Says Beroe Inc.” Cision PR Newswire, 2 Sept. 2021. Web.

      Devaraj, Vivekananthan. “Reference Architecture: Remote PC Access.” Citrix, 2021. Accessed Aug. 2021.

      “Elements of the Project Charter and Project Scope Statement.” A Guide to PMBOK, 7th edition, PMI, 2021. Accessed Sept. 2021.

      Elliott, Christopher. “This Is How The Pandemic Improved Customer Service.” Forbes, 2021. Accessed Oct. 2021.

      “Enable TMP 2.0 on your PC.” Microsoft, Support, Aug. 2021. Web.

      “End User Computing Trends to Look Out for in 2021.” Stratodesk, 30 Oct. 2020. Accessed September 2021.

      “Global State of Customer Service: The Transformation of Customer Service from 2015 to Present Day.” Microsoft, 2019. Web.

      Goodman, Elizabeth et al. “Observing the User Experience” A Practitioner's Guide to User Research, 2nd edition. Elsevier, 2012. Accessed Sept. 2021.

      Govindarajulu, Chittibabu. “An Instrument to Classify End-Users Based On the User Cube” Informing Science, June 2002. Accessed September 2021.

      Griffith, Eric. “Remote Employees to Bosses: Our PCs Suck!” PCMag, 11 Oct. 2021. Web.

      Hutchings, Jeffrey D., and Craig A. de Ridder. “Impact of Remote Working on End User Computing Solutions and Services.” Pillsbury, 2021. Accessed Sept. 2021

      “ITIL4 Create, Deliver, and Support.” Axelos, 2020. Accessed Sept. 2021.

      “ITIL4 Drive Stakeholder Value” Axelos, 2020. Accessed Sept. 2021.

      Mcbride, Neil, and Trevor Wood-Harper. “Towards User-Oriented Control of End-User Computing in Large Organizations” Journal of Organizational and End User Computing, vol. 14, no. 1, pp. 33-41, 2002. Accessed September 2021.

      ““Microsoft Endpoint Configuration Manager Documentation.” Microsoft Docs, Microsoft, 2021. Accessed Sept. 2021.

      “Microsoft Intune documentation.” Microsoft Docs, Microsoft. Accessed Sept. 2021.

      “Mobile Cellular Subscriptions (per 100 People).” The World Bank, International Telecommunication Union (ITU) World Telecommunication/ICT Indicators Database, 2020. Web.

      Morgan, Jacob. “The Employee Experience Advantage: How to Win the War for Talent by Giving Employees the Workspaces they Want, the Tools they Need, and a Culture They Can Celebrate.” Wiley, 2017. Accessed Sept. 2021.

      Murphy, Anna. “How the pandemic has changed customer support forever.” Intercom, 2021. Accessed Sept. 2021.

      “Operating System Market Share Worldwide, Jan 2021-Jan 2022.” StatCounter GlobalStats, 2022. Web.

      “Operating System Market Share Worldwide, Jan-Dec 2011.” StatCounter GlobalStats, 2012. Web.

      Pereira, Karla Susiane, et al. “A Taxonomy to Classify Risk End-User Profile in Interaction with the Computing Environment.” In: Tryfonas T. (eds.) Human Aspects of Information Security, Privacy, and Trust. HAS 2016. Lecture Notes in Computer Science, vol. 9750. Accessed Sept. 2021.

      Perrin, Andrew. “Mobile Technology and Home Broadband 2020.” Pew Research Center, 3 June 2021. Web.

      Quan-Haase, Anabel. “Technology and Society: Social Networks, Power, and Inequality” Oxford University Press, 2012. Accessed Aug. 2021.

      Reed, Karin, and Joseph Allen. “Suddenly Virtual: Making Remote Meetings Work.” Wiley, 2021. Accessed Aug. 2021.

      Rockart, John F., and Lauren S. Flannery. “The management of end user computing.” Communications of the ACM, vol. 26, no. 10, Oct. 1983. Accessed September 2021.

      Turek, Melanie. “Employees Say Smartphones Boost Productivity by 34 Percent: Frost & Sullivan Research.” Samsung Insights, 3 Aug. 2016. Web.

      Vladimirskiy, Vadim. “Windows 365 vs. Azure Virtual Desktop (AVD) – Comparing Two DaaS Products.” Nerdio, 2021. Accessed Aug. 2021.

      “VMware 2021 Annual Report.” VMware, Financial Document Library, 2021. Web.

      VMworld 2021, Oct. 2021.

      Vogels, Emily A. “Digital divide persists even as americans with lower incomes make gains in tech adoption.” Pew Research Center, 22 June 2021. Web.

      “What is End-User computing?” VMware, 2021. Accessed Aug. 2021.

      “Windows 10 Home and Pro.” Microsoft, Docs, 2021. Web.

      Zibreg, Christian. “Microsoft 365 Now Boasts Over 50 Million Subscribers.” MUD, 29 April 2021. Web.

      Create an Effective SEO Keyword Strategy

      • Buy Link or Shortcode: {j2store}568|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Marketing Solutions
      • Parent Category Link: /marketing-solutions

      Digital Marketers working with an outdated or bad SEO strategy often see:

      • Declining keyword ranking and traffic
      • Poor keyword strategy
      • On-page errors

      Our Advice

      Critical Insight

      Most marketers fail in their SEO efforts because they focus on creating content for computers, not people.

      Impact and Result

      Using the SoftwareReviews methodology, digital marketers are able to break up their SEO project and data into bite-sized, actionable steps that focus on long-term improvement. Our methodology includes:

      • Competitive keyword research and identification of opportunities
      • On-page keyword strategy

      Create an Effective SEO Keyword Strategy Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Create an Effective SEO Keyword Strategy

      Update your on-page SEO strategy with competitively relevant keywords.

      • Create an Effective SEO Keyword Strategy Storyboard
      [infographic]

      Further reading

      Create an Effective SEO Keyword Strategy
      Update your on-page SEO strategy with competitively relevant keywords.

      Analyst Perspective

      Most marketers fail in their SEO efforts because they focus on creating content for computers, not people.

      Leading search engine optimization methods focus on creating and posting relevant keyword-rich content, not just increasing page rank. Content and keywords should move a buyer along their journey, close a sale, and develop long-term relationships. Unfortunately, many SEO specialists focus on computers, not the buyer. What's even more concerning is that up to 70% of SaaS businesses have already been impacted by outdated and inefficient SEO techniques. Poor strategies often focus on ballooning SEO metrics in the short-term instead of building the company's long-term PageRank.

      Best-in-class digital marketers stop chasing the short-term highs and focus on long-term growth. This starts with developing a competitive keyword strategy and updating website content with the new keywords.

      SEO is a large topic, so we have broken the strategy into small, easy-to-implement steps, taking the guesswork out of how to use the data from SEO tools and giving CMOs a solid path to increase their SEO results.

      This is a picture of Terra Higginson

      Terra Higginson
      Marketing Research Director
      SoftwareReviews

      Executive Summary

      Your Challenge

      Digital marketers working with an outdated or bad SEO strategy often see:

      • Declining keyword ranking and traffic
      • Poor keyword strategy
      • On-page errors

      Search algorithms change all the time, which means that the strategy is often sitting on the sifting sands of technology, making SEO strategies quickly outdated.

      Common Obstacles

      Digital marketers are responsible for developing and implementing a competitive SEO strategy but increasingly encounter the following obstacles:

      • SEO practitioners that focus on gaming the system
      • Ever-changing SEO technology
      • Lack of understanding of the best SEO techniques
      • SEO techniques focus on the needs of computers, not people
      • Lack of continued investment

      SoftwareReviews' Approach

      Using the SoftwareReviews methodology, digital marketers are able to break up their SEO project and data into bite-sized, actionable steps that focus on long-term improvement. Our methodology includes:

      • Competitive keyword research and identification of opportunities
      • On-page keyword strategy

      Our methodology will take a focused step-by-step strategy in a series of phases that will increase PageRank and competitive positioning.

      SoftwareReviews' SEO Methodology

      In this blueprint, we will cover:

      Good SEO vs. Poor SEO Techniques

      The difference between good and bad SEO techniques.

      Common Good
      SEO Techniques

      Common Poor
      SEO Techniques

      • Writing content for people, not machines.
      • Using SEO tools to regularly adjust and update SEO content, keywords, and backlinks.
      • Pillar and content cluster strategy in addition to a basic on- and off-page strategy.
      • Keyword stuffing and content duplication.
      • A strategy that focuses on computers first and people second.
      • Low-quality or purchased backlinks.

      Companies With Great SEO…

      Keyword Strategy

      • Have identified a keyword strategy that carves out targets within the white space available between themselves and the competition.

      Error-Free Site

      • Have error-free sites without duplicate content. Their URLs and redirects are all updated. Their site is responsive, and every page loads in under two seconds.

      Pillar & Content Clusters

      • Employ a pillar and content cluster strategy to help move the buyer through their journey.

      Authentic Off-Page Strategy

      • Build an authentic backlink strategy that incorporates the right information on the right sites to move the buyer through their journey.

      SEO Terms Defined

      A glossary to define common Phase 1 SEO terms.

      Search Volume: this measures the number of times a keyword is searched for in a certain time period. Target keywords with a volume of between 100-100,000. A search volume greater than 100,000 will be increasingly difficult to rank (A Beginner's Guide to Keyword Search Volume, 2022, Semrush).

      Keyword Difficulty: the metric that quantifies how difficult it will be to rank for a certain keyword. The keyword difficulty percentage includes the number of competitors attempting to rank for the same keyword, the quality of their content, the search intent, backlinks, and domain authority (Keyword Difficulty: What Is It and Why Is It Important? 2022, Semrush).

      Intent: this metric focuses on the intent of the user's search. All search intent is categorized into Informational, Commercial, Navigational, and Transactional (What Is Search Intent? A Complete Guide, 2022, Semrush).

      On-Page SEO: refers to the practice of search engine optimizing elements of your site such as title tags, internal links, HTML code, URL optimization, on-page content, images, and user experience.

      Off-Page SEO: refers to the practice of optimizing brand awareness (What Is Off-Page SEO? A Comprehensive Guide, 2022, Semrush).

      H1: HTML code that tells a search engine the title of the page (neilpatel.com).

      SEO Tool: A subscription-based all-in-one search engine optimization MarTech tool.

      Google's mission is to organize the world's information and make it universally accessible and useful… We believe Search should deliver the most relevant and reliable information available.
      – An excerpt from Google's mission statement

      Your Challenge

      Google makes over 4.5k algorithm changes per year1, directly impacting digital marketing search engine optimization efforts.

      Digital marketers with SEO problems will often see the following issues:

      • Keyword ranking – A decline in keyword ranking is alarming and results in decreased PageRank.
      • Bounce rate – Attracting the wrong audience to your site will increase the bounce rate because the H1 doesn't resonate with your audience.
      • Outdated keywords – Many companies are operating on a poor keyword strategy, or even worse, no keyword strategy. In addition, many marketers haven't updated their strategy to include pillar and cluster content.
      • Errors – Neglected sites often have a large number of errors.
      • Bad backlinks – Neglected sites often have a large number of toxic backlinks.

      The best place to hide a dead body is on page two of the search results.
      – Huffington Post

      Common Obstacles

      Digital marketers are responsible for developing and executing a competitive SEO strategy but increasingly encounter the following obstacles:

      • Inefficient and ineffective SEO practitioners.
      • Changing SEO technology and search engine algorithms.
      • Lack of understanding of the best-in-class SEO techniques.
      • Lack of a sustainable plan to manage the strategy and invest in SEO.

      SEO is a helpful activity when it's applied to people-first content. However, content created primarily for search engine traffic is strongly correlated with content that searchers find unsatisfying.
      – Google Search Central Blog

      Benefits of Proper SEO

      A good SEO keyword strategy will create long-term, sustainable SEO growth:

      • Write content for people, not algorithms – Good SEO prioritizes the needs of humans over the needs of computers, being ever thoughtful of the meaning of content and keywords.
      • Content that aligns with intent – Content and keyword intent will align with the buyer journey to help move prospects through the funnel.
      • Competitive keyword strategy – Find keyword white space for your brand. Keywords will be selected to optimize your ranking among competition with reasonable and sustainable targets.
      • Actionable and impactful fixes – By following the SoftwareReviews phases of SEO, you will be able to take a very large task and divide it into conquerable actions. Small improvements everyday lead to very large improvements over time.

      Digital Marketing SEO Stats

      61%
      61% of marketers believe that SEO is the key to online success.
      Source: Safari Digital

      437%
      Updating an existing title tag with an SEO optimised one can increase page clicks by more than 437%.
      Source: Safari Digital

      Good SEO Aligns With Search Intent

      What type of content is the user searching for? Align your keyword to the logical search objective.

      Informational

      This term categorizes search intent for when a user wants to inform or educate themselves on a specific topic.

      Commercial

      This term categorizes search intent for when a user wants to do research before making a purchase.

      Transactional

      This term categorizes search intent for when a user wants to purchase something.

      Navigational

      This term categorizes search intent for when a user wants to find a specific page.

      SoftwareReviews' Methodology toCreate an Effective SEO Strategy

      1. Competitive Analysis & Keyword Discovery 2. On-Page Keyword Optimization
      Phase Steps
      1. Make a list of keywords in your current SEO strategy – including search volume, keyword difficulty percentage, intent.
      2. Research the keywords of top competitors.
      3. Make a list of target keywords you would like to own – including the search volume, keyword difficulty percentage, and intent. Make sure that these keywords align with your buyer persona.
      1. List product and service pages, along with the URL and current ranking(s) for the keyword(s) for that URL.
      2. Create a new individual page strategy for each URL. Record the current keyword, rank, title tag, H1 tag, and meta description. Then, with keyword optimization in mind, develop the new title tag, new H1 tag, and new meta description. Build the target keywords into the pages and tags.
      3. Record the current ranking for the pages' keywords then reassess after three to six months.
      Phase Outcomes
      • Understanding of competitive landscape for SEO
      • A list of target new keywords
      • Keyword optimized product and service pages

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1 Phase 2

      Call #1: Identify your current SEO keyword strategy.

      Call #2: Discuss how to start a competitive keyword analysis.

      Call #4: Discuss how to build the list of target keywords.

      Call #6: Discuss keyword optimization of the product & services pages.

      Call #8: (optional)

      Schedule a call to update every three to six months.

      Call #3: Discuss the results of the competitive keyword analysis.

      Call #5: Discuss which pages to update with new target keywords.

      Call #7: Review final page content and tags.

      Call #9: Schedule a call for SEO Phase 2: On-Page Technical Refinement.

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is between 8 to 12 calls over the course of 1 to 2 months.

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1 Phase 2

      Call #1: Identify your current SEO keyword strategy.

      Call #2: Discuss how to start a competitive keyword analysis.

      Call #4: Discuss how to build the list of target keywords.

      Call #6: Discuss keyword optimization of the product & services pages.

      Call #8: (optional)

      Schedule a call to update every three to six months.

      Call #3: Discuss the results of the competitive keyword analysis.

      Call #5: Discuss which pages to update with new target keywords.

      Call #7: Review final page content and tags.

      Call #9: Schedule a call for SEO Phase 2: On-Page Technical Refinement.

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is between 8 to 12 calls over the course of 1 to 2 months.

      SoftwareReviews offers various levels of support to best suit your needs

      Included Within an Advisory Membership Optional Add-Ons
      DIY Toolkit Guided Implementation Workshop Consulting
      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful." "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track." "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place." "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Insight Summary

      People-First Content

      Best-in-class SEO practitioners focus on people-first content, not computer-first content. Search engine algorithms continue to focus on how to rank better content first, and a strategy that moves your buyers through the funnel in a logical and cohesive way will beat any SEO trick over the long run.

      Find White Space

      A good SEO strategy uses competitive research to carve out white space and give them a competitive edge in an increasingly difficult ranking algorithm. An understanding of the ideal client profile and the needs of their buyer persona(s) sit as a pre-step to any good SEO strategy.

      Optimize On-Page Keywords

      By optimizing the on-page strategy with competitively relevant keywords that target your ideal client profile, marketers are able to take an easy first step at improving the SEO content strategy.

      Understand the Strategy

      If you don't understand the strategy of your SEO practitioner, you are in trouble. Marketers need to work hand in hand with their SEO specialists to quickly uncover gaps, create a strategy that aligns with the buyer persona(s), and execute the changes.

      Quality Trumps Quantity

      The quality of the prospect that your SEO efforts bring to your site is more important than the number of people brought to your site.

      Stop Here and Ask Yourself:

      • Do I have an updated (completed within the last two years) buyer persona and journey?
      • Do I know who the ICP (ideal client profile) is for my product or company?

      If not, stop here, and we can help you define your buyer persona and journey, as well as your ideal client profile before moving forward with SEO Phase 1.

      The Steps to SEO Phase 1

      The Keyword Strategy

      1. Current Keywords
        • Identify the keywords your SEO strategy is currently targeting.
      2. Competitive Analysis
        • Research the keywords of competitor(s). Identify keyword whitespace.
      3. New Target Keywords
        • Identify and rank keywords that will result in more quality leads and less competition.
      4. Product & Service Pages
        • Identify your current product and service pages. These pages represent the easiest content to update on your site.
      5. Individual Page Update
        • Develop an SEO strategy for each of your product and service pages, include primary target keyword, H1, and title tags, as well as keyword-rich description.

      Resources Needed for Search Engine Optimization

      Consider the working skills required for search engine optimization.

      Required Skills/Knowledge

      • SEO
      • Web development
      • Competitive analysis
      • Content creation
      • Understanding of buyer persona and journey
      • Digital marketing

      Suggested Titles

      • SEO Analyst
      • Competitive Intelligence Analyst
      • Content Marketing Manager
      • Website Developer
      • Digital Marketing Manager

      Digital Marketing Software

      • CMS that allows you to easily access and update your content

      SEO Software

      • SEO tool

      Step 1: Current Keywords

      Use this sheet to record your current keyword research.

      Use your SEO tool to research keywords and find the following:
      Use a quality tool like SEMRush to obtain SEO data.

      1. Keyword difficulty
      2. Search volume
      3. Search intent

      This is a screenshot of the SEO tool SEMRush, which can be used to identify current keywords.

      Step 2: Competitive Analysis

      Use this sheet to guide the research on your competitors' keywords.

      Use your SEO tool to find the following:

      1. Top organic keywords
      2. Ranking of keywords
      3. Domain authority and trust
      4. Position changes

      This is a screenshot of the SEO tool SEMRush, which can be used to perform an competitive analysis

      Step 3: New Target Keywords

      Use this sheet to record target keywords that have a good volume but are less competitive. The new target keywords should align with your buyer persona and their journey.

      Use your SEO tool to research keywords and find the following:
      Use a quality tool like SEMRush to obtain SEO data.

      1. Keyword difficulty
      2. Search volume
      3. Search intent

      This is a screenshot of the SEO tool SEMRush, which can be used to identify new target keywords.

      Step 4: Product & Service Pages

      Duplicate this page so that you have a separate page for each URL from Step 4

      Use this sheet to identify your current product and service pages.

      Use your SEO tool to find the following:

      1. Current rank
      2. Current keywords

      This is a screenshot of the SEO tool SEMRush, showing where you can display product and service pages.

      Step 5: Individual Page Strategy

      Develop a keyword strategy for each of your product and service pages. Use a fresh page for each URL.

      Date last optimized:
      mm/dd/yyyy

      This is a screenshot of the SEO tool SEMRush, with an example of how you can use an individual page strategy to develop a keyword strategy.

      Bibliography

      Council, Y. "Council Post: The Rundown On Black Hat SEO Techniques And Why You Should Avoid Them." Forbes, 2022. Accessed September 2022.

      "Our approach – How Google Search works." Google Search. Accessed September 2022.

      "The Best Place to Hide a Dead Body is Page Two of Google." HuffPost, 2022. Accessed September 2022.

      Patel, Neil. "How to Create the Perfect H1 Tag for SEO." neilpatel.com. Accessed September 2022.

      Schwartz, B. "Google algorithm updates 2021 in review: Core updates, product reviews, page experience and beyond." Search Engine Land, 2022. Accessed September 2022.

      Schwartz, B. "Google algorithm updates 2021 in review: Core updates, product reviews, page experience and beyond." Search Engine Land, 2022. Accessed September 2022.

      IBM i Migration Considerations

      • Buy Link or Shortcode: {j2store}109|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Strategy and Organizational Design
      • Parent Category Link: /strategy-and-organizational-design

      IBM i remains a vital platform and now many CIOs, CTOs, and IT leaders are faced with the same IBM i challenges regardless of industry focus: how do you evaluate the future viability of this platform, assess the future fit and purpose, develop strategies, and determine the future of this platform for your organization?

      Our Advice

      Critical Insight

      For organizations that are struggling with the iSeries/IBM i platform, resourcing challenges are typically the culprit. An aging population of RPG programmers and system administrators means organizations need to be more pro-active in maintaining in-house expertise. Migrating off the iSeries/IBM i platform is a difficult option for most organizations due to complexity, switching costs in the short term, and a higher long-term TCO.

      Impact and Result

      The most common tactic is for the organization to better understand their IBM i options and adopt some level of outsourcing for the non-commodity platform retaining the application support/development in-house. To make the evident, obvious; the options here for the non-commodity are not as broad as with commodity server platforms. Options include co-location, onsite outsourcing, managed and public cloud services.

      IBM i Migration Considerations Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. IBM i Migration Considerations – A brief deck that outlines key migration options for the IBM i platforms.

      This project will help you evaluate the future viability of this platform; assess the fit, purpose, and price; develop strategies for overcoming potential challenges; and determine the future of this platform for your organization.

      • IBM i Migration Considerations Storyboard

      2. Infrastructure Outsourcing IBM i Scoring Tool – A tool to collect vendor responses and score each vendor.

      Use this scoring sheet to help you define and evaluate IBM i vendor responses.

      • Infrastructure Outsourcing IBM i Scoring Tool
      [infographic]

      Further reading

      IBM i Migration Considerations

      Don’t be overwhelmed by IBM i migration options.

      Executive Summary

      Your Challenge

      IBM i remains a vital platform and now many CIO, CTO, and IT leaders are faced with the same IBM i challenges regardless of industry focus; how do you evaluate the future viability of this platform, assess the future fit and purpose, develop strategies, and determine the future of this platform for your organization?

      Common Obstacles

      For organizations that are struggling with the iSeries/IBM i platform, resourcing challenges are typically the culprit. An aging population of RPG programmers and system administrators means organizations need to be more proactive in maintaining in-house expertise. Migrating off the iSeries/IBM i platform is a difficult option for most organizations due to complexity, switching costs in the short term, and a higher long-term TCO.

      Info-Tech Approach

      The most common tactic is for the organization to better understand its IBM i options and adopt some level of outsourcing for the non-commodity platform, retaining the application support/development in-house. To make the evident, obvious: the options here for the non-commodity are not as broad as with commodity server platforms. Options include co-location, onsite outsourcing, managed hosting, and public cloud services.

      Info-Tech Insight

      “For over twenty years, IBM was ‘king,’ dominating the large computer market. By the 1980s, the world had woken up to the fact that the IBM mainframe was expensive and difficult, taking a long time and a lot of work to get anything done. Eager for a new solution, tech professionals turned to the brave new concept of distributed systems for a more efficient alternative. On June 21, 1988, IBM announced the launch of the AS/400, their answer to distributed computing.” (Dale Perkins)

      Review

      We help IT leaders make the most of their IBM i environment.

      Problem Statement:

      The IBM i remains a vital platform for many businesses and continues to deliver exceptional reliability and performance and play a key role in the enterprise. With the limited resources at hand, CIOs and the like must continually review and understand their migration path with the same regard as any other distributed system roadmap.

      This research is designed for:

      • IT strategic direction decision makers
      • IT managers responsible for an existing iSeries or IBM i platform
      • Organizations evaluating platforms for mission-critical applications

      This research will help you:

      1. Evaluate the future viability of this platform.
      2. Assess the fit, purpose, and price.
      3. Develop strategies for overcoming potential challenges.
      4. Determine the future of this platform for your organization.

      The “fit for purpose” plot

      Thought Model

      We will investigate the aspect of different IBM i scenarios as they impact business, what that means, and how that can guide the questions that you are asking as you move to an aligned IBM i IT strategy. Our model considers:

      • Importance to Business Outcomes
        • Important to strategic objectives
        • Provides competitive advantage
        • Non-commodity IT service or process
        • Specialized in-house knowledge required
      • Vendor’s Performance Advantage
        • Talent or access to skills
        • Economies of scale or lower cost at scale
        • Access to technology

      Info-Tech Insights

      With multiple control points to be addressed, care must be taken in simplifying your options while addressing all concerns to ease operational load.

      Map different 'IBM i' scenarios with axes 'Importance to Business Outcomes - Low to High' and 'Vendor’s Performance Advantage - Low to High'. Quadrant labels are '[LI/LA] Potentially Outsource: Service management, Help desk, desk-side support, Asset management', '[LI/HA] Outsource: Application & Infra Support, Web Hosting, SAP Support, Email Services, Infrastructure', '[HI/LA] Insource (For Now): Application development tech support', and '[HI/HA] Potentially Outsource: Onshore or offshore application maintenance'.

      IBM i environments are challenging

      “The IBM i Reality” – Darin Stahl

      Most members relying on business applications/workloads running on non-commodity platforms (zSeries, IBM i, Solaris, AIX, etc.) are first motivated to get out from under the perceived higher costs for the hardware platform.

      An additional challenge for non-commodity platforms is that from an IT Operations Management perspective they become an island with a diminishing number of integrated operations skills and solutions such as backup/restore and monitoring tools.

      The most common tactic is for the organization to adopt some level of outsourcing for the non-commodity platform, retaining the application support and development in-house.

      Key challenges with current IBM i environments:
      1. DR Requirements
        Understand what the business needs are and where users and resources are located.
      2. Market Lack of Expertise
        Skilled team members are hard to find.
      3. Cost Management
        There is a perceived cost disadvantage to managing on-prem solutions.
      4. Aging Support Teams
        Current support teams are aging with little backfill in skill and experience.

      Understand your options

      Co-Location

      A customer transitions their hardware environment to a provider’s data center. The provider can then manage the hardware and “system.”

      Onsite Outsourcing

      A provider will support the hardware/system environment at the client’s site.

      Managed Hosting

      A customer transitions their legacy application environment to an off-prem hosted, multi-tenanted environment.

      Public Cloud

      A customer can “re-platform” the non-commodity workload into public cloud offerings or in a few offerings “re-host.”

      Co-Location

      Provider manages the data center hardware environment.

      Abstract

      Here a provider manages the system data center environment and hardware; however, the client’s in-house IBM i team manages the IBM i hardware environment and the system applications. The client manages all of the licenses associated with the platform as well as the hardware asset management considerations. This is typically part of a larger services or application transformation. This effectively outsources the data center management while maintaining all IBM i technical operations in-house.

      Advantages

      • On-demand bandwidth
      • Cost effective
      • Secure and compliant environment
      • On-demand remote “hands and feet” services
      • Improved IT DR services
      • Data center compliance

      Considerations

      • Application transformation
      • CapEx cost
      • Fluctuating network bandwidth costs
      • Secure connectivity
      • Disaster recovery and availability of vendor
      • Company IT DR and BC planning
      • Remote system maintenance (HW)

      Info-Tech Insights

      This model is extremely attractive for organizations looking to reduce their data center management footprint. Idea for the SMB.

      Onsite Sourcing

      A provider will support the hardware/system environment at the client’s site.

      Abstract

      Here a provider will support and manage the hardware/system environment at the client’s site. The provider may acquire the customer’s hardware and provide software licenses. This could also include hiring or “rebadging” staff supporting the platform. This type of arrangement is typically part of a larger services or application transformation. While low risk, it is not as cost-effective as other deployment models.

      Advantages

      • Managed environment within company premises
      • Cost effective (OpEx expense)
      • Economies of scale
      • On-demand “as-a-service” model
      • Improved IT DR staffing services
      • 24x7 monitoring and support

      Considerations

      • Outsourced IT talent
      • Terms and contract conditions
      • IT staff attrition
      • Increased liability
      • Modified technical support and engagement
      • Secure connectivity and communication
      • Internal problem and change management

      Info-Tech Insights

      Depending on the application lifecycle and viability, in-house skill and technical depth is a key consideration when developing your IBM i strategy.

      Managed Hosting

      Transition legacy application environment to an off-prem hosted multi-tenanted environment.

      Abstract

      This type of arrangement is typically part of an application migration or transformation. In this model, a client can “re-platform” the application into an off-premises-hosted provider platform. This would yield many of the cloud benefits however in a different scaling capacity as experienced with commodity workloads (e.g. Windows, Linux) and the associated application.

      Advantages

      • Turns CapEx into OpEx
      • Reduces in-house need for diminishing or scarce human resources
      • Allows the enterprise to focus on the value of the IBM i platform through the reduction of system administrative toil
      • Improved IT DR services
      • Data center compliance

      Considerations

      • Application transformation
      • Network bandwidth
      • Contract terms and conditions
      • Modified technical support and engagement
      • Secure connectivity and communication
      • Technical security and compliance
      • Limited providers; reduced options

      Info-Tech Insights

      There is a difference between a “re-host” and “re-platform” migration strategy. Determine which solution aligns to the application requirements.

      Public Cloud

      Leverage “public cloud” alternatives with AWS, Google, or Microsoft AZURE.

      Abstract

      This type of arrangement is typically part of a larger migration or application transformation. While low risk, it is not as cost-effective as other deployment models. In this model, client can “re-platform” the non-commodity workload into public cloud offerings or in a few offerings “re-host.” This would yield many of the cloud benefits however in a different scaling capacity as experienced with commodity workloads (e.g. Windows, Linux).

      Advantages

      • Remote workforce accessibility
      • OpEx expense model
      • Improved IT DR services
      • Reduced infrastructure and system administration
      • Vendor management
      • 24x7 monitoring and support

      Considerations

      • Contract terms and conditions
      • Modified technical support and engagement
      • Secure connectivity and communication
      • Technical security and compliance
      • Limited providers; reduced options
      • Vendor/cloud lock-in
      • Application migration/”re-platform”
      • Application and system performance

      Info-Tech Insights

      This model is extremely attractive for organizations that consume primarily cloud services and have a large remote workforce.

      Understand your vendors

      • To best understand your options, you need to understand what IBM i services are provided by the industry vendors.
      • Within the following slides, you will find a defined activity with a working template that will create “vendor profiles” for each vendor.
      • As a working example, you can review the following partners:
      • Connectria (United States)
      • Rowton IT Solutions Ltd (United Kingdom)
      • Mid-Range (Canada)

      Info-Tech Insights

      Creating vendor profiles will help quickly filter the solution providers that directly meet your IBM i needs.

      Vendor Profile #1

      Rowton IT

      Summary of Vendor

      “Rowton IT thrive on creating robust and simple solutions to today's complex IT problems. We have a highly skilled and motivated workforce that will guarantee the right solution.

      Working with select business partners, we can offer competitive and cost effective packages tailored to suit your budget and/or business requirements.

      Our knowledge and experience cover vast areas of IT including technical design, provision and installation of hardware (Wintel and IBM Midrange), technical engineering services, support services, IT project management, application testing, documentation and training.”

      IBM i Services

      • ✔ IBM Power Hardware Sales
      • ✔ Co-Managed Services
      • ✔ DR/High Available Config
      • ✔ Full Managed Services
      • ✖ Co-Location Services
      • ✔ Public Cloud Services (AWS)

      URL
      rowtonit.com

      Regional Coverage:
      United Kingdom

      Logo for RowtonIT.com.

      Vendor Profile #2

      Connectria

      Summary of Vendor

      “Every journey starts with a single step and for Connectria, that step happened to be with the world’s largest bank, Deutsche Bank. Followed quickly by our second client, IBM. Since then, we have added over 1,000 clients worldwide. For 25 years, each customer, large or small, has relied on Connectria to deliver on promises made to make it easy to do business with us through flexible terms, scalable solutions, and straightforward pricing. Join us on our journey.”

      IBM i Services

      • ✔ IBM Power Hardware Sales
      • ✔ Co-Managed Services
      • ✔ DR/High Available Config
      • ✔ Full Managed Services
      • ✔ Co-Location Services
      • ✔ Public Cloud Services (AWS)

      URL
      connectria.com

      Regional Coverage:
      United States

      Logo for Connectria.

      Vendor Profile #3

      Mid-Range

      Summary of Vendor

      “Founded in 1988 and profitable throughout all of those 31 years, we have a solid track record of success. At Mid-Range, we use our expertise to assess your unique needs, in order to proactively develop the most effective IT solution for your requirements. Our full-service approach to technology and our diverse and in-depth industry expertise keep our clients coming back year after year.

      Serving clients across North America in a variety of industries, from small and emerging organizations to large, established enterprises – we’ve seen it all. Whether you need hardware or software solutions, disaster recovery and high availability, managed services or hosting or full ERP services with our JD Edwards offerings – we have the methods and expertise to help.”

      IBM i Services

      • ✔ IBM Power Hardware Sales
      • ✔ Co-Managed Services
      • ✔ DR/High Available Config
      • ✔ Full Managed Services
      • ✔ Co-Location Services
      • ✔ Public Cloud Services (AWS)

      URL
      midrange.ca

      Regional Coverage:
      Canada

      Logo for Mid-Range.

      Activity

      Understand your vendor options

      Activities:
      1. Create your vendor profiles
      2. Score vendor responses
      3. Develop and manage your vendor agenda

      This activity involves the following participants:

      • IT strategic direction decision makers
      • IT managers responsible for an existing iSeries or IBM i platform

      Outcomes of this step:

      • Vendor Profile Template
      • Completed IT Infrastructure Outsourcing Scoring Tool

      Info-Tech Insights

      This check-point process creates transparency around agreement costs with the business and gives the business an opportunity to re-evaluate its requirements for a potentially leaner agreement.

      1. Create your vendor profiles

      Define what you are looking for:

      • Create a vendor profile for every vendor of interest.
      • Leverage our starting list and template to track and record the advantages of each vendor.

      Mindshift

      First National Technology Solutions

      Key Information Systems

      MainLine

      Direct Systems Support

      T-Systems

      Horizon Computer Solutions Inc.

      Vendor Profile Template

      [Vendor Name]

      Summary of Vendor

      [Vendor Summary]
      *Detail the Vendor Services as a Summary*

      IBM i Services

      • ✔ IBM Power Hardware Sales
      • ✔ Co-Managed Services
      • ✔ DR/High Available Config
      • ✔ Full Managed Services
      • ✔ Co-Location Services
      • ✔ Public Cloud Services (AWS)
      *Itemize the Vendor Services specific to your requirements*

      URL
      https://www.url.com/
      *Insert the Vendor URL*

      Regional Coverage:
      [Country\Region]
      *Insert the Vendor Coverage & Locations*

      *Insert the Vendor Logo*

      2. Score your vendor responses

      Use the IT Infrastructure Outsourcing Scoring Tool to manage vendor responses.
      Use Info-Tech’s IT Infrastructure Outsourcing Scoring Tool to systematically score your vendor responses.

      The overall quality of the IBM i questions can help you understand what it might be like to work with the vendor.

      Consider the following questions:

      • Is the vendor clear about what it’s able to offer? Is its response transparent?
      • How much effort did the vendor put into answering the questions?
      • Does the vendor seem like someone you would want to work with?

      Once you have the vendor responses, you will select two or three vendors to continue assessing in more depth leading to an eventual final selection.

      Screenshot of the IT Infrastructure Outsourcing Scoring Tool's Scoring Sheet. There are three tables: 'Scoring Scale', 'Results', and one with 'RFP Questions'. Note on Results table says 'Top Scoring Vendors', and note on questions table says 'List your IBM i questions (requirements)'.

      Info-Tech Insights

      Watch out for misleading scores that result from poorly designed criteria weightings.

      3. Develop your vendor agenda

      Vendor Conference Call

      Develop an agenda for the conference call. Here is a sample agenda:
      • Review the vendor questions.
      • Go over answers to written vendor questions previously submitted.
      • Address new vendor questions.

      Commonly Debated Question:
      Should vendors be asked to remain anonymous on the call or should each vendor mention their organization when they join the call?

      Many organizations worry that if vendors can identify each other, they will price fix. However, price fixing is extremely rare due to its consequences and most vendors likely have a good idea which other vendors are participating in the bid. Another thought is that revealing vendors could either result in a higher level of competition or cause some vendors to give up:

      • A vendor that hears its rival is also bidding may increase the competitiveness of its bid and response.
      • A vendor that feels it doesn’t have a chance may put less effort into the process.
      • A vendor that feels it doesn’t have real competition may submit a less competitive or detailed response than it otherwise would have.

      Vendor Workshop

      A vendor workshop day is an interactive way to provide context to your vendors and to better understand the vendors’ offerings. The virtual or in-person interaction also offers a great way to understand what it’s like to work with each vendor and decide whether you could build a partnership with them in the long run.

      The main focus of the workshop is the vendors’ service solution presentation. Here is a sample agenda for a two-day workshop:

      Day 1
      • Meet and greet
      • Welcome presentation with objectives, acquisition strategy, and company overview
      • Overview of the current IT environment, technologies, and company expectations
      • Question and answer session
      • Site walk
      Day 2
      • Review Day 1 activities
      • Vendor presentations and solution framing
      Use the IT Infrastructure Outsourcing Scoring Tool to manage vendor responses.

      Related Info-Tech Research

      Effectively Acquire Infrastructure Services
      Acquiring a service is like buying an experience. Don’t confuse the simplicity of buying hardware with buying an experience.

      Outsource IT Infrastructure to Improve System Availability, Reliability, and Recovery
      There are very few IT infrastructure components you should be housing internally – outsource everything else.

      Build Your Infrastructure Roadmap
      Move beyond alignment: Put yourself in the driver’s seat for true business value.

      Define Your Cloud Vision
      Make the most of cloud for your organization.

      Document Your Cloud Strategy
      Drive consensus by outlining how your organization will use the cloud.

      Create a Right-Sized Disaster Recovery Plan
      Close the gap between your DR capabilities and service continuity requirements.

      Create a Better RFP Process
      Improve your RFPs to gain leverage and get better results.

      Research Authors

      Photo of Darin Stahl, Principal Research Advisor, Info-Tech Research Group.Darin Stahl, Principal Research Advisor, Info-Tech Research Group

      Principal Research Advisor within the Infrastructure Practice and leveraging 38+ years of experience, his areas of focus include: IT Operations Management, Service Desk, Infrastructure Outsourcing, Managed Services, Cloud Infrastructure, DRP/BCP, Printer Management, Managed Print Services, Application Performance Monitoring (APM), Managed FTP, and non-commodity servers (zSeries, mainframe, IBM i, AIX, Power PC).

      Photo of Troy Cheeseman, Practice Lead, Info-Tech Research Group.Troy Cheeseman, Practice Lead, Info-Tech Research Group

      Troy has over 24 years of experience and has championed large, enterprise-wide technology transformation programs, remote/home office collaboration and remote work strategies, BCP, IT DRP, IT Operations and expense management programs, international right placement initiatives, and large technology transformation initiatives (M&A). Additionally, he has deep experience working with IT solution providers and technology (cloud) start-ups.

      Research Contributors

      Photo of Dan Duffy, President & Owner, Mid-Range.Dan Duffy, President & Owner, Mid-Range

      Dan Duffy is the President and Founder of Mid-Range Computer Group Inc., an IBM Platinum Business Partner. Dan and his team have been providing the Canadian and American IBM Power market with IBM infrastructure solutions including private cloud, hosting and disaster recovery, high availability and data center services since 1988. He has served on numerous boards and associations including the Toronto Users Group for Mid-Range Systems (TUG), the IBM Business Partners of the Americas Advisory Council, the Cornell Club of Toronto, and the Notre Dame Club of Toronto. Dan holds a Bachelor of Science from Cornell University.

      Photo of George Goodall, Executive Advisor, Info-Tech Research Group.George Goodall, Executive Advisor, Info-Tech Research Group

      George Goodall is an Executive Advisor in the Research Executive Services practice at Info-Tech Research Group. George has over 20 years of experience in IT consulting, enterprise software sales, project management, and workshop delivery. His primary focus is the unique challenges and opportunities in organizations with small and constrained IT operations. In his long tenure at Info-Tech, George has covered diverse topics including voice communications, storage, and strategy and governance.

      Bibliography

      “Companies using IBM i (formerly known as i5/OS).” Enlyft, 21 July 2021. Web.

      Connor, Clare. “IBM i and Meeting the Challenges of Modernization.” Ensono, 22 Mar. 2022. Web.

      Huntington, Tom. “60+ IBM i User Groups and Communities to Join?” HelpSystems, 16 Dec. 2021. Web.

      Perkins, Dale. “The Road to Power Cloud: June 21st 1988 to now. The Journey Continues.” Mid-Range, 1 Nov. 2021. Web.

      Prickett Morgan, Timothy. “How IBM STACKS UP POWER8 AGAINST XEON SERVERS.” The Next Platform, 13 Oct. 2015. Web.

      “Why is AS/400 still used? Four reasons to stick with a classic.” NTT, 21 July 2016. Web.

      Appendix

      Public Cloud Provider Notes

      Appendix –
      Cloud
      Providers


      “IBM Power (IBM i and AIX) workloads are also available in the so-called ‘cloud.’” (Darin Stahl)

      AWS

      Appendix –
      Cloud
      Providers



      “IBM Power (IBM i and AIX) workloads are also available in the so-called ‘cloud.’” (Darin Stahl)

      Google

      • Google Cloud console supports IBM Power Systems.
      • This offering provides cloud instances running on IBM Power Systems servers with PowerVM.
      • The service uses a per-day prorated monthly subscription model for cloud instance plans with different capacities of compute, memory, storage, and network. Standard plans are listed below and custom plans are possible.
      • There is no IBM i offering yet that we are aware of.
      • For AIX on Power, this would appear to be a better option than AWS (Converge Enterprise Cloud with IBM Power for Google Cloud).

      Appendix –
      Cloud
      Providers



      “IBM Power (IBM i and AIX) workloads are also available in the so-called ‘cloud.’” (Darin Stahl)

      Azure

      • Azure has partners using the Azure Dedicated Host offerings to deliver “native support for IBM POWER Systems to Azure data centres” (PowerWire).
      • Microsoft has installed Power servers in an couple Azure data centers and Skytap manages the IBM i, AIX, and Linux environments for clients.
      • As far as I am aware there is no ability to install IBM i or AIX within an Azure Dedicated Host via the retail interfaces – these must be worked through a partner like Skytap.
      • The cloud route for IBM i or AIX might be the easiest working with Skytap and Azure. This would appear to be a better option than AWS in my opinion.

      Appendix –
      Cloud
      Providers



      “IBM Power (IBM i and AIX) workloads are also available in the so-called ‘cloud.’” (Darin Stahl)

      IBM

      Select and Use SDLC Metrics Effectively

      • Buy Link or Shortcode: {j2store}150|cart{/j2store}
      • member rating overall impact: 9.4/10 Overall Impact
      • member rating average dollars saved: $2,991 Average $ Saved
      • member rating average days saved: 32 Average Days Saved
      • Parent Category Name: Development
      • Parent Category Link: /development
      • Your organization wants to implement (or revamp existing) software delivery metrics to monitor performance as well as achieve its goals.
      • You know that metrics can be a powerful tool for managing team behavior.
      • You also know that all metrics are prone to misuse and mismanagement, which can lead to unintended consequences that will harm your organization.
      • You need an approach for selecting and using effective software development lifecycle (SDLC) metrics that will help your organization to achieve its goals while minimizing the risk of unintended consequences.

      Our Advice

      Critical Insight

      • Metrics are powerful, dangerous, and often mismanaged, particularly when they are tied to reward or punishment. To use SDLC metrics effectively, know the dangers, understand good practices, and then follow Info-Tech‘s TAG (team-oriented, adaptive, and goal-focused) approach to minimize risk and maximize impact.

      Impact and Result

      • Begin by understanding the risks of metrics.
      • Then understand good practices associated with metrics use.
      • Lastly, follow Info-Tech’s TAG approach to select and use SDLC metrics effectively.

      Select and Use SDLC Metrics Effectively Research & Tools

      Start here – read the Executive Brief

      Understand both the dangers and good practices related to metrics, along with Info-Tech’s TAG approach to the selection and use of SDLC metrics.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Understand the dangers of metrics

      Explore the significant risks associated with metrics selection so that you can avoid them.

      • Select and Use SDLC Metrics Effectively – Phase 1: Understand the Risks of Metrics

      2. Know good practices related to metrics

      Learn about good practices related to metrics and how to apply them in your organization, then identify your team’s business-aligned goals to be used in SDLC metric selection.

      • Select and Use SDLC Metrics Effectively – Phase 2: Know Good Practices Related to Metrics
      • SDLC Metrics Evaluation and Selection Tool

      3. Rank and select effective SDLC metrics for your team

      Follow Info-Tech’s TAG approach to selecting effective SDLC metrics for your team, create a communication deck to inform your organization about your selected SDLC metrics, and plan to review and revise these metrics over time.

      • Select and Use SDLC Metrics Effectively – Phase 3: Rank and Select Effective SDLC Metrics for Your Team
      • SDLC Metrics Rollout and Communication Deck
      [infographic]

      Workshop: Select and Use SDLC Metrics Effectively

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Understand the Dangers of Metrics

      The Purpose

      Learn that metrics are often misused and mismanaged.

      Understand the four risk areas associated with metrics: Productivity loss Gaming behavior Ambivalence Unintended consequences

      Productivity loss

      Gaming behavior

      Ambivalence

      Unintended consequences

      Key Benefits Achieved

      An appreciation of the dangers associated with metrics.

      An understanding of the need to select and manage SDLC metrics carefully to avoid the associated risks.

      Development of critical thinking skills related to metric selection and use.

      Activities

      1.1 Examine the dangers associated with metric use.

      1.2 Share real-life examples of poor metrics and their impact.

      1.3 Practice identifying and mitigating metrics-related risk.

      Outputs

      Establish understanding and appreciation of metrics-related risks.

      Solidify understanding of metrics-related risks and their impact on an organization.

      Develop the skills needed to critically analyze a potential metric and reduce associated risk.

      2 Understand Good Practices Related to Metrics

      The Purpose

      Develop an understanding of good practices related to metric selection and use.

      Introduce Info-Tech’s TAG approach to metric selection and use.

      Identify your team’s business-aligned goals for SDLC metrics.

      Key Benefits Achieved

      Understanding of good practices for metric selection and use.

      Document your team’s prioritized business-aligned goals.

      Activities

      2.1 Examine good practices and introduce Info-Tech’s TAG approach.

      2.2 Identify and prioritize your team’s business-aligned goals.

      Outputs

      Understanding of Info-Tech’s TAG approach.

      Prioritized team goals (aligned to the business) that will inform your SDLC metric selection.

      3 Rank and Select Your SDLC Metrics

      The Purpose

      Apply Info-Tech’s TAG approach to rank and select your team’s SDLC metrics.

      Key Benefits Achieved

      Identification of potential SDLC metrics for use by your team.

      Collaborative scoring/ranking of potential SDLC metrics based on their specific pros and cons.

      Finalize list of SDLC metrics that will support goals and minimize risk while maximizing impact.

      Activities

      3.1 Select your list of potential SDLC metrics.

      3.2 Score each potential metric’s pros and cons against objectives using a five-point scale.

      3.3 Collaboratively select your team’s first set of SDLC metrics.

      Outputs

      A list of potential SDLC metrics to be scored.

      A ranked list of potential SDLC metrics.

      Your team’s first set of goal-aligned SDLC metrics.

      4 Create a Communication and Rollout Plan

      The Purpose

      Develop a rollout plan for your SDLC metrics.

      Develop a communication plan.

      Key Benefits Achieved

      SDLC metrics.

      A plan to review and adjust your SDLC metrics periodically in the future.

      Communication material to be shared with the organization.

      Activities

      4.1 Identify rollout dates and responsible individuals for each SDLC metric.

      4.2 Identify your next SDLC metric review cycle.

      4.3 Create a communication deck.

      Outputs

      SDLC metrics rollout plan

      SDLC metrics review plan

      SDLC metrics communication deck

      Get Started With Customer Advocacy

      • Buy Link or Shortcode: {j2store}565|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Marketing Solutions
      • Parent Category Link: /marketing-solutions

      Getting started with customer advocacy (CA) is no easy task. Many customer success professionals carry out ad hoc customer advocacy activities to address immediate needs but lack a more strategic approach.

      Our Advice

      Critical Insight

      • Customer success leaders must reposition their CA program around growth; the recognition that customer advocacy is a strategic growth initiative is necessary to succeed in today’s competitive market.
      • Get key stakeholders on board early – especially Sales!
      • Always link your CA efforts back to retention and growth.
      • Make building genuine relationships with your advocates the cornerstone of your CA program.

      Impact and Result

      • Enable the organization to identify and develop meaningful relationships with top customers and advocates.
      • Understand the concepts and benefits of CA and how CA can be used to improve marketing and sales and fuel growth and competitiveness.
      • Follow SoftwareReviews’ methodology to identify where to start to apply CA within the organization.
      • Develop a customer advocacy proof of concept/pilot program to gain stakeholder approval and funding to get started with or expand efforts around customer advocacy.

      Get Started With Customer Advocacy Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Get Started With Customer Advocacy Executive Brief – An overview of why customer advocacy is critical to your organization and the recommended approach for getting started with a pilot program.

      Understand the strategic benefits and process for building a formal customer advocacy program. To be successful, you must reposition CA as a strategic growth initiative and continually link any CA efforts back to growth.

      • Get Started With Customer Advocacy Storyboard

      2. Define Your Advocacy Requirements – Assess your current customer advocacy efforts, identify gaps, and define your program requirements.

      With the assessment tool and steps outlined in the storyboard, you will be able to understand the gaps and pain points, where and how to improve your efforts, and how to establish program requirements.

      • Customer Advocacy Maturity Assessment Tool

      3. Win Executive Approval and Launch Pilot – Develop goals, success metrics, and timelines, and gain approval for your customer advocacy pilot.

      Align on pilot goals, key milestones, and program elements using the template and storyboard to effectively communicate with stakeholders and gain executive buy-in for your customer advocacy pilot.

      • Get Started With Customer Advocacy Executive Presentation Template

      Infographic

      Further reading

      Get Started With Customer Advocacy

      Develop a customer advocacy program to transform customer satisfaction into revenue growth.

      EXECUTIVE BRIEF

      Analyst perspective

      Customer advocacy is critical to driving revenue growth

      The image contains a picture of Emily Wright.

      Customer advocacy puts the customer at the center of everything your organization does. By cultivating a deep understanding of customer needs and how they define value and by delivering positive experiences throughout the customer journey, organizations inspire and empower customers to become evangelists for their brands or products. Both the client and solution provider enjoy satisfying and ongoing business outcomes as a result.

      Focusing on customer advocacy is critical for software solutions providers. Business-to-business (B2B) buyers are increasingly looking to their peers and third-party resources to arm themselves with information on solutions they feel they can trust before they choose to engage with solution providers. Your satisfied customers are now your most trusted and powerful resource.

      Customer advocacy helps build strong relationships with your customers, nurtures brand advocacy, gives your marketing messaging credibility, and differentiates your company from the competition; it’s critical to driving revenue growth. Companies that develop mature advocacy programs can increase Customer Lifetime Value (CLV) by 16% (Wharton Business School, 2009), increase customer retention by 35% (Deloitte, 2011), and give themselves a strong competitive advantage in an increasingly competitive marketplace.

      Emily Wright
      Senior Research Analyst, Advisory
      SoftwareReviews

      Executive summary

      Your Challenge

      Ad hoc customer advocacy (CA) efforts and reference programs, while still useful, are not enough to drive growth. Providers increase their chance for success by assessing if they face the following challenges:

      • Lack of referenceable customers that can turn into passionate advocates, or a limited pool that is at risk of burnout.
      • Lack of references for all key customer types, verticals, etc., especially in new growth segments or those that are hard to recruit.
      • Lack of a consistent program for gathering customer feedback and input to make improvements and increase customer satisfaction.
      • Lack of executive and stakeholder (e.g. Sales, Customer Success, channel partners, etc.) buy-in for the importance and value of customer advocacy.

      Building a strong customer advocacy program must be a high priority for customer service/success leaders in today’s highly competitive software markets.

      Common Obstacles

      Getting started with customer advocacy is no easy task. Many customer success professionals carry out ad hoc customer advocacy activities to address immediate needs but lack a more strategic approach. What separates them from success are several nagging obstacles:

      • Efforts lack funding and buy-in from stakeholders.
      • Senior management doesn’t fully understand the business value of a customer advocacy program.
      • Duplicate efforts are taking place between Sales, Marketing, product teams, etc., because ownership, roles, and responsibilities have not been determined.
      • Relationships are guarded/hoarded by those who feel they own the relationship (e.g. Sales, Customer Success, channel partners, etc.).
      • Customer-facing staff often lack the necessary skills to foster customer advocacy.

      SoftwareReviews’ Approach

      This blueprint will help leaders of customer advocacy programs get started with developing a formalized pilot program that will demonstrate the value of customer advocacy and lay a strong foundation to justify rollout. Through SoftwareReviews’ approach, customer advocacy leaders will:

      • Enable the organization to identify and develop meaningful relationships with top customers and advocates.
      • Understand the concepts and benefits of CA and how CA can be used to improve marketing and sales and fuel growth and competitiveness.
      • Follow SoftwareReviews’ methodology to identify where to start to apply CA within the organization.
      • Develop a customer advocacy proof of concept/pilot program to gain stakeholder approval and funding to get started with or expand efforts around customer advocacy.

      What is customer advocacy?

      “Customer advocacy is the act of putting customer needs first and working to deliver solution-based assistance through your products and services." – Testimonial Hero, 2021

      Customer advocacy is designed to keep customers loyal through customer engagement and advocacy marketing campaigns. Successful customer advocacy leaders experience decreased churn while increasing return on investment (ROI) through retention, acquisition, and cost savings.

      Businesses that implement customer advocacy throughout their organizations find new ways of supporting customers, provide additional customer value, and ensure their brands stand unique among the competition.

      Customer Advocacy Is…

      • An integral part of any marketing and/or business strategy.
      • Essential to improving and maintaining high levels of customer satisfaction.
      • Focused on delivering value to customers.
      • Not only a set of actions, but a mindset that should be fostered and reinforced through a customer-centric culture.
      • Mutually beneficial relationships for both company and customer.

      Customer Advocacy Is Not…

      • Only referrals and testimonials.
      • Solely about what you can get from your advocates.
      • Brand advocacy. Brand advocacy is the desired outcome of customer advocacy.
      • Transactional. Brand advocates must be engaged.
      • A nice-to-have.
      • Solved entirely by software. Think about what you want to achieve and how a software solution can you help you reach those goals.

      SoftwareReviews Insight

      Customer advocacy has evolved into being a valued company asset versus a simple referral program – success requires an organization-wide customer-first mindset and the recognition that customer advocacy is a strategic growth initiative necessary to succeed in today’s competitive market.

      Customer advocacy: Essential to high retention

      When customers advocate for your company and products, they are eager to retain the value they receive

      • Customer acts of advocacy correlate to high retention.
      • Acts of advocacy won’t happen unless customers feel their interests are placed ahead of your company’s, thereby increasing satisfaction and customer success. That’s the definition of a customer-centric culture.
      • And yet your company does receive significant benefits from customer advocacy:
        • When customers advocate and renew, your costs go down and margins rise because it costs less to keep a happy customer than it does to bring a new customer onboard.
        • When renewal rates are high, customer lifetime value increases, also increasing profitability.

      Acquiring a new customer can cost five times more than retaining an existing customer (Huify, 2018).

      Increasing customer retention by 5% can increase profits by 25% to 95% (Bain & Company, cited in Harvard Business Review, 2014).

      SoftwareReviews Insight

      Don’t overlook the value of customer advocacy to retention! Despite the common knowledge that it’s far easier and cheaper to sell to an existing customer than to sell to a new prospect, most companies fail to leverage their customer advocacy programs and continue to put pressure on Marketing to focus their budgets on customer acquisition.

      Customer advocacy can also be your ultimate growth strategy

      In your marketing and sales messaging, acts of advocacy serve as excellent proof points for value delivered.

      Forty-five percent of businesses rank online reviews as a top source of information for selecting software during this (top of funnel) stage, followed closely by recommendations and referrals at 42%. These sources are topped only by company websites at 54% (Clutch, 2020).

      With referrals coming from customer advocates to prospects via your lead gen engine and through seller talk tracks, customer advocacy is central to sales, marketing, and customer experience success.

      ✓ Advocates can help your new customers learn your solution and ensure higher adoption and satisfaction.
      ✓ Advocates can provide valuable, honest feedback on new updates and features.

      The image contains a picture to demonstrate the cycle of customer advocacy. The image has four circles, with one big circle in the middle and three circles surrounding with arrows pointing in both directions in between them. The middle circle is labelled customer advocacy. The three circles are labelled: sales, customer success, marketing.

      “A customer advocacy program is not just a fancy buzz word or a marketing tool that’s nice to have. It’s a core discipline that every major brand needs to integrate into their overall marketing, sales and customer success strategies if they expect to survive in this trust economy. Customer advocacy arguably is the common asset that runs throughout all marketing, sales and customer success activities regardless of the stage of the buyer’s journey and ties it all together.” – RO Innovation, 2017

      Positive experience drives acts of advocacy

      More than price or product, experience now leads the way in customer advocacy and retention

      Advocacy happens when customers recommend your product. Our research shows that the biggest drivers of likeliness to recommend and acts of customer advocacy are the positive experiences customers have with vendors and their products, not product features or cost savings. Customers want to feel that:

      1. Their productivity and performance is enhanced and the vendor is helping them to innovate and grow as a company.
      2. Their vendor inspires them and helps them to continually improve.
      3. They can rely on the vendor and the product they purchased.
      4. They are respected by the vendor.
      5. They can trust that the vendor will be on their side and save them time.

      The image contains a graph to demonstrate the correlation of likeliness to recommend a satisfaction driver. Where anything above a 0.5 indicates a strong driver of satisfaction.

      Note that anything above 0.5 indicates a strong driver of satisfaction.
      Source: SoftwareReviews buyer reviews (based on 82,560 unique reviews).

      SoftwareReviews Insight

      True customer satisfaction comes from helping customers innovate, enhancing their performance, inspiring them to continually improve, and being reliable, respectful, trustworthy, and conscious of their time. These true drivers of satisfaction should be considered in your customer advocacy and retention efforts. The experience customers have with your product and brand is what will differentiate your brand from competitors, drive advocacy, and ultimately, power business growth. Talk to a SoftwareReviews advisor to learn how users rate your product on these satisfaction drivers in the SoftwareReviews Emotional Footprint Report.

      Yet challenges exist for customer advocacy program leaders

      Customer success leaders without a strong customer advocacy program feel numerous avoidable pains:

      • Lack of compelling stories and proof points for the sales team, causing long sales cycles.
      • Heavy reliance on a small pool of worn-out references.
      • Lack of references for all needed customer types, verticals, etc.
      • Lack of a reliable customer feedback process for solution improvements.
      • Overspending on acquiring new customers due to a lack of customer proof points.
      • Missed opportunities that could grow the business (customer lifetime value, upsell/cross-sell, etc.).

      Marketing, customer success, and sales teams experiencing any one of the above challenges must consider getting started with a more formalized customer advocacy program.

      Obstacles to customer advocacy programs

      Leaders must overcome several barriers in developing a customer advocacy program:

      • Stakeholders are often unclear on the value customer advocacy programs can bring and require proof of benefits to invest.
      • Efforts are duplicated among sales, marketing, product, and customer success teams, given ownership and collaboration practices are ill-defined or nonexistent.
      • There is a culture of guarding or hoarding customer relationships by those who feel they own the relationship, or there’s high turnover among employees who own the customer relationships.
      • The governance, technology, people, skills, and/or processes to take customer advocacy to the next level are lacking.
      • Leaders don’t know where to start with customer advocacy, what needs to be improved, or what to focus on first.

      A lack of customer centricity hurts organizations

      12% of people believe when a company says they put customers first. (Source: HubSpot, 2019)

      Brands struggle to follow through on brand promises, and a mismatch between expectations and lived experience emerges. Customer advocacy can help close this gap and help companies live up to their customer-first messaging.

      42% of companies don’t conduct any customer surveys or collect feedback. (Source: HubSpot, 2019)

      Too many companies are not truly listening to their customers. Companies that don’t collect feedback aren’t going to know what to change to improve customer satisfaction. Customer advocacy will orient companies around their customer and create a reliable feedback loop that informs product and service enhancements.

      Customer advocacy is no longer a nice-to-have but a necessity for solution providers

      B2B buyers increasingly turn to peers to learn about solutions:

      “84% of B2B decision makers start the buying process with a referral.” (Source: Influitive, Gainsight & Pendo, 2020)

      “46% of B2B buyers rely on customer references for information before purchasing.” (Source: RO Innovation, 2017)

      “91% of B2B purchasers’ buying decisions are influenced by word-of-mouth recommendations.” (Source: ReferralRock, 2022)

      “76% of individuals admit that they’re more likely to trust content shared by ‘normal’ people than content shared by brands.” (Source: TrustPilot, 2020)

      By ignoring the importance of customer advocacy, companies and brands are risking stagnation and missing out on opportunities to gain competitive advantage and achieve growth.

      Getting Started With Customer Advocacy: SoftwareReviews' Approach

      1 BUILD
      Build the business case
      Identify your key stakeholders, steering committee, and working team, understand key customer advocacy principles, and note success barriers and ways to overcome them as your first steps.

      2 DEVELOP
      Develop your advocacy requirements
      Assess your current customer advocacy maturity, identify gaps in your current efforts, and develop your ideal advocate profile.

      3 WIN
      Win executive approval and implement pilot
      Determine goals and success metrics for the pilot, establish a timeline and key project milestones, create advocate communication materials, and finally gain executive buy-in and implement the pilot.

      SoftwareReviews Insight
      Building and implementing a customer advocacy pilot will help lay the foundation for a full program and demonstrate to executives and key stakeholders the impact on revenue, retention, and CLV that can be achieved through coordinated and well-planned customer advocacy efforts.

      Customer advocacy benefits

      Our research benefits customer advocacy program managers by enabling them to:

      • Explain why having a centralized, proactive customer advocacy program is important.
      • Clearly communicate the benefits and business case for having a formalized customer advocacy program.
      • Develop a customer advocacy pilot to provide a proof of concept (POC) and demonstrate the value of customer advocacy.
      • Assess the maturity of your current customer advocacy efforts and identify what to improve and how to improve to grow your customer advocacy function.

      "Advocacy is the currency for business and the fuel for explosive growth. Successful marketing executives who understand this make advocacy programs an essential part of their go-to-market strategy. They also know that advocacy isn't something you simply 'turn on': ... ultimately, it's about making human connections and building relationships that have enduring value for everyone involved."
      - Dan Cote, Influitive, Dec. 2021

      Case Study: Advocate impact on sales at Genesys

      Genesys' Goal

      Provide sales team with compelling customer reviews, quotes, stories, videos, and references.

      Approach to Advocacy

      • Customers were able to share their stories through Genesys' customer hub GCAP as quotes, reviews, etc., and could sign up to host reference forum sessions for prospective customers.
      • Content was developed that demonstrated ROI with using Genesys' solutions, including "top-tier logos, inspiring quotes, and reference forums featuring some of their top advocates" (Influitive, 2021).
      • Leveraged customer advocacy-specific software solution integration with the CRM to easily identify reference recommendations for Sales.

      Advocate Impact on Sales

      According to Influitive (2021), the impacts were:

      • 386% increase in revenue influences from references calls
      • 82% of revenue has been influence by reference calls
      • 78 reference calls resulted in closed-won opportunities
      • 250 customers and prospects attended 7 reference forums
      • 112 reference slides created for sales enablement
      • 100+ quotes were collect and transformed into 78 quote slides

      Who benefits from getting started with customer advocacy?

      This Research Is Designed for:

      • Customer advocacy leaders and marketers who are looking to:
        • Take a more strategic, proactive, and structured approach to customer advocacy.
        • Find a more effective and reliable way to gather customer feedback and input on products and services.
        • Develop and nurture a customer-oriented mindset throughout the organization.
        • Improve marketing credibility both within the company and outside to prospective customers.

      This Research Will Help You:

      • Explain why having a centralized, proactive customer advocacy program is important.
      • Clearly communicate the benefits and business case for having a formalized customer advocacy program.
      • Develop a customer advocacy pilot to provide a proof of concept (POC) and demonstrate the value of customer advocacy.
      • Assess the maturity of your current customer advocacy efforts and identify what to improve and how to improve to grow your customer advocacy function.

      This Research Will Also Assist:

      • Customer success leaders and sales directors who are responsible for:
        • Gathering customer references and testimonials.
        • Referral or voice of the customer (VoC) programs.

      This Research Will Help Them:

      • Align stakeholders on an overall program of identifying ideal advocates.
      • Coordinate customer advocacy efforts and actions.
      • Gather and make use of customer feedback to improve products, solutions, and service provided.
      • Provide an amazing customer experience throughout the entirety of the customer journey.

      SoftwareReviews’ methodology for getting started with customer advocacy

      Phase Steps

      1. Build the business case

      1. Identify your key stakeholders, steering committee, and working team
      2. Understand the concepts and benefits of customer advocacy as they apply to your organization
      3. Outline barriers to success, risks, and risk mitigation tactics

      2. Develop your advocacy requirements

      1. Assess your customer advocacy maturity using the SoftwareReviews CA Maturity Assessment Tool
      2. Identify gaps/pains in current CA efforts and add tasks to your action plan
      3. Develop ideal advocate profile/identify target advocate segment(s)

      3. Create implementation plan and pitch CA pilot

      1. Determine pilot goals and success metrics
      2. Establish timeline and create advocate communication materials
      3. Gain executive buy-in and implement pilot

      Phase Outcomes

      1. Common understanding of CA concepts and benefits
      2. Buy-in from CEO and head of Sales
      3. List of opportunities, risks, and risk mitigation tactics
      1. Identification of gaps in current customer advocacy efforts and/or activities
      2. Understanding customer advocacy readiness
      3. Identification of ideal advocate profile/target segment
      4. Basic actions to bridge gaps in CA efforts
      1. Clear objective for CA pilot
      2. Key metrics for program success
      3. Pilot timelines and milestones
      4. Executive presentation with business case for CA

      Insight summary

      Customer advocacy is a critical strategic growth initiative
      Customer advocacy (CA) has evolved into being a highly valued company asset as opposed to a simple referral program, but not everyone in the organization sees it that way. Customer success leaders must reposition their CA program around growth instead of focusing solely on retention and communicate this to key stakeholders. The recognition that customer advocacy is a strategic growth initiative is necessary to succeed in today’s competitive market.

      Get key stakeholders on board early – especially Sales!
      Work to bring the CEO and the head of Sales on your side early. Sales is the gatekeeper – they need to open the door to customers to turn them into advocates. Clearly reposition CA for growth and communicate that to the CEO and head of Sales; wider buy-in will follow.

      Identify the highest priority segment for generating acts of advocacy
      By focusing on the highest priority segment, you accomplish a number of things: generating growth in a critical customer segment, proving the value of customer advocacy to key stakeholders (especially Sales), and setting a strong foundation for customer advocacy to build upon and expand the program out to other segments.

      Always link your CA efforts back to retention and growth
      By clearly demonstrating the impact that customer advocacy has on not only retention but also overall growth, marketers will gain buy-in from key stakeholders, secure funding for a full CA program, and gain the resources needed to expand customer advocacy efforts.

      Focus on providing value to advocates
      Many organizations take a transactional approach to customer advocacy, focusing on what their advocates can do for them. To truly succeed with CA, focus on providing your advocates with value first and put them in the spotlight.

      Make building genuine relationships with your advocates the cornerstone of your CA program
      "57% of small businesses say that having a relationship with their consumers is the primary driver of repeat business" (Factory360).

      Guided Implementation

      What does our GI on getting started with building customer advocacy look like?

      Build the Business Case

      Call #1: Identify key stakeholders. Map out motivations and anticipate any concerns or objections. Determine steering committee and working team. Plan next call – 1 week.

      Call #2: Discuss concepts and benefits of customer advocacy as they apply to organizational goals. Plan next call – 1 week.

      Call #3: Discuss barriers to success, risks, and risk mitigation tactics. Plan next call – 1 week.

      Call #4: Finalize CA goals, opportunities, and risks and develop business case. Plan next call – 2 weeks.

      Develop Your Advocacy Requirements

      Call #5: Review the SoftwareReviews CA Maturity Assessment Tool. Assess your current level of customer advocacy maturity. Plan next call – 1 week.

      Call #6: Review gaps and pains in current CA efforts. Discuss tactics and possible CA pilot program goals. Begin adding tasks to action plan. Plan next call – 2 weeks.

      Call #7: Discuss ideal advocate profile and target segments. Plan next call – 2 weeks.

      Call #8: Validate and finalize ideal advocate profile. Plan next call – 1 week.

      Win Executive Approval and Implement Pilot

      Call #9: Discuss CA pilot scope. Discuss performance metrics and KPIs. Plan next call – 3 days.

      Call #10: Determine timeline and key milestones. Plan next call –2 weeks.

      Call #11: Develop advocate communication materials. Plan next call – 3 days.

      Call #12: Review final business case and coach on executive presentation. Plan next call – 1 week.

      A Guided Implementation (GI) is series of calls with a SoftwareReviews Advisory analyst to help implement our best practices in your organization. For guidance on marketing applications, we can arrange a discussion with an Info-Tech analyst. Your engagement managers will work with you to schedule analyst calls.


      Customer Advocacy Workshop

      Pre-Workshop Day 1 Day 2 Day 3 Day 4 Day 5 Post-Workshop
      Activities Identify Stakeholders & CA Pilot Team Build the Business Case Assess Current CA Efforts Develop Advocacy Goals & Ideal Advocate Profile Develop Project Timelines, Materials, and Exec Presentation Next Steps and Wrap-Up (offsite) Pitch CA Pilot
      0.1 Identify key stakeholders to involve in customer advocacy pilot and workshop; understand their motivations and anticipate possible concerns. 1.1 Review key CA concepts and identify benefits of CA for the organization.
      1.2 Outline barriers to success, risks, and risk mitigation tactics.
      2.1 Assess your customer advocacy maturity using the SoftwareReviews CA Maturity Assessment Tool.
      2.2 Identify gaps/pains in current CA efforts.
      2.3 Prioritize gaps from diagnostic and any other critical pain points.
      3.1 Identify and document the ideal advocate profile and target customer segment for pilot.
      3.2 Determine goal(s) and success metrics for program pilot.
      4.1 Develop pilot timelines and key milestones.
      4.2 Outline materials needed and possible messaging.
      4.3 Build the executive buy-in presentation.
      5.1 Complete in-progress deliverables from the previous four days. 6.1 Present to executive team and stakeholders.
      6.2 Gain executive buy-in and key stakeholder approval.
      6.3 Execute CA pilot.
      Deliverables
      1. Rationale for CA pilot; clear benefits, and how they apply to the organization.
      2. Documented barriers to success, risks, and risk mitigation tactics.
      1. CA Maturity Assessment results.
      2. Identification of gaps in current customer advocacy efforts and/or activities.
      1. Documented ideal advocate profile/target customer segment.
      2. Clear goal(s) and success metrics for CA pilot.
      1. Documented pilot timelines and key milestones.
      2. Draft/outlines of advocate materials.
      3. Draft executive presentation with business case for CA.
      1. Finalized implementation plan for CA pilot.
      2. Finalized executive presentation with business case for CA.
      1. Buy-in from decision makers and key stakeholders.

      Contact your account representative for more information.
      workshops@infotech.com
      1-888-670-8889

      Get started!

      Know your target market and audience, deploy well-designed strategies based on shared values, and make meaningful connections with people.

      Phase 1
      Build the Business Case

      Phase 2
      Develop Your Advocacy Requirements

      Phase 3
      Win Executive Approval and Implement Pilot

      Phase 1: Build the Business Case

      Steps
      1.1 Identify your key stakeholders, steering committee, and working team
      1.2 Understand the concepts and benefits of customer advocacy as they apply to your organization
      1.3 Outline barriers to success, risks, and risk mitigation tactics

      Phase Outcome

      • Common understanding of CA concepts and benefits
      • Buy-in from CEO and head of Sales
      • List of barriers to success, risks, and risk mitigation tactics

      Build the business case

      Step 1.1 Identify your key stakeholders, steering committee, and working team

      Total duration: 2.5-8.0 hours

      Objective
      Identify, document, and finalize your key stakeholders to know who to involve and how to get them onboard by truly understanding the forces of influence.

      Output

      • Robust stakeholder list with key stakeholders identified.
      • Steering committee and working team decided.

      Participants

      • Customer advocacy lead
      • Identified stakeholders
      • Workstream leads

      MarTech
      None

      Tools

      1.1.1 Identify Stakeholders
      (60-120 min.)

      Identify
      Using the guidance on slide 28, identify all stakeholders who would be involved or impacted by your customer advocacy pilot by entering names and titles into columns A and B on slide 27 "Stakeholder List Worksheet."

      Document
      Document as much information about each stakeholder as possible in columns C, D, E, and F into the table on slide 27.

      1.1.2 Select Steering Committee & Working Team
      (60-90 min.)

      Select
      Using the guidance on slides 28 and 29 and the information collected in the table on slide 27, identify the stakeholders that are steering committee members, functional workstream leads, or operations; document in column G on slide 27.

      Document
      Open the Executive Presentation Template to slides 5 and 6 and document your final steering committee and working team selections. Be sure to note the Executive Sponsor and Program Manager on slide 5.

      Tips & Reminders

      1. It is critical to identify "key stakeholders"; a single missed key stakeholder can disrupt an initiative. A good way to ensure that nobody is missed is to first uncover as many stakeholders as possible and later decide how important they are.
      2. Ensure steering committee representation from each department this initiative would impact or that may need to be involved in decision-making or problem-solving endeavors.

      Consult Info-Tech's Manage Stakeholder Relations blueprint for additional guidance on identifying and managing stakeholders, or contact one of our analysts for more personalized assistance and guidance.

      Stakeholder List Worksheet

      *Possible Roles
      Executive Sponsor
      Program Manager
      Workstream Lead
      Functional Lead
      Steering Committee
      Operations
      A B C D E F G
      Name Position Decision Involvement
      (Driver / Approver / Contributor / Informe
      Direct Benefit?
      (Yes / No)
      Motivation Concerns *Role in Customer Advocacy Pilot
      E.g. Jane Doe VP, Customer Success A N
      • Increase customer retention
      • Customer advocate burnout
      Workstream Lead

      Customer advocacy stakeholders

      What to consider when identifying stakeholders required for CA:
      Customer advocacy should be done as a part of a cross-functional company initiative. When identifying stakeholders, consider:

      • Who can make the ultimate decision on approving the CA program?
      • Who are the senior leadership members you need buy-in from?
      • Who do you need to support the CA program?
      • Who is affected by the CA program?
      • Who will help you build the CA program?
      • Where and among who is there enthusiasm for customer advocacy?
      • Consider stakeholders from Customer Success, Marketing, Sales, Product, PR & Social, etc.
      Key Roles Supporting an Effective Customer Advocacy Pilot
      Executive Sponsor
      • Owns the function at the management/C-suite level
      • Responsible for breaking down barriers and ensuring alignment with organizational strategy
      • CMO, VP of Marketing, and in SMB providers, the CEO
      Program Manager
      • Typically, a senior member of the marketing team
      • Responsible for organizing the customer advocacy pilot, preparing summary executive-level communications, and approval requests
      • Program manages the customer advocacy pilot, and in many cases, the continued formal program
      • Product Marketing Director, or other Marketing Director, who has strong program management skills, has run large-scale marketing or product programs, and is familiar with the stakeholder roles and enabling technologies
      Functional / Workstream Leads
      • Works alongside the Program Manager on planning and implementing the customer advocacy pilot and ensures functional workstreams are aligned with pilot objectives
      • Typical customer advocacy pilots will have a team comprised of representatives from Marketing, Sales, and Customer Success
      Steering Committee
      • Comprised of C-suite/management-level individuals that guide key decisions, approve requests, and mitigate any functional conflicts
      • Responsible for validating goals and priorities, enabling adequate resourcing, and critical decision making
      • CMO, CRO/Head of Sales, Head of Customer Success
      Operations
      • Comprised of individuals whose application and tech tools knowledge and skills support integration of customer advocacy functions into existing tech stack/CRM (e.g. adding custom fields into CRM)
      • Responsible for helping select technology that enables customer advocacy program activities
      • CRM, Marketing Applications, and Analytics Managers, IT Managers

      Customer advocacy working team

      Consider the skills and knowledge required for planning and executing a customer advocacy pilot.

      Workstream leads should have strong project management and collaboration skills and deep understanding of both product and customers (persona, journeys, satisfaction, etc.).

      Required Skills Suggested Functions
      • Project management
      • CRM knowledge
      • Marketing automation experience
      • MarTech knowledge
      • Understanding of buyer persona and journey
      • Product knowledge
      • Understanding of executive-level goals for the pilot
      • Content creation
      • Customer advocacy experience, if possible
      • Customer satisfaction
      • Email and event marketing experience
      • Customer Success
      • Marketing
      • Sales
      • Product
      • PR/Corporate Comms.

      Build the business case

      Step 1.2 Understand key concepts and benefits of customer advocacy

      Total duration: 2.0-4.0 hours

      Objective
      Understand customer advocacy and what benefits you seek from your customer advocacy program, and get set up to best communicate them to executives and decision makers.

      Output

      • Documented customer advocacy benefits

      Participants

      • Customer advocacy lead

      MarTech
      None

      Tools

      1.2.1 Discuss Key Concepts
      (60-120 min.)

      Envision
      Schedule a visioning session with key stakeholders and share the Get Started With Customer Advocacy Executive Brief (slides 3-23 in this deck).

      Discuss how key customer advocacy concepts can apply to your organization and how CA can contribute to organizational growth.

      Document
      Determine the top benefits sought from the customer advocacy program pilot and record them on slides 4 and 12 in the Executive Presentation Template.

      Finalize
      Work with the Executive Sponsor to finalize the "Message from the CMO" on slide 4 in the Executive Presentation Template.

      Tips & Reminders

      Keep in mind that while we're starting off broadly, the pilot for your customer advocacy program should be narrow and focused in scope.

      Build the business case

      Step 1.3 Understand barriers to success, risks, and risk mitigation tactics

      Total duration: 2.0-8.0 hours

      Objective
      Anticipate threats to pilot success; identify barriers to success, any possible risks, and what can be done to reduce the chances of a negative pilot outcome.

      Output

      • Awareness of barriers
      • Tactics to mitigate risk

      Participants

      • Customer advocacy lead
      • Key stakeholders

      MarTech
      None

      Tools

      1.3.1 Brainstorm Barriers to Success & Possible Risks
      (60-120 min.)

      Identify
      Using slide 7 of the Executive Presentation Template, brainstorm any barriers to success that may exist and risks to the customer advocacy program pilot success. Consider the people, processes, and technology that may be required.

      Document
      Document all information on slide 7 of the Executive Presentation Template.

      1.3.2 Develop Risk Mitigation Tactics
      (60-300 min.)

      Develop
      Brainstorm different ways to address any of the identified barriers to success and reduce any risks. Consider the people, processes, and technology that may be required.

      Document
      Document all risk mitigation tactics on slide 7 of the Executive Presentation Template.

      Tips & Reminders
      There are several types of risk to explore. Consider the following when brainstorming possible risks:

      • Damage to brand (if advocate guidance not provided)
      • Legal (compliance with regulations and laws around contact, incentives, etc.)
      • Advocate burnout
      • Negative advocate feedback

      Phase 2: Develop Your Advocacy Requirements

      Steps
      2.1 Assess your customer advocacy maturity
      2.2 Identify and document gaps and pain points
      2.3 Develop your ideal advocate profile

      Phase Outcome

      • Identification of gaps in current customer advocacy efforts or activities
      • Understanding of customer advocacy readiness and maturity
      • Identification of ideal advocate profile/target segment
      • Basic actions to bridge gaps in CA efforts

      Develop your advocacy requirements

      Step 2.1 Assess your customer advocacy maturity

      Total duration: 2.0-8.0 hours

      Objective
      Use the Customer Advocacy Maturity Assessment Tool to understand your organization's current level of customer advocacy maturity and what to prioritize in the program pilot.

      Output

      • Current level of customer advocacy maturity
      • Know areas to focus on in program pilot

      Participants

      • Customer advocacy lead
      • Key stakeholders

      MarTech
      None

      Tools

      2.1.1 Diagnose Current Customer Advocacy Maturity
      (60-120 min.)

      Diagnose
      Begin on tab 1 of the Customer Advocacy Maturity Assessment Tool and read all instructions.

      Navigate to tab 2. Considering the current state of customer advocacy efforts, answer the diagnostic questions in the Diagnostic tab of the Customer Advocacy Maturity Assessment Tool.

      After completing the questions, you will receive a diagnostic result on tab 3 that will identify areas of strength and weakness and make high-level recommendations for your customer advocacy program pilot.

      2.1.2 Discuss Results
      (60-300 min.)

      Discuss
      Schedule a call to discuss your customer advocacy maturity diagnostic results with a SoftwareReviews Advisor.

      Prioritize the recommendations from the diagnostic, noting which will be included in the program pilot and which require funding and resources to advance.

      Transfer
      Transfer results into slides 8 and 11 of the Executive Presentation Template.

      Tips & Reminders
      Complete the diagnostic with a handful of key stakeholders identified in the previous phase. This will help provide a more balanced and accurate assessment of your organization’s current level of customer advocacy maturity.

      Develop your advocacy requirements

      Step 2.2 Identify and document gaps and pain points

      Total duration: 2.5-8.0 hours

      Objective
      Understand the current pain points within key customer-related processes and within any current customer advocacy efforts taking place.

      Output

      • Prioritized list of pain points that could be addressed by a customer advocacy program.

      Participants

      • Customer advocacy lead
      • Key stakeholders

      MarTech
      None

      Tools

      2.2.1 Identify Pain Points
      (60-120 min.)

      Identify
      Identify and list current pain points being experienced around customer advocacy efforts and processes around sales, marketing, customer success, and product feedback.

      Add any gaps identified in the diagnostic to the list.

      Transfer
      Transfer key information into slide 9 of Executive Presentation Template.

      2.2.2 Prioritize Pain Points
      (60-300 min.)

      Prioritize
      Indicate which pains are the most important and that a customer advocacy program could help improve.

      Schedule a call to discuss the outputs of this step with a SoftwareReviews Advisor.

      Document
      Document priorities on slide 9 of Executive Presentation Template.

      Tips & Reminders

      Customer advocacy won't solve for everything; it's important to be clear about what pain points can and can't be addressed through a customer advocacy program.

      Develop your advocacy requirements

      Step 2.3 Develop your ideal advocate profile

      Total duration: 3.0-9.0 hours

      Objective
      Develop an ideal advocate persona profile that can be used to identify potential advocates, guide campaign messaging, and facilitate advocate engagement.

      Output

      • Ideal advocate persona profile

      Participants

      • Customer advocacy lead
      • Key stakeholders
      • Sales lead
      • Marketing lead
      • Customer Success lead
      • Product lead

      MarTech
      May require the use of:

      • CRM or marketing automation platform
      • Available and up-to-date customer database

      Tools

      2.3.1 Brainstorm Session Around Ideal Advocate Persona
      (60-150 min.)

      Brainstorm
      Lead the team to prioritize an initial, single, most important persona and to collaborate to complete the template.

      Choose your ideal advocate for the pilot based on your most important audience. Start with firmographics like company size, industry, and geography.

      Next, consider satisfaction levels and behavioral attributes, such as renewals, engagement, usage, and satisfaction scores.

      Identify motivations and possible incentives for advocate activities.

      Document
      Use slide 10 of the Executive Presentation Template to complete this exercise.

      2.3.2 Review and Refine Advocate Persona
      (60-300 min.)

      Review & Refine
      Place the Executive Presentation Template in a shared drive for team collaboration. Encourage the team to share persona knowledge within the shared drive version.

      Hold any necessary follow-up sessions to further refine persona.

      Validate
      Interview advocates that best represent your ideal advocate profile on their type of preferred involvement with your company, their role and needs when it comes to your solution, ways they'd be willing to advocate, and rewards sought.

      Confirm
      Incorporate feedback and inputs into slide 10 of the Executive Presentation Template. Ensure everyone agrees on persona developed.

      Tips & Reminders

      1. When identifying potential advocates, choose based on your most important audience.
      2. Ensure you're selecting those with the highest satisfaction scores.
      3. Ideally, select candidates that have, on their own, advocated previously such as in social posts, who may have acted as a reference, or who have been highly visible as a positive influence at customer events.
      4. Knowing motivations will determine the type of acts of advocacy they would be most willing to perform and the incentives for participating in the program.

      Consider the following criteria when identifying advocates and developing your ideal advocate persona:

      Demographics Firmographics Satisfaction & Needs/Value Sought Behavior Motivation
      Role - user, decision-maker, etc. Company size: # of employees Satisfaction score Purchase frequency & repeat purchases (renewals), upgrades Career building/promotion
      Department Company size: revenue NPS score Usage Collaboration with peers
      Geography CLV score Engagement (e.g. email opens, response, meetings) Educate others
      Industry Value delivered (outcomes, occasions used, etc.) Social media interaction, posts Influence (on product, service)
      Tenure as client Benefits sought
      Account size ($) Minimal and resolved service tickets, escalations
      1. When identifying potential advocates, choose based on your most important audience/segments. 2. Ensure you're selecting those with the highest satisfaction, NPS, and CLV scores. 3. When identifying potential advocates, choose based on high engagement and interaction, regular renewals, and high usage. 4. Knowing motivations will determine the type of acts of advocacy they would be most willing to perform and incentives for participating in the program.

      Phase 3: Win Executive Approval and Implement Pilot

      Steps
      3.1 Determine pilot goals and success metrics
      3.2 Establish timeline and create advocate communication materials
      3.3 Gain executive buy-in and implement pilot

      Phase Outcome

      • Clear objective for CA pilot
      • Key metrics for program success
      • Pilot timelines and milestones
      • Executive presentation with business case for CA

      Win executive approval and implement pilot

      Step 3.1 Determine pilot goals and success metrics

      Total duration: 2.0-4.0 hours

      Objective
      Set goals and determine the scope for the customer advocacy program pilot.

      Output

      • Documented business objectives for the pilot
      • Documented success metrics

      Participants

      • Customer advocacy lead
      • Key stakeholders
      • Sales lead
      • Marketing lead
      • Customer Success lead
      • Product lead

      MarTech
      May require to use, set up, or install platforms like:

      • Register to a survey platform
      • CRM or marketing automation platform

      Tools

      3.1.1 Establish Pilot Goals
      (60-120 min.)

      Set
      Organize a meeting with department heads and review organizational and individual department goals.

      Using the Venn diagram on slide 39 in this deck, identify customer advocacy goals that align with business goals. Select the highest priority goal for the pilot.

      Check that the goal aligns with benefits sought or addresses pain points identified in the previous phase.

      Document
      Document the goals on slides 9 and 16 of the Executive Presentation Template.

      3.1.2 Establish Pilot Success Metrics
      (60-120 min.)

      Decide
      Decide how you will measure the success of your program pilot using slide 40 in this document.

      Document
      Document metrics on slide 16 of the Executive Presentation Template.

      Tips & Reminders

      1. Don't boil the ocean. Pick the most important goal that can be achieved through the customer advocacy pilot to gain executive buy-in and support or resources for a formal customer advocacy program. Once successfully completed, you'll be able to tackle new goals and expand the program.
      2. Keep your metrics simple, few in number, and relatively easy to track

      Connect customer advocacy goals with organizational goals

      List possible customer advocacy goals, identifying areas of overlap with organizational goals by taking the following steps:

      1. List organizational/departmental goals in the green oval.
      2. List possible customer advocacy program goals in the purple oval.
      3. Enter goals that are covered in both the Organizational Goals and Customer Advocacy Goals sections into the Shared Goals section in the center.
      4. Highlight the highest priority goal for the customer advocacy program pilot to tackle.
      Organizational Goals Shared Goals Customer Advocacy Goals
      Example Example: Gain customer references to help advance sales and improve win rates Example: Develop pool of customer references
      [insert goal] [insert goal] Example: Gather customer feedback
      [insert goal] [insert goal] [insert goal]
      [insert goal] [insert goal] [insert goal]

      Customer advocacy success metrics for consideration

      This table provides a starting point for measuring the success of your customer advocacy pilot depending on the goals you've set.

      This list is by no means exhaustive; the metrics here can be used, or new metrics that would better capture success measurement can be created and tracked.

      Metric
      Revenue influenced by reference calls ($ / % increase)
      # of reference calls resulting in closed-won opportunities
      # of quotes collected
      % of community growth YoY
      # of pieces of product feedback collected
      # of acts of advocacy
      % membership growth
      % product usage amongst community members
      # of social shares, clicks
      CSAT score for community members
      % of registered qualified leads
      # of leads registered
      # of member sign-ups
      # of net-new referenceable customers
      % growth rate of products used by members
      % engagement rate
      # of published third-party reviews
      % increase in fulfilled RFPs

      When selecting metrics, remember:
      When choosing metrics for your customer advocacy pilot, be sure to align them to your specific goals. If possible, try to connect your advocacy efforts back to retention, growth, or revenue.

      Do not choose too many metrics; one per goal should suffice.

      Ensure that you can track the metrics you select to measure - the data is available and measuring won't be overly manual or time-consuming.

      Win executive approval and implement pilot

      Step 3.2 Establish timeline and create advocate communication materials

      Total duration: 2.5-8.0 hours

      Objective
      Outline who will be involved in what roles and capacities and what tasks and activities need to completed.

      Output

      • Timeline and milestones
      • Advocate program materials

      Participants

      • Customer advocacy lead
      • Key stakeholders
      • Sales lead
      • Marketing lead
      • Customer Success lead
      • Product lead

      MarTech
      None

      Tools

      3.2.1 Establish Timeline & Milestones
      (30-60 min.)

      List & Assign
      List all key tasks, phases, and milestones on slides 13, 14, and 15 in the Executive Presentation Template.

      Include any activities that help close gaps or address pain points from slide 9 in the Executive Presentation Template.

      Assign workstream leads on slide 15 in the Executive Presentation Template.

      Finalize all tasks and activities with working team.

      3.2.2 Design & Build Advocate Program Materials
      (180-300 min.)

      Decide
      Determine materials needed to recruit advocates and explain the program to advocate candidates.

      Determine the types of acts of advocacy you are looking for.

      Determine incentives/rewards that will be provided to advocates, such as access to new products or services.

      Build
      Build out all communication materials.

      Obtain incentives.

      Tips & Reminders

      1. When determining incentives, use the validated ideal advocate profile for guidance (i.e. what motivates your advocates?).
      2. Ensure to leave a buffer in the timeline if the need to adjust course arises.

      Win executive approval and implement pilot

      Step 3.3 Implement pilot and gain executive buy-in

      Total duration: 2.5-8.0 hours

      Objective
      Successfully implement the customer advocacy pilot program and communicate results to gain approval for full-fledged program.

      Output

      • Deliver Executive Presentation
      • Successful customer advocacy pilot
      • Provide regular updates to stakeholders, executives

      Participants

      • Customer advocacy lead
      • Workstream leads

      MarTech
      May require the use of:

      • CRM or Marketing Automation Platform
      • Available and up-to-date customer database

      Tools

      3.3.1 Complete & Deliver Executive Presentation
      (60-120 min.)

      Present
      Finalize the Executive Presentation.

      Hold stakeholder meeting and introduce the program pilot.

      3.3.2 Gain Executive Buy-in
      (60-300 min.)

      Pitch
      Present the final results of the customer advocacy pilot using the Executive Presentation Template and gain approval.

      3.3.3 Implement the Customer Advocacy Program Pilot
      (30-60 min.)

      Launch
      Launch the customer advocacy program pilot. Follow the timelines and activities outlined in the Executive Presentation Template. Track/document all advocate outreach, activity, and progress against success metrics.

      Communicate
      Establish a regular cadence to communicate with steering committee, stakeholders. Use the Executive Presentation Template to present progress and resolve roadblocks if/as they arise.

      Tips & Reminders

      1. Continually collect feedback and input from advocates and stakeholders throughout the process.
      2. Don't be afraid to make changes on the go if it helps to achieve the end goal of your pilot.
      3. If the pilot program was successful, consider scaling it up and rolling it out to more customers.

      Summary of Accomplishment

      Mission Accomplished

      • You successfully launched your customer advocacy program pilot and demonstrated clear benefits and ROI. By identifying the needs of the business and aligning those needs with key customer advocacy activities, marketers and customer advocacy leaders can prioritize the most important tasks for the pilot while also identifying potential opportunities for expansion pending executive approval.
      • SoftwareReviews' comprehensive and tactical approach takes you through the steps to build the foundation for a strategic customer advocacy program. Our methodology ensures that a customer advocacy pilot is developed to deliver the desired outcomes and ROI, increasing stakeholder buy-in and setting up your organization for customer advocacy success.

      If you would like additional support, contact us and we'll make sure you get the professional expertise you need.

      Contact your account representative for more information.
      info@softwarereviews.com
      1-888-670-8889

      Related SoftwareReviews Research

      Measure and Manage the Customer Satisfaction Metrics That Matter the Most
      Understand what truly keeps your customer satisfied. Measure what matters to improve customer experience and increase satisfaction and advocacy.

      • Understand the true drivers of satisfaction and dissatisfaction among your customer segments.
      • Establish process and cadence for effective satisfaction measurement and monitoring.
      • Know where resources are needed most to improve satisfaction levels and increase retention.

      Develop the Right Message to Engage Buyers
      Sixty percent of marketers find it hard to produce high-quality content consistently. SaaS marketers have an even more difficult job due to the technical nature of content production.

      • Create more compelling and relevant content that aligns with a buyer's needs and journey.
      • Shrink marketing and sales cycles.
      • Increase the pace of content production.

      Create a Buyer Persona and Journey
      Get deeper buyer understanding and achieve product-market fit, with easier access to market and sales.

      • Reduce time and resources wasted chasing the wrong prospects.
      • Increase open and click-through rates.
      • Perform more effective sales discovery.
      • Increase win rate.

      Bibliography

      "15 Award-Winning Customer Advocacy Success Stories." Influitive, 2021. Accessed 8 June 2023.

      "Advocacy Marketing." Influitive, June 2016. Accessed 26 Oct. 2021.

      Andrews, Marcus. "42% of Companies Don’t Listen to their Customers. Yikes." HubSpot, June 2019. Accessed 2 Nov. 2021.

      "Before you leap! Webcast." Point of Reference, Sept. 2019. Accessed 4 Nov. 2021.

      "Brand Loyalty: 5 Interesting Statistics." Factory360, Jan. 2016. Accessed 2 Nov. 2021.

      Brenner, Michael. "The Data Driven Guide to Customer Advocacy." Marketing Insider Group, Sept. 2021. Accessed 3 Feb. 2022.

      Carroll, Brian. "Why Customer Advocacy Should Be at the Heart of Your Marketing." Marketing Insider Group, Sept. 2017. Accessed 3 Feb. 2022.

      Cote, Dan. "Advocacy Blooms and Business Booms When Customers and Employees Engage." Influitive, Dec. 2021. Accessed 3 Feb. 2022.

      "Customer Success Strategy Guide." ON24, Jan. 2021. Accessed 2 Nov. 2021.

      Dalao, Kat. "Customer Advocacy: The Revenue-Driving Secret Weapon." ReferralRock, June 2017. Accessed 7 Dec. 2021.

      Frichou, Flora. "Your guide to customer advocacy: What is it, and why is it important?" TrustPilot, Jan. 2020. Accessed 26 Oct. 2021.

      Gallo, Amy. "The Value of Keeping the Right Customers." Harvard Business Review, Oct. 2014. Accessed 10 March 2022.

      Huhn, Jessica. "61 B2B Referral Marketing Statistics and Quotes." ReferralRock, March 2022. Accessed 10 March 2022.

      Kemper, Grayson. "B2B Buying Process: How Businesses Purchase B2B Services and Software." Clutch, Feb. 2020. Accessed 6 Jan. 2022.

      Kettner, Kyle. "The Evolution of Ambassador Marketing." BrandChamp.io, Oct. 2018. Accessed 2 Nov. 2021.

      Landis, Taylor. "Customer Retention Marketing vs. Customer Acquisition Marketing." OutboundEngine, April 2022. Accessed 23 April 2022.

      Miels, Emily. "What is customer advocacy? Definition and strategies." Zendesk Blog, June 2021. Accessed 27 Oct. 2021.

      Mohammad, Qasim. "The 5 Biggest Obstacles to Implementing a Successful B2B Customer Advocacy Program." HubSpot, June 2018. Accessed 6 Jan. 2022.

      Murphy, Brandon. "Brand Advocacy and Social Media - 2009 GMA Conference." Deloitte, Dec. 2009. Accessed 8 June 2023.

      Patel, Neil. "Why SaaS Brand Advocacy is More Important than Ever in 2021." Neil Patel, Feb. 2021. Accessed 4 Nov. 2021.

      Pieri, Carl. "The Plain-English Guide to Customer Advocacy." HubSpot, Apr. 2020. Accessed 27 Oct. 2021.

      Schmitt, Philipp; Skiera, Bernd; Van den Bulte, Christophe. "Referral Programs and Customer Value." Wharton Journal of Marketing, Jan. 2011. Accessed 8 June 2023.

      "The Complete Guide to Customer Advocacy." Gray Group International, 2020. Accessed 15 Oct. 2021.

      "The Customer-powered Enterprise: Playbook." Influitive, Gainsight & Pendo. 2020. Accessed 26 Oct. 2021.

      "The Winning Case for a Customer Advocacy Solution." RO Innovation, 2017. Accessed 26 Oct. 2021.

      Tidey, Will. "Acquisition vs. Retention: The Importance of Customer Lifetime Value." Huify, Feb. 2018. Accessed 10 Mar. 2022.

      "What a Brand Advocate Is and Why Your Company Needs One." RockContent, Jan. 2021. Accessed 7 Feb. 2022.

      "What is Customer Advocacy? A Definition and Strategies to Implement It." Testimonial Hero, Oct. 2021. Accessed 26 Jan. 2022.

      Deliver on Your Digital Product Vision

      • Buy Link or Shortcode: {j2store}351|cart{/j2store}
      • member rating overall impact: 9.2/10 Overall Impact
      • member rating average dollars saved: $133,318 Average $ Saved
      • member rating average days saved: 30 Average Days Saved
      • Parent Category Name: Development
      • Parent Category Link: /development
      • Product organizations are under pressure to align the value they provide to the organization’s goals and overall company vision.
      • You need to clearly convey your direction, strategy, and tactics to gain alignment, support, and funding from your organization.
      • Products require continuous additions and enhancements to sustain their value. This requires detailed, yet simple communication to a variety of stakeholders.

      Our Advice

      Critical Insight

      • A vision without tactics is an unsubstantiated dream, while tactics without a vision is working without a purpose. You need to have a handle on both to achieve outcomes that are aligned with the needs of your organization.

      Impact and Result

      • Recognize that a vision is only as good as the data that backs it up – lay out a comprehensive backlog with quality built-in that can be effectively communicated and understood through roadmaps.
      • Your intent is only a dream if it cannot be implemented – define what goes into a release plan via the release canvas.
      • Define a communication approach that lets everyone know where you are heading.

      Deliver on Your Digital Product Vision Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should build a digital product vision that you can stand behind. Review Info-Tech’s methodology and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Define a digital product vision

      Define a digital product vision that takes into account your objectives, business value, stakeholders, customers, and metrics.

      • Deliver on Your Digital Product Vision – Phase 1: Define a Digital Product Vision
      • Digital Product Strategy Template
      • Digital Product Strategy Supporting Workbook

      2. Build a better backlog

      Build a structure for your backlog that supports your product vision.

      • Deliver on Your Digital Product Vision – Phase 2: Build a Better Backlog
      • Product Backlog Item Prioritization Tool

      3. Build a product roadmap

      Define standards, ownership for your backlog to effectively communicate your strategy in support of your digital product vision.

      • Deliver on Your Digital Product Vision – Phase 3: Build a Product Roadmap
      • Product Roadmap Tool

      4. Release and deliver value

      Understand what to consider when planning your next release.

      • Deliver on Your Digital Product Vision – Phase 4: Release and Deliver Value

      5. Communicate the strategy – make it happen

      Build a plan for communicating and updating your strategy and where to go next.

      • Deliver on Your Digital Product Vision – Phase 5: Communicate the Strategy – Make It Happen!

      Infographic

      Workshop: Deliver on Your Digital Product Vision

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Define a Digital Product Vision

      The Purpose

      Understand the elements of a good product vision and the pieces that back it up.

      Key Benefits Achieved

      Provide a great foundation for an actionable vision and goals people can align to.

      Activities

      1.1 Build out the elements of an effective digital product vision

      Outputs

      Completed product vision definition for a familiar product via the product canvas

      2 Build a Better Backlog

      The Purpose

      Define the standards and approaches to populate your product backlog that support your vision and overall strategy.

      Key Benefits Achieved

      A prioritized backlog with quality throughout that enables alignment and the operationalization of the overall strategy.

      Activities

      2.1 Introduction to key activities required to support your digital product vision

      2.2 What do we mean by a quality backlog?

      2.3 Explore backlog structure and standards

      2.4 Define backlog data, content, and quality filters

      Outputs

      Articulate the activities required to support the population and validation of your backlog

      An understanding of what it means to create a quality backlog (quality filters)

      Defining the structural elements of your backlog that need to be considered

      Defining the content of your backlog and quality standards

      3 Build a Product Roadmap

      The Purpose

      Define standards and procedures for creating and updating your roadmap.

      Key Benefits Achieved

      Enable your team to create a product roadmap to communicate your product strategy in support of your digital product vision.

      Activities

      3.1 Disambiguating backlogs vs. roadmaps

      3.2 Defining audiences, accountability, and roadmap communications

      3.3 Exploring roadmap visualizations

      Outputs

      Understand the difference between a roadmap and a backlog

      Roadmap standards and agreed-to accountability for roadmaps

      Understand the different ways to visualize your roadmap and select what is relevant to your context

      4 Define Your Release, Communication, and Next Steps

      The Purpose

      Build a release plan aligned to your roadmap.

      Key Benefits Achieved

      Understand what goes into defining a release via the release canvas.

      Considerations in communication of your strategy.

      Understand how to frame your vision to enable the communication of your strategy (via an executive summary).

      Activities

      4.1 Lay out your release plan

      4.2 How to introduce your product vision

      4.3 Communicate changes to your strategy

      4.4 Where do we get started?

      Outputs

      Release canvas

      An executive summary used to introduce other parties to your product vision

      Specifics on communication of the changes to your roadmap

      Your first step to getting started

      Refine Your Estimation Practices With Top-Down Allocations

      • Buy Link or Shortcode: {j2store}434|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $12,599 Average $ Saved
      • member rating average days saved: 20 Average Days Saved
      • Parent Category Name: Portfolio Management
      • Parent Category Link: /portfolio-management
      • As a portfolio manager, you’re expected to size projects for approval and intake before they have sufficient definition.
      • The consequences of initial sizing are felt throughout the project lifecycle.

      Our Advice

      Critical Insight

      • Your organization lacks strong organizational memory upon which assumptions and estimates can be made.
      • Definition is at a minimum not validated, untested, and is likely incomplete. It has the potential to be dangerously misleading.

      Impact and Result

      • Build project history and make more educated estimates – Projects usually start with a “ROM” or t-shirt size estimate, but if your estimates are consistently off, then it’s time to shift the scale.
      • Plan ahead – Projects face risks; similar projects face similar risks. Provide sponsors with estimates that account for as many risks as possible, so that if something goes wrong you have a plan to make it right.
      • Store and strengthen organizational memory – Each project is rich with lessons that can inform your next project to make it more effective and efficient, and ultimately help to avoid committing the same failures over and over again. Develop a process to catalogue project history and all of the failures and successes associated with those projects.

      Refine Your Estimation Practices With Top-Down Allocations Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should improve your estimation practices, review Info-Tech’s methodology, and understand the ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Build organizational memory to inform early estimates

      Analyze your project history to identify and fill gaps in your estimation practices.

      • Refine Your Estimation Practices With Top-Down Allocations – Phase 1: Build Organizational Memory to Inform Early Estimations
      • PMO Organizational Memory Tool
      • T-Shirt Sizing Health Check Lite
      • Project Estimation Playbook

      2. Develop and refine a reliable estimate with top-down allocations

      Allocate time across project phases to validate and refine estimates and estimate assumptions.

      • Refine Your Estimation Practices With Top-Down Allocations – Phase 2: Develop and Refine a Reliable Estimate With Top-Down Allocations
      • Planning-Level Estimate Calculator

      3. Implement a new estimation process

      Implement a lessons learned process to provide transparency to your sponsors and confidence to your teams.

      • Refine Your Estimation Practices With Top-Down Allocations – Phase 3: Implement a New Estimation Process
      • Project Lessons Learned Template
      [infographic]

      Workshop: Refine Your Estimation Practices With Top-Down Allocations

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Develop the Foundations of Organizational Memory

      The Purpose

      Track key performance indicators on past projects to inform goals for future projects.

      Key Benefits Achieved

      Developed Project History List.

      Refined starting estimates that can be adjusted accurately from project to project.

      Activities

      1.1 Build project history.

      1.2 Analyze estimation capabilities.

      1.3 Identify estimation goals.

      Outputs

      Project History List

      T-Shirt Sizing Health Check

      Estimate Tracking Plan

      2 Define a Requirements Gathering Process

      The Purpose

      Outline the common attributes required to complete projects.

      Identify the commonly forgotten attributes to ensure comprehensive scoping early on.

      Key Benefits Achieved

      Refined initial estimate based on high-level insights into work required and resources available.

      Activities

      2.1 Develop a list of in-scope project attributes.

      2.2 Identify leadership priorities for deliverables and attributes.

      2.3 Track team and skill responsibilities for attributes.

      Outputs

      Identified list or store of past project attributes and costs

      Attribute List and Estimated Cost

      Required Skills List

      3 Build an Estimation Process

      The Purpose

      Set clear processes for tracking the health of your estimate to ensure it is always as accurate as possible.

      Define check-in points to evaluate risks and challenges to the project and identify trigger conditions.

      Key Benefits Achieved

      An estimation process rooted in organizational memory and lessons learned.

      Project estimates that are consistently reevaluated to predict and correct challenges before they can drastically affect your projects.

      Activities

      3.1 Determine Milestone Check-In Points.

      3.2 Develop Lessons Learned Meeting Agendas.

      3.3 Identify common risks and past lessons learned.

      3.4 Develop contingency tracking capabilities.

      Outputs

      Project Lessons Learned Template

      Historic Risks and Lessons Learned Master Template

      Contingency Reserve and Risk Registers

      4 Improve Business Alignment With Your Estimation Plan

      The Purpose

      Bridge the gap between death march projects and bloated and uncertain estimates by communicating expectations and assumptions clearly to your sponsors.

      Key Benefits Achieved

      Clear estimation criteria and assumptions aligned with business priorities.

      Post-mortem discussion items crucial to improving project history knowledge for next time.

      Activities

      4.1 Identify leadership risk priorities.

      4.2 Develop IT business alignment.

      4.3 Develop hand-off procedures and milestone approval methods.

      4.4 Create a list of post-mortem priorities.

      Outputs

      Estimation Quotation

      Risk Priority Rankings

      Hand-Off Procedures

      Post-mortem agenda planning

      Design Your Cloud Operations

      • Buy Link or Shortcode: {j2store}462|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: 20 Average Days Saved
      • member rating average days saved: After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.
      • Parent Category Name: Operations Management
      • Parent Category Link: /i-and-o-process-management
      • Traditional IT capabilities, activities, organizational structures, and culture need to adjust to leverage the value of cloud, optimize spend, and manage risk.
      • Different stakeholders across previously separate teams rely on one another more than ever, but rules of engagement do not yet exist.

      Our Advice

      Critical Insight

      Define your target cloud operations state first, then plan how to get there. If you begin by trying to reconstruct on-prem operations in the cloud, you will build an operations model that is the worst of both worlds.

      Impact and Result

      • Assess your key workflows’ maturity for life in the cloud and evaluate your readiness and need for new ways of working
      • Identify the work that must be done to deliver value in cloud services
      • Design your cloud operations framework and communicate it clearly and succinctly to secure buy-in

      Design Your Cloud Operations Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Design Your Cloud Operations Deck – A step-by-step storyboard to help guide you through the activities and tools in this project.

      This storyboard will help you assess your cloud maturity, understand relevant ways of working, and create a meaningful design of your cloud operations that helps align team members and stakeholders.

      • Design Your Cloud Operations – Storyboard
      • Cloud Operations Design Sketchbook
      • Roadmap Tool

      2. Planning and design tools.

      Use these templates and tools to assess your current state, design the cloud operations organizing framework, and create a roadmap.

      • Cloud Maturity Assessment

      3. Communication tools.

      Use these templates and tools to plan how you will communicate changes to key stakeholders and communicate the new cloud operations organizing framework in an executive presentation.

      • Cloud Operations Communication Plan
      • Cloud Operations Organizing Framework: Executive Brief

      Infographic

      Workshop: Design Your Cloud Operations

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Day 1

      The Purpose

      Establish Context

      Key Benefits Achieved

      Alignment on target state

      Activities

      1.1 Assess current cloud maturity and areas in need of improvement

      1.2 Identify the drivers for organizational redesign

      1.3 Review cloud objectives and obstacles

      1.4 Develop organization design principles

      Outputs

      Cloud maturity assessment

      Project drivers

      Cloud challenges and objectives

      Organization design principles

      2 Day 2

      The Purpose

      Establish Context

      Key Benefits Achieved

      Understanding of cloud workstreams

      Activities

      2.1 Evaluate new ways of working

      2.2 Develop a workstream target statement

      2.3 Identify cloud work

      Outputs

      Workstream target statement

      Cloud operations workflow diagrams

      3 Day 3

      The Purpose

      Design the Organization

      Key Benefits Achieved

      Visualization of the cloud operations future state

      Activities

      3.1 Design a future-state cloud operations diagram

      3.2 Create a current-state cloud operations diagram

      3.3 Define success indicators

      Outputs

      Future-state cloud operations diagram

      Current-state cloud operations diagram

      Success indicators

      4 Day 4

      The Purpose

      Communicate the Changes

      Key Benefits Achieved

      Alignment and buy-in from stakeholders

      Activities

      4.1 Create a roadmap

      4.2 Create a communication plan

      Outputs

      Roadmap

      Communication plan

      Further reading

      It’s “day two” in the cloud. Now what?

      EXECUTIVE BRIEF

      Analysts’ Perspective

      The image contains a picture of Andrew Sharp.

      Andrew Sharp

      Research Director

      Infrastructure & Operations Practice

      It’s “day two” in the cloud. Now what?

      Just because you’re in the cloud doesn’t mean everyone is on the same page about how cloud operations work – or should work.

      You have an opportunity to implement new ways of working. But if people can’t see the bigger picture – the organizing framework of your cloud operations – it will be harder to get buy-in to realize value from your cloud services.

      Use Info-Tech’s methodology to build out and visualize a cloud operations organizing framework that defines cloud work and aligns it to the right areas.

      The image contains a picture of Nabeel Sherif.

      Nabeel Sherif

      Principal Research Director

      Infrastructure & Operations Practice

      The image contains a picture of Emily Sugerman.

      Emily Sugerman

      Research Analyst

      Infrastructure & Operations Practice

      Scott Young

      Principal Research Director

      Infrastructure & Operations Practice

      Executive Summary

      Your Challenge

      Common Obstacles

      Info-Tech’s Approach

      Widespread cloud adoption has created new opportunities and challenges:

      • Traditional IT capabilities, activities, organizational structures, and culture need to adjust to leverage the value of cloud, optimize spend, and manage risk.
      • Different stakeholders across previously separate teams rely on one another more than ever, but rules of engagement do not yet exist, leading to a lack of direction, employee frustration, missed work, inefficiency, and unacceptable risk.
      • Many organizations have bought their way into a SaaS portfolio. Now, as key applications leave their network, I&O leaders still have accountability for these apps, but little visibility and control over them.
      • Few organizations are, or will ever be, cloud only. Your operations will be both on-prem and in-cloud for the foreseeable future and you must be able to accommodate both.
      • Traditional infrastructure siloes no longer work for cloud operations, but key stakeholders are wary of significant change.

      Clearly communicate the need for operations changes:

      • Identify current challenges with cloud operations. Assess your readiness and fit for new ways of working involved in cloud operations: DevOps, SRE, Platform Engineering, and more.
      • Use Info-Tech’s templates to design a cloud operations organizing framework. Define cloud work, and align work to the right work areas.
      • Communicate the design. Gain buy-in from your key stakeholders for the considerable organizational change management required to achieve durable change.

      Info-Tech Insight

      Define your target cloud operations state first, then plan how to get there. If you begin by trying to reconstruct on-prem operations in the cloud, you will build an operations model that is the worst of both worlds.

      Your Challenge

      Traditional IT capabilities, activities, organizational structures, and culture need to adjust to leverage the value of cloud, optimize spend, and manage risk.

      • As key applications leave for the cloud, I&O teams are still expected to manage access, spend, and security but may have little or no visibility or control over the applications themselves.
      • The automation and self-service capabilities of cloud aren’t delivering the speed the business expected because teams don’t work together effectively.
      • Business leaders purchase their own cloud solutions because, from their point of view, IT’s processes are cumbersome and ineffective.
      • Accounting practices and governance mechanisms haven’t adjusted to enable new development practices and technologies.
      • Security and cost management requirements may not be accounted for by teams acquiring or developing solutions.
      • All of this contributes to frustration, missed work, wasteful spending, and unacceptable risk.

      Obstacles, by the numbers:

      85% of respondents reported security in the cloud was a serious concern.

      73% reported balancing responsibilities between a central cloud team and business units was a top concern.

      The average organization spent 13% more than they’d budgeted on cloud – even when budgets were expected to increase by 29% in the next year.

      32% of all cloud spend was estimated to be wasted spend.

      56% of operations professionals said their primary focus is cloud services.

      81% of security professionals thought it was difficult to get developers to prioritize bug fixes.

      42% of security professionals felt bugs were being caught too late in the development process.

      1. Flexera 2022 State of the Cloud Report. 2. GitLab DevSecOps 2021 Survey

      Cloud operations are different, but IT departments struggle to change

      • There’s no sense of urgency in the organization that change is needed, particularly from teams that aren’t directly involved in operations. It can be challenging to make the case that change is needed.
      • Beware “analysis paralysis”! With so many options, philosophies, approaches, and methodologies, it’s easy to be overwhelmed by choice and fail to make needed changes.
      • The solution to the problem requires organizational changes beyond the operations team, but you don’t have the authority to make those changes directly. Operations can influence the solution, but they likely can’t direct it.
      • Behavior, culture, and organizations take time and work to change. Progress is usually evolutionary – but this can also mean it feels like it’s happening too slowly.
      • It’s not just cloud, and it probably never will be. You’ll need to account for operating both on-premises and cloud technologies for the foreseeable future.

      Follow Info-Tech’s Methodology

      1. Ensure alignment with the risks and drivers of the business and understand your organization’s strengths and gaps for a cloud operations world.

      2. Understand the balance of different types of deliveries you’re responsible for in the cloud.

      3. Reduce risk by reinforcing the key operational pillars of cloud operations to your workstreams.

      4. Identify “work areas,” decide which area is responsible for what tasks and how work areas should interact in order to best facilitate desired business outcomes.

      The image contains a screenshot of a diagram demonstrating Info-Tech's Methodology, as described in the text above.

      Info-Tech Insight

      Start by designing operations around the main workflow you have for cloud services; i.e. If you mostly build or host in cloud, build the diagram to maximize value for that workflow.

      Operating Framework Elements

      Proper design of roles and responsibilities for each cloud workflow category will help reduce risk by reinforcing the key operational pillars of cloud operations.

      We base this on a composite of the well-architected frameworks established by the top global cloud providers today.

      Workflow Categories

      • Build
      • Host
      • Consume

      Key Pillars

      • Performance
      • Reliability
      • Cost Effectiveness
      • Security
      • Operational Excellence

      Risks to Mitigate

      • Changes to Support Model
      • Changes to Security & Governance
      • Changes to Skills & Roles
      • Replicating Old Habits
      • Misaligned Stakeholders

      Cloud Operations Design

      Info-Tech’s Methodology

      Assess Maturity and Ways of Working

      Define Cloud Work

      Design Cloud Operations

      Communicate and Secure Buy-in

      Assess your key workflows’ maturity for “life in the cloud,” related to Key Operational Pillars. Evaluate your readiness and need for new ways of working.

      Identify the work that must be done to deliver value in cloud services.

      Define key cloud work areas, the work they do, and how they should share information and interact.

      Outline the change you recommend to a range of stakeholders. Gain buy-in for the plan.

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals.

      Cloud Maturity Assessment

      Assess the intensity and cloud maturity of your IT operations for each of the key cloud workstreams: Consume, Host, and Build

      The image contains screenshots of the Cloud Maturity Assessment.

      Communication Plan

      Identify stakeholders, what’s in it for them, what the impact will be, and how you will communicate over the course of the change.

      The image contains a screenshot of the Communcation Plan.

      Cloud Operations Design Sketchbook

      Capture the diagram as you build it.

      The image contains a screenshot of the Cloud Operations Design Sketchbook.

      Roadmap Tool

      Build a roadmap to put the design into action.

      The image contains a screenshot of the Roadmap Tool.

      Key deliverable:

      Cloud Operations Organizing Framework

      The Cloud Operations Organizing Framework is a communication tool that introduces the cloud operations diagram and establishes its context and justification.

      The image contains a screenshot of the Cloud Operations Organizing Framework.

      Project Outline

      Phase 1: Establish Context

      1.1: Identify challenges, opportunities, and cloud maturity

      1.2: Evaluate new ways of working

      1.3: Define cloud work

      Phase 2: Design the organization and communicate changes

      2.1: Design a draft cloud operations diagram

      2.2: Communicate changes

      Outputs

      Cloud Services Objectives and Obstacles

      Cloud Operations Workflow Diagrams

      Cloud Maturity Assessment

      Draft Cloud Operations Diagram

      Communication Plan

      Roadmap Tool

      Cloud Operations Organizing Framework

      Project benefits

      Benefits for IT

      Benefits for the business

      • Define the work required to effectively deliver cloud services to deliver business value.
      • Define key roles for operating cloud services.
      • Outline an operations diagram that visually communicates what key work areas do and how they interact.
      • Communicate needed changes to key stakeholders.
      • Receive more value from cloud services when the organization is structured to deliver value including:
        • Avoiding cost overruns
        • Securing services
        • Providing faster, more effective delivery
        • Increasing predictability
        • Reducing error rates

      Calculate the value of Info-Tech’s Methodology

      The value of the project is the delivery of organizational change that improves the way you manage cloud services

      Example Goal

      How this blueprint can help

      How you might measure success/value

      Streamline Responsibilities

      The operations team is spending too much time fighting applications fires, which is distracting it from needed platform improvements.

      • Identify shared and separate responsibilities for development and platform operations teams.
      • Focus the operations team on securing and automating cloud platform(s).
      • Reduce time wasted on back and forth between development and operations teams (20 hrs. per employee per year x 50 staff = 1000 hrs.).
      • Deliver automation features that reduces development lead time by one hour per sprint (40 devs x 20 sprints per yr. x 1 hr. = 800 hrs.).

      Improve Cost Visibility

      The teams responsible for cost management today don’t have the authority, visibility, or time to effectively find wasted spend.

      The teams responsible for cost management today don’t have the authority, visibility, or time to effectively find wasted spend.

      • Ensure operations contributes to visibility and execution of cost governance.
      • $1,000,000 annual spend on cloud services.
      • Of this, assume 32% is wasted spend ($320k).1
      • New cost management function has a target to cut waste by half next year saving ~$160k.
      • Cost visibility and capture metrics (e.g. accurate tagging metrics, right-sizing execution).
      1. Average wasted cloud spend across all organizations, from the 2022 Flexera State of the Cloud Report

      Understand your cloud vision and strategy before you redesign operations

      Guide your operations redesign with an overarching cloud vision and strategy that aligns to and enables the business’s goals.

      Cloud Vision

      The image contains a screenshot of the Define Your Cloud Vision.

      Cloud Strategy

      It is difficult to get or maintain buy-in for changes to operations without everyone on the same page about the basic value proposition cloud offers your organization.

      Do the workload and risk analysis to create a defensible cloud vision statement that boils down into a single statement: “This is how we want to use the cloud.”

      Once you have your basic cloud vision, take the next step by documenting a cloud strategy.

      Establish your steering committee with stakeholders from IT, business, and leadership to work through the essential decisions around vision and alignment, people, governance, and technology.

      Your cloud operations design should align to a cloud strategy document that provides guidelines on establishing a cloud council, preparing staff for changing skills, mitigating risks through proper governance, and setting a direction for migration, provisioning, and monitoring decisions.

      Key Insights

      Focus on the future, not the present

      Define your target cloud operations state first, then plan how to get there. If you begin by trying to reconstruct on-prem operations in the cloud, you will build an operations model that is the worst of both worlds.

      Responsibilities change in the cloud

      Understand what you mean by cloud work

      Focus where it matters

      Cloud is a different way of consuming IT resources and applications and it requires a different operational approach than traditional IT.

      In most cases, cloud operations involves less direct execution and more service validation and monitoring

      Work that is invisible to the customer can still be essential to delivering customer value. A lot of operations work is invisible to your organization’s customers but is required to deliver stability, security, efficiency, and more.

      Cloud work is not just applications that have been approved by IT. Consider how unsanctioned software purchased by the business will be integrated and managed.

      Start by designing operations around the main workflow you have for cloud services. If you mostly build or host in the cloud, build the diagram to maximize value for that workflow.

      Design principles will often change over time as the organization’s strategy evolves.

      Identify skills requirements and gaps as early as possible to avoid skills gaps later. Whether you plan to acquire skills via training or cross-training, hiring, contracting, or outsourcing, effectively building skills takes time.

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      Guided Implementation

      Workshop

      Consulting

      “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”“Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”“We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”“Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

      Diagnostics and consistent frameworks used throughout all four options

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1

      Phase 2

      Call #1: Scope requirements, objectives, and your specific challenges

      Calls #2&3: Assess cloud maturity and drivers for org. redesign

      Call #4: Review cloud objectives and obstacles

      Call #5: Evaluate new ways of working and identify cloud work

      Calls #6&7: Create your Cloud Operations diagram

      Call #8: Create your communication plan and build roadmap

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      Workshop Overview

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889

      Day 1

      Day 2

      Day 3

      Day 4

      Day 5

      Establish Context

      Design the Organization and Communicate Changes

      Next Steps and
      Wrap-Up (offsite)

      Activities

      1.1 Assess current cloud maturity and areas in need of improvement

      1.2 Identify the drivers for organizational redesign

      1.3 Review cloud objectives and obstacles

      1.4 Develop organization design principles

      2.1 Evaluate new ways of working

      2.2 Develop a workstream target statement

      2.3 Identify cloud work

      3.1 Design a future-state cloud operations diagram

      3.2 Create a current state cloud operations diagram

      3.3 Define success indicators

      4.1 Create a roadmap

      4.2 Create a communication plan

      5.1 Complete in-progress deliverables from previous four days.

      5.2 Set up review time for workshop deliverables and to discuss next steps.

      Deliverables

      1. Cloud Maturity Assessment
      2. Cloud Challenges and Objectives
      1. Workstream target statement
      2. Cloud Operations Workflow Diagrams
      1. Future and current state cloud operations diagrams
      1. Roadmap
      2. Communication Plan

      Cloud Operations Organizing Framework.

      Phase 1:

      Establish context

      Phase 1

      Phase 2

      1.1 Establish operating model design principals by identifying goals & challenges, workstreams, and cloud maturity

      1.2 Evaluate new ways of working

      1.3 Identify cloud work

      2.1 Draft an operating model

      2.2 Communicate proposed changes

      Phase Outcomes:

      Define current maturity and which workstreams are important to your organization.

      Understand new operating approaches and which apply to your workstream balance.

      Identify a new target state for IT operations.

      Before you get started

      Set yourself up for success with these three steps:

      • This methodology and the related slides are intended to be executed via intensive, collaborative working sessions using the rest of this slide deck.
      • Ensure the working sessions are successful by working through these steps before you start work on defining your cloud operations.

      1. Identify an operations design working group

      2. Review cloud vision and strategy

      3. Create a working folder

      This should be a group with insight into current cloud challenges, and with the authority to drive change. This group is the main audience for the activities in this blueprint.

      Review your established planning work and documentation.

      Create a repository to house your notes and any work in progress.

      Create a working folder

      15 minutes

      Create a central repository to support transparency and collaboration. It’s an obvious step, but one that’s often forgotten.

      1. Download all the documents associated with this blueprint to a shared repository accessible to all participants. Keep separate folders for templates and work-in-progress.
      2. Share the link to the repository with all attendees. Include links to the repository in any meeting invites you set up as working sessions for the project.
      3. Use the repository for all the work you do in the activities listed in this blueprint.

      Step 1.1: Identify goals and challenges, workstreams, and cloud maturity

      Participants

      • Operations Design Working Group, which may include:
        • Cloud owners
        • Platform/Applications Team leads
        • Infra & Ops managers

      Outcomes

      • Identify your current cloud maturity and areas in need of improvement.
      • Define the advantages you expect to realize from cloud services and any obstacles you have to overcome to meet those objectives.
      • Identify the reasons why redesigning cloud operations is necessary.
      • Develop organization design principles.

      “Start small: Begin with a couple services. Then, based on the feedback you receive from Operations and the business, modify your approach and keep increasing your footprint.” – Nenad Begovic

      Cloud changes operational activities, tactics, and goals

      As you adopt cloud services, the operations core mission remains . . .

      • IT operations are expected to deliver stable, efficient, and secure IT services.

      . . . but operational activities are evolving.

      • Core IT operational processes remain relevant, such as incident or capacity management, but opportunities to automate or outsource operations tasks will change how that work is done.
      • As you rely more on automation and outsourcing, the team may see less direct execution in its day-to-day work and more solution design and validation.
      • Outsourcing frees the team from operational toil but reduces the direct control over your end-to-end solution and increases your reliance on your vendor.
      • Pay-as-you-go pricing models present opportunities for streamlined delivery and cost rationalization but require you to rethink how you do cost and asset management.
      • It’s very easy for the business to buy a SaaS solution without consulting IT, which can lead to duplicated functionality, integration challenges, security threats, and more.

      Design a model for cloud operations that helps you achieve value from your cloud environment.

      “As operating models shift to the cloud, you still need the same people and processes. However, the shift is focused on a higher level of operations. If your people no longer focus on server uptime, then their success metrics will change. When security is no longer protected by the four walls of a datacenter, your threat profile changes.

      (Microsoft, “Understand Cloud Operating Models,” 2022)

      Operational responsibilities are shared with a range of stakeholders

      When using a vendor-operated public cloud, IT exists in a shared responsibility model with the cloud service provider, one that is further differentiated by the type of cloud service model in use: broadly, software-as a service (SaaS), platform-as-a-service (PaaS), or infrastructure-as-a-service (IaaS).

      Your IT operations organization may still reflect a structure where IT retains control over the entire infrastructure stack from facilities to application and defines their operational roles and processes accordingly.

      If the organization chooses a co-location facility, they outsource facility responsibility to a third-party provider, but much of the rest of the traditional IT operating model remains the same. The operations model that worked for an entirely premises-based environment is very different from one that is made up of, for instance, a portfolio of SaaS applications, where your control is limited to the top of the infrastructure stack at the application layer.

      Once an organization migrates workloads to the cloud, IT gives up an increasing amount of control to the vendor, and its traditional operational roles & responsibilities necessarily change.

      The image contains a screenshot that demonstrates what the cloud service models are.

      Align operations with customer value

      • Decisions about operational design should be made with customer value in mind. Remember that cloud adoption should be an enabler of adaptability in the face of changing business needs!
      • Think about how the operations team is indispensable to the value received by your customer. Think about the types of changes that can add to the value your customers receive.
      • A focus on value will help you establish and explain the rationale and urgency required to deliver on needed changes. If you can’t explain how the changes you propose will help deliver value, your proposal will come across as change for the sake of change.
      The image contains a screenshot of a diagram to demonstrate how operational design decisions need to be made with customer value in mind.

      Info-Tech Insight

      Work that is invisible to the customer can still be essential to delivering customer value. A lot of operations work is invisible to your organization’s customers but required to deliver stability, security, efficiency, and more.

      A new consumption model means a different mix of activities

      Evolving to cloud-optimal operations also means re-assessing and adapting your team’s approach to achieving cloud maturity, especially with respect to how automation and standardization can be leveraged to best achieve optimization in cloud.

      Traditional ITDesignExecuteValidateSupportMonitor
      CloudDesignExecuteValidateSupportMonitor

      Info-Tech Insight

      Cloud is a different way of consuming IT resources and applications and requires a different operational approach than traditional IT.

      In most cases, cloud operations involves less direct execution and more service validation and monitoring.

      The Service Models in cloud correspond to the way your organization delivers IT

      Service Model

      Example

      Function

      Software-as-a-Service (SaaS)

      Salesforce.com

      Office 365

      Workday

      Consume

      Platform-as-a-Service (PaaS)

      Azure Stack

      AWS SageMaker

      WordPress

      Build

      Infrastructure-as-a-Service (IaaS)

      Microsoft Azure

      Amazon EC2

      Google Cloud Platform

      Host

      Define how you plan to use cloud services

      Your cloud operations will include different tasks, teams, and workflows, depending on whether you consume cloud services, build them, or host on them.

      Function

      Business Need

      Service Model

      Example Tasks

      Consume

      “I need a commodity, off-the-shelf service that we can configure to our organization’s needs.

      Software-as-a-Service (SaaS)

      Onboard and add users to a new SaaS offering. Vendor management of SaaS providers. Configure/integrate the SaaS offering to meet business needs.

      Build

      “I need to create significantly customized or net-new products and services.”

      Platform-as-a-Service (PaaS) & Infrastructure as-a-Service (IaaS)

      Create custom applications. Build and maintain a container platform. Manage CI/CD pipelines and tools. Share infrastructure and applications patterns.

      Host

      “I need compute, storage, and networking components that reflect key cloud characteristics (on-demand self-service, metered usage, etc.).”

      Infrastructure-as-a-Service (IaaS)

      Stand up compute, networking, and storage resources to host a COTS application. Plan to increase storage capacity to support future demand.

      Align to the well-architected framework

      • Each cloud provider has defined a well-architected framework (WAF) that defines effective deployment and operations for their services.
      • WAFs embody a set of best practices and design principles to leverage the cloud in a more efficient, secure, and cost-effective manner.
      • While each vendor’s WAF has its own definitions and nuances, they collectively share a set of key principles, or “pillars,” that define the desired outcome of any cloud deployment.
      • These pillars address the key areas of risk when migrating to a public cloud platform.

      “In order to accelerate public cloud adoption, you need to focus on infrastructure-as-code and script everything you can. Unlike traditional operations, CloudOps focuses on creating scripts: a script for task A, a script for task B, etc.”

      – Nenad Begovic

      Pillars

      • Reliability
      • Security
      • Cost Optimization
      • Operational Excellence
      • Performance Efficiency

      General Best Practice Capability Areas

      • Host
      • Network
      • Data
      • Identity Management
      • Cost/Subscription Management

      Assess cloud maturity

      2 hours

      1. Download a copy of the Cloud Maturity Assessment Tool.
      2. As a group, work through:
        • The balance of your operations activities from a Host/Build/Consume perspective. What are you responsible for delivering now? How do you expect things will change in the future?
        • Which workstreams to focus on. Are there activity categories that are critical or non-critical or that don’t represent a significant portion of overall work? Conversely, are there workstreams that you feel are subject to particular risk when moving to cloud?
      3. Fill out the Maturity Quiz tab in the Cloud Maturity Assessment Tool for the workstreams you have chosen to focus on.
      InputOutput
      • Insight into and experience with your current cloud environment.
      • Maturity scoring for key workload streams as they align to the pillars of a general well-architected cloud framework
      MaterialsParticipants
      • Whiteboard/Flip chart
      • Operating model template
      • Cloud platform SMEs

      Download theCloud Maturity Assessment Tool

      Identify the drivers for organizational redesign

      Whiteboard Activity

      An absolute must-have in any successful redesign is a shared understanding and commitment to changing the status quo.

      Without a clear and urgent call to action, the design changes will be seen as change for the sake of change and therefore entirely safe to ignore.

      Take up the following questions as a group:

      1. What kind of organizational change is needed?
      2. Why do we think the need for this change is urgent?
      3. What do we think will happen if no change occurs? What’s the worst-case scenario?

      Record your answers so you can reference and use them in the communication materials you’ll create in Phase 2.

      InputOutput
      • Cloud maturity assessment
      • Objectives and obstacles
      • Insight into existing challenges stemming from organizational design challenges
      • A list of reasons that form a compelling argument for organizational change
      MaterialsParticipants
      • Whiteboard/Flip chart
      • Cloud Operations Design Working Group

      “We know, for example, that 70 percent of change programs fail to achieve their goals, largely due to employee resistance and lack of management support. We also know that when people are truly invested in change it is 30 percent more likely to stick.”

      – Ewenstein, Smith, Sologar

      McKinsey (2015)

      Consider the value of change from advantage and obstacle perspectives

      Consider what you intend to achieve and the obstacles to overcome to help identify the changes required to achieve your desired future state.

      Advantage Perspective

      Ideas for Change

      Obstacle Perspective

      What advantages do cloud services offer us as an organization?

      For example:

      • Enhance service features.
      • Enhance user experience.
      • Provide ubiquitous access.
      • Scalability to align with demand.
      • Automate or outsource routine tasks.

      What obstacles prevent us from realizing value in cloud services?

      For example:

      • Inadequate stability and reliability
      • Difficult to observe or monitor workloads
      • Challenges ensuring cloud security
      • Insufficient access to relevant skills

      Review risks and challenges

      Changes to Support Model

      • Have we identified who is on the cloud ops team?
      • Do we know where we are procuring skills (internal IT vs. third party) and for how long?
      • Do we know where we are in the migration process?

      Changes to security & governance

      • Have we identified how our attack surface changes in the cloud?
      • Do we have guardrails in place to govern self-provisioning users?
      • Are we managing cost overage risks?

      Replicating old habits

      • Have we made concrete plans to leverage cloud capabilities to standardize and automate outputs?
      • Are we simply reproducing existing systems in the cloud?

      Changes to Skills & Roles

      • Is our staff excited to learn new skills and technologies? Are our specialists prepared to acquire generalist skills to support cloud services?
      • Do we have training plans created and aligned to our technology roadmap?
      • Do we know what head count we need?

      Misaligned stakeholders

      • Have we identified our key stakeholders and teams? Have we considered what changes will impact them and how?
      • Are we meeting regularly and collaborating effectively with our peers, or are we siloed?

      Review cloud objectives and obstacles

      Whiteboard Activity

      1 hour

      1. With your working group, review why you’re using cloud in the first place. What advantages do you expect to realize by adopting cloud services? If we achieve what we’ve set out to do, what should that look and feel like to us, our organization, and our organization’s customers?
        • You should have identified cloud drivers and objectives in your cloud vision and strategy – leverage and validate what you already have!
      2. Next, identify obstacles that are preventing you from fully realizing the value of cloud services.
      3. Finally, brainstorm initial ideas for change. What could we start doing that could help us better use cloud in the future? Are there changes to how we need to organize ourselves to collaborate more effectively?
      InputOutput
      • Insight into and experience with your current cloud environment
      • Identified key business outcomes you expect to realize by adopting cloud services
      • Identified challenges and obstacles that are preventing you from realizing key outcomes
      MaterialsParticipants
      • Whiteboard/Flip chart
      • Cloud operations design working group.

      Commonly cited advantages and obstacles

      Cloud Advantages/Objectives

      • Deliver faster on commitments to the business by removing infrastructure provisioning as a bottleneck.
      • Simplify capacity management on flexible cloud-based infrastructure.
      • Reduce capital spending on IT infrastructure.
      • Create sandboxes/innovation practices to experiment with and develop new functionality on cloud platforms.
      • Easily enable ubiquitous access to key corporate services.
      • Minimize the expense and effort required to maintain a data center – power & cooling, cabling, or physical hardware.
      • Leverage existing automation tools from cloud vendors to speed up integration and deployment.
      • Direct costs for specific services can improve transparency and cost allocation, allowing IT to directly “show-back” or charge-back cloud costs to specific cost centers.

      Obstacles

      Need to speed up provisioning of PaaS/IaaS/data resources to development and project teams.

      No time to develop and improve platform services and standards due to other responsibilities.

      We constantly run up unexpected cloud costs.

      Not enough time for continuous learning and development.

      The business will buy SaaS apps and only let us know after they’ve been purchased, leading to overlapping functionality; gaps in compliance, security, or data protection requirements; integration challenges; cost inefficiencies; and more.

      Role descriptions haven’t kept up with tech changes.

      Obvious opportunities to rationalize costs aren’t surfaced (e.g. failing to make use of existing volume licensing agreements).

      Skills needed to properly operate cloud solutions aren’t identified until breakdowns happen.

      Establish organization design principles

      You’ve established a need for organizational change. What will that change look like?

      Design principles are concise, direct statements that describe how you will design your organization to achieve key objectives and address key challenges.

      This is a critically important step for several reasons:

      • A set of clear, concise statements that describe what the design should achieve provides parameters that will help you create and evaluate different design options.
      • A focused, facilitated discussion to create those statements will help uncover conflicting assumptions between key stakeholders.
      • A comprehensive description of the various ways the organization should change makes it easier to identify misaligned or incompatible objectives.
      • A description of what your organization should look like in the future will help you identify where changes will be required .

      Examples of design principles:

      1. We will create a path to review and publish effective application/platform patterns.
      2. A single governing body should have oversight into all cloud costs.
      3. Development must happen only on approved cloud platforms.
      4. Application teams must address operational issues that derive from the applications they’ve created.
      5. Security practices should be embedded into approved cloud platforms and be automatically applied wherever possible.
      6. Focus is on improving developer experience on cloud platforms.

      Info-Tech Insight

      Design principles will often change as the organization’s strategy evolves.

      Align design principles to your objectives

      Developing design principles starts with your key objectives. What do we absolutely have to get right to deliver value through cloud services?

      Once you have your direction set, work through the points in the star model to establish how you will meet your objectives and deliver value. Each point in the star is an important element in your design – taken together, it paints a holistic picture of your future-state organization.

      The changes you choose to implement that affect capabilities, structure, processes, rewards, and people should be self-reinforcing. Each point in the star is connected to, and should support, the other points.

      “There is no one-size-fits-all organization design that all companies – regardless of their particular strategy needs – should subscribe to.”

      – Jay Galbraith, “The Star Model”

      The image contains a screenshot of a modified versio of Jay Galbraith's Star Model of Organizational Design.

      Establish design principles

      Track your findings in the table on the next slide.

      1. Review the cloud objectives and challenges from the previous activity. As a group, decide from that list: what are the key objectives you are trying to achieve? What are the things you absolutely must get right to get value from cloud services?
      2. Work through the following questions as a group:
        • What capabilities or technologies do we need to adopt or leverage differently?
        • How must our structure change? How will power shift in the new structure?
        • Will our new structure require changes to processes or information sharing?
        • How must we change how we motivate or reward employees?
        • What new skills or knowledge is required? How will we acquire those skills or knowledge?
      InputOutput
      • Cloud objectives and challenges
      • Different viewpoints into how your organization must change to realize objectives and overcome challenges
      • Organizational design principles for cloud operations
      MaterialsParticipants
      • Whiteboard/Flip charts
      • Cloud operations design working group

      Design principles (example)

      What is our key objective?

      • Rapidly develop innovative cloud services aligned to business value.

      What capabilities or technologies do we need to adopt or leverage differently?

      • We will adopt more agile development techniques to make smaller changes, faster.
      • We will standardize and automate tasks that are routine and repeatable.

      How must our structure change? How will power shift in the new structure?

      • Embed development teams within business units to better align to business unit needs.
      • Create a focused cloud platform team to develop infrastructure services.

      Will our new structure require changes to processes or information sharing?

      • Development teams will take on responsibility for application support.
      • Platform teams will be deeply embedded with development teams on new projects to build new infrastructure functionality.

      How must we change how we motivate or reward employees?

      • We will highlight innovative work across the company.
      • We will encourage experimentation and risk-taking.

      What new skills or knowledge is required, and how will we acquire it?

      • We will focus on acquiring skills most closely aligned to our technology roadmap.
      • We will ensure budget is available for training employees who ask for it.
      • We will contract to find skills we cannot develop in-house and use engagements as an opportunity to learn internally.

      Step 1.2: Evaluate new ways of working

      Participants

      Cloud Operations Design Working Group

      Outcomes

      Shared understanding of the horizon of work possibilities:

      • Ways to work
      • Ways to govern and learn

      Consider the different approaches on the following slides, how they change operational work, and decide which approaches are the right fit for you.

      Evaluate new ways of working

      Cut through the hype

      • There are new approaches/ways of working that deal head on with the persistent breakdowns and headaches that come with operations management – work thrown over the wall from development, manual and repetitive work, siloed teams, and more.
      • Many of these approaches emphasize an operations-aware approach to solutions development and apply techniques traditionally associated with AppDev to Operations.
      • Cloud services present opportunities to outsource/automate away routine tasks.

      “DevOps is a set of practices, tools, and a cultural philosophy that automates and integrates the processes between software development and IT teams. It emphasizes team empowerment, cross-team communication and collaboration, and technology automation.”

      – Atlassian, “DevOps”

      “ITIL 4 brings ITIL up to date by…embracing new ways of working, such as Lean, Agile, and DevOps.”

      – ITIL Foundation: ITIL 4 Edition

      “Over time, left to their own devices, the SRE team should end up with very little operational load and almost entirely engage in development tasks, because the service basically runs and repairs itself.”

      – Ben Treynor Sloss, “Site Reliability Engineering”

      The more things change, the more they stay the same:

      • Core processes remain, but they may be done differently, and new technologies and services create new challenges.
      • Not all approaches are right for all organizations, and what’s right for you depends on how you use cloud services.
      • The best solution draws from these management ideas to build an approach to operations that is right for you.

      Leverage patterns to think about new ways of approaching operations work

      Patterns are strategies, approaches, and philosophies that can help you imagine new ways of working in your own organization.

      • The following slides provide an overview of organizing patterns that are applicable to cloud operations.
      • These are strategies that have been applied successfully elsewhere. Review what they can and cannot do and decide whether they are something you can use in your own organizational design.
      • Not every pattern will apply to every organization. For example, an organization which typically consumes SaaS applications will likely have very little need for SRE approaches and techniques.

      Ways to work

      • What work do we do? What skills do we need?
      • How do we create and support systems?

      Ways to govern and learn

      • How do we set and enforce rules?
      • How do we create and share knowledge?

      Explore Applicable Patterns

      Ways to work

      Ways to govern and learn

      1. DevOps

      2. Site Reliability Engineering

      3. Platform Engineering

      4. Cloud Centre of Excellence

      5. Cloud Community of Practice

      What is DevOps?

      “Look for obstacles constantly and treat them as opportunities to experiment and learn.” – Jez Humble, et al. Lean Enterprise: How High Performance Organizations Innovate at Scale

      What it is NOT

      What it IS

      Why Use It

      • Another word for automation or CI/CD tools.
      • A specific role.
      • A fix-all to address friction between existing siloed application and development teams.
      • An approach that will be successful without getting the basics right first.
      • The right fit for every IT organization or every team.

      An operational philosophy that seeks to:

      • Converge accountability for development and operations to align all teams to the goal of delivering customer value.
      • Improve the relationship between Development and Operations teams.
      • Increase the rate of deployment of valuable functionality into production.
      • “A cultural shift giving development teams more control over shipping code to production.” 1
      • You’re doing a lot of custom development.
      • There are opportunities for operations and development teams to work more closely.
      • You want to improve coding quality and throughput.
      • You want to shift the culture of the team to focus on customer value rather than exclusively uptime or new features.
      1 DevOps, SRE, and Platform Engineering

      What is Site Reliability Engineering (SRE)?

      “Hope is not a strategy” – Benjamin Treynor Sloss, Site Reliability Engineering: How Google Runs Production Systems

      What it is NOT

      What it IS

      Why Use It

      • Deeply focussed on a specific technical domain; SRE work “does not discriminate between infrastructure, software, networking, or platforms.” 2
      • A different name for a team of sysadmins.
      • A programming framework or a specific set of technologies.
      • A way to manage COTS software. SRE is less useful when you’re using applications out-of-the-box with minimal customization, integration, or development.
      • An application of skills and approaches from software engineering to improve system reliability.
      • A team responsible for “availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning.”3
      • A team responsible for building systems that become “a platform and workflow that encompasses monitoring, incident management, eliminating single points of failure, [and] failure mitigation.”1
      • You are building services and providing them at scale.
      • You want to improve reliability and reduce “the frequency and impact of failures that can impact the overall reliability of a cloud application.”1
      • You need to define related service metrics and SLOs.
      • To increase the use of automation in operations to avoid mistakes and minimize toil. 3
      1 SRE vs Platform Engineering
      2. Lakhani, Usman. “ISite Reliability Engineering: What Is It? Why Is It Important for Online Businesses?,” 2020.
      3. Sloss, “Introduction,” 2017

      What4 is Platform Engineering?

      “Platform engineers can act as a shield between developers and the infrastructure”

      – Carlos Schults, “What is Platform Engineering? The Concept Behind the Term”

      What it is NOT

      What it IS

      Why Use It

      • A team that manages every aspect of each application on a particular platform.
      • Focussed solely on platform reliability and availability.
      • A different name for a team of sysadmins.
      • Needed for all cloud service deployments. Platform engineers are most useful when you’re building extensively on a particular platform (e.g. AWS, Azure, or your internal cloud).
      • Platform engineers design, build, and manage the infrastructure that supports and hosts work done by developers.
      • The work done by platform engineering allows developers to avoid the repetitive work of setting everything up anew each time.
      • Requires engineers with a deep understanding of cloud services and other platform technologies (e.g. Kubernetes).
      • The big public cloud platforms are built for everyone. You need platform engineering when you need to extensively adapt or manage standard cloud services to support your own requirements.
      • Platform engineers are responsible for creating a secure, stable, maintainable environment that enables developers to do their work faster and without having to manage the underlying technology infrastructure.
      1 DevOps, SRE, and Platform Engineering

      What is a Cloud Center of Excellence?

      You need a strong core to grow a cloud culture.

      What it is NOT

      What it IS

      Why Use It

      • A project management office (PMO) for cloud services.
      • An easy, quick, or temporary fix to cloud governance problems. The CCoE requires champions who provide ongoing support to realize value over time.
      • An approach that’s only for enterprise-sized IT organizations.
      • A standing meeting – members of the CCoE may meet regularly to review progress on their mandate, but work and collaboration need to happen outside of meetings.
      • A cross-functional team responsible for oversight of all cloud initiatives, including architectural, technical, security, financial, contractual, and operational aspects of planned and deployed solutions.
      • The CCoE’s responsibilities typically include governance and continuous improvement; alignment between technical and accounting practices; documentation, training, best practices and standards development; and vendor management.
      • CCoE duties are often part of an existing role rather than a full-time responsibility.
      • You want to enable a core group of cloud experts to promote collaboration and accelerate adoption of cloud services, including members from infrastructure, applications, and security.
      • You need to manage cloud risks, set guidelines and policies, and govern costs across cloud environments.
      • There is an unmet need for training, knowledge sharing, and best practice development across the organization.

      What is a Cloud Community of Practice?

      “We have to stop optimizing for programmers and start optimizing for users”

      – Jeff Atwood

      What it is NOT

      What it IS

      Why Use It

      • A replacement for effective oversight and governance practices, though they may help users navigate and understand governance requirements.
      • A way to advertise cloud to potential new practitioners – engaged members of a CoP are typically already using a particular service.
      • Always exclusively composed of internal staff; in certain cases, a CoP could have external members as well.
      • A network of engaged users and experts who share knowledge and best practices for related technologies, crowdsource solutions to problems, and suggest improvements.
      • Often supported by communication and collaboration tools (e.g. chat channels, knowledge base, forums). May use a range of techniques (e.g. drop-ins, vendor-led training, lunch and learns).
      • Communities of practice may be deliberately created by the organization or develop organically.
      • Communities of practice are an effective way for practitioners to support one another and share ideas and solutions.
      • A CoP can help “shift left” work and help practitioners help themselves.
      • An engaged CoP can help IT to identify improvement opportunities and can also be a channel to communicate updates or changes to practitioners.

      Reinforce what we mean by patterns

      Patterns are . . .

      Ways of Working

      • Sets of habits, processes, and methodologies you want to adopt as part of your operational guidelines and commonly agreed upon definitions.

      Patterns are also . . .

      Ways to Govern and Learn

      • The formal and informal practices and groups that focus on enabling governance, risk management, and adoption.

      Review the implications of each pattern for organizational design

      Ways of Working

      DevOps

      Development teams take on operational work to support the services they create after they are launched to production.

      Some DevOps teams may be aligned around a particular function or product rather than a technology – there are individuals with skills on a number of technologies that are part of the same team.

      Site Reliability Engineering (SRE)

      In the beginning, you can start to adopt SRE practices within existing teams. As demand grows for SRE skills and services, you may decide to create focused SRE roles or teams.

      SRE teams may work across applications or be aligned to just infrastructure services or a particular application, or they may focus on tools that help developers manage reliability. SREs may also be embedded long-term with other teams or take on an internal consulting roles with multiple teams.1

      Platform Engineering

      Platform engineering will often, though not always, be the responsibility of a dedicated team. This team must work very closely with, and tuned into the needs of, its internal customers. There is a constant need to find ways to add value that aren’t already part and parcel of the platform – or its external roadmap.

      This team will take on responsibility for the platform, in terms of feature development, automation, availability and reliability, security, and more. They may also be internal consultants or advisors on the platform to developers.

      1. Gustavo Franco and Matt Brown, “How SRE teams are organized and how to get started.”

      Review the implications of each pattern for organizational design

      Ways to Govern and Learn

      Cloud Center of Excellence

      • A CCoE is a cross-functional group with technical experts from security, infrastructure, applications, and more.
      • There should, ideally, be someone focused on leading the CCoE full-time – often someone with an architecture background. Team members may work on the CCoE part-time alongside their main role, and dedicate more of their time to the CCoE as needed.
      • As the CCoE is a governance function, it will typically bridge and sit above teams working on cloud services, reporting to the CIO, CTO, or to an architecture function.

      Cloud Community of Practice

      • Participation in a community of practice is often above and beyond a core role – it’s a leadership activity taken on by technologically adept experts with a drive to help others.
      • Some organizations will create a role to foster community collaboration, run events, raise opportunities and issues identified by the community with product or technology teams, manage collaboration tools, and more.

      Evolve your organization to meet the needs of increased adoption

      Your operating model should evolve as you increase adoption of cloud services.

      Least Adoption Greatest Adoption

      Initial Adoption

      Early Centralization

      Scaling Up

      Full Steam Ahead

      • One or more small agile teams design, build, manage, and operate individual solutions on cloud resources. Solutions provide early value, and identify new opportunities using small, safe-to-fail experiments.
      • Governance is likely done locally to each team. Knowledge sharing, guidelines, and standards are likely informal.
      • Early experience with cloud services help the organization identify where to invest in cloud services to best meet business demands.
      • Accountability and governance over the platform are more clearly defined, possibly still separate from core IT governance processes. Best practices may be shared across teams through a Community of Practice.
      • Operations may be centralized, where valuable, to support monitoring and incident response.
      • Additional product/service-aligned development teams are created to keep up with demand.
      • There is a focused effort to consolidate best practices and platform knowledge, which can be supported through a culture of learning, effective automation, and appropriate tools.
      • The CCoE takes on additional roles in cloud governance, security, operations, and administration.
      • The organization has reached a relatively steady-state for cloud adoption. Innovation and new service development takes place on a stable platform.
      • A Cloud Center of Excellence is accountable for cloud governance across the organization.
      Adapted from Microsoft, “Get Started: Align your organization,” 2021

      Choose new ways of working that make sense for your team

      1 hour

      Consider if, and how, the approaches to management and governance you’ve just reviewed can offer value to your organization.

      1. List the organizing/managing ideas listed in the previous slides in the table below.
      2. Define why it’s for you. What benefits do you expect to realize? What challenges do you expect this will help you overcome? How does this align with your key benefits and drivers for moving to cloud?
      3. List risks or challenges to adoption. Why will it be hard to do? What could get in the way of adoption? Why might it not be a good fit?
      4. Identify next steps to adopt proposed practices.

      Why it’s for us (drivers)

      Risks or challenges to adoption

      Next steps to build/adopt it

      CCoE

      DevOps

      InputOutput
      • Related Info-Tech slides on new ways of working.
      • Opportunities and challenges in your own cloud deployment that may be addressed through new ways of working.
      • Identify new ways of working aligned to your goals.
      MaterialsParticipants
      • Whiteboard/Flip chart
      • Cloud Operations Design Working Group

      Step 1.3: Identify cloud work

      Participants

      • Operations Design Working Group

      Outcomes

      • Identify core work required to deliver value in key cloud workstreams.

      “At first, for many people, the cloud seems vast. But what you actually do is carve out space.”

      –DevOps Manager

      Identify work

      Before you can identify roles and responsibilities, you have to confirm what work you do as an organization and how that work enables you to meet your goals.

      • A comprehensive approach that connects the work you do to your organizational goals will help you identify work that’s falling through the cracks.
      • Identifying work is an opportunity to look at the tasks you regularly execute and ensure they actually drive value.
      • Working through the exercise as a group will help you develop a common language around the work you do.
      • To make the evident obvious: you can’t decide who should be responsible for something if you don’t know about it in the first place.

      Defining work can be a lot of … work! We recommend you start by identifying work for the workstream you do most – Build, Consume, or Host – to focus your efforts. You can repeat the exercise as needed.

      Map work in workstream diagrams

      The image contains a screenshot of the map work in workstream diagrams.

      The five Well-Architected Framework pillars. These are principles/directions/guideposts that should inform all cloud work.

      The work being done to achieve the workstream target. These are roughly aligned with the three streams on the right.

      Workstream Target: A concise statement of the value you aim to achieve through this workstream. All work should help deliver value (directly or indirectly).

      Define the scope of the exercise

      Whiteboard Activity

      20 minutes

      Over the next few exercises, you’ll do a deep dive into the work you do in one specific workstream. In this exercise, we’ll decide on a workstream to focus on first.

      1. Are you primarily building, hosting on, or consuming cloud services? Start with the workstream where you’re doing the most work.
      2. If this isn’t sufficient to narrow your focus, look at the workstream that is most closely tied to mission critical applications, or that is most in need of review in terms of what work is done and who does it.
      3. You can narrow the scope further if there’s a very specific sub-area that differs from the rest (e.g. managing your O365 environment vs. managing all SaaS applications).
      InputOutput
      • Insight into and experience with your current cloud environment.
      • Your completed cloud maturity assessment.
      • Identify one workstream where you’ll define work first.
      MaterialsParticipants
      • None
      • Cloud Operations Design Working Group

      Create a workstream target statement

      Whiteboard Activity

      30 minutes

      In this activity, come up with a short sentence to describe what all this work you do is building toward. The target statement helps align participants on why work is being done and helps focus the activity on work that is most important to achieving the target statement.

      Start with this common workstream target statement:

      “Deliver valuable, secure, available, reliable, and efficient cloud services.”

      Now, review and adjust the target statement by working through the questions below:

      1. Return to the earlier exercises in Phase 1.1 where you reviewed your key objectives for cloud services. Does the target statement align with what you’d identified previously?
      2. Who is the customer for the work you do? Would they see the target differently than you’ve described it?
      3. Can you be more specific? Are there value drivers that are more specific to your industry, organization, business functions, or products that are key to the value your customers receive from this workstream?
      InputOutput
      • Previous exercises.
      • Workstream target statement.
      MaterialsParticipants
      • Whiteboard/Flip chart
      • Cloud Operations Design Sketchbook
      • Cloud Operations Design Working Group

      Identify cloud work

      1-2 hours

      1. Use the workstream diagram template in the Cloud Operations Design Sketchbook, or draw the template out on a whiteboard and use sticky notes to identify work.
      2. Identify the workstream at the top of the slide. Update the template value statement on the right with the value statement you created in the previous exercise.
      3. Review one or more of the examples in the Cloud Operations Design Sketchbook to get a sense of the level of detail required for this exercise.

      Activity instructions continue on the next slide.

      Some notes to the facilitator:

      • Working directly from the Cloud Operations Design Sketchbook will save you time with transcription. Sharing the document with participants (e.g. via OneDrive) will allow you to collaborate and edit the document together in real-time.
      • Don’t worry about being too tidy for the moment, just get the information written down and you can clean up the diagram later.
      InputOutput
      • Previously identified design principles.
      • An understanding of the work done, and that needs to be done, in your cloud environment.
      • Identify the work that needs to be done to support your key cloud services workstream in the future.
      MaterialsParticipants
      • Cloud Operations Design Sketchbook
      • Whiteboard and sticky notes (optional)
      • Cloud Operations Design Working Group

      Identify cloud work (cont’d)

      4. Work together to identify work, documenting one work item per box. This should focus on future state, so record work whether it’s actually done today or not. Your space is limited on the sheet, so focus on work that is indispensable to delivering the value statement. Use the lists on the right as a reminder of key IT practice areas.

      5. As much as possible, align the work items to the appropriate row (Govern & Align, Design & Execute, or Validate, Support & Monitor). You can overlap boxes between rows if needed.

      Have you captured work related to:

      ITIL practices, such as:

      • Request management
      • Incident & problem management
      • Service catalog
      • Service level management
      • Configuration management

      Security-aligned practices, such as:

      • Identity & access management
      • Vulnerability management
      • Security incident management

      Financial practices, such as:

      • IT asset management
      • Cost management & budgeting
      • Vendor management
      • Portfolio management

      Data-aligned practices, such as:

      • Data integrations
      • Data governance

      Technology-specific tasks, such as:

      • Network, Server & Storage
      • Structured/unstructured DBs
      • Composite services
      • IDEs and compilers

      Other key practices:

      • Monitoring & observability
      • Continuous improvement
      • Testing & quality assurance
      • Training and knowledge management
      • Manage shadow IT

      Info-Tech Insight

      Cloud work is not just applications that have been approved by IT. Consider how unsanctioned software purchased by the business will be integrated and managed.

      Identify cloud work (cont’d)

      6. If you have decided to adopt any of the new ways of working outlined in Step 1.2 (e.g. DevOps, SRE, etc.) review the next slide for examples of the type of work that frequently needs to be done in each of those work models. Add any additional work items as needed.

      7. Consolidate boxes and clean up the diagram (e.g. remove duplicate work items, align boxes, clarify language).

      8. Do a final review. Is all the work in the diagram truly aligned with the value statement? Is the work identified aligned with the design principles from Step 1.1?

      If you used a whiteboard for this exercise, transcribe the output to a copy of the Cloud Operations Design Sketchbook, and repeat the exercise for other key workstreams. You will use this diagram in Phase 2.

      Examples of work

      Examples of work in the "Host" workstream:

      • Bulk patch servers
      • Add a server
      • Add capacity
      • Develop a new server template
      • Incident management

      Examples of work in the "Build" workstream:

      • Provision a production server
      • Provision a test environment
      • Test recovery procedures
      • Add capacity for a service
      • Publish a new pattern
      • Manage capacity/performance for a service
      • Identify wasted spend across services
      • Identify performance bottlenecks
      • Review and shut down idle/unneeded services

      Examples of work in the "Consume" workstream:

      • Conduct vendor risk assessments
      • Develop a standard evaluation matrix to compare solutions to existing or potential in-house offerings
      • Onboard a solution
      • Offboard a solution
      • Conduct a renewal
      • Review and negotiate a contract
      • Rationalize software titles

      Phase 2:

      Design the organization and communicate changes

      Phase 1

      Phase 2

      1.1 Establish operating model design principals by identifying goals & challenges, workstreams, and cloud maturity

      1.2 Evaluate new ways of working

      1.3 Identify cloud work

      2.1 Draft an operating model

      2.2 Communicate proposed changes

      Phase Outcomes:

      Draft your cloud operations diagram, identify key messages and impacts to communicate to your stakeholders, and build out the Cloud Operations Organizing Framework communication deck.

      Step 2.1: Identify groups and responsibilities

      Participants

      • Operations Design Working Group

      Outcomes

      • Cloud Operations Diagram
      • Success Indicators
      • Roadmap

      “No-one ever solved a problem by restructuring.”

      – Anonymous

      Visualize your cloud operations

      Create a visual to help you abstract, analyze, and clarify your vision for the future state of your organization in order to align and instruct stakeholders.

      Create a visual, high-level view of your organization to help you answer questions such as:

      • “What work do we do? What are the roles and responsibilities of different teams?”
      • “How do we interact between work areas?”
      • “How has our organization changed already, and what additional changes may be needed?”
      • “How do we make technology decisions?”
      • “How do we provide services?”
      • “How might this change be received by people on the ground?”
      The image contains a screenshot of the Cloud Operations Diagram Example.

      Decide whether to centralize or decentralize

      Specialization & Focus: A group or work unit developing a focused concentration of skills, expertise, and activities aligned with an area of focus (such as the ones at right).

      Decentralization: Operational teams that report to a decentralized IT or business function, either directly or via a “dotted line” relationship.

      Decentralization and Specialization can:

      • Duplicate work.
      • Localize decision-making authority, which can increase agility and responsiveness.
      • Transfer authority and accountability to local and typically smaller teams, clarifying responsibilities and encouraging staff to take ownership for service delivery.
      • Enable the team to focus on complex and rapidly changing technologies or processes.
      • Create islands of expertise, which can get in the way of collaboration, innovation, and decision making across groups and work units and make oversight difficult.
      • Complicate the transfer of resources and knowledge between groups.

      Examples: Areas of Focus

      Business unit

      • Manufacturing
      • R&D
      • Sales & Marketing

      Region

      • Americas
      • EMEA
      • APAC

      Service

      • ERP
      • Commercial website

      Technology

      • On-premises servers/storage
      • Network
      • Cloud services

      Operational process focus

      • Capacity management & planning
      • Incident management
      • Problem management

      “The concept of organization design is simple in theory but highly complex in practice. Like any strategic decision, it involves making multiple trade-offs before choosing what is best suited to a business context.”

      – Nitin Razdan & Arvind Pandit

      Identify key work areas

      Balance specialization with effective collaboration

      • Much is said about breaking down organizational silos. But at some level, silos are inevitable – any company with more than one employee will have to divide work up somehow.
      • Dividing up work is a delicate balancing act – ensuring individuals and groups are able to do work that is related, meaningful, and that allows autonomy while allowing for effective collaboration between groups that need to work together to achieve business goals.

      Why “work areas”?

      Why don’t we just use teams, groups, squads, or departments, or some other more common term for groups of people working together?

      • We are not yet at the point of deciding who in the organization should be aligned to which areas in the design.
      • Describing work areas as teams can shift the conversation to the organizational chart – to who does the work, rather than what needs to be done.

      That’s not the goal of this exercise. If the conversation gets stuck on what you do today, it can get in the way of thinking about what you need to do in the future.

      Create a future-state cloud operations diagram

      1-3 hours

      1. Review the example cloud operations diagram example in your copy of the Cloud Operations Design Sketchbook.
      2. Identify key work areas (e.g. applications, infrastructure, platform engineering, DevOps, security). Add the name of each work area in one of the larger boxes.
        • Go back to your design principles. Did you define any work areas in your design principles that should be represented here?
        • If you have several groups or teams with similar responsibilities, consider lumping them together in one box (e.g. applications teams, 3x DevOps teams).
      3. Copy the tasks from any workstream diagrams you’ve created to the same slide as the organization design diagram. Keep the workstream diagram intact, as you’ll want to be able to refer back to it later.

      Activity instructions continue on the next slide.

      InputOutput
      • Insight into and experience with your current cloud environment.
      • Cloud Operations Diagram
      MaterialsParticipants
      • Whiteboard/Flip charts
      • Cloud Operations
      • Cloud Operations Design Working Group

      Cloud operations diagram (cont’d)

      1-3 hours

      4. As a group, move the work boxes from the workstream diagram into the appropriate work area.

      • Don’t worry about being too tidy for the moment – clean up the diagram when the exercise is done.
      • Make adjustments to the wording of the work boxes if needed.

      5. Use the space between work areas to describe how work areas must interact to achieve organizational goals. For example:

      • What information should be shared between groups?
      • What information sharing channels may be used?
      • What processes will be handed-off between groups and how?
      • How often will teams interact?
      • Will interactions be formal or informal?

      Create a current-state operations diagram

      1 -2 hours

      This exercise can be done by one person, then reviewed with the working group at a later time.

      This current state diagram helps clarify the changes that may need to happen to get to your future state.

      1. Color code the work boxes for each work area. For example, if you have a “DevOps” work area, make all the work boxes assigned to “DevOps” the same color.
      2. On a separate slide, sketch your existing organization indicating your current teams.
      3. Copy the tasks from the future-state diagram to this current-state chart. Align the tasks to the appropriate groups.
      4. Review the chart with the working group. Discuss: are there teams that are doing work today that will also be done by different teams? Are there groups that may merge into one team? What types of changes may be required?
      InputOutput
      • Future-state cloud operations diagram
      • Current-state cloud operations diagram
      MaterialsParticipants
      • Cloud Operations Design Sketchbook
      • Projector/screen/virtual meeting
      • Project lead
      • Cloud Operations Design Working Group

      Check for biases to make better choices

      Use the strategies below to spot and address flaws in your team’s thinking about your future-state design.

      Biases

      What’s the risk?

      Mitigation strategies

      Is the team making mistakes due to self-interest, love of a single idea, or groupthink?

      Important information may be ignored or left unspoken.

      Rigorously check for the other biases, below. Tactfully seek dissenting opinions.

      Do recommendations use unreasonable analogies to other successes or failures?

      Opportunities or challenges in the current situation may not be sufficiently understood.

      Ask for other examples, and check whether the analogies are still valid.

      Is the team blinkered by the weight of past decisions?

      Doubling-down on bad decisions (sunk costs) or ignoring new opportunities.

      Ask yourself what you'd do if you were new to the position or organization.

      Does the data support the recommendations?

      Data used to make the case isn't a good fit for the challenge, is based on faulty assumptions, or is incomplete.

      If you had a year to make the decision, what data would you want? How much can you get?

      Are there realistic alternative recommendations?

      Alternatives don't exist or are "strawman" options.

      Ask for additional options.

      Is the recommendation too risk averse or cautious?

      Recommendations that may be too risky are ignored, leading to missed opportunities.

      Review options to accept, transfer, distribute, or mitigate the risk of the decision.

      Framework above adapted from Kahneman, Lovallo, and Sibony (2011)

      Be specific with metrics

      Thinking of ways you could measure success can help uncover what success actually means to you.

      Work collectively to generate success indicators for each key cloud initiative. Success indicators are metrics, with targets, aligned to goals, and if you are able to measure them accurately, they should help you report your progress toward your objectives.

      For example, if your driver is “faster access to resources” you might consider indicators like developer satisfaction, project completion time, average time to provision, etc.

      There are several reasons you may not publicize these metrics. They may be difficult to calculate or misconstrued as targets, warping behavior in unexpected ways. But managed properly, they have value in measuring operational success!

      Examples: Operations redesign project metrics

      Key stakeholder satisfaction scores

      IT staff engagement scores

      Support Delivery of New Functionality

      Double number of accepted releases per cycle

      80% of key cloud initiatives completed on time, on budget, and in scope

      Improve Operational Effectiveness

      <1% of servers have more than two major versions out of date

      No more than one capacity-related incident per Q

      Define success indicators

      Whiteboard Activity

      45 minutes

      1. On a whiteboard, draw a table with key objectives for the design across the top.
        • What cloud objectives should the redesign help you achieve? Refer back to the design principles from Phase 1.
        • Think about the redesign itself. How will you measure whether the project itself is proceeding according to plan? Consider metrics such as employee engagement scores and satisfaction scores from key stakeholders.
      2. Consider whether the metrics are feasible to track. Record your decisions in your copy of the Cloud Operations Organizing Framework deck.
      InputOutput
      • Key design goals
      • Success indicators for your design
      MaterialsParticipants
      • Whiteboard
      • Markers
      • Cloud Operations Design Working Group

      Populate a roadmap

      Tool Activity

      45 minutes

      1. In the Roadmap Tool, populate the data entry tab with the initiatives you will take to support changes toward the new cloud operations organizing framework.
      2. Input each of the tasks in the data entry tab and provide a description and rationale behind the task (as needed).
      3. Assign an effort, priority, and cost level to each task (high, medium, low).
      4. Assign an owner to each task – someone who can take points and shepherd the task to completion.
      5. Identify the timeline for each task based on the priority, effort, and cost (short, medium, and long term).
      6. Highlight risk for each task if it will be deferred.
      7. Track the progress of each task with the status column.
      InputOutput
      • Cloud Operations Organizing Framework
      • Roadmap/ implementation plan
      MaterialsParticipants
      • Roadmap Tool
      • Cloud Operations Design Working Group

      Download the Roadmap Tool

      Step 2.2: Communicate changes

      Participants

      • Operations Design Working Group

      Outcomes

      • Build a communication plan for key stakeholders
      • Complete the communication deck Cloud Operations Organizing Framework
      • Build a roadmap

      “Words, words, words.”

      – Shakespeare

      Communicate changes

      Which stakeholders will be affected by the changes?

      Decision makers: Who do you ultimately need to convince to proceed with any changes you’ve outlined?

      Peers: How will managers of other areas be affected by the changes you’re proposing? If you are you suggesting changes to the way that they, or their teams, do their work, you will have to present a compelling case that there’s value in it for them.

      Staff: Are you dictating changes or looking for feedback on the path forward?

      The image contains a screenshot of the Five Elements of Change that is displayed in a cycle. The five elements are: What is the change? Why are we doing it? How are we going to go about it? How long will it take us? What is the role of each team and individual.

      Source: The Qualities of Leadership: Leading Change

      Follow these guidelines for good communication

      Be relevant

      • Talk about what matters to each stakeholder group.
      • Talk about what matters to the initiative.
      • IT thinks in processes but stakeholders only care about results: talk in terms of results.
      • IT wants to be “understood” but this does not matter to stakeholders; think “what’s in it for them?”
      • Communicate truthfully; do not make false promises or hide bad news.
      • If you expect objections, create a plan to handle them.

      Be clear

      • Lead with the point you’re trying to make.
      • Don’t use jargon.
      • Avoid idiomatic language and clichés.
      • Have a third party review draft communications and ask them to tell you the key messages in their own words. If they’re missing the main points, there’s a good chance the draft isn’t clear.

      Be consistent

      • Ensure the core message is consistent regardless of audience, channel, or medium.
      • Changing the core message from one group to another can be interpreted as incompetence or an attempt at deception. This will damage your credibility and can lead to a loss of trust.

      Be concise

      • Get to the point.
      • Minimize word count wherever possible.

      “We tend to use a lot of jargon in our discussions, and that is a sure fire way to turn people away. We realized the message wasn’t getting out because the audience wasn’t speaking the same language. You have to take it down to the next level and help them understand where the needs are.”

      – Jeremy Clement, Director of Finance, College of Charleston

      Create a communication plan

      1 hour

      Fill out the table below.

      Stakeholder group: Identify key stakeholders who may be impacted by changes to the operations team. This might include IT leadership, management, and staff.

      Benefits: What’s in it for them?

      Impact: What are we asking in return?

      How: What mechanisms or channels will you use to communicate?

      When: When (and how often) will you get the message out?

      Benefits

      Impact

      How

      When

      IT Mgrs.

      • Improve agility, stability
      • Deliver faster against business goals
      • Respond to identified needs
      • Improve confidence in IT
      • Must support the process
      • Change and engagement issues during restructuring may affect staff engagement and productivity
      • Training budget required
      • Present at leadership meeting
      • Kick-off email
      • Sept. leadership meeting
      • Weekly touchpoints
      • Informally throughout project

      Ops Staff

      • Clearer direction and clear priorities (Operations mission statement and RACI)
      • Higher-value work – address problems, contribute to plans
      • New skills and training
      • More personal accountability
      • Push toward process consistency
      • Must make time and plan for training during work hours
      • Present at operations team’s offsite meeting
      • AMA channel on Slack
      • 1:1 meetings
      • Add RACI, org. sketch to shared folder
      • Operations offsite
      • Sept. all-hands meeting
      • Ongoing coaching and informal conversations
      InputOutput
      • Discussion
      • Communication Plan
      MaterialsParticipants
      • Whiteboard/Flip Chart
      • Cloud Operations Design Working Group

      Download the Communication Plan Template

      Support the transition with a plan to acquire skills

      Identify the preferred way to acquire needed skill sets: contracting, outsourcing, training, or hiring.

      • Some cloud projects will change the demand for some skills in the organization, and not all skills should be cultivated internally. Uncertainty about future skills and jobs will cause anxiety for your team and can lead to employee exit.
      • Use Info-Tech’s research to conduct a demand analysis to identify which new and critical skills should be acquired via training or hiring (rather than outsourcing or contracting).
      • Create a roadmap to clarify when training needs to be completed, a budget plan that accounts for training costs, and role descriptions that paint a picture of future work.
      • Within the confines of a collective agreement, managers may be required to retrain staff into new roles before those staff are required to do work in their new jobs. Failing to plan can be more consequential.
      • Remember that in cloud, a wealth of automation opportunities present a great option for offloading tasks as well!

      Info-Tech Insight

      Identify skills requirements and gaps as early as possible to avoid skills gaps later. Whether you plan to acquire skills via training or cross-training, hiring, contracting, or outsourcing, effectively building skills takes time. Use Info-Tech’s methodology to address skills gaps in a prioritized and rational way.

      Involve HR for implementation

      Your HR team should help you work through:

      • Which staff and managers will move to which roles, and any headcount changes.
      • Job descriptions, performance metrics, career paths, compensation, and succession planning.
      • Organizational change management and implementation plans.

      When do you need to involve HR?

      Role changes will result in job description changes.

      • New or changed job descriptions need to be evaluated for impact on pay, title, exempt status, career pathing, and more.
      • This is especially true in more traditional or unionized organizations that require specific and granular job descriptions of responsibilities.
      • Changed jobs will likely require union review and approval.

      You anticipate changes to the reporting structure.

      • Work with HR to develop a transition plan including communications, training to new managers, and support to new teams.

      You anticipate redundancies.

      • Your HR department can prepare you for difficult discussions, help you navigate labor laws, and support the offboarding process.

      You anticipate new positions.

      • Recruitment and hiring takes time. Give HR advance notice to support recruitment, hiring, and onboarding to ensure you hire the right people, with the right skills, at the right time.

      Training and development budget is required.

      • If training is a critical part of the onboarding process, don’t just assume funding is available. Work with HR to build your case.

      Related Info-Tech Research

      Define Your Cloud Vision

      Define your cloud vision before it defines you.

      Document Your Cloud Strategy

      Drive consensus by outlining how your organization will use the cloud.

      Map Technical Skills for a Changing Infrastructure & Operations Organization

      Be practical and proactive – identify needed technical skills for your future-state environment and the most efficient way to acquire them.

      Bibliography

      “2021 GitLab DevSecOps Survey.” Gitlab, 2021.
      “2022 State of the Cloud Report.” Flexera, 2022.
      “DevOps.” Atlassian, ND. Web. 21 July 2022.
      Atwood, Jeff. “The 2030 Self-Driving Car Bet.” Coding Horror, 4 Mar 2022. Web. 5 Aug 2022.
      Campbell, Andrew. “What is an operating model?” Operational Excellence Society, 12 May 2016. Web. 13 July 2022.
      “DevOps.” Atlassian, ND. Web. 21 July 2022.
      Ewenstein, Boris, Wesley Smith, Ashvin Sologar. “Changing change management” McKinsey, 1 July 2015. Web. 8 April 2022.
      Franco, Gustavo and Matt Brown. “How SRE teams are organized, and how to get started.” Google Cloud Blog, 26 June 2019. Web. July 13 2022.
      “Get started: Build a cloud operations team.” Microsoft, 10 May 2021.
      ITIL Foundation: ITIL 4 Edition. Axelos, 2019.
      Humble, Jez, Joanne Molesky, and Barry O’Reilly. Lean Enterprise: How High Performance Organizations Innovate at Scale. O’Reilly Media, 2015.
      Franco, Gustavo and Matt Brown. “How SRE teams are organized and how to get started.” 26 June 2019. Web. 21 July 2022.
      Galbraith, Jay. “The Star Model”. ND. Web. 21 July 2022.
      Kahnemanm Daniel, Dan Lovallo, and Olivier Sibony. “Before you make that big decision.” Harv Bus Rev. 2011 Jun; 89(6): 50-60, 137. PMID: 21714386.
      Kesler, Greg. “Star Model of Organizational Design.” YouTube, 1 Oct 2018. Web Video. 21 Jul 2022.
      Lakhani, Usman. “Site Reliability Engineering: What Is It? Why Is It Important for Online Businesses?” Info-Tech. Web. 25 May 2020.
      Mansour, Sherif. “Product Management: The role and best practices for beginners.” Atlassian Agile Coach, n.d.
      Murphy, Annie, Jamie Kirwin, Khalid Abdul Razak. “Operating Models: Delivering on strategy and optimizing processes.” EY, 2016.
      Shults, Carlos. “What is Platform Engineering? The Concept Behind the Term.” liatrio, 3 Aug 2021. Web. 5 Aug 2022.
      Sloss, Benjamin Treynor. Site Reliability Engineering Part I: Introduction. O’Reilly Media, 2017.
      “SRE vs. Platform Engineering.” Ambassador Labs, 8 Feb 2021.
      “The Qualities of Leadership: Leading Change.” Cornelius & Associates, n.d. Web.
      “Understand cloud operating models.” Microsoft, 02 Sept. 2022.
      Velichko, Ivan. “DevOps, SRE, and Platform Engineering.” 15 Mar 2022.

      Research Contributors and Experts

      Nenad Begovic

      Executive Director, Head of IT Operations

      MUFG Investor Services

      Desmond Durham

      Manager, ICT Planning & Infrastructure

      Trinidad & Tobago Unit Trust Corporation

      Virginia Roberts

      Director, Enterprise IT

      Denver Water

      Denis Sharp

      IT/LEAN Consultant

      Three anonymous contributors

      Build an IT Risk Taxonomy

      • Buy Link or Shortcode: {j2store}197|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: IT Governance, Risk & Compliance
      • Parent Category Link: /it-governance-risk-and-compliance
      • Business leaders, driven by the need to make more risk-informed decisions, are putting pressure on IT to provide more timely and consistent risk reporting.
      • IT risk managers need to balance the emerging threat landscape with not losing sight of the risks of today.
      • IT needs to strengthen IT controls and anticipate risks in an age of disruption.

      Our Advice

      Critical Insight

      A common understanding of risks, threats, and opportunities gives organizations the flexibility and agility to adapt to changing business conditions and drive corporate value.

      Impact and Result

      • Use this blueprint as a baseline to build a customized IT risk taxonomy suitable for your organization.
      • Learn about the role and drivers of integrated risk management and the benefits it brings to enterprise decision-makers.
      • Discover how to set up your organization up for success by understanding how risk management links to organizational strategy and corporate performance.

      Build an IT Risk Taxonomy Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Build an IT Risk Taxonomy – Develop a common approach to managing risks to enable faster, more effective decision making.

      Learn how to develop an IT risk taxonomy that will remain relevant over time while providing the granularity and clarity needed to make more effective risk-based decisions.

      • Build an IT Risk Taxonomy – Phases 1-3

      2. Build an IT Risk Taxonomy Guideline and Template – A set of tools to customize and design an IT risk taxonomy suitable for your organization.

      Leverage these tools as a starting point to develop risk levels and definitions appropriate to your organization. Take a collaborative approach when developing your IT risk taxonomy to gain greater acceptance and understanding of accountability.

      • IT Risk Taxonomy Committee Charter Template
      • Build an IT Risk Taxonomy Guideline
      • Build an IT Risk Taxonomy Definitions
      • Build an IT Risk Taxonomy Design Template

      3. IT Risk Taxonomy Workbook – A place to complete activities and document decisions that may need to be communicated.

      Use this workbook to document outcomes of activities and brainstorming sessions.

      • Build an IT Risk Taxonomy Workbook

      4. IT Risk Register – An internal control tool used to manage IT risks. Risk levels archived in this tool are instrumental to achieving an integrated and holistic view of risks across an organization.

      Leverage this tool to document risk levels, risk events, and controls. Smaller organizations can leverage this tool for risk management while larger organizations may find this tool useful to structure and define risks prior to using a risk management software tool.

      • Risk Register Tool

      Infographic

      Workshop: Build an IT Risk Taxonomy

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Review IT Risk Fundamentals and Governance

      The Purpose

      Review IT risk fundamentals and governance.

      Key Benefits Achieved

      Learn how enterprise risk management and IT risk management intersect and the role the IT taxonomy plays in integrated risk management.

      Activities

      1.1 Discuss risk fundamentals and the benefits of integrated risk.

      1.2 Create a cross-functional IT taxonomy working group.

      Outputs

      IT Risk Taxonomy Committee Charter Template

      Build an IT Risk Taxonomy Workbook

      2 Identify Level 1 Risk Types

      The Purpose

      Identify suitable IT level 1 risk types.

      Key Benefits Achieved

      Level 1 IT risk types are determined and have been tested against ERM level one risk types.

      Activities

      2.1 Discuss corporate strategy, business risks, macro trends, and organizational opportunities and constraints.

      2.2 Establish level 1 risk types.

      2.3 Test soundness of IT level 1 types by mapping to ERM level 1 types.

      Outputs

      Build an IT Risk Taxonomy Workbook

      3 Identify Level 2 and Level 3 Risk Types

      The Purpose

      Define level 2 and level 3 risk types.

      Key Benefits Achieved

      Level 2 and level 3 risk types have been determined.

      Activities

      3.1 Establish level 2 risk types.

      3.2 Establish level 3 risk types (and level 4 if appropriate for your organization).

      3.3 Begin to test by working backward from controls to ensure risk events will aggregate consistently.

      Outputs

      Build an IT Risk Taxonomy Design Template

      Risk Register Tool

      4 Monitor, Report, and Respond to IT Risk

      The Purpose

      Test the robustness of your IT risk taxonomy by populating the risk register with risk events and controls.

      Key Benefits Achieved

      Your IT risk taxonomy has been tested and your risk register has been updated.

      Activities

      4.1 Continue to test robustness of taxonomy and iterate if necessary.

      4.2 Optional activity: Draft your IT risk appetite statements.

      4.3 Discuss communication and continual improvement plan.

      Outputs

      Build an IT Risk Taxonomy Design Template

      Risk Register Tool

      Build an IT Risk Taxonomy Workbook

      Further reading

      Build an IT Risk Taxonomy

      If integrated risk is your destination, your IT risk taxonomy is the road to get you there.

      Analyst Perspective

      Donna Bales.

      The pace and uncertainty of the current business environment introduce new and emerging vulnerabilities that can disrupt an organization’s strategy on short notice.

      Having a long-term view of risk while navigating the short term requires discipline and a robust and strategic approach to risk management.

      Managing emerging risks such as climate risk, the impact of digital disruption on internal technology, and the greater use of third parties will require IT leaders to be more disciplined in how they manage and communicate material risks to the enterprise.

      Establishing a hierarchical common language of IT risks through a taxonomy will facilitate true aggregation and integration of risks, enabling more effective decision making. This holistic, disciplined approach to risk management helps to promote a more sustainable risk culture across the organization while adding greater rigor at the IT control level.

      Donna Bales
      Principal Research Director
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      Common Obstacles

      Info-Tech’s Approach

      IT has several challenges when managing and responding to risk events:

      • Business leaders, driven by the need to make more risk-informed decisions, are putting pressure on IT to provide more timely and consistent risk reporting.
      • Navigating today’s ever-evolving threat landscape is complex. IT risk managers need to balance the emerging threat landscape while not losing sight of the risks of today.
      • IT needs to strengthen IT controls and anticipate risks in an age of disruption.

      Many IT organizations encounter obstacles in these areas:

      • Ensuring an integrated, well-coordinated approach to risk management across the organization.
      • Developing an IT risk taxonomy that will remain relevant over time while providing sufficient granularity and definitional clarity.
      • Gaining acceptance and ensuring understanding of accountability. Involving business leaders and a wide variety of risk owners when developing your IT risk taxonomy will lead to greater organizational acceptance.

      .

      • Take a collaborative approach when developing your IT risk taxonomy to gain greater acceptance and understanding of accountability.
      • Spend the time to fully analyze your current and future threat landscape when defining your level 1 IT risks and consider the causal impact and complex linkages and intersections.
      • Recognize that the threat landscape will continue to evolve and that your IT risk taxonomy is a living document that must be continually reviewed and strengthened.

      Info-Tech Insight

      A common understanding of risks, threats, and opportunities gives organizations the flexibility and agility to adapt to changing business conditions and drive corporate value.

      Increasing threat landscape

      The risk landscape is continually evolving, putting greater pressure on the risk function to work collaboratively throughout the organization to strengthen operational resilience and minimize strategic, financial, and reputational impact.

      Financial Impact

      Strategic Risk

      Reputation Risk

      In IBM’s 2021 Cost of a Data Breach Report, the Ponemon Institute found that data security breaches now cost companies $4.24 million per incident on average – the highest cost in the 17-year history of the report.

      58% percent of CROs who view inability to manage cyber risks as a top strategic risk.

      EY’s 2022 Global Bank Risk Management survey revealed that Chief Risk Officers (CROs) view the inability to manage cyber risk and the inability to manage cloud and data risk as the top strategic risks.

      Protiviti’s 2023 Executive Perspectives on Top Risks survey featured operational resilience within its top ten risks. An organization’s failure to be sufficiently resilient or agile in a crisis can significantly impact operations and reputation.

      Persistent and emerging threats

      Organizations should not underestimate the long-term impact on corporate performance if emerging risks are not fully understood, controlled, and embedded into decision-making.

      Talent Risk

      Sustainability

      Digital Disruption

      Protiviti’s 2023 Executive Perspectives on Top Risks survey revealed talent risk as the top risk organizations face, specifically organizations’ ability to attract and retain top talent. Of the 38 risks in the survey, it was the only risk issue rated at a “significant impact” level.

      Sustainability is at the top of the risk agenda for many organizations. In EY’s 2022 Global Bank Risk Management survey, environmental, social, and governance (ESG) risks were identified as a risk focus area, with 84% anticipating it to increase in priority over the next three years. Yet Info-Tech’s Tech Trends 2023 report revealed that only 24% of organizations could accurately report on their carbon footprint.

      Source: Info-Tech 2023 Tech Trends Report

      The risks related to digital disruption are vast and evolving. In the short term, risks surface in compliance and skills shortage, but Protiviti’s 2023 Executive Perspectives survey shows that in the longer term, executives are concerned that the speed of change and market forces may outpace an organization’s ability to compete.

      Build an IT risk taxonomy: As technology and digitization continue to advance, risk management practices must also mature. To strengthen operational and financial resiliency, it is essential that organizations move away from a siloed approach to IT risk management wart an integrated approach. Without a common IT risk taxonomy, effective risk assessment and aggregation at the enterprise level is not possible.

      Blueprint benefits

      IT Benefits

      Business Benefits

      • Simple, customizable approach to build an IT risk taxonomy
      • Improved satisfaction with IT for senior leadership and business units
      • Greater ability to respond to evolving threats
      • Improved understanding of IT’s role in enterprise risk management (ERM)
      • Stronger, more reliable internal control framework
      • Reduced operational surprises and failures
      • More dynamic decision making
      • More proactive risk responses
      • Improve transparency and comparability of risks across silos
      • Better financial resilience and confidence in meeting regulatory requirements
      • More relevant risk assurance for key stakeholders

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

      IT Risk Taxonomy Committee Charter Template

      Create a cross-functional IT risk taxonomy committee.

      The image contains a screenshot of the IT risk taxonomy committee charter template.

      Build an IT Risk Taxonomy Guideline

      Use IT risk taxonomy as a baseline to build your organization’s approach.

      The image contains a screenshot of the build an it risk taxonomy guideline.

      Build an IT Risk Taxonomy Design Template

      Use this template to design and test your taxonomy.

      The image contains a screenshot of the build an IT risk taxonomy design template.

      Risk Register Tool

      Update your risk register with your IT risk taxonomy.

      The image contains a screenshot of the risk register tool.

      Key deliverable:

      Build an IT Risk Taxonomy Workbook

      Use the tools and activities in each phase of the blueprint to customize your IT risk taxonomy to suit your organization’s needs.

      The image contains a screenshot of the build an IT risk taxonomy workbook.

      Benefit from industry-leading best practices

      As a part of our research process, we used the COSO, ISO 31000, and COBIT 2019 frameworks. Contextualizing IT risk management within these frameworks ensures that our project-focused approach is grounded in industry-leading best practices for managing IT risk.

      COSO’s Enterprise Risk Management —Integrating with Strategy and Performance addresses the evolution of enterprise risk management and the need for organizations to improve their approach to managing risk to meet the demands of an evolving business environment.

      ISO 31000 – Risk Management can help organizations increase the likelihood of achieving objectives, improve the identification of opportunities and threats, and effectively allocate and use resources for risk treatment.

      COBIT 2019’s IT functions were used to develop and refine the ten IT risk categories used in our top-down risk identification methodology.

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

      Guided Implementation

      “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”

      Workshop

      “We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”

      Consulting

      “Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

      Diagnostics and consistent frameworks used throughout all four options

      Guided Implementation

      Phase 1 Phase 2 Phase 3

      Call #1: Review risk management fundamentals.

      Call #2: Review the role of an IT risk taxonomy in risk management.

      Call #3: Establish a cross-functional team.

      Calls #4-5: Identify level 1 IT risk types. Test against enterprise risk management.

      Call #6: Identify level 2 and level 3 risk types.

      Call #7: Align risk events and controls to level 3 risk types and test.

      Call #8: Update your risk register and communicate taxonomy internally.

      A Guided Implementation (GI) is a series

      of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is 6 to 8 calls over the course of 3 to 6 months.

      Workshop Overview

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889

      Day 1 Day 2 Day 3 Day 4 Day 5

      Review IT Risk Fundamentals and Governance

      Identify Level 1 IT Risk Types

      Identify Level 2 and Level 3 Risk Types

      Monitor, Report, and Respond to IT Risk

      Next Steps and
      Wrap-Up (offsite)

      Activities

      1.1 Discuss risk fundamentals and the benefits of integrated risk.

      1.2 Create a cross-functional IT taxonomy working group.

      2.1 Discuss corporate strategy, business risks, macro trends, and organizational opportunities and constraints.

      2.2 Establish level 1 risk types.

      2.3 Test soundness of IT level 1 types by mapping to ERM level 1 types.

      3.1 Establish level 2 risk types.

      3.2 Establish level 3 risk types (and level 4 if appropriate for your organization).

      3.3 Begin to test by working backward from controls to ensure risk events will aggregate consistently.

      4.1 Continue to test robustness of taxonomy and iterate if necessary.

      4.2 Optional activity: Draft your IT risk appetite statements.

      4.3 Discuss communication and continual improvement plan.

      5.1 Complete in-progress deliverables from previous four days.

      5.2 Set up review time for workshop deliverables and to discuss next steps.

      Deliverables
      1. T Risk Taxonomy Committee Charter Template
      2. Build an IT Risk Taxonomy Workbook
      1. Build an IT Risk Taxonomy Workbook
      1. IT Risk Taxonomy Design Template
      2. Risk Register
      1. IT Risk Taxonomy Design Template
      2. Risk Register
      3. Build an IT Risk Taxonomy Workbook
      1. Workshop Report

      Phase 1

      Understand Risk Management Fundamentals

      Phase 1

      Phase 2

      Phase 3

      • Governance, Risk, and Compliance
      • Enterprise Risk Management
      • Enterprise Risk Appetite
      • Risk Statements and Scenarios
      • What Is a Risk Taxonomy?
      • Functional Role of an IT Risk Taxonomy
      • Connection to Enterprise Risk Management
      • Establish Committee
      • Steps to Define IT Risk Taxonomy
      • Define Level 1
      • Test Level 1
      • Define Level 2 and 3
      • Test via Your Control Framework

      Governance, risk, and compliance (GRC)

      Risk management is one component of an organization’s GRC function.

      GRC principles are important tools to support enterprise management.

      Governance sets the guardrails to ensure that the enterprise is in alignment with standards, regulations, and board decisions. A governance framework will communicate rules and expectations throughout the organization and monitor adherence.

      Risk management is how the organization protects and creates enterprise value. It is an integral part of an organization’s processes and enables a structured decision-making approach.

      Compliance is the process of adhering to a set of guidelines; these could be external regulations and guidelines or internal corporate policies.

      GRC principles are tightly bound and continuous

      The image contains a screenshot of a continuous circle that is divided into three parts: risk, compliance, and governance.

      Enterprise risk management

      Regardless of size or structure, every organization makes strategic and operational decisions that expose it to uncertainties.

      Enterprise risk management (ERM) is a strategic business discipline that supports the achievement of an organization’s objectives by addressing the full spectrum of its risks and managing the combined impact of those risks as an interrelated risk portfolio (RIMS).

      An ERM is program is crucial because it will:

      • Help shape business objectives, drive revenue growth, and execute risk-based decisions.
      • Enable a deeper understanding of risks and assessment of current risk profile.
      • Support forward-looking risk management and more constructive dialogue with the board and regulatory agencies.
      • Provide insight on the robustness and efficacy of risk management processes, tools, and controls.
      • Drive a positive risk culture.

      ERM is supported by strategy, effective processes, technology, and people

      The image contains a screenshot that demonstrates how ERM is supported by strategy, effective processes, technology, and people.

      Risk frameworks

      Risk frameworks are leveraged by the industry to “provide a structure and set of definitions to allow enterprises of all types and sizes to understand and better manage their risk environments.” COSO Enterprise Risk Management, 2nd edition

      • Many organizations lean on the Committee of Sponsoring Organizations’ Enterprise Risk Management framework (COSO ERM) and ISO 31000 to view organizational risks from an enterprise perspective.
      • Prior to the introduction of standardized risk frameworks, it was difficult to quantify the impact of a risk event on the entire enterprise, as the risk was viewed in a silo or as an individual risk component.
      • Recently, the National Institute of Science and Technology (NIST) published guidance on developing an enterprise risk management approach. The guidance helps to bridge the gap between best practices in enterprise risk management and processes and control techniques that cybersecurity professionals use to meet regulatory cybersecurity risk requirements.

      The image contains a screenshot of NIST ERM approach to strategic risk.

      Source: National Institute of Standards and Technology

      New NIST guidance (NISTIR 8286) emphasizes the complexity of risk management and the need for the risk management process to be carried out seamlessly across three tiers with the overall objective of continuous improvement.

      Enterprise risk appetite

      “The amount of risk an organization is willing to take in pursuit of its objectives”

      – Robert R. Moeller, COSO ERM Framework Model
      • A primary role of the board and senior management is to balance value creation with effectively management of enterprise risks.
      • As part of this role, the board will approve the enterprise’s risk appetite. Placing this responsibility with the board ensures that the risk appetite is aligned with the company’s strategic objectives.
      • The risk appetite is used throughout the organization to assess and respond to individual risks, acting as a constant to make sure that risks are managed within the organization’s acceptable limits.
      • Each year, or in reaction to a risk trigger, the enterprise risk appetite will be updated and approved by the board.
      • Risk appetite will vary across organizations for several reasons, such as industry, company culture, competitors, the nature of the objectives pursued, and financial strength.

      Change or new risks » adjust enterprise risk profile » adjust risk appetite

      Risk profile vs. risk appetite

      Risk profile is the broad parameters an organization considers in executing its business strategy. Risk appetite is the amount of risk an entity is willing to accept in pursuit of its strategic objectives. The risk appetite can be used to inform the risk profile or vice versa. Your organization’s risk culture informs and is used to communicate both.

      Risk Tolerant

      Moderate

      Risk Averse

      • You have no compliance requirements.
      • You have no sensitive data.
      • Customers do not expect you to have strong security controls.
      • Revenue generation and innovative products take priority and risk is acceptable.
      • The organization does not have remote locations.
      • It is likely that your organization does not operate within the following industries:
        • Finance
        • Healthcare
        • Telecom
        • Government
        • Research
        • Education
      • You have some compliance requirements, such as:
        • HIPAA
        • PIPEDA
      • You have sensitive data and are required to retain records.
      • Customers expect strong security controls.
      • Information security is visible to senior leadership.
      • The organization has some remote locations.
      • Your organization most likely operates within the following industries:
        • Government
        • Research
        • Education
      • You have multiple strict compliance and/or regulatory requirements.
      • You house sensitive data, such as medical records.
      • Customers expect your organization to maintain strong and current security controls.
      • Information security is highly visible to senior management and public investors.
      • The organization has multiple remote locations.
      • Your organization operates within the following industries:
        • Finance
        • Healthcare
        • Telecom

      Where the IT risk appetite fits into the risk program

      • Your organization’s strategy and associated risk appetite cascade down to each business department. Overall strategy and risk appetite also set a strategy and risk appetite for each department.
      • Both risk appetite and risk tolerances set boundaries for how much risk an organization is willing or prepared to take. However, while appetite is often broad, tolerance is tactical and focused.
      • Tolerances apply to specific objectives and provide guidance to those executing on a day-to-day basis. They measure the variation around performance expectations that the organization will tolerate.
      • Ideally, they are incorporated into existing governance, risk, and compliance systems and are also considered when evaluated business cases.
      • IT risk appetite statements are based on IT level 1 risk types.

      The risk appetite has a risk lens but is also closely linked to corporate performance.

      The image contains a screenshot of a diagram that demonstrates how risk appetite has a risk lens, and how it is linked to corporate performance.

      Statements of risk

      The image contains a screenshot of a diagram of the risk landscape.

      Risk Appetite

      Risk Tolerance

      • The general amount of risk an organization is willing to accept while pursuing its objectives.
      • Proactive, future view of risks that reflects the desired range of enterprise performance.
      • Reflects the longer-term strategy of what needs to be achieved and the resources available to achieve it, expressed in quantitative criteria.
      • Risk appetites will vary for several reasons, such as the company culture, financial strength, and capabilities.
      • Risk tolerance is the acceptable deviation from the level set by the risk appetite.
      • Risk tolerance is a tactical tool often expressed in quantitative terms.
      • Key risk indicators are often used to align to risk tolerance limits to ensure the organization stays within the set risk boundary.

      Risk scenarios

      Risk scenarios serve two main purposes: to help decision makers understand how adverse events can affect organizational strategy and objectives and to prepare a framework for risk analysis by clearly defining and decomposing the factors contributing to the frequency and the magnitude of adverse events.

      ISACA
      • Organizations’ pervasive use of and dependency on technology has increased the importance of scenario analysis to identify relevant and important risks and the potential impacts of risk events on the organization if the risk event were to occur.
      • Risk scenarios provide “what if” analysis through a structured approach, which can help to define controls and document assumptions.
      • They form a constructive narrative and help to communicate a story by bringing in business context.
      • For the best outcome, have input from business and IT stakeholders. However, in reality, risk scenarios are usually driven by IT through the asset management practice.
      • Once the scenarios are developed, they are used during the risk analysis phase, in which frequency and business impacts are estimated. They are also a useful tool to help the risk team (and IT) communicate and explain risks to various business stakeholders.

      Top-down approach – driven by the business by determining the business impact, i.e. what is the impact on my customers, reputation, and bottom line if the system that supports payment processing fails?

      Bottom-up approach – driven by IT by identifying critical assets and what harm could happen if they were to fail.

      Example risk scenario

      Use level 1 IT risks to derive potential scenarios.

      Risk Scenario Description

      Example: IT Risks

      Risk Scenario Title

      A brief description of the risk scenario

      The enterprise is unable to recruit and retain IT staff

      Risk Type

      The process or system that is impacted by the risk

      • Service quality
      • Product and service cost

      Risk Scenario Category

      Deeper insight into how the risk might impact business functions

      • Inadequate capacity to support business needs
      • Talent and skills gap due to inability to retain talent

      Risk Statement

      Used to communicate the potential adverse outcomes of a particular risk event and can be used to communicate to stakeholders to enable informed decisions

      The organization chronically fails to recruit sufficiently skilled IT workers, leading to a loss of efficiency in overall technology operation and an increased security exposure.

      Risk Owner

      The designated party responsible and accountable for ensuring that the risk is maintained in accordance with enterprise requirements

      • Head of Human Resources
      • Business Process Owner

      Risk Oversight

      The person (role) who is responsible for risk assessments, monitoring, documenting risk response, and establishing key risk indicators

      CRO/COO

      Phase 2

      Set Your Organization Up for Success

      Phase 1

      Phase 2

      Phase 3

      • Governance, Risk, and Compliance
      • Enterprise Risk Management
      • Enterprise Risk Appetite
      • Risk Statements and Scenarios
      • What Is a Risk Taxonomy?
      • Functional Role of an IT Risk Taxonomy
      • Connection to Enterprise Risk Management
      • Establish Committee
      • Steps to Define IT Risk Taxonomy
      • Define Level 1
      • Test Level 1
      • Define Level 2 and 3
      • Test via Your Control Framework

      This phase will walk you through the following activities:

      • How to set up a cross-functional IT risk taxonomy committee

      This phase involves the following participants:

      • CIO
      • CISO
      • CRO
      • IT Risk Owners
      • Business Leaders
      • Human Resources

      What is a risk taxonomy?

      A risk taxonomy provides a common risk view and enables integrated risk

      • A risk taxonomy is the (typically hierarchical) categorization of risk types. It is constructed out of a collection of risk types organized by a classification scheme.
      • Its purpose is to assist with the management of an organization’s risk by arranging risks in a classification scheme.
      • It provides foundational support across the risk management lifecycle in relation to each of the key risks.
      • More material risk categories form the root nodes of the taxonomy, and risk types cascade into more granular manifestations (child nodes).
      • From a risk management perspective, a taxonomy will:
        • Enable more effective risk aggregation and interoperability.
        • Provide the organization with a complete view of risks and how risks might be interconnected or concentrated.
        • Help organizations form a robust control framework.
        • Give risk managers a structure to manage risks proactively.

      Typical Tree Structure

      The image contains a screenshot of the Typical Tree Structure.

      What is integrated risk management?

      • Integrated risk management is the process of ensuring all forms of risk information, including risk related to information and technology, are considered and included in the organization’s risk management strategy.
      • It removes the siloed approach of classifying risks related to specific departments or areas of the organization, recognizing that each risk is a potential threat to the overarching enterprise.
      • By aggregating the different threats or uncertainty that might exist within an organization, integrated risk management enables more informed decisions to be made that align to strategic goals and continue to drive value back to the business.
      • By holistically considering the different risks, the organization can make informed decisions on the best course of action that will reduce any negative impacts associated with the uncertainty and increase the overall value.

      The image contains a screenshot of the ERM.

      Integrated risk management: A strategic and collaborative way to manage risks across the organization. It is a forward-looking, business-specific outlook with the objective of improving risk visibility and culture.

      Drivers and benefits of integrated risk

      Drivers for Integrated Risk Management

      • Business shift to digital experiences
      • The breadth and number of risks requiring oversight
      • The need for faster risk analysis and decision making

      Benefits of Integrated Risk Management

      • Enables better scenario planning
      • Enables more proactive risk responses
      • Provides more relevant risk assurance to key stakeholders
      • Improves transparency and comparability of risks across organizational silos
      • Supports better financial resilience

      Business velocity and complexity are making real-time risk management a business necessity.

      If integrated risk is the destination, your taxonomy is your road to get you there

      Info-Tech’s Model for Integrated Risk

      The image contains a screenshot of Info-Tech's Model for Integrated Risk.

      How the risk practices intersect

      The risk taxonomy provides a common classification of risks that allows risks to roll up systematically to enterprise risk, enabling more effective risk responses and more informed decision making.

      The image contains a screenshot of a diagram that demonstrates how the risk practices intersect.

      ERM taxonomy

      Relative to the base event types, overall there is an increase in the number of level 1 risk types in risk taxonomies

      Oliver Wyman
      • The changing risk profile of organizations and regulatory focus in some industries is pushing organizations to rethink their risk taxonomies.
      • Generally, the expansion of level 1 risk types is due to the increase in risk themes under the operational risk umbrella.
      • Non-financial risks are risks that are not considered to be traditional financial risks, such as operational risk, technology risk, culture, and conduct. Environmental, social, and governance (ESG) risk is often referred to as a non-financial risk, although it can have both financial and non-financial implications.
      • Certain level 1 ERM risks, such as strategic risk, reputational risk, and ESG risk, cover both financial and non-financial risks.

      The image contains a screenshot of a diagram of the Traditional ERM Structure.

      Operational resilience

      • The concept of operational resiliency was first introduced by European Central Bank (ECB) in 2018 as an attempt to corral supervisory cooperation on operational resiliency in financial services.
      • The necessity for stronger operational resiliency became clear during the early stages of COVID-19 when many organizations were not prepared for disruption, leading to serious concern for the safety and soundness of the financial system.
      • It has gained traction and is now defined in global supervisory guidance. Canada’s prudential regulator, Office of the Superintendent of Financial Institutions (OSFI), defines it as “the ability of a financial institution to deliver its operations, including its critical operations, through disruption.”
      • Practically, its purpose is to knit together several operational risk management categories such as business continuity, security, and third-party risk.
      • The concept has been adopted by information and communication technology (ICT) companies, as technology and cyber risks sit neatly under this risk type.
      • It is now not uncommon to see operational resiliency as a level 1 risk type in a financial institution’s ERM framework.

      Operational resilience will often feature in ERM frameworks in organizations that deliver critical services, products, or functions, such as financial services

      Operational Resilience.

      ERM level 1 risk categories

      Although many organizations have expanded their enterprise risk management taxonomies to address new threats, most organizations will have the following level 1 risk types:

      ERM Level 1

      Definition

      Definition Source

      Financial

      The ability to obtain sufficient and timely funding capacity.

      Global Association of Risk Professionals (GARP)

      Non-Financial

      Non-financial risks are risks that are not considered to be traditional financial risks such as operational risk, technology risk, culture and conduct.

      Office of the Superintendent of Financial Institutions (OSFI)

      Reputational

      Potential negative publicity regarding business practices regardless of validity.

      US Federal Reserve

      Global Association of Risk Professionals (GARP)

      Strategic

      Risk of unsuccessful business performance due to internal or external uncertainties, whether the event is event or trend driven. Actions or events that adversely impact an organizations strategies and/or implementation of its strategies.

      The Risk Management Society (RIMS)

      Sustainability (ESG)

      This risk of any negative financial or reputational impact on an organizations stemming from current or prospective impacts of ESG factors on its counterparties or invested assets.

      Open Risk Manual

      Info-Tech Research Group

      Talent and Risk Culture

      The widespread behaviors and mindsets that can threaten sound decision-making, prudent risk-taking, and effective risk management and can weaken an institution’s financial and operational resilience.

      Info-Tech Research Group

      Different models of ERM

      Some large organizations will elevate certain operational risks to level 1 organizational risks due to risk materiality.

      Every organization will approach its risk management taxonomy differently; the number of level 1 risk types will vary and depend highly on perceived impact.

      Some of the reasons why an organization would elevate a risk to a level 1 ERM risk are:

      • The risk has significant impact on the organization's strategy, reputation, or financial performance.
      • The regulator has explicitly called out board oversight within legislation.
      • It is best practice in the organization’s industry or business sector.
      • The organization has structured its operations around a particular risk theme due to its potential negative impact. For example, the organization may have a dedicated department for data privacy.

      Level 1

      Potential Rationale

      Industries

      Risk Definition

      Advanced Analytics

      Use of advanced analytics is considered material

      Large Enterprise, Marketing

      Risks involved with model risk and emerging risks posed by artificial intelligence/machine learning.

      Anti-Money Laundering (AML) and Fraud

      Risk is viewed as material

      Financial Services, Gaming, Real Estate

      The risk of exposure to financial crime and fraud.

      Conduct Risk

      Sector-specific risk type

      Financial Services

      The current or prospective risk of losses to an institution arising from inappropriate supply of financial services including cases of willful or negligent misconduct.

      Operational Resiliency

      Sector-specific risk type

      Financial Services, ICT

      Organizational risk resulting from an organization’s failure to deliver its operations, including its critical operations, through disruption.

      Privacy

      Board driven – perceived as material risk to organization

      Healthcare, Financial Services

      The potential loss of control over personal information.

      Information Security

      Board driven – regulatory focus

      All may consider

      The people, processes, and technology involved in protecting data (information) in any form – whether digital or on paper – through its creation, storage, transmission, exchange, and destruction.

      Risk and impact

      Mapping risks to business outcomes happens within the ERM function and by enterprise fiduciaries.

      • When mapping risk events to enterprise risk types, the relationship is rarely linear. Rather, risk events typically will have multiple impacts on the enterprise, including strategic, reputational, ESG, and financial impacts.
      • As risk information is transmitted from lower levels, it informs the next level, providing the appropriate information to prioritize risk.
      • In the final stage, the enterprise portfolio view will reflect the enterprise impacts according to risk dimensions, such as strategic, operational, reporting, and compliance.

      Rolling Up Risks to a Portfolio View

      The image contains a screenshot to demonstrate rolling up risks to a portfolio view.

      1. A risk event within IT will roll up to the enterprise via the IT risk register.
      2. The impact of the risk on cash flow and operations will be aggregated and allocated in the enterprise risk register by enterprise fiduciaries (e.g. CFO).
      3. The impacts are translated into full value exposures or modified impact and likelihood assessments.

      Common challenges

      How to synthesize different objectives between IT risk and enterprise risk

      Commingling risk data is a major challenge when developing a risk taxonomy, but one of the underlying reasons is that the enterprise and IT look at risk from different dimensions.

      • The role of the enterprise in risk management is to provide and preserve value, and therefore the enterprise evaluates risk on an adjusted risk-return basis.
      • To do this effectively, the enterprise must break down silos and view risk holistically.
      • ERM is a top-down process of evaluating risks that may impact the entity. As part of the process, ERM must manage risks within the enterprise risk framework and provide reasonable assurances that enterprise objectives will be met.
      • IT risk management focuses on internal controls and sits as a function within the larger enterprise.
      • IT takes a bottom-up approach by applying an ongoing process of risk management and constantly identifying, assessing, prioritizing, and mitigating risks.
      • IT has a central role in risk mitigation and, if functioning well, will continually reduce IT risks, simplifying the role for ERM.

      Establish a team

      Cross-functional collaboration is key to defining level 1 risk types.

      Establish a cross-functional working group.

      • Level 1 IT risk types are the most important to get right because they are the root nodes that all subtypes of risk cascade from.
      • To ensure the root nodes (level 1 risk types) address the risks of your organization, it is vital to have a strong understanding or your organization’s value chain, so your organizational strategy is a key input for defining your IT level 1 risk types.
      • Since the taxonomy provides the method for communicating risks to the people who need to make decisions, a wide understanding and acceptance of the taxonomy is essential. This means that multiple people across your organization should be involved in defining the taxonomy.
      • Form a cross-functional tactical team to collaborate and agree on definitions. The team should include subject matter experts and leaders in key risk and business areas. In terms of governance structure, this committee might sit underneath the enterprise risk council, and members of your IT risk council may also be good candidates for this tactical working group.
      • The committee would be responsible for defining the taxonomy as well as performing regular reviews.
      • The importance of collaboration will become crystal clear as you begin this work, as risks should be connected to only one risk type.

      Governance Layer

      Role/ Responsibilities

      Enterprise

      Defines organizational goals. Directs or regulates the performance and behavior of the enterprise, ensuring it has the structure and capabilities to achieve its goals.

      Enterprise Risk Council

      • Approve of risk taxonomy

      Strategic

      Ensures business and IT initiatives, products, and services are aligned to the organization’s goals and strategy and provide expected value. Ensures adherence to key principles.

      IT Risk Council

      • Provide input
      • May review taxonomy ahead of going to the enterprise risk council for approval

      Tactical

      Ensures key activities and planning are in place to execute strategic initiatives.

      Subcommittee

      • Define risk types and definitions
      • Establish and maintain taxonomy
      • Recommend changes
      • Advocate and communicate internally

      2.1 Establish a cross-functional working group

      2-3 hours

      1. Consider your organization’s operating model and current governance framework, specifically any current risk committees.
      2. Consider the members of current committees and your objectives and begin defining:
        1. Committee mandate, goals, and success factors.
        2. Responsibility and membership.
        3. Committee procedures and policies.
      3. Make sure you define how this tactical working group will interact with existing committees.

      Download Build an IT Risk Taxonomy Workbook

      Input Output
      • Organization chart and operating model
      • Corporate governance framework and existing committee charters
      • Cross-functional working group charter
      Materials Participants
      • Whiteboard/flip charts
      • Build an IT Risk Taxonomy Workbook
      • IT Taxonomy Committee Charter
      • CISO
      • Human resources
      • Corporate communications
      • CRO or risk owners
      • Business leaders

      Phase 3

      Structure Your IT Risk Taxonomy

      Phase 1

      Phase 2

      Phase 3

      • Governance, Risk, and Compliance
      • Enterprise Risk Management
      • Enterprise Risk Appetite
      • Risk Statements and Scenarios
      • What Is a Risk Taxonomy?
      • Functional Role of an IT Risk Taxonomy
      • Connection to Enterprise Risk Management
      • Establish Committee
      • Steps to Define IT Risk Taxonomy
      • Define Level 1
      • Test Level 1
      • Define Level 2 and 3
      • Test via Your Control Framework

      This phase will walk you through the following activities:

      • Establish level 1 risk types
      • Test level 1 risk types
      • Define level 2 and level 3 risk types
      • Test the taxonomy via your control framework

      This phase involves the following participants:

      • CIO
      • CISO
      • CRO
      • IT Risk Owners
      • Business Leaders
      • Human Resources

      Structuring your IT risk taxonomy

      Do’s

      • Ensure your organization’s values are embedded into the risk types.
      • Design your taxonomy to be forward looking and risk based.
      • Make level 1 risk types generic so they can be used across the organization.
      • Ensure each risk has its own attributes and belongs to only one risk type.
      • Collaborate on and communicate your taxonomy throughout organization.

      Don’ts

      • Don’t develop risk types based on function.
      • Don’t develop your taxonomy in a silo.

      A successful risk taxonomy is forward looking and codifies the most frequently used risk language across your organization.

      Level 1

      Parent risk types aligned to organizational values

      Level 2

      Subrisks to level 1 risks

      Level 3

      Further definition

      Steps to define your IT risk taxonomy

      Step 1

      Leverage Info-Tech’s Build an IT Risk Taxonomy Guideline and identify IT level 1 risk types. Consider corporate inputs and macro trends.

      Step 2

      Test level 1 IT risk types by mapping to your enterprise's ERM level 1 risk types.

      Step 3

      Draft your level 2 and level 3 risk types. Be mutually exclusive to the extent possible.

      Step 4

      Work backward – align risk events and controls to the lowest level risk category. In our examples, we align to level 3.

      Step 5

      Add risk levels to your risk registry.

      Step 6

      Optional – Add IT risk appetite statements to risk register.

      Inputs to use when defining level 1

      To help you define your IT risk taxonomy, leverage your organization’s strategy and risk management artifacts, such as outputs from risk assessments, audits, and test results. Also consider macro trends and potential risks unique to your organization.

      Step 1 – Define Level 1 Risk Types

      Use corporate inputs to help structure your taxonomy

      • Corporate Strategy
      • Risk Assessment
      • Audit
      • Test Results

      Consider macro trends that may have an impact on how you manage IT risks

      • Geopolitical Risk
      • Economic Downturn
      • Regulation
      • Competition
      • Climate Risk
      • Industry Disruption

      Evaluate from an organizational lens

      Ask risk-based questions to help define level 1 IT risks for your organization.

      IT Risk Type

      Example Questions

      Technology

      How reliant is our organization on critical assets for business operations?

      How resilient is the organization to an unexpected crisis?

      How many planned integrations do we have (over the next 24 months)?

      Talent Risk

      What is our need for specialized skills, like digital, AI, etc.?

      Does our culture support change and innovation?

      How susceptible is our organization to labor market changes?

      Strategy

      What is the extent of digital adoption or use of emerging technologies in our organization?

      How aligned is IT with strategy/corporate goals?

      How much is our business dependent on changing customer preferences?

      Data

      How much sensitive data does our organization use?

      How much data is used and stored aggregately?

      How often is data moved? And to what locations?

      Third-party

      How many third-party suppliers do we have?

      How reliant are we on the global supply chain?

      What is the maturity level of our third-party suppliers?

      Do we have any concentration risk?

      Security

      How equipped is our organization to manage cyber threats?

      How many security incidents occur per year/quarter/day?

      Do we have regulatory obligations? Is there risk of enforcement action?

      Level 1 IT taxonomy structure

      Step 2 – Consider your organization’s strategy and areas where risks may manifest and use this guidance to advance your thinking. Many factors may influence your taxonomy structure, including internal organizational structure, the size of your organization, industry trends and organizational context, etc.

      Most IT organizations will include these level 1 risks in their IT risk taxonomy

      IT Level 1

      Definition

      Definition Source

      Technology

      Risk arising from the inadequacy, disruption, destruction, failure, damage from unauthorized access modifications, or malicious use of information technology assets, people or processes that enable and support business needs, and can result in financial loss and/or reputational damage.

      Open Risk Manual

      Note how this definition by OSFI includes cyber risk as part of technology risk. Smaller organizations and organizations that do not use large amounts of sensitive information will typically fold cyber risks under technology risks. Not all organizations will take this approach. Some organizations may elevate security risk to level 1.

      “Technology risk”, which includes “cyber risk”, refers to the risk arising from the inadequacy, disruption, destruction, failure, damage from unauthorized access, modifications, or malicious use of information technology assets, people or processes that enable and support business needs, and can result in financial loss and/or reputational damage.

      Office of the Superintendent of Financial Institutions (OSFI)

      Talent

      The risk of not having the right knowledge and skills to execute strategy.

      Info-Tech Research Group/McLean & Company

      Human capital challenges including succession challenges and the ability to attract and retain top talent are considered the most dominant risk to organizations’ ability to meet their value proposition (Protiviti, 2023).

      Strategic

      Risks that threaten IT’s ability to deliver expected business outcomes.

      Info-Tech Research Group

      IT’s role as strategic enabler to the business has never been so vital. With the speed of disruptive innovation, IT must be able to monitor alignment, support opportunities, and manage unexpected crises.

      Level 1 IT taxonomy structure cont'd

      Step 2 – Large and more complex organizations may have more level 1 risk types. Variances in approaches are closely linked to the type of industry and business in which the organization operates as well as how they view and position risks within their organization.

      IT Level 1

      Definition

      Definition Source

      Data

      Data risk is the exposure to loss of value or reputation caused by issues or limitations to an organization’s ability to acquire, store, transform, move, and use its data assets.

      Deloitte

      Data risk encompasses the risk of loss value or reputation resulting from inadequate or failed internal processes, people and systems or from external events impacting on data.

      Australian Prudential Regulation Authority (APRA) CPG 235 -2013)

      Data is increasingly being used for strategic growth initiatives as well as for meeting regulatory requirements. Organizations that use a lot of data or specifically sensitive information will likely have data as a level 1 IT risk type.

      Third-Party

      The risk adversely impacting the institutions performance by engaging a third party, or their associated downstream and upstream partners or another group entity (intragroup outsourcing) to provide IT systems or related services.

      European Banking Association (EBA)

      Open Risk Manual uses EBA definition

      Third-party risk (supply chain risk) received heightened attention during COVID-19. If your IT organization is heavily reliant on third parties, you may want to consider elevating third-party risk to level 1.

      Security

      The risk of unauthorized access to IT systems and data from within or outside the institution (e.g., cyber-attacks). An incident is viewed as a series of events that adversely affects the information assets of an organization. The overall narrative of this type of risk event is captured as who, did what, to what (or whom), with what result.

      Open Risk Manual

      Some organizations and industries are subject to regulatory obligations, which typically means the board has strict oversight and will elevate security risk to a level 1.

      Common challenges

      Considerations when defining level 1 IT risk types

      • Ultimately, the identification of a level 1 IT risk type will be driven by the potential for and materiality of vulnerabilities that may impede an organization from delivering successful business outcomes.
      • Senior leaders within organizations play a central role in protecting organizations against vulnerabilities and threats.
      • The size and structure of your organization will influence how you manage risk.
      • The following slide shows typical roles and responsibilities for data privacy.
      • Large enterprises and organizations that use a lot of personal identifiable information (PII) data, such as those in healthcare, financial services, and online retail, will typically have data as a level 1 IT risk and data privacy as a level 2 risk type.
      • However, smaller organizations or organizations that do not use a lot of data will typically fold data privacy under either technology risk or security risk.

      Deciding placement in taxonomy

      Deciding Placement in Taxonomy.

      • In larger enterprises, data risks are managed within a dedicated functional department with its own governance structure. In small organizations, the CIO is typically responsible and accountable for managing data privacy risk.

      Global Enterprise

      Midmarket

      Privacy Requirement

      What Is Involved

      Accountable

      Responsible

      Accountable & Responsible

      Privacy Legal and Compliance Obligations

      • Ensuring the relevant Accountable roles understand privacy obligations for the jurisdictions operated in.

      Privacy Officer (Legal)

      Privacy Officer (Legal)

      Privacy Policy, Standards, and Governance

      • Defining polices and ensuring they are in place to ensure all privacy obligations are met.
      • Monitoring adherence to those policies and standards.

      Chief Risk Officer (Risk)

      Head of Risk Function

      Data Classification and Security Standards and Best-Practice Capabilities

      • Defining the organization’s data classification and security standards and ensuring they align to the privacy policy.
      • Designing and building the data security standards, processes, roles, and technologies required to ensure all security obligations under the privacy policy can be met.
      • Providing oversight of the effectiveness of data security practices and leading resolution of data security issues/incidents.

      Chief Information Security Officer (IT)

      Chief Information Security Officer (IT)

      Technical Application of Data Classification, Management and Security Standards

      • Ensuring all technology design, implementation, and operational decisions adhere to data classification, data management, and data security standards.

      Chief Information Officer (IT)

      Chief Data Architect (IT)

      Chief Information Officer (IT)

      Data Management Standards and Best-Practice Capabilities

      • Defining the organization’s data management standards and ensuring they align to the privacy policy.
      • Designing and building the data management standards, processes, roles, and technologies required to ensure data classification, access, and sharing obligations under the privacy policy can be met.
      • Providing oversight of the effectiveness of data classification, access, and sharing practices and leading resolution of data management issues/incidents.

      Chief Data Officer

      Where no Head of Data Exists and IT, not the business, is seen as de facto owner of data and data quality

      Execution of Data Management

      • Ensuring business processes that involve data classification, sharing, and access related to their data domain align to data management standards (and therefore privacy obligations).

      L1 Business Process Owner

      L2 Business Process Owner

      Common challenges

      Defining security risk and where it resides in the taxonomy

      • For risk management to be effective, risk professionals need to speak the same language, but the terms “information security,” “cybersecurity,” and “IT security” are often used interchangeably.
      • Traditionally, cyber risk was folded under technology risk and therefore resided at a lower level of a risk taxonomy. However, due to heightened attention from regulators and boards stemming from the pervasiveness of cyber threats, some organizations are elevating security risks to a level 1 IT risk.
      • Furthermore, regulatory cybersecurity requirements have emphasized control frameworks. As such, many organizations have adopted NIST because it is comprehensive, regularly updated, and easily tailored.
      • While NIST is prescriptive and action oriented, it start with controls and does not easily integrate with traditional ERM frameworks. To address this, NIST has published new guidance focused on an enterprise risk management approach. The guidance helps to bridge the gap between best practices in enterprise risk management and processes and control techniques that cybersecurity professionals use to meet regulatory cybersecurity risk requirements.

      Definitional Nuances

      “Cybersecurity” describes the technologies, processes, and practices designed to protect networks, computers, programs, and data from attack, damage, or unauthorized access.

      “IT security” describes a function as well as a method of implementing policies, procedures, and systems to defend the confidentiality, integrity, and availability of any digital information used, transmitted, or stored throughout the organization’s environment.

      “Information security” defines the people, processes, and technology involved in protecting data (information) in any form – whether digital or on paper – through its creation, storage, transmission, exchange, and destruction.

      3.1 Establish level 1 risk types

      2-3 hours

      1. Consider your current and future corporate goals and business initiatives, risk management artifacts, and macro industry trends.
      2. Ask questions to understand risks unique to your organization.
      3. Review Info-Tech’s IT level 1 risk types and identify the risk types that apply to your organization.
      4. Add any risk types that are missing and unique to your organization.
      5. Refine the definitions to suit your organization.
      6. Be mutually exclusive and collectively exhaustive to the extent possible.

      Download Build an IT Risk Taxonomy Workbook

      InputOutput
      • Organization's strategy
      • Other organizational artifacts if available (operating model, outputs from audits and risk assessments, risk profile, and risk appetite)
      • Build an IT Risk Taxonomy Guideline
      • IT Risk Taxonomy Definitions
      • Level 1 IT risk types customized to your organization
      MaterialsParticipants
      • Whiteboard/flip charts
      • Build an IT Risk Taxonomy Workbook
      • CISO
      • Human resources
      • Corporate communications
      • CRO or risk owners
      • Business leaders

      3.2 Map IT risk types against ERM level 1 risk types

      1-2 hours

      1. Using the output from Activity 3.1, map your IT risk types to your ERM level 1 risk types.
      2. Record in the Build an IT Risk Taxonomy Workbook.

      Download Build an IT Risk Taxonomy Workbook

      InputOutput
      • IT level 1 risk types customized to your organization
      • ERM level 1 risk types
      • Final level 1 IT risk types
      MaterialsParticipants
      • Whiteboard/flip charts
      • Build an IT Risk Taxonomy Workbook
      • CISO
      • Human resources
      • Corporate communications
      • CRO or risk owners
      • Business leaders

      Map IT level 1 risk types to ERM

      Test your level 1 IT risk types by mapping to your organization’s level 1 risk types.

      Step 2 – Map IT level 1 risk types to ERM

      The image contains two tables. 1 table is ERM Level 1 Risks, the other table is IT Level 1 Risks.

      3.3 Establishing level 2 and 3 risk types

      3-4 hours

      1. Using the level 1 IT risk types that you have defined and using Info-Tech’s Risk Taxonomy Guideline, first begin to identify level 2 risk types for each level 1 type.
      2. Be mutually exclusive and collectively exhaustive to the extent possible.
      3. Once satisfied with your level 2 risk types, break them down further to level 3 risk types.

      Note: Smaller organizations may only define two risk levels, while larger organizations may define further to level 4.

      Download Build an IT Risk Taxonomy Design Template

      InputOutput
      • Output from Activity 3.1, Establish level 1 risk types
      • Build an IT Risk Taxonomy Workbook
      • Build an IT Risk Taxonomy Guideline
      • Level 2 and level 3 risk types recorded in Build an IT Risk Taxonomy Design Template
      MaterialsParticipants
      • Whiteboard/flip charts
      • Build an IT Risk Taxonomy Workbook
      • CISO
      • Human resources
      • Corporate communications
      • CRO or risk owners
      • Business leaders

      Level 2 IT taxonomy structure

      Step 3 – Break down your level 1 risk types into subcategories. This is complicated and may take many iterations to reach a consistent and accepted approach. Try to make your definitions intuitive and easy to understand so that they will endure the test of time.

      The image contains a screenshot of Level 2 IT taxonomy Structure.

      Security vulnerabilities often surface through third parties, but where and how you manage this risk is highly dependent on how you structure your taxonomy. Organizations with a lot of exposure may have a dedicated team and may manage and report security risks under a level 1 third-party risk type.

      Level 3 IT taxonomy structure

      Step 3 – Break down your level 2 risk types into lower-level subcategories. The number of levels of risk you have will depend on the size of and magnitude of risks within your organization. In our examples, we demonstrate three levels.

      The image contains a screenshot of Level 3 IT taxonomy Structure.

      Risk taxonomies for smaller organizations may only include two risk levels. However, large enterprises or more complex organizations may extend their taxonomy to level 3 or even 4. This illustration shows just a few examples of level 3 risks.

      Test using risk events and controls

      Ultimately risk events and controls need to roll up to level 1 risks in a consistent manner. Test the robustness of your taxonomy by working backward.

      Step 4 – Work backward to test and align risk events and controls to the lowest level risk category.

      • A key function of IT risk management is to monitor and maintain internal controls.
      • Internal controls help to reduce the level of inherent risk to acceptable levels, known as residual risk.
      • As risks evolve, new controls may be needed to upgrade protection for tech infrastructure and strengthen connections between critical assets and third-party suppliers.

      Example – Third Party Risk

      Third Party Risk example.

      3.4 Test your IT taxonomy

      2-3 hours

      1. Leveraging the output from Activities 3.1 to 3.3 and your IT Risk Taxonomy Design Template, begin to test the robustness of the taxonomy by working backward from controls to level 1 IT risks.
      2. The lineage should show clearly that the control will mitigate the impact of a realized risk event. Refine the control or move the control to another level 1 risk type if the control will not sufficiently reduce the impact of a realized risk event.
      3. Once satisfied, update your risk register or your risk management software tool.

      Download Build an IT Risk Taxonomy Design Template

      InputOutput
      • Output from Activities 3.1 to 3.3
      • IT risk taxonomy documented in the IT Risk Taxonomy Design Template
      MaterialsParticipants
      • Whiteboard/flip charts
      • IT risk register
      • Build an IT Risk Taxonomy Workbook
      • CISO
      • Human resources
      • Corporate communications
      • CRO or risk owners
      • Business leaders

      Update risk register

      Step 5 – Once you are satisfied with your risk categories, update your risk registry with your IT risk taxonomy.

      Use Info-Tech’s Risk Register Tool or populate your internal risk software tool.

      Risk Register.

      Download Info-Tech’s Risk Register Tool

      Augment the risk event list using COBIT 2019 processes (Optional)

      Other industry-leading frameworks provide alternative ways of conceptualizing the functions and responsibilities of IT and may help you uncover additional risk events.

      1. Managed IT Management Framework
      2. Managed Strategy
      3. Managed Enterprise Architecture
      4. Managed Innovation
      5. Managed Portfolio
      6. Managed Budget and Costs
      7. Managed Human Resources
      8. Managed Relationships
      9. Managed Service Agreements
      10. Managed Vendors
      11. Managed Quality
      12. Managed Risk
      13. Managed Security
      14. Managed Data
      15. Managed Programs
      16. Managed Requirements Definition
      17. Managed Solutions Identification and Build
      18. Managed Availability and Capacity
      19. Managed Organizational Change Enablement
      20. Managed IT Changes
      21. Managed IT Change Acceptance and Transitioning
      22. Managed Knowledge
      23. Managed Assets
      24. Managed Configuration
      25. Managed Projects
      26. Managed Operations
      27. Managed Service Requests and Incidents
      28. Managed Problems
      29. Managed Continuity
      30. Managed Security Services
      31. Managed Business Process Controls
      32. Managed Performance and Conformance Monitoring
      33. Managed System of Internal Control
      34. Managed Compliance with External Requirements
      35. Managed Assurance
      36. Ensured Governance Framework Setting and Maintenance
      37. Ensured Benefits Delivery
      38. Ensured Risk Optimization
      39. Ensured Resource Optimization
      40. Ensured Stakeholder Engagement

      Example IT risk appetite

      When developing your risk appetite statements, ensure they are aligned to your organization’s risk appetite and success can be measured.

      Example IT Risk Appetite Statement

      Risk Type

      Technology Risk

      IT should establish a risk appetite statement for each level 1 IT risk type.

      Appetite Statement

      Our organization’s number-one priority is to provide high-quality trusted service to our customers. To meet this objective, critical systems must be highly performant and well protected from potential threats. To meet this objective, the following expectations have been established:

      • No appetite for unauthorized access to systems and confidential data.
      • Low appetite for service downtime.
        • Service availability objective of 99.9%.
        • Near real-time recovery of critical services – ideally within 30 minutes, no longer than 3 hours.

      The ideal risk appetite statement is qualitative and supported by quantitative measures.

      Risk Owner

      Chief Information Officer

      Ultimately, there is an accountable owner(s), but involve business and technology stakeholders when drafting to gain consensus.

      Risk Oversight

      Enterprise Risk Committee

      Supporting Framework(s)

      Business Continuity Management, Information Security, Internal Audit

      The number of supporting programs and frameworks will vary with the size of the organization.

      3.5 Draft your IT risk appetite statements

      Optional Activity

      2-3 hours

      1. Using your completed taxonomy and your organization’s risk appetite statement, draft an IT risk appetite statement for each level 1 risk in your workbook.
      2. Socialize the statements and gain approval.
      3. Add the approved risk appetite statements to your IT risk register.

      Download Build an IT Risk Taxonomy Workbook

      Input Output
      • Organization’s risk appetite statement
      • Build an IT Risk Taxonomy Workbook
      • IT Risk Taxonomy Design Template
      • IT risk appetite statements
      Materials Participants
      • Whiteboard/flip charts
      • Build an IT Risk Taxonomy Workbook
      • CISO, CIO
      • Human resources
      • Corporate communications
      • CRO or risk owners
      • Business leaders

      Key takeaways and next steps

      • The risk taxonomy is the backbone of a robust enterprise risk management program. A good taxonomy is frequently used and well understood.
      • Not only is the risk taxonomy used to assess organizational impact, but it is also used for risk reporting, scenarios analysis and horizon scanning, and risk appetite expression.
      • It is essential to capture IT risks within the ERM framework to fully understand the impact and allow for consistent risk discussions and meaningful aggregation.
      • Defining an IT risk taxonomy is a team sport, and organizations should strive to set up a cross-functional working group that is tasked with defining the taxonomy, monitoring its effectiveness, and ensuring continual improvement.
      • The work does not end when the taxonomy is complete. The taxonomy should be well socialized throughout the organization after inception through training and new policies and procedures. Ultimately, it should be an activity embedded into risk management practices.
      • The taxonomy is a living document and should be continually improved upon.

      3.6 Prepare to communicate the taxonomy internally

      1-2 hours

      To gain acceptance of your risk taxonomy within your organization, ensure it is well understood and used throughout the organization.

      1. Consider your audience and agree on the key elements you want to convey.
      2. Prepare your presentation.
      3. Test your presentation with a smaller group before communicating to senior leadership or the board.

      Coming soon: Look for our upcoming research Communicate Any IT Initiative.

      InputOutput
      • Build an IT Risk Taxonomy Workbook
      • Upcoming research: Communicate Any IT Initiative
      • Presentation
      MaterialsParticipants
      • Whiteboard/flip charts
      • Upcoming research: Communicate Any IT Initiative
      • Internal communication templates
      • CISO, CIO
      • Human resources
      • Corporate communications
      • CRO or risk owners
      • Business leaders

      Related Info-Tech Research

      Build an IT Risk Management Program

      • Use this blueprint to transform your ad hoc risk management processes into a formalized ongoing program and increase risk management success.
      • Learn how to take a proactive stance against IT threats and vulnerabilities by identifying and assessing IT’s greatest's risks before they occur.

      Integrate IT Risk Into Enterprise Risk

      • Use this blueprint to understand gaps in your organization’s approach to risk management.
      • Learn how to integrate IT risks into the foundational risk practice

      Coming Soon: Communicate Any IT initiative

      • Use this blueprint to compose an easy-to-understand presentation to convey the rationale of your initiative and plan of action.
      • Learn how to identify your target audience and tailor and deliver the message in an authentic and clear manner.

      Risk definitions

      Term Description
      Emergent Risk Risks that are poorly understood but expected to grow in significance.
      Residual Risk The amount of risk you have left after you have removed a source of risk or implemented a mitigation approach (controls, monitoring, assurance).
      Risk Acceptance If the risk is within the enterprise's risk tolerance or if the cost of otherwise mitigating the risk is higher than the potential loss, the enterprise can assume the risk and absorb any losses.
      Risk Appetite An organization’s general approach and attitude toward risk; the total exposed amount that an organization wishes to undertake on the basis of risk-return trade-offs for one or more desired and expected outcomes.
      Risk Assessment The process of estimating and evaluating risk.
      Risk Avoidance The risk response where an organization chooses not to perform a particular action or maintain an existing engagement due to the risk involved.
      Risk Event A risk occurrence (actual or potential) or a change of circumstances. Can consist of more than one occurrence or of something not happening. Can be referred to as an incident or accident.
      Risk Identification The process of finding, recognizing, describing, and documenting risks that could impact the achievement of objectives.
      Risk Management The capability and related activities used by an organization to identify and actively manage risks that affect its ability to achieve goals and strategic objectives. Includes principles, processes, and framework.
      Risk Likelihood The chance of a risk occurring. Usually measured mathematically using probability.
      Risk Management Policy Expresses an organization’s commitment to risk management and clarifies its use and direction.
      Risk Mitigation The risk response where an action is taken to reduce the impact or likelihood of a risk occurring.
      Risk Profile A written description of a set of risks.

      Risk definitions

      Term Description
      Risk Opportunity A cause/trigger of a risk with a positive outcome.
      Risk Owner The designated party responsible and accountable for ensuring that the risk is maintained in accordance with enterprise requirements.
      Risk Register A tool used to identify and document potential and active risks in an organization and to track the actions in place to manage each risk.
      Risk Response How you choose to respond to risk (accept, mitigate, transfer, or avoid).
      Risk Source The element that, alone or in combination, has potential to give rise to a risk. Usually this is the root cause of the risk.
      Risk Statement A description of the current conditions that may lead to the loss, and a description of the loss.
      Risk Tolerance The amount of risk you are prepared or able to accept (in terms of volume or impact); the amount of uncertainty an organization is willing to accept in the aggregate (or more narrowly within a certain business unit or for a specific risk category). Expressed in quantitative terms that can be monitored (such as volatility or deviation measures), risk tolerance often is communicated in terms of acceptable/unacceptable outcomes or as limited levels of risk. Risk tolerance statements identify the specific minimum and maximum levels beyond which the organization is unwilling to accept variations from the expected outcome.
      Risk Transfer The risk response where you transfer the risk to a third party.

      Research Contributors and Experts

      LynnAnn Brewer
      Director
      McLean & Company

      Sandi Conrad
      Principal Research Director
      Info-Tech Research Group

      Valence Howden
      Principal Research Director
      Info-Tech Research Group

      John Kemp
      Executive Counsellor – Executive Services
      Info-Tech Research Group

      Brittany Lutes
      Research Director
      Info-Tech Research Group

      Carlene McCubbin
      Practice Lead – CIO Practice
      Info-Tech Research Group

      Frank Sargent
      Senior Workshop Director
      Info-Tech Research Group

      Frank Sewell
      Advisory Director
      Info-Tech Research Group

      Ida Siahaan
      Research Director
      Info-Tech Research Group

      Steve Willis
      Practice Lead – Data Practice
      Info-Tech Research Group

      Bibliography

      Andrea Tang, “Privacy Risk Management”. ISACA Journal, June 2020, Accessed January 2023
      Anthony Kruizinga, “Reshaping the risk taxonomy”. PwC, April 2021, Accessed January 2023
      Auditboard, "The Essentials of Integrated Risk Management (IRM)", June 2022, Accessed January 2023
      Brenda Boultwood, “How to Design an ERM-Friendly Risk Data Architecture”. Global Association of Risk Professionals, February 2020, Accessed January 2023
      BSI Standards Publication, "Risk Management Guidelines", ISO 31000, 2018
      Dan Swinhoe, "What is Physical Security, How to keep your facilities and devices safe from onsite attackers", August 2021, Accessed January 2023
      Eloise Gratton, “Data governance and privacy risk in Canada: A checklist for boards and c-suite”. Borden Ladner Gervais, November 2022 , Accessed January 2023
      European Union Agency for Cyber Security Glossary
      European Banking Authority, "Guidelines on ICT Risk Assessment under the Supervisory Review and Evaluation process (SREP)", September 2017, Accessed February 2023
      European Banking Authority, "Regulatory Framework for Mitigating Key Resilient Risks", Sept 2018, Accessed February 2023
      EY, "Seeking stability within volatility: How interdependent risks put CROs at the heart of the banking business", 12th annual EY/IFF global bank risk management survey, 2022, Accessed February 2023
      Financial Stability Board, "Cyber Lexicon", November 2018, Accessed February 2023
      Financial Stability Board, "Principles for Effective Risk Appetite Framework", November 2013, Accessed January 2023
      Forbes Technology Council, "14 Top Data Security Risks Every Business Should Address", January 2020, Accessed January 2023
      Frank Martens, Dr. Larry Rittenberg, "COSO, Risk Appetite Critical for Success, Using Risk Appetite to Thrive in a Changing World", May 2020, Accessed January 2023
      Gary Stoneurmer, Alice Goguen and Alexis Feringa, "NIST, Risk Management Guide for Information Technology Systems", Special Publication, 800-30, September 2012, Accessed February 2023
      Guy Pearce, "Real-World Data Resilience Demands and Integrated Approach to AI, Data Governance and the Cloud", ISACA Journal, May 2022
      InfoTech Tech Trends Report, 2023
      ISACA, "Getting Started with Risk Scenarios", 2022, Accessed February 2023
      James Kaplan, "Creating a technology risk and cyber risk appetite framework," McKinsey & Company, August 2022, Accessed February 2023
      Jean-Gregorie Manoukian, Wolters Kluwer, "Risk appetite and risk tolerance: what’s the difference?", Sept 2016, Accessed February 2023
      Jennifer Bayuk, “Technology’s Role in Enterprise Risk Management”, ISACA Journal, March 2018, Accessed in February 2023
      John Thackeray, "Global Association of Risk Professionals, 7 Key Elements of Effective ERM", January 2020, Accessed January 2023
      KPMG, "Regulatory rigor: Managing technology and cyber risk, How FRFI’s can achieve outcomes laid out in OSFI B-13", October 2022, Accessed January 2023
      Marc Chiapolino et al, “Risk and resilience priorities, as told by chief risk officers”, McKinsey and Company, December 2022, Accessed January 2023
      Mike Rost, Workiva, "5 Steps to Effective Strategic Management", Updated February 2023. Accessed February 2023
      NIST, "Risk Management Framework for Information Systems and Organization, The System Life Cycle Approach for Security and Privacy," December 2018, Accessed February 2023
      NIST, NISTIR, "Integrating CyberSecurity and Enterprise Risk", October 2020, Accessed February 2023
      Oliver Wyman, "The ORX Reference Taxonomy for operational and non-financial risk summary report", 2019, Accessed February 2023.
      Office of the Superintendent of Financial Institutions, "Operational Resilience Consultation Results Summary", December 2021, Accessed January 2023
      Open Risk Manual, Risk Taxonomy Definitions
      Ponemon. "Cost of a Data Breach Report 2021." IBM, July 2021. Web.
      Protiviti, "Executive Perspectives on Top Risks, 2023 & 2032, Key Issues being discussed in the boardroom and c-suite", February 2023, Accessed February 2023
      RIMS, ISACA, "Bridging the Digital Gap, How Collaboration Between IT and Risk Management can Enhance Value Creation", September 2019, Accessed February 2023
      Robert, R. Moeller, "COSO, Enterprise Risk Management, Second Edition, 2011", Accessed February 2023
      Robert Putrus, "Effective Reporting to the BoD on Critical Assets, Cyberthreats and Key Controls: The Qualitative and Quantitative Model", ISACA Journal, January 2021, Accessed January 2023
      Ron Brash, "Prioritizing Asset Risk Management in ICS Security", August 2020, Accessed February 2023
      Ronald Van Loon, "What is Data Culture and How to Implement it?", November 2023, Accessed February 2023
      SAS, "From Crisis to Opportunity, Redefining Risk Management", 2021Accessed January 2023
      Satori, Cloudian, "Data Protection and Privacy: 12 Ways to Protect User Data", Accessed January 2023
      Spector Information Security, "Building your Asset and Risk Register to Manage Technology Risk", November 2021, Accessed January 2023
      Talend, "What is data culture", Accessed February 2023
      Tom Schneider, "Managing Cyber Security Risk as Enterprise Risk", ISACA Journal, September 2022, Accessed February 2023
      Tony Martin –Vegue, "How to Write Strong Risk Scenarios and Statements", ISACA Journal, September 2021, Accessed February 2023
      The Wall Street Journal, "Making Data Risk a Top Priority", April 2018, Accessed February 2023

      Master Organizational Change Management Practices

      • Buy Link or Shortcode: {j2store}188|cart{/j2store}
      • member rating overall impact: 9.1/10 Overall Impact
      • member rating average dollars saved: $69,330 Average $ Saved
      • member rating average days saved: 24 Average Days Saved
      • Parent Category Name: Program & Project Management
      • Parent Category Link: /program-and-project-management
      • Organizational change management (OCM) is often an Achilles’ heel for IT departments and business units, putting projects and programs at risk – especially large, complex, transformational projects.
      • When projects that depend heavily on users and stakeholders adopting new tools, or learning new processes or skills, get executed without an effective OCM plan, the likelihood that they will fail to achieve their intended outcomes increases exponentially.
      • The root of the problem often comes down to a question of accountability: who in the organization is accountable for change management success? In the absence of any other clearly identifiable OCM leader, the PMO – as the organizational entity that is responsible for facilitating successful project outcomes – needs to step up and embrace this accountability.
      • As PMO leader, you need to hone an OCM strategy and toolkit that will help ensure not only that projects are completed but also that benefits are realized.

      Our Advice

      Critical Insight

      • The root of poor stakeholder adoption on change initiatives is twofold:
        • Project planning tends to fixate on technology and neglects the behavioral and cultural factors that inhibit user adoption;
        • Accountabilities for managing change and helping to realize the intended business outcomes post-project are not properly defined in advance.
      • Persuading people to change requires a “soft,” empathetic approach to keep them motivated and engaged. But don’t mistake “soft” for easy. Managing the people part of change is amongst the toughest work there is, and it requires a comfort and competency with uncertainty, ambiguity, and conflict.
      • Transformation and change are increasingly becoming the new normal. While this normality may help make people more open to change in general, specific changes still need to be planned, communicated, and managed. Agility and continuous improvement are good, but can degenerate into volatility if change isn’t managed properly.

      Impact and Result

      • Plan for human nature. To ensure project success and maximize benefits, plan and facilitate the non-technical aspects of organizational change by addressing the emotional, behavioral, and cultural factors that foster stakeholder resistance and inhibit user adoption.
      • Make change management as ubiquitous as change itself. Foster a project culture that is proactive about OCM. Create a process where OCM considerations are factored in as early as project ideation and where change is actively managed throughout the project lifecycle, including after the project has closed.
      • Equip project leaders with the right tools to foster adoption. Effective OCM requires an actionable toolkit that will help plant the seeds for organizational change. With the right tools and templates, the PMO can function as the hub for change, helping the business units and project teams to consistently achieve project and post-project success.

      Master Organizational Change Management Practices Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out how implementing an OCM strategy through the PMO can improve project outcomes and increase benefits realization.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Prepare the PMO for change leadership

      Assess the organization’s readiness for change and evaluate the PMO’s OCM capabilities.

      • Drive Organizational Change from the PMO – Phase 1: Prepare the PMO for Change Leadership
      • Organizational Change Management Capabilities Assessment
      • Project Level Assessment Tool

      2. Plant the seeds for change during project planning and initiation

      Build an organic desire for change throughout the organization by developing a sponsorship action plan through the PMO and taking a proactive approach to change impacts.

      • Drive Organizational Change from the PMO – Phase 2: Plant the Seeds for Change During Project Planning and Initiation
      • Organizational Change Management Impact Analysis Tool

      3. Facilitate change adoption throughout the organization

      Ensure stakeholders are engaged and ready for change by developing effective communication, transition, and training plans.

      • Drive Organizational Change from the PMO – Phase 3: Facilitate Change Adoption Throughout the Organization
      • Stakeholder Engagement Workbook
      • Transition Plan Template
      • Transition Team Communications Template

      4. Establish a post-project benefits attainment process

      Determine accountabilities and establish a process for tracking business outcomes after the project team has packed up and moved onto the next project.

      • Drive Organizational Change from the PMO – Phase 4: Establish a Post-Project Benefits Attainment Process
      • Portfolio Benefits Tracking Tool

      5. Solidify the PMO’s role as change leader

      Institute an Organizational Change Management Playbook through the PMO that covers tools, processes, and tactics that will scale all of the organization’s project efforts.

      • Drive Organizational Change from the PMO – Phase 5: Solidify the PMO's Role as Change Leader
      • Organizational Change Management Playbook
      [infographic]

      Workshop: Master Organizational Change Management Practices

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Assess OCM Capabilities

      The Purpose

      Assess the organization’s readiness for change and evaluate the PMO’s OCM capabilities.

      Estimate the relative difficulty and effort required for managing organizational change through a specific project.

      Create a rough but concrete timeline that aligns organizational change management activities with project scope.

      Key Benefits Achieved

      A better understanding of the cultural appetite for change and of where the PMO needs to focus its efforts to improve OCM capabilities.

      A project plan that includes disciplined organizational change management from start to finish.

      Activities

      1.1 Assess the organization’s current readiness for change.

      1.2 Perform a change management SWOT analysis to assess the PMO’s capabilities.

      1.3 Define OCM success metrics.

      1.4 Establish and map out a core OCM project to pilot through the workshop.

      Outputs

      Organizational Change Management Capabilities Assessment

      A diagnosis of the PMO’s strengths and weaknesses around change management, as well as the opportunities and threats associated with driving an OCM strategy through the PMO

      Criteria for implementation success

      Project Level Assessment

      2 Analyze Change Impacts

      The Purpose

      Analyze the impact of the change across various dimensions of the business.

      Develop a strategy to manage change impacts to best ensure stakeholder adoption.

      Key Benefits Achieved

      Improved planning for both your project management and organizational change management efforts.

      A more empathetic understanding of how the change will be received in order to rightsize the PMO’s OCM effort and maximize adoption.

      Activities

      2.1 Develop a sponsorship action plan through the PMO.

      2.2 Determine the relevant considerations for analyzing the change impacts of a project.

      2.3 Analyze the depth of each impact for each stakeholder group.

      2.4 Establish a game plan to manage individual change impacts.

      2.5 Document the risk assumptions and opportunities stemming from the impact analysis.

      Outputs

      Sponsorship Action Plan

      Organizational Change Management Capabilities Assessment

      Risk and Opportunity Assessment

      3 Establish Collaborative Roles and Develop an Engagement Plan

      The Purpose

      Define a clear and compelling vision for change.

      Define roles and responsibilities of the core project team for OCM.

      Identify potential types and sources of resistance and enthusiasm.

      Create a stakeholder map that visualizes relative influence and interest of stakeholders.

      Develop an engagement plan for cultivating support for change while eliciting requirements.

      Key Benefits Achieved

      Begin to communicate a compelling vision for change.

      Delegate and divide work on elements of the transition plan among the project team and support staff.

      Begin developing a communications plan that appeals to unique needs and attitudes of different stakeholders.

      Cultivate support for change while eliciting requirements.

      Activities

      3.1 Involve the right people to drive and facilitate change.

      3.2 Solidify the vision of change to reinforce and sustain leadership and commitment.

      3.3 Proactively identify potential skeptics in order to engage them early and address their concerns.

      3.4 Stay one step ahead of potential saboteurs to prevent them from spreading dissent.

      3.5 Find opportunities to empower enthusiasts to stay motivated and promote change by encouraging others.

      3.6 Formalize the stakeholder analysis to identify change champions and blockers.

      3.7 Formalize the engagement plan to begin cultivating support while eliciting requirements.

      Outputs

      RACI table

      Stakeholder Analysis

      Engagement Plan

      Communications plan requirements

      4 Develop and Execute the Transition Plan

      The Purpose

      Develop a realistic, effective, and adaptable transition plan, including:Clarity around leadership and vision.Well-defined plans for targeting unique groups with specific messages.Resistance and contingency plans.Templates for gathering feedback and evaluating success.

      Clarity around leadership and vision.

      Well-defined plans for targeting unique groups with specific messages.

      Resistance and contingency plans.

      Templates for gathering feedback and evaluating success.

      Key Benefits Achieved

      Execute the transition in coordination with the timeline and structure of the core project.

      Communicate the action plan and vision for change.

      Target specific stakeholder and user groups with unique messages.

      Deal with risks, resistance, and contingencies.

      Evaluate success through feedback and metrics.

      Activities

      4.1 Sustain changes by adapting people, processes, and technologies to accept the transition.

      4.2 Decide which action to take on enablers and blockers.

      4.3 Start developing the training plan early to ensure training is properly timed and communicated.

      4.4 Sketch a communications timeline based on a classic change curve to accommodate natural resistance.

      4.5 Define plans to deal with resistance to change, objections, and fatigue.

      4.6 Consolidate and refine communication plan requirements for each stakeholder and group.

      4.7 Build the communications delivery plan.

      4.8 Define the feedback and evaluation process to ensure the project achieves its objectives.

      4.9 Formalize the transition plan.

      Outputs

      Training Plan

      Resistance Plan

      Communications Plan

      Transition Plan

      5 Institute an OCM Playbook through the PMO

      The Purpose

      Establish post-project benefits tracking timeline and commitment plans.

      Institute a playbook for managing organizational change, including:

      Key Benefits Achieved

      A process for ensuring the intended business outcomes are tracked and monitored after the project is completed.

      Repeat and scale best practices around organizational change to future PMO projects.

      Continue to build your capabilities around managing organizational change.

      Increase the effectiveness and value of organizational change management.

      Activities

      5.1 Review lessons learned to improve organizational change management as a core PM discipline.

      5.2 Monitor capacity for change.

      5.3 Define roles and responsibilities.

      5.4 Formalize and communicate the organizational change management playbook.

      5.5 Regularly reassess the value and success of organizational change management.

      Outputs

      Lessons learned

      Organizational Change Capability Assessment

      Organizational Change Management Playbook

      Further reading

      Master Organizational Change Management Practices

      PMOs, if you don't know who is responsible for org change, it's you.

      Analyst Perspective

      Don’t leave change up to chance.

      "Organizational change management has been a huge weakness for IT departments and business units, putting projects and programs at risk – especially large, complex, transformational projects.

      During workshops with clients, I find that the root of this problem is twofold: project planning tends to fixate on technology and neglects the behavioral and cultural factors that inhibit user adoption; further, accountabilities for managing change and helping to realize the intended business outcomes post-project are not properly defined.

      It makes sense for the PMO to be the org-change leader. In project ecosystems where no one seems willing to seize this opportunity, the PMO can take action and realize the benefits and accolades that will come from coordinating and consistently driving successful project outcomes."

      Matt Burton,

      Senior Manager, Project Portfolio Management

      Info-Tech Research Group

      Our understanding of the problem

      This Research is Designed For:

      • PMO Directors who need to improve user adoption rates and maximize benefits on project and program activity.
      • CIOs who are accountable for IT’s project spend and need to ensure an appropriate ROI on project investments.

      This Research Will Help You:

      • Define change management roles and accountabilities among project stakeholders.
      • Prepare end users for change impacts in order to improve adoption rates.
      • Ensure that the intended business outcomes of projects are more effectively realized.
      • Develop an organizational change management toolkit and best practices playbook.

      This Research Will Also Assist:

      • Project managers and change managers who need to plan and execute changes affecting people and processes.
      • Project sponsors who want to improve benefits attainment.
      • Business analysts who need to analyze the impact of change.

      This Research Will Help Them:

      • Develop communications and training plans tailored to specific audiences.
        • Identify strategies to manage cultural and behavioral change.
      • Maximize project benefits by ensuring changes are adopted.
      • Capitalize upon opportunities and mitigate risks.

      Drive organizational change from the PMO

      Situation

      • As project management office (PMO) leader, you oversee a portfolio of projects that depend heavily on users and stakeholders adopting new tools, complying with new policies, following new processes, and learning new skills.
      • You need to facilitate the organizational change resulting from these projects, ensuring that the intended business outcomes are realized.

      Complication

      • While IT takes accountability to deliver the change, accountability for the business outcomes is opaque with little or no allocated resourcing.
      • Project management practices focus more on the timely implementation of projects than on the achievement of the desired outcomes thereafter or on the behavioral and cultural factors that inhibit change from taking hold in the long term.

      Resolution

      • Plan for human nature. To ensure project success and maximize benefits, plan and facilitate the non-technical aspects of organizational change by addressing the emotional, behavioral, and cultural factors that foster stakeholder resistance and inhibit user adoption.
      • Make change management as ubiquitous as change itself. Foster a project culture that is proactive about OCM. Create a process where OCM considerations are factored in as early as project ideation and change is actively managed throughout the project lifecycle, including after the project has closed.
      • Equip project leaders with the right tools to foster adoption. Effective OCM requires an actionable toolkit that will help plant the seeds for organizational change. With the right tools and templates, the PMO can function as a hub for change, helping business units and project teams to consistently achieve project and post-project success.
      Info-Tech Insight

      Make your PMO the change leader it’s already expected to be. Unless accountabilities for organizational change management (OCM) have been otherwise explicitly defined, you should accept that, to the rest of the organization – including its chief officers – the PMO is already assumed to be the change leader.

      Don’t shy away from or neglect this role. It’s not just the business outcomes of the organization’s projects that will benefit; the long-term sustainability of the PMO itself will be significantly strengthened by making OCM a core competency.

      Completed projects aren’t necessarily successful projects

      The constraints that drive project management (time, scope, and budget) are insufficient for driving the overall success of project efforts.

      For instance, a project may come in on time, on budget, and in scope, but

      • …if users and stakeholders fail to adopt…
      • …and the intended benefits are not achieved…

      …then that “successful project” represents a massive waste of the organization’s time and resources.

      A supplement to project management is needed to ensure that the intended value is realized.

      Mission (Not) Accomplished

      50% Fifty percent of respondents in a KPMG survey indicated that projects fail to achieve what they originally intended. (Source: NZ Project management survey)

      56% Only fifty-six percent of strategic projects meet their original business goals. (Source: PMI)

      70% Lack of user adoption is the main cause for seventy percent of failed projects. (Source: Collins, 2013)

      Improve project outcomes with organizational change management

      Make “completed” synonymous with “successfully completed” by implementing an organizational change management strategy through the PMO.

      Organizational change management is the practice through which the PMO can improve user adoption rates and maximize project benefits.

      Why OCM effectiveness correlates to project success:

      • IT projects are justified because they will make money, save money, or make people happier.
      • Project benefits can only be realized when changes are successfully adopted or accommodated by the organization.

      Without OCM, IT might finish the project but fail to realize the intended outcomes.

      In the long term, a lack of OCM could erode IT’s ability to work with the business.

      The image shows a bar graph, titled Effective change management correlates with project success, with the X-axis labelled Project Success (Percent of respondents that met or exceeded project objectives), and the Y-axis labelled OCM-Effectiveness, with an arrow pointing upwards. The graph shows that with higher OCM-Effectiveness, Project Success is also higher. The source is given as Prosci’s 2014 Best Practices in Change Management benchmarking report.

      What is organizational change management?

      OCM is a framework for managing the introduction of new business processes and technologies to ensure stakeholder adoption.

      OCM involves tools, templates, and processes that are intended to help project leaders analyze the impacts of a change during the planning phase, engage stakeholders throughout the project lifecycle, as well as train and transition users towards the new technologies and processes being implemented.

      OCM is a separate body of knowledge, but as a practice it is inseparable from both project management or business analysis.

      WHEN IS OCM NEEDED?

      Anytime you are starting a project or program that will depend on users and stakeholders to give up their old way of doing things, change will force people to become novices again, leading to lost productivity and added stress.

      CM can help improve project outcomes on any project where you need people to adopt new tools and procedures, comply with new policies, learn new skills and behaviors, or understand and support new processes.

      "What is the goal of change management? Getting people to adopt a new way of doing business." – BA, Natural Resources Company

      The benefits of OCM range from more effective project execution to improved benefits attainment

      82% of CEOs identify organizational change management as a priority. (D&B Consulting) But Only 18% of organizations characterize themselves as “Highly Effective” at OCM. (PMI)

      On average, 95% percent of projects with excellent OCM meet or exceed their objectives. (Prosci) VS For projects with poor OCM, the number of projects that meet objectives drops to 15%. (Prosci)

      82% of projects with excellent OCM practices are completed on budget. (Prosci) VS For projects with poor OCM, the number of projects that stay on budget drops to 51%. (Prosci)

      71% of projects with excellent OCM practices stay on schedule. (Prosci) VS For projects with poor OCM practices, only 16% stay on schedule. (Prosci)

      While critical to project success, OCM remains one of IT’s biggest weaknesses and process improvement gaps

      IT Processes Ranked by Effectiveness:

      1. Risk Management
      2. Knowledge Management
      3. Release Management
      4. Innovation
      5. IT Governance
      6. Enterprise Architecture
      7. Quality Management
      8. Data Architecture
      9. Application Development Quality
      10. Data Quality
      11. Portfolio Management
      12. Configuration Management
      13. Application Portfolio Management
      14. Business Process Controls Internal Audit
      15. Organizational Change Management
      16. Application Development Throughput
      17. Business Intelligence Reporting
      18. Performance Measurement
      19. Manage Service Catalog

      IT Processes Ranked by Importance:

      1. Enterprise Application Selection & Implementation
      2. Organizational Change Management
      3. Data Architecture
      4. Quality Management
      5. Enterprise Architecture
      6. Business Intelligence Reporting
      7. Release Management
      8. Portfolio Management
      9. Application Maintenance
      10. Asset Management
      11. Vendor Management
      12. Application Portfolio Management
      13. Innovation
      14. Business Process Controls Internal Audit
      15. Configuration Management
      16. Performance Measurement
      17. Application Development Quality
      18. Application Development Throughput
      19. Manage Service Catalog

      Based on 3,884 responses to Info-Tech’s Management and Governance Diagnostic, June 2016

      There’s no getting around it: change is hard

      While the importance of change management is widely recognized across organizations, the statistics around change remain dismal.

      Indeed, it’s an understatement to say that change is difficult.

      People are generally – in the near-term at least – resistant to change, especially large, transformational changes that will impact the day-to-day way of doing things, or that involve changing personal values, social norms, and other deep-seated assumptions.

      "There is nothing more difficult to take in hand, more perilous to conduct, or more uncertain in its success, than to take the lead in the introduction of a new order of things." – Niccolo Machiavelli

      70% - Change failure rates are extremely high. It is estimated that up to seventy percent of all change initiatives fail – a figure that has held steady since the 1990s. (McKinsey & Company)

      25% - In a recent survey of 276 large and midsize organizations, only twenty-five percent of respondents felt that the gains from projects were sustained over time. (Towers Watson)

      22% - While eighty-seven percent of survey respondents trained their managers to “manage change,” only 22% felt the training was truly effective. (Towers Watson)

      While change is inherently difficult, the biggest obstacle to OCM success is a lack of accountability

      Who is accountable for change success? …anyone?...

      To its peril, OCM commonly falls into a grey area, somewhere in between project management and portfolio management, and somewhere in between being a concern of IT and a concern of the business.

      While OCM is a separate discipline from project management, it is commonly thought that OCM is something that project managers and project teams do. While in some cases this might be true, it is far from a universal truth.

      The end result: without a centralized approach, accountabilities for key OCM tasks are opaque at best – and the ball for these tasks is, more often than not, dropped altogether.

      29% - Twenty-nine percent of change initiatives are launched without any formal OCM plan whatsoever.

      "That’s 29 percent of leaders with blind faith in the power of prayer to Saint Jude, the patron saint of desperate cases and lost causes." – Torben Rick

      Bring accountability to org-change by facilitating the winds of change through the PMO

      Lasting organizational change requires a leader. Make it the PMO.

      #1 Organizational resistance to change is cited as the #1 challenge to project success that PMOs face. (Source: PM Solutions)

      90% Companies with mature PMOs that effectively manage change meet expectations 90% of the time. (Source: Jacobs-Long)

      Why the PMO?

      A centralized approach to OCM is most effective, and the PMO is already a centralized project office and is already accountable for project outcomes.

      What’s more, in organizations where accountabilities for OCM are not explicitly defined, the PMO will likely already be assumed to be the default change leader by the wider organization.

      It makes sense for the PMO to accept this accountability – in the short term at least – and claim the benefits that will come from coordinating and consistently driving successful project outcomes.

      In the long term, OCM leadership will help the PMO to become a strategic partner with the executive layer and the business side.

      Short-term gains made by the PMO can be used to spark dialogues with those who authorize project spending and have the implicit fiduciary obligation to drive project benefits.

      Ultimately, it’s their job to explicitly transfer that obligation, along with the commensurate resourcing and authority for OCM activities.

      More than a value-added service, OCM competencies will soon determine the success of the PMO itself

      Given the increasingly dynamic nature of market conditions, the need for PMOs to provide change leadership on projects large and small is becoming a necessity.

      "With organizations demanding increasing value, PMOs will need to focus more and more on strategy, innovation, agility, and stakeholder engagement. And, in particular, developing expertise in organizational change management will be essential to their success." – PM Solutions, 2014

      28% PMOs that are highly agile and able to respond quickly to changing conditions are 28% more likely to successfully complete strategic initiatives (69% vs. 41%). (PMI)

      In other words, without heightened competencies around org-change, the PMO of tomorrow will surely sink like a stone in the face of increasingly unstable external factors and accelerated project demands.

      Use Info-Tech’s road-tested OCM toolkit to transform your PMO into a hub of change management leadership

      With the advice and tools in Info-Tech’s Drive Organizational Change from the PMO blueprint, the PMO can provide the right OCM expertise at each phase of a project.

      The graphic has an image of a windmill at centre, with PMO written directly below it. Several areas of expertise are listed in boxes emerging out of the PMO, which line up with project phases as follows (project phase listed first, then area of expertise): Initiation - Impact Assessment; Planning - Stakeholder Engagement; Execution - Transition Planning; Monitoring & Controlling - Communications Execution; Closing - Evaluation & Monitoring.

      Info-Tech’s approach to OCM is a practical/tactical adaptation of several successful models

      Business strategy-oriented OCM models such as John Kotter’s 8-Step model assume the change agent is in a position of senior leadership, able to shape corporate vision, culture, and values.

      • PMO leaders can work with business leaders, but ultimately can’t decide where to take the organization.
      • Work with business leaders to ensure IT-enabled change helps reinforce the organization’s target vision and culture.

      General-purpose OCM frameworks such as ACMP’s Standard for Change Management, CMI’s CMBoK, and Prosci’s ADKAR model are very comprehensive and need to be configured to PMO-specific initiatives.

      • Tailoring a comprehensive, general-purpose framework to PMO-enabled change requires familiarity and experience.

      References and Further Reading

      Info-Tech’s organizational change management model adapts the best practices from a wide range of proven models and distills it into a step-by-step process that can be applied to any IT-enabled project.

      Info-Tech’s OCM research is COBIT aligned and a cornerstone in our IT Management & Governance Framework

      COBIT Section COBIT Management Practice Related Blueprint Steps
      BAI05.01 Establish the desire to change. 1.1 / 2.1 / 2.2
      BAI05.02 Form an effective implementation team. 1.2
      BAI05.03 Communicate the desired vision. 2.1 / 3.2
      BAI05.03 Empower role players and identify short-term wins. 3.2 / 3.3
      BAI05.05 Enable operation and use. 3.1
      BAI05.06 Embed new approaches. 4.1 / 5.1
      BAI05.07 Sustain changes. 5.1

      COBIT 5 is the leading framework for the governance and management of enterprise IT.

      Screenshot of Info-Tech’s IT Management & Governance Framework.

      The image is a screenshot of Info-Tech's IT Management & Governance Framework (linked above). There is an arrow emerging from the screenshot, which offers a zoomed-in view of one of the sections of the framework, which reads BAI05 Organizational Change Management.

      Consider Info-Tech’s additional key observations

      Human behavior is largely a blind spot during the planning phase.

      In IT especially, project planning tends to fixate on technology and underestimate the behavioral and cultural factors that inhibit user adoption. Whether change is project-specific or continuous, it’s more important to instill the desire to change than to apply specific tools and techniques. Accountability for instilling this desire should start with the project sponsor, with direct support from the PMO.

      Don’t mistake change management for a “soft” skill.

      Persuading people to change requires a “soft,” empathetic approach to keep them motivated and engaged. But don’t mistake “soft” for easy. Managing the people part of change is amongst the toughest work there is, and it requires a comfort and competency with uncertainty, ambiguity, and conflict. If a change initiative is going to be successful (especially a large, transformational change), this tough work needs to be done – and the more impactful the change, the earlier it is done, the better.

      In “continuous change” environments, change still needs to be managed.

      Transformation and change are increasingly becoming the new normal. While this normality may help make people more open to change in general, specific changes still need to be planned, communicated, and managed. Agility and continuous improvement are good, but can degenerate into volatility if change isn’t managed properly. People will perceive change to be volatile and undesirable if their expectations aren’t managed through communications and engagement planning.

      Info-Tech’s centralized approach to OCM is cost effective, with a palpable impact on project ROI

      Info-Tech’s Drive Organizational Change from the PMO blueprint can be implemented quickly and can usually be done with the PMO’s own authority, without the need for additional or dedicated change resources.

      Implementation Timeline

      • Info-Tech’s easy-to-navigate OCM tools can be employed right away, when your project is already in progress.
      • A full-scale implementation of a PMO-driven OCM program can be accomplished in 3–4 weeks.

      Implementation Personnel

      • Primary: the PMO director (should budget 10%–15% of her/his project capacity for OCM activities).
      • Secondary: other PMO staff (e.g. project managers, business analysts, etc.).

      OCM Implementation Costs

      15% - The average costs for effective OCM are 10%–15% of the overall project budget. (AMR Research)

      Average OCM Return-on-Investment

      200% - Small projects with excellent OCM practices report a 200% return-on-investment. (Change First)

      650% - Large projects with excellent OCM practices report a 650% return-on-investment. (Change First)

      Company saves 2–4 weeks of time and $10,000 in ERP implementation through responsible OCM

      CASE STUDY

      Industry Manufacturing

      Source Info-Tech Client

      Situation

      A medium-sized manufacturing company with offices all over the world was going through a consolidation of processes and data by implementing a corporate-wide ERP system to replace the fragmented systems that were previously in place. The goal was to have consistency in process, expectations, and quality, as well as improve efficiency in interdepartmental processes.

      Up to this point, every subsidiary was using their own system to track data and sharing information was complicated and slow. It was causing key business opportunities to be compromised or even lost.

      Complication

      The organization was not very good in closing out projects. Initiatives went on for too long, and the original business benefits were usually not realized.

      The primary culprit was recognized as mismanaged organizational change. People weren’t aware early enough, and were often left out of the feedback process.

      Employees often felt like changes were being dictated to them, and they didn’t understand the wider benefits of the changes. This led to an unnecessary number of resistors, adding to the complexity of successfully completing a project.

      Resolution

      Implementing an ERP worldwide was something that the company couldn’t gamble on, so proper organizational change management was a focus.

      A thorough stakeholder analysis was done, and champions were identified for each stakeholder group throughout the organization.

      Involving these champions early gave them the time to work within their groups and to manage expectations. The result was savings of 2–4 weeks of implementation time and $10,000.

      Follow Info-Tech’s blueprint to transform your PMO into a hub for organizational change management

      Prepare the PMO for Change Leadership

      • Assess the organization’s readiness for change.
        • Perform an OCM capabilities assessment.
        • Chart an OCM roadmap for the PMO.
        • Undergo a change management SWOT analysis.
        • Define success criteria.
        • Org. Change Capabilities Assessment
      • Define the structure and scope of the PMO’s pilot OCM initiative.
        • Determine pilot OCM project.
        • Estimate OCM effort.
        • Document high-level project details.
        • Establish a timeline for org-change activities.
        • Assess available resources to support the PMO’s OCM initiative.
        • Project Level Assessment

      Plant the Seeds for Change During Project Planning and Initiation

      • Foster OCM considerations during the ideation phase.
        • Assess leadership support for change
        • Highlight the goals and benefits of the change
        • Refine your change story
        • Define success criteria
        • Develop a sponsorship action plan
        • Transition Team Communications Template
      • Perform an organizational change impact assessment.
        • Perform change impact survey.
        • Assess the depth of impact for the stakeholder group.
        • Determine overall adoptability of the OCM effort.
        • Review risks and opportunities.
        • Org. Change Management Impact Analysis Tool

      Facilitate Change Adoption Throughout the Organization

      • Ensure stakeholders are engaged and ready for change.
        • Involve the right people in change and define roles.
        • Define methods for obtaining stakeholder input.
        • Perform a stakeholder analysis.
        • Stakeholder Engagement Workbook
      • Develop and execute the transition plan.
        • Establish a communications strategy for stakeholder groups.
        • Define the feedback and evaluation process.
        • Assess the full range of support and resistance to change.
        • Develop an objections handling process.
        • Transition Plan Template
      • Establish HR and training plans.
        • Assess training needs. Develop training plan.
        • Training Plan

      Establish a Post-Project Benefits Attainment Process

      • Determine accountabilities for benefits attainment.
        • Conduct a post-implementation review of the pilot OCM project.
        • Assign ownership for realizing benefits after the project is closed.
        • Define a post-project benefits tracking process.
        • Implement a tool to help monitor and track benefits over the long term.
        • Project Benefits Tracking Tool

      Solidify the PMO’s Role as Change Leader

      • Institute an OCM playbook.
        • Review lessons learned to improve OCM as a core discipline of the PMO.
        • Monitor organizational capacity for change.
        • Define roles and responsibilities for OCM oversight.
        • Formalize the Organizational Change Management Playbook.
        • Assess the value and success of your practices relative to OCM effort and project outcomes.
        • Organizational Change Management Playbook

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

      Guided Implementation

      “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”

      Workshop

      “We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”

      Consulting

      “Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

      Diagnostics and consistent frameworks used throughout all four options

      Drive Organizational Change from the PMO

      Phase 1 Phase 2 Phase 3 Phase 4 Phase 5
      Best-Practice Toolkit

      1.1 Assess the organization’s readiness for change.

      1.2 Define the structure and scope of the PMO’s pilot OCM initiative.

      2.1 Foster OCM considerations during the ideation phase.

      2.2 Perform an organizational change impact assessment.

      3.1 Ensure stakeholders are engaged and ready for change.

      3.2 Develop and execute the transition plan.

      3.3 Establish HR and training plans.

      4.1 Determine accountabilities for benefits attainment. 5.1 Institute an OCM playbook.
      Guided Implementations
      • Scoping Call.
      • Review the PMO’s and the organization’s change capabilities.
      • Determine an OCM pilot initiative.
      • Define a sponsorship action plan for change initiatives.
      • Undergo a change impact assessment.
      • Perform a stakeholder analysis.
      • Prepare a communications strategy based on stakeholder types.
      • Develop training plans.
      • Establish a post-project benefits tracking process.
      • Implement a tracking tool.
      • Evaluate the effectiveness of OCM practices.
      • Formalize an OCM playbook for the organization’s projects.
      Onsite Workshop

      Module 1:

      Prepare the PMO for change leadership.

      Module 2:

      Plant the seeds for change during planning and initiation.

      Module 3:

      Facilitate change adoption throughout the organization.

      Module 4:

      Establish a post-project benefits attainment process.

      Module 5:

      Solidify the PMO’s role as change leader.

      Phase 1 Results:

      OCM Capabilities Assessment

      Phase 2 Results:

      Change Impact Analysis

      Phase 3 Results:

      Communications and Transition Plans

      Phase 4 Results:

      A benefits tracking process for sponsors

      Phase 5 Results:

      OCM Playbook

      Workshop overview

      Contact your account representative or email Workshops@InfoTech.com for more information.

      Preparation Workshop Day 1 Workshop Day 2 Workshop Day 3 Workshop Day 4
      Activities

      Organize and Plan Workshop

      • Finalize workshop itinerary and scope.
      • Identify workshop participants.
      • Gather strategic documentation.
      • Engage necessary stakeholders.
      • Book interviews.

      Assess OCM Capabilities

      • Assess current organizational change management capabilities.
      • Conduct change management SWOT analysis.
      • Define change management success metrics.
      • Define core pilot OCM project.

      Analyze Impact of the Change

      • Analyse the impact of the change across multiple dimensions and stakeholder groups.
      • Create an impact management plan.
      • Analyze impacts to product with risk and opportunity assessments.

      Develop Engagement & Transition Plans

      • Perform stakeholder analysis to identify change champions and blockers.
      • Document comm./training requirements and delivery plan.
      • Define plans to deal with resistance.
      • Validate and test the transition plan.

      Institute an OCM Playbook

      • Define feedback and evaluation process.
      • Finalize communications, transition, and training plans.
      • Establish benefits tracking timeline and commitment plans.
      • Define roles and responsibilities for ongoing organizational change management.
      Deliverables
      • Workshop Itinerary
      • Workshop Participant List
      • Defined Org Change Mandate
      • Organizational Change Capabilities Assessment
      • SWOT Assessment
      • Value Metrics
      • Project Level Assessment/Project Definition
      • Project Sponsor Action Plan
      • Organizational Change Impact Analysis Tool
      • Risk Assessment
      • Opportunity Assessment
      • Stakeholder Engagement Workbook
      • Communications Plan
      • Training Plan
      • Resistance Plan
      • Transition Team
      • Communications Template
      • Evaluation Plan
      • Post-Project Benefits Tracking Timelines and Accountabilities
      • OCM Playbook

      Phase 1

      Prepare the PMO for Change Leadership

      Phase 1 outline

      Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

      Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 1: Prepare the PMO for Change Leadership

      Proposed Time to Completion (in weeks): 1 week

      Step 1.1: Assess the organization’s readiness for change

      Start with an analyst kick off call:

      • Scoping call to discuss organizational change challenges and the PMO’s role in managing change.

      Then complete these activities…

      • Perform an assessment survey to define capability levels and chart an OCM roadmap.

      With these tools & templates:

      • Organizational Change Management Capabilities Assessment
      Step 1.2: Define the structure and scope of the PMO’s pilot OCM initiative

      Work with an analyst to:

      • Determine the appropriate OCM initiative to pilot over this series of Guided Implementations from the PMO’s project list.

      Then complete these activities…

      • Rightsize your OCM planning efforts based on project size, timeline, and resource availability.

      With these tools & templates:

      • Project Level Assessment Tool

      Step 1.1: Assess the organization’s readiness for change

      Phase 1 - 1.1

      This step will walk you through the following activities:
      • Perform an OCM capabilities assessment.
      • Chart an OCM roadmap for the PMO.
      • Undergo a change management SWOT analysis.
      • Define success criteria.
      This step involves the following participants:
      • Required: PMO Director
      • Recommended: PMO staff, project management staff, and other project stakeholders
      Outcomes of this step
      • An OCM roadmap for the PMO with specific recommendations.
      • An assessment of strengths, weakness, challenges, and threats in terms of the PMO’s role as organizational change leader.
      • Success metrics for the PMO’s OCM implementation.

      Project leaders who successfully facilitate change are strategic assets in a world of increasing agility and uncertainty

      As transformation and change become the new normal, it’s up to PMOs to provide stability and direction during times of transition and turbulence.

      Continuous change and transition are increasingly common in organizations in 2016.

      A state of constant change can make managing change more difficult in some ways, but easier in others.

      • Inundation with communications and diversity of channels means the traditional “broadcast” approach to communicating change doesn’t work (i.e. you can’t expect every email to get everyone’s attention).
      • People might be more open to change in general, but specific changes still need to be properly planned, communicated, and managed.

      By managing organizational change more effectively, the PMO can build credibility to manage both business and IT projects.

      "The greatest danger in times of turbulence is not the turbulence; it is to act with yesterday’s logic." – Peter Drucker

      In this phase, we will gauge your PMO’s abilities to effectively facilitate change based upon your change management capability levels and your wider organization’s responsiveness to change.

      Evaluate your current capabilities for managing organizational change

      Start off by ensuring that the PMO is sensitive to the particularities of the organization and that it manages change accordingly.

      There are many moving parts involved in successfully realizing an organizational change.

      For instance, even with an effective change toolkit and strong leadership support, you may still fail to achieve project benefits due to such factors as a staff environment resistant to change or poor process discipline.

      Use Info-Tech’s Organizational Change Management Capabilities Assessment to assess your readiness for change across 7 categories:

      • Cultural Readiness
      • Leadership & Sponsorship
      • Organizational Knowledge
      • Change Management Skills
      • Toolkit & Templates
      • Process Discipline
      • KPIs & Metrics

      Download Info-Tech’s Organizational Change Management Capabilities Assessment.

      • The survey can be completed quickly in 5 to 10 minutes; or, if being done as a group activity, it can take up to 60 minutes or more.
      • Based upon your answers, you will get a report of your current change capabilities to help you prioritize your next steps.
      • The tool also provides a customized list of Info-Tech recommendations across the seven categories.

      Perform Info-Tech’s OCM capabilities questionnaire

      1.1.1 Anywhere from 10 to 60 minutes (depending on number of participants)

      • The questionnaire on Tab 2 of the Assessment consists of 21 questions across 7 categories.
      • The survey can be completed individually, by the PMO director or manager, or – even more ideally – by a group of project and business stakeholders.
      • While the questionnaire only takes a few minutes to complete, you may wish to survey a wider swath of business units, especially on such categories as “Cultural Readiness” and “Leadership Support.”

      The image is a screen capture of tab 2 of the Organizational Change Management Capabilities Assessment.

      Use the drop downs to indicate the degree to which you agree or disagree with each of the statements in the survey.

      Info-Tech Insight

      Every organization has some change management capability.

      Even if you find yourself in a fledgling or nascent PMO, with no formal change management tools or processes, you can still leverage other categories of change management effectiveness.

      If you can, build upon people-related assets like “Organizational Knowledge” and “Cultural Readiness” as you start to hone your OCM toolkit and process.

      Review your capability levels and chart an OCM roadmap for your PMO

      Tab 3 of the Assessment tool shows your capabilities graph.

      • The chart visualizes your capability levels across the seven categories of organization change covered in the questionnaire in order to show the areas that your organization is already strong in and the areas where you need to focus your efforts.

      The image is a screen capture of tab 3 of the Organizational Change Management Capabilities Assessment.

      Focus on improving the first capability dimension (from left/front to right/back) that rates below 10.

      Tab 4 of the Assessment tool reveals Info-Tech’s recommendations based upon your survey responses.

      • Use these recommendations to structure your roadmap and bring concrete definitions to your next steps.

      The image is a screen capture of tab 4 of the Organizational Change Management Capabilities Assessment.

      Use the red/yellow/green boxes to focus your efforts.

      The content in the recommendations boxes is based around these categories and the advice therein is designed to help you to, in the near term, bring your capabilities up to the next level.

      Use the steps in this blueprint to help build your capabilities

      Each of Info-Tech’s seven OCM capabilities match up with different steps and phases in this blueprint.

      We recommend that you consume this blueprint in a linear fashion, as each phase matches up to a different set of OCM activities to be executed at each phase of a project. However, you can use the legend below to locate how and where this blueprint will address each capability.

      Cultural Readiness 2.1 / 2.2 / 3.1 / 3.2 / 3.3
      Leadership Support 2.1 / 4.1 / 5.1
      Organizational Knowledge 2.1 / 3.1 / 3.2
      Change Management Skills 2.1 / 2.2 / 3.1 / 3.2 / 3.3
      Toolkit & Templates 2.1 / 2.2 / 3.1 / 3.2 / 3.3 / 4.1 / 5.1
      Process Discipline 2.1 / 2.2 / 3.1 / 3.2 / 3.3 / 4.1 / 5.1
      KPIs & Metrics 3.2 / 5.1

      Info-Tech Insight

      Organizational change must be planned in advance and managed through all phases of a project.

      Organizational change management must be embedded as a key aspect throughout the project, not merely a set of tactics added to execution phases.

      Perform a change management SWOT exercise

      1.1.2 30 to 60 minutes

      Now that you have a sense of your change management strengths and weaknesses, you can begin to formalize the organizational specifics of these.

      Gather PMO and IT staff, as well as other key project and business stakeholders, and perform a SWOT analysis based on your Capabilities Assessment.

      Follow these steps to complete the SWOT analysis:

      1. Have participants discuss and identify Strengths, Weaknesses, Opportunities, and Threats.
      2. Spend roughly 60 minutes on this. Use a whiteboard, flip chart, or PowerPoint slide to document results of the discussion as points are made.
      3. Make sure results are recorded and saved either using the template provided on the next slide or by taking a picture of the whiteboard or flip chart.

      Use the SWOT Analysis Template on the next slide to document results.

      Use the examples provided in the SWOT analysis to kick-start the discussion.

      The purpose of the SWOT is to begin to define the goals of this implementation by assessing your change management capabilities and cultivating executive level, business unit, PMO, and IT alignment around the most critical opportunities and challenges.

      Sample SWOT Analysis

      Strengths

      • Knowledge, skills, and talent of project staff.
      • Good working relationship between IT and business units.
      • Other PMO processes are strong and well adhered to by project staff.
      • Motivation to get things done when priorities, goals, and action plans are clear.

      Weaknesses

      • Project leads lack formal training in change management.
      • IT tried to introduce org change processes in the past, but we failed. Staff were unsure of which templates to use and how/when/why to use them.
      • We can’t designate individuals as change agents. We lack sufficient resources.
      • We’ve had some fairly significant change failures in the past and some skepticism and pessimism has taken root in the business units.

      Opportunities

      • The PMO is strong and well established in the organization, with a history of facilitating successful process discipline.
      • The new incoming CEO has already paid lip service to change and transformation. We should be able to leverage their support as we formalize these processes.
      • We have good lines of project communication already in place via our bi-weekly project reporting meetings. We can add change management matters to the agenda of these meetings.

      Threats

      • Additional processes and documentation around change management could be viewed as burdensome overhead. Adoption is uncertain.
      • OCM success depends on multiple stakeholders and business units coming together; with so many moving parts, we can’t be assured that an OCM program will survive long term.

      Define the “how” and the “what” of change management success for your PMO

      1.1.3 30 to 60 minutes

      Before you move on to develop and implement your OCM processes, spend some time documenting how change management success will be defined for your organization and what conditions will be necessary for success to be achieved.

      With the same group of individuals who participated in the SWOT exercise, discuss the below criteria. You can make this a sticky note or a whiteboard activity to help document discussion points.

      OCM Measured Value Metrics Include:
      • Estimate % of expected business benefits realized on the past 3–5 significant projects/programs.
        • Track business benefits (costs reduced, productivity increased, etc.).
      • Estimate costs avoided/reduced (extensions, cancellations, delays, roll-backs, etc.).
        • Establish baseline by estimating average costs of projects extended to deal with change-related issues.
      What conditions are necessary for OCM to succeed? How will success be defined?
      • e.g. The PMO will need the support of senior leaders and business units.
      • e.g. 20% improvement in benefits realization numbers within the next 12 months.
      • e.g. The PMO will need to establish a portal to help with organization-wide communications.
      • e.g. 30% increase in adoption rates on new software and technology projects within the next 12 months.

      Document additional items that could impact an OCM implementation for your PMO

      1.1.4 15 to 45 minutes

      Use the table below to document any additional factors or uncertainties that could impact implementation success.

      These could be external factors that may impact the PMO, or they could be logistical considerations pertaining to staffing or infrastructure that may be required to support additional change management processes and procedures.

      "[A]ll bets are off when it comes to change. People scatter in all directions. Your past experiences may help in some way, but what you do today and how you do it are the new measures people will use to evaluate you." – Tres Roeder

      Consideration Description of Need Potential Resource Implications Potential Next Steps Timeline
      e.g. The PMO will need to train PMs concerning new processes. We will not only need to train PM staff in the new processes and documentation requirements, but we will also have to provide ongoing training, be it monthly, quarterly, or yearly. Members of PMO staff will be required to support this training. Analyze impact of redeploying existing resources vs. outsourcing. Q3 2016
      e.g. We will need to communicate new OCM requirements to the business and wider organization. The PMO will be taking on added communication requirements, needing to advertise to a wider audience than it has before. None Work with business side to expand the PMO’s communications network and look into leveraging existing communication portals. Next month

      Step 1.2: Define the structure and scope of the PMO’s pilot OCM initiative

      Phase 1 - 1.2

      This step will walk you through the following activities:
      • Determine pilot OCM project.
      • Estimate OCM effort.
      • Document high-level project details.
      • Establish a timeline for org change activities.
      • Assess available resources to support the PMO’s OCM initiative.
      This step involves the following participants:
      • Required: PMO Director
      • Recommended: PMO staff, project management staff, and other project stakeholders
      Outcomes of this step
      • Project definition for the PMO’s pilot OCM initiative.
      • A timeline that aligns the project schedule for key OCM activities.
      • Definition of resource availability to support OCM activities through the PMO.

      Organizational change discipline should align with project structure

      Change management success is contingent on doing the right things at the right time.

      In subsequent phases of this blueprint, we will help the PMO develop an OCM strategy that aligns with your organization’s project timelines.

      In this step (1.2), we will do some pre-work for you by determining a change initiative to pilot during this process and defining some of the roles and responsibilities for the OCM activities that we’ll develop in this blueprint.

      The image shows a sample project timeline with corresponding OCM requirements.

      Get ready to develop and pilot your OCM competencies on a specific project

      In keeping with the need to align organizational change management activities with the actual timeline of the project, the next three phases of this blueprint will move from discussing OCM in general to applying OCM considerations to a single project.

      As you narrow your focus to the organizational change stemming from a specific initiative, review the below considerations to help inform the decisions that you make during the activities in this step.

      Choose a pilot project that:

      • Has an identifiable sponsor who will be willing and able to participate in the bulk of the activities during the workshop.
      • Has an appropriate level of change associated with it in order to adequately develop a range of OCM capabilities.
      • Has a reasonably well-defined scope and timeline – you don’t want the pilot initiative being dragged out unexpectedly.
      • Has PMO/IT staff who will be assisting with OCM efforts and will be relatively familiar and comfortable with them in terms of technical requirements.

      Select a specific project that involves significant organizational change

      1.2.1 5 to 15 minutes

      The need for OCM rigor will vary depending on project size and complexity.

      While we recommend that every project has some aspect of change management to it, you can adjust OCM requirements accordingly, depending on the type of change being introduced.

      Incremental Change Transformational Change

      Organizational change management is highly recommended and beneficial for projects that require people to:

      • Adopt new tools and workflows.
      • Learn new skills.
      • Comply with new policies and procedures.
      • Stop using old tools and workflows.

      Organizational change management is required for projects that require people to:

      • Move into different roles, reporting structures, and career paths.
      • Embrace new responsibilities, goals, reward systems, and values
      • Grow out of old habits, ideas, and behaviors.
      • Lose stature in the organization.

      Phases 2, 3, and 4 of this blueprint will guide you through the process of managing organizational change around a specific project. Select one now that is currently in your request or planning stages to pilot through the activities in this blueprint. We recommend choosing one that involves a large, transformational change.

      Estimate the overall difficulty and effort required to manage organizational change

      1.2.2 5 minutes

      Use Info-Tech’s project levels to define the complexity of the project that you’ve chosen to pilot.

      Defining your project level will help determine how much effort and detail is required to complete steps in this blueprint – and, beyond this, these levels can help you determine how much OCM rigor to apply across each of the projects in your portfolio.

      Incremental Change Transformational Change
      Level 1 Level 2 Level 3
      • Low risk and complexity.
      • Routine projects with limited exposure to the business and low risk of negative impact.
      • Examples: infrastructure upgrades, application refreshes, etc.
      • Medium risk and complexity.
      • Projects with broader exposure that present a moderate level of risk to business operations.
      • Examples: Move or renovate locations, cloud migration, BYOD strategy, etc.
      • High risk and complexity.
      • Projects that affect multiple lines of business and have significant costs and/or risks.
      • Examples: ERP implementation, corporate merger, business model innovation, etc.

      For a more comprehensive assessment of project levels and degrees of risk, see Info-Tech’s Create Project Management Success blueprint – and in particular, our Project Level Assessment Tool.

      Record the goals and scope of the pilot OCM initiative

      1.2.3 15 to 30 minutes

      Description

      What is the project changing?

      How will it work?

      What are the implications of doing nothing?

      What are the phases in execution?

      Expected Benefits

      What is the desired outcome?

      What can be measured? How?

      When should it be measured?

      Goals

      List the goals.

      Align with business and IT goals.

      Expected Costs

      List the costs:

      Software costs

      Hardware costs

      Implementation costs

      Expected Risks

      List the risks:

      Business risks

      Technology risks

      Implementation risks

      Planned Project Activities & Milestones Timeline Owner(s) Status
      1. Example: Vendor Evaluation Finish by Q4-17 Jessie Villar In progress
      2. Example: Define Administrative Policies Finish by Q4-17 Gerry Anantha Starting Q2

      Know the “what” and “when” of org change activities

      The key to change management success is ensuring that the right OCM activities are carried out at the right time. The below graphic serves as a quick view of what OCM activities entail and when they should be done.

      The image is the sample project timeline previously shown, but with additional notes for each segment of the Gantt chart. The notes are as follows: Impact Assessment - Start assessing the impact of change during planning and requirements gathering stages; Stakeholder Engagement - Use requirements gathering and design activities as opportunities to engage stakeholders and users; Transition Planning - The development period provides time for the change manager to develop and refine the transition plan (including communications and training). Change managers need to collaborate with development teams to ensure scope and schedule stay aligned, especially in Agile environments); Communications Execution - Communications should occur early and often, beginning well before change affects people and continuing long enough to reinforce change by celebrating success; Training - Training needs to be well timed to coincide with implementation; Quick Wins - Celebrate early successes to show that change is working; Evaluation & Monitoring - Adoption of change is a key to benefits realization. Don’t declare the project over until adoption of change is proven.

      Rough out a timeline for the org change activities associated with your pilot project’s timeline

      1.2.4 20-30 minutes

      With reference to the graphic on the previous slide, map out a high-level timeline for your pilot project’s milestones and the corresponding OCM activities.
      • This is essentially a first draft of a timeline and will be refined as we develop your OCM discipline in the next phase of this blueprint.
      • The purpose of roughing something out at this time is to help determine the scope of the implementation, the effort involved, and to help with resource planning.
      Project Phase or Milestone Estimated Start Date Estimated End Date Associated OCM Requirement(s)
      e.g. Planning e.g. Already in progress e.g. July e.g. Impact Assessment
      e.g. Requirements & Design e.g. August e.g. October e.g. Stakeholder Engagement & Transition Planning

      Info-Tech Insight

      Proactive change management is easier to execute and infinitely more effective than managing change reactively. A reactive approach to OCM is bound to fail. The better equipped the PMO is to plan OCM activities in advance of projects, the more effective those OCM efforts will be.

      Assess the roles and resources that might be needed to help support these OCM efforts

      1.2.5 30 minutes

      The PMO leader will need to delegate responsibility for many to all of these OCM activities throughout the project lifecycle.

      Compile a list of PMO staff, project workers, and other stakeholders who will likely be required to support these processes at each step, keeping in mind that we will be doing a more thorough consideration of the resources required to support an OCM program in Phase 3.

      OCM Activity Resources Available to Support
      Impact Assessment
      Stakeholder Engagement
      Transition Planning
      Training
      Communications
      Evaluation and Monitoring

      Info-Tech Insight

      OCM processes require a diverse network to support them.

      While we advocate an approach to org change that is centralized through the PMO, this doesn’t change the fact that the PMO’s OCM processes will need to engage the entirety of the project eco-system.

      In addition to IT/PMO directors, org change processes will engage a group as varied as project sponsors, project managers, business analysts, communications leads, and HR/training leads.

      Ensure that you are considering resources and infrastructure beyond IT as you plan your OCM processes – and engage these stakeholders early in this planning process.

      Establish core transition team roles and a reporting structure

      1.2.6 30 minutes

      Once you’ve identified OCM resources and assessed their availability, start to sketch the structure of the core transition team.

      In many cases, the core team only has one or two people responsible for impact analysis and plan development in addition to you, the sponsor, who is accountable for leadership and benefits realization.

      For larger initiatives, the core team might include several co-sponsors or advisors from different departments or lines of business, along with a handful of staff working together on analysis and planning.

      Some team structure templates/examples:

      Small (e.g. Office 365)

      • Sponsor
      • PM/BA

      Medium-Large (e.g. business process initiative)

      • Sponsor
      • PM
      • BA
      • OCM Consultant

      Complex Transformational (e.g. business model initiative, company reorg)

      • Exec. Sponsor (CxO)
      • Steering Committee
      • Project Lead/Champion (VP)
      • Business Lead(s)
      • IT Lead
      • HR/Training Lead
      • OCM Consultant

      Ultimately, organizational change is a collaborative effort

      Effective organizational change involves overlapping responsibilities.

      In keeping with the eclectic network of stakeholders that is required to support OCM processes, Phase 2 is broken up into sections that will, by turn, engage project sponsors, project managers, business analysts, communications leads, and HR/training leads.

      At each step, our intention is to arm the PMO with a toolkit and a set of processes that will help foster a project culture that is proactive about change.

      "It is amazing what you can accomplish if you do not care who gets the credit." – Harry Truman

      Project Step PMO Sponsor Project Manager Business Analyst Blueprint Reference
      Make a high-level case for change.

      A

      R R/C C 1.1
      Initiate project/change planning. A C R C 1.2
      Analyze full breadth and depth of impact. A C R R 1.3
      Assess communications and training requirements. A C R R 2.1
      Develop communications, training, and other transition plans. A R C R 2.2-3
      Approve and communicate transition plans. A C R C 2.4
      Analyze impact and progress. A C R R 3.1
      Revise project/change planning. A C R C 3.2
      Highlight and leverage successes. A R C C 3.3

      Update the Transition Team Communications Template

      1.2.7 10 minutes

      Participants
      • PMO leader
      • PMO staff
      Input
      • The outcomes of various activities in this step
      Output
      • Key sections of the Transition Team Communications Template completed

      Use Info-Tech’s Transition Team Communications Template to help communicate the outcomes of this step.

      • Use the template to document the goals, benefits, and milestones established in 1.2.3, to record the project timeline and schedule for OCM activities from 1.2.4, to document resources available for OCM activities (1.2.5), and to record the membership and reporting structure of the core transition team (1.2.6).

      Download Info-Tech’s Transition Team Communications Template.

      "Managers and user communities need to feel like they are a part of a project instead of feeling like the project is happening to them. It isn't just a matter of sending a few emails or putting up a page on a project website." Ross Latham

      Build organizational change management capabilities by bringing in required skills

      Case Study

      Industry Natural Resources

      Source Interview

      Challenge
      • Like many organizations, the company is undergoing increasing IT-enabled change.
      • Project managers tended to react to effects of change rather than proactively planning for change.

      "The hard systems – they’re easy. It’s the soft systems that are challenging... Be hard on the process. Be easy on the people." – Business Analyst, natural resources company

      Solution
      • Change management was especially challenging when projects were led by the business.
      • IT was often brought in late in business-led projects.
      • As a result, the organization incurred avoidable costs to deal with integration, retraining, etc.
      • The cost of managing change grows later in the project as more effort needs to be spent undoing (or “unfreezing”) the old state or remediating poorly executed change.
      Results
      • The company hired a business analyst with a background in organizational change to bring in the necessary skills.
      • The business analyst brought knowledge, experience, and templates based on best practices and is sharing these with the rest of the project management team.
      • As a result, organizational change management is starting earlier in projects when its effectiveness and value are maximized.

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      1.1.1 Evaluate your current capabilities for managing organizational change

      Take Info-Tech’s OCM capabilities questionnaire and receive custom analyst recommendations concerning next steps.

      1.1.2 Perform a change management SWOT exercise

      Work with a seasoned analyst to assess your PMO’s strengths, weaknesses, opportunities, and threats to becoming an org change leader.

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      1.1.3 Define success metrics for your PMO’s efforts to become an org change leader

      Work with an analyst to clarify how the success of this initiative will be measured and what conditions are necessary for success.

      1.2.2 Determine the appropriate OCM initiative to pilot at your organization

      Receive custom analyst insights on rightsizing your OCM planning efforts based on project size, timeline, and resource availability.

      1.2.4 Develop an OCM timeline that aligns with key project milestones

      Harness analyst experience to develop a project-specific timeline for the PMO’s change management activities to better plan your efforts and resources.

      Phase 2

      Plant the Seeds for Change During Project Planning and Initiation

      Phase 2 outline

      Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

      Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 2: Plant the seeds for change during project planning and initiation

      Proposed Time to Completion (in weeks): 1 week

      Step 2.1: Foster OCM considerations during the ideation phase

      Discuss these issues with an analyst:

      • Disengaged or absent sponsors on change initiatives.
      • Lack of organizational desire for change.
      • How to customize an OCM strategy to suit the personality of the organization.

      Then complete these activities…

      • Develop a sponsorship action plan to help facilitate more engaged change sponsorship.
      • Build a process for making the case for change throughout the organization.

      With these tools & templates:

      • Activity 2.1.3: “Refine your change story”
      • Activity 2.1.4: “Develop a sponsorship action plan”
      • Transition Team Communications Template
      Step 2.2: Perform an organizational change impact analysis

      Work with an analyst to:

      • Perform an impact analysis to make your change planning more complete.
      • Assess the depth of change impacts across various stakeholder groups.

      Then complete these activities…

      • Assign accountability for managing change impacts.
      • Update the business case with risks and opportunities identified during the impact analysis.

      With these tools & templates:

      • Organizational Change Management Impact Analysis Tool

      Step 2.1: Foster OCM considerations during the ideation phase

      Phase 2 - 2.1

      This step will walk you through the following activities:
      • Assess leadership support for change.
      • Highlight the goals and benefits of the change.
      • Refine your change story.
      • Define success criteria.
      • Develop a sponsorship action plan.
      This step involves the following participants:
      • PMO Director
      • Project sponsor for the pilot OCM project
      • Additional project staff: project managers, business analysts, etc.
      Outcomes of this step
      • Strategy to shore up executive alignment around the need for change.
      • Increased definition around the need for change.
      • Increased engagement from project sponsors around change management and project outcomes.

      Accountability for change management begins in advance of the project itself

      As early as the request phase, project sponsors and requestors have a responsibility to communicate the need for the changes that they are proposing.

      Org Change Step #1: Make the case for change during the request phase

      Initiation→Planning→Execution→Monitoring & Controlling→Closing

      Even before project planning and initiation begin, sponsors and requestors have org change responsibilities around communicating the need for a change and demonstrating their commitment to that change.

      In this step, we will look at the OCM considerations that need to be factored in during project ideation.

      The slides ahead will cover what the PMO can do to help foster these considerations among project sponsors and requestors.

      While this project may already be in the planning phase, the activities in the slides ahead will help lay a solid OCM foundation as you move ahead into the impact assessment and stakeholder engagement steps in this phase.

      Strongly recommended: include the sponsor for your pilot OCM project in many of the following activities (see individual activity slides for direction).

      Info-Tech Insight

      Make active sponsorship a criteria when scoring new requests.

      Projects with active sponsors are far more likely to succeed than those where the sponsor cannot be identified or where she/he is unable or unwilling to champion the initiative throughout the organization.

      Consider the engagement level of sponsors when prioritizing new requests. Without this support, the likelihood of a change initiative succeeding is far diminished.

      What does effective sponsorship look like?

      Somewhere along the way a stereotype arose of the project sponsor as a disengaged executive who dreams up a project idea and – regardless of that idea’s feasibility or merit – secures funding, pats themselves on the back, and does not materialize again until the project is over to pat themselves on the back again.

      Indeed, it’s exaggerated, based partly on the fact that sponsors are almost always extremely busy individuals, with very demanding day jobs on top of their responsibilities as sponsors. The stereotype doesn’t capture the very real day-to-day project-level responsibilities of project sponsors.

      Leading change management institute, Prosci, has developed a checklist of 10 identifiable traits and responsibilities that PMO leaders and project managers should help to foster among project sponsors. As Prosci states, the checklist “can be used as an audit tool to see if you are utilizing best practices in how you engage senior leaders on your change initiatives.”

      Prosci’s Change Management Sponsor Checklist:

      Are your sponsors:

      • Aware of the importance they play in making changes successful?
      • Aware of their roles in supporting org change?
      • Active and visible throughout the project?
      • Building necessary coalitions for change success?
      • Communicating directly and effectively with employees?
      • Aware that the biggest mistake is failing to personally engage as the sponsor?
      • Prepared to help manage resistance?
      • Prepared to celebrate successes?
      • Setting clear priorities to help employees manage project and day-to-day work?
      • Avoiding trends and backing change that will be meaningful for the long term?

      (Source: Prosci’s Change Management Sponsor Checklist)

      Assess leadership support for change

      2.1.1 30 minutes

      Participants
      • PMO leader
      • Other PMO/PM staff
      Output
      • Leadership support strategy

      Many change initiatives require significant investments of political capital to garner approval, funding, and involvement from key executives. This process can take months or even years before the project is staffed and implementation begins.

      • In cases where leadership opposition or ambivalence to change is a critical success inhibitor, project sponsors or change leaders need a deliberate strategy for engaging and converting potential supporters.
      • You might need to recruit someone with more influence or authority to become sponsor or co-sponsor to convert supporters you otherwise could not.
      • Use the table below as an example to begin developing your executive engagement strategy (but keep it private).
      Executive/Stakeholder Degree of Support Ability to Influence Potential Contribution/Engagement Strategy
      Board of Directors Med High
      CEO
      CFO
      CIO
      CxO

      “The stakes of having poorly engaged executive sponsors are high, as are the consequences and costs. PMI research into executive sponsorship shows that one in three unsuccessful projects fail to meet goals due to poorly engaged executive sponsors.”

      PMI, 2014

      Highlight the goals and benefits of the change

      2.1.2 30-60 minutes

      Participants
      • PMO leader
      • PMO staff
      • Project sponsor

      Build desire for change.

      The project sponsor is accountable for defining the high-level scope and benefits of the project. The PMO needs to work with the sponsor during the ideation phase to help establish the need for the proposed change.

      Use the table below to begin developing a compelling vision and story of change. If you have not already defined high-level goals and deliverables for your project, download Info-Tech’s Light Project Request Form (a Detailed Project Request Form is also available).

      Why is there a need to change?
      How will change benefit the organization?
      How did we determine this is the right change?
      What would happen if we didn’t change?
      How will we measure success?

      See Info-Tech’s Optimize Project Intake, Approval, and Prioritization blueprint for more detailed advice on working with requestors to define requirements and business value of new requests.

      Stories are more compelling than logic and facts alone

      Crucial facts, data, and figures are made more digestible, memorable, and actionable when they are conveyed through a compelling storyline.

      While you certainly need high-level scope elements and a rigorous cost-benefit analysis in your business case, projects that require organizational change also need a compelling story or vision to influence groups of stakeholders.

      As the PMO works with sponsors to identify and document the goals and benefits of change, begin to sketch a narrative that will be compelling to the organization’s varied audiences.

      Structuring an effective project narrative:

      Research shows (Research and impacts cited in Torben Rick’s “Change Management Require[s] a Compelling Story,” 2014) that when managers and employees are asked about what most inspires them in their work, their responses are evenly split across five forms of impact:

      1. Impact on society – e.g. the organization’s role in the community.
      2. Impact on the customer – e.g. providing effective service.
      3. Impact on the company – e.g. contributing positively to the growth of the organization.
      4. Impact on the working team – e.g. creating an inclusive work environment.
      5. Impact on the individual – e.g. personal development and compensation.

      "Storytelling enables the individuals in an organization to see themselves and the organization in a different light, and accordingly take decisions and change their behavior in accordance with these new perceptions, insights, and identities." – Steve Denning

      Info-Tech Insight

      A micro-to-macro change narrative. A compelling org change story needs to address all five of these impacts in order to optimally engage employees in change. In crafting a narrative that covers both the micro and macro levels, you will be laying a solid foundation for adoption throughout the organization.

      Refine your change story

      2.1.3 45 to 60 minutes

      Participants
      • PMO leader
      • PMO staff
      • Project sponsor
      Input
      • 5 levels of change impact
      • Stakeholder groups
      Output
      • Improved change justification to help inform the request phase and the development of the business case.
      Materials
      • Whiteboard and markers

      Using a whiteboard to capture the discussion, address the 5 levels of change impact covered on the previous slide.

      1. Develop a list of the stakeholder groups impacted by this project.
        • The impacts will be felt differently by different groups, so develop a high-level list of those stakeholder groups that will be directly affected by the change.
        • Keep in mind, this activity is not an impact assessment. This activity is meant to elicit how the change will be perceived by the different stakeholder groups, not how it will actually impact them – i.e. this activity is about making the case for change, not actually managing the change.
      2. Brainstorm how the five impact levels will be perceived from the point of view of each stakeholder group.
        • Spend about 5 to 10 minutes per impact per stakeholder group.
        • The goal here isn’t to create a detailed plotline; your change story may evolve as the project evolves. A point or two per impact per group will suffice.
      3. As a group, prioritize the most prescient points and capture the results of your whiteboarding to help inform future artifacts.
        • The points developed during this activity should inform both the ad hoc conversations that PMO staff and the sponsor have with stakeholders, as well as formal project artifacts, such as the request, business case, charter, etc.

      When it comes to communicating the narrative, project sponsors make the most compelling storytellers

      Whatever story you develop to communicate the goals and the benefits of the change, ultimately it should be the sponsor who communicates this message to the organization at large.

      Given the competing demands that senior leaders face, the PMO still has a pivotal role to play in helping to plan and facilitate these communications.

      The PMO should help sponsors by providing insights to shape change messaging (refer to the characteristics outlined in the table below for assistance) and by developing a sponsorship action plan (Activity 2.1.4).

      Tips for communicating a change story effectively:
      Identify and appeal to the audience’s unique frames of reference. e.g. “Most of you remember when we…”
      Include concrete, vivid details to help visualize change. e.g. “In the future, when a sales rep visits a customer in Wisconsin, they’ll be able to process a $100,000 order in seconds instead of hours.”
      Connect the past, present, and future with at least one continuous theme. e.g. “These new capabilities reaffirm our long-standing commitment to customers, as well as our philosophy of continuously finding ways to be more responsive to their needs.”

      “[T]he sponsor is the preferred sender of messages related to the business reasons and organizational implications for a particular initiative; therefore, effective sponsorship is crucial in building an awareness of the need for change.

      Sponsorship is also critical in building the desire to participate and support the change with each employee and in reinforcing the change.”

      Prosci

      Base the style of your communications on the organization’s receptiveness to change

      Not all organizations embrace or resist change in the same ways. Base your change communications on your organization’s cultural appetite for change in general.

      Use the below dimensions to gauge your organization’s appetite for change. Analyzing this will help determine the form and force of communications.

      In the next slide, we will base aspects of your sponsorship action plan on whether an organization’s indicator is “high” or “low” across these three dimensions.

      • Organizations with low appetite for change will require more direct, assertive communications.
      • Organizations with a high appetite for change are more suited to more open, participatory approaches.

      Three key dimensions determine the appetite for cultural change (Dimensions taken from Joanna Malgorzata Michalak’s “Cultural Catalysts and Barriers of Organizational Change Management: a Preliminary Overview,” 2010):

      Power Distance Refers to the acceptance that power is distributed unequally throughout the organization. Organizations with a high power distance indicator show that the unequal power distribution is accepted by the less powerful employees.
      Individualism Organizations that score high in individualism have employees who are more independent; those who score low in individualism fall into the collectivism side where employees are strongly tied to one another or their groups.
      Uncertainty Avoidance Describes the level of acceptance that an organization has towards uncertainty. Those who score high in this area find that their employees do not favor “uncertain” situations, while those that score low in this area find that their employees are comfortable with change and uncertainty.

      "Societies with a high indicator of power distance, individualism, and uncertainty avoidance create vital inertial forces against transformation." – Michalak

      Develop a sponsorship action plan

      2.1.4 45 to 60 minutes

      Participants
      • PMO leader
      • PMO staff
      • Project sponsor
      Use the table below to define key tasks and responsibilities for the project sponsor.
      1. Populate the first column with the stakeholder groups from Activity 2.1.3.
      2. With reference to the Sponsor Checklist, brainstorm key sponsorship responsibilities for this project across each of the groups.
      3. When gauging the frequency of each activity and the “Estimated Weekly Effort” required by the sponsor to complete them, consider the organization’s appetite for change.
        • Where indicators across the three dimensions are low, the sponsor’s involvement can be less hands-on and more collaborative in nature.
        • Where indicators across the three dimensions are high, the sponsor’s involvement should be hands-on and direct in her/his communications.
      Group Activity Est. Weekly Effort Comments/Frequency
      Project Team Ad hoc check-in on progress 30 mins Try to be visible at least once a week
      Attend status meetings 30 mins Every second Tuesday, 9 am
      Senior Managers Touch base informally 45 mins Aim for bi-weekly, one-on-one touchpoints
      Lead steering committee meetings 60 mins First Thursday of the month, 3 pm
      End Users Organization-wide emails Ad hoc, 20 mins As required, with PMO assistance

      "To manage change is to tell people what to do... but to lead change is to show people how to be." – Weick & Quinn

      Update the Transition Team Communications Template

      2.1.5 10 minutes

      Participants
      • PMO leader
      • PMO staff
      Input
      • The outcomes of various activities in this step
      Output
      • Key sections of the Transition Team Communications Template completed

      Use Info-Tech’s Transition Team Communications Template to help communicate the outcomes of this step.

      The following activities should be recorded in the template:

      Activity 2.1.2

      In addition, the outcome of Activity 2.1.4, the “Sponsorship Action Plan,” should be converted to a format such as Word and provided to the project sponsor.

      Download Info-Tech’s Transition Team Communications Template.

      "In most work situations, the meaning of a change is likely to be as important, if not more so, than the change itself."

      – Roethlisberger (cited in Burke)

      Step 2.2: Perform an organizational change impact assessment

      Phase 2 - 2.2

      This step will walk you through the following activities:
      • Perform change impact survey.
      • Assess the depth of impacts for different stakeholders and stakeholder groups.
      • Determine overall adoptability of the OCM effort.
      • Establish a game plan for managing individual impacts.
      • Review risks and opportunities.
      • Determine how the value of the change will be measured.
      This step involves the following participants:
      • PMO Director
      • Project sponsor for the pilot OCM project
      • Additional project staff: project managers, business analysts, members of the transition team, etc.
      Outcomes of this step:
      • A change impact analysis.
      • An adoptability rating for the change initiative to help the PMO plan its OCM efforts.
      • A better understanding of the risks and opportunities associated with the change to inform the business case.

      Analyze change impacts across multiple dimensions to ensure that nothing is overlooked

      Ensure that no stone is left unturned as you prepare for a comprehensive transition plan.

      In the previous step, we established a process and some accountabilities to help the PMO and project sponsors make the case for change during the ideation and initiation phase of a project.

      In this step, we will help with the project planning phase by establishing a process for analyzing how the change will impact various dimensions of the business and how to manage these impacts to best ensure stakeholder adoption.

      Brace for Impact…

      A thorough analysis of change impacts will help the PMO:

      • Bypass avoidable problems.
      • Remove non-fixed barriers to success.
      • Acknowledge and minimize the impact of unavoidable barriers.
      • Identify and leverage potential benefits.
      • Measure the success of the change.

      Assign the appropriate accountabilities for impact analysis

      In the absence of an assigned change manager, organizational change impact assessments are typically performed by a business analyst or the project manager assigned to the change initiative.

      • Indeed, as with all change management activities, making an individual accountable for performing this activity and communicating its outcomes is key to the success of your org change initiative.
      • At this stage, the PMO needs to assign or facilitate accountability for the impact analysis on the pilot OCM initiative or it needs to take this accountability on itself.

      Sample RACI for this activity. Define these accountabilities for your organization before proceeding with this step.

      Project Sponsor PMO PM or BA
      Survey impact dimensions I A R
      Analyze impacts across multiple stakeholder groups I A R
      Assess required OCM rigor I A/R C
      Manage individual impacts I A R

      Info-Tech Insight

      Bring perspective to an imperfect view.

      No individual has a comprehensive view of the potential impact of change.

      Impact assessment and analysis is most effective when multiple viewpoints are coordinated using a well-defined list of considerations that cover a wide breadth of dimensions.

      Revisit and refine the impact analysis throughout planning and execution, as challenges to adoption become more clear.

      Perform a change impact analysis to make your planning more complete

      Use Info-Tech’s Organizational Change Management Impact Analysis Tool to weigh all of the factors involved in a change and to formalize discipline around impact analysis.

      Info-Tech’s Organizational Change Management Impact Analysis Tool helps to document the change impact across multiple dimensions, enabling the PMO to review the analysis with others to ensure that the most important impacts are captured. The tool also helps to effectively monitor each impact throughout project execution.

      • Change impact considerations can include: products, services, states, provinces, cultures, time zones, legal jurisdictions, languages, colors, brands, subsidiaries, competitors, departments, jobs, stores, locations, etc.
      • Each of these dimensions is an MECE (Mutually Exclusive, Collectively Exhaustive) list of considerations that could be impacted by the change. For example, a North American retail chain might consider “Time Zones” as a key dimension, which could break down as Newfoundland, Atlantic, Eastern, Central, Mountain, and Pacific.

      Download Info-Tech’s Organizational Change Impact Analysis Tool.

      • Required Participants for this Step: PMO Leader; project manager or business analyst
      • Recommended Participants for this Step: Project Sponsor; IT/PMO staff

      Info-Tech Insight

      Anticipate the unexpected. Impact analysis is the cornerstone of any OCM strategy. By shining a light on considerations that might have otherwise escaped project planners and decision makers, an impact analysis is an essential component to change management and project success.

      Enter high-level project information on the “Set Up” tab

      2.2.1 15 minutes

      The “2. Set Up” tab of the Impact Tool is where you enter project-specific data pertaining to the change initiative.

      The inputs on this tab are used to auto-populate fields and drop-downs on subsequent tabs of the analysis.

      Document the stakeholders (by individual or group) associated with the project who will be subject to the impacts.

      You are allowed up to 15 entries. Try to make this list comprehensive. Missing any key stakeholders will threaten the value of this activity as a whole.

      If you find that you have more than 15 individual stakeholders, you can group individuals into stakeholder groups.

      Keep in mind...

      An impact analysis is not a stakeholder management exercise.

      Impact assessments cover:

      • How the change will affect the organization.
      • How individual impacts might influence the likelihood of adoption.

      Stakeholder management covers:

      • Resistance/objections handling.
      • Engagement strategies to promote adoption.

      We will cover the latter in the next step.

      “As a general principle, project teams should always treat every stakeholder initially as a recipient of change. Every stakeholder management plan should have, as an end goal, to change recipients’ habits or behaviors.”

      PMI, 2015

      Determine the relevant considerations for analyzing the change impacts of a project

      2.2.2 15 to 30 minutes

      Use the survey on tab 3 of the Impact Analysis Tool to determine the dimensions of change that are relevant.

      The impact analysis is fueled by the thirteen-question survey on tab 3 of the tool.

      This survey addresses a comprehensive assortment of change dimensions, ranging from customer-facing considerations, to employee concerns, to resourcing, logistical, and technological questions.

      Once you have determined the dimensions that are impacted by the change, you can go on to assess how individual stakeholders and stakeholder groups are affected by the change.

      This image is a screenshot of tab 3, Impact Survey, of the Impact Analysis Tool.

      Screenshot of tab “3. Impact Survey,” showing the 13-question survey that drives the impact analysis.

      Ideally, the survey should be performed by a group of project stakeholders together. Use the drop-downs in column K to record your responses.

      "A new system will impact roles, responsibilities, and how business is conducted within an organization. A clear understanding of the impact of change allows the business to design a plan and address the different levels of changes accordingly. This approach creates user acceptance and buy-in."

      – January Paulk, Panorama Consulting

      Impacts will be felt differently by different stakeholders and stakeholder groups

      As you assess change impacts, keep in mind that no impact will be felt the same across the organization. Depth of impact can vary depending on the frequency (will the impact be felt daily, weekly, monthly?), the actions necessitated by it (e.g. will it change the way the job is done or is it simply a minor process tweak?), and the anticipated response of the stakeholder (support, resistance, indifference?).

      Use the Organizational Change Depth Scale below to help visualize various depths of impact. The deeper the impact, the tougher the job of managing change will be.

      Procedural Behavioral Interpersonal Vocational Cultural
      Procedural change involves changes to explicit procedures, rules, policies, processes, etc. Behavioral change is similar to procedural change, but goes deeper to involve the changing tacit or unconscious habits. Interpersonal change goes beyond behavioral change to involve changing relationships, teams, locations, reporting structures, and other social interactions. Vocational change requires acquiring new knowledge and skills, and accepting the loss or decline in the value or relevance of previously acquired knowledge and skills. Cultural change goes beyond interpersonal and vocational change to involve changing personal values, social norms, and assumptions about the meaning of good vs. bad or right vs. wrong.
      Example: providing sales reps with mobile access to the CRM application to let them update records from the field. Example: requiring sales reps to use tablets equipped with a custom mobile application for placing orders from the field. Example: migrating sales reps to work 100% remotely. Example: migrating technical support staff to field service and sales support roles. Example: changing the operating model to a more service-based value proposition or focus.

      Determine the depth of each impact for each stakeholder group

      2.2.3 1 to 3 hours

      Tab “4. Impact Analysis” of the Analysis Tool contains the meat of the impact analysis activity.
      1. The “Impact Analysis” tab is made up of thirteen change impact tables (see next slide for a screenshot of one of these tables).
      • You may not need to use all thirteen tables. The number of tables you use coincides with the number of “yes” responses you gave in the previous tab.
      • If you no not need all thirteen impact tables (i.e. if you do not answer “yes” to all thirteen questions in tab 2, the unused/unnecessary tables will not auto-populate.)
    • Use one table per change impact. Each of your “yes” responses from tab 3 will auto-populate at the top of each change impact table. You should go through each of your “yes” responses in turn.
    • Analyze how each impact will affect each stakeholder or stakeholder group touched by the project.
      • Column B in each table will auto-populate with the stakeholder groups from the Set Up tab.
    • Use the drop-downs in columns C, D, and E to rate the frequency of each impact, the actions necessitated by each impact, and the anticipated response of each stakeholder group.
      • Each of the options in these drop-downs is tied to a ranking table that informs the ratings on the two subsequent tabs.
    • If warranted, you can use the “Comments” cells in column F to note the specifics of each impact for each stakeholder/group.
    • See the next slide for an accompanying screenshot of a change impact table from tab 4 of the Analysis Tool.

      Screenshot of “Impact Analysis” tab

      The image is a screenshot of the Impact Analysis tab.

      The stakeholder groups entered on the Set Up will auto-populate in column B of each table.

      Your “yes” responses from the survey tab will auto-populate in the cells to the right of the “Change Impact” cells.

      Use the drop-downs in this column to select how often the impact will be felt for each group (e.g. daily, weekly, periodically, one time, or never).

      “Actions” include “change to core job duties,” “change to how time is spent,” “confirm awareness of change,” etc.

      Use the drop-downs to hypothesize what the stakeholder response might be. For now, for the purpose of the impact analysis, a guess is fine. We will come back to build a communications plan based on actual responses in Phase 3 of this blueprint.

      Review your overall impact rating to help assess the likelihood of change adoption

      Use the “Overall Impact Rating” on tab 5 to help right-size your OCM efforts.

      Based upon your assessment of each individual impact, the Analysis Tool will provide you with an “Overall Impact Rating” in tab 5.

      • This rating is an aggregate of each of the individual change impact tables used during the analysis, and the rankings assigned to each stakeholder group across the frequency, required actions, and anticipated response columns.

      The image is a screenshot of tab 5, the Overall Process Adoption Rating. The image shows a semi-circle, where the left-most section is red, the centre yellow, and the right-most section green, with a dial positioned at the right edge of the yellow section.

      Projects in the red should have maximum change governance, applying a full suite of OCM tools and templates, as well as revisiting the impact analysis exercise regularly to help monitor progress.

      Increased communication and training efforts, as well as cross-functional partnerships, will also be key for success.

      Projects in the yellow also require a high level of change governance. Follow the steps and activities in this blueprint closely, paying close attention to the stakeholder engagement activities in the next step to help sway resistors and leverage change champions.

      In order to free up resources for those OCM initiatives that require more discipline, projects in green can ease up in their OCM efforts somewhat. With a high likelihood of adoption as is, stakeholder engagement and communication efforts can be minimized somewhat for these projects, so long as the PMO is in regular contact with key stakeholders.

      "All change is personal. Each person typically asks: 'What’s in it for me?'" – William T. Craddock

      Use the other outputs on tab 5 to help structure your OCM efforts

      In addition to the overall impact rating, tab 5 has other outputs that will help you assess specific impacts and how the overall change will be received by stakeholders.

      The image is a screenshot of tab 5.

      Top-Five Highest Risk Impacts table: This table displays the highest risk impacts based on frequency and action inputs on Tab 4.

      Top-Five Most Impacted Stakeholders table: Here you’ll find the stakeholders, ranked again based on frequency and action, who will be most impacted by the proposed changes.

      Top Five Supporters table: These are the 5 stakeholders most likely to support changes, based on the Anticipated Response column on Tab 4.

      The stakeholder groups entered on the Set Up Tab will auto-populate in column B of each table.

      In addition to these outputs, this tab also lists top five change resistors, and has an impact register and list of potential impacts to watch out for (i.e. your “maybe” responses from tab 3).

      Establish a game plan to manage individual change impacts

      2.2.4 60 to 90 minutes

      The final tab of the Analysis Tool can be used to help track and monitor individual change impacts.
      • Use the “Communications Plan” on tab 7 to come up with a high-level game plan for tracking communications about each change with the corresponding stakeholders.
      • Update and manage this tab as the communication events occur to help keep your implementation on track.

      The image is a screenshot of the Communications Plan, located on tab 7 of the Analysis Tool. There are notes emerging from each of the table headings, as follows: Communication Topic - Select from a list of topics identified on Tab 6 that are central to successful change, then answer the following; Audience/Format/Delivery - Which stakeholders need to be involved in this change? How are we going to meet with them?; Creator - Who is responsible for creating the change?; Communicator - Who is responsible for communicating the change to the stakeholder?; Intended Outcome - Why do you need to communicate with this stakeholder?; Level of Risk - What is the likelihood that you can achieve your attended outcome? And what happens if you don’t?

      Document the risk assumptions stemming from your impact analysis

      2.2.5 30 to 60 minutes

      Use the Analysis Tool to produce a set of key risks that need to be identified, communicated, mitigated, and tracked.

      A proper risk analysis often reveals risks and mitigations that are more important to other people in the organization than those managing the change. Failure to do a risk analysis on other people’s behalf can be viewed as negligence.

      In the table below, document the risks related to the assumptions being made about the upcoming change. What are the risks that your assumptions are wrong? Can steps be taken to avoid these risks?

      Risk Assumption Magnitude if Assumption Wrong Likelihood That Assumption Is Wrong Mitigation Strategy Assessment
      e.g. Customers will accept shipping fees for overweight items > 10 pounds Low High It's a percentage of our business, and usually accompanies a sharply discounted product. We need to extend discretionary discounting on shipping to supervisory staff to mitigate the risk of lost business. Re-assess after each quarter.

      "One strategy to minimize the impact is to determine the right implementation pace, which will vary depending on the size of the company and the complexity of the project" – Chirantan Basu

      Record any opportunities pertaining to the upcoming change

      2.2.6 30 to 60 minutes

      Use the change impacts to identify opportunities to improve the outcome of the change.

      Use the table below to brainstorm the business opportunities arising from your change initiative. Consider if the PMO can take steps to help improve the outcomes either through supporting the project execution or through providing support to the business.

      Opportunity Assumption Potential Value Likelihood That Assumption Is Wrong Leverage Strategy Assessment
      e.g. Customer satisfaction can increase as delivery time frames for the remaining custom products radically shrink and services extend greatly. High Medium Reset the expectations of this market segment so that they go from being surprised by good service to expecting it. Our competitors will not be able to react to this.

      Info-Tech Insight

      The bigger the change, the bigger the opportunity. Project and change management has traditionally focused on a defensive posture because organizations so often fail to mitigate risk. Good change managers also watch for opportunities to improve and exploit the outcomes of the change.

      Determine how to measure the value of the change

      2.2.7 15 to 30 minutes

      Describe the metrics that will be used to assess the management of this change.

      Now that you’ve assessed the impacts of the change, and the accompanying risks and opportunities, use the table below to document metrics that can be used to help assess the management of the change.

      • Don’t rely on the underlying project to determine the value of the change itself: It’s important to recognize the difference between change management and project management, and the establishment of value metrics is an obvious source of this differentiation.
      • For example, consider a project that is introducing a new method of remitting travel expenses for reimbursement.
        • The project itself would be justified on the efficiency of the new process.
        • The value of the change itself could be measured by the number of help desk calls looking for the new form, documentation, etc.
      Metric Calculation How to Collect Who to Report to Frequency
      Price overrides for new shipping costs It is entered as a line item on invoices, so it can be calculated as % of shipping fees discounted. Custom report from CRM (already developed). Project Steering Committee Project Steering Committee

      Document risks and other impact analysis considerations in the business case

      2.2.8 10 minutes

      Participants
      • PMO leader
      • Project Manager
      Input
      • The risks and issues identified through the impact analysis.
      Output
      • Comprehensive list of risks documented in the business case.
      Use the outcomes of the activities in this step to help inform your business case as well as any other risk management artifacts that your project managers may use.
      • Because long-term project success depends upon stakeholder adoption, high-risk impacts should be documented as considerations in the risk section of your business case.
      • In addition, the “Overall Impact Rating” graph and the “Impact Management Worksheet” could be used to help improve business cases as well as charters on some projects.

      If your organization doesn’t have a standard business case document, use one of Info-Tech’s templates. We have two templates to choose from, depending on the size of the project and the amount of rigor required:

      Download Info-Tech’s Comprehensive Business Case Template for large, complex projects or our Fast Track Business Case Template for smaller ones.

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      2.1.3 Create a convincing sponsor-driven story to help build the case for change

      Work with an analyst to exercise your storytelling muscles, building out a process to help make the case for change throughout the organization.

      2.1.4 Develop a sponsorship action plan

      Utilize analyst experience to help develop a sponsorship action plan to help facilitate more engaged change project sponsors.

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      2.2.3 Assess different change impacts across various stakeholder groups

      Get an analyst perspective on how each impact may affect different stakeholders in order to assist with the project and OCM planning process.

      2.2.4 Develop a proactive change impact management plan

      Rightsize your response to change impacts by developing a game plan to mitigate each one according to adoption likelihood.

      2.2.5 Use the results of the impact analysis to inform and improve the business case for the project

      Work with the analyst to translate the risks and opportunities identified during the impact analysis into points of consideration to help inform and improve the business case for the project.

      Phase 3

      Facilitate Change Adoption Throughout the Organization

      Phase 3 outline

      Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

      Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 3: Facilitate Change Adoption Throughout the Organization

      Proposed Time to Completion (in weeks): 4 to 6 weeks

      Step 3.1: Ensure stakeholders are engaged and ready for change

      Discuss these issues with analyst:

      • Lack of alignment between IT and the business.
      • Organizational resistance to a command-and-control approach to change.

      Then complete these activities…

      • Develop a stakeholder engagement plan.

      With these tools & templates:

      • Stakeholder Engagement Workbook
      Step 3.2: Develop and execute the transition plan

      Discuss these issues with analyst:

      • Org change initiatives often fail due to the influence of resistors.
      • Failure to elicit feedback contributes to the feeling of a change being imposed.

      Then complete these activities…

      • Develop a communications strategy to address a variety of stakeholder reactions to change.

      With these tools & templates:

      • Transition Plan Template
      • Activity 3.2.7: “Objections Handling Template”
      Step 3.3: Establish HR and training plans

      Discuss these issues with analyst:

      • Training is often viewed as ineffective, contributing to change resistance rather than fostering adoption.

      Then complete these activities…

      • Rightsize training content based on project requirements and stakeholder sentiment.

      With these tools & templates:

      • “Training Requirements” tab in the Stakeholder Engagement Workbook
      • “Training Plan” section of the Transition Plan Template

      Step 3.1: Ensure stakeholders are engaged and ready for change

      Phase 3 - 3.1

      This step will walk you through the following activities:
      • Involve the right stakeholders in the change.
      • Define project roles and responsibilities.
      • Define elicitation methods for obtaining stakeholder input.
      • Perform a stakeholder analysis to assess influence, interest, and potential contribution.
      • Assess communications plan requirements.
      This step involves the following participants:
      • Required: PMO Director; project manager or business analyst
      • Recommended: Project Sponsor; the Transition Team; other IT/PMO staff
      Outcomes of this step
      • A stakeholder analysis.
      • Requirements for the communications plan.

      The nature of change is changing

      The challenge of managing change is complicated by forces that are changing change.

      Empowerment: Increased worker mobility, effect of millennials in the workforce, and lower average tenure means that people are less tolerant of a hierarchical, command-and-control approach to change.

      • Additionally, lower average tenure means you can’t assume everyone has the same context or background for change (e.g. they might not have been with the organization for earlier phases when project justification/rationale was established).

      Noise: Inundation with communications and diversity of channels means the traditional “broadcast” approach to communicating change doesn’t work (i.e. you can’t expect every email to get everyone’s attention).

      As a result, disciplines around organizational change tend to be less linear and deliberate than they were in the past.

      "People don’t resist change. They resist being changed."

      Peter Senge

      How to manage change in organizations of today and the future:

      • New realities require a more collaborative, engaging, open, and agile approach to change.
      • Communication is increasingly more of a two-way, ongoing, iterative engagement process.
      • Project leaders on change initiatives need to engage diverse audiences early and often.
      • Information about change needs to reach people and be easily findable where and when stakeholders need it.
      Info-Tech Insight

      Accountabilities for change management are still required. While change management needs to adopt more collaborative and organic approaches, org change success still depends on assigning appropriate accountabilities. What’s changed in the move to matrix structure is that accountabilities need to be facilitated more collaboratively.

      Leading change requires collaboration to ensure people, process, and technology factors are aligned

      In the absence of otherwise defined change leadership, the PMO needs to help navigate every technology-enabled change, even if it isn’t in the “driver’s seat.”

      PMO leaders and IT experts often find themselves asked to help implement or troubleshoot technology-related business projects that are already in flight.

      The PMO will end up with perceived or de facto responsibility for inadequate planning, communications, and training around technology-enabled change.

      IT-Led Projects

      Projects led by the IT PMO tend to be more vulnerable to underestimating the impact on people and processes on the business side.

      Make sure you engage stakeholders and representatives (e.g. “power users”) from user populations early enough to refine and validate your impact assessments.

      Business-Led Projects

      Projects led by people on the business side tend to be more vulnerable to underestimating the implications of technology changes.

      Make sure IT is involved early enough to identify and prepare for challenges and opportunities involving integration, user training, etc.

      "A major impediment to more successful software development projects is a corporate culture that results in a lack of collaboration because business executives view the IT departments as "order takers," a view disputed by IT leaders."

      – David Ramel (cited by Ben Linders)

      Foster change collaboration by initiating a stakeholder engagement plan through the PMO

      If project stakeholders aren’t on board, the organization’s change initiatives will be in serious trouble.

      Stakeholders will not only be highly involved in the process improvement initiative, but they also may be participants, so it’s essential that you get their buy-in for the initiative upfront.

      Use Info-Tech’s Stakeholder Engagement Workbook to help plan how stakeholders rate in terms of engagement with the project.

      Once you have identified where different stakeholders fall in terms of interests, influence, and support for/engagement with the change initiative, you can structure your communication plan (to be developed in step 3.2) based on where individuals and stakeholder groups fall.

      • Required participants for the activities in this step: PMO Leader; project manager or business analyst
      • Recommended participants for the activities in this step: Project Sponsor; IT/PMO staff

      Download Info-Tech’s Stakeholder Engagement Workbook.

      The engagement plan is a structured and documented approach for:

      • Gathering requirements by eliciting input and validating plans for change.
      • Cultivating sponsorship and support from key stakeholders early in the project lifecycle.

      Download Info-Tech’s Stakeholder Engagement Workbook.

      Involve the right people to drive and facilitate change

      Refer to your project level assessment from 1.2.2:

      • Level 1 projects tend to only require involvement from the project team, sponsors, and people affected.
      • Level 2 projects often benefit from broad support and capabilities in order to take advantage of opportunities.
      • Level 3 projects require broad support and capabilities in order to deal with risks and barriers.

      Info-Tech Insight

      The more transformational the change, the more it will affect the org chart – not just after the implementation, but also through the transition.

      Take time early in the project to define the reporting structure for the project/transition team, as well as any teams and roles supporting the transition.

      • Project manager: Has primary accountability for project success.
      • Senior executive project sponsor: Needed to “open doors” and signal organization’s commitment to the change.
      • Technology SMEs and architects: Responsible for determining and communicating requirements and risks of the technology being implemented or changed.
      • Business unit leads: Responsible for identifying and communicating impact on business functions, approving changes, and helping champion change.
      • Product/process owners: Responsible for identifying and communicating impact on business functions, approving changes, and helping champion change.
      • HR specialists: Most valuable when roles and organizational design are affected, i.e. change requires staff redeployment, substantial training (not just using a new system or tool but acquiring new skills and responsibilities), or termination.
      • Training specialists: If you have full-time training staff in the organization, you will eventually need them to develop training courses and material. Consulting them early will help with scoping, scheduling, and identifying the best resources and channels to deliver the training.
      • Communications specialists (internal): Valuable in crafting communications plan; required if communications function owns internal communications.

      Use the RACI table on the next slide to clarify who will be accountable, responsible, consulted, and informed for key tasks and activities around this change initiative.

      Define roles and responsibilities for facilitating change on your pilot OCM initiative

      3.1.1 60 minutes

      Perform a RACI exercise pertaining to your pilot change initiative to clarify who to include in the stakeholder engagement activity.

      Don’t reinvent the wheel: revisit the list of stakeholders and stakeholder groups from your impact assessment. The purpose of the RACI is to bring some clarity to project-specific responsibilities.

      Tasks PMO Project Manager Sr. Executives Technology SME Business Lead Process Owner HR Trainers Communications
      Meeting project objectives A R A R R
      Identifying risks and opportunities A R A C C C C I I
      Building the action plan A R C R R R R R R
      Planning and delivering communications A R C C C C C R A
      Planning and delivering training A R C C C C R A C
      Gathering and analyzing feedback and KPIs A R C C C C C R R

      Copy the results of this RACI exercise into tab 1 of the Stakeholder Engagement Workbook. In addition, it can be used to inform the designated RACI section in the Transition Plan Template. Revise the RACI Table there as needed.

      Formalize the stakeholder analysis to identify change champions and blockers

      Define key stakeholders (or stakeholder groups) who are affected by the project or are in positions to enable or block change.

      • Remember to consider customers, partners, and other external stakeholders.
      • People best positioned to provide insight and influence change positively are also best positioned to create resistance.
      • These people should be engaged early and often in the transition process – not just to make them feel included or part of the change, but because their insight could very likely identify risks, barriers, and opportunities that need to be addressed.

      The image is a screenshot of tab 3 of the Stakeholder Engagement Workbook.

      In tab three of the Stakeholder Engagement Workbook, compile the list of stakeholders who are touched by the change and whose adoption of the change will be key to project success.

      To save time, you can copy and paste your stakeholder list from the Set Up tab of the Organizational Change Management Impact Analysis Tool into the table below and edit the list as needed.

      Formal stakeholder analysis should be:

      • Required for Level 3 projects
      • Recommended for Level 2 projects
      • Optional for Level 1 projects

      Info-Tech Insight

      Resistance is, in many cases, avoidable. Resistance is commonly provided by people who are upset about not being involved in the communication. Missed opportunities are the same: they usually could have been avoided easily had somebody known in time. Use the steps ahead as an opportunity to ensure no one has been missed.

      Perform a stakeholder analysis to begin cultivating support while eliciting requirements

      3.1.2 60 minutes

      Use tab 4 of the Stakeholder Engagement Workbook to systematically assess each stakeholder's influence, interest, and potential contribution to the project as well as to develop plans for engaging each stakeholder or stakeholder group.

      The image is a screencapture of tab 4 of the Stakeholder Engagement Workbook.

      Use the drop-downs to select stakeholders and stakeholder groups. These will automatically populate based on your inputs in tab 3.

      Rate each stakeholder on a scale of 1 to 10 in terms of her/his influence in the organization. Not only do these rankings feed the stakeholder map that gets generated on the next slide, but they will help you identify change champions and resistors with influence.

      Similar to the ranking under “Influence,” rate the “Interest” and “Potential Contribution” to help identify stakeholder engagement.

      Document how you will engage each stakeholder and stakeholder group and document how soon you should communicate with them concerning the change. See the following slides for advice on eliciting change input.

      Use the elicitation methods on the following slides to engage stakeholders and gather change requirements.

      Elicitation methods – Observation

      Method Description Assessment and Best Practices Stakeholder Effort BA/PMO Effort
      Casual Observation The process of observing stakeholders performing tasks where the stakeholders are unaware they are being observed. Capture true behavior through observation of stakeholders performing tasks without informing them that they are being observed. This information can be valuable for mapping business process; however, it is difficult to isolate the core business activities from unnecessary actions. Low Medium
      Formal Observation The process of observing stakeholders performing tasks where the stakeholders are aware they are being observed. Formal observation allows business analysts to isolate and study the core activities in a business process because the stakeholder is aware they are being observed. Stakeholders may become distrusting of the business analyst and modify their behavior if they feel their job responsibilities or job security are at risk. Low Medium

      Info-Tech Insight

      Observing stakeholders does not uncover any information about the target state. Be sure to use contextual observation in conjunction with other techniques to discover the target state.

      Elicitation methods – Surveys

      Method Description Assessment and Best Practices Stakeholder Effort BA/PMO Effort
      Closed-Response Survey A survey that has fixed responses for each answer. A Likert-scale (or similar measures) can be used to have respondents evaluate and prioritize possible requirements. Closed-response surveys can be sent to large groups and used to quickly gauge user interest in different functional areas. They are easy for users to fill out and don’t require a high investment of time. However, their main deficit is that they are likely to miss novel requirements that are not listed. As such, closed-response surveys are best used after initial elicitation or brainstorming to validate feature groups. Low Medium
      Open-Response Survey A survey that has open-ended response fields. Questions are fixed, but respondents are free to populate the field in their own words. Open-response surveys take longer to fill out than closed, but can garner deeper insights. Open-response surveys are a useful supplement (and occasionally a replacement) for group elicitation techniques, like focus groups, when you need to receive an initial list of requirements from a broad cross-section of stakeholders. Their primary shortcoming is the analyst can’t immediately follow up on interesting points. However, they are particularly useful for reaching stakeholders who are unavailable for individual one-on-ones or group meetings. Medium Medium

      Info-Tech Insight

      Surveys can be useful mechanisms for initial drafting of raw requirements (open response) and gauging user interest in proposed requirements or feature sets (closed response). However, they should not be the sole focus of your elicitation program due to lack of interactivity and two-way dialogue with the business analyst.

      Elicitation methods – Interviews

      Method Description Assessment and Best Practices Stakeholder Effort BA/PMO Effort

      Structured One-on-One Interview

      In a structured one-on-one interview, the business analyst has a fixed list of questions to ask the stakeholder and follows up where necessary. Structured interviews provide the opportunity to quickly hone in on areas of concern that were identified during process mapping or group elicitation techniques. They should be employed with purpose – to receive specific stakeholder feedback on proposed requirements or help identify systemic constraints. Generally speaking, they should take 30 minutes or less to complete. Low Medium

      Unstructured One-on-One Interview

      In an unstructured one-on-one interview, the business analyst allows the conversation to flow freely. The BA may have broad themes to touch on, but does not run down a specific question list. Unstructured interviews are most useful for initial elicitation when brainstorming a draft list of potential requirements is paramount. Unstructured interviews work best with senior stakeholders (sponsors or power users), since they can be time consuming if they’re applied to a large sample size. It’s important for BAs not to stifle open dialogue and allow the participants to speak openly. They should take 60 minutes or less to complete. Medium Low

      Info-Tech Insight

      Interviews should be used with “high-value targets.” Those who receive one-on-one face time can help generate good requirements, as well as allow effective communication around requirements at a later point (i.e. during the analysis and validation phases).

      Elicitation methods – Focus Groups

      Method Description Assessment and Best Practices Stakeholder Effort BA/PMO Effort
      Focus Group Focus groups are sessions held between a small group (typically ten individuals or less) and an experienced facilitator who leads the conversation in a productive direction. Focus groups are highly effective for initial requirements brainstorming. The best practice is to structure them in a cross-functional manner to ensure multiple viewpoints are represented and the conversation doesn’t become dominated by one particular individual. Facilitators must be wary of “groupthink” in these meetings (the tendency to converge on a single POV). Medium Medium

      Info-Tech Insight

      Group elicitation techniques are most useful for gathering a wide spectrum of requirements from a broad group of stakeholders. Individual or observational techniques are typically needed for further follow-up and in-depth analysis with critical power users or sponsors.

      "Each person has a learning curve. Take the time to assess staff individually as some don’t adjust to change as well as others. Some never will." – CEO, Manufacturing Firm

      Refine your stakeholder analysis through the input elicitation process

      3.1.3 30 minutes

      Review all of these elicitation methods as you go through the workbook as a group. Be sure to document and discuss any other elicitation methods that might be specific to your organization.

      1. Schedule dates and a specific agenda for performing stakeholder elicitation activities.
      • If scheduling more formal methods such as a structured interview or survey, take the time to develop some talking points and questions (see the questionnaire and survey templates in the next step for examples).
    • Assign accountabilities for performing the elicitation exercises and set dates for updating the PMO on the results of these stakeholder elicitations.
    • As curator of the workbook, the PMO will need to refine the stakeholder data in tab 4 of the tool to get a more accurate stakeholder map on the next tab of the workbook.
    • Elicitation method Target stakeholder group(s) PMO staff responsible for eliciting input Next update to PMO
      One-on-one structured interview HR and Sales Karla Molina August 1

      Info-Tech Insight

      Engagement paves the way for smoother communications. The “engagement” approach (rather than simply “communication”) turns stakeholders and users into advocates who help boost your message, sustain change, and realize benefits without constant, direct intervention.

      Develop a stakeholder engagement strategy based on the output of your analysis

      Use the stakeholder map on tab 5 of the Workbook to inform your communications strategy and transition plan.

      Tab 5 of the Workbook provides an output – a stakeholder map – based on your inputs in the previous tab. Use the stakeholder map to inform your communications requirements considerations in the next tab of the workbook as well as your transition plan in the next step.

      The image is a screencapture of tab 5 of the Stakeholder Engagement Workbook.

      This is a screenshot of the “Stakeholder Analysis” from tab 5 of the Workbook. The four quadrants of the map are:

      • Engage (High Interest/High Influence)
      • Communicate – High Level (High Interest/Low Influence)
      • Passive (Low Interest/Low Influence)
      • Communicate – Low Level (Low Interest/High Influence)
      How to interpret each quadrant on the map:

      Top Quadrants: Supporters

      1. Engage: Capitalize on champions to drive the project/change.
      2. Communicate (high level): Leverage this group where possible to help socialize the program and to help encourage dissenters to support.

      Bottom Quadrant: Blockers

      1. Passive: Focus on increasing these stakeholders’ level of support.
      2. Communicate (low level): Pick your battles – focus on your noise makers first and then move on to your blockers.

      Document communications plan requirements based on results of engagement and elicitation

      3.1.4 60 minutes

      The image is a screencapture of the Communications Requirements tab in the Stakeholder Engagement Workbook

      Use the Communications Requirements tab in the Stakeholder Engagement Workbook.

      Do this as a 1–2 hour project team planning session.

      The table will automatically generate a list of stakeholders based on your stakeholder analysis.

      Update the assumptions that you made about the impact of the change in the Impact Analysis with results of stakeholder engagement and elicitation activities.

      Use the table on this tab to refine these assumptions as needed before solidifying your communications plan.

      Define the action required from each stakeholder or stakeholder group (if any) for change to be successful.

      Continually refine messages and methods for communicating with each stakeholder and stakeholder group.

      Note words that work well and words that don’t. For example, some buzzwords might have negative connotations from previous failed initiatives.

      Designate who is responsible for developing and honing the communications plan (see details in the following section on developing the transition plan).

      Step 3.2: Develop and execute the transition plan

      Phase 3 - 3.2

      This step will walk you through the following activities:
      • Create a communications timeline.
      • Establish communications strategy for stakeholder groups.
      • Determine communication delivery methods.
      • Define the feedback and evaluation process.
      • Assess the full range of support and resistance to change.
      • Prepare objections handling process.
      This step involves the following participants:
      • PMO Director
      • Transition Team
      • Project managers
      • Business analyst
      • Project Sponsor
      • Additional IT/PMO staff
      Outcomes of this step
      • A communications strategy
      • A stakeholder feedback process
      • An objections handling strategy
      • A transition plan

      Effective change requires strategic communications and rightsized training plans

      Develop and execute a transition plan through the PMO to ensure long-term adoption.

      In this step we will develop and introduce a plan to manage change around your project.

      After completing this section you will have a realistic, effective, and adaptable transition plan that includes:

      • Clarity around leadership and vision.
      • Well-defined plans for targeting unique groups with specific messages.
      • Resistance and contingency plans.
      • Templates for gathering feedback and evaluating success.

      These activities will enable you to:

      • Execute the transition in coordination with the timeline and structure of the core project.
      • Communicate the action plan and vision for change.
      • Target specific stakeholder and user groups with unique messages.
      • Deal with risks, resistance, and contingencies.
      • Evaluate success through feedback and metrics.

      "Everyone loves change: take what you know and replace it with a promise. Then overlay that promise with the memory of accumulated missed efforts, half-baked attempts, and roads of abandoned promises."

      Toby Elwin

      Assemble the core transition team to help execute this step

      Once the stakeholder engagement step has been completed, the PMO needs to facilitate the involvement of the transition team to help carry out transition planning and communications strategies.

      You should have already sketched out a core transition team in step 1.2.6 of this blueprint. As with all org change activities, ensuring that individuals are made accountable for the execution of the following activities will be key for the long-term success of your change initiative.

      • At this stage, the PMO needs to ensure the involvement of the transition team to participate in the following activities – or the PMO will need to take on the transition planning and communication responsibilities itself.

      Refer to the team structure examples from Activity 1.2.6 of this blueprint if you are still finalizing your transition team.

      Download Info-Tech’s Transition Plan Template to help capture and record the outcomes of the activities in this step.

      Create a high-level communications timeline

      3.2.1 30 minutes

      By now the project sponsor, project manager, and business analysts (or equivalent) should have defined project timelines, requirements, and other key details. Use these to start your communications planning process.

      If your members of the transition team are also part of the core project team, meet with them to elicit the project timeline and requirements.

      Project Milestone Milestone Time Frame Communications Activities Activity Timing Notes
      Business Case Approval
      • Key stakeholder communications
      Pilot Go-Live
      • Pilot launch activity communications
      • Org-wide status communications
      Full Rollout Approval
      • Key stakeholder communications
      Full Rollout
      • Full rollout activity communications
      • Org-wide status communications
      Benefits Assessment
      • Key stakeholder communications
      • Org-wide status communications

      Info-Tech Insight

      Communicate, communicate, communicate.

      Staff are 34% more likely to adapt to change quickly during the implementation and adoption phases when they are provided with a timeline of impending changes specific to their department. (Source: McLean & Company)

      Schedule time to climb out of the “Valley of Despair”

      Many change initiatives fail when leaders give up at the first sign of resistance.

      OCM experts use terms like “Valley of Despair” to describe temporary drops in support and morale that inevitably occur with any significant change. Don’t let these temporary drops derail your change efforts.

      Anticipate setbacks and make sure the project plan accommodates the time and energy required to sustain and reinforce the initiative as people move through stages of resistance.

      The image is a line graph. Segments of the line are labelled with numbers. The beginning of the line is labelled with 1; the descending segment of the line labelled 2; the lowest point is labelled 3; the ascending section is labelled 4; and the end of the graph is labelled 5.

      Based on Don Kelley and Daryl Conner’s Emotional Cycle of Change.

      Identify critical points in the change curve:

      1. Honeymoon of “Uninformed Optimism”: There is usually tentative support and even enthusiasm for change before people have really felt or understood what it involves.
      2. Backlash of “Informed Pessimism” (leading to “Valley of Despair”): As change approaches or begins, people realize they’ve overestimated the benefits (or the speed at which benefits will be achieved) and underestimated the difficulty of change.
      3. Valley of Despair and beginning of “Hopeful Realism”: Eventually, sentiment bottoms out and people begin to accept the difficulty (or inevitability) of change.
      4. Bounce of “Informed Optimism”: People become more optimistic and supportive when they begin to see bright spots and early successes.
      5. Contentment of “Completion”: Change has been successfully adopted and benefits are being realized.

      Tailor a communications strategy for each stakeholder group

      Leveraging the stakeholder analyses you’ve already performed in steps 2.2 and 3.1, customize your communications strategy for the individual stakeholder groups.

      Think about where each of the groups falls within the Organizational Change Depth Scale (below) to determine the type of communications approach required. Don’t forget: the deeper the change, the tougher the job of managing change will be.

      Procedural Behavioral Interpersonal Vocational Cultural

      Position

      • Changing procedures requires clear explanation of what has changed and what people must do differently.
      • Avoid making people think wherever possible. Provide procedural instructions when and where people need them to ensure they remember.

      Incentivize

      • Changing behaviors requires breaking old habits and establishing new ones by adjusting the contexts in which people work.
      • Consider a range of both formal and informal incentives and disincentives, including objective rewards, contextual nudges, cues, and informal recognition

      Empathize

      • Changing people’s relationships (without damaging morale) requires showing empathy for disrupting what is often a significant source of their well-being.
      • Show that efforts have been made to mitigate disruption, and sacrifice is shared by leadership.

      Educate

      • Changing people’s roles requires providing ways to acquire knowledge and skills they need to learn and succeed.
      • Consider a range of learning options that includes both formal training (external or internal) and ongoing self-directed learning.

      Inspire

      • Changing values and norms in the organization (i.e. what type of things are seen as “good” or “normal”) requires deep disruption and persistence.
      • Think beyond incentives; change the vocabularies in which incentives are presented.

      Base your communications approaches on our Organizational Change Depth Scale

      Use the below “change chakras” as a quick guide for structuring your change messages.

      The image is a human, with specific areas of the body highlighted, with notes emerging from them. Above the head is a cloud, labelled Cultural Change/Inspire-Shape ideas and aspirations. The head is the next highlighted element, with notes reading Vocational Change/Educate-Develop their knowledge and skills. The heart is the next area, labelled with Interpersonal Change/Empathize-Appeal to their hearts. The stomach is pictured, with the notes Behavioral Change/Incentivize-Appeal to their appetites and instincts. The final section are the legs, with notes reading Procedural Change/Position-Provide clear direction and let people know where and when they’re needed.

      Categorize stakeholder groups in terms of communications requirements

      3.2.2 30 minutes

      Use the table below to document where your various stakeholder groups fall within the depth scale.
      Depth Levels Stakeholder Groups Tactics
      Procedural Position: Provide explanation of what exactly has changed and specific procedural instructions of what exactly people must do differently to ensure they remember to make adjustments as effortlessly as possible.
      Behavioral Incentivize: Break old habits and establish new ones by adjusting the context of formal and informal incentives (including objective rewards, contextual nudges, cues, and informal recognition).
      Interpersonal Empathize: Offer genuine recognition and support for disruptions of personal networks (a significant source of personal well-being) that may result from changing work relationships. Show how leadership shares the burden of such sacrifices.
      Vocational Educate: Provide a range of learning options (formal and self-directed) to provide the knowledge and skills people need to learn and succeed in changed roles.
      Cultural Inspire: Frame incentives in a vocabulary that reflects any shift in what types of things are seen as “good” or “normal” in the organization.

      The deeper the impact, the more complex the communication strategy

      Interposal, vocational, and cultural changes each require more nuanced approaches when communicating with stakeholders.

      Straightforward → Complex

      When managing interpersonal, vocational, or cultural changes, you will be required to incorporate more inspirational messaging and gestures of empathy than you typically might in a business communication.

      Communications that require an appeal to people’s emotions can be, of course, very powerful, but they are difficult to craft. As a result, oftentimes messages that are meant to inspire do the exact opposite, coming across as farfetched or meaningless platitudes, rather than evocative and actionable calls to change.

      Refer to the tactics below for assistance when crafting more complex change communications that require an appeal to people’s emotions and imaginations.

      • Tell a story. Describe a journey with a beginning (who we are and how we got here) and a destination (our goals and expected success in the future).
      • Convey an intuitive sense of direction. This helps people act appropriately without being explicitly told what to do.
      • Appeal to both emotion and reason. Make people want to be part of the change.
      • Balance abstract ideas with concrete facts. Writers call this “moving up and down the ladder of abstraction.” Without concrete images and facts, the vision will be meaninglessly vague. Without abstract ideas and principles, the vision will lack power to unite people and inspire broad support.
      • Be concise. Make your messages easy to communicate and remember in any situation.

      "Instead of resisting any emotion, the best way to dispel it is to enter it fully, embrace it and see through your resistance."

      Deepak Chopra

      Fine-tune change communications for each stakeholder or audience

      3.2.3 60 to 90 minutes

      Use Info-Tech’s “Message Canvas” (see next slide) to help rationalize and elaborate the change vision for each group.

      Build upon the more high-level change story that you developed in step 1.1 by giving more specificity to the change for specific stakeholder groups.

      Questions to address in your communication strategy include: How will the change benefit the organization and its people? How have we confirmed there is a need for change? What would happen if we didn’t change? How will the change leverage existing strengths – what will stay the same? How will we know when we get to the desired state?

      Remember these guidelines to help your messages resonate:

      • People are busy and easily distracted. Tell people what they really need to know first, before you lose their attention.
      • Repetition is good. Remember the Aristotelian triptych: “Tell them what you’re going to tell them, then tell them, then tell them what you told them.”
      • Don’t use technical terms, jargon, or acronyms. Different groups in organizations tend to develop specialized vocabularies. Everybody grows so accustomed to using acronyms and jargon every day that it becomes difficult to notice how strange it sounds to outsiders. This is especially important when IT communicates with non-technical audiences. Don’t alienate your audience by talking at them in a strange language.
      • Test your message. Run focus groups or deliver communications to a test audience (which could be as simple as asking 2–3 people to read a draft) before delivering messages more broadly.

      Info-Tech Insight

      Change thy language, change thyself.

      Jargon, acronyms, and technical terms represent deeply entrenched cultural habits and assumptions.

      Continuing to use jargon or acronyms after a transition tends to drag people back to old ways of thinking and working.

      You don’t need to invent a new batch of buzzwords for every change (nor should you), but every change is an opportunity to listen for words and phrases that have lost their meaning through overuse and abuse.

      3.2.3 continued - Example “Message Canvas”

      The image is a screencapture of tab 6 of the Organizational Change Impact Analysis Tool, which is a message canvas

      If there are multiple messages or impacts that need to be communicated to a single group or audience, you may need to do multiple Message Canvases per group. Refer back to your Stakeholder Engagement Workbook to help inform the stakeholder groups and messages that this activity should address.

      Go to tab 6 of the Organizational Change Impact Analysis Toolfor multiple message canvas template boxes that you can use. These messages can then help inform your communication plan on tab 7 of that tool.

      Determine methods for communications delivery

      Review your options for communicating your change. This slide covers traditional methods of communication, while the following slides cover some options for multimedia mass-communications.

      Method Best Practices
      Email Email announcements are necessary for every organizational change initiative but are never sufficient. Treat email as a formalizing medium, not a medium of effective communication when organizational change is concerned. Use email to invite people to in-person meetings, make announcements across teams and geographical areas at the same time, and share formal details.
      Team Meeting Team meetings help sell change. Body language and other in-person cues are invaluable when trying to influence people. Team meetings also provide an opportunity to gauge a group’s response to an announcement and gives the audience an opportunity to ask questions and get clarification.
      One-on-One One-on-ones are more effective than team meetings in their power to influence and gauge individual responses, but aren’t feasible for large numbers of stakeholders. Use one-on-ones selectively: identify key stakeholders and influencers who are most able to either advocate change on your behalf or provide feedback (or both).
      Internal Site / Repository Internal sites and repositories help sustain change by making knowledge available after the implementation. People don’t retain information very well when it isn’t relevant to them. Much of their training will be forgotten if they don’t apply that knowledge for several weeks or months. Use internal sites and repositories for how-to guides and standard operating procedures.

      Review multimedia communication methods for reaching wider audiences in the organization

      Method Best Practices
      User Interfaces User interface (UI) design is overlooked as a communication method. Often a simple UI refinement with the clearer prompts or warnings is more effective and efficient than additional training and repeated email reminders.
      Social Media Social media is widely and deeply embraced by people publicly, and is increasingly useful within organizations. Look for ways to leverage existing internal social tools. Avoid trying to introduce new social channels to communicate change unless social transformation is within the scope of the core project’s goals; the social tool itself might become as much of an organizational change management challenge as the original project.
      Posters & Marketing Collateral Posters and other marketing collateral are common communication tools in retail and hospitality industries that change managers in other industries often don’t think of. Making key messages a vivid, visual part of people’s everyday environment is a very effective way to communicate. On the down side, marketing collateral requires professional design skills and can be costly to create. Professional copywriting is also advisable to ensure your message resonates.
      Video Videos are well worth the cost to produce when the change is transformational in nature, as in cultural changes. Videos are useful for both communicating the vision and as part of the training plan.

      Document communication methods and build the Communications Delivery Plan

      3.2.4 30 minutes

      1. Determine when communications need to be delivered for each stakeholder group.
      2. Select the most appropriate delivery methods for each group and for each message.
      • Meetings and presentations
      • Email/broadcast
      • Intranet and other internal channels (e.g. internal social network)
      • Open houses and workshops
    • Designate who will deliver the messages.
    • Develop plans to follow up for feedback and evaluation (Step 3.2.5).
    • The image is a screenshot of the Stakeholder/Audience section of the Transition Plan Template.

      This is a screenshot from the “Stakeholder/Audience” section of Info-Tech’s Transition Plan Template. Use the template to document your communication strategy for each audience and your delivery plan.

      "The role of project communication is to inspire, instigate, inform or educate and ultimately lead to a desired action. Project communication is not a well presented collection of words; rather it is something that propels a series of actions."

      Sidharth Thakur

      Info-Tech Insight

      Repetition is crucial. People need to be exposed to a message 7 times before it sticks. Using a variety of delivery formats helps ensure people will notice and remember key messages. Mix things up to keep employees engaged and looking forward to the next update.

      Define the feedback and evaluation process to ensure an agile response to resistance

      3.2.5 46 to 60 minutes

      1. Designate where/when on the roadmap the project team will proactively evaluate progress/success and elicit feedback in order to identify emerging challenges and opportunities.
      2. Create checklists to review at key milestones to ensure plans are being executed. Review…
      • Key project implementation milestones (i.e. confirm successful deployment/installation).
      • Quick wins identified in the impact analysis and determined in the transition plan (see the following slides for advice in leveraging quick wins).
    • Ensure there is immediate follow-up on communications and training:
      • Confirm understanding and acceptance of vision and action plan – utilize surveys and questionnaires to elicit feedback.
      • Validate people’s acquisition of required knowledge and skills.
      • Identify emerging/unforeseen challenges and opportunities.
    • "While creating and administering a survey represent(s) additional time and cost to the project, there are a number of benefits to be considered: 1) Collecting this information forces regular and systematic review of the project as it is perceived by the impacted organizations, 2) As the survey is used from project to project it can be improved and reused, 3) The survey can quickly collect feedback from a large part of the organization, increasing the visibility of the project and reducing unanticipated or unwelcome reactions."

      – Claire Schwartz

      Use the survey and questionnaire templates on the following two slides for assistance in eliciting feedback. Record the evaluation and feedback gathering process in the Transition Plan Template.

      Sample stakeholder questionnaire

      Use email to distribute a questionnaire (such as the example below) to project stakeholders to elicit feedback.

      In addition to receiving invaluable opinions from key stakeholders and the frontline workers, utilizing questionnaires will also help involve employees in the change, making them feel more engaged and part of the change process.

      Interviewee Date
      Stakeholder Group Interviewer
      Question Response Notes
      How do you think this change will affect you?
      How do you think this change will affect the organization?
      How long do you expect the change to take?
      What do you think might cause the project/change to fail?
      What do you think are the most critical success factors?

      Sample survey template

      Similar to a questionnaire, a survey is a great way to assess the lay of the land in terms of your org change efforts and the likelihood of adoption.

      Using a free online survey tool like Survey Monkey, Typeform, or Google Forms, surveys are quick and easy to generate and deploy. Use the below example as a template to build from.

      Use survey and questionnaire feedback as an occasion to revisit the Impact Analysis Tool and reassess the impacts and roadblocks based on hard feedback.

      To what degree do you agree or disagree with each of the following statements?

      1=Strongly Disagree, 2=Disagree, 3=Somewhat Disagree, 4=Somewhat Agree, 5=Agree, 6=Strongly Agree

      1. I understand why [this change] is happening.
      2. I agree with the decision to [implement this change].
      3. I have the knowledge and tools needed to successfully go through [this change].
      4. Leadership/management is fully committed to the change.
      5. [This change] will be a success.

      Rate the impact of this change.

      1=Very Negative, 2=Negative, 3=Somewhat Negative, 4=Somewhat Positive, 5=Positive, 6=Very Positive

      1. On you personally.
      2. On your team/department/unit.
      3. On the organization as a whole.
      4. On people leading the change.

      Develop plans to leverage support and deal with resistance, objections, and fatigue

      Assess the “Faces of Change” to review the emotions provoked by the change in order to proactively manage resistors and engage supporters.

      The slides that follow walk you through activities to assess the different “faces of change” around your OCM initiative and to perform an objections handling exercise.

      Assessing people’s emotional responses to the change will enable the PMO and transition team to:

      • Brainstorm possible questions, objections, suggestions, and concerns from each audience.
      • Develop responses to questions, objections, and concerns.
      • Revise the communications messaging and plan to include proactive objections handling.
      • Re-position objections and suggestions as questions to plan for proactively communicating responses and objections to show people that you understand their point of view.
      • Develop a plan with clearly defined responsibility for regularly updating and communicating the objections handling document. Active Subversion Quiet Resistance Vocal Skepticism Neutrality / Uncertainty Vocal Approval Quiet Support Active Leadership
      Hard Work Vs. Tough Work

      Carol Beatty’s distinction between “easy work,” “hard work,” and “tough work” can be revealing in terms of the high failure rate on many change initiatives. (“The Tough Work of Managing Change.” Queen’s University IRC. 2015.)

      • Easy work includes administrative tasks like scheduling meetings and training sessions or delivering progress reports.
      • Hard work includes more abstract efforts like estimating costs/benefit or defining requirements.
      • Tough work involves managing people and emotions, i.e. providing leadership through setbacks, and managing resistance and conflict.

      That is what makes organizational change “tough,” as opposed to merely hard. Managing change requires mental and emotional toughness to deal with uncertainty, ambiguity, and conflict.

      Assess the full range of support and resistance to change

      3.2.6 20 minutes

      Categorize the feedback received from stakeholder groups or individual stakeholders across the “faces of change” spectrum.

      Use the table below to document where different stakeholders and stakeholder groups fall within the spectrum.

      Response Symptoms Examples
      Active Subversion Publicly or privately disparaging the transition (in some cases privately disparaging while pretending to support); encouraging people to continue doing things the old way or to leave the organization altogether. Group/Name
      Quiet Resistance Refusing to adopt change, continuing to do things the old way (including seemingly trivial or symbolic things). Non-participative. Group/Name
      Vocal Skepticism Asking questions; questioning the why, what, and how of change, but continuing to show willingness to participate and try new things. Group/Name
      Neutrality / Uncertainty Non-vocal participation, perhaps with some negative body language, but continuing to show tacit willingness to try new things. Group/Name
      Vocal Approval Publicly and privately signaling buy-in for the change. Group/Name
      Quiet Support Actively helping to enable change to succeed without necessarily being a cheerleader or trying to rally others around the transition. Group/Name
      Active Leadership Visibly championing the change and helping to rally others around the transition. Group/Name

      Review strategies and tactics for engaging different responses

      Use the below tactics across the “faces of change” spectrum to help inform the PMO’s responses to sources of objection and resistance and its tactics for leveraging support.

      Response Engagement Strategies and Tactics
      Active Subversion Firmly communicate the boundaries of acceptable response to change: resistance is a natural response to change, but actively encouraging other people to resist change should not be tolerated. Active subversion often indicates the need to find a new role or depart the organization.
      Quiet Resistance Resistance is a natural response to change. Use the Change Curve to accommodate a moderate degree and period of resistance. Use the OCM Depth Scale to ensure communications strategies address the irrational sources of resistance.
      Vocal Skepticism Skepticism can be a healthy sign. Skeptics tend to be invested in the organization’s success and can be turned into vocal and active supporters if they feel their questions and concerns have been heard and addressed.
      Neutrality / Uncertainty Most fence-sitters will approve and support change when they start to see concrete benefits and successes, but are equally likely to become skeptics and resisters when they see signs of failure or a critical mass of skepticism, resistance, or simply ambivalence.
      Vocal Approval Make sure that espoused approval for change isn’t masking resistance or subversion. Engage vocal supporters to convert them into active enablers or champions of change.
      Quiet Support Engage quiet supporters to participate where their skills or social and political capital might help enable change across the organization. This could either be formal or informal, as too much formal engagement can invite minor disagreements and slow down change.
      Active Leadership Engage some of the active cheerleaders and champions of change to help deliver communications (and in some cases training) to their respective groups or teams.

      Don’t let speed bumps become roadblocks

      What If... Do This: To avoid:
      You aren’t on board with the change? Fake it to your staff, then communicate with your superiors to gather the information you need to buy in to the change. Starting the change process off on the wrong foot. If your staff believe that you don’t buy in to the change, but you are asking them to do so, they are not going to commit to it.
      When you introduce the change, a saboteur throws a tantrum? If the employee storms out, let them. If they raise uninformed objections in the meeting that are interrupting your introduction, ask them to leave and meet with them privately later on. Schedule an ad hoc one-on-one meeting. A debate at the announcement. It’s an introduction to the change and questions are good, but it’s not the time for debate. Leave this for the team meetings, focus groups, and one-on-ones when all staff have digested the information.
      Your staff don’t trust you? Don’t make the announcement. Find an Enthusiast or another manager that you trust to make the announcement. Your staff blocking any information you give them or immediately rejecting anything you ask of them. Even if you are telling the absolute truth, if your staff don’t trust you, they won’t believe anything you say.
      An experienced skeptic has seen this tried before and states it won’t work? Leverage their experience after highlighting how the situation and current environment is different. Ask the employee what went wrong before. Reinventing a process that didn’t work in the past and frustrating a very valuable segment of your staff. Don’t miss out on the wealth of information this Skeptic has to offer.

      Use the Objections Handling Template on the next slide to brainstorm specific objections and forms of resistance and to strategize about the more effective responses and mitigation strategies.

      Copy these objections and responses into the designated section of the Transition Plan Template. Continue to revise objections and responses there if needed.

      Objections Handling Template

      3.2.7 45 to 60 minutes

      Objection Source of Objection PMO Response
      We tried this two years ago. Vocal skepticism Enabling processes and technologies needed time to mature. We now have the right process discipline, technologies, and skills in place to support the system. In addition, a dedicated role has been created to oversee all aspects of the system during and after implementation.
      Why aren’t we using [another solution]? Uncertainty We spent 12 months evaluating, testing, and piloting solutions before selecting [this solution]. A comprehensive report on the selection process is available on the project’s internal site [here].

      Info-Tech Insight

      There is insight in resistance. The individuals best positioned to provide insight and influence change positively are also best positioned to create resistance. These people should be engaged throughout the implementation process. Their insights will very likely identify risks, barriers, and opportunities that need to be addressed.

      Make sure the action plan includes opportunities to highlight successes, quick wins, and bright spots

      Highlighting quick wins or “bright spots” helps you go from communicating change to more persuasively demonstrating change.

      Specifically, quick wins help:

      • Demonstrate that change is possible.
      • Prove that change produces positive results.
      • Recognize and reward people’s efforts.

      Take the time to assess and plan quick wins as early as possible in the planning process. You can revisit the impact assessment for assistance in identifying potential quick wins; more so, work with the project team and other stakeholders to help identify quick wins as they emerge throughout the planning and execution phases.

      Make sure you highlight bright spots as part of the larger story and vision around change. The purpose is to continue to build or sustain momentum and morale through the transition.

      "The quick win does not have to be profound or have a long-term impact on your organization, but needs to be something that many stakeholders agree is a good thing… You can often identify quick wins by simply asking stakeholders if they have any quick-win recommendations that could result in immediate benefits to the organization."

      John Parker

      Tips for identifying quick wins (Source: John Parker, “How Business Analysts can Identify Quick Wins,” 2013):
      • Brainstorm with your core team.
      • Ask technical and business stakeholders for ideas.
      • Observe daily work of users and listen to users for problems and opportunities; quick wins often come from the rank and file, not from the top.
      • Review and analyze user support trouble tickets; this can be a wealth of information.
      • Be open to all suggestions.

      Info-Tech Insight

      Stay positive. Our natural tendency is to look for what’s not working and try to fix it. While it’s important to address negatives, it’s equally important to highlight positives to keep people committed and motivated around change.

      Document the outcomes of this step in the Transition Plan Template

      3.2.8 45 minutes

      Consolidate and refine communication plan requirements for each stakeholder and group affected by change.

      Upon completion of the activities in this step, the PMO Director is responsible for ensuring that outcomes have been documented and recorded in the Transition Plan Template. Activities to be recorded include:

      • Stakeholder Overview
      • Communications Schedule Activity
      • Communications Delivery
      • Objections Handling
      • The Feedback and Evaluation Process

      Going forward, successful change will require that many responsibilities be delegated beyond the PMO and core transition team.

      • Delegate responsibilities to HR, managers, and team members for:
        • Advocating the importance of change.
        • Communicating progress toward project milestones and goals.
        • Developing HR and training plan.
      • Ensure sponsorship stays committed and active during and after the transition.
        • Leadership visibility throughout the execution and follow-up of the project is needed to remind people of the importance of change and the organization’s commitment to project success.

      Download Info-Tech’s Transition Plan Template.

      "Whenever you let up before the job is done, critical momentum can be lost and regression may follow." – John Kotter, Leading Change

      Step 3.3: Establish HR and Training Plans

      Phase 3 - 3.3

      This step will walk you through the following activities:
      • Analyze HR requirements for involvement in training.
      • Outline appropriate HR and training timelines.
      • Develop training plan requirements across different stakeholder groups.
      • Define training content.
      • Assess skills required to support the change and review options for filling HR gaps.
      This step involves the following participants:
      • PMO Director
      • Transition Team
      • HR Personnel
      • Project Sponsor
      Outcomes of this step
      • A training plan
      • Assessment of skill required to support the change

      Make sure skills, roles, and teams are ready for change

      Ensure that the organization has the infrastructure in place and the right skills availability to support long-term adoption of the change.

      The PMO’s OCM approach should leverage organizational design and development capabilities already in place.

      Recommendations in this section are meant to help the PMO and transition team understand HR and training plan activities in the context of the overall transition process.

      Where organizational design and development capabilities are low, the following steps will help you do just enough planning around HR, and training and development to enable the specific change.

      In some cases the need for improved OCM will reveal the need for improved organizational design and development capabilities.

      • Required Participants for this Step: PMO Leader; PMO staff; Project manager.
      • Recommended Participants for this Step: Project Sponsor; HR personnel.

      This section will walk you through the basic steps of developing HR, training, and development plans to support and enable the change.

      For comprehensive guidance and tools on role, job, and team design, see Info-Tech’s Transform IT Through Strategic Organizational Design blueprint.

      Info-Tech Insight

      Don’t make training a hurdle to adoption. Training and other disruptions take time and energy away from work. Ineffective training takes credibility away from change leaders and seems to validate the efforts of saboteurs and skeptics. The PMO needs to ensure that training sessions are as focused and useful as possible.

      Analyze HR requirements to ensure efficient use of HR and project stakeholder time

      3.3.1 30-60 minutes

      Refer back to Activity 3.2.4. Use the placement of each stakeholder group on the Organizational Change Depth Scale (below) to determine the type of HR and training approach required. Don’t impose training rigor where it isn’t required.

      Procedural Behavioral Interpersonal Vocational Cultural
      Simply changing procedures doesn’t generally require HR involvement (unless HR procedures are affected). Changing behaviors requires breaking old habits and establishing new ones, often using incentives and disincentives. Changing teams, roles, and locations means changing people’s relationships, which adds disruption to people’s lives and challenges for any change initiative. Changing people’s roles and responsibilities requires providing ways to acquire knowledge and skills they need to learn and succeed. Changing values and norms in the organization (i.e. what type of things are seen as “good” or “normal”) requires deep disruption and persistence.
      Typically no HR involvement. HR consultation recommended to help change incentives, compensation, and training strategies. HR consultation strongly recommended to help define roles, jobs, and teams. HR responsibility recommended to develop training and development programs. HR involvement recommended.

      22%

      In a recent survey of 276 large and midsize organizations, eighty-seven percent of survey respondents trained their managers to “manage change,” but only 22% felt the training was truly effective. (Towers Watson)

      Outline appropriate HR and training timelines

      3.3.2 15 minutes

      Revisit the high-level project schedule from steps 1.2.4 and 3.4.1 to create a tentative timeline for HR and training activities.

      Revise this timeline throughout the implementation process, and refine the timing and specifics of these activities as you move from the development to the deployment phase.

      Project Milestone Milestone Time Frame HR/Training Activities Activity Timing Notes
      Business Case Approval
      • Consulted to estimate timeline and cost
      Pilot Go-Live
      • Train groups affected by pilot
      Full Rollout Approval
      • Consulted to estimate timeline and cost
      Full Rollout
      • Train the trainers for full-scale rollout
      Benefits Assessment
      • Consulted to provide actual time and costs

      "The reason it’s going to hurt is you’re going from a state where you knew everything to one where you’re starting over again."

      – BA, Natural Resources Company

      Develop the training plan to ensure that the right goals are set, and that training is properly timed and communicated

      3.3.3 60 minutes

      Use the final tab in the Stakeholder Engagement Workbook, “7. Training Requirements,” to begin fleshing out a training plan for project stakeholders.

      The image is a screencapture of the final tab in the Stakeholder Engagement Workbook, titled Training Requirements.

      The table will automatically generate a list of stakeholders based on your stakeholder analysis.

      If your stakeholder list has grown or changed since the stakeholder engagement exercise in step 3.1, update the “Stakeholder List” tab in the tool.

      Estimate when training can begin, when training needs to be completed, and the total hours required.

      Training too early and too late are both common mistakes. Training too late hurts morale and creates risks. Training too early is often wasted and creates the need for retraining as knowledge and skills are lost without immediate relevance to their work.

      Brainstorm or identify potential opportunities to leverage for training (such as using existing resources and combining multiple training programs).

      Review the Change Management Impact Analysis to assess skills and knowledge required for each group in order for the change to succeed.

      Depending on the type of change being introduced, you may need to have more in-depth conversations with technical advisors, project management staff, and project sponsors concerning gaps and required content.

      Define training content and make key logistical decisions concerning training delivery for staff and users

      3.3.4 30-60 minutes

      Ultimately, the training plan will have to be put into action, which will require that the key logistical decisions are made concerning content and training delivery.

      The image is a screencapture of the Training Plan section of the Transition Plan Template.

      1. Use the “Training Plan” section in Info-Tech’s Transition Plan Template to document details of your training plan: schedules, resources, rooms, and materials required, etc.
      2. Designate who is responsible for developing the training content details. Responsibilities will include:
        • Developing content modules.
        • Determining the appropriate delivery model for each audience and content module (e.g. online course, classroom, outsourced, job shadowing, video tutorials, self-learning).
        • Finding and booking resources, locations, equipment, etc.

      “95% of learning leaders from organizations that are very effective at implementing important change initiatives find best practices by partnering with a company or an individual with experience in the type of change, twice as often as ineffective organizations.”

      Source: Implementing and Supporting Training for Important Change Initiatives.

      Training content should be developed and delivered by people with training experience and expertise, working closely with subject matter experts. In the absence of such individuals, partnering with experienced trainers is a cost that should be considered.

      Assess skills required to support the change that are currently absent or in short supply

      3.3.5 15 to 30 minutes

      The long-term success of the change is contingent on having the resources to maintain and support the tool, process, or business change being implemented. Otherwise, resourcing shortfalls could threaten the integrity of the new way of doing things post-change, threatening people’s trust and faith in the validity of the change as a whole.

      Use the table below to assess and record skills requirements. Refer to the tactics on the next slide for assistance in filling gaps.

      Skill Required Description of Need Possible Resources Recommended Next Steps Timeline
      Mobile Dev Users expect mobile access to services. We need knowledge of various mobile platforms, languages or frameworks, and UX/UI requirements for mobile.
      • Train web team
      • Outsource
      • Analyze current and future mobile requirements.
      Probably Q1 2015
      DBAs Currently have only one DBA, which creates a bottleneck. We need some DBA redundancy to mitigate risk of single point of failure.
      • Redeploy and train member of existing technology services team.
      • Hire or contract new resources.
      • Analyze impact of redeploying existing resources.
      Q3 2014

      Review your options for filling HR gaps

      Options: Benefits: Drawbacks:
      Redeploy staff internally
      • Retains firm-specific knowledge.
      • Eliminates substantial costs of recruiting and terminating employees.
      • Mitigates risk; reduces the number of unknowns that come with acquiring talent.
      • Employees could already be fully or over-allocated.
      • Employees might lack the skills needed for the new or enhanced positions.
      Outsource
      • Best for addressing short-term, urgent needs, especially when the skills and knowledge required are too new or unfamiliar to manage internally.
      • Risk of sharing sensitive information with third parties.
      • Opportunity cost of not investing in knowledge and skills internally.
      Contract
      • Best when you are uncertain how long needs for particular skills or budget for extra capacity will last.
      • Diminished loyalty, engagement, and organizational culture.
      • Similar drawbacks as with outsourcing.
      Hire externally
      • Best for addressing long-term needs for strategic or core skills.
      • Builds capacity and expertise to support growing organizations for the long term.
      • High cost of recruiting and onboarding.
      • Uncertainty: risk that new hires might have misrepresented their skills or won’t fit culturally.
      • Commitment to paying for skills that might diminish in demand and value over time.
      • Economic uncertainty: high cost of layoffs and buyouts.

      Report HR and training plan status to the transition team

      3.3.6 10 minutes (and ongoing thereafter)

      Ensure that any changes or developments made to HR and training plans are captured in the Transition Plan Template where applicable.
      1. Upon completion of the activities in this step, ensure that the “Training Plan” section of the template reflects outcomes and decisions made during the preceding activities.
      2. Assign ongoing RACI roles for informing the transition team of HR and training plan changes; similarly define accountabilities for keeping the template itself up to date.
      • Record these roles within the template itself under the “Roles & Responsibilities” section.
    • Be sure to schedule a date for eliciting training feedback in the “Training Schedule” section of the template.
      • A simple survey, such as those discussed in step 3.2, can go a long way in both helping stakeholders feel more involved in the change, and in making sure training mistakes and weaknesses are not repeated again and again on subsequent change initiatives.
    • Info-Tech Insight

      Try more ad hoc training methods to offset uncertain project timelines.

      One of the top challenges organizations face around training is getting it timed right, given the changes to schedule and delays that occur on many projects.

      One tactic is to take a more ad hoc approach to training, such as making IT staff available in centralized locations after implementation to address staff issues as they come up.

      This will not only help eliminate the waste that can come from poorly timed and ineffective training sessions, but it will also help with employee morale, giving individuals a sense that they haven’t been left alone to navigate unfamiliar processes or technologies.

      Adoption can be difficult for some, but the cause is often confusion and misunderstanding

      CASE STUDY

      Industry Manufacturing

      Source Info-Tech Client

      Challenge
      • The strategy team responsible for the implementation of a new operation manual for the subsidiaries of a global firm was monitoring the progress of newly acquired firms as the implementation of the manual began.
      • They noticed that one department in a distant location was not meeting the new targets or fulfilling the reporting requirements on staff progress.
      Solution
      • The strategy team representative for the subsidiary firm went to the manager leading the department that was slow to adopt the changes.
      • When asked, the manager insisted that he did not have the time or resources to implement all of these changes while maintaining the operation of the department.
      • With true business value in mind, the manager said, they chose to keep the plant running.
      Results
      • The representative from the strategy team was surprised to find that the manager was having such trouble fitting the changes into daily operations as the changes were the daily operations.
      • The representative took the time to go through the new operation manual with the manager and explain that the changes replaced daily operations and were not additions to them.

      "The cause of slow adoption is often not anger or denial, but a genuine lack of understanding and need for clarification. Avoid snap decisions about a lack of adoption until staff understand the details." – IT Manager

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      3.1.2 Undergo a stakeholder analysis to ensure positive stakeholder engagement

      Move away from a command-and-control approach to change by working with the analyst to develop a strategy that engages stakeholders in the change, making them feel like they are a part of it.

      3.2.3 Develop a stakeholder sentiment-sensitive communications strategy

      Work with the analyst to fine-tune the stakeholder messaging across various stakeholder responses to change.

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      3.2.5 Define a stakeholder feedback and evaluation process

      Utilize analyst experience and perspective in order to develop strategy for effectively evaluating stakeholder feedback early enough that resistance and suggestions can be accommodated with the OCM strategy and project plan.

      3.2.7 Develop a strategy to cut off resistance to change

      Utilize analyst experience and perspective in order to develop an objections handling strategy to deal with resistance, objections, and fatigue.

      3.3.4 Develop the training plan to ensure that the right goals are set, and that training is properly timed and communicated

      Receive custom analyst insights on rightsizing training content and timing your training sessions effectively.

      Phase 4

      Establish a Post-Project Benefits Attainment Process

      Phase 4 outline

      Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

      Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 4: Establish a Post-Project Benefits Attainment Process

      Proposed Time to Completion (in weeks): 1 to 2 weeks

      Step 4.1: Determine accountabilities for benefits attainment

      Discuss these issues with analyst:

      • Accountability for tracking the business outcomes of the project post-completion is frequently opaque, with little or no allocated resourcing.
      • As a result, projects may get completed, but their ROI to the organization is not tracked or understood.

      Then complete these activities…

      • Perform a post-implementation project review of the pilot OCM initiative.
      • Assign post-project benefits tracking accountabilities.
      • Implement a benefits tracking process and tool.

      With these tools & templates:

      • Portfolio Benefits Tracking Tool
      • Activity 4.1.2: “Assign ownership for realizing benefits after the project is closed”
      • Activity 4.1.3: “Define a post-project benefits tracking process”

      Step 4.1: Determine accountabilities for benefits attainment

      Phase 4 - 4.1

      This step will walk you through the following activities:
      • Conduct a post-implementation review of pilot OCM project.
      • Assign ownership for realizing benefits after the project is closed.
      • Define a post-project benefits tracking process.
      • Implement a tool to help monitor and track benefits over the long term.
      This step involves the following participants:
      • PMO Director
      • Project Sponsor
      • Project managers
      • Business analyst
      • Additional IT/PMO staff
      Outcomes of this step
      • Appropriate assignment of accountabilities for tracking benefits after the project has closed
      • A process for tracking benefits over the long-run
      • A benefits tracking tool

      Project benefits result from change

      A PMO that facilitates change is one that helps drive benefits attainment long after the project team has moved onto the next initiative.

      Organizations rarely close the loop on project benefits once a project has been completed.

      • The primary cause of this is accountability for tracking business outcomes post-project is almost always poorly defined, with little or no allocated resourcing.
      • Even organizations that define benefits well often neglect to manage them once the project is underway. If benefits realization is not monitored, the organization will miss opportunities to close the gap on lagging benefits and deliver expected project value.
      • It is commonly understood that the project manager and sponsor will need to work together to shift focus to benefits as the project progresses, but this rarely happens as effectively as it should.

      With all this in mind, in this step we will round out our PMO-driven org change process by defining how the PMO can help to better facilitate the benefits realization process.

      This section will walk you through the basic steps of developing a benefits attainment process through the PMO.

      For comprehensive guidance and tools, see Info-Tech’s Establish the Benefits Realization Process.

      Info-Tech Insight

      Two of a kind. OCM, like benefits realization, is often treated as “nice to have” rather than “must do.” These two processes are both critical to real project success; define benefits properly during intake and let OCM take the reigns after the project kicks off.

      The benefits realization process spans the project lifecycle

      Benefits realization ensures that the benefits defined in the business case are used to define a project’s expected value, and to facilitate the delivery of this value after the project is closed. The process begins when benefits are first defined in the business case, continues as benefits are managed through project execution, and ends when the loop is closed and the benefits are actually realized after the project is closed.

      Benefits Realization
      Define Manage Realize
      Initial Request Project Kick Off *Solution Is Deployed
      Business Case Approved Project Execution Solution Maintenance
      PM Assigned *Project Close Solution Decommissioned

      *For the purposes of this step, we will limit our focus to the PMO’s responsibilities for benefits attainment at project close-out and in the project’s aftermath to ensure that responsibilities for tracking business outcomes post-project have been properly defined and resourced.

      Ultimate project success hinges on a fellowship of the benefits

      At project close-out, stewardship of the benefits tracking process should pass from the project team to the project sponsor.

      As the project closes, responsibility for benefits tracking passes from the project team to the project sponsor. In many cases, the PMO will need to function as an intermediary here, soliciting the sponsor’s involvement when the time comes.

      The project manager and team will likely move onto another project and the sponsor (in concert with the PMO) will be responsible for measuring and reporting benefits realization.

      As benefits realization is measured, results should be collated by the PMO to validate results and help flag lagging benefits.

      The activities that follow in this step will help define this process.

      The PMO should ensure the participation of the project sponsor, the project manager, and any applicable members of the business side and the project team for this step.

      Ideally, the CIO and steering committee members should be involved as well. At the very least, they should be informed of the decisions made as soon as possible.

      Initiation-Planning-Execution-Monitoring & Controlling-Closing

      Conduct post-implementation review for your pilot OCM project

      4.1.1 60 minutes

      The post-project phase is the most challenging because the project team and sponsor will likely be busy with other projects and work.

      Conducting a post-implementation review for every project will force sponsors and other stakeholders to assess actual benefits realization and identify lagging benefits.

      If the project is not achieving its benefits, a remediation plan should be created to attempt to capture these benefits as soon as possible.

      Agenda Item
      Assess Benefits Realization
      • Compare benefits realized to projected benefits.
      • Compare benefit measurements with benefit targets.
      Assess Quality
      • Performance
      • Availability
      • Reliability
      Discuss Ongoing Issues
      • What has gone wrong?
      • Frequency
      • Cause
      • Resolution
      Discuss Training
      • Was training adequate?
      • Is any additional training required?
      Assess Ongoing Costs
      • If there are ongoing costs, were they accounted for in the project budget?
      Assess Customer Satisfaction
      • Review stakeholder surveys.

      Assign ownership for realizing benefits after the project is closed

      4.1.2 45 to 60 minutes

      The realization stage is the most difficult to execute and oversee. The project team will have moved on, and unless someone takes accountability for measuring benefits, progress will not be measured. Use the sample RACI table below to help define roles and responsibilities for post-project benefits attainment.

      Process Step Responsible Accountable Consulted Informed
      Track project benefits realization and document progress Project sponsor Project sponsor PMO (can provide tracking tools and guidance), and directors or managers in the affected business unit who will help gather necessary metrics for the sponsor (e.g. report an increase in sales 3 months post-project) PMO (can collect data and consolidate benefits realization progress across projects)
      Identify lagging benefits and perform root cause analysis Project sponsor and PMO Project sponsor and PMO Affected business unit CIO, IT steering committee
      Adjust benefits realization plan as needed Project sponsor Project sponsor Project manager, affected business units Any stakeholders impacted by changes to plan
      Report project success PMO PMO Project sponsor IT and project steering committees

      Info-Tech Insight

      A business accountability: Ultimately, the sponsor must help close this loop on benefits realization. The PMO can provide tracking tools and gather and report on results, but the sponsor must hold stakeholders accountable for actually measuring the success of projects.

      Define a post-project benefits tracking process

      4.1.3 45 minutes

      While project sponsors should be accountable for measuring actual benefits realization after the project is closed, the PMO can provide monitoring tools and it should collect measurements and compare results across the portfolio.

      Steps in a benefits tracking process.

      1. Collate the benefits of all the projects in your portfolio. Document each project’s benefits, with the metrics, targets, and realization timelines of each project in a central location.
      2. Collect and document metric measurements. The benefit owner is responsible for tracking actual realization and reporting it to the individual(s) tracking portfolio results.
      3. Create a timeline and milestones for benefits tracking. Establish a high-level timeline for assessing benefits, and put reminders in calendars accordingly, to ensure that commitments do not fall off stakeholders’ radars.
      4. Flag lagging benefits for further investigation. Perform root cause analysis to then find out why a benefit is behind schedule, and what can be done to address the problem.

      "Checking the results of a decision against its expectations shows executives what their strengths are, where they need to improve, and where they lack knowledge or information."
      Peter Drucker

      Implement a tool to help monitor and track benefits over the long term

      4.1.4 Times will vary depending on organizational specifics of the inputs

      Download Info-Tech’s Portfolio Benefits Tracking Tool to help solidify the process from the previous step.

      1. Document each project’s benefits, with the metrics, targets, and realization timelines. Tab 1 of the tool is a data entry sheet to capture key portfolio benefit forecasts throughout the project.
      2. Collect and document metric measurements. Tab 2 is where the PMO, with data from the project sponsors, can track actuals month after month post-implementation.
      3. Flag lagging benefits for further investigation. Tab 3 provides a dashboard that makes it easy to flag lagging benefits. The dashboard produces a variety of meaningful benefit reports including a status indication for each project’s benefits and an assessment of business unit performance.

      Continue to increase accountability for benefits and encourage process participation

      Simply publishing a set of best practices will not have an impact unless accountability is consistently enforced. Increasing accountability should not be complicated. Focus on publicly recognizing benefit success. As the process matures, you should be able to use benefits as a more frequent input to your budgeting process.

      • Create an internal challenge. Publish the dashboard from the Portfolio Benefits Tracking Tool and highlight the top 5 or 10 projects that are on track to achieve benefits. Recognize the sponsors and project team members. Recognizing individuals for benefits success will get people excited and encourage an increased focus on benefits.
      • With executive level involvement, the PMO could help institute a bonus structure based on benefits realization. For instance, project teams could be rewarded with bonuses for achieving benefits. Decide upon a set post-project timeline for determining this bonus. For example, 6 months after every project goes live, measure benefits realization. If the project has realized benefits, or is on track to realize benefits, the PM should be given a bonus to split with the team.
      • Include level of benefits realization in the performance reviews of project team members.
      • As the process matures, start decreasing budgets according to the monetary benefits documented in the business case (if you are not already doing so). If benefits are being used as inputs to the budgeting process, sponsors will need to ensure that they are defined properly.

      Info-Tech Insight

      Don’t forget OCM best practices throughout the benefits tracking process. If benefits are lagging, the PMO should revisit phase 3 of this blueprint to consider how challenges to adoption are negatively impacting benefits attainment.

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      4.1.2 Assign appropriate ownership and ensure adequate resourcing for realizing benefits after the project is closed

      Get custom insights into how the benefits tracking process should be carried out post-project at your organization to ensure that intended project outcomes are effectively monitored and, in the long run, achieved.

      4.1.4 Implement a benefits tracking tool

      Let our analysts customize a home-grown benefits tracking tool for your organization to ensure that the PMO and project sponsors are able to easily track benefits over time and effectively pivot on lagging benefits.

      Phase 5

      Solidify the PMO’s Role as Change Leader

      Phase 5 outline

      Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

      Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 5: Solidify the PMO’s role as change leader

      Proposed Time to Completion (in weeks): 1 to 2 weeks

      Step 5.1: Institute an organizational change management playbook

      Discuss these issues with an analyst:

      • With the pilot OCM initiative complete, the PMO will need to roll out an OCM program to accommodate all of the organization’s projects.
      • The PMO will need to facilitate organization-wide OCM accountabilities – whether it’s the PMO stepping into the role of OCM leader, or other appropriate accountabilities being assigned.

      Then complete these activities…

      • Review the success of the pilot OCM initiative.
      • Define organizational roles and responsibilities for change management.
      • Formalize the Organizational Change Management Playbook.

      With these tools & templates:

      • Organizational Change Management Playbook
      • Activity 5.1.1: “Review lessons learned to improve organizational change management as a core discipline of the PMO”
      • Activity 5.1.3: “Define ongoing organizational roles and responsibilities for change management”

      Step 5.1: Institute an organizational change management playbook

      Phase 5 - 5.1

      This step will walk you through the following activities:
      • Review lessons learned to improve OCM as a core discipline of the PMO.
      • Monitor organizational capacity for change.
      • Define organizational roles and responsibilities for change management.
      • Formalize the Organizational Change Management Playbook.
      • Assess the value and success of the PMO’s OCM efforts.
      This step involves the following participants:
      • Required: PMO Director; PMO staff
      • Strongly recommended: CIO and other members of the executive layer
      Outcomes of this step
      • A well-defined organizational mandate for change management, whether through the PMO or another appropriate stakeholder group
      • Definition of organizational roles and responsibilities for change management
      • An OCM playbook
      • A process and tool for ongoing assessment of the value of the PMO’s OCM activities

      Who, in the end, is accountable for org change success?

      We return to a question that we started with in the Executive Brief of this blueprint: who is accountable for organizational change?

      If nobody has explicit accountability for organizational change on each project, the Officers of the corporation retained it. Find out who is assumed to have this accountability.

      On the left side of the image, there is a pyramid with the following labels in descending order: PMO; Project Sponsors; Officers; Directors; Stakeholders. The top three tiers of the pyramid have upward arrows connecting one section to the next; the bottom three tiers have downward pointing arrows, connecting one section to the next. On the right side of the image is the following text: If accountability for organizational change shifted to the PMO, find out and do it right. PMOs in this situation should proceed with this step. Officers of the corporation have the implicit fiduciary obligation to drive project benefits because they ultimately authorize the project spending. It’s their job to transfer that obligation, along with the commensurate resourcing and authority. If the Officers fail to make someone accountable for results of the change, they are failing as fiduciaries appointed by the Board of Directors. If the Board fails to hold the Officers accountable for the results, they are failing to meet the obligations they made when accepting election by the Shareholders.

      Info-Tech Insight

      Will the sponsor please stand up?

      Project sponsors should be accountable for the results of project changes. Otherwise, people might assume it’s the PMO or project team.

      Keep your approach to change management dynamic while building around the core discipline

      The PMO will need to establish an OCM playbook that can scale to a wide variety of projects. Avoid rigidity of processes and keep things dynamic as you build up your OCM muscles as an organization.

      Continually Develop

      Change Management Capabilities

      Progressively build a stable set of core capabilities.

      The basic science of human behavior underlying change management is unlikely to change. Effective engagement, communication, and management of uncertainty are valuable capabilities regardless of context and project specifics.

      Regularly Update

      Organizational Context

      Regularly update recurring activities and artifacts.

      The organization and the environment in which it exists will constantly evolve. Reusing or recycling key artifacts will save time and improve collaboration (by leveraging shared knowledge), but you should plan to update them on at least a quarterly or annual basis.

      Respond To

      Future Project Requirements

      Approach every project as unique.

      One project might involve more technology risk while another might require more careful communications. Make sure you divide your time and effort appropriately for each particular project to make the most out of your change management playbook.

      Info-Tech Insight

      Continuous Change. Continuous Improvement. Change is an ongoing process. Your approach to managing change should be continually refined to keep up with changes in technology, corporate strategy, and people involved.

      Review lessons learned to improve organizational change management as a core discipline of the PMO

      5.1.1 60 minutes

      1. With your pilot OCM initiative in mind, retrospectively brainstorm lessons learned using the template below. Info-Tech recommends doing this with the transition team. Have people spend 10-15 minutes brainstorming individually or in 2- to 3-person groups, then spend 15-30 minutes presenting and discussing findings collectively.

      What worked? What didn't work? What was missing?

      2. Develop recommendations based on the brainstorming and analysis above.

      Continue... Stop... Start...

      Monitor organizational capacity for change

      5.1.2 20 minutes (to be repeated quarterly or biannually thereafter)

      Perform the Organizational Change Management Capabilities Assessment in the wake of the OCM pilot initiative and lessons learned exercise to assess capabilities’ improvements.

      As your OCM processes start to scale out over a range of projects across the organization, revisit the assessment on a quarterly or bi-annual basis to help focus your improvement efforts across the 7 change management categories that drive the survey.

      • Cultural Readiness
      • Leadership & Sponsorship
      • Organizational Knowledge
      • Change Management Skills
      • Toolkit & Templates
      • Process Discipline
      • KPIs & Metrics

      The image is a bar graph, with the above mentioned change management categories on the Y-axis, and the categories Low, Medium, and High on the X-axis.

      Info-Tech Insight

      Continual OCM improvement is a collaborative effort.

      The most powerful way to drive continual improvement of your organizational change management practices is to continually share progress, wins, challenges, feedback, and other OCM related concerns with stakeholders. At the end of the day, the PMO’s efforts to become a change leader will all come down to stakeholder perceptions based upon employee morale and benefits realized.

      Define ongoing organizational roles and responsibilities for change management

      5.1.3 60 minutes

      1. Decide whether to designate/create permanent roles for managing change.
      • Recommended if the PMO is engaged in at least one project at any given time that generates organizational change.
    • Designate a principle change manager (if you choose to) – it is likely that responsibilities will be given to someone’s existing position (such as PM or BA).
      • Make sure any permanent roles are embedded in the organization (e.g. within the PMO, rather than trying to establish a one-person “Change Management Office”) and have leadership support.
    • Consider whether to build a team of permanent change champions – it is likely that responsibilities will be given to existing positions.
      • This type of role is increasingly common in organizations that are aggressively innovating and keeping up with consumer technology adoption. If your organization already has a program like this for engaging early adopters and innovators, build on what’s already established.
      • Work with HR to make sure this is aligned with any existing training and development programs.
    • Info-Tech Insight

      Avoid creating unnecessary fiefdoms.

      Make sure any permanent roles are embedded in the organization (e.g. within the PMO) and have leadership support.

      Copy the RACI table from Activity 3.1.1. and repurpose it to help define the roles and responsibilities.

      Include this RACI when you formalize your OCM Playbook.

      Formalize and communicate the Organizational Change Management Playbook

      5.1.4 45 to 60 minutes

      1. Formalize the playbook’s scope:
        1. Determine the size and type of projects for which organizational change management is recommended.
        2. Make sure you clearly differentiate organizational change management and enablement from technical change management (i.e. release management and acceptance).
      2. Refine and formalize tools and templates:
        1. Determine how you want to customize the structure of Info-Tech’s blueprint and templates, tailored to your organization in the future.
          1. For example:
            1. Establish a standard framework for analyzing context around organizational change.
        2. Add branding/design elements to the templates to improve their credibility and impact as internal documents.
        3. Determine where/how templates and other resources are to be found and make sure they will be readily available to anyone who needs them (e.g. project managers).
      3. Communicate the playbook to the project management team.

      Download Info-Tech’s Organizational Change Management Playbook.

      Regularly reassess the value and success of your practices relative to OCM effort and project outcomes

      5.1.5 20 minutes per project

      The image is a screencapture of the Value tab of the Organizational Change: Management Capabilities Assessment

      Use the Value tab in the Organizational Change Management Capabilities Assessment to monitor the value and success of OCM.

      Measure past performance and create a baseline for future success:

      • % of expected business benefits realized on previous 3–5 significant projects/programs.
        • Track business benefits (costs reduced, productivity increased, etc.).
      • Costs avoided/reduced (extensions, cancellations, delays, roll-backs, etc.)
        • Establish baseline by estimating average costs of projects extended to deal with change-related issues.

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      5.1.3 Define ongoing organizational roles and responsibilities for change management

      As you scale out an OCM program for all of the organization’s projects based on your pilot initiative, work with the analyst to investigate and define the right accountabilities for ongoing, long-term OCM.

      5.1.4 Develop an Organizational Change Management Playbook

      Formalize a programmatic process for organizational change management in Info-Tech’s playbook template.

      Related research

      Develop a Project Portfolio Management Strategy

      Grow Your Own PPM Solution

      Optimize Project Intake, Approval, and Prioritization

      Develop a Resource Management Strategy for the New Reality

      Manage a Minimum-Viable PMO

      Establish the Benefits Realization Process

      Manage an Agile Portfolio

      Project Portfolio Management Diagnostic Program: The Project Portfolio Management Diagnostic Program is a low effort, high impact program designed to help project owners assess and improve their PPM practices. Gather and report on all aspects of your PPM environment in order to understand where you stand and how you can improve.

      Bibliography

      Basu, Chirantan. “Top Organizational Change Risks.” Chiron. Web. June 14, 2016.

      Beatty, Carol. “The Tough Work of Managing Change.” Queens University. 2015. Web. June 14, 2016.

      Brown, Deborah. “Change Management: Some Statistics.” D&B Consulting Inc. May 15, 2014. Web. June 14, 2016.

      Burke, W. Warner. Organizational Change: Theory and Practice. 4th Edition. London: Sage, 2008.

      Buus, Inger. “Rebalancing Leaders in Times of Turbulence.” Mannaz. February 8, 2013. Web. June 14, 2016.

      Change First. “Feedback from our ROI change management survey.” 2010. Web. June 14, 2016.

      Collins, Jeff. “The Connection between User Adoption and Project Management Success.” Innovative Management Solutions. Sept. 21, 2013. Web. June 14, 2016.

      Craddock, William. “Change Management in the Strategic Alignment of Project Portfolios.” PMI. 2015. Web. June 14, 2016.

      Denning, Steve. “The Four Stories you Need to Lead Deep Organizational Change.” Forbes. July 25, 2011. Web. June 14, 2016.

      Drucker, Peter. “What Makes an Effective Executive.” Harvard Business Review. June 2004. Web. June 14, 2016

      Elwin, Toby. “Highlight Change Management – An Introduction to Appreciative Inquiry.” July 6, 2012. Web. June 14, 2016.

      Enstrom, Christopher. “Employee Power: The Bases of Power Used by Front-Line Employees to Effect Organizational Change.” MA Thesis. University of Calgary. April 2003. Web. June 14, 2016.

      Ewenstein, Boris, Wesley Smith, and Ashvin Sologar. “Changing Change Management.” McKinsey & Company. July 2015. Web. June 14, 2016.

      International Project Leadership Academy. “Why Projects Fail: Facts and Figures.” Web. June 14, 2016.

      Jacobs-Long, Ann. “EPMO’s Can Make A Difference In Your Organization.” May 9, 2012. Web. June 14, 2016.

      Kotter, John. Leading Change. Boston: Harvard Business School Press, 1996.

      Latham, Ross. “Information Management Advice 55 Change Management: Preparing for Change.” TAHO. March 2014. Web. June 14, 2016.

      Linders, Ben. “Finding Ways to Improve Business – IT Collaboration.” InfoQ. June 6, 2013. Web. June 14, 2016

      Machiavelli, Niccolo. The Prince, selections from The Discourses and other writings. Ed. John Plamenatz. London: Fontana/Collins, 1972.

      Michalak, Joanna Malgorzata. “Cultural Catalyst and Barriers to Organizational Change Management: a Preliminary Overview.” Journal of Intercultural Management. 2:2. November 2010. Web. June 14, 2016.

      Miller, David, and Mike Oliver. “Engaging Stakeholder for Project Success.” PMI. 2015. Web. June 14, 2016.

      Parker, John. “How Business Analysts Can Identify Quick Wins.” EnFocus Solutions. February 15, 2013. Web. June 14, 2016.

      Paulk, January. “The Fundamental Role a Change Impact Analysis Plays in an ERP Implementation.” Panorma Consulting Solutions. March 24, 2014. Web. June 14, 2016.

      Petouhoff, Natalie, Tamra Chandler, and Beth Montag-Schmaltz. “The Business Impact of Change Management.” Graziadio Business Review. 2006. Web. June 14, 2016.

      PM Solutions. “The State of the PMO 2014.” 2014. Web. June 14, 2016.

      PMI. “Pulse of the Profession: Enabling Organizational Change Throughout Strategic Initiatives.” March 2014. Web. June 14, 2016.

      PMI. “Pulse of the Profession: Executive Sponsor Engagement.” October 2014. Web. June 14, 2016.

      PMI. “Pulse of the Profession: the High Cost of Low Performance.” February 2014. Web. June 14, 2016.

      Powers, Larry, and Ketil Been. “The Value of Organizational Change Management.” Boxley Group. 2014. Web. June 14, 2016.

      Prosci. “Best Practices in Change Management – 2014 Edition: Executive Overview.” Web. June 14, 2016.

      Prosci. “Change Management Sponsor Checklist.” Web. June 14, 2016.

      Prosci. “Cost-benefit analysis for change management.” 2014. Web. June 14, 2016.

      Prosci. “Five Levers of Organizational Change.” 2016. Web. June 14, 2016.

      Rick, Torben. “Change Management Requires a Compelling Story.” Meliorate. October 3, 2014. Web. June 14, 2016.

      Rick, Torben. “The Success Rate of Organizational Change Initiatives.” Meliorate. October 13, 2014. Web. June 14, 2016.

      Schwartz, Claire. “Implementing and Monitoring Organizational Change: Part 3.” Daptiv Blogs. June 24, 2013. Web. June 14, 2016.

      Simcik, Shawna. “Shift Happens! The Art of Change Management.” Innovative Career Consulting, Inc. Web. June 14, 2016.

      Stewart Group. “Emotional Intelligence.” 2014. Web. June 14, 2016.

      Thakur, Sidharth. “Improve your Project’s Communication with These Inspirational Quotes.” Ed. Linda Richter. Bright Hub Project Management. June 9, 2012. Web. June 14, 2016.

      Training Folks. “Implementing and Supporting Training for Important Change Initiatives.” 2012. Web. June 14, 2016.

      Warren, Karen. “Make your Training Count: The Right Training at the Right Time.” Decoded. April 12, 2015. Web. June 14, 2016.

      Willis Towers Watson. “Only One-Quarter of Employers Are Sustaining Gains from Change Management Initiatives, Towers Watson Survey Finds.” August 29, 2013. Web. June 14, 2016.

      Lead Staff through Change

      • Buy Link or Shortcode: {j2store}510|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: High Impact Leadership
      • Parent Category Link: /lead
      • Sixty to ninety percent of change initiatives fail, costing organizations dollars off the bottom line and lost productivity.
      • Seventy percent of change initiatives fail because of people-related issues, which place a major burden on managers to drive change initiatives successfully.
      • Managers are often too busy focusing on the process elements of change; as a result, they neglect major opportunities to leverage and mitigate staff behaviors that affect the entire team.

      Our Advice

      Critical Insight

      • Change is costly, but failed change is extremely costly. Managing change right the first time is worth the time and effort.
      • Staff pose the biggest opportunity and risk when implementing a change – managers must focus on their teams in order to maintain positive change momentum.
      • Large and small changes require the same change process to be followed but at different scales.
      • The size of a change must be measured according to the level of impact the change will have on staff, not how executives and managers perceive the change.
      • To effectively lead their staff through change, managers must anticipate staff reaction to change, develop a communication plan, introduce the change well, help their staff let go of old behaviors while learning new ones, and motivate their staff to adopt the change.

      Impact and Result

      • Anticipate and respond to staff questions about the change in order to keep messages consistent, organized, and clear.
      • Manage staff based on their specific concerns and change personas to get the best out of your team during the transition through change.
      • Maintain a feedback loop between staff, executives, and other departments in order to maintain the change momentum and reduce angst throughout the process.

      Lead Staff through Change Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Learn how to manage people throughout the change process

      Set up a successful change adoption.

      • Storyboard: Lead Staff through Change

      2. Learn the intricacies of the change personas

      Correctly identify which persona most closely resembles individual staff members.

      • None

      3. Assess the impact of change on staff

      Ensure enough time and effort is allocated in advance to people change management.

      • Change Impact Assessment Tool

      4. Organize change communications messages for a small change

      Ensure consistency and clarity in change messages to staff.

      • Basic Business Change Communication Worksheet

      5. Organize change communications messages for a large change

      Ensure consistency and clarity in change messages to staff.

      • Advanced Business Change Description Form

      6. Evaluate leadership of the change process with the team

      Improve people change management for future change initiatives.

      • Change Debrief Questionnaire
      [infographic]

      Renovate the Data Center

      • Buy Link or Shortcode: {j2store}497|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Data Center & Facilities Optimization
      • Parent Category Link: /data-center-and-facilities-optimization
      • 33% of enterprises will be undertaking facility upgrades or refreshes in 2010 aimed at extending the life of their existing data centers.
      • Every upgrade or refresh targeting specific components in the facility to address short-term pain will have significant impact on the data center environment as a whole. Planning upfront and establishing a clear project scope will minimize expensive changes in later years.
      • This solution set will provide you with step-by-step design, planning, and selection tools to define a Data Center renovation plan to reduce cost and risk while supporting cost-effective long-term growth for power, cooling, standby power, and fire protection renovations.

      Our Advice

      Critical Insight

      • 88% of organizations cited they would spend more time and effort on documenting and identifying facility requirements for initial project scoping. Organizations can prevent scope creep by conducting the necessary project planning up front and identify requirements and the effect that the renovation project will have in all areas of the data center facility.
      • Data Center facilities renovations must include the specific requirements related to power provisioning, stand-by power, cooling, and fire protection - not just the immediate short-term pain.
      • 39% of organizations cited they would put more emphasis on monitoring contractor management and performance to improve the outcome of the data center renovation project.

      Impact and Result

      • Early internal efforts to create a budget and facility requirements yields better cost and project outcomes when construction begins. Each data center renovation project is unique and should have its own detailed budget.
      • Upfront planning and detailed project scoping can prevent a cascading impact on data center renovation projects to other areas of the data center that can increase project size, scope and spend.
      • Contractor selection is one of the most important first steps in a complex data center renovation. Organizations must ensure the contractor selected has experience specifically in data center renovation.

      Renovate the Data Center Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Identify and understand the renovation project.

      • Storyboard: Renovate the Data Center
      • None
      • Data Center Annual Review Checklist

      2. Renovate power in the data center.

      • Data Center Power Requirements Calculator

      3. Renovate cooling in the data center.

      • Data Center Cooling Requirements Calculator

      4. Renovate standby power in the data center.

      • Data Center Standby Power Requirements Calculator

      5. Define current and future fire protection requirements.

      • Fire Protection & Suppression Engineer Selection Criteria Checklist
      • None

      6. Assess the opportunities and establish a clear project scope.

      • Data Center Renovation Project Charter
      • Data Center Renovation Project Planning & Monitoring Tool

      7. Establish a budget for the data center renovation project.

      • Data Center Renovation Budget Tool

      8. Select a general contractor to execute the project.

      • None
      • Data Center Renovation Contractor Scripted Interview
      • Data Center Renovation Contractor Scripted Interview Scorecard
      • Data Center Renovation Contractor Reference Checklist
      [infographic]

      Optimize Your Software Selection Process: Why 5 and 30 Are the Magic Numbers

      • Buy Link or Shortcode: {j2store}607|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Selection & Implementation
      • Parent Category Link: /selection-and-implementation
      • Software selection takes forever. The process of choosing even the smallest apps can drag on for years: sometimes in perpetuity. Software selection teams are sprawling, leading to scheduling slowdowns and scope creep. Moreover, cumbersome or ad hoc selection processes lead to business-driven software selection.

      Our Advice

      Critical Insight

      • Maximize project effectiveness with a five-person team. Project satisfaction and effectiveness is stagnant or decreases once the team grows beyond five people.
      • Tight project timelines are critical. Keep stakeholders engaged with a defined application selection timeline that moves the project forward briskly – 30 days is optimal.
      • Empower both IT and end users with a standardized selection process to consistently achieve high satisfaction coming out of software selection projects.

      Impact and Result

      • Shatter stakeholder expectations with truly rapid application selections.
      • Put the “short” back in shortlist by consolidating the vendor shortlist up-front and reducing downstream effort.
      • Identify high-impact software functionality by evaluating fewer use cases.
      • Lock in hard savings and do not pay list price by using data-driven tactics.

      Optimize Your Software Selection Process: Why 5 and 30 Are the Magic Numbers Research & Tools

      Discover the Magic Numbers

      Increase project satisfaction with a five-person core software selection team that will close out projects within 30 days.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      • Optimize Your Software Selection Process: Why 5 and 30 Are the Magic Numbers Storyboard

      1. Align and eliminate elapsed time

      Ensure a formal selection process is in place and make a concerted effort to align stakeholder calendars.

      2. Reduce low-impact activities

      Reduce time spent watching vendor dog and pony shows, while reducing the size of your RFPs or skipping them entirely.

      3. Focus on high-impact activities

      Narrow the field to four contenders prior to in-depth comparison and engage in accelerated enterprise architecture oversight.

      4. Use these rapid and essential selection tools

      Focus on key use cases rather than lists of features.

      • The Software Selection Workbook
      • The Vendor Evaluation Workbook
      • The Guide to Software Selection: A Business Stakeholder Manual

      5. Engage Two Viable Vendors in Negotiation

      Save more by bringing two vendors to the final stage of the project and surfacing a consolidated list of demands prior to entering negotiation.

      [infographic]

      Further reading

      Optimize Your Software Selection Process: Why 5 and 30 Are the Magic Numbers

      Select your applications better, faster, and cheaper.

      How to Read This Software Selection Insight Primer

      1. 43,000 Data Points
      2. This report is based on data gathered from a survey of 43,000 real-world IT practitioners.

      3. Aggregating Feedback
      4. The data is compiled from SoftwareReviews (a sister company of Info-Tech Research Group), which collects and aggregates feedback on a wide variety of enterprise technologies.

      5. Insights Backed by Data
      6. The insights, charts, and graphs in this presentation are all derived from data submitted by real end users.

      The First Magic Number Is Five

      The optimal software selection team comprises five people

      • Derived from 43,000 data points. Analysis of thousands of software selection projects makes it clear a tight core selection team accelerates the selection process.
      • Five people make up the core team. A small but cross-functional team keeps the project moving without getting bogged down on calendar alignment and endless back-and-forth.
      • It is a balancing act. Having too few stakeholders on the core selection team will lead to missing valuable information, while having too many will lead to delays and politically driven inefficiencies.

      There Are Major Benefits to Narrowing the Selection Team Size to Five

      Limit the risk of ineffective “decision making by committee”

      Expedite resolution of key issues and accelerate crucial decisions

      Achieve alignment on critical requirements

      Streamline calendar management

      Info-Tech Insight

      Too many cooks spoil the broth: create a highly focused selection team that can devote the majority of its time to the project while it’s in flight to demonstrate faster time to value.

      Arm Yourself With Data to Choose the Right Plays for Selection

      Software selection takes forever. The process of choosing even the smallest apps can drag on for years: sometimes in perpetuity.

      Organizations keep too many players on the field, leading to scheduling slowdowns and scope creep.

      Keeping the size of the core selection team down, while liaising with more stakeholders and subject matter experts (SMEs), leads to improved results.

      Maximize project effectiveness with a five-person team. Project satisfaction and effectiveness are stagnant or decrease once the team grows beyond five people.

      Cumbersome or ad hoc selection processes lead to business-driven software selection.

      Increase stakeholder satisfaction by using a consistent selection framework that captures their needs while not being a burden.

      Empower both IT and end users with a standardized selection process to consistently achieve high satisfaction coming out of software selection projects.

      The image contains a graph that is titled: A compact selection team can save you weeks. The graph demonstrates time saved with a five person team in comparison to larger teams.

      Project Satisfaction and Effectiveness Are Stagnant Once the Team Grows Beyond Five People

      The image contains a graph to demonstrate project satisfaction and effectiveness being stagnant with a team larger than five.
      • There is only a marginal difference in selection effectiveness when more people are involved, so why include so many? It only bogs down the process!
      • Full-time resourcing: At least one member of the five team members must be allocated to the selection initiative as a full-time resource.

      Info-Tech Insight

      It sounds natural to include as many players as possible in the core selection group; however, expanding the group beyond five people does not lead to an increase in satisfaction. Consider including a general stakeholder feedback working session instead.

      Shorten Project Duration by Capping the Selection Team at Five People

      However, it is important to make all stakeholders feel heard

      The image contains a graph to demonstrate that an increase in time and effort connects with an increase in total number of people involved.

      Exclusion is not the name of the game.

      • Remember, we are talking about the core selection team.
      • Help stakeholders understand their role in the project.
      • Educate stakeholders about your approach to selection.
      • Ensure stakeholders understand why the official selection team is being capped at five people.
      • Soliciting requirements and feedback from a broader array of stakeholders is still critical.

      Large Organizations Benefit From Compact Selection Teams Just as Much as Small Firms

      Think big even if your organization is small

      Small organizations

      Teams smaller than five people are common due to limited resources.

      Medium organizations

      Selection project satisfaction peaks with teams of fewer than two people. Consider growing the team to about five people to make stakeholders feel more included with minimal drops in satisfaction.

      Large organizations

      Satisfaction peaks when teams are kept to three to five people. With many SMEs available, it is critical to choose the right players for your team.

      The image contains a multi bar graph to demonstrate the benefits of compact selection teams depending on the size of the company, small, medium, or large.

      Keep the Core Selection Team to Five People Regardless of the Software Category

      Smaller selection teams yield increased satisfaction across software categories

      Info-Tech Insight

      Core team size remains the same regardless of the application being selected. However, team composition will vary depending on the end users being targeted.

      Think beyond application complexity

      • Our instinct is to vary the size of the core selection team based on perceived application complexity.
      • The data has demonstrated that a small team yields increased satisfaction for applications across a wide array of application complexity profiles.
      • The real differentiator for complex applications will be the number of stakeholders that the core selection team liaise with, particularly for defining strong requirements.

      The image contains a graph to demonstrate satisfaction across software categories increases with smaller selection teams.

      The Second Magic Number Is 30

      Finish the project while stakeholders are still fully engaged in order to maximize satisfaction

      • 30- to 60-day project timelines are critical. Keep stakeholders engaged with a defined application selection timeline that moves the project forward briskly.
      • Strike while the iron is hot. Deliver applications in a timely manner after the initial request. Don’t let IT become the bottleneck for process optimization.
      • Minimize scope creep: As projects drag on in perpetuity, the scope of the project balloons to something that cannot possibly achieve key business objectives in a timely fashion.

      Aggressively Timeboxing the Project Yields Benefits Across Multiple Software Categories

      After four weeks, stakeholder satisfaction is variable

      The image contains a graph to demonstrate that aggressively timeboxing the project yields benefits across multiple software categories.
      Only categories with at least 1,000 responses were included in the analysis.

      Achieve peak satisfaction by allotting 30 days for an application selection project.

      • Spending two weeks or less typically leads to higher levels of satisfaction for each category because it leaves more time for negotiation, implementation, and making sure everything works properly (especially if there is a time constraint).
      • Watch out for the “satisfaction danger zone” once project enters the 6- to 12-week mark. Completing a selection in four weeks yields greater satisfaction.

      Spend Your Time Wisely to Complete the Selection in 30 Days

      Save time in the first three phases of the selection project

      Awareness

      Education & Discovery

      Evaluation

      Reduce Time

      Reduce Time

      Reduce Time

      Save time duplicating existing market research. Save time and maintain alignment with focus groups.

      Save time across tedious demos and understanding the marketplace.

      Save time gathering detailed historical requirements. Instead, focus on key issues.

      Info-Tech Insight – Awareness

      Timebox the process of impact analysis. More time should be spent performing the action than building a business case.

      Info-Tech Insight – Education

      Save time duplicating existing market research. Save time and maintain alignment with focus groups.

      Info-Tech Insight – Evaluation

      Decision committee time is valuable. Get up to speed using third-party data and written collateral. Use committee time to conduct investigative interviews instead. Salesperson charisma and marketing collateral quality should not be primary selection criteria. Sadly, this is the case far too often.

      Limit Project Duration to 30 Days Regardless of the Application Being Selected

      Timeboxing application selection yields increased satisfaction across software categories

      The image contains a graph to demonstrate selection effort in weeks by satisfaction. The graph includes informal and formal methods on the graph across the software categories.

      Info-Tech Insight

      Office collaboration tools are a great case study for increasing satisfaction with decreased time to selection. Given the sharp impetus of COVID-19, many organizations quickly selected tools like Zoom and Teams, enabling remote work with very high end-user satisfaction.

      There are alternative approaches for enterprise-sized applications:

      • New applications that demand rigorous business process improvement efforts may require allotting time for prework before engaging in the 30-day selection project.
      • To ensure that IT is using the right framework, understand the cost and complexity profile of the application you’re looking to select.

      The Data Also Shows That There Are Five Additional Keys to Improving Your Selection Process

      1. ALIGN & ELIMINATE ELAPSED TIME
      • Ensure a formal selection process is in place.
      • Balance the core selection team’s composition.
      • Make a concerted effort to align stakeholder calendars.
      2. REDUCE TIME SPENT ON LOW-IMPACT ACTIVITIES
      • Reduce time spent on internet research. Leverage hard data and experts.
      • Reduce RFP size or skip RFPs entirely.
      • Reduce time spent watching vendor dog and pony shows.
      3. FOCUS ON HIGH- IMPACT ACTIVITIES
      • Narrow the field to four contenders prior to in-depth comparison.
      • Identify portfolio overlap with accelerated enterprise architecture oversight.
      • Focus on investigative interviews and proof of concept projects.
      4. USE RAPID & ESSENTIAL ASSESSMENT TOOLS
      • Focus on key use cases, not lists of features.
      • You only need three essential tools: Info-Tech’s Vendor Evaluation Workbook, Software Selection Workbook, and Business Stakeholder Manual.
      5. ENGAGE TWO VIABLE VENDORS IN NEGOTIATION
      • Save more during negotiation by selecting two viable alternatives.
      • Surface a consolidated list of demands prior to entering negotiation.
      • Communicate your success with the organization.

      1. Align & Eliminate Elapsed Time

      ✓ Ensure a formal selection process is in place.

      ✓ Reduce time by timeboxing the project to 30 days.

      ✓ Align the calendars of the five-person core selection team.

      Improving Your IT Department’s Software Selection Capability Yields Big Results

      Time spent building a better process for software selection is a great investment

      • Enterprise application selection is an activity that every IT department must embark on, often many times per year.
      • The frequency and repeatability of software selection means it is an indispensable process to target for optimization.
      • A formal process is not always synonymous with a well-oiled process.
      • Even if you have a formal selection process already in place, it’s imperative to take a concerted approach to continuous improvement.

      It is critical to improve the selection process before formalizing

      Leverage Info-Tech’s Rapid Application Selection Framework to gain insights on how you can fine-tune and accelerate existing codified approaches to application selection.

      Before Condensing the Selection Team, First Formalize the Software Selection Process

      Software selection processes are challenging

      Vendor selection is politically charged, requiring Procurement to navigate around stakeholder biases and existing relationships.

      Stakeholders

      The process is time consuming and often started too late. In the absence of clarity around requirements, it is easy to default to looking at price instead of best functional and architectural fit.

      Timing

      Defining formal process and methodology

      Formal selection methodologies are repeatable processes that anybody can consistently follow to quickly select new technology.

      Repeatable

      The goal of formalizing the approach is to enable IT to deliver business value consistently while also empowering stakeholders to find tools that meet their needs. Remember! A formal selection process is synonymous with a bureaucratic, overblown approach.

      Driving Value

      Most Organizations Are Already Using a Formal Software Selection Methodology

      Don’t get left behind!

      • A common misconception for software selection is that only large organizations have formal processes.
      • The reality is that organizations of all sizes are making use of formal processes for software selection.
      • Moreover, using a standardized method to evaluate new technology is most likely common practice among your competitors regardless of their size.
      • It is important to remember that the level of rigor for the processes will vary based not only on project size but also on organization size.
      Only categories with at least 1,000 responses were included in the analysis.

      The image contains a double bar graph that compares the sizes of companies using formal or informal evaluation and selection methodology.

      Use a Formal Evaluation and Selection Methodology to Achieve Higher Satisfaction

      A formal selection process does not equal a bloated selection process

      • No matter what process is being used, you should consider implementing a formal methodology to reduce the amount of time required to select the software. This trend continues across different levels of software (commodity, complex, and enterprise).
      • It is worth noting that using a process can actually add more time to the selection process, so it is important to know how to use it properly.
      • Don’t use just one process: you should use a combination, but don’t use more than three when selecting your software.
      The image contains a double bar graph to demonstrate the difference between formal and informal evaluation to achieve a higher satisfaction.

      Hit a Home Run With Your Business Stakeholders

      Use a data-driven approach to select the right application vendor for their needs – fast

      The image contains a screenshot of the data-drive approach. The approach includes: awareness, education & discovery, evaluation, selection, negotiation & configuration.

      Investing time improving your software selection methodology has big returns.

      Info-Tech Insight

      Not all software selection projects are created equal – some are very small; some span the entire enterprise. To ensure that IT is using the right framework, understand the cost and complexity profile of the application you’re looking to select. The Rapid Application Selection Framework approach is best for commodity and mid-tier enterprise applications; selecting complex applications is better handled by the methodology described in Implement a Proactive and Consistent Vendor Selection Process.

      Lock Down the Key Players Before Setting Up the Relevant Timeline

      You are the quarterback of your selection team

      Don’t get bogged down “waiting for the stars to align” in terms of people’s availability: if you wait for the perfect alignment, the project may never get done.

      If a key stakeholder is unavailable for weeks or months due to PTO or other commitments, don’t jeopardize project timelines to wait for them to be free. Find a relevant designate that can act in their stead!

      You don’t need the entire team on the field at once. Keep certain stakeholders on the bench to swap in and out as needed.

      Info-Tech Insight

      Assemble the key stakeholders for project kick-off to synchronize the application selection process and limit elapsed time. Getting all parties on the same page increases output satisfaction and eliminates rework. Save time and get input from key stakeholders at the project kick-off.

      Assemble a Cross-Functional Team for Best Results

      A blend of both worlds gets the best of both worlds from domain expertise (technical and business)

      The image contains a graph labelled: Likeliness to recommend. It is described in the text below.

      How to manage the cross-functional selection team:

      • There should be a combination of IT and businesspeople involved in the selection process, and ideally the ratio would be balanced.
      • No matter what you are looking for, you should never include more than five people in the selection process.
      • You can keep key stakeholders and other important individuals informed with what is going on, but they don’t necessarily have to be involved in the selection process.

      Leverage a Five-Person Team With Players From Both IT and the Business

      For maximum effectiveness, assign at least one resource to the project on a full-time basis

      IT Leader

      Technical IT

      Business Analyst/ Project Manager

      Business Lead

      Process Expert

      This team member is an IT director or CIO who will provide sponsorship and oversight from the IT perspective.

      This team member will focus on application security, integration, and enterprise architecture.

      This team member elicits business needs and translates them into technology requirements.

      This team member will provide sponsorship from the business needs perspective.

      This team member will contribute their domain-specific knowledge around the processes that the new application supports.

      Info-Tech Insight

      It is critical for the selection team to determine who has decision rights. Organizational culture will play the largest role in dictating which team member holds the final say for selection decisions.

      Ensure That Your Project Has the Right Mix of the Core Team and Ancillary Stakeholders

      Who is involved in selecting the new application?

      • Core selection team:
        • The core team ideally comprises just five members.
        • There will be representatives from IT and the specific business function that is most impacted by the application.
        • The team is typically anchored by a business analyst or project management professional.
        • This is the team that is ultimately accountable for ensuring that the project stays on track and that the right vendor is selected.
      • Ancillary stakeholders:
        • These stakeholders are brought into the selection project on an as-needed basis. They offer commentary on requirements and technical know-how.
        • They will be impacted by the project outcome but they do not bear ultimate accountability for selecting the application.
      The image contains an outer circle that lists Ancillary Stakeholders, and an inner selection team that lists core selection teams.

      Tweak the Team Composition Based on the Application Category in Question

      All applications are different. Some categories may require a slightly different balance of business and IT users.

      When to adjust the selection team’s business to IT ratio:

      • Increase the number of business stakeholders for customer-centric applications like customer relationship management and customer service management.
      • Keep projects staffed with more technical resources when selecting internal-facing tools like network monitoring platforms, next-generation firewalls, and endpoint protection systems.
      The image contains a graph to demonstrate how to tweak the team composition based on the application category.

      When to adjust the selection team’s business to IT ratio:

      • Increase the number of business stakeholders for customer-centric applications like customer relationship management and customer service management.
      • Keep projects staffed with more technical resources when selecting internal-facing tools like network monitoring platforms, next-generation firewalls, and endpoint protection systems.

      Balance the Selection Team With Decision Makers and Front-Line Resources

      Find the right balance!

      • Make sure to include key decision makers to increase the velocity of approvals.
      • However, it is critical to include the right number of front-line resources to ensure that end-user needs are adequately reflected in the requirements and decision criteria used for selection.

      The image contains a graph on the team composition with number of decision makers involved.

      Info-Tech Insight

      When selecting their software, organizations have an average of two to four business and IT decision makers/influencers on the core selection team.

      Optimize Meeting Cadence to Complete Selection in 30 Days

      Project Cadence:

      • Execute approximately one phase per week.
      • Conduct weekly checkpoints to move through your formal selection framework.
      • Allot two to four hours per touchpoint.

      The image contains a calendar with the five phases spread put over five weeks.

      Info-Tech Insight

      Use weekly touchpoints with the core selection team to eliminate broken telephone. Hold focus groups and workshops to take a more collaborative, timely, and consensus-driven approach to zero in on critical requirements.

      2. Reduce Time Spent on Low-Impact Activities

      ✓ Reduce time spent on internet research. Leverage hard data and experts.

      ✓ Reduce RFP size or skip RFPs entirely.

      ✓ Reduce time spent watching vendor dog and pony shows.

      Reduce Time Spent on Internet Research by Leveraging Hard Data and Experts

      REDUCE BIAS

      Taking a data-driven approach to vendor selection ensures that decisions are made in a manner that reduces human bias and exposure to misaligned incentives.

      SCORING MODELS

      Create a vendor scoring model that uses several different scored criteria (alignment to needs, alignment to architecture, cost, relationship, etc.) and weight them.

      AGGREGATE EXPERIENCES

      When you leverage services such as SoftwareReviews, you’re relying on amalgamated data from hundreds of others that have already been down this path: benefit from their experience!

      PEER-DRIVEN INSIGHTS

      Formally incorporate a review of Category Reports from SoftwareReviews into your vendor selection process to take advantage of peer-driven expert insights.

      Contact Us

      Info-Tech is just a phone call away. Our expert analysts can guide you to successful project completion at no additional cost to you.

      Bloated RFPs Are Weighing You Down

      Avoid “RFP overload” – parse back deliverables for smaller projects

      1. Many IT and procurement professionals are accustomed to deliverable-heavy application selection projects.
      2. Massive amounts of effort is spent creating onerous RFIs, RFPs, vendor demo scripts, reference guides, and Pugh matrices – with only incremental (if any) benefits.
      3. For smaller projects, focus on creating a minimum viable RFP that sketches out a brief need statement and highlights three or four critical process areas to avoid RFP fatigue.

      Draft a lightweight RFI (or minimum viable RFP) to give vendors a snapshot of your needs while managing effort

      An RFI or MV-RFP is a truncated RFP document that highlights core use cases to vendors while minimizing the amount of time the team has to spend building it.

      You may miss out on the right vendor if:

      • The RFP is too long or cumbersome for the vendor to respond.
      • Vendors believe their time is better spent relationship selling.
      • The RFP is unclear and leads them to believe they won’t be successful.
      • The vendor was forced to guess what you were looking for.

      How to write a successful RFI/MV-RFP:

      • Expend your energy relative to the complexity of the required solution or product you’re seeking.
      • A good MV-RFP is structured as follows: a brief description of your organization, business context, and key requirements. It should not exceed a half-dozen pages in length.
      • Be transparent.
      • This could potentially be a long-term relationship, so don’t try to trick suppliers.
      • Be clear in your expectations and focus on the key aspects of what you’re trying to achieve.

      Use the appropriate Info-Tech template for your needs (RFI, RFQ, or RFP). The Request for Information Template is best suited to the RASF approach.

      If Necessary, Make Sure That You Are Going About RFPs the Right Way

      RFPs only add satisfaction when done correctly

      The image contains a graph to demonstrate RFP and satisfaction.

      Info-Tech Insight

      Prescriptive yet flexible: Avoid RFP overload when selecting customer experience–centric applications, but a formal approach to selection is still beneficial.

      When will an RFP increase satisfaction?

      • Satisfaction is increased when the RFP is used in concert with a formal selection methodology. An RFP on its own does not drive significant value.
      • RFPs that focus on an application’s differentiating features lead to higher satisfaction with the selection process.
      • Using the RFP to evaluate mandatory or standard and/or mandatory features yields neutral results.

      Reduce Time Spent Watching Vendor Dog and Pony Shows

      Salesperson charisma and marketing collateral quality should not be primary selection criteria. Sadly, this is the case far too often.

      Use data to take control back from the vendor

      • Taking a data-driven approach to vendor selection ensures that decisions are made in a manner that reduces human bias and exposure to misaligned incentives.
      • When you leverage services such as SoftwareReviews, you’re relying on amalgamated data from hundreds of others that have already been down this path: benefit from their collective experience!

      Kill the “golf course effect” and eliminate stakeholder bias

      • A leading cause of selection failure is human bias. While rarely malicious, the reality is that decision makers and procurement staff can become unduly biased over time by vendor incentives. Conference passes, box seats, a strong interpersonal relationship – these are all things that may be valuable to a decision maker but have no bearing on the efficacy of an enterprise application.
      • A strong selection process mitigates human bias by using a weighted scoring model and basing decisions on hard data: cost, user satisfaction scores, and trusted third-party data from services such as SoftwareReviews.

      Conduct a Day of Rapid-Fire Investigative Interviews

      Zoom in on high-value use cases and answers to targeted questions

      Make sure the solution will work for your business

      Give each vendor 60 to 90 minutes to give a rapid-fire presentation. We suggest the following structure:

      • 20 minutes: company introduction and vision
      • 20 minutes: one high-value scenario walkthrough
      • 20-40 minutes: targeted Q&A from the business stakeholders and procurement team

      To ensure a consistent evaluation, vendors should be asked analogous questions, and a tabulation of answers should be conducted.

      How to challenge the vendors in the investigative interview

      • Change the visualization/presentation.
      • Change the underlying data.
      • Add additional data sets to the artifacts.
      • Collaboration capabilities.
      • Perform an investigation in terms of finding BI objects and identifying previous changes and examine the audit trail.

      Rapid-Fire Vendor Investigative Interview

      Invite vendors to come onsite (or join you via videoconference) to demonstrate the product and to answer questions. Use a highly targeted demo script to help identify how a vendor’s solution will fit your organization’s particular business capability needs.

      Spend Your Time Wisely and Accelerate the Process

      Join the B2B software selection r/evolution

      Awareness

      Education & Discovery

      Evaluation

      Selection

      Negotiation & Configuration

      Reduce Time

      Reduce Time

      Reduce Time

      Reduce Time

      Reduce Time

      Save time
      duplicating existing market research. Save time and maintain alignment with focus groups.

      Save time across tedious demos and understanding the marketplace.

      Save time gathering detailed historical requirements. Instead, focus on key issues.

      Use your time to validate how the solution will handle mission-critical requirements.

      Spend time negotiating with two viable alternatives to reduce price by up to 50%.

      Use a tier-based model to accelerate commodity and complex selection projects.

      Eliminate elapsed process time with focus groups and workshops.

      3. Focus on High-Impact Activities

      ✓ Narrow the field to four contenders prior to in-depth comparison.

      ✓ Identify portfolio overlap with accelerated enterprise architecture oversight.

      ✓ Focus on investigative interviews and proof of concept projects.

      Narrow the Field to a Maximum of Four Contenders

      Focus time spent on the players that we know can deliver strong value

      1. ACCELERATE SELECTION

      Save time by exclusively engaging vendors that support the organization’s differentiating requirements.

      2. DECISION CLARITY

      Prevent stakeholders from getting lost in the weeds with endless lists of vendors.

      3.CONDENSED DEMOS

      Limiting the project to four contenders allows you to stack demos/investigative interviews into the same day.

      4. LICENSING LEVERAGE

      Keep track of key differences between vendor offerings with a tight shortlist.

      Rapid & Effective Selection Decisions

      Consolidating the Vendor Shortlist Up-Front Reduces Downstream Effort

      Put the “short” back in shortlist!

      • Radically reduce effort by narrowing the field of potential vendors earlier in the selection process. Too many organizations don’t funnel their vendor shortlist until nearing the end of the selection process. The result is wasted time and effort evaluating options that are patently not a good fit.
      • Leverage external data (such as SoftwareReviews) and expert opinion to consolidate your shortlist into a smaller number of viable vendors before the investigative interview stage and eliminate time spent evaluating dozens of RFP responses.
      • Having fewer RFP responses to evaluate means you will have more time to do greater due diligence.

      Rapid Enterprise Architecture Evaluations Are High-Impact Activities

      When accelerating selection decisions, finding the right EA is a balancing act

      • Neglecting enterprise architecture as a shortcut to save time often leads to downstream integration problems and decreases application satisfaction.
      • On the other hand, overly drawn out enterprise architecture evaluations can lead to excessively focusing on technology integration versus having a clear and concise understanding of critical business needs.

      Info-Tech Insight

      Targeting an enterprise architecture evaluation as part of your software selection process that does not delay the selection while also providing sufficient insight into platform fit is critical.

      Key activities for rapid enterprise architecture evaluation include:

      1. Security analysis
      2. Portfolio overlap review + integration assessment
      3. Application standards check

      The data confirms that it is worthwhile to spend time on enterprise architecture

      • Considering software architecture fit up-front to determine if new software aligns with the existing application architecture directly links to greater satisfaction.
      • Stakeholders are most satisfied with their software value when there is a good architectural platform fit.
      • Stakeholders that ranked Architectural Platform Fit lower during the selection process were ultimately more unsatisfied with their software choice.

      The image contains a screenshot of data to demonstrate that it is worthwhile to spend time on enterprise architecture.

      Identify Portfolio Overlap With an Accelerated Enterprise Architecture Assessment

      Develop a clear view of any overlap within your target portfolio subset and clear rationalization/consolidation options

      • Application sprawl is a critical pain point in many organizations. It leads to wasted time, money, and effort as IT (and the business) maintain myriad applications that all serve the same functional purpose.
      • Opportunities are missed to consolidate and streamline associated business process management, training, and end-user adoption activities.
      • Identify which applications in your existing architecture serve a duplicate purpose: these applications are the ones you will want to target for consolidation.
      • As you select a new application, identify where it can be used to serve the goal for application rationalization (i.e. can we replace/retire existing applications in our portfolio by standardizing the new one?).

      Keep the scope manageable!

      • Highlight the major functional processes that are closely related to the application you’re selecting and identify which applications support each.
      • The template below represents a top-level view of a set of customer experience management (CXM) applications. Identify linkages between sets of applications and if they’re uni- or bi-directional.
      The image contains a screenshot of images that demonstrate portfolio overlap with an accelerated enterprise architecture assessment.

      Rapidly Evaluate the Security & Risk Profile for a Right-Sized Enterprise Architecture Evaluation

      There are four considerations for determining the security and risk profile for the new application

      1. Financial Risk
      • Consider the financial impact the new application has on the organization.
        • How significant is the investment in technology?
      • If this application fails to meet its business goals and deliver strong return on investment, will there be a significant amount of financial resources to mitigate the problem?
    • Data Sensitivity Risk
      • Understand the type of data that will be handled/stored by the application.
        • For example, a CRM will house customer personally identifiable information (PII) and an ECM will store confidential business documentation.
      • Determine the consequences of a potential breach (i.e. legal and financial).
    • Application Vulnerability Risk
      • Consider whether the application category has a historically strong security track record.
        • For example, enterprise cloud storage solutions may have a different level of vulnerability than an HRIS platform.
    • Infrastructure Risk
      • Determine whether the new application requires changes to infrastructure or additional security investments to safeguard expanded infrastructure.
      • Consider the ways in which the changes to infrastructure increase the vectors for security breaches.

      Spend More Time Validating Key Issues With Deep Technical Assessments

      The image contains a screenshot of an image of an iceberg. The top part of the iceberg is above water and labelled 40%. The rest of the iceberg is below water and is labelled 60%.

      Conversations With the Vendor

      • Initial conversations with the vendor build alignment on overall application capabilities, scope of work, and pricing.

      Pilot Projects and Trial Environments

      • Conduct a proof of concept project to ensure that the application satisfies your non-functional requirements.
      • Technical assessments not only demonstrate whether an application is compatible with your existing systems but also give your technical resources the confidence that the implementation process will be as smooth as possible.
      • Marketing collateral glosses over actual capabilities and differentiation. Use unbiased third-party data and detailed system training material.

      4. Use Rapid & Essential Assessment Tools

      ✓ Focus on key use cases, not lists of features.

      ✓ You only need three essential tools:

      1. Info-Tech’s Vendor Evaluation Workbook
      2. The Software Selection Workbook
      3. A Business Stakeholder Manual

      Focus on Key Use Cases, Not an Endless Laundry List of Table Stakes Features

      Focus on Critical Requirements

      Failure to differentiate must-have and nice-to-have use cases leads to applications full of non-critical features.

      Go Beyond the Table Stakes

      Accelerate the process by skipping common requirements that we know that every vendor will support.

      Streamline the Quantity of Use Cases

      Working with a tighter list of core use cases increases time spent evaluating the most impactful functionality.

      Over-Customization Kills Projects

      Eliminating dubious “sacred cow” requirements reduces costly and painful platform customization.

      Only Make Use of Essential Selection Artifacts

      Vendor selection projects often demand extensive and unnecessary documentation

      The Software Selection Workbook

      Work through the straightforward templates that tie to each phase of the Rapid Application Selection Framework, from assessing the business impact to requirements gathering.

      The image contains a screenshot of The Software Selection Workbook.

      The Vendor Evaluation Workbook

      Consolidate the vendor evaluation process into a single document. Easily compare vendors as you narrow the field to finalists.

      The image contains a screenshot of The Vendor Evaluation Workbook.

      The Guide to Software Selection: A Business Stakeholder Manual

      Quickly explain the Rapid Application Selection Framework to your team while also highlighting its benefits to stakeholders.

      The image contains a screenshot of The Guide to Software Selection: A Business Stakeholder Manual.

      Software Selection Engagement

      Five advisory calls over a five-week period to accelerate your selection process

      • Expert analyst guidance over five weeks on average to select and negotiate software.
      • Save money, align stakeholders, speed up the process, and make better decisions.
      • Use a repeatable, formal methodology to improve your application selection process.
      • Better, faster results, guaranteed, included in membership.
      The image contains a screenshot of the calendar over 30 days that outlines the five calls.

      Click here to book your selection engagement

      Software Selection Workshop

      With 40 hours of advisory assistance delivered online, select better software, faster.

      • 40 hours of expert analyst guidance.
      • Project and stakeholder management assistance.
      • Save money, align stakeholders, speed up the process, and make better decisions.
      • Better, faster results, guaranteed; $20K standard engagement fee.
      The image contains a screenshot of the calendar over 30 days that outlines the five calls.

      CLICK HERE TO BOOK YOUR WORKSHOP ENGAGEMENT

      5. Select Two Viable Options & Engage Both in Negotiation

      ✓ Save more during negotiation by selecting two viable alternatives.

      ✓ Surface a consolidated list of demands prior to entering negotiation.

      ✓ Communicate your success with the organization.

      Save More During Negotiation by Selecting Two Viable Alternatives

      VENDOR 1

      Build in a realistic plan B that allows you to apply leverage to the incumbent or primary vendor of choice.

      VENDOR 2

      If the top contender is aware that they do not have competition, they will be less inclined to make concessions.

      Maintain momentum with two options

      • Should you realize that the primary contender is no longer a viable option (i.e. security concerns), keeping a second vendor in play enables you to quickly pivot without slowing down the selection project.

      Secure best pricing by playing vendors off each other

      • Vendors are more likely to give concessions on the base price once they become aware that a direct competitor has entered the evaluation.

      Truly commit to a thorough analysis of alternatives

      • By evaluating competitive alternatives, you’ll get a more comprehensive view on market standards for a solution and be able to employ a range of negotiation tactics.

      Focus on 5-10 Specific Contract Change Requests

      Accelerate negotiation by picking your battles

      ANALYZE

      DOCUMENT

      CONSOLIDATE

      PRESENT

      • Parse the contract, order form, and terms & conditions for concerning language.
      • Leverage expertise from internal subject matter experts in addition to relevant legal council.
      • Document all concerns and challenges with the language in the vendor contract in a single spreadsheet.
      • Make vendors more receptive to your cause by going one step beyond writing what the change should be. Provide the reasoning behind the change and even the relevant context.
      • Identify the change requests that are most important for the success of the selection project.
      • Compile a list of the most critical change requests.
      • Consider including nice-to-have requests that you can leverage as strategic concessions.
      • Present the consolidated list of critical change requests to the vendor rather than sharing the entire range of potential changes to the contract.
      • Make sure to include context and background for each request.
      • Eliminate potential delays by proactively establishing a timeline for the vendor’s response.

      Share Stories of Cost Savings With the Organization

      Secure IT’s seat at the table

      Hard cost savings speak louder than words. Executive leadership will see IT as the go-to team for driving business value quickly, yet responsibly.

      Build hype around the new software

      Generate enthusiasm by highlighting the improved user experience provided by the new software that was has just been selected.

      Drive end-user adoption

      Position the cost savings as an opportunity to invest in onboarding. An application is only as valuable as your employees’ ability to effectively use it.

      Keep the process rolling

      Use the momentum from the project and its successful negotiation to roll out the accelerated selection approach to more departments across the organization.

      Overall: The Magic Number Saves You Time and Money

      Software selection takes forever. The process of choosing even the smallest apps can drag on for years: sometimes in perpetuity.

      Organizations keep too many players on the field, leading to scheduling slowdowns and scope creep.

      Keeping the size of the core selection team down, while liaising with more stakeholders and subject matter experts (SMEs), leads to improved results.

      Maximize project effectiveness with a five-person team. Project satisfaction and effectiveness are stagnant or decrease once the team grows beyond five people.

      Cumbersome or ad hoc selection processes lead to business-driven software selection.

      Increase stakeholder satisfaction by using a consistent selection framework that captures their needs while not being a burden.

      Empower both IT and end users with a standardized selection process to consistently achieve high satisfaction coming out of software selection projects.

      The image contains a graph that is titled: A compact selection team can save you weeks. The graph demonstrates time saved with a five person team in comparison to larger teams.

      Key Takeaways for Improving Your Selection Process

      1. ALIGN & ELIMINATE ELAPSED TIME

      • Ensure a formal selection process is in place and reduce time by timeboxing the project to 30 days.
      • Align the calendars of the five-person core selection team to maximize efficiency.

      2. REDUCE TIME SPENT ON LOW-IMPACT ACTIVITIES

      • Go beyond the table stakes and accelerate the process by skipping common requirements that we know that every vendor will support.
      • Only make use of essential selection artifacts.

      3. FOCUS ON HIGH- IMPACT ACTIVITIES

      • Skip the vendor dog and pony shows with investigative interviews.
      • Minimize time spent on novel-sized RFPs; instead highlight three or four critical process areas.

      4. USE RAPID & ESSENTIAL ASSESSMENT TOOLS

      • Consolidating the vendor shortlist up-front reduces downstream effort.
      • Application sprawl is a critical pain point in many organizations that leads to wasted time and money.

      5. ENGAGE TWO VIABLE VENDORS IN NEGOTIATION

      • Build in a realistic plan B that allows you to apply leverage to the incumbent or primary vendor of choice.
      • Pick your battles and focus on 5-10 specific contract change requests.

      Appendix

      This study is based on a survey of 43,000 real-world IT practitioners.

      • SoftwareReviews (a sister company of Info-Tech Research Group) collects and aggregates feedback on a wide variety of enterprise technologies.
      • The practitioners are actual end users of hundreds of different enterprise application categories.
      • The following slides highlight the supplementary data points from the comprehensive survey.

      Methodology

      A comprehensive study based on the responses of thousands of real-world practitioners.

      Qualitative & Secondary

      Using comprehensive statistical techniques, we surveyed what our members identified as key drivers of success in selecting enterprise software. Our goal was to determine how organizations can accelerate selection processes and improve outcomes by identifying where people should spend their time for the best results.

      Large-n Survey

      To determine the “Magic Numbers,” we used a large-n survey: 40,000 respondents answered questions about their applications, selection processes, organizational firmographics, and personal characteristics. We used this data to determine what drives satisfaction not only with the application but with the selection process itself.

      Quantitative Drill-Down

      We used the survey to narrow the list of game-changing practices. We then conducted additional quantitative research to understand why our respondents may have selected the responses they did.

      Create a Service Management Roadmap

      • Buy Link or Shortcode: {j2store}394|cart{/j2store}
      • member rating overall impact: 8.9/10 Overall Impact
      • member rating average dollars saved: $71,003 Average $ Saved
      • member rating average days saved: 24 Average Days Saved
      • Parent Category Name: Service Management
      • Parent Category Link: /service-management
      • Inconsistent adoption of holistic practices has led to a chaotic service delivery model that results in poor customer satisfaction.
      • There is little structure, formalization, or standardization in the way IT services are designed and managed, leading to diminishing service quality and low business satisfaction.

      Our Advice

      Critical Insight

      • Having effective service management practices in place will allow you to pursue activities, such as innovation, and drive the business forward.
      • Addressing foundational elements like business alignment and management practices will enable you to build effective core practices that deliver business value.
      • Providing consistent leadership support and engagement is essential to allow practitioners to focus on delivering expected outcomes.

      Impact and Result

      • Understand the foundational and core elements that allow you to build a successful service management practice focused on outcomes.
      • Use Info-Tech’s advice and tools to perform an assessment of your organization’s current state, identify the gaps, and create a roadmap for success.
      • Increase business and customer satisfaction by delivering services focused on creating business value.

      Create a Service Management Roadmap Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why many service management maturity projects fail to address foundational and core elements, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Launch the project

      Kick-off the project and complete the project charter.

      • Create a Service Management Roadmap – Phase 1: Launch Project
      • Service Management Roadmap Project Charter

      2. Assess the current state

      Determine the current state for service management practices.

      • Create a Service Management Roadmap – Phase 2: Assess the Current State
      • Service Management Maturity Assessment Tool
      • Organizational Change Management Capability Assessment Tool
      • Service Management Roadmap Presentation Template

      3. Build the roadmap

      Build your roadmap with identified initiatives.

      • Create a Service Management Roadmap – Phase 3: Identify the Target State

      4. Build the communication slide

      Create the communication slide that demonstrates how things will change, both short and long term.

      • Create a Service Management Roadmap – Phase 4: Build the Roadmap
      [infographic]

      Workshop: Create a Service Management Roadmap

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Understand Service Management

      The Purpose

      Understand service management.

      Key Benefits Achieved

      Gain a common understanding of service management, the forces that impact your roadmap, and the Info-Tech Service Management Maturity Model.

      Activities

      1.1 Understand service management.

      1.2 Build a compelling vision and mission.

      Outputs

      Constraints and enablers chart

      Service management vision, mission, and values

      2 Assess the Current State of Service Management

      The Purpose

      Assess the organization’s current service management capabilities.

      Key Benefits Achieved

      Understand attitudes, behaviors, and culture.

      Understand governance and process ownership needs.

      Understand strengths, weaknesses, opportunities, and threats.

      Defined desired state.

      Activities

      2.1 Assess cultural ABCs.

      2.2 Assess governance needs.

      2.3 Perform SWOT analysis.

      2.4 Define desired state.

      Outputs

      Cultural improvements action items

      Governance action items

      SWOT analysis action items

      Defined desired state

      3 Continue Current-State Assessment

      The Purpose

      Assess the organization’s current service management capabilities.

      Key Benefits Achieved

      Understand the current maturity of service management processes.

      Understand organizational change management capabilities.

      Activities

      3.1 Perform service management process maturity assessment.

      3.2 Complete OCM capability assessment.

      3.3 Identify roadmap themes.

      Outputs

      Service management process maturity activities

      OCM action items

      Roadmap themes

      4 Build Roadmap and Communication Tool

      The Purpose

      Use outputs from previous steps to build your roadmap and communication one-pagers.

      Key Benefits Achieved

      Easy-to-understand roadmap one-pager

      Communication one-pager

      Activities

      4.1 Build roadmap one-pager.

      4.2 Build communication one-pager.

      Outputs

      Service management roadmap

      Service management roadmap – Brought to Life communication slide

      Further reading

      Create a Service Management Roadmap

      Implement service management in an order that makes sense.

      ANALYST PERSPECTIVE

      "More than 80% of the larger enterprises we’ve worked with start out wanting to develop advanced service management practices without having the cultural and organizational basics or foundational practices fully in place. Although you wouldn’t think this would be the case in large enterprises, again and again IT leaders are underestimating the importance of cultural and foundational aspects such as governance, management practices, and understanding business value. You must have these fundamentals right before moving on."

      Tony Denford,

      Research Director – CIO

      Info-Tech Research Group

      Our understanding of the problem

      This Research Is Designed For:

      • CIO
      • Senior IT Management

      This Research Will Help You:

      • Create or maintain service management (SM) practices to ensure user-facing services are delivered seamlessly to business users with minimum interruption.
      • Increase the level of reliability and availability of the services provided to the business and improve the relationship and communication between IT and the business.

      This Research Will Also Assist

      • Service Management Process Owners

      This Research Will Help Them:

      • Formalize, standardize, and improve the maturity of service management practices.
      • Identify new service management initiatives to move IT to the next level of service management maturity.

      Executive summary

      Situation

      • Inconsistent adoption of holistic practices has led to a chaotic service delivery model that results in poor customer satisfaction.
      • There is little structure, formalization, or standardization in the way IT services are designed and managed, leading to diminishing service quality and low business satisfaction.

      Complication

      • IT organizations want to be seen as strategic partners, but they fail to address the cultural and organizational constraints.
      • Without alignment with the business goals, services often fail to provide the expected value.
      • Traditional service management approaches are not adaptable for new ways of working.

      Resolution

      • Follow Info-Tech’s methodology to create a service management roadmap that will help guide the optimization of your IT services and improve IT’s value to the business.
      • The blueprint will help you right-size your roadmap to best suit your specific needs and goals and will provide structure, ownership, and direction for service management.
      • This blueprint allows you to accurately identify the current state of service management at your organization. Customize the roadmap and create a plan to achieve your target service management state.

      Info-Tech Insight

      Having effective service management practices in place will allow you to pursue activities such as innovation and drive the business forward. Addressing foundational elements like business alignment and management practices will enable you to build effective core practices that deliver business value. Consistent leadership support and engagement is essential to allow practitioners to focus on delivering expected outcomes.

      Poor service management manifests in many different pains across the organization

      Immaturity in service management will not result in one pain – rather, it will create a chaotic environment for the entire organization, crippling IT’s ability to deliver and perform.

      Low Service Management Maturity

      These are some of the pains that can be attributed to poor service management practices.

      • Frequent service-impacting incidents
      • Low satisfaction with the service desk
      • High % of failed deployments
      • Frequent change-related incidents
      • Frequent recurring incidents
      • Inability to find root cause
      • No communication with the business
      • Frequent capacity-related incidents

      And there are many more…

      Mature service management practices are a necessity, not a nice-to-have

      Immature service management practices are one of the biggest hurdles preventing IT from reaching its true potential.

      In 2004, PwC published a report titled “IT Moves from Cost Center to Business Contributor.” However, the 2014-2015 CSC Global CIO Survey showed that a high percentage of IT is still considered a cost center.

      And low maturity of service management practices is inhibiting activities such as agility, DevOps, digitalization, and innovation.

      A pie chart is shown that is titled: Where does IT sit? The chart has 3 sections. One section represents IT and the business have a collaborative partnership 28%. The next section represents at 33% where IT has a formal client/service provider relationship with the business. The last section has 39% where IT is considered as a cost center.
      Source: CSC Global CIO Survey: 2014-2015 “CIOs Emerge as Disruptive Innovators”

      39%: Resources are primarily focused on managing existing IT workloads and keeping the lights on.

      31%: Too much time and too many resources are used to handle urgent incidents and problems.

      There are many misconceptions about what service management is

      Misconception #1: “Service management is a process”

      Effective service management is a journey that encompasses a series of initiatives that improves the value of services delivered.

      Misconception #2: “Service Management = Service Desk”

      Service desk is the foundation, since it is the main end-user touch point, but service management is a set of people and processes required to deliver business-facing services.

      Misconception #3: “Service management is about the ITSM tool”

      The tool is part of the overall service management program, but the people and processes must be in place before implementing.

      Misconception #4: “Service management development is one big initiative”

      Service management development is a series of initiatives that takes into account an organization’s current state, maturity, capacities, and objectives.

      Misconception #5: “Service management processes can be deployed in any order, assuming good planning and design”

      A successful service management program takes into account the dependencies of processes.

      Misconception #6: “Service management is resolving incidents and deploying changes”

      Service management is about delivering high-value and high-quality services.

      Misconception #7: “Service management is not the key determinant of success”

      As an organization progresses on the service management journey, its ability to deliver high-value and high-quality services increases.

      Misconception #8: “Resolving Incidents = Success”

      Preventing incidents is the name of the game.

      Misconception #9: “Service Management = Good Firefighter”

      Service management is about understanding what’s going on with user-facing services and proactively improving service quality.

      Misconception #10: “Service management is about IT and technical services (e.g. servers, network, database)”

      Service management is about business/user-facing services and the value the services provide to the business.

      Service management projects often don’t succeed because they are focused on process rather than outcomes

      Service management projects tend to focus on implementing process without ensuring foundational elements of culture and management practices are strong enough to support the change.

      1. Aligning your service management goals with your organizational objectives leads to better understanding of the expected outcomes.
      2. Understand your customers and what they value, and design your practices to deliver this value.

      3. IT does not know what order is best when implementing new practices or process improvements.
      4. Don't run before you can walk. Fundamental practices must reach the maturity threshold before developing advanced practices. Implement continuous improvement on your existing processes so they continue to support new practices.

      5. IT does not follow best practices when implementing a practice.
      6. Our best-practice research is based on extensive experience working with clients through advisory calls and workshops.

      Info-Tech can help you create a customized, low-effort, and high-value service management roadmap that will shore up any gaps, prove IT’s value, and achieve business satisfaction.

      Info-Tech’s methodology will help you customize your roadmap so the journey is right for you

      With Info-Tech, you will find out where you are, where you want to go, and how you will get there.

      With our methodology, you can expect the following:

      • Eliminate or reduce rework due to poor execution.
      • Identify dependencies/prerequisites and ensure practices are deployed in the correct order, at the correct time, and by the right people.
      • Engage all necessary resources to design and implement required processes.
      • Assess current maturity and capabilities and design the roadmap with these factors in mind.

      Doing it right the first time around

      You will see these benefits at the end

        ✓ Increase the quality of services IT provides to the business.

        ✓ Increase business satisfaction through higher alignment of IT services.

        ✓ Lower cost to design, implement, and manage services.

        ✓ Better resource utilization, including staff, tools, and budget.

      Focus on a strong foundation to build higher value service management practices

      Info-Tech Insight

      Focus on behaviors and expected outcomes before processes.

      Foundational elements

      • Operating model facilitates service management goals
      • Culture of service delivery
      • Governance discipline to evaluate, direct, and monitor
      • Management discipline to deliver

      Stabilize

      • Deliver stable, reliable IT services to the business
      • Respond to user requests quickly and efficiently
      • Resolve user issues in a timely manner
      • Deploy changes smoothly and successfully

      Proactive

      • Avoid/prevent service disruptions
      • Improve quality of service (performance, availability, reliability)

      Service Provider

      • Understand business needs
      • Ensure services are available
      • Measure service performance, based on business-oriented metrics

      Strategic Partner

      • Fully aligned with business
      • Drive innovation
      • Drive measurable value

      Info-Tech Insight

      Continued leadership support of the foundational elements will allow delivery teams to provide value to the business. Set the expectation of the desired maturity level and allow teams to innovate.

      Follow our model and get to your target state

      A model is depicted that shows the various target states. There are 6 levels showing in the example, and the example is made to look like a tree with a character watering it. In the roots, the level is labelled foundational. The trunk is labelled the core. The lowest hanging branches of the tree is the stabilize section. Above it is the proactive section. Nearing the top of the tree is the service provider. The canopy of the tree are labelled strategic partner.

      Before moving to advanced service management practices, you must ensure that the foundational and core elements are robust enough to support them. Leadership must nurture these practices to ensure they are sustainable and can support higher value, more mature practices.

      Each step along the way, Info-Tech has the tools to help you

      Phase 1: Launch the Project

      Assemble a team with the right talent and vision to increase the chances of project success.

      Phase 2: Assess Current State

      Understand where you are currently on the service management journey using the maturity assessment tool.

      Phase 3: Build Roadmap

      Based on the assessments, build a roadmap to address areas for improvement.

      Phase 4: Build Communication slide

      Based on the roadmap, define the current state, short- and long-term visions for each major improvement area.

      Info-Tech Deliverables:

      • Project Charter
      • Assessment Tools
      • Roadmap Template
      • Communication Template

      CIO call to action

      Improving the maturity of the organization’s service management practice is a big commitment, and the project can only succeed with active support from senior leadership.

      Ideally, the CIO should be the project sponsor, even the project leader. At a minimum, the CIO needs to perform the following activities:

      1. Walk the talk – demonstrate personal commitment to the project and communicate the benefits of the service management journey to IT and the steering committee.
      2. Improving or adopting any new practice is difficult, especially for a project of this size. Thus, the CIO needs to show visible support for this project through internal communication and dedicated resources to help complete this project.

      3. Select a senior, capable, and results-driven project leader.
      4. Most likely, the implementation of this project will be lengthy and technical in some nature. Therefore, the project leader must have a good understanding of the current IT structure, senior standing within the organization, and the relationship and power in place to propel people into action.

      5. Help to define the target future state of IT’s service management.
      6. Determine a realistic target state for the organization based on current capability and resource/budget restraints.

      7. Conduct periodic follow-up meetings to keep track of progress.
      8. Reinforce or re-emphasize the importance of this project to the organization through various communication channels if needed.

      Stabilizing your environment is a must before establishing any more-mature processes

      CASE STUDY

      Industry: Manufacturing

      Source: Engagement

      Challenge

      • The business landscape was rapidly changing for this manufacturer and they wanted to leverage potential cost savings from cloud-first initiatives and consolidate multiple, self-run service delivery teams that were geographically dispersed.

      Solution

      Original Plan

      • Consolidate multiple service delivery teams worldwide and implement service portfolio management.

      Revised Plan with Service Management Roadmap:

      • Markets around the world had very different needs and there was little understanding of what customers value.
      • There was also no understanding of what services were currently being offered within each geography.

      Results

      • Plan was adjusted to understand customer value and services offered.
      • Services were then stabilized and standardized before consolidation.
      • Team also focused on problem maturity and drove a continuous improvement culture and increasing transparency.

      MORAL OF THE STORY:

      Understanding the value of each service allowed the organization to focus effort on high-return activities rather than continuous fire fighting.

      Understand the processes involved in the proactive phase

      CASE STUDY

      Industry: Manufacturing

      Source: Engagement

      Challenge

      • Services were fairly stable, but there were significant recurring issues for certain services.
      • The business was not satisfied with the service quality for certain services, due to periodic availability and reliability issues.
      • Customer feedback for the service desk was generally good.

      Solution

      Original Plan

      • Review all service desk and incident management processes to ensure that service issues were handled in an effective manner.

      Revised Plan with Service Management Roadmap:

      • Design and deploy a rigorous problem management process to determine the root cause of recurring issues.
      • Monitor key services for events that may lead to a service outage.

      Results

      • Root cause of recurring issues was determined and fixes were deployed to resolve the underlying cause of the issues.
      • Service quality improved dramatically, resulting in high customer satisfaction.

      MORAL OF THE STORY:

      Make sure that you understand which processes need to be reviewed in order to determine the cause for service instability. Focusing on the proactive processes was the right answer for this company.

      Have the right culture and structure in place before you become a service provider

      CASE STUDY

      Industry: Healthcare

      Source:Journal of American Medical Informatics Association

      Challenge

      • The IT organization wanted to build a service catalog to demonstrate the value of IT to the business.
      • IT was organized in technology silos and focused on applications, not business services.
      • IT services were not aligned with business activities.
      • Relationships with the business were not well established.

      Solution

      Original Plan

      • Create and publish a service catalog.

      Revised Plan: with Service Management Roadmap:

      • Establish relationships with key stakeholders in the business units.
      • Understand how business activities interface with IT services.
      • Lay the groundwork for the service catalog by defining services from the business perspective.

      Results

      • Strong relationships with the business units.
      • Deep understanding of how business activities map to IT services.
      • Service definitions that reflect how the business uses IT services.

      MORAL OF THE STORY:

      Before you build and publish a service catalog, make sure that you understand how the business is using the IT services that you provide.

      Calculate the benefits of using Info-Tech’s methodology

      To measure the value of developing your roadmap using the Info-Tech tools and methodology, you must calculate the effort saved by not having to develop the methods.

      A. How much time will it take to develop an industry-best roadmap using Info-Tech methodology and tools?

      Using Info-Tech’s tools and methodology you can accurately estimate the effort to develop a roadmap using industry-leading research into best practice.

      B. What would be the effort to develop the insight, assess your team, and develop the roadmap?

      This metric represents the time your team would take to be able to effectively assess themselves and develop a roadmap that will lead to service management excellence.

      C. Cost & time saving through Info-Tech’s methodology

      Measured Value

      Step 1: Assess current state

      Cost to assess current state:

      • 5 Directors + 10 Managers x 10 hours at $X an hour = $A

      Step 2: Build the roadmap

      Cost to create service management roadmap:

      • 5 Directors + 10 Managers x 8 hours at $X an hour = $B

      Step 3: Develop the communication slide

      Cost to create roadmaps for phases:

      • 5 Directors + 10 Managers x 6 hours at $X an hour = $C

      Potential financial savings from using Info-Tech resources:

      Estimated cost to do “B” – (Step 1 ($A) + Step 2 ($B) + Step 3 ($C)) = $Total Saving

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful."

      Guided Implementation

      "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keeps us on track."

      Workshop

      "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place."

      Consulting

      "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks are used throughout all four options.

      Create a Service Management Roadmap – project overview


      Launch the project

      Assess the current state

      Build the roadmap

      Build communication slide

      Best-Practice Toolkit

      1.1 Create a powerful, succinct mission statement

      1.2 Assemble a project team with representatives from all major IT teams

      1.3 Determine project stakeholders and create a communication plan

      1.4 Establish metrics to track the success of the project

      2.1 Assess impacting forces

      2.2 Build service management vision, mission, and values

      2.3 Assess attitudes, behaviors, and culture

      2.4 Assess governance

      2.5 Perform SWOT analysis

      2.6 Identify desired state

      2.7 Assess SM maturity

      2.8 Assess OCM capabilities

      3.1 Document overall themes

      3.2 List individual initiatives

      4.1 Document current state

      4.2 List future vision

      Guided Implementations

      • Kick-off the project
      • Build the project team
      • Complete the charter
      • Understand current state
      • Determine target state
      • Build the roadmap based on current and target state
      • Build short- and long-term visions and initiative list

      Onsite Workshop

      Module 1: Launch the project

      Module 2: Assess current service management maturity

      Module 3: Complete the roadmap

      Module 4: Complete the communication slide

      Workshop overview

      Contact your account representative or email Workshops@InfoTech.com for more information

      Workshop Day 1

      Workshop Day 2

      Workshop Day 3

      Workshop Day 4

      Activities

      Understand Service Management

      1.1 Understand the concepts and benefits of service management.

      1.2 Understand the changing impacting forces that affect your ability to deliver services.

      1.3 Build a compelling vision and mission for your service management program.

      Assess the Current State of Your Service Management Practice

      2.1 Understand attitudes, behaviors, and culture.

      2.2 Assess governance and process ownership needs.

      2.3 Perform SWOT analysis.

      2.4 Define the desired state.

      Complete Current-State Assessment

      3.1 Conduct service management process maturity assessment.

      3.2 Identify organizational change management capabilities.

      3.3 Identify themes for roadmap.

      Build Roadmap and Communication Tool

      4.1 Build roadmap one-pager.

      4.2 Build roadmap communication one-pager.

      Deliverables

      1. Constraints and enablers chart
      2. Service management vision, mission, and values
      1. Action items for cultural improvements
      2. Action items for governance
      3. Identified improvements from SWOT
      4. Defined desired state
      1. Service Management Process Maturity Assessment
      2. Organizational Change Management Assessment
      1. Service management roadmap
      2. Roadmap Communication Tool in the Service Management Roadmap Presentation Template

      PHASE 1

      Launch the Project

      Launch the project

      This step will walk you through the following activities:

      • Create a powerful, succinct mission statement based on your organization’s goals and objectives.
      • Assemble a project team with representatives from all major IT teams.
      • Determine project stakeholders and create a plan to convey the benefits of this project.
      • Establish metrics to track the success of the project.

      Step Insights

      • The project leader should have a strong relationship with IT and business leaders to maximize the benefit of each initiative in the service management journey.
      • The service management roadmap initiative will touch almost every part of the organization; therefore, it is important to have representation from all impacted stakeholders.
      • The communication slide needs to include the organizational change impact of the roadmap initiatives.

      Phase 1 outline

      Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

      Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 1: Launch the Project

      Step 1.1 – Kick-off the Project

      Start with an analyst kick-off call:

      • Identify current organization pain points relating to poor service management practices
      • Determine high-level objectives
      • Create a mission statement

      Then complete these activities…

      • Identify potential team members who could actively contribute to the project
      • Identify stakeholders who have a vested interest in the completion of this project

      With these tools & templates:

      • Service Management Roadmap Project Charter

      Step 1.2 – Complete the Charter

      Review findings with analyst:

      • Create the project team; ensure all major IT teams are represented
      • Review stakeholder list and identify communication messages

      Then complete these activities…

      • Establish metrics to complete project planning
      • Complete the project charter

      With these tools & templates:

      • Service Management Roadmap Project Charter

      Use Info-Tech’s project charter to begin your initiative

      1.1 Service Management Roadmap Project Charter

      The Service Management Roadmap Project Charter is used to govern the initiative throughout the project. It provides the foundation for project communication and monitoring.

      The template has been pre-populated with sample information appropriate for this project. Please review this sample text and change, add, or delete information as required.

      The charter includes the following sections:

      • Mission Statement
      • Goals & Objectives
      • Project Team
      • Project Stakeholders
      • Current State (from phases 2 & 3)
      • Target State (from phases 2 & 3)
      • Target State
      • Metrics
      • Sponsorship Signature
      A screenshot of Info-Tech's Service Management Roadmap Project Charter is shown.

      Use Info-Tech’s ready-to-use deliverable to customize your mission statement

      Adapt and personalize Info-Tech’s Service Management Roadmap Mission Statement and Goals & Objectives below to suit your organization’s needs.

      Goals & Objectives

      • Create a plan for implementing service management initiatives that align with the overall goals/objectives for service management.
      • Identify service management initiatives that must be implemented/improved in the short term before deploying more advanced initiatives.
      • Determine the target state for each initiative based on current maturity and level of investment available.
      • Identify service management initiatives and understand dependencies, prerequisites, and level of effort required to implement.
      • Determine the sequence in which initiatives should be deployed.
      • Create a detailed rollout plan that specifies initiatives, time frames, and owners.
      • Engage the right teams and obtain their commitment throughout both the planning and assessment of roadmap initiatives.
      • both the planning and assessment of roadmap initiatives. Obtain support for the completed roadmap from executive stakeholders.

      Example Mission Statement

      To help [Organization Name] develop a set of service management practices that will better address the overarching goals of the IT department.

      To create a roadmap that sequences initiatives in a way that incorporates best practices and takes into consideration dependencies and prerequisites between service management practices.

      To garner support from the right people and obtain executive buy-in for the roadmap.

      Create a well-balanced project team

      The project leader should be a member of your IT department’s senior executive team with goals and objectives that will be impacted by service management implementation. The project leader should possess the following characteristics:

      Leader

      • Influence and impact
      • Comprehensive knowledge of IT and the organization
      • Relationship with senior IT management
      • Ability to get things done

      Team Members

      Identify

      The project team members are the IT managers and directors whose day-to-day lives will be impacted by the service management roadmap and its implementation. The service management initiative will touch almost every IT staff member in the organization; therefore, it is important to have representatives from every single group, including those that are not mentioned. Some examples of individuals you should consider for your team:

      • Service Delivery Managers
      • Director/Manager of Applications
      • Director/Manager of Infrastructure
      • Director/Manager of Service Desk
      • Business Relationship Managers
      • Project Management Office

      Engage & Communicate

      You want to engage your project participants in the planning process as much as possible. They should be involved in the current-state assessment, the establishment of goals and objectives, and the development of your target state.

      To sell this project, identify and articulate how this project and/or process will improve the quality of their job. For example, a formal incident management process will benefit people working at the service desk or on the applications or infrastructure teams. Helping them understand the gains will help to secure their support throughout the long implementation process by giving them a sense of ownership.

      The project stakeholders should also be project team members

      When managing stakeholders, it is important to help them understand their stake in the project as well as their own personal gain that will come out of this project.

      For many of the stakeholders, they also play a critical role in the development of this project.

      Role & Benefits

      • CIO
      • The CIO should be actively involved in the planning stage to help determine current and target stage.

        The CIO also needs to promote and sell the project to the IT team so they can understand that higher maturity of service management practices will allow IT to be seen as a partner to the business, giving IT a seat at the table during decision making.

      • Service Delivery Managers/Process Owners
      • Service Delivery Managers are directly responsible for the quality and value of services provided to the business owners. Thus, the Service Delivery Managers have a very high stake in the project and should be considered for the role of project leader.

        Service Delivery Managers need to work closely with the process owners of each service management process to ensure clear objectives are established and there is a common understanding of what needs to be achieved.

      • IT Steering Committee
      • The Committee should be informed and periodically updated about the progress of the project.

      • Manager/Director – Service Desk
      • The Manager of the Service Desk should participate closely in the development of fundamental service management processes, such as service desk, incident management, and problem management.

        Having a more established process in place will create structure, governance, and reduce service desk staff headaches so they can handle requests or incidents more efficiently.

      • Manager/Director –Applications & Infrastructure
      • The Manager of Applications and Infrastructure should be heavily relied on for their knowledge of how technology ties into the organization. They should be consulted regularly for each of the processes.

        This project will also benefit them directly, such as improving the process to deploy a fix into the environment or manage the capacity of the infrastructure.

      • Business Relationship Manager
      • As the IT organization moves up the maturity ladder, the Business Relationship Manager will play a fundamental role in the more advanced processes, such as business relationship management, demand management, and portfolio management.

        This project will be an great opportunity for the Business Relationship Manager to demonstrate their value and their knowledge of how to align IT objectives with business vision.

      Ensure you get the entire IT organization on board for the project with a well-practiced change message

      Getting the IT team on board will greatly maximize the project’s chance of success.

      One of the top challenges for organizations embarking on a service management journey is to manage the magnitude of the project. To ensure the message is not lost, communicate this roadmap in two steps.

      1. Communicate the roadmap initiative

      The most important message to send to the IT organization is that this project will benefit them directly. Articulate the pains that IT is currently experiencing and explain that through more mature service management, these pains can be greatly reduced and IT can start to earn a place at the table with the business.

      2. Communicate the implementation of each process separately

      The communication of process implementation should be done separately and at the beginning of each implementation. This is to ensure that IT staff do not feel overwhelmed or overloaded. It also helps to keep the project more manageable for the project team.

      Continuously monitor feedback and address concerns throughout the entire process

      • Host lunch and learns to provide updates on the service management initiative to the entire IT team.
      • Understand if there are any major roadblocks and facilitate discussions on how to overcome them.

      Articulate the service management initiative to the IT organization

      Spread the word and bring attention to your change message through effective mediums and organizational changes.

      Key aspects of a communication plan

      The methods of communication (e.g. newsletters, email broadcast, news of the day, automated messages) notify users of implementation.

      In addition, it is important to know who will deliver the message (delivery strategy). You need IT executives to deliver the message – work hard on obtaining their support as they are the ones communicating to their staff and should be your project champions.

      Anticipate organizational changes

      The implementation of the service management roadmap will most likely lead to organizational changes in terms of structure, roles, and responsibilities. Therefore, the team should be prepared to communicate the value that these changes will bring.

      Communicating Change

      • What is the change?
      • Why are we doing it?
      • How are we going to go about it?
      • What are we trying to achieve?
      • How often will we be updated?

      The Qualities of Leadership: Leading Change

      Create a project communication plan for your stakeholders

      This project cannot be successfully completed without the support of senior IT management.

      1. After the CIO has introduced this project through management meetings or informal conversation, find out how each IT leader feels about this project. You need to make sure the directors and managers of each IT team, especially the directors of application and infrastructure, are on board.
      2. After the meeting, the project leader should seek out the major stakeholders (particularly the heads of applications and infrastructure) and validate their level of support through formal or informal meetings. Create a list documenting the major stakeholders, their level of support, and how the project team will work to gain their approval.
      3. For each identified stakeholder, create a custom communication plan based on their role. For example, if the director of infrastructure is not a supporter, demonstrate how this project will enable them to better understand how to improve service quality. Provide periodic reporting or meetings to update the director on project progress.

      INPUT

      • A collaborative discussion between team members

      OUTPUT

      • Thorough briefing for project launch
      • A committed team

      Materials

      • Communication message and plan
      • Metric tracking

      Participants

      • Project leader
      • Core project team

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      Photo of an Info-Tech analyst is shown.
      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      1.1

      A screenshot of activity 1.1 is shown.

      Create a powerful, succinct mission statement

      Using Info-Tech’s sample mission statement as a guide, build your mission statement based on the objectives of this project and the benefits that this project will achieve. Keep the mission statement short and clear.

      1.2

      A screenshot of activity 1.2 is shown.

      Assemble the project team

      Create a project team with representatives from all major IT teams. Engage and communicate to the project team early and proactively.

      1.3

      A screenshot of activity 1.3 is shown.

      Identify project stakeholders and create a communication plan

      Info-Tech will help you identify key stakeholders who have a vested interest in the success of the project. Determine the communication message that will best gain their support.

      1.4

      A screenshot of activity 1.4 is shown.

      Use metrics to track the success of the project

      The onsite analyst will help the project team determine the appropriate metrics to measure the success of this project.

      PHASE 2

      Assess Your Current Service Management State

      Assess your current state

      This step will walk you through the following activities:

      • Use Info-Tech’s Service Management Maturity Assessment Tool to determine your overall practice maturity level.
      • Understand your level of completeness for each individual practice.
      • Understand the three major phases involved in the service management journey; know the symptoms of each phase and how they affect your target state selection.

      Step Insights

      • To determine the real maturity of your service management practices, you should focus on the results and output of the practice, rather than the activities performed for each process.
      • Focus on phase-level maturity as opposed to the level of completeness for each individual process.

      Phase 2 outline

      Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

      Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 2: Determine Your Service Management Current State

      Step 2.1 – Assess Impacting Forces

      Start with an analyst kick-off call:

      • Discuss the impacting forces that can affect the success of your service management program
      • Identify internal and external constraints and enablers
      • Review and interpret how to leverage or mitigate these elements

      Then complete these activities…

      • Present the findings of the organizational context
      • Facilitate a discussion and create consensus amongst the project team members on where the organization should start

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Step 2.2 – Build Vision, Mission, and Values

      Review findings with analyst:

      • Review your service management vision and mission statement and discuss the values

      Then complete these activities…

      • Socialize the vision, mission, and values to ensure they are aligned with overall organizational vision. Then, set the expectations for behavior aligned with the vision, mission, and values

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Step 2.3 – Assess Attitudes, Behaviors, and Culture

      Review findings with analyst:

      • Discuss tactics for addressing negative attitudes, behaviors, or culture identified

      Then complete these activities…

      • Add items to be addressed to roadmap

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Step 2.4 – Assess Governance Needs

      Review findings with analyst:

      • Understand the typical types of governance structure and the differences between management and governance
      • Choose the management structure required for your organization

      Then complete these activities…

      • Determine actions required to establish an effective governance structure and add items to be addressed to roadmap

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Step 2.5 – Perform SWOT Analysis

      Review findings with analyst:

      • Discuss SWOT analysis results and tactics for addressing within the roadmap

      Then complete these activities…

      • Add items to be addressed to roadmap

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Step 2.6 – Identify Desired State

      Review findings with analyst:

      • Discuss desired state and commitment needed to achieve aspects of the desired state

      Then complete these activities…

      • Use the desired state to critically assess the current state of your service management practices and whether they are achieving the desired outcomes
      • Prep for the SM maturity assessment

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Step 2.7 – Perform SM Maturity Assessment

      Review findings with analyst:

      • Review and interpret the output from your service management maturity assessment

      Then complete these activities…

      • Add items to be addressed to roadmap

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Service Management Maturity Assessment

      Step 2.8 – Review OCM Capabilities

      Review findings with analyst:

      • Review and interpret the output from your organizational change management maturity assessment

      Then complete these activities…

      • Add items to be addressed to roadmap

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Organizational Change Management Assessment

      Understand and assess impacting forces – constraints and enablers

      Constraints and enablers are organizational and behavioral triggers that directly impact your ability and approach to establishing Service Management practices.

      A model is shown to demonstrate the possibe constraints and enablers on your service management program. It incorporates available resources, the environment, management practices, and available technologies.

      Effective service management requires a mix of different approaches and practices that best fit your organization. There’s not a one-size-fits-all solution. Consider the resources, environment, emerging technologies, and management practices facing your organization. What items can you leverage or use to mitigate to move your service management program forward?

      Use Info-Tech’s “Organizational Context” template to list the constraints and enablers affecting your service management

      The Service Management Roadmap Presentation Template will help you understand the business environment you need to consider as you build out your roadmap.

      Discuss and document constraints and enablers related to the business environment, available resources, management practices, and emerging technologies. Any constraints will need to be addressed within your roadmap and enablers should be leveraged to maximize your results.


      Screenshot of Info-Tech's Service Management Roadmap Presentation Template is shown.

      Document constraints and enablers

      1. Discuss and document the constrains and enablers for each aspect of the management mesh: environment, resources, management practices, or technology.
      2. Use this as a thought provoker in later exercises.

      INPUT

      • A collaborative discussion

      OUTPUT

      • Organizational context constraints and enablers

      Materials

      • Whiteboards or flip charts

      Participants

      • All stakeholders

      Build compelling vision and mission statements to set the direction of your service management program

      While you are articulating the vision and mission, think about the values you want the team to display. Being explicit can be a powerful tool to create alignment.

      A vision statement describes the intended state of your service management organization, expressed in the present tense.

      A mission statement describes why your service management organization exists.

      Your organizational values state how you will deliver services.

      Use Info-Tech’s “Vision, Mission, and Values” template to set the aspiration & purpose of your service management practice

      The Service Management Roadmap Presentation Template will help you document your vision for service management, the purpose of the program, and the values you want to see demonstrated.

      If the team cannot gain agreement on their reason for being, it will be difficult to make traction on the roadmap items. A concise and compelling statement can set the direction for desired behavior and help team members align with the vision when trying to make ground-level decisions. It can also be used to hold each other accountable when undesirable behavior emerges. It should be revised from time to time, when the environment changes, but a well-written statement should stand the test of time.

      A screenshot of the Service Management Roadmap Presentation Temaplate is shown. Specifically it is showing the section on the vision, mission, and values results.

      Document your organization’s vision, mission , and values

      1. Vision: Identify your desired target state, consider the details of that target state, and create a vision statement.
      2. Mission: Consider the fundamental purpose of your SM program and craft a statement of purpose.
      3. Values: As you work through the vision and mission, identify values that your organization prides itself in or has the aspiration for.
      4. Discuss common themes and then develop a concise vision statement and mission statement that incorporates the group’s ideas.

      INPUT

      • A collaborative discussion

      OUTPUT

      • Vision statement
      • Mission statement
      • Organizational values

      Materials

      • Whiteboards or flip charts
      • Sample vision and mission statements

      Participants

      • All stakeholders
      • Senior leadership

      Understanding attitude, behavior, and culture

      Attitude

      • What people think and feel. It can be seen in their demeanor and how they react to change initiatives, colleagues, and users.

      Any form of organizational change involves adjusting people’s attitudes, creating buy-in and commitment. You need to identify and address attitudes that can lead to negative behaviors and actions or that are counter-productive. It must be made visible and related to your desired behavior.

      Behaviour

      • What people do. This is influenced by attitude and the culture of the organization.

      To implement change within IT, especially at a tactical level, both IT and organizational behavior needs to change. This is relevant because people don’t like to change and will resist in an active or passive way unless you can sell the need, value, and benefit of changing their behavior.

      Culture

      • The accepted and understood ways of working in an organization. The values and standards that people find normal and what would be tacitly identified to new resources.

      The organizational or corporate “attitude,” the impact on employee behavior and attitude is often not fully understood. Culture is an invisible element, which makes it difficult to identify, but it has a strong impact and must be addressed to successfully embed any organizational change or strategy.

      Culture is a critical and under-addressed success factor

      43% of CIOs cited resistance to change as the top impediment to a successful digital strategy.

      CIO.com

      75% of organizations cannot identify or articulate their culture or its impact.

      Info-Tech

      “Shortcomings in organizational culture are one of the main barriers to company success in the digital age.”

      McKinsey – “Culture for a digital age”

      Examples of how they apply

      Attitude

      • “I’ll believe that when I see it”
      • Positive outlook on new ideas and changes

      Behaviour

      • Saying you’ll follow a new process but not doing so
      • Choosing not to document a resolution approach or updating a knowledge article, despite being asked

      Culture

      • Hero culture (knowledge is power)
      • Blame culture (finger pointing)
      • Collaborative culture (people rally and work together)

      Why have we failed to address attitude, behavior, and culture?

        ✓ While there is attention and better understanding of these areas, very little effort is made to actually solve these challenges.

        ✓ The impact is not well understood.

        ✓ The lack of tangible and visible factors makes it difficult to identify.

        ✓ There is a lack of proper guidance, leadership skills, and governance to address these in the right places.

        ✓ Addressing these issues has to be done proactively, with intent, rigor, and discipline, in order to be successful.

        ✓ We ignore it (head in the sand and hoping it will fix itself).

      Avoidance has been a common strategy for addressing behavior and culture in organizations.

      Use Info-Tech’s “Culture and Environment” template to identify cultural constraints that should be addressed in roadmap

      The Service Management Roadmap Presentation Template will help you document attitude, behavior, and culture constraints.

      Discuss as a team attitudes, behaviors, and cultural aspects that can either hinder or be leveraged to support your vision for the service management program. Capture all items that need to be addressed in the roadmap.

      A screenshot of the Service Management Roadmap Presentation Template is shown. Specifically showing the culture and environment slide.

      Document your organization’s attitudes, behaviors, and culture

      1. Discuss and document positive and negative aspects of attitude, behavior, or culture within your organization.
      2. Identify the items that need to be addressed as part of your roadmap.

      INPUT

      • A collaborative discussion

      OUTPUT

      • Culture and environment worksheet

      Materials

      • Whiteboards or flip charts

      Participants

      • All stakeholders

      The relationship to governance

      Attitude, behavior, and culture are still underestimated as core success factors in governance and management.

      Behavior is a key enabler of good governance. Leading by example and modeling behavior has a cascading impact on shifting culture, reinforcing the importance of change through adherence.

      Executive leadership and governing bodies must lead and support cultural change.

      Key Points

      • Less than 25% of organizations have formal IT governance in place (ITSM Tools).
      • Governance tends to focus on risk and compliance (controls), but forgets the impact of value and performance.

      Lack of oversight often limits the value of service management implementations

      Organizations often fail to move beyond risk mitigation, losing focus of the goals of their service management practices and the capabilities required to produce value.

      Risk Mitigation

      • Stabilize IT
      • Service Desk
      • Incident Management
      • Change Management

      Gap

      • Organizational alignment through governance
      • Disciplined focus on goals of SM

      Value Production

      • Value that meets business and consumer needs

      This creates a situation where service management activities and roadmaps focus on adjusting and tweaking process areas that no longer support how the organization needs to work.

      How does establishing governance for service management provide value?

      Governance of service management is a gap in most organizations, which leads to much of the failure and lack of value from service management processes and activities.

      Once in place, effective governance enables success for organizations by:

      1. Ensuring service management processes improve business value
      2. Measuring and confirming the value of the service management investment
      3. Driving a focus on outcome and impact instead of simply process adherence
      4. Looking at the integrated impact of service management in order to ensure focused prioritization of work
      5. Driving customer-experience focus within organizations
      6. Ensuring quality is achieved and addressing quality impacts and dependencies between processes

      Four common service management process ownership models

      Your ownership structure largely defines how processes will need to be implemented, maintained, and improved. It has a strong impact on their ability to integrate and how other teams perceive their involvement.

      An organizational structure is shown. In the image is an arrow, with the tip facing in the right direction. The left side of the arrow is labelled: Traditional, and the right side is labelled: Complex. The four models are noted along the arrow. Starting on the left side and going to the right are: Distributed Process Ownership, Centralized Process Ownership, Federated Process Ownership, and Service Management Office.

      Most organizations are somewhere within this spectrum of four core ownership models, usually having some combination of shared traits between the two models that are closest to them on the scale.

      Info-Tech Insight

      The organizational structure that is best for you depends on your needs, and one is not necessarily better than another. The next four slides describe when each ownership level is most appropriate.

      Distributed process ownership

      Distributed process ownership is usually evident when organizations initially establish their service management practices. The processes are assigned to a specific group, who assumes some level of ownership over its execution.

      The distributed process ownership model is shown. CIO is listed at the top with four branches leading out from below it. The four branches are labelled: Service Desk, Operations, Applications, and Security.

      Info-Tech Insight

      This model is often a suitable approach for initial implementations or where it may be difficult to move out of siloes within the organization’s structure or culture.

      Centralized process ownership

      Centralized process ownership usually becomes necessary for organizations as they move into a more functional structure. It starts to drive management of processes horizontally across the organization while still retaining functional management control.

      A centralized process ownership model is shown. The CIO is at the top and the following are branches below it: Service Manager, Support, Middleware, Development, and Infrastructure.

      Info-Tech Insight

      This model is often suitable for maturing organizations that are starting to look at process integration and shared service outcomes and accountability.

      Federated process ownership

      Federated process ownership allows for global control and regional variation, and it supports product orientation and Agile/DevOps principles

      A federated process ownership model is shown. The Sponsor/CIO is at the top, with the ITSM Executive below it. Below that level is the: Process Owner, Process Manager, and Process Manager.

      Info-Tech Insight

      Federated process ownership is usually evident in organizations that have an international or multi-regional presence.

      Service management office (SMO)

      SMO structures tend to occur in highly mature organizations, where service management responsibility is seen as an enterprise accountability.

      A service management office model is shown. The CIO is at the top with the following branches below it: SMO, End-User Services, Infra., Apps., and Architecture.

      Info-Tech Insight

      SMOs are suitable for organizations with a defined IT and organizational strategy. A SMO supports integration with other enterprise practices like enterprise architecture and the PMO.

      Determine which process ownership and governance model works best for your organization

      The Service Management Roadmap Presentation Template will help you document process ownership and governance model

      Example:

      Key Goals:

        ☐ Own accountability for changes to core processes

        ☐ Understand systemic nature and dependencies related to processes and services

        ☐ Approve and prioritize improvement and CSI initiatives related to processes and services

        ☐ Evaluate success of initiative outcomes based on defined benefits and expectations

        ☐ Own Service Management and Governance processes and policies

        ☐ Report into ITSM executive or equivalent body

      Membership:

        ☐ Process Owners, SM Owner, Tool Owner/Liaison, Audit

      Discuss as a team which process ownership model works for your organization. Determine who will govern the service management practice. Determine items that should be identified in your roadmap to address governance and process ownership gaps.

      Use Info-Tech’s “SWOT” template to identify strengths, weaknesses, opportunities & threats that should be addressed

      The Service Management Roadmap Presentation Template will help you document items from your SWOT analysis.

      A screenshot of the Service Management Roadmap Presentation Template is shown. Specifically the SWOT section is shown.

      Brainstorm the strengths, weaknesses, opportunities, and threats related to resources, environment, technology, and management practices. Add items that need to be addressed to your roadmap.

      Perform a SWOT analysis

      1. Brainstorm each aspect of the SWOT with an emphasis on:
      • Resources
      • Environment
      • Technologies
      • Management Practices
    • Record your ideas on a flip chart or whiteboard.
    • Add items to be addressed to the roadmap.
    • INPUT

      • A collaborative discussion

      OUTPUT

      • SWOT analysis
      • Priority items identified

      Materials

      • Whiteboards or flip charts

      Participants

      • All stakeholders

      Indicate desired maturity level for your service management program to be successful

      Discuss the various maturity levels and choose a desired level that would meet business needs.

      The desired maturity model is depicted.

      INPUT

      • A collaborative discussion

      OUTPUT

      • Desired state of service management maturity

      Materials

      • None

      Participants

      • All stakeholders

      Use Info-Tech’s Service Management Process Maturity Assessment Tool to understand your current state

      The Service Management Process Maturity Assessment Tool will help you understand the true state of your service management.

      A screenshot of Info-Tech's Service Management Process Assessment Tool is shown.

      Part 1, Part 2, and Part 3 tabs

      These three worksheets contain questions that will determine the overall maturity of your service management processes. There are multiple sections of questions focused on different processes. It is very important that you start from Part 1 and continue the questions sequentially.

      Results tab

      The Results tab will display the current state of your service management processes as well as the percentage of completion for each individual process.

      Complete the service management process maturity assessment

      The current-state assessment will be the foundation of building your roadmap, so pay close attention to the questions and answer them truthfully.

      1. Start with tab 1 in the Service Management Process Maturity Assessment Tool. Remember to read the questions carefully and always use the feedback obtained through the end-user survey to help you determine the answer.
      2. In the “Degree of Process Completeness” column, use the drop-down menu to input the results solicited from the goals and objectives meeting you held with your project participants.
      3. A screenshot of Info-Tech's Service Management Process Assessment Tool is shown. Tab 1 is shown.
      4. Host a meeting with all participants following completion of the survey and have them bring their results. Discuss in a round-table setting, keeping a master sheet of agreed upon results.

      INPUT

      • Service Management Process Maturity Assessment Tool questions

      OUTPUT

      • Determination of current state

      Materials

      • Service Management Process Maturity Assessment Tool

      Participants

      • Project team members

      Review the results of your current-state assessment

      At the end of the assessment, the Results tab will have action items you could perform to close the gaps identified by the process assessment tool.

      A screenshot of Info-Tech's Service Management Process Maturity Assessment Results is shown.

      INPUT

      • Maturity assessment results

      OUTPUT

      • Determination of overall and individual practice maturity

      Materials

      • Service Management Maturity Assessment Tool

      Participants

      • Project team members

      Use Info-Tech’s OCM Capability Assessment tool to understand your current state

      The Organizational Change Management Capabilities Assessment tool will help you understand the true state of your organizational change management capabilities.

      A screenshot of Info-Tech's Organizational Change Management Capabilities Assessment

      Complete the Capabilities tab to capture the current state for organizational change management. Review the Results tab for interpretation of the capabilities. Review the Recommendations tab for actions to address low areas of maturity.

      Complete the OCM capability assessment

      1. Open Organizational Change Management Capabilities Assessment tool.
      2. Come to consensus on the most appropriate answer for each question. Use the 80/20 rule.
      3. Review result charts and discuss findings.
      4. Identify roadmap items based on maturity assessment.

      INPUT

      • A collaborative discussion

      OUTPUT

      • OCM Assessment tool
      • OCM assessment results

      Materials

      • OCM Capabilities Assessment tool

      Participants

      • All stakeholders

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      Photo of an Info-Tech analyst is shown.

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      2.1

      A screenshot of activity 2.1 is shown.

      Create a powerful, succinct mission statement

      Using Info-Tech’s sample mission statement as a guide, build your mission statement based on the objectives of this project and the benefits that this project will achieve. Keep the mission statement short and clear.

      2.2

      A screenshot of activity 2.2 is shown.

      Complete the assessment

      With the project team in the room, go through all three parts of the assessment with consideration of the feedback received from the business.

      2.3

      A screenshot of activity 2.3 is shown.

      Interpret the results of the assessment

      The Info-Tech onsite analyst will facilitate a discussion on the overall maturity of your service management practices and individual process maturity. Are there any surprises? Are the results reflective of current service delivery maturity?

      PHASE 3

      Build Your Service Management Roadmap

      Build Roadmap

      This step will walk you through the following activities:

      • Document your vision and mission on the roadmap one-pager.
      • Using the inputs from the current-state assessments, identify the key themes required by your organization.
      • Identify individual initiatives needed to address key themes.

      Step Insights

      • Using the Info-Tech thought model, address foundational gaps early in your roadmap and establish the management methods to continuously make them more robust.
      • If any of the core practices are not meeting the vision for your service management program, be sure to address these items before moving on to more advanced service management practices or processes.
      • Make sure the story you are telling with your roadmap is aligned to the overall organizational goals.

      Phase 3 outline

      Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

      Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 3: Determine Your Service Management Target State

      Step 3.1 – Document the Overall Themes

      Start with an analyst kick-off call:

      • Review the outputs from your current-state assessments to identify themes for areas that need to be included in your roadmap

      Then complete these activities…

      • Ensure foundational elements are solid by adding any gaps to the roadmap
      • Identify any changes needed to management practices to ensure continuous improvement

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Step 3.2 – Determine Individual Initiatives

      Review findings with analyst:

      • Determine the individual initiatives needed to close the gaps between the current state and the vision

      Then complete these activities…

      • Finalize and document roadmap for executive socialization

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Focus on a strong foundation to build higher value service management practices

      Info-Tech Insight

      Focus on behaviors and expected outcomes before processes.

      Foundational elements

      • Operating model facilitates service management goals
      • Culture of service delivery
      • Governance discipline to evaluate, direct, and monitor
      • Management discipline to deliver

      Stabilize

      • Deliver stable, reliable IT services to the business
      • Respond to user requests quickly and efficiently
      • Resolve user issues in a timely manner
      • Deploy changes smoothly and successfully

      Proactive

      • Avoid/prevent service disruptions
      • Improve quality of service (performance, availability, reliability)

      Service Provider

      • Understand business needs
      • Ensure services are available
      • Measure service performance, based on business-oriented metrics

      Strategic Partner

      • Fully aligned with business
      • Drive innovation
      • Drive measurable value

      Info-Tech Insight

      Continued leadership support of the foundational elements will allow delivery teams to provide value to the business. Set the expectation of the desired maturity level and allow teams to innovate.

      Identify themes that can help you build a strong foundation before moving to higher level practices

      A model is depicted that shows the various target states. There are 6 levels showing in the example, and the example is made to look like a tree with a character watering it. In the roots, the level is labelled foundational. The trunk is labelled the core. The lowest hanging branches of the tree is the stabilize section. Above it is the proactive section. Nearing the top of the tree is the service provider. The top most branches of the tree is labelled strategic partner.

      Before moving to advanced service management practices, you must ensure that the foundational and core elements are robust enough to support them. Leadership must nurture these practices to ensure they are sustainable and can support higher value, more mature practices.

      Use Info-Tech’s “Service Management Roadmap” template to document your vision, themes and initiatives

      The Service Management Roadmap Presentation Template contains a roadmap template to help communicate your vision, themes to be addressed, and initiatives

      A screenshot of Info-Tech's Service Management Roadmap template is shown.

      Working from the lower maturity items to the higher value practices, identify logical groupings of initiatives into themes. This will aid in communicating the reasons for the needed changes. List the individual initiatives below the themes. Adding the service management vision and mission statements can help readers understand the roadmap.

      Document your service management roadmap

      1. Document the service management vision and mission on the roadmap template.
      2. Identify, from the assessments, areas that need to be improved or implemented.
      3. Group the individual initiatives into logical themes that can ease communication of what needs to happen.
      4. Document the individual initiatives.
      5. Document in terms that business partners and executive sponsors can understand.

      INPUT

      • Current-state assessment outputs
      • Maturity model

      OUTPUT

      • Service management roadmap

      Materials

      • Whiteboard
      • Roadmap template

      Participants

      • All stakeholders

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      Photo of an Info-Tech analyst is shown.

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      3.1

      A screenshot of activity 3.1 is shown.

      Identify themes to address items from the foundational level up to higher value service management practices

      Identify easily understood themes that will help others understand the expected outcomes within your organization.

      A screenshot of activity 3.2 is shown.

      Document individual initiatives that contribute to the themes

      Identify specific activities that will close gaps identified in the assessments.

      PHASE 2

      Build Communication Slide

      Complete your service management roadmap

      This step will walk you through the following activities:

      • Use the current-state assessment exercises to document the state of your service management practices. Document examples of the behaviors that are currently seen.
      • Document the expected short-term gains. Describe how you want the behaviors to change.
      • Document the long-term vision for each item and describe the benefits you expect to see from addressing each theme.

      Step Insights

      • Use the communication template to acknowledge the areas that need to be improved and paint the short- and long-term vision for the improvements to be made through executing the roadmap.
      • Write it in business terms so that it can be used widely to gain acceptance of the upcoming changes that need to occur.
      • Include specific areas that need to be fixed to make it more tangible.
      • Adding the values from the vision, mission, and values exercise can also help you set expectations about how the team will behave as they move towards the longer-term vision.

      Phase 4 Outline

      Call 1-888-670-8889 or email GuidedImplementations@InfoTech.com for more information.

      Complete these steps on your own, or call us to complete a guided implementation. A guided implementation is a series of 2-3 advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 4: Build the Service Management Roadmap

      Step 4.1: Document the Current State

      Start with an analyst kick-off call:

      • Review the pain points identified from the current state analysis
      • Discuss tactics to address specific pain points

      Then complete these activities…

      • Socialize the pain points within the service delivery teams to ensure nothing is being misrepresented
      • Gather ideas for the future state

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Step 4.2: List the Future Vision

      Review findings with analyst:

      • Review short- and long-term vision for improvements for the pain points identified in the current state analysis

      Then complete these activities…

      • Prepare to socialize the roadmap
      • Ensure long-term vision is aligned with organizational objectives

      With these tools & templates:

      Service Management Roadmap Presentation Template

      Use Info-Tech’s “Service Management Roadmap – Brought to Life” template to paint a picture of the future state

      The Service Management Roadmap Presentation Template contains a communication template to help communicate your vision of the future state

      A screenshot of Info-Tech's Service Management Roadmap - Brought to Life template

      Use this template to demonstrate how existing pain points to delivering services will improve over time by painting a near- and long-term picture of how things will change. Also list specific initiatives that will be launched to affect the changes. Listing the values identified in the vision, mission, and values exercise will also demonstrate the team’s commitment to changing behavior to create better outcomes.

      Document your current state and list initiatives to address them

      1. Use the previous assessments and feedback from business or customers to identify current behaviors that need addressing.
      2. Focus on high-impact items for this document, not an extensive list.
      3. An example of step 1 and 2 are shown.
      4. List the initiatives or actions that will be used to address the specific pain points.

      An example of areas for improvement.

      INPUT

      • Current-state assessment outputs
      • Feedback from business

      OUTPUT

      • Service Management Roadmap Communication Tool, in the Service Management Roadmap Presentation

      Materials

      • Whiteboard
      • Roadmap template

      Participants

      • All stakeholders

      Document your future state

      An example of document your furture state is shown.

      1. For each pain point document the expected behaviors, both short term and longer term.
      2. Write in terms that allow readers to understand what to expect from your service management practice.

      INPUT

      • Current-state assessment outputs
      • Feedback from business

      OUTPUT

      • Service Management Roadmap Communication Tool, in the Service Management Roadmap Presentation Template

      Materials

      • Whiteboard
      • Roadmap template

      Participants

      • All stakeholders

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts:

      Photo of an Info-Tech analyst is shown.

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      4.1

      A screenshot of activity 4.1 is shown.

      Identify the pain points and initiatives to address them

      Identify items that the business can relate to and initiatives or actions to address them.

      4.2

      A screenshot of activity 4.2 is shown.

      Identify short- and long-term expectations for service management

      Communicate the benefits of executing the roadmap both short- and long-term gains.

      Research contributors and experts

      Photo of Valence Howden

      Valence Howden, Principal Research Director, CIO Practice

      Info-Tech Research Group

      Valence helps organizations be successful through optimizing how they govern, design, and execute strategies, and how they drive service excellence in all work. With 30 years of IT experience in the public and private sectors, he has developed experience in many information management and technology domains, with focus in service management, enterprise and IT governance, development and execution of strategy, risk management, metrics design and process design, and implementation and improvement.

      Photo of Graham Price

      Graham Price, Research Director, CIO Practice

      Info-Tech Research Group

      Graham has an extensive background in IT service management across various industries with over 25 years of experience. He was a principal consultant for 17 years, partnering with Fortune 500 clients throughout North America, leveraging and integrating industry best practices in IT service management, service catalog, business relationship management, IT strategy, governance, and Lean IT and Agile.

      Photo of Sharon Foltz

      Sharon Foltz, Senior Workshop Director

      Info-Tech Research Group

      Sharon is a Senior Workshop Director at Info-Tech Research Group. She focuses on bringing high value to members via leveraging Info-Tech’s blueprints and other resources enhanced with her breadth and depth of skills and expertise. Sharon has spent over 15 years in various IT roles in leading companies within the United States. She has strong experience in organizational change management, program and project management, service management, product management, team leadership, strategic planning, and CRM across various global organizations.

      Related Info-Tech Research

      Build a Roadmap for Service Management Agility

      Extend the Service Desk to the Enterprise

      Bibliography

      • “CIOs Emerge as Disruptive Innovators.” CSC Global CIO Survey: 2014-2015. Web.
      • “Digital Transformation: How Is Your Organization Adapting?” CIO.com, 2018. Web.
      • Goran, Julie, Laura LaBerge, and Ramesh Srinivasan. “Culture for a digital age.” McKinsey, July 2017. Web.
      • The Qualities of Leadership: Leading Change. Cornelius & Associates, 14 April 2012.
      • Wilkinson, Paul. “Culture, Ethics, and Behavior – Why Are We Still Struggling?” ITSM Tools, 5 July 2018. Web.

      Infrastructure and Operations Priorities 2023

      • Buy Link or Shortcode: {j2store}54|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Disruptive & Emerging Technologies
      • Parent Category Link: /disruptive-emerging-technologies
      • Get out of your I&O silo. I&O teams must be expected to work alongside and integrate with cyber security operations.
      • Being unprepared for new ESG reporting mandates without a clear and validated ESG reporting process puts your organization at risk.
      • Get ahead of inflationary pressures with early budgetary planning and identify the gap between the catchup projects and required critical net new investments.

      Our Advice

      Critical Insight

      • Establish I&O within an AI governance program to build trust in AI results, behaviors, and limit legal exposure.
      • Develop data governance program that includes an I&O data steward for oversight.
      • Ready or not, the metaverse is coming to an infrastructure near you. Start expanding I&O technologies and processes to support a metaverse infrastructure.

      Impact and Result

      • Provide a framework that highlight the impacts the threats of an economic slowdown, growing regulatory reporting requirements, cyber security attacks and opportunity that smart governance over AI, data stewardship and the looming explosion of augmented reality and Web 3.0 technologies.
      • Info-Tech can help communicate your I&O priorities into compelling cases for your stakeholders.

      Infrastructure and Operations Priorities 2023 Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Infrastructure & Operations Priorities 2023 – A framework to dive deeper into the trends most relevant to you and your organization

      Discover Info-Tech's six priorities for Infrastructure & Operations leaders.

      Infographic

      Further reading

      Infrastructure &Operations Priorities 2023

      Navigate the liminal space between threats and opportunities.

      2023: A liminal space between threats and opportunities

      Over the last several years, successful CEOs turned to their Infrastructure and Operations (I&O) departments to survive the effects of the pandemic. It was I&O leaders who were able to reconfigure critical infrastructure on the fly to support remote work, adapt to critical supply chain shortages, and work with lines of business managers to innovate operational workflows.

      2023 promises to bring a new set of challenges. Building on the credibility established during the pandemic, I&O is in a unique position to influence the direction a business will take to be successful in a time of austerity.

      I&O members are going to be asked to mitigate the threats of volatility from recession pressures, new cybersecurity attacks, and operational process and litigation from regulatory mandates. At the same time, I&O members are being asked for fundamental digital transformation items to realize long-term opportunities to their organizations in 2023.

      Seemingly counter-intuitive in a time of economic slowdown, organizations in 2023 will want to start the groundwork to realizing the I&O opportunities that unstructured data and artificial intelligence have promised, while prepping for what has been mislabeled as the Metaverse.

      If you are in a traditionally risk adverse industry, you’re more likely to be impacted by the threat mitigation.

      Opportunistic I&O members will use 2023 to proactively jumpstart digital transformation.

      Introduction

      Welcome to the Info-Tech 2023 I&O Priorities Report

      If I&O members learned anything from the last few years, it’s how to tactically respond to the disruptive waves often arising from sources external to the organization. The good news is that Info-Tech’s I&O priorities report provides forward-looking insights to help members become more proactive to the tsunami of change predicted in our Trends Report to happen over the next three to five years.

      Info-Tech I&O priorities are generated through a phased approach. The first phase senses and identifies mega and macro tends in the digital landscape to formulate hypotheses about the trends for the next three to five years. These hypotheses are validated by sending out a survey to Info-Tech members. The responses from 813 members was used to produce an Info-Tech Trends Report focused on major long-term trends.

      The I&O Priorities were determined by combining the I&O member responses within the Info-tech Trends Survey with insightful signals from secondary research, economic markets, regulatory bodies, industry organizations, and vendors. The six I&O priorities identified in this report are presented in a framework that highlight the impacts of an economic slowdown, growing regulatory reporting requirements, cybersecurity threats, smart governance of AI, embracing stewardship of data, and the looming explosion of augmented reality and Web 3.0 technologies.

      We also have a challenge exercise to help you communicate which priorities to focus your I&O organization on. Additionally, we linked some Info-tech research and tools related to the priorities that help your I&O organization formulate actionable plans for each area.

      Priorities

      Six forward-looking priorities for the next year.

      Focus

      Activity to help select which priorities are relevant for you.

      Actions

      Actionable Info-tech research and tools to help you deliver.

      Infrastructure & Operations priorities

      The I&O priorities were determined by combining I&O member responses from the Tech Trends and Priorities 2023 survey with insightful signals from secondary research, economic markets, regulatory bodies, industry organizations, and vendors.

      The image contains a screenshot of the Infrastructure & Operations priorities.

      I&O Priorities 2023

      The image contains a screenshot of the I&O Priorities.

      I&O priorities framework

      Threats signals

      Enhance I&O Cybersecurity

      Produce ESG Reporting

      Recession Readiness

      Get out of your silo. Forget your job description and start doing what needs to be done.

      Infrastructure rarely has authority in these areas, but somehow it ends up with many of the responsibilities. You can't afford to be reactive. Forget about your traditional silo and get out in front of these topics. Not in your job description? Find out whose job it is and make them aware. Better yet – take charge! If you're going to be responsible you might as well be in control.

      Opportunities signals

      AI Governance: Watching the Watchers

      Prep for A Brave New Metaverse

      Data Governance: Cornerstone of Value

      Proper stewardship of data is an I&O must. If thought you had problems with your unstructured data, wait until you see the data sprawl coming from the metaverse.

      I&O needs to be so much more than just an order taker for the dev teams and lines of business. The sprawl of unstructured data in Word, Excel, PDF and PowerPoint was bad historically; imagine those same problems at metaverse scale! Simple storage and connectivity is no longer enough – I&O must move upstream with more sophisticated service and product offerings generated through proper governance and stewardship.

      Challenge: Expand the I&O border

      The hidden message in this report is that I&O priorities extend beyond the traditional scope of I&O functions. I&O members need to collaborate across functional areas to successfully address the priorities presented in this report.

      Info-Tech can help! Align your priorities with our material on how to Build a Business-Aligned IT Strategy. Use a modified version of the Strategy Initiative Template (next slide) to convey your strong opinion on the priorities you need your stakeholders to know about. And do so in a way that is familiar so they will easily understand.

      The image contains a screenshot of Info-Tech's Maturity Ladder.
      Info-Tech 2023 Trends Survey Results

      Call your Executive Advisor or Counselor to help identify the one or two key messages you want to bring forward for success in 2023!

      Info-Tech IT Strategy Initiative Template, from the IT Strategy Presentation Template & Priorities Report Initiative Template

      .
      The image contains a screenshot of a template for your priorities.

      Protect from threats

      Get out of your silo. Forget your job description and just start doing what needs to be done.

      Enhance I&O Cybersecurity

      Produce ESG Reporting

      Recession Readiness

      Enhance cybersecurity response

      SIGNALS

      Cybersecurity incidents are
      a clear and present danger
      to I&O members.

      Cybersecurity incidents have
      a large financial impact
      on organizations.

      Related Info-Tech Research

      Of the surveyed I&O members, 53% identified cybersecurity incidents as the number one threat disrupting their operations in 2023. It’s understandable, as over 18% of surveyed I&O members experienced a cybersecurity incident in 2022. Alarmingly, 10% of surveyed I&O members didn’t know if they had a cybersecurity incident. The impact to the organization was with 14% of those incidents directly impacting their organizations for anywhere from 6 to 60 days.

      The 2022 report “Cost of a Data Breach” was conducted by IBM and the Ponemon Institute using data from 550 companies (across 17 countries) that experienced a security incident during a 12-month period ending in March 2022. It highlighted that the average total organizational cost of a security breach globally was USD 4.35M (locally these numbers expand to USA at USD 9.44M, Canada at USD 5.64, UK at USD 5.05M, Germany at USD 4.85M).

      (Source: IBM, 2022)

      Enhance cybersecurity response

      SIGNALS

      Organizations' exposure comes from internal and external sources.

      The right tools and process can reduce the impact of a cybersecurity incident.

      Related Info-Tech Research

      The IBM/Ponemon Institute report highlighted the following:

      • 59% of organizations didn’t deploy a zero-trust architecture on critical infrastructure to reduce exposure.
      • 19% of the breaches originated from within their business partner eco-system.
      • 45% were cloud-based.

      (Source: IBM, 2022)

      The IBM/Ponemon Institute report also identified technologies and procedures to reduce the fiscal impacts of cybersecurity breaches. Having a dedicated security incident response team with a regularly tested plan reduced the incident cost by an average of USD 2.66M. A fully implemented AI security deduction and response automation system can provide average incident savings of 27.6%.

      Enhance cybersecurity response

      SIGNALS

      Cybersecurity spending is a major and expanding expenditure for our members.

      Cybersecurity is going
      to include brand misinformation.

      For 36% of surveyed I&O members, cybersecurity consumed between 10-20% of their total budget in 2022. Moreover, cybersecurity defense funding is expected to increase for 57% of I&O members.

      A third of surveyed I&O members viewed misinformation as a major risk to their organization for 2023 and 2024. Only 38% of the I&O members reported that they will have software in place to monitor and manage social media posts.

      Increasing environment and regulatory complexity demands more sophisticated cybersecurity operations.

      Infrastructure teams must be expected to work alongside and integrate with cybersecurity operations.

      Enhance cybersecurity response

      CALL TO ACTION

      Get out of your I&O silo and form cross-functional cybersecurity teams.

      I&O priority actions

      Establish a cross-functional security steering committee to coordinate security processes and technologies. The complexity of managing security across modern applications, cloud, IoT, and network infrastructure that members operate is greater than ever before and requires coordinated teamwork.

      Contain the cyber threat with zero trust (ZT) architecture. Extend ZT to network and critical infrastructure to limit exposure.

      Leverage AI to build vigilant security intelligence. Smart I&O operators will make use of AI automation to augment their security technologies to help detect threats and contain security incidents on critical infrastructure.

      Enhance cybersecurity response

      I&O priority actions

      Build specialized cybersecurity incident management protocols with your service desk. Build integrated security focused teams within service desk operations that continually test and improve security incident response protocols internally and with specialized security vendors. In some organizations, security incident response teams extend beyond traditional infrastructure into social media. Work cross-functionally to determine the risk exposure to misinformation and incident response procedures.

      Treat lost or stolen equipment as a security incident. Develop hardware asset management protocols for tracking and reporting on these incidents and keep a record of equipment disposal. Implement tools that allow for remote deletion of data and report on lost or stolen equipment.

      Produce ESG reporting

      SIGNALS

      Government mandates present an operational risk to I&O members.

      ESG reporting is
      often incomplete.

      Related Info-Tech Research

      Surveyed members identified government-enacted policy changes to be a top risk to disrupting to their business operations in 2023. One of the trends identified by Info-Tech is that the impact of regulations on environmental, social, and governance (ESG) reporting are being rolled out by governments worldwide.

      Alarmingly, only 7% of surveyed members responded that they could very accurately report on their carbon footprint and 23% said they were not able to report accurately at all.

      Produce ESG reporting

      SIGNALS

      ESG mandates are being rolled out globally.

      ESG reporting has greatly expanded since a 2017 report by Task Force on Climate-Related Financial Disclosures (TCFD, 2017) which recommended that organizations disclose climate-related financial metrics for investors to appropriately price climate-related risks to share price. In 2021, the Swiss Finance Institute research paper (Sautner, 2021) identified 29 countries that require ESG reporting, primarily for larger public companies, financial institutions, and state-owned corporations.

      Global ESG mandates

      The image contains a screenshot of a world map that demonstrates the Global ESG Mandates.

      29 nations with ESG mandates identified by the Swiss Finance Institute

      Produce ESG reporting

      SIGNALS

      ESG mandates are being rolled out globally.

      The EU has mandated ESG reporting for approximately 11,700 large public companies with more than 500 employees under the Non-Financial Reporting Directive (NFRD), since 2014. The EU is going to replace the NFRD with the Corporate Sustainability Reporting Directive (European Council, 2022), which has set a 3-year timetable for escalating the ESG reporting level to what is estimated to be about 75% of EU total turnover (WorldFavor, 2022).

      • 2024: Companies with 500 or more employees.
      • 2025: Companies with 250 or more employee or 40M EU in revenue/20M in total assets.
      • 2026: SMEs, smaller credit financial, and captive insurance institutions.

      It's been a long time since most enterprises had to report on things like power efficiency factors.

      But don't think that being in the cloud will insulate you from a renewed interest in ESG reporting.

      Produce ESG reporting

      CALL TO ACTION

      Being unprepared for new ESG reporting mandates without a clear and validated ESG reporting process puts your organization at risk.

      I&O priority actions

      Understand ESG risk exposure. Define the gap between what ESG reporting is required in your jurisdiction and current reporting capabilities to meet them. Build the I&O role with responsibility for ESG reporting.

      Include vendors in ESG reporting. Review infrastructure facilities with landlords, utilities, and hosting providers to see if they can provide ESG reporting on sustainable power generation, then map it to I&O power consumption as part of their contractual obligations. Ask equipment vendors to provide ESG reporting on manufacturing materials and energy consumption to boot-strap data collection.

      Implement a HAM process to track asset disposal and other types of e-waste. Update agreements with disposal vendors to get reporting on waste and recycle volumes.

      Produce ESG reporting

      I&O priority actions

      Implement an ESG reporting framework. There are five major ESG reporting frameworks being used globally. Select one of the frameworks below that makes sense for your organization, and implement it.

      ISO 14001 Environmental Management: Part of the ISO Technical Committee family of standards that allows your organization to understand its legal requirements to become certified in ESG.

      Global Reporting Initiative (GRI) Sustainability Reporting Standards: GRI has been developing ESG reporting standards since 1997. GRI provides a modular ESG framework applicable to all sizes and sectors of organizations worldwide.

      Principles for Responsible Investment: UN-developed framework for ESG reporting framework for disclosure in responsible investments.

      Sustainability Accounting Standards Board (SASB): ESG report framework to be used by investors.

      UN Global Compact: ESG reporting framework based on 10 principles that organizations can voluntarily contribute data to.

      Implement a HAM process to track asset disposal and other types of e-waste. Update agreements with disposal vendors to get reports on waste and recycle volumes.

      Recession readiness

      SIGNALS

      Managing accelerated technical debt.

      Recessionary pressures.

      Related Info-Tech Research

      I&O members experienced a spike in technical debt following the global pandemic economic shutdown, workforce displacement, and highly disrupted supply chains. 2023 presents a clear opportunity to work on these projects.

      The shortages in workforce and supply chain have accelerated inflation post pandemic. Central banks have started to slow down inflation in 2022 by raising interest rates. However, the World Bank has forecast a potential 2% rise in interest rates as the battle with inflation continues into 2023 and beyond, which could set off a global slowdown in GDP growth to 0.5%, qualifying as a recession. If interest rates continue to climb, I&O members may struggle with the higher cost of capital for their investments.

      (Source: World Bank Organization, 2022)

      Recession readiness

      SIGNALS

      I&O budgets expected to increase.

      Focused budgetary increases.

      Despite economists’ prediction of a looming recession and inflationary pressures, only 11% of I&O members surveyed indicated that they anticipated any reduction in IT budgets for 2023. In fact, 44% of I&O members expected an increase of IT budgets of between 6% and 30%.

      These increases in budget are not uniform across all investments. Surveyed I&O members indicated that the largest anticipated budget increases (compared to 2022) were in the areas of:

      • AI/machine learning ( +7.5%)
      • 5G (+7%)
      • Data Mesh/Fabric and Data Lake infrastructure (+5.7% and +4.4%, respectively)
      • Mixed reality technologies (augmented or virtual reality) (+3.3%)
      • Next generation cybersecurity (+1.7%)

      "2022 has been the first true opportunity to start getting caught up on technical debt stemming from the post pandemic supply chain and resource shortages. That catch-up is going to continue for some time.

      Unfortunately, the world isn't sitting still while doing that. In fact, we see new challenges around inflationary pressures. 2023 planning is going to be a balancing act between old and new projects."

      Paul Sparks,
      CTO at Brookshire Grocery Company

      Recession readiness

      SIGNALS

      Tough choices on budgetary spends.

      The responses indicated that I&O members expect decreased reinvestment for 2023 for the following:

      • API programming (-21.7%)
      • Cloud computing (-19.4%)
      • 44% of I&O members indicated if 2023 requires costs cutting, 5-20% of their cloud computing investment will be at risk of the chopping block!
      • Workforce management (-9.4%)
      • No-code /low-code infrastructure (-5.3%)

      Make sure you can clearly measure the value of all budgeted I&O activities.

      Anything that can't demonstrate clear value to leadership is potentially on the chopping block.

      Recession readiness

      CALL TO ACTION

      Get ahead of inflationary pressures with early budgetary planning, and identify the gap between the catch-up projects and required critical net new investments.

      II&O priority actions

      Hedge against inflation on infrastructure projects. Develop and communicate value-based strategies to lock in pricing and mitigate inflationary risk with vendors.

      Communicate value-add on all I&O budgeted items. Define an infrastructure roadmap to highlight which projects are technical debt and which are new strategic investments, and note their value to the organization.

      Look for cost saving technologies. Focus on I&O projects that automate services to increase productivity and optimize head count.

      Realize opportunities

      Build on a record of COVID-related innovation success and position the enterprise to take advantage of 2023.

      AI governance: Watching the watchers

      Data stewardship: Cornerstone of value

      Prep for a brave new metaverse

      AI governance: Watching the watchers

      SIGNALS

      Continued investment
      in AI technologies

      AI technology is permeating diverse I&O functional areas.

      Related Info-Tech Research

      About 32% of survey respondents who work in I&O said that they already invest in AI, and 40% intend to invest in 2023.

      I&O members have identified the following areas as the top five focal points for AI uses within their organizations.

      • Automated repetitive, low-level tasks
      • Business analytics or intelligence
      • Identification of risks and improvement of security response
      • Monitoring and governance
      • Sensor data analysis

      AI governance: Watching the watchers

      SIGNALS

      Consequences for misbehaving AI.

      I&O leaders can expect to have silos of AI in pockets scattered across the enterprise. Without oversight on the learning model and the data used for training and analytics there is a risk of overprovisioning, which could reduce the efficiency and effectiveness of AI models and results.

      This scale advantage of AI could result in operational inefficiencies without oversight. For example, bad governance means garbage in / garbage out. Which is worse: getting 100 outputs from a system with a 1% error rate, or getting 10,000 outputs from a system with an 1% error rate?

      These are just the operational issues; legally you can be on the hook, as well. The EU Parliament has issued a civil liability regime for AI (European Parliament, n.d.) which imposes liability to operators of AI systems, regardless of whether they acted with operational due diligence. Additionally, the IEEE (IEEE, 2019) is advocating for legal frameworks and accountability for AI that violates human rights and privacy laws and causes legal harm.

      Who is going to instill standards for AI Operations? Who is going to put in the mechanisms to validate and explain the output of AI black boxes?

      If you said it’s going to end up
      being Infrastructure and Operations – you were right!

      AI governance: Watching the watchers

      CALL TO ACTION

      Establish I&O within an AI governance program to build trust in AI results and behaviors and limit legal exposure.

      I&O priority actions

      Define who has overall AI accountability for AI governance within I&O. This role is responsible for establishing strategic governance metrics over AI use and results, and identifying liability risks.

      Maintain an inventory of AI use. Conduct an audit of where AI is used within I&O, and identify gaps in documentation and alignment with I&O processes and organizational values.

      Define an I&O success map. Provide transparency of AI use by generating pseudo code of AI models, and scorecard AI decision making with expected predictions and behavioral actions taken.

      AI governance: Watching the watchers

      Manage bias in AI decision making. Work with AI technology vendors to identify how unethical bias can enter the results, using operational data sets for validation prior to rollout.

      Protect AI data sets from manipulation. Generate new secure storage for AI technology audit trails on AI design making and results. Work with your security team to ensure data sets used by AI for training can’t be corrupted.

      Data governance: Cornerstone of value

      SIGNALS

      Data volumes grow
      with time.

      Data is seen as a source for generating new value.

      Related Info-Tech Research

      Of surveyed I&O members, 63% expected to see the data storage grow by at least 10% in 2023, and 15% expected a 30% or more growth in data storage volumes.

      I&O members identified the top three ways data brings value to the organization:

      • Helping reduce operational costs.
      • Presenting value-added to existing products and services.
      • Acquiring new customers.

      Data governance: Cornerstone of value

      SIGNALS

      Approach to data analysis is primarily done in-house.

      85% of surveyed I&O members are doing data analysis with custom-made or external tools. Interestingly, 10% of I&O members do not conduct any data analysis.

      Members are missing a formal data governance process.

      81% of surveyed I&O members do not have a formal or automated process for data governance. Ironically, 24% of members responded that they aim to have publicly accessible data-as-a-service or information repositories.

      Despite investment in data initiatives, organizations carry high levels of data debt.

      Info-Tech research, Establish Data Governance, points out that data debt, the accumulated cost associated with sub-optimal governance of data assets, is a problem for 78% of organizations.

      What the enterprise expects out of enterprise storage is much more complicated in 2023.

      Data protection and governance are non-negotiable aspects of enterprise storage, even when it’s unstructured.

      Data governance: Cornerstone of value

      SIGNALS

      Data quality is the primary driver for data governance.

      The data governance market
      is booming.

      Related Info-Tech Research

      In the 2022 Zaloni survey of data governance professionals, 71% indicated that consistent data quality was the top metric for data governance, followed by reduced time to insight and regulatory compliance.

      (Source: Zaloni DATAVERSITY, 2022)

      The Business Research Company determined that the global data governance market is expected to grow from $3.28 billion in 2022 to $7.42 billion in 2026 at a CAGR of 22.7% in response to 74 zettabytes of data in 2021, with a growth rate of 1.145 trillion MB of new data being created every day.

      (Source: Business Research Company, 2022)

      Data governance: Cornerstone of value

      CALL TO ACTION

      Develop a data governance program that includes an I&O data steward for oversight.

      I&O priority actions

      Establish an I&O data steward. Make data governance by establishing a data steward role with accountability for governance. The steward works collaboratively with DataOPs to control access to I&O data, enforce policies, and reduce the time to make use of the data.

      Define a comprehensive storage architecture. If you thought you had a data sprawl problem before, wait until you see the volume of data generated from IoT and Web 3.0 applications. Get ahead of the problem by creating an infrastructure roadmap for structured and unstructured data storage.

      Build a solid backbone for AI Operations using data quality best practices. Data quality is the foundation for generation of operational value from the data and artificial intelligence efforts. Focus on using a methodology to build a culture of data quality within I&O systems and applications that generate data rather than reactive fixes.

      Look to partner with third-party vendors for your master data management (MDM) efforts. Modern MDM vendors can work with your existing data fabrics/lake and help leverage your data governance policies into the cloud.

      Prep for a brave new metaverse

      SIGNALS

      From science fiction to science fact.

      The term metaverse was coined in 1992 by Neal Stephenson and is a common theme in science fiction. For most I&O surveyed professionals, the term metaverse conjures up more confusion than clarity, as it’s not one place, but multiple metaverse worlds. The primordial metaverse was focused on multiplayer gaming and some educational experiences. It wasn’t until recently that it gained a critical mass in the fashion and entertainment industries with the use of non-fungible tokens (NFT). The pandemic created a unique opportunity for metaverse-related technologies to expand Web 3.0.

      Related Info-Tech Research

      Prep for a brave new metaverse

      SIGNALS

      Collaboration and beyond.

      On one hand, metaverse technologies virtual reality(VR)/augmented reality (AR) headsets can be a method of collaborating internally within a single organization. About 10% of our surveyed I&O members engaged this type of collaborative metaverse in 2022, with another 24% looking to run proof of concept projects in 2023. However, there is a much larger terrain for metaverse projects outside of workforce collaboration, which 17% of surveyed I&O members are planning to engage with in 2023.

      These are sophisticated new metaverse worlds, and digital twins of production environments are being created for B2B collaboration, operations, engineering, healthcare, architecture, and education that include the use of block chain, NFTs, smart contracts, and other Web 3.0 technologies

      “They are the audiovisual bodies that people use to communicate with each other in the Metaverse.”

      Neal Stephenson,
      Snow Crash 1992

      Prep for a brave new metaverse

      SIGNALS

      Metaverse requires multidimensional security.

      Security in the context of the metaverse presents new challenges to I&O. The infrastructure that runs the metaverse is still vulnerable to “traditional” security threats. New attack vectors include financial and identity fraud, privacy and data loss, along with new cyber-physical threats which are predicted to occur as the metaverse begins to integrate with IoT and other 3D objects in the physical world.

      The ultimate in "not a product" – the metaverse promises to be a hodgepodge of badly standardized technologies for the near future.

      Be prepared to take care of pets and not cattle for the foreseeable future, but keep putting the fencing around the ranch.

      Prep for a brave new metaverse

      SIGNALS

      Generating new wave of sophisticated engineering coming.

      Economics boom around metaverse set to explode.

      Related Info-Tech Research

      Beyond the current online educational resources, there are reputable universities around the world, including Stanford University, that are offering courses on metaverse and Web 3.0 concepts.

      (Source: Arti, 2022)

      So, what’s providing the impetus for all this activity and investment? Economics. In their 2022 report, Metaverse and Money, Citi estimated that the economic value of the metaverse(s) will have 900M to 1B VR/AR users and 5 billion Web 3.0 users with market sizes of $1-2T and $8-$13T, respectively. Yes, that’s a “T” for Trillions.

      (Source: Ghose, 2022)

      Prep for a brave new metaverse

      CALL TO ACTION

      Ready or not, the metaverse is coming to an infrastructure near you. Start expanding I&O technologies and processes to support a metaverse infrastructure.

      I&O priority actions

      Develop a plan for network upgrades.

      A truly immersive VR/AR experience requires very low latency. Identify gaps and develop a plan to enhance your network infrastructure surrounding your metaverse space(s) and end users.

      Extend security posture into the metaverse.

      Securing the infrastructure that runs your metaverse is going to extend the end-user equipment used to navigate it. More importantly, security policies need to encompass the avatars that navigate it and the spatial web that they interact with, which can include physical world items like IoT.

      Prep for a brave new metaverse

      I&O priority actions

      Metaverse theft prevention

      Leverage existing strategies to identify management in the metaverse. Privacy policies need to extend their focus to data loss prevention within the metaverse.

      Collaborate

      The skill set required to build, deploy, manage, and support the metaverse is complex. Develop a metaverse support organization that extends beyond I&O functions into security, DevOps, and end-user experiences.

      Educate

      Web 3.0 technologies and business models are complex. Education of I&O technical- and commerce-focused team members is going to help prevent you from getting blindsided. Seek out specialized training programs for technical staff and strategic education for executives, like the Wharton School of Business certification program.

      Authors

      John Annand

      Theo Antoniadis

      John Annand

      Principal Research Director

      Theo Antoniadis

      Principal Research Director

      Contributors

      Paul Sparks,
      CTO at Brookshire Grocery Company

      2 Anonymous Contributors

      Figuring out the true nature of the “Turbo” button of his 486DX100 launched John on a 20-year career in managed services and solution architecture, exploring the secrets of HPC, virtualization, and DIY WANs built with banks of USR TotalControl modems. Today he focuses his research and advisory on software-defined infrastructure technologies, strategy, organization, and service design in an increasingly Agile and DevOps world.

      Theo has decades of operational and project management experience with start-ups and multinationals across North America and Europe. He has held various consulting, IT management and operations leadership positions within telecommunications, SaaS, and software companies.

      Bibliography

      “3 Cybersecurity Trends that are Changing Financial Data Management." FIMA US. Accessed August 2022.
      Arti. “While much of the world is just discovering the Metaverse, a number of universities have already established centers for studying Web 3." Analytics Insight. 10 July 2022.
      “Artificial intelligence (AI) for cybersecurity." IBM. Accessed September 2022
      “Business in the Metaverse Economy." Wharton School of University of Pennsylvania. Accessed October 2022.
      “Cost of a data breach 2022: A million-dollar race to detect and respond." IBM. Accessed September 2022.
      “Countries affected by mandatory ESG reporting – here’s the list." New Zealand Ministry of Business, Innovation & Employment. Accessed September 2022.
      “Countries affected by mandatory ESG reporting – here’s the list.” WorldFavor. Accessed September 2022.
      Crenshaw, Caroline A. “SEC Proposes to Enhance Disclosures by Certain Investment Advisers and Investment Companies About ESG Investment Practices." U.S. Securities and Exchange Commission. May 2022.
      “Cutting through the metaverse hype: Practical guidance and use cases for business." Avanade. Accessed October 2022.
      “Data Governance Global Market Sees Growth Rate Of 25% Through 2022." The Business Research Company. August 2022.
      “DIRECTIVE 2014/95/EU OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 22 October 2014 amending Directive 2013/34/EU as regards disclosure of non-financial and diversity information by certain large undertakings and groups." UER-Lex. Accessed September 2022.
      "Ethically Aligned Design: A Vision for Prioritizing Human Well-being with Autonomous and Intelligent Systems." IEEE. March 2019.
      “European Parliament resolution of 20 October 2020 with recommendations to the Commission on a civil liability regime for artificial intelligence." European Parliament. Accessed October 2022.
      Ghose, Ronit et al. "Metaverse and Money." Citi GPS. March 2022.
      Hernandez, Roberto, et al. “Demystifying the metaverse." PWC. Accessed August 2022.
      Info-Tech Trends Report Survey, 2023; N=813.
      “ISO 14000 Family: Environmental Management." ISO. Accessed October 2022.
      Knight, Michelle & Bishop, Annie, ”The 2022 State of Cloud Data Governance.“ Zaloni DATAVERSITY. 2022.

      Bibliography

      Kompella, Kashyap, “What is AI governance and why do you need it?“ TechTarget. March 2022.
      “Management of electronic waste worldwide in 2019, by method." Statista. 2022.
      “Model Artificial Intelligence Governance Framework and Assessment Guide.“ World Economic Forum. Accessed September 2022.
      “Model Artificial Intelligence Governance Framework." PDPC Singapore. Accessed October 2022.
      “New rules on corporate sustainability reporting: provisional political agreement between the Council and the European Parliament.“ European Council. June 2022.
      "OECD Economic Outlook Volume 2022." OECD iLibrary. June 2022.
      "Recommendations of the Task Force on Climate-related Financial Disclosures." TCFD. Accessed August 2022.
      “Risk of Global Recession in 2023 Rises Amid Simultaneous Rate Hikes.” World Bank Organization. September 2022.
      Sautner, Zacharias, et al. “The Effects of Mandatory ESG Disclosure around the World.” SSRN. November 2021.
      Sondergaard, Peter. “AI GOVERNANCE – WHAT ARE THE KPIS? AND WHO IS ACCOUNTABLE?“ The Sondergaard Group. November 2019.
      Srivastavam Sudeep, “How can your business enter the Metaverse?." Appinventiv.
      September 2022.
      “Standards Overview." SASB. Accessed October 2022.
      Stephenson, Neal. Snow Crash. Bantam Books, 1992.
      “Sustainability Reporting Standards." Global Reporting Initiative. Accessed October 2022.
      “The Ten Principles of the UN Global Compact." UN Global Compact. Accessed October 2022.
      Tian Tong Lee, Sheryl. "China Unveils ESG Reporting Guidelines to Catch Peers.” Bloomberg. May 2022.
      “What are the Principles for Responsible Investment?" UNPRI. Accessed October 2022.
      "What is the EU's Corporate Sustainability Reporting Directive (CSRD)?" WorldFavor.
      June 2022.
      West, Darrell M. “Six Steps to Responsible AI in the Federal Government.“ Brookings Institution. March 2022. Web.

      Establish a Communication and Collaboration System Strategy

      • Buy Link or Shortcode: {j2store}293|cart{/j2store}
      • member rating overall impact: 9.3/10 Overall Impact
      • member rating average dollars saved: $6,459 Average $ Saved
      • member rating average days saved: 10 Average Days Saved
      • Parent Category Name: End-User Computing Applications
      • Parent Category Link: /end-user-computing-applications
      • Communication and collaboration portfolios are overburdened with redundant and overlapping services. Between Office 365, Slack, Jabber, and WebEx, IT is supporting a collection of redundant apps. This redundancy takes a toll on IT, and on the user.
      • Shadow IT is easier than ever, and cheap sharing tools are viral. Users are literally carrying around computers in their pockets (in the form of smartphones). IT often has no visibility into how these devices – and the applications on them – are used for work.

      Our Advice

      Critical Insight

      • You don’t know what you don’t know. Unstructured conversations with users will uncover insights.
      • Security is meaningless without usability. If security controls make a tool unusable, then users will rush to adopt something that’s free and easy.
      • Training users on a new tool once isn’t effective. Engage with users throughout the collaboration tool’s lifecycle.

      Impact and Result

      • Few supported apps and fewer unsupported apps. This will occur by ensuring that your collaboration tools will be useful to and used by users. Give users a say through surveys, focus groups, and job shadowing.
      • Lower total cost of ownership and greater productivity. Having fewer apps in the workplace, and better utilizing the functionality of those apps, will mean that IT can be much more efficient at managing your ECS.
      • Higher end-user satisfaction. Tools will be better suited to users’ needs, and users will feel heard by IT.

      Establish a Communication and Collaboration System Strategy Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should develop a new approach to communication and collaboration apps, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Create a shared vision on the future of communication and collaboration

      Identify and validate goals and collaboration tools that are used by your users, and the collaboration capabilities that must be supported by your desired ECS.

      • Establish a Communication and Collaboration System Strategy – Phase 1: Create a Shared Vision on the Future of Communication and Collaboration
      • Enterprise Collaboration Strategy Template
      • Building Company Communication and Collaboration Technology Improvement Plan Executive Presentation
      • Communications Infrastructure Stakeholder Focus Group Guide
      • Enterprise Communication and Collaboration System Business Requirements Document

      2. Map a path forward

      Map a path forward by creating a collaboration capability map and documenting your ECS requirements.

      • Establish a Communication and Collaboration System Strategy – Phase 2: Map a Path Forward
      • Collaboration Capability Map

      3. Build an IT and end-user engagement plan

      Effectively engage everyone to ensure the adoption of your new ECS. Engagement is crucial to the overall success of your project.

      • Establish a Communication and Collaboration System Strategy – Phase 3: Proselytize the Change
      • Collaboration Business Analyst
      • Building Company Exemplar Collaboration Marketing One-Pager Materials
      • Communication and Collaboration Strategy Communication Plan
      [infographic]

      Workshop: Establish a Communication and Collaboration System Strategy

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Identify What Needs to Change

      The Purpose

      Create a vision for the future of your ECS.

      Key Benefits Achieved

      Validate and bolster your strategy by involving your end users.

      Activities

      1.1 Prioritize Components of Your ECS Strategy to Improve

      1.2 Create a Plan to Gather Requirements From End Users

      1.3 Brainstorm the Collaboration Services That Are Used by Your Users

      1.4 Focus Group

      Outputs

      Defined vision and mission statements

      Principles for your ECS

      ECS goals

      End-user engagement plan

      Focus group results

      ECS executive presentation

      ECS strategy

      2 Map Out the Change

      The Purpose

      Streamline your collaboration service portfolio.

      Key Benefits Achieved

      Documented the business requirements for your collaboration services.

      Reduced the number of supported tools.

      Increased the effectiveness of training and enhancements.

      Activities

      2.1 Create a Current-State Collaboration Capability Map

      2.2 Build a Roadmap for Desired Changes

      2.3 Create a Future-State Capability Map

      2.4 Identify Business Requirements

      2.5 Identify Use Requirements and User Processes

      2.6 Document Non-Functional Requirements

      2.7 Document Functional Requirements

      2.8 Build a Risk Register

      Outputs

      Current-state collaboration capability map

      ECS roadmap

      Future-state collaboration capability map

      ECS business requirements document

      3 Proselytize the Change

      The Purpose

      Ensure the system is supported effectively by IT and adopted widely by end users.

      Key Benefits Achieved

      Unlock the potential of your ECS.

      Stay on top of security and industry good practices.

      Greater end-user awareness and adoption.

      Activities

      3.1 Develop an IT Training Plan

      3.2 Develop a Communications Plan

      3.3 Create Initial Marketing Material

      Outputs

      IT training plan

      Communications plan

      App marketing one-pagers

      Initiate Your Service Management Program

      • Buy Link or Shortcode: {j2store}398|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Service Management
      • Parent Category Link: /service-management
      • IT organizations continue attempting to implement service management, often based on ITIL, with limited success and without visible value.
      • More than half of service management implementations have failed beyond simply implementing the service desk and the incident, change, and request management processes.
      • Organizational structure, goals, and cultural factors are not considered during service management implementation and improvement.
      • The business lacks engagement and understanding of service management.

      Our Advice

      Critical Insight

      • Service management is an organizational approach. Focus on producing successful and valuable services and service outcomes for the customers.
      • All areas of the organization are accountable for governing and executing service management. Ensure that you create a service management strategy that improves business outcomes and provides the value and quality expected.

      Impact and Result

      • Identified structure for how your service management model should be run and governed.
      • Identified forces that impact your ability to oversee and drive service management success.
      • Mitigation approach to restraining forces.

      Initiate Your Service Management Program Research & Tools

      Start here – read the Executive Brief

      Read this Executive Brief to understand why service management implementations often fail and why you should establish governance for service management.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Identify the level of oversight you need

      Use Info-Tech’s methodology to establish an effective service management program with proper oversight.

      • Service Management Program Initiation Plan
      [infographic]

      Improve Incident and Problem Management

      • Buy Link or Shortcode: {j2store}290|cart{/j2store}
      • member rating overall impact: 9.6/10 Overall Impact
      • member rating average dollars saved: $43,761 Average $ Saved
      • member rating average days saved: 23 Average Days Saved
      • Parent Category Name: Incident and problem management
      • Parent Category Link: /improve-your-core-processes/infra-and-operations/i-and-o-process-management/incident-and-problem-management
      • IT infrastructure managers have conflicting accountabilities. It can be difficult to fight fires as they appear while engaging in systematic fire prevention.
      • Repetitive interruptions erode faith in IT. If incidents recur consistently, why should the business trust IT to resolve them?

      Continue reading

      Build Better Workflows

      • Buy Link or Shortcode: {j2store}496|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Service Desk
      • Parent Category Link: /service-desk

      Do you experience any of the following challenges:

      • You lack process documentation.
      • Your documentation lacks flowchart examples.
      • Your workflows have points of friction and need improvement.

      Our Advice

      Critical Insight

      • Don’t just document – target your future state as you document your workflows.
      • Find opportunities for automation, pinpoint key handoff points, and turn cold handoffs into warm handoffs

      Impact and Result

      • Understand the basics of documenting a workflow in flowchart format.
      • Run activities to revise and stress-test your workflows to improve their accuracy and effectiveness.
      • Ensure your workflows are part of a continuous improvement cycle – keep them up to date as a living document.

      Build Better Workflows Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Build Better Workflows – A step by step document that walks you through the process of convening a working group to design and update a process flowchart.

      Ask the right questions and pressure test the workflow so the documentation is as helpful as possible to all who consult it.

      • Build Better Workflows Storyboard

      2. Workflow Activity: An onboarding example for a completed flowchart review.

      Use this workflow as an example of the output of an onboarding workflow-improvement activity.

      • Workflow Activity: Onboarding Example (Visio)
      • Workflow Activity: Onboarding Example (PDF)
      [infographic]

      Further reading

      Build Better Workflows

      Go beyond draft one to refine and pressure test your process.

      Analyst Perspective

      Remove friction as you document workflows

      Emily Sugerman

      Emily Sugerman
      Research Analyst, Infrastructure & Operations

      Info-Tech Research Group

      You can’t mature processes without also documenting them. Process documentation is most effective when workflows are both written out and also visualized in the form of flow charts.

      Your workflows may appear in standard operating procedures, in business continuity and disaster recovery plans, or anywhere else a process’ steps need to be made explicit. Often, just getting something down on paper is a win. However, the best workflows usually do not emerge fully-formed out of a first draft. Your workflow documentation must achieve two things:

      • Be an accurate representation of how you currently operate or how you will operate in the near future as a target state.
      • Be the output of a series of refinements and improvements as the workflow is reviewed and iterated.

      This research will use the example of improving an onboarding workflow. Ask the right questions and pressure test the workflow so the documentation is as helpful as possible to all who consult it.

      Executive Summary

      Your Challenge

      Common Obstacles

      Info-Tech’s Approach

      • Your documentation lacks workflows entirely, or ...
      • Your workflows are documented in flowchart form but are not accurate, and/or ...
      • Your workflows are documented in flowchart form but contain points of friction and need process improvement.
      • Getting the relevant stakeholders together to contribute to workflow design and validate them.
      • Selecting the right detail level to include in the workflow – not too much and not too little.
      • Knowing the right questions to ask to review and improve your workflow flowcharts.

      Use this material to help

      • Understand the basics of documenting a workflow in flowchart format.
      • Run activities to revise and stress-test your workflows to improve their accuracy and effectiveness.
      • Ensure your workflows are part of a continuous improvement cycle – keep them up-to-date as a living document.

      Info-Tech Insight

      Don’t just document – target your future state as you document your workflows. Find opportunities for automation, pinpoint key handoff points, and turn cold handoffs into warm handoffs.

      Follow these steps to build, analyze, and improve the workflow

      The image contains a screenshot of a diagram that demonstrates the steps needed to build better workflows.

      Insight Summary

      Keep future state in mind.
      Don’t just document – target your future state as you document your workflows. Find opportunities for automation, pinpoint key handoff points, and turn cold handoffs into warm handoffs.

      Promote the benefits of documenting workflows as flowcharts.
      Foreground to the IT team how this will improve customer experience. End-users will benefit from more efficient workflows.

      Remember the principle of constructive criticism.
      Don’t be afraid to critique the workflow but remember this can be a team-building experience. Focus on how these changes will be mutually beneficial, not assigning blame for workflow friction.

      Don’t waste time building shelfware.
      Establish a review cadence to ensure the flowchart is a living document that people actually use.

      Benefits of building better workflows

      Risks of inadequate workflows

      Benefits of documented workflows

      • Lack of clear communication: If you don’t have workflows, you are losing out on an effective way to document and communicate processes.
      • Outdated documentation: If you do have workflows documented in standard operating procedures, they probably need to be updated unless you already consistently update documentation.
      • Facilitate knowledge transfer.
      • Standardize processes for service delivery consistency.
      • Optimize processes by discovering and improving points of friction within the workflow.
      • Improve transparency of processes to set expectations for other stakeholders.
      • Reduce risk.

      Why are visualized workflows useful?

      Use these talking points to build commitment toward documenting/updating processes.

      Risk reduction
      “Our outdated documentation is a risk, as people will assume the documented process is accurate.”

      Transparency
      “The activity of mapping our processes will bring transparency to everyone involved.”

      Accountability
      “Flow charts will help us clarify task ownership at a glance.”

      Accessibility
      “Some team members prefer diagrams over written steps, so we should provide both.”

      Knowledge centralization
      “Our flow charts will include links to other supporting documentation (checklists, vendor documentation, other flowcharts).”

      Role clarification
      “Separating steps into swim lanes can clarify different tiers, process stages, and ownership, while breaking down silos.”

      Communication
      To leadership/upper management: “This process flow chart quickly depicts the big picture.”

      Knowledge transfer
      “Flow charts will help bring new staff up to speed more quickly.”

      Consistency
      “Documenting a process standardizes it and enables everyone to do it in the same way.”

      Review what process mapping is

      A pictorial representation of a process that is used to achieve transparency.

      This research will use one specific example of an onboarding process workflow. Before drilling down into onboarding workflows specifically, review Info-Tech’s Process Mapping Guide for general guidance on what to do before you begin:

      • Know the purpose of process mapping.
      • Articulate the benefits of process mapping.
      • Recognize the risks of not process mapping.
      • Understand the different levels of processes.
      • Adopt BPMN 2.0 as a standard.
      • Consider tools for process mapping.
      • Select a process to map.
      • Learn methods to gather information.

      The image contains screenshots of the Process Mapping Guide.

      Download the Process Mapping Guide

      Select the workflow your team will focus upon

      Good candidates include:

      • Processes you don’t have documented and need to build from scratch.
      • An existing process that results in an output your users are currently dissatisfied with (if you run an annual IT satisfaction survey, use this data to find this information).
      • An existing process that is overly manual, lacks automation, and causes work slowdown for your staff.

      Info-Tech workflow examples

      Active Directory Processes

      Application Development Process

      Application Maintenance Process

      Backup Process

      Benefits Legitimacy Workflow

      Business Continuity Plan Business Process

      Business Continuity Plan Recovery Process

      Commitment Purchasing Workflow

      Coordinated Vulnerability Disclosure Process

      Crisis Management Process

      Data Protection Recovery Workflow

      Disaster Recovery Process

      Disaster Recovery Plan/Business Continuity Plan Review Workflow

      End-User Device Management Workflow Library

      Expense Process

      Event Management Process

      Incident Management and Service Desk Workflows

      MACD Workflow Mapping

      Problem Management Process

      Project Management Process

      Ransomware Response Process

      Sales Process for New Clients

      Security Policy Exception Process

      Self-Service Resolution Process

      Service Definition Process

      Service Desk Ticket Intake by Channel

      Software Asset Management Processes

      Target State Maintenance Workflow

      Example: Onboarding workflow

      Onboarding is a perennial challenge due to the large number of separate teams and departments who are implicated in the process.

      There can be resistance to alignment. As a result, everyone needs to be pulled in to see the big picture and the impact of an overly manual and disconnected process.

      Additionally, the quality of the overall onboarding process (of which IT is but one part) has a significant impact on the employee experience of new hires, and the long-term experience of those employees. This workflow is therefore often a good one to target for improvement.

      “Organizations with a standardized onboarding process experience 62% greater new hire productivity, along with 50% greater new hire retention.”1

      “Companies that focus on onboarding retain 50% more new employees than companies that don’t.”2

      1. Carucci, “To Retain New Hires, Spend More Time Onboarding Them,” 2018
      2. Uzialko, “What Does Poor Onboarding, 2023

      Tabletop exercise: Generate first draft

      In the tabletop exercise, your team will walk through your onboarding process step by step and document what happens at each stage. Prep for this meeting with the following steps:

      1. Identify roles: facilitator, notetaker, and participants. Determine who should be involved in the working group in addition to IT (HR, Hiring Team, Facilities, etc.).
      2. Decide what method of documentation you will use in the meeting. If meeting in person, cue cards are useful because they can be easily rearranged or inserted. If meeting remotely, the notetaker or facilitator will need to share their screen and capture each step with software (such as Visio, PowerPoint, or a whiteboarding software).
      3. Before you even begin mapping out the process, conduct a quick brainstorming session. What are your current challenges with it? What is working? Document on a whiteboard (electronic or hard copy).
      4. Document each step of the process as it currently happens. You will improve it later. Include task ownership.

      Roles

      Facilitator
      Tasks:

      • Guide discussion – restate contributors’ ideas, ask probing questions.
      • Keep group on track – cut off or redirect conversation when off track.

      Notetaker
      Tasks:

      • Ensure the steps are documented via the agreed-upon tools (e.g. cue cards). If the process is being documented in software, the notetaker may be solely responsible for documentation.
      • The notetaker may be the same person as the facilitator.

      Document your workflow challenges: Onboarding

      Brainstorm and document. Group similar challenges together to pull out themes.

      Lack of communication/expectation setting with users:

      Messy process, poor coordination among task owners:

      User experience affected:

      • Users submit onboarding requests with too little lead time.
      • HR/hiring manager does not include all necessary information when submitting new hire request.
      • Approvals are slowing down our ability to fulfill in a timely manner.
      • Lots of manual, repeated tasks.
      • Too much back and forth between technicians.
      • Procurement delays (supply chain challenges) leading to new user starting with no device/workaround.
      • Inconsistent resolution times for these types of requests.
      • Complaints about onboarding were one of the most frequently recurring issues in our most recent annual IT satisfaction survey.
      • Some of these complaints fall more to the responsibility of HR and direct managers, but some of the complaints relate to onboarding tasks not being completed by start date, which is our responsibility.

      Establish flowcharting standards

      If you don’t have existing flowchart standards, use the basic notation conventions used in the examples here.

      Basic notation convention shapes: Circle, oval, square, rectangle, diamond, thought bubble.

      Start, End, and Connector. Traditional flowcharting standards reserve this shape for connectors to other flowcharts or other points in the existing flowchart. Unified modeling language (UML) also uses the circle for start and end points.

      Start, End. Traditional flowcharting standards use this for start and end. However, Info-Tech recommends using the circle shape to reduce the number of shapes and avoid confusion with other similar shapes.

      Process Step. Individual process steps or activities (e.g. create ticket or escalate ticket). If it’s a series of steps, then use the sub-process symbol and flowchart the sub-process separately.

      Sub-Process. A series of steps. For example, a critical incident standard operating procedure (SOP) might reference a recovery process as one of the possible actions. Marking it as a sub-process, rather than listing each step within the critical incident SOP, streamlines the flowchart and avoids overlap with other flowcharts (e.g. the recovery process).

      Decision. Represents decision points, typically with yes/no branches, but you could have other branches depending on the question (e.g. a “Priority” question could branch into separate streams for Priority 1, 2, 3, 4, and 5 issues).

      Document/Report Output. For example, the output from a backup process might include an error log.

      Map the current process

      Prompt the working group with the following questions.

      • What happens when the ticket comes in? Who submits it? Where is it coming from? What are the trigger events? Are there any input channels we should eliminate?
      • What is the terminal event? Where does the workflow end?
      • Do we have a triage step?
      • Is the ticket prioritized? Does this need to be a step?
      • Do we create child tickets? Separate tasks for different teams? Do we create a primary/main ticket and sub-tickets? How should we represent this in the flowchart?
      • How should we represent escalations? How should we represent task ownership by different teams?
      • What are our decision points: points when the path can potentially branch (e.g. into yes/no branches)?

      Map the process: First pass

      The image contains a screenshot example of the first pass.

      Tabletop exercise: Revise workflow

      Time to review and revise the workflow. What gaps exist? How can you improve the process? What documentation gaps have been overlooked?

      Consider the following refinements for the onboarding workflow:

      • Identify missing steps
      • Clearly identify task ownership
      • Establish SLAs and timepoints
      • Capture/implement user feedback
      • Identify approval roadblocks
      • Identify communication points
      • Identify opportunities for automation
      • Create personas
      • Create onboarding checklist

      Roles

      Facilitator
      Tasks:

      • Guide discussion – restate contributors’ ideas, ask probing questions.
      • Keep group on track – cut off or redirect conversation when off track.

      Notetaker
      Tasks:

      • Ensure the steps are documented via the agreed-upon tools (e.g. cue cards). If the process is being documented in software, the notetaker may be solely responsible for documentation.
      • The notetaker may be the same person as the facilitator, but this takes some practice.

      Map the process: Critique draft

      The image contains a screenshot example of critique draft.

      Solicit feedback from the group.

      "

      • Our workflow is slowed down by hidden approvals that we haven’t mapped.
      • We have no efficient way to prevent submission of incomplete requests.
      • Our workflow doesn’t clearly show how different tasks are assigned to different teams.
      • We still don’t know how long this all takes.
      • We’re missing some tasks – what about including facilities?
      • We’re missing next steps for some of the decision points.
      "

      Review: Identify missing steps

      Consider the following refinements.

      Be complete.

      The workflow should surface tacit knowledge, so make it explicit (Haddadpoor et al.):

      • Where are the inputs coming from? Do you need to account for various input channels? Have you forgotten any?
      • Are there any input channels that you want to eliminate?
      • Have you overlooked any hardware, software, or services entitlements that should be called out?
      • Have all decision paths been worked through? Do you need to add any missing decision points?
      • Add information flows and annotations as needed.

      Review: Task ownership

      Identify task ownership.

      The flow chart will be more useful if it clearly identifies who does what in the process.

      • Consider organizing the sub-processes within the overall onboarding process into swim lanes, one for each team or group involved in the process.
      • Swim lanes help clarify who does what in the overall process (e.g. all the tasks completed by HR appear in the HR swim lane, all the tasks completed by service desk appear in the service desk swim lane).
      • They can also help draw attention to escalation points or handoff points between different teams. Assess the steps around the boundary of each swim lane. Does the working group experience/know of friction at these handoff points? What might solve it?
      • In what order should the tasks occur? What dependencies do they have?

      The image contains a screenshot of a model that demonstrates task ownership swim lanes.

      “Each task has an owner, and the task list is visible to the employee and other stakeholders, so there's visibility about whether each person has done their actions.”

      Matthew Stibbe, qtd. in Zapier, 2022

      Review: The time the workflow takes

      For onboarding, this means setting SLOs/SLAs and internal timepoints.

      Add internal timepoints for the major steps/tasks in the workflow. Begin to track these service level objectives and adjust as necessary.

      • Review old onboarding tickets and track how long each main step/task takes (or should take). Every additional approval risks adding days.
      • Consider where there are opportunities to increase automation or use templates to save time.
      • Zero in on which task within the onboarding workflow is slowing down the process.
      • Create an overall service level objective that communicates how many days the onboarding workflow is expected to take. Decide where escalations go when the SLA is breached.

      When you have validated the service level objectives are accurate and you can meet them an acceptable amount of time, communicate the overall SLA to your users. This will ensure they submit future onboarding requests to your team with enough lead time to fulfill the request. Try to place the SLA directly in the service catalog.

      “Tracking the time within the workflow can be a powerful way to show the working group why there is user dissatisfaction.”

      Sandi Conrad, Principal Advisory Director, Info-Tech Research Group

      Review: Capture user feedback

      For onboarding, this means implementing a transactional survey.

      The onboarding workflow will be subject to periodic reviews and continual improvement. Suggestions for improvement should come not only from the internal IT team, but also the users themselves.

      • Transactional surveys, launched at the close of a ticket, allow the ticket submitter to provide feedback on their customer service experience.
      • Onboarding tickets are somewhat more complex than the average incident or service request, since the ticket is often opened by one user (e.g. in HR) on behalf of another (the new employee).
      • Decide whose experience you want feedback on – the submitter of the request or the new user. Investigate your ITSM tool’s capabilities: is it possible to direct the survey to someone who is not the ticket submitter?
      Take Action on Service Desk Customer Feedback

      Use Info-Tech’s Take Action on Service Desk Customer Feedback for more guidance on creating these surveys.

      Review: Identify approval roadblocks

      For onboarding, approvals can be the main roadblock to fulfilling requests

      • How are the requests coming in? Do we have a predefined service catalog?
      • What kinds of approvals do we receive (manager, financial, legal, security, regulatory)? Ask the team to think about where there are instances of back and forth and clean that up.
      • Identify where approvals interrupt the technical flow.
        • Confirm that these approvals are indeed necessary (e.g. are certain approval requests ever declined? If not, follow up on whether they are necessary or whether some can be made into preapprovals).
        • Avoid putting agents in charge of waiting on or following up about approvals.
        • Investigate whether interruptive approvals can be moved.

      Review: Identify communication points

      A positive onboarding experience is an important part of a new employee’s success.

      Though IT is only one part of an employee’s onboarding experience, it’s an important part. Delays for hardware procurement and a lack of communication can lead to employee disengagement. Ask the team:

      • Are we communicating with our users when delays occur? When do delays occur most often?
      • How can we mitigate delays? Though we can’t resolve larger supply chain problems, can we increase stock in the meantime?
      • Can we start tracking delays to incorporate into the SLA
      • Do we offer loaner devices in the meantime?

      Place communication bullet points in the flow chart to indicate where the team will reach out to users to update or notify them of delays.

      Review: Identify opportunities for automation

      Where can we automate for onboarding?

      Identify when the process is dragged out due to waiting times (e.g. times when the technician can’t address the ticket right away).

      • Analyze the workflow to identify which tasks tend to stagnate because technician is busy elsewhere. Are these candidates for automation?
      • Is our ITSM tool capable of setting up automatically routed child tickets triggered by the main onboarding ticket? Does it generate a series of tasks? Is it a manual process? Which teams do these tasks/tickets go to?
      • Can we automate notifications if devices are delayed?
      • Can we use mobile device management for automated software installation?
      • If we have a robust service catalog, can we provide it to the users to download what they need? Or is this too many extra steps for our users?
      • Can we create personas to speed up onboarding?

      Avoid reinforcing manual processes, which make it even harder for departmental silos to work together.

      Review: Automation example – create personas

      Create role-based templates.

      Does HR know which applications our users need? Are they deferring to the manager, who then asks IT to simply duplicate an existing user?

      Personas are asset profiles that apply to multiple users (e.g. in a department) and that can be easily duplicated for new hires. You might create three persona groups in a department, with variations within each subgroup or title. To do this, you need accurate information upfront.

      Then, if you’re doing zero touch deployment, you can automate software to automatically load.

      Many HRIS systems have the ability to create a persona, and also to add users to the AD, email, and distribution groups without IT getting involved. This can alleviate work from the sysadmin. Does our HRIS do this?

      • Review old onboarding tickets. Do they include manual steps like setting up mailboxes, creating user accounts, adding to groups?
      • Investigate your ITSM tool’s onboarding template. Does it allow you to create a form through which to create dynamic required fields?
      • Identify the key information service desk needs from the department supervisor, or equivalent role, to begin the onboarding request – employee type, access level, hardware and software entitlements, etc.

      Revised workflow

      How does the group feel about the revised workflow?

      • Are any outputs still missing?
      • Can we add any more annotations to provide more context to someone reading this for the first time?
      • Do the task names follow a “verb-noun” format?
      • Are the handoffs clear?
      • Are some of the steps overly detailed compared to others?
      • Does it help resolve the challenges we listed?
      • Does it achieve the benefits we want to achieve?

      Download the Workflow Activity: Onboarding Example

      Remember the principle of constructive criticism.

      Don’t be afraid to critique the workflow but remember this can also be a team-building experience. Focus on how these changes will be mutually beneficial, not assigning blame for workflow friction.

      Post-review: Revised workflow

      The image contains a screenshot example of a revised workflow.

      Final check

      • Do we need to run this by Legal?
      • Have we included too many sub-processes? Not enough?
      • Is the flowchart easy to read and follow?

      Decide how often this workflow will be revised.

      • Is this workflow part of a larger piece of documentation that has a set review cadence? Where is it stored?
      • If not, what is a realistic time frame for regular review?
      • Who will own this process in an ongoing way and be in charge of convening a future review working group?

      Validation with stakeholders

      • What documentation does the flowchart belong to? When will you review it again?
      • Who do you need to validate the flowchart with?

      Share the flowchart and set up a review meeting.

      • Walk through the workflow with stakeholders who did not participate in building it.
      • Do they find it easy to follow?
      • Can they identify missing steps?

      Don’t waste time building shelfware.

      Establish a review cadence to ensure the flowchart is a living document that people actually use.

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

      Guided Implementation

      “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”

      Workshop

      “We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”

      Consulting

      “Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

      Diagnostics and consistent frameworks used throughout all four options

      Bibliography

      Bushkill, Claire. “The top 5 ways to automate your onboarding checklist.” Rippling Blog. 18 Mar 2022. Accessed 29 Nov 2022. Ha https://www.rippling.com/blog/the-top-5-ways-to-automate-your-onboarding-checklist
      Carucci, Ron. “To Retain New Hires, Spend More Time Onboarding Them.” Harvard Business Review, 3 Dec 2018
      Haddadpoor, Asefeh, et al. “Process Documentation: A Model for Knowledge Management in Organizations.” Materia Socio-Medica, vol. 27, no. 5, Oct. 2015, pp. 347–50. PubMed Central, https://doi.org/10.5455/msm.2015.27.347-350.
      King, Melissa. “New hire checklist: An employee onboarding checklist template for 2022.” Zapier. 14 Jul 2022. Accessed 29 Nov 2022. https://zapier.com/blog/onboarding-checklist/
      Uzialko, Adam. “What Does Poor Onboarding Really Do to Your Team?” Business News Daily. 23 Jan 2023.
      https://www.manageengine.com/products/service-desk...

      Contributors

      Sandi Conrad, Principal Advisory Director, Infrastructure and Operations, Info-Tech Research Group

      Christine Coz, Executive Counselor, Info-Tech Research Group

      Allison Kinnaird, Practice Lead, Infrastructure and Operations, Info-Tech Research Group

      Natalie Sansone, Research Director, Infrastructure and Operations, Info-Tech Research Group

      The Essential COVID-19 Childcare Policy for Every Organization, Yesterday

      • Buy Link or Shortcode: {j2store}598|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Manage & Coach
      • Parent Category Link: /manage-coach
      • Helping employees navigate personal and business responsibilities to find solutions that ensure both are taken care of.
      • Reducing potential disruption to business operations through employee absenteeism due to increased care-provider responsibilities.

      Our Advice

      Critical Insight

      • Remote work is complicated by children at home with school closures. Implement alternative temporary work arrangements that allow and support employees to balance work and personal obligations.
      • Adjustments to work arrangements and pay may be necessary. Temporary work arrangements while caring for dependents over a longer-term pandemic may require adjustments to the duties carried out, number of hours worked, and adjustments to employee pay.
      • Managing remotely is more than staying in touch by phone. As a leader you will need to provide clear options that provide solutions to your employees to avoid them getting overwhelmed while taking care of the business to ensure there is a business long term.

      Impact and Result

      • Develop a policy that provides parameters around mutually agreed adjustments to performance levels while balancing dependent care with work during a pandemic.
      • Take care of the business through clear guidelines on compensation while taking care of the health and wellness of your people.
      • Develop detailed work-from-home plans that lessen disruption to your work while taking care of children or aged parents.

      The Essential COVID-19 Childcare Policy for Every Organization, Yesterday Research & Tools

      Start here. Read The Essential COVID-19 Childcare Policy for Every Organization, Yesterday

      Read our recommendations and follow the steps to develop a policy that will help your employees work productively while managing care-provider responsibilities at home.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      • The Essential COVID-19 Childcare Policy for Every Organization, Yesterday Storyboard
      • Pandemic Dependent Care Policy
      • COVID-19 Dependent Care Policy Manager Action Toolkit
      • COVID-19 Dependent Care Policy Employee Guide
      • Dependent-Flextime Agreement Template
      • Workforce Planning Tool
      • Nine Ways to Support Working Caregivers Today
      • Employee Resource Group (ERG) Charter Template
      [infographic]

      The First 100 Days As CIO

      • Buy Link or Shortcode: {j2store}540|cart{/j2store}
      • member rating overall impact: 9.2/10 Overall Impact
      • member rating average dollars saved: $54,525 Average $ Saved
      • member rating average days saved: 26 Average Days Saved
      • Parent Category Name: High Impact Leadership
      • Parent Category Link: /lead
      • You’ve been promoted from within to the role of CIO.
      • You’ve been hired externally to take on the role of CIO.

      Our Advice

      Critical Insight

      • Foundational understanding must be achieved before you start. Hit the ground running before day one by using company documents and initial discussions to pin down the company’s type and mode.
      • Listen before you act (usually). In most situations, executives benefit from listening to peers and staff before taking action.
      • Identify quick wins early and often. Fix problems as soon as you recognize them to set the tone for your tenure.

      Impact and Result

      • Collaborate to collect the details needed to identify the right mode for your organization and determine how it will influence your plan.
      • Use Info-Tech’s diagnostic tools to align your vision with that of business executives and form a baseline for future reference.

      The First 100 Days As CIO Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why the first 100 days of being a new executive is a crucial time that requires the right balance of listening with taking action. See how seven calls with an executive advisor will guide you through this period.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Check in with your executive advisor over seven calls

      Organize your first 100 days as CIO into activities completed within two-week periods, aided by the guidance of an executive advisor.

      • The First 100 Days As CIO – Storyboard
      • Organizational Catalog
      • Cultural Archetype Calculator
      • IT Capability Assessment

      2. Communicate your plan to your manager

      Communicate your strategy with a presentation deck that you will complete in collaboration with Info-Tech advisors.

      • The First 100 Days As CIO – Presentation Deck

      3. View an example of the final presentation

      See an example of a completed presentation deck, from the new CIO of Gotham City.

      • The First 100 Days As CIO – Presentation Deck Example

      4. Listen to our podcast

      Check out The Business Leadership podcast in Info-Tech's special series, The First 100 Days.

      • "The First 100 Days" Podcast – Alan Fong, CTO, DealerFX
      • "The First 100 Days" Podcast – Denis Gaudreault, country manager for Intel’s Canada and Latin America region
      • "The First 100 Days" Podcast – Dave Penny & Andrew Wertkin, BlueCat
      • "The First 100 Days" Podcast – Susan Bowen, CEO, Aptum
      • "The First 100 Days" Podcast – Wayne Berger, CEO IWG Plc Canada and Latin America
      • "The First 100 Days" Podcast – Eric Wright, CEO, LexisNexis Canada
      • "The First 100 Days" Podcast – Erin Bury, CEO, Willful
      [infographic]

      Further reading

      The First 100 Days As CIO

      Partner with Info-Tech for success in this crucial period of transition.

      Analyst Perspective

      The first 100 days refers to the 10 days before you start and the first three months on the job.

      “The original concept of ‘the first 100 days’ was popularized by Franklin Delano Roosevelt, who passed a battery of new legislation after taking office as US president during the Great Depression. Now commonly extended to the business world, the first 100 days of any executive role is a critically important period for both the executive and the organization.

      But not every new leader should follow FDR’s example of an action-first approach. Instead, finding the right balance of listening and taking action is the key to success during this transitional period. The type of the organization and the mode that it’s in serves as the fulcrum that determines where the point of perfect balance lies. An executive facing a turnaround situation will want to focus on more action more quickly. One facing a sustaining success situation or a realignment situation will want to spend more time listening before taking action.” (Brian Jackson, Research Director, CIO, Info-Tech Research Group)

      Executive summary

      Situation

      • You’ve been promoted from within to the role of CIO.
      • You’ve been hired externally to take on the role of CIO.

      Complication

      Studies show that two years after a new executive transition, as many as half are regarded as failures or disappointments (McKinsey). First impressions are hard to overcome, and a CIO’s first 100 days are heavily weighted in terms of how others will assess their overall success. The best way to approach this period is determined by both the size and the mode of an organization.

      Resolution

      • Work with Info-Tech to prepare a 100-day plan that will position you for success.
      • Collaborate to collect the details needed to identify the right mode for your organization and determine how it will influence your plan.
      • Use Info-Tech’s diagnostic tools to align your vision with that of business executives and form a baseline for future reference.

      Info-Tech Insight

      1. Foundational understanding must be achieved before you start.
        Hit the ground running before day one by using company documents and initial discussions to pin down the company’s type and mode.
      2. Listen before you act (usually).
        In most situations, executives benefit from listening to peers and staff before taking action.
      3. Identify quick wins early and often.
        Fix problems as soon as you recognize them to set the tone for your tenure.

      The First 100 Days: Roadmap

      A roadmap timeline of 'The 100-Day Plan' for your first 100 days as CIO and related Info-Tech Diagnostics. Step A: 'Foundational Preparation' begins 10 days prior to your first day. Step B: 'Management's Expectations' is Days 0 to 30, with the diagnostic 'CIO-CEO Alignment'. Step C: 'Assessing the IT Team' is Days 10 to 75, with the diagnostics 'IT M&G Diagnostic' at Day 30 and 'IT Staffing Assessment' at Day 60. Step D: 'Assess the Key Stakeholders' is Days 40 to 85 with the diagnostic 'CIO Business Vision Survey'. Step E: 'Deliver First-Year Plan' is Days 80 to 100.

      Concierge service overview

      Organize a call with your executive advisor every two weeks during your first 100 days. Info-Tech recommends completing our diagnostics during this period. If you’re not able to do so, instead complete the alternative activities marked with (a).

      Call 1 Call 2 Call 3 Call 4 Call 5 Call 6 Call 7
      Activities
      Before you start: Day -10 to Day 1
      • 1.1 Interview your predecessor.
      • 1.2 Learn the corporate structure.
      • 1.3 Determine STARS mode.
      • 1.4 Create a one-page intro sheet.
      • 1.5 Update your boss.
      Day 0 to 15
      • 2.1 Introduce yourself to your team.
      • 2.2 Document your sphere of influence.
      • 2.3 Complete a competitor array.
      • 2.4 Complete the CEO-CIO Alignment Program.
      • 2.4(a) Agree on what success looks like with the boss.
      • 2.5 Inform team of IT M&G Framework.
      Day 16 to 30
      • 3.1 Determine the team’s cultural archetype.
      • 3.2 Create a cultural adjustment plan.
      • 3.3 Initiate IT M&G Diagnostic.
      • 3.4 Conduct a high-level analysis of current IT capabilities.
      • 3.4 Update your boss.
      Day 31 to 45
      • 4.1 Inform stakeholders about CIO Business Vision survey.
      • 4.2 Get feedback on initial assessments from your team.
      • 4.3 Initiate CIO Business Vision survey.
      • 4.3(a) Meet stakeholders and catalog details.
      Day 46 to 60
      • 5.1 Inform the team that you plan to conduct an IT staffing assessment.
      • 5.2 Initiate the IT Staffing Assessment.
      • 5.3 Quick wins: Make recommend-ations based on CIO Business Vision Diagnostic/IT M&G Framework.
      • 5.4 Update your boss.
      Day 61 to 75
      • 6.1 Run a start, stop, continue exercise with IT staff.
      • 6.2 Make a categorized vendor list.
      • 6.3 Determine the alignment of IT commitments with business objectives.
      Day 76 to 90
      • 7.1 Finalize your vision – mission – values statement.
      • 7.2 Quick Wins: Make recommend-ations based on IT Staffing Assessment.
      • 7.3 Create and communicate a post-100-day plan.
      • 7.4 Update your boss.
      Deliverables Presentation Deck Section A: Foundational Preparation Presentation Deck slides 9, 11-13, 19-20, 29 Presentation Deck slides 16, 17, 21 Presentation Deck slides 30, 34 Presentation Deck slides 24, 25, 2 Presentation Deck slides 27, 42

      Call 1

      Before you start: Day -10 to Day 1

      Interview your predecessor

      Interviewing your predecessor can help identify the organization’s mode and type.

      Before reaching out to your predecessor, get a sense of whether they were viewed as successful or not. Ask your manager. If the predecessor remains within the organization in a different role, understand your relationship with them and how you'll be working together.

      During the interview, make notes about follow-up questions you'll ask others at the organization.

      Ask these open-ended questions in the interview:

      • Tell me about the team.
      • Tell me about your challenges.
      • Tell me about a major project your team worked on. How did it go?
      • Who/what has been helpful during your tenure?
      • Who/what created barriers for you?
      • What do your engagement surveys reveal?
      • Tell me about your performance management programs and issues.
      • What mistakes would you avoid if you could lead again?
      • Why are you leaving?
      • Could I reach out to you again in the future?

      Learn the corporate structure

      Identify the organization’s corporate structure type based on your initial conversations with company leadership. The type of structure will dictate how much control you'll have as a functional head and help you understand which stakeholders you'll need to collaborate with.

      To Do:

      • Review the organization’s structure list and identify whether the structure is functional, prioritized, or a matrix. If it's a matrix organization, determine if it's a strong matrix (project manager holds more authority), weak matrix (functional manager holds more authority), or balanced matrix (managers hold equal authority).

      Functional

      • Most common structure.
      • Traditional departments such as sales, marketing, finance, etc.
      • Functional managers hold most authority.

      Projectized

      • Most programs are implemented through projects with focused outcomes.
      • Teams are cross-functional.
      • Project managers hold the most authority.

      Matrix

      • Combination of projectized and functional.
      • Organization is a dynamic environment.
      • Authority of functional manager flows down through division, while authority of project manager flows sideways through teams.

      This organization is a ___________________ type.

      (Source: Simplilearn)

      Presentation Deck, slide 6

      Determine the mode of the organization: STARS

      Based on your interview process and discussions with company leadership, and using Michael Watkins’ STARS assessment, determine which mode your organization is in: startup, turnaround, accelerated growth, realignment, or sustaining success.

      Knowing the mode of your organization will determine how you approach your 100-day plan. Depending on the mode, you'll rebalance your activities around the three categories of assess, listen, and deliver.

      To Do:

      • Review the STARS table on the right.

      Based on your situation, prioritize activities in this way:

      • Startup: assess, listen, deliver
      • Turnaround: deliver, listen, assess
      • Accelerated Growth: assess, listen, deliver
      • Realignment: listen, assess, deliver
      • Sustaining success: listen, assess, deliver

      This organization is a ___________________ type.

      (Source: Watkins, 2013.)

      Presentation Deck, slide 6

      Determine the mode of the organization: STARS

      STARS Startup Turnaround Accelerated Growth Realignment Sustaining Success
      Definition Assembling capabilities to start a project. Project is widely seen as being in serious trouble. Managing a rapidly expanding business. A previously successful organization is now facing problems. A vital organization is going to the next level.
      Challenges Must build strategy, structures, and systems from scratch. Must recruit and make do with limited resources. Stakeholders are demoralized; slash and burn required. Requires structure and systems to scale; hiring and onboarding. Employees need to be convinced change is needed; restructure at the top required. Risk of living in shadow of a successful former leader.
      Advantages No rigid preconceptions. High-energy environment and easy to pivot. A little change goes a long way when people recognize the need. Motivated employee base willing to stretch. Organization has clear strengths; people desire success. Likely a strong team; foundation for success likely in place.

      Satya Nadella's listen, lead, and launch approach

      CASE STUDY

      Industry Software
      Source Gregg Keizer, Computerworld, 2014

      When Satya Nadella was promoted to the CEO role at Microsoft in 2014, he received a Glassdoor approval rating of 85% and was given an "A" grade by industry analysts after his first 100 days. What did he do right?

      • Created a sense of urgency by shaking up the senior leadership team.
      • Already understood the culture as an insider.
      • Listened a lot and did many one-on-one meetings.
      • Established a vision communicated with a mantra that Microsoft would be "mobile-first, cloud-first."
      • Met his words with actions. He launched Office for iPad and made many announcements for cloud platform Azure.
      Photo of Satya Nadella, CEO, Microsoft Corp.
      Satya Nadella, CEO, Microsoft Corp. (Image source: Microsoft)

      Listen to 'The First 100 Days' podcast – Alan Fong

      Create a one-page introduction sheet to use in communications

      As a new CIO, you'll have to introduce yourself to many people in the organization. To save time on communicating who you are as a person outside of the office, create a brief one-pager that includes a photo of you, where you were born and raised, and what your hobbies are. This helps make a connection more quickly so your conversations can focus on the business at hand rather than personal topics.

      For your presentation deck, remove the personal details and just keep it professional. The personal aspects can be used as a one-pager for other communications. (Source: Personal interview with Denis Gaudreault, Country Lead, Intel.)

      Presentation Deck, slide 5

      Call 2

      Day 1 to Day 15

      Introduce yourself to your team

      Prepare a 20-second pitch about yourself that goes beyond your name and title. Touch on your experience that's relevant to your new role or the industry you're in. Be straightforward about your own perceived strengths and weaknesses so that people know what to expect from you. Focus on the value you believe you'll offer the group and use humor and humility where you're comfortable. For example:

      “Hi everyone, my name is John Miller. I have 15 years of experience marketing conferences like this one to vendors, colleges, and HR departments. What I’m good at, and the reason I'm here, is getting the right people, businesses, and great ideas in a room together. I'm not good on details; that's why I work with Tim. I promise that I'll get people excited about the conference, and the gifts and talents of everyone else in this room will take over from there. I'm looking forward to working with all of you.”

      Have a structured set of questions ready that you can ask everyone.

      For example:
      • How well is the company performing based on expectations?
      • What must the company do to sustain its financial performance and market competitiveness?
      • How do you foresee the CIO contributing to the team?
      • How have past CIOs performed from the perspective of the team?
      • What would successful performance of this role look like to you? To your peers?
      • What challenges and obstacles to success am I likely to encounter? What were the common challenges of my predecessor?
      • How do you view the culture here and how do successful projects tend to get approved?
      • What are your greatest challenges? How could I help you?

      Get to know your sphere of influence: prepare to connect with a variety of people before you get down to work

      Your ability to learn from others is critical at every stage in your first 100 days. Keep your sphere of influence in the loop as you progress through this period.

      A diagram of circles within circles representing your spheres of influence. The smallest circle is 'IT Leaders' and is noted as your 'Immediate circle'. The next largest circle is 'IT Team', then 'Peers - Business Leads', then 'Internal Clients' which is noted as you 'Extended circle'. The largest circle is 'External clients'.

      Write down the names, or at least the key people, in each segment of this diagram. This will serve as a quick reference when you're planning communications with others and will help you remember everyone as you're meeting lots of new people in your early days on the job.

      • Everyone knows their networks are important.
      • However, busy schedules can cause leaders to overlook their many audiences.
      • Plan to meet and learn from all people in your sphere to gain a full spectrum of insights.

      Presentation Deck, slide 29

      Identify how your competitors are leveraging technology for competitive advantage

      Competitor identification and analysis are critical steps for any new leader to assess the relative strengths and weaknesses of their organization and develop a sense of strategic opportunity and environmental awareness.

      Today’s CIO is accountable for driving innovation through technology. A competitive analysis will provide the foundation for understanding the current industry structure, rivalry within it, and possible competitive advantages for the organization.

      Surveying your competitive landscape prior to the first day will allow you to come to the table prepared with insights on how to support the organization and ensure that you are not vulnerable to any competitive blind spots that may exist in the evaluations conducted by the organization already.

      You will not be able to gain a nuanced understanding of the internal strengths and weaknesses until you are in the role, so focus on the external opportunities and how competitors are using technology to their advantage.

      Info-Tech Best Practice

      For a more in-depth approach to identifying and understanding relevant industry trends and turning them into insights, leverage the following Info-Tech blueprints:

      Presentation Deck, slide 9

      Assess the external competitive environment

      Associated Activity icon

      INPUT: External research

      OUTPUT: Competitor array

      1. Conduct a broad analysis of the industry as a whole. Seek to answer the following questions:
        1. Are there market developments or new markets?
        2. Are there industry or lifestyle trends, e.g. move to mobile?
        3. Are there geographic changes in the market?
        4. Are there demographic changes that are shaping decision making?
        5. Are there changes in market demand?
      2. Create a competitor array by identifying and listing key competitors. Try to be as broad as possible here and consider not only entrenched close competitors but also distant/future competitors that may disrupt the industry.
      3. Identify the strengths, weaknesses, and key brand differentiators that each competitor brings to the table. For each strength and differentiator, brainstorm ways that IT-based innovation enables each. These will provide a toolkit for deeper conversations with your peers and your business stakeholders as you move further into your first 100 days.
      Competitor Strengths Weaknesses Key Differentiators IT Enablers
      Competitor 1
      Competitor 2
      Competitor 3

      Complete the CEO-CIO Alignment Program

      Associated Activity icon Run the diagnostic program or use the alternative activities to complete your presentation

      INPUT: CEO-CEO Alignment Program (recommended)

      OUTPUT: Desired and target state of IT maturity, Innovation goals, Top priorities

      Materials: Presentation Deck, slides 11-13

      Participants: CEO, CIO

      Introduce the concept of the CEO-CIO Alignment Program using slide 10 of your presentation deck and the brief email text below.

      Talk to your advisory contact at Info-Tech about launching the program. More information is available on Info-Tech’s website.

      Once the report is complete, import the results into your presentation:

      • Slide 11, the CEO’s current and desired states
      • Slide 12, IT innovation goals
      • Slide 13, top projects and top departments from the CEO and the CIO

      Include any immediate recommendations you have.

      Hello CEO NAME,

      I’m excited to get started in my role as CIO, and to hit the ground running, I’d like to make sure that the IT department is aligned with the business leadership. We will accomplish this using Info-Tech Research Group’s CEO-CIO Alignment Program. It’s a simple survey of 20 questions to be completed by the CEO and the CIO.

      This survey will help me understand your perception and vision as I get my footing as CIO. I’ll be able to identify and build core IT processes that will automate IT-business alignment going forward and create an effective IT strategy that helps eliminate impediments to business growth.

      Research shows that IT departments that are effectively aligned to business goals achieve more success, and I’m determined to make our IT department as successful as possible. I look forward to further detailing the benefits of this program to you and answering any questions you may have the next time we speak.

      Regards,
      CIO NAME

      New KPIs for CEO-CIO Alignment — Recommended

      Info-Tech CEO-CIO Alignment Program

      Info-Tech's CEO-CIO Alignment Program is set up to build IT-business alignment in any organization. It helps the CIO understand CEO perspectives and priorities. The exercise leads to useful IT performance indicators, clarifies IT’s mandate and which new technologies it should invest in, and maps business goals to IT priorities.

      Benefits

      Master the Basics
      Cut through the jargon.
      Take a comprehensive look at the CEO perspective.
      Target Alignment
      Identify how IT can support top business priorities. Address CEO-CIO differences.
      Start on the Right Path
      Get on track with the CIO vision. Use correct indicators and metrics to evaluate IT from day one.

      Supporting Tool or Template icon Additional materials are available on Info-Tech’s website.

      The desired maturity level of IT — Alternative

      Associated Activity icon Use only if you can’t complete the CEO-CIO Alignment Program

      Step 1: Where are we today?

      Determine where the CEO sees the current overall maturity level of the IT organization.

      Step 2: Where do we want to be as an organization?

      Determine where the CEO wants the IT organization to be in order to effectively support the strategic direction of the business.

      A colorful visual representation of the different IT maturity levels. At the bottom is 'STRUGGLE, Unable to Provide Reliable Business Services', then moving upwards are 'SUPPORT, Reliable Infrastructure and IT Service Desk', 'OPTIMIZE, Effective Fulfillment of Work Orders, Functional Business Applications, and Reliable Service Management', 'EXPAND, Effective Execution on Business Projects, Strategic Use of Analytics and Customer Technology', and at the top is 'TRANSFORM, Reliable Technology Innovation'.

      Presentation Deck, slide 11

      Tim Cook's powerful use of language

      CASE STUDY

      Industry Consumer technology
      Source Carmine Gallo, Inc., 2019

      Apple CEO Tim Cook, an internal hire, had big shoes to fill after taking over from the late Steve Jobs. Cook's ability to control how the company is perceived is a big credit to his success. How does he do it? His favorite five words are “The way I see it..." These words allow him to take a line of questioning and reframe it into another perspective that he wants to get across. Similarly, he'll often say, "Let me tell you the way I look at it” or "To put it in perspective" or "To put it in context."

      In your first two weeks on the job, try using these phrases in your conversations with peers and direct reports. It demonstrates that you value their point of view but are independently coming to conclusions about the situation at hand.

      Photo of Tim Cook, CEO, Apple Inc.
      Tim Cook, CEO, Apple Inc. (Image source: Apple)

      Listen to 'The First 100 Days' podcast – Denis Gaudreault

      Inform your team that you plan to do an IT Management & Governance Diagnostic survey

      Associated Activity icon Run the diagnostic program or use the alternative activities to complete your presentation

      INPUT: IT Management & Governance Diagnostic (recommended)

      OUTPUT: Process to improve first, Processes important to the business

      Materials: Presentation Deck, slides 19-20

      Participants: CIO, IT staff

      Introduce the IT Management & Governance Diagnostic survey that will help you form your IT strategy.

      Explain that you want to understand current IT capabilities and you feel a formal approach is best. You’ll also be using this approach as an important metric to track your department’s success. Tell them that Info-Tech Research Group will be conducting the survey and it’s important to you that they take action on the email when it’s sent to them.

      Example email:

      Hello TEAM,

      I appreciate meeting each of you, and so far I’m excited about the talents and energy on the team. Now I need to understand the processes and capabilities of our department in a deeper way. I’d like to map our process landscape against an industry-wide standard, then dive deeper into those processes to understand if our team is aligned. This will help us be accountable to the business and plan the year ahead. Advisory firm Info-Tech Research Group will be reaching out to you with a simple survey that shouldn’t take too long to complete. It’s important to me that you pay attention to that message and complete the survey as soon as possible.

      Regards,
      CIO NAME

      Call 3

      Day 16 to Day 30

      Leverage team interviews as a source of determining organizational culture

      Info-Tech recommends that you hold group conversations with your team to uncover their opinions of the current organizational culture. This not only helps build transparency between you and your team but also gives you another means of observing behavior and reactions as you listen to team members’ characterizations of the current culture.

      A visualization of the organizational culture of a company asks the question 'What is culture?' Five boxes are stacked, the bottom two are noted as 'The invisible causes' and the top two are noted as 'The visible signs'. From the bottom, 'Fundamental assumptions and beliefs', 'Values and attitudes', 'The way we do things around here', 'Behaviors', and at the top, 'Environment'. (Source: Hope College Blog Network)

      Note: It is inherently difficult for people to verbalize what constitutes a culture – your strategy for extracting this information will require you to ask indirect questions to solicit the highest value information.

      Questions for Discussion:

      • What about the current organizational environment do you think most contributes to your success?
      • What barriers do you experience as you try to accomplish your work?
      • What is your favorite quality that is present in our organization?
      • What is the one thing you would most like to change about this organization?
      • Do the organization's policies and procedures support your efforts to accomplish work or do they impede your progress?
      • How effective do you think IT’s interactions are with the larger organization?
      • What would you consider to be IT’s top three guiding principles?
      • What kinds of people fail in this organization?

      Supporting Tool or Template icon See Info-Tech’s Cultural Archetype Calculator.

      Use the Competing Values Framework to define your organization’s cultural archetype

      THE COMPETING VALUES FRAMEWORK (CVF):

      CVF represents the synthesis of academic study of 39 indicators of effectiveness for organizations. Using a statistical analysis, two polarities that are highly predictive of differences in organizational effectiveness were isolated:

      1. Internal focus and integration vs. external focus and differentiation.
      2. Stability and control vs. flexibility and discretion.

      By plotting these dimensions on a matrix of competing values, four main cultural archetypes are identified with their own value drivers and theories of effectiveness.

      A map of cultural archetypes with 'Internal control and integration' on the left, 'External focus and differentiation' on the right, 'Flexibility and discretion' on top, and 'Stability and control' on the bottom. Top left is 'Clan Archetype', internal and flexible. Top right is 'Adhocracy Archetype', external and flexible. Bottom left is 'Hierarchy Archetype', internal and controlled. Bottom right is 'Market Archetype', external and controlled.

      Presentation Deck, slide 16

      Create a cultural adjustment plan

      Now that you've assessed the cultural archetype, you can plan an appropriate approach to shape the culture in a positive way. When new executives want to change culture, there are a few main options at hand:

      Autonomous evolution: Encourage teams to learn from each other. Empower hybrid teams to collaborate and reward teams that perform well.

      Planned and managed change: Create steering committee and project-oriented taskforces to work in parallel. Appoint employees that have cultural traits you'd like to replicate to hold responsibility for these bodies.

      Cultural destruction: When a toxic culture needs to be eliminated, get rid of its carriers. Putting new managers or directors in place with the right cultural traits can be a swift and effective way to realign.

      Each option boils down to creating the right set of incentives and deterrents. What behaviors will you reward and which ones will you penalize? What do those consequences look like? Sometimes, but not always, some structural changes to the team will be necessary. If you feel these changes should be made, it's important to do it sooner rather than later. (Source: “Enlarging Your Sphere of Influence in Your Organization,” MindTools Corporate, 2014.)

      As you're thinking about shaping a desired culture, it's helpful to have an easy way to remember the top qualities you want to espouse. Try creating an acronym that makes it easy for staff to remember. For example: RISE could remind your staff to be Responsive, Innovative, Sustainable, and Engaging (RISE). Draw upon your business direction from your manager to help produce desired qualities (Source: Jennifer Schaeffer).

      Presentation Deck, slide 17

      Gary Davenport’s welcome “surprise”

      CASE STUDY

      Industry Telecom
      Source Interview with Gary Davenport

      After Gary Davenport was hired on as VP of IT at MTS Allstream, his first weekend on the job was spent at an all-executive offsite meeting. There, he learned from the CEO that the IT department had a budget reduction target of 25%, like other departments in the company. “That takes your breath away,” Davenport says.

      He decided to meet the CEO monthly to communicate his plans to reduce spending while trying to satisfy business stakeholders. His top priorities were:

      1. Stabilize IT after seven different leaders in a five-year period.
      2. Get the IT department to be respected. To act like business owners instead of like servants.
      3. Better manage finances and deliver on projects.

      During Davenport’s 7.5-year tenure, the IT department became one of the top performers at MTS Allstream.

      Photo of Gary Davenport.
      Gary Davenport’s first weekend on the job at MTS Allstream included learning about a 25% reduction target. (Image source: Ryerson University)

      Listen to 'The First 100 Days' podcast – David Penny & Andrew Wertkin

      Initiate IT Management & Governance Diagnostic — Recommended

      Info-Tech Management & Governance Diagnostic

      Talk to your Info-Tech executive advisor about launching the survey shortly after informing your team to expect it. You'll just have to provide the names and email addresses of the staff you want to be involved. Once the survey is complete, you'll harvest materials from it for your presentation deck. See slides 19 and 20 of your deck and follow the instructions on what to include.

      Benefits

      A sample of the 'High Level Process Landscape' materials available from Info-Tech. A sample of the 'Strategy and Governance In Depth Results' materials available from Info-Tech. A sample of the 'Process Accountability' materials available from Info-Tech.
      Explore IT Processes
      Dive deeper into performance. Highlight problem areas.
      Align IT Team
      Build consensus by identifying opposing views.
      Ownership & Accountability
      Identify process owners and hold team members accountable.

      Supporting Tool or Template icon Additional materials available on Info-Tech’s website.

      Conduct a high-level analysis of current IT capabilities — Alternative

      Associated Activity icon

      INPUT: Interviews with IT leadership team, Capabilities graphic on next slide

      OUTPUT: High-level understanding of current IT capabilities

      Run this activity if you're not able to conduct the IT Management & Governance Diagnostic.

      Schedule meetings with your IT leadership team. (In smaller organizations, interviewing everyone may be acceptable.) Provide them a list of the core capabilities that IT delivers upon and ask them to rate them on an effectiveness scale of 1-5, with a short rationale for their score.

      • 1. Not effective (NE)
      • 2. Somewhat Effective (SE)
      • 3. Effective (E)
      • 4. Very Effective (VE)
      • 5. Extremely Effective (EE)

      Presentation Deck, slide 21

      Use the following set of IT capabilities for your assessment

      Strategy & Governance

      IT Governance Strategy Performance Measurement Policies Quality Management Innovation

      People & Resources

      Stakeholder Management Resource Management Financial Management Vendor Selection & Contract Management Vendor Portfolio Management Workforce Strategy Strategic Comm. Organizational Change Enablement

      Service Management & Operations

      Operations Management Service Portfolio Management Release Management Service Desk Incident & Problem Management Change Management Demand Management

      Infrastructure

      Asset Management Infrastructure Portfolio Management Availability & Capacity Management Infrastructure Management Configuration Management

      Information Security & Risk

      Security Strategy Risk Management Compliance, Audit & Review Security Detection Response & Recovery Security Prevention

      Applications

      Application Lifecycle Management Systems Integration Application Development User Testing Quality Assurance Application Maintenance

      PPM & Projects

      Portfolio Management Requirements Gathering Project Management

      Data & BI

      Data Architecture BI & Reporting Data Quality & Governance Database Operations Enterprise Content Management

      Enterprise Architecture

      Enterprise Architecture Solution Architecture

      Quick wins: CEO-CIO Alignment Program

      Complete this while waiting on the IT M&G survey results. Based on your completed CEO-CIO Alignment Report, identify the initiatives you can tackle immediately.

      If you are here... And want to be here... Drive toward... Innovate around...
      Business Partner Innovator Leading business transformation
      • Emerging technologies
      • Analytical capabilities
      • Risk management
      • Customer-facing tech
      • Enterprise architecture
      Trusted Operator Business Partner Optimizing business process and supporting business transformation
      • IT strategy and governance
      • Business architecture
      • Projects
      • Resource management
      • Data quality
      Firefighter Trusted Operator Optimize IT processes and services
      • Business applications
      • Service management
      • Stakeholder management
      • Work orders
      Unstable Firefighter Reduce use disruption and adequately support the business
      • Network and infrastructure
      • Service desk
      • Security
      • User devices

      Call 4

      Day 31 to Day 45

      Inform your peers that you plan to do a CIO Business Vision survey to gauge your stakeholders’ satisfaction

      Associated Activity icon Run the diagnostic program or use the alternative activities to complete your presentation

      INPUT: CIO Business Vision survey (recommended)

      OUTPUT: True measure of business satisfaction with IT

      Materials: Presentation Deck, slide 30

      Participants: CIO, IT staff

      Meet the business leaders at your organization face-to-face if possible. If you can't meet in person, try a video conference to establish some rapport. At the end of your introduction and after listening to what your colleague has to say, introduce the CIO Business Vision Diagnostic.

      Explain that you want to understand how to meet their business needs and you feel a formal approach is best. You'll also be using this approach as an important metric to track your department's success. Tell them that Info-Tech Research Group will be conducting the survey and it’s important to you that they take the survey when the email is sent to them.

      Example email:

      Hello PEER NAMES,

      I'm arranging for Info-Tech Research Group to invite you to take a survey that will be important to me. The CIO Business Vision survey will help me understand how to meet your business needs. It will only take about 15 minutes of your time, and the top-line results will be shared with the organization. We will use the results to plan initiatives for the future that will improve your satisfaction with IT.

      Regards,
      CIO NAME

      Gain feedback on your initial assessments from your IT team

      There are two strategies for gaining feedback on your initial assessments of the organization from the IT team:

      1. Review your personal assessments with the relevant members of your IT organization as a group. This strategy can help to build trust and an open channel for communication between yourself and your team; however, it also runs the risk of being impacted by groupthink.
      2. Ask for your team to complete their own assessments for you to compare and contrast. This strategy can help extract more candor from your team, as they are not expected to communicate what may be nuanced perceptions of organizational weaknesses or criticisms of the way certain capabilities function.

      Who you involve in this process will be impacted by the size of your organization. For larger organizations, involve everyone down to the manager level. In smaller organizations, you may want to involve everyone on the IT team to get an accurate lay of the land.

      Areas for Review:

      • Strategic Document Review: Are there any major themes or areas of interest that were not covered in my initial assessment?
      • Competitor Array: Are there any initiatives in flight to leverage new technologies?
      • Current State of IT Maturity: Does IT’s perception align with the CEO’s? Where do you believe IT has been most effective? Least effective?
      • IT’s Key Priorities: Does IT’s perception align with the CEO’s?
      • Key Performance Indicators: How has IT been measured in the past?

      Info-Tech Best Practice

      You need your team’s hearts and minds or you risk a short tenure. Overemphasizing business commitment by neglecting to address your IT team until after you meet your business stakeholders will result in a disenfranchised group. Show your team their importance.

      Susan Bowen's talent maximization

      CASE STUDY

      Industry Infrastructure Services
      Source Interview with Susan Bowen

      Susan Bowen was promoted to be the president of Cogeco Peer 1, an infrastructure services firm, when it was still a part of Cogeco Communications. Part of her mandate was to help spin out the business to a new owner, which occurred when it was acquired by Digital Colony. The firm was renamed Aptum and Bowen was put in place as CEO, which was not a certainty despite her position as president at Cogeco Peer 1. She credits her ability to put the right talent in the right place as part of the reason she succeeded. After becoming president, she sought a strong commitment from her directors. She gave them a choice about whether they'd deliver on a new set of expectations – or not. She also asks her leadership on a regular basis if they are using their talent in the right way. While it's tempting for directors to want to hold on to their best employees, those people might be able to enable many more people if they can be put in another place.

      Bowen fully rounded out her leadership team after Aptum was formed. She created a chief operating officer and a chief infrastructure officer. This helped put in place more clarity around roles at the firm and put an emphasis on client-facing services.

      Photo of Susan Bowen, CEO, Aptum.
      Susan Bowen, CEO, Aptum (Image source: Aptum)

      Listen to 'The First 100 Days' podcast – Susan Bowen

      Initiate CIO Business Vision survey – new KPIs for stakeholder management — Recommended

      Info-Tech CIO Business Vision

      Be sure to effectively communicate the context of this survey to your business stakeholders before you launch it. Plan to talk about your plans to introduce it in your first meetings with stakeholders. When ready, let your executive advisor know you want to launch the tool and provide the names and email addresses of the stakeholders you want involved. After you have the results, harvest the materials required for your presentation deck. See slide 30 and follow the instructions on what to include.

      Benefits

      Icon for Key Stakeholders. Icon for Credibility. Icon for Improve. Icon for Focus.
      Key Stakeholders
      Clarify the needs of the business.
      Credibility
      Create transparency.
      Improve
      Measure IT’s progress.
      Focus
      Find what’s important.

      Supporting Tool or Template icon Additional materials are available on Info-Tech’s website.

      Create a catalog of key stakeholder details to reference prior to future conversations — Alternative

      Only conduct this activity if you’re not able to run the CIO Business Vision diagnostic.

      Use the Organizational Catalog as a personal cheat sheet to document the key details around each of your stakeholders, including your CEO when possible.

      The catalog will be an invaluable tool to keep the competing needs of your different stakeholders in line, while ensuring you are retaining the information to build the political capital needed to excel in the C-suite.

      Note: It is important to keep this document private. While you may want to communicate components of this information, ensure your catalog remains under lock and (encryption) key.

      Screenshot of the Organizational Catalog for Stakeholders. At the top are spaces for 'Name', 'Job Title', etc. Boxes include 'Key Personal Details', 'Satisfaction Levels With IT', 'Preferred Communications', 'Key Activities', 'In-Flight and Scheduled Projects', 'Key Performance Indicators', and 'Additional Details'.

      Info-Tech Insight

      While profiling your stakeholders is important, do not be afraid to profile yourself as well. Visualizing how your interests overlap with those of your stakeholders can provide critical information on how to manage your communications so that those on the receiving end are hearing exactly what they need.

      Activity: Conduct interviews with your key business stakeholders — Alternative

      Associated Activity icon

      1. Once you have identified your key stakeholders through your interviews with your boss and your IT team, schedule a set of meetings with those individuals.
      2. Use the meetings to get to know your stakeholders, their key priorities and initiatives, and their perceptions of the effectiveness of IT.
        1. Use the probative questions to the right to elicit key pieces of information.
        2. Refer to the Organizational Catalog tool for more questions to dig deeper in each category. Ensure that you are taking notes separate from the tool and are keeping the tool itself secure, as it will contain private information specific to your interests.
      3. Following each meeting, record the results of your conversation and any key insights in the Organizational Catalog. Refer to the following slide for more details.

      Questions for Discussion:

      • Be indirect about your personal questions – share stories that will elicit details about their interests, kids, etc.
      • What are your most critical/important initiatives for the year?
      • What are your key revenue streams, products, and services?
      • What are the most important ways that IT supports your success? What is your satisfaction level with those services?
      • Are there any current in-flight projects or initiatives that are a current pain point? How can IT assist to alleviate challenges?
      • How is your success measured? What are your targets for the year on those metrics?

      Presentation Deck, slide 34

      Call 5

      Day 46 to Day 60

      Inform your team that you plan to do an IT staffing assessment

      Associated Activity icon Introduce the IT Staffing Assessment that will help you get the most out of your team

      INPUT: Email template

      OUTPUT: Ready to launch diagnostic

      Materials: Email template, List of staff, Sample of diagnostic

      Participants: CIO, IT staff

      Explain that you want to understand how the IT staff is currently spending its time by function and by activity. You want to take a formal approach to this task and also assess the team’s feelings about its effectiveness across different processes. The results of the assessment will serve as the foundation that helps you improve your team’s effectiveness within the organization.

      Example email:

      Hello PEER NAMES,

      The feedback I've heard from the team since joining the company has been incredibly useful in beginning to formulate my IT strategy. Now I want to get a clear picture of how everyone is spending their time, especially across different IT functions and activities. This will be an opportunity for you to share feedback on what we're doing well, what we need to do more of, and what we're missing. Expect to receive an email invitation to take this survey from Info-Tech Research Group. It's important to me that you complete the survey as soon as you're can. Attached you’ll find an example of the report this will generate. Thank you again for providing your time and feedback.

      Regards,
      CIO NAME

      Wayne Berger's shortcut to solve staffing woes

      CASE STUDY

      Industry Office leasing
      Source Interview with Wayne Berger

      Wayne Berger was hired to be the International Workplace Group (IWG) CEO for Canada and Latin America in 2014.

      Wayne approached his early days with the office space leasing firm as a tour of sorts, visiting nearly every one of the 48 office locations across Canada to host town hall meetings. He heard from staff at every location that they felt understaffed. But instead of simply hiring more staff, Berger actually reduced the workforce by 33%.

      He created a more flexible approach to staffing:

      • Employees no longer just reported to work at one office; instead, they were ready to go to wherever they were most needed in a specific geographic area.
      • He centralized all back-office functions for the company so that not every office had to do its own bookkeeping.
      • Finally, he changed the labor profile to consist of full-time staff, part-time staff, and time-on-demand workers.
      Photo of Wayne Berger, CEO, IWG Plc.
      Wayne Berger, CEO, IWG Plc (Image source: IWG)

      Listen to 'The First 100 Days' podcast – Wayne Berger

      Initiate IT Staffing Assessment – new KPIs to track IT performance — Recommended

      Info-Tech IT Staffing Assessment

      Info-Tech’s IT Staffing Assessment provides benchmarking of key metrics against 4,000 other organizations. Dashboard-style reports provide key metrics at a glance, including a time breakdown by IT function and by activity compared against business priorities. Run this survey at about the 45-day mark of your first 90 days. Its insights will be used to inform your long-term IT strategy.

      Benefits

      Icon for Right-Size IT Headcount. Icon for Allocate Staff Correctly. Icon for Maximize Teams.
      Right-Size IT Headcount
      Find the right level for stakeholder satisfaction.
      Allocate Staff Correctly
      Identify staff misalignments with priorities.
      Maximize Teams
      Identify how to drive staff.

      Supporting Tool or Template icon Additional materials are available on Info-Tech’s website.

      Quick wins: Make recommendations based on IT Management & Governance Framework

      Complete this exercise while waiting on the IT Staffing Assessment results. Based on your completed IT Management & Governance report, identify the initiatives you can tackle immediately. You can conduct this as a team exercise by following these steps:

      1. Create a shortlist of initiatives based on the processes that were identified as high need but scored low in effectiveness. Think as broadly as possible during this initial brainstorming.
      2. Write each initiative on a sticky note and conduct a high-level analysis of the amount of effort that would be required to complete it, as well as its alignment with the achievement of business objectives.
      3. Draw the matrix below on a whiteboard and place each sticky note onto the matrix based on its potential impact and difficulty to address.
      A matrix of initiative categories based on effort to achieve and alignment with business objectives. It is split into quadrants: the vertical axis is 'Potential Impact' with 'High, Fully supports achievement of business objectives' at the top and 'Low, Limited support of business objectives' at the bottom; the horizontal axis is 'Effort' with 'Low' on the left and 'High' on the right. Low impact, low effort is 'Low Current Value, No immediate attention required, but may become a priority in the future if business objectives change'. Low impact, high effort is 'Future Reassessment, No immediate attention required, but may become a priority in the future if business objectives change'. High impact, high effort is 'Long-Term Initiatives, High impact on business outcomes but will take more effort to implement. Schedule these in your long-term roadmap'. High impact, low effort is 'Quick Wins, High impact on business objectives with relatively small effort. Some combination of these will form your early wins'.

      Call 6

      Day 61 to Day 75

      Run a start, stop, continue exercise with your IT staff — Alternative

      This is an alternative activity to running an IT Staffing Assessment, which contains a start/stop/continue assessment. This activity can be facilitated with a flip chart or a whiteboard. Create three pages or three columns and label them Start, Stop, and Continue.

      Hand out sticky notes to each team member and then allow time for individual brainstorming. Instruct them to write down their contributions for each category on the sticky notes. After a few minutes, have everyone stick their notes in the appropriate category on the board. Discuss as a group and see what themes emerge. Record the results that you want to share in your presentation deck (GroupMap).

      Gather your team and explain the meaning of these categories:

      Start: Activities you're not currently doing but should start doing very soon.

      Stop: Activities you're currently doing but aren’t working and should cease.

      Continue: Things you're currently doing and are working well.

      Presentation Deck, slide 24

      Determine the alignment of IT commitments with business objectives

      Associated Activity icon

      INPUT: Interviews with IT leadership team

      OUTPUT: High-level understanding of in-flight commitments and investments

      Run this only as an alternative to the IT Management & Governance Diagnostic.

      1. Schedule meetings with IT leadership to understand what commitments have been made to the business in terms of new products, projects, or enhancements.
      2. Determine the following about IT’s current investment mix:
        1. What are the current IT investments and assets? How do they align to business goals?
        2. What investments in flight are related to which information assets?
        3. Are there any immediate risks identified for these key investments?
        4. What are the primary business issues that demand attention from IT consistently?
        5. What choices remain undecided in terms of strategic direction of the IT organization?
      3. Document your key investments and commitments as well as any points of misalignment between objectives and current commitments as action items to address in your long-term plans. If they are small fixes, consider them during your quick-win identification.

      Presentation Deck, slide 25

      Determine the alignment of IT commitments with business objectives

      Run this only as an alternative to the IT Staffing Assessment diagnostic.

      Schedule meetings with IT leadership to understand what commitments have been made to the business in terms of new products, projects, or enhancements.

      Determine the following about IT’s current investment mix:

      • What are the current IT investments and assets?
      • How do they align to business goals?
      • What in-flight investments are related to which information assets?
      • Are there any immediate risks identified for these key investments?
      • What are the primary business issues that demand attention from IT consistently?
      • What remains undecided in terms of strategic direction of the IT organization?

      Document your key investments and commitments, as well as any points of misalignment between objectives and current commitments, as action items to address in your long-term plans. If they are small-effort fixes, consider them during your quick-win identification.

      Presentation Deck, slide 25

      Make a categorized vendor list by IT process

      As part of learning the IT team, you should also create a comprehensive list of vendors under contract. Collaborate with the finance department to get a clear view of how much of the IT budget is spent on specific vendors. Try to match vendors to the IT processes they serve from the IT M&G framework.

      You should also organize your vendors based on their budget allocation. Go beyond just listing how much money you’re spending with each vendor and categorize them into either “transactional” relationships or “strategic relationships.” Use the grid below to organize them. Ideally, you’ll want most relationships to be high spend and strategic (Source: Gary Davenport).

      A matrix of vendor categories with the vertical axis 'Spend' increasing upward, and the horizontal axis 'Type of relationship' with values 'Transactional' or 'Strategic'. The bottom left corner is 'Low Spend Transactional', the top right corner is 'High Spend Strategic'.

      Where to source your vendor list:

      • Finance department
      • Infrastructure managers
      • Vendor manager in IT

      Further reading: Manage Your Vendors Before They Manage You

      Presentation Deck, slide 26

      Jennifer Schaeffer’s short-timeline turnaround

      CASE STUDY

      Industry Education
      Source Interview with Jennifer Schaeffer

      Jennifer Schaeffer joined Athabasca University as CIO in November 2017. She was entering a turnaround situation as the all-online university lacked an IT strategy and had built up significant technical debt. Armed with the mandate of a third-party consultant that was supported by the president, Schaeffer used a people-first approach to construct her strategy. She met with all her staff, listening to them carefully regardless of role, and consulted with the administrative council and faculty members. She reflected that feedback in her plan or explained to staff why it wasn’t relevant for the strategy. She implemented a “strategic calendaring” approach for the organization, making sure that her team members were participating in meetings where their work was assessed and valued. Drawing on Spotify as an inspiration, she designed her teams in a way that everyone was connected to the customer experience. Given her short timeline to execute, she put off a deep skills analysis of her team for a later time, as well as creating a full architectural map of her technology stack. The outcome is that 2.5 years later, the IT department is unified in using the same tooling and optimization standards. It’s more flexible and ready to incorporate government changes, such as offering more accessibility options.

      Photo of Jennifer Schaeffer.
      Jennifer Schaeffer took on the CIO role at Athabasca University in 2017 and was asked to create a five-year strategic plan in just six weeks.
      (Image source: Athabasca University)

      Listen to 'The First 100 Days' podcast – Eric Wright

      Call 7

      Day 76 to Day 90

      Finalize your vision – mission – values statement

      A clear statement for your values, vision, and mission will help crystallize your IT strategy and communicate what you're trying to accomplish to the entire organization.

      Mission: This statement describes the needs that IT was created to meet and answers the basic question of why IT exists.

      Vision: Write a statement that captures your values. Remember that the vision statement sets out what the IT organization wants to be known for now and into the future.

      Values: IT core values represent the standard axioms by which the IT department operates. Similar to the core values of the organization as a whole, IT’s core values are the set of beliefs or philosophies that guide its strategic actions.

      Further reading: IT Vision and Mission Statements Template

      Presentation Deck, slide 42

      John Chen's new strategic vision

      CASE STUDY

      Industry Mobile Services
      Source Sean Silcoff, The Globe and Mail

      John Chen, known in the industry as a successful turnaround executive, was appointed BlackBerry CEO in 2014 following the unsuccessful launch of the BlackBerry 10 mobile operating system and a new tablet.

      He spent his first three months travelling, talking to customers and suppliers, and understanding the company's situation. He assessed that it had a problem generating cash and had made some strategic errors, but there were many assets that could benefit from more investment.

      He was blunt about the state of BlackBerry, making cutting observations of the past mistakes of leadership. He also settled a key question about whether BlackBerry would focus on consumer or enterprise customers. He pointed to a base of 80,000 enterprise customers that accounted for 80% of revenue and chose to focus on that.

      His new mission for BlackBerry: to transform it from being a "mobile technology company" that pushes handset sales to "a mobile solutions company" that serves the mobile computing needs of its customers.

      Photo of John Chen, CEO of BlackBerry.
      John Chen, CEO of BlackBerry, presents at BlackBerry Security Summit 2018 in New York City (Image source: Brian Jackson)

      Listen to 'The First 100 Days' podcast – Erin Bury

      Quick wins: Make recommendations based on the CIO Business Vision survey

      Based on your completed CIO Business Vision survey, use the IT Satisfaction Scorecard to determine some initiatives. Focus on areas that are ranked as high importance to the business but low satisfaction. While all of the initiatives may be achievable given enough time, use the matrix below to identify the quick wins that you can focus on immediately. It’s important to not fail in your quick-win initiative.

      • High Visibility, Low Risk: Best bet for demonstrating your ability to deliver value.
      • Low Visibility, Low Risk: Worth consideration, depending on the level of effort required and the relative importance to the stakeholder.
      • High Visibility, High Risk: Limit higher-risk initiatives until you feel you have gained trust from your stakeholders, demonstrating your ability to deliver.
      • Low Visibility, High Risk: These will be your lowest value, quick-win initiatives. Keep them in a backlog for future consideration in case business objectives change.
      A matrix of initiative categories based on organizational visibility and risk of failure. It is split into quadrants: the vertical axis is 'Organizational Visibility' with 'High' at the top and 'Low' at the bottom; the horizontal axis is 'Risk of Failure' with 'Low' on the left and 'High' on the right. 'Low Visibility, Low Risk, Few stakeholders will benefit from the initiative’s implementation.' 'Low Visibility, High Risk, No immediate attention is required, but it may become a priority in the future if business objectives change.' 'High Visibility, Low Risk, Multiple stakeholders will benefit from the initiative’s implementation, and it has a low risk of failure.' 'High Visibility, High Risk, Multiple stakeholders will benefit from the initiative’s implementation, but it has a higher risk of failure.'

      Presentation Deck, slide 27

      Create and communicate a post-100 plan

      The last few slides of your presentation deck represent a roundup of all the assessments you’ve done and communicate your plan for the months ahead.

      Slide 38. Based on the information on the previous slide and now knowing which IT capabilities need improvement and which business priorities are important to support, estimate where you'd like to see IT staff spend their time in the near future. Will you be looking to shift staff from one area to another? Will you be looking to hire staff?

      Slide 39. Take your IT M&G initiatives from slide 19 and list them here. If you've already achieved a quick win, list it and mark it as completed to show what you've accomplished. Briefly outline the objectives, how you plan to achieve the result, and what measurement will indicate success.

      Slide 40. Reflect your CIO Business Vision initiatives from slide 31 here.

      Slide 41. Use this roadmap template to list your initiatives by roughly when they’ll be worked on and completed. Plan for when you’ll update your diagnostics.

      Expert Contributors

      Photo of Alan Fong, Chief Technology Officer, Dealer-FX Alan Fong, Chief Technology Officer, Dealer-FX
      Photo of Andrew Wertkin, Chief Strategy Officer, BlueCat NetworksPhoto of David Penny, Chief Technology Officer, BlueCat Networks Andrew Wertkin, Chief Strategy Officer, BlueCat Networks
      David Penny, Chief Technology Officer, BlueCat Networks
      Photo of Susan Bowen, CEO, Aptum Susan Bowen, CEO, Aptum
      Photo of Erin Bury, CEO, Willful Erin Bury, CEO, Willful
      Photo of Denis Gaudreault, Country Manager, Intel Canada and Latin America Denis Gaudreault, Country Manager, Intel Canada and Latin America
      Photo of Wayne Berger, CEO, IWG Plc Wayne Berger, CEO, IWG Plc
      Photo of Eric Wright, CEO, LexisNexis Canada Eric Wright, CEO, LexisNexis Canada
      Photo of Gary Davenport Gary Davenport, past president of CIO Association” of Canada, former VP of IT, Enterprise Solutions Division, MTS AllStream
      Photo of Jennifer Schaeffer, VP of IT and CIO, Athabasca University Jennifer Schaeffer, VP of IT and CIO, Athabasca University

      Bibliography

      Beaudan, Eric. “Do you have what it takes to be an executive?” The Globe and Mail, 9 July 2018. Web.

      Bersohn, Diana. “Go Live on Day One: The Path to Success for a New CIO.” PDF document. Accenture, 2015. Web.

      Bradt, George. “Executive Onboarding When Promoted From Within To Follow A Successful Leader.” Forbes, 15 Nov. 2018. Web.

      “CIO Stats: Length of CIO Tenure Varies By Industry.” CIO Journal, The Wall Street Journal. 15 Feb. 2017. Web.

      “Enlarging Your Sphere of Influence in Your Organization: Your Learning and Development Guide to Getting People on Side.” MindTools Corporate, 2014.

      “Executive Summary.” The CIO's First 100 Days: A Toolkit. PDF document. Gartner, 2012. Web.

      Forbes, Jeff. “Are You Ready for the C-Suite?” KBRS, n.d. Web.

      Gallo, Carmine. “Tim Cook Uses These 5 Words to Take Control of Any Conversation.” Inc., 9 Aug. 2019. Web.

      Giles, Sunnie. “The Most Important Leadership Competencies, According to Leaders Around the World.” Harvard Business Review, 15 March 2016. Web.

      Godin, Seth. “Ode: How to tell a great story.” Seth's Blog. 27 April 2006. Web.

      Green, Charles W. “The horizontal dimension of race: Social culture.” Hope College Blog Network, 19 Oct. 2014. Web.

      Hakobyan, Hayk. “On Louis Gerstner And IBM.” Hayk Hakobyan, n.d. Web.

      Bibliography

      Hargrove, Robert. Your First 100 Days in a New Executive Job, edited by Susan Youngquist. Kindle Edition. Masterful Coaching Press, 2011.

      Heathfield, Susan M. “Why ‘Blink’ Matters: The Power of Your First Impressions." The Balance Careers, 25 June 2019. Web.

      Hillis, Rowan, and Mark O'Donnell. “How to get off to a flying start in your new job.” Odgers Berndtson, 29 Nov. 2018. Web.

      Karaevli, Ayse, and Edward J. Zajac. “When Is an Outsider CEO a Good Choice?” MIT Sloan Management Review, 19 June 2012. Web.

      Keizer, Gregg. “Microsoft CEO Nadella Aces First-100-Day Test.” Computerworld, 15 May 2014. Web.

      Keller, Scott, and Mary Meaney. “Successfully transitioning to new leadership roles.” McKinsey & Company, May 2018. Web.

      Kress, R. “Director vs. Manager: What You Need to Know to Advance to the Next Step.” Ivy Exec, 2016. Web.

      Levine, Seth. “What does it mean to be an ‘executive’.” VC Adventure, 1 Feb. 2018. Web.

      Lichtenwalner, Benjamin. “CIO First 90 Days.” PDF document. Modern Servant Leader, 2008. Web.

      Nawaz, Sabina. “The Biggest Mistakes New Executives Make.” Harvard Business Review, 15 May 2017. Web.

      Pruitt, Sarah. “Fast Facts on the 'First 100 Days.‘” History.com, 22 Aug. 2018. Web.

      Rao, M.S. “An Action Plan for New CEOs During the First 100 Days.” Training, 4 Oct. 2014. Web.

      Reddy, Kendra. “It turns out being a VP isn't for everyone.” Financial Post, 17 July 2012. Web.

      Silcoff, Sean. “Exclusive: John Chen’s simple plan to save BlackBerry.” The Globe & Mail, 24 Feb. 2014. Web.

      Bibliography

      “Start Stop Continue Retrospective.” GroupMap, n.d. Web.

      Surrette, Mark. “Lack of Rapport: Why Smart Leaders Fail.” KBRS, n.d. Web.

      “Understanding Types of Organization – PMP Study.” Simplilearn, 4 Sept. 2019. Web.

      Wahler, Cindy. “Six Behavioral Traits That Define Executive Presence.” Forbes, 2 July 2015. Web.

      Watkins, Michael D. The First 90 Days, Updated and Expanded. Harvard Business Review Press, 2013.

      Watkins, Michael D. “7 Ways to Set Up a New Hire for Success.” Harvard Business Review, 10 May 2019. Web.

      “What does it mean to be a business executive?” Daniels College of Business, University of Denver, 12 Aug. 2014. Web.

      Yeung, Ken. “Turnaround: Marissa Mayer’s first 300 days as Yahoo’s CEO.” The Next Web, 19 May 2013. Web.

      The Small Enterprise Guide to People and Resource Management

      • Buy Link or Shortcode: {j2store}602|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Train & Develop
      • Parent Category Link: /train-and-develop
      • 52% of small business owners agree that labor quality is their most important problem, and 76% of executives expect the talent market to get even more challenging.
      • The problem? You can't compete on salary, training budgets are slim, you need people skilled in all areas, and even one resignation represents a large part of your workforce.

      Our Advice

      Critical Insight

      • The usual, reactive approach to workforce management is risky:
        • Optimizing tactics helps you hire faster, train more, and negotiate better contracts.
        • But fulfilling needs as they arise costs more, has greater risk of failure, and leaves you unprepared for future needs.
      • In a small enterprise where every resource counts, in which one hire represents 10% of your workforce, it is essential to get it right.

      Impact and Result

      • Workforce planning helps you anticipate future needs.
      • More lead time means better decisions at lower cost.
      • Small Enterprises benefit most, since every resource counts.

      The Small Enterprise Guide to People and Resource Management Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. The Small Enterprise Guide to People and Resource Management Deck – Find out why workforce planning is critical for small enterprises.

      Use this storyboard to lay the foundation of people and resources management practices in your small enterprise IT department.

      • The Small Enterprise Guide to People and Resource Management – Phases 1-3

      2. Workforce Planning Workbook – Use the tool to successfully complete all of the activities required to define and estimate your workforce needs for the future.

      Use these concise exercises to analyze your department’s talent current and future needs and create a skill sourcing strategy to fill the gaps.

      • Workforce Planning Workbook for Small Enterprises

      3. Knowledge Transfer Tools – Use these templates to identify knowledge to be transferred.

      Work through an activity to discover key knowledge held by an employee and create a plan to transfer that knowledge to a successor.

      • IT Knowledge Identification Interview Guide Template
      • IT Knowledge Transfer Plan Template

      4. Development Planning Tools – Use these tools to determine priority development competencies.

      Assess employees’ development needs and draft a development plan that fits with key organizational priorities.

      • IT Competency Library
      • Leadership Competencies Workbook
      • IT Employee Career Development Workbook
      • Individual Competency Development Plan
      • Learning Methods Catalog for IT Employees

      Infographic

      Workshop: The Small Enterprise Guide to People and Resource Management

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Lay Your Foundations

      The Purpose

      Set project direction and analyze workforce needs.

      Key Benefits Achieved

      Planful needs analysis ensures future workforce supports organizational goals.

      Activities

      1.1 Set workforce planning goals and success metrics.

      1.2 Identify key roles and competency gaps.

      1.3 Conduct a risk analysis to identify future needs.

      1.4 Determine readiness of internal successors.

      Outputs

      Work with the leadership team to:

      Extract key business priorities.

      Set your goals.

      Assess workforce needs.

      2 Create Your Workforce Plan

      The Purpose

      Conduct a skill sourcing analysis, and determine competencies to develop internally.

      Key Benefits Achieved

      A careful analysis ensures skills are being sourced in the most efficient way, and internal development is highly aligned with organizational objectives.

      Activities

      2.1 Determine your skill sourcing route.

      2.2 Determine priority competencies for development.

      Outputs

      Create a workforce plan.

      2.Determine guidelines for employee development.

      3 Plan Knowledge Transfer

      The Purpose

      Discover knowledge to be transferred, and build a transfer plan.

      Key Benefits Achieved

      Ensure key knowledge is not lost in the event of a departure.

      Activities

      3.1 Discover knowledge to be transferred.

      3.2 Identify the optimal knowledge transfer methods.

      3.3 Create a knowledge transfer plan.

      Outputs

      Discover tacit and explicit knowledge.

      Create a knowledge transfer roadmap.

      4 Plan Employee Development

      The Purpose

      Create a development plan for all staff.

      Key Benefits Achieved

      A well-structured development plan helps engage and retain employees while driving organizational objectives.

      Activities

      4.1 Identify target competencies & draft development goals

      4.2 Select development activities and schedule check-ins.

      4.3 Build manager coaching skills.

      Outputs

      Assess employees.

      Prioritize development objectives.

      Plan development activities.

      Build management skills.

      Further reading

      The Small Enterprise Guide to People and Resource Management

      Quickly start getting the right people, with the right skills, at the right time

      Is this research right for you?

      Research Navigation

      Managing the people in your department is essential, whether you have three employees or 300. Depending on your available time, resources, and current workforce management maturity, you may choose to focus on the overall essentials, or dive deep into particular areas of talent management. Use the questions below to help guide you to the right Info-Tech resources that best align with your current needs.

      Question If you answered "no" If you answered "yes"

      Does your IT department have fewer than 15 employees, and is your organization's revenue less than $25 million (USD)?

      Review Info-Tech's archive of research for mid-sized and large enterprise clients.

      Follow the guidance in this blueprint.

      Does your organization require a more rigorous and customizable approach to workforce management?

      Follow the guidance in this blueprint.

      Review Info-Tech's archive of research for mid-sized and large enterprise clients.

      Analyst Perspective

      Workforce planning is even more important for small enterprises than large organizations.

      It can be tempting to think of workforce planning as a bureaucratic exercise reserved for the largest and most formal of organizations. But workforce planning is never more important than in small enterprises, where every individual accounts for a significant portion of your overall productivity.

      Without workforce planning, organizations find themselves in reactive mode, hiring new staff as the need arises. They often pay a premium for having to fill a position quickly or suffer productivity losses when a critical role goes unexpectedly vacant.

      A workforce plan helps you anticipate these challenges, come up with solutions to mitigate them, and allocate resources for the most impact, which means a greater return on your workforce investment in the long run.

      This blueprint will help you accomplish this quickly and efficiently. It will also provide you with the essential development and knowledge transfer tools to put your plan into action.

      This is a picture of Jane Kouptsova

      Jane Kouptsova
      Senior Research Analyst, CIO Advisory
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      52% of small business owners agree that labor quality is their most important problem.1

      Almost half of all small businesses face difficulty due to staff turnover.

      76% of executives expect the talent market to get even more challenging.2

      Common Obstacles

      76% of executives expect workforce planning to become a top strategic priority for their organization.2

      But…

      30% of small businesses do not have a formal HR function.3

      Small business leaders are often left at a disadvantage for hiring and retaining the best talent, and they face even more difficulty due to a lack of support from HR.

      Small enterprises must solve the strategic workforce planning problem, but they cannot invest the same time or resources that large enterprises have at their disposal.

      Info-Tech's Approach

      A modular, lightweight approach to workforce planning and talent management, tailored to small enterprises

      Clear activities that guide your team to decisive action

      Founded on your IT strategy, ensuring you have not just good people, but the right people

      Concise yet comprehensive, covering the entire workforce lifecycle from competency planning to development to succession planning and reskilling

      Info-Tech Insight

      Every resource counts. When one hire represents 10% of your workforce, it is essential to get it right.

      1CNBC & SurveyMonkey. 2ADP. 3Clutch.

      Labor quality is small enterprise's biggest challenge

      The key to solving it is strategic workforce planning

      Strategic workforce planning (SWP) is a systematic process designed to identify and address gaps in today's workforce, including pinpointing the human capital needs of the future.

      Linking workforce planning with strategic planning ensures that you have the right people in the right positions, in the right places, at the right time, with the knowledge, skills, and attributes to deliver on strategic business goals.

      SWP helps you understand the makeup of your current workforce and how well prepared it is or isn't (as the case may be) to meet future IT requirements. By identifying capability gaps early, CIOs can prepare to train or develop current staff and minimize the need for severance payouts and hiring costs, while providing clear career paths to retain high performers.

      52%

      of small business owners agree that labor quality is their most important problem.1

      30%

      30% of small businesses have no formal HR function.2

      76%

      of senior leaders expect workforce planning to become the top strategic challenge for their organization.3

      1CNBC & SurveyMonkey. 2Clutch. 3ADP.

      Workforce planning matters more for small enterprises

      You know that staffing mistakes can cost your department dearly. But did you know the costs are greater for small enterprises?

      The price of losing an individual goes beyond the cost of hiring a replacement, which can range from 0.5 to 2 times that employee's salary (Gallup, 2019). Additional costs include loss of productivity, business knowledge, and team morale.

      This is a major challenge for large organizations, but the threat is even greater for small enterprises, where a single individual accounts for a large proportion of IT's productivity. Losing one of a team of 10 means 10% of your total output. If that individual was solely responsible for a critical function, your department now faces a significant gap in its capabilities. And the effect on morale is much greater when everyone is on the same close-knit team.

      And the threat continues when the staffing error causes you not to lose a valuable employee, but to hire the wrong one instead. When a single individual makes up a large percentage of your workforce, as happens on small teams, the effects of talent management errors are magnified.

      A group of 100 triangles is shown above a group of 10 triangles. In each group, one triangle is colored orange, and the rest are colored blue.

      Info-Tech Insight

      One bad hire on a team of 100 is a problem. One bad hire on a team of 10 is a disaster.

      This is an image of Info-Tech's small enterprise guide o people and resource management.

      Blueprint pre-step: Determine your starting point

      People and Resource management is essential for any organization. But depending on your needs, you may want to start at different stages of the process. Use this slide as a quick reference for how the activities in this blueprint fit together, how they relate to other workforce management resources, and the best starting point for you.

      Your IT strategy is an essential input to your workforce plan. It defines your destination, while your workforce is the vessel that carries you there. Ensure you have at least an informal strategy for your department before making major workforce changes, or review Info-Tech's guidance on IT strategy.

      This blueprint covers the parts of workforce management that occur to some extent in every organization:

      • Workforce planning
      • Knowledge transfer
      • Development planning

      You may additionally want to seek guidance on contract and vendor management, if you outsource some part of your workload outside your core IT staff.

      Track metrics

      Consider these example metrics for tracking people and resource management success

      Project Outcome Metric Baseline Target
      Reduced training costs Average cost of training (including facilitation, materials, facilities, equipment, etc.) per IT employee
      Reduced number of overtime hours worked Average hours billed at overtime rate per IT employee
      Reduced length of hiring period Average number of days between job ad posting and new hire start date
      Reduced number of project cancellations due to lack of capacity Total of number of projects cancelled per year
      Increased number of projects completed per year (project throughput) Total number of project completions per year
      Greater net recruitment rate Number of new recruits/Number of terminations and departures
      Reduced turnover and replacement costs Total costs associated with replacing an employee, including position coverage cost, training costs, and productivity loss
      Reduced voluntary turnover rate Number of voluntary departures/Total number of employees
      Reduced productivity loss following a departure or termination Team or role performance metrics (varies by role) vs. one year ago

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

      Guided Implementation

      “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”

      Workshop

      “We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”

      Consulting

      “Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

      Diagnostics and consistent frameworks used throughout all four options

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1 Phase 2 Phase 3

      Call #1:

      Scope requirements, objectives, and your specific challenges.

      Call #2: Assess current workforce needs.

      Call #4: Determine skill sourcing route.

      Call #6:

      Identify knowledge to be transferred.

      Call #8: Draft development goals and select activities.

      Call #3: Explore internal successor readiness.

      Call #5:Set priority development competencies.

      Call #7: Create a knowledge transfer plan.

      Call #9: Build managers' coaching & feedback skills.

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is between 4 to 6 calls over the course of 3 to 4 months.

      Workshop Overview

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889

      Day 1

      Day 2

      Day 3

      Day 4

      Day 5

      1.Lay Your Foundations 2. Create Your Workforce Plan 3. Plan Knowledge Transfer 3. Plan Employee Development Next Steps and Wrap-Up (offsite)
      Activities

      1.1 Set workforce planning goals and success metrics

      1.2 Identify key roles and competency gaps

      1.3 Conduct a risk analysis to identify future needs

      1.4 Determine readiness of internal successors

      1.5 Determine your skill sourcing route

      1.6 Determine priority competencies for development

      3.1 Discover knowledge to be transferred

      3.2 Identify the optimal knowledge transfer methods

      3.3 Create a knowledge transfer plan

      4.1 Identify target competencies & draft development goals

      4.2 Select development activities and schedule check-ins

      4.3 Build manager coaching skills

      Outcomes

      Work with the leadership team to:

      1. Extract key business priorities
      2. Set your goals
      3. Assess workforce needs

      Work with the leadership team to:

      1. Create a workforce plan
      2. Determine guidelines for employee development

      Work with staff and managers to:

      1. Discover tacit and explicit knowledge
      2. Create a knowledge transfer roadmap

      Work with staff and managers to:

      1. Assess employees
      2. Prioritize development objectives
      3. Plan development activities
      4. Build management skills

      Info-Tech analysts complete:

      1. Workshop report
      2. Workforce plan record
      3. Action plan

      Workshop Overview

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889

      Each onsite day is structured with group working sessions from 9-11 a.m. and 1:30-3:30 p.m. and includes Open Analyst Timeslots, where our facilitators are available to expand on scheduled activities, capture and compile workshop results, or review additional components from our comprehensive approach.

      This is a calendar showing days 1-4, and times from 8am-5pm

      Phase 1

      Workforce Planning

      Workforce Planning

      Knowledge Transfer

      Development Planning

      Identify needs, goals, metrics, and skill gaps.

      Select a skill sourcing strategy.

      Discover critical knowledge.

      Select knowledge transfer methods.

      Identify priority competencies.

      Assess employees.

      Draft development goals.

      Provide coaching & feedback.

      The Small Enterprise Guide to People and Resource Management

      Phase Participants

      • Leadership team
      • Managers
      • Human resource partner (if applicable)

      Additional Resources

      Workforce Planning Workbook for Small Enterprises

      Phase pre-step: Gather resources and participants

      1. Ensure you have an up-to-date IT strategy. If you don't have a formal strategy in place, ensure you are aware of the main organizational objectives for the next 3-5 years. Connect with executive stakeholders if necessary to confirm this information.
        If you are not sure of the organizational direction for this time frame, we recommend you consult Info-Tech's material on IT strategy first, to ensure your workforce plan is fully positioned to deliver value to the organization.
      2. Consult with your IT team and gather any documentation pertaining to current roles and skills. Examples include an org chart, job descriptions, a list of current tasks performed/required, a list of company competencies, and a list of outsourced projects.
      3. Gather the right participants. Most of the decisions in this section will be made by senior leadership, but you will also need input from front-line managers. Ensure they are available on an as-needed basis. If your organization has an HR partner, it can also be helpful to involve them in your workforce planning process.

      Formal workforce planning benefits even small teams

      Strategic workforce planning (SWP) is a systematic process designed to identify and address gaps in your workforce today and plan for the human capital needs of the future.

      Your workforce plan is an extension of your IT strategy, ensuring that you have the right people in the right positions, in the right places, at the right time, with the knowledge, skills, and attributes to deliver on strategic business goals.

      SWP helps you understand the makeup of your current workforce and how well prepared it is or isn't (as the case may be) to meet future IT requirements. By identifying capability gaps early, CIOs can prepare to train or develop current staff and minimize the need for severance payouts and hiring costs, while providing clear career paths to retain high performers.

      The smaller the business, the more impact each individual's performance has on the overall success of the organization. When a given role is occupied by a single individual, the organization's performance in that function is determined wholly by one employee. Creating a workforce plan for a small team may seem excessive, but it ensures your organization is not unexpectedly hit with a critical competency gap.

      Right-size your workforce planning process to the size of your enterprise

      Small organizations are 2.2 times more likely to have effective workforce planning processes.1 Be mindful of the opportunities and risks for organizations of your size as you execute the project. How you build your workforce plan will not change drastically based on the size of your organization; however, the scope of your initiative, the size of your team, and the tactics you employ may vary.

      Small Organization

      Medium Organization

      Large Organization

      Project Opportunities

      • Project scope is much more manageable.
      • Communication and planning can be more manageable.
      • Fewer roles can clarify prioritization needs and promotability.
      • Project scope is more manageable.
      • Moderate budget for workforce planning initiatives is needed.
      • Communication and enforcement is easier.
      • Larger candidate pool to pull from.
      • Greater career path options for staff.
      • In-house expertise may be available

      Project Risks

      • Limited resources and time to execute the project.
      • In-house expertise is unlikely.
      • Competencies may be informal and not documented.
      • Limited overlap in responsibilities, resulting in fewer redundancies.
      • Limited staff with experience for the project.
      • Workforce planning may be a lower priority and difficult to generate buy-in for.
      • Requires more staff to manage workforce plan and execute initiatives.
      • Less collective knowledge on staff strengths may make career planning difficult.
      • Geographically dispersed business units make collaboration and communication difficult.

      1 McLean & Company Trends Report 2014

      1.1 Set project outcomes and success metrics

      1-3 hours

      1. As a group, brainstorm key pain points that the IT department experiences due to the lack of a workforce plan. Ask them to consider turnover, retention, training, and talent acquisition.
      2. Discuss any key themes that arise and brainstorm your desired project outcomes. Keep a record of these for future reference and to aid in stakeholder communication.
      3. Break into smaller groups (or if too small, continue as a single group):
        1. For each desired outcome, consider what metrics you could use to track progress. Keep your initial list of pain points in mind as you brainstorm metrics.
        2. Write each of the metric suggestions on a whiteboard and agree to track 3-5 metrics. Set targets for each metric. Consider the effort required to obtain and track the metric, as well as its reliability.
        3. Assign one individual for tracking the selected metrics. Following the meeting, that individual will be responsible for identifying the baseline and targets, and reporting on metrics progress.

      Input

      Output

      • List of workforce data available
      • List of workforce metrics to track the workforce plan's impact

      Materials

      Participants

      • Whiteboard/flip charts
      • Leadership team
      • Human resource partner (if applicable)

      1.2 Identify key roles and competency gaps

      1-3 hours

      1. As a group, identify all strategic, core, and supporting roles by reviewing the organizational chart:
        1. Strategic: What are the roles that must be filled by top performers and cannot be left vacant in order to meet strategic objectives?
        2. Core: What roles are important to drive operational excellence?
        3. Supporting: What roles are required for day-to-day work, but are low risk if the role is vacant for a period of time?
      2. Working individually or in small groups, have managers for each identified role define the level of competence required for the job. Consider factors such as:
        1. The difficulty or criticality of the tasks being performed
        2. The impact on job outcomes
        3. The impact on the performance of other employees
        4. The consequence of errors if the competency is not present
        5. How frequently the competency is used on the job
        6. Whether the competency is required when the job starts or can be learned or acquired on the job within the first six months
      3. Continue working individually and rate the level of proficiency of the current incumbent.
      4. As a group, review the assessment and make any adjustments.

      Record this information in the Workforce Planning Workbook for Small Enterprises.

      Download the Workforce Planning Workbook for Small Enterprises

      1.2 Identify key roles and competency gaps

      Input Output
      • Org chart, job descriptions, list of current tasks performed/required, list of company competencies
      • List of competency gaps for key roles
      Materials Participants
      • Leadership team
      • Managers

      Conduct a risk-of-departure analysis

      A risk-of-departure analysis helps you plan for future talent needs by identifying which employees are most likely to leave the organization (or their current role).

      A risk analysis takes into account two factors: an employee's risk for departure and the impact of departure:

      Employees are high risk for departure if they:

      • Have specialized or in-demand skills (tenured employees are more likely to have this than recent hires)
      • Are nearing retirement
      • Have expressed career aspirations that extend outside your organization
      • Have hit a career development ceiling at your organization
      • Are disengaged
      • Are actively job searching
      • Are facing performance issues or dismissal OR promotion into a new role

      Employees are low risk for departure if they:

      • Are a new hire or new to their role
      • Are highly engaged
      • Have high potential
      • Are 5-10 years out from retirement

      If you are not sure where an employee stands with respect to leaving the organization, consider having a development conversation with them. In the meantime, consider them at medium risk for departure.

      To estimate the impact of departure, consider:

      • The effect of losing the employee in the near- and medium-term, including:
        • Impact on the organization, department, unit/team and projects
        • The cost (in time, resources, and productivity loss) to replace the individual
        • The readiness of internal successors for the role

      1.3 Conduct a risk analysis to identify future needs

      1-3 hours

      Preparation: Your estimation of whether key employees are at risk of leaving the organization will depend on what you know of them objectively (skills, age), as well as what you learn from development conversations. Ensure you collect all relevant information prior to conducting this activity. You may need to speak with employees' direct managers beforehand or include them in the discussion.

      • As a group, list all your current employees, and using the previous slide for guidance, rank them on two parameters: risk of departure and impact of departure, on a scale of low to high. Record your conclusions in a chart like the one on the right. (For a more in-depth risk assessment, use the "Risk Assessment Results" tab of the Key Roles Succession Planning Tool.)
      • Employees that fall in the "Mitigate" quadrant represent key at-risk roles with at least moderate risk and moderate impact. These are your succession planning priorities. Add these roles to your list of key roles and competency gaps, and include them in your workforce planning analysis.
      • Employees that fall in the "Manage" quadrants represent secondary priorities, which should be looked at if there is capacity after considering the "Mitigate" roles.

      Record this information in the Workforce Planning Workbook for Small Enterprises.

      This is an image of the Risk analysis for risk of departure to importance of departure.

      Info-Tech Insight

      Don't be afraid to rank most or all your staff as "high impact of departure." In a small enterprise, every player counts, and you must plan accordingly.

      1.3 Conduct a risk analysis to identify future needs

      Input Output
      • Employee data on competencies, skills, certifications, and performance. Input from managers from informal development conversations.
      • A list of first- and second-priority at-risk roles to carry forward into a succession planning analysis
      Materials Participants
      • Leadership team
      • Managers

      Determine your skill sourcing route

      The characteristics of need steer hiring managers to a preferred choice, while the marketplace analysis will tell you the feasibility of each option.

      Sourcing Options

      Preferred Options

      Final Choice

      four blue circles

      A right facing arrow

      Two blue circles A right facing arrow One blue circle
      State of the Marketplace

      State of the Marketplace

      Urgency: How soon do we need this skill? What is the required time-to-value?

      Criticality: How critical, i.e. core to business goals, are the services or systems that this skill will support?

      Novelty: Is this skill brand new to our workforce?

      Availability: How often, and at what hours, will the skill be needed?

      Durability: For how long will this skill be needed? Just once, or indefinitely for regular operations?

      Scarcity: How popular or desirable is this skill? Do we have a large enough talent pool to draw from? What competition are we facing for top talent?

      Cost: How much will it cost to hire vs. contract vs. outsource vs. train this skill?

      Preparedness: Do we have internal resources available to cultivate this skill in house?

      1.4 Determine your skill sourcing route

      1-3 hours

      1. Identify the preferred sourcing method as a group, starting with the most critical or urgent skill need on your list. Use the characteristics of need to guide your discussion. If more than one option seems adequate, carry several over to the next step.
      2. Consider the marketplace factors applicable to the skill in question and use these to narrow down to one final sourcing decision.
        1. If it is not clear whether a suitable internal candidate is available or ready, refer to the next activity for a readiness assessment.
      3. Be sure to document the rationale supporting your decision. This will ensure the decision can be clearly communicated to any stakeholders, and that you can review on your decision-making process down the line.

      Record this information in the Workforce Planning Workbook for Small Enterprises.

      Info-Tech Insight

      Consider developing a pool of successors instead of pinning your hopes on just one person. A single pool of successors can be developed for either one key role that has specialized requirements or even multiple key roles that have generic requirements.

      Input

      Output

      • List of current and upcoming skill gaps
      • A sourcing decision for each skill

      Materials

      Participants

      • Leadership team
      • Human resource partner (if applicable)

      1.5 Determine readiness of internal successors

      1-3 hours

      1. As a group, and ensuring you include the candidates' direct managers, identify potential successors for the first role on your list.
      2. Ask how effectively the potential successor would serve in the role today. Review the competencies for the key role in terms of:
        1. Relationship-building skills
        2. Business skills
        3. Technical skills
        4. Industry-specific skills or knowledge
      3. Determine what competencies the succession candidate currently has and what must be learned. Be sure you know whether the candidate is open to a career change. Don't assume – if this is not clear, have a development conversation to ensure everyone is on the same page.
      4. Finally, determine how difficult it will be for the successor to acquire missing skills or knowledge, whether the resources are available to provide the required development, and how long it will take to provide it.
      5. As a group, decide whether training an internal successor is a viable option for the role in question, considering the successor's readiness and the characteristics of need for the role. If a clear successor is not readily apparent, consider:
        1. If the development of the successor can be fast-tracked, or if some requirements can be deprioritized and the successor provided with temporary support from other employees.
        2. If the role in question is being discussed because the current incumbent is preparing to leave, consider negotiating an arrangement that extends the incumbent's employment tenure.
      6. Record the decision and repeat for the next role on your list.

      Info-Tech Insight

      A readiness assessment helps to define not just development needs, but also any risks around the organization's ability to fill a key role.

      Input

      Output

      • List of roles for which you are considering training internally
      • Job descriptions and competency requirements for the roles
      • List of roles for which internal successors are a viable option

      Materials

      Participants

      • Leadership team
      • Candidates' direct managers, if applicable

      Use alternative work arrangements to gain time to prepare successors

      Alternative work arrangements are critical tools that employers can use to achieve a mutually beneficial solution that mitigates the risk of loss associated with key roles.

      Alternative work arrangements not only support employees who want to keep working, but more importantly, they allow the business to retain employees that are needed in key roles who are departure risks due to retirement.

      Viewing retirement as a gradual process can help you slow down skill loss in your organization and ensure you have sufficient time to train successors. Retiring workers are becoming increasingly open to alternative work arrangements. Among employed workers aged 50-75, more than half planned to continue working part-time after retirement.
      Source: Statistics Canada.

      Flexible work options are the most used form of alternative work arrangement

      A bar graph showing the percent of organizations who implemented alternate work arrangement, for Flexible work options; Contract based work; Part time roles; Graduated retirement programs; Part year jobs or job sharing; Increased PTO for employees over a certain age.

      Source: McLean & Company, N=44

      Choose the alternative work arrangement that works best for you and the employee

      Alternative Work Arrangement Description Ideal Use Caveats
      Flexible work options Employees work the same number of hours but have flexibility in when and where they work (e.g. from home, evenings). Employees who work fairly independently with no or few direct reports. Employee may become isolated or disconnected, impeding knowledge transfer methods that require interaction or one-on-one time.
      Contract-based work Working for a defined period of time on a specific project on a non-salaried or non-wage basis. Project-oriented work that requires specialized knowledge or skills. Available work may be sporadic or specific projects more intensive than the employee wants. Knowledge transfer must be built into the contractual arrangement.
      Part-time roles Half days or a certain number of days per week; indefinite with no end date in mind. Employees whose roles can be readily narrowed and upon whom people and critical processes are not dependent. It may be difficult to break a traditionally full-time job down into a part-time role given the size and nature of associated tasks.
      Graduated retirement Retiring employee has a set retirement date, gradually reducing hours worked per week over time. Roles where a successor has been identified and is available to work alongside the incumbent in an overlapping capacity while he or she learns. The role may only require a single FTE, and the organization may not be able to afford the amount of redundancy inherent in this arrangement.

      Choose the alternative work arrangement that works best for you and the employee

      Alternative Work Arrangement Description Ideal Use Caveats
      Part-year jobs or job sharing Working part of the year and having the rest of the year off, unpaid. Project-oriented work where ongoing external relationships do not need to be maintained. The employee is unavailable for knowledge transfer activities for a large portion of the year. Another risk is that the employee may opt not to return at the end of the extended time off with little notice.
      Increased paid time off Additional vacation days upon reaching a certain age. Best used as recognition or reward for long-term service. This may be a particularly useful retention incentive in organizations that do not offer pension plans. The company may not be able to financially afford to pay for such extensive time off. If the role incumbent is the only one in the role, this may mean crucial work is not being done.
      Altered roles Concentration of a job description on fewer tasks that allows the employee to focus on his or her specific expertise. Roles where a successor has been identified and is available to work alongside the incumbent, with the incumbent's new role highly focused on mentoring. The role may only require a single FTE, and the organization may not be able to afford the amount of redundancy inherent in this arrangement.

      Phase 2

      Knowledge Transfer

      Workforce Planning

      Knowledge Transfer

      Development Planning

      Identify needs, goals, metrics, and skill gaps.

      Select a skill sourcing strategy.

      Discover critical knowledge.

      Select knowledge transfer methods.

      Identify priority competencies.

      Assess employees.

      Draft development goals.

      Provide coaching & feedback.

      The Small Enterprise Guide to People and Resource Management

      Phase Participants

      • Leadership/management team
      • Incumbent & successor

      Additional Resources

      IT Knowledge Identification Interview Guide Template

      Knowledge Transfer Plan Template

      Determine your skill sourcing route

      Knowledge transfer plans have three key components that you need to complete for each knowledge source:

      Define what knowledge needs to be transferred

      Each knowledge source has unique information which needs to be transferred. Chances are you don't know what you don't know. The first step is therefore to interview knowledge sources to find out.

      Identify the knowledge receiver

      Depending on who the information is going to, the knowledge transfer tactic you employ will differ. Before deciding on the knowledge receiver and tactic, consider three key factors:

      • How will this knowledge be used in the future?
      • What is the next career step for the knowledge receiver?
      • Are the receiver and the source going to be in the same location?

      Identify which knowledge transfer tactics you will use for each knowledge asset

      Not all tactics are good in every situation. Always keep the "knowledge type" (information, process, skills, and expertise), knowledge sources' engagement level, and the knowledge receiver in mind as you select tactics.

      Don't miss tacit knowledge

      There are two basic types of knowledge: "explicit" and "tacit." Ensure you capture both to get a well-rounded overview of the role.

      Explicit Tacit
      • "What knowledge" – knowledge can be articulated, codified, and easily communicated.
      • Easily explained and captured – documents, memos, speeches, books, manuals, process diagrams, facts, etc.
      • Learn through reading or being told.
      • "How knowledge" – intangible knowledge from an individual's experience that is more from the process of learning, understanding, and applying information (insights, judgments, and intuition).
      • Hard to verbalize, and difficult to capture and quantify.
      • Learn through observation, imitation, and practice.

      Types of explicit knowledge

      Types of tacit knowledge

      Information Process Skills Expertise

      Specialized technical knowledge.

      Unique design capabilities/methods/models.

      Legacy systems, details, passwords.

      Special formulas/algorithms/ techniques/contacts.

      • Specialized research & development processes.
      • Proprietary production processes.
      • Decision-making processes.
      • Legacy systems.
      • Variations from documented processes.
      • Techniques for executing on processes.
      • Relationship management.
      • Competencies built through deliberate practice enabling someone to act effectively.
      • Company history and values.
      • Relationships with key stakeholders.
      • Tips and tricks.
      • Competitor history and differentiators.

      e.g. Knowing the lyrics to a song, building a bike, knowing the alphabet, watching a YouTube video on karate.

      e.g. Playing the piano, riding a bike, reading or speaking a language, earning a black belt in karate.

      Embed your knowledge transfer methods into day-to-day practice

      Multiple methods should be used to transfer as much of a person's knowledge as possible, and mentoring should always be one of them. Select your method according to the following criteria:

      Info-Tech Insight

      The more integrated knowledge transfer is in day-to-day activities, the more likely it is to be successful, and the lower the time cost. This is because real learning is happening at the same time real work is being accomplished.

      Type of Knowledge

      • Tacit knowledge transfer methods are often informal and interactive:
        • Mentoring
        • Multi-generational work teams
        • Networks and communities
        • Job shadowing
      • Explicit knowledge transfer methods tend to be more formal and one way:
        • Formal documentation of processes and best practices
        • Self-published knowledge bases
        • Formal training sessions
        • Formal interviews

      Incumbent's Preference/Successor's Preference

      Ensure you consult the employees, and their direct manager, on the way they are best prepared to teach and learn. Some examples of preferences include:

      1. Prefer traditional classroom learning, augmented with participation, critical reflection, and feedback.
      2. May get bored during formal training sessions and retain more during job shadowing.
      3. Prefer to be self-directed or self-paced, and highly receptive to e-learning and media.
      4. Prefer informal, incidental learning, tend to go immediately to technology or direct access to people. May have a short attention span and be motivated by instant results.
      5. May be uncomfortable with blogs and wikis, but comfortable with SharePoint.

      Cost

      Consider costs beyond the monetary. Some methods require an investment in time (e.g. mentoring), while others require an investment in technology (e.g. knowledge bases).

      The good news is that many supporting technologies may already exist in your organization or can be acquired for free.

      Methods that cost time may be difficult to get underway since employees may feel they don't have the time or must change the way they work.

      2.1 Create a knowledge transfer plan

      1-3 hours

      1. Working together with the current incumbent, brainstorm the key information pertaining to the role that you want to pass on to the successor. Use the IT Knowledge Identification Interview Guide Template to ensure you don't miss anything.
        • Consider key knowledge areas, including:
          • Specialized technical knowledge.
          • Specialized research and development processes.
          • Unique design capabilities/methods/models.
          • Special formulas/algorithms/techniques.
          • Proprietary production processes.
          • Decision-making criteria.
          • Innovative sales methods.
          • Knowledge about key customers.
          • Relationships with key stakeholders.
          • Company history and values.
        • Ask questions of both sources and receivers of knowledge to help determine the best knowledge transfer methods to use.
          • What is the nature of the knowledge? Explicit or tacit?
          • Why is it important to transfer?
          • How will the knowledge be used?
          • What knowledge is critical for success?
          • How will the users find and access it?
          • How will it be maintained and remain relevant and usable?
          • What are the existing knowledge pathways or networks connecting sources to recipients?
      2. Once the knowledge has been identified, use the information on the following slides to decide on the most appropriate methods. Be sure to consult the incumbent and successor on their preferences.
      3. Prioritize your list of knowledge transfer activities. It's important not to try to do too much too quickly. Focus on some quick wins and leverage the success of these initiatives to drive the project forward. Follow these steps as a guide:
        1. Take an inventory of all the tactics and techniques which you plan to employ. Eliminate redundancies where possible.
        2. Start your implementation with your highest risk role or knowledge item, using explicit knowledge transfer tactics. Interviews, use cases, and process mapping will give you some quick wins and will help gain momentum for the project.
        3. Then move forward to other tactics, the majority of which will require training and process design. Pick 1-2 other key tactics you would like to employ and build those out. For tactics that require resources or monetary investment, start with those that can be reused for multiple roles.

      Record your plan in the IT Knowledge Transfer Plan Template.

      Download the IT Knowledge Identification Interview Guide Template

      Download the Knowledge Transfer Plan Template

      Info-Tech Insight

      Wherever possible, ask employees about their personal learning styles. It's likely that a collaborative compromise will have to be struck for knowledge transfer to work well.

      2.1 Create a knowledge transfer plan

      Input

      Output

      • List of roles for which you need to transfer knowledge
      • Prioritized list of knowledge items and chosen transfer method

      Materials

      Participants

      • Leadership team
      • Incumbent
      • Successor

      Not every transfer method is effective for every type of knowledge

      Knowledge Type
      Tactic Explicit Tacit
      Information Process Skills Expertise
      Interviews Very Strong Strong Strong Strong
      Process Mapping Medium Very Strong Very Weak Very Weak
      Use Cases Medium Very Strong Very Weak Very Weak
      Job Shadow Very Weak Medium Very Strong Very Strong
      Peer Assist Strong Medium Very Strong Very Strong
      Action Review Medium Medium Strong Strong
      Mentoring Weak Weak Strong Very Strong
      Transition Workshop Strong Strong Strong Weak
      Storytelling Weak Weak Strong Very Strong
      Job Share Weak Weak Very Strong Very Strong
      Communities of Practice Strong Weak Very Strong Very Strong

      This table shows the relative strengths and weaknesses of each knowledge transfer tactic compared against four different knowledge types.

      Not all techniques are effective for all types of knowledge; it is important to use a healthy mixture of techniques to optimize effectiveness.

      Employees' engagement can impact knowledge transfer effectiveness

      Level of Engagement
      Tactic Disengaged/ Indifferent Almost Engaged - Engaged
      Interviews Yes Yes
      Process Mapping Yes Yes
      Use Cases Yes Yes
      Job Shadow No Yes
      Peer Assist Yes Yes
      Action Review Yes Yes
      Mentoring No Yes
      Transition Workshop Yes Yes
      Storytelling No Yes
      Job Share Maybe Yes
      Communities of Practice Maybe Yes

      When considering which tactics to employ, it's important to consider the knowledge holder's level of engagement. Employees who you would identify as being disengaged may not make good candidates for job shadowing, mentoring, or other tactics where they are required to do additional work or are asked to influence others.

      Knowledge transfer can be controversial for all employees as it can cause feelings of job insecurity. It's essential that motivations for knowledge transfer are communicated effectively.

      Pay particular attention to your communication style with disengaged and indifferent employees, communicate frequently, and tie communication back to what's in it for them.

      Putting disengaged employees in a position where they are mentoring others can be a risk, as their negativity could influence others not to participate, or it could negate the work you're doing to create a positive knowledge sharing culture.

      Employees' engagement can impact knowledge transfer effectiveness

      Effort by Stakeholder

      Tactic

      Business Analyst

      IT Manager

      Knowledge Holder

      Knowledge Receiver

      Interviews

      These tactics require the least amount of effort, especially for organizations that are already using these tactics for a traditional requirements gathering process.

      Medium

      N/A

      Low

      Low

      Process Mapping

      Medium

      N/A

      Low

      Low

      Use Cases

      Medium

      N/A

      Low

      Low

      Job Shadow

      Medium

      Medium

      Medium

      Medium

      Peer Assist

      Medium

      Medium

      Medium

      Medium

      Action Review

      These tactics generally require more involvement from IT management and the BA in tandem for preparation. They will also require ongoing effort for all stakeholders. It's important to gain stakeholder buy-in as it is key for success.

      Low

      Medium

      Medium

      Low

      Mentoring

      Medium

      High

      High

      Medium

      Transition Workshop

      Medium

      Low

      Medium

      Low

      Storytelling

      Medium

      Medium

      Low

      Low

      Job Share

      Medium

      High

      Medium

      Medium

      Communities of Practice

      High

      Medium

      Medium

      Medium

      Phase 3

      Development Planning

      Workforce Planning

      Knowledge Transfer

      Development Planning

      Identify needs, goals, metrics, and skill gaps.

      Select a skill sourcing strategy.

      Discover critical knowledge.

      Select knowledge transfer methods.

      Identify priority competencies.

      Assess employees.

      Draft development goals.

      Provide coaching & feedback.

      The Small Enterprise Guide to People and Resource Management

      Phase Participants

      • Leadership team
      • Managers
      • Employees

      Additional Resources

      Effective development planning hinges on robust performance management

      Your performance management framework is rooted in organizational goals and defines what it means to do any given role well.

      Your organization's priority competencies are the knowledge, skills and attributes that enable an employee to do the job well.

      Each individual's development goals are then aimed at building these priority competencies.

      Mission Statement

      To be the world's leading manufacturer and distributor of widgets.

      Business Goal

      To increase annual revenue by 10%.

      IT Department Objective

      To ensure reliable communications infrastructure and efficient support for our sales and development teams.

      Individual Role Objective

      To decrease time to resolution of support requests by 10% while maintaining quality.

      Info-Tech Insight

      Without a performance management framework, your employees cannot align their development with the organization's goals. For detailed guidance, see Info-Tech's blueprint Setting Meaningful Employee Performance Measures.

      What is a competency?

      The term "competency" refers to the collection of knowledge, skills, and attributes an employee requires to do a job well.

      Often organizations have competency frameworks that consist of core, leadership, and functional competencies.

      Core competencies apply to every role in the organization. Typically, they are tied to organizational values and business mission and/or vision.

      Functional competencies are at the department, work group, or job role levels. They are a direct reflection of the function or type of work carried out.

      Leadership competencies generally apply only to people managers in the organization. Typically, they are tied to strategic goals in the short to medium term

      Generic Functional
      • Core
      • Leadership
      • IT
      • Finance
      • Sales
      • HR

      Use the SMART model to make sure goals are reasonable and attainable

      S

      Specific: Be specific about what you want to accomplish. Think about who needs to be involved, what you're trying to accomplish, and when the goal should be met.

      M

      Measurable: Set metrics that will help to determine whether the goal has been reached.

      A

      Achievable: Ensure that you have both the organizational resources and employee capability to accomplish the goal.

      R

      Relevant: Goals must align with broader business, department, and development goals in order to be meaningful.

      T

      Time-bound: Provide a target date to ensure the goal is achievable and provide motivation.

      Example goal:

      "Learn Excel this summer."

      Problems:

      Not specific enough, not measurable enough, nor time bound.

      Alternate SMART goal:

      "Consult with our Excel expert and take the lead on creating an Excel tool in August."

      3.2 Identify target competencies & draft development goals

      1 hour

      Pre-work: Employees should come to the career conversation having done some self-reflection. Use Info-Tech's IT Employee Career Development Workbook to help employees identify their career goals.

      1. Pre-work: Managers should gather any data they have on the employee's current proficiency at key competencies. Potential sources include task-based assessments, performance ratings, supervisor or peer feedback, and informal conversation.

        Prioritize competencies. Using your list of priority organizational competencies, work with your employees to help them identify two to four competencies to focus on developing now and in the future. Use the Individual Competency Development Plan template to document your assessment and prioritize competencies for development. Consider the following questions for guidance:
        1. Which competencies are needed in my current role that I do not have full proficiency in?
        2. Which competencies are related to both my career interests and the organization's priorities?
        3. Which competencies are related to each other and could be developed together or simultaneously?
      2. Draft goals. Ask your employee to create a list of multiple simple goals to develop the competencies they have selected to work on developing over the next year. Identifying multiple goals helps to break development down into manageable chunks. Ensure goals are concrete, for example, if the competency is "communication skills," your development goals could be "presentation skills" and "business writing."
      3. Review goals:
        1. Ask why these areas are important to the employee.
        2. Share your ideas and why it is important that the employee develop in the areas identified.
        3. Ensure that the goals are realistic. They should be stretch goals, but they must be achievable. Use the SMART framework on the previous slide for guidance.

      Info-Tech Insight

      Lack of career development is the top reason employees leave organizations. Development activities need to work for both the organization and the employee's own development, and clearly link to advancing employees' careers either at the organization or beyond.

      Download the IT Employee Career Development Workbook

      Download the Individual Competency Development Plan

      3.2 Identify target competencies & draft development goals

      Input

      Output

      • Employee's career aspirations
      • List of priority organizational competencies
      • Assessment of employee's current proficiency
      • A list of concrete development goals

      Materials

      Participants

      • Employee
      • Direct manager

      Apply a blend of learning methods

      • Info-Tech recommends the 70-20-10 principle for learning and development, which places the greatest emphasis on learning by doing. This experiential learning is then supported by feedback from mentoring, training, and self-reflection.
      • Use the 70-20-10 principle as a guideline – the actual breakdown of your learning methods will need to be tailored to best suit your organization and the employee's goals.

      Spend development time and effort wisely:

      70%

      On providing challenging on-the-job opportunities

      20%

      On establishing opportunities for people to develop learning relationships with others, such as coaching and mentoring

      10%

      On formal learning and training programs

      Internal initiatives are a cost-effective development aid

      Internal Initiative

      What Is It?

      When to Use It

      Special Project

      Assignment outside of the scope of the day-to-day job (e.g. work with another team on a short-term initiative).

      As an opportunity to increase exposure and to expand skills beyond those required for the current job.

      Stretch Assignment

      The same projects that would normally be assigned, but in a shorter time frame or with a more challenging component.

      Employee is consistently meeting targets and you need to see what they're capable of.

      Training Others

      Training new or more junior employees on their position or a specific process.

      Employee wants to expand their role and responsibility and is proficient and positive.

      Team Lead On an Assignment

      Team lead for part of a project or new initiative.

      To prepare an employee for future leadership roles by increasing responsibility and developing basic managerial skills.

      Job Rotation

      A planned placement of employees across various roles in a department or organization for a set period of time.

      Employee is successfully meeting and/or exceeding job expectations in their current role.

      Incorporating a development objective into daily tasks

      What do we mean by incorporating into daily tasks?

      The next time you assign a project to an employee, you should also ask the employee to think about a development goal for the project. Try to link it back to their existing goals or have them document a new goal in their development plan.

      For example: A team of employees always divides their work in the same way. Their goal for their next project could be to change up the division of responsibility so they can learn each other's roles.

      Another example:

      "I'd like you to develop your ability to explain technical terms to a non-technical audience. I'd like you to sit down with the new employee who starts tomorrow and explain how to use all our software, getting them up and running."

      Info-Tech Insight

      Employees often don't realize that they are being developed. They either think they are being recognized for good work or they are resentful of the additional workload.

      You need to tell your employees that the activity you are asking them to do is intended to further their development.

      However, be careful not to sell mundane tasks as development opportunities – this is offensive and detrimental to engagement.

      Establish manager and employee accountability for following up

      Ensure that the employee makes progress in developing prioritized competencies by defining accountabilities:

      Tracking Progress

      Checking In

      Development Meetings

      Coaching & Feedback

      Employee accountability:

      • Employees need to keep track of what they learn.
      • Employees should take the time to reflect on their progress.

      Manager accountability:

      • Managers need to make the time for employees to reflect.

      Employee accountability:

      • Employees need to provide managers with updates and ask for help.

      Manager accountability:

      • Managers need to check in with employees to see if they need additional resources.

      Employee accountability:

      • Employees need to complete assessments again to determine whether they have made progress.

      Manager accountability:

      • Managers should schedule monthly meetings to discuss progress and identify next steps.

      Employee accountability:

      • Employees should ask their manager and colleagues for feedback after development activities.

      Manager accountability:

      • Managers can use both scheduled meetings and informal conversations to provide coaching and feedback to employees.

      3.3 Select development activities and schedule check-ins

      1-3 hours

      Pre-work: Employees should research potential development activities and come prepared with a range of suggestions.

      Pre-work: Managers should investigate options for employee development, such as internal training/practice opportunities for the employee's selected competencies and availability of training budget.

      1. Communicate your findings about internal opportunities and external training allowance to the employee. This can also be done prior to the meeting, to help guide the employee's own research. Address any questions or concerns.
      2. Review the employee's proposed list of activities, and identify priority ones based on:
        1. How effectively they support the development of priority competencies.
        2. How closely they match the employee's original goals.
        3. The learning methods they employ, and whether the chosen activities support a mix of different methods.
        4. The degree to which the employee will have a chance to practice new skills hands-on.
        5. The amount of time the activities require, balanced against the employee's work obligations.
      3. Guide the employee in selecting activities for the short and medium term. Establish an understanding that this list is tentative and subject to ongoing revision during future check-ins.
        1. If in doubt about whether the employee is over-committing, err on the side of fewer activities to start.
      4. Schedule a check-in for one month out to review progress and roadblocks, and to reaffirm priorities.
      5. Check-ins should be repeated regularly, typically once a month.

      Download the Learning Methods Catalog

      Info-Tech Insight

      Adopt a blended learning approach using a variety of techniques to effectively develop competencies. This will reinforce learning and accommodate different learning styles. See Info-Tech's Learning Methods Catalog for a description of popular experiential, relational, and formal learning methods.

      3.3 Select development activities and schedule check-ins

      Input

      Output

      • List of potential development activities (from employee)
      • List of organizational resources (from manager)
      • A selection of feasible development activities
      • Next check-in scheduled

      Materials

      Participants

      • Employee
      • Direct manager

      Tips for tricky conversations about development

      What to do if…

      Employees aren't interested in development:

      • They may have low aspiration for advancement.
      • Remind them about the importance of staying current in their role given increasing job requirements.
      • Explain that skill development will make their job easier and make them more successful at it; sell development as a quick and effective way to learn the skill.
      • Indicate your support and respond to concerns.

      Employees have greater aspiration than capability:

      • Explain that there are a number of skills and capabilities that they need to improve in order to move to the next level. If the specific skills were not discussed during the performance appraisal, do not hesitate to explain the improvements that you require.
      • Inform the employee that you want them to succeed and that by pushing too far and too fast they risk failure, which would not be beneficial to anyone.
      • Reinforce that they need to do their current job well before they can be considered for promotion.

      Employees are offended by your suggestions:

      • Try to understand why they are offended. Before moving forward, clarify whether they disagree with the need for development or the method by which you are recommending they be developed.
      • If it is because you told them they had development needs, then reiterate that this is about helping them to become better and that everyone has areas to develop.
      • If it is about the development method, discuss the different options, including the pros and cons of each.

      Coaching and feedback skills help managers guide employee development

      Coaching and providing feedback are often confused. Managers often believe they are coaching when they are just giving feedback. Learn the difference and apply the right approach for the right situation.

      What is coaching?

      A conversation in which a manager asks questions to guide employees to solve problems themselves.

      Coaching is:

      • Future-focused
      • Collaborative
      • Geared toward growth and development

      What is feedback?

      Information conveyed from the manager to the employee about their performance.

      Feedback is:

      • Past-focused
      • Prescriptive
      • Geared toward behavior and performance

      Info-Tech Insight

      Don't forget to develop your managers! Ensure coaching, feedback, and management skills are part of your management team's development plan.

      Understand the foundations of coaching to provide effective development coaching:

      Knowledge Mindset Relationship
      • Understand what coaching is and how to apply it:
      • Identify when to use coaching, feedback, or other people management practices, and how to switch between them.
      • Know what coaching can and cannot accomplish.
      • When focusing on performance, guide an employee to solve problems related to their work. When focusing on development, guide an employee to reach their own development goals.
      • Adopt a coaching mindset by subscribing to the following beliefs:
      • Employees want to achieve higher performance and have the potential to do so.
      • Employees have a unique and valuable perspective to share of the challenges they face as well as the possible solutions.
      • Employees should be empowered to realize solutions themselves to motivate them in achieving goals.
      • Develop a relationship of trust between managers and employees:
      • Create an environment of psychological safety where employees feel safe to be open and honest.
      • Involve employees in decision making and inform employees often.
      • Invest in employees' success.
      • Give and expect candor.
      • Embrace failure.

      Apply the "4A" behavior-focused coaching model

      Using a model allows every manager, even those with little experience, to apply coaching best practices effectively.

      Actively Listen

      Ask

      Action Plan

      Adapt

      Engage with employees and their message, rather than just hearing their message.

      Key active listening behaviors:

      • Provide your undivided attention.
      • Observe both spoken words and body language.
      • Genuinely try to understand what the employee is saying.
      • Listen to what is being said, then paraphrase back what you heard.

      Ask thoughtful, powerful questions to learn more information and guide employees to uncover opportunities and/or solutions.

      Key asking behaviors:

      • Ask open-ended questions.
      • Ask questions to learn something you didn't already know.
      • Ask for reasoning (the why).
      • Ask "what else?"

      Hold employees and managers accountable for progress and results.

      During check-ins, review each development goal to ensure employees are meeting their targets.

      Key action planning behaviors:

      Adapt to individual employees and situations.

      Key adapting behaviors:

      • Recognize employees' unique characteristics.
      • Appreciate the situation at hand and change your behavior and communication in order to best support the individual employee.

      Use the following questions to have meaningful coaching conversations

      Opening Questions

      • What's on your mind?
      • Do you feel you've had a good week/month?
      • What is the ideal situation?
      • What else?

      Problem-Identifying Questions

      • What is most important here?
      • What is the challenge here for you?
      • What is the real challenge here for you?
      • What is getting in the way of you achieving your goal?

      Problem-Solving Questions

      • What are some of the options available?
      • What have you already tried to solve this problem? What worked? What didn't work?
      • Have you considered all the possibilities?
      • How can I help?

      Next-Steps Questions

      • What do you need to do, and when, to achieve your goal?
      • What resources are there to help you achieve your goal? This includes people, tools, or even resources outside our organization.
      • How will you know when you have achieved your goal? What does success look like?

      The purpose of asking questions is to guide the conversation and learn something you didn't already know. Choose the questions you ask based on the flow of the conversation and on what information you would like to uncover. Approach the answers you get with an open mind.

      Info-Tech Insight

      Avoid the trap of "hidden agenda" questions, whose real purpose is to offer your own advice.

      Use the following approach to give effective feedback

      Provide the feedback in a timely manner

      • Plan the message you want to convey.
      • Provide feedback "just-in-time."
      • Ensure recipient is not preoccupied.
      • Try to balance the feedback; refer to successful as well as unsuccessful behavior.

      Communicate clearly, using specific examples and alternative behaviors

      • Feedback must be honest and helpful.
      • Be specific and give a recent example.
      • Be descriptive, not evaluative.
      • Relate feedback to behaviors that can be changed.
      • Give an alternative positive behavior.

      Confirm their agreement and understanding

      • Solicit their thoughts on the feedback.
      • Clarify if not understood; try another example.
      • Confirm recipient understands and accepts the feedback.

      Manager skill is crucial to employee development

      Development is a two-way street. This means that while employees are responsible for putting in the work, managers must enable their development with support and guidance. The latter is a skill, which managers must consciously cultivate.

      For more in-depth management skills development, see the Info-Tech "Build a Better Manager" training resources:

      Bibliography

      Anderson, Kelsie. "Is Your IT Department Prepared for the 4 Biggest Challenges of 2017?" 14 June 2017.
      Atkinson, Carol, and Peter Sandiford. "An Exploration of Older Worker Flexible Working Arrangements in Smaller Firms." Human Resource Management Journal, vol. 26, no. 1, 2016, pp. 12–28. Wiley Online Library.
      BasuMallick, Chiradeep. "Top 8 Best Practices for Employee Cross-Training." Spiceworks, 15 June 2020.
      Birol, Andy. "4 Ways You Can Succeed With a Staff That 'Wears Multiple Hats.'" The Business Journals, 26 Nov. 2013.
      Bleich, Corey. "6 Major Benefits To Cross-Training Employees." EdgePoint Learning, 5 Dec. 2018.
      Cancialosi, Chris. "Cross-Training: Your Best Defense Against Indispensable Employees." Forbes, 15 Sept. 2014.
      Cappelli, Peter, and Anna Tavis. "HR Goes Agile." Harvard Business Review, Mar. 2018.
      Chung, Kai Li, and Norma D'Annunzio-Green. "Talent Management Practices of SMEs in the Hospitality Sector: An Entrepreneurial Owner-Manager Perspective." Worldwide Hospitality and Tourism Themes, vol. 10, no. 4, Jan. 2018.
      Clarkson, Mary. Developing IT Staff: A Practical Approach. Springer Science & Business Media, 2012.
      "CNBC and SurveyMonkey Release Latest Small Business Survey Results." Momentive, 2019. Press Release. Accessed 6 Aug. 2020.
      Cselényi, Noémi. "Why Is It Important for Small Business Owners to Focus on Talent Management?" Jumpstart:HR | HR Outsourcing and Consulting for Small Businesses and Startups, 25 Mar. 2013.
      dsparks. "Top 10 IT Concerns for Small Businesses." Stratosphere Networks IT Support Blog - Chicago IT Support Technical Support, 16 May 2017.
      Duff, Jimi. "Why Small to Mid-Sized Businesses Need a System for Talent Management | Talent Management Blog | Saba Software." Saba, 17 Dec. 2018.
      Employment and Social Development Canada. "Age-Friendly Workplaces: Promoting Older Worker Participation." Government of Canada, 3 Oct. 2016.
      Exploring Workforce Planning. Accenture, 23 May 2017.
      "Five Major IT Challenges Facing Small and Medium-Sized Businesses." Advanced Network Systems. Accessed 25 June 2020.
      Harris, Evan. "IT Problems That Small Businesses Face." InhouseIT, 17 Aug. 2016.
      Heathfield, Susan. "What Every Manager Needs to Know About Succession Planning." Liveabout, 8 June 2020.
      ---. "Why Talent Management Is an Important Business Strategy." Liveabout, 29 Dec. 2019.
      Herbert, Chris. "The Top 5 Challenges Facing IT Departments in Mid-Sized Companies." ExpertIP, 25 June 2012.
      How Smaller Organizations Can Use Talent Management to Accelerate Growth. Avilar. Accessed 25 June 2020.
      Krishnan, TN, and Hugh Scullion. "Talent Management and Dynamic View of Talent in Small and Medium Enterprises." Human Resource Management Review, vol. 27, no. 3, Sept. 2017, pp. 431–41.
      Mann Jackson, Nancy. "Strategic Workforce Planning for Midsized Businesses." ADP, 6 Feb. 2017.
      McCandless, Karen. "A Beginner's Guide to Strategic Talent Management (2020)." The Blueprint, 26 Feb. 2020.
      McFeely, Shane, and Ben Wigert. "This Fixable Problem Costs U.S. Businesses $1 Trillion." Gallup.com, 13 Mar. 2019.
      Mihelič, Katarina Katja. Global Talent Management Best Practices for SMEs. Jan. 2020.
      Mohsin, Maryam. 10 Small Business Statistics You Need to Know in 2020 [May 2020]. 4 May 2020.
      Ramadan, Wael H., and B. Eng. The Influence of Talent Management on Sustainable Competitive Advantage of Small and Medium Sized Establishments. 2012, p. 15.
      Ready, Douglas A., et al. "Building a Game-Changing Talent Strategy." Harvard Business Review, no. January–February 2014, Jan. 2014.
      Reh, John. "Cross-Training Employees Strengthens Engagement and Performance." Liveabout, May 2019.
      Rennie, Michael, et al. McKinsey on Organization: Agility and Organization Design. McKinsey, May 2016.
      Roddy, Seamus. "The State of Small Business Employee Benefits in 2019." Clutch, 18 Apr. 2019.
      SHRM. "Developing Employee Career Paths and Ladders." SHRM, 28 Feb. 2020.
      Strandberg, Coro. Sustainability Talent Management: The New Business Imperative. Strandberg Consulting, Apr. 2015.
      Talent Management for Small & Medium-Size Businesses. Success Factors. Accessed 25 June 2020.
      "Top 10 IT Challenges Facing Small Business in 2019." Your IT Department, 8 Jan. 2019.
      "Why You Need Workforce Planning." Workforce.com, 24 Oct. 2022.

      Select Your Data Platform

      • Buy Link or Shortcode: {j2store}346|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $62,999 Average $ Saved
      • member rating average days saved: 20 Average Days Saved
      • Parent Category Name: Data Management
      • Parent Category Link: /data-management

      Every organization needs a data management (DM) platform that enables the DM capabilities required. This could be a daunting task because:

      • Every organization has a unique set of requirements for the DM platform.
      • Software products are difficult to compare because every vendor provides a unique set of features.
      • Software vendors are interested in getting as large a footprint as possible.
      • Some products from different categories offer the same functionalities.
      • Some products are just not compatible.

      Our Advice

      Critical Insight

      • Technology requirements start with the business goals.
      • Data platform selection should be based on common best practices and, at the same time, be optimized for the organization’s specific needs and goals and support an evolutionary platform development.
      • What is best for one organization may be totally unacceptable for another – all for very valid reasons.

      Impact and Result

      Understand your current environment and use proven reference architecture patterns to expedite building the data management platform that matches your needs.

      • Use a holistic approach.
      • Understand your goals and priorities.
      • Picture your target-state architecture.
      • Identify your current technology coverage.
      • Select the software covering the gaps in technology enablement based on feature/functional enablement descriptions as well as vendor and deployment preferences.

      Select Your Data Platform Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out what challenges are typically in the way of designing a data platform, review Info-Tech’s methodology, and understand how we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Select your data platform

      Assess your current environment, find the right reference architecture pattern, and match identified capabilities with software features.

      • Data Platform Design Assessment
      • Reference Architecture Pattern

      Infographic

      Availability and Capacity Management

      • Buy Link or Shortcode: {j2store}10|cart{/j2store}
      • Related Products: {j2store}10|crosssells{/j2store}
      • Up-Sell: {j2store}10|upsells{/j2store}
      • member rating overall impact: 8.0/10.0
      • member rating average dollars saved: $2,950
      • member rating average days saved: 10
      • Parent Category Name: Resilient IT Operations
      • Parent Category Link: /resilience/resilient-operations-and-it
      Develop your availability and capacity management plant and align it with exactly what the business expects.

      Develop a Plan to Pilot Enterprise Service Management

      • Buy Link or Shortcode: {j2store}279|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Service Management
      • Parent Category Link: /service-management
      • Many business groups in the organization are siloed and have disjointed services that lead to a less than ideal customer experience.
      • Service management is too often process-driven and is implemented without a holistic view of customer value.
      • Businesses get caught up in the legacy of their old systems and find it difficult to move with the evolving market.

      Our Advice

      Critical Insight

      • Customer experience is the new battleground. Parity between products is creating the need to differentiate via customer experience.
      • Don’t forget your employees! Enterprise service management (ESM) is also about delivering exceptional experiences to your employees so they can deliver exceptional services to your customers.
      • ESM is not driven by tools and processes. Rather, ESM is about pushing exceptional services to customers by pulling from organizational capabilities.

      Impact and Result

      • Understand ESM concepts and how they can improve customer service.
      • Use Info-Tech’s advice and tools to perform an assessment of your organization’s state for ESM, identify the gaps, and create an action plan to move towards an ESM pilot.
      • Increase business and customer satisfaction by delivering services more efficiently.

      Develop a Plan to Pilot Enterprise Service Management Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should move towards ESM, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Understand ESM and get buy-in

      Understand the concepts of ESM, determine the scope of the ESM program, and get buy-in.

      • Develop a Plan to Pilot Enterprise Service Management – Phase 1: Understand ESM and Get Buy-in
      • Enterprise Service Management Executive Buy-in Presentation Template
      • Enterprise Service Management General Communications Presentation Template

      2. Assess the current state for ESM

      Determine the current state for ESM and identify the gaps.

      • Develop a Plan to Pilot Enterprise Service Management – Phase 2: Assess the Current State for ESM
      • Enterprise Service Management Assessment Tool
      • Enterprise Service Management Assessment Tool Action Plan Guide
      • Enterprise Service Management Action Plan Tool

      3. Identify ESM pilot and finalize action plan

      Create customer journey maps, identify an ESM pilot, and finalize the action plan for the pilot.

      • Develop a Plan to Pilot Enterprise Service Management – Phase 3: Identify ESM Pilot and Finalize Action Plan
      • Enterprise Service Management Customer Journey Map Template
      [infographic]

      Workshop: Develop a Plan to Pilot Enterprise Service Management

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Understand ESM and Get Buy-In

      The Purpose

      Understand what ESM is and how it can improve customer service.

      Determine the scope of your ESM initiative and identify who the stakeholders are for this program.

      Key Benefits Achieved

      Understanding of ESM concepts.

      Understanding of the scope and stakeholders for your ESM initiative.

      Plan for getting buy-in for the ESM program.

      Activities

      1.1 Understand the concepts and benefits of ESM.

      1.2 Determine the scope of your ESM program.

      1.3 Identify your stakeholders.

      1.4 Develop an executive buy-in presentation.

      1.5 Develop a general communications presentation.

      Outputs

      Executive buy-in presentation

      General communications presentation

      2 Assess the Current State for ESM

      The Purpose

      Assess your current state with respect to culture, governance, skills, and tools.

      Identify your strengths and weaknesses from the ESM assessment scores.

      Key Benefits Achieved

      Understanding of your organization’s current enablers and constraints for ESM.

      Determination and analysis of data needed to identify strengths or weaknesses in culture, governance, skills, and tools.

      Activities

      2.1 Understand your organization’s mission and vision.

      2.2 Assess your organization’s culture, governance, skills, and tools.

      2.3 Identify the gaps and determine the necessary foundational action items.

      Outputs

      ESM assessment score

      Foundational action items

      3 Define Services and Create Custom Journey Maps

      The Purpose

      Define and choose the top services at the organization.

      Create customer journey maps for the chosen services.

      Key Benefits Achieved

      List of prioritized services.

      Customer journey maps for the prioritized services.

      Activities

      3.1 Make a list of your services.

      3.2 Prioritize your services.

      3.3 Build customer journey maps.

      Outputs

      List of services

      Customer journey maps

      Responsibly Resume IT Operations in the Office

      • Buy Link or Shortcode: {j2store}423|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: DR and Business Continuity
      • Parent Category Link: /business-continuity

      Having shifted operations almost overnight to a remote work environment, and with the crisis management phase of the COVID-19 pandemic winding down, IT leaders and organizations are faced with the following issues:

      • A reduced degree of control with respect to the organization’s assets.
      • Increased presence of unapproved workaround methods, including applications and devices not secured by the organization.
      • Pressure to resume operations at pre-pandemic cadence while still operating in recovery mode.
      • An anticipated game plan for restarting the organization’s project activities.

      Our Advice

      Critical Insight

      An organization’s shift back toward the pre-pandemic state cannot be carried out in isolation. Things have changed. Budgets, resource availability, priorities, etc., will not be the same as they were in early March. Organizations must ensure that all departments work collaboratively to support office repatriation. IT must quickly identify the must-dos to allow safe return to the office, while prioritizing tasks relating to the repopulation of employees, technical assets, and operational workloads via an informed and streamlined roadmap.

      As employees return to the office, PMO and portfolio leaders must sift through unclear requirements and come up with a game plan to resume project activities mid-pandemic. You need to develop an approach, and fast.

      Impact and Result

      Responsibly resume IT operations in the office:

      • Evaluate risk tolerance
      • Prepare to repatriate people to the office
      • Prepare to repatriate assets to the office
      • Prepare to repatriate workloads to the office
      • Prioritize your tasks and build your roadmap

      Quickly restart the engine of your PPM:

      • Restarting the engine of the project portfolio won’t be as simple as turning a key and hitting the gas. The right path forward will differ for every project portfolio practice.
      • Therefore, in this publication we put forth a multi-pass approach that PMO and portfolio managers can follow depending on their unique situations and needs.
      • Each approach is accompanied by a checklist and recommendations for next steps to get you on right path fast.

      Responsibly Resume IT Operations in the Office Research & Tools

      Start here – read the Executive Brief

      As the post-pandemic landscape begins to take shape, ensure that IT can effectively prepare and support your employees as they move back to the office.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Evaluate your new risk tolerance

      Identify the new risk landscape and risk tolerance for your organization post-pandemic. Determine how this may impact the second wave of pandemic transition tasks.

      • Responsibly Resume IT Operations in the Office – Phase 1: Evaluate Your New Risk Tolerance
      • Resume Operations Information Security Pressure Analysis Tool

      2. Repatriate people to the office

      Prepare to return your employees to the office. Ensure that IT takes into account the health and safety of employees, while creating an efficient and sustainable working environment

      • Responsibly Resume IT Operations in the Office – Phase 2: Repatriate People to the Office
      • Mid-Pandemic IT Prioritization Tool

      3. Repatriate assets to the office

      Prepare the organization's assets for return to the office. Ensure that IT takes into account the off-license purchases and new additions to the hardware family that took place during the pandemic response and facilitates a secure reintegration to the workplace.

      • Responsibly Resume IT Operations in the Office – Phase 3: Repatriate Assets to the Office

      4. Repatriate workloads to the office

      Prepare and position IT to support workloads in order to streamline office reintegration. This may include leveraging pre-existing solutions in different ways and providing additional workstreams to support employee processes.

      • Responsibly Resume IT Operations in the Office – Phase 4: Repatriate Workloads to the Office

      5. Prioritize your tasks and build the roadmap

      Once you've identified IT's supporting tasks, it's time to prioritize. This phase walks through the activity of prioritizing based on cost/effort, alignment to business, and security risk reduction weightings. The result is an operational action plan for resuming office life.

      • Responsibly Resume IT Operations in the Office – Phase 5: Prioritize Your Tasks and Build the Roadmap

      6. Restart the engine of your project portfolio

      Restarting the engine of the project portfolio mid-pandemic won’t be as simple as turning a key and hitting the gas. Use this concise research to find the right path forward for your organization.

      • Restart the Engine of Your Project Portfolio
      [infographic]

      Recruit and Retain People of Color in IT

      • Buy Link or Shortcode: {j2store}546|cart{/j2store}
      • member rating overall impact: 9.7/10 Overall Impact
      • member rating average dollars saved: $19,184 Average $ Saved
      • member rating average days saved: 21 Average Days Saved
      • Parent Category Name: Engage
      • Parent Category Link: /engage
      • Organizations have been trying to promote equality for many years. Diversity and inclusion strategies and a myriad of programs have been implemented in companies across the world. Despite the attempts, many organizations still struggle to ensure that their workforce is representative of the populations they support or want to support.
      • IT brings another twist. Many IT companies and departments are based on the culture of white males, and underrepresented ethnic communities find it more of a challenge to fit in.
      • This sometimes means that talented minorities are less incentivized to join or stay in technology.

      Our Advice

      Critical Insight

      • Diversity and inclusion cannot be a one-time campaign or a one-off initiative.
      • For real change to happen, every leader needs to internalize the value of creating and retaining diverse teams.

      Impact and Result

      • To stay competitive, IT leaders need to be more involved and commit to a plan to recruit and retain people of color in their departments and organizations. A diverse team is an answer to innovation that can differentiate your company.
      • Treat recruiting and retaining a diverse team as a business challenge that requires full engagement. Info-Tech offers a targeted solution that will help IT leaders build a plan to attract, recruit, engage, and retain people of color.

      Recruit and Retain People of Color in IT Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should recruit and retain people of color in your IT department or organization, review Info-Tech’s methodology, and understand the ways we can support you in this endeavor.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Recruit people of color in IT

      Diverse teams are necessary to foster creativity and guide business strategies. Overcome limitations by recruiting people of color and creating a diverse workforce.

      • Recruit and Retain People of Color in IT – Phase 1: Recruit People of Color in IT
      • Support Plan
      • IT Behavioral Interview Question Library

      2. Retain people of color in IT

      Underrepresented employees benefit from an expansive culture. Create an inclusive environment and retain people of color and promote value within your organization.

      • Recruit and Retain People of Color in IT – Phase 2: Retain People of Color in IT

      Infographic

      Workshop: Recruit and Retain People of Color in IT

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Setting the Stage

      The Purpose

      Introduce challenges and concerns around recruiting and retaining people of color.

      Key Benefits Achieved

      Gain a sense of direction.

      Activities

      1.1 Introduction to diversity conversations.

      1.2 Assess areas to focus on and determine what is right, wrong, missing, and confusing.

      1.3 Obtain feedback from your team about the benefits of working at your organization.

      1.4 Establish your employee value proposition (EVP).

      1.5 Discuss and establish your recruitment goals.

      Outputs

      Current State Analysis

      Right, Wrong, Missing, Confusing Quadrant

      Draft EVP

      Recruitment Goals

      2 Refine Your Recruitment Process

      The Purpose

      Identify areas in your current recruitment process that are preventing you from hiring people of color.

      Establish a plan to make improvements.

      Key Benefits Achieved

      Optimized recruitment process

      Activities

      2.1 Brainstorm and research community partners.

      2.2 Review current job descriptions and equity statement.

      2.3 Update job description template and equity statement.

      2.4 Set team structure for interview and assessment.

      2.5 Identify decision-making structure.

      Outputs

      List of community partners

      Updated job description template

      Updated equity statement

      Interview and assessment structure

      Behavioral Question Library

      3 Culture and Management

      The Purpose

      Create a plan for an inclusive culture where your managers are supported.

      Key Benefits Achieved

      Awareness of how to better support employees of color.

      Activities

      3.1 Discuss engagement and belonging.

      3.2 Augment your onboarding materials.

      3.3 Create an inclusive culture plan.

      3.4 Determine how to support your management team.

      Outputs

      List of onboarding content

      Inclusive culture plan

      Management support plan

      4 Close the Loop

      The Purpose

      Establish mechanisms to gain feedback from your employees and act on them.

      Key Benefits Achieved

      Finalize the plan to create your diverse and inclusive workforce.

      Activities

      4.1 Ask and listen: determine what to ask your employees.

      4.2 Create your roadmap.

      4.3 Wrap-up and next steps.

      Outputs

      List of survey questions

      Roadmap

      Completed support plan

      Enter Into Mobile Development Without Confusion and Frustration

      • Buy Link or Shortcode: {j2store}282|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Mobile Development
      • Parent Category Link: /mobile-development
      • IT managers don’t know where to start when initiating a mobile program.
      • IT has tried mobile development in the past but didn't achieve success.
      • IT must initiate a mobile program quickly based on business priorities and needs a roadmap based on best practices.

      Our Advice

      Critical Insight

      • Form factors and mobile devices won't drive success – business alignment and user experience will. Don't get caught up with the latest features in mobile devices.
      • Software emulation testing is not true testing. Get on the device and run your tests.
      • Cross form-factor testing cannot be optimized to run in parallel. Therefore, anticipate longer testing cycles for cross form-factor testing.

      Impact and Result

      • Prepare your development, testing, and deployment teams for mobile development.
      • Get a realistic assessment of ROI for the launch of a mobile program.

      Enter Into Mobile Development Without Confusion and Frustration Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Make the Case for a Mobile Program

      Understand the current mobile ecosystem. Use this toolkit to help you initiate a mobile development program.

      • Storyboard: Enter Into Mobile Development Without Confusion and Frustration

      2. Assess Your Dev Process for Readiness

      Review and evaluate your current application development process.

      3. Prepare to Execute Your Mobile Program

      Prioritize your mobile program based on your organization’s prioritization profile.

      • Mobile Program Tool

      4. Communicate with Stakeholders

      Summarize the execution of the mobile program.

      • Project Status Communication Worksheet
      [infographic]

      Workshop: Enter Into Mobile Development Without Confusion and Frustration

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Build your Future Mobile Development State

      The Purpose

      Understand the alignment of stakeholder objectives and priorities to mobile dev IT drivers.

      Assess readiness of your organization for mobile dev.

      Understand how to build your ideal mobile dev process.

      Key Benefits Achieved

      Identify and address the gaps in your existing app dev process.

      Build your future mobile dev state.

      Activities

      1.1 Getting started

      1.2 Assess your current state

      1.3 Establish your future state

      Outputs

      List of key stakeholders

      Stakeholder and IT driver mapping and assessment of current app dev process

      List of practices to accommodate mobile dev

      2 Prepare and Execute your Mobile Program

      The Purpose

      Assess the impact of mobile dev on your existing app dev process.

      Prioritize your mobile program.

      Understand the dev practice metrics to gauge success.

      Key Benefits Achieved

      Properly prepare for the execution of your mobile program.

      Calculate the ROI of your mobile program.

      Prioritize your mobile program with dependencies in mind.

      Build a communication plan with stakeholders.

      Activities

      2.1 Conduct an impact analysis

      2.2 Prepare to execute

      2.3 Communicate with stakeholders

      Outputs

      Impact analysis of your mobile program and expected ROI

      Mobile program order of execution and project dependencies mapping

      List of dev practice metrics

      Manage Your Technical Debt

      • Buy Link or Shortcode: {j2store}108|cart{/j2store}
      • member rating overall impact: 8.5/10 Overall Impact
      • member rating average dollars saved: $60,833 Average $ Saved
      • member rating average days saved: 24 Average Days Saved
      • Parent Category Name: Strategy and Organizational Design
      • Parent Category Link: /strategy-and-organizational-design
      • All organizations, of all sizes, have some amount of technical debt, but very few systematically track, manage, and communicate it.
      • Deferred project work is pushed over to operations, sometimes with little visibility or hand-off, where it gets deprioritized and lost.
      • IT doesn’t have the resources or authority to make needed changes to address the impact of tech debt and can’t make the case for improvement without good data on the problem.
      • Efforts to track technical debt get stuck in the weeds, don’t connect technical issues to business impact, and run out of steam.

      Our Advice

      Critical Insight

      • Technical debt is a type of technical risk, which in turn is business risk. The business, not IT, must make the decision to accept or mitigate risk – but IT must help the business make an informed decision.
      • There are two ways to keep your technical debt at a manageable level – effectively, to mitigate risk: either stop introducing new debt or start paying back what you already have.

      Impact and Result

      • Define and identify your technical debt. Focus on tech debt you think you can actually fix.
      • Conduct a streamlined and targeted business impact analysis to prioritize tech debt based on its ongoing business impact.
      • Identify options to better manage technical debt and present your findings to business decision makers.

      Manage Your Technical Debt Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to understand the business case to manage technical debt, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Identify your technical debt

      Define, identify, and organize your technical debt in preparation for the technical debt impact analysis.

      • Technical Debt Business Impact Analysis Tool

      2. Measure your technical debt

      Conduct a technical debt business impact analysis.

      • Roadmap Tool

      3. Manage your technical debt

      Identify options to resolve technical debt and summarize the challenge and potential solutions for business decision makers.

      • Technical Debt Executive Summary Presentation
      [infographic]

      Workshop: Manage Your Technical Debt

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Define and Identify Technical Debt

      The Purpose

      Create a working definition of technical debt and identify the technical debt in your environment.

      Key Benefits Achieved

      List your technical debt.

      Activities

      1.1 Develop a working definition for technical debt.

      1.2 Discuss your organization’s technical debt risk.

      1.3 Identify 5-10 high-impact technical debts to structure the impact analysis.

      Outputs

      Goals, opportunities, and constraints related to tech debt management

      A list of technical debt

      2 Measure Technical Debt

      The Purpose

      Conduct a more-objective assessment of the business impact of technical debt.

      Key Benefits Achieved

      Identify the most-critical technical debt in your environment, in terms of business risk.

      Activities

      2.1 Review and modify business impact scoring scales.

      2.2 Identify reasonable scenarios to structure the impact analysis.

      2.3 Apply the scoring scale to identify the business impact of each technical debt.

      Outputs

      Business impact scoring scales

      Scenarios to support the impact analysis

      Technical debt impact analysis

      3 Build a Roadmap to Manage Technical Debt

      The Purpose

      Leverage the technical debt impact analysis to identify, compare, and quantify projects that fix technical debt and projects that prevent it.

      Key Benefits Achieved

      Create your plan to manage technical debt.

      Activities

      3.1 Brainstorm projects and action items to manage and pay back critical technical debt. Prioritize projects and action items to build a roadmap.

      3.2 Identify three possible courses of action to pay back each critical technical debt.

      3.3 Identify immediate next steps to manage remaining tech debt and limit the introduction of new tech debt.

      Outputs

      Technical debt management roadmap

      Technical debt executive summary

      Immediate next steps to manage technical debt

      Manage Exponential Value Relationships

      • Buy Link or Shortcode: {j2store}210|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Vendor Management
      • Parent Category Link: /vendor-management

      Implementing exponential IT will require businesses to work with external vendors to facilitate the rapid adoption of cutting-edge technologies such as generative artificial intelligence. IT leaders must:

      These challenges require new skills which build trust and collaboration among vendors.

      Our Advice

      Critical Insight

      Outcome-based relationships require a higher degree of trust than traditional vendor relationships. Build trust by sharing risks and rewards.

      Impact and Result

      • Assess your readiness to take on the new types of vendor relationships that will help you succeed.
      • Identify where you need to build your capabilities in order to successfully manage relationships.
      • Successfully manage outcomes, financials, risk, and relationships in complex vendor relationships.

      Manage Exponential Value Relationships Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Manage Exponential Value Relationships Storyboard – Learn about the new era of exponential vendor relationships and the capabilities needed to succeed.

      This research walks you through how to assess your capabilities to undertake a new model of vendor relationships and drive exponential IT.

      • Manage Exponential Value Relationships Storyboard

      2. Exponential Relationships Readiness Assessment – Assess your readiness to engage in exponential vendor partnerships.

      This tool will facilitate your readiness assessment.

      • Exponential Relationships Readiness Assessment
      [infographic]

      Further reading

      Manage Exponential Value Relationships

      Are you ready to manage outcome-based agreements?

      Analyst Perspective

      Outcome-based agreements require a higher degree of mutual trust.

      Kim Osborne Rodriguez

      Exponential IT brings with it an exciting new world of cutting-edge technology and increasingly accelerated growth of business and IT. But adopting and driving change through this paradigm requires new capabilities to grow impactful and meaningful partnerships with external vendors who can help implement technologies like artificial intelligence and virtual reality.

      Building outcome-based partnerships involves working very closely with vendors who, in many cases, will have just as much to lose as the organizations implementing these new technologies. This requires a greater degree of trust between parties than a standard vendor relationship. It also drastically increases the risks to both organizations; as each loses some control over data and outcomes, they must trust that the other organization will follow through on commitments and obligations.

      Outcome-based partnerships build upon traditional vendor management practices and create the potential for organizations to embrace emerging technology in new ways.

      Kim Osborne Rodriguez
      Research Director, CIO Advisory
      Info-Tech Research Group

      Executive Summary

      Exponential IT drives change

      Vendor relationships must evolve

      To deliver exponential value

      Implementing exponential IT will require businesses to work with external vendors to facilitate the rapid adoption of cutting-edge technologies such as generative artificial intelligence. IT leaders must:

      • Build strategic relationships with external entities to support the autonomization of the enterprise.
      • Procure, operate, and manage contracts and performance in outcome-based relationships.
      • Build relationships with new vendors.

      These challenges require new skills which build trust and collaboration with vendors.

      Traditional vendor management approaches are still important for organizations to develop and maintain. But exponential relationships bring new challenges:

      • A shift from managing technology service agreements to managing business capability agreements
      • Increased vendor access to intellectual property, confidential information, and customers

      IT leaders must adapt traditional vendor management capabilities to successfully lead this change.

      Outcome-based relationships should not be undertaken lightly as they can significantly impact the risk profile of the organization. Use this research to:

      • Assess your foundational vendor management capabilities as well as the transformative capabilities you need to manage outcome-based relationships.
      • Identify where you need to build your capabilities in order to successfully manage relationships.
      • Successfully manage outcomes, financials, risk, and relationships in complex vendor partnerships.

      Exponential value relationships will help drive exponential IT and autonomization of the enterprise.

      Info-Tech Insight

      Outcome-based partnerships require a higher degree of trust than traditional vendor relationships. Build trust by sharing risks and rewards.

      Vendor relationships can be worth billions of dollars

      Positive vendor relationships directly impact the bottom line, sometimes to the tune of billions of dollars annually.

      • Organizations typically spend 40% to 80% of their total budget on external suppliers.
      • Greater supplier trust translates directly to greater business profits, even in traditional vendor relationships.1
      • Based on over a decade of data from vehicle manufacturers, greater supplier relationships nearly doubled the unit profit margin on vehicles, contributing over $20 billion to Toyota’s annual profits based on typical sales volume.2
      • Having positive vendor relationships can be instrumental in times of crisis – when scarcity looms, vendors often choose to support their best customers.3,4 For example, Toyota protected itself from the losses many original equipment manufacturers (OEMs) faced in 2020 and showed improved profitability that year due to increased demand for vehicles which it was able to supply as a result of top-ranked vendor relationships.
      1 PR Newswire, 2022.
      2 Based on 10 years of data comparing Toyota and Nissan, every 1-point increase in the company’s Working Relations Index was correlated with a $15.77 net profit increase per unit. Impact on Toyota annual profits is based on 10.5 million units sold in 2021 and 2022.
      3 Interview with Renee Stanley, University of Texas at Arlington. Conducted 17 May 2023.
      4 Plante Moran, 2020.

      Supplier Trust Impacts OEM Profitability

      Sources: Macrotrends, Plante Moran 2022, Nissan 2022 and 2023, and Toyota 2022. Profit per car is based on total annual profit divided by total annual sales volume.

      Outcome-based relationships are a new paradigm

      In a new model where organizations are procuring autonomous capabilities, outcomes will govern vendor relationships.

      An outcome-based relationship requires a higher level of mutual trust than traditional vendor relationships. This requires shared reward and shared risk.

      Don’t forget about traditional vendor management relationships! Not all vendor relationships can (or should) be outcome-based.

      Managing Exponential Value Relationships.

      Case study

      INDUSTRY: Technology

      SOURCE: Press Release

      Microsoft and OpenAI partner on Azure, Teams, and Microsoft Office suite

      In January 2023, Microsoft announced a $10 billion investment in OpenAI, allowing OpenAI to continue scaling its flagship large language model, ChatGPT, and giving Microsoft first access to deploy OpenAI’s products in services like GitHub, Microsoft Office, and Microsoft Teams.

      Shared risk

      Issues with OpenAI’s platforms could have a debilitating effect on Microsoft’s own reputation – much like Google’s $100 billion stock loss following a blunder by its AI platform Bard – not to mention the financial loss if the platform does not live up to the hype.

      Shared reward

      This was a particularly important strategic move by Microsoft, as its main competitors develop their own AI models in a race to the top. This investment also gave OpenAI the resources to continue scaling and evolving its services much faster than it would be capable of on its own. If OpenAI’s products succeed, there is a significant upside for both companies.

      The image contains a graph that demonstrates time to reach 1 million users.

      Adapt your approach to vendor relationships

      Both traditional vendors and exponential relationships are important.

      Traditional

      procurement

      Vendor

      management

      Exponential vendor relationships

      • Ideal for procuring a product or service
      • Typically evaluates vendors based on their capabilities and track record of success
      • Focuses on metrics, KPIs, and contracts to deliver success to the organization purchasing the product or service
      • Vendors typically only have access to company data showing what is required to deliver their product or service
      • Ideal for managing vendors supplying products or services
      • Typically evaluates vendors based on the value and the criticality of a vendor to drive VM-resource allocation
      • External vendors do not generally participate in sharing of risks or rewards outside of payment for services or incentives/penalties
      • Vendors typically have limited access to company data
      • Ideal for procuring an autonomous capability
      • Typically evaluated based on the total possible value creation for both parties
      • External vendors share in substantial portions of the risks and rewards of the relationship
      • Vendors typically have significant access to company data, including proprietary methods, intellectual property, and customer lists

      Use this research to successfully
      manage outcome-based relationships.

      Use Info-Tech’s research to Jump Start Your Vendor Management Initiative.

      Common obstacles

      Exponential relationships require new approaches to vendor management as businesses autonomize:

      • Autonomization refers to the shift toward autonomous business capabilities which leverage technologies such as AI and quantum computing to operate independently of human interaction.
      • The speed and complexity of technology advancement requires that businesses move quickly and confidently to develop strong relationships and deliver value.
      • We are seeing businesses shift from procuring products and services to procuring autonomous business capabilities (sometimes called “as a service,” or aaS). This shift can drive exponential value but also increases complexity and risk.
      • Exponential IT requires a shift in emphasis toward more mature relationship and risk management strategies, compared to traditional vendor management.

      The shift from technology service agreements to business capability agreements needs a new approach

      Eighty-seven percent of organizations are currently experiencing talent shortages or expect to within a few years.

      Source: McKinsey, “Mind the [skills] gap”, 2021.

      Sixty-three percent of IT leaders plan to implement AI in their organizations by the end of 2023.

      Source: Info-Tech Research Group survey, 2022

      Insight summary

      Build trust

      Successfully managing exponential relationships requires increased trust and the ability to share both risks and rewards. Outcome-based vendors typically have greater access to intellectual property, customer data, and proprietary methods, which can pose a risk to the organization if this information is used to benefit competitors. Build mutual trust by sharing both risks and rewards.

      Manage risk

      Outcome-based relationships with external vendors can drastically affect an organization’s risk profile. Carefully consider third-party risk and shared risk, including ESG risk, as well as the business risk of losing control over capabilities and assets. Qualified risk specialists (such as legal, regulatory, contract, intellectual property law) should be consulted before entering outcome-based relationships.

      Drive outcomes

      Fostering strategic relationships can be instrumental in times of crisis, when being the customer of choice for key vendors can push your organization up the line from the vendor’s side – but be careful about relying on this too much. Vendor objectives may not align with yours, and in the end, everyone needs to protect themselves.

      Assess your readiness for exponential value relationships

      Key deliverable:

      Exponential Relationships Readiness Assessment

      Determine your readiness to build exponential value relationships.

      Measure the value of this blueprint

      Save thousands of dollars by leveraging this research to assess your readiness, before you lose millions from a relationship gone bad.

      Our research indicates that most organizations would take months to prepare this type of assessment without using our research. That’s over 80 person-hours spent researching and gathering data to support due diligence, for a total cost of thousands of dollars. Doesn’t your staff have better things to do?

      Start by answering a few brief questions, then return to this slide at the end to see how much your answers have changed.

      Establish Baseline Metrics

      Use Info-Tech’s research to Exponential Relationships Readiness Assessment.

      Estimated time commitment without Info-Tech’s research (person-hours)

      Establish a baseline

      Gauge the effectiveness of this research by asking yourself the following questions before and after completing your readiness assessment:

      Questions

      Before

      After

      To what extent are you satisfied with your current vendor management approach?

      How many of your current vendors would you describe as being of strategic importance?

      How much do you spend on vendors annually?

      How much value do you derive from your vendor relationships annually?

      Do you have a vendor management strategy?

      What outcomes are you looking to achieve through your vendor relationships?

      How well do you understand the core capabilities needed to drive successful vendor management?

      How well do you understand your current readiness to engage in outcome-based vendor relationships?

      Do you feel comfortable managing the risks when working with organizations to implement artificial intelligence and other autonomous capabilities?

      How to use this research

      Five tips to get the most out of your readiness assessment.

      1. Each category consists of five competencies, with a maximum of five points each. The maximum score on this assessment is 100 points.
      2. Effectiveness levels range from basic (level 1) to advanced (level 5). Level 1 is generally considered the baseline for most effectively operating organizations. If your organization is struggling with level 1 competencies, it is recommended to improve maturity in those areas before pursuing exponential relationships.
      3. This assessment is qualitative; complete the assessment to the best of your ability, based on the scoring rubric provided. If you fall between levels, use the lower one in your assessment.
      4. The scoring rubric may not perfectly fit the processes and practices within every organization. Consider the spirit of the description and score accordingly.
      5. Other industry- and region-specific competencies may be required to succeed at exponential relationships. The competencies in this assessment are a starting point, and internal validation and assessments should be conducted to uncover additional competencies and skills.

      Financial management

      Manage your budget and spending to stay on track throughout your relationship.

      “Most organizations underestimate the amount of time, money, and skill required to build and maintain a successful relationship with another organization. The investment in exponential relationships is exponential in itself – as are the returns.”

      – Jennifer Perrier, Principal Research Director,
      Info-Tech Research Group

      This step involves the following participants:

      • Executive leadership team, including CIO
      • CFO
      • Vendor management leader
      • Other internal stakeholders of vendor relationships

      Activities:

      • Assess your ability to manage scope and budget in exponential IT relationships.

      Successfully manage complex finances

      Stay on track and keep your relationship running smoothly.

      Why is this important?

      • Finance is at the core of most business – it drives decision making, acts as a constraint for innovation and optimization, and plays a key role in assessing options (such as return on investment or payback period).
      • Effectively managing finances is a critical success factor in developing strong relationships. Each organization must be able to manage their own budget and spending in order to balance the risk and reward in the relationship. Often, these risks and rewards will come in the form of profit and loss or revenue and spend.

      Build it into your practice:

      1. Ensure your financial decision-making practices are aligned with the organizational and relationship strategy. Do metrics and criteria reflect the organization’s goals?
      2. Develop strong accounting and financial analysis practices – this includes the ability to conduct financial due diligence on potential vendors.
      3. Develop consistent methodology to track and report on the desired outcomes on a regular basis.

      Build your ability to manage finances

      The five competencies needed to manage finances in exponential value relationships are:

      Budget procedures

      Financial alignment

      Adaptability

      Financial analysis

      Reporting & compliance

      Clearly articulate and communicate budgets, with proactive analysis and reporting.

      There is a strong, direct alignment between financial outcomes and organizational strategy and goals.

      Financial structures can manage many different types of relationships and structures without major overhaul.

      Proactive financial analysis is conducted regularly, with actionable insights.

      This exceeds legal requirements and includes proactive and actionable reporting.

      Relationship management

      Drive exponential value by becoming a customer of choice.

      “The more complex the business environment becomes — for instance, as new technologies emerge or as innovation cycles get faster — the more such relationships make sense. And the better companies get at managing individual relationships, the more likely it is that they will become “partners of choice” and be able to build entire portfolios of practical and value-creating partnerships.”

      (“Improving the management of complex business partnerships.” McKinsey, 2019)

      This step involves the following participants:

      • Executive leadership team, including CIO
      • Vendor management leader
      • Other internal stakeholders of vendor relationships

      Activities:

      • Assess your ability to manage relationships in exponential IT relationships.

      Take your relationships to the next level

      Maintaining positive relationships is key to building trust.

      Why is this important?

      • All relationships will experience challenges, and the ability to resolve these issues will rely heavily on the relationship management skills and soft skills of the leadership within each organization.
      • Based on a 20-year study of vendor relationships in the automotive sector, business-to-business trust is a function of reasonable demands, follow-through, and information sharing.
      (Source: Plante Moran, 2020)

      Build it into your practice:

      1. Develop the soft skills necessary to promote psychological safety, growth mindset, and strong and open communication channels.
      2. Be smart about sharing information – you don’t need to share everything, but being open about relevant information will enhance trust.
      3. Both parties need to work hard to develop trust necessary to build a true relationship. This will require increased access to decision-makers, clearly defined guardrails, and the ability for unsatisfied parties to leave.

      Build your ability to manage relationships

      The five competencies needed to manage relationships in exponential partnerships are:

      Strategic alignment

      Follow-through

      Information sharing

      Shared risk & rewards

      Communication

      Work with vendors to create roadmaps and strategies to drive mutual success.

      Ensure demands are reasonable and consistently follow through on commitments.

      Proactively and freely share relevant information between parties.

      Equitably share responsibility for outcomes and benefits from success.

      Ensure clear, proactive, and frequent communication occurs between parties.

      Performance management

      Outcomes management focuses on results, not methods.

      According to Jennifer Robinson, senior editor at Gallup, “This approach focuses people and teams on a concrete result, not the process required to achieve it. Leaders define outcomes and, along with managers, set parameters and guidelines. Employees, then, have a high degree of autonomy to use their own unique talents to reach goals their own way.” (Forbes, 2023)

      In the context of exponential relationships, vendors can be given a high degree of autonomy provided they meet their objectives.

      This step involves the following participants:

      • Executive leadership team, including CIO
      • Vendor management leader
      • Other internal stakeholders of vendor relationships

      Activities:

      • Assess your ability to manage outcomes in exponential IT relationships.

      Manage outcomes to drive mutual success

      Build trust by achieving shared objectives.

      Why is this important?

      • Relationships are based on shared risk and shared reward for all parties. In order to effectively communicate the shared rewards, you must first understand and communicate your objectives for the relationship, then measure outcomes to ensure all parties are benefiting.
      • Effectively managing outcomes reduces the risk that one party will choose to leave based on a perception of benefits not being achieved. Parties may still leave the agreement, but decisions should be based on shared facts and issues should be communicated and addressed early.

      Build it into your practice:

      1. Clearly articulate what you hope to achieve by entering an outcome-based relationship. Each party should outline and agree to the goals, objectives, and desired outcomes from the relationship.
      2. Document how rewards will be shared among parties. What type of rewards are anticipated? Who will benefit and how?
      3. Develop consistent methodology to track and report on the desired outcomes on a regular basis. This might consist of a vendor scorecard or a monthly meeting.

      Build your ability to manage outcomes

      The five competencies needed to manage outcomes in exponential value relationships are:

      Goal setting

      Negotiation

      Performance tracking

      Issue
      resolution

      Scope management

      Set specific, measurable and actionable goals, and communicate them with stakeholders.

      Clearly articulate and agree upon measurable outcomes between all parties.

      Proactively track progress toward goals/outcomes and discuss results with vendors regularly.

      Openly discuss potential issues and challenges on a regular basis. Find collaborative solutions to problems.

      Proactively manage scope and discuss with vendors on a regular basis.

      Risk management

      Exponential IT means exponential risk – and exponential rewards.

      One of the key differentiators between traditional vendor relationships and exponential relationships is the degree to which risk is shared between parties. This is not possible in all industries, which may limit companies’ ability to participate in this type of exponential relationship.

      This step involves the following participants:

      • Executive leadership team, including CIO
      • Vendor management leader
      • Risk management leader
      • Other internal stakeholders of vendor relationships

      Activities:

      • Assess your ability to manage risk in exponential IT relationships.

      Relationships come with a lot of hidden risks

      Successfully managing complex risks can be the difference between a spectacular success and company-ending failure.

      Why is this important?

      • Relationships inherently involve a loss of control. You are relying on another party to fulfill their part of the agreement, and you depend on the success of the outcome. Loss of control comes with significant risks.
      • Sharing in risk is what differentiates an outcome-based relationship from a traditional vendor relationship; vendors must have skin in the game.
      • Organizations must consider many different types of risk when considering a relationship with a vendor: fraud, security, human rights, labor relations, ESG, and operational risks. Remember that risk is not inherently bad; some risk is necessary.

      Build it into your practice:

      1. Build or hire the necessary risk expertise needed to properly assess and evaluate the risks of potential vendor relationships. This includes intellectual property, ESG, legal/regulatory, cybersecurity, data security, and more.
      2. Develop processes and procedures which clearly communicate and report on risk on a regular basis.

      Info-Tech Insight

      Some highly regulated industries (such as finance) are prevented from transferring certain types of risk. In these industries, it may be much more difficult to form vendor relationships.

      Don’t forget about third-party ESG risk

      Customers care about ESG. You should too.

      Protect yourself against third-party ESG risks by considering the environmental and social impacts of your vendors.

      Third-party ESG risks can include the following:

      • Environmental risk: Vendors with unsustainable practices such as carbon emissions or waste generation of natural resource depletion can negatively impact the organization’s environmental goals.
      • Social risk: Unsafe or illegal labor practices, human rights violations, and supply chain management issues can reflect negatively on organizations that choose to work with vendors who engage in such practices.
      • Governance risk: Vendors who engage in illegal or unethical behaviors, including bribery and corruption or data and privacy breaches can impact downstream customers.

      Working with vendors that have a poor record of ESG carries a very real reputational risk for organizations who do not undertake appropriate due diligence.

      A global survey of nearly 14,000 customers revealed that…

      Source: EY Future Consumer Index, 2021

      Seventy-seven percent of customers believe companies have a responsibility to manufacture sustainably.

      Sixty-eight percent of customers believe businesses should ensure their suppliers meet high social and environmental standards.

      Fifty-five percent of customers consider the environmental impact of production in their purchasing decisions.

      Build your ability to manage risk

      The five competencies needed to manage risk in exponential value relationships are:

      Third-party risk

      Value chain

      Data management

      Regulatory & compliance

      Monitoring & reporting

      Understand and assess third-party risk, including ESG risk, in potential relationships.

      Assess risk throughout the value chain for all parties and balance risk among parties.

      Proactively assess and manage potential data risks, including intellectual property and strategic data.

      Manage regulatory and compliance risks, including understanding risk transfer and ultimate risk holder.

      Proactive and open monitoring and reporting of risks, including regular communication among stakeholders.

      Contract management

      Contract management is a critical part of vendor management.

      Well-managed contracts include clearly defined pricing, performance-based outcomes, clear roles and responsibilities, and appropriate remedies for failure to meet requirements. In outcome-based relationships, contracts are generally used as a secondary method of enforcing performance, with relationship management being the primary method of addressing challenges and ensuring performance.

      This step involves the following participants:

      • Executive leadership team, including CIO
      • Vendor management leader
      • Risk management leader
      • Other internal stakeholders of vendor relationships

      Activities:

      • Assess your ability to manage risk in exponential IT relationships.

      Build your ability to manage contracts

      The five competencies needed to manage contracts in exponential value relationships are:

      Pricing

      Performance outcomes

      Roles and responsibilities

      Remedies

      Payment

      Pricing is clearly defined in contracts so that the total cost is understood including all fees, optional pricing, and set caps on increases.

      Contracts are performance-based whenever possible, including deliverables, milestones, service levels, due dates, and outcomes.

      Each party's roles and responsibilities are clearly defined in the contract documents with adequate detail.

      Contracts contain appropriate remedies for a vendor's failure to meet SLAs, due dates, and other obligations.

      Payment is made after performance targets are met, approved, or accepted.

      Activity 1: Assess your readiness for exponential relationships

      1-3 hours

      1. Gather key stakeholders from across your organization to participate in the readiness assessment exercise.
      2. As a group, review the core competencies from the previous four sections and determine where your organization’s effectiveness lies for each competency. Record your responses in the Exponential Relationships Readiness Assessment tool.

      Download the Exponential Relationships Readiness Assessment tool.

      Input Output
      • Core competencies
      • Knowledge of internal processes and capabilities
      • Readiness assessment
      Materials Participants
      • Exponential
        Relationships Readiness Assessment
        tool
      • Whiteboard/flip charts
      • Executive leadership team, including CIO
      • Vendor management leader
      • Other internal stakeholders of vendor relationships

      Understand your assessment

      This step involves the following participants:

      • Executive leadership team, including CIO
      • Vendor management leader
      • Other internal stakeholders of vendor relationships

      Activities:

      • Create an action plan.

      Understand the results of your assessment

      Consider the following recommendations based on your readiness assessment scores:

      • The chart to the right shows sample results. The bars indicate the recommended scores, and the line indicates the readiness score.
      • Three or more categories below the recommended scores, or any categories more than five points below the recommendation: outcome-based relationships are not recommended at this time.
      • Two or more categories below the recommended scores: Proceed with caution and limit outcome-based relationships to low-risk areas. Continue to mature capabilities.
      • One category below the recommended scores: Evaluate the risks and benefits before engaging in higher-risk vendor relationships. Continue to mature capabilities.
      • All categories at or above the recommended scores: You have many of the core capabilities needed to succeed at exponential relationships! Continue to evaluate and refine your vendor relationships strategy, and identify any additional competencies needed based on your industry or region.

      Acme Corp Exponential Relationships Readiness.

      Activity 2: Create an action plan

      1 hour

      1. Gather the stakeholders who participated in the readiness assessment exercise.
      2. As a group, review the results of the readiness assessment. Where there any surprise? Do the results reflect your understanding of the organization’s maturity?
      3. Determine which areas are likely to limit the organization’s relationship capability, based on lowest scoring areas and relative importance to the organization.
      4. Break out into groups and have each group identify three actions the organization could take to mature the lowest scoring areas.
      5. Bring the group back together and prioritize the actions. Note who will be accountable for each next step.
      InputOutput
      • Readiness assessment
      • Action plan to improve maturity of capabilities
      MaterialsParticipants
      • Exponential
        Relationship Readiness Assessment
        tool
      • Whiteboard/flip charts
      • Executive leadership team, including CIO
      • Vendor management leader
      • Other internal stakeholders of vendor relationships

      Related Info-Tech Research

      Jump Start Your Vendor Management Initiative
      Create and implement a vendor management framework to begin obtaining measurable results in 90 days.

      Elevate Your Vendor Management Initiative
      Transform your VMI from tactical to strategic to maximize its impact and value

      Evaluate Your Vendor Account Team to Optimize Vendor Relations
      Understand the value of knowing your account team’s influence in the organization, and your influence, to drive results.

      Related Info-Tech Research

      Build an IT Risk Management Program
      Mitigate the IT risks that could negatively impact your organization.

      Build an IT Budget
      Effective IT budgets are more than a spreadsheet. They tell a story.

      Adopt an Exponential IT Mindset
      Thrive through the next paradigm shift..

      Author

      Kim Osborne Rodriguez

      Kim Osborne Rodriguez
      Research Director, CIO Advisory
      Info-Tech Research Group

      Kim is a professional engineer and Registered Communications Distribution Designer (RCDD) with over a decade of experience in management and engineering consulting spanning healthcare, higher education, and commercial sectors. She has worked on some of the largest hospital construction projects in Canada, from early visioning and IT strategy through to design, specifications, and construction administration. She brings a practical and evidence-based approach, with a track record of supporting successful projects.

      Kim holds a Bachelor’s degree in Honours Mechatronics Engineering and an option in Management Sciences from the University of Waterloo.

      Research Contributors and Experts

      Jack Hakimian

      Jack Hakimian
      Senior Vice President
      Info-Tech Research Group

      Jack has more than 25 years of technology and management consulting experience. He has served multibillion-dollar organizations in multiple industries including financial services and telecommunications. Jack also served several large public sector institutions.

      He is a frequent speaker and panelist at technology and innovation conferences and events and holds a Master’s degree in Computer Engineering as well as an MBA from the ESCP-EAP European School of Management.

      Michael Tweedie

      Michael Tweedie
      Practice Lead, CIO Strategy
      Info-Tech Research Group

      Mike Tweedie brings over 25 years as a technology executive. He’s led several large transformation projects across core infrastructure, application and IT services as the head of Technology at ADP Canada. He was also the Head of Engineering and Service Offerings for a large French IT services firm, focused on cloud adoption and complex ERP deployment and management.

      Mike holds a Bachelor’s degree in Architecture from Ryerson University.

      Scott Bickley

      Scott Bickley
      Practice Lead, VCCO
      Info-Tech Research Group

      Scott Bickley is a Practice Lead & Principal Research Director at Info-Tech Research Group, focused on Vendor Management and Contract Review. He also has experience in the areas of IT Asset Management (ITAM), Software Asset Management (SAM), and technology procurement along with a deep background in operations, engineering, and quality systems management.

      Scott holds a B.S. in Justice Studies from Frostburg State University. He also holds active IAITAM certification designations of CSAM and CMAM and is a Certified Scrum Master (SCM).

      Donna Bales

      Donna Bales
      Principal Research Director
      Info-Tech Research Group

      Donna Bales is a Principal Research Director in the CIO Practice at Info-Tech Research Group, specializing in research and advisory services in IT risk, governance, and compliance. She brings over 25 years of experience in strategic consulting and product development and has a history of success in leading complex, multistakeholder industry initiatives.

      Donna has a bachelor’s degree in economics from the University of Western Ontario.

      Research Contributors and Experts

      Jennifer Perrier

      Jennifer Perrier
      Principal Research Director
      Info-Tech Research Group

      Jennifer has 25 years of experience in the information technology and human resources research space, joining Info-Tech in 1998 as the first research analyst with the company. Over the years, she has served as a research analyst and research manager, as well as in a range of roles leading the development and delivery of offerings across Info-Tech’s product and service portfolio, including workshops and the launch of industry roundtables and benchmarking. She was also Research Lead for McLean & Company, the HR advisory division of Info-Tech, during its start-up years.

      Jennifer’s research expertise spans the areas of IT strategic planning, governance, policy and process management, people management, leadership, organizational change management, performance benchmarking, and cross-industry IT comparative analysis. She has produced and overseen the development of hundreds of publications across the full breadth of both the IT and HR domains in multiple industries. In 2022, Jennifer joined Info-Tech’s IT Financial Management Practice with a focus on developing financial transparency to foster meaningful dialogue between IT and its stakeholders and drive better technology investment decisions.

      Phil Bode

      Phil Bode
      Principal Research Director
      Info-Tech Research Group

      Phil has 30+ years of experience with IT procurement-related topics: contract drafting and review, negotiations, RFXs, procurement processes, and vendor management. Phil has been a frequent speaker at conferences, a contributor to magazine articles in CIO Magazine and ComputerWorld, and quoted in many other magazines. He is a co-author of the book The Art of Creating a Quality RFP.

      Phil has a Bachelor of Science in Business Administration with a double major of Finance and Entrepreneurship and a Bachelor of Science in Business Administration with a major of Accounting, both from the University of Arizona.

      Research Contributors

      Erin Morgan

      Erin Morgan
      Assistant Vice President, IT Administration
      University of Texas at Arlington

      Renee Stanley

      Renee Stanley
      Assistant Director IT Procurement and Vendor Management
      University of Texas at Arlington

      Note: Additional contributors did not wish to be identified.

      Bibliography

      Andrea, Dave. “Plante Moran’s 2022 Working Relations Index® (WRI) Study shows supplier relations can improve amid industry crisis.” Plante Moran, 25 Aug 2022. Accessed 18 May 2023.
      Andrea, Dave. “Trust between suppliers and OEMs can better prepare you for the next crisis.” Plante Moran, 9 Sept 2020. Accessed 17 May 2023.
      Cleary, Shannon, and Carolan McLarney. “Organizational Benefits of an Effective Vendor Management Strategy.” IUP Journal of Supply Chain Management, Vol. 16, Issue 4, Dec 2019.
      De Backer, Ruth, and Eileen Kelly Rinaudo. “Improving the management of complex business partnerships.” McKinsey, 21 March 2019. Accessed 9 May 2023 .
      Dennean, Kevin et al. “Let's chat about ChatGPT.” UBS, 22 Feb 2023. Accessed 26 May 2023.
      F&I Tools. “Nissan Worldwide Vehicle Sales Report.” Factory Warranty List, 2022. Accessed 18 May 2023.
      Gomez, Robin. “Adopting ChatGPT and Generative AI in Retail Customer Service.” Radial, 235, April 2023. Accessed 10 May 2023.
      Harms, Thomas and Kristina Rogers. “How collaboration can drive value for you, your partners and the planet.” EY, 26 Oct 2021. Accessed 10 May 2023.
      Hedge & Co. “Toyota, Honda finish 1-2; General Motors finishes at 3rd in annual Supplier Working Relations Study.” PR Newswire, 23 May 2022. Accessed 17 May 2023.
      Henke Jr, John W., and T. Thomas. "Lost supplier trust, lost profits." Supply Chain Management Review, May 2014. Accessed 17 May 2023.
      Information Services Group, Inc. “Global Demand for IT and Business Services Continues Upward Surge in Q2, ISG Index™ Finds.” BusinessWire, 7 July 2021. Accessed 8 May 2023.
      Kasanoff, Bruce. “New Study Reveals Costs Of Bad Supplier Relationships.” Forbes, 6 Aug 2014. Accessed 17 May 2023.
      Macrotrends. “Nissan Motor Gross Profit 2010-2022.” Macrotrends. Accessed 18 May 2023.
      Macrotrends. “Toyota Gross Profit 2010-2022.” Macrotrends. Accessed 18 May 2023.
      McKinsey. “Mind the [skills] gap.” McKinsey, 27 Jan 2021. Accessed 18 May 2023.
      Morgan, Blake. “7 Examples of How Digital Transformation Impacted Business Performance.” Forbes, 21 Jul 2019. Accessed 10 May 2023.
      Nissan Motor Corporation. “Nissan reports strong financial results for fiscal year 2022.” Nissan Global Newsroom, 11 May 2023. Accessed 18 May 2023.

      Bibliography

      “OpenAI and Microsoft extend partnership.” Open AI, 23 Jan 2023. Accessed 26 May 2023.
      Pearson, Bryan. “The Apple Of Its Aisles: How Best Buy Lured One Of The Biggest Brands.“ Forbes, 23 Apr 2015. Accessed 23 May 2023.
      Perifanis, Nikolaos-Alexandros and Fotis Kitsios. “Investigating the Influence of Artificial Intelligence on Business Value in the Digital Era of Strategy: A Literature Review.” Information, 2 Feb 2023. Accessed 10 May 2023.
      Scott, Tim and Nathan Spitse. “Third-party risk is becoming a first priority challenge.” Deloitte. Accessed 18 May 2023.
      Stanley, Renee. Interview by Kim Osborne Rodriguez, 17 May 2023.
      Statista. “Toyota's retail vehicle sales from 2017 to 2021.” Statista, 27 Jul 2022. Accessed 18 May 2023.
      Tlili, Ahmed, et al. “What if the devil is my guardian angel: ChatGPT as a case study of using chatbots in education.” Smart Learning Environments, 22 Feb 2023. Accessed 9 May 2023.
      Vitasek, Kate. “Outcome-Based Management: What It Is, Why It Matters And How To Make It Happen.” Forbes, 12 Jan 2023. Accessed 9 May 2023.

      Build a Winning Business Process Automation Playbook

      • Buy Link or Shortcode: {j2store}407|cart{/j2store}
      • member rating overall impact: 8.3/10 Overall Impact
      • member rating average dollars saved: $8,065 Average $ Saved
      • member rating average days saved: 7 Average Days Saved
      • Parent Category Name: Business Analysis
      • Parent Category Link: /business-analysis
      • Organizations often have many business processes that rely on manual, routine, and repetitive data collection and processing work. These processes need to be automated to meet strategic priorities.
      • Your stakeholders may have decided to invest in process automation solutions. They may be ready to begin the planning and delivery of their first automated processes.
      • However, if your processes are costly, slow, defective, and do not generate the value end users want, automation will only magnify these inefficiencies.

      Our Advice

      Critical Insight

      • Put the user front and center. Aim to better understand the end user and their operational environment. Use cases, data models, and quality factors allow you to visualize the human-computer interactions from an end-user perspective and initiate a discussion on how technology and process improvements can be better positioned to help your end users.
      • Build for the future. Automation sets the technology foundations and process governance and management building blocks in your organization. Expect that more automation will be done using earlier investments.
      • Manage automations as part of your application portfolio. Automations are add-ons to your application portfolio. Unmanaged automations, like applications, will sprawl and reduce in value over time. A collaborative rationalization practice pinpoints where automation is required and identifies which business inefficiencies should be automated next.

      Impact and Result

      • Clarify the problem being solved. Gain a grounded understanding of your stakeholders’ drivers for business process automation. Discuss current business operations and systems to identify automation candidates.
      • Optimate your processes. Apply good practices to first optimize (opti-) and then automate (-mate) key business processes. Take a user-centric perspective to understand how users interact with technology to complete their tasks.
      • Deliver minimum viable automations (MVAs). Maximize the learning of automation solutions and business operational changes through small, strategic automation use cases. This sets the foundations for a broader automation practice.

      Build a Winning Business Process Automation Playbook Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Business Process Automation Deck – A step-by-step document that walks you through how to optimize and automate your business processes.

      This blueprint helps you develop a repeatable approach to understand your process challenges and to optimize and automate strategic business processes.

      • Build a Winning Business Process Automation Playbook – Phases 1-3

      2. Business Process Automation Playbook – A repeatable set of practices to assess, optimize, and automate your business processes.

      This playbook template gives your teams a step-by-step guide to build a repeatable and standardized framework to optimize and automate your processes.

      • Business Process Automation Playbook

      3. Process Interview Template – A structured approach to interviewing stakeholders about their business processes.

      Info-Tech's Process Interview Template provides a number of sections that you can populate to help facilitate and document your stakeholder interviews.

      • Process Interview Template

      4. Process Mapping Guide – A guide to mapping business processes using BPMN standards.

      Info-Tech's Process Mapping Guide provides a thorough framework for process mapping, including the purpose and benefits, the best practices for facilitation, step-by-step process mapping instructions, and process mapping naming conventions.

      • Process Mapping Guide

      Infographic

      Workshop: Build a Winning Business Process Automation Playbook

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Identify Automation Opportunities

      The Purpose

      Understand the goals and visions of business process automation.

      Develop your guiding principles.

      Build a backlog of automation opportunities

      Key Benefits Achieved

      Business process automation vision, expectations, and objectives.

      High-priority automation opportunities identified to focus on.

      Activities

      1.1 State your objectives and metrics.

      1.2 Build your backlog.

      Outputs

      Business process automation vision and objectives

      Business process automation guiding principles

      Process automation opportunity backlog

      2 Define Your MVAs

      The Purpose

      Assess and optimize high-strategic-importance business process automation use cases from the end user’s perspective.

      Shortlist your automation solutions.

      Build and plan to deliver minimum viable automations (MVAs).

      Key Benefits Achieved

      Repeatable framework to assess and optimize your business process.

      Selection of the possible solutions that best fit the business process use case.

      Maximized learning with a low-risk minimum viable automation.

      Activities

      2.1 Optimize your processes.

      2.2 Automate your processes.

      2.3 Define and roadmap your MVAs.

      Outputs

      Assessed and optimized business processes with a repeatable framework

      Fit assessment of use cases to automation solutions

      MVA definition and roadmap

      3 Deliver Your MVAs

      The Purpose

      Modernize your SDLC to support business process automation delivery.

      Key Benefits Achieved

      An SDLC that best supports the nuances and complexities of business process automation delivery.

      Activities

      3.1 Deliver your MVAs

      Outputs

      Refined and enhanced SDLC

      Manage Poor Performance While Working From Home

      • Buy Link or Shortcode: {j2store}599|cart{/j2store}
      • member rating overall impact: 9.0/10 Overall Impact
      • member rating average dollars saved: $1,600 Average $ Saved
      • member rating average days saved: 18 Average Days Saved
      • Parent Category Name: Manage & Coach
      • Parent Category Link: /manage-coach
      • For many, emergency WFH comes with several new challenges such as additional childcare responsibilities, sudden changes in role expectations, and negative impacts on wellbeing. These new challenges, coupled with previously existing ones, can result in poor performance. Owing to the lack of physical presence and cues, managers may struggle to identify that an employee’s performance is suffering. Even after identifying poor performance, it can be difficult to address remotely when such conversations would ideally be held in person.

      Our Advice

      Critical Insight

      • Poor performance must be managed, despite the pandemic. Evaluating root causes of performance issues is more important than ever now that personal factors such as lack of childcare and eldercare for those working from home are complicating the issue.

      Impact and Result

      • Organizations need to have a clear process for improving performance for employees working remotely during the COVID-19 pandemic. Provide managers with resources to help them identify performance issues and uncover their root causes as part of addressing overall performance. This will allow managers to connect employees with the required support while working with them to improve performance.

      Manage Poor Performance While Working From Home Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Follow the remote performance improvement process

      Determine how managers can identify poor performance remotely and help them navigate the performance improvement process while working from home.

      • Manage Poor Performance While Working From Home Storyboard
      • Manage Poor Performance While Working From Home: Manager Guide
      • Manage Poor Performance While Working From Home: Infographic

      2. Clarify roles and leverage resources

      Clarify roles and responsibilities in the performance improvement process and tailor relevant resources.

      • Wellness and Working From Home
      [infographic]

      Further reading

      Manage Poor Performance While Working From Home

      Assess and improve remote work performance with our ready-to-use tools.

      Executive Summary

      McLean & Company Insight

      Poor performance must be managed, despite the pandemic. Evaluating root causes of performance issues is more important than ever now that personal factors such as lack of childcare and eldercare for those working from home are complicating the issue.

      Situation

      COVID-19 has led to a sudden shift to working from home (WFH), resulting in a 72% decline in in-office work (Ranosa, 2020). While these uncertain times have disrupted traditional work routines, employee performance remains critical, as it plays a role in determining how organizations recover. Managers must not turn a blind eye to performance issues but rather must act quickly to support employees who may be struggling.

      Complication

      For many, emergency WFH comes with several new challenges such as additional childcare responsibilities, sudden changes in role expectations, and negative impacts on wellbeing. These new challenges, coupled with previously existing ones, can result in poor performance. Owing to the lack of physical presence and cues, managers may struggle to identify that an employee’s performance is suffering. Even after identifying poor performance, it can be difficult to address remotely when such conversations would ideally be held in person.

      Solution

      Organizations need to have a clear process for improving performance for employees working remotely during the COVID-19 pandemic. Provide managers with resources to help them identify performance issues and uncover their root causes as part of addressing overall performance. This will allow managers to connect employees with the required support while working with them to improve performance.

      Manage Poor Performance While Working From Home is made up of the following resources:

      1

      Identify

      2

      Initiate

      3

      Deploy

      4

      a) Follow Up
      b) Decide
      Storyboard

      This storyboard is organized by the four steps of the performance improvement process: identify, initiate, deploy, and follow up/decide. These will appear on the left-hand side of the slides as a roadmap.

      The focus is on how HR can design the process for managing poor performance remotely and support managers through it while emergency WFH measures are in place. Key responsibilities, email templates, and relevant resources are included at the end.

      Adapt the process as necessary for your organization.

      Manager Guide

      The manager guide contains detailed advice for managers on navigating the process and focuses on the content of remote performance discussions.

      It consists of the following sections:

      • Identifying poor performance.
      • Conducting performance improvement discussions.
      • Uncovering and addressing root causes of poor performance.
      Manager Infographic

      The manager infographic illustrates the high-level steps of the performance improvement process for managers in a visually appealing and easily digestible manner.

      This can be used to easily outline the process, providing managers with a resource to quickly reference as they navigate the process with their direct reports.

      In this blueprint, “WFH” and “remote working” are used interchangeably.

      This blueprint will not cover the performance management framework; it is solely focused on managing performance issues.

      For information on adjusting the regular performance management process during the pandemic, see Performance Management for Emergency Work-From-Home.

      Identify how low performance is normally addressed

      A process for performance improvement is not akin to outlining the steps of a performance improvement plan (PIP). The PIP is a development tool used within a larger process for performance improvement. Guidance on how to structure and use a PIP will be provided later in this blueprint.

      Evaluate how low performance is usually brought to the attention of HR in a non-remote situation:
      • Do managers approach HR for an employee transfer or PIP without having prior performance conversations with the employee?
      • Do managers come to HR when they need support in developing an employee in order to meet expectations?
      • Do managers proactively reach out to HR to discuss appropriate L&D for staff who are struggling?
      • Do some departments engage with the process while others do not?
      Poor performance does not signal the immediate need to terminate an employee. Instead, managers should focus on helping the struggling employee to develop so that they may succeed.
      Evaluate how poor performance is determined:
      • Do managers use performance data or concrete examples?
      • Is it based on a subjective assessment by the manager?
      Keep in mind that “poor performance” now might look different than it did before the pandemic. Employees must be aware of the current expectations placed on them before they can be labeled as underperforming – and the performance expectations must be assessed to ensure they are realistic.

      For information on adjusting performance expectations during the pandemic, see Performance Management for Emergency Work-From-Home.

      The process for non-union and union employees will likely differ. Make sure your process for unionized employees aligns with collective agreements.

      Determine how managers can identify poor performance of staff working remotely

      1

      Identify

      2

      Initiate

      3

      Deploy

      4

      a) Follow Up
      b) Decide
      Identify: Determine how managers can identify poor performance.
      In person, it can be easy to see when an employee is struggling by glancing over at their desk and observing body language. In a remote situation, this can be more difficult, as it is easy to put on a brave face for the half-hour to one-hour check-in. Advise managers on how important frequent one-one-ones and open communication are in helping identify issues when they arise rather than when it’s too late.

      Managers must clearly document and communicate instances where employees aren’t meeting role expectations or are showing other key signs that they are not performing at the level expected of them.

      What to look for:
      • PM data/performance-related assessments
      • Continual absences
      • Decreased quality or quantity of output
      • Frequent excuses (e.g. repeated internet outages)
      • Lack of effort or follow-through
      • Missed deadlines
      • Poor communication or lack of responsiveness
      • Failure to improve
      It’s crucial to acknowledge an employee might have an “off week” or need time to adjust to working from home, which can be addressed with performance management techniques. Managers should move into the process for performance improvement when:
      • Performance fluctuates frequently or significantly.
      • Performance has dropped for an extended period of time.
      • Expectations are consistently not being met.

      While it’s important for managers to keep an eye out for decreased performance, discourage them from over-monitoring employees, as this can lead to a damaging environment of distrust.

      Support managers in initiating performance conversations and uncovering root causes

      1

      Identify

      2

      Initiate

      3

      Deploy

      4

      a) Follow Up
      b) Decide
      Initiate: Require that managers have several conversations about low performance with the employee.
      Before using more formal measures, ensure managers take responsibility for connecting with the employee to have an initial performance conversation where they will make the performance issue known and try to diagnose the root cause of the issue.

      Coach managers to recognize behaviors associated with the following performance inhibitors:

      Personal Factors

      Personal factors, usually outside the workplace, can affect an employee’s performance.

      Lack of clarity

      Employees must be clear on performance expectations before they can be labeled as a poor performer.

      Low motivation

      Lack of motivation to complete work can impact the quality of output and/or amount of work an employee is completing.

      Inability

      Resourcing, technology, organizational change, or lack of skills to do the job can all result in the inability of an employee to perform at their best.

      Poor people skills

      Problematic people skills, externally with clients or internally with colleagues, can affect an employee’s performance or the team’s engagement.

      Personal factors are a common performance inhibitor due to emergency WFH measures. The decreased divide between work and home life and the additional stresses of the pandemic can bring up new cases of poor performance or exacerbate existing ones. Remind managers that all potential root causes should still be investigated rather than assuming personal factors are the problem and emphasize that there can be more than one cause.

      Ensure managers continue to conduct frequent performance conversations

      Once an informal conversation has been initiated, the manager should schedule frequent one-on-one performance conversations (above and beyond performance management check-ins).

      1

      Identify

      2

      Initiate

      3

      Deploy

      4

      a) Follow Up
      b) Decide
      Explain to managers the purpose of these discussions is to:
      • Continue to probe for root causes.
      • Reinforce role expectations and performance targets.
      • Follow up on any improvements.
      • Address the performance issue and share relevant resources (e.g. HR or employee assistance program [EAP]).
      Given these conversations will be remote, require managers to:
      • Use video whenever possible to read physical cues and body language.
      • Bookend the conversation. Starting each meeting by setting the context for the discussion and finishing with the employee reiterating the key takeaways back will ensure there are no misunderstandings.
      • Document the conversation and share with HR. This provides evidence of the conversations and helps hold managers accountable.
      What is HR’s role? HR should ensure that the manager has had multiple conversations with the employee before moving to the next step. Furthermore, HR is responsible for ensuring manages are equipped to have the conversations through coaching, role-playing, etc.

      For more information on the content of these conversations or for material to leverage for training purposes, see Manage Poor Performance While Working From Home: Manager Guide.

      McLean & Company Insight

      Managers are there to be coaches, not therapists. Uncovering the root cause of poor performance will allow managers to pinpoint supports needed, either within their expertise (e.g. coaching, training, providing flexible hours) or by directing the employee to proper external resources such as an EAP.

      Help managers use formal performance improvement tools with remote workers

      1

      Identify

      2

      Initiate

      3

      Deploy

      4

      a) Follow Up
      b) Decide
      Deploy: Use performance improvement tools.
      If initial performance conversations were unsuccessful and performance does not improve, refer managers to performance improvement tools:
      • Suggest any other available support and resources they have not yet recommended (e.g. EAP).
      • Explore options for co-creation of a development plan to increase employee buy-in. If the manager has been diligent about clarifying role expectations, invite the employee to put together their own action plan for meeting performance goals. This can then be reviewed and finalized with the manager.
      • Have the manager use a formal PIP for development and to get the employee back on track. Review the development plan or PIP with the manager before they share it with the employee to ensure it is clear and has time bound, realistic goals for improvement.
      Using a PIP solely to avoid legal trouble and terminate employees isn’t true to its intended purpose. This is what progressive discipline is for.In the case of significant behavior problems, like breaking company rules or safety violations, the manager will likely need to move to progressive discipline. HR should advise managers on the appropriate process.

      When does the issue warrant progressive discipline? If the action needs to stop immediately, (e.g. threatening or inappropriate behavior) and/or as outlined in the collective agreement.

      Clarify remote PIP stages and best practices

      1

      Identify

      2

      Initiate

      3

      Deploy

      4

      a) Follow Up
      b) Decide
      Sample Stages:
      1. Written PIP
      • HR reviews and signs off on PIP
      • Manager holds meeting to provide employee with PIP
      • Employee reviews the PIP
      • Manager and employee provide e-signatures
      • Signed PIP is given to HR
      2. Possible Extension
      3. Final Notice
      • Manager provides employee with final notice if there has been no improvement in agreed time frame
      • Copy of signed final notice letter given to HR

      Who is involved?

      The manager runs the meeting with the employee. HR should act as a support by:

      • Ensuring the PIP is clear, aligned with the performance issue, and focused on development, prior to the meeting.
      • Pointing to resources and making themselves available prior to, during, and after the meeting.
        • When should HR be involved? HR should be present in the meeting if the manager has requested it or if the employee has approached HR beforehand with concerns about the manager. Keep in mind that if the employee sees HR has been unexpectedly invited to the video call, it could add extra stress for them.
      • Reviewing documentation and ensuring expectations and the action plan are reasonable and realistic.

      Determine the length of the PIP

      • The length of the initial PIP will often depend on the complexity of the employee’s role and how long it will reasonably take to see improvements. The minimum (before a potential extension) should be 30-60 days.
      • Ensure the action plan takes sustainment into account. Employees must be able to demonstrate improvement and sustain improved performance in order to successfully complete a PIP.

      Timing of delivery

      Help the manager determine when the PIP meeting will occur (what day, time of day). Take into account the schedule of the employee they will be meeting with (e.g. avoid scheduling right before an important client call).

      1

      Identify

      2

      Initiate

      3

      Deploy

      4

      a) Follow Up
      b) Decide

      Follow up: If the process escalated to step 3 and is successful.

      What does success look like? Performance improvement must be sustained after the PIP is completed. It’s not enough to simply meet performance improvement goals and expectations; the employee must continue to perform.

      Have the manager schedule a final PIP review with the employee. Use video, as this enables the employee and manager to read body language and minimize miscommunication/misinterpretation.

      • If performance expectations have been met, instruct managers to document this in the PIP, inform the employee they are off the PIP, and provide it to HR.

      The manager should also continue check-ins with the employee to ensure sustainment and as part of continued performance management.

      • Set a specific timeline, e.g. every two weeks or every month. Choose a cadence that works best for the manager and employee.

      OR

      Decide: Determine action steps if the process is unsuccessful.

      If at the end of step 3 performance has not sufficiently improved, the organization (HR and the manager) should either determine if the employee could/should be temporarily redeployed while the emergency WFH is still in place, if a permanent transfer to a role that is a better fit is an option, or if the employee should be let go.

      See the Complete Manual for COVID-19 Layoffs blueprint for information on layoffs in remote environments.

      Managers, HR, and employees all have a role to play in performance improvement

      Managers
      • Identify the outcomes the organization is looking for and clearly outline and communicate the expectations for the employee’s performance.
      • Diagnose root cause(s) of the performance issue.
      • Support employee through frequent conversations and feedback.
      • Coach for improved performance.
      • Visibly recognize and broadcast employee achievements.
      Employees
      • Have open and honest conversations with their manager, acknowledge their accountability, and be receptive to feedback.
      • Set performance goals to meet expectations of the role.
      • Prepare for frequent check-ins regarding improvement.
      • Seek support from HR as required.
      HR
      • Provide managers with a process, training, and support to improve employee performance.
      • Coach managers to ensure employees have been made aware of their role expectations and current performance and given specific recommendations on how to improve.
      • Reinforce the process for improving employee performance to ensure that adequate coaching conversations have taken place before the formal PIP.
      • Coach employees on how to approach their manager to discuss challenges in meeting expectations.

      HR should conduct checkpoints with both managers and employees in cases where a formal PIP was initiated to ensure the process for performance improvement is being followed and to support both parties in improving performance.

      Email templates

      Use the templates found on the next slides to draft communications to employees who are underperforming while working from home.

      Customize all templates with relevant information and use them as a guide to further tailor your communication to a specific employee.

      Customization Recommendations

      Review all slides and adjust the language or content as needed to suit the needs of the employee, the complexity of their role, and the performance issue.

      • The pencil icon to the left denotes slides requiring customization of the text. Customize text in grey font and be sure to convert all font to black when you are done.

      Included Templates

      1. Performance Discussion Follow-Up
      2. PIP Cover Letter

      This template is not a substitute for legal advice. Ensure you consult with your legal counsel, labor relations representative, and union representative to align with collective agreements and relevant legislation.

      Sample Performance Discussion Follow-Up

      Hello [name],

      Thank you for the commitment and eagerness in our meeting yesterday.

      I wanted to recap the conversation and expectations for the month of [insert month].

      As discussed, you have been advised about your recent [behavior, performance, attendance, policy, etc.] where you have demonstrated [state specific issue with detail of behavior/performance of concern]. As per our conversation, we’ll be working on improvement in this area in order to meet expectations set out for our employees.

      It is expected that employees [state expectations]. Please do not hesitate to reach out to me if there is further clarification needed or you if you have any questions or concerns. The management team and I are committed to helping you achieve these goals.

      We will do a formal check-in on your progress every [insert day] from [insert time] to review your progress. I will also be available for daily check-ins to support you on the right track. Additionally, you can book me in for desk-side coaching outside of my regular desk-side check-ins. If there is anything else I can do to help support you in hitting these goals, please let me know. Other resources we discussed that may be helpful in meeting these objectives are [summarize available support and resources]. By working together through this process, I have no doubt that you can be successful. I am here to provide support and assist you through this.

      If you’re unable to show improvements set out in our discussion by [date], we will proceed to a formal performance measure that will include a performance improvement plan. Please let me know if you have any questions or concerns; I am here to help.

      Please acknowledge this email and let me know if you have any questions.

      Thank you,

      PIP Cover Letter

      Hello [name] ,

      This is to confirm our meeting on [date] in which we discussed your performance to date and areas that need improvement. Please find the attached performance improvement plan, which contains a detailed action plan that we have agreed upon to help you meet role expectations over the next [XX days]. The aim of this plan is to provide you with a detailed outline of our performance expectations and provide you the opportunity to improve your performance, with our support.

      We will check in every [XX days] to review your progress. At the end of the [XX]-day period, we will review your performance against the role expectations set out in this performance improvement plan. If you don’t meet the performance requirements in the time allotted, further action and consequences will follow.

      Should you have any questions about the performance improvement plan or the process outlined in this document, please do not hesitate to discuss them with me.

      [Employee name], it is my personal objective to help you be a fully productive member of our team. By working together through this performance improvement plan, I have no doubt that you can be successful. I am here to provide support and assist you through the process. At this time, I would also like to remind you about the [additional resources available at your organization, for example, employee assistance program or HR].

      Please acknowledge this email and let me know if you have any questions.

      Thank you,

      Prepare and customize manager guide and resources

      Sample of Manage Poor Performance While Working From Home: Manager Guide. Manage Poor Performance While Working From Home: Manager Guide

      This tool for managers provides advice on navigating the process and focuses on the content of remote performance discussions.

      Sample of Set Meaningful Employee Performance Measures. Set Meaningful Employee Performance Measures

      See this blueprint for information on setting holistic measures to inspire employee performance.

      Sample of Manage Poor Performance While Working From Home: Infographic. Manage Poor Performance While Working From Home: Infographic

      This tool illustrates the high-level steps of the performance improvement process.

      Sample of Wellness and Working From Home: Infographic. Wellness and Working From Home: Infographic

      This tool highlights tips to manage physical and mental health while working from home.

      Sample of Build a Better Manager: Team Essentials. Build a Better Manager: Team Essentials

      See this solution set for more information on kick-starting the effectiveness of first-time IT managers with essential management skills.

      Sample of Leverage Agile Goal Setting for Improved Employee Engagement & Performance. Leverage Agile Goal Setting for Improved Employee Engagement & Performance

      See this blueprint for information on dodging the micromanaging foul and scoring with agile short-term goal setting.

      Bibliography

      Arringdale, Chris. “6 Tips For Managers Trying to Overcome Performance Appraisal Anxiety.” TLNT. 18 September 2015. Accessed 2018.

      Borysenko, Karlyn. “What Was Management Thinking? The High Cost of Employee Turnover.” Talent Management and HR. 22 April 2015. Accessed 2018.

      Cook, Ian. “Curbing Employee Turnover Contagion in the Workplace.” Visier. 20 February 2018. Accessed 2018.

      Cornerstone OnDemand. Toxic Employees in the Workplace. Santa Monica, California: Cornerstone OnDemand, 2015. Web.

      Dewar, Carolyn and Reed Doucette. “6 elements to create a high-performing culture.” McKinsey & Company. 9 April 2018. Accessed 2018.

      Eagle Hill. Eagle Hill National Attrition Survey. Washington, D.C.: Eagle Hill, 2015. Web.

      ERC. “Performance Improvement Plan Checklist.” ERC. 21 June 2017. Accessed 2018.

      Foster, James. “The Impact of Managers on Workplace Engagement and Productivity.” Interact. 16 March 2017. Accessed 2018.

      Godwins Solicitors LLP. “Employment Tribunal Statistics for 2015/2016.” Godwins Solicitors LLP. 8 February 2017. Accessed 2018.

      Mankins, Michael. “How to Manage a Team of All-Stars.” Harvard Business Review. 6 June 2017. Accessed 2018.

      Maxfield, David, et al. The Value of Stress-Free Productivity. Provo, Utah: VitalSmarts, 2017. Web.

      Murphy, Mark. “Skip Your Low Performers When Starting Performance Appraisals.” Forbes. 21 January 2015. Accessed 2018.

      Quint. “Transforming into a High Performance Organization.” Quint Wellington Redwood. 16 November 2017. Accessed 2018.

      Ranosa, Rachel. "COVID -19: Canadian Productivity Booms Despite Social Distancing." Human Resources Director, 14 April 2020. Accessed 2020.

      Adopt Design Thinking in Your Organization

      • Buy Link or Shortcode: {j2store}327|cart{/j2store}
      • member rating overall impact: 9.6/10 Overall Impact
      • member rating average dollars saved: $23,245 Average $ Saved
      • member rating average days saved: 13 Average Days Saved
      • Parent Category Name: Innovation
      • Parent Category Link: /innovation
      • End users often have a disjointed experience while interacting with your organization in using its products and services.
      • You have been asked by your senior leadership to start a new or revive an existing design or innovation function within your organization. However, your organization has dismissed design thinking as the latest “management fad” and does not buy into the depth and rigor that design thinking brings.
      • The design or innovation function lives on the fringes of your organization due to its apathy towards design thinking or tumultuous internal politics.
      • You, as a CIO, want to improve the user satisfaction with the IT services your team provides to both internal and external users.

      Our Advice

      Critical Insight

      • A user’s perspective while interacting with the products and services is very different from the organization’s internal perspective while implementing and provisioning those. A design-based organization balances the two perspectives to drive user-satisfaction over end-to-end journeys.
      • Top management must have a design thinker – the guardian angel of the balance between exploration (i.e. discovering new business models) and exploitation (i.e. leveraging existing business models).
      • Your approach to adopt design thinking must consider your organization’s specific goals and culture. There’s no one-size-fits-all approach.

      Impact and Result

      • User satisfaction, with the end-to-end journeys orchestrated by your organization, will significantly increase.
      • Design-centric organizations enjoy disproportionate financial rewards.

      Adopt Design Thinking in Your Organization Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should adopt design thinking in your organization, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. What is design thinking?

      The focus of this phase is on revealing what designers do during the activity of designing, and on building an understanding of the nature of design ability. We will formally examine the many definitions of design thinking from experts in this field. At the core of this phase are several case studies that illuminate the various aspects of design thinking.

      • Adopt Design Thinking in Your Organization – Phase 1: What Is Design Thinking?
      • Victor Scheinman's Experiment for Design

      2. How does an organization benefit from design thinking?

      This phase will illustrate the relevance of design in strategy formulation and in service-design. At the core of this phase are several case studies that illuminate these aspects of design thinking. We will also identify the trends impacting your organization and establish a baseline of user-experience with the journeys orchestrated by your organization.

      • Adopt Design Thinking in Your Organization – Phase 2: How Does an Organization Benefit From Design Thinking?
      • Trends Matrix (Sample)

      3. How do you build a design organization?

      The focus of this phase is to:

    • Measure the design-centricity of your organization and subsequently, identify the areas for improvement.
    • Define an approach for a design program that suites your organization’s specific goals and culture.
      • Adopt Design Thinking in Your Organization – Phase 3: How Do You Build a Design Organization?
      • Report on How Design-Centric Is Your Organization (Sample)
      • Approach for the Design Program (Sample)
      • Interview With David Dunne on Design Thinking
      • Interview With David Dunne on Design Thinking (mp3)
      [infographic]

      Workshop: Adopt Design Thinking in Your Organization

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 What Is Design Thinking?

      The Purpose

      The focus of this module is on revealing what designers do during the activity of designing, and on building an understanding of the nature of design ability. We will also review the report on the design-centricity of your organization and subsequently, earmark the areas for improvement.

      Key Benefits Achieved

      An intimate understanding of the design thinking

      An assessment of design-centricity of your organization and identification of areas for improvement

      Activities

      1.1 Discuss case studies on how designers think and work

      1.2 Define design thinking

      1.3 Review report from Info-Tech’s diagnostic: How design-centric is your organization?

      1.4 Earmark areas for improvement to raise the design-centricity of your organization

      Outputs

      Report from Info-Tech’s diagnostic: ‘How design-centric is your organization?’ with identified areas for improvement.

      2 How Does an Organization Benefit From Design Thinking?

      The Purpose

      In this module, we will discuss the relevance of design in strategy formulation and service design. At the core of this module are several case studies that illuminate these aspects of design thinking. We will also identify the trends impacting your organization. We will establish a baseline of user experience with the journeys orchestrated by your organization.

      Key Benefits Achieved

      An in-depth understanding of the relevance of design in strategy formulation and service design

      An understanding of the trends that impact your organization

      A taxonomy of critical customer journeys and a baseline of customers’ satisfaction with those

      Activities

      2.1 Discuss relevance of design in strategy through case studies

      2.2 Articulate trends that impact your organization

      2.3 Discuss service design through case studies

      2.4 Identify critical customer journeys and baseline customers’ satisfaction with those

      2.5 Run a simulation of design in practice

      Outputs

      Trends that impact your organization.

      Taxonomy of critical customer journeys and a baseline of customers’ satisfaction with those.

      3 How to Build a Design Organization

      The Purpose

      The focus of this module is to define an approach for a design program that suits your organization’s specific goals and culture.

      Key Benefits Achieved

      An approach for the design program in your organization. This includes aspects of the design program such as its objectives and measures, its model (one of the five archetypes or a hybrid one), and its governance.

      Activities

      3.1 Identify objectives and key measures for your design thinking program

      3.2 Structure your program after reviewing five main archetypes of a design program

      3.3 Balance between incremental and disruptive innovation

      3.4 Review best practices of a design organization

      Outputs

      An approach for your design thinking program: objectives and key measures; structure of the program, etc.

      Communicate Any IT Initiative

      • Buy Link or Shortcode: {j2store}428|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Lead
      • Parent Category Link: /lead

      IT communications are often considered ineffective and unengaging. This is demonstrated by the:

      • Lack of expectation that IT should communicate well. Why develop a skill that no one expects IT to deliver on?
      • Failure to recognize the importance of communication to engage employees and communicate ideas.
      • Perception that communication is a broadcast not a continuous dialogue.
      • Inability to create, monitor, and manage feedback mechanisms.
      • Overreliance on data as the main method of communication instead of as evidence to support a broader narrative.

      Our Advice

      Critical Insight

      • Don't make data your star. It is a supporting character. People can argue about the collection methods or interpretation of the data, but they cannot argue with the story you share.
      • Messages are also non-verbal. Practice using your voice and body to set the right tone and impact your audience.
      • Recognize that communications are essential even in highly technical IT environments.
      • Measure if the communication is being received and resulting in the desired outcome. If not, modify what and how the message is being expressed.

      Impact and Result

      • Develop an actionable plan to deliver consistent, timely messaging for all audiences.
      • Compose and deliver meaningful messages.
      • Consistently deliver the right information and the right time to the right stakeholders.

      Communicate Any IT Initiative Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Communicate Any IT Initiative Deck – A step-by-step document that walks you through how to plan, compose, and deliver communications to any stakeholder up, down, or across the organization.

      This blueprint not only provides the tools and techniques for planning, composing, and delivering effective communications, but also walks you through practical exercises. Practice and perfect your communication, composition, and delivery skills for any IT initiative.

      • Communicate Any IT Initiative – Phases 1-3

      2. Communicate Any IT Initiative Facilitation Deck – A step-by-step communications workshop deck suitable for any workshop with a communication component.

      Communication concepts and exercises that teach you how to plan, compose, and deliver effective communications. The deck includes practical tools, techniques, and skills practice.

      • Communicate Any IT Initiative Facilitation Deck

      3. Communications Planner – An communications plan template that includes a section to define a change, a communications plan, communications calendars, and a pitch composition exercise.

      This communications planner is a tool that accompanies the Effective IT Communications blueprint and the Communicate Any IT Initiative Facilitation Deck so that you can plan your communications, view your deliverables, and compose your pitch all in one document.

      • Communications Planner Tool

      4. Stakeholder Analysis Tool – A tool to help ensure that all stakeholders are identified and none are missed.

      A tool for identifying stakeholders and conducting an analysis to understand their degree of influence or impact.

      • Stakeholder Management Analysis Tool
      [infographic]

      Further reading

      Communicate Any IT Initiative

      Plan, compose, and deliver communications that engage your audience.

      Executive Summary

      Your Challenge Common Obstacles Info-Tech’s Approach
      Communicating about your initiative is when the work really begins. Many organizations struggle with:
      • Knowing what target audiences need to be communicated with.
      • Communicating the same message consistently and clearly across target audiences.
      • Communicating to target audiences at the right times.
      • Selecting a channel that will be most effective for the message and practicing to deliver that message.
      Some of the challenges IT faces when it comes to communicating its initiatives includes:
      • Not being given the opportunity or time to practice composing or delivering communications.
      • Coordinating the communications of this initiative with other initiative communications.
      • Forgetting to communicate with key stakeholders.
      Choosing not to communicate because we do not know how it’s leading to initiative failures and lack of adoption by impacted parties.
      For every IT initiative you have going forward, focus on following these three steps:
      1. Create a plan of action around who, what, how, and when communications will take place.
      2. Compose an easy-to-understand pitch for each stakeholder audience.
      3. Practice delivering the message in an authentic and clear manner.
      By following these steps, you will ensure that your audience always understands and feels ready to engage with you.

      Info-Tech Insight
      Every IT employee can be a great communicator; it just takes a few consistent steps, the right tools, and a dedication to practicing communicating your message.

      Info-Tech’s approach

      Effective communications is not a broadcast but a dialogue between communicator and audience in a continuous feedback loop.

      Continuous Feedback Loop

      The Info-Tech difference:

      1. The skills needed to communicate effectively as a front-line employee or CIO are the same. It’s important to begin the development of these skills from the beginning of one's career.
      2. Time is a non-renewable resource. Any communication needs to be considered valuable and engaging by the audience or they will be unforgiving.
      3. Don't make data your star. It is a supporting character. People can argue about the collection methods or interpretation of the data, but they cannot argue about the story you share.

      Poor communication can lead to dissatisfied stakeholders

      27.8% of organizations are not satisfied with IT communications.

      25.8% of business stakeholders are not satisfied with IT communications.

      Source: Info-Tech Diagnostic Programs; n=34,345 business stakeholders within 604 organizations

      The bottom line? Stakeholders for any initiative need to be communicated with often and well. When stakeholders become dissatisfied with IT’s communication, it can lead to an overall decrease in satisfaction with IT.

      Good IT initiative communications can be leverage

      • IT risk mitigation and technology initiative funding are dependent on critical stakeholders comprehending the risk impact and initiative benefit in easy-to-understand terms.
      • IT employees need clear and direct information to feel empowered and accountable to do their jobs well.
      • End users who have a good experience engaging in communications with IT employees have an overall increase in satisfaction with IT.
      • Continuously demonstrating IT’s value to the organization comes when those initiatives are clearly aligned to overall objectives – don’t assume this alignment is being made.
      • Communication prevents assumptions and further miscommunication from happening among IT employees who are usually impacted and fear change the most.

      “Nothing gets done properly if it's not communicated well.”
      -- Nastaran Bisheban, CTO KFC Canada

      Approach to communications

      Introduction
      Review effective communications.

      Plan
      Plan your communications using a strategic tool.

      Compose
      Create your own message.

      Deliver
      Practice delivering your own message.

      Info-Tech’s methodology for effective IT communications

      1. Plan Strategic Communications 2. Compose a Compelling Message 3. Deliver Messages Effectively
      Step Activities
      1. Define the Change
      2. Determine Target Audience
      3. Communication Outcomes
      4. Clarify the Key Message(s)
      5. Identify the Owner and Messenger(s)
      6. Select the Right Channels
      7. Establish a Frequency and Time Frame
      8. Obtain Feedback and Improve
      9. Finalize the Calendar
      1. Craft a Pitch
      2. Revise the Pitch
      1. Deliver Your Pitch
      2. Refine and Deliver Again
      Step Outcomes Establish an easy-to-read view of the key communications that need to take place related to your initiative or change. Practice writing a pitch that conveys the message in a compelling and easy-to-understand way. Practice delivering the pitch. Ensure there is authenticity in the delivery while still maintaining the audience’s attention.

      This blueprint can support communication about any IT initiative

      • Strategy or roadmap
      • Major transformational change
      • System integration
      • Process changes
      • Service changes
      • New solution rollouts
      • Organizational restructuring

      We recommend considering this blueprint a natural add-on to any completed Info-Tech blueprint, whether it is completed in the DIY fashion or through a Guided Implementation or workshop.

      Key deliverable:

      Communication Planner
      A single place to plan and compose all communications related to your IT initiative.

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals.

      Facilitation Guide
      A step-by-step guide to help your IT organization develop a communication plan and practice composing and delivering key messages.

      Stakeholder Analysis
      An ability to assess all stakeholders based on impact, influence, and involvement.

      Workshop Overview

      MorningAfternoon
      ActivitiesPlan Strategic Communications for Your Initiative
      1. Define the Change
      2. Determine Target Audience
      3. Communication Outcomes
      4. Clarify the Key Message(s)
      5. Identify the Owner and Messenger(s)
      6. Select the Right Channels
      7. Establish a Frequency and Time Frame
      8. Obtain Feedback and Improve
      9. Finalize the Calendar
      Compose and Deliver a Compelling Message
      1. Craft a Pitch
      2. Revise the Pitch
      3. Deliver Your Pitch
      4. Refine and Deliver Again
      Deliverables
      1. Communication planner with weekly, monthly, and yearly calendar views to ensure consistent and ongoing engagement with every target audience member
      1. Crafted pitches that can be used for communicating the initiative to different stakeholders
      2. Skills and ability to deliver messages more effectively

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889

      Key KPIs for communication with any stakeholder

      Measuring communication is hard; use these to determine effectiveness:

      Goal Key Performance Indicator (KPI) Related Resource
      Obtain board buy-in for IT strategic initiatives. X% of IT initiatives that were approved to be funded.
      Number of times that technical initiatives were asked to be explained further.
      Using our Board Presentation Review
      Ensure stakeholders feel engaged during initiatives. X% of business leadership satisfied with the statement “IT communicates with your group effectively.” Using the CIO Business Vision Diagnostic
      End users know what IT initiatives are going to impact the products or services they use. X% of end users that are satisfied with communications around changing services or applications. Using the End-User Satisfaction Survey
      Project stakeholders receive sufficient communication throughout the initiative. X% overall satisfaction with the quality of the project communications. Using the PPM Customer Satisfaction Diagnostic
      Employees are empowered to perform on IT initiatives. X% satisfaction employees have with statement “I have all the resources and information I need to do a great job.” Using the Employee Engagement Diagnostic Program

      Phase 1

      Plan Strategic Communications

      Activities
      1.1 Define the Change
      1.2 Determine Target Audience
      1.3 Communication Outcomes
      1.4 Clarify the Key Message(s)
      1.5 Identify the Owner and Messenger(s)
      1.6 Select the Right Channels
      1.7 Establish a Frequency and Time Frame
      1.8 Obtain Feedback and Improve
      1.9 Finalize the Calendar

      Communicate Any IT Initiative Effectively
      Phase1 > Phase 2 > Phase 3

      This step involves the following participants:
      Varies based on those who would be relevant to your initiative.

      Outcomes of this step
      Create an easy-to-follow communications plan to ensure that the right message is sent to the right audience using the right medium and frequency.

      What is an IT change?

      Before communicating, understand the degree of change.

      Incremental Change:
      • Changes made to improve current processes or systems (e.g. optimizing current technology).
      Transitional Change:
      • Changes that involve dismantling old systems and/or processes in favor of new ones (e.g. new product or services added).
      Transformational Change:
      • Significant change in organizational strategy or culture resulting in substantial shift in direction.
      Examples:
      • New or changed policy
      • Switching from on-premises to cloud-first infrastructure
      • Implementing ransomware risk controls
      • Implementing a learning & development plan
      Examples:
      • Moving to an insourced or outsourced service desk
      • Developing a BI & analytics function
      • Integrating risk into organization risk
      • Developing a strategy (technology, architecture, security, data, service, infrastructure, application)
      Examples:
      • Organizational redesign
      • Acquisition or merger of another organization
      • Implementing a digital strategy
      • A new CEO or board taking over the organization's direction

      Consider the various impacts of the change

      Invest time at the start of the project to develop a detailed understanding of the impact of the change. This will help to create a plan that will simplify the change and save time in the end. Evaluate the impact from a people, process, and technology perspective.

      Leverage a design thinking principle: Empathize with the stakeholder – what will change?

      People

      • Team structure
      • Reporting structure
      • Career paths
      • Job skills
      • Responsibilities
      • Company vision/mission
      • Number of FTE
      • Culture
      • Training required

      Process

      • Budget
      • Work location
      • Daily workflow
      • Working conditions
      • Work hours
      • Reward structure
      • Required number of completed tasks
      • Training required

      Technology

      • Required tools
      • Required policies
      • Required systems
      • Training required

      1.1 Define the change

      30 minutes

      1. While different stakeholders will be impacted by the change differently, it’s important to be able to describe what the change is at a higher level.
      2. Have everyone take eight minutes to jot down what the change is and why it is happening in one to two sentences. Tab 2 of the Communication Planner Tool can also be used to house the different ideas.
      3. Present the change statements to one another.
      4. By leveraging one of the examples or consolidating many examples, as a group document:
        • What is the change?
        • Why is it happening?
      5. The goal is to ensure that all individuals involved in establishing or implementing the change have the same understanding.
      Input Output
      • Individual ideas about what change is occurring and why.
      • A single statement that reflects the change occurring and the rationale for why the change is needed.
      Materials Participants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      Ensure effective communication by focusing on four key elements

      Audience
      Stakeholders (either groups or individuals) who will receive the communication.

      Message
      Information communicated to impacted stakeholders. Must be rooted in a purpose or intent.

      Messenger
      Person who delivers the communication to the audience. The communicator and owner are two different things.

      Channel
      Method or channel used to communicate to the audience.

      Identify the target audience

      The target audience always includes groups and individuals who are directly impacted by the change and may also include those who are change adjacent.

      Define the target audience: Identify which stakeholders will be the target audience of communications related to the initiative. Stakeholders can be single individuals (CFO) or groups (Applications Team).

      Stakeholders to consider:

      • Who is sponsoring the initiative?
      • Who benefits from the initiative?
      • Who loses from the initiative?
      • Who can make approvals?
      • Who controls resources?
      • Who has specialist skills?
      • Who implements the changes?
      • Who will be adversely affected by potential environmental and social impacts in areas of influence that are affected by what you are doing?
      • At which stage will stakeholders be most affected (e.g. procurement, implementation, operations, decommissioning)?
      • Will other stakeholders emerge as the phases are started and completed?

      1.2a Determine target audience

      20 minutes

      1. Consider all the potential individuals or groups of individuals who will be impacted or can influence the outcome of the initiative.
      2. On tab 3 of the Communication Planner Tool, list each of the stakeholders who will be part of the target audience. If in person, use sticky notes to define the target audiences. The individuals or group of individuals that make up the target audience are all the people who require being communicated with before, during, or after the initiative.
      3. As you list each target audience, consider how they perceive IT. This perception could impact how you choose to communicate with the stakeholder(s).
      InputOutput
      • The change
      • Why the change is needed
      • A list of individuals or group of individuals that will be communicated with.
      MaterialsParticipants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      1.2b Conduct a stakeholder analysis (optional)

      1 hour

      1. For each stakeholder identified as a part of the target audience, conduct an analysis to understand their degree of influence or impact.
      2. Based on the stakeholder, the influence or impact of the change, initiative, etc. can inform the type and way of communicating.
      3. This is a great activity for those who are unsure how to frame communications for each stakeholder identified as a target audience.
      InputOutput
      • The change
      • Why the change is needed
      • A list of individuals or group of individuals that will be communicated with
      • The degree of influence or impact each target audience stakeholder has.
      MaterialsParticipants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Stakeholder Management Analysis Tool

      Determine the desired outcome of communicating with each audience

      For each target audience, there will be an overall goal on why they need to be communicated with. This outcome or purpose is often dependent on the type of influence the stakeholder wields within the organization as well as the type of impact the change or initiative will have. Depending on the target audience, consider each of the communication outcomes listed below.

      Communicating Across the Organization Communicating Up to Board or Executives Communicating Within IT
      • Obtain buy-in
      • Obtain approval
      • Obtain funding
      • Demonstrate alignment to organization objectives
      • Reduce concerns about risk
      • Demonstrate alignment to organization objectives
      • Demonstrate alignment to individual departments or functions
      • Obtain other departments’ buy-in
      • Inform about a crisis
      • Inform about the IT change
      • Obtain adoption related to the change
      • Obtain buy-in
      • Inform about the IT change
      • Create a training plan
      • Inform about department changes
      • Inform about organization changes
      • Inform about a crisis
      • Obtain adoption related to the change
      • Distribute key messages to change agents

      1.3 Communication outcomes

      30 minutes

      1. For each stakeholder, there may be one or more reasons why you need to communicate with them. On tab 3 of the Communication Planner Tool or on a whiteboard, begin to identify the objective or outcome your team is seeking by engaging in each target audience.
      2. As you move through the communication outcomes, it could result in more than one outcome for each target audience.
      3. Ensure there is one line for each target audience desired communication outcome. Many stakeholders might need to be communicated with for several reasons. If using the Communication Planner Tool, add the target audience name in column C for as many different communication outcomes there are in column D related to that stakeholder.
      InputOutput
      • The change
      • A list of individuals or group of individuals that will be communicated with
      • Outcome or objective of communicating with each stakeholder
      MaterialsParticipants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      Establish and define key messages based on organizational objectives

      What are key messages?
      • Key messages guide all internal communications to ensure they are consistent, unified, and straightforward.
      • Distill key messages down from organizational objectives and use them to reinforce the organization’s strategic direction. Key messages should inspire employees to act in a way that will help the organization reach its objectives.
      How to establish key messages: Ground key messages in organizational strategy and culture. These should be the first places you look to determine the organization’s key messages:
      • Refer to organizational strategy documents. What needs to be reinforced in internal communications to ensure the organization can achieve its strategy? This is a key message.
      • Look at the organization’s values. How do values guide how work should be done? Do employees need to behave in a certain way or keep a certain value top of mind? This is a key message.

      Key messages should be clear, concise, and consistent (Porter, 2014). The intent is to convey important information in a way that is relatable and memorable, to promote reinforcement, and ultimately, to drive action.

      Info-Tech Insight
      Empathizing with the audience is key to anticipating and addressing objections as well as identifying benefits. Customize messaging based on audience attributes such as work model (e.g. hybrid), anticipated objections, what's in it for me? (WIIFM), and specific expectations.

      1.4 Clarify the key messages

      25 minutes

      1. Divide the number of communication lines up equally amongst the participants.
      2. Based on the outcome expected from engaging that target audience in communications, define one to five key messages that should be expressed.
      3. The key messages should highlight benefits anticipated, concerns anticipated, details about the change, and plan of action or next steps. The goal here is to ensure the target audience is included in the communication process.
      4. The key messages should be focused on how the target audience receives a consistent message, especially if different communication messengers are involved.
      5. Document the key messages on tab 3 of the Communication Planner Tool.
      InputOutput
      • The change
      • Target audience
      • Communication outcomes
      • Key messages to support a consistent approach
      MaterialsParticipants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      Understand to how to identify appropriate messengers

      Messages must be communicated by a variety of individuals across the organization. Select the messenger depending on the message characteristics (e.g. audience, message, medium). The same messenger can be used for a variety of messages across different mediums.

      Personal impact messages should be delivered by an employee's direct supervisor.

      Organizational impact messages and rationale should be delivered by senior leaders in the affected areas.

      Chart Preferred Messenger for Change Messages

      Recent research by Prosci found employees prefer to hear personal messages from their direct manager and organizational messages from the executive leadership team.

      Fifty percent of respondents indicated the CEO as the preferred messenger for organizational change messages.

      Select the appropriate messenger

      For each audience, message, and medium, review whether the message is personal or organizational to determine which messengers are best.

      The number and seniority of messengers involved depends on the size of the change:

      • Incremental change
        • Personal messages from direct supervisors
        • Organizational messages from a leader in the audience’s function or the direct supervisor
      • Transitional change
        • Personal messages from direct supervisors or function leaders
        • Organizational messages from a leader in the audience’s function or the C suite
      • Transformational change
        • Personal messages from direct supervisors or function leaders
        • Organizational messages from the CEO or C-suite
        • Cascading messages are critical in this type of change because all levels of the organization will be involved

      Communication owner vs. messenger

      Communication Owner

      Single person
      Accountable for the communication message and activities
      Oversees that the communication does not contradict other communications
      Validates the key messages to be made

      Communication Messenger(s)

      Single person or many people
      Responsible for delivering the intended message
      Engages the target audience in the communication
      Ensures the key messages are made in a consistent and clear manner

      1.5 Identify the owner and messenger(s)

      30 minutes

      1. For every communication, there needs to be a single owner. This is the person who approves the communication and will be accountable for the communication
      2. The messenger(s) can be several individuals or a single individual depending on the target audience and desired outcome being sought through the communications.
      3. Identify the person or role who will be accountable for the communication and document this in the Communication Planner Tool.
      4. Identify the person(s) or role(s) who will be responsible for delivering the communication and engaging the target audience and document this in the Communication Planner Tool.
      Input Output
      • Individual ideas about what change is occurring and why.
      • A single statement that reflects the change occurring and the rationale for why the change is needed.
      Materials Participants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      Review appropriate channel for different types of messages

      Communication channels are in-person, paper-based, or tech-enabled. Provide communicators with guidance on which mediums to use in different situations.

      First question: Should the communication be delivered in-person or not?
      Types of channels In-Person Paper-Based or Tech-Enabled
      Questions to consider
      • How is your message likely to be received? Is the message primarily negative?
      • Will the message prompt a lot of dialogue or questions? Will it require significant context or clarification?
      Note: Messages that are important, complex, or negative must be delivered in person. This allows the sender to provide context, clarify questions, and collect feedback.
      • Use paper-based and tech-enabled communications to provide reminders or updates.
      • When deciding which of the two to use, think about your audience: do they have regular access to a computer?
      Two-way interaction Supplement in-person communications with paper-based or tech-enabled communications to provide follow-up and consistency (Government of Nova Scotia). Tech-enabled communications allow the sender to deliver messages when they do not co-locate with the receiver. That said, make sure paper-based communications are provided to those without regular access to a computer.

      Consider accessibility when communicating change – not all employees will have access to the same mediums. To ensure inclusivity, strategically plan which mediums to use to reach the entire audience.

      Select communication channels

      Medium Description Key Messages When to Use
      One-on-One Meetings Individual meetings between managers and their direct reports to ensure they understand the change, can express any concerns, and obtain feedback or recommendations.
      • How the change will impact the employee, what they can expect throughout the change, how they can get support, what the timelines are, etc.
      • Requests for feedback.
      • Responses to feedback.
      • Most applicable for personal messages throughout all stages of change.
      • When real-time feedback is needed.
      • To understand the change’s impact on each employee, understand their emotional reactions and provide support.
      • After a change has been announced and continuing at a regular cadence until after the change has been implemented. Frequency of meetings will vary by employee over the course of the change.
      Team Meeting A meeting of a work unit or department. Can be virtual, in person, or a combination. Led by the work unit or department head/manager.
      • How the change will impact the team – how work gets done, who they work with, etc.
      • Available timelines regarding the change.
      • Support available throughout the change.
      • Most applicable for personal messages throughout all change stages.
      • When real-time communication is needed to keep everyone on the same page and provide an opportunity to ask questions (essential for buy-in).
      • To announce a small change or after a larger change announcement. Continue frequently until the end of adoption, with time reserved for ad hoc meetings.
      Email Electronic communication sent to the audience’s company emails, or in the absence of that, to their personal emails.
      • Overarching details and timelines.
      • Short, easy-to-digest pieces of information that either provide a summary of what to expect or describe actions employees need to take.
      • Applicable for both personal and organizational messages, depending on the messenger. Send personal messages in separate emails from organizational messages.
      • To communicate key details quickly and to a distributed workforce.
      • To reinforce or reiterate information that has been shared in person. Can be used broadly or target specific employees/groups.

      Select communication channels

      Medium Description Key Messages When to Use
      Town Hall Virtual or in-person meeting where senior leadership shares information with a wide audience about the change and answers questions.
      • Messaging that is applicable to a large audience.
      • The strategic decisions of senior leadership.
      • Highlight positive initiative outcomes.
      • Recognize employee efforts.
      • Report on engagement.
      • Most applicable for organizational messages to launch a change or between milestones in a long-term or complex change.
      • To enable senior leaders to explain strategic decisions to employees.
      • To allow employees to ask questions and provide feedback.
      • When support of senior leadership is critical to change success.
      Roadshow A series of meetings where senior leadership or the change champion travels to different geographic locations to hold town halls adapted to each location’s audience.
      • Why the change is happening, when the change is happening, who will be impacted, expectations, and key points of contact.
      • Most applicable for organizational messages to launch a change and between milestones during a long-term, large, or complex change.
      • For a change impacting several locations.
      • When face time with senior leadership is critical to developing understanding and adoption of the change. Satellite locations can often feel forgotten. A roadshow provides access to senior leadership and lends the credibility of the leader to the change.
      • To enable live two-way communication between employees and leadership.

      Select communication channels

      Medium Description Key Messages When to Use
      Intranet An internal company website that a large number of employees can access at any time.
      • Information that has already been communicated to the audience before, so they can access it at any time.
      • FAQs and/or general details about the change (e.g. milestones).
      • Most applicable for organizational messages.
      • To post relevant documentation so the audience can access it whenever they need it.
      • To enable consistency in answers to common questions.
      Training Scheduled blocks of time for the team to learn new skills and behaviors needed to successfully adapt to the change.
      • Reinforce the need for change and the benefits the change will have.
      • Most applicable for organizational messages during the implementation stage.
      • To reduce anxiety over change initiatives, improve buy-in, and increase adoption by helping employees develop skills and behaviors needed to perform effectively.
      Video Message A prerecorded short video clip designed for either simultaneous broadcast or just-in-time viewing. Can be sent over email or mobile or uploaded to a company portal/intranet.
      • Positive messaging to convey enthusiasm for the change.
      • Details about why the organization is changing and what the benefits will be, updates on major milestone achievements, etc.
      • Most applicable for organizational messages, used on a limited basis at any point during the change.
      • Effective when the message needs to appear more personal by putting a face to the message and when it can be presented in a condensed time frame.
      • When a message needs to be delivered consistently across a variety of employees, locations, and time zones.
      • To provide updates and recognize key achievements.

      Select communication channels

      Medium Description Key Messages When to Use
      Shift Turnover Meeting A meeting between teams or departments when a shift changes over; sometimes called a shift report. Used to communicate any relevant information from the outgoing shift to the incoming shift members.
      • Details related to the activities performed during the shift.
      • Most applicable for personal impact messages during the implementation stage to reinforce information shared using other communication mediums.
      • Where change directly impacts role expectations or performance so teams hear the same message at the same time.
      Company Newsletter Electronic or hardcopy newsletter published by the company. Contains timely updates on company information.
      • Overarching change details.
      • Information that has already been communicated through other mediums.
      • Varies with the change stage and newsletter frequency.
      • Most applicable for organizational messages throughout the change.
      • When the change implementation is expected to be lengthy and audiences need to be kept updated.
      • To celebrate change successes and milestone achievements.
      Sign/Poster Digital or paper-based sign, graphic, or image. Includes posters, screensavers, etc.
      • Positive messaging to convey enthusiasm for the change.
      • Key dates and activities.
      • Key contacts.
      • Most applicable for organizational messages throughout the change.
      • As visual reminders in common, highly visible locations (e.g. a company bulletin board, elevator TV monitors).

      1.6 Select the right channels

      20 minutes

      1. Consider the different channels that were described and presented on the previous five slides. Each channel has element(s) to it that will allow it to be more beneficial based on the communication target audience, outcome, and messenger.
      2. Evenly assign the number of communication rows on tab 3 of the Communication Planner Tool and input the channel that should be used.
      3. Consider if the channel will:
        • Obtain the desired outcome of the communication.
        • Be completed by the messenger(s) defined.
        • Support the target audience in understanding the key messages.
      4. If any target audience communication requires several channels, add additional rows to the planner on TAB 3.
      InputOutput
      • Target audience
      • Communication outcome
      • Communication messenger(s)
      • The right channel selected to support the desired communication outcome.
      MaterialsParticipants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      Define the communication time frame based on the initiative

      Communication occurs during four of the five stages of an initiative:

      01 Identify and prioritize 02 Prepare for initiative 03 Create a communication plan 04 Implement change 05 Sustain the desired outcome
      Before During After
      • Communication begins with sponsors and the project team.
      • Set general expectations with project team and sponsors.
      • Outline the communication plan for the remaining stages.
      • Set specific expectations with each stakeholder group.
      • Implement the communication plan.
      • Use feedback loops to determine updates or changes to communications.
      • Communication continues as required after the change.
      • Feedback loops continue until change becomes business as usual.
      Where communication needs to happen

      Don’t forget: Cascade messages down through the organization to ensure those who need to deliver messages have time to internalize the change before communicating it to others. Include a mix of personal and organizational messages, but where possible, separate personal and organizational content into different communications.

      Establish a frequency that aligns to the desired communication outcome

      Successful communications are frequent communications.

      • The cadence of a communication is highly dependent on the objective of the communication.
      • Each target requires a different frequency as well:
        • Board Presentations > four times a year is a good frequency
        • Executive Leadership > monthly frequency
        • Organizationally > annually and when necessary
        • Organization Crises > daily, if not hourly
        • IT Initiatives and Projects > weekly
        • IT Teams > weekly, if not daily

      Tech Team Frequency for Discussing Goals

      “When goals are talked about weekly, teams are nearly 3X more likely to feel confident hitting them.”
      – Hypercontext, 2022

      Info-Tech Insight
      Communications made once will always fail. Ensure there is a frequency appropriate for every communication — or do not expect the desired outcome.

      1.7 Establish a frequency and time frame

      30 minutes

      1. For each row in tab 3, determine how frequently that communication needs to take place and when that communication needs to be completed by.
        • Frequency: How often the communication will be delivered to the audience (e.g. one-time, monthly, as needed).
        • Time frame: When the communication will be delivered to the audience (e.g. a planned period or a specific date).
      2. When selecting the time frame, consider what dependencies need to take place prior to that communication. For example, IT employees should not be communicated with on anything that has not yet been approved by the CEO. Also consider when other communications might be taking place so the message is not lost in the noise.
      3. For frequency, the only time that a communication needs to take place once is when presenting up to senior leaders of the organization. And even then it will sometimes require more than one conversation. Be mindful of this.
      InputOutput
      • The change
      • Target audience
      • Communication outcome
      • Communication channel
      • Frequency and time frame of the communication
      MaterialsParticipants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      First, ensure feedback mechanisms are in place

      Soliciting and acting on feedback involves employees in the decision-making process and demonstrates to them that their contributions matter.

      Prior to the strategy rollout, make sure you have also established feedback mechanisms to collect feedback on both the messages delivered and how they were delivered. Some ways to collect feedback include:

      • Evaluating intranet comments and interactions (likes, etc.) if this function is enabled.
      • Measuring comprehension and satisfaction through surveys and polls.
      • Looking for themes in the feedback and questions employees bring forward to managers during in-person briefings.

      Feedback Mechanisms:

      • CIO Business Vision Survey
      • Engagement Surveys
      • Focus Groups
      • Suggestion Boxes
      • Team Meetings
      • Random Sampling
      • Informal Feedback
      • Direct Feedback
      • Audience Body Language
      • Repeating the Message Back

      Select metrics to measure progress on key results

      There are two types of metrics that can be used to measure the impact of an internal communications strategy and progress toward strategy goals. These metrics are used to measure both outputs and outcomes.

      Select metrics measuring both:
      Tactical Effectiveness (Outputs) Strategic Effectiveness (Outcomes)
      • Open rate
      • Click-through rate
      • Employee sentiment
      • Participation rates
      • Physical distractions
      • Shift in behavior
      • Manager capability to communicate
      • Organizational ability to meet goals
      • Engagement
      • Turnover

      Pyramid of metrics to measure process on key results

      1.8 Obtain feedback and improve

      20 minutes

      1. Evenly distribute the number of rows in the communication plan to all those involved. Consider a metric that would help inform whether the communication outcome was achieved.
      2. For each row, identify a feedback mechanism (slide 38) that could be used to enable the collection and confirm a successful outcome.
      3. Come back as a group and validate the feedback mechanisms selected.
      4. The important aspect here is not just to measure if the desired outcome was achieved. However, if the desired outcome is not achieved, consider what you might do to change or enable better communication to that target audience.
      5. Every communication can be better. Feedback, whether it is tactical or strategic, will help inform methods to improve future communication activities.
      InputOutput
      • Communication outcome
      • Target audience
      • Communication channel
      • A mechanism to measure communication feedback and adjust future communications when necessary.
      MaterialsParticipants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      Example of internal communications survey

      Use and modify the questions below when building an internal communications survey. Use a Likert scale to gauge responses.

      1. I am satisfied with the communications at our organization.
      2. I am kept fully informed of news and updates relevant to our organization.
      3. I receive information that is relevant to me on a regular basis.
      4. I have the information I need to do my job.
      5. I know where to go to find the information I am looking for.
      6. My manager communicates with me in-person on a regular basis.
      7. I feel I can believe the information I receive from the company.
      8. I feel heard by senior leaders and know that they have received my feedback.
      9. The content and information that I receive is interesting to me.

      Create an easy-to-read approach to communication

      Example of an easy-to-read approach to communication

      1.9 Finalize the calendar

      2 hours

      1. Once the information on tabs 2 and 3 of the Communication Planner Tool has been completed, start to organize the information in an easy-to-read view.
      2. Using the annual, monthly, and weekly calendar views on tabs 3 to 5, begin to formalize the dates of when communications will take place.
      3. Following the instructions on each tab, complete one or all of the views of the communication plan. Remember, the stakeholder that makes up the target audience needs to be considered and whether this communication will overlap with any other communications.
      InputOutput
      • Communication Plan on tab 2
      • Yearly, monthly, and weekly communication calendars
      MaterialsParticipants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      Phase 2

      Compose a Compelling Message

      Activities

      2.1 Craft a Pitch
      2.2 Revise the Pitch

      This step involves the following participants:
      Varies based on those who would be relevant to your initiative.

      Outcomes of this step
      Ability to create a clear, concise, and consistent message using best practices and a pitch framework.

      Communication Any IT Initiative Effectively

      Phase 1 > Phase 2 > Phase 3

      Include all the following pieces in your message for an effective communication

      Pieces needed in your message for effective communication

      Info-Tech Insight
      Time is a non-renewable resource. The message crafted must be considered a value-add communication to your audience.

      Enable good communication with these components

      Be Consistent Be Clear
      • The core message must be consistent regardless of audience, channel, or medium.
      • Test your communication with your team or colleagues to obtain feedback before delivering to a broader audience.
      • A lack of consistency can be interpreted as an attempt at deception. This can hurt credibility and trust.
      • Say what you mean and mean what you say.
      • Choice of language is important: “Do you think this is a good idea? I think we could really benefit from your insights and experience here.” Or do you mean: “I think we should do this. I need you to do this to make it happen.”
      • Don’t use jargon.
      Be Relevant Be Concise
      • Talk about what matters to the stakeholder.
      • Talk about what matters to the initiative.
      • Tailor the details of the message to each stakeholder’s specific concerns.
      • IT thinks in processes but stakeholders only care about results: talk in terms of results.
      • IT wants to be understood, but this does not matter to stakeholders. Think: “what’s in it for them?”
      • Communicate truthfully; do not make false promises or hide bad news.
      • Keep communication short and to the point so key messages are not lost in the noise.
      • There is a risk of diluting your key message if you include too many other details.
      • If you provide more information than necessary, the clarity and consistency of the message can be lost.

      Draft the core messages to communicate

      Draft core messages communicating information consistent with the high-level communications plan. This includes the overall goal of communications, key messaging, specifics related to the change action, and customizations for each audience. It’s also important to:

      1. Hook your audience: Use a compelling introduction that ensures your target audience cares about the message. Use a statistic or another piece of information that presents the problem in a unique way.
      2. Demonstrate you can help: Let the audience know that based on the unique problem you can help. There is value to engaging and working with you further.
      3. Repeat messages several times and through several messengers and mediums throughout the change stages to ensure all audience members receive and understand the details.
      4. Write for the ear: Use concise and clear sentences, avoid technological language, and when you speak it aloud ensure it sounds like how you would normally speak.
      5. Keep messaging positive but realistic. Avoid continually telling stakeholders that “change is hard.” Instead, communicate messages around change success to positively prime the audience’s mindset (Harvard Business Review).
      6. Communicate what is meaningfully unchanged. Not everything will be impacted by the change. To help reduce fears, include information about meaningful aspects of employees’ work that will not be changing (e.g. employees are moving to report to a new manager on a new team, but the job responsibilities are staying the same).
      7. Finish with a call to action: Your concluding statement should not be a thank-you but a call to action that ignites how your audience will behave after the communication.

      Components of a good pitch

      Key Components of a Good Pitch
      Purpose of the pitch What are you asking for? What is the desired outcome of the conversation? What three things do you want the audience to take away?
      Speak to what matters to them Who is your audience and what are their biggest challenges today? What do they care? What is the “so what”? Humanize it. Start with an example of a real person.
      Sell the improvement How is your solution going to solve that problem? Is your solution a pain killer or vitamin?
      Show real value How will your solution create real value? How can that be measured? Give an example.
      Discuss potential fears Identify and alleviate fears the stakeholder may have in working with you. Think about what they think now and what you want them to think.
      Have a call to action Identify what your ask is. What are you looking for from the stakeholder? Listen and respond.
      Follow up with a thank-you Did you ensure that the participants’ time was respected and appreciated? Be genuine and sincere.

      Key questions to answer with change communication

      To effectively communicate change, answer questions before they’re asked, whenever possible. To do this, outline at each stage of the change process what’s happening next for the audience and answer other anticipated questions. Pair key questions with core messages in change communications.

      Examples of key questions by change stage include:

      What is changing?
      When is the change expected?
      Who will be championing the change?
      What are the change expectations?
      Will I have input into how the change is happening?
      What’s happening next?
      Why are we changing?
      Why is the change happening now?
      What are the risks of not changing?
      What will be new?
      What’s in it for me?
      What training will be available?
      Who will be impacted?
      How will I be impacted?
      How will my team be impacted?
      What’s happening next?
      Who should I contact with questions or concerns?
      How will I be updated?
      How can I access more information?
      Will the previous process be available throughout the new process implementation?
      What needs to be done and what needs to stop to succeed?
      Will I be measured on this change?
      What’s happening next?
      How can I access more information?
      Will this change be added to key performance indicators?
      How did the change implementation go?
      What’s happening next?
      Before change During change After change
      Prepare for change Create change action and communication plan Implement change Sustain the change

      2.1 Craft a pitch

      20 minutes

      1. Using the set of stakeholders identified in activity 1.2, every participant takes one stakeholder.
      2. Open tab 7 of the Communication Planner Tool or use a piece of paper and create a communication message specific to that stakeholder.
      3. Select a topic from your workshop or use something you are passionate about.
      4. Consider the pitch components as a way to create your pitch. Remember to use what you have learned from the planning and composing sections of this training (in bold).
      5. Compose a three-minute pitch that you will deliver to your audience member.
      InputOutput
      • Individual ideas about what change is occurring and why.
      • A single statement that reflects the change occurring and the rationale for why the change is needed.
      MaterialsParticipants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      Communication Composition Checklist

      • Did you open the communication with a statistic or other memorable piece of information?
      • Is the topic being communicated in a compelling way that engages the target audience?
      • Are there statistics or data to support the story?
      • Are the statistics and data clear so they cannot be conveyed in any other way than their intended method?
      • Are you writing in clear and concise sentences?
      • Are you avoiding any technical jargon?
      • Is the message only focused on what needs to be said? Have you removed all unnecessary components?
      • Is the content organized in priority order? Could you adapt if the presentation time is shortened?
      • Is the way the communication is written sound like how you would speak normally? Are you writing for the ear?
      • Do you have a clear call to action that the audience will be asked to complete at the end?
      • Does your communication encourage discussion with the target audience? Is the audience a part of the solution?

      2.2 Revise the pitch

      10 minutes

      1. Review the pitch that was created in activity 2.1.
      2. Consider what could be done to make the pitch better:
        • Concise: Identify opportunities to remove unnecessary information.
        • Clear: It uses only terms or language the target audience would understand.
        • Relevant: It matters to the target audience and the problems they face.
        • Consistent: The message could be repeated across audiences.
      3. Validate that when you say the pitch out loud, it sounds like something you would say normally when communicating with other people.
      4. Make updates to the pitch and get ready to present.
      Input Output
      • Individual ideas about what change is occurring and why.
      • A single statement that reflects the change occurring and the rationale for why the change is needed.
      Materials Participants
      • Communication Planner Tool
      • Sticky notes
      • Whiteboard
      • Varies based on those who would be relevant to your initiative.

      Download the Communication Planner Tool

      Phase 3

      Deliver Messages Effectively

      Activities
      3.1 Deliver Your Pitch
      3.2 Refine and Deliver Again

      This step involves the following participants:
      Varies based on those who would be relevant to your initiative.

      Outcomes of this step
      Ability to deliver the pitch in a manner that is clear and would be understood by the specific stakeholder the pitch is intended for.

      Communicate Any IT Initiative Effectively

      Phase 1 > Phase 2 > Phase 3

      Hone presentation skills before meeting with key stakeholders

      Using voice and body

      Think about the message you are trying to convey and how your body can support that delivery. Hands, stance, and frame all have an impact on what might be conveyed.

      If you want your audience to lean in and be eager about your next point, consider using a pause or softer voice and volume.

      Be professional and confident

      State the main points of your presentation confidently. While this should be obvious, it is essential. Your audience should be able to clearly see that you believe the points you are stating.

      Present in a way that is genuine to you and your voice. Whether you have an energetic personality or a calm and composed personality, the presentation should be authentic to you.

      Connect with your audience

      Look each member of the audience in the eye at least once during your presentation. Avoid looking at the ceiling, the back wall, or the floor. Your audience should feel engaged – this is essential to keeping their attention.

      Avoid reading from your slides. If there is text on a slide, paraphrase it while maintaining eye contact.

      Info-Tech Insight
      You are responsible for the response of your audience. If they aren’t engaged, it is on you as the communicator.

      Use clear slides that avoid distracting the audience

      Which slide will be better to present?

      Sample A:

      Sample A

      Sample B:

      Sample B

      3.1 Deliver your pitch

      20 minutes

      1. Take ten minutes to think about how to deliver your pitch. Where will you emphasize words, speak louder, softer, lean in, stand tall, make eye contact, etc.?
      2. Group into pairs. One person is the speaker and the other the audience.
      3. Set a timer on your phone or watch.
      4. Speaker:
        1. Take a few seconds to center yourself and prepare to deliver your pitch.
        2. Deliver your pitch to Person 2. Don’t forget to use your body language and your voice to deliver.
      5. Audience:
        1. Repeats ideas back to Person 1. Are the ideas correct? Are you convinced?
        2. Identifies who the audience is. Are they correct?
      6. Reverse roles and repeat.
      7. Discuss and provide feedback to one another.
      InputOutput
      • Written pitch
      • Best practices for delivering
      • An ability to deliver the pitch in a clear and concise manner that could be understood by the intended stakeholder.
      • Feedback from person 2.
      MaterialsParticipants
      • Pitch framework
      • Communications Plan Tool
      • Piece of paper
      • Varies based on those who would be relevant to your initiative.

      Communication Delivery Checklist

      • Are the slides clean so the audience can focus on your speaking and not on reading the context-heavy slide?
      • Have you practiced delivering the communication to team members or coaches?
      • Have you practiced delivering the communication to someone with little to no technology background?
      • Are you making yourself open to feedback and improvement opportunities?
      • If the communication is derailed from your plan, are you prepared to handle that change?
      • Can you deliver the communication without reading your notes word for word?
      • Have you adapted your voice throughout the communication to highlight specific components you want the audience to focus on?
      • Are you presenting in a way that is genuine to you and your personality?
      • Can you communicate the message within the time allotted?
      • Are you moving in an appropriate manner based on your communication (e.g. toward the screen, across the stage, hand gestures).

      3.2 Refine and deliver again

      1 hour

      1. Go back to what you wrote as your pitch and take ten minutes to eliminate more information to get the pitch down to two minutes based on the feedback from your original partner.
      2. Repeat the last exercise where you deliver your pitch; however, deliver it to the larger group this time.
      3. Focus on ways to adjust body language and voice to make the message more compelling.
      4. Identify if your audience is telling you anything with their body language (e.g. leaning in, leaning back). Use this to adjust as you are presenting.
      5. Have the group provide additional feedback on what was effective about the message and opportunities to further improve the message.
      InputOutput
      • Three-minute pitch
      • Feedback from first delivery
      • An ability to deliver the pitch in a clear and concise manner that could be understood by the intended stakeholder.
      MaterialsParticipants
      • Pitch framework
      • Communications Plan Tool
      • Piece of paper
      • Varies based on those who would be relevant to your initiative.

      Info-Tech Insight
      Whether the CIO or a service desk technician, delivering a presentation is a fear for every role in IT. Prepare your communication to help overcome the fears that are within your control.

      Research Contributors and Experts

      Anuja Agrawal, National Communications Director, PwC

      Anuja Agrawal
      National Communications Director
      PwC

      Anuja is an accomplished global communications professional, with extensive experience in the insurance, banking, financial, and professional services industry in Asia, the US, and Canada. She is currently the National Communications Director at PwC Canada. Her prior work experience includes communication leadership roles at Deutsche Bank, GE, Aviva, and Veritas. Anuja works closely with senior business leaders and key stakeholders to deliver measurable results and effective change and culture building programs. Anuja has experience in both internal and external communications, including strategic leadership communication, employee engagement, PR and media management, digital and social media, M&A/change and crisis management. Anuja believes in leveraging digital tools and technology-enabled solutions combined with in-person engagement to help improve the quality of dialogue and increase interactive communication within the organization to help build an inclusive culture of belonging.

      Nastaran Bisheban, Chief Technology Officer, KFC Canada

      Nastaran Bisheban
      Chief Technology Officer
      KFC Canada

      A passionate technologist and seasoned transformational leader. A software engineer and computer scientist by education, a certified Project Manager that holds an MBA in Leadership with Honors and Distinction from University of Liverpool. A public speaker on various disciplines of technology and data strategy with a Harvard Business School executive leadership program training to round it all. Challenges status quo and conventional practices; is an advocate for taking calculated risk and following the principle of continuous improvement. With multiple computer software and project management publications she is a strategic mentor and board member on various non-profit organizations. Nastaran sees the world as a better place only when everyone has a seat at the table and is an active advocate for diversity and inclusion.

      Heidi Davidson, Co-founder & CEO, Galvanize Worldwide and Galvanize On Demand

      Heidi Davidson
      Co-founder & CEO
      Galvanize Worldwide and Galvanize On Demand

      Dr. Heidi Davidson is the Co-Founder and CEO of Galvanize Worldwide, the largest distributed network of marketing and communications experts in the world. She also is the Co-Founder and CEO of Galvanize On Demand, a tech platform that matches marketing and communications freelancers with client projects. Now with 167 active experts, the Galvanize team delivers startup advisory work, outsourced marketing, training, and crisis communications to organizations of all sizes. Before Galvanize, Heidi spent four years as part of the turnaround team at BlackBerry as the Chief Communications Officer and SVP of Corporate Marketing, where she helped the company move from a device manufacturer to a security software provider.

      Eli Gladstone, Co-founder, Speaker Labs

      Eli Gladstone
      Co-Founder
      Speaker Labs

      Eli is a Co-Founder of Speaker Labs. He has spent over 6 years helping countless individuals overcome their public speaking fears and communicate with clarity and confidence. When he's not coaching others on how to build and deliver the perfect presentation, you'll probably find him reading some weird books, teaching his kids how to ski or play tennis, or trying to develop a good enough jumpshot to avoid being a liability on the basketball court.

      Francisco Mahfuz, Keynote Speaker & Storytelling Coach

      Francisco Mahfuz
      Keynote Speaker & Storytelling Coach

      Francisco Mahfuz has been telling stories in front of audiences for a decade, and even became a National Champion of public speaking. Today, Francisco is a keynote speaker and storytelling coach and offers communication training to individuals and international organisations, and has worked with organisations like Pepsi, HP, the United Nations, Santander and Cornell University. He's the author of Bare: A Guide to Brutally Honest Public Speaking, the host of The Storypowers Podcast, and he’s been part of the IESE MBA communications course since 2020. He's received a BA in English Literature from Birkbeck University in London.

      Sarah Shortreed, EVP & CTO, ATCO Ltd.

      Sarah Shortreed
      EVP & CTO
      ATCO Ltd.

      Sarah Shortreed is ATCO’s Executive Vice President and Chief Technology Officer. Her responsibilities include leading ATCO’s Information Technology (IT) function as it continues to drive agility and collaboration throughout ATCO’s global businesses and expanding and enhancing its enterprise IT strategy, including establishing ATCO’s technology roadmap for the future. Ms. Shortreed's skill and expertise are drawn from her more than 30-year career that spans many industries and includes executive roles in business consulting, complex multi-stakeholder programs, operations, sales, customer relationship management and product management. She was recently the Chief Information Officer at Bruce Power and has previously worked at BlackBerry, IBM and Union Gas. She sits on the Board of Governors for the University of Western Ontario and is the current Chair of the Chief Information Officer (CIO) Committee at the Conference Board of Canada.

      Eric Silverberg, Co-Founder Speaker Labs

      Eric Silverberg
      Co-Founder
      Speaker Labs

      Eric is a Co-Founder of Speaker Labs and has helped thousands of people build their public speaking confidence and become more dynamic and engaging communicators. When he's not running workshops to help people grow in their careers, there's a good chance you'll find him with his wife and dog, drinking Diet Coke and rewatching iconic episodes of the reality TV show Survivor! He's such a die-hard fan, that you'll probably see him playing the game one day.

      Stephanie Stewart, Communications Officer & DR Coordinator, Info Security Services Simon Fraser University

      Stephanie Stewart
      Communications Officer & DR Coordinator
      Info Security Services Simon Fraser University

      Steve Strout, President, Miovision Technologies

      Steve Strout
      President
      Miovision Technologies

      Mr. Strout is a recognized and experienced technology leader with extensive experience in delivering value. He has successfully led business and technology transformations by leveraging many dozens of complex global SFDC, Oracle and/or SAP projects. He is especially adept at leading what some call “Project Rescues” – saving people’s careers where projects have gone awry; always driving "on-time and on-budget.“ Mr. Strout is the current President of Miovision Technologies and the former CEO and board member of the Americas’ SAP Users’ Group (ASUG). His wealth of practical knowledge comes from 30 years of extensive experience in many CxO and executive roles at some prestigious organizations such as Vonage, Sabre, BlackBerry, Shred-it, The Thomson Corporation (now Thomson Reuters) and Morris Communications. Served on Boards including Customer Advisory Boards of Apple, AgriSource Data, Dell, Edgewise, EMC, LogiSense, Socrates.ai, Spiro Carbon Group, and Unifi.

      Info-Tech Research Group Contributors:
      Sanchia Benedict, Research Lead
      Koula Bouloukos, Production Manager
      Antony Chan, Executive Counsellor
      Janice Clatterbuck, Executive Counsellor
      Ahmed Jowar, Research Specialist
      Dave Kish, Practice Lead
      Nick Kozlo, Senior Research Analyst
      Heather Leier Murray, Senior Research Analyst
      Amanda Mathieson, Research Director
      Carlene McCubbin, Practice Lead
      Joe Meier, Executive Counsellor
      Andy Neill, AVP, Research
      Thomas Randall, Research Director

      Plus an additional two contributors who wish to remain anonymous.

      Related Info-Tech Research

      Boardroom Presentation Review

      • You will come away with a clear, concise, and compelling board presentation that IT leaders can feel confident presenting in front of their board of directors.
      • Add improvements to your current board presentation in terms of visual appeal and logical flow to ensure it resonates with your board of directors.
      • Leverage a best-of-breed presentation template.

      Build a Better Manager

      • Management skills training is needed, but organizations are struggling to provide training that makes a long-term difference in the skills managers actually use in their day to day.
      • Many training programs are ineffective because they offer the wrong content, deliver it in a way that is not memorable, and are not aligned with the IT department’s business objectives.

      Crisis Communication Guides

      During a crisis it is important to communicate to employees through messages that convey calm and are transparent and tailored to your audience. Use the Crisis Communication Guides to:

      • Draft a communication strategy.
      • Tailor messages to your audience.
      • Draft employee crisis communications.

      Use this guide to equip leadership to communicate in times of crisis.

      Bibliography

      Gallo, Carmine. "How Great Leaders Communicate." Harvard Business Review. 23 November 2022.

      Gallup. State of the American Workplace Report. Washington, D.C.: Gallup, 6 February 2020.

      Guthrie, Georgina. “Why Good Internal Communications Matter Now More than Ever.” Nulab. 15 Dec. 2021.

      Hypercontext. “The State of High Performing Teams in Tech 2022.” Hypercontext. 2022.

      Lambden, Duncan. “The Importance of Effective Workplace Communication – Statistics for 2022.” Expert Market. 13 June 2022.

      McCreary, Gale & WikiHow. “How to Measure the Effectiveness of Communication: 14 Steps.” WikiHow.

      Nowak, Marcin. “Top 7 Communication Problems in the Workplace.” MIT Enterprise Forum CEE, 2021.

      Nunn, Philip. “Messaging That Works: A Unique Framework to Maximize Communication Success.” iabc.

      Picincu, Andra. “How to Measure Effective Communications.” Small Business Chron. 12 January 2021.

      Price. David A. “Pixar Story Rules.”

      Prosci. “Best Practices in Change Management 2020 Edition.” Prosci, 2020.

      Roberts, Dan. “How CIOs Become Visionary Communicators.” CIO, 2019.

      Schlesinger, Mark. “Why building effective communication skill in IT is incredibly important.”

      Skills Framework for the Information Age, “Mapping SFIA Levels of Responsibilities to Behavioural Factors.” Skills Framework for the Information Age, 2021.

      St. James, Halina. Talk It Out. Podium, 2005.

      TeamState. “Communication in the Workplace Statistics: Importance and Effectiveness in 2022.” TeamStage, 2022.

      Walters, Katlin. “Top 5 Ways to Measure Internal Communication.” Intranet Connections, 30 May 2019.

      Demystify Blockchain: How Can It Bring Value to Your Organization?

      • Buy Link or Shortcode: {j2store}96|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Innovation
      • Parent Category Link: /innovation
      • Most leaders have an ambiguous understanding of blockchain and its benefits, let alone how it impacts their organization.
      • At the same time, with bitcoin drawing most of the media attention, organizations are finding it difficult to translate cryptocurrency usage to business case.

      Our Advice

      Critical Insight

      • Cut through the hype associated with blockchain by focusing on what is relevant to your organization. You have been hearing about blockchain for some time now and want to better understand it. While it is complex, you can beat the learning curve by analyzing its key benefits and purpose. Features such as transparency, efficiency, and security differentiate blockchain from existing technologies and help explain why it has transformative potential.
      • Ensure your use case is actually useful by first determining whether blockchain aligns with your organization. CIOs must take a practical approach to blockchain in order to avoid wasting resources (both time and money) and hurting IT’s image in the eyes of the business. While is easy to get excited and invest in a new technology to help maintain your image as a thought leader, you must ensure that your use case is fully developed prior to doing so.

      Impact and Result

      • Follow Info-Tech’s methodology for simplifying an otherwise complex concept. By focusing on its benefits and how they directly relate to a use case, blockchain technology is made easy to understand for business and IT professionals.
      • Our program will help you understand if blockchain is the optimal solution for your organization by mapping its key benefits (i.e. transparency, integrity, efficiency, and security) to your needs and capabilities.
      • Leverage a repeatable framework for brainstorming blockchain use case ideas and communicate your findings to business stakeholders who may otherwise be confused about the transformative potential of blockchain.

      Demystify Blockchain: How Can It Bring Value to Your Organization? Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why your organization should care about determining whether blockchain aligns with your organization, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. What exactly is blockchain?

      Understand blockchain’s unique feature, benefits, and business use cases.

      • Demystify Blockchain – Phase 1: What Is Blockchain?
      • Blockchain Glossary

      2. What can blockchain do for your organization?

      Envision blockchain’s transformative potential for your organization by brainstorming and validating a use case.

      • Demystify Blockchain – Phase 2: What Can Blockchain Do for Your Organization?
      • Blockchain Alignment Tool
      • Blockchain Alignment Presentation
      [infographic]

      Embrace the Inevitability of Multicloud

      • Buy Link or Shortcode: {j2store}115|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Strategy and Organizational Design
      • Parent Category Link: /strategy-and-organizational-design

      It used to be easy: pick your cloud, build out your IT footprint, and get back to business. But the explosion of cloud adoption has also led to an explosion of options for cloud providers, platforms, and deployment options. And that’s just when talking about infrastructure as a service!

      Our Advice

      Critical Insight

      • Multicloud isn’t good or bad; it’s inevitable.
      • Embracing multicloud in your organization is an opportunity to gain control while enabling choice. Although it increases complexity for both IT operations and governance, with the right tools and principles in place you can reduce the IT burden and increase business agility at the same time.

      Impact and Result

      • Understand what multicloud is, what it isn’t, and why you need to accept it in your organization.
      • Keep your cloud strategy but adapt your approach and tools.
      • Leverage best practices and principles that will help you keep control of the volatility and complexity that comes with multicloud.

      Embrace the Inevitability of Multicloud Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Embrace the Inevitability of Multicloud Storyboard – A deck that helps you implement best practices for your multicloud strategy.

      Use this research to understand the risks and benefits that come with a multicloud posture.

      • Embrace the Inevitability of Multicloud Storyboard

      Infographic

      Further reading

      Embrace the Inevitability of Multicloud

      The heterogeneous ecosystem is worth it; you just need a cohesive strategy.

      Executive summary

      Your Challenge

      Common Obstacles

      Info-Tech’s Approach

      It used to be easy: pick your cloud, build out your IT footprint, and get back to business. But the explosion of cloud adoption has also led to an explosion of options for cloud providers, platforms, and deployment. And that’s just when talking about infrastructure as a service!

      For many businesses, one of the key benefits of the cloud ecosystem is enabling choice for different users, groups, and projects in the organization. But this means embracing multiple cloud platforms. Is it worth it?

      The reality is that multicloud is inevitable for most organizations, and if it’s not yet a reality for your IT team, it soon will be. This brings new challenges:

      1. How do I decide what platforms and offerings to use where? Is my old cloud strategy obsolete?
      2. How do I identify what I want out of multicloud, and what tools and best practices need to be in place to keep control?

      By defining your end goals, framing solutions based on the type of visibility and features your multicloud footprint needs to deliver, you can enable choice and improve performance, flexibility, and availability.

      1. Understand what multicloud is, what it isn’t, and why you need to accept it in your organization.
      2. Keep your cloud strategy but adapt your approach and tools.
      3. Leverage best practices and principles that will help you keep control of the volatility and complexity that comes with multicloud.

      Info-Tech Insight

      Embracing multicloud in your organization is an opportunity to gain control while enabling choice. Although it increases complexity for both IT operations and governance, with the right tools and principles in place you can reduce the IT burden and increase business agility at the same time.

      Project overview

      Multicloud isn’t good or bad; it’s inevitable

      The reality is multicloud is usually not a choice. For most organizations, the requirement to integrate with partners, subsidiaries, and parent organizations, as well as the need to access key applications in the software-as-a-service ecosystem, means that going multicloud is a matter of when, not if.

      The real question most businesses should ask is not whether to go multicloud, but rather how to land in multicloud with intent and use it to their best advantage.

      Your workloads will guide the way

      One piece of good news is that multicloud doesn’t change the basic principles of a good cloud strategy. In fact, a well-laid-out multicloud approach can make it even easier to put the right workloads in the right place – and then even move them around as needed.

      This flexibility isn’t entirely free, though. It’s important to know how and when to apply this type of portability and balance its benefits against the cost and complexity that come with it.

      Don’t fall in reactively; land on your feet

      Despite the risks that come with the increased scale and complexity of multicloud, it is possible to maintain control, realize the benefits, and even use multicloud as a springboard for leveraging cloud benefits in your business. By adopting best practices and forethought in key areas of multicloud risk, you can hit the ground running.

      Aligning the terms

      Modern organizations have multiple IT footprints. How do we classify different stances?

      01 Hybrid Cloud
      Private cloud and public cloud infrastructure managed as one entity

      02 Multicloud
      Includes multiple distinct public cloud services, or “footprints”

      03 Hybrid IT
      Putting the right workloads in the right places with an overall management framework

      Info-Tech Insight

      • Hybrid cloud is about applying the same service model across multiple deployment models (most commonly public and private clouds).
      • Multicloud is about using multiple cloud offerings irrespective of differences in service model or deployment model.

      Multicloud

      • An approach that includes multiple distinct public cloud services (e.g. AWS EC2 but also Salesforce and M365)
      • Usually defined around a steady state for each workload and footprint
      • Everything in its right place (with portability for events and disasters)
      • NOT everything everywhere all at once
      The image contains the Info-Tech thought model for multicloud.

      Multicloud is inevitable

      The SaaS ecosystem has led organizations to encourage business units to exercise the IT choices that are best for them.

      The multicloud maturity journey

      1. Move a workload to the cloud
      2. Move more workloads to the same cloud
      3. Move the right workloads to the right clouds
      4. Hybrid cloud & multicloud
      5. Integrate cloud and traditional/ on-premises footprints

      Hybrid IT: Aggregate Management, Monitoring, Optimization, Continuous Improvement

      Multicloud is about enabling choice while maintaining oversight

      The broader your footprint, the harder it becomes to manage risks across each environment.

      The image contains a screenshot of a diagram of maintaining oversight with multicloud.

      Managing multicloud risks

      The risks in multicloud are the same as in traditional cloud but amplified by the differences across footprints and providers in your ecosystem.

      • Variations across platforms include:
        • Rules
        • Security
        • Mapping corresponding products and services
      • Training and certifications by platform/provider
      • Managing cost across footprints
      • Complexity of integration
      • Managing compliance across platforms
      • Loss of standardization due to multicloud fragmentation

      Info-Tech Insight

      Don’t be afraid to ask for help! Each cloud platform you adopt in your multicloud posture requires training, knowledge, and execution. If you’re already leveraging an ecosystem of cloud providers, leverage the ecosystem of cloud enablers as needed to help you on your way.

      Despite the risks, multicloud is a springboard

      Increasing flexibility & accelerating integration

      Because multicloud increases the number of platforms and environments available to us, we can
      use it as a way to increase our agility (from both a DevOps and a resource deployment perspective) as well as to provide an answer to the problem of vendor lock-in.

      Multicloud also can be a catalyst for integrating and stitching together resources and services that were previously isolated from each other. Because of the modular design and API architecture prevalent in cloud services, they can be easily consumed and integrated from your various footprints.

      Modernizing data strategy

      While it may seem counterintuitive, a proactive multicloud approach will allow you to regain visibility and control of your entire data ecosystem. Defining your data architecture and policies with an eye to the inevitability of multicloud means you can go beyond just regaining control of data stranded in SaaS and other platforms; you can start to really understand the flows of data and how they affect your business processes for better or worse.

      Move to cloud-native IT & design

      Embracing multicloud is also a great opportunity to embrace the refactoring and digital transformation you’ve been blocked on. Instead of treading water with respect to keeping control of fragmented applications, services, and workloads, a proactive approach to multicloud allows you to embrace open standards built to deliver cloud-native power and portability and to build automations that increase reliability, performance, and cost effectiveness while reducing your total in-house work burden.

      Info-Tech Insight

      Don’t bite off more than you can chew! Especially with IaaS and PaaS services, it’s important to ensure you have the skills and bandwidth to manage and deploy services effectively. It’s better to start with one IaaS platform, master it, and then expand.

      Let your workloads guide the way

      Multicloud is a road to best-of-breed everything


      A screenshot of multiclouds.

      Stick with a workload-level approach

      The principles of cloud strategy don’t change with multicloud! The image contains a screenshot of a workload-level approach.
      If anything, a multicloud approach increases your ability to put the right workloads in the right places, wherever that may be.
      It can also (with some work and tooling) provide even broader options for portability and resilience.

      Multicloud = multiple right places

      Put everything in its right place.

      Just like with any cloud strategy, start with a workload-level approach and figure out the right migration path and landing point for your workload in cloud.

      Understand the other right places!

      Multicloud means for many workloads, especially IaaS- and PaaS-focused ones, you will have multiple footprints you can use for secondary locations as desired for portability, resilience, and high availability (with the right tooling and design).

      Info-Tech Insight

      Portability is always a matter of balancing increased flexibility, availability, and resilience against increased complexity, maintenance effort, and cost. Make sure to understand the requirement for your workloads and apply portability efforts where they make the most sense

      Your management will need to evolve

      Don’t manage multicloud with off-the-rack tools.

      The default dashboards and management tools from most cloud vendors are a great starting point when managing a single cloud. Unfortunately, most of these tools do not extend well to other platforms, which can lead to multiple dashboards for multiple footprints.

      These ultimately lead to an inability to view your multicloud portfolio in aggregate and fragmentation of metrics and management practices across your various platforms. In such a situation maintaining compliance and control of IT can become difficult, if not impossible!

      Unified standards and tools that work across your entire cloud portfolio will help keep you on track, and the best way to realize these is by applying repeatable, open standards across your various environments and usually adopting new software and tools from the ecosystem of multicloud management software platforms available in the market.

      Info-Tech Insight

      Even in multicloud, don’t forget that the raw data available from the vendor’s default dashboards is a critical source of information for optimizing performance, efficiency, and costs.

      Multicloud management tool selection

      The ecosystem is heterogeneous.

      The explosion of cloud platforms and stacks means no single multicloud management tool can provide support for every stack in the private and public cloud ecosystem. This challenge becomes even greater when moving from IaaS/PaaS to addressing the near-infinite number of offerings available in the SaaS market.

      When it comes to selecting the right multicloud management tool, it’s important to keep a few things in mind:

      1. Mapping your requirements to the feature sets for your multicloud management platform is critical.
      2. Depending on your goals and metrics, and the underlying platforms and data you need to collect from them, you may need more than one tool.
      3. Especially when it comes to integrating SaaS into your multicloud tool(s), development or partners may be required.

      Key Features

      • Portability
      • Cost management
      • Automation across vendors
      • Standardization of configuration
      • Security alignment across vendors
      • Unified provisioning and self-service

      Info-Tech Insight

      SaaS always presents a unique challenge for gathering necessary cloud management data. It’s important to understand what data is and isn’t available and how it can be accessed and made available to your multicloud management tools.

      Understand your vendors

      Define what you are looking for as a first step.

      • To best understand your options, you need to understand the focus, features, and support services for each vendor. Depending on your requirements, you may need to adopt more than one tool.
      • Remember that SaaS presents unique challenges in terms of accessing and ingesting data into your management tools. This will generally require development to leverage the provider’s API.
      • Within the following slides, you will find a defined activity with a working template that will create a vendor profile for each vendor.

      As a working example, you can review these vendors on the following slides:

      • VMware CloudHealth
      • ServiceNow ITOM
      • CloudCheckr

      Info-Tech Insight

      Creating vendor profiles will help quickly identify the management tools that meet your multicloud needs.

      Vendor Profile #1

      VMware CloudHealth

      Vendor Summary

      CloudHealth is a VMware management suite that provides visibility into VMware-based as well as public cloud platforms. CloudHealth focuses on providing visibility to costs and governance as well as applying automation and standardization of configuration and performance across cloud platforms.

      URL: cloudhealth.vmware.com

      Supported Platforms

      Supports AWS, Azure, GCP, OCI, VMware

      Feature Sets

      • Portability
      • Cost management
      • Automation across platforms
      • Standardization of configuration
      • Security alignment across platforms
      • Unified provisioning and self-service

      Vendor Profile #2

      ServiceNow ITOM

      Vendor Summary

      ServiceNow IT Operations Management (ITOM) is a module for the ServiceNow platform that allows deep visibility and automated intervention/remediation for resources across multiple public and private cloud platforms. In addition to providing a platform for managing workload portability and costs across multiple cloud platforms, ServiceNow ITOM offers features focused on delivering “proactive digital operations with AIOps.”

      URL: servicenow.com/products/it-operations-management.html

      Supported Platforms

      Supports CloudFormation, ARM, GDM, and Terraform templates. Also provisions virtualized VMware environments.

      Feature Sets

      • Portability
      • Cost management
      • Automation across platforms
      • Standardization of configuration
      • Security alignment across platforms
      • Unified provisioning and self-service

      Vendor Profile #3

      CloudCheckr

      Vendor Summary

      CloudCheckr is a SaaS platform that provides end-to-end cloud management to control cost, ensure security, optimize resources, and enable services. Primarily focused on enabling management of public cloud services, CloudCheckr’s broad platform support and APIs can be used to deliver unified visibility across many multicloud postures.

      URL: cloudcheckr.com

      Supported Platforms

      Supports AWS, Azure, GCP, SAP Hana

      Feature Sets

      • Portability
      • Cost management
      • Automation across platforms
      • Standardization of configuration
      • Security alignment across platforms
      • Unified provisioning and self-service

      Activity

      Understand your vendor options

      This activity involves the following participants:

      • IT strategic direction decision makers
      • Cloud governance team
      • Cloud deployment team
      • Vendor and portfolio management

      Outcomes of this step:

      • Vendor profile template (ppt)

      Info-Tech Insight

      This checkpoint process creates transparency around agreement costs with the business and gives the business an opportunity to reevaluate its requirements for a potentially leaner agreement.

      Create your vendor profiles

      Define what you are looking for and score vendors accordingly.

      1. Create a vendor profile for every vendor of interest.
      2. Leverage our starting list and template to track and record the advantages of each vendor.

      Vendor Profile Template

      The image contains a screenshot of a Vendor Profile Template.

      Land on your feet

      Best practices to hit the ground running in multicloud

      Focus your multicloud posture on SaaS (to start)

      SaaS

      While every service model and deployment model has its place in multicloud, depending on the requirements of the workload and the business, most organizations end up in multicloud because of the wide ecosystem of options available at the SaaS level.

      Enabling the ability to adopt SaaS offerings into your multicloud footprint should be an area of focus for most IT organizations, as it’s the easiest way to deliver business impact (without taking on additional infrastructure work).

      IaaS and PaaS

      Although IaaS and PaaS also have their place in multicloud, the benefits are usually focused more on increased portability and availability rather than on enabling business-led IT.

      Additionally, multicloud at these levels can often be complex and/or costly to implement and maintain. Make sure you understand the cost-benefit for implementing multicloud at this level!

      Where the data sits matters

      With multiple SaaS workloads as well as IaaS and PaaS footprints, one of the biggest challenges to effective multicloud is understanding where any given data is, what needs access to it, and how to stitch it all together.

      In short, you need a strategy to understand how to collect and consolidate data from your multiple footprints.

      Relying solely on the built-in tools and dashboards provided by each provider inevitably leads to data fragmentation – disparate data sets that make it difficult to gain clear, unified visibility into your cloud’s data.

      To address the challenge of fragmented data, many organizations will require a multicloud-capable management platform that can provide access and visibility to data from all sources in a unified way.

      Weigh portability against nativeness

      When it comes to multicloud, cloud-native design is both your enemy and your friend. On one hand, it provides the ability to fully leverage the power and flexibility of your chosen platform to run your workload in the most on-demand, performance-efficient, utility-optimized way possible.

      But it’s important to remember that building cloud-native for one platform directly conflicts with that workload’s portability to other platforms! You need to understand the balance between portability and native effectiveness that works best for each of your workloads.

      Info-Tech Insight

      You can (sort of) have the best of both worlds! While the decision to focus on the cloud-native products, services, and functions from a given cloud platform must be weighed carefully, it’s still a good idea to leverage open standards and architectures for your workloads, as those won’t hamper your portability in the same way.

      Broaden your cost management approach

      Even on singular platforms, cloud cost management is no easy task. In multicloud, this is amplified by the increased scale and scope of providers, products, rates, and units of measure.

      There is no easy solution to this – ultimately the same accountabilities and tasks that apply to good cost management on one cloud also apply to multicloud, just at greater scale and impact.

      The image contains a screenshot of cost management approach.

      Info-Tech Insight

      Evolving your tooling applies to cost management too. While the vendor-provided tools and dashboards for cost control on any given cloud provider’s platform are a good start and a critical source for data, to get a proper holistic view you will usually require multicloud cost management software (and possibly some development work).

      Think about the sky between the clouds

      A key theme in cloud service pricing is “it’s free to come in, but it costs to leave.” This is a critical consideration when designing the inflows and outflows of data, interactions, transactions, and resources among workloads sitting on different platforms and different regions or footprints.

      When defining your multicloud posture, think about what needs to flow between your various clouds and make sure to understand how these flows will affect costs, performance, and throughput of your workloads and the business processes they support.

      • Integration and Interfaces
      • Business Process and Application Flows
      • Inter-cloud Transit Costs

      Mature your management technology

      Automation Is Your Friend

      Managing multicloud is a lot of work. It makes sense to eliminate the most burdensome and error-prone tasks. Automating these tasks also increases the ease and speed of workload portability in most cases.

      Automation and scheduling are also key enablers of standardization – which is critical to managing costs and other risks in multicloud. Create policies that manage and optimize costs, resource utilization, and asset configuration. Use these to reduce the management burden and risk profile.

      Evolve Your Tooling

      Effective multicloud management requires a clear picture of your entire cloud ecosystem across all footprints. This generally isn’t possible using the default tools for any given cloud vendor. Fortunately, there is a wide ecosystem of multicloud tools to help provide you with a unified view.

      The best cloud management tools will not only allow you to get a unified view of your IT operations regardless of where the resources lie but also help you to evaluate your multiple cloud environments in a unified way, providing a level playing field to compare and identify opportunities for improvement.

      Info-Tech Insight

      Embrace openness! Leveraging open standards and technologies doesn’t just ease portability in multicloud; it also helps rationalize telemetry and metrics across platforms, making it easier to achieve a unified management view.

      Multicloud security

      Multicloud security challenges remain focused around managing user and role complexity

      • Fragmentation of identity and access management
      • Controlling access across platforms
      • Increased complexity of roles
      • API security
      • Managing different user types and subscriptions across different service models
      • Managing security best practices across multiple platforms
      • Potential increased attack surface

      Info-Tech Insight

      Don’t reinvent the wheel! Where possible, leverage your existing identity and access management platforms and role-based access control (RBAC) discipline and extend them out to your cloud footprints.

      Don’t fall in reactively!

      1. Multicloud isn’t bad or good.
      2. Put everything the right place; understand the other right places.
      3. Know where your data goes.
      4. Automation is your friend.
      5. Strategy fundamentals don’t change.
      6. Focus on SaaS (to start).
      7. Embrace openness.
      8. Modernize your tools.

      Related Info-Tech Research

      Define Your Cloud Vision
      This blueprint covers a workload-level approach to determining cloud migration paths

      10 Secrets for Successful Disaster Recovery in the Cloud
      This research set covers general cloud best practices for implement DR and resilience in the cloud.

      Bibliography

      “7 Best Practices for Multi-Cloud Management.” vmware.com, 29 April 2022. Web.
      Brown, Chalmers. “Six Best Practices For Multi-Cloud Management.” Forbes, 22 Jan. 2019. Web.
      Curless, Tim. “The Risks of Multi-Cloud Outweigh the Benefits.” AHEAD, n.d. Web.
      Tucker, Ryan. “Multicloud Security: Challenges and Solutions.” Megaport, 29 Sept 2022. Web.
      Velimirovic, Andreja. “How to Implement a Multi Cloud Strategy.” pheonixNAP, 23 June 2021. Web.
      “What is a Multi-Cloud Strategy?” vmware.com, n.d. Web.

      IT Talent Trends 2022

      • Buy Link or Shortcode: {j2store}541|cart{/j2store}
      • member rating overall impact: 8.0/10 Overall Impact
      • member rating average dollars saved: After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.
      • member rating average days saved: Read what our members are saying
      • Parent Category Name: People & Leadership
      • Parent Category Link: /people-and-leadership

      Business and IT leaders aiming to build and keep successful teams in 2022 must:

      • Optimize IT in the face of a competitive labor market.
      • Build or maintain a culture of diversity, equity, and inclusion.
      • Manage the monumental shift to the new normal of remote work.
      • Weather the Great Resignation and come out on top.
      • Correctly assess development areas for their teams.
      • Justify investing in IT talent.

      Our Advice

      Critical Insight

      • If 2021 was about beginning to act on employee needs, 2022 will be about strategically examining each trend to ensure that the organization's promises to take action are more than lip service.
      • Employees have always been able to see through disingenuous attempts to engage them, but in 2022 the stakes are higher due to increased talent mobility.

      Impact and Result

      This report includes:

      • A concise, executive-ready trend report.
      • Data and insights from IT organizations from around the world.
      • Steps to take for each of the trends depending on your current maturity level.
      • Examples and case studies.
      • Links to in-depth Info-Tech research and tools.

      IT Talent Trends 2022 Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. IT Talent Trends Report for 2022 – A report to help you incorporate new ways of working into your business to build and keep the best team.

      Discover Info-Tech’s 2022 talent trends for IT leaders, which will provide insight into taking a strategic approach to navigate the post-pandemic IT talent landscape.

      • IT Talent Trends Report for 2022

      Infographic

      Further reading

      IT Talent Trends 2022

      The last two years have been a great experiment … but it’s not over yet.

      Incorporate new ways of working into your business to build and keep the best team.

      Over the past two years, organizations have ventured into unprecedented ways of working and supporting their employees, as they tried to maintain productivity through the pandemic. This experiment has made lasting changes to both business models and employee expectations, and these effects will continue to be seen long after we return to a “new normal.”

      While the pandemic forced us to work differently for the past two years, looking forward, successful organizations will incorporate new ways of working into their business models – beyond simply having a remote work policy.

      How we work, source roles, and develop talent continue to evolve as we navigate a different world with employees being more vocal in their desires, and leaders continue to play a key role.

      The IT talent market will never be the same, and organizations must reevaluate their employee experience from the bottom up to successfully weather the shift to the new normal.

      IT Talent Trends 2022

      Strategic Recruiting Finds Good Talent

      Finding talent in a strained talent market requires a marketing approach. Posting a job description isn’t enough.

      The (Not So) Great Resignation

      IT is faring better than other functions; however, specific industries need to pay attention.

      Grow Your DEI Practices Into Meaningful Actions

      Good intentions are not enough.

      Remote Work Is Here – Can Your Culture Adapt?

      The Great Experiment is over. Are leaders equipped to capitalize on its promises?

      Management Skills Drive Success in a Remote World

      Despite the need for remote team management training, it is still not happening.

      The pandemic has clarified employees’ needs and amplified their voices

      If 2021 was about beginning to act on employee needs, 2022 will be about strategically examining each trend to ensure that the actions taken by the organization are more than lip service.

      Employees have always been able to see through disingenuous attempts to engage them, but in 2022 the stakes are higher due to increased talent mobility.

      Trends that were just starting to come into focus last year have established themselves as critical determinants of the employee experience in 2022.

      2021

      DEI: A Top Talent ObjectiveRemote Work Is Here to StayUncertainty Unlocks PerformanceA Shift in Skills PrioritiesA Greater Emphasis on Wellbeing
      Arrow pointing down.Joiner pointing down.Joiner pointing down.

      2022

      Strategic Recruiting Finds Good Talent

      Finding talent in a strained talent market requires a marketing approach. Posting a job description isn’t enough.

      The (Not So) Great Resignation

      IT is faring better than other functions; however, specific industries need to pay attention.

      Grow Your DEI Practices Into Meaningful Actions

      Good intentions are not enough.

      Remote Work Is Here – Can Your Culture Adapt?

      The Great Experiment is over. Are leaders equipped to capitalize on its promises?

      Management Skills Drive Success in a Remote World

      Despite the need for remote team management training, it is still not happening.

      What employees are looking for is changing

      Superficial elements of traditional office culture were stripped away by the quick shift to a remote environment, giving employees the opportunity to reevaluate what truly matters to them in a job.

      The biggest change from 2019 (pre-pandemic) to today is increases in the importance of culture, flexible/remote work, and work-life balance.

      Organizations that fail to keep up with this shift in priorities will see the greatest difficulty in hiring and retaining staff.

      As an employee, which of the following would be important to you when considering a potential employer?

      2019 2021
      Flexible Work Pie graph representing response percentages from employees regarding importance of these factors. Flexible Work: 2019, Very 46%, Somewhat 49%, Not at All 5%.
      n=275
      Arrow pointing right. Pie graph representing response percentages from employees regarding importance of these factors. Flexible Work: 2021, Very 76%, Somewhat 21%, Not at All 2%.
      n=206
      Work-Life Balance Pie graph representing response percentages from employees regarding importance of these factors. Work-Life Balance: 2019, Very 67%, Somewhat 30%, Not at All 3%.
      n=277
      Arrow pointing right. Pie graph representing response percentages from employees regarding importance of these factors. Work-Life Balance: 2021, Very 80%, Somewhat 18%, Not at All 1%.
      n=206
      Culture Pie graph representing response percentages from employees regarding importance of these factors. Culture: 2019, Very 68%, Somewhat 31%, Not at All 1%.
      n=277
      Arrow pointing right. Pie graph representing response percentages from employees regarding importance of these factors. Culture: 2021, Very 81%, Somewhat 19%, Not at All 0%.
      n=206
      Source: Info-Tech Talent Trends Survey data collected in 2019 and 2021 Purple Very Important
      Blue Somewhat Important
      Green Not at All Important

      IT’s top talent priorities in 2022

      IT’s top Talent priorities reflect a post-pandemic focus on optimizing talent to fulfill strategic objectives: Top challenges for IT departments, by average rank, with 1 being the top priority.

      Important

      In the 2022 IT Talent Trends Survey, IT departments’ top priorities continue to be learning and innovation in support of organizational objectives. —› Enabling leaning and development within IT
      —› Enabling departmental innovation
      5.01
      5.54
      With employees being clearer and more vocal about their needs than ever before, employee experience has risen to the forefront of IT’s concern as a key enabler of strategic objectives. —› Providing a great employee experience for IT 5.66
      Supporting departmental change 6.01
      With organizations finally on the way to financial stability post pandemic, recruiting is a major focus. —› Recruiting (e.g. quickly filling vacant roles in IT with quality external talent) 6.18
      However, IT’s key efforts are threatened by critical omissions: Fostering a positive employee relations climate in the department 6.32
      Despite a focus on learning and development, leadership skills are not yet a top focus. —› Developing the organization's IT leaders 6.33
      Rapidly moving internal IT employees to staff strategic priorities 6.96
      Facilitating data-driven people decisions within IT 7.12
      Controlling departmental labor costs and maximizing the value of the labor spend 7.13
      Despite the need to provide a great employee experience, the focus on diversity, equity, and inclusion is low. —› Fostering an environment of diversity, equity, and inclusion in the department 7.31
      Despite prioritizing recruiting, IT departments see candidate experience as a last priority, either not focusing on it or relegating it to HR. —› Providing a great candidate experience for IT candidates 8.43
      (n=227)

      IT Talent Trends 2022

      Look beneath the surface of the trends to navigate them successfully

      Above Ground
      Focusing on what you see 'Above the line" won't solve the problem.

      Talent isn't a checklist.

      Strategic Recruiting Finds Good Talent

      Finding talent in a strained talent market requires a marketing approach. Posting a job description isn't enough.
      • The number of job openings increased to 11.4 million on the last business day of October, up from 10.6 million in September (US Bureau of Labor Statistics, Dec. 2021)

      The (Not So) Great Resignation

      IT is faring better than other functions; however, specific industries need to pay attention.
      • In September, in the US, 4.4 million people left their jobs. That number dropped to 4.2 million in October. (US Labor Stats, Dec. 2021)
      • 30% of workers will likely switch jobs if they have to return to the office full time. (McKinsey, Dec. 2021)

      Grow Your DEI Practices Into Meaningful Actions

      Good intentions are not enough.
      • 95% of organizations are focusing on DEI. (2022 HR Trends Report)
      • 48% of IT departments have delivered training on DEI over the past year.

      Remote Work is Here. Can Your Culture Adapt?

      The Great Experiment is over. Are you equipped to capitalize on its promises?
      • 85% of organizations saw the same or higher productivity during the pandemic.
      • 91% of organizations are continuing remote work.

      Management Skills Drive Success in a Remote World

      Despite the need for remote team management training, it is still not happening.
      • 72% of IT departments report high effectiveness at managing remote staff.
      • Learning and development is IT's top priority.
      Cross-section of the Earth and various plants with their root systems, highlighting the world above ground and below.
      Beneath the Surface
      For each trend, a strategic approach to get "under the line" will help form your response.

      Talent needs a holistic approach, as under the line everything is connected. If you are experiencing challenges in one area, analyzing data (e.g. engagement, exit surveys, effectiveness of DEI program and leader training) can help drive overall experience.

      • 100% of job seekers cite culture as somewhat to very important.
      • Only 40% of employers advertise culture in job postings.
      • 70% of IT departments state voluntary turnover is less than 10%
      • Top reasons for resignation are salary, development, and opportunity for innovative work.
      • Resignation rates were higher in fields that had experienced extreme stress due to the pandemic (HBR, Dec. 2021)
      • Senior leadership is overestimating their own commitment to DEI.
      • Most IT departments are not driving their own DEI initiatives.
      • Without effectively measuring DEI practices, organizations will see 1.6x more turnover. (2022 HR Trends Report)
      • Senior leadership is not open to remote work in 23% of organizations.
      • Without leadership support, employees will not buy into remote work initiatives.
      • A remote work policy will not bring organizational benefits without employee buy-in.
      • 75% of senior managers believe remote team management is highly effective, but only 60% of frontline staff agree.
      • Training focuses on technical skills, to the exclusion of soft skills, including management and leadership.
      Solutions
      Recommendations depending on your department's maturity level.
      Attention is required for candidate experience underpinned by a realistic employee value proposition. Gather and review existing data (e.g. early retirements, demographics) to understand your turnover rate. Use employee engagement tools to gauge employee sentiment among impacted groups and build out an engagement strategy to meet those needs. Conduct a cultural assessment to reveal hidden biases that may stand in the way of remote work efficacy. Provide management training on performance management and development coaching.

      Logo for Info-Tech.Logo for ITRG.

      This report is based on organizations just like yours

      Survey timeline = October 2021
      Total respondents = 245 IT professionals

      Geospatial map of survey responses shaded in accordance with the percentages listed below.
      01 United States 45% 08 Middle East 2%
      02 Canada 23% 09 Other (Asia) 2%
      03 Africa 8% 10 Germany 1%
      04 Great Britain 6% 11 India 1%
      05 Latin America, South America or Caribbean 4% 12 Netherlands 1%
      06 Other (Europe) 4% 13 New Zealand 1%
      07 Australia 2% (N-245)

      A bar chart titled 'Please estimate your organization's revenue in US$ (Use operating budget if you are a public-sector organization)' measuring survey responses. '$0 - less than 1M, 7%', '$1M - less than 5M, 4%', '$5M - less than 10M, 4%', '$10M - less than 25M, 6%', '$25M - less than 50M, 5%', '$50M - less than 100M, 13%', '$100M - less than 500M, 24%', '$500M - less than 1B, 9%', '1B - less than 5B, 22%', '$5B+, 8%'. (n=191)

      This report is based on organizations just like yours

      Industry

      Bar chart measuring percentage of survey respondents by industry. The largest percentages are from 'Government', 'Manufacturing', 'Media, information, Telecom & Technology', and 'Financial Services (including banking & insurance)'.

      Info-Tech IT Maturity Model

      Stacked bar chart measuring percentage of survey respondents by IT maturity level. Innovator is 7.11%, Business Partner is 16.44%, Trusted Operator is 24.89%, Firefighter is 39.11%, and Unstable is 12.44%.
      (n=225)

      Innovator – Transforms the Business
      Reliable Technology Innovation

      Business Partner – Expands the Business
      Effective Execution Projects, Strategic Use of Analytics and Customer Technology

      Trusted Operator – Optimizes Business
      Effective Fulfillment of Work Orders, Functional Business Applications, and Reliable Data Quality

      Firefighter – Supports the Business
      Reliable Infrastructure and IT Service Desk

      Unstable – Struggles to Support
      Inability to Provide Reliable Business Services

      This report is based on people just like you

      Which of the following ethnicities (ethnicity refers to a group with a shared or common identity, culture, and/or language) do you identify with? Select all that apply. What gender do you identify most with?
      A pie chart measuring percentage of survey respondents by ethnicity. Answers are 'White (e.g. European, North America), 59%', 'Asian (e.g. Japan, India, Philippines, Uzbekistan), 12%', 'Black (e.g. Africa, Caribbean, North America), 12%', 'Latin/Hispanic (e.g. Cuba, Guatemala, Spain, Brazil), 7%', 'Middle Eastern (e.g. Lebanon, Libya, Iran), 4%', 'Indigenous (e.g. First Nations, Inuit, Metis, Maori), 3%', 'Indo-Caribbean (e.g. Trinidad & Tobago, Guyana, St. Vincent), 3%'.
      (N=245)
      A pie chart measuring percentage of survey respondents by gender. Answers are 'Male, 67%', 'Female, 24%', 'Prefer not to answer, 5%', 'No Specification, 4%', 'Intersex, 0%'.
      (n=228)

      This report is based on people just like you

      What is your sub-department of IT? Which title best describes your position?
      Bar chart measuring percentage of survey respondents by sub-department. The top three answers are 'Senior Leadership', 'Infrastructure and Operations', and 'Application Development'.
      (n=227)
      Bar chart measuring percentage of survey respondents by title. The top four answers are 'Director-level, 29%', 'Manager, 22%', 'C-Level Officer, 18%', and 'VP-level, 11%.'
      (N=245)

      IT Talent Trends 2022

      Each trend is introduced with key questions you can ask yourself to see how your department fares in that area.

      The report is based on statistics from a survey of 245 of your peers.

      It includes recommendations of next steps and a key metric to track your success.

      It lists Info-Tech resources that you, as a member, can leverage to begin your journey to improve talent management in your department.

      Strategic Recruiting Finds Good Talent

      Finding talent in a strained talent market requires a marketing approach. Posting a job description isn’t enough.

      The (Not So) Great Resignation

      IT is faring better than other functions; however, specific industries need to pay attention.

      Grow Your DEI Practices Into Meaningful Actions

      Good intentions are not enough.

      Remote Work Is Here – Can Your Culture Adapt?

      The Great Experiment is over. Are leaders equipped to capitalize on its promises?

      Management Skills Drive Success in a Remote World

      Despite the need for remote team management training, it is still not happening.

      The report is based on data gathered from Info-Tech Research Group’s 2022 IT Talent Trends Survey. The data was gathered in September and October of 2021.

      Strategic Recruiting Finds Good Talent

      Trend 1 | The Battle to Find and Keep Talent

      As the economy has stabilized, more jobs have become available, creating a job seeker’s market. This is a clear sign of confidence in the economy, however fragile, as new waves of the pandemic continue.

      Info-Tech Point of View

      Recruiting tactics are an outcome of a well-defined candidate experience and employee value proposition.

      Introduction

      Cross-section of a plant and its roots, above and below ground. During our interviews, members that focused on sharing their culture with a strong employee value proposition were more likely to be successful in hiring their first-choice candidates.
      Questions to ask yourself
      • Do you have a well-articulated employee value proposition?
      • Are you using your job postings to market your company culture?
      • Have you explored multiple channels for posting jobs to increase your talent pool of candidates?

      47% of respondents are hiring external talent to fill existing gaps, with 40% using external training programs to upgrade current employees. (Info-Tech IT Talent Trends 2022 Survey)

      In October, the available jobs (in the USA) unexpectedly rose to 11 million, higher than the 10.4 million experts predicted. (CNN Business, 2021)

      Where has all the talent gone?

      IT faces multiple challenges when recruiting for specialized talent

      Talent scarcity is focused in areas with specialized skill sets such as security and architecture that are dynamic and evolving faster than other skill sets.

      “It depends on what field you work in,” said ADP chief economist Nela Richardson. “There were labor shortages in those fields pre-pandemic and two years forward, there is even more demand for people with those skills” (CNBC, 19 Nov. 2021).

      37% of IT departments are outsourcing roles to fill internal skill shortages. (Info-Tech Talent Trends 2022 Survey)

      Roles Difficult to Fill

      Horizontal bar chart measuring percentage of survey responses about which roles are most difficult to fill. In order from most difficult to least they are 'Security (n=177)', 'Enterprise Architecture (n=172)', 'Senior Leadership (n=169)', 'Data & Business Intelligence (n=171)', 'Applications Development (n=177)', 'Infrastructure & Operations (n=181)', 'Business Relationship Management (n=149)', 'Project Management (n=175)', 'Vendor Management (n=133)', 'Service Desk (n=184)'.(Info-Tech Talent Trends 2022 Survey)

      Case Study: Using culture to drive your talent pool

      This case study is happening in real time. Please check back to learn more as Goddard continues to recruit for the position.

      Recruiting at NASA

      Goddard Space Center is the largest of NASA’s space centers with approximately 11,000 employees. It is currently recruiting for a senior technical role for commercial launches. The position requires consulting and working with external partners and vendors.

      NASA is a highly desirable employer due to its strong culture of inclusivity, belonging, teamwork, learning, and growth. Its culture is anchored by a compelling vision, “For the betterment of Humankind,” and amplified by a strong leadership team that actively lives their mission and vision daily.

      Firsthand lists NASA as #1 on the 50 most prestigious internships for 2022.

      Rural location and no flexible work options add to the complexity of recruiting

      The position is in a rural area of Eastern Shore Virginia with a population of approximately 60,000 people, which translates to a small pool of candidates. Any hire from outside the area will be expected to relocate as the senior technician must be onsite to support launches twice a month. Financial relocation support is not offered and the position is a two-year assignment with the option of extension that could eventually become permanent.

      Photo of Steve Thornton, Acting Division Chief, Solutions Division, Goddard Space Flight Center, NASA.

      “Looking for a Talent Unicorn; a qualified, experienced candidate with both leadership skills and deep technical expertise that can grow and learn with emerging technologies.”

      Steve Thornton
      Acting Division Chief, Solutions Division,
      Goddard Space Flight Center, NASA

      Case Study: Using culture to drive your talent pool

      A good brand overcomes challenges

      Culture takes the lead in NASA's job postings, which attract a high number of candidates. Postings begin with a link to a short video on working at NASA, its history, and how it lives its vision. The video highlights NASA's diversity of perspectives, career development, and learning opportunities.

      NASA's company brand and employer brand are tightly intertwined, providing a consistent view of the organization.

      The employer vision is presented in the best place to reach NASA's ideal candidate: usajobs.gov, the official website of the United States Government and the “go-to” for government job listings. NASA also extends its postings to other generic job sites as well as LinkedIn and professional associations.

      Photo of Robert Leahy, Chief Information Officer, Goddard Space Flight Center, NASA.

      Interview with Robert Leahy
      Chief Information Officer
      Goddard Space Flight Center, NASA

      “Making sure we have the tools and mechanisms are two hiring challenges we are going to face in the future as how we work evolves and our work environment changes. What will we need to consider with our job announcements and the criteria for selecting employees?”

      Liteshia Dennis,
      Office Chief, Headquarter IT Office, Goddard Space Flight Center, NASA

      The ability to attract and secure candidates requires a strategy

      Despite prioritizing recruiting, IT departments see candidate experience as THE last Priority, either not focusing on it or relegating it to HR

      Candidate experience is listed as one of the bottom IT challenges, but without a positive experience, securing the talent you want will be difficult.

      Candidate experience starts with articulating your unique culture, benefits, and opportunities for development and innovative work as well as outlining flexible working options within an employer brand. Defining an employee value proposition is key to marketing your roles to potential employees.

      81% of respondents' rate culture as very important when considering a potential employer. (Info-Tech IT Talent Trends 2022 Survey)

      Tactics Used in Job Postings to Position the Organization Favorably as a Potential Employer

      Horizontal bar chart measuring percentage of survey responses about tactics used in job postings. The top tactics are 'Culture, 40%', 'Benefits, 40%', 'Opportunity for Innovative Work, 30%', and 'Professional Development, 30%'.(Info-Tech IT Talent Trends 2022 Survey)

      Case Study: Increasing talent pool at Info-Tech Research Group

      Strong sales leads to growth in operation capacity

      Info-Tech Research Group is an IT research & advisory firm helping IT leaders make strategic, timely, and well-informed decisions. Our actionable tools and analyst guidance ensure IT organizations achieve measurable results.

      The business has grown rapidly over the last couple of years, creating a need to recruit additional talent who were highly skilled in technical applications and approaches.

      In response, approval was given to expand headcount within Research for fiscal year 2022 and to establish a plan for continual expansion as revenue continues to grow.

      Looking for deep technical expertise with a passion for helping our members

      Hiring for our research department requires talent who are typically subject matter experts within their own respective IT domains and interested in and capable of developing research and advising clients through calls and workshops.

      This combination of skills, experience, and interest can be challenging to find, especially in an IT labor market that is more competitive than ever.

      Photo of Tracy-Lynn Reid, Practice Lead.

      Interview with Practice Lead Tracy-Lynn Reid

      Focus on Candidate Experience increases successful hire rate

      The senior leadership team established a project to focus on recruiting for net-new and open roles. A dedicated resource was assigned and used guidance from our research to enhance our hiring process to reduce time to hire and expand our candidate pool. Senior leaders stayed actively involved to provide feedback.

      The hiring process was improved by including panel interviews with interview protocols and a rubric to evaluate all candidates equitably.

      The initial screening conversation now includes a discussion on benefits, including remote and flexible work offerings, learning and development budget, support for post-secondary education, and our Buy-a-Book program.

      As a result, about 70% of the approved net-new headcount was hired within 12 weeks, with recruitment ongoing.

      Build an Information Security Strategy

      • Buy Link or Shortcode: {j2store}242|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: $45,303 Average $ Saved
      • member rating average days saved: 34 Average Days Saved
      • Parent Category Name: Security Strategy & Budgeting
      • Parent Category Link: /security-strategy-and-budgeting
      • Many security leaders struggle to decide how to best to prioritize their scarce information security resources
      • The need to move from a reactive approach to security towards a strategic planning approach is clear. The path to getting there is less so.

      Our Advice

      Critical Insight

      The most successful information security strategies are:

      • Holistic – They consider the full spectrum of information security, including people, processes, and technology.
      • Risk aware – They understand that security decisions should be made based on the security risks facing their organization, not just on “best practice.”
      • Business aligned – They demonstrate an understanding of the goals and strategies of the organization and how the security program can support the business.

      Impact and Result

      • Info-Tech has developed a highly effective approach to building an information security strategy, an approach that has been successfully tested and refined for more than seven years with hundreds of different organizations:
      • This approach includes tools for:
        • Ensuring alignment with business objectives.
        • Assessing organizational risk and stakeholder expectations.
        • Enabling a comprehensive current state assessment.
        • Prioritizing initiatives and building out a security roadmap.

      Build an Information Security Strategy Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Information Security (IS) Strategy Research – A step-by-step document that helps you build a holistic, risk-based, and business-aligned IS strategy.

      Your security strategy should not be based on trying to blindly follow best practices but on a holistic risk-based assessment that is risk aware and aligns with your business context. Use this storyboard to augment your security strategy by ensuring alignment with business objectives, assessing your organization's risk and stakeholder expectations, understanding your current security state, and prioritizing initiatives and a security roadmap.

      • Build an Information Security Strategy – Phases 1-4

      2. Information Security Requirements Gathering Tool – A tool to make informed security risk decisions to support business needs.

      Use this tool to formally identify business goals and customer and compliance obligations and make explicit links to how security initiatives propose to support these business interests. Then define the scope and boundaries for the security strategy and the risk tolerance definitions that will guide future security risk decisions.

      • Information Security Requirements Gathering Tool

      3. Information Security Pressure Analysis Tool – An evaluation tool to invest in the right security functions using a pressure analysis approach.

      Security pressure posture analysis helps your organization assess your real security context and enables you to invest in the right security functions while balancing the cost and value in alignment with business strategies. Security pressure sets the baseline that will help you avoid over-investing or under-investing in your security functions.

      • Information Security Pressure Analysis Tool

      4. Information Security Program Gap Analysis Tool – A structured tool to systematically understand your current security state.

      Effective security planning should not be one size fits all – it must consider business alignment, security benefit, and resource cost. To enable an effective security program, all areas of security need to be evaluated closely to determine where the organization sits currently and where it needs to go in the future.

      • Information Security Program Gap Analysis Tool

      5. Information Security Strategy Communication Deck – A best-of-breed presentation document to build a clear, concise, and compelling strategy document.

      Use this communication deck template to present the results of the security strategy to stakeholders, demonstrate the progression from the current state to the future state, and establish the roadmap of the security initiatives that will be implemented. This information security communication deck will help ensure that you’re communicating effectively for your cause.

      • Information Security Strategy Communication Deck

      6. Information Security Charter – An essential document for defining the scope and purpose of a security project or program.

      A charter is an essential document for defining the scope and purpose of security. Without a charter to control and set clear objectives for this committee, the responsibility of security governance initiatives will likely be undefined within the enterprise, preventing the security governance program from operating efficiently. This template can act as the foundation for a security charter to provide guidance to the governance of information security.

      • Information Security Charter
      [infographic]

      Workshop: Build an Information Security Strategy

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Assess Security Requirements

      The Purpose

      Understand business and IT strategy and plans.

      Key Benefits Achieved

      Defined security obligations, scope, and boundaries.

      Activities

      1.1 Define business and compliance.

      1.2 Establish security program scope.

      1.3 Analyze the organization’s risk and stakeholder pressures.

      1.4 Identify the organizational risk tolerance level.

      Outputs

      Security obligations statement

      Security scope and boundaries statement

      Defined risk tolerance level

      Risk assessment and pressure analysis

      2 Perform a Gap Analysis

      The Purpose

      Define the information security target state.

      Key Benefits Achieved

      Set goals and Initiatives for the security strategy in line with the business objectives.

      Activities

      2.1 Assess current security capabilities.

      2.2 Identify security gaps.

      2.3 Build initiatives to bridge the gaps.

      Outputs

      Information security target state

      Security current state assessment

      Initiatives to address gaps

      3 Complete the Gap Analysis

      The Purpose

      Continue assessing current security capabilities.

      Key Benefits Achieved

      Identification of security gaps and initiatives to bridge them according to the business goals.

      Activities

      3.1 Identify security gaps.

      3.2 Build initiatives to bridge the maturity gaps.

      3.3 Identify initiative list and task list.

      3.4 Define criteria to be used to prioritize initiatives.

      Outputs

      Completed security current state assessment

      Task list to address gaps

      Initiative list to address gaps

      Prioritize criteria

      4 Develop the Roadmap

      The Purpose

      Create a plan for your security strategy going forward.

      Key Benefits Achieved

      Set path forward to achieving the target state for the business through goal cascade and gap initiatives.

      Activities

      4.1 Conduct cost/benefit analysis on initiatives.

      4.2 Prioritize gap initiatives based on cost and alignment with business.

      4.3 Build an effort list.

      4.4 Determine state times and accountability.

      4.5 Finalize security roadmap and action plan.

      4.6 Create communication plan.

      Outputs

      Information security roadmap

      Draft communication deck

      5 Communicate and Implement

      The Purpose

      Finalize deliverables.

      Key Benefits Achieved

      Consolidate documentation into a finalized deliverable that can be used to present to executives and decision makers to achieve buy-in for the project.

      Activities

      5.1 Support communication efforts.

      5.2 Identify resources in support of priority initiatives.

      Outputs

      Security strategy roadmap documentation

      Detailed cost and effort estimates

      Mapping of Info-Tech resources against individual initiatives

      Further reading

      Build an Information Security Strategy

      Create value by aligning your strategy to business goals and business risks.

      Analyst Perspective

      Set your security strategy up for success.

      “Today’s rapid pace of change in business innovation and digital transformation is a call to action to information security leaders.

      Too often, chief information security officers find their programs stuck in reactive mode, a result of years of mounting security technical debt. Shifting from a reactive to proactive stance has never been more important. Unfortunately, doing so remains a daunting task for many.

      While easy to develop, security plans premised on the need to blindly follow ‘best practices’ are unlikely to win over many stakeholders. To be truly successful, an information security strategy needs to be holistic, risk-aware, and business-aligned.”

      Kevin Peuhkurinen

      Research Director – Security, Risk & Compliance

      Info-Tech Research Group

      Executive summary

      Your Challenge

      • Many security leaders struggle to decide how best to prioritize their scarce information security resources.
      • The need to move from a reactive approach to security toward a strategic planning approach is clear. The path to getting there is less clear.

      Common Obstacle

      • Developing a security strategy can be challenging. Complications include:
        • Performing an accurate assessment of your current security program can be extremely difficult when you don’t know what to assess or how.
        • Determining the appropriate target state for security can be even more challenging. A strategy built around following best practices is unlikely to garner significant support from business stakeholders.

      Info-Tech’s Approach

      • Info-Tech has developed a highly effective approach to building an information security strategy, an approach that has been successfully tested and refined for 7+ years with hundreds of organizations.
      • This unique approach includes tools for:
        • Ensuring alignment with business objectives.
        • Assessing organizational risk and stakeholder expectations.
        • Enabling a comprehensive current state assessment.
        • Prioritizing initiatives and building out a security roadmap.

      Info-Tech Insight

      The most successful information security strategies are:

      • Holistic. They consider the full spectrum of information security, including people, processes, and technologies.
      • Risk-Aware. They understand that security decisions should be made based on the security risks facing their organization, not just on best practice.
      • Business-Aligned. They demonstrate an understanding of the goals and strategies of the organization, and how the security program can support the business.

      It’s not a matter of if you have a security incident, but when

      Organizations need to prepare and expect the inevitable security breach.

      Fifty-eight percent of companies surveyed that experienced a breach were small businesses.

      Eighty-nine percent of breaches have a financial or espionage motive.

      Three graphs are depicted. The first is labeled ‘Total Cost for Three Data Breach Root Causes,’ the second ‘Distribution of Benchmark by Root Cause of the Data Breach,’ and the third ‘Per Capita for Three Root Causes of a Data Breach.’ The three root causes are malicious or criminal attack (US$166 million per capita), system glitch ($132 million per capita), and human error ($133 million per capita).

      Source: Ponemon Institute, “2019 Global Cost of Data Breach Study”

      An information security strategy can help you prepare for incidents

      Organizations need to expect the inevitable security breach.

      90%

      of businesses have experienced an external threat in the last year.

      50%

      of IT professionals consider security to be their number one priority.

      53%

      of organizations claimed to have experienced an insider attack in the previous 12 months. 1

      46%

      of businesses believe the frequency of attacks is increasing. 2

      Effective IT leaders approach their security strategy from an understanding that attacks on their organization will occur. Building a strategy around this assumption allows your security team to understand the gaps in your current approach and become proactive instead of being reactive.

      Sources: 1 Kaspersky Lab, “Global IT Security Risks Survey”; 2 CA Technologies, “Insider Threat 2018 Report”

      Persistent Issues

      Evolving Ransomware

      • Continual changes in types and platforms make ransomware a persistent threat. The frequency of ransomware attacks was reported to have increased by 67% in the past five years. 1

      Phishing Attacks

        • Despite filtering and awareness, email remains the most common threat vector for phishing attacks (94%) and an average of 3% of participants in phishing campaigns still click on them. 2

      Insider Privilege and Misuse

      • Typically, 34% of breaches are perpetrated by insiders, with 15% involving privilege misuse. Takeaway: Care less about titles and more about access levels. 3

      Denial of Service

      • The median amount of time that an organization is under attack from DDoS attack is three days.

      Emerging Trends

      Advanced Identity and Access Governance

      • Using emerging technologies in automation, orchestration, and machine learning, the management and governance of identities and access has become more advanced.

      Sources: 1 Accenture, “2019 The Cost of Cyber Crime Study”; 2,3 Verizon, “2019 Data Breach Investigations Report”

      New threat trends in information security aren’t new.

      Previously understood attacks are simply an evolution of prior implementations, not a revolution.

      Traditionally, most organizations are not doing a good-enough job with security fundamentals, which is why attackers have been able to use the same old tricks.

      However, information security has finally caught the attention of organizational leaders, presenting the opportunity to implement a comprehensive security program.

      Cyberattacks have a significant financial impact

      Global average cost of a data breach: $3.92 Million

      Source: Ponemon Institute, “2019 Cost of a Data Breach Study: Global Overview”

      A bar graph, titled ‘Average cost of data breach by industry,’ is depicted. Of 17 industries depicted, public is the lowest average cost (US$1.29 million) and health is the highest average cost ($6.45 million).

      Primary incident type (with a confirmed data breach)

      1. Leading incident type is Denial of Service attacks (DoS), taking up to 70% of all incidents.
      2. When it comes to data breaches, we see that the use of stolen credentials leads to the most cases of confirmed breaches, accounting for 29%.

      Personal records tend to be the most compromised data types, while databases tend to be the most frequently involved asset in breaches.

      Source: Verizon, “2019 Data Breach Investigations Report”

      Security threats are not going away

      We continue to see and hear of security breaches occurring regularly.

      A bar graph depicts the percentage of businesses who experienced a data breach in the last year–US total and global total. Numbers have increased from 2016 to 2019. In 2016, 19 percent of US businesses experienced a breach. In 2019, this number was 59 percent.

      An attacker must be successful only once. The defender – you – must be successful every time.

      Info-Tech’s approach

      Maturing from reactive to strategic information security

      Two circular graphs depict the move from ‘reactive security’ to ‘strategic security’ organizations can accomplish using Info-Tech’s approach.

      Tools icon that is used in the first three stages of the strategic security graph above. Indicates Info-Tech tools included in this blueprint.

      The Info-Tech difference:

      1. A proven, structured approach to mature your information security program from reactive to strategic.
      2. A comprehensive set of tools to take the pain out of each phase in the strategy building exercise.
      3. Visually appealing templates to communicate and socialize your security strategy and roadmap to your stakeholders.

      Info-Tech’s Security Strategy Model

      Info-Tech’s Security Strategy Model is depicted in this rectangular image with arrows. The first level depicts business context (enterprise goals, compliance obligations, scope and boundaries) and pressures (security risks, risk tolerance, stakeholder expectations). The second level depicts security target state (maturity model, security framework, security alignment goals, target maturity, time frame) and current state (current state assessment, gap analysis). The third level depicts the information security roadmap (initiative list, task list, prioritization methodology, and Gantt chart).

      The Info-Tech difference:

      An information security strategy model that is:

      1. Business-Aligned. Determines business context and cascades enterprise goals into security alignment goals.
      2. Risk-Aware. Understands the security risks of the business and how they intersect with the overall organizational risk tolerance.
      3. Holistic. Leverages a best-of-breed information security framework to provide comprehensive awareness of organizational security capabilities.

      Info-Tech’s best-of-breed security framework

      This image shows how Info-Tech’s framework is based on ISO 27000 series, CIS Top 20, COBIT 2019, NIST 800-53, and NIST CSF.

      Info-Tech’s approach

      Creating an information security strategy

      Value to the business

      Outcome

      Best-of-breed security strategy

      Have documentation that paints a picture of the road to compliance. Integrate your framework with your risk tolerance and external pressures.

      Be ready for future changes by aligning your security strategy to security framework best practices.

      Address the nature of your current information security

      Eliminate gaps in process and know what is in scope for your security strategy. Learn what pressures your business and industry are under.

      Gain insight into your current state, allowing you to focus on high-value projects first, transitioning towards a target state.

      Highlight overlooked functions of your current security strategy

      Build a comprehensive security program that brings to light all aspects of your security program.

      Instead of pursing ad hoc projects, know what needs work and how to prioritize your pressing security issues.

      Create a tangible roadmap to your target state

      Create a plan for your future state of information security. Refer to and update your target state as your business needs change.

      Document your current progress and path forward in the future. Know your goals and requirements, codified in a living document.

      Use our prepopulated deliverables to fast track your progress

      Let Info-Tech do the work for you. With completed deliverables, have tangible documents to convey your business needs.

      A comprehensive set of deliverables with concrete, defensible data to justify any business changes.

      A living security strategy

      Pivot and change prioritization to meet the needs of your security deficits.

      Future-proof your security strategy for any contingency.

      The Info-Tech difference:

      Evolve the security program to be more proactive by leveraging Info-Tech’s approach to building a security strategy.

      • Dive deep into security obligations and security pressures to define the business context.
      • Conduct a thorough current state and future state analysis that is aligned with a best-of-breed framework.
      • Prioritize gap-closing initiatives to create a living security strategy roadmap.

      Use Info-Tech’s blueprint to save one to three months

      This image depicts how using Info-Tech’s four-phase blueprint can save an estimated seven to 14 weeks of an organization’s time and effort.

      Iterative benefit

      Over time, experience incremental value from your initial security strategy. Through continual updates your strategy will evolve but with less associated effort, time, and costs.

      These estimates are based on experiences with Info-Tech clients throughout the creation of this blueprint.

      Key deliverable:

      Information Security Strategy Communication Deck (PPT)

      Present your findings in a prepopulated document that can summarizes all key findings of the blueprint.

      Screenshots from Info-Tech’s Information Security Strategy Communication Deck Template.

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

      Information Security Requirements Gathering Tool

      Define the business, customer, and compliance alignment for your security program.

      Information Security Pressure Analysis Tool

      Determine your organization’s security pressures and ability to tolerate risk.

      Information Security Program Gap Analysis Tool

      Use our best-of-breed security framework to perform a gap analysis between your current and target states.

      Information Security Charter

      Ensure the development and management of your security policies meet the broader program vision.

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

      Guided Implementation

      “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”

      Workshop

      “We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”

      Consulting

      “Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

      Diagnostic and consistent frameworks are used throughout all four options.

      Guided Implementation

      What does a typical Guided Implementation on this topic look like?

      Guided Implementation #1 - Assess security requirements
      • Call #1 - Introduce project and complete pressure analysis.
      Guided Implementation #2 - Build a gap initiative strategy
      • Call #1 - Introduce the maturity assessment.
      • Call #2 - Perform gap analysis and translate into initiatives.
      • Call #3 - Consolidate related gap initiatives and define, cost, effort, alignment, and security benefits.
      Guided Implementation #3 - Prioritize initiatives and build roadmap
      • Call #1 - Review cost/benefit analysis and build an effort map.
      • Call #2 - Build implementation waves and introduce Gantt chart.
      Guided Implementation #4 - Execute and maintain
      • Call #1 - Review Gantt chart and ensure budget/buy-in support.
      • Call #2 - Three-month check-in: Execute and maintain.

      A Guided Implementation is series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical Guided Implementation is between 2-12 calls over the course of 4 to 6 months.

      Workshop Overview

      Contact your account representative for more information, or contact workshops@infotech.com or 1-888-670-8889.

      Day 1

      Day 2

      Day 3

      Day 4

      Day 5

      Activities

      Assess Security Requirements

      Perform a Gap Analysis

      Complete the Gap Analysis

      Develop Roadmap

      Communicate and Implement

      1.1 Understand business and IT strategy and plans

      1.2 Define business and compliance requirements

      1.3 Establish the security program scope

      1.4 Analyze the organization’s risks and stakeholder pressures

      1.5 Identify the organizational risk tolerance level

      2.1 Define the information security target state

      2.2 Assess current security capabilities

      2.3 Identify security gaps

      2.4 Build initiatives to bridge the gaps

      3.1 Continue assessing current security capabilities

      3.2 Identify security gaps

      3.3 Build initiatives to bridge the maturity gaps

      3.4 Identify initiative list and task list

      3.5 Define criteria to be used to prioritize initiatives

      4.1 Conduct cost/benefit analysis on initiatives

      4.2 Prioritize gap initiatives based on cost, time, and alignment with the business

      4.3 Build effort map

      4.4 Determine start times and accountability

      4.5 Finalize security roadmap and action plan

      4.6 Create communication plan

      5.1 Finalize deliverables

      5.2 Support communication efforts

      5.3 Identify resources in support of priority initiatives

      Deliverables

      1.Security obligations statement

      2.Security scope and boundaries statement

      3.Defined risk tolerance level

      4.Risk assessment and pressure analysis

      1.Information security target state

      2.Security current state assessment

      3.Initiatives to address gaps

      1.Completed security current state assessment

      2.Task list to address gaps address gaps

      4.Prioritization criteria

      1.Information security roadmap

      2.Draft communication deck

      1.Security strategy roadmap documentation

      2.Detailed cost and effort estimates

      3.Mapping of Info-Tech resources against individual initiatives

      Executive Brief Case Study

      Credit Service Company

      Industry: Financial Services

      Source: Info-Tech Research group

      Founded over 100 years ago, Credit Service Company (CSC)* operates in the United States with over 40 branches located across four states. The organization services over 50,000 clients.

      Situation

      Increased regulations, changes in technology, and a growing number of public security incidents had caught the attention of the organization’s leadership. Despite awareness, an IT and security strategy had not been previously created. Management was determined to create a direction for the security team that aligned with their core mission of providing exceptional service and expertise.

      Solution

      During the workshop, the IT team and Info-Tech analysts worked together to understand the organization’s ideal state in various areas of information security. Having a concise understanding of requirements was a stepping stone to beginning to develop CSC’s prioritized strategy.

      Results

      Over the course of the week, the team created a document that concisely prioritized upcoming projects and associated costs and benefits. On the final day of the workshop, the team effectively presented the value of the newly developed security strategy to senior management and received buy-in for the upcoming project.

      *Some details have been changed for client privacy.

      Phase 1

      Assess Security Requirements

        Phase 1

      • 1.1 Define goals & scope
      • 1.2 Assess risks
      • 1.3 Determine pressures
      • 1.4 Determine risk tolerance
      • 1.5 Establish target state

        Phase 2

      • 2.1 Review Info-Tech’s security framework
      • 2.2 Assess your current state
      • 2.3 Identify gap closure actions

        Phase 3

      • 3.1 Define tasks & initiatives
      • 3.2 Perform cost/benefit analysis
      • 3.3 Prioritize initiatives
      • 3.4 Build roadmap

        Phase 4

      • 4.1 Build communication deck
      • 4.2 Develop a security charter
      • 4.3 Execute on your roadmap

      This phase will walk you through the following activities:

      1.1 Define goals and scope of the security strategy.

      1.2 Assess your organization’s current inherent security risks.

      1.3 Determine your organization’s stakeholder pressures for security.

      1.4 Determine your organization’s risk tolerance.

      1.5 Establish your security target state.

      1.1.1 Record your business goals

      Once you have identified your primary and secondary business goals, as well as the corresponding security alignment goals, record them in the Information Security Requirements Gathering Tool. The tool provides an activity status that will let you know if any parts of the tool have not been completed.

      1. Record your identified primary and secondary business goals in the Goals Cascade tab of the Information Security Requirements Gathering Tool.

      Use the drop-down lists to select an appropriate goal or choose “Other.” If you do choose “Other,” you will need to manually enter an appropriate business goal.

      2. For each of your business goals, select one to two security alignment goals. The tool will provide you with recommendations, but you can override these by selecting a different goal from the drop-down lists.

      A screenshot of the ‘Business Goals Cascade,’ which is part of the ‘Information Security Requirements Gathering Tool.’

      A common challenge for security leaders is how to express their initiatives in terms that are meaningful to business executives. This exercise helps to make an explicit link between what the business cares about and what security is trying to accomplish.

      1.1.2 Review your goals cascade

      Estimated Time: 15 minutes

      1. When you have completed the goals cascade, you can review a graphic diagram that illustrates your goals. The graphic is found on the Results tab of the Information Security Requirements Gathering Tool.
        • Security must support the primary business objectives. A strong security program will enable the business to compete in new and creative ways, rather than simply acting as an obstacle.
        • Failure to meet business obligations can result in operational problems, impacting the organization’s ability to function and the organization’s bottom line.
      2. Once you have reviewed the diagram, copy it into the Information Security Strategy Communication Deck.

      A screenshot of the ‘Goal Cascade Diagrams,’ which is part of the ‘Information Security Requirements Gathering Tool.’

      Identify your compliance obligations

      Most conventional regulatory obligations are legally mandated legislation or compliance obligations, such as:

      Sarbanes-Oxley Act (SOX)

      Applies to public companies that have registered equity or debt securities within the SEC to guarantee data integrity against financial fraud.

      Payment Card Industry Data Security Standard (PCI DSS)

      Applies to any organization that processes, transmits, or stores credit card information to ensure cardholder data is protected.

      Health Insurance Portability and Accountability Act (HIPAA)

      Applies to the healthcare sector and protects the privacy of individually identifiable healthcare information.

      Health Information Technology for Economic and Clinical Health (HITECH)

      Applies to the healthcare sector and widens the scope of privacy and security protections available under HIPAA.

      Personal Information Protection and Electronic Documents Act (PIPEDA)

      Applies to private sector organizations that collect personal information in Canada to ensure the protection of personal information in the course of commercial business.

      Compliance obligations also extend to voluntary security frameworks:

      NIST

      National Institute of Standards and Technology; a non-regulatory agency that develops and publicizes measurement

      CIS – 20 CSC

      Center for Internet Security – 20 Critical Security Controls; foundational set of effective cybersecurity practices.

      ISO 27001

      An information security management system framework outlining policies and procedures.

      COBIT 5

      An information technology and management and governance framework.

      HITRUST

      A common security framework for organizations that use or hold regulated personal health information.

      1.1.3 Record your compliance obligations

      Estimated Time: 30 minutes

      1. Identify your compliance obligations. Most organizations have compliance obligations that must be adhered to. These can include both mandatory and voluntary obligations. Mandatory obligations include:
        • Laws
        • Government regulations
        • Industry standards
        • Contractual agreements
        Voluntary obligations include standards that the organization has chosen to follow for best practices and any obligations that are required to maintain certifications. Organizations will have many different compliance obligations. For the purposes of your security strategy, include only those that have information security or privacy requirements.
      2. Record your compliance obligations, along with any notes, in your copy of the Information Security Requirements Gathering Tool.

      A screenshot of ‘Security Compliance Obligations,’ part of the ‘Information Security Requirements Gathering Tool.’

      Establish your scope and boundaries

      It is important to know at the outset of the strategy: what are we trying to secure?

      This includes physical areas we are responsible for, types of data we care about, and departments or IT systems we are responsible for.

      This also includes what is not in scope. For some outsourced services or locations, you may not be responsible for their security. In some business departments, you may not have control of security processes. Ensure that it is made explicit at the outset what will be included and what will be excluded from security considerations.

      Physical Scope and Boundaries

      • How many offices and locations does your organization have?
      • Which locations/offices will be covered by your information security management system (ISMS)?
      • How sensitive is the data residing at each location?
      • You may have many physical locations, and it is not necessary to list every one. Rather, list exceptional cases that are specifically in or out of scope.

      IT Systems Scope and Boundaries

      • There may be hundreds of applications that are run and maintained in your organization. Some of these may be legacy applications. Does your ISMS need to secure all your programs or a select few?
      • Is the system owned or outsourced?
      • Where are we accountable for security?
      • How sensitive is the data that each system handles?

      Organizational Scope and Boundaries

      • Will your ISMS cover all departments within your organization? For example, do certain departments (e.g. Operations) not need any security coverage?
      • Do you have the ability to make security decisions for each department?
      • Who are the key stakeholders/data owners for each department?

      Organizational scope considerations

      Many different groups will fall within the purview of the security strategy. Consider these two main points when deciding which departments will be in scope:

      1. If a group/user has access to data or systems that can impact the organization, then securing that group/user should be included within scope of the security strategy.
      2. If your organization provides some work direction to a group/user, they should be included within scope of the security strategy.
      1. Identify your departments and business groups
        • Start by identifying departments that provide some essential input or service to the organization or departments that interact with sensitive data.
      2. Break out different subsidiaries or divisions
        • Subsidiaries may or may not be responsible for securing themselves and protecting their data, but either way they are often heavily reliant on corporate for guidance and share IT resourcing support.
      3. Identify user groups
        • Many user groups exist, all requiring different levels of security. For example, from on-premises to remote access, from full-time employees to part-time or contractors.

      Physical scope considerations

      List physical locations by type

      Offices

      The primary location(s) where business operations are carried out. Usually leased or owned by the business.

      Regional Offices

      These are secondary offices that can be normal business offices or home offices. These locations will have a VPN connection and some sort of tenant.

      Co-Locations

      These are redundant data center sites set up for additional space, equipment, and bandwidth.

      Remote Access

      This includes all remaining instances of employees or contractors using a VPN to connect.

      Clients and Vendors

      Various vendors and clients have dedicated VPN connections that will have some control over infrastructure (whether owed/laaS/other).

      List physical locations by nature of the location

      Core areas within physical scope

      These are many physical locations that are directly managed. These are high-risk locations with many personal and services, resulting in many possible vulnerabilities and attack vectors.

      Locations on the edge of control

      These are on the edge of the physical scope, and thus, in scope of the security strategy. These include remote locations, remote access connections, etc.

      Third-party connections

      Networks of third-party users are within physical scope and need defined security requirements and definitions of how this varies per user.

      BYOD

      Mostly privately owned mobile devices with either on-network or remote access.

      It would be overkill and unhelpful to list every single location or device that is in scope. Rather, list by broad categories as suggested above or simply list exceptional cases that are in/out of scope.

      IT systems scope considerations

      Consider identifying your IT systems by your level of control or ownership.

      Fully owned systems

      These are systems that are wholly owned or managed by your organization.

      IT is almost always the admin of these systems. Generally they are hosted on premises. All securitization through methods such as patching or antivirus is done and managed by your IT department.

      Cloud/remote hosted (SaaS)

      These are systems with a lot of uncertainties because the vendor or service provided is either not known or what they are doing for security is not fully known.

      These systems need to be secured regardless, but supplier and vendor relationship management becomes a major component of how to manage these systems. Often, each system has varying levels of risk based on vendor practices.

      Hybrid owned (IaaS/PaaS)

      You likely have a good understanding of control for these systems, but they may not be fully managed by you (i.e. ownership of the infrastructure). These systems are often hosted by third parties that do some level of admin work.

      A main concern is the unclear definition of responsibility in maintaining these systems. These are managed to some degree by third parties; it is challenging for your security program to perform the full gamut of security or administrative functions.

      Unknown/unowned systems

      There are often systems that are unowned and even unknown and that very few people are using. These apps can be very small and my not fall under your IT management system framework. These systems create huge levels of risk due to limited visibility.

      For example, unapproved (shadow IT) file sharing or cloud storage applications would be unknown and unowned.

      1.1.4 Record your scope and boundaries

      Estimated Time: 30-60 minutes

      1. Divide into groups and give each group member a handful of sticky notes. Ask them to write down as many items as possible for the organization that could fall under one of the scope buckets.
      2. Collect each group’s responses and discuss the sticky notes and the rationale for including them. Discuss your security-related locations, data, people, and technologies, and define their scope and boundaries.
        • Careful attention should be paid to any elements of the strategy that are not in scope.
      3. Discuss and aggregate all responses as to what will be in scope of the security strategy and what will not be. Record these in the Information Security Requirements Gathering Tool.

      A screenshot of ‘Scope and Boundaries,’ part of the ‘Information Security Requirements Gathering Tool.’

      1.2 Conduct a risk assessment

      Estimated Time: 1-3 hours

      1. As a group, review the questions on the Risk Assessment tab of the Information Security Pressure Analysis Tool.
      2. Gather the required information from subject matter experts on the following risk elements:
        • Threats
        • Assets
        • Vulnerabilities (people, systems, supply chain)
        • Historical security incidents

      Input

      • List of organizational assets
      • Historical data on information security incidents

      Output

      • Completed risk assessment

      Materials

      • Information Security Pressure Analysis Tool

      Participants

      • Security Team
      • IT Leadership
      • Risk Management

      Download the Information Security Pressure Analysis Tool

      1.2.1 Complete the risk assessment questionnaire

      Estimated Time: 60-90 minutes

      1. Review each question in the questionnaire and provide the most appropriate response using the drop-down list.
        • If you are unsure of the answer, consult with subject matter experts to obtain the required data.
        • Otherwise, provide your best estimation
      2. When providing responses for the historical incident questions, only count incidents that had a sizeable impact on the business.

      A screenshot of the ‘Organizational Security Risk Assessment,’ part of the ‘Information Security Pressure Analysis Tool.’

      Info-Tech Insight

      Understanding your organization’s security risks is critical to identifying the most appropriate level of investment into your security program. Organizations with more security risks will need more a mature security program to mitigate those risks.

      1.2.2 Review the results of the risk assessment

      Estimated Time: 30 minutes

      1. Once you have completed the risk assessment, you can review the output on the Results tab.
      2. If required, the weightings of each of the risk elements can be customized on the Weightings tab.
      3. Once you have reviewed the results, copy your risk assessment diagram into the Information Security Strategy Communication Deck.

      A screenshot showing sample results of the ‘Organizational Risk Assessment,’ part of the ‘Information Security Pressure Analysis Tool.’

      It is important to remember that the assessment measures inherent risk, meaning the risk that exists prior to the implementation of security controls. Your security controls will be assessed later as part of the gap analysis.

      1.3 Conduct pressure analysis

      Estimated Time: 1-2 hours

      1. As a group, review the questions on the Pressure Analysis tab of the Information Security Pressure Analysis Tool.
      2. Gather the required information from subject matter experts on the following pressure elements:
        • Compliance and oversight
        • Customer expectations
        • Business expectations
        • IT expectations

      Input

      • Information on various pressure elements within the organization

      Output

      • Completed pressure analysis

      Materials

      • Information Security Pressure Analysis Tool

      Participants

      • Security Team
      • IT Leadership
      • Business Leaders
      • Compliance

      Download the Information Security Pressure Analysis Tool

      Risk tolerance considerations

      At this point, we want to frame risk tolerance in terms of business impact. Meaning, what kinds of impacts to the business would we be able to tolerate and how often? This will empower future risk decisions by allowing the impact of a potential event to be assessed, then compared against the formalized tolerance. We will consider impact from three perspectives:

      F

      Functional Impact

      The disruption or degradation of business/organizational processes.

      I

      Informational Impact

      The breach of confidentiality, privacy, or integrity of data/information.

      R

      Recoverability Impact

      The disruption or degradation of the ability to return to conditions prior to a security incident.

      Consider these questions:

      Questions to ask

      Description

      Is there a hard-dollar impact from downtime?

      This refers to when revenue or profits are directly impacted by a business disruption. For example, when an online ordering system is compromised and shut down, it affects sales, and therefore, revenue.

      Is regulatory compliance a factor?

      Depending on the circumstances of the vulnerabilities, it can be a violation of compliance obligations that would cause significant fines.

      Are any critical services dependent on this asset?

      Functional dependencies are sometimes not obvious, and assets that appear marginal can have huge impacts on critical services.

      Is there a health or safety risk?

      Some operations are critical to health and safety. For example, medical organizations have operations that are necessary to ensure uninterrupted critical health services. An exploited vulnerability that impacts these operations can have life and death consequences.

      ANALYST PERSPECTIVE

      It is crucial to keep in mind that you care about a risk scenario impact to the main business processes.

      For example, imagine a complete functional loss of the corporate printers. For most businesses, even the most catastrophic loss of printer function will have a small impact on their ability to carry out the main business functions.

      On the flip side, even a small interruption to email or servers could have a large functional impact on business processes.

      Risk tolerance descriptions

      High

      • Organizations with high risk tolerances are often found in industries with limited security risk, such as Construction, Agriculture and Fishing, or Mining.
      • A high risk tolerance may be appropriate for organizations that do not rely on highly sensitive data, have limited compliance obligations, and where their customers do not demand strong security controls. Organizations that are highly focused on innovation and rapid growth may also tend towards a higher risk tolerance.
      • However, many organizations adopt a high risk tolerance by default simply because they have not adequately assessed their risks.

      Moderate

      • Organizations with medium risk tolerances are often found in industries with moderate levels of security risk, such as Local Government, Education, or Retail and Wholesale
      • A medium risk tolerance may be appropriate for organizations that store and process some sensitive data, have a modest number of compliance obligations, and where customer expectations for security tend to be implicit rather than explicit.

      Low

      • Organizations with low risk tolerances are often found in industries with elevated security risk, such as Financial Services, Federal Governments, or Defense Contractors.
      • A low risk tolerance may be appropriate for organizations that store very sensitive data, process high-value financial transactions, are highly regulated, and where customers demand strong security controls.
      • Some organizations claim to have a low risk tolerance, but in practice will often allow business units or IT to accept more security risk than would otherwise be permissible. A strong information security program will be required to manage risks to an acceptable level.

      1.4.1 Complete the risk tolerance questionnaire

      Estimated Time: 30-60 minutes

      1. In a group discussion, review the low-, medium-, and high-impact scenarios and examples for each impact category. Ensure that everyone has a consistent understanding of the scenarios.
      2. For each impact type, use the frequency drop-down list to identify the maximum frequency that the organization could tolerate for the event scenarios, considering:
        • The current frequency with which the scenarios are occurring in your organization may be a good indication of your tolerance. However, keep in mind that you may be able to tolerate these incidents happening more frequently than they do.
        • Hoping is not the same as tolerating. While everyone hopes that high-impact incidents never occur, carefully consider whether you could tolerate them occurring more frequently.

      A screenshot showing the ‘Organizational Security Risk Tolerance Assessment,’ part of the ‘Information Security Pressure Analysis Tool.’

      1.4.2 Review the results of the risk tolerance analysis

      Estimated Time: 30 minutes

      1. Once you have completed the risk tolerance exercise, you can review the output on the Results tab.
      2. If required, the weightings of each of the impact types can be customized on the Weightings tab.
      3. Once you have reviewed the results, copy your risk tolerance diagram into the Information Security Strategy Communication Deck.

      A screenshot showing the results of the 'Information Security Risk Tolerance Assessment,' part of the ‘Information Security Pressure Analysis Tool.’

      A low risk tolerance will require a stronger information security program to ensure that operational security risk in the organization is minimized. If this tool reports that your risk tolerance is low, it is recommended that you review the results with your senior stakeholders to ensure agreement and support for the security program.

      1.5 Establish your target state

      Estimated Time: 30-60 minutes

      1. As a group, review the overall results of the requirements gathering exercise:
        • Business goals cascade
        • Compliance obligations
        • Scope
      2. Review the overall results of the risk assessment, pressure analysis, and risk tolerance exercises.
      3. Conduct a group discussion to arrive at a consensus of what the ideal target state for the information security program should look like.
        • Developing mission and vision statements for security may be useful for focusing the group.
        • This discussion should also consider the desired time frame for achieving the target state.

      Download the Information Security Pressure Analysis Tool

      Input

      • Information security requirements (goals cascade, compliance obligations, scope)
      • Risk assessment
      • Pressure analysis
      • Risk tolerance

      Output

      • Completed information security target state

      Materials

      Participants

      • Security Team
      • IT Leadership
      • Risk Management
      • Business Leaders
      • Compliance

      Understanding security target states

      Maturity models are very effective for determining information security target states. This table provides general descriptions for each maturity level. As a group, consider which description most accurately reflects the ideal target state for information security in your organization.

      1. AD HOC

        Initial/Ad hoc security programs are reactive. Lacking strategic vision, these programs are less effective and less responsive to the needs of the business.
      2. DEVELOPING

        Developing security programs can be effective at what they do but are not holistic. Governance is largely absent. These programs tend to rely on the talents of individuals rather than a cohesive plan.
      3. DEFINED

        A defined security program is holistic, documented, and proactive. At least some governance is in place, however, metrics are often rudimentary and operational in nature. These programs still often rely on best practices rather than strong risk management.
      4. MANAGED

        Managed security programs have robust governance and metrics processes. Management and board-level metrics for the overall program are produced. These are reviewed by business leaders and drive security decisions. More mature risk management practices take the place of best practices.
      5. OPTIMIZED

        An optimized security program is based on strong risk management practices, including the production of key risk indicators (KRIs). Individual security services are optimized using key performance indicators (KPIs) that continually measure service effectiveness and efficiency.

      1.5.1 Review the results of the target state recommendation

      Estimated Time: 30-60 minutes

      1. Based upon your risk assessment, pressure analysis, and risk tolerance, the Information Security Pressure Analysis Tool will provide a recommended information security target state.
      2. With your group, review the recommendation against your expectations.
      3. If required, the weightings of each of the factors can be customized on the Weightings tab.
      4. Once you have reviewed the results, copy your target state diagram into the Information Security Strategy Communication Deck.

      A screenshot showing the results of the ‘Information Security Target State,’ part of the ‘Information Security Pressure Analysis Tool.’

      Info-Tech Insight

      Higher target states require more investment to attain. It is critical to ensure that all key stakeholders agree on the security target state. If you set a target state that aims too high, you may struggle to gain support and funding for the strategy. Taking this opportunity to ensure alignment from the start will pay off dividends in future.

      1.5.2 Review and adjust risk and pressure weightings

      Estimated Time: 30 minutes

      1. If the results of your risk assessment, pressure analysis, risk tolerance, or target state do not match your expectations, you may need to review and adjust the weightings for the elements within one or more of these areas.
      2. On the Weightings tab, review each of the strategic categories and adjust the weights as required.
        • Each domain is weighted to contribute to your overall pressure score based on the perceived importance of the domain to the organization.
        • The sum of all weights for each category must add up to 100%.

      A screenshot showing the results of the weightings given to each factor in a category, part of the ‘Information Security Pressure Analysis Tool.’

      Case Study

      Credit Service Company

      Industry: Financial Services

      Source: Info-Tech Research group

      Below are some of the primary requirements that influenced CSC’s initial strategy development.

      External Pressure

      Pressure Level: High

      • Highly regulated industries, such as Finance, experience high external pressure.
      • Security pressure was anticipated to increase over the following three years due to an increase in customer requirement.

      Obligations

      Regulatory: Numerous regulations and compliance requirements as a financial institution (PCI, FFIEC guidance).

      Customer: Implicitly assumes personal, financial, and health information will be kept secure.

      Risk Tolerance

      Tolerance Level: Low

      1. Management: Are risk averse and have high visibility into information security.
      2. Multiple locations controlled by a central IT department decreased the organization’s risk tolerance.

      Summary of Security Requirements

      Define and implement dynamic information security program that understands and addresses the business’ inherent pressure, requirements (business, regulatory, and customer), and risk tolerance.

      Phase 2

      Build a Gap Initiative Strategy

        Phase 1

      • 1.1 Define goals & scope
      • 1.2 Assess risks
      • 1.3 Determine pressures
      • 1.4 Determine risk tolerance
      • 1.5 Establish target state

        Phase 2

      • 2.1 Review Info-Tech’s security framework
      • 2.2 Assess your current state
      • 2.3 Identify gap closure actions

        Phase 3

      • 3.1 Define tasks & initiatives
      • 3.2 Perform cost/benefit analysis
      • 3.3 Prioritize initiatives
      • 3.4 Build roadmap

        Phase 4

      • 4.1 Build communication deck
      • 4.2 Develop a security charter
      • 4.3 Execute on your roadmap

        This phase will walk you through the following activities:

      • 2.1 Review Info-Tech’s framework.
      • 2.2 Assess your current state of security against your target state.
      • 2.3 Identify actions required to close gaps.

      2.1 Review the Info-Tech framework

      Estimated Time: 30-60 minutes

      1. As a group, have the security team review the security framework within the Information Security Gap Analysis Tool.
      2. Customize the tool as required using the instructions on the following slides.

      Input

      • Information security requirements
      • Security target state

      Output

      • Customized security framework

      Materials

      • Information Security Gap Analysis Tool

      Participants

      • Security Team

      Download the Information Security Gap Analysis Tool

      Understand the Info-Tech framework

      Info-Tech’s security framework uses a best-of-breed approach to leverage and align with most major security standards, including:

      • ISO 27001/27002
      • COBIT
      • Center for Internet Security (CIS) Critical Controls
      • NIST Cybersecurity Framework
      • NIST SP 800-53
      • NIST SP 800-171

      A diagram depicting Info-Tech’s best-of-breed security framework.

      A best-of-breed approach ensures holistic coverage of your information security program while refraining from locking you in to a specific compliance standard.

      2.1.1 Configure the Information Security Gap Analysis Tool

      Estimated Time: 30 minutes

      Review the Setup tab of the Information Security Gap Analysis Tool. This tab contains several configurable settings that should be customized to your organization. For now, the three settings you will need to modify are:

      • The security target state. Enter the target state from your Information Security Pressure Analysis Tool. If you do not enter a target state, the tool will default to a target of 3 (Defined).
      • Your Security Alignment Goals (from your Information Security Requirements Gathering Tool).
      • The starting year for your security roadmap.

      A screenshot showing the ‘Setup’ tab of the ‘Information Security Gap Analysis Tool.’

      2.2 Assess current state of security

      Estimated Time: 8-16 hours

      1. Using the Information Security Gap Analysis Tool, review each of the controls in the Gap Analysis tab.
      2. Follow the instructions on the next slides to complete your current state and target state assessment.
      3. For most organizations, multiple internal subject matter experts will need to be consulted to complete the assessment.

      Input

      • Security target state
      • Information on current state of security controls, including sources such as audit findings, vulnerability and penetration test results, and risk registers

      Output

      • Gap analysis

      Materials

      • Information Security Gap Analysis Tool

      Participants

      • Security Team
      • Subject Matter Experts From IT, HR, Legal, Facilities, Compliance, Audit, Risk Management

      Download the Information Security Gap Analysis Tool

      Example maturity levels

      To help determine appropriate current and target maturity levels, refer to the example below for the control “Email communication is filtered for spam and potential malicious communications.”

      AD HOC 01

      There is no centrally managed spam filter. Spam may be filtered by endpoint email clients.

      DEVELOPING 02

      There is a secure email gateway. However, the processes for managing it are not documented. Administrator roles are not well defined. Minimal fine-tuning is performed, and only basic features are in use.

      DEFINED 03

      There is a policy and documented process for email security. Roles are assigned and administrators have adequate technical training. Most of the features of the solution are being used. Rudimentary reports are generated, and some fine-tuning is performed.

      MANAGED 04

      Metrics are produced to measure the effectiveness of the email security service. Advanced technical features of the solution have been implemented and are regularly fine-tuned based on the metrics.

      OPTIMIZED 05

      There is a dedicated email security administrator with advanced technical training. Custom filters are developed to further enhance security, based on relevant cyber threat intelligence. Email security metrics feed key risk indicators that are reported to senior management.

      2.2.1 Conduct current state assessment

      Estimated Time: 8-16 hours

      1. Carefully review each of the controls in the Gap Analysis tab. For each control, indicate the current maturity level using the drop-down list.
        • You should only use “N/A” if you are confident that the control is not required in your organization.
        • For example, if your organization does not perform any software development then you can select “N/A” for any controls related to secure coding practices.
      2. Provide comments to describe your current state. This step is optional but recommended as it may be important to record this information for future reference.
      3. Select the target maturity for the control. The tool will default to the target state for your security program, but this can be overridden using the drop-down list.

      2.2.1 Conduct current state assessment

      Estimated Time: 8-16 hours

      1. Carefully review each of the controls in the Gap Analysis tab. For each control, indicate the current maturity level using the drop-down list.
        • You should only use “N/A” if you are confident that the control is not required in your organization. For example, if your organization does not perform any software development then you can select “N/A” for any controls related to secure coding practices.
      2. Provide comments to describe your current state. This step is optional but recommended as it may be important to record this information for future reference.
      3. Select the target maturity for the control. The tool will default to the target state for your security program, but this can be overridden using the drop-down list.

      A screenshot showing the 'Gap Analysis' tab of the 'Information Security Gap Analysis Tool.'

      Review the Gap Analysis Dashboard

      Use the Gap Assessment Dashboard to map your progress. As you fill out the Gap Analysis Tool, check with the Dashboard to see the difference between your current and target state.

      Use the color-coded legend to see how large the gap between your current and target state is. The legend can be customized further if desired.

      Security domains that appear white have not yet been assessed or are rated as “N/A.”

      2.2.3 Identify actions required to close gaps

      Estimated Time: 4-8 hours

      1. Using the Information Security Gap Analysis Tool, review each of the controls in the Gap Analysis tab.
      2. Follow the instructions on the next slides to identify gap closure actions for each control that requires improvement.
      3. For most organizations, multiple internal subject matter experts will need to be consulted to complete the assessment.

      Input

      • Security control gap information

      Output

      • Gap closure action list

      Materials

      • Information Security Gap Analysis Tool

      Participants

      • Security Team
      • Subject Matter Experts From IT, HR, Legal, Facilities, Compliance, Audit, Risk Management

      Download the Information Security Gap Analysis Tool

      2.3.1 Identify gap closure actions

      Estimated Time: 4-8 hours

      1. For each of the controls where there is a gap between the current and target state, a gap closure action should be identified:
        • Review the example actions and copy one or more of them if appropriate. Otherwise, enter your own gap closure action.
      2. Identify whether the action should be managed as a task or as an initiative. Most actions should be categorized as an initiative. However, it may be more appropriate to categorize them as a task when:
        1. They have no costs associated with them
        2. They require a low amount of initial effort to implement and no ongoing effort to maintain
        3. They can be accomplished independently of other tasks

      A screenshot showing gap closure actions, part of the 'Gap Analysis' tab of the 'Information Security Gap Analysis Tool.'

      Considerations for gap closure actions

      • In small groups, have participants ask, “what would we have to do to achieve the target state?” Document these in the Gap Closure Actions column.
      • The example gap closure actions may be appropriate for your organization, but do not simply copy them without considering whether they are right for you.
      • Not all gaps will require their own action. You can enter one action that may address multiple gaps.
      • If you find that many of your actions are along the lines of “investigate and make recommendations,” you should consider using the estimated gap closure percentage column to track the fact that these gaps will not be fully closed by the actions.

      A screenshot showing considerations for gap closure actions, part of the 'Gap Analysis' tab of the 'Information Security Gap Analysis Tool.'

      2.3.2 Define gap closure action effectiveness

      Estimated Time: 1-2 hours

      For each of the gap closure actions, optionally enter an estimated gap closure percentage to indicate how effective the action will be in fully closing the gap.

      • For instance, an action to “investigate solutions and make recommendations” will not fully close the gap.
      • This is an optional step but will be helpful to understand how much progress towards your security target state you will make based on your roadmap.
      • If you do not fill in this column, the tool will assume that your actions will fully close all gaps.

      A screenshot showing considerations for estimated gap closure percentage, part of the 'Gap Analysis' tab of the 'Information Security Gap Analysis Tool.'

      Completing this step will populate the “Security Roadmap Progression” diagram in the Results tab, which will provide a graphic illustration of how close to your target state you will get based upon the roadmap.

      Phase 3

      Prioritize Initiatives and Build Roadmap

      Phase 1

      • 1.1 Define goals & scope
      • 1.2 Assess risks
      • 1.3 Determine pressures
      • 1.4 Determine risk tolerance
      • 1.5 Establish target state

      Phase 2

      • 2.1 Review Info-Tech’s security framework
      • 2.2 Assess your current state
      • 2.3 Identify gap closure actions

      Phase 3

      • 3.1 Define tasks & initiatives
      • 3.2 Perform cost/benefit analysis
      • 3.3 Prioritize initiatives
      • 3.4 Build roadmap

      Phase 4

      • 4.1 Build communication deck
      • 4.2 Develop a security charter
      • 4.3 Execute on your roadmap

      This phase will walk you through the following activities:

      • 3.1 Define tasks and initiatives.
      • 3.2 Define cost, effort, alignment, and security benefit of each initiative.
      • 3.3 Prioritize initiatives.
      • 3.4 Build the prioritized security roadmap

      3.1 Define tasks and initiatives

      Estimated Time: 2-4 hours

      1. As a group, review the gap actions identified in the Gap Analysis tab.
      2. Using the instructions on the following slides, finalize your task list.
      3. Using the instructions on the following slides, review and consolidate your initiative list.

      Input

      • Gap analysis

      Output

      • List of tasks and initiatives

      Materials

      • Information Security Gap Analysis Tool

      Participants

      • Security Team
      • Subject Matter Experts From IT, HR, Legal, Facilities, Compliance, Audit, Risk Management
      • Project Management Office

      Download the Information Security Gap Analysis Tool

      3.1.1 Finalize your task list

      Estimated Time: 1-2 hours

      1. Obtain a list of all your task actions by filtering on the Action Type column in the Gap Analysis tab.
      2. Paste the list into the table on the Task List tab.
        • Use Paste Values to retain the table formatting
      3. Enter a task owner and due date for each task. Without accountability, it is too easy to fall into complacency and neglect these tasks.

      A screenshot showing the 'Task List' tab of the 'Information Security Gap Analysis Tool.'

      Info-Tech Insight

      Tasks are not meant to be managed to the same degree that initiatives will be. However, they are still important. It is recommended that you develop a process for tracking these tasks to completion.

      3.1.2 Consolidate your gap closure actions into initiatives

      Estimated Time: 2-3 hours

      1. Once you have finalized your task list, you will need to consolidate your list of initiative actions. Obtain a list of all your initiative actions by filtering on the Action Type column in the Gap Analysis tab.
      2. Create initiatives on the Initiative List tab. While creating initiatives, consider the following:
        • As much as possible, it is recommended that you consolidate multiple actions into a single initiative. Reducing the total number of initiatives will allow for more efficient management of the overall roadmap.
        • Start by identifying areas of commonality between gap closure actions, for instance:
          • Group all actions within a security domain into a single initiative.
          • Group together similar actions, such as all actions that require updating policies.
          • Consider combining actions that have inter-dependencies.
        • While it is recommended that you consolidate actions as much as possible, some actions should become initiatives on their own. This will be appropriate when:
          • The action is time sensitive and consolidating it with other actions will cause scheduling issues.
          • Actions that could otherwise be consolidated have different business sponsors or owners and need to be kept separate for funding or accountability reasons.
      3. Link the initiative actions on the Gap Analysis tab using the drop-down list in the Initiative Name column.

      Initiative consolidation example

      In the example below, we see three gap closure actions within the Security Culture and Awareness domain being consolidated into a single initiative “Develop security awareness program.”

      We can also see one gap closure action within the same domain being grouped with two actions from the Security Policies domain into another initiative “Update security policies.”

      Info-Tech Insight

      As you go through this exercise, you may find that some actions that you previously categorized as tasks could be consolidated into an initiative.

      A screenshot showing how six sample gap closure actions can be distilled into two gap closure initiatives. Part of the 'Information Security Gap Analysis Tool.'

      3.1.3 Finalize your initiative list

      Estimated Time: 30 minutes

      1. Review your final list of initiatives and make any required updates.
      2. Optionally, add a description or paste in a list of the individual gap closure actions that are associated with the initiative. This will make it easier to perform the cost and benefit analysis.
      3. Use the drop-down list to indicate which of the security alignment goals most appropriately reflects the objectives of the initiative. If you are unsure, use the legend next to the table to find the primary security domain associated with the initiative and then select the recommended security alignment goal.
        • This step is important to understand how the initiative supports the business goals identified earlier.

       A screenshot showing the primary security alignment goal, part of the 'Initiative List' tab of the 'Information Security Gap Analysis Tool.'

      3.2 Conduct cost/ benefit analysis

      Estimated Time: 1-2 hours

      1. As a group, define the criteria to be used to conduct the cost/benefit analysis, following the instructions on the next slide.
      2. Assign costing and benefits information for each initiative.
      3. Define dependencies or business impacts if they will help with prioritization.

      Input

      • Gap analysis
      • Initiative list

      Output

      • Completed cost/benefit analysis for initiative list

      Materials

      • Information Security Gap Analysis Tool

      Participants

      • Security Team
      • Subject Matter Experts From IT, HR, Legal, Facilities, Compliance, Audit, Risk Management
      • Project Management Office

      Download the Information Security Gap Analysis Tool

      3.2.1 Define costing criteria

      Estimated Time: 30 minutes

      1. On the Setup tab of the Information Security Gap Analysis Tool, enter high, medium, and low ranges for initial and ongoing costs and efforts.
        1. Initial costs are one-time, upfront capital investments (e.g. hardware and software costs, project-based consulting fees, training).
        2. Ongoing cost is any annually recurring operating expenses that are new budgetary costs (e.g. licensing, maintenance, subscription fees).
        3. Initial staffing in hours is total time in person hours required to complete a project. It is not total elapsed time but dedicated time. Consider time required to gather requirements and to design, test, and implement the solution.
        4. Ongoing staffing in FTEs is the ongoing average effort required to support that initiative after implementation.
      2. In addition to ranges, provide an average for each. These will be used to calculate estimated total costs for the roadmap.

      A screenshot showing the initiative costs for estimation, part of the 'Setup' tab of the 'Information Security Gap Analysis Tool.' The range of costs is labeled with an arrow with number 1 on it, and the average cost per initiative is labeled with an arrow with number 2 on it.

      Make sure that your ranges allow for differentiation between initiatives to enable prioritization. For instance, if you set your ranges too low, all your initiatives will be assessed as high cost, providing no help when you must prioritize them.

      3.2.2 Define benefits criteria

      Estimated Time: 30 minutes

      1. On the Setup tab of the Information Security Gap Analysis Tool, enter high, medium, and low values for the Alignment with Business Benefit.
        • This variable is meant to capture how well each initiative aligns with organizational goals and objectives.
        • By default, this benefit is linked directly to business goals through the primary and secondary security alignment goals. This allows the tool to automatically calculate the benefit based on the security alignment goals associated with each initiative.
        • If you change these values, you may need to override the calculated values in the prioritization tab.
      2. Enter a high, medium, and low value for the Security Benefit.
        • This variable is meant to capture the relative security benefit or risk reduction being provided by the gap initiative.
        • By default, this benefit is linked to security risk reduction.

      A screenshot showing the initiative benefits for estimation, part of the 'Setup' tab of the 'Information Security Gap Analysis Tool.'

      Some organizations prefer to use the “Security Benefit” criteria to demonstrate how well each initiative supports specific compliance goals.

      3.2.3 Complete the cost/benefit analysis

      Estimated Time: 1-2 hours

      1. On the Prioritization tab, use the drop-down lists to enter the estimated costs and efforts for each initiative, using the criteria defined earlier.
        • If you have actual costs available, you can optionally enter them under the Detailed Cost Estimates columns.
      2. Enter the estimated benefits, also using the criteria defined earlier.
        • The Alignment with Business benefit will be automatically populated, but you can override this value using the drop-down list if desired.

      A screenshot showing the estimated cost, estimated effort, and estimated benefits section, part of the 'Prioritization' tab of the 'Information Security Gap Analysis Tool.' Estimated cost and estimated effort are labeled with an arrow with number 1 on it, and estimated benefits is labeled with an arrow with a number 2 on it.

      3.2.4 Optionally enter detailed cost estimates

      Estimated Time: 30 minutes

      1. For each initiative, the tool will automatically populate the Detailed Cost Estimates and Detailed Staffing Estimates columns using the averages that you provided in steps 3.2.1 and 3.2.2. However, if you have more detailed data about the costs and effort requirements for an initiative, you can override the calculated data by manually entering it into these columns. For example:
        • You are planning to subscribe to a security awareness vendor, and you have a quote from them specifying that the initial cost will be $75,000.
        • You have defined your “Medium” cost range as being “$10-100K”, so you select medium as your initial cost for this initiative in step 3.2.3. As you defined the average for medium costs as being $50,000, this is what the tool will put into the detailed cost estimate.
        • You can override this average by entering $75,000 as the initial cost in the detailed cost estimate column.

      A screenshot showing the detailed cost estimates and detailed staffing estimates columns, part of the 'Prioritization' tab of the 'Information Security Gap Analysis Tool.' These columns are labeled with an arrow with a number 1 on it.

      Case Study

      Credit Service Company

      Industry: Financial Services

      Source: Info-Tech Research Group

      A chart titled 'Framework Components,' displaying how the Credit Service Company profiled in the case study performed a current state assessment, created gap initiatives, and prioritized gap initiatives.

      3.3 Prioritize initiatives

      Estimated Time: 2-3 hours

      1. As a group, review the results of the cost/benefit analysis. Optionally, complete the Other Considerations columns in the Prioritization tab:
        • Dependencies can refer to other initiatives on the list or any other dependency that relates to activities or projects within the organization.
        • Business impacts can be helpful to document as they may require additional planning and communication that could impact initiative timelines.
      2. Follow step 3.3.1 to create an effort map with the results of the cost/benefit analysis.
      3. Follow step 3.3.2 to assign initiatives into execution waves.

      Input

      • Gap analysis
      • Initiative list
      • Cost/benefit analysis

      Output

      • Prioritized list of initiatives

      Materials

      • Information Security Gap Analysis Tool
      • Whiteboard

      Participants

      • Security Team
      • IT Leadership
      • Project Management Office

      Download the Information Security Gap Analysis Tool

      3.3.1 Create effort map

      Estimated Time: 30 minutes

      1. On a whiteboard, draw the quadrant diagram shown.
      2. Create sticky notes for each initiative on your initiative list.
      3. For each initiative, use the “Cost/Effort Rating” and the “Benefit Rating” calculated on the Prioritization tab to place the corresponding sticky note onto the diagram.

      An effort map is a tool used for the visualization of a cost/benefit analysis. It is a quadrant output that visually shows how your gap initiatives were prioritized. In this example, the initiative “Update Security Policies” was assessed as low cost/effort (3) and high benefit (10).

      An image showing how 'update security policies,' as ranked on a cost/effort and benefit quadrant, translates to a cost/effort and benefit rating on the 'Prioritization' tab of the 'Information Security Gap Analysis Tool.'

      3.3.2 Assign initiatives to execution waves

      Estimated Time: 60 minutes

      1. Using sticky flip chart sheets, create four sheets and label them according to the four execution waves:
        • MUST DO – These are initiatives that need to get moving right away. They may be quick wins, items with critical importance, or foundational projects upon which many other initiatives depend.
        • SHOULD DO – These are important initiatives that need to get done but cannot launch immediately due to budget constraints, dependencies, or business impacts that require preparation.
        • COULD DO – Initiatives that have merit but are not a priority.
        • WON’T DO – Initiatives where the costs outweigh the benefits.
      2. Using the further instructions on the following slides, move the initiative sticky notes from your effort map into the waves.

      Considerations for prioritization

      • Starting from the top right of the effort map, begin pulling stickies off and putting them in the appropriate roadmap category.
      • Keep dependencies in mind. If an important initiative depends on a low-priority one being completed first, then pull dependent initiatives up the list.
      • It may be helpful to think of each wave as representing a specific time frame (e.g. wave 1 = first year of your roadmap, wave 2 = year two, wave 3 = year three).

      Info-Tech Insight

      Use an iterative approach. Most organizations tend to put too many initiatives into wave 1. Be realistic about what you can accomplish and take several passes at the exercise to achieve a balance.

      An image showing how to map the sticky notes from a sample exercise, as placed on a cost/effort and benefit quadrant, into waves.

      3.3.3 Finalize prioritization

      Estimated Time: 30 minutes

      1. Once you have completed placing your initiative sticky notes into the waves, update the Prioritization tab with the Roadmap Wave column.
      2. Optionally, use the Roadmap Sub-Wave column to prioritize initiatives within a single wave.
        • This will allow you more granular control over the final prioritization, especially where dependencies require extra granularity.

      Any initiatives that are currently in progress should be assigned to Wave 0.

      An image showing the roadmap wave and roadmap sub-wave sections, part of the 'Prioritization' tab of the 'Information Security Gap Analysis Tool.' Roadmap wave is labeled with an arrow with a number 1 on it, and roadmap sub-wave is labeled with an arrow with a number 2 on it.

      3.4 Build roadmap

      Estimated Time: 1-3 hours

      1. As a group, follow step 3.4.1 to create your roadmap by scheduling initiatives into the Gantt chart within the Information Security Gap Analysis Tool.
      2. Review the roadmap for resourcing conflicts and adjust as required.
      3. Review the final cost and effort estimates for the roadmap.

      Input

      • Gap analysis
      • Cost/benefit analysis
      • Prioritized initiative list
      • (Optional) List of other non-security IT and business projects

      Output

      • Security strategic roadmap

      Materials

      • Information Security Gap Analysis Tool

      Participants

      • Security Team
      • IT Leadership
      • Project Management Office

      Download the Information Security Gap Analysis Tool

      3.4.1 Schedule initiatives using the Gantt chart

      Estimated Time: 1-2 Hours

      1. On the Gantt Chart tab for each initiative, enter an owner (the individual who will be primarily responsible for execution).
      2. Additionally, enter a start month and year for the initiative and the expected duration in months.
        • You can filter the Wave column to only see specific waves at any one time to assist with the scheduling.
        • You do not need to schedule Wave 4 initiatives as the expectation is that these initiatives will not be done.

      Info-Tech Insight

      Use the Owner column to help identify resourcing constraints. If a single individual is responsible for many different initiatives that are planned to start at the same time, consider staggering those initiatives.

      An image showing the owner and planned start sections, part of the 'Security Roadmap Gantt Chart' tab of the 'Information Security Gap Analysis Tool.' The owner column is labeled with an arrow with a 1 on it, and the planned start column is labeled with an arrow with a 2 on it.

      3.4.2 Review your roadmap

      Estimated Time: 30-60 minutes

      1. When you have completed the Gantt chart, as a group review the overall roadmap to ensure that it is reasonable for your organization. Consider the following:
        • Do you have other IT or business projects planned during this time frame that may impact your resourcing or scheduling?
        • Does your organization have regular change freezes throughout the year that will impact the schedule?
        • Do you have over-subscribed resources? You can filter the list on the Owner column to identify potential over-subscription of resources.
        • Have you considered any long vacations, sabbaticals, parental leaves, or other planned longer-term absences?
        • Are your initiatives adequately aligned to your budget cycle? For instance, if you have an initiative that is expected to make recommendations for capital expenditure, it must be completed prior to budget planning.

      A screenshot image showing parts of the 'Security Roadmap Gantt Chart' tab with sample data in it. Taken from the 'Information Security Gap Analysis Tool.'

      3.4.3 Review your expected roadmap progression

      Estimated Time: 30 minutes

      1. If you complete the optional exercise of filling in the Estimated Gap Closure Percentage column on the Gap Analysis tab, the tool will generate a diagram showing how close to your target state you can expect to get based on the tasks and initiatives in your roadmap. You can review this diagram on the Results tab.
        • Remember that this Expected Maturity at End of Roadmap score assumes that you will complete all tasks and initiatives (including all Wave 4 initiatives).
      2. Copy the diagram into the Information Security Strategy Communication Deck.

      Info-Tech Insight

      Often, internal stakeholders will ask the question “If we do everything on this roadmap, will we be at our target state?” This diagram will help answer that question.

      A screenshot image showing the 'Expected Security Roadmap Progression' with sample data in it. Part of the 'Results' tab of the 'Information Security Gap Analysis Tool.'

      3.4.4 Review your cost/effort estimates table

      Estimated Time: 30 minutes

      1. Once you have completed your roadmap, review the total cost/effort estimates. This can be found in a table on the Results tab. This table will provide initial and ongoing costs and staffing requirements for each wave. This also includes the total three-year investment. In your review consider:
        • Is this investment realistic? Will completion of your roadmap require adding more staff or funding than you otherwise expected?
        • If the investment seems unrealistic, you may need to revisit some of your assumptions, potentially reducing target levels or increasing the amount of time to complete the strategy.
        • This table provides you with the information to have important conversations with management and stakeholders
      2. When you have completed your review, copy the table into the Information Security Strategy Communication Deck.

      A screenshot image showing the 'Information Security Roadmap Cost/Effort Estimates,' part of the 'Results' tab of the 'Information Security Gap Analysis Tool.'

      Phase 4

      Execute and Maintain

      Phase 1

      • 1.1 Define goals & scope
      • 1.2 Assess risks
      • 1.3 Determine pressures
      • 1.4 Determine risk tolerance
      • 1.5 Establish target state

      Phase 2

      • 2.1 Review Info-Tech’s security framework
      • 2.2 Assess your current state
      • 2.3 Identify gap closure actions

      Phase 3

      • 3.1 Define tasks & initiatives
      • 3.2 Perform cost/benefit analysis
      • 3.3 Prioritize initiatives
      • 3.4 Build roadmap

      Phase 4

      • 4.1 Build communication deck
      • 4.2 Develop a security charter
      • 4.3 Execute on your roadmap

      This phase will walk you through the following activities:

      • 4.1 Build your security strategy communication deck.
      • 4.2 Develop a security charter.
      • 4.3 Execute on your roadmap.

      4.1 Build your communication deck

      Estimated Time: 1-3 hours

      1. As a group, review the Information Security Strategy Communication Deck.
      2. Follow the instructions within the template and on the next few slides to customize the template with the results of your strategic roadmap planning.

      Input

      • Completed Security Requirements Gathering Tool
      • Completed Security Pressure Analysis Tool
      • Completed Security Gap Analysis Tool

      Output

      • Information Security Strategy Communication Deck

      Materials

      • Information Security Strategy Communication Deck

      Participants

      • Security Team
      • IT Leadership

      Download the Information Security Gap Analysis Tool

      4.1.1 Customize the Communication Deck

      Estimated Time: 1-2 hours

      1. When reviewing the Information Security Strategy Communication Deck, you will find slides that contain instructions within green text boxes. Follow the instructions within the boxes, then delete the boxes.
        • Most slides only require that you copy and paste screenshots or tables from your tools into the slides.
        • However, some slides require that you customize or add text explanations that need to reflect your unique organization.
        • It is recommended that you pay attention to the Next Steps slide at the end of the deck. This will likely have a large impact on your audience.
      2. Once you have customized the existing slides, you may wish to add additional slides. For instance, you may wish to add more context to the risk assessment or pressure analysis diagrams or provide details on high-priority initiatives.

      An image showing the 'Business Goals Cascade,' part of the 'Information Security Strategy Communication Deck.' A green box on top of the screenshot instructs you to 'Paste your goals cascade from the Information Security Requirements Gathering Tool here.'

      Consider developing multiple versions of the deck for different audiences. Senior management may only want an executive summary, whereas the CIO may be more interested in the methodology used to develop the strategy.

      Communication considerations

      Developing an information security strategy is only half the job. For the strategy to be successful, you will need to garner support from key internal stakeholders. These may include the CIO, senior executives, and business leaders. Without their support, your strategy may never get the traction it needs. When building your communication deck and planning to present to these stakeholders, consider the following:

      • Gaining support from stakeholders requires understanding their needs. Before presenting to a new audience, carefully consider their priorities and tailor your presentation to address them.
      • Use the communication deck to clarify the business context and how your initiatives that will support business goals.
      • When presenting to senior stakeholders, anticipate what questions they might ask and be sure to prepare answers in advance. Always be prepared to speak to any data point within the deck.
      • If you are going to present your strategy to a group and you anticipate that one or more members of that group may be antagonistic, seek out an opportunity to speak to them before the meeting and address their concerns one on one.

      If you have already fully engaged your key stakeholders through the requirements gathering exercises, presenting the strategy will be significantly easier. The stakeholders will have already bought in to the business goals, allowing you to show how the security strategy supports those goals.

      Info-Tech Insight

      Reinforce the concept that a security strategy is an effort to enable the organization to achieve its core mission and goals and to protect the business only to the degree that the business demands. It is important that stakeholders understand this point.

      4.2 Develop a security charter

      Estimated Time: 1-3 hours

      1. As a group, review the Information Security Charter.
      2. Customize the template as required to reflect your information security program. It may include elements such as:
        • A mission and vision statement for information security in your organization
        • The objectives and scope of the security program
        • A description of the security principles upon which your program is built
        • High-level roles and responsibilities for information security within the organization

      Input

      • Completed Security Requirements Gathering Tool
      • Completed Security Pressure Analysis Tool
      • Completed Security Gap Analysis Tool

      Output

      • Information security charter

      Materials

      • Information Security Charter

      Participants

      • Security Team

      Download the Information Security Gap Analysis Tool

      4.2.1 Customize the Information Security Charter

      Estimated Time: 1-3 hours

      1. Involve the stakeholders that were present during Phase 1 activities to allow you to build a charter that is truly reflective of your organization.
      2. The purpose of the security charter is too:
        • Establish a mandate for information security within the organization.
        • Communicate executive commitment to risk and information security management.
        • Outline high-level responsibilities for information security within the organization.
        • Establish awareness of information security within the organization.

      A screenshot of the introduction of the 'Information Security Charter' template.

      A security charter is a formalized and defined way to document the scope and purpose of your security program. It will define security governance and allow it to operate efficiently through your mission and vision.

      4.3 Execute on your roadmap

      1. Executing on your information security roadmap will require coordinated effort by multiple teams within your organization. To ensure success, consider the following recommendations:
        1. If you have a project management office, leverage them to help apply formal project management methodologies to your initiatives.
        2. Develop a process to track the tasks on your strategy task list. Because these will not be managed as formal initiatives, it will be easy to lose track of them.
        3. Develop a schedule for regular reporting of progress on the roadmap to senior management. This will help hold yourself and others accountable for moving the project forward.
      2. Plan to review and update the strategy and roadmap on a regular basis. You may need to add, change, or remove initiatives as priorities shift.

      Input

      • Completed Security Gap Analysis Tool

      Output

      • Execution of your strategy and roadmap

      Materials

      • Information Security Gap Analysis Tool
      • Project management tools as required

      Participants

      • Security Team
      • Project Management Office
      • IT and Corporate Teams, as required

      Info-Tech Insight

      Info-Tech has many resources that can help you quickly and effectively implement most of your initiatives. Talk to your account manager to learn more about how we can help your strategy succeed.

      Summary of Accomplishment

      Knowledge Gained

      • Knowledge of organizational pressures and the drivers behind them
      • Insight into stakeholder goals and obligations
      • A defined security risk tolerance information and baseline
      • Comprehensive knowledge of security current state and summary initiatives required to achieve security objectives

      Deliverables Completed

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech workshop.

      Contact your account representative for more information.

      workshops@infotech.com
      1-888-670-8889

      Additional Support

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech workshop.

      To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.

      Info-Tech analysts will join you and your team at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      Information Security Program Gap Analysis Tool

      Use our best-of-breed security framework to perform a gap analysis between your current and target states.

      Information Security Requirements Gathering Tool

      Define the business, customer, and compliance alignment for your security program.

      Related Info-Tech Research

      Develop a Security Operations Strategy

      A unified security operations process actively transforms security events and threat information into actionable intelligence, driving security prevention, detection, analysis, and response processes, addressing the increasing sophistication of cyberthreats, and guiding continuous improvement.

      This blueprint will walk through the steps of developing a flexible and systematic security operations program relevant to your organization.

      Implement a Security Governance and Management Program

      Your security governance and management program needs to be aligned with business goals to be effective.

      This approach also helps to provide a starting point to develop a realistic governance and management program.

      This project will guide you through the process of implementing and monitoring a security governance and management program that prioritizes security while keeping costs to a minimum.

      Align Your Security Controls to Industry Frameworks for Compliance

      Don’t reinvent the wheel by reassessing your security program using a new framework.

      Instead, use the tools in this blueprint to align your current assessment outcomes to required standards.

      Bibliography

      “2015 Cost of Data Breach Study: United States.” Sponsored by IBM. Ponemon Institute, May 2015. Web.

      “2016 Cost of Cyber Crime Study & the Risk of Business Innovation.” Ponemon Institute, Oct. 2016. Web. 25 Oct. 2016.

      “2016 Cost of Data Breach Study: Global Analysis.” Ponemon Institute, June 2016. Web. 26 Oct. 2016.

      “2016 Data Breach Investigations Report.” Verizon, 2016. Web. 25 Oct. 2016.

      “2016 NowSecure Mobile Security Report.” NowSecure, 2016. Web. 5 Nov. 2016.

      “2017 Cost of Cyber Crime Study.” Ponemon Institute, Oct. 2017. Web.

      “2018 Cost of Data Breach Study: Global Overview.” Ponemon Institute, July 2018. Web.

      “2018 Data Breach Investigations Report.” Verizon, 2018. Web. Oct. 2019.

      “2018 Global State of Information Security Survey.” CSO, 2017. Web.

      “2018 Thales Data Threat Report.” Thales eSecurity, 2018. Web.

      “2019 Data Breach Investigations Report.” Verizon, 2020. Web. Feb. 2020.

      “2019 Global Cost of a Data Breach Study.” Ponemon Institute, Feb. 2020. Web.

      “2019 The Cost of Cyber Crime Study.” Accenture, 2019. Web Jan 2020.

      “2020 Thales Data Threat Report Global Edition.” Thales eSecurity, 2020. Web. Mar. 2020.

      Ben Salem, Malek. “The Cyber Security Leap: From Laggard to Leader.” Accenture, 2015. Web. 20 Oct. 2016.

      “Cisco 2017 Annual Cybersecurity Report.” Cisco, Jan. 2017. Web. 3 Jan. 2017.

      “Cyber Attack – How Much Will You Lose?” Hewlett Packard Enterprise, Oct. 2016. Web. 3 Jan. 2017.

      “Cyber Crime – A Risk You Can Manage.” Hewlett Packard Enterprise, 2016. Web. 3 Jan. 2017.

      “Global IT Security Risks Survey.” Kaspersky Lab, 2015. Web. 20 October 2016.

      “How Much Is the Data on Your Mobile Device Worth?” Ponemon Institute, Jan. 2016. Web. 25 Oct. 2016.

      “Insider Threat 2018 Report.” CA Technologies, 2018. Web.

      “Kaspersky Lab Announces the First 2016 Consumer Cybersecurity Index.” Press Release. Kaspersky Lab, 8 Sept. 2016. Web. 3 Jan. 2017.

      “Kaspersky Lab Survey Reveals: Cyberattacks Now Cost Large Businesses an Average of $861,000.” Press Release. Kaspersky Lab, 13 Sept. 2016. Web. 20 Oct. 2016.

      “Kaspersky Security Bulletin 2016.” Kaspersky Lab, 2016. Web. 25 Oct. 2016.

      “Managing Cyber Risks in an Interconnected World: Key Findings From the Global State of Information Security Survey 2015.” PwC, 30 Sept. 2014. Web.

      “Measuring Financial Impact of IT Security on Business.” Kaspersky Lab, 2016. Web. 25 Oct. 2016.

      “Ponemon Institute Releases New Study on How Organizations Can Leapfrog to a Stronger Cyber Security Posture.” Ponemon Institute, 10 Apr. 2015. Web. 20 Oct. 2016.

      “Predictions for 2017: ‘Indicators of Compromise’ Are Dead.” Kaspersky Lab, 2016. Web. 4 Jan. 2017.

      “Take a Security Leap Forward.” Accenture, 2015. Web. 20 Oct. 2016.

      “Trends 2016: (In)security Everywhere.” ESET Research Laboratories, 2016. Web. 25 Oct. 2016.

      Research Contributors

      • Peter Clay, Zeneth Tech Partners, Principal
      • Ken Towne, Zeneth Tech Partners, Security Architect
      • Luciano Siqueria, Road Track, IT Security Manager
      • David Rahbany, The Hain Celestial Group, Director IT Infrastructure
      • Rick Vadgama, Cimpress, Head of Information Privacy and Security
      • Doug Salah, Wabtec Corp, Manager of Information Security and IT Audit
      • Peter Odegard, Children’s Hospitals and Clinics, Information Security Officer
      • Trevor Butler, City of Lethbridge, Information Technology General Manager
      • Shane Callahan, Tractor Supply, Director of Information Security
      • Jeff Zalusky, Chrysalis, President/CEO
      • Candy Alexander, Independent Consultant, Cybersecurity and Information Security Executive
      • Dan Humbert, YMCA of Central Florida, Director of Information Technology
      • Ron Kirkland, Crawford & Co, Manager ICT Security & Customer Service
      • Jason Bevis – FireEye, Senior Director Orchestration Product Management - Office of the CTO
      • Joan Middleton, Village of Mount Prospect, IT Director
      • Jim Burns, Great America Financial Services, Vice President Information Technology
      • Ryan Breed, Hudson’s Bay, Information Security Analyst
      • James Fielder, Farm Credit Services – Central Illinois, Vice President of Information Systems

      Build Your BizDevOps Playbook

      • Buy Link or Shortcode: {j2store}177|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Architecture & Strategy
      • Parent Category Link: /architecture-and-strategy
      • Today’s rapidly scaling and increasingly complex products create mounting pressure on delivery teams to release new features and changes quickly and with sufficient quality.
      • Many organizations see BizDevOps as a solution to help meet this demand. However, they often lack the critical cross-functional collaboration and team-sport culture that are critical for success.
      • The industry provides little consensus and guidance on how to prepare for the transition to BizDevOps.

      Our Advice

      Critical Insight

      • BizDevOps is cultural, not driven by tools. It is about delivering high-quality and valuable releases to stakeholders through collective ownership, continuous collaboration, and team-first behaviors supported by tools.
      • BizDevOps begins with a strong foundation in five key areas. The crux of successful BizDevOps is centered on the strategic adoption and optimization of building great requirements, collaborative practices, iterative delivery, application management, and high-fidelity environments.
      • Teams take STOCK of what it takes to collaborate effectively. Teams and stakeholders must show up, trust the delivery method and people, orchestrate facilitated activities, clearly communicate and knowledge share every time they collaborate.

      Impact and Result

      • Bring the right people to the table. BizDevOps brings significant organizational, process and technology changes to improve delivery effectiveness. Include the key roles in the definition and validation of your BizDevOps vision and practices.
      • Focus on the areas that matter. Review your current circumstances and incorporate the right practices that addresses your key challenges and blockers to becoming BizDevOps.
      • Build your BizDevOps playbook. Gain a broad understanding of the key plays and practices that makes a successful BizDevOps organization. Verify and validate these practices in order to tailor them to your context. Keep your playbook live.

      Build Your BizDevOps Playbook Research & Tools

      Start here – read the Executive Brief

      Find out why you should implement BizDevOps, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Get started with BizDevOps

      Set the right expectations with your stakeholders and define the context of your BizDevOps implementation.

      • Build Your BizDevOps Playbook – Phase 1: Get Started With BizDevOps
      • BizDevOps Playbook

      2. Tailor your BizDevOps playbook

      Tailor the plays in your BizDevOps playbook to your circumstances and vision.

      • Build Your BizDevOps Playbook – Phase 2: Tailor Your BizDevOps Playbook
      [infographic]

      Workshop: Build Your BizDevOps Playbook

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Set Your Expectations

      The Purpose

      Discuss the goals of your BizDevOps playbook.

      Identify the various perspectives who should be included in the BizDevOps discussion.

      Level set expectations of your BizDevOps implementation.

      Key Benefits Achieved

      Identification of the key roles who should be included in the BizDevOps discussion.

      Learning of key practices to support your BizDevOps vision and goals.

      Your vision of BizDevOps in your organization.

      Activities

      1.1 Define BizDevOps.

      1.2 Understand your key stakeholders.

      1.3 Define your objectives.

      Outputs

      Your BizDevOps definition

      List of BizDevOps stakeholders

      BizDevOps vision and objectives

      2 Set the Context

      The Purpose

      Understand the various methods to initiate the structuring of facilitated collaboration.

      Share a common way of thinking and behaving with a set of principles.

      Focus BizDevOps adoption on key areas of software product delivery.

      Key Benefits Achieved

      A chosen collaboration method (Scrum, Kanban, Scrumban) to facilitate collaboration

      A mutually understanding and beneficial set of guiding principles

      Areas where BizDevOps will see the most benefit

      Activities

      2.1 Select your foundation method.

      2.2 Define your guiding principles.

      2.3 Focus on the areas that matter.

      Outputs

      Chosen collaboration model

      List of guiding principles

      High-level assessment of delivery practices and its fit for BizDevOps

      3 Tailor Your BizDevOps Playbook

      The Purpose

      Review the good practices within Info-Tech’s BizDevOps Playbook.

      Tailor your playbook to reflect your circumstances.

      Key Benefits Achieved

      Understanding of the key plays involved in product delivery

      Product delivery plays that reflect the challenges and opportunities of your organization and support your BizDevOps vision

      Activities

      3.1 Review and tailor the plays in your playbook

      Outputs

      High-level discussion of key product delivery plays and its optimization to support BizDevOps

      Secure Operations in High-Risk Jurisdictions

      • Buy Link or Shortcode: {j2store}369|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Security Strategy & Budgeting
      • Parent Category Link: /security-strategy-and-budgeting

      Business operations in high-risk areas of the world contend with complex threat environments and risk scenarios that often require a unique response. But traditional approaches to security strategy often miss these jurisdictional risks, leaving organizations vulnerable to threats that range from cybercrime and data breaches to fines and penalties.

      Security leaders need to identify high-risk jurisdictions, inventory critical assets, identify vulnerabilities, assess risks, and identify security controls necessary to mitigate those risks.

      Secure operations and protect critical assets in high-risk regions

      Across risks that include insider threats and commercial surveillance, the two greatest vulnerabilities that organizations face in high-risk parts of the world are travel and compliance. Organizations can make small adjustments to their security program to address these risks:

      1. Support high-risk travel: Put measures and guidelines in place to protect personnel, data, and devices before, during, and after employee travel.
      2. Mitigate compliance risk: Consider data residency requirements, data breach notification, cross-border data transfer, and third-party risks to support business growth.

      Using these two prevalent risk scenarios in high-risk jurisdictions as examples, this research walks you through the steps to analyze the threat landscape, assess security risks, and execute a response to mitigate them.

      Secure Operations in High-Risk Jurisdictions Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Secure Operations in High-Risk Jurisdictions – A step-by-step approach to mitigating jurisdictional security and privacy risks.

      Traditional approaches to security strategy often miss jurisdictional risks. Use this storyboard to make small adjustments to your security program to mitigate security risks in high-risk jurisdictions.

      • Secure Operations in High-Risk Jurisdictions – Phases 1-3

      2. Jurisdictional Risk Register and Heat Map Tool – A tool to inventory, assess, and treat jurisdictional risks.

      Use this tool to track jurisdictional risks, assess the exposure of critical assets, and identify mitigation controls. Use the geographic heatmap to communicate inherent jurisdictional risk with key stakeholders.

      • Jurisdictional Risk Register and Heat Map Tool

      3. Guidelines for Key Jurisdictional Risk Scenarios – Two structured templates to help you develop guidelines for two key jurisdictional risk scenarios: high-risk travel and compliance risk

      Use these two templates to develop help you develop your own guidelines for key jurisdictional risk scenarios. The guidelines address high-risk travel and compliance risk.

      • Digital Safety Guidelines for International Travel
      • Guidelines for Compliance With Local Security and Privacy Laws Template

      Infographic

      Workshop: Secure Operations in High-Risk Jurisdictions

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Identify Context for Risk Assessment

      The Purpose

      Assess business requirements and evaluate security pressures to set the context for the security risk assessment.

      Key Benefits Achieved

      Understand the goals of the organization in high-risk jurisdictions.

      Assess the threats to critical assets in these jurisdictions and capture stakeholder expectations for information security.

      Activities

      1.1 Determine assessment scope.

      1.2 Determine business goals.

      1.3 Determine compliance obligations.

      1.4 Determine risk appetite.

      1.5 Conduct pressure analysis.

      Outputs

      Business requirements

      Security pressure analysis

      2 Analyze Key Risk Scenarios for High-Risk Jurisdictions

      The Purpose

      Build key risk scenarios for high-risk jurisdictions.

      Key Benefits Achieved

      Identify critical assets in high-risk jurisdictions, their vulnerabilities to relevant threats, and the adverse impact should malicious agents exploit them.

      Assess risk exposure of critical assets in high-risk jurisdictions.

      Activities

      2.1 Identify critical assets.

      2.2 Identify threats.

      2.3 Assess risk likelihood.

      2.4 Assess risk impact.

      Outputs

      Key risk scenarios

      Jurisdictional risk exposure

      Jurisdictional Risk Register and Heat Map

      3 Build Risk Treatment Roadmap

      The Purpose

      Prioritize and treat jurisdictional risks to critical assets.

      Key Benefits Achieved

      Build an initiative roadmap to reduce residual risks in high-risk jurisdictions.

      Activities

      3.1 Identify and assess risk response.

      3.2 Assess residual risks.

      3.3 Identify security controls.

      3.4 Build initiative roadmap.

      Outputs

      Action plan to mitigate key risk scenarios

      Further reading

      Secure Operations in High-Risk Jurisdictions

      Assessments often omit jurisdictional risks. Are your assets exposed?

      EXECUTIVE BRIEF

      Analyst Perspective

      Operations in high-risk jurisdictions face unique security scenarios.

      The image contains a picture of Michel Hebert.

      Michel Hébert

      Research Director

      Security and Privacy

      Info-Tech Research Group


      The image contains a picture of Alan Tang.

      Alan Tang

      Principal Research Director

      Security and Privacy

      Info-Tech Research Group


      Traditional approaches to security strategies may miss key risk scenarios that critical assets face in high-risk jurisdictions. These include high-risk travel, heightened insider threats, advanced persistent threats, and complex compliance environments. Most organizations have security strategies and risk management practices in place, but securing global operations requires its own effort. Assess the security risk that global operations pose to critical assets. Consider the unique assets, threats, and vulnerabilities that come with operations in high-risk jurisdictions. Focus on the business activities you support and integrate your insights with existing risk management practices to ensure the controls you propose get the visibility they need. Your goal is to build a plan that mitigates the unique security risks that global operations pose and secures critical assets in high-risk areas. Don’t leave security to chance.

      Executive Summary

      Your Challenge

      • Security leaders who support operations in many countries struggle to mitigate security risks to critical assets. Operations in high-risk jurisdictions contend with complex threat environments and security risk scenarios that often require a unique response.
      • Security leaders need to identify critical assets, assess vulnerabilities, catalog threats, and identify the security controls necessary to mitigate related operational risks.

      Common Obstacles

      • Securing operations in high-risk jurisdictions requires additional due diligence. Each jurisdiction involves a different risk context, which complicates efforts to identify, assess, and mitigate security risks to critical assets.
      • Security leaders need to engage the organization with the right questions and identify high-risk vulnerabilities and security risk scenarios to help stakeholders make an informed decision about how to assess and treat the security risks they face in high-risk jurisdictions.

      Info-Tech’s Approach

      Info-Tech has developed an effective approach to protecting critical assets in high-risk jurisdictions.

      This approach includes tools for:

      • Evaluating the security context of your organization’s high-risk jurisdictions.
      • Identifying security risk scenarios unique to high-risk jurisdictions and assessing the exposure of critical assets.
      • Planning and executing a response.

      Info-Tech Insight

      Organizations with global operations must contend with a more diverse set of assets, threats, and vulnerabilities when they operate in high-risk jurisdictions. Security leaders need to take additional steps to secure operations and protect critical assets.

      Business operations in high-risk jurisdictions face a more complex security landscape

      Information security risks to business operations vary widely by region.

      The 2022 Allianz Risk Barometer surveyed 2,650 business risk specialists in 89 countries to identify the most important risks to operations. The report identified cybercrime, IT failures, outages, data breaches, fines, and penalties as the most important global business risks in 2022, but their results varied widely by region. The standout finding of the 2022 Allianz Risk Barometer is the return of security risks as the most important threat to business operations. Security risks will continue to be acute beyond 2022, especially in Africa, the Middle East, Europe, and the Asia-Pacific region, where they will dwarf risks of supply chain interruptions, natural catastrophe, and climate change.

      Global operations in high-risk jurisdictions contend with more diverse threats. These security risk scenarios are not captured in traditional security strategies.

      The image contains a picture of the world map that has certain areas of the map highlighted in various shades of blue based on higher security-related business risks.

      Figures represent the number of cybersecurity risks business risk specialists selected as a percentage of all business risks (Allianz, 2022). Higher scores indicate jurisdictions with higher security-related business risks. Jurisdictions without data are in grey.

      Different jurisdictions’ commitment to cybersecurity also varies widely, which increases security risks further

      The Global Cybersecurity Index (GCI) provides insight into the commitment of different countries to cybersecurity.

      The index assesses a country’s legal framework to identify basic requirements that public and private stakeholders must uphold and the legal instruments prohibiting harmful actions.

      The 2020 GCI results show overall improvement and strengthening of the cybersecurity agenda globally, but significant regional gaps persist. Of the 194 countries surveyed:

      • 33% had no data protection legislation.
      • 47% had no breach notification measures in place.
      • 50% had no legislation on the theft of personal information.
      • 19% still had no legislation on illegal access.

      Not every jurisdiction has the same commitment to cybersecurity. Protecting critical assets in high-risk jurisdictions requires additional due diligence.

      The image contains a picture of the world map that has certain areas of the map highlighted in various shades of blue based on scores in relation to the Global Security Index.

      The diagram sets out the score and rank for each country that took part in the Global Cybersecurity Index (ITU, 2021)

      Higher scores show jurisdictions with a lower rank on the CGI, which implies greater risk. Jurisdictions without data are in grey.

      Securing critical assets in high-risk jurisdictions requires additional effort

      Traditional approaches to security strategy may miss these key risk scenarios.

      As a result, security leaders who support operations in many countries need to take additional steps to mitigate security risks to critical assets.

      Guide stakeholders to make informed decisions about how to assess and treat the security risks and secure operations.

      • Engage the organization with the right questions.
      • Identify critical assets and assess vulnerabilities.
      • Catalogue threats and build risk scenarios.
      • Identify the security controls necessary to mitigate risks.

      Work with your organization to analyze the threat landscape, assess security risks unique to high-risk jurisdictions, and execute a response to mitigate them.

      This project blueprint works through this process using the two most prevalent risk scenarios in high-risk jurisdictions: high-risk travel and compliance risk.

      Key Risk Scenarios

      • High-Risk Travel
      • Compliance Risk
      • Insider Threat
      • Advanced Persistent Threat
      • Commercial Surveillance
      The image contains a screenshot of an Info-Tech thought model regarding secure global operations in high-risk jurisdictions.

      Travel risk is the first scenario we use as an example throughout the blueprint

      • This project blueprint outlines a process to identify, assess, and mitigate key risk scenarios in high-risk jurisdictions. We use two common key risk scenarios as examples throughout the deck to illustrate how you create and assess your own scenarios.
      • Supporting high-risk travel is the first scenario we will study in-depth as an example. Business growth, service delivery, and mergers and acquisitions can lead end users to travel to high-risk jurisdictions where staff, devices, and data are at risk.
      • Compromised or stolen devices can provide threat actors with access to data that could compromise the organization’s strategic, economic, or competitive advantage or expose the organization to regulatory risk.

      The project blueprint includes template guidance in Phase 3 to help you build and deploy your own travel guidelines to protect critical assets and support end users before they leave, during their trip, and when they return.

      Before you leave

      • Identify high-risk countries.
      • Enable controls.
      • Limit what you pack.

      During your trip

      • Assume you are monitored.
      • Limit access to systems.
      • Prevent theft.

      When you return

      • Change your password.
      • Restore your devices.

      Compliance risk is the second scenario we use as an example

      • Mitigating compliance risk is the second scenario we will study as an example in this blueprint. The legal and regulatory landscape is evolving rapidly to keep step with the pace of technological change. Security and privacy leaders are expected to mitigate the risk of noncompliance as the organization expands to new jurisdictions.
      • Later sections will show how to think through at least four compliance risks, including:
        • Cross-border data transfer
        • Third-party risk management
        • Data breach notification
        • Data residency

      The project blueprint includes template guidance in Phase 3 to help you deploy your own compliance governance controls as a risk mitigation measure.

      Secure Operations in High-Risk Jurisdictions: Info-Tech’s methodology

      1. Identify Context

      2. Assess Risks

      3. Execute Response

      Phase Steps

      1. Assess business requirements
      2. Evaluate security pressures
      1. Identify risks
      2. Assess risk exposure
      1. Treat security risks
      2. Build initiative roadmap

      Phase Outcomes

      • Internal security pressures that capture the governance, policies, practices, and risk tolerance of the organization
      • External security pressures that capture the expectations of customers, regulators, legislators, and business partners
      • A heatmap that captures not only the global exposure of your critical assets but also the business processes they support
      • A security risk register to allow for the easy transfer of critical assets’ global security risk data to your organization’s enterprise risk management practice
      • A roadmap of prioritized initiatives to apply relevant controls and secure global assets
      • A set of key risk indicators to monitor and report your progress

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

      Business Security Requirements

      Identify the context for the global security risk assessment, including risk appetite and risk tolerance.

      Jurisdictional Risk Register and Heatmap

      Identify critical global assets and the threats they face in high-risk jurisdictions and assess exposure.

      Mitigation Plan

      Roadmap of initiatives and security controls to mitigate global risks to critical assets. Tools and templates to address key security risk scenarios.

      Key deliverable:

      Jurisdictional Risk Register and Heatmap

      Use the Jurisdictional Risk Register and Heatmap Tool to capture information security risks to critical assets in high-risk jurisdictions. The tool generates a world chart that illustrates the risks global operations face to help you engage the business and execute a response.

      Blueprint benefits

      Protect critical assets in high-risk jurisdictions

      IT Benefits

      Assess and remediate information security risk to critical assets in high-risk jurisdictions.

      Easily integrate your risk assessment with enterprise risk assessments to improve communication with the business.

      Illustrate key information security risk scenarios to make the case for action in terms the business understands.

      Business Benefits

      Develop mitigation plans to protect staff, devices, and data in high-risk jurisdictions.

      Support business growth in high-risk jurisdictions without compromising critical assets.

      Mitigate compliance risk to protect your organization’s reputation, avoid fines, and ensure business continuity.

      Quantify the impact of securing global operations

      The tool included with this blueprint can help you measure the impact of implementing the research

      • Use the Jurisdictional Risk Register and Heatmap Tool to describe the key risk scenarios you face, assess their likelihood and impact, and estimate the cost of mitigating measures. Working through the project in this way will help you quantify the impact of securing global operations.
      The image contains a screenshot of Info-Tech's Jurisdictional Risk Register and Heatmap Tool. The image contains a screenshot of the High-Risk Travel Jurisdiction.

      Establish Baseline Metrics

      • Review existing information security and risk management metrics and the output of the tools included with the blueprint.
      • Identify metrics to measure the impact of your risk management efforts. Focus specifically on high-risk jurisdictions.
      • Compare your results with those in your overall security and risk management program.

      ID

      Metric

      Why is this metric valuable?

      How do I calculate it?

      1.

      Overall Exposure – High-Risk Jurisdictions

      Illustrates the overall exposure of critical assets in high-risk jurisdictions.

      Use the Jurisdictional Risk Register and Heatmap Tool. Calculate the impact times the probability rating for each risk. Take the average.

      2.

      # Risks Identified – High-Risk Jurisdictions

      Informs risk tolerance assessments.

      Use the Jurisdictional Risk Register and Heatmap Tool.

      3.

      # Risks Treated – High-Risk Jurisdictions

      Informs residual risk assessments.

      Use the Jurisdictional Risk Register and Heatmap Tool.

      4.

      Mitigation Cost – High-Risk Jurisdictions

      Informs cost-benefit analysis to determine program effectiveness.

      Use the Jurisdictional Risk Register and Heatmap Tool.

      5.

      # Security Incidents – High-Risk Jurisdictions

      Informs incident trend calculations to determine program effectiveness.

      Draw the information from your service desk or IT service management tool.

      6.

      Incident Remediation Cost – High-Risk Jurisdictions

      Informs cost-benefit analysis to determine program effectiveness.

      Estimate based on cost and effort, including direct and indirect cost such as business disruptions, administrative finds, reputational damage, etc.

      7.

      TRENDS: Program Effectiveness – High-Risk Jurisdictions

      # of security incidents over time. Remediation : Mitigation costs over time

      Calculate based on metrics 5 to 7.

      Info-Tech offers various levels of support to best suit your needs.

      DIY Toolkit

      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful."

      Guided Implementation

      "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track."

      Workshop

      "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place."

      Consulting

      "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks are used throughout all four options.

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1

      Call #1: Scope project requirements, determine assessment scope, and discuss challenges.

      Phase 2

      Call #2: Conduct initial risk assessment and determine risk tolerance.

      Call #3: Evaluate security pressures in high-risk jurisdictions.

      Call #4: Identify risks in high-risk jurisdictions.

      Call #5: Assess risk exposure.

      Phase 3

      Call #6: Treat security risks in high-risk jurisdictions.

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization. A typical GI is between 8 to 12 calls over the course of 4 to 6 months.

      Workshop Overview

      Contact your account representative for more information. workshops@infotech.com 1-888-670-8889

      Days 1

      Days 2-3

      Day 4

      Day 5

      Identify Context

      Key Risk Scenarios

      Build Roadmap

      Next Steps and Wrap-Up (offsite)

      Activities

      1.1.1 Determine assessment scope.

      1.1.2 Determine business goals.

      1.1.3 Identify compliance obligations.

      1.2.1 Determine risk appetite.

      1.2.2 Conduct pressure analysis.

      2.1.1 Identify assets.

      2.1.2 Identify threats.

      2.2.1 Assess risk likelihood.

      2.2.2 Assess risk impact.

      3.1.1 Identify and assess risk response.

      3.1.2 Assess residual risks.

      3.2.1 Identify security controls.

      3.2.2 Build initiative roadmap.

      5.1 Complete in-progress deliverables from previous four days.

      5.2 Set up review time for workshop deliverables and to discuss next steps.

      Deliverables

      1. Business requirements for security risk assessment
      2. Identification of high-risk jurisdictions
      3. Security threat landscape for high-risk jurisdictions
      1. Inventory of relevant threats, critical assets, and their vulnerabilities
      2. Assessment of adverse effects should threat agents exploit vulnerabilities
      3. Risk register with key risk scenarios and heatmap of high-risk jurisdictions
      1. Action plan to mitigate key risk scenarios
      2. Investment and implementation roadmap
      1. Completed information security risk assessment for two key risk scenarios
      2. Risk mitigation roadmap

      No safe jurisdictions

      Stakeholders sometimes ask information security and privacy leaders to produce a list of safe jurisdictions from which to operate. We need to help them see that there are no safe jurisdictions, only relatively risky ones. As you build your security program, deepen the scope of your risk assessments to include risk scenarios critical assets face in different jurisdictions. These risks do not need to rule out operations, but they may require additional mitigation measures to keep staff, data, and devices safe and reduce potential reputational harms.

      Traditional approaches to security strategy often omit jurisdictional risks.

      Global operations must contend with a more complex security landscape. Secure critical assets in high-risk jurisdictions with a targeted risk assessment.

      The two greatest risks are high-risk travel and compliance risk.

      You can mitigate them with small adjustments to your security program.

      Support High-Risk Travel

      When securing travel to high-risk jurisdictions, you must consider personnel safety as well as data and device security. Put measures and guidelines in place to protect them before, during, and after travel.

      Mitigate Compliance Risk

      Think through data residency requirements, data breach notification, cross-border data transfer, and third-party risks to support business growth and mitigate compliance risks in high-risk jurisdictions to protect your organization’s reputation and avoid hefty fines or business disruptions.

      Phase 1

      Identify Context

      This phase will walk you through the following activities:

      • Assess business requirements to understand the goals of the organization’s global operations, as well as its risk governance, policies, and practices.
      • Evaluate jurisdictional security pressures to understand threats to critical assets and capture the expectations of external stakeholders, including customers, regulators, legislators, and business partners, and assess risk tolerance.

      This phase involves the following participants:

      • Business stakeholders
      • IT leadership
      • Security team
      • Risk and Compliance

      Step 1.1

      Assess Business Requirements

      Activities

      1.1.1 Determine assessment scope

      1.1.2 Identify enterprise goals in high-risk jurisdictions

      1.1.3 Identify compliance obligations

      This step involves the following participants:

      • Business stakeholders
      • IT leadership
      • Security team
      • Risk and Compliance

      Outcomes of this step

      • Assess business requirements to understand the goals of the organization’s global operations, as well as its risk governance, policies, and practices.

      Focus the risk assessment on high-risk jurisdictions

      Traditional approaches to information security strategy often miss threats to global operations

      • Successful security strategies are typically sensitive to risks to different IT systems and lines of business.
      • However, securing global operations requires additional focus on high-risk jurisdictions, considering what makes them unique.
      • This first phase of the project will help you evaluate the business context of operations in high-risk jurisdictions, including:
        • Enterprise and security goals.
        • Lines of business, physical locations, and IT systems that need additional oversight.
        • Unique compliance obligations.
        • Unique risks and security pressures.
        • Organizational risk tolerance in high-risk jurisdictions.

      Focus your risk assessment on the business activities security supports in high-risk jurisdictions and the unique threats they face to bridge gaps in your security strategy.

      Identify jurisdictions with higher inherent risks

      Your security strategy may not describe jurisdictional risk adequately.

      • Security strategies list lines of business, physical locations, and IT systems the organization needs to secure and those whose security will depend on a third-party. You can find additional guidance on fixing the scope and boundaries of a security strategy in Phase 1 of Build an Information Security Strategy.
      • However, security risks vary widely from one jurisdiction to another according to:
        • Active cyber threats.
        • Legal and regulatory frameworks.
        • Regional security and preparedness capabilities.
      • Your first task is to identify high-risk jurisdictions to target for additional oversight.

      Work closely with your enterprise risk management function.

      Enterprise risk management functions are often tasked with developing risk assessments from composite sources. Work closely with them to complete your own assessment.

      Countries at heightened risk of money laundering and terrorism financing are examples of high-risk jurisdictions. The Financial Action Task Force and the U.S. Treasury publish reports three times a year that identify Non-Cooperative Countries or Territories.

      Develop a robust jurisdictional assessment

      Design an intelligence collection strategy to inform your assessment

      Strategic Intelligence

      White papers, briefings, reports. Audience: C-Suite, board members

      Tactical Intelligence

      Internal reports, vendor reports. Audience: Security leaders

      Operational intelligence

      Indicators of compromise. Audience: IT Operations

      Operational intelligence focuses on machine-readable data used to block attacks, triage and validate alerts, and eliminate threats from the network. It becomes outdated in a matter of hours and is less useful for this exercise.

      Determine travel risks to bolster your assessments

      Not all locations and journeys will require the same security measures.

      • Travel risks vary significantly according to destination, the nature of the trip, and traveler profile.
      • Access to an up-to-date country risk rating system enables your organization and individual staff to quickly determine the overall level of risk in a specific country or location.
      • Based on this risk rating, you can specify what security measures are required prior to travel and what level of travel authorization is appropriate, in line with the organization's security policy or travel security procedures.
      • While some larger organizations can maintain their own country risk ratings, this requires significant capacity, particularly to obtain the necessary information to keep these regularly updated.
      • It may be more effective for your organization to make use of the travel risk ratings provided by an external security information provider, such as a company linked to your travel insurance or travel booking service, if available.
      • Alternatively, various open-source travel risk ratings are available via embassy travel sites or other website providers.

      Without a flexible system to account for the risk exposures of different jurisdictions, staff may perceive measures as a hindrance to operations.

      Develop a tiered risk rating

      The example below outlines potential risk indicators for high-risk travel.

      Rating

      Description

      Low

      Generally secure with adequate physical security. Low violent crime rates. Some civil unrest during significant events. Acts of terrorism rare. Risks associated with natural disasters limited and health threats mainly preventable.

      Moderate

      Periodic civil unrest. Antigovernment, insurgent, or extremist groups active with sporadic acts of terrorism. Staff at risk from common and violent crime. Transport and communications services are unreliable and safety records are poor. Jurisdiction prone to natural disasters or disease epidemics.

      High

      Regular periods of civil unrest, which may target foreigners. Antigovernment, insurgent, or extremist groups very active and threaten political or economic stability. Violent crime rates high, often targeting foreigners. Infrastructure and emergency services poor. May be regular disruption to transportation or communications services. Certain areas off-limits to foreigners. Jurisdictions experiencing natural disasters or epidemics are considered high risk.

      Extreme

      Undergoing active conflict or persistent civil unrest. Risk of being caught up in a violent incident or attack is very high. Authorities may have lost control of significant portions of the country. Lines between criminality and political and insurgent violence are blurred. Foreigners are likely to be denied access to parts of the country. Transportation and communication services are severely degraded or nonexistent. Violence presents a direct threat to staff security.

      Ratings are formulated by assessing several types of risk, including conflict, political/civil unrest, terrorism, crime, and health and infrastructure risks.

      1.1.1 Determine assessment scope

      1 – 2 hours

      1. As a group, brainstorm a list of high-risk jurisdictions to target for additional assessment. Write down as many items as possible to include in:
      • Lines of business
      • Physical locations
      • IT systems

      Pay close attention to elements of the assessment that are not in scope.

    • Discuss the response and the rationale for targeting each of them for additional risk assessments. Identify security-related concerns for different lines of business, locations, user groups, IT systems, and data.
    • Record your responses and your comments in the Information Security Requirements Gathering Tool.
    • Input

      Output

      • Corporate strategy
      • IT strategy
      • Security strategy
      • Relevant threat intelligence
      • A list of high-risk jurisdictions to focus your risk assessment

      Materials

      Participants

      • Laptop
      • Projector
      • Security team
      • IT leadership
      • Business stakeholders
      • Enterprise Risk Management
      • Compliance
      • Legal

      Download the Information Security Requirements Gathering Tool

      Position your efforts in a business context

      Securing critical assets in high-risk jurisdictions is a business imperative

      • Many companies relegate their information security strategies to their IT department. Aside from the strain the choice places on a department that already performs many different functions, it wrongly implies that mitigating information security risk is simply an IT problem.
      • Managing information security risks is a business problem. It requires that organizations identify their risk appetite, prioritize relevant threats, and define risk mitigation initiatives. Business leaders can only do these activities effectively in a context that recognizes the business and financial benefits of implementing protections.
      • This is notably true of businesses with operations in many different countries. Each jurisdiction has its own set of security risks the organization must account for, as well as unique local laws and regulations that affect business operations.
      • In high-risk jurisdictions, your efforts must consider the unique operational challenges your organization may not face in its home country. Your efforts to secure critical assets will be most successful if you describe key risk scenarios in terms of their impact on business goals.
      • You can find additional guidance on assessing the business context of a security strategy in Phase 1 of Build an Information Security Strategy.

      Do you understand the unique business context of operations in high-risk jurisdictions?

      1.1.2 Identify business goals

      Estimated Time: 1-2 hours

      1. As a group, brainstorm the primary and secondary business goals of the organization. Focus your assessment on operations in high-risk jurisdictions you identified in Exercise 1.1.1. Review:
      • Relevant corporate and IT strategies.
      • The business goal definitions and indicator metrics in tab 2, “Goals Definition,” of the Information Security Requirements Gathering Tool.
    • Limit business goals to no more than two primary goals and three secondary goals. This limitation will help you prioritize security initiatives at the end of the project.
    • For each business goal, identify up to two security alignment goals that will support business goals in high-risk jurisdictions.
    • Input

      Output

      • Corporate strategy
      • IT strategy
      • Security strategy
      • Your goals for the security risk assessment for high-risk jurisdictions

      Materials

      Participants

      • Laptop
      • Projector
      • Security team
      • IT leadership
      • Business stakeholders
      • Risk Management
      • Compliance
      • Legal

      Download the Information Security Requirements Gathering Tool

      Record business goals

      Capture the results in the Information Security Requirements Gathering Tool

      1. Record the primary and secondary business goals you identified in tab 3, “Goals Cascade,” of the Information Security Requirements Gathering Tool.
      2. Next, record the two security alignment goals you selected for each business goal based on the tool’s recommendations.
      3. Finally, review the graphic diagram that illustrates your goals on tab 6, “Results,” of the Information Security Requirements Gathering Tool.
      4. Revisit this exercise whenever operations expands to a new jurisdiction to capture how they contribute to the organization’s mission and vision and how the security program can support them.
      The image contains a screenshot of Tab 3, Goals Cascade.

      Tab 3, Goals Cascade

      The image contains a screenshot of Tab 6, Results.

      Tab 6, Results

      Analyze business goals

      Assess how operating in multiple jurisdictions adds nuance to your business goals

      • Security leaders need to understand the direction of the business to propose relevant security initiatives that support business goals in high-risk jurisdictions.
      • Operating in different jurisdictions carries its own degree of risk. The organization is subject not only to the information security risks and legal frameworks of its country of origin but also to those associated with international jurisdictions.
      • You need to understand where your organization operates and how these different jurisdictions contribute to your business goals to support their performance and protect the firm’s reputation.
      • This exercise will make an explicit link between security and privacy concerns in high-risk jurisdictions, what the business cares about, and what security is trying to accomplish.

      If the organization is considering a merger and acquisition project that will expand operations in jurisdictions with different travel risk profiles, the security organization needs to revise the security strategy to ensure the organization can support high-risk travel and mitigate risks to critical assets.

      Identify compliance obligations

      Data compliance obligations loom large in high-risk jurisdictions

      The image contains four hexagons, each with their own words. SOX, PCI DSS, HIPAA, HITECH.

      Security leaders are familiar with most conventional regulatory obligations that govern financial, personal, and healthcare data in North America and Europe.

      The image contains four hexagons, each with their own words. Residency, Cross-Border Transfer, Breach Notification, Third-Party Risk Mgmt.

      Data privacy concerns, nationalism, and the economic value of data are all driving jurisdictions to adopt data residency and data localization and to shut down the cross-border transfer of data.

      The next step requires you to consider the compliance obligations the organization needs to meet to support the business as it expands to other jurisdictions through natural growth, mergers, and acquisitions.

      1.1.3 Identify compliance obligations

      Estimated Time: 1-2 hours

      1. As a group, brainstorm compliance obligations in target jurisdictions. Focus your assessment on operations in high-risk jurisdictions.
      2. Include:

      • Laws
      • Governing regulations
      • Industry standards
      • Contractual agreements
    • Record your compliance obligations and comments on tab 4, “Compliance Obligations,” of the Information Security Requirements Gathering Tool.
    • If you need to take full stock of the laws and regulations in place in the jurisdictions where you operate that you are not familiar with, consider seeking local legal counsel to help you navigate this exercise.
    • Input

      Output

      • Legal and compliance frameworks in target jurisdictions
      • Mandatory and voluntary compliance obligations for target jurisdictions

      Materials

      Participants

      • Laptop
      • Projector
      • Security team
      • IT leadership
      • Business stakeholders
      • Risk Management
      • Compliance
      • Legal

      Download the Information Security Requirements Gathering Tool

      Step 1.2

      Evaluate Security Pressures

      Activities

      1.2.1 Conduct initial risk assessment

      1.2.2 Conduct pressure analysis

      1.2.3 Determine risk tolerance

      This step involves the following participants:

      • Security team
      • Risk and Compliance
      • IT leadership (optional)

      Outcomes of this step

      Identify threats to global assets and capture the security expectations of external stakeholders, including customers, regulators, legislators, and business partners, and determine risk tolerance.

      Evaluate security pressures to set the risk context

      Perform an initial assessment of high-risk jurisdictions to set the context.

      Assess:

      • The threat landscape.
      • The security pressures from key stakeholders.
      • The risk tolerance of your organization.

      You should be able to find the information in your existing security strategy. If you don’t have the information, work through the next three steps of the project blueprint.

      The image contains a diagram to demonstrate evaluating security pressures, as described in the text above.

      Some jurisdictions carry inherent risks

      • Jurisdictional risks stem from legal, regulatory, or political factors that exist in different countries or regions. They can also stem from unexpected legal changes in regions where critical assets have exposure. Understanding jurisdictional risks is critical because they can require additional security controls.
      • Jurisdictional risk tends to be higher in jurisdictions:
        • Where the organization:
          • Conducts high-value or high-volume financial transactions.
          • Supports and manages critical infrastructure.
          • Has high-cost data or data whose compromise could undermine competitive advantage.
          • Has a high percentage of part-time employees and contractors.
          • Experiences a high rate of employee turnover.
        • Where state actors:
          • Have a low commitment to cybersecurity, financial, and privacy legislation and regulation.
          • Support cybercrime organizations within their borders.

      Jurisdictional risk is often reduced to countries where money laundering and terrorist activities are high. In this blueprint, the term refers to the broader set of information security risks that arise when operating in a foreign country or jurisdiction.

      Five key risk scenarios are most prevalent

      Key Risk Scenarios

      • High-Risk Travel
      • Compliance Risk
      • Insider Threat
      • Advanced Persistent Threat
      • Commercial Surveillance

      Security leaders who support operations in many countries need to take additional steps to mitigate security risks to critical assets. The goal of the next two exercises is to analyze the threat landscape and security pressures unique to high-risk jurisdictions, which will inform the construction of key scenarios in Phase 2. These five scenarios are most prevalent in high-risk jurisdictions. Keep them in mind as you go through the exercises in this section.

      1.2.1 Assess jurisdictional risk

      1-3 hours

      1. As a group, review the questions on tab 2, “Risk Assessment,” of the Information Security Pressure Analysis Tool.
      2. Gather the required information from subject matter experts on the following risk elements with a focus on high-risk jurisdictions:
      3. Review each question in tab 2 of the Information Security Pressure Analysis Tool and select the most appropriate response.

      Input

      Output

      • Existing security strategy
      • List of organizational assets
      • Historical data on information security incidents
      • Completed risk assessment

      Materials

      Participants

      • Information Security Pressure Analysis Tool
      • Security team
      • IT leadership
      • Risk Management

      For more information on how to complete the risk assessment questionnaire, see Step 1.2.1 of Build an Information Security Strategy.

      1.2.2 Conduct pressure analysis

      1-3 hours

      1. As a group, review the questions on tab 3, “Pressure Analysis,” of the Information Security Pressure Analysis Tool.
      2. Gather the required information from subject matter experts on the following pressure elements with a focus on high-risk jurisdictions:
      • Compliance and oversight
      • Customer expectations
      • Business expectations
      • IT expectations
    • Review each question in the questionnaire and provide the most appropriate response using the drop-down list. It may be helpful to consult with the appropriate departments to obtain their perspectives.
    • For more information on how to complete the pressure analysis questionnaire, see Step 1.3 of Build an Information Security Strategy.

      Input

      Output

      • Information on various pressure elements within the organization
      • Existing security strategy
      • Completed pressure analysis

      Materials

      Participants

      • Information Security Pressure Analysis Tool
      • Security team
      • IT leadership
      • Business leaders
      • Compliance

      A low security pressure means that your stakeholders do not assign high importance to information security. You may need to engage stakeholders with the right key risk scenarios to illustrate jurisdictional risk and generate support for new security controls.

      Download the Information Security Pressure Analysis Tool

      Assess risk tolerance

      • Risk tolerance expresses the types and amount of risk the organization is willing to accept in pursuit of its goals.
      • These expectations can help you identify, manage, and report on key risk scenarios in high-risk jurisdictions.
      • For instance, an organization with a low risk tolerance will require a stronger information security program to minimize operational security risks.
      • It’s up to business leaders to determine the risks they are willing to accept. They may need guidance to understand how system-level risks affect the organization’s ability to pursue its goals.

      A formalized risk tolerance statement can help:

      • Support risk-based security decisions that align with business goals.
      • Provide a meaningful rationale for security initiatives.
      • Improve the transparency of investments in the organization’s security program.
      • Provide guidance for monitoring inherent risk and residual risk exposure.

      The role of security professionals is to identify and analyze key risk scenarios that may prevent the organization from reaching its goals.

      1.2.3 Determine risk tolerance

      1-3 hours

      1. As a group, review the questions on tab 4, “Risk Tolerance,” of the Information Security Pressure Analysis Tool.
      2. Gather the required information from subject matter experts on the following risk tolerance elements:
      • Recent IT problems, especially downtime and data recovery issues
      • Historical security incidents
    • Review any relevant documentation, including:
      • Existing security strategy
      • Business impact assessments
      • Service-level agreements

      For more information on how to complete the risk tolerance questionnaire, see Step 1.4 of Build an Information Security Strategy.

      Input

      Output

      • Existing security strategy
      • Data on recent IT problems and incidents
      • Business impact assessments
      • Completed risk tolerance statement

      Materials

      Participants

      • Information Security Pressure Analysis Tool
      • Security team
      • IT leadership
      • Risk Management

      Download the Information Security Pressure Analysis Tool

      Review the output of the results tab

      • The organizational risk assessment provides a high-level assessment of inherent risks in high-risk jurisdictions. Use the results to build and assess key risk scenarios in Phase 2.
      • Use the security pressure analysis to inform stakeholder management efforts. A low security pressure indicates that stakeholders do not yet grasp the impact of information security on organizational goals. You may need to communicate its importance before you discuss additional security controls.
      • Jurisdictions in which organizations have a low risk tolerance will require stronger information security controls to minimize operational risks.
      The image contains a screenshot of the organizational risk assessment. The image contains a screenshot of the security pressure analysis. The image contains a screenshot of the risk tolerance curve.

      Phase 2

      Assess Security Risks to Critical Assets

      This phase will walk you through the following activities:

      • Identify critical assets, their vulnerabilities to relevant threats, and the adverse impact a successful threat event would have on the organization.
      • Assess risk exposure of critical assets in high-risk jurisdictions for each risk scenario through an analysis of its likelihood and impact.

      This phase involves the following participants:

      • Security team
      • Risk and Compliance
      • IT leadership (optional)

      Step 2.1

      Identify Risks

      Activities

      2.1.1 Identify assets

      2.1.2 Identify threats

      This step involves the following participants:

      • Security team
      • Risk and Compliance
      • IT leadership (optional)

      Outcomes of this step

      • Define risk scenarios that identify critical assets, their vulnerabilities to relevant threats, and the adverse impact a successful threat event would have on the organization.

      This blueprint focuses on mitigating jurisdictional risks

      The image contains a screenshot of the IT Risk Management Framework. The framework includes: Risk Identification, Risk Assessment, Risk Response, and Risk Governance.

      For a deeper dive into building a risk management program, see Info-Tech’s core project blueprints on risk management:

      Build an IT Risk Management Program

      Combine Security Risk Management Components Into One Program

      Draft key risk scenarios to illustrate adverse events

      Risk scenarios help decision-makers understand how adverse events affect business goals.

      • Risk-scenario building is the process of identifying the critical factors that contribute to an adverse event and crafting a narrative that describes the circumstances and consequences if it were to happen.
      • Risk scenarios set up the risk analysis stage of the risk assessment process. They are narratives that describe in detail:
        • The asset at risk.
        • The threat that can act against the asset.
        • Their intent or motivation.
        • The circumstances and threat actor model associated with the threat event.
        • The potential effect on the organization.
        • When or how often the event might occur.

      Risk scenarios are further distilled into a single sentence or risk statement that communicates the essential elements from the scenario.

      Well-crafted risk scenarios have four components

      The second phase of the project will help you craft meaningful risk scenarios

      Threat

      Exploits an

      Asset

      Using a

      Method

      Creating an

      Effect

      An actor capable of harming an asset

      Anything of value that can be affected and results in loss

      Technique an actor uses to affect an asset

      How loss materializes

      Examples: Malicious or untrained employees, cybercriminal groups, malicious state actors

      Examples: Systems, regulated data, intellectual property, people

      Examples: Credential compromise, privilege escalation, data exfiltration

      Examples: Loss of data confidentiality, integrity, or availability; impact on staff health & safety

      Risk scenarios are concise, four to six sentence narratives that describe the core elements of forecasted adverse events. Use them to engage stakeholders with the right questions and guide them to make informed decisions about how to address and treat security risks in high-risk jurisdictions.

      The next slides review five key risk scenarios prevalent in high-risk jurisdictions. Use them as examples to develop your own.

      Travel to high-risk jurisdictions requires special measures to protect staff, devices, and data

      Governmental, academic, and commercial advisors compile lists of jurisdictions that pose greater travel risks annually.

      For instance, in the US, these lists might include countries that are:

      • Subjects of travel warnings by the US Department of State.
      • Identified as high risk by other US government sources such as:
        • The Department of the Treasury Office of Foreign Assets Control (OFAC).
        • The Federal Bureau of Investigation (FBI).
        • The Office of the Director of National Intelligence (ODNI).
      • Compiled from academic and commercial sources, such as Control Risks.

      When securing travel to high-risk jurisdictions, you must consider personnel safety as well as data and device security.

      The image contains a diagram to present high-risk jurisdictions.

      The diagram presents high-risk jurisdictions based on US governmental sources (2021) listed on this slide.

      High-risk travel

      Likelihood: Medium

      Impact: Medium

      Key Risk Scenario #1

      Malicious state actors, cybercriminals, and competitors can threaten staff, devices, and data during travel to high-risk jurisdictions. Device theft or compromise may occur while traveling through airports, accessing hotel computer and phone networks, or in internet cafés or other public areas. Threat actors can exploit data from compromised or stolen devices to undermine the organization’s strategic, economic, or competitive advantage. They can also infect compromised devices with malware that delivers malicious payloads once they reconnect with home networks.

      Threat Actor:

      • Malicious state actors
      • Cybercriminals
      • Competitors

      Assets:

      • Staff
      • IT systems
      • Sensitive data

      Effect:

      • Compromised staff health and safety
      • Loss of data
      • Lost of system integrity

      Methods:

      • Identify, steal, or target mobile devices.
      • Compromise network, wireless, or Bluetooth connections.
      • Leverage stolen devices as a means of infecting other networks.
      • Access devices to track user location.
      • Activate microphones on devices to collect information.
      • Intercept electronic communications users send from high-risk jurisdictions.

      The data compliance landscape is a jigsaw puzzle of data protection and data residency requirements

      Since the EU passed the GDPR in 2016, jurisdictions have turned to data regulations to protect citizen data

      Data privacy concerns, nationalism, and the economic value of data are all driving jurisdictions to adopt data residency, breach notification, and cross-border data transfer regulations. As 2021 wound down to a close, nearly all the world’s 30 largest economies had some form of data regulation in place. The regulatory landscape is shifting rapidly, which complicates operations as organizations grow into new markets or engage in merger and acquisition activities.

      Global operations require special attention to data-residency requirements, data breach notification requirements, and cross-border data transfer regulations to mitigate compliance risk.

      The image contains a diagram to demonstrate the data regulations placed in various places around the world.

      Compliance risk

      Likelihood: Medium

      Impact: High

      Key Risk Scenario #2

      Rapid changes in the privacy and security regulatory landscape threaten organizations’ ability to meet their compliance obligations from local legal and regulatory frameworks. Organizations risk reputational damage, administrative fines, criminal charges, and loss of market share. In extreme cases, organizations may lose their license to operate in high-risk jurisdictions. Shifts in the regulatory landscape can involve additional requirements for data residency, cross-border data transfer, data breach notification, and third-party risk management.

      Threat Actor:

      • Local, regional, and national state actors

      Asset:

      • Reputation, market share
      • License to operate

      Effect:

      • Administrative fines
      • Loss of reputation, brand trust, and consumer loyalty
      • Loss of market share
      • Suspension of business operations
      • Lawsuits due to collective actions and claims
      • Criminal charges

      Methods:

      • Shifts in the privacy and security regulatory landscape, including requirements for:
        • Data residency.
        • Cross-border data transfer.
        • Data breach notification.
        • Third-party security and privacy risk management.

      The incidence of insider threats varies widely by jurisdiction in unexpected ways

      On average, companies in North America, the Middle East, and Africa had the most insider incidents in 2021, while those in the Asia-Pacific region had the least.

      The Ponemon Institute set out to understand the financial consequences that result from insider threats and gain insight into how well organizations are mitigating these risks.

      In the context of this research, insider threat is defined as:

      • Employee or contractor negligence.
      • Criminal or malicious insider activities.
      • Credential theft (imposter risk).

      On average, the total cost to remediate insider threats in 2021 was US$15.4 million per incident.

      In all regions, employee or contractor negligence occurred most frequently. Organizations in North America and in the Middle East and Africa were most likely to experience insider threat incidents in 2021.

      the image contains a diagram of the world, with various places coloured in different shades of blue.

      The diagram represents the average number of insider incidents reported per organization in 2021. The results are analyzed in four regions (Ponemon Institute, 2022)

      Insider threat

      Likelihood: Low to Medium

      Impact: High

      Key Risk Scenario #3

      Malicious insiders, negligent employees, and credential thieves can exploit inside access to information systems to commit fraud, steal confidential or commercially valuable information, or sabotage computer systems. Insider threats are difficult to identify, especially when security is geared toward external threats. They are often familiar with the organization’s data and intellectual property as well as the methods in place to protect them. An insider may steal information for personal gain or install malicious software on information systems. They may also be legitimate users who make errors and disregard policies, which places the organization at risk.

      Threat Actor:

      • Malicious insiders
      • Negligent employees
      • Infiltrators

      Asset:

      • Sensitive data
      • Employee credentials
      • IT systems

      Effects:

      • Loss of system integrity
      • Loss of data confidentiality
      • Financial loss

      Methods:

      • Infiltrators may compromise credentials.
      • Malicious or negligent insiders may use corporate email to steal or share sensitive data, including:
        • Regulated data.
        • Intellectual property.
        • Critical business information.
      • Malicious agents may facilitate data exfiltration, as well as open-port and vulnerability scans.

      The risk of advanced persistent threats is more prevalent in Central and South America and the Asia-Pacific region

      Attacks from advanced persistent threat (APT) actors are more sophisticated than traditional ones.

      • More countries will use legal indictments as part of their cyber strategy. Exposing toolsets of APT groups carried out at the governmental level will drive more states to do the same.
      • Expect APTs to increasingly target network appliances like VPN gateways as organizations continue to sustain hybrid workforces.
      • The line between APTs and state-sanctioned ransomware groups is blurring. Expect cybercriminals to wield better tools, mount more targeted attacks, and use double-extortion tactics.
      • Expect more disruption and collateral damage from direct attacks on critical infrastructure.

      Top 10 Significant Threat Actors:

      • Lazarus
      • DeathStalker
      • CactusPete
      • IAmTheKing
      • TransparentTribe
      • StrongPity
      • Sofacy
      • CoughingDown
      • MuddyWater
      • SixLittleMonkeys

      Top 10 Targets:

      • Government
      • Banks
      • Financial Institutions
      • Diplomatic
      • Telecommunications
      • Educational
      • Defense
      • Energy
      • Military
      • IT Companies
      The image contains a world map coloured in various shades of blue.
      Top 12 countries targeted by APTs (Kaspersky, 2020)

      Track notable APTs to revise your list of high-risk jurisdictions and review the latest tactics and techniques

      Governmental advisors track notable APT actors that pose greater risks.

      The CISA Shields Up site, SANS Storm Center site, and MITRE ATT&CK group site provide helpful and timely information to understand APT risks in different jurisdictions.

      The following threat actors are currently associated with cyberattacks affiliated with the Russian government.

      Activity Group

      Risks

      APT28 (GRU)

      Known as Fancy Bear, this threat group has been tied to espionage since 2004. They compromised the Hillary Clinton campaign, amid other major events.

      APT29 (SVT)

      Tied to espionage since 2008. Reportedly compromised the Democratic National Committee in 2015. Cited in the 2021 SolarWinds compromise.

      Buhtrap/RTM Group

      Group focused on financial targets since 2014. Currently known to target Russian and Ukrainian banks.

      Gamaredon

      Operating in Crimea. Aligned with Russian interests. Has previously targeted Ukrainian government officials and organizations.

      DEV-0586

      Carried out wiper malware attacks on Ukrainian targets in January 2022.

      UNC1151

      Active since 2016. Linked to information operation campaigns and the distribution of anti-NATO material.

      Conti

      Most successful ransomware gang of 2021, with US$188M revenue. Supported Russian invasion of Ukraine, threatening attacks on allied critical infrastructure.

      Sources: MITRE ATT&CK; Security Boulevard, 2022; Reuters, 2022; The Verge, 2022

      Advanced persistent threat

      Likelihood: Low to Medium

      Impact: High

      Key Risk Scenario #4

      Advanced persistent threats are state actors or state-sponsored affiliates with the means to avoid detection by anti-malware software and intrusion detection systems. These highly-skilled and persistent malicious agents have significant resources with which to bypass traditional security controls, establish a foothold in the information technology infrastructure, and exfiltrate data undetected. APTs have the resources to adapt to a defender’s efforts to resist them over time. The loss of system integrity and data confidentiality over time can lead to financial losses, business continuity disruptions, and the destruction of critical infrastructure.

      Threat Actor:

      • State actors
      • State-sponsored affiliates

      Asset:

      • Sensitive data
      • IT systems
      • Critical infrastructure

      Effects:

      • Loss of system integrity
      • Loss of data confidentiality
      • Financial loss
      • Business continuity disruptions
      • Infrastructure destruction

      Methods:

      • Persistent, consistent attacks using the most advanced threats and tactics to bypass security defenses.
      • The goal of APTs is to maintain access to networks for prolonged periods without being detected.
      • The median dwell time differs widely between regions. FireEye reported the mean dwell time for 2018:
        • Americas: 71 days
        • Europe, Middle East, and Africa: 177 days
        • Asia-Pacific: 204 days
      Sources: Symantec, 2011; FireEye, 2019

      Threat agents have deployed invasive technology for commercial surveillance in at least 76 countries since 2015

      State actors and their affiliates purchased and used invasive spyware from companies in Europe, Israel, and the US.

      • “Customers are predominantly repressive regimes looking for new ways to control the flow of information and stifle dissent. Less than 10% of suspected customers are considered full democracies by the Economist Intelligence Unit.” (Top10VPN, 2021)
      • Companies based in economically developed and largely democratic states are profiting off the technology.
      • The findings demonstrate the need to consider geopolitical realities when assessing high-risk jurisdictions and to take meaningful action to increase layered defenses against invasive malware.
      • Spyware is having an increasingly well-known impact on civil society. For instance, since 2016, over 50,000 individual phone numbers have been identified as potential targets by NSO Group, the Israeli manufacturers of the notorious Pegasus Spyware. The target list contained the phone numbers of politicians, journalists, activists, doctors, and academics across the world.
      • The true number of those affected by spyware is almost impossible to determine given that many fall victim to the technology and do not notice.
      The image contains a map of the world with various countries highlighted in shades of blue.

      Countries where commercial surveillance tools have been deployed (“Global Spyware Market Index,” Top10VPN, 2021)

      The risks and effects of spyware vary greatly

      Spyware can steal mundane information, track a user’s every move, and everything in between.

      Adware

      Software applications that display advertisements while the program is running.

      Keyboard Loggers

      Applications that monitor and record keystrokes. Malicious agents use them to steal credentials and sensitive enterprise data.

      Trojans

      Applications that appear harmless but inflict damage or data loss to a system.

      Mobile Spyware

      Surveillance applications that infect mobile devices via SMS or MMS channels, though the most advanced can infect devices without user input.

      State actors and their affiliates use system monitors to track browsing habits, application usage, and keystrokes and capture information from devices’ GPS location data, microphone, and camera. The most advanced system monitor spyware, such as NSO Group’s Pegasus, can infect devices without user input and record conversations from end-to-end encrypted messaging systems.

      Commercial surveillance

      Likelihood: Low to Medium

      Impact: Medium

      Key Risk Scenario #5

      Malicious agents can deploy malware on end-user devices with commercial tools available off the shelf to secretly monitor the digital activity of users. Attacks exploit widespread vulnerabilities in telecommunications protocols. They occur through email and text phishing campaigns, malware embedded in untested applications, and sophisticated zero-click attacks that deliver payloads without requiring user interactions. Attacks target sensitive as well as mundane information. They can be used to track employee activities, investigate criminal activity, or steal credentials, credit card numbers, or other personally identifiable information.

      Threat Actor:

      • State actors
      • State-sponsored affiliates

      Asset:

      • Sensitive data
      • Staff health and safety
      • IT systems

      Effects:

      • Data breaches
      • Loss of data confidentiality
      • Increased risk to staff health and safety
      • Misuse of private data
      • Financial loss

      Methods:

      • Email and text phishing attacks that delivery malware payloads
      • Sideloading untested applications from a third-party source rather than an official retailer
      • Sophisticated zero-click attacks that deliver payloads without requiring user interaction

      Use the Jurisdictional Risk Register and Heatmap Tool

      The tool included with this blueprint can help you draft risk scenarios and risk statements in this section.

      The risk register will capture a list of critical assets and their vulnerabilities, the threats that endanger them, and the adverse effect your organization may face.

      The image includes two screenshots of the jurisdictional risk register and heatmap tool. The image contains a screenshot of the High-Risk Travel Jurisdiction.

      Download the Jurisdictional Risk Register and Heatmap Tool

      2.1.1 Identify assets

      1 – 2 hours

      1. As a group, consider critical or mission-essential functions in high-risk jurisdictions and the systems on which they depend. Brainstorm a list of the organization’s mission-supporting assets in high-risk jurisdictions. Consider:
      • Staff
      • Critical IT systems
      • Sensitive data
      • Critical operational processes
    • On a whiteboard, brainstorm the potential adverse effect of malicious agents in high-risk jurisdictions compromising critical assets. Consider the impact on:
      • Information systems.
      • Sensitive or regulated data.
      • Staff health and safety.
      • Critical operations and objectives.
      • Organizational finances.
      • Reputation and brand loyalty

      Threat

      Exploits an

      Asset

      Using a

      Method

      Creating an

      Effect

      Inputs for risk scenario identification

      Input

      Output

      • Corporate strategy
      • IT strategy
      • Security strategy
      • Business impact analyses
      • A list of the organization’s mission-supporting assets

      Materials

      Participants

      • Laptop
      • Projector
      • Whiteboard
      • Security team
      • IT leadership
      • System owner
      • Enterprise Risk Management

      Threat

      Exploits an

      Asset

      Using a

      Method

      Creating an

      Effect

      Inputs for risk scenario identification

      The image contains an example of the activity mentioned in the text above.

      Model threats to narrow the range of scenarios

      Motives and capabilities to perform attacks on critical assets vary across different threat actors.

      Category

      Actions

      Motivation

      Sophistication

      Nation-states

      Cyberespionage, cyberattacks

      Geopolitical

      High. Dedicated resources and personnel, extensive planning and coordination.

      Proxy organizations

      Espionage, destructive attacks

      Geopolitical, Ideological, Profit

      Moderate. Some planning and support functions and technical expertise.

      Cybercrime

      Theft, fraud, extortion

      Profit

      Moderate. Some planning and support functions and technical expertise.

      Hacktivists

      Disrupt operations, attack brands, release sensitive data

      Ideological

      Low. Rely on widely available tools that require little skill to deploy.

      Insiders

      Destruction or release of sensitive data, theft, exposure through negligence

      Incompetence, Discontent

      Internal access. Acting on their own or in concert with any of the above.

      • Criminals, hacktivists, and insiders vary in sophistication. Some criminal groups demonstrate a high degree of sophistication; however, a large cyber event that damages critical infrastructure does not align with their incentives to make money at minimal risk.
      • Proxy actors conduct offensive cyber operations on behalf of a beneficiary. They may be acting on behalf of a competitor, national government, or group of individuals.
      • Nation-states engage in long-term espionage and offensive cyber operations that support geopolitical and strategic policy objectives.

      2.1.2 Identify threats

      1 – 2 hours

      1. Review the outputs from activity 1.1.1 and activity 2.1.1.
      2. Identify threat agents that could undermine the security of critical assets in high-risk jurisdictions. Include internal and external actors.
      3. Assess their motives, means, and opportunities.
      • Which critical assets are most attractive? Why?
      • What paths and vulnerabilities can threat agents exploit to reach critical assets without going through a control?
      • How could they defeat existing controls? Draw on the MITRE framework to inform your analysis.
      • Once agents defeat a control, what further attack can they launch?

      Threat

      Exploits an

      Asset

      Using a

      Method

      Creating an

      Effect

      Inputs for risk scenario identification

      Input

      Output

      • Jurisdictional assessment from activity 1.1.1
      • Critical assets from activity 2.1.1
      • Potential vulnerabilities from:
        • Security control gap analysis
        • Security risk register
      • Threat intelligence
      • MITRE framework
      • A list of critical assets, threat agents, vulnerabilities, and potential attack vectors.

      Materials

      Participants

      • Laptop
      • Projector
      • Whiteboard
      • Security team
      • Infrastructure & Operations team
      • Enterprise Risk Management

      2.1.2 Identify threats (continued)

      1 – 2 hours

      1. On a whiteboard, brainstorm how threat agents will exploit vulnerabilities in critical assets to reach their goal. Redefine attack vectors to capture what could result from a successful initial attack.

      For example:

      • State actors and cybercriminals may steal or compromise end-user devices during travel to high-risk jurisdictions using malware they embed in airport charging stations, internet café networks, or hotel business centers.
      • Compromised devices may infect corporate networks and threaten sensitive data once they reconnect to them.

      Threat

      Exploits an

      Asset

      Using a

      Method

      Creating an

      Effect

      The image contains a screenshot of activity 2.1.2 as described in the text above.

      Bring together the critical risk elements into a single risk scenario

      Summarize the scenario further into a single risk statement

      Risk Scenario: High-Risk Travel

      State actors and cybercriminals can threaten staff, devices, and data during travel to high-risk jurisdictions. Device theft or compromise may occur while traveling through airports, accessing hotel computer and phone networks, or in internet cafés or other public areas. Threat actors can exploit data from compromised or stolen devices to undermine the organization’s strategic, economic, or competitive advantage. They can also infect compromised devices with malware that delivers malicious payloads once they reconnect with home networks.

      Risk Statement

      Cybercriminals compromise end-user devices during travel to high-risk jurisdictions, jeopardizing staff safety and leading to loss of sensitive data.

      Risk Scenario: Compliance Risk

      Rapid changes in the privacy and security regulatory landscape threaten an organization’s ability to meet its compliance obligations from local legal and regulatory frameworks. Organizations that fail to do so risk reputational damage, administrative fines, criminal charges, and loss of market share. In extreme cases, organizations may lose their license to operate in high-risk jurisdictions. Shifts in the regulatory landscape can involve additional requirements for data residency, cross-border data transfer, data breach notification, and third-party risk management.

      Risk Statement

      Rapid changes in the privacy and security regulations landscape threaten our ability to remain compliant, leading to reputational and financial loss.

      Fill out the Jurisdictional Risk Register and Heatmap Tool

      The tool is populated with data from two key risk scenarios: high-risk travel and compliance risk.

      The image includes two screenshots of the Jurisdictional Risk Register and Heatmap Tool.

      1. Label the risk in Tab 3, Column B.
      2. Record your risk scenario in Tab 3, Column C.
      3. Record your risk statement in Tab 3, Column D.
      4. Identify the applicable jurisdictions in Tab 3, Column E.
      5. You can further categorize the scenario as:
        • an enterprise risk (Column G).
        • an IT risk (Column H).

      Download the Jurisdictional Risk Register and Heatmap Tool

      Step 2.2

      Assess Risk Exposure

      Activities

      2.2.1 Identify existing controls

      2.2.2 Assess likelihood and impact

      This step involves the following participants:

      • Security team
      • Risk and Compliance
      • IT leadership (optional)

      Outcomes of this step

      • Assess risk exposure for each risk scenario through an analysis of its likelihood and impact.

      Brush up on risk assessment essentials

      The next step will help you prioritize IT risks based on severity.

      Likelihood of Occurrence X Likelihood of Impact = Risk Severity

      Likelihood of occurrence: How likely the risk is to occur.

      Likelihood of impact: The likely impact of a risk event.

      Risk severity: The significance of the risk.

      Evaluate risk severity against the risk tolerance thresholds and the cost of risk response.

      Identify existing controls before you proceed

      Existing controls will reduce the inherent likelihood and impact of the risk scenario you face.

      Existing controls were put in place to avoid, mitigate, or transfer key risks your organization faced in the past. Without considering existing controls, you run the risk of overestimating the likelihood and impact of the risk scenarios your organization faces in high-risk jurisdictions.

      For instance, the ability to remote-wipe corporate-owned devices will reduce the potential impact of a device lost or compromised during travel to high-risk jurisdictions.

      As you complete the risk assessment for each scenario, document existing controls that reduce their inherent likelihood and impact.

      2.2.1 Document existing controls

      6-10 hours

      1. Document the Risk Category and Existing Controls in the Jurisdictional Risk Register and Heatmap Tool.
        • Tactical controls apply to individual risks only. For instance, the ability to remote-wipe devices mitigates the impact of a device lost in a high-risk jurisdiction.
        • Strategic controls apply to multiple risks. For instance, deploying MFA for critical applications mitigates the likelihood that malicious actors can compromise a lost device and impedes their access in devices they do compromise.

      Input

      Output

      • Risk scenarios
      • Existing controls for risk scenarios

      Materials

      Participants

      • Jurisdictional Risk Register and Heatmap Tool
      • Laptop
      • Projector
      • Security team
      • IT leadership
      • Business stakeholders
      • Enterprise Risk Management

      Download the Jurisdictional Risk Register and Heatmap Tool.

      Assess the risk scenarios you identified in Phase 1

      The risk register is the central repository for risks in high-risk jurisdictions.

      • Use the second tab of the Jurisdictional Risk Register and Heatmap Tool to create likelihood, impact, and risk tolerance assessment scales to evaluate every risk event effectively.
      • Severity-level assessment is a “first pass” of your risk scenarios that will reveal your organization’s most severe risks in high-risk jurisdictions.
      • You can incorporate expected cost calculations into your evaluation to assess scenarios in greater detail.
      • Expected cost represents how much you would expect to pay in an average year for each risk event. Expected cost calculations can help compare IT risks to non-IT risks that may not use the same scales and communicate system-level risk to the business in a language they will understand.

      Expected cost calculations may not be practical. Determining robust likelihood and impact values to produce cost estimates can be challenging and time consuming. Use severity-level assessments as a first pass to make the case for risk mitigation measures and take your lead from stakeholders.

      The image contains two screenshots of the Jurisdictional Risk Register and Heatmap Tool.

      Use the Jurisdictional Risk Register and Heatmap Tool to capture and analyze your data.

      2.2.2 Assess likelihood and impact

      6-10 hours

      1. Assign each risk scenario a likelihood of occurrence and a likely impact level that represents the impact of the scenario on the whole organization considering existing controls. Record your results in Tab 3, column R and S, respectively.
      2. You can further dissect likelihood and impact into component parameters but focus first on total likelihood and impact to keep the task manageable.
      3. As you input the first few likelihood and impact values, compare them to one another to ensure consistency and accuracy. For instance, is a device lost in a high-risk jurisdiction truly more impactful than a device compromised with commercial surveillance software?
      4. The tool will calculate the probability of risk exposure based on the likelihood and consequence associated with the scenario. The results are published in Tab 3, Column T.

      Input

      Output

      • Risk scenarios
      • Assessed the likelihood of occurrence and impact for all identified risk events

      Materials

      Participants

      • Jurisdictional Risk Register and Heatmap Tool
      • Laptop
      • Projector
      • Security team
      • IT leadership
      • Business stakeholders
      • Enterprise Risk Management

      Download the Jurisdictional Risk Register and Heatmap Tool.

      Refine your risk assessment to justify your estimates

      Document the rationale behind each value and the level of consensus in group discussions.

      Stakeholders will likely ask you to explain some of the numbers you assigned to likelihood and impact assessments. Pointing to an assessment methodology will give your estimates greater credibility.

      • Assign one individual to take notes during the assessment exercise.
      • Have them document the main rationale behind each value and the level of consensus.

      The goal is to develop robust intersubjective estimates of the likelihood and impact of a risk scenario.

      We assigned a 50% likelihood rating to a risk scenario. Were we correct?

      Assess the truth of the following statements to test likelihood assessments. In this case, do these two statements seem true?

      • The risk event will likely occur once in the next two years, all things being equal.
      • In two nearly identical organizations, one out of two will experience the risk event this year.
      The image includes a screenshot of the High-Risk Travel Jurisdictions.

      Phase 3

      Execute Response

      This phase will walk you through the following activities:

      • Prioritize and treat global risks to critical assets based on their value and exposure.
      • Build an initiative roadmap that identifies and applies relevant controls to protect critical assets. Identify key risk indicators to monitor progress.

      This phase involves the following participants:

      • Security team
      • Risk and Compliance
      • IT leadership (optional)

      Step 3.1

      Treat Security Risks

      Activities

      3.1.1 Identify and assess risk response

      This step involves the following participants:

      • Security team
      • Risk and Compliance
      • IT leadership (optional)

      Outcomes of this step

      • Prioritize and treat global risks to critical assets based on their value and exposure.

      Analyze and select risk responses

      The next step will help you treat the risk scenarios you built in Phase 2.

      Identify

      Identify risk responses.

      Predict

      Predict the effectiveness of the risk response, if implemented, by estimating the residual likelihood and impact of the risk.

      Calculate

      The tool will calculate the residual severity of the risk after applying the risk response.

      The first part of the phase outlines project activities. The second part elaborates on high-risk travel and compliance risk, the two key risk scenarios we are following throughout the project. Use the Jurisdictional Risk Register and Heatmap Tool to capture your work.

      Analyze likelihood and impact to identify response

      The image contains a diagram of he risk response analysis. Risk Transfer and Risk Avoidance has the most likelihood, and Risk Acceptance and Risk Mitigation have the most impact. Risk Avoidance has the most likelihood and most impact in regards to risk response.

      3.1.1 Identify and assess risk response

      Complete the following steps for each risk scenario.

      1. Identify a risk response action that will help reduce the likelihood of occurrence or the impact if the scenario were to occur. Indicate the type of risk response (avoidance, mitigation, transfer, acceptance, or no risk exists).
      2. Assign each risk response action a residual likelihood level and a residual impact level. This is the same step you performed in Activity 2.2.2, but you are now are estimating the likelihood and impact of the risk event after you implemented the risk response action successfully. The Jurisdictional Risk Register and Heatmap Tool will generate a residual risk severity level for each risk event.
      3. Identify the potential Risk Action Owner (Project Manager) if the response is selected and turned into an IT project, and document this in the Jurisdictional Risk Register and Heatmap Tool .
      4. For each risk event, document risk response actions, residual likelihood and impact levels, and residual risk severity level.

      Input

      Output

      • Risk scenarios from Phase 2
      • Risk scenario mitigation plan

      Materials

      Participants

      • Whiteboard/flip charts
      • Jurisdictional Risk Register and Heatmap Tool
      • Security team
      • Risk and Compliance
      • IT leadership (optional)

      Download the Jurisdictional Risk Register and Heatmap Tool

      Step 3.2

      Mitigate Travel Risk

      Activities

      3.2.1 Develop a travel policy

      3.2.2 Develop travel procedures

      3.2.3 Design high-risk travel guidelines

      This step involves the following participants:

      • Security team
      • Risk and Compliance
      • IT leadership (optional)

      Outcomes of this step

      • Prioritize and treat global risks to critical assets based on their value and exposure.

      Identify controls to mitigate jurisdictional risk

      This section provides guidance on the most prevalent risk scenarios identified in Phase 2 and provides a more in-depth examination of the two most prevalent ones, high-risk travel and compliance risk. Determine the appropriate response to each risk scenario to keep global risks to critical assets aligned with the organization’s risk tolerance.

      Key Risk Scenarios

      • High-Risk Travel
      • Compliance Risk
      • Insider Threat
      • Advanced Persistent Threat
      • Commercial Surveillance

      Travel risk is a common concern in organizations with global operations

      • The security of staff, devices, and data is one of the biggest challenges facing organizations with a global footprint. Working and traveling in unpredictable environments will aways carry a degree of risk, but organizations can do much to develop a safer and more secure working environment.
      • Compromised or stolen devices can provide threat actors with access to data that could compromise the organization’s strategic, economic, or competitive advantage or expose the organization to regulatory risk.
      • For many organizations, security risk assessments, security plans, travel security procedures, security training, and incident reporting systems are a key part of their operating language.
      • The following section provides a simple structure to help organizations demystify travel in high-risk jurisdictions.

      The image contains a diagram to present high-risk jurisdictions.

      Before you leave

      • Identify high-risk countries.
      • Enable controls.
      • Limit what you pack.

      During your trip

      • Assume you are monitored.
      • Limit access to systems.
      • Prevent theft.

      When you return

      • Change your password.
      • Restore your devices.

      Case study

      Higher Education: Camosun College

      Interview: Evan Garland

      Frame additional security controls as a value-added service.

      Situation

      The director of the international department at Camosun College reached out to IT security for additional support. Department staff often traveled to hostile environments. They were concerned malicious agents would either steal end-user devices or compromise them and access sensitive data. The director asked IT security for options that would better protect traveling staff, their devices, and the information they contain.

      Challenges

      First, controls would need to admit both work and personal use of corporate devices. Staff relied exclusively on work devices for travel to mitigate the risk of personal device theft. Personal use of corporate devices during travel was common. Second, controls needed to strike the right balance between friction and effortless access. Traveling staff had only intermittent access to IT support. Restrictive controls could prevent them from accessing their devices and data altogether.

      Solution

      IT consulted staff to discuss light-touch solutions that would secure devices without introducing too much complexity or compromising functionality. They then planned security controls that involved user interaction and others that did not and identified training requirements.

      Results

      Controls with user interaction

      Controls without user interaction

      • Multifactor authentication for college systems and collaboration platforms
      • Password manager for both work and personal use for staff for stronger passwords and practices
      • Security awareness training to help traveling staff identify potential threats while traveling through airports or accessing public Wi-Fi.
      • Drive encryption and always-on VPN to protect data at rest and in transit
      • Increased setting for phishing and spam filtering for traveling staff email
      • Enhanced anti-malware/endpoint detection and response (EDR) solution for traveling laptops

      Build a program to mitigate travel risks

      There is no one-size-fits-all solution.

      The most effective solution will take advantage of existing risk management policies, processes, and procedures at your organization.

      • Develop a framework. Outline the organization’s approach to high-risk travel, including the policies, procedures, and mechanisms put in place to ensure safe travel to high-risk jurisdictions.
      • Draft a policy. Outline the organization’s risk attitude and key security principles and define roles and responsibilities. Include security responsibilities and obligations in job descriptions of staff members and senior managers.
      • Provide flexible options. Inherent travel risk will vary from one jurisdiction to another. You will likely not find an approach that works for every case. Establish locally relevant measures and plans in different security contexts and risk environments.
      • Look for quick wins. Identify measures or requirements that you can establish quickly but that can have a positive effect on the security of staff, data, and devices.
      • Monitor and review. Undertake periodic reviews of the organization’s security approach and management framework, as well as their implementation, to ensure the framework remains effective.

      3.2.1 Develop a travel policy

      1. Work with your business leaders to build a travel policy for high-risk jurisdictions. The policy should be a short and accessible document structured around four key sections:
        • A statement on the importance of staff security and safety, the scope of the policy, and who it applies to (staff, consultants, contractors, volunteers, visitors, accompanying dependants, etc.).
        • A principles section explaining the organization’s security culture, risk attitude, and the key principles that shape the organization’s approach to staff security and safety.
        • A responsibilities section setting out the organization’s security risk management structure and the roles and actions allocated to specific positions.
        • A minimal security requirements section establishing the specific security requirements that must be in place in all locations and specific locations.
      2. Common security principles include:
      • Shared responsibility – Managing risks to staff is a shared organizational responsibility.
      • Acknowledgment of risk – Managing security will not remove all risks. Staff need to appreciate, as part of their informed consent, that they are still exposed to risk.
      • Primacy of life – Staff safety is of the highest importance. Staff should never place themselves at excessive risk to meet program objectives or protect property.
      • Proportionate risk – Risks must be assessed to ensure they are proportionate to the benefits organizational activities provide and the ability to manage those risks.
      • Right to withdraw – Staff have the right to withdraw from or refuse to take up work in a particular area due to security concerns.
      • No right to remain – The organization has the right to suspend activities that it considers too dangerous.
    • Cross-reference the organization’s other governing policies that outline requirements related to security risk management, such as the health and safety policy, access control policy, and acceptable use of security assets.
    • Input

      Output

      • List of high-risk jurisdictions
      • Risk scenarios from Phase 2
      • Data inventory and data flows
      • Travel policy for high-risk jurisdictions

      Materials

      Participants

      • Whiteboard/flip charts
      • Jurisdictional Risk Register and Heatmap Tool
      • Security team
      • Legal team
      • IT leadership
      • Risk Management

      Develop security plans for high-risk travel

      Security plans advise staff on how to manage the risk identified in assessments.

      Security plans are key country documents that outline the security measures and procedures in place and the responsibilities and resources required to implement them. Security plans should be established in high-risk jurisdictions where your organization has a regular, significant presence. Security plans must remain relevant and accessible documents that address the specific risks that exist in that location, and, if appropriate, are specific about where the measures apply and who they apply to. Plans should be updated regularly, especially following significant incidents or changes in the operating environment or activities.

      Key Components

      Critical information – One-page summary of pertinent information for easy access and quick reference (e.g. curfew times, no-go areas, important contacts).

      Overview – Purpose and scope of the document, responsibilities for security plan, organization’s risk attitude, date of completion and review date, and a summary of the security strategy and policy.

      Current Context – Summary of current operating context and overall security situation; main risks to staff, assets, and operations; and existing threats and risk rating.

      Procedures – Simple security procedures that staff should adhere to in order to prevent incidents and how to respond should problems arise. Standard operating procedures (SOPs) should address key risks identified in the assessment.

      Security levels – The organization's security levels/phases, with situational indicators that reflect increasing risks to staff in that context and location and specific actions/measures required in response to increasing insecurity.

      Incident reporting – The procedures and responsibilities for reporting security-related incidents; for example, the type of incidents to be reported, the reporting structure, and the format for incident reporting.

      Determine travel risk

      Tailor your risk response to the security risk assessment you conducted in earlier stages of this project.

      Ratings are formulated by assessing several types of risk, including conflict, political/civil unrest, terrorism, crime, and health and infrastructure risks.

      Rating

      Description (Examples)

      Recommended Action

      Low

      Generally secure with adequate physical security. Low violent crime rates. Some civil unrest during significant events. Acts of terrorism rare. Risks associated with natural disasters limited and health threats mainly preventable.

      Basic personal security, travel, and health precautions required.

      Moderate

      Periodic civil unrest. Antigovernment, insurgent, or extremist groups active with sporadic acts of terrorism. Staff at risk from common and violent crime. Transport and communications services are unreliable and safety records are poor. Jurisdiction prone to natural disasters or disease epidemics.

      Increased vigilance and routine security procedures required.

      High

      Regular periods of civil unrest, which may target foreigners. Antigovernment, insurgent, or extremist groups very active and threaten political or economic stability. Violent crime rates high and targeting of foreigners is common. Infrastructure and emergency services poor. May be regular disruption to transportation or communications services. Certain areas off-limits to foreigners. Jurisdictions experiencing a natural disaster or a disease epidemic are considered high risk.

      High level of vigilance and effective, context-specific security precautions required.

      Extreme

      Undergoing active conflict or persistent civil unrest. Risk of being caught up in a violent incident or attack is very high. Civil authorities may have lost control of significant portions of the country. Lines between criminality and political and insurgent violence are blurred. Foreigners are likely to be denied access to significant parts of the country. Transportation and communication services are severely degraded or non-existent. Violence presents a direct threat to staff security.

      Stringent security precautions essential and may not be sufficient to prevent serious incidents.

      Program activities may be suspended and staff withdrawn at very short notice.

      3.2.2 Develop travel procedures

      1. Work with your business leaders to build travel procedures for high-risk jurisdictions. The procedures should be tailored to the risk assessment and address the risk scenarios identified in Phase 2.
      2. Use the categories outlined in the next two slides to structure the procedure. Address all types of travel, detail security measures, and outline what the organization expects of travelers before, during, and after their trip.
      3. Consider the implementation of special measures to limit the impact of a potential security event, including:
        • Information end-user device loaner programs.
        • Temporary travel service email accounts.
      4. Specify what happens when staff add personal travel to their work trip to cover issues such as insurance, check-in, actual travel times, etc.
      5. Discuss the rationale for each procedure. Ensure the components align with the policy statements outlined in the high-risk travel policy developed in the previous step.

      Input

      Output

      • List of high-risk jurisdictions
      • Risk scenarios from Phase 2
      • High-risk travel policy
      • Travel procedures for high-risk jurisdictions

      Materials

      Participants

      • Whiteboard/flip charts
      • Jurisdictional Risk Register and Heatmap Tool
      • Security team
      • Legal team
      • IT leadership
      • Risk Management

      Draft procedures to mitigate travel risks

      Address all types of travel, detail security measures, and outline what the organization expects of travelers before, during, and after their trip

      Introduction

      Clarifies who the procedures apply to. Highlights any differences in travel security requirements or support provided to staff, consultants, partners, and official visitors.

      Travel risk ratings

      Explains the travel or country risk rating system, how staff access the information, the different categories and indicators, and their implications.

      Roles and responsibilities

      Clarifies the responsibilities of travelers, their line managers or contact points, and senior management regarding travel security and how this changes for destinations with higher risk ratings.

      Travel authorization

      Stipulates who in the organization authorizes travel, the various compliance measures required, and how this changes for destinations with higher risk ratings.

      Travel risk assessment

      Explains when travel risk assessments are required, the template that should be used, and who approves the completed assessments.

      Travel security procedures should specify what happens when staff add personal travel to their work trip to cover issues such as insurance, check-in, actual travel times, etc.

      Pre-travel briefings

      Outlines the information that must be provided to travelers prior to departure, the type of briefing required and who provides it, and how these requirements change as risk ratings increase.

      Security training

      Explain security training required prior to travel. This may vary depending on the country’s risk rating. Includes information on training waiver system, including justifications and authorization.

      Traveler profile forms

      Travelers should complete a profile form, which includes personal details, emergency contacts, medical details, social media footprint, and proof-of-life questions (in contexts where there are abduction risks).

      Check-in protocol

      Specifies who travelers must maintain contact with while traveling and how often, as well as the escalation process in case of loss of contact. The frequency of check-ins should reflect the increase in the risk rating for the destination.

      Emergency procedures

      Outlines the organization's emergency procedures for security and medical emergencies.

      3.2.3 Design high-risk travel guidelines

      • Supplement the high-risk travel policies and procedures with guidelines to help international travelers stay safe.
      • The document is intended for an end-user audience and should reflect your organization’s policies and procedures for the use of information and information systems during international travel.
      • Use the Digital Safety Guidelines for International Travel template in concert with this blueprint to provide guidance on what end users can do to stay safe before they leave, during their trip, and when they return.
      • Consider integrating the guidelines into specialized security awareness training sessions that target end users who travel to high-risk jurisdictions.
      • The guidelines should supplement and align with existing technical controls.

      Input

      Output

      • List of high-risk jurisdictions
      • Risk scenarios from Phase 2
      • High-risk travel policy
      • High-risk travel procedure
      • Travel guidelines for high-risk jurisdictions

      Materials

      Participants

      • Whiteboard/flip charts
      • Jurisdictional Risk Register and Heatmap Tool
      • Security team
      • Legal team
      • IT leadership
      • Risk Management

      Download the Digital Safety Guidelines for International Travel template

      Step 3.3

      Mitigate Compliance Risk

      Activities

      3.3.1 Identify data localization obligations

      3.3.2 Integrate obligations into IT system design

      3.3.3 Document data processing activities

      3.3.4 Choose the right mechanism

      3.3.5 Implement the appropriate controls

      3.3.6 Identify data breach notification obligations

      3.3.7 Integrate data breach notification into incident response

      3.3.8 Identify vendor security and data protection requirements

      3.3.9 Build due diligence questionnaire

      3.3.10 Build appropriate data processing agreement

      This step involves the following participants:

      • Security team
      • Risk and Compliance
      • IT leadership (optional)

      Outcomes of this step

      • Prioritize and treat global risks to critical assets based on their value and exposure.

      Compliance risk is a prevalent risk in organizations with a global footprint

      • The legal and regulatory landscape is evolving rapidly to keep step with the pace of technological change. Security and privacy leaders are expected to mitigate the risk of noncompliance as the organization expands to new jurisdictions.
      • Organizations with a global footprint must stay abreast of local regulations and provide risk management guidance to business leaders to support global operations.
      • This sections describes four compliance risks in this context:
        • Cross-border data transfer
        • Third-party risk management
        • Data breach notification
        • Data residency

      Compliance with local obligations

      Likelihood: Medium to High

      Impact: High

      Data Residency

      Gap Controls

      • Identify and document the data localization obligations for the jurisdictions that the organization is operating in.
      • Design and implement IT systems that satisfy the data localization requirements.
      • Comply with data localization obligations within each jurisdiction.

      Heatmap of Global Data Residency Regulations

      The image contains a screenshot of a picture of a world map with various shades of blue to demonstrate the heatmap of global data residency regulations.
      Source: InCountry, 2021

      Examples of Data Residency Requirements

      Country

      Data Type

      Local Storage Requirements

      Australia

      Personal data – heath record

      My Health Records Act 2012

      China

      Personal information — critical information infrastructure operators

      Cybersecurity law

      Government cloud data

      Opinions of the Office of the Central Leading Group for Cyberspace Affairs on Strengthening Cybersecurity Administration of Cloud Computing Services for Communist Party and Government Agencies

      India

      Government email data

      The Public Records Act of 1993

      Indonesia

      Data held by electronic system operator for the public service

      Regulation 82 concerning “Electronic System and Transaction Operation”

      Germany

      Government cloud service data

      Criteria for the procurement and use of cloud services by the federal German administration

      Russia

      Personal data

      The amendments of Data Protection Act No. 152 FZ

      Vietnam

      Data held by internet service providers

      The Decree on Management, Provision, and Use of Internet Services and Information Content Online (Decree 72)

      US

      Government cloud service data

      Defense Federal Acquisition Regulation Supplement: Network Penetration Reporting and Contracting for Cloud Services (DFARS Case 2013-D018)

      3.3.1 Identify data localization obligations

      1-2 hours

      1. Work with your business leaders to identify and document the jurisdictions where your organization is operating in or providing services and products to consumers within.
      2. Work with your legal team to identify and document all relevant data localization obligations for the data your organization generates, collects, and processes in order to operate your business.
      3. Record your data localization obligations in the table below.

      Jurisdiction

      Relevant Regulations

      Local Storage Requirements

      Date Type

      Input

      Output

      • List of jurisdictions your organization is operating in
      • Relevant security and data protection regulations
      • Data inventory and data flows
      • Completed list of data localization obligations

      Materials

      Participants

      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Privacy team
      • Security team
      • Legal team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      3.3.2 Integrate obligations into your IT system design

      1-2 hours

      1. Work with your IT department to design the IT architecture and systems to satisfy the data localization requirements.
      2. The table below provides a checklist for integrating privacy considerations into your IT systems.

      Item

      Consideration

      Answer

      Supporting Document

      1

      Have you identified business services that process data that will be subject to localization requirements?

      2

      Have you identified IT systems associated with the business services mentioned above?

      3

      Have you established a data inventory (i.e. data types, business purposes) for the IT systems mentioned above?

      4

      Have you established a data flow diagram for the data identified above?

      5

      Have you identified the types of data that should be stored locally?

      6

      Have you confirmed whether a copy of the data locally stored will satisfy the obligations?

      7

      Have you confirmed whether an IT redesign is needed or whether modifications (e.g. adding a server) to the IT systems would satisfy the obligations?

      8

      Have you confirmed whether access from another jurisdiction is allowed?

      9

      Have you identified how long the data should be stored?

      Input

      Output

      • Data localization obligations
      • Business services that process data that will be subject to localization requirements
      • IT systems associated with business services
      • Data inventory and data flows
      • Completed checklist of localization obligations for IT system design

      Materials

      Participants

      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Privacy team
      • Security team
      • Legal team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      Compliance with local obligations

      Likelihood: Medium to High

      Impact: High

      Cross-Border Transfer

      Gap Controls

      • Know where you transfer your data.
      • Identify jurisdictions that your organization is operating in and that impose different requirements for the cross-border transfer of personal data.
      • Adopt and implement a proper cross-border data transfer mechanism in accordance with applicable privacy laws and regulations.
      • Re-evaluate at appropriate intervals.

      Which cross-border transfer mechanism should I choose?

      Transfer Mechanism

      Advantages

      Disadvantages

      Standard Contractual Clauses (SCC)

      • Easy to implement
      • No DPA (data processing agreement) approval
      • Not suitable for complex data transfers
      • Do not meet business agility
      • Needs legal solution

      Binding Corporate Rules (BCRs)

      • Meets business agility needs
      • Raises trust in the organization
      • Doubles as solution for art. 24/25 of the GDPR
      • Sets high compliance maturity level
      • Takes time to draft/implement
      • Requires DPA approval (scrutiny)
      • Requires culture of compliance
      • Approved by one "lead" authority and two other "co-lead“ authorities
      • Takes usually between six and nine months for the approval process only

      Code of Conduct

      • Raises trust in the sector
      • Self-regulation instead of law
      • No code of conduct approved yet
      • Takes time to draft/implement
      • Requires DPA approval and culture of compliance
      • Needs of organization may not be met

      Certification

      • Raises trust in the organization
      • No certification schemes available yet
      • Risk of compliance at minimum necessary
      • Requires audits

      Consent

      • Legal certainty
      • Transparent
      • Administrative burden
      • Some data subjects are incapable of consenting all or nothing

      3.3.3 Document data processing activities

      1-2 hours

      1. Identify and document the following information:
        • Name of business process
        • Purposes of processing
        • Lawful basis
        • Categories of data subjects and personal data
        • Data subject categories
        • Which system the data resides in
        • Recipient categories
        • Third country/international organization
        • Documents for appropriate safeguards for international transfer (adequacy, SCCs, BCRs, etc.)
        • Description of mitigating measures

      Input

      Output

      • Name of business process
      • Categories of personal data
      • Which system the data resides
      • Third country/international organization
      • Documents for appropriate safeguards for international transfer
      • Completed list of data processing activities

      Materials

      Participants

      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Privacy team
      • Security team
      • Legal team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      3.3.4 Choose the right mechanism

      1-2 hours

      1. Identify jurisdictions that your organization is operating in and that impose different requirements for the cross-border transfer of personal data. For example, the EU’s GDPR and China’s Personal Information Protection Law require proper cross-border transfer mechanisms before the data transfers. Your organization should decide which cross-border transfer mechanism is the best fit for your cross-border data transfer scenarios.
      2. Use the following table to identify and document the pros and cons of each data transfer mechanism and the final decision.

      Data Transfer Mechanism

      Pros

      Cons

      Final Decision

      SCC

      BCR

      Code of Conduct

      Certification

      Consent

      Input

      Output

      • List of relevant data transfer mechanisms
      • Assessment of the pros and cons of each mechanism
      • Final decision regarding which data transfer mechanism is the best fit for your organization

      Materials

      Participants

      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Privacy team
      • Security team
      • Legal team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      3.3.5 Implement the appropriate controls

      1-3 hours

      • One of the most common mechanisms is standard contractual clauses (SCCs).
      • Use Info-Tech’s Standard Contractual Clauses Template to facilitate your cross-border transfer activities.
      • Identify and check whether the following core components are covered in your SCC and record the results in the table below.
      # Core Components Status Note
      1 Purpose and scope
      2 Effect and invariability of the Clauses
      3 Description of the transfer(s)
      4 Data protection safeguards
      5 Purpose limitation
      6 Transparency
      7 Accuracy and data minimization
      8 Duration of processing and erasure or return of data
      9 Storage limitation
      10 Security of processing
      11 Sensitive data
      12 Onward transfers
      13 Processing under the authority of the data importer
      14 Documentation and compliance
      15 Use of subprocessors
      16 Data subject rights
      17 Redress
      18 Liability
      19 Local laws and practices affecting compliance with the Clauses
      20 Noncompliance with the Clauses and termination
      21 Description of data processing activities, such as list of parties, description of transfer, etc.
      22 Technical and organizational measures
      InputOutput
      • Description of the transfer(s)
      • Duration of processing and erasure or return of data
      • Onward transfers
      • Use of subprocessors
      • Etc.
      • Draft of the standard contractual clauses (SCC)
      MaterialsParticipants
      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Legal team
      • Privacy team
      • Security team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      Compliance with local obligations

      Likelihood: High

      Impact: Medium to High

      Data Breach

      Gap Controls

      • Identify jurisdictions that your organization is operating in and that impose different obligations for data breach reporting.
      • Document the notification obligations for various business scenarios, such as controller to DPA, controller to data subject, and processor to controller.
      • Integrate breach notification obligations into security incident response process.

      Examples of Data Breach Notification Obligations

      Location

      Regulation/ Standard

      Reporting Obligation

      EU

      GDPR

      72 hours

      China

      PIPL

      Immediately

      US

      HIPAA

      No later than 60 days

      Canada

      PIPEDA

      As soon as feasible

      Global

      PCI DSS

      • Visa – immediately after breach discovered
      • Mastercard – within 24 hours of discovering breach
      • American Express – immediately after breach discovered

      Summary of US State Data Breach Notification Statutes

      The image contains a graph to show the summary of the US State Data Breach Notification Statutes.

      Source: Davis Wright Tremaine

      3.3.6 Identify data breach notification obligations

      1-2 hours

      1. Identify jurisdictions that your organization is operating in and that impose different obligations for data breach reporting.
      2. Document the notification obligations for various business scenarios, such as controller to DPA, controller to data subject, and processor to controller.
      3. Record your data breach obligations in the table below.
      Region Regulation/Standard Reporting Obligation

      Input

      Output

      • List of regions and jurisdictions your business is operating in
      • List of relevant regulations and standards
      • Documentation of data breach reporting obligations in applicable jurisdictions

      Materials

      Participants

      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Legal team
      • Privacy team
      • Security team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      3.3.7 Integrate data breach notification into incident response

      1-2 hours

      • Integrate breach notification obligations into the security incident response process. Understand the security incident management framework.
      • All incident runbooks follow the same process: detection, analysis, containment, eradication, recovery, and post-incident activity.
      • The table below provides a basic checklist for you to consider when implementing your data breach and incident handling process.
      # Phase Considerations Status Notes
      1 Prepare Ensure the appropriate resources are available to best handle an incident.
      2 Detect Leverage monitoring controls to actively detect threats.
      3 Analyze Distill real events from false positives.
      4 Contain Isolate the threat before it can cause additional damage.
      5 Eradicate Eliminate the threat from your operating environment.
      6 Recover Restore impacted systems to a normal state of operations.
      7 Report Report data breaches to relevant regulators and data subjects if required.
      8 Post-Incident Activities Conduct a lessons-learned post-mortem analysis.
      InputOutput
      • Security and data protection incident response steps
      • Key considerations for integrating data breach notifications into incident response
      • Data breach notifications integrated into the incident response process
      MaterialsParticipants
      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Security team
      • Privacy team
      • Legal team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      Compliance with local obligations

      Likelihood: High

      Impact: Medium to High

      Third-Party Risk

      Gap Controls

      • Build an end-to-end third-party security and privacy risk management process.
      • Perform internal due diligence prior to selecting a service provider.
      • Stipulate the security and privacy protection obligations of the third party in a legally binding document such as contract or data processing agreement, etc.

      End-to-End Third-Party Security and Privacy Risk Management

      1. Pre-Contract
      • Due diligence check
    • Signing of Contract
      • Data processing agreement
    • Post-Contract
      • Continuous monitoring
      • Regular check or audit
    • Termination of Contract
      • Data deletion
      • Access deprovisioning

      Examples of Vendor Security Management Requirements

      Region

      Law/Standard

      Section

      EU

      General Data Protection Regulation (GDPR)

      Article 28 (1)

      Article 46 (1)

      US

      Health Insurance Portability and Accountability Act (HIPAA)

      §164.308(b)(1)

      US

      New York Department of Financial Services Cybersecurity Requirements

      500.11(a)

      Global

      ISO 27002:2013

      15.1.1

      15.1.2

      15.1.3

      15.2.1

      15.2.2

      US

      NIST 800-53

      SA-12

      SA-12 (2)

      US

      NIST Cybersecurity Framework

      ID-SC-1

      ID-SC-2

      ID-SC-3

      ID-SC-4

      Canada

      OSFI Cybersecurity Guidelines

      4.25

      4.26

      3.3.8 Identify vendor security and data protection requirements

      1-2 hours

      • Effective vendor security risk management is an end-to-end process that includes assessment, risk mitigation, and periodic reassessments.
      • An efficient and effective assessment process can only be achieved when all stakeholders are participating.
      • Identify and document your vendor security and data protection requirements in the table below.
      Region Law/Standard Section Requirements

      Input

      Output

      • List of regions and jurisdictions your business is operating in
      • List of relevant regulations and standards
      • Documentation of vendor security and data protection obligations in applicable jurisdictions

      Materials

      Participants

      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Legal team
      • Privacy team
      • Security team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      3.3.9 Build due diligence questionnaire

      1-2 hours

      Perform internal due diligence prior to selecting a service provider.

      1. Build and right-size your vendor security questionnaire by leveraging Info-Tech’s Vendor Security Questionnaire template.
      2. Document your vendor security questionnaire in the table below.
      # Question Vendor Request Vendor Comments
      1 Document Requests
      2 Asset Management
      3 Governance
      4 Supply Chain Risk Management
      5 Identify Management, Authentication, and Access Control
      InputOutput
      • List of regions and jurisdictions your business is operating in
      • List of relevant regulations and standards
      • Business security and data protection requirements and expectations
      • Draft of due diligence questionnaire
      MaterialsParticipants
      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Legal team
      • Privacy team
      • Security team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      3.3.10 Build appropriate data processing agreement

      1-2 hours

      1. Stipulate the security and privacy protection obligations of the third party in a legally binding document such as contract or data processing agreement, etc.
      2. Leverage Info-Tech’s Data Processing Agreement Template to put the language into your legally binding document.
      3. Use the table below to check whether core components of a typical DPA are covered in your document.
      # Core Components Status Note
      1 Processing of personal data
      2 Scope of application and responsibilities
      3 Processor's obligations
      4

      Controller's obligations

      5 Data subject requests
      6 Right to audit and inspection
      7 Subprocessing
      8 Data breach management
      9 Security controls
      10 Transfer of personal data
      11 Duty of confidentiality
      12 Compliance with applicable laws
      13 Service termination
      14 Liability and damages
      InputOutput
      • Processing of personal data
      • Processor’s obligations
      • Controller’s obligations
      • Subprocessing
      • Etc.
      • Draft of data processing agreement (DPA)
      MaterialsParticipants
      • Guidelines for Compliance With Local Security and Privacy Laws Template
      • Legal team
      • Privacy team
      • Security team
      • IT leadership
      • Risk Management

      Download the Guidelines for Compliance With Local Security and Privacy Laws Template

      Summary of Accomplishment

      Problem Solved

      By following Info-Tech’s methodology for securing global operations, you have:

      • Evaluated the security context of your organization’s global operations.
      • Identified security risks scenarios unique to high-risk jurisdictions and assessed the exposure of critical assets.
      • Planned and executed a response.

      You have gone through a deeper analysis of two key risk scenarios that affect global operations:

      • Travel to high-risk jurisdictions.
      • Compliance risk.

      If you would like additional support, have our analysts guide you through an Info-Tech workshop or Guided Implementation.

      Contact your account representative for more information.

      workshop@infotech.com

      1-888-670-8889

      Additional Support

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech Workshop.

      The image contains a picture of Michel Hebert.

      Contact your account representative for more information.

      workshops@infotech.com 1-888-670-8889

      To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team. Info-Tech analysts will join you and your team at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      The image contains a screenshot of High-Risk Travel Jurisdictions.

      Identify High-Risk Jurisdictions

      Develop requirements to identify high-risk jurisdictions.

      The image contains a screenshot of Build Risk Scenarios.

      Build Risk Scenarios

      Build risk scenarios to capture assets, vulnerabilities, threats, and the potential effect of a compromise.

      External Research Contributors

      Ken Muir

      CISO

      LMC Security

      Premchand Kurup

      CEO

      Paramount Computer Systems

      Preeti Dhawan

      Manager, Security Governance

      Payments Canada

      Scott Wiggins

      Information Risk and Governance

      CDPHP

      Fritz Y. Jean Louis

      CISO

      Globe and Mail

      Eric Gervais

      CIO

      Ovivo Water

      David Morrish

      CEO

      MBS Techservices

      Evan Garland

      Manager, IT Security

      Camosun College

      Jacopo Fumagalli

      CISO

      Axpo

      Dennis Leon

      Governance and Security Manager

      CPA Canada

      Tero Lehtinen

      CIO

      Planmeca Oy

      Related Info-Tech Research

      Build an IT Risk Management Program

      • Build a program to identify, evaluate, assess, and treat IT risks.
      • Monitor and communicate risks effectively to support business decision making.

      Combine Security Risk Management Components Into One Program

      • Develop a program focused on assessing and managing information system risks.
      • Build a governance structure that integrates security risks within the organization’s broader approach to risk management.

      Build an Information Security Strategy

      • Build a holistic, risk-aware strategy that aligns to business goals.
      • Develop a roadmap of prioritized initiatives to implement the strategy over 18 to 36 months.

      Bibliography

      2022 Cost of Insider Threats Global Report.” Ponemon Institute, NOVIPRO, 9 Feb. 2022. Accessed 25 May 22.

      “Allianz Risk Barometer 2022.” Allianz Global Corporate & Specialty, Jan. 2022. Accessed 25 May 22.

      Bickley, Shaun. “Security Risk Management: a basic guide for smaller NGOs”. European Interagency Security Forum (EISF), 2017. Web.

      “Biden Administration Warns against spyware targeting dissidents.” New York Times, 7 Jan 22. Accessed 20 Jan 2022.

      Boehm, Jim, et al. “The risk-based approach to cybersecurity.” McKinsey & Company, October 2019. Web.

      “Cost of a Data Breach Report 2021.” IBM Security, July 2021. Web.

      “Cyber Risk in Asia-Pacific: The Case for Greater Transparency.” Marsh & McLennan Companies, 2017. Web.

      “Cyber Risk Index.” NordVPN, 2020. Accessed 25 May 22

      Dawson, Maurice. “Applying a holistic cybersecurity framework for global IT organizations.” Business Information Review, vol. 35, no. 2, 2018, pp. 60-67.

      “Framework for improving critical infrastructure cybersecurity.” National Institute of Standards and Technology, 16 Apr 2018. Web.

      “Global Cybersecurity Index 2020.” International Telecommunication Union (ITU), 2021. Accessed 25 May 22.

      “Global Risk Survey 2022.” Control Risks, 2022. Accessed 25 May 22.

      “International Travel Guidance for Government Mobile Devices.” Federal Mobility Group (FMG), Aug. 2021. Accessed 18 Nov 2021.

      Kaffenberger, Lincoln, and Emanuel Kopp. “Cyber Risk Scenarios, the Financial System, and Systemic Risk Assessment.” Carnegie Endowment for International Peace, September 2019. Accessed 11 Jan 2022.

      Koehler, Thomas R. Understanding Cyber Risk. Routledge, 2018.

      Owens, Brian. “Cybersecurity for the travelling scientist.” Nature, vol. 548, 3 Aug 2017. Accessed 19 Jan. 2022.

      Parsons, Fintan J., et al. “Cybersecurity risks and recommendations for international travellers.” Journal of Travel Medicine, vol. 1, no. 4, 2021. Accessed 19 Jan 2022.

      Quinn, Stephen, et al. “Identifying and estimating cybersecurity risk for enterprise risk management.” National Institute of Standards and Technology (NIST), Interagency or Internal Report (IR) 8286A, Nov. 2021.

      Quinn, Stephen, et al. “Prioritizing cybersecurity risk for enterprise risk management.” NIST, IR 8286B, Sept. 2021.

      “Remaining cyber safe while travelling security recommendations.” Government of Canada, 27 April 2022. Accessed 31 Jan 2022.

      Stine, Kevin, et al. “Integrating cybersecurity and enterprise risk management.” NIST, IR 8286, Oct. 2020.

      Tammineedi, Rama. “Integrating KRIs and KPIs for effective technology risk management.” ISACA Journal, vol. 4, 1 July 2018.

      Tikk, Eneken, and Mika Kerttunen, editors. Routledge Handbook of International Cybersecurity. Routledge, 2020.

      Voo, Julia, et al. “National Cyber Power Index 2020.” Belfer Center for Science and International Affairs, Harvard Kennedy School, Sept. 2020. Web.

      Zhang, Fang. “Navigating cybersecurity risks in international trade.” Harvard Business Review, Dec 2021. Accessed 31 Jan 22.

      Appendix

      Insider Threat

      Key Risk Scenario

      Likelihood: Medium to High

      Impact: High

      Gap Controls

      The image contains a picture of the Gap Controls. The controls include: Policy and Awareness, Identification, Monitoring and Visibility, which leads to Cooperation.

      • Identification: Effective and efficient management of insider threats begins with a threat and risk assessment to establish which assets and which employees to consider, especially in jurisdictions associated with sensitive or critical data. You need to pay extra attention to employees who are working in satellite offices in jurisdictions with loose security and privacy laws.
      • Monitoring and Visibility: Organizations should monitor critical assets and groups with privileged access to defend against malicious behavior. Implement an insider threat management platform that provides your organization with the visibility and context into data movement, especially cross-border transfers that might cause security and privacy breaches.
      • Policy and Awareness Training: Insider threats will persist without appropriate action and culture change. Training and consistent communication of best practices will mitigate vulnerabilities to accidental or negligent attacks. Customized training materials using local languages and role-based case studies might be needed for employees in high-risk jurisdictions.
      • Cooperation: An effective insider threat management program should be built with cross-team functions such as Security, IT, Compliance and Legal, etc.

      For more holistic approach, you can leverage our Reduce and Manage Your Organization’s Insider Threat Risk blueprint.

      Info-Tech Insight

      You can’t just throw tools at a human problem. While organizations should monitor critical assets and groups with privileged access to defend against malicious behavior, good management and supervision can help detect attacks and prevent them from happening in the first place.

      Insider threats are not industry specific, but malicious insiders are

      Industry

      Actors

      Risks

      Tactics

      Motives

      State and Local Government

      • Full-time employees
      • Current employees
      • Privileged access to personally identifiable information, financial assets, and physical property
      • Abuse of privileged access
      • Received or transferred fraudulent funds
      • Financial gain
      • Recognition
      • Benefiting foreign entity

      Information Technology

      • Equal mix of former and current employees
      • Privileged access to networks or systems as well as data
      • Highly technical attacks
      • Received or transferred fraudulent funds
      • Revenge
      • Financial gain

      Healthcare

      • Majority were full-time and current employees
      • Privileged access to customer data with personally identifiable information, financial assets
      • Abuse of privileged access
      • Received or transferred fraudulent funds
      • Financial gain
      • Entitlement

      Finance and Insurance

      • Majority were full-time and current employees
      • Authorized users
      • Electronic financial assets
      • Privileged access to customer data
      • Created or used fraudulent accounts
      • Fraudulent purchases
      • Identity theft
      • Financial gain
      • Gambling addiction
      • Family pressures
      • Multiple motivations

      Source: Carnegie Mellon University Software Engineering Institute, 2019

      Advanced Persistent Threat

      Key Risk Scenario #4

      Likelihood: Medium to High

      Impact: High

      Gap Controls

      The image contains a screenshot of the Gap Controls listed: Prevent, Detect, Analyze, Respond.

      Prevent: Defense in depth is the best approach to protect against unknown and unpredictable attacks. Effective anti-malware, diligent patching and vulnerability management, and strong human-centric security are essential.

      Detect: There are two types of companies – those who have been breached and know it, and those who have been breached and don’t know it. Ensure that monitoring, logging, and event detection tools are in place and appropriate to your organizational needs.

      Analyze: Raw data without interpretation cannot improve security and is a waste of time, money, and effort. Establish a tiered operational process that not only enriches data but also provides visibility into your threat landscape.

      Respond: Organizations can’t rely on ad hoc response anymore – don’t wait until a state of panic. Formalize your response processes in a detailed incident runbook to reduce incident remediation time and effort.

      Best practices moving forward

      Defense in Depth

      Lock down your organization. Among other tactics, control administrative privileges, leverage threat intelligence, use IP whitelisting, adopt endpoint protection and two-factor authentication, and formalize incident response measures.

      Block Indicators

      Information alone is not actionable. A successful threat intelligence program contextualizes threat data, aligns intelligence with business objectives, and then builds processes to satisfy those objectives. Actively block indicators and act upon gathered intelligence.

      Drive Adoption

      Create organizational situational awareness around security initiatives to drive adoption of foundational security measures: network hardening, threat intelligence, red-teaming exercises, and zero-day mitigation, policies, and procedures.

      Supply Chain Security

      Security extends beyond your organization. Ensure your organization has a comprehensive view of your organizational threat landscape and a clear understanding of the security posture of any managed service providers in your supply chain.

      Awareness and Training

      Conduct security awareness and training. Teach end users how to recognize current cyberattacks before they fall victim – this is a mandatory first line of defense.

      Additional Resources

      Follow only official sources of information to help you assess risk

      The image contains an image highlighting a few additional resources.

      As misinformation is a major attack vector for malicious actors, follow only reliable sources for cyberalerts and actionable intelligence. Aggregate information from these reliable sources.

      Federal Cyber Agency Alerts

      Informational Resources

      Info-Tech Insight

      The CISA Shields Up site provides the latest cyber risk updates on the Russia-Ukraine conflict and should provide the most value in staying informed.

      Structure the Role of the DBA

      • Buy Link or Shortcode: {j2store}273|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Business Intelligence Strategy
      • Parent Category Link: /business-intelligence-strategy
      • The traditional role of Database Administrators (DBAs) is shifting due to a variety of changes such as cloud databases, increased automation, close relations with development, and the need for more integration with the business at large. All this means that organizations will have to adapt to integrate a new type of DBA into IT.
      • Organizations often have difficulty establishing a refined and effective DBA structure based on repeatable and well-grounded processes.
      • The relationship between DBAs and the rest of IT (especially development) can often be problematic due to a lack of mutual co-operation and clear communication.
      • There is often confusion in organizations as how to approach staffing DBAs.

      Our Advice

      Critical Insight

      • An organization’s relative focus on operations or development is essential in determining many DBA related decisions. This focus can determine what kinds of DBAs to hire, what staffing ratios to use, the viability of outsourcing, and the appropriate reporting structure for DBAs.
      • Utilizing technological strategies such as database automation, effective auditing, and database consolidation to bolster the DBA team helps make efficient use of DBA staff and can turn a reactive environment into a proactive one.
      • Ensuring refined and regularly assessed processes are in place for change and incident management is essential for maintaining effective and structured database administration.

      Impact and Result

      • Right-size, support, and structure your DBA team for increased cost effectiveness and optimal productivity.
      • Develop a superior level of co-operation between DBAs and the rest of IT as well as the business at large.
      • Build an environment in which DBAs will be motivated and flourish.

      Structure the Role of the DBA Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Understand how Database Administrators are evolving

      Develop an effective structure for managing and supporting Database Administrators.

      • Storyboard: Structure the Role of the DBA

      2. Create the right Database Administrator roles to meet organizational needs

      Build a team that is relevant to the focus of the organization.

      • System Database Administrator
      • Application Database Administrator
      [infographic]

      Legacy Active Directory Environment

      • Buy Link or Shortcode: {j2store}471|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Cloud Strategy
      • Parent Category Link: /cloud-strategy

      You are looking to lose your dependency on Active Directory (AD), and you need to tackle infrastructure technical debt, but there are challenges:

      • Legacy apps that are in maintenance mode cannot shed their AD dependency or have hardware upgrades made.
      • You are unaware of what processes depend on AD and how integrated they are.
      • Departments invest in apps that are integrated with AD without informing you until they ask for Domain details after purchasing.

      Our Advice

      Critical Insight

      • Remove your dependency on AD one application at a time. If you are a cloud-first organization, rethink your AD strategy to ask “why” when you add a new device to your Active Directory.
      • With the advent of hybrid work, AD is now a security risk. You need to shore up your security posture. Think of zero trust architecture.
      • Take inventory of your objects that depend on Kerberos and NTML and plan on removing that barrier through applications that don’t depend on AD.

      Impact and Result

      Don’t allow Active Directory services to dictate your enterprise innovation and modernization strategies. Determine if you can safely remove objects and move them to a cloud service where your Azure AD Domain Services can handle your authentication and manage users and groups.

      Legacy Active Directory Environment Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Legacy Active Directory Environment Deck – Legacy AD was never built for modern infrastructure. Understand the history and future of Active Directory and what alternatives are in the market.

      Build all new systems with cloud integration in mind. Many applications built in the past had built-in AD components for access, using Kerberos and NTLM. This dependency has prevented organizations from migrating away from AD. When assessing new technology and applications, consider SaaS or cloud-native apps rather than a Microsoft-dependent application with AD ingrained in the code.

      • Legacy Active Directory Environment Storyboard
      [infographic]

      Further reading

      Legacy Active Directory Environment

      Kill the technical debt of your legacy Active Directory environment.

      Analyst Perspective

      Understand what Active Directory is and why Azure Active Directory does not replace it.

      It’s about Kerberos and New Technology LAN Manager (NTLM).

      The image contains a picture of John Donovan.

      Many organizations that want to innovate and migrate from on-premises applications to software as a service (SaaS) and cloud services are held hostage by their legacy Active Directory (AD). Microsoft did a good job taking over from Novell back in the late 90s, but its hooks into businesses are so deep that many have become dependent on AD services to manage devices and users, when in fact AD falls far short of needed capabilities, restricting innovation and progress.

      Despite Microsoft’s Azure becoming prominent in the world of cloud services, Azure AD is not a replacement for on-premises AD. While Azure AD is a secure authentication store that can contain users and groups, that is where the similarities end. In fact, Microsoft itself has an architecture to mitigate the shortcomings of Azure AD by recommending organizations migrate to a hybrid model, especially for businesses that have an in-house footprint of servers and applications.

      If you are a greenfield business and intend to take advantage of software, infrastructure, and platform as a service (SaaS, IaaS, and PaaS), as well as Microsoft 365 in Azure, then Azure AD is for you and you don’t have to worry about the need for AD.

      John Donovan
      Principal Director, I&O Practice
      Info-Tech Research Group

      Insight Summary

      Legacy AD was never built for modern infrastructure

      When Microsoft built AD as a free component for the Windows Server environment to replace Windows NT before the demise of Novell Directory Services in 2001, it never meant Active Directory to work outside the corporate network with Microsoft apps and devices. While it began as a central managing system for users and PCs on Microsoft operating systems, with one user per PC, the IT ecosystem has changed dramatically over the last 20 years, with cloud adoption, SaaS, IaaS, PaaS, and everything as a service. To make matters worse, work-from-anywhere has become a serious security challenge.

      Build all new systems with cloud integration in mind

      Many applications built in the past had built-in AD components for access, using Kerberos and NTLM. This dependency has prevented organizations from migrating away from AD. When assessing new technology and applications, consider SaaS or cloud-native apps rather than a Microsoft-dependent application with AD ingrained in the code. Ensure you are engaged when the business is assessing new apps. Stop the practice of the business purchasing apps without IT’s involvement; for example, if your marketing department is asking you for your Domain credentials for a vendor when you were not informed of this purchase.

      Hybrid AD is a solution but not a long-term goal

      Economically, Microsoft has no interest in replacing AD anytime soon. Microsoft wants that revenue and has built components like Azure AD Connect to mitigate the AD dependency issue, which is basically holding your organization hostage. In fact, Microsoft has advised that a hybrid solution will remain because, as we will investigate, Azure AD is not legacy AD.

      Executive Summary

      Your Challenge

      Common Obstacles

      Info-Tech’s Approach

      You are looking to lose your dependency on Active Directory, and you need to tackle infrastructure technical debt, but there are challenges.

      • Legacy apps that are in maintenance mode cannot shed their AD dependency or have hardware upgrades made.
      • You are unaware of what processes depend on AD and how integrated they are.
      • Departments invest in apps that are integrated with AD without informing you until they ask for Domain details after purchasing.
      • Legacy applications can prevent you from upgrading servers or may need to be isolated due to security concerns related to inadequate patching and upgrades.
      • You do not see any return on investment in AD maintenance.
      • Mergers and acquisitions can prevent you from migrating away from AD if one company is dependent on AD and the other is fully in the cloud. This increases technical debt.
      • Remove your dependency on AD one application at a time. If you are a cloud-first organization, rethink your AD strategy to ask “why” when you add a new device to your Active Directory.
      • With the advent of hybrid work, AD is now a security risk. You need to shore up your security posture. Think of zero trust architecture.
      • Take inventory of your objects that depend on Kerberos and NTML and plan on removing that barrier through applications that don’t depend on AD.

      Info-Tech Insight

      Don’t allow Active Directory services to dictate your enterprise innovation and modernization strategies. Determine if you can safely remove objects and move them to a cloud service where your Azure AD Domain Services can handle your authentication and manage users and groups.

      The history of Active Directory

      The evolution of your infrastructure environment

      From NT to the cloud

      AD 2001 Exchange Server 2003 SharePoint 2007 Server 2008 R2 BYOD Security Risk All in Cloud 2015
      • Active Directory replaces NT and takes over from Novell as the enterprise access and control plane.
      • With slow WAN links, no cellphones, no tablets, and very few laptops, security was not a concern in AD.
      • In 2004, email becomes business critical.
      • This puts pressure on links, increases replication and domains, and creates a need for multiple identities.
      • Collaboration becomes pervasive.
      • Cross domain authentication becomes prevalent across the enterprise.
      • SharePoint sites need to be connected to multiple Domain AD accounts. More multiple identities are required.
      • Exchange resource forest rolls out, causing the new forest functional level to be a more complex environment.
      • Fine-grained password policies have impacted multiple forests, forcing them to adhere to the new password policies.
      • There are powerful Domain controllers, strong LAN and WAN connections, and an increase in smartphones and laptops.
      • Audits and compliance become a focus, and mergers and acquisitions add complexity. Security teams are working across the board.
      • Cloud technology doesn’t work well with complicated, messy AD environment. Cloud solutions need simple, flat AD architecture.
      • Technology changes after 15+ years. AD becomes the backbone of enterprise infrastructure. Managers demand to move to cloud, building complexity again.

      Organizations depend on AD

      AD is the backbone of many organizations’ IT infrastructure

      73% of organizations say their infrastructure is built on AD.

      82% say their applications depend on AD data.

      89% say AD enables authenticated access to file servers.

      90% say AD is the main source for authentication.

      Source: Dimensions research: Active Directory Modernization :

      Info-Tech Insight

      Organizations fail to move away from AD for many reasons, including:

      • Lack of time, resources, budget, and tools.
      • Difficulty understanding what has changed.
      • Migrating from AD being a low priority.

      Active Directory components

      Physical and logical structure

      Authentication, authorization, and auditing

      The image contains a screenshot of the active directory components.

      Active Directory has its hooks in!

      AD creates infrastructure technical debt and is difficult to migrate away from.

      The image contains a screenshot of an active directory diagram.

      Info-Tech Insight

      Due to the pervasive nature of Active Directory in the IT ecosystem, IT organizations are reluctant to migrate away from AD to modernize and innovate.

      Migration to Microsoft 365 in Azure has forced IT departments’ hand, and now that they have dipped their toe in the proverbial cloud “lake,” they see a way out of the mounting technical debt.

      AD security

      Security is the biggest concern with Active Directory.

      Neglecting Active Directory security

      98% of data breaches came from external sources.

      Source: Verizon, Data Breach Report 2022

      85% of data breach took weeks or even longer to discover.

      Source: Verizon Data Breach Report, 2012

      The biggest challenge for recovery after an Active Directory security breach is identifying the source of the breach, determining the extent of the breach, and creating a safe and secure environment.

      Info-Tech Insight

      Neglecting legacy Active Directory security will lead to cyberattacks. Malicious users can steal credentials and hijack data or corrupt your systems.

      What are the security risks to legacy AD architecture?

      • It's been 22 years since AD was released by Microsoft, and it has been a foundational technology for most businesses over the years. However, while there have been many innovations over those two decades, like Amazon, Facebook, iPhones, Androids, and more, Active Directory has remained mostly unchanged. There hasn’t been a security update since 2016.
      • This lack of security innovation has led to several cyberattacks over the years, causing businesses to bolt on additional security measures and added complexity. AD is not going away any time soon, but the security dilemma can be addressed with added security features.

      AD event logs

      84% of organizations that had a breach had evidence of that breach in their event logs.

      Source: Verizon Data Breach Report, 2012

      What is the business risk

      How does AD impact innovation in your business?

      It’s widely estimated that Active Directory remains at the backbone of 90% of Global Fortune 1000 companies’ business infrastructure (Lepide, 2021), and with that comes risk. The risks include:

      • Constraints of AD and growth of your digital footprint
      • Difficulty integrating modern technologies
      • Difficulty maintaining consistent security policies
      • Inflexible central domains preventing innovation and modernization
      • Inability to move to a self-service password portal
      • Vulnerability to being hacked
      • BYOD not being AD friendly

      AD is dependent on Windows Server

      1. Even though AD is compliant with LDAP, software vendors often choose optional features of LDAP that are not supported by AD. It is possible to implement Kerberos in a Unix system and establish trust with AD, but this is a difficult process and mistakes are frequent.
      2. Restricting your software selection to Windows-based systems reduces innovation and may hamper your ability to purchase best-in-class applications.

      Azure AD is not a replacement for AD

      AD was designed for an on-premises enterprise

      The image contains a screenshot of a Azure AD diagram.

      • Despite Microsoft’s Azure becoming prominent in the world of cloud services, Azure AD is not a replacement for on-premises AD.
      • In fact, Microsoft itself has an architecture to mitigate the shortcomings of Azure AD by recommending organizations migrate to a hybrid model, especially those businesses that have an in-house footprint of servers and applications.
      • If you are a greenfield business and intend to take advantage of SaaS, IaaS, and PaaS, as well as Microsoft 365 in Azure, then Azure AD is for you and you don’t have to worry about the need for AD.

      "Azure Active Directory is not designed to be the cloud version of Active Directory. It is not a domain controller or a directory in the cloud that will provide the exact same capabilities with AD. It actually provides many more capabilities in a different way.

      That’s why there is no actual ‘migration’ path from Active Directory to Azure Active Directory. You can synchronize your on-premises directories (Active Directory or other) to Azure Active Directory but not migrate your computer accounts, group policies, OU etc."

      – Gregory Hall,
      Brand Representative for Microsoft
      (Source: Spiceworks)

      The hybrid model for AD and Azure AD

      How the model works

      The image contains a screenshot of a hybrid model for AD and Azure AD.

      Note: AD Federated Services (ADFS) is not a replacement for AD. It’s a bolt-on that requires maintenance, support, and it is not a liberating service.

      Many companies are:

      • Moving to SaaS solutions for customer relationship management, HR, collaboration, voice communication, file storage, and more.
      • Managing non-Windows devices.
      • Moving to a hybrid model of work.
      • Enabling BYOD.

      Given these trends, Active Directory is becoming obsolete in terms of identity management and permissions.

      The difference between AD Domain Services and Azure AD DS

      One of the core principles of Azure AD is that the user is the security boundary, not the network.

      Kerberos is the default authentication and authorization protocol for AD. Kerberos is involved in nearly everything from the time you log on to accessing Sysvol, which is used to deliver policy and logon scripts to domain members from the Domain Controller.

      Info-Tech Insight

      If you are struggling to get away from AD, Kerberos and NTML are to blame. Working around them is difficult. Azure AD uses SAML2.0 OpenID Connect and OAuth2.0.

      Feature Azure AD DS Self-managed AD DS
      Managed service
      Secure deployments Administrator secures the deployment
      DNS server ✓ (managed service)
      Domain or Enterprise administrator privileges
      Domain join
      Domain authentication using NTLM and Kerberos
      Kerberos-constrained delegation Resource-based Resource-based and account-based
      Custom OU structure
      Group Policy
      Schema extensions
      AD domain/forest trusts ✓ (one-way outbound forest trusts only)
      Secure LDAP (LDAPS)
      LDAP read
      LDAP write ✓ (within the managed domain)
      Geo-distributed deployments

      Source: “Compare self-managed Active Directory Domain Services...” Azure documentation, 2022

      Impact of work-from-anywhere

      How AD poses issues that impact the user experience

      IT organizations are under pressure to enable work-from-home/work-from-anywhere.

      • IT teams regard legacy infrastructure, namely Active Directory, as inadequate to securely manage remote workloads.
      • While organizations previously used VPNs to access resources through Active Directory, they now have complex webs of applications that do not reside on premises, such as AWS, G-Suite, and SaaS customer relationship management and HR management systems, among others. These resources live outside the Windows ecosystem, complicating user provisioning, management, and security.
      • The work environment has changed since the start of COVID-19, with businesses scrambling to enable work-from-home. This had a huge impact on on-premises identity management tools such as AD, exposing their limitations and challenges. IT admins are all too aware that AD does not meet the needs of work-from-home.
      • As more IT organizations move infrastructure to the cloud, they have the opportunity to move their directory services to the cloud as well.
        • JumpCloud, OneLogin, Okta, Azure AD, G2, and others can be a solution for this new way of working and free up administrators from the overloaded AD environment.
        • Identity and access management (IAM) can be moved to the cloud where the modern infrastructure lives.
        • Alternatives for printers using AD include Google Cloud Print, PrinterOn, and PrinterLogic.

      How AD can impact your migration to Microsoft 365

      The beginning of your hybrid environment

      • Businesses that have a large on-premises footprint have very few choices for setting up a hybrid environment that includes their on-premises AD and Azure AD synchronization.
      • Microsoft 365 uses Azure AD in the background to manage identities.
      • Azure AD Connect will need to be installed, along with IdFix to identify errors such as duplicates and formatting problems in your AD.
      • Password hash should be implemented to synchronize passwords from on-premises AD so users can sign in to Azure without the need for additional single sign-on infrastructure.
      • Azure AD Connect synchronizes accounts every 30 minutes and passwords within two minutes.

      Alternatives to AD

      When considering retiring Active Directory from your environment, look at alternatives that can assist with those legacy application servers, handle Kerberos and NTML, and support LDAP.

      • JumpCloud: Cloud-based directory services. JumpCloud provides LDAP-as-a-Service and RADIUS-as-a-Service. It authenticates, authorizes, and manages employees, their devices, and IT applications. However, domain name changes are not supported.
      • Apache Directory Studio Pro: Written in Java, it supports LDAP v3–certified directory services. It is certified by Eclipse-based database utilities. It also supports Kerberos, which is critical for legacy Microsoft AD apps authentication.
      • Univention Corporate Server (UCS): Open-source Linux-based solution that has a friendly user interface and gets continuous security and feature updates. It supports Kerberos V5 and LDAP, works with AD, and is easy to sync. It also supports DNS server, DHCP, multifactor authentication and single sign-on, and APIs and REST APIs. However, it has a limited English knowledgebase as it is a German tool.

      What to look for

      If you are embedded in Windows systems but looking for an alternative to AD, you need a similar solution but one that is capable of working in the cloud and on premises.

      Aside from protocols and supporting utilities, also consider additional features that can help you retire your Active Directory while maintaining highly secure access control and a strong security posture.

      These are just a few examples of the many alternatives available.

      Market drivers to modernize your infrastructure

      The business is now driving your Active Directory migration

      What IT must deal with in the modern world of work:

      • Leaner footprint for evolving tech trends
      • Disaster recovery readiness
      • Dynamic compliance requirements
      • Increased security needs
      • The need to future-proof
      • Mergers and acquisitions
      • Security extending the network beyond Windows

      Organizations are making decisions that impact Active Directory, from enabling work-from-anywhere to dealing with malicious threats such as ransomware. Mergers and acquisitions also bring complexity with multiple AD domains.
      The business is putting pressure on IT to become creative with security strategies, alternative authentication and authorization, and migration to SaaS and cloud services.

      Activity

      Build a checklist to migrate off Active Directory.

      Discovery

      Assessment

      Proof of Concept

      Migration

      Cloud Operations

      ☐ Catalog your applications.

      ☐ Define your users, groups and usage.

      ☐ Identify network interdependencies and complexity.

      ☐ Know your security and compliance regulations.

      ☐ Document your disaster recovery plan and recovery point and time objectives (RPO/RTO).

      ☐ Build a methodology for migrating apps to IaaS.

      ☐ Develop a migration team using internal resources and/or outsourcing.

      ☐ Use Microsoft resources for specific skill sets.

      ☐ Map on-premises third-party solutions to determine how easily they will migrate.

      ☐ Create a plan to retire and archive legacy data.

      ☐ Test your workload: Start small and prove value with a phased approach.

      ☐ Estimate cloud costs.

      ☐ Determine the amount and size of your compute and storage requirements.

      ☐ Understand security requirements and the need for network and security controls.

      ☐ Assess network performance.

      ☐ Qualify and test the tools and solutions needed for the migration.

      ☐ Create a blueprint of your desired cloud environment.

      ☐ Establish a rollback plan.

      ☐ Identify tools for automating migration and syncing data.

      ☐ Understand the implications of the production-day data move.

      ☐ Keep up with the pace of innovation.

      ☐ Leverage 24/7 support via skilled Azure resources.

      ☐ Stay on top of system maintenance and upgrades.

      ☐ Consider service-level agreement requirements, governance, security, compliance, performance, and uptime.

      Related Info-Tech Research

      Manage the Active Directory in the Service Desk

      • Build and maintain your Active Directory with good data.
      • Actively maintaining the Active Directory is a difficult task that only gets more difficult with issues like stale accounts and privilege creep.

      SoftwareReviews: Microsoft Azure Active Directory

      • The Azure Active Directory (Azure AD) enterprise identity service provides SSO and multifactor authentication to help protect your users from 99.9% of cybersecurity attacks

      Define Your Cloud Vision

      • Don’t think about the cloud as an inevitable next step for all workloads. The cloud is merely another tool in the toolbox, ready to be used when appropriate and put away when it’s not needed. Cloud-first isn’t always the way to go.

      Bibliography

      “2012 Data Breach Investigations Report.” Verizon, 2012. Web.
      “2022 Data Breach Investigations Report.” Verizon, 2012. Web.
      “22 Best Alternatives to Microsoft Active Directory.” The Geek Page, 16 Feb 2022. Accessed 12 Sept. 2022.
      Altieri, Matt. “Infrastructure Technical Debt.” Device 42, 20 May 2019. Accessed Sept 2022.
      “Are You Ready to Make the Move from ADFS to Azure AD?’” Steeves and Associates, 29 April 2021. Accessed 28 Sept. 2022.
      Blanton, Sean. “Can I Replace Active Directory with Azure AD? No, Here’s Why.” JumpCloud, 9 Mar 2021. Accessed Sept. 2022.
      Chai, Wesley, and Alexander S. Gillis. “What is Active Directory and how does it work?” TechTarget, June 2021. Accessed 10 Sept. 2022.
      Cogan, Sam. “Azure Active Directory is not Active Directory!” SamCogan.com, Oct 2020. Accessed Sept. 2022.
      “Compare Active Directory to Azure Active Directory.” Azure documentation, Microsoft Learn, 18 Aug. 2022. Accessed 12 Sept. 2022.
      "Compare self-managed Active Directory Domain Services, Azure Active Directory, and managed Azure Active Directory Domain Services." Azure documentation, Microsoft Learn, 23 Aug. 2022. Accessed Sept. 2022.
      “Dimensional Research, Active Directory Modernization: A Survey of IT Professionals.” Quest, 2017. Accessed Sept 2022.
      Grillenmeier, Guido. “Now’s the Time to Rethink Active Directory Security.“ Semperis, 4 Aug 2021. Accessed Oct. 2013.
      “How does your Active Directory align to today’s business?” Quest Software, 2017, accessed Sept 2022
      Lewis, Jack “On-Premises Active Directory: Can I remove it and go full cloud?” Softcat, Dec.2020. Accessed 15 Sept 2022.
      Loshin, Peter. “What is Kerberos?” TechTarget, Sept 2021. Accessed Sept 2022.
      Mann, Terry. “Why Cybersecurity Must Include Active Directory.” Lepide, 20 Sept. 2021. Accessed Sept. 2022.
      Roberts, Travis. “Azure AD without on-prem Windows Active Directory?” 4sysops, 25 Oct. 2021. Accessed Sept. 2022.
      “Understanding Active Directory® & its architecture.” ActiveReach, Jan 2022. Accessed Sept. 2022.
      “What is Active Directory Migration?” Quest Software Inc, 2022. Accessed Sept 2022.

      Optimize IT Change Management

      • Buy Link or Shortcode: {j2store}409|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: $33,585 Average $ Saved
      • member rating average days saved: 27 Average Days Saved
      • Parent Category Name: Operations Management
      • Parent Category Link: /i-and-o-process-management
      • Infrastructure managers and change managers need to re-evaluate their change management processes due to slow change turnaround time, too many unauthorized changes, too many incidents and outages because of poorly managed changes, or difficulty evaluating and prioritizing changes.
      • IT system owners often resist change management because they see it as slow and bureaucratic.
      • Infrastructure changes are often seen as different from application changes, and two (or more) processes may exist.

      Our Advice

      Critical Insight

      • ITIL provides a usable framework for change management, but full process rigor is not appropriate for every change request.
      • You need to design a process that is flexible enough to meet the demand for change, and strict enough to protect the live environment from change-related incidents.
      • A mature change management process will minimize review and approval activity. Counterintuitively, with experience in implementing changes, risk levels decline to a point where most changes are “pre-approved.”

      Impact and Result

      • Create a unified change management process that reduces risk. The process should be balanced in its approach toward deploying changes while also maintaining throughput of innovation and enhancements.
      • Categorize changes based on an industry-standard risk model with objective measures of impact and likelihood.
      • Establish and empower a change manager and change advisory board with the authority to manage, approve, and prioritize changes.
      • Integrate a configuration management database with the change management process to identify dependencies.

      Optimize IT Change Management Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should optimize change management, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      • Optimize IT Change Management – Phases 1-4

      1. Define change management

      Assess the maturity of your existing change management practice and define the scope of change management for your organization.

      • Change Management Maturity Assessment Tool
      • Change Management Risk Assessment Tool

      2. Establish roles and workflows

      Build your change management team and standardized process workflows for each change type.

      • Change Manager
      • Change Management Process Library – Visio
      • Change Management Process Library – PDF
      • Change Management Standard Operating Procedure

      3. Define the RFC and post-implementation activities

      Bookend your change management practice by standardizing change intake, implementation, and post-implementation activities.

      • Request for Change Form Template
      • Change Management Pre-Implementation Checklist
      • Change Management Post-Implementation Checklist

      4. Measure, manage, and maintain

      Form an implementation plan for the project, including a metrics evaluation, change calendar inputs, communications plan, and roadmap.

      • Change Management Metrics Tool
      • Change Management Communications Plan
      • Change Management Roadmap Tool
      • Optimize IT Change Management Improvement Initiative: Project Summary Template

      [infographic]

      Workshop: Optimize IT Change Management

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Define Change Management

      The Purpose

      Discuss the existing challenges and maturity of your change management practice.

      Build definitions of change categories and the scope of change management.

      Key Benefits Achieved

      Understand the starting point and scope of change management.

      Understand the context of change request versus other requests such as service requests, projects, and operational tasks.

      Activities

      1.1 Outline strengths and challenges

      1.2 Conduct a maturity assessment

      1.3 Build a categorization scheme

      1.4 Build a risk assessment matrix

      Outputs

      Change Management Maturity Assessment Tool

      Change Management Risk Assessment Tool

      2 Establish Roles and Workflows

      The Purpose

      Define roles and responsibilities for the change management team.

      Develop a standardized change management practice for approved changes, including process workflows.

      Key Benefits Achieved

      Built the team to support your new change management practice.

      Develop a formalized and right-sized change management practice for each change category. This will ensure all changes follow the correct process and core activities to confirm changes are completed successfully.

      Activities

      2.1 Define the change manager role

      2.2 Outline the membership and protocol for the Change Advisory Board (CAB)

      2.3 Build workflows for normal, emergency, and pre-approved changes

      Outputs

      Change Manager Job Description

      Change Management Standard Operating Procedure (SOP)

      Change Management Process Library

      3 Define the RFC and Post-Implementation Activities

      The Purpose

      Create a new change intake process, including a new request for change (RFC) form.

      Develop post-implementation review activities to be completed for every IT change.

      Key Benefits Achieved

      Bookend your change management practice by standardizing change intake, implementation, and post-implementation activities.

      Activities

      3.1 Define the RFC template

      3.2 Determine post-implementation activities

      3.3 Build your change calendar protocol

      Outputs

      Request for Change Form Template

      Change Management Post-Implementation Checklist

      Project Summary Template

      4 Measure, Manage, and Maintain

      The Purpose

      Develop a plan and project roadmap for reaching your target for your change management program maturity.

      Develop a communications plan to ensure the successful adoption of the new program.

      Key Benefits Achieved

      A plan and project roadmap for reaching target change management program maturity.

      A communications plan ready for implementation.

      Activities

      4.1 Identify metrics and reports

      4.2 Build a communications plan

      4.3 Build your implementation roadmap

      Outputs

      Change Management Metrics Tool

      Change Management Communications Plan

      Change Management Roadmap Tool

      Further reading

      Optimize IT Change Management

      Right-size IT change management practice to protect the live environment.

      EXECUTIVE BRIEF

      Analyst Perspective

      Balance risk and efficiency to optimize IT change management.

      Change management (change enablement, change control) is a balance of efficiency and risk. That is, pushing changes out in a timely manner while minimizing the risk of deployment. On the one hand, organizations can attempt to avoid all risk and drown the process in rubber stamps, red tape, and bureaucracy. On the other hand, organizations can ignore process and push out changes as quickly as possible, which will likely lead to change related incidents and debilitating outages.

      Right-sizing the process does not mean adopting every recommendation from best-practice frameworks. It means balancing the efficiency of change request fulfillment with minimizing risk to your organization. Furthermore, creating a process that encourages adherence is key to avoid change implementers from skirting your process altogether.

      Benedict Chang, Research Analyst, Infrastructure and Operations, Info-Tech Research Group

      Executive Summary

      Your Challenge

      Infrastructure and application change occurs constantly and is driven by changing business needs, requests for new functionality, operational releases and patches, and resolution of incidents or problems detected by the service desk.

      IT managers need to follow a standard change management process to ensure that rogue changes are never deployed while the organization remains responsive to demand.

      Common Obstacles

      IT system owners often resist change management because they see it as slow and bureaucratic.

      At the same time, an increasingly interlinked technical environment may cause issues to appear in unexpected places. Configuration management systems are often not kept up-to-date and do not catch the potential linkages.

      Infrastructure changes are often seen as “different” from application changes and two (or more) processes may exist.

      Info-Tech’s Approach

      Info-Tech’s approach will help you:

      • Create a unified change management practice that balances risk and throughput of innovation.
      • Categorize changes based on an industry-standard risk model with objective measures of impact and likelihood.
      • Establish and empower a Change Manager and Change Advisory Board (CAB) with the authority to manage, approve, and prioritize changes.

      Balance Risk and Efficiency to Optimize IT Change Management

      Two goals of change management are to protect the live environment and deploying changes in a timely manner. These two may seem to sometimes be at odds against each other, but assessing risk at multiple points of a change’s lifecycle can help you achieve both.

      Your challenge

      This research is designed to help organizations who need to:

      • Build a right-sized change management practice that encourages adherence and balances efficiency and risk.
      • Integrate the change management practice with project management, service desk processes, configuration management, and other areas of IT and the business.
      • Communicate the benefits and impact of change management to all the stakeholders affected by the process.

      Change management is heavily reliant on organizational culture

      Having a right-sized process is not enough. You need to build and communicate the process to gather adherence. The process is useless if stakeholders are not aware of it or do not follow it.

      Increase the Effectiveness of Change Management in Your Organization

      The image is a bar graph, with the segments labelled 1 and 2. The y-axis lists numbers 1-10. Segment 1 is at 6.2, and segment 2 is at 8.6.

      Of the eight infrastructure & operations processes measured in Info-Tech’s IT Management and Governance Diagnostic (MGD) program, change management has the second largest gap between importance and effectiveness of these processes.

      Source: Info-Tech 2020; n=5,108 IT professionals from 620 organizations

      Common obstacles

      These barriers make this challenge difficult to address for many organizations:

      • Gaining buy-in can be a challenge no matter how well the process is built.
      • The complexity of the IT environment and culture of tacit knowledge for configuration makes it difficult to assess cross-dependencies of changes.
      • Each silo or department may have their own change management workflows that they follow internally. This can make it difficult to create a unified process that works well for everyone.

      “Why should I fill out an RFC when it only takes five minutes to push through my change?”

      “We’ve been doing this for years. Why do we need more bureaucracy?”

      “We don’t need change management if we’re Agile.”

      “We don’t have the right tools to even start change management.”

      “Why do I have to attend a CAB meeting when I don’t care what other departments are doing?”

      Info-Tech’s approach

      Build change management by implementing assessments and stage gates around appropriate levels of the change lifecycle.

      The image is a circle, comprised of arrows, with each arrow pointing to the next, forming a cycle. Each arrow is labelled, as follows: Improve; Request; Assess; Plan; Approve; Implement

      The Info-Tech difference:

      1. Create a unified change management process that balances risk and throughput of innovation.
      2. Categorize changes based on an industry-standard risk model with objective measures of impact and likelihood.
      3. Establish and empower a Change Manager and Change Advisory Board (CAB) with the authority to manage, approve, and prioritize changes.

      IT change is constant and is driven by:

      Change Management:

      1. Operations - Operational releases, maintenance, vendor-driven updates, and security updates can all be key drivers of change. Example: ITSM version update
        • Major Release
        • Maintenance Release
        • Security Patch
      2. Business - Business-driven changes may include requests from other business departments that require IT’s support. Examples: New ERP or HRIS implementation
        • New Application
        • New Version
      3. Service desk → Incident & Problem - Some incident and problem tickets require a change to facilitate resolution of the incident. Examples: Outage necessitating update of an app (emergency change), a user request for new functionality to be added to an existing app
        • Workaround
        • Fix
      4. Configuration Management Database (CMDB) ↔ Asset Management - In addition to software and hardware asset dependencies, a configuration management database (CMDB) is used to keep a record of changes and is queried to assess change requests.
        • Hardware
        • Software

      Insight summary

      “The scope of change management is defined by each organization…the purpose of change management is to maximize the number of successful service and product changes by ensuring that the risk have been properly assessed, authorizing changes to process, and managing the change schedule.” – ALEXOS Limited, ITIL 4

      Build a unified change management process balancing risk and change throughput.

      Building a unified process that oversees all changes to the technical environment doesn’t have to be burdensome to be effective. However, the process is a necessary starting point to identifying cross dependencies and avoiding change collisions and change-related incidents.

      Use an objective framework for estimating risk

      Simply asking, “What is the risk?” will result in subjective responses that will likely minimize the perceived risk. The level of due diligence should align to the criticality of the systems or departments potentially impacted by the proposed changes.

      Integrate your change process with your IT service management system

      Change management in isolation will provide some stability, but maturing the process through service integrations will enable data-driven decisions, decrease bureaucracy, and enable faster and more stable throughput.

      Change management and DevOps can work together effectively

      Change and DevOps tend to be at odds, but the framework does not have to change. Lower risk changes in DevOps are prime candidates for the pre-approved category. Much of the responsibility traditionally assigned to the CAB can be diffused throughout the software development lifecycle.

      Change management and DevOps can coexist

      Shift the responsibility and rigor to earlier in the process.

      • If you are implementing change management in a DevOps environment, ensure you have a strong DevOps lifecycle. You may wish to refer to Info-Tech’s research Implementing DevOps Practices That Work.
      • Consider starting in this blueprint by visiting Appendix II to frame your approach to change management. Follow the blueprint while paying attention to the DevOps Callouts.

      DEVOPS CALLOUTS

      Look for these DevOps callouts throughout this storyboard to guide you along the implementation.

      The image is a horizontal figure eight, with 7 arrows, each pointing into the next. They are labelled are follows: Plan; Create; Verify; Package; Release; Configure; Monitor. At the centre of the circles are the words Dev and Ops.

      Successful change management will provide benefits to both the business and IT

      Respond to business requests faster while reducing the number of change-related disruptions.

      IT Benefits

      • Fewer change-related incidents and outages
      • Faster change turnaround time
      • Higher rate of change success
      • Less change rework
      • Fewer service desk calls related to poorly communicated changes

      Business Benefits

      • Fewer service disruptions
      • Faster response to requests for new and enhanced functionalities
      • Higher rate of benefits realization when changes are implemented
      • Lower cost per change
      • Fewer “surprise” changes disrupting productivity

      IT satisfaction with change management will drive business satisfaction with IT. Once the process is working efficiently, staff will be more motivated to adhere to the process, reducing the number of unauthorized changes. As fewer changes bypass proper evaluation and testing, service disruptions will decrease and business satisfaction will increase.

      Change management improves core benefits to the business: the four Cs

      Most organizations have at least some form of change control in place, but formalizing change management leads to the four Cs of business benefits:

      Control

      Change management brings daily control over the IT environment, allowing you to review every relatively new change, eliminate changes that would have likely failed, and review all changes to improve the IT environment.

      Collaboration

      Change management planning brings increased communication and collaboration across groups by coordinating changes with business activities. The CAB brings a more formalized and centralized communication method for IT.

      Consistency

      Request for change templates and a structured process result in implementation, test, and backout plans being more consistent. Implementing processes for pre-approved changes also ensures these frequent changes are executed consistently and efficiently.

      Confidence

      Change management processes will give your organization more confidence through more accurate planning, improved execution of changes, less failure, and more control over the IT environment. This also leads to greater protection against audits.

      You likely need to improve change management more than any other infrastructure & operations process

      The image shows a vertical bar graph. Each segment of the graph is labelled for an infrastructure/operations process. Each segment has two bars one for effectiveness, and another for importance. The first segment, Change Management, is highlighted, with its Effectiveness at a 6.2 and Importance at 8.6

      Source: Info-Tech 2020; n=5,108 IT Professionals from 620 organizations

      Of the eight infrastructure and operations processes measured in Info-Tech’s IT Management and Governance Diagnostic (MGD) program, change management consistently has the second largest gap between importance and effectiveness of these processes.

      Executives and directors recognize the importance of change management but feel theirs is currently ineffective

      Info-Tech’s IT Management and Governance Diagnostic (MGD) program assesses the importance and effectiveness of core IT processes. Since its inception, the MGD has consistently identified change management as an area for immediate improvement.

      The image is a vertical bar graph, with four segments, each having 2 bars, one for Effectiveness and the other for Importance. The four segments are (with Effectiveness and Importance ratings in brackets, respectively): Frontline (6.5/8.6); Manager (6.6/8.9); Director (6.4/8.8); and Executive (6.1/8.8)

      Source: Info-Tech 2020; n=5,108 IT Professionals from 620 organizations

      Importance Scores

      No importance: 1.0-6.9

      Limited importance: 7.0-7.9

      Significant importance: 8.0-8.9

      Critical importance: 9.0-10.0

      Effectiveness Scores

      Not in place: n/a

      Not effective: 0.0-4.9

      Somewhat Ineffective: 5.0-5.9

      Somewhat effective: 6.0-6.9

      Very effective: 7.0-10.0

      There are several common misconceptions about change management

      Which of these have you heard in your organization?

       Reality
      “It’s just a small change; this will only take five minutes to do.” Even a small change can cause a business outage. That small fix could impact a large system connected to the one being fixed.
      “Ad hoc is faster; too many processes slow things down.” Ad hoc might be faster in some cases, but it carries far greater risk. Following defined processes keeps systems stable and risk-averse.
      “Change management is all about speed.” Change management is about managing risk. It gives the illusion of speed by reducing downtime and unplanned work.
      “Change management will limit our capacity to change.” Change management allows for a better alignment of process (release management) with governance (change management).

      Overcome perceived challenges to implementing change management to reap measurable reward

      Before: Informal Change Management

      Change Approval:

      • Changes do not pass through a formal review process before implementation.
      • 10% of released changes are approved.
      • Implementation challenge: Staff will resist having to submit formal change requests and assessments, frustrated at the prospect of having to wait longer to have changes approved.

      Change Prioritization

      • Changes are not prioritized according to urgency, risk, and impact.
      • 60% of changes are urgent.
      • Implementation challenge: Influential stakeholders accustomed to having changes approved and deployed might resist having to submit changes to a standard cost-benefit analysis.

      Change Deployment

      • Changes often negatively impact user productivity.
      • 25% of changes are realized as planned.
      • Implementation challenge: Engaging the business so that formal change freeze periods and regular maintenance windows can be established.

      After: Right-Sized Change Management

      Change Approval

      • All changes pass through a formal review process. Once a change is repeatable and well-tested, it can be pre-approved to save time. Almost no unauthorized changes are deployed.
      • 95% of changes are approved.
      • KPI: Decrease in change-related incidents

      Change Prioritization

      • The CAB prioritizes changes so that the business is satisfied with the speed of change deployment.
      • 35% of changes are urgent.
      • KPI: Decrease in change turnaround time.

      Change deployment

      • Users are always aware of impending changes and changes don’t interrupt critical business activities.
      • Over 80% of changes are realized as planned
      • KPI: Decrease in the number of failed deployments.

      Info-Tech’s methodology for change management optimization focuses on building standardized processes

       1. Define Change Management2. Establish Roles and Workflows3. Define the RFC and Post-Implementation Activities4. Measure, Manage, and Maintain
      Phase Steps

      1.1 Assess Maturity

      1.2 Categorize Changes and Build Your Risk Assessment

      2.1 Determine Roles and Responsibilities

      2.2 Build Core Workflows

      3.1 Design the RFC

      3.2 Establish Post-Implementation Activities

      4.1 Identify Metrics and Build the Change Calendar

      4.2 Implement the Project

        Change Management Standard Operating Procedure (SOP) Change Management Project Summary Template
      Phase Deliverables
      • Change Management Maturity Assessment Tool
      • Change Management Risk Assessment Tool
      • Change Manager Job Description
      • Change Management Process Library
      • Request for Change (RFC) Form Template
      • Change Management Pre-Implementation Checklist
      • Change Management Post-Implementation Checklist
      • Change Management Metrics Tool
      • Change Management
      • Communications Plan
      • Change Management Roadmap Tool

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

      Change Management Process Library

      Document your normal, pre-approved, and emergency change lifecycles with the core process workflows .

      Change Management Risk Assessment Tool

      Test Drive your impact and likelihood assessment questionnaires with the Change Management Risk Assessment Tool.

      Project Summary Template

      Summarize your efforts in the Optimize IT Change Management Improvement Initiative: Project Summary Template.

      Change Management Roadmap Tool

      Record your action items and roadmap your steps to a mature change management process.

      Key Deliverable:

      Change Management SOP

      Document and formalize your process starting with the change management standard operating procedure (SOP).

      These case studies illustrate the value of various phases of this project

      Define Change Management

      Establish Roles and Workflows

      Define RFC and Post-Implementation Activities

      Measure, Manage, and Maintain

      A major technology company implemented change management to improve productivity by 40%. This case study illustrates the full scope of the project.

      A large technology firm experienced a critical outage due to poor change management practices. This case study illustrates the scope of change management definition and strategy.

      Ignorance of change management process led to a technology giant experiencing a critical cloud outage. This case study illustrates the scope of the process phase.

      A manufacturing company created a makeshift CMDB in the absence of a CMDB to implement change management. This case study illustrates the scope of change intake.

      A financial institution tracked and recorded metrics to aid in the success of their change management program. This case study illustrates the scope of the implementation phase.

      Working through this project with Info-Tech can save you time and money

      Engaging in a Guided Implementation doesn’t just offer valuable project advice, it also results in significant cost savings.

      Guided ImplementationMeasured Vale
      Phase 1: Define Change Management
      • We estimate Phase 1 activities will take 2 FTEs 10 days to complete on their own, but the time saved by using Info-Tech’s methodology will cut that time in half, thereby saving $3,100 (2 FTEs * 5 days * $80,000/year).

      Phase 2: Establish Roles and Workflows

      • We estimate Phase 2 will take 2 FTEs 10 days to complete on their own, but the time saved by using Info-Tech’s methodology will cut that time in half, thereby saving $3,100 (2 FTEs * 5 days * $80,000/year).
      Phase 3: Define the RFC and Post-Implementation Activities
      • We estimate Phase 3 will take 2 FTEs 10 days to complete on their own, but the time saved by using Info-Tech’s methodology will cut that time in half, thereby saving $3,100 (2 FTEs * 5 days * $80,000/year).

      Phase 4: Measure, Manage, and Maintain

      • We estimate Phase 4 will take 2 FTEs 5 days to complete on their own, but the time saved by using Info-Tech’s methodology will cut that time in half, thereby saving $1,500 (2 FTEs * 2.5 days * $80,000/year).
      Total Savings $10,800

      Case Study

      Industry: Technology

      Source: Daniel Grove, Intel

      Intel implemented a robust change management program and experienced a 40% improvement in change efficiency.

      Founded in 1968, the world’s largest microchip and semiconductor company employs over 100,000 people. Intel manufactures processors for major players in the PC market including Apple, Lenovo, HP, and Dell.

      ITIL Change Management Implementation

      With close to 4,000 changes occurring each week, managing Intel’s environment is a formidable task. Before implementing change management within the organization, over 35% of all unscheduled downtime was due to errors resulting from change and release management. Processes were ad hoc or scattered across the organization and no standards were in place.

      Results

      After a robust implementation of change management, Intel experienced a number of improvements including automated approvals, the implementation of a formal change calendar, and an automated RFC form. As a result, Intel improved change productivity by 40% within the first year of the program’s implementation.

      Define Change Management

      Establish Roles and Workflows

      Define RFC and Post-Implementation Activities

      Measure, Manage, and Maintain

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful."

      Guided Implementation

      "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track."

      Workshop

      "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place."

      Consulting

      "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks are used throughout all four options.

      Guided Implementation

      What does a typical GI on this topic look like?

      A Guided Implementation (GI) is series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is between 8 to 12 calls over the course of 4 to 6 months.

      Define Change Management

      • Call #1: Introduce change concepts.
      • Call #2: Assess current maturity.
      • Call #3: Identify target-state capabilities.

      Establish Roles and Workflows

      • Call #4: Review roles and responsibilities.
      • Call #5: Review core change processes.

      Define RFC and Post- Implementation Activities

      • Call #6: Define change intake process.
      • Call #7: Create pre-implementation and post-implementation checklists.

      Measure, Manage, and Maintain

      • Call #8: Review metrics.
      • Call #9: Create roadmap.

      Workshop Overview

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889

       Day 1Day 2Day 3Day 4Day 5
      Activities

      Define Change Management

      1.1 Outline Strengths and Challenges

      1.2 Conduct a Maturity Assessment

      1.3 Build a Change Categorization Scheme

      1.4 Build Your Risk Assessment

      Establish Roles and Workflows

      2.1 Define the Change Manager Role

      2.2 Outline CAB Protocol and membership

      2.3 Build Normal Change Process

      2.4 Build Emergency Change Process

      2.5 Build Pre-Approved Change Process

      Define the RFC and Post-Implementation Activities

      3.1 Create an RFC Template

      3.2 Determine Post-Implementation Activities

      3.3 Build a Change Calendar Protocol

      Measure, Manage, and Maintain

      4.1 Identify Metrics and Reports

      4.2 Create Communications Plan

      4.3 Build an Implementation Roadmap

      Next Steps and Wrap-Up (offsite)

      5.1 Complete in-progress deliverables from previous four days

      5.2 Set up review time for workshop deliverables and to discuss next steps

      Deliverables
      1. Maturity Assessment
      2. Risk Assessment
      1. Change Manager Job Description
      2. Change Management Process Library
      1. Request for Change (RFC) Form Template
      2. Pre-Implementation Checklist
      3. Post-Implementation Checklist
      1. Metrics Tool
      2. Communications Plan
      3. Project Roadmap
      1. Change Management Standard Operating Procedure (SOP)
      2. Workshop Summary Deck

      Phase 1

      Define Change Management

      Define Change Management

      1.1 Assess Maturity

      1.2 Categorize Changes and Build Your Risk Assessment

      Establish Roles and Workflows

      2.1 Determine Roles and Responsibilities

      2.2 Build Core Workflows

      Define the RFC and Post-Implementation Activities

      3.1 Design the RFC

      3.2 Establish Post-Implementation Activities

      Measure, Manage, and Maintain

      4.1 Identify Metrics and Build the Change Calendar

      4.2 Implement the Project

      This phase will guide you through the following steps:

      • Assess Maturity
      • Categorize Changes and Build Your Risk Assessment

      This phase involves the following participants:

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board

      Step 1.1

      Assess Maturity

      Activities

      1.1.1 Outline the Organization’s Strengths and Challenges

      1.1.2 Complete a Maturity Assessment

      This step involves the following participants:

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board

      Outcomes of this step

      • An understanding of maturity change management processes and frameworks
      • Identification of existing change management challenges and potential causes
      • A framework for assessing change management maturity and an assessment of your existing change management processes

      Define Change Management

      Step 1.1: Assess Maturity → Step 1.2: Categorize Changes and Build Your Risk Assessment

      Change management is often confused with release management, but they are distinct processes

      Change

      • Change management looks at software changes as well as hardware, database, integration, and network changes, with the focus on stability of the entire IT ecosystem for business continuity.
      • Change management provides a holistic view of the IT environment, including dependencies, to ensure nothing is negatively affected by changes.
      • Change documentation is more focused on process, ensuring dependencies are mapped, rollout plans exist, and the business is not at risk.

      Release

      • Release and deployment are the detailed plans that bundle patches, upgrades, and new features into deployment packages, with the intent to change them flawlessly into a production environment.
      • Release management is one of many actions performed under change management’s governance.
      • Release documentation includes technical specifications such as change schedule, package details, change checklist, configuration details, test plan, and rollout and rollback plans.

      Info-Tech Insight

      Ensure the Release Manager is present as part of your CAB. They can explain any change content or dependencies, communicate business approval, and advise the service desk of any defects.

      Integrate change management with other IT processes

      As seen in the context diagram, change management interacts closely with many other IT processes including release management and configuration management (seen below). Ensure you delineate when these interactions occur (e.g. RFC updates and CMDB queries) and which process owns each task.

      The image is a chart mapping the interactions between Change Management and Configuration Management (CMDB).

      Avoid the challenges of poor change management

      1. Deployments
        • Too frequent: The need for frequent deployments results in reduced availability of critical business applications.
        • Failed deployments or rework is required: Deployments are not successful and have to be backed out of and then reworked to resolve issues with the installation.
        • High manual effort: A lack of automation results in high resource costs for deployments. Human error is likely, which adds to the risk of a failed deployment.
      2. Incidents
        • Too many unauthorized changes: If the process is perceived as cumbersome and ineffective, people will bypass it or abuse the emergency designation to get their changes deployed faster.
        • Changes cause incidents: When new releases are deployed, they create problems with related systems or applications.
      3. End Users
        • Low user satisfaction: Poor communication and training result in surprised and unhappy users and support staff.

      “With no controls in place, IT gets the blame for embarrassing outages. Too much control, and IT is seen as a roadblock to innovation.” – Anonymous, VP IT of a federal credit union

      1.1.1 Outline the Organization’s Strengths and Challenges

      Input

      • Current change documentation (workflows, SOP, change policy, etc.)
      • Organizational chart(s)

      Output

      • List of strengths and challenges for change management

      Materials

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board
      1. As group, discuss and outline the change management challenges facing the organization. These may be challenges caused by poor change management processes or by a lack of process.
      2. Use the pain points found on the previous slide to help guide the discussion.
      3. As a group, also outline the strengths of change management and the strengths of the current organization. Use these strengths as a guide to know what practices to continue and what strengths you can leverage to improve the change management process.
      4. Record the activity results in the Project Summary Template.

      Download the Optimize IT Change Management Improvement Initiative: Project Summary Template

      Assess current change management maturity to create a plan for improvement

       ChaosReactiveControlled

      Proactive

      Optimized
      Change Requests No defined processes for submitting changes Low process adherence and no RFC form RFC form is centralized and a point of contact for changes exists RFCs are reviewed for scope and completion RFCs trend analysis and proactive change exists
      Change Review Little to no change risk assessment Risk assessment exists for each RFC RFC form is centralized and a point of contact for changes exists Change calendar exists and is maintained System and component dependencies exist (CMDB)
      Change Approval No formal approval process exists Approval process exists but is not widely followed Unauthorized changes are minimal or nonexistent Change advisory board (CAB) is established and formalized Trend analysis exists increasing pre-approved changes
      Post-Deployment No post-deployment change review exists Process exists but is not widely followed Reduction of change-related incidents Stakeholder satisfaction is gathered and reviewed Lessons learned are propagated and actioned
      Process Governance Roles & responsibilities are ad hoc Roles, policies & procedures are defined & documented Roles, policies & procedures are defined & documented KPIs are tracked, reported on, and reviewed KPIs are proactively managed for improvement

      Info-Tech Insight

      Reaching an optimized level is not feasible for every organization. You may be able to run a very good change management process at the Proactive or even Controlled stage. Pay special attention to keeping your goals attainable.

      1.1.2 Complete a Maturity Assessment

      Input

      • Current change documentation (workflows, SOP, change policy, etc.)

      Output

      • Assessment of current maturity level and goals to improve change management

      Materials

      Participants

      • Change Manager
      • Service Desk Manager
      • Operations (optional)
      1. Use Info-Tech’s Change Management Maturity Assessment Tool to assess the maturity and completeness of your change process.
      2. Significant gaps revealed in this assessment should be the focal points of your discussion when investigating root causes and brainstorming remediation activities:
        1. For each activity of each process area of change management, determine the degree of completeness of your current process.
        2. Review your maturity assessment results and discuss as a group potential reasons why you arrived at your maturity level. Identify areas where you should focus your initial attention for improvement.
        3. Regularly review the maturity of your change management practices by completing this maturity assessment tool periodically to identify other areas to optimize.

      Download the Change Management Maturity Assessment Tool

      Case Study

      Even Google isn’t immune to change-related outages. Plan ahead and communicate to help avoid change-related incidents

      Industry: Technology

      Source: The Register

      As part of a routine maintenance procedure, Google engineers moved App Engine applications between data centers in the Central US to balance out traffic.

      Unfortunately, at the same time that applications were being rerouted, a software update was in progress on the traffic routers, which triggered a restart. This temporarily diminished router capacity, knocking out a sizeable portion of Google Cloud.

      The server drain resulted in a huge spike in startup requests, and the routers simply couldn’t handle the traffic.

      As a result, 21% of Google App Engine applications hosted in the Central US experienced error rates in excess of 10%, while an additional 16% of applications experienced latency, albeit at a lower rate.

      Solution

      Thankfully, engineers were actively monitoring the implementation of the change and were able to spring into action to halt the problem.

      The change was rolled back after 11 minutes, but the configuration error still needed to be fixed. After about two hours, the change failure was resolved and the Google Cloud was fully functional.

      One takeaway for the engineering team was to closely monitor how changes are scheduled. Ultimately, this was the result of miscommunication and a lack of transparency between change teams.

      Step 1.2

      Categorize Changes and Build Your Risk Assessment

      Activities

      1.2.1 Define What Constitutes a Change

      1.2.2 Build a Change Categorization Scheme

      1.2.3 Build a Classification Scheme to Assess Impact

      1.2.4 Build a Classification Scheme to Define Likelihood

      1.2.5 Evaluate and Adjust Your Risk Assessment Scheme

      Define Change Management

      Step 1.1: Assess Maturity → Step 1.2: Categorize Changes and Build Your Risk Assessment

      This step involves the following participants:

      • Infrastructure/Applications Manager
      • Change Manager
      • Members of the Change Advisory Board

      Outcomes of this step

      • A clear definition of what constitutes a change in your organization
      • A defined categorization scheme to classify types of changes
      • A risk assessment matrix and tool for evaluating and prioritizing change requests according to impact and likelihood of risk

      Change must be managed to mitigate risk to the infrastructure

      Change management is the gatekeeper protecting your live environment.

      Successfully managed changes will optimize risk exposure, severity of impact, and disruption. This will result in the bottom-line business benefits of removal of risk, early realization of benefits, and savings of money and time.

      • IT change is constant; change requests will be made both proactively and reactively to upgrade systems, acquire new functionality, and to prevent or resolve incidents.
      • Every change to the infrastructure must pass through the change management process before being deployed to ensure that it has been properly assessed and tested, and to check that a backout /rollback plan is in place.
      • It will be less expensive to invest in a rigorous change management process than to resolve incidents, service disruptions, and outages caused by the deployment of a bad change.
      • Change management is what gives you control and visibility regarding what is introduced to the live environment, preventing incidents that threaten business continuity.

      80%

      In organizations without formal change management processes, about 80% (The Visible Ops Handbook) of IT service outage problems are caused by updates and changes to systems, applications, and infrastructure. It’s crucial to track and systematically manage change to fully understand and predict the risks and potential impact of the change.

      Attributes of a change

      Differentiate changes from other IT requests

      Is this in the production environment of a business process?

      The core business of the enterprise or supporting functions may be affected.

      Does the task affect an enterprise managed system?

      If it’s for a local application, it’s a service request

      How many users are impacted?

      It should usually impact more than a single user (in most cases).

      Is there a configuration, or code, or workflow, or UI/UX change?

      Any impact on a business process is a change; adding a user or a recipient to a report or mailing list is not a change.

      Does the underlying service currently exist?

      If it’s a new service, then it’s better described as a project.

      Is this done/requested by IT?

      It needs to be within the scope of IT for the change management process to apply.

      Will this take longer than one week?

      As a general rule, if it takes longer than 40 hours of work to complete, it’s likely a project.

      Defining what constitutes a change

      Every change request will initiate the change management process; don’t waste time reviewing requests that are out of scope.

      ChangeService Request (User)Operational Task (Backend)
      • Fixing defects in code
      • Changing configuration of an enterprise system
      • Adding new software or hardware components
      • Switching an application to another VM
      • Standardized request
      • New PC
      • Permissions request
      • Change password
      • Add user
      • Purchases
      • Change the backup tape
      • Delete temporary files
      • Maintain database (one that is well defined, repeatable, and predictable)
      • Run utilities to repair a database

      Do not treat every IT request as a change!

      • Many organizations make the mistake of calling a standard service request or operational task a “change.”
      • Every change request will initiate the change management process; don’t waste time reviewing requests that are out of scope.
      • While the overuse of RFCs for out-of-scope requests is better than a lack of process, this will slow the process and delay the approval of more critical changes.
      • Requiring an RFC for something that should be considered day-to-day work will also discourage people from adhering to the process, because the RFC will be seen as meaningless paperwork.

       

      1.2.1 Define What Constitutes a Change

      Input

      • List of examples of each category of the chart

      Output

      • Definitions for each category to be used at change intake

      Materials

      • Whiteboard/flip charts (or shared screen if working remotely)
      • Service catalog (if applicable)
      • Sticky notes
      • Markers/pens
      • Change Management SOP

      Participants

      • Infrastructure Manager
      • Change Manager
      • Members of the Change Advisory Board
      1. As a group, brainstorm examples of changes, projects, service requests (user), operational tasks (backend), and releases. You may add additional categories as needed (e.g. incidents).
      2. Have each participant write the examples on sticky notes and populate the following chart on the whiteboard/flip chart.
      3. Use the examples to draw lines and define what defines each category.
        • What makes a change distinct from a project?
        • What makes a change distinct from a service request?
        • What makes a change distinct from an operational task?
        • When do the category workflows cross over with other categories? (For example, when does a project interact with change management?)
      4. Record the definitions of requests and results in section 2.3 of the Change Management Standard Operating Procedure (SOP).
      ChangeProjectService Request (User)Operational Task (Backend)Release
      Changing Configuration ERP upgrade Add new user Delete temp files Software release

      Download the Change Management Standard Operating Procedure (SOP).

      Each RFC should define resources needed to effect the change

      In addition to assigning a category to each RFC based on risk assessment, each RFC should also be assigned a priority based on the impact of the change on the IT organization, in terms of the resources needed to effect the change.

      Categories include

      Normal

      Emergency

      Pre-Approved

      The majority of changes will be pre-approved or normal changes. Definitions of each category are provided on the next slide.

      Info-Tech uses the term pre-approved rather than the ITIL terminology of standard to more accurately define the type of change represented by this category.

      A potential fourth change category of expedited may be employed if you are having issues with process adherence or if you experience changes driven from outside change management’s control (e.g. from the CIO, director, judiciary, etc.) See Appendix I for more details.

      Info-Tech Best Practice

      Do not rush to designate changes as pre-approved. You may have a good idea of which changes may be considered pre-approved, but make sure they are in fact low-risk and well-documented before moving them over from the normal category.

      The category of the change determines the process it follows

       Pre-ApprovedNormalEmergency
      Definition
      • Tasks are well-known, documented, and proven
      • Budgetary approval is preordained or within control of change requester
      • Risk is low and understood
      • There’s a low probability of failure
      • All changes that are not pre-approved or emergency will be classified as normal
      • Further categorized by priority/risk
      • The change is being requested to resolve a current or imminent critical/severity-1 incident that threatens business continuity
      • Associated with a critical incident or problem ticket
      Trigger
      • The same change is built and changed repeatedly using the same install procedures and resulting in the same low-risk outcome
      • Upgrade or new functionality that will capture a business benefit
      • A fix to a current problem
      • A current or imminent critical incident that will impact business continuity
      • Urgency to implement the change must be established, as well as lack of any alternative or workaround
      Workflow
      • Pre-established
      • Repeatable with same sequence of actions, with minimal judgment or decision points
      • Dependent on the change
      • Different workflows depending on prioritization
      • Dependent on the change
      Approval
      • Change Manager (does not need to be reviewed by CAB)
      • CAB
      • Approval from the Emergency Change Advisory Board (E-CAB) is sufficient to proceed with the change
      • A retroactive RFC must be created and approved by the CAB

      Pay close attention to defining your pre-approved changes. They are going to be critical for running a smooth change management practice in a DevOps Environment

      1.2.2 Build a Change Categorization Scheme

      Input

      • List of examples of each change category

      Output

      • Definitions for each change category

      Materials

      • Whiteboard/flip charts (or shared screen if working remotely)
      • Service catalog (if applicable)
      • Sticky notes
      • Markers
      • Change Management SOP

      Participants

      • Infrastructure Manager
      • Change Manager
      • Members of the Change Advisory Board
      1. Discuss the change categories on the previous slide and modify the types of descriptions to suit your organization.
      2. Once the change categories or types are defined, identify several examples of change requests that would fall under each category.
      3. Types of normal changes will be further defined in the next activity and can be left blank for now.
      4. Examples are provided below. Capture your definitions in section 4 of your Change Management SOP.
      Pre-Approved (AKA Standard)NormalEmergency
      • Microsoft patch management/deployment
      • Windows update
      • Minor form changes
      • Service pack updates on non-critical systems
      • Advance label status on orders
      • Change log retention period/storage
      • Change backup frequency

      Major

      • Active directory server upgrade
      • New ERP

      Medium

      • Network upgrade
      • High availability implementation

      Minor

      • Ticket system go-live
      • UPS replacement
      • Cognos update
      • Any change other than a pre-approved change
      • Needed to resolve a major outage in a Tier 1 system

      Assess the risk for each normal change based on impact (severity) and likelihood (probability)

      Create a change assessment risk matrix to standardize risk assessment for new changes. Formalizing this assessment should be one of the first priorities of change management.

      The following slides guide you through the steps of formalizing a risk assessment according to impact and likelihood:

      1. Define a risk matrix: Risk matrices can either be a 3x3 matrix (Minor, Medium, or High Risk as shown on the next slide) or a 4x4 matrix (Minor, Medium, High, or Critical Risk).
      2. Build an impact assessment: Enable consistent measurement of impact for each change by incorporating a standardized questionnaire for each RFC.
      3. Build a likelihood assessment: Enable the consistent measurement of impact for each change by incorporating a standardized questionnaire for each RFC.
      4. Test drive your risk assessment and make necessary adjustments: Measure your newly formed risk assessment questionnaires against historical changes to test its accuracy.

      Consider risk

      1. Risk should be the primary consideration in classifying a normal change as Low, Medium, High. The extent of governance required, as well as minimum timeline to implement the change, will follow from the risk assessment.
      2. The business benefit often matches the impact level of the risk – a change that will provide a significant benefit to a large number of users may likely carry an equally major downside if deviations occur.

      Info-Tech Insight

      All changes entail an additional level of risk. Risk is a function of impact and likelihood. Risk may be reduced, accepted, or neutralized through following best practices around training, testing, backout planning, redundancy, timing and sequencing of changes, etc.

      Create a risk matrix to assign a risk rating to each RFC

      Every normal RFC should be assigned a risk rating.

      How is risk rating determined?

      • Priority should be based on the business consequences of implementing or denying the change.
      • Risk rating is assigned using the impact of the risk and likelihood/probability that the event may occur.

      Who determines priority?

      • Priority should be decided with the change requester and with the CAB, if necessary.
      • Don’t let the change requester decide priority alone, as they will usually assign it a higher priority than is justified. Use a repeatable, standardized framework to assess each request.

      How is risk rating used?

      • Risk rating is used to determine which changes should be discussed and assessed first.
      • Time frames and escalation processes should be defined for each risk level.

      RFCs need to clearly identify the risk level of the proposed change. This can be done through statement of impact and likelihood (low/medium/high) or through pertinent questions linked with business rules to assess the risk.

      Risk always has a negative impact, but the size of the impact can vary considerably in terms of cost, number of people or sites affected, and severity of the impact. Impact questions tend to be more objective and quantifiable than likelihood questions.

      Risk Matrix

      Risk Matrix. Impact vs. Likelihood. Low impact, Low Likelihood and Medium Impact, Medium Likelihood are minor risks. High Likelihood, Low Impact; Medium Likelihood, Medium Impact; and Low Likelihood, High Impact are Medium Risk. High Impact, High Likelihood; High Impact, Medium Likelihood; and Medium Impact, High Likelihood are Major risk.

      1.2.3 Build a Classification Scheme to Assess Impact

      Input

      • Current risk assessment (if available)

      Output

      • Tailored impact assessment

      Materials

      Participants

      • CIO
      • Infrastructure Manager
      • Change Manager
      • Members of the Change Advisory Board
      1. Define a set of questions to measure risk impact.
      2. For each question, assign a weight that should be placed on that factor.
      3. Define criteria for each question that would categorize the risk as high, medium, or low.
      4. Capture your results in section 4.3.1 of your Change Management SOP.
      Impact
      Weight Question High Medium Low
      15% # of people affected 36+ 11-35 <10
      20% # of sites affected 4+ 2-3 1
      15% Duration of recovery (minutes of business time) 180+ 30-18 <3
      20% Systems affected Mission critical Important Informational
      30% External customer impact Loss of customer Service interruption None

      1.2.4 Build a Classification Scheme to Define Likelihood

      Input

      • Current risk assessment (if available)

      Output

      • Tailored likelihood assessment

      Materials

      Participants

      • CIO
      • Infrastructure Manager
      • Change Manager
      • Members of the Change Advisory Board
      1. Define a set of questions to measure risk likelihood.
      2. For each question, assign a weight that should be placed on that factor.
      3. Define criteria for each question that would categorize the risk as high, medium, or low.
      4. Capture your results in section 4.3.2 of your Change Management SOP.
      LIKELIHOOD
      Weight Question High Medium Low
      25% Has this change been tested? No   Yes
      10% Have all the relevant groups (companies, departments, executives) vetted the change? No Partial Yes
      5% Has this change been documented? No   Yes
      15% How long is the change window? When can we implement? Specified day/time Partial Per IT choice
      20% Do we have trained and experienced staff available to implement this change? If only external consultants are available, the rating will be “medium” at best. No   Yes
      25% Has an implementation plan been developed? No   Yes

      1.2.5 Evaluate and Adjust Your Risk Assessment Scheme

      Input

      • Impact and likelihood assessments from previous two activities

      Output

      • Vetted risk assessment

      Materials

      Participants

      • CIO
      • Infrastructure Manager
      • Change Manager
      • Members of the Change Advisory Board
      1. Draw your risk matrix on a whiteboard or flip chart.
      2. As a group, identify up to 10 examples of requests for changes that would apply within your organization. Depending on the number of people participating, each person could identify one or two changes and write them on sticky notes.
      3. Take turns bringing your sticky notes up to the risk matrix and placing each where it belongs, according to the assessment criteria you defined.
      4. After each participant has taken a turn, discuss each change as a group and adjust the placement of any changes, if needed. Update the risk assessment weightings or questions, if needed.

      Download the Change Management Rick Assessment Tool.

      #

      Change Example

      Impact

      Likelihood

      Risk

      1

      ERP change

      High

      Medium

      Major

      2

      Ticket system go-live

      Medium

      Low

      Minor

      3

      UPS replacement

      Medium

      Low

      Minor

      4

      Network upgrade

      Medium

      Medium

      Medium

      5

      AD upgrade

      Medium

      Low

      Minor

      6

      High availability implementation

      Low

      Medium

      Minor

      7

      Key-card implementation

      Low

      High

      Medium

      8

      Anti-virus update

      Low

      Low

      Minor

      9

      Website

      Low

      Medium

      Minor

       

      Case Study

      A CMDB is not a prerequisite of change management. Don’t let the absence of a configuration management database (CMDB) prevent you from implementing change management.

      Industry: Manufacturing

      Source: Anonymous Info-Tech member

      Challenge

      The company was planning to implement a CMDB; however, full implementation was still one year away and subject to budget constraints.

      Without a CMDB, it would be difficult to understand the interdependencies between systems and therefore be able to provide notifications to potentially affected user groups prior to implementing technical changes.

      This could have derailed the change management project.

      Solution

      An Excel template was set up as a stopgap measure until the full implementation of the CMDB. The template included all identified dependencies between systems, along with a “dependency tier” for each IT service.

      Tier 1: The dependent system would not operate if the upstream system change resulted in an outage.

      Tier 2: The dependent system would suffer severe degradation of performance and/or features.

      Tier 3: The dependent system would see minor performance degradation or minor feature unavailability.

      Results

      As a stopgap measure, the solution worked well. When changes ran the risk of degrading downstream dependent systems, the impacted business system owner’s authorization was sought and end users were informed in advance.

      The primary takeaway was that a system to manage configuration linkages and system dependencies was key.

      While a CMDB is ideal for this use case, IT organizations shouldn’t let the lack of such a system stop progress on change management.

      Case Study (part 1 of 4)

      Intel used a maturity assessment to kick-start its new change management program.

      Industry: Technology

      Source: Daniel Grove, Intel

      Challenge

      Founded in 1968, the world’s largest microchip and semiconductor company employs over 100,000 people. Intel manufactures processors for major players in the PC market including Apple, Lenovo, HP, and Dell.

      Intel IT supports over 65,000 servers, 3.2 petabytes of data, over 70,000 PCs, and 2.6 million emails per day.

      Intel’s change management program is responsible for over 4,000 changes each week.

      Solution

      Due to the sheer volume of change management activities present at Intel, over 35% of unscheduled outages were the result of changes.

      Ineffective change management was identified as the top contributor of incidents with unscheduled downtime.

      One of the major issues highlighted was a lack of process ownership. The change management process at Intel was very fragmented, and that needed to change.

      Results

      Daniel Grove, Senior Release & Change Manager at Intel, identified that clarifying tasks for the Change Manager and the CAB would improve process efficiency by reducing decision lag time. Roles and responsibilities were reworked and clarified.

      Intel conducted a maturity assessment of the overall change management process to identify key areas for improvement.

      Phase 2

      Establish Roles and Workflows

      For running change management in DevOps environment, see Appendix II.

      Define Change Management

      1.1 Assess Maturity

      1.2 Categorize Changes and Build Your Risk Assessment

      Establish Roles and Workflows

      2.1 Determine Roles and Responsibilities

      2.2 Build Core Workflows

      Define RFC and Post-Implementation Activities

      3.1 Design the RFC

      3.2 Establish Post-Implementation Activities

      Measure, Manage, and Maintain

      4.1 Identify Metrics and Build the Change Calendar

      4.2 Implement the Project

      This phase will guide you through the following steps:

      • Determine Roles and Responsibilities
      • Build Core Workflows

      This phase involves the following participants:

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board

      Step 2.1

      Determine Roles and Responsibilities

      Activities

      2.1.1 Capture Roles and Responsibilities Using a RACI Chart

      2.1.2 Determine Your Change Manager’s Responsibilities

      2.1.3 Define the Authority and Responsibilities of Your CAB

      2.1.4 Determine an E-CAB Protocol for Your Organization

      Establish Roles and Workflows

      Step 2.1: Determine Roles and Responsibilities → Step 2.2: Build Core Workflows

      This step involves the following participants:

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board

      Outcomes of this step

      • Clearly defined responsibilities to form the job description for a Change Manager
      • Clearly defined roles and responsibilities for the change management team, including the business system owner, technical SME, and CAB members
      • Defined responsibilities and authority of the CAB
      • Protocol for an emergency CAB (E-CAB) meeting

      Identify roles and responsibilities for your change management team

      Business System Owner

      • Provides downtime window(s)
      • Advises on need for change (prior to creation of RFC)
      • Validates change (through UAT or other validation as necessary)
      • Provides approval for expedited changes (needs to be at executive level)

      Technical Subject Matter Expert (SME)

      • Advises on proposed changes prior to RFC submission
      • Reviews draft RFC for technical soundness
      • Assesses backout/rollback plan
      • Checks if knowledgebase has been consulted for prior lessons learned
      • Participates in the PIR, if necessary
      • Ensures that the service desk is trained on the change

      CAB

      • Approves/rejects RFCs for normal changes
      • Reviews lessons learned from PIRs
      • Decides on the scope of change management
      • Reviews metrics and decides on remedial actions
      • Considers changes to be added to list of pre-approved changes
      • Communicates to organization about upcoming changes

      Change Manager

      • Reviews RFCs for completeness
      • Ensures RFCs brought to the CAB have a high chance of approval
      • Chairs CAB meetings, including scheduling, agenda preparation, reporting, and follow-ups
      • Manages post-implementation reviews and reporting
      • Organizes internal communications (within IT)

      2.1.1 Capture Roles and Responsibilities Using a RACI Chart

      Input

      • Current SOP

      Output

      • Documented roles and responsibilities in change management in a RACI chart

      Materials

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board
      1. As a group, work through developing a RACI chart to determine the roles and responsibilities of individuals involved in the change management practice based on the following criteria:
        • Responsible (performs the work)
        • Accountable (ensures the work is done)
        • Consulted (two-way communication)
        • Informed (one-way communication)
      2. Record your results in slide 14 of the Project Summary Template and section 3.1 of your Change Management SOP.
      Change Management TasksOriginatorSystem OwnerChange ManagerCAB MemberTechnical SMEService DeskCIO/ VP ITE-CAB Member
      Review the RFC C C A C R C R  
      Validate changes C C A C R C R  
      Assess test plan A C R R C   I  
      Approve the RFC I C A R C   I  
      Create communications plan R I A     I I  
      Deploy communications plan I I A I   R    
      Review metrics   C A R   C I  
      Perform a post implementation review   C R A     I  
      Review lessons learned from PIR activities     R A   C    

      Designate a Change Manager to own the process, change templates, and tools

      The Change Manager will be the point of contact for all process questions related to change management.

      • The Change Manager needs the authority to reject change requests, regardless of the seniority of the requester.
      • The Change Manager needs the authority to enforce compliance to a standard process.
      • The Change Manager needs enough cross-functional subject-matter expertise to accurately evaluate the impact of change from both an IT and business perspective.

      Info-Tech Best Practice

      Some organizations will not be able to assign a dedicated Change Manager, but they must still task an individual with change review authority and with ownership of the risk assessment and other key parts of the process.

      Responsibilities

      1. The Change Manager is your first stop for change approval. Both the change management and release and deployment management processes rely on the Change Manager to function.
      2. Every single change that is applied to the live environment, from a single patch to a major change, must originate with a request for change (RFC), which is then approved by the Change Manager to proceed to the CAB for full approval.
      3. Change templates and tools, such as the change calendar, list of preapproved changes, and risk assessment template are controlled by the Change Manager.
      4. The Change Manager also needs to have ownership over gathering metrics and reports surrounding deployed changes. A skilled Change Manager needs to have an aptitude for applying metrics for continual improvement activities.

      2.1.2 Document Your Change Manager’s Responsibilities

      Input

      • Current Change Manager job description (if available)

      Output

      • Change Manager job description and list of responsibilities

      Materials

      • Whiteboard/flip charts (or shared screen if working remotely)
      • Markers/pens
      • Info-Tech’s Change Manager Job Description
      • Change Management SOP

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board

      1.Using the previous slide, Info-Tech’s Change Manager Job Description, and the examples below, brainstorm responsibilities for the Change Manager.

      2.Record the responsibilities in Section 3.2 of your Change Management SOP.

      Example:

      Change Manager: James Corey

      Responsibilities

      1. Own the process, tools, and templates.
      2. Control the Change Management SOP.
      3. Provide standard RFC forms.
      4. Distribute RFCs for CAB review.
      5. Receive all initial RFCs and check them for completion.
      6. Approve initial RFCs.
      7. Approve pre-approved changes.
      8. Approve the conversion of normal changes to pre-approved changes.
      9. Assemble the Emergency CAB (E-CAB) when emergency change requests are received.
      10. Approve submission of RFCs for CAB review.
      11. Chair the CAB:
        • Set the CAB agenda and distribute it at least 24 hours before the meeting.
        • Ensure the agenda is adhered to.
        • Make the final approval/prioritization decision regarding a change if the CAB is deadlocked and cannot come to an agreement.
        • Distribute CAB meeting minutes to all members and relevant stakeholders.

      Download the Change Manager Job Description

      Create a Change Advisory Board (CAB) to provide process governance

      The primary functions of the CAB are to:

      1. Protect the live environment from poorly assessed, tested, and implemented changes.
        • CAB approval is required for all normal and emergency changes.
        • If a change results in an incident or outage, the CAB is effectively responsible; it’s the responsibility of the CAB to assess and accept the potential impact of every change.
      2. Prioritize changes in a way that fairly reflects change impact and urgency.
        • Change requests will originate from multiple stakeholders, some of whom have competing interests.
        • It’s up to the CAB to prioritize these requests effectively so that business need is balanced with any potential risk to the infrastructure.
        • The CAB should seek to reduce the number of emergency/expedited changes.
      3. Schedule deployments in a way that minimizes conflict and disruption.
        • The CAB uses a change calendar populated with project work, upcoming organizational initiatives, and change freeze periods. They will schedule changes around these blocks to avoid disrupting user productivity.
        • The CAB should work closely with the release and deployment management teams to coordinate change/release scheduling.

      See what responsibilities in the CAB’s process are already performed by the DevOps lifecycle (e.g. authorization, deconfliction etc.). Do not duplicate efforts.

      Use diverse representation from the business to form an effective CAB

      The CAB needs insight into all areas of the business to avoid approving a high-risk change.

      Based on the core responsibilities you have defined, the CAB needs to be composed of a diverse set of individuals who provide quality:

      • Change need assessments – identifying the value and purpose of a proposed change.
      • Change risk assessments – confirmation of the technical impact and likelihood assessments that lead to a risk score, based on the inputs in RFC.
      • Change scheduling – offer a variety of perspectives and responsibilities and will be able to identify potential scheduling conflicts.
       CAB RepresentationValue Added
      Business Members
      • CIO
      • Business Relationship Manager
      • Service Level Manager
      • Business Analyst
      • Identify change blackout periods, change impact, and business urgency.
      • Assess impact on fiduciary, legal, and/or audit requirements.
      • Determine acceptable business risk.
      IT Operations Members
      • Managers representing all IT functions
      • IT Directors
      • Subject Matter Experts (SMEs)
      • Identify dependencies and downstream impacts.
      • Identify possible conflicts with pre-existing OLAs and SLAs.
      CAB Attendees
      • Specific SMEs, tech specialists, and business and vendor reps relevant to a particular change
      • Only attend meetings when invited by the Change Manager
      • Provide detailed information and expertise related to their particular subject areas.
      • Speak to requirements, change impact, and cost.

      Info-Tech Best Practice

      Form a core CAB (members attend every week) and an optional CAB (members who attend only when a change impacts them or when they can provide value in discussions about a change). This way, members can have their voice heard without spending every week in a meeting where they do not contribute.

      2.1.3 Define the Authority and Responsibilities of Your CAB

      Input

      • Current SOP or CAB charter (if available)

      Output

      • Documented list of CAB authorities and responsibilities

      Materials

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board

      1.Using the previous slide and the examples below, list the authorities and responsibilities of your CAB.

      2.Record the responsibilities in section 3.3.2 of your Change Management SOP and the Project Summary Template.

      Example:

      CAP AuthorityCAP Responsibilities
      • Final authority over the deployment of all normal and emergency changes.
      • Authority to absorb the risk of a change.
      • Authority to set the change calendar:
        • Maintenance windows.
        • Change freeze periods.
        • Project work.
        • Authority to delay changes.
      • Evaluate all normal and emergency changes.
      • Verify all normal change test, backout, and implementation plans.
      • Verify all normal change test results.
      • Approve all normal and emergency changes.
      • Prioritize all normal changes.
      • Schedule all normal and emergency changes.
      • Review failed change deployments.

      Establish an emergency CAB (E-CAB) protocol

      • When an emergency change request is received, you will not be able to wait until the regularly scheduled CAB meeting.
      • As a group, decide who will sit on the E-CAB and what their protocol will be when assessing and approving emergency changes.

      Change owner conferences with E-CAB (best efforts to reach them) through email or messaging.

      E-CAB members and business system owners are provided with change details. No decision is made without feedback from at least one E-CAB member.

      If business continuity is being affected, the Change Manager has authority to approve change.

      Full documentation of the change (a retroactive RFC) is done after the change and is then reviewed by the CAB.

      Info-Tech Best Practice

      Members of the E-CAB should be a subset of the CAB who are typically quick to respond to their messages, even at odd hours of the night.

      2.1.4 Determine an E-CAB Protocol for Your Organization

      Input

      • Current SOP or CAB charter (if available)

      Output

      • E-CAB protocol

      Materials

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board
      1. Gather the members of the E-CAB and other necessary representatives from the change management team.
      2. Determine the order of operations for the E-CAB in the event that an emergency change is needed.
      3. Consult the example emergency protocol below. Determine what roles and responsibilities are involved at each stage of the emergency change’s implementation.
      4. Document the E-CAB protocol in section 3.4 of your Change Management SOP.

      Example

      Assemble E-CAB

      Assess Change

      Test (if Applicable)

      Deploy Change

      Create Retroactive RFC

      Review With CAB

      Step 2.2

      Build Core Workflows

      Activities

      2.2.1 Build a CMDB-lite as a Reference for Requested Changes

      2.2.2 Create a Normal Change Process

      2.2.3 Create a Pre-Approved Change Process

      2.2.4 Create an Emergency Change Process

      Establish Roles and Workflows

      Step 2.1: Determine Roles and Responsibilities → Step 2.2: Build Core Workflows

      This step involves the following participants:

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board

      Outcomes of this step

      • Emergency change workflow
      • Normal process workflow
      • Pre-approved change workflow

      Establishing Workflows: Change Management Lifecycle

      Improve

      • A post-implementation review assesses the value of the actual change measured against the proposed change in terms of benefits, costs, and impact.
      • Results recorded in the change log.
      • Accountability: Change Manager Change Implementer

      Request

      • A change request (RFC) can be submitted via paper form, phone, email, or web portal.
      • Accountability: Change requester/Initiator

      Assess

      • The request is screened to ensure it meets an agreed-upon set of business criteria.
      • Changes are assessed on:
        • Impact of change
        • Risks or interdependencies
        • Resourcing and costs
      • Accountability: Change Manager

      Plan

      • Tasks are assigned, planned, and executed.
      • Change schedule is consulted and necessary resources are identified.
      • Accountability: Change Manager

      Approve

      • Approved requests are sent to the most efficient channel based on risk, urgency, and complexity.
      • Change is sent to CAB members for final review and approval
      • Accountability: Change Manager
        • Change Advisory Board

      Implement

      • Approved changes are deployed.
      • A rollback plan is created to mitigate risk.
      • Accountability: Change Manager Change Implementer

      Establishing workflows: employ a SIPOC model for process definition

      A good SIPOC (supplier, input, process, output, customer) model helps establish the boundaries of each process step and provides a concise definition of the expected outcomes and required inputs. It’s a useful and recommended next step for every workflow diagram.

      For change management, employ a SIPOC model to outline your CAB process:

      Supplier

      • Who or what organization provides the inputs to the process? The supplier can be internal or external.

      Input

      • What goes into the process step? This can be a document, data, information, or a decision.

      Process

      • Activities that occur in the process step that’s being analyzed.

      Output

      • What does the process step produce? This can be a document, data, information, or a decision.

      Customer

      • Who or what organization(s) takes the output of the process? The customer can be internal or external.

      Optional Fields

      Metrics

      • Top-level indicators that usually relate to the input and output, e.g. turnaround time, risk matrix completeness.

      Controls

      • Checkpoints to ensure process step quality.

      Dependencies

      • Other process steps that require the output.

      RACI

      • Those who are Responsible, Accountable, Consulted, or Informed (RACI) about the input, output, and/or process.

      Establish change workflows: assess requested changes to identify impact and dependencies

      An effective change assessment workflow is a holistic process that leaves no stone unturned in an effort to mitigate risk before any change reaches the approval stage. The four crucial areas of risk in a change workflow are:

      Dependencies

      Identify all components of the change.

      Ask how changes will affect:

      • Services on the same infrastructure?
      • Applications?
      • Infrastructure/app architecture?
      • Security?
      • Ability to support critical systems?

      Business Impact

      Frame the change from a business point of view to identify potential disruptions to business activities.

      Your assessment should cover:

      • Business processes
      • User productivity
      • Customer service
      • BCPs

      SLA Impact

      Each new change can impact the level of service available.

      Examine the impact on:

      • Availability of critical systems
      • Infrastructure and app performance
      • Infrastructure and app capacity
      • Existing disaster recovery plans and procedures

      Required Resources

      Once risk has been assessed, resources need to be identified to ensure the change can be executed.

      These include:

      • People (SMEs, tech support, work effort/duration)
      • System time for scheduled implementation
      • Hardware or software (new or existing, as well as tools)

      Establishing workflows: pinpoint dependencies to identify the need for additional changes

      An assessment of each change and a query of the CMDB needs to be performed as part of the change planning process to mitigate outage risk.

      • A version upgrade on one piece of software may require another component to be upgraded as well. For example, an upgrade to the database management system requires that an application that uses the database be upgraded or modified.
      • The sequence of the release must also be determined, as certain components may need to be upgraded before others. For example, if you upgrade the Exchange Server, a Windows update must be installed prior to the Exchange upgrade.
      • If you do not have a CMDB, consider building a CMDB-lite, which consists of a listing of systems, primary users, SMEs, business owners, and system dependencies (see next slide).

      Services Impacted

      • Have affected services been identified?
      • Have supporting services been identified?
      • Has someone checked the CMDB to ensure all dependencies have been accounted for?
      • Have we referenced the service catalog so the business approves what they’re authorizing?

      Technical Teams Impacted

      • Who will support the change throughout testing and implementation?
      • Will additional support be needed?
      • Do we need outside support from eternal suppliers?
      • Has someone checked the contract to ensure any additional costs have been approved?

      Build a dependency matrix to avoid change related collisions (optional)

      A CMDB-lite does not replace a CMDB but can be a valuable tool to leverage when requesting changes if you do not currently have configuration management. Consider the following inputs when building your own CMDB-lite.

      • System
        • To build a CMDB-lite, start with the top 10 systems in your environment that experience changes. This list can always be populated iteratively.
      • Primary Users
        • Listing the primary users will give a change requester a first glance at the impact of the change.
        • You can also use this information when looking at the change communication and training after the change is implemented.
      • SME/Backup
        • These are the staff that will likely build and implement the change. The backup is listed in case the primary is on holiday.
      • Business System Owner
        • The owner of the system is one of the people needed to sign off on the change. Having their support from the beginning of a change is necessary to build and implement it successfully.
      • Tier 1 Dependency
        • If the primary system experiences and outage, Tier 1 dependency functionality is also lost. To request a change, include the business system owner signoffs of the Tier 1 dependencies of the primary system.
      • Tier 2 Dependency
        • If the primary system experiences an outage, Tier 2 dependency functionality is lost, but there is an available workaround. As with Tier 1, this information can help you build a backout plan in case there is a change-related collision.
      • Tier 3 Dependency
        • Tier 3 functionality is not lost if the primary system experiences an outage, but nice-to-haves such as aesthetics are affected.

      2.2.1 Build a CMDB-lite as a Reference for Requested Changes

      Input

      • Current system ownership documentation

      Output

      • Documented reference for change requests (CMDB-lite)

      Materials

      • Whiteboard/flip charts (or shared screen if working remotely)
      • Sticky notes
      • Markers/pens

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board
      1. Start with a list of your top 10-15 systems/services with the highest volume of changes.
      2. Using a whiteboard, flip chart, or shared screen, complete the table below by filling the corresponding Primary Users, SMEs, Business System Owner, and Dependencies as shown below. It may help to use sticky notes.
      3. Iteratively populate the table as you notice gaps with incoming changes.
      SystemPrimary UsersSMEBackup SME(s)Business System OwnerTier 1 Dependency (system functionality is down)Tier 2 (impaired functionality/ workaround available)Tier 3 Dependency (nice to have)
      Email Enterprise Naomi Amos James
      • ITSMs
      • Scan-to-email
      • Reporting
       
      • Lots
      Conferencing Tool Enterprise Alex Shed James
      • Videoconferencing
      • Conference rooms (can use Facebook messenger instead in worst case scenario)
      • IM
      ITSM (Service Now) Enterprise (Intl.) Anderson TBD Mike
      • Work orders
      • Dashboards
      • Purchasing
       
      ITSM (Manage Engine) North America Bobbie Joseph Mike
      • Work orders
      • Dashboards
      • Purchasing
       

      Establishing workflows: create standards for change approvals to improve efficiency

      • Not all changes are created equal, and not all changes require the same degree of approval. As part of the change management process, it’s important to define who is the authority for each type of change.
      • Failure to do so can create bureaucratic bottlenecks if each change is held to an unnecessary high level of scrutiny, or unplanned outages may occur due to changes circumventing the formal approval process.
      • A balance must be met and defined to ensure the process is not bypassed or bottlenecked.

      Info-Tech Best Practice

      Define a list pre-approved changes and automate them (if possible) using your ITSM solution. This will save valuable time for more important changes in the queue.

      Example:

      Change CategoryChange Authority
      Pre-approved change Department head/manager
      Emergency change E-CAB
      Normal change – low and medium risk CAB
      Normal change – high risk CAB and CIO (for visibility)

      Example process: Normal Change – Change Initiation

      Change initiation allows for assurance that the request is in scope for change management and acts as a filter for out-of-scope changes to be redirected to the proper workflow. Initiation also assesses who may be assigned to the change and the proper category of the change, and results in an RFC to be populated before the change reaches the build and test phase.

      The image is a horizontal flow chart, depicting an example of a change process.

      The change trigger assessment is critical in the DevOps lifecycle. This can take a more formal role of a technical review board (TRB) or, with enough maturity, may be automated. Responsibilities such as deconfliction, dependency identification, calendar query, and authorization identification can be done early in the lifecycle to decrease or eliminate the burden on CAB.

      For the full process, refer to the Change Management Process Library.

      Example process: Normal Change – Technical Build and Test

      The technical build and test stage includes all technical prerequisites and testing needed for a change to pass before proceeding to approval and implementation. In addition to a technical review, a solution consisting of the implementation, rollback, communications, and training plan are also built and included in the RFC before passing it to the CAB.

      The image is a flowchart, showing the process for change during the technical build and test stage.

      For the full process, refer to the Change Management Process Library.

      Example process: Normal Change – Change Approval (CAB)

      Change approval can start with the Change Manager reviewing all incoming RFCs to filter them for completeness and check them for red flags before passing them to the CAB. This saves the CAB from discussing incomplete changes and allows the Change Manager to set a CAB agenda before the CAB meeting. If need be, change approval can also set vendor communications necessary for changes, as well as the final implementation date of the change. The CAB and Change Manager may follow up with the appropriate parties notifying them of the approval decision (accepted, rescheduled, or rejected).

      The image shows a flowchart illustrating the process for change approval.

      For the full process, refer to the Change Management Process Library.

      Example process: Normal Change – Change Implementation

      Changes should not end at implementation. Ensure you define post-implementation activities (documentation, communication, training etc.) and a post-implementation review in case the change does not go according to plan.

      The image is a flowchart, illustrating the work process for change implementation and post-implementation review.

      For the full process, refer to the Change Management Process Library.

      2.2.2 Create a Normal Change Process

      Input

      • Current SOP/workflow library

      Output

      • Normal change process

      Materials

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board
      1. Gather representatives from the change management team.
      2. Using the examples shown on the previous few slides, work as a group to determine the workflow for a normal change, with particular attention to the following sub-processes:
        1. Request
        2. Assessment
        3. Plan
        4. Approve
        5. Implementation and Post-Implementation Activities
      3. Optionally, you may create variations of the workflow for minor, medium, and major changes (e.g. there will be fewer authorizations for minor changes).
      4. For further documentation, you may choose to run the SIPOC activity for your CAB as outlined on this slide.
      5. Document the resulting workflows in the Change Management Process Library and section 11 of your Change Management SOP.

      Download the Change Management Process Library.

      Identify and convert low-risk normal changes to pre-approved once the process is established

      As your process matures, begin creating a list of normal changes that might qualify for pre-approval. The most potential for value in gains from change management comes from re-engineering and automating of high-volume changes. Pre-approved changes should save you time without threatening the live environment.

      IT should flag changes they would like pre-approved:

      • Once your change management process is firmly established, hold a meeting with all staff that make change requests and build changes.
      • Run a training session detailing the traits of pre-approved changes and ask these individuals to identify changes that might qualify.
      • These changes should be submitted to the Change Manager and reviewed, with the help of the CAB, to decide whether or not they qualify for pre-approval.

      Pre-approved changes are not exempt from due diligence:

      • Once a change is designated as pre-approved, the deployment team should create and compile all relevant documentation:
        • An RFC detailing the change, dependencies, risk, and impact.
        • Detailed procedures and required resources.
        • Implementation and backout plan.
        • Test results.
      • When templating the RFC for pre-approved changes, aim to write the documentation as if another SME were to implement it. This reduces confusion, especially if there’s staff turnover.
      • The CAB must approve, sign off, and keep a record of all documents.
      • Pre-approved changes must still be documented and recorded in the CMDB and change log after each deployment.

      Info-Tech Best Practice

      At the beginning of a change management process, there should be few active pre-approved changes. However, prior to launch, you may have IT flag changes for conversion.

      Example process: Pre-Approved Change Process

      The image shows two horizontal flow charts, the first labelled Pre-Approval of Recurring RFC, and the second labelled Implementation of Child RFC.

      For the full process, refer to the Change Management Process Library.

      Review the pre-approved change list regularly to ensure the list of changes are still low-risk and repeatable.

      IT environments change. Don’t be caught by surprise.

      • Changes which were once low-risk and repeatable may cause unforeseen incidents if they are not reviewed regularly.
      • Dependencies change as the IT environment changes. Ensure that the changes on the pre-approved change list are still low-risk and repeatable, and that the documentation is up to date.
      • If dependencies have changed, then move the change back to the normal category for reassessment. It may be redesignated as a pre-approved change once the documentation is updated.

      Info-Tech Best Practice

      Other reasons for moving a pre-approved change back to the normal category is if the change led to an incident during implementation or if there was an issue during implementation.

      Seek new pre-approved change submissions. → Re-evaluate the pre-approved change list every 4-6 months.

      The image shows a horizontal flow chart, depicting the process for a pre-approved change list review.

      For the full process, refer to the Change Management Process Library.

      2.2.3 Create a Pre-Approved Change Process

      Input

      • Current SOP/workflow library

      Output

      • Pre-approved change process

      Materials

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board
      1. Gather representatives from the change management team.
      2. Using the examples shown on the previous few slides, work as a group to determine the workflow for a pre-approved change, with particular attention to the following sub-processes:
        1. Request
        2. Assessment
        3. Plan
        4. Approve
      3. Document the process of a converting a normal change to pre-approved. Include the steps from flagging a low-risk change to creating the related RFC template.
      4. Document the resulting workflows in the Change Management Process Library and sections 4.2 and 13 of your Change Management SOP.

      Reserve the emergency designation for real emergencies

      • Emergency changes have one of the following triggers:
        • A critical incident is impacting user productivity.
        • An imminent critical incident will impact user productivity.
      • Unless a critical incident is being resolved or prevented, the change should be categorized as normal.
      • An emergency change differs from a normal change in the following key aspects:
        • An emergency change is required to recover from a major outage – there must be a validated service desk critical incident ticket.
        • An urgent business requirement is not an “emergency.”
        • An RFC is created after the change is implemented and the outage is over.
        • A review by the full CAB occurs after the change is implemented.
        • The first responder and/or the person implementing the change may not be the subject matter expert for that system.
      • In all cases, an RFC must be created and the change must be reviewed by the full CAB. The review should occur within two business days of the event.
      Sample ChangeQuick CheckEmergency?
      Install the latest critical patches from the vendor. Are the patches required to resolve or prevent an imminent critical incident? No
      A virus or worm invades the network and a patch is needed to eliminate the threat. Is the patch required to resolve or prevent an imminent critical incident? Yes

      Info-Tech Best Practice

      Change requesters should be made aware that senior management will be informed if an emergency RFC is submitted inappropriately. Emergency requests trigger urgent CAB meetings, are riskier to deploy, and delay other changes waiting in the queue.

      Example process: Emergency Change Process

      The image is a flowchart depicting the process for an emergency change process

      When building your emergency change process, have your E-CAB protocol from activity 2.1.4 handy.

      • Focus on the following requirements for an emergency process:
        • E-CAB protocol and scope: Does the SME need authorization first before working on the change or can the SME proceed if no E-CAB members respond?
        • Documentation and communication to stakeholders and CAB after the emergency change is completed.
        • Input from incident management.

      For the full process, refer to the Change Management Process Library.

      2.2.4 Create an Emergency Change Process

      Input

      • Current SOP/workflow library

      Output

      • Emergency change process

      Materials

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board
      1. Gather representatives from the change management team.
      2. Using the examples shown on the previous few slides, work as a group to determine the workflow for an emergency change, with particular attention to the following sub-processes:
        1. Request
        2. Assessment
        3. Plan
        4. Approve
      3. Ensure that the E-CAB protocol from activity 2.1.4 is considered when building your process.
      4. Document the resulting workflows in the Change Management Process Library and section 12 of your Change Management SOP.

      Case Study (part 2 of 4)

      Intel implemented a robust change management process.

      Industry: Technology

      Source: Daniel Grove, Intel

      Challenge

      Founded in 1968, the world’s largest microchip and semiconductor company employs over 100,000 people. Intel manufactures processors for major players in the PC market including Apple, Lenovo, HP, and Dell.

      Intel IT supports over 65,000 servers, 3.2 petabytes of data, over 70,000 PCs, and 2.6 million emails per day.

      Intel’s change management program is responsible for over 4,000 changes each week.

      Solution

      Intel identified 37 different change processes and 25 change management systems of record with little integration.

      Software and infrastructure groups were also very siloed, and this no doubt contributed to the high number of changes that caused outages.

      The task was simple: standards needed to be put in place and communication had to improve.

      Results

      Once process ownership was assigned and the role of the Change Manager and CAB clarified, it was a simple task to streamline and simplify processes among groups.

      Intel designed a new, unified change management workflow that all groups would adopt.

      Automation was also brought into play to improve how RFCs were generated and submitted.

      Phase 3

      Define the RFC and Post-Implementation Activities

      Define Change Management

      1.1 Assess Maturity

      1.2 Categorize Changes and Build Your Risk Assessment

      Establish Roles and Workflows

      2.1 Determine Roles and Responsibilities

      2.2 Build Core Workflows

      Define the RFC and Post-Implementation Activities

      3.1 Design the RFC

      3.2 Establish Post-Implementation Activities

      Measure, Manage, and Maintain

      4.1 Identify Metrics and Build the Change Calendar

      4.2 Implement the Project

      This phase will guide you through the following activities:

      • Design the RFC
      • Establish Post-Implementation Activities

      This phase involves the following participants:

      • IT Director
      • Infrastructure Manager
      • Change Manager
      • Members of the Change Advisory Board

      Step 3.1

      Design the RFC

      Activities

      3.1.1 Evaluate Your Existing RFC Process

      3.1.2 Build the RFC Form

      Define the RFC and Post-Implementation Activities

      Step 3.1: Design the RFC

      Step 3.2: Establish Post-Implementation Activities

      This step involves the following participants:

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board

      Outcomes of this step

      • A full RFC template and process that compliments the workflows for the three change categories

      A request for change (RFC) should be submitted for every non-standard change

      An RFC should be submitted through the formal change management practice for every change that is not a standard, pre-approved change (a change which does not require submission to the change management practice).

      • The RFC should contain all the information required to approve a change. Some information will be recorded when the change request is first initiated, but not everything will be known at that time.
      • Further information can be added as the change progresses through its lifecycle.
      • The level of detail that goes into the RFC will vary depending on the type of change, the size, and the likely impact of the change.
      • Other details of the change may be recorded in other documents and referenced in the RFC.

      Info-Tech Insight

      Keep the RFC form simple, especially when first implementing change management, to encourage the adoption of and compliance with the process.

      RFCs should contain the following information, at a minimum:

      1. Contact information for requester
      2. Description of change
      3. References to external documentation
      4. Items to be changed, reason for the change, and impact of both implementing and not implementing the change
      5. Change type and category
      6. Priority and risk assessment
      7. Predicted time frame, resources, and cost
      8. Backout or remediation plan
      9. Proposed approvers
      10. Scheduled implementation time
      11. Communications plan and post-implementation review

      3.1.1 Evaluate Your Existing RFC Process

      Input

      • Current RFC form or stock ITSM RFC
      • Current SOP (if available)

      Output

      • List of changes to the current RFC form and RFC process

      Materials

      Participants

      • IT Director
      • Infrastructure Manager
      • Change Manager
      • Members of the Change Advisory Board
      1. If the organization is already using an RFC form, review it as a group now and discuss its contents:
        • Does this RFC provide adequate information for the Change Manager and/or CAB to review?
        • Should any additional fields be added?
      2. Show the participants Info-Tech’s Request for Change Form Template and compare it to the one the organization is currently using.
      3. As a group, finalize an RFC table of contents that will be used to formalize a new or improved RFC.
      4. Decide which fields should be filled out by the requester before the initial RFC is submitted to the Change Manager:
        • Many sections of the RFC are relevant for change assessment and review. What information does the Change Manager need when they first receive a request?
        • The Change Manager needs enough information to ensure that the change is in scope and has been properly categorized.
      5. Decide how the RFC form should be submitted and reviewed; this can be documented in section 5 of your Change Management SOP.

      Download the Request for Change Form Template.

      Design the RFC to encourage process buy-in

      • When building the RFC, split the form up into sections that follow the normal workflow (e.g. Intake, Assessment and Build, Approval, Implementation/PIR). This way the form walks the requester through what needs to be filled and when.
      • Revisit the form periodically and solicit feedback to continually improve the user experience. If there’s information missing on the RFC that the CAB would like to know, add the fields. If there are sections that are not used or not needed for documentation, remove them.
      • Make sure the user experience surrounding your RFC form is a top priority – make it accessible, otherwise change requesters simply will not use it.
      • Take advantage of your ITSM’s dropdown lists, automated notifications, CMDB integrations, and auto-generated fields to ease the process of filling the RFC

      Draft:

      • Change requester
      • Requested date of deployment
      • Change risk: low/medium/high
      • Risk assessment
      • Description of change
      • Reason for change
      • Change components

      Technical Build:

      • Assess change:
        • Dependencies
        • Business impact
        • SLA impact
        • Required resources
        • Query the CMS
      • Plan and test changes:
        • Test plan
        • Test results
        • Implementation plan
        • Backout plan
        • Backout plan test results

      CAB:

      • Approve and schedule changes:
        • Final CAB review
        • Communications plan

      Complete:

      • Deploy changes:
        • Post-implementation review

      Designing your RFC: RFC draft

      • Change requester – link your change module to the active directory to pull the change requester’s contact information automatically to save time.
      • A requested date of deployment gives approvers information on timeline and can be used to query the change calendar for possible conflicts
      • Information about risk assessment based on impact and likelihood questionnaires are quick to fill out but provide a lot of information to the CAB. The risk assessment may not be complete at the draft stage but can be updated as the change is built. Ensure this field is up-to- date before it reaches CAB.
      • If you have a technical review stage where changes are directed to the proper workflow and resourcing is assessed, the description, reason, and change components are high-level descriptors of the change that will aid in discovery and lining the change up with the business vision (viability from both a technical and business standpoint).
      • Change requester
      • Requested date of deployment
      • Change Risk: low/medium/high
      • Risk assessment
      • Description of change
      • Reason for change
      • Change components

      Use the RFC to point to documentation already gathered in the DevOps lifecycle to cut down on unnecessary manual work while maintaining compliance.

      Designing your RFC: technical build

      • Dependencies and CMDB query, along with the proposed implementation date, are included to aid in calendar deconfliction and change scheduling. If there’s a conflict, it’s easier to reschedule the proposed change early in the lifecycle.
      • Business, SLA impact, and required resources can be tracked to provide the CAB with information on the business resources required. This can also be used to prioritize the change if conflicts arise.
      • Implementation, test, and backout plans must be included and assessed to increase the probability that a change will be implemented without failure. It’s also useful in the case of PIRs to determine root causes of change-related incidents.
      • Assess change:
        • Dependencies
        • Business impact
        • SLA impact
        • Required resources
        • Query the CMS
      • Plan and test changes:
        • Test plan
        • Test results
        • Implementation plan
        • Backout plan
        • Backout plan test results

      Designing your RFC: approval and deployment

      • Documenting approval, rejection, and rescheduling gives the change requester the go-ahead to proceed with the change, rationale on why it was prioritized lower than another change (rescheduled), or rationale on rejection.
      • Communications plans for appropriate stakeholders can also be modified and forwarded to the communications team (e.g. service desk or business system owners) before deployment.
      • Post-implementation activities and reviews can be conducted if need be before a change is closed. The PIR, if filled out, should then be appended to any subsequent changes of the same nature to avoid making the same mistake twice.
      • Approve and schedule changes:
        • Final CAB review
        • Communications plan
      • Deploy changes:
        • Post-implementation review

      Standardize the request for change protocol

      1. Submission Standards
        • Electronic submission will make it easier for CAB members to review the documentation.
        • As the change goes through the assessment, plan, and test phase, new documentation (assessments, backout plans, test results, etc.) can be attached to the digital RFC for review by CAB members prior to the CAB meeting.
        • Change management software won’t be necessary to facilitate the RFC submission and review; a content repository system, such as SharePoint, will suffice.
      2. Designate the first control point
        • All RFCs should be submitted to a single point of contact.
        • Ideally, the Change Manager or Technical Review Board should fill this role.
        • Whoever is tasked with this role needs the subject matter expertise to ensure that the change has been categorized correctly, to reject out-of-scope requests, or to ask that missing information be provided before the RFC moves through the full change management practice.

      Info-Tech Best Practice

      Technical and SME contacts should be noted in each RFC so they can be easily consulted during the RFC review.

      3.1.2 Build the RFC Form

      Input

      • Current RFC form or stock ITSM RFC
      • Current SOP (if available)

      Output

      • List of changes to the current RFC and RFC process

      Materials

      Participants

      • IT Director
      • Infrastructure Manager
      • Change Manager
      • Members of the Change Advisory Board
      1. Use Info-Tech’s Request for Change Form Template as a basis for your RFC form.
      2. Use this template to standardize your change request process and ensure that the appropriate information is documented effectively each time a request is made. The change requester and Change Manager should consolidate all information associated with a given change request in this form. This form will be submitted by the change requester and reviewed by the Change Manager.

      Case Study (part 3 of 4)

      Intel implemented automated RFC form generation.

      Industry: Technology

      Source: Daniel Grove, Intel

      Challenge

      Founded in 1968, the world’s largest microchip and semiconductor company employs over 100,000 people. Intel manufactures processors for major players in the PC market including Apple, Lenovo, HP, and Dell.

      Intel IT supports over 65,000 servers, 3.2 petabytes of data, over 70,000 PCs, and 2.6 million emails per day.

      Intel’s change management program is responsible for over 4,000 changes each week.

      Solution

      One of the crucial factors that was impacting Intel’s change management efficiency was a cumbersome RFC process.

      A lack of RFC usage was contributing to increased ad hoc changes being put through the CAB, and rescheduled changes were quite high.

      Additionally, ad hoc changes were also contributing heavily to unscheduled downtime within the organization.

      Results

      Intel designed and implemented an automated RFC form generator to encourage end users to increase RFC usage.

      As we’ve seen with RFC form design, the UX/UI of the form needs to be top notch, otherwise end users will simply circumvent the process. This will contribute to the problems you are seeking to correct.

      Thanks to increased RFC usage, Intel decreased emergency changes by 50% and reduced change-caused unscheduled downtime by 82%.

      Step 3.2

      Establish Post-Implementation Activities

      Activities

      3.2.1 Determine When the CAB Would Reject Tested Changes

      3.2.2 Create a Post-Implementation Activity Checklist

      Define the RFC and Post-Implementation Activities

      Step 3.1: Design RFC

      Step 3.2: Establish Post-Implementation Activities

      This step involves the following participants:

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board

      Outcomes of this step

      • A formalized post-implementation process for continual improvement

      Why would the CAB reject a change that has been properly assessed and tested?

      Possible reasons the CAB would reject a change include:

      • The product being changed is approaching its end of life.
      • The change is too costly.
      • The timing of the change conflicts with other changes.
      • There could be compliance issues.
      • The change is actually a project.
      • The risk is too high.
      • There could be regulatory issues.
      • The peripherals (test, backout, communication, and training plans) are incomplete.

      Info-Tech Best Practice

      Many reasons for rejection (listed above) can be caught early on in the process during the technical review or change build portion of the change. The earlier you catch these reasons for rejection, the less wasted effort there will be per change.

      Sample RFCReason for CAP Rejection
      There was a request for an update to a system that a legacy application depends on and only a specific area of the business was aware of the dependency. The CAB rejects it due to the downstream impact.
      There was a request for an update to a non-supported application, and the vendor was asking for a premium support contract that is very costly. It’s too expensive to implement, despite the need for it. The CAB will wait for an upgrade to a new application.
      There was a request to update application functionality to a beta release. The risk outweighs the business benefits.

      Determine When the CAB Would Reject Tested Changes

      Input

      • Current SOP (if available)

      Output

      • List of reasons to reject tested changes

      Materials

      • Whiteboard/flip charts (or shared screen if working remotely)
      • Projector
      • Markers/pens
      • Laptop with ITSM admin access
      • Project Summary Template

      Participants

      • IT Director
      • Infrastructure Manager
      • Change Manager
      • Members of the Change Advisory Board

      Avoid hand-offs to ensure a smooth implementation process

      The implementation phase is the final checkpoint before releasing the new change into your live environment. Once the final checks have been made to the change, it’s paramount that teams work together to transition the change effectively rather than doing an abrupt hand-off. This could cause a potential outage.

      1.

      • Deployment resources identified, allocated, and scheduled
      • Documentation complete
      • Support team trained
      • Users trained
      • Business sign-off
      • Target systems identified and ready to receive changes
      • Target systems available for installation maintenance window scheduled
      • Technical checks:
        • Disk space available
        • Pre-requisites met
        • Components/Services to be updated are stopped
        • All users disconnected
      • Download Info-Tech’sChange Management Pre-Implementation Checklist

      Implement change →

      2.

      1. Verification – once the change has been implemented, verify that all requirements are fulfilled.
      2. Review – ensure that all affected systems and applications are operating as predicted. Update change log.
      3. Transition – a crucial phase of implementation that’s often overlooked. Once the change implementation is complete from a technical point of view, it’s imperative that the team involved with the change inform and train the group responsible for managing the new change.

      Create a backout plan to reduce the risk of a failed change

      Every change process needs to plan for the potential for failure and how to address it effectively. Change management’s solution to this problem is a backout plan.

      A backout plan needs to contain a record of the steps that need to be taken to restore the live environment back to its previous state and maintain business continuity. A good backout plan asks the following questions:

      1. How will failure be determined? Who will make the determination to back out of a change be made and when?
      2. Do we fix on fail or do we rollback to the previous configuration?
      3. Is the service desk aware of the impending change? Do they have proper training?

      Notify the Service Desk

      • Notify the Service Desk about backout plan initiation.

      Disable Access

      • Disable user access to affected system(s).

      Conduct Checks

      • Conduct checks to all affected components.

      Enable User Access

      • Enable user access to affected systems.

      Notify the Service Desk

      • Notify the service desk that the backout plan was successful.

      Info-Tech Best Practice

      As part of the backout plan, consider the turnback point in the change window. That is, the point within the change window where you still have time to fully back out of the change.

      Ensure the following post-implementation review activities are completed

      Service Catalog

      Update the service catalog with new information as a result of the implemented change.

      CMDB

      Update new dependencies present as a result of the new change.

      Asset DB

      Add notes about any assets newly affected by changes.

      Architecture Map

      Update your map based on the new change.

      Technical Documentation

      Update your technical documentation to reflect the changes present because of the new change.

      Training Documentation

      Update your training documentation to reflect any information about how users interact with the change.

      Use a post-implementation review process to promote continual improvement

      The post-implementation review (PIR) is the most neglected change management activity.

      • All changes should be reviewed to understand the reason behind them, appropriateness, and recommendations for next steps.
      • The Change Manager manages the completion of information PIRs and invites RFC originators to present their findings and document the lessons learned.

      Info-Tech Best Practice

      Review PIR reports at CAB meetings to highlight the root causes of issues, action items to close identified gaps, and back-up documentation required. Attach the PIR report to the relevant RFC to prevent similar changes from facing the same issues in the future.

      1. Why do a post-implementation review?
        • Changes that don’t fail but don’t perform well are rarely reviewed.
        • Changes may fail subtly and still need review.
        • Changes that cause serious failures (i.e. unplanned downtime) receive analysis that is unnecessarily in-depth.
      2. What are the benefits?
        • A proactive, post-implementation review actually uses less resources than reactionary change reviews.
        • Root-cause analysis of failed changes, no matter what the impact.
        • Insight into changes that took longer than projected.
        • Identification of previously unidentified risks affecting changes.

      Determine the strategy for your PIR to establish a standardized process

      Capture the details of your PIR process in a table similar to the one below.

      Frequency Part of weekly review (IT team meeting)
      Participants
      • Change Manager
      • Originator
      • SME/supervisor/impacted team(s)

      Categories under review

      Current deviations and action items from previous PIR:

      • Complete
      • Partially complete
      • Complete, late
      • Change failed, rollback succeeded
      • Change failed, rollback failed
      • Major deviation from implementation plan
      Output
      • Root cause or failure or deviation
      • External factors
      • Remediation focus areas
      • Remediation timeline (follow-up at appropriate time)
      Controls
      • Reviewed at next CAB meeting
      • RFC close is dependent on completion of PIR
      • Share with the rest of the technical team
      • Lessons learned stored in the knowledgebase and attached to RFC for easy search of past issues.

      3.2.2 Create a Post-Implementation Activity Checklist

      Input

      • Current SOP (if available)

      Output

      • List of reasons to reject tested changes

      Materials

      Participants

      • CIO
      • IT Managers
      • Change Manager
      • Members of the Change Advisory Board
      1. Gather representatives from the change management team.
      2. Brainstorm duties to perform following the deployment of a change. Below is a sample list:
        • Example:
          • Was the deployment successful?
            • If no, was the backout plan executed successfully?
          • List change-related incidents
          • Change assessment
            • Missed dependencies
            • Inaccurate business impact
            • Incorrect SLA impact
            • Inaccurate resources
              • Time
              • Staff
              • Hardware
          • System testing
          • Integration testing
          • User acceptance testing
          • No backout plan
          • Backout plan failure
          • Deployment issues
      3. Record your results in the Change Management Post-Implementation Checklist.

      Download the Change Management Post-Implementation Checklist

      Case Study

      Microsoft used post-implementation review activities to mitigate the risk of a critical Azure outage.

      Industry: Technology

      Source: Jason Zander, Microsoft

      Challenge

      In November 2014, Microsoft deployed a change intended to improve Azure storage performance by reducing CPU footprint of the Azure Table Front-Ends.

      The deployment method was an incremental approach called “flighting,” where software and configuration deployments are deployed incrementally to Azure infrastructure in small batches.

      Unfortunately, this software deployment caused a service interruption in multiple regions.

      Solution

      Before the software was deployed, Microsoft engineers followed proper protocol by testing the proposed update. All test results pointed to a successful implementation.

      Unfortunately, engineers pushed the change out to the entire infrastructure instead of adhering to the traditional flighting protocol.

      Additionally, the configuration switch was incorrectly enabled for the Azure Blob storage Front-Ends.

      A combination of the two mistakes exposed a bug that caused the outage.

      Results

      Thankfully, Microsoft had a backout plan. Within 30 minutes, the change was rolled back on a global scale.

      It was determined that policy enforcement was not integrated across the deployment system. An update to the system shifted the process of policy enforcement from human-based decisions and protocol to automation via the deployment platform.

      Defined PIR activities enabled Microsoft to take swift action against the outage and mitigate the risk of a serious outage.

      Phase 4

      Measure, Manage, and Maintain

      Define Change Management

      1.1 Assess Maturity

      1.2 Categorize Changes and Build Risk Assessment

      Establish Roles and Workflows

      2.1 Determine Roles and Responsibilities

      2.2 Build Core Workflows

      Define RFC and Post-Implementation Activities

      3.1 Design RFC

      3.2 Establish post-implementation activities

      Measure, Manage, and Maintain

      4.1 Identify Metrics and Build the Change Calendar

      4.2 Implement the Project

      This phase will guide you through the following activities:

      • Identify Metrics and Build the Change Calendar
      • Implement the Project

      This phase involves the following participants:

      • CIO/IT Director
      • IT Managers
      • Change Manager

      Step 4.1

      Identify Metrics and Build the Change Calendar

      Activities

      4.1.1 Create an Outline for Your Change Calendar

      4.1.2 Determine Metrics, Key Performance Indicators (KPIs), and Critical Success Factors (CSFs)

      4.1.3 Track and Record Metrics Using the Change Management Metrics Tool

      Measure, Manage, and Maintain

      Step 4.1: Identify Metrics and Build the Change Calendar

      Step 4.2: Implement the Project

      This step involves the following participants:

      • CIO/IT Director
      • IT Managers
      • Change Manager

      Outcomes of this step

      • Clear definitions of change calendar content
      • Guidelines for change calendar scheduling
      • Defined metrics to measure the success of change management with associated reports, KPIs, and CSFs

      Enforce a standard method of prioritizing and scheduling changes

      The impact of not deploying the change and the benefit of deploying it should determine its priority.

      Risk of Not Deploying

      • What is the urgency of the change?
      • What is the risk to the organization if the change is not deployed right away?
      • Will there be any lost productivity, service disruptions, or missed critical business opportunities?
        • Timing
          • Does the proposed timing work with the approved changes already on the change schedule?
          • Has the change been clash checked so there are no potential conflicts over services or resources?
        • Once prioritized, a final deployment date should be set by the CAB. Check the change calendar first to avoid conflicts.

      Positive Impact of Deployment

      • What benefits will be realized once the change is deployed?
      • How significant is the opportunity that triggered the change?
      • Will the change lead to a positive business outcome (e.g. increased sales)?

      “The one who has more clout or authority is usually the one who gets changes scheduled in the time frame they desire, but you should really be evaluating the impact to the organization. We looked at the risk to the business of not doing the change, and that’s a good way of determining the criticality and urgency of that change.” – Joseph Sgandurra, Director, Service Delivery, Navantis

      Info-Tech Insight

      Avoid a culture where powerful stakeholders are able to push change deployment on an ad hoc basis. Give the CAB the full authority to make approval decisions based on urgency, impact, cost, and availability of resources.

      Develop a change schedule to formalize the planning process

      A change calendar will help the CAB schedule changes more effectively and increase visibility into upcoming changes across the organization.

      1. Establish change windows in a consistent change schedule:
        • Compile a list of business units that would benefit from a change.
        • Look for conflicts in the change schedule.
        • Avoid scheduling two or more major business units in a day.
        • Consider clients when building your change windows and change schedule.
      2. Gain commitments from key participants:
        • These individuals can confirm if there are any unusual or cyclical business requirements that will impact the schedule.
      3. Properly control your change calendar to improve change efficiency:
        • Look at the proposed start and end times: Are they sensible? Does the implementation window leave time for anything going wrong or needing to roll back the change?
        • Special considerations: Are there special circumstances that need to be considered? Ask the business if you don’t know.
        • The key principle is to have a sufficient window available for implementing changes so you only need to set up calendar freezes for sound business or technical reasons.

      Our mantra is to put it on the calendar. Even if it’s a preapproved change and doesn’t need a vote, having it on the calendar helps with visibility. The calendar is the one-stop shop for scheduling and identifying change dependencies.“ – Wil Clark, Director of Service and Performance Management, University of North Texas Systems

      Provide clear definitions of what goes on the change calendar and who’s responsible

      Roles

      • The Change Manager will be responsible for creating and maintaining a change calendar.
      • Only the Change Manager can physically alter the calendar by adding a new change after the CAB has agreed upon a deployment date.
      • All other CAB members, IT support staff, and other impacted stakeholders should have access to the calendar on a read-only basis to prevent people from making unauthorized changes to deployment dates.

      Inputs

      • Freeze periods for individual business departments/applications (e.g. finance month-end periods, HR payroll cycle, etc. – all to be investigated).
      • Maintenance windows and planned outage periods.
      • Project schedules, and upcoming major/medium changes.
      • Holidays.
      • Business hours (some departments work 9-5, others work different hours or in different time zones, and user acceptance testing may require business users to be available).

      Guidelines

      • Business-defined freeze periods are the top priority.
      • No major or medium normal changes should occur during the week between Christmas and New Year’s Day.
      • Vendor SLA support hours are the preferred time for implementing changes.
      • The vacation calendar for IT will be considered for major changes.
      • Change priority: High > Medium > Low.
      • Minor changes and preapproved changes have the same priority and will be decided on a case-by-case basis.

      The change calendar is a critical pre-requisite to change management in DevOps. Use the calendar to be proactive with proposed implementation dates and deconfliction before the change is finished.

      4.1.1 Create Guidelines for Your Change Calendar

      Input

      • Current change calendar guidelines

      Output

      • Change calendar inputs and schedule checklist

      Materials

      Participants

      • Change Manager
      • Members of the Change Advisory Board
      • Service Desk Manager
      • Operations (optional)
      1. Gather representatives from the change management team.
        • Example:
          • The change calendar/schedule includes:
            • Approved and scheduled normal changes.
            • Scheduled project work.
            • Scheduled maintenance windows.
            • Change freeze periods with affected users noted:
              • Daily/weekly freeze periods.
              • Monthly freeze periods.
              • Annual freeze periods.
              • Other critical business events.
      2. Create a checklist to run through before each change is scheduled:
        • Check the schedule and assess resource availability:
          • Will user productivity be impacted?
          • Are there available resources (people and systems) to implement the change?
          • Is the vendor available? Is there a significant cost attached to pushing change deployment before the regularly scheduled refresh?
          • Are there dependencies? Does the deployment of one change depend on the earlier deployment of another?
      3. Record your results in your Project Summary Template.

      Start measuring the success of your change management project using three key metrics

      Number of change-related incidents that occur each month

      • Each month, record the number of incidents that can be directly linked to a change. This can be done using an ITSM tool or manually by service desk staff.
      • This is a key success metric: if you are not tracking change-related incidents yet, start doing so as soon as possible. This is the metric that the CIO and business stakeholders will be most interested in because it impacts users directly.

      Number of unauthorized changes applied each month

      • Each month, record the number of changes applied without approval. This is the best way to measure adherence to the process.
      • If this number decreases, it demonstrates a reduction in risk, as more changes are formally assessed and approved before being deployed.

      Percentage of emergency changes

      • Each month, compare the number of emergency change requests to the total number of change requests.
      • Change requesters often designate changes as emergencies as a way of bypassing the process.
      • A reduction in emergency changes demonstrates that your process is operating smoothly and reduces the risk of deploying changes that have not been properly tested.

      Info-Tech Insight

      Start simple. Metrics can be difficult to tackle if you’re starting from scratch. While implementing your change management practice, use these three metrics as a starting point, since they correlate well with the success of change management overall. The following few slides provide more insight into creating metrics for your change process.

      If you want more insight into your change process, measure the progress of each step in change management with metrics

      Improve

      • Number of repeat failures (i.e. making the same mistake twice)
      • Number of changes converted to pre-approved
      • Number of changes converted from pre-approved back to normal

      Request

      • What percentage of change requests have errors or lack appropriate support?
      • What percentage of change requests are actually projects, service requests, or operational tasks?
      • What percentage of changes have been requested before (i.e. documented)?

      Assess

      • What percentage of change requests are out of scope?
      • What percentage of changes have been requested before (i.e. documented)?
      • What are the percentages of changes by category (normal, pre-approved, emergency)?

      Plan

      • What percentage of change requests are reviewed by the CAB that should have been pre-approved or emergency (i.e. what percentage of changes are in the wrong category)?

      Approve

      • Number of changes broken down by department (business unit/IT department to be used in making core/optional CAB membership more efficient)
      • Number of workflows that can be automated

      Implement

      • Number of changes completed on schedule
      • Number of changes rolled back
      • What percentage of changes caused an incident?

      Use metrics to inform project KPIs and CSFs

      Leverage the metrics from the last slide and convert them to data communicable to IT, management, and leadership

      • To provide value, metrics and measurements must be actionable. What actions can be taken as a result of the data being presented?
      • If the metrics are not actionable, there is no value and you should question the use of the metric.
      • Data points in isolation are mostly meaningless to inform action. Observe trends in your metrics to inform your decisions.
      • Using a framework to develop measurements and metrics provides a defined methodology that enables a mapping of base measurements through CSFs.
      • Establishing the relationship increases the value that measurements provide.

      Purposely use SDLC and change lifecycle metrics to find bottlenecks and automation candidates.

      Metrics:

      Metrics are easily measured datapoints that can be pulled from your change management tool. Examples: Number of changes implemented, number of changes without incident.

      KPIs:

      Key Performance Indicators are metrics presented in a way that is easily digestible by stakeholders in IT. Examples: Change efficiency, quality of changes.

      CSFs:

      Critical Success Factors are measures of the business success of change management taken by correlating the CSF with multiple KPIs. Examples: consistent and efficient change management process, a change process mapped to business needs

      List in-scope metrics and reports and align them to benefits

      Metric/Report (by team)Benefit
      Total number of RFCs and percentages by category (pre-approved, normal, emergency, escalated support, expedited)
      • Understand change management activity
      • Tracking maturity growth
      • Identifying “hot spots”
      Pre-approved change list (and additions/removals from the list) Workload and process streamlining (i.e. reduce “red tape” wherever possible)
      Average time between RFC lifecycle stages (by service/application) Advance planning for proposed changes
      Number of changes by service/application/hardware class
      • Identifying weaknesses in the architecture
      • Vendor-specific TCO calculations
      Change triggers Business- vs. IT-initiated change
      Number of RFCs by lifecycle stage Workload planning
      List of incidents related to changes Visible failures of the CM process
      Percentage of RFCs with a tested backout/validation plan Completeness of change planning
      List of expedited changes Spotlighting poor planning and reducing the need for this category going forward (“The Hall of Shame”)
      CAB approval rate Change coordinator alignment with CAB priorities – low approval rate indicates need to tighten gatekeeping by the change coordinator
      Calendar of changes Planning

      4.1.2 Determine Metrics, Key Performance Indicators (KPIs), and Critical Success Factors (CSFs)

      Input

      • Current metrics

      Output

      • List of trackable metrics, KPIs and CSFs

      Materials

      Participants

      • Change Manager
      • Members of the Change Advisory Board
      • Service Desk Manager
      • Operations (optional)
      1. Draw three tables for metrics, KPIs, and CSFs.
      2. Starting with the CSF table, fill in all relevant CSFs that your group wishes to track and measure.
      3. Next, work to determine relevant KPIs correlated with the CSFs and metrics needed to measure the KPIs. Use the tables included below (taken from section 14 of the Change Management SOP) to guide the process.
      4. Record the results in the tables in section 14 of your Change Management SOP.
      5. Decide on where and when to review the metrics to discuss your change management strategy. Designate and owner and record in the RACI and Communications section of your Change Management SOP.
      Ref #Metric

      M1

      Number of changes implemented for a time period
      M2 Number of changes successfully implemented for a time period
      M3 Number of changes implemented causing incidents
      M4 Number of accepted known errors when change is implemented
      M5 Total days for a change build (specific to each change)
      M6 Number of changes rescheduled
      M7 Number of training questions received following a change
      Ref#KPIProduct
      K1 Successful changes for a period of time (approach 100%) M2 / M1 x 100%
      K2 Changes causing incidents (approach 0%) M3 / M1 x 100%
      K3 Average days to implement a change ΣM5 / M1
      K4 Change efficiency (approach 100%) [1 - (M6 / M1)] x 100%
      K5 Quality of changes being implemented (approach 100%) [1 - (M4 / M1)] x 100%
      K6 Change training efficiency (approach 100%) [1 - (M7 / M1)] x 100%
      Ref#CSFIndicator
      C1 Successful change management process producing quality changes K1, K5
      C2 Consistent efficient change process K4, K6
      C3 Change process maps to business needs K5, K6

      Measure changes in selected metrics to evaluate success

      Once you have implemented a standardized change management practice, your team’s goal should be to improve the process, year over year.

      • After a process change has been implemented, it’s important to regularly monitor and evaluate the CSFs, KPIs, and metrics you chose to evaluate. Examine whether the process change you implemented has actually resolved the issue or achieved the goal of the critical success factor.
      • Establish a schedule for regularly reviewing the key metrics. Assess changes in those metrics and determine progress toward reaching objectives.
      • In addition to reviewing CSFs, KPIs, and metrics, check in with the release management team and end users to measure their perceptions of the change management process once an appropriate amount of time has passed.
      • Ensure that metrics are telling the whole story and that reporting is honest in order to be informative.

      Outcomes of standardizing change management should include:

      1. Improved efficiency, effectiveness, and quality of changes.
      2. Changes and processes are more aligned with the business needs and strategy.
      3. Improved maturity of change processes.

      Info-Tech Best Practice

      Make sure you’re measuring the right things and considering all sources of information. It’s very easy to put yourself in a position where you’re congratulating yourselves for improving on a specific metric such as number of releases per month, but satisfaction remains low.

      4.1.3 Track and Record Metrics Using the Change Management Metrics Tool

      Input

      • Current metrics

      Output

      • List of trackable metrics, KPIs and CSFs to be observed over the length of a year

      Materials

      Participants

      • Change Manager
      • Members of the Change Advisory Board
      • Service Desk Manager
      • Operations (optional)

      Tracking the progress of metrics is paramount to the success of any change management process. Use Info-Tech’s Change Management Metrics Tool to record metrics and track your progress. This tool is intended to be a substitute for organizations who do not have the capability to track change-related metrics in their ITSM tool.

      1. Input metrics from the previous activity to track over the course of a year.
      2. To record your metrics, open the tool and go to tab 2. The tool is currently primed to record and track five metrics. If you need more than that, you can edit the list in the hidden calculations tab.
      3. To see the progress of your metrics, move to tab 3 to view a dashboard of all metrics in the tool.

      Download the Change Management Metrics Tool

      Case Study

      A federal credit union was able to track maturity growth through the proper use of metrics.

      Industry: Federal Credit Union (anonymous)

      Source: Info-Tech Workshop

      Challenge

      At this federal credit union, the VP of IT wanted a tight set of metrics to engage with the business, communicate within IT, enable performance management of staff, and provide visibility into workload demands, among other requirements.

      The organization was suffering from “metrics fatigue,” with multiple reports being generated from all groups within IT, to the point that weekly/monthly reports were being seen as spam.

      Solution

      Stakeholders were provided with an overview of change management benefits and were asked to identify one key attribute that would be useful to their specific needs.

      Metrics were designed around the stakeholder needs, piloted with each stakeholder group, fine-tuned, and rolled out.

      Some metrics could not be automated off-the-shelf and were rolled out in a manual fashion. These metrics were subsequently automated and finally made available through a dashboard.

      Results

      The business received clear guidance regarding estimated times to implement changes across different elements of the environment.

      The IT managers were able to plan team workloads with visibility into upstream change activity.

      Architects were able to identify vendors and systems that were the leading source of instability.

      The VP of IT was able to track the maturity growth of the change management process and proactively engage with the business on identified hot spots.

      Step 4.2

      Implement the Project

      Activities

      4.2.1 Use a Communications Plan to Gain End User Buy-In

      4.2.2 Create a Project Roadmap to Track Your Implementation Progress

      Measure, Manage, and Maintain

      Step 4.1: Identify Metrics and Build the Change Calendar

      Step 3.2: Implement the Project

      This step involves the following participants:

      • CIO/IT Director
      • IT Managers
      • Change Manager

      Outcomes of this step

      • A communications plan for key messages to communicate to relevant stakeholders and audiences
      • A roadmap with assigned action items to implement change management

      Success of the new process will depend on introducing change and gaining acceptance

      Change management provides value by promptly evaluating and delivering changes required by the business and by minimizing disruption and rework caused by failed changes. Communication of your new change management process is key. If people do not understand the what and why, it will fail to provide the desired value.

      Info-Tech Best Practice

      Gather feedback from end users about the new process: if the process is too bureaucratic, end users are more likely to circumvent it.

      Main Challenges with Communication

      • Many people fail before they even start because they are buried in a mess created before they arrived – either because of a failed attempt to get change management implemented or due to a complicated system that has always existed.
      • Many systems are maintained because “that’s the way it’s always been done.”
      • Organizations don’t know where to start; they think change management is too complex a process.
      • Each group needs to follow the same procedure – groups often have their own processes, but if they don’t agree with one another, this could cause an outage.

      Educate affected stakeholders to prepare for organizational change

      An organizational change management plan should be part of your change management project.

      • Educate stakeholders about:
        • The process change (describe it in a way that the user can understand and is clear and concise).
          • IT changes will be handled in a standardized and repeatable fashion to minimize change-related incidents.
        • Who is impacted?
          • All users.
        • How are they impacted?
          • All change requests will be made using a standard form and will not be deployed until formal approval is received.
        • Change messaging.
          • How to communicate the change (benefits).
        • Learning and development – training your users on the change.
          • Develop and deliver training session on the Change Management SOP to familiarize users with this new method of handling IT change.

      Host a lunch-and-learn session

      • For the initial deployment, host a lunch-and-learn session to educate the business on the change management practice. Relevant stakeholders of affected departments should host it and cover the following topics:
      • What is change management (change management/change control)?
      • The value of change management.
      • What the Change Management SOP looks like.
      • Who is involved in the change management process (the CAB, etc.)?
      • What constitutes a pre-approved change and an emergency change?
      • An overview of the process, including how to avoid unauthorized changes.
      • Who should they contact in case of questions?

      Communicate the new process to all affected stakeholders

      Do not surprise users or support staff with changes. This will result in lost productivity and low satisfaction with IT services.

      • User groups and the business need to be given sufficient notice of an impending change.
      • This will allow them to make appropriate plans to accept the change, minimizing the impact of the change on productivity.
      • A communications plan will be documented in the RFC while the release is being built and tested.
      • It’s the responsibility of the change team to execute on the communications plan.

      Info-Tech Insight

      The success of change communication can be measured by monitoring the number of service desk tickets related to a change that was not communicated to users.

      Communication is crucial to the integration and overall implementation of your change management initiative. An effective communications plan will:

      • Gain support from management at the project proposal phase.
      • Create end-user buy-in once the program is set to launch.
      • Maintain the presence of the program throughout the business.
      • Instill ownership throughout the business from top-level management to new hires.

      Create your communications plan to anticipate challenges, remove obstacles, and ensure buy-in

      Management

      Technicians

      Business Stakeholders

      Provide separate communications to key stakeholder groups

      Why? What problems are you trying to solve?

      What? What processes will it affect (that will affect me)?

      Who? Who will be affected? Who do I go to if I have issues with the new process?

      When? When will this be happening? When will it affect me?

      How? How will these changes manifest themselves?

      Goal? What is the final goal? How will it benefit me?

      Info-Tech Insight

      Pay close attention to the medium of communication. For example, stakeholders on their feet all day would not be as receptive to an email communication compared to those who primarily work in front of a computer. Put yourself into various stakeholders’ shoes to craft a tailored communication of change management.

      4.2.1 Use a Communications Plan to Gain End User Buy-In

      Input

      • List of stakeholder groups for change management

      Output

      • Tailored communications plans for various stakeholder groups

      Materials

      Participants

      • Change Manager
      • Members of the Change Advisory Board
      • Service Desk Manager
      • Operations (optional)
      1. Using Info-Tech’s Change Management Communications Plan, identify key audiences or stakeholder groups that will be affected by the new change management practice.
      2. For each group requiring a communications plan, identify the following:
        • The benefits for that group of individuals.
        • The impact the change will have on them.
        • The best communication method(s) for them.
        • The time frame of the communication.
      3. Complete this information in a table like the one below:
      GroupBenefitsImpactMethodTimeline
      IT Standardized change process All changes must be reviewed and approved Poster campaign 6 months
      End Users Decreased wait time for changes Formal process for RFCs Lunch-and-learn sessions 3 months
      Business Reduced outages Increased involvement in planning and approvals Monthly reports 1 year
      1. Discuss the communications plan:
        • Will this plan ensure that users are given adequate opportunities to accept the changes being deployed?
        • Is the message appropriate for each audience? Is the format appropriate for each audience?
        • Does the communication include training where necessary to help users adopt any new functions/workflows being introduced?

      Download the Change Management Communications Plan

      Present your SOP to key stakeholders and obtain their approval

      Now that you have completed your Change Management SOP, the final step is to get sign-off from senior management to begin the rollout process.

      Know your audience:

      • Determine the service management stakeholders who will be included in the audience for your presentation.
      • You want your presentation to be succinct and hard hitting. Management’s time is tight and they will lose interest if you drag out the delivery.
      • Briefly speak about the need for more formal change management and emphasize the benefits of implementing a more formal process with a SOP.
      • Present your current state assessment results to provide context before presenting the SOP itself.
      • As with any other foundational activity, be prepared with some quick wins to gain executive attention.
      • Be prepared to review with both technical and less technical stakeholders.

      Info-Tech Insight

      The support of senior executive stakeholders is critical to the success of your SOP rollout. Try to wow them with project benefits and make sure they know about the risks/pain points.

      Download the Change Management Project Summary Template

      4.2.2 Create a Project Roadmap to Track Your Implementation Progress

      Input

      • List of implementation tasks

      Output

      • Roadmap and timeline for change management implementation

      Materials

      Participants

      • Change Manager
      • Members of the Change Advisory Board
      • Service Desk Manager
      • Operations (optional)
      1. Info-Tech’s Change Management Roadmap Tool helps you identify and prioritize tasks that need to be completed for the change management implementation project.
      2. Use this tool to identify each action item that will need to be completed as part of the change management initiative. Chart each action item, assign an owner, define the duration, and set a completion date.
      3. Use the resulting rocket diagram as a guide to task completion as you work toward your future state.

      Download the Change Management Roadmap Tool

      Case Study (part 4 of 4)

      Intel implemented a robust change management process.

      Industry: Technology

      Source: Daniel Grove, Intel

      Challenge

      Founded in 1968, the world’s largest microchip and semiconductor company employs over 100,000 people. Intel manufactures processors for major players in the PC market including Apple, Lenovo, HP, and Dell.

      Intel IT supports over 65,000 servers, 3.2 petabytes of data, over 70,000 PCs, and 2.6 million emails per day.

      Intel’s change management program is responsible for over 4,000 changes each week.

      Solution

      Intel had its new change management program in place and the early milestones planned, but one key challenge with any new project is communication.

      The company also needed to navigate the simplification of a previously complex process; end users could be familiar with any of the 37 different change processes or 25 different change management systems of record.

      Top-level buy-in was another concern.

      Results

      Intel first communicated the process changes by publishing the vision and strategy for the project with top management sponsorship.

      The CIO published all of the new change policies, which were supported by the Change Governance Council.

      Intel cited the reason for success as the designation of a Policy and Guidance Council – a group designed to own communication and enforcement of the new policies and processes put in place.

      Summary of Accomplishment

      Problem Solved

      You now have an outline of your new change management process. The hard work starts now for an effective implementation. Make use of the communications plan to socialize the new process with stakeholders and the roadmap to stay on track.

      Remember as you are starting your implementation to keep your documents flexible and treat them as “living documents.” You will likely need to tweak and refine the processware and templates several times to continually improve the process. Furthermore, don’t shy away from seeking feedback from your stakeholders to gain buy-in.

      Lastly, keep an eye on your progress with objective, data-driven metrics. Leverage the trends in your data to drive your decisions. Be sure to revisit the maturity assessment not only to measure and visualize your progress, but to gain insight into your next steps.

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech workshop.

      Contact your account representative for more information.

      workshops@infotech.com

      1-888-670-8889

      Additional Support

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech workshop.

      To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.

      Info-Tech analysts will join you and your team at your location or welcome you to Info-Tech’s historic office in Toronto, Ontario, Canada to participate in an innovative onsite workshop.

      Contact your account representative for more information.

      workshops@infotech.com 1-888-670-8889

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      1.1.2 Complete a Change Management Maturity Assessment

      Run through the change management maturity assessment with tailored commentary for each action item outlining context and best practices.

      2.2.1 Plot the Process for a Normal Change

      Build a normal change process using Info-Tech’s Change Management Process Library template with an analyst helping you to right size the process for your organization.

      Related Info-Tech Research

      Standardize the Service Desk

      Improve customer service by driving consistency in your support approach and meeting SLAs.

      Stabilize Release and Deployment Management

      Maintain both speed and control while improving the quality of deployments and releases within the infrastructure team.

      Incident and Problem Management

      Don’t let persistent problems govern your department.

      Select Bibliography

      AXELOS Limited. ITIL Foundation: ITIL 4th edition. TSO, 2019, pp. 118–120.

      Behr, Kevin and George Spafford. The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps. IT Revolution Press. 2013.

      BMC. “ITIL Change Management.” BMC Software Canada, 22 December 2016.

      Brown, Vance. “Change Management: The Greatest ROI of ITIL.” Cherwell Service Management.

      Cisco. “Change Management: Best Practices.” Cisco, 10 March 2008.

      Grove, Daniel. “Case Study ITIL Change Management Intel Corporation.” PowerShow, 2005.

      ISACA. “COBIT 5: Enabling Processes.” ISACA, 2012.

      Jantti, M. and M. Kainulainen. “Exploring an IT Service Change Management Process: A Case Study.” ICDS 2011: The Fifth International Conference on Digital Society, 23 Feb. 2011.

      Murphy, Vawns. “How to Assess Changes.” The ITSM Review, 29 Jan. 2016.

      Nyo, Isabel. “Best Practices for Change Management in the Age of DevOps.” Atlassian Engineering, 12 May 2021.

      Phillips, Katherine W., Katie A. Liljenquist, and Margaret A. Neale. “Better Decisions Through Diversity.” Kellogg Insight, 1 Oct. 2010.

      Pink Elephant. “Best Practices for Change Management.” Pink Elephant, 2005.

      Sharwood, Simon. “Google broke its own cloud by doing two updates at once.” The Register, 24 Aug. 2016.

      SolarWinds. “How to Eliminate the No: 1 Cause of Network Downtime.” SolarWinds Tech Tips, 25 Apr. 2014.

      The Stationery Office. “ITIL Service Transition: 2011.” The Stationary Office, 29 July 2011.

      UCISA. “ITIL – A Guide to Change Management.” UCISA.

      Zander, Jason. “Final Root Cause Analysis and Improvement Areas: Nov 18 Azure Storage Service Interruption.” Microsoft Azure: Blog and Updates, 17 Dec. 2014.

      Appendix I: Expedited Changes

      Employ the expedited change to promote process adherence

      In many organizations, there are changes which may not fit into the three prescribed categories. The reason behind why the expedited category may be needed generally falls between two possibilities:

      1. External drivers dictate changes via mandates which may not fall within the normal change cycle. A CIO, judge, state/provincial mandate, or request from shared services pushes a change that does not fall within a normal change cycle. However, there is no imminent outage (therefore it is not an emergency). In this case, an expedited change can proceed. Communicate to the change requester that IT and the change build team will still do their best to implement the change without issue, but any extra risk of implementing this expedited change (compared to an normal change) will be absorbed by the change requester.
      2. The change requester did not prepare for the change adequately. This is common if a new change process is being established (and stakeholders are still adapting to the process). Change requesters or the change build team may request the change to be done by a certain date that does not fall within the normal change cycle, or they simply did not give the CAB enough time to vet the change. In this case, you may use the expedited category as a metric (or a “Hall of Shame” example). If you identify a department or individual that frequently request expedited changes, use the expedited category as a means to educate them about the normal change to discourage the behavior moving forward.

      Two possible ways to build an expedited change category”

      1. Build the category similar to an emergency change. In this case, one difference would be the time allotted to fully obtain authorization of the change from the E-CAB and business owner before implementing the change (as opposed to the emergency change workflow).
      2. Have the expedited change reflect the normal change workflow. In this case, all the same steps of the normal change workflow are followed except for expedited timelines between processes. This may include holding an impromptu CAB meeting to authorize the change.

      Example process: Expedited Change Process

      The image is a flowchart, showing the process for Expedited Change.

      For the full process, refer to the Change Management Process Library.

      Appendix II: Optimize IT Change Management in a DevOps Environment

      Change Management cannot be ignored because you are DevOps or Agile

      But it can be right-sized.

      The core tenets of change management still apply no matter the type of development environment an organization has. Changes in any environment carry risk of degrading functionality, and must therefore be vetted. However, the amount of work and rigor put into different stages of the change life cycle can be altered depending on the maturity of the development workflows. The following are several stage gates for change management that MUST be considered if you are a DevOps or Agile shop:

      • Intake assessment (separation of changes from projects, service requests, operational tasks)
        • Within a DevOps or Agile environment, many of the application changes will come directly from the SDLC and projects going live. It does not mean a change must go through CAB, but leveraging the pre-approved category allows for an organization to stick to development lifecycles without being heavily bogged down by change bureaucracy.
      • Technical review
        • Leveraging automation, release contingencies, and the current SDLC documentation to decrease change risk allows for various changes to be designated as pre-approved.
      • Authorization
        • Define the authorization and dependencies of a change early in the lifecycle to gain authorization and necessary signoffs.
      • Documentation/communication
        • Documentation and communication are post-implementation activities that cannot be ignored. If documentation is required throughout the SDLC, then design the RFC to point to the correct documentation instead of duplicating information.

      "Understand that process is hard and finding a solution that fits every need can be tricky. With this change management process we do not try to solve every corner case so much as create a framework by which best judgement can be used to ensure maximum availability of our platforms and services while still complying with our regulatory requirements and making positive changes that will delight our customers.“ -IT Director, Information Cybersecurity Organization

      Five principals for implementing change in DevOps

      Follow these best practices to make sure your requirements are solid:

      People

      The core differences between an Agile or DevOps transition and a traditional approach are the restructuring and the team behind it. As a result, the stakeholders of change management must be onboard for the process to work. This is the most difficult problem to solve if it’s an issue, but open avenues of feedback for a process build is a start.

      DevOps Lifecycles

      • Plan the dev lifecycle so people can’t skirt it. Ensure the process has automated checks so that it’s more work to skirt the system than it is to follow it. Make the right process the process of least resistance.
      • Plan changes from the start to ensure that cross-dependencies are identified early and that the proposed implementation date is deconflicted and visible to other change requesters and change stakeholders.

      Automation

      Automation comes in many forms and is well documented in many development workflows. Having automated signoffs for QA/security checks and stakeholders/cross dependency owner sign offs may not fully replace the CAB but can ease the burden on discussions before implementation.

      Contingencies

      Canary releases, phased releases, dark releases, and toggles are all options you can employ to reduce risk during a release. Furthermore, building in contingencies to the test/rollback plan decreases the risk of the change by decreasing the factor of likelihood.

      Continually Improve

      Building change from the ground up doesn’t meant the process has to be fully fledged before launch. Iterative improvements are possible before achieving an optimal state. Having the proper metrics on the pain points and bottlenecks in the process can identify areas for automation and improvement.

      Increasing the proportion of pre-approved changes

      Leverage the traditional change infrastructure to deploy changes quickly while keeping your risk low.

      • To designate a change as a pre-approved change it must have a low risk rating (based on impact and likelihood). Fortunately, many of the changes within the Agile framework are designed to be small and lower risk (at least within application development). Putting in the work ahead of time to document these changes, template RFCs, and document the dependencies for various changes allows for a shift in the proportion of pre-approved changes.
      • The designation of pre-approved changes is an ongoing process. This is not an overnight initiative. Measure the proportion of changes by category as a metric, setting goals and interim goals to shift the change proportion to a desired ratio.

      The image is a bar graph, with each bar having 3 colour-coded sections: Emergency, Normal, and Pre-Approved. The first bar is before, where the largest change category is Normal. The second bar is after, and the largest change category is Pre-Approved.

      Turn your CAB into a virtual one

      • The CAB does not have to fully disappear in a DevOps environment. If the SDLC is built in a way that authorizes changes through peer reviews and automated checks, by the time it’s deployed, the job of the CAB should have already been completed. Then the authorization stage-gate (traditionally, the CAB) shifts to earlier in the process, reducing the need for an actual CAB meeting. However, the change must still be communicated and documented, even if it’s a pre-approved change.
      • As the proportion of changes shifts from a high degree of normal changes to a high degree of pre-approved changes, the need for CAB meetings should decrease even further. As an end-state, you may reserve actual CAB meetings for high-profile changes (as defined by risk).
      • Lastly, change management does not disappear as a process. Periodic reviews of change management metrics and the pre-approved change list must still be completed.

      Build a Software Quality Assurance Program

      • Buy Link or Shortcode: {j2store}284|cart{/j2store}
      • member rating overall impact: 9.6/10 Overall Impact
      • member rating average dollars saved: $20,972 Average $ Saved
      • member rating average days saved: 14 Average Days Saved
      • Parent Category Name: Testing, Deployment & QA
      • Parent Category Link: /testing-deployment-and-qa
      • Today’s rapidly scaling and increasingly complex products create mounting pressure on delivery teams to release new systems and changes quickly and with sufficient quality.
      • Many organizations lack the critical capabilities and resources needed to satisfy their growing testing backlog, risking product success.

      Our Advice

      Critical Insight

      • Testing is often viewed as a support capability rather than an enabler of business growth. It receives focus and investment only when it becomes a visible problem.
      • The rise in security risks, aggressive performance standards, constantly evolving priorities, and misunderstood quality policies further complicate QA as it drives higher expectations for effective practices.
      • QA starts with good requirements. Tests are only as valuable as the requirements they are validating and verifying. Early QA improves the accuracy of downstream tests and reduces costs of fixing defects late in delivery.
      • Quality is an organization-wide accountability. Upstream work can have extensive ramifications if all roles are not accountable for the decisions they make.
      • Quality must account for both business and technical requirements. Valuable change delivery is cemented in a clear understanding of quality from both business and IT perspectives.

      Impact and Result

      • Standardize your definition of a product. Come to an organizational agreement of what attributes define a high-quality product. Accommodate both business and IT perspectives in your definition.
      • Clarify the role of QA throughout your delivery pipeline. Indicate where and how QA is involved throughout product delivery. Instill quality-first thinking in each stage of your pipeline to catch defects and issues early.
      • Structure your test design, planning, execution, and communication practices to better support your quality definition and business and IT environments and priorities. Adopt QA good practices to ensure your tests satisfy your criteria for a high-quality and successful product.

      Build a Software Quality Assurance Program Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should build a strong foundation for quality, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Define your QA process

      Standardize your product quality definition and your QA roles, processes, and guidelines according to your business and IT priorities.

      • Build a Strong Foundation for Quality – Phase 1: Define Your QA Process
      • Test Strategy Template

      2. Adopt QA good practices

      Build a solid set of good practices to define your defect tolerances, recognize the appropriate test coverage, and communicate your test results.

      • Build a Strong Foundation for Quality – Phase 2: Adopt QA Good Practices
      • Test Plan Template
      • Test Case Template
      [infographic]

      Workshop: Build a Software Quality Assurance Program

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Define Your QA Process

      The Purpose

      Discuss your quality definition and how quality is interpreted from both business and IT perspectives.

      Review your case for strengthening your QA practice.

      Review the standardization of QA roles, processes, and guidelines in your organization.

      Key Benefits Achieved

      Grounded understanding of quality that is accepted across IT and between the business and IT.

      Clear QA roles and responsibilities.

      A repeatable QA process that is applicable across the delivery pipeline.

      Activities

      1.1 List your QA objectives and metrics.

      1.2 Adopt your foundational QA process.

      Outputs

      Quality definition and QA objectives and metrics.

      QA guiding principles, process, and roles and responsibilities.

      2 Adopt QA Good Practices

      The Purpose

      Discuss the practices to reveal the sufficient degree of test coverage to meet your acceptance criteria, defect tolerance, and quality definition.

      Review the technologies and tools to support the execution and reporting of your tests.

      Key Benefits Achieved

      QA practices aligned to industry good practices supporting your quality definition.

      Defect tolerance and acceptance criteria defined against stakeholder priorities.

      Identification of test scenarios to meet test coverage expectations.

      Activities

      2.1 Define your defect tolerance.

      2.2 Model and prioritize your tests.

      2.3 Develop and execute your QA activities.

      2.4 Communicate your QA activities.

      Outputs

      Defect tolerance levels and courses of action.

      List of test cases and scenarios that meet test coverage expectations.

      Defined test types, environment and data requirements, and testing toolchain.

      Test dashboard and communication flow.

      Position IT to Support and Be a Leader in Open Data Initiatives

      • Buy Link or Shortcode: {j2store}326|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.
      • member rating average days saved: Read what our members are saying
      • Parent Category Name: Innovation
      • Parent Category Link: /innovation
      • Open data programs are often seen as unimportant or not worth taking up space in the budget in local government.
      • Open data programs are typically owned by a single open data evangelist who works on it as a side-of-desk project.
      • Having a single resource spend a portion of their time on open data doesn’t allow the open data program to mature to the point that local governments are realizing benefits from it.
      • It is difficult to gain buy-in for open data as it is hard to track the benefits of an open data program.

      Our Advice

      Critical Insight

      • Local government can help push the world towards being more open, unlocking economic benefits for the wider economy.
      • Cities don’t know the solutions to all of their problems often they don’t know all of the problems they have. Release data as a platform to crowdsource solutions and engage your community.
      • Build your open data policies in collaboration with the community. It’s their data, let them shape the way it’s used!

      Impact and Result

      • Level-set expectations for your open data program. Every local government is different in terms of the benefits they can achieve with open data; ensure the business understands what is realistic to achieve.
      • Create a team of open data champions from departments outside of IT. Identify potential champions for the team and use this group to help gain greater business buy-in and gather feedback on the program’s direction.
      • Follow the open data maturity model in order to assess your current state, identify a target state, and assess capability gaps that need to be improved upon.
      • Use industry best practices to develop an open data policy and processes to help improve maturity of the open data program and reach your desired target state.
      • Identify metrics that you can use to track, and communicate the success of, the open data program.

      Position IT to Support and Be a Leader in Open Data Initiatives Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should develop your open data program, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Set the foundation for the success of your open data program

      Identify your open data program's current state maturity, and gain buy-in from the business for the program.

      • Position IT to Support and Be a Leader in Open Data Initiatives – Phase 1: Set the Foundation for the Success of Your Open Data Program
      • Open Data Maturity Assessment
      • Open Data Program – IT Stakeholder Powermap Template
      • Open Data in Our City Stakeholder Presentation Template

      2. Grow the maturity of your open data program

      Identify a target state maturity and reach it through building a policy and processes and the use of metrics.

      • Position IT to Support and Be a Leader in Open Data Initiatives – Phase 2: Grow the Maturity of Your Open Data Program
      • Open Data Policy Template
      • Open Data Process Template
      • Open Data Process Descriptions Template
      • Open Data Process Visio Templates (Visio)
      • Open Data Process Visio Templates (PDF)
      • Open Data Metrics Template
      [infographic]

      Workshop: Position IT to Support and Be a Leader in Open Data Initiatives

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Define Business Drivers for Open Data Program

      The Purpose

      Ensure that the open data program is being driven out from the business in order to gain business support.

      Key Benefits Achieved

      Identify drivers for the open data program that are coming directly from the business.

      Activities

      1.1 Understand constraints for the open data program.

      1.2 Conduct interviews with the business to gain input on business drivers and level-set expectations.

      1.3 Develop list of business drivers for open data.

      Outputs

      Defined list of business drivers for the open data program

      2 Assess Current State and Define Target State of the Open Data Program

      The Purpose

      Understand the gaps between where your program currently is and where you want it to be.

      Key Benefits Achieved

      Identify top processes for improvement in order to bring the open data program to the desired target state maturity.

      Activities

      2.1 Perform current state maturity assessment.

      2.2 Define desired target state with business input.

      2.3 Highlight gaps between current and target state.

      Outputs

      Defined current state maturity

      Identified target state maturity

      List of top processes to improve in order to reach target state maturity

      3 Develop an Open Data Policy

      The Purpose

      Develop a draft open data policy that will give you a starting point when building your policy with the community.

      Key Benefits Achieved

      A draft open data policy will be developed that is based on best-practice standards.

      Activities

      3.1 Define the purpose of the open data policy.

      3.2 Establish principles for the open data program.

      3.3 Develop a rough governance outline.

      3.4 Create a draft open data policy document based on industry best-practice examples.

      Outputs

      Initial draft of open data policy

      4 Develop Open Processes and Identify Metrics

      The Purpose

      Build open data processes and identify metrics for the program in order to track benefits realization.

      Key Benefits Achieved

      Formalize processes to set in place to improve the maturity of the open data program.

      Identify metrics that can track the success of the open data program.

      Activities

      4.1 Develop the roles that will make up the open data program.

      4.2 Create processes for new dataset requests, updates of existing datasets, and the retiring of datasets.

      4.3 Identify metrics that will be used for measuring the success of the open data program.

      Outputs

      Initial draft of open data processes

      Established metrics for the open data program

      Cost and Budget Management

      • Buy Link or Shortcode: {j2store}8|cart{/j2store}
      • Related Products: {j2store}8|crosssells{/j2store}
      • Up-Sell: {j2store}8|upsells{/j2store}
      • member rating overall impact: 9.5/10
      • member rating average dollars saved: $2,000
      • member rating average days saved: 5
      • Parent Category Name: Financial Management
      • Parent Category Link: /financial-management

      The challenge

      • IT is seen as a cost center in most organizations. Your IT spend is fuelled by negative sentiment instead of contributing to business value.

      • Budgetary approval is difficult, and in many cases, the starting point is lowering the cost-income ratio without looking at the benefits.
      • Provide the right amount of detail in your budgets to tell your investment and spending story. Align it with the business story. Too much detail only increases confusion, too little suspicion.

      Our advice

      Insight

      An effective IT budget complements the business story with how you will achieve the expected business targets.

      • Partner with the business to understand the strategic direction of the company and its future needs.
      • Know your costs and the value you will deliver.
      • Present your numbers and story clearly and credibly. Excellent delivery is part of good communication.
      • Guide your company by clearly explaining the implications of different choices they can make.

      Impact and results 

      • Get a head-start on your IT forecasting exercise by knowing the business strategy and what initiatives they will launch.
      • The coffee corner works! Pre-sell your ideas in quick chats.
      • Do not make innovation budgets bigger than they need to be. It undermines your credibility.
      • You must know your history to accurately forecast your IT operations cost and how it will evolve based on expected business changes.
      • Anticipate questions. IT discretionary proposals are often challenged. Think ahead of time about what areas your business partners will focus on and be ready with researched and credible responses.
      • When you have an optimized budget, tie further cost reductions to consequences in service delivery or deferred projects, or a changed operating model.

      The roadmap

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      Get started

      Our concise executive brief shows you why you should develop a budget based on value delivery. We'll show you our methodology and the ways we can help you in completing this.

      Plan for budget success

      • Build an IT Budget That Demonstrates Value Delivery – Phase 1: Plan (ppt)
      • IT Budget Interview Guide (doc)

      Build your budget.

      • Build an IT Budget That Demonstrates Value Delivery – Phase 2: Build (ppt)
      • IT Cost Forecasting Tool (xls)

      Sell your budget

      • Build an IT Budget That Demonstrates Value Delivery – Phase 3: Sell (ppt)
      • IT Budget Presentation (ppt)

       

      Deliver a Customer Service Training Program to Your IT Department

      • Buy Link or Shortcode: {j2store}484|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $4,339 Average $ Saved
      • member rating average days saved: 6 Average Days Saved
      • Parent Category Name: Service Desk
      • Parent Category Link: /service-desk
      • The scope of service that the service desk must provide has expanded. With the growing complexity of technologies to support, it becomes easy to forget the customer service side of the equation. Meanwhile, customer expectations for prompt, frictionless, and exceptional service from anywhere have grown.
      • IT departments struggle to hire and retain talented service desk agents with the right mix of technical and customer service skills.
      • Some service desk agents don’t believe or understand that customer service is an integral part of their role.
      • Many IT leaders don’t ask for feedback from users to know if there even is a customer service problem.

      Our Advice

      Critical Insight

      • There’s a common misconception that customer service skills can’t be taught, so no effort is made to improve those skills.
      • Even when there is a desire to improve customer service, it’s hard for IT teams to make time for training and improvement when they’re too busy trying to keep up with tickets.
      • A talented service desk agent with both great technical and customer service skills doesn’t have to be a rare unicorn, and an agent without innate customer service skills isn’t a lost cause. Relevant and impactful customer service habits, techniques, and skills can be taught through practical, role-based training.
      • IT leaders can make time for this training through targeted, short modules along with continual on-the-job coaching and development.

      Impact and Result

      • Good customer service is critical to the success of the service desk. How a service desk treats its customers will determine its customers' satisfaction with not only IT but also the company as a whole.
      • Not every technician has innate customer service skills. IT managers need to provide targeted, practical training on what good customer service looks like at the service desk.
      • One training session is not enough to make a change. Leaders must embed the habits, create a culture of engagement and positivity, provide continual coaching and development, regularly gather customer feedback, and seek ways to improve.

      Deliver a Customer Service Training Program to Your IT Department Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should deliver customer service training to your team, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      • Deliver a Customer Service Training Program to Your IT Department – Executive Brief
      • Deliver a Customer Service Training Program to Your IT Department Storyboard

      1. Deliver customer service training to your IT team

      Understand the importance of customer service training, then deliver Info-Tech's training program to your IT team.

      • Customer Service Training for the Service Desk – Training Deck
      • Customer Focus Competency Worksheet
      • Cheat Sheet: Service Desk Communication
      • Cheat Sheet: Service Desk Written Communication
      [infographic]

      Optimize the Mentoring Program to Build a High-Performing Learning Organization

      • Buy Link or Shortcode: {j2store}596|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Employee Development
      • Parent Category Link: /train-and-develop
      • Many organizations have introduced mentoring programs without clearly defining and communicating the purpose and goals around having a program; they simply jumped on the mentoring bandwagon.
      • As a result, these programs have little impact. They don’t add value for mentors, mentees, or the organization.
      • It can be difficult to design a program that is well-suited to your organization, will be adopted by employees, and will drive the results you are looking for.
      • In particular, it is difficult to successfully match mentors and mentees so both derive maximum value from the endeavor.

      Our Advice

      Critical Insight

      • As workforce composition shifts, there is a need for mentoring programs to move beyond the traditional senior–junior format option; organizational culture and goals will dictate the best approach.
      • An organization’s mentoring program doesn’t need to be restricted to one format; individual preferences and goals should also factor in. Be open to choosing format on a case-by-case basis.
      • Be sure to gain upper management buy-in and support early to ensure mentoring becomes a valued part of your organization.
      • Ensure that goal setting, communication, ongoing support for participants, and evaluation all play a role in your mentoring program.

      Impact and Result

      • Mentoring can have a significant positive impact on mentor, mentee, and organization.
      • Mentees gain guidance and advice on their career path and skill development. Mentors often experience re-engagement with their job and the satisfaction of helping another person.
      • Mentoring participants benefit from obtaining different perspectives of both the business and work-related problems. Participation in a mentoring program has been linked to greater access to promotions, pay raises, and increased job satisfaction.
      • Mentoring can have a number of positive outcomes for the organization, including breaking down silos, transferring institutional knowledge, accelerating leadership skills, fostering open communication and dialogue, and resolving conflict.

      Optimize the Mentoring Program to Build a High-Performing Learning Organization Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Align the mentoring program with the organizational culture and goals

      Build a best-fit program that creates a learning culture.

      • Storyboard: Optimize the Mentoring Program to Build a High Performing Learning Organization

      2. Assess the organizational culture and current mentoring program

      Align mentoring practices with culture to improve the appropriateness and effectiveness of the program.

      • Mentoring Program Diagnostic

      3. Align mentoring practices with culture to improve the appropriateness and effectiveness of the program.

      Track project progress and have all program details defined in a central location.

      • Mentoring Project Plan Template
      • Peer Mentoring Guidelines
      • Mentoring Program Guidelines

      4. Gather feedback from the mentoring program participants

      Evaluate the success of the program.

      • Mentoring Project Feedback Surveys Template

      5. Get mentoring agreements in place

      Improve your mentoring capabilities.

      • Mentee Preparation Checklist
      • Mentoring Agreement Template
      [infographic]

      Implement Infrastructure Shared Services

      • Buy Link or Shortcode: {j2store}456|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Operations Management
      • Parent Category Link: /i-and-o-process-management
      • Organizations have service duplications for unique needs. These duplications increase business expenditure.
      • Lack of collaboration between business units to share their services increases business cost and reduces business units’ faith to implement shared services.
      • Transitioning infrastructure to shared services is challenging for many organizations. It requires an accurate planning and efficient communication between participating business units.

      Our Advice

      Critical Insight

      • Identify your current process, tool, and people capabilities before implementing shared services. Understand the financial compensations prior to implementation and assess if your organization is ready for transitioning to shared services model.
      • Do not implement shared services when the nature of the services differs greatly between business units.

      Impact and Result

      • Understand benefits of shared services for the business and determine whether transitioning to shared services would benefit the organization.
      • Identify the best implementation plan based on goals, needs, and services.
      • Build a shared-services process to manage the plan and ensure its success.

      Implement Infrastructure Shared Services Research & Tools

      Start here – Read the Executive Brief

      Read our concise Executive Brief to find out why you should implement shared services, review Info-Tech’s methodology, and understand the ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Conduct gap analysis

      Identify benefits of shared services to your organization and define implementation challenges.

      • Implement Infrastructure Shared Services – Phase 1: Conduct Gap Analysis
      • Shared Services Implementation Executive Presentation
      • Shared Services Implementation Business Case Template
      • Shared Services Implementation Assessment Tool

      2. Choose the right path

      Identify your process and staff capabilities and discover which services will be transitioned to shared services plan. It will also help you to figure out the best model to choose.

      • Implement Infrastructure Shared Services – Phase 2: Choose the Right Path
      • Sample Enterprise Services

      3. Plan the transition

      Discuss an actionable plan to implement shared services to track the project. Walk through a communication plan to document the goals, progress, and expectations with customer stakeholders.

      • Implement Infrastructure Shared Services – Phase 3: Plan the Transition
      • Shared Services Implementation Roadmap Tool
      • Shared Services Implementation Customer Communication Plan
      [infographic]

      Workshop: Implement Infrastructure Shared Services

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Identify Challenges

      The Purpose

      Establish the need for change.

      Key Benefits Achieved

      Set a clear understanding about benefits of shared services to your organization.

      Activities

      1.1 Identify your organization’s main drivers for using a shared services model.

      1.2 Define if it is beneficial to implement shared services.

      Outputs

      Shared services mission

      Shared services goals

      2 Assess Your Capabilities

      The Purpose

      Become aware of challenges to implement shared services and your capabilities for such transition.

      Key Benefits Achieved

      Discover the primary challenges for transitioning to shared services, eliminate resistance factors, and identify your business potentials for implementation.

      Activities

      2.1 Identify your organization’s resistance to implement shared services.

      2.2 Assess process and people capabilities.

      Outputs

      Shared Services Business Case

      Shared Services Assessment

      3 Define the Model

      The Purpose

      Determine the shared services model.

      Key Benefits Achieved

      Identify the core services to be shared and the best model that fits your organization.

      Activities

      3.1 Define core services that will be moved to shared services.

      3.2 Assess different models of shared services and pick the one that satisfies your goals and needs.

      Outputs

      List of services to be transferred to shared services

      Shared services model

      4 Implement and Communicate

      The Purpose

      Define and communicate the tasks to be delivered.

      Key Benefits Achieved

      Confidently approach key stakeholders to make the project a reality.

      Activities

      4.1 Define the roadmap for implementing shared services.

      4.2 Make a plan to communicate changes.

      Outputs

      List of initiatives to reach the target state, strategy risks, and their timelines

      Draft of a communication plan

      Establish Data Governance – APAC Edition

      • Buy Link or Shortcode: {j2store}348|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $172,999 Average $ Saved
      • member rating average days saved: 63 Average Days Saved
      • Parent Category Name: Data Management
      • Parent Category Link: /data-management
      • Organisations are faced with challenges associated with changing data landscapes, evolving business models, industry disruptions, regulatory and compliance obligations, and changing and maturing user landscapes and demands for data.
      • Although the need for a data governance program is often evident, organisations miss the mark when their data governance efforts are not directly aligned to delivering measurable business value by supporting key strategic initiatives, value streams, and their underlying business capabilities.

      Our Advice

      Critical Insight

      • Your organisation’s value streams and the associated business capabilities require effectively governed data. Without this, you face the impact of elevated operational costs, missed opportunities, eroded stakeholder satisfaction, and exposure to increased business risk.
      • Ensure your data governance program delivers measurable business value by aligning the associated data governance initiatives with the business architecture.
      • Data governance must continuously align with the organisation’s enterprise governance function. It should not be perceived as an IT pet project, but rather as a business-driven initiative.

      Impact and Result

      Info-Tech’s approach to establishing and sustaining effective data governance is anchored in the strong alignment of organisational value streams and their business capabilities with key data governance dimensions and initiatives.

      • Align with enterprise governance, business strategy and organizational value streams to ensure the program delivers measurable business value.
      • Understand your current data governance capabilities and build out a future state that is right sized and relevant.
      • Define data governance leadership, accountability, and responsibility, supported by an operating model that effectively manages change and communication and fosters a culture of data excellence.

      Establish Data Governance – APAC Edition Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Data Governance Research – A step-by-step document to ensure that the people handling the data are involved in the decisions surrounding data usage, data quality, business processes, and change implementation.

      Data governance is a strategic program that will help your organisation control data by managing the people, processes, and information technology needed to ensure that accurate and consistent data policies exist across varying lines of the business, enabling data-driven insight. This research will provide an overview of data governance and its importance to your organization, assist in making the case and securing buy-in for data governance, identify data governance best practices and the challenges associated with them, and provide guidance on how to implement data governance best practices for a successful launch.

      • Establish Data Governance – Phases 1-3 – APAC

      2. Data Governance Planning and Roadmapping Workbook – A structured tool to assist with establishing effective data governance practices.

      This workbook will help your organisation understand the business and user context by leveraging your business capability map and value streams, developing data use cases using Info-Tech's framework for building data use cases, and gauging the current state of your organisation's data culture.

      • Data Governance Planning and Roadmapping Workbook – APAC

      3. Data Use Case Framework Template – An exemplar template to highlight and create relevant use cases around the organisation’s data-related problems and opportunities.

      This business needs gathering activity will highlight and create relevant use cases around data-related problems or opportunities that are clear and contained and, if addressed, will deliver value to the organisation. This template provides a framework for data requirements and a mapping methodology for creating use cases.

      • Data Use Case Framework Template – APAC

      4. Data Governance Initiative Planning and Roadmap Tool – A visual roadmapping tool to assist with establishing effective data governance practices.

      This tool will help your organisation plan the sequence of activities, capture start dates and expected completion dates, and create a roadmap that can be effectively communicated to the organisation.

      • Data Governance Initiative Planning and Roadmap Tool – APAC

      5. Business Data Catalogue – A comprehensive template to help you to document the key data assets that are to be governed based on in-depth business unit interviews, data risk/value assessments, and a data flow diagram for the organisation.

      Use this template to document information about key data assets such as data definition, source system, possible values, data sensitivity, data steward, and usage of the data.

      • Business Data Catalogue – APAC

      6. Data Governance Program Charter Template – A program charter template to sell the importance of data governance to senior executives.

      This template will help get the backing required to get a data governance project rolling. The program charter will help communicate the project purpose, define the scope, and identify the project team, roles, and responsibilities.

      • Data Governance Program Charter Template – APAC

      7. Data Policies – A set of policy templates to support the data governance framework for the organisation.

      This set of policies supports the organisation's use and management of data to ensure that it efficiently and effectively serves the needs of the organisation.

      • Data Governance Policy – APAC
      • Data Classification Policy, Standard, and Procedure – APAC
      • Data Quality Policy, Standard, and Procedure – APAC
      • Data Management Definitions – APAC
      • Metadata Management Policy, Standard, and Procedure – APAC
      • Data Retention Policy and Procedure – APAC
      [infographic]

      Workshop: Establish Data Governance – APAC Edition

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Establish Business Context and Value

      The Purpose

      Identify key business data assets that need to be governed.

      Create a unifying vision for the data governance program.

      Key Benefits Achieved

      Understand the value of data governance and how it can help the organisation better leverage its data.

      Gain knowledge of how data governance can benefit both IT and the business.

      Activities

      1.1 Establish business context, value, and scope of data governance at the organisation.

      1.2 Introduction to Info-Tech’s data governance framework.

      1.3 Discuss vision and mission for data governance.

      1.4 Understand your business architecture, including your business capability map and value streams.

      1.5 Build use cases aligned to core business capabilities.

      Outputs

      Sample use cases (tied to the business capability map) and a repeatable use case framework

      Vision and mission for data governance

      2 Understand Current Data Governance Capabilities and Plot Target-State Levels

      The Purpose

      Assess which data contains value and/or risk and determine metrics that will determine how valuable the data is to the organisation.

      Assess where the organisation currently stands in data governance initiatives.

      Determine gaps between the current and future states of the data governance program.

      Key Benefits Achieved

      Gain a holistic understanding of organisational data and how it flows through business units and systems.

      Identify which data should fall under the governance umbrella.

      Determine a practical starting point for the program.

      Activities

      2.1 Understand your current data governance capabilities and maturity.

      2.2 Set target-state data governance capabilities.

      Outputs

      Current state of data governance maturity

      Definition of target state

      3 Build Data Domain to Data Governance Role Mapping

      The Purpose

      Determine strategic initiatives and create a roadmap outlining key steps required to get the organisation to start enabling data-driven insights.

      Determine timing of the initiatives.

      Key Benefits Achieved

      Establish clear direction for the data governance program.

      Step-by-step outline of how to create effective data governance, with true business-IT collaboration.

      Activities

      3.1 Evaluate and prioritise performance gaps.

      3.2 Develop and consolidate data governance target-state initiatives.

      3.3 Define the role of data governance: data domain to data governance role mapping.

      Outputs

      Target-state data governance initiatives

      Data domain to data governance role mapping

      4 Formulate a Plan to Get to Your Target State

      The Purpose

      Consolidate the roadmap and other strategies to determine the plan of action from day one.

      Create the required policies, procedures, and positions for data governance to be sustainable and effective.

      Key Benefits Achieved

      Prioritised initiatives with dependencies mapped out.

      A clearly communicated plan for data governance that will have full business backing.

      Activities

      4.1 Identify and prioritise next steps.

      4.2 Define roles and responsibilities and complete a high-level RACI.

      4.3 Wrap-up and discuss next steps and post-workshop support.

      Outputs

      Initialised roadmap

      Initialised RACI

      Further reading

      Establish Data Governance

      Deliver measurable business value.

      Analyst Perspective

      Establish a data governance program that brings value to your organisation.

      Picture of analyst

      Data governance does not sit as an island on its own in the organisation – it must align with and be driven by your enterprise governance. As you build out data governance in your organisation, it's important to keep in mind that this program is meant to be an enabling framework of oversight and accountabilities for managing, handling, and protecting your company's data assets. It should never be perceived as bureaucratic or inhibiting to your data users. It should deliver agreed-upon models that are conducive to your organisation's operating culture, offering clarity on who can do what with the data and via what means. Data governance is the key enabler for bringing high-quality, trusted, secure, and discoverable data to the right users across your organisation. Promote and drive the responsible and ethical use of data while helping to build and foster an organisational culture of data excellence.

      Crystal Singh

      Director, Research & Advisory, Data & Analytics Practice

      Info-Tech Research Group

      Executive Summary

      Your Challenge

      The amount of data within organisations is growing at an exponential rate, creating a need to adopt a formal approach to governing data. However, many organisations remain uninformed on how to effectively govern their data. Comprehensive data governance should define leadership, accountability, and responsibility related to data use and handling and be supported by a well-oiled operating model and relevant policies and procedures. This will help ensure the right data gets to the right people at the right time, using the right mechanisms.

      Common Obstacles

      Organisations are faced with challenges associated with changing data landscapes, evolving business models, industry disruptions, regulatory and compliance obligations, and changing and maturing user landscape and demand for data. Although the need for a data governance program is often evident, organisations miss the mark when their data governance efforts are not directly aligned to delivering measurable business value. Initiatives should support key strategic initiatives, as well as value streams and their underlying business capabilities.

      Info-Tech's Approach

      Info-Tech's approach to establishing and sustaining effective data governance is anchored in the strong alignment of organisational value streams and their business capabilities with key data governance dimensions and initiatives. Organisations should:

      • Align their data governance with enterprise governance, business strategy and value streams to ensure the program delivers measurable business value.
      • Understand their current data governance capabilities so as to build out a future state that is right-sized and relevant.
      • Define data leadership, accountability, and responsibility. Support these with an operating model that effectively manages change and communication and fosters a culture of data excellence.

      Info-Tech Insight

      Your organisation's value streams and the associated business capabilities require effectively governed data. Without this, you face elevated operating costs, missed opportunities, eroded stakeholder satisfaction, and increased business risk.

      Your challenge

      This research is designed to help organisations build and sustain an effective data governance program.

      • Your organisation has recognised the need to treat data as a corporate asset for generating business value and/or managing and mitigating risk.
      • This has brought data governance to the forefront and highlighted the need to build a performance-driven enterprise program for delivering quality, trusted, and readily consumable data to users.
      • An effective data governance program is one that defines leadership, accountability. and responsibility related to data use and handling. It's supported by a well-oiled operating model and relevant policies and procedures, all of which help build and foster a culture of data excellence where the right users get access to the right data at the right time via the right mechanisms.

      As you embark on establishing data governance in your organisation, it's vital to ensure from the get-go that you define the drivers and business context for the program. Data governance should never be attempted without direction on how the program will yield measurable business value.

      'Data processing and cleanup can consume more than half of an analytics team's time, including that of highly paid data scientists, which limits scalability and frustrates employees.' – Petzold, et al., 2020

      Image is a circle graph and 30% of it is coloured with the number 30% in the middle of the graph

      'The productivity of employees across the organisation can suffer.' – Petzold, et al., 2020

      Respondents to McKinsey's 2019 Global Data Transformation Survey reported that an average of 30% of their total enterprise time was spent on non-value-added tasks because of poor data quality and availability. – Petzold, et al., 2020

      Common obstacles

      Some of the barriers that make data governance difficult to address for many organisations include:

      • Gaps in communicating the strategic value of data and data governance to the organisation. This is vital for securing senior leadership buy-in and support, which, in turn, is crucial for sustained success of the data governance program.
      • Misinterpretation or a lack of understanding about data governance, including what it means for the organisation and the individual data user.
      • A perception that data governance is inhibiting or an added layer of bureaucracy or complication rather than an enabling and empowering framework for stakeholders in their use and handling of data.
      • Embarking on data governance without firmly substantiating and understanding the organisational drivers for doing so. How is data governance going to support the organisation's value streams and their various business capabilities?
      • Neglecting to define and measure success and performance. Just as in any other enterprise initiative, you have to be able to demonstrate an ROI for time, resources and funding. These metrics must demonstrate the measurable business value that data governance brings to the organisation.
      • Failure to align data governance with enterprise governance.
      Image is a circle graph and 78% of it is coloured with the number 78% in the middle of the graph

      78% of companies (and 92% of top-tier companies) have a corporate initiative to become more data-driven. – Alation, 2020.

      Image is a circle graph and 58% of it is coloured with the number 58% in the middle of the graph

      But despite these ambitions, there appears to be a 'data culture disconnect' – 58% of leaders overestimate the current data culture of their enterprises, giving a grade higher than the one produced by the study. – Fregoni, 2020.

      The strategic value of data

      Power intelligent and transformative organisational performance through leveraging data.

      Respond to industry disruptors

      Optimise the way you serve your stakeholders and customers

      Develop products and services to meet ever-evolving needs

      Manage operations and mitigate risk

      Harness the value of your data

      The journey to being data-driven

      The journey to declaring that you are a data-driven organisation requires a pit stop at data enablement.

      The Data Economy

      Data Disengaged

      You have a low appetite for data and rarely use data for decision making.

      Data Enabled

      Technology, data architecture, and people and processes are optimised and supported by data governance.

      Data Driven

      You are differentiating and competing on data and analytics; described as a 'data first' organisation. You're collaborating through data. Data is an asset.

      Data governance is essential for any organisation that makes decisions about how it uses its data.

      Data governance is an enabling framework of decision rights, responsibilities, and accountabilities for data assets across the enterprise.

      Data governance is:

      • Executed according to agreed-upon models that describe who can take what actions with what information, when, and using what methods (Olavsrud, 2021).
      • True business-IT collaboration that will lead to increased consistency and confidence in data to support decision making. This, in turn, helps fuel innovation and growth.

      If done correctly, data governance is not:

      • An annoying, finger-waving roadblock in the way of getting things done.
      • Meant to solve all data-related business or IT problems in an organisation.
      • An inhibitor or impediment to using and sharing data.

      Info-Tech's Data Governance Framework

      An image of Info-Tech's Data Governance Framework

      Create impactful data governance by embedding it within enterprise governance

      A model is depicted to show the relationship between enterprise governance and data governance.

      Organisational drivers for data governance

      Data governance personas:

      Conformance: Establishing data governance to meet regulations and compliance requirements.

      Performance: Establishing data governance to fuel data-driven decision making for driving business value and managing and mitigating business risk.

      Two images are depicted that show the difference between conformance and performance.

      Data Governance is not a one-person show

      • Data governance needs a leader and a home. Define who is going to be leading, driving, and steering data governance in your organisation.
      • Senior executive leaders play a crucial role in championing and bringing visibility to the value of data and data governance. This is vital for building and fostering a culture of data excellence.
      • Effective data governance comes with business and IT alignment, collaboration, and formally defined roles around data leadership, ownership, and stewardship.
      Four circles are depicted. There is one person in the circle on the left and is labelled: Data Governance Leadership. The circle beside it has two people in it and labelled: Organisational Champions. The circle beside it has three people in it and labelled: Data Owners, Stewards & Custodians. The last circle has four people in it and labelled: The Organisation & Data Storytellers.

      Traditional data governance organisational structure

      A traditional structure includes committees and roles that span across strategic, tactical, and operational duties. There is no one-size-fits-all data governance structure. However, most organisations follow a similar pattern when establishing committees, councils, and cross-functional groups. Most organisations strive to identify roles and responsibilities at a strategic and operational level. Several factors will influence the structure of the program, such as the focus of the data governance project and the maturity and size of the organisation.

      A triangular model is depicted and is split into three tiers to show the traditional data governance organisational structure.

      A healthy data culture is key to amplifying the power of your data.

      'Albert Einstein is said to have remarked, "The world cannot be changed without changing our thinking." What is clear is that the greatest barrier to data success today is business culture, not lagging technology.' – Randy Bean, 2020

      What does it look like?

      • Everybody knows the data.
      • Everybody trusts the data.
      • Everybody talks about the data.

      'It is not enough for companies to embrace modern data architectures, agile methodologies, and integrated business-data teams, or to establish centres of excellence to accelerate data initiatives, when only about 1 in 4 executives reported that their organisation has successfully forged a data culture.'– Randy Bean, 2020

      Data literacy is an essential part of a data-driven culture

      • In a data-driven culture, decisions are made based on data evidence, not on gut instinct.
      • Data often has untapped potential. A data-driven culture builds tools and skills, builds users' trust in the condition and sources of data, and raises the data skills and understanding among their people on the front lines.
      • Building a data culture takes an ongoing investment of time, effort, and money. This investment will not achieve the transformation you want without data literacy at the grassroots level.

      Data-driven culture = 'data matters to our company'

      Despite investments in data initiative, organisations are carrying high levels of data debt

      Data debt is 'the accumulated cost that is associated with the sub-optimal governance of data assets in an enterprise, like technical debt.'

      Data debt is a problem for 78% of organisations.

      40% of organisations say individuals within the business do not trust data insights.

      66% of organisations say a backlog of data debt is impacting new data management initiatives.

      33% of organisations are not able to get value from a new system or technology investment.

      30% of organisations are unable to become data-driven.

      Source: Experian, 2020

      Absent or sub-optimal data governance leads to data debt

      Only 3% of companies' data meets basic quality standards. (Source: Nagle, et al., 2017)

      Organisations suspect 28% of their customer and prospect data is inaccurate in some way. (Source: Experian, 2020)

      Only 51% of organisations consider the current state of their CRM or ERP data to be clean, allowing them to fully leverage it. (Source: Experian, 2020)

      35% of organisations say they're not able to see a ROI for data management initiatives. (Source: Experian, 2020)

      Embrace the technology

      Make the available data governance tools and technology work for you:

      • Data catalogue
      • Business data glossary
      • Data lineage
      • Metadata management

      While data governance tools and technologies are no panacea, leverage their automated and AI-enabled capabilities to augment your data governance program.

      Logos of data governance tools and technology.

      Measure success to demonstrate tangible business value

      Put data governance into the context of the business:

      • Tie the value of data governance and its initiatives back to the business capabilities that are enabled.
      • Leverage the KPIs of those business capabilities to demonstrate tangible and measurable value. Use terms and language that will resonate with senior leadership.

      Don't let measurement be an afterthought:

      Start substantiating early on how you are going to measure success as your data governance program evolves.

      Build a right-sized roadmap

      Formulate an actionable roadmap that is right-sized to deliver value in your organisation.

      Key considerations:

      • When building your data governance roadmap, ensure you do so through an enterprise lens. Be cognizant of other initiatives that might be coming down the pipeline that may require you to align your data governance milestones accordingly.
      • Apart from doing your planning with consideration for other big projects or launches that might be in-flight and require the time and attention of your data governance partners, also be mindful of the more routine yet still demanding initiatives.
      • When doing your roadmapping, consider factors like the organisation's fiscal cycle, typical or potential year-end demands, and monthly/quarterly reporting periods and audits. Initiatives such as these are likely to monopolise the time and focus of personnel key to delivering on your data governance milestones.

      Sample milestones:

      Data Governance Leadership & Org Structure Definition

      Define the home for data governance and other key roles around ownership and stewardship, as approved by senior leadership.

      Data Governance Charter and Policies

      Create a charter for your program and build/refresh associated policies.

      Data Culture Diagnostic

      Understand the organisation's current data culture, perception of data, value of data, and knowledge gaps.

      Use Case Build and Prioritisation

      Build a use case that is tied to business capabilities. Prioritise accordingly.

      Business Data Glossary

      Build and/or refresh the business' glossary for addressing data definitions and standardisation issues.

      Tools & Technology

      Explore the tools and technology offering in the data governance space that would serve as an enabler to the program. (e.g. RFI, RFP).

      Key takeaways for effective business-driven data governance

      Data governance leadership and sponsorship is key.

      Ensure strategic business alignment.

      Build and foster a culture of data excellence.

      Evolve along the data journey.

      Make data governance an enabler, not a hindrance.

      Insight summary

      Overarching insight

      Your organisation's value streams and the associated business capabilities require effectively governed data. Without this, you face the impact of elevated operational costs, missed opportunities, eroded stakeholder satisfaction, and exposure to increased business risk.

      Insight 1

      Data governance should not sit as an island in your organisation. It must continuously align with the organisation's enterprise governance function. It shouldn't be perceived as a pet project of IT, but rather as an enterprise-wide, business-driven initiative.

      Insight 2

      Ensure your data governance program delivers measurable business value by aligning the associated data governance initiatives with the business architecture. Leverage the measures of success or KPIs of the underlying business capabilities to demonstrate the value data governance has yielded for the organisation.

      Insight 3

      Data governance remains the foundation of all forms of reporting and analytics. Advanced capabilities such as AI and machine learning require effectively governed data to fuel their success.

      Tactical insight

      Tailor your data literacy program to meet your organisation's needs, filling your range of knowledge gaps and catering to your different levels of stakeholders. When it comes to rolling out a data literacy program, there is no one-size-fits-all solution. Your data literacy program is intended to fill the knowledge gaps about data, as they exist in your organisation. It should be targeted across the board – from your executive leadership and management through to the subject matter experts across different lines of the business in your organisation.

      Info-Tech's methodology for establishing data governance

      1. Build Business and User Context 2. Understand Your Current Data Governance Capabilities 3. Build a Target State Roadmap and Plan
      Phase Steps
      1. Substantiate Business Drivers
      2. Build High-Value Use Cases for Data Governance
      1. Understand the Key Components of Data Governance
      2. Gauge Your Organisation's Current Data Culture
      1. Formulate an Actionable Roadmap and Right-Sized Plan
      Phase Outcomes
      • Your organisation's business capabilities and value streams
      • A business capability map for your organisation
      • Categorisation of your organisation's key capabilities
      • A strategy map tied to data governance
      • High-value use cases for data governance
      • An understanding of the core components of an effective data governance program
      • An understanding your organisation's current data culture
      • A data governance roadmap and target-state plan comprising of prioritised initiatives

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

      Screenshot of Info-Tech's Data Governance Planning and Roadmapping Workbook data-verified=

      Data Governance Planning and Roadmapping Workbook

      Use the Data Governance Planning and Roadmapping Workbook as you plan, build, roll out, and scale data governance in your organisation.

      Screenshot of Info-Tech's Data Use Case Framework Template

      Data Use Case Framework Template

      This template takes you through a business needs gathering activity to highlight and create relevant use cases around the organisation's data-related problems and opportunities.

      Screenshot of Info-Tech's Business Data Glossary data-verified=

      Business Data Glossary

      Use this template to document the key data assets that are to be governed and create a data flow diagram for your organisation.

      Screenshot of Info-Tech's Data Culture Diagnostic and Scorecard data-verified=

      Data Culture Diagnostic and Scorecard

      Leverage Info-Tech's Data Culture Diagnostic to understand how your organisation scores across 10 areas relating to data culture.

      Key deliverable:

      Data Governance Planning and Roadmapping Workbook

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

      Data Governance Initiative Planning and Roadmap Tool

      Leverage this tool to assess your current data governance capabilities and plot your target state accordingly.

      This tool will help you plan the sequence of activities, capture start dates and expected completion dates, and create a roadmap that can be effectively communicated to the organisation.

      Data Governance Program Charter Template

      This template will help get the backing required to get a data governance project rolling. The program charter will help communicate the project purpose, define the scope, and identify the project team, roles, and responsibilities.

      Data Governance Policy

      This policy establishes uniformed data governance standards and identifies the shared responsibilities for assuring the integrity of the data and that it efficiently and effectively serves the needs of your organisation

      Other Deliverables:

      • Data Governance Initiative Planning and Roadmap Tool
      • Data Governance Program Charter Template
      • Data Governance Policy

      Blueprint benefits

      Defined data accountability & responsibility

      Shared knowledge & common understanding of data assets

      Elevated trust & confidence in traceable data

      Improved data ROI & reduced data debt

      Support for ethical use and handling of data in a culture of excellence

      Measure the value of this blueprint

      Leverage this blueprint's approach to ensure your data governance initiatives align and support your key value streams and their business capabilities.

      • Aligning your data governance program and its initiatives to your organisation's business capabilities is vital for tracing and demonstrating measurable business value for the program.
      • This alignment of data governance with value streams and business capabilities enables you to use business-defined KPIs and demonstrate tangible value.
      Screenshot from this blueprint on the Measurable Business Value

      In phases 1 and 2 of this blueprint, we will help you establish the business context, define your business drivers and KPIs, and understand your current data governance capabilities and strengths.

      In phase 3, we will help you develop a plan and a roadmap for addressing any gaps and improving the relevant data governance capabilities so that data is well positioned to deliver on those defined business metrics.

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      'Our team, has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.'

      Guided Implementation

      'Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keeps us on track.'

      Workshop

      'We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.'

      Consulting

      'Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.'

      Diagnostics and consistent frameworks are used throughout all four options.

      Establish Data Governance project overview

      Contact your account representative for more information. workshops@infotech.com 1-888-670-8889

      1. Build Business and User context2. Understand Your Current Data Governance Capabilities3. Build a Target State Roadmap and Plan
      Best-Practice Toolkit
      1. Substantiate Business Drivers
      2. Build High-Value Use Cases for Data Governance
      1. Understand the Key Components of Data Governance
      2. Gauge Your Organisation's Current Data Culture
      1. Formulate an Actionable Roadmap and Right-Sized Plan
      Guided Implementation
      • Call 1
      • Call 2
      • Call 3
      • Call 4
      • Call 5
      • Call 6
      • Call 7
      • Call 8
      • Call 9
      Phase Outcomes
      • Your organisation's business capabilities and value streams
      • A business capability map for your organisation
      • Categorisation of your organisation's key capabilities
      • A strategy map tied to data governance
      • High-value use cases for data governance
      • An understanding of the core components of an effective data governance program
      • An understanding your organisation's current data culture
      • A data governance roadmap and target-state plan comprising of prioritised initiatives

      Guided Implementation

      What does a typical GI on this topic look like?

      An outline of what guided implementation looks like.

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organisation. A typical GI is between 8 to 12 calls over the course of 4 to 6 months.

      Workshop overview

      Contact your account representative for more information. workshops@infotech.com 1-888-670-8889

      Day 1 Day 2 Day 3 Day 4
      Establish Business Context and Value Understand Current Data Governance Capabilities and Plot Target-State Levels Build Data Domain to Data Governance Role Mapping Formulate a Plan to Get to Your Target State
      Activities
      • Establish business context, value, and scope of data governance at the organisation
      • Introduction to Info-Tech's data governance framework
      • Discuss vision and mission for data governance
      • Understand your business architecture, including your business capability map and value streams
      • Build use cases aligned to core business capabilities
      • Understand your current data governance capabilities and maturity
      • Set target state data governance capabilities
      • Evaluate and prioritise performance gaps
      • Develop and consolidate data governance target-state initiatives
      • Define the role of data governance: data domain to data governance role mapping
      • Identify and prioritise next steps
      • Define roles and responsibilities and complete a high-level RACI
      • Wrap-up and discuss next steps and post-workshop support
      Deliverables
      1. Sample use cases (tied to the business capability map) and a repeatable use case framework
      2. Vision and mission for data governance
      1. Current state of data governance maturity
      2. Definition of target state
      1. Target-state data governance initiatives
      2. Data domain to data governance role mapping
      1. Initialised roadmap
      2. Initialised RACI
      3. Completed Business Data Glossary (BDG)

      Phase 1

      Build Business and User Context

      Three circles are in the image that list the three phases and the main steps. Phase 1 is highlighted.

      'When business users are invited to participate in the conversation around data with data users and IT, it adds a fundamental dimension — business context. Without a real understanding of how data ties back to the business, the value of analysis and insights can get lost.' – Jason Lim, Alation

      This phase will guide you through the following activities:

      • Identify Your Business Capabilities
      • Define your Organisation's Key Business Capabilities
      • Develop a Strategy Map that Aligns Business Capabilities to Your Strategic Focus

      This phase involves the following participants:

      • Data Governance Leader/Data Leader (CDO)
      • Senior Business Leaders
      • Business SMEs
      • Data Leadership, Data Owners, Data Stewards and Custodians

      Step 1.1

      Substantiate Business Drivers

      Activities

      1.1.1 Identify Your Business Capabilities

      1.1.2 Categorise Your Organisation's Key Business Capabilities

      1.1.3 Develop a Strategy Map Tied to Data Governance

      This step will guide you through the following activities:

      • Leverage your organisation's existing business capability map or initiate the formulation of a business capability map, guided by Info-Tech's approach
      • Determine which business capabilities are considered high priority by your organisation
      • Map your organisation's strategic objectives to value streams and capabilities to communicate how objectives are realised with the support of data

      Outcomes of this step

      • A foundation for data governance initiative planning that's aligned with the organisation's business architecture: value streams, business capability map, and strategy map

      Info-Tech Insight

      Gaining a sound understanding of your business architecture (value streams and business capabilities) is a critical foundation for establishing and sustaining a data governance program that delivers measurable business value.

      1.1.1 Identify Your Business Capabilities

      Confirm your organisation's existing business capability map or initiate the formulation of a business capability map:

      1. If you have an existing business capability map, meet with the relevant business owners/stakeholders to confirm that the content is accurate and up to date. Confirm the value streams (how your organisation creates and captures value) and their business capabilities are reflective of the organisation's current business environment.
      2. If you do not have an existing business capability map, follow this activity to initiate the formulation of a map (value streams and related business capabilities):
        1. Define the organisation's value streams. Meet with senior leadership and other key business stakeholders to define how your organisation creates and captures value.
        2. Define the relevant business capabilities. Meet with senior leadership and other key business stakeholders to define the business capabilities.

      Note: A business capability defines what a business does to enable value creation. Business capabilities are business terms defined using descriptive nouns such as 'Marketing' or 'Research and Development.' They represent stable business functions, are unique and independent of each other, and typically will have a defined business outcome.

      Input

      • List of confirmed value streams and their related business capabilities

      Output

      • Business capability map with value streams for your organisation

      Materials

      • Your existing business capability map or the template provided in the Data Governance Planning and Roadmapping Workbook accompanying this blueprint

      Participants

      • Key business stakeholders
      • Data stewards
      • Data custodians
      • Data Governance Working Group

      For more information, refer to Info-Tech's Document Your Business Architecture.

      Define or validate the organisation's value streams

      Value streams connect business goals to the organisation's value realisation activities. These value realisation activities, in turn, depend on data.

      If the organisation does not have a business architecture function to conduct and guide Activity 1.1.1, you can leverage the following approach:

      • Meet with key stakeholders regarding this topic, then discuss and document your findings.
      • When trying to identify the right stakeholders, consider: Who are the decision makers and key influencers? Who will impact this piece of business architecture related work? Who has the relevant skills, competencies, experience, and knowledge about the organisation?
      • Engage with these stakeholders to define and validate how the organisation creates value.
      • Consider:
        • Who are your main stakeholders? This will depend on the industry in which you operate. For example, customers, residents, citizens, constituents, students, patients.
        • What are your stakeholders looking to accomplish?
        • How does your organisation's products and/or services help them accomplish that?
        • What are the benefits your organisation delivers to them and how does your organisation deliver those benefits?
        • How do your stakeholders receive those benefits?

      Align data governance to the organisation's value realisation activities.

      Value streams enable the organisation to create or capture value in the market in which it operates by engaging in a set of interconnected activities.

      Info-Tech Insight

      Your organisation's value streams and the associated business capabilities require effectively governed data. Without this, you face the possibilities of elevated operational costs, missed opportunities, eroded stakeholder satisfaction, negative impact to reputation and brand, and/or increased exposure to business risk.

      Example of value streams – Retail Banking

      Value streams connect business goals to the organisation's value realisation activities.

      Example value stream descriptions for: Retail Banking

      Value streams enable the organisation to create or capture value in the market in which it operates by engaging in a set of interconnected activities.

      Model example of value streams for retail banking.

      For this value stream, download Info-Tech's Info-Tech's Industry Reference Architecture for Retail Banking.

      Example of value streams – Higher Education

      Value streams connect business goals to the organisation's value realisation activities.

      Example value stream descriptions for: Higher Education

      Value streams enable the organisation to create or capture value in the market in which it operates by engaging in a set of interconnected activities.

      Model example of value streams for higher education

      For this value stream, download Info-Tech's Industry Reference Architecture for Higher Education.

      Example of value streams – Local Government

      Value streams connect business goals to the organisation's value realisation activities.

      Example value stream descriptions for: Local Government

      Value streams enable the organisation to create or capture value in the market in which it operates by engaging in a set of interconnected activities.

      Model example of value streams for local government

      For this value stream, download Info-Tech's Industry Reference Architecture for Local Government.

      Example of value streams – Manufacturing

      Value streams connect business goals to the organisation's value realisation activities.

      Example value stream descriptions for: Manufacturing

      Value streams enable the organisation to create or capture value in the market in which it operates by engaging in a set of interconnected activities.

      Model example of value streams for manufacturing

      For this value stream, download Info-Tech's Industry Reference Architecture for Manufacturing.

      Example of value streams – Retail

      Value streams connect business goals to the organisation's value realisation activities.

      Example value stream descriptions for: Retail

      Model example of value streams for retail

      Value streams enable the organisation to create or capture value in the market in which it operates by engaging in a set of interconnected activities.

      For this value stream, download Info-Tech's Industry Reference Architecture for Retail.

      Define the organisation's business capabilities in a business capability map

      A business capability defines what a business does to enable value creation. Business capabilities represent stable business functions and typically will have a defined business outcome.

      Business capabilities can be thought of as business terms defined using descriptive nouns such as 'Marketing' or 'Research and Development.'

      If your organisation doesn't already have a business capability map, you can leverage the following approach to build one. This initiative requires a good understanding of the business. By working with the right stakeholders, you can develop a business capability map that speaks a common language and accurately depicts your business.

      Working with the stakeholders as described above:

      • Analyse the value streams to identify and describe the organisation's capabilities that support them.
      • Consider: What is the objective of your value stream? (This can highlight which capabilities support which value stream.)
      • As you initiate your engagement with your stakeholders, don't start a blank page. Leverage the examples on the next slides as a starting point for your business capability map.
      • When using these examples, consider: What are the activities that make up your particular business? Keep the ones that apply to your organisation, remove the ones that don't, and add any needed.

      Align data governance to the organisation's value realisation activities.

      Info-Tech Insight

      A business capability map can be thought of as a visual representation of your organisation's business capabilities and hence represents a view of what your data governance program must support.

      For more information, refer to Info-Tech's Document Your Business Architecture.

      Example business capability map – Retail Banking

      A business capability map can be thought of as a visual representation of your organisation's business capabilities and hence represents a view of what your data governance program must support.

      Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

      Info-Tech Tip:

      Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realisation capabilities under discussion. This will help to build awareness and visibility of the data governance program.

      Example business capability map for: Retail Banking

      Model example business capability map for retail banking

      For this business capability map, download Info-Tech's Industry Reference Architecture for Retail Banking.

      Example business capability map – Higher Education

      A business capability map can be thought of as a visual representation of your organisation's business capabilities and hence represents a view of what your data governance program must support.

      Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

      Info-Tech Tip:

      Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realisation capabilities under discussion. This will help to build awareness and visibility of the data governance program.

      Example business capability map for: Higher Education

      Model example business capability map for higher education

      For this business capability map, download Info-Tech's Industry Reference Architecture for Higher Education.

      Example business capability map – Local Government

      A business capability map can be thought of as a visual representation of your organisation's business capabilities and hence represents a view of what your data governance program must support.

      Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

      Info-Tech Tip:

      Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realisation capabilities under discussion. This will help to build awareness and visibility of the data governance program.

      Example business capability map for: Local Government

      Model example business capability map for local government

      For this business capability map, download Info-Tech's Industry Reference Architecture for Local Government.

      Example business capability map – Manufacturing

      A business capability map can be thought of as a visual representation of your organisation's business capabilities and hence represents a view of what your data governance program must support.

      Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

      Info-Tech Tip:

      Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realisation capabilities under discussion. This will help to build awareness and visibility of the data governance program.

      Example business capability map for: Manufacturing

      Model example business capability map for manufacturing

      For this business capability map, download Info-Tech's Industry Reference Architecture for Manufacturing.

      Example business capability map - Retail

      A business capability map can be thought of as a visual representation of your organisation's business capabilities and hence represents a view of what your data governance program must support.

      Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders.

      Info-Tech Tip:

      Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realisation capabilities under discussion. This will help to build awareness and visibility of the data governance program.

      Example business capability map for: Retail

      Model example business capability map for retail

      For this business capability map, download Info-Tech's Industry Reference Architecture for Retail.

      1.1.2 Categorise Your Organisation's Key Capabilities

      Determine which capabilities are considered high priority in your organisation.

      1. Categorise or heatmap the organisation's key capabilities. Consult with senior and other key business stakeholders to categorise and prioritise the business' capabilities. This will aid in ensuring your data governance future state planning is aligned with the mandate of the business. One approach to prioritising capabilities with business stakeholders is to examine them through the lens of cost advantage creators, competitive advantage differentiators, and/or by high value/high risk.
      2. Identify cost advantage creators. Focus on capabilities that drive a cost advantage for your organisation. Highlight these capabilities and prioritise programs that support them.
      3. Identify competitive advantage differentiators. Focus on capabilities that give your organisation an edge over rivals or other players in your industry.

      This categorisation/prioritisation exercise helps highlight prime areas of opportunity for building use cases, determining prioritisation, and the overall optimisation of data and data governance.

      Input

      • Strategic insight from senior business stakeholders on the business capabilities that drive value for the organisation

      Output

      • Business capabilities categorised and prioritised (e.g. cost advantage creators, competitive advantage differentiators, high value/high risk)

      Materials

      • Your existing business capability map or the business capability map derived in the previous activity

      Participants

      • Key business stakeholders
      • Data stewards
      • Data custodians
      • Data Governance Working Group

      For more information, refer to Info-Tech's Document Your Business Architecture.

      Example of business capabilities categorisation or heatmapping – Retail

      This exercise is useful in ensuring the data governance program is focused and aligned to support the priorities and direction of the business.

      • Depending on the mandate from the business, priority may be on developing cost advantage. Hence the capabilities that deliver efficiency gains are the ones considered to be cost advantage creators.
      • The business' priority may be on maintaining or gaining a competitive advantage over its industry counterparts. Differentiation might be achieved in delivering unique or enhanced products, services, and/or experiences, and the focus will tend to be on the capabilities that are more end-stakeholder-facing (e.g. customer-, student-, patient,- and/or constituent-facing). These are the organisation's competitive advantage creators.

      Example: Retail

      Example of business capabilities categorisation or heatmapping – Retail

      For this business capability map, download Info-Tech's Industry Reference Architecture for Retail.

      1.1.3 Develop a Strategy Map Tied to Data Governance

      Identify the strategic objectives for the business. Knowing the key strategic objectives will drive business-data governance alignment. It's important to make sure the right strategic objectives of the organisation have been identified and are well understood.

      1. Meet with senior business leaders and other relevant stakeholders to help identify and document the key strategic objectives for the business.
      2. Leverage their knowledge of the organisation's business strategy and strategic priorities to visually represent how these map to value streams, business capabilities, and, ultimately, to data and data governance needs and initiatives. Tip: Your map is one way to visually communicate and link the business strategy to other levels of the organisation.
      3. Confirm the strategy mapping with other relevant stakeholders.

      Guide to creating your map: Starting with strategic objectives, map the value streams that will ultimately drive them. Next, link the key capabilities that enable each value stream. Then map the data and data governance to initiatives that support those capabilities. This is one approach to help you prioritise the data initiatives that deliver the most value to the organisation.

      Input

      • Strategic objectives as outlined by the organisation's business strategy and confirmed by senior leaders

      Output

      • A strategy map that maps your organisational strategic objectives to value streams, business capabilities, and, ultimately, to data program

      Materials

      Participants

      • Key business stakeholders
      • Data stewards
      • Data custodians
      • Data Governance Working Group

      Download Info-Tech's Data Governance Planning and Roadmapping Workbook

      Example of a strategy map tied to data governance

      • Strategic objectives are the outcomes that the organisation is looking to achieve.
      • Value streams enable an organisation to create and capture value in the market through interconnected activities that support strategic objectives.
      • Business capabilities define what a business does to enable value creation in value streams.
      • Data capabilities and initiatives are descriptions of action items on the data and data governance roadmap and which will enable one or multiple business capabilities in its desired target state.

      Info-Tech Tip:

      Start with the strategic objectives, then map the value streams that will ultimately drive them. Next, link the key capabilities that enable each value stream. Then map the data and data governance initiatives that support those capabilities. This process will help you prioritise the data initiatives that deliver the most value to the organisation.

      Example: Retail

      Example of a strategy map tied to data governance for retail

      For this strategy map, download Info-Tech's Industry Reference Architecture for Retail.

      Step 1.2

      Build High-Value Use Cases for Data Governance

      Activities

      1.2.1 Build High-Value Use Cases

      This step will guide you through the following activities:

      • Leveraging your categorised business capability map to conduct deep-dive sessions with key business stakeholders for creating high-value uses cases
      • Discussing current challenges, risks, and opportunities associated with the use of data across the lines of business
      • Exploring which other business capabilities, stakeholder groups, and business units will be impacted

      Outcomes of this step

      • Relevant use cases that articulate the data-related challenges, needs, or opportunities that are clear and contained and, if addressed ,will deliver value to the organisation

      Info-Tech Tip

      One of the most important aspects when building use cases is to ensure you include KPIs or measures of success. You have to be able to demonstrate how the use case ties back to the organisational priorities or delivers measurable business value. Leverage the KPIs and success factors of the business capabilities tied to each particular use case.

      1.2.1 Build High-Value Use Cases

      This business needs-gathering activity will highlight and create relevant use cases around data-related problems or opportunities that are clear and contained and, if addressed, will deliver value to the organisation.

      1. Bring together key business stakeholders (data owner, stewards, SMEs) from a particular line of business as well as the relevant data custodian(s) to build cases for their units. Leverage the business capability map you created for facilitating this act.
      2. Leverage Info-Tech's framework for data requirements and methodology for creating use cases, as outlined in the Data Use Case Framework Template and seen on the next slide.
      3. Have the stakeholders move through each breakout session outlined in the Use Case Worksheet. Use flip charts or a whiteboard to brainstorm and document their thoughts.
      4. Debrief and document results in the Data Use Case Framework Template.
      5. Repeat this exercise with as many lines of the business as possible, leveraging your business capability map to guide your progress and align with business value.

      Tip: Don't conclude these use case discussions without substantiating what measures of success will be used to demonstrate the business value of the effort to produce the desired future state, as relevant to each particular use case.

      This business needs-gathering activity will highlight and create relevant use cases around data-related problems or opportunities that are clear and contained and, if addressed, will deliver value to the organisation.

      1. Bring together key business stakeholders (data owner, stewards, SMEs) from a particular line of business as well the relevant data custodian(s) to build cases for their units. Leverage the business capability map you created for facilitating this act.
      2. Leverage Info-Tech's framework for data requirements and methodology for creating use cases, as outlined in the Data Use Case Framework Template and seen on the next slide.
      3. Have the stakeholders move through each breakout session outlined in the Use Case Worksheet. Use flip charts or a whiteboard to brainstorm and document their thoughts.
      4. Debrief and document results in the Data Use Case Framework Template
      5. Repeat this exercise with as many lines of the business as possible, leveraging your business capability map to guide your progress and align with business value.

      Tip: Don't conclude these use case discussions without substantiating what measures of success will be used to demonstrate the business value of the effort to produce the desired future state, as relevant to each particular use case.

      Input

      • Value streams and business capabilities as defined by business leaders
      • Business stakeholders' subject area expertise
      • Data custodian systems, integration, and data knowledge

      Output

      • Use cases that articulate data-related challenges, needs or opportunities that are tied to defined business capabilities and hence if addressed will deliver measurable value to the organisation.

      Materials

      • Your business capability map from activity 1.1.1
      • Info-Tech's Data Use Case Framework Template
      • Whiteboard or flip charts (or shared screen if working remotely)
      • Markers/pens

      Participants

      • Key business stakeholders
      • Data stewards and business SMEs
      • Data custodians
      • Data Governance Working Group

      Download Info-Tech's Data Use Case Framework Template

      Info-Tech's Framework for Building Use Cases

      Objective: This business needs-gathering activity will highlight and create relevant use cases around data-related problems or opportunities that are clear and contained and, if addressed, will deliver value to the organisation.

      Leveraging your business capability map, build use cases that align with the organisation's key business capabilities.

      Consider:

      • Is the business capability a cost advantage creator or an industry differentiator?
      • Is the business capability currently underserved by data?
      • Does this need to be addressed? If so, is this risk- or value-driven?

      Info-Tech's Data Requirements and Mapping Methodology for Creating Use Cases

      1. What business capability (or capabilities) is this use case tied to for your business area(s)?
      2. What are your data-related challenges in performing this today?
      3. What are the steps in this process/activity today?
      4. What are the applications/systems used at each step today?
      5. What data domains are involved, created, used, and/or transformed at each step today?
      6. What does an ideal or improved state look like?
      7. What other business units, business capabilities, activities, and/or processes will be impacted or improved if this issue was solved?
      8. Who are the stakeholders impacted by these changes? Who needs to be consulted?
      9. What are the risks to the organisation (business capability, revenue, reputation, customer loyalty, etc.) if this is not addressed?
      10. What compliance, regulatory, and/or policy concerns do we need to consider in any solution?
      11. What measures of success or change should we use to prove the value of the effort (such as KPIs, ROI)? What is the measurable business value of doing this?

      The resulting use cases are to be prioritised and leveraged for informing the business case and the data governance capabilities optimisation plan.

      Taken from Info-Tech's Data Use Case Framework Template

      Phase 2

      Understand Your Current Data Governance Capabilities

      Three circles are in the image that list the three phases and the main steps. Phase 2 is highlighted.

      This phase will guide you through the following activities:

      • Understand the Key Components of Data Governance
      • Gauge Your Organisation's Current Data Culture

      This phase involves the following participants:

      • Data Leadership
      • Data Ownership & Stewardship
      • Policies & Procedures
      • Data Literacy & Culture
      • Operating Model
      • Data Management
      • Data Privacy & Security
      • Enterprise Projects & Services

      Step 2.1

      Understand the Key Components of Data Governance

      This step will guide you through the following activities:

      • Understanding the core components of an effective data governance program and determining your organisation's current capabilities in these areas:
        • Data Leadership
        • Data Ownership & Stewardship
        • Policies & Procedures
        • Data Literacy & Culture
        • Operating Model
        • Data Management
        • Data Privacy & Security
        • Enterprise Projects & Services

      Outcomes of this step

      • An understanding of the core components of an effective data governance program
      • An understanding your organisation's current data governance capabilities

      Leverage Info-Tech's: Data Governance Initiative Planning and Roadmap Tool to assess your current data governance capabilities and plot your target state accordingly.

      This tool will help your organisation plan the sequence of activities, capture start dates and expected completion dates, and create a roadmap that can be effectively communicated to the organisation.

      Review: Info-Tech's Data Governance Framework

      An image of Info-Tech's Data Governance Framework

      Key components of data governance

      A well-defined data governance program will deliver:

      • Defined accountability and responsibility for data.
      • Improved knowledge and common understanding of the organisation's data assets.
      • Elevated trust and confidence in traceable data.
      • Improved data ROI and reduced data debt.
      • An enabling framework for supporting the ethical use and handling of data.
      • A foundation for building and fostering a data-driven and data-literate organisational culture.

      The key components of establishing sustainable enterprise data governance, taken from Info-Tech's Data Governance Framework:

      • Data Leadership
      • Data Ownership & Stewardship
      • Operating Model
      • Policies & Procedures
      • Data Literacy & Culture
      • Data Management
      • Data Privacy & Security
      • Enterprise Projects & Services

      Data Leadership

      • Data governance needs a dedicated head or leader to steer the organisation's data governance program.
      • For organisations that do have a chief data officer (CDO), their office is the ideal and effective home for data governance.
      • Heads of data governance also have titles such as director of data governance, director of data quality, and director of analytics.
      • The head of your data governance program works with all stakeholders and partners to ensure there is continuous enterprise governance alignment and oversight and to drive the program's direction.
      • While key stakeholders from the business and IT will play vital data governance roles, the head of data governance steers the various components, stakeholders, and initiatives, and provides oversight of the overall program.
      • Vital data governance roles include: data owners, data stewards, data custodians, data governance steering committee (or your organisation's equivalent), and any data governance working group(s).

      The role of the CDO: the voice of data

      The office of the chief data officer (CDO):

      • Has a cross-organisational vision and strategy for data.
      • Owns and drives the data strategy; ensures it supports the overall organisational strategic direction and business goals.
      • Leads the organisational data initiatives, including data governance
      • Is accountable for the policy, strategy, data standards, and data literacy necessary for the organisation to operate effectively.
      • Educates users and leaders about what it means to be 'data-driven.'
      • Builds and fosters a culture of data excellence.

      'Compared to most of their C-suite colleagues, the CDO is faced with a unique set of problems. The role is still being defined. The chief data officer is bringing a new dimension and focus to the organisation: "data." '
      – Carruthers and Jackson, 2020

      Who does the CDO report to?

      Example reporting structure.
      • The CDO should be a true C- level executive.
      • Where the organisation places the CDO role in the structure sends an important signal to the business about how much it values data.

      'The title matters. In my opinion, you can't have a CDO without executive authority. Otherwise no one will listen.'

      – Anonymous European CDO

      'The reporting structure depends on who's the 'glue' that ties together all these uniquely skilled individuals.'

      – John Kemp, Senior Director, Executive Services, Info-Tech Research Group

      Data Ownership & Stewardship

      Who are best suited to be data owners?

      • Wherever they may sit in your organisation, data owners will typically have the highest stake in that data.
      • Data owners needs to be suitably senior and have the necessary decision-making power.
      • They have the highest interest in the related business data domain, whether they are the head of a business unit or the head of a line of business that produces data or consumes data (or both).
      • If they are neither of these, it's unlikely they will have the interest in the data (in terms of its quality, protection, ethical use, and handling, for instance) necessary to undertake and adopt the role effectively.

      Data owners are typically senior business leaders with the following characteristics:

      • Positioned to accept accountability for their data domain.
      • Hold authority and influence to affect change, including across business processes and systems, needed to improve data quality, use, handling, integration, etc.
      • Have access to a budget and resources for data initiatives such as resolving data quality issues, data cleansing initiatives, business data catalogue build, related tools and technology, policy management, etc.
      • Hold the influence needed to drive change in behaviour and culture.
      • Act as ambassadors of data and its value as an organisational strategic asset.

      Right-size your data governance organisational structure

      • Most organisations strive to identify roles and responsibilities at a strategic, and operational level. Several factors will influence the structure of the program such as the focus of the data governance project as well as the maturity and size of the organisation.
      • Your data governance structure has to work for your organisation, and it has to evolve as the organisation evolves.
      • Formulate your blend of data governance roles, committees, councils, and cross-functional groups, that make sense for your organisation.
      • Your data governance organisational structure should not add complexity or bureaucracy to your organisation's data landscape; it should support and enable your principle of treating data as an asset.

      There is no one-size-fits-all data governance organisational structure.

      Example of a Data Governance Organisational Structure

      Critical roles and responsibilities for data governance

      Data Governance Working Groups

      Data governance working groups:

      • Are cross-functional teams
      • Deliver on data governance projects, initiatives, and ad hoc review committees.

      Data Stewards

      Traditionally, data stewards:

      • Serve on an operational level addressing issues related to adherence to standards/procedures, monitoring data quality, raising issues identified, etc.
      • Are responsible for managing access, quality, escalating issues, etc.

      Data Custodians

      • Traditionally, data custodians:
      • Serve on an operational level addressing issues related to data and database administration.
      • Support the management of access, data quality, escalating issues, etc.
      • Are SMEs from IT and database administration.

      Example: Business capabilities to data owner and data stewards mapping for a selected data domain

      Info-Tech Insight

      Your organisation's value streams and the associated business capabilities require effectively governed data. Without this, you face elevated operational costs, missed opportunities, eroded stakeholder satisfaction, and exposure to increased business risk.

      Enabling business capabilities with data governance role definitions

      Example: Business capabilities to data owner and data stewards mapping for a selected data domain

      Operating Model

      Your operating model is the key to designing and operationalizing a form of data governance that delivers measurable business value to your organisation.

      'Generate excitement for data: When people are excited and committed to the vision of data enablement, they're more likely to help ensure that data is high quality and safe.' – Petzold, et al., 2020

      Operating Model

      Defining your data governance operating model will help create a well-oiled program that sustainably delivers value to the organisation and manages risks while building and fostering a culture of data excellence along the way. Some organisations are able to establish a formal data governance office, whether independent or attached to the office of the chief data officer. Regardless of how you are organised, data governance requires a home, a leader, and an operating model to ensure its sustainability and evolution.

      Examples of focus areas for your operating model:

      • Delivery: While there are core tenets to every data governance program, there is a level of variability in the implementation of data governance programs across organisations, sectors, and industries. Every organisation has its own particular drivers and mandates, so the level and rigour applied will also vary.
      • The key is to determine what style will work best in your organisation, taking into consideration your organisational culture, executive leadership support (present and ongoing), catalysts such as other enterprise-wide transformative and modernisation initiatives, and/or regulatory and compliances drivers.

      • Communication: Communication is vital across all levels and stakeholder groups. For instance, there needs to be communication from the data governance office up to senior leadership, as well as communication within the data governance organisation, which is typically made up of the data governance steering committee, data governance council, executive sponsor/champion, data stewards, and data custodians and working groups.
      • Furthermore, communication with the wider organisation of data producers, users, and consumers is one of the core elements of the overall data governance communications plan.

      Communication is vital for ensuring acceptance of new processes, rules, guidelines, and technologies by all data producers and users as well as for sharing success stories of the program.

      Operating Model

      Tie the value of data governance and its initiatives back to the business capabilities that are enabled.

      'Leading organisations invest in change management to build data supporters and convert the sceptics. This can be the most difficult part of the program, as it requires motivating employees to use data and encouraging producers to share it (and ideally improve its quality at the source)[.]' – Petzold, et al., 2020

      Operating Model

      Examples of focus areas for your operating model (continued):

      • Change management and issue resolution: Data governance initiatives will very likely bring about a level of organisational disruption, with governance recommendations and future state requiring potentially significant business change. This may include a redesign of a substantial number of data processes affecting various business units, which will require tweaking the organisation's culture, thought processes, and procedures surrounding its data.
      • Preparing people for change well in advance will allow them to take the steps necessary to adapt and reduce potential confrontation. By planning for and efficiently communicating any changes that a data governance initiative may bring, many initial issues can be resolved from the outset.

        Attempting to implement change without an effective communications plan can result in disagreements over data control and stalemates between stakeholder units. The recommendations of the governance group must reflect the needs of all stakeholders or there will be pushback.

      • Performance measuring, monitoring and reporting: Measuring and reporting on performance, successes, and realisation of tangible business value are a must for sustaining, growing, and scaling your data governance program.
      • Aligning your data governance to the organisation's value realisation activities enables you to leverage the KPIs of those business capabilities to demonstrate tangible and measurable value. Use terms and language that will resonate with your senior business leadership.

      Info-Tech Tip:

      Launching a data governance program will bring with it a level of disruption to the culture of the organisation. That disruption doesn't have to be detrimental if you are prepared to manage the change proactively and effectively.

      Policies, Procedures & Standards

      'Data standards are the rules by which data are described and recorded. In order to share, exchange, and understand data, we must standardise the format as well as the meaning.' – U.S. Geological Survey

      Policies, Procedures & Standards

      • When defining, updating, or refreshing your data policies, procedures, and standards, ensure they are relevant, serve a purpose, and/or support the use of data in the organisation.
      • Avoid the common pitfall of building out a host of policies, procedures, and standards that are never used or followed by users and therefore don't bring value or serve to mitigate risk for the organisation.
      • Data policies can be thought of as formal statements and are typically created, approved, and updated by the organisation's data decision-making body (such as a data governance steering committee).
      • Data standards and procedures function as actions, or rules, that support the policies and their statements.
      • Standards and procedures are designed to standardise the processes during the overall data lifecycle. Procedures are instructions to achieve the objectives of the policies. The procedures are iterative and will be updated with approval from your data governance committee as needed.
      • Your organisation's data policies, standards, and procedures should not bog down or inhibit users; rather, they should enable confident data use and handling across the overall data lifecycle. They should support more effective and seamless data capture, integration, aggregation, sharing, and retention of data in the organisation.

      Examples of data policies:

      • Data Classification Policy
      • Data Retention Policy
      • Data Entry Policy
      • Data Backup Policy
      • Data Provenance Policy
      • Data Management Policy

      See Info-Tech's Data Governance Policy Template: This policy establishes uniformed data governance standards and identifies the shared responsibilities for assuring the integrity of the data and that it efficiently and effectively serves the needs of your organisation.

      Data Domain Documentation

      Select the correct granularity for your business need

      Diagram of data domain documentation
      Sources: Dataversity; Atlan; Analytics8

      Data Domain Documentation Examples

      Data Domain Documentation Examples

      Data Culture

      'Organisational culture can accelerate the application of analytics, amplify its power, and steer companies away from risky outcomes.' – Petzold, et al., 2020

      A healthy data culture is key to amplifying the power of your data and to building and sustaining an effective data governance program.

      What does a healthy data culture look like?

      • Everybody knows the data.
      • Everybody trusts the data.
      • Everybody talks about the data.

      Building a culture of data excellence.

      Leverage Info-Tech's Data Culture Diagnostic to understand your organisation's culture around data.

      Screenshot of Data Culture Scorecard

      Contact your Info-Tech Account Representative for more information on the Data Culture Diagnostic

      Cultivating a data-driven culture is not easy

      'People are at the heart of every culture, and one of the biggest challenges to creating a data culture is bringing everyone into the fold.' – Lim, Alation

      It cannot be purchased or manufactured,

      It must be nurtured and developed,

      And it must evolve as the business, user, and data landscapes evolve.

      'Companies that have succeeded in their data-driven efforts understand that forging a data culture is a relentless pursuit, and magic bullets and bromides do not deliver results.' – Randy Bean, 2020

      Hallmarks of a data-driven culture

      There is a trusted, single source of data the whole company can draw from.

      There's a business glossary and data catalogue and users know what the data fields mean.

      Users have access to data and analytics tools. Employees can leverage data immediately to resolve a situation, perform an activity, or make a decision – including frontline workers.

      Data literacy, the ability to collect, manage, evaluate, and apply data in a critical manner, is high.

      Data is used for decision making. The company encourages decisions based on objective data and the intelligent application of it.

      A data-driven culture requires a number of elements:

      • High-quality data
      • Broad access and data literacy
      • Data-driven decision-making processes
      • Effective communication

      Data Literacy

      Data literacy is an essential part of a data-driven culture.

      • Building a data-driven culture takes an ongoing investment of time, effort, and money.
      • This investment will not realise its full return without building up the organisation's data literacy.
      • Data literacy is about filling data knowledge gaps across all levels of the organisation.
      • It's about ensuring all users – senior leadership right through to core users – are equipped with appropriate levels of training, skills, understanding, and awareness around the organisation's data and the use of associated tools and technologies. Data literacy ensures users have the data they need and they know how to interpret and leverage it.
      • Data literacy drives the appetite, demand, and consumption for data.
      • A data-literate culture is one where the users feel confident and skilled in their use of data, leveraging it for making informed or evidence-based decisions and generating insights for the organisation.

      Data Management

      • Data governance serves as an enabler to all of the core components that make up data management:
        • Data quality management
        • Data architecture management
        • Data platform
        • Data integration
        • Data operations management
        • Data risk management
        • Reference and master data management (MDM)
        • Document and content management
        • Metadata management
        • Business intelligence (BI), reporting, analytics and advanced analytics, artificial intelligence (AI), machine learning (ML)
      • Key tools such as the business data glossary and data catalogue are vital for operationalizing data governance and in supporting data management disciplines such as data quality management, metadata management, and MDM as well as BI, reporting, and analytics.

      Enterprise Projects & Services

      • Data governance serves as an enabler to enterprise projects and services that require, use, share, sell, and/or rely on data for their viability and, ultimately, their success.
      • Folding or embedding data governance into the organisation's project management function or project management office (PMO) serves to ensure that, for any initiative, suitable consideration is given to how data is treated.
      • This may include defining parameters, following standards and procedures around bringing in new sources of data, integrating that data into the organisation's data ecosystem, using and sharing that data, and retaining that data post-project completion.
      • The data governance function helps to identify and manage any ethical issues, whether at the start of the project and/or throughout.
      • It provides a foundation for asking relevant questions as it relates to the use or incorporation of data in delivering the specific project or service. Do we know where the data obtained from? Do we have rights to use that data? Are there legislations, policies, or regulations that guide or dictate how that data can be used? What are the positive effects, negative impacts, and/or risks associated with our intended use of that data? Are we positioned to mitigate those risks?
      • Mature data governance creates organisations where the above considerations around data management and the ethical use and handling of data is routinely implemented across the business and in the rollout and delivery of projects and services.

      Data Privacy & Security

      • Data governance supports the organisation's data privacy and security functions.
      • Key tools include the data classification policy and standards and defined roles around data ownership and data stewardship. These are vital for operationalizing data governance and supporting data privacy, security, and the ethical use and handling of data.
      • While some organisations may have a dedicated data security and privacy group, data governance provides an added level of oversight in this regard.
      • Some of the typical checks and balances include ensuring:
        • There are policies and procedures in place to restrict and monitor staff's access to data (one common way this is done is according to job descriptions and responsibilities) and that these comply with relevant laws and regulations.
        • There's a data classification scheme in place where data has been classified on a hierarchy of sensitivity (e.g. top secret, confidential, internal, limited, public).
        • The organisation has a comprehensive data security framework, including administrative, physical, and technical procedures for addressing data security issues (e.g. password management and regular training).
        • Risk assessments are conducted, including an evaluation of risks and vulnerabilities related to intentional and unintentional misuse of data.
        • Policies and procedures are in place to mitigate the risks associated with incidents such as data breaches.
        • The organisation regularly audits and monitors its data security.

      Ethical Use & Handling of Data

      Data governance will support your organisation's ethical use and handling of data by facilitating definition around important factors, such as:

      • What are the various data assets in the organisation and what purpose(s) can they be used for? Are there any limitations?
      • Who is the related data owner? Who holds accountability for that data? Who will be answerable?
      • Where was the data obtained from? What is the intended use of that data? Do you have rights to use that data? Are there legislations, policies, or regulations that guide or dictate how that data can be used?
      • What are the positive effects, negative impacts, and/or risks associated with the use of that data?

      Ethical Use & Handling of Data

      • Data governance serves as an enabler to the ethical use and handling of an organisation's data.
      • The Open Data Institute (ODI) defines data ethics as: 'A branch of ethics that evaluates data practices with the potential to adversely impact on people and society – in data collection, sharing and use.'
      • Data ethics relates to good practice around how data is collected, used and shared. It's especially relevant when data activities have the potential to impact people and society, whether directly or indirectly (Open Data Institute, 2019).
      • A failure to handle and use data ethically can negatively impact an organisation's direct stakeholders and/or the public at large, lead to a loss of trust and confidence in the organisation's products and services, lead to financial loss, and impact the organisation's brand, reputation, and legal standing.
      • Data governance plays a vital role is building and managing your data assets, knowing what data you have, and knowing the limitations of that data. Data ownership, data stewardship, and your data governance decision-making body are key tenets and foundational components of your data governance. They enable an organisation to define, categorise, and confidently make decisions about its data.

      Step 2.2

      Gauge Your Organisation's Current Data Culture

      Activities

      2.2.1 Gauge Your Organisation's Current Data Culture

      This step will guide you through the following activities:

      • Conduct a data culture survey or leverage Info-Tech's Data Culture Diagnostic to increase your understanding of your organisation's data culture

      Outcomes of this step

      • An understanding of your organisational data culture

      2.2.1 Gauge Your Organisation's Current Data Culture

      Conduct a Data Culture Survey or Diagnostic

      The objectives of conducting a data culture survey are to increase the understanding of the organisation's data culture, your users' appetite for data, and their appreciation for data in terms of governance, quality, accessibility, ownership, and stewardship. To perform a data culture survey:

      1. Identify members of the data user base, data consumers, and other key stakeholders for surveying.
      2. Conduct an information session to introduce Info-Tech's Data Culture Diagnostic survey. Explain the objective and importance of the survey and its role in helping to understand the organisation's current data culture and inform the improvement of that culture.
      3. Roll out the Info-Tech Data Culture Diagnostic survey to the identified users and stakeholders.
      4. Debrief and document the results and scorecard in the Data Strategy Stakeholder Interview Guide and Findings document.

      Input

      • Email addresses of participants in your organisation who should receive the survey

      Output

      • Your organisation's Data Culture Scorecard for understanding current data culture as it relates to the use and consumption of data
      • An understanding of whether data is currently perceived to be an asset to the organisation

      Materials

      Screenshot of Data Culture Scorecard

      Participants

      • Participants include those at the senior leadership level through to middle management, as well as other business stakeholders at varying levels across the organisation
      • Data owners, stewards, and custodians
      • Core data users and consumers

      Contact your Info-Tech Account Representative for details on launching a Data Culture Diagnostic.

      Phase 3

      Build a Target State Roadmap and Plan

      Three circles are in the image that list the three phases and the main steps. Phase 3 is highlighted.

      'Achieving data success is a journey, not a sprint. Companies that set a clear course, with reasonable expectations and phased results over a period of time, get to the destination faster.' – Randy Bean, 2020

      This phase will guide you through the following activities:

      • Build your Data Governance Roadmap
      • Develop a target state plan comprising of prioritised initiatives

      This phase involves the following participants:

      • Data Governance Leadership
      • Data Owners/Data Stewards
      • Data Custodians
      • Data Governance Working Group(s)

      Step 3.1

      Formulate an Actionable Roadmap and Right-Sized Plan

      This step will guide you through the following activities:

      • Build your data governance roadmap
      • Develop a target state plan comprising of prioritised initiatives

      Download Info-Tech's Data Governance Planning and Roadmapping Workbook

      See Info-Tech's Data Governance Program Charter Template: A program charter template to sell the importance of data governance to senior executives.

      This template will help get the backing required to get a data governance project rolling. The program charter will help communicate the project purpose, define the scope, and identify the project team, roles, and responsibilities.

      Outcomes of this step

      • A foundation for data governance initiative planning that's aligned with the organisation's business architecture: value streams, business capability map, and strategy map

      Build a right-sized roadmap

      Formulate an actionable roadmap that is right sized to deliver value in your organisation.

      Key considerations:

      • When building your data governance roadmap, ensure you do so through an enterprise lens. Be cognizant of other initiatives that might be coming down the pipeline that may require you to align your data governance milestones accordingly.
      • Apart from doing your planning with consideration for other big projects or launches that might be in-flight and require the time and attention of your data governance partners, also be mindful of the more routine yet still demanding initiatives.
      • When doing your roadmapping, consider factors like the organisation's fiscal cycle, typical or potential year-end demands, and monthly/quarterly reporting periods and audits. Initiatives such as these are likely to monopolise the time and focus of personnel key to delivering on your data governance milestones.

      Sample milestones:

      Data Governance Leadership & Org Structure Definition

      Define the home for data governance and other key roles around ownership and stewardship, as approved by senior leadership.

      Data Governance Charter and Policies

      Create a charter for your program and build/refresh associated policies.

      Data Culture Diagnostic

      Understand the organisation's current data culture, perception of data, value of data, and knowledge gaps.

      Use Case Build and Prioritisation

      Build a use case that is tied to business capabilities. Prioritise accordingly.

      Business Data Glossary/catalogue

      Build and/or refresh the business' glossary for addressing data definitions and standardisation issues.

      Tools & Technology

      Explore the tools and technology offering in the data governance space that would serve as an enabler to the program. (e.g. RFI, RFP).

      Recall: Info-Tech's Data Governance Framework

      An image of Info-Tech's Data Governance Framework

      Build an actionable roadmap

      Data Governance Leadership & Org Structure Division

      Define key roles for getting started.

      Use Case Build & Prioritisation

      Start small and then scale – deliver early wins.

      Literacy Program

      Start understanding data knowledge gaps, building the program, and delivering.

      Tools & Technology

      Make the available data governance tools and technology work for you.

      Key components of your data governance roadmap

      Data Governance Program Charter Template – A program charter template to sell the importance of data governance to senior executives.

      This template will help get the backing required to get a data governance project rolling. The program charter will help communicate the project purpose, define the scope, and identify the project team, roles, and responsibilities.

      By now, you have assessed current data governance environment and capabilities. Use this assessment, coupled with the driving needs of your business, to plot your data Governance roadmap accordingly.

      Sample data governance roadmap milestones:

      • Define data governance leadership.
      • Define and formalise data ownership and stewardship (as well as the role IT/data management will play as data custodians).
      • Build/confirm your business capability map and data domains.
      • Build business data use cases specific to business capabilities.
      • Define business measures/KPIs for the data governance program (i.e. metrics by use case that are relevant to business capabilities).
      • Data management:
        • Build your data glossary or catalogue starting with identified and prioritised terms.
        • Define data domains.
      • Design and define the data governance operating model (oversight model definition, communication plan, internal marketing such as townhalls, formulate change management plan, RFP of data governance tool and technology options for supporting data governance and its administration).
      • Data policies and procedures:
        • Formulate, update, refresh, consolidate, rationalise, and/or retire data policies and procedures.
        • Define policy management and administration framework (i.e. roll-out, maintenance, updates, adherence, system to be used).
      • Conduct Info-Tech's Data Culture Diagnostic or survey (across all levels of the organisation).
      • Define and formalise the data literacy program (build modules, incorporate into LMS, plan lunch and learn sessions).
      • Data privacy and security: build data classification policy, define classification standards.
      • Enterprise projects and services: embed data governance in the organisation's PMO, conduct 'Data Governance 101' for the PMO.

      Defining data governance roles and organisational structure at Organisation

      The approach employed for defining the data governance roles and supporting organisational structure for .

      Key Considerations:

      • The data owner and data steward roles are formally defined and documented within the organisation. Their involvement is clear, well-defined, and repeatable.
      • There are data owners and data stewards for each data domain within the organisation. The data steward role is given to someone with a high degree of subject matter expertise.
      • Data owners and data stewards are effective in their roles by ensuring that their data domain is clean and free of errors and that they protect the organisation against data loss.
      • Data owners and data stewards have the authority to make final decisions on data definitions, formats, and standard processes that apply to their respective data sets. Data owners and data stewards have authority regarding who has access to certain data.
      • Data owners and data stewards are not from the IT side of the organisation. They understand the lifecycle of the data (how it is created, curated, retrieved, used, archived, and destroyed) and they are well-versed in any compliance requirements as it relates to their data.
      • The data custodian role is formally defined and is given to the relevant IT expert. This is an individual with technical administrative and/or operational responsibility over data (e.g. a DBA).
      • A data governance steering committee exists and is comprised of well-defined roles, responsibilities, executive sponsors, business representatives, and IT experts.
      • The data governance steering committee works to provide oversight and enforce policies, procedures, and standards for governing data.
      • The data governance working group has cross-functional representation. This comprises business and IT representation, as well as project management and change management where applicable: data stewards, data custodians, business subject matter experts, PM, etc.).
      • Data governance meetings are coordinated and communicated about. The meeting agenda is always clear and concise, and meetings review pressing data-related issues. Meeting minutes are consistently documented and communicated.

      Sample: Business capabilities to data owner and data stewards mapping for a selected data domain

      Info-Tech Insight

      Your organisation's value streams and the associated business capabilities require effectively governed data. Without this, you face elevated operational costs, missed opportunities, eroded stakeholder satisfaction, and exposure to increased business risk.

      Enable business capabilities with data governance role definitions.

      Sample: Business capabilities to data owner and data stewards mapping for a selected data domain

      Consider your technology options:

      Make the available data governance tools and technology work for you:

      • Data catalogue
      • Business data glossary
      • Data lineage
      • Metadata management

      Logos of data governance tools and technology.

      These are some of the data governance tools and technology players. Check out SoftwareReviews for help making better software decisions.

      Make the data steward the catalyst for organisational change and driving data culture

      The data steward must be empowered and backed politically with decision-making authority, or the role becomes stale and powerless.

      Ensuring compliance can be difficult. Data stewards may experience pushback from stakeholders who must deliver on the policies, procedures, and processes that the data steward enforces.

      Because the data steward must enforce data processes and liaise with so many different people and departments within the organisation, the data steward role should be their primary full-time job function – where possible.

      However, in circumstances where budget doesn't allow a full-time data steward role, develop these skills within the organisation by adding data steward responsibilities to individuals who are already managing data sets for their department or line of business.

      Info-Tech Tip

      A stewardship role is generally more about managing the cultural change that data governance brings. This requires the steward to have exceptional interpersonal skills that will assist in building relationships across departmental boundaries and ensuring that all stakeholders within the organisation believe in the initiative, understand the anticipated outcomes, and take some level of responsibility for its success.

      Changes to organisational data processes are inevitable; have a communication plan in place to manage change

      Create awareness of your data governance program. Use knowledge transfer to get as many people on board as possible.

      Data governance initiatives must contain a strong organisational disruption component. A clear and concise communication strategy that conveys milestones and success stories will address the various concerns that business unit stakeholders may have.

      By planning for and efficiently communicating any changes that a data governance initiative may bring, many initial issues can be resolved from the outset.

      Governance recommendations will require significant business change. The redesign of a substantial number of data processes affecting various business units will require an overhaul of the organisation's culture, thought processes, and procedures surrounding its data. Preparing people for change well in advance will allow them to take the necessary steps to adapt and reduce potential confrontation.

      Because a data governance initiative will involve data-driven business units across the organisation, the governance team must present a compelling case for data governance to ensure acceptance of new processes, rules, guidelines, and technologies by all data producers and users.

      Attempting to implement change without an effective communication plan can result in disagreements over data control and stalemates between stakeholder units. The recommendations of the governance group must reflect the needs of all stakeholders or there will be pushback.

      Info-Tech Insight

      Launching a data governance initiative is guaranteed to disrupt the culture of the organisation. That disruption doesn't have to be detrimental if you are prepared to manage the change proactively and effectively.

      Create a common data governance vision that is consistently communicated to the organisation

      A data governance program should be an enterprise-wide initiative.

      To create a strong vision for data governance, there must be participation from the business and IT. A common vision will articulate the state the organisation wishes to achieve and how it will reach that state. Visioning helps to develop long-term goals and direction.

      Once the vision is established, it must be effectively communicated to everyone, especially those who are involved in creating, managing, disposing, or archiving data.

      The data governance program should be periodically refined. This will ensure the organisation continues to incorporate best methods and practices as the organisation grows and data needs evolve.

      Info-Tech Tips

      • Use information from the stakeholder interviews to derive business goals and objectives.
      • Work to integrate different opinions and perspectives into the overall vision for data governance.
      • Brainstorm guiding principles for data and understand the overall value to the organisation.

      Develop a compelling data governance communications plan to get all departmental lines of business on board

      A data governance program will impact all data-driven business units within the organisation.

      A successful data governance communications plan involves making the initiative visible and promoting staff awareness. Educate the team on how data is collected, distributed, and used, what internal processes use data, and how that data is used across departmental boundaries.

      By demonstrating how data governance will affect staff directly, you create a deeper level of understanding across lines of business, and ultimately, a higher level of acceptance for new processes, rules, and guidelines.

      A clear and concise communications strategy will raise the profile of data governance within the organisation, and staff will understand how the program will benefit them and how they can share in the success of the initiative. This will end up providing support for the initiative across the board.

      A proactive communications plan will:

      • Assist in overcoming issues with data control, stalemates between stakeholder units, and staff resistance.
      • Provide a formalised process for implementing new policies, rules, guidelines, and technologies, and managing organisational data.
      • Detail data ownership and accountability for decision making, and identify and resolve data issues throughout the organisation.
      • Encourage acceptance and support of the initiative.

      Info-Tech Tip

      Focus on literacy and communication: include training in the communication plan. Providing training for data users on the correct procedures for updating and verifying the accuracy of data, data quality, and standardised data policies will help validate how data governance will benefit them and the organisation.

      Leverage the data governance program to communicate and promote the value of data within the organisation

      The data governance program is responsible for continuously promoting the value of data to the organisation. The data governance program should seek a variety of ways to educate the organisation and data stakeholders on the benefit of data management.

      Even if data policies and procedures are created, they will be highly ineffective if they are not properly communicated to the data producers and users alike.

      There needs to be a communication plan that highlights how the data producer and user will be affected, what their new responsibilities are, and the value of that change.

      To learn how to manage organisational change, refer to Info-Tech's Master Organisational Change Management Practices.

      Understand what makes for an effective policy for data governance

      It can be difficult to understand what a policy is, and what it is not. Start by identifying the differences between a policy and standards, guidelines, and procedures.

      Diagram of an effective policy for data governance

      The following are key elements of a good policy:

      Heading Descriptions
      Purpose Describes the factors or circumstances that mandate the existence of the policy. Also states the policy's basic objectives and what the policy is meant to achieve.
      Scope Defines to whom and to what systems this policy applies. Lists the employees required to comply or simply indicates 'all' if all must comply. Also indicates any exclusions or exceptions, i.e. those people, elements, or situations that are not covered by this policy or where special consideration may be made.
      Definitions Define any key terms, acronyms, or concepts that will be used in the policy. A standard glossary approach is sufficient.
      Policy Statements Describe the rules that comprise the policy. This typically takes the form of a series of short prescriptive and proscriptive statements. Sub-dividing this section into sub-sections may be required depending on the length or complexity of the policy.
      Non-Compliance Clearly describe consequences (legal and/or disciplinary) for employee non-compliance with the policy. It may be pertinent to describe the escalation process for repeated non-compliance.
      Agreement Confirms understanding of the policy and provides a designated space to attest to the document.

      Leverage myPolicies, Info-Tech's web-based application for managing your policies and procedures

      Most organisations have problems with policy management. These include:

      1. Policies are absent or out of date
      2. Employees largely unaware of policies in effect
      3. Policies are unmonitored and unenforced
      4. Policies are in multiple locations
      5. Multiple versions of the same policy exist
      6. Policies managed inconsistently across different silos
      7. Policies are written poorly by untrained authors
      8. Inadequate policy training program
      9. Draft policies stall and lose momentum
      10. Weak policy support from senior management

      Technology should be used as a means to solve these problems and effectively monitor, enforce, and communicate policies.

      Product Overview

      myPolicies is a web-based solution to create, distribute, and manage corporate policies, procedures, and forms. Our solution provides policy managers with the tools they need to mitigate the risk of sanctions and reduce the administrative burden of policy management. It also enables employees to find the documents relevant to them and build a culture of compliance.

      Some key success factors for policy management include:

      • Store policies in a central location that is well known and easy to find and access. A key way that technology can help communicate policies is by having them published on a centralised website.
      • Link this repository to other policies' taxonomies of your organisation. E.g. HR policies to provide a single interface for employees to access guidance across the organisation.
      • Reassess policies annually at a minimum. myPolicies can remind you to update the organisation's policies at the appropriate time.
      • Make the repository searchable and easily navigable.
      • myPolicies helps you do all this and more.
      myPolicies logo myPolicies

      Enforce data policies to promote consistency of business processes

      Data policies are short statements that seek to manage the creation, acquisition, integrity, security, compliance, and quality of data. These policies vary amongst organisations, depending on your specific data needs.

      • Policies describe what to do, while standards and procedures describe how to do something.
      • There should be few data policies, and they should be brief and direct. Policies are living documents and should be continuously updated to respond to the organisation's data needs.
      • The data policies should highlight who is responsible for the data under various scenarios and rules around how to manage it effectively.

      Examples of Data Policies

      Trust

      • Data Cleansing and Quality Policy
      • Data Entry Policy

      Availability

      • Acceptable Use Policy
      • Data Backup Policy

      Security

      • Data Security Policy
      • Password Policy Template
      • User Authorisation, Identification, and Authentication Policy Template
      • Data Protection Policy

      Compliance

      • Archiving Policy
      • Data Classification Policy
      • Data Retention Policy

      Leverage data management-related policies to standardise your data management practices

      Info-Tech's Data Management Policy:

      This policy establishes uniform data management standards and identifies the shared responsibilities for assuring the integrity of the data and that it efficiently and effectively serves the needs of the organisation. This policy applies to all critical data and to all staff who may be creators and/or users of such data.

      Info-Tech's Data Entry Policy:

      The integrity and quality of data and evidence used to inform decision making is central to both the short-term and long-term health of an organisation. It is essential that required data be sourced appropriately and entered into databases and applications in an accurate and complete manner to ensure the reliability and validity of the data and decisions made based on the data.

      Info-Tech's Data Provenance Policy:

      Create policies to keep your data's value, such as:

      • Only allow entry of data from reliable sources.
      • Employees entering and accessing data must observe requirements for capturing/maintaining provenance metadata.
      • Provenance metadata will be used to track the lifecycle of data from creation through to disposal.

      Info-Tech's Data Integration and Virtualisation Policy:

      This policy aims to assure the organisation, staff, and other interested parties that data integration, replication, and virtualisation risks are taken seriously. Staff must use the policy (and supporting guidelines) when deciding whether to integrate, replicate, or virtualise data sets.

      Select the right mix of metrics to successfully supervise data policies and processes

      Policies are only as good as your level of compliance. Ensure supervision controls exist to oversee adherence to policies and procedures.

      Although they can be highly subjective, metrics are extremely important to data governance success.

      • Establishing metrics that measure the performance of a specific process or data set will:
        • Create a greater degree of ownership from data stewards and data owners.
        • Help identify underperforming individuals.
        • Allow the steering committee to easily communicate tailored objectives to individual data stewards and owners.
      • Be cautious when establishing metrics. The wrong metrics can have negative repercussions.
        • They will likely draw attention to an aspect of the process that doesn't align with the initial strategy.
        • Employees will work hard and grow frustrated as their successes aren't accurately captured.

      Policies are great to have from a legal perspective, but unless they are followed, they will not benefit the organisation.

      • One of the most useful metrics for policies is currency. This tracks how up to date the policy is and how often employees are informed about the policy. Often, a policy will be introduced and then ignored. Policies must be continuously reviewed by management and employees.
      • Some other metrics include adherence (including performance in tests for adherence) and impacts from non-adherence.

      Review metrics on an ongoing basis with those data owners/stewards who are accountable, the data governance steering committee, and the executive sponsors.

      Establish data standards and procedures for use across all organisational lines of business

      A data governance program will impact all data-driven business units within the organisation.

      • Data management procedures are the methods, techniques, and steps to accomplish a specific data objective. Creating standard data definitions should be one of the first tasks for a data governance steering committee.
      • Data moves across all departmental boundaries and lines of business within the organisation. These definitions must be developed as a common set of standards that can be accepted and used enterprise wide.
      • Consistent data standards and definitions will improve data flow across departmental boundaries and between lines of business.
      • Ensure these standards and definitions are used uniformly throughout the organisation to maintain reliable and useful data.

      Data standards and procedural guidelines will vary from company to company.

      Examples include:

      • Data modelling and architecture standards.
      • Metadata integration and usage procedures.
      • Data security standards and procedures.
      • Business intelligence standards and procedures.

      Info-Tech Tip

      Have a fundamental data definition model for the entire business to adhere to. Those in the positions that generate and produce data must follow the common set of standards developed by the steering committee and be accountable for the creation of valid, clean data.

      Changes to organisational data processes are inevitable; have a communications plan in place to manage change

      Create awareness of your data governance program, using knowledge transfer to get as many people on board as possible.

      By planning for and efficiently communicating any changes that a data governance initiative may bring, many initial issues can be resolved from the outset.

      Governance recommendations will require significant business change. The redesign of a substantial number of data processes affecting various business units will require an overhaul of the organisation's culture, thought processes, and procedures surrounding its data. Preparing people for change well in advance will allow them to take the necessary steps to adapt and reduce potential confrontation.

      Because a data governance initiative will involve data-driven business units across the organisation, the governance team must present a compelling case for data governance to ensure acceptance of new processes, rules, guidelines, and technologies by all data producers and users.

      Attempting to implement change without an effective communications plan can result in disagreements over data control and stalemates between stakeholder units. The recommendations of the governance group must reflect the needs of all stakeholders or there will be pushback.

      Data governance initiatives will very likely bring about a level of organisational disruption. A clear and concise communications strategy that conveys milestones and success stories will address the various concerns that business unit stakeholders may have.

      Info-Tech Tip

      Launching a data governance program will bring with it a level of disruption to the culture of the organisation. That disruption doesn't have to be detrimental if you are prepared to manage the change proactively and effectively.

      Other Deliverables:

      The list of supporting deliverables will help to kick start on some of the Data Governance initiatives

      • Data Classification Policy, Standard, and Procedure
      • Data Quality Policy, Standard, and Procedure
      • Metadata Management Policy, Standard, and Procedure
      • Data Retention Policy and Procurement

      Screenshot from Data Classification Policy, Standard, and Procedure

      Data Classification Policy, Standard, and Procedure

      Screenshot from Data Retention Policy and Procedure

      Data Retention Policy and Procedure

      Screenshot from Metadata Management Policy, Standard, and Procedure

      Metadata Management Policy, Standard, and Procedure

      Screenshot from Data Quality Policy, Standard, and Procedure

      Data Quality Policy, Standard, and Procedure

      Additional Support

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech Workshop.

      Picture of analyst

      Contact your account representative for more information.

      workshops@infotech.com 1-888-670-8889

      To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team. Info-Tech analysts will join you and your team at your location or welcome you to Info-Tech's historic Toronto office to participate in an innovative onsite workshop.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      Screenshot of example data governance strategy map.

      Build Your Business and User Context

      Work with your core team of stakeholders to build out your data governance strategy map, aligning data governance initiatives with business capabilities, value streams, and, ultimately, your strategic priorities.

      Screenshot of Data governance roadmap

      Formulate a Plan to Get to Your Target State

      Develop a data governance future state roadmap and plan based on an understanding of your current data governance capabilities, your operating environment, and the driving needs of your business.

      Related Info-Tech Research

      Build a Robust and Comprehensive Data Strategy

      Key to building and fostering a data-driven culture.

      Create a Data Management Roadmap

      Streamline your data management program with our simplified framework.

      The First 100 Days as CDO

      Be the voice of data in a time of transformation.

      Research Contributors

      Name Position Company
      David N. Weber Executive Director - Planning, Research and Effectiveness Palm Beach State College
      Izabela Edmunds Information Architect Mott MacDonald
      Andy Neill Practice Lead, Data & Analytics Info-Tech Research Group
      Dirk Coetsee Research Director, Data & Analytics Info-Tech Research Group
      Graham Price Executive Advisor, Advisory Executive Services Info-Tech Research Group
      Igor Ikonnikov Research Director, Data & Analytics Info-Tech Research Group
      Jean Bujold Senior Workshop Delivery Director Info-Tech Research Group
      Rajesh Parab Research Director, Data & Analytics Info-Tech Research Group
      Reddy Doddipalli Senior Workshop Director Info-Tech Research Group
      Valence Howden Principal Research Director, CIO Info-Tech Research Group

      Bibliography

      Alation. “The Alation State of Data Culture Report – Q3 2020.” Alation, 2020. Accessed 25 June 2021.

      Allott, Joseph, et al. “Data: The Next Wave in Forestry Productivity.” McKinsey & Company, 27 Oct. 2020. Accessed 25 June 2021.

      Bean, Randy. “Why Culture Is the Greatest Barrier to Data Success.” MIT Sloan Management Review, 30 Sept. 2020. Accessed 25 June 2021.

      Brence, Thomas. “Overcoming the Operationalization Challenge With Data Governance at New York Life.” Informatica, 18 March 2020. Accessed 25 June 2021.

      Bullmore, Simon, and Stuart Coleman. “ODI Inside Business – A Checklist for Leaders.” Open Data Institute, 19 Oct. 2020. Accessed 25 June 2021.

      Canadian Institute for Health Information. “Developing and Implementing Accurate National Standards for Canadian Health Care Information.” Canadian Institute for Health Information. Accessed 25 June 2021.

      Carruthers, Caroline, and Peter Jackson. “The Secret Ingredients of the Successful CDO.” IRM UK Connects, 23 Feb. 2017.

      Dashboards. “Useful KPIs for Healthy Hospital Quality Management.” Dashboards. Accessed 25 June 2021.

      Dashboards. “Why (and How) You Should Improve Data Literacy in Your Organization Today.” Dashboards. Accessed 25 June 2021.

      Datapine. “Healthcare Key Performance Indicators and Metrics.” Datapine. Accessed 25 June 2021.

      Datapine. “KPI Examples & Templates: Measure what matters the most and really impacts your success.” Datapine. Accessed 25 June 2021.

      Diaz, Alejandro, et al. “Why Data Culture Matters.” McKinsey Quarterly, Sept. 2018. Accessed 25 June 2021.

      Everett, Dan. “Chief Data Officer (CDO): One Job, Four Roles.” Informatica, 9 Sept. 2020. Accessed 25 June 2021.

      Experian. “10 Signs You Are Sitting On A Pile Of Data Debt.” Experian. Accessed 25 June 2021.

      Fregoni, Silvia. “New Research Reveals Why Some Business Leaders Still Ignore the Data.” Silicon Angle, 1 Oct. 2020

      Informatica. Holistic Data Governance: A Framework for Competitive Advantage. Informatica, 2017. Accessed 25 June 2021.

      Knight, Michelle. “What Is a Data Catalog?” Dataversity, 28 Dec. 2017. Web.

      Lim, Jason. “Alation 2020.3: Getting Business Users in the Game.” Alation, 2020. Accessed 25 June 2021.

      McDonagh, Mariann. “Automating Data Governance.” Erwin, 29 Oct. 2020. Accessed 25 June 2021.

      NewVantage Partners. Data-Driven Business Transformation: Connecting Data/AI Investment to Business Outcomes. NewVantage Partners, 2020. Accessed 25 June 2021.

      Olavsrud, Thor. “What Is Data Governance? A Best Practices Framework For Managing Data Assets.” CIO.com, 18 March 2021. Accessed 25 June 2021.

      Open Data Institute. “Introduction to Data Ethics and the Data Ethics Canvas.” Open Data Institute, 2020. Accessed 25 June 2021.

      Open Data Institute. “The UK National Data Strategy 2020: Doing Data Ethically.” Open Data Institute, 17 Nov. 2020. Accessed 25 June 2021.

      Open Data Institute. “What Is the Data Ethics Canvas?” Open Data Institute, 3 July 2019. Accessed 25 June 2021.

      Pathak, Rahul. “Becoming a Data-Driven Enterprise: Meeting the Challenges, Changing the Culture.” MIT Sloan Management Review, 28 Sept. 2020. Accessed 25 June 2021.

      Petzold, Bryan, et al. “Designing Data Governance That Delivers Value.” McKinsey & Company, 26 June 2020. Accessed 25 June 2021.

      Redman, Thomas, et al. “Only 3% of Companies’ Data Meets Basic Quality Standards.” Harvard Business Review. 11 Sept 2017.

      Smaje, Kate. “How Six Companies Are Using Technology and Data To Transform Themselves.” McKinsey & Company, 12 Aug. 2020. Accessed 25 June 2021.

      Talend. “The Definitive Guide to Data Governance.” Talend. Accessed 25 June 2021.

      “The Powerfully Simple Modern Data Catalog.” Atlan, 2021. Web.

      U.S. Geological Survey. “Data Management: Data Standards.” U.S. Geological Survey. Accessed 25 June 2021.

      Waller, David. “10 Steps to Creating a Data-Driven Culture.” Harvard Business Review, 6 Feb. 2020. Accessed 25 June 2021.

      “What Is the Difference Between A Business Glossary, A Data Dictionary, and A Data Catalog, and How Do They Play A Role In Modern Data Management?” Analytics8, 23 June 2021. Web.

      Wikipedia. “RFM (Market Research).” Wikipedia. Accessed 25 June 2021.

      Windheuser, Christoph, and Nina Wainwright. “Data in a Modern Digital Business.” Thoughtworks, 12 May 2020. Accessed 25 June 2021.

      Wright, Tom. “Digital Marketing KPIs - The 12 Key Metrics You Should Be Tracking.” Cascade, 3 March 2021. Accessed 25 June 2021.

      Build Your Data Practice and Platform

      • Buy Link or Shortcode: {j2store}347|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Data Management
      • Parent Category Link: /data-management

      The complex nature of data investment leads to de-scoping and delivery of data services that do not meet business needs or give value to the business. Subject matter experts are hired to resolve the problem, but their success is impacted by absent architecture, technology, and organizational alignment.

      Our Advice

      Critical Insight

      Walking through a book of architecture building plans with a personal guide is cheaper and faster than employing an architect to build and design your home.

      Impact and Result

      Info-Tech's approach provides a proven methodology that includes the following:

      • Business-aligned data initiatives and capabilities that address data challenges and realize business strategic objectives.
      • Comprehensive data practice designed based on the required business and data capabilities.
      • Data platform design based on Info-Tech data architecture reference patterns and prioritized data initiatives and capabilities.

      Build Your Data Practice and Platform Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Build Your Data Practice and Platform Storyboard – A step-by-step document that leverages road-tested patterns and frameworks to properly build your data practice and pattern in continuous alignment with the business landscape.

      Info-Tech's approach provides a proven methodology that includes following:   

    • Business-aligned data initiatives and capabilities that address data challenges and realize business strategic objectives.
    • Comprehensive data practices designed based on the required business and data capabilities.
      • Build Your Data Practice and Platform Storyboard

      2. Data Practice and Platform Models – Leveraging best-of-breed frameworks to help you build a clear, concise, and compelling data practice and platform.

      Data practice & platform pre-build pattern templates based on Info-Tech data reference patterns and data platform design best practices.

      • Data Practice and Platform Models

      Infographic

      Workshop: Build Your Data Practice and Platform

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Establish Business Context and Value

      The Purpose

      Establish business context and value.

      Key Benefits Achieved

      Business context and strategic driver.

      Activities

      1.1 Understand/confirm the organization's strategic goals

      1.2 Classify the strategic goals and map to business drivers

      1.3 Identify the business capabilities that the strategy focuses on

      1.4 Identify the business processes realizing the strategy

      Outputs

      Business context and strategic drivers

      Prioritized business capabilities and processes

      Data culture survey results analysis

      2 Identify Your Top Initiatives

      The Purpose

      Identify your top initiatives.

      Key Benefits Achieved

      High-value business-aligned data initiative.

      Activities

      2.1 Highlight data-related outcomes/goals to realize to fulfill the business goal

      2.2 Map business data initiatives to the business strategic goals

      2.3 Prioritize data initiatives

      Outputs

      High-value, business-aligned data initiatives

      3 Analyze Data Challenges

      The Purpose

      Analyze data challenges.

      Key Benefits Achieved

      Clear understanding of the data challenges.

      Activities

      3.1 Map data challenges to Info-Tech data challenges

      3.2 Review Info-Tech data capabilities based on prioritized initiatives

      3.3 Discuss data platform and practice next steps

      Outputs

      List of data challenges preventing data maturation with the organization

      4 Map Data Capability

      The Purpose

      Map data capability.

      Key Benefits Achieved

      Prioritized data capability.

      Activities

      4.1 Map data challenges to Info-Tech data challenges

      4.2 Review Info-Tech data capabilities based on prioritized initiatives

      4.3 Discuss data platform and practice next steps

      Outputs

      Required data capabilities

      Data platform and practice – plan

      Initialized data management RACI 

      Further reading

      Build Your Data Practice and Platform

      Construct a scalable data foundation

      Analyst Perspective

      Build a data practice and platform that delivers value to your organization.

      The build or optimization of your data practice and data platform must be predicated on a thorough understanding of the organization’s goals, objectives, and priorities and the business capabilities and process they are meant to support and enable.

      Formalizing your practice or constructing your platform just for the sake of doing so often results in an initiative that is lengthy, costly, fizzles out, does not deliver business value, and ends up being considered a failure.

      Leverage Info-Tech’s approach and incorporate our pre-built models and patterns to effectively navigate that crucial and often difficult phase upfront of comprehensively defining business data needs so you can ultimately realize faster time-to-delivery of your overall data practice and platform.

      Photo of Rajesh Parab, Director, Research & Advisory, Data & Analytics Practice, Info-Tech Research Group.

      Rajesh Parab
      Director, Research & Advisory, Data & Analytics Practice
      Info-Tech Research Group

      Photo of Crystal Singh, Director, Research & Advisory, Data & Analytics Practice, Info-Tech Research Group.

      Crystal Singh
      Director, Research & Advisory, Data & Analytics Practice
      Info-Tech Research Group

      Attempting to Solve Data Problems?

      Situation
      • Lack of data centric leadership results in downstream issues such as integration, quality, and accessibility.
      • The complex nature of the data and lack of understanding leads to de-scoping delivery of data services that does not meet business needs or add value.
      • Poorly designed practice and siloed platforms result in an initiative that is lengthy, costly, fizzles out, does not deliver business value, and ends up being considered a failure.
      Complication
      • Data problem: When the data problem is diagnosed, the organization adopts a tactical approach.
      • Confirmation bias: Subject matter experts (SME) are hired to resolve the poorly defined problem, but the success of the SME is impacted by lack of architecture, technology, and organizational alignment.
      • Still no value: The selected tactical approach does not provide a solid foundation or solve your data problem.
      • Strategy for sake of strategy: Implementing a strategic approach for the sake of being strategic but this becomes overwhelming.
      • Fall back to tactical and operational: The data services are now potentially exposed and vulnerable, which strains business continuity and increases data debt.
      • Increased complexity and risk: Data silos, poor understanding, and high complexity results in an unmanageable data environment.
      Resolution
      • Requirements: Define and align your data requirement to business.
      • Capabilities: Discover data, identify data capabilities, and map your requirements.
      • Practices: Design and select fit-for-purpose data practices.
      • Platform: Optimize your data platform investments though sound architecture.

      Info-Tech Insight

      The true value of data comes from defining intentional relationships between the business and the data through a well thought out data platform and practice.

      Situation – Perpetual Data Problem

      Diagram of a head with gears around it and speech bubbles with notes titled 'Data Problem'. The surrounding gears, clockwise from bottom left, say 'Accessibility', 'Trust', 'Data Breach', 'Ambiguity', 'Ownership', 'Duplication', 'System Failure', and 'Manual Manipulation'. The speech bubbles notes, clockwise from bottom left, say 'Value-Add: How do I translate business needs to data capabilities?', 'Practice Organization: How do I organize resources and roles assignment challenges?', 'Platform: How do I organize data flows with no conceptual view of the environment?', and 'Break Down Silos: How do I break down silos?'
      I can’t access the data.
      I don’t trust the data in the report.
      It takes too long to get to the data for decision making
      • Lack of data-centric leadership results in downstream issues: integration, quality, accessibility
      • The organization’s data is too complex to manage without a cohesive plan.
      • The complex nature of the data and a lack of understanding leads to de-scoping delivery of data services that does not meet business needs or add value.
      • Poorly designed practice and siloed platforms result in an initiative that is lengthy, costly, fizzles out, does not deliver business value, and ends up being considered a failure.

      Complication – Data Initiative Fizzles Out

      • Data problem: When the data problem is diagnosed the organization adopts a tactical approach.
      • Confirmation bias: Subject matter experts (SME) are hired to resolve the poorly defined problem, but the success of the SME is impacted by lack of architecture, technology, and organizational alignment.
      • Still no value: the selected tactical approach does not provide a solid foundation or solve your data problem.
      • Strategy for sake of strategy: Implementing a strategic approach for sake of being strategic but this becomes overwhelming.
      • Fall back to tactical and operational: The data services are now potentially exposed and vulnerable, which strains business continuity and increases data debt.
      • Increased complexity and risk: Data silos, poor understanding, and high complexity result in an unmanageable data environment.
      Flowchart beginning with 'Data Symptom Exhibited' and 'Data Problem Diagnosed', then splitting into two paths 'Solve Data Problem as a point solution' or 'Attempt Strategic approach without culture, capacity, and business leadership'. Each approach ends with 'Data too complex, and initiative fizzles out...' and cycles back to the beginning.
      Use the road-tested patterns and frameworks in our blueprint to break the perpetual data solution cycle. Focus on the value that a data and analytics platform will bring rather than focusing on the data problems alone.

      Build Your Data Practice and Platform

      Bring Your Data Strategy to Life

      Logo for Info-Tech.
      Logo for #iTRG.
      CONVENTIONAL WISDOM

      Attempting to Solve Your Data Problems

      DATA SYMPTOM EXHIBITED

      Mismatch report, data quality issue, or similar symptom of a data problem.

      DATA PROBLEM DIAGNOSED

      Data expert identifies it as a data problem.

      COMPLEX STRATEGIC APPROACH ATTEMPTED

      Recognized need to attempt it strategically, but don't have capacity or culture to execute.

      Cycle diagram titled 'Data Problems' with numbers connected to surrounding steps, and a break after Step 3 where one can 'BREAK THE CYCLE'. In the middle are a list of data problems: 'Accessibility’, ‘Data Breach', 'Manual Manipulation', 'System Failure', 'Ambiguity', 'Duplication', 'Ownership', and 'Trust'.
      SOLUTION FAILS

      The tactical solution fails to solve the root cause of the data problem, and the data symptoms persist.

      TACTICAL SOLUTION FALLBACK

      A quick and dirty solution is attempted in order to fix the data problem.

      THE COMPLEX APPROACH FIZZLES OUT

      Attempted strategic approach takes too long, fizzles out.

      BREAK THE CYCLE

      Solving Your Data Problems

      1. DEFINE YOUR DATA REQUIREMENTS Incorporate a Business to Data Approach by utilizing Info-Tech's business capability templates for identifying data needs. BUSINESS-ALIGNED DATA REQUIREMENTS
      2. CONDUCT YOUR DATA DISCOVERY Understand the data behind your business problem. Identify the required data capabilities and domains as required by your business processes. RECOMMENDED DATA CAPABILITIES
      3. DESIGN YOUR DATA PRACTICES Build your custom data practices based on the predefined reusable models. CUSTOMIZED DATA PRACTICE
      4. ARCHITECT YOUR DATA PLATFORM Build your custom data platform based on the redefined reusable architecture patterns. CUSTOMIZED DATA PLATFORM
      CONTINUOUS PHASE: ROADMAP, SPONSORSHIP FEEDBACK AND DELIVERY

      Develop a roadmap to establish the practice and implement the architecture as designed. Ensure continuous alignment of the practice and architecture with the business landscape.

      Phase-by-Phase Approach to Build Your Data Practice and Platform

      Flowchart detailing the path to take through the four phases of this blueprint beginning with the 'Inputs' and 'People' involved and incorporating 'Deliverables' along the way. Phase-by-Phase Approach
      • Phase 1: Step 1 – Define Your Data Requirement
      • Phase 1: Step 2 – Conduct Your Data Discovery
      • Phase 2 – Design Your Data Practice
      • Phase 3 – Architect Your Data Platform

      Measure value when building your data practice and platform

      Sample Data Management Metrics

      Lists of data management metrics in different categories.

      • Refine the metrics for the overall Data Management practice and every initiative therein.
      • Refine the metrics at each platform and practice component to show business value against implementation effort.

      Understand and Build Data Culture

      See your Info-Tech Account Representative for more details on our Data Culture Diagnostic

      Only 14.29% of Transportation and Logistics respondents agree BI and Analytics Process and Technology are sufficient What is a diagnostic?

      Our diagnostics are the simplest way to collect the data you need, turn it into actionable insights, and communicate with stakeholders across the organization.

      52.54% of respondents from the healthcare industry are unaware of their organization’s data security policy
      Ask the Right Questions

      Use our low-effort surveys to get the data you need from stakeholders across the organization.

      Use Our Diagnostic Engine

      Our diagnostic engine does all the heavy lifting and analysis, turning your data into usable information.

      Communicate & Take Action

      Wow your executives with the incredible insights you've uncovered. Then, get to action: make IT better.

      On average only 40% agree that they have the reporting when needed


      (Source: Info-Tech’s Data Culture Diagnostic, 53 Organizations, 3138 Responses)

      35% of respondents feel that a governance body is in place looking at strategic data

      Build a Data-Driven Strategy Using Info-Tech Diagnostic Programs

      Make informed IT decisions by starting your diagnostic program today. Your account manager is waiting to help you.
      Sample of Info-Tech's 'Data Culture Scorecard'.

      Use Our Predefined Data and Analytics Patterns to Build Your DnA Landscape

      Walking through a book of architecture building plans with a personal guide is cheaper and faster than employing an architect to build and design your home

      Two books titled 'The Everything Homebuilding Book' and 'Architecture 101'. An open book with a finger pointing to a diagram.

      The first step is to align business strategy with data strategy and then start building your data practice and data platform

      Flowchart starting with business strategy focuses, then to data strategy focuses, and eventually to 'Data Metrics'.

      Insights

      The true value of data comes from defining intentional relationships between the business and the data through a well-thought-out data platform and practice.

      • Phase 1
        • Some organizations are low maturity so using the traditional Capability Maturity Model Integration (CMMI) would not make sense. A great alternative is to leverage existing models and methodologies to get going off the bat.
        • The Data Strategy is an input into the platform and practice. This is considered the Why; Data Practice and Platform is the How.
      • Phase 2
        • Info-Tech’s approach is business-goal driven and it leverages patterns, which enable the implementation of critical and foundational components and subsequently facilitates the evolution and development of the practice over time.
        • Systems should not be designed in isolation. Cross-functional collaboration throughout the design is critical to ensure all types of issues are revealed early. Otherwise, crucial tests are omitted, deployments fail, and end-users are dissatisfied.
      • Phase 3
        • Build your conceptual data architecture based on well-thought-out formulated patterns that align with your organization’s needs and environment.
        • Functional needs often take precedence over quality architecture. Quality must be baked into design, execution, and decision-making practices to ensure the right trade-offs are made.

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      Guided Implementation

      Workshop

      Consulting

      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful." "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track." "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place." "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks used throughout all four options

      Info-Tech’s Methodology for Building Your Data Practice and Platform

      Phase 1 –
      Define Your Data Requirements and Conduct Your Data Discovery
      Phase 2 –
      Design Your Data Practices
      Phase 3 –
      Architect Your Data Platform
      Phase Steps
      1. Identify your top initiatives
      2. Map your data initiatives to data capabilities
      1. Understand the practices value statement
      2. Review the Info-Tech practice pattern
      3. Initiate your practice design and setup
      1. Identify your data component
      2. Refine your data platform architecture
      3. Design your data platform
      4. Identify your new components and capabilities
      5. Initiative platform build and rollout
      Phase Outcomes Business-aligned data initiatives and capabilities that address data challenges and realize business strategic objectives Comprehensive data practice design based on the required business and data capabilities Data platform design based on Info-Tech data architecture reference pattern and prioritized data initiatives and capabilities

      Data Platform and Practice Implementation Plan

      Example timeline for data platform and practice implementation plan with 'Fiscal Years' across the top, and below they're broken down into quarters. Along the left side 'Phase 1: Step 1...', 'Phase 1: Step 2...', 'Phase 2...' and 'Phase 3'. Tasks are mapped onto the timeline in each phase with a short explanation.

      Workshop Overview

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889
      Info-Tech’s Workshop support for Build Your Data Practice and Platform. 'Build Your Data Practice and Platform' slide from earlier.
      Workshop

      "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place."

      Workshop 1

      Data Needs and Discovery

      Workshop 2

      Data Practice Design

      Workshop 3

      Data Platform Design

      Workshop 1:
      Data Needs and Discovery

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889
      Day 1 Day 2 Day 3 Day 4
      Establish Business Context and Value
      Identify Your Top Initiatives
      Analyze Data Challenges
      Map Data Capability
      Activities

      1.1 Understand/confirm your organization’s strategic goals

      1.2 Classify the strategic goals and map to business drivers

      1.3 Identify the business capabilities that the strategy focus is on

      1.4 Identify the business processes realizing the strategy

      2.1 Highlight data-related outcomes /goals to realize to fulfill the business goal

      2.2 Map business data initiatives to the business strategic goals

      2.3 Prioritize Data initiatives

      3.1 Understand data management capabilities and framework

      3.2 Classify business data requirements using Info-Tech’s classification approach

      3.3 Highlight data challenges in your current environment

      4.1 Map data challenges to Info-Tech data challenges

      4.2 Review Info-Tech data capabilities based on prioritized initiative

      4.3 Discuss Data Platform and Practice Next Steps

      Deliverables
      • Business context and strategic drivers
      • Prioritized business capabilities and processes
      • Data Culture Survey results analysis
      • High-value business-aligned data initiative
      • List of data challenges preventing data maturation with the organization
      • Required data capabilities
      • Data platform and practice – plan
      • Initialized data management RACI
      Participants Business stakeholder, Business leader Business Subject Matter Expert, Data IT sponsor (CIO), Head of Data, Data Architect Business stakeholder, Business leader Business Subject Matter Expert, Data IT sponsor (CIO), Head of Data, Data Architect Data experts, Business Subject Matter Expert, Head of Data, Data Architect Data experts, Business Subject Matter Expert, Head of Data, Data Architect

      Workshop 2:
      Data Practice Design

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889
      Day 1 Day 2 Day 3 Day 4
      Plan Your Data Practices
      Design Your Data Practices 1
      Design Your Data Practices 2
      Design Your Data Practices 3
      Activities

      Prerequisite: Business context, business data requirement, and data capabilities

      1.1 Understand data practice framework

      1.2 Define your practice implementation approach

      1.3 Review and update data management RACI

      2.1 Understand Info-Tech data practice patterns for each prioritized practice

      2.2 Define your practice setup for each prioritized practice

      2.3 Highlight critical processes for each practice

      3.1 Understand Info-Tech data practice patterns for each prioritized practice

      3.2 Define your practice setup for each prioritized practice

      3.3 Highlight critical processes for each practice

      4.1 Understand Info-Tech data practice patterns for each prioritized practice

      4.2 Define your practice setup for each prioritized practice

      4.3 Highlight critical processes for each practice

      4.4 Discuss data platform and practice next steps

      Deliverables
      • Data practice implementation approach
      • Data management RACI
      • Data practice setup pattern for your organization
      • Data practice process pattern for your organization
      • Data practice setup pattern for your organization
      • Data practice process pattern for your organization
      • Data practice setup pattern for your organization
      • Data practice process pattern for your organization
      • Data platform and practice – plan
      Participants Data experts, Business Subject Matter Expert, Head of Data, Data Architect Data experts, Business Subject Matter Expert, Head of Data, Data Architect Data experts, Business Subject Matter Expert, Head of Data, Data Architect Data experts, Business Subject Matter Expert, Head of Data, Data Architect

      Workshop 3:
      Data Platform Design

      Contact your account representative for more information.
      workshops@infotech.com 1-888-670-8889
      Day 1Day 2Day 3Day 4
      Data Platform Overview
      Update Data Platform Reference Architecture
      Design Your Data Platform
      Design Your Data Practices 4
      Activities

      Prerequisite: Business context, business data requirement, and data capabilities

      1.1 Understand data platform framework and data capabilities

      1.2 Understand key data architecture principles and best practices

      1.3 Shortlist data platform patterns

      2.1 Map and identify data capabilities to data platform components

      2.2 Build data platform architecture using Info-Tech data platform reference architecture

      2.3 Highlight critical processes for each practice

      3.1 Design your target data platform using Info-Tech’s data platform template

      3.2 Identify new capabilities and components in your platform design

      4.1 Identify new capabilities and component in your platform design

      4.2 Discuss data platform initiatives

      Deliverables
      • Shortlisted data platform patterns
      • Data platform reference architecture for your organization
      • Data platform design for your organization
      • Data platform plan
      ParticipantsData experts, Business Subject Matter Expert, Head of Data, Data ArchitectData experts, Business Subject Matter Expert, Head of Data, Data ArchitectData experts, Business Subject Matter Expert, Head of Data, Data ArchitectData experts, Business Subject Matter Expert, Head of Data, Data Architect

      Build Your Data Practice and Platform

      Phase 1

      Phase 1: Step 1 – Define Your Data Requirements
      Phase 1: Step 2 – Conduct Your Data Discovery

      Phase 1

      1.1 Define Your Data Requirements
      1.2 Conduct Your Data Discovery

      Phase 2 Phase 3

      Phase 1: Step 1 – Define Your Data Requirements will walk you through the following activities:

      • Confirm the organizational strategic goals, business drivers, business capabilities, and processes driving the Data Practice and Platform effort.
      • Identify the data related outcomes, goals, and ideal environment needed to fulfill the business goals.

      This phase involves the following participants:

      A blend of business leaders and business SMEs together with the Data Strategy team.

      Phase 1: Step 2 – Conduct Your Data Discovery will walk you through the following activities:

      • Identify and highlight the data challenges faced in achieving the desired outcome.
      • Map the data challenges to the data capabilities required to realize the desired data outcome.

      This phase involves the following participants:

      Key personnel from IT/Data team: (Data Architect, Data Engineers, Head of Head of Reporting and Analytics)

      Cost-Optimize Your Security Budget

      • Buy Link or Shortcode: {j2store}250|cart{/j2store}
      • member rating overall impact: 9.0/10 Overall Impact
      • member rating average dollars saved: $2,078 Average $ Saved
      • member rating average days saved: 2 Average Days Saved
      • Parent Category Name: Security Strategy & Budgeting
      • Parent Category Link: /security-strategy-and-budgeting
      • The security budget has been slashed and the team needs to do more with less.
      • Mitigating risk is still the top priority, only now we need to reassess effectiveness and efficiency to ensure we are getting the greatest level of protection for the least amount of money.

      Our Advice

      Critical Insight

      A cost-optimized security budget is one that has the greatest impact on risk for the least amount of money spent.

      Impact and Result

      • Focus on business needs and related risks. Review the risk-reduction efficacy of your people, processes, and technology and justify what can be cut and what must stay.
      • Info-Tech will guide you through this process, and by the end of this blueprint you will have a cost-optimized security budget and an executive presentation to explain your revised spending.

      Cost-Optimize Your Security Budget Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should cost-optimize your security budget, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Cost-optimize your technology and managed services

      This phase will help you assess the efficacy of your current technology and service providers.

      • Threat and Risk Assessment Tool
      • In-House vs. Outsourcing Decision-Making Tool

      2. Cost-optimize your staffing

      This phase will help you assess if layoffs are necessary.

      • Security Employee Layoff Selection Tool

      3. Cost-optimize your security strategy

      This phase will help you revise the pending process-based initiatives in your security strategy.

      • Security Cost Optimization Workbook
      • Security Cost Optimization Executive Presentation
      [infographic]

      Enable Omnichannel Commerce That Delights Your Customers

      • Buy Link or Shortcode: {j2store}534|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: $17,249 Average $ Saved
      • member rating average days saved: 7 Average Days Saved
      • Parent Category Name: Customer Relationship Management
      • Parent Category Link: /customer-relationship-management
      • Today’s customers expect to be able to transact with you in the channels of their choice. The proliferation of e-commerce, innovations in brick-and-mortar retail, and developments in mobile commerce and social media selling mean that IT organizations are managing added complexity in drafting a strategy for commerce enablement.
      • The right technology stack is critical in order to support world-class e-commerce and brick-and-mortar interactions with customers.

      Our Advice

      Critical Insight

      • Support the right transactional channels for the right customers: there is no “one-size-fits-all” approach to commerce enablement – understand your customers to drive selection of the right transactional channels.
      • Don’t assume that “traditional” commerce channels have stagnated: IoT, customer analytics, and blended retail are reinvigorating brick-and-mortar selling.
      • Don’t buy best-of-breed; buy best-for-you. Base commerce vendor selection on your requirements and use cases, not on the vendor’s overall performance.

      Impact and Result

      • Leverage Info-Tech’s proven, road-tested approach to using personas and scenarios to build strong business drivers for your commerce strategy.
      • Before selecting and deploying technology solutions, create a cohesive channel matrix outlining which channels your organization will support with transactional capabilities.
      • Understand evolving trends in the commerce solution space, such as AI-driven product recommendations and integration with other essential enterprise applications (i.e. CRM and marketing automation platforms).
      • Understand and apply operational best practices such as content optimization and dynamic personalization to improve the conversion rate via your e-commerce channels.

      Enable Omnichannel Commerce That Delights Your Customers Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Enable Omnichannel Commerce Deck – A deck outlining the importance of creating a cohesive omnichannel framework to improve your customer experience.

      E-commerce channels have proliferated, and traditional brick-and-mortar commerce is undergoing reinvention. In order to provide your customers with a strong experience, it's imperative to create a strategy – and to deploy the right enabling technologies – that allow for robust multi-channel commerce. This storyboard provides a concise overview of how to do just that.

      • Enable Omnichannel Commerce That Delights Your Customers – Phases 1-2

      2. Create Personas to Drive Omnichannel Requirements Template – A template to identify key customer personas for e-commerce and other channels.

      Customer personas are archetypal representations of your key audience segments. This template (and populated examples) will help you construct personas for your omnichannel commerce project.

      • Create Personas to Drive Omnichannel Requirements Template
      [infographic]

      Further reading

      Enable Omnichannel Commerce That Delights Your Customers

      Create a cohesive, omnichannel framework that supports the right transactions through the right channels for the right customers.

      Analyst Perspective

      A clearly outlined commerce strategy is a necessary component of a broader customer experience strategy.

      This is a picture of Ben Dickie, Research Lead, Research – Applications at Info-Tech Research Group

      Ben Dickie
      Research Lead, Research – Applications
      Info-Tech Research Group

      “Your commerce strategy is where the rubber hits the road, converting your prospects into paying customers. To maximize revenue (and provide a great customer experience), it’s essential to have a clearly defined commerce strategy in place.

      A strong commerce strategy seeks to understand your target customer personas and commerce journey maps and pair these with the right channels and enabling technologies. There is not a “one-size-fits-all” approach to selecting the right commerce channels: while many organizations are making a heavy push into e-commerce and mobile commerce, others are seeking to differentiate themselves by innovating in traditional brick-and-mortar sales. Hybrid channel design now dominates many commerce strategies – using a blend of e-commerce and other channels to deliver the best-possible customer experience.

      IT leaders must work with the business to create a succinct commerce strategy that defines personas and scenarios, outlines the right channel matrix, and puts in place the right enabling technologies (for example, point-of-sale and e-commerce platforms).”

      Stop! Are you ready for this project?

      This Research Is Designed For:

      • IT leaders and business analysts supporting their commercial and marketing organizations in developing and executing a technology enablement strategy for e-commerce or brick-and-mortar commerce.
      • Any organization looking to develop a persona-based approach to identifying the right channels for their commerce strategy.

      This Research Will Help You:

      • Identify key personas and customer journeys for a brick-and-mortar and/or e-commerce strategy.
      • Select the right channels for your commerce strategy and build a commerce channel matrix to codify the results.
      • Review the “art of the possible” and new developments in brick-and-mortar and e-commerce execution.

      This Research Will Also Assist:

      • Sales managers, brand managers, and any marketing professional looking to build a cohesive commerce strategy.
      • E-commerce or POS project teams or working groups tasked with managing an RFP process for vendor selection.

      This Research Will Help Them:

      • Build a persona-centric commerce strategy.
      • Understand key technology trends in the brick-and-mortar and e-commerce space.

      Executive Summary

      Your Challenge

      Today’s customers expect to be able to transact with you in the channels of their choice.

      The proliferation of e-commerce, innovations in brick-and-mortar retail, and developments in mobile commerce and social media selling mean that IT organizations are managing added complexity in drafting a strategy for commerce enablement.

      The right technology stack is critical to support world-class e-commerce and brick-and-mortar interactions with customers.

      Common Obstacles

      Many organizations do not define strong, customer-centric drivers for dictating which channels they should be investing in for transactional capabilities.

      As many retailers look to move shopping experiences online during the pandemic, the impetus for having a strong e-commerce suite has markedly increased. The proliferation of commerce vendors has made it difficult to identify and shortlist the right solution, while the pandemic has also highlighted the importance of adopting new vendors quickly and efficiently: companies need to understand the top players in different commerce market landscapes.

      IT is receiving a growing number of commerce platform requests and must be prepared to speak intelligently about requirements and the “art of the possible.”

      Info-Tech’s Approach

      • Leverage Info-Tech’s proven, road-tested approach to using personas and scenarios to build strong business drivers for your commerce strategy.
      • Before selecting and deploying technology solutions, create a cohesive channel matrix outlining which channels your organization will support with transactional capabilities.
      • Understand evolving trends in the commerce solution space, such as AI-driven product recommendations and integration with other essential enterprise applications (i.e. customer relationship management [CRM] and marketing automation platforms).
      • Understand and apply operational best practices such as content optimization and dynamic personalization to improve the conversion rate via your e-commerce channels.

      Info-Tech Insight

      • Support the right transactional channels for the right customers: there is no “one-size-fits-all” approach to commerce enablement – understand your customers to drive selection of the right transactional channels.
      • Don’t assume that “traditional” commerce channels have stagnated: IoT, customer analytics, and blended retail are reinvigorating brick-and-mortar selling.
      • Don’t buy best-of-breed; buy best-for-you: base commerce vendor selection on your requirements and use cases, not on the vendor’s overall performance.

      A strong commerce strategy is an essential component of a savvy approach to customer experience management

      A commerce strategy outlines an organization’s approach to selling its products and services. A strong commerce strategy identifies target customers’ personas, commerce journeys that the organization wants to support, and the channels that the organization will use to transact with customers.

      Many commerce strategies encompass two distinct but complementary branches: a commerce strategy for transacting through traditional channels and an e-commerce strategy. While the latter often receives more attention from IT, it still falls on IT leaders to provide the appropriate enabling technologies to support traditional brick-and-mortar channels as well. Traditional channels have also undergone a digital renaissance in recent years, with forward-looking companies capitalizing on new technology to enhance customer experiences in their stores.

      Traditional Channels

      • Physical Stores (Brick and Mortar)
      • Kiosks or Pop-Up Stores
      • Telesales
      • Mail Orders
      • EDI Transactions

      E-Commerce Channels

      • E-Commerce Websites
      • Mobile Commerce Apps
      • Embedded Social Shopping
      • Customer Portals
      • Configure Price Quote Tool Sets (CPQ)
      • Hybrid Retail

      Info-Tech Insight

      To better serve their customers, many companies position themselves as “click-and-mortar” shops – allowing customers to transact at a store or online.

      Customers’ expectations are on the rise: meet them!

      Today’s consumers expect speed, convenience, and tailored experiences at every stage of the customer lifecycle. Successful organizations strive to support these expectations.

      58%
      of retail customers admitted that their expectations now are higher than they were a year ago (FinancesOnline).

      70%
      of consumers between the ages of 18 and 34 have increasing customer expectations year after year (FinancesOnline).

      69%
      of consumers now expect store associates to be armed with a mobile device to deliver value-added services, such as looking up product information and checking inventory (V12).

      73%
      of support leaders agree that customer expectations are increasing, but only…

      42%
      of support leaders are confident that they’re actually meeting those expectations.

      How can you be sure that you are meeting your customers’ expectations?

      1. Offer more personalization throughout the entire customer journey
      2. Practice quality customer service – ensure staff have up-to-date knowledge and offer quick resolution time for complaints
      3. Focus on offering low-effort experiences and easy-to-use platforms (i.e. “one-click buying”)
      4. Ensure your products and services perform well and do what they’re meant to do
      5. Ensure omnichannel availability – 9 in 10 consumers want a seamless omnichannel experience

      Info-Tech Insight

      Customers expect to interact with organizations through the channels of their choice. Now more than ever, you must enable your organization to provide tailored commerce and transactional experiences.

      Omnichannel commerce is the way of the future

      Create a strategy that embraces this reality with the right tools!

      Get ahead of the competition by doing omnichannel right! Devise a strategy that allows you to create and maintain a consistent, seamless commerce experience by optimizing operations with an omnichannel framework. Customers want to interact with you on their own terms, and it falls to IT to ensure that applications are in place to support and manage both traditional and e-commerce channels. There must also be consistency of copy, collateral, offers, and pricing between commerce channels.

      71%
      of consumers want a consistent experience across all channels, but only…

      29%
      say that they actually get it.

      (Source: Business 2 Community, 2020)

      Omnichannel is a “multichannel approach that aims to provide customers with a personalized, integrated, and seamless shopping experience across diverse touchpoints and devices.”
      Source: RingCentral, 2021

      IT is responsible for providing technology enablement of the commerce strategy: e-commerce platforms are a cornerstone

      An e-commerce platform is an enterprise application that provides end-to-end capabilities for allowing customers to purchase products or services from your company via an online channel (e.g. a traditional website, a mobile application, or an embedded link in a social media post). Modern e-commerce platforms are essential for delivering a frictionless customer journey when it comes to purchasing online.

      $6.388
      trillion dollars worth of sales will be conducted online by 2024 (eMarketer, 14 Jan. 2021).

      44%
      of all e-commerce transactions are expected to be completed via a mobile device by 2024 (Insider).

      21.8%
      of all sales will be made from online purchases by 2024 (eMarketer, 14 Jan. 2021).

      Strong E-Commerce Platforms Enable a Wide Range of Functional Areas:

      • Product Catalog Management
      • Web Content Delivery
      • Product Search Engine
      • Inventory Management
      • Shopping Cart Management
      • Discount and Coupon Management
      • Return Management and Reverse Logistics
      • Dynamic Personalization
      • Dynamic Promotions
      • Predictive Re-Targeting
      • Predictive Product Recommendations
      • Transaction Processing
      • Compliance Management
      • Commerce Workflow Management
      • Loyalty Program Management
      • Reporting and Analytics

      An e-commerce solution boosts the effectiveness and efficiency of your operations and drives top-line growth

      Take time to learn the capabilities of modern e-commerce applications. Understanding the “art of the possible” will help you to get the most out of your e-commerce platform.

      An e-commerce platform helps marketers and sales staff in three primary ways:

      1. It allows the organization to effectively and efficiently operate e-commerce operations at scale.
      2. It allows commercial staff to have a single system for managing and monitoring all commercial activity through online channels.
      3. It allows the organization to improve the customer-facing e-commerce experience, boosting conversions and top-line sales.

      A dedicated e-commerce platform improves the efficiency of customer-commerce operations

      • Workflow automation reduces the amount of time spent executing dynamic e-commerce campaigns.
      • The use of internal or third-party data increases conversion effectiveness from customer databases across the organization.

      Info-Tech Insight

      A strong e-commerce provides marketers with the data they need to produce actionable insights about their customers.

      Case Study

      INDUSTRY - Retail
      SOURCE - Salesforce (a)

      PetSmart improves customer experience by leveraging a new commerce platform in the Salesforce ecosystem

      PetSmart

      PetSmart is a leading retailer of pet products, with a heavy footprint across North America. Historically, PetSmart was a brick-and-mortar retailer, but it has placed a heavy emphasis on being a true multi-channel “click-and-mortar” retailer to ensure it maintains relevance against competitors like Amazon.

      E-Commerce Overhaul Initiative

      To improve its e-commerce capabilities, PetSmart recognized that it needed to consolidate to a single, unified e-commerce platform to realize a 360-degree view of its customers. A new platform was also required to power dynamic and engaging experiences, with appropriate product recommendations and tailored content. To pursue this initiative, the company settled on Salesforce.com’s Commerce Cloud product after an exhaustive requirements definition effort and rigorous vendor selection approach.

      Results

      After platform implementation, PetSmart was able to effortlessly handle the massive transaction volumes associated with Black Friday and Cyber Monday and deliver 1:1 experiences that boosted conversion rates.

      PetSmart standardized on the Commerce Cloud from Salesforce to great effect.

      This is an image of the journey from Discover & Engage to Retain & Advocate.

      Case Study

      Icebreaker exceeds customer expectations by using AI to power product recommendations

      INDUSTRY - Retail
      SOURCE - Salesforce (b)

      Icebreaker

      Icebreaker is a leading outerwear and lifestyle clothing company, operating six global websites and owning over 5,000 stores across 50 countries. Icebreaker is focused on providing its shoppers with accurate, real-time product suggestions to ensure it remains relevant in an increasingly competitive online market.

      E-Commerce Overhaul Initiative

      To improve its e-commerce capabilities, Icebreaker recognized that it needed to adopt a predictive recommendation engine that would offer its customers a more personalized shopping experience. This new system would need to leverage relevant data to provide both known and anonymous shoppers with product suggestions that are of interest to them. To pursue this initiative, Icebreaker settled on using Salesforce.com’s Commerce Cloud Einstein, a fully integrated AI.

      Results

      After integrating Commerce Cloud Einstein on all its global sites, Icebreaker was able to cross-sell and up-sell its merchandise more effectively by providing its shoppers with accurate product recommendations, ultimately increasing average order value.

      IT must also provide technology enablement for other channels, such as point-of-sale systems for brick-and-mortar

      Point-of-sale systems are the “real world” complement to e-commerce platforms. They provide functional capabilities for selling products in a physical store, including basic inventory management, cash register management, payment processing, and retail analytics. Many firms struggle with legacy POS environments that inhibit a modern customer experience.

      $27.338
      trillion dollars in retail sales are expected to be made globally in 2022 (eMarketer, 2022).

      84%
      of consumers believe that retailers should be doing more to integrate their online and offline channels (Invoca).

      39%
      of consumers are unlikely or very unlikely to visit a retailer’s store if the online store doesn’t provide physical store inventory information (V12).

      Strong Point-of-Sale Platforms Enable a Wide Range of Functional Areas:

      • Product Catalog Management
      • Discount Management
      • Coupon Management and Administration
      • Cash Management
      • Cash Register Reconciliation
      • Product Identification (Barcode Management)
      • Payment Processing
      • Compliance Management
      • Basic Inventory Management
      • Commerce Workflow Management
      • Exception Reporting and Overrides
      • Loyalty Program Management
      • Reporting and Analytics

      E-commerce and POS don’t live in isolation

      They’re key components of a well-oiled customer experience ecosystem!

      Integrate commerce solutions with other customer experience applications – and with ERP or logistics systems – to handoff transactions for order fulfilment.

      Having a customer master database – the central place where all up-to-the-minute data on a customer profile is stored – is essential for traditional and e-commerce success. Typically, the POS or e-commerce platform is not the system of record for the master customer profile: this information lives in a CRM platform or customer data warehouse. Conceptually, this system is at the center of the customer-experience ecosystem.

      Strong POS and e-commerce solutions orchestrate transactions but typically do not do the heavy lifting in terms of order fulfilment, shipping logistics, economic inventory management, and reverse logistics (returns). In an enterprise-grade environment, these activities are executed by an enterprise resource planning (ERP) solution – integrating your commerce systems with a back-end ERP solution is a crucial step from an application architecture point of view.

      This is an example of a customer experience ecosystem.  Core Apps (CRM, ERP): MMS Suite; E-Commerce; POS; Web CMS; Data Marts/BI Tools; Social Media Platforms

      Case Study

      INDUSTRY - Retail
      SOURCES - Amazon, n.d. CNET, 2020

      Amazon is creating a hybrid omnichannel experience for retail by introducing innovative brick-and-mortar stores

      Amazon

      Amazon began as an online retailer of books in the mid-1990s, and rapidly expanded its product portfolio to nearly every category imaginable. Often hailed as the foremost success story in online commerce, the firm has driven customer loyalty via consistently strong product recommendations and a well-designed site.

      Bringing Physical Retail Into the Digital Age

      Beginning in 2016 (and expanding in 2018), Amazon introduced Amazon Go, a next-generation grocery retailer, to the Seattle market. While most firms that pursue an e-commerce strategy traditionally come from a brick-and-mortar background, Amazon upended the usual narrative: the world’s largest online retailer opening physical stores to become a true omnichannel, “click-and-mortar” vendor. From the get-go, Amazon Go focused on innovating the physical retail experience – using cameras, IoT capabilities, and mobile technologies to offer “checkout-free” virtual shopping carts that automatically know what products customers take off the shelves and bill their Amazon accounts accordingly.

      Results

      Amazon received a variety of industry and press accolades for re-inventing the physical store experience and it now owns and operates seven separate store brands, with more still on the horizon.

      Case Study

      INDUSTRY - Retail
      SOURCES - Glossy, 2020

      Old Navy

      Old Navy is a clothing and accessories retail company that owns and operates over 1,200 stores across North America and China. Typically, Old Navy has relied on using traditional marketing approaches, but recently it has shifted to producing more digitally focused campaigns to drive revenue.

      Bringing Physical Retail Into the Digital Age

      To overcome pandemic-related difficulties, including temporary store closures, Old Navy knew that it had to have strong holiday sales in 2020. With the goal of stimulating retail sales growth and maximizing its pre-existing omnichannel capabilities, Old Navy decided to focus more of its holiday campaign efforts online than in years past. With this campaign centered on connected TV platforms, such as Hulu, and social media channels including Facebook, Instagram, and TikTok, Old Navy was able to take a more unique, fun, and good-humored approach to marketing.

      Results

      Old Navy’s digitally focused campaign was a success. When compared with third quarter sales figures from 2019, third quarter net sales for 2020 increased by 15% and comparable sales increased by 17%.

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      “Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

      Guided Implementation

      “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track.”

      Workshop

      “We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place.”

      Consulting

      “Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project.”

      Diagnostics and consistent frameworks used throughout all four options

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1 Phase 2 Phase 3 Phase 4 Phase 5

      Call #1: Scope requirements, objectives, and your specific challenges.

      Call #2: Assess current maturity.

      Call #4: Identify relationship between current initiatives and capabilities.

      Call #6: Identify strategy risks.

      Call #8: Identify and prioritize improvements.

      Call #3: Identify target-state capabilities.

      Call #5: Create initiative profiles.

      Call #7: Identify required budget.

      Call #9: Summarize results and plan next steps.

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is between 8 to 12 calls over the course of 4 to 6 months.

      Enable Omnichannel Commerce That Delights Your Customers – Project Overview

      1. Identify Critical Drivers for Your Omnichannel Commerce Strategy 2. Map Drivers to the Right Channels and Technologies
      Best Practice Toolkit

      1.1 Assess Personas and Scenarios

      1.2 Create Key Drivers and Metrics

      2.1 Build the Commerce Channel Matrix

      2.2 Review Technology and Trends Primer

      Guided Implementations
      • Validate customer personas.
      • Validate commerce scenarios.
      • Review key drivers and metrics.
      • Build the channel matrix.
      • Discuss technology and trends.
      Onsite Workshop

      Module 1:

      Module 2:

      Identify Critical Drivers for Your Omnichannel Commerce Strategy

      Map Drivers to the Right Channels and Technologies

      Phase 1 Outcome:

      Phase 2 Outcome:

      An initial shortlist of customer-centric drivers for your channel strategy and supporting metrics.

      A completed commerce channel matrix tailored to your organization, and a snapshot of enabling technologies and trends.

      Phase 1

      Identify Critical Drivers for Your Omnichannel Commerce Strategy

      1.1 Assess Personas and Scenarios

      1.2 Create Key Drivers and Metrics

      Enable Omnichannel Commerce That Delights Your Customers

      Step 1.1

      Assess Personas and Scenarios

      This step will walk you through the following activities:

      1.1.1 Build key customer personas for your commerce strategy.

      1.1.2 Create commerce scenarios (journey maps) that you need to enable.

      Identify Critical Drivers for Your Omnichannel Commerce Strategy

      This step involves the following participants:

      • Business stakeholders (Sales, Marketing)
      • IT project team

      Outcomes of this step:

      • Critical customer personas
      • Key traditional and e-commerce scenarios

      Use customer personas to picture who will be using your commerce channels and guide scenario design and key drivers

      What Are Personas?

      Personas are detailed descriptions of the targeted audience of your e-commerce presence. Effective personas:

      • Express and focus on the major needs and expectations of the most important user groups.
      • Give a clear picture of the typical user’s behavior.
      • Aid in uncovering universal features and functionality.
      • Describe real people with backgrounds, goals, and values.

      Source: Usability.gov, n.d.

      Why Are Personas Important?

      Personas help:

      • Focus the development of commerce platform features on the immediate needs of the intended audience.
      • Detail the level of customization needed to ensure content is valuable to the user.
      • Describe how users may behave when certain audio and visual stimulus are triggered from the website.
      • Outline the special design considerations required to meet user accessibility needs.

      Key Elements of a Persona:

      • Persona Group (e.g. executives)
      • Demographics (e.g. nationality, age, language spoken)
      • Purpose of Using Commerce Channels (e.g. product search versus ready to transact)
      • Typical Behaviors and Tendencies (e.g. goes to different websites when cannot find products in 20 seconds)
      • Technological Environment of User (e.g. devices, browsers, network connection)
      • Professional and Technical Skills and Experiences (e.g. knowledge of websites, area of expertise)

      Use Info-Tech’s guidelines to assist in the creation of personas

      How many personas should I create?

      The number of personas that should be created is based on the organizational coverage of your commerce strategy. Here are some questions you should ask:

      • Do the personas cover a majority of your revenues or product lines?
      • Is the number manageable for your project team to map out?

      How do I prioritize which personas to create?

      The identified personas should generate the most revenue – or provide a significant opportunity – for your business. Here are some questions that you should ask:

      • Are the personas prioritized based on the revenue they generate for the business?
      • Is the persona prioritization process considering both the present and future revenues the persona is generating?

      Sample: persona for e-commerce platform

      Example

      Persona quote: “After I call the company about the widget, I would usually go onto the company’s website and look at further details about the product. How am I supposed to do so when it is so hard to find the company’s website on everyday search engines, such as Google, Yahoo, or Bing?”

      Michael is a middle-aged manager working in the financial district. He wants to buy the company’s widgets for use in his home, but since he is distrusting of online shopping, he prefers to call the company’s call center first. Afterwards, if Michael is convinced by the call center representative, he will look at the company’s website for further research before making his purchase.

      Michael does not have a lot of free time on his hands, and tries to make his free time as relaxing as possible. Due to most of his work being client-facing, he is not in front of a computer most of the time during his work. As such, Michael does not consider himself to be skilled with technology. Once he makes the decision to purchase, Michael will conduct online transactions and pay most delivery costs due to his shortage of time.

      Needs:

      • Easy-to-find website and widget information.
      • Online purchasing and delivery services.
      • Answer to his questions about the widget.
      • To maintain contact post-purchase for easy future transactions.

      Info-Tech Tip

      The quote attached to a persona should be from actual quotes that your customers have used when you reviewed your voice of the customer (VoC) surveys or focus groups to drive home the impact of their issues with your company.

      1.1.1 Activity: Build personas for your key customers that you’ll need to support via traditional and e-commerce channels

      1 hour

      1. In two to four groups, list all the major, target customer personas that need to be built. In doing so, consider the people who interact with your e-commerce site (or other channels) most often.
      2. Build a demographic profile for each customer persona. Include information such as age, geographic location, occupation, and annual income.
      3. Augment the persona with a psychographic profile. Consider the goals and objectives of each customer persona and how these might inform buyer behaviors.
      4. Introduce your group’s personas to the entire group, in a round-robin fashion, as if you are introducing your persona at a party.
      5. Summarize the personas in a persona map. Rank your personas according to importance and remove any duplicates.
      6. Use Info-Tech’s Create Personas to Drive Omnichannel Requirements Template to assist.

      Info-Tech Insight

      Persona building is typically used for understanding the external customer; however, if you need to gain a better understanding of the organization’s internal customers (those who will be interacting with the e-commerce platform), personas can also be built for this purpose. Examples of useful internal personas are sales managers, brand managers, and customer service directors.

      1.1.1 Activity: Build personas for your key customers that you’ll need to support via traditional and e-commerce channels (continued)

      Input

      • Customer demographics and psychographics

      Output

      • List of prioritized customer personas

      Materials

      • Whiteboard
      • Markers

      Participants

      • Project team

      Build use-case scenarios to model the transactional customer journey and inform drivers for your commerce strategy

      A use-case scenario is a story or narrative that helps explore the set of interactions that a customer has with an organization. Scenario mapping will help identify key business and technology drivers as well as more granular functional requirements for POS or e-commerce platform selection.

      A GOOD SCENARIO…

      • Describes specific task(s) that need to be accomplished.
      • Describes user goals and motivations.
      • Describes interactions with a compelling but not overwhelming amount of detail.
      • Can be rough, as long as it provokes ideas and discussion.

      SCENARIOS ARE USED TO...

      • Provide a shared understanding about what a user might want to do and how they might want to do it.
      • Help construct the sequence of events that are necessary to address in your user interface(s).

      TO CREATE GOOD SCENARIOS…

      • Keep scenarios high level, not granular, in nature.
      • Identify as many scenarios as possible. If you’re time constrained, try to develop two to three key scenarios per persona.
      • Sketch each scenario out so that stakeholders understand the goal of the scenario.

      1.1.2 Exercise: Build commerce user scenarios to understand what you want your customers to do from a transactional viewpoint

      1 hour

      Example

      Simplified E-Commerce Workflow Purchase Products

      This image contains an example of a Simplified E-Commerce Workflow Purchase Products

      Step 1.2

      Create Key Drivers and Metrics

      This step will walk you through the following activities:

      • Create the business drivers you need to enable with your commerce strategy.
      • Enumerate metrics to track the efficacy of your commerce strategy.

      Identify Critical Drivers for Your Omnichannel Commerce Strategy

      This step involves the following participants:

      • Business stakeholders (Sales, Marketing)
      • IT project team

      Outcomes of this step:

      • Business drivers for the commerce strategy
      • Metrics and key performance indicators for the commerce strategy

      1.2 Finish elaboration of your scenarios and map them to your personas: identify core business drivers for commerce

      1.5 hours

      1. List all commerce scenarios required to satisfy the immediate needs of your personas.
        1. Does the use-case scenario address commonly felt user challenges?
        2. Can the scenario be used by those with changing behaviors and tendencies?
      2. Look for recurring themes in use-case scenarios (for example, increasing average transaction cost through better product recommendations) and identify business drivers: drivers are common thematic elements that can be found across multiple scenarios. These are the key principles for your commerce strategy.
      3. Prioritize your use cases by leveraging the priorities of your business drivers.

      Example

      This is an example of how step 1.2 can help you identify business drivers

      1.2 Finish elaboration of your scenarios and map them to your personas: identify core business drivers for commerce (continuation)

      Input

      • User personas

      Output

      • List of use cases
      • Alignment of use cases to business objectives

      Materials

      • Whiteboard
      • Markers

      Participants

      • Business Analyst
      • Developer
      • Designer

      Show the benefits of commerce solution deployment with metrics aimed at both overall efficacy and platform adoption

      The ROI and perceived value of the organization’s e-commerce and POS solutions will be a critical indication of the success of the suite’s selection and implementation.

      Commerce Strategy and Technology Adoption Metrics

      EXAMPLE METRICS

      Commerce Performance Metrics

      Average revenue per unique transaction

      Quantity and quality of commerce insights

      Aggregate revenue by channel

      Unique customers per channel

      Savings from automated processes

      Repeat customers per channel

      User Adoption and Business Feedback Metrics

      User satisfaction feedback

      User satisfaction survey with technology

      Business adoption rates

      Application overhead cost reduction

      Info-Tech Insight

      Even if e-commerce metrics are difficult to track right now, the implementation of a dedicated e-commerce platform brings access to valuable customer intelligence from data that was once kept in silos.

      Phase 2

      Map Drivers to the Right Channels and Technologies

      2.1 Build the Commerce Channel Matrix

      2.2 Review Technology and Trends Primer

      Enable Omnichannel Commerce That Delights Your Customers

      Step 2.1

      Build the Commerce Channel Matrix

      This step will walk you through the following activities:

      • Based on your business drivers, create a blended mix of e-commerce channels that will suit your organization’s and customers’ needs.

      Map Drivers to the Right Channels and Technologies

      This step involves the following participants:

      • Business stakeholders (Sales, Marketing)
      • IT project team

      Outcomes of this step:

      • Commerce channel map

      Pick the transactional channels that align with your customer personas and enable your target scenarios and drivers

      Traditional Channels

      E-Commerce Channels

      Hybrid Channels

      Physical stores (brick and mortar) are the mainstay of retailers selling tangible goods – some now also offer intangible service delivery.

      E-commerce websites as exemplified by services like Amazon are accessible by a browser and deliver both goods and services.

      Online ordering/in-store fulfilment is a model whereby customers can place orders online but pick the product up in store.

      Telesales allows customers to place orders over the phone. This channel has declined in favor of mobile commerce via smartphone apps.

      Mobile commerce allows customers to shop through a dedicated, native mobile application on a smartphone or tablet.

      IoT-enabled smart carts/bags allow customers to shop in store, but check-out payments are handled by a mobile application.

      Mail order allows customers to send (”snail”) mail orders. A related channel is fax orders. Both have diminished in favor of e-commerce.

      Social media embedded shopping allows customers to order products directly through services such as Facebook.

      Info-Tech Insight

      Your channel selections should be driven by customer personas and scenarios. For example, social media may be extensively employed by some persona types (i.e. millennials) but see limited adoption in other demographics or use cases (i.e. B2B).

      2.1 Activity: Build your commerce channel matrix

      30 minutes

      1. Inventory which transactional channels are currently used by your firm (segment by product lines if variation exists).
      2. Interview product leaders, sales leaders, and marketing managers to determine if channels support transactional capabilities or are used for marketing and service delivery.
      3. Review your customer personas, scenarios, and drivers and assess which of the channels you will use in the future to sell products and services. Document below.

      Example: Commerce Channel Map

      Product Line A Product Line B Product Line C
      Currently Used? Future Use? Currently Used? Future Use? Currently Used? Future Use?
      Store Yes Yes No No No No
      Kiosk Yes No No No No No
      E-Commerce Site/Portal No Yes Yes Yes Yes Yes
      Mobile App No No Yes Yes No Yes
      Embedded Social Yes Yes Yes Yes Yes Yes

      Input

      • Personas, scenarios, and driver

      Output

      • Channel map

      Materials

      • Whiteboard
      • Markers

      Participants

      • Project team

      Step 2.2

      Review Technology and Trends Primer

      This step will walk you through the following activities:

      • Review the scope of e-commerce and POS solutions and understand key drivers impacting e-commerce and traditional commerce.

      Map Drivers to the Right Channels and Technologies

      This step involves the following participants:

      • Business stakeholders (Sales, Marketing)
      • IT project team

      Outcomes of this step:

      • Understanding of key technologies
      • Understanding of key trends

      Application spotlight: e-commerce platforms

      How It Enables Your Strategy

      • Modern e-commerce platforms provide capabilities for end-to-end orchestration of online commerce experiences, from product site deployment to payment processing.
      • Some e-commerce platforms are purpose-built for business-to-business (B2B) commerce, emphasizing customer portals and EDI features. Other e-commerce vendors place more emphasis on business-to-consumer (B2C) capabilities, such as product catalog management and executing transactions at scale.
      • There has been an increasing degree of overlap between traditional web experience management solutions and the e-commerce market; for example, in 2018, Adobe acquired Magento to augment its overall web experience offering within Adobe Experience Manager.
      • E-commerce platforms typically fall short when it comes to order fulfilment and logistics; this piece of the puzzle is typically orchestrated via an ERP system or logistics management module.
      • This research provides a starting place for defining e-commerce requirements and selection artefacts.

      Key Trends

      • E-commerce vendors are rapidly supporting a variety of form factors and integration with other channels such as social media. Mobile is sufficiently popular that some vendors and industry commentators refer to it as “m-commerce” to differentiate app-based shopping experiences from those accessed through a traditional browser.
      • Hybrid commerce is driving more interplay between e-commerce solutions and POS.

      E-Commerce KPIs

      Strong e-commerce applications can improve:

      • Bounce Rates
      • Exit Rates
      • Lead Conversion Rates
      • Cart Abandonment Rates
      • Re-Targeting Efficacy
      • Average Cart Size
      • Average Cart Value
      • Customer Lifetime Value
      • Aggregate Reach/Impressions

      Familiarize yourself with the e-commerce market

      How it got here

      Initial Traction as the Dot-Com Era Came to Fruition

      Unlike some enterprise application markets, such as CRM, the e-commerce market appeared almost overnight during the mid-to-late nineties as the dot-com explosion fueled the need to have reliable solutions for executing transactions online.

      Early e-commerce solutions were less full-fledged suites than they were mediums for payment processing and basic product list management. PayPal and other services like Digital River were pioneers in the space, but their functionality was limited vis-à-vis tools such as web content management platforms, and their ability to amalgamate and analyze the data necessary for dynamic personalization and re-targeting was virtually non-existent.

      Rapidly Expanding Scope of Functional Capabilities as the Market Matured

      As marketers became more sophisticated and companies put an increased focus on customer experience and omnichannel interaction, the need arose for platforms that were significantly more feature rich than their early contemporaries. In this context, vendors such as Shopify and Demandware stepped into the limelight, offering far richer functionality and analytics than previous offerings, such as asset management, dynamic personalization, and the ability to re-target customers who abandoned their carts.

      As the market has matured, there has also been a series of acquisitions of some players (for example, Demandware by Salesforce) and IPOs of others (i.e. Shopify). Traditional payment-oriented services like PayPal still fill an important niche, while newer entrants like Square seek to disrupt both the e-commerce market and point-of-sale solutions to boot.

      Familiarize yourself with the e-commerce market

      Where it’s going

      Support for a Proliferation of Form Factors and Channels

      Modern e-commerce solutions are expanding the number of form factors (smartphones, tablets) they support via both responsive design and in-app capabilities. Many platforms now also support embedded purchasing options in non-owned channels (for example, social media). With the pandemic leading to a heightened affinity for online shopping, the importance of fully using these capabilities has been further emphasized.

      AI and Machine Learning

      E-commerce is another customer experience domain ripe for transformation via the potential of artificial intelligence. Machine learning algorithms are being used to enhance the effectiveness of dynamic personalization of product collateral, improve the accuracy of product recommendations, and allow for more effective re-targeting campaigns of customers who did not make a purchase.

      Merger of Online Commerce and Traditional Point-of-Sale

      Many e-commerce vendors – particularly the large players – are now going beyond traditional e-commerce and making plays into brick-and-mortar environments, offering point-of-sale capabilities and the ability to display product assets and customizations via augmented reality – truly blending the physical and virtual shopping experience.

      Emphasis on Integration with the Broader Customer Experience Ecosystem

      The big names in e-commerce recognize they don’t live on an island: out-of-the-box integrations with popular CRM, web experience, and marketing automation platforms have been increasing at a breakneck pace. Support for digital wallets has also become increasingly popular, with many vendors integrating contactless payment technology (i.e. Apple Pay) directly into their applications.

      E-Commerce Vendor Snapshot: Part 1

      Mid-Market E-Commerce Solutions

      This image contains the logos for the following Companies: Magento; Spryker; Bigcommerce; Woo Commerce; Shopify

      E-Commerce Vendor Snapshot: Part 2

      Large Enterprise and Full-Suite E-Commerce Platforms

      This image contains the logos for the following Companies: Salesforce commerce cloud; Oracle Commerce Cloud; Adobe Commerce Cloud; Sitecore; Sap Hybris Commerce

      Speak with category experts to dive deeper into the vendor landscape

      • Fact-based reviews of business software from IT professionals.
      • Product and category reports with state-of-the-art data visualization.
      • Top-tier data quality backed by a rigorous quality assurance process.
      • User-experience insight that reveals the intangibles of working with a vendor.

      Software Reviews is powered by Info-Tech

      Technology coverage is a priority for Info-Tech, and SoftwareReviews provides the most comprehensive unbiased data on today’s technology. The insights of our expert analysts provide unparalleled support to our members at every step of their buying journey.

      CLICK HERE to access SoftwareReviews Comprehensive software reviews to make better IT decisions.

      We collect and analyze the most detailed reviews on enterprise software from real users to give you an unprecedented view into the product and vendor before you buy.

      Evaluate software category leaders through vendor rankings and awards

      SoftwareReviews

      This is an image of the data quarant report

      The Data Quadrant is a thorough evaluation and ranking of all software in an individual category to compare platforms across multiple dimensions.

      This is an image of the data quarant report chart

      Vendors are ranked by their Composite Score, based on individual feature evaluations, user satisfaction rankings, vendor capability comparisons, and likeliness to recommend the platform.

      This is a image of the Emotional Footprint Report

      The Emotional Footprint is a powerful indicator of overall user sentiment toward the relationship with the vendor, capturing data across five dimensions.

      This is a image of the Emotional Footprint Report chart

      Vendors are ranked by their Customer Experience (CX) Score, which combines the overall Emotional Footprint rating with a measure of the value delivered by the solution.

      Leading B2B E-Commerce Platforms

      As of February 2022

      Data Quadrant

      This image contains a screenshot of the Data Quadrant chart for B2B E-commerce

      Emotional Footprint

      This image contains a screenshot of the Emotional Footprint chart for B2B E-commerce

      Leading B2C E-Commerce Platforms

      As of February 2022

      Data Quadrant

      This image contains a screenshot of the Data Quadrant chart for B2C E-commerce

      Emotional Footprint

      This image contains a screenshot of the Emotional Footprint chart for B2C E-commerce

      Application spotlight: point-of-sale solutions

      How It Enables Your Strategy

      • Point-of-sale solutions provide capabilities for cash register/terminal management, transaction processing, and lightweight inventory management.
      • Many POS vendors also offer products that have the ability to create orders from EDI, phone, or fax channels.
      • An increasing emphasis has been placed on retail analytics by POS vendors – providing reporting and analysis tools to help with inventory planning, promotion management, and product recommendations.
      • Integration of POS systems with a central customer data warehouse or other system of record for customer information allows for the ability to build richer customer profiles and compare shopping habits in physical stores against other transactional channels that are offered.
      • POS vendors often offer (or integrate with) loyalty management solutions to track, manage, and redeem loyalty points. See this note on loyalty management systems.
      • Legacy and/or homegrown POS systems tend to be an area of frustration for customer experience management modernization.

      Key Trends

      • POS solutions are moving from “cash-register-only” solutions to encompass mobile POS form factors like smartphones and tablets. Vendors such as Square have experienced tremendous growth in opening up the market via “mPOS” platforms that have lower costs to entry than the traditional hardware needed to support full-fledged POS solutions.
      • This development puts robust POS toolsets in the hands of small and medium businesses that otherwise would be priced out of the market.

      POS KPIs

      Strong POS applications can improve:

      • Customer Data Collection
      • Inventory or Cash Shrinkage
      • Cost per Transaction
      • Loyalty Program Administration Costs
      • Cycle Time for Transaction Execution

      Point-of-Sales Vendor Snapshot: Part 1

      Mid-Market POS Solutions

      This image contains the following company Logos: Square; Shopify; Vend; Heartland|Retail

      Point-of-Sales Vendor Snapshot: Part 2

      Large Enterprise POS Platforms

      This image contains the following Logos: Clover; Oracle Netsuite; RQ Retail Management; Salesforce Commerce Cloud; Korona

      Leading Retail POS Systems

      As of February 2022

      Data Quadrant

      This is an image of the Data Quadrant Chart for the Leading Retail Pos Systems

      Emotional Footprint

      This is an image of the Emotional Footprint chart for the Leading Retail POS Systems

      Summary of Accomplishment

      Knowledge Gained

      • Commerce channel framework
      • Customer affinities
      • Commerce channel overview
      • Commerce-enabling technologies

      Processes Optimized

      • Persona definition for commerce strategy
      • Persona channel shortlist

      Deliverables Completed

      • Customer personas
      • Commerce user scenarios
      • Business drivers for traditional commerce and e-commerce
      • Channel matrix for omnichannel commerce

      Bibliography

      “25 Amazing Omnichannel Statistics Every Marketer Should Know (Updated for 2021).” V12, 29 June 2021. Accessed 12 Jan. 2022.

      “Amazon Go.” Amazon, n.d. Web.

      Andersen, Derek. “33 Statistics Retail Marketers Need to Know in 2021.” Invoca, 19 July 2021. Accessed 12 Jan. 2022.

      Andre, Louie. “115 Critical Customer Support Software Statistics: 2022 Market Share Analysis & Data.” FinancesOnline, 14 Jan. 2022. Accessed 25 Jan. 2022.

      Chuang, Courtney. “The future of support: 5 key trends that will shape customer care in 2022.” Intercom, 10 Jan. 2022. Accessed 11 Jan. 2022.

      Cramer-Flood, Ethan. “Global Ecommerce Update 2021.” eMarketer, 13 Jan. 2021. Accessed 12 Jan. 2022.

      Cramer-Flood, Ethan. “Spotlight on total global retail: Brick-and-mortar returns with a vengeance.” eMarketer, 3 Feb. 2022. Accessed 12 Apr. 2022.

      Fox Rubin, Ben. “Amazon now operates seven different kinds of physical stores. Here's why.” CNET, 28 Feb. 2020. Accessed 12 Jan. 2022.

      Krajewski, Laura. “16 Statistics on Why Omnichannel is the Future of Your Contact Center and the Foundation for a Top-Notch Competitive Customer Experience.” Business 2 Community, 10 July 2020. Accessed 11 Jan. 2022.

      Manoff, Jill. “Fun and convenience: CEO Nany Green on Old Navy’s priorities for holiday.” Glossy, 8 Dec. 2020. Accessed 12 Jan. 2022.

      Meola, Andrew. “Rise of M-Commerce: Mobile Ecommerce Shopping Stats & Trends in 2021.” Insider, 30 Dec. 2020. Accessed 12 Jan. 2022.

      “Outdoor apparel retailer Icebreaker uses AI to exceed shopper expectations.” Salesforce, n.d.(a). Accessed 20 Jan. 2022.

      “Personas.” Usability.gov., n.d. Web. 28 Aug. 2018.

      “PetSmart – Why Commerce Cloud?” Salesforce, n.d.(b). Web. 30 April 2018.

      Toor, Meena. “Customer expectations: 7 Types all exceptional researchers must understand.” Qualtrics, 3 Dec. 2020. Accessed 11 Jan. 2022.

      Westfall, Leigh. “Omnichannel vs. multichannel: What's the difference?” RingCentral, 10 Sept. 2021. Accessed 11 Jan. 2022.

      “Worldwide ecommerce will approach $5 trillion this year.” eMarketer, 14 Jan. 2021. Accessed 12 Jan. 2022.

      Get Started With IT Project Portfolio Management

      • Buy Link or Shortcode: {j2store}443|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $7,599 Average $ Saved
      • member rating average days saved: 46 Average Days Saved
      • Parent Category Name: Portfolio Management
      • Parent Category Link: /portfolio-management
      • Most companies are struggling to get their project work done. This is due in part to the fact that many prescribed remedies are confusing, disruptive, costly, or ineffective.
      • While struggling to find a solution, within the organization, project requests never stop and all projects continue to all be treated the same. Resources are requested for multiple projects without any visibility into their project capacity. Projects lack proper handoffs from closure to ongoing operational work. And the benefits are never tracked.
      • If you have too many projects, limited resources, ineffective communications, or low post-project adoption, keep reading. Perhaps you should spend a bit more on project, portfolio, and organizational change management.

      Our Advice

      Critical Insight

      • Successful project outcomes are not built by rigorous project processes: Projects may be the problem, but project management rigor is not the solution.
      • Don’t fall into the common trap of thinking high-rigor project management should be every organization’s end goal.
      • Instead, understand that it is better to spend time assessing the portfolio to determine what projects should be prioritized.

      Impact and Result

      Begin by establishing a few foundational practices that will work to drive project throughput.

      • Capacity Estimation: Understand what your capacity is to do projects by determining how much time is allocated to doing other things.
      • Book of Record: Establish a basic but sustainable book of record so there is an official list of projects in flight and those waiting in a backlog or funnel.
      • Simple Project Management Processes: Align the rigor of your project management process with what is required, not what is prescribed by the PMP designation.
      • Impact Assessment: Address the impact of change at the beginning of the project and prepare stakeholders with the right level of communication.

      Get Started With IT Project Portfolio Management Research & Tools

      Start here – read the Executive Brief

      Begin by establishing a few foundational practices that will work to drive project throughput. Most project management problems are resolved with portfolio level solutions. This blueprint will address the eco-system of project, portfolio, and organizational change management.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Project portfolio management

      Estimate project capacity, determine what needs to be tracked on an ongoing basis, and determine what criteria is necessary for prioritizing projects.

      • Project Portfolio Supply-Demand Analysis Tool
      • Project Value Scorecard Development Tool
      • Project Portfolio Book of Record

      2. Project management

      Develop a process to inform the portfolio of the project status, create a plan that can be maintained throughout the project lifecycle, and manage the scope through a change request process.

      • Light Project Change Request Form Template

      3. Organizational change management

      Perform a change impact assessment and identify the obvious and non-obvious stakeholders to develop a message canvas accordingly.

      • Organizational Change Management Triage Tool

      4. Develop an action plan

      Develop a roadmap for how to move from the current state to the target state.

      • PPM Wireframe
      • Project Portfolio Management Foundations Stakeholder Communication Deck
      [infographic]

      Workshop: Get Started With IT Project Portfolio Management

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Project Portfolio Management

      The Purpose

      Establish the current state of the portfolio.

      Organize the portfolio requirements.

      Determine how projects are prioritized.

      Key Benefits Achieved

      Understand project capacity supply-demand.

      Build a portfolio book of record.

      Create a project value scorecard.

      Activities

      1.1 Conduct capacity supply-demand estimation.

      1.2 Determine requirements for portfolio book of record.

      1.3 Develop project value criteria.

      Outputs

      Clear project capacity

      Draft portfolio book of record

      Project value scorecard

      2 Project Management

      The Purpose

      Feed the portfolio with the project status.

      Plan the project work with a sustainable level of granularity.

      Manage the project as conditions change.

      Key Benefits Achieved

      Develop a process to inform the portfolio of the project status.

      Create a plan that can be maintained throughout the project lifecycle and manage the scope through a change request process.

      Activities

      2.1 Determine necessary reporting metrics.

      2.2 Create a work structure breakdown.

      2.3 Document your project change request process.

      Outputs

      Feed the portfolio with the project status

      Plan the project work with a sustainable level of granularity

      Manage the project as conditions change

      3 Organizational Change Management

      The Purpose

      Discuss change accountability.

      Complete a change impact assessment.

      Create a communication plan for stakeholders.

      Key Benefits Achieved

      Complete a change impact assessment.

      Identify the obvious and non-obvious stakeholders and develop a message canvas accordingly.

      Activities

      3.1 Discuss change accountability.

      3.2 Complete a change impact assessment.

      3.3 Create a communication plan for stakeholders.

      Outputs

      Assign accountability for the change

      Assess the change impact

      Communicate the change

      4 Develop an Action Plan

      The Purpose

      Summarize current state.

      Determine target state.

      Create a roadmap.

      Key Benefits Achieved

      Develop a roadmap for how to move from the current state to the target state.

      Activities

      4.1 Summarize current state and target state.

      4.2 Create a roadmap.

      Outputs

      Stakeholder Communication Deck

      MS Project Wireframe

      Accelerate Business Growth and Valuation by Building Brand Awareness

      • Buy Link or Shortcode: {j2store}569|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Marketing Solutions
      • Parent Category Link: /marketing-solutions

      Brands that fail to invest in brand awareness are likely to face some, if not all these problems:

      • Lack of brand visibility and recognition
      • Inability to reach and engage with the buyers
      • Difficulties generating and converting leads
      • Low customer retention rate
      • Inability to justify higher pricing
      • Limited brand equity, business valuation, and sustainability

      Our Advice

      Critical Insight

      Awareness brings visibility and traction to brands, which is essential in taking the market leadership position and becoming the trusted brand that buyers think of first.

      Brand awareness also significantly contributes to increasing brand equity, market valuation, and business sustainability.

      Impact and Result

      Building brand awareness allows for the increase of:

      • Brand visibility, perception, recognition, and reputation
      • Interactions and engagement with the target audience
      • Digital advertising performance and ROI
      • Conversion rates and sales wins
      • Revenue and profitability
      • Market share & share of voice (SOV)
      • Talents, partners, and investors attraction and retention
      • Brand equity, business growth, and market valuation

      Accelerate Business Growth and Valuation by Building Brand Awareness Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Accelerate Business Growth and Valuation by Building Brand Awareness Storyboard - Learn how to establish the brand foundation, create assets and workflows, and deploy effective brand awareness strategies and tactics.

      A two-step approach to building brand awareness, starting with defining the brand foundations and then implementing effective brand awareness strategies and tactics.

      • Accelerate Business Growth and Valuation by Building Brand Awareness Storyboard

      2. Define Brand's Personality and Message - Analyze your target market and develop key elements of your brand guidelines.

      With this set of tools, you will be able to capture and analyze your target market, your buyers and their journeys, define your brand's values, personality, and voice, and develop all the key elements of your brand guidelines to enable people within your organization and external resources to build a consistent and recognizable image across all assets and platforms.

      • Market Analysis Template
      • Brand Recognition Survey and Interview Questionnaire and List Template
      • External and Internal Factors Analysis Template
      • Buyer Personas and Journey Presentation Template
      • Brand Purpose, Mission, Vision, and Values Template
      • Brand Value Proposition and Positioning Statement
      • Brand Voice Guidelines Template
      • Writing Style Guide Template
      • Brand Messaging Template
      • Writer Checklist

      3. Start Building Brand Awareness - Achieve strategic alignment.

      These tools will allow you to achieve strategic alignment and readiness, create assets and workflows, deploy tactics, establish Key Performance Indicators (KPIs), and monitor and optimize your strategy on an ongoing basis.

      • Brand Awareness Strategy and Tactics Template
      • Asset Creation and Management List
      • Campaign Workflows Template
      • Brand Awareness Strategy Rollout Plan Template
      • Survey Emails Best Practices Guidelines

      Infographic

      Further reading

      Accelerate Business Growth and Valuation By Building Brand Awareness

      Develop and deploy comprehensive, multi-touchpoint brand awareness strategies to become the trusted brand that buyers think of first.

      EXECUTIVE BRIEF

      Analyst perspective

      Building brand awareness

      Achieving high brand awareness in a given market and becoming the benchmark for buyers

      is what every brand wants to achieve, as it is a guarantee of success. Building brand awareness,

      even though its immediate benefits are often difficult to see and measure, is essential for companies that want to stand out from their competitors and continue to grow in a sustainable way. The return on investment (ROI) may take longer, but the benefits are also greater than those achieved through short-term initiatives with the expectation of immediate, albeit often limited, results.

      Brands that are familiar to their target market have greater credibility, generate more sales,

      and have a more loyal customer base. CMOs that successfully execute brand awareness programs

      build brand equity and grow company valuation.

      This is a picture of Nathalie Vezina

      Nathalie Vezina
      Marketing Research Director
      SoftwareReviews Advisory

      Executive summary

      Brand leaders know that brand awareness is essential to the success of all marketing and sales activities. Brands that fail to invest in brand awareness are likely to face some, if not all these problems:

      • Lack of brand visibility and compelling storytelling.
      • Inability to reach the target audience.
      • Low engagement on digital platforms and with ads.
      • Difficulties generating and converting leads, or closing/winning sales/deals, and facing a high cost per acquisition.
      • Low/no interest or brand recognition, trust level, and customer retention rate.
      • Inability to justify higher pricing.

      Convincing stakeholders of the benefits of strong brand awareness can be difficult when the positive outcomes are hard to quantify, and the return on investment (ROI) is often long-term. Among the many obstacles brand leaders must overcome are:

      • Lack of longer-term corporate vision, focusing all efforts and resources on short-term growth strategies for a quick ROI.
      • Insufficient market and target buyers' information and understanding of the brand's key differentiator.
      • Misalignment of brand message, and difficulties creating compelling content that resonates with the target audience, generates interest, and keeps them engaged.
      • Limited or no resources dedicated to the development of the brand.

      Inspired by top-performing businesses and best practices, this blueprint provides the guidance and tools needed to successfully build awareness and help businesses grow. By following these guidelines, brand leaders can expect to:

      • Gain market intelligence and a clear understanding of the buyer's needs, your competitive advantage, and key differentiator.
      • Develop a clear and compelling value proposition and a human-centric brand messaging driven by the brand's values.
      • Increase online presence and brand awareness to attract and engage with buyers.
      • Develop a long-term brand strategy and execution plan.

      "A brand is the set of expectations, memories, stories, and relationships that, taken together, account for a consumer's decision to choose one product or service over another."

      – Seth Godin

      What is brand awareness?

      The act of making a brand visible and memorable.

      Brand awareness is the degree to which buyers are familiar with and recognize the attributes and image of a particular brand, product, or service. The higher the level of awareness, the more likely the brand is to come into play when a target audience enters the " buying consideration" phase of the buyer's journey.

      Brand awareness also plays an important role in building equity and increasing business valuation. Brands that are familiar to their target market have greater credibility, drive more sales and have a more loyal customer base.
      Building brand awareness allows increasing:

      • Brand visibility, perception, recognition, and reputation
      • Interactions and engagement with the target audience
      • Digital advertising performance and ROI
      • Conversion rates and sales wins
      • Revenue and profitability
      • Market share and share of voice (SOV)
      • Talents, partners, and investors attraction and retention
      • Brand equity, business growth, and market valuation

      "Products are made in a factory, but brands are created in the mind."
      Source: Walter Landor

      Capitalizing on a powerful brand

      A longer-term approach for an increased and more sustainable ROI.

      Market leader position

      Developing brand awareness is essential to increase the visibility and traction of a brand.

      Several factors may cause a brand to be not well-known. One reason might be that the brand recently launched, such as a startup. Another reason could be that the brand has rebranded or entered a new market.

      To become the trusted brand that buyers think of first in their target markets, it is critical for these brands to develop and deploy comprehensive, multi-touchpoint brand awareness strategies.

      A relationship leading to loyalty

      A longer-term brand awareness strategy helps build a strong relationship between the brand and the buyer, fostering a lasting and rewarding alliance.

      It also enables brands to reach and engage with their target audience effectively by using compelling storytelling and meaningful content.

      Adopting a more human-centric approach and emphasizing shared values makes the brand more attractive to buyers and can drive sales and gain loyalty.

      Sustainable business growth

      For brands that are not well established in their target market, short-term tactics that focus on immediate benefits can be ineffective. In contrast, long-term brand awareness strategies provide a more sustainable ROI (return on investment).

      Investing in building brand awareness can impact a business's ability to interact with its target audience, generate leads, and increase sales. Moreover, it can significantly contribute to boosting the business's brand equity and market valuation.

      "Quick wins may work in the short term, but they're not an ideal substitute for long-term tactics and continued success."
      Source: Forbes

      Impacts of low brand awareness on businesses

      Unfamiliar brands, despite their strong potential, won't thrive unless they invest in their notoriety.

      Brands that choose not to invest in longer-term awareness strategies and rely solely on short-term growth tactics in hopes of an immediate gain will see their ability to grow diminished and their longevity reduced due to a lack of market presence and recognition.

      Symptoms of a weakening brand include:

      • High marketing spending and limited result
      • Low market share or penetration
      • Low sales, revenue, and gross margin
      • Weak renewal rate, customer retention, and loyalty
      • Difficulties delivering on the brand promise, low/no trust in the brand
      • Limited brand equity, business valuation, and sustainability
      • Unattractive brand to partners and investors

      "Your brand is the single most important investment you can make in your business."
      Source: Steve Forbes

      Most common obstacles to increasing brand awareness

      Successfully building brand awareness requires careful preparation and planning.

      • Limited market intelligence
      • Unclear competitive advantage/key differentiator
      • Misaligned and inconsistent messaging and storytelling
      • Lack of long-term vision
      • and low prioritization
      • Limited resources to develop and execute brand awareness building tactics
      • Unattractive content that does not resonate, generates little or no interest and engagement

      Investing in the notoriety of the brand

      Become the top-of-mind brand in your target market.

      To stand out, be recognized by their target audience, and become major players in their industry, brands must adopt a winning strategy that includes the following elements:

      • In-depth knowledge and understanding of the market and audience
      • Strengthening digital presence and activities
      • Creating and publishing content relevant to the target audience
      • Reaching out through multiple touchpoints
      • Using a more human-centric approach
      • Ensure consistency in all aspects of the brand, across all media and channels

      How far are you from being the brand buyers think of first in your target market?

      This is an image of the Brand Awareness Pyramid.

      Brand awareness pyramid

      Based on David Aaker's brand loyalty pyramid

      Tactics for building brand awareness

      Focus on effective ways to gain brand recognition in the minds of buyers.

      This is an image of the Brand Awareness Journey Roadmap.

      Brand recognition requires in-depth knowledge of the target market, the creation of strong brand attributes, and increased presence and visibility.

      Understand the market and audience you're targeting

      Be prepared. Act smart.

      To implement a winning brand awareness-building strategy, you must:

      • Be aware of your competitor's strengths and weaknesses, as well as yours.
      • Find out who is behind the keyboard, and the user experience they expect to have.
      • Plan and continuously adapt your tactics accordingly.
      • Make your buyer the hero.

      Identify the brands' uniqueness

      Find your "winning zone" and how your brand uniquely addresses buyers' pain points.

      Focus on your key differentiator

      A brand has found its "winning zone" or key differentiator when its value proposition clearly shows that it uniquely solves its buyers' specific pain points.

      Align with your target audience's real expectations and successfully interact with them by understanding their persona and buyer's journey. Know:

      • How you uniquely address their pain points.
      • Their values and what motivates them.
      • Who they see as authorities in your field.
      • Their buying habits and trends.
      • How they like brands to engage with them.

      An image of a Venn diagram between the following three terms: Buyer pain point; Competitors' value proposition; your unique value proposition.  The overlapping zone is labeled the Winning zone.  This is your key differentiator.

      Give your brand a voice

      Define and present a consistent voice across all channels and assets.

      The voice reflects the personality of the brand and the emotion to be transmitted. That's why it's crucial to establish strict rules that define the language to use when communicating through the brand's voice, the type of words, and do's and don'ts.

      To be recognizable it is imperative to avoid inconsistencies. No matter how many people are behind the brand voice, the brand must show a unique, distinctive personality. As for the tone, it may vary according to circumstances, from lighter to more serious.

      Up to 80% Increased customer recognition when the brand uses a signature color scheme across multiple platforms
      Source: startup Bonsai
      23% of revenue increase is what consistent branding across channels leads to.
      Source: Harvard Business Review

      When we close our eyes and listen, we all recognize Ella Fitzgerald's rich and unique singing voice.

      We expect to recognize the writing of Stephen King when we read his books. For the brand's voice, it's the same. People want to be able to recognize it.

      Adopt a more human-centric approach

      If your brand was a person, who would it be?

      Human attributes

      Physically attractive

      • Brand identity
      • Logo and tagline
      • Product design

      Intellectually stimulating

      • Knowledge and ideas
      • Continuous innovation
      • Thought leadership

      Sociable

      • Friendly, likeable and fun
      • Confidently engage with audience through multiple touchpoints
      • Posts and shares meaningful content
      • Responsive

      Emotionally connected

      • Inspiring
      • Powerful influencer
      • Triggers emotional reactions

      Morally sound

      • Ethical and responsible
      • Value driven
      • Deliver on its promise

      Personable

      • Honest
      • Self-confident and motivated
      • Accountable

      0.05 Seconds is what it takes for someone to form an opinion about a website, and a brand.
      Source: 8ways

      90% of the time, our initial gut reaction to products is based on color alone.
      Source: startup Bonsai

      56% of the final b2b purchasing decision is based on emotional factors.
      Source: B@B International

      Put values at the heart of the brand-buyers relationship

      Highlight values that will resonate with your audience.

      Brands that focus on the values they share with their buyers, rather than simply on a product or service, succeed in making meaningful emotional connections with them and keep them actively engaged.

      Shared values such as transparency, sustainability, diversity, environmental protection, and social responsibility become the foundation of a solid relationship between a brand and its audience.

      The key is to know what motivates the target audience.

      86% of consumers claim that authenticity is one of the key factors they consider when deciding which brands they like and support.
      Source: Business Wire

      56% of the final decision is based on having a strong emotional connection with the supplier.
      Source: B2B International

      64% of today's customers are belief-driven buyers; they want to support brands that "can be a powerful force for change."
      Source: Edelman

      "If people believe they share values with a company, they will stay loyal to the brand."
      – Howard Schultz
      Source: Lokus Design

      Double-down on digital

      Develop your digital presence and reach out to your target audiences through multiple touchpoints.

      Beyond engaging content, reaching the target audience requires brands to connect and interact with their audience in multiple ways so that potential buyers can form an opinion.

      With the right message consistently delivered across multiple channels, brands increase their reach, create a buzz around their brand and raise awareness.

      73% of today's consumers confirm they use more than one channel during a shopping journey
      Source: Harvard Business Review

      Platforms

      • Website and apps
      • Social media
      • Group discussions

      Multimedia

      • Webinars
      • Podcasts
      • Publication

      Campaign

      • Ads and advertising
      • Landing pages
      • Emails, surveys drip campaigns

      Network

      • Tradeshows, events, sponsorships
      • Conferences, speaking opportunities
      • Partners and influencers

      Use social media to connect

      Reach out to the masses with a social media presence.

      Social media platforms represent a cost-effective opportunity for businesses to connect and influence their audience and tell their story by posting relevant and search-engine-optimized content regularly on their account and groups. It's also a nice gateway to their website.

      Building a relationship with their target buyer through social media is also an easy way for businesses to:

      • Understand the buyers.
      • Receive feedback on how the buyers perceive the brand and how to improve it.
      • Show great user experience and responsiveness.
      • Build trust.
      • Create awareness.

      75% of B2B buyers and 84% of C-Suite executives use social media when considering a purchase
      Source: LinkedIn Business

      92% of B2B buyers use social media to connect with leaders in the sales industry.
      Source: Techjury

      With over 4.5 billion social media users worldwide, and 13 new users signing up to their first social media account every second, social media is fast becoming a primary channel of communication and social interaction for many.
      Source: McKinsey

      Become the expert subject matter

      Raise awareness with thought leadership content.

      Thought leadership is about building credibility
      by creating and publishing meaningful, relevant content that resonates with a target audience.
      Thought leaders write and publish all kinds of relevant content such as white papers, ebooks, case studies, infographics, video and audio content, webinars, and research reports.
      They also participate in speaking opportunities, live presentations, and other high-visibility forums.
      Well-executed thought leadership strategies contribute to:

      • Raise awareness.
      • Build credibility.
      • Be recognized as a subject expert matter.
      • Become an industry leader.

      60% of buyers say thought leadership builds credibility when entering a new category where the brand is not already known.
      Source: Edelman | LinkedIn

      70% of people would rather learn about a company through articles rather than advertising.
      Source: Brew Interactive

      57% of buyers say that thought leadership builds awareness for a new or little-known brand.
      Source: Edelman | LinkedIn

      To achieve best results

      • Know the buyers' persona and journey.
      • Create original content that matches the persona of the target audience and that is close to their values.
      • Be Truthful and insightful.
      • Find the right tone and balance between being human-centric, authoritative, and bold.
      • Be mindful of people's attention span and value their time.
      • Create content for each phase of the buyer's journey.
      • Ensure content is SEO, keyword-loaded, and add calls-to-action (CTAs).
      • Add reason to believe, data to support, and proof points.
      • Address the buyers' pain points in a unique way.

      Avoid

      • Focusing on product features and on selling.
      • Publishing generic content.
      • Using an overly corporate tone.

      Promote personal branding

      Rely on your most powerful brand ambassadors and influencers: your employees.

      The strength of personal branding is amplified when individuals and companies collaborate to pursue personal branding initiatives that offer mutual benefits. By training and positioning key employees as brand ambassadors and industry influencers, brands can boost their brand awareness through influencer marketing strategies.

      Personal branding, when well aligned with business goals, helps brands leverage their key employee's brands to:

      • Increase the organization's brand awareness.
      • Broaden their reach and circle of influence.
      • Show value, gain credibility, and build trust.
      • Stand out from the competition.
      • Build employee loyalty and pride.
      • Become a reference to other businesses.
      • Increase speaking opportunities.
      • Boost qualified leads and sales.

      About 90% of organizations' employee network tends to be completely new to the brand.
      Source: Everyone Social

      8X more engagement comes from social media content shared by employees rather than brand accounts.
      Source: Entrepreneur

      561% more reach when brand messages are shared by employees on social media, than the same message shared by the Brand's social media.
      Source: Entrepreneur

      "Personal branding is the art of becoming knowable, likable and trustable."
      Source: Founder Jar, John Jantsch

      Invest in B2B influencer marketing

      Broaden your reach and audiences by leveraging the voice of influencers.

      Influencers are trusted industry experts and analysts who buyers can count on to provide reliable information when looking to make a purchase.

      Influencer marketing can be very effective to reach new audiences, increase awareness, and build trust. But finding the right influencers with the level of credibility and visibility brands are expecting can sometimes be challenging.

      Search for influencers that have:

      • Relevance of audience and size.
      • Industry expertise and credibility.
      • Ability to create meaningful content (written, video, audio).
      • Charismatic personality with values consistent with the brand.
      • Frequent publications on at least one leading media platform.

      76% of people say that they trust content shared by people over a brand.
      Source: Adweek


      44% increased media mention of the brand using B2B influencer marketers.
      Source: TopRank Marketing

      Turn your customers into brand advocates

      Establish customer advocacy programs and deliver a great customer experience.

      Retain your customers and turn them into brand advocates by building trust, providing an exceptional experience, and most importantly, continuously delivering on the brand promise.

      Implement a strong customer advocacy program, based on personalized experiences, the value provided, and mutual exchange, and reap the benefits of developing and growing long-term relationships.

      92% of individuals trust word-of-mouth recommendations, making it one of the most trust-rich forms of advertising.
      Source: SocialToaster

      Word-of-mouth (advocacy) marketing increases marketing effectiveness by 54%
      Source: SocialToaster

      Make your brand known and make it stick in people's minds

      Building and maintaining high brand awareness requires that each individual within the organization carry and deliver the brand message clearly and consistently across all media whether in person, in written communications, or otherwise.

      To achieve this, brand leaders must first develop a powerful, researched narrative that people will embrace and convey, which requires careful preparation.

      Target market and audience intel

      • Target market Intel
      • Buyer persona and journey/pain points
      • Uniqueness and positioning

      Brand attributes

      • Values at the heart of the relationship
      • Brand's human attributes

      Brand visibly and recall

      • Digital and social media presence
      • Thought leadership
      • Personal branding
      • Influencer marketing

      Brand awareness building plan

      • Long-term awareness and multi-touchpoint approach
      • Monitoring and optimization

      Short and long-term benefits of increasing brand awareness

      Brands are built over the long term but the rewards are high.

      • Stronger brand perception
      • Improved engagement and brand associations
      • Enhanced credibility, reputation, and trust
      • Better connection with customers
      • Increased repeat business
      • High-quality leads
      • Higher and faster conversion rate
      • More sales closed/ deals won
      • Greater brand equity
      • Accelerated growth

      "Strong brands outperform their less recognizable competitors by as much as 73%."
      Source: McKinsey

      Brand awareness building

      Building brand awareness, even though immediate benefits are often difficult to see and measure, is essential for companies to stand out from their competitors and continue to grow in a sustainable way.

      To successfully raise awareness, brands need to have:

      • A longer-term vision and strategy.
      • Market Intelligence, a clear value proposition, and key differentiator.
      • Consistent, well-aligned messaging and storytelling.
      • Digital presence and content.
      • The ability to reach out through multiple touchpoints.
      • Necessary resources.

      Without brand awareness, brands become less attractive to buyers, talent, and investors, and their ability to grow, increase their market value, and be sustainable is reduced.

      Brand awareness building methodology

      Define brands' personality and message

      • Gather market intel and analyze the market.
      • Determine the value proposition and positioning.
      • Define the brand archetype and voice.
      • Craft a compelling brand message and story.
      • Get all the key elements of your brand guidelines.

      Start building brand awareness

      • Achieve strategy alignment and readiness.
      • Create and manage assets.
      • Deploy your tactics, assets, and workflows.
      • Establish key performance indicators (KPIs).
      • Monitor and optimize on an ongoing basis.

      Toolkit

      • Market and Influencing Factors Analysis
      • Recognition Survey and Best Practices
      • Buyer Personas and Journeys
      • Purpose, Mission, Vision, Values
      • Value Proposition and Positioning
      • Brand Message, Voice, and Writing Style
      • Brand Strategy and Tactics
      • Asset Creation and Management
      • Strategy Rollout Plan

      Short and long-term benefits of increasing brand awareness

      Increase:

      • Brand perception
      • Brand associations and engagement
      • Credibility, reputation, and trust
      • Connection with customers
      • Repeat business
      • Quality leads
      • Conversion rate
      • Sales closed / deals won
      • Brand equity and growth

      It typically takes 5-7 brand interactions before a buyer remembers the brand.
      Source: Startup Bonsai

      Who benefits from this brand awareness research?

      This research is being designed for:
      Brand and marketing leaders who:

      • Know that brand awareness is essential to the success of all marketing and sales activities.
      • Want to make their brand unique, recognizable, meaningful, and highly visible.
      • Seek to increase their digital presence, connect and engage with their target audience.
      • Are looking at reaching a new segment of the market.

      This research will also assist:

      • Sales with qualified lead generation and customer retention and loyalty.
      • Human Resources in their efforts to attract and retain talent.
      • The overall business with growth and increased market value.

      This research will help you:

      • Gain market intelligence and a clear understanding of the target audience's needs and trends, competitive advantage, and key differentiator.
      • The ability to develop clear and compelling, human-centric messaging and compelling story driven by brand values.
      • Increase online presence and brand awareness activities to attract and engage with buyers.
      • Develop a long-term brand awareness strategy and deployment plan.

      This research will help them:

      • Increase campaign ROI.
      • Develop a longer-term vision and benefits of investing in longer-term initiatives.
      • Build brand equity and increase business valuation.
      • Grow your business in a more sustainable way.

      SoftwareReviews' brand awareness building methodology

      Phase 1 Define brands' personality and message

      Phase 2 Start building brand awareness

      Phase steps

      1.1 Gather market intelligence and analyze the market.

      1.2 Develop and document the buyer's persona and journey.

      1.3 Uncover the brand mission, vision statement, core values, value proposition and positioning.

      1.4 Define the brand's archetype and tone of voice, then craft a compelling brand messaging.

      2.1 Achieve strategy alignment and readiness.

      2.2 Create assets and workflows and deploy tactics.

      2.3 Establish key performance indicators (KPIs), monitor, and optimize on an ongoing basis.

      Phase outcomes

      • Target market and audience are identified and documented.
      • A clear value proposition and positioning are determined.
      • The brand personality, voice, and messaging are developed.
      • All the key elements of the brand guidelines are in place and ready to use, along with the existing logo, typography, color palette, and imagery.
      • A comprehensive and actionable brand awareness strategy, with tactics, KPIs, and metrics, is set and ready to execute.
      • A progressive and effective deployment plan with deliverables, timelines, workflows, and checklists is in place.
      • Resources are assigned.

      Insight summary

      Brands to adapt their strategies to achieve longer-term growth
      Brands must adapt and adjust their strategies to attract informed buyers who have access to a wealth of products, services, and brands from all over. Building brand awareness, even though immediate benefits are often difficult to see and measure, has become essential for companies that want to stand out from their competitors and continue to grow in a sustainable way.

      A more human-centric approach
      Brand personalities matter. Brands placing human values at the heart of the customer-brand relationship will drive interest in their brand and build trust with their target audience.

      Stand out from the crowd
      Brands that develop and promote a clear and consistent message across all platforms and channels, along with a unique value proposition, stand out from their competitors and get noticed.

      A multi-touchpoints strategy
      Engage buyers with relevant content across multiple media to address their pain points. Analyze touchpoints to determine where to invest your efforts.

      Going social
      Buyers expect brands to be active and responsive in their interactions with their audience. To build awareness, brands are expected to develop a strong presence on social media by regularly posting relevant content, engaging with their followers and influencers, and using paid advertising. They also need to establish thought leadership through content such as white papers, case studies, and webinars.

      Thought leaders wanted
      To enhance their overall brand awareness strategy, organizations should consider developing the personal brand of key executives. Thought leadership can be a valuable method to gain credibility, build trust, and drive conversion. By establishing thought leadership, businesses can increase brand mentions, social engagement, website traffic, lead generation, return on investment (ROI), and Net Promoter Score (NPS).

      Save time and money with SoftwareReviews' branding advice

      Collaborating with SoftwareReviews analysts for inquiries not only provides valuable advice but also leads to substantial cost savings during branding activities, particularly when partnering with an agency.

      Guided Implementation Purpose Measured Value
      Build brands' personality and message Get the key elements of the brand guidelines in place and ready to use, along with your existing logo, typography, color palette, and imagery, to ensure consistency and clarity across all brand touchpoints from internal communication to customer-facing materials. Working with SoftwareReviews analysts to develop brand guidelines saves costs compared to hiring an agency.

      Example: Building the guidelines with an agency will take more or less the same amount of time and cost approximately $80K.

      Start building brand awareness Achieve strategy alignment and readiness, then deploy tactics, assets, and other deliverables. Start building brand awareness and reap the immediate and long-term benefits.

      Working with SoftwareReviews analysts and your team to develop a long-term brand strategy and deployment will cost you less than a fraction of the cost of using an agency.

      Example: Developing and executing long-term brand awareness strategies with an agency will cost between $50-$75K/month over a 24-month period minimum.

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1

      Build brands' personality and message

      Phase 2

      Start building brand awareness

      • Call #1: Discuss concept and benefits of building brand awareness. Identify key stakeholders. Anticipate concerns and objections.
      • Call #2: Discuss target market intelligence, information gathering, and analysis.
      • Call #3: Review market intelligence information. Address questions or concerns.
      • Call #4: Discuss value proposition and guide to find positioning and key differentiator.
      • Call #5: Review value proposition. Address questions or concerns.
      • Call #6: Discuss how to build a comprehensive brand awareness strategy using SR guidelines and template.
      • Call #7: Review strategy. Address questions or concerns.
      • Call #8: Second review of the strategy. Address questions or concerns.
      • Call #9 (optional): Third review of the strategy. Address questions or concerns.
      • Call #10: Discuss how to build the Execution Plan using SR template.
      • Call #11: Review Execution Plan. Address questions or concerns.
      • Call #12: Second review of the Execution Plan. Address questions or concerns.
      • Call #13 (optional): Third review of the Execution Plan. Address questions or concerns.
      • Call #14: Discuss how to build a compelling storytelling and content creation.
      • Call #15: Discuss website and social media platforms and other initiatives.
      • Call #16: Discuss marketing automation and continuous monitoring.
      • Call #17 (optional): Discuss optimization and reporting
      • Call #18: Debrief and determine how we can help with next steps.

      A Guided Implementation (GI) is a series of calls with a SoftwareReviews Marketing Analyst to help implement our best practices in your organization.

      Your engagement managers will work with you to schedule analyst calls.

      Brand awareness building tools

      Each step of this blueprint comes with tools to help you build brand awareness.

      Brand Awareness Tool Kit

      This kit includes a comprehensive set of tools to help you better understand your target market and buyers, define your brand's personality and message, and develop an actionable brand awareness strategy, workflows, and rollout plan.

      The set includes these templates:
      • Market and Influencing Factors Analysis
      • Recognition Survey and Best Practices
      • Buyer Personas and Journeys
      • Purpose, Mission, Vision, and Values
      • Value Proposition and Positioning
      • Brand Message, Voice, and Writing Style
      • Brand Strategy and Tactics
      • Asset Creation and Management
      • Strategy Rollout Plan
      An image of a series of screenshots from the templates listed in the column to the left of this image.

      Get started!

      Know your target market and audience, deploy well-designed strategies based on shared values, and make meaningful connections with people.

      Phase 1

      Define brands' personality and message

      Phase 2

      Start building brand awareness

      Phase 1

      Define brands' personality and message

      Steps

      1.1 Gather market intelligence and analyze the market.
      1.2 Develop and document the buyer's persona and journey.
      1.3 Uncover the brand mission, vision statement, core values, positioning, and value proposition.
      1.4 Define the brand's archetype and tone of voice, then craft a compelling brand messaging.

      Phase outcome

      • Target market and audience are identified and documented.
      • A clear value proposition and positioning are determined.
      • The brand personality, voice, and messaging are developed.
      • All the key elements of the brand guidelines are in place. and ready to use, along with the existing logo, typography, color palette, and imagery..

      Build brands' personality and message

      Step 1.1 Gather market intelligence and analyze the market.

      Total duration: 2.5-8 hours

      Objective

      Analyze and document your competitive landscape, assess your strengths, weaknesses, opportunities,
      and threats, gauge the buyers' familiarity with your brand, and identify the forces of influence.

      Output

      This exercise will allow you to understand your market and is essential to developing your value proposition.

      Participants

      • Head of branding and key stakeholders

      MarTech
      May require you to:

      • Register to a Survey Platform.
      • Use, setup, or install platforms like CRM and/or Marketing Automation Platform.

      Tools

      1.1.1 SWOT and competitive landscape

      (60-120 min.)

      Analyze & Document

      Follow the instructions in the Market Analysis Template to complete the SWOT and Competitive Analysis, slides 4 to 7.

      1.1.3 Internal and External Factors

      (30-60 min.)

      Analyze

      Follow the instructions in the External and Internal Factors Analysis Template to perform the PESTLE, Porter's 5 Forces, and Internal Factors and VRIO Analysis.

      Transfer

      Transfer key information into slides 10 and 11 of the Market Analysis Template.

      Consult SoftwareReviews website to find the best survey and MarTech platforms or contact one of our analysts for more personalized assistance and guidance

      1.1.2 Brand recognition

      (60-300 min.)

      Prep

      Adapt the survey and interview questions in the Brand Recognition Survey Questionnaire and List Template.

      Determine how you will proceed to conduct the survey and interviews (internal or external resources, and tools).

      Refer to the Survey Emails Best Practices Guidelines for more information on how to conduct email surveys.

      Collect & Analyze

      Use the Brand Recognition Survey Questionnaire and List Template to build your list, conduct the survey /interviews, and collect and analyze the feedback received.

      Transfer

      Transfer key information into slides 8 and 9 of the Market Analysis Template.

      Brand performance diagnostic

      Have you considered diagnosing your brand's current performance before you begin building brand awareness?

      Audit your brand using the Diagnose Brand Health to Improve Business Growth blueprint.Collect and interpret qualitative and quantitative brand performance measures.

      The toolkit includes the following templates:

      • Surveys and interviews questions and lists
      • External and internal factor analysis
      • Digital and financial metrics analysis

      Also included is an executive presentation template to communicate the results to key stakeholders and recommendations to fix the uncovered issues.

      Build brands' personality and message

      Step 1.2 Develop and document the buyer's persona and journey.

      Total duration: 4-8 hours

      Objective

      Gather existing and desired customer insights and conduct market research to define and personify your buyers' personas and their buying behaviors.

      Output

      Provide people in your organization with clear direction on who your target buyers are and guidance on how to effectively reach and engage with them throughout their journey.
      Participants

      • Head of branding
      • Key stakeholders from sales and product marketing

      MarTech
      May require you to:

      • Register to an Online Survey Platform (free version or subscription).
      • Use, setup, or installation of platforms like CRM and/or Marketing Automation Platform.

      Tools

      1.2.1 Buyer Personas and Journeys

      (240-280 min.)

      Research

      Identify your tier 1 to 3 customers using the Ideal Client Profile (ICP) Workbook. (Recommended)

      Survey and interview existing and desired customers based using the Buyer Persona and Journey Interview Guide and Data Capture Tool. (Recommended)

      Create

      Define and document your tier 1 to 3 Buyer Personas and Journeys using the Buyer Personas and Journeys Presentation Template.

      Consult SoftwareReviews website to find the best survey platform for your needs or contact one of our analysts for more personalized assistance and guidance

      Buyer Personas and Journeys

      A well-defined buyer persona and journey is a great way for brands to ensure they are effectively reaching and engaging their ideal buyers through a personalized buying experience.

      When properly documented, it provides valuable insights about the ideal customers, their needs, challenges, and buying decision processes allowing the development of initiatives that correspond to the target buyers.

      Build brands' personality and message

      Step 1.3 Uncover the brand mission, vision statement, core values, value proposition, and positioning.

      Total duration: 4-5.5 hours

      Objective
      Define the "raison d'être" and fundamental principles of your brand, your positioning in the marketplace, and your unique competitive advantage.

      Output
      Allows everyone in an organization to understand and align with the brand's raison d'être beyond the financial dimension, its current positioning and objectives, and how it intends to achieve them.
      It also serves to communicate a clear and appealing value proposition to buyers.

      Participants

      • Head of branding
      • Chief Executive Officer (CEO)
      • Key stakeholders

      Tools

      • Brand Purpose, Mission, Vision, and Values Template
      • Value Proposition and Positioning Statement Template

      1.3.1 Brand Purpose, Mission, Vision, and Values

      (90-120 min.)

      Capture or Develop

      Capture or develop, if not already existing, your brand's purpose, mission, vision statement, and core values using slides 4 to 7 of the Brand Purpose, Mission, Vision, and Values Template.

      1.3.2 Brand Value Proposition and Positioning

      (150-210 min.)

      Define

      Map the brand value proposition using the canvas on slide 5 of the Value Proposition and Positioning Statement Template, and clearly articulate your value proposition statement on slide 4.

      Optional: Use canvas on slide 7 to develop product-specific product value propositions.

      On slide 8 of the same template, develop your brand positioning statement.

      Build brands' personality and message

      Steps 1.4 Define the brand's archetype and tone of voice, and craft a compelling brand messaging.

      Total duration: 5-8 hours

      Objective

      Define your unique brand voice and develop a set of guidelines, brand story, and messaging to ensure consistency across your digital and non-digital marketing and communication assets.
      Output

      A documented brand personality and voice, as well as brand story and message, will allow anyone producing content or communicating on behalf of your brand to do it using a unique and recognizable voice, and convey the right message.

      Participants

      • Head of branding
      • Content specialist
      • Chief Executive Officer and other key stakeholders

      Tools

      • Brand Voice Guidelines Template
      • Writing Style Guide Template
      • Brand Messaging Template
      • Writer Checklist Template

      1.4.1 Brand Archetype and Tone of Voice

      (120-240 min.)

      Define and document

      Refer to slides 5 and 6 of the Brand Voice Guidelines Template to define your brand personality (archetype), slide 7.

      Use the Brand Voice Guidelines Template to define your brand tone of voice and characteristics on slides 8 and 9, based on the 4 primary tone of voice dimensions, and develop your brand voice chart, slide 9.

      Set Rules

      In the Writing Style Guide template, outline your brand's writing principles, style, grammar, punctuation, and number rules.

      1.4.2 Brand Messaging

      (180-240 min.)

      Craft

      Use the Brand Messaging template, slides 4 to 7, to craft your brand story and message.

      Audit

      Create a content audit to review and approve content to be created prior to publication, using the Writer's Checklist template.

      Important Tip!

      A consistent brand voice leads to remembering and trusting the brand. It should stand out from the competitors' voices and be meaningful to the target audience. Once the brand voice is set, avoid changing it.

      Phase 2

      Start building brand awareness

      Steps

      2.1 Achieve strategy alignment and readiness.
      2.2 Create assets and workflows, and deploy tactics.
      2.3 Establish key performance indicators (KPIs), monitor, and optimize on an ongoing basis.

      Phase outcome

      • A comprehensive and actionable brand awareness strategy, with tactics, KPIs, and metrics, is set and ready to execute.
      • A progressive and effective deployment plan with deliverables, timelines, workflows, and checklists is in place.
      • Resources are assigned.

      Start building brand awareness

      Step 2.1 Achieve strategy readiness and alignment.

      Total duration: 4-5 hours

      Objective

      Now that you have all the key elements of your brand guidelines in place, in addition to your existing logo, typography, color palette, and imagery, you can begin to build brand awareness.

      Start planning to build brand awareness by developing a comprehensive and actionable brand awareness strategy with tactics that align with the company's purpose and objectives. The strategy should include achievable goals and measurables, budget and staffing considerations, and a good workload assessment.

      Output

      A comprehensive long-term, actionable brand awareness strategy with KPIs and measurables.

      Participants

      • Head of branding
      • Key stakeholders

      Tools

      • Brand Awareness Strategy and Tactics Template

      2.1.1 Brand Awareness Analysis

      (60-120 min.)

      Identify

      In slide 5 of the Brand Awareness Strategy and Tactics Template, identify your top three brand awareness drivers, opportunities, inhibitors, and risks to help you establish your strategic objectives in building brand awareness.

      2.1.2 Brand Awareness Strategy

      (60-120 min.)

      Elaborate

      Use slides 6 to 10 of the Brand Awareness Strategy and Tactics Template to elaborate on your strategy goals, key issues, and tactics to begin or continue building brand awareness.

      2.1.3 Brand Awareness KPIs and Metrics

      (180-240 min.)

      Set

      Set the strategy performance metrics and KPIs on slide 11 of the Brand Awareness Strategy and Tactics Template.

      Monitor

      Once you start executing the strategy, monitor and report each quarter using slides 13 to 15 of the same document.

      Understanding the difference between strategies and tactics

      Strategies and tactics can easily be confused, but although they may seem similar at times, they are in fact quite different.

      Strategies and tactics are complementary.

      A strategy is a plan to achieve specific goals, while a tactic is a concrete action or set of actions used to implement that strategy.

      To be effective, brand awareness strategies should be well thought-out, carefully planned, and supported by a series of tactics to achieve the expected outcomes.

      Start building brand awareness

      Step 2.2 Create assets and workflows and deploy tactics.

      Total duration: 3.5-4.5 hours

      Objective

      Build a long-term rollout with deliverables, milestones, timelines, workflows, and checklists. Assign resources and proceed to the ongoing development of assets. Implement, manage, and continuously communicate the strategy and results to key stakeholders.

      Output

      Progressive and effective development and deployment of the brand awareness-building strategy and tactics.

      Participants

      • Head of branding

      Tools

      • Asset Creation and Management List
      • Campaign Workflows Template
      • Brand Awareness Strategy Rollout Plan Template

      2.2.1 Assets Creation List

      (60-120 min.)

      Inventory

      Inventory existing assets to create the Asset Creation and Management List.

      Assign

      Assign the persons responsible, accountable, consulted, and informed of the development of each asset, using the RACI model in the template. Ensure you identify and collaborate with the right stakeholders.

      Prioritize

      Prioritize and add release dates.

      Communicate

      Update status and communicate regularly. Make the list with links to the assets available to the extended team to consult as needed.

      2.2.2 Rollout Plan

      (60-120 min.)

      Inventory

      Map out your strategy deployment in the Brand Awareness Strategy Rollout Plan Template and workflow in the Campaign Workflow Template.

      Assign

      Assign the persons responsible, accountable, consulted, and informed for each tactic, using the RACI model in the template. Ensure you identify and collaborate with the right stakeholders.

      Prioritize

      Prioritize and adjust the timeline accordingly.

      Communicate

      Update status and communicate regularly. Make the list with links to the assets available to the extended team to consult as needed.

      Band Awareness Strategy Rollout Plan
      A strategy rollout plan typically includes the following:

      • Identifying a cross-functional team and resources to develop the assets and deploy the tactics.
      • Listing the various assets to create and manage.
      • A timeline with key milestones, deadlines, and release dates.
      • A communication plan to keep stakeholders informed and aligned with the strategy and tactics.
      • Ongoing performance monitoring.
      • Constant adjustments and improvements to the strategy based on data collected and feedback received.

      Start building brand awareness

      Step 2.3 Establish key performance indicators (KPIs), monitor, and optimize on an ongoing basis.

      Total duration: 3.5-4.5 hours

      Objective

      Brand awareness is built over a long period of time and must be continuously monitored in several ways. Measuring and monitoring the effectiveness of your brand awareness activities will allow you to constantly adjust your tactics and continue to build awareness.

      Output

      This step will provide you with a snapshot of your current level of brand awareness and interactions with the brand, and allow you to set up the tools for ongoing monitoring and optimization.

      Participants

      • Head of branding
      • Digital marketing manager

      MarTech
      May require you to:

      • Register to an Online Survey Platform(free version or subscription), or
      • Use, setup, or installation of platforms like CRM and/or Marketing Automation Platform.
      • Use Google Analytics or other tracking tools.
      • Use social media and campaign management tools.

      Tools

      • Brand Awareness Strategy and Tactics Template

      2.2.2 Rollout Plan

      (60-120 min.)

      Measure

      Monitor and record the strategy performance metrics in slides 12 to 15 of the Brand Awareness Strategy and Tactics template, and gauge its performance against preset KPIs in slide 11. Make ongoing improvements to the strategy and assets.

      Communicate

      The same slides in which you monitor strategy performance can be used to report on the results of the current strategy to key stakeholders on a monthly or quarterly basis, as appropriate.

      Take this opportunity to inform stakeholders of any adjustments you plan to make to the existing plan to improve its performance. Since brand awareness is built over time, be sure to evaluate the results based on how long the strategy has been in place before making major changes.

      Consult SoftwareReviews website to find the best survey, brand monitoring and feedback, and MarTech platforms, or contact one of our analysts for more personalized assistance and guidance

      Measuring brand strategy performance
      There are two ways to measure and monitor your brand's performance on an ongoing basis.

      • By registering to brand monitoring and feedback platforms and tools like Meltwater, Hootsuite, Insights, Brand24, Qualtrics, and Wooltric.
      • Manually, using native analytics built in the platforms you're already using, such as Google and Social Media Analytics, or by gathering customer feedback through surveys, or calculating CAC, ROI, and more in spreadsheets.

      SoftwareReviews can help you choose the right platform for your need. We also equip you with manual tools, available with the Diagnose Brand Health to Improve Business Growthblueprint to measure:

      • Surveys and interviews questions and lists.
      • External and internal factor analysis.
      • Digital and financial metrics analysis.
      • Executive presentation to report on performance.

      Related SoftwareReviews research

      An image of the title page for SoftwareReviews Create a Buyer Persona and Journey. An image of the title page for SoftwareReviews Diagnose Brand Health to Improve Business Growth.

      Create a Buyer Persona and Journey

      Get deeper buyer understanding and achieve product-market fit, with easier access to market and sales

      • Reduce time and resources wasted chasing the wrong prospects.
      • Increase open and click-through rates.
      • Perform more effective sales discovery.
      • Increase win rate.

      Diagnose Brand Health to Improve Business Growth

      Have a significant and well-targeted impact on business success and growth by knowing how your brand performs, identifying areas of improvement, and making data-driven decisions to fix them.

      • Increase brand awareness and equity.
      • Build trust and improve customer retention and loyalty.
      • Achieve higher and faster growth.

      Bibliography

      Aaker, David. "Managing Brand Equity." Simon & Schuster, 1991.
      "6 Factors for Brands to Consider While Designing Their Communication." Lokus Design, 23 Sept. 2022.
      "20 Advocacy Marketing Statistics You Need to Know." Social Toaster, n.d.
      Bazilian, Emma. "How Millennials and Baby Boomers Consume User-Generated Content And what brands can learn from their preferences." Adweek, January 2, 2017.
      B2B International, a Gyro: company, B2B Blog - Why Human-To-Human Marketing Is the Next Big Trend in a Tech-Obsessed World.
      B2B International, a Gyro: company, The State of B2B Survey 2019 - Winning with Emotions: How to Become Your Customer's First Choice.
      Belyh, Anastasia. "Brand Ambassador 101:Turn Your Personal Brand into Cash." Founder Jar, December 6, 2022.
      Brand Master Academy.com.
      Businesswire, a Berkshire Hathaway Company, "Stackla Survey Reveals Disconnect Between the Content Consumers Want & What Marketers Deliver." February 20, 2019.
      Chamat, Ramzi. "Visual Design: Why First Impressions Matter." 8 Ways, June 5, 2019.
      Cognism. "21 Tips for Building a LinkedIn Personal Brand (in B2B SaaS)."
      Curleigh, James. "How to Enhance and Expand a Global Brand." TED.
      "2019 Edelman Trust Barometer." Edelman.
      Erskine, Ryan. "22 Statistics That Prove the Value of Personal Branding." Entrepreneur, September 13, 2016.
      Forbes, Steve. "Branding for Franchise Success: How To Achieve And Maintain Brand Consistency Across A Franchise Network?" Forbes, 9 Feb. 2020.
      Godin, Seth. "Define: Brand." Seth's Blog, 30 Dec. 2009,
      Houragan, Stephen. "Learn Brand Strategy in 7 Minutes (2023 Crash Course)." YouTube.
      Jallad, Revecka. "To Convert More Customers, Focus on Brand Awareness." Forbes, October 22, 2019.
      Kingsbury, Joe, et al. "2021 B2B Thought Leadership Impact Study." Edelman, 2021.
      Kunsman, Todd. "The Anatomy of an Employee Influencer." EveryoneSocial, September 8, 2022.
      Landor, Walter. A Brand New World: The Fortune Guide to the 21st Century. Time Warner Books, 1999.
      Liedke, Lindsay. "37+ Branding Statistics For 2023: Stats, Facts & Trends." Startup Bonsai, January 2, 2023.
      Millman, Debbie. "How Symbols and Brands Shape our Humanity." TED, 2019.
      Nenova, Velina. "21 Eye-Opening B2B Marketing Statistics to Know in 2023." Techjury, February 9, 2023.
      Perrey, Jesko et al., "The brand is back: Staying relevant in an accelerating age." McKinsey & Company, May 1, 2015.
      Schaub, Kathleen. "Social Buying Meets Social Selling: How Trusted Networks Improve the Purchase Experience." LinkedIn Business, April 2014.
      Sopadjieva, Emma et al. "A Study of 46,000 Shoppers Shows That Omnichannel Retailing Works." Harvard Business Review, January 3, 2017.
      Shaun. "B2B Brand Awareness: The Complete Guide 2023." B2B House. 2023.
      TopRank Marketing, "2020 State of B2B Influencer Marketing Research Report." Influencer Marketing Report.

      Release management

      • Buy Link or Shortcode: {j2store}9|cart{/j2store}
      • Related Products: {j2store}9|crosssells{/j2store}
      • Up-Sell: {j2store}9|upsells{/j2store}
      • member rating overall impact: 10.0/10
      • member rating average dollars saved: $35,731
      • member rating average days saved: 20
      • Parent Category Name: Infra and Operations
      • Parent Category Link: /infra-and-operations
      Today's world requires frequent and fast deployments. Stay in control with release management.

      Become a Transformational CIO

      • Buy Link or Shortcode: {j2store}86|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Innovation
      • Parent Category Link: /innovation
      • Business transformations are happening, but CIOs are often involved only when it comes time to implement change. This makes it difficult for the CIO to be perceived as an organizational leader.
      • CIOs find it difficult to juggle operational activities, strategic initiatives, and involvement in business transformation.
      • CIOs don’t always have the IT organization structured and mobilized in a manner that facilitates the identification of transformation opportunities, and the planning for and the implementation of organization-wide change.

      Our Advice

      Critical Insight

      • Don’t take an ad hoc approach to transformation.
      • You’re not in it alone.
      • Your legacy matters

      Impact and Result

      • Elevate your stature as a business leader.
      • Empower the IT organization to act with a business mind first, and technology second.
      • Create a high-powered IT organization that is focused on driving lasting change, improving client experiences, and encouraging collaboration across the entire enterprise.
      • Generate opportunities for organizational growth, as manifested through revenue growth, profit growth, new market entry, new product development, etc.

      Become a Transformational CIO Research & Tools

      Start here – read the Executive Brief

      Read our Executive Brief to find out why you should undergo an evolution in your role as a business leader, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Are you ready to lead transformation?

      Determine whether you are ready to focus your attention on evolving your role.

      • Become a Transformational CIO – Phase 1: Are You Ready to Lead Transformation?

      2. Build business partnerships

      Create a plan to establish key business partnerships and position IT as a co-leader of transformation.

      • Become a Transformational CIO – Phase 2: Build Business Partnerships
      • Partnership Strategy Template

      3. Develop the capability to transform

      Mobilize the IT organization and prepare for the new mandate.

      • Become a Transformational CIO – Phase 3: Develop the Capability to Transform
      • Transformation Capability Assessment

      4. Shift IT’s focus to the customer

      Align IT with the business through a direct, concentrated focus on the customer.

      • Become a Transformational CIO – Phase 4: Shift IT’s Focus to the Customer
      • Transformational CIO Value Stream Map Template
      • Transformational CIO Business Capability Map Template

      5. Adopt a transformational approach to leadership

      Determine the key behaviors necessary for transformation success and delegate effectively to make room for new responsibilities.

      • Become a Transformational CIO – Phase 5: Adopt a Transformational Approach to Leadership
      • Office of the CIO Template

      6. Sustain the transformational capability

      Track the key success metrics that will help you manage transformation effectively.

      • Become a Transformational CIO – Phase 6: Sustain the Transformational Capability
      • Transformation Dashboard
      [infographic]

      Workshop: Become a Transformational CIO

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Determine Readiness to Become a Transformational CIO

      The Purpose

      Understand stakeholder and executive perception of the CIO’s performance and leadership.

      Determine whether the CIO is ready to lead transformation.

      Key Benefits Achieved

      Decision to evolve role or address areas of improvement as a pre-requisite to becoming a transformational CIO.

      Activities

      1.1 Select data collection techniques.

      1.2 Conduct diagnostic programs.

      1.3 Review results and define readiness.

      Outputs

      Select stakeholder and executive perception of the CIO

      Decision as to whether to proceed with the role evolution

      2 Build Business Partnerships

      The Purpose

      Identify potential business partners and create a plan to establish key partnerships.

      Key Benefits Achieved

      An actionable set of initiatives that will help the CIO create valuable partnerships with internal or external business stakeholders.

      Activities

      2.1 Identify potential business partners.

      2.2 Evaluate and prioritize list of potential partners.

      2.3 Create a plan to establish the target partnerships.

      Outputs

      Partnership strategy

      3 Establish IT’s Ability to Transform

      The Purpose

      Make the case and plan for the development of key capabilities that will enable the IT organization to handle transformation.

      Key Benefits Achieved

      A maturity assessment of critical capabilities.

      A plan to address maturity gaps in preparation for a transformational mandate.

      Activities

      3.1 Define transformation as a capability.

      3.2 Assess the current and target transformation capability maturity.

      3.3 Develop a roadmap to address gaps.

      Outputs

      Transformation capability assessment

      Roadmap to develop the transformation capability

      4 Shift IT’s Focus to the Customer

      The Purpose

      Gain an understanding of the end customer of the organization.

      Key Benefits Achieved

      A change in IT mindset away from a focus on operational activities or internal customers to external customers.

      A clear understanding of how the organization creates and delivers value to customers.

      Opportunities for business transformation.

      Activities

      4.1 Analyze value streams that impact the customer.

      4.2 Map business capabilities to value streams.

      Outputs

      Value stream maps

      Business capability map

      5 Establish Transformation Leadership and Sustain the Capability

      The Purpose

      Establish a formal process for empowering employees and developing new leaders.

      Create a culture of continuous improvement and a long-term focus.

      Key Benefits Achieved

      Increased ability to sustain momentum that is inherent to business transformations.

      Better strategic workforce planning and a clearer career path for individuals in IT.

      A system to measure IT’s contribution to business transformation.

      Activities

      5.1 Set the structure for the office of the CIO.

      5.2 Assess current leadership skills and needs.

      5.3 Spread a culture of self-discovery.

      5.4 Maintain the transformation capability.

      Outputs

      OCIO structure document

      Transformational leadership dashboard

      Explore the Secrets of Oracle Cloud Licensing

      • Buy Link or Shortcode: {j2store}142|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: 5 Average Days Saved
      • member rating average days saved: After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.
      • Parent Category Name: Licensing
      • Parent Category Link: /licensing
      • Organizations are considering moving workloads to the cloud; however, they often struggle to understand Oracle's licensing and services models.
      • Complexity of licensing and high price tags can make the renewal process an overwhelming experience.
      • Oracle’s SaaS applications are the most mature, but Oracle’s on-premises E-Business Suite still has functionality gaps in comparison to Oracle’s cloud apps.

      Our Advice

      Critical Insight

      • Understand the Oracle agenda. Oracle has established a unique approach to their cloud offerings – they want all of your workloads on the Red Stack.
      • Communicate effectively. Be aware that Oracle will reach out to members at your organization at various levels. Having your executives on the same page is critical to successfully managing Oracle.
      • Negotiate hard. Oracle needs the deal more than the customer. Oracle's top leaders are heavily incentivized to drive massive cloud adoption and increase Oracle's share price. Use this to your advantage.

      Impact and Result

      • Conducting business with Oracle is not typical compared to other vendors. To emerge successfully from a commercial transaction with Oracle, customers must learn the “Oracle way” of conducting business, which includes a best-in-class sales structure, highly unique contracts, and license use policies coupled with a hyper-aggressive compliance function.
      • Leverage cloud spend to retire support on shelf-ware licenses, or gain virtualization rights for an on-premises environment.
      • Map out the process of how to negotiate from a position of strength, examining terms and conditions, discount percentages, and agreement pitfalls.
      • Carefully review key clauses in the Oracle Cloud Services Agreement to avoid additional spend and compliance risks.

      Explore the Secrets of Oracle Cloud Licensing Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should explore the secrets of Oracle Cloud licensing, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Evaluate licensing requirements

      Review current licensing options and models to determine which cloud products will most appropriately fit the organization's environment.

      • Oracle Cloud Services Agreement Terms and Conditions Evaluation Tool
      [infographic]

      Stabilize Infrastructure & Operations During Work-From-Anywhere

      • Buy Link or Shortcode: {j2store}309|cart{/j2store}
      • member rating overall impact: 9.0/10 Overall Impact
      • member rating average dollars saved: After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.
      • member rating average days saved: Read what our members are saying
      • Parent Category Name: Strategy and Organizational Design
      • Parent Category Link: /strategy-and-organizational-design

      Work-from-anywhere isn’t going anywhere. IT Infrastructure & Operations needs to:

      • Rebuild trust in the stability of IT infrastructure and operations.
      • Identify gaps created from the COVID-19 rush to remote work.
      • Identify how IT can better support remote workers.

      IT went through an initial crunch to enable remote work. It’s time to be proactive and learn from our mistakes.

      Our Advice

      Critical Insight

      • The nature of work has fundamentally changed. IT departments must ensure service continuity, not for how the company worked in 2019, but how the company is working now and will be working tomorrow.
      • Revisit the basics. Don’t focus on becoming an innovator until you have improved network access, app access, file access, and collaboration tools.
      • Aim for near-term innovation. Once you’re a trusted operator, become a business partner by directly empowering end users at home and in the office.

      Impact and Result

      Build a work-from-anywhere strategy that resonates with the business.

      • Strengthen the foundations of collaboration tools, app access, file access, network access, and endpoint standards.
      • Explore opportunities to strengthen IT operations.
      • Proactively help the business through employee experience monitoring and facilities optimization.

      Stabilize Infrastructure & Operations During Work-From-Anywhere Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should build a strategy for improving how well IT infrastructure and operations support work-from-anywhere, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Stabilize IT infrastructure

      Ensure your fundamentals are solid.

      2. Update IT operations

      Revisit your practices to ensure you can effectively operate in work-from-anywhere.

      3. Optimize IT infrastructure & operations

      Offer additional value to the business by proactively addressing these items.

      • Roadmap Tool

      Infographic

      Workshop: Stabilize Infrastructure & Operations During Work-From-Anywhere

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Stabilize IT Infrastructure

      The Purpose

      Strengthen the foundations of IT infrastructure.

      Key Benefits Achieved

      Improved end-user experience

      Stabilized environment

      Activities

      1.1 Review work-from-anywhere framework and identify capability gaps.

      1.2 Review diagnostic results to identify satisfaction gaps.

      1.3 Record improvement opportunities for foundational capabilities: collaboration, network, file access, app access.

      1.4 Identify deliverables and opportunities to provide value for each.

      Outputs

      Projects and initiatives to stabilize IT infrastructure

      Deliverables and opportunities to provide value for foundational capabilities

      2 Update IT Operations and Optimize

      The Purpose

      Update IT operational practices to support work-from-anywhere more effectively.

      Key Benefits Achieved

      Improved IT operations

      Activities

      2.1 Identify IT infrastructure and operational capability gaps.

      2.2 Record improvement opportunities for DRP & BCP.

      2.3 Record improvement opportunities for endpoint and systems management practices.

      2.4 Record improvement opportunities for IT operational practices.

      2.5 Explore office space optimization and employee experience monitoring.

      Outputs

      Projects and initiatives to update IT operations to better support work-from-anywhere

      Longer-term strategic initiatives

      Deliverables and opportunities to provide value for each capability

      Accelerate Digital Transformation With a Digital Factory

      • Buy Link or Shortcode: {j2store}93|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $50,000 Average $ Saved
      • member rating average days saved: 20 Average Days Saved
      • Parent Category Name: Innovation
      • Parent Category Link: /innovation
      • Organizational challenges are hampering digital transformation (DX) initiatives.
      • The organization’s existing digital factory is failing to deliver value.
      • Designing a successful digital factory is a difficult process.

      Our Advice

      Critical Insight

      To remain competitive, enterprises must deliver products and services like a startup or a digital native enterprise. This requires enterprises to:

      • Understand how digital native enterprises are designed.
      • Understand the foundations of good design: purpose, organizational support, and leadership.
      • Understand the design of the operating model: structure and organization, management practices, culture, environment, teams, technology platforms, and meaningful metrics and KPIs.

      Impact and Result

      Organizations that implement this project will draw benefits in the following aspects:

      • Gain awareness and understanding of various aspects that hamper DX.
      • Set the right foundations by having clarity of purpose, alignment on organizational support, and the right leadership in place.
      • Design an optimal operating model by setting up the right organizational structures, management practices, lean and optimal governance, agile teams, and an environment that promotes productivity and wellbeing.
      • Finally, set the right measures and KPIs.

      Accelerate Digital Transformation With a Digital Factory Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to understand the importance of a well-designed digital factory.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Build the case

      Collect data and stats that will help build a narrative for digital factory.

      • Digital Factory Playbook

      2. Lay the foundation

      Discuss purpose, mission, organizational support, and leadership.

      3. Design the operating model

      Discuss organizational structure, management, culture, teams, environment, technology, and KPIs.

      [infographic]

      Workshop: Accelerate Digital Transformation With a Digital Factory

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Build the case

      The Purpose

      Understand and gather data and stats for factors impacting digital transformation.

      Develop a narrative for the digital factory.

      Key Benefits Achieved

      Identification of key pain points and data collected

      Narrative to support the digital factory

      Activities

      1.1 Understand the importance and urgency of digital transformation (DX).

      1.2 Collect data and stats on the progress of DX initiatives.

      1.3 Identify the factors that hamper DX and tie them to data/stats.

      1.4 Build the narrative for the digital factory (DF) using the data/stats.

      Outputs

      Identification of factors that hamper DX

      Data and stats on progress of DX

      Narrative for the digital factory

      2 Lay the foundation

      The Purpose

      Discuss the factors that impact the success of establishing a digital factory.

      Key Benefits Achieved

      A solid understanding and awareness that successful digital factories have clarity of purpose, organizational support, and sound leadership.

      Activities

      2.1 Discuss

      2.2 Discuss what organizational support the digital factory will require and align and commit to it.

      2.3 Discuss reference models to understand the dynamics and the strategic investment.

      2.4 Discuss leadership for the digital age.

      Outputs

      DF purpose and mission statements

      Alignment and commitment on organizational support

      Understanding of competitive dynamics and investment spread

      Develop the profile of a digital leader

      3 Design the operating model (part 1)

      The Purpose

      Understand the fundamentals of the operating model.

      Understand the gaps and formulate the strategies.

      Key Benefits Achieved

      Design of structure and organization

      Design of culture aligned with organizational goals

      Management practices aligned with the goals of the digital factory

      Activities

      3.1 Discuss structure and organization and associated organizational pathologies, with focus on hierarchy and silos, size and complexity, and project-centered mindset.

      3.2 Discuss the importance of culture and its impact on productivity and what shifts will be required.

      3.3 Discuss management for the digital factory, with focus on governance, rewards and compensation, and talent management.

      Outputs

      Organizational design in the context of identified pathologies

      Cultural design for the DF

      Management practices and governance for the digital factory

      Roles/responsibilities for governance

      4 Design the operating model (part 2)

      The Purpose

      Understand the fundamentals of the operating model.

      Understand the gaps and formulate the strategies.

      Key Benefits Achieved

      Discuss agile teams and the roles for DF

      Environment design that supports productivity

      Understanding of existing and new platforms

      Activities

      4.1 Discuss teams and various roles for the DF.

      4.2 Discuss the impact of the environment on productivity and satisfaction and discuss design factors.

      4.3 Discuss technology and tools, focusing on existing and future platforms, platform components, and organization.

      4.4 Discuss design of meaningful metrics and KPIs.

      Outputs

      Roles for DF teams

      Environment design factors

      Platforms and technology components

      Meaningful metrics and KPIs

      Master M&A Cybersecurity Due Diligence

      • Buy Link or Shortcode: {j2store}261|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $12,399 Average $ Saved
      • member rating average days saved: 5 Average Days Saved
      • Parent Category Name: Governance, Risk & Compliance
      • Parent Category Link: /governance-risk-compliance

      This research is designed to help organizations who are preparing for a merger or acquisition and need help with:

      • Understanding the information security risks associated with the acquisition or merger.
      • Avoiding the unwanted possibility of acquiring or merging with an organization that is already compromised by cyberattackers.
      • Identifying best practices for information security integration post merger.

      Our Advice

      Critical Insight

      The goal of M&A cybersecurity due diligence is to assess security risks and the potential for compromise. To succeed, you need to look deeper.

      Impact and Result

      • A repeatable methodology to systematically conduct cybersecurity due diligence.
      • A structured framework to rapidly assess risks, conduct risk valuation, and identify red flags.
      • Look deeper by leveraging compromise diagnostics to increase confidence that you are not acquiring a compromised entity.

      Master M&A Cybersecurity Due Diligence Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Start here – read the Executive Brief

      Read our concise Executive Brief to find out how to master M&A cyber security due diligence, review Info-Tech’s methodology, and understand how we can support you in completing this project.

      [infographic]

      Perform an Agile Skills Assessment

      • Buy Link or Shortcode: {j2store}153|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $32,166 Average $ Saved
      • member rating average days saved: 15 Average Days Saved
      • Parent Category Name: Development
      • Parent Category Link: /development
      • Your organization is trying to address the key delivery challenges you are facing. Early experiments with Agile are starting to bear fruit.
      • As part of maturing your Agile practice, you want to evaluate if you have the right skills and capabilities in place.

      Our Advice

      Critical Insight

      • Focusing on the non-technical skills can yield significant returns for your products, your team, and your organization. These skills are what should be considered as the real Agile skills.

      Impact and Result

      • Define the skills and values that are important to your organization to be successful at being Agile.
      • Put together a standard criterion for measurement of the attainment of given skills.
      • Define the roadmap and communication plan around your agile assessment.

      Perform an Agile Skills Assessment Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should perform an agile skills assessment. review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Take stock of the Agile skills and values important to you

      Confirm the list of Agile skills that you wish to measure.

      • Perform an Agile Skills Assessment – Phase 1: Take Stock of the Agile Skills and Values Important to You
      • Agile Skills Assessment Tool
      • Agile Skills Assessment Tool Example

      2. Define an assessment method that works for you

      Define what it means to attain specific agile skills through a defined ascension path of proficiency levels, and standardized skill expectations.

      • Perform an Agile Skills Assessment – Phase 2: Define an Assessment Method That Works for You

      3. Plan to assess your team

      Determine the roll-out and communication plan that suits your organization.

      • Perform an Agile Skills Assessment – Phase 3: Plan to Assess Your Team
      • Agile Skills Assessment Communication and Roadmap Plan
      • Agile Skills Assessment Communication and Roadmap Plan Example
      [infographic]

      Workshop: Perform an Agile Skills Assessment

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Define Agile Skills and Maturity Levels

      The Purpose

      Learn about and define the Agile skills that are important to your organization.

      Define the different levels of attainment when it comes to your Agile skills.

      Define the standards on a per-role basis.

      Key Benefits Achieved

      Get a clear view of the Agile skills important into meet your Agile transformation goals in alignment with organizational objectives.

      Set a clear standard for what it means to meet your organizational standards for Agile skills.

      Activities

      1.1 Review and update the Agile skills relevant to your organization.

      1.2 Define your Agile proficiency levels to evaluate attainment of each skill.

      1.3 Define your Agile team roles.

      1.4 Define common experience levels for your Agile roles.

      1.5 Define the skill expectations for each Agile role.

      Outputs

      A list of Agile skills that are consistent with your Agile transformation

      A list of proficiency levels to be used during your Agile skills assessment

      A confirmed list of roles that you wish to measure on your Agile teams

      A list of experience levels common to Agile team roles (example: Junior, Intermediate, Senior)

      Define the skill expectations for each Agile role

      Reduce Shadow IT With a Service Request Catalog

      • Buy Link or Shortcode: {j2store}302|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $129,999 Average $ Saved
      • member rating average days saved: 35 Average Days Saved
      • Parent Category Name: Asset Management
      • Parent Category Link: /asset-management
      • Shadow IT: The IT team is regularly surprised to discover new products within the organization, often when following up on help desk tickets or requests for renewals from business users or vendors.
      • Renewal Management: The contracts and asset teams need to be aware of upcoming renewals and have adequate time to review renewals.
      • Over-purchasing: Contracts may be renewed without a clear picture of usage, potentially renewing unused applications.

      Our Advice

      Critical Insight

      There is a direct correlation between service delivery dissatisfaction and increases in shadow IT. Whether the goal is to reduce shadow IT or gain control, improved customer service and fast delivery are key to making lasting changes.

      Impact and Result

      Our blueprint will help you design a service that draws the business to use it. If it is easier for them to buy from IT than it is to find their own supplier, they will use IT.

      A heavy focus on customer service, design optimization, and automation will provide a means for the business to get what they need, when they need it, and provide visibility to IT and security to protect organizational interests.

      This blueprint will help you:

      • Design the request service
      • Design the request catalog
      • Build the request catalog
      • Market the service

      Reduce Shadow IT With a Service Request Catalog Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Reduce Shadow IT With a Service Request Catalog – A step-by-step document that walks you through creation of a request service management program.

      Use this blueprint to create a service request management program that provides immediate value.

      • Reduce Shadow IT With a Service Request Catalog Storyboard

      2. Nonstandard Request Assessment – A template for documenting requirements for vetting and onboarding new applications.

      Use this template to define what information is needed to vet and onboard applications into the IT environment.

      • Nonstandard Request Assessment

      3. Service Request Workflows – A library of workflows used as a starting point for creating and fulfilling requests for applications and equipment.

      Use this library of workflows as a starting point for creating and fulfilling requests for applications and equipment in a service catalog.

      • Service Request Workflows

      4. Application Portfolio – A template to organize applications requested by the business and identify which items are published in the catalog.

      Use this template as a starting point to create an application portfolio and request catalog.

      • Application Portfolio

      5. Reduce Shadow IT With a Service Request Catalog Communications Template – A presentation and communications plan to announce changes to the service and introduce a catalog.

      Use this template to create a presentation and communications plan for launching the new service and service request catalog.

      • Reduce Shadow IT with a Service Request Catalog Communications Template
      [infographic]

      Workshop: Reduce Shadow IT With a Service Request Catalog

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Design the Service

      The Purpose

      Collaborate with the business to determine service model.

      Collaborate with IT teams to build non-standard assessment process.

      Key Benefits Achieved

      Designed a service for service requests, including new product intake.

      Activities

      1.1 Identify challenges and obstacles.

      1.2 Complete customer journey map.

      1.3 Design process for nonstandard assessments.

      Outputs

      Nonstandard process.

      2 Design the Catalog

      The Purpose

      Design the service request catalog management process.

      Key Benefits Achieved

      Ensure the catalog is kept current and is integrated with IT service catalog if applicable.

      Activities

      2.1 Determine what will be listed in the catalog.

      2.2 Determine process to build and maintain the catalog, including roles, responsibilities, and workflows.

      2.3 Define success and determine metrics.

      Outputs

      Catalog scope.

      Catalog design and maintenance plan.

      Defined success metrics

      3 Build and Market the Catalog

      The Purpose

      Determine catalog contents and how requests will be fulfilled.

      Key Benefits Achieved

      Catalog framework and service level agreements will be defined.

      Create communications documents.

      Activities

      3.1 Determine how catalog items will be displayed.

      3.2 Complete application categories for catalog.

      3.3 Create deployment categories and SLAs.

      3.4 Design catalog forms and deployment workflows.

      3.5 Create roadmap.

      3.6 Create communications plan.

      Outputs

      Catalog workflows and SLAs.

      Roadmap.

      Communications deck.

      4 Breakout Groups – Working Sessions

      The Purpose

      Create an applications portfolio.

      Prepare to populate the catalog.

      Key Benefits Achieved

      Portfolio and catalog contents created.

      Activities

      4.1 Using existing application inventory, add applications to portfolio and categorize.

      4.2 Determine which applications should be in the catalog.

      4.3 Determine which applications are packaged and can be easily deployed.

      Outputs

      Application Portfolio.

      List of catalog items.

      Further reading

      Reduce Shadow IT With a Service Request Catalog

      Foster business partnerships with sourcing-as-a-service.

      Analyst Perspective

      Improve the request management process to reduce shadow IT.

      In July 2022, Ivanti conducted a study on the state of the digital employee experience, surveying 10,000 office workers, IT professionals, and C-suite executives. Results of this study indicated that 49% of employees are frustrated by their tools, and 26% of employees were considering quitting their jobs due to unsuitable tech. 42% spent their own money to gain technology to improve their productivity. Despite this, only 21% of IT leaders prioritized user experience when selecting new tools.

      Any organization’s workers are expected to be productive and contribute to operational improvements or customer experience. Yet those workers don’t always have the tools needed to do the job. One option is to give the business greater control, allowing them to choose and acquire the solutions that will make them more productive. Info-Tech's blueprint Embrace Business-Managed Applications takes you down this path.

      However, if the business doesn’t want to manage applications, but just wants have access to better ones, IT is positioned to provide services for application and equipment sourcing that will improve the employee experience while ensuring applications and equipment are fully managed by the asset, service, and security teams.

      Improving the request management and deployment practice can give the business what they need without forcing them to manage license agreements, renewals, and warranties.

      Photo of Sandi Conrad

      Sandi Conrad
      ITIL Managing Professional
      Principal Research Director, IT Infrastructure & Operations,
      Info-Tech Research Group

      Your challenge

      This research is designed to help organizations that are looking to improve request management processes and reduce shadow IT.

      Shadow IT: The IT team is regularly surprised to discover new products within the organization, often when following up on help desk tickets or requests for renewals from business users or vendors.

      Renewal management: The contracts and asset teams need to be aware of upcoming renewals and have adequate time to review renewals.

      Over-purchasing and over-spending: Contracts may be renewed without a clear picture of utilization, potentially renewing unused applications. Applications or equipment may be purchased at retail price where corporate, government, or educational discounts exist.

      Info-Tech Insight

      To increase the visibility of the IT environment, IT needs to transform the request management process to create a service that makes it easier for the business to access the tools they need rather than seeking them outside of the organization.

      609
      Average number of SaaS applications in large enterprises

      40%
      On average, only 60% of provisioned SaaS licenses are used, with the remaining 40% unused.

      — Source: Zylo, SaaS Trends for IT Leaders, 2022

      Common obstacles

      Too many layers of approvals and a lack of IT workers makes it difficult to rethink service request fulfillment.

      Delays: The business may not be getting the applications they need from IT to do their jobs or must wait too long to get the applications approved.

      Denials: Without IT’s support, the business is finding alternative options, including SaaS applications, as they can be bought and used without IT’s input or knowledge.

      Threats: Applications that have not been vetted by security or installed without their knowledge may present additional threats to the organization.

      Access: Self-serve isn’t mature enough to support an applications catalog.

      A diagram that shows the number of SaaS applications being acquired outside of IT is increasing year over year, and that business units are driving the majority of SaaS spend.

      8: average number of applications entering the organization every 30 days

      — Source: Zylo, SaaS Trends for Procurement, 2022

      Info-Tech’s approach

      Improve the request management process to create sourcing-as-a-service for the business.

      • Improve customer service
      • Reduce shadow IT
      • Gain control in a way that keeps the business happy

      1. Design the service

      Collaborate with the business

      Identify the challenges and obstacles

      Gain consensus on priorities

      Design the service

      2. Design the catalog

      Determine catalog scope

      Create a process to build and maintain the catalog

      Define metrics for the request management process

      3. Build the catalog

      Determine descriptions for catalog items

      Create definitions for license types, workflows, and SLAs

      Create application portfolio

      Design catalog forms and workflows

      4. Market the service

      Create a roadmap

      Determine messaging

      Build a communications plan

      Blueprint deliverables

      Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:

      Communications Presentation

      Photo of Communications Presentation

      Application Portfolio

      Photo of Application Portfolio

      Visio Library

      Photo of Visio Library

      Nonstandard Request Assessment

      Photo of Nonstandard Request Assessment

      Create a request management process and service catalog to improve delivery of technology to the business

      Evolve Your Business Through Innovation

      • Buy Link or Shortcode: {j2store}330|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Innovation
      • Parent Category Link: /innovation
      • Innovation teams are tasked with the responsibility of ensuring that their organizations are in the best position to succeed while the world is in a period of turmoil, chaos, and uncertainty.
      • CIOs have been expected to help the organization transition to remote work and collaboration instantaneously.
      • CEOs are under pressure to redesign, and in some cases reinvent, their business model to cope with and compete in a new normal.

      Our Advice

      Critical Insight

      It is easy to get swept up during a crisis and cling to past notions of normal. Unfortunately, there is no controlling the fact that things have changed fundamentally, and it is now incumbent upon you to help your organization adapt and evolve. Treat this as an opportunity because that is precisely what this is.

      Impact and Result

      There are some lessons we can learn from innovators who have succeeded through past crises and from those who are succeeding now.

      There are a number of tactics an innovation team can employ to help their business evolve during this time:

      1. Double down on digital transformation (DX)
      2. Establish a foresight capability
      3. Become a platform for good

      Evolve Your Business Through Innovation Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Evolve your business through innovation

      Download our guide to learn what you can do to evolve your business and innovate your way through uncertainty.

      • Evolve Your Business Through Innovation Storyboard
      [infographic]

      Optimize the IT Operations Center

      • Buy Link or Shortcode: {j2store}449|cart{/j2store}
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A
      • Parent Category Name: Operations Management
      • Parent Category Link: /i-and-o-process-management
      • Your team’s time is burned up by incident response.
      • Manual repetitive work uses up expensive resources.
      • You don’t have the visibility to ensure the availability the business demands.

      Our Advice

      Critical Insight

      • Sell the project to the business.
      • Leverage the Operations Center to improve IT Operations.

      Impact and Result

      • Clarify lines of accountability and metrics for success.
      • Implement targeted initiatives and track key metrics for continual improvement.

      Optimize the IT Operations Center Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should Optimize the IT Operations Center, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Lightning Phase: Pluck Low-Hanging Fruit for Quick Wins

      Get quick wins to demonstrate early value for investments in IT Operations.

      • Optimize the IT Operations Center – Lightning Phase: Pluck Low-Hanging Fruit for Quick Wins

      2. Get buy-in

      Get buy-in from business stakeholders by speaking their language.

      • Optimize the IT Operations Center – Phase 1: Get Buy-In
      • IT Operations Center Prerequisites Assessment Tool
      • IT Operations Center Stakeholder Buy-In Presentation
      • IT Operations Center Continual Improvement Tracker

      3. Define accountability and metrics

      Formalize process and task accountability and develop targeted metrics.

      • Optimize the IT Operations Center – Phase 2: Define Accountability and Metrics
      • IT Operations Center RACI Charts Template

      4. Assess gaps and prioritize initiatives

      Identify pain points and determine the top solutions.

      • Optimize the IT Operations Center – Phase 3: Assess Gaps and Prioritize Initiatives
      • IT Operations Center Gap and Initiative Tracker
      • IT Operations Center Initiative Prioritization Tool

      5. Launch initiatives and track metrics

      Lay the foundation for implementation and continual improvement.

      • Optimize the IT Operations Center – Phase 4: Launch Initiatives and Track Metrics
      [infographic]

      Workshop: Optimize the IT Operations Center

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Check Foundation

      The Purpose

      Ensure base maturity in IT Operations processes.

      Key Benefits Achieved

      Verify that foundation is in place to proceed with Operations Center project.

      Activities

      1.1 Evaluate base maturity.

      Outputs

      IT Operations Center Prerequisites Assessment Tool

      2 Define Accountabilities

      The Purpose

      Define accountabilities for Operations processes and tasks.

      Key Benefits Achieved

      Documented accountabilities.

      Activities

      2.1 Pluck low-hanging fruit for quick wins.

      2.2 Complete process RACI.

      2.3 Complete task RACI.

      Outputs

      Project plan

      Process RACI

      Task RACI

      3 Map the Challenge

      The Purpose

      Define metrics and identify accountabilities and gaps.

      Key Benefits Achieved

      List of initiatives to address pain points.

      Activities

      3.1 Define metrics.

      3.2 Define accountabilities.

      3.3 Identify gaps.

      Outputs

      IT Operations Center Gap and Initiative Tracker

      4 Build Action Plan

      The Purpose

      Develop an action plan to boost KPIs.

      Key Benefits Achieved

      Action plan and success criteria.

      Activities

      4.1 Prioritize initiatives.

      Outputs

      IT Operations Center Initiative Prioritization Tool

      5 Map Out Implementation

      The Purpose

      Build an implementation plan for continual improvement.

      Key Benefits Achieved

      Continual improvement against identified metrics and KPIs.

      Activities

      5.1 Build implementation plan.

      Outputs

      IT Operations Center Continual Improvement Tracker

      Further reading

      Optimize the IT Operations Center

      Stop burning budget on non-value-adding activities.

      ANALYST PERSPECTIVE

      The Network Operations Center is not in Kansas anymore.

      "The old-school Network Operations Center of the telecom world was heavily peopled and reactionary. Now, the IT Operations Center is about more than network monitoring. An effective Operations Center provides visibility across the entire stack, generates actionable alerts, resolves a host of different incidents, and drives continual improvement in the delivery of high-quality services.
      IT’s traditional siloed approach cannot provide the value the business demands. The modern Operations Center breaks down these silos for the end-to-end view required for a service-focused approach."

      Derek Shank,
      Research Analyst, Infrastructure & Operations
      Info-Tech Research Group

      Our understanding of the problem

      This Research Is Designed For:

      • IT Operations Managers
      • IT Infrastructure Managers
      • CIOs

      This Research Will Help You:

      • Improve reliability of services.
      • Reduce the cost of incident response.
      • Reduce the cost of manual repetitive work (MRW).

      This Research Will Also Assist

      • Business Analysts
      • Project Managers
      • Business Relationship Managers

      This Research Will Help Them

      • Develop appropriate non-functional requirements.
      • Integrate non-functional requirements into solution design and project implementation.

      Executive Summary

      Situation

      • Your team’s time is burned up by incident response.
      • MRW burns up expensive resources.
      • You don’t have the visibility to ensure the availability the business demands.

      Complication

      • The increasing complexity of technology has resulted in siloed teams of specialists.
      • The business views IT Operations as a cost center and doesn’t want to provide resources to support improvement initiatives.

      Resolution

      • Pluck low-hanging fruit for quick wins.
      • Obtain buy-in from business stakeholders by speaking their language.
      • Clarify lines of accountability and metrics for success.
      • Implement targeted initiatives and track key metrics for continual improvement.

      Info-Tech Insight

      1. Sell the project to the business. Your first job is a sales job because executive sponsorship is key to project success.
      2. Worship the holy trinity of metrics: impact of downtime, cost of incident response, and time spent on manual repetitive work (MRW).
      3. Invest in order to profit. Improving the Operations Center takes time and money. Expect short-term pain to realize long-term gain.

      The role of the Network Operations Center has changed

      • The old approach was technology siloed and the Network Operations Center (NOC) only cared about the network.
      • The modern Operations Center is about ensuring high availability of end-user services, and requires cross-functional expertise and visibility across all the layers of the technology stack.
      A pie chart is depicted. The data displayed on the chart, in decreasing order of size, include: Applications; Servers; LAN; WAN; Security; Storage. Source: Metzler, n.d.

      Most organizations lack adequate visibility

      • The rise of hybrid cloud has made environments more complex, not less.
      • The increasing complexity makes monitoring and incident response more difficult than ever.
      • Only 31% of organizations use advanced monitoring beyond what is offered by cloud providers.
      • 69% perform no monitoring, basic monitoring, or rely entirely on the cloud provider’s monitoring tools.
      A Pie chart is depicted. Two data are represented on the chart. The first, representing 69% of the chart, is: Using no monitoring, basic monitoring, or relying only on the cloud vendor's monitoring. the second, representing 31% of the chart, is Using advanced monitoring beyond what cloud vendors provide. Source: InterOp ITX, 2018

      Siloed service level agreements cannot ensure availability

      You can meet high service level agreements (SLAs) for functional silos, but still miss the mark for service availability. The business just wants things to work!

      this image contains Info-Tech's SLA-compliance rating chart, which displays the categories: Available, behaving as expected; Slow/degraded; and Unavailable, for each of: Webserver; Database; Storage; Network; Application; and, Business Service

      The cost of downtime is massive

      Increasing reliance on IT makes downtime hurt more than ever.
      98% of enterprises lose $100,000+.
      81% of enterprises lose $300,000+ per hour of downtime.

      This is a bar graph, showing the cost per hour of downtime, against the percentage of enterprises.

      Source: ITIC, 2016

      IT is asked to do more with less

      Most IT budgets are staying flat or shrinking.

      57% of IT departments expect their budget to stay flat or to shrink from 2018 to 2019.

      This image contains a pie chart with two data, one is labeled: Increase; representing 43% of the chart. The other datum is labeled: Shrink or stay flat, and represents 57% of the chart.

      Unify and streamline IT Operations

      A well-run Operations Center ensures high availability at reasonable cost. Improving your Operations Center results in:

      • Higher availability
      • Increased reliability
      • Improved project capacity
      • Higher business satisfaction

      Measure success with the holy trinity of metrics

      Focus on reducing downtime, cost of incident response, and MRW.

      This image contains a Funnel Chart showing the inputs: Downtime; Cost of Incident Response; MRW; and the output: Reduce for continual improvement

      Start from the top and employ a targeted approach

      Analyze data to get buy-in from stakeholders, and use our tools and templates to follow the process for continual improvement in IT Operations.

      This image depicts a cycle, which includes: Data analysis; Executive Sponsorship; Success Criteria; Gap Assessment; Initiatives; Tracking & Measurement

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful.”

      Guided Implementation

      “Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track."

      Workshop

      "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place."

      Consulting

      "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks used throughout all four options

      Optimize the IT Operations Center – project overview

      Launch the Project

      Identify Enterprise Services

      Identify Line of Business Services

      Complete Service Definitions

      Best-Practice Toolkit

      🗲 Pluck Low-Hanging Fruit for Quick Wins

      1.1 Ensure Base Maturity Is in Place

      1.2 Make the Case

      2.1 Define Accountabilities

      2.2 Define Metrics

      3.1 Assess Gaps

      3.2 Plan Initiatives

      4.1 Lay Foundation

      4.2 Launch and Measure

      Guided Implementations

      Discuss current state.

      Review stakeholder presentation.

      Review RACIs.

      Review metrics.

      Discuss gaps.

      Discuss initiatives.

      Review plan and metric schedule.

      Onsite Workshop Module 1:

      Clear understanding of project objectives and support obtained from the business.

      Module 2:

      Enterprise services defined and categorized.

      Module 3:

      LOB services defined based on user perspective.

      Module 4:

      Service record designed according to how IT wishes to communicate to the business.

      Phase 1 Results:

      Stakeholder presentation

      Phase 2 Results:
      • RACIs
      • Metrics
      Phase 3 Results:
      • Gaps list
      • Prioritized list of initiatives
      Phase 4 Results:
      • Implementation plan
      • Continual improvement tracker

      Workshop overview

      Contact your account representative or email Workshops@InfoTech.com for more information.

      Pre-Workshop Workshop Day 1 Workshop Day 2 Workshop Day 3 Workshop Day 4
      Activities

      Check Foundation

      Define Accountabilities

      Map the Challenge

      Build Action Plan

      Map Out Implementation

      1.1 Ensure base maturity.

      🗲 Pluck low-hanging fruit for quick wins.

      2.1 Complete process RACI.

      2.2 Complete task RACI.

      3.1 Define metrics.

      3.2 Define accountabilities.

      3.2 Identify gaps.

      4.1 Prioritize initiatives.

      5.1 Build implementation plan.

      Deliverables
      1. IT Operations Center Prerequisites Assessment Tool
      1. IT Operations Center RACI Charts Template
      1. IT Operations Center Gap and Initiative Tracker
      1. IT Operations Center Initiative Prioritization Tool
      1. IT Operations Center Continual Improvement Tracker

      PHASE 🗲

      Pluck Low-Hanging Fruit for Quick Wins

      Optimize the IT Operations Center

      Conduct a ticket-trend analysis

      Generate reports on tickets from your IT service management (ITSM) tool. Look for areas that consume the most resources, such as:

      • Recurring tickets.
      • Tickets that have taken a long time to resolve.
      • Tickets that could have been resolved at a lower tier.
      • Tickets that were unnecessarily or improperly escalated.

      Identify issues

      Analyze the tickets:

      • Look for recurring tickets that may indicate underlying problems.
      • Ask tier 2 and 3 technicians to flag tickets that could have been resolved at a lower tier.
      • Identify painful and/or time consuming service requests.
      • Flag any manual repetitive work.

      Write the issues on a whiteboard.

      Oil & Gas IT reduces manual repetitive maintenance work

      CASE STUDY
      Industry Oil & Gas
      Source Interview

      Challenge

      The company used a webserver to collect data from field stations for analytics. The server’s version did not clear its cache – it filled up its own memory and would not overwrite, so it would just lock up and have to be rebooted manually.

      Solution

      The team found out that the volumes and units of data would cause the memory to fill at a certain time of the month. They wrote a script to reboot the machine and set up a planned outage during the appropriate weekend each month.

      Results

      The team never had to do manual reboots again – though they did have to tweak their reboot script not to rely on their calendar, after a shift in production broke the pattern between memory consumption and the calendar.

      Rank the issues

      🗲.1.1 10 minutes

      1. Assign each participant five sticky dots to use for voting.
      2. Have each participant place any number of dots beside the issue(s) of their choice.
      3. Count the dots and rank the top three most important issues.

      INPUT

      • List of issues

      OUTPUT

      • Top three issues

      Materials

      • Whiteboard
      • Markers
      • Sticky dots

      Participants

      • Operations Manager
      • Infrastructure Manager
      • I&O team members

      Brainstorm solutions

      🗲.1.2 10 minutes

      1. Write the three issues at the top of a whiteboard, each at the head of its own column.
      2. Focusing on one issue at a time, brainstorm potential solutions for each issue. Have one person write all the proposed solutions on the board beneath the issue.

      Info-Tech Best Practice

      Do not censor or evaluate the proposed solutions at this time. During brainstorming, focus on coming up with as many potential solutions as possible, no matter how infeasible or outlandish.

      INPUT

      • Top three issues

      OUTPUT

      • Potential solutions

      Materials

      • Whiteboard
      • Markers

      Participants

      • Operations Manager
      • Infrastructure Manager
      • I&O team members

      Evaluate and rank potential solutions

      🗲.1.3 30 minutes

      1. Score the solutions from 1-5 on each of the two dimensions:
      • Attainability
      • Probable efficacy
    • Identify the top scoring solution for each issue. In the event of a tie, vote to determine the winner.
    • Info-Tech Insight

      Quick wins are the best of both worlds. To get a quick win, pick a solution that is both readily attainable and likely to have high impact.

      INPUT

      • Potential solutions

      OUTPUT

      • Ranked list of solutions

      Materials

      • Whiteboard
      • Markers

      Participants

      • Operations Manager
      • Infrastructure Manager
      • I&O team members

      Develop metrics to measure the effectiveness of solutions

      You should now have a top potential solution for each pain point.

      For each pain point and proposed solution, identify the metric that would indicate whether the solution had been effective or not. For example:

      • Pain point: Too many unnecessary escalations for SharePoint issues.
      • Solution: Train tier 1 staff to resolve SharePoint tickets.
      • Metric: % of SharePoint tickets resolved at tier 1.

      Design solutions

      • Some solutions explain themselves. E.g., hire an extra service desk person.
      • Others require more planning and design, as they involve a bespoke solution. E.g., improve asset management process or automate onboarding of new users.
      • For the solutions that require planning, take the time to design each solution fully before rushing to implement it.

      Build solutions

      • Build any of the solutions that require building. For example, any scripting for automations requires the writing of those scripts, and any automated ticket routing requires configuration of your ITSM tool.
      • Part of the build phase for many solutions should also involve designing the tests of those solutions.

      Test solutions – refine and iterate

      • Think about the expected outcome and results of the solutions that require testing.
      • Test each solution under production-like circumstances to see if the results and behavior are as expected.
      • Refine and iterate upon the solutions as necessary, and test again.

      Implement solutions and measure results

      • Before implementing each solution, take a baseline measurement of the metric that will measure success.
      • Implement the solutions using your change management process.
      • After implementation, measure the success of the solution using the appropriate metric.
      • Document the results and judge whether the solution has been effective.

      Use the top result as a case study to obtain buy-in

      Your most effective solution will make a great case study.

      Write up the results and input the case study into the IT Operations Center Stakeholder Buy-In Presentation.

      This image contains a screenshot of info-tech's default format for presenting case studies.

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts

      this is a picture of an Info-Tech Analyst
      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.
      The following are sample activities that will be conducted by Info-Tech analysts with your team:
      🗲.1.2 This image contains a screenshot from section 🗲.1.2 of this blueprint.

      Identify issues

      Look for areas that aren’t working optimally.

      🗲.1.3 this image contains a screenshot from section 🗲.1.3 of this blueprint.

      Evaluate and rank potential solutions

      Sort the wheat from the chaff and plan for quick wins.

      PHASE 1

      Get Buy-In

      Optimize the IT Operations Center

      Step 1.1: Ensure Base Maturity Is in Place

      This step will walk you through the following activities:

      • Assess maturity of base IT Operations processes.

      Outcomes of this step

      • Completed IT Operations Center Prerequisites Assessment Tool

      Base processes underpin the Operations Center

      • Before you optimize your Operations Center, you should have foundational ITSM processes in place: service desk, and incident, problem, and change management.
      • Attempting to optimize Operations before it rests on a solid foundation can only lead to frustration.

      IT Operations Center

      • Service Desk
      • Incident Management
      • Problem Management
      • Change Management

      Info-Tech Insight

      ITIL isn’t dead. New technology such as cloud solutions and advanced monitoring tools have transformed how ITSM processes are implemented, but have not obviated them.

      Assess maturity of prerequisite processes

      1.1.1 IT Operations Center Prerequisites Assessment Tool

      • Don’t try to prematurely optimize your Operations Center.
      • Before undertaking this project, you should already have a base level of maturity in the four foundational IT Operations processes.
      • Complete the IT Operations Center Prerequisites Assessment Tool to assess your current level in service desk, incident management, problem management, and change management.
      this image contains a screenshot from Info-Tech's IT Operations Center Prerequisite Assessment

      Make targeted improvements on prerequisite processes if necessary

      If there are deficiencies in any of your foundational processes, take the time to remedy those first before proceeding with Optimize the IT Operations Center. See Info-Tech’s other blueprints:

      Standardize the Service Desk

      Strengthen your service desk to build a strong ITSM foundation.

      Incident and Problem Management

      Don’t let persistent problems govern your department.

      Optimize Change Management

      Turn and face the change with a right-sized change management process.

      Step 1.2: Make the Case

      This step will walk you through the following activities:

      • Estimate the impact of downtime for top five applications.
      • Estimate the cost of incident response.
      • Estimate the cost of MRW.
      • Set success metrics and estimate the ROI of the Operations Center project.
      • IT Operations Center Stakeholder Buy-In Presentation

      Obtaining buy-in is critical

      Buy-in from top-level stakeholders is critical to the success of the project.

      Before jumping into your initiatives, take the time to make the case and bring the business on board.

      Factors that “prevent us from improving the NOC”

      This image contains a graph of factors that prevent us from improving the NOC. In decreasing order, they include: Lack of strategic guidance from our vendors; The unwillingness of our management to accept new risk; Lack of adequate software tools; Our internal processes; Lack of management vision; Lack of funding; and Lack of personnel resources. There is a red circle drawn around the last three entries, with the words: Getting Buy-in Removes the Top Three Roadblocks to Improvement!. Source: Metzier, n.d

      List your top five applications

      List your top five applications for business criticality.

      Don’t agonize over decisions at this point.

      Generally, the top applications will be customer facing, end-user facing for the most critical business units, or critical for health and safety.

      Estimate impact of downtime

      • Come up with a rough, back-of-the-napkin estimate of the hourly cost of downtime for each application.
      • Complete page two of the IT Operations Center Stakeholder Buy-In Presentation.
      • Estimate loss of revenue per hour, loss of productivity per hour, and IT cost per incident resolution hour.
      • Pull a report on incident hours/outages in the past year from your ITSM tool. Multiply the total cost per incident hour by the incident hours per year to determine the current cost per year of service disruptions for each service.
      • Add up the cost for each of the top five services.
      • Now you can show the business a hard value number that quantifies your availability issues.

      Estimate salary cost of non-value-adding work

      Complete page three of the IT Operations Center Stakeholder Buy-In Presentation.

      • Estimate annual wage cost of incident response: multiply incident response hours per year (take from your ITSM tool) by the average hourly wage of incident responders.
      • Estimate annual cost of MRW: multiply MRW hours per year (take from ITSM tool or from time-keeping tool, or use best guess based on talking to staff members) by the average hourly wage of IT staff performing MRW.
      • Add the two numbers together to calculate the non-value-adding IT salary cost per year.
      • Express the previous number as a percentage of total IT salary. Everything that is not incident response or MRW is value-adding work.

      Now you have the holy trinity of metrics: set some targets

      The holy trinity of metrics:

      • Cost of downtime
      • % of salary on incident response
      • % of salary on MRW

      You want to reduce the above numbers. Set some back-of-the-napkin targets for percentage reductions for each of these areas. These are high-level metrics that business stakeholders will care about.

      Take your best guess at targets. Higher maturity organizations will have less potential for reduction from a percentage point of view (eventually you hit diminishing returns), while organizations just beginning to optimize their Operations Center have the potential for huge gains.

      Calculate the potential gains of targets

      Complete page five of the IT Operations Center Stakeholder Buy-In Presentation.

      • Multiply the targeted/estimated % reductions of the costs by your current costs to determine the potential savings/benefits.
      • Do a back-of-the napkin estimate of the cost of the Operations Center improvement project. Use reasonable numbers for cost of personnel time and cost of tools, and be sure to include ongoing personnel time costs – your time isn’t free and continual improvement takes work and effort.
      • Calculate the ROI.

      Fill out the case study

      • Complete page six of the IT Operations Center Stakeholder Buy-In Presentation. If you completed the lightning phase, use the results of your own quick win project(s) as an example of feasibility.
      • If you did not complete the lightning phase, delete this slide, or use an example of what other organizations have achieved to demonstrate feasibility.
      This image contains a screenshot of info-tech's default format for presenting case studies.

      Present to stakeholders

      • Deliver the presentation to key stakeholders.
      • Focus on the high-level story that the current state is costing real dollars and wages, and that these losses can be minimized through process improvements.
      • Be up front that many of the numbers are based on estimates, but be prepared to defend the reasonableness of the estimates.

      Gain buy-in and identify project sponsor

      • If the business is on board with the project, determine one person to be the executive sponsor for the project. This person should have a strong desire to see the project succeed, and should have some skin in the game.

      Formalize communication with the project sponsor

      • Establish how you will communicate with the sponsor throughout the project (e.g. weekly or monthly e-mail updates, bi-weekly meetings).
      • Set up a regular/recurring cadence and stick to it, so it can be put on auto-pilot. Be clear about who is responsible for initiating communication and sticking to the reporting schedule.

      Info-Tech Insight

      Tailor communication to the sponsor. The project sponsor is not the project manager. The sponsor’s role is to drive the project forward by allocating appropriate resources and demonstrating highly visible support to the broader organization. The sponsor should be kept in the loop, but not bothered with minutiae.

      Note the starting numbers for the holy trinity

      Use the IT Operations Center Continual Improvement Tracker:

      • Enter your starting numbers for the holy trinity of metrics.
      • After planning and implementing initiatives, this tracker will be used to update against the holy trinity to assess the success of the project on an ongoing basis and to drive continual improvement.

      PHASE 2

      Define Accountability and Metrics

      Optimize the IT Operations Center

      Step 2.1: Define Accountabilities

      This step will walk you through the following activities:

      • Formalize RACI for key processes.
      • Formalize RACI for key tasks.

      Outcomes of this step

      • Completed RACIs

      List key Operations Center processes

      Compile a list of processes that are key for the Operations Center.

      These processes should include the four foundational processes:

      • Service Desk
      • Incident Management
      • Problem Management
      • Change Management

      You may also want to include processes such as the following:

      • Event Management
      • Configuration Management

      Avoid listing processes you have yet to develop – stick with those already playing a role in your current state.

      Formalize RACI for key processes

      Use the IT Operations Center RACI Charts Template. Complete a RACI for each of the key processes involved in the IT Operations Center.

      RACI:

      • Responsible (does the work on a day-to-day basis)
      • Accountable (reviews, signs off, and is held accountable for outcomes)
      • Consulted (input is sought to feed into decision making)
      • Informed (is given notification of outcomes)

      As a best practice, no more than one person should be responsible or accountable for any given process. The same person can be both responsible and accountable for a given process, or it could be two different people.

      Avoid making someone accountable for a process if they do not have full visibility into the process for appropriate oversight, or do not have time to give the process sufficient attention.

      Formalize RACI for IT tasks

      Now think about the actual tasks or work that goes on in IT. Which roles and individuals are accountable for which tasks or pieces of work?

      In this case, more than one role/person can be listed as responsible or accountable in the RACI because we’re talking about types or categories of work. No conflict will occur because these individuals will be responsible or accountable for different pieces of work or individual tasks of the same type. (e.g. all service desk staff are responsible for answering phones and inputting tickets into the ITSM tool, but no more than one staff member is responsible for the input of any given ticket from a specific phone call).

      Step 2.2: Define Metrics

      This step will walk you through the following activities:

      • Cascade operational metrics from the holy trinity.
      • Evaluate metrics and identify key performance indicators (KPIs).
      • Cascade performance assessment (PA) metrics to support KPIs.
      • Build feedback loop for PA metrics.

      Outcomes of this step

      • KPIs
      • PA metrics

      Metrics must span across silos for shared accountability

      To adequately support the business goals of the organization, IT metrics should span across functional silos.

      Metrics that span across silos foster shared accountability across the IT organization.

      Metrics supported by all groups

      three grain silos are depicted. below, are the words IT Groups, with arrows pointing from the words to each of the three silos.

      Cascade operational metrics from the holy trinity

      Focus on the holy trinity of metrics.

      From these, cascade down to operational metrics that contribute to the holy trinity. It is possible that an operational metric may support more than one trinity metric. For example:

      a flow chart is depicted. two input circles point toward a central circle, and two output circles point away. the input circles include: Cost of Downtime; Cost of Incident Response. The central circle reads: Mean time to restore service. the output circles include the words: Tier 1 Resolution Rate; %% of Known Errors Captured in ITSM Tool.

      Evaluate metrics and identify KPIs

        • Evaluate your operational metrics and determine which ones are likely to have the largest impact on the holy trinity of metrics.
        • Identify the ten metrics likely to have the most impact: these will be your KPIs moving forward.
        • Enter these KPIs into the IT Operations Center Continual Improvement Tracker.
        this image depicts a cycle around the term KPI. The cycle includes: Objective; Measurement; optimization; strategy; performance; evaluation

      Beware how changing variables/context can affect metrics

      • Changes in context can affect metrics drastically. It’s important to keep the overall context in mind to avoid being led astray by certain numbers taken in isolation.
      • For example, a huge hiring spree might exhaust the stock of end-user devices, requiring time to procure hardware before the onboarding tickets can be completely fulfilled. You may have improved your onboarding process through automation, but see a large increase in average time to onboard a new user. Keep an eye out for such anomalies or fluctuations, and avoid putting too much stock in any single operational KPI.
      • Remember, operational KPIs are just a heuristic tool to support the holy trinity of metrics.

      Determine accountability for KPIs

      • For each operational KPI, assign one person to be accountable for that KPI.
      • Be sure the person in charge has the necessary authority and oversight over the processes and personnel that most affect that KPI – otherwise it makes little sense to hold the individual accountable.
      • Consulting your process RACIs is a good place to start.
      • Record the accountable person for each KPI in the IT Operations Center Continual Improvement Tracker.

      Info-Tech Best Practice

      Match accountability with authority. The person accountable for each KPI should be the one who has the closet and most direct control over the work and processes that most heavily impact that KPI.

      Cascade PA metrics to support KPIs

      KPIs are ultimately driven by how IT does its work, and how individuals work is driven by how their performance is assessed and evaluated.

      For the top KPIs, be sure there are individual PA metrics in place that support the KPI, and if not, develop the appropriate PA metrics.

      For example:

      • KPI: Mean time to resolve incidents
      • PA metric: % of escalations that followed SOP (e.g. not holding onto a ticket longer than supposed to)
      • KPI: Number of knowledge base articles written
      • PA metric: Number of knowledge base articles written/contributed to

      Communicate key changes in PA metrics

      Any changes from the previous step will take time and effort to implement and make stick.

      Changing people’s way of working is extremely difficult.

      Build a communication and implementation plan about rolling out these changes, emphasize the benefits for everyone involved, and get buy-in from the affected staff members.

      Build feedback loops for PA metrics

      Now that PA metrics support your Operations Center’s KPIs, you should create frequent feedback loops to drive and boost those PA metrics.

      Once per year or once per quarter is not frequent enough. Managers should meet with their direct reports at least monthly and review their reports’ performance against PA metrics.

      Use a “set it and forget it” implementation, such as a recurring task or meeting in your calendar.

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts

      this is a picture of an Info-Tech Analyst

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.
      The following are sample activities that will be conducted by Info-Tech analysts with your team:
      2.2.1 This image contains a screenshot from section 2.2.1 of this blueprint.

      Cascade operational metrics from the holy trinity

      Rank goals based on business impact and stakeholder pecking order.

      2.2.2 this image contains a screenshot from section 2.2.2 of this blueprint.

      Determine accountability for KPIs

      Craft a concise and compelling elevator pitch that will drive the project forward.

      PHASE 3

      Assess Gaps and Prioritize Initiatives

      Optimize the IT Operations Center

      Step 3.1: Assess Gaps

      This step will walk you through the following activities:

      • Assess visibility provided by monitoring.
      • Assess process workflows and identify areas for automation.
      • Assess requests and identify potential for automation.
      • Assess Operations Center staff capabilities.
      • Conduct a root cause analysis on the gaps/pain points.

      Outcomes of this step

      • List of gaps
      • List of root causes

      Measure current state of KPIs and identify lagging ones

      Take a baseline measurement of each operational KPI.

      If historical data is available, compare the present state measurement to data points collected over the last year or so.

      Review the measured KPIs.

      Identify any KPIs that seem lagging or low, or that may be particularly important to influence.

      Record lagging KPIs in the IT Operations Center Gap and Initiative Tracker tool.

      Assess visibility provided by monitoring

      List the top five most critical business services supported by IT.
      Assess the current state of your monitoring tools.

      For each business service, rate the level of visibility your monitoring tools allow from the following options:

      1. We have no visibility into the service, or lack visibility into crucial elements.
      2. We have basic visibility (up/down) into all the IT components that support the service.
      3. We have basic visibility (up/down) into the end service itself, in addition to all the IT components that make it up.
      4. We have some advanced visibility into some aspects of the service and/or its IT components.
      5. We have a full, end-to-end view of performance across all the layers of the stack, as well as the end business service itself.

      Identify where more visibility may be necessary

      For most organizations it isn’t practical to have complete visibility into everything. For the areas in which visibility is lacking into key services, think about whether more visibility is actually required or not. Consider some of the following questions:

      • How great is the impact of this service being unavailable?
      • Would greater visibility into the service significantly reduce the mean time to restore the service in the event of incidents?

      Record any deficiencies in the IT Operations CenterGap and Initiative Tracker tool.

      Assess alerting

      Assess alerting for your most critical services.

      Consider whether any of the following problems occur:

      • Often receive no alert(s) in the event of critical outages of key services (we find out about critical outages from the service desk).
      • We are regularly overwhelmed with too many alerts to investigate properly.
      • Our alerts are rarely actionable.
      • We often receive many false alerts.

      Identify areas for potential improvement in the managing of alerts. Record any deficiencies in the IT Operations Center Gap and Initiative Tracker tool.

      Assess process workflows and identify areas for automation

      Review your process flows for base processes such as Service Desk, Incident Management, Problem Management, and Change Management.

      Identify areas in the workflows where there may be defects, inefficiencies, or potential for improvement or automation.

      Record any deficiencies in the IT Operations Center Gap and Initiative Tracker tool.

      See the blueprint Prepare for Cognitive Service Management for process workflows and areas to look for automation possibilities.

      Prepare for Cognitive Service Management

      Make ready for AI-assisted IT operations.

      Assess requests and identify potential for automation

      • Assess the most common work orders or requests handled by the Operations Center group (i.e. this does not include requests fulfilled by the help desk).
      • Which work orders are the most painful? That is, what common work orders involve the greatest effort or the most manual work to fulfill?
      • Fulfillment of common, recurring work orders is MRW, and should be reduced or removed if possible.
      • Consider automation of certain work orders, or self-service delivery.
      • Record any deficiencies in the IT Operations Center Gap and Initiative Tracker tool.

      Assess Operations Center staff capabilities

      • Assess the skills and expertise of your team members.
      • Consider some of the following:
        • Are there team members who could perform their job more effectively by picking up certain skills or proficiencies?
        • Are there team members who have the potential to shift into more valuable or useful roles, given the appropriate training?
        • Are there individual team members whose knowledge is crucial for operations, and whose function cannot be taken up by others?

      Record any deficiencies in the IT Operations Center Gap and Initiative Tracker tool.

      Info-Tech Insight

      Train to avoid pain. All too often organizations expose themselves to significant key person risk by relying on the specialized skills and knowledge of one team member. Use cross training to remedy such single points of failure before the risk materializes.

      Brainstorm pain points

      Brainstorm any pain points not discussed in the previous areas.

      Pain points can be specific operational issues that have not yet been considered. For example:

      • Tom is overwhelmed with tickets.
      • Our MSP often breaches SLA.
      • We don’t have a training budget.

      Record any deficiencies in the IT Operations CenterGap and Initiative Tracker tool.

      Conduct a root cause analysis on the gaps/pain points

      • Pain points can often be symptoms of other deficiencies, or somewhat removed from the actual problem.
      • Using the 5 Whys, conduct a root cause analysis on the pain points for which the causes are not obvious.
      • For each pain point, ask “why” for a sequence of five times, attempting to proceed to the root cause of the issue. This root cause is the true gap that needs to be remedied to resolve the pain point.
      • For example:
        • The Wi-Fi network often goes down in the afternoon.
          • Why?: Its bandwidth gets overloaded.
          • Why?: Many people are streaming video.
          • Why?: There’s a live broadcast of a football game at that time.
        • Possible solutions:
          • Block access to the streaming services.
          • Project the game on a screen in a large conference room and encourage everyone to watch it there.

      Step 3.2: Plan Initiatives

      This step will walk you through the following activities:

      • Brainstorm initiatives to boost KPIs and address gaps.
      • Prioritize potential initiatives.
      • Decide which initiatives to include on the roadmap.

      Outcomes of this step

      • Targeted improvement roadmap

      Brainstorm initiatives to boost KPIs and address gaps

      Prioritize potential initiatives

      3.2.1 IT Operations Center Initiative Prioritization Tool

      • Use the IT Operations Center Initiative Prioritization Tool.
      • Enter the initiatives into the tool.
      • For each initiative, input the following ranking criteria:
        • The metric/KPI’s estimated degree of impact on the holy trinity.
        • The gap or pain point’s estimated degree of impact on the metric/KPI.
        • The initiative’s estimated degree of positive impact on the gap or pain point
        • The initiative’s attainability.
      • Estimate the resourcing capacity required for each initiative.
      • For accurate capacity assessment, input as “force include” all current in-flight projects handled by the Operations Center group (including those unrelated to the Operations Center project).

      Decide which initiatives to include on the roadmap

      • Not all initiatives will be worth pursuing – and especially not all at once.
      • Consider the results displayed on the final tab of the IT Operations CenterInitiative Prioritization Tool.
      • Based on the prioritization and taking capacity into account, decide which initiatives to include on your roadmap.
      • Sometimes, for operational or logistical reasons, it may make sense to schedule an initiative at a time other than its priority might dictate. Make such exceptions on a case-by-case basis.

      Assign an owner to each initiative, and provide resourcing

      • For each initiative, assign one person to be the owner of that initiative.
      • Be sure that person has the authority and the bandwidth necessary to drive the initiative forward.
      • Secure additional resourcing for any initiatives you want to include on your roadmap that are lacking capacity.

      Info-Tech Insight

      You must invest resources in order to reduce the time spent on non-value-adding work.

      "The SRE model of working – and all of the benefits that come with it – depends on teams having ample capacity for engineering work. If toil eats up that capacity, the SRE model can’t be launched or sustained. An SRE perpetually buried under toil isn’t an SRE, they are just a traditional long-suffering SysAdmin with a new title."– David N. Blank-Edelman

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts

      this is a picture of an Info-Tech Analyst

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.
      The following are sample activities that will be conducted by Info-Tech analysts with your team:
      3.1.1 This image contains a screenshot from section 3.1.1 of this blueprint.

      Conduct a root cause analysis on the gaps/pain points

      Find out the cause, so you can come up with solutions.

      3.2.1 this image contains a screenshot from section 3.2.1 of this blueprint.

      Prioritize potential initiatives

      Don’t try to boil the ocean. Target what’s manageable and what will have the most impact.

      PHASE 4

      Launch Initiatives and Track Metrics

      Optimize the IT Operations Center

      Step 4.1: Lay Foundation

      This step will walk you through the following activities:

      • Build initiative communication plan.
      • Develop a testing plan for each technical initiative.

      Outcomes of this step

      • Communication plan
      • Testing plan(s)

      Expect resistance to change

      • It’s not as simple as rolling out what you’ve designed.
      • Anything that affects people’s way of working will inevitably be met with suspicion and pushback.
      • Be prepared to fight the battle.
      • "The hardest part is culture. You must get people to see the value of automation. Their first response is ‘We've been doing it this way for 10 years, why do we need to do it another way?’ It's hard to get someone out of their comfort zone to learn something new, especially when they've been at an organization for 20 years. You need to give them incentives."– Cyrus Kalatbari, Senior IT Architect, Infrastructure/Cloud

      Communicate changes in advance, along with their benefits!

      • Communicate changes well in advance of the date(s) of implementation.
      • Emphasize the benefits of the changes – not just for the organization, but for employees and staff members.
      • Advance communication of changes helps make them more palatable, and builds trust in employees by making them feel informed of what’s going on.

      Involve IT staff in design and implementation of changes

      • As you communicate the coming changes, take the opportunity to involve any affected staff members who have not yet participated in the project.
      • Solicit their feedback and get them to help design and implement the initiatives that involve significant changes to their roles.

      Develop a testing plan for each technical initiative

      • Some initiatives, such as appointing a new change manager or hiring a new staff member, do not make sense to test.
      • On the other hand, technical initiatives such as automation scripts, new monitoring tools or dashboards, and changed alert thresholds should be tested thoroughly before implementation.
      • For each technical initiative, think about the expected results and performance if it were to run in production, and build a test plan to ensure it behaves as expected and there are no corner cases.

      Test technology initiatives and iterate if necessary

      • Test each technical initiative under a variety of circumstances, with as close an environment to production as possible.
      • Try to develop corner cases or unusual or unexpected situations, and see if any of these will break the functionality or produce unintended or unexpected results.
      • Document the results of the testing, and iterate on the initiative and test again if necessary.

      "The most important things – and the things that people miss – are prerequisites and expected results. People jump out and build scripts, then the scripts go into the ditch, and they end up debugging in production." – Darin Stahl, Research Director, Infrastructure & Operations

      Step 4.2: Launch and Measure

      This step will walk you through the following activities:

      • Launch initiatives and track adoption and effectiveness.
      • Investigate initiatives that appear ineffective.
      • Measure success with the holy trinity.

      Outcomes of this step

      • Continual improvement roadmap

      Establish a review cycle for each metric

      Info-Tech Best Practice

      Don’t measure what doesn’t matter. If a metric is not going to be reviewed or reported on for informational or decision-making purposes, it should not be tracked.

      Launch initiatives and track adoption and effectiveness

      • Launch the initiatives.
      • Some initiatives will need to proceed through your change management process in order to roll out, but others will not.
      • Track the adoption of initiatives that require it.
        • Some initiatives will require tracking of adoption, whereas others will not.
        • For example, hiring a new service desk staff member does not require tracking of adoption, but implementing a new process for ticket handling does.
        • The implementation plan should include a way to measure the adoption of such initiatives, and regularly review the numbers to see if the implementation has been successful.
      • For all initiatives, measure their effectiveness by continuing to track the KPI/metric that the initiative is intended to influence.

      Assess metrics according to review cycle for continual improvement

      • Assess metrics according to the review cycle.
      • Note whether metrics are improving in the right direction or not.
      • Correlate changes in the metrics with measures of the adoption of the initiatives – see whether initiatives that have been adopted are moving the needle on the KPIs they are intended to.

      Investigate initiatives that appear ineffective

      • If the adoption of an initiative has succeeded, but the expected impact of that initiative on the KPI has not taken place, investigate further and conduct a root causes analysis to determine why this is the case.
      • Sometimes, anomalies or fluctuations will occur that cause the KPI not to move in accordance with the success of the initiative. In this case, it’s just a fluke and the initiative can still be successful in influencing the KPI over the long term.
      • Other times, the initiative may prove mostly or entirely ineffective, either due to misdesign of the initiative itself, a change of circumstances, or other compounding factors or complexities. If the initiative proves ineffective, consider iterating modifications of the initiative and continuing to measure the effect on KPIs – or perhaps killing the initiative altogether.
      • Remember that experimentation is not a bad thing – it’s okay that not every initiative will always prove worthwhile.

      Measure success with the holy trinity

      • Report to business stakeholders on the effect on the holy trinity of metrics at least annually.
      • Calculate the ROI of the project after two years and compare the results to the targeted ROI you initially presented in the IT Operations Center Stakeholder Buy-In Presentation.
      This image contains a Funnel Chart showing the inputs: Downtime; Cost of Incident Response; MRW; and the output: Reduce for continual improvement

      Iterate on the Operations Center process for continual improvement

      This image depicts a cycle, which includes: Data analysis; Executive Sponsorship; Success Criteria; Gap Assessment; Initiatives; Tracking & Measurement

      If you want additional support, have our analysts guide you through this phase as part of an Info-Tech workshop

      Book a workshop with our Info-Tech analysts

      this is a picture of an Info-Tech Analyst

      • To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.
      • Info-Tech analysts will join you and your team onsite at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.
      • Contact your account manager (www.infotech.com/account), or email Workshops@InfoTech.com for more information.
      The following are sample activities that will be conducted by Info-Tech analysts with your team:
      4.1.1This image contains a screenshot from section 3.1.1 of this blueprint.

      Communicate changes in advance, along with their benefits!

      Rank goals based on business impact and stakeholder pecking order.

      4.1.2 this image contains a screenshot from section 3.2.1 of this blueprint.

      Develop a testing plan for each technical initiative

      Craft a concise and compelling elevator pitch that will drive the project forward.

      Research contributors and experts
      This is a picture of Cyrus Kalatbari, IT infrastructure/cloud architect

      Cyrus Kalatbari, IT Infrastructure/Cloud Architect

      Cyrus’ in-depth knowledge cutting across I&O and service delivery has enhanced the IT operations of multiple enterprise-class clients.

      This is a picture of Derek Cullen, Chief Technology Officer

      Derek Cullen, Chief Technology Officer

      Derek is a proven leader in managing enterprise-scale development, deployment, and integration of applications, platforms, and systems, with a sharp focus on organizational transformation and corporate change.

      This is a picture of Phil Webb, Senior Manager

      Phil Webb, Senior Manager – Unified Messaging and Mobility

      Phil specializes in service delivery for cloud-based and hybrid technology solutions, spanning requirements gathering, solution design, new technology introduction, development, integration, deployment, production support, change/release delivery, maintenance, and continuous improvement.

      This is a picture of Richie Mendoza, IT Services Delivery Consultant

      Richie Mendoza, IT Services Delivery Consultant

      Ritchie’s accomplishments include pioneering a cloud capacity management process and presenting to the Operations team and to higher management, while providing a high level of technical leadership in all phases of capacity management activities.

      This is a picture of Rob Thompson, Solutions Architect

      Rob Thomson, Solutions Architect

      Rob is an IT leader with a track record of creating and executing digital transformation initiatives to achieve the desired outcomes by integrating people, process, and technology into an efficient and effective operating model.

      Related Info-Tech research

      Create a Configuration Management Roadmap

      Right-size your CMDB to improve IT operations.

      Harness Configuration Management Superpowers

      Build a CMDB around the IT services that are most important to the organization.

      Develop an IT Infrastructure Services Playbook

      Automation, SDI, and DevOps – build a cheat sheet to manage a changing Infrastructure & Operations environment.

      Develop an Availability and Capacity Management Plan

      Manage capacity to increase uptime and reduce costs.

      Establish a Program to Enable Effective Performance Monitoring

      Maximize the benefits of infrastructure monitoring investments by diagnosing and assessing transaction performance, from network to server to end-user interface.

      Bibliography

      Baker, Dan, and Hal Baylor. “How Benchmarking & Streamlining NOC Operations Can Lower Costs & Boost Effectiveness.” Top Operator, Mar. 2017. Web.

      Blank-Edelman, David. Seeking SRE: Conversations About Running Production Systems at Scale. O'Reilly, 2018. Web.

      CA Technologies. “IT Transformation to Next-Generation Operations Centers: Assure Business Service Reliability by Optimizing IT Operations.” CA Technologies, 2014. Web.

      Ditmore, Jim. “Improving Availability: Where to Start.” Recipes for IT, n.d. Web.

      Ennis, Shawn. “A Phased Approach for Building a Next-Generation Network Operations Center.” Monolith Software, 2009. Web.

      Faraclas, Matt. “Why Does Infrastructure Operations Still Suck?” Ideni, 25 Feb. 2016. Web.

      InterOp ITX. “2018 State of the Cloud.” InterOp ITX, Feb. 2018. Web.

      ITIC. “Cost of Hourly Downtime Soars: 81% of Enterprises Say it Exceeds $300K On Average.” ITIC, 2 Aug. 2016. Web.

      Joe the IT Guy. “Availability Management Is Harder Than it Looks.” Joe the IT Guy, 10 Feb. 2016. Web.

      ---. “Do Quick Wins Exist for Availability Management?” Joe the IT Guy, 15 May 2014. Web.

      Lawless, Steve. “11 Top Tips for Availability Management.” Purple Griffon, 4 Jan. 2019. Web.

      Metzler, Jim. “The Next Generation Network Operations Center: How the Focus on Application Delivery is Redefining the NOC.” Ashton, Metzler & Associates, n.d. Web.

      Nilekar, Shirish. “Beyond Redundancy: Improving IT Availability.” Network Computing, 28 Aug. 2015. Web.

      Slocum, Mac. “Site Reliability Engineering (SRE): A Simple Overview.” O’Reilly, 16 Aug. 2018. Web.

      Spiceworks. “The 2019 State of IT.” Spiceworks, 2019. Web

      Define Your Cloud Vision

      • Buy Link or Shortcode: {j2store}448|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: $182,333 Average $ Saved
      • member rating average days saved: 28 Average Days Saved
      • Parent Category Name: Cloud Strategy
      • Parent Category Link: /cloud-strategy

      The cloud permeates the enterprise technology discussion. It can be difficult to separate the hype from the value. Should everything go to the cloud, or is that sentiment stoked by vendors looking to boost their bottom lines? Not everything should go to the cloud, but coming up with a systematic way to determine what belongs where is increasingly difficult as offerings get more complex.

      Our Advice

      Critical Insight

      Don’t think about the cloud as an inevitable next step for all workloads. The cloud is merely another tool in the toolbox, ready to be used when appropriate and put away when it’s not needed. Cloud-first isn’t always the way to go.

      Impact and Result

      • Evaluate workloads’ suitability for the cloud using Info-Tech’s methodology to select the optimal migration (or non-migration) path based on the value of cloud characteristics.
      • Codify risks tied to workloads’ cloud suitability and plan mitigations.
      • Build a roadmap of initiatives for actions by workload and risk mitigation.
      • Define a cloud vision to share with stakeholders.

      Define Your Cloud Vision Research & Tools

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Define Your Cloud Vision – A step-by-step guide to generating, validating, and formalizing your cloud vision.

      The cloud vision storyboard walks readers through the process of generating, validating and formalizing a cloud vision, providing a framework and tools to assess workloads for their cloud suitability and risk.

      • Define Your Cloud Vision – Phases 1-4

      2. Cloud Vision Executive Presentation – A document that captures the results of the exercises, articulating use cases for cloud/non-cloud, risks, challenges, and high-level initiative items.

      The executive summary captures the results of the vision exercise, including decision criteria for moving to the cloud, risks, roadblocks, and mitigations.

      • Cloud Vision Executive Presentation

      3. Cloud Vision Workbook – A tool that facilitates the assessment of workloads for appropriate service model, delivery model, support model, and risks and roadblocks.

      The cloud vision workbook comprises several assessments that will help you understand what service model, delivery model, support model, and risks and roadblocks you can expect to encounter at the workload level.

      • Cloud Vision Workbook
      [infographic]

      Workshop: Define Your Cloud Vision

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Understand the Cloud

      The Purpose

      Align organizational goals to cloud characteristics.

      Key Benefits Achieved

      An understanding of how the characteristics particular to cloud can support organizational goals.

      Activities

      1.1 Generate corporate goals and cloud drivers.

      1.2 Identify success indicators.

      1.3 Explore cloud characteristics.

      1.4 Explore cloud service and delivery models.

      1.5 Define cloud support models and strategy components.

      1.6 Create state summaries for the different service and delivery models.

      1.7 Select workloads for further analysis.

      Outputs

      Corporate cloud goals and drivers

      Success indicators

      Current state summaries

      List of workloads for further analysis

      2 Assess Workloads

      The Purpose

      Evaluate workloads for cloud value and action plan.

      Key Benefits Achieved

      Action plan for each workload.

      Activities

      2.1 Conduct workload assessment using the Cloud Strategy Workbook tool.

      2.2 Discuss assessments and make preliminary determinations about the workloads.

      Outputs

      Completed workload assessments

      Workload summary statements

      3 Identify and Mitigate Risks

      The Purpose

      Identify and plan to mitigate potential risks in the cloud project.

      Key Benefits Achieved

      A list of potential risks and plans to mitigate them.

      Activities

      3.1 Generate a list of risks and potential roadblocks associated with the cloud.

      3.2 Sort risks and roadblocks and define categories.

      3.3 Identify mitigations for each identified risk and roadblock

      3.4 Generate initiatives from the mitigations.

      Outputs

      List of risks and roadblocks, categorized

      List of mitigations

      List of initiatives

      4 Bridge the Gap and Create the Strategy

      The Purpose

      Clarify your vision of how the organization can best make use of cloud and build a project roadmap.

      Key Benefits Achieved

      A clear vision and a concrete action plan to move forward with the project.

      Activities

      4.1 Review and assign work items.

      4.2 Finalize the decision framework for each of the following areas: service model, delivery model, and support model.

      4.3 Create a cloud vision statement

      Outputs

      Cloud roadmap

      Finalized task list

      Formal cloud decision rubric

      Cloud vision statement

      5 Next Steps and Wrap-Up

      The Purpose

      Complete your cloud vision by building a compelling executive-facing presentation.

      Key Benefits Achieved

      Simple, straightforward communication of your cloud vision to key stakeholders.

      Activities

      5.1 Build the Cloud Vision Executive Presentation

      Outputs

      Completed cloud strategy executive presentation

      Completed Cloud Vision Workbook.

      Further reading

      Define Your Cloud Vision

      Define your cloud vision before it defines you

      Analyst perspective

      Use the cloud’s strengths. Mitigate its weaknesses.

      The cloud isn’t magic. It’s not necessarily cheaper, better, or even available for the thing you want it to do. It’s not mysterious or a cure-all, and it does take a bit of effort to systematize your approach and make consistent, defensible decisions about your cloud services. That’s where this blueprint comes in.

      Your cloud vision is the culmination of this effort all boiled down into a single statement: “This is how we want to use the cloud.” That simple statement should, of course, be representative of – and built from – a broader, contextual strategy discussion that answers the following questions: What should go to the cloud? What kind of cloud makes sense? Should the cloud deployment be public, private, or hybrid? What does a migration look like? What risks and roadblocks need to be considered when exploring your cloud migration options? What are the “day 2” activities that you will need to undertake after you’ve gotten the ball rolling?

      Taken as a whole, answering these questions is difficult task. But with the framework provided here, it’s as easy as – well, let’s just say it’s easier.

      Jeremy Roberts

      Research Director, Infrastructure and Operations

      Info-Tech Research Group

      Executive Summary

      Your Challenge

      • You are both extrinsically motivated to move to the cloud (e.g. by vendors) and intrinsically motivated by internal digital transformation initiatives.
      • You need to define the cloud’s true value proposition for your organization without assuming it is an outsourcing opportunity or will save you money.
      • Your industry, once cloud-averse, is now normalizing the use of cloud services, but you have not established a basic cloud vision from which to develop a strategy at a later point.

      Common Obstacles

      • Organizations jump to the cloud before defining their cloud vision and without any clear plan for realizing the cloud’s benefits.
      • Many organizations have a foot in the cloud already, but these decisions have been made in an ad hoc rather than systematic fashion.
      • You lack a consistent framework to assess your workloads’ suitability for the cloud.

      Info-Tech's Approach

      • Evaluate workloads’ suitability for the cloud using Info-Tech’s methodology to select the optimal migration (or non-migration) path based on the value of cloud characteristics.
      • Codify risks tied to workloads’ cloud suitability and plan mitigations.
      • Build a roadmap of initiatives for actions by workload and risk mitigation.
      • Define a cloud vision to share with stakeholders.

      Info-Tech Insight: 1) Base migration decisions on cloud characteristics. If your justification for the migration is simply getting your workload out of the data center, think again. 2) Address the risks up front in your migration plan. 3) The cloud changes roles and calls for different skill sets, but Ops is here to stay.

      Your challenge

      This research is designed to help organizations who need to:

      • Identify workloads that are good candidates for the cloud.
      • Develop a consistent, cost-effective approach to cloud services.
      • Outline and mitigate risks.
      • Define your organization’s cloud archetype.
      • Map initiatives on a roadmap.
      • Communicate your cloud vision to stakeholders so they can understand the reasons behind a cloud decision and differentiate between different cloud service and deployment models.
      • Understand the risks, roadblocks, and limitations of the cloud.

      “We’re moving from a world where companies like Oracle and Microsoft and HP and Dell were all critically important to a world where Microsoft is still important, but Amazon is now really important, and Google also matters. The technology has changed, but most of the major vendors they’re betting their business on have also changed. And that’s super hard for people..” –David Chappell, Author and Speaker

      Common obstacles

      These barriers make this challenge difficult to address for many organizations:

      • Organizations jump to the cloud before defining their cloud vision and without any clear plan for realizing the cloud’s benefits.
      • Many organizations already have a foot in the cloud, but the choice to explore these solutions was made in an ad hoc rather than systematic fashion. The cloud just sort of happened.
      • The lack of a consistent assessment framework means that some workloads that probably belong in the cloud are kept on premises or with hosted services providers – and vice versa.
      • Securing cloud expertise is remarkably difficult – especially in a labor market roiled by the global pandemic and the increasing importance of cloud services.

      Standard cloud challenges

      30% of all cloud spend is self-reported as waste. Many workloads that end up in the cloud don’t belong there. Many workloads that do belong in the cloud aren’t properly migrated. (Flexera, 2021)

      44% of respondents report themselves as under-skilled in the cloud management space. (Pluralsight, 2021)

      Info-Tech’s approach

      Goals and drivers

      • Service model
        • What type of cloud makes the most sense for workload archetypes? When does it make sense to pick SaaS over IaaS, for example?
      • Delivery model
        • Will services be delivered over the public cloud, a private cloud, or a hybrid cloud? What challenges accompany this decision?
      • Migration Path
        • What does the migration path look like? What does the transition to the cloud look like, and how much effort will be required? Amazon’s 6Rs framework captures migration options: rehosting, repurchasing, replatforming, and refactoring, along with retaining and retiring. Each workload should be assessed for its suitability for one or more of these paths.
      • Support model
        • How will services be provided? Will staff be trained, new staff hired, a service provider retained for ongoing operations, or will a consultant with cloud expertise be brought on board for a defined period? The appropriate support model is highly dependent on goals along with expected outcomes for different workloads.

      Highlight risks and roadblocks

      Formalize cloud vision

      Document your cloud strategy

      The Info-Tech difference:

      1. Determine the hypothesized value of cloud for your organization.
      2. Evaluate workloads with 6Rs framework.
      3. Identify and mitigate risks.
      4. Identify cloud archetype.
      5. Plot initiatives on a roadmap.
      6. Write action plan statement and goal statement.

      What is the cloud, how is it deployed, and how is service provided?

      Cloud Characteristics

      1. On-demand self-service: the ability to access reosurces instantly without vendor interaction
      2. Broad network access: all services delivered over the network
      3. Resource pooling: multi-tenant environment (shared)
      4. Rapid elasticity: the ability to expand and retract capabilities as needed
      5. Measured service: transparent metering

      Service Model:

      1. Software-as-a-Service: all but the most minor configuration is done by the vendor
      2. Platform-as-a-Service: customer builds the application using tools provided by the provider
      3. Infrastructure-as-a-Service: the customer manages OS, storage, and the application

      Delivery Model

      1. Public cloud: accessible to anyone over the internet; multi-tenant environment
      2. Private cloud: provisioned for a single organization with multiple units
      3. Hybrid cloud: two or more connected clouds; data is portage across them
      4. Community cloud: provisioned for a specific group of organizations

      (National Institute of Standards and Technology)

      A workload-first approach will allow you to take full advantage of the cloud’s strengths

      • Under all but the most exceptional circumstances, good cloud strategies will incorporate different service models. Very few organizations are “IaaS shops” or “SaaS shops,” even if they lean heavily in one direction.
      • These different service models (including non-cloud options like colocation and on-premises infrastructure) each have different strengths. Part of your cloud strategy should involve determining which of the services makes the most sense for you.
      • Own the cloud by understanding which cloud (or non-cloud!) offering makes the most sense for you given your unique context.

      Migration paths

      In a 2016 blog post, Amazon introduced a framework for understanding cloud migration strategies. The framework presented here is slightly modified – including a “relocate” component rather than a “retire” component – but otherwise hews close to the standard.

      These migration paths reflect organizational capabilities and desired outcomes in terms of service models – cloud or otherwise. Retention means keeping the workload where it is, in a datacenter or a colocation service, or relocating to a colocation or hosted software environment. These represent the “non-cloud” migration paths.

      In the graphic on the right, the paths within the red box lead to the cloud. Rehosting means lifting and shifting to an infrastructure environment. Migrating a virtual machine from your VMware environment on premises to Azure Virtual machines is a quick way to realize some benefits from the cloud. Migrating from SQL Server on premises to a cloud-based SQL solution looks a bit more like changing platforms (replatforming). It involves basic infrastructure modification without a substantial architectural component.

      Refactoring is the most expensive of the options and involves engaging the software development lifecycle to build a custom solution, fundamentally rewriting the solution to be cloud native and take advantage of cloud-native architectures. This can result in a PaaS or an IaaS solution.

      Finally, repurchasing means simply going to market and procuring a new solution. This may involve migrating data, but it does not require the migration of components.

      Migration Paths

      Retain (Revisit)

      • Keep the application in its current form, at least for now. This doesn’t preclude revisiting it in the future.

      Relocate

      • Move the workload between datacenters or to a hosted software/colocation provider.

      Rehost

      • Move the application to the cloud (IaaS) and continue to run it in more or less the same form as it currently runs.

      Replatform

      • Move the application to the cloud and perform a few changes for cloud optimizations.

      Refactor

      • Rewrite the application, taking advantage of cloud-native architectures.

      Repurchase

      • Replace with an alternative, cloud-native application and migrate the data.

      Support model

      Support models by characteristic

      Duration of engagement Specialization Flexibility
      Internal IT Indefinite Varies based on nature of business Fixed, permanent staff
      Managed Service Provider Contractually defined General, some specialization Standard offering
      Consultant Project-based Specific, domain-based Entirely negotiable

      IT services, including cloud services, can be delivered and managed in multiple ways depending on the nature of the workload and the organization’s intended path forward. Three high-level options are presented here and may be more or less valuable based on the duration of the expected engagement with the service (temporary or permanent), the skills specialization required, and the flexibility necessary to complete the job.

      By way of example, a highly technical, short-term project with significant flexibility requirements might be a good fit for an expensive consultant, whereas post-implementation maintenance of a cloud email system requires relatively little specialization and flexibility and would therefore be a better fit for internal management.

      There is no universally applicable rule here, but there are some workloads that are generally a good fit for the cloud and others that are not as effective, with that fit being conditional on the appropriate support model being employed.

      Risks, roadblocks, and strategy components

      No two cloud strategies are exactly alike, but all should address 14 key areas. A key step in defining your cloud vision is an assessment of these strategy components. Lower maturity does not preclude an aggressive cloud strategy, but it does indicate that higher effort will be required to make the transition.

      Component Description Component Description
      Monitoring What will system owners/administrators need visibility into? How will they achieve this? Vendor Management What practices must change to ensure effective management of cloud vendors?
      Provisioning Who will be responsible for deploying cloud workloads? What governance will this process be subject to? Finance Management How will costs be managed with the transition away from capital expenditure?
      Migration How will cloud migrations be conducted? What best practices/standards must be employed? Security What steps must be taken to ensure that cloud services meet security requirements?
      Operations management What is the process for managing operations as they change in the cloud? Data Controls How will data residency, compliance, and protection requirements be met in the cloud?
      Architecture What general principles must apply in the cloud environment? Skills and roles What skills become necessary in the cloud? What steps must be taken to acquire those skills?
      Integration and interoperability How will services be integrated? What standards must apply? Culture and adoption Is there a cultural aversion to the cloud? What steps must be taken to ensure broad cloud acceptance?
      Portfolio Management Who will be responsible for managing the growth of the cloud portfolio? Governing bodies What formal governance must be put in place? Who will be responsible for setting standards?

      Cloud archetypes – a cloud vision component

      Once you understand the value of the cloud, your workloads’ general suitability for cloud, and your proposed risks and mitigations, the next step is to define your cloud archetype.

      Your organization’s cloud archetype is the strategic posture that IT adopts to best support the organization’s goals. Info-Tech’s model recognizes seven archetypes, divided into three high-level archetypes.

      After consultation with your stakeholders, and based on the results of the suitability and risk assessment activities, define your archetype. The archetype feeds into the overall cloud vision and provides simple insight into the cloud future state for all stakeholders.

      The cloud vision itself is captured in a “vision statement,” a short summary of the overall approach that includes the overall cloud archetype.

      We can best support the organization's goals by:

      More Cloud

      Less Cloud

      Cloud Focused Cloud-Centric Providing all workloads through cloud delivery.
      Cloud-First Using the cloud as our default deployment model. For each workload, we should ask “why NOT cloud?”
      Cloud Opportunistic Hybrid Enabling the ability to transition seamlessly between on-premises and cloud resources for many workloads.
      Integrated Combining cloud and traditional infrastructure resources, integrating data and applications through APIs or middleware.
      Split Using the cloud for some workloads and traditional infrastructure resources for others.
      Cloud Averse Cloud-Light Using traditional infrastructure resources and limiting our use of the cloud to when it is absolutely necessary.
      Anti-Cloud Using traditional infrastructure resources and avoiding use of the cloud wherever possible.

      Info-Tech’s methodology for defining your cloud vision

      1. Understand the Cloud 2. Assess Workloads 3. Identify and Mitigate Risks 4. Bridge the Gap and Create the Vision
      Phase Steps
      1. Generate goals and drivers
      2. Explore cloud characteristics
      3. Create a current state summary
      4. Select workloads for analysis
      1. Conduct workload assessments
      2. Determine workload future state
      1. Generate risks and roadblocks
      2. Mitigate risks and roadblocks
      3. Define roadmap initiatives
      1. Review and assign work items
      2. Finalize cloud decision framework
      3. Create cloud vision
      Phase Outcomes
      1. List of goals and drivers
      2. Shared understanding of cloud terms
      3. Current state of cloud in the organization
      4. List of workloads to be assessed
      1. Completed workload assessments
      2. Defined workload future state
      1. List of risks and roadblocks
      2. List of mitigations
      3. Defined roadmap initiatives
      1. Cloud roadmap
      2. Cloud decision framework
      3. Completed Cloud Vision Executive Presentation

      Insight summary

      The cloud may not be right for you – and that’s okay!

      Don’t think about the cloud as an inevitable next step for all workloads. The cloud is merely another tool in the toolbox, ready to be used when appropriate and put away when it’s not needed. Cloud first isn’t always the way to go.

      Not all clouds are equal

      It’s not “should I go to the cloud?” but “what service and delivery models make sense based on my needs and risk tolerance?” Thinking about the cloud as a binary can force workloads into the cloud that don’t belong (and vice versa).

      Bottom-up is best

      A workload assessment is the only way to truly understand the cloud’s value. Work from the bottom up, not the top down, understand what characteristics make a workload cloud suitable, and strategize on that basis.

      Your accountability doesn’t change

      You are still accountable for maintaining available, secure, functional applications and services. Cloud providers share some responsibility, but the buck stops where it always has: with you.

      Don’t customize for the sake of customization

      SaaS providers make money selling the same thing to everyone. When migrating a workload to SaaS, work with stakeholders to pursue standardization around a selected platform and avoid customization where possible.

      Best of both worlds, worst of both worlds

      Hybrid clouds are in fashion, but true hybridity comes with additional cost, administration, and other constraints. A convoy moves at the speed of its slowest member.

      The journey matters as much as the destination

      How you get there is as important as what “there” actually is. Any strategy that focuses solely on the destination misses out on a key part of the value conversation: the migration strategy.

      Blueprint benefits

      Cloud Vision Executive Presentation

      This presentation captures the results of the exercises and presents a complete vision to stakeholders including a desired target state, a rubric for decision making, the results of the workload assessments, and an overall risk profile.

      Cloud Vision Workbook

      This workbook includes the standard cloud workload assessment questionnaire along with the results of the assessment. It also includes the milestone timeline for the implementation of the cloud vision.

      Blueprint benefits

      IT Benefits

      • A consistent approach to the cloud takes the guesswork out of deployment decisions and makes it easier for IT to move on to the execution stage.
      • When properly incorporated, cloud services come with many benefits, including automation, elasticity, and alternative architectures (micro-services, containers). The cloud vision project will help IT readers articulate expected benefits and work towards achieving them.
      • A clear framework for incorporating organizational goals into cloud plans.

      Business benefits

      • Simple, well-governed access to high-quality IT resources.
      • Access to the latest and greatest in technology to facilitate remote work.
      • Framework for cost management in the cloud that incorporates OpEx and chargebacks/showbacks. A clear understanding of expected changes to cost modeling is also a benefit of a cloud vision.
      • Clarity for stakeholders about IT’s response (and contribution to) IT strategic initiatives.

      Measure the value of this blueprint

      Don’t take our word for it:

      • The cloud vision material in various forms has been offered for several years, and members have generally benefited substantially, both from cloud vision workshops and from guided implementations led by analysts.
      • After each engagement, we send a survey that asks members how they benefited from the experience. Of 30 responses, the cloud vision research has received an average score of 9.8/10. Real members have found significant value in the process.
      • Additionally, members reported saving between 2 and 120 days (for an average of 17), and financial savings ranged from $1,920 all the way up to $1.27 million, for an average of $170,577.90! If we drop outliers on both ends, the average reported value of a cloud vision engagement is $37, 613.
      • Measure the value by calculating the time saved from using Info-Tech’s framework vs. a home-brewed cloud strategy alternative and by comparing the overall cost of a guided implementation or workshop with the equivalent offering from another firm. We’re confident you’ll come out ahead.

      9.8/10 Average reported satisfaction

      17 Days Average reported time savings

      $37, 613 Average cost savings (adj.)

      Executive Brief Case Study

      Industry: Financial

      Source: Info-Tech workshop

      Anonymous financial institution

      A small East Coast financial institution was required to develop a cloud strategy. This strategy had to meet several important requirements, including alignment with strategic priorities and best practices, along with regulatory compliance, including with the Office of the Comptroller of the Currency.

      The bank already had a significant cloud footprint and was looking to organize and formalize the strategy going forward.

      Leadership needed a comprehensive strategy that touched on key areas including the delivery model, service models, individual workload assessments, cost management, risk management and governance. The output had to be consumable by a variety of audiences with varying levels of technical expertise and had to speak to IT’s role in the broader strategic goals articulated earlier in the year.

      Results

      The bank engaged Info-Tech for a cloud vision workshop and worked through four days of exercises with various IT team members. The bank ultimately decided on a multi-cloud strategy that prioritized SaaS while also allowing for PaaS and IaaS solutions, along with some non-cloud hosted solutions, based on organizational circumstances.

      Bank cloud vision

      [Bank] will provide innovative financial and related services by taking advantage of the multiplicity of best-of-breed solutions available in the cloud. These solutions make it possible to benefit from industry-level innovations, while ensuring efficiency, redundancy, and enhanced security.

      Bank cloud decision workflow

      • SaaS
        • Platform?
          • Yes
            • PaaS
          • No
            • Hosted
          • IaaS
            • Other

      Non-cloud

      Cloud

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      "Our team has already made this crticial project a priority, and we have the time and capability, but some guidance along the way would be helpful."

      Guided Implementation

      "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track."

      Workshop

      "We need to hit the ground running and get this project kicked off imediately. Our team has the ability to take this over once we get a framework and strategy in place."

      Consulting

      "Our team does not have the time or the knowledge the take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks are used throughout all four options.

      Guided Implementation

      What does a typical GI on this topic look like?

      A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.

      A typical GI is between 8 to 12 calls over the course of 4 to 6 months.

      Phase 1

      • Call #1: Discuss current state, challenges, etc.
      • Call #2: Goals, drivers, and current state.

      Phase 2

      • Call #3: Conduct cloud suitability assessment for selected workloads.

      Phase 3

      • Call #4: Generate and categorize risks.
      • Call #5: Begin the risk mitigation conversation.

      Phase 4

      • Call #6: Complete the risk mitigation process
      • Call #7: Finalize vision statement and cloud decision framework.

      Workshop Overview

      Contact your account representative for more information.

      workshops@infotech.com 1-888-670-8889

      Day 1 Day 2 Day 3 Day 4 Offsite day
      Understand the cloud Assess workloads Identify and mitigate risks Bridge the gap and create the strategy Next steps and wrap-up (offsite)
      Activities

      1.1 Introduction

      1.2 Generate corporate goals and cloud drivers

      1.3 Identify success indicators

      1.4 Explore cloud characteristics

      1.5 Explore cloud service and delivery models

      1.6 Define cloud support models and strategy components

      1.7 Create current state summaries for the different service and delivery models

      1.8 Select workloads for further analysis

      2.1 Conduct workload assessments using the cloud strategy workbook tool

      2.2 Discuss assessments and make preliminary determinations about workloads

      3.1 Generate a list of risks and potential roadblocks associated with the cloud

      3.2 Sort risks and roadblocks and define categories

      3.3 Identify mitigations for each identified risk and roadblock

      3.4 Generate initiatives from the mitigations

      4.1 Review and assign work items

      4.2 Finalize the decision framework for each of the following areas:

      • Service model
      • Delivery model
      • Support model

      4.3 Create a cloud vision statement

      5.1 Build the Cloud Vision Executive Presentation
      Deliverables
      1. Corporate goals and cloud drivers
      2. Success indicators
      3. Current state summaries
      4. List of workloads for further analysis
      1. Completed workload assessments
      2. Workload summary statements
      1. List of risks and roadblocks, categorized
      2. List of mitigations
      3. List of initiatives
      1. Finalized task list
      2. Formal cloud decision rubric
      3. Cloud vision statement
      1. Completed cloud strategy executive presentation
      2. Completed cloud vision workbook

      Understand the cloud

      Build the foundations of your cloud vision

      Phase 1

      Phase 1

      Understand the Cloud

      Phase 1

      1.1 Generate goals and drivers

      1.2 Explore cloud characteristics

      1.3 Create a current state summary

      1.4 Select workloads for analysis

      Phase 2

      2.1 Conduct workload assessments

      2.2 Determine workload future states

      Phase 3

      3.1 Generate risks and roadblocks

      3.2 Mitigate risks and roadblocks

      3.3 Define roadmap initiatives

      Phase 4

      4.1 Review and assign work items

      4.2 Finalize cloud decision framework

      4.3 Create cloud vision

      This phase will walk you through the following activities:

      1.1.1 Generate organizational goals

      1.1.2 Define cloud drivers

      1.1.3 Define success indicators

      1.3.1 Record your current state

      1.4.1 Select workloads for further assessment

      This phase involves the following participants:

      IT management, the core working group, security, infrastructure, operations, architecture, engineering, applications, non-IT stakeholders.

      It starts with shared understanding

      Stakeholders must agree on overall goals and what “cloud” means

      The cloud is a nebulous term that can reasonably describe services ranging from infrastructure as a service as delivered by providers like Amazon Web Services and Microsoft through its Azure platform, right up to software as a service solutions like Jira or Salesforce. These solutions solve different problems – just because your CRM would be a good fit for a migration to Salesforce doesn’t mean the same system would make sense in Azure or AWS.

      This is important because the language we use to talk about the cloud can color our approach to cloud services. A “cloud-first” strategy will mean something different to a CEO with a concept of the cloud rooted in Salesforce than it will to a system administrator who interprets it to mean a transition to cloud-hosted virtual machines.

      Add to this the fact that not all cloud services are hosted externally by providers (public clouds) and the fact that multiple delivery models can be engaged at once through hybrid or multi-cloud approaches, and it’s apparent that a shared understanding of the cloud is necessary for a coherent strategy to take form.

      This phase proceeds in four steps, each governed by the principle of shared understanding. The first requires a shared understanding of corporate goals and drivers. Step 2 involves coming to a shared understanding of the cloud’s unique characteristics. Step 3 requires a review of the current state. Finally, in Step 4, participants will identify workloads that are suitable for analysis as candidates for the cloud.

      Step 1.1

      Generate goals and drivers

      Activities

      1.1.1 Define organizational goals

      1.1.2 Define cloud drivers

      1.1.3 Define success indicators

      Generate goals and drivers

      Explore cloud characteristics

      Create a current state summary

      Select workloads for analysis

      This step involves the following participants:

      • IT management
      • Core working group
      • Security
      • Applications
      • Infrastructure
      • Service management
      • Leadership

      Outcomes of this step

      • List of organizational goals
      • List of cloud drivers
      • Defined success indicators

      What can the cloud do for you?

      The cloud is not valuable for its own sake, and not all users derive the same value

      • The cloud is characterized by on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. Any or all of those characteristics might be enough to make the cloud appealing, but in most cases, there is an overriding driver.
      • Multiple paths may lead to the cloud. Consider an organization with a need to control costs by showing back to business units, or perhaps by reducing capital expenditure – the cloud may be the most appropriate way to effect these changes. Conversely, an organization expanding rapidly and with a need to access the latest and greatest technology might benefit from the elasticity and pooled resources that major cloud providers can offer.
      • In these cases, the destination might be the same (a cloud solution) but the delivery model – public, private, or hybrid – and the decisions made around the key strategy components, including architecture, provisioning, and cost management, will almost certainly be different.
      • Defining goals, understanding cloud drivers, and – crucially – understanding what success means, are all therefore essential elements of the cloud vision process.

      1.1.1 Generate organizational goals

      1-3 hours

      Input

      • Strategy documentation

      Output

      • Organizational goals

      Materials

      • Whiteboard (digital/physical)

      Participants

      • IT leadership
      • Infrastructure
      • Applications
      • Security
      1. As a group, brainstorm organizational goals, ideally based on existing documentation
        • Review relevant corporate and IT strategies.
        • If you do not have access to internal documentation, review the standard goals on the next slide and select those that are most relevant for you.
      2. Record the most important business goals in the Cloud Vision Executive Presentation. Include descriptions where possible to ensure wide readability.
      3. Make note of these goals. They should inform the answers to prompts offered in the Cloud Vision Workbook and should be a consistent presence in the remainder of the visioning exercise. If you’re conducting the session in person, leave the goals up on a whiteboard and make reference to them throughout the workshop.

      Cloud Vision Executive Presentation

      Standard COBIT 19 enterprise goals

      1. Portfolio of competitive products and services
      2. Managed business risk
      3. Compliance with external laws and regulations
      4. Quality of financial information
      5. Customer-oriented service culture
      6. Business service continuity and availability
      7. Quality of management information
      8. Optimization of internal business process functionality
      9. Optimization of business process costs
      10. Staff skills, motivation, and productivity
      11. Compliance with internal policies
      12. Managed digital transformation programs
      13. Product and business innovation

      1.1.2 Define cloud drivers

      30-60 minutes

      Input

      • Organizational goals
      • Strategy documentation
      • Management/staff perspective

      Output

      • List of cloud drivers

      Materials

      • Sticky notes
      • Whiteboard
      • Markers

      Participants

      • IT leadership
      • Infrastructure
      • Applications
      • Security
      1. Cloud drivers sit at a level of abstraction below organizational goals. Keeping your organizational goals in mind, have each participant in the session write down how they expect to benefit from the cloud on a sticky note.
      2. Solicit input one at a time and group similar responses. Encourage participants to bring forward their cloud goals even if similar goals have been mentioned previously. The number of mentions is a useful way to gauge the relative weight of the drivers.
      3. Once this is done, you should have a few groups of similar drivers. Work with the group to name each category. This name will be the driver reported in the documentation.
      4. Input the results of the exercise into the Cloud Vision Executive Presentation, and include descriptions based on the constituent drivers. For example, if a driver is titled “do more valuable work,” the constituent drivers might be “build cloud skills,” “focus on core products,” and “avoid administration work where possible.” The description would be based on these components.

      Cloud Vision Executive Presentation

      1.1.3 Define success indicators

      1 hour

      Input

      • Cloud drivers
      • Organizational goals

      Output

      • List of cloud driver success indicators

      Materials

      • Whiteboard
      • Markers

      Participants

      • IT leadership
      • Infrastructure
      • Applications
      • Security
      1. On a whiteboard, draw a table with each of the cloud drivers (identified in 1.1.2) across the top.
      2. Work collectively to generate success indicators for each cloud driver. In this case, a success indicator is some way you can report your progress with the stated driver. It is a real-world proxy for the sometimes abstract phenomena that make up your drivers. Think about what would be true if your driver was realized.
        1. For example, if your driver is “faster access to resources,” you might consider indicators like developer satisfaction, project completion time, average time to provision, etc.
      3. Once you are satisfied with your list of indicators, populate the slide in the Cloud Vision Executive Presentation for validation from stakeholders.

      Cloud Vision Executive Presentation

      Step 1.2

      Explore cloud characteristics

      Activities

      Understand the value of the cloud:

      • Review delivery models
      • Review support models
      • Review service models
      • Review migration paths

      Understand the Cloud

      Generate goals and drivers

      Explore cloud characteristics

      Create a current state summary

      Select workloads for analysis

      This step involves the following participants:

      • Core working group
      • Architecture
      • Engineering
      • Security

      Outcomes of this step

      • Understanding of cloud service models and value

      Defining the cloud

      Per NIST, the cloud has five fundamental characteristics. All clouds have these characteristics, even if they are executed in somewhat different ways between delivery models, service models, and even individual providers.

      Cloud characteristics

      On-demand self-service

      Cloud customers are capable of provisioning cloud resources without human interaction (e.g. contacting sales), generally through a web console.

      Broad network access

      Capabilities are designed to be delivered over a network and are generally intended for access by a wide variety of platform types (cloud services are generally device-agnostic).

      Resource pooling

      Multiple customers (internal, in the case of private clouds) make use of a highly abstracted shared infrastructure managed by the cloud provider.

      Rapid elasticity

      Customers are capable of provisioning additional resources as required, pulling from a functionally infinite pool of capacity. Cloud resources can be spun-down when no longer needed.

      Measured service

      Consumption is metered based on an appropriate unit of analysis (number of licenses, storage used, compute cycles, etc.) and billing is transparent and granular.

      Cloud delivery models

      The NIST definition of cloud computing outlines four cloud delivery models: public, private, hybrid, and community clouds. A community cloud is like a private cloud, but it is provisioned for the exclusive use of a like-minded group of organizations, usually in a mutually beneficial, non-competitive arrangement. Universities and hospitals are examples of organizations that can pool their resources in this way without impacting competitiveness. The Info-Tech model covers three key delivery models – public, private, and hybrid, and an overarching model (multi-cloud) that can comprise more than one of the other models – public + public, public + hybrid, etc.

      Public

      The cloud service is provisioned for access by the general public (customers).

      Private

      A private cloud has the five key characteristics, but is provisioned for use by a single entity, like a company or organization.

      Hybrid

      Hybridity essentially refers to interoperability between multiple cloud delivery models (public +private).

      Multi

      A multi-cloud deployment requires only that multiple clouds are used without any necessary interoperability (Nutanix, 2019).

      Public cloud

      This is what people generally think about when they talk about cloud

      • The public cloud is, well, public! Anyone can make use of its resources, and in the case of the major providers, capacity is functionally unlimited. Need to store exabytes of data in the cloud? No problem! Amazon will drive a modified shipping container to your datacenter, load it up, and “migrate” it to a datacenter.
      • Public clouds offer significant variety on the infrastructure side. Major IaaS providers, like Microsoft and Amazon, offer dozens of services across many different categories including compute, networking, and storage, but also identity, containers, machine learning, virtual desktops, and much, much more. (See a list from Microsoft here, and Amazon here)
      • There are undoubtedly strengths to the public cloud model. Providers offer the “latest and greatest” and customers need not worry about the details, including managing infrastructure and physical locations. Providers offer built-in redundancy, multi-regional deployments, automation tools, management and governance solutions, and a variety of leading-edge technologies that would not be feasible for organizations to run in-house, like high performance compute, blockchain, or quantum computing.
      • Of course, the public cloud is not all sunshine and rainbows – there are downsides as well. It can be expensive; it can introduce regulatory complications to have to trust another entity with your key information. Additionally, there can be performance hiccups, and with SaaS products, it can be difficult to monitor at the appropriate (per-transaction) level.

      Prominent examples include:

      AWS

      Microsoft

      Azure

      Salesforce.com

      Workday

      SAP

      Private cloud

      A lower-risk cloud for cloud-averse customers?

      • A cloud is a cloud, no matter how small. Some IT shops deploy private clouds that make use of the five key cloud characteristics but provisioned for the exclusive use of a single entity, like a corporation.
      • Private clouds have numerous benefits. Some potential cloud customers might be uncomfortable with the shared responsibility that is inherent in the public cloud. Private clouds allow customers to deliver flexible, measured services without having to surrender control, but they require significant overhead, capital expenditure, administrative effort, and technical expertise.
      • According to the 2021 State of the Cloud Report, private cloud use is common, and the most frequently cited toolset is VMware vSphere, followed by Azure Stack, OpenStack, and AWS Outposts. Private cloud deployments are more common in larger organizations, which makes sense given the overhead required to manage such an environment.

      Private cloud adoption

      The images shows a graph titled Private Cloud Adoption for Enterprises. It is a horizontal bar graph, with three segments in each bar: dark blue marking currently use; mid blue marking experimenting; and light blue marking plan to use.

      VMware and Microsoft lead the pack among private cloud customers, with Amazon and Red Hat also substantially present across private cloud environments.

      Hybrid cloud

      The best of both worlds?

      Hybrid cloud architectures combine multiple cloud delivery models and facilitate some level of interoperability. NIST suggests bursting and load balancing as examples of hybrid cloud use cases. Note: it is not sufficient to simply have multiple clouds running in parallel – there must be a toolset that allows for an element of cross-cloud functionality.

      This delivery model is attractive because it allows users to take advantage of the strengths of multiple service models using a single management pane. Bursting across clouds to take advantage of additional capacity or disaster recovery capabilities are two obvious use cases that appeal to hybrid cloud users.

      But while hybridity is all the rage (especially given the impact Covid-19 has had on the workplace), the reality is that any hybrid cloud user must take the good with the bad. Multiple clouds and a management layer can be technically complex, expensive, and require maintaining a physical infrastructure that is not especially valuable (“I thought we were moving to the cloud to get out of the datacenter!”).

      Before selecting a hybrid approach through services like VMware Cloud on AWS or Microsoft’s Azure Stack, consider the cost, complexity, and actual expected benefit.

      Amazon, Microsoft, and Google dominate public cloud IaaS, but IBM is betting big on hybrid cloud:

      The image is a screencap of a tweet from IBM News. The tweet reads: IBM CEO Ginni Rometty: Hybrid cloud is a trillion dollar market and we'll be number one #Think2019.

      With its acquisition of Red Hat in 2019 for $34 billion, Big Blue put its money where its mouth is and acquired a substantial hybrid cloud business. At the time of the acquisition, Red Hat’s CEO, Jim Whitehurst, spoke about the benefit IBM expected to receive:

      “Joining forces with IBM gives Red Hat the opportunity to bring more open source innovation to an even broader range of organizations and will enable us to scale to meet the need for hybrid cloud solutions that deliver true choice and agility” (Red Hat, 2019).

      Multi-cloud

      For most organizations, the multi-cloud is the most realistic option.

      Multi-cloud is popular!

      The image shows a graph titled Multi-Cloud Architectures Used, % of all Respondents. The largest percentage is Apps siloed on different clouds, followed by DAta integration between clouds.

      Multi-cloud solutions exist at a different layer of abstraction from public, private, and even hybrid cloud delivery models. A multi-cloud architecture, as the name suggests, requires the user to be a customer of more than one cloud provider, and it can certainly include a hybrid cloud deployment, but it is not bound by the same rules of interoperability.

      Many organizations – especially those with fewer resources or a lack of a use case for a private cloud – rely on a multi-cloud architecture to build applications where they belong, and they manage each environment separately (or occasionally with the help of cloud management platforms).

      If your data team wants to work in AWS and your enterprise services run on basic virtual machines in Azure, that might be the most effective architecture. As the Flexera 2021 State of the Cloud Report suggests, this architecture is far more common than the more complicated bursting or brokering architectures characteristic of hybrid clouds.

      NIST cloud service models

      Software as a service

      SaaS has exploded in popularity with consumers who wish to avail themselves of the cloud’s benefits without having to manage underlying infrastructure components. SaaS is simple, generally billed per-user per-month, and is almost entirely provider-managed.

      Platform as a service

      PaaS providers offer a toolset for their customers to run custom applications and services without the requirement to manage underlying infrastructure components. This service model is ideal for custom applications/services that don’t benefit from highly granular infrastructure control.

      Infrastructure as a service

      IaaS represents the sale of components. Instead of a service, IaaS providers sell access to components, like compute, storage, and networking, allowing for customers to build anything they want on top of the providers’ infrastructure.

      Cloud service models

      • This research focuses on five key service models, each of which has its own strengths and weaknesses. Moving right from “on-prem,” customers gradually give up more control over their environments to cloud service providers.
      • An entirely premises-based environment means that the customer is responsible for everything ranging from the dirt under the datacenter to application-level configurations. Conversely, in a SaaS environment, the provider is responsible for everything but those top-level application configurations.
      • A managed service provider or other third party can manage any or of the components of the infrastructure stack. A service provider may, for example, build a SaaS solution on top of another provider’s IaaS, or might offer configuration assistance with a commercially available SaaS.

      Info-Tech Insight

      Not all workloads fit well in the cloud. Many environments will mix service models (e.g. SaaS for some workloads, some in IaaS, some on-premises), and this can be perfectly effective. It must be consistent and intentional, however.

      On-prem Co-Lo IaaS PaaS SaaS
      Application Application Application Application Application
      Database Database Database Database Database
      Runtime/ Middleware Runtime/ Middleware Runtime/ Middleware Runtime/ Middleware Runtime/ Middleware
      OS OS OS OS OS
      Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor
      Server Network Storage Server Network Storage Server Network Storage Server Network Storage Server Network Storage
      Facilities Facilities Facilities Facilities Facilities

      Organization has control

      Organization or vendor may control

      Vendor has control

      Analytics folly

      SaaS is good, but it’s not a panacea

      Industry: Healthcare

      Source: Info-Tech workshop

      Situation

      A healthcare analytics provider had already moved a significant number of “non-core workloads” to the cloud, including email, HRIS, and related services.

      The company CEO was satisfied with the reduced effort required by IT to manage SaaS-based workloads and sought to extend the same benefits to the core analytics platform where there was an opportunity to reduce overhead.

      Complication

      Many components of the health analytics service were designed to run specifically in a datacenter and were not ready to be migrated to the cloud without significant effort/refactoring. SaaS was not an option because this was a core platform – a SaaS provider would have been the competition.

      That left IaaS, which was expensive and would not bring the expected benefits (reduced overhead).

      Results

      The organization determined that there were no short-term gains from migrating to the cloud. Due to the nature of the application (its extensive customization, the fact that it was a core product sold by the company) any steps to reduce operational overhead were not feasible.

      The CEO recognized that the analytics platform was not a good candidate for the cloud and what distinguished the analytics platform from more suitable workloads.

      Migration paths

      In a 2016 blog post, Amazon Web Services articulated a framework for cloud migration that incorporates elements of the journey as well as the destination. If workload owners do not choose to retain or retire their workloads, there are four alternatives. These alternatives all stack up differently along five key dimensions:

      1. Value: does the workload stand to benefit from unique cloud characteristics? To what degree?
      2. Effort: how much work would be required to make the transition?
      3. Cost: how much money is the migration expected to cost?
      4. Time: how long will the migration take?
      5. Skills: what skills must be brought to bear to complete the migration?

      Not all migration paths can lead to all destinations. Rehosting generally means IaaS, while repurchasing leads to SaaS. Refactoring and replatforming have some variety of outcomes, and it becomes possible to take advantage of new IaaS architectures or migrate workloads over fully to SaaS.

      As part of the workload assessment process, use the five dimensions (expanded upon on the next slide) to determine what migration path makes sense. Preferred migration paths form an important part of the overall cloud vision process.

      Retain (Revisit)

      • Keep the application in its current form, at least for now. This doesn’t preclude revisiting it in the future.

      Retire

      • Get rid of the application completely.

      Rehost

      • Move the application to the cloud (IaaS) and continue to run it in more or less the same form as it currently runs.

      Replatform

      • Move the application to the cloud and perform a few changes for cloud optimizations.

      Refactor

      • Rewrite the application, taking advantage of cloud native architectures.

      Repurchase

      • Replace with an alternative, cloud-native application and migrate the data.

      Migration paths – relative value

      Migration path Value Effort Cost Time Skills
      Retain No real change in the absolute value of the workload if it is retained. No effort beyond ongoing workload maintenance. No immediate hard dollar costs, but opportunity costs and technical debt abound. No time required! (At least not right away…) Retaining requires the same skills it has always required (which may be more difficult to acquire in the future).
      Rehire A retired workload can provide no value, but it is not a drain! Spinning a service down requires engaging that part of the lifecycle. N/A Retiring the service may be simple or complicated depending on its current role. N/A
      Rehost Some value comes with rehosting, but generally components stay the same (VM here vs. a VM there). Minimal effort required, especially with automated tools. The effort will depend on the environment being migrated. Relatively cheap compared to other options. Rehosting infrastructure is the simplest cloud migration path and is useful for anyone in a hurry. Rehosting is the simplest cloud migration path for most workloads, but it does require basic familiarity with cloud IaaS.

      Replatform

      Replatformed workloads can take advantage of cloud-native services (SQL vs. SQLaaS). Replatforming is more effortful than rehosting, but less effortful than refactoring. Moderate cost – does not require fundamental rearchitecture, just some tweaking. Relatively more complicated than a simple rehost, but less demanding than a refactor. Platform and workload expertise is required; more substantial than a simple rehost.
      Refactor A fully formed, customized cloud-based workload that can take advantage of cloud-native architectures is generally quite valuable. Significant effort required based on the requirement to engage the full SDLC. Significant cost required to engage SDLC and rebuild the application/service. The most complicated and time-consuming. The most complicated and time-consuming.
      Repurchase Repurchasing is the quickest way to achieve cloud-native value. There are compromises, however (high cost, vendor-lock-in). Repurchasing is the quickest way to achieve cloud-native value. There are compromises, however (high cost, vendor-lock-in). Repurchasing is the quickest way to achieve cloud-native value. There are compromises, however (high cost, vendor-lock-in). Configuration – especially for massive projects – can be time consuming, but in general repurchasing can be quite fast. Buying software does require knowledge of requirements and integrations, but is otherwise quite simple.

      Where should you get your cloud skills?

      Cloud skills are certainly top of mind right now. With the great upheaval in both work patterns and in the labor market more generally, expertise in cloud-related areas is simultaneously more valuable and more difficult to procure. According to Pluralsight’s 2021 “State of Upskilling” report, 44% of respondents report themselves under-skilled in the cloud management area, making cloud management the most significant skill gap reported on the survey.

      Everyone left the office. Work as we know it is fundamentally altered for a generation or more. Cloud services shot up in popularity by enabling the transition. And yet there is a gap – a prominent gap – in skilling up for this critically important future. What is the cloud manager to do?

      Per the framework presented here, that manager has three essential options. They may take somewhat different forms depending on specific requirements and the quirks of the local market, but the options are:

      1. Train or hire internal resources: This might be easier said than done, especially for more niche skills, but makes sense for workloads that are critical to operations for the long term.
      2. Engage a managed service provider: MSPs are often engaged to manage services where internal IT lacks bandwidth or expertise.
      3. Hire a consultant: Consultants are great for time-bound implementation projects where highly specific expertise is required, such as a migration or implementation project.

      Each model makes sense to some degree. When evaluating individual workloads for cloud suitability, it is critical to consider the support model – both immediate and long term. What makes sense from a value perspective?

      Cloud decisions – summary

      A key component of the Info-Tech cloud vision model is that it is multi-layered. Not every decision must be made at every level. At the workload level, it makes sense to select service models that make sense, but each workload does not need its own defined vision. Workload-level decisions should be guided by an overall strategy but applied tactically, based on individual workload characteristics and circumstances.

      Conversely, some decisions will inevitably be applied at the environment level. With some exceptions, it is unlikely that cloud customers will build an entire private/hybrid cloud environment around a single solution; instead, they will define a broader strategy and fit individual workloads into that strategy.

      Some considerations exist at both the workload and environment levels. Risks and roadblocks, as well as the preferred support model, are concerns that exist at both the environment level and at the workload level.

      The image is a Venn diagram, with the left side titled Workload level, and the right side titled Environment Level. In the left section are: service model and migration path. On the right section are: Overall vision and Delivery model. In the centre section are: support model and Risks and roadblocks.

      Step 1.3

      Create a current state summary

      Activities

      1.3.1 Record your current state

      Understand the Cloud

      Generate goals and drivers

      Explore cloud characteristics

      Create a current state summary

      Select workloads for analysis

      This step involves the following participants: Core working group

      Outcomes of this step

      • Current state summary of cloud solutions

      1.3.1 Record your current state

      30 minutes

      Input

      • Knowledge of existing cloud workloads

      Output

      • Current state cloud summary for service, delivery, and support models

      Materials

      • Whiteboard

      Participants

      • Core working group
      • Infrastructure team
      • Service owners
      1. On a whiteboard (real or virtual) draw a table with each of the cloud service models across the top. Leave a cell below each to list examples.
      2. Under each service model, record examples present in your environment. The purpose of the exercise is to illustrate the existence of cloud services in your environment or the lack thereof, so there is no need to be exhaustive. Complete this in turn for each service model until you are satisfied that you have created an effective picture of your current cloud SaaS state, IaaS state, etc.
      3. Input the results into their own slide titled “current state summary” in the Cloud Vision Executive Presentation.
      4. Repeat for the cloud delivery models and support models and include the results of those exercises as well.
      5. Create a short summary statement (“We are primarily a public cloud consumer with a large SaaS footprint and minimal presence in PaaS and IaaS. We retain an MSP to manage our hosted telephony solution; otherwise, everything is handled in house.”

      Cloud Vision Executive Presentation

      Step 1.4

      Select workloads for current analysis

      Activities

      1.4.1 Select workloads for assessment

      This step involves the following participants:

      • Core working group

      Outcomes of this step

      • List of workloads for assessment

      Understand the cloud

      Generate goals and drivers

      Explore cloud characteristics

      Create a current state summary

      Select workloads for analysis

      1.4.1 Select workloads for assessment

      30 minutes

      Input

      • Knowledge of existing cloud workloads

      Output

      • List of workloads to be assessed

      Materials

      • Whiteboard
      • Cloud Vision Workbook

      Participants

      • Core working group
      • IT management
      1. In many cases, the cloud project is inspired by a desire to move a particular workload or set of workloads. Solicit feedback from the core working group about what these workloads might be. Ask everyone in the meeting to suggest a workload and record each one on a sticky note or white board (virtual or physical).
      2. Discuss the results with the group and begin grouping similar workloads together. They will be subject to the assessments in the Cloud Vision Workbook, so try to avoid selecting too many workloads that will produce similar answers. It might not be obvious, but try to think about workloads that have similar usage patterns, risk levels, and performance requirements, and select a representative group.
      3. You should embrace counterintuition by selecting a workload that you think is unlikely to be a good fit for the cloud if you can and subjecting it to the assessment as well for validation purposes.
      4. When you have a list of 4-6 workloads, record them on tab 2 of the Cloud Vision Workbook.

      Cloud Vision Workbook

      Assess your cloud workloads

      Build the foundations of your cloud vision

      Phase 2

      Phase 2

      Evaluate Cloud Workloads

      Phase 1

      1.1 Generate goals and drivers

      1.2 Explore cloud characteristics

      1.3 Create a current state summary

      1.4 Select workloads for analysis

      Phase 2

      2.1 Conduct workload assessments

      2.2 Determine workload future states

      Phase 3

      3.1 Generate risks and roadblocks

      3.2 Mitigate risks and roadblocks

      3.3 Define roadmap initiatives

      Phase 4

      4.1 Review and assign work items

      4.2 Finalize cloud decision framework

      4.3 Create cloud vision

      This phase will walk you through the following activities:

      • Conduct workload assessments
      • Determine workload future state

      This phase involves the following participants:

      • Subject matter experts
      • Core working group
      • IT management

      Define Your Cloud Vision

      Work from the bottom up and assess your workloads

      A workload-first approach will help you create a realistic vision.

      The concept of a cloud vision should unquestionably be informed by the nature of the workloads that IT is expected to provide for the wider organization. The overall cloud vision is no greater than the sum of its parts. You cannot migrate to the cloud in the abstract. Workloads need to go – and not all workloads are equally suitable for the transition.

      It is therefore imperative to understand which workloads are a good fit for the cloud, which cloud service models make the most sense, how to execute the migration, what support should look like, and what risks and roadblocks you are likely to encounter as part of the process.

      That’s where the Cloud Vision Workbook comes into play. You can use this tool to assess as many workloads as you’d like – most people get the idea after about four – and by the end of the exercise, you should have a pretty good idea about where your workloads belong, and you’ll have a tool to assess any net new or previously unconsidered workloads.

      It’s not so much about the results of the assessment – though these are undeniably important – but about the learnings gleaned from the collaborative assessment exercise. While you can certainly fill out the assessment without any additional input, this exercise is most effective when completed as part of a group.

      Introducing the Cloud Vision Workbook

      • The Cloud Vision Workbook is an Excel tool that answers the age old question: “What should I do with my workloads?”
      • It is divided into eight tabs, each of which offers unique value. Start by reading the introduction and inputting your list of workloads. Work your way through tabs 3-6, completing the suitability, migration, management, and risk and roadblock assessments, and review the results on tab 7.
      • If you choose to go through the full battery of assessments for each workload, expect to answer and weight 111 unique questions across the four assessments. This is an intensive exercise, so carefully consider which assessments are valuable to you, and what workloads you have time to assess.
      • Tab 8 hosts the milestone timeline and captures the results of the phase 3 risk and mitigation exercise.

      Understand Cloud Vision Workbook outputs

      The image shows a graphic with several graphs and lists on it, with sections highlighted with notes. At the top, there's the title Database with the note Workload title (populated from tab 2). Below that, there is a graph with the note Relative suitability of the five service models. The Risks and roadblocks section includes the note: The strategy components – the risks and roadblocks – are captured relative to one another to highlight key focus areas. To the left of that, there is a Notes section with the note Notes populated based on post-assessment discussion. At the bottom, there is a section titled Where should skills be procured?, with the note The radar diagram captures the recommended support model relative to the others (MSP, consultant, internal IT). To the right of that, there is a section titled Migration path, with the note that Ordered list of migration paths. Note: a disconnect here with the suggested service model may indicate an unrealistic goal state.

      Step 2.1

      Conduct workload assessments

      Activities

      2.1.1 Conduct workload assessments

      2.1.2 Interpret your results

      Phase Title

      Conduct workload assessments

      Determine workload future state

      This step involves the following participants:

      • Core working group
      • Workload subject matter experts

      Outcomes of this step

      • Completed workload assessments

      2.1.1 Conduct workload assessments

      2 hours per workload

      Input

      • List of workloads to be assessed

      Output

      • Completed cloud vision assessments

      Materials

      • Cloud Vision Workbook

      Participants

      • Core working group
      • Service owners/workload SMEs
      1. The Cloud Vision Workbook is your one stop shop for all things workload assessment. Open the tool to tab 2 and review the workloads you identified at the end of phase 1. Ensure that these are correct. Once satisfied, project the tool (virtually, if necessary) so that all participants can see the assessment questions.
      2. Work through tabs 3-6, answering the questions and assigning a multiplier for each one. A higher multiplier increases the relative weight of the question, giving it a greater impact on the overall outcome.
      3. Do your best to induce participants to offer opinions. Consensus is not absolutely necessary, but it is a good goal. Ask your participants if they agree with initial responses and occasionally take the opposite position (“I’m surprised you said agree – I would have thought we didn’t care about CapEx vs. OpEx”). Stimulate discussion.
      4. Highlight any questions that you will need to return to or run by someone not present. Include a placeholder answer, as the tool requires all cells to be filled for computation.

      Cloud Vision Workbook

      2.1.2 Interpret your results

      10 minutes

      Input

      • Completed cloud vision assessments

      Output

      • Shared understanding of implications

      Materials

      • Cloud Vision Workbook

      Participants

      • Core working group
      • Service owners/workload SMEs
      1. Once you’ve completed all 111 questions for each workload, you can review your results on tab 7. On tab 7, you will see four populated graphics: cloud suitability, migration path, “where should skills be procured?”, and risks and roadblocks. These represent the components of the overall cloud vision that you will present to stakeholders.
      2. The “cloud suitability” chart captures the service model that the assessment judges to be most suitable for the workload. Ask those present if any are surprised by the output. If there is any disagreement, discuss the source of the surprise and what a more realistic outcome would be. Revisit the assessment if necessary.
      3. Conduct a similar exercise with each of the other outputs. Does it make sense to refactor the workload based on its cloud suitability? Does the fact that we scored so highly on the “consultant” support model indicate something about how we handle upskilling internally? Does the profile of risks and roadblocks identified here align with expectations? What should be ranked higher? What about lower?
      4. Once everyone is generally satisfied with the results, close the tool and take a break! You’ve earned it.

      Cloud Vision Workbook

      Understand the cloud strategy components

      Each cloud strategy will take a slightly different form, but all should contain echoes of each of these components. This process will help you define your vision and direction, but you will need to take steps to execute on that vision. The remainder of the cloud strategy, covered in the related blueprint Document Your Cloud Strategy comprises these fourteen topics divided across three categories: people, governance, and technology. The workload assessment covers these under risks and roadblocks and highlights areas that may require specific additional attention. When interpreting the results, think of these areas as comprising things that you will need to do to make your vision a reality.

      People

      • Skills and roles
      • Culture and adoption
      • Governing bodies

      Governance

      • Architecture
      • Integration and interoperability
      • Operations management
      • Cloud portfolio management
      • Cloud vendor management
      • Finance management
      • Security
      • Data controls

      Technology

      • Monitoring
      • Provisioning
      • Migration

      Strategy component: People

      People form the core of any good strategy. As part of your cloud vision, you will need to understand the implications a cloud transition will have on your staff and users, whether those users are internal or external.

      Component Description Challenges
      Skills and roles The move to the cloud will require staff to learn how to handle new technology and new operational processes. The cloud is a different way of procuring IT resources and may require the definition of new roles to handle things like cost management and provisioning. Staff may not have the necessary experience to migrate to a cloud environment or to effectively manage resources once the cloud transition is made. Cloud skills are difficult to hire for, and with the ever-changing nature of the platforms themselves, this shows no sign of abating. Redefining roles can also be politically challenging and should be done with due care and consideration.
      Culture and adoption If you build it, they will come…right? It is not always the case that a new service immediately attracts users. Ensuring that organizational culture aligns with the cloud vision is a critical success factor. Equally important is ensuring that cloud resources are used as intended. Those unfamiliar with cloud resources may be less willing to learn to use them. If alternatives exist (e.g. a legacy service that has not been shut down), or if those detractors are influential, this resistance may impede your cloud execution. Also, if the cloud transition involves significant effort or a fundamental rework (e.g. a DevOps transition) this role redefinition could cause some internal turmoil.
      Governing bodies A large-scale cloud deployment requires formal governance. Formal governance requires a governing body that is ultimately responsible for designing the said governance. This could take the form of a “center of excellence” or may rest with a single cloud architect in a smaller, less complicated environment. Governance is difficult. Defining responsibilities in a way that includes all relevant stakeholders without paralyzing the decision-making process is difficult. Implementing suggestions is a challenge. Navigating the changing nature of service provision (who can provision their own instances or assign licenses?) can be difficult as well. All these concerns must be addressed in a cloud strategy.

      Strategy component: Governance

      Without guardrails, the cloud deployment will grow organically. This has strengths (people tend to adopt solutions that they select and deploy themselves), but these are more than balanced out by the drawbacks that come with inconsistency, poor administration, duplication of services, suboptimal costing, and any number of other unique challenges. The solution is to develop and deploy governance. The following list captures some of the necessary governance-related components of a cloud strategy.

      Component Description Challenges
      Architecture Enterprise architecture is an important function in any environment with more than one interacting workload component (read: any environment). The cloud strategy should include an approach to defining and implementing a standard cloud architecture and should assign responsibility to an individual or group. Sometimes the cloud transition is inspired by the desire to rearchitect. The necessary skills and knowledge may not be readily available to design and transition to a microservices-based environment, for example, vs. a traditional monolithic application architecture. The appropriateness of a serverless environment may not be well understood, and it may be the case that architects are unfamiliar with cloud best practices and reference architectures.
      Integration and interoperability Many services are only highly functional when integrated with other services. What is a database without its front-end? What is an analytics platform without its data lake? For the cloud vision to be properly implemented, a strategy for handling integration and interoperability must be developed. It may be as simple as “all SaaS apps must be compatible with Okta” but it must be there. Migration to the cloud may require a fundamentally new approach to integration, moving away from a point-to-point integrations and towards an ESB or data lake. In many cases, this is easier said than done. Centralization of management may be appealing, but legacy applications – or those acquired informally in a one-off fashion – might not be so easy to integrate into a central management platform.
      Operations management Service management (ITIL processes) must be aligned with your overall cloud strategy. Migrating to the cloud (where applicable) will require refining these processes, including incident, problem, request, change, and configuration management, to make them more suitable for the cloud environment. Operations management doesn’t go away in the cloud, but it does change in line with the transition to shared responsibility. Responding to incidents may be more difficult on the cloud when troubleshooting is a vendor’s responsibility. Change management in a SaaS environment may be more receptive than staff are used to as cloud providers push changes out that cannot be rolled back.

      Strategy component: Governance (cont.)

      Component Description Challenges
      Cloud portfolio management This component refers to the act of managing the portfolio of cloud services that is available to IT and to business users. What requirements must a SaaS service meet to be onboarded into the environment? How do we account for exceptions to our IaaS policy? What about services that are only available from a certain provider? Rationalizing services offers administrative benefits, but may make some tasks more difficult for end users who have learned things a certain way or rely on niche toolsets. Managing access through a service catalog can also be challenging based on buy-in and ongoing administration. It is necessary to develop and implement policy.
      Cloud vendor management Who owns the vendor management function, and what do their duties entail? What contract language must be standard? What does due diligence look like? How should negotiations be conducted? What does a severing of the relationship look like? Cloud service models are generally different from traditional hosted software and even from each other (e.g. SaaS vs. PaaS). There is a bit of a learning curve when it comes to dealing with vendors. Also relevant: the skills that it takes to build and maintain a system are not necessarily the same as those required to coherently interact with a cloud vendor.
      Finance management Cloud services are, by definition, subject to a kind of granular, operational billing that many shops might not be used to. Someone will need to accurately project and allocate costs, while ensuring that services are monitored for cost abnormalities. Cloud cost challenges often relate to overall expense (“the cloud is more expensive than an alternative solution”), expense variability (“I don’t know what my budget needs to be this quarter”), and cost complexity (“I don’t understand what I’m paying for – what’s an Elastic Beanstalk?”).
      Security The cloud is not inherently more or less secure than a premises-based alternative, though the risk profile can be different. Applying appropriate security governance to ensure workloads are compliant with security requirements is an essential component of the strategy.

      Technical security architecture can be a challenge, as well as navigating the shared responsibility that comes with a cloud transition. There are also a plethora of cloud-specific security tools like cloud access security brokers (CASBs), cloud security posture management (CSPM) solutions, and even secure access services edge (SASE) technology.

      Data controls Data residency, classification, quality, and protection are important considerations for any cloud strategy. With cloud providers taking on outsized responsibility, understanding and governing data is essential. Cloud providers like to abstract away from the end user, and while some may be able to guarantee residency, others may not. Additionally, regulations may prevent some data from going to the cloud, and you may need to develop a new organizational backup strategy to account for the cloud.

      Strategy component: Technology

      Good technology will never replace good people and effective process, but it remains important in its own right. A migration that neglects the undeniable technical components of a solid cloud strategy is doomed to mediocrity at best and failure at worst. Understanding the technical implications of the cloud vision – particularly in terms of monitoring, provisioning, and migration – makes all the difference. You can interpret the results of the cloud workload assessments by reviewing the details presented here.

      Component Description Challenges
      Monitoring The cloud must be monitored in line with performance requirements. Staff must ensure that appropriate tools are in place to properly monitor cloud workloads and that they are capturing adequate and relevant data. Defining requirements for monitoring a potentially unfamiliar environment can be difficult, as can consolidating on a monitoring solution that both meets requirements and covers all relevant areas. There may be some upskilling and integration work required to ensure that monitoring works as required.
      Provisioning How will provisioning be done? Who will be responsible for ensuring the right people have access to the right resources? What tooling must be deployed to support provisioning goals? What technical steps must be taken to ensure that the provisioning is as seamless as possible? There is the inevitable challenge of assigning responsibility and accountability in a changing infrastructure and operations environment, especially if the changes are substantial (e.g. a fundamental operating model shift, reoriented around the cloud). Staff may also need to familiarize themselves with cloud-based provisioning tools like Ansible, Terraform, or even CloudFormation.
      Migration The act of migrating is important as well. In some cases, the migration is as simple as configuring the new environment and turning it up (e.g. with a net new SaaS service). In other cases, the migration itself can be a substantial undertaking, involving large amounts of data, a complicated replatforming/refactoring, and/or a significant configuration exercise.

      Not all migration journeys are created equal, and challenges include a general lack of understanding of the requirements of a migration, the techniques that might be necessary to migrate to a particular cloud (there are many) and the disruption/risk associated with moving large amounts of data. All of these challenges must be considered as part of the overall cloud strategy, whether in terms of architectural principles or skill acquisition (or both!).

      Step 2.2

      Determine workload future state

      Activities

      2.2.1 Determine workload future state

      Conduct workload assessments

      Determine workload future state

      This step involves the following participants:

      • IT management
      • Core working group

      Outcomes of this step

      • Completed workload assessments
      • Defined workload future state

      2.2.1 Determine workload future state

      1-3 hours

      Input

      • Completed workload assessments

      Output

      • Preliminary future state outputs

      Materials

      • Cloud Vision Workbook
      • Cloud Vision Executive Presentation

      Participants

      • Core working group
      • Service owners
      • IT management
      1. After you’ve had a chance to validate your results, refer to tab 7 of the tool, where you will find a blank notes section.
      2. With the working group, capture your answers to each of the following questions:
        1. What service model is the most suitable for the workload? Why?
        2. How will we conduct the migration? Which of the six models makes the most sense? Do we have a backup plan if our primary plan doesn’t work out?
        3. What should the support model look like?
        4. What are some workload-specific risks and considerations that must be taken into account for the workload?
      3. Once you’ve got answers to each of these questions for each of the workloads, include your summary in the “notes” section of tab 7.

      Cloud Vision Executive Presentation

      Paste the output into the Cloud Vision Executive Presentation

      • The Cloud Vision Workbook output is a compact, consumable summary of each workload’s planned future state. Paste each assessment in as necessary.
      • There is no absolutely correct way to present the information, but the output is a good place to start. Do note that, while the presentation is designed to lead with the vision statement, because the process is workload-first, the assessments are populated prior to the overall vision in a bottom-up manner.
      • Be sure to anticipate the questions you are likely to receive from any stakeholders. You may consider preparing for questions like: “What other workloads fit this profile?” “What do we expect the impact on the budget to be?” “How long will this take?” Keep these and other questions in mind as you progress through the vision definition process.

      The image shows the Cloud Vision Workbook output, which was described in an annotated version in an earlier section.

      Info-Tech Insight

      Keep your audience in mind. You may want to include some additional context in the presentation if the results are going to be presented to non-technical stakeholders or those who are not familiar with the terms or how to interpret the outputs.

      Identify and Mitigate Risks

      Build the foundations of your cloud vision

      PHASE 3

      Phase 3

      Identify and Mitigate Risks

      Phase 1

      1.1 Generate goals and drivers

      1.2 Explore cloud characteristics

      1.3 Create a current state summary

      1.4 Select workloads for analysis

      Phase 2

      2.1 Conduct workload assessments

      2.2 Determine workload future states

      Phase 3

      3.1 Generate risks and roadblocks

      3.2 Mitigate risks and roadblocks

      3.3 Define roadmap initiatives

      Phase 4

      4.1 Review and assign work items

      4.2 Finalize cloud decision framework

      4.3 Create cloud vision

      This phase will walk you through the following activities:

      • Generate risks and roadblocks
      • Mitigate risks and roadblocks
      • Define roadmap initiatives

      This phase involves the following participants:

      • Core working group
      • Workload subject matter experts

      You know what you want to do, but what do you have to do?

      What questions remain unanswered?

      There are workload-level risks and roadblocks, and there are environment-level risks. This phase is focused primarily on environment-level risks and roadblocks, or those that are likely to span multiple workloads (but this is not hard and fast rule – anything that you deem worth discussing is worth discussing). The framework here calls for an open forum where all stakeholders – technical and non-technical, pro-cloud and anti-cloud, management and individual contributor – have an opportunity to articulate their concerns, however specific or general, and receive feedback and possible mitigation.

      Start by soliciting feedback. You can do this over time or in a single session. Encourage anyone with an opinion to share it. Focus on those who are likely to have a perspective that will become relevant at some point during the creation of the cloud strategy and the execution of any migration. Explain the preliminary direction; highlight any major changes that you foresee. Remind participants that you are not looking for solutions (yet), but that you want to make sure you hear any and every concern as early as possible. You will get feedback and it will all be valuable.

      Before cutting your participants loose, remind them that, as with all business decisions, the cloud comes with trade-offs. Not everyone will have every wish fulfilled, and in some cases, significant effort may be needed to get around a roadblock, risks may need to be accepted, and workloads that looked like promising candidates for one service model or another may not be able to realize that potential. This is a normal and expected part of the cloud vision process.

      Once the risks and roadblocks conversation is complete, it is the core working group’s job to propose and validate mitigations. Not every risk can be completely resolved, but the cloud has been around for decades – chances are someone else has faced a similar challenge and made it through relatively unscathed. That work will inevitably result in initiatives for immediate execution. Those initiatives will form the core of the initiative roadmap that accompanies the completed Cloud Vision Executive Presentation.

      Step 3.1

      Generate risks and roadblocks

      Activities

      3.1.1 Generate risks and roadblocks

      3.1.2 Generate mitigations

      Identify and mitigate risks

      Generate risks and roadblocks

      Mitigate risks and roadblocks

      Define roadmap initiatives

      This step involves the following participants:

      • Core working group
      • IT management
      • Infrastructure
      • Applications
      • Security
      • Architecture

      Outcomes of this step

      • List of risks and roadblocks

      Understand risks and roadblocks

      Risk

      • Something that could potentially go wrong.
      • You can respond to risks by mitigating them:
        • Eliminate: take action to prevent the risk from causing issues.
        • Reduce: take action to minimize the likelihood/severity of the risk.
        • Transfer: shift responsibility for the risk away from IT, towards another division of the company.
        • Accept: where the likelihood or severity is low, it may be prudent to accept that the risk could come to fruition.

      Roadblock

      • There are things that aren’t “risks” that we care about when migrating to the cloud.
      • We know, for example, that a complicated integration situation will create work items for any migration – this is not an “unknown.”
      • We respond to roadblocks by generating work items.

      3.1.1 Generate risks and roadblocks

      1.5 hours

      Input

      • Completed cloud vision assessments

      Output

      • List of risks and roadblocks

      Materials

      • Whiteboard
      • Sticky notes

      Participants

      • Core working group
      • Service owners/workload SMEs
      • Anyone with concerns about the cloud
      1. Gather your core working group – and really anyone with an intelligent opinion on the cloud – into a single meeting space. Give the group 5-10 minutes to list anything they think could present a difficulty in transitioning workloads to the cloud. Write each risk/roadblock on its own sticky note. You will never be 100% exhaustive, but don’t let anything your users care about go unaddressed.
      2. Once everyone has had time to write down their risks and roadblocks, have everyone share one by one. Make sure you get them all. Overlap in risks and roadblocks is okay! Group similar concerns together to give a sort of heat map of what your participants are concerned about. (This is called “affinity diagramming.”)
      3. Assign names to these categories. Many of these categories will align with the strategy components discussed in the previous phase (governance, security, etc.) but some will be specific whether by nature or by degree.
      4. Sort each of the individual risks into its respective category, collapsing any exact duplicates, and leaving room for notes and mitigations (see the next slide for a visual).

      Understand risks and roadblocks

      The image is two columns--on the left, the column is titled Affinity Diagramming. Below the title, there are many colored blocks, randomly arranged. There is an arrow pointing right, to the same coloured blocks, now sorted by colour. In the right column--titled Categorization--each colour has been assigned a category, with subcategories.

      Step 3.2

      Mitigate risks and roadblocks

      Activities

      3.2.1 Generate mitigations

      Identify and mitigate risks

      Generate risks and roadblocks

      Mitigate risks and roadblocks

      Define roadmap initiatives

      This step involves the following participants:

      • Core working group

      Outcomes of this step

      • List of mitigations

      Is the public cloud less secure?

      This is the key risk-related question that most cloud customers will have to answer at some point: does migrating to the cloud for some services increase their exposure and create a security problem?

      As with all good questions, the answer is “it depends.” But what does it depend on? Consider these cloud risks and potential mitigations:

      1. Misconfiguration: An error grants access to unauthorized parties (as happened to Capital One in 2019). This can be mitigated by careful configuration management and third-party tooling.
      2. Unauthorized access by cloud provider/partner employees: Though rare, it is possible that a cloud provider or partner can be a vector for a breach. Careful contract language, choosing to own your own encryption keys, and a hybrid approach (storing data on-premises) are some possible ways to address this problem.
      3. Unauthorized access to systems: Cloud services are designed to be accessed from anywhere and may be accessed by malicious actors. Possible mitigations include risk-based conditional access, careful identity access management, and logging and detection.

      “The cloud is definitely more secure in that you have much more control, you have much more security tooling, much more visibility, and much more automation. So it is more secure. The caveat is that there is more risk. It is easier to accidentally expose data in the cloud than it is on-premises, but, especially for security, the amount of tooling and visibility you get in cloud is much more than anything we’ve had in our careers on-premises, and that’s why I think cloud in general is more secure.” –Abdul Kittana, Founder, ASecureCloud

      Breach bests bank

      No cloud provider can protect against every misconfiguration

      Industry: Finance

      Source: The New York Times, CNET

      Background

      Capital One is a major Amazon Web Services customer and is even featured on Amazon’s site as a case study. That case study emphasizes the bank’s commitment to the cloud and highlights how central security and compliance were. From the CTO: “Before we moved a single workload, we engaged groups from across the company to build a risk framework for the cloud that met the same high bar for security and compliance that we meet in our on-premises environments. AWS worked with us every step of the way.”

      Complication

      The cloud migration was humming along until July 2019, when the bank suffered a serious breach at the hands of a hacker. That hacker was able to steal millions of credit card applications and hundreds of thousands of Social Security numbers, bank account numbers, and Canadian social insurance numbers.

      According to investigators and to AWS, the breach was caused by an open reverse proxy attack against a misconfigured web app firewall, not by an underlying vulnerability in the cloud infrastructure.

      Results

      Capital One reported that the breach was expected to cost it $150 million, and AWS fervently denied any blame. The US Senate got involved, as did national media, and Capital One’s CEO issued a public apology, writing, “I sincerely apologize for the understandable worry this incident must be causing those affected, and I am committed to making it right.”

      It was a bad few months for IT at Capital One.

      3.2.1 Generate mitigations

      3-4.5 hours

      Input

      • Completed cloud vision assessments

      Output

      • List of risks and roadblocks

      Materials

      • Whiteboard
      • Sticky notes

      Participants

      • Core working group
      • Service owners/workload SMEs
      • Anyone with concerns about the cloud
      1. Recall the four mitigation strategies: eliminate, reduce, transfer, or accept. Keep these in mind as you work through the list of risks and roadblocks with the core working group. For every individual risk or roadblock raised in the initial generation session, suggest a specific mitigation. If the concern is “SaaS providers having access to confidential information,” a mitigation might be encryption, specific contract language, or proof of certifications (or all the above).
      2. Work through this for each of the risks and roadblocks, identifying the steps you need to take that would satisfy your requirements as you understand them.
      3. Once you have gone through the whole list – ideally with input from SMEs in particular areas like security, engineering, and compliance/legal – populate the Cloud Vision Workbook (tab 8) with the risks, roadblocks, and mitigations (sorted by category). Review tab 8 for an example of the output of this exercise.

      Cloud Vision Workbook

      Cloud Vision Workbook – mitigations

      The image shows a large chart titled Risks, roadblocks, and mitigations, which has been annotated with notes.

      Step 3.3

      Define roadmap initiatives

      Activities

      3.3.1 Generate roadmap initiatives

      Identify and mitigate risks

      Generate risks and roadblocks

      Mitigate risks and roadblocks

      Define roadmap initiatives

      This step involves the following participants:

      • Core working group

      Outcomes of this step

      • Defined roadmap initiatives

      3.3.1 Generate roadmap initiatives

      1 hour

      Input

      • List of risk and roadblock mitigations

      Output

      • List of cloud initiatives

      Materials

      • Cloud Vision Workbook

      Participants

      • Core working group
      1. Executing on your cloud vision will likely require you to undertake some key initiatives, many of which have already been identified as part of your mitigation exercise. On tab 8 of the Cloud Vision Workbook, review the mitigations you created in response to the risks and roadblocks identified. Initiatives should generally be assignable to a party and should have a defined scope/duration. For example, “assess all net new applications for cloud suitability” might not be counted as an initiative, but “design a cloud application assessment” would likely be.
      2. Design a timeline appropriate for your specific needs. Generally short-term (less than 3 months), medium-term (3-6 months), and long-term (greater than 6 months) will work, but this is entirely based on preference.
      3. Review and validate the parameters with the working group. Consider creating additional color-coding (highlighting certain tasks that might be dependent on a decision or have ongoing components).

      Cloud Vision Workbook

      Bridge the gap and create the vision

      Build the foundations of your cloud vision

      Phase 4

      Phase 4

      Bridge the Gap and Create the Vision

      Phase 1

      1.1 Generate goals and drivers

      1.2 Explore cloud characteristics

      1.3 Create a current state summary

      1.4 Select workloads for analysis

      Phase 2

      2.1 Conduct workload assessments

      2.2 Determine workload future states

      Phase 3

      3.1 Generate risks and roadblocks

      3.2 Mitigate risks and roadblocks

      3.3 Define roadmap initiatives

      Phase 4

      4.1 Review and assign work items

      4.2 Finalize cloud decision framework

      4.3 Create cloud vision

      This phase will walk you through the following activities:

      • Assign initiatives and propose timelines
      • Build a delivery model rubric
      • Build a service model rubric
      • Built a support model rubric
      • Create a cloud vision statement
      • Map cloud workloads
      • Complete the Cloud Vision presentation

      This phase involves the following participants:

      • IT management, the core working group, security, infrastructure, operations, architecture, engineering, applications, non-IT stakeholders

      Step 4.1

      Review and assign work items

      Activities

      4.1.1 Assign initiatives and propose timelines

      Bridge the gap and create the vision

      Review and assign work items

      Finalize cloud decision framework

      Create cloud vision

      This step involves the following participants:

      • Core working group
      • IT management

      Outcomes of this step

      • Populated cloud vision roadmap

      4.1.1 Assign initiatives and propose timelines

      1 hour

      Input

      • List of cloud initiatives

      Output

      • Initiatives assigned by responsibility and timeline

      Materials

      • Cloud Vision Workbook

      Participants

      • Core working group
      1. Once the list is populated, begin assigning responsibility for execution. This is not a RACI exercise, so focus on the functional responsibility. Once you have determined who is responsible, assign a timeline and include any notes. This will form the basis of a more formal project plan.
      2. To assign the initiative to a party, consider 1) who will be responsible for execution and 2) if that responsibility will be shared. Be as specific as possible, but be sure to be consistent to make it easier for you to sort responsibility later on.
      3. When assigning timelines, we suggest including the end date (when you expect the project to be complete) rather than the start date, though whatever you choose, be sure to be consistent. Make use of the notes column to record anything that you think any other readers will need to be aware of in the future, or details that may not be possible to commit to memory.

      Cloud Vision Workbook

      Step 4.2

      Finalize cloud decision framework

      Activities

      4.2.1 Build a delivery model rubric

      4.2.2 Build a service model rubric

      4.2.3 Build a support model rubric

      Bridge the gap and create the vision

      Review and assign work items

      Finalize cloud decision framework

      Create cloud vision

      This step involves the following participants:

      • Core working group

      Outcomes of this step

      • Cloud decision framework

      4.2.1 Build a delivery model rubric

      1 hour

      Input

      • List of cloud initiatives

      Output

      • Initiatives assigned by responsibility and timeline

      Materials

      Participants

      • Core working group
      1. Now that we have a good understanding of the cloud’s key characteristics, the relative suitability of different workloads for the cloud, and a good understanding of some of the risks and roadblocks that may need to be overcome if a cloud transition is to take place, it is time to formalize a delivery model rubric. Start by listing the delivery models on a white board vertically – public, private, hybrid, and multi-cloud. Include a community cloud option as well if that is feasible for you. Strike any models that do not figure into your vision.
      2. Create a table style rubric for each delivery model. Confer with the working group to determine what characteristics best define workloads suitable for each model. If you have a hybrid cloud option, you may consider workloads that are highly dynamic; a private cloud hosted on-premises may be more suitable for workloads that have extensive regulatory requirements.
      3. Once the table is complete, include it in the Cloud Vision Executive Presentation.

      Cloud Vision Executive Presentation

      Vision for the cloud future state (example)

      Delivery model Decision criteria
      Public cloud
      • Public cloud is the primary destination for all workloads as the goal is to eliminate facilities and infrastructure management
      • Offers features, broad accessibility, and managed updates along with provider-managed facilities and hardware
      Legacy datacenter
      • Any workload that is not a good fit for the public cloud
      • Dependency (like a USB key for license validation)
      • Performance requirements (e.g. workloads highly sensitive to transaction thresholds)
      • Local infrastructure components (firewall, switches, NVR)

      Summary statement: Everything must go! Public cloud is a top priority. Anything that is not compatible (for whatever reason) with a public cloud deployment will be retained in a premises-based server closet (downgraded from a full datacenter). The private cloud does not align with the overall organizational vision, nor does a hybrid solution.

      4.2.2 Build a service model rubric

      1 hour

      Input

      • Output of workload assessments
      • Output of risk and mitigation exercise

      Output

      • Service model rubric

      Materials

      • Whiteboard
      • Cloud Vision Executive Presentation

      Participants

      • Core working group
      1. This next activity is like the delivery model activity, but covers the relevant cloud service models. On a whiteboard, make a vertical list of the cloud service models (SaaS, PaaS, IaaS, etc.) that will be considered for workloads. If you have an order of preference, place your most preferred at the top, your least preferred at the bottom.
      2. Describe the circumstances under which you would select each service model. Do your best to focus on differentiators. If a decision criterion appears for multiple service models, consider refining or excluding it. (For additional information, check out Info-Tech’s Reimagine IT Operations for a Cloud-First World blueprint.)
      3. Create a summary statement to capture your overall service model position. See the next slide for an example. Note: this can be incorporated into your cloud vision statement, so be sure that it reflects your genuine cloud preferences.
      4. Record the results in the Cloud Vision Executive Presentation.

      Cloud Vision Executive Presentation

      Vision for the cloud future state (example)

      Service model Decision criteria
      SaaS

      SaaS first; opt for SaaS when:

      • A SaaS option exists that meets all key business requirements
      • There is a strong desire to have someone else (the vendor) manage infrastructure components/the platform
      • Not particularly sensitive to performance thresholds
      • The goal is to transition management of the workload outside of IT
      • SaaS is the only feasible way to consume the desired service
      PaaS
      • Highly customized service/workload – SaaS not feasible
      • Still preferable to offload as much management as possible to third parties
      • Customization required, but not at the platform level
      • The workload is built using a standard framework
      • We have the time/resources to replatform
      IaaS
      • Service needs to be lifted and shifted out of the datacenter quickly
      • Customization is required at the platform level/there is value in managing components
      • There is no need to manage facilities
      • Performance is not impacted by hosting the workload offsite
      • There is value in right-sizing the workload over time
      On-premises Anything that does not fit in the cloud for performance or other reasons (e.g. licensing key)

      Summary statement: SaaS will be the primary service model. All workloads will migrate to the public cloud where possible. Anything that cannot be migrated to SaaS will be migrated to PaaS. IaaS is a transitory step.

      4.2.3 Build a support model rubric

      1 hour

      Input

      • Results of the cloud workload assessments

      Output

      • Support model rubric

      Materials

      • Whiteboard
      • Cloud Vision Executive Presentation

      Participants

      • Core working group
      1. The final rubric covered here is that for the support model. Where will you procure the skills necessary to ensure the vision’s proper execution? Much like the other rubric activities, write the three support models vertically (in order of preference, if you have one) on a whiteboard.
      2. Next to each model, describe the circumstances under which you would select each support model. Focus on the dimensions: the duration of the engagement, specialization required, and flexibility required. If you have existing rules/practices around hiring consultants/MSPs, consider those as well.
      3. Once you have a good list of decision criteria, form a summary statement. This should encapsulate your position on support models and should mention any notable criteria that will contribute to most decisions.
      4. Record the results in the Cloud Vision Executive Presentation.

      Cloud Vision Executive Presentation

      Vision for the cloud future state (example)

      Support model Decision criteria
      Internal IT

      The primary support model will be internal IT going forward

      • Chosen where the primary work required is administrative
      • Where existing staff can manage the service in the cloud easily and effectively
      • Where the chosen solution fits the SaaS service model
      Consultant
      • Where the work required is time-bound (e.g. a migration/refactoring exercise)
      • Where the skills do not exist in house, and where the skills cannot easily be procured (specific technical expertise required in areas of the cloud unfamiliar to staff)
      • Where opportunities for staff to learn from consultant SMEs are valuable
      • Where ongoing management and maintenance can be handled in house
      MSP
      • Where an ongoing relationship is valued
      • Where ongoing administration and maintenance are disproportionately burdensome on IT staff (or where this administration and maintenance is likely to be burdensome)
      • Where the managed services model has already been proven out
      • Where specific expertise in an area of technology is required but this does not rise to the need to hire an FTE (e.g. telephony)

      Summary statement: Most workloads will be managed in house. A consultant will be employed to facilitate the transition to micro-services in a cloud container environment, but this will be transitioned to in-house staff. An MSP will continue to manage backups and telephony.

      Step 4.3

      Create cloud vision

      Activities

      4.3.1 Create a cloud vision statement

      4.3.2 Map cloud workloads

      4.3.3 Complete the Cloud Vision Presentation

      Review and assign work items

      Finalize cloud decision framework

      Create cloud vision

      This step involves the following participants:

      • Core working group
      • IT management

      Outcomes of this step

      Completed Cloud Vision Executive Presentation

      4.3.1 Create a cloud vision statement

      1 hour

      Input

      • List of cloud initiatives

      Output

      • Initiatives assigned by responsibility and timeline

      Materials

      • Cloud Vision Workbook

      Participants

      • Core working group
      1. Now that you know what service models are appropriate, it’s time to summarize your cloud vision in a succinct, consumable way. A good vision statement should have three components:
        • Scope: Which parts of the organization will the strategy impact?
        • Goal: What is the strategy intended to accomplish?
        • Key differentiator: What makes the new strategy special?
      2. On a whiteboard, make a chart with three columns (one column for each of the features of a good mission statement). Have the group generate a list of words to describe each of the categories. Ideally, the group will produce multiple answers for each category.
      3. Once you’ve gathered a few different responses for each category, have the team put their heads down and generate pithy mission statements that capture the sentiments underlying each category.
      4. Have participants read their vision statements in front of the group. Use the rest of the session to produce a final statement. Record the results in the Cloud Strategy Executive Presentation.

      Example vision statement outputs

      “IT at ACME Corp. hereby commits to providing clients and end users with an unparalleled, productivity-enabling technology experience, leveraging, insofar as it is possible and practical, cloud-based services.”

      “At ACME Corp. our employees and customers are our first priority. Using new, agile cloud services, IT is devoted to eliminating inefficiency, providing cutting-edge solutions for a fast-paced world, and making a positive difference in the lives of our colleagues and the people we serve.”

      As a global leader in technology, ACME Corp. is committed to taking full advantage of new cloud services, looking first to agile cloud options to optimize internal processes wherever efficiency gaps exist. Improved efficiency will allow associates to spend more time on ACME’s core mission: providing an unrivalled customer experience.”

      Scope

      Goal

      Key differentiator

      4.3.2 Map cloud workloads

      1 hour

      Input

      • List of workloads
      • List of acceptable service models
      • List of acceptable migration paths

      Output

      • Workloads mapped by service model/migration path

      Materials

      • Whiteboard
      • Sticky notes

      Participants

      • Core working group
      1. Now that you have defined your overall cloud vision as well as your service model options, consider aligning your service model preferences with your migration path preferences. Draw a table with your expected migration strategies across the top (retain, retire, rehost, replatform, refactor, repurchase, or some of these) and your expected service models across the side.
      2. On individual sticky notes, write a list of workloads in your environment. In a smaller environment, this list can be exhaustive. Otherwise take advantage of the list you created as part of phase 1 along with any additional workloads that warrant discussion.
      3. As a group, go through the list, placing the sticky notes first in the appropriate row based on their characteristics and the decision criteria that have already been defined, and then in the appropriate column based on the appropriate migration path. (See the next slide for an example of what this looks like.)
      4. Record the results in the Cloud Vision Executive Presentation. Note: not every cell will be filled; some migration path/service model combinations are impossible or otherwise undesirable.

      Cloud Vision Executive Presentation

      Example cloud workload map

      Repurchase Replatform Rehost Retain
      SaaS

      Office suite

      AD

      PaaS SQL Database
      IaaS File Storage DR environment
      Other

      CCTV

      Door access

      4.3.3 Complete the Cloud Vision Presentation

      1 hour

      Input

      • List of cloud initiatives

      Output

      • Initiatives assigned by responsibility and timeline

      Materials

      • Cloud Vision Workbook

      Participants

      • Core working group
      1. Open the Cloud Vision Executive Presentation to the second slide and review the templated executive brief. This comprises several sections (see the next slide). Populate each one:
        • Summary of the exercise
        • The cloud vision statement
        • Key cloud drivers
        • Risks and roadblocks
        • Top initiatives and next steps
      2. Review the remainder of the presentation. Be sure to elaborate on any significant initiatives and changes (where applicable) and to delete any slides that you no longer require.

      Cloud Vision Workbook

      Sample cloud vision executive summary

      • From [date to date], a cross-functional group representing IT and its constituents met to discuss the cloud.
      • Over the course of the week, the group identified drivers for cloud computing and developed a shared vision, evaluated several workloads through an assessment framework, identified risks, roadblocks, and mitigations, and finally generated initiatives and next steps.
      • From the process, the group produced a summary and a cloud suitability assessment framework that can be applied at the level of the workload.

      Cloud Vision Statement

      [Organization] will leverage public cloud solutions and retire existing datacenter and colocation facilities. This transition will simplify infrastructure administration, support, and security, while modernizing legacy infrastructure and reducing the need for additional capital expenditure.

      Cloud Drivers Retire the datacenter Do more valuable work
      Right-size the environment Reduce CapEx
      Facilitate ease of mgmt. Work from anywhere
      Reduce capital expenditure Take advantage of elasticity
      Performance and availability Governance Risks and roadblocks
      Security Rationalization
      Cost Skills
      Migration Remaining premises resources
      BC, backup, and DR Control

      Initiatives and next steps

      • Close the datacenter and colocation site in favor of a SaaS-first cloud approach.
      • Some workloads will migrate to infrastructure-as-a-service in the short term with the assistance of third-party consultants.

      Document your cloud strategy

      You did it!

      Congratulations! If you’ve made it this far, you’ve successfully articulated a cloud vision, assessed workloads, developed an understanding (shared with your team and stakeholders) of cloud concepts, and mitigated risks and roadblocks that you may encounter along your cloud journey. From this exercise, you should understand your mission and vision, how your cloud plans will interact with any other relevant strategic plans, and what successful execution looks like, as well as developing a good understanding of overall guiding principles. These are several components of your overall strategy, but they do not comprise the strategy in its entirety.

      How do you fix this?

      First, validate the results of the vision exercise with your stakeholders. Socialize it and collect feedback. Make changes where you think changes should be made. This will become a key foundational piece. The next step is to formally document your cloud strategy. This is a separate project and is covered in the Info-Tech blueprint Document Your Cloud Strategy.

      The vision exercise tells you where you want to go and offers some clues as to how to get there. The formal strategy exercise is a formal documentation of the target state, but also captures in detail the steps you’ll need to take, the processes you’ll need to refine, and the people you’ll need to hire.

      A cloud strategy should comprise your organizational stance on how the cloud will change your approach to people and human resources, technology, and governance. Once you are confident that you can make and enforce decisions in these areas, you should consider moving on to Document Your Cloud Strategy. This blueprint, Define Your Cloud Vision, often serves as a prerequisite for the strategy documentation conversation(s).

      Appendix

      Summary of Accomplishment

      Additional Support

      Research Contributors

      Related Info-Tech Research

      Vendor Resources

      Bibliography

      Summary of Accomplishment

      Problem Solved

      You have now documented what you want from the cloud, what you mean when you say “cloud,” and some preliminary steps you can take to make your vision a reality.

      You now have at your disposal a framework for identifying and evaluating candidates for their cloud suitability, as well as a series of techniques for generating risks and mitigations associated with your cloud journey. The next step is to formalize your cloud strategy using the takeaways from this exercise. You’re well on your way to a completed cloud strategy!

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech workshop.

      Contact your account representative for more information.

      workshops@infotech.com

      1-888-670-8889

      Additional Support

      If you would like additional support, have our analysts guide you through other phases as part of an Info-Tech Workshop.

      Contact your account representative for more information.

      workshops@infotech.com 1-888-670-8889

      To accelerate this project, engage your IT team in an Info-Tech workshop with an Info-Tech analyst team.

      Info-Tech analysts will join you and your team at your location or welcome you to Info-Tech’s historic Toronto office to participate in an innovative onsite workshop.

      The following are sample activities that will be conducted by Info-Tech analysts with your team:

      Generate drivers for cloud adoption

      Work with stakeholders to understand the expected benefits of the cloud migration and how these drivers will impact the overall vision.

      Conduct workload assessments

      Assess your individual cloud workloads for their suitability as candidates for the cloud migration.

      Bibliography

      “2021 State of the Cloud Report.” Flexera, 2021. Web.

      “2021 State of Upskilling Report.” Pluralsight, 2021. Web.

      “AWS Snowmobile.” Amazon Web Services, n.d. Web.

      “Azure products.” Microsoft, n.d. Web.

      “Azure Migrate Documentation.” Microsoft, n.d. Web.

      Bell, Harold. “Multi-Cloud vs. Hybrid Cloud: What’s the Difference?” Nutanix, 2019. Web.

      “Cloud Products.” Amazon Web Services, n.d. Web.

      “COBIT 2019 Framework: Introduction and Methodology.” ISACA, 2019. Web.

      Edmead, Mark T. “Using COBIT 2019 to Plan and Execute an Organization’s Transformation Strategy.” ISACA, 2020. Web.

      Flitter, Emily, and Karen Weise. “Capital One Data Breach Compromises Data of Over 100 Million.” The New York Times, 29 July 2019. Web.

      Gillis, Alexander S. “Cloud Security Posture Management (CSPM).” TechTarget, 2021. Web.

      “’How to Cloud’ with Capital One.” Amazon Web Services, n.d. Web.

      “IBM Closes Landmark Acquisition of Red Hat for $34 Billion; Defines Open, Hybrid Cloud Future.” Red Hat, 9 July 2019. Web.

      Mell, Peter, and Timothy Grance. “The NIST Definition of Cloud Computing.” National Institute of Standards and Technology, Sept. 2011. Web.

      Ng, Alfred. “Amazon Tells Senators it Isn't to Blame for Capital One Breach.” CNET, 2019. Web.

      Orban, Stephen. “6 Strategies for Migrating Applications to the Cloud.” Amazon Web Services, 2016. Web.

      Sullivan, Dan. “Cloud Access Security Broker (CASB).” TechTarget, 2021. Web.

      “What Is Secure Access Service Edge (SASE)?” Cisco, n.d. Web.

      Develop an IT Infrastructure Services Playbook

      • Buy Link or Shortcode: {j2store}451|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: 2 Average Days Saved
      • member rating average days saved: After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.
      • Parent Category Name: Operations Management
      • Parent Category Link: /i-and-o-process-management
      • Infrastructure and operations teams are managing deployments on- and off-premises, and across multiple infrastructure services providers.
      • Though automation tools speed up the delivery process, documentation is always pushed off so the team can meet urgent deadlines.
      • Without documented delivery processes, wait times are longer, controls are adequate but ad hoc, builds are non-standard, and errors are more likely to be introduced in production.

      Our Advice

      Critical Insight

      • Prioritize in-demand services to add to the playbook. Pilot a few services to get value from the project quickly.
      • Do not get lost in automation or tooling. You do not need a complex tool or back-end automation to get value from this project.
      • Learn, then iterate. With a few completed service processes, it is much easier to identify opportunities for service automation.

      Impact and Result

      • Prioritize in-demand services for documentation and standardization.
      • Build service workflows and document service requirements in the services playbook.
      • Create a costing model and track costs to deliver defined services.
      • Leverage data on costs and service requirements to improve service delivery.

      Develop an IT Infrastructure Services Playbook Research & Tools

      Start here – read the Executive Brief

      Read this Executive Brief to find out why you should create an infrastructure services playbook, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

      Besides the small introduction, subscribers and consulting clients within this management domain have access to:

      1. Define and prioritize infrastructure services

      Produce a prioritized list of high-demand infrastructure services.

      • Develop an IT Infrastructure Services Playbook – Phase 1: Define and Prioritize Infrastructure Services
      • Infrastructure Services Playbook

      2. Build workflows and an infrastructure services playbook

      Design workflows and create the first draft of the infrastructure services playbook.

      • Develop an IT Infrastructure Services Playbook – Phase 2: Build Workflows and an Infrastructure Services Playbook
      • Infrastructure Service Workflows (Visio)
      • Infrastructure Service Workflows (PDF)

      3. Identify costs and mature service delivery capabilities

      Build a service rate sheet to track costs and develop better service capabilities.

      • Develop an IT Infrastructure Services Playbook – Phase 3: Identify Costs and Mature Service Delivery Capabilities
      • Service Rate Sheet
      • Infrastructure Service Catalog Mind Map Example
      [infographic]

      Workshop: Develop an IT Infrastructure Services Playbook

      Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

      1 Define and Prioritize Infrastructure Services

      The Purpose

      Define and prioritize infrastructure services.

      Key Benefits Achieved

      Identify candidate services for the Playbook.

      Activities

      1.1 Define the services you own.

      1.2 Prioritize infrastructure services.

      Outputs

      Affinity map of infrastructure services

      Service pain points and root causes

      A list of high-demand infrastructure services

      2 Build the Infrastructure Services Playbook

      The Purpose

      Build workflows and an infrastructure services playbook.

      Key Benefits Achieved

      Produce a draft infrastructure services playbook.

      Activities

      2.1 Design workflow for service delivery.

      2.2 Add steps and requirements to the Services Playbook.

      Outputs

      Documented service workflows

      Infrastructure Services Playbook

      3 Identify Costs and Mature Service Delivery Capabilities

      The Purpose

      Identify costs and mature service delivery capabilities.

      Key Benefits Achieved

      Build an infrastructure service rate sheet.

      Define next steps for infrastructure service capabilities.

      Activities

      3.1 Optimize infrastructure cost estimates.

      3.2 Mature your I&O organization into a service broker.

      Outputs

      Service Rate Sheet

      Master list of infrastructure services

      Action plan for Playbook implementation

      Further reading

      Develop an IT Infrastructure Services Playbook

      Automation, SDI, and DevOps – build a cheat sheet to manage a changing Infrastructure & Operations environment.

      Table of contents

      Analyst Perspective

      Executive Summary

      Project Overview

      Summary and Conclusion

      ANALYST PERSPECTIVE

      Technology is changing how infrastructure services are delivered.

      "Managing a hybrid infrastructure environment is challenge enough. Add to this the pressure on IT Operations to deliver services faster and more continuously – it’s a recipe for boondoggle deployments, overcommitted staff, end-user frustration, and operational gridlock.

      It’s not every service you provide that causes problems, so prioritize a few in-demand, painful services. Build and maintain durable, flexible processes that enable your team to provide consistent, repeatable services at a standard cost. Identify opportunities to improve service delivery.

      You’ll save the business time and money and your own team significant grief." (Andrew Sharp, Research Manager, Infrastructure & Operations, Info-Tech Research Group)

      Your infrastructure and operations team is a service provider; standardize, document, and communicate service capabilities

      This Research is Designed For:

      • CTOs and Infrastructure Managers
      • Service Level Managers
      • ITSM Managers and Process Owners

      This Research Will Help You:

      • Inventory services that IT Infrastructure & Operations (I&O) provides to the business (servers, storage, and network).
      • Standardize services and track costs.
      • Articulate the value of these services to business owners.
      • Develop a catalog of infrastructure services.

      This Research Will Also Assist:

      • CIOs
      • Application Development Managers
      • Security Managers
      • Auditors

      This Research Will Help Them:

      • Understand the complexities of technical service delivery.
      • Make better strategic IT infrastructure decisions.

      Executive summary

      Situation

      • Infrastructure and operations teams are managing deployments on- and off-premises and across multiple infrastructure service providers.
      • Though automation tools speed up the delivery process, documentation is always pushed off so the team can meet urgent deadlines.

      Complication

      • Cloud providers have set the bar high for ease of access to stable infrastructure services.
      • Without documented delivery processes, wait times are longer, controls are adequate but ad hoc, builds are non-standard, and errors are more likely to be introduced in production.

      Resolution

      • Prioritize in-demand services for documentation and standardization.
      • Build service workflows and document service requirements in the services playbook.
      • Create a costing model and track costs to deliver defined services.
      • Leverage data on costs and service requirements to improve service delivery.

      Info-Tech Insight

      1. Keep it simple. Work through a few in-demand services to get early value from the project.
      2. Don’t get lost in automation or tooling. You don’t need a complex tool or back-end automation to get value from standardized services.
      3. Do then iterate. With a few completed service processes, it’s much easier to identify opportunities for service automation.

      Create an infrastructure services playbook to improve efficiency, support DevOps, and streamline service delivery

      Begin building an infrastructure services playbook by defining the services you provide. This will also help your team support changes to service delivery (e.g. more use of cloud services and the shift to DevOps).

      In this blueprint, the first step will be to document infrastructure services to:

      1. Clarify infrastructure capabilities and achievable service levels.

        Document infrastructure services to clarify achievable service levels with given resources and what you will need to meet service-level requirement gaps. Establishing your ability to meet customer demands is the first step toward becoming a broker of internal or external services.
      2. Standardize infrastructure service delivery.

        Sometimes, it’s extremely important to do the exact same thing every time (e.g. server hardening). Sometimes, your team needs room to deviate from the script. Create a playbook that allows you to standardize service delivery as needed.
      3. Make good strategic infrastructure decisions.

        Knowledge is power. Defined services and capabilities will help you make important strategic infrastructure decisions around capacity planning and when outsourcing is appropriate.

      Review and optimize infrastructure service delivery as you shift to more cloud-based services

      If you can’t standardize and streamline how you support cloud services, you risk AppDev and business leaders circumventing the I&O team.

      Logo for 'vmware'.

      Example:

      Create a new server resource in a virtual environment vs. public cloud

      In a virtualized environment, provisioning processes can still be relatively siloed.

      In a software-defined environment, many steps require knowledge across the infrastructure stack. Better documentation will help your team deliver services outside their area of specialty.

      Logo for 'Microsoft Azure'.
      • Identify CPU requirements for a virtual machine (VM)
      • Calculate VM memory requirements
      • Configure the floppy drive for a VM
      • Configure IDE devices for a VM
      • Configure SCSI adapters for a VM
      • Configure network adapters for a VM
      • Configure VM priority for host CPU resources
      • Server is live

      • Complete SDI code development & review, version control, build status, etc.
      • Identify software and specifications for the instance you want to use
      • Review configuration, storage, and security settings
      • Secure the instance with an existing key pair or create a new key pair
      • Update documentation – public IP address, physical & logical connections, data flows, etc.
      • Launch and connect to instance
      • Server is live

      Strengthen DevOps with an infrastructure playbook

      The purpose behind DevOps is to reduce friction and deliver faster, more continuous, more automated services through the use of cross-functional teams.

      DevOps: bridging Applications Development and Infrastructure & Operations by embracing a culture, practices, and tools born out of Lean and Agile methodologies.

      • Create a common language across functions.
      • Ensure that all service steps are documented.
      • Move towards more standard deployments.
      • Increase transparency within the IT department.
      • Cultivate trust across teams.
      • Build the foundation for automated services.
      A colorful visualization of the DevOps cycle. On the Development side is 'Feedback', Plan', 'Build', 'Integrate', then over to the Operations side is 'Deploy', and 'Operate', then back to Dev with 'Feedback', starting the cycle over again.

      "The bar has been raised for delivering technology products and services – what was good enough in previous decades is not good enough now." (Kim, Humble, Debois, Willis (2016))

      Leverage an infrastructure services playbook to improve service delivery, one step at a time

      Crawl

      • Prioritize infrastructure services that are good candidates for standardization.
      • Document the steps and requirements to deliver the service.
      • Use the playbook and workflows internally as you gather requirements and deliver on requests.
      • Track costs internally.

      Walk

      • Provide infrastructure clients with the playbook and allow them to make requests against it.
      • Update and maintain existing documentation.
      • Automate, where possible.
      • Showback costs to the business.

      Run

      • Provide infrastructure customers with scripts to provision infrastructure resources.
      • Audit requests before fulfilling them.
      • Chargeback costs, as needed.
      A turtle smiles happily on four legs, simply content to be alive. Another turtle moves quickly on two legs, seemingly in a runner's trance, eyes closed, oblivious to the fact that another turtle has beaten him to finish line.

      Focus on in-demand infrastructure services — PHASE 1

      Standardize in-demand, repeatable services first.

      Demand for infrastructure services is usually driven by external requests or operational requirements. Prioritize services based on criticality, durability, frequency, availability, and urgency requirements.

      Scheduling Delays
      • Dealing with a slew of capital projects driven by a major funding initiative, the IT team of a major US transit system is struggling to execute on basic operational tasks.

      • Action:
      • A brainstorming and prioritization exercise identifies web server deployment as their most in-demand service.
      • Identifying breakdowns in web server deployment helps free up resources for other tasks and addresses a serious pain point.
      Think outside the box
      • On a new project for a sporting goods client, the IT department for a marketing firm deploys and supports a “locker” kiosk that users engage with for a chance to win a gift.

      • Action:
      • As the campaign proves successful, the I&O Manager creates a playbook to guide kiosk support and deployment in the future, including required skills, timelines, success metrics, and costs.
      Keep it standard, keep it safe
      • An IT audit at a higher education institution finds that no standard process for server hardening has been defined or documented by the infrastructure team.

      • Action:
      • Improving IT security is a strategic priority for the department.
      • The infrastructure team decides to standardize and document processes, guidelines, and configurations for hardening OS, SCCM, SaltStack, scripting, and patching.

      Leverage service workflows to populate the playbook — PHASE 2

      Infrastructure as Code is breaking down traditional infrastructure silos and support models.

      1. Document the workflow to deliver the service. Identify pain points and target broken processes first.
        Provision –› Configure –› Run –› Quiesce –› Destroy
      2. Define logical expected results and metrics for problematic steps in the process. Identify challenges and possible improvements to each problematic step.
        Building and deploying toolsets is taking a long time
        Start
        • Create a baseline offering for common requests.
        • Make clear that non-standard requests will take time to fulfil.
        Stop
        • Move to just one web server.
        Continue
        • Use weekly drop-ins to communicate the change.
      3. Document skills and roles, approvers, and pre-requirements to fill out the documentation, as needed. Use the documented process to guide internal process and align with external expectations.

      Cross-silo knowledge is needed: In a software-defined environment, building and launching a new server requires knowledge across the stack.

      • Complete SDI code development & review, version control, build status, etc.
      • Identify software and specifications for the instance you want to use
      • Review configuration, storage, and security settings
      • Secure the instance with an existing key pair, or create a new key pair
      • Update documentation – public IP address, physical & logical connections, data flows, etc.
      • Launch and connect to the instance
      • Server is live

      Take a progressive approach to cost tracking — PHASE 3

      Infrastructure & Operations are bound by two metrics:

      1. Are systems up?
      2. Is technology delivered as efficiently as possible?

      Because tracking cost is integral to efficiency, cost and budget management, by proxy, is one of the most important Infrastructure & Operations metrics.

      Cost management is not a numbers game. It is an indicator of how well infrastructure is managed.

      Track costs in a practical way that delivers value to your organization:

      1. Build and leverage an internal rate sheet to help estimate cost to serve.
      2. Showback rate sheet to help managers and architects make better infrastructure decisions.
      3. Chargeback costs to defined cost centers.

      Project overview

      Use Info-Tech’s methodology to get value faster from your infrastructure services playbook.

      Phases

      Phase 1: Define and prioritize infrastructure services Phase 2: Build the infrastructure services playbook Phase 3: Identify costs and mature service delivery capabilities

      Steps

      1.1 Define the services you own 2.1 Design workflows for service delivery 3.1 Estimate infrastructure service costs
      1.2 Prioritize infrastructure services 2.2 Add steps and requirements to the services playbook 3.2 Mature your I&O organization into a service broker

      Tools & Templates

      Infrastructure Services Playbook Infrastructure Service Workflows Service Rate Sheet

      Use these icons to help direct you as you navigate this research

      Use these icons to help guide you through each step of the blueprint and direct you to content related to the recommended activities.

      A small monochrome icon of a wrench and screwdriver creating an X.

      This icon denotes a slide where a supporting Info-Tech tool or template will help you perform the activity or step associated with the slide. Refer to the supporting tool or template to get the best results and proceed to the next step of the project.

      A small monochrome icon depicting a person in front of a blank slide.

      This icon denotes a slide with an associated activity. The activity can be performed either as part of your project or with the support of Info-Tech team members, who will come onsite to facilitate a workshop for your organization.

      Info-Tech offers various levels of support to best suit your needs

      DIY Toolkit

      Guided Implementation

      Workshop

      Consulting

      "Our team has already made this critical project a priority, and we have the time and capability, but some guidance along the way would be helpful." "Our team knows that we need to fix a process, but we need assistance to determine where to focus. Some check-ins along the way would help keep us on track." "We need to hit the ground running and get this project kicked off immediately. Our team has the ability to take this over once we get a framework and strategy in place." "Our team does not have the time or the knowledge to take this project on. We need assistance through the entirety of this project."

      Diagnostics and consistent frameworks used throughout all four options

      Guided Implementation Overview

      Your Trusted Advisor is just a call away.

      Scoping
      (Call 1)

      Scope requirements, objectives, and stakeholders. Review the playbook toolset and methodology, and establish fit-for-need.

      Identify Services
      (Call 2)

      Brainstorm common infrastructure services your group provides. Consolidate the list and identify priority services.

      Create Service Workflows
      (Calls 3-4)

      Build Visio workflows for 2-3 priority services.

      Populate the Playbook
      (Calls 4-5)

      Add data to the playbook based on infrastructure service workflows

      Create a Rate Sheet for Costs
      (Call 6)

      Build a rate sheet that allows you to calculate costs for additional

      Your Guided Implementation will pair you with an advisor from our analyst team for the duration of your infrastructure services project.

      Workshop Overview

      Module 1
      (Day 1)
      Module 1
      (Day 1)
      Module 1
      (Day 1)
      Offsite deliverables wrap-up (Day 5)
      Activities
      Define and Prioritize Infrastructure Services

      1.1 Assess current maturity of services and standardization processes.

      1.2 Identify, group, and break out important infrastructure services.

      1.3 Define service delivery pain points and perform root-cause analysis.

      1.4 Prioritize services based on demand criteria.

      Build the Infrastructure Services Playbook

      2.1 Determine criteria for standard versus custom services.

      2.2 Document standard workflows for better alignment and consistent delivery.

      2.3 Build a flowchart for the identified high-demand service(s).

      2.4 Outline information as it relates to the service lifecycle in the Playbook template.

      Identify Costs and Mature Service Delivery Capabilities

      4.1 Gather information for the rate sheet.

      4.2 Choose an allocation method for overhead costs.

      4.3 Select the right approach in the crawl, walk, run model for your organization.

      4.4 Discuss the promotion plan and target revision dates for playbook and rate sheet.

      Deliverables
      1. High-demand infrastructure services list
      1. Right-sized criteria for standardization
      2. Service workflows
      3. Infrastructure Services Playbook
      1. Service Rate Sheet
      2. Deployment plan

      Develop an IT Infrastructure Services Playbook

      PHASE 1

      Define and Prioritize Infrastructure Services

      Step 1.1: Define the services you own

      PHASE 1

      Define and prioritize infrastructure services

      1.1

      Define the services you own

      1.2

      Prioritize infrastructure services

      This step will walk you through the following activities:

      • Define “infrastructure service”
      • Brainstorm service offerings
      • Consolidate services with affinity map

      This step involves the following participants:

      • Infrastructure Manager
      • I&O SMEs

      Results & Insights

      • Results: Consolidated list of end-to-end services
      • Insights: Avoid analysis paralysis by brainstorming without restrictions. It is more effective to cut down in Step 1.2 rather than risk neglecting important services for the playbook.

      Consider a range of infrastructure services

      Your infrastructure team is a service provider to the applications team – and sometimes other users as well.

      Service Requests
      • A developer requests a new web server.
      • The marketing department asks for a database to support a six-month digital marketing campaign.
      Projects
      • A new service is promoted to production.
      Operations
      • Firewall rules are updated to support server, network, or security posture changes.
      • Standard practices are followed and maintained to harden a range of different operating systems.
      • Engineers follow a standard process to integrate new tools and entitlements into Active Directory.
      • Patches and firmware updates are applied to core infrastructure components as needed.
      Problems
      • A database batch job often breaks on overnight batch jobs and requires manual intervention to check and restart.
      A visualization of the word 'Infrastructure Services' being orbited by 'Service Requests', 'Projects', 'Operations', and 'Problems'.

      IT infrastructure & operations teams deliver services that fulfil requests, support projects, resolve problems, and operate systems.