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

z-Series Modernization and Migration

  • Buy Link or Shortcode: {j2store}114|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

Under the best of circumstances, mainframe systems are complex, expensive, and difficult to scale. In today’s world, applications written for mainframe legacy systems also present significant operational challenges to customers compounded by the dwindling pool of engineers who specialize in these outdated technologies. Many organizations want to migrate their legacy applications to the cloud but to do so they need to go through a lengthy migration process that is made more challenging by the complexity of mainframe applications.

Our Advice

Critical Insight

The most common tactic is for the organization to better realize their z/Series options and adopt a strategy built on complexity and workload understanding. To make the evident, obvious, the options here for the non-commodity are not as broad as with commodity server platforms and the mainframe is arguably the most widely used and complex non-commodity platform on the market.

Impact and Result

This research will help you:

  • Evaluate the future viability of this platform.
  • Assess the fit and purpose, and determine TCO
  • Develop strategies for overcoming potential challenges.
  • Determine the future of this platform for your organization.

z/Series Modernization and Migration Research & Tools

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

1. z/Series Modernization and Migration Guide – A brief deck that outlines key migration options and considerations for the z/Series platform.

This blueprint will help you assess the fit, purpose, and price; develop strategies for overcoming potential challenges; and determine the future of z/Series for your organization.

  • z/Series Modernization and Migration Storyboard

2. Scale Up vs. Scale Out TCO Tool – A tool that provides organizations with a framework for TCO.

Use this tool to play with the pre-populated values or insert your own amounts to compare possible database decisions, and determine the TCO of each. Note that common assumptions can often be false; for example, open-source Cassandra running on many inexpensive commodity servers can actually have a higher TCO over six years than a Cassandra environment running on a larger single expensive piece of hardware. Therefore, calculating TCO is an essential part of the database decision process.

  • Scale Up vs. Scale Out TCO Tool
[infographic]

Further reading

z/Series Modernization and Migration

The biggest migration is yet to come.

Executive Summary

Info-Tech Insight

“A number of market conditions have coalesced in a way that is increasingly driving existing mainframe customers to consider running their application workloads on alternative platforms. In 2020, the World Economic Forum noted that 42% of core skills required to perform existing jobs are expected to change by 2022, and that more than 1 billion workers need to be reskilled by 2030.” – Dale Vecchio

Your Challenge

It seems like anytime there’s a new CIO who is not from the mainframe world there is immediate pressure to get off this platform. However, just as there is a high financial commitment required to stay on System Z, moving off is risky and potentially more costly. You need to truly understand the scale and complexity ahead of the organization.

Common Obstacles

Under the best of circumstances, mainframe systems are complex, expensive, and difficult to scale. In today’s world, applications written for mainframe legacy systems also present significant operational challenges to customers compounded by the dwindling pool of engineers who specialize in these outdated technologies. Many organizations want to migrate their legacy applications to the cloud, but to do so they need to go through a lengthy migration process that is made more challenging by the complexity of mainframe applications.

Info-Tech Approach

The most common tactic is for the organization to better realize its z/Series options and adopt a strategy built on complexity and workload understanding. To make the evident, obvious: the options here for the non-commodity are not as broad as with commodity server platforms and the mainframe is arguably the most widely used and complex non-commodity platform on the market.

Review

We help IT leaders make the most of their z/Series environment

Problem statement:

The z/Series 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 and aging 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 z/Series 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 and purpose, and determine TCO.
  3. Develop strategies for overcoming potential challenges.
  4. Determine the future of this platform for your organization.

Analyst Perspective

Good Luck.

Darin Stahl.

Modernize the mainframe … here we go again.

Prior to 2020, most organizations were muddling around in “year eleven of the four-year plan” to exit the mainframe platform where a medium-term commitment to the platform existed. Since 2020, it appears the appetite for the mainframe platform changed. Again. Discussions mostly seem to be about what the options are beyond hardware outsourcing or re-platforming to “cloud” migration of workloads – mostly planning and strategy topics. A word of caution: it would appear unwise to stand in front of the exit door for fear of being trampled.

Hardware expirations between now and 2025 are motivating hosting deployments. Others are in migration activities, and some have already decommissioned and migrated but now are trying to rehab the operations team now lacking direction and/or structure.

There is little doubt that modernization and “digital transformation” trends will drive more exit traffic, so IT leaders who are still under pressure to get off the platform need to assess their options and decide. Being in a state of perpetually planning to get off the mainframe handcuffs your ability to invest in the mainframe, address deficiencies, and improve cost-effectiveness.

Darin Stahl
Principal Research Advisor, Infrastructure & Operations Research
Info-Tech Research Group

The mainframe “fidget spinner”

Thinking of modernizing your mainframe can cause you angst so grab a fidget spinner and relax because we have you covered!

External Business Pressures:

  • Digital transformation
  • Modernization programs
  • Compliance and regulations
  • TCO

Internal Considerations:

  • Reinvest
  • Migrate to a new platform
  • Evaluate public and vendor cloud alternatives
  • Hosting versus infrastructure outsourcing

Info-Tech Insight

With multiple control points to be addressed, care must be taken to simplify your options while addressing all concerns to ease operational load.

The analyst call review

“Who has Darin talked with?” – Troy Cheeseman

Dating back to 2011, Darin Stahl has been the primary z/Series subject matter expert within the Infrastructure & Operations Research team. Below represents the percentage of calls, per industry, where z/Series advisory has been provided by Darin*:

37% - State Government

19% - Insurance

11% - Municipality

8% - Federal Government

8% - Financial Services

5% - Higher Education

3% - Retail

3% - Hospitality/Resort

3% - Logistics and Transportation

3% - Utility

Based on the Info-Tech call history, there is a consistent cross section of industry members who not only rely upon the mainframe but are also considering migration options.

Note:

Of course, this only represents industries who are Info-Tech members and who called for advisory services about the mainframe.

There may well be more Info-Tech members with mainframes who have no topic to discuss with us about the mainframe specifically. Why do we mention this?

We caution against suggesting things like, ”somewhat less than 50% of mainframes live in state data centers” or any other extrapolated inference from this data.

Our viewpoint and discussion is based on the cases and the calls that we have taken over the years.

*37+ enterprise calls were reviewed and sampled.

Scale out versus scale up

For most workloads “scale out" (e.g. virtualized cloud or IaaS ) is going to provide obvious and quantifiable benefits.

However, with some workloads (extremely large analytics or batch processing ) a "scale up" approach is more optimal. But the scale up is really limited to very specific workloads. Despite some assumptions, the gains made when moving from scale up to scale out are not linear.

Obviously, when you scale out from a performance perspective you experience a drop in what a single unit of compute can do. Additionally, there will be latency introduced in the form of network overhead, transactions, and replication into operations that were previously done just bypassing object references within a single frame.

Some applications or use cases will have to be architected or written differently (thinking about the high-demand analytic workloads at large scale). Remember the “grid computing” craze that hit us during the early part of this century? It was advantageous for many to distribute work across a grid of computing devices for applications but the advantage gained was contingent on the workload able to be parsed out as work units and then pulled back together through the application.

There can be some interesting and negative consequences for analytics or batch operations in a large scale as mentioned above. Bottom line, as experienced previously with Microfocus mainframe ports to x86, the batch operations simply take much longer to complete.

Big Data Considerations*:

  • Value: Data has no inherent value until it’s used to solve a business problem.
  • Variety: The type of data being produced is increasingly diverse and ranges from email and social media to geo-spatial and photographic data. This data may be difficult to process using a structured data model.
  • Volume: The sheer size of the datasets is growing exponentially, often ranging from terabytes to petabytes. This is complicating traditional data management strategies.
  • Velocity: The increasing speed at which data is being collected and processed is also causing complications. Big data is often time sensitive and needs to be captured in real time as it is streaming into the enterprise.

*Build a Strategy for Big Data Platforms

Consider your resourcing

Below is a summary of concerns regarding core mainframe skills:

  1. System Management (System Programmers): This is the most critical and hard-to-replace skill since it requires in-depth low-level knowledge of the mainframe (e.g. at the MVS level). These are skills that are generally not taught anymore, so there is a limited pool of experienced system programmers.
  2. Information Management System (IMS) Specialists: Requires a combination of mainframe knowledge and data analysis skills, which makes this a rare skill set. This is becoming more critical as business intelligence takes on an ever-increasing focus in most organizations.
  3. Application Development: The primary concern here is a shortage of developers skilled in older languages such as COBOL. It should be noted that this is an application issue; for example, this is not solved by migrating off mainframes.
  4. Mainframe Operators: This is an easier skill set to learn, and there are several courses and training programs available. An IT person new to mainframes could learn this position in about six weeks of on-the-job training.
  5. DB2 Administration: Advances in database technology have simplified administration (not just for DB2 but also other database products). As a result, as with mainframe operators, this is a skill set that can be learned in a short period of time on the job.

The Challenge

An aging workforce, specialized skills, and high salary expectations

  • Mainframe specialists, such as system programmers and IMS specialists, are typically over 50, have a unique skill set, and are tasked with running mission-critical systems.

The In-House Solution:

Build your mentorship program to create a viable succession plan

  • Get your money’s worth out of your experienced staff by having them train others.
  • Operator skills take about six weeks to learn. However, it takes about two years before a system programmer trainee can become fully independent. This is similar to the learning curve for other platforms; however, this is a more critical issue for mainframes since organizations have far fewer mainframe specialists to fall back on when senior staff retire or move on.

Understand your options

Migrate to another platform

Use a hosting provider

Outsource

Re-platform (cloud/vendors)

Reinvest

There are several challenges to overcome in a migration project, from finding an appropriate alternative platform to rewriting legacy code. Many organizations have incurred huge costs in the attempt, only to be unsuccessful in the end, so make this decision carefully.

Organizations often have highly sensitive data on their mainframes (e.g. financial data), so many of these organizations are reluctant to have this data live outside of their four walls. However, the convenience of using a hosting provider makes this an attractive option to consider.

The most common tactic is for the organization to adopt some level of outsourcing for the non-commodity platform, retaining the application support/development in-house.

A customer can “re-platform” the non-commodity workload into public cloud offerings or in a few offerings
“re-host.”

If you’re staying with the mainframe and keeping it in-house, it’s important to continue to invest in this platform, keep it current, and look for opportunities to optimize its value.

Migrate

Having perpetual plans to migrate handcuffs your ability to invest in your mainframe, extend its value, and improve cost effectiveness.

If this sounds like your organization, it’s time to do the analysis so you can decide and get clarity on the future of the mainframe in your organization.

  1. Identify current performance, availability, and security requirements. Assess alternatives based on this criteria.
  2. Review and use Info-Tech’s Mainframe TCO Comparison Tool to compare mainframe costs to the potential alternative platform.
  3. Assess the business risks and benefits. Can the alternative deliver the same performance, reliability, and security? If not, what are the risks? What do you gain by migrating?
  4. If migration is still a go, evaluate the following:
  • Do you have the expertise or a reliable third party to perform the migration, including code rewrites?
  • How long will the migration take? Can the business function effectively during this transition period?
  • How much will the migration cost? Is the value you expect to gain worth the expense?

*3 of the top 4 challenges related to shortfalls of alternative platforms

The image contains a bar graph that demonstrates challenges related to shortfalls of alternative platforms.

*Source: Maximize the Value of IBM Mainframes in My Business

Hosting

Using a hosting provider is typically more cost-effective than running your mainframe in-house.

Potential for reduced costs

  • Hosting enables you to reduce or eliminate your mainframe staff.
  • Economies of scale enable hosting providers to reduce software licensing costs. They also have more buying power to negotiate better terms.
  • Power and cooling costs are also transferred to the hosting provider.

Reliable infrastructure and experienced staff

  • A quality hosting provider will have 24/7 monitoring, full redundancy, and proven disaster recovery capabilities.
  • The hosting provider will also have a larger mainframe staff, so they don’t have the same risk of suddenly being without those advanced critical skills.

So, what are the risks?

  • A transition to a hosting provider usually means eliminating or significantly reducing your in-house mainframe staff. With that loss of in-house expertise, it will be next to impossible to bring the mainframe back in-house, and you become highly dependent on your hosting provider.

Outsourcing

The most common tactic is for the organization to adopt some level of outsourcing for the non-commodity platform, retaining the application support/development in-house.

The options here for the non-commodity (z/Series, IBM Power platforms, for example) are not as broad as with commodity server platforms. More confusingly, the term “outsourcing” for these can include:

Traditional/Colocation – A customer transitions their hardware environment to a provider’s data center. The provider can then manage the hardware and “system.”

Onsite Outsourcing – Here a provider will support 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.

Managed Hosting – A customer transitions their legacy application environment to an off-prem hosted multi-tenanted environment. It will provide the most cost savings following the transition, stabilization, and disposal of existing environment. Some providers will provide software licensing, and some will also support “Bring Your Own,” as permitted by IBM terms for example.

Info-Tech Insight

Technical debt for non-commodity platforms isn’t only hardware based. Moving an application written for the mainframe onto a “cheaper” hardware platform (or outsourced deployment) leaves the more critical problems and frequently introduces a raft of new ones.

Re-platform – z/Series COBOL Cloud

Re-platforming is not trivial.

While the majority of the coded functionality (JCLs, programs, etc.) migrate easily, there will be a need to re-code or re-write objects – especially if any object, code, or location references are not exactly the same in the new environment.

Micro Focus has solid experience in this but if consider it within the context of an 80/20 rule (the actual metrics might be much better than that), meaning that some level of rework would have to be accomplished as an overhead to the exercise.

Build that thought into your thinking and business case.

AWS Cloud

  • Astadia (an AWS Partner) is re-platforming mainframe workloads to AWS. With its approach you reuse the original application source code and data to AWS services. Consider reviewing Amazon’s “Migrating a Mainframe to AWS in 5 Steps.”

Azure Cloud

Micro Focus COBOL (Visual COBOL)

  • Micro Focus' Visual COBOL also supports running COBOL in Docker containers and managing and orchestrating the containers with Kubernetes. I personally cannot imagine what sort of drunken bender decision would lead me to move COBOL into Docker and then use Kubernetes to run in GCP but there you are...if that's your Jam you can do it.

Re-platform – z/Series (Non-COBOL)

But what if it's not COBOL?

Yeah, a complication for this situation is the legacy code.

While re-platforming/re-hosting non-COBOL code is not new, we have not had many member observations compared to the re-platforming/re-hosting of COBOL functionality initiatives.

That being said, there are a couple of interesting opportunities to explore.

NTT Data Services (GLOBAL)

  • Most intriguing is the re-hosting of a mainframe environment into AWS. Not sure if the AWS target supports NATURAL codebase; it does reference Adabas however (Re-Hosting Mainframe Applications to AWS with NTT DATA Services). Nevertheless, NTT has supported re-platforming and NATURAL codebase environments previously.

ModernSystems (or ModSys) has relevant experience.

  • ModSys is the resulting entity following a merger between BluePhoenix and ATERAS a number of years ago. ATERAS is the entity I find references to within my “wayback machine” for member discussions. There are also a number of published case studies still searchable about ATERAS’ successful re-platforming engagements, including the California Public Employees Retirement System (CalPERS) most famously after the Accenture project to rewrite it failed.

ATOS, as a hosting vendor mostly referenced by customers with global locations in a short-term transition posture, could be an option.

Lastly, the other Managed Services vendors with NATURAL and Adabas capabilities:

Reinvest

By contrast, reducing the use of your mainframe makes it less cost-effective and more challenging to retain in-house expertise.

  • For organizations that have migrated applications off the mainframe (at least partly to reduce dependency on the platform), inevitably there remains a core set of mission critical applications that cannot be moved off for reasons described on the “Migrate” slide. This is when the mainframe becomes a costly burden:
    • TCO is relatively high due to low utilization.
    • In-house expertise declines as workload declines and current staffing allocations become harder to justify.
  • Organizations that are instead adding capacity and finding new ways to use this platform have lower cost concerns and resourcing challenges. The charts below illustrate this correlation. While some capacity growth is due to normal business growth, some is also due to new workloads, and it reflects an ongoing commitment to the platform.

*92% of organizations that added capacity said TCO is lower than for commodity servers (compared to 50% of those who did not add capacity)

*63% of organizations that added capacity said finding resources is not very difficult (compared to 42% of those who did not add capacity)

The image contains a bar graph as described in the above text. The image contains a bar graph as described in the above text.

*Maximize the Value of IBM Mainframes in My Business

An important thought about data migration

Mainframe data migrations – “VSAM, IMS, etc.”

  • While the application will be replaced and re-platformed, there is the historical VIN data remaining in the VSAM files and access via the application. The challenge is that a bulk conversion can add upfront costs and delay the re-platforming of the application functionality. Some shops will break the historical data migration into a couple of phases.
  • While there are technical solutions to accessing VSAM data stores, what I have observed with other members facing a similar scenario is a need to “shrink” the data store over time. The technical accesses to historical VSAM records would also have a lifespan, and rather than kicking the can down the road indefinitely, many have turned to a process-based solution allowing them to shrink the historical data store over time. I have observed three approaches to the handling or digitization of historical records like this:

Temporary workaround. This would align with a technical solution allowing the VASM files to be accessed using platforms other than on mainframe hardware (Micro Focus or other file store trickery). This can be accomplished relatively quickly but does run the risk of technology obsolesce for the workaround at some point in the future.

Bulk conversion. This method would involve the extract/transform/load of the historical records into the new application platform. Often the order of the conversion is completed on work newest to oldest (the idea is that the newest historical records would have the highest likelihood of an access need), but all files would be converted to the new application and the old data store destroyed.

Forward convert, which would have files undergo the extract/transform/load conversion into the new application as they are accessed or reopened. This method would keep historical records indefinitely or until they are converted – or the legal retention schedule allows for their destruction (hopefully no file must be kept forever). This could be a cost-efficient approach since the historical files remaining on the VSAM platform would be shrunk over time based on demand from the district attorney process. The conversion process could be automated and scripted, with a QR step allowing for the records to be deleted from the old platform.

Info-Tech Insight

It is not usual for organizations to leverage options #2 and #3 above to move the functionality forward while containing the scope creep and costs for the data conversions.

Enterprise class job scheduling

Job scheduling or data center automation?

  • Enterprise class job scheduling solutions enable complex unattended batched programmatically conditioned task/job scheduling.
  • Data center automation (DCIM) software automates and orchestrates the processes and workflow for infrastructure operations including provisioning, configuring, patching of physical, virtual, and cloud servers, and monitoring of tasks involved in maintaining the operations of a data center or Infrastructure environment.
  • While there maybe some overlap and or confusion between data center automation and enterprise class job scheduling solutions, data center automation (DCIM) software solutions are least likely to have support for non-commodity server platforms and lack robust scheduling functionality.

Note: Enterprise job scheduling is a topic with low member interest or demand. Since our published research is driven by members’ interest and needs, the lack of activity or member demand would obviously be a significant influence into our ability to aggregate shared member insight, trends, or best practices in our published agenda.

Data Center Automation (DCIM) Software

Orchestration/Provisioning Software

Enterprise class job scheduling 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. At a minimum, the solutions offered by the vendors in the list below will have the following capabilities:

  • Automatic restart and recovery
  • File management
  • Integration with security systems such as AD
  • Operator alerts
  • Ability to control spooling devices
  • Cross-platform support
  • Cyclical scheduling
  • Deadline scheduling
  • Event-based scheduling / triggers
  • Inter-dependent jobs
  • External task monitoring (e.g. under other sub-systems)
  • Multiple calendars and time-zones
  • Scheduling of packaged applications (such as SAP, Oracle, JD Edwards)
  • The ability to schedule web applications (e.g. .net, java-based)
  • Workload analysis
  • Conditional dependencies
  • Critical process monitoring
  • Event-based automation (“self-healing” processes in response to common defined error conditions)
  • Graphical job stream/workflow visualization
  • Alerts (job failure notifications, task thresholds (too long, too quickly, missed windows, too short, etc.) via multiple channels
  • API’s supporting programmable scheduler needs
  • Virtualization support
  • Workload forecasting and workload planning
  • Logging and message data supporting auditing capabilities likely to be informed by or compliant with regulatory needs such as Sarbanes, Gramme-Leach
  • Historical reporting
  • Auditing reports and summaries

Understand your vendors and tools

List and compare the job scheduling features of each vendor.

  • This is not presented as an exhaustive list.
  • The list relies on observations aggregated from analyst engagements with Info-Tech Research Group members. Those member discussions tend to be heavily tilted toward solutions supporting non-commodity platforms.
  • Nothing is implied about a solution suitability or capability by the order of presentation or inclusion or absence in this list.

✓ Advanced Systems Concepts

✓ BMC

✓ Broadcom

✓ HCL

✓ Fortra

✓ Redwood

✓ SMA Technologies

✓ StoneBranch

✓ Tidal Software

✓ Vinzant Software

Info-Tech Insight

Creating vendor profiles will help quickly filter the solution providers that directly meet your z/Series needs.

Advanced Systems Concepts

ActiveBatch

Workload Management:

Summary

Founded in 1981, ASCs ActiveBatch “provides a central automation hub for scheduling and monitoring so that business-critical systems, like CRM, ERP, Big Data, BI, ETL tools, work order management, project management, and consulting systems, work together seamlessly with minimal human intervention.”*

URL

advsyscon.com

Coverage:

Global

Amazon EC2

Hadoop Ecosystem

IBM Cognos

DataStage

IBM PureData (Netezza)

Informatica Cloud

Microsoft Azure

Microsoft Dynamics AX

Microsoft SharePoint

Microsoft Team Foundation Server

Oracle EBS

Oracle PeopleSoft

SAP

BusinessObjects

ServiceNow

Teradata

VMware

Windows

Linux

Unix

IBM i

*Advanced Systems Concepts, Inc.


BMC

Control-M

Workload Management:

Summary

Founded in 1980, BMCs Control-M product “simplifies application and data workflow orchestration on premises or as a service. It makes it easy to build, define, schedule, manage, and monitor production workflows, ensuring visibility, reliability, and improving SLAs.”*

URL

bmc.com/it-solutions/control-m.html

Coverage:

Global

AWS

Azure

Google Cloud Platform

Cognos

IBM InfoSphere

DataStage

SAP HANA

Oracle EBS

Oracle PeopleSoft

BusinessObjects

ServiceNow

Teradata

VMware

Windows

Linux

Unix

IBM i

IBM z/OS

zLinux

*BMC

Broadcom

Atomic Automation

Autosys Workload Automation

Workload Management:

Summary

Broadcom offers Atomic Automation and Autosys Workload Automation which ”gives you the agility, speed and reliability required for effective digital business automation. From a single unified platform, Atomic centrally provides the orchestration and automation capabilities needed accelerate your digital transformation and support the growth of your company.”*

URL

broadcom.com/products/software/automation/automic-automation

broadcom.com/products/software/automation/autosys

Coverage:

Global


Windows

MacOS

Linux

UNIX

AWS

Azure

Google Cloud Platform

VMware

z/OS

zLinux

System i

OpenVMS

Banner

Ecometry

Hadoop

Oracle EBS

Oracle PeopleSoft

SAP

BusinessObjects

ServiceNow

Teradata

VMware

Windows

Linux

Unix

IBM i

*Broadcom

HCL

Workload Automation

Workload Management:

Summary

“HCL Workload Automation streamlined modelling, advanced AI and open integration for observability. Accelerate the digital transformation of modern enterprises, ensuring business agility and resilience with our latest version of one stop automation platform. Orchestrate unattended and event-driven tasks for IT and business processes from legacy to cloud and kubernetes systems.”*

URL

hcltechsw.com/workload-automation

Coverage:

Global


Windows

MacOS

Linux

UNIX

AWS

Azure

Google Cloud Platform

VMware

z/OS

zLinux

System i

OpenVMS

IBM SoftLayer

IBM BigInsights

IBM Cognos

Hadoop

Microsoft Dynamics 365

Microsoft Dynamics AX

Microsoft SQL Server

Oracle E-Business Suite

PeopleSoft

SAP

ServiceNow

Apache Oozie

Informatica PowerCenter

IBM InfoSphere DataStage

Salesforce

BusinessObjects BI

IBM Sterling Connect:Direct

IBM WebSphere MQ

IBM Cloudant

Apache Spark

*HCL Software

Fortra

JAMS Scheduler

Workload Management:

Summary

Fortra’s “JAMS is a centralized workload automation and job scheduling solution that runs, monitors, and manages jobs and workflows that support critical business processes.

JAMS reliably orchestrates the critical IT processes that run your business. Our comprehensive workload automation and job scheduling solution provides a single pane of glass to manage, execute, and monitor jobs—regardless of platforms or applications.”*

URL

jamsscheduler.com

Coverage:

Global


OpenVMS

OS/400

Unix

Windows

z/OS

SAP

Oracle

Microsoft

Infor

Workday

AWS

Azure

Google Cloud Compute

ServiceNow

Salesforce

Micro Focus

Microsoft Dynamics 365

Microsoft Dynamics AX

Microsoft SQL Server

MySQL

NeoBatch

Netezza

Oracle PL/SQL

Oracle E-Business Suite

PeopleSoft

SAP

SAS

Symitar

*JAMS

Redwood

Redwood SaaS

Workload Management:

Summary

Founded in 1993 and delivered as a SaaS solution, ”Redwood lets you orchestrate securely and reliably across any application, service or server, in the cloud or on-premises, all inside a single platform. Automation solutions are at the core of critical business operations such as forecasting, replenishment, reconciliation, financial close, order to cash, billing, reporting, and more. Enterprises in every industry — from manufacturing, utility, retail, and biotech to healthcare, banking, and aerospace.”*

URL

redwood.com

Coverage:

Global


OpenVMS

OS/400

Unix

Windows

z/OS

SAP

Oracle

Microsoft

Infor

Workday

AWS

Azure

Google Cloud Compute

ServiceNow

Salesforce

Github

Office 365

Slack

Dropbox

Tableau

Informatica

SAP BusinessObjects

Cognos

Microsoft Power BI

Amazon QuickSight

VMware

Xen

Kubernetes

*Redwood

Fortra

Robot Scheduler

Workload Management:

Summary

“Robot Schedule’s workload automation capabilities allow users to automate everything from simple jobs to complex, event-driven processes on multiple platforms and centralize management from your most reliable system: IBM i. Just create a calendar of when and how jobs should run, and the software will do the rest.”*

URL

fortra.com/products/job-scheduling-software-ibm-i

Coverage:

Global


IBM i (System i, iSeries, AS/400)

AIX/UNIX

Linux

Windows

SQL/Server

Domino

JD Edwards EnterpriseOne

SAP

Automate Schedule (formerly Skybot Scheduler)

*Fortra

SMA Technologies

OpCon

Workload Management:

Summary

Founded in1980, SMA offers to “save time, reduce error, and free your IT staff to work on more strategic contributions with OpCon from SMA Technologies. OpCon offers powerful, easy-to-use workload automation and orchestration to eliminate manual tasks and manage workloads across business-critical operations. It's the perfect fit for financial institutions, insurance companies, and other transactional businesses.”*

URL

smatechnologies.com

Coverage:

Global

Windows

Linux

Unix

z/Series

IBM i

Unisys

Oracle

SAP

Microsoft Dynamics AX

Infor M3

Sage

Cegid

Temenos

FICS

Microsoft Azure Data Management

Microsoft Azure VM

Amazon EC2/AWS

Web Services RESTful

Docker

Google Cloud

VMware

ServiceNow

Commvault

Microsoft WSUS

Microsoft Orchestrator

Java

JBoss

Asysco AMT

Tuxedo ART

Nutanix

Corelation

Symitar

Fiserv DNA

Fiserv XP2

*SMA Technologies

StoneBranch

Universal Automation Center (UAC)

Workload Management:

Summary

Founded in 1999, ”the Stonebranch Universal Automation Center (UAC) is an enterprise-grade business automation solution that goes beyond traditional job scheduling. UAC's event-based workload automation solution is designed to automate and orchestrate system jobs and tasks across all mainframe, on-prem, and hybrid IT environments. IT operations teams gain complete visibility and advanced control with a single web-based controller, while removing the need to run individual job schedulers across platforms.”*

URL

stonebranch.com/it-automation-solutions/enterprise-job-scheduling

Coverage:

Global

Windows

Linux

Unix

z/Series

Apache Kafka

AWS

Databricks

Docker

GitHub

Google Cloud

Informatica

Jenkins

Jscape

Kubernetes

Microsoft Azure

Microsoft SQL

Microsoft Teams

PagerDuty

PeopleSoft

Petnaho

RedHat Ansible

Salesforce

SAP

ServiceNow

Slack

SMTP and IMAP

Snowflake

Tableau

VMware

*Stonebranch

Tidal Software

Workload Automation

Workload Management:

Summary

Founded in 1979, Tidal’s Workload Automation will “simplify management and execution of end-to-end business processes with our unified automation platform. Orchestrate workflows whether they're running on-prem, in the cloud or hybrid environments.”*

URL

tidalsoftware.com

Coverage:

Global

CentOS

Linux

Microsoft Windows Server

Open VMS

Oracle Cloud

Oracle Enterprise Linux

Red Hat Enterprise Server

Suse Enterprise

Tandem NSK

Ubuntu

UNIX

HPUX (PA-RISC, Itanium)

Solaris (Sparc, X86)

AIX, iSeries

z/Linux

z/OS

Amazon AWS

Microsoft Azure

Oracle OCI

Google Cloud

ServiceNow

Kubernetes

VMware

Cisco UCS

SAP R/3 & SAP S/4HANA

Oracle E-Business

Oracle ERP Cloud

PeopleSoft

JD Edwards

Hadoop

Oracle DB

Microsoft SQL

SAP BusinessObjects

IBM Cognos

FTP/FTPS/SFTP

Informatica

*Tidal

Vinzant Software

Global ECS

Workload Management:

Summary

Founded in 1987, Global ECS can “simplify operations in all areas of production with the GECS automation framework. Use a single solution to schedule, coordinate and monitor file transfers, database operations, scripts, web services, executables and SAP jobs. Maximize efficiency for all operations across multiple business units intelligently and automatically.”*

URL

vinzantsoftware.com

Coverage:

Global

Windows

Linux

Unix

iSeries

SAP R/3 & SAP S/4HANA

Oracle, SQL/Server

*Vizant Software

Activity

Scale Out or Scale Up

Activities:

  1. Complete the Scale Up vs. Scale Out TCO Tool.
  2. Compare total lifecycle costs to determine TCO.

This activity involves the following participants:

IT strategic direction decision makers

IT managers responsible for an existing z/Series platform

Organizations evaluating platforms for mission critical applications

Outcomes of this step:

  • Completed Scale Up vs. Scale Out TCO Tool

Info-Tech Insight

This checkpoint 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.

Scale out versus scale up activity

The Scale Up vs. Scale Out TCO Tool provides organizations with a framework for estimating the costs associated with purchasing and licensing for a scale-up and scale-out environment over a multi-year period.

Use this tool to:

  • Compare the pre-populated values.
  • Insert your own amounts to contrast possible database decisions and determine the TCO of each.
The image contains screenshots of the Scale Up vs. Scale Out TCO Tool.

Info-Tech Insight

Watch out for inaccurate financial information. Ensure that the financials for cost match your maintenance and contract terms.

Use the Scale Up vs. Scale Out TCO Tool to determine your TCO options.

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.

Build a Strategy for Big Data Platforms

Know where to start and where to focus attention in the implementation of a big data strategy.

Create a Better RFP Process

Improve your RFPs to gain leverage and get better results.

Research Authors

Darin Stahl.

Darin Stahl, Principal Research Advisor, Info-Tech Research Group

Darin is a 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, non-commodity servers (z/Series, mainframe, IBM i, AIX, Power PC).

Troy Cheeseman.

Troy Cheeseman, Practice Lead, Info-Tech Research Group

Troy has over 25 years of IT management 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.

Bibliography

“AWS Announces AWS Mainframe Modernization.” Business Wire, 30 Nov. 2021.
de Valence, Phil. “Migrating a Mainframe to AWS in 5 Steps with Astadia?” AWS, 23 Mar. 2018.
Graham, Nyela. “New study shows mainframes still popular despite the rise of cloud—though times are changing…fast?” WatersTechnology, 12 Sept. 2022.
“Legacy applications can be revitalized with API.” MuleSoft, 2022.
Vecchio, Dale. “The Benefits of Running Mainframe Applications on LzLabs Software Defined Mainframe® & Microsoft Azure.” LzLabs Sites, Mar. 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)

    Do you believe in absolute efficiency?

    Weekend read. Hence I post this a bit later on Friday.
    Lately, I've been fascinated by infinity. And in infinity, some weird algebra pops up. Yet that weirdness is very much akin to what our business stakeholders want, driven by what our clients demand, and hence our KPIs drive us. Do more with less. And that is what absolute efficiency means.

    Register to read more …

    Map Technical Skills for a Changing Infrastructure & Operations Organization

    • Buy Link or Shortcode: {j2store}333|cart{/j2store}
    • member rating overall impact: 10.0/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: Strategy and Organizational Design
    • Parent Category Link: /strategy-and-organizational-design
    • Infrastructure & Operations is changing rapidly. It’s a constant challenge to find the right skills to support the next new technology while at the same time maintaining the skills in house that allow you to support your existing platforms.
    • A lack of clarity around required skills makes finding the right skills difficult, and it’s not clear whether you should train, hire, contract, or outsource to address gaps.
    • You need to keep up with changes and new strategy while continuing to support your existing environment.

    Our Advice

    Critical Insight

    • Take a strategic approach to acquiring skills – looking only as far as the needs of the next project will lead to a constant skills shortage with no plan for it to be addressed.
    • Begin by identifying your future state. Identify needed skills in the organization to support planned projects and initiatives, and to mitigate skills-related risks.

    Impact and Result

    • Leverage your infrastructure roadmap and cloud strategy to identify needed skills in your future state environment.
    • Decide how you’ll acquire needed skills based on the characteristics of need for each skill.
    • Communicate the change and create a plan of action for the skills transformation.

    Map Technical Skills for a Changing Infrastructure & Operations Organization Research & Tools

    Start here – read the Executive Brief

    Read our concise Executive Brief to find out why you should map technical skills for a changing Infrastructure & Operations 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. Identify skills needs for the future state environment

    Identify what skills are needed based on where the organization is going.

    • Map Technical Skills for a Changing Infrastructure & Operations Organization – Phase 1: Identify Skills Needs for Your Future State Environment
    • Future State Playbook
    • IT/Cloud Solutions Architect
    • IT/Cloud Engineer
    • IT/Cloud Administrator
    • IT/Cloud Demand Billing & Accounting Analyst

    2. Acquire needed skills

    Ground skills acquisition decisions in the characteristics of need.

    • Map Technical Skills for a Changing Infrastructure & Operations Organization – Phase 2: Acquire Needed Skills
    • Technical Skills Map

    3. Maximize the value of the skills map

    Get stakeholder buy-in; leverage the skills map in other processes.

    • Map Technical Skills for a Changing Infrastructure & Operations Organization – Phase 3: Maximize the Value of Your Skills Map
    • Technical Skills Map Communication Deck Template
    [infographic]

    Workshop: Map Technical Skills for a Changing Infrastructure & Operations 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 Review Initiatives and Skills-Related Risks

    The Purpose

    Identify process and skills changes required by the future state of your environment.

    Key Benefits Achieved

    Set foundation for alignment between strategy-defined technology initiatives and needed skills.

    Activities

    1.1 Review the list of initiatives and projects with the group.

    1.2 Identify how key support, operational, and deployment processes will change through planned initiatives.

    1.3 Identify skills-related risks and pain points.

    Outputs

    Future State Playbook

    2 Identify Needed Skills and Roles

    The Purpose

    Identify process and skills changes required by the future state of your environment.

    Key Benefits Achieved

    Set foundation for alignment between strategy-defined technology initiatives and needed skills.

    Activities

    2.1 Identify skills required to support the new environment.

    2.2 Map required skills to roles.

    Outputs

    IT/Cloud Architect Role Description

    IT/Cloud Engineer Role Description

    IT/Cloud Administrator Role Description

    3 Create a Plan to Acquire Needed Skills

    The Purpose

    Create a skills acquisition strategy based on the characteristics of need.

    Key Benefits Achieved

    Optimal skills acquisition strategy defined.

    Activities

    3.1 Modify impact scoring scale for key skills decision factors.

    3.2 Apply impact scoring scales to needed skills

    3.3 Decide whether to train, hire, contract, or outsource to acquire needed skills.

    Outputs

    Technical Skills Map

    4 Develop a Communication Plan

    The Purpose

    Create an effective communication plan for different stakeholders across the organization.

    Identify opportunities to leverage the skills map elsewhere.

    Key Benefits Achieved

    Create a concise, clear, consistent, and relevant change message for stakeholders across the organization.

    Activities

    4.1 Review skills decisions and decide how you will acquire skills in each role.

    4.2 Update roles descriptions.

    4.3 Create a change message.

    4.4 Identify opportunities to leverage the skills map in other processes.

    Outputs

    Technical Skills Map Communication Deck

    Diagnose Brand Health to Improve Business Growth

    • Buy Link or Shortcode: {j2store}564|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
    • Low number and quality of leads generated, poor conversion rates, and declining customer retention and loyalty
    • Higher customer acquisition vs. marketing costs
    • Difficulties attracting and keeping talent, partners, and investors
    • Slow or low growth and devaluation of the brand due to low brand equity

    Our Advice

    Critical Insight

    • The Brand: Intangible, yet a company’s most valuable asset.
    • Data-driven decisions for a strong brand.
    • Investing in brand-building efforts means investing in your success.

    Impact and Result

    • Increase brand awareness and equity.
    • Build trust and improve customer retention and loyalty.
    • Achieve higher and faster growth.

    Diagnose Brand Health to Improve Business Growth Research & Tools

    Diagnose Brand Health to Improve Business Growth Executive Brief – A deck to help diagnose brand health to improve business growth.

    In this executive brief, you will discover the importance of a strong brand on the valuation, growth, and sustainability of your company. You will also learn about SoftwareReviews' approach to assessing current performance and gaining visibility into areas of improvement.

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

    1. Brand Diagnostic and Analysis Tool Kit

    A comprehensive set of tools to gather and interpret qualitative and quantitative brand performance metrics.

    • Brand Diagnostic Tool - Digital Metrics Analysis Template
    • Brand Diagnostic Tool - Financial Metrics Analysis Template
    • Brand Diagnostic Tool Survey and Interview Questionnaires and Lists Template
    • Survey Emails Best Practices Guidelines
    • Brand Diagnostic Tool - External and Internal Factors Metrics Analysis Template

    2. Brand Diagnostic Executive Presentation

    Fully customizable, pre-built PowerPoint presentation template to communicate the results of the brand performance diagnostic, areas of improvement and trends, as well as your recommendations. It will also allow you to identify and align executive members and key stakeholders on next steps, and set priorities.

    • Brand Diagnostic - Executive Presentation Template

    Infographic

    Further reading

    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 it.

    EXECUTIVE BRIEF

    SoftwareReviews is a division of Info-Tech Research Group Inc., a world-class IT research and consulting firm established in 1997.
    Backed by two decades of IT research and advisory experience, SoftwareReviews offers the most comprehensive insight into the enterprise software landscape and client-vendor relationships.

    Analyst Perspective

    Brand Diagnostic and Monitoring

    In the ever-changing market landscape in which businesses operate, it is imperative to ensure that the brand stays top of mind and quickly adapts. Having a good understanding of where the brand stands and how it performs has become crucial for any company to stand out from its competitors and succeed in a crowded and very dynamic market.

    Unfortunately, the brand does not always receive the attention and importance it deserves, leaving it vulnerable to becoming outdated and unclear to the target audience and to losing its equity.

    Knowing how the brand is perceived, as opposed to how individuals within an organization perceive it, addressing any brand-related issues in a timely manner, and implementing processes to continuously monitor its performance have become key tactics for any company that wants to thrive in today's highly competitive market.

    Photo of Nathalie Vezina, Marketing Research Director, SoftwareReviews Advisory.

    Nathalie Vezina
    Marketing Research Director
    SoftwareReviews Advisory

    Executive Summary

    Your Challenge

    Because it is vulnerable to becoming outdated and unclear to the target audience and to losing its equity, it is essential to ensure that the brand is performing well and to be attentive to these signs of a weakened brand:

    • Low number and quality of leads generated, poor conversion rates, and declining customer retention and loyalty
    • Lack of understanding of the value proposition; lack of interest and interaction with the brand
    • Higher customer acquisition/marketing costs
    • Difficulties attracting and keeping talent, partners, or future investors
    • Low/slow growth; devaluation of the brand due to low brand equity
    Common Obstacles

    Building a strong brand is an everyday challenge, and brand leaders often face what may seem like overwhelming obstacles in achieving their goal. Here are some of the roadblocks they regularly face:

    • Limited visibility on brand perception and overall performance
    • Insufficient supporting information to make clear, undisputable data-driven decisions and convince key stakeholders how to improve brand performance
    • Limited resources (time, budget, headcount, tools) to diagnose, measure, and execute
    • Stakeholders may not be fully aware of the benefits of a strong brand and the impacts that a weak brand can have on the overall performance of the business
    SoftwareReviews’ Approach

    This SoftwareReviews blueprint provides the guidance and tools required to perform a thorough brand diagnostic and enable brand leaders to:

    • Know how the brand performs; pinpoint gaps and areas for improvement
    • Make clear, data-driven recommendations and decisions on how to fix and optimize the brand
    • Communicate, convince key stakeholders, and align on proposed solutions to optimize the brand’s performance
    • Continuously monitor and optimize the brand

    SoftwareReviews Advisory Insight

    The brand is a company’s most valuable asset that should never fall into disrepair. In fact, business leaders should ensure that at least half of their marketing budget is allocated to brand-building efforts.

    What is a brand?

    The brand – both intangible and the most valuable asset for businesses.

    Despite its intangible nature, the brand is at the heart of every business, small and large, around which rotates what drives business success and growth.

    While measuring its real value on the marketplace can be difficult, a brand with high salience will attract and retain customers for as long as it keeps evolving and adapting to its dynamic environment.

    Up to 90% of the total market value of companies is based on intangible assets, such as brand recognition. (Source: Ocean Tomo, 2020)

    Multiple bubbles with the biggest bubble highlighted and labelled 'BRAND'. The other bubbles say 'IDENTITY', 'LOYALTY', 'TRUST', 'STRATEGY', 'GROWTH', 'AWARENESS', and 'VALUE'.

    What makes a brand strong?

    Perception Matters

    The brand reflects the image of a company or a product. The values it conveys and how it’s being perceived have a direct impact on a brand's ability to stand out and grow.

    A brand is strong when it:

    • Projects a positive image
    • Has a clear positioning and value proposition
    • Is authentic and inspiring
    • Conveys values that resonates
    • Is socially engaged
    • Builds awareness
    • Is consistent
    • Delivers on its promise
    • Inspires trust
    “In the past, a brand is what a company told you it was. Today, a brand is what people tell each other it is.” (Source: Mark Schaefer, 2019)

    Investing in building a brand, a top priority for businesses

    Company Valuation

    Branding has become a top priority for companies to increase the value of their business in the marketplace. A good market value is essential to attract and retain investors, obtain future rounds of financing, grow by acquisition, and find buyers.

    The more equity a brand gains, the higher its market value, despite the company’s annual revenue. While annual revenue is factored in the equation, the equity of the brand has a greater impact on the market value. A brand whose market value is lower than its revenue is an important indicator that the brand is weakened and needs to be addressed.

    Revenue and Growth

    Most successful companies are investing heavily in building their brand, and for good reason. A strong brand will deliver the right messaging, and a unique and clear value proposition will resonate with its audience and directly impact customer acquisition costs, outperform competition, enable higher pricing, and increase sales volume and customer lifetime value.

    A strong brand also helps develop partner channels, attract and engage high-value partners, and allow for actionable and incremental KPIs.

    Talent Acquisition and Retention

    Brands with strong values are more attractive to highly skilled talent without having to offer above-market salaries. In addition, when a brand inspires pride and shares common values with employees, it increases their motivation and the company’s retention rate.

    Retaining employees within the company allows for the development of talent and retention of knowledge within the organization, thus contributing to the sustainability of the organization.

    It's no wonder that employer branding has become an essential element of human resources strategies.

    “Sustainable Living Brands are growing 69% faster than the rest of the business and delivering 75% of the company’s growth.” (Source: Unilever, 2019, qtd. in Deloitte, 2021)

    Symptoms of a weakened brand

    Know if your brand is suffering and needs to be fixed.

    Brand leaders experiencing one or more of these brand-related symptoms should consider rebranding or optimizing their brand:
    • Low number and quality of leads generated, poor conversion rates, and declining customer retention and loyalty
    • Higher customer acquisition vs. marketing costs
    • Difficulties attracting and keeping talent, partners, and investors
    • Slow or low growth and devaluation of the brand due to low brand equity

    With visibility into your brand and the supporting data that provides a thorough diagnostic of the brand, combined with ongoing brand performance monitoring, you will have all the information you need to help you drive the brand forward, have a significant impact on business growth, and stand out as a brand leader.

    The largest software companies have an average market cap of 18X their revenue (Source: Companies Market Cap, May 2022)

    Building a strong brand, an everyday challenge

    Brand leaders are often faced with overwhelming obstacles in building a strong brand.

    Limited visibility on brand perception and overall performance Insufficient information to make clear, undisputable data-driven decisions and convince key stakeholders how to improve brand performance Stock image of a person pulling a boulder.
    Misunderstanding of the benefits of a strong brand and negative impacts of a weak brand on business valuation and growth Limited resources (time, budget, headcount, tools) to diagnose, measure, and execute
    Only
    54%
    of businesses have a B2B brand program in place for measuring brand perceptions. (Source: B2B International, 2016) Only
    4%
    of B2B marketing teams measure the impact of their marketing/brand building efforts beyond six months. (Source: LinkedIn’s B2B Institute, 2019) 50%
    of marketing budget is what successful brands spend on average on brand-building efforts. (Source: Les Binet and Peter Field, 2018)
    82% of investors say name recognition is an important factor guiding them in their investment decisions. (Source: Global Banking & Finance Review, 2018) 77% of B2B marketers say branding is crucial for growth. (Source: Circle Research)

    Making brand performance visible

    Implement data-driven strategies and make fact-based decisions to continuously optimize brand performance.

    Diagnose your brand’s health
    Know how your brand is being perceived and have visibility on its performance.
    Cycle titled 'BRAND' with steps 'Diagnose', 'Identify', 'Fix', 'Keep Monitoring' and back to 'Diagnose'. Identify trends and areas of improvement
    Rely on undisputable and reliable data to make clear decisions and educate and communicate with key stakeholders.
    Keep monitoring your brand’s performance
    Stay on top of the game and keep away competitors by continuously monitoring your brand’s health.
    Fix issues with your brand in a timely manner
    Don’t lose the momentum. Achieve better results and have a greater impact on your success and chances to grow.

    Qualitative and quantitative brand performance measures

    Segmented by SoftwareReviews Advisory into three categories for a comprehensive diagnostic.

    Icon of a megaphone. Icon of a head with puzzle pieces. Icon of coins.
    Brand Equity
    • Awareness
    • Perception
    • Positioning
    • Recognition/recall
    • Trust
    Buyer’s Behavior
    • Interaction with the brand
    • Preference
    • Purchase intent
    • Product reviews
    • Social engagement
    • Website traffic
    • Lead generation
    Financial
    • Revenue
    • Profit margin
    • Customer lifetime value (CLV)
    • Customer acquisition cost (CAC)
    • Intangible asset market value (IAMV)

    Benefits of a strong and healthy brand

    A healthy brand is the foundation of your success.

    Ensure a better understanding of the value proposition and positioning Drive more interest, interaction, and traction Increase brand awareness and equity Generate higher number and quality of leads
    Achieve higher and faster conversion rate Build trust and improve customer retention and loyalty Attract and keep talent, partners, and investors Achieve higher and faster growth

    Visual explaining the brand diagnostic methodology: 1. data collection and analysis; and 2. presentation and alignment. Outcomes: gain visibility into the brand's performance, highlight areas for improvement, and make data-driven decisions.

    Who benefits from diagnosing the brand?

    This Research Is Designed for:

    Brand leaders who are looking to:

    • Detect and monitor brand performance, issues, trends, and areas of improvement
    • Optimize and fix their brand
    • Develop strategies, and make recommendations and decisions based on facts
    • Get the support they need from key stakeholders
    This Research Will Help You:
    • Get the visibility you need on your brand’s performance
    • Pinpoint brand issues, trends, and areas of improvement
    • Develop data-driven strategies, and make recommendations and decisions based on facts
    • Communicate with and convince key stakeholders
    • Get the support you need from key stakeholders
    • Put in place new diagnostic and monitoring processes to continually improve your brand
    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 Them:
    • Have a better understanding of the importance of a strong brand on business growth and valuation
    • Align on next steps

    SoftwareReviews’ Brand Diagnostic Methodology

    0. Communication & Alignment 1. Data Collection 2. Data Analysis & Interpretation 3. Report & Presentation
    Phase Steps
    1. Engage and unify the team
    2. Communicate and present
    3. Align on next steps
    1. Identify and document internal and external changes affecting the brand
    2. Conduct internal and external brand perception surveys
    3. Gather customer loyalty feedback
    4. Collect digital performance metrics
    1. Analyze data collected
    2. Identify issues, trends, gaps, and inconsistencies
    3. Compare data with current brand statement
    1. Build report with recommendations
    2. Prioritize brand fixes from high to low positive impact
    3. Build presentation
    Phase Outcomes
    • Importance of the brand is recognized
    • Endorsement and prioritization
    • Support and resources
    • All relevant data/information is collected in one place
    • Visibility on the performance of the brand
    • All the data in hand to support recommendations and make informed decisions
    • Visibility and clear understanding of the brand’s health and how to fix or improve its performance

    Insight summary

    The Brand: Intangible, yet a company’s most valuable asset

    Intangible assets, such as brand recognition, account for almost all of a company’s value.1 Despite its intangible nature, the brand is at the heart of every business and has a direct impact on business growth, profitability, and revenue. While measuring its real value on the marketplace can be difficult, a brand with high traction will attract customers and keep them for as long as it keeps evolving and adapting to its dynamic environment.

    Making brand issues visible

    Having a clear understanding of how the brand performs has become crucial for any company that wants to stand out from its competitors and succeed in a crowded and highly dynamic marketplace.

    Data-driven decisions for a strong brand

    Intuition-based or uninformed decisions are obsolete. Brand leaders must base their decisions on facts to be able to convince key stakeholders.

    Building a strong brand, an everyday challenge

    Brand leaders often face overwhelming obstacles building strong brands. They need guidance and tools to support them to drive the business forward.

    Get team buy-in and alignment

    Brand leaders must ensure that the key stakeholders are aware of the importance of a strong brand to business growth and value increase and that they are aligned and committed to the efforts required to build a successful brand.

    Investing in brand-building efforts means investing in your success

    Successful business leaders allocate at least half of their marketing budget2 to brand-building efforts, enabling them to set themselves apart, significantly increase their market share, grow their business, and thrive in a highly competitive marketplace.

    Guided Implementation

    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.

    What does a typical GI on this topic look like?

    Brand Diagnostic

    Data Analysis & Interpretation

    Report & Presentation Building

    Communication & Alignment

    Call #1: Discuss concept and benefits of performing a brand diagnostic. Identify key stakeholders. Anticipate concerns and objections.

    Call #2: Discuss how to use the tool. Identify resources and internal support needed.

    Call #3: Review results. Discuss how to identify brand issues, areas of improvement, and trends based on data collected and to interpret key metrics.

    Call #4 (optional): Continue discussion from call #3.

    Call #5: Discuss recommendations and best practices to fix the issues identified and resources required.

    Call #6: Discuss purpose and how to build the report and presentation, Prioritize the brand fixes from high to low positive impact.

    Call #7 (optional): Follow up with call on report and presentation preparation.

    Call #8: Discuss key points to focus on when presenting to key stakeholders and the desired outcome.

    Call #9: Discuss how to leverage brand diagnostic tools now in place and the benefits of continuously monitoring the brand.

    Call #10: Debrief and determine how we can help with next steps.

    Key deliverable:

    Blueprint deliverables

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

    Brand Diagnostic Presentation Template

    Sample of the key deliverable, the Brand Diagnostic Presentation Template.

    Pre-built and fully customizable PowerPoint template to communicate key findings, areas of improvements, and recommendations to key stakeholders, align on next steps, and prioritize.

    Brand Diagnostic Report Dashboard

    Sample of the Brand Diagnostic Report Dashboard deliverable.

    Auto-filling dashboard built into the Brand Diagnostic Tool Kit. Ready to be saved and shared as a PDF.

    Brand Diagnostic Tool Kit

    Sample of the Brand Diagnostic Tool Kit deliverable.

    Comprehensive Excel Workbook to gather and interpret brand performance metrics. Includes survey questionnaires.

    Bibliography

    “71% of Consumers More Likely to Buy a Product or Service From a Name They Recognise.” Global Banking & Finance Review, 5 December 2018. Web.

    B2B Marketing Leaders Report. Circle Research, n.d. Web.

    Binet, Les, and Peter Field. Effectiveness In Context: A manual for Brand Building. Institute of Practitioners in Advertising, 12 October 2018. Ebook.

    “Current Trends in the World of B2B Marketing, 2016 Survey.” B2B International, 2016. Web.

    Intangible Asset Market Value Study. Ocean Tomo, July 2020. Web.

    Largest Software Companies By Market Cap. Companies Market Cap, May 2022. Web.

    “Unilever, purpose-led brands outperform.” Unilever, 6 October 2019. Web. qtd. in Kounkel, Suzanne, Amy Silverstein, and Kathleen Peeters. “2021 Global Marketing Trends.” Deloitte Insights, 2020. Web.

    Schaefer, Mark. “The Future Of Branding Is Human Impressions.” Mark Schaefer Blog, 3 June 2019. Web.

    The 5 Principles Of Growth In B2B Marketing - Empirical Observations on B2B Effectiveness. LinkedIn B2B Institute, 2019. Web.

    Visual explaining the brand diagnostic methodology: 1. data collection and analysis; and 2. presentation and alignment. Outcomes: gain visibility into the brand's performance, highlight areas for improvement, and make data-driven decisions.

    Who benefits from diagnosing the brand?

    This Research Is Designed for:

    Brand leaders who are looking to:

    • Detect and monitor brand performance, issues, trends, and areas of improvement
    • Optimize and fix their brand
    • Develop strategies, and make recommendations and decisions based on facts
    • Get the support they need from key stakeholders
    This Research Will Help You:
    • Get the visibility you need on your brand’s performance
    • Pinpoint brand issues, trends, and areas of improvement
    • Develop data-driven strategies, and make recommendations and decisions based on facts
    • Communicate with and convince key stakeholders
    • Get the support you need from key stakeholders
    • Put in place new diagnostic and monitoring processes to continually improve your brand
    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 Them:
    • Have a better understanding of the importance of a strong brand on business growth and valuation
    • Align on next steps

    SoftwareReviews’ Brand Diagnostic Methodology

    0. Communication & Alignment 1. Data Collection 2. Data Analysis & Interpretation 3. Report & Presentation
    Phase Steps
    1. Engage and unify the team
    2. Communicate and present
    3. Align on next steps
    1. Identify and document internal and external changes affecting the brand
    2. Conduct internal and external brand perception surveys
    3. Gather customer loyalty feedback
    4. Collect digital performance metrics
    1. Analyze data collected
    2. Identify issues, trends, gaps, and inconsistencies
    3. Compare data with current brand statement
    1. Build report with recommendations
    2. Prioritize brand fixes from high to low positive impact
    3. Build presentation
    Phase Outcomes
    • Importance of the brand is recognized
    • Endorsement and prioritization
    • Support and resources
    • All relevant data/information is collected in one place
    • Visibility on the performance of the brand
    • All the data in hand to support recommendations and make informed decisions
    • Visibility and clear understanding of the brand’s health and how to fix or improve its performance

    Insight summary

    The Brand: Intangible, yet a company’s most valuable asset

    Intangible assets, such as brand recognition, account for almost all of a company’s value.1 Despite its intangible nature, the brand is at the heart of every business and has a direct impact on business growth, profitability, and revenue. While measuring its real value on the marketplace can be difficult, a brand with high traction will attract customers and keep them for as long as it keeps evolving and adapting to its dynamic environment.

    Making brand issues visible

    Having a clear understanding of how the brand performs has become crucial for any company that wants to stand out from its competitors and succeed in a crowded and highly dynamic marketplace.

    Data-driven decisions for a strong brand

    Intuition-based or uninformed decisions are obsolete. Brand leaders must base their decisions on facts to be able to convince key stakeholders.

    Building a strong brand, an everyday challenge

    Brand leaders often face overwhelming obstacles building strong brands. They need guidance and tools to support them to drive the business forward.

    Get team buy-in and alignment

    Brand leaders must ensure that the key stakeholders are aware of the importance of a strong brand to business growth and value increase and that they are aligned and committed to the efforts required to build a successful brand.

    Investing in brand-building efforts means investing in your success

    Successful business leaders allocate at least half of their marketing budget2 to brand-building efforts, enabling them to set themselves apart, significantly increase their market share, grow their business, and thrive in a highly competitive marketplace.

    Guided Implementation

    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.

    What does a typical GI on this topic look like?

    Brand Diagnostic

    Data Analysis & Interpretation

    Report & Presentation Building

    Communication & Alignment

    Call #1: Discuss concept and benefits of performing a brand diagnostic. Identify key stakeholders. Anticipate concerns and objections.

    Call #2: Discuss how to use the tool. Identify resources and internal support needed.

    Call #3: Review results. Discuss how to identify brand issues, areas of improvement, and trends based on data collected and to interpret key metrics.

    Call #4 (optional): Continue discussion from call #3.

    Call #5: Discuss recommendations and best practices to fix the issues identified and resources required.

    Call #6: Discuss purpose and how to build the report and presentation, Prioritize the brand fixes from high to low positive impact.

    Call #7 (optional): Follow up with call on report and presentation preparation.

    Call #8: Discuss key points to focus on when presenting to key stakeholders and the desired outcome.

    Call #9: Discuss how to leverage brand diagnostic tools now in place and the benefits of continuously monitoring the brand.

    Call #10: Debrief and determine how we can help with next steps.

    Key deliverable:

    Blueprint deliverables

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

    Brand Diagnostic Presentation Template

    Sample of the key deliverable, the Brand Diagnostic Presentation Template.

    Pre-built and fully customizable PowerPoint template to communicate key findings, areas of improvements, and recommendations to key stakeholders, align on next steps, and prioritize.

    Brand Diagnostic Report Dashboard

    Sample of the Brand Diagnostic Report Dashboard deliverable.

    Auto-filling dashboard built into the Brand Diagnostic Tool Kit. Ready to be saved and shared as a PDF.

    Brand Diagnostic Tool Kit

    Sample of the Brand Diagnostic Tool Kit deliverable.

    Comprehensive Excel Workbook to gather and interpret brand performance metrics. Includes survey questionnaires.

    Bibliography

    “71% of Consumers More Likely to Buy a Product or Service From a Name They Recognise.” Global Banking & Finance Review, 5 December 2018. Web.

    B2B Marketing Leaders Report. Circle Research, n.d. Web.

    Binet, Les, and Peter Field. Effectiveness In Context: A manual for Brand Building. Institute of Practitioners in Advertising, 12 October 2018. Ebook.

    “Current Trends in the World of B2B Marketing, 2016 Survey.” B2B International, 2016. Web.

    Intangible Asset Market Value Study. Ocean Tomo, July 2020. Web.

    Largest Software Companies By Market Cap. Companies Market Cap, May 2022. Web.

    “Unilever, purpose-led brands outperform.” Unilever, 6 October 2019. Web. qtd. in Kounkel, Suzanne, Amy Silverstein, and Kathleen Peeters. “2021 Global Marketing Trends.” Deloitte Insights, 2020. Web.

    Schaefer, Mark. “The Future Of Branding Is Human Impressions.” Mark Schaefer Blog, 3 June 2019. Web.

    The 5 Principles Of Growth In B2B Marketing - Empirical Observations on B2B Effectiveness. LinkedIn B2B Institute, 2019. Web.

    Mandate Data Valuation Before It’s Mandated

    • Buy Link or Shortcode: {j2store}121|cart{/j2store}
    • member rating overall impact: 8.0/10 Overall Impact
    • member rating average dollars saved: $25,000 Average $ Saved
    • member rating average days saved: 10 Average Days Saved
    • Parent Category Name: Data Management
    • Parent Category Link: /data-management
    • Data can be valuable if used properly or dangerous when mishandled.
    • The organization needs to understand the value of their data before they can establish proper data management practice.
    • Data is not considered a capital asset unless there is a financial transaction (e.g. buying or selling data assets).
    • Data valuation is not easy, and it costs money to collect, store, and maintain data.

    Our Advice

    Critical Insight

    • Data always outlives people, processes, and technology. They all come and go, while data remains.
    • Oil is a limited resource, data is not. Contrary to oil, data is likely to grow over time.
    • Data is likely to outlast all other current popular financial instruments including currency, assets, or commodities.
    • Data is used internally and externally and can easily be replicated or combined.
    • Data is beyond currency, assets, or commodities and needs to be a category of its own.

    Impact and Result

    • Every organization must calculate the value of their data. This will enable organizations to become truly data-driven.
    • Too much time has been spent arguing different methods of valuation. An organization must settle on valuation that is acceptable to all its stakeholders.
    • Align data governance and data management to data valuation. Often organizations struggle to justify data initiatives due to lack of visibility in data valuation.
    • Establish appropriate roles and responsibilities and ensure alignment to a common set of goals as a foundation to get the most accurate future data valuation for your organization.
    • Assess organization data assets and implementation roadmap that considers the necessary competencies and capabilities and their dependencies in moving towards the higher maturity of data assets.

    Mandate Data Valuation Before It’s Mandated Research & Tools

    Start here – read the Executive Brief

    Read our concise Executive Brief to understand the value associated with the organization's data. Review Info-Tech’s methodology for assessing data value and justifying your data initiatives with a value proposition.

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

    1. Demystify data valuation

    Understand the benefits of data valuation.

    • Mandate Data Valuation Before It’s Mandated – Phase 1: Demystify Data Valuation

    2. Data value chain

    Learn about the data value chain framework and preview the step-by-step guide to start collecting data sources.

    • Mandate Data Valuation Before It’s Mandated – Phase 2: Data Value Chain

    3. Data value assessment

    Mature your data valuation by putting in the valuation dimensions and metrics. Establish documented results that can be leveraged to demonstrate value in your data assets.

    • Mandate Data Valuation Before It’s Mandated – Phase 3: Data Value Assessment
    [infographic]

    Workshop: Mandate Data Valuation Before It’s Mandated

    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 Value of Data Valuation

    The Purpose

    Explain data valuation approach and value proposition.

    Key Benefits Achieved

    A clear understanding and case for data valuation.

    Activities

    1.1 Review common business data sources and how the organization will benefit from data valuation assessment.

    1.2 Understand Info-Tech’s data valuation framework.

    Outputs

    Organization data valuation priorities

    2 Capture Organization Data Value Chain

    The Purpose

    Capture data sources and data collection methods.

    Key Benefits Achieved

    A clear understanding of the data value chain.

    Activities

    2.1 Assess data sources and data collection methods.

    2.2 Understand key insights and value proposition.

    2.3 Capture data value chain.

    Outputs

    Data Valuation Tool

    3 Data Valuation Framework

    The Purpose

    Leverage the data valuation framework.

    Key Benefits Achieved

    Capture key data valuation dimensions and align with data value chain.

    Activities

    3.1 Introduce data valuation framework.

    3.2 Discuss key data valuation dimensions.

    3.3 Align data value dimension to data value chain.

    Outputs

    Data Valuation Tool

    4 Plan for Continuous Improvement

    The Purpose

    Improve organization’s data value.

    Key Benefits Achieved

    Continue to improve data value.

    Activities

    4.1 Capture data valuation metrics.

    4.2 Define data valuation for continuous monitoring.

    4.3 Create a communication plan.

    4.4 Define a plan for continuous improvements.

    Outputs

    Data valuation metrics

    Data Valuation Communication Plan

    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.

    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.

      Streamline Application Management

      • Buy Link or Shortcode: {j2store}403|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: $64,272 Average $ Saved
      • member rating average days saved: 40 Average Days Saved
      • Parent Category Name: Maintenance
      • Parent Category Link: /maintenance
      • 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 lack the critical management capabilities to balance maintenance with new development and ensure high product value.
      • Application management is often viewed as a support function rather than an enabler of business growth. Focus and investments are only placed on management when it becomes a problem.
      • The lack of governance and practice accountability leaves application management in a chaotic state: politics take over, resources are not strategically allocated, and customers are frustrated.

      Our Advice

      Critical Insight

      • New features, fixes, and enhancements are all treated the same and managed in a single backlog. Teams need to focus on prioritizing their efforts on what is valuable to the organization, not to a single department.
      • Business integration is not optional. The business (i.e. product owners) must be represented in guiding delivery efforts and performing ongoing validation and verification of new features and changes.

      Impact and Result

      • Justify the necessity to optimize application management. Gain a grounded understanding of stakeholder objectives and validate their achievability against the current maturity of application management.
      • Strengthen backlog management practices. Obtain a holistic picture of the business and technical impacts, risks, value, complexity, and urgency of each backlog item in order to justify its priority and relevance. Apply the appropriate management approach to each software product according to its criticality and value to the business.
      • Establish and govern a repeatable process. Develop a management process with well-defined steps, quality controls, and roles and responsibilities, and instill good practices to improve the success of delivery.

      Streamline Application Management Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should sustain your application management practice, 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 priorities

      State the success criteria of your application management practice through defined objectives and metrics. Assess your maturity.

      • Streamline Application Management – Phase 1: Define Your Priorities
      • Application Management Strategy Template
      • Application Management Maturity Assessment Tool

      2. Govern application management

      Structure your application management governance model with the right process and roles. Inject product ownership into your practice.

      • Streamline Application Management – Phase 2: Govern Application Management

      3. Build your optimization roadmap

      Build your application management optimization roadmap to achieve your target state.

      • Streamline Application Management – Phase 3: Build Your Optimization Roadmap
      [infographic]

      Workshop: Streamline Application 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 Your Priorities

      The Purpose

      State the success criteria of your application management practice through defined objectives and metrics.

      Assess your maturity.

      Key Benefits Achieved

      Grounded stakeholder expectations

      Application management maturity and identification of optimization opportunities

      Activities

      1.1 Set your objectives.

      1.2 Assess your maturity.

      Outputs

      Application management objectives and metrics

      Application management maturity and optimization opportunities

      2 Govern Application Management

      The Purpose

      Structure your application management governance model with the right process and roles.

      Inject product ownership into your practice.

      Key Benefits Achieved

      Management approach aligned to product value and criticality

      Management techniques to govern the product backlog

      Target-state application management process and roles

      Activities

      2.1 Select your management approach.

      2.2 Manage your single product backlog.

      2.3 Optimize your management process.

      2.4 Define your management roles.

      Outputs

      Application management approach for each application

      Product backlog management practices

      Application management process

      Application management roles and responsibilities and communication flow

      3 Build Your Optimization Roadmap

      The Purpose

      Build your application management optimization roadmap to achieve your target state.

      Key Benefits Achieved

      Optimization opportunities

      Application management optimization roadmap

      Activities

      3.1 Build your optimization roadmap.

      Outputs

      Application management optimization roadmap

      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]

      Develop a Web Experience Management Strategy

      • Buy Link or Shortcode: {j2store}555|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
      • Web Experience Management (WEM) solutions have emerged as applications that provide marketers and other customer experience professionals with a complete set of tools for web content management, delivery, campaign execution, and site analytics.
      • However, many organizations are unsure of how to leverage these new technologies to enhance their customer interaction strategy.

      Our Advice

      Critical Insight

      • WEM products are not a one-size-fits-all investment: unique evaluations and customization is required in order to deploy a solution that fits your organization.
      • WEM technology often complements core CRM and marketing management products – it does not supplant it, and must augment the rest of your customer experience management portfolio.
      • WEM provides benefits by giving web visitors a better experience – leveraging tools such as web analytics gives the customer a tailored experience. Marketing can then monitor their behavior and use this information to warm leads.

      Impact and Result

      • Deploy a WEM platform and execute initiatives that will strengthen the web-facing customer experience, improving customer satisfaction and unlocking new revenue opportunities.
      • Avoid making unnecessary new WEM investments.
      • Make informed decisions about the types of technologies and initiatives that are necessary to support WEM.

      Develop a Web Experience Management Strategy Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should develop a WEM strategy, 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. Harness the value of web experience management

      Make the case for a web experience management suite and structure the WEM strategy project.

      • Develop a Web Experience Management Strategy Phase 1: Harness the Value of Web Experience Management
      • Web Experience Management Strategy Summary Template
      • WEM Project Charter Template

      2. Create the vision for web experience management

      Identify the target state WEM strategy, assess current state, and identify gaps.

      • Develop a Web Experience Management Strategy Phase 2: Create the Vision for Web Experience Management

      3. Execute initiatives for WEM deployment

      Build the WEM technology stack and create a web strategy initiatives roadmap.

      • Develop a Web Experience Management Strategy Phase 3: Execute Initiatives for WEM Deployment
      • Web Process Automation Investment Appropriateness Assessment Tool
      [infographic]

      Workshop: Develop a Web Experience Management 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 Launch the WEM Selection Project

      The Purpose

      Discuss the general project overview for the WEM selection.

      Key Benefits Achieved

      Launch of your WEM selection project.

      Development of your organization’s WEM requirements. 

      Activities

      1.1 Facilitation of activities from the Launch the WEM Project and Collect Requirements phase, including project scoping and resource planning.

      1.2 Conduct overview of the WEM market landscape, trends, and vendors.

      1.3 Conduct process mapping for selected marketing processes.

      1.4 Interview business stakeholders.

      1.5 Prioritize WEM functional requirements.

      Outputs

      WEM Procurement Project Charter

      WEM Use-Case Fit Assessment

      2 Plan the Procurement and Implementation Process

      The Purpose

      Plan the procurement and the implementation of the WEM solution.

      Key Benefits Achieved

      Selection of a WEM solution.

      A plan for implementing the selected WEM solution. 

      Activities

      2.1 Complete marketing process mapping with business stakeholders.

      2.2 Interview IT staff and project team, identify technical requirements for the WEM suite, and document high-level solution requirements.

      2.3 Perform a use-case scenario assessment, review use-case scenario results, identify use-case alignment, and review the WEM Vendor Landscape vendor profiles and performance.

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

      2.5 Meet with project manager to discuss results and action items.

      Outputs

      Vendor Shortlist

      WEM RFP

      Vendor Evaluations

      Selection of a WEM Solution

      WEM projected work break-down

      Implementation plan

      Framework for WEM deployment and CRM/Marketing Management Suite Integration

      Master the Secrets of Adobe’s Creative Cloud Contracts to Right-Size Your Adobe Spend

      • Buy Link or Shortcode: {j2store}139|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $63,667 Average $ Saved
      • member rating average days saved: 110 Average Days Saved
      • Parent Category Name: Licensing
      • Parent Category Link: /licensing
      • Adobe operates in its own niche in the creative space, and Adobe users have grown accustomed to their products, making switching very difficult.
      • With Adobe’s transition to a cloud-based subscription model, it’s important for organizations to actively manage licenses, software provisioning, and consumption.
      • Without a detailed understanding of Adobe’s various purchasing models, overspending often occurs.
      • Organizations have experienced issues in identifying commercial licensed packages with their install files, making it difficult to track and assign licenses.

      Our Advice

      Critical Insight

      • Focus on user needs first. Examine which products are truly needed versus nice to have to prevent overspending on the Creative Cloud suite.
      • Examine what has been deployed. Knowing what has been deployed and what is being used will greatly aid in completing your true-up.
      • Compliance is not automatic with products that are in the cloud. Shared logins or computers that have desktop installs that can be access by multiple users can cause noncompliance.

      Impact and Result

      • Visibility into license deployments and needs
      • Compliance with internal audits

      Master the Secrets of Adobe’s Creative Cloud Contracts to Right-Size Your Adobe Spend Research & Tools

      Start here – read the Executive Brief

      Procuring Adobe software is not the same game as it was just a few years ago. Adopt a comprehensive approach to understanding Adobe licensing to avoid overspending and to maximize negotiation leverage.

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

      1. Manage your Adobe agreements

      Use Info-Tech’s licensing best practices to avoid overspending on Adobe licensing and to remain compliant in case of audit.

      • Adobe ETLA vs. VIP Pricing Table
      • Adobe ETLA Forecasted Costs and Benefits
      • Adobe ETLA Deployment Forecast
      [infographic]

      Further reading

      Master the Secrets of Adobe’s Creative Cloud Contracts to Right-Size Your Adobe Spend

      Learn the essential steps to avoid overspending and to maximize negotiation leverage with Adobe.

      ANALYST PERSPECTIVE

      Only 18% of Adobe licenses are genuine copies: are yours?

      "Adobe has designed and executed the most comprehensive evolution to the subscription model of pre-cloud software publishers with Creative Cloud. Adobe's release of Document Cloud (replacement for the Acrobat series of software) is the final nail in the coffin for legacy licensing for Adobe. Technology procurement functions have run out of time in which to act while they still retain leverage, with the exception of some late adopter organizations that were able to run on legacy versions (e.g. CS6) for the past five years. Procuring Adobe software is not the same game as it was just a few years ago. Adopt a comprehensive approach to understanding Adobe licensing, contract, and delivery models in order to accurately forecast your software needs, transact against the optimal purchase plan, and maximize negotiation leverage. "

      Scott Bickley

      Research Lead, Vendor Practice

      Info-Tech Research Group

      Our understanding of the problem

      This Research is Designed For:

      • IT managers scoping their Adobe licensing requirements and compliance position.
      • CIOs, CTOs, CPOs, and IT directors negotiating licensing agreements in search of cost savings.
      • ITAM/Software asset managers responsible for tracking and managing Adobe licensing.
      • IT and business leaders seeking to better understand Adobe licensing options (Creative Cloud).
      • Vendor management offices in the process of a contract renewal.

      This Research Will Help You:

      • Understand and simplify licensing per product to help optimize spend.
      • Ensure agreement type is aligned to needs.
      • Navigate the purchase process to negotiate from a position of strength.
      • Manage licenses more effectively to avoid compliance issues, audits, and unnecessary purchases.

      This Research Will Also Assist:

      • CFOs and the finance department
      • Enterprise architects
      • ITAM/SAM team
      • Network and IT architects
      • Legal
      • Procurement and sourcing

      This Research Will Help Them:

      • Understand licensing methods in order to make educated and informed decisions.
      • Understand the future of the cloud in your Adobe licensing roadmap.

      Executive summary

      Situation

      • Adobe’s dominant market position and ownership of the creative software market is forcing customers to refocus the software acquisition process to ensure a positive ROI on every license.
      • In early 2017, Adobe announced it would stop selling perpetual Creative Suite 6 products, forcing future purchases to be transitioned to the cloud.

      Complication

      • Adobe operates in its own niche in the creative space, and Adobe users have grown accustomed to their products, making switching very difficult.
      • With transition to a cloud-based subscription model, organizations need to actively manage licenses, software provisioning, and consumption.
      • Without a detailed understanding of Adobe’s various purchasing models, overspending often occurs.
      • Organizations have experienced issues in identifying commercial licensed packages with their install files, making it difficult to track and assign licenses.

      Resolution

      • Gain visibility into license deployments and needs with a strong SAM program/tool; this will go a long way toward optimizing spend.
        • Number of users versus number of installs are not the same, and confusing the two can result in overspending. Device-based licensing historically would have required two licenses, but now only one may be required.
      • Ensure compliance with internal audits. Adobe has a very high rate of piracy stemming from issues such as license overuse, misunderstanding of contract language, using cracks/keygens, virtualized environments, indirect access, and sharing of accounts.
      • A handful of products are still sold as perpetual – Acrobat Standard/Pro, Captivate, ColdFusion, Photoshop, and Premiere Elements – but be aware of what is being purchased and used in the organization.
        • Beware of products deployed on server, where the number of users accessing that product cannot easily be counted.

      Info-Tech Insight

      1. Your user-need analysis has shifted in the new subscription-based model. Determine which products are needed versus nice to have to prevent overspending on the Creative Cloud suite.
      2. Examine what you need, not what you have. You can no longer mix and match applications.
      3. Compliance is not automatic with products that are in the cloud. Shared logins or computers with desktop installs that can be accessed by multiple users can cause noncompliance.

      The aim of this blueprint is to provide a foundational understanding of Adobe

      Why Adobe

      In 2011 Adobe took the strategic but radical move toward converting its legacy on-premises licensing to a cloud-based subscription model, in spite of material pushback from its customer base. While revenues initially dipped, Adobe’s resolve paid off; the transition is mostly complete and revenues have doubled. This was the first enterprise software offering to effect the transition to the cloud in a holistic manner. It now serves as a case study for those following suit, such as Microsoft, Autodesk, and Oracle.

      What to know

      Adobe elected to make this market pivot in a dramatic fashion, foregoing a gradual transition process. Enterprise clients were temporarily allowed to survive on legacy on-premises editions of Adobe software; however, as the Adobe Creative Cloud functionality was quickly enhanced and new applications were launched, customer capitulation to the new subscription model was assured.

      The Future

      Adobe is now leveraging the power of connected customers, the availability of massive data streams, and the ongoing digitalization trend globally to supplement the core Creative Cloud products with online services and analytics in the areas of Creative Cloud for content, Marketing Cloud for marketers, and Document Cloud for document management and workflows. This blueprint focuses on Adobe's Creative Cloud and Document Cloud solutions and the enterprise term license agreement (ETLA).

      Info-Tech Insight

      Beware of your contract being auto-renewed and getting locked into the quantities and product subset that you have in your current agreement. Determining the number of licenses you need is critical. If you overestimate, you're locked in for three years. If you underestimate, you have to pay a big premium in the true-up process.

      Learn the “Adobe way,” whether you are reviewing existing spend or considering the purchase of new products

      1. Legacy on-premises Adobe Creative Suite products used to be available in multiple package configurations, enabling right-sized spend with functionality. Adobe’s support for legacy Creative Suites CS6 products ended in May 2017.
      2. While early ETLAs allowed customer application packaging at a lower price than the full Creative Cloud suite, this practice has been discontinued. Now, the only purchasing options are the full suite or single-application subscriptions.
      3. Buyers must now assess alternative Adobe products as an option for non-power users. For example, QuarkXPress, Corel PaintShop Pro, CorelDRAW, Bloom, and Affinity Designer are possible replacements for some Creative Cloud applications.
      4. Document Cloud, Adobe’s latest step in creating an Acrobat-focused subscription model, limits the ability to reduce costs with an extended upgrade cycle. These changes go beyond the licensing model.
      5. Organizations need to perform a cost-benefit analysis of single app purchases vs. the full suite to right-size spend with functionality.

      As Adobe’s dominance continues to grow, organizations must find new ways to maintain a value-added relationship

      Adobe estimates the total addressable market for creative and document cloud to be $21 billion. With no sign of growth slowing down, Adobe customers must learn how to work within the current design monopoly.

      The image contains two pie graphs. The first is labelled FY2014 Revenue Mix, and the second graph is titled FY2017E Revenue Mix.

      Source: Adobe, 2017

      "Adobe is not only witnessing a steady increase in Creative Cloud subscriptions, but it also gained more visibility into customers’ product usage, which enables it to consistently push out software updates relevant to user needs. The company also successfully transformed its sales organization to support the recurring revenue model."

      – Omid Razavi, Global Head of Success, ServiceNow

      Consider your route forward

      Consider your route forward, as ETLA contract commitments, scope, and mechanisms differ in structure to the perpetual models previously utilized. The new model shortchanges technology procurement leaders in their expectations of cost-usage alignment and opex flexibility (White, 2016).

      ☑ Implement a user profile to assign licenses by version and limit expenditures. Alternatives can include existing legacy perpetual and Acrobat classic versions that may already be owned by the organization.

      ☑ Examine the suitability and/or dependency on Document Cloud functions, such as existing business workflows and e-signature integration.

      ☑ Involve stakeholders in the evaluation of alternate products for use cases where dependency on Acrobat-specific functionality is limited.

      ☑ Identify not just the installs and active use of the applications but also the depth and breadth of use across the various features so that the appropriate products can be selected.

      The image contains a screenshot of a diagram listing the adobe toolkit. The toolkit includes: Adobe ETLA Deployment Forecast Tool, Adobe ETLA Forecasted Cost and Benefits, Adobe ETLA vs. VIP Pricing Table.

      Use Info-Tech’s Adobe toolkit to prepare for your new purchases or contract renewal

      Info-Tech Insight

      IT asset management (ITAM) and software asset management (SAM) are critical! An error made in a true-up can cost the organization for the remaining years of the ETLA. Info-Tech worked with one client that incurred a $600k error in the true-up that they were not able to recoup from Adobe.

      Apply licensing best practices and examine the potential for cost savings through an unbiased third-party perspective

      Establish Licensing Requirements

      • Understand Adobe’s product landscape and transition to cloud.
      • Analyze users and match to correct Adobe SKU.
      • Conduct an internal software assessment.
      • Build an effective licensing position.

      Evaluate Licensing Options

      • Value Incentive Plan (VIP)
      • Cumulative Licensing Program (CLP)
      • Transactional Licensing Program (TLP)
      • Enterprise Term License Agreement (ETLA)

      Evaluate Agreement Options

      • Price
      • Discounts
      • Price protection
      • Terms and conditions

      Purchase and Manage Licenses

      • Learn negotiation tactics to enhance your current strategy.
      • Control the flow of communication.
      • Assign the right people to manage the environment.

      Preventive practices can help find measured value ($)

      Time and resource disruption to business if audited

      Lost estimated synergies in M&A

      Cost of new licensing

      Cost of software audit, penalties, and back support

      Lost resource allocation and time

      Third party, legal/SAM partners

      Cost of poor negotiation tactics

      Lost discount percentage

      Terms and conditions improved

      Explore Adobe licensing and optimize spend – project overview

      Establish Licensing Requirements

      Evaluate Licensing Options

      Evaluate Agreement Options

      Purchase and Manage Licenses

      Best-Practice Toolkit

      • Assess current state and align goals; review business feedback.
      • Interview key stakeholders to define business objectives and drivers.
      • Review licensing options.
      • Review licensing rules.
      • Determine the ideal contract type.
      • Review final contract.
      • Discuss negotiation points.
      • License management.
      • Future licensing strategy.

      Guided Implementations

      • Engage in a scoping call.
      • Assess the current state.
      • Determine licensing position.
      • Review product options.
      • Review licensing rules.
      • Review contract option types.
      • Determine negotiation points.
      • Finalize the contract.
      • Discuss license management.
      • Evaluate and develop a roadmap for future licensing.

      PHASE 1

      Manage Your Adobe Agreements

      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: Managing Adobe Contracts

      Proposed Time to Completion: 3-6 weeks

      Step 1.1: Establish Licensing Requirements

      Start with a kick-off call:

      • Assess the current state.
      • Determine licensing position.

      Then complete these activities…

      • Complete a deployment count, needs analysis, and internal audit.

      With these tools & templates:

      Adobe ETLA Deployment Forecast

      Step 1.2: Determine Licensing Options

      Review findings with analyst:

      • Review licensing options.
      • Review licensing rules.
      • Review contract option types.

      Then complete these activities…

      • Select licensing option.
      • Document forecasted costs and benefits.

      With these tools & templates:

      Adobe ETLA vs. VIP Pricing Table

      Adobe ETLA Forecasted Costs and Benefits

      Step 1.3: Purchase and Manage Licenses

      Review findings with analyst:

      • Review final contract.
      • Discuss negotiation points.
      • Plan a roadmap for SAM.

      Then complete these activities…

      • Negotiate final contract.
      • Evaluate and develop a roadmap for SAM.

      With these tools & templates:

      Adobe ETLA Deployment Forecast

      Adobe’s Cloud – Snapshot of what has changed

      1. Since Adobe has limited the procurement and licensing options with the introduction of Creative Cloud, there are three main choices:
        1. Direct online purchase at Adobe.com
        2. Value Incentive Plan (VIP): Creative Cloud for teams–based purchase with a volume discount (minimal, usually ~10%); may have some incentives or promotional pricing
        3. Enterprise Term License Agreement (ETLA): Creative Cloud for Enterprise (CCE)
      2. Adobe has discontinued support for legacy perpetual licenses, with the latest version being CS6, which is steering organizations to prioritize their options for products in the creative and document management space.
      3. Document Cloud (DC) is the cloud product replacing the Acrobat perpetual licensing model. DC extends the subscription-based model further and limits options to extend the lifespan of legacy on-premises licenses through a protracted upgrade process.
      4. The subscription model, coupled with limited discount options on transactional purchases, forces enterprises to consider the ETLA option. The ETLA brings with it unique term commitments, new pricing structures, and true-up mechanisms and inserts the "land and expand" model vs. license reassignment.

      Info-Tech Insight

      Adobe’s move from a perpetual license to a per-user subscription model can be positive in some scenarios for organizations that experienced challenges with deployment, management of named users vs. devices, and license tracking.

      Core concepts of Adobe agreements: Discounting, pricing, and bundling

      ETLA

      Adobe has been systematically reducing discounts on ETLAs as they enter the second renewal cycle of the original three-year terms.

      Adobe Cloud Bundling

      Adobe cloud services are being bundled with ETLAs with a mandate that companies that do not accept the services at the proposed cost have Adobe management’s approval to unbundle the deal, generally with no price relief.

      Custom Bundling

      The option for custom bundling of legacy Creative Suite component applications has been removed, effectively raising the price across the board for licensees that require more than two Adobe applications who must now purchase the full Creative Cloud suite.

      Higher and Public Education

      Higher education/public education agreements have been revamped over the past couple of years, increasing prices for campus-wide agreements by double-digit percentages (~10-30%+). While they still receive an 80% discount over list price, IT departments in this industry are not prepared to absorb the budget increase.

      Info-Tech Insight

      Adobe has moved to an all-or-one bundle model. If you need more than two application products, you will likely need to purchase the full Creative Cloud suite. Therefore, it is important to focus on creating accurate user profiles to identify usage needs.

      Use Info-Tech’s Adobe deployment tool for SAM: Track deployment and needs

      The image contains a screenshot of Info-Tech's Adobe deployment tool for SAM: Track deployment and needs.

      Use Info-Tech’s Adobe deployment tool for SAM: Audit

      The image contains a screenshot of the Adobe Deployment Tool for SAM, specifically the Audit tab.

      Use Info-Tech’s Adobe deployment tool for SAM: Cost

      The image contains a screenshot of the Adobe Deployment Tool for SAM, specifically the Cost tab.

      Use Info-Tech’s tools to compare ETLA vs. VIP and to document forecasted costs and benefits

      Is the ETLA or VIP option better for your organization?

      Use Info-Tech’s Adobe ETLA vs. VIP Pricing Table tool to compare ETLA costs against VIP costs.

      The image contains a screenshot of Info-Tech's Adobe ETLA vs. VIP Pricing Table.

      Your ETLA contains multiple products and is a multi-year agreement.

      Use Info-Tech’s ETLA Forecasted Costs and Benefits tool to forecast your ETLA costs and document benefits.

      The image contains a screenshot of Info-Tech's ETLA Forecasted Costs and Benefits.

      Adobe’s Creative Cloud Complete offering provides access to all Adobe creative products and ongoing upgrades

      Why subscription model?

      The subscription model forces customers to an annuity-based pricing model, so Adobe has recurring revenue from a subscription-based product. This increases customer lifetime value (CLTV) for Adobe while providing ongoing functionality updates that are not version/edition dependent.

      Key Characteristics:

      • Available as a month-to-month or annual subscription license
      • Can be purchased for one user, for a team, or for an enterprise
      • Subject to annual payment and true-up of license fees
      • Can only true-up during lifespan of contract; quantities cannot be reduced until renewal
      • May contain auto-renewal clauses – beware!

      Key things to know:

      1. Applications can be purchased individually if users require only one specific product. A few products continue to have on-premises licensing options, but most are offered by per-user subscriptions.
      2. At the end of the subscription period, the organization no longer has any rights to the software and would have to return to a previously owned version.
      3. True-downs are not possible (in contrast to Microsoft’s Office 365).
      4. Downgrade rights are not included or are limited by default.

      Which products are in the Creative Cloud bundle?

      Adobe Acrobat® XI Pro

      Adobe After Effects® CC

      Adobe Audition® CC

      Adobe Digital Publishing Suite, Single Edition

      Adobe InDesign® CC

      Adobe Dreamweaver® CC

      Adobe Edge Animate

      Adobe Edge Code preview

      Adobe Edge Inspect

      Adobe Photoshop CC

      Adobe Edge Reflow preview

      Adobe Edge Web Fonts

      Adobe Extension Manager

      ExtendScript Toolkit

      Adobe Fireworks® CS6

      Adobe Flash® Builder® 4.7 Premium Edition

      Adobe Flash Professional CC

      Adobe Illustrator® CC

      Adobe Prelude® CC

      Adobe Premiere® Pro CC

      Adobe Scout

      Adobe SpeedGrade® CC

      Adobe Muse CC

      Adobe Photoshop Lightroom 6

      Adobe offers different solutions for teams vs. enterprise licensing

      Evaluate the various options for Creative Cloud, as they can be purchased individually, for teams, or for enterprise.

      Bundle Name

      Target Customer

      Included Applications

      Features

      CC (for Individuals)

      Individual users

      The individual chooses

      • Sync, store, and share assets
      • Adobe Portfolio website
      • Adobe Typekit font collection
      • Microsoft Teams integration
      • Can only be purchased through credit card

      CC for Teams (CCT)

      Small to midsize organizations with a small number of Adobe users who are all within the same team

      Depends on your team’s requirements. You can select all applications or specific applications.

      Everything that CC (for individuals) does, plus

      • One license per user; can reassign CC licenses
      • Web-based admin console
      • Centralized deployment
      • Usage tracking and reporting
      • 100GB of storage per user
      • Volume discounts for 10+ seats

      CC for Enterprise (CCE)

      Large organizations with users who regularly use multiple Adobe products on multiple machines

      All applications including Adobe Stock for images and Adobe Enterprise Dashboard for managing user accounts

      Everything that CCT does, plus

      • Employees can activate a second copy of software on another device (e.g. home computer) as long as they share the same Adobe ID and are not used simultaneously
      • Ability to reassign licenses from old users to new users
      • Custom storage options
      • Greater integration with other Adobe products
      • Larger volume discounts with more seats

      For further information on specific functionality differences, reference Adobe’s comparison table.

      A Cloud-ish solution: Considerations and implications for IT organizations

      ☑ True cloud products are typically service-based, scalable and elastic, shared resources, have usage metering, and rely upon internet technologies. Currently, Adobe’s Creative Cloud and Document Cloud products lack these characteristics. In fact, the core products are still downloaded and physically installed on endpoint devices, then anchored to the cloud provisioning system, where the software can be automatically updated and continuously verified for compliance by ensuring the subscription is active.

      ☑ Adobe Cloud allows Adobe to increase end-user productivity by releasing new features and products to market faster, but the customer will increase lock-in to the Adobe product suite. The fast-release approach poses a different challenge for IT departments, as they must prepare to test and support new functionality and ensure compatibility with endpoint devices.

      ☑ There are options at the enterprise level that enable IT to exert more granular control over new feature releases, but these are tied to the ETLA and the provided enterprise portal and are not available on other subscription plans. This is another mechanism by which Adobe has been able to spur ETLA adoption.

      Not all CIOs consider SaaS/subscription applications their first choice, but the Adobe’s dominant position in the content and document management marketplace is forcing the shift regardless. It is significant that Adobe bypassed the typical hybrid transition model by effectively disrupting the ability to continue with perpetual licensing without falling behind the functionality curve.

      VIP plans do allow for annual terms and payment, but you lose the price elasticity that comes with multi-year terms.

      Download Info-Tech’s Adobe ETLA vs. VIP Pricing Table tool to compare ETLA costs against VIP costs.

      When moving to Adobe cloud, validate that license requirements meet organizational needs, not a sales quota

      Follow these steps in your transition to Creative Cloud.

      Step 1: Make sure you have a software asset management (SAM) tool to determine Adobe installs and usage within your environment.

      Step 2: Look at the current Adobe install base and usage. We recommend reviewing three months’ worth of reliable usage data to decide which users should have which licenses going forward.

      Step 3: Understand the changes in Adobe packages for Creative Cloud (CC). Also, take into account that the license types are based on users, not devices.

      Step 4: Identify those users who only need a single license for a single application (e.g. Photoshop, InDesign, Muse).

      Step 5: Identify the users who require CC suites. Look at their usage of previous Adobe suites to get an idea of which CC suite they require. Did they have Design Suite Standard installed but only use one or two elements? This is a good way to ensure you do not overspend on Adobe licenses.

      Source: The ITAM Review

      Download Info-Tech’s Adobe ETLA Deployment Forecast tool to track Adobe installs within your environment and to determine usage needs.

      Acquiring Adobe Software

      Adobe offers four common licensing methods, which are reviewed in detail in the following slides.

      Most common purchasing models

      Points for consideration

      • Value Incentive Plan (VIP)
      • Cumulative Licensing Program (CLP)
      • Transactional Licensing Program (TLP)
      • Enterprise Term License Agreement (ETLA)
      • Adobe, as with many other large software providers, includes special benefits and rights when its products are purchased through volume licensing channels.
      • Businesses should typically refrain from purchasing individual OEM (shrink wrap) licenses or those meant for personal use.
      • Purchase record history is available online, making it easier for your organization to manage entitlements in the case of an audit.

      "Customers are not even obliged to manage all the licenses themselves. The reseller partners have access to the cloud console and can manage licenses on behalf of their customers. Even better, they can seize cross and upsell opportunities and provide good insight into the environment. Additionally, Adobe itself provides optimization services."

      B-lay

      CLP and TLP

      The CLP and TLP are transactional agreements generally used for the purchase of perpetual licenses. For example, they could be used for making Acrobat purchases if Creative Suite products are purchased on the ETLA.

      The image contains a screenshot of a table comparing CLP and TLP.

      Source: “Adobe Buying Programs Comparison Guide for Commercial and Government Organizations”

      VIP and ETLA

      The Value Incentive Plan is aimed at small- to medium-sized organizations with no minimum quantity required. However, there is limited flexibility to reduce licenses and limited price protection for future purchases. The ETLA is aimed at large organizations who wish to have new functionality as it comes out, license management portal, services, and security/IT control aspects.

      The image contains a screenshot of a table comparing VIP and ETLA.

      Source: “Adobe Buying Programs Comparison Guide for Commercial and Government Organizations”

      ETLA commitments risk creating “shelfware-as-a-service”

      The Adobe ETLA’s rigid contract parameters, true-up process, and unique deployment/provisioning mechanisms give technology/IT procurement leaders fewer options to maximize cost-usage alignment and to streamline opex costs.

      ☑ No ETLA price book is publicly published; pricing is controlled by the Adobe enterprise sales team.

      ☑ Adobe's retail pricing is a good starting point for negotiating discounted pricing.

      ☑ ETLA commitments are usually for three years, and the lack of a true-down option increases the risk involved in overbuying licenses should the organization encounter a business downturn or adverse event.

      ☑ Pricing discounts are the highest at the initial ETLA signing for the upfront volume commitment. The true-up pricing is discounted from retail but still higher than the signing cost per license.

      ☑ Technical support is included in the ETLA.

      ☑ While purchases typically go through value-added resellers (VARs), procurement can negotiate directly with Adobe.

      "For cloud products, it is less complex when it comes to purchasing and pricing. If larger quantities are purchased on a longer term, the discount may reach up to 15%. As soon as you enroll in the VIP program, you can control all your licenses from an ‘admin console’. Any updates or new functionalities are included in the original price. When the licenses expire, you may choose to renew your subscriptions or remove them. Partial renewal is also accepted. Of course, you can also re-negotiate your price if more subscriptions are added to your console."

      B-lay

      ETLA recommendations

      1. Assess the end-user requirements with a high degree of scrutiny. Perform an analysis that matches the licensee with the correct Adobe product SKU to reduce the risk of overspending.
      • Leverage metering data that identifies actual usage and lack thereof, match to user profile functional requirements, and then determine end users’ actual license requirements.
    • Build in time to evaluate alternative products where possible and position the organization to leverage a Plan B vendor to replace or mitigate growth on the Adobe platform. Re-evaluate options well in advance of the ETLA renewal.
    • Secure price protection through negotiating a price cap or an extended ETLA term beyond the standard three-year term. Short of obtaining an escalation cap, which Adobe is strongly resisting, build in price increases for the ETLA renewal years.
      • Demand price transparency and granularity in the proposal process.
      • Validate that volume discounts are appropriate and show through to the true-up line item pricing.
    • Negotiate a true-down mechanism upfront with Adobe if usage decline is inevitable or expected due to a merger or acquisition, divestiture, or material restructuring event.
    • INFO-TECH TIP: For further guidance on ETLAs and pricing, contact your Info-Tech representative to set up a call with an analyst.

      Use Info-Tech’s Adobe ETLA Deployment Forecast tool to match licensees with Adobe product SKUs.

      Prepare for Adobe’s true-up process

      How the true-up process works

      When adding a license, the true-up price will be prorated to 50% of the license cost for previous year’s usage plus 100% of the license cost for the next year. This back-charging adds up to 150% of the overall true-up license cost. In some rare cases, Adobe has provided an “unlimited” quantity for certain SKUs; these Unlimited ETLAs generally align with FTE counts and limit FTE increases to about 5%. Procurement must monitor and work with SAM/ITAM and stakeholder groups to restrain unnecessary growth during the term of an Unlimited ETLA to avoid the risk of cost escalation at renewal time.

      Higher-education specific

      Higher-education clients can license under the ETLA based on a prescribed number of user and classroom/lab devices and/or on a FTE basis. In these cases, the combination of Creative Cloud and Acrobat Pro volume must equal the FTE total, creating an enterprise footprint. FTE calculations establish the full-time faculty plus one-third of part-time faculty plus one-half of part-time staff.

      Info-Tech Insight

      Compliance takes a different form in terms of the ETLA true-up process. The completion of Adobe's transition to cloud-based licensing and verification has improved compliance rates via phone home telemetry such that pirated software is less available and more easily detected. Adobe has actually decommissioned its audit arm in the Americas and EMEA.

      Audits and software asset management with Adobe

      Watch out for:

      • Virtual desktops, freeware, and test and trial licenses
      • Adobe products that may be bundled into a suite; a manual check will be needed to ensure the suite isn’t recognized as a standalone license
      • Pirated licenses with a “crack” built into the software

      Simplify your process – from start to finish – with these steps:

      Determine License Entitlements

      Obtain documentation from internal records and Adobe to track licenses and upgrades to determine what licenses you own and have the right to use.

      Gather Deployment Information

      Leverage a software asset management tool or process to determine what software is deployed and what is/is not being used.

      Determine Effective License Position

      Compare license entitlements with deployment data to uncover surpluses and deficits in licensing. Look for opportunities.

      Plan Changes to License Position

      Meet with IT stakeholders to discuss the enterprise license program (ELP), short- and long-term project plans, and budget allocation. Plan and document licensing requirements.

      Adobe Genuine Software Integrity Service

      • This service was started in 2014 to combat non-genuine software sold by non-authorized resellers.
      • The service works hand in hand with the cloud movement to reduce piracy.
      • Every Adobe product now contains an executable file that will scan your machine for non-genuine software.
      • If non-genuine software is detected, the user will be notified and directed to the official Adobe website for next steps.

      Detailed list of Adobe licensing contract types

      The table below describes Adobe contract types beyond the four typical purchasing models explained in the previous slides:

      Option

      What is it?

      What’s included?

      For

      Term

      CLP (Cumulative Licensing Program)

      10,000 plus points, support and maintenance optional

      Select Adobe perpetual desktop products

      Business

      2 years

      EA (Adobe Enterprise Agreement)

      100 licenses plus maintenance and support for eligible Adobe products

      All applications

      100+ users requirement

      3 years

      EEA (Adobe Enterprise Education Agreement)

      Creative Cloud enterprise agreement for education establishments

      Creative Cloud applications without services

      Education

      1 or 2 years

      ETLA (Enterprise Term License Agreement)

      Licensing program designed for Adobe’s top commercial, government, and education customers

      All Creative Cloud applications

      Large enterprise companies

      3 years

      K-12 – Enterprise Agreement

      Enterprise agreement for primary and secondary schools

      Creative Cloud applications without services

      Education

      1 year

      K-12 – School Site License

      Allows a school to install a Creative Cloud on up to 500 school-owned computers regardless of school size

      Creative Cloud applications without services

      Education

      1 year

      TLP (Transactional Licensing Program)

      Agreement for SMBs that want volume licensing bonuses

      Perpetual desktop products only

      Aimed at SMBs, but Enterprise customers can use the TLP for smaller requirements

      N/A

      Upgrade Plan

      Insurance program for software purchased under a perpetual license program such as CLP or TLP for Creative Cloud upgrade

      Dependent on the existing perpetual estate

      Anyone

      N/A

      VIP (Value Incentive Plan)

      VIP allows customers to purchase, deploy, and manage software through a term-based subscription license model

      Creative Cloud of teams

      Business, government, and education

      Insight breakdown

      Insight 1

      Adobe operates in its own niche in the creative space, and Adobe users have grown accustomed to their products, making switching very difficult.

      Insight 2

      Adobe has transitioned the vast majority of its software offerings to the cloud-based subscription model. Active management of licenses, software provisioning, and consumption of cloud services is now an ongoing job.

      Insight 3

      With the vendor lock-in process nearly complete via the transition to a SaaS subscription model, Adobe is raising prices on an annual basis. Advance planning and strategic use of the ETLA is key to avoid budget-breaking surprises.

      Summary of accomplishment

      Knowledge Gained

      • The key pieces of licensing information that should be gathered about the current state of your own organization.
      • An in-depth understanding of the required licenses across all of your products.
      • Clear methodology for selecting the most effective contract type.
      • Development of measurable, relevant metrics to help track future project success and identify areas of strength and weakness within your licensing program.

      Processes Optimized

      • Understanding of the importance of licensing in relation to business objectives.
      • Understanding of the various licensing considerations that need to be made.
      • Contract negotiation.

      Deliverables Completed

      • Adobe ETLA Deployment Forecast
      • Adobe ETLA Forecasted Cost and Benefits
      • Adobe ETLA vs. VIP Pricing Table

      Related Info-Tech Research

      Take Control of Microsoft Licensing and Optimize Spend

      Create an Effective Plan to Implement IT Asset Management

      Establish an Effective System of Internal IT Controls to Mitigate Risks

      Optimize Software Asset Management

      Take Control of Compliance Improvement to Conquer Every Audit

      Cut PCI Compliance and Audit Costs in Half

      Bibliography

      “Adobe Buying Programs: At-a-glance comparison guide for Commercial and government organizations.” Adobe Systems Incorporated, 2014. Web. 1 Feb. 2018.

      “Adobe Buying Programs Comparison Guide for Commercial and Government Organizations.” Adobe Systems Incorporated, 2018. Web.

      “Adobe Buying Programs Comparison Guide for Education.” Adobe Systems Incorporated, 2018. Web. 1 Feb 2018.

      “Adobe Education Enterprise Agreement: Give your school access to the latest industry-leading creative tools.” Adobe Systems Incorporated, 2014. Web. 1 Feb. 2018.

      “Adobe Enterprise Term License Agreement for commercial and government organizations.” Adobe Systems Incorporated, 2016. Web. 1 Feb. 2018.

      Adobe Investor Presentation – October 2017. Adobe Systems Incorporated, 2017. Web. 1 Feb. 2018.

      Cabral, Amanda. “Students react to end of UConn-Adobe contract.” The Daily Campus (Uconn), 5 April 2017. Web. 1 Feb. 2018.

      de Veer, Patrick and Alecsandra Vintilescu. “Quick Guide to Adobe Licensing.” B-lay, Web. 1 Feb. 2018.

      “Find the best program for your organization.” Adobe, Web. 1 Feb 2018.

      Foxen, David. “Adobe Upgrade Simplified.” Snow Software, 7 Oct. 2016. Web.

      Frazer, Bryant. “Adobe Stops Reporting Subscription Figures for Creative Cloud.” Studio Daily. Access Intelligence, LLC. 17 March 2016. Web.

      “Give your students the power to create bright futures.” Adobe, Web. 1 Feb 2018.

      Jones, Noah. “Adobe changes subscription prices, colleges forced to pay more.” BG Falcon Media. Bowling Green State University, 18 Feb. 2015. Web. 1 Feb. 2018.

      Mansfield, Adam. “Is Your Organization Prepared for Adobe’s Enterprise Term License Agreements (ETLA)?” UpperEdge,30 April 2013. Web. 1 Feb. 2018.

      Murray, Corey. “6 Things Every School Should Know About Adobe’s Move to Creative Cloud.” EdTech: Focus on K-12. CDW LLC, 10 June 2013. Web.

      “Navigating an Adobe Software Audit: Tips for Emerging Unscathed.” Nitro, Web. 1 Feb. 2018.

      Razavi, Omid. “Challenges of Traditional Software Companies Transitioning to SaaS.” Sand Hill, 12 May 2015. Web. 1 Feb. 2018.

      Rivard, Ry. “Confusion in the Cloud.” Inside Higher Ed. 22 May 2013. Web. 1 Feb. 2018.

      Sharwood, Simon. “Adobe stops software licence audits in Americas, Europe.” The Register. Situation Publishing. 12 Aug. 2016. Web. 1 Feb. 2018.

      “Software Licensing Challenges Faced In The Cloud: How Can The Cloud Benefit You?” The ITAM Review. Enterprise Opinions Limited. 20 Nov. 2015. Web.

      White, Stephen. “Understanding the Impacts of Adobe’s Cloud Strategy and Subscriptions Before Negotiating an ETLA.” Gartner, 22 Feb. 2016. Web.

      Corporate security consultancy

      Corporate security consultancy

      Based on experience
      Implementable advice
      human-based and people-oriented

      Engage our corporate security consultancy firm to discover any weaknesses within your company’s security management. Tymans Group has extensive expertise in helping small and medium businesses set up clear security protocols to safeguard their data and IT infrastructure. Read on to discover how our consulting firm can help improve corporate security within your company.

      Why should you hire a corporate security consultancy company?

      These days, corporate security includes much more than just regulating access to your physical location, be it an office or a store. Corporate security increasingly deals in information and data security, as well as general corporate governance and responsibility. Proper security protocols not only protect your business from harm, but also play an important factor in your overall success. As such, corporate security is all about setting up practical and effective strategies to protect your company from harm, regardless of whether the threat comes from within or outside. As such, hiring a security consulting firm to improve corporate security and security management within your company is not an unnecessary luxury, but a must.

      Security and risk management

      Our security and risk services

      Security strategy

      Security Strategy

      Embed security thinking through aligning your security strategy to business goals and values

      Read more

      Disaster Recovery Planning

      Disaster Recovery Planning

      Create a disaster recovey plan that is right for your company

      Read more

      Risk Management

      Risk Management

      Build your right-sized IT Risk Management Program

      Read more

      Check out all our services

      Improve your corporate security with help from our consulting company

      As a consultancy firm, Tymans Group can help your business to identify possible threats and help set up strategies to avoid them. However, as not all threats can be avoided, our corporate security consultancy firm also helps you set up protocols to mitigate and manage them, as well as help you develop effective incident management protocols. All solutions are practical, people-oriented and based on our extensive experience and thus have proven effectiveness.

      Hire our experienced consultancy firm

      Engage the services of our consulting company to improve corporate security within your small or medium business. Contact us to set up an appointment on-site or book a one-hour talk with expert Gert Taeymans to discuss any security issues you may be facing. We are happy to offer you a custom solution.

      Register to read more …

      Modernize Communications and Collaboration Infrastructure

      • Buy Link or Shortcode: {j2store}306|cart{/j2store}
      • member rating overall impact: 9.4/10 Overall Impact
      • member rating average dollars saved: $68,332 Average $ Saved
      • member rating average days saved: 22 Average Days Saved
      • Parent Category Name: Voice & Video Management
      • Parent Category Link: /voice-video-management
      • Organizations are losing productivity from managing the limitations of yesterday’s technology. The business is changing and the current communications solution no longer adequately connects end users.
      • Old communications technology, including legacy telephony systems, disjointed messaging and communication or collaboration mediums, and unintuitive video conferencing, deteriorates the ability of users to work together in a productive manner.
      • You need a solution that meets budgetary requirements and improves internal and external communication, productivity, and the ability to work together.

      Our Advice

      Critical Insight

      • Project scope and assessment will take more time than you initially anticipate. Poorly defined technical requirements can result in failure to meet the needs of the business. Defining project scope and assessing the existing solution is 60% of project time. Being thorough here will make the difference moving forward.
      • Even when the project is about modernizing technology, it’s not really about the technology. The requirements of your people and the processes you want to maintain or reform should be the influential factors in your decisions on technology.
      • Gaining business buy-in can be difficult for projects that the business doesn’t equate with directly driving revenue. Ensure your IT team communicates with the business throughout the process and establishes business requirements. Framing conversations in a “business first, IT second” way is crucial to speaking in a language the business will understand.

      Impact and Result

      • Define a comprehensive set of requirements (across people, process, and technology) at the start of the project. Communication solutions are long-term commitments and mistakes in planning will be amplified during implementation.
      • Analyze the pros and cons of each deployment option and identify a communications solution that balances your budget and communications objectives and requirements.
      • Create an effective RFP by outlining your specific business and technical needs and goals.
      • Make the case for your communications infrastructure modernization project and be prepared to support it.

      Modernize Communications and Collaboration Infrastructure Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should modernize your communications and collaboration infrastructure, 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. Assess communications infrastructure

      Evaluate the infrastructure requirements and the ability to undergo modernization from legacy technology.

      • Modernize Communications and Collaboration Infrastructure – Phase 1: Assess Communications Infrastructure
      • Communications Infrastructure Roadmap Tool
      • Team Skills Inventory Tool
      • MACD Workflow Mapping Template - Visio
      • MACD Workflow Mapping Template - PDF

      2. Define the target state

      Build and document a formal set of business requirements using Info-Tech's pre-populated template after identifying stakeholders, aligning business and user needs, and evaluating deployment options.

      • Modernize Communications and Collaboration Infrastructure – Phase 2: Define the Target State
      • Stakeholder Engagement Workbook
      • Communications Infrastructure Stakeholder Focus Group Guide
      • IP Telephony and UC End-User Survey Questions
      • Enterprise Communication and Collaboration System Business Requirements Document
      • Communications TCO-ROI Comparison Calculator

      3. Advance the project

      Draft an RFP for a UC solution and gain project approval using Info-Tech’s executive presentation deck.

      • Modernize Communications and Collaboration Infrastructure – Phase 3: Advance the Project
      • Unified Communications Solution RFP Template
      • Modernize Communications Infrastructure Executive Presentation
      [infographic]

      Workshop: Modernize Communications and Collaboration Infrastructure

      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 Communications Infrastructure

      The Purpose

      Identify pain points.

      Build a skills inventory.

      Define and rationalize template configuration needs.

      Define standard service requests and map workflow.

      Discuss/examine site type(s) and existing technology.

      Determine network state and readiness.

      Key Benefits Achieved

      IT skills & process understanding.

      Documentation reflecting communications infrastructure.

      Reviewed network readiness.

      Completed current state analysis.

      Activities

      1.1 Build a skills inventory.

      1.2 Document move, add, change, delete (MACD) processes.

      1.3 List relevant communications and collaboration technologies.

      1.4 Review network readiness checklist.

      Outputs

      Clearly documented understanding of available skills

      Documented process maps

      Complete list of relevant communications and collaboration technologies

      Completed readiness checklist

      2 Learn and Evaluate Options to Define the Future

      The Purpose

      Hold focus group meeting.

      Define business needs and goals.

      Define solution options.

      Evaluate options.

      Discuss business value and readiness for each option.

      Key Benefits Achieved

      Completed value and readiness assessment.

      Current targets for service and deployment models.

      Activities

      2.1 Conduct internal focus group.

      2.2 Align business needs and goals.

      2.3 Evaluate deployment options.

      Outputs

      Understanding of user needs, wants, and satisfaction with current solution

      Assessment of business needs and goals

      Understanding of potential future-state solution options

      3 Identify and Close the Gaps

      The Purpose

      Identify gaps.

      Examine and evaluate ways to remedy gaps.

      Determine specific business requirements and introduce draft of business requirements document.

      Key Benefits Achieved

      Completed description of future state.

      Identification of gaps.

      Identification of key business requirements.

      Activities

      3.1 Identify gaps and brainstorm gap remedies.

      3.2 Complete business requirements document.

      Outputs

      Well-defined gaps and remedies

      List of specific business requirements

      4 Build the Roadmap

      The Purpose

      Introduce Unified Communications Solution RFP Template.

      Develop statement of work (SOW).

      Document technical requirements.

      Complete cost-benefit analysis.

      Key Benefits Achieved

      Unified Communications RFP.

      Documented technical requirements.

      Activities

      4.1 Draft RFP (SOW, tech requirements, etc.).

      4.2 Conduct cost-benefit analysis.

      Outputs

      Ready to release RFP

      Completed cost-benefit analysis

      Manage the Active Directory in the Service Desk

      • Buy Link or Shortcode: {j2store}489|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
      • Actively maintaining the Active Directory is a difficult task that only gets more difficult with issues like stale accounts and privilege creep.
      • Adding permissions without removing them in lateral transfers creates access issues, especially when regulatory requirements like HIPAA require tight controls.
      • With the importance of maintaining and granting permissions within the Active Directory, organizations are hesitant to grant domain admin access to Tier 1 of the service desk. However, inundating Tier 2 analysts with requests to grant permissions takes away project time.

      Our Advice

      Critical Insight

      • Do not treat the Active Directory like a black box. Strive for accurate data and be proactive by managing your monitoring and audit schedules.
      • Catch outage problems before they happen by splitting monitoring tasks between daily, weekly, and monthly routines.
      • Shift left to save resourcing by employing workflow automation or scripted authorization for Tier 1 technicians.
      • Design actionable metrics to monitor and manage your Active Directory.

      Impact and Result

      • Consistent and right-sized monitoring and updating of the Active Directory is key to clean data.
      • Split monitoring activities between daily, weekly, and monthly checklists to raise efficiency.
      • If need be, shift-left strategies can be implemented for identity and access management by scripting the process so that it can be done by Tier 1 technicians.

      Manage the Active Directory in the Service Desk Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should manage your Active Directory in the service desk, 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. Maintain your Active Directory with clean data

      Building and maintaining your Active Directory does not have to be difficult. Standardized organization and monitoring with the proper metrics help you keep your data accurate and up to date.

      • Active Directory Standard Operating Procedure
      • Active Directory Metrics Tool

      2. Structure your service desk Active Directory processes

      Build a comprehensive Active Directory workflow library for service desk technicians to follow.

      • Active Directory Process Workflows (Visio)
      • Active Directory Process Workflows (PDF)
      [infographic]

      2021 IT Talent Trend Report

      • Buy Link or Shortcode: {j2store}516|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $9,919 Average $ Saved
      • member rating average days saved: 2 Average Days Saved
      • Parent Category Name: Lead
      • Parent Category Link: /lead
      • In March 2020, many organizations were forced to switch to a virtual working world. IT enabled organizations to be successful while working from home. Ultimately, this shift changed the way that we all work, and in turn, the way IT leaders manage talent.
      • Many organizations are considering long-term remote work (Kelly, 2020).
      • Change is starting but is lagging.

      Our Advice

      Critical Insight

      • Increase focus on employee experience to navigate new challenges.
      • A good employee experience is what is best for the IT department.

      Impact and Result

      • The data shows IT is changing in the area of talent management.
      • IT has a large role in enabling organizations to work from home, especially from a technological and logistics perspective. There is evidence to show that they are now expanding their role to better support employees when working from home.
      • Survey respondents identified efforts already underway for IT to improve employee experience and subsequently, IT effectiveness.

      2021 IT Talent Trend Report Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should focus on the employee experience and get an overview of what successful IT leaders are doing differently heading into 2021 – the five new talent management trends.

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

      1. DEI: A top talent objective

      The focus on diversity, equity, and inclusion (DEI) initiatives spans the entire organization beyond just HR. Learn which DEI efforts are underway with IT.

      • 2021 IT Talent Trend Report – Trend 1: DEI: A Top Talent Objective

      2. Remote work is here to stay

      Forced work-from-home demonstrated to organizations that employees can be productive while working away from the physical office. Learn more about how remote work is changing work.

      • 2021 IT Talent Trend Report – Trend 2: Remote Work Is Here to Stay

      3. A greater emphasis on wellbeing

      When the pandemic hit, organizations were significantly concerned about how employees were doing. Learn more about wellbeing.

      • 2021 IT Talent Trend Report – Trend 3: A Greater Emphasis on Wellbeing

      4. A shift in skills priorities

      Upskilling and finding sought after skills were challenging before the pandemic. How has it changed since? Learn more about skills priorities.

      • 2021 IT Talent Trend Report – Trend 4: A Shift in Skills Priorities

      5. Uncertainty unlocks performance

      The pandemic and remote work has affected performance. Learn about how uncertainty has impacted performance management.

      • 2021 IT Talent Trend Report – Trend 5: Uncertainty Unlocks Performance
      [infographic]

      Optimize Social Media Strategy by Service

      • Buy Link or Shortcode: {j2store}562|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: 5 Average Days Saved
      • Parent Category Name: Marketing Solutions
      • Parent Category Link: /marketing-solutions
      • Many organizations are jumping the gun on service selection and missing valuable opportunities to tap into conversations their consumers are having about them.
      • Companies are struggling to harness real benefits from social media because they dive into content and engagement strategy without spending the appropriate amount of time on social media service selection.
      • After organizations have selected the appropriate social media services, clients fail to understand best practices for participating in conversations and therefore are unable to optimize their success on each service.

      Our Advice

      Critical Insight

      • Conventional wisdom dictates that you should pick the social network where you have the greatest subscriber base to reach, but this is irrelevant. Organizations need to consider all the social media services available when selecting services, to ensure they are optimizing their social media strategy and interacting with the right people.
      • In today’s social media landscape there is a wide variety of social media services to choose from. Services range from hot micro-blogging services, like Twitter, to more niche social multimedia services, like Flickr or Vimeo.
      • Each department should manage its set of relevant services regardless of platform. For example a marketing manager should manage all social media services in marketing, rather than have one person manage all Twitter feeds, one person manage all Facebook pages, etc.
      • The services your organization selects shouldn’t operate as islands. Consider not only how the services will fit with each other, but also how they will fit with existing channels. Use a market coverage model to ensure the services you select are complementing each other.
      • The landscape for social media services changes rapidly. It is essential to conduct an audit of services to maintain an optimal mix of services. Conduct the audit semi-annually for best effect.

      Impact and Result

      • Learn about the importance of choosing the correct services to ensure you are reaching your consumers and not wasting time playing with the wrong people.
      • Understand the business use cases for each service and best practices for using them.
      • Leverage different social media services to create a market coverage model that balances social media services with your products/services and business objectives.
      • Identify the risks associated with specific platforms and ensure IT works to mitigate them.
      • Create a plan for conducting a Social Media Service Audit to stay on top of changing trends.

      Optimize Social Media Strategy by Service Research & Tools

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

      1. Create the right social media service mix

      Understand the different social media services, their unique value propositions for customer interaction, and the content and timing best practices for each.

      • Storyboard: Optimize Social Media Strategy by Service
      • Social Media Service Selection Tool

      2. Execute a plan for social service selection and management

      Leverage different social media services to create a market coverage model and assign responsibilities.

      3. Perform a semi-annual social media service audit

      Conduct an audit to stay on top of changing trends.

      • Social Media Services Audit Template
      [infographic]

      Contact Tymans Group

      We're here to get your IT Operations performant and resilient

      We have the highest respect for your person. We contact you only with responses to your questions. Our company ethics insist on transparency and honesty.

      Continue reading

      Acquire the Right Hires with Effective Interviewing

      • Buy Link or Shortcode: {j2store}576|cart{/j2store}
      • member rating overall impact: 8.5/10 Overall Impact
      • member rating average dollars saved: $15,749 Average $ Saved
      • member rating average days saved: 2 Average Days Saved
      • Parent Category Name: Attract & Select
      • Parent Category Link: /attract-and-select
      • Scope: Acquiring the best talent relies heavily on an effective interviewing process, which involves the strategic preparation of stakeholders, including interviewers. Asking the most effective questions will draw out the most appropriate information to best assess the candidate. Evaluating the interview process and recording best practices will inspire continuous interviewing improvement within the organization.
      • Challenge: The majority of organizations do not have a solid interviewing process in place, and most interviewers are not practiced at interviewing. This results in many poor hiring decisions, costing the organization in many ways. Upsizing is on the horizon, the competition for good talent is escalating, and distinguishing between a good interviewee and a good candidate fit for a position is becoming more difficult.
      • Pain/Risk: Although properly preparing for and conducting an interview requires additional time on the part of HR, the hiring manager, and all interviewers involved, the long-term benefits of an effective interview process positively affect the organization’s bottom line and company morale.

      Our Advice

      Critical Insight

      • Most interviewers are not as good as they think they are, resulting in many poor hiring decisions. A poor hire can cost an organization up to 15 times the position’s annual salary, as well as hurt employee morale.
      • The Human Resources department needs to take responsibility for an effective interview process, but the business needs to take responsibility for developing its new hire needs, and assessing the candidates using the best questions and the most effective interview types and techniques.
      • All individuals with a stake in the interview process need to invest sufficient time to help define the ideal candidate, understand their roles and decision rights in the process, and prepare individually to interview effectively.
      • There are hundreds of different interview types, techniques, and tools for an organization to use, but the most practiced and most effective is behavioral interviewing.
      • There is no right interview type and technique. Each hiring scenario needs to be evaluated to pick the appropriate type and technique that should be practiced, and the right questions that should be asked.

      Impact and Result

      • Gain insight into and understand the need for a strong interview process.
      • Strategize and plan your organization’s interview process, including how to make up an ideal candidate profile, who should be involved in the process, and how to effectively match interview types, techniques, and questions to assess the ideal candidate attributes.
      • Understand various hiring scenarios, and how an interview process may be modified to reflect your organization’s scenario.
      • Learn about the most common interview types and techniques, when they are appropriate to use, and best practices around using them effectively.
      • Evaluate your interview process and yourself as an interviewer to better inform future candidate interviewing strategy.

      Acquire the Right Hires with Effective Interviewing Research & Tools

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

      1. Implement an effective interview and continuous improvement process

      Acquire the right hire.

      • Storyboard: Acquire the Right Hires with Effective Interviewing

      2. Document all aspects of your interview strategy and plan with stakeholders

      Ensure an effective and seamless interview process.

      • Candidate Interview Strategy and Planning Guide

      3. Recognize common interviewing errors and study best practices to address these errors

      Be an effective interviewer.

      • Screening Interview Template
      • Interview Guide Template
      • Supplement: Quick Fixes to Common Interview Errors
      • Pre-interview Guide for Interviewers
      • Candidate Communication Template
      [infographic]

      Get Started With FinOps

      • Buy Link or Shortcode: {j2store}473|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
      • Runaway cloud costs are wrecking the CIO’s budget, but cloud costs are hard to reign in because vendors are not always up front about the true costs, it’s easy to oversubscribe to services and quickly run up costs with pay-as-you-go service, and cloud bills are complex.
      • While IT isn’t the business owner for cloud services, they often carry the cost of overruns on their budget, and don’t have the skills or influence to more effectively manage cloud costs.
      • Truly optimizing cloud spend and maximizing business value from cloud requires insight and collaboration from IT/engineering, finance, and business owners, but those teams are often siloed and manage their cloud usage or spend differently.

      Our Advice

      Critical Insight

      • The business units that need to collaborate to make FinOps work are often siloed, with different processes, data, metrics and cloud expertise. Coordinating their efforts to encourage shared responsibility can be a big obstacle to overcome.
      • FinOps requires a cultural shift to empower every cloud user to take accountability for cloud cost optimization.
      • To get started with FinOps, it’s essential to first break down those silos and get the multiple teams involved on the same page. Everyone must understand how FinOps is part of their responsibilities.

      Impact and Result

      • Implementing FinOps will lead to improved visibility and control over cloud spend, optimized resource allocation and reduced cloud waste, enhanced transparency, improved forecasting and budgeting, and increased accountability over cloud costs across business units.
      • This blueprint will help you get started with FinOps by identifying the roles involved in FinOps, defining the key activities that must be conducted, and assigning ownership to each task. This will help foster a shared responsibility for FinOps and encourage everyone to work toward common goals.

      Get Started With FinOps Research & Tools

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

      1. Get Started With FinOps Deck – A guide to defining and assigning the roles and activities involved in FinOps.

      This storyboard will help you define FinOps roles and structure of the FinOps and other teams, identify key activities, and assign ownership to each. It will also provide guidance on analyzing the results of the RACI chart.

      • Get Started With FinOps Storyboard

      2. FinOps RACI Chart – A tool to help you assess the current state of FinOps activities and assign ownership to each.

      This tool will help you assess the current state of FinOps activities and assign ownership to each activity. Use the outputs of the exercise to define how roles across the organization will be involved in FinOps and where to focus efforts in maturing in FinOps.

      • FinOps RACI Chart
      [infographic]

      Further reading

      Get Started With FinOps

      FinOps goes beyond identifying cloud savings. It empowers every cloud user to maximize the value of their spend.

      Executive Brief

      Analyst Perspective

      The first step of FinOps is collectively realizing that maximizing value is every cloud user's responsibility.

      Natalie Sansone

      Natalie Sansone, PhD
      Research Director, Infrastructure & Operations
      Info-Tech Research Group

      As cloud adoption increases, and with it the complexity of cloud environments, managing and optimizing cloud spend has become both a top challenge and priority for IT organizations. In response, the practice of FinOps has emerged to help organizations maximize the value they get from the cloud. As its popularity surges, organizations are told they must do FinOps, but many feel their practice is not yet mature. One of their biggest obstacles is empowering engineers and other cloud users to work toward this shared goal with other teams.

      To grow and mature your FinOps practice, your first challenge is breaking down silos, encouraging collaboration across varying business units, and getting all cloud users to be accountable for their cloud usage and spend and to understand the shared goals of FinOps. Beyond finding ways to reduce cloud costs, FinOps is a cultural shift that enables better collaboration between distributed teams. It allows them to leverage data to identify opportunities to maximize business value from cloud investments.

      Whether you’re starting the FinOps journey or looking to mature your practice, this blueprint will help you organize by defining the required role and tasks. Then you can work through a collective exercise to ensure everyone understands who is involved and responsible for each activity. You’ll gain the information you need and be better positioned to continuously improve and mature your processes, but success begins with everyone understanding that FinOps is a shared responsibility.

      Executive Summary

      Your Challenge

      Common Obstacles

      Info-Tech’s Approach

      • Runaway cloud costs are wrecking the CIO’s budget, but these are hard to rein in because cloud vendors are not always upfront about the true costs. It’s easy to oversubscribe to services and quickly run up costs with pay-as-you-go service and complex bills.
      • While IT isn’t the business owner for cloud services, they often carry the cost of overruns on their budget, and don’t have the skills or influence to more effectively manage cloud costs.
      • Truly optimizing cloud spend and maximizing its business value requires insight and collaboration from IT/engineering, finance, and business owners, but those teams are often siloed and manage their cloud usage/spend differently.
      • IT leaders are instructed to implement a FinOps practice, but don’t truly understand what that is, who needs to be involved, or where to start.
      • Business units that must collaborate to make FinOps work are often siloed and have different processes, data, metrics, and cloud expertise. Coordinating efforts to encourage shared responsibility can be a challenge. FinOps requires a cultural shift to empower every cloud user to take accountability for cost optimization.
      • Lack of visibility into cloud usage, spending patterns, and cost drivers along with inadequate tools to get the required data to drive decision making. This leads to hindered progress.
      • Implementing FinOps will improve visibility and control over cloud spend, optimize resource allocation and reduce waste, enhance transparency, improve forecasting and budgeting, and improve cost accountability across business units.
      • To get started with FinOps, first it’s essential to break down those silos and coordinate the multiple teams involved. Everyone must understand how FinOps is part of their responsibilities.
      • This blueprint will help you identify the roles involved in FinOps, define the key activities that must be conducted, and assign ownership to each task. This will help foster a shared responsibility for FinOps and encourage everyone to work toward common goals.

      Info-Tech Insight

      FinOps is not just about driving cloud savings. It’s a cultural shift empowering every cloud user to maximize the value of their spend. The first step of FinOps is therefore to help everyone understand their share of responsibility.

      What is FinOps?

      Definition

      “FinOps is an evolving cloud financial management discipline and cultural practice that enables organizations to get maximum business value by helping engineering, finance, technology, and business teams to collaborate on data-driven spending decisions.”

      Definition Updated: November 2021 by the FinOps Foundation Technical Advisory Council

      The ultimate purpose of FinOps is to bring business value to your organization by reducing cloud waste.

      • FinOps is the people, processes, and tools you use to eliminate waste and ensure you get the most value from your cloud spend.
      • FinOps is the framework within which teams can operate to ensure they are optimizing their use of cloud resources.
      • FinOps brings financial accountability to cloud spend.
      • FinOps is a culture practice where everyone collaborates and takes ownership for their cloud usage while being supported and governed by a central group. It breaks down silos so teams that haven’t worked closely together in the past collaborate toward shared goals.
      • It brings financial accountability and cultural change to cloud spend by enabling distributed teams to better collaborate and leverage data to decide where/when to invest in cloud for maximum business value.
      • FinOps is not done by an individual or just one team. It’s a change in the way that many disparate teams work together, from engineering to finance to business teams.

      Common misconceptions about FinOps

      FinOps is not

      FinOps is

      • Only about saving money
      • Only focused on activities related to cost optimization
      • IT financial management, which involves tracking and analyzing all costs associated with IT services
      • An activity (or set of activities) done by one person or team
      • Short for financial operations
      • About maximizing value. FinOps is optimizing cloud costs to provide maximum business value and support scalability (sometimes this means investing more money in cloud)
      • FinOps also involves building a culture of accountability, visibility, and collaboration around cloud usage and cost
      • Focused specifically on managing/optimizing cloud costs
      • A cultural shift around how disparate teams work together, people from all areas of the organization can play a role
      • The term is a portmanteau (combination) of Finance and (Dev)Ops, emphasizing the collaboration between business and engineering teams1
      1 “What is FinOps?” FinOps Foundation, 2023

      FinOps’ popularity has exploded in recent years

      2012 - The practice of FinOps begins to emerge through early scalers in public cloud like Adobe and Intuit

      2017 - Many IT departments begin to use the cloud for limited use cases, but very few enterprises are all in the cloud

      2019 - Many companies begin moving to a cloud-first strategy, shifting IT spend from capital to operational expenditure (CapEx to OpEx), complicating cloud bills

      February 2019 - The FinOps Foundation is born out of Cloudability’s Customer Advisory Board meeting where many cloud practitioners discuss the need for a community of practitioners

      June 2020 - The FinOps Foundation merges with Linux Foundation and sets the standard for cloud financial management

      Sources: Carr, 2022; Linux Foundation, 2023, Storment & Fuller, 2023.

      The image contains a graph that demonstrates the increasing number of people listing FinOps as a skill.

      Where did the term come from?

      The term FinOps has risen in popularity over the last few years. Originally, organizations used the term cloud cost management, then cloud cost optimization, then more broadly, cloud financial management. The latter has now been largely replaced by FinOps.

      Why is FinOps so essential? (1/2)

      The shift from fixed to variable spend has changed the way organizations must manage and report on costs.

      In the traditional data center era:

      • The enterprise procured infrastructure through large capital refreshes of data center hardware.
      • Infrastructure teams tried their best to avoid running out of storage before the next hardware refresh. Equipment was intentionally oversized to accommodate unexpected growth.
      • IT teams would not worry about how much infrastructure resources they consumed, provided they stayed within planned capacity limits. If capacity ran low, resource usage would be adjusted.
      • The business might not like laying out large capital expenditures, but it had full visibility into the cost and got to approve spending in advance using financial controls.
      • Monthly costs were well-understood and monthly or infrequent reporting was acceptable because day-to-day costs did not vary.
      • Mature organizations might chargeback or showback costs to application teams based on number of virtual machines or other measures, but traditional on-premises chargeback wouldn't save money overall.

      Why is FinOps so essential? (2/2)

      The shift from fixed to variable spend has changed the way organizations must manage and report on costs.

      In the cloud era:

      • Infrastructure resources must no longer be provisioned in advance through spending capital budgets.
      • Capacity management isn’t a major concern. Spare capacity is always available, and savings can result from not paying for unnecessary capacity.
      • Cloud services often offer pay-as-you-go pricing models, allowing more control and flexibility to pay only for the resources you consume.
      • When services use more resources than they need, running costs increase. Cost reductions are realized through reducing the size of allocated resources.
      • The variable consumption model can reduce operating costs but can make budgeting and forecasting difficult. IT and the business can no longer predict what they will pay for infrastructure resources.
      • Billing is no longer straightforward and monthly. Resources are individually charged in micro amounts. Costs must be regularly reviewed as unexpected or forgotten resource usage can add up significantly.

      Managing cloud spend remains a challenge for many organizations

      Given the variable nature of cloud costs and complex pricing structures, it can be easy to overspend without mature FinOps processes in place. Indeed, 82% of organizations cite managing cloud spend as one of their top challenges.

      Respondents reported that public cloud spend was over budget by an average of 18%, up from 13% the previous year.

      Source: Flexera 2023 State of the Cloud Report, n=750

      Organization's top cloud challenges.

      While FinOps adoption has rapidly increased, maturity has not

      Most organizations understand the value of FinOps but are not mature in their practice.

      NetApp’s 2023 State of CloudOps Report found that:

      96% say FinOps is important to their cloud strategy

      9% have a mature FinOps practice

      92% report that they struggle with FinOps

      Source: NetApp, 2023 State of CloudOps Report, n=310 IT decision makers in the United States responsible for public cloud infrastructure investments.

      Flexera’s 2023 State of the Cloud report found that 72% of organizations have a dedicated FinOps team.

      Flexera’s annual report also found that year over year, cloud cost responsibilities are increasingly shifting away from Finance/Accounting and Vendor Management teams and over to FinOps teams as they emerge and mature.

      Source: Flexera, 2023 State of the Cloud Report, n=750 decision-makers and users around the world

      Jump Start Your Vendor Management Initiative

      • Buy Link or Shortcode: {j2store}211|cart{/j2store}
      • member rating overall impact: 9.4/10 Overall Impact
      • member rating average dollars saved: $137,332 Average $ Saved
      • member rating average days saved: 31 Average Days Saved
      • Parent Category Name: Vendor Management
      • Parent Category Link: /vendor-management
      • Each year, IT organizations spend more money “outsourcing” tasks, activities, applications, functions, and other items.
      • The increased spend and associated outsourcing leads to less control, and more risk for IT organizations. Managing this becomes a higher priority for IT, but many IT organizations are ill-equipped to do this proactively.

      Our Advice

      Critical Insight

      • Vendor management is not “plug and play” – each organization’s vendor management initiative (VMI) needs to fit its culture, environment, and goals. There are commonalites among vendor management initiatives, but the key is to adapt vendor management principles to fit your needs, not the other way around.
      • All vendors are not of equal importance to an organization. Internal resources are a scarce commodity and should be deployed so that they provide the best return on the organization’s investment. Classifying or segmenting your vendors allows you to focus your efforts on the most important vendors first, allowing your VMI to have the greatest impact possible.
      • Having a solid foundation is critical to the VMI’s ongoing success. Whether you will be creating a formal vendor management office or using vendor management techniques, tools, and templates “informally,” starting with the basics is essential. Make sure you understand why the VMI exists and what it hopes to achieve, what is in and out of scope for the VMI, what strengths the VMI can leverage and the obstacles it will have to address, and how it will work with other areas within your organization.

      Impact and Result

      • Build and implement a vendor management initiative tailored to your environment.
      • Create a solid foundation to sustain your vendor management initiative as it evolves and matures.
      • Leverage vendor management-specific tools and templates to manage vendors more proactively and improve communication.
      • Concentrate your vendor management resources on the right vendors.
      • Build a roadmap and project plan for your vendor management journey to ensure you reach your destination.
      • Build collaborative relationships with critical vendors.

      Jump Start Your Vendor Management Initiative Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should jump start a vendor management initiative, 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. Plan

      Organize your VMI and document internal processes, relationships, roles, and responsibilities. The main outcomes from this phase are organizational documents, a baseline VMI maturity level, and a desired future state for the VMI.

      • Jump Start Your Vendor Management Initiative – Phase 1: Plan
      • Jump – Phase 1 Tools and Templates Compendium

      2. Build

      Configure and create the tools and templates that will help you run the VMI. The main outcomes from this phase are a clear understanding of which vendors are important to you, the tools to manage the vendor relationships, and an implementation plan.

      • Jump Start Your Vendor Management Initiative – Phase 2: Build
      • Jump – Phase 2 Tools and Templates Compendium
      • Jump – Phase 2 Vendor Classification Tool
      • Jump – Phase 2 Vendor Risk Assessment Tool

      3. Run

      Begin operating the VMI. The main outcomes from this phase are guidance and the steps required to implement your VMI.

      • Jump Start Your Vendor Management Initiative – Phase 3: Run

      4. Review

      Identify what the VMI should stop doing, start doing, and continue doing as it improves and matures. The main outcomes from this phase are ways to advance the VMI and maintain internal alignment.

      • Jump Start Your Vendor Management Initiative – Phase 4: Review

      Infographic

      Workshop: Jump Start Your Vendor Management Initiative

      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 Plan

      The Purpose

      Getting Organized

      Key Benefits Achieved

      Defined Roles and Goals for the VMI

      Activities

      1.1 Mission Statement and Goals

      1.2 Scope

      1.3 Strengths and Obstacles

      1.4 Roles and Responsibilities – OIC Chart

      1.5 Process Mapping

      1.6 Vendor Inventory Tool (Overview)

      Outputs

      Completed Mission Statement and Goals

      List of Items In Scope and Out of Scope for the VMI

      List of Strengths and Obstacles for the VMI

      Completed OIC Chart

      Sample Process Map for One Process

      Begun Using Vendor Inventory Tool

      2 Plan/Build/Run

      The Purpose

      Build VMI Tools and Templates

      Key Benefits Achieved

      Configured Tools and Templates for the VMI Based on Its Roles and Goals

      Activities

      2.1 Maturity Assessment

      2.2 Structure and Job Descriptions

      2.3 Attributes of a Valuable Vendor

      2.4 Classification Model

      2.5 Risk Assessment Tool

      2.6 Scorecards and Feedback

      2.7 Business Alignment Meeting Agenda

      Outputs

      Completed Maturity Assessment.

      Sample Job Descriptions and Phrases.

      List of Attributes of a Valuable Vendor.

      Configured Classification Model.

      Configured Risk Assessment Tool.

      Configured Scorecard and Feedback Questions.

      Configured Business Alignment Meeting Agenda.

      3 Build/Run

      The Purpose

      Continue Building VMI Tools and Templates

      Key Benefits Achieved

      Configured Tools and Templates for the VMI Based on Its Roles and Goals

      Activities

      3.1 Relationship Alignment Document

      3.2 Vendor Orientation

      3.3 Policies and Procedures

      3.4 3-Year Roadmap

      3.5 90-Day Plan

      3.6 Quick Wins

      3.7 Reports

      3.8 Kickoff Meeting

      Outputs

      Relationship Alignment Document Sample and Checklist

      Vendor Orientation Checklist

      Policies and Procedures Checklist

      Completed 3-Year Roadmap

      Completed 90-Day Plan

      List of Quick Wins

      List of Reports

      4 Review

      The Purpose

      Review the Past 12 Months of VMI Operations and Improve

      Key Benefits Achieved

      Keeping the VMI Aligned With the Organization’s Goals and Ensuring the VMI Is Leveraging Leading Practices

      Activities

      4.1 Develop/Improve Vendor Relationships.

      4.2 Assess Compliance.

      4.3 Incorporate Leading Practices.

      4.4 Leverage Lessons Learned.

      4.5 Maintain Internal Alignment.

      4.6 Update Governances.

      Outputs

      Further reading

      Jump Start Your Vendor Management Initiative

      Create and implement a vendor management framework to begin obtaining measurable results in 90 days.

      EXECUTIVE BRIEF

      Analyst Perspective

      What is vendor management?

      When you read the phrase “vendor management,” what comes to mind? This isn’t a rhetorical question. Take your time … I’ll wait.

      Unfortunately, those words conjure up a lot of different meanings, and much of that depends on whom you ask. Those who work in the vendor management field will provide a variety of answers. To complicate matters, those who are vendor management “outsiders” will have a totally different view of what vendor management is. Why is this important? Because we need a common definition to communicate more effectively, even if the definition is broad.

      Let’s start creating a working definition that is not circular. Vendor management is not simply managing vendors. That expression basically reorders the words and does nothing to advance our cause; it only adds to the existing confusion surrounding the concept.

      Vendor management is best thought of as a spectrum or continuum with many points rather than a specific discipline like accounting or finance. There are many functions and activities that fall under the umbrella term of vendor management: some of them will be part of your vendor management initiative (VMI), some will not, and some will exist in your organization but be outside the VMI. This is the unique part of vendor management – the part that makes it fun, but also the part that leads to the confusion. For example, accounts payable sits within the accounting department almost exclusively, but contract management can sit within or outside the VMI. The beauty of vendor management is its flexibility; your VMI can be created to meet your specific needs and goals while leveraging common vendor management principles.

      Every conversation around vendor management needs to begin with “What do you mean by that?” Only then can we home in on the scope and nature of what people are discussing. “Managing vendors” is too narrow because it often ignores many of the reasons organizations create VMIs in the first place: to reduce costs, to improve performance, to improve processes, to improve relationships, to improve communication, and to manage risk better.

      Vendor management is a strategic initiative that takes the big picture into account … navigating the cradle to grave lifecycle to get the most out of your interactions and relationships with your vendors. It is flexible and customizable; it is not plug and play or overly prescriptive. Tools, principles, templates, and concepts are adapted rather than adopted as is. Ultimately, you define what vendor management is for your organization.

      We look forward to helping you on your vendor management journey no matter what it looks like. But first, let’s have a conversation about how you want to define vendor management in your environment.

      This is a picture of Phil Bode, Principal  Research Director, Vendor Management at Info-Tech Research Group.

      Phil Bode
      Principal Research Director, Vendor Management
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      Each year, IT organizations “outsource” tasks, activities, functions, and other items. During 2021:

      • Spend on as-a-service providers increased 38% over 2020.*
      • Spend on managed service providers increased 16% over 2020.*
      • IT service providers increased their merger and acquisition numbers by 47% over 2020.*

      *Source: Information Services Group, Inc., 2022.

      This leads to more spend, less control, and more risk for IT organizations. Managing this becomes a higher priority for IT, but many IT organizations are ill-equipped to do this proactively.

      Common Obstacles

      As new contracts are negotiated and existing contracts are renegotiated or renewed, there is a perception that the contracts will yield certain results, output, performance, solutions, or outcomes. The hope is that these will provide a measurable expected value to IT and the organization. Oftentimes, much of the expected value is never realized. Many organizations don’t have a VMI to help:

      • Ensure at least the expected value is achieved.
      • Improve on the expected value through performance management.
      • Significantly increase the expected value through a proactive VMI.

      Info-Tech’s Approach

      Vendor management is a proactive, cross-functional lifecycle. It can be broken down into four phases:

      • Plan
      • Build
      • Run
      • Review

      The Info-Tech process addresses all four phases and provides a step-by-step approach to configure and operate your VMI. The content in this blueprint helps you quickly establish your VMI and set a solid foundation for its growth and maturity.

      Info-Tech Insight

      Vendor management is not a one-size-fits-all initiative. It must be configured:

      • For your environment, culture, and goals.
      • To leverage the strengths of your organization and personnel.
      • To focus your energy and resources on your critical vendors.

      Executive Summary

      Your Challenge

      Spend on managed service providers and as-a-service providers continues to increase. In addition, IT services vendors continue to be active in the mergers and acquisitions arena. This increases the need for a VMI to help with the changing IT vendor landscape. In 2021, there was increases of:

      38%

      Spend on As-a-Service Providers

      16%

      Spend on Managed Services Providers

      47%

      IT Services Merger & Acquisition Growth (Transactions)

      Source: Information Services Group, Inc., 2022.

      Executive Summary

      Common Obstacles

      When organizations execute, renew, or renegotiate a contract, there is an “expected value” associated with that contract. Without a robust VMI, most of the expected value will never be realized. With a robust VMI, the realized value significantly exceeds the expected value during the contract term.

      A contract’s realized value with and without a vendor management initiative

      Two bars are depicted, showing that vendor collaboration and vendor performance management exceed expected value with a VMI, but without VMI, 75% of a contract's expected value can disappear within 18 months.

      Source: Based on findings from Geller & Company, 2003.

      Executive Summary

      Info-Tech’s Approach

      A sound, cyclical approach to vendor management will help you create a VMI that meets your needs and stays in alignment with your organization as they both change (i.e. mature and grow).

      This is an image of Info-Tech's approach to VMI.  It includes the following four steps: 01 - Plan; 02 - Build; 03 - Run; 04 - Review

      Info-Tech’s Methodology for Creating and Operating Your VMI

      Phase 1: Plan Phase 2: Build Phase 3: Run Phase 4: Review

      Phase Steps

      1.1 Mission Statement and Goals
      1.2 Scope
      1.3 Strengths and Obstacles
      1.4 Roles and Responsibilities
      1.5 Process Mapping
      1.6 Charter
      1.7 Vendor Inventory
      1.8 Maturity Assessment
      1.9 Structure

      2.1 Classification Model
      2.2 Risk Assessment Tool
      2.3 Scorecards and Feedback
      2.4 Business Alignment Meeting Agenda
      2.5 Relationship Alignment Document
      2.6 Vendor Orientation
      2.7 Job Descriptions
      2.8 Policies and Procedures
      2.9 3-Year Roadmap
      2.10 90-Day Plan
      2.11 Quick Wins
      2.12 Reports

      3.1 Classify Vendors
      3.2 Conduct Internal “Kickoff” Meeting
      3.3 Conduct Vendor Orientation
      3.4 Compile Scorecards
      3.5 Conduct Business Alignment Meetings
      3.6 Work the 90-Day Plan
      3.7 Manage the 3-Year Roadmap
      3.8 Measure and Monitor Risk
      3.9 Issue Reports
      3.10 Develop/Improve Vendor Relationships
      3.11 Contribute to Other Processes

      4.1 Assess Compliance
      4.2 Incorporate Leading Practices
      4.3 Leverage Lessons Learned
      4.4 Maintain Internal Alignment
      4.5 Update Governances

      Phase Outcomes

      This phase helps you organize your VMI and document internal processes, relationships, roles, and responsibilities. The main outcomes from this phase are organizational documents, a baseline VMI maturity level, and a desired future state for the VMI. This phase helps you configure and create the tools and templates that will help you run the VMI. The main outcomes from this phase are a clear understanding of which vendors are important to you, the tools to manage the vendor relationships, and an implementation plan. This phase helps you begin operating the VMI. The main outcomes from this phase are guidance and the steps required to implement your VMI. This phase helps the VMI identify what it should stop doing, start doing, and continue doing as it improves and matures. The main outcomes from this phase are ways to advance the VMI and maintain internal alignment.

      Insight Summary

      Insight 1

      Vendor management is not “plug and play” – each organization’s vendor management initiative (VMI) needs to fit its culture, environment, and goals. While there are commonalities and leading practices associated with vendor management, your initiative won’t look exactly like another organization’s. The key is to adapt vendor management principles to fit your needs.

      Insight 2

      All vendors are not of equal importance to your organization. Internal resources are a scarce commodity and should be deployed so that they provide the best return on the organization’s investment. Classifying or segmenting your vendors allows you to focus your efforts on the most important vendors first, allowing your VMI to have the greatest impact possible.

      Insight 3

      Having a solid foundation is critical to the VMI’s ongoing success. Whether you will be creating a formal vendor management office or using vendor management techniques, tools, and templates “informally,” starting with the basics is essential. Make sure you understand why the VMI exists and what it hopes to achieve, what is in and out of scope for the VMI, what strengths the VMI can leverage and the obstacles it will have to address, and how it will work with other areas within your organization.

      Blueprint Deliverables

      The four phases of creating and running a vendor management initiative are supported with configurable tools, templates, and checklists to help you stay aligned internally and achieve your goals.

      VMI Tools and Templates

      This image contains two screenshots of Info-Tech's VMI Tools and Templates

      Build a solid foundation for your VMI and configure tools and templates to help you manage your vendor relationships.

      Key Deliverables:

      1. Jump – Phase 1 Tools and Templates Compendium
      2. Jump – Phase 2 Tools and Templates Compendium
      3. Jump – Phase 2 Vendor Classification Tool
      4. Jump – Phase 2 Vendor Risk Assessment Tool

      A suite of tools and templates to help you create and implement your vendor management initiative.

      Blueprint benefits

      IT Benefits

      • Identify and manage risk proactively.
      • Reduce costs and maximize value.
      • Increase visibility with your critical vendors.
      • Improve vendor performance.
      • Create a collaborative environment with key vendors.
      • Segment vendors to allocate resources more effectively and more efficiently.

      Business Benefits

      • Improve vendor accountability.
      • Increase collaboration between departments.
      • Improve working relationships with your vendors.
      • Create a feedback loop to address vendor or customer issues before they get out of hand or are more costly to resolve.
      • Increase access to meaningful data and information regarding important vendors.

      Establish Baseline Metrics

      Baseline metrics will be improved through:

      Using the Maturity Assessment and 90-Day Plan tools, track how well you are able to achieve your goals and objectives:

      • Did you meet the targeted maturity level for each maturity category as determined by the point system?
      • Did you finish each activity in the 90-Day Plan completely and on time?
      1-Year Maturity Roadmap(by Category) Target Maturity (Total Points) Actual Maturity (Total Points)
      Contracts 12 12
      Risk 8 7
      Vendor Selection 9 9
      Vendor Relationships 21 21
      VMI Operations 24 16
      90-Day Plan (by Activity) Activity Completed
      Finalize mission and goals; gain executive approval Yes
      Finalize OIC chart; gain buy-in from other departments Yes
      Classify top 40 vendors by spend Yes
      Create initial scorecard Yes
      Develop the business alignment meeting agenda Yes
      Conduct two business alignment meetings No
      Update job descriptions Yes
      Map two VMI processes No

      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 Phases 2 & 3 Phase 4

      Call #1: Mission statement and goals, scope, and strengths and obstacles.

      Call #5: Classification model.

      Call #9: Policies and procedures and reports.

      Call #12: Assess compliance, incorporate leading practices, leverage lessons learned, maintain internal alignment, and update governances.

      Call #2: Roles and responsibilities and process mapping.

      Call #6: Risk assessment.

      Call #10: 3-year roadmap.

      Call #3: Charter and vendor inventory.

      Call #7: Scorecards and feedback and business alignment meetings.

      Call #11: 90-day plan and quick wins.

      Call #4: Maturity assessment and VMI structure.

      Call #8: Relationship alignment document, vendor orientation, and job descriptions.

      Workshop Overview

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

      Day 1 Day 2 Day 3 Day 4
      Plan Plan/Build/Run Build/Run Review

      Activities

      1.1 Mission Statement and Goals
      1.2 Scope
      1.3 Strengths and Obstacles
      1.4 Roles and Responsibilities
      1.5 Process Mapping
      1.6 Charter
      1.7 Vendor Inventory
      1.8 Maturity Assessment
      1.9 Structure

      2.1 Classification Model
      2.2 Risk Assessment Tool
      2.3 Scorecards and Feedback
      2.4 Business Alignment Meeting Agenda
      2.5 Relationship Alignment Document
      2.6 Vendor Orientation
      2.7 Job Descriptions
      2.8 Policies and Procedures
      2.9 3-Year Roadmap
      2.10 90-Day Plan
      2.11 Quick Wins
      2.12 Reports

      3.1 Classify Vendors
      3.2 Conduct Internal “Kickoff” Meeting
      3.3 Conduct Vendor Orientation
      3.4 Compile Scorecards
      3.5 Conduct Business Alignment Meetings
      3.6 Work the 90-Day Plan
      3.7 Manage the 3-Year Roadmap
      3.8 Measure and Monitor Risk
      3.9 Issue Reports
      3.10 Develop/Improve Vendor Relationships
      3.11 Contribute to Other Processes

      4.1 Assess Compliance
      4.2 Incorporate Leading Practices
      4.3 Leverage Lessons Learned
      4.4 Maintain Internal Alignment
      4.5 Update Governances

      Deliverables

      1. Completed Mission Statement and Goals
      2. List of Items In Scope and Out of Scope for the VMI
      3. List of Strengths and Obstacles for the VMI
      4. Completed OIC Chart
      5. Sample Process Map for One Process
      6. Vendor Inventory tab
      1. Completed Maturity Assessment
      2. Sample Job Descriptions and Phrases
      3. List of Attributes of a Valuable Vendor
      4. Configured Classification Model
      5. Configured Risk Assessment Tool
      6. Configured Scorecard and Feedback Questions
      7. Configured Business Alignment Meeting Agenda
      1. Relationship Alignment Document Sample and Checklist
      2. Vendor Orientation Checklist
      3. Policies and Procedures Checklist
      4. Completed 3-Year Roadmap
      5. Completed 90-Day Plan
      6. List of Quick Wins
      7. List of Reports

      Phase 1: Plan

      Get Organized

      1.1 Mission Statement and Goals
      1.2 Scope
      1.3 Strengths and Obstacles
      1.4 Roles and Responsibilities
      1.5 Process Mapping
      1.6 Charter
      1.7 Vendor Inventory
      1.8 Maturity Assessment
      1.9 Structure

      Phase 1 Phase 2 Phase 3 Phase 4
      1.1 Mission Statement and Goals
      1.2 Scope
      1.3 Strengths and Obstacles
      1.4 Roles and Responsibilities
      1.5 Process Mapping
      1.6 Charter
      1.7 Vendor Inventory
      1.8 Maturity Assessment
      1.9 Structure

      2.1 Classification Model
      2.2 Risk Assessment Tool
      2.3 Scorecards and Feedback
      2.4 Business Alignment Meeting Agenda
      2.5 Relationship Alignment Document
      2.6 Vendor Orientation
      2.7 Job Descriptions
      2.8 Policies and Procedures
      2.9 3-Year Roadmap
      2.10 90-Day Plan
      2.11 Quick Wins
      2.12 Reports

      3.1 Classify Vendors
      3.2 Conduct Internal “Kickoff” Meeting
      3.3 Conduct Vendor Orientation
      3.4 Compile Scorecards
      3.5 Conduct Business Alignment Meetings
      3.6 Work the 90-Day Plan
      3.7 Manage the 3-Year Roadmap
      3.8 Measure and Monitor Risk
      3.9 Issue Reports
      3.10 Develop/Improve Vendor Relationships
      3.11 Contribute to Other Processes

      4.1 Assess Compliance
      4.2 Incorporate Leading Practices
      4.3 Leverage Lessons Learned
      4.4 Maintain Internal Alignment
      4.5 Update Governances

      This phase will walk you through the following activities:

      Organize your VMI and document internal processes, relationships, roles, and responsibilities. The main outcomes from this phase are organizational documents, a baseline VMI maturity level, and a desired future state for the VMI.

      This phase involves the following participants:

      • VMI team
      • Applicable stakeholders and executives
      • Procurement/Sourcing
      • IT
      • Others as needed

      Jump Start Your Vendor Management Initiative

      Phase 1: Plan

      Get organized.

      Phase 1: Plan focuses on getting organized. Foundational elements (mission statement, goals, scope, strengths and obstacles, roles and responsibilities, and process mapping) will help you define your VMI. These and the other elements of this Phase will follow you throughout the process of standing up your VMI and running it.

      Spending time up front to ensure that everyone is on the same page will help avoid headaches down the road. The tendency is to skimp (or even skip) on these steps to get to “the good stuff.” To a certain extent, the process provided here is like building a house. You wouldn’t start building your dream home without having a solid blueprint. The same is true with vendor management. Leveraging vendor management tools and techniques without the proper foundation may provide some benefit in the short term, but in the long term it will ultimately be a house of cards waiting to collapse.

      Step 1.1: Mission statement and goals

      Identify why the VMI exists and what it will achieve.

      Whether you are starting your vendor management journey or are already down the path, it is important to know why the vendor management initiative exists and what it hopes to achieve. The easiest way to document this is with a written declaration in the form of a mission statement and goals. Although this is the easiest way to proceed, it is far from easy.

      The mission statement should identify at a high level the nature of the services provided by the VMI, who it will serve, and some of the expected outcomes or achievements. The mission statement should be no longer than one or two sentences.

      The complement to the mission statement is the list of goals for the VMI. Your goals should not be a reassertion of your mission statement in bullet format. At this stage it may not be possible to make them SMART (Specific, Measurable, Achievable/Attainable, Relevant, Time-Bound/Time-Based), but consider making them as SMART as possible. Without some of the SMART parameters attached, your goals are more like dreams and wishes. At a minimum, you should be able to determine the level of success achieved for each of the VMI goals.

      Although the VMI’s mission statement will stay static over time (other than for significant changes to the VMI or organization as a whole), the goals should be re-evaluated periodically using a SMART filter and adjusted as needed.

      1.1.1: Mission statement and goals

      20-40 minutes

      1. Meet with the participants and use a brainstorming activity to list on a whiteboard or flip chart the reasons why the VMI will exist.
      2. Review external mission statements for inspiration.
      3. Review internal mission statements from other areas to ensure consistency.
      4. Draft and document your mission statement in the Phase 1 Tools and Templates Compendium, Tab 1.1 Mission Statement and Goals.
      5. Continue brainstorming and identify the high-level goals for the VMI.
      6. Review the list of goals and make them as SMART (Specific, Measurable, Achievable/Attainable, Relevant, Time-Bound/Time-Based) as possible.
      7. Document your goals in the Phase 1 Tools and Templates Compendium, Tab 1.1 Mission Statement and Goals.
      8. Obtain sign-off on the mission statement and goals from stakeholders and executives as required.

      Input

      • Brainstorming results
      • Mission statements from other internal and external sources

      Output

      • Completed mission statement and goals

      Materials

      • Whiteboard/Flip Charts
      • Jump – Phase 1 Tools and Templates Compendium, Tab 1.1 Mission Statement and Goals

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Step 1.2: Scope

      Determine what is in scope and out of scope for the VMI

      Regardless of where your VMI resides or how it operates, it will be working with other areas within your organization. Some of the activities performed by the VMI will be new and not currently handled by other groups or individuals internally; at the same time, some of the activities performed by the VMI may be currently handled by other groups or individuals internally. In addition, executives, stakeholders, and other internal personnel may have expectations or make assumptions about the VMI. As a result, there can be a lot of confusion about what the VMI does and doesn’t do, and the answers cannot always be found in the VMI’s mission statement and goals.

      One component of helping others understand the VMI landscape is formalizing the VMI scope. The scope will define boundaries for the VMI. The intent is not to fence itself off and keep others out but provide guidance on where the VMI’s territory begins and ends. Ultimately, this will help clarify the VMI’s roles and responsibilities, improve workflow, and reduce errant assumptions.

      When drafting your VMI scoping document, make sure you look at both sides of the equation (similar to what you would do when following best practices for a statement of work): Identify what is in scope and what is out of scope. Be specific when describing the individual components of the VMI scope, and make sure executives and stakeholders are on board with the final version.

      1.2.1: Scope

      20-40 minutes

      1. Meet with the participants and use a brainstorming activity to list on a whiteboard or flip chart the activities and functions in scope and out of scope for the VMI.
        1. Be specific to avoid ambiguity and improve clarity.
        2. Go back and forth between in scope and out of scope as needed; it is not necessary to list all of the in-scope items and then turn your attention to the out-of-scope items.
      2. Review the lists to make sure there is enough specificity. An item may be in scope or out of scope but not both.
      3. Use the Phase 1 Tools and Templates Compendium, Tab 1.2 Scope, to document the results.
      4. Obtain sign-off on the scope from stakeholders and executives as required.

      Input

      • Brainstorming
      • Mission statement and goals

      Output

      • Completed list of items in and out of scope for the VMI

      Materials

      • Whiteboard/Flip Charts
      • Jump – Phase 1 Tools and Templates Compendium, Tab 1.2 Scope

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Step 1.3: Strengths and obstacles

      Pinpoint the VMI’s strengths and obstacles.

      A SWOT analysis (strengths, weaknesses, opportunities, and threats) is a valuable tool, but it is overkill for your VMI at this point. However, using a modified and simplified form of this tool (strengths and obstacles) will yield significant results and benefit the VMI as it grows and matures.

      Your output will be two lists: the strengths associated with the VMI and the obstacles facing the VMI. For example, strengths could include items such as smart people working within the VMI and executive support. Obstacles could include items such as limited headcount and training required for VMI staff.

      The goals are 1) to harness the strengths to help the VMI be successful and 2) to understand the impact of the obstacles and plan accordingly. The output can also be used to enlighten executives and stakeholders about the challenges associated with their directives or requests (e.g. human bandwidth may not be sufficient to accomplish some of the vendor management activities and there is a moratorium on hiring until the next budget year).

      For each strength identified, determine how you will or can leverage it when things are going well or when the VMI is in a bind. For each obstacle, list the potential impact on the VMI (e.g. scope, growth rate, and number of vendors that can actively be part of the VMI).

      As you do your brainstorming, be as specific as possible and validate your lists with stakeholders and executives as needed.

      1.3.1: Strengths and obstacles

      20-40 minutes

      1. Meet with the participants and use a brainstorming activity to list on a whiteboard or flip chart the VMI’s strengths and obstacles.
        1. Be specific to avoid ambiguity and improve clarity.
        2. Go back and forth between strengths and obstacles as needed; it is not necessary to list all of the strengths and then turn your attention to the obstacles.
        3. It is possible for an item to be a strength and an obstacle; when this happens, add details to distinguish the situations.
      2. Review the lists to make sure there is enough specificity.
      3. Determine how you will leverage each strength and how you will manage each obstacle.
      4. Use the Phase 1 Tools and Templates Compendium, Tab 1.3 Strengths and Obstacles, to document the results.
      5. Obtain sign-off on the strengths and obstacles from stakeholders and executives as required.

      Download the Info-Tech Jump – Phase 1 Tools and Templates Compendium

      Input

      • Brainstorming
      • Mission statement and goals
      • Scope

      Output

      • Completed list of items impacting the VMI’s ability to be successful: strengths the VMI can leverage and obstacles the VMI must manage

      Materials

      • Whiteboard/Flip Charts
      • Jump – Phase 1 Tools and Templates Compendium, Tab 1.3 Strengths and Obstacles

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Step 1.4: Roles and responsibilities

      Obtain consensus on who is responsible for what.

      One crucial success factor for VMIs is gaining and maintaining internal alignment. There are many moving parts to an organization, and a VMI must be clear on the various roles and responsibilities related to the relevant processes. Some of this information can be found in the VMI’s scope, referenced in Step 1.2, but additional information is required to avoid stepping on each other’s toes since many of the processes require internal departments to work together. (For example, obtaining requirements for a request for proposal takes more than one person or one department to complete this process.) While it is not necessary to get too granular, it is imperative that you have a clear understanding of how the VMI activities will fit within the larger vendor management lifecycle (which is comprised of many sub processes) and who will be doing what.

      As we have learned through our workshops and guided implementations, a traditional RACI* or RASCI* chart does not work well for this purpose. These charts are not intuitive, and they lack the specificity required to be effective. For vendor management purposes, a higher-level view and a slightly different approach provide much better results.

      This step will lead your through the creation of an OIC* chart to determine vendor management lifecycle roles and responsibilities. Afterward, you’ll be able to say, “Oh, I see clearly who is involved in each part of the process and what their role is.”

      *RACI – Responsible, Accountable, Consulted, Informed
      *RASCI – Responsible, Accountable, Support, Consulted, Informed
      *OIC – Owner, Informed, Contributor

      This is an image of a table which shows an example of which role would be responsible for which step

      Step 1.4: Roles and responsibilities (cont.)

      Obtain consensus on who is responsible for what.

      To start, define the vendor management lifecycle steps or process applicable to your VMI. Next, determine who participates in the vendor management lifecycle. There is no need to get too granular – think along the lines of departments, subdepartments, divisions, agencies, or however you categorize internal operational units. Avoid naming individuals other than by title; this typically happens when a person oversees a large group (e.g. the CIO [chief information officer] or the CPO [chief procurement officer]). Be thorough, but the chart can get out of hand quickly. For each role and step of the lifecycle, ask whether the entry is necessary – does it add value to the clarity of understanding the responsibilities associated with the vendor management lifecycle? Consider two examples, one for roles and one for lifecycle steps: 1) Is IT sufficient or do you need IT Operations and IT Development? 2) Is “negotiate contract documents” sufficient or do you need “negotiate the contract” and “negotiate the renewal”? The answer will always depend on your culture and environment, but be wary of creating a spreadsheet that requires an 85-inch monitor to view it in its entirety.

      After defining the roles (departments, divisions, agencies) and the vendor management lifecycle steps or process, assign one of three letters to each box in your chart:

      • O – Owner – who owns the process; they may also contribute to it.
      • I – Informed – who is informed about the progress or results of the process.
      • C – Contributor – who contributes or works on the process; it can be tangible or intangible contributions.

      This activity can be started by the VMI or done as a group with representatives from each of the named roles. If the VMI starts the activity, the resulting chart should be validated by the each of the named roles.

      1.4.1: Roles and responsibilities

      1-6 hours

      1. Meet with the participants and configure the OIC Chart in the Jump – Phase 1 Tools and Templates Compendium, Tab 1.4 OIC Chart.
        1. Review the steps or activities across the top of the chart and modify as needed.
        2. Review the roles listed along the left side of the chart and modify as needed.
      2. For each activity or step across the top of the chart, assign each role a letter – O for owner of that activity or step; I for informed; or C for contributor. Use only one letter per cell.
      3. Work your way across the chart. Every cell should have an entry or be left blank if it is not applicable.
      4. Review the results and validate that every activity or step has an O assigned to it; there must be an owner for every activity or step.
      5. Obtain sign-off on the OIC chart from stakeholders and executives as required.

      Download the Info-Tech Jump – Phase 1 Tools and Templates Compendium

      Input

      • A list of activities or steps to complete a project, starting with requirements gathering and ending with ongoing risk management
      • A list of internal areas (departments, divisions, agencies, etc.) and stakeholders that contribute to completing a project

      Output

      • Completed OCI chart indicating roles and responsibilities for the VMI and other internal areas

      Materials

      • Jump – Phase 1 Tools and Templates Compendium, Tab 1.4 OIC Chart

      Participants

      • VMI team
      • Procurement/Sourcing
      • IT
      • Representatives from other areas as needed
      • Applicable stakeholders and executives as needed

      Step 1.5: Process mapping

      Diagram the workflow.

      Although policies and procedures are important, their nature can make it difficult to grasp how things work at a high level (or even at the detail level). To help bridge the gap, map the applicable processes (determined by how deep and wide you want to go) involving the VMI. To start, look at the OIC chart from Step 1.4. You can expand the breadth and depth of your mapping to include the VMI scope, the 3-year roadmap (see Step 2.9), and the processes driven by the day-to-day work within the VMI.

      Various mapping tools can be used. Three common approaches that can be mixed and matched are:

      • Traditional flowcharts.
      • Swimlane diagrams.
      • Work breakdown structures.
      This is an example of a Workflow Process Map

      Step 1.5: Process mapping (cont.)

      Diagram the workflow.

      Your goal is not to create an in-depth diagram for every step of the vendor management lifecycle. However, for steps owned by the VMI, the process map should include sufficient details for the owner and the contributors (see Step 1.4) to understand what is required of them to support that step in the lifecycle.

      For VMI processes that don’t interact with other departments, follow the same pattern as outlined above for steps owned by the VMI.

      Whatever methodology you use to create your process map, make sure it includes enough details so that readers and users can identify the following elements:

      • Input:
        • What are the inputs?
        • Where do the inputs originate or come from?
      • Process:
        • Who is involved/required for this step?
        • What happens to the inputs in this step?
        • What additional materials, tools, or resources are used or required during this step?
      • Output:
        • What are the outputs?
        • Where do the outputs go next?

      1.5.1: Process Mapping

      1-8 hours (or more)

      1. Meet with the participants and determine which processes you want to map.
        1. For processes owned by the VMI, map the entire process.
        2. For processes contributed to by the VMI, map the entire process at a high level and map the VMI portion of the process in greater detail.
      2. Select the right charts/diagrams for your output.
        1. Flowchart
        2. Swimlane diagram
        3. Modified SIPOC (Supplier, Input, Process, Output, Customer)
        4. WBS (work breakdown structure)
      3. Begin mapping the processes either in a tool or using sticky notes. You want to be able to move the steps and associated information easily; most people don’t map the entire process accurately or with sufficient detail the first time through. An iterative approach works best.
      4. Obtain signoff on the process maps from stakeholders and executives as required. A copy of the final output can be kept in the Jump – Phase 1 Tools and Templates Compendium, Tab 1.5 Process Mapping, if desired.

      Download the Info-Tech Jump – Phase 1 Tools and Templates Compendium

      Input

      • Existing processes (formal, informal, documented, and undocumented)
      • OIC chart

      Output

      • Process maps for processes contributed to or owned by the VMI

      Materials

      • Sticky Notes
      • Flowchart/process mapping software or something similar
      • (Optional) Jump – Phase 1 Tools and Templates Compendium, Tab 1.5 Process Mapping

      Participants

      • VMI team
      • Procurement/Sourcing
      • IT
      • Representatives from other areas as needed
      • Applicable stakeholders and executives (as needed)

      Step 1.6: Charter

      Document how the VMI will operate.

      As you continue getting organized by working through steps 1.1-1.5, you may want to document your progress in a charter and add some elements. Basically, a charter is a written document laying out how the VMI will operate within the organization. It clearly states the VMI’s mission, goals, scope, roles and responsibilities, and vendor governance model. In addition, it can include a list of team members and sponsors.

      Whether you create a VMI charter will largely depend on:

      • Your organization’s culture.
      • Your organization’s formality.
      • The perceived value of creating a charter.

      If you decide to create a VMI charter, this is a good place in the process to create an initial draft. As you continue working through the blueprint and your VMI matures, update the VMI charter as needed.

      VMI Charter:

      • Purpose
      • Sponsors
      • Roles
      • Responsibilities
      • Governance

      1.6.1: Charter

      1-4 hours

      1. Meet with the participants and review the template in Jump – Phase 1 Tools and Templates Compendium, Tab 1.6 Charter.
      2. Determine whether the participants will use this template or add materials to your standard charter template.
      3. Complete as much of the charter as possible, knowing that some information may not be available until later.
      4. Return to the charter as needed until it is completed.
      5. Obtain sign-off on the charter from stakeholders and executives as required.

      Download the Info-Tech Jump – Phase 1 Tools and Templates Compendium

      Input

      • Mission statement and goals
      • Scope
      • Strengths and obstacles
      • OIC chart
      • List of stakeholders and executives and their VMI roles and responsibilities

      Output

      • Completed VMI charter

      Materials

      • Jump – Phase 1 Tools and Templates Compendium, Tab 1.6 Charter
      • Your organization’s standard charter document

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Step 1.7: Vendor inventory

      Compile a list of vendors and relevant vendor information.

      As you prepare your VMI for being operational, it’s critical to identify all of your current vendors providing IT products or services to the organization. This can be tricky and may depend on how you view things internally. For example, you may have traditional IT vendors that are managed by IT, and you may have IT vendors that are managed by other internal departments (shadow IT or out-in-the-open IT). If it wasn’t determined with the help of stakeholders and executives before now, make sure you establish the purview of the VMI at this point. What types of vendors are included and excluded from the VMI?

      You may find that a vendor can be included and excluded based on the product or service they provide. A vendor may provide a service that is managed by IT and a service that is managed/controlled by another department. In this instance, a good working relationship and clearly defined roles and responsibilities between the VMI and the other department will be required. But, it all starts with compiling a list of vendors and validating the VMI’s purview (and any limitations) for the vendors with stakeholders and executives.

      Step 1.7: Vendor inventory (cont.)

      Compile a list of vendors and relevant vendor information.

      At a minimum, the VMI should be able to quickly retrieve key information about each of “its” vendors:

      • Vendor Name
      • Classification (see Steps 2.1 and 3.1)
      • Categories of Service
      • Names of Products and Services Provided
      • Brief Descriptions of Products and Services Provided
      • Annualized Vendor Spend
      • Vendor Contacts
      • Internal Vendor Relationship Owner

      Not all of this information will be available at this point, but you can begin designing or configuring your tool to meet your needs. As your VMI enters Phase 3: Run and continues to mature, you will return to this tool and update the information. For example, the vendor classification category won’t be known until Phase 3, and it can change over time.

      1.7.1: Vendor inventory

      1-10 hours

      Meet with the participants and review the Jump – Phase 1 Tools and Templates Compendium, Tab 1.7 Vendor Inventory. Determine whether the VMI wants to collect and/or monitor additional information and make any necessary modifications to the tool.

      Enter the “Annual IT Vendor Spend” amount in the appropriate cell toward the top of the spreadsheet. This is for IT spend for vendor-related activities within the VMI’s scope; include shadow IT spend and “non-shadow” IT spend if those vendors will be included in the VMI’s scope.

      Populate the data fields for your top 50 vendors by annual spend; you may need multiple entries for the same vendor depending on the nature of the products and services they provide.

      Ignore the “Classification” column for now; you will return to this later when classification information is available.

      Ignore the “Percentage of IT Budget” column as well; it uses a formula to calculate this information.

      Input

      • Data from various internal and external sources such as accounts payable, contracts, and vendor websites

      Output

      • List of vendors with critical information required to manage relationships with key vendors

      Materials

      • Jump – Phase 1 Tools and Templates Compendium, Tab 1.7 Vendor Inventory

      Participants

      • VMI team (directly)
      • Other internal and external personnel (indirectly)

      Download the Info-Tech Jump – Phase 1 Tools and Templates Compendium

      Step 1.8: Maturity assessment

      Establish a VMI maturity baseline and set an ideal future state.

      Knowing where you are and where you want to go are essential elements for any journey in the physical world, and the same holds true for your VMI journey. Start by assessing your current-state VMI maturity. This will provide you with a baseline to measure progress against. Next, using the same criteria, determine the level of VMI maturity you would like to achieve one year in the future. This will be your future-state VMI maturity. Lastly, identify the gaps and plot your course.

      The maturity assessment provides three main benefits:

      1. Focus – you’ll know what is important to you moving forward.
      2. 3-Year Roadmap (discussed more fully in Step 2.9) – you’ll have additional input for your short-term and long-term roadmap (1, 2, and 3 years out).
      3. Quantifiable Improvement – you’ll be able to measure your progress and make midcourse corrections when necessary.

      Step 1.8: Maturity assessment (cont.)

      Establish a VMI maturity baseline and set an ideal future state.

      The Info-Tech VMI Maturity Assessment tool evaluates your maturity across several criteria across multiple categories. Once completed, the assessment will specify:

      • A current-state score by category and overall.
      • A target-state score by category and overall.
      • A quantifiable gap for each criterion.
      • A priority assignment for each criterion.
      • A level of effort required by criterion to get from the current state to the target state.
      • A target due date by criterion for achieving the target state.
      • A rank order for each criterion (note: limit your ranking to your top 7 or 9).

      Many organizations will be tempted to mature too quickly. Resource constraints and other items from Step 1.3 (Strengths and Obstacles) will impact how quickly you can mature. Being aggressive is fine, but it must be tempered with a dose of reality. Otherwise, morale, perception, and results can suffer.

      1.8.1: Maturity assessment

      45-90 minutes

      1. Meet with the participants and use Jump – Phase 1 Tools and Templates Compendium, Tab 1.8 Maturity Assessment Input, to complete the first part of this activity. Provide the required information indicated below.
        1. Review each statement in column B and enter a value in the “Current” column using the drop-down menus based on how much you disagree or agree (0-4) with the statement. This establishes a baseline maturity.
        2. Repeat this process for the “Future” column using a target date of one year from now to achieve this level. This is your desired maturity.
        3. Enter information regarding priority, level of effort, and target due date in the applicable columns using the drop-down menus. (Priority levels are critical, high, medium, low, and maintain; Levels of Effort are high, medium, and low; Target Due Dates are broken into timelines: 1-3 months, 4-6 months, 7-9 months, and 10-12 months.)
      2. Review the information on Jump – Phase 1 Tools and Templates Compendium, Tab 1.8 Maturity Assessment Output; use the Distribution Tables to help you rank your top priorities. Enter a unique number into the Priority (Rank) column. Limit your ranking to the top 7 to 9 activities to provide focus.

      Input

      • Knowledge of current VMI practices and desired future states

      Output

      • VMI maturity baseline
      • Desired VMI target maturity state (in one year)
      • Prioritized areas to improve and due dates
      • Graphs and tables to identify maturity deltas and track progress

      Materials

      • Jump – Phase 1 Tools and Templates Compendium, Tab 1.8 Maturity Assessment Input
      • Jump – Phase 1 Tools and Templates Compendium, Tab 1.8 Maturity Assessment Output

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Step 1.9: Structure

      Determine the VMI’s organizational and reporting structure.

      There are two parts to the VMI structure:

      1. Organization Structure. Who owns the VMI – where does it fit on the organization chart?
      2. Reporting Structure. What is the reporting structure within the VMI – what are the job functions, titles, and solid and dotted lines of accountability?

      VMI Organization Structure

      The decision regarding who owns the VMI can follow one of two paths:

      1. The decision has already been made by the board of directors, executives, senior leadership, or stakeholders; OR
      2. The decision has not been made, and options will be reviewed and evaluated before it is implemented.

      Many organizations overlook the importance of this decision. The VMI’s position on the organization chart can aid or hinder its success. Whether the decision has already been made or not, this is the perfect time to evaluate the decision or options based on the following question: Why is the VMI being created and how will it operate? Review the documents you created during Steps 1.1-1.8 and other factors to answer this question.

      Step 1.9: Structure (cont.)

      Determine the VMI’s organizational and reporting structure.

      Based on your work product from Steps 1.1-1.8 and other factors, select where the VMI will be best located from the following areas/offices or their equivalent:

      • Chief Compliance Officer (CCO)
      • Chief Information Officer (CIO)
      • Chief Financial Officer (CFO)
      • Chief Procurement Officer (CPO)
      • Chief Operating Officer (COO)
      • Other area

      Without the proper support and placement in the organization chart, the VMI can fail. It is important for the VMI to find a suitable home with a direct connection to one of the sponsors identified above and for the VMI lead to have significant stature (aka title) within the organization. For example, if the VMI lead is a “manager” level who is four reporting layers away from the chief officer/sponsor, the VMI will have an image issue within and outside of the sponsor’s organization (as well as within the vendor community). While this is not to say that the VMI lead should be a vice president* or senior director, our experience and research indicate that the VMI and the VMI lead will be taken more seriously when the VMI lead is at least a director level reporting directly to a CXO.

      *For purposes of the example above, the reporting structure hierarchy used is manager, senior manager, director, senior director, vice president, CXO.

      Step 1.9: Structure (cont.)

      Determine the VMI’s organizational and reporting structure.

      VMI Reporting Structure

      As previously mentioned, the VMI reporting structure describes and identifies the job functions, titles, and lines of accountability. Whether you have a formal vendor management office or you are leveraging the principles of vendor management informally, your VMI reporting structure design will involve some solid lines and some dotted lines. In this instance, the dotted lines represent part-time participation or people/areas that will assist the VMI in some capacity. For example, if the VMI sits within IT, a dotted line to Procurement will show that a good working relationship is required for both parties to succeed; or a dotted line to Christina in Legal will indicate that Christina will be helping the VMI with legal issues.

      There is no one-size-fits-all reporting structure for VMIs, and your approach must leverage the materials from Steps 1.1-1.8, your culture, and your needs. By way of example, your VMI may include some or all of the following functions:

      • Contract Management
      • Relationship Management
      • Financial Management
      • Asset Management
      • Performance Management
      • Sourcing/Procurement
      • Risk Management

      Step 1.9: Structure (cont.)

      Determine the VMI’s organizational and reporting structure.

      Once you’ve identified the functional groups, you can assign titles, responsibilities, and reporting relationships. A good diagram goes a long way to helping others understand your organization. Traditional organization charts work well with VMIs, but a target diagram allows for rapid absorption of the dotted-line relationships. Review the two examples below and determine an approach that works best for you.

      An organizational Chart is depicted.  At the top of the chart is: Office of the CIO.  Below that is: VMI: Legal; Accounting & Finance; Corporate Procurement; below that are the following: Vendor Risk Management; Vendor Reporting and Analysis; Asset Management; Performance Management; Contract Management; IT Procurement Three concentric circles are depicted.  In the inner circle is the term: VMI.  In the middle circle are the terms: Reporting & Analysis; Asset Mgmt; Contract Mgmt; Performance Mgmt; It Proc; Vendor Risk.  In the outer circle are the following terms: Compliance; Finance; HR; Accounting; Procurement; Business Units; Legal; IT

      1.9.1: Structure

      15-60 minutes

      1. Meet with the participants and review decisions that have been made or options that are available regarding the VMI’s placement in the organization chart.
        1. Common options include the Chief Information Officer (CIO), Chief Financial Officer (CFO), or Chief Procurement Officer (CPO).
        2. Less common but viable options include the Chief Compliance Officer (CCO), Chief Operating Officer (COO), or another area.
      2. Brainstorm and determine the job functions and titles
      3. Define the reporting structure within the VMI.
      4. Identify the “dotted line” relationships between the VMI and other internal areas.
      5. Using flowchart, org. chart, or other similar software, reduce your results to a graphic representation that indicates where the VMI resides, its reporting structure, and its dotted-line relationships.
      6. Obtain sign-off on the structure from stakeholders and executives as required. A copy of the final output can be kept in the Jump – Phase 1 Tools and Templates Compendium, Tab 1.9 Structure, if desired.

      Input

      • Mission statement and goals
      • Scope
      • Maturity assessment results (current and target state)
      • Existing org. charts
      • Brainstorming

      Output

      • Completed org. chart with job titles and reporting structure

      Materials

      • Whiteboard/flip chart
      • Sticky notes
      • Flowchart/org. chart software or something similar
      • (Optional) Jump – Phase 1 Tools and Templates Compendium, Tab 1.9 Structure

      Participants

      • VMI team
      • VMI sponsor
      • Stakeholders and executives

      Phase 2: Build

      Create and Configure Tools, Templates, and Processes

      Phase 1Phase 2Phase 3Phase 4
      1.1 Mission Statement and Goals


      1.2 Scope

      1.3 Strengths and Obstacles

      1.4 Roles and Responsibilities

      1.5 Process Mapping

      1.6 Charter

      1.7 Vendor Inventory

      1.8 Maturity Assessment

      1.9 Structure

      2.1 Classification Model
      2.2 Risk Assessment Tool
      2.3 Scorecards and Feedback
      2.4 Business Alignment Meeting Agenda
      2.5 Relationship Alignment Document
      2.6 Vendor Orientation
      2.7 Job Descriptions
      2.8 Policies and Procedures
      2.9 3-Year Roadmap
      2.10 90-Day Plan
      2.11 Quick Wins
      2.12 Reports

      3.1 Classify Vendors
      3.2 Conduct Internal “Kickoff” Meeting
      3.3 Conduct Vendor Orientation
      3.4 Compile Scorecards
      3.5 Conduct Business Alignment Meetings
      3.6 Work the 90-Day Plan
      3.7 Manage the 3-Year Roadmap
      3.8 Measure and Monitor Risk
      3.9 Issue Reports
      3.10 Develop/Improve Vendor Relationships
      3.11 Contribute to Other Processes

      4.1 Assess Compliance
      4.2 Incorporate Leading Practices
      4.3 Leverage Lessons Learned
      4.4 Maintain Internal Alignment
      4.5 Update Governances

      This phase will walk you through the following activities:

      Configure and create the tools and templates that will help you run the VMI. The main outcomes from this phase are a clear understanding of which vendors are important to you, the tools to manage the vendor relationships, and an implementation plan.

      This phase involves the following participants:

      • VMI team
      • Applicable stakeholders and executives
      • Human Resources
      • Legal
      • Others as needed

      Jump Start Your Vendor Management Initiative

      Phase 2: Build

      Create and configure tools, templates, and processes.

      Phase 2: Build focuses on creating and configuring the tools and templates that will help you run your VMI. Vendor management is not a plug-and-play environment, and unless noted otherwise, the tools and templates included with this blueprint require your input and thought. The tools and templates must work in concert with your culture, values, and goals. That will require teamwork, insights, contemplation, and deliberation.

      During this Phase, you’ll leverage the various templates and tools included with this blueprint and adapt them for your specific needs and use. In some instances, you’ll be starting with mostly a blank slate; while in others, only a small modification may be required to make it fit your circumstances. However, it is possible that a document or spreadsheet may need heavy customization to fit your situation. As you create your VMI, use the included materials for inspiration and guidance purposes rather than as absolute dictates.

      Step 2.1: Classification model

      Configure the COST Vendor Classification Tool.

      One of the functions of a VMI is to allocate the appropriate level of vendor management resources to each vendor since not all vendors are of equal importance to your organization. While some people may be able intuitively to sort their vendors into vendor management categories, a more objective, consistent, and reliable model works best. Info-Tech’s COST model helps you assign your vendors to the appropriate vendor management category so that you can focus your vendor management resources where they will do the most good.

      COST is an acronym for Commodity, Operational, Strategic, and Tactical. Your vendors will occupy one of these vendor management categories, and each category helps you determine the nature of the resources allocated to that vendor, the characteristics of the relationship desired by the VMI, and the governance level used.

      The easiest way to think of the COST model is as a 2x2 matrix or graph. The model should be configured for your environment so that the criteria used for determining a vendor’s classification align with what is important to you and your organization. However, at this point in your VMI’s maturation, a simple approach works best. The Classification Model included with this blueprint requires minimal configuration to get you started and that is discussed on the activity slide associated with this Step 2.1.


      Speed
      Operational Strategic
      Commodity Tactical
      →→→
      Criticality and Risk to the Organization

      Step 2.1: Classification model (cont.)

      Configure the COST Vendor Classification Tool.

      Common Characteristics by Vendor Management Category

      Operational Strategic
      • Low to moderate risk and criticality; moderate to high spend and switching costs
      • Product or service used by more than one area
      • Price is a key negotiation point
      • Product or service is valued by the organization
      • Quality or the perception of quality is a differentiator (i.e. brand awareness)
      • Moderate to high risk and criticality; moderate to high spend and switching costs
      • Few competitors and differentiated products and services
      • Product or service significantly advances the organization’s vision, mission, and success
      • Well-established in their core industry
      Commodity Tactical
      • Low risk and criticality; low spend and switching costs
      • Product or service is readily available from many sources
      • Market has many competitors and options
      • Relationship is transactional
      • Price is the main differentiator
      • Moderate to high risk and criticality; low to moderate spend and switching costs
      • Vendor offerings align with or support one or more strategic objectives
      • Often IT vendors “outside” of IT (i.e. controlled and paid for by other areas)
      • Often niche or new vendors

      Source: Compiled in part from Stephen Guth, “Vendor Relationship Management Getting What You Paid for (And More)”

      2.1.1: Classification Model

      15-30 minutes

      1. Meet with the participants to configure the spend ranges in Jump – Phase 2 Vendor Classification Tool, Tab 1. Configuration, for your environment.
      2. Sort the data from Jump – Phase 1 Tools and Templates Compendium, Tab 1.7 Vendor Inventory, by spend; if you used multiple line items for a vendor in the Vendor Inventory tab, you will have to aggregate the spend data for this activity.
      3. Update cells F14-J14 in the Classification Model based on your actual data.
        1. Cell F14 – set the boundary at a point between the spend for your 10th and 11th ranked vendors. For example, if the 10th vendor by spend is $1,009,850 and the 11th vendor by spend is $980,763, the range for F14 would be $1,000,00+.
        2. Cell G14 – set the bottom of the range at a point between the spend for your 30th and 31st ranked vendors; the top of the range will be $1 less than the bottom of the range specified in F14.
        3. Cell H14 – set the bottom of the range slightly below the spend for your 50th ranked vendor; the top of the range will be $1 less than the bottom of the range specified in G14.
        4. Cells I14 and J14 – divide the remaining range in half and split it between the two cells; for J14 the range will be $0 to $1 less than the bottom range in I14.
      4. Ignore the other variables at this time.

      Download the Info-Tech Jump – Phase 2 Vendor Risk Assessment Tool

      Input

      • Jump – Phase 1 Tools and Templates Compendium, Tab 1.7 Vendor Inventory

      Output

      • Configured Vendor Classification Tool

      Materials

      • Jump – Phase 2 Vendor Classification Tool, Tab 1. Configuration

      Participants

      • VMI team

      Step 2.2: Risk assessment tool

      Identify risks to measure, monitor, and report on.

      One of the typical drivers of a VMI is risk management. Organizations want to get a better handle on the various risks their vendors pose. Vendor risks originate from many areas: financial, performance, security, legal, and many others. However, security risk is the high-profile risk and the one organizations often focus on almost exclusively, which leaves the organization vulnerable in other areas.

      Risk management is a program, not a project – there is no completion date. A proactive approach works best and requires continual monitoring, identification, and assessment. Reacting to risks after they occur can be costly and can have other detrimental effects on the organization. Any risk that adversely affects IT will adversely affect the entire organization.

      While the VMI won’t necessarily be quantifying or calculating the risk directly, it generally is the aggregator of risk information across the risk categories, which it then includes in its reporting function. (See Steps 2.12 and 3.8.)

      At a minimum, your risk management strategy should involve:

      • Identifying the risks you want to measure and monitor.
      • Identifying your risk appetite (the amount of risk you are willing to live with).
      • Measuring, monitoring, and reporting on the applicable risks.
      • Developing and deploying a risk management plan to minimize potential risk impact.

      Vendor risk is a fact of life, but you do have options for how you handle it. Be proactive and thoughtful in your approach, and focus your resources on what is important.

      2.2.1: Risk assessment tool

      30-90 minutes

      1. Meet with the participants to configure the risk indicators in Jump – Phase 2 Vendor Risk Assessment Tool, Tab 1. Set Parameters, for your environment.
      2. Review the risk categories and determine which ones you will be measuring and monitoring.
      3. Review the risk indicators under each risk category and determine whether the indicator is acceptable as written, is acceptable with modifications, should be replaced, or should be deleted.
      4. Make the necessary changes to the risk indicators; these changes will cascade to each of the vendor tabs. Limit the number of risk indicators to no more than seven per risk category.
      5. Gain input and approval as needed from sponsors, stakeholders, and executives as required.

      Download the Info-Tech Jump – Phase 2 Vendor Risk Assessment Tool

      Input

      • Scope
      • OIC Chart
      • Process Maps
      • Brainstorming

      Output

      • Configured Vendor Classification Tool

      Materials

      • Jump – Phase 2 Vendor Classification Tool, Tab 1. Configuration

      Participants

      • VMI team

      Step 2.3: Scorecards and feedback

      Design a two-way feedback loop with your vendors.

      A vendor management scorecard is a great tool for measuring, monitoring, and improving relationship alignment. In addition, it is perfect for improving communication between you and the vendor.

      Conceptually, a scorecard is similar to a report card you received when you were in school. At the end of a learning cycle, you received feedback on how well you did in each of your classes. For vendor management, the scorecard is also used to provide periodic feedback, but there are some different nuances and some additional benefits and objectives when compared to a report card.

      Although scorecards can be used in a variety of ways, the main focus here will be on vendor management scorecards – contract management, project management, and other types of scorecards will not be included in the materials covered in this Step 2.3 or in Step 3.4.

      Category 1 Score
      Vendor Objective A 4
      Objective B 3
      Objective C 5
      Objective D 4 !

      Step 2.3: Scorecards and feedback (cont.)

      Design a two-way feedback loop with your vendors.

      Anatomy

      The Info-Tech Scorecard includes five areas:

      • Measurement Categories. Measurement categories help organize the scorecard. Limit the number of measurement categories to three to five; this allows the parties to stay focused on what’s important. Too many measurement categories make it difficult for the vendor to understand the expectations.
      • Criteria. The criteria describe what is being measured. Create criteria with sufficient detail to allow the reviewers to fully understand what is being measured and to evaluate it. Criteria can be objective or subjective. Use three to five criteria per measurement category.
      • Measurement Category Weights. Not all of your measurement categories may be of equal importance to you; this area allows you to give greater weight to a measurement category when compiling the overall score.
      • Rating. Reviewers will be asked to assign a score to each criteria using a 1 to 5 scale.
      • Comments. A good scorecard will include a place for reviewers to provide additional information regarding the rating or other items that are relevant to the scorecard.

      An overall score is calculated based on the rating for each criteria and the measurement category weights.

      Step 2.3: Scorecards and feedback (cont.)

      Design a two-way feedback loop with your vendors.

      Goals and Objectives

      Scorecards can be used for a variety of reasons. Some of the common ones are listed below:

      • Improve vendor performance.
      • Convey expectations to the vendor.
      • Identify and recognize top vendors.
      • Increase alignment between the parties.
      • Improve communication with the vendor.
      • Compare vendors across the same criteria.
      • Measure items not included in contract metrics.
      • Identify vendors for “strategic alliance” consideration.
      • Help the organization achieve specific goals and objectives.
      • Identify and resolve issues before they impact performance or the relationship.

      Identifying your scorecard drivers first will help you craft a suitable scorecard.

      Step 2.3: Scorecards and feedback (cont.)

      Design a two-way feedback loop with your vendors.

      Info-Tech recommends starting with simple scorecards to allow you and the vendors to acclimate to the new process and information. As you build your scorecards, keep in mind that internal personnel will be scoring the vendors and the vendors will be reviewing the scorecard. Make your scorecard easy for your personnel to fill out and composed of meaningful content to drive the vendor in the right direction. You can always make the scorecard more complex in the future.

      Our recommendation of five categories is provided below. Choose three to five categories to help you accomplish your scorecard goals and objectives:

      1. Timeliness – responses, resolutions, fixes, submissions, completions, milestones, deliverables, invoices, etc.
      2. Cost – total cost of ownership, value, price stability, price increases/decreases, pricing models, etc.
      3. Quality – accuracy, completeness, mean time to failure, bugs, number of failures, etc.
      4. Personnel – skilled, experienced, knowledgeable, certified, friendly, trustworthy, flexible, accommodating, etc.
      5. Risk – adequate contractual protections, security breaches, lawsuits, finances, audit findings, etc.

      Some criteria may be applicable in more than one category. The categories above should cover at least 80% of the items that are important to your organization. The general criteria listed for each category is not an exhaustive list, but most things break down into time, money, quality, people, and risk issues.

      Step 2.3: Scorecards and feedback (cont.)

      Design a two-way feedback loop with your vendors.

      Additional Considerations

      • Even a good rating system can be confusing. Make sure you provide some examples or a way for reviewers to discern the differences between 1, 2, 3, 4, and 5. Don’t assume your “Rating Key” will be intuitive.
      • When assigning weights, don’t go lower than 10% for any measurement category. If the weight is too low, it won’t be relevant enough to have an impact on the total score. If it doesn’t “move the needle,” don’t include it.
      • Final sign-off on the scorecard template should occur outside of the VMI. The heavy lifting can be done by the VMI to create it, but the scorecard is for the benefit of the organization overall and those impacted by the vendors specifically. You may end up playing arbiter or referee, but the scorecard is not the exclusive property of the VMI. Try to reach consensus on your final template whenever possible.
      • You should notice improved ratings and total scores over time for your vendors. One explanation for this is the Pygmalion Effect: “The Pygmalion [E]ffect describes situations where someone’s high expectations improves our behavior and therefore our performance in a given area. It suggests that we do better when more is expected of us.”* Convey your expectations and let the vendors’ competitive juices take over.
      • While you’re creating your scorecard and materials to explain the process to internal personnel, identify those pieces that will help you explain it to your vendors as part of your vendor orientation (see steps 2.6 and 3.4). Leveraging pre-existing materials is a great shortcut.

      *Source: The Decision Lab, 2020

      Step 2.3: Scorecards and feedback (cont.)

      Design a two-way feedback loop with your vendors.

      Vendor Feedback

      After you’ve built your scorecard, turn your attention to the second half of the equation – feedback from the vendor. A communication loop cannot be successful without the dialogue flowing both ways. While this can happen with just a scorecard, a mechanism specifically geared toward the vendor providing you with feedback improves communication, alignment, and satisfaction.

      You may be tempted to create a formal scorecard for the vendor to use. Our recommendation is to avoid that temptation until later in your maturity or development of the VMI. You’ll be implementing a lot of new processes, deploying new tools and templates, and getting people to work together in new ways. Work on those things first.

      For now, implement an informal process for obtaining information from the vendor. Start by identifying information that you will find useful, information that will allow you to improve overall, to reduce waste or time, to improve processes, to identify gaps in skills. Incorporate these items into your business alignment meetings (see Steps 2.4 and 3.5). Create three to five good questions to ask the vendor and include these in the business alignment meeting agenda. The goal is to get meaningful feedback, and that starts with asking good questions.

      Keep it simple at first. When the time is right, you can build a more formal feedback form or scorecard. Don’t be in a rush though. So long as the informal method works, keep using it.

      2.3.1: Scorecards and feedback

      30-60 minutes

      1. Meet with the participants and brainstorm ideas for your scorecard measurement categories:
        1. What makes a vendor valuable to your organization?
        2. What differentiates a “good” vendor from a “bad” vendor?
        3. What items would you like to measure and provide feedback to the vendor to improve performance, the relationship, risk, and other areas?
      2. Select three, but no more than five, of the following measure categories: timeliness, cost, quality, personnel, and risk.
      3. Within each measurement category, list two or three criteria that you want to measure and track for your vendors; choose items that are as universal as possible rather than being applicable to one vendor or one vendor type.
      4. Assign a weight to each measurement category, ensuring that the total weight is 100% for all measurement categories.
      5. Document your results as you go in Jump – Phase 2 Tools and Templates Compendium, Tab 2.3 Scorecard.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • Brainstorming

      Output

      • Configured scorecard template

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.3 Scorecard

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      2.3.2: Scorecards and feedback

      15-30 minutes

      1. Meet with the participants and brainstorm ideas for feedback to seek from your vendors during your business alignment meetings. During the brainstorming, identify questions to ask the vendor about your organization that will:
        1. Help you improve the relationship.
        2. Help you improve your processes or performance.
        3. Help you improve ongoing communication.
        4. Help you evaluate your personnel.
      2. Identify the top five questions you want to include in your business alignment meeting agenda. (Note: you may need to refine the actual questions from the brainstorming activity before they are ready to include in your business alignment meeting agenda.)
      3. Document both your brainstorming activity and your final results in Jump – Phase 2 Tools and Templates Compendium, Tab 2.3 Feedback. The brainstorming questions can be used in the future as your VMI matures and your feedback transforms from informal to formal. The final results will be used in Steps 2.4 and 3.5.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • Brainstorming

      Output

      • Feedback questions to include with the business alignment meeting agenda

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.3 Feedback

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Step 2.4: Business alignment meeting agenda

      Craft an agenda that meets the needs of the VMI.

      A business alignment meeting (BAM) is a great, multi-faceted tool to ensure the customer and the vendor stay focused on what is important to the customer at a high level. BAMs are not traditional “operational” meetings where the parties get into the details of the contracts, deal with installation problems, address project management issues, or discuss specific cost overruns. The main focus of the BAM is the scorecard (see Step 2.3), but other topics are discussed and other purposes are served. For example, you can use the BAM to develop the relationship with the vendor’s leadership team so that if escalation is ever needed, your organization is more than just a name on a spreadsheet or customer list; you can learn about innovations the vendor is working on (without the meeting turning into a sales call); you can address high-level performance trends and request corrective action as needed; you can clarify your expectations; you can educate the vendor about your industry, culture, and organization; and you can learn more about the vendor.

      As you build your BAM agenda, someone in your organization may say, “Oh, that’s just a quarterly business review (QBR) or top-to-top meeting.” However, in most instances, an existing QBR or top-to-top meeting is not the same as a BAM. Using the term QBR or top-to-top meeting instead of BAM can lead to confusion internally. The VMI may say to the business unit, Procurement, or another department, “We’re going to start running some QBRs for our strategic vendors.” The typical response is, “There’s no need to do that. We already run QBRs/top-to-top meetings with our important vendors.” This may be accompanied by an invitation to join their meeting, where you may be an afterthought, have no influence, and get five minutes at the end to talk about your agenda items. Keep your BAM separate so that it meets your needs.

      Step 2.4: Business alignment meeting agenda (cont.)

      Craft an agenda that meets the needs of the VMI.

      As previously noted, using the term BAM more accurately depicts the nature of the VMI meeting and prevents confusion internally with other meetings already occurring. In addition, hosting the BAM yourself rather than piggybacking onto another meeting ensures that the VMI’s needs are met. The VMI will set and control the BAM agenda and determine the invite list for internal personnel and vendor personnel. As you may have figured out by now, having the right customer and vendor personnel attend will be essential.

      BAMs are conducted at the vendor level … not the contract level. As a result, the frequency of the BAMs will depend on the vendor’s classification category (see Steps 2.1 and 3.1). General frequency guidelines are provided below, but they can be modified to meet your goals:

      • Commodity Vendors – Not applicable
      • Operational Vendors – Biannually or annually
      • Strategic Vendors – Quarterly
      • Tactical Vendors – Quarterly or biannually

      BAMs can help you achieve some additional benefits not previously mentioned:

      • Foster a collaborative relationship with the vendor.
      • Avoid erroneous assumptions by the parties.
      • Capture and provide a record of the relationship (and other items) over time.

      Step 2.4: Business alignment meeting agenda (cont.)

      Craft an agenda that meets the needs of the VMI.

      As with any meeting, building the proper agenda will be one of the keys to an effective and efficient meeting. A high-level BAM agenda with sample topics is set out below:

      BAM Agenda

      • Opening Remarks
        • Welcome and introductions
        • Review of previous minutes
      • Active Discussion
        • Review of open issues
        • Scorecard and feedback
        • Current status of projects to ensure situational awareness by the vendor
        • Roadmap/strategy/future projects
        • Accomplishments
      • Closing Remarks
        • Reinforce positives (good behavior, results, and performance, value added, and expectations exceeded)
        • Recap
      • Adjourn

      2.4.1: Business alignment meeting agenda

      20-45 minutes

      1. Meet with the participants and review the sample agenda in Jump – Phase 2 Tools and Templates Compendium, Tab 2.4 BAM Agenda.
      2. Using the sample agenda as inspiration and brainstorming activities as needed, create a BAM agenda tailored to your needs.
        1. Select the items from the sample agenda applicable to your situation.
        2. Add any items required based on your brainstorming.
        3. Add the feedback questions identified during Activity 2.3.2 and documented in Jump – Phase 2 Tools and Templates Compendium, Tab 2.3 Feedback.
      3. Gain input and approval from sponsors, stakeholders, and executives as required or appropriate.
      4. Document the final BAM agenda in Jump – Phase 2 Tools and Templates Compendium, Tab 2.4 BAM Agenda.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • Brainstorming
      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.3 Feedback

      Output

      • Configured BAM agenda

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.4 BAM Agenda

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Step 2.5: Relationship alignment document

      Draft a document to convey important VMI information to your vendors.

      Throughout this blueprint, alignment is mentioned directly (e.g. business alignment meetings [Steps 2.4 and 3.5]) or indirectly implied. Ensuring you and your vendors are on the same page, have clear and transparent communication, and understand each other’s expectations is critical to fostering strong relationships. One component of gaining and maintaining alignment with your vendors is the relationship alignment document (RAD). Depending upon the scope of your VMI and what your organization already has in place, your RAD will fill in the gaps on various topics.

      Early in the VMI’s maturation, the easiest approach is to develop a short document (i.e. 1 page) or a pamphlet (i.e. the classic trifold) describing the rules of engagement when doing business with your organization. The RAD can convey expectations, policies, guidelines, and other items. The scope of the document will depend on 1) what you believe is important for the vendors to understand, and 2) any other similar information already provided to the vendors.

      The first step to drafting a RAD is to identify what information vendors need to know to stay on your good side. For example, you may want vendors to know about your gift policy (e.g. employees may not accept gifts from vendors above a nominal value such as a pen or mousepad). Next, compare your list of what vendors need to know and determine if the content is covered in other vendor-facing documents such as a vendor code of conduct or your website’s vendor portal. Lastly, create your RAD to bridge the gap between what you want and what is already in place. In some instances, you may want to include items from other documents to reemphasize them with the vendor community.

      Info-Tech Insight

      The RAD can be used with all vendors regardless of classification category. It can be sent directly to the vendors or given to them during vendor orientation (see Step 3.3)

      2.5.1: Relationship alignment document

      1-4 hours

      1. Meet with the participants and review the RAD sample and checklist in Jump – Phase 2 Tools and Templates Compendium, Tab 2.5 Relationship Alignment Doc.
      2. Determine:
        1. Whether you will create one RAD for all vendors or one RAD for strategic vendors and another RAD for tactical and operational vendors; whether you will create a RAD for commodity vendors.
        2. The concepts you want to include in your RAD(s).
        3. The format for your RAD(s) – traditional, pamphlet, or other.
        4. Whether signoff or acknowledgement will be required by the vendors.
      3. Draft your RAD(s) and work with other internal areas such as Marketing to create a consistent brand for the RADS and Legal to ensure consistent use and preservation of trademarks or other intellectual property rights and other legal issues.
      4. Review other vendor-facing documents (e.g. supplier code of conduct, onsite safety and security protocols) for consistencies between them and the RAD(s).
      5. Obtain signoff on the RAD(s) from stakeholders, sponsors, executives, Legal, Marketing, and others as needed.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • Brainstorming
      • Vendor-facing documents, policies, and procedures

      Output

      • Completed relationship alignment document(s)

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.5 Relationship Alignment Doc

      Participants

      • VMI team
      • Marketing, as needed
      • Legal, as needed

      Step 2.6: Vendor orientation

      Create a VMI awareness process to build bridges with your vendors.

      Vendor Orientation: 01 - Orientation; 02 - Reorientation; 03 - Debrief

      Your organization is unique. It may have many similarities with other organizations, but your culture, risk tolerance, mission, vision, and goals, finances, employees, and “customers” (those that depend on you) make it different. The same is true of your VMI. It may have similar principles, objectives, and processes to other organizations’ VMIs, but yours is still unique. As a result, your vendors may not fully understand your organization and what vendor management means to you.

      Vendor orientation is another means to helping you gain and maintain alignment with your important vendors, educate them on what is important to you, and provide closure when/if the relationship with the vendor ends. Vendor orientation is comprised of three components, each with a different function:

      • Orientation
      • Reorientation
      • Debrief

      Vendor orientation focuses on the vendor management pieces of the puzzle (e.g. the scorecard process) rather than the operational pieces (e.g. setting up a new vendor in the system to ensure invoices are processed smoothly).

      Step 2.6: Vendor orientation (cont.)

      Create a VMI awareness process to build bridges with your vendors.

      Vendor Orientation: 01 - Orientation

      Orientation

      Orientation is conceptually similar to new hire orientation for employees at your organization. Generally conducted as a meeting, orientation provides your vendors with the information they need to be successful when working with your organization. Sadly, this is often overlooked by customers; it can take months or years for vendors to figure it out by themselves. By controlling the narrative and condensing the timeline, vendor relationships and performance improve more rapidly.

      A partial list of topics for orientation is set out below:

      • Your organization’s structure
      • Your organization’s culture
      • Your relationship expectations
      • Your governances (VMI and other)
      • Their vendor classification designation (commodity, operational, strategic, or tactical)
      • The scorecard process
      • Business alignment meetings
      • Relationship alignment documents

      In short, this is the first step toward building (or continuing to build) a robust, collaborative, mutually beneficial relationship with your important vendors.

      Step 2.6: Vendor orientation (cont.)

      Create a VMI awareness process to build bridges with your vendors.

      Vendor Orientation: 02 - Reorientation

      Reorientation

      Reorientation is either identical or similar to orientation, depending upon the circumstances. Reorientation occurs for a number of reasons, and each reason will impact the nature and detail of the reorientation content. Reorientation occurs whenever:

      • There is a significant change in the vendor’s products or services.
      • The vendor has been through a merger, acquisition, or divestiture.
      • A significant contract renewal/renegotiation has recently occurred.
      • Sufficient time has passed from orientation; commonly 2 to 3 years.
      • The vendor has been placed in a “performance improvement plan” or “relationship improvement plan” protocol.
      • Significant turnover has occurred within your organization (executives, key stakeholders, and/or VMI personnel).
      • Substantial turnover has occurred at the vendor at the executive or account management level.
      • The vendor has changed vendor classification categories after the most current classification.

      As the name implies, the goal is to refamiliarize the vendor with your current VMI situation, governances, protocols, and expectations. The drivers for reorientation will help you determine its scope, scale, and frequency.

      Step 2.6: Vendor orientation (cont.)

      Create a VMI awareness process to build bridges with your vendors.

      Vendor Orientation: 03 - Debrief

      Debrief

      To continue the analogy from orientation, debrief is similar to an exit interview for an employee when their employment is terminated. In this case, debrief occurs when the vendor is no longer an active vendor with your organization – all contracts have terminated or expired, and no new business with the vendor is anticipated within the next three months.

      Similar to orientation and reorientation, debrief activities will be based on the vendor’s classification category within the COST model. Strategic vendors don’t go away very often; usually, they transition to operational or tactical vendors first. However, if a strategic vendor is no longer providing products or services to you, dig a little deeper into their experiences and allocate extra time for the debrief meeting.

      The debrief should provide you with feedback on the vendor’s experience with your organization and their participation in your VMI. In addition, it can provide closure for both parties since the relationship is ending. Be careful that the debrief does not turn into a finger-pointing meeting or therapy session for the vendor. It should be professional and productive; if it is going off the rails, terminate the meeting before more damage can occur.

      End the debrief on a high note if possible. Thank the vendor, highlight its key contributions, and single out any personnel who went above and beyond. You never know when you will be doing business with this vendor again – don’t burn bridges!

      Step 2.6: Vendor orientation (cont.)

      Create a VMI awareness process to build bridges with your vendors.

      • As you create your vendor orientation materials, focus on the message you want to convey.
      • For orientation and reorientation:
        • What is important to you that vendors need to know?
        • What will help the vendors understand more about your organization … your VMI?
        • What and how are you different from other organizations overall … in your “industry”?
        • What will help them understand your expectations?
        • What will help them be more successful?
        • What will help you build the relationship?
      • For debrief:
        • What information or feedback do you want to obtain?
        • What information or feedback to you want to give?
      • The level of detail you provide strategic vendors during orientation and reorientation may be different from the information you provide tactical and operational vendors. Commodity vendors are not typically involved in the vendor orientation process. The orientation meetings can be conducted on a one-to-one basis for strategic vendors and a one-to-many basis for operational and tactical vendors; reorientation and debrief are best conducted on a one-to-one basis. Lastly, face-to-face or video meetings work best for vendor orientation; voice-only meetings, recorded videos, or distributing only written materials seldom hit their mark or achieve the desired results.

      2.6.1: Vendor orientation

      1 to several hours

      1. Meet with the participants and review the Phase Tools and Templates Compendium, Tab 2.6 Vendor Orientation.
        1. Use the orientation checklist to identify the materials you want to create for your orientation meetings.
        2. Use the reorientation checklist to identify the materials you want to create for your reorientation meetings.
      2. The selections can be made by classification category (i.e. different items can apply to strategic, operational, and tactical vendors).
      3. Create the materials and seek input and/or approval from sponsors, stakeholders, and executives as needed.
      4. Use the debrief section of the tool to create an agenda, list the questions you want to ask vendors, and list information you want to provide to vendors. The agenda, questions, and information can be segregated by classification category.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • Brainstorming

      Output

      • Agendas and materials for orientation, reorientation, and debrief

      Materials

      • Phase Tools and Templates Compendium, Tab 2.6 Vendor Orientation

      Participants

      • VMI team

      Step 2.7: Job descriptions

      Ensure new and existing job descriptions are up to date.

      Based on your work product from Steps 1.1-1.9, it’s time to start drafting new or modifying existing job descriptions applicable to the VMI team members. Some of the VMI personnel may be dedicated full-time to the VMI, while others may be supporting the VMI on a part-time basis. At a minimum, create or modify your job descriptions based on the categories set out below. Remember to get the internal experts involved so that you stay true to your environment and culture.

      01 Title

      This should align overall with what the person will be doing and what the person will be responsible for. Your hands may be tied with respect to titles, but try to make them intuitively descriptive if possible.

      02 Duties

      This is the main portion of the job description. List the duties, responsibilities, tasks, activities, and results expected. Again, there may be some limitations imposed by your organization, but be as thorough as possible.

      03 Qualifications

      This tends to be a gray area for many organizations, with the qualifications, certifications, and experience desired expressed in “ranges” so that good candidates are not eliminated from consideration unnecessarily.

      2.7.1: Job descriptions

      1 to several hours

      1. Meet with the participants and review the VMI structure from Step 1.9.
        1. List the positions that require new job descriptions.
        2. List the positions that require updated job descriptions.
      2. Review the other Phase 1 work product and list the responsibilities, tasks, and functions that need to be incorporated into the new and updated job descriptions.
      3. Review the sample VMI job descriptions and sample VMI job description language in Jump – Phase 2 Tools and Templates Compendium, Tab 2.7 Job Descriptions, and identify language and concepts you want to include in the new and revised job descriptions.
      4. Using your template, draft the new job descriptions and modify the existing job descriptions to synchronize with the VMI structure. Work with other internal areas such as Human Resources to ensure cultural fit and compliance.
      5. Obtain input and signoff on the job descriptions from stakeholders, sponsors, executives, Human Resources, and others as needed.
      6. Document your final job descriptions in Jump – Phase 2 Tools and Templates Compendium, Tab 2.7 Job Descriptions.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • Brainstorming
      • Existing job descriptions
      • Work product from Phase 1

      Output

      • Job descriptions for new positions
      • Updated job descriptions for existing positions

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.7 Job Descriptions

      Participants

      • VMI team
      • Human Resources (as needed)
      • Applicable stakeholders and executives (as needed)

      Step 2.8: Policies and procedures

      Prepare policies and procedures for VMI functions.

      Policies and procedures are often thought of as boring documents that are 1) tedious to create, 2) seldom read after creation, and 3) only used to punish people when they do something “wrong.” However, when done well, these documents:

      • Communicate expectations.
      • Capture institutional knowledge.
      • Provide guidance for decision making.
      • Help workers avoid errors and minimize risk.
      • Ensure regulatory and organizational compliance.
      • List the steps required to achieve consistent results.

      Definitions of Policies and Procedures

      Policies and procedures are essential, but they are often confused with each other. A policy is a rule, guideline, or framework for making decisions. For example, in the vendor management space, you may want a policy indicating your organization’s view on gifts from vendors. A procedure is a set of instructions for completing a task or activity. For example, staying in the vendor management space, you may want a procedure to outline the process for classifying vendors.

      Step 2.8: Policies and procedures (cont.)

      Prepare policies and procedures for VMI functions.

      Start With Your Policy/Procedure Template or Create One for Consistency

      When creating policies and procedures, follow your template. If you don’t have one (or want to see if anything is missing from your template) the following list of potential components for your governance documents is provided.* Not every concept is required. Use your judgment and err on the side of caution when drafting; balance readability and helpfulness against over documenting and over complicating.

      • Descriptive Title
      • Policy Number
      • Brief Overview
      • Purpose
      • Scope
      • The Policy or Procedure
      • Definitions
      • Revision Date
      • History
      • Related Documents
      • Keywords

      Step 2.8: Policies and procedures (cont.)

      Prepare policies and procedures for VMI functions.

      Although they are not ever going to be compared to page-turning novels, policies and procedures can be improved by following a few basic principles. By following the guidelines set out below, your VMI policies and procedures will contribute to the effectiveness of your initiative.*

      • Use short sentences.
      • Organize topics logically.
      • Use white space liberally.
      • Use mandatory language.
      • Use gender-neutral terms.
      • Write with an active voice.
      • Avoid jargon when possible.
      • Use a consistent “voice” and tone.
      • Use pictures or diagrams when they will help.
      • Write in the same tense throughout the document.
      • Use icons and colors to designate specific elements.
      • Make sure links to other policies and procedures work.
      • Define all acronyms and jargon (when it must be used).
      • Avoid a numbering scheme with more than three levels.

      *Adapted in part from smartsheet.com

      Info-Tech Insight

      Drafting policies and procedures is an iterative process that requires feedback from the organization’s leadership team.

      2.8.1: Policies and procedures

      Several hours

      1. Meet with the participants and review the sample policies and procedures topics in Jump – Phase 2 Tools and Templates Compendium, Tab 2.8 Policies and Procedures.
      2. Determine:
        1. The concepts you want to include in your policies and procedures; brainstorm for any additional concepts you want to include.
        2. The format/template for your policies and procedures.
      3. Draft your policies and procedures based on the sample topics and your brainstorming activity. Work with other internal areas such as Legal and Human Resources to ensure cultural and environmental fit within your organization.
      4. Obtain input and signoff on the policies and procedures from stakeholders, sponsors, executives, Legal, Human Resources, and others as needed.
      5. Document your final policies and procedures in Jump – Phase 2 Tools and Templates Compendium, Tab 2.8 Policies and Procedures.
      6. Publish your policies and procedures and conduct training sessions or awareness sessions as needed.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • Existing policies and procedures (if any)
      • Existing policies and procedures template (if any)
      • Scope
      • OIC chart
      • Process maps
      • Brainstorming

      Output

      • VMI policies and procedures

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.8 Policies and Procedures

      Participants

      • VMI team
      • Legal and Human Resources (as needed)
      • Applicable stakeholders and executives (as needed)

      Step 2.9: 3-year roadmap

      Plot your path at a high level.

      The VMI exists in many planes concurrently: 1) it operates both tactically and strategically, and 2) it focuses on different timelines or horizons (e.g. the past, the present, and the future). Creating a 3-year roadmap facilitates the VMI’s ability to function effectively across these multiple landscapes.

      The VMI roadmap will be influenced by many factors. The work product from Phase 1: Plan, input from executives, stakeholders, and internal clients, and the direction of the organization as a whole are great sources of information as you begin to build your roadmap.

      To start, identify what you would like to accomplish in Year 1. This is arguably the easiest year to complete: budgets are set (or you have a good idea what the budget will look like), personnel decisions have been made, resources have been allocated, and other issues impacting the VMI are known with a higher degree of certainty than any other year. This does not mean things won’t change during the first year of the VMI, but expectations are usually lower and the short event horizon makes things more predictable during the Year-1 ramp-up period.

      Years 2 and 3 are more tenuous, but the process is the same: identify what you would like to accomplish or roll out in each year. Typically, the VMI maintains the Year 1 plan into subsequent years and adds to the scope or maturity. For example, you may start Year 1 with BAMs and scorecards for three of your strategic vendors; during Year 2, you may increase that to five vendors; and during Year 3, you may increase that to nine vendors. Or, you may not conduct any market research during Year 1, waiting to add it to your roadmap in Year 2 or 3 as you mature.

      Breaking things down by year helps you identify what is important and the timing associated with your priorities. A conservative approach is recommended. It is easy to overcommit, but the results can be disastrous and painful.

      2.9.1: 3-year roadmap

      45-90 minutes

      1. Meet with the participants and decide how to coordinate Year 1 of your 3-year roadmap with your existing fiscal year or reporting year. Year 1 may be shorter or longer than a calendar year.
      2. Review the VMI activities listed in Jump – Phase 2 Tools and Templates Compendium, Tab 2.9 3-Year Roadmap. Use brainstorming and your prior work product from Phase 1 and Phase 2 to identify additional items for the roadmap and add them at the bottom of the spreadsheet.
      3. Starting with the first activity, determine when that activity will begin and put an X in the corresponding column; if the activity is not applicable, leave it blank or insert N/A.
      4. Go back to the top of the list and add information as needed.
        1. For any Year-1 or Year-2 activities, add an X in the corresponding columns if the activity will be expanded/continued in subsequent periods (e.g. if a Year 2 activity will continue in Year 3, put an X in Year 3 as well).
        2. Use the comments column to provide clarifying remarks or additional insights related to your plans or “X’s.” For example, “Scorecards begin in Year 1 with three vendors and will roll out to five vendors in Year 2 and nine vendors in Year 3.”
      5. Obtain signoff from stakeholders, sponsors, and executives as needed.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • Phase 1 work product
      • Steps 2.1-2.8 work product
      • Brainstorming

      Output

      • High level 3-year roadmap for the VMI

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.9 3-Year Roadmap

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Step 2.10: 90-day plan

      Pave your short-term path with a series of detailed quarterly plans.

      Now that you have prepared a 3-year roadmap, it’s time to take the most significant elements from the first year and create action plans for each three-month period. Your first 90-day plan may be longer or shorter if you want to sync to your fiscal or calendar quarters. Aligning with your fiscal year can make it easier for tracking and reporting purposes; however, the more critical item is to make sure you have a rolling series of four 90-day plans to keep you focused on the important activities and tasks throughout the year.

      The 90-day plan is a simple project plan that will help you measure, monitor, and report your progress. Use the Info-Tech tool to help you track:

      • Activities
      • Tasks comprising each activity
      • Who will be performing the tasks
      • An estimate of the time required per person per task
      • An estimate of the total time to achieve the activity
      • A due date for the activity
      • A priority of the activity

      The first 90-day plan will have the greatest level of detail and should be as thorough as possible; the remaining three 90-day plans will each have less detail for now. As you approach the middle of the first 90-day plan, start adding details to the next 90-day plan; toward the end of the first quarter add a high-level 90-day plan to the end of the chain. Continue repeating this cycle each quarter and consult the 3-year roadmap and the leadership team as necessary.

      90 Days

      2.10.1: 90-day plan

      45-90 minutes

      1. Meet with the participants and decide how to coordinate the first 90-day plan with your existing fiscal year or reporting cycles. Your first plan may be shorter or longer than 90 days.
      2. Looking at the Year 1 section of the 3-year roadmap, identify the activities that will be started during the next 90 days.
      3. Using the Jump – Phase 2 Tools and Templates Compendium, Tab 2.10 90-Day Plan, enter the following information into the spreadsheet for each activity to be accomplished during the next 90 days:
        1. Activity description
        2. Tasks required to complete the activity (be specific and descriptive)
        3. The people who will be performing each task
        4. The estimated number of hours required to complete each task
        5. The start date and due date for each task or the activity
      4. Validate the tasks are a complete list for each activity and the people performing the tasks have adequate time to complete the tasks by the due date(s).
      5. Assign a priority to each activity.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • 3-year roadmap
      • Phase 1 work product
      • Steps 2.1-2.9 work product
      • Brainstorming

      Output

      • Detailed plan for the VMI for the next quarter or 90 days

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.10 90-Day Plan

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Step 2.11: Quick wins

      Identify potential short-term successes to gain momentum and show value immediately.

      As the final step in the timeline trilogy, you are ready to identify some quick wins for the VMI. Using the first 90-day plan and a brainstorming activity, create a list of things you can do in 15 to 30 days that add value to your initiative and build momentum.

      As you evaluate your list of potential candidates, look for things that:

      • Are achievable within the stated timeline.
      • Don’t require a lot of effort.
      • Involve stopping a certain process, activity, or task; this is sometimes known as a “stop doing stupid stuff” approach.
      • Will reduce or eliminate inefficiencies; this is sometimes known as the war on waste.
      • Have a moderate to high impact or bolster the VMI’s reputation.

      As you look for quick wins, you may find that everything you identify does not meet the criteria. That’s ok … don’t force the issue. Return your focus to the 90-day plan and 3-year roadmap, and update those documents if the brainstorming activity associated with this Step 2.11 identified anything new.

      2.11.1: Quick wins

      15-30 minutes

      1. Meet with the participants and review the 3-year roadmap and 90-day plan. Determine if any item on either document can be completed:
        1. Quickly (30 days or less)
        2. With minimal effort
        3. To provide or show moderate to high levels of value or provide the VMI with momentum
      2. Brainstorm to identify any other items that meet the criteria in step 1 above.
      3. Compile a comprehensive list of these items and select up to five to pursue.
      4. Document the list in the Jump – Phase 2 Tools and Templates Compendium, Tab 2.11 Quick Wins.
      5. Manage the quick wins list and share the results with the VMI team and applicable stakeholders and executives.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • 3-year roadmap
      • 90-day plan
      • Brainstorming

      Output

      • A list of activities that require low levels of effort to achieve moderate to high levels of value in a short period

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.11 Quick Wins

      Participants

      • VMI team

      Step 2.12: Reports

      Construct your reports to resonate with your audience.

      Issuing reports is a critical piece of the VMI since the VMI is a conduit of information for the organization. It may be aggregating risk data from internal areas, conducting vendor research, compiling performance data, reviewing market intelligence, or obtaining relevant statistics, feedback, comments, facts, and figures from other sources. Holding onto this information minimizes the impact a VMI can have on the organization; however, the VMI’s internal clients, stakeholders, and executives can drown in raw data and ignore it completely if it is not transformed into meaningful, easily-digested information.

      Before building a report, think about your intended audience:

      • What information are they looking for … what will help them understand the big picture?
      • What level of detail is appropriate, keeping in mind the audience may not be like-minded?
      • What items are universal to all of the readers and what items are of interest to one or two readers?
      • How easy or hard will it be to collect the data … who will be providing it, how time consuming will it be?
      • How accurate, valid, and timely will the data be?
      • How frequently will each report need to be issued?

      Step 2.12: Reports (cont.)

      Construct your reports to resonate with your audience.

      Use the following guidelines to create reports that will resonate with your audience:

      • Value information over data, but sometimes data does have a place in your report.
      • Use pictures, graphics, and other representations more than words, but words are often necessary in small, concise doses.
      • Segregate your report by user; for example, general information up top, CIO information below that on the right, CFO information to the left of CIO information, etc.
      • Send a draft report to the internal audience and seek feedback, keeping in mind you won’t be able to cater to or please everyone.

      Step 2.12: Reports (cont.)

      Construct your reports to resonate with your audience.

      The report’s formatting and content display can make or break your reports.*

      • Make the report look inviting and easy to read. Use:
        • Short paragraphs and bullet points.
        • A simple layout and uncluttered, wide margins.
        • Minimal boldface, underline, or italics to attract the readers’ attention.
        • High contrast between text and background.
      • Charts, graphs, and infographics should be intuitive and tell the story on their own.
      • Make it easy to peruse the report for topics of interest.
        • Maintain consistent design features.
        • Use impactful, meaningful headings and subheadings.
        • Include callouts to draw attention to important high-level information.
      • Demonstrate the impact of the accomplishments or success stories when appropriate.
      • Finish with a simple concise summary when appropriate. Consider adding:
        • Key points for the reader to takeaway.
        • Action items or requests.
        • Plans for next reporting period.

      *Sources: Adapted and compiled in part from: designeclectic.com, ahrq.gov, and 60secondmarketer.com.

      2.12.1: Reports

      15-45 minutes

      1. Meet with the participants and review the applicable work product from Phases 1 and 2; identify qualitative and quantitative items the VMI measures, monitors, tracks, or aggregates.
      2. Determine which items will be reported and to whom (by category):
        1. Internally to personnel within the VMI
        2. Internally to personnel outside the VMI
        3. Externally to vendors
      3. Within each category above, determine your intended audiences/recipients. For example, you may have a different list of recipients for a risk report than you do a scorecard summary report. This will help you identify the number of reports required.
      4. Create a draft structure for each report based on the audience and the information being conveyed. Determine the frequency of each report and person responsible for creating for each report.
      5. Document your final choices in Jump – Phase 2 Tools and Templates Compendium, Tab 2.12 Reports.

      Download the Info-Tech Jump – Phase 2 Tools and Templates Compendium

      Input

      • Brainstorming
      • Phase 1 work product
      • Steps 2.1-2.11 work product

      Output

      • A list of reports used by the VMI
      • For each report:
      • The conceptual content
      • A list of who will receive or have access
      • A creation/distribution frequency

      Materials

      • Jump – Phase 2 Tools and Templates Compendium, Tab 2.12 Reports

      Participants

      • VMI team
      • Applicable stakeholders and executives (as needed)

      Phase 3: Run

      Implement Your Processes and Leverage Your Tools and Templates

      Phase 1 Phase 2 Phase 3 Phase 4
      1.1 Mission Statement and Goals
      1.2 Scope
      1.3 Strengths and Obstacles
      1.4 Roles and Responsibilities
      1.5 Process Mapping
      1.6 Charter
      1.7 Vendor Inventory
      1.8 Maturity Assessment
      1.9 Structure

      2.1 Classification Model
      2.2 Risk Assessment Tool
      2.3 Scorecards and Feedback
      2.4 Business Alignment Meeting Agenda
      2.5 Relationship Alignment Document
      2.6 Vendor Orientation
      2.7 Job Descriptions
      2.8 Policies and Procedures
      2.9 3-Year Roadmap
      2.10 90-Day Plan
      2.11 Quick Wins
      2.12 Reports

      3.1 Classify Vendors
      3.2 Conduct Internal “Kickoff” Meeting
      3.3 Conduct Vendor Orientation
      3.4 Compile Scorecards
      3.5 Conduct Business Alignment Meetings
      3.6 Work the 90-Day Plan
      3.7 Manage the 3-Year Roadmap
      3.8 Measure and Monitor Risk
      3.9 Issue Reports
      3.10 Develop/Improve Vendor Relationships
      3.11 Contribute to Other Processes

      4.1 Assess Compliance
      4.2 Incorporate Leading Practices
      4.3 Leverage Lessons Learned
      4.4 Maintain Internal Alignment
      4.5 Update Governances

      This phase will walk you through the following activities:

      Begin operating the VMI. The main outcomes from this phase are guidance and the steps required to implement your VMI.

      This phase involves the following participants:

      • VMI team
      • Applicable stakeholders and executives
      • Others as needed

      Jump Start Your Vendor Management Initiative

      Phase 3: Run

      Implement your processes and leverage your tools and templates.

      All of the hard work invested in Phase 1: Plan and Phase 2: Build begins to pay off in Phase 3: Run. It’s time to stand up your VMI and ensure that the proper level of resources is devoted to your vendors and the VMI itself. There’s more hard work ahead, but the foundational elements are in place. This doesn’t mean there won’t be adjustments and modifications along the way, but you are ready to use the tools and templates in the real world; you are ready to begin reaping the fruits of your labor.

      Phase 3: Run guides you through the process of collecting data, monitoring trends, issuing reports, and conducting effective meetings to:

      • Manage risk better.
      • Improve vendor performance.
      • Improve vendor relationships.
      • Identify areas where the parties can improve.
      • Improve communication between the parties.
      • Increase the value proposition with your vendors.

      Step 3.1: Classify vendors

      Begin classifying your top 25 vendors by spend.

      Step 3.1 sets the table for many of the subsequent steps in Phase 3: Run. The results of your classification process will determine: which vendors go through the scorecarding process (Step 3.4); which vendors participate in BAMs (Step 3.5); the nature and content of the vendor orientation activities (Step 3.3); which vendors will be part of the risk measurement and monitoring process (Step 3.8); which vendors will be included in the reports issued by the VMI (Step 3.9); and which vendors you will devote relationship-building resources to (Step 3.10).

      As you begin classifying your vendors, Info-Tech recommends using an iterative approach initially to validate the results from the classification model you configured in Step 2.1.

      1. Using the information from the Vendor Inventory tab (Step 1.7), identify your top 25 vendors by spend.
      2. Run your top 10 vendors by spend through the classification model and review the results.
        1. If the results are what you expected and do not contain any significant surprises, go to next page.
        2. If the results are not what you expected or contain significant surprises, look at the configuration page of the tool (Tab 1) and adjust the weights or the spend categories slightly. Be cautious in your evaluation of the results before modifying the configuration page – some legitimate results are unexpected or surprising based on bias. If you modify the weighting, review the new results and repeat your evaluation. If you modify the spend categories, review the answers on the vendor tabs to ensure that the answers are still accurate; review the new results and repeat your evaluation.

      Step 3.1: Classify vendors (cont.)

      Review your results and adjust the classification tool as needed.

      1. Run your top 11 through 25 vendors by spend through the classification model and review the results. Identify any unexpected results or surprises. Determine if further configuration makes sense and repeat the process outlined in 2.b, previous page, as necessary. If no further modifications are required, continue to 4, below.
      2. Share the preliminary results with the leadership team, executives, and stakeholders to obtain their approval or adjustments to the results.
        1. They may have questions and want to understand the process before approving the results.
        2. They may request that you move a vendor from one quadrant to another based on your organization’s roadmap, the vendor’s roadmap, or other information not available to you.
      3. Identify the vendors that will be part of the VMI at this stage – how many and which ones. Based on this number and the VMI’s scope (Step 1.2), make sure you have the resources necessary to accommodate the number of vendors participating in the VMI. Proceed cautiously and gradually increase the number of vendors participating in the VMI.

      Step 3.1: Classify vendors (cont.)

      Finalize the results and update VMI tools and templates.

      1. Update the Vendor Inventory tab (Step 1.7) to indicate the current classification status for the top 25 vendors by spend. Once your vendors have been classified, you can sort the Vendor Inventory tab by classification status to see all the vendors in that category at once.
      2. Review your 3-year roadmap (Step 2.9) and 90-day plans (Step 2.10) to determine if any modifications are needed to the activities and timelines.

      Additional classification considerations:

      • You should only have a few vendors that fit in the strategic category. As a rough guideline, no more than 5% to 10% of your IT vendors should end up in the strategic category. If you have a large number of vendors, even 5% may be too many. The classification model is an objective start to the classification process, but common sense must prevail over the “math” at the end of the day.
      • At this point, there is no need to go beyond the top 25 by spend. Most VMIs starting out can’t handle more than three to five strategic vendors initially. Allow the VMI to run a pilot program with a small sample size, work out any bugs, make adjustments, and then ramp up the VMI’s rollout in waves. Vendors can be added quarterly, biannually, or annually, depending upon the desired goals and available resources.

      Step 3.1: Classify vendors (cont.)

      Align your vendor strategy to your classification results.

      As your VMI matures, additional vendors will be part of the VMI. Review the table below and incorporate the applicable strategies into your deployment of vendor management principles over time. Stay true to your mission, goals, and scope, and remember that not all of your vendors are of equal importance.

      Operational Strategic
      • Focus on spend containment
      • Concentrate on lowering total cost of ownership
      • Invest moderately in cultivating the relationship
      • Conduct BAMs biannually or annually
      • Compile scorecards quarterly or biannually
      • Identify areas for performance and cost improvement
      • Focus on value, collaboration, and alignment
      • Review market intelligence for the vendor’s industry
      • Invest significantly in cultivating the relationship
      • Initiate executive-to-executive relationships
      • Conduct BAMs quarterly
      • Compile scorecards quarterly
      • Understand how the vendors view your organization

      Commodity

      Tactical

      • Investigate vendor rationalization and consolidation
      • Negotiate for the best-possible price
      • Leverage competition during negotiations
      • Streamline the purchasing and payment process
      • Allocate minimal VMI resources
      • Assign the lowest priority for vendor management metrics
      • Conduct risk assessments biannually or annually
      • Cultivate a collaborative relationship based on future growth plans or potential with the vendor
      • Conduct BAMs quarterly or biannually
      • Compile scorecards quarterly
      • Identify areas of performance improvement
      • Leverage innovation and creative problem solving

      Step 3.1: Classify vendors (cont.)

      Be careful when using the word “partner” with your strategic and other vendors.

      For decades, vendors have used the term “partner” to refer to the relationship they have with their clients and customers. In many regards, this is often an emotional ploy used by the vendors to get the upper hand. To fully understand the terms “partner” and “partnership” let’s evaluate them through two more-objective, less-cynical lenses.

      If you were to talk to your in-house or outside legal counsel, you may be told that partners share in profits and losses, and they have a fiduciary obligation to each other. Unless there is a joint venture between the parties, you are unlikely to have a partnership with a vendor from this perspective.

      What about a “business” partnership … one that doesn’t involve sharing profits and losses? What would that look like? Here are some indicators of a business partnership (or preferably a strategic alliance):

      • Trust and transparent communication exist.
      • You have input into the vendor’s roadmap for products and services.
      • The vendor is aligned with your desired outcomes and helps you achieve success.
      • You and the vendor are accountable for actions and inactions, with both parties being at risk.
      • There is parity in the peer-to-peer relationships between the organizations (e.g. C-Level to C-Level).
      • The vendor provides transparency in pricing models and proactively suggests ways for you to reduce costs.
      • You and the vendor work together to make each party better, providing constructive feedback on a regular basis.
      • The vendor provides innovative suggestions for you to improve your processes, performance, the bottom line, etc.
      • Negotiations are not one-sided; they are meaningful and productive, resulting in an equitable distribution of money and risk.

      Step 3.1: Classify vendors (cont.)

      Understand the implications and how to leverage the words “partner” and “partnership.”

      By now you might be thinking, “What’s all the fuss? Why does it matter?” At Info-Tech, we’ve seen firsthand how referring to the vendor as a partner can have the following impact:

      • Confidences are disclosed unnecessarily.
      • Negotiation opportunities and leverage are lost.
      • Vendors no longer have to earn the customer’s business.
      • Vendor accountability is missing due to shared responsibilities.
      • Competent skilled vendor resources are assigned to other accounts.
      • Value erodes over time since contracts are renewed without being competitively sourced.
      • One-sided relationships are established, and false assurances are provided at the highest levels within the customer organization.

      Proceed with caution when using partner or partnership with your vendors. Understand how your organization benefits from using these terms and mitigate the negatives outlined above by raising awareness internally to ensure people understand the psychology behind the terms. Finally, use the term to your advantage when warranted by referring to the vendor as a partner when you want or need something that the vendor is reluctant to provide. Bottom line: Be strategic in how you refer to vendors and know the risks.

      Step 3.2: Conduct internal “kickoff” meeting

      Raise awareness about the VMI and its mission, vision, and goals.

      To be effective, your VMI needs executive support, a clear vision, appropriate governances and tools, personnel with the right skills, and other items discussed in this blueprint. However, the VMI doesn’t exist in a vacuum … it can’t sit back and be reactive. As part of being proactive, the VMI must be aware of its brand and “market” its services. An effective way to market the VMI is to conduct an internal kickoff meeting. There are at least a couple of ways to do this:

      • Host a meeting for stakeholders, executives, and others who will be contributing to the VMI processes (but are not part of the VMI). The meeting can be part of a townhall or standalone meeting; it can be done live or via a recorded video.
      • Attend appropriate staff meetings and make your presentation.

      With either approach above or one of your choosing, keep in mind the following objectives for your kickoff meeting:

      • Make sure you provide a way for those in attendance to ask questions at that time and later. You want to create and foster a communication loop with the people who will be impacted by the VMI or participating with it.
      • Raise awareness of your existence and personnel. Tell the VMI’s story by sharing your mission statement, goals, and scope; this will help dispel (or confirm) rumors about the VMI that often lead to confusion and faulty assumptions.
      • As you share the VMI’s vision, connect the story to how the VMI will impact the organization and individuals and to how they can help. The VMI tends to be the least autonomous area within an organization; it needs the assistance of others to be successful. Convey an atmosphere of collaboration and appreciation for their help.

      Host a kickoff meeting annually to kickoff the new year. Remind people of your story, announce successes from the past year, and indicate what the future year holds. Keep it brief, make it personal for the audience, and help them connect the names of VMI personnel to faces.

      Step 3.3: Conduct vendor orientation

      Introduce your VMI to your top vendors.

      Based on the results from your vendor classification (Step 3.1) and your VMI deployment timeline, identify the vendors who will participate in the initial orientation meetings. Treat the orientation as a formal, required meeting for the vendors to attend. Determine the attendee list for your organization and the vendors, and send out invites. Ideally, you will want the account manager, a sales director or vice president, the “delivery” director or vice president, and an executive from the vendor in the meeting. From the customer side, you may need more than one or two people from the VMI to entice the vendor’s leadership team to attend; you may need attendance from your own leadership team to add weight or credibility to the meeting (unfortunately).

      Before going into the meeting, make sure everyone on your side knows their roles and responsibilities, and review the agenda. Control the agenda or the meeting is likely to get out of hand and turn into a sales call.

      Conduct orientation meetings even if the participating vendors have been doing business with you for several years. Don’t assume they know all about your organization and your VMI (even if their other clients have a VMI).

      Run two or three orientation meetings and then review the “results.” What needs to be modified? What lessons have you learned? Make any necessary adjustments and continue rolling out the orientation meetings.

      Early in the VMI’s deployment, reorientation and debrief may not be in play. As time passes, it is important to remember them! Use them when warranted to help with vendor alignment.

      Step 3.4: Compile scorecards

      Begin scoring your top vendors.

      The scorecard process typically is owned and operated by the VMI, but the actual rating of the criteria within the measurement categories is conducted by those with day-to-day interactions with the vendors, those using or impacted by the services and products provided by the vendors, and those with the skills to research other information on the scorecard (e.g. risk). Chances are one person will not be able to complete an entire scorecard by themselves. As a result, the scorecard process is a team sport comprising sub-teams where necessary.

      The VMI will compile the scores, calculate the final results, and aggregate all of the comments into one scorecard. There are two common ways to approach this task:

      1. Send out the scorecard template to those who will be scoring the vendor and ask them to return it when completed, providing them with a due date a few days before you actually need it; you’ll need time to compile, calculate, and aggregate.
      2. Invite those who will be scoring the vendor to a meeting and let the contributors use that time to score the vendors; make VMI team members available to answer questions and facilitate the process.

      Step 3.4: Compile scorecards (cont.)

      Gather input from stakeholders and others impacted by the vendors.

      Since multiple people will be involved in the scorecarding process or have information to contribute, the VMI will have to work with the reviewers to ensure that the right mix of data is provided. For example:

      • If you are tracking lawsuits filed by or against the vendor, one person from Legal may be able to provide that, but they may not be able to evaluate any other criteria on the scorecard.
      • If you are tracking salesperson competencies, multiple people from multiple areas may have valuable insights.
      • If you are tracking deliverable timeliness, several project managers may want to contribute across several projects.

      Where one person is contributing exclusively to limited criteria, make it easy for the person to identify the criteria they are to evaluate. When multiple people from the same functional area will provide insights, they can contribute individually (and the VMI will average their responses) or they can respond collectively after reaching consensus among themselves.

      After the VMI has compiled, calculated, and aggregated, share the results with executives, impacted stakeholders, and others who will be attending the BAM for that vendor. Depending upon the comments provided by internal personnel, you may need to create a sanitized version of the scorecard for the vendor.

      Make sure your process timeline has a buffer built in. You’ll be sending the final scorecard to the vendor three to five days before the BAM, and you’ll need some time to assemble the results. The scorecarding process can be perceived as a low-priority activity for people outside of the VMI, and other “priorities” will arise for them. Without a timeline buffer, the VMI may find itself behind schedule and unprepared due to things beyond its control.

      Step 3.5: Conduct business alignment meetings

      Determine which vendors will participate and how long the meetings will last.

      At their core, BAMs aren’t that different from any other meeting. The basics of running a meeting still apply, but there are a few nuances that apply to BAMs Set out below are leading practices for conducing your BAMs; adapt them to meet your needs and suit your environment.

      Who

      Initially, BAMs are conducted with the strategic vendors in your pilot program. Over time, you’ll add vendors until all of your strategic vendors are meeting with you quarterly. After that, roll out the BAMs to those tactical and operational vendors located close to the strategic quadrant in the classification model (Steps 2.1 and 3.1) and as VMI resources allow. It may take several years before you are holding regular BAMs with all of your strategic, tactical, and operational vendors.

      Duration

      Keep the length of your meetings reasonable. The first few with a vendor may need to be 60 to 90 minutes long. After that, you should be able to trim them to 45 to 60 minutes. The BAM does not have to fill the entire time. When you are done, you are done.

      Step 3.5: Conduct business alignment meetings (cont.)

      Identify who will be invited and send out invitations.

      Invitations

      Set up a recurring meeting whenever possible. Changes will be inevitable, but keeping the timeline regular works to your advantage. Also, the vendors included in your initial BAMs won’t change for twelve months. For the first BAM with a vendor, provide adequate notice; four weeks is sufficient in most instances, but calendars will fill up quickly for the main attendees from the vendor. Treat the meeting as significant and make sure your invitation reflects this. A simple meeting request will often be rejected, treated as optional, or ignored completely by the vendor’s leadership team (and maybe yours as well!).

      Invitees

      Internal invitees should include those with a vested interest in the vendor’s performance and the relationship. In addition, other functional areas may be invited based on need or interest. Be careful the attendee list doesn’t get too big. Based on this, internal BAM attendees often include representatives from IT, Sourcing/Procurement, and the applicable business units. At times, Finance and Legal are included.

      From the vendor’s side, strive to have decision makers and key leaders attend. The salesperson/account manager is often included for continuity, but a director or vice president of sales will have more insights and influence. The project manager is not needed at this meeting due to the nature of the meeting and its agenda; however, a director or vice president from the “product or service delivery” area is a good choice. Bottom line: get as high into the vendor’s organization as possible whenever possible; look at the types of contracts you have with that vendor to provide guidance on the type of people to invite.

      Step 3.5: Conduct business alignment meetings (cont.)

      Prepare for the meetings and maintain control.

      Preparation

      Send the scorecard and agenda to the vendor five days prior to the BAM. The vendor should provide you with any information you require for the meeting five days prior as well.

      Decide who will run the meeting. Some customers like to lead and others let the vendor present. How you craft the agenda and your preferences will dictate who runs the show.

      Make sure the vendor knows what materials it should bring to the meeting or have access to. This will relate to the agenda and any specific requests listed under the discussion points. You don’t want the vendor to be caught off guard and unable to discuss a matter of importance to you.

      Running the BAM

      Regardless of which party leads, make sure you manage the agenda to stay on topic. This is your meeting – not the vendor’s, not IT’s, not Procurement’s or Sourcing’s. Don’t let anyone hijack it.

      Make sure someone is taking notes. If you are running this virtually, consider recording the meeting. Check with your legal department first for any concerns, notices, or prohibitions that may impact your recording the session.

      As a reminder, this is not a sales call, and this is not a social activity. Innovation discussions are allowed and encouraged, but that can quickly devolve into a sales presentation. People can be friendly toward one another, but the relationship building should not overwhelm the other purposes.

      Step 3.5: Conduct business alignment meetings (cont.)

      Follow these additional guidelines to maximize your meetings.

      More Leading Practices

      • Remind everyone that the conversation may include items covered by various confidentiality provisions or agreements.
      • Publish the meeting minutes on a timely basis (within 48 hours).
      • Focus on the bigger picture by looking at trends over time; get into the details only when warranted.
      • Meet internally immediately beforehand to prepare – don’t go in cold; review the agenda and the roles and responsibilities for the attendees.
      • Physical meetings are better than virtual meetings, but travel constraints, budgets, and pandemics may not allow for physical meetings.

      Final Thoughts

      • When performance or the relationship is suffering, be constructive in your feedback and conversations rather than trying to assign blame; lead with the carrot rather than the stick.
      • Look for collaborative solutions whenever possible and avoid referencing the contract if possible. Communicate your willingness to help resolve outstanding issues.
      • Use inclusive language and avoid language that puts the vendor on the defensive.
      • Make sure that your meetings are not focused exclusively on the negative, but don’t paint a rosy picture where one doesn’t exist.
      • A vendor that is doing well should be commended. This is an important part of relationship building.

      Step 3.6: Work the 90-day plan

      Monitor your progress and share your results.

      Having a 90-day plan is a good start, but assuming the tasks on the plan will be accomplished magically or without any oversight can lead to failure. While it won’t take a lot of time to work the plan, following a few basic guidelines will help ensure the 90-day plan gets results and wasn’t created in vain.

      90-Day Plan: Activity 1; Activity 2; Activity 3; Activity 4; Activity 5
      1. Measure and track your progress against the initial/current 90-day plan at least weekly; with a short timeline, any delay can have a huge impact.
      2. If adjustments are needed to any elements of the plan, understand the cause and the impact of those adjustments before making them.
      3. Make adjustments ONLY when warranted. The temptation will be to push activities and tasks further out on the timeline (or to the next 90-day plan!) when there is any sort of “hiccup” along the way, especially when personnel outside the VMI are involved. Hold true to the timeline whenever possible; once you start slipping, it often becomes a habit.
      4. Report on progress every week and hold people accountable for their assignments and contributions.
      5. Take the 90-day plan seriously and treat it as you would any significant project – this is part of the VMI’s branding and image.

      Step 3.7: Manage the 3-year roadmap

      Keep an eye on the future since it will feed the present.

      The 3-year roadmap is a great planning tool, but it is not 100% reliable. There are inherent flaws and challenges. Essentially, the roadmap is a set of three “crystal balls” attempting to tell you what the future holds. The vision for Year 1 may be fairly clear, but for each subsequent year, the crystal ball becomes foggier. In addition, the timeline is constantly changing; before you know it, tomorrow becomes today and Year 2 becomes Year 1.

      To help navigate through the roadmap and maximize its potential, follow these principles:

      • Manage each year of the roadmap differently.
        • Review the Year 1 map each quarter to update your 90-day plans (See steps 2.10 and 3.6).
        • Review the Year 2 map every six months to determine if any changes are necessary. As you cycle through this, your vantage point of Year 2 will be 6 months or 12 months away from the beginning of Year 2, and time moves quickly.
        • Review the Year 3 map annually, and determine what needs to be added, changed, or deleted. Each time you review Year 3, it will be a “new” Year 3 that needs to be built.
      • Analyze the impact on the proposed modifications from two perspectives: 1) What is the impact if a requested modification is made? 2) What is the impact if a requested modification is not made?
      • Validate all modifications with leadership and stakeholders before updating the 3-year roadmap to ensure internal alignment.

      Step 3.8: Measure and monitor risk

      Understand and manage risk levels.

      Using the configured Vendor Risk Assessment Tool (Step 2.2), confirm which risks you will be measuring and monitoring and identify the vendors that will be part of the initial risk management process. Generally, organizations start measuring and monitoring risk in two to five risk categories for two or three strategic vendors. Over time, additional risk categories and/or vendors can be added in waves. Resist the temptation to add risk categories or vendors into the mix too quickly. Expanding requires resources inside and outside of the VMI.

      The VMI will rely heavily on other areas to provide input or the risk data, and the VMI needs to establish good working relationships with those areas. For example, if legal risk is something being measured and monitored, the VMI will need data from Legal on the number and nature of any lawsuits filed by or against the applicable vendors; the VMI will need data from Legal, Contract Management, or Procurement/Sourcing on the number and nature of any agreed upon deviations from your organization’s preferred contract terms that increase legal risk.

      With respect to risk, the VMI’s main role is threefold: 1) take the data obtained from others (or in some instances the VMI may have the data) and turn it into useful information, 2) monitor the risk categories over time and periodically issue reports, and 3) work with other areas to manage the risk.

      Step 3.9: Issue reports

      Inform internal personnel and vendors about trends, issues, progress, and results.

      Issuing the reports created in Step 2.12 is one of the main ways the VMI 1) will communicate with internal and external personnel and 2) track trends and information over time. Even with input from the potential reviewers of the reports, you’ll still want to seek their feedback and input periodically. It may take a few iterations until the reports are hitting their mark. You may find that a metric is no longer required, that a metric is missing completely or it is missing a component, or a formatting change would improve the report’s readability. Once a report has been “finalized,” try not to change it until you are engaged in Phase 4: Review activities. It can be unsettling for the reviewers when reports change constantly.

      Whenever possible, find ways to automate the reports. While issuing reports is critical, the function should not consume more time than necessary. Automation can remove some of the manual and repetitive tasks.

      Internal reports may need to be kept confidential. An automated dashboard or reporting tool can help lock down who has access to the information. At a minimum, the internal reports should contain a “Confidential” stamp, header, watermark, or other indicator that the materials are sensitive and should not be disclosed outside of your organization without approval.

      Reports for vendors may not need to be sent as often as reports are generated or prepared for internal personnel. Establish a cadence by classification model category and stick to it. Letting each vendor choose the frequency will make it more difficult for you to manage. The vendors can choose to ignore the report if they so choose.

      This is an image of an example of a bar graph showing ROI and Benchmark for Categories 1-6

      Step 3.10: Develop/improve vendor relationships

      Drive better performance through better relationships.

      One of the key components of a VMI is relationship management. Good relationships with your vendors provide many benefits for both parties, but they don’t happen by accident. Do not assume the relationship will be good or is good merely because your organization is buying products and services from a vendor.

      In many respects, the VMI should mirror a vendor’s sales organization by establishing relationships at multiple levels within the vendor organizations – not just with the salesperson or account manager. Building and maintaining relationships is hard work, but the return on investment makes it worthwhile.

      Business relationships are comprised of many components, not all of which have to be present to have a great relationship. However, there are some essential components. Whether you are trying to develop, improve, or maintain a relationship with a vendor, make sure you are conscious of the following:*

      • Focus your energies on strategic vendors first and then tactical and operational vendors.
      • Be transparent and honest in your communications.
      • Continue building trust by being responsive and honoring commitments (timely).
      • Create a collaborative environment and build upon common ground.
      • Thank the vendor when appropriate.
      • Resolve disputes early, avoid the “blame game,” and be objective when there are disagreements.

      Step 3.11: Contribute to other processes

      Continue assisting others and managing roles and responsibilities outside of the VMI.

      The VMI has processes that it owns and processes that it contributes to. Based on the VMI scope (Step 1.2), the OIC chart (Step 1.4), and the process mapping activities (Step 1.5), ensure that the VMI is honoring its contribution commitments. This is often easier said than done though. A number of factors can make it difficult to achieve the balance required to handle VMI processes and contribute to other processes associated with the VMI’s mission and vision. Understanding the issues is half the battle. If you see signs of these common “vampires,” take action quickly to address the situation.

      • The VMI’s first focus is often internal, and the tendency is to operate in a bubble. Classifying vendors, running BAMs, coordinating the risk process, and other inward-facing processes can consume all of the VMI’s energy. As a result, there is little time, effort, or let’s be honest, desire to participate in other processes outside of the VMI.
      • It is easy for VMI personnel to get dragged into processes and situations that are outside of its scope. This often happens when personnel join the VMI from other internal areas or departments and have good relationships with their former teammates. The relationships make it hard to say “No” when out-of-scope assistance is being requested.
      • The VMI may have “part-time” personnel who have responsibilities across internal departments, divisions, agencies, or teams. When the going gets tough and time is at a premium, people gravitate toward the easiest or most comfortable work. That work may not be VMI work.

      Phase 4: Review

      Keep Your VMI Up to Date and Running Smoothly

      Phase 1Phase 2Phase 3Phase 4
      1.1 Mission Statement and Goals


      1.2 Scope

      1.3 Strengths and Obstacles

      1.4 Roles and Responsibilities

      1.5 Process Mapping

      1.6 Charter

      1.7 Vendor Inventory

      1.8 Maturity Assessment

      1.9 Structure

      2.1 Classification Model
      2.2 Risk Assessment Tool
      2.3 Scorecards and Feedback
      2.4 Business Alignment Meeting Agenda
      2.5 Relationship Alignment Document
      2.6 Vendor Orientation
      2.7 Job Descriptions
      2.8 Policies and Procedures
      2.9 3-Year Roadmap
      2.10 90-Day Plan
      2.11 Quick Wins
      2.12 Reports

      3.1 Classify Vendors
      3.2 Conduct Internal “Kickoff” Meeting
      3.3 Conduct Vendor Orientation
      3.4 Compile Scorecards
      3.5 Conduct Business Alignment Meetings
      3.6 Work the 90-Day Plan
      3.7 Manage the 3-Year Roadmap
      3.8 Measure and Monitor Risk
      3.9 Issue Reports
      3.10 Develop/Improve Vendor Relationships
      3.11 Contribute to Other Processes

      4.1 Assess Compliance
      4.2 Incorporate Leading Practices
      4.3 Leverage Lessons Learned
      4.4 Maintain Internal Alignment
      4.5 Update Governances

      This phase will walk you through the following activities:

      Identify what the VMI should stop doing, start doing, and continue doing as it improves and matures. The main outcomes from this phase are ways to advance the VMI and maintain internal alignment.

      This phase involves the following participants:

      • VMI team
      • Applicable stakeholders and executives
      • Others as needed

      Jump Start Your Vendor Management Initiative

      Phase 4: Review

      Keep your VMI up to date and running smoothly.

      As the old adage says, “The only thing constant in life is change.” This is particularly true for your VMI. It will continue to mature; people inside and outside of the VMI will change; resources will expand or contract from year to year; your vendor base will change. As a result, your VMI needs the equivalent of a physical every year. In place of bloodwork, x-rays, and the other paces your physician may put you through, you’ll assess compliance with your policies and procedures, incorporate leading practices, leverage lessons learned, maintain internal alignment, and update governances.

      Be thorough in your actions during this Phase to get the most out of it. It requires more than the equivalent of gauging a person’s health by taking their temperature, measuring their blood pressure, and determining their body mass index. Keeping your VMI up to date and running smoothly takes hard work.

      Some of the items presented in this Phase require an annual review; others may require quarterly review or timely review (i.e. when things are top of mind and current). For example, collecting lessons learned should happen on a timely basis rather than annually, and classifying your vendors should occur annually rather than every time a new vendor enters the fold.

      Ultimately, the goal is to improve over time and stay aligned with other areas internally. This won’t happen by accident. Being proactive in the review of your VMI further reinforces the nature of the VMI itself – proactive vendor management, NOT reactive!

      Step 4.1: Assess compliance

      Determine what is functionally going well and not going well.

      Whether you have a robust set of vendor management-related policies and procedures or they are the bare minimum, gathering data each quarter and conducting an assessment each year will provide valuable feedback. The scope of your assessment should focus on two concepts: 1) are the policies and procedures being followed and 2) are the policies and procedures accurate and relevant. This approach requires parallel thinking, but it will help you understand the complete picture and minimize the amount of time required.

      Use the steps listed below (or modify them for your culture) to conduct your assessment:

      • Determine the type of assessment – formal or informal.
      • Determine the scale of the assessment – which policies and procedures will be reviewed and how many people will be interviewed.
      • Determine the compliance levels, and seek feedback on the policies and procedures – what is going well and what can be improved?
      • Review the compliance deviations.
      • Conduct a root cause analysis for the deviations.
      • Create a list of improvements and gain approval.
      • Create a plan for minimizing noncompliance in the future.
        • Improve/increase education and awareness.
        • Clarify/modify policies and procedures.
        • Add resources, tools, and people (as necessary and as allowed).

      Step 4.2: Incorporate leading practices

      Identify and evaluate what external VMIs are doing.

      The VMI’s world is constantly shifting and evolving. Some changes will take place slowly, while others will occur quickly. Think about how quickly the cloud environment has changed over the past five years versus the 15 years before that; or think about issues that have popped up and instantly altered the landscape (we’re looking at you COVID-19 and ransomware). As a result, the VMI needs to keep pace, and one of the best ways to do that is to incorporate leading practices.

      At a high level, a leading practice is a way of doing something that is better at producing a particular outcome or result or performing a task or activity than other ways of proceeding. The leading practice can be based on methodologies, tools, processes, procedures, and other items. Leading practices change periodically due to innovation, new ways of thinking, research, and other factors. Consequently, a leading practice is to identify and evaluate leading practices each year.

      Step 4.2: Incorporate leading practices (cont.)

      Update your VMI based on your research.

      • A simple approach for incorporating leading practices into your regular review process is set out below:
      • Research:
        • What other VMIs in your industry are doing.
        • What other VMIs outside your industry are doing.
        • Vendor management in general.
      • Based on your results, list specific leading practices others are doing that would improve your VMI (be specific – e.g. other VMIs are incorporating risk into their classification process).
      • Evaluate your list to determine which of these potential changes fit or could be modified to fit your culture and environment.
      • Recommend the proposed changes to leadership (with a short business case or explanation/justification, as needed) and gain approval.

      Remember: Leading practices or best practices may not be what is best for you. In some instances, you will have to modify them to fit your culture and environment; in other instances, you will elect not to implement them at all (in any form).

      Step 4.3: Leverage lessons learned

      Tap into the collective wisdom and experience of your team members.

      There are many ways to keep your VMI running smoothly, and creating a lessons learned library is a great complement to the other ways covered in this Phase 4: Review. By tapping into the collective wisdom of the team and creating a safe feedback loop, the VMI gains the following benefits:

      • Documented institutional wisdom and knowledge normally found only in the team members’ brains.
      • The ability for one team member to gain insights and avoid mistakes without having to duplicate the events leading to the insights or mistakes.
      • Improved methodologies, tools, processes, procedures, skills, and relationships.

      Many of the processes raised in this Phase can be performed annually, but a lessons learned library works best when the information is “deposited” in a timely manner. How you choose to set up your lessons learned process will depend on the tools you select and your culture. You may want to have regular “input” meetings to share the lessons as they are being deposited, or you may require team members to deposit lessons learned on a regular basis (within a week after they happen, monthly, or quarterly). Waiting too long can lead to vague or lost memories and specifics – timeliness of the deposits is a crucial element.

      Step 4.3: Leverage lessons learned (cont.)

      Create a library to share valuable information across the team.

      Lessons learned are not confined to identifying mistakes or dissecting bad outcomes. You want to reinforce good outcomes as well. When an opportunity for a lessons-learned deposit arises, identify the following basic elements:

      • A brief description of the situation and outcome.
      • What went well (if anything) and why did it go well?
      • What didn't go well (if anything) and why didn't it go well?
      • What would/could you do differently next time?
      • A synopsis of the lesson(s) learned.

      Info-Tech Insights

      The lessons learned library needs to be maintained. Irrelevant material needs to be culled periodically, and older or duplicate material may need to be archived.

      The lessons learned process should be blameless. The goal is to share insightful information … not to reward or punish people based on outcomes or results.

      Step 4.4: Maintain internal alignment

      Review the plans of other internal areas to stay in sync.

      Maintaining internal alignment is essential for the ongoing success of the VMI. Over time, it is easy to lose sight of the fact that the VMI does not operate in a vacuum; it is an integral component of a larger organization whose parts must work well together to function optimally. Focusing annually on the VMI’s alignment within the enterprise helps reduce any breakdowns that could derail the organization.

      To ensure internal alignment:

      • Review the key components of the applicable materials from Phase 1: Plan and Phase 2: Build with the appropriate members of the leadership team (e.g. executives, sponsors, and stakeholders). Not every item from those Phases and Steps needs to be reviewed, but err on the side of caution for the first set of alignment discussions, and be prepared to review each item. You can gauge the audience’s interest on each topic and move quickly when necessary or dive deeper when needed. Identify potential changes required to maintain alignment.
      • Review the strategic plans (e.g. 1-, 3-, and 5- year plans) for various portions of the organization if you have access to them or gather insights if you don’t have access.
        • If the VMI is under the IT umbrella, review the strategic plans for IT and its departments.
        • Review the strategic plans for the areas the VMI works with (e.g. Procurement, Business Units).
        • The organization itself.
      • Create and vet a list of modifications to the VMI and obtain approval.
      • Develop a plan for making the necessary changes.

      Step 4.5: Update governances

      Revise your protocols and return to the beginning of cyclical processes.

      You’re at the final Step and ready to update governances. This is comprised of two sequential paths.

      • First, use the information from Steps 4.1-4.4 to make any required modifications to the items in Phase 1: Plan, Phase 2: Build, and Phase 3: Run. For example, you may need to update your policies and procedures (Step 2.8) based on your findings in Step 4.1; or you may need to update the VMI’s scope (Step 1.2) to ensure internal alignment issues identified in Step 4.4. are accounted for.
      • Second, return to Phase 3: Run to perform the activities below; they tend to be performed annually, but use your discretion and perform them on an as-needed basis:
        • Reclassify vendors.
        • Complete a new maturity assessment.
        • Run reorientation sessions for vendors.
        • Conduct a kickoff meeting to update internal personnel.

      Other activities and tasks (e.g. scorecards and BAMs) may be impacted by the modifications made above, but the nature of their performance follows a shorter cadence. As a result, they are not specifically called out here in this Step 4.5 since they are performed on an ongoing basis. However, don’t overlook them as part of your update.

      Summary of Accomplishment

      Problem Solved

      Vendor management is a broad, often overwhelming, comprehensive spectrum that encompasses many disciplines. By now, you should have a great idea of what vendor management can or will look like in your organization. Focus on the basics first: Why does the VMI exist and what does it hope to achieve? What is its scope? What are the strengths you can leverage, and what obstacles must you manage? How will the VMI work with others? From there, the spectrum of vendor management will begin to clarify and narrow.

      Leverage the tools and templates from this blueprint and adapt them to your needs. They will help you concentrate your energies in the right areas and on the right vendors to maximize the return on your organization’s investment in the VMI of time, money, personnel, and other resources. You may have to lead by example internally and with your vendors at first, but they will eventually join you on your path if you stay true to your course.

      At the heart of a good VMI is the relationship component. Don’t overlook its value in helping you achieve your vendor management goals. The VMI does not operate in a vacuum, and relationships (internal and external) will be critical.

      Lastly, seek continual improvement from the VMI and from your vendors. Both parties should be held accountable, and both parties should work together to get better. Be proactive in your efforts, and you, the VMI, and the organization will be rewarded.

      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

      Related Info-Tech Research

      Prepare for Negotiations More Effectively

      Don't leave negotiation preparations and outcomes to chance. Learn how to prepare for negotiations more effectively and improve your results.

      Understand Common IT Contract Provisions to Negotiate More Effectively

      Info-Tech’s guidance and insights will help you navigate the complex process of contract review and identify the key details necessary to maximize the protections for your organization.

      Capture and Market the ROI of Your VMO

      Calculating the impact or value of a vendor management office (VMO) can be difficult without the right framework and tools. Let Info-Tech’s tools and templates help you account for the contributions made by your VMO.

      Bibliography

      “Best Practices for Writing Corporate Policies and Procedures.” PowerDMS, 29 Dec. 2020. Accessed 11 January 2022.

      Duncan. “Top 10 Tips for Creating Compelling Reports.” Design Eclectic, 11 October 2019. Accessed 29 March 2022.

      Eby, Kate. “Master Writing Policies, Procedures, Processes, and Work Instructions.” 1 June 2018, updated 19 July 2021. Accessed 11 January 2022.

      “Enterprise Risk Management.” Protiviti, n.d. Accessed 16 Feb. 2017.

      Geller & Company. “World-Class Procurement — Increasing Profitability and Quality.” Spend Matters, 2003. Accessed 4 March 2019.

      Guth, Stephen. “Vendor Relationship Management Getting What You Paid for (And More).” Citizens, 26 Feb. 2015. Web.

      Guth, Stephen. The Vendor Management Office: Unleashing the Power of Strategic Sourcing. Lulu.com, 2007. Print.

      “ISG Index 4Q 2021.” Information Services Group, Inc., 2022. Web.

      “Six Tips for Making a Quality Report Appealing and Easy To Skim.” AHRQ, Oct. 2019. Accessed 29 March 2022.

      Tucker, Davis. “Marketing Reporting: Tips to Create Compelling Reports.” 60 Second Marketer, 28 March 2020. Accessed 29 March 2022.

      “Why Do We Perform Better When Someone Has High Expectations of Us?” The Decision Lab, 9 Sept. 2020. Accessed 31 January 2022.

      Data Architecture

      • Buy Link or Shortcode: {j2store}17|cart{/j2store}
      • Related Products: {j2store}17|crosssells{/j2store}
      • member rating overall impact: 9.5/10
      • member rating average dollars saved: $30,159
      • member rating average days saved: 5
      • Parent Category Name: Data and Business Intelligence
      • Parent Category Link: /data-and-business-intelligence
      Enable the business to achieve operational excellence, client intimacy, and product leadership with an innovative, agile, and fit-for-purpose data architecture practice

      Customer Relationship Management Platform Selection Guide

      • Buy Link or Shortcode: {j2store}529|cart{/j2store}
      • member rating overall impact: 9.2/10 Overall Impact
      • member rating average dollars saved: $14,719 Average $ Saved
      • member rating average days saved: 32 Average Days Saved
      • Parent Category Name: Customer Relationship Management
      • Parent Category Link: /customer-relationship-management
      • Customer relationship management (CRM) suites are an indispensable part of a holistic strategy for managing end-to-end customer interactions.
      • After defining an approach to CRM, selection and implementation of the right CRM suite is a critical step in delivering concrete business value for marketing, sales, and customer service.
      • Despite the importance of CRM selection and implementation, many organizations struggle to define an approach to picking the right vendor and rolling out the solution in an effective and cost-efficient manner.
      • IT often finds itself in the unenviable position of taking the fall for CRM platforms that don't deliver on the promise of the CRM strategy.

      Our Advice

      Critical Insight

      • IT needs to be a trusted partner in CRM selection and implementation, but the business also needs to own the requirements and be involved from the beginning.
      • CRM requirements dictate the components of the target CRM architecture, such as deployment model, feature focus, and customization level. Savvy application directors recognize the points in the project where the CRM architecture model necessitates deviations from a "canned" roll-out plan.
      • CRM selection is a multi-step process that involves mapping target capabilities for marketing, sales, and customer service, assigning requirements across functional categories, determining the architecture model to prioritize criteria, and developing a comprehensive RFP that can be scored in a weighted fashion.
      • Companies that succeed with CRM implementation create a detailed roadmap that outlines milestones for configuration, security, points of implementation, data migration, training, and ongoing application maintenance.

      Impact and Result

      • A CRM platform that effectively meets the needs of marketing, sales, and customer service and delivers value.
      • Reduced costs during CRM selection.
      • Reduced implementation costs and time frame.
      • Faster time to results after implementation.

      Customer Relationship Management Platform Selection Guide Research & Tools

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

      1. Customer Relationship Management Platform Selection Guide – Speed up the process to build your business case and select your CRM solution.

      This blueprint will help you build a business case for selecting the right CRM platform, defining key requirements, and conducting a thorough analysis and scan of the ever-evolving CRM market space.

      • Customer Relationship Management Platform Selection Guide — Phases 1-3

      2. CRM Business Case Template – Document the key drivers for selecting a new CRM platform.

      Having a sound business case is essential for succeeding with a CRM. This template will allow you to document key drivers and impact, in line with the CRM Platform Selection Guide blueprint.

      • CRM Business Case Template

      3. CRM Request for Proposal Template

      Create your own request for proposal (RFP) for your customer relationship management (CRM) solution procurement process by customizing the RFP template created by Info-Tech.

      • CRM Request for Proposal Template

      4. CRM Suite Evaluation and RFP Scoring Tool

      The CRM market has many strong contenders and differentiation may be difficult. Instead of relying solely on reputation, organizations can use this RFP tool to record and objectively compare vendors according to their specific requirements.

      • CRM Suite Evaluation and RFP Scoring Tool

      5. CRM Vendor Demo Script

      Use this template to support your business's evaluation of vendors and their solutions. Provide vendors with scenarios that prompt them to display not only their solution's capabilities, but also how the tool will support your organization's particular needs.

      • CRM Vendor Demo Script

      6. CRM Use Case Fit Assessment Tool

      Use this tool to help build a CRM strategy for the organization based on the specific use case that matches your organizational needs.

      • CRM Use-Case Fit Assessment Tool
      [infographic]

      Further reading

      Customer Relationship Management Platform Selection Guide

      Speed up the process to build your business case and select your CRM solution.

      Table of Contents

      1. Analyst Perspective
      2. Executive Summary
      3. Blueprint Overview
      4. Executive Brief
      5. Phase 1: Understand CRM Functionality
      6. Phase 2: Build the Business Case and Elicit CRM requirements
      7. Phase 3: Discover the CRM Marketspace and Prepare for Implementation
      8. Conclusion

      Analyst Perspective

      A strong CRM platform is paramount to succeeding with customer engagement.

      Modern CRM platforms are the workhorses that provide functional capabilities and data curation for customer experience management. The market for CRM platforms has seen an explosion of growth over the last five years, as organizations look to mature their ability to deliver strong capabilities across marketing, sales, and customer service.

      IT needs to be a trusted partner in CRM selection and implementation, but the business also needs to own the requirements and be involved from the get-go.

      CRM selection must be a multistep process that involves defining target capabilities for marketing, sales, and customer service, prioritizing requirements across functional categories, determining the architecture model for the CRM environment, and developing a comprehensive RFP that can be scored in a weighted fashion.

      To succeed with CRM implementation, create a detailed roadmap that outlines milestones for configuration, security, points of implementation, data migration, training, and ongoing application maintenance.

      Photo of Ben Dickie, Research Lead, Customer Experience Strategy, Info-Tech Research Group. Ben Dickie
      Research Lead, Customer Experience Strategy
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      Customer Relationship Management (CRM) suites are an indispensable part of a holistic strategy for managing end-to-end customer interactions. Selecting the right platform that aligns with your requirements is a significant undertaking.

      After defining an approach to CRM, selection and implementation of the right CRM suite is a critical step in delivering concrete business value for marketing, sales, and customer service.
      Common Obstacles

      Despite the importance of CRM selection and implementation, many organizations struggle to define an approach to picking the right vendor and rolling out the solution in an effective and cost-efficient manner.

      The CRM market is rapidly evolving and changing, making it tricky to stay on top of the space.

      IT often finds itself in the unenviable position of taking the fall for CRM platforms that don’t deliver on the promise of the CRM strategy.
      Info-Tech’s Approach

      CRM platform selection must be driven by your overall customer experience management strategy: link your CRM selection to your organization’s CXM framework.

      Determine if you need a CRM platform that skews toward marketing, sales, or customer service; leverage use cases to help guide selection.

      Ensure strong points of integration between CRM and other software such as MMS. A CRM should not live in isolation; it must provide a 360-degree view.

      Info-Tech Insight

      IT must work in lockstep with its counterparts in marketing, sales, and customer service to define a unified vision for the CRM platform.

      Info-Tech’s methodology for selecting the right CRM platform

      1. Understand CRM Features 2. Build the Business Case & Elicit CRM Requirements 3. Discover the CRM Market Space & Prepare for Implementation
      Phase Steps
      1. Define CRM platforms
      2. Classify table stakes & differentiating capabilities
      3. Explore CRM trends
      1. Build the business case
      2. Streamline requirements elicitation for CRM
      3. Construct the RFP
      1. Discover key players in the CRM landscape
      2. Engage the shortlist & select finalist
      3. Prepare for implementation
      Phase Outcomes
      • Consensus on scope of CRM and key CRM capabilities
      • CRM selection business case
      • Top-level use cases and requirements
      • Completed CRM RFP
      • CRM market analysis
      • Shortlisted vendor
      • Implementation considerations

      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.

      The CRM purchase process should be broken into segments:

      1. CRM vendor shortlisting with this buyer’s guide
      2. Structured approach to selection
      3. Contract review

      What does a typical GI on this topic look like?

      Phase 1

      Phase 2

      Phase 3

      Call #1: Understand what a CRM platform is and the “art of the possible” for sales, marketing, and customer service. Call #2: Build the business case to select a CRM.

      Call #3: Define your key CRM requirements.

      Call #4: Build procurement items such as an RFP.
      Call #5: Evaluate the CRM solution landscape and shortlist viable options.

      Call #6: Review implementation considerations.

      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 RESEARCH GROUP

      Customer Relationship Management Platform Selection Guide

      Speed up the process to build your business case and select your CRM solution.

      EXECUTIVE BRIEF

      Info-Tech Research Group Inc. is a global leader in providing IT research and advice. Info-Tech’s products and services combine actionable insight and relevant advice with ready-to-use tools and templates that cover the full spectrum of IT concerns.
      © 1997-2022 Info-Tech Research Group Inc.

      What exactly is a CRM platform?

      Our Definition: A customer relationship management (CRM) platform (or suite) is a core enterprise application that provides a broad feature set for supporting customer interaction processes, typically across marketing, sales and customer service. These suites supplant more basic applications for customer interaction management (such as the contact management module of an enterprise resource planning (ERP) platform or office productivity suite).

      A customer relationship management suite provides many key capabilities, including but not limited to:

      • Account management
      • Order history tracking
      • Pipeline management
      • Case management
      • Campaign management
      • Reports and analytics
      • Customer journey execution

      A CRM suite provides a host of native capabilities, but many organizations elect to tightly integrate their CRM solution with other parts of their customer experience ecosystem to provide a 360-degree view of their customers.

      Stock image of a finger touching a screen showing a stock chart.

      Info-Tech Insight

      CRM feature sets are rapidly evolving. Focus on the social component of sales, marketing, and service management features, as well as collaboration, to get the best fit for your requirements. Moreover, consider investing in best-of-breed social media management platforms (SMMPs) and internal collaboration tools to ensure sufficient functionality.

      Build a cohesive CRM selection approach that aligns business goals with CRM capabilities.

      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 customer experiences.

      Customer expectations are on the rise: meet them!

      A CRM platform is a crucial system for enabling good customer experiences.

      CUSTOMER EXPERIENCE IS EVOLVING

      1. Thoughtfulness is in
          Connect with customers on a personal level
      2. Service over products
          The experience is more important than the product
      3. Culture is now number one
          Culture is the most overlooked piece of customer experience strategy
      4. Engineering and service finally join forces
          Companies are combining their technology and service efforts to create strong feedback loops
      5. The B2B world is inefficiently served
          B2B needs to step up with more tools and a greater emphasis placed on customer experience

      (Source: Forbes, 2019)

      Identifying organizational objectives of high priority will assist in breaking down business needs and CRM objectives. This exercise will better align the CRM systems with the overall corporate strategy and achieve buy-in from key stakeholders.

      A strong CRM platform supports a range of organizational objectives for customer engagement.

      Increase Revenue Enable lead scoring Deploy sales collateral management tools Improve average cost per lead via a marketing automation tool
      Enhance Market Share Enhance targeting effectiveness with a CRM Increase social media presence via an SMMP Architect customer intelligence analysis
      Improve Customer Satisfaction Reduce time-to-resolution via better routing Increase accessibility to customer service with live chat Improve first contact resolution with customer KB
      Increase Customer Retention Use a loyalty management application Improve channel options for existing customers Use customer analytics to drive targeted offers
      Create Customer-Centric Culture Ensure strong training and user adoption programs Use CRM to provide 360-degree view of all customer interactions Incorporate the voice of the customer into product development

      Succeeding with CRM selection and implementation has a positive effect on driving revenues and decreasing costs

      There are three buckets of metrics and KPIs where CRM will drive improvements

      The metrics of a smooth CRM selection and implementation process include:

      • Better alignment of CRM functionality to business needs.
      • Better functionality coverage of the selected platform.
      • Decreased licensing costs via better vendor negotiation.
      • Improved end-user satisfaction with the deployed solution.
      • Fewer errors and rework during implementation.
      • Reduced total implementation costs.
      • Reduced total implementation time.

      A successful CRM deployment drives revenue

      • Increased customer acquisition due to enhanced accuracy of segmentation and targeting, superior lead qualification, and pipeline management.
      • Increased customer satisfaction and retention due to targeted campaigns (e.g. customer-specific deals), quicker service incident resolution, and longitudinal relationship management.
      • Increased revenue per customer due to comprehensive lifecycle management tools, social engagement, and targeted upselling of related products and services (enabled by better reporting/analytics).

      A successful CRM deployment decreases cost

      • Deduplication of effort across business domains as marketing, sales, and service now have a common repository of customer information and interaction tools.
      • Increased sales and service agent efficiency due to their focus on selling and resolution, rather than administrative tasks and overhead.
      • Reduced cost-to-sell and cost-to-serve due to automation of activities that were manually intensive.
      • Reduced cost of accurate data due to embedded reporting and analytics functionality.

      CRM platforms sit at the core of a well-rounded customer engagement ecosystem

      At the center is 'Customer Relationship Management Platform' surrounded by 'Web Experience Management Platform', 'E-Commerce & Point-of-Sale Solutions', 'Social Media Management Platform', 'Customer Intelligence Platform', 'Customer Service Management Tools', and 'Marketing Management Suite'.

      Customer Experience Management (CXM) Portfolio

      Customer relationship management platforms are increasingly expansive in functional scope and foundational to an organization’s customer engagement strategy. Indeed, CRMs form the centerpiece for a comprehensive CXM system, alongside tools such as customer intelligence platforms and adjacent point solutions for sales, marketing, and customer service.

      Review Info-Tech’s CXM blueprint below to build a complete, end-to-end customer interaction solution portfolio that encompasses CRM alongside other critical components. The CXM blueprint also allows you to develop strategic requirements for CRM based on customer personas and external market analysis.

      Build a Strong Technology Foundation for Customer Experience Management

      Sample of the 'Build a Strong Technology Foundation for Customer Experience Management' blueprint. Design an end-to-end technology strategy to drive sales revenue, enhance marketing effectiveness, and create compelling experiences for your customers.

      View the blueprint

      Considering a CRM switch? Switching software vendors drives high satisfaction

      Eighty percent of organizations are more satisfied after changing their software vendor.

      • Most organizations see not only a positive change in satisfaction with their new vendor, but also a substantial change in satisfaction.
      • What matters is making sure your organization is well-positioned to make a switch.
      • When it comes to switching software vendors, the grass really can be greener on the other side.

      Over half of organizations are 60%+ more satisfied after changing their vendor.

      (Source: Info-Tech Research Group, "Switching Software Vendors Overwhelmingly Drives Increased Satisfaction", 2020.)

      IT is critical to the success of your CRM selection and rollout

      Today’s shared digital landscape of the CIO and CMO

      Info-Tech Insight

      Technology is the key enabler of building strong customer experiences: IT must stand shoulder to shoulder with the business to develop a technology framework for customer relationship management.

      CIO

      IT Operations

      Service Delivery and Management

      IT Support

      IT Systems and Application

      IT Strategy and Governance

      Cybersecurity
      Collaboration and Partnership

      Digital Strategy = Transformation
      Business Goals | Innovation | Leadership | Rationalization

      Customer Experience
      Architecture | Design | Omnichannel Delivery | Management

      Insight (Market Facing)
      Analytics | Business Intelligence | Machine Learning | AI

      Marketing Integration + Operating Model
      Apps | Channels | Experiences | Data | Command Center

      Master Data
      Customer | Audience | Industry | Digital Marketing Assets
      CMO

      PEO Media

      Brand Management

      Campaign Management

      Marketing Tech

      Marketing Ops

      Privacy, Trust, and Regulatory Requirements

      (Source: ZDNet, 2020)

      CRM by the numbers

      1/3

      Statistical analysis of CRM projects indicates failures vary from 18% to 69%. Taking an average of those analyst reports, about one-third of CRM projects are considered a failure. (Source: CIO Magazine, 2017)

      92%

      92% of organizations report that CRM use is important for accomplishing revenue objectives. (Source: Hall, 2020)

      40%

      In 2019, 40% of executives name customer experience the top priority for their digital transformation. (Source: CRM Magazine, 2019)

      Case Study

      Align strategy and technology to meet consumer demand.
      INDUSTRY
      Entertainment
      SOURCE
      Forbes, 2017
      Challenge

      Beginning as a mail-out service, Netflix offered subscribers a catalog of videos to select from and have mailed to them directly. Customers no longer had to go to a retail store to rent a video. However, the lack of immediacy of direct mail as the distribution channel resulted in slow adoption.

      Blockbuster was the industry leader in video retail but was lagging in its response to industry, consumer, and technology trends around customer experience.

      Solution

      In response to the increasing presence of tech-savvy consumers on the internet, Netflix invested in developing its online platform as its primary distribution channel. The benefit of doing so was two-fold: passive brand advertising (by being present on the internet) and meeting customer demands for immediacy and convenience. Netflix also recognized the rising demand for personalized service and created an unprecedented, tailored customer experience.

      Results

      Netflix’s disruptive innovation is built on the foundation of great customer experience management. Netflix is now a $28-billion company, which is tenfold what Blockbuster was worth.

      Netflix used disruptive technologies to innovatively build a customer experience that put it ahead of the long-time video rental industry leader, Blockbuster.

      CRM Buyer’s Guide

      Phase 1

      Understand CRM Features

      Phase 1

      1.1 Define CRM platforms

      1.2 Classify table stakes & differentiating capabilities

      1.3 Explore CRM trends

      Phase 2

      2.1 Build the business case

      2.2 Streamline requirements elicitation for CRM

      2.3 Construct the RFP

      Phase 3

      3.1 Discover key players in the CRM landscape

      3.2 Engage the shortlist & select finalist

      3.3 Prepare for implementation

      This phase will walk you through the following activities:

      • Set a level of understanding of CRM technology.
      • Define which CRM features are table stakes (standard) and which are differentiating.
      • Identify the “Art of the Possible” in a modern CRM from a sales, marketing, and service lens.

      This phase involves the following participants:

      • CIO
      • Applications manager
      • Project manager
      • Sales executive
      • Marketing executive
      • Customer service executive

      Understand CRM table stakes features

      Organizations can expect nearly all CRM vendors to provide the following functionality.

      Lead Management Pipeline Management Contact Management Campaign Management Customer Service Management
      • Tracks and captures a lead’s information, automatically building a profile. Leads are then qualified through contact scoring models. Assigning leads to sales is typically automated.
      • Enables oversight over future sales. Includes revenue forecasting based on past/present trends, tracking sales velocity, and identifying ineffective sales processes.
      • Tracks and stores customer data, including demography, account and billing history, social media, and contact information. Typically, records and fields can be customized.
      • Provides integrated omnichannel campaign functionality and data analysis of customer intelligence. Data insights can be used to drive new and effective marketing campaigns.
      • Provides integrated omnichannel customer experiences to provide convenient service. Includes case and ticket management, automated escalation rules, and third-party integrations.

      Identify differentiating CRM features

      While not always “must-have” functionality, these features may be the final dealbreaker when deciding between two CRM vendors.

      Image of clustered screens with various network and business icons surounding them.
      • Workflow Automation
        Automate repetitive tasks by creating workflows that trigger actions or send follow-up reminders for next steps.
      • Advanced Analytics and Reporting
        Provides customized dashboard visualizations, detailed reporting, AI-driven virtual assistants, data extraction & analysis, and ML forecasting.
      • Customizations and Open APIs
        Broad range of available customizations (e.g. for dashboards and fields), alongside ease of integration (e.g. via plugins or APIs).
      • Document Management
        Out-of-the-box centralized content repository for storing, uploading, and sharing documents.
      • Mobile Support
        Ability to support mobile devices, OSes, and platforms with a native application or HTML-based web-access.
      • Project and Task Management
        Native project and task management functionality, enhancing cross-team organization and communication.
      • Configure, Price, Quote (CPQ)
        Create and send quotes or proposals to prospective and current customers.

      Features aren’t everything – be wary of common CRM selection pitfalls

      You can have all the right features, but systemic problems will lead to poor CRM implementation. Dig out these root causes first to ensure a successful CRM selection.

      50% of organizations believe the quality of their CRM data is “very poor” or “neutral.”

      Without addressing data governance issues, CRMs will only be as good as your data.

      Source: (Validity 2020)
      27% of organizations report that bad data costs them 10% or more in lost revenue annually.
      42% rate the trust that users have in their data as “high” or “very high.”
      54% believe that sales forecasts are accurate or very accurate.
      69% attribute poor CRM governance to missing or incomplete data, followed by duplicate data, incorrect data, and expired data. Other data issues include siloed data or disparate systems.
      73% believe that they do not have a 360-degree view of their customers.

      Ensure you understand the “art of the possible” in the CRM landscape

      Knowing what is possible will help funnel which features are most suitable for your organization – having all the bells and whistles does not always equal strong ROI.

      Holistically examine the potential of any CRM solution through three main lenses: Stock image of a person working with dashboards.

      Sales

      Identify sales opportunities through recording customers’ interactions, generating leads, nurturing contacts, and forecasting revenues.
      Stock image of people experiencing digital ideas.

      Marketing

      Analyze customer interactions to identify upsell and cross-sell opportunities, drive customer loyalty, and use customer data for targeted campaigns.
      Stock image of a customer service representative.

      Customer Service

      Improve and optimize customer engagement and retention, leveraging customer data to provide round-the-clock omnichannel experiences.

      Art of the possible: Sales

      Stock image of a person working with dashboards.

      TRACK PROSPECT INTERACTIONS

      Want to engage with a prospect but don’t know what to lead with? CRM solutions can track and analyze many of the interactions a prospect has with your organization, including with fellow staff, their clickthrough rate on marketing material, and what services they are downloading on your website. This information can then auto-generate tasks to begin lead generation.

      COORDINATE LEAD SCORING

      Information captured from a prospect is generated into contact cards; missing data (such as name and company) can be auto-captured by the CRM via crawling sites such as LinkedIn. The CRM then centralizes and scores (according to inputted business rules) a lead’s potential, ensuring sales teams coordinate and keep a track of the lead’s journey without wrongful interference.

      AI-DRIVEN REVENUE FORECASTING

      Generate accurate forecasting reports using AI-driven “virtual assistants” within the CRM platform. These assistants are personal data scientists, quickly noting discrepancies, opportunities, and what-if scenarios – tasks that might take weeks to do manually. This pulled data is then auto-forecasted, with the ability to flexibly adjust to real-time data.

      Art of the possible: Marketing

      Stock image of people experiencing digital ideas.

      DRIVE LOYALTY

      Data captured and analyzed in the CRM from customer interactions builds profiles and a deeper understanding of customers’ interests. With this data, marketing teams can deliver personalized promotions and customer service to enhance loyalty – from sending a discount on a product the customer was browsing on the website, to providing notifications about delivery statuses.

      AUTOMATE WORKFLOWS

      Building customer profiles, learning spending habits, and charting a customer’s journey for upselling or cross-selling can be automated through workflows, saving hours of manual work. These workflows can immediately respond to customer enquiries or deliver offers to the customer’s preferred channel based on their prior usage.

      TARGETED CAMPAIGNING

      Information attained through a CRM platform directly informs any marketing strategy: identifying customer segments, spending habits, building a better product based on customer feedback, and identifying high-spending customers. With any new product or offering, it is straightforward for marketing teams to understand where to target their next campaign for highest impact.

      Art of the possible: Customer service

      Stock image of a customer service representative.

      OMNICHANNEL SUPPORT

      Rapidly changing demographics and modes of communications require an evolution toward omnichannel engagement. Many customers now expect to communicate with contact centers not just by voice, but via social media. Agents need customer information synced across each channel they use, meeting the customer’s needs where they are.

      INTELLIGENT SELF-SERVICE PORTALS

      Customers want their issues resolved as quickly as possible. Machine-learning self-service options deliver personalized customer experiences, which also reduce both agent call volume and support costs for the organization.

      LEVERAGING ANALYTICS

      The future of customer service is tied up with analytics. This not only entails AI-driven capabilities that fetch the agent relevant information, skills-based routing, and using biometric data (e.g. speech) for security. It also feeds operations leaders’ need for easy access to real insights about how their customers and agents are doing.

      Best-of-Breed Point Solutions

      Full CRM Suite

      Blue smiley face. Benefits
      • Features may be more advanced for specific functional areas and a higher degree of customization may be possible.
      • If a potential delay in real-time customer data transfer is acceptable, best-of-breeds provide a similar level of functionality to suites for a lower price.
      • Best-of-breeds allow value to be realized faster than suites, as they are easier and faster to implement and configure.
      • Rip and replace is easier, and vendor updates are relatively quick to market.
      Benefits
      • Everyone in the organization works from the same set of customer data.
      • There is a “lowest common denominator” for agent learning as consistent user interfaces lower learning curves and increase efficiency in usage.
      • There is a broader range of functionality using modules.
      • Integration between functional areas will be strong and the organization will be in a better position to enable version upgrades without risking invalidation of an integration point between separate systems.
      Green smiley face.
      Purple frowny face. Challenges
      • Best-of-breeds typically cover less breadth of functionality than suites.
      • There is a lack of uniformity in user experience across best-of-breeds.
      • Data integrity risks are higher.
      • Variable infrastructure may be implemented due to multiple disparate systems, which adds to architecture complexity and increased maintenance.
      • There is potential for redundant functionality across multiple best-of-breeds.
      Challenges
      • Suites exhibit significantly higher costs compared to point solutions.
      • Suite module functionality may not have the same depth as point solutions.
      • Due to high configuration availability and larger-scale implementation requirements, the time to deploy is longer than point solutions.
      Orange frowny face.
      Info-Tech Insight

      Even if a suite is missing a potential module, the proliferation of app extensions, integrations, and services could provide a solution. Salesforce’s AppExchange, for instance, offers a plethora of options to extend its CRM solution – from telephony integration, to gamification.

      CRM Buyer’s Guide

      Phase 2

      Build the Business Case & Elicit CRM Requirements

      Phase 1

      1.1 Define CRM platforms

      1.2 Classify table stakes & differentiating capabilities

      1.3 Explore CRM trends

      Phase 2

      2.1 Build the business case

      2.2 Streamline requirements elicitation for CRM

      2.3 Construct the RFP

      Phase 3

      3.1 Discover key players in the CRM landscape

      3.2 Engage the shortlist & select finalist

      3.3 Prepare for implementation

      This phase will walk you through the following activities:

      • Identify goals, objectives, challenges, and costs to inform the business case for a new CRM platform.
      • Elicit and prioritize key requirements for your platform.
      • Port the requirements into Info-Tech’s CRM RFP Template.

      This phase involves the following participants:

      • CIO
      • Applications manager
      • Project manager
      • Sales executive
      • Marketing executive
      • Customer service executive

      Right-size the CRM selection team to ensure you get the right information but are still able to move ahead quickly

      Full-Time Resourcing: At least one of these five team members must be allocated to the selection initiative as a full-time resource.

      A silhouetted figure.

      IT Leader

      A silhouetted figure.

      Technical Lead

      A silhouetted figure.

      Business Analyst/
      Project Manager

      A silhouetted figure.

      Business Lead

      A silhouetted figure.

      Process Expert(s)

      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. Typically, a CMO or SVP of sales. These team members are the sales, marketing, and service process owners who will help steer the CRM requirements and direction.

      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. For more information on stakeholder management and involvement, see this guide.

      Be prepared to define what issues you are trying to address and why a new CRM is the right approach

      Identify the current state and review the background of what you’ve done leading up to this point, goals you’ve been asked to meet, and challenges in solving known problems to help to set the stage for why your proposed solution is needed. If your process improvements have taken you as far as you can go without improved workflows or data, specify where the gaps are.
      Arrows with icons related to the text on the right merging into one arrow. Alignment

      Alignment to strategic goals is always important, but that is especially true with CRM because customer relationship management platforms are at the intersection of your organization and your customers. What are the strategic marketing, sales and customer service goals that you want to realize (in whole or in part) by improving your CRM ecosystem?

      Impact to your business

      Identify areas where your customers may be impacted by poor experiences due to inadequate or aging technology. What’s the impact on customer retention? On revenue?

      Impact to your organization

      Define how internal stakeholders within the organization are impacted by a sub-optimal CRM experience – what are their frustrations and pain points? How do issues with your current CRM environment prevent teams in sales, marketing, or service from doing their jobs?

      Impact to your department

      Describe the challenges within IT of using disparate systems, workarounds, poor data and reporting, lack of automation, etc., and the effect these challenges have on IT’s goals.

      Align the CRM strategy with the corporate strategy

      Corporate Strategy Unified Strategy CRM Strategy
      Spectrum spanning all columns.
      Your corporate strategy:
      • Conveys the current state of the organization and the path it wants to take.
      • Identifies future goals and business aspirations.
      • Communicates the initiatives that are critical for getting the organization from its current state to the future state.
      • The CRM strategy and the rationale for deploying a new CRM can be and should be linked, with metrics, to the corporate strategy and ultimate business objectives (such as improving customer acquisition, entering new segments, or improving customer lifetime value).
      Your CRM strategy:
      • Communicates the organization’s budget and spending on CRM.
      • Identifies IT initiatives that will support the business and key CRM objectives.
      • Outlines staffing and resourcing for CRM initiatives.
      CRM projects are more successful when the management team understands the strategic importance and the criticality of alignment. Time needs to be spent upfront aligning business strategies with CRM capabilities. Effective alignment between sales, marketing, customer service, operations, IT, and the business should happen daily. Alignment doesn’t just need to occur at the executive level, but also at each level of the organization.

      2.1 Create your list of goals and milestones for CRM

      1-3 hours

      Input: Corporate strategy, Target key performance indicators, End-user satisfaction results (if applicable)

      Output: Prioritized list of goals with milestones that can be met with a new or improved CRM solution

      Materials: Whiteboard/flip charts, CRM Business Case Template

      Participants: CIO, Application managers, CMO/SVP sales, Marketing, sales or service SMEs

      1. Review strategic goals to identify alignment to your CRM selection project. For example, digital transformation may be enhanced or enabled with a CRM solution that supports better outreach to key customer segments through improved campaign management.
      2. Next, brainstorm tactical goals with your colleagues.
      3. Identify specific goals the organization has set for the business that may be supported by improved customer prospecting, customer service, or analytics functionality through a better CRM solution.
      4. Identify specific goals your organization will be able to make possible with a new or improved CRM solution.
      5. Prioritize this list and lead with the most important goal that can be reached at the one-year, six-month, and three-month milestones.
      6. Document in the goals section of your business case.

      Download the CRM Business Case Template and record the outputs of this exercise in the strategic business goals, business drivers, and technical drivers slides.

      Identify what challenges exist with the current environment

      Ensure you are identifying issues at a high level, so as not to drown in detail, but still paint the right picture. Identify technical issues that are impacting customer experience or business goals. Typical complaints for CRM solutions that are old or have been outgrown include:

      1.

      Lack of a flexible, configurable customer data model that supports complex relationships between accounts and contacts.

      2.

      Lack of a flexible, configurable customer data model that supports complex relationships between accounts and contacts.

      3.

      Lack of meaningful reports and useable dashboards, or difficulty in surfacing them.

      4.

      Poor change enablement resulting in business interruptions.

      5.

      Inability to effectively automate routine sales, marketing, or service tasks at scale via a workflow tool.

      6.

      Lack of proper service management features, such as service knowledge management.

      7.

      Inability to ingest customer data at scale (for example, no ability to automatically log e-mails or calls).

      8.

      Major technical deficiencies and outages – the incumbent CRM platform goes down, causing business disruption.

      9.

      The platform itself doesn’t exist in the current state – everything is done in Microsoft Excel!

      Separate business issues from technical issues, but highlight where they’re connected and where technical issues are causing business issues or preventing business goals from being reached.

      Before switching vendors, evaluate your existing CRM to see if it’s being underutilized or could use an upgrade

      The cost of switching vendors can be challenging, but it will depend entirely on the quality of data and whether it makes sense to keep it.
      • Achieving success when switching vendors first requires reflection. We need to ask why we are dissatisfied with our incumbent software.
      • If the product is old and inflexible, the answer may be obvious, but don’t be afraid to include your incumbent in your evaluation if your issues might be solved with an upgrade.
      • Look at your use-case requirements to see where you want to take the CRM solution and compare them to your incumbent’s roadmap. If they don’t match, switching vendors may be the only solution. If your roadmaps align, see if you’re fully leveraging the solution or will be able to start working through process improvements.
      Pie graph with a 20% slice. Pie graph with a 25% slice.

      20%

      Small/Medium Enterprises

      25%

      Large Enterprises
      only occasionally or rarely/never use their software (Source: Software Reviews, 2020; N = 45,027)
      Fully leveraging your current software now will have two benefits:
      1. It may turn out that poor leveraging of your incumbent software was the problem all along; switching vendors won’t solve the problem by itself. As the data to the right shows, a fifth of small/medium enterprises and a quarter of large enterprises do not fully leverage their incumbent software.
      2. If you still decide to switch, you’ll be in a good negotiating position. If vendors can see you are engaged and fully leveraging your software, they will be less complacent during negotiations to win you over.
      Info-Tech Insight

      Switching vendors won’t improve poor internal processes. To be fully successful and meet the goals of the business case, new software implementations must be accompanied by process review and improvement.

      2.2 Create your list of challenges as they relate to your goals and their impacts

      1-2 hours

      Input: Goals lists, Target key performance indicators, End-user satisfaction results (if applicable)

      Output: Prioritized list of challenges preventing or hindering customer experiences

      Materials: Whiteboard/flip charts, CRM Business Case Template

      Participants: CIO, Application managers, CMO/SVP sales, Marketing, sales, or service SMEs

      1. Brainstorm with your colleagues to discuss your challenges with CRM today from an application and process lens.
      2. Identify how these challenges are impacting your ability to meet the goals and identify any that are creating customer-facing issues.
      3. Group together like areas and arrange in order of most impactful. Identify which of these issues will be most relevant to the business case for a new CRM platform.
      4. Document in the current-state section of your business case.
      5. Discuss and determine if the incumbent solution can meet your needs or if you’ll need to replace it with a different product.

      Download the CRM Business Case Template and document the outputs of this exercise in the current-state section of your business case.

      Determine costs of the solution

      Ensure the business case includes both internal and external costs related to the new CRM platform, allocating costs of project managers to improve accuracy of overall costs and level of success.

      CRM solutions include application costs and costs to design processes, install, and configure. These start-up costs can be a significant factor in whether the initial purchase is feasible.

      CRM Vendor Costs

      • Application licensing
      • Implementation and configuration
      • Professional services
      • Maintenance and support
      • Training
      • 3rd Party add-ons
      • Data transformation
      • Integration
      When thinking about vendor costs, also consider the matching internal cost associated with the vendor activity (e.g. data cleansing, internal support).

      Internal Costs

      • Project management
      • Business readiness
      • Change management
      • Resourcing (user groups, design/consulting, testing)
      • Training
      • Auditors (if regulatory requirements need vetting)
      Project management is a critical success factor at all stages of an enterprise application initiative from planning to post-implementation. Ensuring that costs for such critical areas are accurately represented will contribute to success.

      Download the blueprint Improve Your Statements of Work to Hold Your Vendors Accountable to define requirements for installation and configuration.

      Bring in the right resources to guarantee success. Work with the PMO or project manager to get help with creating the SOW.

      60% of IT projects are NOT finished “mostly or always” on time (Wellingtone, 2018).

      55% of IT personnel feel that the business objectives of their software projects are clear to them (Geneca, 2017).

      Document costs and expected benefits of the new CRM

      The business case should account for the timing of both expenditures and benefits. It is naïve to expect straight-line benefit realization or a big-bang cash outflow related to the solution implementation. Proper recognition and articulation of ramp-up time will make your business case more convincing.

      Make sure your timelines are realistic for benefits realization, as these will be your project milestones and your metrics for success.

      Example:
      Q1-Q2 Q3-Q6 Q6 Onwards

      Benefits at 25%

      At the early stages of an implementation, users are still learning the new system and go-live issues are being addressed. Most of the projected process improvements are likely to be low, zero, or even negative.

      Benefits at 75%

      Gradually, as processes become more familiar, an organization can expect to move closer to realizing the forecasted benefits or at least be in a position to recognize a positive trend toward their realization.

      Benefits at 100%

      In an ideal world, all projected benefits are realized at 100% or higher. This can be considered the stage where processes have been mastered, the system is operating smoothly, and change has been broadly adopted. In reality, benefits are often overestimated.

      Costs at 50%

      As with benefits, some costs may not kick in until later in the process or when the application is fully operational. In the early phases of implementation, factor in the cost of overlapping technology where you’ll need to run redundant systems and transition any data.

      Costs at 100%

      Costs are realized quicker than benefits as implementation activities are actioned, licensing and maintenance costs are introduced, and resourcing is deployed to support vendor activities internally. Costs that were not live in the early stages are an operational reality at this stage.

      Costs at 100%+

      Costs can be expected to remain relatively static past a certain point, if estimates accurately represented all costs. In many instances, costs can exceed original estimates in the business case, where costs were either underestimated, understated, or missed.

      2.3 Document your costs and expected benefits

      1-2 hours

      Input: Quotes with payment schedule, Budget

      Output: Estimated payment schedule and cost breakdown

      Materials: Spreadsheet or whiteboard, CRM Business Case Template

      Participants: CIO, Application managers, CMO/SVP sales, Marketing, sales, or service SMEs

      1. Estimate costs for the CRM solution. If you’re working with a vendor, provide the initial requirements to quote; otherwise, estimate as closely as you’re able.
      2. Calculate the five-year total cost for the solution to ensure the long-term budget is calculated.
      3. Break down costs for licenses, implementation, training, internal support, and hardware or hosting fees.
      4. Determine a reasonable breakdown of costs for the first year.
      5. Identify where residual costs of the old system may factor in if there are remaining contract obligations during the technology transition.
      6. Create a list of benefits expected to be realized within the same timeline.

      Sample of the table on the previous slide.

      Download the CRM Business Case Template and document the outputs of this exercise in the current-state section of your business case.

      Identify risks and dependencies to mitigate barriers to success as you look to roll out a CRM suite

      A risk assessment will be helpful to better understand what risks need to be mitigated to make the project a success and what risks are pending should the solution not be approved or be delayed.

      Risk Criteria Relevant Questions
      Timeline Uncertainty
      • How much risk is associated with the timeline of the CRM project?
      • Is this timeline realistic and can you reach some value in the first year?
      Success of Similar Projects
      • Have we undertaken previous projects that are similar?
      • Were those successful?
      • Did we note any future steps for improvement?
      Certainty of Forecasts
      • Where have the numbers originated?
      • How comfortable are the sponsors with the revenue and cost forecasts?
      Chance of Cost Overruns
      • How likely is the project to have cost overruns?
      • How much process and design work needs to be done prior to implementation?
      Resource Availability
      • Is this a priority project?
      • How likely are resourcing issues from a technical and business perspective?
      • Do we have the right resources?
      Change During Delivery
      • How volatile is the area in which the project is being implemented?
      • Are changes in the environment likely?
      • How complex are planned integrations?

      2.4 Identify risks to the success of the solution rollout and mitigation plan

      1-2 hours

      Input: List of goals and challenges, Target key performance indicators

      Output: Prioritized list of challenges preventing or hindering improvements for the IT teams

      Materials: Whiteboard/flip charts, CRM Business Case Template

      Participants: CIO, Application managers, CMO/SVP sales, Marketing, sales, or service SMEs

      1. Brainstorm with your colleagues to discuss potential roadblocks and risks that could impact the success of the CRM project.
      2. Identify how these risks could impact your project.
      3. Document the ones that are most likely to occur and derail the project.
      4. Discuss potential solutions to mitigate risks.

      Download the CRM Business Case Template and document the outputs of this exercise in the risk and dependency section of your business case. If the risk assessment needs to be more complex, complete the Risk Indicator Analysis in Info-Tech’s Business Case Workbook.

      Start requirements gathering by identifying your most important use cases across sales, marketing, and service

      Add to your business case by identifying which top-level use cases will meet your goals.

      Examples of target use cases for a CRM project include:

      • Enhance sales acquisition capabilities (i.e. via pipeline management)
      • Enhance customer upsell and cross-sell capabilities
      • Improve customer segmentation and targeting capabilities for multi-channel marketing campaigns
      • Strengthen customer care capabilities to improve customer satisfaction and retention (i.e. via improved case management and service knowledge management)
      • Create actionable insights via enhanced reporting and analytics

      Info-Tech Insight

      Lead with the most important benefit and consider the timeline. Can you reach that goal and report success to your stakeholders within the first year? As you look toward that one-year goal, you can consider secondary benefits, some of which may be opportunities to bring early value in the solution.

      Benefits of a successful deployment of use cases will include:
      • Improved customer satisfaction
      • Improved operational efficiencies
      • Reduced customer turnover
      • Increased platform uptime
      • License or regulatory compliance
      • Positioned for growth

      Typically, we see business benefits in this order of importance. Lead with the outcome that is most important to your stakeholders.

      • Net income increases
      • Revenue generators
      • Cost reductions
      • Improved customer service

      Consider perspectives of each stakeholder to ensure functionality needs are met and high satisfaction results

      Best of breed vs. “good enough” is an important discussion and will feed your success.

      Costs can be high when customizing an ill-fitting module or creating workarounds to solve business problems, including loss of functionality, productivity, and credibility.

      • Start with use cases to drive the initial discussion, then determine which features are mandatory and which are nice-to-haves. Mandatory features will help determine high success for critical functionality and identify where “good enough” is an acceptable state.
      • Consider the implications to implementation and all use cases of buying an all-in-one solution, integration of multiple best-of-breed solutions, or customizing features that were not built into a solution.
      • Be prepared to shelve a use case for this solution and look to alternatives for integration where mandatory features cannot meet highly specialized needs that are outside of traditional CRM solutions.

      Pros and Cons

      Build vs. Buy

      Multi-Source Best of Breed

      Flexibility
      vs.
      architectural complexity

      Vendor Add-Ons & Integrations

      Lower support costs
      vs.
      configuration

      Multi-source Custom

      Flexibility
      vs.
      high skills requirements

      Single Source

      Lower support costs
      vs.
      configuration

      2.5 Define use cases and high-level features for meeting business and technical goals

      1-2 hours

      Input: List of goals and challenges

      Output: Use cases to be used for determining requirements

      Materials: Whiteboard/flip charts, CRM Business Case Template

      Participants: CIO, Application managers, CMO/SVP sales, Marketing, sales, or service SMEs

      1. Identify the key customer engagement use cases that will support your overall goals as defined in the previous section.
      2. The following slide has examples of use case domains that will be enhanced from a CRM platform.
      3. Define high-level goals you wish to achieve in the first year and longer term. If you have more specific KPIs to add, and it is a requirement for your organization’s documentation, add them to this section.
      4. Take note of where processes will need to be improved to benefit from these use-case solutions – the tools are only as good as the process behind them.

      Download the CRM Business Case Template and document the outputs from this exercise in the current-state section of your business case.

      Understand the dominant use-case scenarios across organizations to narrow the list of potential CRM solutions

      Sales
      Enablement

      • Generate leads through multiple channels.
      • Rapidly sort, score, and prioritize leads based on multiple criteria.
      • Create in-depth sales forecasts segmented by multiple criteria (territory, representative, etc.).

      Marketing
      Management

      • Manage marketing campaigns across multiple channels (web, social, email, etc.).
      • Aggregate and analyze customer data to generate market intelligence.
      • Build and deploy customer-facing portals.

      Customer Service
      Management

      • Generate tickets, and triage customer service requests through multiple channels.
      • Track customer service interactions with cases.
      • There is a need to integrate customer records with contact center infrastructure.
      Info-Tech Insight

      Use your understanding of the CRM use case to accelerate the vendor shortlisting process. Since the CRM use case has a direct impact on the prioritization of a platform’s features and capabilities, you can rapidly eliminate vendors from contention or designate superfluous modules as out-of-scope.

      2.5.1 Use Info-Tech’s CRM Use-Case Fit Assessment Tool to align your CRM requirements to the vendor use cases

      30 min

      Input: Understanding of business objectives for CRM project, Use-Case Fit Assessment Tool

      Output: Use-case suitability

      Materials: Use-Case Fit Assessment Tool

      Participants: Core project team, Project managers

      1. Use the Use-Case Fit Assessment Tool to understand how your unique business requirements map into which CRM use case.
      2. This tool will assess your answers and determine your relative fit against the use-case scenarios.
      3. Fit will be assessed as “Weak,” “Moderate,” or “Strong.”
        1. 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.
        2. Note: These use-case scenarios are not mutually exclusive, meaning 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.

      Download the CRM Use-Case Fit Assessment Tool

      Once you’ve identified the top-level use cases a CRM must support, elicit, and prioritize granular platform requirements.

      Understanding business needs through requirements gathering is the key to defining everything about what is being purchased, yet it is an area where people often make critical mistakes.

      Info-Tech Insight

      To avoid creating makeshift solutions, an organization needs to gather requirements with the desired future state in mind.

      Risks of poorly scoped requirements

      • Fail to be comprehensive and miss certain areas of scope
      • Focus on how the solution should work instead of what it must accomplish
      • Have multiple levels of detail within the requirements, which are inconsistent and confusing
      • Drill all the way down into system-level detail
      • Add unnecessary constraints based on what is done today rather than focusing on what is needed for tomorrow
      • Omit constraints or preferences that buyers think are “obvious”

      Best practices

      • Get a clear understanding of what the system needs to do and what it is expected to produce
      • Test against the principle of MECE – requirements should be “mutually exclusive and collectively exhaustive”
      • Explicitly state the obvious and assume nothing
      • Investigate what is sold on the market and how it is sold. Use language that is consistent with that of the market and focus on key differentiators – not table stakes
      • Contain the appropriate level of detail – the level should be suitable for procurement and sufficient for differentiating vendors

      Prioritize requirements to assist with vendor selection: focus on priority requirements linked to differentiated capabilities

      Prioritization is the process of ranking each requirement based on its importance to project success. Hold a meeting for the domain SMEs, implementation SMEs, project managers, and project sponsors to prioritize the requirements list. At the conclusion of the meeting, each requirement should be assigned a priority level. The implementation SMEs will use these priority levels to ensure efforts are targeted toward the proper requirements and to plan features available on each release. Use the MoSCoW Model of Prioritization to effectively order requirements.


      Pyramid of the MoSCoW Model.
      The MoSCoW model was introduced by Dai Clegg of Oracle UK in 1994.

      The MoSCoW Model of Prioritization

      Requirements must be implemented for the solution to be considered successful.

      Requirements that are high priority should be included in the solution if possible.

      Requirements are desirable but not necessary and could be included if resources are available.

      Requirements won’t be in the next release, but will be considered for the future releases.

      Base your prioritization on the right set of criteria

      Effective Prioritization Criteria

      Criteria

      Description

      Regulatory & Legal Compliance These requirements will be considered mandatory.
      Policy Compliance Unless an internal policy can be altered or an exception can be made, these requirements will be considered mandatory.
      Business Value Significance Give a higher priority to high-value requirements.
      Business Risk Any requirement with the potential to jeopardize the entire project should be given a high priority and implemented early.
      Likelihood of Success Especially in “proof of concept” projects, it is recommended that requirements have good odds.
      Implementation Complexity Give a higher priority to low implementation difficulty requirements.
      Alignment With Strategy Give a higher priority to requirements that enable the corporate strategy.
      Urgency Prioritize requirements based on time sensitivity.
      Dependencies A requirement on its own may be low priority, but if it supports a high-priority requirement, then its priority must match it.

      2.6 Identify requirements to support your use cases

      1-2 hours

      Input: List of goals and challenges

      Output: Use cases to be used for determining requirements

      Materials: Whiteboard/flip charts, Vendor Evaluation Workbook

      Participants: CIO, Application managers, CMO/SVP sales, Marketing, sales, or service SMEs

      1. Work with the team to identify which features will be most important to support your use cases. Keep in mind there will be some features that will require more effort to implement fully. Add that into your project plan.
      2. Use the features lists on the following slides as a guide to get started on requirements.
      3. Prioritize your requirements list into mandatory features and nice-to-have features (or use the MoSCoW model from the previous slides). This will help you to eliminate vendors who don’t meet bare minimums and to score remaining vendors.
      4. Use this same list to guide your vendor demos.

      Our Improve Requirements Gathering blueprint provides a deep dive into the process of eliciting, analyzing, and validating requirements if you need to go deeper into effective techniques.

      CRM features

      Table stakes vs. differentiating

      What is a table stakes/standard feature?

      • Certain features are standard for all CRM tools, but that doesn’t mean they are all equal.
      • The existence of features doesn’t guarantee their quality or functionality to the standards you need. Never assume that “Yes” in a features list means you don’t need to ask for a demo.
      • If Table Stakes are all you need from your CRM solution, the only true differentiator for the organization is price. Otherwise, dig deeper to find the best price to value for your needs.

      What is a differentiating/additional feature?

      • Differentiating features take two forms:
        • Some CRM platforms offer differentiating features that are vertical specific.
        • Other CRM platforms offer differentiating features that are considered cutting edge. These cutting-edge features may become table stakes over time.

      Table stakes features for CRM

      Account Management Flexible account database that stores customer information, account history, and billing information. Additional functionality includes: contact deduplication, advanced field management, document linking, and embedded maps.
      Interaction Logging and Order History Ability to view all interactions that have occurred between sales teams and the customer, including purchase order history.
      Basic Pipeline Management View of all opportunities organized by their current stage in the sales process.
      Basic Case Management The ability to create and manage cases (for customer service or order fulfilment) and associate them with designated accounts or contacts.
      Basic Campaign Management Basic multi-channel campaign management (i.e. ability to execute outbound email campaigns). Budget tracking and campaign dashboards.
      Reports and Analytics In-depth reports on CRM data with dashboards and analytics for a variety of audiences.
      Mobile Support Mobile access across multiple devices (tablets, smartphones and/or wearables) with access to CRM data and dashboards.

      Additional features for CRM

      Customer Information Management Customizable records with detailed demographic information and the ability to created nested accounts (accounts with associated sub-accounts or contact records).
      Advanced Case Management Ability to track detailed interactions with members or constituents through a case view.
      Employee Collaboration Capabilities for employee-to-employee collaboration, team selling, and activity streams.
      Customer Collaboration Capabilities for outbound customer collaboration (i.e. the ability to create customer portals).
      Lead Generation Capabilities for generating qualified leads from multiple channels.
      Lead Nurturing/Lead Scoring The ability to evaluate lead warmth using multiple customer-defined criteria.
      Pipeline and Deal Management Managing deals through cases, providing quotes, and tracking client deliverables.

      Additional features for CRM (Continued)

      Marketing Campaign Management Managing outbound marketing campaigns via multiple channels (email, phone, social, mobile).
      Customer Intelligence Tools for in-depth customer insight generation and segmentation, predictive analytics, and contextual analytics.
      Multi-Channel Support Capabilities for supporting customer interactions across multiple channels (email, phone, social, mobile, IoT, etc.).
      Customer Service Workflow Management Capabilities for customer service resolution, including ticketing and service management.
      Knowledge Management Tools for capturing and sharing CRM-related knowledge, especially for customer service.
      Customer Journey Mapping Visual workflow builder with automated trigger points and business rules engine.
      Document Management The ability to curate assets and attachments and add them to account or contact records.
      Configure, Price, Quote The ability to create sales quotes/proposals from predefined price lists and rules.

      2.7 Put it all together – port your requirements into a robust RFP template that you can take to market!

      1-2 hours
      1. Once you’ve captured and prioritized your requirements – and received sign-off on them from key stakeholders – it’s time to bake them into a procurement vehicle of your choice.
      2. For complex enterprise systems like a CRM platform, Info-Tech recommends that this should take the form of a structured RFP document.
      3. Use our CRM RFP Template and associated CRM RFP Scoring Tool to jump-start the process.
      4. The next step will be conducting a market scan to identify contenders, and issuing the RFP to a shortlist of viable vendors for further evaluation.

      Need additional guidance on running an effective RFP process? Our Drive Successful Sourcing Outcomes with a Robust RFP Process has everything you need to ace the creation, administration and assessment of RFPs!

      Samples of the CRM Request for Proposal Template and CRM Suite Evaluation and RFP Scoring Tool.

      Download the CRM Request for Proposal Template

      Download the CRM Suite Evaluation and RFP Scoring Tool

      Identify whether vertical-specific CRM platforms are a best fit

      In mature vendor landscapes (like CRM) vendors begin to differentiate themselves by offering vertical-specific platforms, modules, or feature sets. These feature sets accelerate the implantation, decrease the platform’s learning curve, and drive user adoption. The three use cases below cover the most common industry-specific offerings:

      Public Sector

      • Constituent management and communication.
      • Constituent portal deployment for self-service.
      • Segment constituents based on geography, needs and preferences.

      Education

      • Top-level view into the student journey from prospect to enrolment.
      • Track student interactions with services across the institution.
      • Unify communications across different departments.

      Financial Services

      • Determine customer proclivity for new services.
      • Develop self-service banking portals.
      • Track longitudinal customer relationships from first account to retirement management.
      Info-Tech Insight

      Vertical-specific solutions require less legwork to do upfront but could cost you more in the long run. Interoperability and vendor viability must be carefully examined. Smaller players targeting niche industries often have limited integration ecosystems and less funding to keep pace with feature innovation.

      Rein-in ballooning scope for CRM selection projects

      Stretching the CRM beyond its core capabilities is a short-term solution to a long-term problem. Educate stakeholders about the limits of CRM technology.

      Common pitfalls for CRM selection

      • Tangential capabilities may require separate solutions. It is common for stakeholders to list features such as “content management” as part of the new CRM platform. While content management goes hand in hand with the CRM’s ability to manage customer interactions, document management is best handled by a standalone platform.

      Keeping stakeholders engaged and in line

      • Ballooning scope leads to stakeholder dissatisfaction. Appeasing stakeholders by over-customizing the platform will lead to integration and headaches down the road.
      • Make sure stakeholders feel heard. Do not turn down ideas in the midst of an elicitation session. Once the requirements-gathering sessions are completed, the project team has the opportunity to mark requirements as “out of scope” and communicate the reasoning behind the decision.
      • Educate stakeholders on the core functionality of CRM. Many stakeholders do not know the best-fit use cases for CRM platforms. Help end users understand what CRM is good at and where additional technologies will be needed.
      Stock image of a man leaping with a balloon.

      CRM Buyer’s Guide

      Phase 3

      Discover the CRM Market Space & Prepare for Implementation

      Phase 1

      1.1 Define CRM platforms

      1.2 Classify table stakes & differentiating capabilities

      1.3 Explore CRM trends

      Phase 2

      2.1 Build the business case

      2.2 Streamline requirements elicitation for CRM

      2.3 Construct the RFP

      Phase 3

      3.1 Discover key players in the CRM landscape

      3.2 Engage the shortlist & select finalist

      3.3 Prepare for implementation

      This phase will walk you through the following activities:

      • Dive into the key players of the CRM vendor landscape.
      • Understand best practices for building a vendor shortlist.
      • Understand key implementation considerations for CRM.

      This phase involves the following participants:

      • CIO
      • Applications manager
      • Project manager
      • Sales executive
      • Marketing executive
      • Customer service executive

      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.
      Stock image of river rapids.

      Review your use cases to start your shortlist

      Your Info-Tech analysts can help you narrow down the list of vendors that will meet your requirements.

      Next steps will include:
      1. Reviewing your requirements
      2. Checking out SoftwareReviews
      3. Shortlisting your vendors
      4. Conducting demos and detailed proposal reviews
      5. Selecting and contracting with a finalist!
      Image of a person presenting a dashboard of the steps on the left.

      Get to know the key players in the CRM landscape

      The proceeding slides provide a top-level overview of the popular players you will encounter in the CRM shortlisting process.

      Logos of the key players in the CRM landscape (Salesforce, Microsoft, Oracle, HubSpot, etc).

      Evaluate software category leaders through vendor rankings and awards

      SoftwareReviews

      Sample of SoftwareReviews' Data Quadrant Report. Title page of SoftwareReviews' Data Quadrant Report. The Data Quadrant is a thorough evaluation and ranking of all software in an individual category to compare platforms across multiple dimensions.

      Vendors are ranked by their Composite Score, based on individual feature evaluations, user satisfaction rankings, vendor capability comparisons, and likeliness to recommend the platform.

      Sample of SoftwareReviews' Emotional Footprint. Title page of SoftwareReviews' Emotional Footprint. The Emotional Footprint is a powerful indicator of overall user sentiment toward the relationship with the vendor, capturing data across five dimensions.

      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.

      Speak with category experts to dive deeper into the vendor landscape

      SoftwareReviews

      Icon of a person.


      Fact-based reviews of business software from IT professionals.

      Icon of a magnifying glass over a chart.


      Top-tier data quality backed by a rigorous quality assurance process.

      CLICK HERE to ACCESS

      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.

      Icon of a tablet.


      Product and category reports with state-of-the-art data visualization.

      Icon of a phone.


      User-experience insight that reveals the intangibles of working with a vendor.

      SoftwareReviews 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. Combined with the insights of our expert analysts, our members receive unparalleled support in their buying journey.

      Logo for Salesforce.
      Est. 1999 | CA, USA | NYSE: CRM

      bio

      Link for their Twitter account. Link for their LinkedIn profile. Link for their website.
      Sales Cloud Enterprise allows you to be more efficient, more productive, more everything than ever before as it allows you to close more deals, accelerate productivity, get more leads, and make more insightful decisions.

      SoftwareReviews’ Enterprise CRM Rankings

      Strengths:
      • Breadth of features
      • Quality of features
      • Sales management functionality
      Areas to Improve:
      • Cost of service
      • Ease of implementation
      • Telephony and contact center management
      Logo gif for SoftwareReviews.
      8.0
      COMPOSITE SCORE
      8.3
      CX SCORE
      +77
      EMOTIONAL FOOTPRINT
      83%
      LIKELINESS TO RECOMMEND
      DOWNLOAD REPORT 600
      REVIEWS
      Vendor scores are driven by real-world practitioner reviews via SoftwareReviews. Composite, CX, EF and NPS scores pulled from live data as of June 2022. Rankings and ”strengths” and ”areas to improve” pulled from January 2022 Category Report.
      Sample of a Salesforce screen. Vendor Pulse rating. How often do we hear about Salesforce from our members for CRM? 'Very Frequently'.
      History of Salesforce in a vertical timeline.
      *Pricing correct as of August 2021. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.
      Logo for Salesforce.

      “Salesforce is the pre-eminent vendor in the CRM marketplace and is a force to be reckoned with in terms of the breadth and depth of its capabilities. The company was an early disruptor in the category, placing a strong emphasis from the get-go on a SaaS delivery model and strong end-user experience. This allowed them to rapidly gain market share at the expense of more complacent enterprise application vendors. A series of savvy acquisitions over the years has allowed Salesforce to augment their core Sales and Service Clouds with a wide variety of other solutions, from e-commerce to marketing automation to CPQ. Salesforce is a great fit for any organization looking to partner with a market leader with excellent functional breadth, strong interoperability, and a compelling technology and partner ecosystem. All of this comes at a price, however – Salesforce prices at a premium, and our members routinely opine that Salesforce’s commercial teams are overly aggressive – sometimes pushing solutions without a clear link to underpinning business requirements.”

      Ben Dickie
      Research Practice Lead, Info-Tech Research Group

      Sales Cloud Essentials Sales Cloud Professional Sales Cloud Enterprise Sales Cloud Ultimate
      • Starts at $25*
      • Per user/mo
      • Small businesses after basic functionality
      • Starts at $75*
      • Per user/mo
      • Mid-market target
      • Starts at $150*
      • Per user/mo
      • Enterprise target
      • Starts at $300*
      • Per user/mo
      • Strong upmarket feature additions
      Logo for Microsoft.


      Est. 1975 | WA, USA | NYSE: MSFT

      bio

      Link for their Twitter account.Link for their LinkedIn profile.Link for their website.
      Dynamics 365 Sales is an adaptive selling solution that helps your sales team navigate the realities of modern selling. At the center of the solution is an adaptive, intelligent system – prebuilt and ready to go – that actively monitors myriad signals and distills them into actionable insights.

      SoftwareReviews’ Enterprise CRM Rankings

      Strengths:

      • Business value created
      • Analytics and reporting
      • Lead management

      Areas to Improve:

      • Quote, contract, and proposals
      • Vendor support
      Logo gif for SoftwareReviews.
      8.1
      COMPOSITE SCORE
      8.3
      CX SCORE
      +84
      EMOTIONAL FOOTPRINT
      82%
      LIKELINESS TO RECOMMEND
      DOWNLOAD REPORT 198
      REVIEWS
      Vendor scores are driven by real-world practitioner reviews via SoftwareReviews. Composite, CX, EF and NPS scores pulled from live data as of June 2022. Rankings and ”strengths” and ”areas to improve” pulled from January 2022 Category Report.
      Sample of a Microsoft screen.Vendor Pulse rating. How often do we hear about Microsoft Dynamics from our Members? 'Very Frequently'.

      History of Microsoft in a vertical timeline.

      *Pricing correct as of June 2022. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.
      Logo for Microsoft.
      “”

      “Microsoft Dynamics 365 is a strong and compelling player in the CRM arena. While Microsoft is no stranger to the CRM space, their offerings here have seen steady and marked improvement over the last five years. Good functional breadth paired with a modern user interface and best-in-class Microsoft stack compatibility ensures that we consistently see them on our members’ shortlists, particularly when our members are looking to roll out CRM capabilities alongside other components of the Dynamics ecosystem (such as Finance, Operations, and HR). Today, Microsoft segments the offering into discrete modules for sales, service, marketing, commerce, and CDP. While Microsoft Dynamics 365 is a strong option, it’s occasionally mired by concerns that the pace of innovation and investment lags Salesforce (its nearest competitor). Additionally, the marketing module of the product is softer than some of its competitors, and Microsoft themselves points organizations with complex marketing requirements to a strategic partnership that they have with Adobe.”

      Ben Dickie
      Research Practice Lead, Info-Tech Research Group

      D365 Sales Professional D365 Sales Enterprise D365 Sales Premium
      • Starts at $65*
      • Per user/mo
      • Midmarket focus
      • Starts at $95*
      • Per user/mo
      • Enterprise focus
      • Starts at $135*
      • Per user/mo
      • Enterprise focus with customer intelligence
      Logo for Oracle.


      Est. 1977 | CA, USA | NYSE: ORCL

      bio

      Link for their Twitter account.Link for their LinkedIn profile.Link for their website.
      Oracle Engagement Cloud (CX Sales) provides a set of capabilities to help sales leaders transition smoothly from sales planning and execution through customer onboarding, account management, and support services.

      SoftwareReviews’ Enterprise CRM Rankings

      Strengths:

      • Quality of features
      • Activity and workflow management
      • Analytics and reporting

      Areas to Improve:

      • Marketing management
      • Product strategy & rate of improvement
      Logo gif for SoftwareReviews.
      7.8
      COMPOSITE SCORE
      7.9
      CX SCORE
      +77
      EMOTIONAL FOOTPRINT
      78%
      LIKELINESS TO RECOMMEND
      DOWNLOAD REPORT 140
      REVIEWS
      Vendor scores are driven by real-world practitioner reviews via SoftwareReviews. Composite, CX, EF and NPS scores pulled from live data as of June 2022. Rankings and ”strengths” and ”areas to improve” pulled from January 2022 Category Report.
      Sample of an Oracle screen.Vendor Pulse rating. How often do we hear about Oracle from our members for CRM? 'Frequently'.

      History of Oracle in a vertical timeline.

      Logo for Oracle.

      “Oracle is long-term juggernaut of the enterprise applications space. Their CRM portfolio is diverse – rather than a single stack, there are multiple Oracle solutions (many made by acquisition) that support CRM capabilities – everything from Siebel to JD Edwards to NetSuite to Oracle CX applications. The latter constitute Oracle’s most modern stab at CRM and are where the bulk of feature innovation and product development is occurring within their portfolio. While historically seen as lagging behind other competitors like Salesforce and Microsoft, Oracle has made excellent strides in improving their user experience (via their Redwoods design paradigm) and building new functional capabilities within their CRM products. Indeed, SoftwareReviews shows Oracle performing well in our most recent peer-driven reports. Nonetheless, we most commonly see Oracle as a pricier ecosystem play that’s often subordinate to a heavy Oracle footprint for ERP. Many of our members also express displeasure with Oracle as a vendor and highlight their heavy-handed “threat of audit” approach. ”

      Ben Dickie
      Research Practice Lead, Info-Tech Research Group

      Oracle CX Sales - Pricing Opaque:

      “Request a Demo”

      Logo for SAP.


      Est. 1972 | Germany | NYSE: SAP

      bio

      Link for their Twitter account.Link for their LinkedIn profile.Link for their website.
      SAP is the third-largest independent software manufacturer in the world, with a presence in over 120 countries. Having been in the industry for over 40 years, SAP is perhaps best known for its ERP application, SAP ERP.

      SoftwareReviews’ Enterprise CRM Rankings

      Strengths:

      • Ease of data integration

      Areas to Improve:

      • Lead management
      • Marketing management
      • Collaboration
      • Usability & intuitiveness
      • Analytics & reporting
      Logo gif for SoftwareReviews.
      7.4
      COMPOSITE SCORE
      7.8
      CX SCORE
      +74
      EMOTIONAL FOOTPRINT
      75%
      LIKELINESS TO RECOMMEND
      DOWNLOAD REPORT 108
      REVIEWS
      Vendor scores are driven by real-world practitioner reviews via SoftwareReviews. Composite, CX, EF and NPS scores pulled from live data as of June 2022. Rankings and ”strengths” and ”areas to improve” pulled from January 2022 Category Report.
      Sample of a SAP screen.Vendor Pulse rating. How often do we hear about SAP from our members for CRM? 'Occasionally'.

      History of SAP in a vertical timeline.

      *Pricing correct as of August 2021. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.
      Logo for SAP.

      “SAP is another mainstay of the enterprise applications market. While they have a sound breadth of capabilities in the CRM and customer experience space, SAP consistently underperforms in many of our relevant peer-driven SoftwareReviews reports for CRM and adjacent areas. CRM seems decidedly a secondary focus for SAP, behind their more compelling play in the enterprise resource planning (ERP) space. Indeed, most instances where we see SAP in our clients’ shortlists, it’s as an ecosystem play within a broader SAP strategy. If you’re blue on the ERP side, looking to SAP’s capabilities on the CRM front makes logical sense and can help contain costs. If you’re approaching a CRM selection from a greenfield lens and with no legacy vendor baggage for SAP elsewhere, experience suggests you’ll be better served by a vendor that places a higher degree of primacy on the CRM aspect of their portfolio.”

      Ben Dickie
      Research Practice Lead, Info-Tech Research Group

      SAP CRM - Pricing Opaque:

      “Request a Demo”

      Logo for pipedrive.


      Est. 2010 | NY, USA | Private

      bio

      Link for their Twitter account.Link for their LinkedIn profile.Link for their website.
      Pipedrive brings together the tools and data, the platform focuses sales professionals on fundamentals to advance deals through their pipelines. Pipedrive's goal is to make sales success inevitable - for salespeople and teams.

      SoftwareReviews’ Enterprise CRM Rankings

      Strengths:

      • Sales Management
      • Account & Contact Management
      • Lead Management
      • Usability & Intuitiveness
      • Ease of Implementation

      Areas to Improve:

      • Customer Service Management
      • Marketing Management
      • Product Strategy & Rate of Improvement
      Logo gif for SoftwareReviews.
      8.3
      COMPOSITE SCORE
      8.4
      CX SCORE
      +85
      EMOTIONAL FOOTPRINT
      85%
      LIKELINESS TO RECOMMEND
      DOWNLOAD REPORT 262
      REVIEWS
      Vendor scores are driven by real-world practitioner reviews via SoftwareReviews. Composite, CX, EF and NPS scores pulled from live data as of June 2022. Rankings and ”strengths” and ”areas to improve” pulled from January 2022 Category Report.
      Sample of a Pipedrive screen.Vendor Pulse rating. How often do we hear about Pipedrive from our members for CRM? 'Occasionally'.

      History of Pipedrive in a vertical timeline.

      *Pricing correct as of June 2022. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.
      Logo for Pipedrive.

      “A relatively new offering, Pipedrive has seen explosive growth over the last five years. They’re a vendor that has gone from near-obscurity to popping up frequently on our members’ shortlists. Pipedrive’s secret sauce has been a relentless focus on high-velocity sales enablement. Their focus on pipeline management, lead assessment and routing, and a good single pane of glass for sales reps has driven significant traction for the vendor when sales enablement is the driving rationale behind rolling out a new CRM platform. Bang for your buck is also strong with Pipedrive, with the vendor having a value-driven licensing and implementation model.

      Pipedrive is not without some shortcomings. It’s laser-focus on sales enablement is at the expense of deep capabilities for marketing and service management, and its profile lends itself better to SMBs and lower midmarket than it does large organizations looking for enterprise-grade CRM.”

      Ben Dickie
      Research Practice Lead, Info-Tech Research Group

      Essential Advanced Professional Enterprise
      • Starts at $12.50*
      • Per user/mo
      • Small businesses after basic functionality
      • Starts at $24.90*
      • Per user/mo
      • Small/mid-sized businesses
      • Starts at $49.90*
      • Per user/mo
      • Lower mid-market focus
      • Starts at $99*
      • Per user/mo
      • Enterprise focus
      Logo for SugarCRM.


      Est. 2004 | CA, USA | Private

      bio

      Link for their Twitter account.Link for their LinkedIn profile.Link for their website.
      Produces Sugar, a SaaS-based customer relationship management application. SugarCRM is backed by Accel-KKR.

      SoftwareReviews’ Enterprise CRM Rankings

      Strengths:

      • Ease of customization
      • Product strategy and rate of improvement
      • Ease of IT administration

      Areas to Improve:

      • Marketing management
      • Analytics and reporting
      Logo gif for SoftwareReviews.
      8.4
      COMPOSITE SCORE
      8.8
      CX SCORE
      +92
      EMOTIONAL FOOTPRINT
      84%
      LIKELINESS TO RECOMMEND
      DOWNLOAD REPORT 97
      REVIEWS
      Vendor scores are driven by real-world practitioner reviews via SoftwareReviews. Composite, CX, EF and NPS scores pulled from live data as of June 2022. Rankings and ”strengths” and ”areas to improve” pulled from January 2022 Category Report.
      Sample of a SugarCRM screen.Vendor Pulse rating. How often do we hear about SugarCRM from our members for CRM? 'Frequently'.
      History of SugarCRM in a vertical timeline.
      *Pricing correct as of August 2021. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.
      Logo for SugarCRM.

      “SugarCRM offers reliable baseline capabilities at a lower price point than other large CRM vendors. While SugarCRM does not offer all the bells and whistles that an Enterprise Salesforce plan might, SugarCRM is known for providing excellent vendor support. If your organization is only after standard features, SugarCRM will be a good vendor to shortlist.

      However, ensure you have the time and labor power to effectively implement and train on SugarCRM’s solutions. SugarCRM does not score highly for user-friendly experiences, with complaints centering on outdated and unintuitive interfaces. Setting up customized modules takes time to navigate, and SugarCRM does not provide a wide range of native integrations with other applications. To effectively determine whether SugarCRM does offer a feasible solution, it is recommended that organizations know exactly what kinds of integrations and modules they need.”

      Thomas Randall
      Research Director, Info-Tech Research Group

      Sugar Professional Sugar Serve Sugar Sell Sugar Enterprise Sugar Market
      • Starts at $52*
      • Per user/mo
      • Min. 3 users
      • Small businesses
      • Starts at $80*
      • Per user/mo
      • Min. 3 users
      • Focused on customer service
      • Starts at $80*
      • Per user/mo
      • Min. 3 users
      • Focused on sales automation
      • Starts at $80*
      • Per user/mo
      • Min. 3 users
      • On-premises, mid-sized businesses
      • Starts at $1000*
      • Priced per month
      • Min. 10k contacts
      • Large enterprise
      Logo for .


      Est. 2006 | MA, USA | HUBS (NYSE)

      bio

      Link for their Twitter account.Link for their LinkedIn profile.Link for their website.
      Develops software for inbound customer service, marketing, and sales. Software includes CRM, SMM, lead gen, SEO, and web analytics.

      SoftwareReviews’ Enterprise CRM Rankings

      Strengths:

      • Breadth of features
      • Product strategy and rate of improvement
      • Ease of customization

      Areas to Improve:

      • Ease of data integration
      • Customer service management
      • Telephony and call center management
      Logo gif for SoftwareReviews.
      8.3
      COMPOSITE SCORE
      8.4
      CX SCORE
      +84
      EMOTIONAL FOOTPRINT
      86%
      LIKELINESS TO RECOMMEND
      DOWNLOAD REPORT 97
      REVIEWS
      Vendor scores are driven by real-world practitioner reviews via SoftwareReviews. Composite, CX, EF and NPS scores pulled from live data as of June 2022. Rankings and ”strengths” and ”areas to improve” pulled from January 2022 Category Report.
      Sample of a HubSpot screen.Vendor Pulse rating. How often do we hear about HubSpot from our members for CRM? 'Frequently'.

      History of HubSpot in a vertical timeline.

      *Pricing correct as of August 2021. Listed in USD and absent discounts
      See pricing on vendor’s website for latest information.
      Logo for HubSpot.

      “ HubSpot is best suited for small to mid-sized organizations that need a range of CRM tools to enable growth across sales, marketing campaigns, and customer service. Indeed, HubSpot offers a content management solution that offers a central storage location for all customer and marketing data. Moreover, HubSpot offers plenty of freemium tools for users to familiarize themselves with the software before buying. However, though HubSpot is geared toward growing businesses, smaller organizations may not see high ROI until they begin to scale. The “Starter” and “Professional” plans’ pricing is often cited by small organizations as a barrier to commitment, and the freemium tools are not a sustainable solution. If organizations can take advantage of discount behaviors from HubSpot (e.g. a startup discount), HubSpot will be a viable long-term solution. ”

      Thomas Randall
      Research Director, Info-Tech Research Group

      Starter Professional Enterprise
      • Starts at $50*
      • Per month
      • Min. 2 users
      • Small businesses
      • Starts at $500*
      • Per month
      • Min. 5 users
      • Small/mid-sized businesses
      • Starts at $1200*
      • Billed yearly
      • Min. 10 users
      • Mid-sized/small enterprise
      Logo for Zoho.


      Est. 1996 | India | Private

      bio

      Link for their Twitter account.Link for their LinkedIn profile.Link for their website.
      Zoho Corporation offers a cloud software suite, providing a full operating system for CRM, alongside apps for finance, productivity, HR, legal, and more.

      SoftwareReviews’ Enterprise CRM Rankings

      Strengths:

      • Business value created
      • Breadth of features
      • Collaboration capabilities

      Areas to Improve:

      • Usability and intuitiveness
      Logo gif for SoftwareReviews.
      8.7
      COMPOSITE SCORE
      8.9
      CX SCORE
      +92
      EMOTIONAL FOOTPRINT
      85%
      LIKELINESS TO RECOMMEND
      DOWNLOAD REPORT 152
      REVIEWS
      Vendor scores are driven by real-world practitioner reviews via SoftwareReviews. Composite, CX, EF and NPS scores pulled from live data as of June 2022. Rankings and ”strengths” and ”areas to improve” pulled from January 2022 Category Report.
      Sample of a Zoho screen.Vendor Pulse rating. How often do we hear about Zoho from our members for CRM? 'Occasionally'.

      History of Zoho in a vertical timeline.

      *
      See pricing on vendor’s website for latest information.
      Logo for Zoho.

      “Zoho has a long list of software solutions for businesses to run end to end. As one of Zoho’s earliest software releases, though, ZohoCRM remains a flagship product. ZohoCRM’s pricing is incredibly competitive for mid/large enterprises, offering high business value for its robust feature sets. For those organizations that already utilize Zoho solutions (such as its productivity suite), ZohoCRM will be a natural extension.

      However, small/mid-sized businesses may wonder how much ROI they can get from ZohoCRM, when much of the functionality expected from a CRM (such as workflow automation) cannot be found until one jumps to the “Enterprise” plan. Given the “Enterprise” plan’s pricing is on par with other CRM vendors, there may not be much in a smaller organization’s eyes that truly distinguishes ZohoCRM unless they are already invested Zoho users.”

      Thomas Randall
      Research Director, Info-Tech Research Group

      Standard Professional Enterprise Ultimate
      • Starts at $20*
      • Per user/mo
      • Small businesses after basic functionality
      • Starts at $35*
      • Per user/mo
      • Small/mid-sized businesses
      • Adds inventory management
      • Starts at $50*
      • Per user/mo
      • Mid-sized/small enterprise
      • Adds Zia AI
      • Starts at $65*
      • Per user/mo
      • Enterprise
      • Bundles Zoho Analytics
      Logo for Zendesk.


      Est. 2009 | CA, USA | ZEN (NYSE)

      bio

      Link for their Twitter account.Link for their LinkedIn profile.Link for their website.
      Software developer for customer service. Founded in Copenhagen but moved to San Francisco after $6 million Series B funding from Charles River Ventures and Benchmark Capital.

      SoftwareReviews’ Enterprise CRM Rankings

      Strengths:

      • Quality of features
      • Breadth of features
      • Vendor support

      Areas to Improve:

      • Business value created
      • Ease of customization
      • Usability and intuitiveness
      Logo gif for SoftwareReviews.
      7.8
      COMPOSITE SCORE
      7.9
      CX SCORE
      +80
      EMOTIONAL FOOTPRINT
      72%
      LIKELINESS TO RECOMMEND
      DOWNLOAD REPORT 50
      REVIEWS
      Vendor scores are driven by real-world practitioner reviews via SoftwareReviews. Composite, CX, EF and NPS scores pulled from live data as of June 2022. Rankings and ”strengths” and ”areas to improve” pulled from January 2022 Category Report.
      Sample of a Zendesk screen.Vendor Pulse rating. How often do we hear about Zendesk from our members for CRM? 'Rarely'.

      History of Zendesk in a vertical timeline.

      *Pricing correct as of August 2021. Listed in USD and absent discounts
      See pricing on vendor’s website for latest information.
      Logo for Zendesk.

      “Zendesk’s initial growth was grounded in word-of-mouth advertising, owing to the popularity of its help desk solution’s design and functionality. Zendesk Sell has followed suit, receiving strong feedback for the breadth and quality of its features. Organizations that have already reaped the benefits of Zendesk’s customer service suite will find Zendesk Sell a straightforward fit for their sales teams.

      However, it is important to note that Zendesk Sell is predominantly focused on sales. Other key components of a CRM, such as marketing, are less fleshed out. Organizations should ensure they verify what requirements they have for a CRM before choosing Zendesk Sell – if sales process requirements (such as forecasting, call analytics, and so on) are but one part of what the organization needs, Zendesk Sell may not offer the highest ROI for the pricing offered.”

      Thomas Randall
      Research Director, Info-Tech Research Group

      Sell Team Sell Professional Sell Enterprise
      • Starts at $19*
      • Per user/mo
      • Max. 3 users
      • Small businesses
      • Basic functionality
      • Starts at $49*
      • Per user/mo
      • Small/mid-sized businesses
      • Advanced analytics
      • Starts at $99*
      • Per user/mo
      • Mid-sized/small enterprise
      • Task automation

      Speak with category experts to dive deeper into the vendor landscape

      Icon of a person.
      Fact-based reviews of business software from IT professionals.
      Icon of a magnifying glass over a chart.
      Top-tier data quality backed by a rigorous quality assurance process.
      CLICK HERE to ACCESS

      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.

      Icon of a tablet.
      Product and category reports with state-of-the-art data visualization.
      Icon of a phone.
      User-experience insight that reveals the intangibles of working with a vendor.

      SoftwareReviews 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. Combined with the insights of our expert analysts, our members receive unparalleled support in their buying journey.

      Conduct a day of rapid-fire vendor demos

      Zoom in on high-value use cases and answers to targeted questions

      Make sure the solution will work for your business

      Give each vendor 90 to 120 minutes to give a rapid-fire presentation. We suggest the following structure:

      • 30 minutes: company introduction and vision
      • 60 minutes: walk-through of two or three high-value demo scenarios
      • 30 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 video conference) 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.

      Graphic of an alarm clock.
      To kick-start scripting your demo scenarios, leverage our CRM Demo Script Template.

      A vendor scoring model provides a clear anchor point for your evaluation of CRM vendors based on a variety of inputs

      A vendor scoring model is a systematic method for effectively assessing competing vendors. A weighted-average scoring model is an approach that strikes a strong balance between rigor and evaluation speed.

      Info-Tech Insight

      Even the best scoring model will still involve some “art” rather than science – scoring categories such as vendor viability always entails a degree of subjective interpretation.

      How do I build a scoring model?

      • Start by shortlisting the key criteria you will use to evaluate your vendors. Functional capabilities should always be a critical category, but you’ll also want to look at criteria such as affordability, architectural fit, and vendor viability.
      • Depending on the complexity of the project, you may break down some criteria into sub-categories to assist with evaluation (for example, breaking down functional capabilities into constituent use cases so you can score each one).
      • Once you’ve developed the key criteria for your project, the next step is weighting each criterion. Your weightings should reflect the priorities for the project at hand. For example, some projects may put more emphasis on affordability, others on vendor partnership.
      • Using the information collected in the subsequent phases of this blueprint, score each criterion from 1-100, then multiply by the weighting factor. Add up the weighted scores to arrive at the aggregate evaluation score for each vendor on your shortlist.

      What are some of the best practices?

      • While the criteria for each project may vary, it’s helpful to have an inventory of repeatable criteria that can be used across application selection projects. The next slide contains an example that you can add or subtract from.
      • Don’t go overboard on the number of criteria: five to 10 weighted criteria should be the norm for most projects. The more criteria (and sub-criteria) you must score against, the longer it will take to conduct your evaluation. Always remember, link the level of rigor to the size and complexity of your project! It’s possible to create a convoluted scoring model that takes significant time to fill out but yields little additional value.
      • Creation of the scoring model should be a consensus-driven activity among IT, procurement, and the key business stakeholders – it should not be built in isolation. Everyone should agree on the fundamental criteria and weights that are employed.
      • Consider using not just the outputs of investigative interviews and RFP responses to score vendors, but also third-party review services like SoftwareReviews.

      Define how you’ll score CRM proposals and demos

      Define key CRM selection criteria for your organization – this should be informed by the following goals, use cases, and requirements covered in the blueprint.

      Criteria

      Description

      Functional CapabilitiesHow well does the vendor align with the top-priority functional requirements identified in your accelerated needs assessment? What is the vendor’s functional breadth and depth?
      AffordabilityHow affordable is this vendor? Consider a three-to-five-year total cost of ownership (TCO) that encompasses not just licensing costs, but also implementation, integration, training, and ongoing support costs.
      Architectural FitHow well does this vendor align with our direction from an enterprise architecture perspective? How interoperable is the solution with existing applications in our technology stack? Does the solution meet our deployment model preferences?
      ExtensibilityHow easy is it to augment the base solution with native or third-party add-ons as our business needs may evolve?
      ScalabilityHow easy is it to expand the solution to support increased user, data, and/or customer volumes? Are there any capacity constraints of the solution?
      Vendor ViabilityHow viable is this vendor? Are they an established player with a proven track record, or a new and untested entrant to the market? What is the financial health of the vendor? How committed are they to the particular solution category?
      Vendor VisionDoes the vendor have a cogent and realistic product roadmap? Are they making sensible investments that align with your organization’s internal direction?
      Emotional FootprintHow well does the vendor’s organizational culture and team dynamics align to yours?
      Third-Party Assessments and/or ReferencesHow well-received is the vendor by unbiased, third-party sources like SoftwareReviews? For larger projects, how well does the vendor perform in reference checks (and how closely do those references mirror your own situation)?

      Decision Point: Select the Finalist

      After reviewing all vendor responses to your RFP, conducting vendor demos, and running a pilot project (if applicable), the time has arrived to select your finalist.

      All core selection team members should hold a session to score each shortlisted vendor against the criteria enumerated on the previous slide – based on an in-depth review of proposals, the demo sessions, and any pilots or technical assessments.

      The vendor that scores the highest in aggregate is your finalist.

      Congratulations – you are now ready to proceed to final negotiation and inking a contract. This blueprint provides a detailed approach on the mechanics of a major vendor negotiation.

      Leverage Info-Tech’s research to plan and execute your CRM implementation

      Use Info-Tech Research Group’s three phase implementation process to guide your own planning.
      The three phases of software implementation: 'Assess', 'Prepare', 'Govern & Course Correct'. Sample of the 'Governance and Management of Enterprise Software Implementation' blueprint.

      Establish and execute an end-to-end, agile framework to succeed with the implementation of a major enterprise application.

      Visit this link

      Prepare for implementation: establish a clear resourcing plan

      Organizations rarely have sufficient internal staffing to resource a CRM project on their own. Consider the options for closing the gap in internal resource availability.

      The most common project resourcing structures for enterprise projects are:
      Your own staff +
      1. Management consultant
      2. Vendor consultant
      3. System integrator
      Info-Tech Insight

      When contemplating a resourcing structure, consider:

      • Availability of in-house implementation competencies and resources.
      • Timeline and constraints.
      • Integration environment complexity.

      Consider the following:

      Internal vs. External Roles and Responsibilities

      Clearly delineate between internal and external team responsibilities and accountabilities, and communicate this to your technology partner up front.

      Internal vs. External Accountabilities

      Accountability is different than responsibility. Your vendor or SI partner may be responsible for completing certain tasks, but be careful not to outsource accountability for the implementation – ultimately, the internal team will be accountable.

      Partner Implementation Methodologies

      Often vendors and/or SIs will have their own preferred implementation methodology. Consider the use of your partner's implementation methodology; however, you know what will work for your organization.

      Establish team composition

      1 – 2 hours

      Input: Skills assessment, Stakeholder analysis, Vendor partner selection

      Output: Team composition

      Materials: Sticky notes, Whiteboard, Markers

      Participants: Project team

      Use Info-Tech’s Governance and Management of Enterprise Software Implementation to establish your team composition. Within that blueprint:

      1. Assess the skills necessary for an implementation. Inventory the competencies required for the implementation project team. Map your internal resources to each competency as applicable.
      2. Select your internal implementation team. Determine who needs to be involved closely with the implementation. Key stakeholders should also be considered as members of your implementation team.
      3. Identify the number of external consultants/support required for implementation. Consider your in-house skills, timeline considerations, integration environment complexity, and cost constraints as you make your team composition plan. Be sure to dedicate an internal resource to managing the vendor and partner relationships.
      4. Document the roles and responsibilities, accountabilities, and other expectations of your team as they relate to each step of the implementation.

      Governance and Management of Enterprise Software Implementation

      Sample of the 'Governance and Management of Enterprise Software Implementation' blueprint.Follow our iterative methodology with a task list focused on the business must-have functionality to achieve rapid execution and to allow staff to return to their daily work sooner.

      Visit this link

      Ensure your implementation team has a high degree of trust and communication

      If external partners are needed, dedicate an internal resource to managing the vendor and partner relationships.

      Communication

      Teams must have some type of communication strategy. This can be broken into:
      • Regularity: Having a set time each day to communicate progress and a set day to conduct retrospectives.
      • Ceremonies: Injecting awards and continually emphasizing delivery of value can encourage relationship-building and constructive motivation.
      • Escalation: Voicing any concerns and having someone responsible for addressing those concerns.

      Proximity

      Distributed teams create complexity as communication can break down. This can be mitigated by:
      • Location: Placing teams in proximity can close the barrier of geographical distance and time zone differences.
      • Inclusion: Making a deliberate attempt to pull remote team members into discussions and ceremonies.
      • Communication tools: Having the right technology (e.g. video conference) can help bring teams closer together virtually.

      Trust

      Members should trust other members are contributing to the project and completing their required tasks on time. Trust can be developed and maintained by:
      • Accountability: Having frequent quality reviews and feedback sessions. As work becomes more transparent, people become more accountable.
      • Role clarity: Having a clear definition of what everyone’s role is.

      Plan for your implementation of CRM based on deployment model

      Place your CRM application into your IT landscape by configuring and adjusting the tool based on your specific deployment method.

      Icon of a housing development.
      On-Premises

      1. Identify custom features and configuration items
      2. Train developers and IT staff on new software investment
      3. Install software
      4. Configure software
      5. Test installation and configuration
      6. Test functionality

      Icon of a cloud upload.
      SaaS-based

      1. Train developers and IT staff on new software investment
      2. Set up connectivity
      3. Identify VPN or internal solution
      4. Check firewalls
      5. Validate bandwidth regulations

      Integration is a top IT challenge and critical to the success of the CRM suite

      CRM suites are most effective when they are integrated with ERP and MarTech solutions.

      Data interchange between the CRM solution and other data sources is necessary

      Formulate a comprehensive map of the systems, hardware, and software with which the CRM solution must be able to integrate. Customer data needs to constantly be synchronized: without this, you lose out on one of the primary benefits of CRM. These connections must be bidirectional for maximum value (i.e. marketing data to the CRM, customer data to MMS).
      Specialized projects that include an intricate prospect or customer list and complex rules may need to be built by IT The more custom fields you have in your CRM suite and point solutions, the more schema mapping you will have to do. Include this information in the RFP to receive guidance from vendors on the ease with which integration can be achieved.

      Pay attention to legacy apps and databases

      If you have legacy CRM, POS, or customer contact software, more custom code will be required. Many vendors claim that custom integration can be performed for most systems, but custom comes at a cost. Don’t just ask if they can integrate; ask how long it will take and for references from organizations which have been successful in this.
      When assessing the current application portfolio that supports CRM, the tendency will be to focus on the applications under the CRM umbrella, relating mostly to marketing, sales, and customer service. Be sure to include systems that act as inputs to, or benefit due to outputs from, the CRM or similar applications.

      CRM data flow

      Example of a CRM data flow.

      Be sure to include enterprise applications that are not included in the CRM application portfolio. Popular systems to consider for POIs include billing, directory services, content management, and collaboration tools.

      Sample CRM integration map

      Sample of a CRM integration map.

      Scenario: Failure to address CRM data integration will cost you in the long run

      A company spent $15 million implementing a new CRM system in the cloud and decided NOT to spend an additional $1.5 million to do a proper cloud DI tool procurement. The mounting costs followed.

      Cost Element – Custom Data Integration

      $

      2 FTEs for double entry of sales order data $ 100,000/year
      One-time migration of product data to CRM $ 240,000 otc
      Product data maintenance $ 60,000/year
      Customer data synchronization interface build $ 60,000 otc
      Customer data interface maintenance $ 10,000/year
      Data quality issues $ 100,000/year
      New SaaS integration built in year 3 $ 300,000 otc
      New SaaS integration maintenance $ 150,000/year

      Cost Element – Data Integration Tool

      $

      DI strategy and platform implementation $1,500,000 otc
      DI tool maintenance $ 15,000/year
      New SaaS integration point in year 3 $ 300,000 otc
      Thumbs down color coded red to the adjacent chart. Custom integration is costing this organization $300,000/year for one SaaS solution.
      Thumbs up color coded blue to the adjacent chart.

      The proposed integration solution would have paid for itself in 3-4 years and saved exponential costs in the long run.

      Proactively address data quality in the CRM during implementation

      Data quality is a make-or-break issue in a CRM platform; garbage in is garbage out.
      • CRM suites are one of the leading offenders for generating poor-quality data. As such, it’s important to have a plan in place for structuring your data architecture in such a way the poor data quality is minimized from the get-go.
      • Having a plan for data quality should precede data migration efforts; some types of poor data quality can be mitigated prior to migration.
      • There are five main types of poor-quality data found in CRM platforms.
        • Duplicate data: Duplicate records can be a major issue. Leverage dedicated deduplication tools to eliminate them.
        • Stale data: Out-of-date customer information can reduce the usefulness of the platform. Use automated social listening tools to help keep data fresh.
        • Incomplete data: Records with missing info limit platform value. Specify data validation parameters to mandate that all fields are filled in.
        • Invalid and conflicting data: These can create cascading errors. Establishing conflict resolution rules in ETL tools for data integration can lessen issues.
      Info-Tech Insight

      If you have a complex POI environment, appoint data stewards for each major domain and procure a deduplication tool. As the complexity of CRM system-to-system integrations increases, so will the chance that data quality errors will crop up – for example, bidirectional POI with other sources of customer information dramatically increase the chances of conflicting/duplicate data.

      Profile data, eliminate dead weight, and enforce standards to protect data

      Identify and eliminate dead weight

      Poor data can originate in the firm’s CRM system. Custom queries, stored procedures, or profiling tools can be used to assess the key problem areas.

      Loose rules in the CRM system may lead to records of no significant value in the database. Those rules need to be fixed, but if changes are made before the data is fixed, users could encounter database or application errors, which will reduce user confidence in the system.

      • Conduct a data flow analysis: map the path that data takes through the organization.
      • Use a mass cleanup to identify and destroy dead weight data. Merge duplicates either manually or with the aid of software tools. Delete incomplete data, taking care to reassign related data.
      • COTS packages typically allow power users to merge records without creating orphaned records in related tables, but custom-built applications typically require IT expertise.

      Create and enforce standards and policies

      Now that the data has been cleaned, it’s important to protect the system from relapsing.

      Work with business users to find out what types of data require validation and which fields should have changes audited. Whenever possible, implement drop-down lists to standardize values and make programming changes to ensure that truncation ceases.

      • Truncated data is usually caused by mismatches in data structures during either one-time data loads or ongoing data integrations.
      • Don’t go overboard on assigning required fields; users will just put key data in note fields.
      • Discourage the use of unstructured note fields: the data is effectively lost except if it gets subpoenaed.
      Info-Tech Insight

      Data quality concerns proliferate with the customization level of your platform. The more extensive the custom integration points and module/database extensions that you have made, the more you will need to have a plan in place for managing data quality from a reactive and proactive standpoint.

      Create a formal communication process throughout the CRM implementation

      Establish a comprehensive communication process around the CRM enterprise roll-out to ensure that end users stay informed.

      The CRM kick-off meeting(s) should encompass: 'The high-level application overview', 'Target business-user requirements', 'Target quality of service (QoS) metrics', 'Other IT department needs', 'Tangible business benefits of application', 'Special consideration needs'. The overall objective for interdepartmental CRM kick-off meetings is to confirm that all parties agree on certain key points and understand platform rationale and functionality.

      The kick-off process will significantly improve internal communications by inviting all affected internal IT groups, including business units, to work together to address significant issues before the application process is formally activated.

      Department groups or designated trainers should take the lead and implement a process for:

      • Scheduling CRM platform roll-out/kick-off meetings.
      • Soliciting preliminary input from the attending groups to develop further training plans.
      • Establishing communication paths and the key communication agents from each department who are responsible for keeping lines open moving forward.

      Ensure requirements are met with robust user acceptance testing

      User acceptance testing (UAT) is a test procedure that helps to ensure end-user requirements are met. Test cases can reveal bugs before the suite is implemented.

      Five Secrets of UAT Success

      Bracket with colors corresponding the adjacent list items.

      1

      Create the plan With the information collected from requirements gathering, create the plan. Make sure this information is added to the main project plan documentation.

      2

      Set the agenda The time allotted will vary depending on the functionality being tested. Ensure that the test schedule allows for the resolution of issues and discussion.

      3

      Determine who will participate Work with the relevant stakeholders to identify the people who can best contribute to system testing. Look for experienced power users who have been involved in earlier decision making about the system.

      4

      Highlight acceptance criteria Together with the UAT group, pinpoint the criteria to determine system acceptability. Refer back to requirements specified in use cases in the initial requirements-gathering stages of the project.

      5

      Collect end user feedback Weaknesses in resolution workflow design, technical architecture, and existing customer service processes can be highlighted and improved on with ongoing surveys and targeted interviews.

      Calculate post-deployment metrics to assess measurable value of the project

      Track the post-deployment results from the project and compare the metrics to the current state and target state.

      CRM Selection and Implementation Metrics
      Description Formula Current or Estimated Target Post-Deployment
      End-User Satisfaction # of Satisfied Users
      # of End Users
      70% 90% 85%
      Percentage Over/Under Estimated Budget Amount Spent - 100%
      Budget
      5% 0% 2%
      Percentage Over/Under Estimated Timeline Project Length - 100%
      Estimated Timeline
      10% -5% -10%

      CRM Strategy Metrics
      Description Formula Current or Estimated Target Post-Deployment
      Number of Leads Generated (per month) # of Leads Generated 150 200 250
      Average Time to Resolution (in minutes) Time Spent on Resolution
      # of Resolutions
      30 minutes 10 minutes 15 minutes
      Cost per Interaction by Campaign Total Campaign Spending
      # of Customer Interactions
      $17.00 $12.00 $12.00

      Select the Right CRM Platform

      CRM technology is critical to facilitate an organization’s relationships with customers, service users, employees, and suppliers. Having a structured approach to building a business case, defining key requirements, and engaging with the right shortlist of vendors to pick the best finalist is crucial.

      This selection guide allows organizations to execute a structured methodology for picking a CRM that aligns with their needs. This includes:
      • Alignment and prioritization of key business and technology drivers for a CRM selection business case.
      • Identification of key use cases and requirements for CRM.
      • Construction of a robust CRM RFP.
      • A strong market scan of key players.
      • A survey of crucial implementation considerations.
      This formal CRM selection initiative will drive business-IT alignment, identify sales and marketing automation priorities, and allow for the rollout of a platform that’s highly likely to satisfy all stakeholder needs.

      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

      Insight summary

      Stakeholder satisfaction is critical to your success

      Choosing a solution for a single use case and then expanding it to cover other purposes can be a way to quickly gain approvals and then make effective use of dollars spent. However, this can also be a nightmare if the product is not fit for purpose and requires significant customization effort for future use cases. Identify use cases early, engage stakeholders to define success, and recognize where you need to find balance between a single off-the-shelf CRM platform and adjacent MarTech or sales enablement systems.

      Build a business case

      An effective business case isn’t a single-purpose document for obtaining funding. It can also be used to drive your approach to product selection, requirements gathering, and ultimately evaluating stakeholder and user satisfaction.

      Use your business case to define use cases and milestones as well as success.

      Balance process with technology

      A new solution with old processes will result in incremental increased value. Evaluate existing processes and identify opportunities to improve and remove workarounds. Then define requirements.

      You may find that the tools you have would be adequate with an upgrade and tool optimization. If not, this exercise will prepare you to select the right solution for your current and future needs.

      Drive toward early value

      Lead with the most important benefit and consider the timeline. Most stakeholders will lose interest if they don’t realize benefits within the fist year. Can you reach your goal and report success within that timeline?

      Identify secondary, incremental customer engagement improvements that can be made as you work toward the overall goal to be achieved at the one-year milestone.

      Related Info-Tech Research

      Stock image of an office worker. Build a Strong Technology Foundation for Customer Experience Management
      • Any CRM project needs to be guided by the broader strategy around customer engagement. This blueprint explores how to create a strong technology enablement approach for CXM using voice of the customer analysis.
      Stock image of a target with arrows. Improve Requirements Gathering
      • 70% of projects that fail do so because of poor requirements. If you need to double-click on best practices for eliciting, analyzing, and validating requirements as you build up your CRM picklist and RFP, this blueprint will equip you with the knowledge and tools you need to hit the ground running.
      Stock image of a pen on paper. Drive Successful Sourcing Outcomes with a Robust RFP Process
      • Managing a complex RFP process for an enterprise application like a CRM platform can be a challenging undertaking. This blueprint zooms into how to build, run, administer, and evaluate RFP responses effectively.

      Bibliography

      “Doomed From the Start? Why a Majority of Business and IT Teams Anticipate Their Software Development Projects Will Fail.” Geneca, 25 Jan. 2017. Web.

      Hall, Kerrie. “The State of CRM Data Management 2020.” Validity. 27 April 2020. Web.

      Hinchcliffe, Dion. “The Evolving Role of the CIO and CMO in Customer Experience.” ZDNet, 22 Jan. 2020. Web.

      Klie, L. “CRM Still Faces Challenges, Most Speakers Agree: CRM Systems Have Been Around for Decades, but Interoperability and Data Siloes Still Have to Be Overcome.” CRM Magazine, vol. 23, no. 5, 2019, pp. 13-14.

      Markman, Jon. "Netflix Knows What You Want... Before You Do." Forbes. 9 Jun. 2017. Web.

      Morgan, Blake. “50 Stats That Prove The Value Of Customer Experience.” Forbes, 24 Sept. 2019. Web.

      Taber, David. “What to Do When Your CRM Project Fails.” CIO Magazine, 18 Sept. 2017. Web.

      “The State of Project Management Annual Survey 2018.” Wellingtone, 2018. Web.

      “The History of Microsoft Dynamics.” Eswelt. 2021. Accessed 8 June 2022.

      “Unlock the Mysteries of Your Customer Relationships.” Harvard Business Review. 1 July 2014. Accessed 30 Mar. 2016.

      Develop Meaningful Service Metrics

      • Buy Link or Shortcode: {j2store}399|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: $20,308 Average $ Saved
      • member rating average days saved: 30 Average Days Saved
      • Parent Category Name: Service Management
      • Parent Category Link: /service-management
      • IT organizations measure services from a technology perspective but rarely from a business goal or outcome perspective.
      • Most organizations do a poor job of identifying and measuring service outcomes over the duration of a service’s lifecycle – never ensuring the services remain valuable and meet expected long-term ROI.

      Our Advice

      Critical Insight

      • Service metrics are critical to ensuring alignment of IT service performance and business service value achievement.
      • Service metrics reinforce positive business and end-user relationships by providing user-centric information that drives responsiveness and consistent service improvement.
      • Poorly designed metrics drive unintended and unproductive behaviors that have negative impacts on IT and produce negative service outcomes.

      Impact and Result

      Effective service metrics will provide the following service gains:

      • Confirm service performance and identify gaps.
      • Drive service improvement to maximize service value.
      • Validate performance improvements while quantifying and demonstrating business value.
      • Ensure service reporting aligns with end-user experience.
      • Achieve and confirm process and regulatory compliance.

      Which will translate into the following relationship gains:

      • Embed IT into business value achievement.
      • Improve the relationship between the business and IT.
      • Achieve higher customer satisfaction (happier end users receiving expected service, the business is able to identify how things are really performing).
      • Reinforce desirable actions and behaviors from both IT and the business.

      Develop Meaningful Service Metrics Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should develop meaningful service metrics, 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:

      • Develop Meaningful Service Metrics – Executive Brief
      • Develop Meaningful Service Metrics – Phases 1-3

      1. Design the metrics

      Identify the appropriate service metrics based on stakeholder needs.

      • Develop Meaningful Service Metrics to Ensure Business and User Satisfaction – Phase 1: Design the Metrics
      • Metrics Development Workbook

      2. Design reports and dashboards

      Present the right metrics in the most interesting and stakeholder-centric way possible.

      • Develop Meaningful Service Metrics to Ensure Business and User Satisfaction – Phase 2: Design Reports and Dashboards
      • Metrics Presentation Format Selection Guide

      3. Implement, track, and maintain

      Run a pilot with a smaller sample of defined service metrics, then continuously validate your approach and make refinements to the processes.

      • Develop Meaningful Service Metrics to Ensure Business and User Satisfaction – Phase 3: Implement, Track, and Maintain
      • Metrics Tracking Tool
      [infographic]

      Workshop: Develop Meaningful Service Metrics

      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 Metrics

      The Purpose

      Define stakeholder needs for IT based on their success criteria and identify IT services that are tied to the delivery of business outcomes.

      Derive meaningful service metrics based on identified IT services and validate that metrics can be collected and measured.

      Key Benefits Achieved

      Design meaningful service metrics from stakeholder needs.

      Validate that metrics can be collected and measured.

      Activities

      1.1 Determine stakeholder needs, goals, and pain points.

      1.2 Determine the success criteria and related IT services.

      1.3 Derive the service metrics.

      1.4 Validate the data collection process.

      1.5 Validate metrics with stakeholders.

      Outputs

      Understand stakeholder priorities

      Adopt a business-centric perspective to align IT and business views

      Derive meaningful business metrics that are relevant to the stakeholders

      Determine if and how the identified metrics can be collected and measured

      Establish a feedback mechanism to have business stakeholders validate the meaningfulness of the metrics

      2 Design Reports and Dashboards

      The Purpose

      Determine the most appropriate presentation format based on stakeholder needs.

      Key Benefits Achieved

      Ensure the metrics are presented in the most interesting and stakeholder-centric way possible to guarantee that they are read and used.

      Activities

      2.1 Understand the different presentation options.

      2.2 Assess stakeholder needs for information.

      2.3 Select and design the metric report.

      Outputs

      Learn about infographic, scorecard, formal report, and dashboard presentation options

      Determine how stakeholders would like to view information and how the metrics can be presented to aid decision making

      Select the most appropriate presentation format and create a rough draft of how the report should look

      3 Implement, Track, and Maintain Your Metrics

      The Purpose

      Run a pilot with a smaller sample of defined service metrics to validate your approach.

      Make refinements to the implementation and maintenance processes prior to activating all service metrics.

      Key Benefits Achieved

      High user acceptance and usability of the metrics.

      Processes of identifying and presenting metrics are continuously validated and improved.

      Activities

      3.1 Select the pilot metrics.

      3.2 Gather data and set initial targets.

      3.3 Generate the reports and validate with stakeholders.

      3.4 Implement the service metrics program.

      3.5 Track and maintain the metrics program.

      Outputs

      Select the metrics that should be first implemented based on urgency and impact

      Complete the service intake form for a specific initiative

      Create a process to gather data, measure baselines, and set initial targets

      Establish a process to receive feedback from the business stakeholders once the report is generated

      Identify the approach to implement the metrics program across the organization

      Set up mechanism to ensure the success of the metrics program by assessing process adherence and process validity

      Further reading

      Develop Meaningful Service Metrics

      Select IT service metrics that drive business value.

      ANALYST PERSPECTIVE

      Are you measuring and reporting what the business needs to know?

      “Service metrics are one of the key tools at IT’s disposal in articulating and ensuring its value to the business, yet metrics are rarely designed and used for that purpose.

      Creating IT service metrics directly from business and stakeholder outcomes and goals, written from the business perspective and using business language, is critical to ensuring that the services that IT provides are meeting business needs.

      The ability to measure, manage, and improve IT service performance in relation to critical business success factors, with properly designed metrics, embeds IT in the value chain of the business and ensures IT’s focus on where and how it enables business outcomes.”

      Valence Howden,
      Senior Manager, CIO Advisory
      Info-Tech Research Group

      Our understanding of the problem

      This Research Is Designed For:
      • CIO
      • IT VPs
      This Research Will Help You:
      • Align business/IT objectives (design top-down or outside-in)
      • Significantly improve the relationship between the business and IT aspects of the organization
      • Reinforce desirable actions and behaviors
      This Research Will Also Assist:
      • Service Level Managers
      • Service Owners
      • Program Owners
      This Research Will Help Them
      • Identify unusual deviations from the normal operating state
      • Drive service improvement to maximize service value
      • Validate the value of performance improvements while quantifying and demonstrating benefits realization

      Executive summary

      Situation

      • IT organizations measure services from a technology perspective yet rarely measure services from a business goal/outcome perspective.
      • Most organizations do a poor job of identifying and measuring service outcomes over the duration of a service’s lifecycle – never ensuring the services remain valuable and meet expected long-term ROI.

      Complication

      • IT organizations have difficulty identifying the right metrics to demonstrate the value of IT services to the business in tangible terms.
      • IT metrics, as currently designed, reinforce division between the IT and business perspectives of service performance. They drive siloed thinking and finger-pointing within the IT structure, and prevent IT resources from understanding how their work impacts business value.

      Resolution

      • Our program enables IT to develop the right service metrics to tie IT service performance to business value and user experience.
      • Ensure the metrics you implement have immediate stakeholder value, reinforcing alignment between IT and the business while influencing behavior in the desired direction.
      • Make sure that your metrics are defined in relation to the business goals and drivers, ensuring they will provide actionable outcomes.

      Info-Tech Insight

      1. Service metrics are critical to ensuring alignment of IT service performance and business service value achievement.
      2. Service metrics reinforce positive business and end-user relationships by providing user-centric information that drives responsiveness and consistent service improvement.
      3. Poorly designed metrics drive unintended and unproductive behaviors, which have negative impacts on IT and produce negative service outcomes.

      Service metrics 101

      What are service metrics?

      Service metrics measure IT services in a way that relates to a business outcome. IT needs to measure performance from the business perspective using business language.

      Why do we need service metrics?

      To ensure the business cares about the metrics that IT produces, start with business needs to make sure you’re measuring the right things. This will give IT the opportunity talk to the right stakeholders and develop metrics that will meet their business needs.

      Service metrics are designed with the business perspective in mind, so they are fully aligned with business objectives.

      Perspectives Matter

      Different stakeholders will require different types of metrics. A CEO may require metrics that provide a snapshot of the critical success of the company while a business manager is more concerned about the performance metrics of their department.

      What are the benefits of implementing service metrics?

      Service metrics help IT communicate with the business in business terms and enables IT to articulate how and where they provide business value. Business stakeholders can also easily understand how IT services contribute to their success.

      The majority of CIOs feel metrics relating to business value and stakeholder satisfaction require significant improvement

      A significantly higher proportion of CIOs than CEOs feel that there is significant improvement necessary for business value metrics and stakeholder satisfaction reporting. Stacked horizontal bar chart presenting survey results from CIOs and CXOs of 'Business Value Metrics'. Answer options are 'Effective', 'Some Improvement Necessary', 'Significant Improvement Necessary', and 'Not Required'.N=364

      Stacked horizontal bar chart presenting survey results from CIOs and CXOs of 'Stakeholder Satisfaction Reporting'. Answer options are 'Effective', 'Some Improvement Necessary', 'Significant Improvement Necessary', and 'Not Required'.N=364

      (Source: Info-Tech CIO-CXO Alignment Diagnostic Survey)

      Meaningless metrics are a headache for the business

      A major pitfall of many IT organizations is that they often provide pages of technical metrics that are meaningless to their business stakeholders.

      1. Too Many MetricsToo many metrics are provided and business leaders don’t know what to do with these metrics.
      2. Metrics Are Too TechnicalIT provides technical metrics that are hard to relate to business needs, and methods of calculating metrics are not clearly understood, articulated, and agreed on.
      3. Metrics Have No Business ValueService metrics are not mapped to business goals/objectives and they drive incorrect actions or spend.
      When considering only CEOs who said that stakeholder satisfaction reporting needed significant improvement, the average satisfaction score goes down to 61.6%, which is a drop in satisfaction of 12%.

      A bar that says 73% dropping to a bar that says 61%. Description above.

      (Source: Info-Tech Research Group CIO-CXO Alignment Diagnostic Survey)

      Poorly designed metrics hurt IT’s image within the organization

      By providing metrics that do not articulate the value of IT services, IT reinforces its role as a utility provider and an outsider to strategic decisions.

      When the CIOs believe business value metrics weren’t required, 50% of their CEOs said that significant improvements were necessary.

      Pie Chart presenting the survey results from CEOs regarding 'Business Value Metrics'. Description above.

      (Source: Info-Tech Research Group CIO-CXO Alignment Diagnostic Survey)
      1. Reinforce the wrong behaviorThe wrong metrics drive us-against-them, siloed thinking within IT, and meeting metric targets is prioritized over providing meaningful outcomes.
      2. Do not reflect user experienceMetrics don’t align with actual business/user experience, reinforcing a poor view of IT services.
      3. Effort ≠ ValueInvesting dedicated resources and effort to the achievement of the wrong metrics will only leave IT more constrained for other important initiatives.

      Articulate meaningful service performance that supports the achievement of business outcomes

      Service metrics measure the performance of IT services and how they enable or drive the activity outcomes.

      A business process consists of multiple business activities. In many cases, these business activities require one or more supporting IT services.

      A 'Business Process' broken down to its parts, multiple 'Business Activities' and their 'IT Services'. For each business process, business stakeholders and their goals and objectives should be identified.

      For each business activity that supports the completion of a business process, define the success criteria that must be met in order to produce the desirable outcome.

      Identify the IT services that are used by business stakeholders for each business activity. Measure the performance of these services from a business perspective to arrive at the appropriate service metrics.

      Differentiate between different types of metrics

      Stakeholders have different goals and objectives; therefore, it is critical to identify what type of metrics should be presented to each stakeholder.

      Business Metrics

      Determine Business Success

      Business metrics are derived from a pure business perspective. These are the metrics that the business stakeholders will measure themselves on, and business success is determined using these metrics.

      Arrow pointing right.

      Service Metrics

      Manage Service Value to the Business

      Service metrics are used to measure IT service performance against business outcomes. These metrics, while relating to IT services, are presented in business terms and are tied to business goals.

      Arrow pointing right.

      IT Metrics

      Enable Operational Excellence

      IT metrics are internal to the IT organization and used to manage IT service delivery. These metrics are technical, IT-specific, and drive action for IT. They are not presented to the business, and are not written in business language.

      Implementing service metrics is a key step in becoming a service provider and business partner

      As a prerequisite, IT organizations must have already established a solid relationship with the business and have a clear understanding of its critical business-facing services.

      At the very least, IT needs to have a service-oriented view and understand the specific needs and objectives associated with each stakeholder.

      Visualization of 'Business Relationship Management' with an early point on the line representing 'Service Provider: Establish service-oriented culture and business-centric service delivery', and the end of the line being 'Strategic Partner'.

      Once IT can present service metrics that the business cares about, it can continue on the service provider journey by managing the performance of services based on business needs, determine and influence service demand, and assess service value to maximize benefits to the business.

      Which processes drive service metrics?

      Both business relationship management (BRM) and service level management (SLM) provide inputs into and receive outputs from service metrics.

      Venn Diagram of 'Business Relationship Management', 'Service Metrics', and 'Service Level Management'.

      Business Relationship Management

      BRM works to understand the goals and objectives of the business and inputs them into the design of the service metrics.

      Service Metrics

      BRM leverages service metrics to help IT organizations manage the relationship with the business.

      BRM articulates and manages expectations and ensures IT services are meeting business requirements.

      Which processes drive service metrics?

      Both BRM and SLM provide inputs into and receive outputs from service metrics.

      Venn Diagram of 'Business Relationship Management', 'Service Metrics', and 'Service Level Management'.

      Service Level Management

      SLM works with the business to understand service requirements, which are key inputs in designing the service metrics.

      Service Metrics

      SLM leverages service metrics in overseeing the day-to-day delivery of IT services. It ensures they are provided to meet expected service level targets and objectives.

      Effective service metrics will deliver both service gains and relationship gains

      Effective service metrics will provide the following service gains:

      • Confirm service performance and identify gaps
      • Drive service improvement to maximize service value
      • Validate performance improvements while quantifying and demonstrating business value
      • Ensure service reporting aligns with end-user experience
      • Achieve and confirm process and regulatory compliance
          Which will translate into the following relationship gains:
          • Embed IT into business value achievement
          • Improve relationship between the business and IT
          • Achieve higher customer satisfaction (happier end users receiving expected service, the business is able to identify how things are really performing)
          • Reinforce desirable actions and behaviors from both IT and the business

      Don’t let conventional wisdom become your roadblock

      Conventional Wisdom

      Info-Tech Perspective

      Metrics are measured from an application or technology perspective Metrics need to be derived from a service and business outcome perspective.
      The business doesn’t care about metrics Metrics are not usually designed to speak in business terms about business outcomes. Linking metrics to business objectives creates metrics that the business cares about.
      It is difficult to have a metrics discussion with the business It is not a metrics/number discussion, it is a discussion on goals and outcomes.
      Metrics are only presented for the implementation of the service, not the ongoing outcome of the service IT needs to focus on service outcome and not project outcome.
      Quality can’t be measured Quality must be measured in order to properly manage services.

      Our three-phase approach to service metrics development

      Let Info-Tech guide you through your service metrics journey

      1

      2

      3

      Design Your Metrics Develop and Validate Reporting Implement, Track, and Maintain
      Sample of Phase 1 of Info-Tech's service metric development package, 'Design Your Metrics'. Sample of Phase 2 of Info-Tech's service metric development package, 'Develop and Validate Reporting'. Sample of Phase 3 of Info-Tech's service metric development package, 'Implement, Track, and Maintain'.
      Start the development and creation of your service metrics by keeping business perspectives in mind, so they are fully aligned with business objectives. Identify the most appropriate presentation format based on stakeholder preference and need for metrics. Track goals and success metrics for your service metrics programs. It allows you to set long-term goals and track your results over time.

      CIOs must actively lead the design of the service metrics program

      The CIO must actively demonstrate support for the service metrics program and lead the initial discussions to determine what matters to business leaders.

      1. Lead the initiative by defining the need
        Show visible support and demonstrate importance
      2. Articulate the value to both IT and the business
        Establish the urgency and benefits
      3. Select and assemble an implementation group
        Find the best people to get the job done
      4. Drive initial metrics discussions: goals, objectives, actions
        Lead brainstorming with senior business leaders
      5. Work with the team to determine presentation formats and communication methods
        Identify the best presentation approach for senior stakeholders
      6. Establish a feedback loop for senior management
        Solicit feedback on improvements
      7. Validate the success of the metrics
        Confirm service metrics support business outcomes

      Measure the success of your service metrics

      It is critical to determine if the designed service metrics are fulfilling their intended purpose. The process of maintaining the service metrics program and the outcomes of implementing service metrics need to be monitored and tracked.

      Validating Service Metrics Design

      Target Outcome

      Related Metrics

      The business is enabled to identify and improve service performance to their end customer # of improvement initiatives created based on service metrics
      $ cost savings/revenue generated due to actions derived from service metrics

      Procedure to validate the usefulness of IT metrics

      # / % of service metrics added/removed per year

      Alignment between IT and business objectives and processes Business’ satisfaction with IT

      Measure the success of your service metrics

      It is critical to determine if the designed service metrics are fulfilling their intended purpose. The process of maintaining the service metrics program and the outcomes of implementing service metrics need to be monitored and tracked.

      Validating Service Metrics Process

      Target Outcome

      Related Metrics

      Properly defined service metrics aligned with business goals/outcomes
      Easy understood measurement methodologies
      % of services with (or without) defined service metrics

      % of service metrics tied to business goals

      Consistent approach to review and adjust metrics# of service metrics adjusted based on service reviews

      % of service metrics reviewed on schedule

      Demonstrate monetary value and impact through the service metrics program

      In a study done by the Aberdeen Group, organizations engaged in the use of metrics benchmarking and measurement have:
      • 88% customer satisfaction rate
      • 60% service profitability
      • 15% increase in workforce productivity over the last 12 months

      Stock image of a silhouette of three people's head and shoulders.
      (Source: Aberdeen Group. “Service Benchmarking and Measurement.”)

      A service metric is defined for: “Response time for Business Application A

      The expected response time has not been achieved and this is visible in the service metrics. The reduced performance has been identified as having an impact of $250,000 per month in lost revenue potential.

      The service metric drove an action to perform a root-cause analysis, which identified a network switch issue and drove a resolution action to fix the technology and architect redundancy to ensure continuity.

      The fix eliminated the performance impact, allowing for recovery of the $250K per month in revenue, improved end-user confidence in the organization, and increased use of the application, creating additional revenue.

      Implementing and measuring a video conferencing service

      CASE STUDY
      Industry: Manufacturing | Source: CIO interview and case material
      Situation

      The manufacturing business operates within numerous countries and requires a lot of coordination of functions and governance oversight. The company has monthly meetings, both regional and national, and key management and executives travel to attend and participate in the meetings.

      Complication

      While the meetings provide a lot of organizational value, the business has grown significantly and the cost of business travel has started to become prohibitive.

      Action

      It was decided that only a few core meetings would require onsite face-to-face meetings, and for all other meetings, the company would look at alternative means. The face-to-face aspect of the meetings was still considered critical so they focused on options to retain that aspect.

      The IT organization identified that they could provide a video conferencing service to meet the business need. The initiative was approved and rolled out in the organization.

      Result:

      IT service metrics needed to be designed to confirm that the expected value outcome of the implementation of video conferencing was achieved.

      Under the direction of the CIO, the business goals and needs driving use of the service (i.e. reduction in travel costs, efficiency, no loss of positive outcome) were used to identify success criteria and key questions to confirm success.

      With this information, the service manager was able to implement relevant service metrics in business language and confirmed an 80% adoption rate and a 95% success rate in term meetings running as expected and achieving core outcomes.

      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

      Develop meaningful service metrics to ensure business and user satisfaction

      1. Design the Metrics 2. Design Reports and Dashboards 3. Implement, Track, and Maintain
      Supporting Tool icon

      Best-Practice Toolkit

      1. Defining stakeholder needs for IT based on their success criteria
      2. Derive meaningful service metrics based on identified IT services and validate with business stakeholders
      3. Validate metrics can be collected and measured
      4. Determine calculation methodology
      1. Presentation format selected based on stakeholder needs and preference for information
      2. Presentation format validated with stakeholders
      1. Identify metrics that will be presented first to the stakeholders based on urgency or impact of the IT service
      2. Determine the process to collect data, select initial targets, and integrate with SLM and BRM functions
      3. Roll out the metrics implementation for a broader audience
      4. Establish roles and timelines for metrics maintenance

      Guided Implementations

      • Design metrics based on business needs
      • Validate the metrics
      • Select presentation format
      • Review metrics presentation design
      • Select and implement pilot metrics
      • Determine rollout process and establish maintenance/tracking mechanism
      Associated Activity icon

      Onsite Workshop

      Module 1:
      Derive Service Metrics From Business Goals
      Module 2:
      Select and Design Reports and Dashboards
      Module 3:
      Implement, Track, and Maintain Your Metrics to Ensure Success
      Phase 1 Outcome:
      • Meaningful service metrics designed from stakeholder needs
      Phase 2 Outcome:
      • Appropriate presentation format selected for each stakeholder
      Phase 3 Outcome:
      • Metrics implemented and process established to maintain and track program success

      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
      Design the Metrics
      Determine Presentation Format and Implement Metrics
      Gather Service Level Requirements
      Monitor and Improve Service Levels

      Activities

      • 1.1 Determine stakeholder needs
      • 1.2 Determine success criteria and key performance indicators
      • 1.3 Derive metrics
      • 1.4 Validate the metric collection
      • 2.1 Discuss stakeholder needs/preference for data and select presentation format
      • 2.2 Select and design the metric report
      • Requirements
      • 3.1 Determine the business requirements
      • 3.2 Negotiate service levels
      • 3.3 Align operational level agreements (OLAs) and supplier contracts
      • 4.1 Conduct service report and perform service review
      • 4.2 Communicate service review
      • 4.3 Remediate issues using action plan
      • 4.4 Proactive prevention

      Deliverables

      1. Metrics Development Workbook
      1. Metrics Presentation Format Selection Guide
      2. Metrics Tracking Tool
      1. Service Level Management SOP
      2. Service Level Agreement
      1. Service Level Report
      2. Service Level Review
      3. Business Satisfaction Report

      Develop Meaningful Service Metrics to Ensure Business and User Satisfaction

      PHASE 1

      Design the Metrics

      Step (1): Design the Metrics

      PHASE 1 PHASE 2 PHASE 3

      1.1

      Derive the Service Metrics

      1.2

      Validate the Metrics

      2.1

      Determine Reporting Format

      3.1

      Select Pilot Metrics

      3.2

      Activate and Maintain Metrics

      This step involves the following participants:

      • CIO
      • Business Relationship Manager (BRM)
      • Service Level Manager (SLM)

      Outcomes of this step

      • Defined stakeholder needs for IT based on their success criteria
      • Identified IT services that are tied to the delivery of business outcomes
      • Derived meaningful service metrics based on identified IT services and validated with business stakeholders
      • Validated that metrics can be collected and measured
      • Determined calculation methodology

      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: Design the Metrics

      Proposed Time to Completion (in weeks): 4 weeks
      Step 1.1: Design Metrics Step 1.2: Validate the Metrics
      Start with an analyst kick-off call:
      • Determine the stakeholder and their needs
      • Identify IT services that are tied to the delivery of business outcomes
      • Derive the service metrics
      Review findings with analyst:
      • For the selected metrics, identify the data source for collection
      • Validate whether or not the data can be created
      • Create a calculation method for the metrics
      Then complete these activities…
      • Using the methodology provided, identify additional stakeholders and map out their success criteria, including KPIs to determine the appropriate service metrics
      Then complete these activities…
      • Determine whether the designed metrics are measurable, and if so, how
      With these tools & templates:
      • Metrics Development Workbook
      With these tools & templates:
      • Metrics Development Workbook

      Design your service metrics – overview

      Figure representing 'CIO'. Step 1
      Derive your service metrics

      Metrics Worksheet

      Figure representing 'SLM' and/or 'BRM'. Step 2
      Validate your metrics

      Metrics Worksheet

      Figures representing 'CIO', 'SLM', and/or 'BRM'. Step 3
      Confirm with stakeholders

      Metrics Tracking Sheet

      A star.

      Defined IT Service Metrics

      Deriving the right metrics is critical to ensuring that you will generate valuable and actionable service metrics.

      Derive your service metrics from business objectives and needs

      Service metrics must be designed with the business perspective in mind so they are fully aligned with business objectives.

      Thus, IT must start by identifying specific stakeholder needs. The more IT understands about the business, the more relevant the metrics will be to the business stakeholders.

      1. Who are your stakeholders?
      2. What are their goals and pain points?
      3. What do the stakeholders need to know?
      4. What do I need to measure?
      5. Derive your service metrics

      Derive your service metrics

      Supporting Tool icon 1.1 Metrics Development Workbook

      This workbook guides the development and creation of service metrics that are directly tied to stakeholder needs.

      This process will ensure that your service metrics are designed with the business perspective in mind so they are fully aligned with business objectives.

      1. Who are the relevant stakeholders?
      2. What are the goals and pain points of your stakeholders?
      3. What do the stakeholders need to know?
      4. What does IT need to measure?
      5. What are the appropriate IT metrics?

      Download the Metrics Development Workbook.

      Sample of Info-Tech's Metrics Development Workbook.

      Determine your stakeholders

      Supporting Tool icon 1.1 0.5 Hour

      Who are your stakeholders?

      1. Identify the primary stakeholders of your service metrics. Stakeholders are the people who have a very specific need to know about how IT services affect their business outcomes. Different stakeholders can have different perspective on the same IT service metric.Most often, the primary target of service metrics are the business stakeholders, e.g. VP of a business unit.
      2. Identify any additional stakeholders. The CIO is also a stakeholder since they are effectively the business relationship manager for the senior leaders.

      Video Conferencing Case Study
      Manufacturing company

      For this phase, we will demonstrate how to derive the service metrics by going through the steps in the methodology.

      At a manufacturing company, the CIO’s main stakeholder is the CEO, whose chief concern is to improve the financial position of the company.

      Identify goals and pain points of your stakeholders

      Supporting Tool icon 1.2 0.5 Hour

      What are their goals and pain points?

      1. Clearly identify each stakeholder’s business goals and outcomes. These would be particular business goals related to a specific business unit.
      2. Identify particular pain points for each business unit to understand what is preventing them from achieving the desirable business outcome.

      VC Case Study

      One of the top initiatives identified by the company to improve financial performance was to reduce expense.

      Because the company has several key locations in different states, company executives used to travel extensively to carry out meetings at each location.

      Therefore, travel expenses represent a significant proportion of operational expenses and reducing travel costs is a key goal for the company’s executives.

      What do the stakeholders need to know?

      Supporting Tool icon 1.3 0.5 Hour

      What do the stakeholders need to know?

      1. Identify the key things that the stakeholders would need to know based on the goals and pain points derived from the previous step.These are your success criteria and must be met to successfully achieve the desired goals.

      VC Case Study

      The CEO needs to have assurance that without executives traveling to each location, remote meetings can be as effective as in-person meetings.

      These meetings must provide the same outcome and allow executives to collaborate and make similar strategic decisions without the onsite, physical presence.

      Therefore, the success criteria are:

      • Reduced travel costs
      • Effective collaboration
      • High-quality meetings

      What do I need to measure?

      Supporting Tool icon 1.4 1 Hour

      What does IT need to measure?

      1. Identify the IT services that are leveraged to achieve the business goals and success criteria.
      2. Identify the users of those services and determine the nature of usage for each group of users.
      3. Identify the key indicators that must be measured for those services from an IT perspective.

      VC Case Study

      The IT department decides to implement the video conferencing service to reduce the number of onsite meetings. This technology would allow executives to meet remotely with both audio and video and is the best option to replicate a physical meeting.

      The service is initially available to senior executives and will be rolled out to all internal users once the initial implementation is deemed successful.

      To determine the success of the service, the following needs to be measured:

      1. Outcomes of VC meetings
      2. Quality of the VC meetings
      3. Reduction in travel expenses

      Derive service metrics

      Supporting Tool icon 1.5 0.5 Hour

      Derive your service metrics

      1. Derive the service metrics that are meaningful to business stakeholders based on the IT services and the key indicators identified in the previous steps.
      2. Distinguish between service metrics and business metrics. You may identify some business metrics in addition to the IT metrics, and although these are important, IT doesn’t own the process of tracking and reporting business metrics.

      VC Case Study

      In the previous step, IT identified that it must measure the outcomes of VC meetings, quality of the VC meetings, and the reduction in travel expenses. From these, the appropriate service metrics can be derived to answer the needs of the CEO.

      IT needs to measure:

      1. Percent of VC meetings successfully delivered
      2. Growth of number of executive meetings conducted via VC
      Outcomes

      IT also identified the following business metrics:

      1. Reduction in percent of travel expense/spend
      2. Reduction in lost time due to travel

      Validate your metrics

      Once appropriate service metrics are derived from business objectives, the next step is to determine whether or not it is viable to actually measure the metrics.

      Can you measure it? The first question IT must answer is whether the metric is measurable. IT must identify the data source, validate its ability to collect the data, and specify the data requirement. Not all metrics can be measured!
      How will you measure it? If the metric is measurable, the next step is to create a way to measure the actual data. In most cases, simple formulas that can be easily understood are the best approach.
      Define your actions Metrics must be used to drive or reinforce desirable outcomes and behaviors. Thus, IT must predetermine the necessary actions associated with the different metric levels, thresholds, or trends.

      Determine if you can measure the identified metric

      Supporting Tool icon 1.6 0.5 Hour

      INSTRUCTIONS

      1. Determine what data sources are available. Make sure that you know where the information you need is captured, or will need to be captured. This would include:
        • A ticket/request system
        • An auto discovery tool
        • A configuration management database ( CMDB)
      2. Confirm that IT has the ability to collect the information.
        • If the necessary data is already contained in an identified data source, then you can proceed.
        • If not, consider whether it’s possible to gather the information using current sources and systems.
        • Understand the constraints and cost/ROI to implement new technology or revise processes and data gathering to produce the data.

      VC Case Study

      Using the metric derived from the video conferencing service example, IT wants to measure the % of VC meetings successfully delivered.

      What are the data sources?

      • Number of VC meetings that took place
      • Number of service incidents
      • User survey

      Determine if you can measure the identified metric

      Supporting Tool icon 1.6 0.5 Hour

      INSTRUCTIONS

      1. Understand your data requirements
        • To produce relevant metrics from your data, you need to ensure the level of quality and currency that provides you with useful information. You need to define:
          • The level of detail that has to be captured to make the data useful.
          • The consistency of the data, and how it needs to be entered or gathered.
          • The accuracy of the data. This includes how current the data needs to be, how quickly changes have to be made, and how data quality will be verified.

      VC Case Study

      Data requirement for percent of successful VC meetings:

      • Level of detail – user category, location, date/time,
      • Consistency – how efficiently are VC-related incidents opened and closed? Is the data collected and stored consistently?
      • Accuracy – is the information entered accurately?

      Create the calculation to measure it

      Supporting Tool icon 1.7 0.5 Hour

      Determine how to calculate the metrics.

      INSTRUCTIONS
      1. Develop the calculations that will be used for each accepted metric. The measurement needs to be clear and straightforward.
      2. Define the scope and assumptions for each calculation, including:
        • The defined measurement period (e.g. monthly, weekly)
        • Exclusions (e.g. nonbusiness hours, during maintenance windows)

      VC Case Study

      Metric: Percent of VC meetings delivered successfully

      IT is able to determine the total number of VC meetings that took place and the number of VC service requests to the help desk.

      That makes it possible to use the following formula to determine the success percentage of the VC service:

      ((total # VC) – (# of VC with identified incidents)) / (total # VC) * 100

      Define the actions to be taken for each metric

      Supporting Tool icon 1.7 1.5 Hour

      INSTRUCTIONS

      Centered on the defined metrics and their calculations, IT can decide on the actions that should be driven out of each metric based on one of the following scenarios:
      • Scenario 1: Ad hoc remedial action and root-cause investigation. If the reason for the result is unknown, determining root cause or identifying trends is required to determine required actions.
      • Scenario 2: Predefined remedial action. A set of predetermined actions associated with different results. This is useful when the meaning of the results is clear and points to specific issues within the environment.
      • Scenario 3: Nonremedial action. The metrics may produce a result that reinforces or supports company direction and strategy, or identifies an opportunity that may drive a new initiative or idea.

      VC Case Study

      If the success rate of the VC meetings is below 90%, IT needs to focus on determining if there is a common cause and identify if this is a consistent downward trend.

      A root-cause analysis is performed that identifies that network issues are causing difficulties, impacting the connection quality and usability of the VC service.

      Validate the confirmed metrics with the business

      Supporting Tool icon 1.8 1 Hour

      INPUT: Selected service metrics, Discussion with the business

      OUTPUT: Validated metrics with the business

      Materials: Metrics with calculation methodology

      Participants: IT and business stakeholders, Service owners

      INSTRUCTIONS

      1. Once you have derived the appropriate metrics and established that the metrics are measurable, you must go back to the targeted stakeholders and validate that the selected metrics will provide the right information to meet their identified goals and success criteria.
      2. Add confirmed metrics to the Metrics Tracking Tool, in the Metrics Tracking Plan tab.
      Service Metric Corresponding
      Business Goal
      Measurement
      Method
      Defined Actions

      Example: Measuring the online banking service at a financial institution

      Who are IT’s stakeholders? The financial institution provides various banking solutions to its customers. Retail banking is a core service offered by the bank and the VP of retail banking is a major stakeholder of IT.
      What are their goals and pain points? The VP of retail banking’s highest priorities are to increase revenue, increase market share, and maintain the bank’s brand and reputation amongst its customers.
      What do they need to know? In order to measure success, the VP of retail banking needs to determine performance in attracting new clients, retaining clients, expanding into new territory, and whether they have increased the number of services provided to existing clients.
      What does IT need to measure? The recent implementation of an online banking service is a key initiative that will keep the bank competitive and help retail banking meet its goals. The key indicators of this service are: the total number of clients, the number of products per client, percent of clients using online banking, number of clients by segment, service, territory.
      Derive the service metrics Based on the key indicators, IT can derive the following service metrics:
      1. Number of product applications originated from online banking
      2. Customer satisfaction/complaints
      As part of the process, IT also identified some business metrics, such as the number of online banking users per month or the number of times a client accesses online banking per month.

      Design service metrics to track service performance and value

      CASE STUDY
      Industry: Manufacturing | Source: CIO
      Challenge Solution Results
      The IT organization needed to generate metrics to show the business whether the video conferencing service was being adopted and if it was providing the expected outcome and value.

      Standard IT metrics were technical and did not provide a business context that allowed for easy understanding of performance and decision making.

      The IT organization, working through the CIO and service managers, sat down with the key business stakeholders of the video conferencing service.

      They discussed the goals for the meeting and defined the success criteria for those goals in the context of video conference meeting outcomes.

      The success criteria that were discussed were then translated into a set of questions (key performance indicators) that if answered, would show that the success criteria were achieved.

      The service manager identified what could be measured to answer the defined questions and eliminated any metrics that were either business metrics or non-IT related.

      The remaining metrics were identified as the possible service metrics, and the ability to gather the information and produce the metric was confirmed.

      Service metrics were defined for:

      1. Percent of video conference meetings delivered successfully
      2. Growth in the number of executive meetings conducted via video conference

      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 Valence Howden, Senior Manager, CIO Advisory, Info-Tech Research Group.
      • 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

      Sample of activity 1.1 'Determine your stakeholders'. Determine stakeholder needs, goals, and pain points

      The onsite analyst will help you select key stakeholders and analyze their business objectives and current pain points.

      1.2

      Sample of activity 1.2 'Identify goals and pain points of your stakeholders'. Determine the success criteria and related IT services

      The analyst will facilitate a discussion to uncover the information that these stakeholders care about. The group will also identify the IT services that are supporting these objectives.

      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.5

      Sample of activity 1.5 'Derive service metrics'. Derive the service metrics

      Based on the key performance indicators obtained in the previous page, derive meaningful business metrics that are relevant to the stakeholders.

      1.6

      Sample of activity 1.6 'Determine if you can measure the identified metric'. Validate the data collection process

      The analyst will help the workshop group determine whether the identified metrics can be collected and measured. If so, a calculation methodology is created.

      1.7

      Sample of activity 1.7 'Create the caluclation to measure it'. Validate metrics with stakeholders

      Establish a feedback mechanism to have business stakeholders validate the meaningfulness of the metrics.

      Develop Meaningful Service Metrics to Ensure Business and User Satisfaction

      PHASE 2

      Design Reports and Dashboards

      Step (2): Design Reports and Dashboards

      PHASE 1PHASE 2PHASE 3

      1.1

      Derive the Service Metrics

      1.2

      Validate the Metrics

      2.1

      Determine Reporting Format

      3.1

      Select Pilot Metrics

      3.2

      Activate and Maintain Metrics

      This step involves the following participants:

      • Business Relationship Manager
      • Service Level Manager
      • Business Stakeholders

      Outcomes of this step

      • Presentation format selected based on stakeholder needs and preference for information
      • Presentation format validated with stakeholders

      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: Design Reports and Dashboards

      Proposed Time to Completion (in weeks): 3 weeks
      Step 2.1: Select Presentation Format Step 2.2: Review Design
      Start with an analyst kick-off call:
      • Review the different format of metrics presentation and discuss the pros/cons of each format
      • Discuss stakeholder needs/preference for data
      • Select the presentation format
      Review findings with analyst:
      • Discuss stakeholder feedback based on selected presentation format
      • Modify and adjust the presentation format as needed
      Then complete these activities…
      • Design the metrics using the selected format
      Then complete these activities…
      • Finalize the design for metrics presentation
      With these tools & templates:
      • Metrics Presentation Format Selection Guide
      With these tools & templates:
      • Metrics Presentation Format Selection Guide

      Design the reports – overview

      Figure representing 'SLM' and/or 'BRM'. Step 1
      Understand the pros and cons of different reporting styles
      Figure representing 'SLM' and/or 'BRM'. Step 2
      Determine your reporting and presentation style

      Presentation Format Selection

      Figure representing 'SLM' and/or 'BRM'. Step 3
      Design your metrics reports
      A star.

      Validated Service Reports

      The design of service metrics reporting is critically important. The reporting style must present the right information in the most interesting and stakeholder-centric way possible to ensure that it is read and used.

      The reports must also display information in a way that generates actions. If your stakeholders cannot make decisions, kick off activities, or ask questions based on your reports, then they have no value.

      Determine the right presentation format for your metrics

      Most often, metrics are presented in the following ways:

      Dashboard
      (PwC. “Mega-Trends and Implications.”)
      Sample of the 'Dashboard' metric presentation format.
      Infographic
      (PwC. “Healthcare’s new entrants.”)
      Sample of the 'Infographic' metric presentation format.
      Report
      (PwC Blogs. “Northern Lights.”)
      Sample of the 'Report' metric presentation format.
      Scorecard
      (PwC. “Annual Report 2015.”)
      Sample of the 'Scorecard' metric presentation format.

      Understand the advantages and disadvantages of each reporting style – Dashboard

      A dashboard is a reporting method that provides a dynamic at-a-glance view of key metrics from the perspective of key stakeholders. It provides a quick graphical way to process important performance information in real time.

      Features

      Typically web-based

      Dynamic data that is updated in real time

      Advantage

      Aggregates a lot of information into a single view

      Presents metrics in a simplistic style that is well understood

      Provides a quick point-in-time view of performance

      Easy to consume visual presentation style

      Disadvantage

      Complicated to set up well.
      Requires additional technology support: programming, API, etc.

      Promotes a short-term outlook – focus on now, no historical performance and no future trends. Doesn’t provide the whole picture and story.

      Existing dashboard tools are often not customized enough to provide real value to each stakeholder.

      Dashboards present real-time metrics that can be accessed and viewed at any time

      Sample of the 'Dashboard' metric presentation format.
      (Source: PwC. “Mega-Trends and Implications.”)
      Metrics presented through online dashboards are calculated in real time, which allows for a dynamic, current view into the performance of IT services at any time.

      Understand the advantages and disadvantages of each reporting style – Infographic

      An infographic is a graphical representation of metrics or data, which is used to show information quickly and clearly. It’s based on the understanding that people retain and process visual information more readily than written details.

      Features

      Turns dry into attractive –transforms data into eye-catching visual memory that is easier to retain

      Can be used as the intro to a formal report

      There are endless types of infographics

      Advantage

      Easily consumable

      Easy to retain

      Eye catching

      Easily shared

      Spurs conversation

      Customizable

      Disadvantage

      Require design expertise and resources

      Can be time consuming to generate

      Could be easily misinterpreted

      Message can be lost with poor design

      Infographics allow for completely unique designs

      Sample of the 'Infographic' metric presentation format.
      (Source: PwC. “Healthcare’s new entrants…”)
      There is no limit when it comes to designing an infographic. The image used here visually articulates the effects of new entrants pulling away the market.

      Understand the advantages and disadvantages of each reporting style – Formal Report

      A formal report is a more structured and official reporting style that contains detailed research, data, and information required to enable specific business decisions, and to help evaluate performance over a defined period of time.

      Definition

      Metrics can be presented as a component of a periodic, formal report

      A physical document that presents detailed information to a particular audience

      Advantage

      More detailed, more structured and broader reporting period

      Formal, shows IT has put in the effort

      Effectively presents a broader and more complete story

      Targets different stakeholders at the same time

      Disadvantage

      Requires significant effort and resources

      Higher risk if the report does not meet the expectation of the business stakeholder

      Done at a specific time and only valuable for that specific time period

      Harder to change format

      Formal reports provide a detailed view and analysis of performance

      Sample of the 'Formal Report' metric presentation format.
      (Source: PwC Blogs. “Northern Lights: Where are we now?”)
      An effective report incorporates visuals to demonstrate key improvements.

      Formal reports can still contain visuals, but they are accompanied with detailed explanations.

      Understand the advantages and disadvantages of each reporting style – Scorecard

      A scorecard is a graphic view of the progress and performance over time of key performance metrics. These are in relation to specified goals based on identified critical stakeholder objectives.

      Features

      Incorporates multiple metrics effectively.

      Scores services against the most important organizational goals and objectives. Scorecards may tie back into strategy and different perspectives of success.

      Advantage

      Quick view of performance against objectives

      Measure against a set of consistent objectives

      Easily consumable

      Easy to retain

      Disadvantage

      Requires a lot of forethought

      Scorecards provide a time-bound summary of performance against defined goals

      Sample of the 'Scorecard' metric presentation format.
      (PwC. “Annual Report 2015.”)
      Scorecards provide a summary of performance that is directly linked to the organizational KPIs.

      Determine your report style

      Supporting Tool icon 2.1 Metrics Presentation Format Selection Guide

      In this section, you will determine the optimal reporting style for the service metrics.

      This guide contains four questions, which will help IT organizations identify the most appropriate presentation format based on stakeholder preference and needs for metrics.

      1. Who is the relevant stakeholder?
      2. What are the defined actions for the metric?
      3. How frequently does the stakeholder need to see the metric?
      4. How does the stakeholder like to receive information?
      Sample of Info-Tech's Metrics Presentation Format Selection Guide.
      Download the Metrics Presentation Format Selection Guide.

      Determine your best presentation option

      Supporting Tool icon 2.1 2 Hours

      INPUT: Identified stakeholder and his/her role

      OUTPUT: Proper presentation format based on need for information

      Materials: Metrics Presentation Format Selection Guide

      Participants: BRM, SLM, Program Manager

      After deciding on the report type to be used to present the metric, the organization needs to consider how stakeholders will consume the metric.

      There are three options based on stakeholder needs and available presentation options within IT.

      1. Paper-based presentation is the most traditional form of reporting and works well with stakeholders who prefer physical copies. The report is produced at a specific time and requires no additional IT capability.
      2. Online documents stored on webpages, SharePoint, or another knowledge management system could be used to present the metrics. This allows the report to be linked to other information and easily shared.
      3. Online dashboards and graphics can be used to have dynamic, real-time reporting and anytime access. These webpages can be incorporated into an intranet and allow the user to view the metrics at any time. This will require IT to continuously update the data in order to maintain the accuracy of the metrics.

      Design your metric reports with these guidelines in mind

      Supporting Tool icon 2.2 30 Minutes
      1. Stakeholder-specificThe report must be driven by the identified stakeholder needs and preferences and articulate the metrics that are important to them.
      2. ClarityTo enable decision making and drive desired actions, the metrics must be clear and straightforward. They must be presented in a way that clearly links the performance measurement to the defined outcome without leading to different interpretations of the results.
      3. SimplicityThe report must be simple to read, understand, and analyze. The language of the report must be business-centric and remove as much complexity as possible in wording, imaging, and context.

      Be sure to consider access rights for more senior reports. Site and user access permissions may need to be defined based on the level of reporting.

      Metrics reporting on the video conferencing service

      CASE STUDY
      Industry: Manufacturing | Source: CIO Interview
      The Situation

      The business had a clear need to understand if the implementation of video conferencing would allow previously onsite meetings to achieve the same level of effectiveness.

      Reporting Context

      Provided reports had always been generated from an IT perspective and the business rarely used the information to make decisions.

      The metrics needed to help the business understand if the meetings were remaining effective and be tied into the financial reporting against travel expenses, but there would be limited visibility during the executive meetings.

      Approach

      The service manager reviewed the information that he had gathered to confirm how often they needed information related to the service. He also met with the CIO to get some insight into the reports that were already being provided to the business, including the ones that were most effective.

      Considerations

      The conversations identified that there was no need for a dynamic real-time view of the performance of the service, since tracking of cost savings and utility would be viewed monthly and quarterly. They also identified that the item would be discussed within a very small window of time during the management meetings.

      The Solution

      It was determined that the best style of reporting for the metric was an existing scorecard that was produced monthly, using some infographics to ensure that the information is clear at a glance to enable quick decision making.

      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 Valence Howden, Senior Manager, CIO Advisory, Info-Tech Research Group.
      • 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:

      2.1

      Sample of presentation format option slide 'Determine the right presentation format for your metrics'. Understand the different presentation options

      The onsite analyst will introduce the group to the communication vehicles of infographic, scorecard, formal report, and dashboard.

      2.1

      Sample of activity 2.1 'Determine your best presentation option'. Assess stakeholder needs for information

      For selected stakeholders, the analyst will facilitate a discussion on how stakeholders would like to view information and how the metrics can be presented to aid decision making.

      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:

      2.2

      Sample of activity 2.2 'Design your metric reports with these guidelines in mind'. Select and design the metric report

      Based on the discussion, the working group will select the most appropriate presentation format and create a rough draft of how the report should look.

      Develop Meaningful Service Metrics to Ensure Business and User Satisfaction

      PHASE 3

      Implement, Track, and Maintain Your Metrics

      Step (3): Implement, Track, and Maintain Your Metrics

      PHASE 1PHASE 2PHASE 3

      1.1

      Derive the Service Metrics

      1.2

      Validate the Metrics

      2.1

      Determine Reporting Format

      3.1

      Select Pilot Metrics

      3.2

      Activate and Maintain Metrics

      This step involves the following participants:

      • Service Level Manager
      • Business Relationship Manager
      • Service Metrics Program Manager

      Activities in this step

      • Determine the first batch of metrics to be implemented as part of the pilot program
      • Create a process to collect and validate data, determine initial targets, and integrate with SLM and BRM functions
      • Present the metric reports to the relevant stakeholders and incorporate the feedback into the metric design
      • Establish a standard process and roll out the implementation of metrics in batches
      • Establish a process to monitor and track the effectiveness of the service metrics program and make adjustments when necessary

      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: Implement, Track, and Maintain Your Metrics

      Proposed Time to Completion (in weeks): 4 weeks
      Step 3.1: Select and Launch Pilot Metrics Step 3.2: Track and Maintain the Metrics
      Start with an analyst kick-off call:
      • Identify metrics that will be presented first to the stakeholders based on urgency or impact of the IT service
      • Determine the process to collect data, select initial targets, and integrate with SLM and BRM functions
      Review findings with analyst:
      • Review the success of metrics and discuss feedback from stakeholders
      • Roll out the metrics implementation to a broader audience
      • Establish roles and timelines for metrics maintenance
      Then complete these activities…
      • Document the first batch of metrics
      • Document the baseline, initial targets
      • Create a plan to integrate with SLM and BRM functions
      Then complete these activities…
      • Create a document that defines how the organization will track and maintain the success of the metrics program
      • Review the metrics program periodically
      With these tools & templates:
      • Metrics Tracking Tool
      With these tools & templates:
      • Metrics Tracking Tool

      Implement, Track, and Maintain the Metrics

      Figure representing 'SLM' and/or 'BRM'. Step 1
      Run your pilot

      Metrics Tracking Tool

      Figure representing 'SLM' and/or 'BRM'. Step 2
      Validate success

      Metrics Tracking Tool

      Figure representing 'SLM' and/or 'BRM'. Step 3
      Implement your metrics program in batches

      Metrics Tracking Tool

      A star.

      Active Service Metrics Program

      Once you have defined the way that you will present the metrics, you are ready to run a pilot with a smaller sample of defined service metrics.

      This allows you to validate your approach and make refinements to the implementation and maintenance processes where necessary, prior to activating all service metrics.

      Track the performance of your service metrics

      Supporting Tool icon 3.1

      The Metrics Tracking Tool will enable you to track goals and success metrics for your service metrics programs. It allows you to set long-term goals and track your results over time.

      There are three sections in this tool:
      1. Metrics Tracking Plan. Identify the metrics to be tracked and their purpose.
      2. Metrics Tracking Actuals. Monitor and track the actual performance of the metrics.
      3. Remediation Tracking. Determine and document the steps that need to be taken to correct a sub-performing metric.
      Sample of Info-Tech's Metrics Tracking Tool.

      Select pilot metrics

      Supporting Tool icon 3.1 30 Minutes

      INPUT: Identified services, Business feedback

      OUTPUT: Services with most urgent need or impact

      Materials: Service catalog or list of identified services

      Participants: BRM, SLM, Business representatives

      To start the implementation of your service metrics program and drive wider adoption, you need to run a pilot using a smaller subset of metrics.

      INSTRUCTIONS

      To determine the sample for the pilot, consider metrics that:

      • Are related to critical business services and functions
      • or
      • Address known/visible pain points for the business
      • or
      • Were designed for supportive or influential stakeholders

      Metrics that meet two or more criteria are ideal for the pilot

      Collect and validate data

      Supporting Tool icon 3.2 1 Hour

      INPUT: Identified metrics

      OUTPUT: A data collection mythology, Metrics tracking

      Materials: Metrics

      Participants: SLM, BRM, Service owner

      You will need to start collection and validation of your identified data in order to calculate the results for your pilot metrics.

      INSTRUCTIONS

      1. Initiate data collection
        • Use the data sources identified during the design phase and initiate the data collection process.
      2. Determine start date
        • If historical data can be retrieved and gathered, determine how far back you want your measurements to start.
      3. Compile data and validate
        • Ensure that the information is accurate and up to date. This will require some level of data validation and audit.
      4. Run the metric
        • Use the defined calculation and source data to generate the metrics result.
      5. Record metrics results
        • Use the metrics tracking sheet to track the actual results.

      Determine initial targets

      Supporting Tool icon 3.3 1 Hour

      INPUT: Historical data/baseline data

      OUTPUT: Realistic initial target for improvement

      Materials: Metrics Tracking Tool

      Participants: BRM, SLM, Service owner

      INSTRUCTIONS

      Identify an initial service objective based on one or more of the following options:

      1. Establish an initial target using historical data and trends of performance.
      2. Establish an initial target based on stakeholder-identified requirements and expectations.
      3. Run the metrics report over a defined period of time and use the baseline level of achievement to establish an initial target.

      The target may not always be a number - it could be a trend. The initial target will be changed after review with stakeholders

      Integrate with SLM and BRM processes

      Supporting Tool icon 3.4 1 Hour

      INPUT: SLM and BRM SOPs or responsibility documentations

      OUTPUT: Integrate service metrics into the SLM/BRM role

      Materials: SLM / BRM reports

      Participants: SLM, BRM, CIO, Program manager, Service manager

      The service metrics program is usually initiated, used, and maintained by the SLM and BRM functions.

      INSTRUCTIONS

      Ensure that the metrics pilot is integrated with those functions by:

      1. Engaging with SLM and BRM functions/resources
        • Identify SLM and BRM resources associated with or working on the services where the metrics are being piloted
        • Obtain their feedback on the metrics/reporting
      2. Integrating with the existing reporting and meeting cycles
        • Ensure the metrics will be calculated and available for discussion at standing meetings and with existing reports
      3. Establishing the metrics review and validation cycle for these metrics
        • Confirm the review and validation period for the metrics in order to ensure they remain valuable and actionable

      Generate reports and present to stakeholders

      Supporting Tool icon 3.5 1 Hour

      INPUT: Identified metrics, Selected presentation format

      OUTPUT: Metrics reports that are ready for distribution

      Materials: Metrics Presentation Format Selection Guide

      Participants: BRM, SLM, CIO, Business representatives

      INSTRUCTIONS

      Once you have completed the calculation for the pilot metrics:

      1. Confirm the report style for the selected metrics (as defined in Phase 2)
      2. Generate the reporting for the pilot metrics
      3. Present the pilot metric reports to the identified BRM and SLM resources who will present the reporting to the stakeholders
      4. Gather feedback from Stakeholders on metrics - results and process
      5. Create and execute remediation plans for any actions identified from the metrics
      6. Initiate the review cycle for metrics (to ensure they retain value)

      Plan the rollout and implementation of the metrics reporting program

      Supporting Tool icon 3.6 1 Hour

      INPUT: Feedback from pilot, Services in batch

      OUTPUT: Systematic implementation of metrics

      Materials: Metrics Tracking Tool

      Participants: BRM, SLM, Program manager

      Upon completion of the pilot, move to start the broader implementation of metrics across the organization:

      INSTRUCTIONS

      1. Identify the service metrics that you will implement. They can be selected based on multiple criteria, including:
        • Organizational area/business unit
        • Service criticality
        • Pain points
        • Stakeholder engagement (detractors, supporters)
      2. Create a rollout plan for implementation in batches, identifying expected launch timelines, owners, targeted stakeholders, and communications plans
      3. Use the implementation plan from the pilot to roll out each batch of service metrics:
        • Collect and validate data
        • Determine target(s)
        • Integrate with BRM and SLM
        • Generate and communicate reports to stakeholders

      Maintain the service metrics

      Supporting Tool icon 3.7 1.5 Hour

      INPUT: Feedback from business stakeholders

      OUTPUT: Modification to individual metrics or to the process

      Materials: Metrics Tracking Tool, Metrics Development Workbook

      Participants: CIO, BRM, SLM, Program manager, Service owner

      Once service metrics and reporting become active, it is necessary to determine the review time frame for your metrics to ensure they remain useful.

      INSTRUCTIONS

      1. Confirm and establish a review time frame with stakeholders (e.g. annually, bi-annually, after organizational or strategic changes).
      2. Meet with stakeholders by the review date to discuss the value of existing metrics and validate:
        • Whether the goals associated with the metrics are still valid
        • If the metric is still necessary
        • If there is a more effective way to present the metrics
      3. Track actions based on review outcomes and update the remediation tracking sheet.
      4. Update tracking sheet with last complete review date.

      Maintain the metrics

      Supporting Tool icon 3.7

      Based on the outcome of the review meeting, decide what needs to be done for each metric, using the following options:

      Add

      A new metric is required or an existing metric needs large-scale changes (example: calculation method or scope).
      Triggers metrics design as shown in phases 1 and 2.

      Change

      A minor change is required to the presentation format or data. Note: a major change in a metric would be performed through the Add option.

      Remove

      The metric is no longer required, and it needs to be removed from reporting and data gathering. A final report date for that metric should be determined.

      Maintain

      The metric is still useful and no changes are required to the metric, its measurement, or how it’s reported.

      Ensuring metrics remain valuable

      VC CASE STUDY
      Industry: Manufacturing | Source: CIO Interview

      Reviewing the value of active metrics

      When the video conferencing service was initially implemented, it was performed as a pilot with a group of executives, and then expanded for use throughout the company. It was understood that prior to seeing the full benefit in cost reduction and increased efficiency and effectiveness, the rate of use and adoption had to be understood.

      The primary service metrics created for the service were based on tracking the number of requests for video conference meetings that were received by the IT organization. This identified the growth in use and could be used in conjunction with financial metrics related to travel to help identify the impact of the service through its growth phase.

      Once the service was adopted, this metric continued to be tracked but no longer showed growth or expanded adoption.

      The service manager was no longer sure this needed to be tracked.

      Key Activity

      The metrics around requests for video conference meetings were reviewed at the annual metrics review meeting with the business. The service manager asked if the need for the metric, the goal of tracking adoption, was still important for the business.

      The discussion identified that the adoption rate was over 80%, higher than anticipated, and that there was no value in continuing to track this metric.

      Based on the discussion, the adoption metrics were discontinued and removed from data gathering and reporting, while a success rate metric was added (how many meetings ran successfully and without issue) to ensure the ongoing value of the video conferencing service.

      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 Valence Howden, Senior Manager, CIO Advisory, Info-Tech Research Group.
      • 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

      Sample of activity 3.1 'Select pilot metrics'. Select the pilot metrics

      The onsite analyst will help the workshop group select the metrics that should be first implemented based on the urgency and impact of these metrics.

      3.2

      Sample of activity 3.2 'Collect and validate data'. Gather data and set initial targets

      The analyst will help the group create a process to gather data, measure baselines, and set initial targets.

      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.5

      Sample of activity 3.5 'Generate reports and present to stakeholders'. Generate the reports and validate with stakeholders

      The Info-Tech analyst will help the group establish a process to receive feedback from the business stakeholders once the report is generated.

      3.6

      Sample of activity 3.6 'Plan the rollout and implementation of the metrics reporting program'. Implement the service metrics program

      The analyst will facilitate a discussion on how to implement the metrics program across the organization.

      3.7

      Sample of activity 3.7 'Maintain the service metrics'. Track and maintain the metrics program

      Set up a mechanism to ensure the success of the metrics program by assessing process adherence and process validity.

      Insight breakdown

      Insight 1

      Service metrics are critical to ensuring alignment of IT service performance and business service value achievement.

      Insight 2

      Service metrics reinforce positive business and end-user relationships by providing user-centric information that drives responsiveness and consistent service improvement.

      Insight 3

      Poorly designed metrics drive unintended and unproductive behaviors that have negative impacts on IT and produce negative service outcomes.

      Summary of accomplishment

      Knowledge Gained

      • Follow a methodology to identify metrics that are derived from business objectives.
      • Understand the proper presentation format based on stakeholder needs for information.
      • Establish a process to ensure the metrics provided will continue to provide value and aid decision making.

      Processes Optimized

      • Metrics presentation to business stakeholders
      • Metrics maintenance and tracking

      Deliverables Completed

      • Metrics Development Workbook
      • Metrics Presentation Format Selection Guide
      • Metrics Tracking Tool

      Research contributors and experts

      Name Organization
      Joe Evers Joe Evers Consulting
      Glen Notman Associate Partner, Citihub
      David Parker Client Program Manager, eHealth Ontario
      Marianne Doran Collins CIO, The CIO-Suite, LLC
      Chris Kalbfleisch Manager, Service Management, eHealth Ontario
      Joshua Klingenberg BHP Billiton Canada Inc.

      Related Info-Tech research

      Stock image of a menu. Design & Build a User-Facing Service Catalog
      The user-facing service catalog is the go-to place for IT service-related information.
      Stock image of a laptop keyboard. Unleash the True Value of IT by Transforming Into a Service Provider
      Earn your seat at the table and influence business strategy by becoming an IT service provider.

      Bibliography

      Pollock, Bill. “Service Benchmarking and Measurement: Using Metrics to Drive Customer Satisfaction and Profits.” Aberdeen Group. June 2009. http://722consulting.com/ServiceBenchmarkingandMeasurement.pdf

      PwC. “Mega-Trends and Implications.” RMI Discussion. LinkedIn SlideShare. September 2015. http://www.slideshare.net/AnandRaoPwC/mega-trends-and-implications-to-retirement

      PwC. “Healthcare’s new entrants: Who will be the industry’s Amazon.com?” Health Research Institute. April 2014. https://www.pwc.com/us/en/health-industries/healthcare-new-entrants/assets/pwc-hri-new-entrant-chart-pack-v3.pdf

      PwC. “Northern Lights: Where are we now?” PwC Blogs. 2012. http://pwc.blogs.com/files/12.09.06---northern-lights-2--summary.pdf

      PwC. “PwC’s key performance indicators

      Build a Data Classification MVP for M365

      • Buy Link or Shortcode: {j2store}67|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: End-User Computing Applications
      • Parent Category Link: /end-user-computing-applications
      • Resources are the primary obstacle to getting a foot hold in O365 governance, whether it is funding or FTE resources.
      • Data is segmented and is difficult to analyze when you can’t see it or manage the relationships between sources.
      • Organizations expect results early and quickly and a common obstacle is that building a proper data classification framework can take more than two years and the business can't wait that long.

      Our Advice

      Critical Insight

      • Data classification is the lynchpin to ANY effective governance of O/M365 and your objective is to navigate through this easily and effectively and build a robust, secure, and viable governance model.
      • Start your journey by identifying what and where your data is and how much data you have. You need to understand what sensitive data you have and where it is stored before you can protect it or govern that data.
      • Ensure there is a high-level leader who is the champion of the governance objective.

      Impact and Result

      • Using least complex sensitivity labels in your classification are your building blocks to compliance and security in your data management schema; they are your foundational steps.

      Build a Data Classification MVP for M365 Research & Tools

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

      1. Build a Data Classification MVP for M365 Deck – A guide for how to build a minimum-viable product for data classification that end users will actually use.

      Discover where your data resides, what governance helps you do, and what types of data you're classifying. Then build your data and security protection baselines for your retention policy, sensitivity labels, workload containers, and both forced and unforced policies.

      • Build a Data Classification MVP for M365 Storyboard
      [infographic]

      Further reading

      Build a Data Classification MVP for M365

      Kickstart your governance with data classification users will actually use!

      Executive Summary

      Info-Tech Insight

      • Creating an MVP gets you started in data governance
        Information protection and governance are not something you do once and then you are done. It is a constant process where you start with the basics (a minimum-viable product or MVP) and enhance your schema over time. The objective of the MVP is reducing obstacles to establishing an initial governance position, and then enabling rapid development of the solution to address a variety of real risks, including data loss prevention (DLP), data retention, legal holds, and data labeling.
      • Define your information and protection strategy
        The initial strategy is to start looking across your organization and identifying your customer data, regulatory data, and sensitive information. To have a successful data protection strategy you will include lifecycle management, risk management, data protection policies, and DLP. All key stakeholders need to be kept in the loop. Ensure you keep track of all available data and conduct a risk analysis early. Remember, data is your highest valued intangible asset.
      • Planning and resourcing are central to getting started on MVP
        A governance plan and governance decisions are your initial focus. Create a team of stakeholders that include IT and business leaders (including Legal, Finance, HR, and Risk), and ensure there is a top-level leader who is the champion of the governance objective, which is to ensure your data is safe, secure, and not prone to leakage or theft, and maintain confidentiality where it is warranted.

      Executive Summary

      Your Challenge
      • Today, the amount of data companies are gathering is growing at an explosive rate. New tools are enabling unforeseen channels and ways of collaborating.
      • Combined with increased regulatory oversight and reporting obligations, this makes the discovery and management of data a massive undertaking. IT can’t find and protect the data when the business has difficulty defining its data.
      • The challenge is to build a framework that can easily categorize and classify data yet allows for sufficient regulatory compliance and granularity to be useful. Also, to do it now because tomorrow is too late.
      Common Obstacles

      Data governance has several obstacles that impact a successful launch, especially if governing M365 is not a planned strategy. Below are some of the more common obstacles:

      • Resources are the primary obstacle to starting O365 governance, whether it is funding or people.
      • Data is segmented and is difficult to analyze when you can’t see it or manage the relationships between sources.
      • Organizations expect results early and quickly and a common obstacle is that building a "proper data classification framework” is a 2+ year project and the business can't wait that long.
      Info-Tech’s Approach
      • Start with the basics: build a minimum-viable product (MVP) to get started on the path to sustainable governance.
      • Identify what and where your data resides, how much data you have, and understand what sensitive data needs to be protected.
      • Create your team of stakeholders, including Legal, records managers, and privacy officers. Remember, they own the data and should manage it.
      • Categorization comes before classification, and discovery comes before categorization. Use easy-to-understand terms like high, medium, or low risk.

      Info-Tech Insight

      Data classification is the lynchpin to any effective governance of O/M365 and your objective is to navigate through this easily and effectively and build a robust, secure, and viable governance model. Start your journey by identifying what and where your data is and how much data do you have. You need to understand what sensitive data you have and where it is stored before you can protect or govern it. Ensure there is a high-level leader who is the champion of the governance objectives. Data classification fulfills the governance objectives of risk mitigation, governance and compliance, efficiency and optimization, and analytics.

      Questions you need to ask

      Four key questions to kick off your MVP.

      1

      Know Your Data

      Do you know where your critical and sensitive data resides and what is being done with it?

      Trying to understand where your information is can be a significant project.

      2

      Protect Your Data

      Do you have control of your data as it traverses across the organization and externally to partners?

      You want to protect information wherever it goes through encryption, etc.

      3

      Prevent Data Loss

      Are you able to detect unsafe activities that prevent sharing of sensitive information?

      Data loss prevention (DLP) is the practice of detecting and preventing data breaches, exfiltration, or unwanted destruction of sensitive data.

      4

      Govern Your Data

      Are you using multiple solutions (or any) to classify, label, and protect sensitive data?

      Many organizations use more than one solution to protect and govern their data, making it difficult to determine if there are any coverage gaps.

      Classification tiers

      Build your schema.

      Pyramid visualization for classification tiers. The top represents 'Simplicity', and the bottom 'Complexity' with the length of the sides at each level representing the '# of policies' and '# of labels'. At the top level is 'MVP (Minimum-Viable Product) - Confidential, Internal (Subcategory: Personal), Public'. At the middle level is 'Regulated - Highly Confidential, Confidential, Sensitive, General, Internal, Restricted, Personal, Sub-Private, Public'. And a the bottom level is 'Government (DOD) - Top Secret (TS), Secret, Confidential, Restricted, Official, Unclassified, Clearance'

      Info-Tech Insight

      Deciding on how granular you go into data classification will chiefly be governed by what industry you are in and your regulatory obligations – the more highly regulated your industry, the more classification levels you will be mandated to enforce. The more complexity you introduce into your organization, the more operational overhead both in cost and resources you will have to endure and build.

      Microsoft MIP Topology

      Microsoft Information Protection (MIP), which is Microsoft’s Data Classification Services, is the key to achieving your governance goals. Without an MVP, data classification will be overwhelming; simplifying is the first step in achieving governance.

      A diagram of multiple offerings all connected to 'MIP Data Classification Service'. Circled is 'Sensitivity Labels' with an arrow pointing back to 'MIP' at the center.
      (Source: Microsoft, “Microsoft Purview compliance portal”)

      Info-Tech Insight

      Using least-complex sensitivity labels in your classification are your building blocks to compliance and security in your data management schema; they are your foundational steps.

      MVP RACI Chart

      Data governance is a "takes a whole village" kind of effort.

      Clarify who is expected to do what with a RACI chart.

      End User M365 Administrator Security/ Compliance Data Owner
      Define classification divisions R A
      Appy classification label to data – at point of creation A R
      Apply classification label to data – legacy items R A
      Map classification divisions to relevant policies R A
      Define governance objectives R A
      Backup R A
      Retention R A
      Establish minimum baseline A R

      What and where your data resides

      Data types that require classification.

      Logos for 'Microsoft', 'Office 365', and icons for each program included in that package.
      M365 Workload Containers
      Icon for MS Exchange. Icon for MS SharePoint.Icon for MS Teams. Icon for MS OneDrive. Icon for MS Project Online.
      Email
      • Attachments
      Site Collections, Sites Sites Project Databases
      Contacts Teams and Group Site Collections, Sites Libraries and Lists Sites
      Metadata Libraries and Lists Documents
      • Versions
      Libraries and Lists
      Teams Conversations Documents
      • Versions
      Metadata Documents
      • Versions
      Teams Chats Metadata Permissions
      • Internal Sharing
      • External Sharing
      Metadata
      Permissions
      • Internal Sharing
      • External Sharing
      Files Shared via Teams Chats Permissions
      • Internal Sharing
      • External Sharing

      Info-Tech Insight

      Knowing where your data resides will ensure you do not miss any applicable data that needs to be classified. These are examples of the workload containers; you may have others.

      Discover and classify on- premises files using AIP

      AIP helps you manage sensitive data prior to migrating to Office 365:
      • Use discover mode to identify and report on files containing sensitive data.
      • Use enforce mode to automatically classify, label, and protect files with sensitive data.
      Can be configured to scan:
      • SMB files
      • SharePoint Server 2016, 2013
      Stock image of a laptop uploading to the cloud with a padlock and key in front of it.
      • Map your network and find over-exposed file shares.
      • Protect files using MIP encryption.
      • Inspect the content in file repositories and discover sensitive information.
      • Classify and label file per MIP policy.
      Azure Information Protection scanner helps discover, classify, label, and protect sensitive information in on-premises file servers. You can run the scanner and get immediate insight into risks with on-premises data. Discover mode helps you identify and report on files containing sensitive data (Microsoft Inside Track and CIAOPS, 2022). Enforce mode automatically classifies, labels, and protects files with sensitive data.

      Info-Tech Insight

      Any asset deployed to the cloud must have approved data classification. Enforcing this policy is a must to control your data.

      Understanding governance

      Microsoft Information Governance

      Information Governance
      • Retention policies for workloads
      • Inactive and archive mailboxes

      Arrow pointing down-right

      Records Management
      • Retention labels for items
      • Disposition review

      Arrow pointing down-left

      Retention and Deletion

      ‹——— Connectors for Third-Party Data ———›

      Information governance manages your content lifecycle using solutions to import, store, and classify business-critical data so you can keep what you need and delete what you do not. Backup should not be used as a retention methodology since information governance is managed as a “living entity” and backup is a stored information block that is “suspended in time.” Records management uses intelligent classification to automate and simplify the retention schedule for regulatory, legal, and business-critical records in your organization. It is for that discrete set of content that needs to be immutable.
      (Source: Microsoft, “Microsoft Purview compliance portal”)

      Retention and backup policy decision

      Retention is not backup.

      Info-Tech Insight

      Retention is not backup. Retention means something different: “the content must be available for discovery and legal document production while being able to defend its provenance, chain of custody, and its deletion or destruction” (AvePoint Blog, 2021).

      Microsoft Responsibility (Microsoft Protection) Weeks to Months Customer Responsibility (DLP, Backup, Retention Policy) Months to Years
      Loss of service due to natural disaster or data center outage Loss of data due to departing employees or deactivated accounts
      Loss of service due to hardware or infrastructure failure Loss of data due to malicious insiders or hackers deleting content
      Short-term (30 days) user error with recycle bin/ version history (including OneDrive “File Restore”) Loss of data due to malware or ransomware
      Short-term (14 days) administrative error with soft- delete for groups, mailboxes, or service-led rollback Recovery from prolonged outages
      Long-term accidental deletion coverage with selective rollback

      Understand retention policy

      What are retention policies used for? Why you need them as part of your MVP?

      Do not confuse retention labels and policies with backup.

      Remember: “retention [policies are] auto-applied whereas retention label policies are only applied if the content is tagged with the associated retention label” (AvePoint Blog, 2021).

      E-discovery tool retention policies are not turned on automatically.

      Retention policies are not a backup tool – when you activate this feature you are unable to delete anyone.

      “Data retention policy tools enable a business to:

      • “Decide proactively whether to retain content, delete content, or retain and then delete the content when needed.
      • “Apply a policy to all content or just content meeting certain conditions, such as items with specific keywords or specific types of sensitive information.
      • “Apply a single policy to the entire organization or specific locations or users.
      • “Maintain discoverability of content for lawyers and auditors, while protecting it from change or access by other users. […] ‘Retention Policies’ are different than ‘Retention Label Policies’ – they do the same thing – but a retention policy is auto-applied, whereas retention label policies are only applied if the content is tagged with the associated retention label.

      “It is also important to remember that ‘Retention Label Policies’ do not move a copy of the content to the ‘Preservation Holds’ folder until the content under policy is changed next.” (Source: AvePoint Blog, 2021)

      Definitions

      Data classification is a focused term used in the fields of cybersecurity and information governance to describe the process of identifying, categorizing, and protecting content according to its sensitivity or impact level. In its most basic form, data classification is a means of protecting your data from unauthorized disclosure, alteration, or destruction based on how sensitive or impactful it is.

      Once data is classified, you can then create policies; sensitive data types, trainable classifiers, and sensitivity labels function as inputs to policies. Policies define behaviors, like if there will be a default label, if labeling is mandatory, what locations the label will be applied to, and under what conditions. A policy is created when you configure Microsoft 365 to publish or automatically apply sensitive information types, trainable classifiers, or labels.

      Sensitivity label policies show one or more labels to Office apps (like Outlook and Word), SharePoint sites, and Office 365 groups. Once published, users can apply the labels to protect their content.

      Data loss prevention (DLP) policies help identify and protect your organization's sensitive info (Microsoft Docs, April 2022). For example, you can set up policies to help make sure information in email and documents is not shared with the wrong people. DLP policies can use sensitive information types and retention labels to identify content containing information that might need protection.

      Retention policies and retention label policies help you keep what you want and get rid of what you do not. They also play a significant role in records management.

      Data examples for MVP classification

      • Examples of the type of data you consider to be Confidential, Internal, or Public.
      • This will help you determine what to classify and where it is.
      Internal Personal, Employment, and Job Performance Data
      • Social Security Number
      • Date of birth
      • Marital status
      • Job application data
      • Mailing address
      • Resume
      • Background checks
      • Interview notes
      • Employment contract
      • Pay rate
      • Bonuses
      • Benefits
      • Performance reviews
      • Disciplinary notes or warnings
      Confidential Information
      • Business and marketing plans
      • Company initiatives
      • Customer information and lists
      • Information relating to intellectual property
      • Invention or patent
      • Research data
      • Passwords and IT-related information
      • Information received from third parties
      • Company financial account information
      • Social Security Number
      • Payroll and personnel records
      • Health information
      • Self-restricted personal data
      • Credit card information
      Internal Data
      • Sales data
      • Website data
      • Customer information
      • Job application data
      • Financial data
      • Marketing data
      • Resource data
      Public Data
      • Press releases
      • Job descriptions
      • Marketing material intended for general public
      • Research publications

      New container sensitivity labels (MIP)

      New container sensitivity labels

      Public Private
      Privacy
      1. Membership to group is open; anyone can join
      2. “Everyone except external guest” ACL onsite; content available in search to all tenants
      1. Only owner can add members
      2. No access beyond the group membership until someone shares it or changes permissions
      Allowed Not Allowed
      External guest policy
      1. Membership to group is open; anyone can join
      2. “Everyone except external guest” ACL onsite; content available in search to all tenants
      1. Only owner can add members
      2. No access beyond the group membership until someone shares it or changes permissions

      What users will see when they create or label a Team/Group/Site

      Table of what users will see when they create or label a team/group/site highlighting 'External guest policy' and 'Privacy policy options' as referenced above.
      (Source: Microsoft, “Microsoft Purview compliance portal”)

      Info-Tech Insights

      Why you need sensitivity container labels:
      • Manage privacy of Teams Sites and M365 Groups
      • Manage external user access to SPO sites and teams
      • Manage external sharing from SPO sites
      • Manage access from unmanaged devices

      Data protection and security baselines

      Data Protection Baseline

      “Microsoft provides a default assessment in Compliance Manager for the Microsoft 365 data protection baseline" (Microsoft Docs, June 2022). This baseline assessment has a set of controls for key regulations and standards for data protection and general data governance. This baseline draws elements primarily from NIST CSF (National Institute of Standards and Technology Cybersecurity Framework) and ISO (International Organization for Standardization) as well as from FedRAMP (Federal Risk and Authorization Management Program) and GDPR (General Data Protection Regulation of the European Union).

      Security Baseline

      The final stage in M365 governance is security. You need to implement a governance policy that clearly defines storage locations for certain types of data and who has permission to access it. You need to record and track who accesses content and how they share it externally. “Part of your process should involve monitoring unusual external sharing to ensure staff only share documents that they are allowed to” (Rencore, 2021).

      Info-Tech Insights

      • Controls are already in place to set data protection policy. This assists in the MVP activities.
      • Finally, you need to set your security baseline to ensure proper permissions are in place.

      Prerequisite baseline

      Icon of crosshairs.
      Security

      MFA or SSO to access from anywhere, any device

      Banned password list

      BYOD sync with corporate network

      Icon of a group.
      Users

      Sign out inactive users automatically

      Enable guest users

      External sharing

      Block client forwarding rules

      Icon of a database.
      Resources

      Account lockout threshold

      OneDrive

      SharePoint

      Icon of gears.
      Controls

      Sensitivity labels, retention labels and policies, DLP

      Mobile application management policy

      Building baselines

      Sensitivity Profiles: Public, Internal, Confidential; Subcategory: Highly Confidential

      Microsoft 365 Collaboration Protection Profiles

      Sensitivity Public External Collaboration Internal Highly Confidential
      Description Data that is specifically prepared for public consumption Not approved for public consumption, but OK for external collaboration External collaboration highly discouraged and must be justified Data of the highest sensitivity: avoid oversharing, internal collaboration only
      Label details
      • No content marking
      • No encryption
      • Public site
      • External collaboration allowed
      • Unmanaged devices: allow full access
      • No content marking
      • No encryption
      • Private site
      • External collaboration allowed
      • Unmanaged devices: allow full access
      • Content marking
      • Encryption
      • Private site
      • External collaboration allowed but monitored
      • Unmanaged devices: limited web access
      • Content marking
      • Encryption
      • Private site
      • External collaboration disabled
      • Unmanaged devices: block access
      Teams or Site details Public Team or Site open discovery, guests are allowed Private Team or Site members are invited, guests are allowed Private Team or Site members are invited, guests are not allowed
      DLP None Warn Block

      Please Note: Global/Compliance Admins go to the 365 Groups platform, the compliance center (Purview), and Teams services (Source: Microsoft Documentation, “Microsoft Purview compliance documentation”)

      Info-Tech Insights

      • Building baseline profiles will be a part of your MVP. You will understand what type of information you are addressing and label it accordingly.
      • Sensitivity labels are a way to classify your organization's data in a way that specifies how sensitive the data is. This helps you decrease risks in sharing information that shouldn't be accessible to anyone outside your organization or department. Applying sensitivity labels allows you to protect all your data easily.

      MVP activities

      PRIMARY
      ACTIVITIES
      Define Your Governance
      The objective of the MVP is reducing barriers to establishing an initial governance position, and then enabling rapid progression of the solution to address a variety of tangible risks, including DLP, data retention, legal holds, and labeling.
      Decide on your classification labels early.

      CATEGORIZATION





      CLASSIFICATION

      MVP
      Data Discovery and Management
      AIP (Azure Information Protection) scanner helps discover, classify, label, and protect sensitive information in on-premises file servers. You can run the scanner and get immediate insight into risks with on-premises data.
      Baseline Setup
      Building baseline profiles will be a part of your MVP. You will understand what type of information you are addressing and label it accordingly. Microsoft provides a default assessment in Compliance Manager for the Microsoft 365 data protection baseline.
      Default M365 settings
      Microsoft provides a default assessment in Compliance Manager for the Microsoft 365 data protection baseline. This baseline assessment has a set of controls for key regulations and standards for data protection and general data governance.
      SUPPORT
      ACTIVITIES
      Retention Policy
      Retention policy is auto-applied. Decide whether to retain content, delete content, or retain and then delete the content.
      Sensitivity Labels
      Automatically enforce policies on groups through labels; classify groups.
      Workload Containers
      M365: SharePoint, Teams, OneDrive, and Exchange, where your data is stored for labels and policies.
      Unforced Policies
      Written policies that are not enforceable by controls in Compliance Manager such as acceptable use policy.
      Forced Policies
      Restrict sharing controls to outside organizations. Enforce prefix or suffix to group or team names.

      ACME Company MVP for M/O365

      PRIMARY
      ACTIVITIES
      Define Your Governance


      Focus on ability to use legal hold and GDPR compliance.

      CATEGORIZATION





      CLASSIFICATION

      MVP
      Data Discovery and Management


      Three classification levels (public, internal, confidential), which are applied by the user when data is created. Same three levels are used for AIP to scan legacy sources.

      Baseline Setup


      All data must at least be classified before it is uploaded to an M/O365 cloud service.

      Default M365 settings


      Turn on templates 1 8 the letter q and the number z

      SUPPORT
      ACTIVITIES
      Retention Policy


      Retention policy is auto-applied. Decide whether to retain content, delete content, or retain and then delete the content.

      Sensitivity Labels


      Automatically enforce policies on groups through labels; classify groups.

      Workload Containers


      M365: SharePoint, Teams, OneDrive, and Exchange, where your data is stored for labels and policies.

      Unforced Policies


      Written policies that are not enforceable by controls in Compliance Manager such as acceptable use policy.

      Forced Policies


      Restrict sharing controls to outside organizations. Enforce prefix or suffix to group or team names.

      Related Blueprints

      Govern Office 365

      Office 365 is as difficult to wrangle as it is valuable. Leverage best practices to produce governance outcomes aligned with your goals.

      Map your organizational goals to the administration features available in the Office 365 console. Your governance should reflect your requirements.

      Migrate to Office 365 Now

      Jumping into an Office 365 migration project without careful thought of the risks of a cloud migration will lead to project halt and interruption. Intentionally plan in order to expose risk and to develop project foresight for a smooth migration.

      Microsoft Teams Cookbook

      Remote work calls for leveraging your Office 365 license to use Microsoft Teams – but IT is unsure about best practices for governance and permissions. Moreover, IT has few resources to help train end users with Teams best practices

      IT Governance, Risk & Compliance

      Several blueprints are available on a broader topic of governance, from Make Your IT Governance Adaptable to Improve IT Governance to Drive Business Results and Build an IT Risk Management Program.

      Bibliography

      “Best practices for sharing files and folders with unauthenticated users.” Microsoft Build, 28 April 2022. Accessed 2 April 2022.

      “Build and manage assessments in Compliance Manager.” Microsoft Docs, 15 June 2022. Web.

      “Building a modern workplace with Microsoft 365.” Microsoft Inside Track, n.d. Web.

      Crane, Robert. “June 2020 Microsoft 365 Need to Know Webinar.” CIAOPS, SlideShare, 26 June 2020. Web.

      “Data Classification: Overview, Types, and Examples.” Simplilearn, 27 Dec. 2021. Accessed 11 April 2022.

      “Data loss prevention in Exchange Online.” Microsoft Docs, 19 April 2022. Web.

      Davies, Nahla. “5 Common Data Governance Challenges (and How to Overcome Them).” Dataversity. 25 October 2021. Accessed 5 April 2022.

      “Default labels and policies to protect your data.” Microsoft Build, April 2022. Accessed 3 April 2022.

      M., Peter. "Guide: The difference between Microsoft Backup and Retention." AvePoint Blog, 9 Oct. 2021. Accessed 4 April 2022.

      Meyer, Guillaume. “Sensitivity Labels: What They Are, Why You Need Them, and How to Apply Them.” nBold, 6 October 2021. Accessed 2 April 2022.

      “Microsoft 365 guidance for security & compliance.” Microsoft, 27 April 2022. Accessed 28 April 2022.

      “Microsoft Purview compliance portal.” Microsoft, 19 April 2022. Accessed 22 April 2022.

      “Microsoft Purview compliance documentation.” Microsoft, n.d. Accessed 22 April 2022.

      “Microsoft Trust Center: Products and services that run on trust.” Microsoft, 2022. Accessed 3 April 2022.

      “Protect your sensitive data with Microsoft Purview.” Microsoft Build, April 2022. Accessed 3 April 2022.

      Zimmergren, Tobias. “4 steps to successful cloud governance in Office 365.” Rencore, 9 Sept. 2021. Accessed 5 April 2022.

      Enhance Your Solution Architecture Practices

      • Buy Link or Shortcode: {j2store}157|cart{/j2store}
      • member rating overall impact: 9.0/10 Overall Impact
      • member rating average dollars saved: $33,359 Average $ Saved
      • member rating average days saved: 11 Average Days Saved
      • Parent Category Name: Development
      • Parent Category Link: /development
      • In today’s world, business agility is essential to stay competitive. Quick responses to business needs through efficient development and deployment practices is critical for business value delivery.
      • A mature solution architecture practice is the basic necessity for a business to have technical agility.

      Our Advice

      Critical Insight

      Don’t architect for normal situations. That is a shallow approach and leads to decisions that may seem “right” but will not be able to stand up to system elasticity needs.

      Impact and Result

      • Understand the different parts of a continuous security architecture framework and how they may apply to your decisions.
      • Develop a solution architecture for upcoming work (or if there is a desire to reduce tech debt).

      Enhance Your Solution Architecture Practices Research & Tools

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

      1. Solution Architecture Practices Deck – A deck to help you develop an approach for or validate existing solution architecture capability.

      Translate stakeholder objectives into architecture requirements, solutions, and changes. Incorporate architecture quality attributes in decisions to increase your architecture’s life. Evaluate your solution architecture from multiple views to obtain a holistic perspective of the range of issues, risks, and opportunities.

      • Enhance Your Solution Architecture Practices – Phases 1-3

      2. Solution Architecture Template – A template to record the results from the exercises to help you define, detail, and make real your digital product vision.

      Identify and detail the value maps that support the business, and discover the architectural quality attribute that is most important for the value maps. Brainstorm solutions for design decisions for data, security, scalability, and performance.

      • Solution Architecture Template
      [infographic]

      Workshop: Enhance Your Solution Architecture 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 Vision and Value Maps

      The Purpose

      Document a vision statement for the solution architecture practice (in general) and/or a specific vision statement, if using a single project as an example.

      Document business architecture and capabilities.

      Decompose capabilities into use cases.

      Key Benefits Achieved

      Provide a great foundation for an actionable vision and goals that people can align to.

      Develop a collaborative understanding of business capabilities.

      Develop a collaborative understanding of use cases and personas that are relevant for the business.

      Activities

      1.1 Develop vision statement.

      1.2 Document list of value stream maps and their associated use cases.

      1.3 Document architectural quality attributes needed for use cases using SRME.

      Outputs

      Solution Architecture Template with sections filled out for vision statement canvas and value maps

      2 Continue Vision and Value Maps, Begin Phase 2

      The Purpose

      Map value stream to required architectural attributes.

      Prioritize architecture decisions.

      Discuss and document data architecture.

      Key Benefits Achieved

      An understanding of architectural attributes needed for value streams.

      Conceptual understanding of data architecture.

      Activities

      2.1 Map value stream to required architectural attributes.

      2.2 Prioritize architecture decisions.

      2.3 Discuss and document data architecture.

      Outputs

      Solution Architecture Template with sections filled out for value stream and architecture attribute mapping; a prioritized list of architecture design decisions; and data architecture

      3 Continue Phase 2, Begin Phase 3

      The Purpose

      Discuss security and threat assessment.

      Discuss resolutions to threats via security architecture decisions.

      Discuss system’s scalability needs.

      Key Benefits Achieved

      Decisions for security architecture.

      Decisions for scalability architecture.

      Activities

      3.1 Discuss security and threat assessment.

      3.2 Discuss resolutions to threats via security architecture decisions.

      3.3 Discuss system’s scalability needs.

      Outputs

      Solution Architecture Template with sections filled out for security architecture and scalability design

      4 Continue Phase 3, Start and Finish Phase 4

      The Purpose

      Discuss performance architecture.

      Compile all the architectural decisions into a solutions architecture list.

      Key Benefits Achieved

      A complete solution architecture.

      A set of principles that will form the foundation of solution architecture practices.

      Activities

      4.1 Discuss performance architecture.

      4.2 Compile all the architectural decisions into a solutions architecture list.

      Outputs

      Solution Architecture Template with sections filled out for performance and a complete solution architecture

      Further reading

      Enhance Your Solution Architecture Practice

      Ensure your software systems solution is architected to reflect stakeholders’ short- and long-term needs.

      Analyst Perspective

      Application architecture is a critical foundation for supporting the growth and evolution of application systems. However, the business is willing to exchange the extension of the architecture’s life with quality best practices for the quick delivery of new or enhanced application functionalities. This trade-off may generate immediate benefits to stakeholders, but it will come with high maintenance and upgrade costs in the future, rendering your system legacy early.

      Technical teams know the importance of implementing quality attributes into architecture but are unable to gain approval for the investments. Overcoming this challenge requires a focus of architectural enhancements on specific problem areas with significant business visibility. Then, demonstrate how quality solutions are vital enablers for supporting valuable application functionalities by tracing these solutions to stakeholder objectives and conducting business and technical risk and impact assessments through multiple business and technical perspectives.

      this is a picture of Andrew Kum-Seun

      Andrew Kum-Seun
      Research Manager, Applications
      Info-Tech Research Group

      Enhance Your Solution Architecture

      Ensure your software systems solution is architected to reflect stakeholders’ short- and long-term needs.

      EXECUTIVE BRIEF

      Executive Summary

      Your Challenge

      • Most organizations have some form of solution architecture; however, it may not accurately and sufficiently support the current and rapidly changing business and technical environments.
      • To enable quick delivery, applications are built and integrated haphazardly, typically omitting architecture quality practices.

      Common Obstacles

      • Failing to involve development and stakeholder perspectives in design can lead to short-lived architecture and critical development, testing, and deployment constraints and risks being omitted.
      • Architects are experiencing little traction implementing solutions to improve architecture quality due to the challenge of tracing these solutions back to the right stakeholder objectives.

      Info-Tech's Approach

      • Translate stakeholder objectives into architecture requirements, solutions, and changes. Incorporate architecture quality attributes in decisions to increase your architecture’s life.
      • Evaluate your solution architecture from multiple views to obtain a holistic perspective of the range of issues, risks, and opportunities.
      • Regularly review and recalibrate your solution architecture so that it accurately reflects and supports current stakeholder needs and technical environments.

      Info-Tech Insight

      Well-received applications can have poor architectural qualities. Functional needs often take precedence over quality architecture. Quality must be baked into design, execution, and decision-making practices to ensure the right tradeoffs are made.

      A badly designed solution architecture is the root of all technical evils

      A well-thought-through and strategically designed solution architecture is essential for the long-term success of any software system, and by extension, the organization because:

      1. It will help achieve quality attribute requirements (security, scalability, performance, usability, resiliency, etc.) for a software system.
      2. It can define and refine architectural guiding principles. A solution architecture is not only important for today but also a vision for the future of the system’s ability to react positively to changing business needs.
      3. It can help build usable (and reusable) services. In a fast-moving environment, the convenience of having pre-made plug-and-play architectural objects reduces the risk incurred from knee-jerk reactions in response to unexpected demands.
      4. It can be used to create a roadmap to an IT future state. Architectural concerns support transition planning activities that can lead to the successful implementation of a strategic IT plan.

      Demand for quick delivery makes teams omit architectural best practices, increasing downstream risks

      In its need for speed, a business often doesn’t see the value in making sure architecture is maintainable, reusable, and scalable. This demand leads to an organizational desire for development practices and the procurement of vendors that favor time-to-market over long-term maintainability. Unfortunately, technical teams are pushed to omit design quality and validation best practices.

      What are the business impacts of omitting architecture design practices?

      Poor quality application architecture impedes business growth opportunities, exposes enterprise systems to risks, and consumes precious IT budgets in maintenance that could otherwise be used for innovation and new projects.

      Previous estimations indicate that roughly 50% of security problems are the result of software design. […] Flaws in the architecture of a software system can have a greater impact on various security concerns in the system, and as a result, give more space and flexibility for malicious users.(Source: IEEE Software)

      Errors in software requirements and software design documents are more frequent than errors in the source code itself according to Computer Finance Magazine. Defects introduced during the requirements and design phase are not only more probable but also more severe and more difficult to remove. (Source: iSixSigma)

      Design a solution architecture that can be successful within the constraints and complexities set before you

      APPLICATION ARCHITECTURE…

      … describes the dependencies, structures, constraints, standards, and development guidelines to successfully deliver functional and long-living applications. This artifact lays the foundation to discuss the enhancement of the use and operations of your systems considering existing complexities.

      Good architecture design practices can give you a number of benefits:

      Lowers maintenance costs by revealing key issues and risks early. The Systems Sciences Institute at IBM has reported that the cost to fix an error found after product release was 4 to 5 times as much as one uncovered during design.(iSixSigma)

      Supports the design and implementation activities by providing key insights for project scheduling, work allocation, cost analysis, risk management, and skills development.(IBM: developerWorks)

      Eliminates unnecessary creativity and activities on the part of designers and implementers, which is achieved by imposing the necessary constraints on what they can do and making it clear that deviation from constraints can break the architecture.(IBM: developerWorks)

      Use Info-Tech’s Continuous Solution Architecture (CSA) Framework for designing adaptable systems

      Solution architecture is not a one-size-fits-all conversation. There are many design considerations and trade-offs to keep in mind as a product or services solution is conceptualized, evaluated, tested, and confirmed. The following is a list of good practices that should inform most architecture design decisions.

      Principle 1: Design your solution to have at least two of everything.

      Principle 2: Include a “kill switch” in your fault-isolation design. You should be able to turn off everything you release.

      Principle 3: If it can be monitored, it should be. Use server and audit logs where possible.

      Principle 4: Asynchronous is better than synchronous. Asynchronous design is more complex but worth the processing efficiency it introduces.

      Principle 5: Stateless over stateful: State data should only be used if necessary.

      Principle 6: Go horizonal (scale out) over vertical (scale up).

      Principle 7: Good architecture comes in small packages.

      Principle 8: Practice just-in-time architecture. Delay finalizing an approach for as long as you can.

      Principle 9: X-ilities over features. Quality of an architecture is the foundation over which features exist. A weak foundation can never be obfuscated through shiny features.

      Principle 10: Architect for products not projects. A product is an ongoing concern, while a project is short lived and therefore only focused on what is. A product mindset forces architects to think about what can or should be.

      Principle 11: Design for rollback: When all else fails, you should be able to stand up the previous best state of the system.

      Principle 12: Test the solution architecture like you test your solution’s features.

      CSA should be used for every step in designing a solution’s architecture

      Solution architecture is a technical response to a business need, and like all complex evolutionary systems, must adapt its design for changing circumstances.

      The triggers for changes to existing solution architectures can come from, at least, three sources:

      1. Changing business goals
      2. Existing backlog of technical debt
      3. Solution architecture roadmap

      A solution’s architecture is cross-cutting and multi-dimensional and at the minimum includes:

      • Product Portfolio Strategy
      • Application Architecture
      • Data Architecture
      • Information Architecture
      • Operational Architecture

      along with several qualitative attributes (also called non-functional requirements).

      This image contains a chart which demonstrates the relationship between changing hanging business goals, Existing backlog of technical debt, Solution architecture roadmap, and Product Portfolio Strategy, Application Architecture, Data Architecture, Information Architecture and, Operational Architecture

      Related Research: Product Portfolio Strategy

      Integrate Portfolios to Create Exceptional Customer Value

      • Define an organizing principle that will structure your projects and applications in a way that matters to your stakeholders.
      • Bridge application and project portfolio data using the organizing principle that matters to communicate with stakeholders across the organization.
      • Create a dashboard that brings together the benefits of both project and application portfolio management to improve visibility and decision making.

      Deliver on Your Digital Portfolio Vision

      • 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.

      Related Research: Data, Information & Integration Architecture

      Build a Data Architecture Roadmap

      • Have a framework in place to identify the appropriate solution for the challenge at hand. Our three-phase practical approach will help you build a custom and modernized data architecture.
      • Identify and prioritize the business drivers in which data architecture changes would create the largest overall benefit and determine the corresponding data architecture tiers that need to be addressed.
      • Discover the best-practice trends, measure your current state, and define the targets for your data architecture tactics.
      • Build a cohesive and personalized roadmap for restructuring your data architecture. Manage your decisions and resulting changes.

      Build a Data Pipeline for Reporting and Analytics

      • Understand your high-level business capabilities and interactions across them – your data repositories and flows should be just a digital reflection thereof.
      • Divide your data world in logical verticals overlaid with various speed data progression lanes, i.e. build your data pipeline – and conquer it one segment at a time.
      • Use the most appropriate database design pattern for a given phase/component in your data pipeline progression.

      Related Research:Operational Architecture

      Optimize Application Release Management

      • Acquire release management ownership. Ensure there is appropriate accountability for the speed and quality of the releases passing through the entire pipeline.
      • A release manager has oversight over the entire release process and facilitates the necessary communication between business stakeholders and various IT roles.
      • Instill holistic thinking. Release management includes all steps required to push release and change requests to production along with the hand-off to Operations and Support. Increase the transparency and visibility of the entire pipeline to ensure local optimizations do not generate bottlenecks in other areas.
      • Standardize and lay a strong release management foundation. Optimize the key areas where you are experiencing the most pain and continually improve.

      Build Your Infrastructure Roadmap

      • Increased communication. More information being shared to more people who need it.
      • Better planning. More accurate information being shared.
      • Reduced lead times. Less due diligence or discovery work required as part of project implementations.
      • Faster delivery times. Less low-value work, freeing up more time for project work.

      Related Research:Security Architecture

      Identify Opportunities to Mature the Security Architecture

      • A right-sized security architecture can be created by assessing the complexity of the IT department, the operations currently underway for security, and the perceived value of a security architecture within the organization. This will bring about a deeper understanding of the organizational infrastructure.
      • Developing a security architecture should also result in a list of opportunities (i.e. initiatives) that an organization can integrate into a roadmap. These initiatives will seek to improve security operations and strengthen the IT department’s understanding of security’s role within the organization.
      • A better understanding of the infrastructure will help to save time on determining the correct technologies required from vendors, and therefore, cut down on the amount of vendor noise.
      • Creating a defensible roadmap will assist with justifying future security spend.

      Key deliverable:

      Solution Architecture Template
      Record the results from the exercises to help you define, detail, and make real your digital product vision.

      Blueprint Deliverables

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

      This image contains screenshots of the deliverables which will be discussed later in this blueprint

      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

      Workshop Overview

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

      Day 1 Day 2 Day 3 Day 4
      Exercises
      1. Articulate an architectural vision
      2. Develop dynamic value stream maps
      1. Create a conceptual map between the value stream, use case, and required architectural attribute
      2. Create a prioritized list of architectural attributes
      3. Develop a data architecture that supports transactional and analytical needs
      1. Document security architecture risks and mitigations
      2. Document scalability architecture
      1. Document performance-enhancing architecture
      2. Bring it all together
      Outcomes
      1. Architecture vision
      2. Dynamic value stream maps (including user stories/personas)
      1. List of required architectural attributes
      2. Architectural attributes prioritized
      3. Data architecture design decisions
      1. Security threat and risk analysis
      2. Security design decisions
      3. Scalability design decisions
      1. Performance design decisions
      2. Finalized decisions

      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.
      This GI is between 8 to 10 calls over the course of approximately four to six months.

      Phase 1 Phase 2 Phase 2
      Call #1:
      Articulate an architectural vision.
      Call #4:
      Continue discussion on value stream mapping and related use cases.
      Call #6:
      Document security design decisions.
      Call #2:
      Discuss value stream mapping and related use cases.
      Call #5:
      • Map the value streams to required architectural attribute.
      • Create a prioritized list of architectural attributes.
      Call #7:
      • Document scalability design decisions.
      • Document performance design decisions.
      Call #3:
      Continue discussion on value stream mapping and related use cases.
      Call #8:
      Bring it all together.

      Phase 1: Visions and Value Maps

      Phase 1

      1.1 Articulate an Architectural Vision
      1.2 Develop Dynamic Value Stream Maps
      1.3 Map Value Streams, Use Cases, and Required Architectural Attributes
      1.4 Create a Prioritized List of Architectural Attributes

      Phase 2

      2.1 Develop a Data Architecture That Supports Transactional and Analytical Needs
      2.2 Document Security Architecture Risks and Mitigations

      Phase 3

      3.1 Document Scalability Architecture
      3.2 Document Performance Enhancing Architecture
      3.3 Combine the Different Architecture Design Decisions Into a Unified Solution Architecture

      This phase will walk you through the following activities:

      • Determine a vision for architecture outcomes
      • Draw dynamic value stream maps
      • Derive architectural design decisions
      • Prioritize design decisions

      This phase involves the following participants:

      • Business Architect
      • Product Owner
      • Application Architect
      • Integration Architect
      • Database Architect
      • Enterprise Architect

      Enhance Your Solution Architecture Practice

      Let’s get this straight: You need an architectural vision

      If you start off by saying I want to architect a system, you’ve already lost. Remember what a vision is for!

      An architectural vision...

      … is your North Star

      Your product vision serves as the single fixed point for product development and delivery.

      … aligns stakeholders

      It gets everyone on the same page.

      … helps focus on meaningful work

      There is no pride in being a rudderless ship. It can also be very expensive.

      And eventually...

      … kick-starts your strategy

      We know where to go, we know who to bring along, and we know the steps to get there. Let’s plan this out.

      An architectural vision is multi-dimensional

      Who is the target customer (or customers)?

      What is the key benefit a customer can get from using our service or product?

      Why should they be engaged with you?

      What makes our service or product better than our competitors?

      (Adapted from Crossing the Chasm)

      Info-Tech Insight

      It doesn’t matter if you are delivering value to internal or external stakeholders, you need a product vision to ensure everyone understands the “why.”

      Use a canvas as the dashboard for your architecture

      The solution architecture canvas provides a single dashboard to quickly define and communicate the most important information about the vision. A canvas is an effective tool for aligning teams and providing an executive summary view.

      This image contains a sample canvas for you to use as the dashboard for your architecture. The sections are: Solution Name, Tracking Info, Vision, Business Goals, Metrics, Personas, and Stakeholders.

      Leverage the solution architecture canvas to state and inform your architecture vision

      This image contains the sample canvas from the previous section, with annotations explaining what to do for each of the headings.

      1.1 Craft a vision statement for your solution’s architecture

      1. Use the product canvas template provided for articulating your solution’s architecture.

      *If needed, remove or add additional data points to fit your purposes.

      There are different statement templates available to help form your product vision statements. Some include:

      • For [our target customer], who [customer’s need], the [product] is a [product category or description] that [unique benefits and selling points]. Unlike [competitors or current methods], our product [main differentiators].
      • We believe (in) a [noun: world, time, state, etc.] where [persona] can [verb: do, make, offer, etc.], for/by/with [benefit/goal].
      • To [verb: empower, unlock, enable, create, etc.] [persona] to [benefit, goal, future state].
      • Our vision is to [verb: build, design, provide] the [goal, future state] to [verb: help, enable, make it easier to...] [persona].

      (Adapted from Crossing the Chasm)

      Download the Solution Architecture Template and document your vision statement.

      Input

      • Business Goals
      • Product Portfolio Vision

      Output

      • Solution Architecture Vision

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Product Owner
      • IT Leadership
      • Business Leadership

      Solution Architecture Canvas: Refine your vision statement

      This image contains a screenshot of the canvas from earlier in the blueprint, with only the annotation for Solution Name: Vision, unique value proposition, elevator pitch, or positioning statement.

      Understand your value streams before determining your solution’s architecture

      Business Strategy

      Sets and communicates the direction of the entire organization.

      Value Stream

      Segments, groups, and creates a coherent narrative as to how an organization creates value.

      Business Capability Map

      Decomposes an organization into its component parts to establish a common language across the organization.

      Execution

      Implements the business strategy through capability building or improvement projects.

      Identify your organization’s goals and define the value streams that support them

      Goal

      Revenue Growth

      Value Streams

      Stream 1- Product Purchase
      Stream 2- Customer Acquisition
      stream 3- Product Financing

      There are many techniques that help with constructing value streams and their capabilities.

      Domain-driven design is a technique that can be used for hypothesizing the value maps, their capabilities, and associated solution architecture.

      Read more about domain-driven design here.

      Value streams can be external (deliver value to customers) or internal (support operations)

        External Perspective

      1. Core value streams are mostly externally facing: they deliver value to either an external/internal customer and they tie to the customer perspective of the strategy map.
      • E.g. customer acquisition, product purchase, product delivery

      Internal Perspective

    • Support value streams are internally facing: they provide the foundational support for an organization to operate.
      • E.g. employee recruitment to retirement

      Key Questions to Ask While Evaluating Value Streams

      • Who are your customers?
      • What benefits do we deliver to them?
      • How do we deliver those benefits?
      • How does the customer receive the benefits?
      This image contains an example of value streams. The main headings are: Customer Acquisitions, Product Purchase, Product Delivery, Confirm Order, Product Financing, and Product Release.

      Value streams highlight the what, not the how

      Value chains set a high-level context, but architectural decisions still need to be made to deal with the dynamism of user interaction and their subsequent expectations. User stories (and/or use cases) and themes are great tools for developing such decisions.

      Product Delivery

      1. Order Confirmation
      2. Order Dispatching
      3. Warehouse Management
      4. Fill Order
      5. Ship Order
      6. Deliver Order

      Use Case and User Story Theme: Confirm Order

      This image shows the relationship between confirming the customer's order online, and the Online Buyer, the Online Catalog, the Integrated Payment, and the Inventory Lookup.

      The use case Confirming Customer’s Online Order has four actors:

      1. An Online Buyer who should be provided with a catalog of products to purchase from.
      2. An Online Catalog that is invoked to display its contents on demand.
      3. An Integrated Payment system for accepting an online form of payment (credit card, Bitcoins, etc.) in a secure transaction.
      4. An Inventory Lookup module that confirms there is stock available to satisfy the Online Buyer’s order.

      Info-Tech Insight

      Each use case theme links back to a feature(s) in the product backlog.

      Related Research

      Deliver on Your Digital Portfolio Vision

      • 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.

      Document Your Business Architecture

      • Recognize the opportunity for architecture work, analyze the current and target states of your business strategy, and identify and engage the right stakeholders.
      • Model the business in the form of architectural blueprints.
      • Apply business architecture techniques such as strategy maps, value streams, and business capability maps to design usable and accurate blueprints of the business.
      • Drive business architecture forward to promote real value to the organization.
      • Assess your current projects to determine if you are investing in the right capabilities. Conduct business capability assessments to identify opportunities and to prioritize projects.

      1.2 Document dynamic value stream maps

      1. Create value stream maps that support your business objectives.
      • The value stream maps could belong to existing or new business objectives.
    • For each value stream map:
      • Determine use case(s), the actors, and their expected activity.

      *Refer to the next slide for an example of a dynamic value stream map.

      Download the Solution Architecture Template for documentation of dynamic value stream map

      Input

      • Business Goals
      • Some or All Existing Business Processes
      • Some or All Proposed New Business Processes

      Output

      • Dynamic Value Stream Maps for Multiple Use Roles and Use Cases

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Product Owner
      • Application Architect
      • Integration Architect

      Example: Dynamic value stream map

      Loan Provision*

      *Value Stream Name: Usually has the same name as the capability it illustrates.

      Loan Application**; Disbursement of Fund**; Risk Management**; Service Accounts**

      **Value Stream Components: Specific functions that support the successful delivery of a value stream.

      Disbursement of Funds

      This image shows the relationship between depositing the load into the applicant's bank account, and the Applicant's bank, the Loan Applicant, and the Loan Supplier.

      Style #1:

      The use case Disbursement of Funds has three actors:

      1. A Loan Applicant who applied for a loan and got approved for one.
      2. A Loan Supplier who is the source for the funds.
      3. The Applicant’s Bank that has an account into which the funds are deposited.

      Style # 2:

      Loan Provision: Disbursement of Funds
      Use Case Actors Expectation
      Deposit Loan Into Applicant’s Bank Account
      1. Loan Applicant
      2. Loan Supplier
      3. Applicant’s Bank
      1. Should be able to see deposit in bank account
      2. Deposit funds into account
      3. Accept funds into account

      Mid-Phase 1 Checkpoint

      By now, the following items are ideally completed:

      • Mid-Phase 1 Checkpoint

      Start with an investigation of your architecture’s qualitative needs

      Quality attributes can be viewed as the -ilities (e.g. scalability, usability, reliability) that a software system needs to provide. A system not meeting any of its quality attribute requirements will likely not function as required. Examples of quality attributes are:

      1. Slow system response time
      2. Security breaches that result in loss of personal data
      3. A product feature upgrade that is not compatible with previous versions
      Examples of Qualitative Attributes
      Performance Compatibility Usability Reliability Security Maintainability
      • Response Time
      • Resource Utilization
      • System Capacity
      • Interoperability
      • Accessibility
      • User Interface
      • Intuitiveness
      • Availability
      • Fault Tolerance
      • Recoverability
      • Integrity
      • Non-Repudiation
      • Modularity
      • Reusability
      • Modifiability
      • Testability

      Focus on quality attributes that are architecturally significant.

      • Not every system requires every quality attribute.
      • Pay attention to those attributes without which the solution will not be able to satisfy a user’s abstract* expectation.
      • This set can be considered Architecturally Significant Requirements (ASR). ASR concern scenarios have the most impact on the architecture of the software system.
      • ASR are fundamental needs of the system and changing them in the future can be a costly and difficult exercise.

      *Abstract since attributes like performance and reliability are not directly measurable by a user.

      Stimulus Response Measurement Environmental Context

      For applicable use cases: (*Adapted from S Carnegie Mellon University, 2000)

      1. Determine the Stimulus (temporal, external, or internal) that puts stress on the system. For example, a VPN-accessed hospital management system is used for nurses to login at 8am every weekday.
      2. Describe how the system should Respond to the stimulus. For example, the hospital management system should complete a nurse login under 10ms on initiation of the HTTPS request.
      3. Set a Measurement criteria for determining the success of the response to the stimulus. For example, the system should be able to successfully respond to 98% of the HTTPS requests the first time.
      4. Note the environmental context under which the stimulus occurs, including any unusual conditions in effect.
      • The hospital management system needs to respond in under 10ms under typical load or peak load?
      • What is the time variance of peak loads, for example, an e-commerce system during a Black Friday sale?
      • How big is the peak load?

      Info-Tech Insight

      Three out of four is bad. Don’t architect for normal situations because the solution will be fragile and prone to catastrophic failure under unexpected events.
      Read article: Retail sites crash under weight of online Black Friday shoppers.

      Discover and evaluate the qualitative attributes needed for use cases or user stories

      Deposit Loan Into Applicant’s Bank Account

      Assume analysis is being done for a to-be developed system.

      User Loan Applicant
      Expectations On login to the web system, should be able to see accurate bank balance after loan funds are deposited.
      User signs into the online portal and opens their account balance page.
      Expected Response From System System creates a connection to the data source and renders it on the screen in under 10ms.
      Measurement Under Normal Loads:
      • Response in 10ms or less
      • Data should not be stale
      Under Peak Loads:
      • Response in 15ms or less
      • Data should not be stale
      Quality Attribute Required Required Attribute # 1: Performance
      • Design Decision: Reduce latency by placing authorization components closer to user’s location.
      Required Attribute # 2: Data Reliability
      • Design Decision: Use event-driven ETL pipelines.
      Required Attribute # 3: Scalability
      • Design Decision: Following Principle # 4 of the CSA (JIT Architecture), delay decision until necessary.

      Use cases developed in Phase 1.2 should be used here. (Adapted from the ATAM Utility Tree Method for Quality Attribute Engineering)

      Reduce technical debt while you are at it

      Deposit Loan Into Applicant’s Bank Account

      Assume analysis is being done for a to-be developed system.

      UserLoan Applicant
      ExpectationsOn login to the web system, should be able to see accurate bank balance after loan funds are deposited.
      User signs into the online portal and opens their account balance page.
      Expected Response From SystemSystem creates a connection to the data source and renders it on the screen in under 10ms.
      MeasurementUnder Normal Loads:
      • Response in 10ms or less
      • Data should not be stale
      Under Peak Loads:
      • Response in 15ms or less
      • Data should not be stale
      Quality Attribute RequiredRequired Attribute # 1: Performance
      • Design Decision: Reduce latency by placing authorization components closer to user’s location.

      Required Attribute # 2: Data Reliability

      • Expected is 15ms or less under peak loads, but average latency is 21ms.
      • Design Decision: Use event-driven ETL pipelines.

      Required Attribute # 3: Scalability

      • Data should not be stale and should sync instantaneously, but in some zip codes data synchronization is taking 8 hours.
      • Design Decision: Investigate integrations and flows across application, database, and infrastructure. (Note: A dedicated section for discussing scalability is presented in Phase 2.)

      1.3 Create a conceptual map between the value streams, use cases, and required architectural attributes

      1. For selected use cases completed in Phase 1.2:
      • Map the value stream to its associated use cases.
      • For each use case, list the required architectural quality attributes.

      Download the Solution Architecture Template for mapping value stream components to their required architectural attribute.

      Input

      • Use Cases
      • User Roles
      • Stimulus to System
      • Response From System
      • Response Measurement

      Output

      • List of Architectural Quality Attributes

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Application Architect
      • Integration Architect
      • Database Architect
      • Infrastructure Architect

      Example for Phase 1.3

      Loan Provision

      Loan Application → Disbursement of Funds → Risk Management → Service Accounts

      Value Stream Component Use Case Required Architectural Attribute
      Loan Application UC1: Submit Loan Application
      UC2: Review Loan Application
      UC3: Approve Loan Application
      UCn: ……..
      UC1: Resilience, Data Reliability
      UC2: Data Reliability
      UC3: Scalability, Security, Performance
      UCn: …..
      Disbursement of Funds UC1: Deposit Funds Into Applicant’s Bank Account
      UCn: ……..
      UC1: Performance, Scalability, Data Reliability
      Risk Management ….. …..
      Service Accounts ….. …..

      1.2 Document dynamic value stream maps

      1. Create value stream maps that support your business objectives.
      • The value stream maps could belong to existing or new business objectives.
    • For each value stream map:
      • Determine use case(s), the actors, and their expected activity.

      *Refer to the next slide for an example of a dynamic value stream map.

      Download the Solution Architecture Template for documentation of dynamic value stream map

      Input

      • Business Goals
      • Some or All Existing Business Processes
      • Some or All Proposed New Business Processes

      Output

      • Dynamic Value Stream Maps for Multiple Use Roles and Use Cases

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Product Owner
      • Application Architect
      • Integration Architect

      Example: Dynamic value stream map

      Loan Provision*

      *Value Stream Name: Usually has the same name as the capability it illustrates.

      Loan Application**; Disbursement of Fund**; Risk Management**; Service Accounts**

      **Value Stream Components: Specific functions that support the successful delivery of a value stream.

      Disbursement of Funds

      This image shows the relationship between depositing the load into the applicant's bank account, and the Applicant's bank, the Loan Applicant, and the Loan Supplier.

      Style #1:

      The use case Disbursement of Funds has three actors:

      1. A Loan Applicant who applied for a loan and got approved for one.
      2. A Loan Supplier who is the source for the funds.
      3. The Applicant’s Bank that has an account into which the funds are deposited.

      Style # 2:

      Loan Provision: Disbursement of Funds
      Use Case Actors Expectation
      Deposit Loan Into Applicant’s Bank Account
      1. Loan Applicant
      2. Loan Supplier
      3. Applicant’s Bank
      1. Should be able to see deposit in bank account
      2. Deposit funds into account
      3. Accept funds into account

      Mid-Phase 1 Checkpoint

      By now, the following items are ideally completed:

      • Mid-Phase 1 Checkpoint

      Start with an investigation of your architecture’s qualitative needs

      Quality attributes can be viewed as the -ilities (e.g. scalability, usability, reliability) that a software system needs to provide. A system not meeting any of its quality attribute requirements will likely not function as required. Examples of quality attributes are:

      1. Slow system response time
      2. Security breaches that result in loss of personal data
      3. A product feature upgrade that is not compatible with previous versions
      Examples of Qualitative Attributes
      Performance Compatibility Usability Reliability Security Maintainability
      • Response Time
      • Resource Utilization
      • System Capacity
      • Interoperability
      • Accessibility
      • User Interface
      • Intuitiveness
      • Availability
      • Fault Tolerance
      • Recoverability
      • Integrity
      • Non-Repudiation
      • Modularity
      • Reusability
      • Modifiability
      • Testability

      Focus on quality attributes that are architecturally significant.

      • Not every system requires every quality attribute.
      • Pay attention to those attributes without which the solution will not be able to satisfy a user’s abstract* expectation.
      • This set can be considered Architecturally Significant Requirements (ASR). ASR concern scenarios have the most impact on the architecture of the software system.
      • ASR are fundamental needs of the system and changing them in the future can be a costly and difficult exercise.

      *Abstract since attributes like performance and reliability are not directly measurable by a user.

      Stimulus Response Measurement Environmental Context

      For applicable use cases: (*Adapted from S Carnegie Mellon University, 2000)

      1. Determine the Stimulus (temporal, external, or internal) that puts stress on the system. For example, a VPN-accessed hospital management system is used for nurses to login at 8am every weekday.
      2. Describe how the system should Respond to the stimulus. For example, the hospital management system should complete a nurse login under 10ms on initiation of the HTTPS request.
      3. Set a Measurement criteria for determining the success of the response to the stimulus. For example, the system should be able to successfully respond to 98% of the HTTPS requests the first time.
      4. Note the environmental context under which the stimulus occurs, including any unusual conditions in effect.
      • The hospital management system needs to respond in under 10ms under typical load or peak load?
      • What is the time variance of peak loads, for example, an e-commerce system during a Black Friday sale?
      • How big is the peak load?

      Info-Tech Insight

      Three out of four is bad. Don’t architect for normal situations because the solution will be fragile and prone to catastrophic failure under unexpected events.
      Read article: Retail sites crash under weight of online Black Friday shoppers.

      Discover and evaluate the qualitative attributes needed for use cases or user stories

      Deposit Loan Into Applicant’s Bank Account

      Assume analysis is being done for a to-be developed system.

      User Loan Applicant
      Expectations On login to the web system, should be able to see accurate bank balance after loan funds are deposited.
      User signs into the online portal and opens their account balance page.
      Expected Response From System System creates a connection to the data source and renders it on the screen in under 10ms.
      Measurement Under Normal Loads:
      • Response in 10ms or less
      • Data should not be stale
      Under Peak Loads:
      • Response in 15ms or less
      • Data should not be stale
      Quality Attribute Required Required Attribute # 1: Performance
      • Design Decision: Reduce latency by placing authorization components closer to user’s location.
      Required Attribute # 2: Data Reliability
      • Design Decision: Use event-driven ETL pipelines.
      Required Attribute # 3: Scalability
      • Design Decision: Following Principle # 4 of the CSA (JIT Architecture), delay decision until necessary.

      Use cases developed in Phase 1.2 should be used here. (Adapted from the ATAM Utility Tree Method for Quality Attribute Engineering)

      Reduce technical debt while you are at it

      Deposit Loan Into Applicant’s Bank Account

      Assume analysis is being done for a to-be developed system.

      UserLoan Applicant
      ExpectationsOn login to the web system, should be able to see accurate bank balance after loan funds are deposited.
      User signs into the online portal and opens their account balance page.
      Expected Response From SystemSystem creates a connection to the data source and renders it on the screen in under 10ms.
      MeasurementUnder Normal Loads:
      • Response in 10ms or less
      • Data should not be stale
      Under Peak Loads:
      • Response in 15ms or less
      • Data should not be stale
      Quality Attribute RequiredRequired Attribute # 1: Performance
      • Design Decision: Reduce latency by placing authorization components closer to user’s location.

      Required Attribute # 2: Data Reliability

      • Expected is 15ms or less under peak loads, but average latency is 21ms.
      • Design Decision: Use event-driven ETL pipelines.

      Required Attribute # 3: Scalability

      • Data should not be stale and should sync instantaneously, but in some zip codes data synchronization is taking 8 hours.
      • Design Decision: Investigate integrations and flows across application, database, and infrastructure. (Note: A dedicated section for discussing scalability is presented in Phase 2.)

      1.3 Create a conceptual map between the value streams, use cases, and required architectural attributes

      1. For selected use cases completed in Phase 1.2:
      • Map the value stream to its associated use cases.
      • For each use case, list the required architectural quality attributes.

      Download the Solution Architecture Template for mapping value stream components to their required architectural attribute.

      Input

      • Use Cases
      • User Roles
      • Stimulus to System
      • Response From System
      • Response Measurement

      Output

      • List of Architectural Quality Attributes

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Application Architect
      • Integration Architect
      • Database Architect
      • Infrastructure Architect

      Prioritize architectural quality attributes to ensure a right-engineered solution

      Trade-offs are inherent in solution architecture. Scaling systems may impact performance and weaken security, while fault-tolerance and redundancy may improve availability but at higher than desired costs. In the end, the best solution is not always perfect, but balanced and right-engineered (versus over- or under-engineered).

      Loan Provision

      Loan Application → Disbursement of Funds → Risk Management → Service Accounts

      1. Map architecture attributes against the value stream components.
      • Use individual use cases to determine which attributes are needed for a value stream component.
      This image contains a screenshot of the table showing the importance of scalability, resiliance, performance, security, and data reliability for loan application, disbursement of funds, risk management, and service accounts.

      In our example, the prioritized list of architectural attributes are:

      • Security (4 votes for Very Important)
      • Data Reliability (2 votes for Very Important)
      • Scalability (1 vote for Very Important and 1 vote for Fairly Important) and finally
      • Resilience (1 vote for Very Important, 0 votes for Fairly Important and 1 vote for Mildly Important)
      • Performance (0 votes for Very Important, 2 votes for Fairly Important)

      1.4 Create a prioritized list of architectural attributes (from 1.3)

      1. Using the tabular structure shown on the previous slide:
      • Map each value stream component against architectural quality attributes.
      • For each mapping, indicate its importance using the green, blue, and yellow color scheme.

      Download the Solution Architecture Template and document the list of architectural attributes by priority.

      Input

      • List of Architectural Attributes From 1.3

      Output

      • Prioritized List of Architectural Attributes

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Application Architect
      • Integration Architect
      • Database Architect
      • Infrastructure Architect

      End of Phase 1

      At the end of this Phase, you should have completed the following activities:

      • Documented a set of dynamic value stream maps along with selected use cases.
      • Using the SRME framework, identified quality attributes for the system under investigation.
      • Prioritized quality attributes for system use cases.

      Phase 2: Multi-Purpose Data and Security Architecture

      Phase 1

      1.1 Articulate an Architectural Vision
      1.2 Develop Dynamic Value Stream Maps
      1.3 Map Value Streams, Use Cases, and Required Architectural Attributes
      1.4 Create a Prioritized List of Architectural Attributes

      Phase 2

      2.1 Develop a Data Architecture That Supports Transactional and Analytical Needs
      2.2 Document Security Architecture Risks and Mitigations

      Phase 3

      3.1 Document Scalability Architecture
      3.2 Document Performance Enhancing Architecture
      3.3 Combine the Different Architecture Design Decisions Into a Unified Solution Architecture

      This phase will walk you through the following activities:

      • Understand the scalability, performance, resilience, and security needs of the business.

      This phase involves the following participants:

      • Business Architect
      • Product Owner
      • Application Architect
      • Integration Architect
      • Database Architect
      • Enterprise Architect

      Enhance Your Solution Architecture Practice

      Fragmented data environments need something to sew them together

      • A full 93% of enterprises have a multi-cloud strategy, with 87% having a hybrid-cloud environment in place.
      • On average, companies have data stored in 2.2 public and 2.2 private clouds as well as in various on-premises data repositories.
      This image contains a breakdown of the cloud infrastructure, including single cloud versus multi-cloud.

      Source: Flexera

      In addition, companies are faced with:

      • Access and integration challenges (Who is sending the data? Who is getting it? Can we trust them?)
      • Data format challenges as data may differ for each consumer and sender of data
      • Infrastructure challenges as data repositories/processors are spread out over public and private clouds, are on premises, or in multi-cloud and hybrid ecosystems
      • Structured vs. unstructured data

      A robust and reliable integrated data architecture is essential for any organization that aspires to be relevant and impactful in its industry.

      Data’s context and influence on a solution’s architecture cannot be overestimated

      Data used to be the new oil. Now it’s the life force of any organization that has serious aspirations of providing profit-generating products and services to customers. Architectural decisions about managing data have a significant impact on the sustainability of a software system as well as on quality attributes such as security, scalability, performance, and availability.

      Storage and Processing go hand in hand and are the mainstay of any data architecture. Due to their central position of importance, an architecture decision for storage and processing must be well thought through or they become the bottleneck in an otherwise sound system.

      Ingestion refers to a system’s ability to accept data as an input from heterogenous sources, in different formats, and at different intervals.

      Dissemination is the set of architectural design decisions that make a system’s data accessible to external consumers. Major concerns involve security for the data in motion, authorization, data format, concurrent requests for data, etc.

      Orchestration takes care of ensuring data is current and reliable, especially for systems that are decentralized and distributed.

      Data architecture requires alignment with a hybrid data management plan

      Most companies have a combination of data. They have data they own using on-premises data sources and on the cloud. Hybrid data management also includes external data, such as social network feeds, financial data, and legal information amongst many others.

      Data integration architectures have typically been put in one of two major integration patterns:

      Application to Application Integration (or “speed matters”) Analytical Data Integrations (or “send it to me when its all done”)
      • This domain is concerned with ensuring communication between processes.
      • Examples include patterns such as Service-Oriented Architecture, REST, Event Hubs and Enterprise Service Buses.
      • This domain is focused on integrating data from transactional processes towards enterprise business intelligence. It supports activities that require well-managed data to generate evidence-based insights.
      • Examples of this pattern are ELT, enterprise data warehouses, and data marts.

      Sidebar

      Difference between real-time, batch, and streaming data movements

      Real-Time

      • Reacts to data in seconds or even quicker.
      • Real-time systems are hard to implement.

      Batch

      • Batch processing deals with a large volume of data all at once and data-related jobs are typically completed simultaneously in non-stop, sequential order.
      • Batch processing is an efficient and low-cost means of data processing.
      • Execution of batch processing jobs can be controlled manually, providing further control over how the system treats its data assets.
      • Batch processing is only useful if there are no requirements for data to be fresh and current. Real-time systems are suited to processing data that requires these attributes.

      Streaming

      • Stream processing allows almost instantaneous analysis of data as it streams from one device to another.
      • Since data is analyzed quickly, storage may not be a concern (since only computed data is stored while raw data can be dispersed).
      • Streaming requires the flow of data into the system to equal the flow of data computing, otherwise issues of data storage and performance can rise.

      Modern data ingestion and dissemination frameworks keep core data assets current and accessible

      Data ingestion and dissemination frameworks are critical for keeping enterprise data current and relevant.

      Data ingestion/dissemination frameworks capture/share data from/to multiple data sources.

      Factors to consider when designing a data ingestion/dissemination architecture

      What is the mode for data movement?

      • The mode for data movement is directly influenced by the size of data being moved and the downstream requirements for data currency.
      • Data can move in real-time, as a batch, or as a stream.

      What is the ingestion/dissemination architecture deployment strategy?

      • Outside of critical security concerns, hosting on the cloud vs. on premises leads to a lower total cost of ownership (TCO) and a higher return on investment (ROI).

      How many different and disparate data sources are sending/receiving data?

      • Stability comes if there is a good idea about the data sources/recipient and their requirements.

      What are the different formats flowing through?

      • Is the data in the form of data blocks? Is it structured, semi-unstructured, or unstructured?

      What are expected performance SLAs as data flow rate changes?

      • Data change rate is defined as the size of changes occurring every hour. It helps in selecting the appropriate tool for data movement.
      • Performance is a derivative of latency and throughput, and therefore, data on a cloud is going to have higher latency and lower throughput then if it is kept on premises.
      • What is the transfer data size? Are there any file compression and/or file splits applied on the data? What is the average and maximum size of a block object per ingestion/dissemination operation?

      What are the security requirements for the data being stored?

      • The ingestion/dissemination framework should be able to work through a secure tunnel to collect/share data if needed.

      Sensible storage and processing strategy can improve performance and scalability and be cost-effective

      The range of options for data storage is staggering...

      … but that’s a good thing because the range of data formats that organizations must deal with is also richer than in the past.

      Different strokes for different workloads.

      The data processing tool to use may depend upon the workloads the system has to manage.

      Expanding upon the Risk Management use case (as part of the Loan Provision Capability), one of the outputs for risk assessment is a report that conducts a statistical analysis of customer profiles and separates those that are possibly risky. The data for this report is spread out across different data systems and will need to be collected in a master data management storage location. The business and data architecture team have discussed three critical system needs, noted below:

      Data Management Requirements for Risk Management Reporting Data Design Decision
      Needs to query millions of relational records quickly
      • Strong indexing
      • Strong caching
      • Message queue
      Needs a storage space for later retrieval of relational data
      • Data storage that scales as needed
      Needs turnkey geo-replication mechanism with document retrieval in milliseconds
      • Add NoSQL with geo-replication and quick document access

      Keep every core data source on the same page through orchestration

      Data orchestration, at its simplest, is the combination of data integration, data processing, and data concurrency management.

      Data pipeline orchestration is a cross-cutting process that manages the dependencies between your data integration tasks and scheduled data jobs.

      A task or application may periodically fail, and therefore, as a part of our data architecture strategy, there must be provisions for scheduling, rescheduling, replaying, monitoring, retrying, and debugging the entire data pipeline in a holistic way.

      Some of the functionality provided by orchestration frameworks are:

      • Job scheduling
      • Job parametrization
      • SLAs tracking, alerting, and notification
      • Dependency management
      • Error management and retries
      • History and audit
      • Data storage for metadata
      • Log aggregation
      Data Orchestration Has Three Stages
      Organize Transform Publicize
      Organizations may have legacy data that needs to be combined with new data. It’s important for the orchestration tool to understand the data it deals with. Transform the data from different sources into one standard type. Make transformed data easily accessible to stakeholders.

      2.1 Discuss and document data architecture decisions

      1. Using the value maps and associated use cases from Phase 1, determine the data system quality attributes.
      2. Use the sample tabular layout on the next slide or develop one of your own.

      Download the Solution Architecture Template for documenting data architecture decisions.

      Input

      • Value Maps and Use Cases

      Output

      • Initial Set of Data Design Decisions

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Application Architect
      • Integration Architect
      • Database Architect
      • Infrastructure Architect

      Example: Data Architecture

      Data Management Requirements for Risk Management Reporting Data Design Decision
      Needs to query millions of relational records quickly
      • Strong indexing
      • Strong caching
      • Message queue
      Needs a storage space for later retrieval of relational data
      • Data storage that scales as needed
      Needs turnkey geo-replication mechanism with document retrieval in milliseconds
      • Add NoSQL with geo-replication and quick document access

      There is no free lunch when making the most sensible security architecture decision; tradeoffs are a necessity

      Ensuring that any real system is secure is a complex process involving tradeoffs against other important quality attributes (such as performance and usability). When architecting a system, we must understand:

      • Its security needs.
      • Its security threat landscape.
      • Known mitigations for those threats to ensure that we create a system with sound security fundamentals.

      The first thing to do when determining security architecture is to conduct a threat and risk assessment (TRA).

      This image contains a sample threat and risk assessment. The steps are Understand: Until we thoroughly understand what we are building, we cannot secure it. Structure what you are building, including: System boundary, System structure, Databases, Deployment platform; Analyze: Use techniques like STRIDE and attack trees to analyze what can go wrong and what security problems this will cause; Mitigate: The security technologies to use, to mitigate your concerns, are discussed here. Decisions about using single sign-on (SSO) or role-based access control (RBAC), encryption, digital signatures, or JWT tokens are made. An important part of this step is to consider tradeoffs when implementing security mechanisms; validate: Validation can be done by experimenting with proposed mitigations, peer discussion, or expert interviews.

      Related Research

      Optimize Security Mitigation Effectiveness Using STRIDE

      • Have a clear picture of:
        • Critical data and data flows
        • Organizational threat exposure
        • Security countermeasure deployment and coverage
      • Understand which threats are appropriately mitigated and which are not.
      • Generate a list of initiatives to close security gaps.
      • Create a quantified risk and security model to reassess program and track improvement.
      • Develop measurable information to present to stakeholders.

      The 3A’s of strong security: authentication, authorization, and auditing

      Authentication

      Authentication mechanisms help systems verify that a user is who they claim to be.

      Examples of authentication mechanisms are:

      • Two-Factor Authentication
      • Single Sign-On
      • Multi-Factor Authentication
      • JWT Over OAUTH

      Authorization

      Authorization helps systems limit access to allowed features, once a user has been authenticated.

      Examples of authentication mechanisms are:

      • RBAC
      • Certificate Based
      • Token Based

      Auditing

      Securely recording security events through auditing proves that our security mechanisms are working as intended.

      Auditing is a function where security teams must collaborate with software engineers early and often to ensure the right kind of audit logs are being captured and recorded.

      Info-Tech Insight

      Defects in your application software can compromise privacy and integrity even if cryptographic controls are in place. A security architecture made after thorough TRA does not override security risk introduced due to irresponsible software design.

      Examples of threat and risk assessments using STRIDE and attack trees

      STRIDE is a threat modeling framework and is composed of:

      • Spoofing or impersonation of someone other than oneself
      • Tampering with data and destroying its integrity
      • Repudiation by bypassing system identity controls
      • Information disclosure to unauthorized persons
      • Denial of service that prevents system or parts of it from being used
      • Elevation of privilege so that attackers get rights they should not have
      Example of using STRIDE for a TRA on a solution using a payment system This image contains a sample attack tree.
      Spoofing PayPal Bad actor can send fraudulent payment request for obtaining funds.
      Tampering PayPal Bad actor accesses data base and can resend fraudulent payment request for obtaining funds.
      Repudiation PayPal Customer claims, incorrectly, their account made a payment they did not authorize.
      Disclosure PayPal Private service database has details leaked and made public.
      Denial of Service PayPal Service is made to slow down through creating a load on the network, causing massive build up of requests
      Elevation of Privilege PayPal Bad actor attempts to enter someone else’s account by entering incorrect password a number of times.

      2.2 Document security architecture risks and mitigations

      1. Using STRIDE, attack tree, or any other framework of choice:
      • Conduct a TRA for use cases identified in Phase 1.2
    • For each threat identified through the TRA, think through the implications of using authentication, authorization, and auditing as a security mechanism.
    • Download the Solution Architecture Template for documenting data architecture decisions.

      Input

      • Dynamic Value Stream Maps

      Output

      • Security Architecture Risks and Mitigations

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Product Owner
      • Security Team
      • Application Architect
      • Integration Architect

      Examples of threat and risk assessments using STRIDE

      Example of using STRIDE for a TRA on a solution using a payment system
      Threat System Component Description Quality Attribute Impacted Resolution
      Spoofing PayPal Bad actor can send fraudulent payment request for obtaining funds. Confidentiality Authorization
      Tampering PayPal Bad actor accesses data base and can resend fraudulent payment request for obtaining funds. Integrity Authorization
      Repudiation PayPal Customer claims, incorrectly, their account made a payment they did not authorize. Integrity Authentication and Logging
      Disclosure PayPal Private service database has details leaked and made public. Confidentiality Authorization
      Denial of Service PayPal Service is made to slow down through creating a load on the network, causing massive build up of requests Availability N/A
      Elevation of Privilege PayPal Bad actor attempts to enter someone else’s account by entering incorrect password a number of times. Confidentiality, Integrity, and Availability Authorization

      Phase 3: Upgrade Your System’s Availability

      Phase 1

      1.1 Articulate an Architectural Vision
      1.2 Develop Dynamic Value Stream Maps
      1.3 Map Value Streams, Use Cases, and Required Architectural Attributes
      1.4 Create a Prioritized List of Architectural Attributes

      Phase 2

      2.1 Develop a Data Architecture That Supports Transactional and Analytical Needs
      2.2 Document Security Architecture Risks and Mitigations

      Phase 3

      3.1 Document Scalability Architecture
      3.2 Document Performance Enhancing Architecture
      3.3 Combine the Different Architecture Design Decisions Into a Unified Solution Architecture

      This phase will walk you through the following activities:

      • Examine architecture for scalable and performant system designs
      • Integrate all design decisions made so far into a solution design decision log

      This phase involves the following participants:

      • Business Architect
      • Product Owner
      • Application Architect
      • Integration Architect
      • Database Architect
      • Enterprise Architect

      Enhance Your Solution Architecture Practice

      In a cloud-inspired system architecture, scalability takes center stage as an architectural concern

      Scale and scope of workloads are more important now than they were, perhaps, a decade and half back. Architects realize that scalability is not an afterthought. Not dealing with it at the outset can have serious consequences should an application workload suddenly exceed expectations.

      Scalability is …

      … the ability of a system to handle varying workloads by either increasing or decreasing the computing resources of the system.

      An increased workload could include:

      • Higher transaction volumes
      • A greater number of users

      Architecting for scalability is …

      … not easy since organizations may not be able to accurately judge, outside of known circumstances, when and why workloads may unexpectedly increase.

      A scalable architecture should be planned at the:

      • Application Level
      • Infrastructure Level
      • Database Level

      The right amount and kind of scalability is …

      … balancing the demands of the system with the supply of attributes.

      If demand from system > supply from system:

      • Services and products are not useable and deny value to customers.

      If supply from system > demand from system:

      • Excess resources have been paid for that are not being used.

      When discussing the scalability needs of a system, investigate the following, at a minimum:

      • In case workloads increase due to higher transaction volumes, will the system be able to cope with the additional stress?
      • In situations where workloads increase, will the system be able to support the additional stress without any major modifications being made to the system?
      • Is the cost associated with handling the increased workloads reasonable for the benefit it provides to the business?
      • Assuming the system doesn’t scale, is there any mechanism for graceful degradation?

      Use evidence-based decision making to ensure a cost-effective yet appropriate scaling strategy

      The best input for an effective scaling strategy is previously gathered traffic data mapped to specific circumstances.

      In some cases, either due to lack of monitoring or the business not being sure of its needs, scalability requirements are hard to determine. In such cases, use stated tactical business objectives to design for scalability. For example, the business might state its desire to achieve a target revenue goal. To accommodate this, a certain number of transactions would need to be conducted, assuming a particular conversion rate.

      Scaling strategies can be based on Vertical or Horizontal expansion of resources.
      Pros Cons
      Vertical
      Scale up through use of more powerful but limited number of resources
      • May not require frequent upgrades.
      • Since data is managed through a limited number of resources, it is easier to share and keep current.
      • Costly upfront.
      • Application, database, and infrastructure may not be able to make optimal use of extra processing power.
      • As the new, more powerful resource is provisioned, systems may experience downtime.
      • Lacks redundancy due to limited points of failure.
      • Performance is constrained by the upper limits of the infrastructure involved.
      Horizontal
      Scale out through use of similarly powered but larger quantity of resources
      • Cost-effective upfront.
      • System downtime is minimal, when scaling is being performed.
      • More redundance and fault-tolerance is possible since there are many nodes involved, and therefore, can replace failed nodes.
      • Performance can scale out as more nodes are added.
      • Upgrades may occur more often than in vertical scaling.
      • Increases machine footprints and administrative costs over time.
      • Data may be partitioned on multiple nodes, leading to administrative and data currency challenges.

      Info-Tech Insight

      • Scalability is the one attribute that sparks a lot of trade-off discussions. Scalable solutions may have to compromise on performance, cost, and data reliability.
      • Horizontal scalability is mostly always preferable over vertical scalability.

      Sidebar

      The many flavors of horizontal scaling

      Traffic Shard-ing

      Through this mechanism, incoming traffic is partitioned around a characteristic of the workload flowing in. Examples of partitioning characteristics are user groups, geo-location, and transaction type.

      Beware of:

      • Lack of data currency across shards.

      Copy and Paste

      As the name suggests, clone the compute resources along with the underlying databases. The systems will use a load balancer as the first point of contact between itself and the workload flowing in.

      Beware of:

      • Though this is a highly scalable model, it does introduce risks related to data currency across all databases.
      • In case master database writes are frequent, it could become a bottleneck for the entire system.

      Productization Through Containers

      This involves breaking up the system into specific functions and services and bundling their business rules/databases into deployable containers.

      Beware of:

      • Too many containers introduce the need to orchestrate the distributed architecture that results from a service-oriented approach.

      Start a scalability overview with a look at the database(s)

      To know where to go, you must know where you are. Before introducing architectural changes to database designs, use the right metrics to get an insight into the root cause of the problem(s).

      In a nutshell, the purpose of scaling solutions is to have the technology stack do less work for the most requested services/features or be able to effectively distribute the additional workload across multiple resources.

      For databases, to ensure this happens, consider these techniques:

      • Reuse data through caching on the server and/or the client. This eliminates the need for looking up already accessed data. Examples of caching are:
        • In-memory caching of data
        • Caching database queries
      • Implement good data retrieval techniques like indexes.
      • Divide labor at the database level.
        • Through setting up primary-secondary distribution of data. In such a setup, the primary node is involved in writing data to itself and passes on requests to secondary nodes for fulfillment.
        • Through setting up database shards (either horizontally or vertically).
          • In a horizontal shard, a data table is broken into smaller pieces with the same data model but unique data in it. The sum total of the shared databases contains all the data in the primary data table.
          • In a vertical shard, a data table is broken into smaller pieces, but each piece may have a subset of the data columns. The data’s corresponding columns are put into the table where the column resides.

      Info-Tech Insight

      A non-scalable architecture has more than just technology-related ramifications. Hoping that load balancers or cloud services will manage scalability-related issues is bound to have economic impacts as well.

      Sidebar

      Caching Options

      CSA PRINCIPLE 5 applies to any decision that supports system scalability.
      “X-ilities Over Features”

      Database Caching
      Fetches and stores result of database queries in memory. Subsequent requests to the database for the same queries will investigate the cache before making a connection with the database.
      Tools like Memcached or Redis are used for database caching.

      Precompute Database Caching
      Unlike database caching, this style of caching precomputes results of queries that are popular and frequently used. For example, a database trigger could execute several predetermined queries and have them ready for consumption. The precomputed results may be stored in a database cache.

      Application Object Caching
      Stores computed results in a cache for later retrieval. For data sources, which are not changing frequently and are part of a computation output, application caching will remove the need to connect with a database.

      Proxy Caching
      Caches retrieved web pages on a proxy server and makes them available for the next time the page is requested.

      The intra- and inter-process communication of the systems middle tier can become a bottleneck

      To synchronize or not to synchronize?

      A synchronous request (doing one thing at a time) means that code execution will wait for the request to be responded to before continuing.

      • A synchronous request is a blocking event and until it is completed, all following requests will have to wait for getting their responses.
      • An increasing workload on a synchronous system may impact performance.
      • Synchronous interactions are less costly in terms of design, implementation, and maintenance.
      • Scaling options include:
      1. Vertical scale up
      2. Horizontal scale out of application servers behind a load balancer and a caching technique (to minimize data retrieval roundtrips)
      3. Horizonal scale out of database servers with data partitioning and/or data caching technique

      Use synchronous requests when…

      • Each request to a system sets the necessary precondition for a following request.
      • Data reliability is important, especially in real-time systems.
      • System flows are simple.
      • Tasks that are typically time consuming, such as I/O, data access, pre-loading of assets, are completed quickly.

      Asynchronous requests (doing many things at the same time) do not block the system they are targeting.

      • It is a “fire and forget” mechanism.
      • Execution on a server/processor is triggered by the request, however, additional technical components (callbacks) for checking the state of the execution must be designed and implemented.
      • Asynchronous interactions require additional time to be spent on implementation and testing.
      • With asynchronous interactions, there is no guarantee the request initiated any processing until the callbacks check the status of the executed thread.

      Use asynchronous requests when…

      • Tasks are independent in nature and don’t require inter-task communication.
      • Systems flows need to be efficient.
      • The system is using event-driven techniques for processing.
      • Many I/O tasks are involved.
      • The tasks are long running.

      Sidebar

      Other architectural tactics for inter-process communication

      STATELESS SERVICES VERSUS STATEFUL SERVICES
      • Does not require any additional data, apart from the bits sent through with the request.
      • Without implementing a caching solution, it is impossible to access the previous data trail for a transaction session.
      • In addition to the data sent through with the request, require previous data sent to complete processing.
      • Requires server memory to store the additional state data. With increasing workloads, this could start impacting the server’s performance.
      It is generally accepted that stateless services are better for system scalability, especially if vertical scaling is costly and there is expectation that workloads will increase.
      MICROSERVICES VERSUS SERVERLESS FUNCTIONS
      • Services are designed as small units of code with a single responsibility and are available on demand.
      • A microservices architecture is easily scaled horizontally by adding a load balancer and a caching mechanism.
      • Like microservices, these are small pieces of code designed to fulfill a single purpose.
      • Are provided only through cloud vendors, and therefore, there is no need to worry about provisioning of infrastructure as needs increase.
      • Stateless by design but the life cycle of a serverless function is vendor controlled.
      Serverless function is an evolving technology and tightly controlled by the vendor. As and when vendors make changes to their serverless products, your own systems may need to be modified to make the best use of these upgrades.

      A team that does not measure their system’s scalability is a team bound to get a 5xx HTTP response code

      A critical aspect of any system is its ability to monitor and report on its operational outcomes.

      • Using the principle of continuous testing, every time an architectural change is introduced, a thorough load and stress testing cycle should be executed.
      • Effective logging and use of insightful metrics helps system design teams make data-driven decisions.
      • Using principle of site reliability engineering and predictive analytics, teams can be prepared for any unplanned exaggerated stimulus on the system and proactively set up remedial steps.

      Any system, however well architected, will break one day. Strategically place kill-switches to counter any failures and thoroughly test their functioning before releasing to production.

      • Using Principles 2 and 9 of the CSA, (include kill-switches and architect for x-ilities over features), introduce tactics at the code and higher levels that can be used to put a system in its previous best state in case of failure.
      • Examples of such tactics are:
        • Feature flags for turning on/off code modules that impact x-ilities.
        • Implement design patterns like throttling, autoscaling, and circuit breaking.
        • Writing extensive log messages that bubble up as exceptions/error handling from the code base. *Logging can be a performance drag. Use with caution as even logging code is still code that needs CPU and data storage.

      Performance is a system’s ability to satisfy time-bound expectations

      Performance can also be defined as the ability for a system to achieve its timing requirements, using available resources, under expected full-peak load:

      (International Organization for Standardization, 2011)

      • Performance and scalability are two peas in a pod. They are related to each other but are distinct attributes. Where scalability refers to the ability of a system to initiate multiple simultaneous processes, performance is the system’s ability to complete the processes within a mandated average time period.
      • Degrading performance is one of the first red flags about a system’s ability to scale up to workload demands.
      • Mitigation tactics for performance are very similar to the tactics for scalability.

      System performance needs to be monitored and measured consistently.

      Measurement Category 1: System performance in terms of end-user experience during different load scenarios.

      • Response time/latency: Length of time it takes for an interaction with the system to complete.
      • Turnaround time: Time taken to complete a batch of tasks.
      • Throughput: Amount of workload a system is capable of handling in a unit time period.

      Measurement Category 2: System performance in terms of load managed by computational resources.

      • Resource utilization: The average usage of a resource (like CPU) over a period. Peaks and troughs indicate excess vs. normal load times.
      • Number of concurrent connections: Simultaneous user requests that a resource like a server can successfully deal with at once.
      • Queue time: The turnaround time for a specific interaction or category of interactions to complete.

      Architectural tactics for performance management are the same as those used for system scalability

      Application Layer

      • Using a balanced approach that combines CSA Principle 7 (Good architecture comes in small packages) and Principle 10 (Architect for products, not projects), a microservices architecture based on domain-driven design helps process performance. Microservices use lightweight HTTP protocols and have loose coupling, adding a degree of resilience to the system as well. *An overly-engineered microservices architecture can become an orchestration challenge.
      • The code design must follow standards that support performance. Example of standards is SOLID*.
      • Serverless architectures can run application code from anywhere – for example, from edge servers close to an end user – thereby reducing latency.

      Database Layer

      • Using the right database technologies for persistence. Relational databases have implicit performance bottlenecks (which get exaggerated as data size grows along with indexes), and document store database technologies (key-value or wide-column) can improve performance in high-read environments.
      • Data sources, especially those that are frequently accessed, should ideally be located close to the application servers. Hybrid infrastructures (cloud and on premises mixed) can lead to latency when a cloud-application is accessing on-premises data.
      • Using a data partitioning strategy, especially in a domain-driven design architecture, can improve the performance of a system.

      Performance modeling and continuous testing makes the SRE a happy engineer

      Performance modeling and testing helps architecture teams predict performance risks as the solution is being developed.
      (CSA Principle 12: Test the solution architecture like you test your solution’s features)

      Create a model for your system’s hypothetical performance testing by breaking an end-to-end process or use case into its components. *Use the SIPOC framework for decomposition.

      This image contains an example of modeled performance, showing the latency in the data flowing from different data sources to the processing of the data.

      In the hypothetical example of modeled performance above:

      • The longest period of latency is 15ms.
      • The processing of data takes 30ms, while the baseline was established at 25ms.
      • Average latency in sending back user responses is 21ms – 13ms slower than expected.

      The model helps architects:

      • Get evidence for their assumptions
      • Quantitatively isolate bottlenecks at a granular level

      Model the performance flow once but test it periodically

      Performance testing measures the performance of a software system under normal and abnormal loads.

      Performance testing process should be fully integrated with software development activities and as automated as possible. In a fast-moving Agile environment, teams should attempt to:

      • Shift-left performance testing activities.
      • Use performance testing to pinpoint performance bottlenecks.
      • Take corrective action, as quickly as possible.

      Performance testing techniques

      • Normal load testing: Verifies the system’s behavior under the expected normal load to ensure that its performance requirements are met. Load testing can be used to measure response time, responsiveness, turnaround time, and throughput.
      • Expected maximum load testing: Like the normal load testing process, ensures system meets its performance requirements under expected maximum load.
      • Stress testing: Evaluates system behavior when processing loads beyond the expected maximum.

      *In a real production scenario, a combination of these tests are executed on a regular basis to monitor the performance of the system over a given period.

      3.1-3.2 Discuss and document initial decisions made for architecture scalability and performance

      1. Use the outcomes from either or both Phases 1.3 and 1.4.
      • For each value stream component, list the architecture decisions taken to ensure scalability and performance at client-facing and/or business-rule layers.

      Download the Solution Architecture Template for documenting data architecture decisions.

      Input

      • Output From Phase 1.3 and/or From Phase 1.4

      Output

      • Initial Set of Design Decisions Made for System Scalability and Performance

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Application Architect
      • Integration Architect
      • Database Architect
      • Infrastructure Architect

      Example: Architecture decisions for scalability and performance

      Value Stream Component Design Decision for User Interface Layer Design Decisions for Middle Processing Layer
      Loan Application Scalability: N/A
      Resilience: Include circuit breaker design in both mobile app and responsive websites.
      Performance: Cache data client.
      Scalability: Scale vertically (up) since loan application processing is very compute intensive.
      Resilience: Set up fail-over replica.
      Performance: Keep servers in the same geo-area.
      Disbursement of Funds *Does not have a user interface Scalability: Scale horizontal when traffic reaches X requests/second.
      Resilience: Create microservices using domain-driven design; include circuit breakers.
      Performance: Set up application cache; synchronous communication since order of data input is important.
      …. …. ….

      3.3 Combine the different architecture design decisions into a unified solution architecture

      Download the Solution Architecture Template for documenting data architecture decisions.

      Input

      • Output From Phase 1.3 and/or From Phase 1.4
      • Output From Phase 2.1
      • Output From Phase 2.2
      • Output From 3.1 and 3.2

      Output

      • List of Design Decisions for the Solution

      Materials

      • Whiteboard/Flip Charts

      Participants

      • Business Architect
      • Application Architect
      • Integration Architect
      • Database Architect
      • Infrastructure Architect

      Putting it all together is the bow that finally ties this gift

      This blueprint covered the domains tagged with the yellow star.

      This image contains a screenshot of the solution architecture framework found earlier in this blueprint, with stars next to Data Architecture, Security, Performance, and Stability.

      TRADEOFF ALERT

      The right design decision is never the same for all perspectives. Along with varying opinions, comes the “at odds with each other set” of needs (scalability vs. performance, or access vs. security).

      An evidence-based decision-making approach using a domain-driven design strategy is a good mix of techniques for creating the best (right?) solution architecture.

      This image contains a screenshot of a table that summarizes the themes discussed in this blueprint.

      Summary of accomplishment

      • Gained understanding and clarification of the stakeholder objectives placed on your application architecture.
      • Completed detailed use cases and persona-driven scenario analysis and their architectural needs through SRME.
      • Created a set of design decisions for data, security, scalability, and performance.
      • Merged the different architecture domains dealt with in this blueprint to create a holistic view.

      Bibliography

      Ambysoft Inc. “UML 2 Sequence Diagrams: An Agile Introduction.” Agile Modeling, n.d. Web.

      Bass, Len, Paul Clements, and Rick Kazman. Software Architecture in Practices: Third Edition. Pearson Education, Inc. 2003.

      Eeles, Peter. “The benefits of software architecting.” IBM: developerWorks, 15 May 2006. Web.

      Flexera 2020 State of the Cloud Report. Flexera, 2020. Web. 19 October 2021.

      Furdik, Karol, Gabriel Lukac, Tomas Sabol, and Peter Kostelnik. “The Network Architecture Designed for an Adaptable IoT-based Smart Office Solution.” International Journal of Computer Networks and Communications Security, November 2013. Web.

      Ganzinger, Matthias, and Petra Knaup. “Requirements for data integration platforms in biomedical research networks: a reference model.” PeerJ, 5 February 2015. (https://peerj.com/articles/755/).

      Garlan, David, and Mary Shaw. An Introduction to Software Architecture. CMU-CS-94-166, School of Computer Science Carnegie Mellon University, January 1994.

      Gupta, Arun. “Microservice Design Patterns.” Java Code Geeks, 14 April 2015. Web.

      How, Matt. The Modern Data Warehouse in Azure. O’Reilly, 2020.

      ISO/IEC 17788:2014: Information technology – Cloud computing, International Organization for Standardization, October 2014. Web.

      ISO/IEC 18384-1:2016: Information technology – Reference Architecture for Service Oriented Architecture (SOA RA), International Organization for Standardization, June 2016. Web.

      ISO/IEC 25010:2011(en) Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models. International Organization for Standardization, March 2011. Web.

      Kazman, R., M. Klein, and P. Clements. ATAM: Method for Architecture Evaluation. S Carnegie Mellon University, August 2000. Web.

      Microsoft Developer Network. “Chapter 16: Quality Attributes.” Microsoft Application Architecture Guide. 2nd Ed., 13 January 2010. Web.

      Microsoft Developer Network. “Chapter 2: Key Principles of Software Architecture.” Microsoft Application Architecture Guide. 2nd Ed., 13 January 2010. Web.

      Microsoft Developer Network. “Chapter 3: Architectural Patterns and Styles.” Microsoft Application Architecture Guide. 2nd Ed., 14 January 2010. Web.

      Microsoft Developer Network. “Chapter 5: Layered Application Guidelines.” Microsoft Application Architecture Guide. 2nd Ed., 13 January 2010. Web.

      Mirakhorli, Mehdi. “Common Architecture Weakness Enumeration (CAWE).” IEEE Software, 2016. Web.

      Moore, G. A. Crossing the Chasm, 3rd Edition: Marketing and Selling Disruptive Products to Mainstream Customers (Collins Business Essentials) (3rd ed.). Harper Business, 2014.

      OASIS. “Oasis SOA Reference Model (SOA RM) TC.” OASIS Open, n.d. Web.

      Soni, Mukesh. “Defect Prevention: Reducing Costs and Enhancing Quality.” iSixSigma, n.d. Web.

      The Open Group. TOGAF 8.1.1 Online, Part IV: Resource Base, Developing Architecture Views. TOGAF, 2006. Web.

      The Open Group. Welcome to the TOGAF® Standard, Version 9.2, a standard of The Open Group. TOGAF, 2018. Web.

      Watts, S. “The importance of solid design principles.” BMC Blogs, 15 June 2020. 19 October 2021.

      Young, Charles. “Hexagonal Architecture–The Great Reconciler?” Geeks with Blogs, 20 Dec 2014. Web.

      APPENDIX A

      Techniques to enhance application architecture.

      Consider the numerous solutions to address architecture issues or how they will impact your application architecture

      Many solutions exist for improving the layers of the application stack that may address architecture issues or impact your current architecture. Solutions range from capability changes to full stack replacement.

      Method Description Potential Benefits Risks Related Blueprints
      Business Capabilities:
      Enablement and enhancement
      • Introduce new business capabilities by leveraging unused application functionalities or consolidate redundant business capabilities.
      • Increase value delivery to stakeholders.
      • Lower IT costs through elimination of applications.
      • Increased use of an application could overload current infrastructure.
      • IT cannot authorize business capability changes.
      Use Info-Tech’s Document Your Business Architecture blueprint to gain better understanding of business and IT alignment.
      Removal
      • Remove existing business capabilities that don’t contribute value to the business.
      • Lower operational costs through elimination of unused and irrelevant capabilities.
      • Business capabilities may be seen as relevant or critical by different stakeholder groups.
      • IT cannot authorize business capability changes.
      Use Info-Tech’s Build an Application Rationalization Framework to rationalize your application portfolio.
      Business Process:
      Process integration and consolidation
      • Combine multiple business processes into a single process.
      • Improved utilization of applications in each step of the process.
      • Reduce business costs through efficient business processes.
      • Minimize number of applications required to execute a single process.
      • Significant business disruption if an application goes down and is the primary support for business processes.
      • Organizational pushback if process integration involves multiple business groups.
      Business Process (continued):
      Process automation
      • Automate manual business processing tasks.
      • Reduce manual processing errors.
      • Improve speed of delivery.
      • Significant costs to implement automation.
      • Automation payoffs are not immediate.
      Lean business processes
      • Eliminate redundant steps.
      • Streamline existing processes by focusing on value-driven steps.
      • Improve efficiency of business process through removal of wasteful steps.
      • Increase value delivered at the end of the process.
      • Stakeholder pushback from consistently changing processes.
      • Investment from business is required to fit documentation to the process.
      Outsource the process
      • Outsource a portion of or the entire business process to a third party.
      • Leverage unavailable resources and skills to execute the business process.
      • Loss of control over process.
      • Can be costly to bring the process back into the business if desired in the future.
      Business Process (continued):
      Standardization
      • Implement standards for business processes to improve uniformity and reusability.
      • Consistently apply the same process across multiple business units.
      • Transparency of what is expected from the process.
      • Improve predictability of process execution.
      • Process bottlenecks may occur if a single group is required to sign off on deliverables.
      • Lack of enforcement and maintenance of standards can lead to chaos if left unchecked.
      User Interface:
      Improve user experience (UX)
      • Eliminate end-user emotional, mechanical, and functional friction by improving the experience of using the application.
      • UX encompasses both the interface and the user’s behavior.
      • Increase satisfaction and adoption rate from end users.
      • Increase brand awareness and user retention.
      • UX optimizations are only focused on a few user personas.
      • Current development processes do not accommodate UX assessments
      Code:
      Update coding language
      Translate legacy code into modern coding language.
      • Coding errors in modern languages can have lesser impact on the business processes they support.
      • Modern languages tend to have larger pools of coders to hire.
      • Increase availability of tools to support modern languages.
      • Coding language changes can create incompatibilities with existing infrastructure.
      • Existing coding translation tools do not offer 100% guarantee of legacy function retention.
      Code (continued):
      Open source code
      • Download pre-built code freely available in open source communities.
      • Code is rapidly evolving in the community to meet current business needs.
      • Avoid vendor lock-in from proprietary software
      • Community rules may require divulgence of work done with open source code.
      • Support is primarily provided through community, which may not address specific concerns.
      Update the development toolchain
      • Acquire new or optimize development tools with increased testing, build, and deployment capabilities.
      • Increase developer productivity.
      • Increase speed of delivery and test coverage with automation.
      • Drastic IT overhauls required to implement new tools such as code conversion, data migration, and development process revisions.
      Update source code management
      • Optimize source code management to improve coding governance, versioning, and development collaboration.
      • Ability to easily roll back to previous build versions and promote code to other environments.
      • Enable multi-user development capabilities.
      • Improve conflict management.
      • Some source code management tools cannot support legacy code.
      • Source code management tools may be incompatible with existing development toolchain.
      Data:
      Outsource extraction
      • Outsource your data analysis and extraction to a third party.
      • Lower costs to extract and mine data.
      • Leverage unavailable resources and skills to translate mined data to a usable form.
      • Data security risks associated with off-location storage.
      • Data access and control risks associated with a third party.
      Update data structure
      • Update your data elements, types (e.g. transactional, big data), and formats (e.g. table columns).
      • Standardize on a common data definition throughout the entire organization.
      • Ease data cleansing, mining, analysis, extraction, and management activities.
      • New data structures may be incompatible with other applications.
      • Implementing data management improvements may be costly and difficult to acquire stakeholder buy-in.
      Update data mining and data warehousing tools
      • Optimize how data is extracted and stored.
      • Increase the speed and reliability of the data mined.
      • Perform complex analysis with modern data mining and data warehousing tools.
      • Data warehouses are regularly updated with the latest data.
      • Updating data mining and warehousing tools may create incompatibilities with existing infrastructure and data sets.
      Integration:
      Move from point-to-point to enterprise service bus (ESB)
      • Change your application integration approach from point-to-point to an ESB.
      • Increase the scalability of enterprise services by exposing applications to a centralized middleware.
      • Reduce the number of integration tests to complete with an ESB.
      • Single point of failure can cripple the entire system.
      • Security threats arising from centralized communication node.
      Leverage API integration
      • Leverage application programming interfaces (APIs) to integrate applications.
      • Quicker and more frequent transfers of lightweight data compared to extract, load, transfer (ETL) practices.
      • Increase integration opportunities with other modern applications and infrastructure (including mobile devices).
      • APIs are not as efficient as ETL when handling large data sets.
      • Changing APIs can break compatibility between applications if not versioned properly.

      Cybersecurity Priorities in Times of Pandemic

      • Buy Link or Shortcode: {j2store}381|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 Processes & Operations
      • Parent Category Link: /security-processes-and-operations
      • Novel coronavirus 2019 (COVID-19) has thrown organizations around the globe into chaos as they attempt to continue operations while keeping employees safe.
      • IT needs to support business continuity – juggling available capacity and ensuring that services are available to end users – without clarity of duration, amid conditions that change daily, on a scale never seen before.
      • Security has never been more important than now. But…where to start? What are the top priorities? How do we support remote work while remaining secure?

      Our Advice

      Critical Insight

      • There is intense pressure to enable employees to work remotely, as soon as possible. IT is scrambling to enable access, source equipment to stage, and deploy products to employees, many of whom are unfamiliar with working from home.
      • There is either too much security to allow people to be productive or too little security to ensure that the organization remains protected and secure.
      • These events are unprecedented, and no plan currently exists to sufficiently maintain a viable security posture during this interim new normal.

      Impact and Result

      • Don’t start from scratch. Leverage your current security framework, processes, and mechanisms but tailor them to accommodate the new way of remote working.
      • Address priority security items related to remote work capability and its implications in a logical sequence. Some security components may not be as time sensitive as others.
      • Remain diligent! Circumstances may have changed, but the importance of security has not. In fact, IT security is likely more important now than ever before.

      Cybersecurity Priorities in Times of Pandemic Research & Tools

      Start here – read our Cybersecurity Priorities research.

      Our recommendations and the accompanying checklist tool will help you quickly get a handle on supporting a remote workforce while maintaining security in your organization.

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

      • Cybersecurity Priorities in Times of Pandemic Storyboard
      • Cybersecurity Priorities Checklist Tool
      [infographic]

      AI Trends 2023

      • Buy Link or Shortcode: {j2store}207|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

      As AI technologies are constantly evolving, organizations are looking for AI trends and research developments to understand the future applications of AI in their industries.

      Our Advice

      Critical Insight

      • Understanding trends and the focus of current and future AI research helps to define how AI will drive an organization’s new strategic opportunities.
      • Understanding the potential application of AI and its promise can help plan the future investments in AI-powered technologies and systems.

      Impact and Result

      Understanding AI trends and developments enables an organization’s competitive advantage.

      AI Trends 2023 Research & Tools

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

      1. AI Trends 2023 – An overview of trends that will continue to drive AI innovation.

      • AI Trends Report 2023
      [infographic]

      Further reading

      AI Trends Report 2023

      The eight trends:

      1. Design for AI
      2. Event-Based Insights
      3. Synthetic Data
      4. Edge AI
      5. AI in Science and Engineering
      6. AI Reasoning
      7. Digital Twin
      8. Combinatorial Optimization
      Challenges that slowed the adoption of AI

      To overcome the challenges, enterprises adopted different strategies

      Data Readiness

      • Lack of unified systems and unified data
      • Data quality issues
      • Lack of the right data required for machine learning
      • Improve data management capabilities, including data governance and data initiatives
      • Create data catalogs
      • Document data and information architecture
      • Solve data-related problems including data quality, privacy, and ethics

      ML Operations Capabilities

      • Lack of tools, technologies, and methodologies to operationalize models created by data scientists
      • Increase availability of cloud platforms, tools, and capabilities
      • Develop and grow machine learning operations (MLOps) tools, platforms, and methodologies to enable model operationalizing and monitoring in production

      Understanding of AI Role and Its Business Value

      • Lack of understanding of AI use cases – how AI/ML can be applied to solve specific business problems
      • Lack of understanding how to define the business value of AI investments
      • Identify AI C-suite toolkits (for example, Empowering AI Leadership from the World Economic Forum, 2022)
      • Document industry use cases
      • Use frameworks and tools to define business value for AI investments

      Design for AI

      Sustainable AI system design needs to consider several aspects: the business application of the system, data, software and hardware, governance, privacy, and security.

      It is important to define from the beginning how AI will be used by and for the application to clearly articulate business value, manage expectations, and set goals for the implementation.

      Design for AI will change how we store and manage data and how we approach the use of data for development and operation of AI systems.

      An AI system design approach should cover all stages of AI lifecycle, from design to maintenance. It should also support and enable iterative development of an AI system.

      To take advantage of different tools and technologies for AI system development, deployment, and monitoring, the design of an AI system should consider software and hardware needs and design for seamless and efficient integrations of all components of the system and with other existing systems within the enterprise.

      AI in Science and Engineering

      AI helps sequence genomes to identify variants in a person’s DNA that indicate genetic disorders. It allows researchers to model and calculate complicated physics processes, to forecast the genesis of the universe’s structure, and to understand planet ecosystem to help advance the climate research. AI drives advances in drug discovery and can assist with molecule synthesis and molecular property identification.

      AI finds application in all areas of science and engineering. The role of AI in science will grow and allow scientists to innovate faster.

      AI will further contribute to scientific understanding by assisting scientists in deriving new insights, generating new ideas and connections, generalizing scientific concepts, and transferring them between areas of scientific research.

      Using synthetic data and combining physical and machine learning models and other advances of AI/ML – such as graphs, use of unstructured data (language models), and computer vision – will accelerate the use of AI in science and engineering.

      Event- and Scenario-Driven AI

      AI-driven signal-gathering systems analyze a continuous stream of data to generate insights and predictions that enable strategic decision modeling and scenario planning by providing understanding of how and what areas of business might be impacted by certain events.

      AI enables the scenario-based approach to drive insights through pattern identification in addition to familiar pattern recognition, helping to understand how events are related.

      A system with anticipatory capabilities requires an event-driven architecture that enables gathering and analyzing different types of data (text, video, images) across multiple channels (social media, transactional systems, news feeds, etc.) for event-driven and event-sequencing modeling.

      ML simulation-based training of the model using advanced techniques under the umbrella of Reinforcement Learning in conjunction with statistically robust Bayesian probabilistic framework will aid in setting up future trends in AI.

      AI Reasoning

      Most of the applications of machine learning and AI today is about predicting future behaviors based on historical data and past behaviors. We can predict what product the customer would most likely buy or the price of a house when it goes on sale.

      Most of the current algorithms use the correlation between different parameters to make a prediction, for example, the correlation between the event and the outcome can look like “When X occurs, we can predict that Y will occur.” This, however, does not translate into “Y occurred because of X.”

      The development of a causal AI that uses causal inference to reason and identify the root cause and the causal relationships between variables without mistaking correlation and causation is still in its early stages but rapidly evolving.

      Some of the algorithms that the researchers are working with are casual graph models and algorithms that are at the intersection of causal inference with decision making and reinforcement learning (Causal Artificial Intelligence Lab, 2022).

      Synthetic Data

      Synthetic data is artificially generated data that mimics the structure of real-life data. It should also have the same mathematical and statistical properties as the real-world data that it is created to replicate.

      Synthetic data is used to train machine learning models when there is not enough real data or the existing data does not meet specific needs. It allows users to remove contextual bias from data sets containing personal data, prevent privacy concerns, and ensure compliance with privacy laws and regulations.

      Another application of synthetic data is solving data-sharing challenges.

      Researchers learned that quite often synthetic data sets outperform real-world data. Recently, a team of researchers at MIT built a synthetic data set of 150,000 video clips capturing human actions and used that data set to train the model. The researchers found that “the synthetically trained models performed even better than models trained on real data for videos that have fewer background objects” (MIT News Office, 2022).

      Today, synthetic data is used in language systems, in training self-driving cars, in improving fraud detection, and in clinical research, just to name a few examples.

      Synthetic data opens the doors for innovation across all industries and applications of AI by enabling access to data for any scenario and technology and business needs.

      Digital Twins

      Digital twins (DT) are virtual replicas of physical objects, devices, people, places, processes, and systems. In Manufacturing, almost every product and manufacturing process can have a complete digital replica of itself thanks to IoT, streaming data, and cheap cloud storage.

      All this data has allowed for complex simulations of, for example, how a piece of equipment will perform over time to predict future failures before they happen, reducing costly maintenance and extending equipment lifetime.

      In addition to predictive maintenance, DT and AI technologies have enabled organizations to design and digitally test complex equipment such as aircraft engines, trains, offshore oil platforms, and wind turbines before physically manufacturing them. This helps to improve product and process quality, manufacturing efficiency, and costs. DT technology also finds applications in architecture, construction, energy, infrastructure industries, and even retail.

      Digital twins combined with the metaverse provide a collaborative and interactive environment with immersive experience and real-time physics capabilities (as an example, Siemens presented an Immersive Digital Twin of a Plant at the Collision 2022 conference).

      Future trends include enabling autonomous behavior of a DT. An advanced DT can replicate itself as it moves into several devices, hence requiring the autonomous property. Such autonomous behavior of the DT will in turn influence the growth and further advancement of AI.

      Edge AI

      A simple definition for edge AI: A combination of edge computing and artificial intelligence, it enables the deployment of AI applications in devices of the physical world, in the field, where the data is located, such as IoT devices, devices on the manufacturing floor, healthcare devices, or a self-driving car.

      Edge AI integrates AI into edge computing devices for quicker and improved data processing and smart automation.

      The main benefits of edge AI include:

      • Real-time data processing capabilities to reduce latency and enable near real-time analytics and insights.
      • Reduced cost and bandwidth requirements as there is no need to transfer data to the cloud for computing.
      • Increased data security as the data is processed locally, on the device, reducing the risk of loss of sensitive data.
      • Improved automation by training machines to perform automated tasks.

      Edge AI is already used in a variety of applications and use cases including computer vision, geospatial intelligence, object detection, drones, and health monitoring devices.

      Combinatorial Optimization

      “Combinatorial optimization is a subfield of mathematical optimization that consists of finding an optimal object from a finite set of objects” (Wikipedia, retrieved December 2022).

      Applications of combinatorial optimization include:

      • Supply chain optimization
      • Scheduling and logistics, for example, vehicle routing where the trucks are making stops for pickup and deliveries
      • Operations optimization

      Classical combinatorial optimization (CO) techniques were widely used in operations research and played a major role in earlier developments of AI.

      The introduction of deep learning algorithms in recent years allowed researchers to combine neural network and conventional optimization algorithms; for example, incorporating neural combinatorial optimization algorithms in the conventional optimization framework. Researchers confirmed that certain combinations of these frameworks and algorithms can provide significant performance improvements.

      The research in this space continues and we look forward to learning how machine learning and AI (backtracking algorithms, reinforcement learning, deep learning, graph attention networks, and others) will be used for solving challenging combinatorial and decision-making problems.

      References

      “AI Can Power Scenario Planning for Real-Time Strategic Insights.” The Wall Street Journal, CFO Journal, content by Deloitte, 7 June 2021. Accessed 11 Dec. 2022.
      Ali Fdal, Omar. “Synthetic Data: 4 Use Cases in Modern Enterprises.” DATAVERSITY, 5 May 2022. Accessed
      11 Dec. 2022.
      Andrews, Gerard. “What Is Synthetic Data?” NVIDIA, 8 June 2021. Accessed 11 Dec. 2022.
      Bareinboim, Elias. “Causal Reinforcement Learning.” Causal AI, 2020. Accessed 11 Dec. 2022.
      Bengio, Yoshua, Andrea Lodi, and Antoine Prouvost. “Machine learning for combinatorial optimization: A methodological tour d’horizon.” European Journal of Operational Research, vol. 290, no. 2, 2021, pp. 405-421, https://doi.org/10.1016/j.ejor.2020.07.063. Accessed 11 Dec. 2022.
      Benjamins, Richard. “Four design principles for developing sustainable AI applications.” Telefónica S.A., 10 Sept. 2018. Accessed on 11 Dec. 2022.
      Blades, Robin. “AI Generates Hypotheses Human Scientists Have Not Thought Of.” Scientific American, 28 October 2021. Accessed 11 Dec. 2022.
      “Combinatorial Optimization.” Wikipedia article, Accessed 11 Dec. 2022.
      Cronholm, Stefan, and Hannes Göbel. “Design Principles for Human-Centred Artificial Intelligence.” University of Borås, Sweden, 11 Aug. 2022. Accessed on 11 Dec. 2022
      Devaux, Elise. “Types of synthetic data and 4 real-life examples.” Statice, 29 May 2022. Accessed 11 Dec. 2022.
      Emmental, Russell. “A Guide to Causal AI.” ITBriefcase, 30 March 2022. Accessed 11 Dec. 2022.
      “Empowering AI Leadership: AI C-Suite Toolkit.” World Economic Forum, 12 Jan. 2022. Accessed 11 Dec 2022.
      Falk, Dan. “How Artificial Intelligence Is Changing Science.” Quanta Magazine, 11 March 2019. Accessed 11 Dec. 2022.
      Fritschle, Matthew J. “The Principles of Designing AI for Humans.” Aumcore, 17 Aug. 2018. Accessed 8 Dec. 2022.
      Garmendia, Andoni I., et al. Neural Combinatorial Optimization: a New Player in the Field.” IEEE, arXiv:2205.01356v1, 3 May 2022. Accessed 11 Dec. 2022.
      Gülen, Kerem. “AI Is Revolutionizing Every Field and Science is no Exception.” Dataconomy Media GmbH, 9 Nov. 9, 2022. Accessed 11 Dec. 2022
      Krenn, Mario, et al. “On scientific understanding with artificial intelligence.” Nature Reviews Physics, vol. 4, 11 Oct. 2022, pp. 761–769. https://doi.org/10.1038/s42254-022-00518-3. Accessed 11 Dec. 2022.
      Laboratory for Information and Decision Systems. “The real promise of synthetic data.” MIT News, 16 Oct. 2020. Accessed 11 Dec. 2022.
      Lecca, Paola. “Machine Learning for Causal Inference in Biological Networks: Perspectives of This Challenge.” Frontiers, 22 Sept. 2021. Accessed 11 Dec. 2022. Mirabella, Lucia. “Digital Twin x Metaverse: real and virtual made easy.” Siemens presentation at Collision 2022 conference, Toronto, Ontario. Accessed 11 Dec. 2022. Mitchum, Rob, and Louise Lerner. “How AI could change science.” University of Chicago News, 1 Oct. 2019. Accessed 11 Dec. 2022.
      Okeke, Franklin. “The benefits of edge AI.” TechRepublic, 22 Sept. 2022, Accessed 11 Dec. 2022.
      Perlmutter, Nathan. “Machine Learning and Combinatorial Optimization Problems.” Crater Labs, 31 July 31, 2019. Accessed 11 Dec. 2022.
      Sampson, Ovetta. “Design Principles for a New AI World.” UX Magazine, 6 Jan. 2022. Accessed 11 Dec. 2022.
      Sgaier, Sema K., Vincent Huang, and Grace Charles. “The Case for Causal AI.” Stanford Social Innovation Review, Summer 2020. Accessed 11 Dec. 2022.
      “Synthetic Data.” Wikipedia article, Accessed 11 Dec. 2022.
      Take, Marius, et al. “Software Design Patterns for AI-Systems.” EMISA Workshop 2021, CEUR-WS.org, Proceedings 30. Accessed 11 Dec. 2022.
      Toews, Rob. “Synthetic Data Is About To Transform Artificial Intelligence.” Forbes, 12 June 2022. Accessed
      11 Dec. 2022.
      Zewe, Adam. “In machine learning, synthetic data can offer real performance improvements.” MIT News Office, 3 Nov. 2022. Accessed 11 Dec. 2022.
      Zhang, Junzhe, and Elias Bareinboim. “Can Humans Be out of the Loop?” Technical Report, Department of Computer Science, Columbia University, NY, June 2022. Accessed 11 Dec. 2022.

      Contributors

      Irina Sedenko Anu Ganesh Amir Feizpour David Glazer Delina Ivanova

      Irina Sedenko

      Advisory Director

      Info-Tech

      Anu Ganesh

      Technical Counselor

      Info-Tech

      Amir Feizpour

      Co-Founder & CEO

      Aggregate Intellect Inc.

      David Glazer

      VP of Analytics

      Kroll

      Delina Ivanova

      Associate Director, Data & Analytics

      HelloFresh

      Usman Lakhani

      DevOps

      WeCloudData

      Improve Your IT Recruitment Process

      • Buy Link or Shortcode: {j2store}578|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: Attract & Select
      • Parent Category Link: /attract-and-select

      Business and IT leaders aiming to recruit and select the best talent need to:

      • Get involved in the talent acquisition process at key moments.
      • Market their organization to top talent through an authentic employer brand.
      • Create engaging and accurate job ads.
      • Leverage purposeful sourcing for anticipated talent needs.
      • Effectively assess candidates with a strong interview process.
      • Set up new employees for success.

      Our Advice

      Critical Insight

      To create a great candidate experience, IT departments must be involved in the process at key points, recruitment and selection is not a job for HR alone!

      Impact and Result

      • Use this how-to guide to articulate an authentic (employee value proposition) EVP and employer brand.
      • Perform an analysis of current sourcing methods and build an action plan to get IT involved.
      • Create an effective and engaging job ad to insure the right people are applying.
      • Train hiring managers to effectively deliver interviews that correctly assess candidate suitability.
      • Get links to in-depth Info-Tech resources and tools.

      Improve Your IT Recruitment Process Research & Tools

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

      1. Improve Your IT Recruitment Process – A guide to help you attract and select the best talent.

      Train your IT department to get involved in the recruitment process to attract and select the best talent.

      • Improve Your IT Recruitment Process Capstone Deck

      2. Improve Your IT Recruitment Process Workbook – A tool to document your action plans.

      Use this tool in conjunction with the Improve you IT Recruitment Process to document your action plans

      • Improve Your IT Recruitment Process Workbook

      3. Interview Guide Template – A template to organize interview questions and their rating scales, take notes during the interview, and ensure all interviews follow a similar structure.

      To get useful information from an interview, the interviewer should be focused on what candidates are saying and how they are saying it, not on what the next question will be, what probes to ask, or how they will score the responses. This Interview Guide Template will help interviewers stay focused and collect good information about candidates.

      • Interview Guide Template

      4. IT Behavioral Interview Question Library – A tool that contains a complete list of sample questions aligned with core, leadership, and IT competencies.

      Hiring managers can choose from a comprehensive collection of core, functional, and leadership competency-based behavioral interview questions.

      • IT Behavioral Interview Question Library

      5. Job Ad Template – A template to allow complete documentation of the characteristics, responsibilities, and requirements for a given job posting in IT.

      Use this template to develop a well-written job posting that will attract the star candidates and, in turn, deflect submission of irrelevant applications by those unqualified.

      • Job Ad Template

      6. Idea Catalog – A tool to evaluate virtual TA solutions.

      The most innovative technology isn’t necessarily the right solution. Review talent acquisition (TA) solutions and evaluate the purpose each option serves in addressing critical challenges and replacing critical in-person activities.

      • Idea Catalog: Adapt the Talent Acquisition Process to a Virtual Environment
      [infographic]

      Workshop: Improve Your IT Recruitment Process

      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 Employee Value Proposition and Employer Branding

      The Purpose

      Establish the employee value proposition (EVP) and employer brand.

      Key Benefits Achieved

      Have a well-defined EVP that you communicate through your employer brand.

      Activities

      1.1 Gather feedback.

      1.2 Build key messages.

      1.3 Assess employer brand.

      Outputs

      Content and themes surrounding the EVP

      Draft EVP and supporting statements

      A clearer understanding of the current employer brand and how it could be improved

      2 Job Ads and Sourcing

      The Purpose

      Develop job postings and build a strong sourcing program.

      Key Benefits Achieved

      Create the framework for an effective job posting and analyze existing sourcing methods.

      Activities

      2.1 Review and update your job ads.

      2.2 Review the effectiveness of existing sourcing programs.

      2.3 Review job ads and sourcing methods for bias.

      Outputs

      Updated job ad

      Low usage sourcing methods identified for development

      Minimize bias present in ads and sourcing methods

      3 Effective Interviewing

      The Purpose

      Create a high-quality interview process to improve candidate assessment.

      Key Benefits Achieved

      Training on being an effective interviewer.

      Activities

      3.1 Create an ideal candidate scorecard.

      3.2 Map out your interview process.

      3.3 Practice behavioral interviews.

      Outputs

      Ideal candidate persona

      Finalized interview and assessment process

      Practice interviews

      4 Onboarding and Action Plan

      The Purpose

      Drive employee engagement and retention with a robust program that acclimates, guides, and develops new hires.

      Key Benefits Achieved

      Evaluation of current onboarding practice.

      Activities

      4.1 Evaluate and redesign the onboarding program.

      Outputs

      Determine new onboarding activities to fill identified gaps.

      Further reading

      Improve Your IT Recruitment Process

      Train your IT department to get involved in the recruitment process to attract and select the best talent.

      Own the IT recruitment process

      Train your IT department to get involved in the recruitment process to attract and select the best talent.

      Follow this blueprint to:

      • Define and communicate the unique benefits of working for your organization to potential candidates through a strong employer brand.
      • Learn best practices around creating effective job postings.
      • Target your job posting efforts on the areas with the greatest ROI.
      • Create and deliver an effective, seamless, and positive interview and offer process for candidates.
      • Acclimate new hires and set them up for success.

      Get involved at key moments of the candidate experience to have the biggest impact


      Employee Value Proposition (EVP) and Employer Brand



      Job Postings and a Strong Sourcing Program

      Effective Interviewing

      Onboarding: Setting up New Hires For Success

      Awareness Research Application Screening Interview and Assessment Follow Up Onboarding

      RECRUIT QUALITY STAFF

      Hiring talent is critical to organizational success

      Talent is a priority for the entire organization:

      Respondents rated “recruitment” as the top issue facing organizations today (McLean & Company 2022 HR Trends Report).

      37% of IT departments are outsourcing roles to fill internal skill shortages (Info-Tech Talent Trends 2022 Survey).

      Yet bad hires are alarmingly common:

      Hiring is one of the least successful business processes, with three-quarters of managers reporting that they have made a bad hire (Robert Half, 2021).

      48% of survey respondents stated improving the quality of hires was the top recruiting priority for 2021 (Jobvite, 2021).

      Workshop overview

      Prework

      Day 1

      Day 2

      Day 3

      Day 4

      Post work

      Current Process and Job Descriptions Documented

      Establish the Employee Value Proposition (EVP) and Employer Brand

      Develop Job Postings and Build a Strong Sourcing Program

      Effective Interviewing

      Onboarding and Action Planning

      Putting the Action Plan Into Action!

      Activities

      • Recruitment Process Mapped Out and Stakeholders Identified
      • Prepare a JD and JP for Four Priority Jobs
      • Collect Information on Where Your Best Candidates Are Coming From

      1.1 Introduce the Concept of an EVP

      1.2 Brainstorm Unique Benefits of Working at Your Organization

      1.2 Employer Brand Introduction

      2.1 What Makes an Attractive Job Posting

      2.2 Create the Framework for Job Posting

      2.3 Improve the Sourcing Process

      2.4 Review Process for Bias

      3.1 Creating an Interview Process

      3.2 Selecting Interview Questions

      3.3 Avoiding Bias During Interviews

      3.4 Practice Interviews

      4.1 Why Onboarding Matters

      4.2 Acclimatize New Hires and Set Them Up for Success

      4.3 Action Plan

      5.1 Review Outputs and Select Priorities

      5.2 Consult With HR and Senior Management to Get Buy-In

      5.3 Plan to Avoid Relapse Behaviors

      Deliverables

      1. EVP draft completed
      2. Employer brand action plan
      1. Organization-specific job posting framework
      2. Sourcing Plan Template for four priority jobs
      3. Sourcing action plan
      1. Completed Interview Guide Template
      2. Managers practice a panel interview
      1. Onboarding best practices
      2. Action plan

      Enhance Your Recruitment Strategies

      The way you position the organization impacts who is likely to apply to posted positions.

      Develop a strong employee value proposition

      What is an employee value proposition?

      And what are the key components?

      The employee value proposition is your opportunity to showcase the unique benefits and opportunities of working at your organization, allowing you to attract a wider pool of candidates.

      AN EMPLOYEE VALUE PROPOSITION IS:

      AN EMPLOYEE VALUE PROPOSITION IS NOT:

      • An authentic representation of the employee experience
      • Aligned with organizational culture
      • Fundamental to all stages of the employee lifecycle
      • A guide to help investment in programs and policies
      • Short and succinct
      • What the employee can do for you
      • A list of programs and policies
      • An annual project

      THE FOUR KEY COMPONENTS OF AN EMPLOYEE VALUE PROPOSITION

      Rewards

      Organizational Elements

      Working Conditions

      Day-to-Day Job Elements

      • Compensation
      • Health Benefits
      • Retirement Benefits
      • Vacation
      • Culture
      • Customer Focus
      • Organization Potential
      • Department Relationships
      • Senior Management Relationships
      • Work/Life Balance
      • Working Environment
      • Employee Empowerment
      • Development
      • Rewards & Recognition
      • Co-Worker Relationships
      • Manager Relationships

      Creating a compelling EVP that presents a picture of your employee experience, with a focus on diversity, will attract a wide pool of diverse candidates to your team. This can lead to many internal and external benefits for your organization.

      How to collect information on your EVP

      Existing Employee Value Proposition: If your organization or IT department has an existing employee value proposition, rather than starting from scratch, we recommend leveraging that and moving to the testing phase to see if the EVP still resonates with staff and external parties.

      Employee Engagement Results: If your organization does an employee engagement survey, review the results to identify the areas in which the IT organization is performing well. Identify and document any key comment themes in the report around why employees enjoy working for the organization or what makes your IT department a great place to work.

      Social Media Sites. Prepare for the good, the bad, and the ugly. Social media websites like Glassdoor and Indeed make it easier for employees to share their experiences at an organization honestly and candidly. While postings on these sites won’t relate exclusively to the IT department, they do invite participants to identify their department in the organization. You can search these to identify any positive things people are saying about working for the organization and potentially opportunities for improvement (which you can use as a starting point in the retention section of this report).

      1.1 Gather feedback

      1. Download the Improve Your IT Recruitment Workbook.
      2. On tab 1.1, brainstorm the top five things you value most about working at the organization. Ask yourself what would fall in each category and identify any key themes. Be sure to take note of any specific quotes you have.
      3. Brainstorm limitations that the organization currently has in each of those areas.

      Download the Recruitment Workbook

      Input

      Output
      • Employee opinions
      • Employee responses to four EVP components
      • Content for EVP

      Materials

      Participants

      • Recruitment Workbook
      • Diverse employees
      • Different departments
      • Different role levels

      1.2 Build key messages

      1. Go to tab 1.2 in your workbook
      2. Identify themes from activity 1.1 that would be considered current strengths of you organization.
      3. Identify themes from activity 1.2 that are aspirational elements of your organization.
      4. Identify up to four key statements to focus on for the EVP, ensuring that your EVP speaks to at least one of the five categories above.
      5. Integrate these into one overall statement.

      Examples below.

      Input

      Output
      • Feedback from focus groups
      • EVP and supporting statements

      Materials

      Participants

      • Workbook handout
      • Pen and paper for documenting responses
      • IT leadership team

      Sample EVPs

      Shopify

      “We’re Shopify. Our mission is to make commerce better for everyone – but we’re not the workplace for everyone. We thrive on change, operate on trust, and leverage the diverse perspectives of people on our team in everything we do. We solve problems at a rapid pace. In short, we get shit done.”

      Bettercloud

      “At Bettercloud, we have a smart, ambitious team dedicated to delighting our customers. Our culture of ownership and transparency empowers our team to achieve goals they didn’t think possible. For all those on board, it’s going to be a challenging and rewarding journey – and we’re just getting started.”

      Ellevest

      “As a team member at Ellevest, you can expect to make a difference through your work, to have a direct impact on the achievement of a very meaningful mission, to significantly advance your career trajectory, and to have room for fun and fulfillment in your daily life. We know that achieving a mission as critical as ours requires incredible talent and teamwork, and team is the most important thing to us.”

      Sources: Built In, 2021; Workology, 2022

      Ensure your EVP resonates with employees and prospects

      Test your EVP with internal and external audiences.

      INTERNAL TEST REVOLVES AROUND THE 3A’s

      EXTERNAL TEST REVOLVES AROUND THE 3C’s

      ALIGNED: The EVP is in line with the organization’s purpose, vision, values, and processes. Ensure policies and programs are aligned with the organization’s EVP.

      CLEAR: The EVP is straightforward, simple, and easy to understand. Without a clear message in the market, even the best intentioned EVPs can be lost in confusion.

      ACCURATE: The EVP is clear and compelling, supported by proof points. It captures the true employee experience, which matches the organization’s communication and message in the market.

      COMPELLING: The EVP emphasizes the value created for employees and is a strong motivator to join this organization. A strong EVP will be effective in drawing in external candidates. The message will resonate with them and attract them to your organization.

      ASPIRATIONAL: The EVP inspires both individuals and the IT organization as a whole. Identify and invest in the areas that are sure to generate the highest returns for employees.

      COMPREHENSIVE: The EVP provides enough information for the potential employee to understand the true employee experience and to self-assess whether they are a good fit for your organization. If the EVP lacks depth, the potential employee may have a hard time understanding the benefits and rewards of working for your organization.

      Want to learn more?

      Recruit IT Talent

      • Improve candidate experience to hire top IT talent.

      Recruit and Retain More Women in IT

      • Gender diversity is directly correlated to IT performance.

      Recruit and Retain People of Color in IT

      • Good business, not just good philanthropy.

      Enhance Your Recruitment Strategies

      The way you position the organization impacts who is likely to apply to posted positions.

      Market your EVP to potential candidates: Employer Brand

      Employer brand includes how you market the EVP internally and externally – consistency is key

      The employer brand is the perception internal and external stakeholders hold of the organization and exists whether it has been curated or not. Curating the employer brand involves marketing the organization and employee experience. Grounding your employer brand in your EVP enables you to communicate and market an accurate portrayal of your organization and employee experience and make you desirable to both current and potential employees.

      The image contains a picture of several shapes. There is a trapezoid that is labelled EVP, and has a an arrow pointing to the text beside it. There is also an arrowing pointing down from it to another trapezoid that is labelled Employer Brand.

      The unique offering an employer provides to employees in return for their effort, motivating them to join or remain at the organization.

      The perception internal and external stakeholders hold of the organization.

      Alignment between the EVP, employer brand, and corporate brand is the ideal branding package. An in-sync marketing strategy ensures stakeholders perceive and experience the brand the same way, creating brand ambassadors.

      The image contains three circles that are connected. The circles are labelled: EVP, Employer Brand, Corporate Brand.

      Ensure your branding material creates a connection

      How you present your employer brand is just as important as the content. Ideally, you want the viewer to connect with and personalize the material for the message to have staying power. Use Marketing’s expertise to help craft impactful promotional materials to engage and excite the viewer.

      Visuals

      Images are often the first thing viewers notice. Use visuals that connect to your employer brand to engage the viewer’s attention and increase the likelihood that your message will resonate. However, if there are too many visuals this may detract from your content – balance is key!

      Language

      Wordsmithing is often the most difficult aspect of marketing. Your message should be accurate, informative, and engaging. Work with Marketing to ensure your wording is clever and succinct – the more concise, the better.

      Composition

      Integrate visuals and language to complete your marketing package. Ensure that the text and images are balanced to draw in the viewer.

      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.

      The image contains a picture of Steve Thornton.

      “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.

      The image contains a picture of Robert Leahy.

      Interview with Robert Leahy

      Chief Information Officer, Goddard Space Flight Center, NASA

      2.1 Assess your organization’s employer brand

      1. Go to tab 2.1 in the Improve Your IT Recruitment Workbook.
      2. Put yourself in the shoes of someone on the outside looking in. If they were to look up your organization, what impression would they be given about what is like to work there?
      3. Run a Google search on your organization with key words “jobs,” “culture,” and “working environment” to see what a potential candidate would see when they begin researching your organization.
      4. You can use sites like:

      • Glassdoor
      • Indeed company pages
      • LinkedIn company pages
      • Social media
      • Your own website
    • Identify what your organization is doing well and record that under the “Continue” box in your workbook.
    • Record anything your organization should stop doing under the “Stop” box.
    • Brainstorm some ideas that your organization should think about implementing to improve the employer brand under the “Start” Box.
    • Input Output
      • Existing branding material on the internet
      • A clearer understanding of the current employer brand and how it could be improved
      Materials Participants
      • Workbook handout
      • Senior IT Leaders

      Want to learn more?

      Recruit IT Talent

      • Improve candidate experience to hire top IT talent.

      Recruit and Retain More Women in IT

      • Gender diversity is directly correlated to IT performance.

      Recruit and Retain People of Color in IT

      • Good business, not just good philanthropy.

      Enhance Your Recruitment Strategies

      The way you position the organization impacts who is likely to apply to posted positions.

      Create engaging job ads to attract talent to the organization

      We have a job description; can I just post that on Indeed?

      A job description is an internal document that includes sections such as general job information, major responsibilities, key relationships, qualifications, and competencies. It communicates job expectations to incumbents and key job data to HR programs.

      A job ad is an externally facing document that advertises a position with the intent of attracting job applicants. It contains key elements from the job description as well as information on the organization and its EVP.

      Write an Effective Job Ad

      • Ensure that your job ad speaks to the audience you are targeting through the language you use.
        • E.g. If you are hiring for a creative role, use creative language and formatting. If you are writing for students, emphasize growth opportunities.
      • Highlight the organization’s EVP.
      • Paint an accurate picture of key aspects of the role but avoid the nitty gritty as it may overwhelm applicants.
      • Link to your organization’s website and social media platforms so applicants can easily find more information.

      A job description informs a job ad, it doesn’t replace it. Don’t be lulled into using a job description as a posting when there’s a time crunch to fill a position. Refer to job postings as job advertisements to reinforce that their purpose is to attract attention and talent.

      An effective job posting contains the following elements:

      Position Title
      • Clearly defined job titles are important for screening applicants as this is one of the first things the candidate will read.
      • Indicating the earnings range that the position pays cuts out time spent on reviewing candidates who may never accept the position and saves them from applying to a job that doesn’t match what they are looking for.
      Company
      • Provide a brief description of the organization including the products or services it offers, the corporate culture, and any training and career development programs.
      Summary Description
      • Describe briefly why the position exists. In other words, what is the position's primary purpose? The statement should include the overall results the job is intended to produce and some of the key means by which the position achieves these results.
      Responsibilities
      • Use bullet points to list the fundamental accountabilities of the position. Candidates want to know what they will be doing on a day-to-day basis.
      • Begin each responsibility or accountability statement with an action word and follow with a brief phrase to describe what is done to accomplish the function.
      Position Characteristics
      • Give examples of key problems and thinking challenges encountered by the position. Describe the type of analysis or creativity required to resolve these problems.
      • Provide examples of final decision-making authority. The examples should reflect the constraints placed on the position by people, policies, and/or procedures.
      Position Requirements
      • List all formal education and certifications required.
      • List all knowledge and experience required.
      • List all personal attributes required.
      Work Conditions
      • List all work conditions that the employee must accommodate. This could include any sensory, physical, or mental requirements of the position or any special conditions of employment, such as hours.
      Process to Apply
      • Include the methods in which the organization wants to receive applications and contact information of who will receive the applications.

      Bottom Line: A truly successful job posting ferrets out those hidden stars that may be over cautious and filters out hundreds of applications from the woefully under qualified.

      The do’s and don’ts of an inclusive job ad

      DON’T overlook the power of words. Avoid phrases like “strong English language skills” as this may deter non-native English speakers from applying and a “clean-shaven” requirement can exclude candidates whose faith requires them to maintain facial hair.

      DON’T post a long requirements list. A study showed that the average jobseeker spends only 49.7 seconds reviewing a listing before deciding it's not a fit.*

      DON’T present a toxic work culture; phrases such as “work hard, play hard” can put off many candidates and play into the “bro- culture” stereotype in tech.

      Position Title: Senior Lorem Ipsum

      Salary Band: $XXX to $XXX

      Diversity is a core value at ACME Inc. We believe that diversity and inclusion is our strength, and we’re passionate about building an environment where all employees are valued and can perform at their best.

      As a … you will …

      Our ideal candidate ….

      Required Education and Experience

      • Bachelor’s degree in …
      • Minimum five (5) years …

      Required Skills

      Preferred Skills

      At ACME Inc. you will find …

      DO promote pay equity by being up front and honest about salary expectations.

      DO emphasize your organization’s commitment to diversity and an inclusive workplace by adding an equity statement.

      DO limit your requirements to “must haves” or at least showcase them first before the “nice-to-haves.”

      DO involve current employees or members of your employee resource groups when creating job descriptions to ensure that they ask for what you really need.

      DO focus on company values and criteria that are important to the job, not just what’s always been done.

      *Source: Ladders, 2013

      Before posting the job ad complete the DEI job posting validation checklist

      Does the job posting highlight your organization’s EVP

      Does the job posting avoid words that might discourage women, people of color, and other members of underrepresented groups from applying?

      Has the position description been carefully reviewed and revised to reflect current and future expectations for the position, rather than expectations informed by the persons who have previously held the job?

      Has the hiring committee eliminated any unnecessary job skills or requirements (college degree, years or type of previous experience, etc.) that might negatively impact recruitment of underrepresented groups?

      Has the hiring committee posted the job in places (job boards, websites, colleges, etc.) where applicants from underrepresented groups will be able to easily view or access it?

      Have members of the hiring committee attended job fairs or other events hosted by underrepresented groups?

      Has the hiring committee asked current employees from underrepresented groups to spread the word about the position?

      Has the hiring committee worked with the marketing team to ensure that people from diverse groups are featured in the organization’s website, publications, and social media?

      es the job description clearly demonstrate the organization’s and leadership’s commitment to DEI?

      *Source: Recruit and Retain People of Color in IT

      3.1 Review and update your job ads

      1. Download the Job Ad Template.
      2. Look online or ask HR for an example of a current job advertisement you are using.
      • If you don’t have one, you can use a job description as a starting point.
    • Review all the elements of the job ad and make sure they align with the list on the previous slide, adding or changing, as necessary. Your job ad should be no more than two pages long.
    • Using the tools on the previous two slides, review your first draft to ensure the job posting is free of language or elements that will discourage diverse candidates from applying.
    • Review your job advertisement with HR to get feedback or to use as a template going forward.
    • Input Output
      • Existing job ad or job description
      • Updated job ad
      Materials Participants
      • Job ad or job description
      • Job Ad Template
      • Hiring Managers

      Want to learn more?

      Recruit IT Talent

      • Improve candidate experience to hire top IT talent.

      Recruit and Retain More Women in IT

      • Gender diversity is directly correlated to IT performance.

      Recruit and Retain People of Color in IT

      • Good business, not just good philanthropy.

      Enhance Your Recruitment Strategies

      Focus on key programs and tactics to improve the effectiveness of your sourcing approach.

      Get involved with sourcing to get your job ad seen

      To meet growing expectations, organizations need to change the way they source

      Social Media

      Social media has trained candidates to expect:

      • Organizations to stay in touch and keep track of them.
      • A personalized candidate experience.
      • To understand organizational culture and a day in the life.

      While the focus on the candidate experience is important throughout the talent acquisition process, social media, technology, and values have made it a critical component of sourcing.

      Technology

      Candidates expect to be able to access job ads from all platforms.

      • Today, close to 90% of candidates use a mobile platform to job hunt (SmartRecruiters, 2022).
      • However, only 36% of organizations are optimizing their job postings for mobile. (The Undercover Recruiter, 2021)

      Job ads must be clear, concise, and easily viewed on a mobile device.

      Candidate Values

      Job candidate’s values are changing.

      • There is a growing focus on work/life balance, purpose, innovation, and career development. Organizations need to understand candidate values and highlight how the EVP aligns with these interests.

      Authenticity remains important.

      • Clearly and accurately represent your organization and its culture.

      Focus on key programs and tactics to improve the effectiveness of your sourcing approach

      Internal Talent Mobility (ITM) Program

      Social Media Program

      Employee Referral Program

      Alumni Program

      Campus Recruiting Program

      Other Sourcing Tactics

      Take advantage of your current talent with an internal talent mobility program

      What is it?

      Positioning the right talent in the right place, at the right time, for the right reasons, and supporting them appropriately.

      Internal Talent Mobility (ITM) Program

      Social Media Program

      Employee Referral Program

      Alumni Program

      Campus Recruiting Program

      Other Sourcing Tactics

      ITM program benefits:

      1. Retention
      2. Provide opportunities to develop professionally, whether in the current role or through promotions/lateral moves. Keep strong performers and high-potential employees committed to the organization.

      3. Close Skills Gap
      4. Address rapid change, knowledge drain due to retiring Baby Boomers, and frustration associated with time to hire or time to productivity.

      5. Cost/Time Savings
      6. Reduce spend on talent acquisition, severance, time to productivity, and onboarding.

      7. Employee Engagement
      8. Increase motivation and productivity by providing increased growth and development opportunities.

      9. EVP
      10. Align with the organization’s offering and what is important to the employees from a development perspective.

      11. Employee & Leadership Development
      12. Support and develop employees from all levels and job functions.

      Leverage social media to identify and connect with talent

      Internal Talent Mobility (ITM) Program

      Social Media Program

      Employee Referral Program

      Alumni Program

      Campus Recruiting Program

      Other Sourcing Tactics

      What is it? The widely accessible electronic tools that enable anyone to publish and access information, collaborate on common efforts, and build relationships.

      Learning to use social media effectively is key to sourcing the right talent.

      • Today, 92% of organizations leverage social media for talent acquisition.
      • 80% of employers find passive candidates through social media – second only to referrals.
      • 86% percent of job seekers used social media for their most recent job search.
      (Ku, 2021)

      Benefits of social media:

      • Provides access to candidates who may not know the organization.
      • Taps extended networks.
      • Facilitates consistent communication with candidates and talent in pipelines.
      • Personalizes the candidate experience.
      • Provides access to extensive data.

      Challenges of social media:

      With the proliferation of social media and use by most organizations, social media platforms have become overcrowded. As a result:

      • Organizations are directly and very apparently competing for talent with competitors.
      • Users are bombarded with information and are tuning out.

      “It is all about how we can get someone’s attention and get them to respond. People are becoming jaded.”

      – Katrina Collier, Social Recruiting Expert, The Searchologist

      Reap the rewards of an employee referral program

      Internal Talent Mobility (ITM) Program

      Social Media Program

      Employee Referral Program

      Alumni Program

      Campus Recruiting Program

      Other Sourcing Tactics

      What is it? Employees recommend qualified candidates. If the referral is hired, the referring employee typically receives some sort of reward.

      Benefits of an employee referral program:

      1. Lower Recruiting Costs
      2. 55% of organizations report that hiring a referral is less expensive that a non-referred candidate (Clutch, 2020).

      3. Decreased time to fill
      4. The average recruiting lifecycle for an employee referral is 29 days, compared with 55 days for a non referral (Betterup, 2022).

      5. Decreased turnover
      6. 46% percent of employees who were referred stay at their organization for a least one year, compared to 33% of career site hires (Betterup, 2022).

      7. Increased quality of hire
      8. High performers are more likely to refer other high performers to an organization (The University of Chicago Press, 2019).

      Avoid the Like Me Bias: Continually evaluate the diversity of candidates sourced from the employee referral program. Unless your workforce is already diverse, referrals can hinder diversity because employees tend to recommend people like themselves.

      Tap into your network of former employees

      Internal Talent Mobility (ITM) Program

      Social Media Program

      Employee Referral Program

      Alumni Program

      Campus Recruiting Program

      Other Sourcing Tactics

      What is it? An alumni referral program is a formalized way to maintain ongoing relationships with former employees of the organization.

      Successful organizations use an alumni program:

      • 98% of the F500 have some sort of Alumni program (LinkedIn, 2019).

      Benefits of an alumni program:

      1. Branding
      • Alumni are regarded as credible sources of information. They can be a valuable resource for disseminating and promoting the employer brand.
    • Source of talent
      • Boomerang employees are doubly valuable as they understand the organization and also have developed skills and industry experience.
        • Recover some of the cost of turnover and cost per hire with a pool of prequalified candidates who will more quickly reach full productivity.
    • Referral potential
      • Developing a robust alumni network provides access to a larger network through referrals.
      • Alumni already know what is required to be successful in the organization so they can refer more suitable candidates.

      Make use of a campus recruiting program

      Internal Talent Mobility (ITM) Program

      Social Media Program

      Employee Referral Program

      Alumni Program

      Campus Recruiting Program

      Other Sourcing Tactics

      What is it? A formalized means of attracting and hiring individuals who are about to graduate from schools, colleges, or universities.

      Almost 70% of companies are looking to employ new college graduates every year (HR Shelf, 2022).

      Campus recruitment benefits:

      • Increases employer brand awareness among talent entering the workforce.
      • Provides the opportunity to interact with large groups of potential candidates at one time.
      • Presents the opportunity to identify and connect with high-quality talent before they graduate and are actively looking for positions.
      • Offers access to a highly diverse audience.

      Info-Tech Insight

      Target schools that align with your culture and needs. Do not just focus on the most prestigious schools: they are likely more costly, have more intense competition, and may not actually provide the right talent.

      Identify opportunities to integrate non-traditional techniques

      Internal Talent Mobility (ITM) Program

      Social Media Program

      Employee Referral Program

      Alumni Program

      Campus Recruiting Program

      Other Sourcing Tactics

      1. Professional industry associations
      • Tap into candidates who have the necessary competencies.

      5. Not-for-profit intermediaries

      • Partner with not-for-profits to tap into candidates in training or mentorship programs.
      • Example:
        • Year Up (General)
        • Bankwork$ (Banking)
        • Youth Build (Construction)
        • iFoster (Grocery)

      American Expresscreated a boot camp for software engineers in partnership with Year Up and Gateway Community College to increase entry-level IT hires.

      Results:

      • Annually hire 80-100 interns from Year Up.
      • Improved conversion rates: 72% of Year Up interns versus 60% of traditional interns.
      • Increased retention: 44 (Year Up) versus 18 months (traditional).
      (HBR, 2016)

      2. Special interest groups

      • Use for niche role sourcing.
      • Find highly specialized talent.
      • Drive diversity (Women in Project Management).

      6. Gamification

      • Attract curiosity and reaffirm innovation at your organization.
      • Communicate the EVP.
      3. Customers
      • Access those engaged with the organization.
      • Add the employer brand to existing messaging.

      PwC (Hungary) created Multiploy, a two-day game that allows students to virtually experience working in accounting or consulting at the organization.

      Results:

      • 78% of students said they wanted to work for PwC.
      • 92% indicated they had a more positive view of the firm.
      • Increase in the number of job applicants.
      (Zielinski, 2015)

      4. Exit interviews

      • Ask exiting employees “where should we recruit someone to replace you?”
      • Leverage their knowledge to glean insight into where to find talent.

      Partner with other organizational functions to build skills and leverage existing knowledge

      Use knowledge that already exists in the organization to improve talent sourcing capabilities.

      Marketing

      HR

      Marketing knows how to:

      • Build attention-grabbing content.
      • Use social media platforms effectively.
      • Effectively promote a brand.
      • Use creative methods to connect with people.

      HR knows how to:

      • Organize recruitment activities.
      • Identify the capabilities of various technologies available to support sourcing.
      • Solve issues that may arise along the way

      To successfully partner with other departments in your organization:

      • Acknowledge that they are busy. Like IT, they have multiple competing priorities.
      • Present your needs and prioritize them. Create a list of what you are looking for and then be willing to just pick your top need. Work with the other department to decide what needs can and cannot be met.
      • Present the business case. Emphasize how partnering is mutually beneficial. For example, illustrate to Marketing that promoting a strong brand with candidates will improve the organization’s overall reputation because often, candidates are customers.
      • Be reasonable and patient. You are asking for help, so be moderate in your expectations and flexible in working with your partner.

      Info-Tech Insight

      Encourage your team to seek out, and learn from, employees in different divisions. Training sessions with the teams may not always be possible but one-on-one chats can be just as effective and may be better received.

      5.1 Review the effectiveness of existing sourcing programs

      1. As a group review the description of each program as defined on previous slides. Ensure that everyone understands the definitions.
      2. In your workbook, look for the cell Internal Talent Mobility under the title; you will find five rows with the following
      • This program is formally structured and documented.
      • This program is consistently applied across the organization.
      • Talent is sourced this way on an ad hoc basis.
      • Our organization currently does not source talent this way.
      • There are metrics in place to assess the effectiveness of this program.
    • Ask everyone in the group if they agree with the statement for each column; once everyone has had a chance to answer each of the questions, discuss any discrepancies which exist.
    • After coming to a consensus, record the answers.
    • Repeat this process for the other four sourcing programs (social media, employee referral program, alumni network program, and campus recruiting program).
    • InputOutput
      • Existing knowledge on sourcing approach
      • Low usage sourcing methods identified for development
      MaterialsParticipants
      • Workbook
      • Hiring Managers

      Want to learn more?

      Recruit IT Talent

      • Improve candidate experience to hire top IT talent.

      Recruit and Retain More Women in IT

      • Gender diversity is directly correlated to IT performance.

      Recruit and Retain People of Color in IT

      • Good business, not just good philanthropy.

      Enhance Your Recruitment Strategies

      Interviews are the most often used yet poorly executed hiring tool.

      Create a high-quality interview process to improve candidate assessment

      Everyone believes they’re a great interviewer; self-assess your techniques, and “get real” to get better

      If you…

      • Believe everything the candidate says.
      • Ask mostly hypothetical questions: "What would you do in a situation where…"
      • Ask gimmicky questions: "If you were a vegetable, what vegetable would you be?"
      • Ask only traditional interview questions: "What are your top three strengths?”
      • Submit to a first impression bias.
      • Have not defined what you are looking for before the interview.
      • Ignore your gut feeling in an attempt to be objective.
      • Find yourself loving a candidate because they are just like you.
      • Use too few or too many interviewers in the process.
      • Do not ask questions to determine the motivational fit of the candidate.
      • Talk more than the interviewee.
      • Only plan and prepare for the interview immediately before it starts.

      …then stop. Use this research!

      Most interviewers are not effective, resulting in many poor hiring decisions, which is costly and counter-productive

      Most interviewers are not effective…

      • 82% of organizations don’t believe they hire highly talented people (Trost, 2022).
      • Approximately 76% of managers and HR representatives that McLean & Company interviewed agreed that the majority of interviewers are not very effective.
      • 66% of hiring managers come to regret their interview-based hiring decisions (DDI, 2021).

      …because, although everyone knows interviewing is a priority, most don’t make it one.

      • Interviewing is often considered an extra task in addition to an employee’s day-to-day responsibilities, and these other responsibilities take precedence.
      • It takes time to effectively design, prepare for, and conduct an interview.
      • Employees would rather spend this time on tasks they consider to be an immediate priority.

      Even those interviewers who are good at interviewing, may not be good enough.

      • Even a good interviewer can be fooled by a great interviewee.
      • Some interviewees talk the talk, but don’t walk the walk. They have great interviewing abilities but not the skills required to be successful in the specific position for which they are interviewing.
      • Even if the interviewer is well trained and prepared to conduct a strong interview, they can get caught up with an interviewee that seems very impressive on the surface, and end up making a bad hire.

      Preparing the Perfect Interview

      Step 5: Define decision rights

      Establish decision-making authority and veto power to mitigate post-interview conflicts over who has final say over a candidate’s status.

      Follow these steps to create a positive interview experience for all involved.

      Step 1: Define the ideal candidate profile; determine the attributes of the ideal candidate and their relative importance

      Define the attributes of the ideal candidate…

      Ideal candidate = Ability to do the job + Motivation to do the job + Fit

      Competencies

      • Education
      • Credentials
      • Technical skills
      • Career path
      • Salary expectations
      • Passion
      • Potential
      • Personality
      • Managerial style/preference

      Experiences

      • Years of service
      • Specific projects
      • Industry

      Data for these come from:

      • Interviews
      • Personality tests
      • Gut instinct or intuition

      Data for these come from:

      • Resumes
      • Interviews
      • Exercises and tests
      • References

      Caution: Evaluating for “organizational or cultural fit” can lead to interviewers falling into the trap of the “like me” bias, and excluding diverse candidates.

      …then determine the importance of the attributes.

      Non-negotiable = absolutely required for the job!

      Usually attributes that are hard to train, such as writing skills, or expensive to acquire after hire, such as higher education or specific technical skills.

      An Asset

      Usually attributes that can be trained, such as computer skills. It’s a bonus if the new hire has it.

      Nice-to-have

      Attributes that aren’t necessary for the job but beneficial. These could help in breaking final decision ties.

      Deal Breakers: Also discuss and decide on any deal breakers that would automatically exclude a candidate.

      The job description is not enough; meet with stakeholders to define and come to a consensus on the ideal candidate profile

      Definition of the Ideal Candidate

      • The Hiring Manager has a plan for the new hire and knows the criteria that will best fulfill that mandate.
      • The Executive team may have specific directives for what the ideal candidate should look like, depending on the level and critical nature of the position.
      • Industry standards, which are defined by regulatory bodies, are available for some positions. Use these to identify skills and abilities needed for the job.
      • Competitor information such as job descriptions and job reviews could provide useful data about a similar role in other organizations.
      • Exit interviews can offer insight into the most challenging aspects of the job and identify skills or abilities needed for success.
      • Current employees who hold the same or a similar position can explain the nuances of the day-to-day job and what attributes are most needed on the team.

      “The hardest work is accurately defining what kind of person is going to best perform this job. What are their virtues? If you’ve all that defined, the rest is not so tough.”

      – VP, Financial Services

      Use a scorecard to document the ideal candidate profile and help you select a superstar

      1. Download the Workbook and go to tab 6.1.
      2. Document the desired attributes for each category of assessment: Competencies, Experiences, Fit, and Motivation. You can find an Attribute Library on the next tab.
      3. Rank each attribute by level of priority: Required, Asset, or Nice-to-Have.
      4. Identify deal breakers that would automatically disqualify a candidate from moving forward.
      InputOutput
      • Job description
      • Stakeholder input
      • Ideal candidate persona
      MaterialsParticipants
      • Workbook
      • Hiring Managers

      To identify questions for screening interviews, use the Screening Interview Template

      A screening interview conducted by phone should have a set of common questions to identify qualified candidates for in-person interviews.

      The Screening Interview Template will help you develop a screening interview by providing:

      • Common screening questions that can be modified based on organizational needs and interview length.
      • Establishing an interview team.
      • A questionnaire format so that the same questions are asked of all candidates and responses can be recorded.

      Once completed, this template will help you or HR staff conduct candidate screening interviews with ease and consistency. Always do screening interviews over the phone or via video to save time and money.

      Info-Tech Insight

      Determine the goal of the screening interview – do you want to evaluate technical skills, communication skills, attitude, etc.? – and create questions based on this goal. If evaluating technical skill, have someone with technical competency conduct the interview.

      The image contains screenshots of the Screening Interview Template.

      Step 2: Choose interview types and techniques that best assess the ideal candidate attributes listed on the position scorecard

      There is no best interview type or technique for assessing candidates, but there could be a wrong one depending on the organization and job opening.

      • Understanding common interviewing techniques and types will help inform your own interviewing strategy and interview development.
      • Each interview technique and type has its own strengths and weakness and can be better suited for a particular organizational environment, type of job, or characteristic being assessed.
      The image contains a diagram to demonstrate the similarities and differences of Interview Technique and Interview Type. There is a Venn Diagram, the right circle is labelled: Interview Technique, and the right is: Interview Type. There is a double sided arrow below that has the following text: Unstructure, Semi-Structured, and Structured.

      Unstructured: A traditional method of interviewing that involves no constraints on the questions asked, no requirements for standardization, and a subjective assessment of the candidate. This format is the most prone to bias.

      Semi-Structured: A blend of structured and unstructured, where the interviewer will ask a small list of similar questions to all candidates along with some questions pertaining to the resume.

      Structured: An interview consisting of a standardized set of job-relevant questions and a scoring guide. The goal is to reduce interviewer bias and to help make an objective and valid decision about the best candidate.

      No matter which interview types or techniques you use, aim for it to be as structured as possible to increase its validity

      The validity of the interview increases as the degree of interview structure increases.

      Components of a highly structured interview include:

      1. Interview questions are derived from a job analysis (they are job related).
      2. Interview questions are standardized (all applicants are asked the same questions).
      3. Prompting, follow-up questioning, probing, and/or elaboration on questions are limited. Try to identify all prompts, follow-ups, and probes beforehand and include them in the interview guide so that all candidates get the same level of prompting and probing.
      4. Interview questions focus on behaviors or work samples rather than opinions or self-evaluations.
      5. Interviewer access to ancillary information (e.g. resumes, letters of reference, test scores, transcripts) is controlled. Sometimes limiting access to these documents can limit interviewer biases.
      6. Questions from the candidate are not allowed until after the interview. This allows the interviewer to stay on track and not go off the protocol.
      7. Each answer is rated during the interview using a rating scale tailored to the question (this is preferable to rating dimensions at the end of the interview and certainly preferable to just making an overall rating or ranking at the end).
      8. Rating scales are “anchored” with behavioral examples to illustrate scale points (e.g. examples of a “1,” “3,” or “5” answer).
      9. Total interview score is obtained by summing across scores for each of the questions.

      The more of these components your interview has, the more structured it is, and the more valid it will be.

      Step 3: Prepare interview questions to assess the attributes you are looking for in a candidate

      The purpose of interviewing is to assess, not just listen. Questions are what help you do this.

      Preparing questions in advance allows you to:

      • Match each question to a position requirement (included in your scorecard) to ensure that you assess all required attributes. Everything assessed should be job relevant!
      • Determine each question’s weighting, if applicable.
      • Give each candidate a chance to speak to all their job-relevant attributes.
      • Keep records should an unselected candidate decide to contest the decision.

      If you don’t prepare in advance:

      • You’ll be distracted thinking about what you are going to ask next and not be fully listening.
      • You likely won’t ask the same questions of all candidates, which impacts the ability to compare across candidates and doesn’t provide a fair process for everyone.
      • You likely won’t ask the questions you need to elicit the information needed to make the right decision.
      • You could ask illegal questions (see Acquire the Right Hires with Effective Interviewing for a list of questions not to ask in an interview).

      Use the Interview Question Planning Guide tab in the Candidate Interview Strategy and Planning Guide to prepare your interview questions.

      Use these tips to draft interview questions:

      • Use job analysis output, in particular the critical incident technique, to develop structured interview questions.
      • Search online or in books for example interview questions for the target position to inform interview question development. Just remember that candidates access these too, so be sure to ask for specific examples, include probing questions, and adapt or modify questions to change them.
      • Situational questions: The situation should be described in sufficient detail to allow an applicant to visualize it accurately and be followed by “what would you do?” Scoring anchors should reflect effective, typical, and ineffective behaviors.
      • Behavioral questions: Should assess a behavioral dimension (e.g. meeting deadlines) and apply to a variety of situations that share the underlying dimension (e.g. at work or school). Scoring anchors should be applicable to a variety of situations and reflect effective, typical, and ineffective behavior.

      Conduct an effective screening interview by listening to non-verbal cues and probing

      Follow these steps to conduct an effective screening interview:

      Introduce yourself and ask if now is a good time to talk. (Before calling, prepare your sales pitch on the organization and the position.)

      You want to catch candidates off guard so that they don’t have time to prepare scripted answers; however, you must be courteous to their schedule.

      Provide an overview of the position, then start asking pre-set questions. Take a lot of notes.

      It is important to provide candidates with as much information as possible about the position – they are deciding whether they are interested in the role as much as you are deciding whether they are suitable.

      Listen to how the questions are answered. Ask follow-up questions when appropriate and especially if the candidate seems to be holding something back.

      If there are long pauses or the candidate’s voice changes, there may be something they aren’t telling you that you should know.

      Be alert to inconsistencies between the resume and answers to the questions and address them.

      It’s important to get to the bottom of issues before the in-person interview. If dates, titles, responsibilities, etc. seem to be inconsistent, ask more questions.

      Ask candidates about their salary expectations.

      It’s important to ensure alignment of the salary expectations early on. If the expectations are much higher than the range, and the candidate doesn’t seem to be open to the lower range, there is no point interviewing them. This would be a waste of everyone’s time.

      Answer the applicant’s questions and conclude the interview.

      Wait until after the interview to rate the applicant.

      Don’t allow yourself to judge throughout the interview, or it could skew questions. Rate the applicant once the interview is complete.

      When you have a shortlist of candidates to invite to an in-person interview, use the Candidate Communication Template to guide you through proper phone and email communications.

      Don’t just prepare top-level interview questions; also prepare probing questions to probe to gain depth and clarity

      Use probing to drill down on what candidates say as much as possible and go beyond textbook answers.

      Question (traditional): “What would you identify as your greatest strength?”

      Answer: Ability to work on a team.

      Top-level interview questions set the stage for probing.

      Your interview script should contain the top two levels of questions in the pyramid and a few probes that you will likely need to ask. You can then drill down further depending on the candidate’s answers.

      Follow-Up Question:

      “Can you outline a particular example when you were able to exercise your teamwork skills to reach a team goal?”

      Probing questions start with asking what, when, who, why, and how, and gain insight into a candidate’s thought process, experiences, and successes.

      Probing Level 1:

      Probe around the what, how, who, when, and where. “How did you accomplish that?”

      How to develop probes? By anticipating the kinds of responses that candidates from different backgrounds or with different levels of experience are likely to give as a response to an interview question. Probes should provide a clear understanding of the situation, the behavior, and the outcome so that the response can be accurately scored. Common probes include:

      • What did you do? What was the outcome?
      • When did this take place (and how long did it take)?
      • Who was involved?
      • Were you leading or being led?
      • How did you accomplish what you did?
      • Why did you take those steps?

      Tailor probes to the candidate’s answers to evoke meaningful and insightful responses.

      Probing Level 2:

      Allow for some creativity.

      “What would you do differently if you were to do it again?”

      Conduct effective interviews and assessments

      Mitigate inherent biases of assessors by integrating formal assessments with objective anchors and clear criteria to create a more inclusive process.

      Consider leveraging behavioral interview questions in your interview to reduce bias.

      • In the past, companies were pushing the boundaries of the conventional interview, using unconventional questions to find top talent, e.g. “what color is your personality?” The logic was that the best people are the ones who don’t necessarily show perfectly on a resume, and they were intent on finding the best.
      • However, many companies have stopped using these questions after extensive statistical analysis revealed there was no correlation between candidates’ ability to answer them and their future performance on the job.
      • Asking behavioral interview questions based on the competency needs of the role is the best way to uncover if the candidates will be able to execute on the job.

      Assessments are created by people that have biases. This often means that assessments can be biased, especially with preferences towards a Western perspective. Even if the same assessments are administered, the questions will be interpreted differently by candidates with varying cultural backgrounds and lived experiences. If assessments do not account for this, it ultimately leads to favoring the answers of certain demographic groups, often ones similar to those who developed the assessment.

      Creating an interview question scorecard

      Attribute you are evaluating

      Probing questions prepared

      Area to take notes

      The image contains a screenshot of an Interview question scorecard.

      Exact question you will ask

      Place to record score

      Anchored scale with definitions of a poor, ok and great answer

      Step 4: Assemble an interview team

      HR and the direct reporting supervisor should always be part of the interview. Make a good impression with a good interview team.

      The must-haves:

      • The Future Manager should always be involved in the process. They should be comfortable with the new hire’s competencies and fit.
      • Human Resources should always be involved in the process – they maintain consistency, legality, and standardization. It’s their job to know the rules and follow them. HR may coordinate and maintain policy standards and/or join in assessing the candidate.
      • There should always be more than just one interviewer, even if it is not at the same time. This helps keep the process objective, allows for different opinions, and gives the interviewee exposure to multiple individuals in the company. But, try to limit the number of panel members to four or less.

      “At the end of the day, it’s the supervisor that has to live with the person, so any decision that does not involve the supervisor is a very flawed process.” – VP, Financial Services

      The nice-to-haves:

      • Future colleagues can offer benefits to both the interviewee and the colleague by:
        • Giving the candidate some insight into what their day-to-day job would be.
        • Relaxing the candidate; allowing for a less formal, less intimidating conversation.
        • Introducing potential teammates for a position that is highly collaborative.
        • Offering the interviewer an excellent professional development opportunity – a chance to present their understanding of what they do.
      • Executives should take part in interviewing for executive hiring, individuals that will report to an executive, or for positions that are extremely important. Executive time is scarce and expensive, so only use it when absolutely necessary.

      Record the interview team details in the Candidate Interview Strategy and Planning Guide template.

      Assign interviewers roles inside and outside the actual interview

      Define Interview Process Roles

      Who Should… Contact candidates to schedule interviews or communicate decisions?

      Who Should… Be responsible for candidate welcomes, walk-outs, and hand-offs between interviews?

      Who Should… Define and communicate each stakeholder’s role?

      Who Should… Chair the preparation and debrief meetings and play the role of the referee when trying to reach a consensus?

      Define Interview Roles

      • Set a role for each interviewer so they know what to focus on and where they fit into the process (e.g. Interviewer A will assess fit). Don’t ad hoc the process and allow everyone to interview based on their own ideas.
      • Consider interviewer qualifications and the impact of the new employee on each interviewer, when deciding the roles of each interviewer (i.e. who will interview for competency and who will interview for fit).
        • For example, managers may be most impacted by technical competencies and should be the interviewer to evaluate the candidate for technical competency.

      “Unless you’ve got roles within the panel really detailed and agreed upon, for example, who is going to take the lead on what area of questions, you end up with a situation where nobody is in charge or accountable for the final interview assessment." – VP, Financial Services

      Info-Tech Insight

      Try a Two Lens Assessment: One interviewer assesses the candidate as a project leader while another assesses them as a people leader for a question such as “Give me an example of when you exercised your leadership skills with a junior team member.”

      Step 5: Set decision rights in stone and communicate them in advance to manage stakeholder expectations and limit conflict

      All interviewers must understand their decision-making authority prior to the interview. Misunderstandings can lead to resentment and conflict.

      It is typical and acceptable that you, as the direct reporting manager, should have veto power, as do some executives.

      Veto Power

      Direct Supervisor or Manager

      Decision Makers: Must Have Consensus

      Other Stakeholders

      Direct Supervisor’s Boss

      Direct Supervisor

      Contributes Opinion

      HR Representative

      Peer

      After the preliminary interview, HR should not be involved in making the decision unless they have a solid understanding of the position.

      Peers can make an unfair assessment due to perceived competition with a candidate. Additionally, if a peer doesn’t want a candidate to be hired and the direct supervisor does hire the candidate, the peer may hold resentment against that candidate and set the team up for conflict.

      The decision should rest on those who will interact with the candidate on a daily basis and who manage the team or department that the candidate will be joining.

      The decisions being made can include whether or not to move a candidate onto the next phase of the hiring process or a final hiring decision. Deciding decision rights in advance defines accountability for an effective interview process.

      Create your interview team, assessments, and objective anchor scale

      1. Download the Behavioral Interview Question Library as a reference.
      2. On tab 9 of your workbook, document all the members of the team and their respective roles in the interview process. Fill in the decision-making authority section to ensure every team member is held accountable to their assigned tasks and understands how their input will be used.
      3. For each required attribute in the Ideal Candidate Scorecard, chose one to two questions from the library that can properly evaluate that attribute.
      4. Copy and paste the questions and probing questions into the Interview Guide Template.
      5. Create an objective anchor scale and clearly define what a poor, ok, and great answer to each question is.

      Download the Behavioral Interview Question Library

      Input Output
      • List of possible team members
      • Ideal Candidate Scorecard
      • Finalized hiring panel
      • Finalized interview and assessment process
      Materials Participants
      • IT Behavioral Interview Question Library
      • Workbook
      • Interview Guide Template
      • IT leadership team
      • IT staff members

      Conduct an effective, professional, and organized in-person interview

      Give candidates a warm, genuine greeting. Introduce them to other interviewers present. Offer a drink. Make small talk.

      “There are some real advantages to creating a comfortable climate for the candidate; the obvious respect for the individual, but people really let their guard down.”

      – HR Director, Financial Services

      Give the candidate an overview of the process, length, and what to expect of the interview. Indicate to the candidate that notes will be taken during the interview.

      If shorter than an hour, you probably aren’t probing enough or even asking the right questions. It also looks bad to candidates if the interview is over quickly.

      Start with the first question in the interview guide and make notes directly on the interview guide (written or typed) for each question.

      Take lots of notes! You think you’ll remember what was said, but you won’t. It also adds transparency and helps with documentation.

      Ask the questions in the order presented for interview consistency. Probe and clarify as needed (see next slide).

      Keep control of the interview by curtailing any irrelevant or long-winded responses.

      After all interview questions are complete, ask candidates if there was anything about their qualifications that was missed that they want to highlight.

      Lets you know they understand the job and gives them the feeling they’ve put everything on the table.

      Ask if the candidate has any questions. Respond to the questions asked.

      Answer candidate questions honestly because fit works both ways. Ensure candidates leave with a better sense of the job, expectations, and organizational culture.

      Review the compensation structure for the position and provide a realistic preview of the job and organization.

      Provide each candidate with a fair chance by maintaining a consistent interview process.

      Tell interviewees what happens next in the process, the expected time frame, and how they will be informed of the outcome. Escort them out and thank them for the interview.

      The subsequent slides provide additional detail on these eight steps to conducting an effective interview.

      Avoid these common biases and mistakes

      Common Biases

      Like-me effect: An often-unconscious preference for, and unfairly positive evaluation of, a candidate based on shared interests, personalities, and experiences, etc.

      Status effect: Overrating candidates based on the prestige of previously held positions, titles, or schools attended.

      Recency bias: Placing greater emphasis on interviews held closer to the decision-making date.

      Contrast effect: Rating candidates relative to those who precede or follow them during the interview process, rather than against previously determined data.

      Solution

      Assess candidates by using existing competency-based criteria.

      Common Mistakes

      Negative tone: Starting the interview on a negative or stressful note may derail an otherwise promising candidate.

      Poor interview management: Letting the candidate digress may leave some questions unanswered and reduce the interview value.

      Reliance of first impressions: Basing decisions on first impressions undermines the objectivity of competency-based selection.

      Failure to ask probing questions: Accepting general answers without asking follow-up questions reduces the evidentiary value of the interview.

      Solution

      Follow the structured interview process you designed and practiced.

      Ask the questions in the order presented in the interview guide, and probe and clarify as needed

      Do...

      Don’t…

      Take control of the interview by politely interrupting to clarify points or keep the interviewee on topic.

      Use probing to drill down on responses and ask for clarification. Ask who, what, when, why, and how.

      Be cognizant of confidentiality issues. Ask for a sample of work from a past position.

      Focus on knowledge or information gaps from previous interviews that need to be addressed in the interview.

      Ensure each member of a panel interview speaks in turn and the lead is given due respect to moderate.

      Be mean when probing. Intimidation actually works against you and is stressful for candidates. When you’re friendly, candidates will actually open up more.

      Interrupt or undermine other panel members. Their comments and questions are just as valid as yours are, and treating others unprofessionally gives a bad impression to the candidate.

      Ask illegal questions. Questions about things like religion, disability, and marital and family status are off limits.

      When listening to candidate responses, watch for tone, body language, and red flags

      Do...

      While listening to responses, also watch out for red and yellow flags.

      Listen to how candidates talk about their previous bosses – you want it to be mainly positive. If their discussion of past bosses reflects a strong sense of self-entitlement or a consistent theme of victimization, this could be a theme in their behavior and make them hard to work with.

      Red Flag

      A concern about something that would keep you from hiring the person.

      Yellow Flag

      A concern that needs to be addressed, but wouldn’t keep you from hiring the person.

      Pay attention to body language and tone. They can tell you a lot about candidate motivation and interest.

      Listen to what candidates want to improve. It’s an opportunity to talk about development and advancement opportunities in the organization.

      Not all candidates have red flags, but it is important to keep them in mind to identify potential issues with the candidate before they are hired.

      Don’t…

      Talk too much! You are there to listen. Candidates should do about 80% of the talking so you can adequately evaluate them. Be friendly, but ensure to spend the time allotted assessing, not chatting.

      If you talk too much, you may end up hiring a weak candidate because you didn’t perceive weaknesses or not hire a strong candidate because you didn’t identify strengths.

      What if you think you sense a red or yellow flag?

      Following the interview, immediately discuss the situation with others involved in the recruitment process or those familiar with the position, such as HR, another hiring manager, or a current employee in the role. They can help evaluate if it’s truly a matter of concern.

      Increase hiring success: Give candidates a positive perception of the organization in the interview

      Great candidates want to work at great organizations.

      When the interviewer makes a positive impression on a candidate and provides a positive impression of the organization it carries forward after they are hired.

      In addition, better candidates can be referred over the course of time due to higher quality networking.

      As much as choosing the right candidate is important to you, make sure the right candidate wants to choose you and work for your organization.

      The image contains a screenshot of a graph to demonstrate the percent of successful hires relates strongly to interviewers giving candidates a positive perception of the organization.

      Interview advice seems like common sense, but it’s often not heeded, resulting in poor interviews

      Don’t…

      Believe everything candidates say. Most candidates embellish and exaggerate to find the answers they think you want. Use probing to drill down to specifics and take them off their game.

      Ask gimmicky questions like “what color is your soul?” Responses to these questions won’t give you any information about the job. Candidates don’t like them either!

      Focus too much on the resume. If the candidate is smart, they’ve tailored it to match the job posting, so of course the person sounds perfect for the job. Read it in advance, highlight specific things you want to ask, then ignore it.

      Oversell the job or organization. Obviously you want to give candidates a positive impression, but don’t go overboard because this could lead to unhappy hires who don’t receive what you sold them. Candidates need to evaluate fit just as much as you.

      Get distracted by a candidate’s qualifications and focus only on their ability to do the job. Just because they are qualified does not mean they have the attitude or personality to fit the job or culture.

      Show emotion at any physical handicap. You can’t discriminate based on physical disability, so protect the organization by not drawing attention to it. Even if you don’t say anything, your facial expression may.

      Bring a bad day or excess baggage into the interview, or be abrupt, rushed, or uninterested in the interview. This is rude behavior and will leave a negative impression with candidates, which could impact your chances of hiring them.

      Submit to first impression bias because you’ll spend the rest of the interview trying to validate your first impression, wasting your time and the candidate’s. Remain as objective as possible and stick to the interview guide to stay focused on the task at hand.

      “To the candidate, if you are meeting person #3 and you’re hearing questions that person #1 and #2 asked, the company doesn’t look too hot or organized.” – President, Recruiting Firm

      Practice behavioral interviews

      1. In groups of at least three:
      • Assign one person to act as the manager conducting the interview, a second person to act as the candidate, and a third to observe.
      • The observer will provide feedback to the manager at the end of the role play based on the information you just learned.
      • Observers – please give feedback on the probing questions and body language.
    • Managers, select an interview question from the list your group put together during the previous exercise. Take a few minutes to think about potential probing questions you could follow up with to dig for more information.
    • Candidates, try to act like a real candidate. Please don’t make it super easy on the managers – but don’t make it impossible either!
    • Once the question has been asked and answered:
      • How did it go?
      • Were you able to get the candidate to speak in specifics rather than generalities? What tips do you have for others?
      • What didn’t go so well? Any surprises?
      • What would you do differently next time?
      • If this was a real hiring situation, would the information you got from just that one question help you make a hiring decision for the role?
    • Now switch roles and select a new interview question to use for this round. Repeat until everyone has had a chance to practice.
    • Input Output
      • Interview questions and scorecard
      • Practice interviews
      Materials Participants
      • IT Behavioral Interview Question Library
      • Workbook
      • Hiring Manager
      • Interview Panel Members

      Download the Behavioral Interview Question Library

      Record best practices, effective questions, and candidate insights for future use and current strategy

      Results and insights gained from evaluations need to be recorded and assessed to gain value from them going forward.

      • To optimize evaluation, all feedback should be forwarded to a central point so that the information can be shared with all stakeholders. HR can serve in this role.
      • Peer evaluations should be shared shortly after the interview. Immediate feedback that represents all the positive and negative responses is instructional for interviewers to consider right away.
      • HR can take a proactive approach to sharing information and analyzing and improving the interview process in order to collaborate with hiring departments for better talent management.
      • Collecting information about effective and ineffective interview questions will guide future interview revision and development efforts.

      Evaluations Can Inform Strategic Planning and Professional Development

      Strategic Planning

      • Survey data can be used to inform strategic planning initiatives in recruiting.
      • Use the information to build a case to the executive team for training, public relations initiatives, or better candidate management systems.

      Professional Development

      • Survey data from all evaluations should be used to inform future professional development initiatives.
      • Interview areas where all team members show weaknesses should be training priorities.
      • Individual weaknesses should be integrated into each professional development plan.

      Want to learn more?

      Recruit IT Talent

      • Improve candidate experience to hire top IT talent.

      Recruit and Retain More Women in IT

      • Gender diversity is directly correlated to IT performance.

      Recruit and Retain People of Color in IT

      • Good business, not just good philanthropy.

      Develop a Comprehensive Onboarding Plan

      Drive employee engagement and retention with a robust program that acclimates, guides, and develops new hires.

      Onboarding should pick up where candidate experience leaves off

      Do not confuse onboarding with orientation

      Onboarding ≠ Orientation

      Onboarding is more than just orientation. Orientation is typically a few days of completing paperwork, reading manuals, and learning about the company’s history, strategic goals, and culture. By contrast, onboarding is three to twelve months dedicated to welcoming, acclimating, guiding, and developing new employees – with the ideal duration reflecting the time to productivity for the role.

      A traditional orientation approach provides insufficient focus on the organizational identification, socialization, and job clarity that a new hire requires. This is a missed opportunity to build engagement, drive productivity, and increase organizational commitment. This can result in early disengagement and premature departure.

      Effective onboarding positively impacts the organization and bottom line

      Over the long term, effective onboarding has a positive impact on revenue and decreases costs.

      The benefits of onboarding:

      • Save money and frustration
        • Shorten processing time, reduce administrative costs, and improve compliance.
      • Boost revenue
        • Help new employees become productive faster – also reduce the strain on existing employees who would normally be overseeing them or covering a performance shortfall.
      • Drive engagement and reduce turnover
        • Quickly acclimate new hires to your organization’s environment, culture, and values.
      • Reinforce culture and employer brand
        • Ensure that new hires feel a connection to the organization’s culture.

      Onboarding drives new hire engagement from day one

      The image contains a graph to demonstrate the increase in overall engagement in relation to onboarding.

      When building an onboarding program, retain the core aims: acclimate, guide, and develop

      The image contains a picture of a circle with a smaller circle inside it, and a smaller circle inside that one. The smallest circle is labelled Acclimate, the medium sized circle is labelled Guide, and the biggest circle is labelled Develop.

      Help new hires feel connected to the organization by clearly articulating the mission, vision, values, and what the company does. Help them understand the business model, the industry, and who their competitors are. Help them feel connected to their new team members by providing opportunities for socialization and a support network.

      Help put new hires on the path to high performance by clearly outlining their role in the organization and how their performance will be evaluated.

      Help new hires receive the experience and training they require to become high performers by helping them build needed competencies.

      We recommend a three-to-twelve-month onboarding program, with the performance management aspect of onboarding extending out to meet the standard organizational performance management cycle.

      Info-Tech Insight

      The length of the onboarding program should align with the average time to productivity for the role(s). Consider the complexity of the role, the industry, and the level of the new hire when determining program length.

      For example, call center workers who are selling a straight-forward product may only require a three-month onboarding, while senior leaders may require a year-long program.

      Watch for signs that you aren’t effectively acclimating, guiding, and developing new hires

      Our primary and secondary research identified the following as the most commonly stated reasons why employees leave organizations prematurely. These issues will be addressed throughout the next section.

      Acclimate

      Guide

      Develop

      • Onboarding experience is misaligned from the employer’s brand.
      • Socialization and/or integration into the existing culture is left to the employee.
      • Key role expectations or role usefulness is not clearly communicated.
      • Company strategy is unclear.
      • Opportunities for advancement are unclear.
      • Coaching, counseling, and/or support from co-workers and/or management is lacking.
      • The organization fails to demonstrate that it cares about the new employee’s needs.

      “Onboarding is often seen as an entry-level HR function. It needs to rise in importance because it’s the first impression of the organization and can be much more powerful than we sometimes give it credit for. It should be a culture building and branding program.” – Doris Sims, SPHR, The Succession Consultant, and Author, Creative Onboarding Programs

      Use the onboarding tabs in the workbook to evaluate and redesign the onboarding program

      1. On tab 10, brainstorm challenges that face the organization's current onboarding program. Identify if they fall into the "acclimate," "guide," or "develop" category. Next, record the potential impact of this challenge on the overall effectiveness of the onboarding program.
      2. On tab 11, record each existing onboarding activity. Then, identify if that activity will be kept or if it should be retired. Next, document if the activity fell into the "acclimate," "guide," or "develop" category.
      3. On tab 12, document gaps that currently exist in the onboarding program. Modify the timeline along the side of the tab to ensure it reflects the timeline you have identified.
      4. On tab 13, document the activities that will occur in the new onboarding program. This should be a combination of current activities that you want to retain and new activities that will be added to address the gaps noted on tab 12. For each activity, identify if it will fall in the acclimate, guide, or develop section. Add any additional notes. Before moving on, make sure that there are no categories that have no activities (e.g. no guide activities).
      Input Output
      • Existing onboarding activities
      • Determine new onboarding activities
      • Map out onboarding responsibilities
      Materials Participants
      • Workbook
      • Hiring Managers
      • HR

      Review the administrative aspects of onboarding and determine how to address the challenges

      The image contains tabs, three main large tabs are labelled: Acclimate, Guide, and Develop. There are smaller tabs in between that are in relation to the three main ones.

      Sample challenges

      Potential solutions

      Some paperwork cannot be completed digitally (e.g. I-9 form in the US).

      Where possible, complete forms with digital signatures (e.g. DocuSign). Where not possible, begin the process earlier and mail required forms to employees to sign and return, or scan and email for the employee to print and return.

      Required compliance training material is not available virtually.

      Seek online training options where possible. Determine the most-critical training needs and prioritize the replication of materials in audio/video format (e.g. recorded lecture) and distribute virtually.

      Employees may not have access to their equipment immediately due to shipping or supply issues.

      Delay employee start dates until you can set them up with the proper equipment and access needed to do their job.

      New hires can’t get answers to their questions about benefits information and setup.

      Schedule a meeting with an HR representative or benefits vendor to explain how benefits will work and how to navigate employee self-service or other tools and resources related to their benefits.

      Info-Tech Insight

      One of the biggest challenges for remote new hires is the inability to casually ask questions or have conversations without feeling like they’re interrupting. Until they have a chance to get settled, providing formal opportunities for questions can help address this.

      Review how company information is shared during onboarding and how to address the challenges

      The image contains tabs, three main large tabs are labelled: Acclimate, Guide, and Develop. There are smaller tabs in between that are in relation to the three main ones.

      Sample challenges

      Potential solutions

      Key company information such as organizational history, charts, or the vision, mission, and values cannot be clearly learned by employees on their own.

      Have the new hire’s manager call to walk through the important company information to provide a personal touch and allow the new hire to ask questions and get to know their new manager.

      Keeping new hires up to date on crisis communications is important, but too much information may overwhelm them or cause unnecessary stress.

      Sharing the future of the organization is a critical part of the company information stage of onboarding and the ever-changing nature of the COVID-19 crisis is informing many organizations’ future right now. Be honest but avoid over-sharing plans that may change.

      New hires can’t get answers to their questions about benefits information and setup.

      Schedule a meeting with an HR representative or benefits vendor to explain how benefits will work and how to navigate employee self-service or other tools and resources related to their benefits.

      Review the socialization aspects of onboarding and determine how to address the challenges

      The image contains tabs, three main large tabs are labelled: Acclimate, Guide, and Develop. There are smaller tabs in between that are in relation to the three main ones.

      Sample challenges

      Potential solutions

      Team introductions via a team lunch or welcome event are typically done in person.

      Provide managers with a calendar of typical socialization events in the first few weeks of onboarding and provide instructions and ideas for how to schedule replacement events over videoconferencing.

      New hires may not have a point of contact for informal questions or needs if their peers aren’t around them to help.

      If it doesn’t already exist, create a virtual buddy program and provide instructions for managers to select a buddy from the new hire’s team. Explain that their role is to field informal questions about the company, team, and anything else and that they should book weekly meetings with the new hire to stay in touch.

      New hires will not have an opportunity to learn or become a part of the informal decision-making networks at the organization.

      Hiring managers should consider key network connections that new hires will need by going through their own internal network and asking other team members for recommendations.

      New hires will not be able to casually meet people around the office.

      Provide the employee with a list of key contacts for them to reach out to and book informal virtual coffee chats to introduce themselves.

      Adapt the Guide phase of onboarding to a virtual environment

      The image contains tabs, three main large tabs are labelled: Acclimate, Guide, and Develop. There are smaller tabs in between that are in relation to the three main ones.

      Sample challenges

      Potential solutions

      Performance management (PM) processes have been paused given the current crisis.

      Communicate to managers that new hires still need to be onboarded to the organization’s performance management process and that goals and feedback need to be introduced and the review process outlined even if it’s not currently happening.

      Goals and expectations differ or have been reprioritized during the crisis.

      Ask managers to explain the current situation at the organization and any temporary changes to goals and expectations as a result of new hires.

      Remote workers often require more-frequent feedback than is mandated in current PM processes.

      Revamp PM processes to include daily or bi-weekly touchpoints for managers to provide feedback and coaching for new hires for at least their first six months.

      Managers will not be able to monitor new hire work as effectively as usual.

      Ensure there is a formal approach for how employees will keep their managers updated on what they're working on and how it's going, for example, daily scrums or task-tracking software.

      For more information on adapting performance management to a virtual environment, see Info-Tech’s Performance Management for Emergency Work-From-Home research.

      Take an inventory of training and development in the onboarding process and select critical activities

      The image contains tabs, three main large tabs are labelled: Acclimate, Guide, and Develop. There are smaller tabs in between that are in relation to the three main ones.

      Categorize the different types of formal and informal training in the onboarding process into the following three categories. For departmental and individual training, speak to managers to understand what is required on a department and role basis:

      Organizational

      Departmental

      Individual

      For example:

      • Employee self-service overview
      • Health and safety/compliance training
      • Core competencies

      For example:

      • Software training (e.g. Salesforce)
      • Job shadowing to learn how to work equipment or to learn processes

      For example:

      • Mentoring
      • External courses
      • Support to work toward a certification

      In a crisis, not every training can be translated to a virtual environment in the short term. It’s also important to focus on critical learning activities versus the non-critical. Prioritize the training activities by examining the learning outcomes of each and asking:

      • What organizational training does every employee need to be a productive member of the organization?
      • What departmental or individual training do new hires need to be successful in their role?

      Lower priority or non-critical activities can be used to fill gaps in onboarding schedules or as extra activities to be completed if the new hire finds themselves with unexpected downtime to fill.

      Determine how onboarding training will be delivered virtually

      The image contains tabs, three main large tabs are labelled: Acclimate, Guide, and Develop. There are smaller tabs in between that are in relation to the three main ones.

      Who will facilitate virtual training sessions?

      • For large onboarding cohorts, consider live delivery via web conferencing where possible. This will create a more engaging training program and will allow new hires to interact with and ask questions of the presenter.
      • For individual new hires or small cohorts, have senior leaders or key personnel from across the organization record different trainings that are relevant for their role.
        • For example, training sessions about organizational culture can be delivered by the CEO or other senior leader, while sales training could be delivered by a sales executive.

        If there is a lack of resources, expertise, or time, outsource digital training to a content provider or through your LMS.

      What existing or free tools can be leveraged to immediately support digital training?

      • Laptops and PowerPoint to record training sessions that are typically delivered in-person
      • YouTube/Vimeo to host recorded lecture-format training
      • Company intranet to host links and files needed to complete training
      • Web conferencing software to host live training/orientation sessions (e.g. Webex)
      • LMS to host and track completion of learning content

      Want to learn more?

      Recruit IT Talent

      • Improve candidate experience to hire top IT talent.

      Recruit and Retain More Women in IT

      • Gender diversity is directly correlated to IT performance.

      Recruit and Retain People of Color in IT

      • Good business, not just good philanthropy.

      Adapt Your Onboarding Process to a Virtual Environment

      • Develop short-term solutions with a long-term outlook to quickly bring in new talent.

      Bibliography

      2021 Recruiter Nation Report. Survey Analysis, Jobvite, 2021. Web.

      “5 Global Stats Shaping Recruiting Trends.” The Undercover Recruiter, 2022. Web.

      Barr, Tavis, Raicho Bojilov, and Lalith Munasinghe. "Referrals and Search Efficiency: Who Learns What and When?" The University of Chicago Press, Journal of Labor Economics, vol. 37, no. 4, Oct. 2019. Web.

      “How to grow your team better, faster with an employee referral program.” Betterup, 10 Jan. 2022. Web.

      “Employee Value Proposition: How 25 Companies Define Their EVP.” Built In, 2021. Web.

      Global Leadership Forecast 2021. Survey Report, DDI World, 2021. Web.

      “Connecting Unemployed Youth with Organizations That Need Talent.” Harvard Business Review, 3 November 2016. Web.

      Ku, Daniel. “Social Recruiting: Everything You Need To Know for 2022.” PostBeyond, 26 November 2021. Web.

      Ladders Staff. “Shedding light on the job search.” Ladders, 20 May 2013. Web.

      Merin. “Campus Recruitment – Meaning, Benefits & Challenges.” HR Shelf, 1 February 2022. Web.

      Mobile Recruiting. Smart Recruiters, 2020. Accessed March 2022.

      Roddy, Seamus. “5 Employee Referral Program Strategies to Hire Top Talent.” Clutch, 22 April 2020. Web.

      Sinclair, James. “What The F*dge: That's Your Stranger Recruiting Budget?” LinkedIn, 11 November 2019. Web.

      “Ten Employer Examples of EVPs.” Workology, 2022. Web

      “The Higher Cost of a Bad Hire.” Robert Half, 15 March 2021. Accessed March 2022.

      Trost, Katy. “Hiring with a 90% Success Rate.” Katy Trost, Medium, 8 August 2022. Web.

      “Using Social Media for Talent Acquisition.” SHRM, 20 Sept. 2017. Web.

      Lead Strategic Decision Making With Service Portfolio Management

      • Buy Link or Shortcode: {j2store}397|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: Service Management
      • Parent Category Link: /service-management
      • There are no standardized processes for the intake of new ideas and no consistent view of the drivers needed to assess the value of these ideas.
      • IT is spending money on low-value services and doesn’t have the ability to understand and track value in order to prioritize IT investment.
      • CIOs are not trusted to drive innovation.

      Our Advice

      Critical Insight

      • The service portfolio empowers IT to be a catalyst in business strategy, change, and growth.
      • IT must drive value-based investment by understanding value of all services in the portfolio.
      • Organizations must assess the value of their services throughout their lifecycle to optimize business outcomes and IT spend.

      Impact and Result

      • Optimize IT investments by prioritizing services that provide more value to the business, ensuring that you do not waste money on low-value or out-of-date IT services.
      • Ensure that services are directly linked to business objectives, goals, and needs, keeping IT embedded in the strategic vision of the organization.
      • Enable the business to understand the impact of IT capabilities on business strategy.
      • Ensure that IT maintains a strategic and tactical view of the services and their value.
      • Drive agility and innovation by having a streamlined view of your business value context and a consistent intake of ideas.
      • Provide strategic leadership and create new revenue by understanding the relative value of new ideas vs. existing services.

      Lead Strategic Decision Making With Service Portfolio Management Research & Tools

      Start here – read the Executive Brief

      Service portfolio management enables organizations to become strategic value creators by establishing a dynamic view of service value. Understand the driving forces behind the need to manage services through their lifecycles.

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

      1. Establish the service portfolio

      Establish and understand the service portfolio process by setting up the Service Portfolio Worksheet.

      • Lead Strategic Decision Making With Service Portfolio Management – Phase 1: Establish the Service Portfolio
      • Service Portfolio Worksheet

      2. Develop a value assessment framework

      Use the value assessment tool to assess services based on the organization’s context of value.

      • Lead Strategic Decision Making With Service Portfolio Management – Phase 2: Develop a Value Assessment Framework
      • Value Assessment Tool
      • Value Assessment Example Tool

      3. Manage intake and assessment of initiatives

      Create a centralized intake process to manage all new service ideas.

      • Lead Strategic Decision Making With Service Portfolio Management – Phase 3: Manage Intake and Assessment of Initiatives
      • Service Intake Form

      4. Assess active services

      Continuously validate the value of the existing service and determine the future of service based on the value and usage of the service.

      • Lead Strategic Decision Making With Service Portfolio Management – Phase 4: Assess Active Services

      5. Manage and communicate the service portfolio

      Communicate and implement the service portfolio within the organization, and create a mechanism to seek out continuous improvement opportunities.

      • Lead Strategic Decision Making With Service Portfolio Management – Phase 5: Manage and Communicate the Service Portfolio
      [infographic]

      Workshop: Lead Strategic Decision Making With Service 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 Establish the Service Portfolio

      The Purpose

      Establish and understand the service portfolio process by setting up the Service Portfolio Worksheet.

      Understand at a high level the steps involved in managing the service portfolio.

      Key Benefits Achieved

      Adapt the Service Portfolio Worksheet to organizational needs and create a plan to begin documenting services in the worksheet.

      Activities

      1.1 Review the Service Portfolio Worksheet.

      1.2 Adapt the Service Portfolio Worksheet.

      Outputs

      Knowledge about the use of the Service Portfolio Worksheet.

      Adapt the worksheet to reflect organizational needs and structure.

      2 Develop a Value Assessment Framework

      The Purpose

      Understand the need for a value assessment framework.

      Key Benefits Achieved

      Identify the organizational context of value through a holistic look at business objectives.

      Leverage Info-Tech’s Value Assessment Tool to validate and determine service value.

      Activities

      2.1 Understand value from business context.

      2.2 Determine the governing body.

      2.3 Assess culture and organizational structure.

      2.4 Complete the value assessment.

      2.5 Discuss value assessment score.

      Outputs

      Alignment on value context.

      Clear roles and responsibilities established.

      Ensure there is a supportive organizational structure and culture in place.

      Understand how to complete the value assessment and obtain a value score for selected services.

      Understand how to interpret the service value score.

      3 Manage Intake and Assessment of Initiatives

      The Purpose

      Create a centralized intake process to manage all new service ideas.

      Key Benefits Achieved

      Encourage collaboration and innovation through a transparent, formal, and centralized service intake process.

      Activities

      3.1 Review or design the service intake process.

      3.2 Review the Service Intake Form.

      3.3 Design a process to assess and transfer service ideas.

      3.4 Design a process to transfer completed services to the service catalog.

      Outputs

      Create a centralized process for service intake.

      Complete the Service Intake Form for a specific initiative.

      Have a process designed to transfer approved projects to the PMO.

      Have a process designed for transferring of completed services to the service catalog.

      4 Assess Active Services

      The Purpose

      Continuously validate the value of existing services.

      Key Benefits Achieved

      Ensure services are still providing the expected outcome.

      Clear next steps for services based on value.

      Activities

      4.1 Discuss/review management of active services.

      4.2 Complete value assessment for an active service.

      4.3 Determine service value and usage.

      4.4 Determine the next step for the service.

      4.5 Document the decision regarding the service outcome.

      Outputs

      Understand how active services must be assessed throughout their lifecycles.

      Understand how to assess an existing service.

      Place the service on the 2x2 matrix based on value and usage.

      Understand the appropriate next steps for services based on value.

      Formally document the steps for each of the IRMR options.

      5 Manage and Communicate Your Service Portfolio

      The Purpose

      Communicate and implement the service portfolio within the organization.

      Key Benefits Achieved

      Obtain buy-ins for the process.

      Create a mechanism to identify changes within the organization and to seek out continuous improvement opportunities for the service portfolio management process and procedures.

      Activities

      5.1 Create a communication plan for service portfolio and value assessment.

      5.2 Create a communication plan for service intake.

      5.3 Create a procedure to continuously validate the process.

      Outputs

      Document the target audience, the message, and how the message should be communicated.

      Document techniques to encourage participation and promote participation from the organization.

      Document the formal review process, including cycle, roles, and responsibilities.

      First 30 Days Pandemic Response Plan

      • Buy Link or Shortcode: {j2store}418|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
      • Given the speed and scope of the spread of the pandemic, governments are responding with changes almost daily as to what organizations and people can and can’t do. This volatility and uncertainty challenges organizations to respond, particularly in the absence of a business continuity or crisis management plan.

      Our Advice

      Critical Insight

      • Assess the risk to and viability of your organization in order to create appropriate action and communication plans quickly.

      Impact and Result

      • HR departments must be directly involved in developing the organization’s pandemic response plan. Use Info-Tech's Risk and Viability Matrix and uncover the crucial next steps to take during the first 30 days of the COVID-19 pandemic.

      First 30 Days Pandemic Response Plan Research & Tools

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

      1. Create a response plan for the first 30 days of a pandemic

      Manage organizational risk and viability during the first 30 days of a crisis.

      • First 30 Days Pandemic Response Plan Storyboard
      • Crisis Matrix Communications Template: Business As Usual
      • Crisis Matrix Communications Template: Organization Closing
      • Crisis Matrix Communications Template: Manage Risk and Leverage Resilience
      • Crisis Matrix Communications Template: Reduce Labor and Mitigate Risk
      [infographic]

      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.

      Take the First Steps to Embrace Open-Source Software

      • Buy Link or Shortcode: {j2store}164|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: Development
      • Parent Category Link: /development

      Your organization is looking to invest in new software or a tool to solve key business and IT problems. They see open source as a viable option given the advertised opportunities and the popularity of many open-source projects, but they have concerns:

      • Despite the longevity and broad adoption of open-source software, stakeholders are hesitant about its long-term viability and the costs of ongoing support.
      • A clear direction and strategy are needed to align the expected value of open source to your stakeholders’ priorities and gain the funding required to select, implement, and support open-source software.

      Our Advice

      Critical Insight

      • Position open source in the same light as commercial software. The continuous improvement and evolution of popular open-source software and communities have established a reputation for reliability in the industry.
      • Consider open source as another form of outsource development. Open source is externally developed software where the code is accessible and customizable. Code quality may not align to your organization’s standards, which can require extensive testing and optimization.
      • Treat open source as any internally developed solution. Configurations, integrations, customizations, and orchestrations of open-source software are often done at the code level. While some community support is provided, most of the heavy lifting is done by the applications team.

      Impact and Result

      • Outline the value you expect to gain. Discuss current business and IT priorities, use cases, and value opportunities to determine what to expect from open-source versus commercial software.
      • Define your open-source selection criteria. Clarify the driving factors in your evaluation of open-source and commercial software using your existing IT procurement practices as a starting point.
      • Assess the readiness of your team. Clarify the roles, processes, and tools needed for the implementation, use, and maintenance of open-source software.

      Take the First Steps to Embrace Open-Source Software Research & Tools

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

      1. Take the First Steps to Embrace Open-Source Software Storyboard – A guide to learn the fit, value, and considerations of open-source software.

      This research walks you through the misconceptions about open source, factors to consider in its selection, and initiatives to prepare your teams for its adoption.

      • Take the First Steps to Embrace Open-Source Software Storyboard

      2. Open-Source Readiness Assessment – A tool to help you evaluate your readiness to embrace open-source software in your environment.

      Use this tool to identify key gaps in the people, processes, and technologies needed to support open source in your organization. It also contains a canvas to facilitate discussions about expectations with your stakeholders and applications teams.

      • Open-Source Readiness Assessment
      [infographic]

      Further reading

      Take the First Steps to Embrace Open-Source Software

      Begin to understand what is required to embrace open-source software in your organization.

      Analyst Perspective

      With great empowerment comes great responsibilities.

      Open-source software promotes enticing technology and functional opportunities to any organization looking to modernize without the headaches of traditional licensing. Many organizations see the value of open source in its ability to foster innovation, be flexible to various use cases and system configurations, and give complete control to the teams who are using and managing it.

      However, open source is not free. While the software is freely and easily accessible, its use and sharing are bound by its licenses, and its implementation requires technical expertise and infrastructure investments. Your organization must be motivated and capable of taking on the various services traditionally provided and managed by the vendor.

      Photo of Andrew Kum-Seun

      Andrew Kum-Seun
      Research Director,
      Application Delivery and Application Management
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      Your organization is looking to invest in new software or a tool to solve key business and IT problems. They see open source as a viable option because of the advertised opportunities and the popularity of many open-source projects.

      Despite the longevity and the broad adoption of open-source software, stakeholders are hesitant about its adoption, its long-term viability, and the costs of ongoing support.

      A clear direction and strategy is needed to align the expected value of open source to your stakeholders’ priorities and gain the funding required to select, implement, and support open-source software.

      Common Obstacles

      Your stakeholders’ fears, uncertainties, and doubts about open source may be driven by misinterpretation or outdated information. This hesitancy can persist despite some projects being active longer than their proprietary counterparts.

      Certain software features, support capabilities, and costs are commonly overlooked when selecting open-source software because they are often assumed in the licensing and service costs of commercial software.

      Open-source software is often technically complicated and requires specific skill sets and knowledge. Unfortunately, current software delivery capability gaps impede successful adoption and scaling of open-source software.

      Info-Tech’s Approach

      Outline the value you expect to gain. Discuss current business and IT priorities, use cases, and value opportunities to determine what to expect from open-source versus commercial software.

      Define your open-source selection criteria. Clarify the driving factors in your evaluation of open-source and commercial software using your existing IT procurement practices as a starting point.

      Assess the readiness of your team. Clarify the roles, processes, and tools needed for the implementation, use, and maintenance of open-source software.

      Insight Summary

      Overarching Info-Tech Insight

      Open source is as much about an investment in people as it is about technology. It empowers applications teams to take greater control over their technology and customize it as they see fit. However, teams need the time and funding to conduct the necessary training, management, and ongoing community engagement that open-source software and its licenses require.

      • Position open source in the same light as commercial software.
        The continuous improvement and evolution of popular open-source software and communities have established a trusting and reliable reputation in the industry. Open-source software quality and community support can rival similar vendor capabilities given the community’s maturity and contributions in the technology.
      • Consider open source another form of outsource development.
        Open source is externally developed software where the code is accessible and customizable. Code quality may not align to your organization’s standards, which can require extensive testing and optimization. A thorough analysis of change logs, code repositories, contributors, and the community is recommended – much to the same degree as one would do with prospective outsourcing partners.
      • Treat open source as any internally developed solution.
        Configurations, integrations, customizations, and orchestrations of open-source software are often done at the code level. While some community support is provided, most of the heavy lifting is done by the applications team. Teams must be properly resourced, upskilled, and equipped to meet this requirement. Otherwise, third-party partners are needed.

      What is open source?

      According to Synopsys, “Open source software (OSS) is software that is distributed with its source code, making it available for use, modification, and distribution with its original rights. … Programmers who have access to source code can change a program by adding to it, changing it, or fixing parts of it that aren’t working properly. OSS typically includes a license that allows programmers to modify the software to best fit their needs and control how the software can be distributed.”

      What are the popular use cases?

      1. Programming languages and frameworks
      2. Databases and data technologies
      3. Operating systems
      4. Git public repos
      5. Frameworks and tools for AI/ML/DL
      6. CI/CD tooling
      7. Cloud-related tools
      8. Security tools
      9. Container technology
      10. Networking

      Source: OpenLogic, 2022

      Common Attributes of All Open-Source Software

      • Publicly shared repository that anyone can access to use the solution and contribute changes to the design and functionality of the project.
      • A community that is an open forum to share ideas and solution enhancements, discuss project direction and vision, and seek support from peers.
      • Project governance that sets out guidelines, rules, and requirements to participate and contribute to the project.
      • Distribution license that defines the terms of how a solution can be used, assessed, modified, and distributed.

      Take the first steps to embrace open-source software

      Begin to understand what is required to embrace open-source software in your organization.

      A diagram of open-source community.

      State the Value of Open Source: Discuss current business and IT priorities, use cases, and value opportunities to determine what to expect from open-source versus commercial software.

      Select Your Open-Source Software: Clarify the driving factors in your evaluation of open-source and commercial software using your existing IT procurement practices as a starting point.

      Prepare for Open Source: Clarify the roles, processes, and tools needed for the implementation, use, and maintenance of open-source software.

      Step 1.1: State the Value of Open Source

      Diagram of step 1.1

      Activities

      1.1.1 Outline the value you expect to gain from open-source software

      This step involves the following participants:

      • Applications team
      • Product owner

      Outcomes of this step:

      • Value proposition for open source
      • Potential open-source use cases

      Use a canvas to frame your open-source evaluation

      A photo of open-source canvas

      This canvas is intended to provide a single pane of glass to start collecting your thoughts and framing your future conversations on open-source software selection and adoption.

      Record the results in the “Open-Source Canvas” tab in the Open-Source Readiness Assessment.

      Open source presents unique software and tooling opportunities

      Innovation

      Many leading-edge and bleeding-edge technologies are collaborated and innovated in open-source projects, especially in areas that are beyond the vision and scope of vendor products and priorities.

      Niche Solutions

      Open-source projects are focused. They are designed and built to solve specific business and technology problems.

      Flexible & Customizable

      All aspects of the open-source software are customizable, including source code and integrations. They can be used to extend, complement, or replace internally developed code. Licenses define how open-source code should be and must be used, productized, and modified.

      Brand & Recognition

      Open-source communities encourage contribution and collaboration among their members to add functionality and improve quality and adoption.

      Cost

      Open-source software is accessible to everyone, free of charge. Communities do not need be consulted prior to acquisition, but the software’s use, configurations, and modifications may be restricted by its license.

      However, myths continue to challenge adoption

      • Open source is less secure or poorer quality than proprietary solutions.
      • Open source is free from risk of intellectual property (IP) infringement.
      • Open source is cheaper than proprietary solutions.

      What are the top perceived barriers to using enterprise open source?

      • Concerns about the level of support
      • Compatibility concerns
      • Concerns about inherent security of the code
      • Lack of internal skills to manage and support it

      Source: Red Hat, 2022

      Build an ERP Strategy and Roadmap

      • Buy Link or Shortcode: {j2store}585|cart{/j2store}
      • member rating overall impact: 9.4/10 Overall Impact
      • member rating average dollars saved: $76,462 Average $ Saved
      • member rating average days saved: 22 Average Days Saved
      • Parent Category Name: Enterprise Resource Planning
      • Parent Category Link: /enterprise-resource-planning
      • Organizations often do not know where to start with an ERP project.
      • They focus on tactically selecting and implementing the technology.
      • ERP projects are routinely reported as going over budget, over schedule, and they fail to realize any benefits.

      Our Advice

      Critical Insight

      • An ERP strategy is an ongoing communication tool for the business.
      • Accountability for ERP success is shared between IT and the business.
      • An actionable roadmap provides a clear path to benefits realization.

      Impact and Result

      • Align the ERP strategy and roadmap with business priorities, securing buy-in from the business for the program.
      • Identification of gaps, needs, and opportunities in relation to business processes; ensuring the most critical areas are addressed.
      • Assess alternatives for the critical path(s) most relevant to your organization’s direction.

      Build an ERP Strategy and Roadmap Research & Tools

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

      1. Build an ERP Strategy and Roadmap – A comprehensive guide to align business and IT on what the organization needs from their ERP.

      A business-led, top-management-supported initiative partnered with IT has the greatest chance of success.

    • Aligning and prioritizing key business and technology drivers.
    • Clearly defining what is in and out of scope for the project.
    • Getting a clear picture of how the business process and underlying applications support the business strategic priorities.
    • Pulling it all together into an actionable roadmap.
      • Build an ERP Strategy and Roadmap – Phases 1-4
      • ERP Strategy Report Template
      [infographic]

      Workshop: Build an ERP Strategy and 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 Introduction to ERP

      The Purpose

      To build understanding and alignment between business and IT on what an ERP is and the goals for the project

      Key Benefits Achieved

      Clear understanding of how the ERP supports the organizational goals

      What business processes the ERP will be supporting

      An initial understanding of the effort involved

      Activities

      1.1 Introduction to ERP

      1.2 Background

      1.3 Expectations and goals

      1.4 Align business strategy

      1.5 ERP vision and guiding principles

      1.6 ERP strategy model

      1.7 ERP operating model

      Outputs

      ERP strategy model

      ERP Operating model

      2 Build the ERP operation model

      The Purpose

      Generate an understanding of the business processes, challenges, and application portfolio currently supporting the organization.

      Key Benefits Achieved

      An understanding of the application portfolio supporting the business

      Detailed understanding of the business operating processes and pain points

      Activities

      2.1 Build application portfolio

      2.2 Map the level 1 ERP processes including identifying stakeholders, pain points, and key success indicators

      2.3 Discuss process and technology maturity for each level 1 process

      Outputs

      Application portfolio

      Mega-processes with level 1 process lists

      3 Project set up

      The Purpose

      A project of this size has multiple stakeholders and may have competing priorities. This section maps those stakeholders and identifies their possible conflicting priorities.

      Key Benefits Achieved

      A prioritized list of ERP mega-processes based on process rigor and strategic importance

      An understanding of stakeholders and competing priorities

      Initial compilation of the risks the organization will face with the project to begin early mitigation

      Activities

      3.1 ERP process prioritization

      3.2 Stakeholder mapping

      3.3 Competing priorities review

      3.4 Initial risk register compilation

      Outputs

      Prioritized ERP operating model

      Stakeholder map.

      Competing priorities list.

      Initial risk register.

      4 Roadmap and presentation review

      The Purpose

      Select a future state and build the initial roadmap to set expectations and accountabilities.

      Key Benefits Achieved

      Identification of the future state

      Initial roadmap with expectations on accountability and timelines

      Activities

      4.1 Discuss future state options

      4.2 Build initial roadmap

      4.3 Review of final deliverable

      Outputs

      Future state options

      Initiative roadmap

      Draft final deliverable

      Further reading

      Build an ERP Strategy and Roadmap

      Align business and IT to successfully deliver on your ERP initiative

      Table of Contents

      Analyst Perspective

      Phase 3: Plan Your Project

      Executive Summary

      Step 3.1: Stakeholders, risk, and value

      Phase 1: Build Alignment and Scope

      Step 3.2: Project set up

      Step 1.1: Aligning Business and IT

      Phase 4: Next Steps

      Step 1.2: Scope and Priorities

      Step 4.1: Build your roadmap

      Phase 2: Define Your ERP

      Step 4.2: Wrap up and present

      Step 2.1: ERP business model

      Summary of Accomplishment

      Step 2.2: ERP processes and supporting applications

      Research Contributors

      Step 2.3: Process pains, opportunities, and maturity

      Related Info-Tech Research

      Bibliography

      Build an ERP Strategy and Roadmap

      Align business and IT to successfully deliver on your ERP initiative

      EXECUTIVE BRIEF

      Analyst Perspective

      A foundational ERP strategy is critical to decision making.

      Photo of Robert Fayle, Research Director, Enterprise Applications, Info-Tech Research Group.

      Enterprise resource planning (ERP) is a core tool that the business leverages to accomplish its goals. An ERP that is doing its job well is invisible to the business. The challenges come when the tool is no longer invisible. It has become a source of friction in the functioning of the business

      ERP systems are expensive, their benefits are difficult to quantify, and they often suffer from poor user satisfaction. Post-implementation, technology evolves, organizational goals change, and the health of the system is not monitored. This is complicated in today’s digital landscape with multiple integration points, siloed data, and competing priorities.

      Too often organizations jump into selecting replacement systems without understanding the needs of the organization. Alignment between business and IT is just one part of the overall strategy. Identifying key pain points and opportunities, assessed in the light of organizational strategy, will provide a strong foundation to the transformation of the ERP system.

      Robert Fayle
      Research Director, Enterprise Applications
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      Organizations often do not know where to start with an ERP project. They focus on tactically selecting and implementing the technology but ignore the strategic foundation that sets the ERP system up for success. ERP projects are routinely reported as going over budget, over schedule, and they fail to realize any benefits.

      Common Obstacles

      ERP projects impact the entire organization – they are not limited to just financial and operating metrics. The disruption is felt during both implementation and in the production environment.

      Missteps early on can cost time, financial resources, and careers. Roughly 55% of ERP projects reported being over budget, and two-thirds of organizations implementing ERP realized less than half of their anticipated benefits.

      Info-Tech’s Approach

      Obtain organizational buy-in and secure top management support. Set clear expectations, guiding principles, and critical success factors.

      Build an ERP operating model/business model that identifies process boundaries, scope, and prioritizes requirements. Assess stakeholder involvement, change impact, risks, and opportunities.

      Understand the alternatives your organization can choose for the future state of ERP. Develop an actionable roadmap and meaningful KPIs that directly align with your strategic goals.

      Info-Tech Insight

      Accountability for ERP success is shared between IT and the business. There is no single owner of an ERP. A unified approach to building your strategy promotes an integrated roadmap so all stakeholders have clear direction on the future state.

      Insight summary

      Enterprise resource planning (ERP) systems facilitate the flow of information across business units. It allows for the seamless integration of systems and creates a holistic view of the enterprise to support decision making.

      In many organizations, the ERP system is considered the lifeblood of the enterprise. Problems with this key operational system will have a dramatic impact on the ability of the enterprise to survive and grow.

      A measured and strategic approach to change will help mitigate many of the risks associated with ERP projects, which will avoid the chances of these changes becoming the dreaded “career killers.”

      A business led, top management supported initiative partnered with IT has the greatest chance of success.

      • A properly scoped ERP project reduces churn and provides all parts of the business with clarity.
      • This blueprint provides the business and IT the methodology to get the right level of detail for the business processes that the ERP supports so you can avoid getting lost in the details.
      • Build a successful ERP Strategy and roadmap by:
        • Aligning and prioritizing key business and technology drivers.
        • Clearly defining what is in and out of scope for the project.
        • Providing a clear picture of how the business process and underlying applications support the business strategic priorities.
        • Pulling it all together into an actionable roadmap.

      Enterprise Resource Planning (ERP)

      What is ERP?

      Enterprise resource planning (ERP) systems facilitate the flow of information across business units. They allow for the seamless integration of systems and create a holistic view of the enterprise to support decision making.

      In many organizations, the ERP system is considered the lifeblood of the enterprise. Problems with this key operational system will have a dramatic impact on the ability of the enterprise to survive and grow.

      An ERP system:

      • Automates processes, reducing the amount of manual, routine work.
      • Integrates with core modules, eliminating the fragmentation of systems.
      • Centralizes information for reporting from multiple parts of the value chain to a single point.

      A diagram visualizing the many aspects of ERP and the categories they fall under. Highlighted as 'Supply Chain Management' are 'Supply Chain: Procure to Pay' and 'Distribution: Forecast to Delivery'. Highlighted as 'Customer Relationship Management' are 'Sales: Quote to Cash', 'CRM: Market to Order', and 'Customer Service: Issue to Resolution'.

      ERP use cases:

      • Product-Centric
        Suitable for organizations that manufacture, assemble, distribute, or manage material goods.
      • Service-Centric
        Suitable for organizations that provide and manage field services and/or professional services.

      ERP by the numbers

      50-70%
      Statistical analysis of ERP projects indicates rates of failure vary from 50 to 70%. Taking the low end of those analyst reports, one in two ERP projects is considered a failure. (Source: Saxena and Mcdonagh)

      85%
      Companies that apply the principles of behavioral economics outperform their peers by 85% in sales growth and more than 25% in gross margin. (Source: Gallup)

      40%
      Nearly 40% of companies said functionality was the key driver for the adoption of a new ERP. (Source: Gheorghiu)

      ERP dissatisfaction

      Drivers of Dissatisfaction
      Business
      • Misaligned objectives
      • Product fit
      • Changing priorities
      • Lack of metrics
      Data
      • Access to data
      • Data hygiene
      • Data literacy
      • One view of the customer
      People and teams
      • User adoption
      • Lack of IT support
      • Training (use of data and system)
      • Vendor relations
      Technology
      • Systems integration
      • Multi-channel complexity
      • Capability shortfall
      • Lack of product support

      Finance, IT, Sales, and other users of the ERP system can only optimize ERP with the full support of each other. The cooperation of the departments is crucial when trying to improve ERP technology capabilities and customer interaction.

      Info-Tech Insight

      While technology is the key enabler of building strong customer experiences, there are many other drivers of dissatisfaction. IT must stand shoulder-to-shoulder with the business to develop a technology framework for ERP.

      Info-Tech’s methodology for developing a foundational ERP strategy and roadmap

      1. Build alignment and scope 2. Define your ERP 3. Plan your project 4. Next Steps
      Phase Steps
      1. Aligning business and IT
      2. Scope and priorities
      1. ERP Business Model
      2. ERP processes and supporting applications
      3. Process pains, opportunities & maturity
      1. Stakeholders, risk & value
      2. Project set up
      1. Build your roadmap
      2. Wrap up and present
      Phase Outcomes Discuss organizational goals and how to advance those using the ERP system. Establish the scope of the project and ensure that business and IT are aligned on project priorities. Build the ERP business model then move on to the top level (mega) processes and an initial list of the sub-processes. Generate a list of applications that support the identified processes. Conclude with a complete view of the mega-processes and their sub-processes. Map out your stakeholders to evaluate their impact on the project, build an initial risk register and discuss group alignment. Conclude the phase by setting the initial core project team and their accountabilities to the project. Review the different options to solve the identified pain points then build out a roadmap of how to get to that solution. Build a communication plan as part of organizational change management, which includes the stakeholder presentation.

      Blueprint deliverables

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

      Sample of the Key Deliverable 'ERP Strategy Report'.

      ERP Strategy Report

      Complete an assessment of processes, prioritization, and pain points, and create an initiative roadmap.

      Samples of blueprint deliverables related to 'ERP Strategy Report'.

      ERP Business Model
      Align your business and technology goals and objectives in the current environment.
      Sample of the 'ERP Business Model' blueprint deliverable.
      ERP Operating Model
      Identify and prioritize your ERP top-level processes.
      Sample of the 'ERP Operating Model' blueprint deliverable.
      ERP Process Prioritization
      Assess ERP processes against the axes of rigor and strategic importance.
      Sample of the 'ERP Process Prioritization' blueprint deliverable.
      ERP Strategy Roadmap
      A data-driven roadmap of how to address the ERP pain points and opportunities.
      Sample of the 'ERP Strategy Roadmap' blueprint deliverable.

      Executive Brief Case Study

      INDUSTRY: Aerospace
      SOURCE: Panorama, 2021

      Aerospace organization assesses ERP future state from opportunities, needs, and pain points

      Challenge

      Several issues plagued the aerospace and defense organization. Many of the processes were ad hoc and did not use the system in place, often relying on Excel. The organization had a very large pain point stemming from its lack of business process standardization and oversight. The biggest gap, however, was from the under-utilization of the ERP software.

      Solution

      By assessing the usage of the system by employees and identifying key workarounds, the gaps quickly became apparent. After assessing the organization’s current state and generating recommendations from the gaps, it realized the steps needed to achieve its desired future state. The analysis of the pain points generated various needs and opportunities that allowed the organization to present and discuss its key findings with executive leadership to set milestones for the project.

      Results

      The overall assessment led the organization to the conclusion that in order to achieve its desired future state and maximize ROI from its ERP, the organization must address the internal issues prior to implementing the upgraded software.

      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?

      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 eight to twelve calls over the course of four to six months.

      Phase 1

      • Call #1: Scoping call to understand the current situation.
      • Call #2: Establish business & IT alignment and project scope.

      Phase 2

      • Call #3: Discuss the ERP Strategy business model and mega-processes.
      • Call #4: Begin the drill down on the level 1 processes.

      Phase 3

      • Call #5: Establish the stakeholder map and project risks.
      • Call #6: Discuss project setup including stakeholder commitment and accountability.

      Phase 4

      • Call #7: Discuss resolution paths and build initial roadmap.
      • Call #8: 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
      Introduction to ERP

      1.1 Introduction to ERP

      1.2 Background

      1.3 Expectations and goals

      1.4 Align business strategy

      1.5 ERP vision and guiding principles

      1.6 ERP strategy model

      1.7 ERP operating model

      Build the ERP operating model

      2.1 Build application portfolio

      2.2 Map the level 1 ERP processes including identifying stakeholders, pain points, and key success indicators

      2.3 Discuss process and technology maturity for each level 1 process

      Project set up

      3.1 ERP process prioritization

      3.2 Stakeholder mapping

      3.3 Competing priorities review

      3.4 Initial risk register compilation

      3.5 Workshop retrospective

      Roadmap and presentation review

      4.1 Discuss future state options

      4.2 Build initial roadmap

      4.3 Review of final deliverable

      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. ERP strategy model
      2. ERP operating model
      1. Application portfolio
      2. Mega-processes with level 1 process lists
      1. Prioritized ERP operating model
      2. Stakeholder map
      3. Competing priorities list
      4. Initial risk register
      1. Future state options
      2. Initiative roadmap
      3. Draft final deliverable
      1. Completed ERP strategy template
      2. ERP strategy roadmap

      Build an ERP Strategy and Roadmap

      Phase 1

      Build alignment and scope

      Phase 1

      • 1.1 Aligning business and IT
      • 1.2 Scope and priorities

      Phase 2

      • 2.1 ERP Business Model
      • 2.2 ERP processes and supporting applications
      • 2.3 Process pains, opportunities & maturity

      Phase 3

      • 3.1 Stakeholders, risk & value
      • 3.2 Project set up

      Phase 4

      • 4.1 Build your roadmap
      • 4.2 Wrap up and present

      This phase will walk you through the following activities:

      Build a common language to ensure clear understanding of the organizational needs. Define a vision and guiding principles to aid in decision making and enumerate how the ERP supports achievement of the organizational goals. Define the initial scope of the ERP project. This includes the discussion of what is not in scope.

      This phase involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP Applications support team

      Create a compelling case that addresses strategic business objectives

      When someone at the organization asks you WHY, you need to deliver a compelling case. The ERP project will receive pushback, doubt, and resistance; if you can’t answer the question WHY, you will be left back-peddling.

      When faced with a challenge, prepare for the WHY.

      • Why do we need this?
      • Why are we spending all this money?
      • Why are we bothering?
      • Why is this important?
      • Why did we do it this way?
      • Why did we choose this vendor?

      Most organizations can answer “What?”
      Some organizations can answer “How?”
      Very few organizations have an answer for “Why?”

      Each stage of the project will be difficult and present its own unique challenges and failure points. Re-evaluate if you lose sight of WHY at any stage in the project.

      Step 1.1

      Aligning business and IT

      Activities
      • 1.1.1 Build a glossary
      • 1.1.2 ERP Vision and guiding principles
      • 1.1.3 Corporate goals and ERP benefits

      This step will walk you through the following activities:

      • Building a common language to ensure a clear understanding of the organization’s needs.
      • Creating a definition of your vision and identifying the guiding principles to aid in decision making.
      • Defining how the ERP supports achievement of the organizational goals.

      This step involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP Applications support team

      Outcomes of this step

      Business and IT have a shared understanding of how the ERP supports the organizational goals.

      Are we all talking about the same thing?

      Every group has their own understanding of the ERP system, and they may use the same words to describe different things. For example, is there a difference between procurement of office supplies and procurement of parts to assemble an item for sale? And if they are different, do your terms differ (e.g., procurement versus purchasing)?

      Term(s) Definition
      HRMS, HRIS, HCM Human Resource Management System, Human Resource Information System, Human Capital Management. These represent four capabilities of HR: core HR, talent management, workforce management, and strategic HR.
      Finance Finance includes the core functionalities of GL, AR, and AP. It also covers such items as treasury, financial planning and analysis (FP&A), tax management, expenses, and asset management.
      Supply Chain The processes and networks required to produce and distribute a product or service. This encompasses both the organization and the suppliers.
      Procurement Procurement is about getting the right products from the right suppliers in a timely fashion. Related to procurement is vendor contract management.
      Distribution The process of getting the things we create to our customers.
      CRM Customer Relationship Management, the software used to maintain records of our sales and non-sales contact with our customers.
      Sales The process of identifying customers, providing quotes, and converting those quotes to sales orders to be invoiced.
      Customer Service This is the process of supporting customers with challenges and non-sales questions related to the delivery of our products/services.
      Field Service The group that provides maintenance services to our customers.

      Activity 1.1.1 Build a glossary

      1 hour
      1. As a group, discuss the organization’s functional areas, business capabilities, value streams, and business processes.
      2. Ask each of the participants if there are terms or “jargon” that they hear used that they may be unclear on or know that others may not be aware of. Record these items in the table along with a description.
        • Acronyms are particularly important to document. These are often bandied about without explanation. For example, people outside of finance may not understand that FP&A is short for Financial Planning and Analysis.

      Record this information in the ERP Strategy Report Template.

      Sample of the 'ERP Strategy Report Template: Glossary'.

      Download the ERP Strategy Report Template

      Activity 1.1.1 Working slide

      Example/working slide for your glossary. Consider this a living document and keep it up to date.

      Term(s) Definition
      HRMS, HRIS, HCM Human Resource Management System, Human Resource Information System, Human Capital Management. These represent four capabilities of HR: core HR, talent management, workforce management, and strategic HR.
      Finance Finance includes the core functionalities of GL, AR, and AP. It also covers such items as treasury, financial planning and analysis (FP&A), tax management, expenses, and asset management.
      Supply Chain The processes and networks required to produce and distribute a product or service. This encompasses both the organization and the suppliers.
      Procurement Procurement is about getting the right products from the right suppliers in a timely fashion. Related to procurement is vendor contract management.
      Distribution The process of getting the things we create to our customers.
      CRM Customer Relationship Management, the software used to maintain records of our sales and non-sales contact with our customers.
      Sales The process of identifying customers, providing quotes, and converting those quotes to sales orders to be invoiced.
      Customer Service This is the process of supporting customers with challenges and non-sales questions related to the delivery of our products/services.
      Field Service The group that provides maintenance services to our customers.

      Vision and Guiding Principles

      GUIDING PRINCIPLES

      Guiding principles are high-level rules of engagement that help to align stakeholders from the outset. Determine guiding principles to shape the scope and ensure stakeholders have the same vision.

      Creating Guiding Principles

      Guiding principles should be constructed as full sentences. These statements should be able to guide decisions.

      EXAMPLES

      • [Organization] is implementing an ERP system to streamline processes and reduce redundancies, saving time and money.
      • [Organization] is implementing an ERP to integrate disparate systems and rationalize the application portfolio.
      • [Organization] is aiming at taking advantage of best industry practices and strives to minimize the level of customization required in solution.

      Questions to Ask

      1. What is a strong statement that will help guide decision making throughout the life of the ERP project?
      2. What are your overarching requirements for business processes?
      3. What do you ultimately want to achieve?
      4. What is a statement that will ensure all stakeholders are on the same page for the project?

      Activity 1.1.2 – ERP Vision and Project Guiding Principles

      1 hour

      1. As a group, discuss whether you want to create a separate ERP vision statement or re-state your corporate vision and/or goals.
        • An ERP vision statement will provide project-guiding principles, encompass the ERP objectives, and give a rationale for the project.
        • Using the corporate vision/goals will remind the business and IT that the project is to find an ERP solution that supports and enhances the organizational objectives.
      2. Review each of the sample guiding principles provided and ask the following questions:
        1. Do we agree with the statement?
        2. Is this statement framed in the language we used internally? Does everyone agree on the meaning of the statement?
        3. Will this statement help guide our decision-making process?

      Record this information in the ERP Strategy Report Template.

      Sample of the 'ERP Strategy Report Template: Guiding Principles.

      Download the ERP Strategy Report Template

      Activity 1.1.2 – ERP Vision and Project Guiding Principles

      We, [Organization], will select and implement an integrated software suite that enhances the growth and profitability of the organization through streamlined global business processes, real time data-driven decisions, increased employee productivity, and IT investment protection.

      • Support Business Agility: A flexible and adaptable integrated business system providing a seamless user experience.
      • Utilize ERP best practices: Do not recreate or replicate what we have today, focus on modernization. Exercise customization governance by focusing on those customizations that are strategically differentiating.
      • Automate: Take manual work out where we can, empowering staff and improving productivity through automation and process efficiencies.
      • Stay focused: Focus on scope around core business capabilities. Maintain scope control. Prioritize demand in line with the strategy.
      • Strive for “One Source of Truth”: Unify data model and integrate processes where possible. Assess integration needs carefully.

      Align the ERP strategy with the corporate strategy

      Corporate Strategy Unified Strategy ERP Strategy
      • Conveys the current state of the organization and the path it wants to take.
      • Identifies future goals and business aspirations.
      • Communicates the initiatives that are critical for getting the organization from its current state to the future state.
      • ERP optimization can be and should be linked, with metrics, to the corporate strategy and ultimate business objectives.
      • Communicates the organization’s budget and spending on ERP.
      • Identifies IT initiatives that will support the business and key ERP objectives.
      • Outlines staffing and resourcing for ERP initiatives.

      Info-Tech Insight

      ERP projects are more successful when the management team understands the strategic importance and the criticality of alignment. Time needs to be spent upfront aligning business strategies with ERP capabilities. Effective alignment between IT and the business should happen daily. Alignment doesn’t just to occur at the executive level alone, but at each level of the organization.

      1.1.3 – Corporate goals and ERP benefits

      1-2 hours

      1. Discuss the business objectives. Identify two or three objectives that are a priority for this year.
      2. Produce several ways a new ERP system will meet each objective.
      3. Think about the modules and ERP functions that will help you realize these benefits.

      Cost Reduction

      • Decrease Total Cost: Reduce total costs by five percent by January 2022.
      • Decrease Specific Costs: Reduce costs of “x” business unit by ten percent by Jan. next year.

      ERP Benefits

      • Reduce headcount
      • Reallocate workers
      • Reduce overtime
      • Increased compliance
      • Streamlined audit process
      • Less rework due to decrease in errors

      Download the ERP Strategy Report Template

      Activity 1.1.3 – Corporate goals and ERP benefits

      Corporate Strategy ERP Benefits
      End customer visibility (consumer experience)
      • Help OEM’s target customers
      • Keep customer information up-to-date, including contact choices
      • [Product A] process support improvements
      • Ability to survey and track responses
      • Track and improve renewals
      • Service support – improve cycle times for claims, payment processing, and submission quality
      Social responsibility
      • Reduce paper internally and externally
      • Facilitating tracking and reporting of EFT
      • One location for all documents
      New business development
      • Track all contacts
      • Measure where in process the contact is
      • Measure impact of promotions
      Employee experience
      • Improve integration of systems reducing manual processes through automation
      • Better tracking of sales for employee comp
      • Ability to survey employees

      Step 1.2

      Scope and priorities

      Activities
      • 1.2.1 Project scope
      • 1.2.2 Competing priorities

      This step will walk you through the following activities:

      • Define the initial scope of the ERP project. This includes the discussion of what is not in scope. For example, a stand-alone warehouse management system may be out of scope while an existing HRMS could be in scope.

      This step involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP Applications support team

      Outcomes of this step

      A project scope statement and a prioritized list of projects that may compete for organizational resources.

      Understand the importance of setting expectations with a scope statement

      Be sure to understand what is in scope for an ERP strategy project. Prevent too wide of a scope to avoid scope creep – for example, we aren’t tackling MMS or BI under ERP.

      A diamond shape with three layers. Inside is 'In Scope', middle is 'Scope Creep', and outside is 'Out of Scope'.

      Establishing the parameters of the project in a scope statement helps define expectations and provides a baseline for resource allocation and planning. Future decisions about the strategic direction of ERP will be based on the scope statement.

      Well-executed requirements gathering will help you avoid expanding project parameters, drawing on your resources, and contributing to cost overruns and project delays. Avoid scope creep by gathering high-level requirements that lead to the selection of category-level application solutions (e.g. HRIS, CRM, PLM etc.) rather than granular requirements that would lead to vendor application selection (e.g. SAP, Microsoft, Oracle, etc.).

      Out-of-scope items should also be defined to alleviate ambiguity, reduce assumptions, and further clarify expectations for stakeholders. Out-of-scope items can be placed in a backlog for later consideration.

      In Scope Out of Scope
      Strategy High-level ERP requirements, strategic direction
      Software selection Vendor application selection, Granular system requirements

      Activity 1.2.1 – Define scope

      1 hour

      1. Formulate a scope statement. Decide which people, processes, and functions the ERP strategy will address. Generally, the aim of this project is to develop strategic requirements for the ERP application portfolio – not to select individual vendors.
      2. To assist in forming your scope statement, answer the following questions:
        • What are the major coverage points?
        • Who will be using the systems?
        • How will different users interact with the systems?
        • What are the objectives that need to be addressed?
        • Where do we start?
        • Where do we draw the line?

      Record this information in the ERP Strategy Report Template.

      Sample of the 'ERP Strategy Report Template: Scope Statements'.

      Download the ERP Strategy Report Template

      Activity 1.2.1 – Define scope

      Scope statements

      The following systems are considered in scope for this project:

      • Finance
      • HRMS
      • CRM
      • Supply chain

      The following systems are out of scope for this project:

      • PLM – product lifecycle management
      • Project management
      • Contract management

      The following systems are in scope, in that they must integrate into the new system. They will not change.

      • Payroll processing
      • Bank accounts
      • EDI software

      Know your competing priorities

      Organizations typically have multiple projects on the table or in flight. Each of those projects requires resources and attention from business and/or the IT organization.

      Don’t let poor prioritization hurt your ERP implementation.
      BNP Paribas Fortis had multiple projects that were poorly prioritized resulting in the time to bring products to market to double over a three-year period. (Source: Neito-Rodriguez, 2016)

      Project Timeline Priority notes Implications
      Warehouse management system upgrade project Early 2022 implementation High Taking IT staff and warehouse team, testing by finance
      Microsoft 365 October 2021-March 2022 High IT Staff, org impacted by change management
      Electronic Records Management April 2022 – Feb 2023 High Legislative requirement, org impact due to record keeping
      Web site upgrade Early fiscal 2023

      Activity 1.2.2 – Competing priorities

      1 hour

      1. As a group, discuss the projects that are currently in flight as well as any known projects including such things as territory expansion or new regulation compliance.
      2. For each project discuss and record the following items:
        • The project timeline. When does it start and how long is it expected to run?
        • How important is this project to the organization? A lot of high priority projects are going to require more attention from the staff involved.
        • What are the implications of this project?
          • What staff will be impacted? What business users will be impacted, and what is the IT involvement?
          • To what extent will the overall organization be impacted? Is it localized to a location or is it organization wide?
          • Can the project be deferred?

      Record this information in the ERP Strategy Report Template.

      Sample of the 'ERP Strategy Report Template: Priorities'.

      Download the ERP Strategy Report Template

      Activity 1.2.2 – Competing priorities

      List all your known projects both current and proposed. Discuss the prioritization of those projects, whether they are more or less important than your ERP project.

      Project Timeline Priority notes Implications
      Warehouse management system upgrade project Early 2022 implementation High Taking IT staff and warehouse team, testing by finance
      Microsoft 365 October 2021-March 2022 High IT Staff, org impacted by change management
      Electronic Records Management April 2022 – Feb 2023 High Legislative requirement, org impact due to record keeping
      Web site upgrade Early fiscal 2023 Medium
      Point of Sale replacement Oct 2021– Mar 2022 Medium
      ERP utilization and training on unused systems Friday, Sept 17 Medium Could impact multiple staff
      Managed Security Service RFP This calendar year Medium
      Mental Health Dashboard In research phase Low

      Build an ERP Strategy and Roadmap

      Phase 2

      Define your ERP

      Phase 1

      • 1.1 Aligning business and IT
      • 1.2 Scope and priorities

      Phase 2

      • 2.1 ERP Business Model
      • 2.2 ERP processes and supporting applications
      • 2.3 Process pains, opportunities & maturity

      Phase 3

      • 3.1 Stakeholders, risk & value
      • 3.2 Project set up

      Phase 4

      • 4.1 Build your roadmap
      • 4.2 Wrap up and present

      This phase will walk you through the following activities:

      • Build the ERP business model then move on to the top level (mega) processes and an initial list of the sub-processes
      • Generate a list of applications that support the identified processes
      • Assign stakeholders, discuss pain points, opportunities, and key success indicators
      • Assign process and technology maturity to each stakeholder

      This phase involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP applications support team

      Step 2.1

      ERP business model

      Activities
      • 2.1.1 Environmental factors, technology drivers, and business needs
      • 2.1.2 Challenges, pain points, enablers, and organizational goals

      This step will walk you through the following activities:

      • Identify ERP drivers and objectives
      • Explore ERP challenges and pain points
      • Discuss the ERP benefits and opportunities

      This step involves the following participants:

      • ERP implementation team
      • Business stakeholders

      Outcomes of this step

      • ERP business model

      Explore environmental factors and technology drivers

      1. Identify business drivers that are contributing to the organization’s need for ERP.
      2. Understand how the company is running today and what the organization’s future will look like. Try to identify the purpose for becoming an integrated organization.
      3. Consider external considerations, organizational drivers, technology drivers, and key functional requirements
      The ERP Business Model with 'Business Needs', 'Environmental Factors', and 'Technology Drivers' highlighted. At the center is 'ERP Strategy' with 'Barriers' above and 'Enablers' below. Surrounding and feeding into the center group are 'Business Needs', 'Environmental Factors', 'Technology Drivers', and 'Organizational Goals'.
      External Considerations
      • Regulations
      • Elections
      • Availability of resources
      • Staff licensing and certifications
      Organizational Drivers
      • Compliance
      • Scalability
      • Operational efficiency
      • Union agreements
      • Self service
      • Role appropriate dashboards and reports
      • Real time data access
        • Use of data in the system (no exports)
      Technology Considerations
      • Data accuracy
      • Data quality
      • Better reporting
      Functional Requirements
      • Information availability
      • Integration between systems
      • Secure data

      Activity 2.1.1 – Explore environmental factors and technology drivers

      1 hour

      1. Identify business drivers that are contributing to the organization’s need for ERP.
      2. Understand how the company is running today and what the organization’s future will look like. Try to identify the purpose for becoming an integrated organization. Use a whiteboard or flip charts and markers to capture key findings.
      3. Consider External Considerations, Organizational Drivers, Technology Drivers, and Key Functional Requirements.

      Record this information in the ERP Strategy Report Template.

      Sample of the next slide, 'ERP Business Model', with an iconized ERP Business Model and a table highlighting 'Environmental Factors', 'Technology Drivers', and 'Business Needs'.

      Download the ERP Strategy Report Template

      ERP Business Model A iconized version of the ERP Business Model.

      Environmental FactorsTechnology DriversBusiness Needs
      • Regulations
      • Elections
      • Availability of resources
      • Staff licensing and certifications
      • Document storage
      • Cloud security standards
      • Functionality based on deployment
      • Cloud-first based on above
      • Integration with external data suppliers
      • Integration with internal systems (Elite?)
      • Compliance
      • Scalability
      • Operational efficiency
      • Union agreements
      • Self service
      • Role appropriate dashboards and reports
      • Real time data access
      • Use of data in the system (no exports)
      • CapEx vs. OpEx

      Discuss challenges, pain points, enablers and organizational goals

      1. Identify challenges with current systems and processes.
      2. Brainstorm potential barriers to successful ERP selection and implementation. Use a whiteboard and marker to capture key findings.
      3. Consider organizational goals along with barriers and enablers to ERP success.
      The ERP Business Model with 'Organizational Goals', 'Enablers', and 'Barriers' highlighted. At the center is 'ERP Strategy' with 'Barriers' above and 'Enablers' below. Surrounding and feeding into the center group are 'Business Needs', 'Environmental Factors', 'Technology Drivers', and 'Organizational Goals'.
      Functional Gaps
      • No online purchase order requisition
      Technical Gaps
      • Inconsistent reporting – data quality concerns
      Process Gaps
      • Duplication of data
      • Lack of system integration
      Barriers to Success
      • Cultural mindset
      • Resistance to change
      Business Benefits
      • Business-IT alignment
      IT Benefits
      • Compliance
      • Scalability
      Organizational Benefits
      • Data accuracy
      • Data quality
      Enablers of Success
      • Change management
      • Alignment to strategic objectives

      Activity 2.1.2 – Discuss challenges, pain points, enablers, and organizational goals

      1 hour

      1. Identify challenges with the current systems and processes.
      2. Brainstorm potential barriers to successful ERP selection and implementation. Use a whiteboard or flip chart and markers to capture key findings.
      3. Consider functional gaps, technical gaps, process gaps, and barriers to ERP success.
      4. Identify the opportunities and benefits from an integrated system.
      5. Brainstorm potential enablers for successful ERP selection and implementation. Use a whiteboard and markers to capture key findings.
      6. Consider business benefits, IT benefits, organizational benefits, and enablers of success.

      Record this information in the ERP Strategy Report Template.

      Sample of the next slide, 'ERP Business Model', with an iconized ERP Business Model and a table highlighting 'Organizational Goals', 'Enablers', and 'Barriers'.

      Download the ERP Strategy Report Template

      ERP Business Model A iconized version of the ERP Business Model.

      Organizational Goals Enablers Barriers
      • Efficiency
      • Effectiveness
      • Integrity
      • One source of truth for data
      • One team
      • Customer service, external and internal
      • Cross-trained employees
      • Desire to focus on value-add activities
      • Collaborative
      • Top level executive support
      • Effective change management process
      • Organizational silos
      • Lack of formal process documentation
      • Funding availability
      • What goes first? Organizational priorities

      Step 2.2

      ERP processes and supporting applications

      Activities
      • 2.2.1 ERP process inventory
      • 2.2.2 Application portfolio

      This step will walk you through the following activities:

      • Identify the top-level (mega) processes and create an initial list of the sub-processes
      • Generate a list of applications that support the identified processes

      This step involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP applications support team

      Outcomes of this step

      • A list of in scope business processes
      • A list of current applications and services supporting the business processes

      Process Inventory

      In business architecture, the primary view of an organization is known as a business capability map.

      A business capability defines what a business does to enable value creation rather than how.

      Business capabilities:

      • Represent stable business functions
      • Are unique and independent of each other
      • Will typically have a defined business outcome

      A business capability map provides details that help the business architecture practitioner direct attention to a specific area of the business for further assessment.

      A process map titled 'Business capability map (Level 0)' with many processes sectioned off into sections and subsections. The top-left section is 'Products and Services Development' with subsections 'Design'(6 processes) and 'Manufacturing'(3 processes). The top-middle section is 'Revenue Generation'(3 processes) and below that is 'Sourcing'(2 processes). The top-right section is 'Demand Fulfillment'(9 processes). Along the bottom is the section 'Enterprise Management and Planning' with subsections 'Human Resources'(4 processes), 'Business Direction'(4 processes), and 'Finance'(4 processes).

      If you do not have a documented process model, you can use the APQC Framework to help define your inventory of business processes.

      APQC’s Process Classification Framework is a taxonomy of cross-functional business processes intended to allow the objective comparison of organizational performance within and among organizations.

      APQC’s Process Classification Framework

      Activity 2.2.1 – Process inventory

      2-4 hours

      1. As a group, discuss the business capabilities, value streams, and business processes.
      2. For each capability determine the following:
        • Is this capability applicable to our organization?
        • What application, if any, supports this capability?
      3. Are there any missing capabilities to add?

      Record this information in the ERP Strategy Report Template.

      Sample of the 'Process Inventory' table on the next slide.

      Download the ERP Strategy Report Template

      Activity 2.2.1 – Process inventory

      Core Finance Core HR Workforce Management Talent Management Warehouse Management Enterprise Asset Management
      Process Technology Process Technology Process Technology Process Technology Process Technology Process Technology
      • General ledger
      • Accounts payable
      • Accounts receivable
      • GL consolidation
      • Cash management
      • Billing and invoicing
      • Expenses
      • Payroll accounting
      • Tax management
      • Reporting
      • Payroll administration
      • Benefits administration
      • Position management
      • Organizational structure
      • Core HR records
      • Time and attendance
      • Leave management
      • Scheduling
      • Performance management
      • Talent acquisition
      • Offboarding & onboarding
      • Plan layout
      • Manage inventory
      • Manage loading docks
      • Pick, pack, ship
      • Plan and manage workforce
      • Manage returns
      • Transfer product cross-dock
      • Asset lifecycle management
      • Supply chain management
      • Maintenance planning & scheduling
      Planning & Budgeting Strategic HR Procurement Customer Relationship Management Facilities Management Project Management
      Process Technology Process Technology Process Technology Process Technology Process Technology Process Technology
      • Budget reporting
      • Variance analysis
      • Multi-year operating plan
      • Monthly forecasting
      • Annual operating plan
      • Compensation planning
      • Workforce planning
      • Succession planning
      • Supplier management
      • Purchase order management
      • Workflow approvals
      • Contract / tender management
      • Contact management
      • Activity management
      • Analytics
      • Plan and acquire
      • Asset maintenance
      • Disposal
      • Project management
      • Project costing
      • Budget control
      • Document management

      Complete an inventory collection of your application portfolio

      MANAGED vs. UNMANAGED APPLICATION ENVIRONMENTS

      • Managed environments make way for easier inventory collection since there is significant control as to what applications can be installed on a company asset. Organizations will most likely have a comprehensive list of supported and approved applications.
      • Unmanaged environments are challenging to control because users are free to install any applications on company assets, which may or may not be supported by IT.
      • Most organizations fall somewhere in between – there is usually a central repository of applications and several applications that are exceptions to the company policies. Ensure that all applications are accounted for.

      Determine your inventory collection method:

      MANUAL INVENTORY COLLECTION
      • In its simplest form, a spreadsheet is used to document your application inventory.
      • For large organizations, reps interview all business domains to create a list of installed applications.
      • Conducting an end-user survey within your business domains is one way to gather your application inventory and assess quality.
      • This manual approach is most appropriate for smaller organizations with small application portfolios across domains.
      AUTOMATED INVENTORY COLLECTION
      • Using inventory collection compatibility tools, discover all of the supported applications within your organization.
      • This approach may not capture all applications, depending on the parameters of your automated tool.
      • This approach works well in a managed environment.

      Activity 2.2.2 – Understand the current application portfolio

      1-2 hours

      1. Brainstorm a list of the applications that support the ERP business processes inventoried in Activity 2.2.1. If an application has multiple instances, list each instance as a separate line item.
      2. Indicate the following for each application:
        1. User satisfaction. This may be more than one entry as different groups – e.g., IT vs. business – may differ.
        2. Processes supported. Refer to processes defined in Activity 2.2.1. Update 2.2.1 if additional processes are identified during this exercise.
        3. Define a future disposition: Keep, Update, Replace. It is possible to have more than one disposition, e.g., Update or Replace is a valid disposition.
      3. [Optional] Collect the following information about each application. This information can be used to calculate the cost per application and total cost per user:
        1. Number of users or user groups
        2. Estimated maintenance costs
        3. Estimated capital costs
        4. Estimated licensing costs
        5. Estimated support costs

      Record this information in the ERP Strategy Report Template.

      Sample of the 'Application Portfolio' table on the next slide.

      Download the ERP Strategy Report Template

      2.2.2 - Application portfolio

      Inventory your applications and assess usage, satisfaction, and disposition

      Application Name Satisfaction Processes Supported Future Disposition
      PeopleSoft Financials Medium and declining ERP – shares one support person with HR Update or Replace
      Time Entry (custom) Low Time and Attendance Replace
      PeopleSoft HR Medium Core HR Update or Replace
      ServiceNow High ITSM
      CSM: Med-Low
      ITSM and CSM
      CSM – complexity and process changes
      Update
      Data Warehouse High IT
      Business: Med-Low
      BI portal – Tibco SaaS datamart Keep
      Regulatory Compliance Medium Regulatory software – users need training Keep
      ACL Analytics Low Audit Replace
      Elite Medium Supply chain for wholesale Update (in progress)
      Visual Importer Med-High Customs and taxes Keep
      Custom Reporting application Med-High Reporting solution for wholesale (custom for old system, patched for Elite) Replace

      2.3.1 – Visual application portfolio [optional]

      A diagram of applications and how they connect to each other. There are 'External Systems' and 'Internal Systems' split into three divisions, 'Retail Division', 'Wholesale Division', and 'Corporate Services'. Example external systems are 'Moneris', 'Freight Carriers', and 'Banks'. Example internal systems are 'Retail ERP/POS', 'Elite', and 'Excel'.

      Step 2.3

      Process pains, opportunities, and maturity

      Activities
      • 2.3.1 Level one process inventory with stakeholders
      • 2.3.2 Process pain points and opportunities
      • 2.3.3 Process key success indicators
      • 2.3.4 Process and technology maturity
      • 2.3.5 Mega-process prioritization

      This step will walk you through the following activities:

      • Assign stakeholders, discuss pain points, opportunities, and key success indicators for the mega-processes identified in Step 2.1
      • Assign process and technology maturity to each prioritizing the mega-processes

      This step involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP applications support team

      Outcomes of this step

      For each mega-process:

      • Level 1 processes with process and technology maturity assigned
      • Stakeholders identified
      • Process pain points, opportunities, and key success indicators identified
      • Prioritize the mega-processes

      Building out the mega-processes

      Congratulations, you have made it to the “big lift” portion of the blueprint. For each of the processes that were identified in exercise 2.2.1, you will fill out the following six details:

      1. Primary stakeholder(s)
      2. A description of the process
      3. hat level 1 processes/capabilities the mega-process is composed of
      4. Problems the new system must solve
      5. What success will look like when the new system is implemented
      6. The process and technological maturity of each level 1 process.

      Sample of the 'Core Finance' slide in the ERP Strategy Report, as shown on the next slide, with numbers corresponding to the ordered list above. 1 is on a list of 'Stakeholders', 2 is by the 'Description' box, 3 is on the 'Capability' table column, 4 is on the 'Current Pain Points' box, 5 is on the 'Key Success Factors' box, and 6 is on the 'Maturity' ratings column.

      It will take one to three hours per mega-process to complete the six different sections.

      Note:
      For each mega-process identified you will create a separate slide in the ERP Strategy Report. Default slides have been provided. Add or delete as necessary.

      Sample of the 'Core Finance' slide in the ERP Strategy Report. Note on the list of stakeholders reads 'Primary Stakeholders'. Note on the title, Core Finance, reads 'Mega-process name'. Note on the description box reads 'Description of the process'. Note on the 'Key Success Factors' box reads 'What success looks like'. Note on the 'Current Pain Points' box reads 'Problems the new system must solve'. Below is a capability table with columns 'Capability', 'Maturity', and a blank on for notes. Note on the 'Capability' table column reads 'Level 1 process'. Note on the 'Maturity' ratings column reads 'Level 1 process maturity of process and technology'. Note on the notes column reads 'Level 1 process notes'.

      An ERP project is most effective when you follow a structured approach to define, select, implement, and optimize

      Top-down approach

      ERP Strategy
      • Operating Model – Define process strategy, objectives, and operational implications.
      • Level 1 Processes –Define process boundaries, scope at the organization level; the highest level of mega-process.

      • Level 2 Processes – Define processes by function/group which represent the next level of process interaction in the organization.
      • Level 3 Processes – Decompose process by activity and role and identify suppliers, inputs, outputs, customers, metrics, and controls.
      • Functional Specifications; Blueprint and Technical Framework – Refine how the system will support and enable processes; includes functional and technical elements.
      • Org Structure and Change Management – Align org structure and develop change mgmt. strategy to support your target operating model.
      • Implementation and Transition to Operations – Execute new methods, systems, processes, procedures, and organizational structure.
      • ERP Optimization and Continuous Improvement – Establish a program to monitor, govern, and improve ERP systems and processes.

      *A “stage gate” approach should be used: the next level begins after consensus is achieved for the previous level.

      Activity 2.3.1 – Level 1 process inventory with stakeholders

      1 hour per mega-process

      1. Identify the primary stakeholder for the mega-process. The primary stakeholder is usually the process owner. For example, for core finance the CFO is the process owner/primary stakeholder. Name a maximum of three stakeholders.
      2. In the lower section, detail all the capabilities/processes associated with the mega-process. Be careful to remain at the level 1 process level as it is easy to start identifying the “How” of a process. The “How” is too deep.

      Record this information in the ERP Strategy Report Template.

      Sample of the 'Core Finance' slide in the ERP Strategy Report with the 'Stakeholders' list and 'Capability' table column highlighted.

      Download the ERP Strategy Report Template

      Activity 2.3.2 – Process pain points and opportunities

      30+ minutes per mega-process

      1. As a group, write a clear description of the mega-process. This helps establish alignment on the scope of the mega-process.
      2. Start with the discussion of current pain points with the various capabilities. These pain points will be items that the new solution will have to resolve.

      Record this information in the ERP Strategy Report Template.

      Sample of the 'Core Finance' slide in the ERP Strategy Report with the 'Description', 'Key Success Factors', and 'Current Pain Points' boxes highlighted.

      Download the ERP Strategy Report Template

      Activity 2.3.3 – Key success indicators

      30 minutes per mega-process

      1. Document key success factors that should be base-lined in the existing system to show the overall improvement once the new system is implemented. For example, if month-end close takes 12 days in the current system, target three days for month-end close in the new system.

      Record this information in the ERP Strategy Report Template.

      Sample of the 'Core Finance' slide in the ERP Strategy Report with the 'Description', 'Key Success Factors', and 'Current Pain Points' boxes highlighted.

      Download the ERP Strategy Report Template

      Activity 2.3.4 – Process and technology maturity

      1 hour

      1. For each capability/level 1 process identified determine you level of process maturity:
        • Weak – Ad hoc processes without documentation
        • Moderate – Documented processes that are often executed consistently
        • Strong – Documented processes that include exception handling that are rigorously followed
        • Payroll is an example of a strong process, even if every step is manual. The process is executed the same every time to ensure staff are paid properly and on time.
      2. For each capability/level 1 process identified determine you level of technology maturity:
        • Weak – manual execution and often paper-based
        • Moderate – Some technology support with little automation
        • Strong – The process executed entirely within the technology stack with no manual processes

      Record this information in the ERP Strategy Report Template.

      Sample of the 'Core Finance' slide in the ERP Strategy Report with the 'Maturity' and notes columns highlighted.

      Download the ERP Strategy Report Template

      Activity 2.3.5 – Mega-process prioritization

      1 hour

      1. For the mega-processes identified, map each process’s current state in terms of process rigor versus organizational importance.
        • For process rigor, refer to your process maturity in the previous exercises.
      2. Now, as a group discuss how you want to “move the needle” on each of the processes. Remember that you have a limited capacity so focus on the processes that are, or will be, of strategic importance to the organization. The processes that are placed in the top right quadrant are the ones that are likely the strategic differentiators.

      Record this information in the ERP Strategy Report Template.

      A smaller version of the process prioritization map on the next slide.

      Download the ERP Strategy Report Template.

      ERP Process Prioritization

      Establishing an order of importance can impact vendor selection and implementation roadmap; high priority areas are critical for ERP success.

      A prioritization map placing processes by 'Rigor' and 'Organizational Importance' They are numbered 1-9, 0, A, and B and are split into two colour-coded sets for 'Future (green)' and 'Current(red)'. On the x-axis 'Organizational Importance' ranges from 'Operational' to 'Strategic' and on the y-axis 'Process Rigor' ranges from 'Get the Job Done' to 'Best Practice'. Comparing 'Current' to 'Future', they have all moved up from 'Get the Job Done' into 'Best Practice' territory and a few have migrated over from 'Operational' to 'Strategic'. Processes are 1. Core Finance, 2. Core HR, 3. Workforce Management, 4.Talent Management, 5. Employee Health and Safety, 6. Enterprise Asset Management, 7.Planning & Budgeting, 8. Strategic HR, 9. Procurement Mgmt., 0. CRM, A. Facilities, and B. Project Management.

      Build an ERP Strategy and Roadmap

      Phase 3

      Plan your project

      Phase 1

      • 1.1 Aligning business and IT
      • 1.2 Scope and priorities

      Phase 2

      • 2.1 ERP Business Model
      • 2.2 ERP processes and supporting applications
      • 2.3 Process pains, opportunities & maturity

      Phase 3

      • 3.1 Stakeholders, risk & value
      • 3.2 Project set up

      Phase 4

      • 4.1 Build your roadmap
      • 4.2 Wrap up and present

      This phase will walk you through the following activities:

      • Map out your stakeholders to evaluate their impact on the project
      • Build an initial risk register and ensure the group is aligned
      • Set the initial core project team and their accountabilities and get them started on the project

      This phase involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP Applications support team

      Step 3.1

      Stakeholders, risk, and value

      Activities
      • 3.1.1 Stakeholder analysis
      • 3.1.2 Potential pitfalls and mitigation strategies
      • 3.1.3 Project value [optional]

      This step will walk you through the following activities:

      • Map out your stakeholders to evaluate their impact on the project
      • Build an initial risk register and ensure the group is aligned

      This step involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP Applications support team

      Outcomes of this step

      • An understanding of the stakeholders and their project influence
      • An initial risk register
      • A consensus on readiness to proceed

      Understand how to navigate the complex web of stakeholders in ERP

      Identify which stakeholders to include and what their level of involvement should be during requirements elicitation based on relevant topic expertise.

      Sponsor End User IT Business
      Description An internal stakeholder who has final sign-off on the ERP project. Front-line users of the ERP technology. Back-end support staff who are tasked with project planning, execution, and eventual system maintenance. Additional stakeholders that will be impacted by any ERP technology changes.
      Examples
      • CEO
      • CIO/CTO
      • COO
      • CFO
      • Warehouse personnel
      • Sales teams
      • HR admins
      • Applications manager
      • Vendor relationship manager(s)
      • Director, Procurement
      • VP, Marketing
      • Manager, HR
      Value Executive buy-in and support is essential to the success of the project. Often, the sponsor controls funding and resource allocation. End users determine the success of the system through user adoption. If the end user does not adopt the system, the system is deemed useless and benefits realization is poor. IT is likely to be responsible for more in-depth requirements gathering. IT possesses critical knowledge around system compatibility, integration, and data. Involving business stakeholders in the requirements gathering will ensure alignment between HR and organizational objectives.

      Large-scale ERP projects require the involvement of many stakeholders from all corners and levels of the organization, including project sponsors, IT, end users, and business stakeholders. Consider the influence and interest of stakeholders in contributing to the requirements elicitation process and involve them accordingly.

      An example stakeholder map, categorizing stakeholders by amount of influence and interest.

      Activity 3.1.1 – Map your stakeholders

      1 hour

      1. As a group, identify all the ERP stakeholders. A stakeholder may be an individual such as the CEO or CFO, or it may be a group such as front-line employees.
      2. Map each stakeholder on the quadrant based on their expected Influence and Involvement in the project
      3. [Optional] Color code the users using the scale below to quickly identify the group that the stakeholder belongs to.
        • Sponsor – An internal stakeholder who has final sign-off on the ERP project.
        • End User – Front-line users of the ERP technology.
        • IT – Back-end support staff who are tasked with project planning, execution, and eventual system maintenance.
        • Business – Additional stakeholders that will be impacted by any ERP technology changes.

      Record this information in the ERP Strategy Report Template.

      Preview of the next slide.

      Download the ERP Strategy Report Template

      Slide titled 'Map the organization's stakeholders with a more in-depth example of a stakeholder map and long 'List of Stakeholders'. The quadrants that stakeholders are sorted into by influence and involvement are labelled 'Keep Satisfied (1)', 'Involve Closely (2)', 'Monitor (3)', and 'Keep Informed (4)'.

      Prepare contingency plans to minimize time spent handling unexpected risks

      Understanding the technical and strategic risks of a project can help you establish contingencies to reduce the likelihood of risk occurrence and devise mitigation strategies to help offset their impact if contingencies are insufficient.

      Risk Impact Likelihood Mitigation Effort
      Inadequate budget for additional staffing resources. 2 1 Use internal transfers and role-sharing rather than external hiring.
      Push-back on an ERP solution. 2 2 Use formal communication plans, an ERP steering committee, and change management to overcome organizational readiness.
      Overworked resources. 1 1 Create a detailed project plan that outlines resources and timelines in advance.
      Rating Scale:
      Impact: 1- High Risk 2- Moderate Risk 3- Minimal Risk
      Likelihood: 1- High/Needs Focus 2- Can Be Mitigated 3- Remote Likelihood

      Remember

      The biggest sources of risk in an ERP strategy are lack of planning, poorly defined requirements, and lack of governance.

      Apply the following mitigation tips to avoid pitfalls and delays.

      Risk Mitigation Tips

      • Upfront planning
      • Realistic timelines
      • Resource support
      • Managing change
      • Executive sponsorship
      • Sufficient funding
      • Setting the right expectations

      Activity 3.1.2 – Identify potential project pitfalls and mitigation strategies

      1-2 hours

      1. Discuss what “Impact” and “Likelihood” mean to your organization. For example, define Impact by what is important to your organization – financial loss, reputational impact, employee loss, and process impairment are all possible factors.
      2. Identify potential risks that may impede the successful completion of each work initiative. Risks may include predictable factors such as low resource capability, or unpredictable factors such as a change in priorities leading to withdrawn buy-in.
      3. For each risk, identify mitigation tactics. In some cases, mitigation tactics might take the form of standalone work initiative. For example, if a risk is lack of end-user buy-in, a work initiative to mitigate that risk might be to build an end-user communication plan.

      Record this information in the ERP Strategy Report Template.

      Preview of the next slide.

      Download the ERP Strategy Report Template

      Risks

      Risk Impact Likelihood Mitigation Effort
      Inadequate budget for additional staffing resources. 2 1 Use internal transfers and role-sharing rather than external hiring.
      Push-back on an ERP solution. 2 2 Use formal communication plans, an ERP steering committee, and change management to overcome organizational readiness.
      Overworked resources. 1 1 Create a detailed project plan that outlines resources and timelines in advance.
      Project approval 1 1 Build a strong business case for project approval and allow adequate time for the approval process
      Software does not work as advertised resulting in custom functionality with associated costs to create/ maintain 1 2 Work with staff to change processes to match the software instead of customizing the system thorough needs analysis prior to RFP creation
      Under estimation of staffing levels required, i.e. staff utilized at 25% for project when they are still 100% on their day job 1 2 Build a proper business case around staffing (be somewhat pessimistic)
      EHS system does not integrate with new HRMS/ERP system 2 2
      Selection of an ERP/HRMS that does not integrate with existing systems 2 3 Be very clear in RFP on existing systems that MUST be integrated to
      Rating Scale:
      Impact: 1- High Risk 2- Moderate Risk 3- Minimal Risk
      Likelihood: 1- High/Needs Focus 2- Can Be Mitigated 3- Remote Likelihood

      Is the organization committed to the ERP project?

      A recent study of critical success factors to an ERP implementation identified top management support and interdepartmental communication and cooperation as the top two success factors.

      By answering the seven questions the key stakeholders are indicating their commitment. While this doesn’t guarantee that the top two critical success factors have been met, it does create the conversation to guide the organization into alignment on whether to proceed.

      A table of example stakeholder questions with options 1-5 for how strongly they agree or disagree. 'Strongly disagree - 1', 'Somewhat disagree - 2', 'Neither agree or disagree - 3', 'Somewhat agree - 4', 'Strongly agree - 5'.

      Activity 3.1.3 – Project value (optional)

      30 minutes

      1. As a group, discuss the seven questions in the table. Ensure everyone agrees on what the questions are asking. If necessary, modify the language so that the meaning is clear to everyone.
      2. Have each stakeholder answer the seven questions on their own. Have someone compile the answers looking for:
        1. Any disagrees, strongly, somewhat, or neither as this indicates a lack of clarity. Endeavour to discover what additional information is required.
        2. [Optional] Have the most positive and most negative respondents present their points of view for the group to discuss. Is someone being overly optimistic, or pessimistic? Did the group miss something?

      There are no wrong answers. It should be okay to disagree with any of these statements. The goal of the exercise is to generate conversation that leads to support of the project and collaboration on the part of the participants.

      Record this information in the ERP Strategy Report Template.

      A preview of the next slide.

      Download the ERP Strategy Report Template

      Ask the right questions now to determine the value of the project to the organization

      Please indicate how much you agree or disagree with each of the following statements.

      Question # Question Strongly disagree Somewhat disagree Neither agree nor disagree Somewhat agree Strongly agree
      1. I have everything I need to succeed. 1 2 3 4 5
      2. The right people are involved in the project. 1 2 3 4 5
      3. I understand the process of ERP selection. 1 2 3 4 5
      4. My role in the project is clear to me. 1 2 3 4 5
      5. I am clear about the vision for this project. 1 2 3 4 5
      6. I am nervous about this project. 1 2 3 4 5
      7. There is leadership support for the project. 1 2 3 4 5

      Step 3.2

      Project set up

      Activities
      • 3.2.1 Create the project team
      • 3.2.2 Set the project RACI

      This step will walk you through the following activities:

      • Set the initial core project team and their accountabilities to the project.

      This step involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP Applications support team

      Outcomes of this step

      • Identify the core team members and their time commitments.
      • Assign responsibility, accountability or communication needs.

      Identify the right stakeholders for your project team

      Consider the core team functions when composing the project team. It is essential to ensure that all relevant perspectives (business, IT, etc.) are evaluated to create a well-aligned and holistic ERP strategy.

      PROJECT TEAM ROLES

      • Project champion
      • Project advisor
      • Steering committee
      • Project manager
      • Project team
      • Subject matter experts
      • Change management specialist

      PROJECT TEAM FUNCTIONS

      • Collecting all relevant inputs from the business.
      • Gathering high-level requirements.
      • Creating a roadmap.

      Info-Tech Insight

      There may be an inclination towards a large project team when trying to include all relevant stakeholders. Carefully limiting the size of the project team will enable effective decision making while still including functional business units like HR and Finance, as well as IT.

      Activity 3.2.1 – Project team

      1 hour

      1. Considering your ERP project scope, discuss the resources and capabilities necessary, and generate a complete list of key stakeholders considering each of the roles indicated on the chart to the right.
      2. Using the list previously generated, identify a candidate(s) for each role and determine their responsibility in the ERP strategy and their expected time commitment.

      Record this information in the ERP Strategy Report Template.

      Preview of the table on the next slide.

      Download the ERP Strategy Report Template

      Project team

      Of particular importance for this table is the commitment column. It is important that the organization understands the level of involvement for all roles. Failure to properly account for the necessary involvement is a major risk factor.

      Role Candidate Responsibility Commitment
      Project champion John Smith
      • Provide executive sponsorship.
      20 hours/week
      Steering committee
      • Establish goals and priorities.
      • Define scope and approve changes.
      • Provide adequate resources and resolve conflict.
      • Monitor project milestones.
      10 hours/week
      Project manager
      • Prepare and manage project plan.
      • Monitor project team progress.
      • Conduct project team meetings.
      40 hours/week
      Project team
      • Drive day-to-day project activities.
      • Coordinate department communication.
      • Make process and design decisions.
      40 hours/week
      Subject matter experts by area
      • Attend meetings as needed.
      • Respond to questions and inquiries.
      5 hours/week

      Define project roles and responsibilities to improve progress tracking

      Build a list of the core ERP strategy team members and then structure a RACI chart with the relevant categories and roles for the overall project.

      • Responsible – Conducts work to achieve the task
      • Accountable – Answerable for completeness of task
      • Consulted – Provides input for the task
      • Informed – Receives updates on the task

      Benefits of assigning RACI early:

      • Improve project quality by assigning the right people to the right tasks.
      • Improve chances of project task completion by assigning clear accountabilities.
      • Improve project buy-in by ensuring stakeholders are kept informed of project progress, risks, and successes.

      Activity 3.2.2 – Project RACI

      1 hour

      1. The ERP strategy will require a cross-functional team within IT and business units. Make sure the responsibilities are clearly communicated to the selected project sponsor.
      2. Modify the left-hand column to match the activities expected in your project.

      Record this information in the ERP Strategy Report Template.

      Preview of the RACI chart on the next slide.

      Download the ERP Strategy Report Template

      3.2.2 – Project RACI

      Project champion Project advisor Project steering committee Project manager Project team Subject matter experts
      Determine project scope & vision I C A R C C
      Document business goals I I A R I C
      Inventory ERP processes I I A C R R
      Map current state I I A R I R
      Assess gaps and opportunities I C A R I I
      Explore alternatives R R A I I R
      Build a roadmap R A R I I R
      Create a communication plan R A R I I R
      Present findings R A R I I R

      Build an ERP Strategy and Roadmap

      Phase 4

      Next steps

      Phase 1

      • 1.1 Aligning business and IT
      • 1.2 Scope and priorities

      Phase 2

      • 2.1 ERP Business Model
      • 2.2 ERP processes and supporting applications
      • 2.3 Process pains, opportunities & maturity

      Phase 3

      • 3.1 Stakeholders, risk & value
      • 3.2 Project set up

      Phase 4

      • 4.1 Build your roadmap
      • 4.2 Wrap up and present

      This phase will walk you through the following activities:

      • Review the different options to solve the identified pain points
      • Build out a roadmap showing how you will get to those solutions
      • Build a communication plan that includes the stakeholder presentation

      This phase involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP Applications support team

      Step 4.1

      Build your roadmap

      Activities
      • 4.1.1 Pick your path
      • 4.1.2 Build your roadmap
      • 4.1.3 Visualize your roadmap (optional)

      This step will walk you through the following activities:

      • Review the different options to solve the identified pain points then build out a roadmap of how to get to that solution.

      This step involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP Applications support team

      Outcomes of this step

      • A strategic direction is set
      • An initial roadmap is laid out

      Choose the right path for your organization

      There are several different paths you can take to achieve your ideal future state. Make sure to pick the one that suits your needs as defined by your current state.

      A diagram of strategies. At the top is 'Current State', at the bottom is 'Future State', and listed strategies are 'Maintain Current System', 'Augment Current System', 'Optimize', and 'Transform'.

      Explore the options for achieving your ideal future state

      CURRENT STATE STRATEGY
      Your existing application satisfies both functionality and integration requirements. The processes surrounding it likely need attention, but the system should be considered for retention. MAINTAIN CURRENT SYSTEM
      Your existing application is, for the most part, functionally rich, but may need some tweaking. Spend time and effort building and enhancing additional functionalities or consolidating and integrating interfaces. AUGMENT CURRENT SYSTEM
      Your ERP application portfolio consists of multiple apps serving the same functions. Consolidating applications with duplicate functionality is more cost efficient and makes integration and data sharing simpler. OPTIMIZE: CONSOLIDATE AND INTEGRATE SYSTEMS
      Your existing system offers poor functionality and poor integration. It would likely be more cost and time efficient to replace the application and its surrounding processes altogether. TRANSFORM: REPLACE CURRENT SYSTEM

      Option: Maintain your current system

      Resolve your existing process and people pain points

      MAINTAIN CURRENT SYSTEM

      Keep the system, change the process.

      Your existing application satisfies both functionality and integration requirements. The processes surrounding it likely need attention, but the system should be considered for retention.

      Maintaining your current system entails adjusting current processes and/or adding new ones, and involves minimal cost, time, and effort.

      INDICATORS POTENTIAL SOLUTIONS
      People Pain Points
      • Lack of training
      • Low user adoption
      • Lack of change management
      • Contact vendor to inquire about employee training opportunities
      • Build a change management strategy
      Process Pain Points
      • Legacy processes
      • Workarounds and shortcuts
      • Highly specialized processes
      • Inconsistent processes
      • Explore process reengineering and process improvement opportunities
      • Evaluate and standardize processes

      Option: Augment your current system

      Use augmentation to resolve your existing technology and data pain points

      AUGMENT CURRENT SYSTEM

      Add to the system.

      Your existing application is for the most part functionally rich but may need some tweaking. Spend time and effort enhancing your current system.

      You will be able to add functions by leveraging existing system features. Augmentation requires limited investment and less time and effort than a full system replacement.

      INDICATORS POTENTIAL SOLUTIONS
      Technology Pain Points
      • Lack of reporting functions.
      • Lacking functional depth in key process areas.
      • Add point solutions or enable modules to address missing functionality.
      Data Pain Points
      • Poor data quality
      • Lack of data for processing and reporting
      • Single-source data entry
      • Add modules or augment processes to capture data

      Option: Consolidate and integrate

      Consolidate and integrate your current systems to address your technology and data pain points

      CONSOLIDATE AND INTEGRATE SYSTEMS

      Get rid of one system, combine two, or connect many.

      Your ERP application portfolio consists of multiple apps serving the same functions.

      Consolidating your systems eliminates the need to manage multiple pieces of software that provide duplicate functionality. Reducing the number of ERP applications makes integration and data sharing simpler.

      INDICATORS POTENTIAL SOLUTIONS
      Technology Pain Points
      • Disparate and disjointed systems
      • Multiple systems supporting the same function
      • Unused software licenses
      • System consolidation
      • System and module integration
      • Assess usage and consolidate licensing
      Data Pain Points
      • Multiple versions of same data
      • Duplication of data entry in different modules or systems
      • Poor data quality
      • Centralize core records
      • Assign data ownership
      • Single-source data entry

      Option: Replace your current system

      Replace your system to address gaps in your existing processes and various pain points

      REPLACE CURRENT SYSTEM

      Start from scratch.

      You’re transitioning from an end-of-life legacy system. Your existing system offers poor functionality and poor integration. It would likely be more cost and time efficient to replace the application and its surrounding processes all together.

      INDICATORS POTENTIAL SOLUTIONS
      Technology Pain Points
      • Lack of functionality and poor integration.
      • Obsolete technology.
      • Not aligned with technology direction or enterprise architecture plans.
      • Evaluate the ERP technology landscape.
      • Determine if you need to replace the current system with a point solution or an all-in-one solution.
      • Align ERP technologies with enterprise architecture.
      Data Pain Points
      • Limited capability to store and retrieve data.
      • Understand your data requirements.
      Process Pains
      • Insufficient tools to manage workflow.
      • Review end-to-end processes.
      • Assess user satisfaction.

      Activity 4.1.1 – Path to future state

      1+ hour
      1. Discuss the four options and the implications for your organization.
      2. Come to an agreement on your chosen path.

      The same diagram of strategies. At the top is 'Current State', at the bottom is 'Future State', and listed strategies are 'Maintain Current System', 'Augment Current System', 'Optimize', and 'Transform'.

      Activity 4.1.2 – Build a roadmap

      1-2 hours

      1. Start your roadmap with the stakeholder presentation. This is your mark in the sand to launch the project.
      2. For each item on your roadmap assign an owner who will be accountable to the completion of the roadmap item.
      3. Wherever possible, assign a start date, month, or quarter. The more specific you can be the better.
      4. Identify completion dates to create a sense of urgency. If you are struggling with start dates, it can help to start with a finish date and “back in” to a start date based on estimated efforts.

      Record this information in the ERP Strategy Report Template.

      Note:
      Your roadmap should be treated as a living document that is updated and shared with the stakeholders on a regular schedule.

      Preview of the strategy roadmap table on the next slide.

      Download the ERP Strategy Report Template

      ERP Strategy roadmap

      Initiative Owner Start Date Completion Date
      Create final workshop deliverable Info-Tech 16 September, 2021
      Review final deliverable Workshop sponsor
      Present to executive team Oct 2021
      Build business case CFO, CIO, Directors 3 weeks to build
      3-4 weeks process time
      Build an RFI for initial costings 1-2 weeks
      Stage 1 approval for requirements gathering Executive committee Milestone
      Determine and acquire BA support for next step 1 week
      Requirements gathering – level 2 processes Project team 5-6 weeks effort
      Build RFP (based on informal approval) CFO, CIO, Directors 4th calendar quarter 2022 Possible completion January 2023
      2-4 weeks

      Activity 4.1.3 – Build a visual roadmap [optional]

      1 hour

      1. For some, a visual representation of a roadmap is easier to comprehend. Consider taking the roadmap built in 4.1.2 and creating a visual.

      Record this information in the ERP Strategy Report Template.

      Preview of the visual strategy roadmap chart on the next slide.

      Download the ERP Strategy Report Template

      ERP Strategy Roadmap

      A table set up similarly to the previous one, but instead of 'Start Date' and 'Completion Date' columns there are multiple small columns broken up by fiscal quarters (i.e.. FY2022: Q1, Q2, Q3, Q4). There is a key with a light blue diamond shape representing a 'Milestone' and a blue arrow representing a 'Work in progress'; they are placed the Quarters columns according to when each row item reached a milestone or began its progress.

      Step 4.2

      Wrap up and present

      Activities
      • 4.2.1 Communication plan
      • 4.2.2 Stakeholder presentation

      This step will walk you through the following activities:

      • Build a communication plan as part of organizational change management, which includes the stakeholder presentation

      This step involves the following participants:

      • Primary stakeholders in each value stream supported by the ERP
      • ERP Applications support team

      Outcomes of this step

      • An initial communication plan for organizational change management
      • A stakeholder presentation

      Effectively communicate the changes an ERP foundation strategy will impose

      A communication plan is necessary because not everyone will react positively to change. Therefore, you must be prepared to explain the rationale behind any initiatives that are being rolled out.

      Steps:

      1. Start by building a sound communication plan.
      2. The communication plan should address all stakeholders that will be subject to change, including executives and end users.
      3. Communicate how a specific initiative will impact the way employees work and the work they do.
      4. Clearly convey the benefits of the strategy to avoid resistance.

      “The most important thing in project management is communication, communication, communication. You have to be able to put a message into business terms rather than technical terms.” (Lance Foust, I.S. Manager, Plymouth Tube Company)

      Project Goals Communication Goals Required Resources Communication Channels
      Why is your organization embarking on an ERP project? What do you want employees to know about the project? What resources are going to be utilized throughout the ERP strategy? How will your project team communicate project updates to the employees?
      Streamline processes and achieve operational efficiency. We will focus on mapping and gathering requirements for (X) mega-processes. We will be hiring process owners for each mega-process. You will be kept up to date about the project progress via email and intranet. Please feel free to contact the project owner if you have any questions.

      Activity 4.2.1 – Communication plan

      1 hour

      1. List the types of communication events and documents you will need to produce and distribute.
      2. Indicate the purpose of the event or document, who the audience is, and who is responsible for the communication.
      3. Identify who will be responsible for the development and delivery of the communication plan.

      Record this information in the ERP Strategy Report Template.

      Preview of the Communication Plan table on the next slide.

      Download the ERP Strategy Report Template

      Communication plan

      Use the communication planning template to track communication methods needed to convey information regarding ERP initiatives.

      This is designed to help your organization make ERP initiatives visible and create stakeholder awareness.

      Audience Purpose Delivery/ Format Communicator Delivery Date Status/Notes
      Front-line employees Highlight successes Bi-weekly email CEO Mondays
      Entire organization Highlight successes
      Plans for next iteration
      Monthly townhall Senior leadership Last Thursday of every month Recognize top contributors from different parts of the business. Consider giving out prizes such as coffee mugs
      Iteration demos Show completed functionality to key stakeholders Iteration completion web conference Delivery lead Every other Wednesday Record and share the demonstrations to all employees

      Conduct a presentation of the final deliverable for stakeholders

      After completing the activities and exercises within this blueprint, the final step of the process is to present the deliverable to senior management and stakeholders.

      Know Your Audience

      • Decide what needs to be presented and to whom. The purpose and format for communicating initiatives varies based on the audience. Identify the audience first to ensure initiatives are communicated appropriately.
      • IT and the business speak different languages. The business may not have the patience to try to understand IT, so it is up to IT to learn and use the language of business. Failing to put messages into language that resonates with the business will create disengagement and resistance.
      • Effective communication takes preparation to get the right content and tone to convey your real message.

      Learn From Other Organizations

      “When delivering the strategy and next steps, break the project down into consumable pieces. Make sure you deliver quick wins to retain enthusiasm and engagement.

      By making it look like a different project you keep momentum and avoid making it seem unattainable.” (Scott Clark, Innovation Credit Union)

      “To successfully sell the value of ERP, determine what the high-level business problem is and explain how ERP can be the resolution. Explicitly state which business areas ERP is going to touch. The business often has a very narrow view of ERP and perceives it as just a financial system. The key part of the strategy is that the organization sees the broader view of ERP.” (Scott Clark, Innovation Credit Union)

      Activity 4.2.2 – Stakeholder presentation

      1 hour

      1. The following sections of the ERP Strategy Report Template are designed to function as the stakeholder presentation:
        1. Workshop Overview
        2. ERP Models
        3. Roadmap
      2. You can use the Template as your presentation deck or extract the above sections to create a stand-alone stakeholder presentation.
      3. Remember to take your audience into account and anticipate the questions they may have.

      Samples of the ERP Strategy Report Template.

      Download the ERP Strategy Report Template

      Summary of Accomplishment

      Get the Most Out of Your ERP

      ERP technology is critical to facilitating an organization’s flow of information across business units. It allows for seamless integration of systems and creates a holistic view of the enterprise to support decision making. ERP implementation should not be a one-and-done exercise. There needs to be an ongoing optimization to enable business processes and optimal organizational results.

      Build an ERP Strategy and Roadmap allows organizations to proactively implement continuous assessment and optimization of their enterprise resource planning system, including:

      • Alignment and prioritization of key business and technology drivers.
      • Identification of ERP processes, including classification and gap analysis.
      • Measurement of user satisfaction across key departments.
      • Improved vendor relations.
      • Data quality initiatives.

      This formal ERP optimization initiative will drive business-IT alignment, identify IT automation priorities, and dig deep into continuous process improvement.

      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

      Research Contributors

      Name Title Organization
      Anonymous Anonymous Software industry
      Anonymous Anonymous Pharmaceutical industry
      Boris Znebel VP of Sales Second Foundation
      Brian Kudeba Director, Administrative Systems Fidelis Care
      David Lawrence Director, ERP Allegheny Technologies Inc.
      Ken Zima CIO Aquarion Water Company
      Lance Foust I.S. Manager Plymouth Tube Company
      Pooja Bagga Head of ERP Strategy & Change Transport for London
      Rob Schneider Project Director, ERP Strathcona County
      Scott Clark Innovation Credit Union
      Tarek Raafat Manager, Application Solutions IDRC
      Tom Walker VP, Information Technology StarTech.com

      Related Info-Tech Research

      Bibliography

      Gheorghiu, Gabriel. "The ERP Buyer’s Profile for Growing Companies." Selecthub. 2018. Accessed 21 Feb. 2021.

      "Maximizing the Emotional Economy: Behavioral Economics." Gallup. n.d. Accessed 21 Feb. 2021.

      Neito-Rodriguez, Antonio. Project Management | How to Prioritize Your Company's Projects. 13 Dec. 2016. Accessed 29 Nov 2021. Web.

      "A&D organization resolves organizational.“ Case Study. Panorama Consulting Group. 2021. PDF. 09 Nov. 2021. Web.

      "Process Frameworks." APQC. n.d. Accessed 21 Feb. 2021.

      Saxena, Deepak and Joe Mcdonagh. "Evaluating ERP Implementations: The Case for a Lifecycle-based Interpretive Approach." The Electronic Journal of Information Systems Evaluation, 29-37. 22 Feb. 2019. Accessed 21 Feb. 2021.

      Diagnose and Optimize Your Lead Gen Engine

      • Buy Link or Shortcode: {j2store}567|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

      88% of marketing professionals are unsatisfied with their ability to convert leads (Convince & Convert), but poor lead conversion is just a symptom of much deeper problems.

      Globally, B2B SaaS marketers without a well-running lead gen engine will experience:

      • A low volume of quality leads from their website.
      • A low conversion rate from their website visitors.
      • A long lead conversion time compared to competitors.
      • A low volume of organic website visitors.

      If treated without a root cause analysis, these symptoms often result in higher-than-average marketing spend and wasted resources. Without an accurate lead gen engine diagnostic tool and a strategy to fix the misfires, marketers will continue to waste valuable time and resources.

      Our Advice

      Critical Insight

      The lead gen engine is foundational in building profitable long-term customer relationships. It is the process through which marketers build awareness, trust, and loyalty. Without the ability to continually diagnose lead gen engine flaws, marketers will fail to optimize new customer relationship creation and long-term satisfaction and loyalty.

      Impact and Result

      With a targeted set of diagnostic tools and an optimization strategy, you will:

      • Uncover the critical weakness in your lead generation engine.
      • Develop a best-in-class lead gen engine optimization strategy that builds relationships, creates awareness, and establishes trust and loyalty with prospects.
      • Build profitable long-term customer relationships.

      Organizations who activate the findings from their lead generation diagnostic and optimization strategy will decrease the time and budget spent on lead generation by 25% to 50%. They will quickly uncover inefficiencies in their lead gen engine and develop a proven lead generation optimization strategy based on the diagnostic findings.

      Diagnose and Optimize Your Lead Gen Engine Research & Tools

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

      1. Diagnose and Optimize Your Lead Gen Engine Deck – A deck to help you diagnose what’s not working in your lead gen engine so that you can remedy issues and get back on track, building new customer relationships and driving loyalty.

      Organizations who activate the findings from their lead generation diagnostic and optimization strategy will decrease the time and budget spent on lead generation by 25% to 50%. They will quickly uncover inefficiencies in their lead gen engine and develop a proven lead generation optimization strategy based on the diagnostic findings.

      • Diagnose and Optimize Your Lead Gen Engine Storyboard

      2. Lead Gen Engine Diagnostic Tool – An easy-to-use diagnostic tool that will help you pinpoint weakness within your lead gen engine.

      The diagnostic tool allows digital marketers to quickly and easily diagnose weakness within your lead gen engine.

      • Lead Gen Engine Diagnostic Tool

      3. Lead Gen Engine Optimization Strategy Template – A step-by-step document that walks you through how to properly optimize the performance of your lead gen engine.

      Develop a best-in-class lead gen engine optimization strategy that builds relationships, creates awareness, and establishes trust and loyalty with prospects.

      • Lead Gen Engine Optimization Strategy Template

      Infographic

      Further reading

      Diagnose and Optimize Your Lead Gen Engine

      Quickly and easily pinpoint any weakness in your lead gen engine so that you stop wasting money and effort on ineffective advertising and marketing.

      EXECUTIVE BRIEF

      Analyst Perspective

      Quickly and easily pinpoint any weakness in your lead gen engine so that you stop wasting money and effort on ineffective advertising and marketing.

      The image contains a photo of Terra Higginson.

      Senior digital marketing leaders are accountable for building relationships, creating awareness, and developing trust and loyalty with website visitors, thereby delivering high-quality, high-value leads that Sales can easily convert to wins. Unfortunately, many marketing leaders report that their website visitors are low-quality and either disengage quickly or, when they engage further with lead gen engine components, they just don’t convert. These marketing leaders urgently need to diagnose what’s not working in three key areas in their lead gen engine to quickly remedy the issue and get back on track, building new customer relationships and driving loyalty. This blueprint will provide you with a tool to quickly and easily diagnose weakness within your lead gen engine. You can use the results to create a strategy that builds relationships, creates awareness, and establishes trust and loyalty with prospects.

      Terra Higginson

      Marketing Research Director

      SoftwareReviews

      Executive Summary

      Your Challenge

      Globally, business-to-business (B2B) software-as-a-service (SaaS) marketers without a well-running lead gen engine will experience:

      • A low volume of quality leads from their website.
      • A low conversion rate from their website visitors.
      • A long lead conversion time compared to competitors.
      • A low volume of organic website visitors.

      88% of marketing professionals are unsatisfied with their ability to convert leads (Convince & Convert), but poor lead conversion is just a symptom of a much larger problem with the lead gen engine. Without an accurate lead gen engine diagnostic tool and a strategy to fix the leaks, marketers will continue to waste valuable time and resources.

      Common Obstacles

      Even though lead generation is a critical element of marketing success, marketers struggle to fix the problems with their lead gen engine due to:

      • A lack of resources.
      • A lack of budget.
      • A lack of experience in implementing effective lead generation strategies.

      Most marketers spend too much on acquiring leads and not enough on converting and keeping them. For every $92 spent acquiring customers, only $1 is spent converting them (Econsultancy, cited in Outgrow). Marketers are increasingly under pressure to deliver high-quality leads to sales but work under tight budgets with inadequate or inexperienced staff who don’t understand the importance of optimizing the lead generation process.

      SoftwareReviews’ Approach

      With a targeted set of diagnostic tools and an optimization strategy, you will:

      • Uncover the critical weakness in your lead generation engine.
      • Develop a best-in-class lead gen engine optimization strategy that builds relationships, creates awareness, and establishes trust and loyalty with prospects.
      • Build profitable long-term customer relationships.

      Organizations who activate the findings from their lead generation diagnostic and optimization strategy will decrease the time and budget spent on lead generation by 25% to 50%. They will quickly uncover inefficiencies in their lead gen engine and develop a proven lead generation optimization strategy based on the diagnostic findings.

      SoftwareReviews Insight

      The lead gen engine is foundational in building profitable long-term customer relationships. It is the process through which marketers build awareness, trust, and loyalty. Without the ability to continually diagnose lead gen engine flaws, marketers will fail to optimize new customer relationship creation and long-term satisfaction and loyalty.

      Your Challenge

      88% of marketing professionals are unsatisfied with their ability to convert leads, but poor lead conversion is just a symptom of much deeper problems.

      Globally, B2B SaaS marketers without a well-running lead gen engine will experience:

      • A low volume of organic website visitors.
      • A low volume of quality leads from their website.
      • A low conversion rate from their website visitors.
      • A longer lead conversion time than competitors in the same space.

      If treated without a root-cause analysis, these symptoms often result in higher-than-average marketing spend and wasted resources. Without an accurate lead gen engine diagnostic tool and a strategy to fix the misfires, marketers will continue to waste valuable time and resources.

      88% of marketers are unsatisfied with lead conversion (Convince & Convert).

      The image contains a diagram that demonstrates a flowchart of the areas where visitors fail to convert. It incorporates observations, benchmarks, and uses a flowchart to diagnose the root causes.

      Benchmarks

      Compare your lead gen engine metrics to industry benchmarks.

      For every 10,000 people that visit your website, 210 will become leads.

      For every 210 leads, 101 will become marketing qualified leads (MQLs).

      For every 101 MQLs, 47 will become sales qualified leads (SQLs).

      For every 47 SQLs, 23 will become opportunities.

      For every 23 opportunities, nine will become customers.

      .9% to 2.1%

      36% to 48%

      28% to 46%

      39% to 48%

      32% to 40%

      Leads Benchmark

      MQL Benchmark

      SQL Benchmark

      Opportunity Benchmark

      Closing Benchmark

      The percentage of website visitors that convert to leads.

      The percentage of leads that convert to marketing qualified leads.

      The percentage of MQLs that convert to sales qualified leads.

      The percentage of SQLs that convert to opportunities.

      The percentage of opportunities that are closed.

      Midmarket B2B SaaS Industry

      Source: “B2B SaaS Marketing KPIs,” First Page Sage, 2021

      Common obstacles

      Why do most organizations improperly diagnose a misfiring lead gen engine?

      Lack of Clear Starting Point

      The lead gen engine is complex, with many moving parts, and marketers and marketing ops are often overwhelmed about where to begin diagnosis.

      Lack of Benchmarks

      Marketers often call out metrics such as increasing website visitors, contact-to-lead conversions, numbers of qualified leads delivered to Sales, etc., without a proven benchmark to compare their results against.

      Lack of Alignment Between Marketing and Sales

      Definitions of a contact, a marketing qualified lead, a sales qualified lead, and a marketing influenced win often vary.

      Lack of Measurement Tools

      Integration gaps between the website, marketing automation, sales enablement, and analytics exist within some 70% of enterprises. The elements of the marketing (and sales) tech stack change constantly. It’s hard to keep up.

      Lack of Understanding of Marketing ROI

      This drives many marketers to push the “more” button – more assets, more emails, more ad spend – without first focusing on optimization and effectiveness.

      Lack of Resources

      Marketers have an endless list of to-dos that drive them to produce daily results. Especially among software startups and mid-sized companies, there are just not enough staff with the right skills to diagnose and fix today’s sophisticated lead gen engines.

      Implications of poor diagnostics

      Without proper lead gen engine diagnostics, marketing performs poorly

      • The lead gen engine builds relationships and trust. When a broken lead gen engine goes unoptimized, customer relationships are at risk.
      • When the lead gen engine isn’t working well, customer acquisition costs rise as more expensive sales resources are charged with prospect qualification.
      • Without a well-functioning lead gen engine, marketers lack the foundation they need to create awareness among prospects – growth suffers.
      • Marketers will throw money at content or ads to generate more leads without any real understanding of engine leakage and misfires – your cost per lead climbs and reduces marketing profitability.

      Most marketers are spending too much on acquiring leads and not enough on converting and keeping them. For every $92 spent acquiring customers, only $1 is spent converting them.

      Source: Econsultancy, cited in Outgrow

      Lead gen engine optimization increases the efficiency of your marketing efforts and has a 223% ROI.

      Source: WordStream

      Benefits of lead gen engine diagnostics

      Diagnosing your lead gen engine delivers key benefits:

      • Pinpoint weakness quickly. A quick and accurate lead gen engine diagnostic tool saves Marketing 50% of the effort spent uncovering the reason for low conversion and low-quality leads.
      • Optimize more easily. Marketing executives will save 70% of the time spent creating a lead gen optimization marketing strategy based upon the diagnostic findings.
      • Maximize marketing ROI. Build toward and maintain the golden 3:1 LTV:CAC (lifetime value to customer acquisition cost) ratio for B2B SaaS marketing.
      • Stop wasting money on ineffective advertising and marketing. Up to 75% of your marketing budget is being inefficiently spent if you are running on a broken lead gen engine.

      “It’s much easier to double your business by doubling your conversion rate than by doubling your traffic. Correct targeting and testing methods can increase conversion rates up to 300 percent.” – Jeff Eisenberg, IterateStudio

      Source: Lift Division

      True benefits of fixing the lead gen engine

      These numbers add up to a significant increase in marketing influenced wins.

      175%
      Buyer Personas Increase Revenue
      Source: Illumin8

      202%
      Personalized CTAs Increase Conversions
      Source: HubSpot

      50%
      Lead Magnets Increase Conversions
      Source: ClickyDrip

      79%
      Lead Scoring Increases Conversions
      Source: Bloominari

      50%
      Lead Nurturing Increases Conversions
      Source: KevinTPayne.com

      80%
      Personalized Landing Pages Increase Conversions
      Source: HubSpot

      Who benefits from an optimized lead gen engine?

      This Research Is Designed for:

      • Senior digital marketing leaders who are:
        • Looking to increase conversions.
        • Looking to increase the quality of leads.
        • Looking to increase the value of leads.

      This Research Will Help You:

      • Diagnose issues with your lead gen engine.
      • Create a lead gen optimization strategy and a roadmap.

      This Research Will Also Assist:

      • Digital marketing leaders and product marketing leaders who are:
        • Looking to decrease the effort needed by Sales to close leads.
        • Looking to increase leadership’s faith in Marketing’s ability to generate high-quality leads and conversions.

      This Research Will Help Them:

      • Align the Sales and Marketing teams.
      • Receive the necessary buy-in from management to increase marketing spend and headcount.
      • Avoid product failure.
      The image contains a screenshot of the thought model that is titled: Diagnose and Optimize your Lead Gen Engine. The image contains the screenshot of the previous image shown on Where Lead Gen Engines Fails, and includes new information. The flowchart connects to a box that says: STOP, Your engine is broken. It then explains phase 1, the diagnostic, and then phase 2 Optimization strategy.

      SoftwareReviews’ approach

      1. Diagnose Misfires in the Lead Gen Engine
      2. Identifying any areas of weakness within your lead gen engine is a fundamental first step in improving conversions, ROI, and lead quality.

      3. Create a Lead Gen Optimization Strategy
      4. Optimize your lead gen strategy with an easily customizable template that will provide your roadmap for future growth.

      The SoftwareReviews Methodology to Diagnose and Optimize Your Lead Gen Engine

      1. Lead Gen Engine Diagnostic

      2. Lead Gen Engine Optimization Strategy

      Phase Steps

      1. Select lead gen engine optimization steering committee & working team
      2. Gather baseline metrics
      3. Run the lead gen engine diagnostic
      4. Identify low-scoring areas & prioritize lead gen engine fixes
      1. Define the roadmap
      2. Create lead gen engine optimization strategy
      3. Present strategy to steering committee

      Phase Outcomes

      • Identify weakness within the lead gen engine.
      • Prioritize the most important fixes within the lead gen engine.
      • Create a best-in-class lead gen engine optimization strategy and roadmap that builds relationships, creates awareness, and develops trust and loyalty with website visitors.
      • Increase leadership’s faith in Marketing’s ability to generate high-quality leads and conversions.

      Insight Summary

      The lead gen engine is the foundation of marketing

      The lead gen engine is critical to building relationships. It is the foundation upon which marketers build awareness, trust, and loyalty.

      Misalignment between Sales and Marketing is costly

      Digital marketing leaders need to ensure agreement with Sales on the definition of a marketing qualified lead (MQL), as it is the most essential element of stakeholder alignment.

      Prioritization is necessary for today’s marketer

      By prioritizing the fixes within the lead gen engine that have the highest impact, a marketing leader will be able to focus their optimization efforts in the right place.

      Stop, your engine is broken

      Any advertising or effort expended while running marketing on a broken lead gen engine is time and money wasted. It is only once the lead gen engine is fixed that marketers will see the true results of their efforts.

      Tactical insight

      Without a well-functioning lead gen engine, marketers risk wasting valuable time and money because they aren’t creating relationships with prospects that will increase the quality of leads, conversion rate, and lifetime value.

      Tactical insight

      The foundational lead relationship must be built at the marketing level, or else Sales will be entirely responsible for creating these relationships with low-quality leads, risking product failure.

      Blueprint Deliverable:

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

      Lead Gen Engine Diagnostic

      An efficient and easy-to-use diagnostic tool that uncovers weakness in your lead gen engine.

      The image contains a screenshot of the Lead Gen Engine Diagnostic is shown.

      Key Deliverable:

      Lead Gen Engine Optimization Strategy Template

      The image contains a screenshot of the Lead Gen Engine Optimization Strategy.

      A comprehensive strategy for optimizing conversions and increasing the quality of leads.

      SoftwareReviews Offers Various Levels of Support to Meet Your Needs

      Included within Advisory Membership:

      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.”

      Optional add-ons:

      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.”

      Guided Implementation

      What does a typical GI on lead gen engine diagnostics look like?

      Diagnose Your Lead Gen Engine

      Call #1: Scope requirements, objectives, and specific challenges with your lead gen engine.

      Call #2: Gather baseline metrics and discuss the steering committee and working team.

      Call #3: Review results from baseline metrics and answer questions.

      Call #4: Discuss the lead gen engine diagnostic tool and your steering committee.

      Call #5: Review results from the diagnostic tool and answer questions.

      Develop Your Lead Gen Engine Optimization Strategy

      Call #6: Identify components to include in the lead gen engine optimization strategy.

      Call #7: Discuss the roadmap for continued optimization.

      Call #8: Review final lead gen engine optimization strategy.

      Call #9: (optional) Follow-up quarterly to check in on progress and answer questions.

      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.

      Workshop Overview

      Day 1

      Day 2

      Activities

      Complete Lead Gen Engine Diagnostic

      1.1 Identify the previously selected lead gen engine steering committee and working team.

      1.2 Share the baseline metrics that were gathered in preparation for the workshop.

      1.3 Run the lead gen engine diagnostic.

      1.4 Identify low-scoring areas and prioritize lead gen engine fixes.

      Create Lead Gen Engine Optimization Strategy

      2.1 Define the roadmap.

      2.2 Create a lead gen engine optimization strategy.

      2.3 Present the strategy to the steering committee.

      Deliverables

      1. Lead gen engine diagnostic scorecard

      1. Lead gen engine optimization strategy

      Contact your account representative for more information.

      workshops@infotech.com1-888-670-8889

      Phase 1

      Lead Gen Engine Diagnostic

      Phase 1

      Phase 2

      1.1 Select lead gen engine steering committee & working team

      1.2 Gather baseline metrics

      1.3 Run the lead gen engine diagnostic

      1.4 Identify & prioritize low-scoring areas

      2.1 Define the roadmap

      2.2 Create lead gen engine optimization strategy

      2.3 Present strategy to steering committee

      This phase will walk you through the following activities:

      The diagnostic tool will allow you to quickly and easily identify the areas of weakness in the lead gen engine by answering some simple questions. The steps include:

      • Select the lead gen engine optimization committee and team.
      • Gather baseline metrics.
      • Run the lead gen engine diagnostic.
      • Identify and prioritize low-scoring areas.

      This phase involves the following participants:

      • Marketing lead
      • Lead gen engine steering committee

      Step 1.1

      Identify Lead Gen Engine Optimization Steering Committee & Working Team

      Activities

      1.1.1 Identify the lead gen engine optimization steering committee and document in the Lead Gen Engine Optimization Strategy Template

      1.1.2 Identify the lead gen engine optimization working team document in the Lead Gen Engine Optimization Strategy Template

      This step will walk you through the following activities:

      Identify the lead gen engine optimization steering committee.

      This step involves the following participants:

      • Marketing director
      • Leadership

      Outcomes of this step

      An understanding of who will be responsible and who will be accountable for accomplishing the lead gen engine diagnostic and optimization strategy.

      1.1.1 Identify the lead gen engine optimization steering committee

      1-2 hours

      1. The marketing lead should meet with leadership to determine who will make up the steering committee for the lead gen engine optimization.
      2. Document the steering committee members in the Lead Gen Engine Optimization Strategy Template slide entitled “The Steering Committee.”

      Input

      Output

      • Stakeholders and leaders across the various functions outlined on the next slide
      • List of the lead gen engine optimization strategy steering committee members

      Materials

      Participants

      • Lead Gen Engine Optimization Strategy Template
      • Marketing director
      • Executive leadership

      Download the Lead Gen Engine Optimization Strategy Template

      Lead gen engine optimization steering committee

      Consider the skills and knowledge required for the diagnostic and the implementation of the strategy. Constructing a cross-functional steering committee will be essential for the optimization of the lead gen engine. At least one stakeholder from each relevant department should be included in the steering committee.

      Required Skills/Knowledge

      Suggested Functions

      • Target Buyer
      • Product Roadmap
      • Brand
      • Competitors
      • Campaigns/Lead Gen
      • Sales Enablement
      • Media/Analysts
      • Customer Satisfaction
      • Data Analytics
      • Ad Campaigns
      • Competitive Intelligence
      • Product Marketing
      • Product Management
      • Creative Director
      • Competitive Intelligence
      • Field Marketing
      • Sales
      • PR/AR/Corporate Comms
      • Customer Success
      • Analytics Executive
      • Campaign Manager

      For small and mid-sized businesses (SMB), because employees wear many different hats, assign people that have the requisite skills and knowledge, not the role title.

      The image contains examples of small and mid-sized businesses, and the different employee recommendations.

      1.1.2 Identify the lead gen engine optimization working team

      1-2 hours

      1. The marketing director should meet with leadership to determine who will make up the working team for the lead gen engine optimization.
      2. Finalize selection of team members and fill out the slide entitled “The Working Team” in the Lead Gen Engine Optimization Strategy Template.

      Input

      Output

      • Executives and analysts responsible for execution of tasks across Marketing, Product, Sales, and IT
      • The lead gen engine optimization working team

      Materials

      Participants

      • The Lead Gen Engine Optimization Strategy Template
      • Marketing director
      • Executive leadership

      Download the Lead Gen Engine Optimization Strategy Template

      Lead gen engine working team

      Consider the working skills required for the diagnostic and implementation of the strategy and assign the working team.

      Required Skills/Knowledge

      Suggested Titles

      • SEO
      • Inbound Marketing
      • Paid Advertising
      • Website Development
      • Content Creation
      • Lead Scoring
      • Landing Pages
      • A/B Testing
      • Email Campaigns
      • Marketing and Sales Automation
      • SEO Analyst
      • Content Marketing Manager
      • Product Marketing Manager
      • Website Manager
      • Website Developer
      • Sales Manager
      • PR
      • Customer Success Manager
      • Analytics Executive
      • Campaign Manager

      Step 1.2

      Gather Baseline Metrics

      Activities

      1.2.1 Gather baseline metrics and document in the Lead Gen Engine Optimization Strategy Template

      This step will walk you through the following activities:

      Gather baseline metrics.

      This step involves the following participants:

      • Marketing director
      • Analytics lead

      Outcomes of this step

      Understand and document baseline marketing metrics.

      1.2.1 Gather baseline metrics and document in the Lead Gen Engine Optimization Strategy Template

      1-2 hours

      1. Use the example on the next slide to learn about the B2B SaaS industry-standard baseline metrics.
      2. Meet with the analytics lead to analyze and record the data within the “Baseline Metrics” slide of the Lead Gen Engine Optimization Strategy Template. The baseline metrics will include:
        • Unique monthly website visitors
        • Visitor to lead conversion rate
        • Lead to MQL conversion rate
        • Customer acquisition cost (CAC)
        • Lifetime customer value to customer acquisition cost (LTV to CAC) ratio
        • Campaign ROI

      Recording the baseline data allows you to measure the impact your lead gen engine optimization strategy has over the baseline.

      Input

      Output
      • Marketing and analytics data
      • Documentation of baseline marketing metrics

      Materials

      Participants

      • The lead gen engine optimization strategy
      • Marketing director
      • Analytics lead

      B2B SaaS baseline metrics

      Industry standard metrics for B2B SaaS in 2022

      Unique Monthly Visitors

      Industry standard is 5% to 10% growth month over month.

      Visitor to Lead Conversion

      Industry standard is between 0.9% to 2.1%.

      Lead to MQL Conversion

      Industry standard is between 36% to 48%.

      CAC

      Industry standard is a cost of $400 to $850 per customer acquired.

      LTV to CAC Ratio

      Industry standard is an LTV:CAC ratio between 3 to 6.

      Campaign ROI

      Email: 201%

      Pay-Per-Click (PPC): 36%

      LinkedIn Ads: 94%

      Source: “B2B SaaS Marketing KPIs,” First Page Sage, 2021

      Update the Lead Gen Optimization Strategy Template with your company’s baseline metrics.

      Download the Lead Gen Engine Optimization Strategy Template

      Step 1.3

      Run the Lead Gen Engine Diagnostic

      Activities

      1.3.1 Gather steering committee and working team to complete the Lead Gen Engine Diagnostic Tool

      This step will walk you through the following activities:

      Gather the steering committee and answer the questions within the Lead Gen Engine Diagnostic Tool.

      This step involves the following participants:

      • Lead gen engine optimization working team
      • Lead gen engine optimization steering committee

      Outcomes of this step

      Lead gen engine diagnostic and scorecard

      1.3.1 Gather the committee and team to complete the Lead Gen Engine Diagnostic Tool

      2-3 hours

      1. Schedule a two-hour meeting with the steering committee and working team to complete the Lead Gen Engine Diagnostic Tool. To ensure the alignment of all departments and the quality of results, all steering committee members must participate.
      2. Answer the questions within the tool and then review your company’s results in the Results tab.

      Input

      Output

      • Marketing and analytics data
      • Diagnostic scorecard for the lead gen engine

      Materials

      Participants

      • Lead Gen Engine Diagnostic Tool
      • Marketing director
      • Analytics lead

      Download the Lead Gen Engine Diagnostic Tool

      Step 1.4

      Identify & Prioritize Low-Scoring Areas

      Activities

      1.4.1 Identify and prioritize low-scoring areas from the diagnostic scorecard

      This step will walk you through the following activities:

      Identify and prioritize the low-scoring areas from the diagnostic scorecard.

      This step involves the following participants:

      • Marketing director

      Outcomes of this step

      A prioritized list of the lead gen engine problems to include in the Lead Gen Engine Optimization Strategy Template

      1.4.1 Identify and prioritize low-scoring areas from the diagnostic scorecard

      1 hour

      1. Transfer the results from the Lead Gen Engine Diagnostic Scorecard Results tab to the Lead Gen Engine Optimization Strategy Template slide entitled “Lead Gen Engine Diagnostic Scorecard.”
        • Results between 0 and 2 should be listed as high-priority fixes on the “Lead Gen Engine Diagnostic Scorecard” slide. You will use these areas for your strategy.
        • Results between 2 and 3 should be listed as medium-priority fixes on “Lead Gen Engine Diagnostic Scorecard” slide. You will use these areas for your strategy.
        • Results between 3 and 4 are within the industry standard and will require no fixes or only small adjustments.

      Input

      Output

      • Marketing and analytics data
      • Documentation of baseline marketing metrics

      Materials

      Participants

      • Lead Gen Engine Optimization Strategy Template
      • Marketing director
      • Analytics lead

      Download the Lead Gen Engine Diagnostic Tool

      Phase 2

      Lead Gen Engine Optimization Strategy

      Phase 1

      Phase 2

      1.1 Select lead gen engine steering committee & working team

      1.2 Gather baseline metrics

      1.3 Run the lead gen engine diagnostic

      1.4 Identify & prioritize low-scoring areas

      2.1 Define the roadmap

      2.2 Create lead gen engine optimization strategy

      2.3 Present strategy to steering committee

      This phase will walk you through the following activities:

      Create a best-in-class lead gen optimization strategy and roadmap based on the weaknesses found in the diagnostic tool. The steps include:

      • Define the roadmap.
      • Create a lead gen engine optimization strategy.
      • Present the strategy to the steering committee.

      This phase involves the following participants:

      • Marketing director

      Step 2.1

      Define the Roadmap

      Activities

      2.1.1 Create the roadmap for the lead gen optimization strategy

      This step will walk you through the following activities:

      Create the optimization roadmap for your lead gen engine strategy.

      This step involves the following participants:

      • Marketing director

      Outcomes of this step

      Strategy roadmap

      2.1.1 Create the roadmap for the lead gen optimization strategy

      1 hour

      1. Copy the results from "The Lead Gen Engine Diagnostic Scorecard" slide to the "Value, Resources & Roadmap Matrix" slide in the Lead Gen Engine Optimization Strategy Template. Adjust the Roadmap Quarter column after evaluating the internal resources of your company and expected value generated.
      2. Using these results, create your strategy roadmap by updating the slide entitled “The Strategy Roadmap” in the Lead Gen Engine Optimization Strategy Template.

      Input

      Output

      • Diagnostic scorecard
      • Strategy roadmap

      Materials

      Participants

      • Lead Gen Engine Optimization Strategy Template
      • Marketing Director

      Download the Lead Gen Engine Optimization Strategy Template

      Step 2.2

      Create the Lead Gen Engine Optimization Strategy

      Activities

      2.2.1 Customize your lead gen engine optimization strategy using the template

      This step will walk you through the following activities:

      Create a lead gen engine optimization strategy based on the results of your diagnostic scorecard.

      This step involves the following participants:

      Marketing director

      Outcomes of this step

      A leadership-facing lead gen optimization strategy

      2.2.1 Customize your lead gen engine optimization strategy using the template

      2-3 hours

      Review the strategy template:

      1. Use "The Strategy Roadmap" slide to organize the remaining slides from the Q1, Q2, and Q3 sections.
        1. Fixes listed in "The Strategy Roadmap" under Q1 should be placed within the Q1 section.
        2. Fixes listed in "The Strategy Roadmap" under Q2 should be placed within the Q2 section.
        3. Fixes listed in "The Strategy Roadmap" under Q3 should be placed within the Q3 section.

      Input

      Output

      • The strategy roadmap
      • Your new lead gen engine optimization strategy

      Materials

      Participants

      • Lead Gen Engine Optimization Strategy Template
      • Marketing director

      Download the Lead Gen Engine Optimization Strategy Template

      Step 2.3

      Present the strategy to the steering committee

      Activities

      2.3.1 Present the findings of the diagnostic and the lead gen optimization strategy to the steering committee.

      This step will walk you through the following activities:

      Get executive buy-in on the lead gen engine optimization strategy.

      This step involves the following participants:

      • Marketing director
      • Steering committee

      Outcomes of this step

      • Buy-in from leadership on the strategy

      2.3.1 Present findings of diagnostic and lead gen optimization strategy to steering committee

      1-2 hours

      1. Schedule a presentation to present the findings of the diagnostic, the lead gen engine optimization strategy, and the roadmap to the steering committee.
      InputOutput
      • Your company’s lead gen engine optimization strategy
      • Official outline of strategy and buy-in from executive leadership

      Materials

      Participants

      • Lead Gen Engine Optimization Strategy Template
      • Marketing director
      • Executive leadership
      • Steering committee

      Download the Lead Gen Engine Optimization Strategy Template

      Related SoftwareReviews Research

      Create a Buyer Persona and Journey

      Make it easier to market, sell, and achieve product-market fit with deeper buyer understanding.

      • Reduce time and treasure wasted chasing the wrong prospects.
      • Improve product-market fit.
      • Increase open and click-through rates in your lead gen engine.
      • Perform more effective sales discovery and increase eventual win rates.

      Optimize Lead Generation With Lead Scoring

      In today’s competitive environment, optimizing Sales’ resources by giving them qualified leads is key to B2B marketing success.

      • Lead scoring is a must-have capability for high-tech marketers.
      • Without lead scoring, marketers will see increased costs of lead generation and decreased SQL-to-opportunity conversion rates.
      • Lead scoring increases sales productivity and shortens sales cycles.

      Build a More Effective Go-to-Market Strategy

      Creating a compelling go-to-market strategy and keeping it current is a critical software company function – as important as financial strategy, sales operations, and even corporate business development – given its huge impact on the many drivers of sustainable growth.

      • Align stakeholders on a common vision and execution plan.
      • Build a foundation of buyer and competitive understanding.
      • Deliver a team-aligned launch plan that enables commercial success.

      Bibliography

      “11 Lead Magnet Statistics That Might Surprise You.” ClickyDrip, 28 Dec. 2020. Accessed April 2022.

      “45 Conversion Rate Optimization Statistics Every Marketer Should Know.” Outgrow, n.d. Accessed April 2022.

      Bailyn, Evan. “B2B SaaS Funnel Conversion Benchmarks.” First Page Sage, 24 Feb. 2021. Accessed April 2022.

      Bailyn, Evan. “B2B SaaS Marketing KPIs: Behind the Numbers.” First Page Sage, 1 Sept. 2021. Accessed April 2022.

      Conversion Optimization.” Lift Division, n.d. Accessed April 2022.

      Corson, Sean. “LTV:CAC Ratio [2022 Guide] | Benchmarks, Formula, Tactics.” Daasity, 3 Nov. 2021. Accessed April 2022.

      Dudley, Carrie. “What are personas?” Illumin8, 26 Jan. 2018. Accessed April 2022.

      Godin, Seth. “Permission Marketing.” Accenture, Oct. 2009. Accessed April 2022.

      Lebo, T. “Lead Conversion Statistics All B2B Marketers Need to Know.” Convince & Convert, n.d. Accessed April 2022.

      Lister, Mary. “33 CRO & Landing Page Optimization Stats to Fuel Your Strategy.” WordStream, 24 Nov. 2021. [Accessed April 2022].

      Nacach, Jamie. “How to Determine How Much Money to Spend on Lead Generation Software Per Month.” Bloominari, 18 Sept. 2018. Accessed April 2022.

      Needle, Flori. “11 Stats That Make a Case for Landing Pages.” HubSpot, 10 June 2021. Accessed April 2022.

      Payne, Kevin. “10 Effective Lead Nurturing Tactics to Boost Your Sales.” Kevintpayne.com, n.d. Accessed April 2022.

      Tam, Edwin. “ROI in Marketing: Lifetime Value (LTV) & Customer Acquisition Cost (CAC).” Construct Digital, 19 Jan. 2016. Accessed April 2022.

      Ransomware Cyber Attack. The real Disaster Recovery Scenario

      Cyber-ransomware criminals need to make sure that you cannot simply recover your encrypted data via your backups. They must make it look like paying is your only option. And if you do not have a strategy that takes this into account, unfortunately, you may be up the creek without a paddle. because how do they make their case? Bylooking for ways to infect your backups, way before you find out you have been compromised. 

      That means your standard disaster recovery scenarios provide insufficient protection against this type of event. You need to think beyond DRP and give consideration to what John Beattie and Michael Shandrowski call "Cyber Incident Recovery Risk management" (CIR-RM).  

      incident, incident management, cybersecurity, cyber, disaster recovery, drp, business continuity, bcm, recovery

      Register to read more …

      Build Your Security Operations Program From the Ground Up

      • Buy Link or Shortcode: {j2store}263|cart{/j2store}
      • member rating overall impact: 9.7/10 Overall Impact
      • member rating average dollars saved: $56,299 Average $ Saved
      • member rating average days saved: 43 Average Days Saved
      • Parent Category Name: Security Processes & Operations
      • Parent Category Link: /security-processes-and-operations
      • Analysts cannot monitor and track events coming from multiple tools because they have no visibility into the threat environment.
      • Incident management takes away time from problem management because processes are ad hoc and the continuous monitoring, collection, and analysis of massive volumes of security event data is responsive rather than tactical.
      • Organizations are struggling to defend against and prevent threats while juggling business, compliance, and consumer obligations.

      Our Advice

      Critical Insight

      • Security operations is no longer a center but a process. The need for a physical security hub has evolved into the virtual fusion of prevention, detection, analysis, and response efforts. When all four functions operate as a unified process, your organization will be able to proactively combat changes in the threat landscape.
      • Raw data without correlation is a waste of time, money, and effort. A SIEM on its own will not provide this contextualization and needs configuration. Prevention, detection, analysis, and response processes must contextualize threat data and supplement one another – true value will only be realized once all four functions operate as a unified process.
      • If you are not communicating, then you are not secure. Collaboration eliminates siloed decisions by connecting people, processes, and technologies. You leave less room for error, consume fewer resources, and improve operational efficiency with a transparent security operations process.

      Impact and Result

      • A centralized security operations process actively transforms security events and threat information into actionable intelligence, driving security prevention, detection, analysis, and response processes that address the increasing sophistication of cyberthreats while guiding continuous improvement.
      • This blueprint will walk through the steps of developing a flexible and systematic security operations program relevant to your organization.

      Build Your Security Operations Program From the Ground Up Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should build a security operations program, 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. Establish your foundation

      Determine how to establish the foundation of your security operations.

      • Build Your Security Operations Program From the Ground Up – Phase 1: Establish Your Foundation
      • Information Security Pressure Analysis Tool

      2. Assess your current state

      Assess the maturity of your prevention, detection, analysis, and response processes.

      • Build Your Security Operations Program From the Ground Up – Phase 2: Assess Your Current State
      • Security Operations Roadmap Tool

      3. Design your target state

      Design a target state and improve your governance and policy solutions.

      • Build Your Security Operations Program From the Ground Up – Phase 3: Design Your Target State
      • Security Operations Policy

      4. Develop an implementation roadmap

      Make your case to the board and develop a roadmap for your prioritized security initiatives.

      • Build Your Security Operations Program From the Ground Up – Phase 4: Develop an Implementation Roadmap
      • In-House vs. Outsourcing Decision-Making Tool
      • Security Operations MSSP RFP Template
      • Security Operations Project Charter Template
      • Security Operations RACI Tool
      • Security Operations Metrics Summary Document
      [infographic]

      Workshop: Build Your Security Operations Program From the Ground Up

      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 Your Foundation

      The Purpose

      Identify security obligations and the security operations program’s pressure posture.

      Assess current people, process, and technology capabilities.

      Determine foundational controls and complete system and asset inventory.

      Key Benefits Achieved

      Identified the foundational elements needed for planning before a security operations program can be built

      Activities

      1.1 Define your security obligations and assess your security pressure posture.

      1.2 Determine current knowledge and skill gaps.

      1.3 Shine a spotlight on services worth monitoring.

      1.4 Assess and document your information system environment.

      Outputs

      Customized security pressure posture

      Current knowledge and skills gaps

      Log register of essential services

      Asset management inventory

      2 Assess Current Security Operations Processes

      The Purpose

      Identify the maturity level of existing security operations program processes.

      Key Benefits Achieved

      Current maturity assessment of security operations processes

      Activities

      2.1 Assess the current maturity level of the existing security operations program processes.

      Outputs

      Current maturity assessment

      3 Design a Target State

      The Purpose

      Design your optimized target state.

      Improve your security operations processes with governance and policy solutions.

      Identify and prioritize gap initiatives.

      Key Benefits Achieved

      A comprehensive list of initiatives to reach ideal target state

      Optimized security operations with repeatable and standardized policies

      Activities

      3.1 Complete standardized policy templates.

      3.2 Map out your ideal target state.

      3.3 Identify gap initiatives.

      Outputs

      Security operations policies

      Gap analysis between current and target states

      List of prioritized initiatives

      4 Develop an Implementation Roadmap

      The Purpose

      Formalize project strategy with a project charter.

      Determine your sourcing strategy for in-house or outsourced security operations processes.

      Assign responsibilities and complete an implementation roadmap.

      Key Benefits Achieved

      An overarching and documented strategy and vision for your security operations

      A thorough rationale for in-house or outsourced security operations processes

      Assigned and documented responsibilities for key projects

      Activities

      4.1 Complete a security operations project charter.

      4.2 Determine in-house vs. outsourcing rationale.

      4.3 Identify dependencies of your initiatives and prioritize initiatives in phases of implementation.

      4.4 Complete a security operations roadmap.

      Outputs

      Security operations project charter

      In-house vs. outsourcing rationale

      Initiatives organized according to phases of development

      Planned and achievable security operations roadmap

      Learn the right way to manage metrics

      • Parent Category Name: Improve Your Processes
      • Parent Category Link: /improve-your-processes

      Learn to use metrics in the right way. Avoid staff (subconciously) gaming the numbers, as it is only natural to try to achieve the objective. This is really a case of be careful what you wish for, you may just get it.

      Register to read more …

      Improve IT Operations With AI and ML

      • Buy Link or Shortcode: {j2store}454|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: Operations Management
      • Parent Category Link: /i-and-o-process-management
      • Many IT departments experience difficulty with meeting the business' expectations for service delivery on a regular basis.
      • Despite significant investment in improving various areas of IT operations, you still feel like you’re constantly firefighting.
      • To tackle these issues, businesses tend to invest in purchasing multiple solutions. This not only complicates their IT operations, but also, in some cases, deteriorates functionality.

      Our Advice

      Critical Insight

      • To leverage AI capabilities, you first need to assess the current state of your IT operations and know what your priorities are.
      • Contemplate use cases that will get the most benefit from automation and start with processes that you are relatively comfortable handling.
      • Analyze your initial plan to identify easy wins, then expand your AIOps.

      Impact and Result

      • Perform a current state assessment to spot which areas within your operations management are the least mature and causing you the most grief. Identify which functional areas within operations management need to be prioritized for improvement.
      • Make a shortlist of use cases that will get the most benefit from AI-based technology.
      • Prepare a plan to deploy AI capabilities to improve your IT operations.

      Improve IT Operations With AI and ML Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out about the latest improvements in AIOps and how these can help you improve your IT operations. 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. Assess the current state of IT operations management

      Identify where your organization currently stands in its operations management practices.

      • AIOps Project Summary Template
      • AIOps Prerequisites Assessment Tool

      2. Identify initiatives that align with operations requirements

      Recognize the benefits of AI and ML for your business. Determine the necessary roles and responsibilities for potential initiatives, then develop and assess your shortlist.

      • AIOps RACI Template
      • AIOps Shortlisting Tool

      3. Develop the AI roadmap

      Analyze your ROI for AIOps and create an action plan. Communicate your AI and ML initiatives to stakeholders to obtain their support.

      • AIOps ROI Calculator
      • AIOps Roadmap Tool
      • AIOps Communications Plan Template
      [infographic]

      The MVP Major Incident Manager

      The time has come to hire a new major incident manager. How do you go about that? How do you choose the right candidate? Major incident managers must have several typically conflicting traits, so how do you pick the right person? Let's dive into that.

      Register to read more …

      Choose Your Mobile Platform and Tools

      • Buy Link or Shortcode: {j2store}281|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
      • Organizations see the value of mobile applications in improving productivity and reach of day-to-day business and IT operations. This motivates leaders to begin the planning of their first application.
      • However, organizations often lack the critical foundational knowledge and skills to deliver and maintain high quality and valuable applications that meet business and user priorities and technical requirements.
      • Mobile technologies and trends are continually evolving and maturing. It is hard to predict which trends will make a significant impact and to prepare current mobile investments to harness their value of these trends.

      Our Advice

      Critical Insight

      • Mobile applications can stress the stability, reliability, and overall quality of your enterprise systems and services. They will also increase your security risks because of the exposure of your enterprise technology assets to unsecured networks and devices.
      • High costs of entry may restrict what built-in features your users can have in their mobile experience. Workarounds may not be sufficient to offset the costs of certain built-in feature needs.
      • Many operating models do not enable or encourage the collaboration required to fully understand user needs and behaviors and evaluate mobile opportunities and underlying operational systems from multiple perspectives.

      Impact and Result

      • Establish the right expectations. Understand your mobile users by learning their needs, challenges, and behaviors. Discuss the current state of your systems and your high priority non-functional requirements to determine what to expect from your mobile applications.
      • Choose the right mobile platform approach and shortlist your mobile delivery solutions. Obtain a thorough view of the business and technical complexities of your mobile opportunities, including current mobile delivery capabilities and system compatibilities.
      • Create your mobile roadmap. Describe the gradual rollout of your mobile technologies through minimal valuable products (MVPs).

      Choose Your Mobile Platform and Tools Research & Tools

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

      1. Choose Your Mobile Platform and Tools Storyboard

      This blueprint helps you develop an approach to understand the mobile experience your stakeholders want your users to have and select the appropriate platform and delivery tools to meet these expectations.

      • Choose Your Mobile Platform and Tools Storyboard

      2. Mobile Application Delivery Communication Template – Clearly communicate the goal and approach of your mobile application implementation in a language your audience understands.

      This template narrates a story to describe the need and expectations of your low- and no-code initiative to get buy-in from stakeholders and interested parties.

      • Mobile Application Delivery Communication Template

      Infographic

      Workshop: Choose Your Mobile Platform and Tools

      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 Choose Your Platform and Delivery Solution

      The Purpose

      Choose the right mobile platform.

      Shortlist your mobile delivery solution and desired features and services.

      Key Benefits Achieved

      A chosen mobile platform that meets user and enterprise needs.

      Candidate mobile delivery solutions that meet your delivery needs and capacity of your teams.

      Activities

      1.1 Select your platform approach.

      1.2 Shortlist your mobile delivery solution.

      1.3 Build your feature and service lists.

      Outputs

      Desired mobile platform approach.

      Shortlisted mobile delivery solutions.

      Desired list of vendor features and services.

      2 Create Your Roadmap

      The Purpose

      Design the mobile application minimal viable product (MVP).

      Create your mobile roadmap.

      Key Benefits Achieved

      An achievable and valuable mobile application that is scalable for future growth.

      Clear intent of business outcome delivery and completing mobile delivery activities.

      Activities

      2.1 Define your MVP release.

      2.2 Build your roadmap.

      Outputs

      MVP design.

      Mobile delivery roadmap.

      3 Set the Mobile Context

      The Purpose

      Understand your user’s environment needs, behaviors, and challenges.

      Define stakeholder expectations and ensure alignment with the holistic business strategy.

      Identify your mobile application opportunities.

      Key Benefits Achieved

      Thorough understanding of your mobile user and opportunities where mobile applications can help.

      Level set stakeholder expectations and establish targeted objectives.

      Prioritized list of mobile opportunities.

      Activities

      3.1 Generate user personas with empathy maps.

      3.2 Build your mobile application canvas.

      3.3 Build your mobile backlog.

      Outputs

      User personas.

      Mobile objectives and metrics.

      Mobile opportunity backlog.

      4 Identify Your Technical Needs

      The Purpose

      Define the mobile experience you want to deliver and the features to enable it.

      Understand the state of your current system to support mobile.

      Identify your definition of mobile application quality.

      List the concerns with mobile delivery.

      Key Benefits Achieved

      Clear understanding of the desired mobile experience.

      Potential issues and risks with enabling mobile on top of existing systems.

      Grounded understanding of mobile application quality.

      Holistic readiness assessment to proceed with mobile delivery.

      Activities

      4.1 Discuss your mobile needs.

      4.2 Conduct a technical assessment.

      4.3 Define mobile application quality.

      4.4 Verify your decision to deliver mobile applications.

      Outputs

      List of mobile features to enable the desired mobile experience.

      System current assessment.

      Mobile application quality definition.

      Verification to proceed with mobile delivery.

      Further reading

      Choose Your Mobile Platform and Tools

      Maximize the value of your mobile investments by prioritizing technology decisions on user experience, business priorities, and system quality.

      EXECUTIVE BRIEF

      Analyst Perspective

      Mobile is the way of working.

      Workers require access to enterprise products, data, and services anywhere at anytime on any device. Give them the device-specific features, offline access, desktop-like interfaces, and automation capabilities they need to be productive.

      To be successful, you need to instill a collaborative business-IT partnership. Only through this partnership will you be able to select the right mobile platform and tools to balance desired outcomes with enterprise security, performance, integration, quality, and other delivery capacity concerns.

      This is a picture of Andrew Kum-Seun Senior Research Analyst, Application Delivery and Application Management Info-Tech Research Group

      Andrew Kum-Seun
      Senior Research Analyst,
      Application Delivery and Application Management
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      • Organizations see the value of mobile applications in improving productivity and reach of day-to-day business and IT operations. This motivates leaders to begin the planning of their first application.
      • However, organizations often lack the critical foundational knowledge and skills to deliver and maintain high quality and valuable applications that meet business and user priorities and technical requirements.
      • Mobile technologies and trends are continually evolving and maturing. It is hard to predict which trends will make a significant impact and to prepare current mobile investments to harness the value of these trends.

      Common Obstacles

      • Mobile applications can stress the stability, reliability and overall quality of your enterprise systems and services. They will also increase your security risks because of the exposure of your enterprise technology assets to unsecured networks and devices.
      • High costs of entry may restrict what native features your users can have in their mobile experience. Workarounds may not be sufficient to offset the costs of certain native feature needs.
      • Many operating models do not enable or encourage the collaboration required to fully understand user needs and behaviors and evaluate mobile opportunities and underlying operational systems from multiple perspectives.

      Info-Tech's Approach

      • Establish the right expectations. Understand your mobile users by learning their needs, challenges, and behaviors. Discuss the current state of your systems and your high priority non-functional requirements to determine what to expect from your mobile applications.
      • Choose the right mobile platform approach and shortlist your mobile delivery solutions. Obtain a thorough view of the business and technical complexities of your mobile opportunities, including current mobile delivery capabilities and system compatibilities.
      • Create your mobile roadmap. Describe the gradual rollout of your mobile technologies through minimal valuable products (MVPs).

      Insight Summary

      Overarching Info-Tech Insight

      Treat your mobile applications as digital products. Digital products are continuously modernized to ensure they are fit-for-purpose, secured, accessible, and immersive. A successful mobile experience involves more than just the software and supporting system. It involves good training and onboarding, efficient delivery turnaround, and a clear and rational vision and strategy.

      Phase 1: Set the Mobile Context

      • Build applications your users need and desire – Design the right mobile application that enables your users to address their frustrations and productivity challenges.
      • Maximize return on your technology investments – Build your mobile applications with existing web APIs, infrastructure, and services as much as possible.
      • Prioritize mobile security, performance and integration requirements – Understand the unique security, performance, and integration influences has on your desired mobile user experience. Find the right balance of functional and non-functional requirements through business and IT collaboration.

      Phase 2: Define Your Mobile Approach

      • Start with a mobile web platform - Minimize disruptions to your existing delivery process and technical stack by building against common web standards. Select a hybrid platform or cross-platform if you need device hardware access or have complicated non-functional requirements.
      • Focus your mobile solution decision on vendor support and functional complexity – Verify that your solution is not only compatible with the architecture, data, and policies of existing business systems, but satisfies IT's concerns with access to restricted technology and data, and with IT's ability to manage and operate your applications.
      • Anticipate changes, defects & failures in your roadmap - Quickly shift your mobile roadmaps according to user feedback, delivery challenges, value, and stability.

      Mobile is how the business works today

      Mobile adoption continues to grow in part due to the need to be a mobile workforce, and the shift in customer behaviors. This reality pushed the industry to transform business processes and technologies to better support the mobile way of working.

      Mobile Builds Interests
      61%
      Mobile devices drove 61% of visits to U.S. websites
      Source: Perficient, 2021

      Mobile Maintains Engagement
      54%
      Mobile devices generated 54.4% of global website traffic in Q4 2021.
      Source: Statista, 2022

      Mobile Drives Productivity
      82%
      According to 82% of IT executives, smartphones are highly important to employee productivity
      Source: Samsung and Oxford Economics, 2022

      Mobile applications enable and drive your digital business strategy

      Organizations know the criticality of mobile applications in meeting key business and digital transformation goals, and they are making significant investments. Over half (58%) of organizations say their main strategy for driving application adoption is enabling mobile access to critical enterprise systems (Enterprise CIO, 2016). The strategic positioning and planning of mobile applications are key for success.

      Mobile Can Motivate, Support and Drive Progress in Key Activities Underpinning Digital Transformation Goals

      Goal: Enhance Customer Experience

      • A shift from paper to digital communications
      • Seamless, omni-channel client experiences across devices
      • Create Digital interactive documents with sections that customers can customize to better understand their communications

      Goal: Increase Workflow Throughput & Efficiency

      • Digitized processes and use of data to improve process efficiency
      • Modern IT platforms
      • Automation through robotic process automation (RPA) where possible
      • Use of AI and machine learning for intelligent automation

      Source: Broadridge, 2022

      To learn more, visit Info-Tech's Define Your Digital Business Strategy blueprint.

      Well developed mobile applications bring unique opportunities to drive more value

      Role

      Opportunities With Mobile Applications

      Expected Value

      Stationary Worker

      Design flowcharts and diagrams, while abandoning paper and desktop applications in favor of easy-to-use, drawing tablet applications.

      Multitask by checking the application to verify information given by a vendor during their presentation or pitch.

      • Reduce materials cost to complete administrative responsibilities.
      • Digitally and automatically store and archive frequently used documents.

      Roaming Worker
      (Engineer)

      Replace physical copies of service and repair manuals with digital copies, and access them with mobile applications.

      Scan or input product bar code to determine whether a replacement part is available or needs to be ordered.

      • Readily access and update corporate data anywhere at anytime.
      • Expand employee responsibilities with minimal skills impact.

      Roaming Worker
      (Nurse)

      Log patient information according to HIPAA standards and complete diagnostics live to propose medication for a patient.

      Receive messages from senior staff about patients and scheduling while on-call.

      • Quickly and accurately complete tasks and update patient data at site.
      • Be readily accessible to address urgent issues.

      Info-Tech Insight

      If you build it, they may not come. Design and build the applications your user wants and needs, and ensure users are properly onboarded and trained. Learn how your applications are leveraged, capture feedback from the user and system dashboards, and plan for enhancements, fixes, and modernizations.

      Workers expect IT to deliver against their high mobile expectations

      Workers want sophisticated mobile applications like what they see their peers and competitors use.

      Why is IT considering building their own applications?

      • Complex and Unique Workflows: Canned templates and shells are viewed as incompatible to the workflows required to complete worker responsibilities outside the office, with the same level of access to corporate data as on premise.
      • Supporting Bring Your Own Device (BYOD): Developing your own mobile applications around your security protocols and standards can help mitigate the risks with personal devices that are already in your workforce.
      • Long-Term Architecture Misalignment: Outsourcing mobile development risks the mobile application misaligned with your quality standards or incompatible with other enterprise and third-party systems.

      Continuously meeting aggressive user expectations will not be easy

      Value Quickly Wears Off
      39.9% of users uninstall an application because it is not in use.
      40%
      Source: n=2,000, CleverTap, 2021

      Low Tolerance to Waiting
      Keeping a user waiting for 3 seconds is enough to dissatisfy 43% of users.
      43%
      Source: AppSamurai, 2018

      Quick Fixes Are Paramount
      44% of defects are found by users
      44%
      Source: Perfecto Mobile, 2014

      Mobile emphasizes the importance of good security, performance, and integration

      Today's mobile workers are looking for new ways to get more work done quickly. They want access to enterprise solutions and data directly on their mobile devices, which can reside on multiple legacy systems and in the cloud and third-party infrastructure. This presents significant performance, integration, and security risks.

      Cloud Solutions: Can I use my existing APIs?. Solutions in Corporate Networks: Do my legacy systems have the capacity to support mobile?; How do I integrate solutions and data from multiple sources into a single view?; Third Party Solutions: Will I have a significant performance bottleneck?; Single View on Mobile Devices: How is corporate data stored on the device?; What new technology dependencies must I account for in my architecture and operational support capabilities?

      Accept change as the norm

      IT is challenged with keeping up with disruptive technologies, such as mobile, which are arriving and changing faster and faster.

      What is the issue? Mobile priorities, concepts, and technologies do not remain static. For example, current Google's Pixels benefit from at least three versions of Android updates and at least three years of monthly security patches after their release (NextPit, 2022). Keeping up to date with anything mobile is difficult if you do not have the right delivery and product management practices in place.

      What is the impact on IT? Those who fail to prepare for changing requirements and technologies will quickly run into maintainability, extensibility, and flexibility issues. Mobile applications will quickly become stale and misaligned with the maturity of other enterprise infrastructure and applications.

      Continuously look at the trends, vendor roadmaps, and your user's feedback to envision where your mobile applications should be. Learning from your past attempts gives you insights on the opportunities and impacts changes will have on your people, process, and technology.

      How do I address this issue? A well-defined mobile vision and roadmap ensures your initiatives are aligned with your holistic business and technology strategies, the right problem is being solved, and resources are available to deliver high priority changes.

      To learn more, visit Info-Tech's Deliver on Your Digital Product Vision blueprint.

      Address the difficulties in managing enterprise mobile technologies

      Adaptability During Development

      Teams must be ready to alter their mobile approach when new insights and issues arise during and after the delivery of your mobile application and its updates.

      High Cybersecurity Standards

      Cybersecurity should be a top priority given the high security exposure of mobiles and the sensitive data mobile applications need to operate. Role-based access, back-up systems, advanced scanning, and protection software and encryption should all be implemented.

      Integration with Other Systems

      Your application will likely be integrated with other systems to expand service offerings and optimize performance and user experience. Your enterprise integration strategy ensures all systems connect against a common pattern with compatible technologies.

      Finding the Right Mobile Developers

      Enterprise mobile delivery requires a broad skillset to build valuable applications against extensive non-functional requirements in complex and integration environments. The right resources are even harder to find when native applications are preferred over web-based ones.

      Source: Radoslaw Szeja, Netguru, 2022.

      Build and manage the right experience by treating mobile as digital products

      Digital products are continuously modernized to ensure they are fit-for-purpose, secured, insightful, accessible, and interoperable. A good experience involves more than just technology.

      First, deliver the experience end users want and expect by designing the application against digital application principles.

      Business Value

      Continuous modernization

      • Fit for purpose
      • User-centric
      • Adaptable
      • Accessible
      • Private and secured
      • Informative and insightful
      • Seamless application connection
      • Relationship and network building

      To learn more, visit Info-Tech's Modernize Your Applications blueprint.

      Then, deliver a long-lasting experience by supporting your applications with key governance and management capabilities.

      • Product Strategy and Roadmap
      • External Relationships
      • User Adoption and Organizational Change Management
      • Funding
      • Knowledge Management
      • Stakeholder Management
      • Product Governance
      • Maintenance & Enhancement
      • User Support
      • Managing and Governing Data
      • Requirements Analysis and Design
      • Research & Development

      To learn more, visit Info-Tech's Make the Case for Product Delivery blueprint.

      Choose Your Mobile Platform and Tools

      Maximize the value of your mobile investments by prioritizing technology decisions on user experience, business priorities, and system quality.

      WORKFLOW

      1. Capture Your User Personas and Journey workflow: Trigger: Step 1; Step 2; Step 3; Step 4; Outcome
      2. Select Your Platform Nine datapoints are arranged on a graph where the x axis s labeled: User Centric Needs; and the Y axis is labeled: Enterprise-centric needs. The datapoints are, in order from left to right, top to bottom: Hybrid; Cross- Platform; Native; Web; Hybrid or Cross- Platform; Cros-s Platform; Web; Web; Hybrid or Cross- Platform.
      3. Shortlist Your Solutions A quadrant analysis is depicted. the top data is labeled Complex Mobile Features; the right side is labeled Organization-Managed Stack; the bottom is labeled Simple Mobile Features; and the left side is labeled Vendor-Managed Stack. The quadrants are labeled the following, in order from left to right, top to bottom. Vendor- Hosted Mobile Platform; Custom Native Development Solutions; Commercial-Off-the-Shelf Solutions; Custom Web Development Solutions. In the middle of the graph are the following, in order from top to bottom: Cross-Platform Development Solutions; Hybrid Development Solutions

      Strategic Perspective
      Business and Product Strategies

      1. End-User Perspective

      End User Needs

      • Productivity
      • Innovation
      • Transformation

      Native User Experience

      • Anytime, Anywhere
      • Visually Pleasing & Fulfilling
      • Personalized & Insightful
      • Hands-Off & Automated
      • Integrated Ecosystem

      2. Platform Perspective

      Technical Requirements

      Security

      Performance

      Integration

      Mobile Platform

      3. Solution Perspective

      Vendor Support

      Services

      Stack Mgmt.

      Quality & Risk

      Mobile Delivery Solutions

      Make user experience (UX) the standard

      User experience (UX) focuses on a user's emotions, beliefs, and physical and psychological responses that occur before, during, or after interacting with a service or product.

      For a mobile application to be meaningful, the functions, aesthetics and content must be:

      • Usable
        • Users can intuitively navigate through your mobile application and complete their desired tasks.
      • Desirable
        • The application elements are used to evoke positive emotions and appreciation.
      • Accessible
        • Users can easily use your mobile application, including those with disabilities.
      • Valuable
        • Users find the content useful, and it fulfills a need.

      Enable a greater experience with UX-driven thinking

      Designing for a high-quality experience requires more than just focusing on the UI. It also requires the merging of multiple business, technical, and social disciplines in order to create an immersive, practical, and receptive application. The image on the right explains the disciplines involved in UX. This is critical for ensuring users have a strong desire to use the mobile application, it is adequately supported technically, and it supports business objectives.

      To learn more, visit Info-Tech's Implement and Mature Your User Experience Design Practice blueprint.

      A Venn diagram is depicted, demonstrating the inputs that lead to an interactive design, with interactive elements, usability, and accessibility. This work by Mark Roden is licensed under a Creative Commons Attribution 3.0 Unported License.

      Source: Marky Roden, Xomino, 2018

      Define the mobile experience your end users want

      • Anytime, Anywhere
        • The user can access, update and analyze data and corporate products and services whenever they want, in all networks, and on any device.
      • Hands-Off and Automated
        • The application can perform various workflows and tasks without the user's involvement and notify the user when specific triggers are hit.
      • Personalized and Insightful
        • Content presentation and subject are tailored for the user based on specific inputs from the user, device hardware, or predicted actions.
      • Integrated Ecosystem
        • The application supports a seamless experience across various third-party and enterprise applications and services the user needs.
      • Visually Pleasing and Fulfilling
        • The UI is intuitive and aesthetically gratifying, with little security and performance trade-offs to use the full breadth of its functions and services.

      Each mobile platform has its own take on the mobile native experience. The choice ultimately depends on whether the costs and effort are worth the anticipated value.

      Mobile value is dependent on the platform you choose

      What is a platform?

      "A platform is a set of software and a surrounding ecosystem of resources that helps you to grow your business. A platform enables growth through connection: its value comes not only from its own features, but from its ability to connect external tools, teams, data, and processes." (Source: Emilie Nøss Wangen, 2021) In the mobile context, applications in a platform execute and communicate through a loosely-coupled API architecture, whether the supporting system is managed and supported by your organization or by third-party providers.

      Web

      Mobile web applications are deployed and executed within the mobile web browser. They are often developed with a combination of web and scripting languages, such as HTML, CSS, and JavaScript. Web often takes two forms on mobile:

      • Progressive Web Applications (PWA)
      • Mobile Web Sites

      Hybrid

      Hybrid applications are developed with web technologies but are deployed as native applications. The code is wrapped using a framework so that it runs locally within a native container. It uses the device's browser runtime engine to support more sophisticated designs and features than to the web approach.

      Cross-Platform

      Cross-platform applications are developed within a distinct programming or scripting environment that uses its own scripting language (often like web languages) and APIs. The solution compiles the code into device-specific builds for native deployment.

      Native

      Native applications are developed and deployed to specific devices and OSs using platform-specific software development kits (SDKs) provided by the operating system vendors. The programming language and framework are dictated by the targeted device, such as Java for Android.

      Start mobile development on a mobile web platform

      Start with what you have: begin with a mobile web platform to minimize impacts to your existing delivery skill sets and technical stack while addressing business needs. Resort to a hybrid first. Then consider a cross-platform application if you require device access or need to meet specific non-functional requirements.

      Why choose a mobile web platform?

      Pros

      The latest versions of the most popular web languages (HTML5, CSS3, JavaScript) abstract away from the granular, physical components of the application, simplifying the development process. HTML5 offer some mobile features (e.g. geolocation, accelerometer) that can meet your desired experience without the need for native development skills. Native look-and-feel, high performance, and full device access are just a few tradeoffs of going with web languages.

      Cons

      Native mobile platforms depend on device-specific code which follows specific frameworks and leverages unique programming libraries, such as Objective C for iOS and Java for Android. Each language requires a high level of expertise in the coding structure and hardware of specific devices. This requires resources with specific skillsets and different tools to support development and testing.

      Other Notable Benefits with Web Languages

      • Modern browsers in most mobile devices can execute and render many mobile features developed in web languages, allowing for greater portability and sophistication of code across multiple devices. However, this flexibility comes at the cost of performance since the browser's runtime engine will not perform as well as a native engine.
      • Web languages are well known by developers, minimizing skills and resourcing impacts. Consequently, changes can be quickly accommodated and updated uniformly across all end users.

      Select your mobile platform

      Drive your mobile platform selection against user-centric needs (e.g. device access, aesthetics) and enterprise-centric needs (e.g. security, system performance).

      When does a platform makes sense to use?

      Web

      • Desire to maximize current web technologies investments (people, process, and technologies).
      • Use cases do not require significant computational resources on the device or are tightly constrained by non-functional requirements.
      • Limited budget to acquire mobile development resources.
      • Access to device hardware is not a high priority.

      Hybrid / Cross-Platform

      • The need to quickly spin up native-like applications for multiple platforms and devices.
      • Desire to leverage existing web development skills, but also a need for device access and meeting specific non-functional requirements.
      • Vendor support is needed for the entire mobile delivery process.

      Native

      • Developers are experts in the target programming language and with the device's hardware.
      • Strong need for high performance, security, and device-specific access and customizations.
      • Application use cases require significant computing resources.

      Nine datapoints are arranged on a graph where the x axis s labeled: User Centric Needs; and the Y axis is labeled: Enterprise-centric needs. The datapoints are, in order from left to right, top to bottom: Hybrid; Cross- Platform; Native; Web; Hybrid or Cross- Platform; Cros-s Platform; Web; Web; Hybrid or Cross- Platform.

      Understand the common attributes of a mobile delivery solution

      • Source Code Management – Built-in or having the ability to integrate with code management solutions for branching, merging, and versioning. Debugging and coding assistance capabilities may be available.
      • Single Code Base – Capable of programming in a standard coding and scripting language for deployment into several platforms and devices. This code base is aligned to a common industry framework (e.g. AngularJS, Java) or a vendor-defined one.
      • Out-of-the-Box Connectors & Plug-ins – Pre-built APIs enhance the solution's capabilities with third-party tools and systems to deliver and manage high quality and valuable mobile applications.
      • Emulators – Ability to virtualize an application's execution on a target platform and device.
      • Support for Native Features – Supports plug-ins and APIs for access to device-specific features.

      What are mobile delivery solutions?

      A mobile delivery solution provides the tools, resources, and support to enable or build your mobile application. It can provide pre-built applications, vendor supported components to allow some configurations, or resources for full stack customizations. Solutions can be barebone software development kits (SDKs), or comprehensive suites offering features to support the entire software delivery lifecycle, such as:

      • Mobile application management
      • Testing and publishing to app stores
      • Content management
      • Cloud hosting
      • Application performance management

      Info-Tech Insight

      Mobile enablement and development capabilities are already embedded in many common productivity tools and enterprise applications, such as Microsoft PowerApps and ERP modules. They can serve as a starting point in the initial rollout of new management and governance practices without the need to acquire new tools.

      Select your mobile delivery solutions

      1. Set the scope of your framework.
      • The initial context of this framework is based on the mobile functions needed to support your desired mobile experience and on the current state of your enterprise and 3rd party systems.
    • Define the decision factors for your solution selection.
      • Review the decision factors that will influence the selection of your mobile delivery solution for each mobile opportunity:
      • Stack Management – Who will be hosting and supporting your mobile application stack?
      • Workflows Complexity & Native Experience – How complex is your desired mobile experience and how will native device features be leveraged?
    • Select your solution type.
      • Mobile delivery solutions are broadly defined in the following groups:
      • Commercial-Off-The-Shelf (COTS) – Pre-built mobile applications requiring little to no configurations or implementation effort.
      • Vendor Hosted Mobile Platform – Back-end and mid-tier infrastructure and operational support are managed by a vendor.
      • Cross-Platform Development – Frameworks that transform a single code base into platform-specific builds.
      • Hybrid Development – Tools that wrap a single code base into a locally deployable build.
      • Custom Web Development – Environment enabling full stack development for mobile web applications.
      • Custom Native Development – Environment enabling full stack development for mobile native applications.
    • A quadrant analysis is depicted. the top data is labeled Complex Mobile Features; the right side is labeled Organization-Managed Stack; the bottom is labeled Simple Mobile Features; and the left side is labeled Vendor-Managed Stack. The quadrants are labeled the following, in order from left to right, top to bottom. Vendor- Hosted Mobile Platform; Custom Native Development Solutions; Commercial-Off-the-Shelf Solutions; Custom Web Development Solutions. In the middle of the graph are the following, in order from top to bottom: Cross-Platform Development Solutions; Hybrid Development Solutions

      Optimize your software delivery process

      Mobile brings new delivery and management challenges that are often difficult for organizations that are tied to legacy systems, hindered by rigid and slow delivery lifecycles, and are unable to adopt leading-edge technologies. Many of these challenges stem from the fact that mobile is a significant shift from desktop development:

      • Mobile devices and operating systems are heavily fragmented, especially in the Android space.
      • Test coverage is significantly expanded to include physical environments and multiple network connections.
      • Mobile devices do not have the same performance capabilities and memory storage as their desktop counterparts.
      • The user interface must be strategically designed to accommodate the limited screen size.
      • Mobile applications are highly susceptible to security breaches.
      • Mobile users often expect quick turnaround time on fixes and enhancements due to continuously changing technology, business priorities, and user needs.

      To learn more, visit Info-Tech's Modernize Your SDLC blueprint.

      How should the process change?

      • Cross-functional collaboration – Bringing business and IT together at the most opportune times to clarify user needs and business priorities, and set realistic expectations given technology and capacity constraints. The appropriate tactics and techniques are used to improve decision making and delivery effectiveness according to the type of work.
      • Iterative delivery – Frequent delivery of progressive changes minimizes the risk of low-quality features by containing and simplifying scope, and enables responsive turnarounds of fixes, enhancements, and priority changes.
      • Feedback loops –Mobile application owners constantly review, update and refine their backlog of mobile features and changes to reflect user feedback and system performance metrics. Delivery teams proactively prepare the application for future scaling based on lessons and feedback learned from earlier releases.

      Achieve mobile success with MVPs

      By delivering mobile capabilities in small iterations, teams recognize value sooner and reduce accumulated risk. Both benefits are realized as the iteration enters validation testing and release.

      This image depicts a graph of the learn-build-measure cycle over time, adapted from Managing the Development of Large Software Systems, Dr. Winston W. Royce, 1970

      An MVP focuses on a small set of functions, involves minimal possible effort to deliver a working and valuable solution, and is designed to satisfy a specific user group. Its purpose is to:

      • Maximize learning.
      • Evaluate the value and acceptance of mobile applications.
      • Inform the building of a mobile delivery practice.

      The build-measure-learn loop suggests mobile delivery teams should perpetually take an idea and develop, test, and validate it with the mobile development solution, then expand on the MVP using the lessons learned and evolving ideas. In this sense the MVP is just the first iteration in the loop.

      Gauge the value with the right metrics

      Metrics are a powerful way to drive behavior change in your organization. But metrics are highly prone to creating unexpected outcomes so they must be used with great care. Use metrics judiciously to avoid gaming or ambivalent behavior, productivity loss, and unintended consequences.

      To learn more, visit Info-Tech's Select and Use SDLC Metrics Effectively blueprint.

      What should I measure?

      1. Mobile Application Engagement, Retention and User Satisfaction
        1. The activeness of users on the applications, the number of returning users, and the happiness of the users.
        2. Example: Number of tasks completed, number of active and returning users, session length and intervals, user satisfaction
      2. Value Driven from Mobile Applications
        1. The business value that the user directly or indirectly receives with the mobile application.
        2. Example: Mobile application revenue, business operational costs, worker productivity, business reputation and image
      3. Delivery Throughput and Quality
        1. The health and quality of your mobile applications throughout their lifespan and the speed to deliver working applications that meet stakeholder expectations.
        2. Example: Frequency of release, lead time, request turnaround, escaped defects, test coverage.

      Use Info-Tech's diagnostic to evaluate the reception of your mobile applications

      Info-Tech's Application Portfolio Assessment (APA) Diagnostic is a canned end-user satisfaction survey used to evaluate your application portfolio health to support data-driven decisions.

      This image contains a screenshot from Info-Tech's Application Portfolio Assessment (APA) Diagnostic

      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.

      Grow your mobile delivery practice

      Level 1: Mobile Delivery Foundations

      You understand the opportunities and impacts mobile has on your business operations and its disruptive nature on your enterprise systems. Your software delivery lifecycle was optimized to incorporate the specific practices and requirements needed for mobile. A mobile platform was selected based on stakeholder needs that are weighed against current skillsets, high priority non-functional requirements, the available capacity and scalability of your stack, and alignment to your current delivery process.

      Level 2: Scaled Mobile Delivery

      New features and mobile use cases are regularly emerging in the industry. Ensuring your mobile platform and delivery process can easily scale to incorporate constantly changing mobile features and technologies is key. This can help minimize the impact these changes will have on your mobile stack and the resulting experience.

      Achieving this state requires three competencies: mobile security, performance optimization, and integration practices.

      Level 3: Leading-Edge Mobile Delivery

      Many of today's mobile trends involve, in one form or another, hardware components on the mobile device (e.g., NFC receivers, GPS, cameras). You understand the scope of native features available on your end user's mobile device and the required steps and capabilities to enable and leverage them.

      Hit a home run with your stakeholders

      Use a data-driven approach to select the right tooling vendor for your needs – fast.

      Awareness Education & Discovery Evaluation Selection

      Negotiation & Configuration

      1.1 Proactively Lead Technology Optimization & Prioritization 2.1 Understand Marketplace Capabilities & Trends 3.1 Gather & Prioritize Requirements & Establish Key Success Metrics 4.1 Create a Weighted Selection Decision Model 5.1 Initiate Price Negotiation with Top Two Venders
      1.2 Scope & Define the Selection Process for Each Selection Request Action 2.2 Discover Alternate Solutions & Conduct Market Education 3.2 Conduct a Data Driven Comparison of Vendor Features & Capabilities 4.2 Conduct Investigative Interviews Focused on Mission Critical Priorities with Top 2-4 Vendors 5.2 Negotiate Contract Terms & Product Configuration

      1.3 Conduct an Accelerated Business Needs Assessment

      2.3 Evaluate Enterprise Architecture & Application Portfolio Narrow the Field to Four Top Contenders 4.3 Validate Key Issues with Deep Technical Assessments, Trial Configuration & Reference Checks 5.3 Finalize Budget Approval & Project
      1.4 Align Stakeholder Calendars to Reduce Elapsed Time & Asynchronous Evaluation 2.4 Validate the Business Case 5.4 Invest in Training & Onboarding Assistance

      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. Info-Tech's Rapid Application Selection Framework approach is best for commodity and mid-tier enterprise applications; selecting complex applications is better handled by the methodology in Info-Tech's Implement a Proactive and Consistent Vendor Selection Process.

      Pitch your mobile delivery approach with Info-Tech's template

      Communicate the justification of your approach to mobile applications with Info-Tech's Mobile Application Delivery Communication Template:

      • Level set your mobile application goals and objectives by weighing end user expectations with technical requirements.
      • Define the high priority opportunities for mobile applications.
      • Educate decision makers of the limitations and challenges of delivering specific mobile experiences with the various mobile platform options.
      • Describe your framework to select the right mobile platform and delivery tools.
      • Lay out your mobile delivery roadmap and initiatives.

      INFO-TECH DELIVERABLE

      This is a screenshot from Info-Tech's Mobile Application Delivery Communication Template

      Info-Tech's methodology for mobile platform and delivery solution selection

      1. Set the Mobile Context

      2. Define Your Mobile Approach

      Phase Steps

      Step 1.1 Build Your Mobile Backlog

      Step 1.2 Identify Your Technical Needs

      Step 1.3 Define Your Non-Functional Requirements

      Step 2.1 Choose Your Platform Approach

      Step 2.2 Shortlist Your Mobile Delivery Solution

      Step 2.3 Create a Roadmap for Mobile Delivery

      Phase Outcomes

      • User personas
      • Mobile objectives and metrics
      • Mobile opportunity backlog
      • List of mobile features to enable the desired mobile experience
      • System current assessment
      • Mobile application quality definition
      • Readiness for mobile delivery
      • Desired mobile platform approach
      • Shortlisted mobile delivery solutions
      • Desired list of vendor features and services
      • MVP design
      • Mobile delivery roadmap

      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

      Call #1: Understand the case and motivators for mobile applications.

      Call #2: Discuss the end user and desired mobile experience.

      Call #5: Discuss the desired mobile platform.

      Call #8: Discuss your mobile MVP.

      Call #3: Review technical complexities and non-functional requirements.

      Call #6: Shortlist mobile delivery solutions and desired features.

      Call #9: Review your mobile delivery roadmap.

      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 9 calls over the course of 2 to 3 months.

      Workshop Overview

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

      Module 1 Module 2 Module 3 Module 4 Post-Workshop
      Activities Set the Mobile Context Identify Your Technical Needs Choose Your Platform & Delivery Solution Create Your Roadmap Next Steps andWrap-Up (offsite)

      1.1 Generate user personas with empathy maps

      1.2 Build your mobile application canvas

      1.3 Build your mobile backlog

      2.1 Discuss your mobile needs

      2.2 Conduct a technical assessment

      2.3 Define mobile application quality

      2.4 Verify your decision to deliver mobile applications

      3.1 Select your platform approach

      3.2 Shortlist your mobile delivery solution

      3.3 Build your feature and service lists

      4.1 Define your MVP release

      4.2 Build your 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

      • User personas
      • Mobile objectives and metrics
      • Mobile opportunity backlog
      • List of mobile features to enable the desired mobile experience
      • System current assessment
      • Mobile application quality definition
      • Verification to proceed with mobile delivery
      • Desired mobile platform approach
      • Shortlisted mobile delivery solutions
      • Desired list of vendor features and services
      • MVP design
      • Mobile delivery roadmap
      • Completed workshop output deliverable
      • Next steps

      Phase 1

      Set the Mobile Context

      Choose Your Mobile Platform and Tools

      This phase will walk you through the following steps:

      • Step 1.1 – Build Your Mobile Backlog
      • Step 1.2 – Identify Your Technical Needs
      • Step 1.3 – Define Your Non-Functional Requirements

      This phase involves the following participants:

      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      Step 1.1

      Build Your Mobile Backlog

      Activities

      1.1.1 Generate user personas with empathy maps

      1.1.2 Build your mobile application canvas

      1.1.3 Build your mobile backlog

      Set the Mobile Context

      This step involves the following participants:

      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      Outcomes of this step

      • User personas
      • Mobile objectives and metrics
      • Mobile opportunity backlog

      Users expect your organization to support their mobile way of working

      Today, users expect sophisticated and personalized features, immersive interactions, and cross-platform capabilities from their mobile applications and be able to access information and services anytime, anywhere and on any device. These demands are pushing organizations to become more user-driven, placing greater importance on user experience (UX) with enterprise-grade technologies.

      How has technologies evolved to easily enable mobile capabilities?

      • Desktop-Like Features
        • Native-like features, such as geolocation and local caching, are supported through web language or third-party plugins and extensions.
      • Extendable & Scalable
        • Plug-and-play architecture is designed to allow software delivery teams to explore new use cases and mobile capabilities with out-of-the-box connectors and/or customizable REST APIs.
      • Low Barrier to Entry
        • Low- and no-code development tools, full-stack solutions, and plug-and-play architectures allow non-technical users to easily build and implement applications without direct IT involvement.
      • Templates & Shells
        • Vendors provide UI templates and application shells that contain pre-built native features and multiple aesthetic layouts in a publishing-friendly and configurable way.
      • Personalized Content
        • Content can be uniquely tailored to a user's preference or be automatically generated based on the user's profile or activity history.
      • Hands-Off Operations
        • Many mobile solutions operate in a as-a-service model where the underlying and integrated technologies are managed by the vendor and abstracted away.

      Make user experience (UX) the standard

      User experience (UX) focuses on a user's emotions, beliefs, and physical and psychological responses that occur before, during, or after interacting with a service or product.

      For a mobile application to be a meaningful experience, the functions, aesthetics and content must be:

      • Usable
        • Users can intuitively navigate through your mobile application and complete their desired tasks.
      • Desirable
        • The application elements are used to evoke positive emotions and appreciation.
      • Accessible
        • Users can easily use your mobile application, including those with disabilities.
      • Valuable
        • Users find the content useful, and it fulfills a need.

      Enable a greater experience with UX-driven thinking

      Designing for a high-quality experience requires more than just focusing on the UI. It also requires the merging of multiple business, technical, and social disciplines in order to create an immersive, practical, and receptive application. The image on the right explains the disciplines involved in UX. This is critical for ensuring users have a strong desire to use the mobile application, it is adequately supported technically, and it supports business objectives.

      To learn more, visit Info-Tech's Implement and Mature Your User Experience Design Practice blueprint.

      A Venn diagram is depicted, demonstrating the inputs that lead to an interactive design, with interactive elements, usability, and accessibility. This work by Mark Roden is licensed under a Creative Commons Attribution 3.0 Unported License.

      Source: Marky Roden, Xomino, 2018

      UX-driven mobile apps bring together a compelling UI with valuable functionality

      Info-Tech Insight

      Organizations often over-rotate on the UI. Receptive and satisfying applications require more than just pretty pictures, bold colors, and flashy animations. UX-driven mobile applications require the seamless merging of enticing design elements and valuable functions that are specifically tailored to the behaviors of the users. Take a deep look at how each design element and function is used and perceived by the user, and how your application can sufficiently support user needs.

      UI-Function Balance to Achieve Highly Satisfying Mobile Applications

      An application's UI and function both contribute to UX, but they do so in different ways.

      • The UI generates the visual, audio, and vocal cues to draw the attention of users to key areas of the application while stimulating the user's emotions.
      • Functions give users the means to satisfy their needs effortlessly.

      Finding the right balance of UI and function is dependent on the organization's understanding of user emotions, needs, and tendencies. However, these factors are often left out of an application's design. Having the right UX competencies is key in assuring user behaviors are appropriately accommodated early in the delivery process.

      To learn more, visit Info-Tech's Modernize Your Corporate Website to Drive Business Value blueprint.

      Focus your efforts on all items that drive high user experience and satisfaction

      UX-driven mobile applications involve all interaction points and system components working together to create an immersive experience while being actively supported by delivery and operations teams. Many organizations commonly focus on visual and content design to improve the experience, but this is only a small fraction of the total UX design. Look beyond the surface to effectively enhance your application's overall UX.

      Typical Focus of Mobile UX

      Aesthetics
      What Are the Colors & Fonts?

      Relevance & Modern
      Will Users Receive Up to Date Content and Trending Features?

      UI Design
      Where Are the Interaction Points?

      Content Layout
      How Is Content Organized?

      Critical Areas of Mobile UX That Are Often Ignored

      Web Infrastructure
      How Will Your Application Be Operationally Supported?

      Human Behavior
      What Do the Users Feel About Your Application?

      Coding Language
      What Is the Best Language to Use?

      Cross-Platform Compatibility
      How Does It Work in a Browser Versus Each Mobile Platform?

      Application Quality
      How are Functional and Non-Functional Needs Balanced?

      Adoption & Retention
      How Do I Promote Adoption and Maintain User Engagement?

      Application Support
      How Will My Requests and Issues Be Handled?

      Use personas to envision who will be using your mobile application

      What Are Personas?

      Personas are detailed descriptions of the targeted audience of your mobile application. It represents a type of user in a particular scenario. 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 critical features and functionalities.
      • Describe real people with backgrounds, goals, and values.

      Why Are Personas Important to UX?

      They are important because they help:

      • Focus the development of mobile application features on the immediate needs of the intended audience.
      • Detail the level of customization needed to ensure content is valuable to and resonates with the user.
      • Describe how users may behave when certain audio and visual stimulus are triggered from the mobile application.
      • Outline the special design considerations required to meet user accessibility needs.

      Key Elements of a Persona:

      • Professional and Technical Skills and Experiences (e.g., knowledge of mobile applications, area of expertise)
      • Persona Group (e.g., executives)
      • Technological Environment of User (e.g., devices, browsers, network connection)
      • Demographics (e.g., nationality, age, language spoken)
      • Typical Behaviors and Tendencies (e.g., goes to different website when cannot find information in 20 seconds)
      • Purpose of Using the Mobile Application (e.g., search for information, submit registration form)

      Create empathy maps to gain a deeper understanding of stakeholder personas

      Empathy mapping draws out the characteristics, motivations, and mannerisms of a potential end user.

      This image contains an image of an empathy map from XPLANE, 2017. it includes the following list: 1. Who are we empathizing with; 2. What do they need to DO; 3. What do they SEE; 4. What do they SAY?; 5. What do they DO; 6. What do they HEAR; 7. What do they THINK and FEEL.

      Source: XPLANE, 2017

      Empathy mapping focuses on identifying the problems, ambitions, and frustrations they are looking to resolve and describes their motivations for wanting to resolve them. This analysis helps your teams:

      • Better understand the reason behind the struggles, frustrations and motivators through a user's perspective.
      • Verify the accuracy of assertions made about the user.
      • Pinpoint the specific problem the mobile application will be designed to solve and the constraints to its successful adoption and on-going use.
      • Read more about empathy mapping and download the empathy map PDF template here.

      To learn more, visit Info-Tech's Use Experience Design to Drive Empathy with the Business blueprint.

      1.1.1 Generate user personas with empathy maps

      1-3 hours

      1. Download the Empathy Map Canvas and draw the map on a whiteboard or project it on the screen.
      2. Choose an end user to be the focus of your empathy map. Using sticky notes, fill out the sections of the empathy map in the following order:
        1. Start by filling out the goals section. State who the subject of the empathy map will be and what activity or task you would like them to do.
          1. Focus on activities and tasks that may benefit from mobile.
        2. Next, complete the outer sections in clockwise order (see, say, do, hear). The purpose of this is to think in terms of what the subject of your empathy map is observing, sensing, and experiencing.
          1. Indicate the mobile devices and OS users will likely use and the environments they will likely be in (e.g., places with poor connections)
          2. Discuss accessibility needs and how user prefer to consume content.
        3. Last, complete the inner circle of the empathy map (pains and gains). Since you spent the last step of the exercise thinking about the external influences on your stakeholder, you can think about how those stimuli affect their emotions.
      3. Document your end user persona into Info-Tech's Mobile Application Delivery Communication Template.

      Input

      Output
      • List of potential mobile application users
      • User personas
      Materials Participants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      1.1.1 cont'd

      This image contains an image of an empathy map from XPLANE, 2017. it includes the following list: 1. Who are we empathizing with; 2. What do they need to DO; 3. What do they SEE; 4. What do they SAY?; 5. What do they DO; 6. What do they HEAR; 7. What do they THINK and FEEL.

      Download the Empathy Map Canvas

      Many business priorities are driving mobile

      Mobile Applications

      • Product Roadmap
        • Upcoming enterprise technology releases and updates offer mobile capabilities to expand its access to a broader userbase.
      • Cost Optimization
        • Maximizing business value in processes and technologies through disciplined and strategic cost and spending reduction practices with mobile applications.
      • Competitive Differentiation
        • Developing and optimizing your organization's distinct products and services quickly with mobile applications.
      • Digital Transformation
        • Transitioning processes, data and systems to a digital environment to broaden access to enterprise data and services anywhere at anytime.
      • Operational Efficiency
        • Improving software delivery and business process throughput by increasing worker productivity with mobile applications.
      • Other Business Priorities
        • New corporate products and services, business model changes, application rationalization and other priorities may require modernization, innovation and a mobile way of working.

      Focus on the mobile business and end user problem, not the solution

      People are naturally solution-focused. The onus isn't on them to express their needs in the form of a problem statement!

      When refining your mobile problem statement, attempt to answer the following four questions:

      • Who is impacted?
      • What is the (user or organizational) challenge that needs to be addressed?
      • Where does it happen?
      • Why does it matter?

      There are many ways of writing problem statements, a clear approach follows the format:

      • "Our (who) has the problem that (what) when (where). Our solution should (why)."
      • Example: "Our system analysts has the problem that new tickets take too long to update when working on user requests. Our approach should enable the analyst to focus on working with customers and not on administration."

      Adapted from: "Design Problem Statements – What and How to Frame Them"

      How to write a vision statement

      It's ok to dream a little!

      When thinking about a vision statement, think about:

      • Who is it for?
      • What does the customer need?
      • What can we do for them?
      • And why is this special?

      There are different statement templates available to help form your vision statements. Some include:

      1. For [our target customer], who [customer's need], the [product] is a [product category or description] that [unique benefits and selling points]. Unlike [competitors or current methods], our product [main differentiators]. (Crossing the Chasm)
      2. "We believe (in) a [noun: world, time, state, etc.] where [persona] can [verb: do, make, offer, etc.], for/by/with [benefit/goal].
      3. To [verb: empower, unlock, enable, create, etc.] [persona] to [benefit, goal, future state].
      4. Our vision is to [verb: build, design, provide], the [goal, future state], to [verb: help, enable, make it easier to...] [persona]."

      (Numbers 2-4 from: How to define a product vision)

      Info-Tech Best Practice

      A vision shouldn't be so far out that it doesn't feel real and so short term that it gets bogged down in minutiae and implementation details. Finding that right balance will take some trial and error and will be different depending on your organization.

      Ensure mobile supports ongoing value delivery and stakeholder expectations

      Success hinges on your team's ability to deliver business value. Well-developed mobile applications instill stakeholder confidence in ongoing business value delivery and stakeholder buy-in, provided proper expectations are set and met.

      Business value defines the success criteria of an organization, and it is interpreted from four perspectives:

      • Profit Generation – The revenue generated from a business capability with mobile applications.
      • Cost Reduction – The cost reduction when performing business capabilities with mobile applications.
      • Service Enablement – The productivity and efficiency gains of internal business operations with mobile applications.
      • Customer and Market Reach – Metrics measuring the improved reach and insights of the business in existing or new markets.

      See our Build a Value Measurement Framework blueprint for more information about business value definition.

      This image contains a quadrant analysis with the following labels: Left - Improved Capabilities; Top - Outward; Right - Financial Benefit; Bottom - Inward. the quadrants are labeled the following, in order from left to right, top to bottom. Customer and Market Reach; Profit Generation; Service Enhancement; Cost Reduction

      Set realistic mobile goals

      Mobile applications enables the exploration of new and different ways to improve worker productivity and deliver business value. However, the realities of mobile applications may limit your ability to meet some of your objectives:

      • On the day of installation, the average retention rate for public-facing applications was 25.3%. By day 30, the retention rate drops to 5.7%. (Source: Statista, 2020)
      • 63% of 3,335 most popular Android mobile applications on the Google Play Store contained open-source components with known security vulnerabilities and other pervasive security concerns including exposing sensitive data (Source: Synopsys, 2021)
      • 62% of users would delete the application because of performance issues, such as crashes, freezes and other errors (Source: Intersog, 2021).

      These realities are not guaranteed to occur or impede your ability to deliver valuable mobile applications, but they can lead to unachievable expectations. Ensure your stakeholders are not oversold on advertised benefits and hold you accountable for unrealistic objectives. Recognize that the organization must also change how it works and operates to see the full benefit and adoption of mobile applications and overcome the known and unknown challenges and hurdles that often come with mobile delivery.

      Benchmarks present enticing opportunities, but should be used to set reasonable expectations

      66%
      Improve Market Reach
      66% of the global population uses a mobile device
      Source: DataReportal, 2021

      20%
      Connected Workers are More Productive
      Nearly 20 percent of mobile professionals estimate they miss more than three hours of working time a week not being able to get connected to the internet
      Source: iPass, 2017

      80%
      Increase Brand Recognition
      80% of smartphone users are more likely to purchase from companies whose mobile sites of apps help them easily find answers to their questions
      Source: Google, 2018

      Gauge the value with the right metrics

      Metrics are a powerful way to drive behavior change in your organization. But metrics are highly prone to creating unexpected outcomes so they must be used with great care. Use metrics judiciously to avoid gaming or ambivalent behavior, productivity loss, and unintended consequences.

      To learn more, visit Info-Tech's Select and Use SDLC Metrics Effectively blueprint.

      What should I measure?

      1. Mobile Application Engagement, Retention and User Satisfaction
        • The activeness of users on the applications, the number of returning users, and the happiness of the users.
        • Example: Number of tasks completed, number of active and returning users, session length and intervals, user satisfaction
      2. Value Driven from Mobile Applications
        • The business value that the user directly or indirectly receives with the mobile application.
        • Example: Mobile application revenue, business operational costs, worker productivity, business reputation and image
      3. Delivery Throughput and Quality
        • The health and quality of your mobile applications throughout their lifespan and the speed to deliver working applications that meet stakeholder expectations.
        • Example: Frequency of release, lead time, request turnaround, escaped defects, test coverage.

      Use Info-Tech's diagnostic to evaluate the reception of your mobile applications

      Info-Tech's Application Portfolio Assessment (APA) Diagnostic is a canned end user satisfaction survey used to evaluate your application portfolio health to support data-driven decisions.

      This image contains a screenshot from Info-Tech's Application Portfolio Assessment (APA) Diagnostic

      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 a canvas to define key elements of your mobile initiative

      Mobile Application Initiative Name

      Owner:
      Parent Initiative:
      Updated:

      NAME
      LINK
      October 05, 2022

      Problem Statement

      Vision

      The problem or need mobile applications are addressing

      Vision, unique value proposition, elevator pitch, or positioning statement

      Business Goals & Metrics

      Capabilities, Processes & Application Systems

      List of business objectives or goals for the mobile application initiative.

      List of business capabilities, processes and application systems related to this initiative.

      Personas/Customers/Users

      Stakeholders

      List of groups who consume the mobile application

      List of key resources, stakeholders, and teams needed to support the process, systems and services

      To learn more, visit Info-Tech's Deliver on Your Digital Product Vision blueprint.

      1.1.2 Build your mobile application canvas

      1-3 hours

      1. Complete the following fields to build your mobile application canvas:
        • Mobile application initiative name
        • Mobile application owner
        • Parent initiative name
        • Problem that mobile applications are intending to solve and your vision. See the outcome from the previous exercise.
        • Mobile application business goals and metrics.
        • Capabilities, processes and application systems involved
        • Primary customers/users (For additional help with your product personas, download and complete to Deliver on Your Digital Product Vision.)
      2. Stakeholders
      3. Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Download the Mobile Application Delivery Communication Template

      Input

      Output
      • User personas
      • Business strategy
      • Problem and vision statements
      • Mobile objectives and metrics
      • Mobile application canvas
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      1.1.2 cont'd

      Mobile Application Initiative Name

      Owner:
      Parent Initiative:
      Updated:

      NAME
      LINK
      October 05, 2022

      Problem Statement

      Vision

      [Problem Statement]

      [Vision]

      Business Goals & Metrics

      Capabilities, Processes & Application Systems

      [Business Goal 1, Metric]
      [Business Goal 2, Metric]
      [Business Goal 3, Metric]

      [Business Capability]
      [Business Process]
      [Application System]

      Personas/Customers/Users

      Stakeholders

      [User 1]
      [User 2]
      [User 3]

      [Stakeholder 1]
      [Stakeholder 2]
      [Stakeholder 3]

      Create your mobile backlog

      Your backlog gives you a holistic understanding of the demand for mobile applications across your organization.

      Opportunities
      Trends
      MVP

      External Sources

      Internal Sources

      • Market Trends Analysis
      • Competitive Analysis
      • Regulations & Industry Standards
      • Customer & Reputation Analysis
      • Application Rationalization
      • Capability & Value Stream Analysis
      • Business Requests & Incidents
      • Discovery & Mining Capabilities

      A mobile application minimum viable product (MVP) focuses on a small set of functions, involves minimal possible effort to deliver a working and valuable solution, and is designed to satisfy a specific user group. Its purpose is to maximize learning, evaluate value and acceptance, and inform the development of a full-fledged mobile delivery practice.

      Find your mobile opportunities

      Modern mobile technologies enable users to access, analyze and change data anywhere with native device features, which opens the door to enhanced processes and new value sources.

      Examples of Mobile Opportunities:

      • Mobile Payment
        • Cost alternative to credit card transaction fees.
        • Loyalty systems are updated upon payment without need of a physical card.
        • Quicker completion of transactions.
      • Inventory Management
        • Update inventory database when shipments arrive or deliveries are made.
        • Inform retailers and consumers of current stock on website.
        • Alert staff of expired or outdated products.
      • Quick and Small Data Transfer
        • Embed tags into posters to transfer URIs, which sends users to sites containing product or location information.
        • Replace entry tags, fobs, or smart cards at doors.
        • Exchange contact details.
      • Location Sensitive Information
        • Proactively send promotions and other information (e.g. coupons, event details) to users within a defined area.
        • Inform employees of nearby prospective clients.
      • Supply Chain Management
        • Track the movement and location of goods and delivery trucks.
        • Direct drivers to the most optimal route.
        • Location-sensitive billing apps such as train and bus ticket purchases.
      • Education and Learning
        • Educate users about real-world objects and places with augmented books and by pushing relevant learning materials.
        • Visualize theories and other text with dynamic 3D objects.
      • Augmented Reality (AR)
        • Provide information about the user's surroundings and the objects in the environment through the mobile device.
        • Interactive and immersive experiences with the inclusion of virtual reality.
      • Architecture and Planning
        • Visualize historic buildings or the layout of structural projects and development plans.
        • Develop a digital tour with location-based audio initiated with location-based services or a camera.
      • Navigation
        • Provide directions to users to navigate and provide contextual travelling instructions.
        • Push traffic notifications and route changes to travelling users.
      • Tracking User Movement
        • Predict the future location of users based on historic information and traffic modelling.
        • Proactively push information to users before they reach their destination.

      1.1.3 Build your mobile backlog

      1-3 hours

      1. As a group, discuss the use and value mobile already has within your organization for each persona.
        1. What are some of the apps being used?
        2. What enterprise systems and applications are already exposed to the web and accessible by mobile devices?
        3. How critical is mobile to business operations, marketing campaigns, etc.?
      2. Discuss how mobile can bring additional business value to other areas of your organization for each persona.
        1. Can mobile enhance your customer reach? Do your customers care that your services are offered through mobile?
        2. Are employees asking for better access to enterprise systems in order to improve their productivity?
      3. Write your mobile opportunities in the following form: As a [end user persona], I want to [process or capability to enable with mobile applications], so that [organizational benefit]. Prioritize each opportunity against feasibility, desirability, and viability.
      4. Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Input

      Output
      • Problem and vision statements
      • Mobile objectives and metrics
      • Mobile application canvas
      • Mobile opportunities backlog
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      Manage your mobile backlog

      Your backlog stores and organizes your mobile opportunities at various stages of readiness. It must be continuously refined to address new requests, maintenance and changing priorities.

      3 – IDEAS
      Composed of raw, vague, and potentially large ideas that have yet to go through any formal valuation.

      2 – QUALIFIED
      Researched and qualified opportunities awaiting refinement.

      1 READY
      Discrete, refined opportunities that are ready to be placed in your team's delivery plans.

      Adapted from Essential Scrum

      A well-formed backlog can be thought of as a DEEP backlog

      • Detailed Appropriately: opportunities are broken down and refined as necessary
      • Emergent: The backlog grows and evolves over time as opportunities are added and removed.
      • Estimated: The effort an opportunity requires is estimated at each tier.
      • Prioritized: The opportunity's value and priority are determined at each tier.

      (Source Perforce, 2018)

      See our Deliver on Your Digital Product Vision for more information on backlog practices.

      Step 1.2

      Identify Your Technical Needs

      Activities

      1.2.1 Discuss your mobile needs

      1.2.2 Conduct a technical assessment

      Set the Mobile Context

      This step involves the following participants:

      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      Outcomes of this step

      • List of mobile features to enable the desired mobile experience
      • System current assessment

      Describe your desired mobile experiences with journey maps

      A journey map tells the story of the user's experience with an existing or prospective product or service, starting with a trigger, through the process of engagement, to create an outcome. Journey maps can focus on a particular part of the user's or the entire experience with your organization's products or services. All types of maps capture key interactions and motivations of the user in chronological order.

      Why are journey maps an important for mobile application delivery?

      Everyone has their own preferred method for completing their tasks on mobile devices – often, what differentiates one persona from another has to do with how users privately behave. Understand that the activities performed outside of IT's purview develop context for your persona's pain points and position IT to meet their needs with the appropriate solution.

      To learn more, visit Info-Tech's Use Experience Design to Drive Empathy with the Business blueprint.

      Two charts are depicted, the first shows the path from Trigger, through steps 1-4, to the outcome, and the Activities and Touchpoints for each. The second chart shows the Expectation analysis, showing which steps are must-haves, nice-to-haves, and hidden-needs.

      Pinpoint specific mobile needs in your journey map

      Realize that mobile applications may not precisely fit with your personas workflow or align to their expectations due to device and system limitations and restrictions. Flag the mobile opportunities that require significant modifications to underlying systems.

      Consider these workflow scenarios that can influence your persona's desire for mobile:

      Workflow Scenarios Ask Yourself The Key Questions Technology Constraints or Restrictions to Consider Examples of Mobile Opportunities

      Data View – Data is queried, prepared and presented to make informed decisions, but it cannot be edited.

      Where is the data located and can it be easily gathered and prepared?

      Is the data sensitive and can it be locally stored?

      What is the level of detail in my view?

      Multi-factor authentication required.

      Highly sensitive data requires encryption in transit and at rest.

      Minor calculations and preparation needed before data view.

      Generate a status report.

      View social media channels.

      View contact information.

      Data Collection – Data is inputted directly into the application and updates back-end system or integrated 3rd party services.

      Do I need special permission to add, delete and overwrite data?

      How much data can I edit?

      Is the data automatically gathered?

      Bandwidth restrictions.

      Multi-factor authentication required.

      Native device access required (e.g., camera).

      Multiple types and formats of gathered data.

      Manual and automatic data gathering

      Book appointments with clients.

      Update inventory.

      Tracking movement of company assets.

      Data Analysis & Modification – Data is evaluated, manipulated and transformed through the application, back-end system or 3rd party service.

      How complex are my calculations?

      Can computations be offloaded?

      What resources are needed to complete the analysis?

      Memory and processing limitations on device.

      Inability to configure device and enterprise hardware to support system resource demand.

      Scope and precision of analysis and modifications.

      Evaluate and propose trends.

      Gauge user sentiment.

      Propose next steps and directions.

      Define the mobile experience your end users want

      Anytime, Anywhere
      The user can access, update and analyze data, and corporate products and services whenever they want, in all networks, and on any device.

      Hands-Off & Automated
      The application can perform various workflows and tasks without the user's involvement and notify the user when specific triggers are hit.

      Personalized & Insightful
      Content presentation and subject are tailored for the user based on specific inputs from the user, device hardware or predicted actions.

      Integrated Ecosystem
      The application supports a seamless experience across various 3rd party and enterprise applications and services the user needs.

      Visually Pleasing & Fulfilling
      The UI is intuitive and aesthetically gratifying with little security and performance trade-offs to use the full breadth of its functions and services.

      Each mobile platform has its own take on the mobile native experience. The choice ultimately depends on whether the costs and effort are worth the anticipated value.

      1.2.1 Discover your mobile needs

      1-3 hours

      1. Define the workflow of a high priority opportunity in your mobile backlog. This workflow can be pertaining to an existing mobile application or a workflow that can benefit with a mobile application.
        1. Indicate the trigger that will initiate the opportunity and the desired outcome.
        2. Break down the persona's desired outcome into small pieces of value that are realized in each workflow step.
      2. Identify activities and touchpoints the persona will need to complete to finish each step in the workflow. Indicate the technology used to complete the activity or to facilitate the touchpoint.
      3. Indicate which activities and touchpoints can be satisfied, complimented or enhanced with mobile.

      Input

      Output
      • User personas
      • Mobile application canvas
      • Desired mobile experience
      • List of mobile features
      • Journey map
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      1.2.1 cont'd

      Workflow

      Trigger

      Conduct initial analysis

      Get planning help

      Complete and submit RFP

      Design and implement solution

      Implement changes

      Activities, Channels, and Touchpoints

      Need is recognized in CIO council meeting

      See if we have a sufficient solution internally

      Seek planning help (various channels)

      *Meet with IT shared services business analyst

      Select the appropriate vendor

      Follow action plan

      Compliance rqmt triggered by new law

      See if we have a sufficient solution internally

      *Hold in-person initial meeting with IT shared services

      *Review and approve rqmts (email)

      Seek miscellaneous support

      Implement project and manage change

      Research potential solutions in the marketplace

      Excess budget identified for utilization

      Pick a "favorite" solution

      *Negotiate and sign statement of work (email)

      Prime organization for the change

      Create action plan

      If solution is unsatisfactory, plan remediation

      Current Technology

      • Email
      • Video conferencing
      • Phone
      • Meeting transcripts and recordings
      • ERP
      • IT asset management
      • Internet browser for research
      • Virtual environment to demonstrate solutions
      • Email
      • Vendor assessment and procurement solution
      • Email
      • Video conferencing
      • Phone
      • Meeting transcripts and recordings
      • PDF documents and reader
      • Digital signature
      • Email
      • Video conferencing
      • Phone
      • Meeting transcripts and recordings
      • PDF documents and reader
      • Digital signature
      • Email
      • Video conferencing
      • Phone
      • Vendor assessment and procurement solution
      • Project management solution
      • Team collaboration solution
      • Email
      • Video conferencing
      • Phone
      • Project management solution
      • Team collaboration solution
      • Vendor's solution

      Legend:

      Bold – Touchpoint

      * – Activities or Touchpoints That Can Benefit with Mobile

      1.2.1 cont'd

      1-3 hours

      1. Analyze persona expectations. Identify the persona's must-haves, then nice-to-haves, and then hidden needs to effectively complete the workflow.
        1. Must-haves. The necessary outcomes, qualities, and features of the workflow step.
        2. Nice-to-haves. Desired outcomes, qualities, or features that your persona is able to articulate or express.
        3. Hidden needs. Outcomes, qualities, or features that your persona is not aware they have a desire for; benefits that they are pleasantly surprised to receive. These will usually be unknown for your first-iteration journey map.
      2. Indicate which persona expectations can be satisfied with mobile. Discuss what would the desired mobile experience be.
      3. Discuss feedback and experiences your team has heard from the personas they engage with regularly.
      4. Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Download the Mobile Application Delivery Communication Template

      1.2.1 cont'd

      Example

      This image contains an example workflow for determining mobile needs.

      1.2.1 cont'd

      Template:

      Workflow

      TriggerStep 1Step 2Step 3Step 4

      Desired Outcome

      Journey Map

      Activities & Touch-points

      <>

      <>

      <>

      <>

      <>

      <>

      Must-Haves

      <>

      <>

      <>

      <>

      <>

      <>

      Nice-to-Haves

      <>

      <>

      <>

      <>

      <>

      <>

      Hidden Needs

      <>

      <>

      <>

      <>

      <>

      <>

      Emotional Journey

      <>

      <>

      <>

      <>

      <>

      <>

      If you need more than four steps in the workflow, duplicate this slide.

      Understand how mobile fits with your current system

      Evaluate the risks and impacts of your desired mobile features by looking at your enterprise system architecture from top to bottom. Is your mobile vision and needs compatible with your existing business capabilities and technologies?

      An architecture is usually represented by one or more architecture views that together provide a coherent description of the application system, including demonstrating the full impact mobile will have. A single, comprehensive model is often too complex to be understood and communicated in its most detailed form, and a model too high level hides the underlying complexity of an application's structure and deployment (The Open Group, TOGAF 8.1.1 - Developing Architecture Views). Obtain a complete understanding of your architecture by assessing it through multiple levels of views to reveal different sets of concerns:

      Application Architecture Views

      1. Use Case View
      • How does your business operate, and how will users interact with your mobile applications?
    • . Process View
      • What is the user workflow impacted by mobile, and how will it change?
    • Component View
      • How are my existing applications structured? What are its various components? How will mobile expand the costs of the existing technical debt?
    • Data View
      • What is the relationship of the data and information consumed, analyzed, and transmitted? Will mobile jeopardize the quality and reliability of the data?
    • Deployment View
      • In what environment are your mobile application components deployed? How will the existing systems operate with your mobile applications?
    • System View
      • How does your mobile application communicate with other internal and external systems? How will dependencies change with mobile?
    • See our Enhance Your Solution Architecture for more information.

      Ask key questions in your current system assessment

      • How do the various components of your system communicate with each other (e.g., web APIs, middleware, and point to point)?
      • What information is exchanged during the conversation?
      • How does the data flow from one component to the next? Is the data read-only or can application and users edit and modify it?
      • What are the access points to your mid- and back-tier systems (e.g., user access through web interface, corporate networks and third-party application access through APIs)?
      • Who has access to your enterprise systems?
      • Which components are managed and operated by third-party providers? What is your level of control?
      • What are the security protocols currently enforced in your system?
      • How often are your databases updated? Is it real-time or periodic extract, transfer, and load (ETL)?
      • What are the business rules?
      • Is your mobile stack dependent on other systems?
      • Is a mobile middleware, web server, or API gateway needed to help facilitate the integration between devices and your back-end support?

      1.2.2 Conduct a technical assessment

      1-3 hours

      1. Evaluate your current systems that will support the journey map of your mobile opportunities based on two categories: system quality and system management. Use the tables on the following slides and modify the questions if needed.
      2. Discuss if the current state of your system will impede your ability to succeed with mobile. Use this discussion to verify the decision to continue with mobile applications in your current state.
      3. Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Download the Mobile Application Delivery Communication Template

      Input

      Output
      • Journey map
      • Understanding of current system
      • Assessment of current system
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      1.2.2 cont'd

      Current State System Quality Assessment

      Factors Definitions Survey Responses
      Fit-for-Purpose System functionalities, services and integrations are designed and implemented for the purpose of satisfying the end users' needs and technology compatibilities. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Response Rate The system completes computation and processing requests within acceptable timeframes. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Data Quality The system delivers consumable, accurate, and trustworthy data. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Usability The system provides functionalities, services and integrations that are rewarding, engaging, intuitive, and emotionally satisfying. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Reliability The system is resilient or quickly recovers from issues and defects. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Accessible The system is available on demand and on the end user's preferred interface and device. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Secured End-user activity and data is protected from unauthorized access. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Adaptable The system can be quickly tailored to meet changing end-user and technology needs with reusable and customizable components. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)

      1.2.2 cont'd

      Current State System Management Assessment

      Factors Definitions Survey Responses
      Documentation The system is documented, accurate, and shared in the organization. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Measurement The system is continuously measured against clearly defined metrics tied to business value. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Compliance The system is compliant with regulations and industry standards. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Continuous Improvement The system is routinely rationalized and enhanced. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Architecture There is a shared overview of how the process supports business value delivery and its dependencies with technologies and other processes. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Ownership & Accountability The process has a clearly defined owner who is accountable for its risks and roadmap. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Support Resources are available to address adoption and execution challenges. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)
      Organizational Change Management Communication, onboarding, and other change management capabilities are available to facilitate technology and related role and process changes. 1 (Very Poor) – 2 – 3 (Fair) – 4 – 5 (Excellent)

      Step 1.3

      Define Your Non-Functional Requirements

      Activities

      1.3.1 Define mobile application quality

      1.3.2 Verify your decision to deliver mobile applications

      Set the Mobile Context

      This step involves the following participants:

      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams

      Outcomes of this step

      • Mobile application quality definition
      • Readiness for mobile delivery

      Build a strong foundation of mobile application quality

      Functionality and aesthetics often take front seats in mobile application delivery. Applications are then frequently modified and changed, not because they are functionally deficient or visually displeasing, but because they are difficult to maintain or scale, too slow, vulnerable or compromised. Implementing clear quality principles (i.e., non-functional requirements) and strong quality assurance practices throughout delivery are critical to minimize the potential work of future maintenance and to avoid, mitigate and manage IT risks.

      What is Mobile Application Quality?

      • Quality requirements (i.e., non-functional requirements) are properties of a system or product that dictate how it should behave at runtime and how it should be designed, implemented, and maintained.
      • These requirements should be involved in decision making around architecture, UI and functional design changes.
      • Functionality should not dictate the level of security, availability, or performance of a product, thereby risking system quality. Functionality and quality are viewed orthogonally, and trade-offs are discussed when one impacts the other.
      • Quality attributes should never be achieved in isolation as one attribute can have a negative or positive impact on another (e.g. security and availability).

      Why is Mobile Quality Assurance Critical?

      • Quality assurance (QA) is a necessity for the validation and verification of mobile delivery, whether you are delivering applications in an Agile or Waterfall fashion. Effective QA practices implemented across the software development lifecycle (SDLC) are vital, as all layers of the mobile stack need to readily able to adjust to suddenly evolving and changing business and user needs and technologies without risking system stability and breaking business standards and expectations.
      • However, investments in QA optimizations are often afterthoughts. QA is commonly viewed as a lower priority compared to other delivery capabilities (e.g., design and coding) and is typically the first item cut when delivery is under pressure.

      See our Build a Software Quality Assurance Program for more information.

      Mobile emphasizes the importance of good security, performance and integration

      Today's mobile workforce is looking for new ways to get more work done quickly. They want access to enterprise solutions and data directly on their mobile device, which can reside on multiple legacy systems and in the cloud and third-party infrastructure. This presents significant performance, integration, and security risks.

      Cloud Solutions: Can I use my existing APIs?. Solutions in Corporate Networks: Do my legacy systems have the capacity to support mobile?; How do I integrate solutions and data from multiple sources into a single view?; Third Party Solutions: Will I have a significant performance bottleneck?; Single View on Mobile Devices: How is corporate data stored on the device?; What new technology dependencies must I account for in my architecture and operational support capabilities?

      Mobile risks opening and widening existing security gaps

      New mobile technologies and the continued expansion of the enterprise environment increase the number of entry points attackers to your corporate data and networks. The ever-growing volume, velocity, and variety of new threats puts significant pressure on mobile delivery teams who are responsible for implementing mobile security measures and maintaining alignment to your security policies and those of app stores.

      Mobile attacks can come from various vectors:

      Attack Surface: Mobile Device

      Attack Surface: Network

      Attack Surface: Data Center

      Browser:
      Phishing
      Buffer Overflow
      Data Caching

      System:
      No Passcode
      Jailbroken and Rooted OS
      No/Weak Encryption
      OS Data Caching

      Phone:
      SMSishing
      Radio Frequency Attacks

      Apps:
      Configuration Manipulation
      Runtime Injection
      Improper SSL Validation

      • Packet Sniffing
      • Session Hijacking
      • Man-in-the-Middle (circumvent password verification systems)
      • Fake SSL Certificate
      • Rogue Access Points

      Web Server:
      Cross-Site Scripting (XSS)
      Brute Force Attacks
      Server Misconfigurations

      Database:
      SQL Injection
      Data Dumping

      Understand the top web security risks and vulnerabilities seen in the industry

      Recognize mobile applications are exposed to the same risks and vulnerabilities as web applications. Learn of OWASP's top 10 web security risks.

      • Broken Access Control
        • Failures typically lead to unauthorized information disclosure, modification, or destruction of all data or performing a business function outside the user's limits.
      • Cryptographic Failures
        • Improper and incorrect protection of data in transit and at rest, especially proprietary and confidential data and those that fall under privacy laws.
      • Injection
        • Execution of malicious code and injection of hostile or unfiltered data on the mobile device via the mobile application.
      • Insecure Design
        • Missing or ineffective security controls in the application design. An insecure design cannot be fixed by a perfect implementation,. Needed security controls were never created to defend against specific attacks.
      • Security Misconfiguration
        • The security settings in the application are not securely set or configured, including poor security hardening and inadequate system upgrading practices.
      • Vulnerable and Outdated Components
        • System components are vulnerable because they are unsupported, out of date, untested or not hardened against current security concerns.
      • Identification and Authentication Failures
        • Improper or poor protection against authentication-related attacks, particularly to the user's identity, authentication and session management.
      • Software and Data Integrity Failures
        • Failures related to code and infrastructure that does not protect against integrity violations, such as an application relying upon plugins, libraries, or modules from untrusted sources, repositories, and content delivery networks
      • Security Logging and Monitoring Failures
        • Insufficient logging, detection, monitoring, and active response that hinders the ability to detect, escalate, and respond to active breaches.
      • Server-Side Request Forgery (SSRF)
        • SSRF flaws occur whenever a web application is fetching a remote resource without validating the user-supplied URL.

      Good mobile application performance drives satisfaction and value delivery

      Underperforming mobile applications can cause your users to be unproductive. Your mobile applications should always aim to satisfy the productivity requirements of your end users.

      Users quickly notice applications that are slow and difficult to use. Providing a seamless experience for the user is now heavily dependent on how well your application performs. Optimizing your mobile application's processing efficiency can help your users perform their jobs properly in various environment conditions.

      Productive Users Need
      Performant Mobile Applications

      Persona

      Mobile Application Use Case

      Optimized Mobile Application

      Stationary Worker

      • Design flowcharts and diagrams, while abandoning paper and desktop apps in favor of easy-to-use, drawing tablet applications.
      • Multitask by checking the application to verify information given by a vendor during their presentation or pitch.
      • Flowcharts and diagrams are updated in real time for team members to view and edit
      • Compare vendors under assessment with a quick look-up app feature

      Roaming Worker (Engineer)

      • Replace physical copies of service and repair manuals physically stored with digital copies and access them with mobile applications.
      • Scan or input product bar code to determine whether a replacement part is available or needs to be ordered.
      • Worker is capable of interacting with other features of the mobile web app while product bar code is being verified

      Enhance the performance of the entire mobile stack

      Due to frequently changing mobile hardware, users' high performance expectations and mobile network constraints, mobile delivery teams must focus on the entire mobile stack for optimizing performance.

      Fine tune your enterprise mobile applications using optimization techniques to improve performance across the full mobile stack.

      This image contains a bar graph ranking the importance of the following datapoints: Minimize render blocking resources; Configure the mobile application viewport; Determine the right image file format ; Determine above-the-fold content; Minimize browser reflow; Adopt UI techniques to improve perceived latency; Resource minification; Data compression; Asynchronous programming; Resource HTTP caching; Minimize network roundtrips for first time to render.

      Info-Tech Insight

      Some user performance expectations can be managed with clever UI design (e.g., spinning pinwheels to indicate loading in progress and directing user focus to quick loading content) and operational choices (e.g. graceful degradation and progressive enhancements).

      Create an API-centric integration strategy

      Mobile delivery teams are tasked to keep up with the changing needs of end users and accommodate the evolution of trending mobile features. Ensuring scalable APIs is critical in quickly releasing changes and ensuring availability of corporate services and resources.

      As your portfolio of mobile applications grows, and device platforms and browsers diversify, it will become increasingly complex to provide all the data and service capabilities your mobile apps need to operate. It is important that your APIs are available, reliable, reusable, and secure for multiple uses and platforms.

      Take an API-centric approach to retain control of your mobile development and ensure reliability.

      APIs are the underlying layer of your mobile applications, enabling remote access of company data and services to end users. Focusing design and development efforts on the maintainability, reliability and scalability of your APIs enables your delivery teams to:

      • Reuse tried-and-tested APIs to deliver, test and harden applications and systems quicker by standardizing on the use and structure of REST APIs.
      • Ensure a consistent experience and performance across different applications using the same API.
      • Uniformly apply security and access control to remain compliant to security protocols, industry standards and regulations.
      • Provide reliable integration points when leveraging third-party APIs and services.

      See our Build Effective Enterprise Integration on the Back of Business Process for more information.

      Guide your integration strategy with principles

      Craft your principles around good API management and integration practices

      Expose Enterprise Data And Functionality in API-Friendly Formats
      Convert complex on-premises application services into developer-friendly RESTful APIs

      Protect Information Assets Exposed Via APIs to Prevent Misuse
      Ensure that enterprise systems are protected against message-level attack and hijack

      Authorize Secure, Seamless Access for Valid Identities
      Deploy strong access control, identity federation and social login functionality

      Optimize System Performance and Manage the API Lifecycle
      Maintain the availability of backend systems for APIs, applications and end users

      Engage, Onboard, Educate and Manage Developers
      Give developers the resources they need to create applications that deliver real value

      Source: 5 Pillars of API Management, Broadcom, 2021

      Clarify your definition of mobile quality

      Quality does not mean the same thing to everyone

      Do not expect a universal definition of mobile quality. Each department, person and industry standard will have a different interpretation of quality, and they will perform certain activities and enforce policies that meet those interpretations. Misunderstanding of what is defined as a high quality mobile application within business and IT teams can lead to further confusion behind governance, testing priorities and compliance.

      Each interpretation of quality can lead to endless testing, guardrails and constraints, or lack thereof. Be clear on the priority of each interpretation and the degree of effort needed to ensure they are met.

      For example:

      Mobile Application Owner
      What does an accessible mobile application mean?

      Persona: Customer
      I can access it on mobile phones, tablets and the web browser

      Persona: Developer
      I have access to each layer of the mobile stack including the code & data

      Persona: Operations
      The mobile application is accessible 24/7 with 95% uptime

      Example: A School Board's Quality Definition

      Quality Attribute Definitions
      Usability The product is an intuitive solution. Usability is the ease with which the user accomplishes a desired task in the application system and the degree of user support the system provides. Limited training and documentation are required.
      Performance Usability and performance are closely related. A solution that is slow is not usable. The application system is able to meet timing requirements, which is dependent on stable infrastructure to support it regardless of where the application is hosted. Baseline performance metrics are defined and changes must result in improvements. Performance is validated against peak loads.
      Availability The application system is present, accessible, and ready to carry out its tasks when needed. The application is accessible from multiple devices and platforms, is available 24x7x365, and teams communicate planned downtimes and unplanned outages. IT must serve teachers international student's parents, and other users who access the application outside normal business hours. The application should never be down when it should be up. Teams must not put undue burden on end users accessing the systems. Reasonable access requirements are published.
      Security Applications handle both private and personal data, and must be able to segregate data based on permissions to protect privacy. The application system is able to protect data and information from unauthorized access. Users want it to be secure but seamless. Vendors need to understand and implement the District School Board's security requirements into their products. Teams ensure access is authorized, maintain data integrity, and enforce privacy.
      Reusability Reusability is the capability for components and subsystems to be suitable for use in other applications and in other scenarios. This attribute minimizes the duplication of components and implementation time. Teams ensure a modular design that is flexible and usable in other applications.
      Interoperability The degree to which two or more systems can usefully exchange meaningful information via interfaces in a particular context.

      Scalability

      There are two kinds of scalability:

      • Horizontal scalability (scaling out): Adding more resources to logical units, such as adding another server to a cluster of servers.
      • Vertical scalability (scaling up): Adding more resources to a physical unit, such as adding more memory to a single computer.

      Ease of maintenance and enhancements are critical. Additional care is given to custom code because of the inherent difficulty to make it scale and update.

      Modifiability The capability to manage the risks and costs of change, considering what can be changed, the likelihood of change, and when and who makes the change. Teams minimize the barriers to change, and get business buy in to keep systems current and valuable.
      Testability The ease with which software are made to demonstrate its faults through (typically execution-based) testing. It cannot be assumed that the vendor has already tested the system against District School Board's requirements. Testability applies to all applications, operating systems, and databases.
      Supportability The ability of the system to provide information helpful for identifying and resolving issues when it fails to work correctly. Supportability applies to all applications and systems within the District School Board's portfolio, whether that be custom developed applications or vendor provided solutions. Resource investments are made to better support the system.
      Cost Efficiency The application system is executed and maintained in such a way that each area of cost is reduced to what is critically needed. Cost efficiency is critical (e.g. printers cost per page, TCO, software what does downtime cost us), and everyone must understand the financial impact of their decisions.
      Self-Service End users are empowered to make configurations, troubleshoot and make changes to their application without the involvement of IT. The appropriate controls are in place to manage the access to unauthorized access to corporate systems.
      Modifiability The capability to manage the risks and costs of change, considering what can be changed, the likelihood of change, and when and who makes the change. Teams minimize the barriers to change, and get business buy in to keep systems current and valuable.
      Testability The ease with which software are made to demonstrate its faults through (typically execution-based) testing. It cannot be assumed that the vendor has already tested the system against District School Board's requirements. Testability applies to all applications, operating systems, and databases.
      Supportability The ability of the system to provide information helpful for identifying and resolving issues when it fails to work correctly. Supportability applies to all applications and systems within the District School Board's portfolio, whether that be custom developed applications or vendor provided solutions. Resource investments are made to better support the system.

      1.3.1 Define mobile application quality

      1-3 hours

      1. List 5 quality attributes that your organization sees as important for a successful mobile application.
      2. List the core personas that will support mobile delivery and that will consume the mobile application. Start with development, operations and support, and end user.
      3. Describe each quality attributes from the perspective of each persona by asking, "What does quality mean to you?".
      4. Review each description from each persona to come to an acceptable definition.
      5. Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Download the Mobile Application Delivery Communication Template

      Input

      Output
      • User personas
      • Mobile application canvas
      • Journey map
      • Mobile application quality definition
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      1.3.1 cont'd

      Example: Info-Tech Guided Implementation with a Legal and Professional Services Organization

      Quality AttributeDeveloperOperations & Support TeamEnd Users

      Usability

      • Architecture and frameworks are aligned with industry best practices
      • Regular feedback through analytics and user feedback
      • Faster development and less technical debt
      • Pride in the product
      • Satisfaction that the product is serving its purpose and is actually being used by the user
      • Increased update of product use and feedback for future lifecycle
      • Standardization and positive perception of IT processes
      • Simpler to train users to adopt products and changes
      • Trust in system and ability to promote the product in a positive light
      • Trusted list of applications
      • Intuitive (easy to use, no training required)
      • Encourage collaboration and sharing ideas between end users and delivery teams
      • The information presented is correct and accurate
      • Users understand where the data came from and the algorithms behind it
      • Users learn features quickly and retain their knowledge longer, which directly correlates to decreased training costs and time
      • High uptake in use of the product
      • Seamless experience, use less energy to work with product

      Security

      • Secure by design approach
      • Testing across all layers of the application stack
      • Security analysis of our source code
      • Good approach to security requirement definition, secure access to databases, using latest libraries and using semantics in code
      • Standardized & clear practices for development
      • Making data access granular (not all or none)
      • Secure mission critical procedures which will reduce operational cost, improve compliance and mitigate risks
      • Auditable artifacts on security implementation
      • Good data classification, managed secure access, system backups and privacy protocols
      • Confidence of protection of user data
      • Encryption of sensitive data
      Availability
      • Good access to the code
      • Good access to the data
      • Good access to APIs and other integration technologies
      • Automatic alerts when something goes wrong
      • Self-repairing/recovering
      • SLAs and uptimes
      • Code documentation
      • Proactive support from the infrastructure team
      • System availability dashboard
      • Access on any end user device, including mobile and desktop
      • 24/7 uptime
      • Rapid response to reported defects or bugs
      • Business continuity

      1.3.2 Verify your decision to deliver mobile applications

      1-3 hours

      1. Review the various end user, business and technical expectations for mobile its achievability given the current state of your system and non-functional requirements.
      2. Complete the list of questions on the following slide as an indication for your readiness for mobile delivery.

      Input

      Output
      • Mobile application canvas
      • Assessment to proceed with mobile
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      1.3.2 cont'd

      Skill Sets
      Software delivery teams have skills in creating mobile applications that stakeholders are expecting in value and quality. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Architects look for ways to reuse existing technical asset and design for future growth and maturity in mobile. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Resources can be committed to implement and manage a mobile platform. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Software delivery teams and resources are adaptable and flexible to requirements and system changes. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Delivery Process
      My software delivery process can accommodate last minute and sudden changes in mobile delivery tasks. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Business and IT requirements for the mobile are clarified through collaboration between business and IT representatives. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Mobile will help us fill the gaps and standardize our software delivery process process. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      My testing practices can be adapted to verify and validate the mobile functional and non-functional requirements. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Technical Stack
      My mid-tier and back-end support has the capacity to accommodate additional traffic from mobile. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      I have access to my web infrastructure and integration technologies, and I am capable of making configurations. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      My security approaches and capabilities can be enhanced address specific mobile application risks and vulnerabilities. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      I have a sound and robust integration strategy involving web APIs that gives me the flexibility to support mobile applications. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)

      Phase 2

      Define Your Mobile Approach

      Choose Your Mobile Platform and Tools

      This phase will walk you through the following activities:

      • Step 2.1 – Choose Your Platform Approach
      • Step 2.2 – Shortlist Your Mobile Delivery Solution
      • Step 2.3 – Create a Roadmap for Mobile Delivery

      This phase involves the following participants:

      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      Step 2.1

      Choose Your Platform Approach

      Activities

      2.1.1 Select your platform approach

      Define Your Mobile Approach

      This step involves the following participants:

      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      Outcomes of this step

      • Desired mobile platform approach

      Mobile value is dependent on the platform you choose

      What is a platform?

      "A platform is a set of software and a surrounding ecosystem of resources that helps you to grow your business. A platform enables growth through connection: its value comes not only from its own features, but from its ability to connect external tools, teams, data, and processes." (Source: Emilie Nøss Wangen, 2021) In the mobile context, applications in a platform execute and communicate through a loosely coupled API architecture whether the supporting system is managed and supported by your organization or by 3rd party providers.

      Web

      The mobile web often takes on one of the following two approaches:

      • Responsive websites – Content, UI and other website elements automatically adjusts itself according to the device, creating a seamless experience regardless of the device.
      • Progressive web applications (PWAs) – PWAs uses the browser's APIs and features to offer native-like experiences.

      Mobile web applications are often developed with a combination of HTML, CSS, and JavaScript languages.

      Hybrid

      Hybrid applications are developed with web technologies but are deployed as native applications. The code is wrapped using a framework so that it runs locally within a native container, and it uses the device's browser runtime engine to support more sophisticated designs and features compared to the web approach. Hybrid mobile solutions allows teams to code once and deploy to multiple platforms.

      Some notable examples:

      • Gmail
      • Instagram

      Cross-Platform

      Cross-platform applications are developed within a distinct programming or scripting environment that uses its own scripting language (often like web languages) and APIs. Then the solution will compile the code into device-specific builds for native deployment.

      Some notable examples:

      • Facebook
      • Skype
      • Slack

      Native

      Native applications are developed and deployed to specific devices and OSs using platform-specific software development kits (SDKs) provided by the operating system vendors. The programming language and framework are dictated by the targeted device, such as Java for Android.

      With this platform, developers have direct access to local device features allowing customized operations. This enables the use of local resources, such as memory and runtime engines, which will achieve a higher performance than hybrid and cross-platform applications.

      Each platform offers unique pros and cons depending on your mobile needs

      WebHybridCross-PlatformNative

      Pros

      Cons

      Pros

      Cons

      Pros

      Cons

      Pros

      Cons

      • Modern browsers support the popular of web languages (HTML, CSS, and JavaScript).
      • Ubiquitous across multiple form factors and devices.
      • Mobile can be easily integrated into traditional web development processes and technical stacks.
      • Installations are not required, and updates are immediate.
      • Sensitive data can be wiped from memory after app is closed.
      • Limited access to local device hardware and software.
      • Local caching is available for limited offline capabilities, but the scope of tasks that can be completed in this scenario is restricted.
      • The browser's runtime engine is limited in computing power.
      • Not all browsers fully support the latest versions of HTML, CSS, or JavaScript.
      • Web languages can be used to develop a complete application.
      • Code can be reused for multiple platforms, including web.
      • Access to commonly-used native features that are not available through the web platform.
      • Quick delivery and maintenance updates compared to native and cross-platform platforms.
      • Consistent internet access is needed due to its reliance heavily reliance on web technologies to operate.
      • Limited ability to support complex workflows and features.
      • Sluggish performance compared to cross-platform and native applications.
      • Certain features may not operate the same across all platforms given the code once, deploy everywhere approach.
      • More cost-effective to develop than using native development approaches to gain similar features. Platform-specific developers are not needed.
      • Common codebase to develop applications on different applications.
      • Enables more complex application functionalities and technical customizations compared to hybrid applications.
      • Code is not portable across cross-platform delivery solutions.
      • The framework is tied to the vendor solution which presents the risk of vendor lock-in.
      • Deployment is dependent on an app store and the delivery solution may not guarantee the application's acceptance into the application store.
      • Significant training and onboarding may be needed using the cross-platform framework.
      • Tight integration with the device's hardware enables high performance and greater use of hardware features.
      • Computationally-intensive and complex tasks can be completed on the device.
      • Available offline access.
      • Apps are available through easy-to-access app stores.
      • Requires additional investments, such as app stores, app-specific support, versioning, and platform-specific extensions.
      • Developers skilled in a device-specific language are difficult to acquire and costly to train.
      • Testing is required every time a new device or OS is introduced.
      • Higher development and maintenance costs are tradeoffs for native device features.

      Start mobile development on a mobile web platform

      Start with what you have: begin with a mobile web platform to minimize impacts to your existing delivery skill sets and technical stack while addressing business needs. Resort to a hybrid first and then consider a cross-platform application if you require device access or the need to meet specific non-functional requirements.

      Why choose a mobile web platform?

      Pros

      The latest versions of the most popular web languages (HTML5, CSS3, JavaScript) abstract away from the granular, physical components of the application, simplifying the development process. HTML5 offer some mobile features (e.g., geolocation, accelerometer) that can meet your desired experience without the need for native development skills. Native look-and-feel, high performance, and full device access are just a few tradeoffs of going with web languages.

      Cons

      Native mobile platforms depend on device-specific code which follows specific frameworks and leverages unique programming libraries, such as Objective C for iOS and Java for Android. Each language requires a high level of expertise in the coding structure and hardware of specific devices requiring resources with specific skillsets and different tools to support development and testing.

      Other Notable Benefits with Web Languages

      • Modern browsers in most mobile devices are capable of executing and rendering many mobile features developed in web languages, allowing for greater portability and sophistication of code across multiple devices. However, this flexibility comes at the cost of performance since the browser's runtime engine will not perform as well as a native engine.
      • Web languages are well known by developers, minimizing skills and resourcing impacts. Consequently, changes can be quickly accommodated and updated uniformly across all end users.

      Do you need a native platform?

      Consider web workarounds if you choose a web platform but require some native experiences.

      The web platform does not give you direct access or sophisticated customizations to local device hardware and services, underlying code and integrations. You may run into the situation where you need some native experiences, but the value of these features may not offset the costs to undertake a native, hybrid or cross-platform application. When developing hybrid and cross-platform applications with a mobile delivery solution, only the APIs of the commonly used device features are available. Note that some vendors may not offer a particular native feature across all devices, inhibiting your ability to achieve feature parity or exploiting device features only available in certain devices. Workarounds are then needed.

      Consider the following workarounds to address the required native experiences on the web platform:

      Native Function Description Web Workaround Impact
      Camera Takes pictures or records videos through the device's camera. Create an upload form in the web with HTML5. Break in workflow leading to poor user experience (UX).
      Geolocation Detects the geographical location of the device. Available through HTML5. Not Applicable.
      Calendar Stores the user's calendar in local memory. Integrate with calendaring system or manually upload contacts. Costly integration initiative. Poor user experience.
      Contacts Stores contact information in local memory. Integrate app with contact system or manually upload contacts. Costly integration initiative. Poor user experience.
      Near Field Communication (NFC) Communication between devices by touching them together or bringing them into proximity. Manual transfer of data. A lot of time is consumed transferring simple information.
      Native Computation Computational power and resources needed to complete tasks on the device. Resource-intensive requests are completed by back-end systems and results sent back to user. Slower application performance given network constraints.

      Info-Tech Insight

      In many cases, workarounds are available when evaluating the gaps between web and native applications. For example, not having application-level access to the camera does not negate the user option to upload a picture taken by the camera through a web form. Tradeoffs like this will come down to assessing the importance of each platform gap for your organization and whether a workaround is good enough as a native-like experience.

      Architect and configure your entire mobile stack with a plan

      • Assess your existing technology stack that will support your mobile platform. Determine if it has the capacity to handle mobile traffic and the necessary integration between devices and enterprise and 3rd party systems are robust and reliable. Reach out to your IT teams and vendors if you are missing key mobile components, such as:
      • The acquisition and provisioning of physical or virtual mobile web servers and middleware from existing vendors.
      • Cloud services [e.g., Mobile Back-end as a Service (mBaaS)] that assists in the mobilization of back-end data sources with API SDKs, orchestration of data from multiple sources, transformation of legacy APIs to mobile formats, and satisfaction of other security, integration and performance needs.
      • Configure the services of your web server or middleware to facilitate the translation, transformation, and transfer of data between your mobile front-end and back-end. If your plan involves scripts, maintenance and other ongoing costs will likely increase.
      • Leverage the APIs or adapters provided by your vendors or device manufacturers to integrate your mobile front-end and back-end support to your web server or middleware. If you are reusing a web server, the back-end integration should already be in place. Remember, APIs implement business rules to maintain the integrity of data exchange within your mobile stack.
      • See Appendix A for examples of reference architectures of mobile platforms.

      See our Enhance Your Solution Architecture for more information.

      Do Not Forget Your Security and Performance Requirements

      Security: New threats from mobile put organizations into a difficult situation beyond simply responding to them in a timely matter. Be careful not to take the benefits of security out of the mobile context. You need to make security a first-order citizen during the scoping, design, and optimization of your systems supporting mobile. It must also be balanced with other functional and non-functional requirements with the right roles taking accountability for these decisions.

      See our Strengthen the SSDLC for Enterprise Mobile Applications for more information.

      Performance: Within a distributed mobile environment, performance has a risk of diminishing due to limited device capacity, network hopping, lack of server scalability, API bottlenecks, and other device, network and infrastructure issues. Mobile web APIs suffer from the same pain points as traditional web browsing and unplanned API call management in an application will lead to slow performance.

      See our Develop Enterprise Mobile Applications With Realistic and Relevant Performance for more information.

      Enterprise platform selection requires a shift in perspective

      Your mobile platform selection must consider both user and enterprise (i.e., non-functional) needs. Use a two-step process for your analysis:

      Begin Platform Selection with a User-Centric Approach

      Organizations appealing to end users place emphasis on the user experience: the look and appeal of the user interface, and the satisfaction, ease of use, and value of its functionalities. In this approach, IT concerns and needs are not high priorities, but many functions are completed locally or isolated from mission critical corporate networks and sensitive data. Some needs include:

      • Performance: quick execution of tasks and calculations made on the device or offloaded to web servers or the cloud.
      • User Interface: cross-platform compatibility and feature-rich design and functionality. The right native experience is critical to the user adoption and satisfaction.
      • Device Access: use of local device hardware and software to complete app use cases, such as camera, calendar, and contact lists.

      Refine Platform Selection with an Enterprise-Centric Approach

      From the enterprise perspective, emphasis is on security, system performance, integration, reuse and other non-functional requirements as the primary motivations in the selection of a mobile platform. User experience is still a contributing factor because of the mobile application's need to drive value but its priority is not exclusive. Some drivers include:

      • Openness: agreed-upon industry standards and technologies that can be applied to serve enterprise needs which support business processes.
      • Integration: increase the reuse of legacy investments and existing applications and services with integration capabilities.
      • Flexibility: support for multiple data types from applications such as JSON format for mobile.
      • Capacity: maximize the utilization of your software delivery resources beyond the initial iteration of the mobile application.

      Info-Tech Insight

      Selecting a mobile platform should not solely be made on business requirements. Key technical stakeholders should be at the table in this discussion to provide insight on the implementation and ongoing costs and benefits of each platform. Both business and technical requirements should be considered when deciding on a final platform.

      Select your mobile platform

      Drive your mobile platform selection against user-centric needs (e.g. device access, aesthetics) and enterprise-centric needs (e.g. security, system performance).

      When does a platform makes sense to use?

      Web

      • Desire to maximize current web technologies investments (people, process, and technologies).
      • Use cases do not require significant computational resources on the device or are tightly constrained by non-functional requirements.
      • Limited budget to acquire mobile development resources.
      • Access to device hardware is not a high priority.

      Hybrid / Cross-Platform

      • The need to quickly spin up native-like applications for multiple platforms and devices.
      • Desire to leverage existing web development skills, but also a need for device access and meeting specific non-functional requirements.
      • Vendor support is needed for the entire mobile delivery process.

      Native

      • Developers are experts in the target programming language and with the device's hardware.
      • Strong need for high performance, security and device-specific access and customizations.
      • Application use cases requiring significant computing resources.

      Nine datapoints are arranged on a graph where the x axis s labeled: User Centric Needs; and the Y axis is labeled: Enterprise-centric needs. The datapoints are, in order from left to right, top to bottom: Hybrid; Cross- Platform; Native; Web; Hybrid or Cross- Platform; Cros-s Platform; Web; Web; Hybrid or Cross- Platform.

      2.1.1 Select your platform approach

      1-3 hours

      1. Review your mobile objectives, end user needs and non-functional requirements.
      2. Determine which mobile platform is appropriate for each mobile opportunity or use case by answering the following questions on the following slides against two factors: user-centric and enterprise-centric needs.
      3. Calculate an average score for user-centric and one for enterprise-centric. Then, map them on the matrix to indicate possible platform options. Consider all options around the plotted point.
      4. Further discuss which platforms should be the preferred choice.
      5. Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Download the Mobile Application Delivery Communication Template

      Input

      Output
      • Desired mobile experience
      • List of desired mobile features
      • Current state assessments
      • Mobile platform approach
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      2.1.1 cont'd

      User-Centric Needs: Functional Requirements

      Factors Definitions Survey Responses
      Device Hardware Access The scope of access to native device hardware features. Basic features include those that are available through current web languages (e.g., geolocation) whereas comprehensive features are those that are device-specific. 1 (Basic) – 2 – 3 (Moderate) – 4 – 5 (Comprehensive)
      Customized Execution of Device Hardware The degree of changes to the execution of local device hardware to satisfy functional needs. 1 (Use as Is) – 2 – 3 (Configure) – 4 – 5 (Customize)
      Device Software Access The scope of access to software on the user's device, such as calendars and contact. 1 (Basic) – 2 – 3 (Moderate) – 4 – 5 (Comprehensive)
      Customized Execution of Device Software The degree of changes to the execution of local device software to satisfy functional needs. 1 (Use as Is) – 2 – 3 (Configure) – 4 – 5 (Customize)
      Use Case Complexity Workflow tasks and decisions are simple and straightforward. Complex computation is not needed to acquire the desired outcome. 1 (Strongly Agree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Disagree)
      Computational Resources The resources needed on the device to complete desired functional needs. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Use Case Ambiguity The mobile use case and technical requirements are well understood and documented. Changes to the mobile application is likely. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Mobile Application Access Enterprise systems and data are accessible to the broader organization through the mobile application. This factor does not necessarily mean that anyone can access it untracked. You may still need to identify yourself or log in, etc. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Scope of Adoption & Impact The extent to which the mobile application is leveraged in the organization. 1 (Enterprise) – 2 – 3 (Department) – 4 – 5 (Team)
      Installable The need to locally install the mobile application. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Targeted Devices & Platforms Mobile applications are developed for a defined set of mobile platform versions and types and device. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Output Audience The mobile application transforms an input into a valuable output for high-priority internal or external stakeholders. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)

      2.1.1 cont'd

      User-Centric Needs: Native User Experience Factors

      Factors Definitions Survey Responses
      Immersive Experience The need to bridge physical world with the virtual and digital environment, such as geofencing and NFC. 1 (Internally Delivered) – 2 – 3 (3rd Party Supported) – 4 – 5 (Business Implemented)
      Timeliness of Content and Updates The speed of which the mobile application (and supporting system) responds with requested information, data and updates from enterprise systems and 3rd party services. 1 (Reasonable Delayed Response) – 2 – 3 (Partially Outsourced) – 4 – 5 (Fully Outsourced)
      Application Performance The speed of which the mobile application completes tasks is critical to its success. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Network Accessibility The needed ability to access and use the mobile application in various network conditions. 1 (Only Available When Online) – 2 – 3 (Partially Available When Online) – 4 – 5 (Available Online)
      Integrated Ecosystem The approach to integrate the mobile application with enterprise or 3rd party systems and services. 1 (Out-of-the-Box Connectors) – 2 – 3 (Configurable Connectors) – 4 – 5 (Customized Connectors)
      Desire to Have a Native Look-and-Feel The aesthetics and UI features (e.g., heavy animations) that are only available through native and cross-platform applications. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      User Tolerance to Change The degree of willingness and ableness for a user to change their way of working to maximize the value of the mobile application. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Mission Criticality The business could not execute its main strategy if the mobile application was removed. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Business Value The mobile application directly adds business value to the organization. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Industry Differentiation The mobile application provides a distinctive competitive advantage or is unique to your organization. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)

      2.1.1 cont'd

      Enterprise-Centric Needs: Non-Functional Requirements

      Factors Definitions Survey Responses
      Legacy Compatibility The need to integrate and operate with legacy systems. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Code Portability The need to enable the "code once and deploy everywhere" approach. 1 (High) – 2 – 3 (Moderate) – 4 – 5 (Low)
      Vendor & Technology Lock-In The tolerance to lock into a vendor mobile delivery solution or technology framework. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Data Sensitivity The data used by the mobile application does not fall into the category of sensitive data – meaning nothing financial, medical, or personal identity (GDPR and worldwide equivalents). The disclosure, modification, or destruction of this data would cause limited harm to the organization. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Data Policies Policies of the mobile application's data are mandated by internal departmental standards (e.g. naming standards, backup standards, data type consistency). Policies only mandated in this way usually have limited use in a production capacity. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Security Risks Mobile applications are connected to private data sources and its intended use will be significant if underlying data is breached. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      Business Continuity & System Integrity Risks The mobile application in question does not have much significance relative to the running of mission critical processes in the organization. 1 (Strongly Disagree) – 2 – 3 (Neutral) – 4 – 5 (Strongly Agree)
      System Openness Openness of enterprise systems to enable mobile applications from the user interface to the business logic and backend integrations and database. 1 (High) – 2 – 3 (Moderate) – 4 – 5 (Low)
      Mobile Device Management The organization's policy for the use of mobile devices to access and leverage enterprise data and services. 1 (Bring-Your-Own-Device) – 2 – 3 (Hybrid) – 4 – 5 (Corporate Devices)

      2.1.1 cont'd

      Enterprise-Centric Needs: Delivery Capacity

      Factors Definitions Survey Responses
      Ease of Mobile Delivery The desire to have out-of-the-box and packaged tools to expedite mobile application delivery using web technologies. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Solution Competency The capability for internal staff to and learn how to implement and administer mobile delivery tools and deliver valuable, high-quality applications. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Ease of Deployment The desire to have the mobile applications delivered by the team or person without specialized resources from outside the team. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Delivery Approach The capability to successfully deliver mobile applications given budgetary and costing, resourcing, and supporting services constraints. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Maintenance & Operational Support The capability of the resources to responsibly maintain and operate mobile applications, including defect fixes and the addition and extension of modules to base implementations of the digital product. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Domain Knowledge Support The availability and accessibility of subject and domain experts to guide facilitate mobile application implementation and adoption. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Delivery Urgency The desire to have the mobile application delivered quickly. 1 (High) – 2 – 3 (Moderate) – 4 – 5 (Low)
      Reusable Components The desire to reuse UI elements and application components. 1 (High) – 2 – 3 (Moderate) – 4 – 5 (Low)

      2.1.1 cont'd

      Example:

      Score Factors (Average) Mobile Opportunity 1: Inventory Management Mobile Opportunity 2: Remote Support
      User-Centric Needs 4.25 3
      Functional Requirements 4.5 2.25
      Native User Experience Factors 4 1.75
      Enterprise-Centric Needs 4 2
      Non-Functional Requirements 3.75 3.25
      Delivery Capacity 4.25 2.75
      Possible Mobile Platform Cross-Platform Native PWA Hybrid

      Nine datapoints are arranged on a graph where the x axis s labeled: User Centric Needs; and the Y axis is labeled: Enterprise-centric needs. The datapoints are, in order from left to right, top to bottom: Hybrid; Cross- Platform; Native; Web; Hybrid or Cross- Platform; Cros-s Platform; Web; Web; Hybrid or Cross- Platform. Two yellow circles are overlaid, one containing the phrase: Remote Support - over the box containing Progressive Web Applications (PWA) or Hybrid; and a yellow circle containing the phrase Inventory MGMT, partly covering the box containing Native; and the box containing Cross-Platform.

      Build a scalable and manageable platform

      Long-term mobile success depends on the efficiency and reliability of the underlying operational platform. This platform must support the computational and performance demands in a changing business environment, whether it is composed of off-the-self or custom-developed solutions, or a single vendor or best-of-breed.

      • Application
        • The UI design and content language is standardized and consistently applied
        • All mobile configurations and components are automatically versioned
        • Controlled administration and tooling access, automation capabilities, and update delivery
        • Holistic portfolio management
      • Data
        • Automated data management to preserve data quality (e.g. removal of duplications)
        • Defined single source of truth
        • Adherence to data governance, and privacy and security policies
        • Good content management practices, governance and architecture
      • Infrastructure
        • Containers and sandboxes are available for development and testing
        • Self-healing and self-service environments
        • Automatic system scaling and load balancing
        • Comply to budgetary and licensing constraints
      • Integration
        • Backend database and system updates are efficient
        • Loosely coupled architecture to minimize system regressions and delivery effort
        • Application, system and data monitoring

      Step 2.2

      Shortlist Your Mobile Delivery Solution

      Activities

      2.2.1 Shortlist your mobile delivery solution

      2.2.2 Build your feature and service lists

      Define Your Mobile Approach

      This step involves the following participants:

      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      Outcomes of this step

      • Shortlisted mobile delivery solutions
      • Desired list of vendor features and services

      Ask yourself: should I build or buy?

      Build Buy

      Multi-Source Best-of-Breed

      Vendor Add-Ons & Integrations

      Integrate various technologies that provide subset(s) of the features needed for supporting the business functions.

      Enhance an existing vendor's offerings by using their system add-ons either as upgrades, new add-ons or integrations.

      Pros

      • Flexibility in choice of tools.
      • In some cases, cost may be lower.
      • Easier to enhance with in-house teams.

      Cons

      • Introduces tool sprawl.
      • Requires resources to understand tools and how they integrate.
      • Some of the tools necessary may not be compatible with each other.

      Pros

      • Reduces tool sprawl.
      • Supports consistent tool stack.
      • Vendor support can make enhancement easier.
      • Total cost of ownership may be lower.

      Cons

      • Vendor Lock-In.
      • The processes to enhance may require tweaking to fit tool capability.

      Multi-Source Custom

      Single Source

      Integrate systems built in-house with technologies developed by external organizations.

      Buy an application/system from one vendor only.

      Pros

      • Flexibility in choice of tools.
      • In some cases, cost may be lower.
      • Easier to enhance with in-house teams.

      Cons

      • May introduce tool sprawl.
      • Requires resources to have strong technical skills
      • Some of the tools necessary may
      • not be compatible with each other.

      Pros

      • Reduces tool sprawl.
      • Supports consistent tool stack.
      • Vendor support can make enhancement easier.
      • Total cost of ownership may be lower.

      Cons

      • Vendor Lock-In.
      • The processes to enhance may require tweaking to fit tool capability.

      Weigh the pros and cons of mobile enablement versus development

      Mobile Enablement

      Mobile Development

      Description Mobile interfaces that heavily rely on enterprise or 3rd party systems to operate. Mobile does not expand the functionality of the system but complements it with enhanced access, input and consumption capabilities. Mobile applications that are custom built or configured in a way that can operate as a standalone entity, whether they are locally deployed to a user's device or virtually hosted.
      Mobile Platform Mobile web, locally installed mobile application provided by vendor Mobile web, hybrid, cross-platform, native
      Typical Audience Internal staff, trusted users Internal and external users, general public
      Examples of Tooling Flavors Enterprise applications, point solutions, robotic & process automation Mobile enterprise application platform, web development, low and no code development, software development kits (SDKs)
      Technical Skills Required Little to no mobile delivery experience and skillsets are needed, but teams must be familiar with the supporting system to understand how a mobile interface can improve the value of the system. Have good UX-driven and quality-first practices in the mobile context. In-depth coding, networking, system and UX design, data management and security skills are needed for complex designs, functions, and architectures.
      Architecture & Integration Architecture is standardized by the vendor or enterprise with UI elements that are often minimally configurable. Extensions and integrations must be done through the system rather than the mobile interface. Much of application stack and integration approach can be customized to meet the specific functional and non-functional needs. It should still leverage web and design standards and investments currently used.
      Functional Scope Functionality is limited to the what the underlying system allows the interface to do. This often is constrained to commodity web application features (e.g., reporting) or tied to minor configurations to the vendor-provided point solution Functionality is only constrained by the platform and the targeted mobile devices whether it is performance, integration, access or security related. Teams should consider feature and content parity across all products within the organization portfolio.
      Delivery Pipeline End-to-end delivery and automated pipeline is provided by the vendor to ensure parity across all interfaces. Many vendors provide cloud-based services for hosting. Otherwise, it is directly tied to the SDLC of the supporting system. End-to-end delivery and automated pipeline is directly tied to enterprise SDLC practices or through the vendor. Some vendors provide cloud-based services for hosting. Updates are manually or automatically (through a vendor) published to app stores and can be automatically pushed to corporate users through mobile application management capabilities.
      Standards & Guardrails Quality standards and technology governance are managed by the vendor or IT with limited capabilities to tailor them to be mobile specific. Quality standards and technology governance are managed by the mobile delivery teams. The degree of customizations to these standards and guardrails is dependent on the chosen platform and delivery team competencies.

      Understand the common attributes of a mobile delivery solution

      • Source Code Management – Built-in or having the ability to integrate with code management solutions for branching, merging, and versioning. Debugging and coding assistance capabilities may be available.
      • Single Code Base – Capable of programming in a standard coding and scripting language for deployment into several platforms and devices. This code base is aligned to a common industry framework (e.g., AngularJS, Java) or a vendor-defined one.
      • Out-of-the-Box Connectors & Plug-ins – Pre-built APIs enhance the solution's capabilities with 3rd party tools and systems to deliver and manage high quality and valuable mobile applications.
      • Emulators – Ability to virtualize an application's execution on a target platform and device.
      • Support for Native Features – Supports plug-ins and APIs for access to device-specific features.

      What are mobile delivery solutions?

      A mobile delivery solution gives you the tools, resources and support to enable or build your mobile application. They can provide pre-built applications, vendor supported components to allow some configurations, or resources for full stack customizations. Some solutions can be barebone software development kits (SDKs) or comprehensive suites offering features to support the entire software delivery lifecycle, such as:

      • Mobile application management
      • Testing and publishing to app stores
      • Content management
      • Cloud hosting
      • Application performance management

      Info-Tech Insight

      Mobile enablement and development capabilities are already embedded in many common productivity tools and enterprise applications, such as Microsoft PowerApps and ERP modules. They can serve as a starting point in the initial rollout of new management and governance practices without the need of acquiring new tools.

      Select your mobile delivery solutions

      1. Set the scope of your framework.
      • The initial context of this framework is based on the mobile functions needed to support your desired mobile experience and on the current state of your enterprise and 3rd party systems.
    • Define the decision factors for your solution selection.
      • Review the decision factors that will influence the selection of your mobile delivery solution for each mobile opportunity:
      • Stack Management – Who will be hosting and supporting your mobile application stack?
      • Workflows Complexity & Native Experience – How complex is your desired mobile experience and how will native device features be leveraged?
    • Select your solution type.
      • Mobile delivery solutions are broadly defined in the following groups:
      • Commercial-Off-The-Shelf (COTS) – Pre-built mobile applications requiring little to no configurations or implementation effort.
      • Vendor Hosted Mobile Platform – Back-end and mid-tier infrastructure and operational support are managed by a vendor.
      • Cross-Platform Development – Frameworks that transform a single code base into platform-specific builds.
      • Hybrid Development – Tools that wrap a single code base into a locally deployable build.
      • Custom Web Development – Environment enabling full stack development for mobile web applications.
      • Custom Native Development – Environment enabling full stack development for mobile native applications.
    • A quadrant analysis is depicted. the top data is labeled Complex Mobile Features; the right side is labeled Organization-Managed Stack; the bottom is labeled Simple Mobile Features; and the left side is labeled Vendor-Managed Stack. The quadrants are labeled the following, in order from left to right, top to bottom. Vendor- Hosted Mobile Platform; Custom Native Development Solutions; Commercial-Off-the-Shelf Solutions; Custom Web Development Solutions. In the middle of the graph are the following, in order from top to bottom: Cross-Platform Development Solutions; Hybrid Development Solutions

      Explore the various solution options

      Vendor Hosted Mobile Platform

      • Cloud Services (Mobile Backend-as-a-Service) (Amazon Amplify, Kinvey, Back4App, Google Firebase, Apache Usergrid)
      • Low Code Mobile Platforms (Outsystems, Mendix, Zoho Creator, IBM Mobile Foundation, Pega Mobile, HCL Volt MX, Appery)
      • Mobile Development via Enterprise Application (SalesForce Heroku, Oracle Application Accelerator MAX, SAP Mobile Development Kit, NetSuite Mobile)
      • Mobile Development via Business Process Automation (PowerApps, Appian, Nintex, Quickbase)

      Cross-Platform Development SDKs

      React Native, NativeScript, Xamarin Forms, .NET MAUI, Flutter, Kotlin Multiplatform Mobile, jQuery Mobile, Telerik, Temenos Quantum

      Custom Native Development Solutions

      • Native Development Languages and Environments (Swift, Java, Objective-C, Kotlin, Xcode, NetBeans, Android Studio, AppCode, Microsoft Visual Studio, Eclipse, DriodScript, Compose, Atom)
      • Mobile Application Utilities (Unity, MonoGame, Blender, 3ds Max Design, Maya, Unreal Engine, Amazon Lumberyard, Oculus)

      Commercial-Off-the-Shelf Solutions

      • No Code Mobile Platforms (Swiftic, Betty Blocks, BuildFire, Appy Pie, Plant an App, Microsoft Power Apps, AppSheet, Wix, Quixy)
      • Mobile Application Point Solutions and Enablement via Enterprise Applications

      Hybrid Development SDKs

      Cordova Project, Sencha Touch, Electron, Ionic, Capacitor, Monaca, Voltbuilder

      Custom Web Development Solutions

      Web Development Frameworks (React, Angular, Vue, Express, Django, Rails, Spring, Ember, Backbone, Bulma, Bootstrap, Tailwind CSS, Blade)

      Get the most out of your solutions by understanding their core components

      While most of the heavy lifting is handled by the vendor or framework, understanding how the mobile application is built and operates can identify where further fine-tuning is needed to increase its value and quality.

      Platform Runtime

      Automatic provisioning, configurations, and tuning of organizational and 3rd party infrastructure for high availability, performance, security and stability. This can include cloud management and non-production environments.

      Extensions

      • Mobile delivery solutions can be extended to allow:
      • Custom development of back-end code
      • Customizable integrations and hooks where needed
      • Integrations with CI/CD pipelines and administrative services
      • Integrations with existing databases and authentication services

      Platform Services

      The various services needed to support mobile delivery and enable continuous delivery, such as:

      • Configuration & Change Management – Verifies, validates, and monitors builds, deployments and changes across all components.
      • Code Generator – Transforms UI and data models into native application components that are ready to be deployed.
      • Deployment Services – Deploys application components consistently across all target environments and app stores.
      • Application Services – Manages the mobile application at runtime, including executing scheduled tasks and instrumentation.

      Application Architecture

      Fundamentally, mobile application architecture is no different than any other application architecture so much of your design standards still applies. The trick is tuning it to best meet your mobile functional and non-functional needs.

      This image contains an example of mobile application architecture.

      Source: "HCL Volt MX", HCL.

      Build your shortlist decision criteria

      The decision on which type of mobile delivery solution to use is dependent on several key questions?

      Who is the Mobile Delivery Team?

      • Is it a worker, business or IT?
      • What skills and knowledge does this person have?
      • Who is supporting mobile delivery and management?
      • Are other skills and tools needed to support, extend or mature mobile delivery adoption?

      What are the Use Cases?

      • What is the value and priority of the use cases?
      • What native features do we need?
      • Who is the audience of the output and who is impacted?
      • What systems, data and services do I need access?
      • Is it best to build it or buy it?
      • What are the quality standards?
      • How strategic is the use case?

      How Complex is the System?

      • Is the mobile application a standalone or integrated with enterprise systems?
      • What is the system's state and architecture?
      • What 3rd party services do we need integrated?
      • Are integrations out-of-the-box or custom?
      • Is the data standardized and who can edit its definition?
      • Is the system monolithic or loosely coupled?

      How Much Can We Tolerate?

      • Risks: What are the business and technical risks involved?
      • Costs: How much can we invest in implementation, training and operations?
      • Change: What organizational changes am I expecting to make? Will these changes be accepted and adopted?

      2.2.1 Shortlist your mobile delivery solution

      1-3 hours

      1. Determine which mobile delivery solutions is appropriate for each mobile opportunity or use case by answering the following questions on the following slides against two factors: complexity of mobile workflows and native features and management of the mobile stack.
        1. Take the average of the enterprise-centric and user-centric scores from step 2.1 for your complexity of mobile workflows and native features scores.
      2. Calculate an average score for the management of the mobile stack. Then, map them on the matrix to indicate possible solution options alongside your user-centric scores. Consider all options around the plotted point.
      3. Further discuss which solution should be the preferred choice and compare those options with your selected platform approach.
      4. Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Download the Mobile Application Delivery Communication Template

      Input

      Output
      • Current state assessment
      • Mobile platform approach
      • Shortlist of mobile delivery solution
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      2.2.1 cont'd

      Stack Management

      Factors Definitions Survey Responses
      Cost of Delayed Delivery The expected cost if a vendor solution or update is delayed. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Vendor Negotiation Organization's ability to negotiate favorable terms from vendors. 1 (High) – 2 – 3 (Moderate) – 4 – 5 (Low)
      Controllable Delivery Timeline Organization's desire to control when solutions and updates are delivered. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Solution Hosting The desired approach to host the mobile application. 1 (Fully Outsourced) – 2 – 3 (Partially Outsourced) – 4 – 5 (Internally Hosted)
      Vendor Lock-In The tolerance to be locked into a specific technology stack or vendor ecosystem. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Operational Cost Target The primary target of the mobile application's operational budget. 1 (External Resources) – 2 – 3 (Hybrid) – 4 – 5 (Internal Resources)
      Platform Management The desired approach to manage the mobile delivery solution, platform or underlying technology. 1 (Decentralized) – 2 – 3 (Federated) – 4 – 5 (Centralized)
      Skill & Competency of Mobile Delivery Team The ability of the team to create and manage valuable and high-quality mobile applications. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Current Investment in Enterprise Technologies The need to maximize the ROI of current enterprise technologies or integrate with legacy technologies. 1 (High) – 2 – 3 (Moderate) – 4 – 5 (Low)
      Ease of Extensibility Need to have out-of-the-box connectors and plug-ins to extend the mobile delivery solution beyond its base implementation. 1 (High) – 2 – 3 (Moderate) – 4 – 5 (Low)
      Holistic Application Strategy Organizational priorities on the types of applications the portfolio should be comprised. 1 (Buy) – 2 – 3 (Hybrid) – 4 – 5 (Build)
      Control of Delivery Pipeline The desire to control the software delivery pipeline from design to development, testing, publishing and support. 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)
      Specific Quality Requirements Software and mobile delivery is constrained to your unique quality standards (e.g., security, performance, availability) 1 (Low) – 2 – 3 (Moderate) – 4 – 5 (High)

      2.2.1 cont'd

      Example:

      Score Factors (Average) Mobile Opportunity 1: Inventory Management Mobile Opportunity 2: Remote Support
      User-Centric & Enterprise Centric Needs (From Step 2.1) 4.125 2.5
      Stack Management 2 2.5
      Desired Mobile Delivery Solution Vendor-Hosted Mobile Platform

      Commercial-Off-the-Shelf Solution

      Hybrid Development Solution

      A quadrant analysis is depicted. the top data is labeled Complex Mobile Features; the right side is labeled Organization-Managed Stack; the bottom is labeled Simple Mobile Features; and the left side is labeled Vendor-Managed Stack. The quadrants are labeled the following, in order from left to right, top to bottom. Vendor- Hosted Mobile Platform; Custom Native Development Solutions; Commercial-Off-the-Shelf Solutions; Custom Web Development Solutions. In the middle of the graph are the following, in order from top to bottom: Cross-Platform Development Solutions; Hybrid Development Solutions.

      Consider the following in your solution selection and implementation

      • Vendor lock in – Each solution has its own approach, frameworks, and data schemas to convert designs and logic into an executable build that is stable in the targeted environment. Consequently, moving application artifacts (e.g., code and designs) from one solution or environment to another may not be easily accomplished without significant modifications or the use of application modernization or migration services.
      • Conflicting priorities and viewpoints of good delivery practices – Mobile delivery solutions are very particular on how they generate applications from designs and configurations. The solution's approach may not accommodate your interpretation of high-quality code (e.g., scalability, maintainability, extensibility, security). Technical experts should be reviewing and refactoring the generated code.
      • Incompatibility with enterprise applications and systems – The true benefit of mobile delivery solutions is their ability to connect your mobile application to enterprise and 3rd party technologies and services. This capability often requires enterprise technologies and services to be architected in a way that is compatible with your delivery solution while ensuring data, security protocols and other standards and policies are consistently enforced.
      • Integration with current application development and management tools – Mobile delivery solutions should be extensions from your existing application development and management tools that provides the versioning, testing, monitoring, and deployment capabilities to sustain a valuable application portfolio. Without this integration, IT will be unable to:
        • Root cause issues found on IT dashboards or reported to help desk.
        • Rollback defective applications to a previous stable state.
        • Obtain a complete application portfolio inventory.
        • Execute comprehensive testing for high-risk applications.
        • Trace artifacts throughout the development lifecycle.
        • Generate reports of the status of releases.

      Enhance your SDLC to support mobile delivery

      What is the SDLC?

      The software development lifecycle (SDLC) is a process that ensures valuable software products are efficiently delivered to customers. It contains a repeatable set of activities needed to intake and analyze requirements to design, build, test, deploy, and maintain software products.

      How will mobile delivery influence my SDLC?

      • Cross-functional collaboration – Bringing business and IT together at the most opportune times to clarify user needs and business priorities, and set realistic expectations given technology and capacity constraints. The appropriate tactics and techniques are used to improve decision making and delivery effectiveness according to the type of work.
      • Iterative delivery – Frequent delivery of progressive changes minimizes the risk of low-quality features by containing and simplifying scope, and enables responsive turnarounds of fixes, enhancements, and priority changes.
      • Feedback loops –Mobile application owners constantly review, update and refine their backlog of mobile features and changes to reflect user feedback and system performance metrics. Delivery teams proactively prepare the application for future scaling based on lessons and feedback learned from earlier releases.

      To learn more, visit Info-Tech's Modernize Your SDLC blueprint.

      Example: Low- & No-Code Mobile Delivery Pipeline

      Low Code

      Data Modeling & Configuration

      No Code

      Visual Interface with Complex Data Models

      Data Modeling & Configuration

      Visual Interfaces with Simple Data Models

      GUI Designer with Customizable Components & Entities

      UI Definition & Design

      GUI Designer with Canned Templates

      Visual Workflow and Custom Scripting

      Business Logic Rules and Workflow Specification

      Visual Workflow and Natural Language Scripting

      Out-of-the-Box Plugins & Custom Integrations

      Integration of External Services (via 3rd Party APIs)

      Out-of-the-Box Plugins

      Automated and Manual Build & Packaging

      Build & Package

      Automated Build & Packaging

      Automated & Manual Testing

      Test

      Automated Testing

      One-Click Push or IT Push to App Store

      Publish to App Store

      One-Click Push to App Store

      Use Info-Tech's research to address your delivery gaps

      Mobile success requires more than a set of good tools.

      Overcome the Common Challenges Faced with Building Mobile Applications

      Common Challenges with Digital Applications

      Suggested Solutions

      • Time & Resource Constraints
      • Buy-In From Internal Stakeholders
      • Rapidly Changing Requirements
      • Legacy Systems
      • Low-Priority for Internal Tools
      • Insufficient Data Access

      Source: DronaHQ, 2021

      Learn the differentiators of mobile delivery solutions

      • Native Program Languages – Supports languages other than web (Java, Ruby, C/C++/C#, Objective-C).
      • IDE Integration – Available plug-ins for popular development suites and editors.
      • Debugging Tools – Finding and eliminating bugs (breakpoints, single stepping, variable inspection, etc.).
      • Application Packaging via IDE – Digitally sign applications through the IDE for it to be packaged and published in app stores.
      • Automated Testing Tools – Native or integration with automated functional and unit testing tools.
      • Low- and No- Code Designer – Tools for designing graphical user interfaces and features and managing data with drag-and-drop functionalities.
      • Publishing and Deployment Capabilities – Automated deployment to mobile device management (MDM) systems, mobile application management (MAM) systems, mobile application stores, and web servers.
      • Third-Party and Open-Source Integration – Integration with proprietary and open-source third-party modules, development tools, and systems.
      • Developer Marketplace – Out-of-the-box plug-ins, templates, and integration are available through a marketplace.
      • Mobile Application Support Capabilities – Ability to gather, manage, and address application issues and defects.
      • API Gateway, Monitoring, and Management – Services that enable the creation, publishing, maintenance, monitoring, and securing of APIs through a common interface.
      • Mobile Analytics and Monitoring – View the adoption, usage, and performance of deployed mobile applications through graphical dashboards.
      • Mobile Content Management – Publish and manage mobile content through a centralized system.
      • Mobile Application Security – Supports the securing of application access and usage, data encryption, and testing of security controls.

      Define your mobile delivery vendor selection criteria

      Focus on the key vendor attributes and capabilities that enable mobile delivery scaling and growth in your organization

      Considerations in Mobile Delivery Vendor Selection
      Platform Features & Capabilities Price to Implement & Operate Platform
      Types of Mobile Applications That Can Be Developed Ease of IT Administration & Management
      User Community & Marketplace Size Security, Privacy & Access Control Capabilities
      SME in Industry Verticals & Business Functions Vendor Product Roadmap & Corporate Strategy
      Pre-Built Designs, Templates & Application Shells Scope of Device- and OS-Specific Compatibilities
      Regulatory & Industry Compliance Integration & Technology Partners
      Importing Artifacts From and Exporting to Other Solutions Platform Architecture & Underlying Technology
      End-to-End Support for the Entire Mobile SDLC Relevance to Current Mobile Trends & Practices

      Build your features list

      Incorporate different perspectives when defining the list of mandatory and desired features of your target solution.

      Appendix B contains a list of features for low- and no-code solutions that can be used as a starting point.

      Visit Info-Tech's Implement a Proactive and Consistent Vendor Selection Process blueprint.

      Mobile Developer

      • Visual, drag-and-drop models to define data models, business logic, and user interfaces.
      • One-click deployment.
      • Self-healing capabilities.
      • Vendor-managed infrastructure.
      • Active community and marketplace.
      • Pre-built templates and libraries.
      • Optical character recognition and natural language processing.
      • Knowledgebase and document management.
      • Business value, operational costs, and other KPI monitoring.
      • Business workflow automation.

      Mobile IT Professional

      • Audit and change logs.
      • Theme and template builder.
      • Template management.
      • Role-based access.
      • Regulatory compliance.
      • Consistent design and user experience across applications.
      • Application and system performance monitoring.
      • Versioning and code management.
      • Automatic application and system refactoring and recovery.
      • Exception and error handling.
      • Scalability (e.g. load balancing) and infrastructure management.
      • Real-time debugging.
      • Testing capabilities.
      • Security management.
      • Application integration management.

      2.2.2 Build your feature and service lists

      1-3 hours

      Review the key outcomes in the previous exercises to help inform the features and vendor support you require to support your mobile delivery needs:

      End user personas and desired mobile experience

      Objectives and expectations

      Desired mobile features and platform

      Mobile delivery solutions

      Brainstorm a list of features and functionalities you require from your ideal solution vendors. Prioritize these features and functionalities. See our Implement a Proactive and Consistent Vendor Selection Process blueprint for more information on vendor procurement.

      Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Download the Mobile Application Delivery Communication Template

      Input

      Output
      • Shortlist of mobile solutions
      • Quality definitions
      • Mobile objectives and metrics
      • List of desired features and services of mobile delivery solution vendors
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      Hit a home run with your stakeholders

      Use a data-driven approach to select the right tooling vendor for your needs – fast.

      AwarenessEducation & DiscoveryEvaluationSelection

      Negotiation & Configuration

      1.1 Proactively Lead Technology Optimization & Prioritization2.1 Understand Marketplace Capabilities & Trends3.1 Gather & Prioritize Requirements & Establish Key Success Metrics4.1 Create a Weighted Selection Decision Model5.1 Initiate Price Negotiation with Top Two Venders
      1.2 Scope & Define the Selection Process for Each Selection Request Action2.2 Discover Alternate Solutions & Conduct Market Education3.2 Conduct a Data Driven Comparison of Vendor Features & Capabilities4.2 Conduct Investigative Interviews Focused on Mission Critical Priorities with Top 2-4 Vendors5.2 Negotiate Contract Terms & Product Configuration

      1.3 Conduct an Accelerated Business Needs Assessment

      2.3 Evaluate Enterprise Architecture & Application PortfolioNarrow the Field to Four Top Contenders4.3 Validate Key Issues with Deep Technical Assessments, Trial Configuration & Reference Checks5.3 Finalize Budget Approval & Project
      1.4 Align Stakeholder Calendars to Reduce Elapsed Time & Asynchronous Evaluation2.4 Validate the Business Case5.4 Invest in Training & Onboarding Assistance

      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. Info-Tech's Rapid Application Selection Framework approach is best for commodity and mid-tier enterprise applications; selecting complex applications is better handled by the methodology in Info-Tech's Implement a Proactive and Consistent Vendor Selection Process.

      Step 2.3

      Create a Roadmap for Mobile Delivery

      Activities

      2.3.1 Define your MVP release

      2.3.2 Build your roadmap

      Define Your Mobile Approach

      This step involves the following participants:

      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      Outcomes of this step

      • MVP design
      • Mobile delivery roadmap

      Achieve mobile success with MVPs

      By delivering mobile capabilities in small iterations, teams recognize value sooner and reduce accumulated risk. Both benefits are realized as the iteration enters validation testing and release.

      This image depicts a graph of the learn-build-measure cycle over time, adapted from Managing the Development of Large Software Systems, Dr. Winston W. Royce, 1970

      An MVP focuses on a small set of functions, involves minimal possible effort to deliver a working and valuable solution, and is designed to satisfy a specific user group. Its purpose is to:

      • Maximize learning.
      • Evaluate the value and acceptance of mobile applications.
      • Inform the building of a mobile delivery practice.

      The build-measure-learn loop suggests mobile delivery teams should perpetually take an idea and develop, test, and validate it with the mobile development solution, then expand on the MVP using the lessons learned and evolving ideas. In this sense the MVP is just the first iteration in the loop.

      Leverage a canvas to detail your MVP

      Use the release canvas to organize and align the organization around your MVP!

      This is an example of a release canvas which can be used to detail your MVP.

      2.3.1 Define your MVP release

      1-3 hours

      1. Create a list of high priority use cases slated for mobile application delivery. Brainstorm the various supporting activities required to implement your use cases including the shortlisting of mobile delivery tools.
      2. Prioritize these use cases based on business priority (from your canvas). Size the effort of these use cases through collaboration.
      3. Define your MVPs using a release canvas as shown on the following slide.
      4. Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Input

      Output
      • High priority mobile opportunities
      • Mobile platform approach
      • Shortlist of mobile solutions
      • List of potential MVPs
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      2.3.1 cont'd

      MVP Name

      Owner:
      Parent Initiative:
      Updated:

      NAME
      LINK
      October 05, 2022

      MVP Theme/Goals

      [Theme / Goal]

      Use Cases

      Value

      Costs

      [Use Case 1]
      [Use Case 2]
      [Use Case 3]

      [Business Value 1]
      [Business Value 2]
      [Business Value 3]

      [Cost Item 1]
      [Cost Item 2]
      [Cost Item 3]

      Impacted Personas

      Impacted Workflows

      Stakeholders

      [Persona 1]
      [Persona 2]
      [Persona 3]

      [Workflow 1]
      [Workflow 2]
      [Workflow 3]

      [Stakeholder 1]
      [Stakeholder 2]
      [Stakeholder 3]

      Build your mobile roadmap

      It's more than a set of colorful boxes. It's the map to align everyone to where you are going

      Your mobile roadmap

      • Lays out a strategy for your mobile application, platform and practice implementation and scaling.
      • Is a statement of intent for your mobile adoption.
      • Communicates direction for the implementation and use of mobile delivery tools, mobile applications and supporting technologies.
      • Directly connects to the organization's goals

      However, it is not:

      • Representative of a hard commitment.
      • A simple combination of your current product roadmaps

      Roadmap your MVPs against your milestones and release dates

      This is an image of an example of a roadmap for your MVPS, with milestones across Jan 2022, Feb 2022, Mar 2022, Apr 2022. under milestones, are the following points: Points in the timeline when an established set of artifacts is complete (feature-based), or to check status at a particular point in time (time-based); Typically assigned a date and used to show progress; Plays an important role when sequencing different types of artifacts. Under Release Dates are the following points: Releases mark the actual delivery of a set of artifacts packaged together in a new version of processes and applications or new mobile application and delivery capabilities. ; Release dates, firm or not, allow stakeholders to anticipate when this is coming.

      To learn more, visit Info-Tech's Deliver on Your Digital Product Vision blueprint.

      Understand what is communicated in your roadmap

      WHY is the work being done?

      Explains the overarching goal of work being done to a specific audience.

      WHO is doing the work?

      Categorizes the different groups delivering the work on the product.

      WHAT is the work being done?

      Explains the artifacts, or items of work, that will be delivered.

      WHEN is the work being done?

      Explains when the work will be delivered within your timeline.

      To learn more, visit Info-Tech's Deliver on Your Digital Product Vision blueprint.

      Pay attention to organizational changes

      Be prepared to answer:

      "How will mobile change the way I do my job?"

      • Plan how workers will incorporate mobile applications into their way of working and maximize the features it offers.
      • Address the human concerns regarding the transition to a digital world involving modern and mobile technologies and automation.
      • Accept changes, challenges and failures with open arms and instill tactics to quickly address them.
      • Build and strengthen business-IT trust, empowerment, and collaborative culture by adopting the right practices throughout the mobile delivery process.
      • Ensure continuous management and leadership support for business empowerment, operational changes, and shifts in role definitions to best support mobile delivery.
      • Establish a committee to manage the growth, adoption, and delivery of mobile as part of a grandeur digital application portfolio and address conflicts among business units and IT.

      Anticipate and prepare for changes and issues

      Verify and validate the flexibility and adaptability of your mobile applications, strategy and roadmap against various scenarios

      • Scenarios
        • Application Stores Rejecting the Application
        • Security Incidents & Risks
        • Low User Adoption, Retention & Satisfaction
        • Incompatibility with User's Device & Other Systems
        • Device & OS Patches & Updates
        • Changes in Industry Standards & Regulations

      Use the "Now, Next, Later" roadmap

      Use this when deadlines and delivery dates are not strict. This is best suited for brainstorming a product plan when dependency mapping is not required.

      Now

      What are you going to do now?

      Next

      What are you going to do very soon?

      Later

      What are you going to do in the future?

      This is a roadmap showing various points in the following categories: Now; Next; Later

      Adapted From: "Tips for Agile product roadmaps & product roadmap examples," Scrum.org, 2017

      2.3.2 Build your roadmap

      1-3 hours

      1. Identify the business outcomes your mobile application delivery and MVP is expected to deliver.
      2. Build your strategic roadmap by grouping each business outcome by how soon you need to deliver it:
        1. Now: Let's achieve this ASAP.
        2. Next: Sometime very soon, let's achieve these things.
        3. Later: Much further off in the distance, let's consider these things.
      3. Identify what the critical steps are for the organization to embrace mobile application delivery and deliver your MVP.
      4. Build your tactical roadmap by grouping each critical step by how soon you need to address it:
        1. Now: Let's do this ASAP.
        2. Next: Sometime very soon, let's do these things.
        3. Later: Much further off in the distance, let's consider these things.
      5. Document your findings and discussions into Info-Tech's Mobile Application Delivery Communication Template.

      Input

      Output
      • List of potential MVPs
      • Mobile roadmap
      MaterialsParticipants
      • Whiteboard/Flip Charts
      • Mobile Application Delivery Communication Template
      • Applications Manager
      • Product and Platform Owners
      • Software Delivery Teams
      • Business and IT Leaders

      2.3.2 cont'd

      Example: Tactical Roadmap

      Milestone 1

      • Modify the business processes of the MVP to best leverage mobile technologies. Streamline the business processes by removing the steps that do not directly support value delivery.
      • Develop UI templates using the material design framework and the organization's design standards. Ensure it is supported on mobile devices through the mobile browser and satisfy accessibility design standards.
      • Verify and validate current security controls against latest security risks using the W3C as a starting point. Install the latest security patches to maintain compliance.
      • Acquire the Ionic SDK and upskill delivery teams.

      Milestone 2

      • Update the current web framework and third-party libraries with the latest version and align web infrastructure to latest W3C guidelines.
      • Verify and validate functionality and stability of APIs with third-party applications. Begin transition to REST APIs where possible.
      • Make minor changes to the existing data architecture to better support the data volume, velocity, variety, and veracity the system will process and deliver.
      • Update the master data management with latest changes. Keep changes to a minimum.
      • Develop and deliver the first iteration of the MVP with Ionic.

      Milestone 3

      • Standardize the initial mobile delivery practice.
      • Continuously monitor the system and proactively address business continuity, system stability and performance, and security risks.
      • Deliver a hands-on and facilitated training session to end users.
      • Develop intuitive user manuals that are easily accessible on SharePoint.
      • Consult end users for their views and perspectives of suggested business model and technology changes.
      • Regularly survey end users and the media to gauge industry sentiment toward the organization.

      Pitch your roadmap initiatives

      There are multiple audiences for your pitch, and each audience requires a different level of detail when addressed. Depending on the outcomes expected from each audience, a suitable approach must be chosen. The format and information presented will vary significantly from group to group.

      Audience

      Key Contents

      Outcome

      Outcome

      • Costs or benefits estimates

      Sign off on cost and benefit projections

      Executives and decision makers

      • Business value and financial benefits
      • Notable business risks and impacts
      • Business rationale and strategic roadmap

      Revisions, edits, and approval

      IT teams

      • Notable technical and IT risks
      • IT rationale and tactical roadmap
      • Proposed resourcing and skills capacity

      Clarity of vision and direction and readiness for delivery

      Business workers

      • Business rationale
      • Proposed business operations changes
      • Application roadmap

      Verification on proposed changes and feedback

      Continuously measure the benefits and value realized in your mobile applications

      Success hinges on your team's ability to deliver business value. Well-developed mobile applications instill stakeholder confidence in ongoing business value delivery and stakeholder buy-in, provided proper expectations are set and met.

      Business value defines the success criteria of an organization, and it is interpreted from four perspectives:

      • Profit Generation – The revenue generated from a business capability with mobile applications.
      • Cost Reduction – The cost reduction when performing business capabilities with mobile applications.
      • Service Enablement – The productivity and efficiency gains of internal business operations with mobile applications.
      • Customer and Market Reach – Metrics measuring the improved reach and insights of the business in existing or new markets.

      See our Build a Value Measurement Framework blueprint for more information about business value definition.

      Business Value Matrix

      This image contains a quadrant analysis with the following labels: Left - Improved Capabilities; Top - Outward; Right - Financial Benefit; Bottom - Inward. the quadrants are labeled the following, in order from left to right, top to bottom. Customer and Market Reach; Profit Generation; Service Enhancement; Cost Reduction

      Grow your mobile delivery practice

      We are Here
      Level 1: Mobile Delivery Foundations Level 2: Scaled Mobile Delivery Level 3: Leading-Edge Mobile Delivery

      You understand the opportunities and impacts mobile has on your business operations and its disruptive nature on your enterprise systems. Your software delivery lifecycle was optimized to incorporate the specific practices and requirements needed for mobile. A mobile platform was selected based on stakeholder needs that are weighed against current skillsets, high priority non-functional requirements, the available capacity and scalability of your stack, and alignment to your current delivery process.

      New features and mobile use cases are regularly emerging in the industry. Ensuring your mobile platform and delivery process can easily scale to incorporate constantly changing mobile features and technologies is key. This can help minimize the impact these changes will have on your mobile stack and the resulting experience.

      Achieving this state requires three competencies: mobile security, performance optimization, and integration practices.

      Many of today's mobile trends involve, in one form or another, hardware components on the mobile device (e.g., NFC receivers, GPS, cameras). You understand the scope of native features available on your end user's mobile device and the required steps and capabilities to enable and leverage them.

      Grow your mobile delivery practice (cont'd)

      Ask yourself the following questions:
      Level 1: Mobile Delivery Foundations Level 2: Scaled Mobile Delivery Level 3: Leading-Edge Mobile Delivery

      Checkpoint questions shown at the end of step 1.2 of this blueprint

      You should be at this point upon the successful delivery of your first mobile application.

      Security

      • Your mobile stack (application, data, and infrastructure) is updated to incorporate the security risks mobile apps will have on your systems and business operations.
      • Leading edge encryption, authentication management (e.g., multi-factor), and access control systems are used to bolster existing mobile security infrastructure.
      • Network traffic to and from mobile application is monitored and analyzed.

      Performance Optimization

      • Performance enhancements are made with the entire mobile stack in mind.
      • Mobile performance is monitored and assessed with both proactive (data flow) and retroactive (instrumentation) approaches.
      • Development and testing practices and technologies accommodate the performance differences between mobile and desktop applications.

      API Development

      • Existing web APIs are compatible with mobile applications, or a gateway / middleware is used to facilitate communication with backend and third-party services.
      • APIs are secured to prevent unauthorized access and misuse.
      • Web APIs are documented and standardized for reuse in multiple mobile applications.
      • Implementing APIs of native features in native and/or cross-platform and/or hybrid platforms is well understood.
      • All leading-edge mobile features are mapped to and support business requirements and objectives.
      • The new mobile use cases are well understood and account for the various scenarios/environments a user may encounter with the leading-edge mobile features.
      • The relevant non-mobile devices, readers, sensors, and other dependent systems are shortlisted and acquired to enable and support your new mobile capabilities.
      • Delivery teams are prepared to accommodate the various security, performance, and integration risks associated with implementing leading-edge mobile features. Practices and mechanisms are established to minimize the impact to business operations.
      • Metrics are used to measure the success of your leading-edge mobile features implementation by comparing its performance and acceptance against past projects.
      • Business stakeholders and development teams are up to date with the latest mobile technologies and delivery techniques.

      Summary of Accomplishment

      Choose Your Mobile Platform and Tools

      • User personas
      • Mobile objectives and metrics
      • Mobile opportunity backlog
      • List of mobile features to enable the desired mobile experience
      • System current assessment
      • Mobile application quality definition
      • Readiness for mobile delivery
      • Desired mobile platform approach
      • Shortlisted mobile delivery solutions
      • Desired list of vendor features and services
      • MVP design
      • Mobile delivery roadmap

      If you would like additional support, have our analysts guide you through other phases as part of Info-Tech workshop.

      Contact your account representative for more information

      workshops@infotech.com

      1-888-670-8889

      Research Contributors and Experts

      This is a picture of Chaim Yudkowsky, Chief Information Officer for The American Israel Public Affairs Committee

      Chaim Yudkowsky
      Chief Information Officer
      The American Israel Public Affairs Committee

      Chaim Yudkowsky is currently Chief information Officer for American Israel Public Affairs Committee (AIPAC), the DC headquartered not-for-profit focused on lobbying for a strong US-Israel relationship. In that role, Chaim is responsible for all traditional IT functions including oversight of IT strategy, vendor relationships, and cybersecurity program. In addition, Chaim also has primary responsibility for all physical security technology and strategy for US offices and event technology for the many AIPAC events.

      Bibliography

      "5 Pillars of API Management". Broadcom, 2021. Web.

      Bourne, James. "Apperian research shows more firms pushing larger numbers of enterprise apps". Enterprise CIO, 17 Feb 2016. Web.

      Ceci, L. "Mobile app user retention rate worldwide 2020, by vertical". Statista, 6 Apr 2022. Web.

      Clement, J. "Share of global mobile website traffic 2015-2021". Statista, 18 Feb 2022. Web

      DeVos, Jordan. "Design Problem Statements – What They Are and How to Frame Them." Toptal, n.d. Web.

      Enge, Eric. "Mobile vs. Desktop Usage in 2020". Perficient, 23 March 2021. Web.

      Engels, Antoine. "How many Android updates does Samsung, Xiaomi or OnePlus offer?" NextPit, Mar 2022. Web.

      "Fast-tracking digital transformation through next-gen technologies". Broadridge, 2022. Web.

      Gayatri. "The Pulse of Digital Transformation 2021 – Survey Results." DronaHQ, 2021. Web.

      Gray, Dave. "Updated Empathy Map Canvas." The XPLANE Collection, 15 July 2017. Web.

      "HCL Volt MX". HCL, n.d. Web.

      "iPass Mobile Professional Report 2017". iPass, 2017. Web.

      Karlsson, Johan. "Backlog Grooming: Must-Know Tips for High-Value Products." Perforce, 2019. Web.

      Karnes, KC. "Why Users Uninstall Apps: 28% of People Feel Spammed [Survey]". CleverTap, 27 July 2021. Web.

      Kemp, Simon. "Digital 2021: Global Overview Report". DataReportal, 27 Jan 2021. Web.

      Kleinberg, Sara. "Consumers are always shopping and eager for your help". Google, Aug 2018. Web.

      MaLavolta, Ivano. "Anatomy of an HTML 5 mobile web app". University of L'Aquila, 16 Apr 2012. Web.

      "Maximizing Mobile Value: To BYOD or not to BYOD?" Samsung and Oxford Economics, 2022. Web.

      "Mobile App Performance Metrics For Crash-Free Apps." AppSamurai, 27 June 2018. Web.

      "Mobile Application Development Statistics: 5 Facts". Intersog, 23 Nov 2021. Web.

      Moore, Geoffrey A. "Crossing the Chasm, 3rd Edition: Marketing and Selling Disruptive Products to Mainstream Customers." Harper Business, 3rd edition, 2014. Book.

      "OWASP Top Ten". OWASP, 2021. Web.

      "Personas". Usability.gov, n.d. Web.

      Roden, Marky. "PSC Tech Talk: UX Design – Not just making things pretty". Xomino, 18 Mar 2018. Web.

      Royce, Dr. Winston W. "Managing the Development of Large Software Systems." USC Student Computing Facility, 1970. Web.

      Rubin, Kenneth S. Essential Scrum: A Practical Guide to the Most Popular Agile Process. Pearson Education, 2012. Book.

      Sahay, Apurvanand et al. "Supporting the understanding and comparison of low-code development platforms." Universit`a degli Studi dell'Aquila, 2020. Web.

      Schuurman, Robbin. "Tips for Agile product roadmaps & product roadmap examples." Scrum.org, 2017. Web.

      Strunk, Christian. "How to define a product vision (with examples)." Christian Strunk. n.d. Web.

      Szeja, Radoslaw. "14 Biggest Challenges in Mobile App Development in 2022". Netguru, 4 Jan 2022. Web.

      "Synopsys Research Reveals Significant Security Concerns in Popular Mobile Apps Amid Pandemic". Synopsys, 25 Mar 2021. Web.

      "TOGAF 8.1.1 Online, Part IV: Resource Base, Developing Architecture Views." The Open Group, n.d. Web.

      Wangen, Emilie Nøss. "What Is a Software Platform & How Is It Different From a Product?" HubSpot, 2021. Web.

      "Mobile App Retention Rate: What's a Good Retention Rate?" Localytics, July 2021. Web.

      "Why Mobile Apps Fail: Failure to Launch". Perfecto Mobile, 26 Jan 2014. Web.

      Appendix A

      Sample Reference Frameworks

      Reference Framework: Web Platform

      Most of the operations of the applications on a web platform are executed in the mid-tier or back-end servers. End users interact with the platform through the presentation layer, developed with web languages, in the browser.

      This is an image of the Reference Framework: Web Platform

      Reference Framework: Mobile Web Application

      Many mobile web applications are composed of JavaScript (the muscle of the app), HTML5 (the backbone of the app), and CSS (the aesthetics of the app). The user will make a request to the web server which will interact with the application to provide a response. Since each device has unique attributes, consider a device detection service to help adjust content for each type of device.

      this is an image of the Reference Framework: Mobile Web Application

      Source: MaLavolta, Ivono, 2012.

      Web Platform: Anatomy of a Web Server

      Web Server Services

      • Mediation Services: Perform transformation of data/messages.
      • Boundary Services: Provide interface protocol and data/message conversion capabilities.
      • Event Distribution: Provides for the enterprise-wide adoption of content and topic-based publish/subscribe event distribution.
      • Transport Services: Facilitate data transmission across the middleware/server.
      • Service Directory: Manages multiple service identifiers and locations.

      This image shows the relationships of the various web server services listed above

      Reference Framework: Hybrid Platform

      Unlike the mobile web platform, most of an application's operations on the hybrid platform is on the device within a native container. The container leverages the device browser's runtime engine and is based on the framework of the mobile delivery solution.

      This is an image of the Reference Framework: Hybrid Platform

      Reference Framework: Native Platform

      Applications on a native platform are installed locally on the device giving it access to native device hardware and software. The programming language depends on the operating system's or device's SDK.

      This is an image of the Reference Framework: Native Platform

      Appendix B

      List of Low- and No- Code Software Delivery Solution Features

      Supplementary List of Features

      Graphical user interface

      • Drag-and-drop designer - This feature enhances the user experience by permitting to drag all the items involved in making an app including actions, responses, connections, etc.
      • Point and click approach - This is similar to the drag-and-drop feature except it involves pointing on the item and clicking on the interface rather than dragging and dropping the item.
      • Pre-built forms/reports - This is off-the-shelf and most common reusable editable forms or reports that a user can use when developing an application.
      • Pre-built dashboards - This is off-the-shelf and most common dashboards that a user can use when developing an application.
      • Forms - This feature helps in creating a better user interface and user experience when developing applications. A form includes dashboards, custom forms, surveys, checklists, etc. which could be useful to enhance the usability of the application being developed.
      • Progress tracking - This features helps collaborators to combine their work and track the development progress of the application.
      • Advanced Reporting - This features enables the user to obtain a graphical reporting of the application usage. The graphical reporting includes graphs, tables, charts, etc.
      • Built-in workflows - This feature helps to concentrate the most common reusable workflows when creating applications.
      • Configurable workflows - Besides built-in workflows, the user should be able to customize workflows according to their needs.

      Interoperability support

      • Interoperability with external services - This feature is one of the most important features to incorporate different services and platforms including that of Microsoft, Google, etc. It also includes the interoperability possibilities among different low-code platforms.
      • Connection with data sources - This features connects the application with data sources such as Microsoft Excel, Access and other relational databases such as Microsoft SQL, Azure and other non-relational databases such as MongoDB.

      Security Support

      • Application security - This feature enables the security mechanism of an application which involves confidentiality, integrity and availability of an application, if and when required.
      • Platform security - The security and roles management is a key part in developing an application so that the confidentiality, integrity and authentication (CIA) can be ensured at the platform level.

      Collaborative development support

      • Off-line collaboration - Different developers can collaborate on the specification of the same application. They work off-line locally and then they commit to a remote server their changes, which need to be properly merged.
      • On-line collaboration - Different developers collaborate concurrently on the specification of the same application. Conflicts are managed at run-time.

      Reusability support

      • Built-in workflows - This feature helps to concentrate the most common reusable workflows in creating an application.
      • Pre-built forms/reports - This is off-the-shelf and most common reusable editable forms or reports that a user might want to employ when developing an application.
      • Pre-built dashboards - This is off-the-shelf and most common dashboards that a user might want to employ when developing an application.

      Scalability

      • Scalability on number of users - This features enables the application to scale-up with respect to the number of active users that are using that application at the same time.
      • Scalability on data traffic - This features enables the application to scale-up with respect to the volume of data traffic that are allowed by that application in a particular time.
      • Scalability on data storage - This features enables the application to scale-up with respect to the data storage capacity of that application.

      Business logic specification mechanisms

      • Business rules engine - This feature helps in executing one or more business rules that help in managing data according to user's requirements.
      • Graphical workflow editor - This feature helps to specify one or more business rules in a graphical manner.
      • AI enabled business logic - This is an important feature which uses Artificial Intelligence in learning the behavior of an attributes and replicate those behaviors according to learning mechanisms.

      Application build mechanisms

      • Code generation - According to this feature, the source code of the modeled application is generated and subsequently deployed before its execution.
      • Models at run-time - The model of the specified application is interpreted and used at run-time during the execution of the modeled application without performing any code generation phase.

      Deployment support

      • Deployment on cloud - This features enables an application to be deployed online in a cloud infrastructure when the application is ready to deployed and used.
      • Deployment on local infrastructures - This features enables an application to be deployed locally on the user organization's infrastructure when the application is ready to be deployed and used.

      Kinds of supported applications

      • Event monitoring - This kind of applications involves the process of collecting data, analyzing the event that can be caused by the data, and signaling any events occurring on the data to the user.
      • Process automation - This kind of applications focuses on automating complex processes, such as workflows, which can take place with minimal human intervention.
      • Approval process control - This kind of applications consists of processes of creating and managing work approvals depending on the authorization of the user. For example, payment tasks should be managed by the approval of authorized personnel only.
      • Escalation management - This kind of applications are in the domain of customer service and focuses on the management of user viewpoints that filter out aspects that are not under the user competences.
      • Inventory management - This kind of applications is for monitoring the inflow and outflow of goods and manages the right amount of goods to be stored.
      • Quality management - This kind of applications is for managing the quality of software projects, e.g., by focusing on planning, assurance, control and improvements of quality factors.
      • Workflow management - This kind of applications is defined as sequences of tasks to be performed and monitored during their execution, e.g., to check the performance and correctness of the overall workflow.

      Source: Sahay, Apurvanand et al., 2020

      Leverage Big Data by Starting Small

      • Buy Link or Shortcode: {j2store}201|cart{/j2store}
      • member rating overall impact: 7.0/10 Overall Impact
      • member rating average dollars saved: 3 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: Big Data
      • Parent Category Link: /big-data
      • The desire for rapid decision making is increasing and the complexity of data sources is growing; business users want access to several new data sources, but in a way that is controlled and easily consumable.
      • Organizations may understand the transformative potential of a big data initiative, but struggle to make the transition from the awareness of its importance to identifying a concrete use case for a pilot project.
      • The big data ecosystem is crowded and confusing, and a lack of understanding of that ecosystem may cause a paralysis for organizations.

      Our Advice

      Critical Insight

      • Big data is simply data. With technological advances, what was once considered big data is now more approachable for all organizations irrespective of size.
      • The variety element is the key to unlocking big data value. Drill down into your specific use cases more effectively by focusing on what kind of data you should use.
      • Big data is about deep analytics. Deep doesn’t mean difficult. Visualization of data, integrating new data, and understanding associations are ways to deepen your analytics.

      Impact and Result

      • Establish a foundational understanding of what big data entails and what the implications of its different elements are for your organization.
      • Confirm your current maturity for taking on a big data initiative, and make considerations for core data management practices in the context of incorporating big data.
      • Avoid boiling the ocean by pinpointing use cases by industry and functional unit, followed by identifying the most essential data sources and elements that will enable the initiative.
      • Leverage a repeatable pilot project framework to build out a successful first initiative and implement future projects en-route to evolving a big data program.

      Leverage Big Data by Starting Small Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should leverage big data, 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. Undergo big data education

      Build a foundational understanding of the current big data landscape.

      • Leverage Big Data by Starting Small – Phase 1: Undergo Big Data Education

      2. Assess big data readiness

      Appraise current capabilities for handling a big data initiative and revisit the key data management practices that will enable big data success.

      • Leverage Big Data by Starting Small – Phase 2: Assess Big Data Readiness
      • Big Data Maturity Assessment Tool

      3. Pinpoint a killer big data use case

      Armed with Info-Tech’s variety dimension framework, identify the top use cases and the data sources/elements that will power the initiative.

      • Leverage Big Data by Starting Small – Phase 3: Pinpoint a Killer Big Data Use Case
      • Big Data Use-Case Suggestion Tool

      4. Structure a big data proof-of-concept project

      Leverage a repeatable framework to detail the core components of the pilot project.

      • Leverage Big Data by Starting Small – Phase 4: Structure a Big Data Proof-of-Concept Project
      • Big Data Work Breakdown Structure Template
      • Data Scientist
      • Big Data Cost/Benefit Tool
      • Big Data Stakeholder Presentation Template
      • Big Data Communication Tracking Template
      [infographic]

      Workshop: Leverage Big Data by Starting Small

      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 Undergo Big Data Education

      The Purpose

      Understand the basic elements of big data and its relationship to traditional business intelligence.

      Key Benefits Achieved

      Common, foundational knowledge of what big data entails.

      Activities

      1.1 Determine which of the four Vs is most important to your organization.

      1.2 Explore new data through a social lens.

      1.3 Brainstorm new opportunities for enhancing current reporting assets with big data sources.

      Outputs

      Relative importance of the four Vs from IT and business perspectives

      High-level improvement ideas to report artifacts using new data sources

      2 Assess Your Big Data Readiness

      The Purpose

      Establish an understanding of current maturity for taking on big data, as well as revisiting essential data management practices.

      Key Benefits Achieved

      Concrete idea of current capabilities.

      Recommended actions for developing big data maturity.

      Activities

      2.1 Determine your organization’s current big data maturity level.

      2.2 Plan for big data management.

      Outputs

      Established current state maturity

      Foundational understanding of data management practices in the context of a big data initiative

      3 Pinpoint Your Killer Big Data Use Case

      The Purpose

      Explore a plethora of potential use cases at the industry and business unit level, followed by using the variety element of big data to identify the highest value initiative(s) within your organization.

      Key Benefits Achieved

      In-depth characterization of a pilot big data initiative that is thoroughly informed by the business context.

      Activities

      3.1 Identify big data use cases at the industry and/or departmental levels.

      3.2 Conduct big data brainstorming sessions in collaboration with business stakeholders to refine use cases.

      3.3 Revisit the variety dimension framework to scope your big data initiative in further detail.

      3.4 Create an organizational 4-column data flow model with your big data sources/elements.

      3.5 Evaluate data sources by considering business value and risk.

      3.6 Perform a value-effort assessment to prioritize your initiatives.

      Outputs

      Potential big data use cases

      Potential initiatives rooted in the business context and identification of valuable data sources

      Identification of specific data sources and data elements

      Characterization of data sources/elements by value and risk

      Prioritization of big data use cases

      4 Structure a Big Data Proof-of-Concept Project

      The Purpose

      Put together the core components of the pilot project and set the stage for enterprise-wide support.

      Key Benefits Achieved

      A repeatable framework for implementing subsequent big data initiatives.

      Activities

      4.1 Construct a work breakdown structure for the pilot project.

      4.2 Determine your project’s need for a data scientist.

      4.3 Establish the staffing model for your pilot project.

      4.4 Perform a detailed cost/benefit analysis.

      4.5 Make architectural considerations for supporting the big data initiative.

      Outputs

      Comprehensive list of tasks for implementing the pilot project

      Decision on whether or not a data scientist is needed, and where data science capabilities will be sourced

      RACI chart for the project

      Big data pilot cost/benefit summary

      Customized, high-level architectural model that incorporates technologies that support big data

      Microsoft Teams Cookbook

      • Buy Link or Shortcode: {j2store}408|cart{/j2store}
      • member rating overall impact: 8.8/10 Overall Impact
      • member rating average dollars saved: $6,299 Average $ Saved
      • member rating average days saved: 27 Average Days Saved
      • Parent Category Name: DR and Business Continuity
      • Parent Category Link: /business-continuity

      Remote work calls for leveraging your Office 365 license to use Microsoft Teams – but IT is unsure about best practices for governance and permissions. Moreover, IT has few resources to help train end users with Teams best practices.

      Our Advice

      Critical Insight

      Microsoft Teams is not a standalone app. Successful utilization of Teams occurs when conceived in the broader context of how it integrates with Office 365. Understanding how information flows between Teams, SharePoint Online, and OneDrive for Business, for instance, will aid governance with permissions, information storage, and file sharing.

      Impact and Result

      Use Info-Tech’s Microsoft Teams Cookbook to successfully implement and use Teams. This cookbook includes recipes for:

      • IT best practices concerning governance of the creation process and Teams rollout.
      • End-user best practices for Teams functionality and common use cases.

      Microsoft Teams Cookbook Research & Tools

      Start here – read the Executive Brief

      Learn critical insights for an effective Teams rollout.

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

      • Microsoft Teams Cookbook – Sections 1-2

      1. Teams for IT

      Understand best practices for governance of the Teams creation process and Teams rollout.

      • Microsoft Teams Cookbook – Section 1: Teams for IT

      2. Teams for end users

      Get end users on board with this series of how-tos and common use cases for Teams.

      • Microsoft Teams Cookbook – Section 2: Teams for End Users

      [infographic]

       

      Further reading

      Microsoft Teams Cookbook

      Recipes for best practices and use cases for Microsoft Teams.

      Table of contents

      Executive Brief

      Section 1: Teams for IT

      Section 2: Teams for End Users

      Executive Summary

      Situation

      Remote work calls for leveraging your Office 365 license to utilize Teams – but IT is unsure about best practices for governance and permissions.

      Without a framework or plan for governing the rollout of Teams, IT risks overlooking secure use of Teams, the phenomenon of “teams sprawl,” and not realizing how Teams integrates with Office 365 more broadly.

      Complication

      Teams needs to be rolled out quickly, but IT has few resources to help train end users with Teams best practices.

      With teams, channels, chats, meetings, and live events to choose from, end users may get frustrated with lack of guidance on how to use Teams’ many capabilities.

      Resolution

      Use Info-Tech’s Microsoft Teams Cookbook to successfully implement and utilize Teams. This cookbook includes recipes for:

      • IT best practices concerning governance of the creation process and Teams rollout.
      • End-user best practices for Teams functionality and common use cases.

      Key Insights

      Teams is not a standalone app

      Successful utilization of Teams occurs when conceived in the broader context of how it integrates with Office 365. Understanding how information flows between Teams, SharePoint Online, and OneDrive for Business, for instance, will aid governance with permissions, information storage, and file sharing.

      IT should paint the first picture for team creation

      No initial governance for team creation can lead to “teams sprawl.” While Teams was built to allow end users’ creativity to flow in creating teams and channels, this can create problems with a cluttered interface and keeping track of information. To prevent end-user dissatisfaction here, IT’s initial Teams rollout should offer a basic structure for end users to work with first, limiting early teams sprawl.

      The Teams admin center can only take you so far with permissions

      Knowing how Teams integrates with other Office 365 apps will help with rolling out sensitivity labels to protect important information being accidentally shared in Teams. Of course, technology only does so much – proper processes to train and hold people accountable for their actions with data sharing must be implemented, too.

      Related Info-Tech Research

      Establish a Communication and Collaboration System Strategy

      Don’t waste your time deploying yet another collaboration tool that won’t get used.

      Modernize Communication and Collaboration Infrastructure

      Your legacy telephony infrastructure is dragging you down – modern communications and collaboration technology will dramatically improve productivity.

      Migrate to Office 365 Now

      One small step to cloud, one big leap to Office 365. The key is to look before you leap.

      Section 1: Teams for IT

      Governance best practices and use cases for IT

      Section 1

      Teams for IT

      Section 2

      Teams for end users

      From determining prerequisites to engaging end users.

      IT fundamentals
      • Creation process
      • Teams rollout
      Use cases
      • Retain and search for legal/regulatory compliance
      • Add an external user to a team
      • Delete/archive a team

      Overview: Creation process

      IT needs to be prepared to manage other dependent services when rolling out Teams. See the figure below for how Teams integrates with these other Office 365 applications.

      A flow chart outlining how Teams integrates with other Office 365 applications. Along the side are different applications, from the top: 'Teams client', 'OneDrive for Business', 'Sharepoint Online', 'Planner (Tasks for Teams)', 'Exchange Online', and 'Stream'. Along the top are services of 'Teams client', 'Files', 'Teams', 'Chat', 'Meeting', and 'Calls'.

      Which Microsoft 365 license do I need to access Teams?

      • Microsoft 365 Business Essentials
      • Microsoft 365 Business Premium
      • Office 365 Enterprise, E1, E3, or E5
      • Office 365 Enterprise E4 (if purchased prior to its retirement)

      Please note: To appeal to the majority of Info-Tech’s members, this blueprint refers to Teams in the context of Office 365 Enterprise licenses.

      Assign admin roles

      You will already have at least one global administrator from setting up Office 365.

      Global administrators have almost unlimited access to settings and most of the data within the software, so Microsoft recommends having only two to four IT and business owners responsible for data and security.

      Info-Tech Best Practice

      Configure multifactor authentication for your dedicated Office 365 global administrator accounts and set up two-step verification.

      Once you have organized your global administrators, you can designate your other administrators with “just-enough” access for managing Teams. There are four administrator roles:

      Teams Service Administrator Manage the Teams service; manage and create Microsoft 365 groups.
      Teams Communications Administrator Manage calling and meetings features with Teams.
      Teams Communications Support Engineer Troubleshoot communications issues within Teams using the advanced troubleshooting toolset.
      Teams Communications Support Specialist Troubleshoot communications issues using Call Analytics.

      Prepare the network

      There are three prerequisites before Teams can be rolled out:

      • UDP ports 3478 through 3481 are opened.
      • You have a verified domain for Office 365.
      • Office 365 has been rolled out, including Exchange Online and SharePoint Online.

      Microsoft then recommends the following checklist to optimize your Teams utilization:

      • Optimize calls and performance using the Call Quality Dashboard.
      • Assess network requirements in the Network Planner in the Teams admin center.
      • Ensure all computers running Teams client can resolve external DNS queries.
      • Check adequate public IP addresses are assigned to the NAT pools to prevent port exhaustion.
      • Route to local or regional Microsoft data centers.
      • Whitelist all Office 365 URLs to move through security layers, especially IDS/IPS.
      • Split tunnel Teams traffic so it bypasses your organization’s VPN.

      Info-Tech Best Practice

      For online support and walkthroughs, utilize Advisor for Teams. This assistant can be found in the Teams admin center.

      Team Creation

      You can create and manage Teams through the Teams PowerShell module and the Teams admin center. Only the global administrator and Teams service administrator have full administrative capabilities in this center.

      Governance over team creation intends to prevent “teams sprawl” – the phenomenon whereby end users create team upon team without guidance. This creates a disorganized interface, with issues over finding the correct team and sharing the right information.

      Prevent teams sprawl by painting the first picture for end users:

      1. Decide what kind of team grouping would best fit your organization: by department or by project.
      2. Start with a small number of teams before letting end users’ creativity take over. This will prevent initial death by notifications and support adoption.
      3. Add people or groups to these teams. Assign multiple owners for each team in case people move around at the start of rollout or someone leaves the organization.
      4. Each team has a general channel that cannot be removed. Use it for sharing an overview of the team’s goals, onboarding, and announcements.

      Info-Tech Best Practice

      For smaller organizations that are project-driven, organize teams by projects. For larger organizations with established, siloed departments, organize by department; projects within departments can become channels.

      Integrations with SharePoint Online

      Teams does not integrate with SharePoint Server.

      Governance of Teams is important because of how tightly it integrates with other Office 365 apps, including SharePoint Online.

      A poor rollout of Teams will have ramifications in SharePoint. A good rollout will optimize these apps for the organization.

      Teams and SharePoint integrate in the following ways:

      • Each team created in Teams automatically generates a SharePoint team site behind it. All documents and chat shared through a team are stored in that team’s SharePoint document library.
      • As such, all files shared through Teams are subject to SharePoint permissions.
      • Existing SharePoint folders can be tied to a team without needing to create a new one.
      • If governance over resource sharing in Teams is poor, information can get lost, duplicated, or cluttered throughout both Teams and SharePoint.

      Info-Tech Best Practice

      End users should be encouraged to integrate their teams and channels with existing SharePoint folders and, where no folder exists, to create one in SharePoint first before then attaching a team to it.

      Permissions

      Within the Teams admin center, the global or Teams service administrator can manage Teams policies.

      Typical Teams policies requiring governance include:

      • The extent end users can discover or create private teams or channels
      • Messaging policies
      • Third-party app use

      Chosen policies can be either applied globally or assigned to specific users.

      Info-Tech Best Practice

      If organizations need to share sensitive information within the bounds of a certain group, private channels help protect this data. However, inviting users into that channel will enable them to see all shared history.

      External and guest access

      Within the security and compliance center, the global or Teams service administrator can set external and guest access.

      External access (federation) – turned on by default.

      • Lets you find, call, and chat with users in other domains. External users will have no access to the organization’s teams or team resources.

      Guest access – turned off by default.

      • Lets you add individual users with their own email address. You do this when you want external users to access teams and team resources. Approved guests will be added to the organization’s active directory.

      If guest access is enabled, it is subject to Azure AD and Office 365 licensing and service limits. Guests will have no access to the following, which cannot be changed:

      • OneDrive for Business
      • An organization’s calendar/meetings
      • PSTN
      • Organization’s hierarchical chart
      • The ability to create, revise, or browse a team
      • Upload files to one-on-one chat

      Info-Tech Best Practice

      Within the security and compliance center, you can allow users to add sensitivity labels to their teams that can prevent external and guest access.

      Expiration and archiving

      To reduce the number of unused teams and channels, or delete information permanently, the global or Teams service administrator can implement an Office 365 group expiration and archiving policy through the Teams admin center.

      If a team has an expiration policy applied to it, the team owner will receive a notification for team renewal 30 days, 15 days, and 1 day before the expiry date. They can renew their team at any point within this time.

      • To prevent accidental deletion, auto-renewal is enabled for a team. If the team owner is unable to manually respond, any team that has one channel visit from a team member before expiry is automatically renewed.
      • A deleted Office 365 group is retained for 30 days and can be restored at any point within this time.

      Alternatively, teams and their channels (including private) can be archived. This will mean that all activity for the team ceases. However, you can still add, remove, and update roles of the members.

      Retention and data loss prevention

      Retention policies can be created and managed in the Microsoft 365 Compliance Center or the security and compliance center PowerShell cmdlets. This can be applied globally or to specific users.

      By default, information shared through Teams is retained forever.

      However, setting up retention policies ensures data is retained for a specified time regardless of what happens to that data within Teams (e.g. user deletes).

      Info-Tech Best Practice

      To prevent external or guest users accessing and deleting sensitive data, Teams is able to block this content when shared by internal users. Ensure this is configured appropriately in your organization:

      • For guest access in teams and channels
      • For external access in meetings and chat

      Please note the following limitations of Teams’ retention and data loss prevention:

      • Organization-wide retention policies will need to be manually inputted into Teams. This is because Teams requires a retention policy that is independent of other workloads.
      • As of May 2020, retention policies apply to all information in Teams except private channel messages. Files shared in private channels, though, are subject to retention policies.
      • Teams does not support advanced retention settings, such as a policy that pertains to specific keywords or sensitive information.
      • It will take three to seven days to permanently delete expired messages.

      Teams telephony

      Teams has built-in functionality to call any team member within the organization through VoIP.

      However, Teams does not automatically connect to the PSTN, meaning that calling or receiving calls from external users is not immediately possible.

      Bridging VoIP calls with the PSTN through Teams is available as an add-on that can be attached to an E3 license or as part of an E5 license.

      There are two options to enable this capability:

      • Enable Phone System. This allows for call control and PBX capabilities in Office 365.
      • Use direct routing. You can use an existing PSTN connection via a Session Border Controller that links with Teams (Amaxra).

      Steps to implement Teams telephony:

      1. Ensure Phone System and required (non-Microsoft-related) services are available in your country or region.
      2. Purchase and assign Phone System and Calling Plan licenses. If Calling Plans are not available in your country or region, Microsoft recommends using Direct Routing.
      3. Get phone numbers and/or service numbers. There are three ways to do this:
        • Get new numbers through the Teams admin center.
        • If you cannot get new numbers through the Teams admin center, you can request new numbers from Microsoft directly.
        • Port or transfer existing numbers. To do this, you need to send Microsoft a letter of authorization, giving them permission to request and transfer existing numbers on your behalf.
      4. To enable service numbers, including toll-free numbers, Microsoft recommends setting up Communications Credits for your Calling Plans and Audio Conferencing.

      Overview: Teams rollout

      1. From Skype (and Slack) to Teams
      2. Gain stakeholder purchase
      3. Employ a phased deployment
      4. Engage end users

      Skype for Business is being retired; Microsoft offers a range of transitions to Teams.

      Combine the best transition mode with Info-Tech’s adoption best practices to successfully onboard and socialize Teams.

      From Skype to Teams

      Skype for Business Online will be retired on July 31, 2021. Choose from the options below to see which transition mode is right for your organization.

      Skype for Business On-Premises will be retired in 2024. To upgrade to Teams, first configure hybrid connectivity to Skype for Business Online.

      Islands mode (default)

      • Skype for Business and Teams coexist while Teams is rolled out.
      • Recommended for phased rollouts or when Teams is ready to use for chat, calling, and meetings.
      • Interoperability is limited. Teams and Skype for Business only transfer information if an internal Teams user sends communications to an external Skype for Business user.

      Teams only mode (final)

      • All capabilities are enabled in Teams and Skype for Business is disabled.
      • Recommended when end users are ready to switch fully to Teams.
      • End users may retain Skype for Business to join meetings with non-upgraded or external parties. However, this communication is only initiated from the Skype for Business external user.

      Collaboration first mode

      • Skype for Business and Teams coexist, but only Teams’ collaboration capabilities are enabled. Teams communications capabilities are turned off.
      • Recommended to leverage Skype for Business communications yet utilize Teams for collaboration.

      Meetings first mode

      • Skype for Business and Teams coexist, but only Teams’ meetings capabilities are enabled.
      • Recommended for organizations that want to leverage their Skype for Business On-Premises’ Enterprise Voice capability but want to benefit from Teams’ meetings through VoIP.

      From Slack to Teams

      The more that’s left behind in Slack, the easier the transition. As a prerequisite, pull together the following information:

      • Usage statistics of Slack workspaces and channels
      • What apps end users utilize in Slack
      • What message history you want to export
      • A list of users whose Slack accounts can map on to required Microsoft accounts
      Test content migration

      Your Slack service plan will determine what you can and can’t migrate. By default, public channels content can be exported. However, private channels may not be exportable, and a third-party app is needed to migrate Direct Messages.

      Files migration

      Once you have set up your teams and channels in Teams, you can programmatically copy files from Slack into the target Teams channel.

      Apps migration

      Once you have a list of apps and their configurations used in Slack’s workspaces, you can search in Teams’ app store to see if they’re available for Teams.

      User identity migration

      Slack user identities may not map onto a Microsoft account. This will cause migration issues, such as problems with exporting text content posted by that user.

      Follow the migration steps to the right.

      Importantly, determine which Slack workspaces and channels should become teams and channels within Teams.

      Usage statistics from Slack can help pinpoint which workspaces and channels are redundant.

      This will help IT paint an ordered first picture for new Teams end users.

      1. Create teams and channels in Teams
      2. Copy files into Teams
      3. Install apps, configure Office 365 Connecters
      4. Import Slack history
      5. Disable Slack user accounts

      Info-Tech Best Practice

      Avoid data-handling violations. Determine what privacy and compliance regulations (if any) apply to the handling, storage, and processing of data during this migration.

      Gain stakeholder purchase

      Change management is a challenging aspect of implementing a new collaboration tool. Creating a communication and adoption plan is crucial to achieving universal buy-in for Teams.

      To start, define SMART objectives and create a goals cascade.

      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?

      Sample list of stakeholder-specific benefits from improving collaboration

      Stakeholder Driver Benefits
      Senior Leadership Resource optimization Increased transparency into IT operational costs.
      Better ability to forecast hardware, resourcing costs.
      All employees Increasing productivity Apps deployed faster.
      Issues fixed faster.
      Easier access to files.
      Able to work more easily offsite.
      LBU-HR, legal, finance Mitigating risk Better able to verify compliance with external regulations.
      Better understanding of IT risks.
      Service desk Resource optimization Able to resolve issues faster.
      Fewer issues stemming from updates.
      Tier 2 Increasing productivity Less time spent on routine maintenance.

      Use these activities to define what pain points stakeholders face and how Teams can directly mitigate those pain points.

      (Source: Rationalize Your Collaboration Tools (coming soon), Activities: 3.1C – 3.1D)

      Employ a phased deployment

      Info-Tech Best Practice

      Deploy Teams over a series of phases. As such, if you are already using Skype for Business, choose one of the coexistence phases to start.

        1. Identify and pilot Teams with early adopters that will become your champions. These champions should be formally trained, be encouraged to help and train their colleagues, and be positively reinforced for their efforts.
        2. Iron out bugs identified with the pilot group and train middle management. Enterprise collaboration tool adoption is strongly correlated with leadership adoption.
          1. Top-level management
            Control and direct overall organization.
          2. Middle management
            Execute top-level management’s plans in accordance with organization’s norms.
          3. First-level management
            Execute day-to-day activities.
        3. Use Info-Tech’s one-pager marketing template to advertise the new tool to stakeholders. Highlight how the new tool addresses specific pain points. Address questions stemming from fear and uncertainty to avoid employees’ embarrassment or their rejection of the tool.
      A screenshot of Info-Tech's one-pager marketing template.
      1. Extend the pilot to other departments and continue this process for the whole organization.

      (Source: Rationalize Your Collaboration Tools (coming soon), Tools:GANTT Chart and Marketing Materials, Activities: 3.2A – 3.2B)

      Info-Tech Insight

      Be in control of setting and maintaining expectations. Aligning expectations with reality and the needs of employees will lower onboarding resistance.

      Engage end users

      Short-term best practices

      Launch day:
      • Hold a “lunch and learn” targeted training session to walk end users through common use cases.
      • Open a booth or virtual session (through Teams!) and have tool representatives available to answer questions.
      • Create a game to get users exploring the new tool – from scavenger hunts to bingo.
      Launch week:
      • Offer incentives for using the tool and helping others, including small gift cards.
      • Publicize achievements if departments hit adoption milestones.

      Long-term best practices

      • Make available additional training past launch week. End users should keep learning new features to improve familiarity.
      • Distribute frequent training clips, slowly exposing end users to more complex ways of utilizing Teams.
      • Continue to positively reinforce and recognize those who use Teams well. This could be celebrating those that help others use the tool, how active certain users are, and attendance at learning events.

      Info-Tech Best Practice

      Microsoft has a range of training support that can be utilized. From instructor-led training to “Coffee in the Cloud” sessions, leverage all the support you can.

      Use case #1: Retain and search data for legal/regulatory compliance

      Scenario:

      Your organization requires you to retain data and documents for a certain period of time; however, after this period, your organization wishes to delete or archive the data instead of maintaining it indefinitely. Within the timeframe of the retention policy, the admin may be asked to retrieve information that has been requested through a legal channel.

      Purpose:
      • Maintain compliance with the legal and regulatory standards to which the organization is subject.
      Jobs:
      • Ensure the data is retained for the approved time period.
      • Ensure the policy applies to all relevant data and users.
      Solution: Retention Policies
      • Ensure that your organization has an Office 365 E3 or higher license.
      • Set the desired retention policy through the Security & Compliance Center or PowerShell by deciding which teams, channels, chats, and users the policies will apply to and what will happen once the retention period ends.
      • Ensure that matching retention policies are applied to SharePoint and OneDrive, since this is where files shared in Teams are stored.
      • Be aware that Teams retention policies cannot be applied to messages in private channels.
      Solution: e-Discovery
      • If legally necessary, place users or Teams on legal hold in order to retain data that would be otherwise deleted by your organization’s retention policies.
      • Perform e-discovery on Teams messages, files, and summaries of meetings and calls through the Security & Compliance Center.
      • See Microsoft’s chart on the next slide for what is e-discoverable.

      Content subject to e-discovery

      Content type eDiscoverable Notes
      Teams chat messages Yes Chat messages from chats where guest users are the only participants in a 1:1 or 1:N chat are not e-discoverable.
      Audio recordings No  
      Private channel messages Yes  
      Emojis, GIFs, stickers Yes  
      Code snippets No  
      Chat links Yes  
      Reactions (likes, hearts, etc) No  
      Edited messages Yes If the user is on hold, previous versions of edited messages are preserved.
      Inline images Yes  
      Tables Yes  
      Subject Yes  
      Quotes Yes Quoted content is searchable. However, search results don’t indicate that the content was quoted.
      Name of channel No  

      E-discovery does not capture audio messages and read receipts in MS Teams.

      Since files shared in private channels are stored separately from the rest of a team, follow Microsoft’s directions for how to include private channels in e-discovery. (Source: “Conduct an eDiscovery investigation of content in Microsoft Teams,” Microsoft, 2020.)

      Use case #2: Add external person to a team

      Scenario:

      A team in your organization needs to work in an ongoing way with someone external to the company. This user needs access to the relevant team’s work environment, but they should not be privy to the goings-on in the other parts of the organization.

      Jobs:

      This external person needs to be able to:

      • Attend meetings
      • Join calls
      • Chat with individual team members
      • View and collaborate on the team’s files
      Solution:
      • If necessary, set a data loss prevention policy to prevent your users from sharing certain types of information or files with external users present in your organization’s Teams chats and public channels.
      • Ensure that your Microsoft license includes DLP protection. However:
        • DLP cannot be applied to private channel messages.
        • DLP cannot block messages from external Skype for Business users nor external users who are not in “Teams only” mode.
      • Ensure that you have a team set up for the project that you wish the external user to join. The external user will be able to see all the channels in this team, unless you create a private channel they are restricted from.
      • Complete Microsoft’s “Guest Access Checklist” to enable guest access in Teams, if it isn’t already enabled.
      • As admin, give the external user guest access through the Teams admin center or Azure AD B2B collaboration. (If given permission, team owners can also add guests through the Teams client).
      • Decide whether to set a policy to monitor and audit external user activity.

      Use case #3: Delete/archive a team

      Scenario:

      In order to avoid teams sprawl, organizations may want IT to periodically delete or archive unused teams within the Teams client in order to improve the user interface.

      Alternately, if you are using a project-based approach to organizing Teams, you may wish to formalize a process to archive a team once the project is complete.

      Delete:
      • Determine if the team owner anticipates the team will need to be restored one day.
      • Ensure that deletion does not contradict the organization’s retention policy.
      • If not, proceed with deletion. Find the team in the Teams admin center and delete.
      • Restore a deleted team within 30 days of its initial deletion through PowerShell.
      Archive:
      • Determine if the team owner anticipates the team will need to be restored one day.
      • Find the relevant team in the Teams admin center and change its status to “Archived.”
      • Restore the archived team if the workspace becomes relevant once again.

      Info-Tech Best Practice

      Remind end users that they can hide teams or channels they do not wish to see in their Teams interface. Knowing a team can be hidden may impact a team owner’s decision to delete it.

      Section 2: Teams for End Users

      Best practices for utilizing teams, channels, chat, meetings, and live events

      Section 1

      Teams for IT

      Section 2

      Teams for end users

      From Teams how-tos to common use cases for end users.

      End user basics
      • Teams, channels, and chat
      • Meetings and live events
      Common use cases: Workspaces
      • WS#1: Departments
      • WS#2: A cross-functional committee
      • WS#3: An innovation day event
      • WS#4: A non-work-related social event
      • WS#5: A project team with a defined end time
      Common use cases: Meetings
      • M#1: Job interview with an external candidate
      • M#2: Quarterly board meeting
      • M#3: Weekly recurring team meeting
      • M#4: Morning stand-up/scrum
      • M#5: Phone call between two people

      Overview: Teams, channels, and chat

      Teams

      • Team: A workspace for a group of collaborative individuals.
        • Public channel: A focused area where all members of a team can meet, communicate, and share ideas and content.
        • Private channel: Like a public channel but restricted to a subset of team members, defined by channel owner.

      Chat

      • Chat: Two or more users collected into a common conversation thread.
      (Source: “Overview of teams and channels in Microsoft Teams,” Microsoft, 2020.)

      For any Microsoft Teams newcomer, the differences between teams, channels, and chat can be confusing.

      Use Microsoft’s figure (left) to see how these three mediums differ in their role and function.

      Best practices: Workspaces 1/2

        Team
      A workspace for a group of collaborative individuals.
      Public Channel
      A focused area where all members of a team can meet, communicate, and share ideas and content.
      Private Channel
      Like a public channel but restricted to a subset of team members, defined by channel owner.
      Group Chat
      Two or more users collected into a common conversation thread.
      Limits and Administrative Control
      Who can create? Default setting: All users in an organization can create a team

      Maximum 500,000 teams per tenant

      Any member of a team can create a public channel within the team

      Maximum 200 public channels per team

      Any member of a team can create a private channel and define its members

      Maximum 30 private channels per team

      Anyone
      Who can add members? Team owner(s); max 5,000 members per team N/A Channel owner(s) can add up to 250 members Anyone can bring new members into the chat (and decide if they can see the previous history) up to 100 members
      Who can delete? Team owner/admin can delete Any team member Channel owner(s) Anyone can leave a chat but cannot delete chat, but they are never effectively deleted
      Social Context
      Who can see it? Public teams are indexed and searchable

      Private teams are not indexed and are visible only to joined members

      All members of the team can see all public channels. Channels may be hidden from view for the purposes of cleaning up the UI. Individuals will only see private channels for which they have membership Only participants in the group chat can see the group chat
      Who can see the content? Team members can see any content that is not otherwise part of a private channel All team members All members of the private channel Only members of the group chat

      When does a Group Chat become a Channel?

      • When it’s appropriate for the conversation to have a gallery – an audience of members who may not be actively participating in the discussion.
      • When control over who joins the conversation needs to be centrally governed and not left up to anyone in the discussion.
      • When the discussion will persist over a longer time period.
      • When the number of participants approaches 100.

      When does a Channel become a Team?

      • When a team approaches 30 private channels, many of those private channels are likely candidates to become their own team.
      • When the channel membership needs to extend beyond the boundary of the team membership.

      Best practices: Workspaces 2/2

        Team
      A workspace for a group of collaborative individuals.
      Public Channel
      A focused area where all members of a team can meet, communicate, and share ideas and content.
      Private Channel
      Like a public channel but restricted to a subset of team members, defined by channel owner.
      Group Chat
      Two or more users collected into a common conversation thread.
      Data and Applications
      Where does the content live? SharePoint: Every team resides in its own SharePoint site SharePoint: Each team (public and private) has its own folder off the root of the SharePoint site’s repository SharePoint: Each team (public and private) has its own folder off the root of the SharePoint site’s repository OneDrive: Files that are shared in a chat are stored in the OneDrive folder of the original poster and shared to the other members
      How does the data persist or be retained? If a team expires/is deleted, its corresponding SharePoint site and those artifacts are also deleted Available for 21 days after deletion. Any member of the team can delete a public channel. The team owner and private channel owner can delete/restore a private channel Chats are never effectively deleted. They can be hidden to clean up the user interface.
      Video N/A Yes, select “Meet now” in channel below text entry box Yes, select “Meet now” in channel below text entry box Yes
      Phone calls N/A Yes, select “Meet now” in channel below text entry box Yes, select “Meet now” in channel below text entry box Yes
      Shared computer audio/screen N/A Yes, select “Meet now” in channel below text entry box Yes, select “Meet now” in channel below text entry box Yes
      File-sharing Within channels Yes. Frequently used/collaborated files can be turned into discrete tab. Yes. Frequently used/collaborated files can be turned into discrete tab. Yes
      Wikis Within channels Yes Yes No
      Whiteboarding No No No No

      When does a Team become a Channel?

      • When a team’s purpose for existing can logically be subsumed by another team that has a larger scope.

      When does a Channel become a Group Chat?

      • When a conversation within a channel between select users does not pertain to that channel’s scope (or any other existing channel), they should move the conversation to a group chat.
      • However, this is until that group chat desires to form a channel of its own.

      Create a new team

      Team owner: The person who creates the team. It is possible for the team owner to then invite other members of the team to become co-owners to distribute administrative responsibilities.

      Team members: People who have accepted their invitation to be a part of the team.

      NB: Your organization can control who has permission to set up a team. If you can’t set a up a team, contact your IT department.

      Screenshots detailing how to create a new team in Microsoft Teams, steps 1 to 3. Step 1: 'Click the <Teams data-verified= tab on the left-hand side of the app'. Step 2: 'At the bottom of the app, click '. Step 3: 'Under the banner , click '.">

      Create a new team

      Screenshot detailing how to create a new team in Microsoft Teams, the step 4 starting point with an arrow pointing to the 'Build a team from scratch' button.

      Decide from these two options:

      • Building a team from scratch, which will create a new group with no prior history imported (steps 4.1–4.3).
      • Creating a team from an existing group in Office 365, including an already existing team (steps 4.4–4.6).

      NB: You cannot create a team from an existing group if:

      • That group has 5,000 members or more.
      • That group is in Yammer.

      Screenshot detailing how to create a new team in Microsoft Teams, step 4.1. There are buttons for 'Private' and 'Public'.

      Decide if you want you new team from scratch to be private or public. If you set up a private team, any internal or external user you invite into the team will have access to all team history and files shared.

      Screenshot detailing how to create a new team in Microsoft Teams, step 4.2 and 4.3. 4.2 has a space to give your team a name and another for a description. 4.3 says 'Then click <Create data-verified='.">

      Create a new team

      Screenshot detailing how to create a new team in Microsoft Teams, the step 4 starting point with an arrow pointing to the 'Create from...' button.

      Decide from these two options:

      • Building a team from scratch, which will create a new group with no prior history imported (steps 4.1–4.3).
      • Creating a team from an existing group in Office 365, including an already existing team (steps 4.4–4.6).

      NB: You cannot create a team from an existing group if:

      • That group has 5,000 members or more.
      • That group is in Yammer.

      Screenshot detailing how to create a new team in Microsoft Teams, step 4.4. It reads 'Create a new team from something you already own' with a button for 'Team'.

      Configure your new team settings, including privacy, apps, tabs, and members.

      Screenshot detailing how to create a new team in Microsoft Teams, step 4.5 and 4.6. 4.5 has a space to give your team a name, a description, choose privacy settings, and what you'd like to include from the original team. 4.6 says 'Then click <Create data-verified='.">

      Add team members

      Remove team members

      Screenshot detailing how to add team members in Microsoft Teams, step 1.

      To add a team member, on the right-hand side of the team name, click “More options.”

      Then, from the drop-down menu, click “Add member.”

      Screenshot detailing how to remove team members in Microsoft Teams, step 1.

      Only team owners can remove a team member. To do so, on the right-hand side of the team name, click “More options.”

      Then, from the drop-down menu, click “Manage team.”

      Screenshot detailing how to add team members in Microsoft Teams, step 2.

      If you’re a team owner, you can then type a name or an email address to add another member to the team.

      If you’re a team member, typing a name or an email address will send a request to the team owner to consider adding the member.

      Screenshot detailing how to remove team members in Microsoft Teams, step 2.

      Under the “Members” tab, you’ll see a list of the members in the team. Click the “X” at the far right of the member’s name to remove them.

      Team owners can only be removed if they change their role to team member first.

      Create a new channel

      Screenshot detailing how to create a new channel in Microsoft Teams, step 1.

      On the right-hand side of the team name, click “More options.”

      Then, from the drop-down menu, click “Add channel.”

      Screenshot detailing how to create a new channel in Microsoft Teams, step 2.

      Name your channel, give a description, and set your channel’s privacy.

      Screenshot detailing how to create a new channel in Microsoft Teams, step 3.

      To manage subsequent permissions, on the right-hand side of the channel name, click “More options.”

      Then, from the drop-down menu, click “Manage channel.”

      Adding and removing members from channels:

      Only members in a team can see that team’s channels. Setting channel privacy as “standard” means that the channel can be accessed by anyone in a team. Unless privacy settings for a channel are set as “private” (from which the channel creator can choose who can be in that channel), there is no current way to remove members from channels.

      It will be up to the end user to decide which channels they want to hide.

      Link team/channel to SharePoint folder

      Screenshot detailing how to link a team or channel to a SharePoint folder in Microsoft Teams, steps 1, 2, and 3. Step 1: 'Along the top of the team/channel tab bar, click the “+” symbol'. Step 2: 'Select “Document Library” to link the team/channel to a SharePoint folder'. Step 3: 'Copy and paste the SharePoint URL for the desired folder, or search in “Relevant sites” if the folder can be found there'.

      Need to find the SharePoint URL?

      Screenshot detailing how to find the SharePoint URL in Microsoft Teams. 'Locate the folder in SharePoint and click <Show actions data-verified=', 'Click to access the folder's SharePoint URL.'">

      Hide/unhide teams

      Hide/unhide channels

      Screenshot detailing how to hide and unhide teams in Microsoft Teams, step 1.

      To hide a team, on the right-hand side of the team name, click “More options.”

      Then, from the drop-down menu, click “Hide.” Hidden teams are moved to the “hidden teams” menu at the bottom of your team list.

      Screenshot detailing how to hide and unhide channels in Microsoft Teams, step 1.

      To hide a channel, on the right-hand side of the channel name, click “More options.”

      Then, from the drop-down menu, click “Hide.” Hidden channels are moved to the “hidden channels” menu at the bottom of your channel list in that team.

      Screenshot detailing how to hide and unhide teams in Microsoft Teams, step 2. Screenshot of a button that says 'Hidden teams'.

      To unhide a team, click on the “hidden teams” menu. On the right-hand side of the team name, click “More options.”

      Then, from the drop-down menu, click “Show.”

      Screenshot detailing how to hide and unhide channels in Microsoft Teams, step 2.

      To unhide a channel, click on the “hidden channels” menu at the bottom of the team. This will produce a drop-down menu of all hidden channels in that team.

      Hover over the channel you want to unhide and click “Show.”

      Find/join teams

      Leave teams

      Screenshot detailing how to find and join teams in Microsoft Teams, step 1. Click the “Teams” tab on the left-hand side of the app. Screenshot detailing how to find and join teams in Microsoft Teams, step 2.

      At the bottom of the app, click “Join or create a team.” Teams will then suggest a range of teams that you might be looking for. You can join public teams immediately. You will have to request approval to join a private team.

      Screenshot detailing how to leave teams in Microsoft Teams.

      To leave a team, on the right-hand side of the team name, click “More options.”

      Then, from the drop-down menu, click “Leave the team.”

      NB: If the owner of a private team has switched off discoverability, you will have to contact that owner to join that team. Screenshot detailing how to find and join teams in Microsoft Teams, step 3. If you can’t immediately see the team, you have two options: either search for the team or enter that team’s code under the banner “Join a team with a code.” Can I find a channel?

      No. To join a channel, you need to first join the team that channel belongs to.

      Can I leave a channel?

      No. The most you can do is hide the channel. By default, if you join a team you will have access to all the channels within that team (unless a channel is private, in which case you’ll have to request access to that channel).

      Create a chat

      Screenshots detailing how to create a chat in Microsoft Teams, steps 1 to 5. Step 1:'Click the “Chat” tab on the left hand side of the app (or keyboard shortcut Ctrl+N)'. Step 2: 'Search the name of the person you want to chat with'. Step 3: 'You’re now ready to start the chat! You can also send a chat message while working in a separate channel by typing/chat into the search bar and entering the recipient’s name'. Step 4: 'For group chat, click the “Add people” button in the top right hand corner of the app to add other persons into the existing chat'. Step 5: 'You can then rename the group chat (if there are 3+ people) by clicking the “Name group chat” option to the right of the group chat members’ names'.

      Hide a chat

      Unhide a chat

      Screenshots detailing how to hide a chat in Microsoft Teams, steps 1 to 3. Step 1:'Click the “Chat” tab on the left-hand side of the app'. Step 2: 'Search the name of the chat or group chat that you want to hide'. Step 3: In either 'Single person chat options' or 'Group chat options' Click “More options.” Then click “Hide.”' To unhide a chat, search for the hidden person or name of the group chat in the search bar. Click “More options.” Then click “Unhide.” Screenshot detailing how to unhide a chat in Microsoft Teams.

      Leave a chat

      You can only leave group chats. To do so, click “More options.” Then click “Leave.” Screenshot detailing how to leave a chat in Microsoft Teams.

      Overview: Meetings and live events

      Teams Meetings: Real-time communication and collaboration between a group, limited to 250 people.

      Teams Live Events: designed for presentations and webinars to a large audience of up to 10,000 people, in which attendees watch rather than interact.

       

      Office 365 and Microsoft 365 Licenses

      I want to: F1 F3 E1 E3 E5 Audio conferencing add-on
      Join a Teams meeting No license required. Any email address can participate in a Teams meeting.
      Attend a Teams meeting with a dial-in phone number No license required. Any phone number can dial into a Teams meeting. (Meeting organizers need to have an Audio Conferencing add-on license to send an invite that includes dial-in conferencing.)
      Attend a Teams live event No license required. Any phone number can dial into a Teams live event.
      Create a Teams meeting for up to 250 attendees   One of these licensing plans
      Create a Teams meeting for up to 250 attendees with a dial-in phone number   One of these licensing plans + Audio Conferencing (Meeting organizers need to have an Audio Conferencing add-on license to send an invite that includes dial-in conferencing.)
      Create a Teams live event for up to 10,000 attendees     One of these licensing plans
      Dial out from a Teams meeting to add someone at their Call me at number   One of these licensing plans + Audio Conferencing (Meeting dial out to a Call me at number requires organizers to have an E5 or Audio Conference add-in license. A dial plan may also be needed.)

      Depending on the use case, end users will have to determine whether they need to hold a meeting or a live event.

      Use Microsoft’s table (left) to see what license your organization needs to perform meetings and live events.

      (Source: “Admin quick start – Meetings and live events in Microsoft Teams,” Microsoft, 2020.)

      Best practices: Meetings

        Ad Hoc Call
      Direct audio/video call
      Scheduled Meeting Live Event
      Limits and Administrative Control
      Who can create? Anyone Anyone Anyone, unless altered by admin (permission to create MS Stream events also required if external production tools are used).
      Who can add members? Anyone in the session. The meeting organizer can add new attendees to the meeting. The event creator (the “organizer”) sets attendee permissions and assigns event group roles (“producer” and “presenter”).
      Can external stakeholders attend? Yes, through email invite. However, collaboration tools are restricted. Yes, through email invite. However, collaboration tools are restricted. Public events: yes, through shared invite link.
      Org-wide event: yes, if guest/external access granted.
      Who can delete? Anyone can leave the session. There is no artifact to delete. The meeting organizer Any attendee can leave the session.
      The organizer can cancel the event.
      Maximum attendees 100 250 10,000 attendees and 10 active presenters/producers (250 presenters and producers can be present at the event).
      Social Context
      How does the request come in? Unscheduled.
      Notification of an incoming audio or video call.
      Scheduled.
      Meeting invite, populated in the calendar, at a scheduled time.
      Meeting only auto-populated in event group’s calendars. Organizer must circulate event invite link to attendees – for instance, by pasting link into an Outlook meeting invite.
      Available Functionality
      Screen-sharing Yes Yes Producers and Presenters (through Teams, no third-party app).
      Whiteboard No Yes Yes
      OneNote (for minutes) Yes (from a member’s OneDrive) Yes, part of the meeting construct. No. A Meeting Notes tab is available instead.
      Dedicated chat space Yes. Derived from a group chat. Meeting has its own chat room. The organizer can set up a moderated Q&A (not chat) when creating the event. Only Presenters and Producers can chat.
      Recording Yes Yes Yes. Event can last up to 4 hours.

      When should an Ad Hoc Call become a Scheduled Meeting?

      • When the participants need time to prepare content for the call.
      • When an answer is not required immediately.
      • When bringing a group of people together requires logistical organizing.

      When should a Scheduled Meeting become an Ad Hoc Call?

      • When the participants can meet on short notice.
      • When a topic under discussion requires creating alignment quickly.

      When should a Live Event be created?

      • When the expected attendance exceeds 250 people.
      • If the event does not require collaboration and is mostly a presenter conveying information.

      Create a scheduled meeting

      Screenshots detailing how to create a scheduled meeting in Microsoft Teams, steps 1 to 4. Step 1:'Click the “Calendar” tab on the left-hand side of the app'. Step 2: 'On the top-right of the app, click the drop-down menu for “+ New meeting” and then “Schedule meeting.”' Step 3: 'Fill in the meeting details. When inputting internal attendees, their names will drop down without needing their email. You will need to input email addresses for external attendees'. Step 4: 'To determine internal attendees’ availability, click “Scheduling assistant” on the top left. Then click “Save” to create the meeting'.

      Create an ad hoc meeting

      Screenshots detailing how to create an ad hoc meeting in Microsoft Teams, steps 1 to 4. Step 1:'Click the “Calendar” tab on the left-hand side of the app'. Step 2: 'Along the top-right, click “Meet now.”' Step 3: 'Name your meeting, choose your audio and video settings, and click “Join now.”'. Step 4: 'To determine internal attendees’ availability, click “Scheduling assistant” on the top left. Then click “Save” to create the meeting. You’ll then be prompted to fill in the meeting details. When inputting internal attendees, their names will drop down without needing their email. You will need to input email addresses for external attendees'.

      Tip: Use existing channels to host the chatrooms for your online meetings

      When you host a meeting online with Microsoft Teams, there will always be a chatroom associated with the meeting. While this is a great place for meeting participants to interact, there is one particular downside.

      Problem: The never-ending chat. Often the activity in these chatrooms can persist long after the meeting. The chatroom itself becomes, unofficially, a channel. When end users can’t keep up with the deluge of communication, the tools have failed them.

      Solution: Adding an existing channel to the meeting. This ensures that discussion activity is already hosted in the appropriate venue for the group, during and after the meeting. Furthermore, it provides non-attendees with a means to catch up on the discussion they have missed.

      In section two of this cookbook, we will often refer to this tactic.

      A screenshot detailing how to add an existing channel to a meeting in Microsoft Teams. 'Break the habit of online booking meetings in Outlook – use the Teams Calendar View instead! In order to make use of this function, the meeting must be setup in Microsoft Teams, not Microsoft Outlook. The option to assign a channel to the meeting will then be available to the meeting organizer.'

      Don’t have a channel for the chat session of your online meeting? Perhaps you should!

      If your meeting is with a group of individuals that will be collaborating frequently, they may need a workspace that persists beyond the meeting.

      Guests can still attend the meeting, but they can’t chat!

      If there are attendees in your meeting that do not have access to the channel you select to host the chat, they will not see the chat discussion nor have any ability to use this function.

      This may be appropriate in some cases – for example, a vendor providing a briefing as part of a regular team meeting.

      However, if there are attendees outside the channel membership that need to see the meeting chat, consider another channel or simply default to not assigning one.

      Meeting settings explained

      Show device settings. For settings concerning audio, video, and whether viewing is private.

      Show meeting notes. Use to take notes throughout the meeting. The notes will stay attached to this event.

      Show meeting details. Find meeting information for: a dial-in number, conference ID, and link to join.

      Enter full screen.

      Show background effects. Choose from a range of video backgrounds to hide/blur your location.

      Turn on the captions (preview). Turn on live speech-to-text captions.

      Keypad. For dialing a number within the meeting (when enabled as an add-on with E3 or as part of E5).

      Start recording. Recorded and saved using Microsoft Stream.

      End meeting.

      Turn off incoming video. To save network bandwidth, you can decline receiving attendee’s video.

      Click “More options” to access the meetings settings.

      Screen share. In the tool tray, select “Share” to share your screen. Select particular applications if you only want to share certain information; otherwise, you can share your whole desktop.

      System audio share. To share your device’s audio while screen sharing, checkbox the “Include system audio” option upon clicking “Share.”

      If you didn’t click that option at the start but now want to share audio during screen share, click the “Include systems audio” option in the tool tray along the top of the screen.

      Give/take control of screen share. To give control, click “Give control” in the tool tray along the top of the screen when sharing content. Choose from the drop-down who you would like to give control to. In the same spot, click “Take back control” when required.

      To request control, click “Request control” in the same space when viewing someone sharing their content. Click “Release control” once finished.

      Start whiteboarding

      1. You’ll first need to enable Microsoft Whiteboard in the Microsoft 365 admin center. Ask your relevant admin to do so if Whiteboard is not already enabled.
      2. Once enabled, click “Share” in a meeting. This feature only appears if you have 3+ participants in the meeting.
      3. Under the “Whiteboard” section in the bottom right, click “Microsoft Whiteboard.”
      4. Click the pen icons to the right of the screen to begin sketching.

      NB: Anonymous, federated, or guest users are currently not supported to start, view, or ink a whiteboard in a Teams meeting.

      Will the whiteboard session be recorded if the meeting is being recorded?

      No. However, the final whiteboard will be available to all meeting attendees after the meeting, under “Board Gallery” in the Microsoft Whiteboard app. Attendees can then continue to work on the whiteboard after the meeting has ended.

      Create a live event

      Screenshots detailing how to create a live event in Microsoft Teams, steps 1 to 3. Step 1: 'Click the “Calendar” tab on the left-hand side of the app'. Step 2: 'On the top right of the app, click the drop-down menu for “+ New meeting” and then “Live event.”' Step 3: 'You will be labeled the “Event organizer.” First, fill in the live event details on the left'. Screenshot detailing how to create a live event in Microsoft Teams, step 4.

      As the organizer, you can invite other people to the event who will be the “producers” or “presenters.”

      Producers: Control the live event stream, including being able to start and stop the event, share their own and others’ video, share desktop or window, and select layout.

      Presenters: Present audio, video, or a screen.

      Screenshot detailing how to create a live event in Microsoft Teams, step 5.

      Select who your audience will be for your live event from three options: specified people and groups, the organization, or the public with no sign-in required.

      Edit the setting for whether you want recording to be available for attendees.

      Then click “Schedule” to finish.

      Live event settings explained

      When you join the live event as a producer/presenter, nothing will be immediately broadcast. You’ll be in a pre-live state. Decide what content to share and in what order. Along the bottom of the screen, you can share your video and audio, share your screen, and mute incoming attendees.

      Once your content is ready to share along the bottom of the screen, add it to the screen on the left, in order of viewing. This is your queue – your “Pre-live” state. Then, click “Send now.”

      This content will now move to the right-hand screen, ready for broadcasting. Once you’re ready to broadcast, click “Start.” Your state will change from “Pre-live” to “Live.”

      Along the top right of the app will be a tools bar.

      Screenshot listing live events settings icons in Microsoft Teams. Beside the heart monitor icon is 'Monitor health and performance of network, devices, and media sharing'. Beside the notepad icon is 'Take meeting notes'. Beside the chatbox icon is 'Chat function'. Beside the two little people with a plus sign icon is 'Invite and show participants'. Beside the gear icon is 'Device settings'. Beside the small 'i' in a circle is 'Meeting details, including schedule, meeting link, and dial-in number'.

      Workspace #1: Departments

      Scenario: Most of your organization’s communication and collaboration occurs within its pre-existing departmental divisions.

      Conventional communication channels:

      • Oral communication: Employees work in proximity to each other and communicate in person, by phone, in department meetings
      • Email: Department-wide announcements
      • Memos: Typically posted/circulated in mailboxes

      Solution: Determine the best way to organize your organization’s departments in Teams based on its size and your requirements to keep information private between departments.

      Option A:

      • Create a team for the organization/division.
      • Create channels for each department. Remember that all members of a team can view all public channels created in that team and the default General channel.
      • Create private channels if you wish to have a channel that only select members of that team can see. Remember that private channels have some limitations in functionality.

      Option B:

      • Create a new team for each department.
      • Create channels within this team for projects or topics that are recurring workflows for the department members. Only department members can view the content of these channels.

      Option C:

      • Post departmental memos and announcements in the General channel.
      • Use “Meet now” in channels for ad hoc meetings. For regular department meetings, create a recurring Teams calendar event for the specific department channel (Option A) or the General channel (Option B). Remember that all members of a team can join a public channel meeting.

      Workspace #2: A cross-functional committee

      Scenario: Your organization has struck a committee composed of members from different departments. The rest of the organization should not have access to the work done in the committee.

      Purpose: To analyze a particular organizational challenge and produce a plan or report; to confidentially develop or carry out a series of processes that affect the whole organization.

      Jobs: Committee members must be able to:

      • Attend private meetings.
      • Share files confidentially.

      Solution:

      Ingredients:

      • Private team

      Construction:

      • Create a new private team for the cross-functional committee.
      • Add only committee members to the team.
      • Create channels based on the topics likely to be the focal point of the committee work.
      • Decide how you will use the mandatory General channel. If the committee is small and the work limited in scope, this channel may be the main communication space. If the committee is larger or the work more complex, use the General channel for announcements and move discussions to new topic-related channels.
      • Schedule recurring committee meetings in the Teams calendar. Add the relevant channel to the meeting invite to keep the meeting chat attached to this team and channel (as meeting organizer, put your name in the meeting invite notes, as the channel will show as the organizer in the Outlook invite).
      • Remember that all members of this team will have access to these meetings and be able to view that they are occurring.

      Workspace #3: An innovation day event

      Scenario: The organization holds a yearly innovation day event in which employees form small groups and work on a defined, short-term problem or project.

      Purpose: To develop innovative solutions and ideas.

      Jobs:

      • Convene small groups.
      • Work toward time-sensitive goals.
      • Communicate synchronously.
      • Share files.

      Solution:

      Ingredients:

      • Public team
      • Channel tabs
      • Whiteboard
      • Planner

      Construction:

      • Create a team for the innovation day event.
      • Add channels for each project working group.
      • Communicate to participants the schedule for the day and their assigned channel.
      • Use the General channel for announcements and instructions throughout the day. Ensure someone moderates the General channel for participants’ questions.
      • Pre-populate the channel tabs with files the participants need to work with. To add a scrum board, refer to M#4 (Morning stand-up/Scrum) in this slide deck.
      • For breakouts, instruct participants to use the “meet now” feature in their channel and how to use the Whiteboard during these meetings.
      • Arrange to have your IT admin archive the team after a certain point so the material is still viewable but not editable.

      Workspace #4: A non-work-related social event

      Scenario: Employees within the organization wish to organize social events around shared interests: board game clubs, book clubs, TV show discussion groups, trivia nights, etc.

      Purpose: To encourage cohesion among coworkers and boost morale.

      Jobs:

      • Schedule the event.
      • Invite participants.
      • Prepare the activity.
      • Host and moderate the discussion.

      Solution:

      Ingredients:

      • Public team
      • Private channels
      • Screen-sharing

      Construction:

      • Create a public team for the social event so that interested people can find and join it.
      • Example: Trivia Night
        • Schedule the event in the Teams calendar.
        • Publish the link to the Trivia Night team where other employees will see it.
        • Create private channels for each trivia team so they cannot see the other competitors’ discussions. Add yourself to each private channel so you can see their answers.
        • As the host, begin a meeting in the General channel. Pose the trivia questions live or present the questions on PowerPoint via screen-sharing.
        • Ask each team to post its answers to its private channel.
      • To avoid teams sprawl, ask your IT admin to set a deletion policy for the team, as long as this request does not contradict your organization’s policies on data retention. If the team becomes moribund, it can be set to auto-delete after a certain period of time.

      Workspace #5: A project team with a defined end time

      Scenario: Within a department/workplace team, employees are assigned to projects with defined end times, after which they will be assigned to a new project.

      Purpose: To complete project-based work that fulfills business needs.

      Jobs:

      • Oral communication with team members.
      • Synchronous and asynchronous work on project files.
      • The ability to attend scheduled meetings and ad hoc meetings.
      • The ability to access shared resources related to the project.

      Solution:

      If your working group already has its own team within Teams:

      • Create a new public or private channel for the project. Remember that some functionality is not available in private channels (such as Microsoft Planner).
      • Use the channel for the project team’s meetings (scheduled in Teams calendar or through Meet Now).
      • Add a tab that links to the team’s project folder in SharePoint.

      If your workplace team does not already have its own team in Teams:

      • Determine if there is a natural fit for this project as a new channel in an existing team. Remember that all team members will be able to see the channel if it is public and that all relevant project members need to belong to the Team to participate in the channel.
      • If necessary, create a new team for the project. Add the project members.
      • Create channels based on the type of work that comprises the project.
      • Use the channel for the project team’s meetings (scheduled in Teams calendar or through Meet Now)
      • Add a tab to link to the team’s project folder in SharePoint.

      Info-tech Best Practice

      Hide the channel after the project concludes to de-clutter your Teams user interface.

      Meeting #1: Job interview with external candidate

      Scenario: The organization must interview a slate of candidates to fill an open position.

      Purpose:

      • Select the most qualified candidate for the job.

      Jobs:

      • Create a meeting, ensuring the candidate and other attendees know when and where the meeting will happen.
      • Ensure the meeting is secure to protect confidential information.
      • Ensure the meeting is accessible, allowing the candidate to present themselves through audio and/or visual means.
      • Create a professional environment for the meeting to take place.
      • Engender a space for the candidate to share their CV, research, or other relevant file.
      • The interview must be transcribed and recorded.

      Solution:

      Ingredients:

      • Private Teams meeting
      • Screen-sharing
      • Microsoft Stream

      Construction:

      • Create a Teams meeting, inviting the candidate with their email, alongside other internal attendees. The Teams meeting invite will auto-generate a link to the meeting itself.
      • The host can control who joins the meeting through settings for the “lobby.”
      • Through the Teams meeting, the attendees will be able to use the voice and video chat functionality.
      • All attendees can opt to blur their backgrounds to maintain a professional online presence.
      • The candidate can share their screen, either specific applications or their whole desktop, during the Teams meeting.
      • A Teams meeting can be recorded and transcribed through Stream. After the meeting, the transcript can be searched, edited, and shared

      NB: The external candidate does not need the Teams application. Through the meeting invite, the external candidate will join via a web browser.

      Meeting #2: Quarterly board meeting

      Scenario: Every quarter, the organization holds its regular board meeting.

      Purpose: To discuss agenda items and determine the company’s future direction.

      Jobs:

      During meeting:
        • Attendance and minutes must be taken.
        • Votes must be recorded.
        • In-camera sessions must occur.
        • External experts must be included.
      After meeting:
      • Follow-up items must be assigned.
      • Reports must be submitted.

      Solution:

      Ingredients:

      • Teams calendar invite
      • Planner; Forms
      • Private channel
      • Microsoft Stream

      Construction:

      • Guest Invite: Invites can be sent to any non-domain-joined email address to join a private, invitation-only channel within the team controlled by the board chair.
      • SharePoint & Flow: Documents are emailed to the Team addresses, which kicks off an MS Flow routine to collect review notes.
      • Planner: Any board member can assign tasks to any employee.
      • Forms/Add-On: Chair puts down the form of the question and individual votes are tracked.
      • Teams cloud meeting recording: Recording available through Stream. Manual edits can be made to VTT caption file. Greater than acceptable transcription error rate.
      • Meeting Log: Real-time attendance is viewable but a point-in-time record needs admin access.

      NB: The external guests do not need the Teams application. Through the meeting invite, the guests will join via a web browser.

      Meeting #3: Weekly team meeting

      Scenario: A team meets for a weekly recurring meeting. The meeting is facilitated by the team lead (or manager) who addresses through agenda items and invites participation from the attendees.

      Purpose: The purpose of the meeting is to:

      • Share information verbally
      • Present content visually
      • Achieve consensus
      • Build team morale

      Jobs: The facilitator must:

      • Determine participants
      • Book room
      • Book meeting in calendar

      Solution:

      Ingredients:

      • Meeting Place: A channel in Microsoft Teams (must be public) where all members of the meeting make up the entirety of the audience.
      • Calendar Recurrence: A meeting is booked through Teams and appears in all participants’ Outlook calendar.
      • Collaboration Space: Participants join the meeting through video or audio and can share screens and contribute text, images, and links to the meeting chat.

      Construction:

      • Ensure your team already has a channel created for it. If not, create one in the appropriate team.
      • Create the meeting using the calendar view within Microsoft Teams:
        • Set the meeting’s name, attendees, time, and recurrence.
        • Add the team channel that serves as the most appropriate workplace for the meeting. (Any discussion in the meeting chat will be posted to this channel.)

      NB: Create the meeting in the Teams calendar, not Outlook, or you will not be able to add the Teams channel. As meeting organizer, put your name in the meeting invite notes, as the channel will show as the organizer in the Outlook invite.

      Meeting #4: Morning stand-up/scrum

      Scenario: Each morning, at 9am, members of the team meet online.

      Purpose: After some pleasantries, the team discusses what tasks they each plan to complete in the day.

      Jobs: The team leader (or scrum master) must:

      • Place all tasks on a scrum board, each represented by a sticky note denoting the task name and owner.
      • Move the sticky notes through the columns, adjusting assignments as needed.
      • Sort tasks into the following columns: “Not Started,” “In Progress,” and “Done.”

      Solution:

      Ingredients:

      • Meeting Place: A channel in Microsoft Teams (must be public) where all members of the meeting make up the entirety of the audience.
      • Scrum Board: A tab within that channel where a persistent scrum board has been created and is visible to all team members.

      Meeting Place Construction:

      • Create the meeting using the calendar view in Teams.
      • Set the meeting’s name, attendees, time, and work-week daily recurrence (see left).
      • Add the channel that is the most appropriate workplace for the meeting. Any meeting chat will be posted to this channel rather than a separate chat.

      Scrum Board Construction:

      • Add a tab to the channel using Microsoft Planner as the app. (You can use other task management apps such as Trello, but the identity integration of first-party Office 365 tools may be less hassle.)
      • Create a new (or import an existing) Plan to the channel. This will be used as the focal point.

      Meeting #5: Weekly team meeting

      Scenario: An audio-only conversation that could be a regularly scheduled event but is more often conducted on an ad-hoc basis.

      Purpose: To quickly share information, achieve consensus, or clarify misunderstandings.

      Jobs:

      • Dial recipient
      • See missed calls
      • Leave/check voicemail
      • Create speed-dial list
      • Conference call

      Solution:

      Ingredients:

      • Audio call begun through Teams chat.

      Construction:

      • Voice over IP calls between users in the same MS Teams tenant can begin in multiple ways:
        • A call can be initiated through any appearance of a user’s profile picture: hover over user’s profile photo in the Chat list and select the phone icon.
        • Enter your last chat with a user and click phone icon in upper-right corner.
        • Go to the Calls section and type the name in the “Make a call” text entry form.
      • Voicemail: Voicemail, missed calls, and call history are available in the Calls section.
      • Speed dial: Speed dial lists can be created in the Calls section.
      • Conference call: Other users can be added to an ongoing call.

      NB: Microsoft Teams can be configured to provide an organization’s telephony for external calls, but this requires an E5 license. Additional audio-conferencing licenses are required to call in to a Teams meeting over a phone.

      Bibliography 1/4

      Section 1: Teams for IT › Creation Process

      Overview: Creation process
      Assign admin roles
      Prepare the network
      Team creation
      Integrations with SharePoint Online
      Permissions

      Bibliography 2/4

      Section 1: Teams for IT › Creation Process (cont'd.)

      External and guest access
      Expiration and archiving
      Retention and data loss prevention
      Teams telephony

      Bibliography 3/4

      Section 1: Teams for IT › Teams Rollout

      From Skype to Teams
      From Slack to Teams
      Teams adoption

      Section 1: Teams for IT › Use Cases

      Bibliography 4/4

      Section 2: Teams for End Users › Teams, Channels, Chat

      Section 2: Teams for End Users › Meetings and Live Events

      Section 2: Teams for End Users › Use Cases

      Implement a Social Media Program

      • Buy Link or Shortcode: {j2store}560|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
      • IT is being caught in the middle of various business units, all separately attempting to create, staff, implement, and instrument a social media program.
      • Requests for procuring social media tools and integrating with CRM systems are coming from all directions, with no central authority governing a social media program or coordinating business goals.
      • Public Relations and Corporate Communications groups have been acting as the first level of response to social media channels since the company’s first Twitter account went live, but the volume of inquiries received through social channels has become too great for these groups to continue in a first responder role.

      Our Advice

      Critical Insight

      • Social media immaturity is an opportunity for IT leadership. As with so many of the “next new things,” IT has an opportunity to help the business understand social media technologies, trends, and risks, and coordinate efforts to approach social media as a united company.
      • Social media maturity must reach the Social Media Steering Committee stage before major investments in technology can proceed. As with all business initiatives, technology automation decisions cannot be made without respect to organizational and process maturity. Social media strategy stakeholders must join together and form a steering committee to create policies and procedures, govern strategy, develop workflows, and facilitate technology selection processes. IT not only belongs on such a steering committee, but it can also be instrumental in the formation of it.
      • Info-Tech’s research repeatedly indicates that the greatest return from social media investments is in the customer service domain, by reacting to incoming social inquiries and proactively listening to social conversations for product and service inquiry opportunities. This means CRM integration is essential to long-term social media program success.

      Impact and Result

      • Assess your organization’s social maturity to know where to begin and where to go in implementation of a social media program.
      • Form a social media steering committee to bring order to chaos among different business units.
      • Develop comprehensive workflows to categorize and prioritize inquiries, and then route them to the appropriate part of the business for resolution.
      • Consider creating one or more physical social media command centers to process large volumes of social inquiries more efficiently and monitor real-time social media metrics to improve critical response times.

      Implement a Social Media Program Research & Tools

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

      1. Assess your organization's social maturity

      Know where to begin and where to go in implementation of a social media program.

      • Storyboard: Implement a Social Media Program
      • Social Media Maturity Assessment Tool

      2. Form a social media steering committee

      Bring order to chaos among different business units.

      • Social Media Steering Committee Charter Template
      • Social Media Acceptable Use Policy
      • Blogging and Microblogging Guidelines Template

      3. Consider creating one or more physical social media command centers

      Process large volumes of social inquiries more efficiently, and monitor real-time social media metrics to improve critical response times.

      • Social Media Representative
      • Social Media Manager
      [infographic]

      Implement the Next-Generation IT Operating Model

      • Buy Link or Shortcode: {j2store}85|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 Strategy
      • Parent Category Link: /it-strategy

      IT is being challenged to change how it operates to better support evolving organizations by:

      • Considering the needs of customers, end users, and organizational stakeholders simultaneously.
      • Leveraging resources strategically to support the various IT and digital services being offered.
      • Creating a digital services enablement office that can design, monitor, and continuously enhance services.

      Our Advice

      Critical Insight

      • The role of IT is changing, and with that, how IT needs to operate to deliver value is also changing. Don’t get left behind with an irrelevant IT operating model.
      • Elevate your reputation as a leader beyond the CIO role. Mature your organization’s digital services by considering the customer experience first.
      • As recessions, disasters, and pandemics hit, don’t adopt old ways of operating with 2008 centralized models. Embrace a hybrid IT where value sets your organization apart.

      Impact and Result

      • Embrace the Exponential IT Operating Model so you can:
        • Say “yes” to stakeholders trying to provide a better experience for customers and consumers.
        • Leverage data more effectively across your organization.
        • Consider how to integrate and deliver services using resources effectively and strategically.

      Implement the Next-Generation IT Operating Model Research & Tools

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

      1. Implement the Next-Generation IT Operating Model Deck – The next generation operating model for organizations embracing exponential IT.

      This research piece is for any IT leaders looking to support the organization in its post-transformation state by focusing on the customer experience when operating. CIOs struggling with outdated IT operating models can demonstrate true partnership with this digital services next-generation IT operating model.

      • Implement the Next-Generation IT Operating Model Storyboard

      2. Exponential IT Operating Model Readiness Assessment – A tool to assess your organization’s readiness to adopt this next generation of IT operating models.

      Use this tool to determine whether your organization has the fundamental components necessary to support the adoption of an Exponential IT operating model.

      • Exponential IT Operating Model Readiness Assessment

      3. Career Vision Roadmap Tool – A template to create a simple visual roadmap of your desired career progression from CIO to chief digital services officer (CDSO).

      Use this template to create a roadmap on how to transform your career from CIO to CDSO leveraging key strengths and relationships. Focus on opportunities to demonstrate IT’s maturity and the customer experience at the forefront of your decisions.

      • Career Vision Roadmap
      [infographic]

      Further reading

      Implement the Next-Generation IT Operating Model

      The operating model for organizations embracing Exponential IT and transforming into technology-first enterprises.

      Analyst Perspective

      Be the organization that can thrive in an exponential IT world.

      A picture of Carlene McCubbin A picture of Brittany Lutes

      Carlene McCubbin
      Research Practice Lead
      CIO Organizational
      Transformation Practice
      Info-Tech Research Group

      Brittany Lutes
      Research Director,
      CIO Organization Transformation Practice
      Info-Tech Research Group

      IT leaders are increasingly expected to be responsible for understanding and delivering high-value customer experiences. This evolution depends on the distribution and oversight of IT capabilities that are embedded throughout the organizational structure.

      Defining digital strategic objectives, establishing governance frameworks for an autonomous culture, and enabling the organization to act on insightful data are all impossible without a new way of operating that involves the oversight and accountability of advancing IT roles. Through exponential change, functional groups can lose clarity regarding their responsibilities, creating a sense of ambiguity and disorder.

      But adopting a new way of working that supports an exponential IT organization does not have to be difficult. Leveraging Info-Tech Research Group's next-generation operating model, you can clearly demonstrate how the organization will collaborate to deliver on the various digital and IT services. This is no longer just an IT operating model, but a technology-first enterprise model.

      Included in this blueprint:

      Exponential IT Model

      Defines how the Exponential IT model operates and delivers value to the organization.
      This is done by exploring:

      • Exponential IT cultural norms and behaviors
      • Opportunities and risks of the Exponential IT model
      • A breakdown of the embedded, integrated, and centralized aspects of the model
      • Operating model value stream stages
      • An assessment on whether the Exponential IT operating model is right for your organization

      Changing Role of IT Leader

      Defines how chief information officers (CIOs) can operate or elevate their role in this changing operating model.

      • Identifies why the C-suite is changing – again
      • How IT leaders should consider where they will add value in the new operating model
      • Outlines examples of future organization-wide structures and where IT roles are positioned
      • Supports IT leaders in developing themselves to operate in this structure

      Executive Summary

      Your Challenge

      IT is challenged to change how it operates to better support evolving organizations. IT must:

      • Consider the needs of customers, end users, and organization stakeholders simultaneously.
      • Leverage resources strategically to support the various IT and digital services being offered.
      • Create a digital services enablement office to design, monitor, and enhance services continuously.

      While many organizations have projects that support a digital strategy, few have an operating model that supports this digital services strategy.

      Common Obstacles

      Organizations struggle to support the definition and ongoing maintenance of services because:

      • The organization's Digital and IT services offerings are not clear.
      • The functional team accountable to deliver on each IT or Digital service is ambiguous.
      • There are insufficient resources to support all the IT and Digital services being offered.
      • C-suite leaders required to support the services are missing or in the wrong role to effectively lead.
      • Technology has not been standardized to ensure consistency and effectiveness.

      Info-Tech's Approach

      Embrace the IT operating model that focuses on the enablement and delivery of Digital and IT services by:

      • Having technology stakeholders actively collaborate to decide on priorities and deliver on objectives.
      • Leveraging data more effectively across the organization to understand and meet user needs.
      • Ensuring technology architecture and security standards are well-established and followed by all throughout the organization.
      • Allocating dedicated and skilled resources to ensure services can be continuously delivered.

      Info-Tech Insight

      The first IT operating model where customer engagement with IT and Digital Services is at the forefront.

      What is an operating model?

      An IT operating model is a visual representation of the way your IT organization will function using a clear and coherent blueprint. This visualization demonstrates how capabilities are organized and aligned to deliver on the business mission and strategic and technological objectives.

      The should visualize the optimization and alignment of the IT organization to deliver the capabilities required to achieve business goals. Additionally, it should demonstrate the workflow so key stakeholders can understand where inputs flow in and outputs flow out of the IT organization. Investing time in the front-end to get the operating model right is critical. This will give you a framework to rationalize future organizational changes, allowing you to be more iterative and your model to change as the business changes.

      An image of a sample Operating Model


      From computerization to digitization to the new frontier in autonomization, IT has progressively matured, enabling it to actively lead this next stage of business transformation.

      EXPONENTIAL RISK
      Autonomous processes will integrate with human-led processes, creating risks to business continuity, information security, and quality of delivery. Supplier power will exacerbate business risks.

      EXPONENTIAL REWARD
      The efficiency gains and new value chains created through artificial intelligence (AI), robotics, and additive manufacturing will be very significant. Most of this value will be realized through the augmentation of human labor.

      EXPONENTIAL DEMAND
      Autonomous solutions for productivity and back-office applications will eventually become commoditized and provided by a handful of large vendors. There will, however, be a proliferation of in-house algorithms and workflows to autonomize the middle and front office, offered by a busy landscape of industry-centric capability vendors.

      EXPONENTIAL IT

      Exponential IT involves IT leading the cognitive re-engineering of the organization with evolved practices for:

      • IT governance
      • Asset management
      • Vendor management
      • Data management
      • Business continuity management
      • Information security management

      To learn more about IT's journey into autonomization, check out Info-Tech Research Group's Adopt an Exponential IT Mindset blueprint.

      The IT operating model must evolve to respond to exponential change

      • Ensuring customers are not an afterthought to IT leaders. Customers inform how and where IT leaders invest resources to realize organizational objectives.
      • Adopting a formalized approach to service definition and delivery to eliminate silos.
      • Leveraging data throughout the organization to better inform and enable the various digital services in meeting customer demands.
      • Responding to employee demands for development and training opportunities by applying skills in new settings.
      • Having cross-collaboration mechanisms built into the ways of operating to reduce silos across the organization.
      • Enabling services through a strong set of governance and risk mandates and practices.
      • Eliminating the need for IT capabilities to only be within an IT department.

      IT can no longer be just a service provider:

      78% of IT leaders with established digital strategies and 45% of IT leaders with emerging digital strategies are driven by customer experiences.
      Source: Foundry "Digital Business Study,"2023

      40% - The number of CIOs that are responsible for creating new products or services to support revenue generation.
      Source: Foundry, "The State of the CIO," 2023

      This change requires a breakdown of traditional IT-business divisions

      CIOs must recognize that separating IT from the business is restrictive

      • Many organizations have recently completed or are in the process of completing a digital transformation focused on enhanced employee and customer experiences.
      • Post-transformation organizations must change how they operate to continue to deliver on those enhanced experiences, especially for the customer.
      • There must no longer be a wall between IT and the business, but a unified organization offering digital services that include IT components. Already, 81% of work is being performed across the functional boundaries created in an organization (Deloitte, 2023).
      • Effectively designing, delivering, and maintaining these services depends on a Digital Services functional layer, expanding IT's involvement into how the business delivers worthwhile experiences to customers.
      • This Digital Services functional layer will consider whether the new services are better owned by the IT group or another area of the organization.
      • CIOs need to be prepared to adopt a new way of operating or be left to manage a smaller subset of IT functions.

      "I think we've done the IT industry a disservice by constantly referring to IT and the business, artificially creating this wedge."
      – David Vidoni, VP of IT at Pegasystems
      Source: Dan Roberts, CIO, 2023

      Four trends driving an Exponential IT organization include:

      Emerging Technologies

      • 67% of respondents to KPMG's 2022 Global Tech Survey indicated they intend to embrace emerging platforms by the end of 2024.(1)
      • The technology landscape is constantly shifting with artificial intelligence (AI), quantum computing, 5G cellular networks, and next-generation robotics. Each of these technologies requires new capabilities and a new way in which those capabilities are organized.

      Enhanced Customer Experiences

      • 24% of CIOs have been tasked by their CEO to increase the customer experience.(3)
      • Organizations realize that to gain and retain customers, it has become necessary to consistently evaluate service offerings and identify opportunities for enhancement or new services.

      Digital Trust

      • 1/3 of CISOs plan to increase their GRC focus during the next year and 36% have already begun to implement Zero Trust components.(2)
      • Risk and security capabilities mature focusing on defined enterprise accountability, consideration of ethics and inclusivity and proactive security controls.

      Embedded Technology & Skills

      • Spending on embedded software is expected to increase to $21.5 billion by 2027.(4)
      • The technology strategy no longer resides solely within IT. The organization must take ownership of this strategy while they define their digital strategies. Technology services are also embedded.

      (1) "Global Tech Survey," KPMG, 2022
      (2) "Global Digital Trust Insights Report," PwC, 2023
      (3) "State of IT Report," Foundry, 2023
      (4) "Global surge in embedded software demand; here is why," DAC Digital, 2023

      Application of the Four Key Trends on your Exponential IT operating model:

      Respond to Emerging Technology In response to changing customer demands, organizations need to actively seek, assess, and integrate emerging technology offerings easily and effectively. By governing data at an enterprise level and implementing the necessary guardrails in the form of architecture and security standards at the technology layer, it becomes easier to adopt new technologies such as artificial intelligence (AI). This should be tied to any mandated objectives.
      Build Digital Trust Capabilities Finding and hiring the right security professionals has long been a challenge for organizations. In the Exponential IT model, focus on security oversight increases and fewer operational resources are required. The model sees governing IT security processes and vendor delivery as priorities to enable the right technology without exposing the organization to undue risk. There should be more security-related capabilities in your Exponential IT model.
      Elevate the Customer Experience Evolving the organization's digital offering requires understanding of and active response to the changing demands of customers. This is accomplished by leveraging information from organization-wide data sources and the modular components of the organization's current digital offerings. The components can be reconfigured (or new ones added) to create digital services for the customer.
      Formalize Embedded Business Technology & Roles Technology is actively included in the organization's business (digital) strategy. This ensures that technology remains an embedded component of how the organization competes in the market, supplies invaluable services, and delivers on strategic objectives. The separation of IT from the organization becomes redundant.
      Visualize your IT Operating Model.

      Adopting an Exponential IT operating model is typically influenced by resonating with the following drivers:

      Culture

      IT Strategy & Objectives

      Organization Operating Model

      Organization Size & Structure

      Perception of IT

      Risk Appetite

      A cooperative and innovative culture where the organization does not feel constrained by current processes. Establishing a growth mindset across all the organization's groups is reflected by the trust service owners receive.

      Focused on delivering the best customer experience. The roadmap would include ample opportunities to better support the customer in obtaining or exceeding the degree of value they receive from the organization.

      Empowering service owners across the organization to be accountable for the delivery and value of their services. Lots of collaboration among stakeholders who know what services are offered and how those services leverage technology.

      More appropriate for larger organizations due to the resources required to design and enable successful services. IT resources would also be pooled by skills.

      IT is not a service provider but an equal that enables the organization's success. Without IT involvement, digital services may be omitted and opportunities to enhance the customer experience would be missed.

      While innovation and new service offerings are critical to success, there are functional groups that remain focused on defining the level of risk tolerance that supports the appropriate risk appetite to consider new service offerings.

      Section 1: The Next-Generation Operating Model

      The Technology Value Trinity

      Delivery of Business Value & Strategic Needs

      I&T OPERATING MODEL

      DIGITAL & TECHNOLOGY STRATEGY

      I&T GOVERNANCE

      The model for how IT is organized to deliver on business needs and strategies.

      The identification of objectives and initiatives necessary to achieve business goals.

      Ensures the organization and its customers extract maximum value from the use of information and technology.

      All three elements of the Technology Value Trinity work together to deliver business value and achieve strategic needs. As one changes, the others must change as well.
      How do these three elements relate?

      • I&T Operating Model aligns resources, processes, measures, stakeholders, value streams, and decision rights to enable the delivery of your strategy and priorities. This is done by strategically structuring IT capabilities in a way that enables the organization's vision and considers the context in which the model will operate.
      • Digital and IT Strategy tells you what you must achieve to be successful. For an Exponential IT organization, customer demands and digital service offerings would drive strategic decisions.
      • I&T Governance is the confirmation of IT's goals and strategy, which ensures the alignment of IT and business strategy. This is the mechanism by which you continuously prioritize work so that what is delivered aligns with the strategy.

      Strategy, operating models, and governance are too often considered separate practices – strategies are defined without clarity on how to support. A significant change to your strategy necessitates a change to your operating model, which in turn necessitates a change to your governance and organizational structure.

      The Exponential IT operating model delivers value across seven components

      Exponential IT

      Capabilities

      Products, Services and Technology

      Performance Measures

      Stakeholder Engagement & Collaboration

      Decision Rights & Authority

      Value Streams

      Sourcing

      IT capabilities in the Exponential IT model are spread across the organization. The result removes the separation between IT and the organization. Instead, the organization takes accountability for ensuring technology capabilities are delivered.

      Digital service offerings dominate this model, focusing on providing better experiences for customers. Some technology platforms are specific to a service such as access management, while others span service offerings such as architecture or security.

      This model's success is measured by the overall ability to satisfy the customer experience through designing and delivering the right digital service offerings. Service owners are responsible for continuously monitoring and advancing the delivery of the service.

      The end-customer is the main stakeholder for this operating model, where understanding their needs and demands informs the design, maintenance, and improvement of all services. There is no longer IT vs. the business but an organizational perspective of services.

      This model's decision-making spans the organization. The service owners of digital offerings have authority and autonomy deciding which services to design, how they should be integrated with other services, and how those services will continually deliver value to customers.

      Exponential IT's five core value streams are:

      1. Identifying and prioritizing customer needs
      2. Designing IT and Digital Services
      3. Enabling IT & Digital Service success
      4. Assigning skilled employees to deliver services
      5. Owning & managing services

      Internal resource pools might need to be supplemented with contract resources when demand exceeds capacity, requiring a strong partnership with the Vendor Management Team. Service owners will also need to engage and manage the performance of their vendor solution partners.

      Organizations adopting the Exponential IT Model will experience new norms and behaviors

      Customer-Centric
      Dedicated to the customer experience and making sure that the end customer is considered first and foremost.

      "Yes" Approach
      The organization can say yes to emerging technology and customer desires because it has organized itself to be agile in its digital service offerings.

      Digital Service Ownership
      Digital service offerings are owned and managed across the organization ensuring the continuous delivery of value to customers.

      Employee Development
      Resources are organized into pods based on specific skills or functions increasing the likelihood of adopting new skills.

      Autonomization
      Centralized and accessible data provides service owners autonomy when making informed decisions that support enhanced customer experiences.

      Exponential IT is an embedded model approach

      Info-Tech has identified seven common IT operating model archetypes. Each model represents a different approach to who delivers technology services and how. Each model is designed to drive different outcomes, as the way your organization is structured will dictate the way it behaves. The Exponential IT model is an emerging archetype which capitalizes on embedded delivery.

      An image of the exponential IT embedded model approach.

      Centralized

      Shifted

      Embedded

      Owned and operated by leadership within IT. IT takes full responsibility of the functional areas and maintains control over the outcomes.

      Can be owned/operated by a variety of leadership roles throughout the organization. This can shift from IT ownership to other organizational leadership. Decisions about ownership are often made to enable quick response or mitigate risks.

      Owned/operated by leadership outside of traditional IT. Another area of the organization has taken authoritative power over the outcome of this functional area for a quicker response.

      Even as an embedded IT operating model, shifted and centralized IT functions as support

      1. Embedded functions required for scaled autonomation
        Definition and oversight of the organization's strategic direction demonstrated through a customer-first culture, data insights, and a well-defined risk appetite.
      2. Integrated design and optimization of the digital service offering
        Actively considers the customer experience and designs the appropriate services to be delivered. Considers all aspects in the design and delivery of services by exploring opportunities to integrate components to enhance customer experiences or architecting new service offerings to eliminate gaps.
      3. Centralized standards for IT technology, security & resources
        Technology functions continue to deliver exceptional services to the enterprise including clear standards for technology and solution architecture, application of security requirements, and resources to enable various service offerings.

      Opportunities and risks of the Exponential IT model

      Opportunities

      Risks
      • Focused on the end-customer experience and how to ensure that customer remains satisfied and loyal to the organization.
      • The capability center allows resources to be used strategically according to where they would most improve the customer experience.
      • Services are owned by the most appropriate areas within the organization—sometimes IT and other times not. In either case, services should always possess technological knowledge.
      • The organization's transformation strategy is not just driving IT's strategy but how IT should be organized and operating. This eliminates disconnect from larger strategic objectives.
      • Data intelligence and customer insights enable the shifted and centralized areas of the operating model to deliver effective and valuable experiences for all stakeholders.
      • Requires a high degree of maturity to support a variety of individuals in owning IT and digital capabilities.
      • Organizational buy-in to this operating model archetype is a must. IT cannot select this operating model without that support.
      • Processes around how all IT and Digital Services consider security and technology standards need to be well-documented and enforceable.
      • Depending on which leaders oversee the three areas of the model (embedded, shifted, or centralized), power struggles could occur which negatively impact services.
      • This model will demand governance, risk, and culture to be at the forefront of how it operates. If an accountability framework does not exist, expect this model to fail.

      The Exponential IT operating model blends embedded, shifted and centralized delivery to balance agility & risk

      An image of the Exponential IT Operating Model.

      The Exponential IT model commands a new placement and significance of IT capabilities

      Using capabilities for the operating model

      • Capabilities are focused on the entire system that would be in place to satisfy a particular need. This not only includes the people who are able to complete a specific task, but the technology, processes, and resources required to deliver.
      • Focusing on capabilities rather than the individuals in organizational redesign enables a more objective and holistic view of what your organization is striving toward.
      • Capabilities deliver on specific need(s) and how they are organized changes the way those needs are delivered.
      The Exponential IT principles as an image: Strategy and Governance, Financial Management, Service Planning and Architecture, People and Resources, Security and Risk, Applications, Data and Analytics, Infrastructure and Operations, and PPM and Projects.

      1. Embedded functions required for autonomization

      Overview of the function:

      • Focuses on a single strategy and roadmap for the organization that actively includes technology.
      • Governance, risk, compliance, and general oversight are defined and embedded throughout the organization.
      • Ensures that quality data is being generated to help inform the defined digital service offering.
      • Readies the organization to adopt emerging technology quickly and with minimal disruption to other digital service offerings.
      • A team of technical experts that decides what information should exist for operational efficiency or service innovation.

      Embedded functions required for autonomization

      2. Integrated design and optimization of the digital service offering

      Overview of the function:

      • Analyzes and responds to insights about the customer experience.
      • Maintains the portfolio of the organization's digital service offerings.
      • Considers what is necessary to operate efficiently as an organization while simultaneously exploring emerging technology to optimize new or existing digital services.
      • Requires the expertise and involvement of both business-minded and technology-skilled resources.
      • The differentiating factor from other IT operating models is how it holistically considers all the components throughout the organization and how they are connected.

      Integrated design and optimization of the digital service offering

      3. Centralized standards for IT technology, security & resources

      Overview of the function:

      • Compared with other IT operating model archetypes, the Exponential IT model has fewer capabilities that are centralized within the technology function of an organization.
      • Architecture and standards are the foundation of successful embedded delivery, ensuring reuse, improved integration, and a unified experience. This includes technology, risk, data, AI and security architecture, models, and standards.
      • Employee resources are also organized in pods to be leveraged based on greatest need and skills availability.
      • This lets the organization be more agile when innovating and implementing new digital service offerings.

      Centralized standards for IT technology, security & resources

      Exponential IT explores new value stream stages

      Customer Perspective

      The organization is continually anticipating their wants and needs and establishing mechanisms to vocalize those needs.

      Customer receives the right IT and digital services to respond to their needs.

      The service is easy to use and continuously responds to wants and needs.

      The service is meeting expectations or exceeding them.

      There is a dedicated service owner who can hear demands and feedback, then action desirable outcomes.

      Value Stream Stages

      An image of the Value Stream

      Organizational Perspective

      Expected Outcome

      Customers' wants and needs are understood and at times anticipated before the customer requests them.

      Assess needs to determine if service is already offered or needs to be created. Design services that will enhance the customer experience.

      Look for opportunities to integrate processes and resources to increase the performance of IT and Digital Services.

      Ensure that the right employees with the right skills are working to develop or enhance service offering.

      The service owner manages the ongoing lifecycle of the service and establishes a roadmap on how value will continue to be delivered.

      Critical Processes

      • Customer experience
      • Research and innovation
      • Stakeholder management
      • Research and innovation
      • Service design & portfolio management
      • Performance management
      • Continuous improvement
      • Integration planning
      • Service management
      • Resource planning and allocation
      • Service strategy & roadmap
      • Service governance
      • Service performance management

      Metrics

      • Customer satisfaction score
      • Service-to-need alignment
      • Gaps in service portfolio
      • Speed to design services
      • Service performance
      • Service adoption
      • Time to resolve customer demand
      • Frequency by which service requires enhancements
      • Service satisfaction
      • Alignment of service strategy to organization strategy

      1.1 Assess if the Exponential IT operating model is right for your organization

      1 hour

      1. Begin by downloading the Exponential IT Operating Model Assessment.
      2. Review the questions within each of the operating model components. For each question, use the drop-down menu to determine your level of agreement.
      3. The more your organization agrees with the statements, the more likely your organization is prepared to implement an Exponential IT operating model.
      4. The less your organization agrees with the statements, the more likely you should adopt a different IT operating model.
      5. For support implementing the Exponential IT or another IT operating model, explore the Visualize Your IT Operating Model blueprint (coming soon).

      Input

      • Desire to change the organization's IT & Digital operating model

      Output

      • Desire to implement the IT & Digital Service Enablement operating model

      Materials

      • Exponential IT Operating Model Assessment

      Participants

      • Executive IT leadership
      • Business leadership

      Explore other Info-Tech research to support your organization transformation initiatives

      Visualize the IT Operating Model blueprint (coming soon)

      Visualize the IT Operating Model blueprint (coming soon)

      Redesign Your IT Organizational Structure

      Redesign Your IT Organizational Structure

      Section 2: Elevating the CIO Role

      The next generation of IT C-suite roles are here

      As the operating model changes and becomes increasingly embedded into the organization's delivery of IT and Digital Services, new C-suite roles are being defined

      • One of the most critical roles being defined in this change is the Chief Digital Services Officer (CDSO) who focuses on all components of the digital experience from the lens of the customer.
      • There are two directions from which the CDSO role is typically approached as it gains popularity:
        • CIOs evolve beyond just information and technology—focusing on how IT & Digital Services enhance the customer experience
        • Business leaders who have technical know-how increase their involvement and responsibility over IT related functions
      • IT leaders need to consider where they would rather sit: focused only on technology and remaining a service provider to the organization, or embedding technology into the services, products, and organization in general?

      60%

      The number of APAC CIOs who can anticipate their job to be challenged by their peers within the organization.

      Source: Singh, Yashvendra, CIO, 2023.

      Info-Tech Insight

      This is not about making the CIO report to someone else but allowing the CIO to elevate their role into that of a CDSO.

      Increasing IT leadership's span of control throughout the organization

      As maturity increases so does span of control, ownership & executive influence

      Organizations hoping to fully adopt the Exponential IT operating model require a shift in leadership expectations. Notably, these leaders will have oversight and accountability for functions beyond the traditional IT group.

      As the organization matures its governance, security, and data management practices, increasing how it delivers high-impact experiences to customers, it would have one leader who owns all the components to ensure clear alignment with goals and business strategy.

      An image of a graph where the X axis is labeled Span of Control & Influence, and the Y axis is Organization Maturity.

      Emerging Exponential IT organizations will have distributed authority

      • Organizations beginning their transition toward an exponential model often continue to have distributed leaders providing oversight of distinct functional areas.
      • Their spans of control are smaller, but very clearly defined, eliminating confusion through a transparent accountability framework.
      • Each leader strives toward optimization and efficiency regarding IT capabilities, for which they are responsible.
      1. Distributed Leadership
        Embedded functions required for scaled autonomation
        Distributed leaders identify the ways technology will enable them to advance enterprise objectives while maintaining autonomy over their own functions. They may oversee technology.
      2. Experience Officer
        Integrated design and optimization of the digital service offering
        An Experience Officer will help consider the insights gained from enterprise data and make informed decisions around enterprise service offerings. They actively explore new ways to deliver high-value experiences.
      3. Chief Technology Officer (CTO)
        Centralized standards for IT technology, security & resources
        A CTO will continue to oversee the core technology, including infrastructure and service management functions.

      Established organizations will be driven by a digital transformation journey

      • Organizations that have begun to deliver on their transformation journey will typically see two distinct C-suite leaders emerge—the CIO and the CDO.
      • The Chief Digital Officer (CDO) often explores ways to optimize the integration and management of data to enable insightful decision making from the organization.
      • The Chief Information Officer (CIO), however, considers mechanisms to standardize how new technologies can be integrated with the architecture.
      • While both leaders have distinct responsibilities, their roles intersect at the customer experience.

      An image of the digital transformation journey

      Advanced organizations will be managed by a single emerging role

      • A single leader will oversee all the functional areas where value is delivered and enabled by IT capabilities.
      • Through a large span of control, this leader can holistically consider opportunities to optimize the customer experience and ensure recommendations are actioned to deliver on that enhanced experience.
      • This leader's span of control will require a strong understanding of both strategic and operational functions to authoritatively oversee all aspects for which they are responsible.

      CDSO – Chief Digital Service Officer

      1. Embedded functions required for scaled autonomation
        The CDSO will set, oversee, and manage the delivery of an enterprise's digital strategy, ensuring accountability through good governance and data practices.
      2. Integrated design and optimization of the digital service offering
        They ensure that the enterprise holistically considers the various services that could be offered to exceed customer expectations through high-impact experiences.
      3. Centralized standards for IT technology, security & resources
        They also ensure stable and secure architecture standards to enable consistency across the organization and a seamless ability to integrate new technology to support service offerings.

      Evolution of the IT C-suite now includes the CDSO

      Chief Digital Service Officer

      Chief Information Officer

      Chief Digital Officer

      Chief Technology Officer

      Chief Experience Officer

      Main Stakeholder(s):

      • Board
      • CEO/Executive Leadership
      • Organization Leadership
      • Service Owners
      • Customers & End Users

      Main Responsibilities:

      • Oversight of the entire portfolio of IT and Digital Services
      • Use of information & technology to meet organizational objectives

      *Some leaders in this role are being called Chief Digital Information Officer.

      Main Stakeholder(s):

      • Board
      • CEO/Executive Leadership
      • Organization Leadership
      • End Users

      Main Responsibilities:

      • Oversight of the information and technology required to support and enable the organization

      Main Stakeholder(s):

      • Board
      • CEO/Executive Leadership
      • Customers & End Users

      Main Responsibilities:

      • Oversight on transforming how the organization uses technology, often considering customer perspectives

      Main Stakeholder(s):

      • Organization Leadership
      • Customers & End Users

      Main Responsibilities:

      • Collaborating with the CIO, the CTO leads the organization's ability to integrate and adopt necessary technology products and services

      Main Stakeholder(s):

      • Customers & End Users

      Main Responsibilities:

      • Establish the customer experience strategy
      • Create policies to support that strategy
      • Collaborate with other organizational leaders to integrate any activities around the customer experience

      Examples of what the emerging organizational structure can look like

      An image of three hierarchies, showing what the emerging organizational structure can look like.

      This is more than a new title for IT leaders

      It's about establishing a business first perspective

      • IT leaders exploring this new way of operating are not just adopting the new title of CDSO or CDIO.
      • These leaders must change how information, technology, and digital experiences are consumed across the various stakeholders – especially the end customer.
      • IT leaders who pursue this new IT operating model choose to be more than order takers for an organization.
      • They are:
        • Partners in defining the organization's digital service offerings
        • Recognizing the benefits of distributing decision-making authority for IT-related aspects to others throughout the organization
        • Prioritizing capabilities like portfolio management, architecture, vendor management, relationship management, cloud and user experience

      "'For me, the IT portfolio for the next few years and the IT architecture have taken the place that IT strategy used to have,' he adds. This view doesn't position IT outside of the organization, but rather gives it central importance in the company."
      – Bernd Rattey, Group CIO and CDO of Deutsche Bahn (DB), qtd. by Jens Dose, CIO, 2023

      1.2 Plan your career move to CDSO

      1-3 hours

      • Create a roadmap on how to move from your current role to CDSO by identifying current strengths and opportunities to improve.
      • Download the Career Vision Roadmap Tool from the website. An example of this is on the next slide.
      • Document the tagline. This is your overarching career focus and goal – what is your passion? Think beyond titles to what you want to be doing, the atmosphere you want to be in, and what you want to add value to.
      • Document the current role: what are the strengths, achievements and opportunities?
      • Consider the CDSO role: how will you build stronger relationships and competencies to elevate your profile within the organization? What is an example of what someone would display in this role?
      • Define specific roles or stakeholders that you should develop a stronger relationship with.

      Download the Career Vision Roadmap Tool

      Input

      • Desire to implement the IT & Digital Service Enablement Operating Model

      Output

      • Roadmap to elevate from a CIO to a CDSO

      Materials

      • Career Vision Roadmap
      • IT & Digital Services Enablement operating model archetype
      • CDSO job profile

      Participants

      • CIO (or any other role aspiring to eventually become a CDSO)
      • Individual activity

      Career Vision Roadmap:
      Executive Leader
      Akbar K.

      Sample

      To provide customers with an exceptional experience by ensuring all IT and Digital Services consider and anticipate their needs or wants. Enable IT and Digital Services to be successful through clear leadership, strong collaboration, and continuous improvement or innovation.

      CIO

      1. Establish technology standards that enable the organization to consistently and securely integrate platforms or solutions.
      2. Lead the project team that defined and standardized the organization's reference architecture.
      3. Need to work on listening to a variety of stakeholder demands rather than only specific roles/titles.

      Transition

      • Strengths: Technology acumen, budget planning, allocating resources
      • Enhance: Stakeholder relationship management.
      • Work with current CDO to define and implement more digital transformation initiatives.

      CDSO

      • Being responsive to customer expectations and communicating clear and realistic timelines.
      • Establish trust among the organization that services will deliver expected value.
      • Empowering service owners to manage and oversee the delivery of their services.

      Network Opportunities

      • Connect with board members and understand each of their key areas of priority.
      • Begin to interact with end customers and define ways that will enhance their customer experience.
      • Chief Digital Officer

      Actions now in line with aspiration

      Appendix: Capabilities & Capability Model

      IT and digital capabilities

      Using capabilities for the operating model:

      • Capabilities are focused on the entire system that would be in place to satisfy a particular need. This not only includes people who have skills to complete a specific task, but also the technology, processes, and resources required to deliver.
      • Focusing on capabilities rather than the individuals in organizational redesign enables a more objective and holistic view of what your organization is striving toward.
      • Capabilities deliver on specific need(s) and how they are organized changes the way those need(s) are delivered.

      An image of the IT Management and Governance Framework.

      Strategic Direction

      • IT Governance
      • Strategic Planning
      • Digital Strategy
      • Performance Measurement
      • IT Management & Policies
      • Organizational Quality Management
      • R&D and Innovation
      • Stakeholder Management

      People & Resources

      • Strategic Communications
      • People Resource Management
      • Workforce Strategy & Planning
      • Organizational Change Enablement
      • Adoption & Training
      • Financial/Budget Management
      • Vendor Portfolio Management
      • Vendor Selection & Contract Management
      • Vendor Performance Management

      Architecture & Integration

      • Enterprise Architecture Delivery
      • Business Architecture Delivery
      • Solution Architecture Delivery
      • Technology Architecture
      • Data Architecture
      • Security Architecture
      • Process Integration
      • Integration Planning

      Service Planning

      • Service Governance
      • Service Strategy & Roadmap
      • Service Management
      • Service Governance
      • Service Performance Measurement
      • Service Design & Planning
      • Service Orchestration

      Security & Risk

      • Security Strategic Planning
      • Risk Management
      • External Compliance Management
      • Security Response & Recovery Management
      • Security Management
      • Controls & Internal Audit Planning
      • Security Defense Operations
      • Security Administration
      • Cybersecurity Threat Intelligence
      • Integrated Physical/IT Security
      • OT/IoT Security
      • Data Protection & Privacy

      Application Delivery

      • Application Lifecycle Management
      • Systems Integration Management
      • Application Development
      • User Experience
      • Quality Assurance & UAT
      • Application Maintenance
      • Low Code Development

      Project Portfolio Management

      • Demand Management
      • Requirement Analysis Management
      • Portfolio Management
      • Project Management

      Data & Business Intelligence (BI)

      • Reporting & Analytics
      • Data Management
      • Data Quality
      • Data Integration
      • Enterprise Content Management
      • Data Governance
      • Data Strategy
      • AI/ML Management

      Service Delivery

      • Operations Management
      • Service Desk Management
      • Incident Management
      • Problem Management
      • Service Enhancements
      • Operational Change Enablement
      • Release Management
      • Automation Management

      Infrastructure & Operations

      • Asset Management
      • Infrastructure Portfolio Strategic Planning
      • Availability & Capacity Management
      • Network & Infrastructure Management
      • Configuration Management
      • Cloud Orchestration
      An image of the summary slide for this blueprint, with the headings: Centralized; Shifted; and Embedded.

      Research Contributors and Experts

      Donna Bales
      Principal Research Director
      Info-Tech Research Group

      Scott Bickley
      Practice Lead – Vendor Management Practice
      Info-Tech Research Group

      Christine Coz
      Executive Counselor – Executive Services
      Info-Tech Research Group

      Valence Howden
      Principal Research Director
      Info-Tech Research Group

      Duraid Ibrahim
      Executive Counselor – Executive Services
      Info-Tech Research Group

      Chris Goodhue
      Managing Partner– Executive Services
      Info-Tech Research Group

      Carlene McCubbin
      Practice Lead – CIO Practice
      Info-Tech Research Group

      Mike Tweedie
      Practice Lead – CIO Practice
      Info-Tech Research Group

      Vicki van Alphen
      Executive Counselor – Executive Services
      Info-Tech Research Group

      *Plus an additional 5 industry experts who anonymously contributed to this research piece.

      Related Info-Tech Research

      Adopt an Exponential IT Mindset

      • To succeed in the coming business transformation, IT will have to adopt different priorities in its mission, governance, capabilities, and partnerships.
      • CIOs will have to provide exceptionally mature services while owning business targets.

      Become a Transformational CIO

      • 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.
      • Elevate your stature as a business leader.
      • Create a high-powered IT organization that is focused on driving lasting change, improving client experiences, and encouraging collaboration across the entire enterprise.

      Define Your Digital Business Strategy

      • Design a strategy that applies innovation to your business model, streamline and transform processes, and make use of technologies to enhance interactions with customers and employees.
      • Pre-pandemic digital strategies have been primarily focused on automation. However, your post-pandemic digital strategy must focus on driving resilience for growth opportunities.

      Bibliography

      Bennet, Trevon. "What is a Chief Experience Officer (CXO)? And what do they do?" Indeed, 14 March 2023. https://www.indeed.com/career-advice/finding-a-job/what-is-chief-experience-officer#:~:text=A%20CXO%20plans%20strategies%20and,customer%20acquisition%20and%20retention%20strategies
      Bishop, Carrie. "Five years of Digital Services in San Francisco." Medium, 20 January 2022. https://medium.com/san-francisco-digital-services/five-years-of-digital-services-in-san-francisco-805a758c2b83
      DAC Digital and Chawla, Yash. "Global surge in embedded software demand; here is why." DAC Digital, 2023 <ttps://dac.digital/global-surge-in-embedded-software-demand-here-is-why/
      Deloitte. "If you want your digital transformation to succeed, align your operating model to your strategy." Harvard Business Review, 31 January 2020. https://hbr.org/sponsored/2020/01/if-you-want-your-digital-transformation-to-succeed-align-your-operating-model-to-your-strategy.
      Deloitte. "2023 Global Human Capital Trends Report." Deloitte, 2023. https://www2.deloitte.com/content/dam/Deloitte/sg/Documents/human-capital/sea-cons-hc-trends-report-2023.pdf
      Dose, Jens. "Deutsche Bahn CIO on track to decentralize IT." CIO, 19 April 2023. https://www.cio.com/article/473071/deutsche-bahn-cio-on-track-to-decentralize-it.html
      Ehrlich, Oliver., Fanderl, Harald., Maldara, David., & Mittangunta, Divya. "How the operating model can unlock the power of customer experience." McKinsey, 28 June 2022. https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/how-the-operating-model-can-unlock-the-full-power-of-customer-experience
      FCW. "Digital Government Summit Agenda." FCW. 2021. https://events-archive.fcw.com/events/2021/digital-government-summit/index.html
      Foundry. "State of the CIO." IDG, 25 January 2023. https://foundryco.com/tools-for-marketers/research-state-of-the-cio/
      Foundry. "Digital Business Study 2023: IT Leaders are future-proofing their business with digital strategies." IDG, 2023. https://foundryco.com/tools-for-marketers/research-digital-business/
      Indeed Editorial Team. "Centralized vs. Decentralized Structures: 7 Key Differences." Indeed, 10 March 2023. https://www.indeed.com/career-advice/career-development/centralized-vs-decentralized
      Indeed Editorial Team. "What is process integration?." Indeed, 14 November 2022. https://ca.indeed.com/career-advice/career-development/process-integration#:~:text=Process%20integration%2C%20or%20business%20process,it%20reach%20its%20primary%20objectives
      KPMG International. "Global Tech Report." KPMG, 2022.
      McHugh, Brian. "Service orchestration is reshaping IT—Here's what to know." Active Batch, 8 November 2022. https://www.advsyscon.com/blog/service-orchestration-what-is/
      Morris, Chris. "IDC FutureScape: Worldwide CIO Agenda 2023 Predictions."" IDC, January, 2023. https://www.idc.com/getdoc.jsp?containerId=AP49998523
      PwC. "Global Digital Trust Insights Report." PwC, 2023
      Roberts, Dan. "5 CIOs on building a service-oriented IT culture." CIO, 13 April 2023. https://www.cio.com/article/472805/5-cios-on-building-a-service-oriented-it-culture.html
      Singh, Yashvendra. "CIOs must evolve to stave off existential threat to their role." CIO, 30 March 2023. https://www.cio.com/article/465612/cios-must-evolve-to-stave-off-existential-threat-to-their-role.html
      Spacey, John. "16 Examples of IT Services." Simplicable, 28 January 2018. https://simplicable.com/IT/it-services

      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.

      The Rush Trap: Why "Move Fast and Break Things" Breaks Your Business

      • Large vertical image:

      Most business leaders think that the best way to beat the competition is to push their development teams harder and demand faster delivery. I've seen the opposite happen many times.

      When you prioritize "shipping fast" and "getting to market first," you often end up taking the longest time to succeed, because your team must spend months, sometimes years, addressing the problems caused by your haste. On the surface, things appear to be improving, but internally, they can feel overwhelming. You will notice this impact on your staff.

      This is the harsh truth about rushing IT development:

      Every Shortcut Creates Two New Problems

      Here's what really happens in the codebase when you tell your team to "just get it done fast": you don't do proper input validation and sanitization because you say, "We'll add that later." And then you have to deal with SQL injection attacks and data breaches for months. This wasted time could have been avoided by using simple parameterized queries and validation frameworks.

      In 2024, the average cost of a data breach was $4.88 million. 73% of these breaches require more than 200 days to resolve. You only code for the happy flow, but real users submit incorrect data, experience network timeouts, and encounter failures with third-party APIs. 

      Your app crashes more than it should because you didn't set up proper error handling, or circuit breakers, or graceful degradation patterns. I know these take time to implement, but what would you rather have? Customers abandoning it?

      Businesses lose an average of $5,600 per minute when their systems go down, and e-commerce sites can lose up to $300,000 per hour during busy times. Instead of fixing the root causes of problems, you just patch them up with quick fixes. Instead of proper garbage collection, that memory leak gets a band-aid restart script. Instead of being optimized, the slow database query is cached.

      Soon, you will find yourself struggling to keep your building intact.

      To keep up with technical debt, companies usually have to spend 23–42% of their total IT budget each year.

      You don't do full testing because "writing unit tests takes longer than manual testing." This approach does not include load testing, test-driven development, or integration testing. Your first real test is when you have paying customers in production. Companies that don't test their software properly have 60% more bugs in their products and spend 40% more time fixing them than companies that do.

      You start without being able to properly monitor and see what's going on. There are no logging frameworks, no application performance monitoring, and no health checks in place. When things go wrong—and they will—it's difficult to figure out what's amiss. Without proper monitoring, it takes an average of 4.5 hours to find and fix IT problems. With full observability tools, it only takes 45 minutes.

      It's easy to see that every shortcut you take today will cause two new problems tomorrow. Each of those problems makes two more. You're going to be in a lot of trouble with technical debt, security holes, and unstable systems soon. All because you were in a hurry to meet some random deadline.

      The true cost of rushing in those "move fast and break things" success stories is often overlooked. You don't guarantee a quick time to market when you rush code to market. You're just making sure that failure to market happens quickly. Remember that most Silicon Valley break-movers lose millions, but you never read about those; you only read about the 1 in 350 VC-backed companies that make it. That is a staggering 0.29%. I would not bet on that strategy just yet.

      Because code that is rushed doesn't just break once. It breaks all the time. In production. This issue arises when dealing with real customers. At the worst times. Your developers are putting out fires instead of adding new features. Instead of adding the features that the customer asked for, they're fixing race conditions at 2 AM. They're patching vulnerabilities in dependencies rather than creating the next version.

      According to research, developers in environments with a lot of technical debt spend 42% of their time on maintenance and bug fixes, while those in well-architected systems spend only 23% of their time on these tasks. Bad code drives up your infrastructure costs by requiring more servers to handle the same load. Your database runs slower because no one took the time to make the right indexes or make the queries run faster. Unoptimized applications typically require 3 to 5 times more infrastructure resources, directly impacting your cloud computing and operational costs.

      The costs of getting new customers go up because products that are rushed have higher churn rates. People stop using apps that crash a lot or don't work well. For example, 53% of mobile users will stop using an app if it takes longer than 3 seconds to load. It costs 5 to 25 times more to get a new customer than to keep an old one.

      In the meantime, what about your competitor who took an extra month to set up proper error handling, security controls, and performance optimization? They're growing smoothly while you're still working on the base.

      The Slow Way Is the Quick Way

      Let me tell you a myth that is costing you millions: The race isn't about speed unless you're in a real winner-take-all market with huge network effects. It's about lasting.

      There is usually room for more than one winner in most markets. Your real job isn't to be the first to market; it's to still be there when the "fast movers" fail because they owe too much money. The businesses that are the biggest in their markets aren't usually the first ones there. They are the ones who took the time to use excellent software engineering practices from the start. They used well-known security frameworks like the OWASP guidelines to make their systems safe, set up the right authentication and authorization patterns, and made sure their APIs were designed with security and resilience in mind from the start.

      Companies that have good security practices have 76% fewer security incidents and save an average of $1.76 million for every breach they avoid. They wrote code for failure scenarios using patterns like retry logic with exponential backoff, circuit breakers to stop failures from spreading, and bulkhead isolation to keep problems from spreading.

      They set up full logging and monitoring so they could find problems before customers did. Systems that are built well and have the right resilience patterns are up 99.9% of the time, while systems that are built quickly are up 95% to 98% of the time. While you may believe that 95% to 98% uptime is an acceptable figure to agree to, take a moment to consider what that actually translates to in terms of downtime for your availability metrics. Remember that you should only calculate the times you really want to be available. This is due to the fact that any unavailability during your downtime is not taken into account. But failures do not take your opening hours into consideration. 

      Successful companies used domain-driven design to get the business requirements right, made complete API documentation, and built automated testing suites that found regressions before deployment. Companies that do a lot of testing deliver features 2.5 times faster and with 50% fewer bugs after deployment.

      They made sure that their environments were always the same by using infrastructure as code, setting up the right CI/CD pipelines with automated security scanning and regression testing, and planning for horizontal scaling from the start.

      Companies that have mature DevOps practices deploy 208 times more often and have lead times that are 106 times faster, all while being more reliable.

      What This Means for Your Process of Development

      The truth is that your development schedule isn't about meeting deadlines. The purpose is to create systems that function effectively when real people use them in real-life situations with actual data and at a large scale. If your code crashes under load because you didn't use the right caching strategies or database connection pooling, it doesn't matter how fast it is to market.

      If you neglect to conduct security code reviews and utilize static analysis tools, the likelihood of hacking increases significantly.

      Think about the return on investment: putting in an extra 20–30% up front for the right architecture, security, and testing usually cuts the total cost of ownership by 60–80% over the life of the application.

      The first "delay" of 2 to 4 weeks for proper engineering practices saves 6 to 12 months of fixing technical debt later on.

      You have a simple choice: either take the time to follow excellent software engineering practices now, or spend the next two years telling customers why your system is down again while your competitors take your market share. The companies that last and eventually take over choose quality engineering over random speed. I leave it up to your imagination as to what multi-trillion-dollar company immediately comes to mind.

      I am always up for a conversation.

      Create Visual SOP Documents that Drive Process Optimization, Not Just Peace of Mind

      • Buy Link or Shortcode: {j2store}416|cart{/j2store}
      • member rating overall impact: 9.0/10 Overall Impact
      • member rating average dollars saved: $38,999 Average $ Saved
      • member rating average days saved: 17 Average Days Saved
      • Parent Category Name: DR and Business Continuity
      • Parent Category Link: /business-continuity
      • Writing SOPs is the last thing most people want to do, so the work gets pushed down the priority list and the documents become dated.
      • Most organizations know it is good practice to have SOPs as it improves consistency, facilitates process improvement, and contributes to efficient operations.
      • Though the benefits are understood, many organizations don't have SOPs and those that do don't maintain them.

      Our Advice

      Critical Insight

      • Create visual documents, not dense SOP manuals.
      • Start with high-impact SOPs, and identify the most critical undocumented SOPs and address them first.
      • Integrate SOP creation into project requirements and create SOP approval steps to ensure documentation is reviewed and completed in a timely fashion.

      Impact and Result

      • Create visual documents that can be scanned. Flowcharts, checklists, and diagrams are quicker to create, take less time to update, and are ultimately more usable than a dense manual.
      • Use simple but effective document management practices.
      • Make SOPs part of your project deliverables rather than an afterthought. That includes checking documentation status as part of your change management process.

      Create Visual SOP Documents that Drive Process Optimization, Not Just Peace of Mind Research & Tools

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

      1. Create Visual SOP Documents that Drive Process Optimization, Not Just Peace of Mind – Make SOPs work for you with visual documents that are easier to create and more effective for process management and optimization.

      Learn best practices for creating, maintaining, publishing, and managing effective SOP documentation.

      • Create Visual SOP Documents that Drive Process Optimization, Not Just Peace of Mind – Phases 1-3

      2. Standard Operating Procedures Workbook and Document Management Checklist – Prioritize, optimize, and document critical SOPs.

      Identify required documentation and prioritize them according to urgency and impact.

      • Standard Operating Procedures Workbook
      • Document Management Checklist

      3. Process Templates and Examples – Review and assess templates to find samples that are fit for purpose.

      Review the wide variety of samples to see what works best for your needs.

      • Standard Operating Procedures Project Roadmap Tool
      • System Recovery Procedures Template
      • Application Development Process – AppDev Example (Visio)
      • Application Development Process – AppDev Example (PDF)
      • Network Backup for Atlanta Data Center – Backups Example
      • DRP Recovery Workflow Template (PDF)
      • DRP Recovery Workflow Template (Visio)
      • Employee Termination Process Checklist – IT Security Example
      • Sales Process for New Clients – Sales Example (Visio)
      • Sales Process for New Clients – Sales Example (PDF)
      • Incident and Service Management Procedures – Service Desk Example (Visio)
      • Incident and Service Management Procedures – Service Desk Example (PDF)
      [infographic]

      Further reading

      Create Visual SOP Documents that Drive Process Optimization, Not Just Peace of Mind

      Change your focus from satisfying auditors to driving process optimization, consistent IT operations, and effective knowledge transfer.

      Project Outline

      Two flowcharts are depicted. The first is labelled 'Executive Brief' and the second is labelled 'Tools and Templates Roadmap'. Both outline the following project.

      ANALYST PERSPECTIVE

      Do your SOPs drive process optimization?

      "Most organizations struggle to document and maintain SOPs as required, leading to process inconsistencies and inefficiencies. These breakdowns directly impact the performance of IT operations. Effective SOPs streamline training and knowledge transfer, improve transparency and compliance, enable automation, and ultimately decrease costs as processes improve and expensive breakdowns are avoided. Documenting SOPs is not just good practice; it directly impacts IT efficiency and your bottom line."

      Frank Trovato, Senior Manager, Infrastructure Research Info-Tech Research Group

      Our understanding of the problem

      This Research Is Designed For:

      • IT Process Owners
      • IT Infrastructure Managers
      • IT Service Managers
      • System Administrators
      • And more…

      This Research Will Help You:

      • Identify, prioritize, and document SOPs for critical business processes.
      • Discover opportunities for overall process optimization by documenting SOPs.
      • Develop documentation best practices that support ongoing maintenance and review.

      This Research Will Also Assist:

      • CTOs
      • Business unit leaders

      This Research Will Help Them:

      • Understand the need for and value of documenting SOPs in a usable format.
      • Help set expectations around documentation best practices.
      • Extend IT best practices to other parts of the business.

      Executive summary

      Situation

      • Most organizations know it is good practice to have SOPs as it improves consistency, facilitates process improvement, and contributes to efficient operations.
      • Though the benefits are understood, many organizations don't have SOPs and those that do don't maintain them.

      Complication

      • Writing SOPs is the last thing most people want to do, so the work gets pushed down the priority list and the documents become dated.
      • Promoting the use of SOPs can also face staff resistance as the documentation is seen as time consuming to develop and maintain, too convoluted to be useful, and generally out of date.

      Resolution

      • Overcome staff resistance while implementing a sustainable SOP documentation approach by doing the following:
        • Create visual documents that can be scanned. Flowcharts, checklists, and diagrams are quicker to create, take less time to update, and are ultimately more usable than a dense manual.
        • Use simple, but effective document management practices.
        • Make SOPs part of your project deliverables rather than an afterthought. That includes checking documentation status as part of your change management process.
      • Extend these principles to other areas of IT and business processes. The survey data and examples in this report include application development and business processes as well as IT operations.

      Info-Tech Insight

      1. Create visual documents, not dense SOP manuals.
      2. Start with high-impact SOPs. Identify the most critical undocumented SOPs and document them first.
      3. Integrate SOP creation into project requirements and create SOP approval steps to ensure documentation is reviewed and completed in a timely fashion.

      Most organizations struggle to create and maintain SOP documents, especially in North America, despite the benefits

      North American companies are traditionally more technology focused than process focused, and that is reflected in the approach to documenting SOPs.

      • An ad hoc approach to SOPs almost certainly means documents will be out of date and ineffective. The same is also true when updating SOPs as part of periodic concerted efforts to prepare for an audit, annual review, or certification process, and this makes the task more imposing.
      • Incorporating SOP updates as part of regular change management processes ensures documents are up to date and usable. This can also make reviews and audits much more manageable.

      '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

      Organizations are most likely to update documents on an ad hoc basis or via periodic formal reviews. Less than 25% keep SOPs updated as needed.

      Graph depicting North America versus Asia and Europe practices of document updates

      Source: Info-Tech Research Group; N=104

      Document SOPs to improve knowledge transfer, optimize processes, and ultimately save money

      Benefits of documented SOPs Impact of undocumented/undefined SOPs
      Improved training and knowledge transfer: Routine tasks can be delegated to junior staff (freeing senior staff to work on higher priority tasks). Without documented SOPs: Tasks will be difficult to delegate, key staff become a bottleneck, knowledge transfer is inconsistent, and there is a longer onboarding process for new staff.
      IT automation, process optimization, and consistent operations: Defining, documenting, and then optimizing processes enables IT automation to be built on sound processes, so consistent positive results can be achieved. Without documented SOPs: IT automation built on poorly defined, unoptimized processes leads to inconsistent results.
      Compliance: Compliance audits are more manageable because the documentation is already in place. Without documented SOPs: Documenting SOPs to prepare for an audit becomes a major time-intensive project.
      Transparency: Visually documented processes answer the common business question of “why does that take so long?” Without documented SOPs: Other areas of the organization may not understand how IT operates, which can lead to confusion and unrealistic expectations.
      Cost savings: Work can be assigned to the lowest level of support cost, IT operations achieve greater efficiency, and expensive breakdowns are avoided. Without documented SOPs: Work may be distributed uneconomically, money may be wasted through inefficient processes, and the organization is vulnerable to costly disruptions.

      COBIT, ISO, and ITIL aren’t a complete solution

      "Being ITIL and ISO compliant hasn’t solved our documentation problem. We’re still struggling."

      – Vendor Relationship Manager, Financial Services Industry

      • Adopting a framework such as ITIL, COBIT, or ISO doesn’t always mean that SOP documents are accurate, effective, or up to date.
      • Although these frameworks emphasize the importance of documenting processes, they tend to focus more on process development and requirements than on actual documentation. In other words, they deal more with what needs to be done than with how to do it.
      • This research will focus more on the documentation process itself – so how to go about creating, updating, optimizing, managing, and distributing SOP documents.

      Inadequate SOPs lead to major data loss and over $99,000 in recovery costs

      CASE STUDY 1

      Company A mid-sized US organization with over 1,000 employees

      Source Info-Tech Interview

      Situation

      • IT supports storage nodes replicated across two data centers. SOPs for backup procedures did not include an escalation procedure for failed backups or a step to communicate successful backups. Management was not aware of the issue and therefore could not address it before a failure occurred.

      Incident

      • Primary storage had a catastrophic failure, and that put pressure on the secondary storage, which then also failed. All active storage failed and the data corrupted. Daily backups were failing due to lack of disk space on the backup device. The organization had to resort to monthly tape backups.

      Impact

      • Lost 1 month of data (had to go back to the last tape backup).
      • Recovery also took much longer because recovery procedures were also not documented.
      • Key steps such as notifying impacted customers were overlooked. Customers were left unhappy not only with the outage and data loss but also the lack of communication.
      Hard dollar recovery costs
      Backup specialist (vendor) to assist with restoring data from tape $12,000
      Temps to re-enter 1 month of data $5,000
      Weekend OT for 4 people (approximately 24 hours per person) $5,538
      Productivity cost for affected employees for 1 day of downtime $76,923
      Total $99,462

      Intangible costs

      High “goodwill” impact for internal staff and customers.

      "The data loss pointed out a glaring hole in our processes – the lack of an escalation procedure. If I knew backups weren’t being completed, I would have done something about that immediately."

      – Senior Division Manager, Information Technology Division

      IT services company optimizes its SOPs using “Lean” approach

      CASE STUDY 2

      Company Atrion

      SourceInfo-Tech Interview

      Lean and SOPs

      • Standardized work is important to Lean’s philosophy of continuous improvement. SOPs allow for replication of the current best practices and become the baseline standard for member collaboration toward further improvements.
      • For more on Lean’s approach to SOPs, see “Lean Six Sigma Quality Transformation Toolkit (LSSQTT) Tool #17.”

      Atrion’s approach

      • Atrion is focused on documenting high-level processes that improve the client and employee experience or which can be used for training.
      • Cross-functional teams collaborate to document a process and find ways to optimize that SOP.
      • Atrion leverages visual documentation as much as possible: flowcharts, illustrations, video screen captures, etc.

      Outcomes

      • Large increase in usable, up-to-date documentation.
      • Process and efficiency improvements realized and made repeatable.
      • Success has been so significant that Atrion is planning to offer SOP optimization training and support as a service for its clients in the future.

      Atrion

      • Atrion provides IT services, solutions, and leadership to clients in the 250+ user range.
      • After adopting the Lean framework for its organization, it has deliberately focussed on optimizing its documentation.

      When we initiated a formal process efficiency program a little over a year ago and began striving towards a culture of continuous improvement, documenting our SOPs became key. We capture how we do things today and how to make that process more efficient. We call it current state and future state mapping of any process.

      – Michelle Pope, COO, Atrion Networking Corp.

      Strategies to overcome common documentation challenges

      Use Info-Tech’s methodology to streamline the SOP documentation process.

      Common documentation challenges Info-Tech’s methodology
      Where to start. For organizations with very few (if any) documented SOPs, the challenge is where to start. Apply a client focus to prioritize SOPs. Start with mission-critical operations, service management, and disaster recovery.
      Lack of time. Writing SOPs is viewed as an onerous task, and IT staff typically do not like to write documentation or lack the time. Use flowcharts, checklists, and diagrams over traditional dense manuals. Flowcharts, checklists, and diagrams take less time to create and maintain, and the output is far more usable than traditional manuals.
      Inconsistent document management. Documents are unorganized, e.g. hard to find documents, or you don’t know if you have the correct, latest version. Keep it simple. You don’t need a full-time SOP librarian if you stick to a simple, but consistent approach to documentation management. Simple is easier to follow (therefore, be consistent).
      Documentation is not maintained. More urgent tasks displace documentation efforts. There is little real motivation for staff to keep documents current. Ensure accountability at the individual and project level. Incorporate documentation requirements into performance evaluations, project planning, and change control procedures.

      Use this blueprint as a building block to complete these other Info-Tech projects

      Improve IT-Business Alignment Through an Internal SLA

      Understand business requirements, clarify capabilities, and close gaps.

      Standardize the Service Desk – Module 2 & 3

      Improve reporting and management of incidents and build service request workflows.

      Create a Right-Sized Disaster Recovery Plan

      Define appropriate objectives for DR, build a roadmap to close gaps, and document your incident response plan.

      Extend the Service Desk to the Enterprise

      Position IT as an innovator.

      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

      Create Visual SOP Documents – project overview

      1. Prioritize, optimize, and document critical SOPs 2. Establish a sustainable documentation process 3. Identify a content management solution
      Best-Practice Toolkit

      1.1 Identify and prioritize undocumented/outdated critical processes

      1.2 Reduce effort and improve usability with visual documentation

      1.3 Optimize and document critical processes

      2.1 Establish guidelines for identifying and organizing SOPs

      2.2 Write an SOP for creating and maintaining SOPs

      2.3 Plan SOP working sessions to put a dent into your documentation backlog

      3.1 Understand the options when it comes to content management solutions

      3.2 Use Info-Tech’s evaluation tool to determine the right approach for you

      Guided Implementations
      • Identify undocumented critical SOPs.
      • Understand the benefits of a visual approach.
      • Work through a tabletop exercise to document two visual SOP documents.
      • Establish documentation information guidelines.
      • Identify opportunities to create a culture that fosters SOP creation.
      • Address outstanding undocumented SOPs by working through process issues together.
      • Review your current approach to content management and discuss possible alternatives.
      • Evaluate options for a content management strategy, in the context of your own environment.
      Onsite Workshop Module 1:

      Identify undocumented critical processes and review the SOP mapping process.

      Module 2:

      Review and improve your documentation process and address your documentation backlog.

      Module 3:

      Evaluate strategies for publishing and managing SOP documentation.

      Phase 1 Outcome:
        Review and implement the process for creating usable SOPs.
      Phase 2 Outcome:
        Optimize your SOP maintenance processes.
      Phase 3 Outcome:
        Choose a content management solution that meets your needs.

      Workshop overview

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

      Workshop Prep Workshop Day 1 Workshop Day 2 Workshop Day 3 Workshop Day 4
      Activities Scope the SOP pilot and secure resources
      • Identify the scope of the pilot project.
      • Develop a list of processes to document.
      • Ensure required resources are available.
      Prioritize SOPs and review methodology

      1.1 Prioritize undocumented SOPs.

      1.2 Review the visual approach to SOP planning.

      1.3 Conduct a tabletop planning exercise.

      Review SOPs and identify process gaps

      2.1 Continue the tabletop planning exercise with other critical processes.

      2.2 Conduct a gap analysis to identify solutions to issues discovered during SOP mapping.

      Identify projects to meet process gaps

      3.1 Develop a prioritized project roadmap to address gaps.

      3.2 Define a process for documenting and maintaining SOPs.

      3.3 Identify and assign actions to improve SOP management and maintenance.

      Set next steps and put a dent in your backlog

      4.1 Run an SOP working session with experts and process owners to put a dent in the documentation backlog.

      4.2 Identify an appropriate content management solution.

      Deliverables
      1. Defined scope for the workshop.
      2. A longlist of key processes.
      1. Undocumented SOPs prioritized according to business criticality and current state.
      2. One or more documented SOPs.
      1. One or more documented SOPs.
      2. Gap analysis.
      1. SOP Project Roadmap.
      2. Publishing and Document Management Solution Evaluation Tool.
      1. Multiple documented SOPs.
      2. Action steps to improve SOP management and maintenance.

      Measured value for Guided Implementations (GIs)

      Engaging in GIs doesn’t just offer valuable project advice, it also results in significant cost savings.

      GI Measured Value
      Phase 1: Prioritize, optimize, and document critical SOPs
      • Time, value, and resources saved using Info-Tech’s methodology to prioritize and document SOPs in the ideal visual format.
      • For example, 4 FTEs*4 days*$80,000/year = $5,120
      Phase 2: Establish a sustainable documentation process
      • Time, value, and resources saved using our tools and methodology to implement a process to ensure SOPs are maintained, accessible, and up to date.
      • For example: 4 FTEs*5 days*$80,000/year = $6,400
      Phase 3: Identify a content management solution
      • Time, value, and resources saved using our best-practice guidance and tools to select an approach and solution to manage your organization’s SOPs.
      • For example: 2 FTEs*5 days*$80,000/year = $3,200
      Total Savings $14,720

      Note: Documenting SOPs provides additional benefits that are more difficult to quantify: reducing the time spent by staff to find or execute processes, improving transparency and accountability, presenting opportunities for automation, etc.

      Phase 1

      Prioritize, Optimize, and Document Critical SOPs

      Create Visual SOP Documents that Drive Process Optimization, Not Just Peace of Mind

      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: Prioritize, optimize, and document critical SOPs

      Proposed Time to Completion (in weeks): 2 weeks

      Step 1.1: Prioritize SOPs

      Start with an analyst kick off call:

      • Apply a client focus to critical IT services.
      • Identify undocumented, critical SOPs.

      Then complete these activities…

      • Rank and prioritize your SOP documentation needs.

      With this template:

      Standard Operating Procedures Workbook

      Step 1.2: Develop visual documentation

      Review findings with analyst:

      • Understand the benefits of a visual approach.
      • Review possibilities for visual documentation.

      Then complete these activities…

      • Identify formats that can improve your SOP documentation.

      With these templates:

      • Example DRP Process Flows
      • Example App Dev Process And more…

      Step 1.3: Optimize and document critical processes

      Finalize phase deliverable:

      • Two visual SOP documents, mapped using a tabletop exercise.

      Then complete these activities…

      • Create the visual SOP.
      • Review and optimize the process.

      With this tool:

      SOP Project Roadmap Tool

      Phase 1 Results & Insights:

      Identify opportunities to deploy visual documentation, and follow Info-Tech’s process to capture steps, gaps, and opportunities to improve IT processes.

      Focus first on client-facing and high-impact SOPs

      IT’s number one obligation to internal and external customers is to keep critical services running – that points to mission-critical operations, service management, and disaster recovery.

      Topic Description
      Mission-critical operations
      • Maintenance processes for mission-critical systems (e.g. upgrade procedures, batch processing, etc.).
      • Client-facing services with either formal or informal SLAs.
      • Change management – especially for mission-critical systems, change management is more about minimizing risk of downtime than expediting change.
      Service management
      • Service desk procedures (e.g. ticket assignment and issue response).
      • Escalation procedures for critical outages.
      • System monitoring.
      Disaster recovery procedures
      • Management-level incident response plans, notification procedures, and high-level failover procedures (e.g. which systems must come up first, second, third).
      • Recovery or failover procedures for individual systems.
      • Backup and restore procedures – to ensure backups are available if needed.

      Understand what makes an application or service mission critical

      When email or a shared drive goes down, it may impact productivity, but may not be a significant impact to the business. Ask these questions when assessing whether an application or service is mission critical.

      Criteria Description
      Is there a hard-dollar impact from downtime?
      • For example, when an online catalog system goes down, it impacts sales and therefore revenue. Without determining the actual financial impact, you can make an immediate assessment that this is a Gold system.
      • By contrast, loss of email may impact productivity but may not affect revenue streams, depending on your business. A classification of Silver is most likely appropriate.
      Impact on goodwill/customer trust?
      • If downtime means delays in service delivery or otherwise impacts goodwill, there is an intangible impact on revenue that may make the associated systems Gold status.
      Is regulatory compliance a factor?
      • If a system requires redundancy and/or high availability due to legal or regulatory compliance requirements, it may need to be classified as a Gold system.
      Is there a health or safety risk?
      • For example, police and medical organizations have systems that are mission critical due to their impact on health and safety rather than revenue or cost, and therefore are classified as Gold systems. Are there similar considerations in your organization?

      "Email and other Windows-based applications are important for our day-to-day operations, but they aren’t critical. We can still manufacture and ship clothing without them. However, our manufacturing systems, those are absolutely critical"

      – Bob James, Technical Architect, Carhartt, Inc.

      Create a high-level risk and benefit scale

      1.1a

      15 minutes

      Define criteria for high, medium, and low risks and benefits, as shown in the example below. These criteria will be used in the upcoming exercises to rank SOPs.

      Note: The goal in this section is to provide high-level indicators of which SOPs should be documented first, so a high-level set of criteria is used. To conduct a detailed business impact analysis, see Info-Tech’s Create a Right-Sized Disaster Recovery Plan.

      Materials

      • Whiteboard

      Participants

      • Process Owners
      • SMEs
      Risk to the business Score
      Low: Affects ad hoc activities or non-critical data. 1
      Moderate: Impacts productivity and internal goodwill. 2
      High: Impacts revenue, safety, and external goodwill. 3
      Benefit (e.g. productivity improvement) Score
      Low: Minimal impact. 1
      Moderate: Items with short-term or occasional applicability, so limited benefit. 2
      High: Save time for common or ongoing processes, and extensive improvement to training/knowledge transfer. 3

      Identify and prioritize undocumented mission-critical operations

      1.1b

      15 minutes

      1. To navigate to this exercise, open Info-Tech’s Standard Operating Procedures Workbook.
      2. List your top three–five mission critical applications or services.
      3. Identify relevant SOPs that support those applications or services.
      4. Indicate SOP status: Green = up to date and complete, Yellow = out-of-date or incomplete, Red = undocumented.
      5. Assign risk and benefit scores (3=high, 1=low) to Yellow and Red SOPs based on potential impact if those processes failed (risk) and opportunity for process improvement (benefit).

      OUTPUT

      • Analysis of SOPs supporting mission-critical operations

      Materials

      • Whiteboard

      Participants

      • Process Owners
      • SMEs
      Application SOPs Status Risk Benefit
      Enterprise Resource Planning (ERP)
      • System administration (user administration, adding projects, etc.).
      Red 1 2
      • System upgrades (including OS upgrades and patches).
      Red 2 2
      • Report generation.
      Green n/a n/a
      Network services
      • Network monitoring (including fault detection).
      Yellow 3 2
      • Network upgrades.
      Red 2 1
      • Backup procedures.
      Yellow 3 1

      Identify and prioritize undocumented service management procedures

      1.1c

      15 minutes

      1. To navigate to this exercise, open Info-Tech’s Standard Operating Procedures Workbook.
      2. Identify service management SOPs.
      3. Indicate SOP status: Green = up to date and complete, Yellow = out-of-date or incomplete, Red = undocumented.
      4. Assign risk and benefit scores (3=high, 1=low) to Yellow and Red SOPs based on potential impact if those processes failed (risk) and opportunity for process improvement (benefit).

      OUTPUT

      • Analysis of SOPs supporting service management

      Materials

      • Whiteboard

      Participants

      • Process Owners
      • SMEs
      Service Type SOPs Status Risk Benefit
      Service Request
      • Software install
      Red 3 1
      • Software update
      Yellow 3 1
      • New hardware
      Green n/a n/a
      Incident Management
      • Ticket entry and triage
      Yellow 3 2
      • Ticket escalation
      Red 2 1
      • Notification for critical issues
      Yellow 3 1

      Identify and prioritize undocumented DR procedures

      1.1d

      20 minutes

      1. To navigate to this exercise, open Info-Tech’s Standard Operating Procedures Workbook.
      2. Identify DR SOPs.
      3. Indicate SOP status: Green = up to date and complete, Yellow = out-of-date or incomplete, Red = undocumented.
      4. Assign risk and benefit scores (3=high, 1=low) to Yellow and Red SOPs based on potential impact if those processes failed (risk) and opportunity for process improvement (benefit).

      OUTPUT

      • Analysis of SOPs supporting DR

      Materials

      • Whiteboard

      Participants

      • Process Owners
      • SMEs
      DR Phase SOPs Status Risk Benefit
      Discovery and Declaration
      • Initial detection and escalation
      Red 3 1
      • Notification procedures to Emergency Response Team (ERT)
      Yellow 3 1
      • Notification procedures to staff
      Green n/a n/a
      Recover Gold Systems
      • ERP recovery procedures
      Red 2 2
      • Corporate website recovery procedures
      Yellow 3 2
      Recover Silver Systems
      • MS Exchange recovery procedures
      Red 2 1

      Select the SOPs to focus on for the first round of documentation

      1.1e

      20 minutes

      1. Identify two significantly different priority 1 SOPs to document during this workshop. It’s important to get a sense of how the Info-Tech templates and methodology can be applied to different types of SOPs.
      2. Rank the remaining SOPs that you still need to address post-workshop by priority level within each topic area.

      INPUT

      • SOP analysis from activities 1.1 and 1.2

      OUTPUT

      • A shortlist of critical, undocumented SOPs to review later in this phase

      Materials

      • Whiteboard

      Participants

      • Process Owners
      • SMEs
      Category Area SOPs Status Risk Benefit
      Disaster Recovery Procedures Discovery and Declaration
      • Initial detection and escalation
      Red 3 1
      • Notification procedures to ERT
      Yellow 3 1
      Mission-Critical Operations Network Services
      • Network monitoring (including fault detection)
      Yellow 3 2
      Service Management Procedures Incident Management
      • Ticket entry and triage
      Yellow 3 2

      Change the format of your documentation

      Which document is more effective? Which is more likely to be used?

      "The end result for most SOPs is a 100-page document that makes anyone but the author want to stab themselves rather than read it. Even worse is when you finally decide to waste an hour of your life reading it only to be told afterwards that it might not be quite right because Bob or Stan needed to make some changes last year but never got around to it."

      – Peter Church, Solutions Architect

      Create visual-based documentation to improve usability and effectiveness

      "Without question, 300-page DRPs are not effective. I mean, auditors love them because of the detail, but give me a 10-page DRP with contact lists, process flows, diagrams, and recovery checklists that are easy to follow."

      – Bernard Jones, MBCI, CBCP, CORP, Manager Disaster Recovery/BCP, ActiveHealth Management

      SOPs, including those that support your disaster recovery plan (DRP), are often created to meet certification requirements. However, this often leads to lengthy overly detailed documentation that is geared to auditors and business leaders, not IT staff trying to execute a procedure in a high-pressure, time-sensitive scenario.

      Staff don’t have time to flip through a 300-page manual, let alone read lengthy instructions, so organizations are transforming monster manuals into shorter, visual-based documentation. Benefits include:

      • Quicker to create than lengthy manuals.
      • Easier to be absorb, so they are more usable.
      • More likely to stay up to date because they are easier to maintain.

      Example: DRPs that include visual SOPs are easier to use — that leads to shorter recovery times and fewer mistakes.

      Chart is depicted showing the success rates of traditional manuals versus visual documentation.

      Use flowcharts for process flows or a high-level view of more detailed procedures

      • Flowcharts depict who does what and when; they provide an at-a-glance view that is easy to follow and makes task ownership clear.
      • Use swim lanes, as in this example, to indicate process stages and task ownership.
      • For experienced staff, a high-level reminder of process flows or key steps is sufficient.
      • Where more detail is required, include links to supporting documentation (which could include checklists, vendor documentation, other flowcharts, etc.).

      See Info-Tech’s Incident and Service Management Procedures – Service Desk Example.

      "Flowcharts are more effective when you have to explain status and next steps to upper management."

      – Assistant Director-IT Operations, Healthcare Industry

      Example: SOP in flowchart format

      A flowchart is depicted as an example flowchart. This one is an SOP flowchart labelled 'Triage Process - Incidents'

      Review your options for diagramming software

      Many organizations look for an option that easily integrates with the MS Office suite. The default option is often Microsoft Visio.

      Pros:

      • Easy to learn and use.
      • Has a wide range of features and capabilities.
      • Comes equipped with a large collection of stencils and templates.
      • Offers the convenience of fluid integration with the MS Office Suite.

      Cons:

      • Isn’t included in any version of the MS Office Suite and can be quite expensive to license.
      • Not available for Mac or Linux environments.

      Consider the options below if you’re looking for an alternative to Microsoft Visio:

      Desktop Solutions

      • Dia Diagram Editor
      • Diagram Designer
      • LibreOffice Draw
      • Pencil Project
      • yEd Graph Editor

      • Draw.io
      • Creately
      • Gliffy
      • LucidChart

      Note: No preference or recommendation is implied from the ordering of the options above.

      This list is not intended to be comprehensive.

      Evaluate different solutions to identify one that works for you

      Use the criteria below to identify a flowchart software that fits your needs.

      Criteria Description
      Platform What platform(s) can run the software?
      Description What use cases are identified by the vendor – and do these cover your needs for documenting your SOPs? Is the software open source?
      Features What are the noteworthy features and characteristics?
      Usability How easy is the program to use? What’s the learning curve like? How intuitive is the design?
      Templates and Stencils Availability of templates and stencils.
      Portability Can the solution integrate with other pieces of software? Consider whether other tools can view, open, and/or edit documents; what file formats can be published, etc.
      Cost Cost of the software to purchase or license.

      Use checklists to streamline step-by-step procedures

      • Checklists are ideal when staff just need a reminder of what to do, not how to do it.
      • Remember your audience. You aren’t pulling in a novice to run a complex procedure, so all you really need here are a series of reminders.
      • Where more detail is required, include links to supporting documentation.
      • Note that a flowchart can often be used instead of a checklist, depending on preference.

      For two different examples of a checklist template, see:

      Image depicting an example checklist. This checklist depicts an employee termination checklist

      Use topology diagrams to capture network layout, integrations, and system information

      • Organizations commonly have network topology diagrams for reference purposes, so this is just a re-use of existing resources.
      • Physically label real world equipment to correspond to topology diagrams. While these labels will be redundant for most IT employees, they help give clarity and confidence when changes are being made.
      • If your topology diagrams are housed in a tool such as a systems management product, then export the diagrams so they can be included in your SOP documentation suite.

      "Our network engineers came to me and said our standard SOP template didn't work for them. They're now using a lot of diagrams and flowcharts, and that has worked out better for them."

      The image shows a topology organization diagram as an example network layout

      Use screen captures and tutorials to facilitate training for applications and SOPs

      • Screen capture tutorials or videos are effective for training staff on applications. For example, create a screen capture tutorial to train staff on the use of a help desk application and your company’s specific process for using that tool.
      • Similarly, create tutorials to train end users on straightforward “technical” tasks (e.g. setting up their VPN connection) to reduce the demand on IT staff.
      • Tutorials can be created quickly and easily with affordable software such as Snag-It, ScreenHunter Pro, HyperSnap, PicPick, FastStone, Ashampoo Snap 6, and many others.

      "When contractors come onboard, they usually don't have a lot of time to learn about the organization, and we have a lot of unique requirements. Creating SOP documents with screenshots has made the process quicker and more accurate."

      – Susan Bellamore, Business Analyst, Public Guardian and Trustee of British Columbia

      The image is an example of a screen caption tutorial, depicting desktop icons and a password login

      Example: Disaster recovery notification and declaration procedure

      1. Swim lanes indicate task ownership and process stages.
      2. Links to supporting documentation (which could include checklists, vendor documentation, other flowcharts, etc.) are included where necessary.
      3. Additional DR SOPs are captured within the same spreadsheet for convenient, centralized access.

      Review Info-Tech’s Incident Response and Recovery Process Flows – DRP Example.

      Example: DRP flowchart with links to supporting documents

      The image is an example of an DRP flowchart labelled 'Initial Discovery/Notification and Declaration Procedures'

      Establish flowcharting standards

      If you don’t have existing flowchart standards, then keep it simple and stick to basic flowcharting conventions as described below.

      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 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.

      Conduct a tabletop planning exercise to build an SOP

      1.3a

      20 minutes

      Tabletop planning is a paper-based exercise where your team walks through a particular process and maps out what happens at each stage.

      1. For this exercise, choose one particular process to document.
      2. Document each step of the process using 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.

      OUTPUT

      • Steps in the current process for one SOP

      Materials

      • Tabletop, pen, and cue cards

      Participants

      • Process Owners
      • SMEs

      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.

      The image depicts three cue cards labelled steps 3 to 5. The cue cards are examples of the tabletop planning exercise.

      Collaborate to optimize the SOP

      1.3b

      20 minutes

      Review the tabletop exercise. What gaps exist in current processes?

      How can the process be made better? What are the outputs and checkpoints?

      The image depicts five cue cards, two of which are examples on how to improve the process. This is an example of the tabletop exercise.

      OUTPUT

      • Identify steps to optimize the SOP

      Materials

      • Tabletop, pen, and cue cards

      Participants

      • Process Owners
      • SMEs

      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, also use green cards for decision diamonds, purple for document/report outputs, and blue for sub-processes.

      Capture opportunities to improve processes in the Standard Operating Procedures Project Roadmap Tool

      1.3

      Rank and track projects to close gaps you discover in your processes.

      1. As a group, identify potential solutions to close the gaps in your processes that you’ve uncovered through the tabletop mapping exercise.
      2. Add these project names to the Standard Operating Procedures Project Roadmap Tool on the “Project Scoring” tab.
      3. Review and adjust the criteria for evaluating the benefits and costs of different projects on the “Scoring Criteria” tab.
      4. Return to the “Project Scoring” tab, and assign weights at the top of each scoring column. Use the drop-down menus to adjust the scores for each project category. The tool will automatically rank the projects based on your input, but you can adjust the ranks as needed.
      5. Assign dates and descriptions to the projects on the “Implementation Schedule” tab, below.
      The image depicts a graph showing an example of ranked and tracked projects.

      Identify gaps to improve process performance and make SOP documentation a priority

      CASE STUDY

      Industry Government (700+ FTEs)
      Source Info-Tech Workshop

      Challenge

      • Tabletop planning revealed a 77-hour gap between current and desired RTO for critical systems.
      • Similarly, the current achievable RPO gap was up to one week, but the desired RPO was one hour.
      • A DR site was available but not yet set up with the necessary equipment.
      • Lack of documented standard operating procedures (SOPs) was identified as a risk since that increased the dependence on two or three key SMEs.

      Solution

      • Potential projects to close RTO/RPO gaps were identified, including:
        • Deploy servers that were decommissioned (as a result of a server refresh) to the DR site as warm standby servers.
        • Implement site-to-site data replication.
        • Document SOPs to enable tasks to be delegated and minimize resourcing risks.

      Results

      • A DR project implementation schedule was defined.
      • Many of the projects required no further investment, but rather deployment of existing equipment that could function as standby equipment at the DR site.
      • The DR risk from a lack of SOPs enabled SOPs to be made a priority. An expected side benefit is the ability to review and optimize processes and improve consistency in IT operations.

      Document the SOPs from the tabletop exercise

      1.3c

      20 minutes

      Document the results from the tabletop exercise in the appropriate format.

      1. Identify an appropriate visual format for the high-level SOP as well as for any sub-processes or supporting documentation.
      2. Break into groups of two or three.
      3. Each group will be responsible for creating part of the SOP. Include both the high-level SOP itself and any supporting documentation such as checklists, sign-off forms, sub-processes, etc.
      4. Once your document is complete, exchange it with that of another group. Review each other’s documents to check for clarity and completeness.

      OUTPUT

      • Output from activities 1.4 and 1.5

      Materials

      • Flowcharting software, laptops

      Participants

      • Process Owners
      • SMEs

      This image has four cue cards, and an arrow pointing to a flowchart, depicting the transfer of the information on the cue cards into a flowchart software

      Repeat the tabletop exercise for the second process

      Come back together as a large group. Choose a process that is significantly different from the one you’ve just documented, and repeat the tabletop exercise.

      As a reminder, the steps are:

      1. Use the tabletop exercise to map out a current SOP.
      2. Collaborate to optimize the SOP.
      3. Decide on appropriate formats for the SOP and its supporting documents.
      4. Divide into small groups to create the SOP and its supporting documents.
      5. Repeat the steps above as needed for your initial review of critical processes.

      Info-Tech Insight

      If you plan to document more than two or three SOPs at once, consider making it an SOP “party” to add momentum and levity to an otherwise dry process. Review section 2.3 to find out how.

      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.1a-e

      Get started by prioritizing SOPs

      Ensure the SOP project remains business focused, and kick off the project by analyzing critical business services. Identify key IT services that support the relevant business services. Conduct a benefit/risk analysis to prioritize which SOPs should become the focus of the workshop.

      1.3a-c

      Document the SOPs from the tabletop exercise

      Leverage a tabletop planning exercise to walk the team through the SOP. During the exercise, focus on identifying timelines, current gaps, and potential risks. Document the steps via que cards first and transpose the hard copies to an electronic version.

      Phase 2

      Establish a Sustainable Documentation Process

      Create Visual SOP Documents that Drive Process Optimization, Not Just Peace of Mind

      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: Establish a sustainable SOP documentation process

      Proposed Time to Completion (in weeks): 4 weeks

      Step 2.1: Establish guidelines for identifying and organizing SOPs

      Start with an analyst call:

      • Establish documentation information guidelines.
      • Review version control best practices.

      Then complete these activities…

      • Implement best practices to identify and organize your SOPs.

      With these tools & templates:

      • SOP Workbook

      Step 2.2: Define a process to document and maintain SOPs

      Review findings with analyst:

      • Identify opportunities to create a culture that fosters SOP creation.

      Then complete these activities…

      • Create a plan to address SOP documentation gaps.

      With these tools & templates:

      • Document Management Checklist

      Step 2.3: Plan time with experts to put a dent in your documentation backlog

      Finalize phase deliverable:

      • Address outstanding undocumented SOPs by working through process issues together.

      Then complete these activities…

      • Organize and run a working session to document and optimize processes.

      With these tools & templates:

      • SOP Workbook
      • SOP Project Roadmap Tool

      Phase 2 Results & Insights:

      Improve the process for documenting and maintaining your SOPs, while putting a dent in your documentation backlog and gaining buy-in with staff.

      Identify current content management practices and opportunities for improvement

      DISCUSS

      What is the current state of your content management practices?

      Are you using a content management system? If not, where are documents kept?

      Are your organizational or departmental SOPs easy to find?

      Is version control a problem? What about file naming standards?

      Get everyone on the same page on the current state of your SOP document management system, using the questions above as the starting point.

      Keep document management simple for better adoption and consistency

      If there is too much complexity and staff can’t easily find what they need, you won’t get buy-in and you won’t get consistency.

      Whether you store SOPs in a sophisticated content management system (CMS) or on a shared network drive, keep it simple and focus on these primary goals:

      • Enable staff to find the right document.
      • Know if a document is the latest, approved version.
      • Minimize document management effort to encourage buy-in and consistency.

      If users can’t easily find what they need, it leads to bad practices. For example:

      • Users maintain their own local copies of commonly used documents to avoid searching for them. The risk is that local copies will not be automatically updated when the SOP changes.
      • Separate teams will implement their own document management system and repository. Now you have duplication of effort and company resources, multiple copies of documents (where each group needs their own version), and no centralized control over potentially sensitive documents.
      • Users will ignore documented SOPs or ask a colleague who might also be following the above bad practices.

      Insert a document information block on the first page of every document to identify key attributes

      Include a document information block on the first page of every document to identify key attributes. This strategy is as much about minimizing resistance as it is ensuring key attributes are captured.

      • A consistent document information block saves time (e.g. vs. customized approaches per document). If some fields don’t apply, enter “n/a.”
      • It provides key information about the document without having to check soft copy metadata, especially if you work with hard copies.
      • It’s a built-in reminder of what to capture and easier than updating document properties or header/footer information or entering metadata into a CMS.

      Note: The Info-Tech templates in this blueprint include a copy of the document information block shown in this example. Add more fields if necessary for your organization’s needs.

      For an example of a completed document information block, see Network Backup for Atlanta Data Center – Backups Example

      Info-Tech Insight

      For organizations with more advanced document management requirements, consider more sophisticated strategies (e.g. using metadata) as described in Info-Tech’s Use SharePoint for Enterprise Content Management and Reintroduce the Information Lifecycle to the Content Management Strategy. However, the basic concepts above still apply: establish standard attributes you need to capture and do so in a consistent manner.

      Modify the Info-Tech document information block to meet your requirements

      2.1a

      15 minutes

      1. Review “Guidelines and Template for the Document Information Block” in the Standard Operating Procedures Workbook. Determine if any changes are required, such as additional fields.
      2. Identify which fields you want to standardize and then establish standard terms. Balance the needs for simplicity and consistency – don’t force consistency where it isn’t a good fit.
      3. Pre-fill the document information block with standard terms and examples and add it to an SOP template that’s stored in your content management system.

      Educate staff by pre-filling the document

      • Providing examples built into the templates provides in-context, just-in-time training which is far more effective and easier than formal education efforts.
      • Focus your training on communicating when the template or standard terms change so that staff know to obtain the new version. Otherwise, the tendency for many staff will be to use one of their existing documents as their template.

      OUTPUT

      • Completed document information block

      Materials

      • Laptop
      • Projector

      Participants

      • Process Owners
      • SMEs

      Leverage the document information block to create consistent filenames that facilitate searching

      Use the following filename format to create consistent, searchable, and descriptive filenames:

      Topic – Document Title – Document Type – Version Date

      Filename Component Purpose
      Topic
      • Functions as a filename prefix to group related documents but is also a probable search term. For project work, use a project name/number.
      Document Title
      • The title should be fairly descriptive of the content (if it isn’t, it’s not a good title) so it will help make the file easily identifiable and will include more probable search terms.
      Document Type Further distinguishes similar files (e.g. Maintenance SOP vs. a Maintenance Checklist).
      Version Date (for local files or if not using a CMS)
      • If it’s necessary to work on a file locally, include the version date at the end of the filename. The date is a more recognizable indicator of whether it’s the latest version or an old copy.
      • Establish a standard date format. Although MM-DD-YY is common in the US, the format YYYY-MM-DD reduces confusion between the month and day.

      For example:

      • ERP – System Administration Monthly Maintenance Tasks – Checklist – 2016-01-15.docx
      • ERP – System Administration Monthly Maintenance Tasks – SOP – 2017-01-10.docx
      • Backups – Network Backup Procedure for Atlanta Data Center – SOP – 2017-03-06.docx
      • PROJ437 – CRM Business Requirements – BRD – 2017-02-01.xlsx
      • DRP – Notification Procedures – SOP – 2016-09-14.docx
      • DRP – Emergency Response Team Roles and Responsibilities – Reference – 2018-03-10.xlsx

      Apply filename and document information block guidelines to existing SOPs

      2.1b

      15 minutes

      1. Review the SOPs created during the earlier exercises.
      2. Update the filenames and document information block based on guidelines in this section.
      3. Apply these guidelines to other select existing SOPs to see if additional modifications are required (e.g. additional standard terms).

      INPUT

      • Document Information Block

      OUTPUT

      • Updated filenames and document information blocks

      Materials

      • Laptop and projector

      Participants

      • Process Owners
      • SMEs

      Implement version control policies for local files as well as those in your content management system (CMS)

      1. Version Control in Your CMS

      2. Always keep one master version of a document:

      • When uploading a new copy of an existing SOP (or any other document), ensure the filenames are identical so that you are just adding a new version rather than a separate new file.
      • Do not include version information in the filename (which would create a new separate file in your CMS). Allow your CMS to handle version numbering.
    • Version Control for Local Files

    • Ideally, staff would never keep local copies of files. However, there are times when it is practical or preferable to work from a local copy: for example, when creating or updating an SOP, or when working remotely if the CMS is not easily accessible.

      Implement the following policies to govern these circumstances:

      • Add the version date to the end of the filename while the document is local, as shown in the slide on filenames.
      • Remove the date when uploading it to a CMS that tracks date and version. If you leave the date in the filename, you will end up with multiple copies in your CMS.
      • When distributing copies for review, upload a copy to the CMS and send the link. Do not attach a physical file.
    • Minimize the Need for Version Updates

    • Reduce the need for version updates by isolating volatile information in a separate, linked document. For example:

      • Use Policy documents to establish high-level expectations and goals, and use SOPs to capture workflow, but put volatile details in a separate reference document. For example, for Backup procedures, put offsite storage vendor details such as contact information, pick up times, and approved couriers in a separate document.
      • Similarly, for DRP Notification procedures, reference a separate contacts list.

      Modify the Info-Tech Document Management Checklist to meet your requirements

      2.1c

      15 minutes

      1. Review the Info-Tech Document Management Checklist.
      2. Add or remove checklist items.
      3. Update the document information block.

      OUTPUT

      • Completed document management checklist

      Materials

      • Laptop, projector

      Participants

      • Process Owners
      • SMEs

      See Info-Tech’s Document Management Checklist.

      If you aren’t going to keep your SOPs current, then you’re potentially doing more harm than good

      An outdated SOP can be just as dangerous as having no SOP at all. When a process is documented, it’s trusted to be accurate.

      • Disaster recovery depends as much on supporting SOPs – such as backup and restore procedures – as it does on a master incident response plan.
      • For disaster scenarios, the ability to meet recovery point objectives (i.e. minimize data loss) and recovery time objectives (i.e. minimize downtime) depends on smoothly executed recovery procedures and on having well-defined and up-to-date DR documentation and supporting SOPs. For example:
        • Recovery point (data loss) objectives are directly impacted by your backup procedures.
        • Recovery time is minimized by a well-defined restore procedure that reduces the risk of human error during recovery which could lead to data loss or a delay in the recovery.
        • Similarly, a clearly documented configuration procedure will reduce the time to bring a standby system online.
      A graph depicting the much faster recovery time of up-to-date SOPs versus out-of-date SOPs.

      Follow Info-Tech best practices to keep SOPs current and drive consistent, efficient IT operations

      The following best practices were measured in this chart, and will be discussed further in this section:

      1. Identify documentation requirements as part of project planning.
      2. Require a manager or supervisor to review and approve SOPs.
      3. Check documentation status as part of change management.
      4. Hold staff accountable.
      Higher adoption of Info-Tech best practices leads to more effective SOPs and greater benefits in areas such as training and process improvement.

      Graph depicting the efficiency of adopting Info-Tech practices regarding SOPs. Four categories of 'Training', 'process improvement', 'IT automation', and 'consistent IT operations' are shown increasing in efficiency with a high adoption of Info-Tech strategies.

      Info-Tech Insight

      Audits for compliance requirements have little impact on getting SOPs done in a timely manner or the actual usefulness of those SOPs, because the focus is on passing the audit instead of creating SOPs that improve operations. The frantic annual push to complete SOPs in time for an audit is also typically a much greater effort than maintaining documents as part of ongoing change management.

      Identify documentation requirements as part of project planning

      DISCUSS

      When are documentation requirements captured, including required changes to SOPs?

      Make documentation requirements a clearly defined deliverable. As with any other task, this should include:

      • Owner: The person ultimately responsible for the documentation.
      • Assigned resource: The person who will actually put pen to paper. This could be the same person as the owner, or the owner could be a reviewer.
      • Deadlines: Include documentation deliverables in project milestones.
      • Verification process: Validate completion and accuracy. This could be a peer review or management review.
      Example: Implement a new service desk application.
      • Service desk SOP documentation requirements: SOP for monitoring and managing tickets will require changes to leverage new automation features.
      • Owner: Service Desk Lead.
      • Assigned resource: John Smith (service desk technician).
      • Deadline: Align with “ready for QA testing.”
      • Verification process: Service Desk Lead document review and signoff.

      Info-Tech Insight

      Realistically, documentation will typically be a far less urgent task than the actual application or system changes. However, if you want the necessary documentation to be ultimately completed, even if it’s done after more urgent tasks, it must be tracked.

      Implement document approval steps at the individual and project level

      DISCUSS

      How do you currently review and validate SOP documents?

      Require a manager or supervisor to review and approve SOPs.

      • Avoid a bureaucratic review process involving multiple parties. The goal is to ensure accuracy and not just provide administrative protection.
      • A review by the immediate supervisor or manager is often sufficient. Their feedback and the implied accountability improve the quality and usefulness of the SOPs.

      Check documentation status as part of change management.

      • Including a documentation status check holds the project leaders and management accountable.
      • If SOPs are not critical to the project deliverable, then realistically the deliverable is not held back. However, keep the project open until relevant documents are updated so those tasks can’t be swept under the rug until the next audit.

      SOP reviews, change management, and identifying requirements led to benefits such as training and process improvement.

      A chart depicting the impact and benefits of SOP reviews, change management and identifying requirements. The chart is accompanied by a key for the grey to blue colours depicted

      "Our directors and our CIO have tied SOP work to performance evaluations and SOP status is reviewed during management meetings. People have now found time to get this work done."

      – Assistant Director-IT Operations, Healthcare Industry

      Review SOPs regularly and assign a process owner to avoid reinforcing silos

      CASE STUDY

      Industry

      Public service organization

      Source

      Info-Tech client engagement

      Situation

      • The organization’s IT department consists of five heavily siloed units.
      • Without communication or workflow accountability across units, each had developed incompatible workflows, making estimates of “time to resolution” for service requests difficult.
      • The IT service manager purchases a new service desk tool, attempting to standardize requests across IT to improve efficiency, accountability, and transparency.

      Complication

      • The IT service manager implements the tool and creates standardized workflows without consulting stakeholders in the different service units.
      • The separate units immediately rebel against the service manager and try to undermine the implementation of the new tool.

      Results

      • Info-Tech analysts helped to facilitate a solution between experts in the different units.
      • In order to develop a common workflow and ticket categorization scheme, Info-Tech recommended that each service process should have a single approver.

      The bottom line: ensure that there’s one approver per process to drive process efficiency and accountability and avoid problems down the road.

      Hold staff accountable to encourage SOP work to be completed in a timely manner

      DISCUSS

      Are SOP updates treated as optional or “when I have time” work?

      Hold staff directly accountable for SOP work.

      Holding staff accountable is really about emphasizing the importance of ensuring SOPs stay current. If management doesn’t treat SOPs as a priority, then neither will your staff. Strategies include:

      • Include SOP work in performance appraisals.
      • Keep relevant tickets open until documentation is completed.
      • Ensure documents are reviewed, as discussed earlier.
      • Identify and assign documentation tasks as part of project planning efforts, as discussed earlier.

      Holding staff accountable minimizes procrastination and therefore maintenance effort.

      Chart depicting the impact on reducing SOP maintenance effort followed by a key defining the colours on the chart

      Info-Tech Insight

      Holding staff accountable does not by itself make a significant impact on SOP quality (and therefore the typical benefits of SOPs), but it minimizes procrastination, so the work is ultimately done in a more timely manner. This ensures SOPs are current and usable, so they can drive benefits such as consistent operations, improved training, and so on.

      Assign action items to address SOP documentation process challenges

      2.2

      1. Discuss the challenges mentioned at the start of this section, and other challenges highlighted by the strategies discussed in this section. For example:
      • Are documentation requirements included in project planning?
      • Are SOPs and other documentation deliverables reviewed?
      • Are staff held accountable for documentation?
    • Document the challenges in your copy of the Standard Operating Procedures Workbook and assign action items to address those challenges.
    • Challenge Action Items Action Item Owner
      Documentation requirements are identified at the end of a project.
      • Modify project planning templates and checklists to include “identify documentation requirements.”
      Bob Ryan
      SOPs are not reviewed.
      • When assigning documentation tasks, also assign an owner who will be responsible for reviewing and approving the deliverable.
      • Create a mechanism for officially signing off on the document (e.g. email approval or create a signoff form).
      Susan Jones

      An “SOP party” fosters a collaborative approach and can add some levity to an otherwise dry exercise

      What is an SOP party?

      • An SOP party is a working session, bringing together process owners and key staff to define current SOPs and collaborate to identify optimization opportunities.
      • The party aspect is really just about how you market the event. Order in food or build in a cooking contest (e.g. a chilli cook-off or dessert bake-off) to add some fun to what can be a dry activity.

      Why does this work?

      • Process owners become so familiar with their tasks that many of the steps essentially live in their heads. Questions from colleagues draw out those unwritten steps and get them down on paper so another sufficiently qualified employee could carry out the same steps.
      • Once the processes are defined (e.g. via a tabletop exercise), input from colleagues can help identify risks and optimization opportunities, and process questions can be quickly answered because the key people are all present.
      • The group approach also promotes consistency and enables you to set expectations (e.g. visual-based approach, standards, level of detail, etc.).

      When is collaboration necessary (e.g. via tabletop planning)?

      • Tabletop planning is ideal for complex processes as well as processes that span multiple tasks, people, and/or systems.
      • For processes with a narrow focus (e.g. recovery steps for a specific server), assign these to the SME to document. Then ensure the SOP is reviewed to draw out the unwritten steps as described above.
      • For example, if you use tabletop planning to document a high-level DR plan, sub-processes might include recovery procedures for individual systems; those SOPs can then be assigned to individual SMEs.

      Schedule SOP working sessions until critical processes are documented

      Ultimately, it’s more efficient to create and update SOPs as needed but dedicated working sessions will help address immediate critical needs.

      Organize the working session:
      1. Book a full-day meeting in an out of the way meeting room, invite key staff (system and process owners who ultimately need to be SOP owners), and order in lunch so no one has to leave.
      2. Prioritize SOPs (see Phase 1) and set goals (e.g. complete the top 6 SOPs during this session).
      3. Alternate between collaborative efforts and documenting the SOPs. For example:
        1. Tabletop or flowchart the current SOP. Take a picture of the current state for reference purposes.
        2. Look for process improvements. If you have the authority in the room to enable process changes, then modify the tabletop/flowchart accordingly and capture this desired future state (e.g. take a picture). Otherwise, identify action items to follow up on proposed changes.
        3. Identify all related documentation deliverables (e.g. sub-processes, checklists, approval forms, etc.).
        4. Create the identified documentation deliverables (divide the work among the team). Then repeat the above.
      4. Repeat these working sessions on a monthly or quarterly basis, depending on your requirements, until critical SOPs are completed.
      5. When the SOP backlog is cleared, conduct quarterly or semi-annual refreshers for ongoing review and optimization of key processes.

      Assign action items to capture next steps after SOP working sessions

      2.3

      1. Review the SOPs documented during this workshop. Identify action items to complete and validate those SOPs and related documents. For example, do the SOPs require further approval or testing?
      2. Similarly, review the document management checklist and identify action items to complete, expand, and/or validate proposed standards.
      3. For SOP working sessions, decide on a date, time, and who should be there based on the guidelines in this section. If the SOP party approach does not meet your requirements, then at the very least assign owners for the identified critical SOPs and set deadlines for completing those SOPs. Document these extra action items in your copy of the Standard Operating Procedures Workbook.
      SOP or Task Action Items Action Item Owner
      Ticket escalation SOP
      • Debrief the rest of the Service Desk team on the new process.
      • Modify the SOP further based on feedback, if warranted.
      • Implement the new SOP. This includes communicating visible changes to business users and other IT staff.
      Jeff Sutter
      SOP party
      • Contact prospective attendees to communicate the purpose of the SOP party.
      • Schedule the SOP party.
      Bob Smith

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

      Book a workshop with out 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

      Identify current content management practices

      As a group, identify current pain points and opportunities for improvement in your current content management practices.

      2.2

      Assign action items to address documentation process challenges

      Develop a list of action items to address gaps in the SOP documentation and maintenance process.

      Phase 3

      Identify a Content Management Solution

      Create Visual SOP Documents that Drive Process Optimization, Not Just Peace of Mind

      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: Decide on a content management solution for your SOPs

      Proposed Time to Completion (in weeks): 1 week

      Step 3.1: Understand the options for CM solutions

      Start with an analyst kick off call:

      • Review your current approach to content management and discuss possible alternatives.

      Then complete these activities…

      • Evaluate the pros and cons of different approaches to content management.
      • Discuss approaches for fit with your team.

      Step 3.2: Identify the right solution for you

      Review findings with analyst:

      • Identify 2–3 possible options for a content management strategy.

      Then complete these activities…

      • Identify the best solution based on portability, maintainability, cost, and implementation effort.

      With these tools & templates:

      • Publishing and Document Management Solution Evaluation Tool
      • SOP Project Roadmap
      • SOP Workbook

      Phase 3 Results & Insights:

      Choose an approach to content management that will best support your organization’s SOP documentation and maintenance process.

      Decide on an appropriate publishing and document management strategy for your organization

      Publishing and document management considerations:

      • Portability/External Access: At the best of times, portability is nice because it enables flexibility, but at the worst of times (such as in a disaster recovery situation) it is absolutely essential. If your primary site is down, can you still access your documentation? As shown in this chart, traditional storage strategies still dominate DRP documentation, but these aren’t necessarily the best options.
      • Maintainability/Usability: How easy is it to create, update, and use the documentation? Is it easy to link to other documents? Is there version control? The easier the system is to use, the easier it is to get employees to use it.
      • Cost/Effort: Is the cost and effort appropriate? For example, a large enterprise may need a formal solution like SharePoint or a Content Management System. For smaller organizations, the cost of these tools might be harder to justify.

      Consider these approaches:

      This section reviews the following approaches, their pros and cons, and how they meet publishing and document management requirements:

      • SOP tools.
      • Cloud-based content management software.
      • In-house solutions combining SharePoint and MS Office (or equivalent).
      • Wiki site.
      • “Manual” approaches such as storing documents on a USB drive.
      Chart depicting the portable strategy popularity, followed by a key defining the colours on the graph

      Source: Info-Tech Research Group; N=118

      Note: Percentages total more than 100% due to respondents using more than one portability strategy.

      Develop a content management strategy and process to reduce organizational risk

      CASE STUDY

      Segment

      Mid-market company

      Source

      Info-Tech Interview

      Situation

      • A mid-sized company hired a technical consultancy to manage its network.
      • As part of this move, the company’s network administrator was fired.
      • Over time, this administrator had become a “go-to” person for several other IT functions.

      Complication

      • The consulting team realizes that the network administrator kept critical documentation on his local hard drive.
      • This includes configs, IP addresses, passwords, logins to vendor accounts, and more.
      • It becomes clear the administrator was able to delete some of this information before leaving, which the consultants are required to retrieve and re-document.

      Result

      • Failing to implement effective SOPs for document management and terminating key IT staff exposed the organization to unnecessary risk and additional costs.
      • Allowing a local content management system to develop created a serious security risk.
      • The bottom line: create a secure, centralized, and backed-up location and establish SOPs around using it to help keep the company’s data safe.

      Info-Tech offers a web-based policy management solution with process management capabilities

      Role How myPolicies helps you
      Policy Sponsors
      • CEO
      • Board of Directors

      Reduced Corporate Risk

      Avoid being issued a regulatory fine or sanction that could jeopardize operations or hurt brand image.

      Policy Reviewers
      • Internal Audit
      • Compliance
      • Risk
      • Legal

      A Culture of Compliance

      Adherence with regulatory requirements as well as documented audit trail of all critical policy activities.

      Policy Owners
      • HR
      • IT
      • Finance
      • Operations

      Less Administrative Burden

      Automation and simplification of policy creation, distribution, and tracking.

      Policy Users
      • Employees
      • Vendors
      • Contractors

      Policy Clarity

      Well-written policies are stored in one reliable, easy to navigate location.

      About this Approach:

      myPolicies is a web-based solution to create, distribute, and manage corporate policies, procedures, and forms, built around best practices identified by our research.

      Contact your Account Manager today to find out if myPolicies is right for you.

      SOP software and DR planning tools can help, but they aren’t a silver bullet

      Portability/External Access:
      • Pros: Typically have a SaaS option, providing built-in external access with appropriate security and user administration to vary access rights.
      • Cons: Dependent on the vendor to ensure external access, but this is typically not an issue.
      Maintainability/Usability:
      • Pros: Built-in templates encourage consistency as well as guide initial content development by indicating what details need to be captured.
      • Pros: Built-in document management (e.g. version control, metadata support, etc.), centralized access/navigation to required documents, and some automation (e.g. update contacts throughout the system).
      • Cons: Not a silver bullet. You still have to do the work to define and capture your processes.
      • Cons: Requires end-user and administrator training.
      • Cons: Often modules of larger software suites. If you use the entire suite, it may make sense to use the SOP tool, but otherwise probably not.
      Cost/Effort:
      • Pros: For large enterprises, the convenience of built-in document management and templates can outweigh the cost.
      • Cons: SOP tools can be costly. Expect to pay at least $3,000-7,000 for software licensing, plus additional per user and hosting fees.
      About this Approach:

      SOP tools such as Princeton Center’s SOP ExpressTM and SOP Tracks or MasterControl’s SOP Management and eSOP allow organizations to create, manage, and access SOPs. These programs typically offer a range of SOP templates and formats, electronic signatures, version control, and review options and training features such as quizzes and monitoring.

      Similarly, DR planning solutions (e.g. eBRP, Recovery Planner, LDRPS, etc.) provide templates, tools, and document management to create DR documentation including SOPs.

      Consider leveraging SharePoint to provide document management capabilities

      Portability/External Access:
      • Pros: SharePoint is commonly web-enabled and supports external access with appropriate security and user administration.
      • Cons: Must be installed at redundant sites or be cloud-based to be effective in the event of a worst-case scenario disaster recovery situation in which the primary data center is down.
      Maintainability/Usability:
      • Pros: Built-in document management (e.g. version control, metadata support, etc.) as well as centralized access to required documents.
      • Pros: No tool learning curve – SharePoint and MS Office would be existing solutions already used on a daily basis.
      • Cons: No built-in automated updates (e.g. automated updates to contacts throughout the system).
      • Cons: Consistency depends on creating templates and implementing processes for document updates, review, and approval.
      Cost/Effort:
      • Pros: Using existing tools, so this is a sunk cost in terms of capex.
      • Cons: Additional effort required to create templates and manage the documentation library.

      For more information on SharePoint as a content management solution, see Info-Tech’s Use SharePoint for Enterprise Content Management.

      About this Approach:

      Most SOP documents start as MS Office documents, even if there is an SOP tool available (some SOP tools actually run within MS Office on the desktop). For organizations that decide to bypass a formal SOP tool, the biggest gap they have to overcome is document management.

      Many organizations are turning to SharePoint to meet this need. For those that already have SharePoint in place, it makes sense to further leverage SharePoint for SOP documentation.

      For SharePoint to be a practical solution, the documentation must still be accessible if the primary data center is down, e.g. by having redundant SharePoint instance at multiple in-house locations or using a cloud-based SharePoint solution.

      As an alternative to SharePoint, SaaS tools such as Power DMS, NetDocuments, Xythos on Demand, Knowledge Tree, Spring CM, and Zoho Docs offer cloud-based document management, authoring, and distribution services that can work well for SOPs. Some of these, such as Power DMS and Spring CM, are geared specifically toward workflows.

      A wiki may be all you need

      Portability/External Access:
      • Pros: Wiki sites can support external access as with any web solution.
      • Cons: May lack more sophisticated content management features.
      Maintainability/Usability:
      • Pros: Built-in document management (e.g. version control, metadata support, etc.) as well as centralized access to required information.
      • Pros: Authorized users can make updates dynamically, depending on how much restriction you have on the site.
      • Cons: No built-in automation (e.g. automated updates to contacts throughout the system).
      • Cons: Consistency depends on creating templates and implementing processes for document updates, review, and approval.
      Cost/Effort:
      • Pros: An inexpensive option compared to traditional content management solutions such as SharePoint.
      • Cons: Learning curve if wikis are new to your organization.
      About this Approach:

      Wiki sites are websites where users collaborate to create and edit the content. Wikipedia is an example.

      While wiki sites are typically used for collaboration and dynamic content development, the traditional collaborative authoring model can be restricted to provide structure and an approval process.

      Several tools are available to create and manage wiki sites (and other collaboration solutions), as outlined in the following research:

      An approach that I’ve seen work well is to consult the wiki for any task, activity, job, etc. Is it documented? If not, then document it there and then. Sure, this led to 6-8 weeks of huge effort, but the documentation grew in terms of volume and quality at an alarming but pleasantly surprising rate. Providing an environment to create the documentation is important and a wiki is ideal. Fast, lightweight, in-browser editing leads to little resistance in creating documents.

      - Lee Blackwell, Global IT Operation Services Manager, Avid Technology

      Managing SOPs on a shared network drive involves major challenges and limitations

      Portability/External Access:
      • Cons: Must be hosted at redundant sites in order to be effective in a worst-case scenario that takes down your data center.
      Maintainability/Usability:
      • Pros: Easy to implement and no learning curve.
      • Pros: Access can be easily managed.
      • Cons: Version control, standardization, and document management can be significant challenges.
      Cost/Effort:
      • Pros: Little to no cost and no tool management required.
      • Cons: Managing documents on a shared network drive requires strict attention to process for version control, updates, approvals, and distribution.
      About this Approach:

      With this strategy, SOP documents are stored and managed locally on a shared network drive. Only process owners and administrators have read-write permissions on documents on the shared drive.

      The administrator grants access and manages security permissions.

      Info-Tech Insight

      For small organizations, the shared network drive approach can work, but this is ultimately a short-term solution. Move to an online library by creating a wiki site. Start slow by beginning with a particular department or project, then evaluate how well your staff adapt to this technology as well as its potential effectiveness in your organization. Refer to the Info-Tech collaboration strategy research cited on the previous slide for additional guidance.

      Avoid extensive use of paper copies of SOP documentation

      SOP documents need to be easy to update, accessible from anywhere, and searchable. Paper doesn’t meet these needs.

      Portability/External Access:
      • Pros: Does not rely on technology or power.
      • Cons: Not adequate for disaster recovery situations; would require all staff to have a copy and to have it with them at all times.
      Maintainability/Usability:
      • Pros: In terms of usability, again there is no dependence on technology.
      • Cons: Updates need to be printed and distributed to all relevant staff every time there is a change to ensure staff have access to the latest most accurate documentation.
      • Cons: Navigation to other information is manual – flipping through pages etc. No searching or hyperlinks.
      Cost/Effort:
      • Pros: No technology system to maintain, aside from what you use for printing.
      • Cons: Printing expenses are actually among the highest incurred by organizations and this adds to it.
      • Cons: Labor-intensive due to need to print and physically distribute documentation updates.
      About this Approach

      Traditionally, SOPs were printed and kept somewhere in a large binder (or several large binders). This isn’t adequate to the needs of most organizations and typically results in documents that aren’t up to date or effective.

      Use Info-Tech’s solution evaluation tool to decide on a publishing and document management strategy

      All organizations have existing document management methodologies, even if it’s simply storing documents on a network drive.

      Use Info-Tech’s solution evaluation tool to decide whether your existing solution meets the portability/external access, maintainability/usability, and cost/effort criteria, or whether you need to explore a different option.

      Note: This tool was originally built to evaluate DRP publishing options, so the tool name and terminology refers to DR. However, the same tool can be used to evaluate general SOP publishing and document management solutions.

      The image is a screenshot of Info-Tech's evaluation tool
      Consider using Info-Tech’s DRP Publishing and Document Management Solution Evaluation Tool.

      Info-Tech Insight

      There is no absolute ranking for possible solutions. The right choice will depend on factors such as current in-house tools, maturity around document management, the size of your IT department, and so on. For example, a small shop may do very well with the USB drive strategy, whereas a multi-national company will need a more formal strategy to ensure consistent application of corporate guidelines.

      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

      Decide on a publishing and document management strategy

      Review the pros and cons of different strategies for publishing and document management. Identify needs, priorities, and limitations of your environment. Create a shortlist of options that can meet your organization’s needs and priorities.

      3.2

      Complete the solution evaluation tool

      Evaluate solutions on the shortlist to identify the strongest option for your organization, based on the criteria of maintainability, affordability, effort to implement, and accessibility/portability.

      Insight breakdown

      Create visual documents, not dense SOP manuals.

      • Visual documents that can be scanned are more usable and easier to update.
      • Flowcharts, checklists, and diagrams all have their place in visual documentation.

      Start with high-impact SOPs.

      • It can be difficult to decide where to start when faced with a major documentation backlog.
      • Focus first on client facing and high-impact SOPs, i.e. mission-critical operations, service management, and disaster recovery procedures.

      Integrate SOP creation into project requirements and hold staff accountable.

      • Holding staff accountable does not provide all the benefits of a well documented and maintained SOP, but it minimizes procrastination, so the work is ultimately done in a more timely manner.

      Summary of accomplishment

      Knowledge Gained

      SOPs may not be exciting, but they’re very important to organizational consistency, efficiency, and improvement.

      This blueprint outlined how to:

      • Prioritize and execute SOP documentation work.
      • Establish a sustainable process for creating and maintaining SOP documentation.
      • Choose a content management solution for best fit.

      Processes Optimized

      • Multiple processes supporting mission-critical operations, service management, and disaster recovery were documented. Gaps in those processes were uncovered and addressed.
      • In addition, your process for maintaining process documents was improved, including adding documentation requirements and steps requiring documentation approval.

      Deliverables Completed

      As part of completing this project, the following deliverables were completed:

      • Standard Operating Procedures Workbook
      • Standard Operating Procedures Project Roadmap Tool
      • Document Management Checklist
      • Publishing and Document Management Solution Evaluation Tool

      Project step summary

      Client Project: Create and maintain visual SOP documentation.

      1. Prioritize undocumented SOPs.
      2. Develop visual SOP documentation.
      3. Optimize and document critical processes.
      4. Establish guidelines for identifying and organizing SOPs.
      5. Define a process for documenting and maintaining SOPs.
      6. Plan time with experts to put a dent in your documentation backlog.
      7. Understand the options for content management solutions.
      8. Identify the right content management solution for your organization.

      Info-Tech Insight

      This project has the ability to fit the following formats:

      • Onsite workshop by Info-Tech Research Group consulting analysts.
      • Do-it-yourself with your team.
      • Remote delivery (Info-Tech Guided Implementation).

      Bibliography

      Anderson, Chris. “What is a Standard Operating Procedure (SOP)?” Bizmanualz, Inc. No date. Web. 25 Jan. 2016. https://www.bizmanualz.com/save-time-writing-procedures/what-are-policies-and-procedures-sop.html

      Grusenmeyer, David. “Developing Effective Standard Operating Procedures.” Dairy Business Management. 1 Feb. 2003. Web. 25 Jan. 2016. https://ecommons.cornell.edu/handle/1813/36910

      Mosaic. “The Value of Standard Operating Procedures.” 22 Oct. 2012. Web. 25 Jan. 2016. ttp://www.mosaicprojects.com.au/WhitePapers/WP1086_Standard_Operating_Procedures.pdf

      Sinn, John W. “Lean, Six Sigma, Quality Transformation Toolkit (LSSQTT) Tool #17 Courseware Content – Standard Operating Procedures (SOP) For Lean and Six Sigma: Infrastructure for Understanding Process.” Summer 2006. Web. 25 Jan. 2016. https://www.bgsu.edu/content/dam/BGSU/college-of-technology/documents/LSSQTT/LSSQTT%20Toolkit/toolkit3/LSSQTT-Tool-17.pdf

      United States Environmental Protection Agency. “Guidance for Preparing Standard Operating Procedures (SOPs).” April 2007. Web. 25 Jan. 2016. http://www.epa.gov/sites/production/files/2015-06/documents/g6-final.pdf

      Make Prudent Decisions When Increasing Your Salesforce Footprint

      • Buy Link or Shortcode: {j2store}134|cart{/j2store}
      • member rating overall impact: 8.9/10 Overall Impact
      • member rating average dollars saved: $55,224 Average $ Saved
      • member rating average days saved: 4 Average Days Saved
      • Parent Category Name: Licensing
      • Parent Category Link: /licensing
      • Too often, organizations fail to achieve economy of scale. They neglect to negotiate price holds, do not negotiate deeper discounts as volume increases, or do not realize there are already existing contracts within the organization.
      • Understand what to negotiate. Organizations do not know what can and cannot be negotiated, which means value gets left on the table.
      • Integrations with other applications must be addressed from the outset. Many users buy the platform only to realize later on that the functionality they wanted does not exist and may be an extra expense with customization.

      Our Advice

      Critical Insight

      • Buying power dissipates when you sign the contract. Get the right product for the right number of users for the right term and get it right the first time.
      • Getting the best price does not assure a great total cost of ownership or ROI. There are many components as part of the purchasing process that if unaccounted for can lead to dramatic and unbudgeted spend.
      • Avoid buyer’s remorse through due diligence before signing the deal. If you need to customize the software or extend it with a third-party add-in, identify your costs and timelines upfront. Plan for successful adoption.

      Impact and Result

      • Centralize purchasing instead of enabling small deals to maximize discount levels by creating a process to derive a cost-effective methodology when subscribing to Sales Cloud, Service Cloud, and Force.com.
      • Educate your organization on Salesforce’s licensing methods and contract types, enabling informed purchasing decisions. Critical components of every agreement that need to be negotiated are a renewal escalation cap, term protection, and license metrics to document what comes with each. Re-bundling protection is also critical in case a product is no longer desired.
      • Proactively addressing integrations and business requirements will enable project success and enable the regular upgrades the come with a multi-tenant cloud services SaaS solution.

      Make Prudent Decisions When Increasing Your Salesforce Footprint Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you need to understand and document your Salesforce licensing strategy, 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. Establish software requirements

      Begin your journey by understanding whether Salesforce is the right CRM. Also proactively approach Salesforce licensing by understanding which information to gather and assessing the current state and gaps.

      • Make Prudent Decisions When Increasing Your Salesforce Footprint – Phase 1: Establish Software Requirements
      • Salesforce Licensing Purchase Reference Guide
      • RASCI Chart

      2. Evaluate licensing options

      Review current products and licensing models to determine which licensing models will most appropriately fit the organization's environment.

      • Make Prudent Decisions When Increasing Your Salesforce Footprint – Phase 2: Evaluate Licensing Options
      • Salesforce TCO Calculator
      • Salesforce Discount Calculator

      3. Evaluate agreement options

      Review Salesforce’s contract types and assess which best fits the organization’s licensing needs.

      • Make Prudent Decisions When Increasing Your Salesforce Footprint – Phase 3: Evaluate Agreement Options
      • Salesforce Terms and Conditions Evaluation Tool

      4. Purchase and manage licenses

      Conduct negotiations, purchase licensing, finalize a licensing management strategy, and enhance your CRM with a Salesforce partner.

      • Make Prudent Decisions When Increasing Your Salesforce Footprint – Phase 4: Purchase and Manage Licenses
      • Controlled Vendor Communications Letter
      • Vendor Communication Management Plan
      [infographic]

      Workshop: Make Prudent Decisions When Increasing Your Salesforce Footprint

      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 Software Requirements

      The Purpose

      Assess current state and align goals; review business feedback.

      Interview key stakeholders to define business objectives and drivers.

      Key Benefits Achieved

      Have a baseline for whether Salesforce is the right solution.

      Understand Salesforce as a solution.

      Examine all CRM options.

      Activities

      1.1 Perform requirements gathering to review Salesforce as a potential solution.

      1.2 Gather your documentation before buying or renewing.

      1.3 Confirm or create your Salesforce licensing team.

      1.4 Meet with stakeholders to discuss the licensing options and budget allocation.

      Outputs

      Copy of your Salesforce Master Subscription Agreement

      RASCI Chart

      Salesforce Licensing Purchase Reference Guide

      2 Evaluate Licensing Options

      The Purpose

      Review product editions and licensing options.

      Review add-ons and licensing rules.

      Key Benefits Achieved

      Understand how licensing works.

      Discuss licensing rules and their application to your current environment.

      Determine the product and license mix that is best for your requirements.

      Activities

      2.1 Determine the editions, licenses, and add-ons for your Salesforce CRM solution.

      2.2 Calculate total cost of ownership.

      2.3 Use the Salesforce Discount Calculator to ensure you are getting the discount you deserve.

      2.4 Meet with stakeholders to discuss the licensing options and budget allocation.

      Outputs

      Salesforce CRM Solution

      Salesforce TCO Calculator

      Salesforce Discount Calculator

      Salesforce Licensing Purchase Reference Guide

      3 Evaluate Agreement Options

      The Purpose

      Review terms and conditions of Salesforce contracts.

      Review vendors.

      Key Benefits Achieved

      Determine if MSA or term agreement is best.

      Learn what specific terms to negotiate.

      Activities

      3.1 Perform a T&Cs review and identify key “deal breakers.”

      3.2 Decide on an agreement that nets the maximum benefit.

      Outputs

      Salesforce T&Cs Evaluation Tool

      Salesforce Licensing Purchase Reference Guide

      4 Purchase and Manage Licenses

      The Purpose

      Finalize the contract.

      Discuss negotiation points.

      Discuss license management and future roadmap.

      Discuss Salesforce partner and implementation strategy.

      Key Benefits Achieved

      Discuss negotiation strategies.

      Learn about licensing management best practices.

      Review Salesforce partner options.

      Create an implementation plan.

      Activities

      4.1 Know the what, when, and who to negotiate.

      4.2 Control the flow of communication.

      4.3 Assign the right people to manage the environment.

      4.4 Discuss Salesforce partner options.

      4.5 Discuss implementation strategy.

      4.6 Meet with stakeholders to discuss licensing options and budget allocation.

      Outputs

      Salesforce Negotiation Strategy

      Vendor Communication Management Plan

      RASCI Chart

      Info-Tech’s Core CRM Project Plan

      Salesforce Licensing Purchase Reference Guide

      Human Resources Management

      • Buy Link or Shortcode: {j2store}31|cart{/j2store}
      • Related Products: {j2store}31|crosssells{/j2store}
      • member rating overall impact: 9.6/10
      • member rating average dollars saved: $13,367
      • member rating average days saved: 7
      • Parent Category Name: people and Resources
      • Parent Category Link: /people-and-resources
      Talent is the differentiator; availability is not.

      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]

      CIO Priorities 2022

      • Buy Link or Shortcode: {j2store}328|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $31,499 Average $ Saved
      • member rating average days saved: 9 Average Days Saved
      • Parent Category Name: Innovation
      • Parent Category Link: /innovation
      • Understand how to respond to trends affecting your organization.
      • Determine your priorities based on current state and relevant internal factors.
      • Assign the right amount of resources to accomplish your vision.
      • Consider what new challenges outside of your control will demand a response.

      Our Advice

      Critical Insight

      A priority is created when external factors hold strong synergy with internal goals and an organization responds by committing resources to either avert risk or seize opportunity. These are the priorities identified in the report:

      1. Reduce Friction in the Hybrid Operating Model
      2. Improve Your Ransomware Readiness
      3. Support an Employee-Centric Retention Strategy
      4. Design an Automation Platform
      5. Prepare to Report on New Environmental, Social, and Governance Metrics

      Impact and Result

      Update your strategic roadmap to include priorities that are critical and relevant for your organization based on a balance of external and internal factors.

      CIO Priorities 2022 Research & Tools

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

      1. CIO Priorities 2022 – A report on the key priorities for competing in the digital economy.

      Discover Info-Tech’s five priorities for CIOs in 2022.

      • CIO Priorities Report for 2022

      2. Listen to the podcast series

      Hear directly from our contributing experts as they discuss their case studies with Brian Jackson.

      • Frictionless hybrid working: How the Harvard Business School did it
      • Close call with ransomware: A CIO recounts a near security nightmare
      • How a financial services company dodged "The Great Resignation"
      • How Allianz took a blockchain platform from pilot to 1 million transactions
      • CVS Health chairman David Dorman on healthcare's hybrid future

      Infographic

      Further reading

      CIO Priorities 2022

      A jumble of business-related words. Info-Tech’s 2022 Tech Trends survey asked CIOs for their top three priorities. Cluster analysis of their open-ended responses shows four key themes:
      1. Business process improvements
      2. Digital transformation or modernization
      3. Security
      4. Supporting revenue growth or recovery

      Info-Tech’s annual CIO priorities are formed from proprietary primary data and consultation with our internal experts with CIO stature

      2022 Tech Trends Survey CIO Demographic N=123

      Info-Tech’s Tech Trends 2022 survey was conducted between August and September 2021 and collected a total of 475 responses from IT decision makers, 123 of which were at the C-level. Fourteen countries and 16 industries are represented in the survey.

      2022 IT Talent Trends Survey CIO Demographic N=44

      Info-Tech’s IT Talent Trends 2022 survey was conducted between September and October 2021 and collected a total of 245 responses from IT decision makers, 44 of which were at the C-level. A broad range of countries from around the world are represented in the survey.

      Internal CIO Panels’ 125 Years Of Combined C-Level IT Experience

      Panels of former CIOs at Info-Tech focused on interpreting tech trends data and relating it to client experiences. Panels were conducted between November 2021 and January 2022.

      CEO-CIO Alignment Survey Benchmark Completed By 107 Different Organizations

      Info-Tech’s CEO-CIO Alignment program helps CIOs align with their supervisors by asking the right questions to ensure that IT stays on the right path. It determines how IT can best support the business’ top priorities and address the gaps in your strategy. In 2021, the benchmark was formed by 107 different organizations.

      Build IT alignment

      IT Management & Governance Diagnostic Benchmark Completed By 320 Different Organizations

      Info-Tech’s Management and Governance Diagnostic helps IT departments assess their strengths and weaknesses, prioritize their processes and build an improvement roadmap, and establish clear ownership of IT processes. In 2021, the benchmark was formed by data from 320 different organizations.

      Assess your IT processes

      The CIO priorities are informed by Info-Tech’s trends research reports and surveys

      Priority: “The fact or condition of being regarded or treated as more important than others.” (Lexico/Oxford)

      Trend: “A general direction in which something is developing or changing.” (Lexico/Oxford)

      A sequence of processes beginning with 'Sensing', 'Hypothesis', 'Validation', and ending with 'Trends, 'Priorities'. Under Sensing is Technology Research, Interviews & Insights, Gathering, and PESTLE. Under Hypothesis is Near-Future Probabilities, Identify Patterns, Identify Uncertainties, and Identify Human Benefits. Under Validation is Test Hypothesis, Case Studies, and Data-Driven Insights. Under Trends is Technology, Talent, and Industry. Under Priorities is CIO, Applications, Infrastructure, and Security.

      Visit Info-Tech’s Trends & Priorities Research Center

      Image called 'Defining the CIO Priorities for 2022'. Image shows 4 columns, Implications, Resource Investment, Amplifiers, and Actions and Outcomes, with 2 dotted lines, labeled External Context and Internal Context, running through all 4 columns and leading to bottom-right label called CIO Priorities Formed

      The Five Priorities

      Priorities to compete in the digital economy

      1. Reduce Friction in the Hybrid Operating Model
      2. Improve Your Ransomware Readiness
      3. Support an Employee-Centric Retention Strategy
      4. Design an Automation Platform
      5. Prepare to Report on New Environmental, Social, and Governance Metrics

      Reduce friction in the hybrid operating model

      Priority 01 | APO07 Human Resources Management

      Deliver solutions that create equity between remote workers and office workers and make collaboration a joy.

      Hybrid work is here to stay

      CIOs must deal with new pain points related to friction of collaboration

      In 2020, CIOs adapted to the pandemic’s disruption to offices by investing in capabilities to enable remote work. With restrictions on gathering in offices, even digital laggards had to shift to an all-remote work model for non-essential workers.

      Most popular technologies already invested in to facilitate better collaboration

      • 24% Web Conferencing
      • 23% Instant Messaging
      • 20% Document Collaboration

      In 2022, the focus shifts to solving problems created by the new hybrid operating model where some employees are in the office and some are working remotely. Without the ease of collaborating in a central hub, technology can play a role in reducing friction in several areas:

      • Foster more connections between employees. Remote workers are less likely to collaborate with people outside of their department and less likely to spontaneously collaborate with their peers. CIOs should provide a digital employee experience that fosters collaboration habits and keeps workers engaged.
      • Prevent employee attrition. With more workers reevaluating their careers and leaving their jobs, CIOs can help employees feel connected to the overall purpose of the organization. Finding a way to maintain culture in the new context will require new solutions. While conference room technology can be a bane to IT departments, making hybrid meetings effortless to facilitate will be more important.
      • Provide new standards for mediated collaboration. Meeting isn’t as easy as simply gathering around the same table anymore. CIOs need to provide structure around how hybrid meetings are conducted to create equity between all participants. Business continuity processes must also consider potential outages for collaboration services so employees can continue the work despite a major outage.

      Three in four organizations have a “hybrid” approach to work. (Tech Trends 2022 Survey)

      In most organizations, a hybrid model is being implemented. Only 14.9% of organizations are planning for almost everyone to return to the office, and only 9.9% for almost everyone to work remotely.

      Elizabeth Clark

      CIO, Harvard Business School

      "I want to create experiences that are sticky. That keep people coming back and engaging with their colleagues."

      Photo of Elizabeth Clark, CIO, Harvard Business School.

      Listen to the Tech Insights podcast:
      Frictionless hybrid working: How the Harvard Business School did it

      Internal interpretation: Harvard Business School

      • March 2020
        The pandemic disrupts in-class education at Harvard Business School. Their case study method of instruction that depends on in-person, high-quality student engagement is at risk. While students and faculty completed the winter semester remotely, the Dean and administration make the goal to restore the integrity of the classroom experience with equity for both remote and in-person students.
      • May 2020
        A cross-functional task force of about 100 people work intensively, conducting seven formal experiments, 80 smaller tests, and hundreds of polling data points, and a technology and facilities solution is designed: two 4K video cameras capturing both the faculty and the in-class students, new ceiling mics, three 85-inch TV screens, and students joining the videoconference from their laptops. A custom Zoom room, combining three separate rooms, integrated all the elements in one place and integrated with the lecture capture system and learning management system.
      • October 2020
        Sixteen classrooms are renovated to install the new solution. Students return to the classroom but in lower numbers due to limits on in-room capacity, but students rotate between the in-person and remote experience.
      • September 2021
        Renovations for the hybrid solution are complete in 26 classrooms and HBS has determined this will be its standard model for the classroom. The case method of teaching is kept alive and faculty and students are thrilled with the results.
      • November 2021
        HBS is adapting its solution for the classroom to its conference rooms and has built out eight different rooms for a hybrid experience. The 4K cameras and TV screens capture all participants in high fidelity as well as the blackboard.

      Photo of a renovated classroom with Zoom participants integrated with the in-person students.
      The renovated classrooms integrate all students, whether they are participating remotely or in person. (Image courtesy of Harvard Business School.)

      Implications: Organization, Process, Technology

      External

      • Organization – About half of IT practitioners in the Tech Trends 2022 survey feel that IT leaders, infrastructure and operations teams, and security teams were “very busy” in 2021. Capacity to adapt to hybrid work could be constrained by these factors.
      • Process – Organizations that want employees to benefit from being back in the office will have to rethink how workers can get more value out of in-person meetings that also require videoconference participation with remote workers.
      • Technology – Fifty-four percent of surveyed IT practitioners say the pandemic raised IT spending compared to the projections they made in 2020. Much of that investment went into adapting to a remote work environment.

      Internal

      • Organization – HBS added 30 people to its IT staff on term appointments to develop and implement its hybrid classroom solutions. Hires included instructional designers, support technicians, coordinators, and project managers.
      • Process – Only 25 students out of the full capacity of 95 could be in the classroom due to COVID-19 regulations. On-campus students rotated through the classroom seats. An app was created to post last-minute seat availability to keep the class full.
      • Technology – A Zoom room was created that combines three rooms to provide the full classroom experience: a view of the instructor, a clear view of each student that enlarges when they are speaking, and a view of the blackboard.

      Resources Applied

      Appetite for Technology

      CIOs and their direct supervisors both ranked internal collaboration tools as being a “critical need to adopt” in 2021, according to Info-Tech’s CEO-CIO Alignment Benchmark Report.

      Intent to Invest

      Ninety-seven percent of IT practitioners plan to invest in technology to facilitate better collaboration between employees in the office and outside the office by the end of 2022, according to Info-Tech’s 2022 Tech Trends survey.

      “We got so many nice compliments, which you don’t get in IT all the time. You get all the complaints, but it’s a rare case when people are enthusiastic about something that was delivered.” (Elizabeth Clark, CIO, Harvard Business School)

      Harvard Business School

      • IT staff were reassigned from other projects to prioritize building a hybrid classroom solution. A cloud migration and other portfolio projects were put on pause.
      • The annual capital A/V investment was doubled. The amount of spend on conference rooms was tripled.
      • Employees were hired to the media services team at a time when other areas of the organization were frozen.

      Outcomes at Harvard Business School

      The new normal at Harvard Business School

      New normal: HBS has found its new default operating model for the classroom and is extending its solution to its operating environment.

      Improved CX: The high-quality experience for students has helped avoid attrition despite the challenges of the pandemic.

      Engaged employees: The IT team is also engaged and feels connected to the mission of the school.

      Photo of a custom Zoom room bringing together multiple view of the classroom as well as all remote students.
      A custom Zoom room brings together multiple different views of the classroom into one single experience for remote students. (Image courtesy of Harvard Business School.)

      From Priorities to Action

      Make hybrid collaboration a joy

      Align with your organization’s goals for collaboration and customer interaction, with the target of high satisfaction for both customers and employees. Invest in capital projects to improve the fidelity of conference rooms, develop and test a new way of working, and increase IT capacity to alleviate pressure points.

      Foster both asynchronous and synchronous collaboration approaches to avoid calendars filling up with videoconference meetings to get things done and to accommodate workers contributing from across different time zones.

      “We’ll always have hybrid now. It’s opened people’s eyes and now we’re thinking about the future state. What new markets could we explore?” (Elizabeth Clark, CIO, Harvard Business School)

      Take the next step

      Run Better Meetings
      Hybrid, virtual, or in person – set meeting best practices that support your desired meeting norms.

      Prepare People Leaders for the Hybrid Work Environment
      Set hybrid work up for success by providing people leaders with the tools they need to lead within the new model.

      Hoteling and Hot-Desking: A Primer
      What you need to know regarding facilities, IT infrastructure, maintenance, security, and vendor solutions for desk hoteling and hot-desking.

      “Human Resources Management” gap between importance and effectiveness
      Info-Tech Research Group Management and Governance Diagnostic Benchmark 2021

      A bar chart illustrating the Human Resources Management gap between importance and effectiveness. The difference is marked as Delta 2.3.

      Improve your ransomware readiness

      Priority 02 | APO13 Security Strategy

      Mitigate the damage of successful ransomware intrusions and make recovery as painless as possible.

      The ransomware crisis threatens every organization

      Prevention alone won’t be enough against the forces behind ransomware.

      Cybersecurity is always top of mind for CIOs but tends to be deprioritized due to other demands related to digital transformation or due to cost pressures. That’s the case when we examine our data for this report.

      Cybersecurity ranked as the fourth-most important priority by CIOs in Info-Tech’s 2022 Tech Trends survey, behind business process improvement, digital transformation, and modernization. Popular ways to prepare for a successful attack include creating offline backups, purchasing insurance, and deploying new solutions to eradicate ransomware.

      CIOs and their direct supervisors ranked “Manage IT-Related Security” as the third-most important top IT priority on Info-Tech’s CEO-CIO Alignment Benchmark for 2021, in support of business goals to manage risk, comply with external regulation, and ensure service continuity.

      Most popular ways for organizations to prepare for the event of a successful ransomware attack:

      • 25% Created offline backups
      • 18% Purchased cyberinsurance
      • 19% New tech to eradicate ransomware

      Whatever priority an organization places on cybersecurity, when ransomware strikes, it quickly becomes a red alert scenario that disrupts normal operations and requires all hands on deck to respond. Sophisticated attacks executed at wide scale demonstrate that security can be bypassed without creating an alert. After that’s accomplished, the perpetrators build their leverage by exfiltrating data and encrypting critical systems.

      CIOs can plan to mitigate ransomware attacks in several constructive ways:

      • Business impact analysis. Determine the costs of an outage for specific periods and the system and data recovery points in time.
      • Engage a partner for 24/7 monitoring. Gain real-time awareness of your critical systems.
      • Review your identity access management (IAM) policies. Use of multi-factor authentication and limiting access to only the roles that need it reduces ransomware risk.

      50% of all organizations spent time and money specifically to prevent ransomware in the past year. (Info-Tech Tech Trends 2022 Survey)

      John Doe

      CIO, mid-sized manufacturing firm in the US

      "I want to create experiences that are sticky. That keep people coming back and engaging with their colleagues."

      Blank photo.

      Listen to the Tech Insights podcast:
      Close call with ransomware: a CIO recounts a near security nightmare

      Internal interpretation: US-based, mid-sized manufacturing firm

      • May 1, 2021
        A mid-sized manufacturing firm (“The Firm”) CIO gets a call from his head of security about odd things happening on the network. A call is made to Microsoft for support. Later that night, the report is that an unwanted crypto-mining application is the culprit. But a couple of hours later, that assessment is proven wrong when it’s realized that hundreds of systems are staged for a ransomware attack. All the attacker has to do is push the button.
      • May 2, 2021
        The Firm disconnects all its global sites to cut off new pathways for the malware to infect. All normal operations cease for 24 hours. It launches its cybersecurity insurance process. The CIO engages a new security vendor, CrowdStrike, to help respond. Employees begin working from home if they can so they can make use of their own internet service. The Firm has cut off its public internet connectivity and is severed from cloud services such as Azure storage and collaboration software.
      • May 4, 2021
        The hackers behind the attack are revealed by security forensics experts. A state-sponsored agency in Russia set up the ransomware and left it ready to execute. It sold the staged attack to a cybercriminal group, Doppel Spider. According to CrowdStrike, the group uses malware to run “big game hunting operations” and targets 18 different countries including the US and multiple industries, including manufacturing.
      • May 10, 2021
        The Firm has totally recovered from the ransomware incident and avoided any serious breach or paying a ransom. The CIO worked more hours than at any other point in his career, logging an estimated 130 hours over the two weeks.
      • November 2021
        The Firm never previously considered itself a ransomware target but has now reevaluated that stance. It has hired a service provider to run a security operations center on a 24/7 basis. It's implemented a more sophisticated detection and response model and implemented multi-factor authentication. It’s doubled its security spend in 2021 and will invest more in 2022.

      “Now we take the approach that if someone does get in, we're going to find them out.” (John Doe, CIO, “The Firm”)

      Implications: Organization, Process, Technology

      External

      • Organization – Organizations must consider how their employees play a role in preventing ransomware and plan for training to recognize phishing and other common traps. They must make plans for employees to continue their work if systems are disrupted by ransomware.
      • Process – Backup processes across multiple systems should be harmonized to have both recent and common points to recover from. Work with the understanding IT will have to take systems offline if ransomware is discovered and there is no time to ask for permission.
      • Technology – Organizations can benefit from security services provided by a forensics-focused vendor. Putting cybersecurity insurance in place not only provides financial protection but also guidance in what to do and which vendors to work with to prevent and recover from ransomware.

      Internal

      • Organization – The Firm was prepared with a business continuity plan to allow many of its employees to work remotely, which was necessary because the office network was incapacitated for ten days during recovery.
      • Process – Executives didn’t seek to assign blame for the security incident but took it as a signal there were some new costs involved to stay in business. It initiated new outsource relationships and hired one more full-time employee to shore up security resources.
      • Technology – New ransomware eradication software was deployed to 2,000 computers. Scripted processes automated much of the work, but in some cases full system rebuilds were required. Backup systems were disconnected from the network as soon as the malware was discovered.

      Resources Applied

      Consider the Alternative

      Organizations should consider how much a ransomware attack on critical systems would cost them if they were down for a minimum of 24-48 hours. Plan to invest an amount at least equal to the costs of that downtime.

      Ask for ID

      Implementing across-the-board multi-factor authentication reduces chances of infection and is cheap, with enterprise solutions ranging from $2 to $5 per user on average. Be strict and deny access when connections don’t authenticate.

      “You'll never stop everything from getting into the network. You can still focus on stopping the bad actors, but then if they do make it in, make sure they don't get far.” (John Doe, CIO, “The Firm”)

      “The Firm” (Mid-Sized Manufacturer)

      • During the crisis, The Firm paused all activities and focused solely on isolating and eliminating the ransomware threat.
      • New outsourcing relationship with a vendor provides a 24/7 Security Operations Center.
      • One more full-time employee on the security team.
      • Doubled investment in security in 2021 and will spend more in 2022.

      Outcomes at “The Firm” (Mid-Sized Manufacturer)

      The new cost of doing business

      Real-time security: While The Firm is still investing in prevention-based security, it is also developing its real-time detection and response capabilities. When ransomware makes it through the cracks, it wants to know as soon as possible and stop it.

      Leadership commitment: The C-suite is taking the experience as a wake-up call that more investment is required in today’s threat landscape. The Firm rates security more highly as an overall organizational goal, not just something for IT to worry about.

      Stock photo of someone using their phone while sitting at a computer, implying multi-factor authentication.
      The Firm now uses multi-factor authentication as part of its employee sign-on process. For employees, authenticating is commonly achieved by using a mobile app that receives a secret code from the issuer.

      From Priorities to Action

      Cybersecurity is everyone’s responsibility

      In Info-Tech’s CEO-CIO Alignment Benchmark for 2021, the business goal of “Manage Risk” was the single biggest point of disagreement between CIOs and their direct supervisors. CIOs rank it as the second-most important business goal, while CEOs rank it as sixth-most important.

      Organizations should align on managing risk as a top priority given the severity of the ransomware threat. The threat actors and nature of the attacks are such that top leadership must prepare for when ransomware hits. This includes halting operations quickly to contain damage, engaging third-party security forensics experts, and coordinating with government regulators.

      Cybersecurity strategies may be challenged to be effective without creating some friction for users. Organizations should look beyond multi-layer prevention strategies and lean toward quick detection and response, spending evenly across prevention, detection, and response solutions.

      Take the next step

      Create a Ransomware Incident Response Plan
      Don’t be the next headline. Determine your current readiness, response plan, and projects to close gaps.

      Simplify Identity and Access Management
      Select and implement IAM and produce vendor RFPs that will contain the capabilities you need, including multi-factor authentication.

      Cybersecurity Series Featuring Sandy Silk
      More from Info-Tech’s Senior Workshop Director Sandy Silk in this video series created while she was still at Harvard University.

      Gap between CIOs and CEOs in points allocated to “Manage risk” as a top business goal

      A bar chart illustrating the gap between CIOs and CEOs in points allocated to 'Manage risk' as a top business goal. The difference is marked as Delta 1.5.

      Support an employee-centric retention strategy

      Priority 03 | ITRG02 Leadership, Culture & Values

      Avoid being a victim of “The Great Resignation” by putting employees at the center of an experience that will engage them with clear career path development, purposeful work, and transparent feedback.

      Defining an employee-first culture that improves retention

      The Great resignation isn’t good for firms

      In 2021, many workers decided to leave their jobs. Working contexts were disrupted by the pandemic and that saw non-essential workers sent home to work, while essential workers were asked to continue to come into work despite the risks of COVID-19. These disruptions may have contributed to many workers reevaluating their professional goals and weighing their values differently. At the same time, 2021 saw a surging economy and many new job opportunities to create a talent-hungry market. Many workers could have been motivated to take a new opportunity to increase their salary or receive other benefits such as more flexibility.

      Annual turnover rate for all us employees on the rise

      • 20% – Jan.-Aug. 2020, Dipped from 22% in 2019
      • 25% Jan.-Aug. 2021, New record high
      • Data from Visier Inc.

      When you can’t pay them, develop them

      IT may be less affected than other departments by this trend. Info-Tech’s 2022 IT Talent Trends Report shows that on average, estimated turnover rate in IT is lower than the rest of the organization. Almost half of respondents estimated their organization’s voluntary turnover rate was 10% or higher. Only 30% of respondents estimate that IT’s voluntary turnover rate is in the same range. However, CIOs working in industries with the highest turnover rates will have to work to keep their workers engaged and satisfied, as IT skills are easily transferred to other industries.

      49% ranked “enabling learning & development within IT” as high priority, more than any other single challenge. (IT Talent Trends 2022 Survey, N=227)

      A bar chart of 'Industries with highest turnover rates (%)' with 'Leisure and Hospitality' at 6.4%, 'Trade, Transportation & Utilities' at 3.6%, 'Professional and Business' at 3.3%, and 'Other Services' at 3.1%. U.S. Bureau of Labor Statistics, 2022.

      Jeff Previte

      Executive Vice-President of IT, CrossCountry Mortgage

      “We have to get to know the individual at a personal level … Not just talking about the business, but getting to know the person."

      Photo of Jeff Previte, Executive Vice-President of IT, CrossCountry Mortgage.

      Listen to the Tech Insights podcast:
      How a financial services company dodged ‘The Great Resignation’

      Internal interpretation: CrossCountry Mortgage

      • May 2019
        Jeff Previte joins Cleveland, Ohio-based CrossCountry Mortgage in the CIO role. The company faces a challenge with employee turnover, particularly in IT. The firm is a sales-focused organization and saw its turnover rate reach as high as 60%. Yet Previte recognized that IT had some meaningful goals to achieve and would need to attract – and retain – some higher caliber talent. His first objective in his new role was to meet with IT employees and business leadership to set priorities.
      • July 2019
        Previte takes a “people-first” approach to leadership and meets his staff face-to-face to understand their personal situations. He sets to work on defining roles and responsibilities in the organization, spending about a fifth of his time on defining the strategy.
      • June 2020
        Previte assigned his leadership team to McLean & Company’s Design an Impactful Employee Development Program. From there, the team developed a Salesforce tool called the Career Development Workbook. “We had some very passionate developers and admins that wanted to build a home-grown tool,” he says. It turns McLean & Company’s process into a digital tool employees can use to reflect on their careers and explore their next steps. It helps facilitate development conversations with managers.
      • January 2021
        CrossCountry Mortgage changes its approach to career development activities. Going to external conferences and training courses is reduced to just 30% of that effort. The rest is by doing hands-on work at the company. Previte aligned with his executives and road-mapped IT projects annually. Based on employee’s interests, opportunities are found to carve out time from usual day-to-day activities to spend time on a project in a new area. When there’s a business need, someone internally can be ready to transition roles.
      • June 2021
        In the two years since joining the company, Previte has reduced the turnover rate to just 12%. The IT department has grown to more adequately meet the needs of the business and employees are engaged with more opportunities to develop their careers. Instead of focusing on compensation, Previte focused more on engaging employees with a developmentally dedicated environment and continuous hands-on learning.

      “It’s come down to a culture shift. Folks have an idea of where we’re headed as an organization, where we’re headed as an IT team, and how their role contributes to that.” (Jeff Previte, EVP of IT, CrossCountry Mortgage)

      Implications: Organization, Process, Technology

      External

      • Organization – A high priority is being placed on improving IT’s maturity through its talent. Enabling learning and development in IT, enabling departmental innovation, and recruiting are the top three highest priorities according to IT Talent Trends 2022 survey responses.
      • Process – Recruiting is more challenging for industries that operate primarily onsite, according to McLean & Company's 2022 HR Trends Report. They face more challenges attracting applications, more rejected offers, and more candidate ghosting compared to remote-capable industries.
      • Technology – Providing a great employee experience through digital tools is more important as many organizations see a mix of workers in the office and at home. These tools can help connect colleagues, foster professional development, and improve the candidate experience.

      Internal

      • Organization – CrossCountry Mortgage faced a situation where IT employees did not have clarity on their roles and responsibilities. In terms of salary, it wasn’t offering at the high end compared to other employers in Cleveland.
      • Process – To foster a culture of growth and development, CrossCountry Mortgage put in place a performance assessment system that encouraged reflection and goal setting, aided by collaboration with a manager.
      • Technology – The high turnover rate was limiting CrossCountry Mortgage from achieving the level of maturity it needed to support the company’s goals. It ingrained its new PA process with a custom build of a Salesforce tool.

      Resources Applied

      Show me the money

      Almost six in ten Talent Trends survey respondents identified salary and compensation as the reason that employees resigned in the past year. Organizations looking to engage employees must first pay a fair salary according to market and industry conditions.

      Build me up

      Professional development and opportunity for innovative work are the next two most common reasons for resignations. Organizations must ensure they create enough capacity to allow workers time to spend on development.

      “Building our own solution created an element of engagement. There was a sense of ownership that the team had in thinking through this.” (Jeff Previte, CrossCountry Mortgage)

      CrossCountry Mortgage

      • Executive time: CIO spends 10-20% of his time on activities related to designing the approach.
      • Leveraged memberships with Info-Tech Research Group and McLean & Company to define professional development process.
      • Internal IT develops automated workflow in Salesforce.
      • Hired additional IT staff to build out overall capacity and create time for development activities.

      Outcomes at CrossCountry Mortgage

      Engaged IT workforce

      The Great Maturation: IT staff turnover rate dropped to 10-12% and IT talent is developing on the job to improve the department’s overall skill level. More IT staff on hand and more engaged workers mean IT can deliver higher maturity level results.

      Alignment achieved: Connecting IT’s initiatives to the vision of the C-suite creates a clear purpose for IT in its initiatives. Staff understand what they need to achieve to progress their careers and can grow while they work.

      Photo of employees from CrossCountry Mortgage assisting with a distribution event.
      Employees from CrossCountry Mortgage headquarters assist with a drive-thru distribution event for the Cleveland Food Bank on Dec. 17, 2021. (Image courtesy of CrossCountry Mortgage.)

      From Priorities to Action

      Staff retention is a leadership priority

      The Great Resignation trend is bringing attention to employee engagement and staff retention. IT departments are busier than ever during the pandemic as they work overtime to keep up with a remote workforce and new security threats. At the same time, IT talent is among the most coveted on the market.

      CIOs need to develop a people-first approach to improve the employee experience. Beyond compensation, IT workers need clarity in terms of their career paths, a direct connection between their work and the goals of the organization, and time set aside for professional development.

      Info-Tech’s 2021 benchmark for “Leadership, Culture & Values” shows that most organizations rate this capability very highly (9) but see room to improve on their effectiveness (6.9).

      Take the next step

      IT Talent Trends 2022
      See how IT talent trends are shifting through the pandemic and understand how themes like The Great Resignation has impacted IT.

      McLean & Company’s Modernize Performance Management
      Customize the building blocks of performance management to best fit organizational needs to impact individual and organizational performance, productivity, and engagement.

      Redesign Your IT Organizational Structure
      Define future-state work units, roles, and responsibilities that will enable the IT organization to complete the work that needs to be done.

      “Leadership, Culture & Values” gap between importance and effectiveness
      Info-Tech Research Group Management and Governance Diagnostic Benchmark 2021

      A bar chart illustrating the 'Leadership, Culture & Values' gap between importance and effectiveness. The difference is marked as Delta 2.1.

      Design an automation platform

      Priority 04 | APO04 Innovation

      Position yourself to buy or build a platform that will enable new automation opportunities through seamless integration.

      Build it or buy it, but platform integration can yield great benefits

      Necessity is the mother of innovation

      When it’s said that digital transformation accelerated during the pandemic, what’s really meant is that processes that were formerly done manually became automated through software. In responses to the Tech Trends survey, CIOs say digital transformation was more of a focus during the pandemic, and eight in ten CIOs also say they shifted more than 20% of their organization’s processes to digital during the pandemic. Automating tasks through software can be called digitalization.

      Most organizations became more digitalized during the pandemic. But how they pursued it depends on their IT maturity. For digital laggards, partnering with a technology services platform is the path of least resistance. For sophisticated innovators, they can consider building a platform to address the specific needs of their business process. Doing so requires the foundation of an existing “digital factory” or innovation arm where new technologies can be tested, proofs of concept developed, and external partnerships formed. Patience is key with these efforts, as not every investment will yield immediate returns and some will fail outright.

      Build it or buy it, platform participants integrate with their existing systems through application programming interfaces (APIs). Organizations should determine their platform strategies based on maturity, then look to integrate the business processes that will yield the most gains.

      What role should you play in the platform ecosystem?

      A table with levels on the maturity ladder laid out as a sprint. Column headers are maturity levels 'Struggle', 'Support', 'Optimize', 'Expand', and 'Transform', row headers are 'Maturity' and 'Role'. Roles are assigned to one or many levels. 'Improve' is solely under Struggle. 'Integrate' spans from Support to Transform. 'Buy' spans Support to Expand. 'Build' begins midway through Expand and all of Transform. 'Partner' spans from Optimize to halfway through Transform.

      68% of CIOs say digital transformation became much more of a focus for their organization during the pandemic (Info-Tech Tech Trends 2022 Survey)

      Bob Crozier

      Chief Architect, Allianz Technology & Global Head of Blockchain, Allianz Technology SE

      "Smart contracts are really just workflows between counterparties."

      Photo of Bob Crozier, Chief Architect, Allianz Technology & Global Head of Blockchain, Allianz Technology SE.

      Listen to the Tech Insights podcast:
      How Allianz took a blockchain platform from pilot to 1 million transactions

      Internal interpretation: Allianz Technology

      • 2015
        After smart contracts are demonstrated on the Ethereum blockchain, Allianz and other insurers recognize the business value. There is potential to use the capability to administer a complex, multi-party contract where the presence of the reinsurer in the risk transfer ecosystem is required. Manual contracts could be turned into code and automated. Allianz organized an early proof of concept around a theoretical pandemic excessive loss contract.
      • 2018
        Allianz Chief Architect Bob Crozier is leading the Global Blockchain Center of Competence for Allianz. They educate Allianz on the value of blockchain for business. They also partner with a joint venture between the Technology University of Munich and the state of Bavaria. A cohort of Masters students is looking for real business problems to solve with open-source distributed ledger technology. Allianz puts its problem statement in front of the group. A student team presents a proof of concept for an international motor insurance claims settlement and it comes in second place at a pitch day competition.
      • 2019
        Allianz brings the concept back in-house, and its business leaders return to the concept. Startup Luther Systems is engaged to build a minimum-viable product for the solution, with the goal being a pilot involving three or four subsidiaries in different countries. The Blockchain Center begins communicating with 25 Allianz subsidiaries that will eventually deploy the platform.
      • 2020
        Allianz is in build mode on its international motor insurance claims platform. It leverages its internal Dev/SecOps teams based in Munich and in India.
      • May 2021
        Allianz goes live with its new platform on May 17, decommissioning its old system and migrating all live claims data onto the new blockchain platform. It sees 400 concurrent users go live across Europe.
      • January 2022
        Allianz mines its one-millionth block to its ledger on Jan. 19, with each block representing a peer-to-peer transaction across its 25 subsidiaries in different countries. The platform has settled hundreds of millions of dollars.

      Stock photo of two people arguing over a car crash.

      Implications: Organization, Process, Technology

      External

      • Organization – To explore emerging technologies like blockchain, organizations need staff that are accountable for innovation and have leeway to develop proofs of concept. External partners are often required to bring in fresh ideas and move quickly towards an MVP.
      • Process – According to the Tech Trends 2022 survey, 84% of CIOs consider automation a high-value digital capability, and 77% say identity verification is a high-value capability. A blockchain platform using smart contracts can deliver those.
      • Technology – The Linux Foundation’s Hyperledger Fabric is an open-source blockchain technology that’s become popular in the financial industry for its method of forming consensus and its modular architecture. It’s been adopted by USAA, MasterCard, and PayPal. It also underpins the IBM Blockchain Platform and is supported by Azure Blockchain.

      Internal

      • Organization – Allianz is a holding company that owns Allianz Technology and 25 operating entities across Europe. It uses the technology arm to innovate on the business process and creates shared platforms that its entities can integrate with to automate across the value chain.
      • Process – Initial interest in smart contracts on blockchain were funneled into a student competition, where a proof of concept was developed. Allianz partnered with a startup to develop an MVP, then developed the platform while aligning with its business units ahead of launch.
      • Technology – Allianz built its blockchain platform on Hyperledger Fabric because it was a permissioned system, unlike other public permissionless blockchains such as Ethereum, and because its mining mechanism was much more energy efficient compared to other blockchains using Proof of Work consensus models.

      Resources Applied

      Time to innovate

      Exploring emerging technology for potential use cases is difficult for staff tasked with running day-to-day operations. Organizations serious about innovation create a separate team that can focus on “moonshot” projects and connect with external partners.

      Long-term ROI

      Automation of new business processes often requires a high upfront initial investment for a long-term efficiency gain. A proof of concept should demonstrate clear business value that can be repeated often and for a long period.

      “My next project has to deliver in the tens of millions of value in return. The bar is high and that’s what it should be for a business of our size.” (Bob Crozier, Allianz)

      Allianz

      • Several operating entities from different countries supplied subject matter expertise and helped with the testing process.
      • Allianz Technology team has eight staff members. It is augmented by Luther Systems and the team at industry group B3i.
      • Funding of less than $5 million to develop. Dev team continues to add improvements.
      • Operating requires just one full-time employee plus infrastructure costs, mostly for public cloud hosting.

      Outcomes at Allianz

      From insurer to platform provider

      Deliver your own SaaS: Allianz Technology built its blockchain-based claims settlement platform and its subsidiaries consume it as software as a service. The platform runs on a distributed architecture across Europe, with each node running the same version of the software. Operating entities can also integrate their own systems to the platform via APIs and further automate business processes such as billing.

      Ready to scale: After processing one million transactions, the international claims settlement platform is proven and ready to add more participants. Crozier sees auto repair shops and auto manufacturers as the next logical users.

      Stock photo of Blockchain.
      Allianz is a shareholder of the Blockchain Insurance Industry Initiative (B3i). It is providing a platform used by a group of insurance companies in the commercial and reinsurance space.

      When should we use blockchain? THREE key criteria:

      • Redundant processes
        Different entities follow the same process to achieve the desired outcome.
      • Audit trail
        Accountability in the decision making must be documented.
      • Reconciliation
        Parties need to be able to resolve disputes by tracing back to the truth.

      From Priorities to Action

      It’s a build vs. buy question for platforms

      Allianz was able to build a platform for its group of European subsidiaries because of its established digital factory and commitment to innovation. Allianz Technology is at the “innovate” level of IT maturity, allowing it to create a platform that subsidiaries can integrate with via APIs. For firms that are lower on the IT maturity scale, buying a platform solution is the better path to automation. These firms will be concerned with integrating their legacy systems to platforms that can reduce the friction of their operating environments and introduce modern new capabilities.

      From Info-Tech’s Build a Winning Business Process Automation Playbook

      An infographic comparing pros and cons of Build versus Buy. On the 'Build: High Delivery Capacity & Capability' side is 'Custom Development', 'Data Integration', 'AI/ML', 'Configuration', 'Native Workflow', and 'Low & No Code'. On the 'Buy: Low Delivery Capacity & Capability' side is 'Outsource Development', 'iPaaS', 'Chatbots', 'iBPMS & Rules Engines', 'RPA', and 'Point Solutions'.

      Take the next step

      Accelerate Your Automation Processes
      Integrate automation solutions and take the first steps to building an automation suite.

      Build Effective Enterprise Integration on the Back of Business Process
      From the backend to the frontlines – let enterprise integration help your business processes fly.

      Evolve Your Business Through 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.

      “Innovation” gap between importance and effectiveness Info-Tech Research Group Management and Governance Diagnostic Benchmark 2021

      A bar chart illustrating the 'Innovation' gap between importance and effectiveness. The difference is marked as Delta 2.1.

      Prepare to report on new environmental, social, and governance (ESG) metrics

      Priority 05 | ITRG06 Business Intelligence and Reporting

      Be ready to either lead or support initiatives to meet the criteria of new ESG reporting mandates and work toward disclosure reporting solutions.

      Time to get serious about ESG

      What does CSR or ESG mean to a CIO?

      Humans are putting increasing pressure on the planet’s natural environment and creating catastrophic risks as a result. Efforts to mitigate these risks have been underway for the past 30 years, but in the decade ahead regulators are likely to impose more strict requirements that will be linked to the financial value of an organization. Various voluntary frameworks exist for reporting on environmental, social, and governance (ESG) or corporate social responsibility (CSR) metrics. But now there are efforts underway to unify and clarify those standards.

      The most advanced effort toward a global set of standards is in the environmental area. At the United Nations’ COP26 summit in Scotland last November, the International Sustainability Standards Board (ISSB) announced its headquarters (Frankfurt) and three other international office locations (Montreal, San Francisco, and London) and its roadmap for public consultations. It is working with an array of voluntary standards groups toward a consensus.

      In Info-Tech’s 2022 Tech Trends survey, two-thirds of CIOs say their organization is committed to reducing greenhouse gas emissions, yet only 40% say their organizational leadership is very concerned with reducing those emissions. CIOs will need to consider how to align organizational concern with internal commitments and new regulatory pressures. They may investigate new real-time reporting solutions that could serve as a competitive differentiator on ESG.

      Standards informing the ISSB’s global set of climate standards

      A row of logos of organizations that inform ISSB's global set of climate standards.

      67% of CIOs say their organization is committed to reducing greenhouse gases, with one-third saying that commitment is public. (Info-Tech Tech Trends 2022 Survey)

      40% of CIOs say their organizational leadership is very concerned with reducing greenhouse gas emissions.

      David W. Dorman

      Chairman of the board, CVS Health

      “ESG is a question of what you do in the microcosm of your company to make sure there is a clear, level playing field – that there is a color-blind, gender-blind meritocracy available – that you are aware that not in every case can you achieve that without really focusing on it. It’s not going to happen on its own. That’s why our commitments have real dollars behind them and real focus behind them because we want to be the very best at doing them.”

      Photo of David W. Dorman, Chairman of the Board, CVS Health.

      Listen to the Tech Insights podcast:
      CVS Health chairman David Dorman on healthcare's hybrid future

      Internal interpretation: CVS Health

      CVS Health established a new steering committee of senior leaders in 2020 to oversee ESG commitments. It designs its corporate social responsibility strategy, Transform Health 2030, by aligning company activities in four key areas: healthy people, healthy business, healthy planet, and healthy community. The strategy aligns with the United Nations’ Sustainable Development Goals. In alignment with these goals, CVS identifies material topics where the company has the most ability to make an impact. In 2020, its top three topics were:

      1. Access to quality health care
      2. Patient and customer safety
      3. Data protection and privacy
      Material Topic
      Access to quality health care
      Material Topic
      Patient and customer safety
      Material Topic
      Data protection and privacy
      Technology Initiative
      MinuteClinic’s Virtual Collaboration for Nurses

      CVS provided Apple iPads compliant with the Health Insurance Portability and Accountability Act (HIPAA) to clinics in a phased approach, providing training to more than 700 providers in 26 states by February 2021. Nurses could use the iPads to attend virtual morning huddles and access clinical education. Nurses could connect virtually with other healthcare experts to collaborate on delivering patient care in real-time. The project was able to scale across the country through a $50,000 American Nurses Credentialing Center Pathway Award. (Wolters Kluwer Health, Inc.)

      Technology Initiative
      MinuteClinic’s E-Clinic

      MinuteClinics launched this telehealth solution in response to the pandemic, rolling it out in three weeks. The solution complemented video visits delivered in partnership with the Teladoc platform. Visits cost $59 and are covered by Aetna insurance plans, a subsidiary of CVS Health. It hosted more than 20,000 E-Clinic visits through the end of 2020. CVS connected its HealthHUBs to the solution to increase capacity in place of walk-in appointments and managed patients via phone for medication adherence and care plans. CVS also helped behavioral health providers transition patients to virtual visits. (CVS Health)

      Technology Initiative
      Next Generation Authentication Platform

      CVS patented this solution to authenticate customers accessing digital channels. It makes use of the available biometrics data and contextual information to validate identity without the need for a password. CVS planned to extend the platform to voice channels as well, using voiceprint technology. The solution prevents unauthorized access to sensitive health data while providing seamless access for customers. (LinkedIn)

      Implications: Organization, Process, Technology

      External

      • Organization – Since the mid-2010s, younger investors have demonstrated reliance on ESG data when making investment decisions, resulting in the creation of voluntary standards that offered varied approaches. Organizations in ESG exchange-traded funds are outperforming the overall S&P 500 (S&P Global Market Intelligence).
      • Process – Organizations are issuing ESG reports today despite the absence of clear rules to follow for reporting results. With regulators expected to step in to establish more rigid guidelines, many organizations will need to revisit their approach to ESG reports.
      • Technology – Real-time reporting of ESG metrics will become a competitive advantage before 2030. Engineering a solution that can alert organizations to poor performance on ESG measures and allow them to respond could avert losing market value.

      Internal

      • Organization – CVS Health established an ESG Steering Committee in 2020 composed of senior leaders including its chief governance officers, chief sustainability officer, chief risk officer, and controller and SVP of investor relations. It is supported by the ESG Operating Committee.
      • Process – CVS conducts a materiality assessment in accordance with Global Reporting Initiative standards to determine the most significant ESG impacts it can make and what topics most influence the decisions of stakeholders. It engages with various stakeholder groups on CSR topics.
      • Technology – CVS technology initiatives during the pandemic focused on supporting patients and employees in collaborating on health care delivery using virtual solutions, providing rich digital experiences that are easily accessible while upholding high security and privacy standards.

      Resources Applied

      Lack of commitment

      While 83% of businesses state support for the Sustainable Development Goals outlined by the Global Reporting Initiative (GRI), only 40% make measurable commitments to their goals.

      Show your work

      The GRI recommends organizations not only align their activities with sustainable development goals but also demonstrate contributions to specific targets in reporting on the positive actions they carry out. (GRI, “State of Progress: Business Contributions to the SDGS.”)

      “We end up with a longstanding commitment to diversity because that’s what our customer base looks like.” (David Dorman, CVS Health)

      CVS Health

      • The MinuteClinic Virtual Collaboration solution was piloted in Houston, demonstrated success, and won additional $50,000 funding from the Pathway to Excellence Award to scale the program across the country (Wolters Kluwer Health, Inc.).
      • The Next-Gen Authentication solution is provided by the vendor HYPR. It is deployed to ten million users and looking to scale to 30 million more. Pricing for enterprises is quoted at $1 per user, but volume pricing would apply to CVS (HYPR).

      Outcomes at CVS Health

      Delivering on hybrid healthcare solutions

      iPads for collaboration: Healthcare practitioners in the MinuteClinic Virtual Collaboration initiative agreed that it improved the use of interprofessional teams, working well virtually with others, and improved access to professional resources (Wolters Kluwer Health, Inc.)

      Remote healthcare: Saw a 400% increase in MinuteClinic virtual visits in 2020 (CVS Health).

      Verified ID: The Next Generation Authentication platform allowed customers to register for a COVID-19 vaccination appointment. CVS has delivered more than 50 million vaccines (LinkedIn).

      Stock photo of a doctor with an iPad.
      CVS Health is making use of digital channels to connect its customers and health practitioners to a services platform that can supplement visits to a retail or clinic location to receive diagnostics and first-hand care.

      From Priorities to Action

      Become your organization’s ESG Expert

      The risks posed to organizations and wider society are becoming more severe, driving a transition from voluntary frameworks for ESG goals to a mandatory one that’s enforced by investors and governments. Organizations will be expected to tie their core activities to a defined set of ESG goals and maintain a balance sheet of their positive and negative impacts. CIOs should become experts in ESG disclosure requirements and recommend the steps needed to meet or exceed competitors’ efforts. If a leadership vacuum for ESG accountability exists, CIOs can either seek to support their peers that are likely to become accountable or take a leadership role in overseeing the area. CIOs should start working toward solutions that deliver real-time reporting on ESG goals to make reporting frictionless.

      “If you don’t have ESG oversight at the highest levels of the company, it won’t wind up getting the focus. That’s why we review it at the Board multiple times per year. We have an annual report, we compare how we did, what we intended to do, where did we fall short, where did we exceed, and where we can run for daylight to do more.” (David Dorman, CVS Health)

      Take the next step

      ESG Disclosures: How Will We Record Status Updates on the World We Are Creating?
      Prepare for the era of mandated environmental, social, and governance disclosures.

      Private Equity and Venture Capital Growing Impact of ESG Report
      Learn about how the growing impact of ESG affects both your organization and IT specifically, including challenges and opportunities, with expert assistance.

      “Business Intelligence and Reporting” gap between importance and effectiveness
      Info-Tech Research Group Management and Governance Diagnostic Benchmark 2021

      A bar chart illustrating the 'BI and Reporting' gap between importance and effectiveness. The difference is marked as Delta 2.4.

      The Five Priorities

      Priorities to compete in the digital economy

      1. Reduce Friction in the Hybrid Operating Model
      2. Improve Your Ransomware Readiness
      3. Support an Employee-Centric Retention Strategy
      4. Design an Automation Platform
      5. Prepare to Report on New Environmental, Social, and Governance Metrics

      Contributing Experts

      Elizabeth Clark

      CIO, Harvard Business School
      Photo of Elizabeth Clark, CIO, Harvard Business School.

      Jeff Previte

      Executive Vice-President of IT, CrossCountry Mortgage
      Photo of Jeff Previte, Executive Vice-President of IT, CrossCountry Mortgage.

      Bob Crozier

      Chief Architect, Allianz Technology & Global Head of Blockchain, Allianz Technology SE
      Photo of Bob Crozier, Chief Architect, Allianz Technology & Global Head of Blockchain, Allianz Technology SE.

      David W. Dorman

      Chairman of the Board, CVS Health
      Photo of David W. Dorman, Chairman of the Board, CVS Health.

      Info-Tech’s internal CIO panel contributors

      • Bryan Tutor
      • John Kemp
      • Mike Schembri
      • Janice Clatterbuck
      • Sandy Silk
      • Sallie Wright
      • David Wallace
      • Ken McGee
      • Mike Tweedie
      • Cole Cioran
      • Kevin Tucker
      • Angelina Atkins
      • Yakov Kofner
      Photo of an internal CIO panel contributor. Photo of an internal CIO panel contributor.Photo of an internal CIO panel contributor.
      Photo of an internal CIO panel contributor.Photo of an internal CIO panel contributor.Photo of an internal CIO panel contributor.Photo of an internal CIO panel contributor.
      Photo of an internal CIO panel contributor.Photo of an internal CIO panel contributor.Photo of an internal CIO panel contributor.

      Thank you for your support

      Logo for the Blockchain Research Institute.
      Blockchain Research Institute

      Bibliography – CIO Priorities 2022

      “2020 Corporate Social Responsibility Report.” CVS Health, 2020, p. 127. Web.

      “Adversary: Doppel Spider - Threat Actor.” Crowdstrike Adversary Universe, 2021. Accessed 29 Dec. 2021.

      “Aetna CVS Health Success Story.” HYPR, n.d. Accessed 6 Feb. 2022.

      Baig, Aamer. “The CIO agenda for the next 12 months: Six make-or-break priorities.” McKinsey Digital, 1 Nov. 2021. Web.

      Ball, Sarah, Kristene Diggins, Nairobi Martindale, Angela Patterson, Anne M. Pohnert, Jacinta Thomas, Tammy Todd, and Melissa Bates. “2020 ANCC Pathway Award® winner.” Wolters Kluwer Health, Inc., 2021. Accessed 6 Feb. 2022.

      “Canadian Universities Propose Designs for a Central Bank Digital Currency.” Bank of Canada, 11 Feb. 2021. Accessed 14 Dec. 2021.

      “Carbon Sequestration in Wetlands.” MN Board of Water and Soil Resources, n.d. Accessed 15 Nov. 2021.

      “CCM Honored as a NorthCoast 99 Award Winner.” CrossCountry Mortgage, 1 Dec. 2021. Web.

      Cheek, Catherine. “Four Things We Learned About the Resignation Wave–and What to Do Next.” Visier Inc. (blog), 5 Oct. 2021. Web.

      “Companies Using Hyperledger Fabric, Market Share, Customers and Competitors.” HG Insights, 2022. Accessed 25 Jan. 2022.

      “IFRS Foundation Announces International Sustainability Standards Board, Consolidation with CDSB and VRF, and Publication of Prototype Disclosure Requirements.” IFRS, 3 Nov. 2021. Web.

      “IT Priorities for 2022: A CIO Report.” Mindsight, 28 Oct. 2021. Web.

      “Job Openings and Labor Turnover Survey.” Databases, Tables & Calculators by Subject, U.S. Bureau of Labor Statistics, 2022. Accessed 9 Feb. 2022.

      Kumar, Rashmi, and Michael Krigsman. “CIO Planning and Investment Strategy 2022.” CXOTalk, 13 Sept. 2021. Web.

      Leonhardt, Megan. “The Great Resignation Is Hitting These Industries Hardest.” Fortune, 16 Nov. 2021. Accessed 7 Jan. 2022.

      “Most companies align with SDGs – but more to do on assessing progress.” Global Reporting Initiative (GRI), 17 Jan. 2022. Web.

      Navagamuwa, Roshan. “Beyond Passwords: Enhancing Data Protection and Consumer Experience.” LinkedIn, 15 Dec. 2020.

      Ojo, Oluwaseyi. “Achieving Digital Business Transformation Using COBIT 2019.” ISACA, 19 Aug. 2019. Web.

      “Priority.” Lexico.com, Oxford University Press, 2021. Web.

      Riebold, Jan, and Yannick Bartens. “Reinventing the Digital IT Operating Model for the ‘New Normal.’” Capgemini Worldwide, 3 Nov. 2020. Web.

      Samuels, Mark. “The CIO’s next priority: Using the tech budget for growth.” ZDNet, 1 Sept. 2021. Accessed 1 Nov. 2021.

      Sayer, Peter. “Exclusive Survey: CIOs Outline Tech Priorities for 2021-22.” CIO, 5 Oct. 2021. Web.

      Shacklett, Mary E. “Where IT Leaders Are Likely to Spend Budget in 2022.” InformationWeek, 10 Aug. 2021. Web.

      “Table 4. Quits Levels and Rates by Industry and Region, Seasonally Adjusted - 2021 M11 Results.” U.S. Bureau of Labor Statistics, Economic News Release, 1 Jan. 2022. Accessed 7 Jan. 2022.

      “Technology Priorities CIOs Must Address in 2022.” Gartner, 19 Oct. 2021. Accessed 1 Nov. 2021.

      Thomson, Joel. Technology, Talent, and the Future Workplace: Canadian CIO Outlook 2021. The Conference Board of Canada, 7 Dec. 2021. Web.

      “Trend.” Lexico.com, Oxford University Press, 2021. Web.

      Vellante, Dave. “CIOs signal hybrid work will power tech spending through 2022.” SiliconANGLE, 25 Sept. 2021. Web.

      Whieldon, Esther, and Robert Clark. “ESG funds beat out S&P 500 in 1st year of COVID-19; how 1 fund shot to the top.” S&P Global Market Intelligence, April 2021. Accessed Dec. 2021.

      Create a Right-Sized Disaster Recovery Plan

      • Buy Link or Shortcode: {j2store}410|cart{/j2store}
      • member rating overall impact: 9.6/10 Overall Impact
      • member rating average dollars saved: $83,037 Average $ Saved
      • member rating average days saved: 32 Average Days Saved
      • Parent Category Name: DR and Business Continuity
      • Parent Category Link: /business-continuity
      • Any time a natural disaster or major IT outage occurs, it increases executive awareness and internal pressure to create a disaster recovery plan (DRP).
      • Traditional DRP templates are onerous and result in a lengthy, dense plan that might satisfy auditors but will not be effective in a crisis.
      • The myth that a DRP is only for major disasters leaves organizations vulnerable to more common incidents.
      • The growing use of outsourced infrastructure services has increased reliance on vendors to meet recovery timeline objectives.

      Our Advice

      Critical Insight

      • At its core, disaster recovery (DR) is about ensuring service continuity. Create a plan that can be leveraged for both isolated and catastrophic events.
      • Remember Murphy’s Law. Failure happens. Focus on improving overall resiliency and recovery, rather than basing DR on risk probability analysis.
      • Cost-effective DR and service continuity starts with identifying what is truly mission critical so you can focus resources accordingly. Not all services require fast failover.

      Impact and Result

      • Define appropriate objectives for service downtime and data loss based on business impact.
      • Document an incident response plan that captures all of the steps from event detection to data center recovery.
      • Create a DR roadmap to close gaps between current DR capabilities and recovery objectives.

      Create a Right-Sized Disaster Recovery Plan Research & Tools

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

      1. Disaster Recovery Plan (DRP) Research – A step-by-step document that helps streamline your DR planning process and build a plan that's concise, usable, and maintainable.

      Any time a major IT outage occurs, it increases executive awareness and internal pressure to create an IT DRP. This blueprint will help you develop an actionable DRP by following our four-phase methodology to define scope, current status, and dependencies; conduct a business impact analysis; identify and address gaps in the recovery workflow; and complete, extend, and maintain your DRP.

      • Create a Right-Sized Disaster Recovery Plan – Phases 1-4

      2. DRP Case Studies – Examples to help you understand the governance and incident response components of a DRP and to show that your DRP project does not need to be as onerous as imagined.

      These examples include a client who leveraged the DRP blueprint to create practical, concise, and easy-to-maintain DRP governance and incident response plans and a case study based on a hospital providing a wide range of healthcare services.

      • Case Study: Practical, Right-Sized DRP
      • Case Study: Practical, Right-Sized DRP – Healthcare Example

      3. DRP Maturity Scorecard – An assessment tool to evaluate the current state of your DRP.

      Use this tool to measure your current DRP maturity and identify gaps to address. It includes a comprehensive list of requirements for your DRP program, including core and industry requirements.

      • DRP Maturity Scorecard

      4. DRP Project Charter Template – A template to communicate important details on the project purpose, scope, and parameters.

      The project charter template includes details on the project overview (description, background, drivers, and objectives); governance and management (project stakeholders/roles, budget, and dependencies); and risks, assumptions, and constraints (known and potential risks and mitigation strategy).

      • DRP Project Charter Template

      5. DRP Business Impact Analysis Tool – An evaluation tool to estimate the impact of downtime to determine appropriate, acceptable recovery time objectives (RTOs) and recovery point objectives (RPOs) and to review gaps between objectives and actuals.

      This tool enables you to identify critical applications/systems; identify dependencies; define objective scoring criteria to evaluate the impact of application/system downtime; determine the impact of downtime and establish criticality tiers; set recovery objectives (RTO/RPO) based on the impact of downtime; record recovery actuals (RTA/RPA) and identify any gaps between objectives and actuals; and identify dependencies that regularly fail (and have a significant impact when they fail) to prioritize efforts to improve resiliency.

      • DRP Business Impact Analysis Tool
      • Legacy DRP Business Impact Analysis Tool

      6. DRP BIA Scoring Context Example – A tool to record assumptions you made in the DRP Business Impact Analysis Tool to explain the results and drive business engagement and feedback.

      Use this tool to specifically record assumptions made about who and what are impacted by system downtime and record assumptions made about impact severity.

      • DRP BIA Scoring Context Example

      7. DRP Recovery Workflow Template – A flowchart template to provide an at-a-glance view of the recovery workflow.

      This simple format is ideal during crisis situations, easier to maintain, and often quicker to create. Use this template to document the Notify - Assess - Declare disaster workflow, document current and planned future state recovery workflows, including gaps and risks, and review an example recovery workflow.

      • DRP Recovery Workflow Template (PDF)
      • DRP Recovery Workflow Template (Visio)

      8. DRP Roadmap Tool – A visual roadmapping tool that will help you plan, communicate, and track progress for your DRP initiatives.

      Improving DR capabilities is a marathon, not a sprint. You likely can't fund and resource all the measures for risk mitigation at once. Instead, use this tool to create a roadmap for actions, tasks, projects, and initiatives to complete in the short, medium, and long term. Prioritize high-benefit, low-cost mitigations.

      • DRP Roadmap Tool

      9. DRP Recap and Results Template – A template to summarize and present key findings from your DR planning exercises and documents.

      Use this template to present your results from the DRP Maturity Scorecard, BCP-DRP Fitness Assessment, DRP Business Impact Analysis Tool, tabletop planning exercises, DRP Recovery Workflow Template, and DRP Roadmap Tool.

      • DRP Recap and Results Template

      10. DRP Workbook – A comprehensive tool that enables you to organize information to support DR planning.

      Leverage this tool to document information regarding DRP resources (list the documents/information sources that support DR planning and where they are located) and DR teams and contacts (list the DR teams, SMEs critical to DR, and key contacts, including business continuity management team leads that would be involved in declaring a disaster and coordinating response at an organizational level).

      • DRP Workbook

      11. Appendix

      The following tools and templates are also included as part of this blueprint to use as needed to supplement the core steps above:

      • DRP Incident Response Management Tool
      • DRP Vendor Evaluation Questionnaire
      • DRP Vendor Evaluation Tool
      • Severity Definitions and Escalation Rules Template
      • BCP-DRP Fitness Assessment
      [infographic]

      Workshop: Create a Right-Sized Disaster Recovery Plan

      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 Parameters for Your DRP

      The Purpose

      Identify key applications and dependencies based on business needs.

      Key Benefits Achieved

      Understand the entire IT “footprint” that needs to be recovered for key applications. 

      Activities

      1.1 Assess current DR maturity.

      1.2 Determine critical business operations.

      1.3 Identify key applications and dependencies.

      Outputs

      Current challenges identified through a DRP Maturity Scorecard.

      Key applications and dependencies documented in the Business Impact Analysis (BIA) Tool.

      2 Determine the Desired Recovery Timeline

      The Purpose

      Quantify application criticality based on business impact.

      Key Benefits Achieved

      Appropriate recovery time and recovery point objectives defined (RTOs/RPOs).

      Activities

      2.1 Define an objective scoring scale to indicate different levels of impact.

      2.2 Estimate the impact of downtime.

      2.3 Determine desired RTO/RPO targets for applications based on business impact.

      Outputs

      Business impact analysis scoring criteria defined.

      Application criticality validated.

      RTOs/RPOs defined for applications and dependencies.

      3 Determine the Current Recovery Timeline and DR Gaps

      The Purpose

      Determine your baseline DR capabilities (your current state).

      Key Benefits Achieved

      Gaps between current and desired DR capability are quantified.

      Activities

      3.1 Conduct a tabletop exercise to determine current recovery procedures.

      3.2 Identify gaps between current and desired capabilities.

      3.3 Estimate likelihood and impact of failure of individual dependencies.

      Outputs

      Current achievable recovery timeline defined (i.e. the current state).

      RTO/RPO gaps identified.

      Critical single points of failure identified.

      4 Create a Project Roadmap to Close DR Gaps

      The Purpose

      Identify and prioritize projects to close DR gaps.

      Key Benefits Achieved

      DRP project roadmap defined that will reduce downtime and data loss to acceptable levels.

      Activities

      4.1 Determine what projects are required to close the gap between current and desired DR capability.

      4.2 Prioritize projects based on cost, effort, and impact on RTO/RPO reduction.

      4.3 Validate that the suggested projects will achieve the desired DR capability.

      Outputs

      Potential DR projects identified.

      DRP project roadmap defined.

      Desired-state incident response plan defined, and project roadmap validated.

      5 Establish a Framework for Documenting Your DRP, and Summarize Next Steps

      The Purpose

      Outline how to create concise, usable DRP documentation.

      Summarize workshop results. 

      Key Benefits Achieved

      A realistic and practical approach to documenting your DRP.

      Next steps documented. 

      Activities

      5.1 Outline a strategy for using flowcharts and checklists to create concise, usable documentation.

      5.2 Review Info-Tech’s DRP templates for creating system recovery procedures and a DRP summary document.

      5.3 Summarize the workshop results, including current potential downtime and action items to close gaps.

      Outputs

      Current-state and desired-state incident response plan flowcharts.

      Templates to create more detailed documentation where necessary.

      Executive communication deck that outlines current DR gaps, how to close those gaps, and recommended next steps.

      Further reading

      Create a Right-Sized Disaster Recovery Plan

      Close the gap between your DR capabilities and service continuity requirements.

      ANALYST PERSPECTIVE

      An effective disaster recovery plan (DRP) is not just an insurance policy.

      "An effective DRP addresses common outages such as hardware and software failures, as well as regional events, to provide day-to-day service continuity. It’s not just insurance you might never cash in. Customers are also demanding evidence of an effective DRP, so organizations without a DRP risk business impact not only from extended outages but also from lost sales. If you are fortunate enough to have executive buy-in, whether it’s due to customer pressure or concern over potential downtime, you still have the challenge of limited time to dedicate to disaster recovery (DR) planning. Organizations need a practical but structured approach that enables IT leaders to create a DRP without it becoming their full-time job."

      Frank Trovato,

      Research Director, Infrastructure

      Info-Tech Research Group

      Is this research for you?

      This Research Is Designed For:

      • Senior IT management responsible for executing DR.
      • Organizations seeking to formalize, optimize, or validate an existing DRP.
      • Business continuity management (BCM) professionals leading DRP development.

      This Research Will Help You:

      • Create a DRP that is aligned with business requirements.
      • Prioritize technology enhancements based on DR requirements and risk-impact analysis.
      • Identify and address process and technology gaps that impact DR capabilities and day-to-day service continuity.

      This Research Will Also Assist:

      • Executives who want to understand the time and resource commitment required for DRP.
      • Members of BCM and crisis management teams who need to understand the key elements of an IT DRP.

      This Research Will Help Them:

      • Scope the time and effort required to develop a DRP.
      • Align business continuity, DR, and crisis management plans.

      Executive summary

      Situation

      • Any time a natural disaster or major IT outage occurs, it increases executive awareness and internal pressure to create a DRP.
      • Industry standards and government regulations are driving external pressure to develop business continuity and IT DR plans.
      • Customers are asking suppliers and partners to provide evidence that they have a workable DRP before agreeing to do business.

      Complication

      • Traditional DRP templates are onerous and result in a lengthy, dense plan that might satisfy auditors, but will not be effective in a crisis.
      • The myth that a DRP is only for major disasters leaves organizations vulnerable to more common incidents.
      • The growing use of outsourced infrastructure services has increased reliance on vendors to meet recovery timeline objectives.

      Resolution

      • Create an effective DRP by following a structured process to discover current capabilities and define business requirements for continuity:
        • Define appropriate objectives for service downtime and data loss based on business impact.
        • Document an incident response plan that captures all of the steps from event detection to data center recovery.
        • Create a DR roadmap to close gaps between current DR capabilities and recovery objectives.

      Info-Tech Insight

      1. At its core, DR is about ensuring service continuity. Create a plan that can be leveraged for both isolated and catastrophic events.
      2. Remember Murphy’s Law. Failure happens. Focus on improving overall resiliency and recovery, rather than basing DR on risk probability analysis.
      3. Cost-effective DR and service continuity starts with identifying what is truly mission critical so you can focus resources accordingly. Not all services require fast failover.

      An effective DRP is critical to reducing the cost of downtime

      If you don’t have an effective DRP when failure occurs, expect to face extended downtime and exponentially rising costs due to confusion and lack of documented processes.

      Image displayed is a graph that shows that delay in recovery causes exponential revenue loss.

      Potential Lost Revenue

      The impact of downtime tends to increase exponentially as systems remain unavailable (graph at left). A current, tested DRP will significantly improve your ability to execute systems recovery, minimizing downtime and business impact. Without a DRP, IT is gambling on its ability to define and implement a recovery strategy during a time of crisis. At the very least, this means extended downtime – potentially weeks or months – and substantial business impact.

      Adapted from: Philip Jan Rothstein, 2007

      Cost of Downtime for the Fortune 1000

      Cost of unplanned apps downtime per year: $1.25B to $2.5B.

      Cost of critical apps failure per hour: $500,000 to $1M.

      Cost of infrastructure failure per hour: $100,000.

      35% reported to have recovered within 12 hours.

      17% of infrastructure failures took more than 24 hours to recover.

      13% of application failures took more than 24 hours to recover.

      Source: Stephen Elliot, 2015

      Info-Tech Insight

      The cost of downtime is rising across the board, and not just for organizations that traditionally depend on IT (e.g. e-commerce). Downtime cost increase since 2010:

      Hospitality: 129% increase

      Transportation: 108% increase

      Media organizations: 104% increase

      An effective DRP also sets clear recovery objectives that align with system criticality to optimize spend

      The image displays a disaster recovery plan example, where different tiers are in place to support recovery in relation to time.

      Take a practical approach that creates a more concise and actionable DRP

      DR planning is not your full-time job, so it can’t be a resource- and time-intensive process.

      The Traditional Approach Info-Tech’s Approach

      Start with extensive risk and probability analysis.

      Challenge: You can’t predict every event that can occur, and this delays work on your actual recovery procedures.

      Focus on how to recover regardless of the incident.

      We know failure will happen. Focus on improving your ability to failover to a DR environment so you are protected regardless of what causes primary site failure.

      Build a plan for major events such as natural disasters.

      Challenge: Major destructive events only account for 12% of incidents while software/hardware issues account for 45%. The vast majority of incidents are isolated local events.

      An effective DRP improves day-to-day service continuity, and is not just for major events.

      Leverage DR planning to address both common (e.g. power/network outage or hardware failure) as well as major events. It must be documentation you can use, not shelfware.

      Create a DRP manual that provides step-by-step instructions that anyone could follow.

      Challenge: The result is lengthy, dense manuals that are difficult to maintain and hard to use in a crisis. The usability of DR documents has a direct impact on DR success.

      Create concise documentation written for technical experts.

      Use flowcharts, checklists, and diagrams. They are more usable in a crisis and easier to maintain. You aren’t going to ask a business user to recover your SQL Server databases, so you can afford to be concise.

      DR must be integrated with day-to-day incident management to ensure service continuity

      When a tornado takes out your data center, it’s an obvious DR scenario and the escalation towards declaring a disaster is straightforward.

      The challenge is to be just as decisive in less-obvious (and more common) DR scenarios such as a critical system hardware/software failure, and knowing when to move from incident management to DR. Don’t get stuck troubleshooting for days when you could have failed over in hours.

      Bridge the gap with clearly-defined escalation rules and criteria for when to treat an incident as a disaster.

      Image displays two graphs. The graph on the left measures the extent that service management processes account for disasters by the success meeting RTO and RPO. The graph on the right is a double bar graph that shows DRP being integrated and not integrated in the following categories: Incident Classifications, Severity Definitions, Incident Models, Escalation Procedures. These are measured based on the success meeting RTO and RPO.

      Source: Info-Tech Research Group; N=92

      Myth busted: The DRP is separate from day-to-day ops and incident management.

      The most common threats to service continuity are hardware and software failures, network outages, and power outages

      The image displayed is a bar graph that shows the common threats to service continuity. There are two areas of interest that have labels. The first is: 45% of service interruptions that went beyond maximum downtime guidelines set by the business were caused by software and hardware issues. The second label is: Only 12% of incidents were caused by major destructive events.

      Source: Info-Tech Research Group; N=87

      Info-Tech Insight

      Does this mean I don’t need to worry about natural disasters? No. It means DR planning needs to focus on overall service continuity, not just major disasters. If you ignore the more common but less dramatic causes of service interruptions, you are diminishing the business value of a DRP.

      Myth busted: DRPs are just for destructive events – fires, floods, and natural disasters.

      DR isn’t about identifying risks; it’s about ensuring service continuity

      The traditional approach to DR starts with an in-depth exercise to identify risks to IT service continuity and the probability that those risks will occur.

      Here’s why starting with a risk register is ineffective:

      • Odds are, you won’t think of every incident that might occur. If you think of twenty risks, it’ll be the twenty-first that gets you. If you try to guard against that twenty-first risk, you can quickly get into cartoonish scenarios and much more costly solutions.
      • The ability to failover to another site mitigates the risk of most (if not all) incidents (fire, flood, hardware failure, tornado, etc.). A risk and probability analysis doesn’t change the need for a plan that includes a failover procedure.

      Where risk is incorporated in this methodology:

      • Use known risks to further refine your strategy (e.g. if you are prone to hurricanes, plan for greater geographic separation between sites; ensure you have backups, in addition to replication, to mitigate the risk of ransomware).
      • Identify risks to your ability to execute DR (e.g. lack of cross-training, backups that are not tested) and take steps to mitigate those risks.

      Myth busted: A risk register is the critical first step to creating an effective DR plan.

      You can’t outsource accountability and you can’t assume your vendor’s DR capabilities meet your needs

      Outsourcing infrastructure services – to a cloud provider, co-location provider, or managed service provider (MSP) – can improve your DR and service continuity capabilities. For example, a large public cloud provider will generally have:

      • Redundant telecoms service providers, network infrastructure, power feeds, and standby power.
      • Round-the-clock infrastructure and security monitoring.
      • Multiple data centers in a given region, and options to replicate data and services across regions.

      Still, failure is inevitable – it’s been demonstrated multiple times1 through high-profile outages. When you surrender direct control of the systems themselves, it’s your responsibility to ensure the vendor can meet your DR requirements, including:

      • A DR site and acceptable recovery times for systems at that site.
      • An acceptable replication/backup schedule.

      Sources: Kyle York, 2016; Shaun Nichols, 2017; Stephen Burke, 2017

      Myth busted: I outsource infrastructure services so I don’t have to worry about DR. That’s my vendor’s responsibility.

      Choose flowcharts over process guides, checklists over procedures, and diagrams over descriptions

      IT DR is not an airplane disaster movie. You aren’t going to ask a business user to execute a system recovery, just like you wouldn’t really want a passenger with no flying experience to land a plane.

      In reality, you write a DR plan for knowledgeable technical staff, which allows you to summarize key details your staff already know. Concise, visual documentation is:

      • Quicker to create.
      • Easier to use.
      • Simpler to maintain.

      "Without question, 300-page DRPs are not effective. I mean, auditors love them because of the detail, but give me a 10-page DRP with contact lists, process flows, diagrams, and recovery checklists that are easy to follow."

      – Bernard Jones, MBCI, CBCP, CORP, Manager Disaster Recovery/BCP, ActiveHealth Management

      A graph is displayed. It shows a line graph where the DR success is higher by using flowcharts, checklists, and diagrams.

      Source: Info-Tech Research Group; N=95

      *DR Success is based on stated ability to meet recovery time objectives (RTOs) and recovery point objectives (RPOs), and reported confidence in ability to consistently meet targets.

      Myth busted: A DRP must include every detail so anyone can execute recovery.

      A DRP is part of an overall business continuity plan

      A DRP is the set of procedures and supporting documentation that enables an organization to restore its core IT services (i.e. applications and infrastructure) as part of an overall business continuity plan (BCP), as described below. Use the templates, tools, and activities in this blueprint to create your DRP.

      Overall BCP
      IT DRP BCP for Each Business Unit Crisis Management Plan
      A plan to restore IT services (e.g. applications and infrastructure) following a disruption. This includes:
      • Identifying critical applications and dependencies.
      • Defining an appropriate (desired) recovery timeline based on a business impact analysis (BIA).
      • Creating a step-by-step incident response plan.
      A set of plans to resume business processes for each business unit. Info-Tech’s Develop a Business Continuity Plan blueprint provides a methodology for creating business unit BCPs as part of an overall BCP for the organization. A set of processes to manage a wide range of crises, from health and safety incidents to business disruptions to reputational damage. This includes emergency response plans, crisis communication plans, and the steps to invoke BC/DR plans when applicable. Info-Tech’s Implement Crisis Management Best Practices blueprint provides a structured approach to develop a crisis management process.

      Note: For DRP, we focus on business-facing IT services (as opposed to the underlying infrastructure), and then identify required infrastructure as dependencies (e.g. servers, databases, network).

      Take a practical but structured approach to creating a concise and effective DRP

      Image displayed shows the structure of this blueprint. It shows the structure of phases 1-4 and the related tools and templates for each phase.

      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

      Info-Tech advisory services deliver measurable value

      Info-Tech members save an average of $22,983 and 22 days by working with an Info-Tech analyst on DRP (based on client response data from Info-Tech Research Group’s Measured Value Survey, following analyst advisory on this blueprint).

      Why do members report value from analyst engagement?

      1. Expert advice on your specific situation to overcome obstacles and speed bumps.
      2. Structured project and guidance to stay on track.
      3. Project deliverables review to ensure the process is applied properly.

      Guided implementation overview

      Your trusted advisor is just a call away.

      Define DRP scope (Call 1)

      Scope requirements, objectives, and your specific challenges. Identify applications/ systems to focus on first.

      Define current status and system dependencies (Calls 2-3)

      Assess current DRP maturity. Identify system dependencies.

      Conduct a BIA (Calls 4-6)

      Create an impact scoring scale and conduct a BIA. Identify RTO and RPO for each system.

      Recovery workflow (Calls 7-8)

      Create a recovery workflow based on tabletop planning. Identify gaps in recovery capabilities.

      Projects and action items (Calls 9-10)

      Identify and prioritize improvements. Summarize results and plan next steps.

      Your guided implementations will pair you with an advisor from our analyst team for the duration of your DRP project.

      Workshop overview

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

      Image displays the workshop overview for this blueprint. It is a workshop that runs for 4 days and covers various activities and produces many deliverables.

      End-user complaints distract from serious IT-based risks to business continuity

      Case Study

      Industry: Manufacturing
      Source: Info-Tech Research Group Client Engagement

      A global manufacturer with annual sales over $1B worked with Info-Tech to improve DR capabilities.

      DRP BIA

      Conversations with the IT team and business units identified the following impact of downtime over 24 hours:

      • Email: Direct Cost: $100k; Goodwill Impact Score: 8.5/16
      • ERP: Direct Cost: $1.35mm; Goodwill Impact Score: 12.5/16

      Tabletop Testing and Recovery Capabilities

      Reviewing the organization’s current systems recovery workflow identified the following capabilities:

      • Email: RTO: minutes, RPO: minutes
      • ERP: RTO: 14 hours, RPO: 24 hours

      Findings

      Because of end-user complaints, IT had invested heavily in email resiliency though email downtime had a relatively minimal impact on the business. After working through the methodology, it was clear that the business needed to provide additional support for critical systems.

      Insights at each step:

      Identify DR Maturity and System Dependencies

      Conduct a BIA

      Outline Incident Response and Recovery Workflow With Tabletop Exercises

      Mitigate Gaps and Risks

      Create a Right-Sized Disaster Recovery Plan

      Phase 1

      Define DRP Scope, Current Status, and Dependencies

      Step 1.1: Set Scope, Kick-Off the DRP Project, and Create a Charter

      This step will walk you through the following activities:

      • Establish a team for DR planning.
      • Retrieve and review existing, relevant documentation.
      • Create a project charter.

      This step involves the following participants:

      • DRP Coordinator
      • DRP Team (Key IT SMEs)
      • IT Managers

      Results and Insights

      • Set scope for the first iteration of the DRP methodology.
      • Don’t try to complete your DR and BCPs all at once.
      • Don’t bite off too much at once.

      Kick-off your DRP project

      You’re ready to start your DR project.

      This could be an annual review – but more likely, this is the first time you’ve reviewed the DR plan in years.* Maybe a failed audit might have provided a mandate for DR planning, or a real disaster might have highlighted gaps in DR capabilities. First, set appropriate expectations for what the project is and isn’t, in terms of scope, outputs, and resource commitments. Very few organizations can afford to hire a full-time DR planner, so it’s likely this won’t be your full-time job. Set objectives and timelines accordingly.

      Gather a team

      • Often, DR efforts are led by the infrastructure and operations leader. This person can act as the DRP coordinator or may delegate this role.
      • Key infrastructure subject-matter experts (SMEs) are usually part of the team and involved through the project.

      Find and review existing documentation

      • An existing DRP may have information you can re-purpose rather than re-create.
      • High-level architecture diagrams and network diagrams can help set scope (and will become part of your DR kit).
      • Current business-centric continuity of operations plans (COOPs) or BCPs are important to understand.

      Set specific, realistic objectives

      • Create a project charter (see next slide) to record objectives, timelines, and assumptions.
      *Only 20% of respondents to an Info-Tech Research Group survey (N=165) had a complete DRP; only 38% of respondents with a complete or mostly complete DRP felt it would be effective in a crisis.

      List DRP drivers and challenges

      1(a) Drivers and roadblocks

      Estimated Time: 30 minutes

      Identify the drivers and challenges to completing a functional DRP plan with the core DR team.

      DRP Drivers

      • Past outages (be specific):
        • Hardware and software failures
        • External network and power outages
        • Building damage
        • Natural disaster(s)
      • Audit findings
      • Events in the news
      • Other?

      DRP Challenges

      • Lack of time
      • Insufficient DR budget
      • Lack of executive support
      • No internal DRP expertise
      • Challenges making the case for DRP
      • Other?

      Write down insights from the meeting on flip-chart paper or a whiteboard and use the findings to inform your DRP project (e.g. challenges to address).

      Clarify expectations with a project charter

      1(b) DRP Project Charter Template

      DRP Project Charter Template components:

      Define project parameters, roles, and objectives, and clarify expectations with the executive team. Specific subsections are listed below and described in more detail in the remainder of this phase.

      • Project Overview: Includes objectives, deliverables, and scope. Leverage relevant notes from the “Project Drivers” brainstorming exercise (e.g. past outages and near misses which help make the case).
      • Governance and Management: Includes roles, responsibilities, and resource requirements.
      • Project Risks, Assumptions, and Constraints: Includes risks and mitigation strategies, as well as any assumptions and constraints.
      • Project Sign-Off: Includes IT and executive sign-off (if required).

      Note: Identify the initial team roles and responsibilities first so they can assist in defining the project charter.

      The image is a screenshot of the first page of the DRP Project Charter Template.

      Step 1.2: Assess Current State DRP Maturity

      This step will walk you through the following activities:

      • Complete Info-Tech’s DRP Maturity Scorecard.

      This step involves the following participants:

      • DRP Coordinator
      • IT SMEs

      Results and Insights

      • Identify the current state of the organization’s DRP and continuity management. Set a baseline for improvement.
      • Discover where improvement is most needed to create an effective plan.

      Only 38% of IT departments believe their DRPs would be effective in a real crisis

      Even organizations with documented DRPs struggle to make them actionable.

      • Even when a DRP does become a priority (e.g. due to regulatory or customer drivers), the challenge is knowing where to start and having a methodical step-by-step process for doing the work. With no guide to plan and resource the project, it becomes work that you complete piecemeal when you aren’t working on other projects, or at night after the kids go to bed.
      • Far too many organizations create a document to satisfy auditors rather than creating a usable plan. People in this group often just want a fill-in-the-blanks template. What they will typically find is a template for the traditional 300-page manual that goes in a binder that sits on a shelf, is difficult to maintain, and is not effective in a crisis.
      Two bar graphs are displayed. The graph on the left shows that only 20% of survey respondents indicate they have a complete DRP. The graph on the right shows that 38% of those who have a mostly completed or full DRP actually feel it would be effective in a crisis.

      Use the DRP Maturity Scorecard to assess the current state of your DRP and identify areas to improve

      1(c) DRP Maturity Scorecard

      Info-Tech’s DRP Maturity Scorecard evaluates completion status and process maturity for a comprehensive yet practical assessment across three aspects of an effective DRP program – Defining Requirements, Implementation, and Maintenance.

      Image has three boxes. One is labelled Completion status, another below it is labelled Process Maturity. There is an addition sign in between them. With an arrow leading from both boxes is another box that is labelled DRP Maturity Assessment

      Completion Status: Reflects the progress made with each component of your DRP Program.

      Process Maturity: Reflects the consistency and quality of the steps executed to achieve your completion status.

      DRP Maturity Assessment: Each component (e.g. BIA) of your DRP Program is evaluated based on completion status and process maturity to provide an accurate holistic assessment. For example, if your BIA completion status is 4 out of 5, but process maturity is a 2, then requirements were not derived from a consistent defined process. The risk is inconsistent application prioritization and misalignment with actual business requirements.

      Step 1.3: Identify Applications, Systems, and Dependencies

      This step will walk you through the following activities:

      • Identify systems, applications, and services, and the business units that use them.
      • Document applications, systems, and their dependencies in the DRP Business Impact Analysis Tool.

      This step involves the following participants:

      • DRP Coordinator
      • DRP Team

      Results and Insights

      • Identify core services and the applications that depend on them.
      • Add applications and dependencies to the DRP Business Impact Analysis Tool.

      Select 5-10 services to get started on the DRP methodology

      1(d) High-level prioritization

      Estimated Time: 30 minutes

      Working through the planning process the first time can be challenging. If losing momentum is a concern, limit the BIA to a few critical systems to start.

      Run this exercise if you need a structured exercise to decide where to focus first and identify the business users you should ask for input on the impact of system downtime.

      1. On a whiteboard or flip-chart paper, list business units in a column on the left. List key applications/systems in a row at the top. Draw a grid.
      2. At a high level, review how applications are used by each unit. Take notes to keep track of any assumptions you make.
        • Add a ✓ if members of the unit use the application or system.
        • Add an ✱ if members of the unit are heavy users of the application or system and/or use it for time sensitive tasks.
        • Leave the box blank if the app isn’t used by this unit.
      3. Use the chart to prioritize systems to include in the BIA (e.g. systems marked with an *) but also include a few less-critical systems to illustrate DRP requirements for a range of systems.

      Image is an example of what one could complete from step 1(d). There is a table shown. In the column on the left lists sales, marketing, R&D, and Finance. In the top row, there is listed: dialer, ERP. CRM, Internet, analytics, intranet

      Application Notes
      CRM
      • Supports time-critical sales and billing processes.
      Dialer
      • Used for driving the sales-call queue, integration with CRM.

      Draw a high-level sketch of your environment

      1(e) Sketch your environment

      Estimated Time: 1-2 hours

      A high-level topology or architectural diagram is an effective way to identify dependencies, application ownership, outsourced services, hardware redundancies, and more.

      Note:

      • Network diagrams or high-level architecture diagrams help to identify dependencies and redundancies. Even a rough sketch is a useful reference tool for participants, and will be valuable documentation in the final DR plan.
      • Keep the drawings tidy. Visualize the final diagram before you start to draw on the whiteboard to help with spacing and placement.
      • Collaborate with relevant SMEs to identify dependencies. Keep the drawing high-level.
      • Illustrate connections between applications or components with lines. Use color coding to illustrate where applications are hosted (e.g. in-house, at a co-lo, in a cloud or MSP environment).
      Example of a high-level topology or architectural diagram

      Document systems and dependencies

      Collaborate with system SMEs to identify dependencies for each application or system. Document the dependencies in the DRP Business Impact Analysis Tool (see image below)

      • When listing applications, focus on business-facing systems or services that business users will recognize and use terminology they’ll understand.
      • Group infrastructure components that support all other services as a single core infrastructure service to simplify dependency mapping (e.g. core router, virtual hosts, ID management, and DNS).
      • In general, each data center will have its own core infrastructure components. List each data center separately – especially if different services are hosted at each data center.
      • Be specific when documenting dependencies. Use existing asset tracking tables, discovery tools, asset management records, or configuration management tools to identify specific server names.
      • Core infrastructure dependencies, such as the network infrastructure, power supply, and centralized storage, will be a common set of dependencies for most applications, so group these into a separate category called “Core Infrastructure” to minimize repetition in your DR planning.
      • Document production components in the BIA tool. Capture in-production, redundant components performing the same work on a single dependency line. List standby systems in the notes.

      Info-Tech Best Practice

      In general, visual documentation is easier to use in a crisis and easier to maintain over time. Use Info-Tech’s research to help build your own visual SOPs.

      Document systems and dependencies

      1(f) DRP Business Impact Analysis Tool – Record systems and dependencies

      A screenshot of Info-Tech's DRP Business Impact Analysis Tool.

      Stories from the field: Info-Tech clients find value in Phase 1 in the following ways

      An organization uncovers a key dependency that needed to be treated as a Tier 1 system

      Reviewing the entire ecosystem for applications identified key dependencies that were previously considered non-critical. For example, a system used to facilitate secure data transfers was identified as a key dependency for payroll and other critical business processes, and elevated to Tier 1.

      A picture’s worth a thousand words (and 1600 servers)

      Drawing a simple architectural diagram was an invaluable tool to identify key dependencies and critical systems, and to understand how systems and dependencies were interconnected. The drawing was an aha moment for IT and business stakeholders trying to make sense of their 1600-server environment.

      Make the case for DRP

      A member of the S&P 500 used Info-Tech’s DRP Maturity Scorecard to provide a reliable objective assessment and make the case for improvements to the board of directors.

      State government agency initiates a DRP project to complement an existing COOP

      Info-Tech's DRP Project Charter enabled the CIO to clarify their DRP project scope and where it fit into their overall COOP. The project charter example provided much of the standard copy – objectives, scope, project roles, methodology, etc. – required to outline the project.

      Phase 1: Insights and accomplishments

      Image has two screenshots from Info-Tech's Phase 1 tools and templates.

      Created a charter and identified current maturity

      Image has two screenshots. One is from Info-Tech's DRP Business Impact Analysis Tool and the other is from the example in step 1(d).

      Identified systems and dependencies for the BIA

      Summary of Accomplishments:

      • Created a DRP project charter.
      • Completed the DRP Maturity Scorecard and identified current DRP maturity.
      • Prioritized applications/systems for a first pass through DR planning.
      • Identified dependencies for each application and system.

      Up Next: Conduct a BIA to establish recovery requirements

      Create a Right-Sized Disaster Recovery Plan

      Phase 2

      Conduct a BIA to Determine Acceptable RTOs and RPOs

      Step 2.1: Define an Objective Impact Scoring Scale

      This step will walk you through the following activities:

      • Create a scoring scale to measure the business impact of application and system downtime.

      This step involves the following participants:

      • DRP Coordinator
      • DRP Team

      Results and Insights

      • Use a scoring scale tied to multiple categories of real business impact to develop a more objective assessment of application and system criticality.

      Align capabilities to appropriate and acceptable RTOs and RPOs with a BIA

      Too many organizations avoid a BIA because they perceive it as onerous or unneeded. A well-managed BIA is straightforward and the benefits are tangible.

      A BIA enables you to identify appropriate spend levels, maintain executive support, and prioritize DR planning for a more successful outcome. Info-Tech has found that a BIA has a measurable impact on the organization’s ability to set appropriate objectives and investment goals.

      Two bar graphs are depicted. The one on the left shows 93% BIA impact on appropriate RTOs. The graph on the right shows that with BIA, there is 86% on BIA impact on appropriate spending.

      Info-Tech Insight

      Business input is important, but don’t let a lack of it delay a draft BIA. Complete a draft based on your knowledge of the business. Create a draft within IT, and use it to get input from business leaders. It’s easier to edit estimates than to start from scratch; even weak estimates are far better than a blank sheet.

      Pick impact categories that are relevant to your business to develop a holistic view of business impact

      Direct Cost Impact Categories

      • Revenue: permanently lost revenue.
        • Example: one third of daily sales are lost due to a website failure.
      • Productivity: lost productivity.
        • Example: finance staff can’t work without the accounting system.
      • Operating costs: additional operating costs.
        • Example: temporary staff are needed to re-key data.
      • Financial penalties: fines/penalties that could be incurred due to downtime.
        • Example: failure to meet contractual service-level agreements (SLAs) for uptime results in financial penalties.

      Goodwill, Compliance, and Health and Safety Categories

      • Stakeholder goodwill: lost customer, staff, or business partner goodwill due to harm, frustration, etc.
        • Example: customers can’t access needed services because the website is down.
        • Example: a payroll system outage delays paychecks for all staff.
        • Example: suppliers are paid late because the purchasing system is down.
      • Compliance, health, and safety:
        • Example: financial system downtime results in a missed tax filing.
        • Example: network downtime disconnects security cameras.

      Info-Tech Insight

      You don’t have to include every impact category in your BIA. Include categories that could affect your business. Defer or exclude other categories. For example, the bulk of revenue for governmental organizations comes from taxes, which won’t be permanently lost if IT systems fail.

      Modify scoring criteria to help you measure the impact of downtime

      The scoring scales define different types of business impact (e.g. costs, lost goodwill) using a common four-point scale and 24-hour timeframe to simplify BIA exercises and documentation.

      Use the suggestions below as a guide as you modify scoring criteria in the DRP Business Impact Analysis Tool:

      • All the direct cost categories (revenue, productivity, operating costs, financial penalties) require the user to define only a maximum value; the tool will populate the rest of the criteria for that category. Use the suggestions below to find the maximum scores for each of the direct cost categories:
        • Revenue: Divide total revenue for the previous year by 365 to estimate daily revenue. Assume this is the most revenue you could lose in a day, and use this number as the top score.
        • Loss of Productivity: Divide fully-loaded labor costs for the organization by 365 to estimate daily productivity costs. Use this as a proxy measure for the work lost if all business stopped for one day.
        • Increased Operating Costs: Isolate this to known additional costs that result from a disruption (e.g. costs for overtime or temporary staff). Estimate the maximum cost for the organization.
        • Financial Penalties: Isolate this to known financial penalties (e.g. due to failure to meet SLAs or compliance requirements). Use the estimated maximum penalty as the highest value on the scale.
      • Impact on Goodwill: Use an estimate of the percentage of all stakeholders impacted to assess goodwill impact.
      • Impact on Compliance; Impact on Health and Safety: The BIA tool contains default scoring criteria that account for the severity of the impact, the likelihood of occurrence, and in the case of compliance, whether a grace period is available. Use this scale as-is, or adapt this scale to suit your needs.

      Modify the default scoring scale in the DRP Business Impact Analysis Tool to reflect your organization

      2(a) DRP Business Impact Analysis Tool – Scoring criteria


      A screenshot of Info-Tech's DRP Business Impact Analysis Tool's scoring criteria

      Step 2.2: Estimate the Impact of Downtime

      This step will walk you through the following activities:

      • Identify the business impact of service/system/application downtime.

      This step involves the following participants:

      • DRP Coordinator
      • DRP Team
      • IT Service SMEs
      • Business-Side Technology Owners (optional)

      Results and Insights

      • Apply the scoring scale to develop a more objective assessment of the business impact of downtime.
      • Create criticality tiers based on the business impact of downtime.

      Estimate the impact of downtime for each system and application

      2(b) Estimate the impact of systems downtime

      Estimated Time: 3 hours

      On tab 3 of the DRP Business Impact Analysis Tool indicate the costs of downtime, as described below:

      1. Have a copy of the “Scoring Criteria” tab available to use as a reference (e.g. printed or on a second display). In tab 3 use the drop-down menu to assign a score of 0 to 4 based on levels of impact defined in the “Scoring Criteria” tab.
      2. Work horizontally across all categories for a single system or application. This will familiarize you with your scoring scales for all impact categories, and allow you to modify the scoring scales if needed before you proceed much further.
      3. For example, if a core call center phone system was down:

      • Loss of Revenue would be the portion of sales revenue generated through the call center. This might score a 1 or 2 depending on the percent of sales that are processed by the call center.
      • The Impact on Customers might be a 2 or 3 depending on the extent that some customers might be using the call center to receive support or purchase new products or services.
      • The Legal/Regulatory Compliance and Health or Safety Risk might be a 0, as the call center has no impact in either area.
    • Next, work vertically across all applications or systems within a single impact category. This will allow you to compare scores within the category as you create them to ensure internal consistency.
    • Add impact scores to the DRP Business Impact Analysis Tool

      2(c) DRP Business Impact Analysis Tool

      Screenshot of Info-Tech's DRP Business Impact Analysis Tool

      Record business reasons and assumptions that drive BIA scores

      2(d) DRP BIA Scoring Context Example

      Info-Tech suggests that IT leadership and staff identify the impact of downtime first to create a version that you can then validate with relevant business owners. As you work through the BIA as a team, have a notetaker record assumptions you make to help you explain the results and drive business engagement and feedback.

      Some common assumptions:

      • You can’t schedule a disaster, so Info-Tech suggests you assume the worst possible timing for downtime. Base the impact of downtime on the worst day for a disaster (e.g. year-end close, payroll run).
      • Record assumptions made about who and what are impacted by system downtime.
      • Record assumptions made about impact severity.
      • If you deviate from the scoring scale, or if a particular impact doesn’t fit well into the defined scoring scale, document the exception.

      Screenshot of Info-Tech's DRP BIA Scoring Context Example

      Use Info-Tech’s DRP BIA Scoring Context Example as a note-taking template.

      Info-Tech Insight

      You can’t build a perfect scoring scale. It’s fine to make reasonable assumptions based on your judgment and knowledge of the business. Just write down your assumptions. If you don’t write them down, you’ll forget how you arrived at that conclusion.

      Assign a criticality rating based on total direct and indirect costs of downtime

      2(e) DRP Business Impact Analysis Tool – Assign criticality tiers

      Once you’ve finished estimating the impact of downtime, use the following rough guideline to create an initial sort of applications into Tiers 1, 2, and 3.

      1. In general, sort applications based on the Total Impact on Goodwill, Compliance, and Safety first.
        • An effective tactic for a quick sort: assign a Tier 1 rating where scores are 50% or more of the highest total score, Tier 2 where scores are between 25% and 50%, and Tier 3 where scores are below 25%. Some organizations will also include a Tier 0 for the highest-scoring systems.
        • Then review and validate these scores and assignments.
      2. Next, consider the Total Cost of Downtime.
        • The Total Cost is calculated by the tool based on the Scoring Criteria in tab 2 and the impact scores on tab 3.
        • Decide if the total cost impact justifies increasing the criticality rating (e.g. from Tier 2 to Tier 1 due to high cost impact).
      3. Review the assigned impact scores and tiers to check that they’re in alignment. If you need to make an exception, document why. Keep exceptions to a minimum.

      Example: Highest total score is 12

      Screenshot of Info-Tech's DRP Business Impact Analysis Tool

      Step 2.3: Determine Acceptable RTO/RPO Targets

      This step will walk you through the following activities:

      • Review the “Debate Space” approach to setting RTO and RPO (recovery targets).
      • Set preliminary RTOs and RPOs by criticality tier.

      This step involves the following participants:

      • DRP Coordinator
      • DRP Team

      Results and Insights

      • Align recovery targets with the business impact of downtime and data loss.

      Use the “Debate Space” approach to align RTOs and RPOs with the impact of downtime

      The business must validate acceptable and appropriate RTOs and RPOs, but IT can use the guidelines below to set an initial estimate.

      Right-size recovery.

      A shorter RTO typically requires higher investment. If a short period of downtime has minimal impact, setting a low RTO may not be justifiable. As downtime continues, impact begins to increase exponentially to a point where downtime is intolerable – an acceptable RTO must be shorter than this. Apply the same thinking to RPOs – how much data loss is unnoticeable? How much is intolerable?

      A diagram to show the debate space in relation to RTOs and RPOs

      The “Debate Space” is between minimal impact and maximum tolerance for downtime.

      Estimate appropriate, acceptable RTOs and RPOs for each tier

      2(f) Set recovery targets

      Estimated Time: 30 minutes

      RTO and RPO tiers simplify management by setting similar recovery goals for systems and applications with similar criticality.

      Use the “Debate Space” approach to set appropriate and acceptable targets.

      1. For RTO, establish a recovery time range that is appropriate based on impact.
        • Overall, the RTO tiers might be 0-4 hours for gold, 4-24 hours for silver, and 24-48 hours for bronze.
      2. RPOs reflect target data protection measures.
        • Identify the lowest RPO within a tier and make that the standard.
        • For example, RPO for gold data might be five minutes, silver might be four hours, and bronze might be one day.
        • Use this as a guideline. RPO doesn’t always align perfectly with RTO tiers.
      3. Review RTOs and RPOs and make sure they accurately reflect criticality.

      Info-Tech Insight

      In general, the more critical the system, the shorter the RPO. But that’s not always the case. For example, a service bus might be Tier 1, but if it doesn’t store any data, RPO might be longer than other Tier 1 systems. Some systems may have a different RPO than most other systems in that tier. As long as the targets are acceptable to the business and appropriate given the impact, that’s okay.

      Add recovery targets to the DRP Business Impact Analysis Tool

      2(g) DRP Business Impact Analysis Tool – Document recovery objectives

      A screenshot of Info-Tech's DRP Business Impact Analysis Tool – Document recovery objectives

      Stories from the field: Info-Tech clients find value in Phase 2 in the following ways

      Most organizations discover something new about key applications, or the way stakeholders use them, when they work through the BIA and review the results with stakeholders. For example:

      Why complete a BIA? There could be a million reasons

      • A global manufacturer completed the DRP BIA exercise. When email went down, Service Desk phones lit up until it was resolved. That grief led to a high availability implementation for email. However, the BIA illustrated that ERP downtime was far more impactful.
      • ERP downtime would stop production lines, delay customer orders, and ultimately cost the business a million dollars a day.
      • The BIA results clearly showed that the ERP needed to be prioritized higher, and required business support for investment.

      Move from airing grievances to making informed decisions

      The DRP Business Impact Analysis Tool helped structure stakeholder consultations on DR requirements for a large university IT department. Past consultations had become an airing of grievances. Using objective impact scores helped stakeholders stay focused and make informed decisions around appropriate RTOs and RPOs.

      Phase 2: Insights and accomplishments

      Screenshots of the tools and templates from this phase.

      Estimated the business impact of downtime

      Screenshot of a tools from this phase

      Set recovery targets

      Summary of Accomplishments

      • Created a scoring scale tied to different categories of business impact.
      • Applied the scoring scale to estimate the business impact of system downtime.
      • Identified appropriate, acceptable RTOs and RPOs.

      Up Next:Conduct a tabletop planning exercise to establish current recovery capabilities

      Create a Right-Sized Disaster Recovery Plan

      Phase 3

      Identify and Address Gaps in the Recovery Workflow

      Step 3.1: Determine Current Recovery Workflow

      This step will walk you through the following activities:

      • Run a tabletop exercise.
      • Outline the steps for the initial response (notification, assessment, disaster declaration) and systems recovery (i.e. document your recovery workflow).
      • Identify any gaps and risks in your initial response and systems recovery.

      This step involves the following participants:

      • DRP Coordinator
      • IT Infrastructure SMEs (for systems in scope)
      • Application SMEs (for systems in scope)

      Results and Insights

      • Use a repeatable practical exercise to outline and document the steps you would use to recover systems in the event of a disaster, as well as identify gaps and risks to address.
      • This is also a knowledge-sharing opportunity for your team, and a practical means to get their insights, suggestions, and recovery knowledge down on paper.

      Tabletop planning: an effective way to test and document your recovery workflow

      In a tabletop planning exercise, the DRP team walks through a disaster scenario to map out what should happen at each stage, and effectively defines a high-level incident response plan (i.e. recovery workflow).

      Tabletop planning had the greatest impact on meeting recovery objectives (RTOs/RPOs) among survey respondents.

      A bar graph is displayed that shows that tabletop planning has the greatest impact on meeting recovery objectives (RTOs/RPOs) among survey respondents.

      *Note: Relative importance indicates the contribution an individual testing methodology, conducted at least annually, had on predicting success meeting recovery objectives, when controlling for all other types of tests in a regression model. The relative-importance values have been standardized to sum to 100%.

      Success was based on the following items:

      • RTOs are consistently met.
      • IT has confidence in the ongoing ability to meet RTOs.
      • RPOs are consistently met.
      • IT has confidence in the ongoing ability to meet RPOs.

      Why is tabletop planning so effective?

      • It enables you to play out a wider range of scenarios than technology-based testing (e.g. full-scale, parallel) due to cost and complexity factors.
      • It is non-intrusive, so it can be executed more frequently than other testing methodologies.
      • It easily translates into the backbone of your recovery documentation, as it allows you to review all aspects of your recovery plan.

      Focus first on IT DR

      Your DRP is IT contingency planning. It is not crisis management or BCP.

      The goal is to define a plan to restore applications and systems following a disruption. For your first tabletop exercise, Info-Tech recommends you use a non-life-threatening scenario that requires at least a temporary relocation of your data center (i.e. failing over to a DR site/environment). Assume a gas leak or burst water pipe renders the data center inaccessible. Power is shut off and IT must failover systems to another location. Once you create the master procedure, review the plan to ensure it addresses other scenarios.

      Info-Tech Insight

      When systems fail, you are faced with two high-level options: failover or recover in place. If you document the plan to failover systems to another location, you’ll have documented the core of your DR procedures. This differs from traditional scenario planning where you define separate plans for different what-if scenarios. The goal is one plan that can be adapted to different scenarios, which reduces the effort to build and maintain your DRP.

      Conduct a tabletop planning exercise to outline DR procedures in your current environment

      3(a) Tabletop planning

      Estimated Time: 2-3 hours

      For each high-level recovery step, do the following:

      1. On white cue cards:
        • Record the step.
        • Indicate the task owner (if required for clarity).
        • Note time required to complete the step. After the exercise, use this to build a running recovery time where 00:00 is when the incident occurred.
      2. On yellow cue cards, document gaps in people, process, and technology requirements to complete the step.
      3. On red cue cards, indicate risks (e.g. no backup person for a key staff member).
      An example is shown on what can be done during step 3(a). Three cue cards are showing in white, yellow, and red.

      Do:

      • Review the complete workflow from notification all the way to user acceptance testing.
      • Keep focused; stay on task and on time.
      • Revisit each step and record gaps and risks (and known solutions, but don’t dwell on this).
      • Revise and improve the plan with task owners.

      Don't:

      • Get weighed down by tools.
      • Document the details right away – stick to the high-level plan for the first exercise.
      • Try to find solutions to every gap/risk as you go. Save in-depth research/discussion for later.

      Flowchart the current-state incident response plan (i.e. document the recovery workflow)

      3(b) DRP Recovery Workflow Template and Case Study: Practical, Right-Sized DRP

      Why use flowcharts?

      • Flowcharts provide an at-a-glance view, ideal for disaster scenarios where pressure is high and quick upward communication is necessary.
      • For experienced staff, a high-level reminder of key steps is sufficient.

      Use the completed tabletop planning exercise results to build this workflow.

      "We use flowcharts for our declaration procedures. Flowcharts are more effective when you have to explain status and next steps to upper management." – Assistant Director, IT Operations, Healthcare Industry

      Source: Info-Tech Research Group Interview

      Screenshot of Info-Tech's DRP Recovery Workflow Template

      For a formatted template you can use to capture your plan, see Info-Tech’s DRP Recovery Workflow Template.

      For a completed example of tabletop planning results, review Info-Tech’s Case Study: Practical, Right-Sized DRP.

      Identify RPA

      What’s my RPA? Consider the following case:

      • Once a week, a full backup is taken of the complete ERP system and is transferred over the WAN to a secondary site 250 miles away, where it is stored on disk.
      • Overnight, an incremental backup is taken of the day’s changes, and is transferred to the same secondary site, and also stored on disk.
      • During office hours, the SAN takes a snapshot of changes which are kept on local storage (information on the accounting system usually only changes during office hours).
      • So what’s the RPA? One hour (snapshots), one day (incrementals), or one week (full backups)?

      When identifying RPA, remember the following:

      You are planning for a disaster scenario, where on-site systems may be inaccessible and any copies of data taken during the disaster may fail, be corrupt, or never make it out of the data center (e.g. if the network fails before the backup file ships). In the scenario above, it seems likely that off-site incremental backups could be restored, leading to a 24-hour RPA. However, if there were serious concerns about the reliability of the daily incrementals, the RPA could arguably be based on the weekly full backups.

      Info-Tech Best Practice

      The RPA is a commitment to the maximum data you would lose in a DR scenario with current capabilities (people, process, and technology). Pick a number you can likely achieve. List any situations where you couldn’t meet this RPA, and identify those for a risk tolerance discussion. In the example above, complete loss of the primary SAN would also mean losing the snapshots, so the last good copy of the data could be up to 24-hours old.

      Add recovery actuals (RTA/RPA) to your copy of the BIA

      3(c) DRP Business Impact Analysis Tool– Recovery actuals

      On the “Impact Analysis” tab in the DRP Business Impact Analysis Tool, enter the estimated maximum downtime and data loss in the RTA and RPA columns.

      1. Estimate the RTA based on the required time for complete recovery. Review your recovery workflow to identify this timeline. For example, if the notification, assessment, and declaration process takes two hours, and systems recovery requires most of a day, the estimated RTA could be 24 hours.
      2. Estimate the RPA based on the longest interval between copies of the data being shipped offsite. For example, if data on a particular system is backed up offsite once per day, and the onsite system was destroyed just before that backup began, the entire day’s data could be lost and estimated RPA could be 24 hours. Note: Enter 9999 to indicate that data is unrecoverable.

      A screenshot of Info-Tech's DRP Business Impact Analysis Tool – Recovery actuals

      Info-Tech Best Practice

      It’s okay to round numbers to the nearest shift, day, or week for simplicity (e.g. 24 hours rather than 22.5 hours, or 8 hours rather than 7.25 hours).

      Test the recovery workflow against additional scenarios

      3(d) Workflow review

      Estimated Time: 1 hour

      Review your recovery workflow with a different scenario in mind.

      • Work from and update the soft copy of your recovery workflow.
      • Would any steps be different if the scenario changes? If yes, capture the different flow with a decision diamond. Identify any new gaps or risks you encounter with red and yellow cards. Use as few decision diamonds as possible.

      Screenshot of testing the workflow against the additional scenarios

      Info-Tech Best Practice

      As you start to consider scenarios where injuries or loss of life are a possibility, remember that health and safety risks are the top priority in a crisis. If there’s a fire in the data center, evacuating the building is the first priority, even if that means foregoing a graceful shut down. For more details on emergency response and crisis management, see Implement Crisis Management Best Practices.

      Consider additional IT disaster scenarios

      3(e) Thought experiment – Review additional scenarios

      Walk through your recovery workflow in the context of additional, different scenarios to ensure there are no gaps. Collaborate with your DR team to identify changes that might be required, and incorporate these changes in the plan.

      Scenario Type Considerations
      Isolated hardware/software failure
      • Failover to the DR site may not be necessary (or only for affected systems).
      Power outage or network outage
      • Do you have standby power? Do you have network redundancy?
      Local hazard (e.g. chemical leak, police incident)
      • Systems might be accessible remotely, but hands-on maintenance will be required eventually.
      • An alternate site is required for service continuity.
      Equipment/building damage (e.g. fire, roof collapse)
      • Staff injuries or loss of life are a possibility.
      • Equipment may need repair or replacement (vendor involvement).
      • An alternate site is required for service continuity.
      Regional natural disasters
      • Staff injuries or loss of life are a possibility.
      • Utilities may be affected (power, running water, etc.).
      • Expect staff to take care of their families first before work.
      • A geographically distant alternate site may be required for service continuity.

      Step 3.2: Identify and Prioritize Projects to Close Gaps

      This step will walk you through the following activities:

      • Analyze the gaps that were identified from the maturity scorecard, tabletop planning exercise, and the RTO/RPO gaps analysis.
      • Brainstorm solutions to close gaps and mitigate risks.
      • Determine a course of action to close these gaps. Prioritize each project. Create a project implementation timeline.

      This step involves the following participants:

      • DRP Coordinator
      • IT Infrastructure SMEs

      Results and Insights

      • Prioritized list of projects and action items that can improve DR capabilities.
      • Often low-cost, low-effort quick wins are identified to mitigate at least some gaps/risks. Higher-cost, higher-effort projects can be part of a longer-term IT strategy. Improving service continuity is an ongoing commitment.

      Brainstorm solutions to address gaps and risk

      3(f) Solutioning

      Estimated Time: 1.5 hours

      1. Review each of the risk and gap cards from the tabletop exercise.
      2. As a group, brainstorm ideas to address gaps, mitigate risks, and improve resiliency. Write the list of ideas on a whiteboard or flip-chart paper. The solutions can range from quick-wins and action items to major capital investments.
      3. Try to avoid debates about feasibility at this point – that should happen later. The goal is to get all ideas on the board.

      An example of how to complete Activity 3(f). Three cue cards showing various steps are attached by arrows to steps on a whiteboard.

      Info-Tech Best Practice

      It’s about finding ways to solve the problem, not about solving the problem. When you’re brainstorming solutions to problems, don’t stop with the first idea, even if the solution seems obvious. The first idea isn’t always the best or only solution; other ideas can expand on and improve that first idea.

      Select an optimal DR deployment model from a world of choice

      There are many options for a DR deployment. What makes sense for you?

      • Sifting through the options for a DR site can be overwhelming. Simplify by eliminating deployment models that aren’t a good fit for your requirements or organization using Info-Tech’s research.
      • Someone will ask you about DR in the cloud. Cut to the chase and evaluate cloud for fit with your organization’s current capabilities and requirements. Read about the 10 Secrets for Successful DR in the Cloud.
      • Selecting and deploying a DR site is an exercise in risk mitigation. IT’s role is to advise the business on options to address the risk of not having a DR site, including cost and effort estimates. The business must then decide how to manage risk. Build total cost of ownership (TCO) estimates and evaluate possible challenges and risks for each option.

      Is it practical to invest in greater geo-redundancy that meets RTOs and RPOs during a widespread event?

      Info-Tech suggests you consider events that impact both sites, and your risk tolerance for that impact. Outline the impact of downtime at a high level if both the primary and secondary site were affected. Research how often events severe enough to have impacted both your primary and secondary sites have occurred in the past. What’s the business tolerance for this type of event?

      A common strategy: have a primary and DR site that are close enough to support low RPO/RTO, but far enough away to mitigate the impact of known regional events. Back up data to a remote third location as protection against a catastrophic event.

      Info-Tech Insight

      Approach site selection as a project. Leverage Select an Optimal Disaster Recovery Deployment Model to structure your own site-selection project.

      Set up the DRP Roadmap Tool

      3(g) DRP Roadmap Tool – Set up tool

      Use the DRP Roadmap Tool to create a high-level roadmap to plan and communicate DR action items and initiatives. Determine the data you’ll use to define roadmap items.

      Screenshot of Info-Tech's DRP Roadmap Tool

      Plan next steps by estimating timeline, effort, priority, and more

      3(h) DRP Roadmap Tool – Describe roadmap items

      A screenshot of Info-Tech's DRP Roadmap Tool to show how to describe roadmap items

      Review and communicate the DRP Roadmap Tool

      3(i) DRP Roadmap Tool – View roadmap chart

      A screenshot of Info-Tech's DRP Roadmap Tool's Roadmap tab

      Step 3.3: Review the Future State Recovery Process

      This step will walk you through the following activities:

      • Update the recovery workflow to outline your future recovery procedure.
      • Summarize findings from DR exercises and present the results to the project sponsor and other interested executives.

      This step involves the following participants:

      • DRP Coordinator
      • IT SMEs (Future State Recovery Flow)
      • DR Project Sponsor

      Results and Insights

      • Summarize results from DR planning exercises to make the case for needed DR investment.

      Outline your future state recovery flow

      3(j) Update the recovery workflow to outline response and recovery in the future

      Estimated Time: 30 minutes

      Outline your expected future state recovery flow to demonstrate improvements once projects and action items have been completed.

      1. Create a copy of your DRP recovery workflow in a new tab in Visio.
      2. Delete gap and risk cards that are addressed by proposed projects. Consolidate or eliminate steps that would be simplified or streamlined in the future if projects are implemented.
      3. Create a short-, medium-, and long-term review of changes to illustrate improvements over time to the project roadmap.
      4. Update this workflow as you implement and improve DR capabilities.

      Screenshot of the recovery workflow

      Validate recovery targets and communicate actual recovery capabilities

      3(k) Validate findings, present recommendations, secure budget

      Estimated Time: time required will vary

      1. Interview managers or process owners to validate RTO, RPO, and business impact scores.Use your assessment of “heavy users” of particular applications (picture at right) to remind you which business users you should include in the interview process.
      2. Present an overview of your findings to the management team.Use Info-Tech’s DRP Recap and Results Template to summarize your findings.
      3. Take projects into the budget process.With the management team aware of the rationale for investment in DRP, build the business case and secure budget where needed.

      Present DRP findings and make the case for needed investment

      3(I) DRP Recap and Results Template

      Create a communication deck to recap key findings for stakeholders.

      • Write a clear problem statement. Identify why you did this project (what problem you’re solving).
      • Clearly state key findings, insights, and recommendations.
      • Leverage the completed tools and templates to populate the deck. Callouts throughout the template presentation will direct you to take and populate screenshots throughout the document.
      • Use the presentation to communicate key findings to, and gather feedback from, business unit managers, executives, and IT staff.
      Screenshots of Info-Tech's DRP Recap and Results Template

      Stories from the field: Info-Tech clients find value in Phase 3 in the following ways

      Tabletop planning is an effective way to discover gaps in recovery capabilities. Identify issues in the tabletop exercise so you can manage them before disaster strikes. For example:

      Back up a second…

      A client started to back up application data offsite. To minimize data transfer and storage costs, the systems themselves weren’t backed up. Working through the restore process at the DR site, the DBA realized 30 years of COBOL and SQR code – critical business functionality – wasn’t backed up offsite.

      Net… work?

      A 500-employee professional services firm realized its internet connection could be a significant roadblock to recovery. Without internet, no one at head office could access critical cloud systems. The tabletop exercise identified this recovery bottleneck and helped prioritize the fix on the roadmap.

      Someone call a doctor!

      Hospitals rely on their phone systems for system downtime procedures. A tabletop exercise with a hospital client highlighted that if the data center were damaged, the phone system would likely be damaged as well. Identifying this provided more urgency to the ongoing VOIP migration.

      The test of time

      A small municipality relied on a local MSP to perform systems restore, but realized it had never tested the restore procedure to identify RTA. Contacting the MSP to review capabilities became a roadmap item to address this risk.

      Phase 3: Insights and accomplishments

      Screenshot of Info-Tech's DRP recovery workflow template

      Outlined the DRP response and risks to recovery

      Screenshots of activities completed related to brainstorming risk mitigation measures.

      Brainstormed risk mitigation measures

      Summary of Accomplishments

      • Planned and documented your DR incident response and systems recovery workflow.
      • Identified gaps and risks to recovery and incident management.
      • Brainstormed and identified projects and action items to mitigate risks and close gaps.

      Up Next: Leverage the core deliverables to complete, extend, and maintain your DRP

      Create a Right-Sized Disaster Recovery Plan

      Phase 4

      Complete, Extend, and Maintain Your DRP

      Phase 4: Complete, Extend, and Maintain Your DRP

      This phase will walk you through the following activities:

      • Identify progress made on your DRP by reassessing your DRP maturity.
      • Prioritize the highest value major initiatives to complete, extend, and maintain your DRP.

      This phase involves the following participants:

      • DRP Coordinator
      • Executive Sponsor

      Results and Insights

      • Communicate the value of your DRP by demonstrating progress against items in the DRP Maturity Scorecard.
      • Identify and prioritize future major initiatives to support the DRP, and the larger BCP.

      Celebrate accomplishments, plan for the future

      Congratulations! You’ve completed the core DRP deliverables and made the case for investment in DR capabilities. Take a moment to celebrate your accomplishments.

      This milestone is an opportunity to look back and look forward.

      • Look back: measure your progress since you started to build your DRP. Revisit the assessments completed in phase 1, and assess the change in your overall DRP maturity.
      • Look forward: prioritize future initiatives to complete, extend, and maintain your DRP. Prioritize initiatives that are the highest impact for the least requirement of effort and resources.

      We have completed the core DRP methodology for key systems:

      • BIA, recovery objectives, high-level recovery workflow, and recovery actuals.
      • Identify key tasks to meet recovery objectives.

      What could we do next?

      • Repeat the core methodology for additional systems.
      • Identify a DR site to meet recovery requirements, and review vendor DR capabilities.
      • Create a summary DRP document including requirements, capabilities, and change procedures.
      • Create a test plan and detailed recovery documentation.
      • Coordinate the creation of BCPs.
      • Integrate DR in other key operational processes.

      Revisit the DRP Maturity Scorecard to measure progress and identify remaining areas to improve

      4(a) DRP Maturity Scorecard – Reassess your DRP program maturity

      1. Find the copy of the DRP Maturity Scorecard you completed previously. Save a second copy of the completed scorecard in the same folder.
      2. Update scoring where you have improved your DRP documentation or capabilities.
      3. Review the new scores on tab 3. Compare the new scores to the original scores.

      Screenshot of DRP Maturity Assessment Results

      Info-Tech Best Practice

      Use the completed, updated DRP Maturity Scorecard to demonstrate the value of your continuity program, and to help you decide where to focus next.

      Prioritize major initiatives to complete, extend, and maintain the DRP

      4(b) Prioritize major initiatives

      Estimated Time: 2 hours

      Prioritize major initiatives that mitigate significant risk with the least cost and effort.

      1. Use the scoring criteria below to evaluate risk, effort, and cost for potential initiatives. Modify the criteria if required for your organization. Write this out on a whiteboard or flip-chart paper.
      2. Assign a score from 1 to 3. Multiply the scores for each initiative together for an aggregate score. In general, prioritize initiatives with higher scores.
      Score A: How significant are the risks this initiative will mitigate? B: How easily can we complete this initiative? C: How cost-effective is this initiative?
      3: High Critical impact on +50% of stakeholders, or major impact to compliance posture, or significant health/safety risk. One sprint, can be completed by a few individuals with minor supervision. Within the IT discretionary budget.
      2: Medium Impacts <50% of stakeholders, or minor impact on compliance, or degradation to health or safety controls. One quarter, and/or some increased effort required, some risk to completion. Requires budget approval from finance.
      1: Low Impacts limited to <25% of stakeholders, no impact on compliance posture or health/safety. One year, and/or major vendor or organizational challenges. Requires budget approval from the board of directors.

      Info-Tech Best Practice

      You can use a similar scoring exercise to prioritize and schedule high-benefit, low-effort, low-cost items identified in the roadmap in phase 3.

      Example: Prioritize major initiatives

      4(b) Prioritize major initiatives continued

      Write out the table on a whiteboard (record the results in a spreadsheet for reference). In the case below, IT might decide to work on repeating the core methodology first as they create the active testing plans, and tackle process changes later.

      Initiative A: How significant are the risks this initiative will mitigate? B: How easily can we complete this initiative? C: How cost-effective is this initiative? Aggregate score (A x B x C)
      Repeat the core methodology for all systems 2 – will impact some stakeholders, no compliance or safety impact. 2 – will require about 3 months, no significant complications. 3 – No cost. 12
      Add DR to project mgmt. and change mgmt. 1 – Mitigates some recovery risks over the long term. 1 – Requires extensive consultation and process review. 3 – No cost. 3
      Active failover testing on plan 2 – Mitigates some risks; documentation and cross training is already in place. 2 – Requires 3-4 months of occasional effort to prepare for test. 2 – May need to purchase some equipment before testing. 8

      Info-Tech Best Practice

      Find a pace that allows you to keep momentum going, but also leaves enough time to act on the initial findings, projects, and action items identified in the DRP Roadmap Tool. Include these initiatives in the Roadmap tool to visualize how identified initiatives fit with other tasks identified to improve your recovery capabilities.

      Repeat the core DR methodology for additional systems and applications


      You have created a DR plan for your most critical systems. Now, add the rest:

      • Build on the work you’ve already done. Re-use the BIA scoring scale. Update your existing recovery workflows, rather than creating and formatting an entirely new document. A number of steps in the recovery will be shared with, or similar to, the recovery procedures for your Tier 1 systems.

      Risks and Challenges Mitigated

      • DR requirements and capabilities for less-critical systems have not been evaluated.
      • Gaps in the recovery process for less critical systems have not been evaluated or addressed.
      • DR capabilities for less critical systems may not meet business requirements.
      Sample Outputs
      Add Tier 2 & 3 systems to the BIA.
      Complete another tabletop exercise for Tier 2 & 3 systems recovery, and add the results to the recovery workflow.
      Identify projects to close additional gaps in the recovery process. Add projects to the project roadmap.

      Info-Tech Best Practice

      Use this example of a complete, practical, right-size DR plan to drive and guide your efforts.

      Extend your core DRP deliverables

      You’ve completed the core DRP deliverables. Continue to create DRP documentation to support recovery procedures and governance processes:

      • DR documentation efforts fail when organizations try to boil the ocean with an all-in-one plan aimed at auditors, business leaders, and IT. It’s long, hard to maintain, and ends up as shelfware.
      • Create documentation in layers to keep it manageable. Build supporting documentation over time to support your high-level recovery workflow.

      Risks and Challenges Mitigated

      • Key contact information, escalation, and disaster declaration responsibilities are not identified or formalized.
      • DRP requirements and capabilities aren’t centralized. Key DRP findings are in multiple documents, complicating governance and oversight by auditors, executives, and board members.
      • Detailed recovery procedures and peripheral information (e.g. network diagrams) are not documented.
      Sample Outputs
      Three to five detailed systems recovery flowcharts/checklists.
      Documented team roles, succession plans, and contact information.
      Notification, assessment, and disaster declaration plan.
      DRP summary.
      Layer 1, 2 & 3 network diagrams.

      Info-Tech Best Practice

      Use this example of a complete, practical, right-size DR plan to drive and guide your efforts.

      Select an optimal DR deployment model and deployment site

      Your DR site has been identified as inadequate:

      • Begin with the end in mind. Commit to mastering the selected model and leverage your vendor relationship for effective DR.
      • Cut to the chase and evaluate the feasibility of cloud first. Gauge your organization’s current capabilities for DR in the cloud before becoming infatuated with the idea.
      • A mixed model gives you the best of both worlds. Diversify your strategy by identifying fit for purpose and balancing the work required to maintain various models.

      Risks and Challenges Mitigated

      • Without an identified DR site, you’ll be scrambling when a disaster hits to find and contract for a location to restore IT services.
      • Without systems and application data backed up offsite, you stand to lose critical business data and logic if all copies of the data at your primary site were lost.
      Sample Outputs
      Application assessment for cloud DR.
      TCO tool for different environments.
      Solution decision and executive presentation.

      Info-Tech Best Practice

      Use Info-Tech’s blueprint, Select the Optimal Disaster Recovery Deployment Model, to help you make sense of a world of choice for your DR site.

      Extend DRP findings to business process resiliency with a BCP pilot

      Integrate your findings from DRP into the overall BCP:

      • As an IT leader you have the skillset and organizational knowledge to lead a BCP project, but ultimately business leaders need to own the BCP – they know their processes and requirements to resume business operations better than anyone else.
      • The traditional approach to BCP is a massive project that most organizations can’t execute without hiring a consultant. To execute BCP in-house, carve up the task into manageable pieces.

      Risks and Challenges Mitigated

      • No formal plan exists to recover from a disruption to critical business processes.
      • Business requirements for IT systems recovery may change following a comprehensive review of business continuity requirements.
      • Outside of core systems recovery, IT could be involved in relocating staff, imaging and issuing new end-user equipment, etc. Identifying these requirements is part of BCP.
      Sample Outputs
      Business process-focused BIA for one business unit.
      Recovery workflows for one business unit.
      Provisioning list for one business unit.
      BCP project roadmap.

      Info-Tech Best Practice

      Use Info-Tech’s blueprint, Develop a Business Continuity Plan, to develop and deploy a repeatable BCP methodology.

      Test the plan to validate capabilities and cross-train staff on recovery procedures

      You don’t have a program to regularly test the DR plan:

      • Most DR tests are focused solely on the technology and not the DR management process – which is where most plans fail.
      • Be proactive – establish an annual test cycle and identify and coordinate resources well in advance.
      • Update DRP documentation with findings from the plan, and track the changes you make over time.

      Risks and Challenges Mitigated

      • Gaps likely still exist in the plan that are hard to find without some form of testing.
      • Customers and auditors may ask for some form of DR testing.
      • Staff may not be familiar with DR documentation or how they can use it.
      • No formal cycle to validate and update the DRP.
      Sample Outputs
      DR testing readiness assessment.
      Testing handbooks.
      Test plan summary template.
      DR test issue log and analysis tool.

      Info-Tech Best Practice

      Uncover deficiencies in your recovery procedures by using Info-Tech’s blueprint Reduce Costly Downtime Through DR Testing.

      “Operationalize” DRP management

      Inject DR planning in key operational processes to support plan maintenance:

      • Major changes, or multiple routine changes, can materially alter DR capabilities and requirements. It’s not feasible to update the DR plan after every routine change, so leverage criticality tiers in the BIA to focus your change management efforts. Critical systems require more rigorous change procedures.
      • Likewise, you can build criticality tiers into more focused project management and performance measurement processes.
      • Schedule regular tasks in your ticketing system to verify capabilities and cross-train staff on key recovery procedures (e.g. backup and restore).

      Risks and Challenges Mitigated

      • DRP is not updated “as needed” – as requirements and capabilities change due to business and technology changes.
      • The DRP is disconnected from day-to-day operations.
      Sample Outputs
      Reviewed and updated change, project, and performance management processes.
      Reviewed and updated internal SLAs.
      Reviewed and updated data protection and backup procedures.

      Review infrastructure service provider DR capabilities

      Insert DR planning in key operational processes to support plan maintenance:

      • Reviewing vendor DR capabilities is a core IT vendor management competency.
      • As your DR requirements change year-to-year, ensure your vendors’ service commitments still meet your DR requirements.
      • Identify changes in the vendor’s service offerings and DR capabilities, e.g. higher costs for additional DR support, new offerings to reduce potential downtime, or conversely, a degradation in DR capabilities.

      Risks and Challenges Mitigated

      • Vendor capabilities haven’t been measured against business requirements.
      • No internal capability exists currently to assess vendor ability to meet promised SLAs.
      • No internal capability exists to track vendor performance on recoverability.
      Sample Outputs
      A customized vendor DRP questionnaire.
      Reviewed vendor SLAs.
      Choose to keep or change service levels or vendor offerings based on findings.

      Phase 4: Insights and accomplishments

      Screenshot of DRP Maturity Assessment Results

      Identified progress against targets

      Screenshot of prioritized further initiatives.

      Prioritized further initiatives

      Screenshot of DRP Planning Roadmap

      Added initiatives to the roadmap

      Summary of Accomplishments

      • Developed a list of high-priority initiatives that can support the extension and maintenance of the DR plan over the long term.
      • Reviewed and update maturity assessments to establish progress and communicate the value of the DR program.

      Summary of accomplishment

      Knowledge Gained

      • Conduct a BIA to determine appropriate targets for RTOs and RPOs.
      • Identify DR projects required to close RTO/RPO gaps and mitigate risks.
      • Use tabletop planning to create and validate an incident response plan.

      Processes Optimized

      • Your DRP process was optimized, from BIA to documenting an incident response plan.
      • Your vendor evaluation process was optimized to identify and assess a vendor’s ability to meet your DR requirements, and to repeat this evaluation on an annual basis.

      Deliverables Completed

      • DRP Maturity Scorecard
      • DRP Business Impact Analysis Tool
      • DRP Roadmap Tool
      • Incident response plan and systems recovery workflow
      • Executive presentation

      Info-Tech’s insights bust the most obstinate myths of DRP

      Myth #1: DRPs need to focus on major events such as natural disasters and other highly destructive incidents such as fire and flood.

      Reality: The most common threats to service continuity are hardware and software failures, network outages, and power outages.

      Myth #2: Effective DRPs start with identifying and evaluating potential risks.

      Reality: DR isn’t about identifying risks; it’s about ensuring service continuity.

      Myth #3: DRPs are separate from day-to-day operations and incident management.

      Reality: DR must be integrated with service management to ensure service continuity.

      Myth #4: I use a co-lo or cloud services so I don’t have to worry about DR. That’s my vendor’s responsibility.

      Reality: You can’t outsource accountability. You can’t just assume your vendor’s DR capabilities will meet your needs.

      Myth #5: A DRP must include every detail so anyone can execute the recovery.

      Reality: IT DR is not an airplane disaster movie. You aren’t going to ask a business user to execute a system recovery, just like you wouldn’t really want a passenger with no flying experience to land a plane.

      Supplement the core documentation with these tools and templates

      • An Excel workbook workbook to track key roles on DR, business continuity, and emergency response teams. Can also track DR documentation location and any hardware purchases required for DR.
      • A questionnaire template and a response tracking tool to structure your investigation of vendor DR capabilities.
      • Integrate escalation with your DR plan by defining incident severity and escalation rules . Use this example as a template or integrate ideas into your own severity definitions and escalation rules in your incident management procedures.
      • A minute-by-minute time-tracking tool to capture progress in a DR or testing scenario. Monitor progress against objectives in real time as recovery tasks are started and completed.

      Next steps: Related Info-Tech research

      Select the Optimal Disaster Recovery Deployment Model Evaluate cloud, co-lo, and on-premises disaster recovery deployment models.

      Develop a Business Continuity Plan Streamline the traditional approach to make BCP development manageable and repeatable.

      Prepare for a DRP Audit Assess your current DRP maturity, identify required improvements, and complete an audit-ready DRP summary document.

      Document and Maintain Your Disaster Recovery Plan Put your DRP on a diet: keep it fit, trim, and ready for action.

      Reduce Costly Downtime Through DR Testing Improve your DR plan and your team’s ability to execute on it.

      Implement Crisis Management Best Practices An effective crisis response minimizes the impact of a crisis on reputation, profitability, and continuity.

      Research contributors and experts

      • Alan Byrum, Director of Business Continuity, Intellitech
      • Bernard Jones (MBCI, CBCP, CORP, ITILv3), Owner/Principal, B Jones BCP Consulting, LLC
      • Paul Beaudry, Assistant Vice-President, Technical Services, MIS, Richardson International Limited
      • Yogi Schulz, President, Corvelle Consulting

      Glossary

      • Business Continuity Management (BCM) Program: Ongoing management and governance process supported by top management and appropriately resourced to implement and maintain business continuity management. (Source: ISO 22301:2012)
      • Business Continuity Plan (BCP): Documented procedures that guide organizations to respond, recover, resume, and restore to a pre-defined level of operation following disruption. The BCP is not necessarily one document, but a collection of procedures and information.
      • Crisis: A situation with a high level of uncertainty that disrupts the core activities and/or credibility of an organization and requires urgent action. (Source: ISO 22300)
      • Crisis Management Team (CMT): A group of individuals responsible for developing and implementing a comprehensive plan for responding to a disruptive incident. The team consists of a core group of decision makers trained in incident management and prepared to respond to any situation.
      • Disaster Recovery Planning (DRP): The activities associated with the continuing availability and restoration of the IT infrastructure.
      • Incident: An event that has the capacity to lead to loss of, or a disruption to, an organization’s operations, services, or functions – which, if not managed, can escalate into an emergency, crisis, or disaster.
      • BCI Editor’s Note: In most countries “incident” and “crisis” are used interchangeably, but in the UK the term “crisis” has been generally reserved for dealing with wide-area incidents involving Emergency Services. The BCI prefers the use of “incident” for normal BCM purposes. (Source: The Business Continuity Institute)

      • Incident Management Plan: A clearly defined and documented plan of action for use at the time of an incident, typically covering the key personnel, resources, services, and actions needed to implement the incident management process.
      • IT Disaster: A service interruption requiring IT to rebuild a service, restore from backups, or activate redundancy at the backup site.
      • Recovery Point: Time elapsed between the last good copy of the data being taken and failure/corruption on the production environment; think of this as data loss.
      • Recovery Point Actual (RPA): The currently achievable recovery point after a disaster event, given existing people, processes, and technology. This reflects expected maximum data loss that could actually occur in a disaster scenario.
      • Recovery Point Objective (RPO): The target recovery point after a disaster event, usually calculated in hours, on a given system, application, or service. Think of this as acceptable and appropriate data loss. RPO should be based on a business impact analysis (BIA) to identify an acceptable and appropriate recovery target.
      • Recovery Time: Time required to restore a system, application, or service to a functional state; think of this as downtime.
      • Recovery Time Actual (RTA): The currently achievable recovery time after a disaster event, given existing people, processes, and technology. This reflects expected maximum downtime that could actually occur in a disaster scenario.
      • Recovery Time Objective (RTO): The target recovery time after a disaster event for a given system, application, or service. RTO should be based on a business impact analysis (BIA) to identify acceptable and appropriate downtime.

      Bibliography

      BCMpedia. “Recovery Objectives: RTO, RPO, and MTPD.” BCMpedia, n.d. Web.

      Burke, Stephen. “Public Cloud Pitfalls: Microsoft Azure Storage Cluster Loses Power, Puts Spotlight On Private, Hybrid Cloud Advantages.” CRN, 16 Mar. 2017. Web.

      Elliot, Stephen. “DevOps and the Cost of Downtime: Fortune 1000 Best Practice Metrics Quantified.” IDC, 2015. Web.

      FEMA. Planning & Templates. FEMA, 2015. Web.

      FINRA. “Business Continuity Plans and Emergency Contact Information.” FINRA, 2015. Web.

      FINRA. “FINRA, the SEC and CFTC Issue Joint Advisory on Business Continuity Planning.” FINRA, 2013. Web.

      Gosling, Mel, and Andrew Hiles. “Business Continuity Statistics: Where Myth Meets Fact.” Continuity Central, 2009. Web.

      Hanwacker, Linda. “COOP Templates for Success Workbook.” The LSH Group, n.d. Web.

      Homeland Security. Federal Information Security Management Act (FISMA). Homeland Security, 2015. Web.

      Nichols, Shaun. “AWS's S3 Outage Was So Bad Amazon Couldn't Get Into Its Own Dashboard to Warn the World.” The Register, 1 Mar. 2017. Web.

      Potter, Patrick. “BCM Regulatory Alphabet Soup.” RSA Archer Organization, 2012. Web.

      Rothstein, Philip Jan. “Disaster Recovery Testing: Exercising Your Contingency Plan.” Rothstein Associates Inc., 2007. Web.

      The Business Continuity Institute. “The Good Practice Guidelines.” The Business Continuity Institute, 2013. Web.

      The Disaster Recovery Journal. “Disaster Resource Guide.” The Disaster Recovery Journal, 2015. Web.

      The Disaster Recovery Journal. “DR Rules & Regulations.” The Disaster Recovery Journal, 2015. Web.

      The Federal Financial Institution Examination Council (FFIEC). Business Continuity Planning. IT Examination Handbook InfoBase, 2015. Web.

      York, Kyle. “Read Dyn’s Statement on the 10/21/2016 DNS DDoS Attack.” Oracle, 22 Oct. 2016. Web.

      Extend Agile Practices Beyond IT

      • Buy Link or Shortcode: {j2store}175|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
      • Your organization has started to realize benefits from adopting Agile principles and practices. However, these advances are contained within your IT organization.
      • You are seeking to extend Agile development beyond IT into other areas of the organization. You are looking for a coordinated approach aligned to business priorities.

      Our Advice

      Critical Insight

      • Not all lessons from scaling Agile to IT are transferable. IT Agile scaling processes are tailored to IT’s scope, team, and tools, which may not account for diverse attributes within your organization.
      • Control may be necessary for coordination. With increased time-to-value, enforcing consistent cadences, reporting, and communication is a must if teams are not disciplined or lack good governance.
      • Extend Agile in departments tolerant to change. Incrementally roll out Agile in departments where its principles are accepted (e.g. a culture that embraces failures as lessons).

      Impact and Result

      • Complete an assessment of your prior efforts to scale Agile across IT to gauge successful, consistent adoption. Identify the business objectives and the group drivers that are motivating the extension of Agile to the business.
      • Understand the challenges that you may face when extending Agile to business partners. Investigate the root causes of existing issues that can derail your efforts.
      • Ideate solutions to your scaling challenges and envision a target state for your growing Agile environment. Your target state should realize new opportunities to drive more business value and eliminate current activities driving down productivity.
      • Coordinate the implementation and execution of your scaling Agile initiatives with an implementation action plan. This collaborative document will lay out the process, roles, goals, and objectives needed to successfully manage your Agile environment.

      Extend Agile Practices Beyond IT Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should extend Agile practices to improve product delivery, 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. Assess your readiness to scale agile vertically

      Assess your readiness to scale Agile vertically by identifying and mitigating potential Agile maturity gaps remaining after scaling Agile across your IT organization.

      • Extend Agile Practices Beyond IT – Phase 1: Assess Your Readiness to Scale Agile Vertically
      • Agile Maturity Assessment Tool

      2. Establish an enterprise scaled agile framework

      Complete an overview of various scaled Agile models to help you develop your own customized delivery framework.

      • Extend Agile Practices Beyond IT – Phase 2: Establish an Enterprise Scaled Agile Framework
      • Framework Selection Tool

      3. Create your implementation action plan

      Determine the effort and steps required to implement your extended delivery framework.

      • Extend Agile Practices Beyond IT – Phase 3: Create Your Implementation Action Plan
      [infographic]

      Workshop: Extend Agile Practices Beyond 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 Assess Current State of Agile Maturity

      The Purpose

      Assess your readiness to scale Agile vertically.

      Identify and mitigate potential Agile maturity gaps remaining after scaling Agile across your IT organization.

      Key Benefits Achieved

      IT Agile maturity gaps identified and mitigated to ensure successful extension of Agile to the business

      Activities

      1.1 Characterize your Agile implementation using the CLAIM model.

      1.2 Assess the maturity of your Agile teams and organization.

      Outputs

      Maturity gaps identified with mitigation requirements

      2 Establish an Enterprise Scaled Agile Framework

      The Purpose

      Complete a review of scaled Agile models to help you develop your own customized delivery framework.

      Key Benefits Achieved

      A customized Agile delivery framework

      Activities

      2.1 Explore various scaled frameworks.

      2.2 Select an appropriate scaled framework for your enterprise.

      2.3 Define the future state of your team and the communication structure of your functional business group.

      Outputs

      Blended framework delivery model

      Identification of team and communication structure impacts resulting from the new framework

      3 Create Your Implementation Action Plan

      The Purpose

      Create your implementation action plan for the new Agile delivery framework.

      Key Benefits Achieved

      A clearly defined action plan

      Activities

      3.1 Define your value drivers.

      3.2 Brainstorm the initiatives that must be completed to achieve your target state.

      3.3 Estimate the effort of your Agile initiatives.

      3.4 Define your Agile implementation action plan.

      Outputs

      List of target state initiatives

      Estimation of effort to achieve target state

      An implementation action plan

      IT Project Management Lite

      • Buy Link or Shortcode: {j2store}187|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: Project Management Office
      • Parent Category Link: /project-management-office
      • Organizations want reliable project reporting and clear, consistent project management standards, but many are unwilling or unable to allocate time for it.
      • Many IT project managers are given project management responsibilities in addition to other full-time roles – without any formal allocation of time, authority, or training.
      • Most IT project managers and stakeholders actually want clear and consistent standards but resist tools and procedures they believe are too time consuming and inflexible.
      • Standard project management procedures must be “light” enough for project managers to adapt to a wide range of projects without increasing the total time required to manage projects successfully.

      Our Advice

      Critical Insight

      • Most IT project management advice is focused on the largest 10-20% of projects – projects with large enough budgets to allocate time to project management. This leaves most IT projects (and most people who manage IT projects) in limbo between high-risk ad hoc management and high-cost project management best practices.
      • Project management success doesn’t equate to project success. While formal methodologies are a key ingredient in the success of large, complex projects, most IT projects do not require the same degree of rigorous record-keeping and planning.
      • Consistent, timely, and accurate reporting is the “linchpin” in any sustainable project and portfolio management practice.

      Impact and Result

      • Maintain timely and accurate project portfolio reporting with right-sized tools and processes.
      • Establish clear and consistent project management standards that make better use of time already spent managing projects.
      • Enable project managers to manage their projects more successfully with a set of flexible and lightweight tools and templates.

      IT Project Management Lite Research & Tools

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

      1. Assess the value of a minimum-viable PMO strategy

      Perform a measured value assessment for building and managing a minimum-viable PMO.

      • IT Project Management Lite Storyboard

      2. Perform a project and portfolio needs assessment

      Focus on the minimum required to maintain accuracy of portfolio reporting and effectiveness in managing projects.

      • Minimum-Viable PMO Needs Assessment

      3. Establish standards for realistic, accurate, and consistent portfolio reporting

      Emphasize reporting high-level project status as a way to identify and address issues to achieve the best results with the least effort.

      • Minimum-Viable Project and Portfolio Management SOP

      4. Create a standard, right-sized project management toolkit

      Free PMs to focus on actually managing the project while still delivering accurate portfolio metrics.

      • Zero-Allocation Project Management Workbook

      5. Train PMs for zero allocation

      Ensure project manager compliance with the portfolio reporting process by incorporating activities that create value.

      • Zero-Allocation Project Manager Development Plan
      • Zero-Allocation Project Management Survival Guide

      6. Perform a post-implementation assessment

      Evaluate success and identify opportunities for further improvement.

      Infographic

      Workshop: IT Project Management Lite

      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 Preparation

      The Purpose

      Define goals and success criteria.

      Finalize agenda.

      Gather information: update project and resource lists (Info-Tech recommends using the Project Portfolio Workbook).

      Key Benefits Achieved

      More efficiently organized and executed workshop.

      Able to better customize and tailor content to your specific needs.

      Activities

      1.1 Discuss specific pain points with regards to project manager allocations

      1.2 Review project lists, tools and templates, and other documents

      1.3 Map existing strategies to Info-Tech’s framework

      Outputs

      Understanding of where efforts must be focused in workshop

      Assessment of what existing tools and templates may need to be included in zero-allocation workbook

      Revisions that need to be made based on existing strategies

      2 Make the Case and Assess Needs

      The Purpose

      Assess current state (including review of project and resource lists).

      Discuss and analyze SWOT around project and portfolio management.

      Define target state.

      Define standards / SOP / processes for project and portfolio management.

      Key Benefits Achieved

      Gain perspective on how well your processes match up with the amount of time your project managers have for their PM duties.

      Determine the value of the time and effort that your project teams are investing in project management activities.

      Begin to define resource optimized processes for zero-allocation project managers.

      Ensure consistent implementation of processes across your portfolio.

      Establish project discipline and best practices that are grounded in actual project capacity.

      Activities

      2.1 Perform and/or analyze Minimum-Viable PMO Needs Assessment

      2.2 SWOT analysis

      2.3 Identify target allocations for project management activities

      2.4 Begin to define resource optimized processes for zero-allocation project managers

      Outputs

      Current state analysis based on Minimum-Viable PMO Needs Assessment

      Overview of current strengths, weaknesses, opportunities and threats

      Target state analysis based on Minimum-Viable PMO Needs Assessment

      A refined Minimum-Viable Project and Portfolio Management SOP

      3 Establish Strategy

      The Purpose

      Select and customize project and portfolio management toolkit.

      Implement (test/pilot) toolkit and processes.

      Customize project manager training plan.

      Evaluate and refine toolkit and processes as needed.

      Key Benefits Achieved

      Ensure consistent implementation of processes across your portfolio.

      Establish project discipline and best practices that are grounded in actual project capacity.

      A customized training session that will suit the needs of your project managers.

      Activities

      3.1 Customize the Zero-Allocation Toolkit to accommodate the needs of your projects

      3.2 Test toolkit on projects currently underway

      3.3 Tweak project manager training to suit the needs of your team

      Outputs

      Customized Zero-Allocation Project Management Workbook

      A tested and standardized copy of the workbook

      A customized training session for your project managers (to take place on Day 4 of Info-Tech’s workshop)

      4 Train Your Zero-Allocation Project Managers

      The Purpose

      Communicate project and portfolio management SOP to Project Managers.

      Deliver project manager training: standards for portfolio reporting and toolkit.

      Key Benefits Achieved

      Equip project managers to improve their level of discipline and documentation without spending more time in record keeping and task management.

      Execute a successful training session that clearly and succinctly communicates your minimal and resource-optimized processes.

      Activities

      4.1 Project Manager Training, including communication of the processes and standard templates and reports that will be adopted by all project managers

      Outputs

      Educated and disciplined project managers, aware of the required processes for portfolio reporting

      5 Assess Strategy and Next Steps

      The Purpose

      Debrief from the training session.

      Plan for ongoing evaluation and improvement.

      Evaluate and refine toolkit and processes if needed.

      Answer any remaining questions.

      Key Benefits Achieved

      Assess portfolio and project manager performance in light of the strategy implemented.

      Understanding of how to keep living documents like the workbook and SOP up to date.

      Clearly defined next steps.

      Activities

      5.1 Review the customized tools and templates

      5.2 Send relevant documentation to relevant stakeholders

      5.3 Schedule review call

      5.4 Schedule follow-up call with analysts to discuss progress in six months

      Outputs

      Finalized workbook and processes

      Satisfied and informed stakeholders

      Scheduled review call

      Scheduled follow-up call

      Define Service Desk Metrics That Matter

      • Buy Link or Shortcode: {j2store}491|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
      • Consolidate your metrics and assign context and actions to ones currently tracked.
      • Establish tension metrics to see and tell the whole story.
      • Split your metrics for each stakeholder group. Assign proper cadences for measurements as a first step to building an effective dashboard.

      Our Advice

      Critical Insight

      • Identify the metrics that serve a real purpose and eliminate the rest. Establish a formal review process to ensure metrics are still valid, continue to provide the answers needed, and are at a manageable and usable level.

      Impact and Result

      • Tracking goal- and action-based metrics allows you to make meaningful, data-driven decisions for your service desk. You can establish internal benchmarks to set your own baselines.
      • Predefining the audience and cadence of each metric allows you to construct targeted dashboards to aid your metrics analysis.

      Define Service Desk Metrics That Matter Research & Tools

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

      1. Define Service Desk Metrics That Matter Storyboard – A deck that shows you how to look beyond benchmarks and rely on internal metrics to drive success.

      Deciding which service desk metrics to track and how to analyze them can be daunting. Use this deck to narrow down your goal-oriented metrics as a starting point and set your own benchmarks.

      • Define Service Desk Metrics That Matter Storyboard

      2. Service Desk Metrics Workbook – A tool to organize your service desk metrics.

      For each metric, consider adding the relevant overall goal, audience, cadence, and action. Use the audience and cadence of the metric to split your tracked metrics into various dashboards. Your final list of metrics and reports can be added to your service desk SOP.

      • Service Desk Metrics Workbook
      [infographic]

      Further reading

      Define Service Desk Metrics That Matter

      Look beyond benchmarks and rely on internal metrics to drive success.

      Analyst Perspective

      Don’t get paralyzed by benchmarks when establishing metrics

      When establishing a suite of metrics to track, it’s tempting to start with the metrics measured by other organizations. Naturally, benchmarking will enter the conversation. While benchmarking is useful, measuring you organization against others with a lack of context will only highlight your failures. Furthermore, benchmarks will highlight the norm or common practice. It does not necessarily highlight best practice.

      Keeping the limitations of benchmarking in mind, establish your own metrics suite with action-based metrics. Define the audience, cadence, and actions for each metric you track and pair them with business goals. Measure only what you need to.

      Slowly improve your metrics process over time and analyze your environment using your own data as your benchmark.

      Benedict Chang

      Research Analyst, Infrastructure & Operations

      Info-Tech Research Group

      Executive Summary

      Your Challenge

      • Measure the business value provided by the service desk.
      • Consolidate your metrics and assign context and actions to ones currently tracked.
      • Establish tension metrics to see and tell the whole story.
      • Split your metrics for each stakeholder group. Assign proper cadences for measurements as a first step to building an effective dashboard or effective dashboards.

      Common Obstacles

      • Becoming too focused on benchmarks or unidimensional metrics (e.g. cost, first-contact resolution, time to resolve) can lead to misinterpretation of the data and poorly informed actions.
      • Sifting through the many sources of data post hoc can lead to stalling in data analysis or slow reaction times to poor metrics.
      • Dashboards can quickly become cluttered with uninformative metrics, thus reducing the signal-to-noise ratio of meaningful data.

      Info-Tech's Approach

      • Use metrics that drive productive change and improvement. Track only what you need to report on.
      • Ensure each metric aligns with the desired business goal, is action-based, and includes the answers to what, why, how, and who.
      • Establish internal benchmarks by analyzing the trends from your own data to set baselines.
      • Act on the results of your metrics by adjusting targets and measuring success.

      Info-Tech Insight

      Identify the metrics that serve a real purpose and eliminate the rest. Establish a formal review process to ensure metrics are still valid, continue to provide the answers needed, and are at a manageable and usable level.

      Improve your metrics to align IT with strategic business goals

      The right metrics can tell the business how hard IT works and how well they perform.

      • Only 19% of CXOs feel that their organization is effective at measuring the success of IT projects with their current metrics.
      • Implementing the proper metrics can facilitate communication between the business division and IT practice.
      • The proper metrics can help IT know what issues the business has and how the CEO and CIO should tackle them.
      • If the goals above resonate with your organization, our blueprint Take Control of Infrastructure and Operations Metrics will take you through the right steps.

      Current Metrics Suite

      19% Effective

      36% Some Improvement Necessary

      45% Significant Improvement Necessary

      Source: Info-Tech Research Group’s CEO/CIO Alignment Diagnostic, 2019; N=622

      CXOs stress that value is the most critical area for IT to improve in reporting

      • You most likely have to improve your metrics suite by addressing business value.
      • Over 80% of organizations say they need improvement to their business value metrics, with 32% of organizations reporting that significant improvement is needed.
      • Of course, measuring metrics for service desk operations is important, but don’t forget business-oriented metrics such as measuring knowledgebase articles written for shift-left enablement, cost (time and money) of service desk tickets, and overall end-user satisfaction.

      The image shows a bar graph with percentages on the Y-Acis, and the following categories on the X-Axis: Business value metrics; Stakeholder satisfaction reporting; Risk metrics; Technology performance & operating metrics; Cost & Salary metrics; and Ad hoc feedback from executives and staff. Each bar is split into two sections, with the blue section marked a Significant Improvement Necessary, and the purple section labelled Some Improvement necessary. Two sections are highlighted with red circles: Business Value metrics--32% blue; 52% purple; and Technology performance & operating metrics--23% blue and 51% purple.

      Source: Info-Tech Research Group’s CEO/CIO Alignment Diagnostic, 2019; N=622

      Benchmarking used in isolation will not tell the whole story

      Benchmarks can be used as a step in the metrics process

      They can be the first step to reach an end goal, but if benchmarks are observed in isolation, it will only highlight your failures.

      Benchmarking relies on standardized models

      This does not account for all the unique variables that make up an IT organization.

      For example, benchmarks that include cost and revenue may include organizations that prioritize first-call resolution (FCR), but the variables that make up this benchmark model will be quite different within your own organization.

      Info-Tech Insight

      Benchmarks reflect the norm and common practice, not best practice.

      Benchmarks are open to interpretation

      Taking the time to establish proper metrics is often more valuable time spent than going down the benchmark rabbit hole.

      Being above or below the norm is neither a good nor a bad thing.

      Determining what the results mean for you depends on what’s being measured and the unique factors, characteristics, and priorities in your organization.

      If benchmark data is a priority within your IT organization, you may look up organizations like MetricNet, but keep the following in mind:

      Review the collected benchmark data

      See where IT organizations in your industry typically stand in relation to the overall benchmark.

      Assess the gaps

      Large gaps between yourself and the overall benchmark could indicate areas for improvement or celebration. Use the data to focus your analysis, develop deeper self-awareness, and prioritize areas for potential concern.

      Benchmarks are only guidelines

      The benchmark source data may not come from true peers in every sense. Each organization is different, so always explore your unique context when interpreting any findings.

      Rely on internal metrics to measure and improve performance

      Measure internal metrics over time to define goals and drive real improvement

      • Internally measured metrics are more reliable because they provide information about your actual performance over time. This allows for targeted improvements and objective measurements of your milestones.
      • Whether a given metric is the right one for your service desk will depend on several different factors, including:
        • The maturity and capability of your service desk processes
        • The volume of service requests and incidents
        • The complexity of your environment when resolving tickets
        • The degree to which your end users are comfortable with self-service

      Take Info-Tech’s approach to metrics management

      Use metrics that drive productive change and improvement. Track only what you need to report on.

      Ensure each metric aligns with the desired business goal, is action-based, and includes the answers to what, why, how, and who.

      Establish internal benchmarks by analyzing the trends from your own data to set baselines.

      Act on the results of your metrics by adjusting targets and measuring success.

      Define action-based metrics to cut down on analysis paralysis

      Every metric needs to be backed with the following criteria:

      • Defining audience, cadence, goal, and action for each metric allows you to keep your tracked metrics to a minimum while maximizing the value.
      • The audience and cadence of each metric may allow you to define targeted dashboards.

      Audience - Who is this metric tracked for?

      Goal - Why are you tracking this metric? This can be defined along with the CSFs and KPIs.

      Cadence - How often are you going to view, analyze, and action this metric?

      Action - What will you do if this metric spikes, dips, trends up, or trends down?

      Activity 1. Define your critical success factors and key performance indicators

      Critical success factors (CSFs) are high-level goals that help you define the direction of your service desk. Key performance indicators (KPIs) can be treated as the trend of metrics that will indicate that you are moving in the direction of your CSFs. These will help narrow the data you have to track and action (metrics).

      CSFs, or your overall goals, typically revolve around three aspects of the service desk: time spent on tickets, resources spent on tickets, and the quality of service provided.

      1. As a group, brainstorm the CSFs and the KPIs that will help narrow your metrics. Use the Service Desk Metrics Workbook to record the results.
      2. Look at the example to the right as a starting point.

      Example metrics:

      Critical success factor Key performance indicator
      High End-User Satisfaction Increasing CSAT score on transactional surveys
      High end-user satisfaction score
      Proper resolution of tickets
      Low time to resolve
      Low Cost per Ticket Decreasing cost per ticket (due to efficient resolution, FCR, automation, self-service, etc.)
      Improve Access to Self-Service (tangential to improve customer service) High utilization of knowledgebase
      High utilization of portal

      Download the Service Desk Metrics Workbook

      Activity 2. Define action-based metrics that align with your KPIs and CSFs

      1. Now that you have defined your goals, continue to fill the workbook by choosing metrics that align with those goals.
      2. Use the chart below as a guide. For every metric, define the cadence of measurement, audience of the metric, and action associated with the metric. There may be multiple metrics for each KPI.
      3. If you find you are unable to define the cadence, audience, or action associated with a metric, you may not need to track the metric in the first place. Alternatively, if you find that you may action a metric in the future, you can decide to start gathering data now.

      Example metrics:

      Critical success factor Key performance indicator Metric Cadence Audience Action
      High End-User Satisfaction Increasing CSAT score on transactional surveys Monthly average of ticket satisfaction scores Monthly Management Action low scores immediately, view long-term trends
      High end-user satisfaction score Average end-user satisfaction score from annual survey Annually IT Leadership View IT satisfaction trends to align IT with business direction
      Proper resolution of tickets Number of tickets reopened Weekly Service Desk Technicians Action reopened tickets, look for training opportunities
      SLA breach rate Daily Service Desk Technicians Action reopened tickets, look for training opportunities
      Low time to resolve Average TTR (incidents) Weekly Management Look for trends to monitor resources
      Average TTR by priority Weekly Management Look for TTR solve rates to align with SLA
      Average TTR by tier Weekly Management Look for improperly escalated tickets or shift-left opportunities

      Download the Service Desk Metrics Workbook

      Activity 3. Define the data ownership, metric viability, and dashboards

      1. For each metric, define where the data is housed. Ideally, the data is directly in the ticketing tool or ITSM tool. This will make it easy to pull and analyze.
      2. Determine how difficult the metric will be to pull or track. If the effort is high, decide if the value of tracking the metric is worth the hassle of gathering it.
      3. Lastly, for each metric, use the cadence and audience to place the metric in a reporting dashboard. This will help divide your metrics and make them easier to report and action.
      4. You may use the output of this exercise to add your tracked metrics to your service desk SOP.
      5. A full suite of metrics can be found in our Infrastructure & Operations Metrics Library in the Take Control of Infrastructure Metrics Storyboard. The metrics have been categorized by low, medium, and advanced capabilities for you.

      Example metrics:

      Metric Who Owns the Data? Efforts to Track? Dashboards
      Monthly average of ticket satisfaction scores Service Desk Low Monthly Management Meeting
      Average end-user satisfaction score Service Desk Low Leadership Meeting
      Number of tickets reopened Service Desk Low Weekly Technician Standup
      SLA breach rate Service Desk Low Daily Technician Standup
      Average TTR (incidents) Service Desk Low Weekly Technician Standup
      Average TTR by priority Service Desk Low Weekly Technician Standup
      Average TTR by tier Service Desk Low Weekly Technician Standup
      Average TTR (SRs) Service Desk Low Weekly Technician Standup
      Number of tickets reopened Service Desk Low Daily Technician Standup

      Download the Service Desk Metrics Workbook

      Keep the following considerations in mind when defining which metrics matter

      Keep the customer in mind

      Metrics are typically focused on transactional efficiency and process effectiveness and not what was achieved against the customers’ need and satisfaction.

      Understand the relationships between performance and metrics management to provide the end-to-end service delivery picture you are aiming to achieve.

      Don’t settle for tool defaults

      ITSM solutions offer an abundance of metrics to choose from. The most common ones are typically built into the reporting modules of the tool suite.

      Do not start tracking everything. Choose metrics that are specifically aligned to your organization’s desired business outcomes.

      Establish tension metrics to achieve balance

      Don’t ignore the correlation and context between the suites of metrics chosen and how one interacts and affects the other.

      Measuring metrics in isolation may lead to an incomplete picture or undesired technician behavior. Tension metrics help complete the picture and lead to proper actions.

      Adjust those targets

      An arbitrary target on a metric that is consistently met month over month is useless. Each metric should inform the overall performance by combining capable service level management and customer experience programs to prove the value IT is providing to the organization.

      Related Info-Tech Research

      Standardize the Service Desk

      This project will help you build and improve essential service desk processes, including incident management, request fulfillment, and knowledge management, to create a sustainable service desk.

      Take Control of Infrastructure and Operations Metrics

      Make faster decisions and improve service delivery by using the right metrics for the job.

      Analyze Your Service Desk Ticket Data

      Take a data-driven approach to service desk optimization.

      IT Diagnostics: Build a Data-Driven IT Strategy

      Our data-driven programs ask business and IT stakeholders the right questions to ensure you have the inputs necessary to build an effective IT strategy.

      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

      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.

      Prepare for Post-Quantum Cryptography

      • Buy Link or Shortcode: {j2store}268|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 Processes & Operations
      • Parent Category Link: /security-processes-and-operations
      • Fault-tolerant quantum computers, capable of breaking existing encryption algorithms and cryptographic systems, are widely expected to be available sooner than originally projected.
      • Data considered secure today may already be at risk due to the threat of harvest-now-decrypt-later schemes.
      • Many current security controls will be completely useless, including today's strongest encryption techniques.

      Our Advice

      Critical Insight

      The advent of quantum computing is closer than you think: some nations have already demonstrated capability with the potential to break current asymmetric-key encryption. Traditional encryption methods will no longer provide sufficient protection. You need to act now to begin your transformation to quantum-resistant encryption.

      Impact and Result

      • Developing quantum-resistant cryptography capabilities is crucial to maintaining data security and integrity for critical applications.
      • Organizations need to act now to begin their transformation to quantum-resistant encryption.
      • Data security (especially for sensitive data) should be an organization’s top priority. Organizations with particularly critical information need to be on top of this quantum movement.

      Prepare for Post-Quantum Cryptography Research & Tools

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

      1. Prepare for Post-Quantum Cryptography Storyboard – Research to help organizations to prepare and implement quantum-resistance cryptography solutions.

      Developing quantum-resistant cryptography capabilities is crucial to maintaining data security and integrity for critical applications. Organizations need to act now to begin their transformation to quantum-resistant encryption.

      • Prepare for Post-Quantum Cryptography Storyboard
      [infographic]

      Further reading

      Prepare for Post-Quantum Cryptography

      It is closer than you think, and you need to act now.

      Analyst Perspective

      It is closer than you think, and you need to act now.

      The quantum realm presents itself as a peculiar and captivating domain, shedding light on enigmas within our world while pushing the boundaries of computational capabilities. The widespread availability of quantum computers is expected to occur sooner than anticipated. This emerging technology holds the potential to tackle valuable problems that even the most powerful classical supercomputers will never be able to solve. Quantum computers possess the ability to operate millions of times faster than their current counterparts.

      As we venture further into the era of quantum mechanics, organizations relying on encryption must contemplate a future where these methods no longer suffice as effective safeguards. The astounding speed and power of quantum machines have the potential to render many existing security measures utterly ineffective, including the most robust encryption techniques used today. To illustrate, a task that currently takes ten years to crack through a brute force attack could be accomplished by a quantum computer in under five minutes.

      Amid this transition into a quantum future, the utmost priority for organizations remains data security, particularly safeguarding sensitive information. Organizations must proactively prepare for the development of countermeasures and essential resilience measures to attain a state of being "quantum safe."

      This is a picture of Alan Tang

      Alan Tang
      Principal Research Director, Security and Privacy
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      • Anticipated advancements in fault-tolerant quantum computers, surpassing existing encryption algorithms and cryptographic systems, are expected to materialize sooner than previously projected. The timeframe for their availability is diminishing daily.
      • Data that is presently deemed secure faces potential vulnerability due to the emergence of harvest-now-decrypt-later strategies.
      • Numerous contemporary security controls, including the most robust encryption techniques, have become obsolete and offer little efficacy.

      Common Obstacles

      • The complexity involved makes it challenging for organizations to incorporate quantum-resistant cryptography into their current IT infrastructure.
      • The endeavor of transitioning to quantum-resilient cryptography demands significant effort and time, with the specific requirements varying for each organization.
      • A lack of comprehensive understanding regarding the cryptographic technologies employed in existing IT systems poses difficulties in identifying and prioritizing systems for upgrading to post-quantum cryptography.

      Info-Tech's Approach

      • The development of quantum-resistant cryptography capabilities is essential for safeguarding the security and integrity of critical applications.
      • Organizations must proactively initiate their transition toward quantum-resistant encryption to ensure data protection.
      • Ensuring the security of corporate data assets should be of utmost importance for organizations, with special emphasis on those possessing highly critical information in light of the advancements in quantum technology.

      Info-Tech Insight

      The advent of quantum computing (QC) is closer than you think: some nations have demonstrated capability with the potential to break current asymmetric-key encryption. Traditional encryption methods will no longer be sufficient as a means of protection. You need to act now to begin your transformation to quantum-resistant encryption.

      Evolvement of QC theory and technologies

      1900-1975

      1976-1997

      1998-2018

      2019-Now

      1. 1900: Max Planck – The energy of a particle is proportional to its frequency: E = hv, where h is a relational constant.
      2. 1926: Erwin Schrödinger – Since electrons can affect each other's states, their energies change in both time and space. The total energy of a particle is expressed as a probability function.
      1. 1976: Physicist Roman Stanisław Ingarden publishes the paper "Quantum Information Theory."
      2. 1980: Paul Benioff describes the first quantum mechanical model of a computer.
      3. 1994: Peter Shor publishes Shor's algorithm.
      1. 1998: A working 2-qubit NMR quantum computer is used to solve Deutsch's problem by Jonathan A. Jones and Michele Mosca at Oxford University.
      2. 2003: DARPA Quantum Network becomes fully operational.
      3. 2011: D-Wave claims to have developed the first commercially available quantum computer, D-Wave One.
      4. 2018: the National Quantum Initiative Act was signed into law by President Donald Trump.
      1. 2019: A paper by Google's quantum computer research team was briefly available, claiming the project has reached quantum supremacy.
      2. 2020: Chinese researchers claim to have achieved quantum supremacy, using a photonic peak 76-qubit system known as Jiuzhang.
      3. 2021: Chinese researchers reported that they have built the world's largest integrated quantum communication network.
      4. 2022: The Quantinuum System Model H1-2 doubled its performance claiming to be the first commercial quantum computer to pass quantum volume 4096.

      Info-Tech Insight

      The advent of QC will significantly change our perception of computing and have a crucial impact on the way we protect our digital economy using encryption. The technology's applicability is no longer a theory but a reality to be understood, strategized about, and planned for.

      Fundamental physical principles and business use cases

      Unlike conventional computers that rely on bits, quantum computers use quantum bits or qubits. QC technology surpasses the limitations of current processing powers. By leveraging the properties of superposition, interference, and entanglement, quantum computers have the capacity to simultaneously process millions of operations, thereby surpassing the capabilities of today's most advanced supercomputers.

      A 2021 Hyperion Research survey of over 400 key decision makers in North America, Europe, South Korea, and Japan showed nearly 70% of companies have some form of in-house QC program.

      Three fundamental QC physical principles

      1. Superposition
      2. Interference
      3. Entanglement

      This is an image of two headings, Optimization; and Simulation. there are five points under each heading, with an arrow above pointing left to right, labeled Qbit Count.

      Info-Tech Insight

      Organizations need to reap the substantial benefits of QC's power, while simultaneously shielding against the same technologies when used by cyber adversaries.

      Percentage of Surveyed Companies That Have QC Programs

      • 31% Have some form of in-house QC program
      • 69% Have no QC program

      Early adopters and business value

      QC early adopters see the promise of QC for a wide range of computational workloads, including machine learning applications, finance-oriented optimization, and logistics/supply chain management.

      This is an image of the Early Adopters, and the business value drivers.

      Info-Tech Insight

      Experienced attackers are likely to be the early adopters of quantum-enabled cryptographic solutions, harnessing the power of QC to exploit vulnerabilities in today's encryption methods. The risks are particularly high for industries that rely on critical infrastructure.

      The need of quantum-safe solution is immediate

      Critical components of classical cryptography will be at risk, potentially leading to the exposure of confidential and sensitive information to the general public. Business, technology, and security leaders are confronted with an immediate imperative to formulate a quantum-safe strategy and establish a roadmap without delay.

      Case Study – Google, 2019

      In 2019, Google claimed that "Our Sycamore processor takes about 200 seconds to sample one instance of a quantum circuit a million times—our benchmarks currently indicate that the equivalent task for a state-of-the-art classical supercomputer would take approximately 10,000 years."
      Source: Nature, 2019

      Why You Should Start Preparation Now

      • The complexity with integrating QC technology into existing IT infrastructure.
      • The effort to upgrade to quantum-resilient cryptography will be significant.
      • The amount of time remaining will decrease every day.

      Case Study – Development in China, 2020

      On December 3, 2020, a team of Chinese researchers claim to have achieved quantum supremacy, using a photonic peak 76-qubit system (43 average) known as Jiuzhang, which performed calculations at 100 trillion times the speed of classical supercomputers.
      Source: science.org, 2020

      Info-Tech Insight

      The emergence of QC brings forth cybersecurity threats. It is an opportunity to regroup, reassess, and revamp our approaches to cybersecurity.

      Security threats posed by QC

      Quantum computers have reached a level of advancement where even highly intricate calculations, such as factoring large numbers into their primes, which serve as the foundation for RSA encryption and other algorithms, can be solved within minutes.

      Threat to data confidentiality

      QC could lead to unauthorized decryption of confidential data in the future. Data confidentiality breaches also impact improperly disposed encrypted storage media.

      Threat to authentication protocols and digital governance

      A recovered private key, which is derived from a public key, can be used through remote control to fraudulently authenticate a critical system.

      Threat to data integrity

      Cybercriminals can use QC technology to recover private keys and manipulate digital documents and their digital signatures.

      Example:

      Consider RSA-2048, a widely used public-key cryptosystem that facilitates secure data transmission. In a 2021 survey, a majority of leading authorities believed that RSA-2048 could be cracked by quantum computers within a mere 24 hours.
      Source: Quantum-Readiness Working Group, 2022

      Info-Tech Insight

      The development of quantum-safe cryptography capabilities is of utmost importance in ensuring the security and integrity of critical applications' data.

      US Quantum Computing Cybersecurity Preparedness Act

      The US Congress considers cryptography essential for the national security of the US and the functioning of the US economy. The Quantum Computing Cybersecurity Preparedness Act was introduced on April 18, 2022, and became a public law (No: 117-260) on December 21, 2022.

      Purpose

      The purpose of this Act is to encourage the migration of Federal Government information technology systems to quantum-resistant cryptography, and for other purposes.

      Scope and Exemption

      • Scope: Systems of government agencies.
      • Exemption: This Act shall not apply to any national security system.

      Main Obligations

      Responsibilities

      Requirements
      Inventory Establishment Not later than 180 days after the date of enactment of this Act, the Director of OMB, shall issue guidance on the migration of information technology to post-quantum cryptography.
      Agency Reports "Not later than 1 year after the date of enactment of this Act, and on an ongoing basis thereafter, the head of each agency shall provide to the Director of OMB, the Director of CISA, and the National Cyber Director— (1) the inventory described in subsection (a)(1); and (2) any other information required to be reported under subsection (a)(1)(C)."
      Migration and Assessment "Not later than 1 year after the date on which the Director of NIST has issued post-quantum cryptography standards, the Director of OMB shall issue guidance requiring each agency to— (1) prioritize information technology described under subsection (a)(2)(A) for migration to post-quantum cryptography; and (2) develop a plan to migrate information technology of the agency to post-quantum cryptography consistent with the prioritization under paragraph (1)."

      "It is the sense of Congress that (1) a strategy for the migration of information technology of the Federal Government to post-quantum cryptography is needed; and (2) the government wide and industry-wide approach to post- quantum cryptography should prioritize developing applications, hardware intellectual property, and software that can be easily updated to support cryptographic agility." – Quantum Computing Cybersecurity Preparedness Act

      The development of post-quantum encryption

      Since 2016, the National Institute of Standards and Technology (NIST) has been actively engaged in the development of post-quantum encryption standards. The objective is to identify and establish standardized cryptographic algorithms that can withstand attacks from quantum computers.

      NIST QC Initiative Key Milestones

      Date Development
      Dec. 20, 2016 Round 1 call for proposals: Announcing request for nominations for public-key post-quantum cryptographic algorithms
      Nov. 30, 2017 Deadline for submissions – 82 submissions received
      Dec. 21, 2017 Round 1 algorithms announced (69 submissions accepted as "complete and proper")
      Jan. 30, 2019 Second round candidates announced (26 algorithms)

      July 22, 2020

      Third round candidates announced (7 finalists and 8 alternates)

      July 5, 2022

      Announcement of candidates to be standardized and fourth round candidates
      2022/2024 (Plan) Draft standards available

      Four Selected Candidates to be Standardized

      CRYSTALS – Kyber

      CRYSTALS – Dilithium

      FALCON

      SPHINCS+

      NIST recommends two primary algorithms to be implemented for most use cases: CRYSTALS-KYBER (key-establishment) and CRYSTALS-Dilithium (digital signatures). In addition, the signature schemes FALCON and SPHINCS+ will also be standardized.

      Info-Tech Insight

      There is no need to wait for formal NIST PQC standards selection to begin your post-quantum mitigation project. It is advisable to undertake the necessary steps and allocate resources in phases that can be accomplished prior to the finalization of the standards.

      Prepare for post-quantum cryptography

      The advent of QC is closer than you think: some nations have demonstrated capability with the potential to break current asymmetric-key encryption. Traditional encryption methods will no longer be sufficient as a means of protection. You need to act now to begin your transformation to quantum-resistant encryption.

      This is an infographic showing the three steps: Threat is Imminent; Risks are Profound; and Take Acton Now.

      Insight summary

      Overarching Insight

      The advent of QC is closer than you think as some nations have demonstrated capability with the potential to break current asymmetric-key encryption. Traditional encryption methods will no longer be sufficient as a means of protection. You need to act now to begin your transformation to quantum-resistant encryption.

      Business Impact Is High

      The advent of QC will significantly change our perception of computing and have a crucial impact on the way we protect our digital economy using encryption. The technology's applicability is no longer a theory but a reality to be understood, strategized about, and planned for.

      It's a Collaborative Effort

      Embedding quantum resistance into systems during the process of modernization requires collaboration beyond the scope of a Chief Information Security Officer (CISO) alone. It is a strategic endeavor shaped by leaders throughout the organization, as well as external partners. This comprehensive approach involves the collective input and collaboration of stakeholders from various areas of expertise within and outside the organization.

      Leverage Industry Standards

      There is no need to wait for formal NIST PQC standards selection to begin your post-quantum mitigation project. It is advisable to undertake the necessary steps and allocate resources in phases that can be accomplished prior to the finalization of the standards.

      Take a Holistic Approach

      The advent of QC poses threats to cybersecurity. It's a time to regroup, reassess, and revamp.

      Blueprint benefits

      IT Benefits

      Business Benefits

      • This blueprint will help organizations to discover and then prioritize the systems to be upgraded to post-quantum cryptography.
      • This blueprint will enable organizations to integrate quantum-resistant cryptography into existing IT infrastructure.
      • Developing quantum-resistant cryptography capabilities is crucial to maintaining data security and integrity for critical applications.
      • This blueprint will help organizations to save effort and time needed upgrade to quantum-resilient cryptography.
      • Organizations will reap the substantial benefits of QC's power, while simultaneously shielding against the same technologies when used by cyber adversaries.
      • Avoid reputation and brand image by preventing data breach and leakage.
      • This blueprint will empower organizations to protect corporate data assets in the post-quantum era.
      • Be compliant with various security and privacy laws and regulations.

      Info-Tech Project Value

      Time, value, and resources saved to obtain buy-in from senior leadership team using our research material:

      1 FTEs*10 days*$100,000/year = $6,000

      Time, value, and resources saved to implement quantum-resistant cryptography using our research guidance:

      2 FTEs* 30 days*$100,000/year = $24,000

      Estimated cost and time savings from this blueprint:

      $6,000 + $24,000 =$30,000

      Get prepared for a post-quantum world

      The advent of sufficiently powerful quantum computers poses a risk of compromising or weakening traditional forms of asymmetric and symmetric cryptography. To safeguard data security and integrity for critical applications, it is imperative to undertake substantial efforts in migrating an organization's cryptographic systems to post-quantum encryption. The development of quantum-safe cryptography capabilities is crucial in this regard.

      Phase 1 - Prepare

      • Obtain buy-in from leadership team.
      • Educate your workforce about the upcoming transition.
      • Create defined projects to reduce risks and improve crypto-agility.

      Phase 2 - Discover

      • Determine the extent of your exposed data, systems, and applications.
      • Establish an inventory of classical cryptographic use cases.

      Phase 3 - Assess

      • Assess the security and data protection risks posed by QC.
      • Assess the readiness of transforming existing classical cryptography to quantum-resilience solutions.

      Phase 4 - Prioritize

      • Prioritize transformation plan based on criteria such as business impact, near-term technical feasibility, and effort, etc.
      • Establish a roadmap.

      Phase 5 - Mitigate

      • Implement post-quantum mitigations.
      • Decommissioning old technology that will become unsupported upon publication of the new standard.
      • Validating and testing products that incorporate the new standard.

      Phase 1 – Prepare: Protect data assets in the post-quantum era

      The rise of sufficiently powerful quantum computers has the potential to compromise or weaken conventional asymmetric and symmetric cryptography methods. In anticipation of a quantum-safe future, it is essential to prioritize crypto-agility. Consequently, organizations should undertake specific tasks both presently and in the future to adequately prepare for forthcoming quantum threats and the accompanying transformations.

      Quantum-resistance preparations must address two different needs:

      Reinforce digital transformation initiatives

      To thrive in the digital landscape, organizations must strengthen their digital transformation initiatives by embracing emerging technologies and novel business practices. The transition to quantum-safe encryption presents a unique opportunity for transformation, allowing the integration of these capabilities to evolve business transactions and relationships in innovative ways.

      Protect data assets in the post-quantum era

      Organizations should prioritize supporting remediation efforts aimed at ensuring the quantum safety of existing data assets and services. The implementation of crypto-agility enables organizations to respond promptly to cryptographic vulnerabilities and adapt to future changes in cryptographic standards. This proactive approach is crucial, as the need for quantum-safe measures existed even before the complexities posed by QC emerged.

      Preparation for the post-quantum world has been recommended by the US government and other national bodies since 2016.

      In 2016, NIST, the National Security Agency (NSA), and Central Security Service stated in their Commercial National Security Algorithm Suite and QC FAQ: "NSA believes the time is now right [to start preparing for the post-quantum world] — consistent with advances in quantum computing."
      Source: Cloud Security Alliance, 2021

      Phase 1 – Prepare: Key tasks

      Preparing for quantum-resistant cryptography goes beyond simply acquiring knowledge and conducting experiments in QC. It is vital for senior management to receive comprehensive guidance on the challenges, risks, and potential mitigations associated with the post-quantum landscape. Quantum and post-quantum education should be tailored to individuals based on their specific roles and the impact of post-quantum mitigations on their responsibilities. This customized approach ensures that individuals are equipped with the necessary knowledge and skills relevant to their respective roles.

      Leadership Buy-In

      • Get senior management commitment to post-quantum project.
      • Determine the extent of exposed data, systems, and applications.
      • Identify near-term, achievable cryptographic maturity goals, creating defined projects to reduce risks and improve crypto-agility.

      Roles and Responsibilities

      • The ownership should be clearly defined regarding the quantum-resistant cryptography program.
      • This should be a cross-functional team within which members represent various business units.

      Awareness and Education

      • Senior management needs to understand the strategic threat to the organization and needs to adequately address the cybersecurity risk in a timely fashion.
      • Educate your workforce about the upcoming transition. All training and education should seek to achieve awareness of the following items with the appropriate stakeholders.

      Info-Tech Insight

      Embedding quantum resistance into systems during the process of modernization requires collaboration beyond the scope of a CISO alone. It is a strategic endeavor shaped by leaders throughout the organization, as well as external partners. This comprehensive approach involves the collective input and collaboration of stakeholders from various areas of expertise within and outside the organization.

      Phase 2 – Discover: Establish a data protection inventory

      During the discovery phase, it is crucial to locate and identify any critical data and devices that may require post-quantum protection. This step enables organizations to understand the algorithms in use and their specific locations. By conducting this thorough assessment, organizations gain valuable insights into their existing infrastructure and cryptographic systems, facilitating the implementation of appropriate post-quantum security measures.

      Inventory Core Components

      1. Description of devices and/or data
      2. Location of all sensitive data and devices
      3. Criticality of the data
      4. How long the data or devices need to be protected
      5. Effective cryptography in use and cryptographic type
      6. Data protection systems currently in place
      7. Current key size and maximum key size
      8. Vendor support timeline
      9. Post-quantum protection readiness

      Key Things to Consider

      • The accuracy and thoroughness of the discovery phase are critical factors that contribute to the success of a post-quantum project.
      • It is advisable to conduct this discovery phase comprehensively across all aspects, not solely limited to public-key algorithms.
      • Performing a data protection inventory can be a time-consuming and challenging phase of the project. Breaking it down into smaller subtasks can help facilitate the process.
      • Identifying all information can be particularly challenging since data is typically scattered throughout an organization. One approach to begin this identification process is by determining the inputs and outputs of data for each department and team within the organization.
      • To ensure accountability and effectiveness, it is recommended to assign a designated individual as the ultimate owner of the data protection inventory task. This person should have the necessary responsibilities and authority to successfully accomplish the task.

      Phase 3 – Assess: The workflow

      Quantum risk assessment entails evaluating the potential consequences of QC on existing security measures and devising strategies to mitigate these risks. This process involves analyzing the susceptibility of current systems to attacks by quantum computers and identifying robust security measures that can withstand QC threats.

      Risk Assessment Workflow

      This is an image of the Risk Assessment Workflow

      By identifying the security gaps that will arise with the advent of QC, organizations can gain insight into the substantial vulnerabilities that core business operations will face when QC becomes a prevalent reality. This proactive understanding enables organizations to prepare and implement appropriate measures to address these vulnerabilities in a timely manner.

      Phase 4 – Prioritize: Balance business value, security risks, and effort

      Organizations need to prioritize the mitigation initiatives based on various factors such as business value, level of security risk, and the effort needed to implement the mitigation controls. In the diagram below, the size of the circle reflects the degree of effort. The bigger the size, the more effort is needed.

      This is an image of a chart where the X axis represents Security Risk level, and the Y axis is Business Value.

      QC Adopters Anticipated Annual Budgets

      This is an image of a bar graph showing the Anticipated Annual Budgets for QC Adopters.
      Source: Hyperion Research, 2022

      Hyperion's survey found that the range of expected budget varies widely.

      • The most selected option, albeit by only 38% of respondents, was US$5 million to US$15 million.
      • About one-third of respondents foresaw annual budgets that exceeded US$15 million, and one-fifth expected budgets to exceed US$25 million.

      Build your risk mitigation roadmap

      2 hours

      1. Review the quantum-resistance initiatives generated in Phase 3 – Assessment.
      2. With input from all stakeholders, prioritize the initiatives based on business value, security risks, and effort using the 2x2 grid.
      3. Review the position of all initiatives and adjust accordingly considering other factors such as dependency, etc.
      4. Place prioritized initiatives to a wave chart.
      5. Assign ownership and target timeline for each initiative.

      This is an image the Security Risk Vs. Business value graph, above an image showing Initiatives Numbered 1-7, divided into Wave 1; Wave 2; and Wave 3.

      Input

      • Data protection inventory created in phase 2
      • Risk assessment produced in phase 3
      • Business unit leaders' and champions' understanding (high-level) of challenges posed by QC

      Output

      • Prioritization of quantum-resistance initiatives

      Materials

      • Whiteboard/flip charts
      • Sticky notes
      • Pen/whiteboard markers

      Participants

      • Quantum-resistance program owner
      • Senior leadership team
      • Business unit heads
      • Chief security officer
      • Chief privacy officer
      • Chief information officer
      • Representatives from legal, risk, and governance

      Phase 5 – Mitigate: Implement quantum-resistant encryption solutions

      To safeguard against cybersecurity risks and threats posed by powerful quantum computers, organizations need to adopt a robust defense-in-depth approach. This entails implementing a combination of well-defined policies, effective technical defenses, and comprehensive education initiatives. Organizations may need to consider implementing new cryptographic algorithms or upgrading existing protocols to incorporate post-quantum encryption methods. The selection and deployment of these measures should be cost-justified and tailored to meet the specific needs and risk profiles of each organization.

      Governance

      Implement solid governance mechanisms to promote visibility and to help ensure consistency

      • Update policies and documents
      • Update existing acceptable cryptography standards
      • Update security and privacy audit programs

      Industry Standards

      • Stay up to date with newly approved standards
      • Leverage industry standards (i.e. NIST's post-quantum cryptography) and test the new quantum-safe cryptographic algorithms

      Technical Mitigations

      Each type of quantum threat can be mitigated using one or more known defenses.

      • Physical isolation
      • Replacing quantum-susceptible cryptography with quantum-resistant cryptography
      • Using QKD
      • Using quantum random number generators
      • Increasing symmetric key sizes
      • Using hybrid solutions
      • Using quantum-enabled defenses

      Vendor Management

      • Work with key vendors on a common approach to quantum-safe governance
      • Assess vendors for possible inclusion in your organization's roadmap
      • Create acquisition policies regarding quantum-safe cryptography

      Research Contributors and Experts

      This is a picture of Adib Ghubril

      Adib Ghubril
      Executive Advisor, Executive Services
      Info-Tech Research Group

      This is a picture of Erik Avakian

      Erik Avakian
      Technical Counselor
      Info-Tech Research Group

      This is a picture of Alaisdar Graham

      Alaisdar Graham
      Executive Counselor
      Info-Tech Research Group

      This is a picture of Carlos Rivera

      Carlos Rivera
      Principal Research Advisor
      Info-Tech Research Group

      This is a picture of Hendra Hendrawan

      Hendra Hendrawan
      Technical Counselor
      Info-Tech Research Group

      This is a picture of Fritz Jean-Louis

      Fritz Jean-Louis
      Principal Cybersecurity Advisor
      Info-Tech Research Group

      Bibliography

      117th Congress (2021-2022). H.R.7535 - Quantum Computing Cybersecurity Preparedness Act. congress.gov, 21 Dec 2022.
      Arute, Frank, et al. Quantum supremacy using a programmable superconducting processor. Nature, 23 Oct 2019.
      Bernhardt, Chris. Quantum Computing for Everyone. The MIT Press, 2019.
      Bob Sorensen. Quantum Computing Early Adopters: Strong Prospects For Future QC Use Case Impact. Hyperion Research, Nov 2022.
      Candelon, François, et al. The U.S., China, and Europe are ramping up a quantum computing arms race. Here's what they'll need to do to win. Fortune, 2 Sept 2022.
      Curioni, Alessandro. How quantum-safe cryptography will ensure a secure computing future. World Economic Forum, 6 July 2022.
      Davis, Mel. Toxic Substance Exposure Requires Record Retention for 30 Years. Alert presented by CalChamber, 18 Feb 2022.
      Eddins, Andrew, et al. Doubling the size of quantum simulators by entanglement forging. arXiv, 22 April 2021.
      Gambetta, Jay. Expanding the IBM Quantum roadmap to anticipate the future of quantum-centric supercomputing. IBM Research Blog, 10 May 2022.
      Golden, Deborah, et al. Solutions for navigating uncertainty and achieving resilience in the quantum era. Deloitte, 2023.
      Grimes, Roger, et al. Practical Preparations for the Post-Quantum World. Cloud Security Alliance, 19 Oct 2021.
      Harishankar, Ray, et al. Security in the quantum computing era. IBM Institute for Business Value, 2023.
      Hayat, Zia. Digital trust: How to unleash the trillion-dollar opportunity for our global economy. World Economic Forum, 17 Aug 2022.
      Mateen, Abdul. What is post-quantum cryptography? Educative, 2023.
      Moody, Dustin. Let's Get Ready to Rumble—The NIST PQC 'Competition.' NIST, 11 Oct 2022.
      Mosca, Michele, Dr. and Dr. Marco Piani. 2021 Quantum Threat Timeline Report. Global Risk Institute, 24 Jan 2022.
      Muppidi, Sridhar and Walid Rjaibi. Transitioning to Quantum-Safe Encryption. Security Intelligence, 8 Dec 2022.
      Payraudeau, Jean-Stéphane, et al. Digital acceleration: Top technologies driving growth in a time of crisis. IBM Institute for Business Value, Nov 2020.
      Quantum-Readiness Working Group (QRWG). Canadian National Quantum-Readiness- Best Practices and Guidelines. Canadian Forum for Digital Infrastructure Resilience (CFDIR), 17 June 2022.
      Rotman, David. We're not prepared for the end of Moore's Law. MIT Technology Review, 24 Feb 2020.
      Saidi, Susan. Calculating a computing revolution. Roland Berger, 2018.
      Shorter., Ted. Why Companies Must Act Now To Prepare For Post-Quantum Cryptography. Forbes.com, 11 Feb 2022.
      Sieger, Lucy, et al. The Quantum Decade, Third edition. IBM, 2022.
      Sorensen, Bob. Broad Interest in Quantum Computing as a Driver of Commercial Success. Hyperion Research, 17 Nov 2021.
      Wise, Jason. How Much Data is Created Every Day in 2022? Earthweb, 22 Sept 2022.
      Wright, Lawrence. The Plague Year. The New Yorker, 28 Dec 2020.
      Yan, Bao, et al. Factoring integers with sublinear resources on a superconducting quantum processor. arXiv, 23 Dec 2022.
      Zhong, Han-Sen, et al. Quantum computational advantage using photons. science.org, 3 Dec 2020.

      Build Your Enterprise Innovation Program

      • Buy Link or Shortcode: {j2store}104|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $100,000 Average $ Saved
      • member rating average days saved: 10 Average Days Saved
      • Parent Category Name: Innovation
      • Parent Category Link: /innovation
      • You don’t know where to start when it comes to building an innovation program for your organization.
      • You need to create a culture of innovation in your business, department, or team.
      • Past innovation efforts have been met with resistance and cynicism.
      • You don’t know what processes you need to support business-led innovation.

      Our Advice

      Critical Insight

      Innovation is about people, not ideas or processes. Innovation does not require a formal process, a dedicated innovation team, or a large budget; the most important success factor for innovation is culture. Companies that facilitate innovative behaviors like growth mindset, collaboration, and taking smart risks are most likely to see the benefits of innovation.

      Impact and Result

      • Outperform your peers by 30% by adopting an innovative approach to your business.
      • Move quickly to launch your innovation practice and beat the competition.
      • Develop the skills and capabilities you need to sustain innovation over the long term.

      Build Your Enterprise Innovation Program Research & Tools

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

      1. Build Your Enterprise Innovation Program Storyboard – A step-by-step process to create the innovation culture, processes, and tools you need for business-led innovation.

      This storyboard includes three phases and nine activities that will help you define your purpose, align your people, and build your practice.

      • Build Your Enterprise Innovation Program – Phases 1-3

      2. Innovation Program Template – An executive communication deck summarizing the outputs from this research.

      Use this template in conjunction with the activities in the main storyboard to create and communicate your innovation program. This template uses sample data from a fictional retailer, Acme Corp, to illustrate an ideal innovation program summary.

      • Innovation Program Template

      3. Job Description – Chief Innovation Officer

      This job description can be used to hire your Chief Innovation Officer. There are many other job descriptions available on the Info-Tech website and referenced within the storyboard.

      • Chief Innovation Officer

      4. Innovation Ideation Session Template – Use this template to facilitate innovation sessions with the business.

      Use this framework to facilitate an ideation session with members of the business. Instructions for how to customize the information and facilitate each section is included within the deck.

      • Innovation Ideation Session Template

      5. Initiative Prioritization Workbook – Use this spreadsheet template to easily and transparently prioritize initiatives for pilot.

      This spreadsheet provides an analytical and transparent method to prioritize initiatives based on weighted criteria relevant to your business.

      • Initiative Prioritization Workbook

      Infographic

      Workshop: Build Your Enterprise Innovation 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 Ambitions

      The Purpose

      Define your innovation ambitions.

      Key Benefits Achieved

      Gain a better understanding of why you are innovating and what your organization will gain from an innovation program.

      Activities

      1.1 Understand your innovation mandate.

      1.2 Define your innovation ambitions.

      1.3 Determine value proposition & metrics.

      Outputs

      Complete the "Our purpose" section of the Innovation Program Template

      Complete "Vision and guiding principles" section

      Complete "Scope and value proposition" section

      Success metrics

      2 Align Your People

      The Purpose

      Build a culture, operating model, and team that support innovation.

      Key Benefits Achieved

      Develop a plan to address culture gaps and identify and implement your operating model.

      Activities

      2.1 Foster a culture of innovation.

      2.2 Define your operating model.

      Outputs

      Complete "Building an innovative culture" section

      Complete "Operating model" section

      3 Develop Your Capabilities

      The Purpose

      Create the capability to facilitate innovation.

      Key Benefits Achieved

      Create a resourcing plan and prioritization templates to make your innovation program successful.

      Activities

      3.1 Build core innovation capabilities.

      3.2 Develop prioritization criteria.

      Outputs

      Team structure and resourcing requirements

      Prioritization spreadsheet template

      4 Build Your Program

      The Purpose

      Finalize your program and complete the final deliverable.

      Key Benefits Achieved

      Walk away with a complete plan for your innovation program.

      Activities

      4.1 Define your methodology to pilot projects.

      4.2 Conduct a program retrospective.

      Outputs

      Complete "Operating model" section in the template

      Notable wins and goals

      Further reading

      Build Your Enterprise Innovation Program

      Transform your business by adopting the culture and practices that drive innovation.

      Analyst Perspective

      Innovation is not about ideas, it's about people.

      Many organizations stumble when implementing innovation programs. Innovation is challenging to get right, and even more challenging to sustain over the long term.

      One of the common stumbling blocks we see comes from organizations focusing more on the ideas and the process than on the culture and the people needed to make innovation a way of life. However, the most successful innovators are the ones which have adopted a culture of innovation and reinforce innovative behaviors across their organization. Organizational cultures which promote growth mindset, trust, collaboration, learning, and a willingness to fail are much more likely to produce successful innovators.

      This research is not just about culture, but culture is the starting point for innovation. My hope is that organizations will go beyond the processes and methodologies laid out here and use this research to dramatically improve their organization's performance.

      Kim Rodriguez

      Kim Osborne Rodriguez
      Research Director, CIO Advisory
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      As a leader in your organization, you need to:

      • Understand your organization's innovation goals.
      • Create an innovation program or structure.
      • Develop a culture of innovation across your team or organization.
      • Demonstrate an ability to innovate and grow the business.

      Common Obstacles

      In the past, you might have experienced one or more of the following:

      • Innovation initiatives lose momentum.
      • Cynicism and distrust hamper innovation.
      • Innovation efforts are unfocused or don't provide the anticipated value.
      • Bureaucracy has created a bottleneck that stifles innovation.

      Info-Tech's Approach

      This blueprint will help you:

      • Understand the different types of innovation.
      • Develop a clear vision, scope, and focus.
      • Create organizational culture and behaviors aligned with your innovation ambitions.
      • Adopt an operational model and methodologies best suited for your culture, goals, and budget.
      • Successfully run a pilot program.

      Info-Tech Insight

      There is no single right way to approach innovation. Begin with an understanding of your innovation ambitions, your existing culture, and the resources available to you, then adopt the innovation operating model that is best suited to your situation.

      Note: This research is written for the individual who is leading the development of the innovation. This role is referred to as the Chief Innovation Officer (CINO) throughout this research but could be the CIO, CTO, IT director, or another business leader.

      Why is innovation so challenging?

      Most organizations want to be innovative, but very few succeed.

      • Bureaucracy slows innovation: Innovation requires speed – it is important to fail fast and early so you can iterate to improve the final solution. Small, agile organizations like startups tend to be more risk tolerant and can move more quickly to iterate on new ideas compared to larger organizations.
      • Change is uncomfortable: Most people are profoundly uncomfortable with failure, risk, and unknowns – three critical components of innovation. Humans are wired to think efficiently rather than innovatively, which leads to confirmation bias and lack of ingenuity.
      • You will likely fail: Innovation initiatives rarely succeed on the first try – Harvard Business Review estimates between 70% and 90% of innovation efforts fail. Organizations which are more tolerant of failure tend to be significantly more innovative than those which are not (Review of Financial Studies, 2014).

      Based on a survey of global innovation trends and practices:

      75%

      Three-quarters of companies say innovation is a top-three priority.
      Source: BCG, 2021

      30%

      But only 30% of executives say their organizations are doing it well.
      Source: BCG, 2019

      The biggest obstacles to innovation are cultural

      The biggest obstacles to innovation in large companies

      Based on a survey of 270 business leaders.
      Source: Harvard Business Review, 2018

      A bar graph from the Harvard Business Review

      The most common challenges business leaders experience relate to people and culture. Success is based on people, not ideas.

      Politics, turf wars, and a lack of alignment: territorial departments, competition for resources, and unclear roles are holding back the innovation efforts of 55% of respondents.

      FIX IT
      Senior leadership needs to be clear on the innovation goals and how business units are expected to contribute to them.

      Cultural issues: many large companies have a culture that rewards operational excellence and disincentivizes risk. A history of failed innovation attempts may result in significant resistance to new change efforts.

      FIX IT
      Cultural change takes time. Ensure you are rewarding collaboration and risk-taking, and hire people with fresh new perspectives.

      Inability to act on signals crucial to the future of the business: only 18% of respondents indicated their organization was unaware of disruptions, but 42% said they struggled with acting on leading indicators of change.

      FIX IT
      Build the ability to quickly run pilots or partner with startups and incubators to test out new ideas without lengthy review and approval processes.
      Source: Harvard Business Review, 2018

      Build Your Enterprise Innovation Program

      Define your purpose, assess your culture, and build a practice that delivers true innovation.

      An image summarizing how to define your purpose, align your people, and Build your Practice.
      1 Source: Boston Consulting Group, 2021
      2 Source: Boston Consulting Group, 2019
      3 Source: Harvard Business Review, 2018

      Use this research to outperform your peers

      A seven-year review showed that the most innovative companies outperformed the market by upwards of 30%.

      A line graph showing the Normalized Market Capitalization for 2020.

      Innovators are defined as companies that were listed on Fast Company World's 50 Most Innovative Companies for 2+ years.

      Innovation is critical to business success.

      A 25-year study by Business Development Canada and Statistics Canada showed that innovation was more important to business success than management, human resources, marketing, or finance.

      Executive brief case study

      INDUSTRY: Healthcare
      SOURCE: Interview

      Culture is critical

      This Info-Tech member is a nonprofit, community-based mental health organization located in the US. It serves about 25,000 patients per year in community, school, and clinic settings.

      This organization takes its innovation culture very seriously and has developed methodologies to assess individual and team innovation readiness as well as innovation types, which it uses to determine everyone's role in the innovation process. These assessments look at knowledge of and trust in the organization, its innovation profile, and its openness to change. Innovation enthusiasts are involved early in the process when it's important to dream big, while more pragmatic perspectives are incorporated later to improve the final solution.

      Results

      The organization has developed many innovative approaches to delivering healthcare. Notably, they have reimagined patient scheduling and reduced wait times to the extent that some patients can be seen the same day. They are also working to improve access to mental health care despite a shortage of professionals.

      Developing an Innovative Culture

      • Innovation Readiness Assessment
      • Coaching Specific to Innovation Profile
      • Innovation Enthusiasts Involved Early
      • Innovation Pragmatists Involved Later
      • High Success Rate of Innovation

      Define innovation roles and responsibilities

      A table showing key innovation roles and responsibilities.

      Info-Tech's methodology for building your enterprise innovation program

      1. Define Your Purpose

      2. Align Your People

      3. Build Your Practice

      Phase Steps

      1. Understand your mandate
      2. Define your innovation ambitions
      3. Determine value proposition and metrics
      1. Foster a culture of innovation
      2. Define your operating model
      3. Build core innovation capabilities
      1. Build your ideation and prioritization methodologies
      2. Define your pilot project methodology
      3. Conduct a program retrospective

      Phase Outcomes

      Understand where the mandate for innovation comes from, and what the drivers are for pursuing innovation. Define what innovation means to your organization, and set the vision, mission, and guiding principles. Articulate the value proposition and key metrics for measuring success.

      Understand what it takes to build an innovative culture, and what types of innovation structure are most suited to your innovation goals. Define an innovation methodology and build your core innovation capabilities and team.

      Gather ideas and understand how to assess and prioritize initiatives based on standardized metrics. Develop criteria for tracking and measuring the success of pilot projects and conduct a program retrospective.

      Innovation program taxonomy

      This research uses the following common terms:

      Innovation Operating Model
      The operating model describes how the innovation program delivers value to the organization, including how the program is structured, the steps from idea generation to enterprise launch, and the methodologies used.
      Examples: Innovation Hub, Grassroots Innovation.

      Innovation Methodology
      Methodologies describe the ways the operating model is carried out, and the approaches used in the innovation practice.
      Examples: Design Thinking, Weighted Criteria Scoring

      Chief Innovation Officer
      This research is written for the person or team leading the innovation program – this might be a CINO, CIO, or other leader in the organization.

      Innovation Team
      The innovation team may vary depending on the operating model, but generally consists of the individuals involved in facilitating innovation across the organization. This may be, but does not have to be, a dedicated innovation department.

      Innovation Program
      The program for generating ideas, running pilot projects, and building a business case to implement across the enterprise.

      Pilot Project
      A way of testing and validating a specific concept in the real world through a minimum viable product or small-scale implementation. The pilot projects are part of the overall pilot program.

      Insight summary

      Innovation is about people, not ideas or processes
      Innovation does not require a formal process, a dedicated innovation team, or a large budget; the most important success factor for innovation is culture. Companies that facilitate innovative behaviors like growth mindset, collaboration, and the ability to take smart risk are most likely to see the benefits of innovation.

      Very few are doing innovation well
      Only 30% of companies consider themselves innovative, and there's a good reason: innovation involves unknowns, risk, and failure – three situations that people and organizations typically do their best to avoid. Counter this by removing the barriers to innovation.

      Culture is the greatest barrier to innovation
      In a survey of 270 business leaders, the top three most common obstacles were politics, turf wars, and alignment; culture issues; and inability to act on signals crucial to the business (Harvard Business Review, 2018). If you don't have a supportive culture, your ability to innovate will be significantly reduced.

      Innovation is a means to an end
      It is not the end itself. Don't get caught up in innovation for the sake of innovation – make sure you are getting the benefits from your investments. Measurable success factors are critical for maintaining the long-term success of your innovation engine.

      Tackle wicked problems
      Innovative approaches are better at solving complex problems than traditional practices. Organizations that prioritize innovation during a crisis tend to outperform their peers by over 30% and improve their market position (McKinsey, 2020).

      Innovate or die
      Innovation is critical to business growth. A 25-year study showed that innovation was more important to business success than management, human resources, marketing, or finance (Statistics Canada, 2006).

      Blueprint deliverables

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

      Sample Job Descriptions and Organization Charts

      Determine the skills, knowledge, and structure you need to make innovation happen.

      Sample Job Descriptions and Organization Charts

      Ideation Session Template

      Facilitate an ideation session with your staff to identify areas for innovation.

      Ideation Session Template

      Initiative Prioritization Workbook

      Evaluate ideas to identify those which are most likely to provide value.

      Prioritization Workbook

      Key deliverable:

      Enterprise Innovation Program Summary

      Communicate how you plan to innovate with a report summarizing the outputs from this research.

      Enterprise Innovation Program Summary

      Measure the value of this research

      US businesses spend over half a trillion dollars on innovation annually. What are they getting for it?

      • The top innovators(1) typically spend 5-15% of their budgets on innovation (including R&D).
      • This research helps organizations develop a successful innovation program, which delivers value to the organization in the form of new products, services, and methods.
      • Leverage this research to:
        • Get your innovation program off the ground quickly.
        • Increase internal knowledge and expertise.
        • Generate buy-in and excitement about innovation.
        • Develop the skills and capabilities you need to drive innovation over the long term.
        • Validate your innovation concept.
        • Streamline and integrate innovation across the organization.

      (1) based on BCG's 50 Most Innovative Companies 2022

      30%

      The most innovative companies outperform the market by 30%.
      Source: McKinsey & Company, 2020

      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 guided implementation (GI) on this topic look like?

      Phase 0 Phase 1 Phase 2 Phase 3 Finish

      Call #1: Scope requirements, objectives, and your specific challenges.

      Call #2: Understand your mandate.
      (Activity 1.1)

      Call #3: Innovation vision, guiding principles, value proposition, and scope.
      (Activities 1.2 and 1.3)

      Call #4: Foster a culture of innovation. (Activity 2.1)

      Call #5: Define your methodology. (Activity 2.2)

      Call #6: Build core innovation capabilities. (Activity 2.3)

      Call #7: Build your ideation and pilot programs. (Activities 3.1 and 3.2)

      Call #8: Identify success metrics and notable wins. (Activity 3.3)

      Call #9: Summarize results and plan next steps.

      A 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 three to six months.

      Workshop overview

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

      Session 1 Session 2 Session 3 Session 4

      Wrap Up

      Activities

      Define Your Ambitions

      Align Your People

      Develop Your Capabilities

      Build Your Program

      Next Steps and
      Wrap Up (offsite)

      1. Understand your innovation mandate (complete activity prior to workshop)
      2. Define your innovation ambitions
      3. Determine value proposition and metrics
      1. Foster a culture of innovation
      2. Define your operating model
      1. Build core innovation capabilities
      2. Develop prioritization criteria
      1. Define your methodology to pilot projects
      2. Conduct a program retrospective
      1. Complete in-progress deliverables from previous four days
      2. Set up review time for workshop deliverables and to discuss next steps

      Deliverables

      1. Our purpose
      2. Message from the CEO
      3. Vision and guiding principles
      4. Scope and value proposition
      5. Success metrics
      1. Building an innovative culture
      2. Operating model
      1. Core capabilities and structure
      2. Idea evaluation prioritization criteria
      1. Program retrospective
      2. Notable wins
      3. Executive summary
      4. Next steps
      1. Completed enterprise innovation program
      2. An engaged and inspired team

      Phase 1: Define Your Purpose

      Develop a better understanding of the drivers for innovation and what success looks like.

      Purpose

      People

      Practice

      1. Understand your mandate
      2. Define your innovation ambitions
      3. Determine value proposition and metrics
      1. Foster a culture of innovation
      2. Define your operating model
      3. Build core innovation capabilities
      1. Build your ideation and prioritization methodologies
      2. Define your pilot project methodology
      3. Conduct a program retrospective

      This phase will walk you through the following activities:

      • Understand your innovation mandate, including its drivers, scope, and focus.
      • Define what innovation means to your organization.
      • Develop an innovation vision and guiding principles.
      • Articulate the value proposition and proposed metrics for evaluating program success.

      This phase involves the following participants:

      • CINO
      • Business executives

      Case study

      INDUSTRY: Transportation
      SOURCE: Interview

      ArcBest
      ArcBest is a multibillion-dollar shipping and logistics company which leverages innovative technologies to provide reliable and integrated services to its customers.

      An Innovative Culture Starts at the Top
      ArcBest's innovative culture has buy-in and support from the highest level of the company. Michael Newcity, ArcBest's CEO, is dedicated to finding better ways of serving their customers and supports innovation across the company by dedicating funding and resources toward piloting and scaling new initiatives.
      Having a clear purpose and mandate for innovation at all levels of the organization has resulted in extensive grassroots innovation and the development of a formalized innovation program.

      Results
      ArcBest has a legacy of innovation, going back to its early days when it developed a business intelligence solution before anything else existed on the market. It continues to innovate today and is now partnering with start-ups to further expand its innovation capabilities.

      "We don't micromanage or process-manage incremental innovation. We hire really smart people who are inspired to create new things and we let them run – let them create – and we celebrate it.
      Our dedication to innovation comes from the top – I am both the President and the Chief Innovation Officer, and innovation is one of my top priorities."

      Michael Newcity

      Michael Newcity
      President and Chief Innovation Officer ArcBest

      1.1 Understand your innovation mandate

      Before you can act, you need to understand the following:

      • Where is the drive for innovation coming from?
        The source of your mandate dictates the scope of your innovation practice – in general, innovating outside the scope of your mandate (i.e. trying to innovate on products when you don't have buy-in from the product team) will not be successful.
      • What is meant by "innovation"?
        There are many different definitions for innovation. Before pursuing innovation at your organization, you need to understand how it is defined. Use the definition in this section as a starting point, and craft your own definition of innovation.
      • What kind of innovation are you targeting?
        Innovation can be internal or external, emergent or deliberate, and incremental or radically transformative. Understanding what kind of innovation you want is the starting point for your innovation practice.

      The source of your mandate dictates the scope of your influence

      You can only influence what you can control.

      Unless your mandate comes from the CEO or Board of Directors, driving enterprise-wide innovation is very difficult. If you do not have buy-in from senior business leaders, use lighthouse projects and a smaller innovation practice to prove the value of innovation before taking on enterprise innovation.

      In order to execute on a mandate to build innovation, you don't just need buy-in. You need support in the form of resources and funding, as well as strong leadership who can influence culture and the authority to change policies and practices that inhibit innovation.

      For more resources on building relationships in your organization, refer to Info-Tech's Become a Transformational CIO blueprint.

      What is "innovation"?

      Innovation is often easier to recognize than define.

      Align on a useful definition of innovation for your organization before you embark on a journey of becoming more innovative.

      Innovation is the practice of developing new methods, products or services which provide value to an organization.

      Practice
      This does not have to be a formal process – innovation is a means to an end, not the end itself.

      New
      What does "new" mean to you?

      • New application of an existing method
      • Developing a completely original product
      • Adopting a service from another industry

      Value
      What does value mean to you? Look to your business strategy to understand what goals the organization is trying to achieve, then determine how "value" will be measured.

      Info-Tech Insight

      Some innovations are incremental, while some are radically transformative. Decide what kind of innovation you want to cultivate before developing your strategy.

      We can categorize innovation in three ways

      Evaluate your goals with respect to innovation: focus, strategy, and potential to transform.

      Focus: Where will you innovate?

      Focus

      Strategy: To what extent will you guide innovation efforts?

      Strategy

      Potential: How radical will your innovations be?

      Potential

      What are your ambitions?

      1. Develop a better understanding of what type of innovation you are trying to achieve by plotting out your goals on the categories on the left.
      2. All categories are independent of one another, so your goals may fall anywhere on the scales for each category.
      3. Understanding your innovation ambitions helps establish the operating model best suited for your innovation practice.
      4. In general, innovation which is more external, deliberate, and radical tends to be more centralized.

      Activity 1.1 Understand your innovation mandate

      1 hour

      1. Schedule a 30-minute discussion with the person (i.e. CEO) or group (i.e. Board of Directors) ultimately requesting the shift toward innovation. If there is no external party, then conduct this assessment yourself.
      2. Facilitate a discussion that addresses the following questions:
      • What is meant by "innovation"?
      • What are they hoping to achieve through innovation?
      • What is the innovation scope? Are any areas off-limits (i.e. org structure, new products, certain markets)?
      • What is the budget (i.e. people, money) they are willing to commit to innovation?
      • What type of innovation are they pursuing?
      1. Record this information and complete the "Our Purpose" section of the Innovation Program Template.

      Download the Innovation Program Template.

      Input

      • Knowledge of the key decision maker/sponsor for innovation

      Output

      • Understanding of the mandate for innovation, including definition, value, scope, budget, and type of innovation

      Materials

      • Innovation Program Template

      Participants

      • CINO
      • CEO, CTO, or Board of Directors (whoever is requesting/sponsoring the pursuit of innovation)

      1.2 Define your innovation ambitions

      Articulate your future state through a vision and guiding principles.

      • Vision and purpose make up the foundation on which all other design aspects will be based. These aspects should not be taken lightly, but rather they should be the force that aligns everyone to work toward a common outcome. It is incumbent on leaders to make them part of the DNA of the organization – to drive organization, structure, culture, and talent strategy.
      • Your vision statement is a future-focused statement that summarizes what you hope to achieve. It should be inspirational, ambitious, and concise.
      • Your guiding principles outline the guardrails for your innovation practice. What will your focus be? How will you approach innovation? What is off-limits?
      • Define the scope and focus for your innovation efforts. This includes what you can innovate on and what is off limits.

      Your vision statement is your North Star

      Articulate an ambitious, inspirational, and concise vision statement for your innovation efforts.

      A strong vision statement:

      • Is future-focused and outlines what you want to become and what you want to achieve.
      • Provides focus and direction.
      • Is ambitious, focused, and concise.
      • Answers: What problems are we solving? Who and what are we changing?

      Examples:

      • "We create radical new technologies to solve some of the world's hardest problems." – Google X, the Moonshot Factory
      • "To be the most innovative enterprise in the world." – 3M
      • "To use our imagination to bring happiness to millions of people." – Disney

      "Good business leaders create a vision, articulate the vision, passionately own the vision, and relentlessly drive it to completion." – Jack Welch, Former Chairman and CEO of GE

      Your guiding principles are the guardrails for creativity

      Strong guiding principles give your team the freedom and direction to innovate.

      Strong guiding principles:

      • Focus on the approach, i.e. how things are done, as opposed to what needs to be done.
      • Are specific to the organization.
      • Inform and direct decision making with actionable statements. Avoid truisms, general statements, and observations.
      • Are long-lasting and based on values, not solutions.
      • Are succinct and easily digestible.
      • Can be measured and verified.
      • Answers: How do we approach innovation? What are our core values

      Craft your guiding principles using these examples

      Encourage experimentation and risk-taking
      Innovation often requires trying new things, even if they might fail. We encourage experimentation and learn from failure, so that new ideas can be tested and refined.

      Foster collaboration and cross-functional teams
      Innovation often comes from the intersection of different perspectives and skill sets.

      Customer-centric
      Focus on creating value for the end user. This means understanding their needs and pain points, and using that knowledge to develop new methods, products, or services.

      Embrace diversity and inclusivity
      Innovation comes from a variety of perspectives, backgrounds, and experiences. We actively seek out and encourage diversity and inclusivity among our team members.

      Foster a culture of learning and continuous improvement
      Innovation requires continuous learning, development, and growth. We facilitate a culture that encourages learning and development, and that seeks feedback and uses it to improve.

      Flexible and adaptable
      We adapt to changes in the market, customer needs, and new technologies, so that it can continue to innovate and create value over time.

      Data-driven
      We use performance metrics and data to guide our innovation efforts.

      Transparency
      We are open and transparent in our processes and let the business needs guide our innovation efforts. We do not lead innovation, we facilitate it.

      Activity 1.2 Craft your vision statement and guiding principles

      1-2 hours

      1. Gather your innovation team and key program sponsors. Review the guidelines for creating vision statements and guiding principles, as well as your mandate and focus for innovation.
      2. As a group, discuss what you hope to achieve through your innovation efforts.
      3. Separately, have each person write down their ideas for a vision statement. Bring the group back together and share ideas. Group the concepts together and construct a single statement which outlines your aspirational vision.
      4. As a group, review the example guiding principles.
      5. Separately, have each person write down three to five guiding principles. Bring the group back together and share ideas. Group similar concepts together and consolidate duplicate ideas. From this list, construct six to eight guiding principles.
      6. Document your vision and guiding principles in the appropriate sections of the Innovation Program Template.

      Input

      • Understanding of your innovation mandate
      • Business vision, mission, and values
      • Sample vision statements and guiding principles

      Output

      • Vision statement
      • Guiding principles

      Materials

      • In person: Whiteboard/flip charts, sticky notes, pens, and notepads
      • Virtual: Consider using a shared document, virtual whiteboard, or online facilitation tool like MURAL
      • Innovation Program Template

      Participants

      • CINO
      • Innovation sponsors
      • Business leaders
      • Innovation team

      1.3 Determine your value proposition and metrics

      Justify the existence of the innovation program with a strong value proposition.

      • The value proposition for developing an innovation program will be different for each organization, depending on what the organization hopes to achieve. Consider your mandate for innovation as well as the type of innovation you are pursuing when crafting the value proposition.
      • Some of the reasons organizations may pursue innovation:
        • Business growth: Respond to market disruption; create new customers; take advantage of opportunities.
        • Branding: Create market differentiation; increase customer satisfaction and retention; adapt to customer needs.
        • Profitability: Improve products, services, or operations to increase competitiveness and profitability; develop more efficient processes.
        • Culture: Foster a culture of creativity and experimentation within the organization, encouraging employees to think outside the box.
        • Positive impact: Address social challenges such as poverty and climate change.

      Develop a strong value proposition for your innovation program

      Demonstrate the value to the business.

      A strong value proposition not only articulates the value that the business will derive from the innovation program but also provides a clear focus, helps to communicate the innovation goals, and ultimately drives the success of the program.

      Focus
      Prioritize and focus innovation efforts to create solutions that provide real value to the organization

      Communicate
      Communicate the mandate and benefits of innovation in a clear and compelling way and inspire people to think differently

      Measure Success
      Measure the success of your program by evaluating outcomes based on the value proposition

      Track appropriate success metrics for your innovation program

      Your success metrics should link back to your organizational goals and your innovation program's value proposition.

      Revenue Growth: Increase in revenue generated by new products or services.

      Market Share: Percentage of total market that the business captures as a result of innovation.

      Customer Satisfaction: Reviews, customer surveys, or willingness to recommend the company.

      Employee Engagement: Engagement surveys, performance, employee retention, or turnover.

      Innovation Output: The number of new products, services, or processes that have been developed.

      Return on Investment: Financial return on the resources invested in the innovation process.

      Social Impact: Number of people positively impacted, net reduction in emissions, etc.

      Time to Launch: The time it takes for a new product or service to go from idea to launch.

      Info-Tech Insight

      The total impact of innovation is often intangible and extremely difficult to capture in performance metrics. Focus on developing a few key metrics rather than trying to capture the full value of innovation.

      How much does innovation cost?

      Company Industry Revenue(2)
      (USD billions)
      R&D Spend
      (USD billions)
      R&D Spend
      (% of revenue)
      Apple Technology $394.30 $26.25 6.70%
      Microsoft Technology $203.10 $25.54 12.50%
      Amazon.com Retail $502.20 $67.71 13.40%
      Alphabet Technology $282.10 $37.94 13.40%
      Tesla Manufacturing $74.90 $3.01 4.00%
      Samsung Technology $244.39 (2021)(3) $19.0 (2021) 7.90%
      Moderna Pharmaceuticals $23.39 $2.73 11.70%
      Huawei Technology $99.9 (2021)4 Not reported -
      Sony Technology $83.80 Not reported -
      IBM Technology $60.50 $1.61 2.70%
      Meta Software $118.10 $32.61 27.60%
      Nike Commercial goods $49.10 Not reported -
      Walmart Retail $600.10 Not reported -
      Dell Technology $105.30 $2.60 2.50%
      Nvidia Technology $28.60 $6.85 23.90%


      The top innovators(1) in the world spend 5% to 15% of their revenue on innovation.

      Innovation requires a dedicated investment of time, money, and resources in order to be successful. The most innovative companies, based on Boston Consulting Group's ranking of the 50 most innovative companies in the world, spend significant portions of their revenue on research and development.

      Note: This data uses research and development as a proxy for innovation spending, which may overestimate the total spend on what this research considers true innovation.

      (1) Based on Boston Consulting Group's ranking of the 50 most innovative companies in the world, 2022
      (2) Macrotrends, based on the 12 months ending Sept 30, 2022
      (3) Statista
      (4) CNBC, 2022

      Activity 1.3 Develop your value proposition and performance metrics

      1 hour

      1. Review your mandate and vision statement. Write down your innovation goals and desired outcomes from pursuing innovation, prioritize the desired outcomes, and select the top five.
      2. For each desired outcome, develop one to two metrics which could be used to track its success. Some outcomes are difficult to track, so get creative when it comes to developing metrics. If you get stuck, think about what would differentiate a great outcome from an unsuccessful one.
      3. Once you have developed a list of three to five key metrics, read over the list and ensure that the metrics you have developed don't negatively influence your innovation. For example, a metric of the number of successful launches may drive people toward launching before a product is ready.
      4. For each metric, develop a goal. For example, you may target 1% revenue growth over the next fiscal year or 20% energy use reduction.
      5. Document your value proposition and key performance metrics in the appropriate sections of the Innovation Program Template.

      Input

      • Understanding of your innovation mandate
      • Vision statement

      Output

      • Value proposition
      • Performance metrics

      Materials

      • Innovation Program Template

      Participants

      • CINO

      Phase 2: Align Your People

      Create a culture that fosters innovative behaviors and puts processes in place to support them.

      Purpose

      People

      Practice

      1. Understand your mandate
      2. Define your innovation ambitions
      3. Determine value proposition and metrics
      1. Foster a culture of innovation
      2. Define your operating model
      3. Build core innovation capabilities
      1. Build your ideation and prioritization methodologies
      2. Define your pilot project methodology
      3. Conduct a program retrospective

      This phase will walk you through the following activities:

      • Understand the key aspects of innovative cultures, and the behaviors associated with innovation.
      • Assess your culture and identify gaps.
      • Define your innovation operating model based on your organizational culture and the focus for innovation.
      • Build your core innovation capabilities, including an innovation core team (if required based on your operating model).

      This phase involves the following participants:

      • CINO
      • Innovation team

      2.1 Foster a culture of innovation

      Culture is the most important driver of innovation – and the most challenging to get right.

      • Fostering a culture of innovation requires a broad approach which considers the perspectives of individuals, teams, leadership, and the overall organization.
      • If you do not have support from leadership, it is very difficult to change organizational culture. It may be more effective to start with an innovation pilot or lighthouse project in order to gain support before addressing your culture.
      • Rather than looking to change outcomes, focus on the behaviors which lead to innovation – such as growth mindset and willingness to fail. If these aren't in place, your ability to innovate will be limited.
      • This section focuses on the specific behaviors associated with increased innovation. For additional resources on implementing these changes, refer to Info-Tech's other research:

      Info-Tech's Fix Your IT Culture can help you promote innovative behaviors

      Refer to Improve IT Team Effectiveness to address team challenges

      Build a culture of innovation

      Focus on behaviors, not outcomes.

      The following behaviors and key indicators either stifle or foster innovation.

      Stifles Innovation Key Indicators Fosters Innovation Key Indicators
      Fixed mindset "It is what it is" Growth mindset "I wonder if there's a better way"
      Performance focused "It's working fine" Learning focused "What can we learn from this?"
      Fear of reprisal "I'll get in trouble" Psychological safety "I can disagree"
      Apathy "We've always done it this way" Curiosity "I wonder what would happen if…"
      Cynicism "It will never work" Trust "You have good judgement"
      Punishing failure "Who did this?" Willingness to fail "It's okay to make mistakes"
      Individualism "How does this benefit me?" Collaboration "How does this benefit us?"
      Homogeneity "We never disagree" Diversity and inclusion "We appreciate different views"
      Excessive bureaucracy "We need approval" Autonomy "I can do this"
      Risk avoidance "We can't try that" Appropriate risk-taking "How can we do this safely?"

      Ensure you are not inadvertently stifling innovation.
      Review the following to ensure that the desired behaviors are promoted:

      • Hiring practices
      • Performance evaluation metrics
      • Rewards and incentives
      • Corporate policies
      • Governance structures
      • Leadership behavior

      Case study

      INDUSTRY: Commercial Real Estate and Retail
      SOURCE: Interview

      How not to approach innovation.

      This anonymous national organization owned commercial properties across the country and had the goal of becoming the most innovative real estate and retail company in the market.

      The organization pursued innovation in the digital solutions space across its commercial and retail properties. Within this space, there were significant differences in risk tolerance across teams, which resulted in the more risk-tolerant teams excluding the risk-averse members from discussions in order to circumvent corporate policies on risk tolerance. This resulted in an adversarial and siloed culture where each group believed they knew better than the other, and the more risk-averse teams felt like they were policing the actions of the risk-tolerant group.

      Results

      Morale plummeted, and many of the organization's top people left. Unfortunately, one of the solutions did not meet regulatory requirements, and the company faced negative media coverage and legal action. There was significant reputational damage as a result.

      Lessons Learned

      Considering differences in risk tolerance and risk appetite is critical when pursuing innovation. While everyone doesn't have to agree, leadership needs to understand the different perspectives and ensure that no one party is dominating the conversation over the others. An understanding of corporate risk tolerance and risk appetite is necessary to drive innovation.

      All perspectives have a place in innovation. More risk tolerant perspectives should be involved early in the ideas-generation phase, and risk-averse perspectives should be considered later when ideas are being refined.

      Speed should not override safety or circumvent corporate policies.

      Understand your risk tolerance and risk appetite

      Evaluate and align the appetite for risk.

      • It is important to understand the organization's risk tolerance as well as the desire for risk. Consider the following risk categories when investigating the organization's views on risk:
        • Financial risk: the potential for financial or property loss.
        • Operational risk: the potential for disruptions to operations.
        • Reputational risk: the potential for negative impact to brand or reputation.
        • Compliance risk: the potential for loss due to non-compliance with laws and regulations.
      • Greater risk tolerance typically enables greater innovation. Understand the varying levels of risk tolerance across your organization, and how these differences might impact innovation efforts.

      An arrow showing the directions of risk tolerance.

      It is more important to match the level of risk tolerance to the degree of innovation required. Not all innovation needs to be (or can feasibly be) disruptive.
      Many factors impact risk tolerance including:

      • Regulation
      • Organization size
      • Country
      • Industry
      • Personal experience
      • Type of risk

      Use Info-Tech's Security Risk Management research to better understand risk tolerance

      Activity 2.1 Assess your innovation culture

      1-3 hours

      1. Review the behaviors which support and stifle innovation and give each behavior a score from 1 (stifling innovation) to 5 (fostering innovation). Any behaviors which fall below a 4 on this scale should be prioritized in your efforts to create an innovative culture.
      2. Review the following policies and practices to determine how they may be contributing to the behaviors you see in your organization:
        1. Hiring practices
        2. Performance evaluation metrics
        3. Rewards, recognition, and incentives
        4. Corporate policies
        5. Governance structures
        6. Leadership behavior
      3. Identify three concrete actions you can take to correct any behaviors which are stifling innovation. Examples might be revising a policy which punishes failure or changing performance incentives to reward appropriate risk taking.
      4. Summarize your findings in the appropriate section of the Innovation Program Template.

      Input

      • Innovation behaviors

      Output

      • Understanding of your organization's culture
      • Concrete actions you can take to promote innovation

      Materials

      • List of innovative behaviors
      • Relevant policies and documents to review
      • Innovation Program Template

      Participants

      • CINO

      2.2 Define your innovation model

      Set up your innovation practice for success using proven models and methodologies.

      • There are many ways to approach innovation, from highly distributed forms where it's just part of everyone's job to very centralized and arm's-length innovation hubs or even outsourced innovation via startups. You can combine different approaches to create your own approach.
      • You may or may not have a formal innovation team, but if you do, their role is to facilitate innovation – not lead it. Innovation is most effective when it is led by the business.
      • There are many tools and methodologies you can use to facilitate innovation. Choose the one (or combination) that best suits your needs.

      Select the right model

      There is no one right way to pursue innovation, but some methods are better than others for specific situations and goals. Consider your existing culture, your innovation goals, and your budget when selecting the right methodology for your innovation.

      Model Description Advantages Disadvantages Good when…
      Grassroots Innovation Innovation is the responsibility of everyone, and there is no centralized innovation team. Ideas are piloted and scaled by the person/team which produces it.
      • Can be used in any organization or team
      • Can support low or high degree of structure
      • Low funding requirement
      • Requires a strong innovation culture
      • Often does not produce results since people don't have time to focus on innovation
      • Innovation culture is strong
      • Funding is limited
      • Goal is internal, incremental innovation
      Community of Practice Innovation is led by a cross-divisional Community of Practice (CoP) which includes representation from across the business. Champions consult with their practice areas and bring ideas forward.
      • Bringing people together can help stimulate and share ideas
      • Low funding requirement
      • Able to support many types of innovation
      • Some people may feel left out if they can't be involved
      • May not produce results if people are too busy to dedicate time to innovate
      • Innovation culture is present
      • Funding is limited
      • Goal is incremental or disruptive innovation
      Innovation Enablement
      *Most often recommended*
      A dedicated innovation team with funding set aside to support pilots with a high degree of autonomy, with the role of facilitating business-led innovation.
      • Most flexible of all options
      • Supports business-led innovation
      • Can deliver results quickly
      • Can enable a higher degree of innovation
      • Requires dedicated staff and funding
      • Innovation culture is present
      • Funding is available
      • Goal is internal or external, incremental or radical innovation
      Center of Excellence Dedicated team responsible for leading innovation on behalf of the organization. Generally, has business relationship managers who gather ideas and liaise with the business.
      • Can deliver results quickly
      • Can offer a fresh perspective
      • Can enable a higher degree of innovation
      • Requires dedicated staff and funding
      • Is typically separate from the business
      • Results may not align with the business needs or have adequate input
      • Innovation culture is weak
      • Funding is significant
      • Goal is external, disruptive innovation
      Innovation Hub An arm's length innovation team is responsible for all or much of the innovation and may not interact much with the core business.
      • Can deliver results quickly
      • Can be extremely innovative
      • Expensive
      • Results may not align with the business needs or have adequate/any input
      • Innovation culture is weak
      • Funding is very significant
      • Goal is external, radical innovation
      Outsourced Innovation Innovation is outsourced to an external organization which is not linked to the primary organization. This can take the form of working with or investing in startups.
      • Can lead to more innovative ideas than internal innovation
      • Investments can become a diverse revenue stream if startups are successful
      • Innovation does not rely on culture
      • Higher risk of failure
      • Less control over goals or focus
      • Results may not align with the business needs or have any input from users
      • Innovation does not rely on culture
      • Funding is significant
      • Goal is external or internal, radical innovation

      Use the right methodologies to support different stages of your innovation process

      A chart showing methodologies to support different stages of the integration process.

      Adapted from Niklaus Gerber via Medium, 2022

      Methodologies are most useful when they are aligned with the goals of the innovation organization.

      For example, design thinking tends to be excellent for earlier innovation planning, while Agile can allow for faster implementation and launch of initiatives later in the process.

      Consider combining two or more methodologies to create a custom approach that best suits your organization's capabilities and goals.

      Sample methodologies

      A robust innovation methodology ensures that the process for developing, prioritizing, selecting, implementing, and measuring initiatives is aligned with the results you are hoping to achieve.

      Different types of problems (drivers for innovation) may necessitate different methodologies, or a combination of methodologies.

      Hackathon: An event which brings people together to solve a well-defined problem.

      Design Thinking: Creative approach that focuses on understanding the needs of users.

      Lean Startup: Emphasizes rapid experimentation in order to validate business hypotheses.

      Design Sprint: Five-day process for answering business questions via design, prototyping, and testing.

      Agile: Iterative design process that emphasizes project management and retrospectives.

      Three Horizons: Framework that looks at opportunities on three different time horizons.

      Innovation Ambition Matrix: Helps organizations categorize projects as part of the core offering, an adjacent offering, or completely new.

      Global Innovation Management: A process of identifying, developing and implementing new ideas, products, services, or processes using alternative thinking.

      Blue Ocean Strategy: A methodology that helps organizations identify untapped market space and create new markets via unique value propositions.

      Activity 2.2 Design your innovation model

      1-2 hours

      1. Think about the following factors which influence the design of your innovation practice:
        1. Existing organizational culture
        2. Available funding to support innovation
        3. Type of innovation you are targeting
      2. Review the innovation approaches, and identify which approach is most suitable for your situation. Note why this approach was selected.
      3. Review the innovation methodologies and research those of interest. Select two to five methodologies to use for your innovation practice.
      4. Document your decisions in the Innovation Program Template.

      Input

      • Understanding of your mandate and existing culture

      Output

      • Innovation approach
      • Selected methodologies

      Materials

      • Innovation Program Template

      Participants

      • CINO
      • Innovation team

      2.3 Build your core innovation capabilities

      Develop the skills, knowledge, and experience to facilitate successful innovation.

      • Depending on the approach you selected in step 2.2, you may or may not require a dedicated innovation team. If you do, use the job descriptions and sample organization charts to build it. If not, focus on developing key capabilities which are needed to facilitate innovation.
      • Diversity is key for successful innovation – ensure your team (formal or otherwise) includes diverse perspectives and backgrounds.
      • Use your guiding principles when hiring and training your team.
      • Focus on three core roles: evangelists, enablers, and experts.

      Focus on three key roles when building your innovation team

      Types of roles will depend on the purpose and size of the innovation team.

      You don't need to grow them all internally. Consider partnering with vendors and other organizations to build capabilities.

      Evangelists

      Visionaries who inspire, support, and facilitate innovation across the business. Their responsibilities are to drive the culture of innovation.

      Key skills and knowledge:

      • Strong communication skills
      • Relationship-building
      • Consensus-building
      • Collaboration
      • Growth mindset

      Sample titles:

      • CINO
      • Chief Transformation Officer
      • Chief Digital Officer
      • Innovation Lead
      • Business Relationship Manager

      Enablers

      Translate ideas into tangible business initiatives, including assisting with business cases and developing performance metrics.

      Key skills and knowledge:

      • Critical thinking skills
      • Business knowledge
      • Facilitation skills
      • Consensus-building
      • Relationship-building

      Sample titles:

      • Product Owner
      • Design Thinking Lead
      • Data Scientist
      • Business Analyst
      • Human Factors Engineer
      • Digital Marketing Specialist

      Experts

      Provide expertise in product design, delivery and management, and responsible for supporting and executing on pilot projects.

      Key skills and knowledge:

      • Project management skills
      • Technical expertise
      • Familiarity with emerging technologies
      • Analytical skills
      • Problem-solving skills

      Sample titles:

      • Product Manager
      • Scrum Master/Agile Coach
      • Product Engineer/DevOps
      • Product Designer
      • Emerging tech experts

      Sample innovation team structure (large enterprise)

      Visualize the whole value delivery process end-to-end to help identify the types of roles, resources, and capabilities required. These capabilities can be sourced internally (i.e. grow and hire internally) or through collaboration with centers of excellence, commercial partners, etc.

      A flow chart of a sample innovation team structure.

      Streamline your process by downloading Info-Tech's job description templates:

      Activity 2.3 Build your innovation team

      2-3 hours

      1. Review your work from the previous activities as well as the organizational structure and the job description templates.
      2. Start a list with two columns: currently have and needed. Start listing some of the key roles and capabilities from earlier in this step, categorizing them appropriately.
      3. If you are using an organizational structure for your innovation process, start to frame out the structure and roles for your team.
      4. Develop a list of roles you need to hire, and the key capabilities you need from candidates. Using the job descriptions, write job postings for each role.
      5. Record your work in the appropriate section of the Innovation Program Template.

      Input

      • Previous work
      • Info-Tech job description templates

      Output

      • List of capabilities required
      • Org chart
      • Job postings for required roles

      Materials

      • Note-taking capability
      • Innovation Program Template

      Participants

      • CINO

      Related Info-Tech Research

      Fix Your IT Culture

      • Promote psychological safety and growth mindset within your organization.
      • Develop the organizational behaviors that lead to innovation.

      Improve IT Team Effectiveness

      • Address behaviors, processes, and cultural factors which impact team effectiveness.
      • Grow the team's ability to address challenges and navigate volatile, uncertain, complex and ambiguous environments.

      Master Organizational Change Management Practices

      • 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.

      Phase 3: Build Your Practice

      Define your innovation process, streamline pilot projects, and scale for success.

      Purpose

      People

      Practice

      1. Understand your mandate
      2. Define your innovation ambitions
      3. Determine value proposition and metrics
      1. Foster a culture of innovation
      2. Define your operating model
      3. Build core innovation capabilities
      1. Build your ideation and prioritization methodologies
      2. Define your pilot project methodology
      3. Conduct a program retrospective

      This phase will walk you through the following activities:

      • Build the methodologies needed to elicit ideas from the business.
      • Develop criteria to evaluate and prioritize ideas for piloting.
      • Define your pilot program methodologies and processes, including criteria to assess and compare the success of pilot projects.
      • Conduct an end-of-year program retrospective to evaluate the success of your innovation program.

      This phase involves the following participants:

      • CINO
      • Innovation team

      Case study

      INDUSTRY: Government
      SOURCE: Interview

      Confidential US government agency

      The business applications group at this government agency strongly believes that innovation is key to progress and has instituted a formal innovation program as part of their agile operations. The group uses a Scaled Agile Framework (SAFe) with 2-week sprints and a 12-week program cycle.

      To support innovation across the business unit, the last sprint of each cycle is dedicated toward innovation and teams do not commit to any other during these two weeks. At the end of each innovation sprint, ideas are presented to leadership and the valuable ones were either implemented initially or were given time in the next cycle of sprints for further development. This has resulted in a more innovative culture across the practice.

      Results

      There have been several successful innovations since this process began. Notably, the agency had previously purchased a robotic process automation platform which was only being used for a few specific applications. One team used their innovation sprint to expand the use cases for this solution and save nearly 10,000 hours of effort.

      Standard 12-week Program Cycle
      An image of a standard 12-week program

      Design your innovation operating model to maximize value and learning opportunities

      Pilots are an iterative process which brings together innovators and business teams to test and evaluate ideas.

      Your operating model should include several steps including ideation, validation, evaluation and prioritization, piloting, and a retrospective which follows the pilot. Use the example on this slide when designing your own innovation operating model.

      An image of the design process for innovation operation model.

      3.1 Build your ideation and prioritization methodologies

      Engage the business to generate ideas, then prioritize based on value to the business.

      • There are many ways of generating ideas, from informal discussion to formal ideation sessions or submission forms. Whatever you decide to use, make sure that you're getting the right information to evaluate ideas for prioritization.
      • Use quantitative and qualitative metrics to evaluate ideas generated during the ideation process.
        • Quantitative metrics might include potential return on investment (ROI) or effort and resources required to implement.
        • Qualitative metrics might include alignment with the organizational strategy or the level of risk associated with the idea.

      Engage the business to generate ideas

      There are many ways of generating innovative ideas. Pick the methods that best suit your organization and goals.

      Design Thinking
      A structured approach that encourages participants to think creatively about the needs of the end user.

      An image including the following words: Empathize, Define; Ideate; Test.

      Ideation Workshop
      A formal session that is used to understand a problem then generate potential solutions. Workshops can incorporate the other methodologies (such as brainstorming, design thinking, or mind mapping) to generate ideas.

      • Define the problem
      • Generate ideas
      • Capture ideas
      • Evaluate and prioritize
      • Assign next steps

      Crowdsourcing
      An informal method of gathering ideas from a large group of people. This can be a great way to generate many ideas but may lack focus.

      Value Proposition Canvas
      A visual tool which helps to identify customer (or user) needs and design products and services that meet those needs.

      an image of the Value Proposition Canvas

      Evaluate ideas and focus on those with the greatest value

      Evaluation should be transparent and use both quantitative and qualitative metrics. The exact metrics used will depend on your organization and goals.

      It is important to include qualitative metrics as these dimensions are better suited to evaluating highly innovative ideas and can capture important criteria like alignment with overall strategy and feasibility.

      Develop 5 to 10 criteria that you can use to evaluate and prioritize ideas. Some criteria may be a pass/fail (for example, minimum ROI) and some may be comparative.

      Evaluate
      The first step is to evaluate ideas to determine if they meet the minimum criteria. This might include quantitative criteria like ROI as well as qualitative criteria like strategic alignment and feasibility.

      Prioritize
      Ideas that pass the initial evaluation should be prioritized based on additional criteria which might include quantitative criteria such as potential market size and cost to implement, and qualitative criteria such as risk, impact, and creativity.

      Quantitative Metrics

      Quantitative metrics are objective and easily comparable between initiatives, providing a transparent and data-driven process for evaluation and prioritization.
      Examples:

      • Potential market size
      • ROI
      • Net present value
      • Payback period
      • Number of users impacted
      • Customer acquisition cost
      • Customer lifetime value
      • Breakeven analysis
      • Effort required to implement
      • Cost to implement

      Qualitative Metrics

      Qualitative metrics are less easily comparable but are equally important when it comes to evaluating ideas. These should be developed based on your organization strategy and innovation goals.
      Examples:

      • Strategy alignment
      • Impact on users
      • Uncertainty and risk
      • Innovation potential
      • Culture impact
      • Feasibility
      • Creativity and originality
      • Type of innovation

      Activity 3.1 Develop prioritization metrics

      1-3 hours

      1. Review your mandate, purpose, innovation goals and the sample prioritization and evaluation metrics.
      2. Write down a list of your goals and their associated metrics, then prioritize which are the most important.
      3. Determine which metrics will be used to evaluate ideas before they move on to the prioritization stage, and which metrics will be used to compare initiatives in order to determine which will receive further investment.
      4. For each evaluation metric, determine the minimum threshold required for an idea to move forward. For each prioritization metric identify the definition and how it will be evaluated. Qualitative metrics may require more precise definitions than quantitative metrics.
      5. Enter your metrics into the Initiative Prioritization Template.

      Input

      • Innovation mandate
      • Innovation goals
      • Sample metrics

      Output

      • Evaluation and prioritization metrics for ideas

      Materials

      • Whiteboard/Flip charts
      • Innovation Program Template

      Participants

      • Innovation leader

      Download the Initiative Prioritization Template

      3.2 Build your program to pilot initiatives

      Test and refine ideas through real-world pilot projects.

      • The purpose of your pilot is to test and refine ideas in the real world. In order to compare pilot projects, it's important to track key performance indicators throughout the pilot. Measurements should be useful and comparable.
      • Innovation facilitators are responsible for supporting pilot projects, including designing the pilot, setting up metrics, tracking outcomes, and facilitating retrospectives.
      • Pilots generally follow an Agile methodology where ideas may be refined as the pilot proceeds, and the process iterates until either the idea is discarded or it has been refined into an initiative which can be scaled.
      • Expect that most pilots will fail the first time, and many will fail completely. This is not a loss; lessons learned from the retrospective can be used to improve the process and later pilots.

      Use pilot projects to test and refine initiatives before scaling to the rest of the organization

      "Learning is as powerful as the outcome." – Brett Trelfa, CIO, Arkansas Blue Cross

      1. Clearly define the goals and objectives of the pilot project. Goals and objectives ensure that the pilot stays on track and can be measured.
      2. Your pilot group should include a variety of participants with diverse perspectives and skill sets, in order to gather unique insights.
      3. Continuously track the progress of the pilot project. Regularly identify areas of improvement and implement changes as necessary to refine ideas.
      4. Regularly elicit feedback from participants and iterate in order to improve the final innovation. Not all pilots will be successful, but every failure can help refine future solutions.
      5. Consider scalability. If the pilot project is successful, it should be scalable and the lessons learned should be implemented in the larger organization.

      Sample pilot metrics

      Metrics are used to validate and test pilot projects to ensure they deliver value. This is an important step before scaling to the rest of the organization.

      Adoption: How many end users have adopted the pilot solution?

      Utilization: Is the solution getting utilized?

      Support Requests: How many support requests have there been since the pilot was initiated?

      Value: Is the pilot delivering on the value that it proposed? For example, time savings.

      Feasibility: Has the feasibility of the solution changed since it was first proposed?

      Satisfaction: Focus groups or surveys can provide feedback on user/customer satisfaction.

      A/B Testing: Compare different methods, products or services.

      Info-Tech Insight

      Ensure standard core metrics are used across all pilot projects so that outcomes can be compared. Additional metrics may be used to refine and test hypotheses through the pilot process.

      Activity 3.2 Build your program to pilot initiatives

      1-2 hours

      1. Gather the innovation team and review your mandate, purpose, goals, and the sample innovation operating model and metrics.
      2. As a group, brainstorm the steps needed from idea generation to business case. Use sticky notes if in person, or a collaboration tool if remote.
      3. Determine the metrics that will be used to evaluate ideas at each decision step (for example, prior to piloting). Outline what the different decisions might be (for example, proceed, refine or discard) and what happens as a result of each decision.
      4. Document your final steps and metrics in the Innovation Program Template.

      Input

      • Innovation mandate
      • Innovation goals
      • Sample metrics

      Output

      • Pilot project methodology
      • Pilot project metrics

      Materials

      • Innovation Program Template
      • Sticky notes (in person) or digital collaboration tool (if remote)

      Participants

      • Innovation leader
      • Innovation team

      3.3 Conduct a program retrospective

      Generate value from your successful pilots by scaling ideas across the organization.

      • The final step in the innovation process is to scale ideas to the enterprise in order to realize the full potential.
      • Keeping track of notable wins is important for showing the value of the innovation program. Track performance of initiatives that come out of the innovation program, including their financial, cultural, market, and brand impacts.
      • Track the success of the innovation program itself by evaluating the number of ideas generated, the number of pilots run and the success of the pilots. Keep in mind that many failed pilots is not a failure of the program if the lessons learned were valuable.
      • Complete an innovation program retrospective every 6 to 12 months in order to adjust and make any changes if necessary to improve your process.

      Retrospectives should be objective, constructive, and action-oriented

      A retrospective is a review of your innovation program with the aim of identifying lessons learned, areas for improvement, and opportunities for growth.

      During a retrospective, the team will reflect on past experiences and use that information to inform future decision making and improve outcomes.

      The goal of a retrospective is to learn from the past and use that knowledge to improve in the future.

      Objective

      Ensure that the retrospective is based on facts and objective data, rather than personal opinions or biases.

      Constructive

      Ensure that the retrospective is a positive and constructive experience, with a focus on finding solutions rather than dwelling on problems.

      Action-Oriented

      The retrospective should result in a clear action plan with specific steps to improve future initiatives.

      Activity 3.3 Conduct a program retrospective

      1-2 hours

      1. Post a large piece of paper on the wall with a timeline from the last year. Include dates and a few key events, but not much more. Have participants place sticky notes in the spots to describe notable wins or milestones that they were proud of. This can be done as part of a formal meeting or asynchronously outside of meetings.
      2. Bring the innovation team together and review the poster with notable wins. Do any themes emerge? How does the team feel the program is doing? Are there any changes needed?
      3. Consider the metrics you use to track your innovation program success. Did the scaled projects meet their targets? Is there anything that could be refined about the innovation process?
      4. Evaluate the outcomes of your innovation program. Did it meet the targets set for it? Did the goals and innovation ambitions come to fruition?
      5. Complete this step every 6 to 12 months to assess the success of your program.
      6. Complete the "Notable Wins" section of the Innovation Program Template.

      Input

      • Innovation mandate
      • Innovation goals
      • Sample metrics

      Output

      • Notable wins
      • Action items for refining the innovation process

      Materials

      • Innovation Program Template
      • Sticky notes (in person) or digital collaboration tool (if remote)

      Participants

      • CIO
      • Innovation team
      • Others who have participated in the innovation process

      Related Info-Tech Research

      Adopt Design Thinking in Your Organization

      • 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.

      Prototype With an Innovation Design Sprint

      • Build and test a prototype in four days using Info-Tech's Innovation Design Sprint Methodology.
      • Create an environment for co-creation between IT and the business.

      Fund Innovation With a Minimum Viable Business Case

      • Our approach guides you through effectively designing a solution, de-risking a project through impact reduction techniques, building and pitching the case for your project, and applying the business case as a mechanism to ensure that benefits are realized.

      Summary of Accomplishment

      Congratulations on launching your innovation program!

      You have now completed your innovation strategy, covering the following topics:

      • Executive Summary
      • Our Purpose
      • Scope and Value Proposition
      • Guiding Principles
      • Building an Innovative Culture
      • Program Structure
      • Success Metrics
      • Notable Wins

      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.
      workshops@infotech.com 1-888-670-8889

      Related Info-Tech Research

      Accelerate Digital Transformation With a Digital Factory

      • 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.

      Sustain and Grow the Maturity of Innovation in Your Enterprise

      • Unlock your innovation potential by looking at your innovation projects on both a macro and micro level.
      • Innovation capacity is directly linked with creativity; allow your employees' creativity to flourish using Info-Tech's positive innovation techniques.

      Define Your Digital Business Strategy

      • Design a strategy that applies innovation to your business model, streamline and transform processes, and make use of technologies to enhance interactions with customers and employees.
      • Create a balanced roadmap that improves digital maturity and prepares you for long-term success in a digital economy.

      Research Contributors and Experts

      Kim Osborne Rodriguez

      Kim Osborne Rodriguez
      Research Director, CIO Advisory
      Info-Tech Research Group

      Kim is a professional engineer and Registered Communications Distribution Designer 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 Mechatronics Engineering from University of Waterloo.

      Joanne Lee

      Joanne Lee
      Principal Research Director, CIO Advisory
      Info-Tech Research Group

      Joanne is an executive with over 25 years of experience in digital technology and management consulting across both public and private entities from solution delivery to organizational redesign across Canada and globally.
      Prior to joining Info-Tech Research Group, Joanne was a management consultant within KPMG's CIO management consulting services and the Western Canadas Digital Health Practice lead. She has held several executive roles in the industry with the most recent position as Chief Program Officer for a large $450M EHR implementation. Her expertise spans cloud strategy, organizational design, data and analytics, governance, process redesign, transformation, and PPM. She is passionate about connecting people, concepts, and capital.
      Joanne holds a Master's in Business and Health Policy from the University of Toronto and a Bachelor of Science (Nursing) from the University of British Columbia.

      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 multi-billion-dollar organizations in multiple industries including Financial Services and Telecommunications. Jack also served a number of 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.

      Mike Schembri

      Mike Schembri
      Senior Executive Advisor
      Info-Tech Research Group

      Mike is the former CIO of Fuji Xerox Australia and has 20+ years' experience serving IT and wider business leadership roles. Mike has led technical and broader business service operations teams to value and growth successfully in organizations ranging from small tech startups through global IT vendors, professional service firms, and manufacturers.
      Mike has passion for strategy and leadership and loves working with individuals/teams and seeing them grow.

      John Leidl

      John Leidl
      Senior Director, Member Services
      Info-Tech Research Group

      With over 35 years of IT experience, including senior-level VP Technology and CTO leadership positions, John has a breadth of knowledge in technology innovation, business alignment, IT operations, and business transformation. John's experience extends from start-ups to corporate enterprise and spans higher education, financial services, digital marketing, and arts/entertainment.

      Joe Riley

      Joe Riley
      Senior Workshop Director
      Info-Tech Research Group

      Joe ensures our members get the most value out of their Info-Tech memberships by scoping client needs, current state and desired business outcomes, and then drawing upon his extensive experience, certifications, and degrees (MBA, MS Ops/Org Mgt, BS Eng/Sci, ITIL, PMP, Security+, etc.) to facilitate our client's achievement of desired and aspirational business outcomes. A true advocate of ITSM, Joe approaches technology and technology practices as a tool and enabler of people, core business, and competitive advantage activities.

      Denis Goulet

      Denis Goulet
      Senior Workshop Director
      Info-Tech Research Group

      Denis is a transformational leader and experienced strategist who has worked with 100+ organizations to develop their digital, technology, and governance strategies.
      He has held positions as CIO, Chief Administrative Office (City Manager), General Manager, Vice President of Engineering, and Management Consultant, specializing in enterprise and technology strategy.

      Cole Cioran

      Cole Cioran
      Managing Partner
      Info-Tech Research Group

      I knew I wanted to build great applications that would delight their users. I did that over and over. Along the way I also discovered that it takes great teams to deliver great applications. Technology only solves problems when people, processes, and organizations change as well. This helped me go from writing software to advising some of the largest organizations in the world on how to how to build a digital delivery umbrella of Product, Agile, and DevOps and create exceptional products and services powered by technology.

      Carlene McCubbin

      Carlene McCubbin
      Research Lead, CIO Practice
      Info-Tech Research Group

      During her tenure at Info-Tech, Carlene has led the development of Info-Tech's Organization and Leadership practice and worked with multiple clients to leverage the methodologies by creating custom programs to fit each organization's needs.
      Before joining Info-Tech, Carlene received her Master of Communications Management from McGill University, where she studied development of internal and external communications, government relations, and change management.

      Isabelle Hertanto

      Isabelle Hertanto
      Principal Research Director
      Info-Tech Research Group

      Isabelle Hertanto has over 15 years of experience delivering specialized IT services to the security and intelligence community. As a former federal officer for Public Safety Canada, Isabelle trained and led teams on data exploitation and digital surveillance operations in support of Canadian national security investigations. Since transitioning into the private sector, Isabelle has held senior management and consulting roles across a variety of industry sectors, including retail, construction, energy, healthcare, and the broader Canadian public sector.

      Hans Eckman

      Hans Eckman
      Principal Research Director
      Info-Tech Research Group

      Hans Eckman is a business transformation leader helping organizations connect business strategy and innovation to operational excellence. He supports Info-Tech members in SDLC optimization, Agile and DevOps implementation, CoE/CoP creation, innovation program development, application delivery, and leadership development. Hans is based out of Atlanta, Georgia.

      Valence Howden

      Valence Howden
      Principal Research Director
      Info-Tech Research Group

      With 30 years of IT experience in the public and private sector, Valence has developed experience in many Information Management and Technology domains, with a particular focus in the areas of Service Management, Enterprise and IT Governance, Development and Execution of Strategy, Risk Management, Metrics Design and Process Design, and Implementation and Improvement. Prior to joining Info-Tech, he served in technical and client-facing roles at Bell Canada and CGI Group Inc., as well as managing the design, integration, and implementation of services and processes in the Ontario Public Sector.

      Clayton Gillett

      Clayton Gillett
      Managing Partner
      Info-Tech Research Group

      Clayton Gillett is a Managing Partner for Info-Tech, providing technology management advisory services to healthcare clients. Clayton joined Info-Tech with more than 28 years of experience in health care information technology. He has held senior IT leadership roles at Group Health Cooperative of Puget Sound and OCHIN, as well as advisory or consulting roles at ECG Management Consultants and Gartner.

      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, multi-stakeholder industry initiatives.

      Igor Ikonnikov

      Igor Ikonnikov
      Research Director
      Info-Tech Research Group

      Igor Ikonnikov is a Research and Advisory Director in the Data and Analytics practice. Igor has extensive experience in strategy formation and execution in the information management domain, including master data management, data governance, knowledge management, enterprise content management, big data, and analytics.
      Igor has an MBA from the Ted Rogers School of Management (Toronto, Canada) with a specialization in Management of Technology and Innovation.

      Research Contributors and Experts

      Michael Newcity

      Michael Newcity
      Chief Innovation Officer
      ArcBest

      Kevin Yoder

      Kevin Yoder
      Vice President, Innovation
      ArcBest

      Gary Boyd

      Gary Boyd
      Vice President, Information Systems & Digital Transformation
      Arkansas Blue Cross and Blue Shield

      Brett Trelfa

      Brett Trelfa
      Chief Information Officer
      Arkansas Blue Cross and Blue Shield

      Kristen Wilson-Jones

      Kristen Wilson-Jones
      Chief Technology & Product Officer
      Medcurio

      Note: additional contributors did not wish to be identified

      Bibliography

      Altringer, Beth. "A New Model for Innovation in Big Companies" Harvard Business Review. 19 Nov. 2013. Accessed 30 Jan. 2023. https://hbr.org/2013/11/a-new-model-for-innovation-in-big-companies
      Arpajian, Scott. "Five Reasons Why Innovation Fails" Forbes Magazine. 4 June 2019. Accessed 31 Jan. 2023. https://www.forbes.com/sites/forbestechcouncil/2019/06/04/five-reasons-why-innovation-fails/?sh=234e618914c6
      Baldwin, John & Gellatly, Guy. "Innovation Capabilities: The Knowledge Capital Behind the Survival and Growth of Firms" Statistics Canada. Sept. 2006. Accessed 30 Jan. 2023. https://www.bdc.ca/fr/documents/other/innovation_capabilities_en.pdf
      Bar Am, Jordan et al. "Innovation in a Crisis: Why it is More Critical Than Ever" McKinsey & Company, 17 June 2020. Accessed 12 Jan. 2023. <https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/innovation-in-a-crisis-why-it-is-more-critical-than-ever >
      Boston Consulting Group, "Most Innovative Companies 2021" BCG, April 2021. Accessed 30 Jan. 2023. https://web-assets.bcg.com/d5/ef/ea7099b64b89860fd1aa3ec4ff34/bcg-most-innovative-companies-2021-apr-2021-r.pdf
      Boston Consulting Group, "Most Innovative Companies 2022" BGC, 15 Sept. 2022. Accessed 6 Feb. 2023. https://www.bcg.com/en-ca/publications/2022/innovation-in-climate-and-sustainability-will-lead-to-green-growth
      Christensen, Clayton M. The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail. Harvard Business Review Press, 2016.
      Gerber, Niklaus. "What is innovation? A beginner's guide into different models, terminologies and methodologies" Medium. 20 Sept 2022. Accessed 7 Feb. 2023. https://world.hey.com/niklaus/what-is-innovation-a-beginner-s-guide-into-different-models-terminologies-and-methodologies-dd4a3147
      Google X, Homepage. Accessed 6 Feb. 2023. https://x.company/
      Harnoss, Johann D. & Baeza, Ramón. "Overcoming the Four Big Barriers to Innovation Success" Boston Consulting Group, 24 Sept. 2019. Accessed 30 Jan 2023. https://www.bcg.com/en-ca/publications/2019/overcoming-four-big-barriers-to-innovation-success
      Jaruzelski, Barry et al. "Global Innovation 1000 Study" Pricewaterhouse Cooper, 30 Oct. 2018. Accessed 13 Jan. 2023. <https://www.strategyand.pwc.com/gx/en/insights/innovation1000.html>
      Kharpal, Arjun. "Huawei posts first-ever yearly revenue decline as U.S. sanctions continue to bite, but profit surges" CNBC. 28 March 2022. Accessed 7 Feb. 2023. https://www.cnbc.com/2022/03/28/huawei-annual-results-2021-revenue-declines-but-profit-surges.html
      Kirsner, Scott. "The Biggest Obstacles to Innovation in Large Companies" Harvard Business Review, 30 July 2018. Accessed 12 Jan. 2023. <https://hbr.org/2018/07/the-biggest-obstacles-to-innovation-in-large-companies>
      Macrotrends. "Apple Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/AAPL/apple/revenue
      Macrotrends. "Microsoft Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/MSFT/microsoft/revenue
      Macrotrends. "Amazon Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/AMZN/amazon/revenue
      Macrotrends. "Alphabet Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/GOOG/alphabet/revenue
      Macrotrends. "Tesla Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/TSLA/tesla/revenue
      Macrotrends. "Moderna Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/MRNA/moderna/revenue
      Macrotrends. "Sony Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/SONY/sony/revenue
      Macrotrends. "IBM Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/IBM/ibm/revenue
      Macrotrends. "Meta Platforms Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/META/meta-platforms/revenue
      Macrotrends. "NIKE Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/NKE/nike/revenue
      Macrotrends. "Walmart Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/WMT/walmart/revenue
      Macrotrends. "Dell Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/DELL/dell/revenue
      Macrotrends. "NVIDIA Revenue 2010-2022" Macrotrends. Accessed 23 Jan. 2023. https://www.macrotrends.net/stocks/charts/NVDA/nvidia/revenue
      Sloan, Paul. "How to Develop a Vision for Innovation" Innovation Management, 10 Aug. 2009. Accessed 7 Feb. 2023. https://innovationmanagement.se/2009/08/10/how-to-develop-a-vision-for-innovation/
      Statista. "Samsung Electronics' global revenue from 2005 to 2021" Statista. Accessed 7 Feb. 2023. https://www.statista.com/statistics/236607/global-revenue-of-samsung-electronics-since-2005/
      Tichy, Noel & Ram Charan. "Speed, Simplicity, Self-Confidence: An Interview with Jack Welch" Harvard Business Review, 2 March 2020. Accessed 7 Feb. 2023. https://hbr.org/1989/09/speed-simplicity-self-confidence-an-interview-with-jack-welch
      Weick, Karl and Kathleen Sutcliffe. Managing the Unexpected: Sustained Performance in a Complex World, Third Edition. John Wiley & Sons, 2015.
      Xuan Tian, Tracy Yue Wang, Tolerance for Failure and Corporate Innovation, The Review of Financial Studies, Volume 27, Issue 1, 2014, Pages 211–255, Accessed https://doi.org/10.1093/rfs/hhr130

      Establish Data Governance

      • Buy Link or Shortcode: {j2store}123|cart{/j2store}
      • member rating overall impact: 9.3/10 Overall Impact
      • member rating average dollars saved: $48,494 Average $ Saved
      • member rating average days saved: 31 Average Days Saved
      • Parent Category Name: Data Management
      • Parent Category Link: /data-management
      • Organizations are faced with challenges associated with changing data landscapes, evolving business models, industry disruptions, regulatory and compliance obligations, as well as changing and maturing user landscapes and demands for data.
      • Although the need for a data governance program is often evident, organizations often miss the mark.
      • Your data governance efforts should be directly aligned to delivering measurable business value by supporting key strategic initiatives, value streams, and underlying business capabilities.

      Our Advice

      Critical Insight

      • Your organization’s value streams and their associated business capabilities require effectively governed data. Without this, you may experience 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 organization’s enterprise governance function. It should not be perceived as a pet project of IT, but rather as an enterprise-wide, business-driven initiative.

      Impact and Result

      Info-Tech’s approach to establishing and sustaining effective data governance is anchored in the strong alignment of organizational value streams and their business capabilities with key data governance dimensions and initiatives. Info-Tech's approach will help you:

      • Align your data governance with enterprise governance, business strategy, and the 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.
      • Ensure data governance is supported by an operating model that effectively manages change and communication and fosters a culture of data excellence.

      Establish Data Governance 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 organization 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

      2. Data Governance Planning and Roadmapping Workbook – A structured tool to assist with establishing effective data governance practices.

      This workbook will help your organization understand the business and user context by leveraging your business capability map and value streams, develop data use cases using Info-Tech's framework for building data use cases, and gauge the current state of your organization's data culture.

      • Data Governance Planning and Roadmapping Workbook

      3. Data Use Case Framework Template – An exemplar template to highlight and create relevant use cases around the organization’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 organization. This template provides a framework for data requirements and a mapping methodology for creating use cases.

      • Data Use Case Framework Template

      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 organization plan the sequence of activities, capture start dates and expected completion dates, and create a roadmap that can be effectively communicated to the organization.

      • Data Governance Initiative Planning and Roadmap Tool

      5. Business Data Catalog – 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 organization.

      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 Catalog

      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

      7. Data Governance Policy

      This policy establishes uniform 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 organization.

      • Data Governance Policy

      8. Data Governance Exemplar – An exemplar showing how you can plan and document your data governance outputs.

      Use this exemplar to understand how to establish data governance in your organization. Follow along with the sections of the blueprint Establish Data Governance and complete the document as you progress.

      • Data Governance Exemplar
      [infographic]

      Workshop: Establish Data Governance

      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 organization 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 organization

      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 organization.

      Assess where the organization 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 organizational 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 organization 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 prioritize 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

      Prioritized initiatives with dependencies mapped out.

      A clearly communicated plan for data governance that will have full business backing.

      Activities

      4.1 Identify and prioritize 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

      Initialized roadmap

      Initialized RACI

      Further reading

      Establish Data Governance

      Deliver measurable business value.

      Executive Brief

      Analyst Perspective

      Establish a data governance program that brings value to your organization.

      Picture of analyst

      Data governance does not sit as an island on its own in the organization – it must align with and be driven by your enterprise governance. As you build out data governance in your organization, 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 organization’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 organization. Promote and drive the responsible and ethical use of data while helping to build and foster an organizational 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 organizations is growing at an exponential rate, creating a need to adopt a formal approach to governing data. However, many organizations 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

      Organizations 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, organizations 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 organizational value streams and their business capabilities with key data governance dimensions and initiatives. Organizations 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 organization’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 organizations build and sustain an effective data governance program.

      • Your organization has recognized 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 organization, 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 organization 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 organizations include:

      • Gaps in communicating the strategic value of data and data governance to the organization. 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 organization 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 organizational drivers for doing so. How is data governance going to support the organization’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 organization.
      • 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 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

      The journey to being data-driven

      The journey to declaring that you are a data-driven organization 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 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.

      Data governance is essential for any organization 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 organization.
      • 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.

      Organizational 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 organization.
      • 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: Organizational 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 Organization & Data Storytellers.

      Traditional data governance organizational 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 organizations follow a similar pattern when establishing committees, councils, and cross-functional groups. Most organizations 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 organization.

      A triangular model is depicted and is split into three tiers to show the traditional data governance organizational 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 centers of excellence to accelerate data initiatives, when only about 1 in 4 executives reported that their organization 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, organizations 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 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

      Absent or sub-optimal data governance leads to data debt

      Only 3% of companies’ data meets basic quality standards. (Source: Nagle, et al., 2017)

      Organizations suspect 28% of their customer and prospect data is inaccurate in some way. (Source: Experian, 2020)

      Only 51% of organizations consider the current state of their CRM or ERP data to be clean, allowing them to fully leverage it. (Source: Experian, 2020)

      35% of organizations 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 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.

      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 organization.

      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 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 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 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

      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 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 organization’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 organization. It must continuously align with the organization’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 organization.

      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 organization’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 organization. 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 organization.

      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 Organization’s Current Data Culture
      1. Formulate an Actionable Roadmap and Right-Sized Plan
      Phase Outcomes
      • Your organization’s business capabilities and value streams
      • A business capability map for your organization
      • Categorization of your organization’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 organization’s current data culture
      • A data governance roadmap and target-state plan comprising of prioritized 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 organization.

      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 organization’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 organization.

      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 organization scores across 10 areas relating to data culture.

      Key deliverable:

      Data Governance Planning and Roadmapping Workbook

      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 organization’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 Organization’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 organization’s business capabilities and value streams
      • A business capability map for your organization
      • Categorization of your organization’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 organization’s current data culture
      • A data governance roadmap and target-state plan comprising of prioritized 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 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

      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 organization
      • 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 prioritize 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 prioritize 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. Initialized roadmap
      2. Initialized RACI

      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 Organization’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 Categorize Your Organization’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 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 governance initiative planning that’s aligned with the organization’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 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 are reflective of the organization’s current business environment.
      • 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 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 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 organization

      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 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.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 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, 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 governance 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 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 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.

      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 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.

      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 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.

      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 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.

      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 organization’s value realization activities.

      Example value stream descriptions for: Retail

      Model example of value streams for retail

      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.

      For this value stream, download Info-Tech’s Industry Reference Architecture for Retail.

      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 above:

      • Analyze the value streams to identify and describe the organization’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 organization, remove the ones that don’t, and add any needed.

      Align data governance 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 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 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 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 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: 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 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

      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 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

      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 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

      Model example business capability map for retail

      For this business capability map, download Info-Tech’s Industry Reference Architecture for Retail.

      1.1.2 Categorize Your Organization’s Key Capabilities

      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.

      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)

      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 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 of business capabilities categorization 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 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, 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 organization.
      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 prioritize the data initiatives that deliver the most value to the organization.

      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, 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 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 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 prioritize the data initiatives that deliver the most value to the organization.

      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 categorized 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 organization

      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 organizational 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 organization.

      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.

      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.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 organization.

      Leveraging your business capability map, build use cases that align with the organization’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 organization (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 prioritized and leveraged for informing the business case and the data governance capabilities optimization 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 Organization’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 organization’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 the core components of an effective data governance program
      • An understanding your organization’s current data governance capabilities

      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 organization’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 organizational 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 organization’s data governance program.
      • For organizations 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 organization’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-organizational vision and strategy for data.
      • Owns and drives the data strategy; ensures it supports the overall organizational strategic direction and business goals.
      • Leads the organizational data initiatives, including data governance
      • Is accountable for the policy, strategy, data standards, and data literacy necessary for the organization 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 organization: ‘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 organization 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 organization, data owners will typically have the highest stake in that data.
      • Data owners need 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 catalog build, related tools and technology, policy management, etc.
      • Hold the influence needed to drive change in behavior and culture.
      • Act as ambassadors of data and its value as an organizational strategic asset.

      Right-size your data governance organizational structure

      • Most organizations 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 organization.
      • Your data governance structure has to work for your organization, and it has to evolve as the organization evolves.
      • Formulate your blend of data governance roles, committees, councils, and cross-functional groups, that make sense for your organization.
      • Your data governance organizational structure should not add complexity or bureaucracy to your organization’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 organizational structure.

      Example of a Data Governance Organizational 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 organization’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 organization.

      “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 organization and manages risks while building and fostering a culture of data excellence along the way. Some organizations 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 organized, 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 organizations, sectors, and industries. Every organization has its own particular drivers and mandates, so the level and rigor applied will also vary.
      • The key is to determine what style will work best in your organization, taking into consideration your organizational culture, executive leadership support (present and ongoing), catalysts such as other enterprise-wide transformative and modernization 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 organization, 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 organization 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 organizations invest in change management to build data supporters and convert the skeptics. 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 organizational 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 organization’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 realization of tangible business value are a must for sustaining, growing, and scaling your data governance program.
      • Aligning your data governance to the organization's value realization 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 organization. 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 standardize 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 organization.
      • 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 organization.
      • Data policies can be thought of as formal statements and are typically created, approved, and updated by the organization’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 standardize 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 organization’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 organization.

      Examples of data policies:

      • Data Classification Policy
      • Data Retention Policy
      • Data Entry Policy
      • Data Backup Policy
      • Data Provenance Policy
      • Data Management Policy

      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

      “Organizational 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 organization’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 catalog 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 realize its full return without building up the organization’s data literacy.
      • Data literacy is about filling data knowledge gaps across all levels of the organization.
      • 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 organization’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 organization.

      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 catalog 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 organization’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 organization’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 organizations 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 organization’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 organizations 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 organization 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 organization regularly audits and monitors its data security.

      Ethical Use & Handling of Data

      Data governance will support your organization’s ethical use and handling of data by facilitating definition around important factors, such as:

      • What are the various data assets in the organization 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 organization’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 organization’s direct stakeholders and/or the public at large, lead to a loss of trust and confidence in the organization's products and services, lead to financial loss, and impact the organization’s brand, reputation, and legal standing.
      • Data governance plays a vital role in 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 organization to define, categorize, and confidently make decisions about its data.

      Step 2.2

      Gauge Your Organization’s Current Data Culture

      Activities

      2.2.1 Gauge Your Organization’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 organization’s data culture

      Outcomes of this step

      • An understanding of your organizational data culture

      2.2.1 Gauge Your Organization’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 organization'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 organization’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 organization who should receive the survey

      Output

      • Your organization’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 organization

      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 organization
      • 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 prioritized 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 prioritized initiatives

      Outcomes of this step

      • A foundation for data governance initiative planning that’s aligned with the organization’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 organization.

      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 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 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 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 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 & Prioritization

      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

      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 formalize 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 catalog starting with identified and prioritized 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, rationalize, 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 organization).
      • Define and formalize 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 organization’s PMO, conduct “Data Governance 101” for the PMO.

      Defining data governance roles and organizational structure at Organization

      The approach employed for defining the data governance roles and supporting organizational structure for .

      Key Considerations:

      • The data owner and data steward roles are formally defined and documented within the organization. Their involvement is clear, well-defined, and repeatable.
      • There are data owners and data stewards for each data domain within the organization. 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 organization 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 organization. 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 organization’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 catalog
      • 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 organizational 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 organization, 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 organization 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 organization believe in the initiative, understand the anticipated outcomes, and take some level of responsibility for its success.

      Changes to organizational 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 organizational 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 organization’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 organization, 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 organization. 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 organization

      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 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 governance 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.

      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 organization.

      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 organization.

      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 organization, 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 formalized process for implementing new policies, rules, guidelines, and technologies, and managing organizational data.
      • Detail data ownership and accountability for decision making, and identify and resolve data issues throughout the organization.
      • 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 standardized data policies will help validate how data governance will benefit them and the organization.

      Leverage the data governance program to communicate and promote the value of data within the organization

      The data governance program is responsible for continuously promoting the value of data to the organization. The data governance program should seek a variety of ways to educate the organization 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 organizational change, refer to Info-Tech’s Master Organizational 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 organizations 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 centralized website.
      • Link this repository to other policies’ taxonomies of your organization. E.g. HR policies to provide a single interface for employees to access guidance across the organization.
      • Reassess policies annually at a minimum. myPolicies can remind you to update the organization’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 organizations, 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 organization’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 Authorization, Identification, and Authentication Policy Template
      • Data Protection Policy

      Compliance

      • Archiving Policy
      • Data Classification Policy
      • Data Retention Policy

      Leverage data management-related policies to standardize 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 organization. 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 organization. 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 Virtualization Policy:

      This policy aims to assure the organization, staff, and other interested parties that data integration, replication, and virtualization risks are taken seriously. Staff must use the policy (and supporting guidelines) when deciding whether to integrate, replicate, or virtualize 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 organization.

      • 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 organizational lines of business

      A data governance program will impact all data-driven business units within the organization.

      • 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 organization. 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 organization to maintain reliable and useful data.

      Data standards and procedural guidelines will vary from company to company.

      Examples include:

      • Data modeling 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 organizational 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 organization’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 organization, 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 organizational 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 organization. That disruption doesn’t have to be detrimental if you are prepared to manage the change proactively and effectively.

      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.

      Redman, Thomas, et al. “Only 3% of Companies’ Data Meets Basic Quality Standards.” Harvard Business Review. 11 Sept 2017.

      Petzold, Bryan, et al. “Designing data governance that delivers value.” McKinsey & Company, 26 June 2020. Accessed 25 June 2021.

      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.

      Make the Case for Legacy Application Modernization

      • Buy Link or Shortcode: {j2store}613|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
      • Organizations are under continual pressure to deliver faster, with shorter time-to-market, while introducing new products and services at the same time.
      • You and your team have concerns that your existing portfolio of applications is not up to the task.
      • While you understand the need for more investments to modernize your portfolio, your leadership does not appreciate what is required.

      Our Advice

      Critical Insight

      • Legacy modernization is a process, not a single event.
      • Your modernization approach requires you to understand your landscape and decide on a path that minimizes business continuity risks, keeps the investments under control, and is prepared for surprises but always has your final state in mind.

      Impact and Result

      • Evaluate the current state, develop a legacy application strategy, and execute in an agile manner.
      • When coupled with a business case and communications strategy, this approach gives the organization a clear decision-making framework that will maximize business outcomes and deliver value where needed.

      Make the Case for Legacy Application Modernization Research & Tools

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

      1. Make the Case for Legacy Application Modernization Storyboard – Understand legacy application modernization in the context of your organization, assess your landscape of applications, and define prioritization and disposition.

      This blueprint provides the steps necessary to build your own enterprise application implementation playbook that can be deployed and leveraged by your implementation teams.

      • Make the Case for Legacy Application Modernization Storyboard

      2. Make the Case for Legacy Application Modernization Presentation Template – The key output from leveraging this research is a presentation to pitch the modernization process.

      Build a proposal deck to make the case for legacy application modernization for your stakeholders. This will contain a definition of what a legacy application is in the context of your organization, a list of candidate applications to modernize, and a disposition strategy for each selected application.

      • Make the Case for Legacy Application Modernization Presentation Template
      [infographic]

      Further reading

      Make the Case for Legacy Application Modernization

      Revamp your business potential to improve agility, security, and user experience while reducing costs.

      Analyst Perspective

      An old application may have served us reliably, but it can prevent us from pursuing future business needs.

      Legacy systems remain well-embedded in the fabric of many organizations' application portfolios. They were often custom-built to meet the needs of the business. Typically, these are core tools that the business leverages to accomplish its goals.

      A legacy application becomes something we need to address when it no longer supports our business goals, is no longer supportable, bears an unsustainable ownership cost, or poses a threat to the organization's cybersecurity or compliance.

      When approaching your legacy application strategy, you must navigate a complex web of business, stakeholder, software, hardware, resourcing, and financial decisions. To complicate matters, the full scope of required effort is not immediately clear. Years of development are embedded in these legacy applications, which must be uncovered and dealt with appropriately.

      IT leaders require a proactive approach for evaluating the current state, developing a legacy application strategy, and executing in an agile manner. When coupled with a business case and communications strategy, the organization will have a clear decision-making framework that will maximize business outcomes and deliver value where needed.

      Ricardo de Oliveira, Research Director, Enterprise Applications

      Ricardo de Oliveira
      Research Director, Enterprise Applications
      Info-Tech Research Group

      Executive Summary

      Your Challenge Common Obstacles Info-Tech's Approach
      • Organizations face continual pressure to decrease time-to-market while also introducing new products and services.
      • You and your team have concerns that the existing application portfolio is not up to the task.
      • While you may understand the need for greater investment to modernize your portfolio, leadership does not appreciate what is required.
      • For well-established organizations, applications can have a long lifespan. Employees who are used to existing tools and processes often resist change.
      • Modernization plans can be substantial, but budget and resources are limited.
      • Poor documentation of legacy applications can make it challenging to know what to modernize and how to do it effectively.
      • There are concerns that any changes will have material impacts on business continuity.
      • Info-Tech will enable you to build a proposal deck to make the case for legacy application modernization for your stakeholders. This will assist with:
        • Defining what a legacy application is in the context of your organization.
        • Creating a list of candidate applications for modernization.
        • Articulating the right disposition strategy for each selected applications.
        • Laying out what is next on your modernization journey.

      Info-Tech Insight
      Legacy modernization is a process, not a single event. Your modernization approach requires you to understand your landscape and decide on a path that minimizes business continuity risks, keeps investments under control, and is prepared for surprises but always has your final state in mind.

      An approach to making the case for legacy application modernization

      Understand
      Assess the challenges, lay out the reasons, define your legacy, and prepare to remove the barriers to modernization.
      Assess
      Determine the benefits by business capability. Leverage APM foundations to select the candidate applications and prioritize.
      Legacy Application Modernization
      Define
      Use the prioritized application list to drive the next steps to modernization.

      Legacy application modernization is perceived as necessary to remain competitive

      The 2022 State CIO Survey by NASCIO shows that legacy application modernization jumped from fifth to second in state CIO priorities.

      "Be patient and also impatient. Patient because all states have a lot of legacy tech they are inheriting and government is NOT easy. But also, impatient because there is a lot to do - make your priorities clear but also find out what the CIO needs to accomplish those priorities."

      Source: NASCIO, 2022

      State CIO Priorities

      US government agencies feel pressured to deal with legacy applications

      In fiscal year 2021, the US government planned to spend over $100 billion on information technology. Most of that was to be used to operate and maintain existing systems, including legacy applications, which can be both more expensive to maintain and more vulnerable to hackers. The Government Accountability Office (GAO) identified:

      • 10 critical federal IT legacy systems
      • In operation between 8 and 51 years
      • Collectively cost $337 million per year to operate and maintain

      Source: U.S. Government Accountability Office, 2021

      Example: In banking, modern platforms are essential

      Increasing competition from fintech 73% of financial services executives perceive retail banking as being the most susceptible to fintech disruption (PwC, 2016)
      Growing number of neo-banks The International Monetary Fund (IMF) notes the fast growth of fintech in financial services is creating systemic risk to global financial stability (IMF, 2022)
      Access to data and advanced analytics Estimated global bank revenue lost due to poor data is 15% to 25% (MIT, 2017)
      Shifting client expectations/demographics 50% of Gen X, millennials, and Gen Z use a digital bank to provide their primary checking account (Finextra, 2022)
      Generational transfer of wealth It is estimated that up to US$68 trillion in wealth will be transferred from baby boomers (Forbes, 2021)

      Case Study

      Delta takes off with a modernized blend of mainframes and cloud

      INDUSTRY: Transportation
      SOURCE: CIO Magazine, 2023

      Challenge
      The airline has hundreds of applications in the process of moving to the cloud, but most main capabilities are underpinned by workloads on the mainframe and will remain so for the foreseeable future.
      Some of those workloads include travel reservation systems and crew scheduling systems - mission-critical, 24/7 applications that are never turned off.
      Solution
      Delta has shifted to a hybrid architecture, with a customer experience transformation that makes the most of the cloud's agility and the mainframe's dependability.
      Delta's foray into the cloud began about two years ago as the pandemic brought travel to a virtual halt. The airline started migrating many front-end and distributed applications to the cloud while retaining traditional back-end workloads on the mainframe.
      Results
      Hybrid infrastructures are expected to remain in complex industries such as airlines and banking, where high availability and maximum reliability are non-negotiable.
      While some CIOs are sharpening their mainframe exit strategies by opting for a steep journey to the cloud, mainframes remain ideal for certain workloads.

      Phase 1: Make the Case for Legacy Application Modernization

      Phase 1
      1.1 Understand your challenges
      1.2 Define legacy applications
      1.3 Assess your barriers
      1.4 Find the impacted capabilities
      1.5 Define candidate applications
      1.6 Now, Next, Later

      This phase will walk you through the following activities:

      • Understand your challenges with modernization
      • Define legacy applications in your context
      • Assess your barriers to modernization
      • Find the impacted capabilities and their benefits
      • Define candidate applications and dispositions

      This phase involves the following participants:

      • Application group leaders
      • Individual application owners

      Quality Management

      • Buy Link or Shortcode: {j2store}45|cart{/j2store}
      • Related Products: {j2store}45|crosssells{/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 Planning and Architecture
      • Parent Category Link: /service-planning-and-architecture
      Drive efficiency and agility with right-sized quality management

      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.

      Understand the Data and Analytics Landscape

      • Buy Link or Shortcode: {j2store}131|cart{/j2store}
      • member rating overall impact: 9.8/10 Overall Impact
      • member rating average dollars saved: $2,000 Average $ Saved
      • member rating average days saved: 14 Average Days Saved
      • Parent Category Name: Data Management
      • Parent Category Link: /data-management
      • The data and analytics landscape comprises many disciplines and components; organizations may find themselves unsure of where to start or what data topic or area they should be addressing.
      • Organizations want to better understand the components of the data and analytics landscape and how they are connected.

      Our Advice

      Critical Insight

      • This deck will provide a base understanding of the core data disciplines and will point to the various Info-Tech blueprints that dive deeper into each of the areas.

      Impact and Result

      • This deck will provide a base understanding of the core disciplines of the data and analytics landscape and will point to the various Info-Tech blueprints that dive deeper into each of the areas.

      Understand the Data and Analytics Landscape Research & Tools

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

      1. Understand the data and analytics landscape

      Get an overview of the core disciplines of the data and analytics landscape.

      • Understand the Data and Analytics Landscape Storyboard

      Infographic

      Prepare for Cognitive Service Management

      • Buy Link or Shortcode: {j2store}335|cart{/j2store}
      • member rating overall impact: 9.0/10 Overall Impact
      • member rating average dollars saved: 10 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: Strategy and Organizational Design
      • Parent Category Link: /strategy-and-organizational-design
      • The evolution of natural language processing and machine learning applications has led to specialized AI-assisted toolsets that promise to improve the efficiency and timeliness of IT operations.

      Our Advice

      Critical Insight

      • These are early days. These AI-assisted toolsets are generating a considerable amount of media attention, but most of them are relatively untested. Early adopters willing to absorb experimentation costs are in the process of deploying the first use cases. Initial lessons are showing that IT operations in most organizations are not yet mature enough to take advantage of AI-assisted toolsets.
      • Focus on the problem, not the tool. Explicit AI questions should be at the end of the list. Start by asking what business problem you want to solve.
      • Get your house in order. The performance of AI-assisted tools depends on mature IT operations processes and reliable data sets. Standardize service management processes and build a knowledgebase of structured content to prepare for AI-assisted IT operations.

      Impact and Result

      • Don’t fall prey to the AI-bandwagon effect. AI-assisted innovations will support shift-left service support strategies through natural language processing and machine learning applications. However, the return on your AI investment will depend on whether it helps you meet an actual business goal.
      • AI-assisted tools presuppose the existence of mature IT operations functions, including standardized processes, high-quality structured content focused on the incidents and requests that matter, and a well-functioning ITSM web portal.
      • The success of AI ITSM projects hinges on adoption. If your vision is to power end-user interactions with chatbots and deploy intelligent agents on tickets coming through the web portal, be sure to develop a self-service culture that empowers end users to help themselves and experiment with new tools and technologies. Without end-user adoption, the promised benefits of AI projects will not materialize.

      Prepare for Cognitive Service Management Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should prepare for cognitive service 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:

      1. Review emerging AI technology

      Get an overview of emerging AI applications to understand how they will strengthen a shift-left service support strategy.

      2. Sort potential IT operations AI use cases

      Review potential use cases for AI applications to prioritize improvement initiatives and align them to organizational goals.

      • Disruptive Technology Shortlisting Tool
      • Disruptive Technology Value-Readiness and SWOT Analysis Tool

      3. Prepare for a cognitive service management project

      Develop an ITSM AI strategy to prepare your organization for the coming of cognitive service management, and build a roadmap for implementation.

      • Customer Journey Map (PDF)
      • Customer Journey Map (Visio)
      • Infrastructure Roadmap Technology Assessment Tool
      • Strategic Infrastructure Roadmap Tool
      [infographic]

      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.

      Improve Security Governance With a Security Steering Committee

      • Buy Link or Shortcode: {j2store}373|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: 20 Average Days Saved
      • Parent Category Name: Governance, Risk & Compliance
      • Parent Category Link: /governance-risk-compliance
      • Security is still seen as an IT problem rather than a business risk, resulting in security governance being relegated to the existing IT steering committee.
      • Security is also often positioned in the organization where they are not privy to the details of the organization’s overall strategy. Security leaders struggle to get the full enterprise picture.

      Our Advice

      Critical Insight

      • Work to separate the Information Security Steering Committee (ISSC) from the IT Steering Committee (ITSC). Security transcends the boundaries of IT and needs an independent, eclectic approach to make strategic decisions.
      • Be the lawyer, not the cop. Ground your communications in business terminology to facilitate a solution that makes sense to the entire organization.
      • Develop and stick to the agenda. Continued engagement from business stakeholders requires sticking to a strategic level-focused agenda. Dilution of purpose will lead to dilution in attendance.

      Impact and Result

      • Define a clear scope of purpose and responsibilities for the ISSC to gain buy-in and consensus for security governance receiving independent agenda time from the broader IT organization.
      • Model the information flows necessary to provide the steering committee with the intelligence to make strategic decisions for the enterprise.
      • Determine membership and responsibilities that shift with the evolving security landscape to ensure participation reflects interested parties and that money being spent on security mitigates risk across the enterprise.
      • Create clear presentation material and strategically oriented meeting agendas to drive continued participation from business stakeholders and executive management.

      Improve Security Governance With a Security Steering Committee Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out how to improve your security governance with a security steering committee, 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. Define committee purpose and responsibilities

      Identify the purpose of your committee, determine the capabilities of the committee, and define roles and responsibilities.

      • Improve Security Governance With a Security Steering Committee – Phase 1: Define Committee Purpose and Responsibilities
      • Information Security Steering Committee Charter

      2. Determine information flows, membership & accountabilities

      Determine how information will flow and the process behind that.

      • Improve Security Governance With a Security Steering Committee – Phase 2: Determine Information Flows, Membership & Accountabilities

      3. Operate the Information Security Steering Committee

      Define your meeting agendas and the procedures to support those meetings. Hold your kick-off meeting. Identify metrics to measure the committee’s success.

      • Improve Security Governance With a Security Steering Committee – Phase 3: Operate the Information Security Steering Committee
      • Security Metrics Summary Document
      • Information Security Steering Committee Stakeholder Presentation
      [infographic]

      Further reading

      Improve Security Governance With a Security Steering Committee

      Build an inclusive committee to enable holistic strategic decision making.

      ANALYST PERSPECTIVE

      "Having your security organization’s steering committee subsumed under the IT steering committee is an anachronistic framework for today’s security challenges. Conflicts in perspective and interest prevent holistic solutions from being reached while the two permanently share a center stage.

      At the end of the day, security is about existential risks to the business, not just information technology risk. This focus requires its own set of business considerations, information requirements, and delegated authorities. Without an objective and independent security governance body, organizations are doomed to miss the enterprise-wide nature of their security problems."

      – Daniel Black, Research Manager, Security Practice, Info-Tech Research Group

      Our understanding of the problem

      This Research Is Designed For:

      • CIOs
      • CISOs
      • IT/Security Leaders

      This Research Will Help You:

      • Develop an effective information security steering committee (ISSC) that ensures the right people are involved in critical decision making.
      • Ensure that business and IT strategic direction are incorporated into security decisions.

      This Research Will Also Assist:

      • Information Security Steering Committee (ISSC) members

      This Research Will Help Them:

      • Formalize roles and responsibilities.
      • Define effective security metrics.
      • Develop a communication plan to engage executive management in the organization’s security planning.

      Executive summary

      Situation

      • Successful information security governance requires a venue to address security concerns with participation from across the entire business.
      • Without access to requisite details of the organization – where we are going, what we are trying to do, how the business expects to use its technology – security can not govern its strategic direction.

      Complication

      • Security is still seen as an IT problem rather than a business risk, resulting in security governance being relegated to the existing IT steering committee.
      • Security is also often positioned in the organization where they are not privy to the details of the organization’s overall strategy. Security leaders struggle to get the full enterprise picture.

      Resolution

      • Define a clear scope of purpose and responsibilities for the Information Security Steering Committee to gain buy-in and consensus for security governance receiving independent agenda time from the broader IT organization.
      • Model the information flows necessary to provide the steering committee with the intelligence to make strategic decisions for the enterprise.
      • Determine membership and responsibilities that shift with the evolving security landscape to ensure participation reflects interested parties and that money being spent on security mitigates risk across the enterprise.
      • Create security metrics that are aligned with committee members’ operational goals to incentivize participation.
      • Create clear presentation material and strategically oriented meeting agendas to drive continued participation from business stakeholders and executive management.

      Info-Tech Insight

      1. Work to separate the ISSC from the IT Steering Committee (ITSC). Security transcends the boundaries of IT and needs an independent, eclectic approach to make strategic decisions.
      2. Be the lawyer, not the cop. Ground your communications in business terminology to facilitate a solution that make sense to the entire organization.
      3. Develop and stick to the agenda. Continued engagement from business stakeholders requires sticking to a strategic level-focused agenda. Dilution of purpose will lead to dilution in attendance.

      Empower your security team to act strategically with an ISSC

      Establishing an Information Security Steering Committee (ISSC)

      Even though security is a vital consideration of any IT governance program, information security has increasingly become an important component of the business, moving beyond the boundaries of just the IT department.

      This requires security to have its own form of steering, beyond the existing IT Steering Committee, that ensures continual alignment of the organization’s security strategy with both IT and business strategy.

      An ISSC should have three primary objectives:

      • Direct Strategic Planning The ISSC formalizes organizational commitments to strategic planning, bringing visibility to key issues and facilitating the integration of security controls that align with IT and business strategy.
      • Institute Clear Accountability The ISSC facilitates the involvement and commitment of executive management through clearly defined roles and accountabilities for security decisions, ensuring consistency in participation as the organization’s strategies evolve.
      • Optimize Security Resourcing The ISSC maximizes security by monitoring the implementation of the security strategic plan, making recommendations on prioritization of effort, and securing necessary resources through the planning and budgeting processes, as necessary.

      What does the typical ISSC do?

      Ensuring proper governance over your security program is a complex task that requires ongoing care and feeding from executive management to succeed.

      Your ISSC should aim to provide the following core governance functions for your security program:

      1. Define Clarity of Intent and Direction How does the organization’s security strategy support the attainment of the business and IT strategies? The ISSC should clearly define and communicate strategic linkage and provide direction for aligning security initiatives with desired outcomes.
      2. Establish Clear Lines of Authority Security programs contain many important elements that need to be coordinated. There needs to be clear and unambiguous authority, accountability, and responsibility defined for each element so lines of reporting/escalation are clear and conflicting objectives can be mediated.
      3. Provide Unbiased Oversight The ISSC should vet the organization’s systematic monitoring processes to make certain there is adherence to defined risk tolerance levels and ensure that monitoring is appropriately independent from the personnel responsible for implementing and managing the security program.
      4. Optimize Security Value Delivery Optimized value delivery occurs when strategic objectives for security are achieved and the organization’s acceptable risk posture is attained at the lowest possible cost. This requires constant attention to ensure controls are commensurate with any changes in risk level or appetite.

      Formalize the most important governance functions for your organization

      Creation of an ISSC is deemed the most important governance and oversight practice that a CISO can implement, based on polling of IT security leaders analyzing the evolving role of the CISO.

      Relatedly, other key governance practices reported – status updates, upstream communications, and executive-level sponsorship – are within the scope of what organizations traditionally formalize when establishing their ISSC.

      Vertical bar chart highlighting the most important governance functions according to respondents. The y axis is labelled 'Percentage of Respondents' with the values 0%-60%, and the x axis is labelled 'Governance and Oversight Practices'. Bars are organized from highest percentage to lowest with 'Creation of cross-functional committee to oversee security strategy' at 56%, 'Regularly scheduled reporting on the state of security to stakeholders' at 55%, 'Upstream communication channel from security leadership to CEO' at 46%, and 'Creation of program charter approved by executive-level sponsor' at 37%. Source: Ponemon Institute, 2017; N=184 organizations; 660 respondents.

      Despite the clear benefits of an ISSC, organizations are still falling short

      83% of organizations have not established formal steering committees to evaluate the business impact and risks associated with security decisions. (Source: 2017 State of Cybersecurity Metrics Report)

      70% of organizations have delegated cybersecurity oversight to other existing committees, providing security limited agenda time. (Source: PwC 2017 Annual Corporate Director Survey)

      "This is a group of risk managers an institution would bring together to deal with a response anyway. Having them in place to do preventive discussions and formulate policy to mitigate the liability sets and understand compliance obligations is just powerful." (Kirk Bailey, CISO, University of Washington)

      Prevent the missteps that make 9 out of 10 steering committees unsuccessful

      Why Do Steering Committees Fail?

      1. A lack of appetite for a steering committee from business partners. An effective ISSC requires participation from core members of the organization’s leadership team. The challenge is that most business partners don’t understand the benefits of an ISSC and the responsibilities aren’t tailored to participants’ needs or interests. It’s the CISO’s (or senior IT/security leader’s) responsibility to make this case to stakeholders and right-size the committee responsibilities and membership.
      2. ISSC committees are given inappropriate responsibilities. The steering committee is fundamentally about decision making; it’s not a working committee. Security leadership typically struggles with clarifying these responsibilities on two fronts: either the responsibilities are too vague and there is no clear way to execute on them within a meeting or responsibilities are too tactical and require knowledge that participants do not have. Responsibilities should determine who is on the ISSC, not the other way around.
      3. Lack of process around execution. An ISSC is only valuable if members are able to successfully execute on its mandate. Without well-defined processes it becomes nearly impossible for the ISSC to be actionable. As a result, participants lack the information they need to make critical decisions, agendas are unmet, and meetings are seen as a waste of time.

      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

      Improve Security Governance With a Security Steering Committee – project overview

      1. Define Committee Purpose and Responsibilities

      2. Determine Information Flows, Membership & Accountabilities

      3. Operate the Information Security Steering Committee

      Supporting Tool icon

      Best-Practice Toolkit

      1.1 Tailor Info-Tech’s Information Security Steering Committee Charter Template to define terms of reference for the ISSC

      1.2 Conduct a SWOT analysis of your information security governance capabilities

      1.3 Identify the responsibilities and duties of the ISSC

      1.4 Draft the committee purpose statement of your ISSC

      2.1 Define your SIPOC model for each of the ISSC responsibilities

      2.2 Identify committee participants and responsibility cadence

      2.3 Define ISSC participant RACI for each of the responsibilities

      3.1 Define the ISSC meeting agendas and procedures

      3.2 Define which metrics you will report to the ISSC

      3.3 Hold a kick-off meeting with your ISSC members to explain the process, responsibilities, and goals

      3.4 Tailor the Information Security Steering Committee Stakeholder Presentation template

      3.5 Present the information to the security leadership team

      3.6 Schedule your first meeting of the ISSC

      Guided Implementations

      • Identify the responsibilities and duties of the ISSC.
      • Draft the committee purpose of the ISSC.
      • Determine SIPOC modeling of information flows.
      • Determine accountabilities and responsibilities.
      • Set operational standards.
      • Determine effectiveness metrics.
      • Steering committee best practices.
      Associated Activity icon

      Onsite Workshop

      This blueprint can be combined with other content for onsite engagements, but is not a standalone workshop.
      Phase 1 Outcome:
      • Determine the purpose and responsibilities of your information security steering committee.
      Phase 2 Outcome:
      • Determine membership, accountabilities, and information flows to enable operational excellence.
      Phase 3 Outcome:
      • Define agendas and standard procedures to operate your committee.
      • Design an impactful stakeholder presentation.

      Improve Security Governance With a Security Steering Committee

      PHASE 1

      Define Committee Purpose and Responsibilities

      Phase 1: Define Committee Purpose and Responsibilities

      ACTIVITIES:

      • 1.1 Tailor Info-Tech’s Information Security Steering Committee Charter Template to define terms of reference for the ISSC
      • 1.2 Conduct a SWOT analysis of your information security governance capabilities
      • 1.3 Identify the responsibilities and duties of the ISSC
      • 1.4 Draft the committee purpose statement for your ISSC

      OUTCOMES:

      • Conduct an analysis of your current information security governance capabilities and identify opportunities and weaknesses.
      • Define a clear scope of purpose and responsibilities for your ISSC.
      • Begin to customize your ISSC charter.

      Info-Tech Insight

      Balance vision with direction. Purpose and responsibilities should be defined so that they encompass your mission and objectives to the enterprise in clear terms, but provide enough detail that you can translate the charter into operational plans for the security team.

      Tailor Info-Tech’s Information Security Steering Committee Charter Template to define terms of reference for the ISSC

      Supporting Tool icon 1.1

      A charter is the organizational mandate that outlines the purpose, scope, and authority of the ISSC. Without a charter, the steering committee’s value, scope, and success criteria are unclear to participants, resulting in unrealistic stakeholder expectations and poor organizational acceptance.

      Start by reviewing Info-Tech’s template. Throughout the next two sections we will help you to tailor its contents.

      • Committee Purpose: The rationale, benefits of, and overall function of the committee.
      • Organization and Membership: Who is on the committee and how is participation measured against organizational need.
      • Responsibilities and Duties: What tasks/decisions the accountable committee is making.
      • RACI: Who is accountable, responsible, consulted, and informed regarding each responsibility.
      • Committee Procedures and Agendas: Includes how the committee will be organized and how the committee will interact and communicate with interested parties.
      Sample of the Info-Tech deliverable 'Information Security Steering Committee Charter Template'.

      Download the Information Security Steering Committee Charter to customize your organization’s charter

      Conduct a SWOT analysis of your information security governance capabilities

      Associated Activity icon 1.2

      INPUT: Survey outcomes, Governance overview handouts

      OUTPUT: SWOT analysis, Top identified challenges and opportunities

      1. Hold a meeting with your IT leadership team to conduct a SWOT analysis on your current information security governance capabilities.
      2. In small groups, or individually, have each group complete a SWOT analysis for one of the governance areas. For each consider:
        • Strengths: What is currently working well in this area?
        • Weaknesses: What could you improve? What are some of the challenges you’re experiencing?
        • Opportunities: What are some organizational trends that you can leverage? Consider whether your strengths or weaknesses could create opportunities.
        • Threats: What are some key obstacles across people, process, and technology?
      3. Have each team or individual rotate until each person has contributed to each SWOT. Add comments from the stakeholder survey to the SWOT.
      4. As a group, rank the inputs from each group and highlight the top five challenges and the top five opportunities you see for improvement.

      Identify the responsibilities and duties of the ISSC

      Associated Activity icon 1.3

      INPUT: SWOT analysis, Survey reports

      OUTPUT: Defined ISSC responsibilities

      1. With your security leadership team, review the typical responsibilities of the ISSC on the following slides (also included in the templated text of the charter linked below).
      2. Print off the following two slides, and in small teams or individually, identify which responsibilities the ISSC should have in your organization, brainstorm any additional responsibilities, and document reasoning.
      3. Have each team present to the larger group, track the similarities and differences between each of the groups, and come to consensus on the list of categories and responsibilities.
      4. Complete a sanity check: review your SWOT analysis. Do the responsibilities you’ve identified resolve the critical challenges or weaknesses?
      5. As a group, consider the responsibilities and whether you can reasonably implement those in one year or if there are any that will need to wait until year two of the committee.

      Add or modify responsibilities in Info-Tech’s Information Security Steering Committee Charter.

      Typical ISSC responsibilities and duties

      Use the following list of responsibilities to customize the list of responsibilities your ISSC may take on. These should link directly to the Responsibilities and Duties section of your ISSC charter.

      Strategic Oversight

      • Provide oversight and ensure alignment between information security strategy and company objectives.
      • Assess the adequacy of resources and funding to sustain and advance successful security programs and practices for identifying, assessing, and mitigating cybersecurity risks across all business functions.
      • Review controls to prevent, detect, and respond to cyber-attacks or information or data breaches involving company electronic information, intellectual property, data, or connected devices.
      • Review the company’s cyberinsurance policies to ensure appropriate coverage.
      • Provide recommendations, based on security best practices, for significant technology investments.

      Policy Governance

      • Review company policies pertaining to information security and cyberthreats, taking into account the potential for external threats, internal threats, and threats arising from transactions with trusted third parties and vendors.
      • Review privacy and information security policies and standards and the ramifications of updates to policies and standards.
      • Establish standards and procedures for escalating significant security incidents to the ISSC, board, other steering committees, government agencies, and law enforcement, as appropriate.

      Typical ISSC responsibilities and duties (continued)

      Use the following list of responsibilities to customize the list of responsibilities your ISSC may take on. These should link directly to the Responsibilities and Duties section of your ISSC charter.

      Risk Governance

      • Review and approve the company’s information risk governance structure and key risk management processes and capabilities.
      • Assess the company’s high-risk information assets and coordinate planning to address information privacy and security needs.
      • Provide input to executive management regarding the enterprise’s information risk appetite and tolerance.
      • Review the company’s cyber-response preparedness, incident response plans, and disaster recovery capabilities as applicable to the organization’s information security strategy.
      • Promote an open discussion regarding information risk and integrate information risk management into the enterprise’s objectives.

      Monitoring & Reporting

      • Receive periodic reports and coordinate with management on the metrics used to measure, monitor, and manage cyber and IT risks posed to the company and to review periodic reports on selected risk topics as the Committee deems appropriate.
      • Review reports provided by the IT organization regarding the status of and plans for the security of the company’s data stored on internal resources and with third-party providers.
      • Monitor and evaluate the quality and effectiveness of the company’s technology security, capabilities for disaster recovery, data protection, cyberthreat detection and cyber incident response, and management of technology-related compliance risks.

      Review the organization’s security strategy to solidify understanding of the ISSC’s purpose

      The ISSC should consistently evolve to reflect the strategic purpose of the security program. If you completed Info-Tech’s Security Strategy methodology, review the results to inform the scope of your committee. If you have not completed Info-Tech’s methodology, determining these details should be achieved through iterative stakeholder consultations.

      Strategy Components

      ISSC Considerations

      Security Pressure Analysis

      Review the ten security domains and your organization’s pressure levels to review the requisite maturity level of your security program. Consider how this may impact the focus of your ISSC.

      Security Drivers/Obligations

      Review how your security program supports the attainment of the organization’s business objectives. By what means should the ISSC support these objectives? This should inform the rationale, benefits, and overall function of the committee.

      Security Strategy Scope and Boundaries

      Consider the scope and boundaries of your security program to reflect on what the program is responsible for securing. Is this reflected adequately in the language of the committee’s purpose? Should components be added or redacted?

      Draft the committee purpose statement of your ISSC

      Associated Activity icon 1.4

      INPUT: SWOT Analysis, Security Strategy

      OUTPUT: ISSC Committee Purpose

      1. In a meeting with your IT leadership team – and considering the organization’s security strategy, defined responsibilities, and opportunities and threats identified – review the example goal statement in the Information Security Steering Committee Charter, and identify whether any of these statements apply to your organization. Select the statements that apply and collaboratively make any changes needed.
      2. Define unique goal statements by considering the following questions:
        • What three things would you realistically list for the ISSC to achieve?
        • If you were to accomplish three things in the next year, what would those be?
      3. With those goal statements in mind, consider the overall purpose of the committee. The purpose statement should be a reflection of what the committee does, why, and the goals.
      4. Have each individual review the example purpose statement and draft what they think a good purpose statement would be.
      5. Present each statement, and work together to determine a best-of-breed statement.

      Alter the Committee Purpose section in the Information Security Steering Committee Charter.

      Leading Through Uncertainty Workshop Overview

      • Buy Link or Shortcode: {j2store}474|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $123,999 Average $ Saved
      • member rating average days saved: 5 Average Days Saved
      • Parent Category Name: Leadership Development Programs
      • Parent Category Link: /leadership-development-programs

      As the world around us changes there is a higher risk that IT productivity and planned priorities will be derailed.

      Our Advice

      Critical Insight

      To meet the challenges of uncertainty head on IT leaders must adapt so their employees are supported and IT departments continue to operate successfully.

      Impact and Result

      • Clearly define and articulate the current and future priorities to provide direction and cultivate hope for the future.
      • Recognize and manage your own reactions to be conscious of how you are showing up and the perceptions others may have.
      • Incorporate the 4Cs of Leading Through Uncertainty into your leadership practice to make sense of the situation and lead others through it.
      • Build tactics to connect with your employees that will ensure employee engagement and productivity.

      Leading Through Uncertainty Workshop Overview Research & Tools

      Start here – read the Workshop Overview

      Read our concise Workshop Overview to find out how this program can support IT leaders when managing teams through uncertain times.

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

      • Leading Through Uncertainty (LTU) Workshop Overview
      [infographic]

      Your Company is an Economy: Why This is Your Secret Weapon for Resilience

      • Large vertical image:
      • member rating overall impact: N/A
      • member rating average dollars saved: N/A
      • member rating average days saved: N/A

      IT specialists often instinctively focus on technical issues, such as server failures or network problems, because they are trained to address the broken parts. However, it's important to consider the context in which these occur. But what if the real problem isn't just the part but the entire system it operates in?

      I want you to take a step back and to stop thinking about your company as a collection of departments and IT systems. Start seeing it for what it truly is: a complex, living, breathing economic system. This isn't some academic analogy. It’s a powerful model that will change how you approach resilience.

      An economic system involves production, resource allocation, and distribution of goods and services, which parallels how a company operates internally. It includes the combination of various departments, the people doing things, the business units, and even the decision-making steps that make up the economic structure of your company. Once you see this, you can never unsee it.

      What is an economic system?

      Let’s quickly demystify this. Forget textbooks and complex theories for a moment. Think about a national economy. It does three basic things:

      1. Production: It makes things. Factories build cars, farms grow food, and programmers write software. This is the creation of value.

      2. Resource Allocation: This process decides who gets what to make those things. Who gets the steel for the cars? The land for the farms? The funding for the software developers? These are all decisions about how to use scarce resources. 

      3. Distribution: This process gets the finished products to the people who need them. Cars go to importers, then dealerships then the customers, food goes to grocery stores, and software gets deployed to servers and then used by clients (in the general sense).

      That's it. Production, allocation, distribution. Every economy, from a simple bartering tribe to the global financial market, operates on these principles. And so does your company.

      So, how is your company an economy?

      Your company doesn't just “do work.” It produces, allocates, and distributes services in its own internal market (and eventually sells outside, otherwise… trouble).

      The production is everywhere. The human resources department produces a “payroll service.” The sales department produces “revenue contracts.” And the IT department? It produces a vast array of services: “compute cycles,” “data storage,” “network connectivity,” and “application uptime.” These are the goods and services that every other part of the company consumes to do their jobs.

      Resource allocation is the lifeblood of your corporate economy. It's the annual budgeting process, the project prioritization meetings, and the daily decisions managers make about where to assign their people. In IT, you are equally part of the allocation process. Most people get to decide at least what they will give priority to that day. Perhaps via the daily scrum or stand-up meetings. Perhaps during the review process. As a manager, when you approve a request for a new high-powered virtual machine for one team, you are making an economic choice. You are allocating a scarce resource that another team can no longer use. As a developer, when you decide that task X is now a higher priority than task Y, you make an economic decision to allocate yourself to task X. It's important to understand that there is an opportunity cost to every decision, whether you label it that way or not. 

      And distribution? That's how these services get to their “consumers.” It’s the internal platforms, the APIs that connect applications, the service desk that fulfills requests, the operations teams that update data via forms into databases, and even the reporting dashboards that deliver information. These are the supply chains and logistics networks of your company’s economy. The consumers are your clients, of course, but also every department that uses a service provided by another department.

      The IT department plays a central role in the company's economy, akin to a central bank and infrastructure provider, by managing essential digital resources like compute, storage, and bandwidth. You control its supply and, through your decisions, influence its value. You also build and maintain the “roads” and “power grid”—the networks and platforms—that the entire corporate economy depends on to function.

      Why This Perspective Is Important for Resilience

      This is where I feel it gets fascinating. When you start seeing your company as an economic system, your understanding of resilience deepens dramatically. You move beyond simply fixing broken things and start thinking about stabilizing a complex, interconnected market.

      It helps you understand true systemic risk.

      When a core database goes down, an engineer sees a technical failure. An economist sees a supply chain collapse. That database isn't just a box with blinking lights; it's a critical supplier of a raw material, namely data. Every single business process, application, and team that creates, updates or consumes that data is now starved of a resource they need to produce their own services. The failure cascades not just through technical dependencies but through economic dependencies. Seeing it this way forces you to ask better questions: Who are the biggest “consumers” of this data supplier? What is the total economic impact of this outage, not just the technical impact? This changes the incident's priority and your response strategy.

      You move beyond simple redundancy.

      The traditional engineering approach to resilience is redundancy. If one server is important, have two. This is like a town having two power plants. It's a good start, but it's not true economic resilience. An economist would ask different questions. Can we diversify our suppliers? Can we re-route via another path? If our primary database provider fails, can we switch to a secondary one, even if it's slower or pricier for a short time? This is the principle of substitution. Can a business process continue to function in a degraded mode, producing a lower-quality “good” for a while instead of stopping completely? This is about economic adaptability, not just technical duplication.

      You could take this even further and move into the realm of business continuity. Can your process work when your primary resource (the database) is not available? How would you redesign your process to work with an alternative solution? This thinking is at the heart of modern operational resilience regulations worldwide. Authorities are no longer just asking if your backups work; they're asking if your firm can fulfill its economic function in the face of severe adversity. They demand a clear grasp of your entire supply chain and a testable exit plan for critical suppliers, including cloud providers.

      You see that this goes way beyond a failing-part view. It goes to the heart of the economic function of your company.

      Incident response becomes economic intervention.

      During a major incident, the incident commander is now no longer just a technical coordinator. You are the head of the “central bank” during a "market crash". Your job is to prevent a localized failure from causing a full-blown corporate recession. Think about your actions:

      • You allocate scarce capital (your top engineers' time) to the most critical problem. The economic cost is the non-delivery of any other product by those people.

      • You implement fiscal policy by prioritizing certain fixes over others to stimulate the quickest “economic” recovery.

      • You manage market confidence through clear, calm, and regular communication to stakeholders, preventing panic from spreading.

      Each decision is an economic intervention designed to restore stability to the system. (If that is not the job description of a central banker, then I eat my hat.)

      Side Note: I often see teams who are obsessed with their own service's uptime, their own local metrics. They proudly report “five nines” of availability, but they do not report on how their service is actually consumed or how critical it is to the company's overall economic output. They've optimized their own factory but don't disclose their output's need level to the company or that their occasional one-hour outage brings the entire company's main assembly line to a halt. Resilience is not about local optimization; it is about the stability of the entire economic system. A dashboard that lists teams in order of availability or whatever other metric is fine, but these numbers must be mapped against their economic relevance. Without the economic relevance weighting, you may be misallocating resources in areas that are not critical or sufficiently important.

      How to Start Thinking Like an Economist in Your Resilience Practice

      This isn't just a theoretical exercise. You can apply this model today to make your organization stronger and yourself more effective to any employer or client.

      First, map your economic flows. Go beyond standard architecture diagrams. Create maps that show how value and services are produced, distributed, and consumed across departments. Identify your most important “supply chains.” Ask business units what IT services are essential for their “production lines” and what the financial impact is when those services are unavailable. This gives you a heat map of economic risk.

      Second, identify your single points of economic failure. In every economy, there are institutions that are “too big to fail.” What are yours? Is it a single authentication service? A legacy mainframe? A specific team of two people who know how a critical system works? These are the areas where a failure will cause a systemic crisis. They require more than just technical redundancy; they need deep, thoughtful resilience planning, including succession plans for people and substitution options for technology.

      Finally, reframe your post-incident reviews. Stop just asking, “What broke and why?” Start asking, “Which economic activity was disrupted?” and “How did the disruption flow through the system?” This shifts the conversation from blaming a component or a team to understanding systemic weaknesses in your company's economy. The goal is not to find a guilty party but to identify where your internal market is fragile and how you can strengthen it with better “monetary policy” (resource allocation) or “infrastructure” (more robust platforms).

      The vicious cycle of a failing economy

      In another article, I mentioned that resilience is a mindset.
       Resilience mindset graphic 

      So what happens when this economic system becomes unstable?

      These issues are typically considered failures and they manifest as irritations, perceived slowness and bugs, all the way to (regular) failures of a process or whole system.

      If this broken economic system is allowed to remain unstable, people will adopt negative behaviors.

      When “the government” (IT) fails to deliver, business teams take matters into their hands and start shadow IT. They may even purchase their own subscriptions.

      In a stable economy, participants trust that resources will be available when needed, but in a broken system, that trust is gone and leads to the hoarding of assets. This may be visible in the requested need for time or even budget allocation. And that leads into protectionism where teams build walls around their data and systems.

      When failures are common, the focus shifts from resolving the systemic problems to assigning blame for the specific symptom. This is akin to the breakdown of trade relations. The applications team blames the infrastructure team for slow servers. The infrastructure team blames the network team for latency. The network team blames the applications team for inefficient code. And around we go.

      Taking it just that little step further: If people live in a failing state long enough, they lose hope. This is learned helplessness. Your most valuable “citizens”—your engineers and business users—become disengaged. They stop reporting bugs because they assume they will never be fixed. They stop suggesting process improvements because they believe their voice doesn't matter.

      And lastly: In a functional system, there are clear processes for requesting services. In your broken economy, these official channels are considered worthless. The only way to get anything done is to generate a crisis. Escalation becomes the primary currency. People learn to bypass the ticketing system and send direct messages to senior leaders because they perceive that's the only way to get a response.

      How to Break the Cycle: Start Small

      To break this cycle, you need to start small and use mechanisms that turn the negative effects of problems into positive effects, like seeing opportunities.

      • Opportunities to correct irritations
      • Opportunities to enhance processes
      • Opportunities to perhaps redesign a service

      Proposing a grand vision will get you polite nods and zero action. I recommend you pick one irritation and fix it. Repeat multiple times until staff starts to perceive a change. Don't try to move the mountain. Remove the first obstacle and make your way up from there. This can be solving an issue, reducing an uncertainty, or actually spotting a way forward. 

      It will go easier as you continue this. Accept that on day one, your credibility is zero. It doesn’t matter whether you're a new manager or a seasoned expert. Trust is earned on the factory floor. Fix one small, nagging irritation for one person. Then another. This is how you build the political and social capital needed to tackle the mountain. It takes time.

      But what will happen next is crucial. There will be a reduction of the negative behaviors. And when you work it efficiently with enough time, you will eliminate those behaviors. And yes, there will be many ifs and buts, and each of the broken elements of a larger chain may require their own solutions. But it is this act of seeing the bigger picture through the constituent parts that will allow you to assign priorities and move closer to the solution in a structural way.
      Seeing step by step results feeds positivism and higher stability. Which in turn again feeds more positivism. 

       

      When you view your company through the lens of an economic system, it elevates the practice of resilience from a purely technical discipline to a value function. It gives you a language to communicate impact and risk to leadership in terms they understand: production, supply, and cost.

      It forces you to see the interconnectedness of everything you do and to appreciate that the failure of a single, seemingly minor component can have large, cascading effects across the entire organization. By thinking like an economist, you stop being just a firefighter, putting out isolated blazes. You become the architect of a more stable, more robust, and ultimately more resilient economy.

      You become the architect of a more stable, more robust, and ultimately more resilient economy. Now, go manage it.

      Always ready for a chat.

      Create an IT View of the Service Catalog

      • Buy Link or Shortcode: {j2store}396|cart{/j2store}
      • member rating overall impact: 9.0/10 Overall Impact
      • member rating average dollars saved: $59,399 Average $ Saved
      • member rating average days saved: 66 Average Days Saved
      • Parent Category Name: Service Management
      • Parent Category Link: /service-management
      • Organizations often don’t understand which technical services affect user-facing services.
      • Organizations lack clarity around ownership of responsibilities for service delivery.
      • Organizations are vulnerable to change-related incidents when they don’t have insight into service dependencies and their business impact.

      Our Advice

      Critical Insight

      • Even IT professionals underestimate the effort and the complexity of technical components required to deliver a service.
      • Info-Tech’s methodology promotes service orientation among technical teams by highlighting how their work affects the value of user-facing services.
      • CIOs can use the technical part of the catalog as a tool to articulate the value, dependencies, and constraints of services to business leaders.

      Impact and Result

      • Extend the user-facing service catalog to document the people, processes, and technology required to deliver user-facing services.
      • Bring transparency to how services are delivered to better articulate IT’s capabilities and strengthen IT-business alignment.
      • Increase IT’s ability to assess the impact of changes, make informed decisions, and mitigate change-related risks.
      • Respond to incidents and problems in the IT environment with more agility due to reduced diagnosis time for issues.

      Create an IT View of the Service Catalog Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should build the technical components of your service catalog, 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

      Build a strong foundation for the project to increase the chances of success.

      • Create an IT View of the Service Catalog – Phase 1: Launch the Project
      • Service Catalog Extension Project Charter
      • Service Catalog Extension Training Deck

      2. Identify service-specific technologies

      Identify which technologies are specific to certain services.

      • Create an IT View of the Service Catalog – Phase 2: Identify Service-Specific Technology
      • IT Service Catalog

      3. Identify underpinning technologies

      Determine which technologies underpin the existence of user-facing services.

      • Create an IT View of the Service Catalog – Phase 3: Identify Underpinning Services

      4. Map the people and processes to the technologies they support

      Document the roles and responsibilities required to deliver each user-facing service.

      • Create an IT View of the Service Catalog – Phase 4: Determine People & Process
      • Service Definitions: Visual Representations
      [infographic]

      Workshop: Create an IT View of the Service 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 Launch the Project

      The Purpose

      Build a foundation to kick off the project.

      Key Benefits Achieved

      A carefully selected team of project participants.

      Identified stakeholders and metrics.

      Activities

      1.1 Create a communication plan

      1.2 Complete the training deck

      Outputs

      Project charter

      Understanding of the process used to complete the definitions

      2 Identify Service-Specific Technologies and Underpinning Technologies

      The Purpose

      Determine the technologies that support the user-facing services.

      Key Benefits Achieved

      Understanding of what is required to run a service.

      Activities

      2.1 Determine service-specific technology categories

      2.2 Identify service-specific technologies

      2.3 Determine underpinning technologies

      Outputs

      Logical buckets of service-specific technologies makes it easier to identify them

      Identified technologies

      Identified underpinning services and technologies

      3 Identify People and Processes

      The Purpose

      Discover the roles and responsibilities required to deliver each user-facing service.

      Key Benefits Achieved

      Understanding of what is required to deliver each user-facing service.

      Activities

      3.1 Determine roles required to deliver services based on organizational structure

      3.2 Document the services

      Outputs

      Mapped responsibilities to each user-facing service

      Completed service definition visuals

      4 Complete the Service Definition Chart and Visual Diagrams

      The Purpose

      Create a central hub (database) of all the technical components required to deliver a service.

      Key Benefits Achieved

      Single source of information where IT can see what is required to deliver each service.

      Ability to leverage the extended catalog to benefit the organization.

      Activities

      4.1 Document all the previous steps in the service definition chart and visual diagrams

      4.2 Review service definition with team and subject matter experts

      Outputs

      Completed service definition visual diagrams and completed catalog

      Determine Your Zero Trust Readiness

      • Buy Link or Shortcode: {j2store}249|cart{/j2store}
      • member rating overall impact: 9.8/10 Overall Impact
      • member rating average dollars saved: $24,574 Average $ Saved
      • member rating average days saved: 12 Average Days Saved
      • Parent Category Name: Security Strategy & Budgeting
      • Parent Category Link: /security-strategy-and-budgeting

      CISOs pushing for zero trust as their security strategy face several challenges including:

      • Understanding and clarifying the benefits of zero trust for the organization.
      • The inability to verify all business operations are maintaining security best practices.
      • Convincing business units to add more security controls that go against the grain of reducing friction in workflows while still demonstrating these controls support the business.

      Our Advice

      Critical Insight

      • Zero trust must benefit the business and security. Because the road to zero trust is an iterative process, IT security will need to constantly determine how different areas of zero trust will affect core business processes.
      • Zero trust reduces reliance on perimeter security. Zero trust is a strategy that solves how to move beyond the reliance on perimeter security and move controls to where the user accesses resources.
      • Not everyone can achieve zero trust, but everyone can adopt it. Zero trust will be different for every organization and may not be applicable in every control area. This means that zero trust is not a one-size-fits-all approach to IT security. Zero trust is the goal, but some organizations can only get so close to the ideal.

      Impact and Result

      Zero trust is a journey that uses multiple capabilities and requires multiple parties to contribute to an organization’s security. Use Info-Tech’s approach to:

      • Understand zero trust as a strategic platform for building your security roadmap.
      • Assess your current state and determine the benefits of adopting zero trust to help plan your roadmap.
      • Separate vendors from the hype surrounding zero trust to adopt a vendor-agnostic approach to your zero trust planning.

      Determine Your Zero Trust Readiness Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should determine your zero trust readiness, 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. Understand zero trust

      Recognize the zero trust ideal and understand the different zero trust schools of thought.

      2. Assess your zero trust readiness

      Assess and determine the benefits of zero trust and identify and evaluate vendors in the zero trust market.

      • Zero Trust Security Benefit Assessment Tool
      [infographic]

      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)

       

      Develop Necessary Documentation for GDPR Compliance

      • Buy Link or Shortcode: {j2store}258|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: Governance, Risk & Compliance
      • Parent Category Link: /governance-risk-compliance
      • It can be an overwhelming challenge to understand what documentation is required under the GDPR.

      Our Advice

      Critical Insight

      • Hiring the right data protection officer (DPO) isn’t always easy. The person you think might be best may result in a conflict of interest. Be aware of all requirements and be objective when hiring for this role.
      • Keep retention to the bare minimum. Limiting the amount of data you are responsible for limits your liability for protecting it.
      • Under the GDPR, cookies constitute personal data. They require a standalone policy, separate from the privacy policy. Ensure pop-up cookie notification banners require active consent and give users the clear opportunity to reject them.

      Impact and Result

      • Save time developing documents by leveraging ready-to-go templates for the DPO job description, retention documents, privacy notice, and cookie policy.
      • Establishing GDPR-compliance documentation will set the foundation for an overall compliant program.

      Develop Necessary Documentation for GDPR Compliance Research & Tools

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

      1. Hire a data protection officer

      Understand the need for a DPO and what qualities to look for in a strong candidate.

      • Develop Necessary Documentation for GDPR Compliance Storyboard
      • Data Protection Officer Job Description Template

      2. Define retention requirements

      Understand your data retention requirements under the GDPR. Develop the necessary documentation.

      • Data Retention Policy Template
      • Data Retention Schedule Tool – GDPR

      3. Develop privacy and cookie policies

      Understand your website or application’s GDPR requirements to inform users on how you process their personal data and how cookies are used. Develop the necessary documentation.

      • Privacy Notice Template – External Facing
      • Cookie Policy Template – External Facing
      [infographic]

      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]

      Determine the Future of Microsoft Project in Your Organization

      • Buy Link or Shortcode: {j2store}357|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: 50 Average Days Saved
      • Parent Category Name: Project Management Office
      • Parent Category Link: /project-management-office
      • You use Microsoft tools to manage your work, projects, and/or project portfolio.
      • Its latest offering, Project for the web, is new and you’re not sure what to make of it. Microsoft says it will soon replace Microsoft Project and Project Online, but the new software doesn’t seem to do what the old software did.
      • The organization has adopted M365 for collaboration and work management. Meetings happen on Teams, projects are scoped a bit with Planner, and the operations group uses Azure Boards to keep track of what they need to get done.
      • Despite your reservations about the new project management software, Microsoft software has become even more ubiquitous.

      Our Advice

      Critical Insight

      • The various MS Project offerings (but most notably the latest, Project for the web) hold the promise of integrating with the rest of M365 into a unified work management solution. However, out of the box, Project for the web and the various platforms within M365 are all disparate utilities that need to be pieced together in a purpose-built manner to make use of them for holistic work management purposes. If you’re looking for a cohesive product out of the box, look elsewhere. If you’re looking to assemble a wide array of work, project, and portfolio management functions across different functions and departments, you may have found what you seek.
      • Rather than choosing tools based on your gaps, assess your current maturity level so that you optimize your investment in the Microsoft landscape.

      Impact and Result

      Follow Info-Tech’s path in this blueprint to:

      • Perform a tool audit to trim your work management tool landscape.
      • Navigate the MS Project and M365 licensing landscape.
      • Make sense of what to do with Project for the web and take the right approach to rolling it out (i.e. DIY or MS Gold Partner driven) based upon your needs.
      • Create an action plan to inform next steps.

      After following the program in this blueprint, you will be prepared to advise the organization on how to best leverage the rapidly shifting work management options within M365 and the place of MS Project within it.

      Determine the Future of Microsoft Project in Your Organization Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should make sense of the MS Project and M365 landscapes, 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. Determine your tool needs

      Assess your work management tool landscape, current state maturity, and licensing needs to inform a purpose-built work management action plan.

      • M365 Task Management Tool Guide
      • M365 Project Management Tool Guide
      • M365 Project Portfolio Management Tool Guide
      • Tool Audit Workbook
      • Force Field Analysis Tool
      • Microsoft Project & M365 Licensing Tool
      • Project Portfolio Management Maturity Assessment Workbook (With Tool Analysis)
      • Project Management Maturity Assessment Workbook (With Tool Analysis)

      2. Weigh your MS Project implementation options

      Get familiar with Project for the web’s extensibility as well as the MS Gold Partner ecosystem as you contemplate the best implementation approach(s) for your organization.

      • None
      • None

      3. Finalize your implementation approach

      Prepare a boardroom-ready presentation that will help you communicate your MS Project and M365 action plan to PMO and organizational stakeholders.

      • Microsoft Project & M365 Action Plan Template

      Infographic

      Workshop: Determine the Future of Microsoft Project 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 Assess Driving Forces and Risks

      The Purpose

      Assess the goals and needs as well as the risks and constraints of a work management optimization.

      Take stock of your organization’s current work management tool landscape.

      Key Benefits Achieved

      Clear goals and alignment across workshop participants as well as an understanding of the risks and constraints that will need to be mitigated to succeed.

      Current-state insight into the organization’s work management tool landscape.

      Activities

      1.1 Review the business context.

      1.2 Explore the M365 work management landscape.

      1.3 Identify driving forces for change.

      1.4 Analyze potential risks.

      1.5 Perform current-state analysis on work management tools.

      Outputs

      Business context

      Current-state understanding of the task, project, and portfolio management options in M365 and how they align with the organization’s ways of working

      Goals and needs analysis

      Risks and constraints analysis

      Work management tool overview

      2 Determine Tool Needs and Process Maturity

      The Purpose

      Determine your organization’s work management tool needs as well as its current level of project management and project portfolio management process maturity.

      Key Benefits Achieved

      An understanding of your tooling needs and your current levels of process maturity.

      Activities

      2.1 Review tool audit dashboard and conduct the final audit.

      2.2 Identify current Microsoft licensing.

      2.3 Assess current-state maturity for project management.

      2.4 Define target state for project management.

      2.5 Assess current-state maturity for project portfolio management.

      2.6 Define target state for project portfolio management.

      Outputs

      Tool audit

      An understanding of licensing options and what’s needed to optimize MS Project options

      Project management current-state analysis

      Project management gap analysis

      Project portfolio management current-state analysis

      Project portfolio management gap analysis

      3 Weigh Your Implementation Options

      The Purpose

      Take stock of your implementation options for Microsoft old project tech and new project tech.

      Key Benefits Achieved

      An optimized implementation approach based upon your organization’s current state and needs.

      Activities

      3.1 Prepare a needs assessment for Microsoft 365 and Project Plan licenses.

      3.2 Review the business case for Microsoft licensing.

      3.3 Get familiar with Project for the web.

      3.4 Assess the MS Gold Partner Community.

      3.5 Conduct a feasibility test for PFTW.

      Outputs

      M365 and Project Plan needs assessment

      Business case for additional M365 and MS Project licensing

      An understand of Project for the web and how to extend it

      MS Gold Partner outreach plan

      A go/no-go decision for extending Project for the web on your own

      4 Finalize Implementation Approach

      The Purpose

      Determine the best implementation approach for your organization and prepare an action plan.

      Key Benefits Achieved

      A purpose-built implementation approach to help communicate recommendations and needs to key stakeholders.

      Activities

      4.1 Decide on the implementation approach.

      4.2 Identify the audience for your proposal.

      4.3 Determine timeline and assign accountabilities.

      4.4 Develop executive summary presentation.

      Outputs

      An implementation plan

      Stakeholder analysis

      A communication plan

      Initial executive presentation

      5 Next Steps and Wrap-Up (offsite)

      The Purpose

      Finalize your M365 and MS Project work management recommendations and get ready to communicate them to key stakeholders.

      Key Benefits Achieved

      Time saved in developing and communicating an action plan.

      Stakeholder buy-in.

      Activities

      5.1 Complete in-progress deliverables from previous four days.

      5.2 Set up review time for workshop deliverables and to discuss next steps.

      Outputs

      Finalized executive presentation

      A gameplan to communicate your recommendations to key stakeholders as well as a roadmap for future optimization

      Further reading

      Determine the Future of Microsoft Project in Your Organization

      View your task management, project management, and project portfolio management options through the lens of M365.

      EXECUTIVE BRIEF

      Analyst Perspective

      Microsoft Project is an enigma

      Microsoft Project has dominated its market since being introduced in the 1980s, yet the level of adoption and usage per license is incredibly low.

      The software is ubiquitous, mostly considered to represent its category for “Project Management.” Yet, the software is conflated with its “Portfolio Management” offerings as organizations make platform decisions with Microsoft Project as the incorrectly identified incumbent.

      And incredibly, Microsoft has dominated the next era of productivity software with the “365” offerings. Yet, it froze the “Project” family of offerings and introduced the not-yet-functional “Project for the web.”

      Having a difficult time understanding what to do with, and about, Microsoft Project? You’re hardly alone. It’s not simply a question of tolerating, embracing, or rejecting the product: many who choose a competitor find they’re still paying for Microsoft Project-related licensing for years to come.

      If you’re in the Microsoft 365 ecosystem, use this research to understand your rapidly shifting landscape of options.

      (Barry Cousins, Project Portfolio Management Practice Lead, Info-Tech Research Group)

      Executive Summary

      Your Challenge

      You use Microsoft (MS) tools to manage your work, projects, and/or project portfolio.

      Their latest offering, Project for the web, is new and you’re not sure what to make of it. Microsoft says it will soon replace Microsoft Project and Project Online, but the new software doesn’t seem to do what the old software did.

      The organization has adopted M365 for collaboration and work management. Meetings happen on Teams, projects are scoped a bit with Planner, and the operations group uses Azure Boards to keep track of what they need to get done.

      Despite your reservations about the new project management software, Microsoft software has become even more ubiquitous.

      Common Obstacles

      M365 provides the basic components for managing tasks, projects, and project portfolios, but there is no instruction manual for making those parts work together.

      M365 isn’t the only set of tools at play. Business units and teams across the organization have procured other non-Microsoft tools for work management without involving IT.

      Microsoft’s latest project offering, Project for the web, is still evolving and you’re never sure if it is stable or ready for prime time. The missing function seems to involve the more sophisticated project planning disciplines, which are still important to larger, longer, and costlier projects.

      Common Obstacles

      Follow Info-Tech’s path in this blueprint to:

      • Perform a tool audit to trim your work management tool landscape.
      • Navigate the MS Project and M365 licensing landscape.
      • Make sense of what to do with Project for the web and take the right approach to rolling it out (i.e. DIY or MS Gold Partner driven) for your needs.
      • Create an action plan to inform next steps.

      After following the program in this blueprint, you will be prepared to advise the organization on how to best leverage the rapidly shifting work management options within M365 and the place of MS Project within it.

      M365 and, within it, O365 are taking over

      Accelerated partly by the pandemic and the move to remote work, Microsoft’s market share in the work productivity space has grown exponentially in the last two years.

      70% of Fortune 500 companies purchased 365 from Sept. 2019 to Sept. 2020. (Thexyz blog, 2020)

      In its FY21 Q2 report, Microsoft reported 47.5 million M365 consumer subscribers – an 11.2% increase from its FY20 Q4 reporting. (Office 365 for IT Pros, 2021)

      As of September 2020, there were 258,000,000 licensed O365 users. (Thexyz blog, 2020)

      In this blueprint, we’ll look at what the what the phenomenal growth of M365 means for PMOs and project portfolio practitioners who identify as Microsoft shops

      The market share of M365 warrants a fresh look at Microsoft’s suite of project offerings

      For many PMO and project portfolio practitioners, the footprint of M365 in their organizations’ work management cultures is forcing a renewed look at Microsoft’s suite of project offerings.

      The complicating factor is this renewed look comes at a transitional time in Microsoft’s suite of project and portfolio offerings.

      • The market dominance of MS Project Server and Project Online are wanning, with Microsoft promising the end-of-life for Online sometime in the coming years.
      • Project Online’s replacement, Project for the web, is a viable task management and lightweight project management tool, but its viability as a replacement for the rigor of Project Online is at present largely a question mark.
      • Related to the uncertainty and promise around Project for the web, the Dataverse and the Power Platform offer a glimpse into a democratized future of work management tools but anything specific about that future has yet to solidify.

      Microsoft Project has 66% market share in the project management tool space. (Celoxis, 2018)

      A copy of MS project is sold or licensed every 20 seconds. (Integent, 2013)

      MS Project is evolving to meet new work management realities

      It also evolved to not meet the old project management realities.

      • The lines between traditional project management and operational task management solutions are blurring as organizations struggle to keep up with demands.
      • To make the software easier to use, modern work management doesn’t involve the complexities from days past. You won’t find anywhere to introduce complex predecessor-successor relationships, unbalanced assignments with front-loading or back-loading, early-start/late-finish, critical path, etc.
      • “Work management” is among the latest buzzwords in IT consulting. With Project for the web (PFTW), Azure Boards, and Planner, Microsoft is attempting to compete with lighter and better-adopted tools like Trello, Basecamp, Asana, Wrike, and Monday.com.
      • Buyers of project and work management software have struggled to understand how PFTW will still be usable if it gets the missing project management function from MS Project.

      Info-Tech Insight

      Beware of the Software Granularity Paradox.

      Common opinion 1: “Plans and estimates that are granular enough to be believable are too detailed to manage and maintain.”

      Common opinion 2: “Plans simple enough to publish aren’t detailed enough to produce believable estimates.”

      In other words, software simple enough to get widely adopted doesn’t produce believable plans. Software that can produce believable plans is too complex to use at scale.

      A viable task and project management option must walk the line between these dichotomies.

      M365 gives you the pieces, but it’s on PMO users to piece them together in a viable way

      With the new MS Project and M365, it’s on PMOs to avoid the granularity paradox and produce a functioning solution that fits with the organization’s ways of working.

      Common perception still sees Microsoft Project as a rich software tool. Thus, when we consider the next generation of Microsoft Project, it’s easy to expect a newer and friendlier version of what we knew before.

      In truth, the new solution is a collection of partially integrated but largely disparate tools that each satisfy a portion of the market’s needs. While it looks like a rich collection of function when viewed through high-level requirements, users will find:

      • Overlaps, where multiple tools satisfy the same functional requirement (e.g. “assign a task”)
      • Gaps, where a tool doesn’t quite do enough and you’re forced to incorporate another tool (e.g. reverting back to Microsoft Project for advanced resource planning)
      • Islands, where tools don’t fluently talk to each other (e.g. Planner data integrated in real-time with portfolio data, which requires clunky, unstable, decentralized end-user integrations with Microsoft Power Automate)
      A colourful arrangement of Microsoft programs arranged around a pile of puzzle pieces.

      Info-Tech's approach

      Use our framework to best leverage the right MS Project offerings and M365 components for your organization’s work management needs.

      The Info-Tech difference:

      1. A simple to follow framework to help you make sense of a chaotic landscape.
      2. Practical and tactical tools that will help you save time.
      3. Leverage industry best practices and practitioner-based insights.
      An Info-Tech framework titled 'Determine the Future of Microsoft Project in Your Organization, subtitle 'View your task, project, and portfolio management options through the lens of Microsoft 365'. There are four main sections titled 'Background', 'Approaches', 'Deployments', and 'Portfolio Outcomes'. In '1) Background' are 'Analyze Content', 'Assess Constraints', and 'Determine Goals and Needs'. In '2) Approaches' are 'DIY: Are you ready to do it yourself?' 'Info-Tech: Can our analysts help?', and 'MS Gold Partner: Are you better off with a third party?'. In '3) Deployments' are five sections: 'Personal Task Management', Barriers to Portfolio Outcomes: Isolated to One Person. 'Team Task Management', Barriers to Portfolio Outcomes: Isolated to One Team. 'Project Portfolio Management', Barriers to Portfolio Outcomes: Isolated to One Project. 'Project Management', Barriers to Portfolio Outcomes: Functionally Incomplete. 'Enterprise Project and Portfolio Management', Barriers to Portfolio Outcomes: Underadopted. In '4) Portfolio Outcomes' are 'Informed Steering Committee', 'Increased Project Throughput', 'Improved Portfolio Responsiveness', 'Optimized Resource Utilization', and 'Reduced Monetary Waste'.

      Determine the Future of Microsoft Project in Your Organization

      View your task, project, and portfolio management options through the lens of Microsoft 365.

      1. Background

      • Analyze Content
      • Assess Constraints
      • Determine Goals and Needs

      2. Approaches

      • DIY – Are you ready to do it yourself?
      • Info-Tech – Can our analysts help?
      • MS Gold Partner – Are you better off with a third party?

      3. Deployments

        Task Management

      • Personal Task Management
        • Who does it? Knowledge workers
        • What is it? To-do lists
        • Common Approaches
          • Paper list and sticky notes
          • Light task tools
        • Applications
          • Planner
          • To Do
        • Level of Rigor 1/5
        • Barriers to Portfolio Outcomes: Isolated to One Person
      • Team Task Management
        • Who does it? Groups of knowledge workers
        • What is it? Collaborative to-do lists
        • Common Approaches
          • Kanban boards
          • Spreadsheets
          • Light task tools
        • Applications
          • Planner
          • Azure Boards
          • Teams
        • Level of Rigor 2/5
        • Barriers to Portfolio Outcomes: Isolated to One Team
      • Project Management

      • Project Portfolio Management
        • Who does it? PMO Directors, Portfolio Managers
        • What is it?
          • Centralized list of projects
          • Request and intake handling
          • Aggregating reporting
        • Common Approaches
          • Spreadsheets
          • PPM software
          • Roadmaps
        • Applications
          • Project for the Web
          • Power Platform
        • Level of Rigor 3/5
        • Barriers to Portfolio Outcomes: Isolated to One Project
      • Project Management
        • Who does it? Project Managers
        • What is it? Deterministic scheduling of related tasks
        • Common Approaches
          • Spreadsheets
          • Lists
          • PM software
          • PPM software
        • Applications
          • Project Desktop Client
        • Level of Rigor 4/5
        • Barriers to Portfolio Outcomes: Functionally Incomplete
      • Enterprise Project and Portfolio Management

      • Enterprise Project and Portfolio Management
        • Who does it? PMO and ePMO Directors, Portfolio Managers, Project Managers
        • What is it?
          • Centralized request and intake handling
          • Resource capacity management
          • Deterministic scheduling of related tasks
        • Common Approaches
          • PPM software
        • Applications
          • Project Online
          • Project Desktop Client
          • Project Server
        • Level of Rigor 5/5
        • Barriers to Portfolio Outcomes: Underadopted

      4. Portfolio Outcomes

      • Informed Steering Committee
      • Increased Project Throughput
      • Improved Portfolio Responsiveness
      • Optimized Resource Utilization
      • Reduced Monetary Waste

      Info-Tech's methodology for Determine the Future of MS Project for Your Organization

      1. Determine Your Tool Needs

      2. Weigh Your MS Project Implementation Options

      3. Finalize Your Implementation Approach

      Phase Steps

      1. Survey the M365 Work Management Tools
      2. Perform a Process Maturity Assessment to Help Inform Your M365 Starting Point
      3. Consider the Right MS Project Licenses for Your Stakeholders
      1. Get Familiar With Extending Project for the Web Using Power Apps
      2. Assess the MS Gold Partner Community
      1. Prepare an Action Plan

      Phase Outcomes

      1. Work Management Tool Audit
      2. MS Project and Power Platform Licensing Needs
      3. Project Management and Project Portfolio Management Maturity Assessment
      1. Project for the Web Readiness Assessment
      2. MS Gold Partner Outreach Plan
      1. MS Project and M365 Action Plan Presentation

      Insight Summary

      Overarching blueprint insight: Microsoft Parts Sold Separately. Assembly required.

      The various MS Project offerings (but most notably the latest, Project for the web) hold the promise of integrating with the rest of M365 into a unified work management solution. However, out of the box, Project for the web and the various platforms within M365 are all disparate utilities that need to be pieced together in a purpose-built manner to make use of them for holistic work management purposes.

      If you’re looking for a cohesive product out of the box, look elsewhere. If you’re looking to assemble a wide array of work, project, and portfolio management functions across different functions and departments, you may have found what you seek

      Phase 1 insight: Align your tool choice to your process maturity level.

      Rather than choosing tools based on your gaps, make sure to assess your current maturity level so that you optimize your investment in the Microsoft landscape.

      Phase 2 insight: Weigh your options before jumping into Microsoft’s new tech.

      Microsoft’s new Project plans (P1, P3, and P5) suggest there is a meaningful connection out of the box between its old tech (Project desktop, Project Server, and Project Online) and its new tech (Project for the web).

      However, the offerings are not always interoperable.

      Phase 3 insight: Keep the iterations small as you move ahead with trials and implementations.

      Organizations are changing as fast as the software we use to run them.

      If you’re implementing parts of this platform, keep the changes small as you monitor the vendors for new software versions and integrations.

      Blueprint deliverables

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

      Key deliverable: Microsoft Project & M365 Action Plan Template

      The Action Plan will help culminate and present:

      • Context and Constraints
      • DIY Implementation Approach
      Or
      • MS Partner Implementation Approach
      • Future-State Vision and Goals
      Samples of Info-Tech's key deliverable 'Microsoft Project and M365 Action Plan Template'.

      Tool Audit Workbook

      Sample of Info-Tech deliverable 'Tool Audit Workbook'.

      Assess your organization's current work management tool landscape and determine what tools drive value for individual users and teams and which ones can be rationalized.

      Force Field Analysis

      Sample of Info-Tech deliverable 'Force Field Analysis'.

      Document the driving and resisting forces for making a change to your work management tools.

      Maturity Assessments

      Sample of Info-Tech deliverable 'Maturity Assessments'.

      Use these assessments to identify gaps in project management and project portfolio management processes. The results will help guide process improvement efforts and measure success and progress.

      Microsoft Project & M365 Licensing Tool

      Sample of Info-Tech deliverable 'Microsoft Project and M365 Licensing Tool'.

      Determine the best licensing options and approaches for your implementation of Microsoft Project.

      Curate your work management tools to harness valuable portfolio outcomes

      • Increase Project Throughput

        Do more projects by ensuring the right projects and the right amount of projects are approved and executed.
      • Support an Informed Steering Committee

        Easily compare progress of projects across the portfolio and enable the leadership team to make decisions.
      • Improve portfolio responsiveness

        Make the portfolio responsive to executive steering when new projects and changing priorities need rapid action.
      • Optimize Resource Utilization

        Assign the right resources to approved projects and minimize the chronic over-allocation of resources that leads to burnout.
      • Reduce Monetary Waste

        Terminate low-value projects early and avoid sinking additional funds into unsuccessful ventures.

      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?

      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 6 to 8 calls over the course of 3 to 4 months.

        Introduction

      • Call #1: Scope requirements, objectives, and your specific challenges.
      • Phase 1

      • Call #2: Explore the M365 work management landscape.
      • Call #3: Discuss Microsoft Project Plans and their capabilities.
      • Call #4: Assess current-state maturity.
      • Phase 2

      • Call #5: Get familiar with extending Project for the web using Power Apps.
      • Call #6: Assess the MS Gold Partner Community.
      • Phase 3

      • Call #7: Determine approach and deployment.
      • Call #8: Discuss action plan.

      Workshop Overview

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

      Day 1
      Assess Driving Forces and Risks

      Day 2
      Determine Tool Needs and Process Maturity

      Day 3
      Weigh Your Implementation Options

      Day 4
      Finalize Implementation Approach

      Day 5
      Next Steps and Wrap-Up (offsite)

      Activities

      • 1.1 Review the business context.
      • 1.2 Explore the M365 work management landscape.
      • 1.3 Identify driving forces for change.
      • 1.4 Analyze potential risks.
      • 1.5 Perform current-state analysis on work management tools.
      • 2.1 Review tool audit dashboard and conduct the final audit.
      • 2.2 Identify current Microsoft licensing.
      • 2.3 Assess current-state maturity for project management.
      • 2.4 Define target state for project management.
      • 2.5 Assess current-state maturity for project portfolio management.
      • 2.6 Define target state for project portfolio management.
      • 3.1 Prepare a needs assessment for Microsoft 365 and Project Plan licenses.
      • 3.2 Review the business case for Microsoft licensing.
      • 3.3 Get familiar with Project for the web.
      • 3.4 Assess the MS Gold Partner Community.
      • 3.5 Conduct a feasibility test for PFTW.
      • 4.1 Decide on the implementation approach.
      • 4.2 Identify the audience for your proposal.
      • 4.3 Determine timeline and assign accountabilities.
      • 4.4 Develop executive summary presentation.
      • 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. Force Field Analysis
      2. Tool Audit Workbook
      1. Tool Audit Workbook
      2. Project Management Maturity Assessment
      3. Portfolio Management Maturity Assessment
      1. Microsoft Project and M365 Licensing Tool
      1. Microsoft Project & M365 Action Plan
      1. Microsoft Project & M365 Action Plan

      Determine the Future of Microsoft Project for Your Organization

      Phase 1: Determine Your Tool Needs

      Phase 1: Determine Your Tool Needs

      Phase 2: Weigh Your Implementation Options Phase 3: Finalize Your Implementation Approach
      • Step 1.1: Survey the M365 work management landscape
      • Step 1.2: Explore the Microsoft Project Plans and their capabilities
      • Step 1.3: Assess the maturity of your current PM & PPM capabilities
      • Step 2.1: Get familiar with extending Project for the web using Power Apps
      • Step 2.2: Assess the MS Gold Partner Community
      • Step 3.1: Prepare an action plan

      Phase Outcomes

      • Tool Audit
      • Microsoft Project Licensing Analysis
      • Project Management Maturity Assessment
      • Project Portfolio Management Maturity Assessments

      Step 1.1

      Survey the M365 Work Management Landscape

      Activities

      • 1.1.1 Distinguish between task, project, and portfolio capabilities
      • 1.1.2 Review Microsoft’s offering for task, project, and portfolio management needs
      • 1.1.4 Assess your organizational context and constraints
      • 1.1.3 Explore typical deployment options

      This step will walk you through the following activities:

      • Assessing your organization’s context for project and project portfolio management
      • Documenting the organization’s constraints
      • Establishing the organization’s goals and needs

      This step involves the following participants:

      • PMO Director
      • Resource Managers
      • Project Managers
      • Knowledge Workers

      Outcomes of Step

      • Knowledge of the Microsoft ecosystem as it relates to task, project, and portfolio management
      • Current organizational context and constraints

      Don’t underestimate the value of interoperability

      The whole Microsoft suite is worth more than the sum of its parts … if you know how to put it together.

      38% of the worldwide office suite market belongs to Microsoft. (Source: Statistica, 2021)

      1 in 3 small to mid-sized organizations moving to Microsoft Project say they are doing so because it integrates well with Office 365. (Source: CBT Nuggets, 2018)

      There’s a gravity to the Microsoft ecosystem.

      And while there is no argument that there are standalone task management tools, project management tools, or portfolio management tools that are likely more robust, feature-rich, and easier to adopt, it’s rare that you find an ecosystem that can do it all, to an acceptable level.

      That is the value proposition of Microsoft: the ubiquity, familiarity, and versatility. It’s the Swiss army knife of software products.

      The work management landscape is evolving

      With M365, Microsoft is angling to become the industry leader, and your organization’s hub, for work management.

      Workers lose up to 40% of their time multi-tasking and switching between applications. (Bluescape, 2018)

      25 Context switches – On average, workers switch between 10 apps, 25 times a day. (Asana, 2021)

      “Work management” is among the latest buzzwords in IT consulting.

      What is work management? It was born of a blurring of the traditional lines between operational or day-to-day tasks and project management tasks, as organizations struggle to keep up with both operational and project demands.

      To make the software easier to use, modern work management doesn’t involve the complexities from days past. You won’t find anywhere to introduce complex predecessor-successor relationships, unbalanced assignments with front-loading or back-loading, early-start/late-finish, critical path, etc.

      Indeed, with Project for the web, Azure Boards, Planner, and other M365 utilities, Microsoft is attempting to compete with lighter and better-adopted tools (e.g. Trello, Wike, Monday.com).

      The Microsoft world of work management can be understood across three broad categories

      1. Task Management

        Task management is essentially the same as keeping track of a to-do list. While you can have a project-related task, you can also have a non-project-related task. The sum of project and non-project tasks make up the work that you need to complete.
      2. Project Management

        Project management (PM) is a methodical approach to planning and guiding project processes from start to finish. Implementing PM processes helps establish repeatable steps and controls that enable project success. Documentation of PM processes leads to consistent results and dependable delivery on expectations.
      3. Portfolio Management

        Project portfolio management (PPM) is a strategic approach to approving, prioritizing, resourcing, and reporting on project. In addition, effective PPM should nurture the completion of projects in the portfolio in the most efficient way and track the extent to which the organization is realizing the intended benefits from completed projects.

      The slides ahead explain each of these modes of working in the Microsoft ecosystem in turn. Further, Info-Tech’s Task, Project, and Project Portfolio Management Tool Guides explain these areas in more detail.

      Use Info-Tech’s Tool Guides assess your MS Project and M365 work management options

      Lean on Info-Tech’s Tool Guides as you navigate Microsoft’s tasks management, project management, and project portfolio management options.

      • The slides ahead take you through a bird’s-eye view of what your MS Project and M365 work management options look like across Info-Tech’s three broad categories
      • In addition to these slides, Info-Tech has three in-depth tool guides that take you through your operational task management, project management, and project portfolio management options in MS Project and M365.
      • These tool guides can be leveraged as you determine whether Microsoft has the required toolset for your organization’s task, project, and project portfolio management needs.

      Download Info-Tech’s Task Management, Project Management, and Project Portfolio Management Tool Guides

      Task Management Overview

      What is task management?

      • It is essentially the same as keeping track of a to-do list. While you can have a project-related task, you can also have a non-project-related task. The sum of project and non-project tasks make up the work that you need to complete.

      What are the benefits of task management using applications within the MS suite?

      • Many organizations already own the tools and don't have to go out and buy something separately.
      • There is easy integration with other MS applications.

      What is personal task management?

      • Tools that allow you to structure work that is visible only to you. This can include work from tasks you are going to be completing for yourself and tasks you are completing as part of a larger work effort.

      What is team task management?

      • Tools that allow users to structure work that is visible to a group. When something is moved or changed, it affects what the group is seeing because it is a shared platform.

      Get familiar with the Microsoft product offerings for task management

      A diagram of Microsoft products and what they can help accomplish. It starts on the right with 'Teams' and 'Outlook'. Both can flow through to 'Personal Task Management' with products 'Teams Tasks' and 'To-Do', but Teams also flows into 'Team Task Management' with products 'Planner' and 'Project for the web'. See the next two slides for more details on these modes of working.

      Download the M365 Task Management Tool Guide

      Personal Task Management

      The To-Do list

      • Who does it?
        • Knowledge workers
      • What is it?
        • How each knowledge worker organizes their individual work tasks in M365
      • When is it done?
        • As needed throughout the day
      • Where is it done?
        • Paper
        • Digital location
      • How is it done?
        • DIY and self-developed
        • Usually not repeatable and evolves depending on work location and tools available
        • Not governed

      Microsoft differentiator:

      Utilities like Planner and To-Do make it easier to turn what are often ad hoc approaches into a more repeatable process.

      Team Task Management

      The SharedTo-Do list

      • Who does it?
        • Groups of knowledge workers
      • What is it?
        • Temporary and permanent collections of knowledge workers
      • When is it done?
        • As needed or on a pre-determined cadence
      • Where is it done?
        • Paper
        • Digital location
      • How is it done?
        • User norms are established organically and adapted based upon the needs of the team.
        • To whatever extent processes are repeatable in the first place, they remain repeatable only if the team is a collective.
        • Usually governed within the team and not subject to wider visibility.

      Microsoft differentiator:

      Teams has opened personal task management tactics up to more collaborative approaches.

      Project Management Overview

      2003

      Project Server: This product serves many large enterprise clients, but Microsoft has stated that it is at end of life. It is appealing to industries and organizations where privacy is paramount. This is an on-premises system that combines servers like SharePoint, SQL, and BI to report on information from Project Desktop Client. To realize the value of this product, there must be adoption across the organization and engagement at the project-task level for all projects within the portfolio.

      2013

      Project Online: This product serves many medium enterprise clients. It is appealing for IT departments who want to get a rich set of features that can be used to intake projects, assign resources, and report on project portfolio health. It is a cloud solution built on the SharePoint platform, which provides many users a sense of familiarity. However, due to the bottom-up reporting nature of this product, again, adoption across the organization and engagement at the project task level for all projects within the portfolio is critical.

      2020

      Project for the web: This product is the newest on the market and is quickly being evolved. Many O365 enthusiasts have been early adopters of Project for the web despite its limited features when compared to Project Online. It is also a cloud solution that encourages citizen developers by being built on the MS Power Platform. This positions the product well to integrate with Power BI, Power Automate, and Power Apps. It is, so far, the only MS product that lends itself to abstracted portfolio management, which means it doesn’t rely on project task level engagement to produce portfolio reports. The portfolio can also run with a mixed methodology by funneling Project, Azure Boards, and Planner boards into its roadmap function.

      Get familiar with the Microsoft product offerings for project management

      A diagram of Microsoft products and what they can help accomplish in Personal and Team Project Management. Products listed include 'Project Desktop Client', 'Project Online', 'SharePoint', 'Power Platform', 'Azure DevOps', 'Project for the web', Project Roadmap', 'Project Home', and 'Project Server'. See the next slide for more details on personal and team project management as modes of working.

      Download the M365 Project Management Tool Guide

      Project Management

      Orchestrating the delivery of project work

      • Who does it?
        • Project managers
      • What is it?
        • Individual project managers developing project plans and schedules in the MS Project Desktop Client
      • When is it done?
        • Throughout the lifecycle of the project
      • Where is it done?
        • Digital location
      • How is it done?
        • Used by individual project managers to develop and manage project plans.
        • Common approaches may or may not involve reconciliation of resource capacity through integration with Active Directory.
        • Sometimes usage norms are established by organizational project management governance standards, though individual use of the desktop client is largely ungoverned.

      Microsoft differentiator:

      For better or worse, Microsoft’s core solution is veritably synonymous with project management itself and has formally contributed to the definition of the project management space.

      Project Portfolio Management Overview

      Optimize what you’re already using and get familiar with the Power Platform.

      What does PPM look like within M365?

      • The Office suite in the Microsoft 365 suite boasts the world’s most widely used application for the purposes of abstracted and strategic PPM: Excel. For the purposes of PPM, Excel is largely implemented in a suboptimal fashion, and as a result, organizations fail to gain PPM adoption and maturation through its use.
      • Until very recently, Microsoft toolset did not explicitly address abstracted PPM needs.
      • However, with the latest version of M365 and Project for the web, Microsoft is boasting of renewed PPM capabilities from its toolset. These capabilities are largely facilitated through what Microsoft is calling its Power Platform (i.e. a suite of products that includes Power, Power Apps, and Power Automate).

      Explore the Microsoft product offering for abstracted project portfolio management

      A diagram of Microsoft products for 'Adaptive or Abstracted Portfolio Management'. Products listed include 'Excel', 'MS Lists', 'Forms', 'Teams', and the 'Power Platform' products 'Power BI', 'Power Apps', and 'Power Automate'. See the next slide for more details on adaptive or abstracted portfolio management as a mode of working.

      Download the M365 Project Portfolio Management Tool Guide

      Project Portfolio Management

      Doing the right projects, at the right time, with the right resources

      • Who does it?
        • PMO directors; portfolio managers
      • What is it?
        A strategic approach to approving, prioritizing, resourcing, and reporting on projects using applications in M365 and Project for the web. In distinction to enterprise PPM, a top-down or abstracted approach is applied, meaning PPM data is not tied to project task details.
      • Where is it done?
        • Digital tool, either homegrown or commercial
      • How is it done?
        • Currently in M365, PPM approaches are largely self-developed, though Microsoft Gold Partners are commonly involved.
        • User norms are still evolving, along with the software’s (Project for the web) function.

      Microsoft differentiator:

      Integration between Project for the web and Power Apps allows for custom approaches.

      Project Portfolio Management Overview

      Microsoft’s legacy project management toolset has contributed to the definition of traditional or enterprise PPM space.

      A robust and intensive bottom-up approach that requires task level roll-ups from projects to inform portfolio level data. For this model to work, reconciliation of individual resource capacity must be universal and perpetually current.

      If your organization has low or no maturity with PPM, this approach will be tough to make successful.

      In fact, most organizations under adopt the tools required to effectively operate with the traditional project portfolio management. Once adopted and operationalized, this combination of tools gives the executives the most precise view of the current state of projects within the portfolio.

      Explore the Microsoft product offering for enterprise project portfolio management

      A diagram of Microsoft products for 'Enterprise or Traditional Portfolio Management'. Products listed include 'Project Desktop Client', 'SharePoint', 'Project Online', 'Azure DevOps', 'Project Roadmaps', and 'Project Home'. See the next slide for more details on this as a mode of working.

      Download the M365 Project Portfolio Management Tool Guide

      Enterprise Project and Portfolio Management

      Bottom-up approach to managing the project portfolio

      • Who does it?
        • PMO and ePMO directors; portfolio managers
        • Project managers
      • What is it?
        • A strategic approach to approving, prioritizing, resourcing, and reporting on projects using applications in M365 and Project for the web. In distinction to enterprise PPM, a top-down or abstracted approach is applied, meaning PPM data is not tied to project task details.
      • Where is it done?
        • Digital tool that is usually commercial.
      • How is it done?
        • Microsoft Gold Partner involvement is highly likely in successful implementations.
        • Usage norms are long established and customized solutions are prevalent.
        • To be successful, use must be highly governed.
        • Reconciliation of individual resource capacity must be universal and perpetually current.

      Microsoft differentiator:

      Microsoft’s established network of Gold Partners helps to make this deployment a viable option.

      Assess your current tool ecosystem across work management categories

      Use Info-Tech’s Tool Audit Workbook to assess the value and satisfaction for the work management tools currently in use.

      • With the modes of working in mind that have been addressed in the previous slides and in Info-Tech’s Tool Guides, the activity slides ahead encourage you to engage your wider organization to determine all of the ways of working across individuals and teams.
      • Depending on the scope of your work management optimization, these engagements may be limited to IT or may extend to the business.
      • Use Info-Tech’s Tool Audit Workbook to help you gather and make sense of the tool data you collect. The result of this activity is to gain insight into the tools that drive value and fail to drive value across your work management categories with a view to streamline the organization’s tool ecosystem.

      Download Info-Tech’s Tool Audit Workbook

      Sample of Info-Tech's Tool Audit Workbook.

      1.2.1 Compile list of tools

      1-3 hours

      Input: Information on tools used to complete task, project, and portfolio tasks

      Output: Analyzed list of tools

      Materials: Whiteboard/Flip Charts, Tool Audit Workbook

      Participants: Portfolio Manager (PMO Director), PMO Admin Team, Project Managers, Business Stakeholders

      1. Identify the stakeholder groups that are in scope. For each group that you’ve identified, brainstorm the different tools and artifacts that are necessary to get the task, project, and project portfolio management functions done.
      2. Make sure to record the tool name and specify its category (standard document, artifact, homegrown solution, or commercial solution).
      3. Think about and discuss how often the tool is being used for each use case across the organization. Document whether its use is required. Then assess reporting functionality, data accuracy, and cost.
      4. Lastly, give a satisfaction rating for each use case.

      Excerpt from the Tool Audit Workbook

      Excerpt from Info-Tech's Tool Audit Workbook on compiling tools.

      1.2.1 Review dashboard

      1-3 hours

      Input: List of key PPM decision points, List of who is accountable for PPM decisions, List of who has PPM decision-making authority

      Output: Prioritized list of PPM decision-making support needs

      Materials: Whiteboard/Flip Charts, Tool Audit Workbook

      Participants: Portfolio Manager (PMO Director), PMO Admin Team, CIO

      Discuss the outputs of the Dashboards tab to inform your decision maker on whether to pass or fail the tool for each use case.

      Sample of a BI dashboard used to evaluate the usefulness of tools. Written notes include: 'Slice the data based on stakeholder group, tool, use case, and category', and 'Review the results of the questionnaire by comparing cost and satisfaction'.

      1.2.1 Execute final audit

      1 hour

      Input: List of key PPM decision points, List of who is accountable for PPM decisions, List of who has PPM decision-making authority

      Output: Prioritized list of PPM decision-making support needs

      Materials: Whiteboard/Flip Charts, Tool Audit Workbook

      Participants: Portfolio Manager (PMO Director), PMO Admin Team, CIO

      1. Using the information available, schedule time with the leadership team to present the results.
      2. Identify the accountable party to make the final decision on what current tools pass or fail the final audit.
      3. Mind the gap presented by the failed tools and look to possibilities within the M365 and Microsoft Project suite. For each tool that is deemed unsatisfactory for the future state, mark it as “Fail” in column O on tab 2 of the Tool Audit Workbook. This will ensure the item shows in the “Fail” column on tab 4 of the tool when you refresh the data.
      4. For each of the tools that “fail” your audit and that you’re going to make recommendations to rationalize in a future state, try to capture the annual total current-state spending on licenses, and the work modes the tool currently supports (i.e. task, project, and/or portfolio management).
      5. Additionally, start to think about future-state replacements for each tool within or outside of the M365/MS Project platforms. As we move forward to finalize your action plan in the last phase of this blueprint, we will capture and present this information to key stakeholders.

      Document your goals, needs, and constraints before proceeding

      Use Info-Tech’s Force Field Analysis Tool to help weigh goals and needs against risks and constraints associated with a work management change.

      • Now that you have discussed the organization’s ways of working and assessed its tool landscape – and made some initial decisions on some tool options that might need to change across that landscape – gather key stakeholders to define (a) why a change is needed at this time and (b) to document some of the risks and constraints associated with changing.
      • Info-Tech’s Force Field Analysis Tool can be used to capture these data points. It takes an organizational change management approach and asks you to consider the positive and negative forces associated with a work management tool change at this time.
      • The slides ahead walk you through a force field analysis activity and help you to navigate the relevant tabs in the Tool.

      Download Info-Tech's Force Field Analysis Tool

      Sample of Info-Tech's Force Field Analysis Tool.

      1.2.1 Identify goals and needs (1 of 2)

      Use tab 1 of the Force Field Analysis Workbook to assess goals and needs.

      30 minutes

      Input: Opportunities associated with determining the use case for Microsoft Project and M365 in your organization

      Output: Plotted opportunities based on probability and impact

      Materials: Whiteboard/Flip Charts, Force Field Analysis Tool

      Participants: Portfolio Manager (PMO Director), PMO Admin Team, Project Managers

      1. Brainstorm opportunities associated with exploring and/or implementing Microsoft Project and the Microsoft 365 suite of products for task, project, and project portfolio management.
      2. Document relevant opportunities in tab 1 of the Force Field Analysis Tool. For each driving force for the change (note: a driving force can include goals and needs) that is identified, provide a category that explains why the driving force is a concern (i.e. with this force is the organization looking to mature, integrate, scape, or accelerate?).
      3. In addition, assess the ease of achieving or realizing each goal or need and the impact of realizing them on the PMO and/or the organization.
      4. See the next slide for a screenshot that helps you navigate tab 1 of the Tool.

      Download the Force Field Analysis Tool

      1.2.1 Identify goals and needs (2 of 2)

      Screenshot of tab 1 of the Force Field Analysis Workbook.

      Screenshot of tab 1 of the Force Field Analysis Workbook. There are five columns referred to as columns B through F with the headings 'Opportunities', 'Category', 'Source', 'Ease of Achieving', and 'Impact on PMO/Organization'.

      In column B on tab 1, note the specific opportunities the group would like to call out.

      In column C, categorize the goal or need being articulated by the list of drop-down options: will it accelerate the time to benefit? Will it help to integrate systems and data sources? Will it mature processes and the organization overall? Will it help to scale across the organization? Choose the option that best aligns with the opportunity.

      In column D, categorize the source of the goal or need as internal or external.

      In column E, use the drop-down menus to indicate the ease of realizing each goal or need for the organization. Will it be relatively easy to manifest or will there be complexities to implementing it?

      In column F, use the drop-down menus to indicate the positive impact of realizing or achieving each need on the PMO and/or the organization.

      On tab 3 of the Force Field Analysis Workbook, your inputs on tab 1 are summarized in graphical form from columns B to G. On tab 3, these goals and needs results are contrasted with your inputs on tab 2 (see next slide).

      1.2.2 Identify risk and constraints (1 of 2)

      Use tab 2 of the Force Field Analysis Workbook to assess opposing forces to change.

      30 minutes

      Input: Risks associated with determining the use case for Microsoft Project and M365 in your organization

      Output: Plotted risks based on probability and impact

      Materials: Whiteboard/Flip Charts, Force Field Analysis Tool

      Participants: Portfolio Manager (PMO Director), PMO Admin Team, Project Managers

      1. With the same working group from 1.2.1, brainstorm risks, constraints, and other opposing forces pertaining to your potential future state.
      2. Document relevant opposing forces in tab 2 of the Force Field Analysis Tool. For each opposing force for the change (note: a driving force can include goals and needs) that is identified, provide a category that explains why the opposing force is a concern (i.e. will it impact or is it impacted by time, resources, maturity, budget, or culture?).
      3. In addition, assess the likelihood of the risk or constraint coming to light and the negative impact of it coming to light for your proposed change.
      4. See the next slide for a screenshot that helps you navigate tab 2 of the Force Field Analysis Tool.

      Download the Force Field Analysis Tool

      1.2.2 Identify risk and constraints (2 of 2)

      Screenshot of tab 2 of the Force Field Analysis Workbook.

      Screenshot of tab 2 of the Force Field Analysis Workbook. There are five columns referred to as columns B through F with the headings 'Risks and Constraints', 'Category', 'Source', 'Likelihood of Constraint/Risk/Resisting Force Being Felt', and 'Impact to Derailing Goals and Needs'.

      In column B on tab 2, note the specific risks and constraints the group would like to call out.

      In column C, categorize the risk or constraint being articulated by the list of drop-down options: will it impact or is it impacted by time, resources, budget, culture or maturity?

      In column D, categorize the source of the goal or need as internal or external.

      In column E, use the drop-down menus to indicate the likelihood of each risk or constraint materializing during your implementation. Will it definitely occur or is there just a small chance it could come to light?

      In column F, use the drop-down menus to indicate the negative impact of the risk or constraint to achieving your goals and needs.

      On tab 3 of the Force Field Analysis Workbook, your inputs on tab 2 are summarized in graphical form from columns I to N. On tab 3, your risk and constraint results are contrasted with your inputs on tab 1 to help you gauge the relative weight of driving vs. opposing forces.

      Step 1.2

      Explore the Microsoft Project Plans and their capabilities

      Activities

      • 1.1.1 Review the Microsoft 365 licensing features
      • 1.1.2 Explore the Microsoft Project Plan licenses
      • 1.1.3 Prepare a needs assessment for Microsoft 365 and Project Plan licenses

      This step will walk you through the following activities:

      • Review the suite of task management, project management, and project portfolio management options available in Microsoft 365.
      • Prepare a preliminary checklist of required M365 apps for your stakeholders.

      This step usually involves the following participants:

      • PMO/Portfolio Manager
      • Project Managers
      • CIO and other executive stakeholders
      • Other project portfolio stakeholders (project and IT workers)

      Outcomes of Step

      • Preliminary requirements for an M365 project management and project portfolio management tool implementation

      Microsoft recently revamped its project plans to balance its old and new tech

      Access to the new tech, Project for the web, comes with all license types, while Project Online Professional and Premium licenses have been revamped as P3 and P5.

      Navigating Microsoft licensing is never easy, and Project for the web has further complicated licensing needs for project professionals.

      As we’ll cover in step 2.1 of this blueprint, Project for the web can be extended beyond its base lightweight work management functionality using the Power Platform (Power Apps, Power Automate, and Power BI). Depending on the scope of your implementation, this can require additional Power Platform licensing.

      • In this step, we will help you understand the basics of what’s already included in your enterprise M365 licensing as well as what’s new in Microsoft’s recent Project licensing plans (P1, P3, and P5).
      • As we cover toward the end of this step, you can use Info-Tech’s MS Project and M365 Licensing Tool to help you understand your plan and licensing needs. Further assistance on licensing can be found in the Task, Project, and Portfolio Management Tool Guides that accompany this blueprint and Info-Tech’s Modernize Your Microsoft Licensing for the Cloud Era.

      Download Info-Tech’s Modernize Your Microsoft Licensing for the Cloud Era

      Licensing features for knowledge workers

      Please note that licensing packages are frequently subject to change. This is up to date as of August 2021. For the most up-to-date information on licensing, visit the Microsoft website.

      Bundles are extremely common and can be more cost effective than à la carte options for the Microsoft products.

      The biggest differentiator between M365 and O365 is that the M365 product also includes Windows 10 and Enterprise Mobility and Security.

      The color coding in the diagram indicates that the same platform/application suite is available.

      Platform or Application M365 E3 M365 E5 O365 E1 O365 E3 O365 E5
      Microsoft Forms X X X X X
      Microsoft Lists X X X X X
      OneDrive X X X X X
      Planner X X X X X
      Power Apps for Office 365 X X X X X
      Power Automate for Office X X X X X
      Power BI Pro X X
      Power Virtual Agents for Teams X X X X X
      SharePoint X X X X X
      Stream X X X X X
      Sway X X X X X
      Teams X X X X X
      To Do X X X X X

      Get familiar with Microsoft Project Plan 1

      Please note that licensing packages are frequently subject to change. This is up to date as of August 2021. For the most up to date information on licensing, visit the Microsoft website.

      Who is a good fit?

      • New project managers
      • Zero-allocation project managers
      • Individuals and organizations who want to move out of Excel into something less fragile (easily breaking formulas)

      What does it include?

      • Access to Project Home, a landing page to access all project plans you’ve created or have been assigned to.
      • Access to Grid View, Board View, and Timeline (Gantt) View to plan and manage your projects with Project for the web
      • Sharing Project for the web plans across Microsoft Teams channels
      • Co-authoring on project plans

      When does it make sense?

      • Lightweight project management
      • No process to use bottom-up approach for resourcing data
      • Critical-path analysis is not required
      • Organization does not have an appetite for project management rigor

      Get familiar with Microsoft Project Plan 3

      Please note that licensing packages are frequently subject to change. This is up to date as of August 2021. For the most up to date information on licensing, visit the Microsoft website.

      Who is a good fit?

      • Experienced and dedicated project managers
      • Organizations with complex projects
      • Large project teams are required to complete project work
      • Organizations have experience using project management software

      What does it include?

      Everything in Project Plan 1 plus the following:

      • Reporting through Power BI Report template apps (note that there are no pre-built reports for Project for the web)
      • Access to build a Roadmap of projects from Project for the web and Azure DevOps with key milestones, statuses, and deadlines
      • Project Online to submit and track timesheets for project teams
      • MS Project Desktop Client to support resource management

      When does it make sense?

      • Project management is an established discipline at the organization
      • Critical-path analysis is commonly used
      • Organization has some appetite for project management rigor
      • Resources are expected to submit timesheets to allow for more precise resource management data

      Get familiar with Microsoft Project Plan 5

      Please note that licensing packages are frequently subject to change. This is up to date as of August 2021. For the most up to date information on licensing, visit the Microsoft website.

      Who is a good fit?

      • Experienced and dedicated project managers
      • Experienced and dedicated PMO directors
      • Dedicated portfolio managers
      • Organizations proficient at sustaining data in a standard tool

      What does it include?

      Everything in Project Plan 3 plus the following:

      • Portfolio selection and optimization
      • Demand management
      • Enterprise resource planning and management through deterministic task and resource scheduling
      • MS Project Desktop Client to support resource management

      When does it make sense?

      • Project management is a key success factor at the organization
      • Organization employs a bottom-up approach for resourcing data
      • Critical-path analysis is required
      • Formal project portfolio management processes are well established
      • The organization is willing to either put in the time, energy, and resources to learn to configure the system through DIY or is willing to leverage a Microsoft Partner to help them do so

      What’s included in each plan (1 of 2)

      Plan details are up to date as of September 2021. Plans and pricing can change often. Visit the Microsoft website to validate plan options and get pricing details.
      MS Project Capabilities Info-Tech's Editorial Description P1 P3 P5
      Project Home Essentially a landing page that allows you to access all the project plans you've created or that you're assigned to. It amalgamates plans created in Project for the web, the Project for the web app in Power Apps, and Project Online. X X X
      Grid view One of three options in which to create your project plans in Project for the web (board view and timeline view are the other options). You can switch back and forth between the options. X X X
      Board view One of three options in which to create your project plans in Project for the web (grid view and timeline view are the other options). You can switch back and forth between the options. X X X
      Timeline (Gantt) view One of three options in which to create your project plans in Project for the web (board view and grid view are the other options). You can switch back and forth between the options. X X X
      Collaboration and communication This references the ability to add Project for the web project plans to Teams channels. X X X
      Coauthoring Many people can have access to the same project plan and can update tasks. X X X
      Project planning and scheduling For this the marketing lingo says "includes familiar scheduling tools to assign project tasks to team members and use different views like Grid, Board, and Timeline (Gantt chart) to oversee the schedule." Unclear how this is different than the project plans in the three view options above. X X X

      X - Functionality Included in Plan

      O - Functionality Not Included in Plan

      What’s included in each plan (2 of 2)

      Plan details are up to date as of September 2021. Plans and pricing can change often. Visit the Microsoft website to validate plan options and get pricing details.
      MS Project Capabilities Info-Tech's Editorial Description P1 P3 P5
      Reporting This seems to reference Excel reports and the Power BI Report Template App, which can be used if you're using Project Online. There are no pre-built reports for Project for the web, but third-party Power Apps are available. O X X
      Roadmap Roadmap is a platform that allows you to take one or more projects from Project for the web and Azure DevOps and create an organizational roadmap. Once your projects are loaded into Roadmap you can perform additional customizations like color status reporting and adding key days and milestones. O X X
      Timesheet submission Project Online and Server 2013 and 2016 allow team members to submit timesheets if the functionality is required. O X X
      Resource management The rich MS Project client supports old school, deterministic project scheduling at the project level. O X X
      Desktop client The full desktop client comes with P3 and P5, where it acts as the rich editor for project plans. The software enjoys a multi-decade market dominance as a project management tool but was never paired with an enterprise collaboration server engine that enjoyed the same level of success. O X X
      Portfolio selection and optimization Portfolio selection and optimization has been offered as part of the enterprise project and portfolio suite for many years. Most people taking advantage of this capability have used a Microsoft Partner to formalize and operationalize the feature. O O X
      Demand Management Enterprise demand management is targeted at the most rigorous of project portfolio management practices. Most people taking advantage of this capability have used a Microsoft Partner to formalize and operationalize the feature. O O X
      Enterprise resource planning and management The legacy MS Project Online/Server platform supports enterprise-wide resource capacity management through an old-school, deterministic task and resource scheduling engine, assuming scaled-out deployment of Active Directory. Most people succeeding with this capability have used a Microsoft Partner to formalize and operationalize the feature. O O X

      X - Functionality Included in Plan

      O - Functionality Not Included in Plan

      Use Info-Tech’s MS Project and M365 Licensing Tool

      Leverage the analysis in Info-Tech’s MS Project & M365 Licensing Tool to help inform your initial assumptions about what you need and how much to budget for it.

      • The Licensing Tool can help you determine what Project Plan licensing different user groups might need as well as additional Power Platform licensing that may be required.
      • It consists of four main tabs: two set-up tabs where you can validate the plan and pricing information for M365 and MS Project; an analysis tab where you set up your user groups and follow a survey to assess their Project Plan needs; and another analysis tab where you can document your Power Platform licensing needs across your user groups.
      • There is also a business case tab that breaks down your total licensing needs. The outputs of this tab can be used in your MS Project & M365 Action Plan Template, which we will help you develop in phase three of this blueprint.

      Download Info-Tech's Microsoft Project & M365 Licensing Tool

      Sample of Info-Tech's Microsoft Project and M365 Licensing Tool.

      1.2.1 Conduct a needs assessment

      1-2 hours

      Input: List of key user groups/profiles, Number of users and current licenses

      Output: List of Microsoft applications/capabilities included with each license, Analysis of user group needs for Microsoft Project Plan licenses

      Materials: Microsoft Project & 365 Licensing Tool

      Participants: Portfolio Manager (PMO Director), PMO Admin Team, Project Managers

      1. As a group, analyze the applications included in your current or desired 365 license and calculate any additional Power Platform licensing needs.
      2. Screenshot of the 'Application/Capabilities' screen from the 'Microsoft Project and M365 Licensing Tool'.
      3. Within the same group, use the drop-down menus to analyze your high-level MS Project requirements by selecting whether each capability is necessary or not.
      4. Your inputs to the needs assessment will determine the figures in the Business Case tab. Consider exporting this information to PDF or other format to distribute to stakeholders.
      5. Screenshot of the 'Business Case' tab from the 'Microsoft Project and M365 Licensing Tool'.

      Download Info-Tech's Microsoft Project & M365 Licensing Tool

      Step 1.3

      Assess the maturity of your current PM & PPM capabilities

      Activities

      • Assess current state project and project portfolio management processes and tools
      • Determine target state project and project portfolio management processes and tools

      This step will walk you through the following activities:

      • Assess current state project and project portfolio management processes and tools
      • Determine target state project and project portfolio management processes and tools

      This step usually involves the following participants:

      • PMO/Portfolio Manager
      • Project Managers
      • CIO and other executive stakeholders
      • Other project portfolio stakeholders (project and IT workers)

      Outcomes of Step

      • Current and target state maturity for project management and project portfolio management processes

      Project portfolio management and project management are more than tools

      Implementing commercial tools without a matching level of process discipline is a futile exercise, leaving organizations frustrated at the wasted time and money.

      • The tool is only as good as the data that is input. There is often a misunderstanding that a tool will be “automatic.” While it is true that a tool can help make certain processes easier and more convenient by aggregating information, enhancing reporting, and coauthoring, it will not make up the data. If data becomes stale, the tool is no longer valid for accurate decision making.
      • Getting people onboard and establishing a clear process is often the hardest part. As IT folk, it can be easy to get wrapped up in the technology. All too often excitement around tools can drown out the important requisites around people and process. The reality is people and process are a necessary condition for a tool to be successful. Having a tool will not be sufficient to overcome obstacles like poor stakeholder buy-in, inadequate governance, and the absence of a standard operating procedure.

      • Slow is the way to go. When deciding what tools to purchase, start small and scale up rather than going all in and all too often ending up with many unused features and fees.

      "There's been a chicken-egg debate raging in the PPM world for decades: What comes first, the tool or the process? It seems reasonable to say, ‘We don't have a process now, so we'll just adopt the one in the tool.’ But you'll soon find out that the tool doesn't have a process, and you needed to do more planning and analysis before buying the tool." (Barry Cousins, Practice Lead, Project Portfolio Management)

      Assess your process maturity to determine the right tool approach

      Take the time to consider and reflect on the current and target state of the processes for project portfolio management and project management.

      Project Portfolio Management

      • Status and Progress Reporting
        1. Intake, Approval, and Prioritization

          PPM is the practice of selecting the right projects and ensuring the organization has the necessary resources to complete them. PPM should enable executive decision makers to make sense of the excess of demand and give IT the ability to prioritize those projects that are most valuable to the business.
        2. Resource Management

        3. Project Management

          1. Initiation
          2. Planning
          3. Execution
          4. Monitoring and Controlling
          5. Closing
          Tailor a project management framework to fit your organization. Formal methodologies aren’t always the best fit. Take what you can use from formal frameworks and define a right-sized approach to your project management processes.
        4. Project Closure

        5. Benefits Tracking

      Info-Tech’s maturity assessment tools can help you match your tools to your maturity level

      Use Info-Tech’s Project Portfolio Management Maturity Assessment Tool and Project Management Maturity Assessment Tool.

      • The next few slides in this step take you through using our maturity assessment tools to help gauge your current-state and target-state maturity levels for project management (PM) and project portfolio management (PPM).
      • In addition to the process maturity assessments, these workbooks also help you document current-state support tools and desired target-state tools.
      • The outputs of these workbooks can be used in your MS Project & M365 Action Plan Template, which we will help you develop in phase three of this blueprint.

      Download Info-Tech’s Project Portfolio Management Maturity Assessment Tool and Project Management Maturity Assessment Tool

      Samples of Info-Tech's Project Portfolio Management Maturity Assessment Tool and Project Management Maturity Assessment Tool.

      Conduct a gap analysis survey for both project and project portfolio management.

      • Review the category and activity statements: For each gap analysis tab in the maturity assessments, use the comprehensive activity statements to identify gaps for the organization.
      • Assess the current state: To assess the current state, evaluate whether the statement should be labeled as:
        • Absent: There is no evidence of any activities supporting this process.
        • Initial: Activity is ad hoc and not well defined.
        • Defined: Activity is established and there is moderate adherence to its execution.
        • Repeatable: Activity is established, documented, repeatable, and integrated with other phases of the process.
        • Managed: Activity execution is tracked by gathering qualitative and quantitative feedback

      Once this is documented, take some time to describe the type of tool being used to do this (commercial, home-grown, standardized document) and provide additional details, where applicable.

      Define the target state: Repeat the assessment of activity statements for the target state. Then gauge the organizational impact and complexity of improving each capability on a scale of very low to very high.

      Excerpt from Info-Tech's Project Portfolio Management Maturity Assessment Tool, the 'PPM Current State Target State Maturity Assessment Survey'. It has five columns whose purpose is denoted in notes. Column 1 'Category within the respective discipline'; Column 2 'Statement to consider'; Column 3 'Select the appropriate answer for current and target state'; Column 4 'Define the tool type'; Column 5 'Provide addition detail about the tool'.

      Analyze survey results for project and project portfolio management maturity

      Take stock of the gap between current state and target state.

      • What process areas have the biggest gap between current and target state?
      • What areas are aligned across current and target state?

      Identify what areas are currently the least and most mature.

      • What process area causes the most pain in the organization?
      • What process area is the organization’s lowest priority?

      Note the overall current process maturity.

      • After having done this exercise, does the overall maturity come as a surprise?
      • If so, what are some of the areas that were previously overlooked?
      A table and bar graph documenting and analysis of maturity survey results. The table has four columns labelled 'Process Area', 'Current Process Completeness', 'Current Maturity Level', and 'Target State Maturity'. Rows headers in the 'Process Area' column are 'Intake, Approval, and Prioritization', 'Resource Management', 'Portfolio Reporting', 'Project Closure and Benefits Realization', 'Portfolio Administration', and finally 'Overall Maturity'. The 'Current Process Completeness' column's values are in percentages. The 'Current Maturity Level' and 'Target State Maturity' columns' values can be one of the following: 'Absent', 'Initial', 'Defined', 'Repeatable', or 'Managed'. The bar chart visualizes the levels of the 'Target State' and 'Current State' with 'Absent' from 0-20%, 'Initial' from 20-40%, 'Defined' from 40-60%, 'Repeatable' from 60-80%, and 'Managed' from 80-100%.
      • Identify process areas with low levels of maturity
      • Spot areas of inconsistency between current and target state.
      • Assess the overall gap to get a sense of the magnitude of the effort required to get to the target state.
      • 100% doesn’t need to be the goal. Set a goal that is sustainable and always consider the value to effort ratio.

      Screenshot your results and put them into the MS Project and M365 Action Plan Template.

      Review the tool overview and plan to address gaps (tabs 3 & 4)

      Tool Overview:

      Analyze the applications used to support your project management and project portfolio management processes.

      Look for:

      • Tools that help with processes across the entire PM or PPM lifecycle.
      • Tools that are only used for one specific process.

      Reflect on the overlap between process areas with pain points and the current tools being used to complete this process.

      Consider the sustainability of the target-state tool choice

      Screenshot of a 'Tool Overview' table. Chart titled 'Current-to-Target State Supporting Tools by PPM Activity' documenting the current and target states of different supporting tools by PPM Activity. Tools listed are 'N/A', 'Standardized Document', 'Homegrown Tool', and 'Commercial Tool'.

      You have the option to create an action plan for each of the areas of improvement coming out of your maturity assessment.

      This can include:

      • Tactical Optimization Action: What is the main action needed to improve capability?
      • Related Actions: Is there a cross-over with any actions for other capabilities?
      • Timeframe: Is this near-term, mid-term, or long-term?
      • Proposed Start Date
      • Proposed Go-Live Date
      • RACI: Who will be responsible, accountable, consulted, and informed?
      • Status: What is the status of this action item over time?

      Determine the Future of Microsoft Project for Your Organization

      Phase 2: Weigh Your Implementation Options

      Phase 1: Determine Your Tool Needs

      Phase 2: Weigh Your Implementation Options

      Phase 3: Finalize Your Implementation Approach
      • Step 1.1: Survey the M365 work management landscape
      • Step 1.2: Perform a process maturity assessment to help inform your M365 starting point
      • Step 1.3: Consider the right MS Project licenses for your stakeholders
      • Step 2.1: Get familiar with extending Project for the web using Power Apps
      • Step 2.2: Assess the MS Gold Partner Community
      • Step 3.1: Prepare an action plan

      Phase Outcomes

      • A decision on how best to proceed (or not proceed) with Project for the web
      • A Partner outreach plan

      Step 2.1

      Get familiar with extending Project for the web using Power Apps

      Activities

      • Get familiar with Project for the web: how it differs from Microsoft’s traditional project offerings and where it is going
      • Understand the basics of how to extend Project for the web in Power Apps
      • Perform a feasibility test

      This step will walk you through the following activities:

      • Get familiar with Project for the web
      • Understand the basics of how to extend Project for the web in Power Apps
      • Perform a feasibility test to determine if taking a DIY approach to extending Project for the web is right for your organization currently

      This step usually involves the following participants:

      • Portfolio Manager (PMO Director)
      • Project Managers
      • Other relevant PMO stakeholders

      Outcomes of Step

      • A decision on how best to proceed (or not proceed) with Project for the web

      Project for the web is the latest of Microsoft’s project management offerings

      What is Project for the web?

      • First introduced in 2019 as Project Service, Project for the web (PFTW) is Microsoft’s entry into the world of cloud-based work management and lightweight project management options.
      • Built on the Power Platform and leveraging the Dataverse for data storage, PFTW integrates with the many applications that M365 users are already employing in their day-to-day work management and collaboration activities.
      • It is available as a part of your M365 subscription with the minimum activation of P1 license – it comes with P3 and P5 licenses as well.
      • From a functionality and user experience perspective, PFTW is closer to applications like Planner or Azure Boards than it is to traditional MS Project options.

      What does it do?

      • PFTW allows for task and dependency tracking and basic timeline creation and scheduling and offers board and grid view options. It also allows real-time coauthoring of tasks among team members scheduled to the same project.
      • PFTW also comes with a product/functionality Microsoft calls Roadmap, which allows users to aggregate multiple project timelines into a single view for reporting purposes.

      What doesn't it do?

      • With PFTW, Microsoft is offering noticeably less traditional project management functionality than its existing solutions. Absent are table stakes project management capabilities like critical path, baselining, resource load balancing, etc.

      Who is it for?

      • Currently, in its base lightweight project management option, PFTW is targeted toward occasional or part-time project managers (not the PMP-certified set) tasked with overseeing and/or collaborating on small to mid-sized initiatives and projects.

      Put Project for the web in perspective

      Out of the box, PFTW occupies a liminal space when it comes to work management options

      • More than a task management tool, but not quite a full project management tool
      • Not exactly a portfolio management tool, yet some PPM reporting functionality is inherent in the PFTW through Roadmap

      The table to the right shows some of the functionality in PFTW in relation to the task management functionality of Planner and the enterprise project and portfolio management functionality of Project Online.

      Table 2.1a Planner Project for the web Project Online
      Coauthoring on Tasks X X
      Task Planning X X X
      Resource Assignments X X X
      Board Views X X X
      MS Teams Integration X X X
      Roadmap X X
      Table and Gantt Views X X
      Task Dependency Tracking X X
      Timesheets X
      Financial Planning X
      Risks and Issues Tracking X
      Program Management X
      Advanced Portfolio Management X

      Project for the web will eventually replace Project Online

      • As early as 2018 Microsoft has been foreshadowing a transition away from the SharePoint-backed Project environments of Server and Online toward something based in Common Data Service (CDS) – now rebranded as the Dataverse.
      • Indeed, as recently as the spring of 2021, at its Reimagine Project Management online event, Microsoft reiterated its plans to sunset Project Online and transition existing Online users to the new environment of Project for the web – though it provided no firm dates when this might occur.
        • The reason for this move away from Online appears to be an acknowledgment that the rigidity of the tool is awkward in our current dynamic, collaborative, and overhead-adverse work management paradigm.
        • To paraphrase a point made by George Bullock, Sr. Product Marketing Manager, for Microsoft at the Reimagine Project Management event, teams want to manage work as they see fit, but the rigidity of legacy solutions doesn’t allow for this, leading to a proliferation of tools and data sprawl. (This comment was made during the “Overview of Microsoft Project” session during the Reimagine event.)

      PFTW is Microsoft’s proposed future-state antidote to this challenge. Its success will depend on how well users are able to integrate the solution into a wider M365 work management setting.

      "We are committed to supporting our customers on Project Online and helping them transition to Project for the Web. No end-of-support has been set for Project Online, but when the time comes, we will communicate our plans on the transition path and give you plenty of advance notice." (Heather Heide, Program Manager, Microsoft Planner and Project. This comment was made during the “Overview of Microsoft Project” session during the Reimagine event.)

      Project for the web can be extended beyond its base lightweight functionality

      Project for the web can be extended to add more traditional and robust project and project portfolio management functionality using the Power Platform.

      Microsoft plans to sunset Project Online in favor of PFTW will at first be a head-scratcher for those familiar with the extensive PPM functionality in Project Online and underwhelmed by the project and portfolio management in PFTW.

      However, having built the solution upon the Power Platform, Microsoft has made it possible to take the base functionality in PFTW and extend it to create a more custom, organizationally specific user experience.

      • With a little taste of what can be done with PFTW by leveraging the Power Platform – and, in particular, Power Apps – it becomes more obvious how we, as users, can begin to evolve the base tool toward a more traditional PPM solution and how, in time, Microsoft’s developers may develop the next iteration of PFTW into something more closely resembling Project Online.

      Before users get too excited about using these tools to build a custom PPM approach, we should consider the time, effort, and skills required. The slides ahead will take you through a series of considerations to help you gauge whether your PMO is ready to go it alone in extending the solution.

      Extending the tool enhances functionality

      Table 2.1a in this step displayed the functionality in PFTW in relation to the task management tool Planner and the robust PPM functionality in Online.

      The table to the right shows how the functionality in PFTW can differ from the base solution and Project Online when it is extended using the model-driven app option in Power Apps.

      Caveat: The list of functionality and processes in this table is sample data.

      This functionality is not inherent in the solution as soon as you integrate with Power Apps. Rather it must be built – and your success in developing these functions will depend upon the time and skills you have available.

      Table 2.1b Project for the web PFTW extended with PowerApps Project Online
      Critical Path X
      Timesheets X
      Financial Planning X X
      Risks and Issues Tracking X X
      Program Management X
      Status Updates X
      Project Requests X
      Business Cases X
      Project Charters X
      Resource Planning and Capacity Management X X
      Project Change Requests X

      Get familiar with the basics of Power Apps before you decide to go it alone

      While the concept of being able to customize and grow a commercial PPM tool is enticing, the reality of low-code development and application maintenance may be too much for resource-constrained PMOs.

      Long story short: Extending PFTW in Power Apps is time consuming and can be frustrating for the novice to intermediate user.

      It can take days, even weeks, just to find your feet in Power Apps, let alone to determine requirements to start building out a custom model-driven app. The latter activity can entail creating custom columns and tables, determining relationships between tables to get required outputs, in addition to basic design activities.

      Time-strapped and resource-constrained practitioners should pause before committing to this deployment approach. To help better understand the commitment, the slides ahead cover the basics of extending PFTW in Power Apps:

      1. Dataverse environments.
      2. Navigating Power App Designer and Sitemap Designer
      3. Customizing tables and forms in the Dataverse

      See Info-Tech’s M365 Project Portfolio Management Tool Guide for more information on Power Apps in general.

      Get familiar with Power Apps licensing

      Power Apps for 365 comes with E1 through E5 M365 licenses (and F3 and F5 licenses), though additional functionality can be purchased if required.

      While extending Project for the web with Power Apps does not at this time, in normal deployments, require additional licensing from what is included in a E3 or E5 license, it is not out of the realm of possibility that a more complex deployment could incur costs not included in the Power Apps for 365 that comes with your enterprise agreement.

      The table to the right shows current additional licensing options.

      Power Apps, Per User, Per App Plan

      Per User Plan

      Cost: US$10 per user per app per month, with a daily Dataverse database capacity of 40 MB and a daily Power Platform request capacity of 1,000. Cost: US$40 per user per month, with a daily Dataverse database capacity of 250 MB and a daily Power Platform request capacity of 5,000.
      What's included? This option is marketed as the option that allows organizations to “get started with the platform at a lower entry point … [or those] that run only a few apps.” Users can run an application for a specific business case scenario with “the full capabilities of Power Apps” (meaning, we believe, that unlicensed users can still submit data via an app created by a licensed user). What's included? A per-user plan allows licensed users to run unlimited canvas apps and model-driven apps – portal apps, the licensing guide says, can be “provisioned by customers on demand.” Dataverse database limits (the 250 MB and 5,000 request capacity mentioned above) are pooled at the per tenant, not the per user plan license, capacity.

      For more on Power Apps licensing, refer to Info-Tech’s Modernize Your Microsoft Licensing for the Cloud Era for more information.

      What needs to be configured?

      Extending Project for the web requires working with your IT peers to get the right environments configured based upon your needs.

      • PFTW data is stored in the Microsoft Dataverse (formerly Common Data Service or CDS).
      • The organization’s Dataverse can be made up of one to many environments based upon its needs. Environments are individual databases with unique proprieties in terms of who can access them and what applications can store data in them.
      • Project for the web supports three different types of environments: default, production, and sandbox.
      • You can have multiple instances of a custom PFTW app deployed across these environments and across different users – and the environment you choose depends upon the use case of each instance.

      Types of Environments

      • Default Environment

        • It is the easiest to deploy and get started with the PFTW Power App in the default environment. However, it is also the most restricted environment with the least room for configuration.
        • Microsoft recommends this environment for simple deployments or for projects that span the organization. This is because everyone in the organization is by default a member of this environment – and, with the least room for configuration, the app is relatively straightforward.
        • At minimum, you need one project license to deploy PFTW in the default environment.
      • Production Environment

        • This environment affords more flexibility for how a custom app can be configured and deployed. Unlike the default environment, deploying a production environment is a manual process (through the Power Platform Admin Center) and security roles need to be set to limit users who can access the environment.
        • Because users can be limited, production environments can be used to support more advanced deployments and can support diverse processes for different teams.
        • At present, you need at least five Project licenses to deploy to production environments.
      • Sandbox Environment

        • This environment is for users who are responsible for the creation of custom apps. It offers the same functionality as a production environment but allows users to make changes without jeopardizing a production environment.

      Resources to provide your IT colleagues with to help in your PFTW deployment:

      1. Project for the web admin help (Product Documentation, Microsoft)
      2. Advanced deployment for Project for the web (Video, Microsoft)
      3. Get Started with Project Power App (Product Support Documentation, Microsoft)
      4. Project for the Web Security Roles (Product Support Documentation, Microsoft)

      Get started creating or customizing a model-driven app

      With the proper environments procured, you can now start extending Project for the web.

      • Navigate to the environment you would like to extend PFTW within. For the purposes of the slides ahead, we’ll be using a sandbox environment for an example. Ensure you have the right access set up for production and sandbox environments of your own (see links on previous slide for more assistance).
      • To begin extending PFTW, the two core features you need to be familiar with before you start in Power Apps are (1) Tables/Entities and (2) the Power Apps Designer – and in particular the Site Map.

      From the Power Apps main page in 365, you can change your environment by selecting from the options in the top right-hand corner of the screen.

      Screenshot of the Power Apps “Apps” page in a sandbox environment. The Project App will appear as “Project” when the application is installed, though it is also easy to create an app from scratch.

      Model-driven apps are built around tables

      In Power Apps, tables (formerly called entities and still referred to as entities in the Power Apps Designer) function much like tables in Excel: they are containers of columns of data for tracking purposes. Tables define the data for your app, and you build your app around them.

      In general, there are three types of tables:

      • Standard: These are out-of-the box tables included with a Dataverse environment. Most standard tables can be customized.
      • Managed: These are tables that get imported into an environment as part of a managed solution. Managed tables cannot be customized.
      • Custom: These types of tables can either be imported from another solution or created directly in the Dataverse environment. To create custom tables, users need to have System Administrator or System Customizer security roles within the Dataverse.

      Tables can be accessed under Data banner on the left-hand panel of your Power Apps screen.

      The below is a list of standard tables that can be used to customize your Project App.

      A screenshot of the 'Data' banner in 'Power Apps' and a list of table names.

      Table Name

      Display Name

      msdyn_project Project
      msdyn_projectchange Change
      msdyn_projectprogram Program
      msdyn_projectrequest Request
      msdyn_projectrisk Risk
      msdyn_projectissue Issue
      msdyn_projectstatusreport Status

      App layouts are designed in the Power App Designer

      You configure tables with a view to using them in the design of your app in the Power Apps Designer.

      • If you’re customizing a Project for the web app manually installed into your production or sandbox environment, you can access Designer by highlighting the app from your list of apps on the Apps page and clicking “Edit” in the ribbon above.
        • If you’re creating a model-driven app from scratch, Designer will open past the “Create a New App” intro screen.
        • If you need to create separate apps in your environment for different PMOs or business units, it is as easy to create an app from scratch as it is to customize the manual install.
      • The App Designer is where you can design the layout of your model-driven app and employ the right data tables.
      Screenshot of the 'App Designer' screen in 'Power Apps'.

      The Site Map determines the navigation for your app, i.e. it is where you establish the links and pages users will navigate. We will review the basics of the sitemap on the next few slides.

      The tables that come loaded into your Project Power App environment (at this time, 37) via the manual install will appear in the Power Apps Designer in the Entity View pane at the bottom of the page. You do not have to use all of them in your design.

      Navigate the Sitemap Designer

      With the components of the previous two slides in mind, let’s walk through how to use them together in the development of a Project app.

      As addressed in the previous slide, the sitemap determines the navigation for your app, i.e. it is where you establish the links and the pages that users will navigate.

      To get to the Sitemap Designer, highlight the Project App from your list of apps on the Apps page and click “Edit” in the ribbon above. If you’re creating a model-driven app from scratch, Designer will open past the “Create a New App” intro screen.

      • To start designing your app layout, click the pencil icon beside the Site Map logo on the App Designer screen.
      • This will take you into the Sitemap Designer (see screenshot to the right). This is where you determine the layout of your app and the relevant data points (and related tables from within the Dataverse) that will factor into your Project App.
      • In the Sitemap Designer, you simply drag and drop the areas, groups, and subareas you want to see in your app’s user interface (see next slide for more details).
      Screenshot of the 'Sitemap Designer' in 'Power Apps'.

      Use Areas, Groups, and Subareas as building blocks for your App

      Screenshots of the main window and the right-hand panel in the 'Sitemap Designer', and of the subarea pop-up panel where you connect components to data tables. The first two separate elements into 'Area', 'Group', and 'Subarea'.

      Drag and drop the relevant components from the panel on the right-hand side of the screen into the main window to design the core pieces that will be present within your user interface.

      For each subarea in your design, use the pop-up panel on the right-hand side of the screen to connect your component the relevant table from within your Dataverse environment.

      How do Areas, Groups, and Subareas translate into an app?

      Screenshots of the main window in the 'Sitemap Designer' and of a left-hand panel from a published 'Project App'. There are notes defining the terms 'Area', 'Group', and 'Subarea' in the context of the screenshot.

      The names or titles for your Areas and Groups can be customized within the Sitemap Designer.

      The names or titles for your Subareas is dependent upon your table name within the Dataverse.

      Area: App users can toggle the arrows to switch between Areas.

      Group: These will change to reflect the chosen Area.

      Subarea: The tables and forms associated with each subarea.

      How to properly save and publish your changes made in the Sitemap Designer and Power Apps Designer:

      1. When you are done making changes to your components within the Sitemap Designer, and want your changes to go live, hit the “Publish” button in the top right corner; when it has successfully published, select “Save and Close.”
      2. You will be taken back to the Power App Designer homepage. Hit “Save,” then “Publish,” and then finally “Play,” to go to your app or “Save and Close.”

      How to find the right tables in the Dataverse

      While you determine which tables will play into your app in the Sitemap Designer, you use the Tables link to customize tables and forms.

      Screenshots of the tables search screen and the 'Tables' page under the 'Data' banner in 'Power Apps'.

      The Tables page under the Data banner in Power Apps houses all of the tables available in your Dataverse environment. Do not be overwhelmed or get too excited. Only a small portion of the tables in the Tables folder in Power Apps will be relevant when it comes to extending PFTW.

      Find the table you would like to customize and/or employ in your app and select it. The next slides will look at customizing the table (if you need to) and designing an app based upon the table.

      To access all the tables in your environment, you’ll need to ensure your filter is set correctly on the top right-hand corner of the screen, otherwise you will only see a small portion of the tables in your Dataverse environment.

      If you’re a novice, it will take you some time to get familiar with the table structure in the Dataverse.

      We recommend you start with the list of tables listed on slide. You can likely find something there that you can use or build from for most PPM purposes.

      How to customize a table (1 of 3)

      You won’t necessarily need to customize a table, but if you do here are some steps to help you get familiar with the basics.

      Screenshot of the 'Columns' tab, open in the 'msdyn_project table' in 'Power Apps'.

      In this screenshot, we are clicked into the msdyn_project (display name: Project) table. As you can see, there are a series of tabs below the name of the table, and we are clicked into the Columns tab. This is where you can see all of the data points included in the table.

      You are not able to customize all columns. If a column that you are not able to customize does not meet your needs, you will need to create a custom column from the “+Add column” option.

      “Required” or “Optional” status pertains to when the column or field is used within your app. For customizable or custom columns this status can be set when you click into each column.

      How to customize a table (2 of 3)

      Create a custom “Status” column.

      By way of illustrating how you might need to customize a table, we’ll highlight the “msdyn_project_statecode” (display name: Project Status) column that comes preloaded in the Project (msdyn_project) table.

      • The Project Status column only gives you a binary choice. While you are able to customize what that binary choice is (it comes preloaded with “Active” and “Inactive” as the options) you cannot add additional choices – so you cannot set it to red/yellow/green, the most universally adopted options for status in the project portfolio management world.
      • Because of this, let’s look at the effort involved in creating a choice and adding a custom column to your table based upon that choice.
      Screenshots of the '+New choice' button in the 'Choices' tab and the 'New choice' pane that opens when you click it.

      From within the Choices tab, click “+New choice” option to create a custom choice.

      A pane will appear to the right of your screen. From there you can give your choice a name, and under the “Items” header, add your list of options.

      Click save. Your custom choice is now saved to the Choices tab in the Dataverse environment and can be used in your table. Further customizations can be made to your choice if need be.

      How to customize a table (3 of 3)

      Back in the Tables tab, you can put your new choice to work by adding a column to a table and selecting your custom choice.

      Screenshots of the pop-up window that appear when you click '+Add Column', and details of what happens when you select the data type 'Choice'.

      Start by selecting “+ Add Column” at the top left-hand side of your table. A window will appear on the right-hand side of the page, and you will have options to name your column and choose the data type.

      As you can see in this screenshot to the left, data type options include text, number and date types, and many more. Because we are looking to use our custom choice for this example, we are going to choose “Choice.”

      When you select “Choice” as your data type, all of the choice options available or created in your Dataverse environment will appear. Find your custom choice – in this example the one name “RYG Status” – and click done. When the window closes, be sure to select “Save Table.”

      How to develop a Form based upon your table (1 of 3 – open the form editor)

      A form is the interface users will engage with when using your Project app.

      When the Project app is first installed in your environment, the main user form will be lacking, with only a few basic data options.

      This form can be customized and additional tabs can be added to your user interface.

      1. To do this, go to the table you want to customize.
      2. In the horizontal series of tabs at the top of the screen, below the table title select the “Forms” option.
      3. Click on the main information option or select Edit Form for the form with “Main” under its form type. A new window will open where you can customize your form.
      Screenshot of the 'Forms' tab, open in the 'msdyn_project' table in 'Power Apps'.

      Select the Forms tab.

      Start with the form that has “Main” as its Format Type.

      How to develop a Form based upon your table (2 of 3 – add a component)

      Screenshot of the 'Components' window in 'Power Apps' with a list of layouts as a window to the right of the main screen where you can name and format the chosen layout.

      You can add element like columns or sections to your form by selecting the Components window.

      In this example, we are adding a 1-Column section. When you select that option from the menu options on the left of the screen, a window will open to the right of the screen where you can name and format the section.

      Choose the component you would like to add from the layout options. Depending on the table element you are looking to use, you can also add input options like number inputs and star ratings and pull in related data elements like a project timeline.

      How to develop a Form based upon your table (3 of 3 – add table columns)

      Screenshot of the 'Table Columns' window in 'Power Apps' and instructions for adding table columns.

      If you click on the “Table Columns” option on the left-hand pane, all of the column options from within your table will appear in alphabetical order.

      When clicked within the form section you would like to add the new column to, select the column from the list of option in the left-hand pane. The new data point will appear within the section. You can order and format section elements as you would like.

      When you are done editing the form, click the “Save” icon in the top right-hand corner. If you are ready for your changes to go live within your Project App, select the “Publish” icon in the top right-hand corner. Your updated form will go live within all of the apps that use it.

      The good and the bad of extending Project for the web

      The content in this step has not instructed users how to extend PFTW; rather, it has covered three basic core pieces of Power Apps that those interesting in PFTW need to be aware of: Dataverse environments, the Power Apps and Sitemaps Designers, and Tables and associated Forms.

      Because we have only covered the very tip of the iceberg, those interested in going further and taking a DIY approach to extending PFTW will need to build upon these basics to unlock further functionality. Indeed, it takes work to develop the product into something that begins to resemble a viable enterprise project and portfolio management solution. Here are some of the good and the bad elements associated with that work:

      The Good:

      • You can right-size and purpose build: add as much or as little project management rigor as your process requires. Related, you can customize the solution in multiple ways to suit the needs of specific business units or portfolios.
      • Speed to market: it is possible to get up and running quickly with a minimum-viable product.

      The Bad:

      • Work required: to build anything beyond MVP requires independent research and trial and error.
      • Time required: to build anything beyond MVP requires time and skills that many PMOs don’t have.
      • Shadow support costs: ungoverned app creation could have negative support and maintenance impacts across IT.

      "The move to Power Platform and low code development will […increase] maintenance overhead. Will low code solution hit problems at scale? [H]ow easy will it be to support hundreds or thousands of small applications?

      I can hear the IT support desks already complaining at the thought of this. This part of the puzzle is yet to hit real world realities of support because non developers are busy creating lots of low code applications." (Ben Hosking, Software Developer and Blogger, "Why low code software development is eating the world")

      Quick start your extension with the Accelerator

      For those starting out, there is a pre-built app you can import into your environment to extend the Project for the web app without any custom development.

      • If the DIY approach in the previous slides was overwhelming, and you don’t have the budget for a MS Partner route in the near-term, this doesn’t mean that evolving your Project for the web app is unattainable.
      • Thanks to a partnership between OnePlan (one of the MS Gold Partners we detail in the next step) and Microsoft, Project for the web users have access to a free resource to help them evolve the base Project app. It’s called the “Project for the web Accelerator” (commonly referred to as “the Accelerator” for short).
      • Users interested in learning more about, and accessing, this free resource should refer to the links below:
        1. The Future of Microsoft Project Online (source: OnePlan).
        2. Introducing the Project Accelerator (source: Microsoft).
        3. Project for the web Accelerator (source: GitHub)
      Screen shot from one of the dashboards that comes with the Accelerator (image source: GitHub).

      2.1.1 Perform a feasibility test (1 of 2)

      15 mins

      As we’ve suggested, and as the material in this step indicates, extending PFTW in a DIY fashion is not small task. You need a knowledge of the Dataverse and Power Apps, and access to the requisite skills, time, and resources to develop the solution.

      To determine whether your PMO and organization are ready to go it alone in extending PFTW, perform the following activity:

      1. Convene a collection of portfolio, project, and PMO staff.
      2. Using the six-question survey on tab 5 of the Microsoft Project & M365 Licensing Tool (see screenshot to the right) as a jumping off point for a discussion, consider the readiness of your PMO or project organization to undertake a DIY approach to extending and implementing PFTW at this time.
      3. You can use the recommendations on tab 5 of the Microsoft Project & 365 Licensing Tool to inform your next steps, and input the gauge graphic in section 4 of the Microsoft Project & M365 Action Plan Template.
      Screenshots from the 'Project for the Web Extensibility Feasibility Test'.

      Go to tab 5 of the Microsoft Project & M365 Licensing Tool

      See next slide for additional activity details

      2.1.1 Perform a feasibility test (2 of 2)

      Input: The contents of this step, The Project for the Web Extensibility Feasibility Test (tab 5 in the Microsoft Project & 365 Licensing Tool)

      Output: Initial recommendations on whether to proceed and how to proceed with a DIY approach to extending Project for the web

      Materials: The Project for the Web Extensibility Feasibility Test (tab 5 in the Microsoft Project & 365 Licensing Tool)

      Participants: Portfolio Manager (PMO Director), Project Managers, Other relevant PMO stakeholders

      Step 2.2

      Assess the Microsoft Gold Partner Community

      Activities

      • Review what to look for in a Microsoft Partner
      • Determine whether your needs would benefit from reaching out to a Microsoft Partner
      • Review three key Partners from the North American market
      • Create a Partner outreach plan

      This step will walk you through the following activities:

      • Review what to look for in a Microsoft Partner.
      • Determine whether your needs would benefit from reaching out to a Microsoft Partner.
      • Review three key Partners from the North American market.

      This step usually involves the following participants:

      • Portfolio Manager (PMO Director)
      • Project Managers
      • Other relevant PMO stakeholders

      Outcomes of Step

      • A better understanding of MS Partners
      • A Partner outreach plan

      You don’t have to go it alone

      Microsoft has an established community of Partners who can help in your customizations and implementations of Project for the web and other MS Project offerings.

      If the content in the previous step seemed too technical or overly complex in a way that scared you away from a DIY approach to extending Microsoft’s latest project offering (and at some point in the near future, soon to be its only project offering), Project for the web, fear not.

      You do not have to wade into the waters of extending Project for the web alone, or for that matter, in implementing any other MS Project solution.

      Instead, Microsoft nurtures a community of Silver and Gold partners who offer hands-on technical assistance and tool implementation services. While the specific services provided vary from partner to partner, all can assist in the customization and implementation of any of Microsoft’s Project offerings.

      In this step we will cover what to look for in a Partner and how to assess whether you are a good candidate for the services of a Partner. We will also highlight three Partners from within the North American market.

      The basics of the Partner community

      What is a Microsoft Partner?

      Simply put, an MS Gold Partner is a software or professional services organization that provides sales and services related to Microsoft products.

      They’re resellers, implementors, integrators, software manufacturers, trainers, and virtually any other technology-related business service.

      • Microsoft has for decades opted out of being a professional services organization, outside of its very “leading edge” offerings from MCS (Microsoft Consulting Services) for only those technologies that are so new that they aren’t yet supported by MS Partners.
      • As you can see in the chart on the next slide, to become a silver or gold certified partner, firms must demonstrate expertise in specific areas of business and technology in 18 competency areas that are divided into four categories: applications and infrastructure, business applications, data and AI, and modern workplace and security.

      More information on what it takes to become a Microsoft Partner:

      1. Partner Center (Document Center, Microsoft)
      2. Differentiate your business by attaining Microsoft competencies (Document Center, Microsoft)
      3. Partner Network Homepage (Webpage, Microsoft)
      4. See which partner offer is right for you (Webpage, Microsoft)

      Types of partnerships and qualifications

      Microsoft Partner Network

      Microsoft Action Pack

      Silver Competency

      Gold Competency

      What is it?

      The Microsoft Partner Network (MPN) is a community that offers members tools, information, and training. Joining the MPN is an entry-level step for all partners. The Action Pack is an annual subscription offered to entry-level partners. It provides training and marketing materials and access to expensive products and licenses at a vastly reduced price. Approximately 5% of firms in the Microsoft Partner Network (MPN) are silver partners. These partners are subject to audits and annual competency exams to maintain silver status. Approximately 1% of firms in the Microsoft Partner Network (MPN) are gold partners. These partners are subject to audits and annual competency exams to maintain Gold status.

      Requirements

      Sign up for a membership Annual subscription fee While requirements can vary across competency area, broadly speaking, to become a silver partner firms must:
      • Pass regular exams and skills assessments, with at least two individuals on staff with Microsoft Certified Professional Status.
      • Hit annual customer, revenue, and licensing metrics.
      • Pay the annual subscription fee.
      While requirements can vary across competency area, broadly speaking, to become a gold partner firms must:
      • Pass regular exams and skills assessments, with at least two individuals on staff with Microsoft Certified Professional Status.
      • Hit annual customer, revenue, and licensing metrics.
      • Pay the annual subscription fee.

      Annual Fee

      No Cost $530 $1800 $5300

      When would a MS Partner be helpful?

      • Project management and portfolio management practitioners might look into procuring the services of a Microsoft Partner for a variety of reasons.
      • Because services vary from partner to partner (help to extend Project for the web, implement Project Server or Project Online, augment PMO staffing, etc.) we won’t comment on specific needs here.
      • Instead, the three most common conditions that trigger the need are listed to the right.

      Speed

      When you need to get results faster than your staff can grow the needed capabilities.

      Cost

      When the complexity of the purchase decision, implementation, communication, training, configuration, and/or customization cannot be cost-justified for internal staff, often because you’ll only do it once.

      Expertise & Skills

      When your needs cannot be met by the core Microsoft technology without significant extension or customization.

      Canadian Microsoft Partners Spotlight

      As part of our research process for this blueprint, Info-Tech asked Microsoft Canada for referrals and introductions to leading Microsoft Partners. We spent six months collaborating with them on fresh research into the underlying platform.

      These vendors are listed below and are highlighted in subsequent slides.

      Spotlighted Partners:

      Logo for One Plan. Logo for PMO Outsource Ltd. Logo for Western Principles.

      Please Note: While these vendors were referred to us by Microsoft Canada and have a footprint in the Canadian market, their footprints extend beyond this to the North American and global markets.

      A word about our approach

      Photo of Barry Cousins, Project Portfolio Management Practice Lead, Info-Tech Research Group.
      Barry Cousins
      Project Portfolio Management Practice Lead
      Info-Tech Research Group

      Our researchers have been working with Microsoft Project Online and Microsoft Project Server clients for years, and it’s fair to say that most of these clients (at some point) used a Microsoft Partner in their deployment. They’re not really software products, per se; they’re platforms. As a Microsoft Partner in 2003 when Project Server got its first big push, I heard it loud and clear: “Some assembly required. You might only make 7% on the licensing, but the world’s your oyster for services.”

      In the past few years, Microsoft froze the market for major Microsoft Project decisions by making it clear that the existing offering is not getting updates while the new offering (Project for the web) doesn’t do what the old one did. And in a fascinating timing coincidence, the market substantially adopted Microsoft 365 during that period, which enables access to Project for the web.

      Many of Info-Tech’s clients are justifiably curious, confused, and concerned, while the Microsoft Partners have persisted in their knowledge and capability. So, we asked Microsoft Canada for referrals and introductions to leading Microsoft Partners and spent six months collaborating with them on fresh research into the underlying platform.

      Disclosure: Info-Tech conducted collaborative research with the partners listed on the previous slide to produce this publication. Market trends and reactions were studied, but the only clients identified were in case studies provided by the Microsoft Partners. Info-Tech’s customers have been, and remain, anonymous. (Barry Cousins, Project Portfolio Management Practice Lead, Info-Tech Research Group)

      MS Gold Partner Spotlight:

      OnePlan

      Logo for One Plan.
      Headquarters: San Marcos, California, and Toronto, Ontario
      Number of Employees: ~80
      Active Since: 2007 (as EPMLive)
      Website: www.oneplan.ai

      Who are they?

      • While the OnePlan brand has only been the marketplace for a few years, the company has been a major player in MS Gold Partner space for well over a decade.
      • Born out of EPMLive in the mid-aughts, OnePlan Solutions has evolved through a series of acquisitions, including Upland, Tivitie, and most recently Wicresoft.

      What do they do?

      • Software: Its recent rebranding is largely because OnePlan Solutions is as much a software company as it is a professional services firm. The OnePlan software product is an impressive solution that can be used on its own to facilitate the portfolio approaches outlined on the next slide and that can also integrate with the tools your organization is already using to manage tasks (see here for a full rundown of the solutions within the Microsoft stack and beyond OnePlan can integrate with).
      • Beyond its ability to integrate with existing solutions, as a software product, OnePlan has modules for resource planning, strategic portfolio planning, financial planning, time tracking, and more.

      • PPM Consulting Services: The OnePlan team also offers portfolio management consulting services. See the next slide for a list of its approaches to project portfolio management.

      Markets served

      • US, Canada, Europe, and Australia

      Channel Differentiation

      • OnePlan scales to all the PPM needs of all industry types.
      • Additionally, OnePlan offers insights and functionality specific to the needs of BioTech-Pharma.

      What differentiates OnePlan?

      • OnePlan co-developed the Project Accelerator for Project for the web with Microsoft. The OnePlan team’s involvement in developing the Accelerator and making it free for users to access suggests it is aligned to and has expertise in the purpose-built and collaborative vision behind Microsoft’s move away from Project Online and toward the Power Platform and Teams collaboration.
      • 2021 MS Gold Partner of the Year. At Microsoft’s recent Microsoft Inspire event, OnePlan was recognized as the Gold Partner of the Year for Project and Portfolio Management as well as a finalist for Power Apps and Power Automate.
      • OnePlan Approaches: Below is a list of the services or approaches to project portfolio management that OnePlan provides. See its website for more details.
        • Strategic Portfolio Management: Align work to objectives and business outcomes. Track performance against the proposed objectives outcomes.
        • Agile Portfolio Management: Implement Agile practices across the organization, both at the team and executive level.
        • Adaptive Portfolio Management: Allow teams to use the project methodology and tools that best suit the work/team. Maintain visibility and decision making across the entire portfolio.
        • Professional Services Automation: Use automation to operate with greater efficiency.

      "OnePlan offers a strategic portfolio, financial and resource management solution that fits the needs of every PMO. Optimize your portfolio, financials and resources enterprise wide." (Paul Estabrooks, Vice President at OnePlan)

      OnePlan Case Study

      This case study was provided to Info-Tech by OnePlan.

      Brambles

      INDUSTRY: Supply Chain & Logistics
      SOURCE: OnePlan

      Overview: Brambles plays a key role in the delivery or return of products amongst global trading partners such as manufacturers, distributors and retailers.

      Challenge

      Brambles had a variety of Project Management tools with no easy way of consolidating project management data. The proliferation of project management solutions was hindering the execution of a long-term business transformation strategy. Brambles needed certain common and strategic project management processes and enterprise project reporting while still allowing individual project management solutions to be used as part of the PPM platform.

      Solution

      As part of the PMO-driven business transformation strategy, Brambles implemented a project management “operating system” acting as a foundation for core processes such as project intake, portfolio management, resource, and financial planning and reporting while providing integration capability for a variety of tools used for project execution.

      OnePlan’s new Adaptive PPM platform, combining the use of PowerApps and OnePlan, gives Brambles the desired PPM operating system while allowing for tool flexibility at the execution level.

      Results

      • Comprehensive picture of progress across the portfolio.
      • Greater adoption by allowing flexibility of work management tools.
      • Modern portfolio management solution that enables leadership to make confident decision.

      Solution Details

      • OnePlan
      • Project
      • Power Apps
      • Power Automate
      • Power BI
      • Teams

      Contacting OnePlan Solutions

      www.oneplan.ai

      Joe Larscheid: jlarscheid@oneplan.ai
      Paul Estabrooks: pestabrooks@oneplan.ai
      Contact Us: contact@oneplan.ai
      Partners: partner@oneplan.ai

      Partner Resources. OnePlan facilitates regular ongoing live webinars on PPM topics that anyone can sign up for on the OnePlan website.

      For more information on upcoming webinars, or to access recordings of past webinars, see here.

      Additional OnePlan Resources

      1. How to Extend Microsoft Teams into a Collaborative Project, Portfolio and Work Management Solution (on-demand webinar, OnePlan’s YouTube channel)
      2. What Does Agile PPM Mean To The Modern PMO (on-demand webinar, OnePlan’s YouTube channel)
      3. OnePlan is fused with the Microsoft User Experience (blog article, OnePlan)
      4. Adaptive Portfolio Management Demo – Bringing Order to the Tool Chaos with OnePlan (product demo, OnePlan’s YouTube channel)
      5. How OnePlan is aligning with Microsoft’s Project and Portfolio Management Vision (blog article, OnePlan)
      6. Accelerating Office 365 Value with a Hybrid Project Portfolio Management Solution (product demo, OnePlan’s YouTube channel)

      MS Gold Partner Spotlight:

      PMO Outsource Ltd.

      Logo for PMO Outsource Ltd.

      Headquarters: Calgary, Alberta, and Mississauga, Ontario
      Website: www.pmooutsource.com

      Who are they?

      • PMO Outsource Ltd. is a Microsoft Gold Partner and PMI certified professional services firm based in Alberta and Ontario, Canada.
      • It offers comprehensive project and portfolio management offerings with a specific focus on project lifecycle management, including demand management, resource management, and governance and communication practices.

      What do they do?

      • Project Online and Power Platform Expertise. The PMO Outsource Ltd. team has extensive knowledge in both Microsoft’s old tech (Project Server and Desktop) and in its newer, cloud-based technologies (Project Online, Project for the web, the Power Platform, and Dynamics 365). As the case study in two slides demonstrates, PMO Outsource Ltd. Uses its in-depth knowledge of the Microsoft suite to help organizations automate project and portfolio data collection process, create efficiencies, and encourage cloud adoption.
      • PPM Consulting Services: In addition to its Microsoft platform expertise, the PMO Outsource Ltd. team also offers project and portfolio management consulting services, helping organizations evolve their process and governance structures as well as their approaches to PPM tooling.

      Markets served

      • Global

      Channel Differentiation

      • PMO Outsource Ltd. scales to all the PPM needs of all industry types.

      What differentiates PMO Outsource Ltd.?

      • PMO Staff Augmentation. In addition to its technology and consulting services, PMO Outsource Ltd. offers PMO staff augmentation services. As advertised on its website, it offers “scalable PMO staffing solutions. Whether you require Project Managers, Business Analysts, Admins or Coordinators, [PMO Outsource Ltd.] can fulfill your talent search requirements from a skilled pool of resources.”
      • Multiple and easy-to-understand service contract packages. PMO Outsource Ltd. offers many prepackaged service offerings to suit PMOs’ needs. Those packages include “PMO Management, Admin, and Support,” “PPM Solution, Site and Workflow Configuration,” and “Add-Ons.” For full details of what’s included in these services packages, see the PMO Outsource Ltd. website.
      • PMO Outsource Ltd. Services: Below is a list of the services or approaches to project portfolio management that PMO Outsource Ltd. Provides. See its website for more details.
        • Process Automation, Workflows, and Tools. Facilitate line of sight by tailoring Microsoft’s technology to your organization’s needs and creating custom workflows.
        • PMO Management Framework. Receive a professionally managed PPM methodology as well as governance standardization of processes, tools, and templates.
        • Custom BI Reports. Leverage its expertise in reporting and dashboarding to create the visibility your organization needs.

      "While selecting an appropriate PPM tool, the PMO should not only evaluate the standard industry tools but also analyze which tool will best fit the organization’s strategy, budget, and culture in the long run." (Neeta Manghnani, PMO Strategist, PMO Outsource Ltd.)

      PMO Outsource Ltd. Case Study

      This case study was provided to Info-Tech by PMO Outsource Ltd.

      SAMUEL

      INDUSTRY: Manufacturing
      SOURCE: PMO Outsource Ltd.

      Challenge

      • MS Project 2013 Server (Legacy/OnPrem)
      • Out-of-support application and compliance with Office 365
      • Out-of-support third-party application for workflows
      • No capability for resource management
      • Too many manual processes for data maintenance and server administration

      Solution

      • Migrate project data to MS Project Online
      • Recreate workflows using Power Automate solution
      • Configure Power BI content packs for Portfolio reporting and resource management dashboards
      • Recreate OLAP reports from legacy environment using Power BI
      • Cut down nearly 50% of administrative time by automating PMO/PPM processes
      • Save costs on Server hardware/application maintenance by nearly 75%

      Full Case Study Link

      • For full details about how PMO Outsource Ltd. assisted Samuel in modernizing its solution and creating efficiencies, visit the Microsoft website where this case study is highlighted.

      Contacting PMO Outsource Ltd.

      www.pmooutsource.com

      700 8th Ave SW, #108
      Calgary, AB T2P 1H2
      Telephone : +1 (587) 355-3745
      6045 Creditview Road, #169
      Mississauga, ON L5V 0B1
      Telephone : +1 (289) 334-1228
      Information: info@pmooutsource.com
      LinkedIn: https://www.linkedin.com/company/pmo-outsource/

      Partner Resources. PMO Outsource Ltd.’s approach is rooted within a robust and comprehensive PPM framework that is focused on driving strategic outcomes and business success.

      For a full overview of its PPM framework, see here.

      Additional PMO Outsource Ltd. Resources

      1. 5 Benefits of PPM tools and PMO process automation (blog article, PMO Outsource Ltd.)
      2. Importance of PMO (blog article, PMO Outsource Ltd.)
      3. Meet the Powerful and Reimagined PPM tool for Everyone! (video, PMO Outsource Ltd. LinkedIn page)
      4. MS Project Tips: How to add #Sprints to an existing Project? (video, PMO Outsource Ltd. LinkedIn page)
      5. MS Project Tips: How to add a milestone to your project? (video, PMO Outsource Ltd. LinkedIn page)
      6. 5 Benefits of implementing Project Online Tools (video, PMO Outsource Ltd. LinkedIn page)

      MS Gold Partner Spotlight:

      Western Principles

      Logo for Western Principles.

      Headquarters: Vancouver, British Columbia
      Years Active: 16 Years
      Website: www.westernprinciples.com

      Who are they?

      • Western Principles is a Microsoft Gold Partner and UMT 360 PPM software provider based in British Columbia with a network of consultants across Canada.
      • In the last sixteen years, it has successfully conducted over 150 PPM implementations, helping in the implementation, training, and support of Microsoft Project offerings as well as UMT360 – a software solution provider that, much like OnePlan, enhances the PPM capabilities of the Microsoft platform.

      What do they do?

      • Technology expertise. The Western Principles team helps organizations maximize the value they are getting form the Microsoft Platform. Not only does it offer expertise in all the solutions in the MS Project ecosystem, it also helps organizations optimize their use and understanding of Teams, SharePoint, the Power Platform, and more. In addition to the Microsoft platform, Western Principles is partnered with many other technology providers, including UMT360 for strategic portfolio management, the Simplex Group for project document controls, HMS for time sheets, and FluentPro for integration, back-ups, and migrations.
      • PPM Consulting Services: In addition to its technical services and solutions, Western Principles offers PPM consulting and staff augmentation services.

      Markets served

      • Canada

      Channel Differentiation

      • Western Principles scales to all the PPM needs of all industry types, public and private sector.
      • In addition, its website offers persona-specific information based on the PPM needs of engineering and construction, new product development, marketing, and more.

      What differentiates Western Principles?

      • Gold-certified UMT 360 partner. In addition to being a Microsoft Gold Partner, Western Principles is a gold-certified UMT 360 partner. UMT 360 is a strategic portfolio management tool that integrates with many other work management solutions to offer holistic line of sight into the organization’s supply-demand pain points and strategic portfolio management needs. Some of the solutions UMT 360 integrates with include Project Online and Project for the web, Azure DevOps, Jira, and many more. See here for more information on the impressive functionality in UMT360.
      • Sustainment Services. Adoption can be the bane of most PPM tool implementations. Among the many services Western Principles offers, its “sustainment services” stand out. According to Western Principles’ website, these services are addressed to those who require “continual maintenance, change, and repair activities” to keep PPM systems in “good working order” to help maximize ROI.
      • Western Principles Services: In addition to the above, below is a list of some of the services that Western Principles offers. See its website for a full list of services.
        • Process Optimization: Determine your requirements and process needs.
        • Integration: Create a single source of truth.
        • Training: Ensure your team knows how to use the systems you implement.
        • Staff Augmentation: Provide experienced project team members based upon your needs.

      "One of our principles is to begin with the end in mind. This means that we will work with you to define a roadmap to help you advance your strategic portfolio … and project management capabilities. The roadmap for each customer is different and based on where you are today, and where you need to get to." (Western Principles, “Your Strategic Portfolio Management roadmap,” Whitepaper)

      Contacting Western Principles

      www.westernprinciples.com

      610 – 700 West Pender St.
      Vancouver, BC V6C 1G8
      +1 (800) 578-4155
      Information: info@westernprinciples.com
      LinkedIn: https://www.linkedin.com/company/western-principle...

      Partner Resources. Western Principles provides a multitude of current case studies on its home page. These case studies let you know what the firm is working on this year and the type of support it provides to its clientele.

      To access these case studies, see here.

      Additional Western Principles Resources

      1. Program and Portfolio Roll ups with Microsoft Project and Power BI (video, Western Principles YouTube Channel)
      2. Dump the Spreadsheets for Microsoft Project Online (video, Western Principles YouTube Channel)
      3. Power BI for Project for the web (video, Western Principles YouTube Channel)
      4. How to do Capacity Planning and Resource Management in Microsoft Project Online [Part 1 & Part 2] (video, Western Principles YouTube Channel)
      5. Extend & Integrate Microsoft Project (whitepaper, Western Principles)
      6. Your COVID-19 Return-to-Work Plan (whitepaper, Western Principles)

      Watch Info-Tech’s Analyst-Partner Briefing Videos to lean more

      Info-Tech was able to sit down with the partners spotlighted in this step to discuss the current state of the PPM market and Microsoft’s place within it.

      • All three partners spotlighted in this step contributed to Info-Tech’s research process for this publication.
      • For two of the partners, OnePlan and PMO Outsource Ltd., Info-Tech was able to record a conversation where our analysts and the partners discuss Microsoft’s current MS Project offerings, the current state of the PPM tool market, and the services and the approaches of each respective partner.
      • A third video briefing with Western Principles has not happened yet due to logistical reasons. We are hoping we can include a video chat with our peers at Western Principles in the near future.
      Screenshot form the Analyst-Partner Briefing Videos. In addition to the content covered in this step, you can use these videos for further information about the partners to inform your next steps.

      Download Info-Tech’s Analyst-Partner Briefing Videos (OnePlan & PMO Outsource Ltd.)

      2.2.1 Create a partner outreach plan

      1-3 hours

      Input: Contents of this step, List of additional MS Gold Partners

      Output: A completed partner outreach program

      Materials: MS Project & M365 Action Plan Template

      Participants: Portfolio Manager (PMO Director), PMO Admin Team, Project Managers, CIO

      1. With an understanding of the partner ecosystem, compile a working group of PMO peers and stakeholders to produce a gameplan for engaging the MS Gold Partner ecosystem.
        • For additional partner options see Microsoft’s Partner Page.
      2. Using slide 20 in Info-Tech’s MS Project and M365 Action Plan Template, document the Partners you would want or have scheduled briefings with.
        • As you go through the briefings and research process, document the pros and cons and areas of specialized associated with each vendor for your particular work management implementation.

      Download the Microsoft Project & M365 Action Plan Template

      2.2.2 Document your PM and PPM requirements

      1-3 hours

      Input: Project Portfolio Management Maturity Assessment, Project Management Maturity Assessment

      Output: MS Project & M365 Action Plan Template

      Materials: Project Portfolio Management Maturity Assessment, Project Management Maturity Assessment, MS Project & M365 Action Plan Template

      Participants: Portfolio Manager (PMO Director), PMO Admin Team, Project Managers, CIO

      1. As you prepare to engage the Partner Community, you should have a sense of where your project management and project portfolio management gaps are to better communicate your tooling needs.
      2. Leverage tab 4 from both your Project Portfolio Management Assessment and Project Management Assessment from step 1.3 of this blueprint to help document and communicate your requirements. Those tabs prioritize your project and portfolio management needs by highest impact for the organization.
      3. You can use the outputs of the tab to inform your inputs on slide 23 of the MS Project & M365 Action Plan Template to present to organizational stakeholders and share with the Partners you are briefing with.

      Download the Microsoft Project & M365 Action Plan Template

      Determine the Future of Microsoft Project for Your Organization

      Phase 3: Finalize Your Implementation Approach

      Phase 1: Determine Your Tool NeedsPhase 2: Weigh Your Implementation Options

      Phase 3: Finalize Your Implementation Approach

      • Step 1.1: Survey the M365 work management landscape
      • Step 1.2: Perform a process maturity assessment to help inform your M365 starting point
      • Step 1.3: Consider the right MS Project licenses for your stakeholders
      • Step 2.1: Get familiar with extending Project for the web using Power Apps
      • Step 2.2: Assess the MS Gold Partner Community
      • Step 3.1: Prepare an action plan

      Phase Outcomes

      An action plan concerning what to do with MS Project and M365 for your PMO or project organization.

      Step 3.1

      Prepare an action plan

      Activities

      • Compile the current state results
      • Prepare an Implementation Roadmap
      • Complete your presentation deck

      This step will walk you through the following activities:

      • Assess the impact of organizational change for the project
      • Develop your vision for stakeholders
      • Compile the current state results and document the implementation approach
      • Create clarity through a RACI and proposed implementation timeline

      This step usually involves the following participants:

      • Portfolio Manager (PMO Director)
      • PMO Admin Team
      • Business Analysts
      • Project Managers

      Outcomes of Step

      • Microsoft Project and M365 Action Plan

      Assess the impact of organizational change

      Be prepared to answer: “What’s in it for me?”

      Before jumping into licensing and third-party negotiations, ensure you’ve clearly assessed the impact of change.

      Tailor the work effort involved in each step, as necessary:

      1. Assess the impact
        • Use the impact assessment questions to identify change impacts.
      2. Plan for change
        • Document the impact on each stakeholder group.
        • Anticipate their response.
        • Curate a compelling message for each stakeholder group.
        • Develop a communication plan.
      3. Act according to plan
        • Identify your executive sponsor.
        • Enable the sponsor to drive change communication.
        • Coach managers on how they can drive change at the individual level.

      Impact Assessment Questions

      • Will the change impact how our clients/customers receive, consume, or engage with our products/services?
      • Will there be a price increase?
      • Will there be a change to compensation and/or rewards?
      • Will the vision or mission of the job change?
      • Will the change span multiple locations/time zones?
      • Are multiple products/services impacted by this change?
      • Will staffing levels change?
      • Will this change increase the workload?
      • Will the tools of the job be substantially different?
      • Will a new or different set of skills be needed?
      • Will there be a change in reporting relationships?
      • Will the workflow and approvals be changed?
      • Will there be a substantial change to scheduling and logistics?

      Master Organizational Change Management Practices blueprint

      Develop your vision for stakeholders

      After careful analysis and planning, it’s time to synthesize your findings to those most impacted by the change.

      Executive Brief

      • Prepare a compelling message about the current situation.
      • Outline the considerations the working group took into account when developing the action plan.
      • Succinctly describe the recommendations proposed by the working group.

      Goals

      • Identify the goals for the project.
      • Explain the details for each goal to develop the organizational rationale for the project.
      • These goals are the building blocks for the change communication that the executive sponsor will use to build a coalition of sponsors.

      Future State Vision

      • Quantify the high-level costs and benefits of moving forward with this project.
      • Articulate the future- state maturity level for both the project and project portfolio management process.
      • Reiterate the organizational rationale and drivers for change.

      "In failed transformations, you often find plenty of plans, directives, and programs, but no vision…A useful rule of thumb: If you can’t communicate the vision to someone in five minutes or less and get a reaction that signifies both understanding and interest, you are not yet done…" (John P. Kotter, Leading Change)

      Get ready to compile the analysis completed throughout this blueprint in the subsequent activities. The outputs will come together in your Microsoft Project and M365 Action Plan.

      Use the Microsoft Project & M365 Action Plan Template to help communicate your vision

      Our boardroom-ready presentation and communication template can be customized using the outputs of this blueprint.

      • Getting stakeholders to understand why you are recommending specific work management changes and then communicating exactly what those changes are and what they will cost is key to the success of your work management implementation.
      • To that end, the slides ahead walk you through how to customize the Microsoft Project & M365 Action Plan Template.
      • Many of the current-state analysis activities you completed during phase 1 of this blueprint can be directly made use of within the template as can the decisions you made and requirements you documented during phase 2.
      • By the end of this step, you will have a boardroom-ready presentation that will help you communicate your future-state vision.
      Screenshot of Info-Tech's Microsoft Project and M365 Action Plan Template with a note to 'Update the presentation or distribution date and insert your name, role, and organization'.

      Download Info-Tech’s Microsoft Project & M365 Action Plan Template

      3.1.1 Compile current state results

      1-3 hours

      Input: Force Field Analysis Tool, Tool Audit Workbook, Project Management Maturity Assessment Tool, Project Portfolio Management Maturity Assessment Tool

      Output: Section 1: Executive Brief, Section 2: Context and Constraints

      Materials: Microsoft Project and M365 Action Plan Template

      Participants: PMO Director, PMO Admin Team, Business Analysts, Project Managers

      1. As a group, review the results of the tools introduced throughout this blueprint. Use this information along with organizational knowledge to document the business context and current state.
      2. Update the driving forces for change and risks and constraints slides using your outputs from the Force Field Analysis Tool.
      3. Update the current tool landscape, tool satisfaction, and tool audit results slides using your outputs from the Tool Audit Workbook.
      4. Update the gap analysis results slides using your outputs from the Project Management and Project Portfolio Management Maturity Assessment Tools.

      Screenshots of 'Business Context and Current State' screen from the 'Force Field Analysis Tool', the 'Tool Audit Results' screen from the 'Tool Audit Workbook', and the 'Project Portfolio Management Gap Analysis Results' screen from the 'PM and PPM Maturity Assessments Tool'.

      Download the Microsoft Project & M365 Action Plan Template

      3.2.1 Option A: Prepare a DIY roadmap

      1-3 hours; Note: This is only applicable if you have chosen the DIY route

      Input: List of key PPM decision points, List of who is accountable for PPM decisions, List of who has PPM decision-making authority

      Output: Section 3: DIY Implementation Approach

      Materials: Microsoft Project and M365 Action Plan Template

      Participants: PMO Director, PMO Admin Team, Business Analysts, Project Managers

      1. As a group, review the results of the Microsoft Project and M365 Licensing Tool. Use this information along with organizational knowledge and discussion with the working group to complete Section 3: DIY Implementation Approach.
      2. Copy and paste your results from tab 5 of the Microsoft Project and M365 Licensing Tool. Update the Implementation Approach slide to detail the rationale for selecting this option.
      3. Update the Action Plan to articulate the details for total and annual costs of the proposed licensing solution.
      4. Facilitate a discussion to determine roles and responsibilities for the implementation. Based on the size, risk, and complexity of the implementation, create a reasonable timeline.
      Screenshots from the 'Microsoft Project and M365 Action Plan Template' outlining the 'DIY Implementation Approach'.

      Download the Microsoft Project and M365 Action Plan Template

      3.2.1 Option b: Prepare a Partner roadmap

      1-3 hours; Note: This is only applicable if you have chosen the Partner route

      Input: Microsoft Project and M365 Licensing Tool, Information on Microsoft Partners

      Output: Section 4: Microsoft Partner Implementation Route

      Materials: Microsoft Project and M365 Action Plan Template

      Participants: PMO Director, PMO Admin Team, Business Analysts, Project Managers

      1. As a group, review the results of the Microsoft Project and M365 Licensing Tool. Use this information along with organizational knowledge and discussion with the working group to complete Section 4: Microsoft Partner Implementation Route.
      2. Copy and paste your results from tab 5 of the Microsoft Project and M365 Licensing Tool. Update the Implementation Approach slide to detail the rationale for selecting this option.
      3. Develop an outreach plan for the Microsoft Partners you are planning to survey. Set targets for briefing dates and assign an individual to own any back-and-forth communication. Document the pros and cons of each Partner and gauge interest in continuing to analyze the vendor as a possible solution.
      4. Facilitate a discussion to determine roles and responsibilities for the implementation. Based on the size, risk, and complexity of the implementation, create a reasonable timeline.

      Screenshots from the 'Microsoft Project and M365 Action Plan Template' outlining the 'Microsoft Partner Implementation Route'.

      Microsoft Project and M365 Action Plan Template

      3.1.2 Complete your presentation deck

      1-2 hours

      Input: Outputs from the exercises in this blueprint

      Output: Section 5: Future-State Vision and Goals

      Materials: Microsoft Project and M365 Action Plan Template

      Participants: PMO Director, PMO Admin Team, Business Analysts, Project Managers

      1. Put the finishing touches on your presentation deck by documenting your future- state vision and goals.
      2. Prepare to present to your stakeholders.
        • Understand your audience, their needs and priorities, and their degree of knowledge and experiences with technology. This informs what to include in your presentation and how to position the message and goal.
      3. Review the deck beginning to end and check for spelling, grammar, and vertical logic.
      4. Practice delivering the vision for the project through several practice sessions.

      Screenshots from the 'Microsoft Project and M365 Action Plan Template' regarding finishing touches.

      Microsoft Project and M365 Action Plan Template

      Pitch your vision to key stakeholders

      There are multiple audiences for your pitch, and each audience requires a different level of detail when addressed. Depending on the outcomes expected from each audience, a suitable approach must be chosen. The format and information presented will vary significantly from group to group.

      Audience

      Key Contents

      Outcome

      Business Executives

      • Section 1: Executive Brief
      • Section 2: Context and Constraints
      • Section 5: Future-State Vision and Goals
      • Identify executive sponsor

      IT Leadership

      • Sections 1-5 with a focus on Section 3 or 4 depending on implementation approach
      • Get buy-in on proposed project
      • Identify skills or resourcing constraints

      Business Managers

      • Section 1: Executive Brief
      • Section 2: Context and Constraints
      • Section 5: Future-State Vision and Goals
      • Get feedback on proposed plan
      • Identify any unassessed risks and organizational impacts

      Business Users

      • Section 1: Executive Brief
      • Support the organizational change management process

      Summary of Accomplishment

      Problem Solved

      Knowledge Gained
      • How you work: Work management and the various ways of working (personal and team task management, strategic project portfolio management, formal project management, and enterprise project and portfolio management).
      • Where you need to go: Project portfolio management and project management current- and target-state maturity levels.
      • What you need: Microsoft Project Plans and requisite M365 licensing.
      • The skills you need: Extending Project for the web.
      • Who you need to work with: Get to know the Microsoft Gold Partner community.
      Deliverables Completed
      • M365 Tool Guides
      • Tool Audit Workbook
      • Force Field Analysis Tool
      • Project Portfolio Management Maturity Assessment Tool
      • Project Management Maturity Assessment Tool
      • Microsoft Project & M365 Action Plan Template

      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.

      Photo of Barry Cousins.
      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:

      Perform a work management tool audit

      Gain insight into the tools that drive value or fail to drive value across your work management landscape with a view to streamline the organization’s tool ecosystem.

      Prepare an action plan for your tool needs

      Prepare the right work management tool recommendations for your IT teams and/or business units and develop a boardroom-ready presentation to communicate needs and next steps.

      Research Contributors and Experts

      Neeta Manghnani
      PMO Strategist
      PMO Outsource Ltd.

      Photo of Neeta Manghnani, PMO Strategist, PMO Outsource Ltd.
      • Innovative, performance-driven executive with significant experience managing Portfolios, Programs & Projects, and technical systems for international corporations with complex requirements. A hands-on, dynamic leader with over 20 years of experience guiding and motivating cross-functional teams. Highly creative and brings a blend of business acumen and expertise in multiple IT disciplines, to maximize the corporate benefit from capital investments.
      • Successfully deploys inventive solutions to automate processes and improve the functionality, scalability and security of critical business systems and applications. Leverages PMO/PPM management and leadership skills to meet the strategic goals and business initiatives.

      Robert Strickland
      Principal Consultant & Owner
      PMO Outsource Ltd.

      Photo of Robert Strickland, Principal Consultant and Owner, PMO Outsource Ltd.
      • Successful entrepreneur, leader, and technologist for over 15 years, is passionate about helping organizations leverage the value of SharePoint, O365, Project Online, Teams and the Power Platform. Expertise in implementing portals, workflows and collaboration experiences that create business value. Strategic manager with years of successful experience building businesses, developing custom solutions, delivering projects, and managing budgets. Strong transformational leader on large implementations with a technical pedigree.
      • A digital transformation leader helping clients move to the cloud, collaborate, automate their business processes and eliminate paper forms, spreadsheets and other manual practices.

      Related Info-Tech Research

      • Develop a Project Portfolio Management Strategy
        Time is money; spend it wisely.
      • Establish Realistic IT Resource Management Practices
        Holistically balance IT supply and demand to avoid overallocation.
      • Tailor Project Management Processes to Fit Your Projects
        Spend less time managing processes and more time delivering results

      Bibliography

      “13 Reasons not to use Microsoft Project.” Celoxis, 14 Sept. 2018. Accessed 17 Sept. 2021.

      Advisicon. “Project Online vs Project for the Web.” YouTube, 13 Nov. 2013. Accessed 17 Sept. 2021.

      Branscombe, Mary. “Is Project Online ready to replace Microsoft Project?” TechRepublic, 23 Jan. 2020. Accessed 17 Sept. 2021.

      Chemistruck, Dan. “The Complete Office 365 and Microsoft 365 Licensing Comparison.” Infused Innovations, 4 April 2019. Accessed 17 Sept. 2021.

      “Compare Project management solutions and costs.” Microsoft. Accessed 17 Sept. 2021.

      Day to Day Dynamics 365. “Microsoft Project for the web - Model-driven app.” YouTube, 29 Oct. 2019. Accessed 17 Sept. 2021.

      “Deploying Project for the web.” Microsoft, 24 Aug. 2021. Accessed 17 Sept. 2021.

      “Differentiate your business by attaining Microsoft competencies.” Microsoft, 26 Jan. 2021. Accessed 17 Sept. 2021.

      “Extend & Integrate Microsoft Project.” Western Principles. Accessed 17 Sept. 2021.

      “Get Started with Project Power App.” Microsoft. Accessed 17 Sept. 2021.

      Hosking, Ben. “Why low code software development is eating the world.” DevGenius, May 2021. Accessed 17 Sept. 2021.

      “How in the World is MS Project Still a Leading PM Software?” CBT Nuggets, 12 Nov. 2018. Accessed 17 Sept. 2021.

      Integent. “Project for the Web - Create a Program Entity and a model-driven app then expose in Microsoft Teams.” YouTube, 25 Mar. 2020. Accessed 17 Sept. 2021.

      “Introducing the Project Accelerator.” Microsoft, 10 Mar. 2021. Accessed 17 Sept. 2021.

      “Join the Microsoft Partner Network.” Microsoft. Accessed 17 Sept. 2021.

      Kaneko, Judy. “How Productivity Tools Can Lead to a Loss of Productivity.” Bluescape, 2 Mar. 2018 Accessed 17 Sept. 2021.

      Kotter, John. Leading Change. Harvard Business School Press, 1996.

      Leis, Merily. “What is Work Management.” Scoro. Accessed 17 Sept. 2021.

      Liu, Shanhong. “Number of Office 365 company users worldwide as of June 2021, by leading country.” Statistica, 2021. Web.

      Manghnani, Neeta. “5 Benefits of PPM tools and PMO process automation.” PMO Outsource Ltd., 11 Apr. 2021. Accessed 17 Sept. 2021.

      “Microsoft 365 and Office 365 plan options.” Microsoft, 31 Aug. 2021. Accessed 17 Sept. 2021.

      “Microsoft 365 for enterprise.” Microsoft. Accessed 17 Sept. 2021

      “Microsoft Office 365 Usage Statistics.” Thexyz blog, 18 Sept. 2020. Accessed 17 Sept. 2021.

      “Microsoft Power Apps, Microsoft Power Automate and Microsoft Power Virtual Agents Licensing Guide.” Microsoft, June 2021. Web.

      “Microsoft Project service description.” Microsoft, 31 Aug. 2021. Accessed 17 Sept. 2021.

      “Microsoft Project Statistics.” Integent Blog, 12 Dec. 2013. Accessed 17 Sept. 2021.

      Nanji, Aadil . Modernize Your Microsoft Licensing for the Cloud Era. Info-Tech Research Group, 12 Mar. 2020. Accessed 17 Sept. 2021.

      “Number of Office 365 company users worldwide as of June 2021, by leading country.” Statista, 8 June 2021. Accessed 17 Sept. 2021.

      “Overcoming disruption in a digital world.” Asana. Accessed 17 Sept. 2021.

      Pajunen, Antti. “Customizing and extending Project for the web.” Day to Day Dynamics 365, 20 Jan. 2020. Accessed 17 Sept. 2021.

      “Partner Center Documentation.” Microsoft. Accessed 17 Sept. 2021.

      Pragmatic Works. “Building First Power Apps Model Driven Application.” YouTube, 21 June 2019. Accessed 17 Sept. 2021.

      “Project architecture overview.” Microsoft, 27 Mar. 2020. Accessed 17 Sept. 2021.

      “Project for the web Accelerator.” GitHub. Accessed 17 Sept. 2021.

      “Project for the web admin help.” Microsoft, 28 Oct. 2019. Accessed 17 Sept. 2021.

      “Project for the Web – The New Microsoft Project.” TPG. Accessed 17 Sept. 2021.

      “Project for the Web Security Roles.” Microsoft, 1 July 2021. Accessed 17 Sept. 2021.

      “Project Online: Project For The Web vs Microsoft Project vs Planner vs Project Online.” PM Connection, 30 Nov. 2020. Accessed 17 Sept. 2021.

      Redmond, Tony. “Office 365 Insights from Microsoft’s FY21 Q2 Results.” Office 365 for IT Pros, 28 Jan. 2021. Accessed 17 Sept. 2021.

      Reimagine Project Management with Microsoft. “Advanced deployment for Project for the web.” YouTube, 4 Aug. 2021. Accessed 17 Sept. 2021.

      Reimagine Project Management with Microsoft. “Overview of Microsoft Project.” YouTube, 29 July 2021. Accessed 17 Sept. 2021.

      “See which partner offer is right for you.” Microsoft. Accessed 17 Sept. 2021.

      Shalomova, Anna. “Microsoft Project for Web 2019 vs. Project Online: What’s Best for Enterprise Project Management?” FluentPro, 23 July 2020. Accessed 17 Sept. 2021.

      Speed, Richard. “One Project to rule them all: Microsoft plots end to Project Online while nervous Server looks on.” The Register, 28 Sept. 2018. Accessed 17 Sept. 2021.

      Spataro, Jared. “A new vision for modern work management with Microsoft Project.” Microsoft, 25 Sept. 2018. Accessed 17 Sept. 2021.

      Stickel, Robert. “OnePlan Recognized as Winner of 2021 Microsoft Project & Portfolio Management Partner of the Year.” OnePlan, 8 July 2021. Accessed 17 Sept. 2021.

      Stickel, Robert. “The Future of Project Online.” OnePlan, 2 Mar. 2021. Accessed 17 Sept. 2021.

      Stickel, Robert. “What It Means to be Adaptive.” OnePlan, 24 May 2021. Accessed 17 Sept. 2021.

      “The Future of Microsoft Project Online.” OnePlan. Accessed 17 Sept. 2021.

      Weller, Joe. “Demystifying Microsoft Project Licensing.” Smartsheet, 10 Mar. 2016. Accessed 17 Sept. 2021.

      Western Principles Inc. “Dump the Spreadsheets for Microsoft Project Online.” YouTube, 2 July 2020. Accessed 17 Sept. 2021.

      Western Principles Inc. “Project Online or Project for the web? Which project management system should you use?” YouTube, 11 Aug. 2020. Accessed 17 Sept. 2021.

      “What is Power Query?” Microsoft, 22 July 2021. Web.

      Wicresoft. “The Power of the New Microsoft Project and Microsoft 365.” YouTube, 29 May 2020. Accessed 17 Sept. 2021.

      Wicresoft. “Why the Microsoft Power Platform is the Future of PPM.” YouTube, 11 June 2020. Accessed 17 Sept. 2021.

      Customer Service Management Software Selection Guide

      • Buy Link or Shortcode: {j2store}530|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 business is unaware of cross-selling opportunities across multiple product lines.
      • Customer service staff attrition rates continue to be high, creating longer response delays for voice channels.
      • Customer service responses are reactive in nature, reinforcing a poor culture for customer experience.

      Our Advice

      Critical Insight

      • After-sales customer service is critical for creating, maintaining, and growing customer relationships. Organizations that fail to provide adequate service will be ill positioned for future customer service and sales efforts.
      • Shift left toward delivering predictive service instead of reactive service to enhance customer experiences.
      • Ensure your key performance indicators accurately reflect the incentives you want to give your customer support staff for delivering appropriate customer service.

      Impact and Result

      • Determine your organization’s customer service maturity (and thus if a standalone CSM tool is relevant).
      • Understand key trends and differentiating features in the CSM marketspace.
      • Evaluate major vendors in the CSM marketspace to discover the best-fitting provider.

      Customer Service Management Software Selection Guide Research & Tools

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

      1. Customer Service Management Software Selection Guide – A guide to walk you through the process of selecting CSM software.

      This trends and buyer’s guide will help you:

      • Customer Service Management Software Selection Guide Storyboard

      2. CSM Platform RFP Template – A template to provide vendors with a detailed account of the requirements and the expected capabilities of the desired suite.

      Create your own request for proposal (RFP) for your customer service management suite procurement process by customizing Info-Tech's RFP template.

      • CSM Platform RFP Template

      3. CSM Platform Opportunity Assessment Tool – A tool to assess whether a CSM solution is right for your organization.

      Use this tool to assess your maturity and fit for a CSM solution. It will help identify your current CSM state and assist with the decision to move forward with a new solution or augment certain features.

      • CSM Platform Opportunity Assessment Tool

      4. Software Selection Workbook – A workbook to document your progress as your select software.

      Keep stakeholders engaged with simple and friction-free templates to document your progress for Rapid Application Selection.

      • The Software Selection Workbook

      5. Vendor Evaluation Workbook – A workbook to assess vendor capabilities and compare vendors.

      Leverage a traceable and straightforward Vendor Evaluation Workbook to narrow the field of potential vendors and accelerate the application selection process.

      • The Vendor Evaluation Workbook

      6. CSM Platform RFP Scoring Tool – A tool to support your business in objectively evaluating the CSM vendors being considered for procurement.

      Create an objective and fair scoring process to evaluate the RFPs and demonstrations provided by shortlisted vendors. Within this framework, provide a multidimensional evaluation that analyzes the solution's functional capabilities, architecture, costs, service support, and overall suitability in comparison to the organization's expressed requirements.

      • CSM Platform RFP Scoring Tool

      7. CSM Platform Vendor Demo Script Template – A template to support your business’ evaluation of vendors and their solutions with an effective demonstration.

      Create an organized and streamlined vendor demonstration process by clearly outlining your expectations for the demo. Use the demo as an opportunity to ensure that capabilities expressed by vendors are actually present within the considered solution.

      • CSM Platform Vendor Demo Script Template
      [infographic]

      Further reading

      Customer Service Management Software Selection

      Market trends and buyer’s guide

      Analyst Perspective

      The pandemic and growing younger demographic have shifted the terrain of customer service delivery. Customer service management (CSM) tools ensure organizations enhance customer acquisition, customer retention, and overall revenues into the future.

      It is one thing to research customer service best practices; it is another to experience such service. Whether being put on hold for an hour with a telecommunications company, encountering voice biometric security with a bank, or receiving automated FAQs from a chatbot, we all perform our own primary research in customer service by going about our daily lives. Yet while the pandemic required a shift to this multichannel and digital assistant environment (to account for ongoing agent attrition), this trend was actually just accelerated. A growing younger demographic now prefers online communication channels to voice. Social media (whichever the platform) is a fundamental part of this demographic’s online presence and has instigated the need for customer service delivery to meet customers where they are – for both damage control and enhancing customer relationships.

      Organizations delivering customer service across multiple product lines need to examine what delivery channels they need to satisfy customers, alongside assessing how customer loyalty and cross-selling can increase revenues and company reputation. Customer service management tools can assist and enable the future state.

      Thomas Randall, Ph.D., Research Director

      Thomas Randall, Ph.D.
      Research Director, Info-Tech Research Group

      Executive Summary

      Your Challenge Common Obstacles Info-Tech’s Solution
      • The business is unaware of cross-selling opportunities across multiple product lines.
      • Customer service staff attrition rates continue to be high, creating longer response delays for voice channels.
      • Customer service responses are reactive in nature, reinforcing a poor culture for customer experience.
      • It is not clear if a CSM tool would resolve the business’ challenges or if a better-fitting technology solution is preferable (such as a customer relationship management add-on).
      • The business does not know its customer service maturity well enough to assess the feasibility of adopting a CSM tool.
      This trends and buyer’s guide will help you:
      1. Determine your organization’s customer service maturity (and thus if a standalone CSM tool is relevant).
      2. Understand key trends and differentiating features in the CSM marketspace.
      3. Evaluate major vendors in the CSM marketspace to discover the best-fitting provider.

      The objective at the end of the day is to have a single interface that the front-line staff interacts with. I think that is the holy grail when we look at CSM technology. The objective that everyone has in mind is we'd all like to get to one screen and one window. Ultimately, the end game really hasn't changed: How can we make it easy for the agents and how can we minimize their errors? How can we streamline the process so they can work?
      Colin Taylor, CEO, The Taylor Reach Group

      Customer service management tools form an integral part of your CXM technology portfolio

      Customer service management tools are an integral part of CXM

      Info-Tech’s methodology for selecting the right CSM platform

      1. Contextualize the CSM Landscape 2. Select the Right CSM Vendor
      Phase Steps
      1. Define CSM tools.
      2. Explore CSM trends.
      3. Understand if CSM tools are a good fit for your organization.
      1. Build the business case.
      2. Streamline requirements elicitation for CSM.
      3. Construct the request for proposal (RFP)/vendor evaluation workbook.
      Phase Outcomes
      1. Consensus on scope of CSM and key CSM capabilities
      2. Identify your customer service maturity and use for CSM tools
      1. CSM business case
      2. High-value use cases and requirements
      3. CSM RFP/vendor evaluation workbook

      Info-Tech Insight
      Need help constructing your RFP? Use Info-Tech’s CSM Platform RFP Template!

      Guided Implementation

      What does a typical GI on this topic look like?

      Phase 1 Phase 2

      Call #1: Discover if CSM tools are right for your organization. Understand what a CSM platform is and discover the “art of the possible.”

      Call #2: Identify right-sized vendors and build the business case to select a CSM platform.

      Call #3: Define your key CSM requirements.

      Call #4: Build procurement items, such as an RFP and demo script.

      Call #5: Evaluate vendors and perform final due diligence.

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

      The CSM selection process should be broken into segments:

      1. CSM vendor shortlisting with this buyer’s guide
      2. Structured approach to selection
      3. Contract review

      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 his 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 are used throughout all four options

      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

      Five advisory calls over a five week period to accelerate your selection process

      Book Your Selection Engagement

      Software Selection Workshops

      40 Hours of Advisory Assistance Delivered Online

      Select Better Software, Faster

      40 hours of expert analyst guidance

      Project & stakeholder management assistance

      Save money, align stakeholders, speed up the process, and make better decisions

      Better, faster results, guaranteed, $25,000 standard engagement fee

      Software selection workshops

      Book Your Workshop Engagement

      Customer Service Management (CSM) Software

      Phase 1: Contextualize the CSM Landscape

      Receive and resolve after-sales requests within a unified CSM platform

      MULTIPLE CHANNELS
      Customers may resolve their issues via a variety of channels, including voice, SMS, email, social media, and live webchat.
      KNOWLEDGE BASE
      Provide a knowledge base for FAQs that is both customer facing (via customer portal) and agent facing (for live resolutions).
      ANALYTICS
      Track customer satisfaction, agent performances, ticket resolutions, backlogs, traffic analysis, and other key performance indicators (KPIs).
      COLLABORATION
      Enable agents to escalate and collaborate within a unified platform (e.g. tagging colleagues to flag a relevant customer query).

      Info-Tech Insight
      After-sales customer service is critical for creating, maintaining, and growing customer relationships. Organizations that fail to provide adequate service will be poorly positioned for future customer service and sales efforts.

      Identify your differentiating CSM requirements that align to your use cases

      INTEGRATIONS
      Note what integrations are available for your contact center, CRM, or industry-specific solutions (e.g. inventory management) to get the most out of CSM.

      SENTIMENT ANALYSIS
      Reads, contextualizes, and categorizes tickets by sentiment (e.g. “positive”) before escalating to an appropriate agent.

      AUTO-RESPONSE EDITOR
      Built-in AI provides prewritten responses or auto-pulls the relevant knowledge article, assisting agents with speed to resolution.

      ATTRIBUTES-BASED ROUTING
      Learns over time how best to route tickets to appropriate agents based on skills, availability, or proximity of an agent (e.g. multilingual, local, or specialist agents).

      AUTOMATED WORKFLOWS
      CSM tool providers have varying usability for workflow building and enablement. Ensure your use cases align.

      TICKET PRIORITIZATION
      Adapts and prioritizes customer issues by service-level agreement (SLA), priority, and severity according to inputted KPIs.

      Good technology will not fix a bad process. I don't care how good the technology is. If the use case is wrong and the process is wrong, it's not going to work.
      Colin Taylor, CEO
      The Taylor Reach Group

      Leverage CSM tools to shift left toward predictive customer service

      Real-time Pre-event Post-event
      Channel example: Notifications via SMS or social media. Channel example: Notifications via SMS or social media. Channel example: Working with an agent or live chatbot. Channel example: Working with an agent or live chatbot.
      “Your car may need a check-up for faulty parts.” “Here is a local garage to fix your tire pressure.” “I see you have poor tire pressure. Here is a local garage.” “Thank you for your patience, how can we help?”
      Predictive Service
      The CSM recommends mitigation options to the customer before the issue occurs and before the customer knows they need it.
      Proactive Service
      The issue occurs but the CSM recommends mitigation options to the customer before the customer contacts the organization.
      Real-Time Service
      The organization offers real-time mitigation options while working with the customer to resolve the issue.
      Reactive Service
      The customer approaches the organization after the issue occurs, but the organization has no insight into the event.

      Selecting a CSM tool should form part of your broader CXM strategy

      Organizations should ask whether they need a standalone CSM solution or a CSM as part of a broader suite of CXM tools. The latter is especially relevant if your organization already invests in a CXM platform.

      Matrix of CMS tools as part of CXM strategy

      CSM tools are best-suited for organizations with high product and service complexity

      Customer Service Complexity

      Low complexity refers to primarily transactional inquiries. High complexity refers to service workflows for symptom analysis, problem identification, and solution delivery.

      Product Complexity

      High complexity refers to having a large number of brands and individual SKUs, technologically complex products, and products with many add-ons.

      A matrix showing that a standalone CSM tool is best where customer service complexity and product complexity are both high.

      Info-Tech Insight
      Use Info-Tech’s CSM Platform Opportunity Assessment Tool to discover your organization’s customer service maturity.

      Activity: Discover your customer service maturity

      30 minutes

      1. Complete the CSM Platform Opportunity Assessment Tool.
      2. Evaluate your result and document whether a CSM business case is warranted (or if a separate technology selection process is needed).
      Input Output
      • Understanding of the current state and how complex the organization’s product line and help desk support are
      • Ranking of the importance of each decision point
      • Assessment results that provide a high-level view of whether your organization’s product and customer service complexity warrant a standalone CSM tool
      Materials Participants
      • CSM Platform Opportunity Assessment Tool
      • Shared screen or projection
      • Customer support analyst(s)
      • Infrastructure and Operations lead(s)
      • Representative customer support staff
      • Product management analyst(s)

      Download the CSM Platform Opportunity Assessment Tool

      Finalize whether your organization is well positioned to leverage CSM tools

      Bypass Adopt
      Monochannel approach
      You do not participate in multichannel campaigns or your customer personas are typically limited to one or two channels (e.g. voice or SMS).
      Multichannel approach
      You are pursuing multifaceted, customer-specific campaigns across a multitude of channels.
      Small to mid-sized business with small CX team
      Do not buy what you do not need. Focus on the foundations of customer experience (CX) first before extending into a full-fledged CSM tool.
      Maturing CX department
      Customer service needs are extending into managing budgets, generating and segmenting leads, and measuring channel effectiveness.
      Limited product range
      CSM tools typically gain return on investment (ROI) if the organization has a complex product range and is looking to increase cross-sell opportunities across different customer personas.
      Multiple product lines
      Customer base and product lines are large enough to engage in opportunities for cross- and up-selling.

      Case Study

      AkzoNobel

      INDUSTRY
      Retail

      SOURCE
      Sprinklr (2021)

      Use CSM tools to unify the multichannel experience and reduce response time.

      Challenge Solution Results
      AzkoNobel is a leading global paints and coatings company. AzkoNobel had 60+ fragmented customer service accounts on social media for multiple brands. There was little consistency in customer experience and agent responses. Moreover, the customer journey was not being tracked, resulting in lost opportunities for cross-selling across brands. The result: slow response times (up to one week) and unsatisfied customers, leaving the AzkoNobel brand in a vulnerable state.

      AkzoNobel leveraged Sprinklr, a customer experience software provider, to unify six social channels, 19 accounts, and six brands. Sprinklr aligned governance across social media channels with AzkoNobel’s strategic business goals, emphasizing the need for process, increasing revenue, and streamlining customer service.

      AzkoNobel was able to use keywords from customers’ inbound messaging to put an escalation process in place.

      Since bringing on Sprinklr in 2015-2016, unifying customer service channels under one multichannel platform resulted in:

      • 172% increase in customer engagement.
      • 133% increase in post comments.
      • 80% reduced response times.
      • 47% of inquiries answered within five minutes.
      • $18,500 added revenues via social media responses.

      How it got here: The birth of CSM tools

      CSM developed alongside the telephone and call center, rather than customer relationship management platforms.

      1920s 1950s 1967-1973 1980-1990s 2000-2010s
      The introduction of lines of credit and growth of household appliance innovations meant households were buying products at an unprecedented rate. Department stores would set up customer service sections to assist with live fixes or returns. Following the Great Depression and World War II, process, efficiency, and computational technology became defining features of customer service. These features were played out in call centers as automatic call distribution (ACD) technology began to scale. With the development of private automatic branch exchange (PABX), AT&T introduced the toll-free telephone number. Companies began training staff and departments for customer service and building loyalty. With the development of interactive voice response (IVR) in 1973, call centers became increasingly more efficient at routing. Analog technology shifted to digital and the term “contact center” was coined. These centers began being outsourced internationally. With the advent of the internet, CSM technology (in the early guise of a “help desk”) became equipped with computer telephony integration (CTI). Software as a service (SaaS) and CRM maturation strengthened the retention and organization of customer data. Social media also enhanced consumer power as companies rushed to prevent online embarrassment. This prompted investment in multichannel customer service.

      Where it’s going: The future of CSM tools lies in predictive analytics

      The capabilities below are available today but will mature over the next few years. Use the roadmap as a guide for your year of implementation.

      2023
      Go mobile first
      85% of customers believe a company’s mobile website should be just as good as its desktop website. Enabling user-friendly mobile websites provides an effective channel to keep inbound calls down.

      2024
      Shift from multichannel to omnichannel
      Integrating CSM tools with your broader CXM suite enables customer data to seamlessly travel between channels for an omnichannel experience.

      2025
      Enable predictive service
      CSM tools integrate with Internet of Things (IoT) systems to provide automated notifications that alert staff of issues and mitigate issues with customers before the issue even occurs.

      2026
      Leverage predictive analytics for ML use cases
      Use customers’ historic data and preferences to perform better automated customer service over time (e.g. providing personalized resolutions based on previous customer engagements).

      Context and scenario play a huge role in measuring good customer service. Ensure your KPIs accurately reflect the incentives you want to give your customer support staff for delivering appropriate customer service.
      David Thomas, Customer Service Specialist
      Freedom Mobile
      (Reve Chat, 2022)

      Key trends in CSM technology

      As predictive analytics matures, organizations are making use of CSM tools’ ability to enhance personalization, improve their social media response times, and enable self-service.

      BIOMETRICS
      65% of customers say they would accept voice recognition to authorize their identity when calling a customer support line (GetApp, 2021).

      PERSONALIZATION
      51% of marketers, advocating for personalization across multiple touchpoints saw 300% ROI (KoMarketing, 2020).

      SOCIAL MEDIA
      29% of customers aged 18 to 39 prefer online chat communication before and after purchase (RingCentral, 2020).

      SELF-SERVICE
      92% of customers say they would use a knowledge base for self-service support if it was available (Vanilla, 2020).

      Customer Service Management (CSM) Software

      Phase 2: Select the Right CSM Vendor

      Conduct a business impact assessment to document the case for CSM tool selection

      Business Opportunity
      Determine high-level understanding of the need that must be addressed, along with the project goals and affiliated key metrics. Establish KPIs to measure project success.

      System Diagram
      Determine the impact on the application portfolio and where integration is necessary.

      Risks
      Identify potential blockers and risk factors that will impede selection.

      High-Level Requirements
      Consider the business functions and processes affected.

      People Impact
      Confirm who will be affected by the output of the technology selection.

      Overall Business Case
      Calculate the ROI and the financial implications of the application selection. Highlight the overarching value.

      Activity: Build the business case

      2 hours

      1. Access the Business Impact Assessment within the Software Selection Workbook (linked below). Store the assessment in a shared folder (such as in SharePoint, OneDrive, or Google Drive).
      2. Set aside two hours (does not need to be all at once) to ensure the selection team aligns with the unifying rationale for selection.
      3. Complete the six steps to arrive at a high-level business case. This case can then be shared and communicated with interested parties (e.g. impacted stakeholders).
      InputOutput
      • Drivers for the business opportunity to adopt CSM tools
      • Understanding of key stakeholders
      • Overview of application portfolio
      • Budgetary information
      • Business Impact Assessment, which captures your high-level business case
      MaterialsParticipants
      • Software Selection Workbook
      • Screen sharing or projector
      • Whiteboard and drawing materials
      • Customer support analyst(s)
      • Infrastructure and Operations lead(s)
      • Representative customer support staff
      • Product management analyst(s)

      Download the Software Selection Workbook

      Elicit and prioritize granular requirements for your CSM platform

      Understanding business needs through requirements gathering is key to defining everything about what is being purchased, yet it is an area where people often make critical mistakes.

      Signs of poorly scoped requirements Best practices
      • Requirements focus on how the solution should work instead of what it must accomplish.
      • Multiple levels of detail exist within the requirements, which are inconsistent and confusing.
      • Requirements drill all the way down into system-level detail.
      • Language is technical and dense, leaving some stakeholder groups confused on what they are actually looking for in a solution.
      • Requirements are copied from a market analysis of the art of the possible, abstract from organization’s own customer persona analysis.
      • Get a clear understanding of what the system needs to do and what it is expected to produce. Build customer personas to assist with identifying high-value use cases.
      • Test against the principle of MECE – requirements should be “mutually exclusive and collectively exhaustive.”
      • Use language that is consistent with that of the market and focus on key differentiators – not table stakes.
      • Include the appropriate level of detail, which should be suitable for procurement and sufficient for differentiating vendors.

      Info-Tech Insight
      Review Info-Tech’s requirements gathering methodology to improve your requirements gathering process.

      Choose your route: RFP or otherwise?

      As you gather requirements, decide which procurement route best suits your context.

      RFI (Request for Information) RFQ (Request for Quotation) RFP (Request for Proposal)
      Purpose and Usage

      Gather information about products/services when you know little about what’s available.

      Often followed by an RFP.

      Solicit pricing and delivery information for products/services with clearly defined requirements.

      Best for standard or commodity products/services.

      Solicit formal proposals from vendors to conduct an evaluation and selection process.

      Formal and fair process; identical for each participating vendor.

      Level of Intent

      Fact-finding there is no commitment to engage the vendor.

      Vendors are often reluctant to provide quotes.

      Committed to procure a specific product/service at the lowest price.

      Intent to buy the products/services in the RFP.

      Business case/approval to spend is already obtained.

      Level of Detail High-level requirements and business goals.

      Detailed specifications of what products/services are needed.

      Detailed contract and delivery terms.

      Detailed business requirements and objectives.

      Standard questions and contract term requests for all vendors.

      Response

      Generalized response with high-level product/services.

      Sometimes standard pricing quote.

      Price quote and confirmation of ability to fulfill desired terms.

      Detailed solution description, delivery approach, customized price quote, and additional requested information.

      Product demo and/or hands-on trial.

      Info-Tech Insight
      If you are in a hurry, consider instead issuing Info-Tech’s Vendor Evaluation Workbook. This workbook speeds up the typical procurement process by adding RFP-like requirements (such as operational and technical requirements) while driving the procurement process via emphasis on high-value use cases.

      Download the Vendor Evaluation Workbook

      Activity: Document requirements

      2 hours

      1. Review each tab of Info-Tech’s CSM Platform RFP Scoring Tool to generate use cases and ideas for your requirements building.
      2. Modify and include additional features you may need, using Info-Tech’s CSM Platform RFP Template to assist with structure (if pursuing an RFP process) or Vendor Evaluation Workbook (if an RFP process is not needed). Pay attention to any nonfunctional requirements (such as security or integrations), alongside future trends of CSM. Vendors must be able to scale with your organization’s growth.
      3. You can use the CSM Platform RFP Scoring Tool again when assessing vendor responses.
      Input Output
      • Key use cases that capture your most important customer service support processes
      • Discussion of CSM future trends and differentiating features
      • Confirmation on organization’s significant nonfunctional requirements (e.g. security or integrations)
      • Either a Requirements Workbook to go straight to shortlisted vendor(s) or an RFP document to solicit a broader market response
      Materials Participants
      • CSM Platform RFP Scoring Tool
      • CSM Platform RFP Template
      • Vendor Evaluation Workbook
      • Customer support analyst(s)
      • Infrastructure and Operations lead(s)
      • Other major stakeholders (for requirements elicitation)

      Download the CSM Platform RFP Scoring Tool

      Download the CSM Platform RFP Template

      Once vendor responses are in, turn product demos into investigative interviews

      Avoid vendor glitz and glamour shows by ensuring vendors are concretely applying their solution to your high-value use cases.

      1 Minimize the number of vendors to four to keep up the pace of the selection process.
      2 Provide a demo script that captures your high-value use cases and differentiating requirements.
      3 Ensure demos are booked close together and the selection committee attends all demos.

      Conduct a day of rapid-fire vendor demos

      Zoom in on high-value use cases and answers to targeted questions

      Rapid-fire vendor investigative interview

      Invite vendors to come onsite (or join you via videoconference) to demonstrate the product and 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.

      Give each vendor 90 to 120 minutes to give a rapid-fire presentation. We suggest the following structure:

      • 30 minutes: Company introduction and vision
      • 60 minutes: Walkthrough of two or three high-value demo scenarios
      • 30 minutes: Targeted Q&A from the business stakeholders and procurement team

      To ensure a consistent evaluation, vendors should be asked analogous questions and answers should be tabulated.

      How to challenge the vendors in the investigative interview

      • Change the visualization/presentation.
      • Change the underlying data.
      • Add additional data sets to the artifacts.
      • Test voice quality (if the vendor offers a native telephony channel).
      • Test collaboration capabilities.

      To kick-start scripting your demo scenarios, leverage our CSM Platform Vendor Demo Script Template.

      A vendor scoring model provides a clear anchor point for your evaluation of CRM vendors based on a variety of inputs

      A vendor scoring model is a systematic method for effectively assessing competing vendors. A weighted-average scoring model is an approach that strikes a strong balance between rigor and evaluation speed.

      How do I build a scoring model? What are some of the best practices?
      • Start by shortlisting the key criteria you will use to evaluate your vendors. Functional capabilities should always be a critical category, but you’ll also want to look at criteria such as affordability, architectural fit, and vendor viability.
      • Depending on the complexity of the project, you may break down some criteria into subcategories to assist with evaluation (for example, breaking down functional capabilities into constituent use cases so you can score each one).
      • Once you’ve developed the key criteria for your project, the next step is weighting each criterion. Your weightings should reflect the priorities for the project at hand. For example, some projects may put more emphasis on affordability, others on vendor partnership.
      • Using the information collected in the subsequent phases of this blueprint, score each criterion from 1 to 100, then multiply by the weighting factor. Add up the weighted scores to arrive at the aggregate evaluation score for each vendor on your shortlist.
      • While the criteria for each project may vary, it’s helpful to have an inventory of repeatable criteria that can be used across application selection projects. The next slide contains an example that you can add to or subtract from.
      • Don’t go overboard on the number of criteria: five to ten weighted criteria should be the norm for most projects. The more criteria (and subcriteria) you must score against, the longer it will take to conduct your evaluation. Always remember, link the level of rigor to the size and complexity of your project! It’s possible to create a convoluted scoring model that takes significant time to fill out but yields little additional value.
      • Creation of the scoring model should be a consensus-driven activity among IT, procurement, and the key business stakeholders – it should not be built in isolation. Everyone should agree on the fundamental criteria and weights that are employed.
      • Consider using not just the outputs of investigative interviews and RFP responses to score vendors, but also third-party review services like SoftwareReviews.

      Info-Tech Insight
      Even the best scoring model will still involve some “art” rather than science. Scoring categories such as vendor viability always entail a degree of subjective interpretation.

      Define how you will score vendor responses and demos

      Your key CSM criteria should be informed by the following goals, use cases, and requirements.

      Criteria Description
      Functional Capabilities How well does the vendor align with the top-priority functional requirements identified in your accelerated needs assessment? What is the vendor’s functional breadth and depth?
      Affordability How affordable is this vendor? Consider a three-to-five-year total cost of ownership (TCO) that encompasses not just licensing costs but also implementation, integration, training, and ongoing support costs.
      Architectural Fit How well does this vendor align with your direction from an enterprise architecture perspective? How interoperable is the solution with existing applications in your technology stack? Does the solution meet your deployment model preferences?
      Extensibility How easy is it to augment the base solution with native or third-party add-ons as your business needs may evolve?
      Scalability How easy is it to expand the solution to support increased user, data, and/or customer volumes? Does the solution have any capacity constraints?
      Vendor Viability How viable is this vendor? Are they an established player with a proven track record or a new and untested entrant to the market? What is the financial health of the vendor? How committed are they to the particular solution category?
      Vendor Vision Does the vendor have a cogent and realistic product roadmap? Are they making sensible investments that align with your organization’s internal direction?
      Emotional Footprint How well does the vendor’s organizational culture and team dynamics align to yours?
      Third-Party Assessments and/or References How well-received is the vendor by unbiased third-party sources like SoftwareReviews? For larger projects, how well does the vendor perform in reference checks (and how closely do those references mirror your own situation)?

      Leverage Info-Tech’s Contract Review Services to level the playing field with shortlisted vendors

      You may be faced with multiple products, services, master service agreements, licensing models, service agreements, and more.

      Use Info-Tech’s Contract Review Services to gain insights on your agreements.

      Consider the aspects of a contract review:

      1. Are all key terms included?
      2. Are they applicable to your business?
      3. Can you trust that results will be delivered?
      4. What questions should you be asking from an IT perspective?

      Validate that a contract meets IT’s and the business’ needs by looking beyond the legal terminology. Use a practical set of questions, rules, and guidance to improve your value for dollar spent.

      Book Contract Review Service

      Download Master Contract Review and Negotiation for Software Agreements

      Customer Service Management (CSM) Software

      Vendor Analysis

      Evaluate software category leaders through vendor rankings and awards

      SoftwareReviews

      The Data Quadrant is a thorough evaluation and ranking of all software in an individual category to compare platforms across multiple dimensions.

      Vendors are ranked by their Composite Score, based on individual feature evaluations, user satisfaction rankings, vendor capability comparisons, and likeliness to recommend the platform.

      The Emotional Footprint is a powerful indicator of overall user sentiment toward the relationship with the vendor, capturing data across five dimensions.

      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.

      Speak with category experts to dive deeper into the vendor landscape

      SoftwareReviews

      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.

      SoftwareReviews 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. Combined with the insight of our expert analysts, our members receive unparalleled support in 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.

      Microsoft Dynamics 365

      Est. 2003 | WA, USA | MSFT:NASDAQ

      Bio

      To accelerate your digital transformation, you need a new type of business application. One that breaks down the silos between CRM and ERP, that’s powered by data and intelligence, and helps capture new business opportunities. That’s Microsoft Dynamics 365.

      Offices

      Microsoft is located all over the world. For a full list, see Microsoft Worldwide Sites.

      representative Customers

      Stated Industry Specializations

      • Covers an extremely wide range of industries, such as finance, education, government, healthcare, manufacturing, and retail.

      Software review for Microsoft

      SoftwareReviews’ CSM Enterprise Vendor Ranking
      (out of 7)

      Likeliness to Recommend

      • 7th (81%)

      Plan to Renew

      • 6th (93%)

      Satisfaction That Cost Is Fair Relative to Value

      • 2nd (81%)

      Strengths

      • Product Strategy and Rate of Improvement (1st)
      • Ease of Customization (1st)
      • Breadth of Features (2nd)

      Areas to Improve

      • Availability and Quality of Training (5th)
      • Ease of Implementation (7th)
      • Usability and Intuitiveness (7th

      Microsoft Dynamics 365

      History

      Founded 2003 (as Microsoft Dynamics CRM)
      2005 Second version branded Dynamics 3.0.
      2009 Dynamics CRM 4.0 (Titan) passes 1 million user mark.
      2015 Announces availability of CRM Cloud design for FedRAMP compliance.
      2016 Dynamics 365 released as successor to Dynamics CRM.
      2016 Microsoft’s acquisition of LinkedIn provides line of data to 500 million users.
      2021 First-party voice channel added to Dynamics 365.
      2022 Announces Digital Contact Center Platform powered with Nuance AI, MS Teams, and Dynamics 365.

      Microsoft is rapidly innovating in the customer experience technology marketspace. Alongside Dynamics 365’s omnichannel offering, Microsoft is building out its own native contact center platform. This will provide new opportunities for centralization without multivendor management between Dynamics 365, Microsoft Teams, and an additional third-party telephony or contact-center-as-a-service (CCaaS) vendor. SoftwareReviews reports suggest that Microsoft is a market leader in the area of product innovation for CSM, and this area of voice channel capability is where I see most industry interest.

      Of course, Dynamics 365 is not a platform to get only for CSM functionality. Users will typically be a strong Microsoft shop already (using Dynamics 365 for customer relationship management) and are looking for native CSM features to enhance customer service workflow management and self-service.
      Thomas Randall
      Research Director, Info-Tech Research Group

      Info-Tech Insight
      Pricing for Microsoft Dynamics 365 is often contextualized to an organization’s needs. However, this can create complicated licensing structures. Two Info-Tech resources to assist are:

      *This service may be used for other enterprise CSM providers too, including Salesforce, ServiceNow, SAP, and Oracle.
      Contact your account manager to review your access to this service.

      Freshworks

      Est. 2010 | CA, USA | FRSH:NASDAQ

      Bio

      Freshworks' cloud-based customer support software, Freshdesk, makes customer happiness refreshingly easy. With powerful features, an easy-to-use interface, and a freemium pricing model, Freshdesk enables companies of all sizes to provide a seamless multichannel support experience across email, phone, web, chat, forums, social media, and mobile apps. Freshdesk’s capabilities include robust ticketing, SLA management, smart automations, intelligent reporting, and game mechanics to motivate agents.

      Offices

      • Americas: US
      • Asia-Pacific (APAC): Australia, India, Singapore
      • Europe, Middle East, and Africa (EMEA): France, Germany, Netherlands, UK

      Freshworks Representative Customers

      Stated Industry Specializations

      • Automotive
      • Education
      • Energy
      • Finance
      • Healthcare
      • Nonprofit
      • Professional Services
      • Publishing
      • Real Estate
      • Retail
      • Travel

      Software Review of Freshworks

      SoftwareReviews’ CSM Enterprise Vendor Ranking
      (out of 7)

      Likeliness to Recommend

      • 3rd (83%)

      Plan to Renew

      • 4th (94%)

      Satisfaction That Cost Is Fair Relative to Value

      • 3rd (80%)

      Strengths

      • Breadth of Features (1st)
      • Usability and Intuitiveness (1st)
      • Ease of Implementation (2nd)

      Areas to Improve

      • Ease of IT Administration (3rd)
      • Vendor Support (4th)
      • Product Strategy and Rate of Improvement (4th)

      Freshworks

      History

      Founded 2010
      2011 Freshdesk forms a core component of product line.
      2014 Raises significant capital in Series D round: $31M.
      2016 Acquires Airwoot, enabling real-time customer support on social media.
      2019 Raises $150M in Series H funding round.
      2019 Acquires Natero, which predicts, analyzes, and drives customer behavior.
      2021 Surpasses $300M in annual recurring revenues.
      2021 Freshworks posts its IPO listing.

      Freshworks stepped into the SaaS customer support marketspace in 2010 to attract dissatisfied Zendesk eSupport customers, following Zendesk’s large price increases that year (of 300%). After performing well during the pandemic, Freshworks has reinforced its global positioning in the CSM tool marketspace; SoftwareReviews data suggests Freshworks performs very well against its competitors for breadth and intuitiveness of its features.

      Freshworks receives strong recommendations from Info-Tech’s members, boasting a broad product selection that enables opportunities for scaling and receiving a high rate of value return. Of note are Freshworks’ internal customer management solution and its native contact center offering, limiting multivendor management typically required for integrating separate IT service management (ITSM) and CCaaS solutions.
      Thomas Randall
      Research Director, Info-Tech Research Group

      Free Growth Pro Enterprise
      • $0 up to 10 agents
      • Knowledge base
      • Ticket routing
      • Out-of-box analytics
      • $15 agent/month
      • Collision detection
      • Integrations
      • Automated follow-ups
      • $49 agent/month
      • Multiple product lines
      • Personalization
      • CSAT surveys
      • Customer journey
      • $79 agent/month
      • Assist bot and email bot
      • Skill-based routing

      *Pricing correct as of November 2022. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.

      Help Scout

      Est. 2006 | MA, USA | HUBS:NYSE

      Bio
      Help Scout is designed with your customers in mind. Provide email and live chat with a personal touch and deliver help content right where your customers need it, all in one place, all for one low price. The customer experience is simple and training staff is painless, but Help Scout still has all the powerful features you need to provide great support at scale. With best-in-class reporting, an integrated knowledge base, 50+ integrations, and a robust API, Help Scout lets your team focus on what really matters: your customers.

      Offices

      • Americas: Canada, Colombia, US
      • APAC: Australia, Japan, Singapore
      • EMEA: Belgium, France, Ireland, Germany, UK

      Questions for support transition

      Stated Industry Specializations

      • eCommerce
      • Education
      • Finance
      • Healthcare
      • Logistics
      • Manufacturing
      • Media
      • Professional Services
      • Property Management
      • Software

      Software Review of Help Scout

      SoftwareReviews’ CSM Enterprise Vendor Ranking
      (out of 7)

      Likeliness to Recommend

      • 4th (82%)

      Plan to Renew

      • 7th (87%)

      Satisfaction That Cost Is Fair Relative to Value

      • 7th (71%)

      Strengths

      • Business Value Created (1st)
      • Ease of Data Integration (1st)
      • Breadth of Features (3rd)

      Areas to Improve

      • Ease of IT Administration (5th)
      • Product Strategy and Rate of Improvement (5th)
      • Quality of Features (6th)

      Help Scout

      History

      Founded 2011
      2015 Raised $6M in Series A funding.
      2015 Rebrands from Brightwurks to Help Scout.
      2015 Named by Appstorm as one of six CSM tools to delight Mac users.
      2016 iOS app released.
      2017 Android app released.
      2020 All employees instructed to work remotely.
      2021 Raises $15M in Series B funding.

      Help Scout provides a simplified, standalone CSM tool that operates like a shared email inbox. Best suited for mid-sized organizations, customers can expect live chat, in-app messaging, and knowledge-base functionality. A particular strength is Help Scout’s integration capabilities, with a wide range of CRM, eCommerce, marketing, and communication APIs available. This strength is also reflected in the data: SoftwareReviews lists Help Scout as first in its CSM category for ease of data integrations.

      Customers who are expecting a broader range of channels (including voice, video cobrowsing, and so on) will not find good return on investment with Help Scout. However, for mid-sized organizations looking to begin maturing their customer service management, Help Scout provides a strong foundation – especially for enhancing in-house collaboration between support staff.
      Thomas Randall
      Research Director, Info-Tech Research Group

      Standard Plus Pro
      • $20 user/month
      • Live chat
      • Up to 25 users
      • 50+ integrations
      • 2 mailboxes
      • $40 user/month
      • Advanced permissions
      • Group users
      • 5 mailboxes
      • $65 user/month
      • HIPAA compliance
      • Onboarding service
      • Dedicated account manager

      *Pricing correct as of November 2022. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.

      HubSpot

      Est. 2006 | MA, USA | HUBS:NYSE

      Bio
      HubSpot’s Service Hub brings all your customer service data and channels together in one place and helps scale your support through automation and self-service. The result? More time for proactive service that delights, retains, and grows your customer base. HubSpot provides software and support to help businesses grow better. The overall platform includes marketing, sales, service, and website management products that start free and scale to meet our customers’ needs at any stage of growth.

      Offices

      • Americas: Canada, Colombia, US
      • APAC: Australia, Japan, Singapore
      • EMEA: Belgium, France, Ireland, Germany, UK

      HubSpot Representative Customers

      Stated Industry Specializations

      • Covers an extremely wide range of industries, such as finance, education, healthcare, manufacturing, and retail.

      Software Review for HubSpot

      SoftwareReviews’ CSM Enterprise Vendor Ranking
      (out of 7)

      Likeliness to Recommend

      • 1st (88%)

      Plan to Renew

      • 1st (98%)

      Satisfaction That Cost Is Fair Relative to Value

      • 5th (78%)

      Strengths:

      • Vendor Support (1st)
      • Availability and Quality of Training (1st)
      • Ease of IT Administration (1st)

      Areas to Improve:

      • Ease of Data Integration (5th)
      • Ease of Customization (5th)
      • Breadth of Features (7th)

      HubSpot

      History

      Founded 2006
      2013 Opens first international office in Ireland.
      2014 First IPO listing on NYSE, raising $140M.
      2015 Milestone for acquiring 15,000 customers
      2017 Acquires Kemvi for AI and ML support for sales teams.
      2019 Acquires PieSync for customer data synchronization.
      2021 Yamini Rangan is announced as new CEO.
      2021 Records $1B in revenues.

      HubSpot is a competitive player in the enterprise sales and marketing technology market. Offering an all-in-one platform, HubSpot allows users to leverage its CRM, marketing solutions, content management tool, and CSM tool. Across knowledge management, contact center integration, and customer self-service, SoftwareReviews data pits HubSpot as performing better than its enterprise competitors.

      While customers can leverage HubSpot’s CSM tool independently, watch out for scope creep. HubSpot’s other offerings are tightly integrated and module extensions could quickly add up in price. HubSpot may not be affordable for most regional, mid-sized organizations, and a poor ROI may be expected. For instance, the Pro plan is required to get a knowledge base, which is typically a standard CSM feature – yet the same plan also comes with multicurrency support, which could remain unleveraged.
      Thomas Randall
      Research Director, Info-Tech Research Group

      Free Starter Pro Enterprise
      • $0 month
      • Ticketing
      • Live chat
      • 200 notifications per month
      • $45 month
      • 5,000 email templates
      • White label
      • 500 calling minutes
      • $450 month
      • 30 currencies
      • Knowledge base
      • Up to 300 workflows
      • $1,200 month
      • Conversation intelligence
      • SSO

      *Pricing correct as of November 2022. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.

      Salesforce

      Est. 1999 | CA, USA | CRM:NYSE

      Bio

      Service Cloud customer service software gives you faster, smarter customer support. Salesforce provides customer relationship management software and applications focused on sales, customer service, marketing automation, analytics, and application development.

      Offices

      • Americas: US
      • APAC: Australia, India, Singapore
      • EMEA: France, Germany, Netherlands, UK

      Salesforce Representative Customers

      Stated Industry Specializations

      • Covers an extremely wide range of industries, such as finance, education, government, healthcare, manufacturing, and retail.

      Software Review for Salesforce

      SoftwareReviews’ CSM Enterprise Vendor Ranking
      (out of 7)

      Likeliness to Recommend

      • 6th (81%)

      Plan to Renew

      • 2nd (96%)

      Satisfaction That Cost Is Fair Relative to Value

      • 4th (79%)

      Strengths:

      • Usability and Intuitiveness (5th)
      • Breadth of Features (5th)
      • Ease of Implementation (6th)

      Areas to Improve:

      • Ease of IT Administration (7th)
      • Availability and Quality of Training (7th)
      • Ease of Customization (7th)

      Salesforce

      History

      Founded 1999
      2000 Salesforce launches its cloud-based products.
      2003 The first Dreamforce (a leading CX conference) happens.
      2005 Salesforce unveils AppExchange.
      2013 Salesforce acquires ExactTarget and expands Marketing Cloud offering.
      2016 Salesforce acquires Demandware, launches Commerce Cloud.
      2019 Salesforce acquires Tableau to expand business intelligence capabilities.
      2021 Salesforce buys major collaboration vendor Slack.

      Salesforce was an early disruptor in CRM marketspace, placing a strong emphasis on a SaaS delivery model and end-user experience. This allowed Salesforce to rapidly gain market share at the expense of complacent enterprise application vendors. A series of savvy acquisitions over the years has allowed Salesforce to augment its core Sales and Service Clouds with a wide variety of other solutions, from ecommerce to marketing automation – and recently Slack for internal collaboration.

      Salesforce Service Cloud Voice is now available to take advantage of integrating telephony and voice channels into your CRM. This service is still maturing, though, with Salesforce selecting Amazon Connect as its preferred integrator. However, Connect is not necessarily plug-and-play – it is a communications platform as a service, requiring you to build your own contact center solution. This is either a fantastic opportunity for creativity or a time suck of already tied-up resources.
      Thomas Randall
      Research Director, Info-Tech Research Group

      Service Cloud Essentials Service Cloud Professional Service Cloud Enterprise Service Cloud Unlimited
      • $25 user/month
      • Small businesses after basic functionality
      • $75 user/month
      • Mid-market target
      • $150 user/month
      • Enterprise target
      • Web Services API
      • $300 user/month
      • Strong upmarket feature additions

      *Pricing correct as of November 2022. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.

      Zendesk

      Est. 2007 | CA, USA | ZEN:NYSE

      Bio

      Zendesk streamlines your support with time-saving tools like ticket views, triggers, and automations. This helps you get straight to what matters most – better customer service and more meaningful conversations. Today, Zendesk is the champion of great service everywhere for everyone and powers billions of conversations, connecting more than 100,000 brands with hundreds of millions of customers over telephony, chat, email, messaging, social channels, communities, review sites, and help centers.

      Offices

      • Americas: Brazil, Canada, US
      • APAC: Australia, China, India, Indonesia, Japan, Korea, Malaysia, Philippines, Singapore, Thailand, Vietnam
      • EMEA: Denmark, France, Germany, Ireland, Italy, Netherlands, Poland, Spain, Sweden, UK

      Zendesk Representative Customers

      Stated Industry Specializations

      • Education
      • Finance
      • Government
      • Healthcare
      • Manufacturing
      • Media
      • Retail
      • Software
      • Telecommunications

      Software Review for Zendesk

      SoftwareReviews’ CSM Enterprise Vendor Ranking
      (out of 7)

      Likeliness to Recommend

      • 5th (81%)

      Plan to Renew

      • 5th (94%)

      Satisfaction That Cost Is Fair Relative to Value

      • 6th (77%)

      Strengths

      • Ease of IT Administration (2nd)
      • Ease of Implementation (5th)
      • Quality of Features (5th)

      Areas to Improve

      • Business Value Created (7th)
      • Vendor Support (7th)
      • Product Strategy and Rate of Improvement (7th)

      Zendesk

      History

      Founded 2007
      2008 Initial seed funding of $500,000.
      2009 Receives $6M through Series B Funding.
      2009 Relocates from Copenhagen to San Francisco.
      2014 Acquires Zopin Technologies.
      2014 Listed on NYSE.
      2015 Acquires We Are Cloud SAS.
      2018 Launches Zendesk Sell.

      Zendesk is a global player in the CSM tool marketspace and works with enterprises across a wide variety of industries. Unlike some other CSM players, Zendesk provides more service channels at its lowest licensing offer, affording organizations a quicker expansion in customer service delivery without making enterprise-grade investments. However, the price of the lowest licensing offer starts much higher than Zendesk’s competitors; organizations will need to consider if the cost to try Zendesk over an annual contract is within budget.

      Unfortunately, SoftwareReviews data suggests that Zendesk may not always provide that immediate value, especially to mid-sized organizations. Zendesk is rated lower for vendor support and business value created. However, Zendesk provides strong functionality that competes with other enterprise players, and mid-sized organizations are continually impressed with Zendesk’s automation workflows.
      Thomas Randall
      Research Director, Info-Tech Research Group

      *Pricing correct as of November 2022. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.

      Team Growth Pro
      • $49 user/month
      • Ticketing
      • Email, voice, SMS, and live chat channels
      • $79 user/month
      • AI-powered knowledge management
      • Self-service portal
      • $99 user/month
      • HIPAA compliance
      • Customizable dashboards

      LiveChat

      Est. 2002 | Poland | WSE:LVC

      Bio

      Manage all emails from customers in one app and save time on customer support. LiveChat is a real-time live-chat software tool for ecommerce sales and support that is helping ecommerce companies create a new sales channel. It serves more than 30,000 businesses in over 150 countries, including large brands like Adobe, Asus, LG, Acer, Better Business Bureau, and Air Asia and startups like SproutSocial, Animoto, and HasOffers.

      Offices

      • Americas: US
      • EMEA: Poland

      LiveChat Representative Customers

      Stated Industry Specializations

      • eCommerce
      • Education
      • Finance
      • Software and IT

      Software Review for LiveChat

      SoftwareReviews’ CSM Midmarket Vendor Ranking
      (out of 8)

      Likeliness to Recommend

      • 1st (93%)

      Plan to Renew

      • 4th (92%)

      Satisfaction That Cost Is Fair Relative to Value

      • 5th (83%)

      Strengths

      • Product Strategy and Rate of Improvement (1st)
      • Usability and Intuitiveness (1st)
      • Breadth of Features (1st)

      Areas to Improve

      • Ease of Implementation (5th)
      • Ease of IT Administration (5th)
      • Ease of Customization (7th)

      LiveChat

      History

      Founded 2002
      2006 50% of company stock bought by Capital Partners.
      2008 Capital Partners sells entire stake to Naspers.
      2011 LiveChat buys back majority of stakeholder shares.
      2013 Listed by Red Herring in group of most innovative companies across Europe.
      2014 Listed on Warsaw Stock Exchange.
      2019 HelpDesk is launched.
      2020 Offered services for free to organizations helping mitigate the pandemic.

      LiveChat’s HelpDesk solution for CSM is a relatively recent solution (2019) that is proving very popular for small to mid-sized businesses (SMBs) – especially across Western Europe. SoftwareReviews’ data shows that HelpDesk is well-rated for breadth of features, usability and intuitiveness, and rate of improvement. Indeed, LiveChat has won and been shortlisted for several awards over the past decade for customer feedback, innovation, and fast growth to IPO.

      When shortlisting LiveChat’s HelpDesk, SMBs should be careful of scope creep. LiveChat offers a range of other solutions that are intended to work together. The LiveChat self-titled product is designed to integrate with HelpDesk to provide ticketing, email management, and chat management. Moreover, LiveChat’s AI-based ChatBot (for automated webchat) comes with additional cost (starting at $52 team/month).
      Thomas Randall
      Research Director, Info-Tech Research Group

      Team Plan Enterprise
      • $29 user/month.
      • Customized canned responses
      • Real-time reporting
      • Request quote
      • White labelling
      • Product training
      • Account manager

      *Pricing correct as of November 2022. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.

      ManageEngine

      Est. 1996 | India | Privately Owned

      Bio

      SupportCenter Plus is a web-based customer support software that lets organizations effectively manage customer tickets, their account and contact information, and their service contracts, and in the process provide a superior customer experience. ManageEngine is a division of Zoho.

      Offices

      • Americas: Brazil, Colombia, Mexico, US
      • APAC: Australia, China, India, Japan, Singapore
      • EMEA: Netherlands, Saudi Arabia, South Africa, UAE, UK

      ManageEngine Representative Customers

      Stated Industry Specializations

      • None stated but representative customers cover manufacturing, R&D, real estate, and transportation.

      Software Review for ManageEngine

      SoftwareReviews’ CSM Midmarket Vendor Ranking
      (out of 8)

      Likeliness to Recommend

      • 6th (85%)

      Plan to Renew

      • 5th (91%)

      Satisfaction That Cost Is Fair Relative to Value

      • 6th (83%)

      Strengths

      • Ease of Customization (1st)
      • Ease of Implementation (2nd)
      • Ease of IT Administration (2nd)

      Areas to Improve

      • Quality of Features (4th)
      • Usability and Intuitiveness (6th)
      • Availability and Quality of Training (8th)

      ManageEngine

      History

      Founded 1996
      2002 Branches from Zoho to become division focused on IT management.
      2004 Becomes an authorized MySQL Partner.
      2009 Begins shift of offerings into the cloud.
      2010 Tops 35,000 customers.
      2011 Integration with Zoho Assist.
      2015 Integration with Zoho Reports.

      ManageEngine, as a division of Zoho, has its strengths in IT operations management (ITOM). SupportCenter thus scores well in our SoftwareReviews data for ease of customization, implementation, and administration. As ManageEngine is a frequently discussed low-cost vendor in the ITOM market, customers often get good scalability across IT, sales, and marketing teams. Although SupportCenter is aimed at the midmarket and is low cost, organizations have the benefit of ManageEngine’s global presence and backing by Zoho for viability.

      However, because ManageEngine’s focus is ITOM, the breadth and quality of features for SupportCenter are not rated as well compared to its competitors. These features may be “good enough,” but usability and intuitiveness is not scored high. Organizations thinking about SupportCenter are recommended to identify their high-value use cases and perform user acceptance testing before adopting.
      Thomas Randall
      Research Director, Info-Tech Research Group

      Standard* Pro* Enterprise*
      • Account and contact management
      • Knowledge base
      • SLA management
      • Customer portal
      • Active Directory integration
      • Reporting and dashboards
      • Billing contracts
      • Live chat
      • APIs
      • Automation tools

      *Pricing unavailable. Request quote.
      See pricing on vendor’s website for latest information.

      Zoho Desk

      Est. 1996 | India | Privately Owned

      Bio

      Use the power of customer context to improve agent productivity, promote self-service, manage cross-functional service processes, and increase customer happiness. Zoho offers beautifully smart software to help you grow your business. With over 80 million users worldwide, Zoho's 55+ products (including Zoho Desk) aid your sales and marketing, support and collaboration, finance, and recruitment needs – letting you focus only on your business.

      Offices

      • Americas: Brazil, Colombia, Mexico, US
      • APAC: Australia, China, India, Japan, Singapore
      • EMEA: Netherlands, Saudi Arabia, South Africa, UAE, UK

      Zoho Desk Representative Customers

      Stated Industry Specializations

      • Covers an extremely wide range of industries, such as finance, education, government, healthcare, manufacturing, and retail.

      Software Review for Zoho Desk

      SoftwareReviews’ CSM Midmarket Vendor Ranking
      (out of 8)

      Likeliness to Recommend

      • 2nd (90%)

      Plan to Renew

      • 2nd (98%)

      Satisfaction That Cost Is Fair Relative to Value

      • 3rd (83%)

      Strengths

      • Breadth of Features (2nd)
      • Quality of Features (3rd)
      • Ease of Implementation (3rd)

      Areas to Improve

      • Business Value Created (5th)
      • Ease of Data Integration (5th)
      • Product Strategy and Rate of Improvements (5th)

      Zoho Desk

      History

      Founded 1996
      2001 Expands into Japan and shifts focus to SMBs.
      2006 Zoho CRM is launched, alongside first Office suite.
      2008 Reaches 1M users.
      2009 Rebrands from AdventNet to Zoho Corp.
      2011 Zoho Desk is built and launched.
      2017 Zoho One, a suite of applications, is launched.
      2020 Reaches 50M users.

      Zoho Desk is one of the highest scoring CSM tool providers for likelihood to renew and recommend (98% and 90%, respectively). A major reason is that users receive a broad range of functionality for a lower-cost price model. There is also the capacity to scale with Zoho Desk as midmarket customers expand; companies can grow with Zoho and can receive high return on investment in the process.

      However, while Zoho Desk can be used as a standalone CSM tool, there is danger of scope creep with other Zoho products. Zoho now has 50+ applications, all tied into one another. For Zoho Desk, customers may also lean into Zoho Assist (for troubleshooting customer problems via remote access) and Zoho Lens (for reality-based remote assistance, typically for plant machinery or servers). Consequently, customers should keep an eye on business value created if the scope of CSM grows wider.
      Thomas Randall
      Research Director, Info-Tech Research Group

      Standard Pro Enterprise
      • $14 user/month
      • 1 social media channel
      • 5 workflow rules
      • $23 user/month
      • Telephony channel
      • Round-robin ticket assignment
      • Ticket sharing
      • $40 user/month
      • Live chat
      • Contract management SLAs

      *Pricing correct as of November 2022. Listed in USD and absent discounts.
      See pricing on vendor’s website for latest information.

      Summary of AccomplishmentSuccessful selection of a CSM tool

      In this trends and buyer’s guide for CSM tool selection, we engaged in several activities to:

      1. Contextualize the CSM technology marketspace.
      2. Engage in a selection process for CSM tools.

      The result:

      • Understanding of key trends and differentiating features in the CSM marketspace.
      • Determination of your organization’s customer service maturity (and thus if a standalone CSM tool is relevant).
      • Identification of high-value use cases that CSM tools should successfully enable.
      • Evaluation of major vendors in the CSM marketspace to discover the best-fitting provider.
      • Procurement items to finalize selection process.

      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.
      workshops@infotech.com
      1-888-670-8889

      Related Info-Tech Research

      Governance and Management of Enterprise Software Implementation

      • Being Agile will increase the likelihood of success.

      The Rapid Application Selection Framework

      • Application selection is a critical activity for IT departments. Implement a repeatable, data-driven approach that accelerates application selection efforts.

      Build a Strong Technology Foundation for Customer Experience Management

      • Design an end-to-end technology strategy to drive sales revenue, enhance marketing effectiveness, and create compelling experiences for your customers.

      Bibliography

      Capers, Zach. “How the Pandemic Changed Customer Attitudes Toward Biometric Technology.” GetApp, 21 Feb. 2022. Accessed Nov. 2022.

      Gomez, Jenny. “The Good, the Bad, and the Ugly: A History of Customer Service.” Lucidworks, 15 Jul. 2021. Accessed Nov. 2022.

      Hoory. “History of Customer Service: How Did It All Begin?” Hoory, 24 Mar. 2022. Accessed Nov. 2022.

      Patel, Snigdha. “Top 10 Customer Service Technology Trends to Follow in 2022.” Reve Chat, 21 Feb. 2021. Accessed Nov. 2022.

      RingCentral. “The 2020 Customer Communications Review: A Survey of How Consumers Prefer to Communicate with Businesses.” RingCentral, 2020. Accessed Nov. 2022.

      Robinson-Yu, Sarah. “What is a Knowledgebase? How Can It Help my Business?” Vanilla, 25 Feb. 2022. Accessed Nov. 2022.

      Salesforce. “The Complete History of CRM.” Salesforce, n.d. Accessed Nov. 2022.

      Salesforce. “State of the Connected Customer.” 5th ed. Salesforce, 2022. Accessed Nov. 2022.

      Sprinklr. “How AzkoNobel UK Reduced Response Times and Increased Engagement.” Sprinklr, 2021. Accessed Nov. 2022.

      Vermes, Krystle. “Study: 70% of Marketers Using Advanced Personalization Seeing 200% ROI.” KoMarketing, 2 Jun. 2020. Accessed Nov. 2022.

      Research Contributors and Experts

      Colin Taylor, CEO, The Taylor Research Group

      Colin Taylor
      CEO
      The Taylor Reach Group

      Recognized as one of the leading contact/call center pioneers and experts, Colin has received 30 awards on two continents for excellence in contact center management and has been acknowledged as a leader and influencer on the topics of call/contact centers, customer service, and customer experience, in published rankings on Huffington Post, Call Center Helper, and MindShift. Colin was recognized as number 6 in the global 100 for customer service.

      The Taylor Reach Group is a contact center, call center and customer experience (CX) consultancy specializing in CX consulting and call and contact center consulting, management, performance, technologies, site selection, tools, training development and center leadership training, center audits, benchmarking, and assessments.

      David Thomas, Customer Service Specialist, Freedom Mobile

      David Thomas
      Customer Service Specialist
      Freedom Mobile

      David Thomas has both managerial and hands-on experience with delivering quality service to Freedom Mobile customers. With several years being involved in training customer support and being at the forefront of retail during the pandemic, David has witnessed first-hand how to incentivize staff with the right metrics that create positive experiences for both staff and customers.

      Freedom Mobile Inc. is a Canadian wireless telecommunications provider owned by Shaw Communications. It has 6% market share of Canada, mostly in urban areas of Ontario, British Columbia, and Alberta. Freedom Mobile is the fourth-largest wireless carrier in Canada.

      A special thanks to three other anonymous contributors, all based in customer support and contact center roles for Canada’s National Park Booking Systems’ software provider.

      Transition Projects Over to the Service Desk

      • Buy Link or Shortcode: {j2store}495|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
      • IT suffers from a lack of strategy and plan for transitioning support processes to the service desk.
      • Lack of effective communication between the project delivery team and the service desk, leads to an inefficient knowledge transfer to the service desk.
      • New service is not prioritized and categorized, negatively impacting service levels and end-user satisfaction.

      Our Advice

      Critical Insight

      Make sure to build a strong knowledge management strategy to identify, capture, and transfer knowledge from project delivery to the service desk.

      Impact and Result

      • Build touchpoints between the service desk and project delivery team and make strategic points in the project lifecycles to ensure service support is done effectively following the product launch.
      • Develop a checklist of action items on the initiatives that should be done following project delivery.
      • Build a training plan into the strategy to make sure service desk agents can handle tickets independently.

      Transition Projects Over to the Service Desk Research & Tools

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

      1. Transition Projects Over to the Service Desk – A guideline to walk you through transferring project support to the service desk.

      This storyboard will help you craft a project support plan to document information to streamline service support.

      • Transition Projects Over to the Service Desk Storyboard

      2. Project Handover and Checklist – A structured document to help you record information on the project and steps to take to transfer support.

      Use these two templates as a means of collaboration with the service desk to provide information on the application/product, and steps to take to make sure there are efficient service processes and knowledge is appropriately transferred to the service desk to support the service.

      • Project Handover Template
      • Service Support Transitioning Checklist
      [infographic]

      Further reading

      Transition Projects Over to the Service Desk

      Increase the success of project support by aligning your service desk and project team.

      Analyst Perspective

      Formalize your project support plan to shift customer service to the service desk.

      Photo of Mahmoud Ramin, Senior Research Analyst, Infrastructure and Operations, Info-Tech Research Group

      As a service support team member, you receive a ticket from an end user about an issue they’re facing with a new application. You are aware of the application release, but you don’t know how to handle the issue. So, you will need to either spend a long time investigating the issue via peer discussion and research or escalate it to the project team.

      Newly developed or improved services should be transitioned appropriately to the support team. Service transitioning should include planning, coordination, and communication. This helps project and support teams ensure that upon a service failure, affected end users receive timely and efficient customer support.

      At the first level, the project team and service desk should build a strategy around transitioning service support to the service desk by defining tasks, service levels, standards, and success criteria.

      In the second step, they should check the service readiness to shift support from the project team to the service desk.

      The next step is training on the new services via efficient communication and coordination between the two parties. The project team should allocate some time, according to the designed strategy, to train the service desk on the new/updated service. This will enable the service desk to provide independent service handling.

      This research walks you through the above steps in more detail and helps you build a checklist of action items to streamline shifting service support to the service desk.

      Mahmoud Ramin, PhD

      Senior Research Analyst
      Infrastructure and Operations
      Info-Tech Research Group

      Executive Summary

      Your Challenge

      • IT suffers from a lack of strategy and planning for transitioning support processes to the service desk.
      • Lack of effective communication between the project delivery team and the service desk leads to an inefficient knowledge transfer to the service desk.
      • New service is not prioritized and categorized, negatively impacting service levels and end-user satisfaction.

      Common Obstacles

      • Building the right relationship between the service desk and project team is challenging, making support transition tedious.
      • The service desk is siloed; tasks and activities are loosely defined. Service delivery is inconsistent, which impacts customer satisfaction.
      • Lack of training on new services forces the service desk to unnecessarily escalate tickets to other levels and delays service delivery.

      Info-Tech’s Approach

      • Build touchpoints between the service desk and project delivery team and make strategic points in the project lifecycles to ensure service support is done effectively following the product launch.
      • Develop a checklist of action items on the initiatives that should be done following project delivery.
      • Build a training plan into the strategy to make sure service desk agents can handle tickets independently.

      Info-Tech Insight

      Make sure to build a strong knowledge management strategy to identify, capture, and transfer knowledge from project delivery to the service desk.

      A lack of formal service transition process presents additional challenges

      When there is no formal transition process following a project delivery, it will negatively impact project success and customer satisfaction.

      Service desk team:

      • You receive a request from an end user to handle an issue with an application or service that was recently released. You are aware of the features but don’t know how to solve this issue particularly.
      • You know someone in the project group who is familiar with the service, as he was involved in the project. You reach out to him, but he is very busy with another project.
      • You get back to the user to let them know that this will be done as soon as the specialist is available. But because there is no clarity on the scope of the issue, you cannot tell them when this will be resolved.
      • Lack of visibility and commitment to the service recovery will negatively impact end-user satisfaction with the service desk.

      Project delivery team:

      • You are working on an exciting project, approaching the deadline. Suddenly, you receive a ticket from a service desk agent asking you to solve an incident on a product that was released three months ago.
      • Given the deadline on the current project, you are stressed, thinking about just focusing on the projects. On the other hand, the issue with the other service is impacting multiple users and requires much attention.
      • You spend extra time handling the issue and get back to your project. But a few days later the same agent gets back to you to take care of the same issue.
      • This is negatively impacting your work quality and causing some friction between the project team and the service desk.

      Link how improvement in project transitioning to the service desk can help service support

      A successful launch can still be a failure if the support team isn't fully informed and prepared.

      • In such a situation, the project team sends impacted users a mass notification without a solid plan for training and no proper documentation.
      • To provide proper customer service, organizations should involve several stakeholder groups to collaborate for a seamless transition of projects to the service desk.
      • This shift in service support takes time and effort; however, via proper planning there will be less confusion around customer service, and it will be done much faster.
        • For instance, if AppDev is customizing an ERP solution without considering knowledge transfer to the service desk, relevant tickets will be unnecessarily escalated to the project team.
      • On the other hand, the service desk should update configuration items (CIs) and the service catalog and related requests, incidents, problems, and workarounds to the relevant assets and configurations.
      • In this transition process, knowledge transfer plays a key role. Users, the service desk, and other service support teams need to know how the new application or service works and how to manage it when an issue arises.
      • Without a knowledge transfer, service support will be forced to either reinvent the wheel or escalate the ticket to the development team. This will unnecessarily increase the time for ticket handling, increase cost per ticket, and reduce end-user satisfaction.

      Info-Tech Insight

      Involve the service desk in the transition process via clear communication, knowledge transfer, and staff training.

      Integrate the service desk into the project management lifecycle for a smooth transition of service support

      Service desk involvement in the development, testing, and maintenance/change activity steps of your project lifecycle will help you logically define the category and priority level of the service and enable service level improvement accordingly after the project goes live.

      Project management lifecycle

      As some of the support and project processes can be integrated, responsibility silos should be broken

      Processes are done by different roles. Determine roles and responsibilities for the overlapping processes to streamline service support transition to the service desk.

      The project team is dedicated to projects, while the support team focuses on customer service for several products.

      Siloed responsibilities:

      • Project team transfers the service fully to the service desk and leaves technicians alone for support without a good knowledge transfer.
      • Specialists who were involved in the project have deep knowledge about the product, but they are not involved in incident or problem management.
      • Service desk was not involved in the planning and execution processes, which leads to lack of knowledge about the product. This leaves the support team with some vague knowledge about the service, which negatively impacts the quality of incident and problem management.

      How to break the silos:

      Develop a tiered model for the service desk and include project delivery in the specialist tier.

      • Use tier 1 (service desk) as a single point of contact to support all IT services.
      • Have tier 2/3 as experts in technology. These agents are a part of the project team. They are also involved in incident management, root-cause analysis, and change management.

      Determine the interfaces

      At the project level, get a clear understanding of support capabilities and demands, and communicate them to the service desk to proactively bring them into the planning step.

      The following questions help you with an efficient plan for support transition

      Questions for support transition

      Clear responsibilities help you define the level of involvement in the overlapping processes

      Conduct a stakeholder analysis to identify the people that can help ensure the success of the transition.

      Goal: Create a prioritized list of people who are affected by the new service and will provide support.

      Why is stakeholder analysis essential?

      Why is stakeholder analysis essential

      Identify the tasks that are required for a successful project handover

      Embed the tasks that the project team should deliver before handing support to the service desk.

      Task/Activity Example

      Conduct administrative work in the application

      • New user setup
      • Password reset

      Update documentation

      • Prepare for knowledge transfer>
      Service request fulfillment/incident management
      • Assess potential bugs
      Technical support for systems troubleshooting
      • Configure a module in ITSM solution

      End-user training

      • FAQs
      • How-to questions
      Service desk training
      • Train technicians for troubleshooting

      Support management (monitoring, meeting SLAs)

      • Monitoring
      • Meeting SLAs

      Report on the service transitioning

      • Transition effectiveness
      • Four-week warranty period
      Ensure all policies follow the transition activities
      • The final week of transition, the service desk will be called to a meeting for final handover of incidents and problems

      Integrate project description and service priority throughout development phase

      Include the service desk in discussions about project description, so it will be enabled to define service priority level.

      • Project description will be useful for bringing the project forward to the change advisory board (CAB) for approval and setting up the service in the CMDB.
      • Service priority is used for adding the next layer of attributes to the CMDB for the service and ensuring the I&O department can set up systems monitoring.
      • This should be done early in the process in conjunction with the project manager and business sponsors.
      • It should be done as the project gets underway and the team can work on specifically where that milestone will be in each project.
      • What to include in the project description:
        • Name
        • Purpose
        • Publisher
        • Departments that will use the service
        • Service information
        • Regulatory constrains
      • What to include in the service priority information:
        • Main users
        • Number of users
        • Service requirements
        • System interdependencies
        • Criticality of the dependent systems
        • Service category
        • Service SME and support backup
        • System monitoring resources
        • Alert description and flow

      Document project description and service priority in the Project Handover Template.

      Embed service levels and maintenance information

      Include the service desk in discussions about project description, so it will be enabled to define service priority level.

      • Service level objectives (SLOs) will be added to CMDB to ensure the product is reviewed for business continuity and disaster recovery and that the service team knows what is coming.
      • This step will be good to start thinking about training agents and documenting knowledgebase (KB) articles.
      • What to include in SLO:
        • Response time
        • Resolution time
        • Escalation time
        • Business owner
        • Service owner
        • Vendor(s)
        • Vendor warranties
        • Data archiving/purging
        • Availability list
        • Business continuity/recovery objectives
        • Scheduled reports
        • Problem description
      • Maintenance and change requirements: You should add maintenance windows to the change calendar and ensure the maintenance checklist is added to KB articles and technician schedules.
      • What to include in maintenance and change requirements:
        • Scheduled events for the launch
        • Maintenance windows
        • Module release
        • Planned upgrades
        • Anticipated intervals for changes and trigger points
        • Scheduled batches

      Document service level objectives and maintenance in the Project Handover Template.

      Enhance communication between the project team and the service desk

      Communicating with the service desk early and often will ensure that agents fully get a deep knowledge of the new technology.

      Transition of a project to the service desk includes both knowledge transfer and execution transfer.

      01

      Provide training and mentoring to ensure technical knowledge is passed on.

      02

      Transfer leadership responsibilities by appointing the right people.

      03

      Transfer support by strategically assigning workers with the right technical and interpersonal skills.

      04

      Transfer admin rights to ensure technicians have access rights for troubleshooting.

      05

      Create support and a system to transfer work process. For example, using an online platform to store knowledge assets is a great way for support to access project information.

      Info-Tech Insight

      A communication plan and executive presentation will help project managers outline recommendations and communicate their benefits.

      Communicate reasons for projects and how they will be implemented

      Proactive communication of the project to affected stakeholders will help get their buy-in for the new technology and feedback for better support.

      Leaders of successful change spend considerable time developing a powerful change message, i.e. a compelling narrative that articulates the desired end state, that makes the change concrete and meaningful to staff.

      The message should:

      • Explain why the change or new application is needed.
      • Summarize what will stay the same.
      • Highlight what will be left behind.
      • Emphasize what is being changed due to the new or updated product.
      • Explain how the application will be implemented.
      • Address how this will affect various roles in the organization.
      • Discuss the staff’s role in making the project successful.
      • Communicate the supporting roles in the early implementation stages and later on.

      Five elements of communicating change

      Implement knowledge transfer to the service desk to ensure tickets won’t be unnecessarily escalated

      The support team usually uses an ITSM solution, while the project team mostly uses a project management solution. End users’ support is done and documented in the ITSM tool.

      Even terminologies used by these teams are different. For instance, service desk’s “incident” is equivalent to a project manager’s “defect.” Without proper integration of the development and support processes, the contents get siloed and outdated over time.

      Potential ways to deal with this challenge:

      Use the same platform for both project and service support

      This helps you document information in a single platform and provides better visibility of the project status to the support team as well. It also helps project team find out change-related incidents for a faster rollback.

      Note: This is not always feasible because of the high costs incurred in purchasing a new application with both ITSM and PM capabilities and the long time it takes for implementing such a solution.

      Integrate the PM and ITSM tools to improve transition efficiency

      Note: Consider the processes that should be integrated. Don’t integrate unnecessary steps in the development stage, such as design, which will not be helpful for support transition.

      Build a training plan for the new service

      When a new system is introduced or significant changes are applied, describe the steps and timeline for training.

      Training the service desk has two-fold benefits:
      Improve support:
      • Support team gets involved in user acceptance testing, which will provide feedback on potential bugs or failures in the technology.
      • Collaboration between specialists and tier 1 technicians will allow the service desk to gather information for handling potential incidents on the application.
      Shift-left enablement:
      • At the specialist level, agents will be more focused on other projects and spend less time on application issues, as they are mostly handled by the service desk.
      • As you shift service support left:
        • Cost per ticket decreases as more of the less costly resources are doing the work.
        • Average time to resolve decreases as the ticket is handled by the service desk.
        • End-user satisfaction increases as they don’t need to wait long for resolution.

      Who resolves the incident

      For more information about shift-left enablement, refer to InfoTech’s blueprint Optimize the Service Desk With a Shift-Left Strategy.

      Integrate knowledge management in the transition plan

      Build a knowledge transfer process to streamline service support for the newly developed technology.

      Use the following steps to ensure the service desk gets trained on the new project.

      1. Identify learning opportunities.
      2. Prioritize the identified opportunities based on:
      • Risk of lost knowledge
      • Impact of knowledge on support improvement
    • Define ways to transfer knowledge from the project team to the service desk. These could be:
      • One-on-one meetings
      • Mentoring sessions
      • Knowledgebase articles
      • Product road test
      • Potential incident management shadowing
    • Capture and transfer knowledge (via the identified means).
    • Support the service desk with further training if the requirement arises.
    • Info-Tech Insight

      Allocate knowledge transfer within ticket handling workflows. When incident is resolved by a specialist, they will assess if it is a good candidate for technician training and/or a knowledgebase article. If so, the knowledge manager will be notified of the opportunity to assign it to a SME for training and documentation of an article.

      For more information about knowledge transfer, refer to phase 3 of Info-Tech’s blueprint Standardize the Service Desk.

      Focus on the big picture first

      Identify training functions and plan for a formal knowledge transfer

      1. Brainstorm training functions for each group.
      2. Determine the timeline needed to conduct training for the identified training topics.
      RoleTraining FunctionTimeline

      Developer/Technical Support

      • Coach the service desk on the new application
      • Document relevant KB articles
      Business Analysts
      • Conduct informational interviews for new business requirements

      Service Desk Agents

      • Conduct informational interviews
      • Shadow incident management procedures
      • Document lessons learned
      Vendor
      • Provide cross-training to support team

      Document your knowledge transfer plan in the Project Handover Template.

      Build a checklist of the transition action items

      At this stage, the project is ready to go live and support needs to be independently done by the service desk.

      Checklist of the transition action items

      Info-Tech Insight

      No matter how well training is done, specialists may need to work on critical incidents and handle emergency changes. With effective service support and transition planning, you can make an agreement between the incident manager, change manager, and project manager on a timeline to balance critical incident or emergency change management and project management and define your SLA.

      Activity: Prepare a checklist of initiatives before support transition

      2-3 hours

      Document project support information and check off each support transition initiative as you shift service support to the service desk.

      1. As a group, review the Project Handover Template that you filled out in the previous steps.
      2. Download the Service Support Transitioning Checklist, and review the items that need to be done throughout the development, testing, and deployment steps of your project.
      3. Brainstorm at what step service desk needs to be involved.
      4. As you go through each initiative and complete it, check it off to make sure you are following the agreed document for a smooth transition of service support.
      Input Output
      • Project information
      • Support information for developed application/service
      • List of transitioning initiatives
      MaterialsParticipants
      • Project Handover Template
      • Service Support Transitioning Checklist
      • Project Team
      • Service Desk Manager
      • IT Lead

      Download the Project Handover Template

      Download the Service Support Transitioning Checklist

      Define metrics to track the success of project transition

      Consider key metrics to speak the language of targeted end users.

      You won’t know if transitioning support processes are successful unless you measure their impact. Find out your objectives for project transition and then track metrics that will allow you to fulfill these goals.

      Determine critical success factors to help you find out key metrics:

      High quality of the service

      Effectiveness of communication of the transition

      Manage risk of failure to help find out activities that will mitigate risk of service disruption

      Smooth and timely transition of support to the service desk

      Efficient utilization of the shared services and resources to mitigate conflicts and streamline service transitioning

      Suggested metrics:

      • Time to fulfill requests and resolve incidents for the new project
      • Time spent training the service desk
      • Number of knowledgebase articles created by the project team
      • Percentage of articles used by the service desk that prevented ticket escalation
      • First-level resolution
      • Ratio of escalated tickets for the new project
      • Problem ticket volume for the new project
      • Average customer satisfaction with the new project support
      • SLA breach rate

      Summary of Accomplishment

      Problem Solved

      Following the steps outlined in this research has helped you build a strategy to shift service support from the project team to the service desk, resulting in an improvement in customer service and agent satisfaction.

      You have also developed a plan to break the silo between the service desk and specialists and enable knowledge transfer so the service desk will not need to unnecessarily escalate tickets to developers. In the meantime, specialists are also responsible for service desk training on the new application.

      Efficient communication of service levels has helped the project team set clear expectations for managers to create a balance between their projects and service 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

      Related Info-Tech Research

      Standardize the Service Desk

      Improve customer service by driving consistency in your support approach and meeting SLAs.

      Optimize the Service Desk With a Shift-Left Strategy

      The best type of service desk ticket is the one that doesn’t exist.

      Tailor IT Project Management Processes to Fit Your Projects

      Right-size PMBOK for all of your IT projects.

      Works Cited

      Brown, Josh. “Knowledge Transfer: What it is & How to Use it Effectively.” Helpjuice, 2021. Accessed November 2022.

      Magowan, Kirstie. “Top ITSM Metrics & KPIs: Measuring for Success, Aiming for Improvement.” BMC Blogs, 2020. Accessed November 2022.

      “The Complete Blueprint for Aligning Your Service Desk and Development Teams (Process Integration and Best Practices).” Exalate, 2021. Accessed October 2022.

      “The Qualities of Leadership: Leading Change.” Cornelius & Associates, 2010. Web.

      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

      Create a Holistic IT Dashboard

      • Buy Link or Shortcode: {j2store}117|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: $8,049 Average $ Saved
      • member rating average days saved: 8 Average Days Saved
      • Parent Category Name: Performance Measurement
      • Parent Category Link: /performance-measurement
      • IT leaders do not have a single holistic view of how their 45 IT processes are operating.
      • Expecting any single individual to understand the details of all 45 IT processes is unrealistic.
      • Problems in performance only become evident when the process has already failed.

      Our Advice

      Critical Insight

      • Mature your IT department by measuring what matters.
      • Don’t measure things just because you can; change what you measure as your organization matures.

      Impact and Result

      • Use Info-Tech’s IT Metrics Library to review typical KPIs for each of the 45 process areas and select those that apply to your organization.
      • Configure your IT Management Dashboard to record your selected KPIs and start to measure performance.
      • Set up the cadence for review of the KPIs and develop action plans to improve low-performing indicators.

      Create a Holistic IT Dashboard Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out how to develop your KPI program that leads to improved performance.

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

      1. Choose the KPIs

      Identify the KPIs that matter to your organization’s goals.

      • Create a Holistic IT Dashboard – Phase 1: Choose the KPIs
      • IT Metrics Library

      2. Build the Dashboard

      Use the IT Management Dashboard on the Info-Tech website to display your chosen KPIs.

      • Create a Holistic IT Dashboard – Phase 2: Build the Dashboard

      3. Create the Action Plan

      Use the review of your KPIs to build an action plan to drive performance.

      • Create a Holistic IT Dashboard – Phase 3: Build the Action Plan
      [infographic]

      Workshop: Create a Holistic IT Dashboard

      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 to Measure (Offsite)

      The Purpose

      Determine the KPIs that matter to your organization.

      Key Benefits Achieved

      Identify organizational goals

      Identify IT goals and their organizational goal alignment

      Identify business pain points

      Activities

      1.1 Identify organizational goals.

      1.2 Identify IT goals and organizational alignment.

      1.3 Identify business pain points.

      Outputs

      List of goals and pain points to create KPIs for

      2 Configure the Dashboard Tool (Onsite)

      The Purpose

      Learn how to configure and use the IT Management Dashboard.

      Key Benefits Achieved

      Configured IT dashboard

      Initial IT scorecard report

      Activities

      2.1 Review metrics and KPI best practices.

      2.2 Use the IT Metrics Library.

      2.3 Select the KPIs for your organization.

      2.4 Use the IT Management Dashboard.

      Outputs

      Definition of KPIs to be used, data sources, and ownership

      Configured IT dashboard

      3 Review and Develop the Action Plan

      The Purpose

      Learn how to review and plan actions based on the KPIs.

      Key Benefits Achieved

      Lead KPI review to actions to improve performance

      Activities

      3.1 Create the scorecard report.

      3.2 Interpret the results of the dashboard.

      3.3 Use the IT Metrics Library to review suggested actions.

      Outputs

      Initial IT scorecard report

      Action plan with initial actions

      4 Improve Your KPIs (Onsite)

      The Purpose

      Use your KPIs to drive performance.

      Key Benefits Achieved

      Improve your metrics program to drive effectiveness

      Activities

      4.1 Develop your action plan.

      4.2 Execute the plan and tracking progress.

      4.3 Develop new KPIs as your practice matures.

      Outputs

      Understanding of how to develop new KPIs using the IT Metrics Library

      5 Next Steps and Wrap-Up (Offsite)

      The Purpose

      Ensure all documentation and plans are complete.

      Key Benefits Achieved

      Documented next steps

      Activities

      5.1 Complete IT Metrics Library documentation.

      5.2 Document decisions and next steps.

      Outputs

      IT Metrics Library

      Action plan

      Further reading

      Create a Holistic IT Dashboard

      Mature your IT department by measuring what matters.

      Executive Brief

      Analyst Perspective

      Measurement alone provides only minimal improvements

      It’s difficult for CIOs and other top-level leaders of IT to know if everything within their mandate is being managed effectively. Gaining visibility into what’s happening on the front lines without micromanaging is a challenge most top leaders face.

      Understanding Info-Tech’s Management and Governance Framework of processes that need to be managed and being able to measure what’s important to their organization's success can give leaders the ability to focus on their key responsibilities of ensuring service effectiveness, enabling increased productivity, and creating the ability for their teams to innovate.

      Even if you know what to measure, the measurement alone will lead to minimal improvements. Having the right methods in place to systematically collect, review, and act on those measurements is the differentiator to driving up the maturity of your IT organization.

      The tools in this blueprint can help you identify what to measure, how to review it, and how to create effective plans to improve performance.

      Tony Denford

      Research Director, Info-Tech Research Group

      Executive Summary

      Your Challenge

      • IT leaders do not have a single holistic view of how their IT processes are operating.
      • Expecting any single individual to understand the details of all IT processes is unrealistic.
      • Problems in performance only become evident when the process has already failed.

      Common Obstacles

      • Business changes quickly, and what should be measured changes as a result.
      • Most measures are trailing indicators showing past performance.
      • Measuring alone does not result in improved performance.
      • There are thousands of operational metrics that could be measured, but what are the right ones for an overall dashboard?

      Info-Tech's Approach

      • Use Info-Tech’s IT Metrics Library to review typical KPIs for each of the process areas and select those that apply to your organization.
      • Configure your IT Management Dashboard to record your selected KPIs and start to measure performance.
      • Set up the cadence for review of the KPIs and develop action plans to improve low-performing indicators.

      Info-Tech Insight

      Mature your IT department by aligning your measures with your organizational goals. Acting early when your KPIs deviate from the goals leads to improved performance.

      Your challenge

      This research is designed to help organizations quickly choose holistic measures, review the results, and devise action plans.

      • The sheer number of possible metrics can be overwhelming. Choose metrics from our IT Metrics Library or choose your own, but always ensure they are in alignment with your organizational goals.
      • Ensure your dashboard is balanced across all 45 process areas that a modern CIO is responsible for.
      • Finding leading indicators to allow your team to be proactive can be difficult if your team is focused on the day-to-day operational tasks.
      • It can be time consuming to figure out what to do if an indicator is underperforming.

      Build your dashboard quickly using the toolset in this research and move to improvement actions as soon as possible.

      The image is a bar graph, titled KPI-based improvements. On the X-axis are four categories, each with one bar for Before KPIs and another for After KPIs. The categories are: Productivity; Fire Incidents; Request Response Time; and Savings.

      Productivity increased by 30%

      Fire/smoke incidents decreased by 25% (high priority)

      Average work request response time reduced by 64%

      Savings of $1.6 million in the first year

      (CFI, 2013)

      Common obstacles

      These barriers make this challenge difficult to address for many organizations:

      • What should be measured can change over time as your organization matures and the business environment changes. Understanding what creates business value for your organization is critical.
      • Organizations almost always focus on past result metrics. While this is important, it will not indicate when you need to adjust something until it has already failed.
      • It’s not just about measuring. You also need to review the measures often and act on the biggest risks to your organization to drive performance.

      Don’t get overwhelmed by the number of things you can measure. It can take some trial and error to find the measures that best indicate the health of the process.

      The importance of frequent review

      35% - Only 35% of governing bodies review data at each meeting. (Committee of University Chairs, 2008)

      Common obstacles

      Analysis paralysis

      Poor data can lead to incorrect conclusions, limit analysis, and undermine confidence in the value of your dashboard.

      Achieving perfect data is extremely time consuming and may not add much value. It can also be an excuse to avoid getting started with metrics and analytics.

      Data quality is a struggle for many organizations. Consider how much uncertainty you can tolerate in your analysis and what would be required to improve your data quality to an acceptable level. Consider cost, technological resources, people resources, and time required.

      Info-Tech Insight

      Analytics are only as good as the data that informs it. Aim for just enough data quality to make informed decisions without getting into analysis paralysis.

      Common obstacles

      The problem of surrogation

      Tying KPIs and metrics to performance often leads to undesired behavior. An example of this is the now infamous Wells Fargo cross-selling scandal, in which 3.5 million credit card and savings accounts were opened without customers’ consent when the company incented sales staff to meet cross-selling targets.

      Although this is an extreme example, it’s an all-too-common phenomenon.

      A focus on the speed of closure of tickets often leads to shortcuts and lower-quality solutions.

      Tying customer value to the measures can align the team on understanding the objective rather than focusing on the measure itself, and the team will no longer be able to ignore the impact of their actions.

      Surrogation is a phenomenon in which a measure of a behavior replaces the intent of the measure itself. People focus on achieving the measure instead of the behavior the measure was intended to drive.

      Info-Tech’s thought model

      The Threefold Role of the IT Executive Core CIO Objectives
      IT Organization - Manager A - Optimize the Effectiveness of the IT Organization
      Enterprise - Partner B - Boost the Productivity of the Enterprise
      Market - Innovator C - Enable Business Growth Through Technology

      Low-Maturity Metrics Program

      Trailing indicators measure the outcomes of the activities of your organization. Hopefully, the initiatives and activities are aligned with the organizational goals.

      High-Maturity Metrics Program

      The core CIO objectives align with the organizational goals, and teams define leading indicators that show progress toward those goals. KPIs are reviewed often and adjustments are made to improve performance based on the leading indicators. The results are improved outcomes, greater transparency, and increased predictability.

      The image is a horizontal graphic with multiple text boxes. The first (on the left) is a box that reads Organizational Goals, second a second box nested within it that reads Core CIO Objectives. There is an arrow pointing from this box to the right. The arrow connects to a text box that reads Define leading indicators that show progress toward objectives. To the right of that, there is a title Initiatives & activities, with two boxes beneath it: Processes and Projects. Below this middle section, there is an arrow pointing left, with the text: Adjust behaviours. After this, there is an arrow pointing right, to a box with the title Outcomes, and the image of an unlabelled bar graph.

      Info-Tech’s approach

      Adopt an iterative approach to develop the right KPIs for your dashboard

      Periodically: As appropriate, review the effectiveness of the KPIs and adjust as needed.

      Frequently: At least once per month, but the more frequent, the more agility your organization will have.

      The image shows a series of steps in a process, each connected by an arrow. The process is iterative, so the steps circle back on themselves, and repeat. The process begins with IT Metrics Library, then Choose or build KPIs, then Build Dashboard, then Review KPIs and Create action plan. Review KPIs and Create action plan are steps that the graphic indicates should be repeated, so the arrows are arranged in a circle around these two items. Following that, there is an additional step: Are KPIs and action plans leading to improved results? After this step, we return to the Choose or build KPIs step.

      The Info-Tech difference:

      1. Quickly identify the KPIs that matter to your organization using the IT Metrics Library.
      2. Build a presentable dashboard using the IT Management Dashboard available on the Info-Tech website.
      3. When indicators show underperformance, quickly get them back on track using the suggested research in the IT Metrics Library.
      4. If your organization’s needs are different, define your own custom metrics using the same format as the IT Metrics Library.
      5. Use the action plan tool to keep track of progress

      Info-Tech’s methodology for creating a holistic IT dashboard

      1. Choose the KPIs 2. Build the Dashboard 3. Create the Action Plan
      Phase Steps
      1. Review available KPIs
      2. Select KPIs for your organization
      3. Identify data sources and owners
      1. Understand how to use the IT Management Dashboard
      2. Build and review the KPIs
      1. Prioritize low-performing indicators
      2. Review suggested actions
      3. Develop your action plan
      Phase Outcomes A defined and documented list of the KPIs that will be used to monitor each of the practice areas in your IT mandate A configured dashboard covering all the practice areas and the ability to report performance in a consistent and visible way An action plan for addressing low-performing indicators

      Insight summary

      Mature your IT department by aligning your measures with your organizational goals. Acting early when your KPIs deviate from the goals leads to improved performance.

      Don’t just measure things because you can. Change what you measure as your organization becomes more mature.

      Select what matters to your organization

      Measure things that will resolve pain points or drive you toward your goals.

      Look for indicators that show the health of the practice, not just the results.

      Review KPIs often

      Ease of use will determine the success of your metrics program, so keep it simple to create and review the indicators.

      Take action to improve performance

      If indicators are showing suboptimal performance, develop an action plan to drive the indicator in the right direction.

      Act early and often.

      Measure what your customers value

      Ensure you understand what’s valued and measure whether the value is being produced. Let front-line managers focus on tactical measures and understand how they are linked to value.

      Look for predictive measures

      Determine what action will lead to the desired result and measure if the action is being performed. It’s better to predict outcomes than react to them.

      Blueprint deliverables

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

      IT Metrics Library

      Customize the KPIs for your organization using the IT Metrics Library

      IT Metrics Library Action Plan

      Keep track of the actions that are generated from your KPI review

      Key deliverable:

      IT Management Dashboard and Scorecard

      The IT Overall Scorecard gives a holistic view of the performance of each IT function

      Blueprint benefits

      IT Benefits

      • An IT dashboard can help IT departments understand how well they are performing against key indicators.
      • It can allow IT teams to demonstrate to their business partners the areas they are focusing on.
      • Regular review and action planning based on the results will lead to improved performance, efficiency, and effectiveness.
      • Create alignment of IT teams by focusing on common areas of performance.

      Business Benefits

      • Ensure alignment and transparency between the business and IT.
      • Understand the value that IT brings to the operation and strategic initiatives of your organization.
      • Understand the contribution of the IT team to achieving business outcomes.
      • Focus IT on the areas that are important to you by requesting new measures as business needs change.

      Measure the value of this blueprint

      Utilize the existing IT Metrics Library and IT Dashboard tools to quickly kick off your KPI program

      • Developing the metrics your organization should track can be very time consuming. Save approximately 120 hours of effort by choosing from the IT Metrics Library.
      • The need for a simple method to display your KPIs means either developing your own tool or buying one off the shelf. Use the IT Management Dashboard to quickly get your KPI program up and running. Using these tools will save approximately 480 hours.
      • The true value of this initiative comes from using the KPIs to drive performance.

      Keeping track of the number of actions identified and completed is a low overhead measure. Tracking time or money saved is higher overhead but also higher value.

      The image is a screen capture of the document titled Establish Baseline Metrics. It shows a table with the headings: Metric, Current, Goal.

      The image is a chart titled KPI benefits. It includes a legend indicating that blue bars are for Actions identified, purple bars are for Actions completed, and the yellow line is for Time/money saved. The graph shows Q1-Q4, indicating an increase in all areas across the quarters.

      Executive Brief Case Study

      Using data-driven decision making to drive stability and increase value

      Industry: Government Services

      Source: Info-Tech analyst experience

      Challenge

      A newly formed application support team with service desk responsibilities was becoming burned out due to the sheer volume of work landing on their desks. The team was very reactive and was providing poor service due to multiple conflicting priorities.

      To make matters worse, there was a plan to add a major new application to the team’s portfolio.

      Solution

      The team began to measure the types of work they were busy doing and then assessed the value of each type of work.

      The team then problem solved how they could reduce or eliminate their low-value workload.

      This led to tracking how many problems were being resolved and improved capabilities to problem solve effectively.

      Results

      Upon initial data collection, the team was performing 100% reactive workload. Eighteen months later slightly more than 80% of workload was proactive high-value activities.

      The team not only was able to absorb the additional workload of the new application but also identified efficiencies in their interactions with other teams that led to a 100% success rate in the change process and a 92% decrease in resource needs for major incidents.

      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 GI on this topic look like?

      Phase 1 - Choose the KPIs

      Call #1: Scope dashboard and reporting needs.

      Call #2: Learn how to use the IT Metrics Library to select your metrics.

      Phase 2 – Build the Dashboard

      Call #3: Set up the dashboard.

      Call #4: Capture data and produce the report.

      Phase 3 – Create the Action Plan

      Call #5: Review the data and use the metrics library to determine actions.

      Call #6: Improve the KPIs you measure.

      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 5 and 8 calls over the course of 2 to 3 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
      Identify What to Measure Configure the Dashboard Tool Review and Develop the Action Plan Improve Your KPIs Compile Workshop Output
      Activities

      1.1 Identify organizational goals.

      1.2 Identify IT goals and organizational alignment.

      1.3 Identify business pain points.

      2.1 Determine metrics and KPI best practices.

      2.2 Learn how to use the IT Metrics Library.

      2.3 Select the KPIs for your organization.

      2.4 Configure the IT Management Dashboard.

      3.1 Create the scorecard report.

      3.2 Interpret the results of the dashboard.

      3.3 Use the IT Metrics Library to review suggested actions.

      4.1 Develop your action plan.

      4.2 Execute the plan and track progress.

      4.3 Develop new KPIs as your practice matures.

      5.1 Complete the IT Metrics Library documentation.

      5.2 Document decisions and next steps.

      Outcomes 1. List of goals and pain points that KPIs will measure

      1. Definition of KPIs to be used, data sources, and ownership

      2. Configured IT dashboard

      1. Initial IT scorecard report

      2. Action plan with initial actions

      1. Understanding of how to develop new KPIs using the IT Metrics Library

      1. IT Metrics Library documentation

      2. Action plan

      Phase 1

      Choose the KPIs

      Phase 1

      1.1 Review Available KPIs

      1.2 Select KPIs for Your Org.

      1.3 Identify Data Sources and Owners

      Phase 2

      2.1 Understand the IT Management Dashboard

      2.2 Build and Review the KPIs

      Phase 3

      3.1 Prioritize Low-Performing Indicators

      3.2 Review Suggested Actions

      3.3 Develop the Action Plan

      This phase will walk you through the following activities:

      Reviewing and selecting the KPIs suggested in the IT Metrics Library.

      Identifying the data source for the selected KPI and the owner responsible for data collection.

      This phase involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Step 1.1

      Review Available KPIs

      Activities

      1.1.1 Download the IT Metrics Library and review the KPIs for each practice area.

      Choose the KPIs

      Step 1.1 – Review Available KPIs

      Step 1.2 – Select KPIs for Your Org.

      Step 1.3 – Identify Data Sources and owners

      This step will walk you through the following activities:

      Downloading the IT Metrics Library

      Understanding the content of the tool

      Reviewing the intended goals for each practice area

      This step involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Outcomes of this step

      Downloaded tool ready to select the KPIs for your organization

      Using the IT Metrics Library

      Match the suggested KPIs to the Management and Governance Framework

      The “Practice” and “Process” columns relate to each of the boxes on the Info-Tech Management and Governance Framework. This ensures you are measuring each area that needs to be managed by a typical IT department.

      The image shows a table on the left, and on the right, the Info-Tech Management and Governance Structure. Sections from the Practice and Process columns of the table have arrows emerging from them, pointing to matching sections in the framework.

      Using the IT Metrics Library

      Content for each entry

      KPI - The key performance indicator to review

      CSF - What needs to happen to achieve success for each goal

      Goal - The goal your organization is trying to achieve

      Owner - Who will be accountable to collect and report the data

      Data Source (typical) - Where you plan to get the data that will be used to calculate the KPI

      Baseline/Target - The baseline and target for the KPI

      Rank - Criticality of this goal to the organization's success

      Action - Suggested action if KPI is underperforming

      Blueprint - Available research to address typical underperformance of the KPI

      Practice/Process - Which practice and process the KPI represents

      1.1.1 Download the IT Metrics Library

      Input

      • IT Metrics Library

      Output

      • Ideas for which KPIs would be useful to track for each of the practice areas

      Materials

      • Whiteboard/flip charts

      Participants

      • IT senior leadership
      • Process area owners
      • Metrics program owners and administrators

      4 hours

      1. Click the link below to download the IT Metrics Library spreadsheet.
      2. Open the file and select the “Data Entry” tab.
      3. The sheet has suggested KPIs for each of the 9 practice areas and 45 processes listed in the Info-Tech Management and Governance Framework. You can identify this grouping in the “Practice” and “Process” columns.
      4. For each practice area, review the suggested KPIs and their associated goals and discuss as a team which of the KPIs would be useful to track in your organization.

      Download the IT Metrics Library

      Step 1.2

      Select KPIs for Your Organization

      Activities

      1.2.1 Select the KPIs that will drive your organization forward

      1.2.2 Remove unwanted KPIs from the IT Metrics Library

      Choose the KPIs

      Step 1.1 – Review Available KPIs

      Step 1.2 – Select KPIs for Your Org.

      Step 1.3 – Identify Data Sources and Owners

      This step will walk you through the following activities:

      • Selecting the KPIs for your organization and removing unwanted KPIs from IT Metrics Library

      This step involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Outcomes of this step

      A shortlist of selected KPIs

      1.2.1 Select the KPIs that will drive your organization forward

      Input

      • IT Metrics Library

      Output

      • KPIs would be useful to track for each of the practice areas

      Materials

      • IT Metrics Library

      Participants

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      4 hours

      1. Review the suggested KPIs for each practice area and review the goal.
      2. Some suggested KPIs are similar, so make sure the goal is appropriate for your organization.
      3. Pick up to three KPIs per practice.

      1.2.2 Remove unwanted KPIs

      Input

      • IT Metrics Library

      Output

      • KPIs would be useful to track for each of the practice areas

      Materials

      • IT Metrics Library

      Participants

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      0.5 hours

      1. To remove unwanted KPIs from the IT Metric Library Tool, select the unwanted row, right-click on the row, and delete it.
      2. The result should be up to three KPIs per practice area left on the spreadsheet.

      Step 1.3

      Identify data sources and owners

      Activities

      1.3.1 Document the data source

      1.3.2 Document the owner

      1.3.3 Document baseline and target

      Choose the KPIs

      Step 1.1 – Review Available KPIs

      Step 1.2 – Select KPIs for Your Org.

      Step 1.3 – Identify Data Sources and Owners

      This step will walk you through the following activities:

      Documenting for each KPI where you plan to get the data, who is accountable to collect and report the data, what the current baseline is (if available), and what the target is

      This step involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Outcomes of this step

      A list of KPIs for your organization with appropriate attributes documented

      1.3 Identify data sources, owners, baseline, and target

      Input

      • IT Metrics Library

      Output

      • Completed IT Metrics Library

      Materials

      • IT Metrics Library

      Participants

      • Process area owners
      • Metrics program owners and administrators

      2 hours

      1. For each selected KPI, complete the owner, data source, baseline, and target if the information is available.
      2. If the information is not available, document the owner and assign them to complete the other columns.

      Phase 2

      Build the Dashboard

      Phase 1

      1.1 Review Available KPIs

      1.2 Select KPIs for Your Org.

      1.3 Identify Data Sources and Owners

      Phase 2

      2.1 Understand the IT Management Dashboard

      2.2 Build and Review the KPIs

      Phase 3

      3.1 Prioritize Low-Performing Indicators

      3.2 Review Suggested Actions

      3.3 Develop the Action Plan

      This phase will walk you through the following activities:

      Understanding the IT Management Dashboard

      Configuring the IT Management Dashboard and entering initial measures

      Produce thing IT Scorecard from the IT Management Dashboard

      Interpreting the results

      This phase involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Step 2.1

      Understand the IT Management Dashboard

      Activities

      2.1.1 Logging into the IT Management Dashboard

      2.1.2 Understanding the “Overall Scorecard” tab

      2.1.3 Understanding the “My Metrics” tab

      Build the Dashboard

      Step 2.1 – Understand the IT Management Dashboard

      Step 2.2 – Build and review the KPIs

      This step will walk you through the following activities:

      Accessing the IT Management Dashboard

      Basic functionality of the tool

      This step involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Outcomes of this step

      Understanding of how to administer the IT Management Dashboard

      2.1.1 Logging into the IT Management Dashboard

      Input

      • Info-Tech membership

      Output

      • Access to the IT Management Dashboard

      Materials

      • Web browser

      Participants

      • Metrics program owners and administrators

      0.5 hours

      1. Using your web browser, access your membership at infotech.com.
      2. Log into your Info-Tech membership account.
      3. Select the “My IT Dashboard” option from the menu (circled in red).
      4. If you cannot gain access to the tool, contact your membership rep.

      The image is a screen capture of the Info-Tech website, with the Login button at the top right of the window circled in red.

      2.1.2 Understanding the “Overall Scorecard” tab

      0.5 hours

      1. Once you select “My IT Dashboard,” you will be in the “Overall Scorecard” tab view.
      2. Scrolling down reveals the data entry form for each of the nine practice areas in the Info-Tech Management and Governance Framework, with each section color-coded for easy identification.
      3. Each of the section headers, KPI names, data sources, and data values can be updated to fit the needs of your organization.
      4. This view is designed to show a holistic view of all areas in IT that are being managed.

      2.1.3 Understanding the “My Metrics” tab

      0.5 hours

      1. On the “My Metrics” tab you can access individual scorecards for each of the nine practice areas.
      2. Below the “My Metrics” tab is each of the nine practice areas for you to select from. Each shows a different subset of KPIs specific to the practice.
      3. The functionality of this view is the same as the overall scorecard. Each title, KPI, description, and actuals are editable to fit your organization’s needs.
      4. This blueprint does not go into detail on this tab, but it is available to be used by practice area leaders in the same way as the overall scorecard.

      Step 2.2

      Build and review the KPIs

      Activities

      2.2.1 Entering the KPI descriptions

      2.2.2 Entering the KPI actuals

      2.2.3 Producing the IT Overall Scorecard

      Build the Dashboard

      Step 2.1 – Understand the IT Management Dashboard

      Step 2.2 – Build and review the KPIs

      This step will walk you through the following activities:

      Entering the KPI descriptions

      Entering the actuals for each KPI

      Producing the IT Overall Scorecard

      This step involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Outcomes of this step

      An overall scorecard indicating the selected KPI performance

      2.2.1 Entering the KPI descriptions

      Input

      • Access to the IT Management Dashboard
      • IT Metrics Library with your organization’s KPIs selected

      Output

      • KPI descriptions entered into tool

      Materials

      • Web browser

      Participants

      • Metrics program owners and administrators

      1 hour

      1. Navigate to the IT Management Dashboard as described in section 2.1.1 and scroll down to the practice area you wish to complete.
      2. If needed, modify the section name to match your organization’s needs.
      3. Select “Add another score.”

      2.2.1 Entering the KPI descriptions

      1 hour

      1. Select if your metric is a custom metric or a standard metric available from one of the Info-Tech diagnostic tools.
      2. Enter the metric name you selected from the IT Metrics Library.
      3. Select the value type.
      4. Select the “Add Metric” button.
      5. The descriptions only need to be entered when they change.

      Example of a custom metric

      The image is a screen capture of the Add New Metric function. The metric type selected is Custom metric, and the metric name is Employee Engagement. There is a green Add Metric button, which is circled in red.

      Example of a standard metric

      The image is a screen capture of the Add New Metric function. The metric type selected is Standard Metric. The green Add Metric button at the bottom is circled in red.

      2.2.2 Entering the KPI actuals

      Input

      • Actual data from each data source identified

      Output

      • Actuals recorded in tool

      Materials

      • Web browser

      Participants

      • Metrics program owners and administrators

      1 hour

      1. Select the period you wish to create a scorecard for by selecting “Add New Period” or choosing one from the drop-down list.
      2. For each KPI on your dashboard, collect the data from the data source and enter the actuals.
      3. Select the check mark (circled) to save the data for the period.

      The image is a screen capture of the My Overall Scorecard Metrics section, with a button at the bottom that reads Add New Period circled in red

      The image has the text People and Resources at the top. It shows data for the KPI, and there is a check mark circled in red.

      2.2.3 Producing the IT Overall Scorecard

      Input

      • Completed IT Overall Scorecard data collection

      Output

      • IT Overall Scorecard

      Materials

      • Web browser

      Participants

      • Metrics program owners and administrators

      0.5 hours

      1. Select the period you wish to create a scorecard for by selecting from the drop-down list.
      2. Click the “Download as PDF” button to produce the scorecard.
      3. Once the PDF is produced it is ready for review or distribution.

      Phase 3

      Create the Action Plan

      Phase 1

      1.1 Review Available KPIs

      1.2 Select KPIs for Your Org.

      1.3 Identify Data Sources and Owners

      Phase 2

      2.1 Understand the IT Management Dashboard

      2.2 Build and Review the KPIs

      Phase 3

      3.1 Prioritize Low-Performing Indicators

      3.2 Review Suggested Actions

      3.3 Develop the Action Plan

      This phase will walk you through the following activities:

      Prioritizing low-performing indicators

      Using the IT Metrics Library to review suggested actions

      Developing your team’s action plan to improve performance

      This phase involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Step 3.1

      Prioritize low-performing indicators

      Activities

      3.1.1 Determine criteria for prioritization

      3.1.2 Identify low-performing indicators

      3.1.3 Prioritize low-performing indicators

      Create the action plan

      Step 3.1 – Prioritize low-performing indicators

      Step 3.2 – Review suggested actions

      Step 3.3 – Develop the action plan

      This step will walk you through the following activities:

      Determining the criteria for prioritization of low-performing indicators

      Identifying low-performing indicators

      Prioritizing the low-performing indicators

      This step involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Outcomes of this step

      A prioritized list of low-performing indicators that need remediation

      3.1.1 Determine criteria for prioritization

      Often when metrics programs are established, there are multiple KPIs that are not performing at the desired level. It’s easy to expect the team to fix all the low-performing indicators, but often teams are stretched and have conflicting priorities.

      Therefore it’s important to spend some time to prioritize which of your indicators are most critical to the success of your business.

      Also consider, if one area is performing well and others have multiple poor indicators, how do you give the right support to optimize the results?

      Lastly, is it better to score slightly lower on multiple measures or perfect on most but failing badly on one or two?

      3.1.1 Determine criteria for prioritization

      Input

      • Business goals and objectives
      • IT goals and objectives
      • IT organizational structure

      Output

      • Documented scorecard remediation prioritization criteria

      Materials

      • Whiteboard or flip charts

      Participants

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      1 hour

      1. Identify any KPIs that are critical and cannot fail without high impact to your organization.
      2. Identify any KPIs that cannot fail for an extended period and document the time period.
      3. Rank the KPIs from most critical to least critical in the IT Metrics Library.
      4. Look at the owner accountable for the performance of each KPI. If there are any large groups, reassess the ownership or rank.
      5. Periodically review the criteria to see if they’re aligned with meeting current business goals.

      3.1.2 Identify low-performing indicators

      Input

      • Overall scorecard
      • Overall scorecard (previous period)
      • IT Metrics Library

      Output

      • List of low-performing indicators that need remediation
      • Planned actions to improve performance

      Materials

      • Whiteboard or flip charts

      Participants

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      1 hour

      1. Review the overall scorecard for the current period. List any KPIs that are not meeting the target for the current month in the “Action Plan” tab of the IT Metrics Library.
      2. Compare current month to previous month. List any KPIs that are moving away from the long-term target documented in the tool IT Metrics Library.
      3. Revise the target in the IT Metrics Library as business needs change.

      3.1.3 Prioritize low-performing indicators

      Input

      • IT Metrics Library

      Output

      • Prioritized list of planned actions for low-performing indicators

      Materials

      • IT Metrics Library

      Participants

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators
      • Task owners

      1 hour

      1. Look through the list of new and outstanding planned actions in the “Action Plan” tab of the IT Metrics Library, review progress, and prioritize outstanding items.
      2. Compare the list that needs remediation with the rank in the data entry tab.
      3. Adjust the priority of the outstanding and new actions to reflect the business needs.

      Step 3.2

      Review suggested actions

      Activities

      3.2.1 Review suggested actions in the IT Metrics Library

      Create the Action Plan

      Step 3.1 – Prioritize low-performing indicators

      Step 3.2 – Review suggested actions

      Step 3.3 – Develop the action plan

      This step will walk you through the following activities:

      Reviewing the suggested actions in the IT Metrics Library

      This step involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Outcomes of this step

      An idea of possible suggested actions

      Take Action

      Knowing where you are underperforming is only half the battle. You need to act!

      • So far you have identified which indicators will tell you whether or not your team is performing and which indicators are most critical to your business success.
      • Knowing is the first step, but things will not improve without some kind of action.
      • Sometimes the action needed to course-correct is small and simple, but sometimes it is complicated and may take a long time.
      • Utilize the diverse ideas of your team to find solutions to underperforming indicators.
      • If you don’t have a viable simple solution, leverage the IT Metrics Library, which suggests high-level action needed to improve each indicator. If you need additional information, use your Info-Tech membership to review the recommended research.

      3.2.1 Review suggested actions in the IT Metrics Library

      Input

      • IT Metrics Library

      Output

      • Suggested actions

      Materials

      • IT Metrics Library

      Participants

      • Process area owners
      • Metrics program owners and administrators
      • Task owners

      0.5 hours

      1. For each of your low-performing indicators, review the suggested action and related research in the IT Metrics Library.

      Step 3.3

      Develop the action plan

      Activities

      3.3.1 Document planned actions

      3.3.2 Assign ownership of actions

      3.3.3 Determine timeline of actions

      3.3.4 Review past action status

      Create the action plan

      Step 3.1 – Prioritize low- performing indicators

      Step 3.2 – Review suggested actions

      Step 3.3 – Develop the action plan

      This step will walk you through the following activities:

      Using the action plan tool to document the expected actions for low-performing indicators

      Assigning an owner and expected due date for the action

      Reviewing past action status for accountability

      This step involves the following participants:

      • Senior IT leadership
      • Process area owners
      • Metrics program owners and administrators

      Outcomes of this step

      An action plan to invoke improved performance

      3.3.1 Document planned actions

      Input

      • IT Metrics Library

      Output

      • Planned actions

      Materials

      • IT Metrics Library

      Participants

      • Process area owners
      • Metrics program owners and administrators
      • Task owners

      1 hour

      1. Decide on the action you plan to take to bring the indicator in line with expected performance and document the planned action in the “Action Plan” tab of the IT Metrics Library.

      Info-Tech Insight

      For larger initiatives try to break the task down to what is likely manageable before the next review. Seeing progress can motivate continued action.

      3.3.2 Assign ownership of actions

      Input

      • IT Metrics Library

      Output

      • Identified owners for each action

      Materials

      • IT Metrics Library

      Participants

      • Process area owners
      • Metrics program owners and administrators
      • Task owners

      0.5 hours

      1. For each unassigned task, assign clear ownership for completion of the task.
      2. The task owner should be the person accountable for the task.

      Info-Tech Insight

      Assigning clear ownership can promote accountability for progress.

      3.3.3 Determine timeline of actions

      Input

      • IT Metrics Library

      Output

      • Expected timeline for each action

      Materials

      • IT Metrics Library

      Participants

      • Process area owners
      • Metrics program owners and administrators
      • Task owners

      0.5 hours

      1. For each task, agree on an estimated target date for completion.

      Info-Tech Insight

      If the target completion date is too far in the future, break the task into manageable chunks.

      3.3.4 Review past action status

      Input

      • IT Metrics Library

      Output

      • Complete action plan for increased performance

      Materials

      • IT Metrics Library

      Participants

      • Process area owners
      • Metrics program owners and administrators
      • Task owners

      0.5 hours

      1. For each task, review the progress since last review.
      2. If desired progress is not being made, adjust your plan based on your organizational constraints.

      Info-Tech Insight

      Seek to understand the reasons that tasks are not being completed and problem solve for creative solutions to improve performance.

      Measure the value of your KPI program

      KPIs only produce value if they lead to action

      • Tracking the performance of key indicators is the first step, but value only comes from taking action based on this information.
      • Keep track of the number of action items that come out of your KPI review and how many are completed.
      • If possible, keep track of the time or money saved through completing the action items.

      Keeping track of the number of actions identified and completed is a low overhead measure.

      Tracking time or money saved is higher overhead but also higher value.

      The image is a chart titled KPI benefits. It includes a legend indicating that blue bars are for Actions identified, purple bars are for Actions completed, and the yellow line is for Time/money saved. The graph shows Q1-Q4, indicating an increase in all areas across the quarters.

      Establish Baseline Metrics

      Baseline metrics will be improved through:

      1. Identifying actions needed to remediate poor-performing KPIs
      2. Associating time and/or money savings as a result of actions taken
      Metric Current Goal
      Number of actions identified per month as a result of KPI review 0 TBD
      $ saved through actions taken due to KPI review 0 TBD
      Time saved through actions taken due to KPI review 0 TBD

      Summary of Accomplishment

      Problem Solved

      Through this project we have identified typical key performance indicators that are important to your organization’s effective management of IT.

      You’ve populated the IT Management Dashboard as a simple method to display the results of your selected KPIs.

      You’ve also established a regular review process for your KPIs and have a method to track the actions that are needed to improve performance as a result of the KPI review. This should allow you to hold individuals accountable for improvement efforts.

      You can also measure the effectiveness of your KPI program by tracking how many actions are identified as a result of the review. Ideally you can also track the money and time savings.

      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:

      Select the KPIs for your organization

      Examine the benefits of the KPIs suggested in the IT Metrics Library and help selecting those that will drive performance for your maturity level.

      Build an action plan

      Discuss options for identifying and executing actions that result from your KPI review. Determine how to set up the discipline needed to make the most of your KPI review program.

      Research Contributors and Experts

      Valence Howden

      Principal Research Director, CIO – Service Management Info-Tech Research Group

      • Valence has extensive experience in helping organizations be successful through optimizing how they govern themselves, how they design and execute strategies, and how they drive service excellence in all work.

      Tracy-Lynn Reid

      Practice Lead, CIO – People & Leadership Info-Tech Research Group

      • Tracy-Lynn covers key topics related to People & Leadership within an information technology context.

      Fred Chagnon

      Practice Lead, Infrastructure & Operations Info-Tech Research Group

      • Fred brings extensive practical experience in all aspects of enterprise IT Infrastructure, including IP networks, server hardware, operating systems, storage, databases, middleware, virtualization and security.

      Aaron Shum

      Practice Lead, Security, Risk & Compliance Info-Tech Research Group

      • With 20+ years of experience across IT, InfoSec, and Data Privacy, Aaron currently specializes in helping organizations implement comprehensive information security and cybersecurity programs as well as comply with data privacy regulations.

      Cole Cioran

      Practice Lead, Applications and Agile Development Info-Tech Research Group

      • Over the past twenty-five years, Cole has developed software; designed data, infrastructure, and software solutions; defined systems and enterprise architectures; delivered enterprise-wide programs; and managed software development, infrastructure, and business systems analysis practices.

      Barry Cousins

      Practice Lead, Applications – Project and Portfolio Mgmt. Info-Tech Research Group

      • Barry specializes in Project Portfolio Management, Help/Service Desk, and Telephony/Unified Communications. He brings an extensive background in technology, IT management, and business leadership.

      Jack Hakimian

      Vice President, Applications Info-Tech Research Group

      • Jack has close to 25 years of Technology and Management Consulting experience. He has served multi-billion-dollar organizations in multiple industries, including Financial Services and Telecommunications. Jack also served several large public sector institutions.

      Vivek Mehta

      Research Director, CIO Info-Tech Research Group

      • Vivek publishes on topics related to digital transformation and innovation. He is the author of research on Design a Customer-Centric Digital Operating Model and Create Your Digital Strategy as well as numerous keynotes and articles on digital transformation.

      Carlos Sanchez

      Practice Lead, Enterprise Applications Info-Tech Research Group

      • Carlos has a breadth of knowledge in enterprise applications strategy, planning, and execution.

      Andy Neill

      Practice Lead, Enterprise Architecture, Data & BI Info-Tech Research Group

      • Andy has extensive experience in managing technical teams, information architecture, data modeling, and enterprise data strategy.

      Michael Fahey

      Executive Counselor Info-Tech Research Group

      • As an Executive Counselor, Mike applies his decades of business experience and leadership, along with Info-Tech Research Group’s resources, to assist CIOs in delivering outstanding business results.

      Related Info-Tech Research

      Develop Meaningful Service Metrics to Ensure Business and User Satisfaction

      • Reinforce service orientation in your IT organization by ensuring your IT metrics generate value-driven resource behavior.

      Use Applications Metrics That Matter

      • It all starts with quality and customer satisfaction.

      Take Control of Infrastructure Metrics

      • Master the metrics maze to help make decisions, manage costs, and plan for change.

      Bibliography

      Bach, Nancy. “How Often Should You Measure Your Organization's KPIs?” EON, 26 June 2018. Accessed Jan. 2020.

      “The Benefits of Tracking KPIs – Both Individually and for a Team.” Hoopla, 30 Jan. 2017. Accessed Jan. 2020.

      Chepul, Tiffany. “Top 22 KPI Examples for Technology Companies.” Rhythm Systems, Jan. 2020. Accessed Jan. 2020.

      Cooper, Larry. “CSF's, KPI's, Metrics, Outcomes and Benefits” itSM Solutions. 5 Feb. 2010. Accessed Jan 2020.

      “CUC Report on the implementation of Key Performance Indicators: case study experience.” Committee of University Chairs, June 2008. Accessed Jan 2020.

      Harris, Michael, and Bill Tayler. “Don’t Let Metrics Undermine Your Business.” HBR, Sep.–Oct 2019. Accessed Jan. 2020.

      Hatari, Tim. “The Importance of a Strong KPI Dashboard.” TMD Coaching. 27 Dec. 2018. Accessed Jan. 2020.

      Roy, Mayu, and Marian Carter. “The Right KPIs, Metrics for High-performing, Cost-saving Space Management.” CFI, 2013. Accessed Jan 2020.

      Schrage, Michael, and David Kiron. “Leading With Next-Generation Key Performance Indicators.” MIT Sloan Management Review, 26 June 2018. Accessed Jan. 2020.

      Setijono, Djoko, and Jens J. Dahlgaard. “Customer value as a key performance indicator (KPI) and a key improvement indicator (KII)” Emerald Insight, 5 June 2007. Accessed Jan 2020.

      Skinner, Ted. “Balanced Scorecard KPI Examples: Comprehensive List of 183 KPI Examples for a Balanced Scorecard KPI Dashboard (Updated for 2020).” Rhythm Systems, Jan. 2020. Accessed Jan 2020.

      Wishart, Jessica. “5 Reasons Why You Need The Right KPIs in 2020” Rhythm Systems, 1 Feb. 2020. Accessed Jan. 2020.

      Create a Buyer Persona and Journey

      • Buy Link or Shortcode: {j2store}558|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
      • Contacts fail to convert to leads because messaging fails to resonate with buyers.
      • Products fail to reach targets given shallow understanding of buyer needs.
      • Sellers' emails go unopened and attempts at discovery fail due to no understanding of buyer challenges, pain points, and needs.

      Our Advice

      Critical Insight

      • Marketing leaders in possession of well-researched and up-to-date buyer personas and journeys dramatically improve product market fit, lead gen, and sales results.
      • Success starts with product, marketing, and sales alignment on targeted personas.
      • Speed to deploy is enabled via initial buyer persona attribute discovery internally.
      • However, ultimate success requires buyer interviews, especially for the buyer journey.
      • Leading marketers update journey maps every six months as disruptive events such as COVID-19 and new media and tech platform advancements require continual innovation.

      Impact and Result

      • Reduce time and treasure wasted chasing the wrong prospects.
      • Improve product-market fit.
      • Increase open and click-through rates in your lead gen engine.
      • Perform more effective sales discovery and increase eventual win rates.

      Create a Buyer Persona and Journey Research & Tools

      Start here – read the Executive Brief

      Our Executive Brief summarizes the challenges faced when buyer persona and journeys are ill-defined. It describes the attributes of, and the benefits that accrue from, a well-defined persona and journey and the key steps to take to achieve success.

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

      1. Drive an aligned initial draft of buyer persona

      Define and align your team on target persona, outline steps to capture and document a robust buyer persona and journey, and capture current team buyer knowledge.

      • Buyer Persona Creation Template
      • Buyer Persona and Journey Interview Guide and Data Capture Tool

      2. Interview buyers and validate persona and journey

      Hold initial buyer interviews, test initial results, and continue with interviews.

      3. Prepare communications and educate stakeholders

      Consolidate interview findings, present to product, marketing, and sales teams. Work with them to apply to product design, marketing launch/campaigning, and sales and customer success enablement.

      • Buyer Persona and Journey Summary Template
      [infographic]

      Workshop: Create a Buyer Persona and Journey

      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 Align Team, Identify Persona, and Document Current Knowledge

      The Purpose

      Organize, drive alignment on target persona, and capture initial views.

      Key Benefits Achieved

      Steering committee and project team roles and responsibilities clarified.

      Product, marketing, and sales aligned on target persona.

      Build initial team understanding of persona.

      Activities

      1.1 Outline a vision for buyer persona and journey creation and identify stakeholders.

      1.2 Identify buyer persona choices and settle on an initial target.

      1.3 Document team knowledge about buyer persona (and journey where possible).

      Outputs

      Documented steering committee and working team

      Executive Brief on personas and journey

      Personas and initial targets

      Documented team knowledge

      2 Validate Initial Work and Identify Buyer Interviewees

      The Purpose

      Build list of buyer interviewees, finalize interview guide, and validate current findings with analyst input.

      Key Benefits Achieved

      Interview efficiently using 75-question interview guide.

      Gain analyst help in persona validation, reducing workload.

      Activities

      2.1 Share initial insights with covering industry analyst.

      2.2 Hear from industry analyst their perspectives on the buyer persona attributes.

      2.3 Reconcile differences; update “current understanding.”

      2.4 Identify interviewee types by segment, region, etc.

      Outputs

      Analyst-validated initial findings

      Target interviewee types

      3 Schedule and Hold Buyer Interviews

      The Purpose

      Validate current persona hypothesis and flush out those attributes only derived from interviews.

      Key Benefits Achieved

      Get to a critical mass of persona and journey understanding quickly.

      Activities

      3.1 Identify actual list of 15-20 interviewees.

      3.2 Hold interviews and use interview guides over the course of weeks.

      3.3 Hold review session after initial 3-4 interviews to make adjustments.

      3.4 Complete interviews.

      Outputs

      List of interviewees; calls scheduled

      Initial review – “are you going in the right direction?”

      Completed interviews

      4 Summarize Findings and Provide Actionable Guidance to Colleagues

      The Purpose

      Summarize persona and journey attributes and provide activation guidance to team.

      Key Benefits Achieved

      Understanding of product market fit requirements, messaging, and marketing, and sales asset content.

      Activities

      4.1 Summarize findings.

      4.2 Create action items for supporting team, e.g. messaging, touch points, media spend, assets.

      4.3 Convene steering committee/executives and working team for final review.

      4.4 Schedule meetings with colleagues to action results.

      Outputs

      Complete findings

      Action items for team members

      Plan for activation

      5 Measure Impact and Results

      The Purpose

      Measure results, adjust, and improve.

      Key Benefits Achieved

      Activation of outcomes; measured results.

      Activities

      5.1 Review final copy, assets, launch/campaign plans, etc.

      5.2 Develop/review implementation plan.

      5.3 Reconvene team to review results.

      Outputs

      Activation review

      List of suggested next steps

      Further reading

      Create a Buyer Persona and Journey

      Make it easier to market, sell, and achieve product-market fit with deeper buyer understanding.

      EXECUTIVE BRIEF

      Executive Summary

      Your Challenge

      B2B marketers without documented personas and journeys often experience the following:

      • Contacts fail to convert to leads because messaging fails to resonate with buyers.
      • Products fail to reach targets given shallow understanding of buyer needs.
      • Sellers’ emails go unopened, and attempts at discovery fail due to no understanding of buyer challenges, pain points, and needs.

      Without a deeper understanding of buyer needs and how they buy, B2B marketers will waste time and precious resources targeting the incorrect personas.

      Common Obstacles

      Despite being critical elements, organizations struggle to build personas due to:

      • A lack of alignment and collaboration among marketing, product, and sales.
      • An internal focus; or a lack of true customer centricity.
      • A lack of tools and techniques for building personas and buyer journeys.

      In today’s Agile development environment, combined with the pressure to generate revenues quickly, high tech marketers often skip the steps necessary to go deeper to build buyer understanding.

      SoftwareReviews’ Approach

      With a common framework and target output, clients will:

      • Align marketing, sales, and product, and collaborate together to share current knowledge on buyer personas and journeys.
      • Target 12-15 customers and prospects to interview and validate insights. Share that with customer-facing staff.
      • Activate the insights for more customer-centric lead generation, product development, and selling.

      Clients who activate findings from buyer personas and journeys will see a 50% results improvement.

      SoftwareReviews Insight:
      Buyer personas and buyer journeys are essential ingredients in go-to-market success, as they inform for product, marketing, sales, and customer success who we are targeting and how to engage with them successfully.

      Buyer personas and journeys: A go-to-market critical success factor

      Marketers – large and small – will fail to optimize product-market fit, lead generation, and sales effectiveness without well-defined buyer personas and a buyer journey.

      Critical Success Factors of a Successful G2M Strategy:

      • Opportunity size and business case
      • Buyer personas and journey
      • Competitively differentiated product hypothesis
      • Buyer-validated commercial concept
      • Sales revenue plan and program cost budget
      • Consolidated communications to steering committee

      Jeff Golterman, Managing Director, SoftwareReviews Advisory

      “44% of B2B marketers have already discovered the power of Personas.”
      – Hasse Jansen, Boardview.io!, 2016

      Documenting buyer personas enables success beyond marketing

      Documenting buyer personas has several essential benefits to marketing, sales, and product teams:

      • Achieve a better understanding of your target buyer – by building a detailed buyer persona for each type of buyer and keeping it fresh, you take a giant step toward becoming a customer-centric organization.
      • Team alignment on a common definition – will happen when you build buyer personas collaboratively and among those teams that touch the customer.
      • Improved lead generation – increases dramatically when messaging and marketing assets across your lead generation engine better resonate with buyers because you have taken the time to understand them deeply.
      • More effective selling – is possible when sellers apply persona development output to their interactions with prospects and customers.
      • Better product-market fit – increases when product teams more deeply understand for whom they are designing products. Documenting buyer challenges, pain points, and unmet needs gives product teams what they need to optimize product adoption.

      “It’s easier buying gifts for your best friend or partner than it is for a stranger, right? You know their likes and dislikes, you know the kind of gifts they’ll have use for, or the kinds of gifts they’ll get a kick out of. Customer personas work the same way, by knowing what your customer wants and needs, you can present them with content targeted specifically to their wants and needs.”
      – Emma Bilardi, Product Marketing Alliance, 2020

      Buyer understanding activates just about everything

      Without the deep buyer insights that persona and journey capture enables, marketers are suboptimized.

      Buyer Persona and Journey

      • Product design
      • Customer targeting
      • Personalization
      • Messaging
      • Content marketing
      • Lead gen & scoring
      • Sales Effectiveness
      • Customer retention

      “Marketing eutopia is striking the all-critical sweet spot that adds real value and makes customers feel recognized and appreciated, while not going so far as to appear ‘big brother’. To do this, you need a deep understanding of your audience coming from a range of different data sets and the capability to extract meaning.”
      – Plexure, 2020

      Does your organization need buyer persona and journey updating?

      “Yes,” if experiencing one or more key challenges:

      • Sales time is wasted on unqualified leads
      • Website abandon rates are high
      • Lead gen engine click-through rates are low
      • Ideal customer profile is ill defined
      • Marketing asset downloads are low
      • Seller discovery with prospects is ineffective
      • Sales win/loss rates drop due to poor product-market fit
      • Higher than desired customer churn

      SoftwareReviews Advisory Insight:
      Marketers developing buyer personas and journeys that lack agreement among Marketing, Sales, and Product of personas to target will squander precious time and resources throughout the customer targeting and acquisition process.

      Outcomes and benefits

      Building your buyer persona and journey using our methodology will enable:

      • Greater stakeholder alignment – when marketing, product, and sales agree on personas, less time is wasted on targeting alternate personas.
      • Improved product-market fit – when buyers see both pain-relieving features and value-based pricing, “because you asked vs. guessed,” win rates increase.
      • Greater open and click-through rates – because you understood buyer pain points and motivations for solution seeking, you’ll see higher visits and engagement with your lead gen engine, and because you asked “what asset types do you find most helpful” your CTAs become ”lead-gen magnets” because you’ve offered the right asset types in your content marketing strategy.
      • More qualified leads – because you defined a more accurate ideal customer profile (ICP) and your lead scoring algorithm has improved, sellers see more qualified leads.
      • Increased sales cycle velocity – since you learned from personas their content and engagement preferences and what collateral types they need during the down-funnel sales discussions, sales calls are more productive and sales cycles shrink.

      Our methodology for buyer persona and journey creation

      1. Document Team Knowledge of Buyer Persona and Drive Alignment 2. Interview Target Buyer Prospects and Customers 3. Create Outputs and Apply to Marketing, Sales, and Product
      Phase Steps
      1. Outline a vision for buyer persona and journey creation and identify stakeholders.
      2. Pull stakeholders together, identify initial buyer persona, and begin to document team knowledge about buyer persona (and journey where possible).
      3. Validate with industry and marketing analyst’s initial buyer persona, and identify list of buyer interviewees.
      1. Hold interviews and document and share findings.
      2. Validate initial drafts of buyer persona and create initial documented buyer journey. Review findings among key stakeholders, steering committee, and supporting analysts.
      3. Complete remaining interviews.
      1. Summarize findings.
      2. Convene steering committee/exec. and working team for final review.
      3. Communicate to key stakeholders in product, marketing, sales, and customer success for activation.
      Phase Outcomes
      1. Steering committee and team selection
      2. Team insights about buyer persona documented
      3. Buyer persona validation with industry and marketing analysts
      4. Sales, marketing, and product alignment
      1. Interview guide
      2. Target interviewee list
      3. Buyer-validated buyer persona
      4. Buyer journey documented with asset types, channels, and “how buyers buy” fully documented
      1. Education deck on buyer persona and journey ready for use with all stakeholders: product, field marketing, sales, executives, customer success, partners
      2. Activation will update product-market fit, optimize lead gen, and improve sales effectiveness

      Our approach provides interview guides and templates to help rebuild buyer persona

      Our methodology will enable you to align your team on why it’s important to capture the most important attributes of buyer persona including:

      • Functional – helps you find and locate your target personas
      • Emotive – deepens team understanding of buyer initiatives, motivations for seeking alternatives, challenges they face, pain points for your offerings to address, and terminology that describes the “space”
      • Solution – enables greater product market fit
      • Behavioral – clarifies how to communicate with personas and understand their content preferences
      Functional – “to find them”
      Job Role Title Org. Chart Dynamics Buying Center Firmographics
      Emotive – “what they do and jobs to be done”
      Initiatives: What programs/projects the persona is tasked with and their feelings and aspirations about these initiatives. Motivations? Build credibility? Get promoted? Challenges: Identify the business issues, problems, and pain points that impede attainment of objectives. What are their fears, uncertainties, and doubts about these challenges? Buyer Need: They may have multiple needs; which need is most likely met with the offering? Terminology: What are the keywords/phrases they organically use to discuss the buyer need or business issue?
      Decision Criteria – “how they decide”
      Buyer Role: List decision-making criteria and power level. The five common buyer roles are champion, influencer, decision maker, user, and ratifier (purchaser/negotiator). Evaluation and Decision Criteria: Which lens – strategic, financial, or operational – does the persona evaluate the impact of purchase through?
      Solution Attributes – “what does the ideal solution look like”
      Steps in “Jobs to Be Done” Elements of the “Ideal Solution” Business outcomes from ideal solution Opportunity scope; other potential users Acceptable price for value delivered Alternatives that see consideration Solution sourcing: channel, where to buy
      Behavioral Attributes – “how to approach them successfully”
      Content Preferences: List the persona’s content preferences – blog, infographic, demo, video – vs. long-form assets (e.g. white paper, presentation, analyst report). Interaction Preferences: Which are preferred among in-person meetings, phone calls, emails, videoconferencing, conducting research via Web, mobile, and social? Watering Holes: Which physical or virtual places do they go to network or exchange info with peers (e.g. LinkedIn)?

      Buyer journeys are constantly shifting

      If you didn’t remap buyer journeys in 2021, you may be losing to competitors that did. Leaders remap buyer journey frequently.

      • The multi-channel buyer journey is constantly changing. Today’s B2B buyer uses industry research sites, vendor content marketing assets, software reviews sites, contacts with vendor salespeople, events participation, peer networking, consultants, emails, social media sites, and electronic media to research purchasing decisions.
      • COVID-19 has dramatically decreased face-to-face interaction. We estimate a B2B buyer spent 20-25% more time online in 2021 than pre-COVID-19 researching software buying decisions. This has diminished the importance of face-to-face selling and given dramatic rise to digital selling and outbound marketing.
      • Content marketing has exploded, but without mapping the buyer journey and knowing where – by channel –and when – by buyer journey step – to offer content marketing assets, we will fail to convert prospects into buyers.

      “~2/3 of [B2B] buyers prefer remote human interactions or digital self-service.” And during Aug. ‘20 to Feb. ‘21, use of digital self-service to interact with sales reps leapt by more than 10% for both researching and evaluating new suppliers.”
      – Liz Harrison, Dennis Spillecke, Jennifer Stanley, and Jenny Tsai McKinsey & Company, 2021

      SoftwareReviews Advisory Insight:
      Marketers are advised to update their buyer journey annually and with greater frequency when the human vs. digital mix is affected due to events such as COVID-19 and as emerging media such as AR shifts asset-type usage and engagement options.

      Our approach helps you define the buyer journey

      Because marketing leaders need to reach buyers through the right channel with the right message at the right time during their decision cycle, you’ll benefit by using questionnaires that enable you to build the below easily and quickly.

      You’ll be more successful by following our overall guidance

      Overarching insight

      Buyer personas and buyer journeys are essential ingredients in go-to-market success, as they inform for product, marketing, sales, and customer success who we are targeting and how to engage with them successfully.

      Align Your Team

      Marketers developing buyer personas and journeys that lack agreement among Marketing, Sales, and Product of personas to target will squander precious time and resources throughout the customer targeting and acquisition process.

      Jump-Start Persona Development

      Marketing leaders leverage the buyer persona knowledge not only from in-house experts in areas such as sales and executives but from analysts that speak with their buyers each and every day.

      Buyer Interviews Are a Must

      While leaders will get a fast start by interviewing sellers, executives, and analysts, you will fail to craft the right messages, build the right marketing assets, and design the best buyer journey if you skip buyer interviews.

      Watch for Disruption

      Leaders will update their buyer journey annually and with greater frequency when the human vs. digital mix is effected due to events such as COVID-19 and as emerging media such as AR and VR shifts the way buyers engage.

      Advanced Buyer Journey Discovery

      Digital marketers that ramp up lead gen engine capabilities to capture “wins” and measure engagement back through the lead gen and nurturing engines will build a more data-driven view of the buyer journey. Target to build this advanced capability in your initial design.

      Tools and templates to speed your success

      This blueprint is accompanied by supporting deliverables to help you gather team insights, interview customers and prospects, and summarize results for ease in communications.

      To support your buyer persona and journey creation, we’ve created the enclosed tools

      Buyer Persona Creation Template

      A PowerPoint template to aid the capture and summarizing of your team’s insights on the buyer persona.

      Buyer Persona and Journey Interview Guide and Data Capture Tool

      For interviewing customers and prospects, this tool is designed to help you interview personas and summarize results for up to 15 interviewees.

      Buyer Persona and Journey Summary Template

      A PowerPoint template into which you can drop your buyer persona and journey interviewees list and summary findings.

      SoftwareReviews offers two 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."

      The "do-it-yourself" step-by-step instructions begin with Phase 1.

      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."

      A Guided Implementation is a series of analysts inquiries with you and your team.

      Diagnostics and consistent frameworks are used throughout each option.

      Guided Implementation

      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.

      What does our GI on buyer persona and journey mapping look like?

      Drive an Aligned Initial Draft of Buyer Persona

      • Call #1: Collaborate on vision for buyer persona and the buyer journey. Review templates and sample outputs. Identify your team.
      • Call #2: Review work in progress on capturing working team knowledge of buyer persona elements.
      • Call #3: (Optional) Review Info-Tech’s research-sourced persona insights.
      • Call #4: Validate the persona WIP with Info-Tech analysts. Review buyer interview approach and target list.

      Interview Buyers and Validate Persona and Journey

      • Call #5: Revise/review interview guide and final interviewee list; schedule interviews.
      • Call #6: Review interim interview finds; adjust interview guide.
      • Call #7: Use interview findings to validate/update persona and build journey map.
      • Call #8: Add supporting analysts to final stakeholder review.

      Prepare Communications and Educate Stakeholders

      • Call #9: Review output templates completed with final persona and journey findings.
      • Call #10: Add supporting analysts to stakeholder education meetings for support and help with addressing questions/issues.

      Workshop overview

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

      Day1 Day 2 Day 3 Day 4 Day 5
      Align Team, Identify Persona, and Document Current Knowledge Validate Initial Work and Identify Buyer Interviewees Schedule and Hold Buyer interviews Summarize Findings and Provide Actionable Guidance to Colleagues Measure Impact and Results
      Activities

      1.1 Outline a vision for buyer persona and journey creation and identify stakeholders.

      1.2 Identify buyer persona choices and settle on an initial target.

      1.3 Document team knowledge about buyer persona (and journey where possible).

      2.1 Share initial insights with covering industry analyst.

      2.2 Hear from industry analyst their perspectives on the buyer persona attributes.

      2.3 Reconcile differences; update “current understanding.”

      2.4 Identify interviewee types by segment, region, etc.

      3.1 Identify actual list of 15-20 interviewees.

      A gap of up to a week for scheduling of interviews.

      3.2 Hold interviews and use interview guides (over the course of weeks).

      3.3 Hold review session after initial 3-4 interviews to make adjustments.

      3.4 Complete interviews.

      4.1 Summarize findings.

      4.2 Create action items for supporting team, e.g. messaging, touch points, media spend, assets.

      4.3 Convene steering committee/exec. and working team for final review.

      4.4 Schedule meetings with colleagues to action results.

      5.1 Review final copy, assets, launch/campaign plans, etc.

      5.2 Develop/review implementation plan.

      A period of weeks will likely intervene to execute and gather results.

      5.3 Reconvene team to review results.

      Deliverables
      1. Documented steering committee and working team
      2. Executive Brief on personas and journey
      3. Personas and initial targets
      4. Documented team knowledge
      1. Analyst-validated initial findings
      2. Target interviewee types
      1. List of interviewees; calls scheduled
      2. Initial review – “are we going in the right direction?”
      3. Completed interviews
      1. Complete findings
      2. Action items for team members
      3. Plan for activation
      1. Activation review
      2. List of suggested next steps

      Phase 1
      Drive an Aligned Initial Draft of Buyer Persona

      This Phase walks you through the following activities:

      • Develop an understanding of what comprises a buyer persona and journey, including their importance to overall go-to-market strategy and execution.
      • Sample outputs.

      This Phase involves the following stakeholders:

      • Program leadership
      • Product Marketing
      • Product Management
      • Representative(s) from Sales
      • Executive Leadership

      1.1 Establish the team and align on shared vision

      Input

      • Typically a joint recognition that buyer personas have not been fully documented.
      • Identify working team members/participants (see below), and an executive sponsor.

      Output

      • Communication of team members involved and the make-up of steering committee and working team
      • Alignment of team members on a shared vision of “Why Build Buyer Personas and Journey” and what key attributes define both.

      Materials

      • N/A

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • CMO/Sponsoring Executive Working Team – typically representatives in Product Marketing, Product Management, and Sales
      • SoftwareReviews marketing analyst

      60 minutes

      1. Schedule inquiry with working team members and walk the team through the Buyer Persona and Journey Executive Brief PowerPoint presentation.
      2. Optional: Have the (SoftwareReviews Advisory) SRA analyst walk the team through the Buyer Persona and Journey Executive Brief PowerPoint presentation as part of your session.

      Review the Create a Buyer Persona Executive Brief (Slides 3-14)

      1.2 Document team knowledge of buyer persona

      Input

      • Working team member knowledge

      Output

      • Initial draft of your buyer persona

      Materials

      • Buyer Persona Creation Template

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • CMO/Sponsoring Executive (optional)
      • Working Team – typically representatives in Product Marketing, Product Management, and Sales

      2-3 sessions of 60 minutes each

      1. Schedule meeting with working team members and, using the Buyer Persona Template, lead the team in a discussion that documents current team knowledge of the target buyer persona.
      2. Lead the team to prioritize an initial, single, most important persona and to collaborate to complete the template (and later, the buyer journey). Once the team learns the process for working on the initial persona, the development of additional personas will become more efficient.
      3. Place the PowerPoint template in a shared drive for team collaboration. Expect to schedule several 60-minute meets. Quicken collaboration by encouraging team to “do their homework” by sharing persona knowledge within the shared drive version of the template. Your goal is to get to an initial agreed upon version that can be shared for additional validation with industry analyst(s) in the next step.

      Download the Buyer Persona Creation Template

      1.3 Validate with industry analysts

      Input

      • Identify gaps in persona from previous steps

      Output

      • Further validated buyer persona

      Materials

      • Bring your Buyer Persona Creation Template to the meeting to share with analysts

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • CMO/Sponsoring Executive (Optional)
      • Working Team – typically representatives in Product Marketing, Product Management, and Sales
      • Info-Tech analyst covering your product category and SoftwareReviews marketing analyst

      30 minutes

      1. Schedule meeting with working team members and discuss which persona areas require further validation from an Info-Tech analyst who has worked closely with those buyers within your persona.

      60 minutes

      1. Schedule an inquiry with the appropriate Info-Tech analyst and SoftwareReviews Advisory analyst to share current findings and see:
        1. Info-Tech analyst provide content feedback given what they know about your target persona and product category.
        2. SoftwareReviews Advisory analyst provide feedback on persona approach and to coach any gaps or important omissions.
      2. Tabulate results and update your persona summary. At this point you will likely require additional validation through interviews with customers and prospects.

      1.4 Identify interviewees and prepare for interviews

      Input

      • Identify segments within which you require persona knowledge
      • Understand your persona insight gaps

      Output

      • List of interviewees

      Materials

      • Interviewee recording template on following slide
      • Interview guide questions found within the Buyer Persona and Journey Interview Guide and data Capture Tool

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • Working Team – typically representatives in Product Marketing, Product Management, and Sales

      1-2 weeks

      1. Identify the types of customers and prospects that will best represent your target persona. Choose interviewees that when interviewed will inform key differences among key segments (geographies, company size, mix of customers and prospects, etc.).
      2. Recruit interviewees and schedule interviews for 45 minutes.
      3. Keep track of Interviewees using the slide following this one.
      4. In preparation for interviews, review the Buyer Persona and Journey Interview Guide and Data Capture Tool. Review the two sets of questions:
        1. Buyer Persona-Related – use to validate areas where you still have gaps in your persona, OR if you are starting with a blank persona and wish to build your personas entirely based on customer and prospect interviews.
        2. Buyer-Journey Related, which we will focus on in the next phase.

      Download the Buyer Persona and Journey Interview Guide and Data Capture Tool

      The image shows a table titled ‘Interviewee List.’ A note next to the title indicates: Here you will document your interviewee list and outreach plan. A note in the Segment column indicates: Ensure you are interviewing personas across segments that will give you the insights you need, e.g. by size, by region, mix of customers and prospects. A note in the Title column reads: Vary your title types up or down in the “buying center” if you are seeking to strengthen buying center dynamics understanding. A note in the Roles column reads: Vary your role types according to decision-making roles (decision maker, influencer, ratifier, coach, user) if you are seeking to strengthen decision-making dynamics understanding.

      Phase 2
      Interview Buyers and Validate Persona and Journey

      This Phase walks you through the following activities:

      • Developing final interview guide.
      • Interviewing buyers and customers.
      • Adjusting approach.
      • Validating buyer persona.
      • Crafting buyer journey
      • Gaining analyst feedback.

      This Phase involves the following stakeholders:

      • Program leadership
      • Product Marketing
      • Representative(s) from Sales

      2.1 Hold interviews

      Input

      • List of interviewees
      • Final list of questions

      Output

      • Buyer perspectives on their personas and buyer journeys

      Materials

      • Buyer Persona and Journey Interview Guide and data Capture Tool

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • Working Team – typically representatives in Product Marketing, Product Management, and Sales

      1-2 weeks

      1. Hold interviews and adjust your interviewing approach as you go along. Uncover where you are not getting the right answers, check with working team and analysts, and adjust.

      Download the Buyer Persona and Journey Interview Guide and Data Capture Tool

      2.2 Use interview findings to validate what’s needed for activation

      Input

      • List of interviewees
      • Final list of questions

      Output

      • Buyer perspectives on their personas and buyer journeys
      • Stakeholder feedback that actionable insights are resulting from interviews

      Materials

      • Buyer Persona Creation Template
      • Buyer Persona and Journey Interview Guide and Data Capture Tool

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • Working Team – typically representatives in Product Marketing, Product Management, and Sales
      • SoftwareReviews marketing analyst

      2 hours

      1. Convene your team, with marketing analysts, and test early findings: It’s wise to test initial interview results to check that you are getting the right insights to understand and validate key challenges, pain points, needs, and other vital areas pertaining to the buyer persona. Are the answers you are getting enabling you to complete the Summary slides for later communications and training for Sales?
      2. Check when doing buyer journey interviews that you are getting actionable answers that drive messaging, what asset types are needed, what the marketing channel mix is, and other vital insights to activate the results. Are the answers you are getting adequate to give guidance to campaigners, content marketers, and sales enablement?
      3. See the following slides for detailed questions that need to be answered satisfactorily by your team members that need to “activate” the results.

      Download the Buyer Persona and Journey Interview Guide and Data Capture Tool

      2.2.1 Are you getting what you need from interviews to inform the buyer persona?

      Test that you are on the right track:

      1. Are you getting the functional answers so you can guide sellers to the right roles? Can you guide marketers/campaigners to the right “Ideal Customer Profile” for lead scoring?
      2. Are you capturing the right emotive areas that will support message crafting? Solutioning? SEM/SEO?
      3. Are you capturing insights into “how they decide” so sellers are well informed on the decision-making dynamics?
      4. Are you getting a strong understanding of content, interaction preferences, and news and information sources so sellers can outreach more effectively, you can pinpoint media spend, and content marketing can create the right assets?
      Functional – “to find them”
      Job Role Title Org. Chart Dynamics Buying Center Firmographics
      Emotive – “what they do and jobs to be done”
      Initiatives: What programs/projects the persona is tasked with and their feelings and aspirations about these initiatives. Motivations? Build credibility? Get promoted? Challenges: Identify the business issues, problems, and pain points that impede attainment of objectives. What are their fears, uncertainties, and doubts about these challenges? Buyer Need: They may have multiple needs; which need is most likely met with the offering? Terminology: What are the keywords/phrases they organically use to discuss the buyer need or business issue?
      Decision Criteria – “how they decide”
      Buyer Role: List decision-making criteria and power level. The five common buyer roles are champion, influencer, decision maker, user, and ratifier (purchaser/negotiator). Evaluation and Decision Criteria: Which lens – strategic, financial, or operational – does the persona evaluate the impact of purchase through?
      Solution Attributes – “what does the ideal solution look like”
      Steps in “Jobs to Be Done” Elements of the “Ideal Solution” Business outcomes from ideal solution Opportunity scope; other potential users Acceptable price for value delivered Alternatives that see consideration Solution sourcing: channel, where to buy
      Behavioral Attributes – “how to approach them successfully”
      Content Preferences: List the persona’s content preferences – blog, infographic, demo, video – vs. long-form assets (e.g. white paper, presentation, analyst report). Interaction Preferences: Which are preferred among in-person meetings, phone calls, emails, videoconferencing, conducting research via Web, mobile, and social? Watering Holes: Which physical or virtual places do they go to network or exchange info with peers (e.g. LinkedIn)?

      2.2.2 Are you getting what you need from interviews to support the buyer journey?

      Our approach helps you define the buyer journey

      Because marketing leaders need to reach buyers through the right channel with the right message at the right time during their decision cycle, you’ll benefit by using questionnaires that enable you to build the below easily and quickly.

      2.3 Continue interviews

      Input

      • Final adjustments to list of interview questions

      Output

      • Final buyer perspectives on their personas and buyer journeys

      Materials

      • Buyer Persona Creation Template
      • Buyer Persona and Journey Interview Guide and data Capture Tool

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • Working Team – typically representatives in Product Marketing, Product Management, and Sales

      1-2 weeks

      1. Continue customer and prospect interviews.
      2. Ensure you are gaining the segment perspectives needed.
      3. Complete the “Summary” columns within the Buyer Persona and Journey Interview Guide and Data Capture Tool.

      Download the Buyer Persona and Journey Interview Guide and Data Capture Tool

      Phase 3
      Prepare Communications and Educate Stakeholders

      This Phase walks you through the following activities:

      • Creating outputs for key stakeholders
      • Communicating final findings and supporting marketing, sales, and product activation.

      This Phase involves the following stakeholders:

      • Program leadership
      • Product Marketing
      • Product Management
      • Sales
      • Field Marketing/Campaign Management
      • Executive Leadership

      3.1 Summarize interview results and convene full working team and steering committee for final review

      Input

      • Buyer persona and journey interviews detail

      Output

      • Buyer perspectives on their personas and buyer journeys

      Materials

      • Buyer Persona and Journey Interview Guide and Data Capture Tool
      • Buyer Persona and Journey Summary Template

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • CMO/Sponsoring Executive (Optional)
      • Working Team – typically representatives in Product Marketing, Product Management, and Sales
      • SoftwareReviews marketing analyst

      1-2 hours

      1. Summarize interview results within the Buyer Persona and Journey Summary Template.

      Download the Buyer Persona and Journey Interview Guide and Data Capture Tool

      Download the Buyer Persona and Journey Summary Template

      3.2 Convene executive steering committee and working team to review results

      Input

      • Buyer persona and journey interviews summary

      Output

      • Buyer perspectives on their personas and buyer journeys

      Materials

      • Buyer Persona and Journey Summary Template

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • Working Team – typically representatives in Product Marketing, Product Management, and Sales

      1-2 hours

      1. Present final persona and journey results to the steering committee/executives and to working group using the summary slides interview results within the Buyer Persona and Journey Summary Template to finalize results.

      Download the Buyer Persona and Journey Summary Template

      3.3 Convene stakeholder meetings to activate results

      Input

      • Buyer persona and journey interviews summary

      Output

      Activation of key learnings to drive:

      • Better product –market fit
      • Lead gen
      • Sales effectiveness
      • Awareness

      Materials

      • Buyer Persona and Journey Summary Template

      Participants

      • Initiative Manager – individual leading the buyer persona and journey initiative
      • Working Team – typically representatives in Product Marketing, Product Management, and Sales
      • Stakeholder team members (see left)

      4-5 hours

      Present final persona and journey results to each stakeholder team. Key presentations include:

      1. Product team to validate product market fit.
      2. Content marketing to provide messaging direction for the creation of awareness and lead gen assets.
      3. Campaigners/Field Marketing for campaign-related messaging and to identify asset types required to be designed and delivered to support the buyer journey.
      4. Social media strategists for social post copy, and PR for other awareness-building copy.
      5. Sales enablement/training to enable updating of sales collateral, proposals, and sales training materials. Sellers to help with their targeting, prospecting, and crafting of outbound messaging and talk tracks.

      Download the Buyer Persona and Journey Summary Template

      Summary of Accomplishment

      Problem Solved

      With the help of this blueprint, you have deepened your and your colleagues’ buyer understanding at both the persona “who they are” level and the buyer journey “how do they buy” level. You are among the minority of marketing leaders that have fully documented a buyer persona and journey – congratulations!

      The benefits of having led your team through the process are significant and include the following:

      • Better alignment of customer/buyer-facing teams such as in product, marketing, sales, and customer success.
      • Messaging that can be used by marketing, sales, and social teams that will resonate with buyer initiatives, pain points, sought-after “pain relief,” and value.
      • Places in the digital and physical universe where your prospects “hang out” so you can optimize your media spend.
      • More effective use of marketing assets and sales collateral that align with the way your prospect needs to consume information throughout their buyer journey to make a decision in your solution area.

      And by capturing and documenting your buyer persona and journey even for a single buyer type, you have started to build the “institutional strength” to apply the process to other roles in the decision-making process or for when you go after new and different buyer types for new products. And finally, by bringing your team along with you in this process, you have also led your team in becoming a more customer-focused organization – a strategic shift that all organizations should pursue.

      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 Software Reviews Research

      Optimize Lead Generation With Lead Scoring

      • Save time and money and improve your sales win rates when you apply our methodology to score contacts with your lead gen engine more accurately and pass better qualified leads over to your sellers.
      • Our methodology teaches marketers to develop your own lead scoring approach based upon lead/contact profile vs. your Ideal Customer Profile (ICP) and scores contact engagement. Applying the methodology to arrive at your own approach to scoring will mean reduced lead gen costs, higher conversion rates, and increased marketing-influenced wins.

      Bibliography

      Bilardi, Emma. “How to Create Buyer Personas.” Product Marketing Alliance, July 2020. Accessed Dec. 2021.

      Harrison, Liz, Dennis Spillecke, Jennifer Stanley, and Jenny Tsai. “Omnichannel in B2B sales: The new normal in a year that has been anything but.” McKinsey & Company, 15 March 2021. Accessed Dec. 2021.

      Jansen, Hasse. “Buyer Personas – 33 Mind Blowing Stats.” Boardview.io!, 19 Feb. 2016. Accessed Jan. 2022.

      Raynor, Lilah. “Understanding The Changing B2B Buyer Journey.” Forbes Agency Council, 18 July 2021. Accessed Dec. 2021.

      Simpson, Jon. “Finding Your Audience: The Importance of Developing a Buyer Persona.” Forbes Agency Council, 16 May 2017. Accessed Dec. 2021.

      “Successfully Executing Personalized Marketing Campaigns at Scale.” Plexure, 6 Jan. 2020. Accessed Dec 2020.

      Ulwick, Anthony W. JOBS TO BE DONE: Theory to Practice. E-book, Strategyn, 1 Jan. 2017. Accessed Jan. 2022.

      Embed Security Into the DevOps Pipeline

      • Buy Link or Shortcode: {j2store}265|cart{/j2store}
      • member rating overall impact: 9.3/10 Overall Impact
      • member rating average dollars saved: $31,515 Average $ Saved
      • member rating average days saved: 26 Average Days Saved
      • Parent Category Name: Secure Cloud & Network Architecture
      • Parent Category Link: /secure-cloud-network-architecture
      • Your organization is starting its DevOps journey and is looking to you for guidance on how to ensure that the outcomes are secure.
      • Or, your organization may have already embraced DevOps but left the security team behind. Now you need to play catch-up.

      Our Advice

      Critical Insight

      • Shift security left. Identify opportunities to embed security earlier in the development pipeline.
      • Start with minimum viable security. Use agile methodologies to further your goals of secure DevOps.
      • Treat “No” as a finite resource. The role of security must transition from that of naysayer to a partner in finding the way to “Yes.”

      Impact and Result

      • Leverage the CLAIM (Culture, Learning, Automation, Integration, Measurement) Framework to identify opportunities to close the gaps.
      • Collaborate to find new ways to shift security left so that it becomes part of development rather than an afterthought.
      • Start with creating minimum viable security by developing a DevSecOps implementation strategy that focuses initially on quick wins.

      Embed Security Into the DevOps Pipeline Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should secure the DevOps pipeline, 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. Identify opportunities

      Brainstorm opportunities to secure the DevOps pipeline using the CLAIM Framework.

      • Embed Security Into the DevOps Pipeline – Phase 1: Identify Opportunities

      2. Develop strategy

      Assess opportunities and formulate a strategy based on a cost/benefit analysis.

      • Embed Security Into the DevOps Pipeline – Phase 2: Develop Strategy
      • DevSecOps Implementation Strategy Template
      [infographic]

      Design a VIP Experience for Your Service Desk

      • Buy Link or Shortcode: {j2store}480|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
      • VIPs and executives expect to get immediate service for every IT issue, no matter how minor, and the service desk is constantly in reactive mode trying to quickly resolve these issues.
      • VIPs don’t understand or have input into service desk processes, procedures, and SLAs, especially when it comes to prioritization of their issues over other tickets.
      • The C-suite calls the CIO directly with every issue they have, tying them up and forcing them to redirect resources with little notice.
      • VIP tickets sit in the queue too long without a response or resolution, and VIPs are dissatisfied with the service they receive.

      Our Advice

      Critical Insight

      • Service desk and IT leaders are unclear on VIPs' service delivery expectations or the best support model to meet their needs while continuing to meet SLAs for the rest of the organization.
      • Deploying resources to service VIPs ahead of other users or more critical problems can result in inappropriate prioritization of issues and poor service delivery to the rest of the organization.
      • The reality for most organizations is that VIPs need special treatment; but providing VIP service shouldn’t come at the expense of good service delivery for the rest of the organization.

      Impact and Result

      • Stop being reactive to VIP requests and start planning for them so you can formally define the service and set expectations.
      • Talk to all relevant stakeholders to clarify their expectations before choosing a VIP service delivery model. Once you have designed your model, define and document the VIP service processes and procedures and communicate them to your stakeholders so everyone is clear on what is in and out of scope.
      • Once you’ve launched the service, track and report on key service desk metrics associated with VIP requests so you can properly allocate resources, budget accurately, evaluate the effectiveness of the service and demonstrate it to executives.

      Design a VIP Experience for Your Service Desk Research & Tools

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

      1. Design a VIP Experience for Your Service Desk Storyboard – A guide to defining your VIP service desk support model

      Follow the seven steps outlined in this blueprint to design a VIP support model that best suits your organization, then communicate and evaluate the service to ensure it delivers results.

      • Design a VIP Experience for Your Service Desk Storyboard

      2. Service Desk VIP Procedures Template – A customizable template to document your service desk procedures for handling VIP tickets.

      This template is designed to assist with documenting your service desk procedures for handling VIP or executive tickets. It can be adapted and customized to reflect your specific support model and procedures.

      • Service Desk VIP Procedures Template

      3. VIP Support Process Workflow Example – A Visio template to document your process for resolving VIP tickets.

      This Visio template provides an example of a VIP support process, with every step involved in resolving or fulfilling VIP service desk tickets. Use this as an example to follow and a template to document your own process.

      • VIP Support Process Workflow Example

      4. VIP Support Service Communication Template – A customizable PowerPoint template to communicate and market the service to VIP users.

      This template can be customized to use as an executive presentation to communicate and market the service to VIP users and ensure everyone is on the same page.

      • VIP Support Service Communication Template
      [infographic]

      Further reading

      Design a VIP Experience for Your Service Desk

      Keep the C-suite satisfied without sacrificing service to the rest of the organization.

      Analyst Perspective

      Stop being reactive to VIP demands and formalize their service offering.

      Natalie Sansone, PHD

      Natalie Sansone, PHD

      Research Director,
      Infrastructure & Operations
      Info-Tech Research Group

      In a perfect world, executives wouldn’t need any special treatment because the service desk could rapidly resolve every ticket, regardless of the submitter, keeping satisfaction levels high across the board.

      But we know that’s not the case for most organizations. Executives and VIPs demand higher levels of service because the reality in most companies is that their time is worth more. And any IT leader who’s had a VIP complain about their service knows that their voice also carries more weight than that of a regular dissatisfied user.

      That said, most service desks feel strapped for resources and don’t know how to improve service for VIPs without sacrificing service to the rest of the organization.

      The key is to stop being reactive to VIP demands and formalize your VIP service procedures so that you can properly set expectations for the service, monitor and measure it, and continually evaluate it to make changes if necessary.

      A VIP offering doesn’t have to mean a white glove concierge service, either – it could simply mean prioritizing VIP tickets differently. How do you decide which level of service to offer? Start by assessing your specific needs based on demand, gather requirements from relevant stakeholders, choose the right approach to fit your business needs and capabilities, clearly define and document all aspects of the service then communicate it so that everyone is on the same page as to what is in and out of scope, and continually monitor and evaluate the service to make changes and improvements as needed.

      Executive Summary

      Your Challenge

      • VIPs and executives expect to get immediate service for every IT issue, no matter how minor, and the service desk is constantly in reactive mode trying to quickly resolve these issues.
      • VIPs don’t understand or have input into service desk processes, procedures, and SLAs, especially when it comes to prioritization of their issues over other tickets.
      • The C-suite calls the CIO directly with every issue they have, tying them up and forcing them to redirect resources with little notice.
      • VIP tickets sit in the queue too long without a response or resolution, and VIPs are dissatisfied with the service they receive.

      Common Obstacles

      • Service desk and IT leaders are unclear on the expectations that VIPs have for service delivery, or they disagree about the best support model to meet their needs while continuing to meet SLAs for the rest of the organization.
      • Service desk teams with limited resources are unsure how best to allocate those resources to handle VIP tickets in a timely manner.
      • There aren’t enough resources available at the service desk to provide the level of service that VIPs expect for their issues.
      • Deploying resources to service VIPs ahead of other users can result in inappropriate prioritization of issues and poor service delivery to the rest of the organization

      Info-Tech's Approach

      • Stop being reactive to VIP requests and start planning for them so you can formally define the service and set expectations.
      • Talk to all relevant stakeholders to clarify their expectations before choosing a VIP service delivery model.
      • Define and document the VIP service processes and procedures, including exactly what is in and out of scope.
      • Track and report on metrics associated with VIP requests so you can properly allocate resources and budget for the service.
      • Continually evaluate the service to expand, reduce, or redefine it, as necessary.

      Info-Tech Insight

      The reality for most organizations is that VIPs need special treatment. But providing VIP service shouldn’t come at the expense of good service delivery for the rest of the organization. To be successful with your approach, formalize the VIP offering to bring consistency and clear expectations for both users and the IT staff delivering the service.

      Do any of these scenarios sound familiar?

      All these familiar scenarios can occur when the service desk treats VIP issues reactively and doesn’t have a defined, documented, and agreed-upon VIP process in place.
      • A VIP calls because their personal printer isn’t working, but you also have a network issue affecting payroll being able to issue paychecks. The VIP wants their issue fixed immediately despite there being a workaround and a higher priority incident needing resources.
      • The COO calls the CIO after hours about issues they’re having with their email. The CIO immediately deploys a field tech back to the office to help the COO. Once the tech arrives, the COO says the issue could have waited until the morning.
      • The company president wants IT to spend a day at their house setting up their new personal laptop to be able to connect into the office before their vacation tomorrow. It would take away one FTE from an already understaffed service desk.
      • The CEO brings their child’s new iPhone in and asks the service desk if they have time to set it up as a favor today. The service desk manager instructs the T2 apps specialist to drop his other tickets to work on this immediately.
      • Two tickets come in at the same time – one is from an SVP who can’t log in to Teams and has an online meeting in half an hour, and the other is for a department of 10 who can’t access the network. The service desk doesn’t know who to help first.

      Different organizations can take very different approaches to VIP requests

      CASE STUDIES

      Providing VIP support helped this company grow

      Allocating a dedicated VIP technician slowed down service delivery for this company

      Situation

      A SaaS company looking to build and scale its services and customers decided to set up a VIP support program, which involved giving their most valuable customers white glove treatment to ensure they had a great experience, became long-term customers, and thus had a positive influence on others to build up the company’s customer base. VIPs were receiving executive-level support with a dedicated person for VIP tickets. The VIPs were happy with the service, but the VIP technician’s regular work was frequently impeded by having to spend most of her time doing white glove activities. The service desk found that in some cases, more critical work was slipping as a result of prioritizing all executive tickets.

      Resolution

      First, they defined who would receive VIP support, then they clearly defined the service, including what VIP support includes, who gets the service, and what their SLAs for service are. They found that the program was an effective way to focus their limited resources on the customers with the highest value potential to increase sales.
      While this model differs from an IT service desk VIP support program, the principles of dedicating resources to provide elevated support to your most important and influential customers for the benefit and growth of the company as a whole remain the same.
      The service desk decided to remove the VIP function. They demonstrated that the cost per contact was too high for dedicated executive support, and reallocating that dedicated technician to the service desk would improve the resolution time of all business incidents and requests. VIPs could still receive prioritized support through the escalation process, but they would contact the regular service desk with their issues. VIPs approved the change, and as a result of removing the dedicated support function, the service desk reduced average incident resolution times by 28% and request fulfillment times by 33%.

      A well-designed and communicated VIP support service can deliver many benefits

      The key to deciding whether a VIP service is right for your organization is to first analyze your needs, match them against your resources, then clearly define and document exactly what is in scope for the service.

      A successfully designed VIP service will lead to:

      • Executives and VIPs can easily contact the service desk and receive exceptional support and customer service from a knowledgeable technician, increasing their trust in the service desk.
      • All service desk tickets are prioritized appropriately and effectively in order to maximize overall ticket resolution and fulfillment times.
      • All users have a clear understanding of how to get in touch with the service desk and expected SLAs for specific ticket types.
      • Critical, business-impacting issues still receive priority service ahead of minor tickets submitted by a VIP.
      • All service desk technicians are clear on processes and procedures for prioritizing and handling VIP tickets.
      • Executives are satisfied with the service they receive and the value that IT provides
      • Reduced VIP downtime, contributing to overall organization productivity and growth.

      A poorly designed or reactive VIP service will lead to:

      • VIPs expect immediate service for non-critical issues, including after-hours.
      • VIPs circumvent the correct process and contact the CIO or service desk manager directly for all their issues.
      • Service desk resources stretched thin, or poor allocation of resources leads to degraded service for the majority of users.
      • More critical business issues are pushed back in order to fix non-critical executive issues.
      • Service desk is not clear how to prioritize tickets and always addresses VIP tickets first regardless of priority.
      • The service desk automatically acts on VIP tickets even when the VIP doesn’t require it or realize they’re getting a different level of service.
      • Non-VIP users are aware of the different service levels and try to request the same priority for their tickets. Support costs are over budget.

      Follow Info-Tech’s approach to design a successful VIP support model

      Follow the seven steps in this blueprint to design a VIP support model that works for your organization:
      1. Understand the support models available, from white glove service to the same service for everyone.
      2. Gather business requirements from all relevant stakeholders.
      3. Based on your business needs, choose the right approach.
      4. Define and document all details of the VIP service offering.
      5. Communicate and market the offering to VIPs so they’re aware of what’s in scope.
      6. Monitor volume and track metrics to evaluate what’s working.
      7. Continually improve or modify the service as needed over time.

      Blueprint deliverables

      The templates listed below are designed to assist you with various stages of this project. This storyboard will direct you when and how to complete them.

      Service Desk VIP Procedures Template

      Use this template to assist with documenting your service desk procedures for handling VIP or executive tickets.

      VIP Support Process Workflow Example

      Use this Visio template to document your process for resolving or fulfilling VIP tickets, from when the ticket is submitted to when it’s closed.

      VIP Support Service Communication Template

      Use this template to customize your executive presentation to communicate and market the service to VIP users.

      Insight Summary

      Key Insight

      The reality for most organizations is that VIPs need special treatment. But providing VIP service shouldn’t be at the expense of good service delivery for the rest of the organization. To be successful with your approach, formalize the VIP offering to bring consistency and clear expectations for both users and the IT staff delivering the service.

      Additional insights:

      Insight 1

      VIP service doesn’t have to mean concierge service. There are different levels and models of VIP support that range in cost and level of service provided. Carefully evaluate your needs and capacity to choose the approach that works best for your organization.

      Insight 2

      This service is for your most valued users, so design it right from the start to ensure their satisfaction. Involve stakeholders from the beginning, incorporate their feedback and requirements, keep them well-informed about the service, and continually collect and act on feedback to deliver the intended value.

      Insight 3

      Intentional, continual monitoring and measurement of the program must be part of your strategy. If your metrics or feedback show that something isn’t working, fix it. If you find that the perceived value isn’t worth the high cost of the program, make changes. Even if everything seems to be working fine, identify ways to improve it or make it more efficient.

      Step 1: Understand the different support models

      Step overview:

      • Understand the support models available, from white glove service to the same service for everyone

      First, define what “VIP support” means in your organization

      VIP support from the service desk usually refers to an elevated level of service (i.e. faster, after-hours, off-site, and/or with more experienced resources) that is provided to those at the executive level of the organization.

      A VIP typically includes executives across the business (e.g. CIO, CEO, CxO, VPs) and sometimes the executive assistants who work directly with them. However, it can also include non-executive-level but critical business roles in some organizations.

      The level of VIP service provided can differ from receiving prioritization in the queue to having a dedicated, full-time technician providing “white glove” service.

      Info-Tech Insight

      You don’t have to use the term “VIP”, as long as you clearly define the terms you are using. Some organizations use the term “VIR” to refer to very important roles rather than people, and some define “critical users” to reflect who should receive prioritized service, for example.

      There are essentially two options for VIP support, but multiple determining factors

      While the details are more specific, your options for VIP support really come down to two: they either receive some kind of enhanced service (either from a dedicated support team or through prioritization from the regular support team) or they don’t. Which option you choose will depend on a wide range of factors, some of which are represented in the diagram below. Factors such as IT budget, size of organization help determine which VIP support model you choose: Enhanced, or the same as everyone else. With enhanced service, you can opt to a dedicated support team or same support team but with prioritized service.

      Option 1: Same service for everyone

      What does it look like?

      VIP tickets are prioritized in the same way as every other ticket – with an assessment by impact and urgency. This allows every ticket to be prioritized appropriately according to how big the impact of the issue is and how quickly it needs to be resolved – regardless of who the submitter is. This means that VIPs with very urgent issues will still receive immediate support, as would a non-VIP user with a critical issue.

      Who is it best suited for?

      • Small organizations and IT teams.
      • Executives don’t want special treatment.
      • Not enough service desk resources or budget to provide prioritized or dedicated VIP service.
      • Service desk is already efficient and meeting SLAs for all requests and incidents.

      Pros

      • Highest level of consistency in service because the same process is followed for all user groups.
      • Ensures that service doesn’t suffer for non-VIP users for teams with a limited number of service desk staff.
      • No additional cost.
      • Potential to argue for more resources if executive service expectations aren’t met.

      Cons

      • Does not work if executives expect or require elevated service regardless of issue type.
      • Potential for increase in management escalations or complaints from dissatisfied executives. Some may end up jumping the queue as a result, which results in unstandardized VIP treatment only for some users.

      Info-Tech Insight

      Don’t design a VIP service solely out of fear that VIPs will be unhappy with the standard level of support the service desk provides. In some cases, it is better to focus your efforts on improving your standard support for everyone rather than only for a small percentage of users, especially if providing that elevated VIP support would further deteriorate service levels for the rest of the organization.

      Option 2: Prioritized service for VIPs

      What does it look like?

      • VIPs still go through the service desk but receive higher priority than non-VIP tickets.
      • Requests from VIP submitters are still evaluated using the standard prioritization matrix but are bumped up in urgency or priority. More critical issues can still take precedence.
      • Existing service desk resources are still used to resolve the request, but requests are just placed closer to the “front of the line.”
      • VIP users are identified in the ticketing system and may have a separate number to call or are routed differently/skip the queue within the ACD/IVR.

      Who is it best suited for?

      • Organizations that want or need to give VIPs expedited or enhanced service, but that don’t have the resources to dedicate to a completely separate VIP service desk team.

      Pros

      • Meets the need of executives for faster service.
      • Balances the need for prioritized service to VIPs while not sacrificing resources to handle most user requests.
      • All tickets still go through a single point of contact to be triaged and monitored by the service desk.
      • Easy to measure and compare performance of VIP service vs. standard service because processes are the same.

      Cons

      • Slight cost associated with implementing changes to phone system if necessary.
      • Makes other users aware that VIPs receive “special treatment” – some may try to jump the queue themselves.
      • May not meet the expectations of some executives who prefer dedicated, face-to-face resources to resolve their issues.

      Info-Tech Insight

      If you’re already informally bumping VIP tickets up the queue, this may be the most appropriate model for you. Bring formalization to your process by clearly defining exactly where VIP tickets fit in your prioritization matrix to ensure they are handled consistently and that VIPs are aware of the process.

      Option 3: Dedicated VIP service

      What does it look like?

      • VIPs contact a dedicated service desk and receive immediate/expedited support, often face to face.
      • Often a separate phone number or point of contact.
      • Similar to concierge service or “white glove” service models.
      • At least one dedicated FTE with good customer service skills and technical knowledge who builds trust with executives.

      Who is it best suited for?

      • Larger enterprises with many VIP users to support, but where VIPs are geographically clustered (as geography sprawls, the cost of the service will spiral).
      • IT organizations with enough resources on the service desk to support a dedicated VIP function.
      • Organizations where executives require immediate, in-person support.

      Pros

      • Most of the time, this model results in the fastest service delivery to executives.
      • Most personal method of delivering support with help often provided in person and from familiar, trusted technicians.
      • Usually leads to the highest level of satisfaction with the service desk from executives.

      Cons

      • Most expensive model; usually requires at least one dedicated, experienced FTE to support and sometimes after-hours support.
      • Essentially two separate service desks; can result in a disconnect between staff.
      • Career path and cross-training opportunities for the dedicated staff may be limited; role can be exhausting.
      • Reporting on the service can be more complicated and tickets are often logged after the fact.
      • If not done well, quality of service can suffer for the rest of the organization.

      Info-Tech Insight

      This type of model is essential in many large enterprises where the success of the company can depend on VIPs having access to dedicated support to minimize downtime as much as possible. However, it also requires the highest level of planning and dedication to get right. Without carefully documented processes and procedures and highly trained staff to support the model, it will fail to deliver the expected benefits.

      Step 2: Capture business needs

      Step overview:

      • Analyze your data and gather requirements to determine whether there is a need for a VIP service.

      Assess current state and metrics

      You can’t define your target state without a clear understanding of your current state. Analyze your ticket data and reports to identify the type and volume of VIP requests the service desk receives and how well you’re able to meet these requests with your current resources and structure.

      Analyze ticket data

      • What volume of tickets are you supporting? How many of those tickets come from VIP users?
      • What is your current resolution time for incidents and requests? How well are you currently meeting SLAs?
      • How quickly are executive/VIP tickets being resolved? How long do they have to wait for a response?
      • How many after-hours requests do you receive?

      Assess resourcing

      • How many users do you support; what percentage of them would be identified as VIP users?
      • How many service desk technicians do you have at each tier?
      • How well are you currently meeting demand? Would you be able to meet demand if you dedicated one or more Tier 2 technicians to VIP support?
      • If you would need to hire additional resources, is there budget to do so?

      Use the data to inform your assessment

      • Do you have a current problem with service delivery to VIPs and/or all users that needs to be addressed by changing the VIP support model?
      • Do you have the demand to support the need for a VIP service?
      • Do you have the resources to support providing VIP service?

      Leverage Info-Tech’s tools to inform your assessment

      Analyze your ticket data and reports to understand how well you’re currently meeting SLAs, your average response and resolution times, and the volume and type of requests you get from VIPs in order to understand the need for changing your current model. If you don’t have the ticket data to inform your assessment, leverage Info-Tech’s Service Desk Ticket Analysis Tool.

      Service Desk Ticket Analysis Tool

      Use this tool to identify trends and patterns in your ticket data. The ticket summary dashboard contains multiple reports analyzing how tickets come in, who requests them, who resolves them, and how long it takes to resolve them.

      If you need help understanding how well your current staff is able to handle your current ticket volume, leverage Info-Tech’s Service Desk Staffing Calculator to analyze demand and ticket volume trends. While not specifically designed to analyze VIP tickets, you could run the assessment separately for VIP volume if you have that data available.

      Service Desk Staffing Calculator

      Use this tool to help you estimate the optimal resource allocation to support your demand over time.

      Engage stakeholders to understand their requirements

      Follow your organization’s requirements gathering process to identify and prioritize stakeholders, conduct stakeholder interviews, and identify, track, and prioritize their requirements and expectations for service delivery.

      Gather requirements from VIP stakeholders

      1. Identify which stakeholders need to be consulted.
      2. Prioritize stakeholders in terms of influence and interest in order to identify who to engage in the requirements gathering process.
      3. Build a plan for gathering the requirements of key stakeholders in terms of VIP service delivery.
      4. Conduct requirements gathering and record the results of each stakeholder interaction.
      5. Analyze and summarize the results to determine the top expectations and requirements for VIP service desk support.

      If your organization does not have a defined requirements gathering process or template, leverage Info-Tech tools and templates:

      The Improve Requirements Gathering blueprint can be adapted from software requirements gathering to service desk.

      The PMO Requirements Gathering Tool can be adapted from interviewing stakeholders on their PMO requirements to service desk requirements.

      Info-Tech Insight

      Don’t guess at what your VIPs need or want – ask them and involve them in the service design. Many IT leaders sacrifice overall service quality to prioritize VIPs, thinking they expect immediate service. However, they later find out that the VIPs just assumed the service they were receiving was the standard service and many of their issues can wait.

      Identify additional challenges and opportunities by collecting perceptions of business users and stakeholders

      Formally measuring perceptions from your end users and key business stakeholders will help to inform your needs and determine how well the service desk is currently meeting demands from both VIP users and the entire user base.

      CIO Business Vision

      Info-Tech's CIO Business Vision program is a low-effort, high-impact program that will give you detailed report cards on the organization’s satisfaction with IT’s core services. Use these insights to understand your key business stakeholders, find out what is important to them, and improve your interactions.

      End User Satisfaction

      Info-Tech’s End User Satisfaction Program helps you measure end-user satisfaction and importance ratings of core IT services, IT communications, and business enablement to help you decide which IT service capabilities need to be addressed to meet the demands of the business.

      Learn more about Info-Tech’s CIO Business Vision or End User Satisfaction Program .

      Step 3: Choose the right approach

      Step overview:

      • Based on your assessment from Step 2, decide on the best way to move forward with your VIP service model.

      Use your assessment results to choose the most appropriate support model

      The table below is a rough guide for how the results of your assessments may line up to the most appropriate model for your organization:

      Example assessment results for: Dedicated service, prioritized service, and same servce based off of the assessment source: Ticket analysis, staffing analysis, or stakeholder.

      Info-Tech Insight

      If you’re in the position of deciding how to improve service to VIPs, it’s unlikely that you will end up choosing the “same service” model. If your data analysis tells you that you are currently meeting every metric target for all users, this may actually indicate that you’re overstaffed at the service desk.

      If you choose a specialized VIP support model, ensure there is a strong, defined need before moving forward

      Do not proceed if:

      • Your decision is purely reactive in response to a perceived need or challenges you’re currently experiencing
      • The demand is coming from a single dissatisfied executive without requirements from other VIPs being collected.
      • Your assessment data does not support the demand for a dedicated VIP function.
      • You don’t have the resources or support required to be successful in the approach.

      Proceed with a VIP model if:

      • You’re prepared to scale and support the model over the long term.
      • Business stakeholders have clearly expressed a need for improved VIP service.
      • Data shows that there is a high volume of urgent requests from VIPs.
      • You have the budget and resources required to support an enhanced VIP service delivery model.

      Step 4: Design the service offering

      Step overview:

      • Define and document all processes, procedures, and responsibilities relevant to the VIP support offering.

      Clearly define the service and eligible users

      Once you’ve decided on the most appropriate model, clearly describe the service and document who is eligible to receive it.

      1. Define exactly what the service is before going into the procedural details. High-level examples to start from are provided below:

      Prioritized Service Model

      When a designated VIP user contacts the service desk with a question, incident, or service request, their ticket will be prioritized over non-VIP tickets following the prioritization matrix. This process has been designed in accordance with business needs and requirements, as defined VIP users have more urgent demands on their time and the impact of downtime is greater as it has the potential to impact the business. However, all tickets, VIP tickets included, must still be prioritized by impact and urgency. Incidents that are more critical will still be resolved before VIP tickets in accordance with the prioritization process.

      Dedicated Service Model

      VIP support is a team of dedicated field technicians available to provide an elevated level of service including deskside support for executives and designated VIP users. VIP users have the ability to contact the VIP support service through a dedicated phone number and will receive expedited ticket handling and resolution by dedicated Tier 2 specialists with experience dealing with executives and their unique needs and requirements. This process has been designed in accordance with business needs and requirements.

      2 Identify VIP-eligible users

      • Define who qualifies as a VIP to receive VIP support or be eligible to contact the dedicated VIP service desk/concierge desk.
      • If other users or EAs can submit tickets on behalf of VIPs, identify those individuals as well.
      • Review the list and cut back if necessary. Less is usually more here, especially when starting out. If everyone is a VIP, then no one is truly a VIP.
      • Identify who maintains ownership over the list of eligible VIP users and how any changes to the list or requests for changes will be handled.
      • Ensure that all VIP-eligible users are clearly identified in the ITSM system.

      Map out the VIP process in a workflow

      Use a visual workflow to document the process for resolving or fulfilling VIP tickets, from when the ticket is submitted to when it gets closed.

      Your workflow should address the following:

      • How should the ticket be prioritized?
      • When are escalations necessary?
      • What happens if a user requests VIP service but is not defined as eligible?
      • Should the user verify that the issue is resolved before the ticket is closed?
      • What automatic notifications or communications need to go out and when?
      • What manual communications or notifications need to be sent out (e.g. when a ticket is escalated or reassigned)?
      VIP Support Process Example.

      Use the VIP Support Process Workflow Example as a template to map out your own process.

      Define and document all VIP processes and procedures

      Clearly describe the service and all related processes and procedures so that both the service delivery team and users are on the same page.

      Define all aspects of the service so that every VIP request will follow the same standardized process and VIPs will have clear expectations for the service they receive. This may include:

      • How VIPs should contact the service desk
      • How VIP tickets will be prioritized
      • SLAs and service expectations for VIP tickets
      • Ticket resolution or fulfillment steps and process
      • Escalation points and contacts
      • After-hours requests process

      If VIP user requests receive enhanced priority, for example, define exactly how those requests should be prioritized using your prioritization matrix. An example is found below and in the Service Desk VIP Procedures Template.

      Prioritization matrix for classification of incidents and requests.

      Use Info-Tech’s Service Desk VIP Procedures Template as a guide

      This template is designed to assist with documenting your service desk procedures for handling VIP or executive tickets. The template is not meant to cover all possible VIP support models but is an example of one support model only. It should be adapted and customized to reflect your specific support model and procedures.

      It includes the following sections:

      1. VIP support description/overview
      2. VIP support entitlement (who is eligible)
      3. Procedures
        • Ticket submission and triage
        • Ticket prioritization
        • SLAs and escalation
        • VIP ticket resolution process
        • After-hours requests
      4. Monitoring and reporting

      Download the Service Desk VIP Procedures Template

      Allocate resources or assign responsibilities specific to VIP support

      Regardless of the support model you choose, you’ll need to be clear on service desk agents’ responsibilities when dealing with VIP users.
      • Clarify the expectations of any service desk agent who will be handling VIP tickets; they should demonstrate excellent customer service skills and expertise, respect for the VIP and the sensitivity of their data, and prompt service.
      • Use a RACI chart to clarify responsibility and accountability for VIP-specific support tasks.
      • If you will be moving to a dedicated VIP support team, clearly define the responsibilities of any new roles or tasks. Sample responsibilities can be found on the right.
      • If you will be changing the role of an existing service desk agent to become focused solely on providing VIP support, clarify how the responsibilities of other service desk agents may change too, if at all.
      • Be clear on expectations of agents for after-hours support, especially if there will be a change to the current service provision.

      Sample responsibilities for a dedicated VIP support technician/specialist may include:

      • Resolve support tickets for all eligible VIP users following established processes and procedures.
      • Provide both onsite and remote support to executives.
      • Quickly and effectively diagnose and resolve technical issues with minimal disruption to the executive team.
      • Establish trust with executives/VIPs by maintaining confidentiality and privacy while providing technical support.
      • Set up, monitor, and support high-priority meetings, conferences, and events.
      • Demonstrate excellent communication and customer service skills when providing support to executives.
      • Coordinate more complex support issues with higher level support staff and track tickets through to resolution when needed.
      • Learn new technology and software ahead of implementation to train and support executive teams for use.
      • Conduct individual or group training as needed to educate on applications or how to best use technology to enhance productivity.
      • Proactively manage, maintain, update, and upgrade end-user devices as needed.

      Configure your ITSM tool to support your processes

      Configure your tool to support your processes, not the other way around.
      • Identify and configure VIP users in the system to ensure that they are easily identifiable in the system (e.g. there may be a symbol beside their name).
      • Configure automations or build ticket templates that would automatically set the urgency or priority of VIP tickets.
      • Configure any business rules or workflows that apply to the VIP support process.
      • Define any automated notifications that need to be sent when a VIP ticket is submitted, assigned, escalated, or resolved (e.g. notify service desk manager or a specific DL).
      • Define metrics and customize dashboards and reports to monitor VIP tickets and measure the success of the VIP service.
      • Configure any SLAs that apply only to VIPs to ensure displayed SLAs are accurate.

      Step 5: Launch the service

      Step overview:

      • Communicate and market the service to all relevant stakeholders so everyone is on the same page as to how it works and what’s in scope.

      Communicate the new or revised service to relevant stakeholders ahead of the launch

      If you did your due diligence, the VIP service launch won’t be a surprise to executives. However, it’s critical to

      continue the engagement and communicate the details of the service well to ensure there are no misperceptions about the

      service when it launches.

      Goals of communicating and marketing the service:

      1. Create awareness and understanding of the purpose of the VIP service and what it means for eligible users.
      2. Solidify commitment and buy-in for the service from all stakeholders.
      3. Ensure that all users know how to access the service and any changes to the way they should interact with the service desk.
      4. Set expectations for new/revised service levels.
      5. Reduce and address any concerns about the change in process.

      Info-Tech Insight

      This step isn’t only for the launch of new services. Even if you’re enhancing or right-sizing an existing VIP service, take the opportunity to market the improvements, remind users of the correct processes, and collect feedback.

      Leverage Info-Tech’s communication template to structure your presentation

      This template can be customized to use as an executive presentation to communicate and market the service to VIP users. It includes:

      • Key takeaways
      • Current-state assessment
      • Requirements gathering and feedback results
      • Objectives for the service
      • Anticipated benefits
      • Service entitlement
      • How the service works
      • Escalations and feedback contacts
      • Timeline of next steps

      Info-Tech Insight

      If you’re launching a dedicated concierge service for VIPs, highlight the exclusivity of the service in your marketing to draw users in. For example, if eligible VIPs get a separate number to call, expedited SLAs, or access to more tenured service desk experts, promote this added value of the service.

      Download the VIP Support Service Communication Template

      Step 6: Monitor and measure

      Step overview:

      • Measure and monitor the success of the program by tracking and reporting on targeted metrics.

      Evaluate and demonstrate the success of the program with key metrics

      Targeted metrics to evaluate the success of the VIP program will be critical to understanding and demonstrating whether the service is delivering the intended value. Track key metrics to:

      • Track if and how well you’re meeting your defined SLAs for VIP support.
      • Measure demand for VIP support (i.e. ticket volume and types of tickets) and evaluate against resource supply to determine whether a staffing adjustment is needed to meet demand.
      • Measure the cost of providing the VIP service in order to report back to executives.
      • Leverage real data to quantitatively demonstrate that you’re providing enhanced service to VIPs if there is an escalation or negative feedback from one individual.
      • Monitor service delivery to non-VIP users to ensure that service to the rest of the organization isn’t impacted by the VIP service
      • Evaluate the types of ticket that are submitted to the VIP service to inform training plans, self-service options, device upgrades, or alternatives to reduce future volume.

      Info-Tech Insight

      If your data definitively shows the VIP offering delivers enhanced service levels, publish these results to business leadership. A successful VIP service is a great accomplishment to market and build credibility for the service desk.

      Tie metrics to critical success factors

      Apart from your regular service desk metrics, identify the top metrics to tie to the key performance indicators of the program’s success factors.

      Sample Critical Success Factors

      • Increased executive satisfaction with the service desk
      • Improved response and resolution times to VIP tickets
      • Demand for the service is matched by supply

      Sample Metrics

      • End-user satisfaction scores on VIP tickets
      • Executive satisfaction with the service desk as measured on a broader annual survey
      • Response and resolution times for VIP tickets
      • Percentage of SLAs met for VIP tickets
      • VIP ticket volume
      • Average speed of answer for VIP calls

      Download Define Service Desk Metrics that Matter and the Service Desk Metrics Workbook for help defining CSFs, KPIs, and key metrics

      Step 7: Continually improve

      Step overview:

      • Continually evaluate the program to identify opportunities for improvement or modifications to the service support model.

      Continually evaluate the service to identify improvements

      Executives are happy, resolution times are on target – now what? Even if everything seems to be working well, never stop monitoring, measuring, and evaluating the service. Not only can metrics change, but there can also always be ways to improve service.

      • Continual improvement should be a mindset – there are always opportunities for improvement, and someone should be responsible for identifying and tracking these opportunities so that they actually get done.
      • Just as you asked for feedback and involvement from VIPs (and their assistants who may submit tickets on their behalf) in designing the service, you should continually collect that feedback and use it to inform improvements to the service.
      • End-user satisfaction surveys, especially broader, more targeted surveys, are also a great source of improvement ideas.
      • Even if end users don’t perceive any need for improvement, IT should still assess how they can make their own processes more efficient or offer alternatives to make delivery easier.

      Download Info-Tech’s Build a Continual Improvement Program blueprint to help you build a process around continual improvement, and use the Continual Improvement Register tool to help you identify and prioritize improvement initiatives.

      Info-Tech Insight

      Don’t limit your continual improvement efforts to the VIP service. Once you’ve successfully elevated the VIP service, look to how you can apply elements of that service to elevate support to the rest of the organization. For example, through providing a roaming service desk, a concierge desk, a Genius-Bar-style walk-in service, etc.

      Expand, reduce, or modify as needed

      Don’t stop with a one-time program evaluation. Continually use your metrics to evaluate whether the service offering needs to change to better suit the needs of your executives and organization. It may be fine as is, or you may find you need to do one of the following:

      Expand

      • If the service offering has been successful and/or your data shows underuse of VIP-dedicated resources, you may be able to expand the offering to identify additional roles as VIP-eligible.
      • Be cautious not to expand the service too widely; not only should it feel exclusive to VIPs, but you need to be able to support it.
      • Also consider whether elements that have been successful in the VIP program (e.g. a concierge desk, after-hours support) should be expanded to be offered to non-VIPs.

      Reduce

      • If VIPs are not using the service as much as anticipated or data shows supply outweighs demand, you may consider scaling back the service to save costs and resources.
      • However, be careful in how you approach this – it shouldn’t negatively impact service to existing users.
      • Rather, evaluate costly services like after-hours support and whether it’s necessary based on demand, adjust SLAs if needed, or reallocate service desk resources or responsibilities. For example, if demand doesn’t justify a dedicated service desk technician, either add non-VIP tasks to their responsibilities or consider moving to a prioritized model.

      Modify

      • The support model doesn’t need to be set in stone. If elements aren’t working, change them! If the entire support model isn’t working, reevaluate if it’s the best model for your organization.
      • Don’t make decisions in a vacuum, though. Just as executives were involved in decision-making at the outset, continually gather their feedback and use it to inform the service design.

      Related Info-Tech Research

      Standardize the Service Desk

      This project will help you build and improve essential service desk processes, including incident management, request fulfillment, and knowledge management to create a sustainable service desk.

      Optimize the Service Desk With a Shift-Left Strategy

      This project will help you build a strategy to shift service support left to optimize your service desk operations and increase end-user satisfaction.

      Build a Continual Improvement Plan

      This project will help you build a continual improvement plan for the service desk to review key processes and services and manage the progress of improvement initiatives.

      Deliver a Customer Service Training Program to Your IT Department

      This project will help you deliver a targeted customer service training program to your IT team to enhance their customer service skills when dealing with end users, improve overall service delivery, and increase customer satisfaction.

      Works Cited

      Munger, Nate. “Why You Should Provide VIP Customer Support.” Intercom, 13 Jan. 2016. Accessed Jan. 2023.

      Ogilvie, Ryan. “We Did Away With VIP Support and Got More Efficient.” HDI, 17 Sep. 2020. Accessed Jan. 2023.

      Apply Design Thinking to Build Empathy With the Business

      • Buy Link or Shortcode: {j2store}89|cart{/j2store}
      • member rating overall impact: 8.5/10 Overall Impact
      • member rating average dollars saved: $20,772 Average $ Saved
      • member rating average days saved: 13 Average Days Saved
      • Parent Category Name: Innovation
      • Parent Category Link: /innovation
      • Business satisfaction with IT is low.
      • IT and the business have independently evolving strategy, initiatives, and objectives.
      • IT often exceeds their predicted project costs and has difficulty meeting the business’ expectations of project quality and time-to-market.

      Our Advice

      Critical Insight

      • Business needs are unclear or ambiguous.
      • IT and the business do not know how to leverage each other’s talent and resources to meet their common goals.
      • Not enough steps are taken to fully understand and validate problems.
      • IT can’t pivot fast enough when the business’s needs change.

      Impact and Result

      Product, service, and process design should always start with an intimate understanding of what the business is trying to accomplish and why it is important.

      Apply Design Thinking to Build Empathy With the Business Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should apply experience design to partner with the business, 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. Research

      Identify goals and objectives for experience design, establish targeted stakeholders, and conduct discovery interviews.

      • Apply Design Thinking to Build Empathy With the Business – Phase 1: Research
      • Stakeholder Discovery Interview Template

      2. Map and iterate

      Create the journey map, design a research study to validate your hypotheses, and iterate and ideate around a refined, data-driven understanding of stakeholder problems.

      • Apply Design Thinking to Build Empathy With the Business – Phase 2: Map and Iterate
      • Journey Map Template
      • Research Study Log Tool
      [infographic]

      Workshop: Apply Design Thinking to Build Empathy With the Business

      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 Introduction to Journey Mapping

      The Purpose

      Understand the method and purpose of journey mapping.

      Key Benefits Achieved

      Initial understanding of the journey mapping process and the concept of end-user empathy.

      Activities

      1.1 Introduce team and discuss workshop motivations and goals.

      1.2 Discuss overview of journey mapping process.

      1.3 Perform journey mapping case study activity.

      Outputs

      Case Study Deliverables – Journey Map and Empathy Maps

      2 Persona Creation

      The Purpose

      Begin to understand the goals and motivations of your stakeholders using customer segmentation and an empathy mapping exercise.

      Key Benefits Achieved

      Understand the demographic and psychographic factors driving stakeholder behavior.

      Activities

      2.1 Discuss psychographic stakeholder segmentation.

      2.2 Create empathy maps for four segments.

      2.3 Generate problem statements.

      2.4 Identify target market.

      Outputs

      Stakeholder personas

      Target market of IT

      3 Interview Stakeholders and Start a Journey Map

      The Purpose

      Get first-hand knowledge of stakeholder needs and start to capture their perspective with a first-iteration journey map.

      Key Benefits Achieved

      Capture the process stakeholders use to solve problems and empathize with their perspectives, pains, and gains.

      Activities

      3.1 Review discovery interviewing techniques.

      3.2 Review and modify the discovery questionnaire

      3.3 Demonstrate stakeholder interview.

      3.4 Synthesize learnings and begin creating a journey map.

      Outputs

      Customized discovery interview template

      Results of discovery interviewing

      4 Complete the Journey Map and Create a Research Study

      The Purpose

      Hypothesize the stakeholder journey, identify assumptions, plan a research study to validate your understanding, and ideate around critical junctures in the journey.

      Key Benefits Achieved

      Understand the stakeholder journey and ideate solutions with the intention of improving their experience with IT.

      Activities

      4.1 Finish the journey map.

      4.2 Identify assumptions and create hypotheses.

      4.3 Discuss field research and hypothesis testing.

      4.4 Design the research study.

      4.5 Discuss concluding remarks and next steps.

      Outputs

      Completed journey map for one IT process, product, or service

      Research study design and action plan

      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)

       

       

      Infrastructure & Operations Priorities 2022

      • Buy Link or Shortcode: {j2store}56|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
      • The expectation amongst IT professionals for permanent transformational change has gone up 30% year over year. Further, 47% expect a lot of permanent change in 2022.
      • We are experiencing a great rate of change concurrent with a low degree of predictability.
      • How do you translate a general trend into a specific priority you can work on?

      Our Advice

      Critical Insight

      • Trends don’t matter but pressure does: Trends can be analyzed based on the pressure they exert (or not) on your I&O practice. Organizing trends into categories based on source makes for a more successful and contextual analysis.
      • Different prioritization is being demanded in 2022. For the foreseeable future prioritization is about drawing a line, below which you can ignore items with a clean conscience.
      • The priorities you choose to advocate for will be how your leadership is evaluated in the upcoming year.

      Impact and Result

      • By reading through this publication, you will begin to address the age-old problem “You don’t know what you don’t know.”
      • More importantly you will have a framework to dive deeper into the trends most relevant to you and your organization.
      • Info-Tech can help you turn your strong opinion into a compelling case for your stakeholders.

      Infrastructure & Operations Priorities 2022 Research & Tools

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

      1. Infrastructure & Operations Priorities 2022 – A framework to dive deeper into the trends most relevant to you and your organization

      Discover Info-Tech's four trends for Infrastructure & Operations leaders.

      • Infrastructure & Operations Priorities Report for 2022

      Infographic

      Adopt Change Management Practices and Succeed at IT Organizational Redesign

      • Buy Link or Shortcode: {j2store}393|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: Organizational Design
      • Parent Category Link: /organizational-design

      Organizational redesigns frequently fail when it comes to being executed. This leads to:

      • The loss of critical talent and institutional knowledge.
      • An inability to deliver on strategic goals and objectives.
      • Financial and time losses to the organization.

      Organizational redesigns fail during implementation primarily because they do not consider the change management required to succeed.

      Our Advice

      Critical Insight

      Implementing your organizational design with good change management practices is more important than defining the new organizational structure.

      Implementation is often negatively impacted due to:

      • Employees not understanding the need to redesign the organizational structure or operating model.
      • Employees not being communicated with or engaged throughout the process, which can cause chaos.
      • Managers not being prepared or trained to have difficult conversations with employees.

      Impact and Result

      When good change management practices are used and embedded into the implementation process:

      • Employees feel respected and engaged, reducing turnover and productivity loss.
      • The desired operating structure can be implemented faster, enabling the delivery of strategic objectives.
      • Gaps and disorganization are avoided, saving the organization time and money.

      Invest change management for your IT redesign.

      Adopt Change Management Practices and Succeed at IT Organizational Redesign Research & Tools

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

      1. Adopt Change Management Practices and Succeed at IT Organizational Redesign Deck – Succeed at implementing your IT organizational structure by adopting the necessary change management practices.

      The best IT organizational structure will still fail to be implemented if the organization does not leverage and use good change management practices. Consider practices such as aligning the structure to a meaningful vision, preparing leadership, communicating frequently, including employees, and measuring adoption to succeed at organizational redesign implementation.

      • Adopt Change Management Practices and Succeed at IT Organizational Redesign Storyboard

      2. IT Organizational Redesign Pulse Survey Template – A survey template that can be used to measure the success of your change management practices during organizational redesign implementation.

      Taking regular pulse checks of employees and managers during the transition will enable IT Leaders to focus on the right practices to enable adoption.

      • IT Organizational Redesign Pulse Survey Template
      [infographic]

      Further reading

      Adopt Change Management Practices & Succeed at IT Organizational Redesign

      The perfect IT organizational structure will fail to be implemented if there is no change management.

      Analyst Perspective

      Don’t doom your organizational redesign efforts

      The image contains a picture of Brittany Lutes.

      After helping hundreds of organizations across public and private sector industries redesign their organizational structure, we can say there is one thing that will always doom this effort: A failure to properly identify and implement change management efforts into the process.

      Employees will not simply move forward with the changes you suggest just because you as the CIO are making them. You need to be prepared to describe the individual benefits each employee can expect to receive from the new structure. Moreover, it has to be clear why this change was needed in the first place. Redesign efforts should be driven by a clear need to align to the organization’s vision and support the various objectives that will need to take place.

      Most organizations do a great job defining a new organizational structure. They identify a way of operating that tells them how they need to align their IT capabilities to deliver on strategic objectives. What most organizations do poorly is invest in their people to ensure they can adopt this new way of operating.

      Brittany Lutes
      Research Director, Organizational Transformation

      Info-Tech Research Group

      Executive Summary

      Your Challenge

      Common Obstacles

      Info-Tech’s Approach

      Organizational redesigns frequently fail when it comes to being executed. This leads to:

      • The loss of critical talent and institutional knowledge.
      • An inability to deliver on strategic goals and objectives.
      • Financial and time losses to the organization.

      Organizational redesigns fail during implementation primarily because they do not consider the change management required to succeed.

      Implementation of the organizational redesign is often impacted when:

      • Employees do not understand the need to redesign the organizational structure or operating model.
      • Employees are not communicated with or engaged throughout the process, which can cause chaos.
      • Managers are not prepared or trained to have difficult conversations with employees.

      Essentially, implementation is impacted when change management is not included in the redesign process.

      When good change management practices are used and embedded into the implementation process:

      • Employees feel respected and engaged, reducing turnover and productivity loss.
      • The desired operating structure can be implemented faster, enabling the delivery of strategic objectives.
      • Gaps and disorganization are avoided, saving the organization time and money.

      Invest in change management for your IT redesign.

      Info-Tech Insight

      Implementing your organizational design with good change management practices is more important than defining the new organizational structure.

      Your challenge

      This research enables organizations to succeed at their organizational redesign:

      • By implementing the right change management practices. These methods prevent:
        • The loss of critical IT employees who will voluntarily exit the organization.
        • Employees from creating rumors that will be detrimental to the change.
        • Confusion about why the change was needed and how it will benefit the strategic objectives the organization is seeking to achieve.
        • Spending resources (time, money, and people) on the initiative longer than is necessary.

      McKinsey reported less than 25% of organizational redesigns are successful. Which is worse than the average change initiative, which has a 70% failure rate.

      Source: AlignOrg, 2020.

      The value of the organizational redesign efforts is determined by the percentage of individuals who adopt the changes and operate in the desired way of working.

      When organizations properly use organizational design processes, they are:

      4× more likely to delight customers

      13× more effective at innovation

      27× more likely to retain employees

      Source: The Josh Bersin Company, 2022

      Common obstacles

      These barriers make implementing an organizational redesign difficult to address for many organizations:

      • You communicated the wrong message to the wrong audience at the wrong time. Repeatedly.
      • There is a lack of clarity around the drivers for an organizational redesign.
      • A readiness assessment was not completed ahead of the changes.
      • There is no flexibility built into the implementation approach.
      • The structure is not aligned to the strategic goals of IT and the organization.
      • IT leadership is not involved in their staff’s day-to-day activities, making it difficult to suggest realistic changes.

      Don’t doom your organizational redesign with poor change management

      Only 17% of frontline employees believe the lines of communication are open.

      Source: Taylor Reach Group, 2019

      43% Percentage of organizations that are ineffective at the organizational design methodology.

      Source: The Josh Bersin Company, 2022.

      Change management is a must for org design

      Forgetting change management is the easiest way to fail at redesigning your IT organizational structure

      • Change management is not a business transformation.
      • Change management consists of the practices and approaches your organization takes to support your people through a transformation.
      • Like governance, change management happens regardless of whether it is planned or ad hoc.
      • However, good change management will be intentional and agile, using data to help inform the next action steps you will take.
      • Change management is 100% focused on the people and how to best support them as they learn to understand the need for the change, what skills they must have to support and adopt the change, and eventually to advocate for the change.

      "Organizational transformation efforts rarely fail because of bad design, but rather from lack of sufficient attention to the transition from the old organization to the new one."

      – Michael D. Watkins & Janet Spencer. ”10 Reason Why Organizational Change Fails.”

      Info-Tech’s approach

      Redesigning the IT structure depends on good change management

      The image contains a screenshot of Info-Tech's approach, and good change management.

      Common changes in organizational redesigns

      Entirely New Teams

      Additions, reductions, or new creations. The individuals that make up a functional team can shift.

      New Team Members

      As roles become defined, some members might be required to shift and join already established groups.

      New Responsibilities

      The capabilities individuals will be accountable or responsible for become defined.

      New Ways of Operating

      From waterfall to Agile, collaborative to siloed, your operating model provides insight into the ways roles will engage one another.

      Top reasons organizational redesigns fail

      1. The rationale for the redesign is not clear.
      2. Managers do not have the skills to lead their teams through a change initiative like organizational redesign.
      3. You communicated the wrong messages at the wrong times to the wrong audiences.
      4. Frontline employees were not included in the process.
      5. The metrics you have to support the initiative are countering one another – if you have metrics at all.
      6. Change management and project management are being treated interchangeably.

      Case study: restructuring to reduce

      Clear Communication & Continuous Support

      Situation

      On July 26th, 2022, employees at Shopify – an eCommerce platform – were communicated to by their CEO that a round of layoffs was about to take place. Effective that day, 1,000 employees or 10% of the workforce would be laid off.

      In his message to staff, CEO Tobi Lutke admitted he had assumed continual growth in the eCommerce market when the COVID-19 pandemic forced many consumers into online shopping. Unfortunately, it was clear that was not the case.

      In his communications, Tobi let people know what to expect throughout the day, and he informed people what supports would be made available to those laid off. Mainly, employees could expect to see a transparent approach to severance pay; support in finding new jobs through coaching, connections, or resume creation; and ongoing payment for new laptops and internet to support those who depend on this connectivity to find new jobs.

      Results

      Unlike many of the other organizations (e.g. Wayfair and Peloton) that have had to conduct layoffs in 2022, Shopify had a very positive reaction. Many employees took to LinkedIn to thank their previous employer for all that they had learned with the organization and to ask their network to support them in finding new opportunities. Below is a letter from the CEO:

      The image contains a screenshot of a letter from the CEO.

      Shopify, 2022.
      Forbes, 2022.

      Aligned to a Meaningful Vision

      An organizational redesign must be aligned to a clear and meaningful vision of the organization.

      Define the drivers for organizational redesign

      And align the structure to execute on those drivers.

      • Your structure should follow your strategy. However, 83% of people in an organization do not fully understand the strategy (PWC, 2017).
      • How can employees be expected to understand why the IT organization needs to be restructured to meet a strategy if the strategy itself is still vague and unclear?
      • When organizations pursue a structural redesign, there are often a few major reasons:
        • Digital/organizational transformation
        • New organizational strategy
        • Acquisition or growth of products, services, or capabilities
        • The need to increase effectiveness
        • Cost savings
      • Creating a line of sight for your employees and leadership team will increase the likelihood that they want to adopt this structure.

      “The goal is to align your operating model with your strategy, so it directly supports your differentiating capabilities.”

      – PWC, 2017.

      How to align structure to strategy

      Recommended action steps:

      • Describe the end state of the organizational structure and how long you anticipate it will take to reach that state. It's important that employees be able to visualize the end state of the changes being made.
      • Ensure people understand the vision and goals of the IT organization. Are you having discussions about these? Are managers discussing these? Do people understand that their day-to-day job is intended to support those goals?
      • Create a visual:
        • The goals of the organization → align to the initiatives IT → which require this exact structure to deliver.
      • Do not assume people are willing to move forward with this vision. If people are not willing, assess why and determine if there are benefits specific to the individual that can support them in adopting the future state.
      • Define and communicate the risks of not making the organizational structure changes.

      Info-Tech Insight

      A trending organizational structure or operating model should never be the driver for an organizational redesign.

      IT Leaders Are Not Set Up To Succeed

      Empower these leaders to have difficult conversations.

      Lacking key leadership capabilities in managers

      Technical leaders are common in IT, but people leaders are necessary during the implementation of an organizational structure.

      • Managers are important during a transformational change for many reasons:
        • Managers play a critical role in being able to identify the skill gaps in employees and to help define the next steps in their career path.
        • After the sponsor (CIO) has communicated to the group the what and the why, the personal elements of the change fall to managers.
        • Managers’ displays of disapproval for the redesign can halt the transformation.
      • However, many managers (37%) feel uncomfortable talking to employees and providing feedback if they think it will elicit a negative response (Taylor Reach Group, 2019).
      • Unfortunately, organizational redesign is known for eliciting negative responses from employees as it generates fears around the unknown.
      • Therefore, managers must be able to have conversations with employees to further the successful implementation and adoption of the structure.

      “Successful organizational redesign is dependent on the active involvement of different managerial levels."

      – Marianne Livijn, “Managing Organizational Redesign: How Organizations Relate Macro and Micro Design.”

      They might be managers, but are they leaders?

      Recommended action steps:

      • Take time to speak with managers one on one and understand their thoughts, feelings, and understanding of the change.
      • Ensure that middle-managers have an opportunity to express the benefits they believe will be realized through the proposed changes to the organizational chart.
      • Provide IT leaders with leadership training courses (e.g. Info-Tech’s Leadership Programs).
      • Do not allow managers to start sharing and communicating the changes to the organizational structure if they are not demonstrating support for this change. Going forward, the group is all-in or not, but they should never demonstrate not being bought-in when speaking to employees.
      • Ensure IT leaders want to manage people, not just progress to a management position because they cannot climb a technical career ladder within the proposed structure. Provide both types of development opportunities to all employees.
      • Reduce the managers’ span of control to ensure they can properly engage all direct reports and there is no strain on the managers' time.

      Info-Tech Insight

      47% of direct reports do not agree that their leader is demonstrating the change behaviors. Often, a big reason is that many middle-managers do not understand their own attitudes and beliefs about the change.

      Source: McKinsey & Company “How Do We Manage the Change Journey?”

      Check out Info-Tech’s Build a Better Manager series to support leadership development

      These blueprints will help you create strong IT leaders who can manage their staff and themselves through a transformation.

      Build a Better Manager: Basic Management Skills

      Build a Better Manager: Personal Leadership

      Build a Better Manager: Manage Your People

      Build Successful Teams

      Transparent & Frequent Communication

      Provide employees with several opportunities to hear information and ask questions about the changes.

      Communication must be done with intention

      Include employees in the conversation to get the most out of your change management.

      • Whether it is a part of a large transformation or a redesign to support a specific goal of IT, begin thinking about how you will communicate the anticipated changes and who you will communicate those changes to right away.
      • The first group of people who need to understand why this initiative is important are the other IT leaders. If they are not included in the process and able to understand the foundational drivers of the initiative, you should not continue to try and gain the support of other members within IT.
      • Communication is critical to the success of the organizational redesign.
      • Communicating the right information at the right time will make the difference between losing critical talent and emerging from the transition successfully.
      • The sponsor of this redesign initiative must be able to communicate the rationale of the changes to the other members of leadership, management, and employees.
      • The sponsor and their change management team must then be prepared to accept the questions, comments, and ideas that members of IT might have around the changes.

      "Details about the new organization, along with details of the selection process, should be communicated as they are finalized to all levels of the organization.”

      – Courtney Jackson, “7 Reasons Why Organizational Structures Fail.”

      Two-way communication is necessary

      Recommended action steps:

      • Don't allow rumors to disrupt this initiative – be transparent with people as early as possible.
      • If the organizational restructure will not result in a reduction of staff – let them know! If someone's livelihood (job) is on the line, it increases the likelihood of panic. Let's avoid panic.
      • Provide employees with an opportunity to voice their concerns, questions, and recommendations – so long as you are willing to take that information and address it. Even if the answer to a recommendation is "no" or the answer to a question is "I don't know, but I will find out," you've still let them know their voice was heard in the process.
      • As the CIO, ensure that you are the first person to communicate the changes. You are the sponsor of this initiative – no one else.
      • Create communications that are clear and understandable. Imagine someone who does not work for your organization is hearing the information for the first time. Would they be able to comprehend the changes being suggested?
      • Conduct a pulse survey on the changes to identify whether employees understand the changes and feel heard by the management team.

      Info-Tech Insight

      The project manager of the organizational redesign should not be the communicator. The CIO and the employees’ direct supervisor should always be the communicators of key change messages.

      Communication spectrum

      An approach to communication based on the type of redesign taking place

      ← Business-Mandated Organizational Redesign

      Enable Alignment & Increased Effectiveness

      IT-Driven & Strategic Organizational Redesign →

      Reduction in roles

      Cost savings

      Requires champions who will maintain employee morale throughout

      Communicate with key individuals ahead of time

      Restructure of IT roles

      Increase effectiveness

      Lean on managers & supervisors to provide consistent messaging

      Communicate the individual benefits of the change

      Increase in IT Roles

      Alignment to business model

      Frequent and ongoing communication from the beginning

      Collaborate with IT groups for input on best structure

      Include Employees in the Redesign Process

      Stop talking at employees and ensure they are involved in the changes impacting their day-to-day lives.

      Employees will enable the change

      Old-school approaches to organizational redesign have argued employee engagement is a hinderance to success – it’s not.

      • We often fail to include the employees most impacted by a restructuring in the redesign process. As a result, one of the top reasons employees do not support the change is that they were not included in the change.
      • A big benefit of including employees in the process is it mitigates the emergence of a rumor mill.
      • Moreover, being open to suggestions from staff will help the transformation succeed.
      • Employees can best describe what this transition might entail on a day-to-day basis and the supports they will require to succeed in moving from their current state to their future state.
        • CIOs and other IT leaders are often too far removed from the day-to-day to best describe what will or will not work.
      • When employees feel included in the process, they are more likely to feel like they had a choice in what and how things change.

      "To enlist employees, leadership has to be willing to let things get somewhat messy, through intensive, authentic engagement and the involvement of employees in making the transformation work."

      – Michael D. Watkins & Janet Spencer, “10 Reasons Why Organizational Change Fails.”

      Empowering employees as change agents

      Recommended action steps:

      • Do not tell employees what benefits they will gain from this new change. Instead, ask them what benefits they anticipate.
      • Ask employees what challenges they anticipate, and identify actions that can be taken to minimize those challenges.
      • Identify who the social influencers are in the organization by completing an influencer map. The informal social networks in your organization can be powerful drivers of change when the right individuals are brought onboard.
      • Create a change network using those influencers. The change network includes individuals who represent all levels within the organization and can represent the employee perspective. Use them to help communicate the change and identify opportunities to increase the success of adoption: “Engaging influencers in change programs makes them 3.8 times more likely to succeed," (McKinsey & Company, 2020).
      • Ask members of the change network to identify possible resistors of the new IT structure and inform you of why they might be resisting the changes.

      Info-Tech Insight

      Despite the persistent misconceptions, including employees in the process of a redesign reduces uncertainty and rumors.

      Monitor employee engagement & adoption throughout the redesign

      Only 22% of organizations include the employee experience as a part of the design process

      – The Josh Bersin Company, 2022.
      1 2 3
      Monitor IT Employee Experience

      When Prosci designed their Change Impact Analysis, they identified the ways in which roles will be impacted across 10 different components:

      • Location
      • Process
      • Systems
      • Tools
      • Job roles
      • Critical behaviors
      • Mindset/attitudes/beliefs
      • Reporting structure
      • Performance reviews
      • Compensation

      Engaging employees in the process so that they can define how their role might be impacted across these 10 categories not only empowers the employee, but also ensures they are a part of the process.

      Source: Prosci, 2019.

      Conduct an employee pulse survey

      See the next slide for more information on how to create and distribute this survey.

      Employee Pulse Survey

      Conduct mindful and frequent check-ins with employees

      Process to conduct survey:

      1. Using your desired survey solution (e.g. MS Forms, SurveyMonkey, Qualtrics) input the questions into the survey and send to staff. A template of the survey in MS Forms is available here: IT Organizational Redesign Pulse Survey Template.
      2. When sending to staff, ensure that the survey is anonymous and reinforce this message.
      3. Leverage the responses from the survey to learn where there might be opportunities to improve the transformation experience (aligning the structure to the vision, employee inclusion, communication, or managerial support for the change). Review the recommended action steps in this research set for help.
      4. This assessment is intended for frequent but purposeful use. Only send out the survey when you have taken actions in order to improve adoption of the change or have provided communications. The Employee Pulse Survey should be reevaluated on a regular basis until adoption across all four categories reaches the desired state (80-100% adoption is recommended).

      The image contains a screenshot of the employee pulse survey.

      Define Key Metrics of Adoption & Success

      Metrics have a dual benefit of measuring successful implementation and meeting the original drivers.

      Measuring the implementation is a two-pronged approach

      Both employee adoption and the transformation of the IT structure need to be measured during implementation

      • Organizations that are going through any sort of transformation – such as organizational redesign – should be measuring whether they are successfully on track to meet their target or have already met that goal.
      • Throughout the organizational structure transition, a major factor that will impact the success of that goal is employee willingness to move forward with the changes.
      • However, rather than measuring these two components using hard data, we rely on gut checks that let us know if we think we are on track to gaining adoption and operating in the desired future state.
      • Given how fluid employees and their responses to change can be, conducting a pulse survey at a regular (but strategically identified) interval will provide insight into where the changes will be adopted or resisted.

      “Think about intentionally measuring at the moments in the change storyline where feedback will allow leaders to make strategic decisions and interventions.”

      – Bradley Wilson, “Employee Survey Questions: The Ultimate Guide.”

      Report that the organizational redesign for IT was a success

      Recommended action steps:

      • Create clear metrics related to how you will measure the success of the organizational redesign, and communicate those metrics to people. Ensure the metrics are not contrary to the goals of other initiatives or team outcomes.
      • Create one set of metrics related to adoption and another set of metrics tied to the successful completion of the project objective.
        • Are people changing their attitudes and behaviors to reflect the required outcome?
        • Are you meeting the desired outcome of the organizational redesign?
      • Use the metrics to inform how you move forward. Do not attempt the next phase of the organizational transformation before employees have clearly indicated a solid understanding of the changes.
      • Ensure that any metrics used to measure success will not negatively interfere with another team’s progress. The metrics of the group need to work together, not against each other.

      Info-Tech Insight

      Getting 100% adoption from employees is unlikely. However, if employee adoption is not sitting in the 80-90% range, it is not recommended that you move forward with the next phase of the transformation.

      Example sustainment metrics

      Driver Goal Measurement Key Performance Indicator (KPI)
      Workforce Challenges and Increased Effectiveness Employee Engagement The change in employee engagement before, during, and after the new organizational structure is communicated and implemented.
      Increased Effectiveness Alignment of Demand to Resources Does your organization have sufficient resources to meet the demands being placed on your IT organization?
      Increased Effectiveness and Workforce Challenges Role Clarity An increase in role clarity or a decrease in role ambiguity.

      Increased Effectiveness

      Reduction in Silos

      Employee effectiveness increases by 27% and efficiency by 53% when provided with role clarity (Effectory, 2019).
      Increased Effectiveness Reduction in Silos Frequency of communication channels created (scrum meetings, Teams channels, etc.) specific to the organizational structure intended to reduce silos.
      Operating in a New Org. Structure Change Adoption Rate The percentage of employees who have adopted their defined role within the new organizational chart in 3-, 6-, and 12-month increments.
      Workforce Challenges Turnover Rate The number of employees who voluntarily leave the organization, citing the organizational redesign.
      Workforce Challenges Active Resistors The number of active resistors anticipated related to the change in organizational structure versus the number of active resistors that actually present themselves to the organizational restructuring.
      New Capabilities Needed Gap in Capability Delivery The increase in effectiveness in delivering on new capabilities to the IT organization.
      Operating in a New Org. Structure Change Adoption Rate The percentage of employees who found the communication around the new organizational structure clear, easy to understand, and open to expressing feedback.
      Lack of Business Understanding or Increased Effectiveness Business Satisfaction with IT Increase in business satisfaction toward IT products and services.
      Workforce Challenges Employee Performance Increase in individual employee performances on annual/bi-annual reviews.
      Adoption Pulse Assessment Increase in overall adoption scores on pulse survey.
      Adoption Communication Effectiveness Reduction in the number of employees who are still unsure why the changes are required.
      Adoption Leadership Training Percentage of members of leadership attending training to support their development at the managerial level.

      Change Management ≠ Project Management

      Stop treating the two interchangeably.

      IT organizations struggle to mature their OCM capabilities

      Because frankly they didn’t need it

      • Change management is all about people.
      • If the success of your organization is dependent on this IT restructuring, it is important to invest the time to do it right.
      • This means it should not be something done off the side of someone's desk.
      • Hire a change manager or look to roles that have a responsibility to deliver on organizational change management.
      • While project success is often measured by if it was delivered on time, on budget, and in scope, change management is adaptable. It can move backward in the process to secure people's willingness to adopt the required behaviors.
      • Strategic organizations recognize it’s not just about pushing an initiative or project forward. It’s about making sure that your employees are willing to move that initiative forward too.
      • A major organizational transformation initiative like restructuring requires you lean into employee adoption and buy-in.

      “Only if you have your employees in mind can you implement change effectively and sustainably.”

      – Creaholic Pulse Feedback, “Change Management – And Why It Has to Change.”

      Take the time to educate & communicate

      Recommended action steps:

      • Do not treat change management and project management as synonymous.
      • Hire a change manager to support the organizational redesign transformation.
      • Invest the resources (time, money, people) that can support the change and enable its success. This can look like:
        • Training and development.
        • Hiring the right people.
        • Requesting funds during the redesign process to support the transition.
      • Create a change management plan – and be willing to adjust the timelines or actions of this plan based on the feedback you receive from employees.
      • Implement the new organizational structure in a phased approach. This allows time to receive feedback and address any fears expressed by staff.

      Info-Tech Insight

      OCM is often not included or used due to a lack of understanding of how it differs from project management.

      And an additional five experts across a variety of organizations who wish to remain anonymous.

      Research Contributors and Experts

      Info-Tech Research Group

      Amanda Mathieson Research Director Heather Munoz Executive Counselor Valence Howden Principal Research Director
      Ugbad Farah Research Director Lisa Hager Duncan Executive Counselor Alaisdar Graham Executive Counselor
      Carlene McCubbin Practice Lead

      Related Info-Tech Research

      Redesign Your IT Organizational Structure

      Build a Strategic IT Workforce Plan

      Implement a New IT Organizational Structure

      • Organizational redesign is only as successful as the process leaders engage in.
      • Benchmarking your organizational redesign to other organizations will not work.
      • 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.
      • A well-defined strategic workforce plan (SWP) isn’t just a nice-to-have, it’s a must-have.
      • Integrate as much data as possible into your workforce plan to best prepare you for the future. Without knowledge of your future initiatives, you are filling hypothetical holes.
      • To be successful, you need to understand your strategic initiatives, workforce landscape, and external and internal trends.
      • Organizational design implementations can be highly disruptive for IT staff and business partners. Without a structured approach, IT leaders may experience high turnover, decreased productivity, and resistance to change.
      • CIOs walk a tightrope as they manage operational and emotional turbulence while aiming to improve business satisfaction with IT. Failure to achieve balance could result in irreparable failure.

      Bibliography

      Aronowitz, Steven, et al. “Getting Organizational Design Right,” McKinsey, 2015. Web.
      Ayers, Peg. “5 Ways to Engage Your Front-Line Staff.” Taylor Reach Group, 2019. Web.
      Bushard, Brian, and Carlie Porterfield. “Meta Reportedly Scales Down, Again – Here Are the Major US Layoffs This Year.” Forbes, September 28, 2022. Web.
      Caruci, Ron. “4 Organizational Design Issues that Most Leaders Misdiagnose.” Harvard Business Review, 2019.
      “Change Management – And Why It Has to Change.” Creaholic Pulse Feedback. Web.
      “Communication Checklist for Achieving Change Management.” Prosci, 27 Oct. 2022. Web.
      “Defining Change Impact.” Prosci. 29 May 2019. Web.
      “The Definitive Guide To Organization Design.” The Josh Bersin Company, 2022.
      Deshler, Reed. “Five Reasons Organizational Redesigns Fail to Deliver.” AlignOrg. 28 Jan. 2020. Web.
      The Fit for Growth Mini Book. PwC, 12 Jan. 2017.
      Helfand, Heidi. Dynamic Reteaming: The Art and Wisdom of Changing Teams. 2nd ed., O’Reilly Media, 2020.
      Jackson, Courtney. “7 Reasons Why Organizational Structures Fail.” Scott Madden Consultants. Web.
      Livijn, Marianne. Managing Organizational Redesign: How Organizations Relate Macro and Micro Design. Doctoral dissertation. Department of Management, Aarhus University, 2020.
      Lutke, Tobias. “Changes to Shopify’s Team.” Shopify. 26 July 2022.
      McKinsey & Company. “How Do We Manage the Change Journey?” McKinsey & Company.2020.
      Pijnacker, Lieke. “HR Analytics: Role Clarity Impacts Performance.” Effectory, 29 Sept. 2019. Web.
      Tompkins, Teri C., and Bruce G. Barkis. “Conspiracies in the Workplace: Symptoms and Remedies.” Graziadio Business Review, vol. 21, no. 1, 2021.Web.
      “Understanding Organizational Structures.” SHRM,2022.
      Watkins, Michael D., and Janet Spencer. “10 Reasons Why Organizational Change Fails.” I by IMD, 10 March 2021. Web.
      Wilson, Bradley. “Employee Survey Questions: The Ultimate Guide.” Perceptyx, 1 July 2020. Web.

      The Complete Manual for Layoffs

      • Buy Link or Shortcode: {j2store}514|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $30,999 Average $ Saved
      • member rating average days saved: 20 Average Days Saved
      • Parent Category Name: Lead
      • Parent Category Link: /lead

      When the economy is negatively influenced by factors beyond any organization’s control, the impact can be felt almost immediately on the bottom line. This decline in revenue as a result of a weakening economy will force organizations to reconsider every dollar they spend.

      Our Advice

      Critical Insight

      • The remote work environment many organizations find themselves in adds a layer of complexity to the already sensitive process of laying off employees.
      • Carrying out layoffs must be done while keeping personal contact as your first priority. That personal contact should be the basis for all subsequent communication with laid-off and remaining staff, even after layoffs have occurred.

      Impact and Result

      By following our process, we can provide your organization with the direction, tools, and best practices to lay off employees. This will need to be done with careful consideration into your organization’s short- and longer-term strategic goals.

      The Complete Manual for Layoffs Research & Tools

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

      1. Prepare for layoffs

      Understand the most effective cost-cutting solutions and set layoff policies and guidelines.

      • The Complete Manual for Layoffs Storyboard
      • Layoffs SWOT Analysis Template
      • Redeployment and Layoff Strategy Workbook
      • Sample Layoffs Policy
      • Cost-Cutting Planning Tool
      • Termination Costing Tool

      2. Objectively identify employees

      Develop an objective layoff selection method and plan for the transfer of essential responsibilities.

      • Workforce Planning Tool
      • Employee Layoff Selection Tool

      3. Prepare to meet with employees

      Plan logistics, training, and a post-layoff plan communication.

      • Termination Logistics Tool
      • IT Knowledge Transfer Risk Assessment Tool
      • IT Knowledge Transfer Plan Template
      • IT Knowledge Identification Interview Guide Template
      • Knowledge Transfer Job Aid
      • Layoffs Communication Package

      4. Meet with employees

      Collaborate with necessary departments and deliver layoffs notices.

      • Employee Departure Checklist Tool

      5. Monitor and manage departmental effectiveness

      Plan communications for affected employee groups and monitor organizational performance.

      • Ten Ways to Connect With Your Employees
      • Creating Connections
      [infographic]

      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.

      Choose a Right-Sized Contact Center Solution

      • Buy Link or Shortcode: {j2store}334|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $25,535 Average $ Saved
      • member rating average days saved: 18 Average Days Saved
      • Parent Category Name: Strategy and Organizational Design
      • Parent Category Link: /strategy-and-organizational-design
      • IT needs a method to pinpoint which contact center solution best aligns with business objectives, adapting to a post-COVID world of remote work, flexibility, and scalability.
      • Scoring RFP and RFQ proposals is a complex process, and it is difficult to map and gap without a clear view of the organization’s needs. SOWs can contain pitfalls that cause expensive headaches for the organization in the long run. Guidance through a SOW is required to best represent the organization’s interests.

      Our Advice

      Critical Insight

      • “On-premises versus cloud” is a false dichotomy. Contact center architectures come in all shapes and sizes, and organizations should discern whether a hybrid option best meets their needs.
      • Contact centers should service customers – not capabilities. Capabilities must work for you, your agents, and your customers – not the other way around.
      • Deliverables and responsibilities should be a contract’s focal point. While organizations are right to focus on avoiding unanticipated license charges, it is more important to clearly define how deliverables and responsibilities will be divided among the organization, the vendor, and potential third parties.

      Impact and Result

      • Assess the array of contact center architectures with Info-Tech’s Contact Center Decision Points Tool to select a right-sized solution.
      • Build business requirements in a formalized process to achieve stakeholder buy-in.
      • Use Info-Tech’s Contact Center RFP Scoring Tool to evaluate and choose from a range of vendors.
      • Successfully navigate and avoid major pitfalls in a SOW construction.
      • Justify each stage of the process with this blueprint’s key deliverable: the Contact Center Playbook.

      Choose a Right-Sized Contact Center Solution Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to examine the current contact center marketspace, review Info-Tech’s methodology for choosing a right-sized contact center solution, 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 Contact Center Architectures

      Establish your project vision and metrics of success before shortlisting potential contact center architectures and deciding which is right-sized for the organization.

      • Choose a Right-Sized Contact Center Solution – Phase 1: Assess Contact Center Architectures
      • Contact Center Playbook
      • Contact Center Decision Points Tool

      2. Gather Requirements and Shortlist Vendors

      Build business requirements to achieve stakeholder buy-in, define key deliverables, and issue an RFP/RFQ to shortlisted vendors.

      • Choose a Right-Sized Contact Center Solution – Phase 2: Gather Requirements and Shortlist Vendors
      • Requirements Gathering Documentation Tool
      • Lean RFP Template
      • Contact Center Business Requirements Document
      • Request for Quotation Template
      • Long-Form RFP Template

      3. Score Vendors and Construct SOW

      Score RFP/RFQ responses and decide upon a vendor before constructing a SOW.

      • Choose a Right-Sized Contact Center Solution – Phase 3: Score Vendors and Construct SOW
      • Contact Center RFP Scoring Tool
      • Contact Center SOW Template and Guide
      [infographic]

      Workshop: Choose a Right-Sized Contact Center 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 Assess Architecture

      The Purpose

      Shortlist and decide upon a right-sized contact center architecture.

      Key Benefits Achieved

      A high-level decision for a right-sized architecture

      Activities

      1.1 Define vision and mission statements.

      1.2 Identify infrastructure metrics of success.

      1.3 Confirm key performance indicators for contact center operations.

      1.4 Complete architecture assessment.

      1.5 Confirm right-sized architecture.

      Outputs

      Project outline

      Metrics of success

      KPIs confirmed

      Quickly narrow down right-sized architecture

      Decision on right-sized contact center architecture

      2 Gather Requirements

      The Purpose

      Build business requirements and define key deliverables to achieve stakeholder buy-in and shortlist potential vendors.

      Key Benefits Achieved

      Key deliverables defined and a shortlist of no more than five vendors

      Sections 7-8 of the Contact Center Playbook completed

      Activities

      2.1 Hold focus groups with key stakeholders.

      2.2 Gather business, nonfunctional, and functional requirements.

      2.3 Define key deliverables.

      2.4 Shortlist five vendors that appear meet those requirements.

      Outputs

      User requirements identified

      Business Requirements Document completed

      Key deliverables defined

      Shortlist of five vendors

      3 Initial Vendor Scoring

      The Purpose

      Compare and evaluate shortlisted vendors against gathered requirements.

      Key Benefits Achieved

      Have a strong overview of which vendors are preferred for issuing RFP/RFQ

      Section 9 of the Contact Center Playbook

      Activities

      3.1 Input requirements to the Contact Center RFP Scoring Tool. Define which are mandatory and which are desirable.

      3.2 Determine which vendors best meet requirements.

      3.3 Compare requirements met with anticipated TCO.

      3.4 Compare and rank vendors.

      Outputs

      An assessment of requirements

      Vendor scoring

      A holistic overview of requirements scoring and vendor TCO

      An initial ranking of vendors to shape RFP process after workshop end

      4 SOW Walkthrough

      The Purpose

      Walk through the Contact Center SOW Template and Guide to identify how much time to allocate per section and who will be responsible for completing it.

      Key Benefits Achieved

      An understanding of a SOW that is designed to avoid major pitfalls with vendor management

      Section 10 of the Contact Center Playbook

      Activities

      4.1 Get familiar with the SOW structure.

      4.2 Identify which sections will demand greater time allocation.

      4.3 Strategize how to avoid potential pitfalls.

      4.4 Confirm reviewer responsibilities.

      Outputs

      A broad understanding of a SOW’s key sections

      A determination of how much time should be allocated for reviewing major sections

      A list of ways to avoid major pitfalls with vendor management

      A list of reviewers, the sections they are responsible for reviewing, and their time allocation for their review

      5 Communicate and Implement

      The Purpose

      Finalize deliverables and plan post-workshop communications.

      Key Benefits Achieved

      A completed Contact Center Playbook that justifies each decision of this workshop

      Activities

      5.1 Finalize deliverables.

      5.2 Support communication efforts.

      5.3 Identify resources in support of priority initiatives.

      Outputs

      Contact Center Playbook delivered

      Post-workshop engagement to confirm satisfaction

      Follow-up research that complements the workshop or leads workshop group in relevant new directions

      Optimize the Current Testing Process for Enterprise Mobile Applications

      • Buy Link or Shortcode: {j2store}404|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: Testing, Deployment & QA
      • Parent Category Link: /testing-deployment-and-qa
      • Your team has little or no experience in mobile testing.
      • You need to optimize current testing processes to include mobile.
      • You need to conduct an RFP for mobile testing tools.

      Our Advice

      Critical Insight

      • One-size-fits-all testing won’t work for mobile. The testing tools are fragmented.
      • Mobile offers many new test cases, so organizations can expect to spend more time testing.

      Impact and Result

      • Identify and address gaps between your current testing process and a target state that includes mobile testing.
      • Establish project value metrics to ensure business and technical requirements are met.

      Optimize the Current Testing Process for Enterprise Mobile Applications Research & Tools

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

      1. Assess the current testing state

      Determine a starting point for architecture and discuss pain points that will drive reusability.

      • Storyboard: Optimize the Current Testing Process for Enterprise Mobile Applications
      • Mobile Testing Project Charter Template
      • Visual SOP Template for Application Testing

      2. Determine the target state testing framework

      Document a preliminary list of test requirements and create vendor RFP and scoring.

      • Test Requirements Tool
      • Request for Proposal (RFP) Template

      3. Implement testing tools to support the testing SOP

      Create an implementation rollout plan.

      • Project Planning and Monitoring Tool

      Infographic

      Workshop: Optimize the Current Testing Process for Enterprise Mobile Applications

      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 Fit for Test Process Optimization

      The Purpose

      Understand mobile testing pain points.

      Evaluate current statistics and challenges around mobile testing and compare with your organization.

      Realize the benefits of mobile testing.

      Understand the differences of mobile testing.

      Assess your readiness for optimizing testing to include mobile.

      Key Benefits Achieved

      Preliminary understanding of how mobile testing is different from conventional approaches to testing apps.

      Understanding of how mobile testing can optimize your current testing process.

      Activities

      1.1 Understand the pain points experienced with mobile testing

      1.2 Evaluate current statistics and challenges of mobile testing and compare your organization

      1.3 Realize the benefits that come from mobile testing

      1.4 Understand the differences between mobile app testing and conventional app testing

      1.5 Assess your readiness for optimizing the testing process to include mobile

      Outputs

      Organizational state assessment for mobile testing

      2 Structure & Launch the Project

      The Purpose

      Identify stakeholders for testing requirements gathering.

      Create a project charter to obtain project approval.

      Present and obtain project charter sign-off.

      Key Benefits Achieved

      Well documented project charter.

      Approval to launch the project.

      Activities

      2.1 Identify stakeholders for testing requirements gathering

      2.2 Create a project charter to obtain project approval

      2.3 Present & obtain project charter sign-off

      Outputs

      Project objectives and scope

      Project roles and responsibilities

      3 Assess Current Testing State

      The Purpose

      Document your current non-mobile testing processes.

      Create a current testing visual SOP.

      Determine current testing pain points.

      Key Benefits Achieved

      Thorough understanding of current testing processes and pain points.

      Activities

      3.1 Document your current non-mobile testing processes

      3.2 Create a current state visual SOP

      3.3 Determine current testing pain points

      Outputs

      Documented current testing processes in the form of a visual SOP

      List of current testing pain points

      4 Determine Target State Testing Framework

      The Purpose

      Determine your target state for mobile testing.

      Choose vendors for the RFP process.

      Evaluate selected vendor(s) against testing requirements.

      Design mobile testing visual SOP(s).

      Key Benefits Achieved

      Prioritized list of testing requirements for mobile.

      Vendor selection for mobile testing solutions through an RFP process.

      New SOP designed to include both current testing and mobile testing processes.

      Activities

      4.1 Determine your target state for mobile testing by following Info-Tech’s framework as a starting point

      4.2 Design new SOP to include testing for mobile apps

      4.3 Translate all considered visual SOP mobile injections into requirements

      4.4 Document the preliminary list of test requirements in the RFP

      4.5 Determine which vendors to include for the RFP process

      4.6 Reach out to vendors for a request for proposal

      4.7 Objectively evaluate vendors against testing requirements

      4.8 Identify and assess the expected costs and impacts from determining your target state

      Outputs

      List of testing requirements for mobile

      Request for Proposal

      5 Implement Testing Tools to Support Your Testing SOP

      The Purpose

      Develop an implementation roadmap to integrate new testing initiatives.

      Anticipate potential roadblocks during implementation rollout.

      Operationalize mobile testing and ensure a smooth hand-off to IT operations.

      Key Benefits Achieved

      Creation of implementation project plan.

      List of approaches to mitigate potential implementation roadblocks.

      Achieving clean hand-off to IT ops team.

      Activities

      5.1 Develop a project plan to codify your current understanding of the scope of work

      5.2 Anticipate potential roadblocks during your tool’s implementation

      5.3 Operationalize your testing tools and ensure a smooth hand-off from the project team

      Outputs

      Mobile testing metrics implementation plan

      6 Conduct Your Retrospectives

      The Purpose

      Conduct regular retrospectives to consider areas for improvement.

      Adjust your processes, systems, and testing tools to improve performance and usability.

      Revisit implementation metrics to communicate project benefits.

      Leverage the lessons learned and apply them to other projects.

      Key Benefits Achieved

      Project specific metrics.

      Discovery of areas to improve.

      Activities

      6.1 Conduct regular retrospectives to consider areas for improvement

      6.2 Revisit your implementation metrics to communicate project benefits to business stakeholders

      6.3 Adjust your processes, systems, and testing tools to improve performance and usability

      6.4 Leverage the lessons learned and apply them to other IT projects

      Outputs

      Steps to improve your mobile testing

      Build a Security Metrics Program to Drive Maturity

      • Buy Link or Shortcode: {j2store}266|cart{/j2store}
      • member rating overall impact: 9.5/10 Overall Impact
      • member rating average dollars saved: $22,947 Average $ Saved
      • member rating average days saved: 8 Average Days Saved
      • Parent Category Name: Security Processes & Operations
      • Parent Category Link: /security-processes-and-operations
      • Many security leaders put off adding metrics to their program because they don't know where to start or how to assess what is worth measuring.
      • Sometimes, this uncertainty causes the belief that their security programs are not mature enough for metrics to be worthwhile.
      • Because metrics can become very technical and precise,it's easy to think that they're inherently complicated (not true).

      Our Advice

      Critical Insight

      • The best metrics are tied to goals.
      • Tying your metrics to goals ensures that you are collecting metrics for a specific purpose rather than just to watch the numbers change.

      Impact and Result

      • A metric, really, is just a measure of success against a given goal. Gradually, programs will achieve their goals and set new more specific goals, and with them come more-specific metrics.
      • It is not necessary to jump into highly technical metrics right away. A lot can be gained from metrics that track behaviors.
      • A metrics program can be very simple and still effectively demonstrate the value of security to the organization. The key is to link your metrics to the goals or objectives the security team is pursuing, even if they are simple implementation plans (e.g. percentage of departments that have received security training course).

      Build a Security Metrics Program to Drive Maturity Research & Tools

      Start here – read the Executive Brief

      Read our concise Executive Brief to find out why you should build a security metrics 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. Link security metrics to goals to boost maturity

      Develop goals and KPIs to measure your progress.

      • Build a Security Metrics Program to Drive Maturity – Phase 1: Link Security Metrics to Goals to Boost Maturity
      • Security Metrics Determination and Tracking Tool
      • KPI Development Worksheets

      2. Adapt your reporting strategy for various metric types

      Learn how to present different types of metrics.

      • Build a Security Metrics Program to Drive Maturity – Phase 2: Adapt Your Reporting Strategy for Various Metric Types
      • Security Metrics KPX Dashboard
      • Board-Level Security Metrics Presentation Template
      [infographic]

      Workshop: Build a Security Metrics Program to Drive Maturity

      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 Current State, Initiatives, and Goals

      The Purpose

      Create a prioritized list of goals to improve the security program’s current state.

      Key Benefits Achieved

      Insight into the current program and the direct it needs to head in.

      Activities

      1.1 Discuss current state and existing approach to metrics.

      1.2 Review contract metrics already in place (or available).

      1.3 Determine security areas that should be measured.

      1.4 Determine what stakeholders are involved.

      1.5 Review current initiatives to address those risks (security strategy, if in place).

      1.6 Begin developing SMART goals for your initiative roadmap.

      Outputs

      Gap analysis results

      SMART goals

      2 KPI Development

      The Purpose

      Develop unique KPIs to measure progress against your security goals.

      Key Benefits Achieved

      Learn how to develop KPIs

      Prioritized list of security goals

      Activities

      2.1 Continue SMART goal development.

      2.2 Sort goals into types.

      2.3 Rephrase goals as KPIs and list associated metric(s).

      2.4 Continue KPI development.

      Outputs

      KPI Evolution Worksheet

      3 Metrics Prioritization

      The Purpose

      Determine which metrics will be included in the initial program launch.

      Key Benefits Achieved

      A set of realistic and manageable goals-based metrics.

      Activities

      3.1 Lay out prioritization criteria.

      3.2 Determine priority metrics (implementation).

      3.3 Determine priority metrics (improvement & organizational trend).

      Outputs

      Prioritized metrics

      Tool for tracking and presentation

      4 Metrics Reporting

      The Purpose

      Strategize presentation based around metric type to indicate organization’s risk posture.

      Key Benefits Achieved

      Develop versatile reporting techniques

      Activities

      4.1 Review metric types and discuss reporting strategies for each.

      4.2 Develop a story about risk.

      4.3 Discuss the use of KPXs and how to scale for less mature programs.

      Outputs

      Key Performance Index Tool and presentation materials

      Further reading

      Build a Security Metrics Program to Drive Maturity

      Good metrics come from good goals.

      ANALYST PERSPECTIVE

      Metrics are a maturity driver.

      "Metrics programs tend to fall into two groups: non-existent and unhelpful.

      The reason so many security professionals struggle to develop a meaningful metrics program is because they are unsure of what to measure or why.

      The truth is, for metrics to be useful, they need to be tied to something you care about – a state you are trying to achieve. In other words, some kind of goal. Used this way, metrics act as the scoreboard, letting you know if you’re making progress towards your goals, and thus, boosting your overall maturity."

      Logan Rohde, Research Analyst, Security Practice Info-Tech Research Group

      Executive summary

      Situation

      • Many security leaders put off adding metrics to their program because they don't know where to start or how to assess what is worth measuring.

      Complication

      • Sometimes, this uncertainty causes the belief that their security programs are not mature enough for metrics to be worthwhile.
      • Because metrics can become very technical and precise, it's easy to think they're inherently complicated (not true).

      Resolution

      • A metric, really, is just a measure of success against a given goal. Gradually, programs will achieve their goals and set new, more specific goals, and with them comes more specific metrics.
      • It is not necessary to jump into highly technical metrics right away. A lot can be gained from metrics that track behaviors.
      • A metrics program can be very simple and still effectively demonstrate the value of security to the organization. The key is to link your metrics to the goals or objectives the security team is pursuing, even if they are simple implementation plans (e.g. percentage of departments that have received security training).

      Info-Tech Insight

      1. Metrics lead to maturity, not vice versa
        • Tracking metrics helps you assess progress and regress in your security program. This helps you quantify the maturity gains you’ve made and continue to make informed strategic decisions.
      2. The best metrics are tied to goals
        • Tying your metrics to goals ensures that you are collecting metrics for a specific purpose rather than just to watch the numbers change.

      Our understanding of the problem

      This Research is Designed For:

      • CISO

      This Research Will Help You:

      • Understand the value of metrics.
      • Right-size a metrics program based on your organization’s maturity and risk profile.
      • Tie metrics to goals to create meaningful KPIs.
      • Develop strategies to effectively communicate the right metrics to stakeholders.

      This Research Will Also Assist:

      • CIO
      • Security Manager
      • Business Professionals

      This Research Will Help Them:

      • Become informed on the metrics that matter to them.
      • Understand that investment in security is an investment in the business.
      • Feel confident in the progress of the organization’s security strategy.

      Info-Tech’s framework integrates several best practices to create a best-of-breed security framework

      Information Security Framework

      Governance

      • Context and Leadership
        • Information Security Charter
        • Information Security Organizational Structure
        • Culture and Awareness
      • Evaluation and Direction
        • Security Risk Management
        • Security Policies
        • Security Strategy and Communication
      • Compliance, Audit, and Review
        • Security Compliance Management
        • External Security Audit
        • Internal Security Audit
        • Management Review of Security

      Management

      • Prevention
        • Identity Security
          • Identity and Access Management
        • Data Security
          • Hardware Asset Management
          • Data Security & Privacy
        • Infrastructure Security
          • Network Security
          • Endpoint Security
          • Malicious Code
          • Application Security
          • Vulnerability Management
          • Cryptography Management
          • Physical Security
          • Cloud Security
        • HR Security
          • HR Security
        • Change and Support
          • Configuration and Change Management
          • Vendor Management
      • Detection
        • Security Threat Detection
        • Log and Event Management
      • Response and Recovery
        • Security Incident Management
        • Information Security in BCM
        • Security eDiscovery and Forensics
        • Backup and Recovery
      • Measurement
        • Metrics Program
        • Continuous Improvement

      Metrics help to improve security-business alignment

      While business leaders are now taking a greater interest in cybersecurity, alignment between the two groups still has room for improvement.

      Key statistics show that just...

      5% of public companies feel very confident that they are properly secured against a cyberattack.

      41% of boards take on cybersecurity directly rather than allocating it to another body (e.g. audit committee).

      19% of private companies do not discuss cybersecurity with the board.

      (ISACA, 2018)

      Info-Tech Insight

      Metrics help to level the playing field

      Poor alignment between security and the business often stems from difficulties with explaining how security objectives support business goals, which is ultimately a communication problem.

      However, metrics help to facilitate these conversations, as long as the metrics are expressed in practical, relatable terms.

      Security metrics benefit the business

      Executives get just as much out of management metrics as the people running them.

      1. Metrics assuage executives’ fears
        • Metrics help executives (and security leaders) feel more at ease with where the company is security-wise. Metrics help identify areas for improvement and gaps in the organization’s security posture that can be filled. A good metrics program will help identify deficiencies in most areas, even outside the security program, helping to identify what work needs to be done to reduce risk and increase the security posture of the organization.
      2. Metrics answer executives’ questions
        • Numbers either help ease confusion or signify other areas for improvement. Offering quantifiable evidence, in a language that the business can understand, offers better understanding and insight into the information security program. Metrics also help educate on types of threats, staff needed for security, and budget needs to decrease risk based on management’s threat tolerance. Metrics help make an organization more transparent, prepared, and knowledgeable.
      3. Metrics help to continually prove security’s worth
        • Traditionally, the security team has had to fight for a seat at the executive table, with little to no way to communicate with the business. However, the new trend is that the security team is now being invited before they have even asked to join. This trend allows the security team to better communicate on the organization’s security posture, describe threats and vulnerabilities, present a “plan of action,” and get a pulse on the organization’s risk tolerance.

      Common myths make security metrics seem challenging

      Security professionals have the perception that metrics programs are difficult to create. However, this attitude usually stems from one of the following myths. In reality, security metrics are much simpler than they seem at first, and they usually help resolve existing challenges rather than create new ones.

      Myth Truth
      1 There are certain metrics that are important to all organizations, based on maturity, industry, etc. Metrics are indications of change; for a metric to be useful it needs to be tied to a goal, which helps you understand the change you're seeing as either a positive or a negative. Industry and maturity have little bearing here.
      2 Metrics are only worthwhile once a certain maturity level is reached Metrics are a tool to help an organization along the maturity scale. Metrics help organizations measure progress of their goals by helping them see which tactics are and are not working.
      3 Security metrics should focus on specific, technical details (e.g. of systems) Metrics are usually a means of demonstrating, objectively, the state of a security program. That is, they are a means of communicating something. For this reason, it is better that metrics be phrased in easily digestible, non-technical terms (even if they are informed by technical security statistics).

      Tie your metrics to goals to make them worthwhile

      SMART metrics are really SMART goals.

      Specific

      Measurable

      Achievable

      Realistic

      Timebound

      Achievable: What is an achievable metric?

      When we say that a metric is “achievable,” we imply that it is tied to a goal of some kind – the thing we want to achieve.

      How do we set a goal?

      1. Determine what outcome you are trying to achieve.
        • This can be small or large (e.g. I want to determine what existing systems can provide metrics, or I want a 90% pass rate on our monthly phishing tests).
      2. Decide what indicates that you’ve achieved your goal.
        • At what point would you be satisfied with the progress made on the initiative(s) you’re working on? What conditions would indicate victory for you and allow you to move on to another goal?
      3. Develop a key performance indicator (KPI) to measure progress towards that goal.
        • Now that you’ve defined what you’re trying to achieve, find a way to indicate progress in relative or relational terms (e.g. percentage change from last quarter, percentage of implementation completed, ratio of programs in place to those still needing implementation).

      Info-Tech’s security metrics methodology is repeatable and iterative to help boost maturity

      Security Metric Lifecycle

      Start:

      Review current state and decide on priorities.

      Set a SMART goal for improvement.

      Develop an appropriate KPI.

      Use KPI to monitor program improvement.

      Present metrics to the board.

      Revise metrics if necessary.

      Metrics go hand in hand with your security strategy

      A security strategy is ultimately a large goal-setting exercise. You begin by determining your current maturity and how mature you need to be across all areas of information security, i.e. completing a gap analysis.

      As such, linking your metrics program to your security strategy is a great way to get your metrics program up and running – but it’s not the only way.

      Check out the following Info-Tech resource to get started today:

      Build an Information Security Strategy

      The value of security metrics goes beyond simply increasing security

      This blueprint applies to you whether you need to develop a metrics program from scratch or optimize and update your current strategy.

      Value of engaging in security metrics:

      • Increased visibility into your operations.
      • Improved accountability.
      • Better communication with executives as a result of having hard evidence of security performance.
      • Improved security posture through better understanding of what is working and what isn’t within the security program.

      Value of Info-Tech’s security metrics blueprint:

      • Doesn’t overwhelm you and allows you to focus on determining the metrics you need to worry about now without pressuring you to do it all at once.
      • Helps you develop a growth plan as your organization and metrics program mature, so you continue to optimize.
      • Creates effective communication. Prepares you to present the metrics that truly matter to executives rather than confusing them with unnecessary data. Pay attention to metric accuracy and reproducibility. No management wants inconsistent reporting.

      Impact

      Short term: Streamline your program. Based on your organization’s specific requirements and risk profile, figure out which metrics are best for now while also planning for future metrics as your organization matures.

      Long term: Once the program is in place, improvements will come with increased visibility into operations. Investments in security will be encouraged when more evidence is available to executives, contributing to overall improved security posture. Potential opportunities for eventual cost savings also exist as there is more informed security spending and fewer incidents.

      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

      Link Security Metrics to Goals to Boost Maturity – Project Overview

      1. Link Security Metrics to Goals to Boost Maturity 2. Adapt Your Reporting Strategy for Various Metric Types
      Best-Practice Toolkit

      1.1 Review current state and set your goals

      1.2 Develop KPIs and prioritize your goals

      1.3 Implement and monitor the KPI to track goal progress

      2.1 Review best practices for presenting metrics

      2.2 Strategize your presentation based on metric type

      2.3 Tailor presentation to your audience

      2.4 Use your metrics to create a story about risk

      2.5 Revise your metrics

      Guided Implementations
      • Call 1: Setting Goals
      • Call 2: KPI Development
      • Call 1: Best Practices and Reporting Strategy
      • Call 2: Build a Dashboard and Presentation Deck
      Onsite Workshop Module 1: Current State, Initiatives, Goals, and KPIs Module 2: Metrics Reporting

      Phase 1 Outcome:

      • KPI development and populated metrics tracking tool.

      Phase 2 Outcome:

      • Reporting strategy with dashboard and presentation deck.

      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 Workshop Day 5
      Activities

      Current State, Initiatives, and Goals

      • Discuss current state and existing approach to metrics.
      • Review contract metrics already in place (or available).
      • Determine security areas that should be measured.
      • Determine which stakeholders are involved.
      • Review current initiatives to address those risks (security strategy, if in place).
      • Begin developing SMART goals for your initiative roadmap.

      KPI Development

      • Continue SMART goal development.
      • Sort goals into types.
      • Rephrase goals as KPIs and list associated metric(s).
      • Continue KPI development.

      Metrics Prioritization

      • Lay out prioritization criteria.
      • Determine priority metrics (implementation).
      • Determine priority metrics (improvement & organizational trend).

      Metrics Reporting

      • Review metric types and discuss reporting strategies for each.
      • Develop a story about risk.
      • Discuss the use of KPXs and how to scale for less mature programs.

      Offsite Finalization

      • Review and finalization of documents drafted during workshop.
      Deliverables
      1. Gap analysis results
      1. Completed KPI development templates
      1. Prioritized metrics and tool for tracking and presentation.
      1. Key Performance Index tool and presentation materials.
      1. Finalization of completed deliverables

      Phase 1

      Link Security Metrics to Goals to Boost Maturity


      Phase 1

      1.1 Review current state and set your goals

      1.2 Develop KPIs and prioritize your goals

      1.3 Implement and monitor KPIs

      This phase will walk you through the following activities:

      • Current state assessment
      • Setting SMART goals
      • KPI development
      • Goals prioritization
      • KPI implementation

      This phase involves the following participants:

      • Security Team

      Outcomes of this phase

      • Goals-based KPIs
      • Security Metrics Determination and Tracking Tool

      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 two to three advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 1: Link Security Metrics to Goals to Boost Maturity

      Proposed Time to Completion: 2-4 weeks

      Step 1.1: Setting Goals

      Start with an analyst kick-off call:

      • Determine current and target maturity for various security programs.
      • Develop SMART Goals.

      Then complete these activities…

      • CMMI Assessment

      Step 1.2 – 1.3: KPI Development

      Review findings with analyst:

      • Prioritize goals
      • Develop KPIs to track progress on goals
      • Track associated metrics

      Then complete these activities…

      • KPI Development

      With these tools & templates:

      • KPI Development Worksheet
      • Security Metrics Determination and Tracking Tool

      Phase 1 Results & Insights:

      • Basic Metrics program

      1.1 Review current state and set your goals

      120 minutes

      Let’s put the security program under the microscope.

      Before program improvement can take place, it is necessary to look at where things are at presently (in terms of maturity) and where we need to get them to.

      In other words, we need to perform a security program gap analysis.

      Info-Tech Best Practice

      The most thorough way of performing this gap analysis is by completing Info-Tech’s Build an Information Security Strategy blueprint, as it will provide you with a prioritized list of initiatives to boost your security program maturity.

      Completing an abbreviated gap analysis...

      • Security Areas
      • Network Security
      • Endpoint Security
      • Vulnerability Management
      • Identity Access Management
      • Incident Management
      • Training & Awareness
      • Compliance, Audit, & Review
      • Risk Management
      • Business Alignment & Governance
      • Data Security
      1. Using the CMMI scale on the next slide, assess your maturity level across the security areas to the left, giving your program a score from 1-5. Record your assessment on a whiteboard.
      2. Zone in on your areas of greatest concern and choose 3 to 5 areas to prioritize for improvement.
      3. Set a SMART goal for improvement, using the criteria on goals slides.

      Use the CMMI scale to contextualize your current maturity

      Use the Capability Maturity Model Integration (CMMI) scale below to help you understand your current level of maturity across the various areas of your security program.

      1. Initial
        • Incident can be managed. Outcomes are unpredictable due to lack of a standard operating procedure.
      2. Repeatable
        • Process in place, but not formally implemented or consistently applied. Outcomes improve but still lack predictability.
      3. Defined
        • Process is formalized and consistently applied. Outcomes become more predictable, due to consistent handling procedure.
      4. Managed
        • Process shows signs of maturity and can be tracked via metrics. Moving towards a predictive approach to incident management.
      5. Optimizing
        • Process reaches a fully reliable level, though improvements still possible. Regularity allows for process to be automated.

      (Adapted from the “CMMI Institute Maturity Model”)

      Base your goals around the five types of metrics

      Choose goals that make sense – even if they seem simple.

      The most effective metrics programs are personalized to reflect the goals of the security team and the business they work for. Using goals-based metrics allows you to make incremental improvements that can be measured and reported on, which makes program maturation a natural process.

      Info-Tech Best Practice

      Before setting a SMART goal, take a moment to consider your maturity for each security area, and which metric type you need to collect first, before moving to more ambitious goals.

      Security Areas

      • Network Security
      • Endpoint Security
      • Vulnerability Management
      • Identity Access Management
      • Incident Management
      • Training & Awareness
      • Compliance, Audit & Review
      • Risk Management
      • Business Alignment & Governance
      • Data Security
      Metric Type Description
      Initial Probe Determines what can be known (i.e. what sources for metrics exist?).
      Baseline Testing Establishes organization’s normal state based on current metrics.
      Implementation Focuses on setting up a series of related processes to increase organizational security (i.e. roll out MFA).
      Improvement Sets a target to be met and then maintained based on organizational risk tolerance.
      Organizational Trends Culls together several metrics to track (sometimes predict) how various trends affect the organization’s overall security. Usually focuses on large-scale issues (e.g. likelihood of a data breach).

      Set SMART goals for your security program

      Specific

      Measurable

      Achievable

      Realistic

      Timebound

      Now that you have determined which security areas you’d like to improve, decide on a goal that meets the SMART criteria.

      Examples of possible goals for various maturity levels:

      1. Perform initial probe to determine number of systems capable of providing metrics by the end of the week.
      2. Take baseline measurements each month for three months to determine organization’s baseline state.
      3. Implement a vulnerability management program to improve baseline state by the end of the quarter.
      4. Improve deployment of critical patches by applying 90% of them within the set window by the end of the year.
      5. Demonstrate how vulnerability management affects broad organizational trends at quarterly report to senior leadership.

      Compare the bolded text in these examples with the metric types on the previous slide

      Record and assess your goals in the Security Metrics Determination and Tracking Tool

      1.1 Security Metrics Determination and Tracking Tool

      Use tab “2. Identify Security Goals” to document and assess your goals.

      To increase visibility into the cost, effort, and value of any given goal, assess them using the following criteria:

      • Initial Cost
      • Ongoing Cost
      • Initial Staffing
      • Ongoing Staffing
      • Alignment w/Business
      • Benefit

      Use the calculated Cost/Effort Rating, Benefit Rating, and Difference Score later in this project to help with goal prioritization.

      Info-Tech Best Practice

      If you have already completed a security strategy with Info-Tech resources, this work may likely have already been done. Consult your Information Security Program Gap Analysis Tool from the Build an Information Security Strategy research.

      1.2 Develop KPIs and prioritize your goals

      There are two paths to success.

      At this time, it is necessary to evaluate the priorities of your security program.

      Option 1: Progress to KPI Development

      • If you would like practice developing KPIs for multiple goals to get used to the process, move to KPI development and then assess which goals you can pursue now based on resources available, saving the rest for later.

      Option 2: Progress to Prioritization of Goals

      • If you are already comfortable with KPI development and do not wish to create extras for later use, then prioritize your goals first and then develop KPIs for them.

      Phase 1 Schematic

      • Gap Analysis
      • Set SMART Goals (You are here.)
        • Develop KPIs
      • Prioritize Goals
      • Implement KPI & Monitor
      • Phase 2

      Develop a key performance indicator (KPI)

      Find out if you’re meeting your goals.

      Terms like “key performance indicator” may make this development practice seem more complicated than it really is. A KPI is just a single metric used to measure success towards a goal. In relational terms (i.e. as a percentage, ratio, etc.) to give it context (e.g. % of improvement over last quarter).

      KPI development is about answering the question: what would indicate that I have achieved my goal?

      To develop a KPI follow these steps:

      1. Review the case study on the following slides to get a sense of how KPIs can start simple and general and get more specific and complex over time.
      2. Using the example to the right, sort your SMART goals from step 1.1 into the various metric types, then determine what success would look like for you. What outcome are you trying to achieve? How will you know when you’ve achieved it?
      3. Fill out the KPI Development Worksheets to create sample KPIs for each of the SMART goals you have created. Ensure that you complete the accompanying KPI Checklist.

      KPIs differ from goal to goal, but their forms follow certain trends

      Metric Type KPI Form
      Initial Probe Progress of probe (e.g. % of systems checked to see if they can supply metrics).
      Baseline Testing What current data shows (e.g. % of systems needing attention).
      Implementation Progress of the implementation (e.g. % of complete vulnerability management program implementation).
      Improvement The threshold or target to be achieved and maintained (e.g. % of incidents responded to within target window).
      Organizational Trends The interplay of several KPIs and how they affect the organization’s risk posture (e.g. assessing the likelihood for a data breach).

      Explore the five metric types

      1. Initial Probe

      Focused on determining how many sources for metrics exist.

      • Question: What am I capable of knowing?
      • Goal: To determine what level of insight we have into our security processes.
      • Possible KPI: % of systems for which metrics are available.
      • Decision: Do we have sufficient resources available to collect metrics?

      2. Baseline Testing

      Focused on gaining initial insights about the state of your security program (what are the measurements?).

      • Question: Does this data suggest areas for improvement?
      • Goal: To create a roadmap for improvement.
      • Possible KPI: % of systems that provide useful metrics to measure improvement.
      • Decision: Is it necessary to acquire tools to increase, enhance, or streamline the metrics-gathering process?

      Info-Tech Insight

      Don't lose hope if you lack resources to move beyond these initial steps. Even if you are struggling to pull data, you can still draw meaningful metrics. The percent or ratio of processes or systems you lack insight into can be very valuable, as it provides a basis to initiate a risk-based discussion with management about the organization's security blind spots.

      Explore the five metric types (cont’d)

      3. Program Implementation

      Focused on developing a basic program to establish basic maturity (e.g. implement an awareness and training program).

      • Question: What needs to be implemented to establish basic maturity?
      • Goal: To begin closing the gap between current and desired maturity.
      • Possible KPI: % of implementation completed.
      • Decision: Have we achieved a formalized and repeatable process?

      4. Improvement

      Focused on attaining operational targets to lower organizational risk.

      • Question: What other related activities could help to support this goal (e.g. regular training sessions)?
      • Goal: To have metrics operate above or below a certain threshold (e.g. lower phishing-test click rate to an average of 10% across the organization)
      • Possible KPI: Phishing click rate %
      • Decision: What other metrics should be tracked to provide insight into KPI fluctuations?

      Info-Tech Insight

      Don't overthink your KPI. In many cases it will simply be your goal rephrased to express a percentage or ratio. In others, like the example above, it makes sense for them to be identical.

      5. Organizational Impact

      Focused on studying several related KPIs (Key Performance Index, or KPX) in an attempt to predict risks.

      • Question: What risks does the organization need to address?
      • Goal: To provide high-level summaries of several metrics that suggest emerging or declining risks.
      • Possible KPI: Likelihood of a given risk (based on the trends of the KPX).
      • Decision: Accept the risk, transfer the risk, mitigate the risk?

      Case study: Healthcare example

      Let’s take a look at KPI development in action.

      Meet Maria, the new CISO at a large hospital that desperately needs security program improvements. Maria’s first move was to learn the true state of the organization’s security. She quickly learned that there was no metrics program in place and that her staff were unaware what, if any, sources were available to pull security metrics from.

      After completing her initial probe into available metrics and then investigating the baseline readings, she determined that her areas of greatest concern were around vulnerability and access management. But she also decided it was time to get a security training and awareness program up and running to help mitigate risks in other areas she can’t deal with right away.

      See examples of Maria’s KPI development on the next four slides...

      Info-Tech Insight

      There is very little variation in the kinds of goals people have around initial probes and baseline testing. Metrics in these areas are virtually always about determining what data sources are available to you and what that data actually shows. The real decisions start in determining what you want to do based on the measures you’re seeing.

      Metric development example: Vulnerability Management

      See examples of Maria’s KPI development on the next four slides...

      Implementation

      Goal: Implement vulnerability management program

      KPI: % increase of insight into existing vulnerabilities

      Associated Metric: # of vulnerability detection methods

      Improvement

      Goal: Improve deployment time for patches

      KPI: % of critical patches fully deployed within target window

      • Associated Metric 1: # of critical vulnerabilities not patched
      • Associated Metric 2: # of patches delayed due to lack of staff
      • Associated Metric X

      Metric development example: Identity Access Management

      Implementation

      Goal: Implement MFA for privileged accounts

      KPI: % of privileged accounts with MFA applied

      Associated Metric: # of privileged accounts

      Improvement

      Goal: Remove all unnecessary privileged accounts

      KPI: % of accounts with unnecessary privileges

      • Associated Metric 1: # of privileged accounts
      • Associated Metric 2: # of necessary privileged accounts
      • Associated Metric X

      Metric development example: Training and Awareness

      Implementation

      Goal: Implement training and awareness program

      KPI: % of organization trained

      Associated Metric: # of departments trained

      Improvement

      Goal: Improve time to report phishing

      KPI: % of phishing cases reported within target window

      • Associated Metric 1: # of phishing tests
      • Associated Metric 2: # of training sessions
      • Associated Metric X

      Metric development example: Key Performance Index

      Organizational Trends

      Goal: Predict Data Breach Likelihood

      • KPX 1: Insider Threat Potential
        • % of phishing cases reported within target window
          • Associated Metrics:
            • # of phishing tests
            • # of training sessions
        • % of critical patches fully deployed within target window
          • Associated Metrics:
            • # of critical vulnerabilities not patched
            • # of patches delayed due to lack of staff
        • % of accounts with unnecessary privileges
          • Associated Metrics:
            • # of privileged accounts
            • # of necessary privileged accounts
      • KPX 2: Data Leakage Issues
        • % of incidents related to unsecured databases
          • Associated Metrics:
            • # of unsecured databases
            • # of business-critical databases
        • % of misclassified data
          • Associated Metrics:
            • # of misclassified data reports
            • # of DLP false positives
        • % of incidents involving data-handling procedure violations.
          • Associated Metrics:
            • # of data processes with SOP
            • # of data processes without SOP
      • KPX 3: Endpoint Vulnerability Issues
        • % of unpatched critical systems
          • Associated Metrics:
            • # of unpatched systems
            • # of missed patches
        • % of incidents related to IoT
          • Associated Metrics:
            • # of IoT devices
            • # of IoT unsecure devices
        • % of incidents related to BYOD
          • Associated Metrics:
            • # of end users doing BYOD
            • # of BYOD incidents

      Develop Goals-Based KPIs

      1.2 120 minutes

      Materials

      • Info-Tech KPI Development Worksheets

      Participants

      • Security Team

      Output

      • List of KPIs for immediate and future use (can be used to populate Info-Tech’s KPI Development Tool).

      It’s your turn.

      Follow the example of the CISO in the previous slides and try developing KPIs for the SMART goals set in step 1.1.

      • To begin, decide if you are starting with implementation or improvement metrics.
      • Enter your goal in the space provided on the left-hand side and work towards the right, assigning a KPI to track progress towards your goal.
      • Use the associated metrics boxes to record what raw data will inform or influence your KPI.
        • Associated metrics are connected to the KPI box with a segmented line. This is because these associated metrics are not absolutely necessary to track progress towards your goal.
        • However, if a KPI starts trending in the wrong direction, these associated metrics would be used to determine where the problem has occurred.
      • If desired, bundle together several related KPIs to create a key performance index (KPX), which is used to forecast the likelihood of certain risks that would have a major business impact (e.g. potential for insider threat, or risk for a data breach).

      Record KPIs and assign them to goals in the Security Metrics Determination and Tracking Tool

      1.2 Security Metrics Determination and Tracking Tool

      Document KPI metadata in the tool and optionally assign them to a goal.

      Tab “3. Identify Goal KPIs” allows you to record each KPI and its accompanying metadata:

      • Source
      • Owner
      • Audience
      • KPI Target
      • Effort to Collect
      • Frequency of Collection
      • Comments

      Optionally, each KPI can be mapped to goals defined on tab “2. Identify Security Goals.”

      Info-Tech Best Practice

      Ensure your metadata is comprehensive, complete, and realistic. A different employee should be able to use only the information outlined in the metadata to continue collecting measurements for the program.

      Complete Info-Tech’s KPI Development Worksheets

      1.2 KPI Development Worksheet

      Use these worksheets to model the maturation of your metrics program.

      Follow the examples contained in this slide deck and practice creating KPIs for:

      • Implementation metrics
      • Improvement metrics
      • Organizational trends metrics

      As well as drafting associated metrics to inform the KPIs you create.

      Info-Tech Best Practice

      Keep your metrics program manageable. This exercise may produce more goals, metrics, and KPIs than you deal with all at once. But that doesn’t mean you can’t save some for future use.

      Build an effort map to prioritize your SMART goals

      1.2 120 minutes

      Materials

      • Whiteboard
      • Sticky notes
      • Laptop

      Participants

      • Security team
      • Other stakeholders

      Output

      • Prioritized list of SMART goals

      An effort map visualizes a cost and benefit analysis. It is a quadrant output that visually shows how your SMART goals were assessed. Use the calculated Cost/Effort Rating and Benefit Rating values from tab “2. Identify Security Goals” of the Security Metrics Determination and Tracking Tool to aid this exercise.

      Steps:

      1. Establish the axes and colors for your effort map:
        1. X-axis (horizontal) - Security benefit
        2. Y-axis (vertical) - Overall cost/effort
        3. Sticky color - Business alignment
      2. Create sticky notes for each SMART goal and place them onto the effort map based on your determined axes.
        • Goal # Example Security Goal - Benefit (1-12) - Cost (1-12)

      The image shows a matric with four quadrants. The X-axis is labelled Low Benefit on the left side and High benefit on the right side. The Y-axis is labelled Low cost at the top and High cost at the bottom. The top left quadrant is labelled Could Dos, the top right quadrant is labelled Must Dos, the lower left quadrant is labelled May Not Dos, and the lower right quadrant is Should Dos. On the right, there are three post-it style notes, the blue one labelled High Alignment, the yellow labelled Medium Alignment, and the pink labelled Low Alignment.

      1.3 Implement and monitor the KPI to track goal progress

      Let’s put your KPI into action!

      Now that you’ve developed KPIs to monitor progress on your goals, it’s time to use them to drive security program maturation by following these steps:

      1. Review the KPI Development Worksheets (completed in step 1.2) for your prioritized list of goals. Be sure that you are able to track all of the associated metrics you have identified.
      2. Track the KPI and associated metrics using Info-Tech’s KPI Development Tool (see following slide).
      3. Update the data as necessary according to your SMART criteria of your goal.

      A Word on Key Risk Indicators...

      The term key risk indicator (KRI) gets used in a few different ways. However, in most cases, KRIs are closely associated with KPIs.

      1. KPIs and KRIs are the same thing
        • A KPI, at its core, is really a measure of risk. Sometimes it is more effective to emphasize that risk rather than performance (i.e. the data shows you’re not meeting your goal).
      2. KRI is KPI going the wrong way
        • After achieving the desired threshold for an improvement goal, our new goal is usually to maintain such a state. When this balance is upset, it indicates that settled risk has once again become active.
      3. KRI as a predictor of emerging risks
        • When organizations reach a highly mature state, they often start assessing how events external to the organization can affect the optimal performance of the organization. They monitor such events or trends and try to predict when the organization is likely to face additional risks.

      Track KPIs in the Security Metrics Determination and Tracking Tool

      1.3 Security Metrics Determination and Tracking Tool

      Once a metric has been measured, you have the option of entering that data into tab “4. Track Metrics” of the Tool.

      Tracking metric data in Info-Tech's tool provides the following data visualizations:

      • Sparklines at the end of each row (on tab “4. Track Metrics”) for a quick sense of metric performance.
      • A metrics dashboard (on tab “5. Graphs”) with three graph options in two color variations for each metric tracked in the tool, and an overall metric program health gauge.

      Info-Tech Best Practice

      Be diligent about measuring and tracking your metrics. Record any potential measurement biases or comments on measurement values to ensure you have a comprehensive record for future use. In the tool, this can be done by adding a comment to a cell with a metric 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:

      Workshops offer an easy way to accelerate your project. While onsite, our analysts will work with you and your team to facilitate the activities outlined in the blueprint.

      Getting key stakeholders together to formalize the program, while getting started on data discovery and classification, allows you to kickstart the overall program.

      In addition, leverage over-the-phone support through Guided Implementations included in advisory memberships to ensure the continuous improvement of the classification program even after the workshop.

      Logan Rohde

      Research Analyst – Security, Risk & Compliance Info-Tech Research Group

      Ian Mulholland

      Senior Research Analyst – Security, Risk & Compliance Info-Tech Research Group

      Call 1-888-670-8889 for more information.

      Phase 2

      Adapt Your Reporting Strategy for Various Metric Types


      Phase 2

      2.1 Review best practices for presenting metrics

      2.2 Strategize your presentation based on metric type

      2.3 Tailor your presentation to your audience

      2.4 Use your metrics to create a story about risk

      2.5 Revise Metrics

      This phase will walk you through the following activities:

      • Develop reporting strategy
      • Use metrics to create a story about risk
      • Metrics revision

      This phase involves the following participants:

      • Security Team

      Outcomes of this phase

      • Metrics Dashboard
      • Metrics Presentation Deck

      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 two to three advisory calls that help you execute each phase of a project. They are included in most advisory memberships.

      Guided Implementation 2: Adapt Your Reporting Strategy for Various Metric Types

      Proposed Time to Completion: 2-4 weeks

      Step 2.1 – 2.3: Best Practices and Reporting Strategy

      Start with an analyst kick-off call:

      • Do’s and Don’ts of reporting metrics.
      • Strategize presentation based on metric type.

      Then complete these activities…

      • Strategy development for 3-5 metrics

      Step 2.4 – 2.5: Build a Dashboard and Presentation Deck

      Review findings with analyst:

      • Review strategies for reporting.
      • Compile a Key Performance Index.
      • Revise metrics.

      Then complete these activities…

      • Dashboard creation
      • Presentation development

      With these tools & templates:

      • Security Metrics Determination and Tracking Tool Template
      • Security Metrics KPX Dashboard Tool

      Phase 2 Results & Insights:

      • Completed reporting strategy with presentable dashboard

      2.1 Review best practices for presenting metrics

      Avoid technical details (i.e. raw data) by focusing on the KPI.

      • KPIs add context to understand the behavior and associated risks.

      Put things in terms of risk; it's the language you both understand.

      • This usually means explaining what will happen if not addressed and what you recommend.
      • There are always three options:
        • Address it completely
        • Address it partially
        • Do not address it (i.e. accept the risk)

      Explain why you’re monitoring metrics in terms of the goals you’re hoping to achieve.

      • This sets you up well to explain what you've been doing and why it's important for you to meet your goals.

      Choose between KPI or KRI as the presentation format.

      • Base your decision on whether you are trying to emphasize current success or risk.

      Match presentation with the audience.

      • Board presentations will be short; middle-management ones may be a bit longer.
      • Maximize your results by focusing on the minimum possible information to make sure you sufficiently get your point across.
      • With the board, plan on showing no more than three slides.

      Read between the lines.

      • It can be difficult to get time with the board, so you may find yourself in a trial and error position, so pay attention to cues or suggestions that indicate the board is interested in something.
      • If you can, make an ally to get the inside scoop on what the board cares about.

      Read the news if you’re stuck for content.

      • Board members are likely to have awareness (and interest) in large-scale risks like data breaches and ransomware.

      Present your metrics as a story.

      • Summarize how the security program looks to you and why the metrics lead you to see it this way.

      2.2 Strategize your presentation based on metric type (1 of 5)

      Metric Type: Initial Probe

      Scenario: Implementing your first metrics program.

      • All metrics programs start with determining what measurements you are capable of taking.

      Decisions: Do you have sufficient insight into the program? (i.e. do you need to acquire additional tools to collect metrics?)

      Strategy: If there are no barriers to this (e.g. budget), then focus your presentation on the fact that you are addressing the risk of not knowing what your organization's baseline state is and what potential issues exist but are unknown. This is likely the first phase of an improvement plan, so sketching the overall plan is a good idea too.

      • If budget is an issue, explain the risks associated with not knowing and what you would need to make it happen.

      Possible KPIs:

      • % of project complete.
      • % of systems that provide worthwhile metrics.

      Strategize your presentation based on metric type (2 of 5)

      Metric Type: Baseline Testing

      Scenario: You've taken the metrics to determine what your organization’s normal state is and you're now looking towards addressing your gaps or problem areas.

      Decisions: What needs to be prioritized first and why? Are additional resources required to make this happen?

      Strategy: Explain your impression of the organization's normal state and what you plan to do about it. In other words, what goals are you prioritizing and why? Be sure to note any challenges that may occur along the way (e.g. staffing).

      • If the board doesn't like to open their pocketbook, your best play is to explain what stands to happen (or is happening) if risks are not addressed.

      Possible KPIs:

      • % of goals complete.
      • % of metrics indicating urgent attention needed.

      Strategize your presentation based on metric type (3 of 5)

      Metric Type: Implementation

      Scenario: You are now implementing solutions to address your security priorities.

      Decisions: What, to you, would establish the basis of a program?

      Strategy: Focus on what you're doing to implement a certain security need, why, and what still needs to be done when you’re finished.

      • Example: To establish a training and awareness program, a good first step is to actually hold training sessions with each department. A single lecture is simple but something to build from. A good next step would be to hold regular training sessions or implement monthly phishing tests.

      Possible KPIs:

      • % of implementation complete (e.g. % of departments trained).

      Strategize your presentation based on metric type (4 of 5)

      Metric Type: Improvement

      Scenario: Now that a basic program has been established, you are looking to develop its maturity to boost overall performance (i.e. setting a new development goal).

      Decisions: What is a reasonable target, given the organization's risk tolerance and current state?

      Strategy: Explain that you're now working to tighten up the security program. Note that although things are improving, risk will always remain, so we need to keep it within a threshold that’s proportionate with our risk tolerance.

      • Example: Lower phishing-test click rate to 10% or less. Phishing will always be a risk, and just one slip up can have a huge effect on business (i.e. lost money).

      Possible KPIs:

      • % of staff passing the phishing test.
      • % of employees reporting phishing attempts within time window.

      Strategize your presentation based on metric type (5 of 5)

      Metric Type: Organizational Trends

      Scenario: You've reached a mature state and now how several KPIs being tracked. You begin to look at several KPIs together (i.e. a KPX) to assess the organization's exposure for certain broad risk trends.

      Decisions: Which KPIs can be used together to look at broader risks?

      Strategy: Focus on the overall likelihood of a certain risk and why you've chosen to assess it with your chosen KPIs. Spend some time discussing what factors affect the movement of these KPIs, demonstrating how smaller behaviors create a ripple effect that affects the organization’s exposure to large-scale risks.

      Possible KPX: Insider Threat Risk

      • % of phishing test failures.
      • % of critical patches missed.
      • % of accounts with unnecessary privileges.

      Change your strategy to address security challenges

      Even challenges can elicit useful metrics.

      Not every security program is capable of progressing smoothly through the various metric types. In some cases, it is impossible to move towards goals and metrics for implementation, improvement, or organizational trends because the security program lacks resources.

      Info-Tech Insight

      When your business is suffering from a lack of resources, acquiring these resources automatically becomes the goal that your metrics should be addressing. To do this, focus on what risks are being created because something is missing.

      When your security program is lacking a critical resource, such as staff or technology, your metrics should focus on what security processes are suffering due to this lack. In other words, what critical activities are not getting done?

      KPI Examples:

      • % of critical patches not deployed due to lack of staff.
      • % of budget shortfall to acquire vulnerability scanner.
      • % of systems with unknown risk due to lack of vulnerability scanner.

      2.3 Tailor presentation to your audience

      Metrics come in three forms...

      1. Raw Data

      • Taken from logs or reports, provides values but not context.
      • Useful for those with technical understanding of the organization’s security program.

      2. Management-Level

      • Raw data that has been contextualized and indicates performance of something (i.e. a KPI).
      • Useful for those with familiarity with the overall state of the security program but do not have a hands-on role.

      3. Board-Level

      • KPI with additional context indicating overall effect on the organization.
      • Useful for those removed from the security program but who need to understand the relationship between security, business goals, and cyber risk.

      For a metric to be useful it must...

      1. Be understood by the audience it’s being presented to.
        • Using the criteria on the left, choose which metric form is most appropriate.
      2. Indicate whether or not a certain target or goal is being met.
        • Don’t expect metrics to speak for themselves; explain what the indications and implications are.
      3. Drive some kind of behavioral or strategic change if that target or goal is not being met.
        • Metrics should either affirm that things are where you want them to be or compel you to take action to make an improvement. If not, it is not a worthwhile metric.

      As a general rule, security metrics should become decreasingly technical and increasingly behavior-based as they are presented up the organizational hierarchy.

      "The higher you travel up the corporate chain, the more challenging it becomes to create meaningful security metrics. Security metrics are intimately tied to their underlying technologies, but the last thing the CEO cares about is technical details." – Ben Rothke, Senior Information Security Specialist, Tapad.

      Plan for reporting success

      The future of your security program may depend on this presentation; make it count.

      Reporting metrics is not just another presentation. Rather, it is an opportunity to demonstrate and explain the value of security.

      It is also a chance to correct any misconceptions about what security does or how it works.

      Use the tips on the right to help make your presentation as relatable as possible.

      Info-Tech Insight

      There is a difference between data manipulation and strategic presentation: the goal is not to bend the truth, but to present it in a way that allows you to show the board what they need to see and to explain it in terms familiar to them.

      General Tips for a Successful Presentation

      Avoid jargon; speak in practical terms

      • The board won’t receive your message if they can’t understand you.
      • Explain things as simply as you can; they only need to know enough to make decisions about addressing cyber risk.

      Address compliance

      • Boards are often interested in compliance, so be prepared to talk about it, but clarify that it doesn't equal security.
      • Instead, use compliance as a bridge to discussing areas of the security program that need attention.

      Have solid answers

      • Try to avoid answering questions with the answer, “It depends.”
        • Depends on what?
        • Why?
        • What do you recommend?
      • The board is relying on you for guidance, so be prepared to clarify what the board is asking (you may have to read between the lines to do this).
      • Also address the pain points of board members and have answers to their questions about how to resolve them.

      2.4 Use your metrics to create a story about risk

      Become the narrator of your organization’s security program.

      Security is about managing risk. This is also its primary value to the organization. As such, risk should be the theme of the story you tell.

      "Build a cohesive story that people can understand . . . Raw metrics are valuable from an operations standpoint, but at the executive level, it's about a cohesive story that helps executives understand the value of the security program and keeps the company moving forward. "– Adam Ely, CSO and Co-Founder, Bluebox Security, qtd. by Tenable, 2016

      How to Develop Your Own Story...

      1. Review your security program goals and the metrics you’re using to track progress towards them. Then, decide which metrics best tell this story (i.e. what you’re doing and why).
        • Less is more when presenting metrics, so be realistic about how much your audience can digest in one sitting.
        • Three metrics is usually a safe number; choose the ones that are most representative of your goals.
      2. Explain why you chose the goals you did (i.e. what risks were you addressing?). Then, make an honest assessment of how the security program is doing as far as meeting those goals:
        • What’s going well?
        • What still needs improvement?
        • What about your metrics suggests this?
      3. Address how risks have changed and explain your new recommended course of action.
        • What risks were present when you started?
        • What risks remain despite your progress?
        • How do these risks affect the business operation and what can security do to help?

      Story arc for security metrics

      The following model encapsulates the basic trajectory of all story development.

      Use this model to help you put together your story about risk.

      Introduction: Overall assessment of security program.

      Initial Incident: Determination of the problems and associated risks.

      Rising Action: Creation of goals and metrics to measure progress.

      Climax: Major development indicated by metrics.

      Falling Action: New insights gained about organization’s risks.

      Resolution: Recommendations based on observations.

      Info-Tech Best Practice

      Follow this model to ensure that your metrics presentation follows a coherent storyline that explains how you assessed the problem, why you chose to address it the way you did, what you learned in doing so, and finally what should be done next to boost the security program’s maturity.

      Use a nesting-doll approach when presenting metrics

      Move from high-level to low-level to support your claims

      1. Avoid the temptation to emphasize technical details when presenting metrics. The importance of a metric should be clear from just its name.
      2. This does not mean that technical details should be disregarded entirely. Your digestible, high-level metrics should be a snapshot of what’s taking place on the security ground floor.
      3. With this in mind, we should think of our metrics like a nesting doll, with each metrics level being supported by the one beneath it.

      ...How do you know that?

      Board-Level KPI

      Mgmt.-Level KPI

      Raw Data

      Think of your lower-level metrics as evidence to back up the story you are telling.

      When you’re asked how you arrived at a given conclusion, you know it’s time to go down a level and to explain those results.

      Think of this like showing your work.

      Info-Tech Insight

      This approach is built into the KPX reporting format, but can be used for all metric types by drawing from your associated metrics and goals already achieved.

      Use one of Info-Tech’s dashboards to present your metrics

      2.4 Security Metrics Determination and Tracking Tool

      Choose the dashboard tool that makes the most sense for you.

      Info-Tech provides two options for metric dashboards to meet the varying needs of our members.

      If you’re just starting out, you’ll likely be inclined towards the dashboard within the Security Metrics Determination and Tracking Tool (seen here).

      The image shows a screenshot of the Security Metrics Determination and Tracking Tool.

      But if you’ve already got several KPIs to report on, you may prefer the Security Metrics KPX Dashboard Tool, featured on the following slides.

      Info-Tech Best Practice

      Not all graphs will be needed in all cases. When presenting, consider taking screenshots of the most relevant data and displaying them in Info-Tech’s Board-Level Security Metrics Presentation Template.

      Use one of Info-Tech’s dashboards to present your metrics

      2.4 Security Metrics KPX Dashboard

      Use Info-Tech’s Security Metrics KPX Dashboard to track and show your work.

      The image shows a screenshot of the Definitions section of the Security Metrics KPX Dashboard

      1. Start by customizing the definitions on tab 1 to match your organization’s understanding of high, medium, and low risk across the three impact areas (functional, informational, and recoverability).
      2. Next, enter up to 5 business goals that your security program supports.

      Use one of Info-Tech’s dashboards to present your metrics

      2.4 Security Metrics KPX Dashboard

      Use Info-Tech’s Security Metrics KPX Dashboard to track and show your work.

      The image shows a screenshot of tab 2 of the Security Metrics KPX Dashboard.

      1. On tab 2, enter the large-scale risk you are tracking
      2. Proceed by naming each of your KPXs after three broad risks that – to you – contribute to the large-scale risk.

      Use one of Info-Tech’s dashboards to present your metrics

      2.4 Security Metrics KPX Dashboard

      Use Info-Tech’s Security Metrics KPX Dashboard to track and show your work.

      The image is the same screenshot from the previous section, of tab 2 of the Security Metrics KPX Dashboard.

      1. Then, add up to five KPIs aimed at managing more granular risks that contribute to the broad risk.
      2. Assess the frequency and impact associated with these more granular risks to determine how likely it is to contribute to the broad risk the KPX is tracking.

      Use one of Info-Tech’s dashboards to present your metrics

      2.4 Security Metrics KPX Dashboard

      Use Info-Tech’s Security Metrics KPX Dashboard to track and show your work.

      The image is the same screenshot of tab 2 of the Security Metrics KPX Dashboard.

      1. Repeat as necessary for the other KPXs on tab 2.
      2. Repeat steps 3-7 for up to two more large-scale risks and associated KPXs on tabs 3 and 4.

      Use one of Info-Tech’s dashboards to present your metrics

      2.4 Security Metrics KPX Dashboard

      Use Info-Tech’s Security Metrics KPX Dashboard to track and show your work.

      The image shows a chart titled Business Alignment, with sample Business Goals and KPXs filled in.

      1. If desired, complete the Business Alignment evaluation (located to the right of KPX 2 on tabs 2-4) to demonstrate how well security is supporting business goals.

      "An important key to remember is to be consistent and stick to one framework once you've chosen it. As you meet with the same audiences repeatedly, having the same framework for reference will ensure that your communications become smoother over time." – Caroline Wong, Chief Strategy Officer, Cobalt.io

      Use one of Info-Tech’s dashboards to present your metrics

      2.4 Security Metrics KPX Dashboard

      Use Info-Tech’s Security Metrics KPX Dashboard to track and show your work.

      The image shows a screenshot of the dashboard on tab 5 of the Security Metrics KPX Dashboard.

      1. Use the dashboard on tab 5 to help you present your security metrics to senior leadership.

      Use one of Info-Tech’s dashboards to present your metrics

      2.4 Security Metrics KPX Dashboard

      Use Info-Tech’s Security Metrics KPX Dashboard to track and show your work.

      The image shows the same screenshot of Tab 2 of the Security Metrics KPX Dashboard that was shown in previous sections.

      Best Practice:

      This tool helps you convert your KPIs into the language of risk by assessing frequency and severity, which helps to make the risk relatable for senior leadership. However, it is still useful to track fluctuations in terms of percentage. To do this, track changes in the frequency, severity, and trend scores from quarter to quarter.

      Customize Info-Tech’s Security Metrics Presentation Template

      2.4 Board-Level Security Metrics Presentation Template

      Use the Board-Level Security Metrics Presentation Template deck to help structure and deliver your metrics presentation to the board.

      To make the dashboard slide, simply copy and paste the charts from the dashboard tool and arrange the images as needed.

      Adapt the status report and business alignment slides to reflect the story about risk that you are telling.

      2.5 Revise your metrics

      What's next?

      Now that you’ve made it through your metrics presentation, it’s important to reassess your goals with feedback from your audience in mind. Use the following workflow.

      The image shows a flowchart titled Metrics-Revision Workflow. The flowchart begins with the question Have you completed your goal? and then works through multiple potential answers.

      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:

      Workshops offer an easy way to accelerate your project. While onsite, our analysts will work with you and your team to facilitate the activities outlined in the blueprint.

      Getting key stakeholders together to formalize the program, while getting started on data discovery and classification, allows you to kickstart the overall program.

      In addition, leverage over-the-phone support through Guided Implementations included in advisory memberships to ensure the continuous improvement of the classification program even after the workshop.

      Logan Rohde

      Research Analyst – Security, Risk & Compliance Info-Tech Research Group

      Ian Mulholland

      Senior Research Analyst – Security, Risk & Compliance Info-Tech Research Group

      Call 1-888-670-8889 for more information.

      Insight breakdown

      Metrics lead to maturity, not vice versa.

      • Tracking metrics helps you assess progress and regress in your security program, which helps you quantify the maturity gains you’ve made.

      Don't lose hope if you lack resources to move beyond baseline testing.

      • Even if you are struggling to pull data, you can still draw meaningful metrics. The percent or ratio of processes or systems you lack insight into can be very valuable, as it provides a basis to initiate a risk-based discussion with management about the organization's security blind spots.

      The best metrics are tied to goals.

      • Tying your metrics to goals ensures that you are collecting metrics for a specific purpose rather than just to watch the numbers change.

      Summary of accomplishment

      Knowledge Gained

      • Current maturity assessment of security areas
      • Setting SMART goals
      • Metric types
      • KPI development
      • Goals prioritization
      • Reporting and revision strategies

      Processes Optimized

      • Metrics development
      • Metrics collection
      • Metrics reporting

      Deliverables Completed

      • KPI Development Worksheet
      • Security Metrics Determination and Tracking Tool
      • Security Metrics KPX Dashboard Tool
      • Board-Level Security Metrics Presentation Template

      Research contributors and experts

      Mike Creaney, Senior Security Engineer at Federal Home Loan Bank of Chicago

      Peter Chestna, Director, Enterprise Head of Application Security at BMO Financial Group

      Zane Lackey, Co-Founder / Chief Security Officer at Signal Sciences

      Ben Rothke, Senior Information Security Specialist at Tapad

      Caroline Wong, Chief Strategy Officer at Cobalt.io

      2 anonymous contributors

      Related Info-Tech research

      Build an Information Security Strategy

      Tailor best practices to effectively manage information security.

      Implement a Security Governance and Management Program

      Align security and business objectives to get the greatest benefit from both.

      Bibliography

      Capability Maturity Model Integration (CMMI). ISACA. Carnegie Mellon University.

      Ely, Adam. “Choose Security Metrics That Tell a Story.” Using Security Metrics to Drive Action: 33 Experts Share How to Communicate Security Program Effectiveness to Business Executives and the Board Eds. 2016. Web.

      https://www.ciosummits.com/Online_Assets_Tenable_eBook-_Using_Security_Metrics_to_Drive_Action.pdf

      ISACA. “Board Director Concerns about Cyber and Technology Risk.” CSX. 11 Sep. 2018. Web.

      Rothke, Ben. “CEOs Require Security Metrics with a High-Level Focus.” Using Security Metrics to Drive Action: 33 Experts Share How to Communicate Security Program Effectiveness to Business Executives and the Board Eds. 2016. Web.

      https://www.ciosummits.com/Online_Assets_Tenable_eBook-_Using_Security_Metrics_to_Drive_Action.pdf

      Wong, Caroline. Security Metrics: A Beginner’s Guide. McGraw Hill: New York, 2012.

      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

      Develop the Right Message to Engage Buyers

      • 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

      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. Without an easy content development strategy, marketers have an insurmountable task of continually creating interesting content for an audience they don’t understand.

      Globally, B2B SaaS marketers without the ability to consistently produce and activate quality content will experience:

      • High website bounce rates and low time on site
      • Low page views
      • A low percentage of return visitors
      • Low conversions
      • Low open and click-through rates on email campaigns

      Our Advice

      Critical Insight

      Marketing content that identifies the benefit of the product along with a deep understanding of the buyer pain points, desired value, and benefit proof points is a key driver in delivering value to a prospect, thereby increasing marketing metrics such as open rates, time on site, page views, and click-through rates.

      Impact and Result

      Marketers that activate the SoftwareReviews message mapping architecture will be able to crack the code on the formula for improving open and click-through rates.

      By applying the SoftwareReviews message mapping architecture, clients will be able to:

      • Quickly diagnose the current state of their content marketing effectiveness compared to industry metrics.
      • Compare their current messaging approach versus the key elements of the Message Map Architecture.
      • 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.

      Develop the Right Message to Engage Buyers Research & Tools

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

      1. Develop the Right Message to Engage Buyers Executive Brief – A mapping architecture to enable marketers to crack the code on the formula for improving open and click-through rates.

      Through this blueprint marketers will learn how to shift content away from low-performing content that only focuses on the product and company to high-performing customer-focused content that answers the “What’s in it for me?” question for a buyer, increasing engagement and conversions.

      Infographic

      Further reading

      Develop the Right Message to Engage Buyers

      Drive higher open rates, time-on-site, and click-through rates with buyer-relevant messaging.

      Analyst Perspective

      Develop the right message to engage buyers.

      Marketers only have seven seconds to capture a visitor's attention but often don't realize that the space between competitors and their company is that narrow. They often miss the mark on content and create reams of product and company-focused messaging that result in high bounce rates, low page views, low return visits, low conversions, and low click-through rates.

      We wouldn't want to sit in a conversation with someone who only speaks about themselves, so why would it be any different when we buy something? Today's marketers must quickly hook their visitors with content that answers the critical question of "What's in it for me?"

      Our research finds that leading content marketers craft messaging that lets their audience ”know they know them,” points out what’s in it for them, and includes proof points of promised value. This simple, yet often missed approach, we call Message Mapping, which helps marketers grab a visitor’s initial attention and when applied throughout the customer journey will turn prospects into customers, lifelong buyers, advocates, and referrals.

      Photo of Terra Higginson, Marketing Research Director, SoftwareReviews.

      Terra Higginson
      Marketing Research Director
      SoftwareReviews

      Executive Summary

      Your Challenge

      Globally, B2B SaaS marketers without the ability to consistently produce and activate quality content will experience:

      • High website bounce rates and low time on site
      • Low page views
      • A low percentage of return visitors
      • Low conversions
      • Low open and click-through rates on email campaigns
      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. Without an easy content development strategy, marketers have an insurmountable task of continually creating interesting content for an audience they don’t understand.
      Common Obstacles

      Marketers struggle to create content that quickly engages the buyer because they lack:

      • Resources to create a high volume of quality content.
      • True buyer understanding.
      • Experience in how to align technical messaging with the buyer persona.
      • Easy-to-deploy content strategy tools.
      Even though most marketers will say that it’s important to produce interesting content, only 58% of B2B markers take the time to ask their customers what’s important to them. Without a true and deep understanding of buyers, marketers continue to invest their time and resources in an uninteresting product and company-focused diatribe.
      SoftwareReviews’ Approach

      By applying the SoftwareReviews’ message mapping architecture, clients will be able to:

      • Quickly diagnose the current state of their content marketing effectiveness compared to industry metrics.
      • Compare their current messaging approach against the key elements of the Message Map Architecture.
      • 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.
      Marketers that activate the SoftwareReviews message mapping architecture will be able to crack the code on the formula for improving open and click-through rates.

      SoftwareReviews Insight

      Marketing content that identifies the benefit of the product, along with a deep understanding of the buyer pain points, desired value, and benefit proof-points, is a key driver in delivering value to a prospect, thereby increasing marketing metrics such as open rates, time on site, page views, and click-through rates.

      Your Challenge

      65% of marketers find it challenging to produce engaging content.

      Globally, B2B SaaS marketers without the ability to consistently produce and activate quality content will experience:

      • High website bounce rates and low time on site
      • Low page views
      • A low percentage of return visitors
      • Low conversions
      • Low open and click-through rates on email campaigns

      A staggering 60% of marketers find it hard to produce high-quality content consistently and 62% don’t know how to measure the ROI of their campaigns according to OptinMonster.

      SaaS marketers have an even more difficult job due to the technical nature of content production. Without an easy content development strategy, marketers have an insurmountable task of continually creating interesting content for an audience they don’t understand.


      Over 64% of marketers want to learn how to build a better content
      (Source: OptinMonster, 2021)

      Benchmark your content marketing

      Do your content marketing metrics meet the industry-standard benchmarks for the software industry?
      Visualization of industry benchmarks for 'Bounce Rate', 'Organic CTR', 'Pages/Session', 'Average Session Duration', '% of New Sessions', 'Email Open Rate', 'Email CTR', and 'Sales Cycle Length (Days)' with sources linked below.
      GrowRevenue, MarketingSherpa, Google Analytics, FirstPageSage, Google Analytics, HubSpot
      • Leaders will measure content marketing performance against these industry benchmarks.
      • If your content performance falls below these benchmarks, your content architecture may be missing the mark with prospective buyers.

      Common flaws in content messaging

      Why do marketers have a hard time consistently producing messaging that engages the buyer?

      Mistake #1

      Myopic Focus on Company and Product

      Content suffers a low ROI due to a myopic focus on the company and the product. This self-focused content fails to engage prospects and move them through the funnel.

      Mistake #2

      WIIFM Question Unanswered

      Content never answers the fundamental “What’s in it for me?” question due to a lack of true buyer understanding. This leads to an inability to communicate the value proposition to the prospect.

      Mistake #3

      Inability to Select the Right Content Format

      Marketers often guess what kind of content their buyers prefer without any real understanding or research behind what buyers would actually want to consume.

      Leaders Will Avoid the “Big Three” Pitfalls
      • While outdated content, poor content organization on your website, and poor SEO are additional strategic factors (outside the scope of this research), poor messaging structure will doom your content marketing strategy.
      • Leaders will be vigilant to diagnose current messaging structure and avoid:
        1. Making messaging all about you and your company.
        2. Failing to describe what’s in it for your prospects.
        3. Often guessing at what approach to use when structuring your messaging.

      Implications of poor content

      Without quality content, the sales and marketing cycles elongate and content marketing metrics suffer.
      • Lost sales: Research shows that B2B buyers are 57-70% done with their buying research before they ever contact sales.(Worldwide Business Research, 2022)
      • The buyer journey is increasingly digital: Research shows that 67% of the buyer's journey is now done digitally.(Worldwide Business Research, 2022)
      • Wasted time: In a Moz study of 750,000 pieces of content, 50% had zero backlinks, indicating that no one felt these assets were interesting enough to reference or share. (Moz, 2015)
      • Wasted money: SaaS companies spend $342,000 to $1,080,000 per year (or more) on content marketing. (Zenpost, 2022) The wrong content will deliver a poor ROI.

      50% — Half of the content produced has no backlinks. (Source: Moz, 2015)

      Content matters more than ever since 67% of the buyer's journey is now done digitally. (Source: Worldwide Business Research, 2022)

      Benefits of good content

      A content mapping approach lets content marketers:
      • Create highly personalized content. Content mapping helps marketers to create highly targeted content at every stage of the buyer’s journey, helping to nurture leads and prospects toward a purchase decision.
      • Describe “What’s in it for me?” to buyers. Remember that you aren’t your customer. Good content quickly answers the question “What’s in it for me?” (WIIFM) developed from the findings of the buyer persona. WIIFM-focused content engages a prospect within seven seconds.
      • Increase marketing ROI. Content marketing generates leads three times greater than traditional marketing (Patel, 2016).
      • Influence prospects. Investing in a new SaaS product isn’t something buyers do every day. In a new situation, people will often look to others to understand what they should do. Good content uses the principles of authority and social proof to build the core message of WIIFM. Authority can be conferred with awards and accolades, whereas social proof is given through testimonials, case studies, and data.
      • Build competitive advantage. Increase competitive advantage by providing content that aligns with the ideal client profile. Fifty-two percent of buyers said they were more likely to buy from a vendor after reading its content (1827 Marketing, 2022).
      Avoid value claiming. Leaders will use client testimonials as proof points because buyers believe peers more than they believe you.

      “… Since 95 percent of the people are imitators and only 5 percent initiators, people are persuaded more by the actions of others than by any proof we can offer. (Robert Cialdini, Influence: The Psychology of Persuasion)

      Full slide: 'Message Map Architecture'.

      Full slide: 'Message Map Template' with field descriptions and notes.

      Full slide: 'Message Map Template' with field descriptions, no notes.

      Full slide: 'Message Map Template' with blank fields.

      Full slide: 'Message Map Template' with 'Website Example segment.com' filled in fields.

      Full slide: 'Website Example segment.com' the website as it appears online with labels on the locations of elements of the message map.

      Full slide: 'Website Example segment.com' the website as it appears online with labels on the locations of elements of the message map.

      Full slide: 'Website Example segment.com' the website as it appears online with labels on the locations of elements of the message map.

      Full slide: 'Website Example segment.com' the website as it appears online with labels on the locations of elements of the message map.

      Email & Social Post Example

      Use the message mapping architecture to create other types of content.

      Examples of emails and social media posts as they appear online with labels on the locations of elements of the message map.

      Insight Summary

      Create Content That Matters

      Marketing content that identifies the benefit of the product along with a deep understanding of the buyer pain points, desired value, and benefit proof-points is a key driver in delivering value to a prospect, thereby increasing marketing metrics such as open rates, time on site, page views, and click-through rates.

      What’s in It for Me?

      Most content has a focus on the product and the company. Content that lacks a true and deep understanding of the buyer suffers low engagement and low conversions. Our research shows that all content must answer ”What’s in it for me?” for a prospect.

      Social Proof & Authority

      Buyers that are faced with a new and unusual buying experience (such as purchasing SaaS) look at what others say about the product (social proof) and what experts say about the product (authority) to make buying decisions.

      Scarcity & Loss Framing

      Research shows that scarcity is a strong principle of influence that can be used in marketing messages. Loss framing is a variation of scarcity and can be used by outlining what a buyer will lose instead of what will be gained.

      Unify the Experience

      Use your message map to structure all customer-facing content across Sales, Product, and Marketing and create a unified and consistent experience across all touchpoints.

      Close the Gap

      SaaS marketers often find the gap between product and company-focused content and buyer-focused content to be so insurmountable that they never manage to overcome it without a framework like message mapping.

      Related SoftwareReviews Research

      Sample of 'Create a Buyer Persona and Journey' blueprint.

      Create a Buyer Persona and Journey

      Make it easier to market, sell, and achieve product-market fit with deeper buyer understanding.
      • Reduce time and treasure wasted chasing the wrong prospects.
      • Improve product-market fit.
      • Increase open and click-through rates in your lead gen engine.
      • Perform more effective sales discovery and increase eventual win rates.
      Sample of 'Diagnose Brand Health to Improve Business Growth' blueprint.

      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 it.
      • Importance of brand is recognized, endorsed, and prioritized.
      • Support and resources allocated.
      • All relevant data and information collected in one place.
      • Ability to make data-driven recommendations and decisions on how to improve.
      Sample of 'Build a More Effective Go-to-Market Strategy' blueprint.

      Build a More Effective Go-to-Market Strategy

      Creating a compelling Go-to-Market strategy, and keeping it current, is a critical software company function – as important as financial strategy, sales operations, and even corporate business development – given its huge impact on the many drivers of sustainable growth.
      • Align stakeholders on a common vision and execution plan.
      • Build a foundation of buyer and competitive understanding.
      • Deliver a team-aligned launch plan that enables commercial success.

      Bibliography

      Arakelyan, Artash. “How SaaS Companies Increase Their ROI With Content Marketing.” Clutch.co, 27 July 2018. Accessed July 2022.

      Bailyn, Evan. “Average Session Duration: Industry Benchmarks.” FirstPageSage, 16 March 2022. Accessed July 2022.

      Burstein, Daniel. “Marketing Research Chart: Average clickthrough rates by industry.” MarketingSherpa, 1 April 2014. Accessed July 2022.

      Cahoon, Sam. “Email Open Rates By Industry (& Other Top Email Benchmarks).” HubSpot, 10 June 2021. Accessed July 2022.

      Cialdini, Robert. Influence: Science and Practice. 5th ed. Pearson, 29 July 2008. Print.

      Cialdini, Robert. Influence: The Psychology of Persuasion. Revised ed. Harper Business, 26 Dec. 2006. Print.

      Content Marketing—Statistics, Evidence and Trends.” 1827 Marketing, 7 Jan. 2022. Accessed July 2022.

      Devaney, Erik. “Content Mapping 101: The Template You Need to Personalize Your Marketing.” HubSpot, 21 April 2022. Accessed July 2022.

      Hiscox Business Insurance. “Growing Your Business--and Protecting It Every Step of the Way.” Inc.com. 25 April 2022. Accessed July 2022.

      Hurley Hall, Sharon. “85 Content Marketing Statistics To Make You A Marketing Genius.” OptinMonster, 14 Jan. 2021. Accessed July 2022.

      Patel, Neil. “38 Content Marketing Stats That Every Marketer Needs to Know.” NeilPatel.com, 21 Jan. 2016. Web.

      Prater, Meg. “SaaS Sales: 7 Tips on Selling Software from a Top SaaS Company.” HubSpot, 9 June 2021. Web.

      Polykoff, Dave. “20 SaaS Content Marketing Statistics That Lead to MRR Growth in 2022.” Zenpost blog, 22 July 2022. Web.

      Rayson, Steve. “Content, Shares, and Links: Insights from Analyzing 1 Million Articles.” Moz, 8 Sept. 2015. Accessed July 2022.

      “SaaS Content Marketing: How to Measure Your SaaS Content’s Performance.” Ken Moo, 9 June 2022. Accessed July 2022.

      Taylor Gregory, Emily. “Content marketing challenges and how to overcome them.” Longitude, 14 June 2022. Accessed July 2022.

      Visitors Benchmarking Channels. Google Analytics, 2022. Accessed July 2022.

      WBR Insights. “Here's How the Relationship Between B2B Buying, Content, and Sales Reps Has Changed.” Worldwide Business Research, 2022. Accessed July 2022.

      “What’s a good bounce rate? (Here’s the average bounce rate for websites).” GrowRevenue.io, 24 Feb. 2020. Accessed July 2022.

      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.

      CIO Priorities 2023

      • Buy Link or Shortcode: {j2store}84|cart{/j2store}
      • member rating overall impact: 10.0/10 Overall Impact
      • member rating average dollars saved: $10,000 Average $ Saved
      • member rating average days saved: 9 Average Days Saved
      • Parent Category Name: IT Strategy
      • Parent Category Link: /it-strategy

      CIOs are facing these challenges in 2023:

      • Trying to understand the implications of external trends.
      • Determining what capabilities are most important to support the organization.
      • Understanding how to help the organization pursue new opportunities.
      • Preparing to mitigate new sources of organizational risk.

      Our Advice

      Critical Insight

      • While functional leaders may only see their next move, as head of the organization with a complete view of all the pieces, the CIO has full context awareness. It's up to them to assess their gaps, consider the present scenario, and then make their next move.
      • Each priority carries new opportunities for organizations that pursue them.
      • There are also different risks to mitigate as each priority is explored.

      Impact and Result

      • Inform your IT strategy for the year ahead.
      • Identify which capabilities you need to improve.
      • Add initiatives that support your priorities to your roadmap.

      CIO Priorities 2023 Research & Tools

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

      1. CIO Priorities 2023 Report – Read about the priorities on IT leaders' agenda.

      Understand the five priorities that will help navigate the opportunities and risks of the year ahead.

      • CIO Priorities 2023 Report

      Infographic

       

      Further reading

      CIO Priorities 2023

      Engage cross-functional leadership to seize opportunity while protecting the organization from volatility.

      Analyst Perspective

      Take a full view of the board and use all your pieces to win.

      In our Tech Trends 2023 report, we called on CIOs to think of themselves as chess grandmasters. To view strategy as playing both sides of the board, simultaneously attacking the opponent's king while defending your own. In our CIO Priorities 2023 report, we'll continue with that metaphor as we reflect on IT's capability to respond to trends.

      If the trends report is a study of the board state that CIOs are playing with, the priorities report is about what move they should make next. We must consider all the pieces we have at our disposal and determine which ones we can afford to use to seize on opportunity. Other pieces are best used by staying put to defend their position.

      In examining the different capabilities that CIOs will require to succeed in the year ahead, it's apparent that a siloed view of IT isn't going to work. Just like a chess player in a competitive match would never limit themselves to only using their knights or their rooks, a CIO's responsibility is to deploy each of their pieces to win the day. While functional leaders may only see their next move, as head of the organization with a complete view of all the pieces, the CIO has full awareness of the board state.

      It's up to them to assess their gaps, consider the present scenario, and then make their next move.

      This is a picture of Brian Jackson

      Brian Jackson
      Principal Research Director, Research – CIO
      Info-Tech Research Group

      CIO Priorities 2023 is informed by Info-Tech's primary research data of surveys and benchmarks

      Info-Tech's Tech Trends 2023 report and State of Hybrid Work in IT: A Trend Report inform the externalities faced by organizations in the year ahead. They imply opportunities and risks that organizations face. Leadership must determine if they will respond and how to do so. CIOs then determine how to support those responses by creating or improving their IT capabilities. The priorities are the initiatives that will deliver the most value across the capabilities that are most in demand. The CIO Priorities 2023 report draws on data from several different Info-Tech surveys and diagnostic benchmarks.

      2023 Tech Trends and Priorities Survey; N=813 (partial), n=521 (completed)
      Info-Tech's Trends and Priorities 2023 Survey was conducted between August 9 and September 9, 2022. We received 813 total responses with 521 completed surveys. More than 90% of respondents work in IT departments. More than 84% of respondents are at a manager level of seniority or higher.

      2023 The State of Hybrid Work in IT Survey; N=518
      The State of Hybrid Work in IT Survey was conducted between July 11 and July 29 and received 518 responses. Nine in ten respondents were at a manager level of seniority or higher.

      Every organization will have its own custom list of priorities based on its internal context. Organizational goals, IT maturity level, and effectiveness of capabilities are some of the important factors to consider. To provide CIOs with a starting point for their list of priorities for 2023, we used aggregate data collected in our diagnostic benchmark tools between August 1, 2021, and October 31, 2022.

      Info-Tech's CEO-CIO Alignment Program is intended to be completed by CIOs and their supervisors (CEO or other executive position [CxO]) and will provide the average maturity level and budget expectations (N=107). The IT Management and Governance Diagnostic will provide the average capability effectiveness and importance ranking to CIOs (N=271). The CIO Business Vision Diagnostic will provide stakeholder satisfaction feedback (N=259).

      The 2023 CIO priorities are based on that data, internal collaboration sessions at Info-Tech, and external interviews with CIOs and subject matter experts.

      Build IT alignment

      Assess your IT processes

      Determine stakeholder satisfaction

      Most IT departments should aim to drive outcomes that deliver better efficiency and cost savings

      Slightly more than half of CIOs using Info-Tech's CEO-CIO Alignment Program rated themselves at a Support level of maturity in 2022. That aligns with IT professionals' view of their organizations from our Tech Trends and Priorities Survey, where organizations are rated at the Support level on average. At this level, IT departments can provide reliable infrastructure and support a responsive IT service desk that reasonably satisfies stakeholders.

      In the future, CIOs aspire to attain the Transform level of maturity. Nearly half of CIOs select this future state in our diagnostic, indicating a desire to deliver reliable innovation and lead the organization to become a technology-driven firm. However, we see that fewer CxOs aspire for that level of maturity from IT. CxOs are more likely than CIOs to say that IT should aim for the Optimize level of maturity. At this level, IT will help other departments become more efficient and lower costs across the organization.

      Whether a CIO is aiming for the top of the maturity scale in the future or not, IT maturity is achieved one step at a time. Aiming for outcomes at the Optimize level will be a realistic goal for most CIOs in 2023 and will satisfy many stakeholders.

      Current and future state of IT maturity

      This image depicts a table showing the Current and future states of IT maturity.

      Trends indicate a need to focus on leadership and change management

      Trends imply new opportunities and risks that an organization must decide on. Organizational leadership determines if action will be taken to respond to the new external context based on its importance compared to current internal context. To support their organizations, IT must use its capabilities to deliver on initiatives. But if a capability's effectiveness is poor, it could hamper the effort.

      To determine what capabilities IT departments may need to improve or create to support their organizations in 2023, we conducted an analysis of our trends data. Using the opportunities and risks implied by the Tech Trends 2023 report and the State of Hybrid Work in IT: A Trend Report, we've determined the top capabilities IT will need to respond. Capabilities are defined by Info-Tech's IT Management and Governance Framework.

      Tier 1: The Most Important Capabilities In 2023

      Enterprise Application Selection & Implementation

      Manage the selection and implementation of enterprise applications, off-the-shelf software, and software as a service to ensure that IT provides the business with the most appropriate applications at an acceptable cost.

      Effectiveness: 6.5; Importance: 8.8

      Leadership, Culture, and Values

      Ensure that the IT department reflects the values of your organization. Improve the leadership skills of your team to generate top performance.

      Effectiveness: 6.9; Importance: 9

      Data Architecture

      Manage the business' databases, including the technology, the governance processes, and the people that manage them. Establish the principles, policies, and guidelines relevant to the effective use of data within the organization.

      Effectiveness: 6.3; Importance: 8.8

      Organizational Change Management

      Implement or optimize the organization's capabilities for managing the impact of new business processes, new IT systems, and changes in organizational structure or culture.

      Effectiveness: 6.1; Importance: 8.8

      External Compliance

      Ensure that IT processes and IT-supported business processes are compliant with laws, regulations, and contractual requirements.

      Effectiveness: 7.4; Importance: 8.8

      Info-Tech's Management and Diagnostic Benchmark

      Tier 2: Other Important Capabilities In 2023

      Ten more capabilities surfaced as important compared to others but not as important as the capabilities in tier 1.

      Asset Management

      Track IT assets through their lifecycle to make sure that they deliver value at optimal cost, remain operational, and are accounted for and physically protected. Ensure that the assets are reliable and available as needed.

      Effectiveness: 6.4; Importance: 8.5

      Business Intelligence and Reporting

      Develop a set of capabilities, including people, processes, and technology, to enable the transformation of raw data into meaningful and useful information for the purpose of business analysis.

      Effectiveness: 6.3; Importance: 8.8

      Business Value

      Secure optimal value from IT-enabled initiatives, services, and assets by delivering cost-efficient solutions and services and by providing a reliable and accurate picture of costs and benefits.

      Effectiveness: 6.5; Importance: 8.7

      Cost and Budget Management

      Manage the IT-related financial activities and prioritize spending through the use of formal budgeting practices. Provide transparency and accountability for the cost and business value of IT solutions and services.

      Effectiveness: 6.5; Importance: 8.8

      Data Quality

      Put policies, processes, and capabilities in place to ensure that appropriate targets for data quality are set and achieved to match the needs of the business.

      Effectiveness: 6.4; Importance: 8.9

      Enterprise Architecture

      Establish a management practice to create and maintain a coherent set of principles, methods, and models that are used in the design and implementation of the enterprise's business processes, information systems, and infrastructure.

      Effectiveness: 6.8; Importance: 8.8

      IT Organizational Design

      Set up the structure of IT's people, processes, and technology as well as roles and responsibilities to ensure that it's best meeting the needs of the business.

      Effectiveness: 6.8; Importance: 8.8

      Performance Measurement

      Manage IT and process goals and metrics. Monitor and communicate that processes are performing against expectations and provide transparency for performance and conformance.

      Effectiveness: 6; Importance: 8.4

      Stakeholder Relations

      Manage the relationship between the business and IT to ensure that the stakeholders are satisfied with the services they need from IT and have visibility into IT processes.

      Effectiveness: 6.7; Importance: 9.2

      Vendor Management

      Manage IT-related services provided by all suppliers, including selecting suppliers, managing relationships and contracts, and reviewing and monitoring supplier performance.

      Effectiveness: 6.6; Importance: 8.4

      Defining the CIO Priorities for 2023

      Understand the CIO priorities by analyzing both how CIOs respond to trends in general and how a specific CIO responded in the context of their organization.

      This is an image of the four analyses: 1: Implications; 2: Opportunities and risks; 3: Case examples; 4: Priorities to action.

      The Five CIO Priorities for 2023

      Engage cross-functional leadership to seize opportunity while protecting the organization from volatility.

      1. Adjust IT operations to manage for inflation
        • Business Value
        • Vendor Management
        • Cost and Budget Management
      2. Prepare your data pipeline to train AI
        • Business Intelligence and Reporting
        • Data Quality
        • Data Architecture
      3. Go all in on zero-trust security
        • Asset Management
        • Stakeholder Relations
        • External Compliance
      4. Engage employees in the digital age
        • Leadership, Culture, and Values
        • Organizational Change Management
        • Enterprise Architecture
      5. Shape the IT organization to improve customer experience
        • Enterprise Application Selection & Implementation
        • Performance Measurement
        • IT Organizational Design

      Adjust IT operations to manage for inflation

      Priority 01

      • APO06 Cost and Budget Management
      • APo10 Vendor Management
      • EDM02 Business Value

      Recognize the relative impact of higher inflation on IT's spending power and adjust accordingly.

      Inflation takes a bite out of the budget

      Two-thirds of IT professionals are expecting their budgets to increase in 2023, according to our survey. But not every increase is keeping up with the pace of inflation. The International Monetary Fund forecasts that global inflation rose to 8.8% in 2022. It projects it will decline to 6.5% in 2023 and 4.1% by 2024 (IMF, 2022).

      CIOs must account for the impact of inflation on their IT budgets and realize that what looks like an increase on paper is effectively a flat budget or worse. Applied to our survey takers, an IT budget increase of more than 6.5% would be required to keep pace with inflation in 2023. Only 40% of survey takers are expecting that level of increase. For the 27% expecting an increase between 1-5%, they are facing an effective decrease in budget after the impact of inflation. Those expecting no change in budget or a decrease will be even worse off.

      Looking ahead to 2023, how do you anticipate your IT spending will change compared to spending in 2022?

      Global inflation estimates by year

      2022 8.8%
      2023 6.5%
      2024 4.1%

      International Monetary Fund, 2022

      CIOs are more optimistic about budgets than their supervisors

      Data from Info-Tech's CEO-CIO Alignment Diagnostic benchmark also shows that CIOs and their supervisors are planning for increases to the budget. This diagnostic is designed for a CIO to use with their direct supervisor, whether it's the CEO or otherwise (CxO). Results show that on average, CIOs are more optimistic than their supervisors that they will receive budget increases and headcount increases in the years ahead.

      While 14% of CxOs estimated the IT budget would see no change or a decrease in the next three to five years, only 3% of CIOs said the same. A larger discrepancy is seen in headcount, where nearly one-quarter of CXOs estimated no change or decrease in the years ahead, versus only 10% of CIOs estimating the same.

      When we account for the impact of inflation in 2023, this misalignment between CIOs and their supervisors increases. When adjusting for inflation, we need to view the responses projecting an increase of between 1-5% as an effective decrease. With the inflation adjustment, 26% of CXOs are predicting IT budgets to stay flat or see a decrease compared to only 10% of CIOs.

      CIOs should consider how inflation has affected their projected spending power over the past year and take into account projected inflation rates over the next couple of years. Given that the past decade has seen inflation rates between 2-3%, the higher rates projected will have more of an impact on organizational budgets than usual.

      Expect headcount to stay flat or decline over 3-5 years

      CIO: 10%; CXO: 24%

      IT budget expectations to stay flat or decrease before inflation

      CIO: 13.6 %; CXO: 3.2%

      IT budget expectations to stay flat or decrease adjusted for inflation

      CIO: 25.8%; CXO: 9.7%

      Info-Tech's CEO-CIO Alignment Program

      Opportunities

      Appoint a "cloud economist"

      Organizations that migrated from on-premises data centers to infrastructure as a service shifted their capital expenditures on server racks to operational expenditures on paying the monthly service bill. Managing that monthly bill so that it is in line with desired performance levels now becomes crucial. The expected benefit of the cloud is that an organization can turn the dial up to meet higher demand and turn it down when demand slows. In practice this is sometimes more difficult to execute than anticipated. Some IT departments realize their cloud-based data flows aren't always connected to the revenue-generating activity seen in the business. As a result, a "cloud economist" is needed to closely monitor cloud usage and adjust it to financial expectations. Especially during any recessionary period, IT departments will want to avoid a "bill shock" incident.

      Partner with technology providers

      Keep your friends close and your vendors closer. Look for opportunities to create leverage with your strategic vendors to unlock new opportunities. Identify if a vendor you work with is not entrenched in your industry and offer them the credibility of working with you in exchange for a favorable contract. Offering up your logo for a website listing clients or giving your own time to speak in a customer session at a conference can go a long way to building up some goodwill with your vendors. That's goodwill you'll need when you ask for a new multi-year contract on your software license without annual increases built into the structure.

      Demonstrate IT projects improve efficiency

      An IT department that operates at the Optimize level of Info-Tech's maturity scale can deliver outcomes that lower costs for other departments. IT can defend its own budget if it's able to demonstrate that its initiatives will automate or augment business activities in a way that improves margins. The argument becomes even more compelling if IT can demonstrate it is supporting a revenue-generating initiative or customer-facing experience. CIOs will need to find business champions to vouch for the important contributions IT is making to their area.

      Risks

      Imposition of non-financial reporting requirements

      In some jurisdictions, the largest companies will be required to start collecting information on carbon emissions emitted as a result of business activities by the end of next year. Smaller sized organizations will be next on the list to determine how to meet new requirements issued by various regulators. Risks of failure include facing fines or being shunned by investors. CIOs will need to support their financial reporting teams in collecting the new required data accurately. This will incur new costs as well.

      Rising asset costs

      Acquiring IT equipment is becoming more expensive due to overall inflation and specific pressures around semiconductor supply chains. As a result, more CIOs are extending their device refresh policies to last another year or two. Still, demands for new devices to support new hybrid work models could put pressure on budgets as IT teams are asked to modernize conferencing rooms. For organizations adopting mixed reality headsets, cutting-edge capabilities will come at a premium. Operating costs of devices may also increase as inflation increases costs of the electricity and bandwidth they depend on.

      CASE STUDY
      Leverage your influence in vendor negotiations

      Denise Cornish, Associate VP of IT and Deputy COO,
      Western University of Health Sciences

      Since taking on the lead IT role at Western University in 2020, Denise Cornish has approached vendor management like an auditable activity. She evaluates the value she gets from each vendor relationship and creates a list of critical vendors that she relies upon to deliver core business services. "The trick is to send a message to the vendor that they also need us as a customer that's willing to act as a reference," she says. Cornish has managed to renegotiate a contract with her ERP vendor, locking in a multi-year contract with a very small escalator in exchange for presenting as a customer at conferences. She's also working with them on developing a new integration to another piece of software popular in the education space.

      Western University even negotiated a partnership approach with Apple for a program run with its College of Osteopathic Medicine of the Pacific (COMP) called the Digital Doctor Bag. The partnership saw Apple agree to pre-package a customer application developed by Western that delivered the curriculum to students and facilitated communications across students and faculty. Apple recognized Western as an Apple Distinguished School, a program that recognizes innovative schools that use Apple products.

      "I like when negotiations are difficult.
      I don't necessarily expect a zero-sum game. We each need to get something out of this and having the conversation and really digging into what's in it for you and what's in it for me, I enjoy that. So usually when I negotiate a vendor contract, it's rare that it doesn't work out."

      CASE STUDY
      Control cloud costs with a simplified approach

      Jim Love, CIO, IT World Canada

      As an online publisher and a digital marketing platform for technology products and services companies, IT World Canada (ITWC) has observed that there are differences in how small and large companies adopt the cloud as their computing infrastructure. For smaller companies, even though adoption is accelerating, there may still be some reluctance to fully embrace cloud platforms and services. While larger companies often have a multi-cloud approach, this might not be practical for smaller IT shops that may struggle to master the skills necessary to effectively manage one cloud platform. While Love acknowledges that the cloud is the future of corporate computing, he also notes that not all applications or workloads may be well suited to run in the cloud. As well, moving data into the cloud is cheap but moving it back out can be more expensive. That is why it is critical to understand your applications and the data you're working with to control costs and have a successful cloud implementation.

      "Standardization is the friend of IT. So, if you can standardize on one platform, you're going to do better in terms of costs."

      From priorities to action

      Go deeper on pursuing your priorities by improving the associated capabilities.

      Improve Cost and Budget Management

      Take control of your cloud costs by providing central financial oversight on the infrastructure-as-a-service provider your organization uses. Create visibility into your operational costs and define policies to control them. Right-size the use of cloud services to stay within organizational budget expectations.

      Take Control of Cloud Costs on AWS

      Take Control of Cloud Costs on Microsoft Azure

      Improve Business Value

      Reduce the funds allocated to ongoing support and impose tougher discipline around change requests to lighten your maintenance burden and make room for investment in net-new initiatives to support the business.

      Free up funds for new initiatives

      Improve Vendor Management

      Lay the foundation for a vendor management process with long-term benefits. Position yourself as a valuable client with your strategic vendors and leverage your position to improve your contract terms.

      Elevate Your Vendor Management Initiative

      Prepare your data pipeline to train AI

      Priority 02

      • ITRG06 BUSINESS INTELLIGENCE AND REPORTING
      • ITRG07 DATA ARCHITECTURE
      • ITRG08 DATA QUALITY

      Keep pace as the market adopts AI capabilities, and be ready to create competitive advantage.

      Today's innovation is tomorrow's expectation

      During 2022, some compelling examples of generative-AI-based products took the world by storm. Images from AI-generating bots Midjourney and Stable Diffusion went viral, flooding social media and artistic communities with images generated from text prompts. Exchanges with OpenAI's ChatGPT bot also caught attention, as the bot was able to do everything from write poetry, to provide directions on a cooking recipe and then create a shopping list for it, to generate working code in a variety of languages. The foundation models are trained with AI techniques that include generative adversarial networks, transformers, and variational autoencoders. The end result is an algorithm that can produce content that's meaningful to people based on some simple direction. The industry is only beginning to come to grips with how this sort of capability will disrupt the enterprise.

      Slightly more than one-third of IT professionals say their organization has already invested in AI or machine learning. It's the sixth-most popular technology to have already invested in after cloud computing (82%), application programming interfaces (64%), workforce management solutions (44%), data lakes (36%), and next-gen cybersecurity (36%). It's ahead of 12 other technologies that IT is already invested in.

      When we asked what technologies organizations planned to invest in for next year, AI rocketed up the list to second place, as it's selected by 44% of IT professionals. It falls behind only cloud computing. This jump up the list makes AI the fastest growing technology for new investment from organizations.

      Many AI capabilities seem cutting edge now, but organizations are prioritizing it as a technology investment. In a couple of years, access to foundational models that produce images, text, or code will become easy to access with a commercial license and an API integration. AI will become embedded in off-the-shelf software and drive many new features that will quickly become commonplace.

      To stay even with the competition and meet customer expectations, organizations will have to work to at least adopt these AI-enhanced products and services. For those that want to create a competitive advantage, they will have to build a data pipeline that is capable of training their own custom AI models based on their unique data sets.

      Which of the following technology categories has your organization already invested in?

      A bar graph is depicted the percentage of organizations which already had invested in the following Categories: Cloud Computing; Application Programming; Next-Gen Cybersecurity; Workforce Management Solutions; Data Lake/Lakehouse; Artificial Intelligence or Machine Learning.

      Which of those same technologies does your organization plan to invest in by the end of 2023?

      A bar graph is depicted the percentage of organizations which plan to invest in the following categories by the end of 2023: No-Code / Low-Code Platforms; Next-Gen Cybersecurity; Application Programming Interfaces (APIs); Data Lake / Lakehouse; Artificial Intelligence (AI) or Machine Learning; Cloud Computing

      Tech Trends 2023 Survey

      Data quality and governance will be critical to customize generative AI

      Data collection and analysis are on the minds of both CIOs and their supervisors. When asked what technologies the business should adopt in the next three to five years, big data (analytics) ranked as most critical to adopt among CIOs and their supervisors. Big data (collection) ranked fourth out of 11 options.

      Organizations that want to drive a competitive advantage from generative AI will need to train these large, versatile models on their own data sets. But at the same time, IT organizations are struggling to provide clean data. The second-most critical gap for IT organizations on average is data quality, behind only organizational change management. Organizations know that data quality is important to support analytics goals, as algorithms can suffer in their integrity if they don't have reliable data to work with. As they say, garbage in, garbage out.

      Another challenge to overcome is the gap seen in IT governance, the sixth largest gap on average. Using data toward training custom generative models will hold new compliance and ethical implications for IT departments to contend with. How user data can be leveraged is already the subject of privacy legislation in many different jurisdictions, and new AI legislation is being developed in various places around the world that could create further demands. In some cases, users are reacting negatively to AI-generated content.

      Biggest capability gaps between rated importance and effectiveness

      This is a Bar graph showing the capability gaps between rated importance and effectiveness.

      IT Management and Governance Diagnostic

      Most critical technologies to adopt rated by CIOs and their supervisors

      This is a Bar graph showing the most critical technologies to adopt as rated by CIO's and their supervisors

      CEO-CIO Alignment Program

      Opportunities

      Enterprise content discovery

      Many organizations still cobble together knowledgebases in SharePoint or some other shared corporate drive, full of resources that no one quite knows how to find. A generative AI chatbot holds potential to be trained on an organization's content and produce content based on an employee's queries. Trained properly, it could point employees to the right resource they need to answer their question or just provide the answer directly.

      Supply chain forecasts

      After Hurricane Ian shut down a Walmart distribution hub, the retailer used AI to simulate the effects on its supply chain. It rerouted deliveries from other hubs based on the predictions and planned for how to respond to demand for goods and services after the storm. Such forecasts would typically take a team of analysts days to compose, but thanks to AI, Walmart had it done in a matter of hours (The Economist, 2022).

      Reduce the costs of AI projects

      New generative AI models of sufficient scale offer advantages over previous AI models in their versatility. Just as ChatGPT can write poetry or dialogue for a play or perhaps a section of a research report (not this one, this human author promises), large models can be deployed for multiple use cases in the enterprise. One AI researcher says this could reduce the costs of an AI project by 20-30% (The Economist, 2022).

      Risks

      Impending AI regulation

      Multiple jurisdictions around the world are pursuing new legislation that imposes requirements on organizations that use AI, including the US, Europe, and Canada. Some uses of AI will be banned outright, such as the real-time use of facial recognition in public spaces, while in other situations people can opt out of using AI and work with a human instead. Regulations will take the risk of the possible outcomes created by AI into consideration, and organizations will often be required to disclose when and how AI is used to reach decisions (Science | Business, 2022). Questions around whether creators can prevent their content from being used for training AI are being raised, with some efforts already underway to collect a list of those who want to opt out. Organizations that adopt a generative AI model today may find it needs to be amended for copyright reasons in the future.

      Bias in the algorithms

      Organizations using a large AI model trained by a third party to complete their tasks or as a foundation to further customize it with their own data will have to contend with the inherent bias of the algorithm. This can lead to unintended negative experiences for users, as it did for MIT Technology Review journalist Melissa Heikkilä when she uploaded her images to AI avatar app Lensa, only to have it render a collection of sexualized portraits. Heikkilä contends that her Asian heritage overly influenced the algorithm to associate her with video-game characters, anime, and adult content (MIT Technology Review, 2022).

      Convincing nonsense

      Many of the generative AI bots released so far often create very good responses to user queries but sometimes create nonsense that at first glance might seem to be accurate. One example is Meta's Galactica bot – intended to streamline scientific research discovery and aid in text generation – which was taken down only three days after being made available. Scientists found that it generated fake research that sounded convincing or failed to do math correctly (Spiceworks, 2022).

      CASE STUDY
      How MLSE enhances the Toronto Raptors' competitiveness with data-driven practices

      Christian Magsisi, Vice President of Venue and Digital Technology, MLSE

      At the Toronto Raptors practice facility, the OVO Athletic Centre, a new 120-foot custom LG video screen towers over the court. The video board is used to playback game clips so coaches can use them to teach players, but it also displays analytics from algorithmic models that are custom-made for each player. Data on shot-making or defensive deflections are just a couple examples of what might inform the players.

      Vice President of Digital Technology Christian Magsisi leads a functional Digital Labs technical group at MLSE. The in-house team builds the specific data models that support the Raptors in their ongoing efforts to improve. The analytics are fed by Noah Analytics, which uses cognitive vision to provide real-time feedback on shot accuracy. SportsVU is a motion capture system that represents how players are positioned on the court, with detail down to which way they are facing and whether their arms are up or down. The third-party vendors provide the solutions to generate the analytics, but it's up to MLSE's internal team to shape them to be actionable for players during a practice.

      "All the way from making sure that a specific player is achieving the results that they're looking for and showing that through data, or finding opportunities for the coaching staff. This is the manifestation of it in real life. Our ultimate goal with the coaches was to be able to take what was on emails or in a report and sometimes even in text message and actually implement it into practice."

      Read the full story on Spiceworks Insights.

      How MLSE enhances the Toronto Raptors' competitiveness with data-driven practices (cont.)

      Humza Teherany, Chief Technology Officer, MLSE

      MLSE's Digital Labs team architects its data insights pipeline on top of cloud services. Amazon Web Services Rekognition provides cognitive vision analysis from video and Amazon Kinesis provides the video processing capabilities. Beyond the court, MLSE uses data to enhance the fan experience, explains CTO Humza Teherany. It begins with having meaningful business goals about where technology can provide the most value. He starts by engaging the leadership of the organization and considering the "art of the possible" when it comes to using technology to unlock their goals.

      Humza Teherany (left) and Christian Magsisi lead MLSE's digital efforts for the pro sports teams owned by the group, including the Toronto Raptors, Toronto Maple Leafs, and Toronto Argonauts. (Photo by Brian Jackson).

      Read the full story on Spiceworks Insights.

      "Our first goal in the entire buildup of the Digital Labs organization has been to support MLSE and all of our teams. We like to do things first. We leverage our own technology to make things better for our fans and for our teams to complete and find incremental advantages where possible."
      Humza Teherany,
      Chief Technology Officer, MLSE

      From priorities to action

      Go deeper on pursuing your priorities by improving the associated capabilities.

      Improve Data Quality

      The performance of AI-assisted tools depends on mature IT operations processes and reliable data sets. Standardize service management processes and build a knowledgebase of structured content to prepare for AI-assisted IT operations.

      Prepare for Cognitive Service Management

      Improve Business Intelligence and Reporting

      Explore the enterprise chatbots that are available to not only assist with customer interactions but also help your employees find the resources they need to do their jobs and retrieve data in real time.

      Explore the best chatbots software

      Improve Data Architecture

      Understand if you are ready to embark on the AI journey and what business use cases are appropriate for AI. Plan around the organization's maturity in people, tools, and operations for delivering the correct data, model development, and model deployment and managing the models in the operational areas.

      Create an Architecture for AI

      Go all in on zero-trust security

      Priority 03

      • BAI09 ASSET MANAGEMENT
      • APO08 STAKEHOLDER RELATIONS
      • MEA03 EXTERNAL COMPLIANCE

      Adopt zero-trust architecture as the new security paradigm across your IT stack and from an organizational risk management perspective.

      Putting faith in zero trust

      The push toward a zero-trust security framework is becoming necessary for organizations for several different reasons over the past couple of years. As the pandemic forced workers away from offices and into their homes, perimeter-based approaches to security were challenged by much wider network footprints and the need to identify users external to the firewall. Supply-chain security became more of a concern with notable attacks affecting many thousands of firms, some with severe consequences. Finally, the regulatory pressure to implement zero trust is rising following President Joe Biden's 2021 Executive Order on Improving the Nation's Cybersecurity. It directs federal agencies to implement zero trust. That will impact any company doing business with the federal government, and it's likely that zero trust will propagate through other government agencies in the years ahead. Zero-trust architecture can also help maintain compliance around privacy-focused regulations concerned about personal data (CSO Online, 2022).

      IT professionals are modestly confident that they can meet new government legislation regarding cybersecurity requirements. When asked to rank their confidence on a scale of one to five, the most common answer was 3 out of 5 (38.5%). The next most common answer was 4 out of 5 (33.3%).

      Zero-trust barriers:
      Talent shortage and lack of leadership involvement

      Out of a list of challenges, IT professionals are most concerned with talent shortages leading to capacity constraints in cybersecurity. Fifty-four per cent say they are concerned or very concerned with this issue. Implementing a new zero-trust framework for security will be difficult if capacity only allows for security teams to respond to incidents.

      The next most pressing concern is that cyber risks are not on the radar of executive leaders or the board of directors, with 46% of IT pros saying they are concerned or very concerned. Since zero-trust requires that organizations take an enterprise risk management approach to cybersecurity and involve top decision makers, this reveals another area where organizations may fall short of achieving a zero-trust environment.

      How confident are you that your organization is prepared to meet current and future government legislation regarding cybersecurity requirements? A circle graph is shown with 68.6% colored dark green, and the words: AVG 3.43 written inside the graph.
      a bar graph showing the confidence % for numbers 1-5
      54%

      of IT professionals are concerned with talent shortages leading to capacity constraints in cybersecurity.

      46%

      of IT professionals are concerned that cyber risks are not on the radar of executive leaders or the board of directors.

      Zero trust mitigates risk while removing friction

      A zero-trust approach to security requires organizations to view cybersecurity risk as part of its overall risk framework. Both CIOs and their supervisors agree that IT-related risks are a pain point. When asked to rate the severity of pain points, 58% of CIOs rated IT-related business risk incidents as a minor pain or major pain. Their supervisors were more concerned, with 61% rating it similarly. Enterprises can mitigate this pain point by involving top levels of leadership in cybersecurity planning.

      Organizations can be wary about implementing new security measures out of concern it will put barriers between employees and what they need to work. Through a zero-trust approach that focuses on identity verification, friction can be avoided. Overall, IT organizations did well to provide security without friction for stakeholders over the past 18 months. Results from Info-Tech's CIO Business Vision Diagnostic shows that stakeholders almost all agree friction due to security practices are acceptable. The one area that stands to be improved is remote/mobile device access, where 78.3% of stakeholders view the friction as acceptable.

      A zero-trust approach treats user identity the same regardless of device and whether it is inside or outside of the corporate network. This can remove friction when workers are looking to connect remotely from a mobile device.

      IT-related business risk incidents viewed as a pain point

      CXO 61%
      CIO 58%

      Business stakeholders rate security friction levels as acceptable

      A bar graph is depicted with the following dataset: Regulatory Compliance: 93.80%; Office/Desktop Computing:	86.50%;Data Access/Integrity: 86.10%; Remote/Mobile Device Access:	78.30%;

      CIO Business Vision Diagnostic, N=259

      Opportunities

      Move to identity-driven access control

      Today's approach to access control on the network is to allow every device to exchange data with every other device. User endpoints and servers talk to each other directly without any central governance. In a zero-trust environment, a centralized zero-trust network access broker provides one-to-one connectivity. This allows servers to rest offline until needed by a user with the right access permissions. Users verify their identity more often as they move throughout the network. The user can access the resources and data they need with minimal friction while protecting servers from unauthorized access. Log files are generated for analysis to raise alerts about when an authorized identity has been compromised.

      Protect data with just-in-time authentication

      Many organizations put process in place to make sure data at rest is encrypted, but often when users copy that data to their own devices, it becomes unencrypted, allowing attackers opportunities to exfiltrate sensitive data from user endpoints. Moving to a zero-trust environment where each data access is brokered by a central broker allows for encryption to be preserved. Parties accessing a document must exchange keys to gain access, locking out unauthorized users that don't have both sets of keys to decrypt the data (MIT Lincoln Laboratory, 2022).

      Harness free and open-source tools to deploy zero trust

      IT teams may not be seeing a budget infusion to invest in a new approach to security. By making use of the many free and open-source tools available, they can bootstrap their strategy into reality. Here's a list to get started:

      PingCastle Wrangle your Active Directory and find all the domains that you've long since forgotten about and manage the situation appropriately. Also builds a spoke-and-hub map of your Active Directory.

      OpenZiti Create an overlay network to enable programmable networking that supports zero trust.

      Snyk Developers can automatically find and fix vulnerabilities before they commit their code. This vendor offers a free tier but users that scale up will need to pay.

      sigstore Open-source users and maintainers can use this solution to verify the code they are running is the code the developer intended. Works by stitching together free services to facilitate software signing, verify against a transparent ledger, and provide auditable logs.

      Microsoft's SBOM generation tool A software bill of materials is a requirement in President Biden's Executive Order, intended to provide organizations with more transparency into their software components by providing a comprehensive list. Microsoft's tool will work with Windows, Linux, and Mac and auto-detect a longlist of software components, and it generates a list organized into four sections that will help organizations comprehend their software footprint.

      Risks

      Organizational culture change to accommodate zero trust

      Zero trust requires that top decision makers get involved in cybersecurity by treating it as an equal consideration of overall enterprise risk. Not all boards will have the cybersecurity expertise required, and some executives may not prioritize cybersecurity despite the warnings. Organizations that don't appoint a chief information security officer (CISO) role to drive the cybersecurity agenda from the top will be at risk of cybersecurity remaining an afterthought.

      Talent shortage

      No matter what industry you're in or what type of organization you run, you need cybersecurity. The demand for talent is very high and organizations are finding it difficult to hire in this area. Without the talent needed to mature cybersecurity approaches to a zero-trust model, the focus will remain on foundational principles of patch management to eliminate vulnerabilities and intrusion prevention. Smaller organizations may want to consider a "virtual CISO" that helps shape the organizational strategy on a part-time basis.

      Social engineering

      Many enterprise security postures remain vulnerable to an attack that commandeers an employee's identity to infiltrate the network. Hosted single sign-on models provide low friction and continuity of identity across applications but also offer a single point of failure that hackers can exploit. Phishing scams that are designed to trick an employee into providing their credentials to a fake website or to just click on a link that delivers a malware payload are the most common inroads that criminals take into the corporate network. Being aware of how user behavior influences security is crucial.

      CASE STUDY
      Engage the entire organization with cybersecurity awareness

      Serge Suponitskiy, CIO, Brosnan Risk Consultants

      Brosnan provides private security services to high-profile clients and is staffed by security experts with professional backgrounds in intelligence services and major law enforcement agencies. Safe to say that security is taken seriously in this culture and CIO Serge Suponitskiy makes sure that extends to all back-office staff that support the firm's activities. He's aware that people are often the weakest link in a cybersecurity posture and are prone to being fooled by a phishing email or even a fraudulent phone call. So cybersecurity training is an ongoing activity that takes many forms. He sends out a weekly cybersecurity bulletin that features a threat report and a story about the "scam of the week." He also uses KnowBe4, a tool that simulates phishing attacks and trains employees in security awareness. Suponitskiy advises reaching out to Marketing or HR for help with engaging employees and finding the right learning opportunities.

      "What is financially the best solution to protect yourself? It's to train your employees. … You can buy all of the tools and it's expensive. Some of the prices are going up for no reason. Some by 20%, some by 50%, it's ridiculous. So, the best way is to keep training, to keep educating, and to reimagine the training. It's not just sending this video that no one clicks on or posting a poster no one looks at. … Given the fact we're moving into this recession world, and everyone is questioning why we need to spend more, it's time to reimagine the training approach."

      CASE STUDY
      Focus on micro-segmentation as the foundation of zero trust

      David Senf, National Cybersecurity Strategist, Bell

      As a cybersecurity analyst and advisor that works with Bell's clients, David Senf sees zero-trust security as an opportunity for organizations to put a strong set of mitigating controls in place to defend against the thorny challenge of reducing vulnerabilities in their software supply chain. With major breaches being linked to widely used software in the past couple of years, security teams might find it effective to focus on a different layer of security to prevent certain breaches. With security policy being enforced at a narrow point/perimeter, attacks are in essence blocked from exploiting application vulnerabilities (e.g. you can't exploit what you can see). Organizations must still ensure there is a solid vulnerability management program in place, but surrounding applications with other controls is critical. One aspect of zero trust, micro-segmentation, which is an approach to network management, can limit the damage caused by a breach. The solutions help to map out and protect the different connections between applications that could otherwise be abused for discovery or lateral movement. Senf advises that knowing your inventory of software and the interdependencies between applications is the first step on a zero-trust journey, before putting protection and detection in place.

      "Next year will be a year of a lot more ZTNA, zero-trust network access, being deployed. So, I think that will give organizations more of an understanding of what zero trust is as well, from a really basic perspective. If I can just limit what applications you can see and no one can even see that application, it's undiscoverable because I've got that ZTNA solution in place. … I would see that as a leading area of deployment and coming to understand what zero trust is in 2023."

      From priorities to action

      Go deeper on pursuing your priorities by improving the associated capabilities.

      Improve Asset Management

      Enable reduced friction in the remote user experience by underpinning it with a hardware asset management program. Creating an inventory of devices and effectively tracking them will aid in maintaining compliance, result in stronger policy enforcement, and reduce the harm of a lost or stolen device.

      Implement Hardware Asset Management

      Improve Stakeholder Relations

      Communicate the transition from a perimeter-based security approach to an "Always Verify" approach with a clear roadmap toward implementation. Map key protect surfaces to business goals to demonstrate the importance of zero-trust security in helping the organization succeed. Help the organization's top leadership build awareness of cybersecurity risk.

      Build a Zero Trust Roadmap

      Improve External Compliance

      Manage the challenge of meeting new government requirements to implement zero-trust security and other data protection and cybersecurity regulations with a compliance program. Create a control environment that aligns multiple compliance regimes, and be prepared for IT audits.

      Build a Security Compliance Program

      Engage employees in the digital age

      Priority 04

      • ITRG02 LEADERSHIP, CULTURE, AND VALUES
      • BAI05 ORGANIZATIONAL CHANGE MANAGEMENT
      • APO03 ENTERPRISE ARCHITECTURE

      Lead a strong culture through digital means to succeed in engaging the hybrid workforce.

      The new deal for employers in a hybrid work world

      Necessity is the mother of innovation.

      The pandemic's disruption for non-essential workers looks to have a long-lasting, if not permanent, effect on the relationship between employer and employee. The new bargain for almost all organizations is a hybrid work reality, with employees splitting time between the office and working remotely, if not working remotely full-time. IT is in a unique position in the organization as it must not only contend with the shift to this new deal with its own employees but facilitate it for the entire organization.

      With 90% of organizations embracing some form of hybrid work, IT leaders have an opportunity to shift from coping with the new work reality to finding opportunities to improve productivity. Organizations that embrace a hybrid model for their IT departments see a more effective IT department. Organizations that offered no remote work for IT rated their IT effectiveness on average 6.2 out of 10, while organizations with at least 10% of IT roles in a hybrid model saw significantly higher effectiveness. At minimum, organizations with between 50%-70% of IT roles in a hybrid model rated their effectiveness at 6.9 out of 10.

      IT achieved this increase in effectiveness during a disruptive time that often saw IT take on a heavier burden. Remote work required IT to support more users and be involved in facilitating more work processes. Thriving through this challenging time is a win that's worth sharing with the rest of the organization.

      90% of organizations are embracing some form of hybrid work.

      IT's effectiveness compared to % working hybrid or remotely

      A bar graph is shown which compares the effectiveness of IT work with hybrid and full remote work, compared to No Remote Work for IT.

      High effectiveness doesn't mean high engagement

      Despite IT's success with hybrid work, CIOs are more concerned about their staff sufficiency, skill, and engagement than their supervisors. Among clients using our CEO-CIO Alignment Diagnostic, 49% of CIOs considered this issue a major pain point compared to only 32% of CXOs. While IT staff are more effective than ever, even while carrying more of a burden in the digital age, CIOs are still looking to improve staff engagement.

      Info-Tech's State of Hybrid Work Survey illuminates further details about where IT leaders are concerned for their employee engagement. About four in ten IT leaders say they are concerned for employee wellbeing, and almost the same amount say they are concerned they are not able to see signs that employees are demotivated (N=518).

      Boosting IT employees' engagement levels to match their effectiveness will require IT leaders to harness all the tools at their disposal. Communicating culture and effectively managing organizational change in the digital age is a real test of leadership.

      Staff sufficiency, skill, and engagement issues as a major pain point

      CXO 32%
      CIO 49%

      CEO-CIO Alignment Diagnostic

      Opportunities

      Drive effectiveness with a hybrid environment

      IT leaders concerned about the erosion of culture and connectedness due to hybrid work can mitigate those effects with increased and improved communication. Among highly effective IT departments, 55% of IT leaders made themselves highly available through instant messaging chat. Another 54% of highly effective leaders increased team meetings (State of Hybrid Work Survey, n=213). The ability to adapt to the team's needs and use a number of tactics to respond is the most important factor. The greater the number of tactics used to overcome communication barriers, the more effective the IT department (State of Hybrid Work Survey, N=518).

      Modernize the office conference room

      A hybrid work approach emphasizes the importance of not only the technology in the office conference room but the process around how meetings are conducted. Creating an equal footing for all participants regardless of how they join is the goal. In pursuit of that, 63% of organizations say they have made changes or upgrades to their conference room technology (n=496). The conferencing experience can influence employee engagement and work culture and enhance collaboration. IT should determine if the business case exists for upgrades and work to decrease the pain of using legacy solutions where possible (State of Hybrid Work in IT: A Trend Report).

      Understand the organizational value chain

      Map out the value chain from the customer perspective and then determine the organizational capabilities involved in delivering on that experience. It is a useful tool for helping IT staff understand how they're connected to the customer experience and organizational mission. It's crucial to identify opportunities to resolve pain points and create more efficiency throughout the organization.

      Risks

      Talent rejects the working model

      Many employees that experienced hybrid work over the past couple of years are finding it's a positive development for work/life balance and aren't interested in a full-time return to the office. Organizations that insist on returning all employees to the office all the time may find that employees choose to leave the organization. Similarly, it could be hard to hire IT talent in a competitive market if the position is required to be onsite every day. Most organizations are providing flexible options to employees and finding ways to manage work in the new digital age.

      Wasted expense on facilities

      Organizations may choose to keep their physical office only to later realize that no one is going to work there. While providing an office space can help foster positive culture through valuable face time, it has to be used intentionally. Managers should plan for specific days that their teams will meet in the office and make sure that work activities take advantage of everyone being in the same place at the same time. Asking everyone to come in so that they can be on a videoconference meeting in their cubicle isn't the point.

      Isolated employees and teams

      Studies on a remote work environment show it has an impact on how many connections each employee maintains within the company. Employees still interact well within their own teams but have fewer interactions across departments. Overall, workers are likely to collaborate just as often as they did when working in the office but with fewer other individuals at the company. Keep the isolating effect of remote work in mind and foster collaboration and networking opportunities across different departments (BBC News, 2022).

      CASE STUDY
      Equal support of in-office and remote work

      Roberto Eberhardt, CIO, Ontario Legislative Assembly

      Working in the legislature of the Ontario provincial government, CIO Roberto Eberhardt's staff went from a fully onsite model to a fully remote model at the outset of the pandemic. Today he's navigating his path to a hybrid model that's somewhere in the middle. His approach is to allow his business colleagues to determine the work model that's needed but to support a technology environment that allows employees to work from home or in the office equally. Every new process that's introduced must meet that paradigm, ensuring it will work in a hybrid environment. For his IT staff, he sees a culture of accountability and commitment to metrics to drive performance measurement as key to the success of this new reality.

      "While it's good in a way, the challenge for us is it became a little more complex because you have to account for all those things in the office environment and in the remote work approach. Everything you do now, you have to say OK well how is this going to work in this world and how will it work in the other world?"

      Creating purpose for IT through strategy

      Mike Russell, Virginia Community College System

      At the Virginia Community College System (VCCS), CIO Mike Russell's IT team supports an organization that governs and delivers services to all community colleges in the state. Russell sees his IT team's purpose as being driven by the organization's mission to ensure success throughout the entire student journey, from enrolment to becoming employed after graduation. That customer-focused mindset starts from the top-level leadership, the chancellor, and the state governor. The VCCS maintains a six-year business plan that informs IT's strategic plan and aligns IT with the mission, and both plans are living documents that get refreshed every two years. Updating the plans provides opportunities for the chancellor to engage the organization and remind everyone of the purpose of their work.

      "The outcome isn't the degree. The outcome we're trying to measure is the job. Did you get the job that you wanted? Whether it's being re-employed or first-time employment, did you get what you were after?"

      From priorities to action

      Go deeper on pursuing your priorities by improving the associated capabilities.

      Improve Leadership, Culture, and Values

      Help leaders manage their teams effectively in a hybrid environment by providing them with the right tools and tactics to manage the challenges of hybrid work. Focus on promoting teamwork and fostering connection.

      Prepare People Leaders for the Hybrid Work Environment

      Improve Organizational Change Management

      Assign accountability for managing the changes that the organization is experiencing in the digital age. Make a people-centric approach that takes human behavior into account and plans to address different needs in different ways. Be proactive about change.

      Master Organizational Change Management Practices

      Improve Enterprise Architecture

      Develop a foundation for aligning IT's activities with business value by creating a right-sized enterprise architecture approach that isn't heavy on bureaucracy. Drive IT's purpose by illustrating how their work contributes to the overall mission and the customer experience.

      Create a Right-Sized Enterprise Architecture Governance Framework

      Shape the IT organization to improve customer experience

      PRIORITY 05

      • BAI03 ENTERPRISE APPLICATION SELECTION & IMPLEMENTATION
      • MEA01 PERFORMANCE MEASUREMENT
      • ITRG01 IT ORGANIZATIONAL DESIGN

      Tightly align the IT organization with the organization's value chain from a customer perspective.

      IT's value is defined by faster, better, bigger

      The pandemic motivated organizations to accelerate their digital transformation efforts, digitalizing more of their tasks and organizing the company's value chain around satisfying the customer experience. Now we see organizations taking their foot off the gas pedal of digitalization and shifting their focus to extracting the value from their investments. They want to execute on the digital transformation in their operations and realize the vision they set out to achieve.

      In our Trends Report we compared the emphasis organizations are putting on digitalization to last year. Overall, we see that most organizations shifted fewer of their processes to digital in the past year.

      We also asked organizations what motivated their push toward automation. The most common drivers are to improve efficiency, with almost seven out of ten organizations looking to increase staff on high-level tasks by automating repetitive tasks, 67% also wanting to increase productivity without increasing headcount, and 59% wanting to reduce errors being made by people. In addition, more than half of organizations pursued automation to improve customer satisfaction.

      What best describes your main motivation to pursue automation, above other considerations?

      A bar graph is depicted showing the following dataset: Increase staff focus on high-level tasks by automating repetitive tasks:	69%; Increase productivity of existing staff to avoid increasing headcount:	67%; Reduce errors made by people:	59%; Improve customer satisfaction:	52%; Achieve cost savings through reduction in headcount:	35%; Increase revenue by enabling higher volume of work:	30%

      Tech Trends 2023 Survey

      To what extent did your organization shift its processes from being manually completed to digitally completed during past year?

      A bar graph is depicted showing the extent to which organizations shifted processes from manual to digital during the past year for 2022 and 2023, from Tech Trends 2023 Survey

      With the shift in focus from implementing new applications to support digital transformation to operating in the new environment, IT must shift its own focus to help realize the value from these systems. At the same time, IT must reorganize itself around the new value chain that's defined by a customer perspective.

      IT struggles to deliver business value or support innovation

      Many current IT departments are structured around legacy processes that hinder their ability to deliver business value. CIOs are trying to grapple with the misalignment between the modern business structure and keep up with the demands for innovation and agility.

      Almost nine in ten CIOs say that business frustration with IT's failure to deliver value is a pain point. Their supervisors have a slightly more favorable opinion, with 76% agreeing that it is a pain point.

      Similarly, nine in ten CIOs say that IT limits affecting business innovation and agility is a pain point, while 81% of their supervisors say the same.

      Supervisors say that IT should "ensure benefits delivery" as the most important process (CEO-CIO Alignment Program). This underlines the need to achieve alignment, optimize service delivery, and facilitate innovation. The pain points identified here will need to be resolved to make this possible.

      IT departments will need to contend with a tight labor market and economic volatility in the year ahead. If this drives down resource capacity, it will be even more critical to tightly align with the organization.

      Views business frustration with IT failure to deliver value as a pain point

      CXO 76%
      CIO 88%

      Views IT limits affecting business innovation and agility as a pain point

      CXO 81%
      CIO

      90%

      CEO-CIO Alignment Program

      Opportunities

      Define IT's value by its contributions to enterprise value

      Communicate the performance of IT to stakeholders by attributing positive changes in enterprise value to IT initiatives. For example, if a digital channel helped increase sales in one area, then IT can claim some portion of that revenue. If optimization of another process resulted in cost savings, then IT can claim that as a contribution toward the bottom line. CIOs should develop their handle on how KPIs influence revenues and costs. Keeping tabs on normalized year-over-year revenue comparisons can help demonstrate that IT contributions are making an impact on driving profitability.

      Go with buy versus build if it's a commodity service

      Most back-office functions common to operating a company can be provided by cloud-based applications accessed through a web browser. There's no value in having IT spend time maintaining on-premises applications that require hosting and ongoing maintenance. Organizations that are still accruing technical debt and are unable to modernize will increasingly find it is negatively impacting employee experience, as users expect their working experience to be similar to their experience with consumer applications. In addition, IT will continue to have capacity challenges as resources will be consumed by maintenance. As they seek to outsource some applications, IT will need to consider the geopolitical risk of certain jurisdictions in selecting a provider.

      Redefine how employee performance is tracked

      The concept of "clocking in" for a shift and spending eight hours a day on the job doesn't help guide IT toward its objectives or create any higher sense of purpose. Leaders must work to create a true sense of accountability by reaching consensus on what key performance indicators are important and tasking staff to improve them. Metrics should clearly link back to business outcomes and IT should understand the role they play in delivering a good customer experience.

      Risks

      Lack of talent available to drive transformation

      CIOs are finding it difficult to hire the talent needed to create the capacity they need as digital demands of their organizations increase. This could slow the pace of change as new positions created in IT go unfilled. CIOs may need to consider reskilling and rebalancing workloads of existing staff in the short term and tap outsourcing providers to help make up shortfalls.

      Resistance to change

      New processes may have been given the official rubber stamp, but that doesn't mean staff are adhering to them. Organizations that reorganize themselves must take steps to audit their processes to ensure they're executed the way they intend. Some employees may feel they are being made obsolete or pushed out of their jobs and become disengaged.

      Short-term increased costs

      Restructuring the organization can come with the need for new tools and more training. It may be necessary to operate with redundant staff for the transitional period. Some additional expenses might be incurred for a brief period as the new structure is being put in place.

      Emphasize the value of IT in driving revenue

      Salman Ali, CIO, McDonald's Germany

      As the new CIO to McDonald's Germany, Salman Ali came on board with an early mandate to reorganize the IT department. The challenge is to merge two organizations together: one that delivers core technology services of infrastructure, security, service desk, and compliance and one that delivers customer-facing technology such as in-store touchscreen kiosks and the mobile app for food delivery. He is looking to organize this new-look department around the technology in the hands of both McDonald's staff and its customers. In conversations with his stakeholders, Ali emphasizes the value that IT is driving rather than discussing the costs that go into it. For example, there was a huge cost in integrating third-party meal delivery apps into the point-of-sales system, but the seamless experience it delivers to customers looking to place an order helps to drive a large volume of sales. He plans to reorganize his department around this value-driven approach. The organization model will be executed with clear accountability in place and key performance indicators to measure success.

      "Technology is no longer just an enabler. It's now a strategic business function. When they talk about digital, they are really talking about what's in the customers' hands and what do they use to interact with the business directly? Digital transformation has given technology a new front seat that's really driving the business."

      CASE STUDY
      Overhauling the "heartbeat" of the organization

      Ernest Solomon, Former CIO, LAWPRO

      LAWPRO is a provider of professional liability insurance and title insurance in Canada. The firm is moving its back-office applications from a build approach to a buy approach and focusing its build efforts on customer-facing systems tied to revenue generation. CIO Ernest Solomon says his team has been developing on a legacy platform for two decades, but it's time to modernize. The firm is replacing its legacy platform and moving to a cloud-based system to address technical debt and improve the experience for staff and customers. The claims and policy management platform, the "heartbeat" of the organization, is moving to a software-as-a-service model. At the same time, the firm's customer-facing Title Plus application is being moved to a cloud-native, serverless architecture. Solomon doesn't see the need for IT to spend time building services for the back office, as that doesn't align with the mission of the organization. Instead, he focuses his build efforts on creating a competitive advantage.

      "We're redefining the customer experience, which is how do we move the needle in a positive direction for all the lawyers that interact with us? How do we generate that value-based proposition and improve their interactions with our organization?"

      From priorities to action

      Go deeper on pursuing your priorities by improving the associated capabilities.

      Improve Enterprise Application Selection & Implementation

      Help leaders manage their teams effectively in a hybrid environment by providing them with the right tools and tactics to manage the challenges of hybrid work. Focus on promoting teamwork and fostering connection.

      Embrace Business-Managed Applications

      Improve Performance Measurement

      Drive the most important IT process in the eyes of supervisors by defining business value and linking IT spend to it. Make benefits realization part of your IT governance.

      Maximize Business Value From IT Through Benefits Realization

      Improve IT Organizational Design

      Showcase IT's value to the business by aligning IT spending and staffing to business functions. Provide transparency into business consumption of IT and compare your spending to your peers'.

      IT Spend & Staffing Benchmarking

      The Five Priorities

      Engage cross-functional leadership to seize opportunity while protecting the organization from volatility.

      1. Adjust IT operations to manage for inflation
      2. Prepare your data pipeline to train AI
      3. Go all in on zero-trust security
      4. Engage employees in the digital age
      5. Shape the IT organization to improve customer experience

      Expert Contributors

      In order of appearance

      Denise Cornish, Associate VP of IT and Deputy COO, Western University of Health Sciences

      Jim Love, CIO, IT World Canada

      Christian Magsisi, Vice President of Venue and Digital Technology, MLSE

      Humza Teherany, Chief Technology Officer, MLSE

      Serge Suponitskiy, CIO, Brosnan Risk Consultants

      David Senf, National Cybersecurity Strategist, Bell

      Roberto Eberhardt, CIO, Ontario Legislative Assembly

      Mike Russell, Virginia Community College System

      Salman Ali, CIO, McDonald's Germany

      Ernest Solomon, Former CIO, LAWPRO

      Bibliography

      Anderson, Brad, and Seth Patton. "In a Hybrid World, Your Tech Defines Employee Experience." Harvard Business Review, 18 Feb. 2022. Accessed 12 Dec. 2022.
      "Artificial Intelligence Is Permeating Business at Last." The Economist, 6 Dec. 2022. Accessed 12 Dec. 2022.
      Badlani, Danesh Kumar, and Adrian Diglio. "Microsoft Open Sources Its Software Bill
      of Materials (SBOM) Generation Tool." Engineering@Microsoft, 12 July 2022. Accessed
      12 Dec. 2022.
      Birch, Martin. "Council Post: Equipping Employees To Succeed In Digital Transformation." Forbes, 9 Aug. 2022. Accessed 7 Dec. 2022.
      Bishop, Katie. "Is Remote Work Worse for Wellbeing than People Think?" BBC News,
      17 June 2022. Accessed 7 Dec. 2022.
      Carlson, Brian. "Top 5 Priorities, Challenges For CIOs To Recession-Proof Their Business." The Customer Data Platform Resource, 19 July 2022. Accessed 7 Dec. 2022.
      "CIO Priorities: 2020 vs 2023." IT PRO, 23 Sept. 2022. Accessed 2 Nov. 2022.
      cyberinsiders. "Frictionless Zero Trust Security - How Minimizing Friction Can Lower Risks and Boost ROI." Cybersecurity Insiders, 9 Sept. 2021. Accessed 7 Dec. 2022.
      Garg, Sampak P. "Top 5 Regulatory Reasons for Implementing Zero Trust."
      CSO Online, 27 Oct. 2022. Accessed 7 Dec. 2022.
      Heikkilä, Melissa. "The Viral AI Avatar App Lensa Undressed Me—without My Consent." MIT Technology Review, 12 Dec. 2022. Accessed 12 Dec. 2022.
      Jackson, Brian. "How the Toronto Raptors Operate as the NBA's Most Data-Driven Team." Spiceworks, 1 Dec. 2022. Accessed 12 Dec. 2022.
      Kiss, Michelle. "How the Digital Age Has Transformed Employee Engagement." Spiceworks,16 Dec. 2021. Accessed 7 Dec. 2022.
      Matthews, David. "EU Hopes to Build Aligned Guidelines on Artificial Intelligence with US." Science|Business, 22 Nov. 2022. Accessed 12 Dec. 2022.
      Maxim, Merritt. "New Security & Risk Planning Guide Helps CISOs Set 2023 Priorities." Forrester, 23 Aug. 2022. Accessed 7 Dec. 2022.
      Miller, Michael J. "Gartner Surveys Show Changing CEO and Board Concerns Are Driving a Different CIO Agenda for 2023." PCMag, 20 Oct. 2022. Accessed 2 Nov. 2022.
      MIT Lincoln Laboratory. "Overview of Zero Trust Architectures." YouTube,
      2 March 2022. Accessed 7 Dec. 2022.
      MIT Technology Review Insights. "CIO Vision 2025: Bridging the Gap between BI and AI." MIT Technology Review, 20 Sept. 2022. Accessed 1 Nov. 2022.
      Paramita, Ghosh. "Data Architecture Trends in 2022." DATAVERSITY, 22 Feb. 2022. Accessed 7 Dec. 2022.
      Rosenbush, Steven. "Cybersecurity Tops the CIO Agenda as Threats Continue to Escalate - WSJ." The Wall Street Journal, 17 Oct. 2022. Accessed 2 Nov. 2022.
      Sacolick, Isaac. "What's in the Budget? 7 Investments for CIOs to Prioritize." StarCIO,
      22 Aug. 2022. Accessed 2 Nov. 2022.
      Singh, Yuvika. "Digital Culture-A Hurdle or A Catalyst in Employee Engagement." International Journal of Management Studies, vol. 6, Jan. 2019, pp. 54–60. ResearchGate, https://doi.org/10.18843/ijms/v6i1(8)/08.
      "Talent War Set to Become Top Priority for CIOs in 2023, Study Reveals." CEO.digital,
      8 Sept. 2022. Accessed 7 Dec. 2022.
      Tanaka, Rodney. "WesternU COMP and COMP-Northwest Named Apple Distinguished School." WesternU News. 10 Feb. 2022. Accessed 12 Dec. 2022.
      Wadhwani, Sumeet. "Meta's New Large Language Model Galactica Pulled Down Three Days After Launch." Spiceworks, 22 Nov. 2022. Accessed 12 Dec. 2022.
      "World Economic Outlook." International Monetary Fund (IMF), 11 Oct. 2022. Accessed
      14 Dec. 2022.

      Adapt Your Onboarding Process to a Virtual Environment

      • Buy Link or Shortcode: {j2store}577|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: Attract & Select
      • Parent Category Link: /attract-and-select
      • For many, the WFH arrangement will be temporary, however, the uncertainty around the length of the pandemic makes it hard for organizations to plan long term.
      • As onboarding plans traditionally carry a six- to twelve-month outlook, the uncertainty around how long employees will be working remotely makes it challenging to determine how much of the current onboarding program needs to change. In addition, introducing new technologies to a remote workforce and planning training on how to access and effectively use these technologies is difficult.

      Our Advice

      Critical Insight

      • The COVID-19 pandemic has led to a virtual environment many organizations were not prepared for.
      • Focusing on critical parts of the onboarding process and leveraging current technology allows organizations to quickly adapt to the uncertainty and constant change.

      Impact and Result

      • Organizations need to assess their existing onboarding process and identify the parts that are critical.
      • Using the technology currently available, organizations must adapt onboarding to a virtual environment.
      • Develop a plan to re-assess and update the onboarding program according to the duration of the situation.

      Adapt Your Onboarding Process to a Virtual Environment Research & Tools

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

      1. Assess current onboarding processes

      Map the current onboarding process and identify the challenges to a virtual approach.

      • Adapt Your Onboarding Process to a Virtual Environment Storyboard
      • Virtual Onboarding Workbook
      • Process Mapping Guide

      2. Modify onboarding activities

      Determine how existing onboarding activities can be modified for a virtual environment.

      • Virtual Onboarding Ideas Catalog
      • Performance Management for Emergency Work-From-Home

      3. Launch the virtual onboarding process and plan to re-assess

      Finalize the virtual onboarding process and create an action plan. Continue to re-assess and iterate over time.

      • Virtual Onboarding Guide for HR
      • Virtual Onboarding Guide for Managers
      • HR Action and Communication Plan
      • Virtual Onboarding Schedule
      [infographic]