Industry-Specific Digital Transformation
- Parent Category Name: Innovation
- Parent Category Link: /innovation
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Evaluate the infrastructure requirements and the ability to undergo modernization from legacy technology.
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.
Draft an RFP for a UC solution and gain project approval using Info-Tech’s executive presentation deck.
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.
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.
IT skills & process understanding.
Documentation reflecting communications infrastructure.
Reviewed network readiness.
Completed current state analysis.
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.
Clearly documented understanding of available skills
Documented process maps
Complete list of relevant communications and collaboration technologies
Completed readiness checklist
Hold focus group meeting.
Define business needs and goals.
Define solution options.
Evaluate options.
Discuss business value and readiness for each option.
Completed value and readiness assessment.
Current targets for service and deployment models.
2.1 Conduct internal focus group.
2.2 Align business needs and goals.
2.3 Evaluate deployment options.
Understanding of user needs, wants, and satisfaction with current solution
Assessment of business needs and goals
Understanding of potential future-state solution options
Identify gaps.
Examine and evaluate ways to remedy gaps.
Determine specific business requirements and introduce draft of business requirements document.
Completed description of future state.
Identification of gaps.
Identification of key business requirements.
3.1 Identify gaps and brainstorm gap remedies.
3.2 Complete business requirements document.
Well-defined gaps and remedies
List of specific business requirements
Introduce Unified Communications Solution RFP Template.
Develop statement of work (SOW).
Document technical requirements.
Complete cost-benefit analysis.
Unified Communications RFP.
Documented technical requirements.
4.1 Draft RFP (SOW, tech requirements, etc.).
4.2 Conduct cost-benefit analysis.
Ready to release RFP
Completed cost-benefit analysis
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Use Info-Tech’s licensing best practices to avoid overspending on Adobe licensing and to remain compliant in case of audit.
"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
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.
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.
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).
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.
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.
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
☑ 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.
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.
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
Establish Licensing Requirements |
Evaluate Licensing Options |
Evaluate Agreement Options |
Purchase and Manage Licenses |
|
|---|---|---|---|---|
Best-Practice Toolkit |
|
|
|
|
Guided Implementations |
|
|
|
|
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:
Then complete these activities…
With these tools & templates: Adobe ETLA Deployment Forecast |
Step 1.2: Determine Licensing Options Review findings with analyst:
Then complete these activities…
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:
Then complete these activities…
With these tools & templates: Adobe ETLA Deployment Forecast |
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.
Adobe has been systematically reducing discounts on ETLAs as they enter the second renewal cycle of the original three-year terms.
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.
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 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.
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 ETLA vs. VIP Pricing Table tool to compare ETLA costs against VIP costs.
Use Info-Tech’s ETLA Forecasted Costs and Benefits tool to forecast your ETLA costs and document benefits.
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:
Adobe Digital Publishing Suite, Single Edition
Bundle Name |
Target Customer |
Included Applications |
Features |
|---|---|---|---|
CC (for Individuals) |
Individual users |
The individual chooses |
|
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
|
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
|
For further information on specific functionality differences, reference Adobe’s comparison table.
☑ 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.
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.
Download Info-Tech’s Adobe ETLA Deployment Forecast tool to track Adobe installs within your environment and to determine usage needs.
Most common purchasing models |
Points for consideration |
|---|---|
|
|
"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
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.
Source: “Adobe Buying Programs Comparison Guide for Commercial and Government Organizations”
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.
Source: “Adobe Buying Programs Comparison Guide for Commercial and Government Organizations”
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
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.
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 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.
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.
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.
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 |
Adobe operates in its own niche in the creative space, and Adobe users have grown accustomed to their products, making switching very difficult.
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.
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.
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
“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.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Info-Tech's expert analyst guidance will help you save money, align stakeholders, and speed up the application selection process.
Info-Tech's workshop will help you implement a repeatable, data-driven approach that accelerates software selection efforts.
Perform an insurance policy comparison with scores based on policy coverage and exclusions.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Use this blueprint to score your potential cyber insurance policies and develop skills to overcome common insurance pitfalls.
Use these tools to gather cyber insurance requirements, prepare for the underwriting process, and compare policies.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Understand the stakeholder priorities driving changes in your application maintenance practice.
Identify the appropriate level of governance and enforcement to ensure accountability and quality standards are upheld across maintenance practices.
Build a maintenance triage and prioritization scheme that accommodates business and IT risks and urgencies.
Define and enforce quality standards in maintenance activities and build a high degree of transparency to readily address delivery challenges.
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.
Understand the business and IT stakeholder priorities driving the success of your application maintenance practice.
Understand any current issues that are affecting your maintenance practice.
Awareness of business and IT priorities.
An understanding of the maturity of your maintenance practices and identification of issues to alleviate.
1.1 Define priorities for enhanced maintenance practices.
1.2 Conduct a current state assessment of your application maintenance practices.
List of business and technical priorities
List of the root-cause issues, constraints, and opportunities of current maintenance practice
Define the processes, roles, and points of communication across all maintenance activities.
An in-depth understanding of all maintenance activities and what they require to function effectively.
2.1 Modify your maintenance process.
2.2 Define your maintenance roles and responsibilities.
Application maintenance process flow
List of metrics to gauge success
Maintenance roles and responsibilities
Maintenance communication flow
Understand in greater detail the process and people involved in receiving and triaging a request.
Define your criteria for value, impact, and urgency, and understand how these fit into a prioritization scheme.
Understand backlog management and release planning tactics to accommodate maintenance.
An understanding of the stakeholders needed to assess and approve requests.
The criteria used to build a tailored prioritization scheme.
Tactics for efficient use of resources and ideal timing of the delivery of changes.
A process that ensures maintenance teams are always working on tasks that are valuable to the business.
3.1 Review your maintenance intake process.
3.2 Define a request prioritization scheme.
3.3 Create a set of practices to manage your backlog and release plans.
Understanding of the maintenance request intake process
Approach to assess the impact, urgency, and severity of requests for prioritization
List of backlog management grooming and release planning practices
Understand how to apply development best practices and quality standards to application maintenance.
Learn the methods for monitoring and visualizing maintenance work.
An understanding of quality standards and the scenarios for where they apply.
The tactics to monitor and visualize maintenance work.
Streamlined maintenance delivery process with best practices.
4.1 Define approach to monitor maintenance work.
4.2 Define application quality attributes.
4.3 Discuss best practices to enhance maintenance development and deployment.
Taskboard structure and rules
Definition of application quality attributes with user scenarios
List of best practices to streamline maintenance development and deployment
Create a target state built from appropriate metrics and attainable goals.
Consider the required items and steps for the implementation of your optimization initiatives.
A realistic target state for your optimized application maintenance practice.
A well-defined and structured roadmap for the implementation of your optimization initiatives.
5.1 Refine your target state maintenance practices.
5.2 Develop a roadmap to achieve your target state.
Finalized application maintenance process document
Roadmap of initiatives to achieve your target state
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Analyze your project history to identify and fill gaps in your estimation practices.
Allocate time across project phases to validate and refine estimates and estimate assumptions.
Implement a lessons learned process to provide transparency to your sponsors and confidence to your teams.
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.
Track key performance indicators on past projects to inform goals for future projects.
Developed Project History List.
Refined starting estimates that can be adjusted accurately from project to project.
1.1 Build project history.
1.2 Analyze estimation capabilities.
1.3 Identify estimation goals.
Project History List
T-Shirt Sizing Health Check
Estimate Tracking Plan
Outline the common attributes required to complete projects.
Identify the commonly forgotten attributes to ensure comprehensive scoping early on.
Refined initial estimate based on high-level insights into work required and resources available.
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.
Identified list or store of past project attributes and costs
Attribute List and Estimated Cost
Required Skills List
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.
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.
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.
Project Lessons Learned Template
Historic Risks and Lessons Learned Master Template
Contingency Reserve and Risk Registers
Bridge the gap between death march projects and bloated and uncertain estimates by communicating expectations and assumptions clearly to your sponsors.
Clear estimation criteria and assumptions aligned with business priorities.
Post-mortem discussion items crucial to improving project history knowledge for next time.
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.
Estimation Quotation
Risk Priority Rankings
Hand-Off Procedures
Post-mortem agenda planning
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Understand the current mobile ecosystem. Use this toolkit to help you initiate a mobile development program.
Review and evaluate your current application development process.
Prioritize your mobile program based on your organization’s prioritization profile.
Summarize the execution of the mobile 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.
Understand the alignment of stakeholder objectives and priorities to mobile dev IT drivers.
Assess readiness of your organization for mobile dev.
Understand how to build your ideal mobile dev process.
Identify and address the gaps in your existing app dev process.
Build your future mobile dev state.
1.1 Getting started
1.2 Assess your current state
1.3 Establish your future state
List of key stakeholders
Stakeholder and IT driver mapping and assessment of current app dev process
List of practices to accommodate mobile dev
Assess the impact of mobile dev on your existing app dev process.
Prioritize your mobile program.
Understand the dev practice metrics to gauge success.
Properly prepare for the execution of your mobile program.
Calculate the ROI of your mobile program.
Prioritize your mobile program with dependencies in mind.
Build a communication plan with stakeholders.
2.1 Conduct an impact analysis
2.2 Prepare to execute
2.3 Communicate with stakeholders
Impact analysis of your mobile program and expected ROI
Mobile program order of execution and project dependencies mapping
List of dev practice metrics
While most CIOs understand the importance of using metrics to measure IT’s accomplishments, needs, and progress, when it comes to creating dashboards to communicate these metrics, they:
While most CIOs understand the importance of using metrics to measure IT’s accomplishments, needs, and progress, when it comes to creating dashboards to communicate these metrics, they:
Use Info-Tech’s ready-made dashboards for executives to ensure you:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
This blueprint guides you through reviewing Info-Tech’s IT dashboards for your audience and organization, then walks you through practical exercises to customize the dashboards to your audience and organization. The blueprint also gives practical guidance for delivering your dashboards and actioning your metrics.
IT dashboards with visuals and metrics that are aligned and organized by CIO priority and that allow you to customize with your own data, eliminating 80% of the dashboard design work.
The IT Dashboard Workbook accompanies the Establish High Value IT Metrics and Dashboards blueprint and guides you through customizing the Info-Tech IT Dashboards to your audience, crafting your messages, delivering your dashboards to your audience, actioning metrics results, and addressing audience feedback.
Reference the IT Metrics Library for ideas on metrics to use and how to measure them.
Reference the HR Metrics Library for ideas on metrics to use and how to measure them.
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.
Introduce the Info-Tech IT Dashboards to give the participants an idea of how they can be used in their organization.
Understand the importance of starting with the audience and understanding audience needs before thinking about data and metrics.
Explain how audience needs translate into metrics.
Understanding of where to begin when it comes to considering dashboards and metrics (the audience).
Identified audience and needs and derived metrics from those identified needs.
1.1 Review the info-Tech IT Dashboards and document impressions for your organization.
1.2 Identify your audience and their attributes.
1.3 Identify timeline and deadlines for dashboards.
1.4 Identify and prioritize audience needs and desired outcomes.
1.5 Associate metrics to each need.
1.6 Identify a dashboard for each metric.
Initial impressions of Info-Tech IT Dashboards.
Completed Tabs 2 and 3 of the IT Dashboard Workbook.
Provide guidance on how to derive metrics and assess data.
Understand the importance of considering how you will measure each metric and get the data.
Understand that measuring data can be costly and that sometimes you just can’t afford to get the measure or you can’t get the data period because the data isn’t there.
Understand how to assess data quality and readiness.
2.1 Complete a data inventory for each metric on each dashboard: determine how you will measure the metric, the KPI, any observation biases, the location of the data, the type of source, the owner, and the security/compliance requirements.
2.2 Assess data quality for availability, accuracy, and standardization.
2.3 Assess data readiness and the frequency of measurement and reporting.
Completed Tab 4 of the IT Dashboard Workbook.
Guide participants in customizing the Info-Tech IT Dashboards with the data identified in previous steps.
This step may vary as some participants may not need to alter the Info-Tech IT Dashboards other than to add their own data.
Understanding of how to customize the dashboards to the participants’ organization.
3.1 Revisit the Info-Tech IT Dashboards and use the identified metrics to determine what should change in them.
3.2 Build your dashboards by editing the Info-Tech IT Dashboards with your changes as planned in Step 3.1.
Assessed Info-Tech IT Dashboards for your audience’s needs.
Completed Tab 5 of the IT Dashboard Workbook.
Finalized dashboards.
Guide participants in learning how to create a story around the dashboards.
Guide participants in planning to action metrics and where to record results.
Guide participants in how to address results of metrics and feedback from audience about dashboards.
Participants understand how to speak to their dashboards.
Participants understand how to action metrics results and feedback about dashboards.
4.1 Craft your story.
4.2 Practice delivering your story.
4.3 Plan to action your metrics.
4.4 Understand how to record and address your results.
Completed Tabs 6 and 7 of the IT Dashboard Workbook.
Finalize work outstanding from previous steps and answer any questions.
Participants have thought about and documented how to customize the Info-Tech IT Dashboards to use in their organization, and they have everything they need to customize the dashboards with their own metrics and visuals (if necessary).
5.1 Complete in-progress deliverables from previous four days.
5.2 Set up review time for workshop deliverables and to discuss next steps.
Completed IT Dashboards tailored to your organization.
Completed IT Dashboard Workbook
CIOs naturally gravitate toward data and data analysis. This is their strength. They lean into this strength, using data to drive decisions, track performance, and set targets because they know good data drives good decisions.
However, when it comes to interpreting and communicating this complex information to executives who may be less familiar with data, CIOs struggle, often falling back on showing IT activity level data instead of what the executives care about. This results in missed opportunities to tell IT’s unique story, secure funding, reveal important trends, or highlight key opportunities for the organization.
Break through these traditional barriers by using Info-Tech’s ready-made IT dashboards. Spend less time agonizing over visuals and layout and more time concentrating on delivering IT information that moves the organization forward.

Diana MacPherson
Senior Research Analyst, CIO
Info-Tech Research Group
Your ChallengeWhile most CIOs understand the importance of using metrics to measure IT’s accomplishments, needs, and progress, when it comes to creating dashboards to communicate these metrics, they:
|
Common ObstaclesCIOs often experience these challenges because they:
|
Info-Tech’s ApproachUse Info-Tech’s ready-made dashboards for executives to ensure you:
|
The purpose of a dashboard is to drive decision making. A well designed dashboard presents relevant, clear, concise insights that help executives make data-driven decisions.
CIOs struggle to select the right metrics and dashboards to communicate IT’s accomplishments, needs, and progress to their executives. CIOs:
The bottom line: CIOs often communicate to the wrong audience, about the wrong things, in the wrong amount, using the wrong metrics, at the wrong time.
In a survey of 500 executives, organizations that struggled with dashboards identified the reasons as:
61% Inadequate context
54% Information overload
— Source: Exasol
When asked which performance indicators should be implemented in your business, CXOs and CIOs both agree that IT needs to improve its metrics across several activity areas: technology performance, cost and salary, and risk.
The Info-Tech IT Dashboards center key metrics around these activities ensuring you align your metrics to the needs of your CXO audience.
Info-Tech CEO/CIO Alignment Survey Benchmark Report n=666
The top six areas that a CIO needs to prioritize and measure outcomes, no matter your organization or industry, are:
Executives recognize the benefits of dashboards:
87% of respondents to an Exasol study agreed that their organization’s leadership team would make more data-driven decisions if insights were presented in a simpler and more understandable way
(Source: Exasol)
We created dashboards for you so you don’t have to!
Phase Steps
Phase Outcomes
Phase Steps
Phase Outcomes
Phase Steps
Phase Outcomes
Phase Steps
Phase Outcomes
Phase Steps
Phase Outcomes
Choose the path that works for you
The Info-Tech IT Dashboards address several needs:
The need for easy-to-consume data is on the rise making dashboards a vital data communication tool.
70%: Of employees will be expected to use data heavily by 2025, an increase from 40% in 2018.
— Source: Tableau
A dashboard’s primary purpose is to drive action. It may also serve secondary purposes to update, educate, and communicate, but if a dashboard does not drive action, it is not serving its purpose.
Start with the audience. Resist the urge to start with the data. Think about who your audience is, what internal and external environmental factors influence them, what problems they need to solve, what goals they need to achieve, then tailor the metrics and dashboards to suit.
Avoid showing IT activity-level metrics. Instead use CIO priority-based metrics to report on what matters to the organization. The Info-Tech IT Dashboards are organized by the CIO priorities: risks, financials, talent, and strategic initiatives.
Dashboards show the what not the why. Do not assume your audience will draw the same conclusions from your graphs and charts as you do. Provide the why by interpreting the results, adding insights and calls to action, and marking key areas for discussion.
A dashboard is a communication tool and should reflect the characteristics of good communication. Be clear, concise, consistent, and relevant.
Action your data. Act and report progress on your metrics. Gathering metrics has a cost, so if you do not plan to action a metric, do not measure it.
Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:
|
|
Key deliverable: DashboardsReady-made risk, financials, talent, and strategic initiatives dashboards that organize your data in a visually appealing way so you can concentrate on the metrics and communication. |
|
|
IT Dashboard WorkbookThe IT Dashboard Workbook keeps all your metrics, data, and dashboard work in one handy file! |
|
|
IT Dashboard GuideThe IT Dashboard Guide provides the Info-Tech IT Dashboards and information about how to use them. |
CIO Benefits
Business Benefits
Realize measurable benefits after using Info-Tech’s approach:
Determining what you should measure, what visuals you should use, and how you should organize your visuals, is time consuming. Calculate the time it has taken you to research what metrics you should show, create the visuals, figure out how to categorize the visuals, and layout your visuals. Typically, this takes about 480 hours of time. Use the ready-made Info-Tech IT Dashboards and the IT Dashboard Workbook to quickly put together a set of dashboards to present your CXO. Using these tools will save approximately 480 hours.
A study at the University of Minnesota shows that visual presentations are 43% more effective at persuading their audiences (Bonsignore). Estimate how persuasive you are now by averaging how often you have convinced your audience to take a specific course of action. After using the Info-Tech IT Dashboards and visual story telling techniques described in this blueprint, average again. You should be 43% more persuasive.
Further value comes from making decisions faster. Baseline how long it takes, on average, for your executive team to make a decision before using Info-Tech’s IT Dashboards then time how long decisions take when you use your Info-Tech’s IT Dashboards. Your audience should reach decisions 21% faster according to studies at Stanford University and the Wharton School if business (Bonsignore).
ChallengeYear after year, the CIO of a construction company attended business planning with the Board to secure funding for the year. One year, the CEO interrupted and said, “You're asking me for £17 million. You asked me for £14 million last year and you asked me for £12 million the year before that. I don't quite understand what we get for our money.” The CEO could not understand how fixing laptops would cost £17 million and for years no one had been able to justify the IT spend. |
SolutionsThe CIO worked with his team to produce a simple one-page bubble diagram representing each IT department. Each bubble included the total costs to deliver the service, along with the number of employees. The larger the bubble, the higher the cost. The CIO brought each bubble to life as he explained to the Board what each department did. The Board saw, for example, that IT had architects who thought about the design of a service, where it was going, the life cycle of that service, and the new products that were coming out. They understood what those services cost and knew how many architects IT had to provide for those services. |
RecommendationsThe CEO remarked that he finally understood why the CIO needed £17 million. He even saw that the costs for some IT departments were low for the amount of people and offered to pay IT staff more (something the CIO had requested for years). Each year the CIO used the same slide to justify IT costs and when the CIO needed further investment for things like security or new products, an upgrade, or end of life support, the sign-offs came very quickly because the Board understood what IT was doing and that IT wasn't a bottomless pit. |
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."
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.
Activities
1.1 Review the info-Tech IT Dashboards and document impressions for your organization.
1.2 Identify your audience’s attributes.
1.3 Identify timeline and deadlines for dashboards.
1.4 Identify and prioritize audience needs and desired outcomes.
1.5 Associate metrics to each need.
1.6 Identify a dashboard for each metric.
Deliverables
1. Initial impressions of Info-Tech IT Dashboards.
2. Completed Tabs 2 and 3 of the IT Dashboard Workbook.
Activities
2.1 Complete a data inventory for each metric on each dashboard: determine how you will measure the metric, the KPI, any observation biases, the location of the data, the type of source, and the owner and security/compliance requirements.
2.2 Assess data quality for availability, accuracy, and standardization.
2.3 Assess data readiness and frequency of measurement and reporting.
Deliverables
1. Completed Tab 4 of the IT Dashboard Workbook.
Activities
3.1 Revisit the Info-Tech IT Dashboards and use the identified metrics to determine what should change on the dashboards.
3.2 Build your dashboards by editing the Info-Tech IT Dashboards with your changes as planned in Step 3.1.
Deliverables
1. Assessed Info-Tech IT Dashboards for your audience’s needs.
2. Completed Tab 5 of the IT Dashboard Workbook.
3. Finalized dashboards.
Activities
4.1 Craft your story.
4.2 Practice delivering your story.
4.3 Plan to action your metrics.
4.4 Understand how to record and address your results.
Deliverables
1. Completed Tabs 6 and 7 of the IT Dashboard Workbook.
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.
Deliverables
1. Completed IT Dashboards tailored to your organization.
2. Completed IT Dashboard Workbook.
workshops@infotech.com
1-888-670-8889

An IT dashboard is…
a visual representation of data, and its main purpose is to drive actions. Well-designed dashboards use an easy to consume presentation style free of clutter. They present their audience with a curated set of visuals that present meaningful metrics to their audience.
Dashboards can be both automatically or manually updated and can show information that is dynamic or a snapshot in time.
Use the link below to download the Info-Tech IT Dashboards and consider the following:
Download the Info-Tech IT Dashboards
Cognitively
Emotionally
Visual clues
Persuasion
— Source: (Vogel et al.)
This phase will walk you through the following:
This phase involves the following participants:
We created a compelling way to organize IT dashboards so you don’t have to. The Info-Tech IT Dashboards are organized by CIO Priorities, and these are consistent irrespective of industry or organization. This is a constant that you can organize your metrics around.
The categories represent a constant around which you can change the order; for example, if your CXO is more focused on Financials, you can switch the Financials dashboard to appear first.
The Info-Tech IT Dashboards are aimed at a CXO audience so if your audience is the CXO, then you may decide to change very little, but you can customize any visual to appeal to your audience.
Phase 1 will get you started with your audience.
Reliable, accurate data plays a critical role in dashboards, but data is only worthwhile if it is relevant to the audience who consumes it, and dashboards are only as meaningful as the data and metrics they represent.
Instead of starting with the data, start with the audience. The more IT understands about the audience, the more relevant the metrics will be to their audience and the more aligned leadership will be with IT.
Don’t forget yourself and who you are. Your audience will have certain preconceived notions about who you are and what you do. Consider these when you think about what you want your audience to know.
|
46% executives identify lack of customization to individual user needs as a reason they struggle with dashboards. |
If you find yourself thinking about data and you haven’t thought about your audience, pull yourself back to the audience.
| Ask first | Ask later |
| Who is this dashboard for? | What data should I show? |
| How will the audience use the dashboard to make decisions? | Where do I get the data? |
| How can I show what matters to the audience? | How much effort is required to get the data? |
It is crucial to think about who your audience is so that you can translate their needs into metrics and create meaningful visuals for your dashboards.
Activities:
1.1.1 Examine Info-Tech’s IT Dashboards.
This phase involves the following participants:
Outcomes of this step:
Download Info-Tech IT Dashboards
Jot down your thoughts below. You can refer to this later as you consider your audience.
Consider:
Activities:
1.2.1 Document your audience’s needs in the IT Dashboard Workbook.
This phase involves the following participants:
Outcomes of this step:
Validate the needs you’ve uncovered with the audience to ensure you have not misinterpreted them and clarify the desired timeline and deadline for the dashboard.
| Typical Audience | Needs |
| Senior Leadership |
|
| Board of Directors |
|
| Business Partners |
|
| CFO |
|
Select three to five of the highest priority needs for each audience to include on a dashboard.
Click the link below to download the IT Dashboard Workbook and open the file. Select Tab 2. The workbook contains pre-populated text that reflects information about Info-Tech’s IT Dashboards. You may want to keep the pre-populated text as reference as you identify your own audience then remove after you have completed your updates.
Download Info-Tech IT Dashboard Workbook
This phase will walk you through the following:
This phase involves the following participants:
When you present metrics that your audience cares about, you:
29% of respondents to The Economist Intelligence Unit survey cited inadequate collaboration between IT and the business as one of the top barriers to the organization’s digital objectives.
— Source: Watson, Morag W., et al.
The Info-Tech IT Dashboards use measures for each dashboard that correspond with what the audience (CXO) cares about. You can find these measures in the IT Dashboard Workbook. If your audience is the CXO, you may have to change a little but you should still validate the needs and metrics in the IT Dashboard Workbook.
Phase 2 covers the process of translating needs into metrics.
Activities:
2.1.1 Compare the Info-Tech IT Dashboards with your audience’s needs.
2.1.2 Document prioritized audience needs and the desired outcome of each in the IT Dashboard Workbook.
This phase involves the following participants:
Outcomes of this step:
Download Info-Tech IT Dashboard Workbook

The Info-Tech IT Dashboards contain a set of monthly metrics tailored toward a CXO audience.
Download Info-Tech IT Dashboards
Any changes to the Info-Tech IT Dashboards?
Consider:
When it’s not immediately apparent what the link between needs and metrics is, brainstorm desired outcomes.
Now that you’ve examined the Info-Tech IT Dashboards and considered the needs of your audience, it is time to understand the outcomes and goals of each need so that you can translate your audience’s needs into metrics.
Click the link below to download the IT Dashboard Workbook and open the file. Select Tab 3. The workbook contains pre-populated text that reflects information about Info-Tech’s IT Dashboards. You may want to keep the pre-populated text as reference as you identify your own audience then remove it after you have completed your updates.
Download Info-Tech IT Dashboard Workbook
Once you know the desired outcomes, you can identify meaningful metrics
Avoid the following oversights when selecting your metrics.
Activities:
2.2.1 Derive metrics using the Info-Tech IT Dashboards and the IT Dashboard Workbook.
This phase involves the following participants:
Outcomes of this step:
Now that you have completed the desired outcomes, you can determine if you are meeting those desired outcomes. If you struggle with the metrics, revisit the desired outcomes. It could be that they are not measurable or are not specific enough.
Click the link below to download the IT Dashboard Workbook and open the file. Select Tab 3. The workbook contains pre-populated text that reflects information about Info-Tech’s IT Dashboards. You may want to keep the pre-populated text as reference as you identify your own audience then remove it after you have completed your updates.
Download Info-Tech IT Dashboard Workbook
Download IT Metrics Library
Download HR Metrics Library
Activities:
2.3.1 Review the metrics and identify which dashboard they should appear on.
This phase involves the following participants:
Outcomes of this step:
Once you have identified all your metrics from Step 2.2, identify which dashboard they should appear on. As with all activities, if the Info-Tech IT Dashboard meets your audience’s needs, you do not have to edit this content and can instead use the pre-populated information.
This phase will walk you through the following:
This phase involves the following participants:
Once appropriate service metrics are derived from business objectives, the next step is to determine how easily you can get your metric.
40% of organizations say individuals within the business do not trust data insights.
— Source: Experian, 2020
Phase 3 covers the process of identifying data for each metric, creating a data inventory, assessing the readiness of your data, and documenting the frequency of measuring your data. Once complete, you will have a guide to help you add data to your dashboards.
Activities:
3.1.1 Download the IT Dashboard Workbook and complete the data inventory section on Tab 4.
This phase involves the following participants:
Outcomes of this step:
Click the link below to download the IT Dashboard Workbook and open the file. Select Tab 4. The pre-populated text is arranged into the tables according to the dashboard they appear on; you may need to scroll down to see all the dashboard tables.
Create a data inventory by placing each metric identified on Tab 3 into the corresponding dashboard table. Complete each column as described below.
Metrics Libraries: Use the IT Metrics Library and HR Metrics Library for ideas for metrics to use and how to measure them.
Download Info-Tech IT Dashboard Workbook
Activities:
3.2.1 Use the IT Dashboard Workbook to complete an assessment of data quality on Tab 4.
This phase involves the following participants:
Outcomes of this step:
Document the data quality on Tab 4 of the IT Dashboard Workbook by filling in the data availability, data accuracy, and data standardization columns as described below.
Data quality is a struggle for many organizations. Consider how much uncertainty you can tolerate and what would be required to improve your data quality to an acceptable level. Consider cost, technological resources, people resources, and time required.
Download Info-Tech IT Dashboard Workbook
Activities:
3.3.1 Use the IT Dashboard Workbook to determine the readiness of your data.
This phase involves the following participants:
Outcomes of this step:
Once the data quality has been documented and examined, complete the Data Readiness section of Tab 4 in the Info-Tech IT Dashboard Workbook. Select a readiness classification using the definitions below. Use the readiness of your data to determine the level of effort required to obtain the data and consider the constraints and cost/ROI to implement new technology or revise processes and data gathering to produce the data.
Remember: Although in most cases, simple formulas that can be easily understood are the best approach, both because effort is lower and data that is not manipulated is more trustworthy, do not abandon data because it is not perfect but instead plan to make it easier to obtain.
Download Info-Tech IT Dashboard Workbook
Activities:
3.4.1 Use the IT Dashboard Workbook to determine the readiness of your data and how frequently you will measure your data.
This phase involves the following participants:
Outcomes of this step:
Document the planned frequency of measurement for all your metrics on Tab 4 of the IT Dashboard Workbook.
For each metric, determine how often you will need to refresh it on the dashboard and select a frequency from the drop down. The Info-tech IT Dashboards assume a monthly refresh.
Download Info-Tech IT Dashboard Workbook
This phase will walk you through the following:
This phase involves the following participants:
Now that you have linked metrics to the needs of your audience and you understand how to get your data, it is time to start building your dashboards.
— Source: American Management Association
Phase 4 guides you through using the Info-Tech IT Dashboard visuals for your audience’s needs and your story.
Activities:
4.1.1 Plan and validate dashboard metrics, data, level of effort and visuals.
This phase involves the following participants:
Outcomes of this step:
Sample A:
Sample B:
Identify the purpose of the visualization. Determine which of the four categories below aligns with the story and choose the appropriate visual to display the data.

Scatterplots

Histogram

Scatterplot

Pie chart

Table

Bar graph

Line chart
(Calzon)
To compare categories, use a bar chart:
Conclusion: Visualizing the spend in various areas helps prioritize.
To show trends, use a line graph:
Conclusion: Overlaying a trend line on revenue per employee helps justify headcount costs.
To show simple results, text is sometimes more clear:
Conclusion: Text with meaningful graphics conveys messages quickly.
To display relative percentages of values, use a pie chart:
Conclusion: Displaying proportions in a pie chart gives an at-a-glance understanding of the amount any area uses.
Select colors that will enhance the story
Keep the design simple and clear
Example
Leverage this checklist to ensure you are creating the perfect visuals and graphs for your presentation.
Checklist:
Click the links below to download the Info-Tech IT Dashboards and the IT Dashboard Workbook. Open the IT Dashboard Workbook and select Tab 5. For each dashboard, represented by its own table, open the corresponding Info-Tech IT Dashboard as reference.
Download Info-Tech IT Dashboards
Download Info-Tech IT Dashboard Workbook
Activities:
4.2.1 Update the visuals on the Info-Tech IT Dashboards with data and visuals identified in the IT Dashboard Workbook.
This phase involves the following participants:
Outcomes of this step:
Do not worry about the Key Insights or Calls to Action; you will create this in the next step when you plan your story.
Download Info-Tech IT Dashboards
Activities:
4.3.1 Craft Your Story
4.3.2 Finalize Your Dashboards
4.3.3 Practice Delivering Your Story With Your Dashboards
This phase involves the following participants:
Outcomes of this step:
IT dashboards are valuable tools to provide insights that drive decision making.
“Data storytelling is a universal language that everyone can understand – from people in STEM to arts and psychology.” — Peter Jackson, Chief Data and Analytics Officer at Exasol
Storytelling provides context, helping the audience understand and connect with data and metrics.
— Exasol
For more visual guidance, download the IT Dashboard Guide
Time is a non-renewable resource. The message crafted must be considered a value-adding communication to your audience.
Be Consistent
Be Clear
Be Relevant
Be Concise
Click the link below to download the IT Dashboard Workbook and open the file. Select Tab 6. The workbook contains grey text that reflects a sample story about the Info-Tech IT Dashboards. You may want to keep the sample text as reference, then remove after you have entered your information.
Download Info-Tech IT Dashboard Workbook
Tip: Aim to be brief and concise with any text. Dashboards simplify information and too much text can clutter the visuals and obscure the message.
Download Info-Tech IT Dashboard Workbook
Ideally you can present your dashboard to your audience so that you are available to clarify questions and add a layer of interpretation that would crowd out boards if added as text.
Don’t overwhelm your audience with information and data. You spent time to craft your dashboards so that they are clear and concise, so spend time practicing delivering a message that matches your clear, concise dashboards
Download Info-Tech IT Dashboard Workbook
Think about the message you are trying to convey and how your body can support that delivery. Hands, stance, and frame all have an impact on what might be conveyed.
If you want your audience to lean in and be eager about your next point, consider using a pause or softer voice and volume.
State the main points of your dashboard confidently. While this should be obvious, it needs to be stated explicitly. Your audience should be able to clearly see that you believe the points you are stating.
Present in a way that is genuine to you and your voice. Whether you have an energetic personality or a calm and composed personality, the presentation should be authentic to you.
Look each member of the audience in the eye at least once during your presentation or if you are presenting remotely, look into the camera. Avoid looking at the ceiling, the back wall, or the floor. Your audience should feel engaged – this is essential to keeping their attention.
Avoid reading the text from your dashboard, and instead paraphrase it while maintaining eye/camera contact.
You are responsible for the response of your audience. If they aren’t engaged, it is on you as the communicator.
This phase will walk you through the following:
This phase involves the following participants:
Don’t fail on execution! The whole reason you labor to create inviting visuals and meaningful metrics is to action those metrics. The metrics results inform your entire story! It’s important to plan and do, but everything is lost if you fail to check and act.
70%: of survey respondents say that managers do not get insights from performance metrics to improve strategic decision making.
60%: of survey respondents say that operational teams do not get insights to improve operation decision making.
(Bernard Marr)
“Metrics aren’t a passive measure of progress but an active part of an organization’s everyday management….Applying the “plan–do–check–act” feedback loop…helps teams learn from their mistakes and identify good ideas that can be applied elsewhere”
(McKinsey)
Activities:
5.1.1 For each dashboard, add a baseline and target to existing metrics and KPIs.
This phase involves the following participants:
Outcomes of this step:
To action your metrics, you must first establish what your baselines and targets are so that you can determine if you are on track.
To establish baselines:
If you do not have a baseline. Run your metric to establish one.
To establish targets:
Actions for Success:
How will you ensure you can get this metric? For example, if you would like to measure delivered value, to make sure the metric is measurable, you will need to ensure that measures of success are documented for an imitative and then measured once complete.
Download Info-Tech IT Dashboard Workbook
Activities:
5.2.1 Record and Action Results
This phase involves the following participants:
Outcomes of this step:
After analyzing your results, use this information to update your dashboards. Revisit Tab 6 of the IT Dashboard Workbook to update your story. Remember to record any audience feedback about the dashboards in the Audience Feedback section.
Action your measures as well as your metrics
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. If metrics need to be changed, record metrics actions under Identified Actions on Tab 7. A metric will need to be addressed in one of the following ways:
Don’t be discouraged if you need to update your metrics a few times before you get it right. It can take some trial and error to find the measures that best indicate the health of what you are measuring.
Download Info-Tech IT Dashboard Workbook
If a metric deviates from your target, you may need to analyze how to correct the issue then run the metric again to see if the results have improved.
Identify Root Cause
Root Cause Analysis can include problem exploration techniques like The 5 Whys, fishbone diagrams, or affinity mapping.
Select a Solution
Once you have identified a possible root cause, use the same technique to brainstorm and select a solution then re-run your metrics.
Consider Tension Metrics
Consider tension metrics when selecting a solution. Will improving one area affect another? A car can go faster but it will consume more fuel – a project can be delivered faster but it may affect the quality.
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.
workshops@infotech.com
1-888-670-8889
The following are sample activities that will be conducted by Info-Tech analysts with your team:

Review the Info-Tech IT Dashboards
Determine how you can use the Info-Tech IT Dashboards in your organization and the anticipated level of customization.

Plan your dashboards
Complete the IT Dashboard Workbook to help plan your dashboards using Info-Tech’s IT Dashboards.

John Corrado
Head of IT
X4 Pharmaceuticals
As head of IT, John is charged with the creation of strategic IT initiatives that align with X4s vision, mission, culture, and long-term goals and is responsible for the organization’s systems, security, and infrastructure. He works closely developing partnerships with X4tizens across the organization to deliver value through innovative programs and services.

Grant Frost
Chief Information & Security Officer
Niagara Catholic School Board
Grant Frost is an experienced executive, information technologist and security strategist with extensive experience in both the public and private sector. Grant is known for, and has extensive experience in, IT transformation and the ability to increase capability while decreasing cost in IT services.

Nick Scozzaro
CEO and Co-Founder of MobiStream and ShadowHQ
ShadowHQ
Nick got his start in software development and mobility working at BlackBerry where he developed a deep understanding of the technology landscape and of what is involved in both modernizing legacy systems and integrating new ones. Working with experts across multiple industries, he innovated, learned, strategized, and ultimately helped push the boundaries of what was possible.

Joseph Sanders
Managing Director of Technology/Cyber Security Services
Kentucky Housing Corporation
In his current role Joe oversees all IT Operations/Applications Services that are used to provide services and support to the citizens of Kentucky. Joe has 30+ years of leadership experience and has held several executive roles in the public and private sector. He has been a keynote speaker for various companies including HP, IBM, and Oracle.

Jochen Sievert
Director Performance Excellence & IT
Zeon Chemicals
Jochen moved to the USA from Duesseldorf, Germany in 2010 to join Zeon Chemicals as their IT Manager. Prior to Zeon, Jochen has held various technical positions at Novell, Microsoft, IBM, and Metro Management Systems.
Info-Tech Contributors
Ibrahim Abdel-Kader, Research Analyst
Donna Bales, Principal Research Director
Shashi Bellamkonda, Principal Research Director
John Burwash, Executive Counselor
Tony Denford, Research Lead
Jody Gunderman, Senior Executive Advisor
Tom Hawley, Managing Partner
Mike Higginbotham, Executive Counselor
Valence Howden, Principal Research Director
Dave Kish, Practice Lead
Carlene McCubbin, Practice Lead
Jennifer Perrier, Principal Research Director
Gary Rietz, Executive Counselor
Steve Schmidt, Senior Managing Partner
Aaron Shum, Vice President, Security & Privacy
Ian Tyler-Clarke, Executive Counselor
Plus, an additional four contributors who wish to remain anonymous.
|
|
Build an IT Risk TaxonomyUse this blueprint as a baseline to build a customized IT risk taxonomy suitable for your organization. |
|
|
Create a Holistic IT DashboardThis blueprint will help you identify the KPIs that matter to your organization. |
|
|
Develop Meaningful Service MetricsThis blueprint will help you Identify the appropriate service metrics based on stakeholder needs. |
|
|
IT Spend & Staffing BenchmarkingUse this benchmarking service to capture, analyze, and communicate your IT spending and staffing. |
|
|
Key Metrics for Every CIOThis short research piece highlights the top metrics for every CIO, how those align to your CIO priorities, and action steps against those metrics. |
|
|
Present Security to Executive StakeholdersThis blueprint helps you identify communication drivers and goals and collect data to support your presentation. It provides checklists for building and delivering a captivating security presentation. |
“10 Signs You Are Sitting on a Pile of Data Debt.” Experian, n.d. Web.
“From the What to the Why: How Data Storytelling Is Key to Success.” Exasol, 2021. Web.
Bonsignore, Marian. “Using Visual Language to Create the Case for Change.” Amarican Management Association. Accessed 19 Apr. 2023.
Calzon, Bernardita. “Top 25 Dashboard Design Principles, Best Practices & How To’s.” Datapine, 5 Apr. 2023.
“Data Literacy.” Tableau, n.d. Accessed 3 May 2023.
“KPIs Don’t Improve Decision-Making In Most Organizations.” LinkedIn, n.d. Accessed 2 May 2023.
Miller, Amanda. “A Comprehensive Guide to Accessible Data Visualization.” Betterment, 2020. Accessed May 2022.
“Performance Management: Why Keeping Score Is so Important, and so Hard.” McKinsey. Accessed 2 May 2023.
Vogel, Douglas, et al. Persuasion and the Role of Visual Presentation Support: The UM/3M Study. Management Information Systems Research Center School of Management University of Minnesota, 1986.
Watson, Morag W., et al. ”IT’s Changing Mandate in an Age of Disruption.” The Economist Intelligence Unit Limited, 2021.
Data has quickly become one of the most valuable assets in any organization. But when it comes to strategically and effectively managing those data assets, many businesses find themselves playing catch-up. The stakes are high because ineffective data management practices can have serious consequences, from poor business decisions and missed revenue opportunities to critical cybersecurity risks.
Successful management and consistent delivery of data assets requires collaboration between the business and IT and the right balance of technology, process, and resourcing solutions.
Data management is not one-size-fits-all. Cut through the noise around data management and create a roadmap that is right for your organization:
This blueprint will help you design a data management practice that builds capabilities to support your organization’s current use of data and its vision for the future.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Effective data delivery and management provides the business with new and improved opportunities to leverage data for business operations and decision making. This blueprint will help you design a data management practice that will help your team build capabilities that align to the business' current usage of data and its vision for the future.
Begin by using the interview guide to engage stakeholders to gain a thorough understanding of the business’ challenges with data, their strategic goals, and the opportunities for data to support their future plans. From there, these tools will help you identify the current and target capabilities for your data management practice, analyze gaps, and build your roadmap.
Strong messaging around the value and purpose of the data management practice is essential to ensure buy-in. Use these templates to build a business case for the project and socialize the idea of data management across the various levels of the organization while anticipating the impact on and reactions from key stakeholders.
This customizable template will support an organized approach to designing a program that addresses the business’ current and evolving data management needs. Use it to plan and track your deliverables and outcomes related to each stage of the project.
Create a roadmap for your data management practice that aligns to your organization’s current needs for data and its vision for how it wants to use data over the next 3-5 years. The initiative tool guides you to identify and record all initiative components, from benefits to costs, while the roadmap template helps you create a presentation to share your project findings with your executive team and project sponsors.
Benefits tracking enables you to measure the effectiveness of your project and make adjustments where necessary to realize expected benefits. This tool will help you track benefit metrics at regular intervals to report progress on goals and identify benefits that are not being realized so that you can take remedial action.
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.
Understand the business’s vision for data and the role of the data management practice.
Determine business requirements for data.
Map business goals and strategic plans to create data strategies.
Understanding of business’s vision for data
Unified vision for data management (business and IT)
Identification of the business’s data strategies
1.1 Establish business context for data management.
1.2 Develop data management principles and scope.
1.3 Develop conceptual data model (subject areas).
1.4 Discuss strategic information needs for each subject area.
1.5 Develop data strategies.
1.6 Identify data management strategies and enablers.
Practice vision
Data management guiding principles
High-level data requirements
Data strategies for key data assets
Determine the current and target states of your data management practice.
Clear understanding of current environment
2.1 Determine the role and scope of data management within the organization.
2.2 Assess current data management capabilities.
2.3 Set target data management capabilities.
2.4 Identify performance gaps.
Data management scope
Data management capability assessment results
Identify how to bridge the gaps between the organization’s current and target environments.
Creation of key strategic plans for data management
3.1 Evaluate performance gaps.
3.2 Identify improvement initiatives.
3.3 Create preliminary improvement plans.
Data management improvement initiatives
Create a realistic and action-oriented plan for implementing and improving the capabilities for data management.
Completion of a Data Management Roadmap
Plan for how to implement the roadmap’s initiatives
4.1 Align data management initiatives to data strategies and business drivers.
4.2 Identify dependencies and priorities
4.3 Build a data management roadmap (short and long term)
4.4 Create a communication plan
Data management roadmap
Action plan
Communication plan
| Executive Brief |
| Analyst Perspective |
| Executive Summary |
| Phase 1: Build Business and User Context |
| Phase 2: Assess Data Management and Build Your Roadmap |
| Additional Support |
| Related Research |
| Bibliography |
Data is one of the most valuable organizational assets, and data management is the foundation – made up of plans, programs, and practices – that delivers, secures, and enhances the value of those assets.
Digital transformation in how we do business and innovations like artificial intelligence and automation that deliver exciting experiences for our customers are all powered by readily available, trusted data. And there’s so much more of it.
A data management roadmap designed for where you are in your business journey and what’s important to you provides tangible answers to “Where do we start?” and “What do we do?”
This blueprint helps you build and enhance data management capabilities as well as identify the next steps for evaluating, strengthening, harmonizing, and optimizing these capabilities, aligned precisely with business objectives and data strategy.
| Andrea Malick
Director, Research & Advisory, Data & Analytics Practice Info-Tech Research Group |
Who this research is for
|
This research will help you
|
This research will also assist
|
This research will also help you
|
Your Challenge
|
Common Obstacles
|
Info-Tech’s Approach
|
Use value streams and business capabilities to develop a prioritized and practical data management plan that provides the highest business satisfaction in the shortest time.
Data management is an enabler of the business and therefore needs to be driven by business goals and objectives. For data to be a strategic asset of the business, the business and IT processes that support its delivery and management must be mature and clearly executed.
Business Drivers
|
Data Management Enablers
|
| REGULATORY COMPLIANCE Regulations are the #1 driver for risk management. |
US$11M:Fine incurred by a well-known Wall Street firm after using inaccurate data to execute short sales orders. |
| “To successfully leverage customer data while maintaining compliance and transparency, the financial sector must adapt its current data management strategies to meet the needs of an ever-evolving digital landscape.” (Phoebe Fasulo, Security Scorecard, 2021) | |
| GOVERNMENT TRANSPARENCY With frequent government scandals and corruption dominating the news, transparency to the public is quickly becoming a widely adopted practice at every level of government. Open government is the guiding principle that the public has access to the documents and proceedings of government to allow for effective public oversight. With growing regulations and pressure from the public, governments must adopt a comprehensive data management strategy to ensure they remain accountable to their rate payers, residents, businesses, and other constituents. |
|
| SPORTS ANALYTICS A professional sports team is essentially a business that is looking for wins to maximize revenue. While they hope for a successful post-season, they also need strong quarterly results, just like you. Sports teams are renowned for adopting data-driven decision making across their organizations to do everything from improving player performance to optimizing tickets sales. At the end of the day, to enable analytics you must have top-notch information management. |
Team Performance Benefits
|
| Industry leaders cite data, and the insights they glean from it, as their means of standing apart from their competitors. | |
| SUPPLY CHAIN EFFICIENCY Data offers key insights and opportunities when it comes to supply chain management. The supply chain is where the business strategy gets converted to operational service delivery of the business. Proper data management enables business processes to become more efficient, productive, and profitable through the greater availability of quality data and analysis. Fifty-seven percent of companies believe that supply chain management gives them a competitive advantage that enables them to further develop their business (FinancesOnline, 2021). |
Involving Data in Your Supply Chain
|
| INFORMED PRODUCT DEVELOPMENT |
Consumer shopping habits and preferences are notoriously variable, making it a challenge to develop a well-received product. Information and insights into consumer trends, shopping preferences, and market analysis support the probability of a successful outcome. |
|
Maintaining a Product Portfolio
|
Internal Data
|
| The world moves a lot faster today
Businesses of today operate in real time. To maintain a competitive edge, businesses must identify and respond quickly to opportunities and events. To effectively do this businesses must have accurate and up-to-date data at their fingertips. To support the new demands around data consumption, data velocity (pace in which data is captured, organized, and analyzed) must also accelerate. Data Management Implications
|
Studies and projections show a clear case of how data and its usage will grow and evolve.
|
|
Analytic Competitor“Given the unforgiving competitive landscape, organizations have to transform now, and correctly. Winning requires an outcome-focused analytics strategy.” (Ramya Srinivasan, Forbes, 2021) |
| Data and the use of data analytics has become a centerpiece to effective modern business. Top-performing organizations across a variety of industries have been cited as using analytics five times more than lower performers (MIT Sloan). | |
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 |
Data debt is the accumulated cost that is associated with the suboptimal governance of data assets in an enterprise, like technical debt.
| Data debt is a problem for 78% of organizations. | |||
40%of organizations say individuals within the business do not trust data insights. |
66%of organizations say a backlog of data debt is impacting new data management initiatives. |
33%of organizations are not able to get value from a new system or technology investment. |
30%of organizations are unable to become data-driven. |
(Source: Experian, 2020)
The journey to being data-drivenThe journey to becoming a data-driven organization requires a pit stop at data enablement. |
The Data Economy
|
Measure success to demonstrate tangible business valuePut data management into the context of the business:
|
Don’t let measurement be an afterthought:Start substantiating early on how you are going to measure success as your data management program evolves. |
|
|
Insight 1Data – it’s your business.Data is a digital imprint of business activities. Data architecture and flows are reflective of the organizational business architecture. Take data management capabilities as seriously as other core business capabilities. |
Insight 2Take a data-oriented approach.Data management must be data-centric – with technology and functional enablement built around the data and its structure and flows. Maintain the data focus during project’s planning, delivery, and evaluation stages. |
Insight 3Get the business into the data business.Data is not “IT’s thing.” Just as a bank helps you properly allocate your money to achieve your financial goals, IT will help you implement data management to support your business goals, but the accountability for data resides with the business. |
Data management is the program and environment we build once we have direction, i.e. a data strategy, and we have formed an ongoing channel with the guiding voice of the business via data governance. Without an ultimate goal in a strategy or the real requirements of the business, what are we building data systems and processes for? We are used to tech buzz words and placing our hope in promising innovations like artificial intelligence. There are no shortcuts, but there are basic proven actions we can take to meet the digital revolution head on and let our data boost our journey.
Key deliverable:Data Management Roadmap TemplateUse this template to guide you in translating your project's findings and outcomes into a presentation that can be shared with your executive team and project sponsors.
|
Blueprint deliverablesEach step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:
|
|
|
In Phase 1 of this blueprint, we will help you establish the business context, define your business drivers and KPIs, and understand your current data management capabilities and strengths.
In Phase 2, we will help you develop a plan and a roadmap for addressing any gaps and improving the relevant data management capabilities so that data is well positioned to deliver on those defined business metrics. |
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 |
|||
| 1. Build Business Context and Drivers for the Data Management Program | 2. Assess Data Management and Build Your Roadmap | |
| Best-Practice Toolkit |
1.1 Review the Data Management Framework 1.2 Understand and Align to Business Drivers 1.3 Build High-Value Use Cases 1.4 Create a Vision |
2.1 Assess Data Management 2.2 Build Your Data Management Roadmap 2.3 Organize Business Data Domains |
| Guided Implementation |
|
|
| Phase Outcomes |
|
|
A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.
A typical GI is 8 to 12 calls over the course of 4 to 6 months.
What does a typical GI on this topic look like?
Phase 1 |
Phase 2 |
|||
| Call #1: Understand drivers, business context, and scope of data management at your organization. Learn about Info-Tech’s approach and resources.
Call #2: Get a detailed overview of Info-Tech’s approach, framework, Data Culture Diagnostic, and blueprint. |
Call #3:Align your business capabilities with your data management capabilities. Begin to develop a use case framework.
Call #4:Further discuss alignment of business capabilities to data management capabilities and use case framework. |
Call #5: Assess your current data management capabilities and data environment. Review your Data Culture Diagnostic Scorecard, if applicable.
Call #6: Plan target state and corresponding initiatives. |
Call #7: Identify program risks and formulate a roadmap.
Call #8: Identify and prioritize improvements. Define a RACI chart. |
Call #9: Summarize results and plan next steps. |
Workshop Overview |
Contact your account representative for more information.
workshops@infotech.com1-888-670-8889 |
| Day 1 | Day 2 | Day 3 | Day 4 | Day 5 | |
| Activities |
Understand and contextualize1.1 Review your data strategy. 1.2 Learn data management capabilities. 1.3 Discuss DM capabilities cross-dependencies and interactions. 1.4 Develop high-value use cases. |
Assess current DM capabilities and set improvement targets2.1 Assess you current DM capabilities. 2.2 Set targets for DM capabilities. |
Formulate and prioritize improvement initiatives3.1 Formulate core initiatives for DM capabilities improvement. 3.2 Discuss dependencies across the initiatives and prioritize them. |
Plan for delivery dates and assign RACI4.1 Plan dates and assign RACI for the initiatives. 4.2 Brainstorm initiatives to address gaps and enable business goals. |
Next steps and wrap-up (offsite)5.1 Complete in-progress deliverables from previous four days. 5.2 Set up review time for workshop deliverables and to discuss next steps. |
| Deliverables |
|
|
|
|
|
What is data management and why is it needed?“Data management is the development, execution, and supervision of plans, policies, programs and practices that deliver, control, protect and enhance the value of data and information assets throughout their lifecycles.” (DAMA International, 2017)Achieving successful management and consistent delivery of data assets throughout their lifecycle requires the collaboration of the business and IT and the balance of technology, process, and resourcing solutions. |
Who:This research is designed for:
Are your data management capabilities optimized to support your organization’s data use and demand? |
Situation
|
Complication
|
Info-Tech Insight
A data strategy should never be formulated disjointed from the business. Ensure the data strategy aligns with the business strategy and supports the business architecture. |
“Data management is the development, execution, and supervision of plans, policies, programs and practices that deliver, control, protect and enhance the value of data and information assets throughout their lifecycles.” (DAMA International, 2017)
|
Adapted from DAMA-DMBOK and Advanced Knowledge Innovations Global Solutions |
Info-Tech’s Data Management Framework is designed to show how an organization’s business model sits as the foundation of its data management practice. Drawing from the requirements of the underpinning model, a practice is designed and maintained through the creation and application of the enablers and dimensions of data management.
| Business Resources
Data subject areas provide high-level views of the data assets that are used in business processes and enable an organization to perform its business functions. Classified by specific subjects, these groups reflect data elements that, when used effectively, are able to support analytical and operational use cases of data. This layer is representative of the delivery of the data assets and the business’ consumption of the data. Data is an integral business asset that exists across all areas of an organization
|
For a data management practice to be effective it ultimately must show how its capabilities and operations better support the business in accessing and leveraging its key data assets.* *This project focuses on building capabilities for data management. Leverage our data quality management research to support you in assessing the performance of this model. |
| Information Dimensions
Components at the Information Dimensions layer manage the different types of data and information present with an environment. At this layer, data is managed based on its type and how the business is looking to use and access the data. Custom capabilities are developed at this level to support:
|
|
| Use these guiding principles to contextualize the purpose and value for each data management enabler.
Info-Tech categorizes data management enablers as the processes that guide the management of the organization’s data assets and support the delivery. |
|
| Info-Tech employs a consumer-driven approach to requirements gathering in order to support a data management practice. This will create a vision and strategic plan that will help to make data an enabler to the business as it looks to achieve its strategic objectives. | ||
Data Strategy PlanningTo support the project in building an accurate understanding of the organization’s data requirements and the role of data in its operations (current and future), the framework first guides organizations on a business and subject area assessment. By focusing on data usage and strategies for unique data subject areas, the project team will be better able to craft a data management practice with capabilities that will generate the greatest value and proactively handle evolving data requirements. |
|
Data Management AssessmentTo support the design of a fit-for-purpose data management practice that aligns with the business’ data requirements this assessment will guide you in:
|
Phase 1
1.1 Review the Data Management Framework 1.2 Understand and Align to Business Drivers 1.3 Build High-Value Use Cases 1.4 Create a Vision | Phase 22.1 Assess Data Management 2.2 Build Your Data Management Roadmap 2.3 Organize Business Data Domains |
This phase will walk you through the following activities:
|
This phase involves the following participants:
|
1.1.1 Walk through the main parts of the best-practice Data Management Framework
This step will guide you through the following activities:
|
Outcomes of this step
|
| Step 1.1 | Step 1.2 | Step 1.3 | Step 1.4 |
| Business Strategy
Organizational Goals & Objectives Business Drivers Industry Drivers Current EnvironmentData Management Capability Maturity Assessment Data Culture Diagnostic Regulatory and Compliance Requirements |
Data Strategy
|
Unlock the Value of Data
Generate Game-Changing Insights Fuel Data-Driven Decision Making Innovate and Transform With Data Thrive and Differentiate With a Data-Driven Culture Elevate Organizational Data IQ Build a Foundation for Data Valuation |
What is a data strategy and why is it needed?
What is driving the need to formulate or refresh your organization’s data strategy? | Who:This research is designed for:
Info-Tech InsightA data strategy should never be formulated disjointed from the business. Ensure the data strategy aligns with the business strategy and supports the business architecture. |
What is data governance and why is it needed?
Do you feel there is a clear definition of data accountability and responsibility in your organization? | Who:This research is designed for:
Info-Tech InsightData governance should not sit as an island in your organization. It must continuously align with the organization’s enterprise governance function. |
Info-Tech’s Data Platform FrameworkData pipeline for versatile and scalable data delivery
|
What are the data platform and practice and why are they needed?
Does your data platform effectively serve your reporting and analytics capabilities? | Who:This research is designed for:
Info-Tech InsightInfo-Tech’s approach is driven by business goals and leverages standard data practice and platform patterns. This enables the implementation of critical and foundational data and analytics components first and subsequently facilitates the evolution and development of the practice and platform over time. |
Formulating an enterprise reporting and analytics strategy requires the business vision and strategies to first be substantiated. Any optimization to the data warehouse, integration, and source layers is in turn driven by the enterprise reporting and analytics strategy.
The current states of your integration and warehouse platforms determine what data can be used for BI and analytics. |
Your enterprise reporting and analytics strategy is driven by your organization’s vision and corporate strategy. |
What is reporting and analytics and why is it needed?
Do you have a strategy to enable self-serve analytics? What does your operating model look like? Have you an analytics CoE? | Who:This research is designed for:
Info-Tech InsightFormulating an enterprise reporting and analytics strategy requires the business vision and strategies to first be substantiated. Any optimization to the data warehouse, integration, and source layer is in turn driven by the enterprise reporting and analytics strategy. |
Info-Tech’s methodology:
|
|
|
|
|
|
What is data architecture and why is it needed?
Is your architecture optimized to sustainably deliver readily available and accessible data to users? | Who:This research is designed for:
Info-Tech InsightData architecture is not just about models. Viewing data architecture as just technical data modeling can lead to a data environment that does not aptly serve or support the business. Identify your business’ priorities and adapt your data architecture to those needs. |
What is data quality management and why is it needed?
Do your users have an optimal level of trust and confidence in the quality of the organization’s data? | Who:This research is designed for:
Info-Tech InsightData quality suffers most at the point of entry. The resulting domino effect of error propagation makes these errors among the most costly forms of data quality errors. Fix data ingestion, whether through improving your application and database design or improving your data ingestion policy, and you will fix a majority of data quality issues. |
| Drivers | Governance | Information Architecture | Process | Policy | Systems Architecture |
Regulatory, Legal –›Efficiency, Cost-Effectiveness –›Customer Service –›User Experience –› |
|
|
|
|
|
|
|||||
What is enterprise content management and why is it needed?“Enterprise Content Management is the systematic collection and organization of information that is to be used by a designated audience – business executives, customers, etc. Neither a single technology nor a methodology nor a process, it is a dynamic combination of strategies, methods and tools used to capture, manage, store, preserve and deliver information supporting key organizational processes through its entire lifecycle.” (AIIM, 2021)
| Who:This research is designed for:
Info-Tech InsightECM is critical to becoming a digital and modernized operation, where both structured data (such as sales reports) and unstructured content (such as customer sentiment in social media) are brought together for a 360-degree view of the customer or for a comprehensive legal discovery. |
| Overview
Metadata is structured information that describes, explains, locates, or otherwise makes it easier to retrieve, use, or manage an information resource. Metadata is often called data about data or information about information (NISO). Metadata management is the function that manages and maintains the technology and processes that creates, processes, and stores metadata created by business processes and data.
|
Value of Effective Metadata Management
Critical Success Factors of Metadata Management
|
||||||||
| On one hand…
Data has massive potential to bring insight to an organization when combined and analyzed in creative ways. On the other hand…It is difficult to bring data together from different sources to generate insights and prevent stale data. How can these two ideas be reconciled?Answer: Info-Tech’s Data Integration Onion Framework summarizes an organization’s data environment at a conceptual level and is used to design a common data-centric integration environment. |
Info-Tech’s Data Integration Onion Framework |
Data-centric integration is the solution you need to bring data together to break down data silos. |
What is data integration and why is it needed?
Is your integration near real time and scalable? | Who:This research is designed for:
Info-Tech InsightEvery IT project requires data integration. Any change in the application and database ecosystem requires you to solve a data integration problem. |
|
Master data management (MDM) “entails control over Master Data values and identifiers that enable consistent use, across systems, of the most accurate and timely data about essential business entities” (DAMA, 2017).
Fundamental objective of MDM: Enable the business to see one view of critical data elements across the organization. |
|
What is MDM and why is it needed?
Is there traceability and visibility into your data’s lineage? Does your data pipeline facilitate that single view across the organization? | Who:This research is designed for:
Info-Tech InsightSuccessful MDM requires a comprehensive approach. To be successfully planned, implemented, and maintained it must include effective capabilities in the critical processes and subpractices of data management. |
Data Modeling Framework
|
|
Model hierarchy
| ![]() Info-Tech InsightThe Conceptual model acts as the root of all the models required and used by an organization. |
The Conceptual data model adds relationships to your business data glossary terms and is the first step of the modeling journey.
Objectives of Data Operations Management
Indicators of Successful Data Operations Management
|
|
1.2.1 Define your value streams
1.2.2 Identify your business capabilities
1.2.3 Categorize your organization’s key business capabilities
1.2.4 Develop a strategy map tied to data management
This step will guide you through the following activities:
| Outcomes of this step
|
Build Business Context and Drivers
| Step 1.1 | Step 1.2 | Step 1.3 | Step 1.4 |
| There are several key questions to ask when endeavouring to identify value streams. |
Key Questions
|
Input: Business strategy/goals, Financial statements, Info-Tech’s industry-specific business architecture
Output: List of organization-specific value streams, Detailed value stream definition(s)
Materials: Whiteboard/kanban board, Info-Tech’s Reference Architecture Template – contact your Account Representative for details, Other industry standard reference architecture models: BIZBOK, APQC, etc., Info-Tech’s Archimate models
Participants: Enterprise/Business Architect, Business Analysts, Business Unit Leads, CIO, Departmental Executive & Senior managers
Unify the organization’s perspective on how it creates value.
Contact your Account Representative for access to Info-Tech’s Reference Architecture Template
| Value streams connect business goals to the organization’s value realization activities. These value realization activities, in turn, depend on data. If the organization does not have a business architecture function to conduct and guide Activity 1.2.1, you can leverage the following approach:
| Align data management to the organization’s value realization activities.Value streams enable the organization to create or capture value in the market in which it operates by engaging in a set of interconnected activities. Info-Tech InsightYour organization’s value streams and the associated business capabilities require effectively managed and governed data. Without this, you could face elevated operational costs, missed opportunities, eroded stakeholder satisfaction, negative impact to reputation and brand, and/or increased exposure to business risk. |
Example 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. |
|
For this value stream, download Info-Tech’s Industry Reference Architecture for Retail Banking.
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. |
|
For this value stream, download Info-Tech’s Industry Reference Architecture for Higher Education.
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. |
|
For this value stream, download Info-Tech’s Industry Reference Architecture for Local Government.
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. |
|
For this value stream, download Info-Tech’s Industry Reference Architecture for Manufacturing.
| A business capability defines what a business does to enable value creation. Business capabilities represent stable business functions and typically will have a defined business outcome. Business capabilities can be thought of as business terms defined using descriptive nouns such as “Marketing” or “Research and Development.” If your organization doesn’t already have a business capability map, you can leverage the following approach to build one. This initiative requires a good understanding of the business. By working with the right stakeholders, you can develop a business capability map that speaks a common language and accurately depicts your business. Working with the stakeholders as described in the slide entitled “Define or validate the organization’s value streams”:
| Align data management to the organization’s value realization activities.Info-Tech InsightA business capability map can be thought of as a visual representation of your organization’s business capabilities and hence represents a view of what your data management program must support. For more information, refer to Info-Tech’s Document Your Business Architecture. |
Input: List of confirmed value streams and their related business capabilities
Output: Business capability map with value streams for your organization
Materials: Your existing business capability map, Business Alignment worksheet provided in the Data Management Assessment and Planning Tool, Info-Tech’s Document Your Business Architecture blueprint
Participants: Key business stakeholders, Data stewards, Data custodians, Data leads and administrators
Confirm your organization's existing business capability map or initiate the formulation of a business capability map:
Note: A business capability defines what a business does to enable value creation. Business capabilities are business terms defined using nouns such as “Marketing” or “Research and Development.” They represent stable business functions, are unique and independent of one another, and typically will have a defined business outcome.
Example business capability map – Retail BankingA business capability map can be thought of as a visual representation of your organization’s business capabilities and hence represents a view of what your data governance program must support.Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders. Info-Tech Tip: Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realization capabilities under discussion. This will help to build awareness and visibility of the data management program. |
Example business capability map for: Retail Banking
For this business capability map, download Info-Tech’s Industry Reference Architecture for Retail Banking. |
Example business capability map – Higher EducationA business capability map can be thought of as a visual representation of your organization’s business capabilities and hence represents a view of what your data governance program must support.Validate your business capability map with the right stakeholders, including your executive team, business unit leaders, and/or other key stakeholders. Info-Tech Tip: Leverage your business capability map verification session with these key stakeholders as a prime opportunity to share and explain the role of data and data governance in supporting the very value realization capabilities under discussion. This will help to build awareness and visibility of the data management program. | Example business capability map for: Higher Education
For this business capability map, download Info-Tech’s Industry Reference Architecture for Higher Education. |
Example business capability map – Local GovernmentA 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
For this business capability map, download Info-Tech’s Industry Reference Architecture for Local Government. |
Example business capability map – ManufacturingA 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
For this business capability map, download Info-Tech’s Industry Reference Architecture for Manufacturing. |
Example business capability map – RetailA 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
For this business capability map, download Info-Tech’s Industry Reference Architecture for Retail. |
Input: Strategic insight from senior business stakeholders on the business capabilities that drive value for the organization
Output: Business capabilities categorized and prioritized (e.g. cost advantage creators, competitive advantage differentiators, high value/high risk) See next slide for an example
Materials: Your existing business capability map or the business capability map derived in Activity 1.2.2
Participants: Key business stakeholders, Data stewards, Data custodians, Data governance working group
Determine which capabilities are considered high priority in your organization.
This categorization/prioritization exercise helps highlight prime areas of opportunity for building use cases, determining prioritization, and the overall optimization of data and data governance.
For more information, refer to Info-Tech’s Document Your Business Architecture.
Example of business capabilities categorization or heatmapping – RetailThis exercise is useful in ensuring the data governance program is focused and aligned to support the priorities and direction of the business.
|
Example: Retail
For this business capability map, download Info-Tech’s Industry Reference Architecture for Retail. |
Input: Strategic objectives as outlined by the organization’s business strategy and confirmed by senior leaders
Output: A strategy map that maps your organizational strategic objectives to value streams, business capabilities, and ultimately data programs
Materials: Your existing business capability map or the one created in Activity 1.2.2, Business strategy (see next slide for an example)
Participants: Key business stakeholders, Data stewards, Data custodians, Data governance working group
Identify the strategic objectives for the business. Knowing the key strategic objectives will drive business–data governance alignment. It’s important to make sure the right strategic objectives of the organization have been identified and are well understood.
Example of a strategy map tied to data management
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
For this strategy map, download Info-Tech’s Industry Reference Architecture for Retail. |
1.3.1 Build high-value use cases
This step will guide you through the following activities:
|
Outcomes of this step
|
Build Business Context and Drivers
| Step 1.1 | Step 1.2 | Step 1.3 | Step 1.4 |
Input: Value streams and business capabilities as defined by business leaders, Business stakeholders’ subject area expertise, Data custodian systems, integration, and data knowledge
Output: Use cases that articulate data-related challenges, needs, or opportunities that are tied to defined business capabilities and hence, if addressed, will deliver measurable value to the organization
Materials: Your business capability map from Activity 1.2.2, Info-Tech’s Data Use Case Framework Template, Whiteboard or flip charts (or shared screen if working remotely), Markers/pens
Participants: Key business stakeholders, Data stewards and business SMEs, Data custodians, Data leads and administrators
This business needs gathering activity will highlight and create relevant use cases around data-related problems or opportunities that are clear and contained and, if addressed, will deliver value to the organization.
Tip: Don’t conclude these use case discussions without substantiating what measures of success will be used to demonstrate the business value of the effort to produce the desired future state, as relevant to each particular use case.
Download Info-Tech’s Data Use Case Framework Template
Data use cases |
Sample Data |
The following is the list of use cases as articulated by key stakeholders at [Organization Name].
The stakeholders see these as areas that are relevant and highly valuable for delivering strategic value to [Organization Name].
Use Case 1: Customer/Student/Patient/Resident 360 View
Use Case 2: Project/Department Financial Performance
Use Case 3: Vendor Lifecycle Management
Use Case 4: Project Risk Management
Use case 1 | Sample Data |
Problem statement:
If we could solve this:
Use case 1: challenges, risks, and opportunities | Sample Data |
Use case 1 (cont'd) | Sample Data |
Use case 1 (cont'd) | Sample Data |
| 1. |
What business capability (or capabilities) in your business area is this use case tied to? |
Examples: Demand Planning, Assortment Planning, Allocation & Replenishment, Fulfillment Planning, Customer Management |
| 2. |
What are your data-related challenges in performing this today? |
| 3. |
What are the steps in the process/activity today? |
|
| 4. |
What are the applications/systems used at each step today? |
|
| 5. |
What data domains are involved, created, used, or transformed at each step today? |
| 6. |
What does an ideal or improved state look like? |
|
| 7. |
What other business units, business capabilities, activities, or processes will be impacted and/or improved if this were to be solved? |
|
| 8. |
Who are the stakeholders impacted by these changes? Who needs to be consulted? |
|
| 9. |
What are the risks to the organization (business capability, revenue, reputation, customer loyalty, etc.) if this is not addressed? |
| 10. |
What compliance, regulatory, or policy concerns do we need to consider in any solution? |
|
| 11. |
What measures of success or change should we use to prove the value of the effort (KPIs/ROI)? What is the measurable business value of doing this? |
| 10. |
Conclusion: What are the data capabilities that need to be optimized, addressed, or improved to support or help realize the business capability (or capabilities) highlighted in this use case?(Tip: This will inform your future-state data capabilities optimization planning and roadmapping activities.) |
Data Management Workshop
|
[SAMPLE] |
| Problem Statement
Inability to provide insights to DPH due to inconsistent data, inaccurate reporting, missing governance, and unknown data sources resulting in decisions that impact citizens being made without accurate information. |
||
Challenges
|
What Does Amazing Look Like?
|
|
Related Processes/Impact
|
Compliance
|
Benefits/KPIs
|
Data Management Workshop
|
[SAMPLE] |
| Problem Statement Inability to provide insights to DPH due to inconsistent data, inaccurate reporting, missing governance, and unknown data sources resulting in decisions that impact citizens being made without accurate information. | |||
Current Steps in Process Activity (Systems)
| Data Flow diagram
| ||
| Systems | Data Management Dimensions
| ||
Data Management Workshop
| [SAMPLE] |
| Problem Statement Inability to provide insights to DPH due to inconsistent data, inaccurate reporting, missing governance, and unknown data sources resulting in decisions that impact citizens being made without accurate information. | |
| List Future Process Steps Prior to COVID-19 Emergency Response:
After COVID-19 Emergency Response:
| Future Process and Data Flow
|
1.4.1 Craft a vision
1.4.2 Create guiding principles
This step will guide you through the following activities:
| Outcomes of this step
|
Build Business Context and Drivers
| Step 1.1 | Step 1.2 | Step 1.3 | Step 1.4 |
Input: Organizational vision and mission statements, Stakeholder survey results and elicitation findings, Use cases, Business and data capability map
Output: Vision and mission statements
Materials: Markers and pens, Whiteboard, Online whiteboard, Vision samples and templates
Participants: Key business stakeholders, Data managers, Data owners, Business leads and SMEs, Project team, Project sponsor
Complete the vision statement to set the direction, the “why,” for the changes we’re making. The vision is a reference point that should galvanize everyone in the organization and set guardrails for technical and process decisions to follow.
Create a common data management vision that is consistently communicated to the organizationA data management program should be an enterprise-wide initiative.
|
Info-Tech Tips
|
| A vision represents the way your organization intends to be in the future.
A clear vision statement helps align the entire organization to the same end goal. Your vision should be brief, concise, and inspirational; it is attempting to say a lot in a few words, so be very thoughtful and careful with the words you choose. Consider your strengths across departments – business and IT, the consumers of your services, and your current/future commitments to service quality. Remember that a vision statement is internally facing for other members of your company throughout the process. |
A mission expresses why you exist.
While your vision is a declaration of where your organization aspires to be in the future, your mission statement should communicate the fundamental purpose of the data management practice. It identifies the function of the practice, what it produces, and its high-level goals that are linked to delivering timely, high-quality, relevant, and valuable data to business processes and end users. Consider if the practice is responsible for providing data for analytical and/or operational use cases. A mission statement should be a concise and clear statement of purpose for both internal and external stakeholders. |
| “The Vision is the What, Where or Who you want the company to become. The Mission is the WHY the company exists, it is your purpose, passion or cause.” (Doug Meyer-Cuno, Forbes, 2021) | |
Corporate |
Group 1 |
Group 2 |
| Vision:
Create and maintain an institution of world-class excellence. |
Vision: | Vision: |
| Mission:
Foster an economic and financial environment conducive to sustainable economic growth and development. |
Mission: | Mission: |
|
The vision is a statement about the organization’s goals and provides a basis to guide decisions and rally employees toward a shared goal. The principles or themes communicate the organization’s priorities for its information management program. Policies are a set of official guidelines that determine a course of action. For example: Company is committed to safety for its employees. Procedures are a set of actions for doing something. For example: Company employees will wear protective gear while on the production floor. |
Use the insights you gathered from users and stakeholders to develop a vision statement
|
The vision should be short, memorable, inspirational and draw a clear picture of what that future-state data management experience looks like.
Is it modern and high end, with digital self-service? Is it a trusted and transparent steward of customer assets? |
Input: Sample data management guiding principles, Stakeholder survey results and elicitation findings, Use cases, Business and data capability map
Output: Data management guiding principles
Materials: Markers and pens, Whiteboard, Online whiteboard, Guiding principles samples and templates
Participants: Key business stakeholders, Data managers, Data owners, Business leads and SMEs, Project team, Project sponsor
Draft a set of guiding principles that express your program’s values as a framework for decisions and actions and keep the data strategy alive.
Twelve data management universal principles |
[SAMPLE] |
| Principle | Definitions |
| Data Is Accessible | Data is accessible across the organization based on individuals’ roles and privileges. |
| Treat Data as an Asset | Treat data as a most valuable foundation to make right decisions at the right time. Manage the data lifecycle across organization. |
| Manage Data | Define strategic enterprise data management that defines, integrates, and effectively retrieves data to generate accurate, consistent insights. |
| Define Ownership & Stewardship | Organizations should clearly appoint data owners and data stewards and ensure all team members understand their role in the company’s data management system. |
| Use Metadata | Use metadata to ensure data is properly managed by tacking how data has been collected, verified, reported, and analyzed. |
| Single Source of Truth | Ensure the master data maintenance across the organization. |
| Ensure Data Quality | Ensure data integrity though out the lifecycle of data by establishing a data quality management program. |
| Data Is Secured | Classify and maintain the sensitivity of the data. |
| Maximize Data Use | Extend the organization’s ability to make the most of its data. |
| Empower the Users | Foster data fluency and technical proficiency through training to maximize optimal business decision making. |
| Share the Knowledge | Share and publish the most valuable insights appropriately. |
| Consistent Data Definitions | Establish a business data glossary that defines consistent business definitions and usage of the data. |
Phase 11.1 Review the Data Management Framework 1.2 Understand and Align to Business Drivers 1.3 Build High-Value Use Cases 1.4 Create a Vision | Phase 2
2.1 Assess Data Management 2.2 Build Your Data Management Roadmap 2.3 Organize Business Data Domains |
This phase will walk you through the following activities:
| This phase involves the following participants:
|
2.1.1 Define current state of data management capabilities
2.1.2 Set target state and identify gaps
This step will guide you through the following activities:
| Outcomes of this step
|
Assess Data Management and Build Your Roadmap
| Step 2.1 | Step 2.2 | Step 2.3 |
Define current stateThe Data Management Assessment and Planning Tool will help you analyze your organization’s data requirements, identify data management strategies, and systematically develop a plan for your target data management practice.
|
|
Input: Stakeholder survey results and elicitation findings, Use cases, Business and data management capability map
Output: Current-state data management capabilities
Materials: Data Management Assessment and Planning Tool
Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians
Assign a maturity level value from 1 to 5 for each question in the assessment tool, organized into capabilities, e.g. Data Governance, Data Quality, Risk.
Input: Stakeholder survey results and elicitation findings, Use cases, Business and data management capability map to identify priorities
Output: Target-state data management capabilities, Gaps identification and analysis
Materials: Data Management Assessment and Planning Tool
Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians
Assign a maturity level value from 1 to 5 for each question in the assessment tool, organized into capabilities, e.g., Data Governance, Data Quality, Risk.
2.2.1 Describe gaps
2.2.2 Define gap initiatives
2.2.2 Build a data management roadmap
This step will guide you through the following activities:
| Outcomes of this step
|
Assess Data Management and Build Your Roadmap
| Step 2.1 | Step 2.2 | Step 2.3 |
Input: Target-state maturity level
Output: Detail and context about gaps to lead planners to specific initiatives
Materials: Data Management Assessment and Planning Tool
Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians
Based on the gaps result, describe the nature of the gap, which will lead to specific initiatives for the data management plan:
Input: Gaps analysis, Gaps descriptions
Output: Data management initiatives
Materials: Data Management Assessment and Planning Tool
Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians
Based on the gap analysis, start to define the data management initiatives that will close the gaps and help the organization achieve its target state.
Input: Gap initiatives, Target state and current-state assessment
Output: Data management initiatives and roadmap
Materials: Data Management Assessment and Planning Tool
Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians
Start to list tangible actions you will take to address gaps and achieve data objectives and business goals along with timelines and responsibility:
2.3.1 Define business data domains and assign owners
This step will guide you through the following activities:
| Outcomes of this step
|
Assess Data Management and Build Your Roadmap
| Step 2.1 | Step 2.2 | Step 2.3 |
Input: Target-state maturity level
Output: Detail and context about gaps to lead planners to specific initiatives
Materials: Data Management Assessment and Planning Tool
Participants: Key business stakeholders, Business leads and SMEs, Project team, Project sponsor, Data leads, Data custodians
Identify the key data domains for each line of business, where the data resides, and the main contact or owner.
Business and data domains | [SAMPLE] |
| Business Domain | App/Data Domains | Business Stewards | Application Owners | Business Owners |
| Client Experience and Sales Tech | Salesforce (Sales, Service, Experience Clouds), Mulesoft (integration point) | (Any team inputting data into the system) | ||
| Quality and Regulatory | Salesforce | |||
| Operations | Salesforce, Salesforce Referrals, Excel spreadsheets, SharePoint | |||
| Finance | Workday, Sage 300 (AccPac), Salesforce, Moneris | Finance | ||
| Risk/Legal | Network share drive/SharePoint | |||
| Human Resources | Workday, Network share drive/SharePoint | HR team | ||
| Corporate Sales | Salesforce (Sales, Service, Health, Experience Clouds), | |||
| Sales and Client Success | Mitel, Outlook, PDF intake forms, Workday, Excel. | Sales & Client Success Director, Marketing Director | CIO, Sales & Client Success Director, Marketing Director |
Embrace the technologyMake the available data governance tools and technology work for you:
|
|
Additional SupportIf 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.
|
|
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:
|
|
Build a Robust and Comprehensive Data StrategyKey to building and fostering a data-driven culture. |
|
Understand the Data and Analytics LandscapeOptimize your data and analytics environment. |
|
Build a Data Pipeline for Reporting and AnalyticsData architecture best practices to prepare data for reporting and analytics. |
| Name | Position | Company |
| Anne Marie Smith | Board of Directors | DAMA International |
| Andy Neill | Practice Lead, Data & Analytics | Info-Tech Research Group |
| Dirk Coetsee | Research Director, Data & Analytics | Info-Tech Research Group |
| Graham Price | Executive Advisor, Advisory Executive Services | Info-Tech Research Group |
| Igor Ikonnikov | Research Director, Data & Analytics | Info-Tech Research Group |
| Jean Bujold | Senior Workshop Delivery Director | Info-Tech Research Group |
| Mario Cantin | Chief Data Strategist | Prodago |
| Martin Sykora | Director | NexJ Analytics |
| Michael Blaha | Author, Patterns of Data Modeling | Consultant |
| Rajesh Parab | Research Director, Data & Analytics | Info-Tech Research Group |
| Ranjani Ranganathan | Product Manager, Research – Workshop Delivery | Info-Tech Research Group |
| Reddy Doddipalli | Senior Workshop Director | Info-Tech Research Group |
AIIM, “What is Enterprise Content Management (ECM)?” Intelligent Information Management Glossary, AIIM, 2021. Web.
BABOK V3: A Guide to Business Analysis Body of Knowledge. IIBA, 2014. Web.
Barton, Dominic, and David Court. "Three Keys To Building a Data-Driven Strategy." McKinsey and Company, 1 Mar. 2013. Web.
Boston University Libraries. "Data Life Cycle » Research Data Management | Boston University." Research Data Management RSS. Boston University, n.d. Accessed Oct. 2015.
Chang, Jenny. “97 Supply Chain Statistics You Must Know: 2020 / 2021 Market Share Analysis & Data.” FinancesOnline, 2021. Web.
COBIT 5: Enabling Information. ISACA, 2013. Web.
CSC (Computer Sciences Corporation), Big Data Infographic, 2012. Web.
DAMA International. DAMA-DMBOK Guide. 1st ed., Technics Publications, 2009. Digital.
DAMA International. “DAMA Guide to the Data Management Body of Knowledge (DAMA-DMBOK2 Guide).” 2nd ed., 2017. Accessed June 2017.
Davenport, Thomas H. "Analytics in Sports: The New Science of Winning." International Institute for Analytics, 2014. Web.
Department of Homeland Security. Enterprise Data Management Policy. Department of Homeland Security, 25 Aug. 2014. Web.
Enterprise Data Management Data Governance Plan. US Federal Student Aid, Feb. 2007. Accessed Oct. 2015.
Experian. “10 signs you are sitting on a pile of data debt.” Experian, 2020. Accessed 25 June 2021.
Fasulo, Phoebe. “6 Data Management Trends in Financial Services.” SecurityScorecard, 3 June 2021. Web.
Georgia DCH Medicaid Enterprise – Data Management Strategy. Georgia Department of Community Health, Feb. 2015. Accessed Oct. 2015.
Hadavi, Cyrus. “Use Exponential Growth of Data to Improve Supply Chain Operations.” Forbes, 5 Oct. 2021. Web.
Harbert, Tam. “Tapping the power of unstructured data.” MIT Sloan, 1 Feb. 2021. Web.
Hoberman, Steve, and George McGeachie. Data Modeling Made Simple with PowerDesigner. Technics Pub, 2011. Print.
“Information Management Strategy.” Information Management – Alberta. Service Alberta, Nov.-Dec. 2013. Web.
Jackson, Brian, et al. “2021 Tech Trends.” Info-Tech Research Group, 2021. Web.
Jarvis, David, et al. “The hyperquantified athlete: Technology, measurement, and the business of sports.” Deloitte Insights, 7 Dec. 2020. Web.
Johnson, Bruce. “Leveraging Subject Area Models.” EIMInsight Magazine, vol. 3, no. 4, April 2009. Accessed Sept. 2015.
Lewis, Larry. "How to Use Big Data to Improve Supply Chain Visibility." Talking Logistics, 14 Sep. 2014. Web.
McAfee, Andrew, and Erik Brynjolfsson. “Big Data: The Management Revolution,” Harvard Business Review, vol. 90, no. 10, 2012, pp. 60-68.
Meyer-Cuno, Doug. “Is A Vision Statement Important?” Forbes, 24 Feb. 2021. Web.
MIT. “Big Data: The Management Revolution.” MIT Center for Digital Business, 29 May 2014. Accessed April 2014.
"Open Framework, Information Management Strategy & Collaborative Governance.” MIKE2 Methodology RSS, n.d. Accessed Aug. 2015.
PwC. “Asset Management 2020: A Brave New World.” PwC, 2014. Accessed April 2014.
Riley, Jenn. Understanding Metadata: What is Metadata, and What is it For: A Primer. NISO, 1 Jan. 2017. Web.
Russom, Philip. "TDWI Best Practices Report: Managing Big Data." TDWI, 2013. Accessed Oct. 2015.
Schneider, Joan, and Julie Hall. “Why Most Product Launches Fail.” Harvard Business Review, April 2011. Web.
Sheridan, Kelly. "2015 Trends: The Growth of Information Governance | Insurance & Technology." InformationWeek. UBM Tech, 10 Dec. 2014. Accessed Nov. 2015.
"Sports Business Analytics and Tickets: Case Studies from the Pros." SloanSportsConference. Live Analytics – Ticketmaster, Mar. 2013. Accessed Aug. 2015.
Srinivasan, Ramya. “Three Analytics Breakthroughs That Will Define Business in 2021.” Forbes, 4 May 2021. Web.
Statista. “Amount of data created, consumed, and stored 2010-2020.” Statista, June 2021. Web.
“Understanding the future of operations: Accenture Global Operations Megatrends research.” Accenture Consulting, 2015. Web.
Vardhan, Harsh. “Why So Many Product Ideas Fail?” Medium, 26, Sept. 2020. Web.
With COVID-19's rapid spread through populations, governments are looking for technology tools that can augment the efforts of manual contact tracing processes. How the system is designed is crucial to a positive outcome.
Mobile contact tracing apps that use a decentralized design approach will be the most likely to be adopted by a wide swath of the population.
There are some key considerations to realize from the way different governments are approaching contact tracing:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Brands that fail to invest in brand awareness are likely to face some, if not all these problems:
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.
Building brand awareness allows for the increase of:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
A two-step approach to building brand awareness, starting with defining the brand foundations and then implementing effective brand awareness strategies and tactics.
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.
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.
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.

Nathalie Vezina
Marketing Research Director
SoftwareReviews Advisory
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:
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:
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:
"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
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:
"Products are made in a factory, but brands are created in the mind."
Source: Walter Landor
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
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:
"Your brand is the single most important investment you can make in your business."
Source: Steve Forbes
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:
How far are you from being the brand buyers think of first in your target market?

Based on David Aaker's brand loyalty pyramid
Focus on effective ways to gain brand recognition in the minds of buyers.

Brand recognition requires in-depth knowledge of the target market, the creation of strong brand attributes, and increased presence and visibility.
To implement a winning brand awareness-building strategy, you must:
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:

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.
If your brand was a person, who would it be?
Physically attractive
Intellectually stimulating
Sociable
Emotionally connected
Morally sound
Personable
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
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
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
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:
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
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:
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
Avoid
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:
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
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:
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
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
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
Brand attributes
Brand visibly and recall
Brand awareness building plan
"Strong brands outperform their less recognizable
competitors by as much as 73%."
Source: McKinsey
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:
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
Start building brand awareness
Toolkit
Short and long-term benefits of increasing brand awareness
Increase:
It typically takes 5-7 brand interactions before a buyer remembers the brand.
Source: Startup Bonsai
This research is being designed for:
Brand and marketing leaders who:
This research will also assist:
This research will help you:
This research will help them:
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 |
|
|
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).
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. |
Phase 1Build brands' personality and message |
Phase 2Start building brand awareness |
||
|---|---|---|---|
|
|
|
|
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.
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:
|
![]() |
Define brands' personality and message
Start building brand awareness
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
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
MarTech
May require you to:
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. |
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:
Also included is an executive presentation template to communicate the results to key stakeholders and recommendations to fix the uncovered issues.
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
MarTech
May require you to:
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.
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
Tools
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. |
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
Tools
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. |
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.
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
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
Tools
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.
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
Tools
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:
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
MarTech
May require you to:
Tools
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.
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:
![]() |
![]() |
Create a Buyer Persona and Journey Get deeper buyer understanding and achieve product-market fit, with easier access to market and sales
|
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.
|
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.
After three decades navigating the complexities of organizational resilience, one truth stands clearer than ever: you cannot truly protect what you do not deeply understand. And for any business, especially in today's dynamic landscape, what you do is ultimately about what you do for your customers. There is something that I see insufficiently matured or missing in many companies: building a comprehensive “service map.”
Think about it. We pour resources into product development, marketing, and sales, yet how often do we collectively pause to articulate, across all departments, exactly what services we provide to our customers? It sounds simple, doesn't it? Yet, the reality is typically a fragmented understanding, siloed information, and a distinct lack of a holistic view, except by a few key people.
Why is this clear view so critical? Because your customers don't interact with your internal departments; they interact with your services. They don't care about your organizational chart; they care about how seamlessly you meet their needs. Without a clear service map, you have blind spots. You miss opportunities for optimization, you introduce friction into customer journeys, and critically, you compromise your ability to recover when things go wrong. Resilience isn't just about bouncing back; it's about understanding what's truly essential to protect your customer relationships.
Let's make this real.
What services do banks offer? It’s far more than just “banking.” They provide:
Retail Banking: Current accounts, savings accounts, debit/credit cards, personal loans, mortgages.
Investment Services: Wealth management, brokerage, mutual funds, pension products.
Business Banking: Corporate loans, treasury services, payroll solutions, trade finance.
Digital Services: Online banking platforms, mobile apps, and payment gateways.
Advisory Services: Financial planning, retirement planning, and estate planning.
Let's hone in on an often complex offering: a pension savings product where you contribute monthly. This isn't just a “product” on a shelf; it's a living, breathing service with a distinct customer journey.
Imagine the customer journey for this:
Customer Initiates Payment (or Automated Process Triggers): On the designated payment date, a SEPA Direct Debit instruction is initiated, pulling funds from the customer's linked bank account.
Funds Transfer & Clearance: The funds travel through interbank networks, cleared and settled between the customer's bank and the financial institution’s holding accounts.
Internal Reconciliation & Allocation: Upon receipt, the funds are reconciled against the customer's pension account number and allocated to their specific pension product.
Investment Instruction: Based on the product's pre-defined investment strategy (e.g., a balanced fund, equity fund), an instruction is generated to purchase units in the underlying investments.
Market Execution: The instruction is sent to the relevant trading desks or automated systems, which execute the purchase of shares, bonds, or other assets on the stock market at prevailing market prices.
Confirmation & Update: Once the trade is settled, the customer's pension account is updated to reflect the new units purchased and the updated total value, often visible via an online portal or statement.
For every single step in this service, your organization needs robust capabilities to make these steps visible and resilient to all stakeholders who “work around that service.” This isn't just for IT; it's for compliance, operations, customer service, and even marketing.
Let's look at the same for a realtor company specializing in rental properties:
Service Map for property owners and landlords:
Property Listing & Marketing: Creating professional listings, photography, virtual tours, and advertising on various platforms (online portals, social media, and local networks).
Tenant Sourcing & Vetting: Conducting viewings, screening potential tenants (credit checks, employment verification, previous landlord references), and background checks.
Lease Agreement Management: Drafting, negotiating, and executing legally compliant rental contracts.
Property Maintenance & Repairs Coordination: Arranging routine maintenance, coordinating emergency repairs with vetted contractors, and overseeing work quality.
Property Inspections: Conducting periodic property inspections (move-in, routine, move-out) to ensure property condition and compliance with lease terms.
Compliance & Legal Guidance: Advising on landlord-tenant laws, health & safety regulations, and handling eviction processes if necessary.
Security Deposit Management: Collecting, holding, and returning security deposits in accordance with legal requirements.
Services for tenants:
Property Search & Matching: Assisting prospective tenants in finding suitable properties based on their needs and budget.
Viewing Scheduling: Arranging property viewings and providing access.
Application Processing: Guiding tenants through the application process and necessary documentation.
Lease Onboarding: Explaining lease terms, facilitating key handover, and conducting move-in inspections.
Maintenance Request Handling: A clear process for tenants to report maintenance issues and track resolution.
Emergency Support: Providing contact points and procedures for urgent property-related emergencies.
Lease Renewal & Move-out Support: Managing lease renewals, providing guidance on move-out procedures, and facilitating security deposit returns.
Many of these will require automated systems. The customer-facing ones even more so. You need to understand the customer journeys for each entry in your service map.
You need:
Comprehensive Monitoring & Alerting: Real-time visibility into every step of the journey, flagging anomalies or delays before they become customer-impacting issues. Build monitoring capabilities into the systems and build the operational capability to follow up on alerts and events. There are now products on the market that can do a lot of the heavy lifting for you. Be prepared to open your wallet. This is not cheap. I hear AI already rolling off the tongues: this is not cheap. For smaller service maps and customer journeys, consider using built-in tools and hiring a small team of people that can leverage the next points. For large institutions, let alone manufacturing, automation and continuous testing are key.
Centralized Knowledge Management: A single source of truth for service definitions, processes, dependencies, and known issues, accessible to everyone who needs it. No more tribal knowledge. For condensed setups, it can be as simple as a folder on a hard drive that contains your knowledge base articles (aka Word documents that explain the process, how it was set up, what you need to operate it etc.). Most businesses will use some form of knowledge management system that is a bit more sophisticated, perhaps even built-in to the IT Operations Management (ITOM) tooling. It's a shame it's called IT ops tooling, because you can equally use this for business process documentation. Just remember the last bullet below: DR and BCP. Your knowledge system is useless if you cannot get to it!
Robust Development & Operations Processes: Seamless collaboration between development, operations, and business teams to make sure services are built, tested, deployed, and managed efficiently and reliably. It does not really matter if you want to use DevOps, or change/run, or scrum and squads, or anything in between. Pick what works in your culture. Also, it is not one-size-fits-all. Some systems are core and require a more strict regimen; others must be able to turn on a dime. But whatever you use: keep your service and the customer journey through it front and center. Build it so that you have clearly separated “stations” where something is done to fulfill the system. Make the mental analogy with a factory. It will keep each station atomic, so that when the time comes to make changes, you can do so without having to re-invent large parts of the value delivery chain.
End-to-End Security Protocols: Protect sensitive customer data and financial transactions at every touchpoint throughout the journey. I mean, duh. You must. This is non-negotiable. This includes your backups. Large or small company, you must maintain backups. Use the 321 method: 3 copies of your data and setups on 2 different platforms or data storage carriers and 1 offsite. Your backups should include at least 1 immutable copy. That is a copy that cannot be altered. Large firms partner with their hosting companies to include that in the service offering; small companies have cheap options. I use 2 separate backup providers (total cost around €100/month at the time of writing in 2025) and my own disconnected storage carriers. I even use a backup provider and disconnected storage for my family's data (around €25/month).
Effective Disaster Recovery (DR) & Business Continuity Planning (BCP) Capabilities: Understanding critical service components, their recovery time objectives (RTOs), and recovery point objectives (RPOs) to ensure rapid restoration of service even after major disruptions. This isn't a theoretical exercise; it needs to be tested and proven. Your expectations also need to be realistic.
There are more elements to consider when building your service map and the customer journeys when it comes to resilience. Things like performance metrics, scalability, peak usage management, and so on. McKinsey wrote years ago, design for the storm, not the sunny days. That is right, but keep the design within the commercial service parameters. It is equally bad to overbuild to a $5 million system, if your expected revenue is less than $100,000 a year, than it is to use a $10,000 system to support a $5 million revenue stream. (I remember the Excel sheet from hell that actually supported a macro-economist at a large brokerage.)
Start mapping your services today. Start with what you feel are the most critical ones. You'll uncover inefficiencies, mitigate risks, and strengthen the very foundation of your customer relationships. You may even save some money.
Don’t wait until the necessity arises to evaluate your networking in the cloud. Get ahead of the curve and choose the topology that optimizes benefits and supports organizational needs in the present and the future.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
What cloud networking topology should you use? How do you provide access to shared resources in the cloud or hybrid infrastructure? What sits in the hub and what sits in the spoke?
Cloud adoption among organizations increases gradually across both the number of services used and the amount those services are used. However, network builders tend to overlook the vulnerabilities of network topologies, which leads to complications down the road, especially since the structures of cloud network topologies are not all of the same quality. A network design that suits current needs may not be the best solution for the future state of the organization.
Even if on-prem network strategies were retained for ease of migration, it is important to evaluate and identify the cloud network topology that can not only elevate the performance of your infrastructure in the cloud, but also that can make it easier to manage and provision resources.
An "as the need arises" strategy will not work efficiently since changing network designs will change the way data travels within your network, which will then need to be adopted to existing application architectures. This becomes more complicated as the number of services hosted in the cloud grows.
Keep a network strategy in place early on and start designing your infrastructure accordingly. This gives you more control over your networks and eliminates the need for huge changes to your infrastructure down the road.
Nitin Mukesh
Senior Research Analyst, Infrastructure and Operations
Info-Tech Research Group
The organization is planning to move resources to the cloud or devise a networking strategy for their existing cloud infrastructure to harness value from the cloud.
The right topology needs to be selected to deploy network level isolation, design the cloud for management efficiencies, and provide access to shared services in the cloud.
A perennial challenge for infrastructure in the cloud is planning for governance vs. flexibility, which is often overlooked.
The choice of migration method may result in retaining existing networking patterns and only making changes when the need arises.
Networking in the cloud is still new, and organizations new to the cloud may not be aware of the cloud network designs they can consider for their business needs.
Define organizational needs and understand the pros and cons of cloud network topologies to strategize for the networking design.
Consider the layered complexities of addressing the governance vs. flexibility spectrum for your domains when designing your networks.
Don't wait until the necessity arises to evaluate your networking in the cloud. Get ahead of the curve and choose the topology that optimizes benefits and supports organizational needs in the present and future.
Selecting the right topology: Many organizations migrate to the cloud retaining a mesh networking topology from their on-prem design, or they choose to implement the mesh design leveraging peering technologies in the cloud without a strategy in place for when business needs change. While there may be many network topologies for on-prem infrastructure, the network design team may not be aware of the best approach in cloud platforms for their requirements, or a cloud networking strategy may even go overlooked during the migration.
Finding the right cloud networking infrastructure for:
Deciding between governance and flexibility in networking design: In the hub and spoke model, if a domain is in the hub, the greater the governance over it, and if it sits in the spoke, the higher the flexibility. Having a strategy for the most important domains is key. For example, some security belongs in the hub and some security belongs in the spoke. The tradeoff here is if it sits completely in the spoke, you give it a lot of freedom, but it becomes harder to standardize across the organization.
A mesh is a design where virtual private clouds (VPCs) are connected to each other individually creating a mesh network. The network traffic is fast and can be redirected since the nodes in the network are interconnected. There is no hierarchical relationship between the networks, and any two networks can connect with each other directly.
In the cloud, this design can be implemented by setting up peering connections between any two VPCs. These VPCs can also be set up to communicate with each other internally through the cloud service provider's network without having to route the traffic via the internet.
While this topology offers high redundancy, the number of connections grows tremendously as more networks are added, making it harder to scale a network using a mesh topology.
Mesh Network on AWS
Source: AWS, 2018
| Number of virtual networks | 10 | 20 | 50 | 100 |
| Peering links required [(n-1)*n]/2 |
45 | 190 | 1225 | 4950 |
Proportional relationship of virtual networks to required peering links in a mesh topology
INDUSTRY: Blockchain
SOURCE: Microsoft
An organization with four members wants to deploy a blockchain in the cloud, with each member running their own virtual network. With only four members on the team, a mesh network can be created in the cloud with each of their networks being connected to each other, adding up to a total of 12 peering connections (four members with three connections each). While the members may all be using different cloud accounts, setting up connections between them will still be possible.
The organization wants to expand to 15 members within the next year, with each new member being connected with their separate virtual networks. Once grown, the organization will have a total of 210 peering connections since each of the virtual networks will then need 14 peering connections. While this may still be possible to deploy, the number of connections makes it harder to manage and would be that much more difficult to deploy if the organization grows to even 30 or 40 members. The new scale of virtual connections calls for an alternative networking strategy that cloud providers offer – the hub and spoke topology.
Source: Microsoft, 2017
In hub and spoke network design, each network is connected to a central network that facilitates intercommunication between the networks. The central network, also called the hub, can be used by multiple workloads/servers/services for hosting services and for managing external connectivity. Other networks connected to the hub through network peering are called spokes and host workloads.
Communications between the workloads/servers/services on spokes pass in or out of the hub where they are inspected and routed. The spokes can also be centrally managed from the hub with IT rules and processes.
A hub and spoke design enable a larger number of virtual networks to be interconnected as each network only needs one peered connection (to the hub) to be able to communicate with any other network in the system.
While there are plenty of benefits to using this topology, there are still a few notable disadvantages with the design.
The total number of total peered connections required might be lower than mesh, but the cost of running independent projects is cheaper on mesh as point-to-point data transfers are cheaper.
With global organizations, implementing a single monolithic hub network for network ingress and egress will slow down access to cloud services that users will require. A distributed network will ramp up the speeds for its users to access these services.
Connectivity between the spokes can fail if the hub site dies or faces major disruptions. While there are redundancy plans for cloud networks, it will be an additional cost to plan and build an environment for it.
Providing access to shared services: Hub and spoke can be used to give workloads that are deployed on different networks access to shared services by placing the shared service in the hub. For example, DNS servers can be placed in the hub network, and production or host networks can be connected to the hub to access it, or if the central network is set up to host Active Directory services, then servers in other networks can act as spokes and have full access to the central VPC to send requests. This is also a great way to separate workloads that do not need to communicate with each other but all need access to the same services.
Adding new locations: An expanding organization that needs to add additional global or domestic locations can leverage hub and spoke to connect new network locations to the main system without the need for multiple connections.
Cost savings: Apart from having fewer connections than mesh that can save costs in the cloud, hub and spoke can also be used to centralize services such as DNS and NAT to be managed in one location rather than having to individually deploy in each network. This can bring down management efforts and costs considerably.
Centralized security: Enterprises can deploy a center of excellence on the hub for security, and the spokes connected to it can leverage a higher level of security and increase resilience. It will also be easier to control and manage network policies and networking resources from the hub.
Network management: Since each spoke is peered only once to the hub, detecting connectivity problems or other network issues is made simpler in hub and spoke than on mesh. A network manager deployed on the cloud can give access to network problems faster than on other topologies.
The advantages of using a hub and spoke model far exceed those of using a mesh topology in the cloud and go to show why most organizations ultimately end up using the hub and spoke as their networking strategy.
However, organizations, especially large ones, are complex entities, and choosing only one model may not serve all business needs. In such cases, a hybrid approach may be the best strategy. The following slides will demonstrate the advantages and use cases for mesh, however limited they might be.
An organization can have multiple network topologies where system X is a mesh and system Y is a hub and spoke. A shared system Z can be a part of both systems depending on the needs.
An organization can have multiple networks interconnected in a mesh and some of the networks in the mesh can be a hub for a hub-spoke network. For example, a business unit that works on data analysis can deploy their services in a spoke that is connected to a central hub that can host shared services such as Active Directory or NAT. The central hub can then be connected to a regional on-prem network where data and other shared services can be hosted.
|
Benefits Of Mesh |
Use Cases For Mesh |
|---|---|
|
Security: Setting up a peering connection between two VPCs comes with the benefit of improving security since the connection can be private between the networks and can isolate public traffic from the internet. The traffic between the networks never has to leave the cloud provider's network, which helps reduce a class of risks. Reduced network costs: Since the peered networks communicate internally through the cloud's internal networks, the data transfer costs are typically cheaper than over the public internet. Communication speed: Improved network latency is a key benefit from using mesh because the peered traffic does not have to go over the public internet but rather the internal network. The network traffic between the connections can also be quickly redirected as needed. Higher flexibility for backend services: Mesh networks can be desirable for back-end services if egress traffic needs to be blocked to the public internet from the deployed services/servers. This also helps avoid having to set up public IP or network address translation (NAT) configurations. |
Connecting two or more networks for full access to resources: For example, consider an organization that has separate networks for each department, which don't all need to communicate with each other. Here, a peering network can be set up only between the networks that need to communicate with full or partial access to each other such as finance to HR or accounting to IT. Specific security or compliance need: Mesh or VPC peering can also come in handy to serve specific security needs or logging needs that require using a network to connect to other networks directly and in private. For example, global organizations that face regulatory requirements of storing or transferring data domestically with private connections. Systems with very few networks that do not need internet access: Workloads deployed in networks that need to communicate with each other but do not require internet access or network address translation (NAT) can be connected using mesh especially when there are security reasons to keep them from being connected to the main system, e.g. backend services such as testing environments, labs, or sandboxes can leverage this design. |
The complexities of designing an organization's networks grow with the organization as it becomes global and takes on more services and lines of business. Organizations that choose to deploy the hub and spoke model face a dilemma in choosing between governance and flexibility for their networks. Organizations need to find that sweet spot to find the right balance between how much they want to govern their systems, mainly for security- and cost-monitoring, and how much flexibility they want to provide for innovation and other operations, since the two usually tend to have an inverse relationship.
This decision in hub and spoke usually means that the domains chosen for higher governance must be placed in the hub network, and the domains that need more flexibility in a spoke. The key variables in the following slide will help determine the placement of the domain and will depend entirely on the organization's context.
The two networking patterns in the cloud have layered complexities that need to be systematically addressed.
If a network has more flexibility in all or most of these domains, it may be a good candidate for a spoke-heavy design; otherwise, it may be better designed in a hub-centric pattern.
Resources that are shared between multiple projects or departments or even by the entire organization should be hosted on the hub network to simplify sharing these services. For example, e-learning applications that may be used by multiple business units to train their teams, Active Directory accessed by most teams, or even SAAS platforms such as O365 and Salesforce can leverage buying power and drive down the costs for the organization. Shared services should also be standardized across the organization and for that, it needs to have high governance.
Services that are an individual need for a network and have no preexisting relationship with other networks or buying power and scale can be hosted in a spoke network. For example, specialized accounting software used exclusively by the accounting team or design software used by a single team. Although the services are still a part of the wider network, it helps separate duties from the shared services network and provides flexibility to the teams to customize and manage their services to suit their individual needs.
Network connections, be they in the cloud or hybrid-cloud, are used by everyone to either connect to the internet, access cloud services, or access the organization's data center. Since this is a shared service, a centralized networking account must be placed in the hub for greater governance. Interactions between the spokes in a hub and spoke model happens through the hub, and providing internet access to the spokes through the hub can help leverage cost benefits in the cloud. The network account will perform routing duties between the spokes, on-prem assets, and egress out to the internet.
For example, NAT gateways in the cloud that are managed services are usually charged by the hour, and deploying NAT on each spoke can be harder to manage and expensive to maintain. A NAT gateway deployed in a central networking hub can be accessed by all spokes, so centralizing it is a great option.
Note that, in some cases, when using edge locations for data transfers, it may be cost effective to deploy a NAT in the spoke, but such cases usually do not apply to most organizational units.
A centralized network hub can also be useful to configure network policies and network resources while organizational departments can configure non-network resources, which helps separate responsibilities for all the spokes in the system. For example, subnets and routes can be controlled from the central network hub to ensure standardized network policies across the network.
While there needs to be security in the hub and the spokes individually, finding the balance of operation can make the systems more robust. Hub and spoke design can be an effective tool for security when a principal security hub is hosted in the hub network. The central security hub can collect data from the spokes as well as non-spoke sources such as regulatory bodies and threat intelligence providers, and then share the information with the spokes.
Threat information sharing is a major benefit of using this design, and the hub can take actions to analyze and enrich the data before sharing it with spokes. Shared services such as threat intelligence platforms (TIP) can also benefit from being centralized when stationed in the hub. A collective defense approach between the hub and spoke can be very successful in addressing sophisticated threats.
Compliance and regulatory requirements such as HIPAA can also be placed in the hub, and the spokes connected to it can make use of it instead of having to deploy it in each spoke individually.
The governance vs. flexibility paradigm usually decides the placement of cloud metering, i.e. if the organization wants higher control over cloud costs, it should be in the central hub, whereas if it prioritizes innovation, the spokes should be allowed to control it. Regardless of the placement of the domain, the costs can be monitored from the central hub using cloud-native monitoring tools such as Azure Monitor or any third-party software deployed in the hub.
For ease of governance and since resources are usually shared at a project level, most cloud service providers suggest that an individual metering service be placed in the spokes. The centralized billing system of the organization, however, can make use of scale and reserved instances to drive down the costs that the spokes can take advantage of. For example, billing and access control resources are placed in the lower levels in GCP to enable users to set up projects and perform their tasks. These billing systems in the lower levels are then controlled by a centralized billing system to decide who pays for the resources provisioned.

Borschel, Brett. "Azure Hub Spoke Virtual Network Design Best Practices." Acendri Solutions, 13 Jan. 2022. Web.
Singh, Garvit. "Amazon Virtual Private Cloud Connectivity Options." AWS, January 2018. Web.
"What Is the Hub and Spoke Information Sharing Model?" Cyware, 16 Aug. 2021. Web.
Youseff, Lamia. "Mesh and Hub-and-Spoke Networks on Azure." Microsoft, Dec. 2017. Web.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Understand your applications team.
Understand your stakeholders.
Design and plan your applications 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.
Understand the expectations, structure, and dynamics of your applications team.
Review your team’s current capacity.
Gauge the team’s effectiveness to execute their operating model.
Clear understanding of the current responsibilities and accountabilities of your teams.
Identification of improvement opportunities based on your team’s performance.
1.1 Define your team’s role and responsibilities.
1.2 Understand your team’s application and project portfolios.
1.3 Understand your team’s values and expectations.
1.4 Gauge your team’s ability to execute your operating model.
Current team structure, RACI chart, and operating model
Application portfolios currently managed by applications team and projects currently committed to
List of current guiding principles and team expectations
Team effectiveness of current operating model
Understand the expectations of stakeholders.
Review the services stakeholders consume to support their applications.
Gauge stakeholder satisfaction of the services and applications your team provides and supports.
Grounded understanding of the drivers and motivators of stakeholders that teams should accommodate.
Identification of improvement opportunities that will increase the value your team delivers to stakeholders.
2.1 Understand your stakeholders and applications services.
2.2 Define stakeholder expectations.
2.3 Gauge stakeholder satisfaction of applications services and portfolio.
Expectations stakeholders have on the applications team and the applications services they use
List of applications expectations
Stakeholder satisfaction of current operating model
Align and consolidate a single set of applications expectations.
Develop key initiatives to alleviate current pain points and exploit existing opportunities to deliver new value.
Create an achievable roadmap that is aligned to organizational priorities and accommodate existing constraints.
Applications team and stakeholders are aligned on the core focus of the applications department.
Initiatives to address the high priority issues and opportunities.
3.1 Define your applications expectations.
3.2 Investigate your diagnostic results.
3.3 Envision your future state.
3.4 Create a tactical plan to achieve your future state.
3.5 Finalize your applications strategy.
List of applications expectations that accommodates the team and stakeholder needs
Root causes to issues and opportunities revealed in team and stakeholder assessments
Future-state applications portfolio, operating model, supporting people, process, and technologies, and applications strategic model
Roadmap that lays out initiatives to achieve the future state
Completed applications strategy
You have made significant investments in availability and disaster recovery – but your ability to recover hasn’t been tested in years. Testing will:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Use this research to understand the different types of tests, prioritize and plan tests for your organization, review the results, and establish a cadence for testing.
Use this template to document scope and goals, participants, key pre-test milestones, the test-day schedule, and your findings from the testing exercise.
Identify the tests you will run over the next year and the expertise, governance, process, and funding required to support testing.
[infographic]

Most businesses make significant investments in disaster recovery and technology resilience. Redundant sites and systems, monitoring, intrusion prevention, backups, training, documentation: it all costs time and money.
But does this investment deliver expected value? Specifically, can you deliver service continuity in a way that meets business requirements?
You can’t know the answer without regularly testing recovery processes and systems. And more than just validation, testing helps you deliver service continuity by finding and addressing gaps in your plans and training your staff on recovery procedures.
Use the insights, tools, and templates in this research to create a streamlined and effective resilience testing program that helps validate recovery capabilities and enhance service reliability, availability, and continuity.
Research Director, Infrastructure & Operations
Info-Tech Research Group
Your ChallengeYou have made significant investments in availability and disaster recovery (DR) – but your ability to recover hasn’t been tested in years. Testing will:
|
Common ObstaclesDespite the value testing can offer, actually executing on DR tests is difficult because:
|
Info-Tech's ApproachTake a realistic approach to resilience testing by starting with small, low-risk tests, then iterating with the lessons you’ve learned:
|
If you treat testing as a pass/fail exercise, you aren’t meeting the end goal of improving organizational resilience. Focus on identifying gaps and risks so you can address them before a real disaster hits.
This research is accompanied by templates to help you achieve your goals faster.
1 - Establish the business rationale for DR testing.
2 - Review a range of options for testing.
3 - Prioritize tests that are most valuable to your business.
4 - Create a disaster recovery test plan.
5 - Establish a Test Program to support a regular testing cycle.
Orange activity slides like the one on the left provide directions to help you make key decisions.
Disaster Recovery Test Plan Template
Build a plan for your first disaster recovery test.
This document provides a complete example you can use to quickly build your own plan, including goals, milestones, participants, the test-day schedule, and findings from the after-action review.
“Routine testing is vital to survive a disaster… that’s when muscle memory sets in. If you don’t test your DR plan it falls [in importance], and you never see how routine changes impact it.”
– Jennifer Goshorn
Chief Administrative Officer
Gunderson Dettmer LLP
Info-Tech members estimated even one day of system downtime could lead to significant revenue losses. 
Average estimated potential loss* in thousands of USD due to a 24-hour outage (N=41)
*Data aggregated from 41 business impact analyses (BIAs) conducted with Info-Tech advisory assistance. BIAs evaluate potential revenue loss due to a full day of system downtime, at the worst possible time.

30 minutes
Identify a group of participants who can fill the following roles and inform the discussions around testing in this research. A single person could fill multiple roles and some roles could be filled by multiple people. Many participants will be drawn from the larger DRP team.
Input
|
Output
|
Participants
|
Use Info-Tech’s Create a Right-Sized Disaster Recovery Plan research to identify recovery objectives based on business impact and outline recovery processes. Both are tremendously valuable inputs to your test plans.
IT Disaster Recovery PlanA plan to restore IT services (e.g. applications and infrastructure) following a disruption. A DRP:
|
BCP for Each Business UnitA set of plans to resume business processes for each business unit. A business continuity plan (BCP) is also sometimes called a continuity of operations plan (COOP). BCPs are created and owned by each business unit, and creating a BCP requires deep involvement from the leadership of 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. |
Crisis Management PlanA plan to manage a wide range of crises, from health and safety incidents to business disruptions to reputational damage. Info-Tech’s Implement Crisis Management Best Practices blueprint provides a framework for planning a response to any crisis, from health and safety incidents to reputational damage. |
15-30 minutes
Identify the value recovery testing for your organization. Use language appropriate for a nontechnical audience. Start with the list below and add, modify, or delete bullet points to reflect your own organization.
Drivers for testing – Examples:
Time-strapped technical staff will sometimes push back on planning and testing, objecting that the team will “figure it out” in a disaster. But the question isn’t whether recovery is possible – it’s whether the recovery aligns with business needs. If your plan is to “MacGyver” a solution on the fly, you can’t know if it’s the right solution for your organization.
Input
|
Output
|
Participants
|

In a tabletop planning exercise, the team walks through a disaster scenario to outline the recovery workflow, and risks or gaps that could disrupt that workflow.
Tabletops are particularly effective because:
2 hours
Tabletop testing is part of our core DRP methodology, Create a Right-Sized Disaster Recovery Plan. This exercise can be run using cue cards, sticky notes, or on a whiteboard; many of our facilitators find building the workflow directly in flowchart software to be very effective.
Use our Recovery Workflow Template as a starting point.
Some tips for running your first tabletop exercise:
Do
|
Don't
|
Input
|
Output
|
Participants
|
In live exercises, some portion of your recovery plans are executed in a way that mimics a real recovery scenario. Some advantages of live testing:
| Boot and smoke test | Turn on a standby system and confirm it boots up correctly. |
| Restore and validate data | Restore data or servers from backup. Confirm data integrity. |
| Parallel testing | Send familiar transactions to production and standby systems. Confirm both systems produce the same result. |
| Failover systems | Shut down the production system and use the standby system in production. |
Most unacceptable downtime is caused by localized issues, such as hardware or software failures, rather than widespread destructive events. Regular local testing can help validate the recovery plan for local issues and improve overall service continuity.
Make local testing a standard step in maintenance work and new deployments to embed resilience considerations in day-to-day activities. Run the same tests in both your primary and your DR environment.
Some examples of localized tests:
Local tests will vary between different services, and local test design is usually best left to the system SMEs. At the same time, centralize reporting to understand where tests are being done.
Investigate whether your IT Service Management or ticketing system can create recurring tasks or work orders to schedule, document, and track test exercises. Tasks can be pre-populated with checklists and documentation to support the test and provide a record of completed tests to support oversight and reporting.
User acceptance testing (UAT) after system recovery is a key step in the recovery process. Like any step in the process, there’s value in testing it before it actually needs to be done. Assign responsibility for building UATs to the person who will be responsible for executing them.
An acceptance test script might look something like the checklist below.
“I cannot stress how important it is to assign ownership of responsibilities in a test; this is the only way to truly mitigate against issues in a test.”
– Robert Nardella
IT Service Management
Certified z/OS Mainframe Professional
Build test scripts and test transactions ahead of time to minimize the amount of new work required during a recovery scenario.
What you get:
What you need:
What you get:
What you need:
What you get:
What you need:
What you get:
What you need:
More complex, challenging, risky, or costly tests, such as full failover tests, can deliver value. But do the high-value, low-effort stuff first!
30-60 minutes
Even if you have an idea of what you need to test and how you want to run those tests, this brainstorming exercise can generate useful ideas for testing that might otherwise have been missed.
The next steps will help you prioritize the list – if needed – to tests that are highest value and lowest effort.
“There are different levels of testing and it is very progressive. I do not recommend my clients to do anything, unless they do it in a progressive fashion. Don’t try to do a live failover test with your users, right out of the box.”
– Steve Tower
Principal Consultant
Prompta Consulting Group
Input
|
Output
|
Participants
|
3-5 days
Building a test plan helps the test run smoothly and can uncover issues with the underlying DRP as you dig into the details.
The test coordinator will own the plan document but will rely on the sponsor to confirm scope and goals, technical SMEs to develop system recovery plans, and business liaisons to create UAT scripts.
Download Info-Tech’s Disaster Recovery Test Plan Template. Use the structure of the template to build your own document, deleting example data as you go. Consider saving a separate copy of this document as an example and working from a second copy.
Key sections of the document include:
Download the Disaster Recovery Test Plan Template
Input
|
Output
|
Participants
|
30-60 minutes
Take time after test exercises – especially large-scale tests with many participants – to consider what went well, what didn’t, and where you can improve future testing exercises. Track lessons learned and next steps at the bottom of your test plan.
Input
|
Output
|
Participants
|
All tests are expected to drive actions to improve resilience, as appropriate. Experience from previous tests will be applied to future testing exercises.

Outputs and lessons learned from testing should help you run future tests.

Testing should get easier over time. But if you’re easily passing every test, it’s a sign that you’re ready to run more challenging tests.
2-4 hours
Regular testing allows you to build on prior tests and helps keep plans current despite changes to your environment.
Keeping a regular testing schedule requires expertise, a process to coordinate your efforts, and a level of governance to provide oversight and ensure testing continues to deliver value. Create a call to action using Info-Tech’s Disaster Recovery Testing Program Summary Template.
The result is a summary document that:
“It is extremely important in the early stages of development to concentrate the focus on actual recoverability and data protection, enhancing these capabilities over time into a fully matured program that can truly test the recovery, and not simply focusing on the testing process itself.”
– Joe Starzyk
Senior Business Development Executive
IBM Global Services
Alton, Yoni. “Ransomware simulators – reality or a bluff?” Palo Alto Blog, 2 May 2022. Accessed 31 Jan 2023.
https://www.paloaltonetworks.com/blog/security-operations/ransomware-simulators-reality-or-a-bluff/
Brathwaite, Shimon. “How to Test your Business Continuity and Disaster Recovery Plan,” Security Made Simple, 13 Nov 2022. Accessed 31 Jan 2023.
https://www.securitymadesimple.org/cybersecurity-blog/how-to-test-your-business-continuity-and-disaster-recovery-plan
The Business Continuity Institute. Good Practice Guidelines: 2018 Edition. The Business Continuity Institute, 2017.
Emigh, Jacqueline. “Disaster Recovery Testing: Ensuring Your DR Plan Works,” Enterprise Storage Forum, 28 May 2019. Accessed 31 Jan 2023.
Disaster Recovery Testing: Ensuring Your DR Plan Works | Enterprise Storage Forum
Gardner, Dana. "Case Study: Strategic Approach to Disaster Recovery and Data Lifecycle Management Pays off for Australia's SAI Global." ZDNet. BriefingsDirect, 26 Apr 2012. Accessed 31 Jan 2023.
http://www.zdnet.com/article/case-study-strategic-approach-to-disaster-recovery-and-data-lifecycle-management-pays-off-for-australias-sai-global/.
IBM. “Section 11. Testing the Disaster Recovery Plan.” IBM, 2 Aug 2021. Accessed 31 Jan 2023. Section 11. Testing the disaster recovery plan - IBM Documentation Lutkevich, Ben and Alexander Gillis. “Chaos Engineering”. TechTarget, Jun 2021. Accessed 31 Jan 2023.
https://www.techtarget.com/searchitoperations/definition/chaos-engineering
Monperrus, Martin. “Principles of Antifragility.” Arxiv Forum, 7 June 2017. Accessed 31 Jan 2023.
https://arxiv.org/ftp/arxiv/papers/1404/1404.3056.pdf
“Principles of Chaos Engineering.” Principles of Chaos Engineering, 2019 March. Accessed 31 Jan 2023.
https://principlesofchaos.org/
Sloss, Benjamin Treynor. “Introduction.” Site Reliability Engineering. Ed. Betsy Beyer. O’Reilly Media, 2017. Accessed 31 Jan 2023.
https://sre.google/sre-book/introduction/
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
This storyboard will help you understand the spectrum of different Agile xOps working modes and how best to leverage them and build an architecture and toolset that support rapid continuous IT operations
IT Operations continue to be challenged by increasing needs for scale and speed, often in the face of constrained resources and time. For most, Agile methodologies have become a foundational part of tackling this problem. Since then, we've seen Agile evolve into DevOps, which started a trend into different categories of "xOps" that are too many to count. How does one make sense of the xOps spectrum? What is InfraOps and where does it fit in?
Ultimately, all these methodologies and approaches are there to serve the same purpose: increase effectiveness through automation and improve governance through visibility. The key is to understand what tools and methodologies will deliver actual benefits to your IT operation and to the organization as a whole.
By defining your end goals and framing solutions based on the type of visibility and features you need, you can enable speed and reliability without losing control of the work.
InfraOps, when applied well, should be the embodiment of the governance policies as expressed by standards in architecture and automation.
|
Understand the xOps spectrum |
There are as many different types of "xOps" as there are business models and IT teams. To pick the approaches that deliver the best value to your organization and that align to your way of operating, it's important to understand the different major categories in the spectrum and how they do or don't apply to your IT approach. |
|---|---|
|
How to optimize the Ops in DevOps |
InfraOps is one of the major methodologies to address a key problem in IT at cloud scale: eliminating friction and error from your deliveries and outputs. The good news is there are architectures, tools, and frameworks you can easily leverage to make adopting this approach easier. |
|
Evolve to integration and build a virtuous cycle |
Ultimately your DevOps and InfraOps approaches should embody your governance needs via architecture and process. As time goes on, however, both your IT footprint and your business environment will shift. Build your tools, telemetry, and governance to anticipate and adapt to change and build a virtuous cycle between development needs and IT Operations tools and governance. |
There is no definitive list of x's in the xOps spectrum. Different organizations and teams will divide and define these in different ways. In many cases, the definitions and domains of various xOps will overlap.
Some of the commonly adopted and defined xOps models are listed here.
Shifting left or right isn't an either/or choice. They're more like opposite sides of the same coin. Like the different xOps approaches, usually more than one shift approach will apply to your IT Operations.
With the shift from execution to governing and validating, the role of deployment falls downstream of IT Operations.
IT Operations needs to move to a mindset that focuses on creating the guardrails, enforced standards, and compliance rules that need to be used downstream, then apply those standards using automation and tooling to remove friction and error from the interstitia (the white spaces between chevrons) of the various phases.
Your tools can be broken into two categories:
Keep in mind that while your infrastructure architecture is usually an either/or choice, your automation approach should use any and all tooling that helps.
Hyperconvergence is the next phase of convergence, virtualizing servers, networks, and storage on a single server/storage appliance. Capacity scales as more appliances are added to a cluster or stack.
The disruptive departure:
HCI follows convergence trends of the past ten years but is also a departure from how IT infrastructure has traditionally been provisioned and managed.
HCI is at the same time a logical progression of infrastructure convergence and a disruptive departure.
HCI can be the foundation block for a fully software defined data center, a prerequisite for private cloud.
Key attributes of a cloud are automation, resource elasticity, and self-service. This kind of agility is impossible if physical infrastructure needs intervention.
Virtualization alone does not a private cloud make, but complete stack virtualization (software defined) running on a hands-off preconfigured HCI appliance (or group of appliances) provides a solid foundation for building cloud services.
Silo-busting and private cloud sound great, but are your people and processes able to manage the change?
In traditional infrastructure, performance and capacity are managed as distinct though complementary jobs. An all-in-one approach may not work.
Use Case Example: Composable AI flow
Data Ingestion > Data Cleaning/Tagging > Training > Conclusion
Where it's useful
Considerations
Many organizations using a traditional approach report resource stranding as having an impact of 20% or more on efficiency. When focusing specifically on the stranding of memory in workloads, the number can often approach 40%.
Infrastructure as code (IaC) is the process of managing and provisioning computer data centers through machine-readable definition files rather than physical hardware configuration or interactive configuration tools.
Before IaC, IT personnel would have to manually change configurations to manage their infrastructure. Maybe they would use throwaway scripts to automate some tasks, but that was the extent of it.
With IaC, your infrastructure's configuration takes the form of a code file, making it easy to edit, copy, and distribute.
Orchestration describes the automated arrangement, coordination, and management of complex computer systems, middleware, and services.
This usage of orchestration is often discussed in the context of service-oriented architecture, virtualization, provisioning, converged infrastructure, and dynamic data center topics. Orchestration in this sense is about aligning the business request with the applications, data, and infrastructure.
It defines the policies and service levels through automated workflows,
provisioning, and change management. This creates an application-aligned infrastructure that can be scaled up or down based on the needs of each application.
As the requirement for more resources or a new application is triggered, automated tools now can perform tasks that previously could only be done by multiple administrators operating on their individual pieces of the physical stack.
Orchestration also provides centralized management of the resource pool, including billing, metering, and chargeback for consumption. For example, orchestration reduces the time and effort for deploying multiple instances of a single application.
Automation and orchestration tools can be key components of an effective governance toolkit too! Remember to understand what data can be pulled from your various tools and leveraged for other purposes such as cost management and portfolio roadmapping.
Configuration Management
|
Configuration Management |
|
|---|---|
|
CI/CD |
|
|
Container |
|
|
Cloud-Specific |
|
|
PaaS |
Automation and orchestration tools and software offerings are plentiful, and many of them have a different focus on where in the application delivery ecosystem they provide automation functionality.
Often there are different tools for different deployment and service models as well as for different functional phases for each service model.
Let the large ecosystem of tools be your ally. Leverage the right tools where needed and then address the complexity of tools using a master orchestration scheme.
Additionally, most tools do not cover all aspects required for most automation implementations, especially in hybrid cloud scenarios.
As such, often multiple tools must be deployed, which can lead to fragmentation and loss of unified controls.
Many enterprises address this fragmentation using a cloud management platform approach.
One method of achieving this is to establish a higher layer of orchestration – an "orchestrator of orchestrators," or metaorchestration.
In complex scenarios, this can be a challenge that requires customization and development.
| Toolkit | Pros | Cons | Tips |
|---|---|---|---|
| HCI | Easy scale out | Shift in skills required | Good for enabling automation and hybridization with current-gen public cloud services |
| CI | Maximal workload resource efficiency | Investment in new fabrics and technologies | Useful for very dynamic or highly scalable workloads like AI |
| IaC | Error reduction and standardization | Managing drift in standards and requirements | Leverage a standards and exception process to keep track of drift |
| A&O | Key enabler of DevOps automation within phases | Usually requires multiple toolsets/frameworks | Use the right tools and stitch together at the metaorchestration layer |
| Metaorchestration | Reduces the complexity of a diverse A&O and IaC toolkit | Requires understanding of the entire ecosystems of tools used | Key layer of visibility and control for governance |
Remember, the goal is to increase speed AND reliability. That's why we focus on removing friction from our delivery pipelines.
Remember that, especially in modern and rapid methodologies, your IT footprint can drift unexpectedly. This means you need a real feedback mechanism on where the friction moves to next.
This is particularly important in more Agile methodologies.
| Plan | Code | Test | Deploy | Monitor | |
|---|---|---|---|---|---|
| Incoming Friction | |||||
| In-Cycle Friction | |||||
| Outgoing Friction |
Map your ops groups to the delivery cycles in your pipeline. How many delivery cycles do you have or need?
Good InfraOps is a reflection of governance policies, expressed by standards in architecture and automation.
Evaluate Hyperconverged Infrastructure for Your Infrastructure Roadmap
Banks, Ethan, host. "Choosing Your Next Infrastructure." Datanauts, episode 094, Packet Pushers, 26 July 2017. Podcast.
"Composable Infrastructure Solutions." Hewlett Packard Canada, n.d. Web.
"Composable Infrastructure Technology." Liqid Inc., n.d. Web.
"DataOps architecture design." Azure Architecture Center, Microsoft Learn, n.d. Web.
Tan, Pei Send. "Differences: DevOps, ITOps, MLOps, DataOps, ModelOps, AIOps, SecOps, DevSecOps." Medium, 5 July 2021. Web.
IT communications are often considered ineffective and unengaging. This is demonstrated by the:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
This blueprint not only provides the tools and techniques for planning, composing, and delivering effective communications, but also walks you through practical exercises. Practice and perfect your communication, composition, and delivery skills for any IT initiative.
Communication concepts and exercises that teach you how to plan, compose, and deliver effective communications. The deck includes practical tools, techniques, and skills practice.
This communications planner is a tool that accompanies the Effective IT Communications blueprint and the Communicate Any IT Initiative Facilitation Deck so that you can plan your communications, view your deliverables, and compose your pitch all in one document.
A tool for identifying stakeholders and conducting an analysis to understand their degree of influence or impact.
| Your Challenge | Common Obstacles | Info-Tech’s Approach |
Communicating about your initiative is when the work really begins. Many organizations struggle with:
|
Some of the challenges IT faces when it comes to communicating its initiatives includes:
|
For every IT initiative you have going forward, focus on following these three steps:
|
Info-Tech Insight
Every IT employee can be a great communicator; it just takes a few consistent steps, the right tools, and a dedication to practicing communicating your message.
The Info-Tech difference:
27.8% of organizations are not satisfied with IT communications.
25.8% of business stakeholders are not satisfied with IT communications.
Source: Info-Tech Diagnostic Programs; n=34,345 business stakeholders within 604 organizations
The bottom line? Stakeholders for any initiative need to be communicated with often and well. When stakeholders become dissatisfied with IT’s communication, it can lead to an overall decrease in satisfaction with IT.
“Nothing gets done properly if it's not communicated well.”
-- Nastaran Bisheban, CTO KFC Canada
Introduction
Review effective communications.
Plan
Plan your communications using a strategic tool.
Compose
Create your own message.
Deliver
Practice delivering your own message.
| 1. Plan Strategic Communications | 2. Compose a Compelling Message | 3. Deliver Messages Effectively | |
|---|---|---|---|
| Step Activities |
|
|
|
| Step Outcomes | Establish an easy-to-read view of the key communications that need to take place related to your initiative or change. | Practice writing a pitch that conveys the message in a compelling and easy-to-understand way. | Practice delivering the pitch. Ensure there is authenticity in the delivery while still maintaining the audience’s attention. |
We recommend considering this blueprint a natural add-on to any completed Info-Tech blueprint, whether it is completed in the DIY fashion or through a Guided Implementation or workshop.
Communication Planner
A single place to plan and compose all communications related to your IT initiative.
Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals.
Facilitation Guide
A step-by-step guide to help your IT organization develop a communication plan and practice composing and delivering key messages.
Stakeholder Analysis
An ability to assess all stakeholders based on impact, influence, and involvement.
| Morning | Afternoon | |
|---|---|---|
| Activities | Plan Strategic Communications for Your Initiative
| Compose and Deliver a Compelling Message
|
| Deliverables |
|
|
Contact your account representative for more information.
workshops@infotech.com 1-888-670-8889
| Goal | Key Performance Indicator (KPI) | Related Resource |
| Obtain board buy-in for IT strategic initiatives. | X% of IT initiatives that were approved to be funded. Number of times that technical initiatives were asked to be explained further. |
Using our Board Presentation Review |
| Ensure stakeholders feel engaged during initiatives. | X% of business leadership satisfied with the statement “IT communicates with your group effectively.” | Using the CIO Business Vision Diagnostic |
| End users know what IT initiatives are going to impact the products or services they use. | X% of end users that are satisfied with communications around changing services or applications. | Using the End-User Satisfaction Survey |
| Project stakeholders receive sufficient communication throughout the initiative. | X% overall satisfaction with the quality of the project communications. | Using the PPM Customer Satisfaction Diagnostic |
| Employees are empowered to perform on IT initiatives. | X% satisfaction employees have with statement “I have all the resources and information I need to do a great job.” | Using the Employee Engagement Diagnostic Program |
Activities
1.1 Define the Change
1.2 Determine Target Audience
1.3 Communication Outcomes
1.4 Clarify the Key Message(s)
1.5 Identify the Owner and Messenger(s)
1.6 Select the Right Channels
1.7 Establish a Frequency and Time Frame
1.8 Obtain Feedback and Improve
1.9 Finalize the Calendar
Communicate Any IT Initiative Effectively
Phase1 > Phase 2 > Phase 3
This step involves the following participants:
Varies based on those who would be relevant to your initiative.
Outcomes of this step
Create an easy-to-follow communications plan to ensure that the right message is sent to the right audience using the right medium and frequency.
Incremental Change:
|
Transitional Change:
|
Transformational Change:
|
Examples:
|
Examples:
|
Examples:
|
Invest time at the start of the project to develop a detailed understanding of the impact of the change. This will help to create a plan that will simplify the change and save time in the end. Evaluate the impact from a people, process, and technology perspective.
Leverage a design thinking principle: Empathize with the stakeholder – what will change?
People
Process
Technology
30 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
Audience
Stakeholders (either groups or individuals) who will receive the communication.
Message
Information communicated to impacted stakeholders. Must be rooted in a purpose or intent.
Messenger
Person who delivers the communication to the audience. The communicator and owner are two different things.
Channel
Method or channel used to communicate to the audience.
The target audience always includes groups and individuals who are directly impacted by the change and may also include those who are change adjacent.
Define the target audience: Identify which stakeholders will be the target audience of communications related to the initiative. Stakeholders can be single individuals (CFO) or groups (Applications Team).
Stakeholders to consider:
20 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
1 hour
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Stakeholder Management Analysis Tool
For each target audience, there will be an overall goal on why they need to be communicated with. This outcome or purpose is often dependent on the type of influence the stakeholder wields within the organization as well as the type of impact the change or initiative will have. Depending on the target audience, consider each of the communication outcomes listed below.
| Communicating Across the Organization | Communicating Up to Board or Executives | Communicating Within IT |
|---|---|---|
|
|
|
30 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
| What are key messages? |
|
| How to establish key messages: | Ground key messages in organizational strategy and culture. These should be the first places you look to determine the organization’s key messages:
|
Key messages should be clear, concise, and consistent (Porter, 2014). The intent is to convey important information in a way that is relatable and memorable, to promote reinforcement, and ultimately, to drive action.
Info-Tech Insight
Empathizing with the audience is key to anticipating and addressing objections as well as identifying benefits. Customize messaging based on audience attributes such as work model (e.g. hybrid), anticipated objections, what's in it for me? (WIIFM), and specific expectations.
25 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
Messages must be communicated by a variety of individuals across the organization. Select the messenger depending on the message characteristics (e.g. audience, message, medium). The same messenger can be used for a variety of messages across different mediums.
Personal impact messages should be delivered by an employee's direct supervisor.
Organizational impact messages and rationale should be delivered by senior leaders in the affected areas.
Recent research by Prosci found employees prefer to hear personal messages from their direct manager and organizational messages from the executive leadership team.
Fifty percent of respondents indicated the CEO as the preferred messenger for organizational change messages.
For each audience, message, and medium, review whether the message is personal or organizational to determine which messengers are best.
The number and seniority of messengers involved depends on the size of the change:
Communication Owner
Single person
Accountable for the communication message and activities
Oversees that the communication does not contradict other communications
Validates the key messages to be made
Communication Messenger(s)
Single person or many people
Responsible for delivering the intended message
Engages the target audience in the communication
Ensures the key messages are made in a consistent and clear manner
30 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
| First question: Should the communication be delivered in-person or not? | ||
|---|---|---|
| Types of channels | In-Person | Paper-Based or Tech-Enabled |
| Questions to consider |
|
|
| Two-way interaction | Supplement in-person communications with paper-based or tech-enabled communications to provide follow-up and consistency (Government of Nova Scotia). | Tech-enabled communications allow the sender to deliver messages when they do not co-locate with the receiver. That said, make sure paper-based communications are provided to those without regular access to a computer. |
Consider accessibility when communicating change – not all employees will have access to the same mediums. To ensure inclusivity, strategically plan which mediums to use to reach the entire audience.
| Medium | Description | Key Messages | When to Use |
|---|---|---|---|
| One-on-One Meetings | Individual meetings between managers and their direct reports to ensure they understand the change, can express any concerns, and obtain feedback or recommendations. |
|
|
| Team Meeting | A meeting of a work unit or department. Can be virtual, in person, or a combination. Led by the work unit or department head/manager. |
|
|
| Electronic communication sent to the audience’s company emails, or in the absence of that, to their personal emails. |
|
|
| Medium | Description | Key Messages | When to Use |
|---|---|---|---|
| Town Hall | Virtual or in-person meeting where senior leadership shares information with a wide audience about the change and answers questions. |
|
|
| Roadshow | A series of meetings where senior leadership or the change champion travels to different geographic locations to hold town halls adapted to each location’s audience. |
|
|
| Medium | Description | Key Messages | When to Use |
|---|---|---|---|
| Intranet | An internal company website that a large number of employees can access at any time. |
|
|
| Training | Scheduled blocks of time for the team to learn new skills and behaviors needed to successfully adapt to the change. |
|
|
| Video Message | A prerecorded short video clip designed for either simultaneous broadcast or just-in-time viewing. Can be sent over email or mobile or uploaded to a company portal/intranet. |
|
|
| Medium | Description | Key Messages | When to Use |
|---|---|---|---|
| Shift Turnover Meeting | A meeting between teams or departments when a shift changes over; sometimes called a shift report. Used to communicate any relevant information from the outgoing shift to the incoming shift members. |
|
|
| Company Newsletter | Electronic or hardcopy newsletter published by the company. Contains timely updates on company information. |
|
|
| Sign/Poster | Digital or paper-based sign, graphic, or image. Includes posters, screensavers, etc. |
|
|
20 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
| 01 Identify and prioritize | 02 Prepare for initiative | 03 Create a communication plan | 04 Implement change | 05 Sustain the desired outcome |
|---|---|---|---|---|
| Before | During | After | ||
|
|
|
|
|
| Where communication needs to happen | ||||
Don’t forget: Cascade messages down through the organization to ensure those who need to deliver messages have time to internalize the change before communicating it to others. Include a mix of personal and organizational messages, but where possible, separate personal and organizational content into different communications.
“When goals are talked about weekly, teams are nearly 3X more likely to feel confident hitting them.”
– Hypercontext, 2022
Info-Tech Insight
Communications made once will always fail. Ensure there is a frequency appropriate for every communication — or do not expect the desired outcome.
30 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
Prior to the strategy rollout, make sure you have also established feedback mechanisms to collect feedback on both the messages delivered and how they were delivered. Some ways to collect feedback include:
Feedback Mechanisms:
There are two types of metrics that can be used to measure the impact of an internal communications strategy and progress toward strategy goals. These metrics are used to measure both outputs and outcomes.
| Select metrics measuring both: | |
|---|---|
| Tactical Effectiveness (Outputs) | Strategic Effectiveness (Outcomes) |
|
|
20 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
2 hours
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
Activities
2.1 Craft a Pitch
2.2 Revise the Pitch
This step involves the following participants:
Varies based on those who would be relevant to your initiative.
Outcomes of this step
Ability to create a clear, concise, and consistent message using best practices and a pitch framework.
Communication Any IT Initiative Effectively
Phase 1 > Phase 2 > Phase 3
Info-Tech Insight
Time is a non-renewable resource. The message crafted must be considered a value-add communication to your audience.
| Be Consistent | Be Clear |
|---|---|
|
|
| Be Relevant | Be Concise |
|
|
Draft core messages communicating information consistent with the high-level communications plan. This includes the overall goal of communications, key messaging, specifics related to the change action, and customizations for each audience. It’s also important to:
| Key Components of a Good Pitch | |
| Purpose of the pitch | What are you asking for? What is the desired outcome of the conversation? What three things do you want the audience to take away? |
| Speak to what matters to them | Who is your audience and what are their biggest challenges today? What do they care? What is the “so what”? Humanize it. Start with an example of a real person. |
| Sell the improvement | How is your solution going to solve that problem? Is your solution a pain killer or vitamin? |
| Show real value | How will your solution create real value? How can that be measured? Give an example. |
| Discuss potential fears | Identify and alleviate fears the stakeholder may have in working with you. Think about what they think now and what you want them to think. |
| Have a call to action | Identify what your ask is. What are you looking for from the stakeholder? Listen and respond. |
| Follow up with a thank-you | Did you ensure that the participants’ time was respected and appreciated? Be genuine and sincere. |
To effectively communicate change, answer questions before they’re asked, whenever possible. To do this, outline at each stage of the change process what’s happening next for the audience and answer other anticipated questions. Pair key questions with core messages in change communications.
Examples of key questions by change stage include:
| What is changing? When is the change expected? Who will be championing the change? What are the change expectations? Will I have input into how the change is happening? What’s happening next? |
Why are we changing? Why is the change happening now? What are the risks of not changing? What will be new? What’s in it for me? What training will be available? Who will be impacted? How will I be impacted? How will my team be impacted? What’s happening next? |
Who should I contact with questions or concerns? How will I be updated? How can I access more information? Will the previous process be available throughout the new process implementation? What needs to be done and what needs to stop to succeed? Will I be measured on this change? What’s happening next? |
How can I access more information? Will this change be added to key performance indicators? How did the change implementation go? What’s happening next? |
| Before change | During change | After change | |
|---|---|---|---|
| Prepare for change | Create change action and communication plan | Implement change | Sustain the change |
20 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
10 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Communication Planner Tool
Activities
3.1 Deliver Your Pitch
3.2 Refine and Deliver Again
This step involves the following participants:
Varies based on those who would be relevant to your initiative.
Outcomes of this step
Ability to deliver the pitch in a manner that is clear and would be understood by the specific stakeholder the pitch is intended for.
Communicate Any IT Initiative Effectively
Phase 1 > Phase 2 > Phase 3
Using voice and body
Think about the message you are trying to convey and how your body can support that delivery. Hands, stance, and frame all have an impact on what might be conveyed.
If you want your audience to lean in and be eager about your next point, consider using a pause or softer voice and volume.
Be professional and confident
State the main points of your presentation confidently. While this should be obvious, it is essential. Your audience should be able to clearly see that you believe the points you are stating.
Present in a way that is genuine to you and your voice. Whether you have an energetic personality or a calm and composed personality, the presentation should be authentic to you.
Connect with your audience
Look each member of the audience in the eye at least once during your presentation. Avoid looking at the ceiling, the back wall, or the floor. Your audience should feel engaged – this is essential to keeping their attention.
Avoid reading from your slides. If there is text on a slide, paraphrase it while maintaining eye contact.
Info-Tech Insight
You are responsible for the response of your audience. If they aren’t engaged, it is on you as the communicator.
Sample A:
Sample B:
20 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
1 hour
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Info-Tech Insight
Whether the CIO or a service desk technician, delivering a presentation is a fear for every role in IT. Prepare your communication to help overcome the fears that are within your control.
Anuja Agrawal
National Communications Director
PwC
Anuja is an accomplished global communications professional, with extensive experience in the insurance, banking, financial, and professional services industry in Asia, the US, and Canada. She is currently the National Communications Director at PwC Canada. Her prior work experience includes communication leadership roles at Deutsche Bank, GE, Aviva, and Veritas. Anuja works closely with senior business leaders and key stakeholders to deliver measurable results and effective change and culture building programs. Anuja has experience in both internal and external communications, including strategic leadership communication, employee engagement, PR and media management, digital and social media, M&A/change and crisis management. Anuja believes in leveraging digital tools and technology-enabled solutions combined with in-person engagement to help improve the quality of dialogue and increase interactive communication within the organization to help build an inclusive culture of belonging.
Nastaran Bisheban
Chief Technology Officer
KFC Canada
A passionate technologist and seasoned transformational leader. A software engineer and computer scientist by education, a certified Project Manager that holds an MBA in Leadership with Honors and Distinction from University of Liverpool. A public speaker on various disciplines of technology and data strategy with a Harvard Business School executive leadership program training to round it all. Challenges status quo and conventional practices; is an advocate for taking calculated risk and following the principle of continuous improvement. With multiple computer software and project management publications she is a strategic mentor and board member on various non-profit organizations. Nastaran sees the world as a better place only when everyone has a seat at the table and is an active advocate for diversity and inclusion.
Heidi Davidson
Co-founder & CEO
Galvanize Worldwide and Galvanize On Demand
Dr. Heidi Davidson is the Co-Founder and CEO of Galvanize Worldwide, the largest distributed network of marketing and communications experts in the world. She also is the Co-Founder and CEO of Galvanize On Demand, a tech platform that matches marketing and communications freelancers with client projects. Now with 167 active experts, the Galvanize team delivers startup advisory work, outsourced marketing, training, and crisis communications to organizations of all sizes. Before Galvanize, Heidi spent four years as part of the turnaround team at BlackBerry as the Chief Communications Officer and SVP of Corporate Marketing, where she helped the company move from a device manufacturer to a security software provider.
Eli Gladstone
Co-Founder
Speaker Labs
Eli is a Co-Founder of Speaker Labs. He has spent over 6 years helping countless individuals overcome their public speaking fears and communicate with clarity and confidence. When he's not coaching others on how to build and deliver the perfect presentation, you'll probably find him reading some weird books, teaching his kids how to ski or play tennis, or trying to develop a good enough jumpshot to avoid being a liability on the basketball court.
Francisco Mahfuz
Keynote Speaker & Storytelling Coach
Francisco Mahfuz has been telling stories in front of audiences for a decade, and even became a National Champion of public speaking. Today, Francisco is a keynote speaker and storytelling coach and offers communication training to individuals and international organisations, and has worked with organisations like Pepsi, HP, the United Nations, Santander and Cornell University. He's the author of Bare: A Guide to Brutally Honest Public Speaking, the host of The Storypowers Podcast, and he’s been part of the IESE MBA communications course since 2020. He's received a BA in English Literature from Birkbeck University in London.
Sarah Shortreed
EVP & CTO
ATCO Ltd.
Sarah Shortreed is ATCO’s Executive Vice President and Chief Technology Officer. Her responsibilities include leading ATCO’s Information Technology (IT) function as it continues to drive agility and collaboration throughout ATCO’s global businesses and expanding and enhancing its enterprise IT strategy, including establishing ATCO’s technology roadmap for the future. Ms. Shortreed's skill and expertise are drawn from her more than 30-year career that spans many industries and includes executive roles in business consulting, complex multi-stakeholder programs, operations, sales, customer relationship management and product management. She was recently the Chief Information Officer at Bruce Power and has previously worked at BlackBerry, IBM and Union Gas. She sits on the Board of Governors for the University of Western Ontario and is the current Chair of the Chief Information Officer (CIO) Committee at the Conference Board of Canada.
Eric Silverberg
Co-Founder
Speaker Labs
Eric is a Co-Founder of Speaker Labs and has helped thousands of people build their public speaking confidence and become more dynamic and engaging communicators. When he's not running workshops to help people grow in their careers, there's a good chance you'll find him with his wife and dog, drinking Diet Coke and rewatching iconic episodes of the reality TV show Survivor! He's such a die-hard fan, that you'll probably see him playing the game one day.
Stephanie Stewart
Communications Officer & DR Coordinator
Info Security Services Simon Fraser University
Steve Strout
President
Miovision Technologies
Mr. Strout is a recognized and experienced technology leader with extensive experience in delivering value. He has successfully led business and technology transformations by leveraging many dozens of complex global SFDC, Oracle and/or SAP projects. He is especially adept at leading what some call “Project Rescues” – saving people’s careers where projects have gone awry; always driving "on-time and on-budget.“ Mr. Strout is the current President of Miovision Technologies and the former CEO and board member of the Americas’ SAP Users’ Group (ASUG). His wealth of practical knowledge comes from 30 years of extensive experience in many CxO and executive roles at some prestigious organizations such as Vonage, Sabre, BlackBerry, Shred-it, The Thomson Corporation (now Thomson Reuters) and Morris Communications. Served on Boards including Customer Advisory Boards of Apple, AgriSource Data, Dell, Edgewise, EMC, LogiSense, Socrates.ai, Spiro Carbon Group, and Unifi.
Info-Tech Research Group Contributors:
Sanchia Benedict, Research Lead
Koula Bouloukos, Production Manager
Antony Chan, Executive Counsellor
Janice Clatterbuck, Executive Counsellor
Ahmed Jowar, Research Specialist
Dave Kish, Practice Lead
Nick Kozlo, Senior Research Analyst
Heather Leier Murray, Senior Research Analyst
Amanda Mathieson, Research Director
Carlene McCubbin, Practice Lead
Joe Meier, Executive Counsellor
Andy Neill, AVP, Research
Thomas Randall, Research Director
Plus an additional two contributors who wish to remain anonymous.
During a crisis it is important to communicate to employees through messages that convey calm and are transparent and tailored to your audience. Use the Crisis Communication Guides to:
Use this guide to equip leadership to communicate in times of crisis.
Gallo, Carmine. "How Great Leaders Communicate." Harvard Business Review. 23 November 2022.
Gallup. State of the American Workplace Report. Washington, D.C.: Gallup, 6 February 2020.
Guthrie, Georgina. “Why Good Internal Communications Matter Now More than Ever.” Nulab. 15 Dec. 2021.
Hypercontext. “The State of High Performing Teams in Tech 2022.” Hypercontext. 2022.
Lambden, Duncan. “The Importance of Effective Workplace Communication – Statistics for 2022.” Expert Market. 13 June 2022.
McCreary, Gale & WikiHow. “How to Measure the Effectiveness of Communication: 14 Steps.” WikiHow.
Nowak, Marcin. “Top 7 Communication Problems in the Workplace.” MIT Enterprise Forum CEE, 2021.
Nunn, Philip. “Messaging That Works: A Unique Framework to Maximize Communication Success.” iabc.
Picincu, Andra. “How to Measure Effective Communications.” Small Business Chron. 12 January 2021.
Price. David A. “Pixar Story Rules.”
Prosci. “Best Practices in Change Management 2020 Edition.” Prosci, 2020.
Roberts, Dan. “How CIOs Become Visionary Communicators.” CIO, 2019.
Schlesinger, Mark. “Why building effective communication skill in IT is incredibly important.”
Skills Framework for the Information Age, “Mapping SFIA Levels of Responsibilities to Behavioural Factors.” Skills Framework for the Information Age, 2021.
St. James, Halina. Talk It Out. Podium, 2005.
TeamState. “Communication in the Workplace Statistics: Importance and Effectiveness in 2022.” TeamStage, 2022.
Walters, Katlin. “Top 5 Ways to Measure Internal Communication.” Intranet Connections, 30 May 2019.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Review current licensing options and models to determine which cloud products will most appropriately fit the organization's environment.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
This trends and buyer’s guide will help you:
Create your own request for proposal (RFP) for your customer service management suite procurement process by customizing Info-Tech's RFP template.
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.
Keep stakeholders engaged with simple and friction-free templates to document your progress for Rapid Application Selection.
Leverage a traceable and straightforward Vendor Evaluation Workbook to narrow the field of potential vendors and accelerate the application selection process.
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.
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.
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, Info-Tech Research Group
| Your Challenge | Common Obstacles | Info-Tech’s Solution |
|
|
This trends and buyer’s guide will help you:
|
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
| 1. Contextualize the CSM Landscape | 2. Select the Right CSM Vendor | |
|---|---|---|
| Phase Steps |
|
|
| Phase Outcomes |
|
|
Info-Tech Insight
Need help constructing your RFP? Use Info-Tech’s CSM Platform RFP Template!
| 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:
| 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
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
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
| 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.
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
| 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. |
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.
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.
Info-Tech Insight
Use Info-Tech’s CSM Platform Opportunity Assessment Tool to discover your organization’s customer service maturity.
30 minutes
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the CSM Platform Opportunity Assessment Tool
| 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. |
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:
|
| 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. |
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)
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).
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.
2 hours
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Software Selection Workbook
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 |
|---|---|
|
|
Info-Tech Insight
Review Info-Tech’s requirements gathering methodology to improve your requirements gathering process.
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
2 hours
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the CSM Platform RFP Scoring Tool
Download the CSM Platform RFP Template
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. |
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:
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
To kick-start scripting your demo scenarios, leverage our CSM Platform Vendor Demo Script Template.
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? |
|---|---|
|
|
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.
| 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)? |
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:
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.
Download Master Contract Review and Negotiation for Software Agreements
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.
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.
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.
Stated Industry Specializations
SoftwareReviews’ CSM Enterprise Vendor Ranking
(out of 7)
Likeliness to Recommend
Plan to Renew
Satisfaction That Cost Is Fair Relative to Value
Strengths
Areas to Improve
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.
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
Stated Industry Specializations
SoftwareReviews’ CSM Enterprise Vendor Ranking
(out of 7)
Likeliness to Recommend
Plan to Renew
Satisfaction That Cost Is Fair Relative to Value
Strengths
Areas to Improve
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 |
|---|---|---|---|
|
|
|
|
*Pricing correct as of November 2022. Listed in USD and absent discounts.
See pricing on vendor’s website for latest information.
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
Stated Industry Specializations
SoftwareReviews’ CSM Enterprise Vendor Ranking
(out of 7)
Likeliness to Recommend
Plan to Renew
Satisfaction That Cost Is Fair Relative to Value
Strengths
Areas to Improve
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 |
|---|---|---|
|
|
|
*Pricing correct as of November 2022. Listed in USD and absent discounts.
See pricing on vendor’s website for latest information.
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
Stated Industry Specializations
SoftwareReviews’ CSM Enterprise Vendor Ranking
(out of 7)
Likeliness to Recommend
Plan to Renew
Satisfaction That Cost Is Fair Relative to Value
Strengths:
Areas to Improve:
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 |
|---|---|---|---|
|
|
|
|
*Pricing correct as of November 2022. Listed in USD and absent discounts.
See pricing on vendor’s website for latest information.
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
Stated Industry Specializations
SoftwareReviews’ CSM Enterprise Vendor Ranking
(out of 7)
Likeliness to Recommend
Plan to Renew
Satisfaction That Cost Is Fair Relative to Value
Strengths:
Areas to Improve:
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 |
|---|---|---|---|
|
|
|
|
*Pricing correct as of November 2022. Listed in USD and absent discounts.
See pricing on vendor’s website for latest information.
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
Stated Industry Specializations
SoftwareReviews’ CSM Enterprise Vendor Ranking
(out of 7)
Likeliness to Recommend
Plan to Renew
Satisfaction That Cost Is Fair Relative to Value
Strengths
Areas to Improve
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 |
|---|---|---|
|
|
|
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
Stated Industry Specializations
SoftwareReviews’ CSM Midmarket Vendor Ranking
(out of 8)
Likeliness to Recommend
Plan to Renew
Satisfaction That Cost Is Fair Relative to Value
Strengths
Areas to Improve
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 |
|---|---|
|
|
*Pricing correct as of November 2022. Listed in USD and absent discounts.
See pricing on vendor’s website for latest information.
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
Stated Industry Specializations
SoftwareReviews’ CSM Midmarket Vendor Ranking
(out of 8)
Likeliness to Recommend
Plan to Renew
Satisfaction That Cost Is Fair Relative to Value
Strengths
Areas to Improve
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* |
|---|---|---|
|
|
|
*Pricing unavailable. Request quote.
See pricing on vendor’s website for latest information.
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
Stated Industry Specializations
SoftwareReviews’ CSM Midmarket Vendor Ranking
(out of 8)
Likeliness to Recommend
Plan to Renew
Satisfaction That Cost Is Fair Relative to Value
Strengths
Areas to Improve
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 |
|---|---|---|
|
|
|
*Pricing correct as of November 2022. Listed in USD and absent discounts.
See pricing on vendor’s website for latest information.
In this trends and buyer’s guide for CSM tool selection, we engaged in several activities to:
The result:
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
Governance and Management of Enterprise Software Implementation
The Rapid Application Selection Framework
Build a Strong Technology Foundation for Customer Experience Management
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.
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 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.
Using the MITRE ATT&CK® framework, Info-Tech’s approach helps you understand your preparedness and effective detection and mitigation actions.
This blueprint and associated tool are scalable for all types of organizations within various industry sectors, allowing them to know what types of risk they are facing and what security services are recommended to mitigate those risks.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Review a breakdown of each of the various attack vectors and their techniques for additional context and insight into the most prevalent attack tactics.
Map your current security protocols against the impacts of various techniques on your network to determine your risk preparedness.
Use your prioritized attack vectors to plan your next threat modeling session with confidence that the most pressing security concerns are being addressed with substantive remediation actions.
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:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
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.
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.
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.
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.
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.
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.
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.
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.
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.
Identify key business data assets that need to be governed.
Create a unifying vision for the data governance program.
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.
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
Sample use cases (tied to the business capability map) and a repeatable use case framework
Vision and mission for data governance
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.
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.
2.1 Understand your current data governance capabilities and maturity
2.2 Set target-state data governance capabilities
Current state of data governance maturity
Definition of target state
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.
Establish clear direction for the data governance program.
Step-by-step outline of how to create effective data governance, with true business-IT collaboration.
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
Target-state data governance initiatives
Data domain to data governance role mapping
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.
Prioritized initiatives with dependencies mapped out.
A clearly communicated plan for data governance that will have full business backing.
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
Initialized roadmap
Initialized RACI
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
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.
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 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:
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.
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
“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
78% of companies (and 92% of top-tier companies) have a corporate initiative to become more data-driven. – Alation, 2020
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
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
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 an enabling framework of decision rights, responsibilities, and accountabilities for data assets across the enterprise.
Data governance is:
If done correctly, data governance is not:
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.
“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
“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-driven culture = “data matters to our company”
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
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)
Make the available data governance tools and technology work for you:
While data governance tools and technologies are no panacea, leverage their automated and AI-enabled capabilities to augment your data governance program.
Put data governance into the context of the business:
Start substantiating early on how you are going to measure success as your data governance program evolves.
Key considerations:
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).
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.
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.
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.
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.
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.
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.
| 1. Build Business and User Context | 2. Understand Your Current Data Governance Capabilities | 3. Build a Target State Roadmap and Plan | |
|---|---|---|---|
| Phase Steps |
|
|
|
| Phase Outcomes |
|
|
|
Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:
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.
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.
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.
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.
Data Governance Planning and Roadmapping Workbook
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.
"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 keeps 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."
| 1. Build Business and User context | 2. Understand Your Current Data Governance Capabilities | 3. Build a Target State Roadmap and Plan | |
|---|---|---|---|
| Best-Practice Toolkit |
|
|
|
| Guided Implementation |
|
|
|
| Phase Outcomes |
|
|
|
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.
| 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 |
|
|
|
|
| Deliverables |
|
|
|
|
“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:
This phase involves the following participants:
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:
Outcomes of this step
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.
Confirm your organization's existing business capability map or initiate the formulation of a business capability map:
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
Output
Materials
Participants
For more information, refer to Info-Tech’s Document Your Business Architecture.
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:
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.
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.
Value streams connect business goals 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.
For this value stream, download Info-Tech’s Info-Tech’s Industry Reference Architecture for Retail Banking.
Value streams connect business goals 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.
For this value stream, download Info-Tech’s Industry Reference Architecture for Higher Education.
Value streams connect business goals 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.
For this value stream, download Info-Tech’s Industry Reference Architecture for Local Government.
Value streams connect business goals 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.
For this value stream, download Info-Tech’s Industry Reference Architecture for Manufacturing.
Value streams connect business goals 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.
For this value stream, download Info-Tech’s Industry Reference Architecture for Retail.
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:
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.
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.
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
For this business capability map, download Info-Tech’s Industry Reference Architecture for 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.
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
For this business capability map, download Info-Tech’s Industry Reference Architecture for 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.
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
For this business capability map, download Info-Tech’s Industry Reference Architecture for 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.
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
For this business capability map, download Info-Tech’s Industry Reference Architecture for 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.
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
For this business capability map, download Info-Tech’s Industry Reference Architecture for Retail.
Determine which capabilities are considered high priority in your organization.
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
Output
Materials
Participants
For more information, refer to Info-Tech’s Document Your Business Architecture.
This exercise is useful in ensuring the data governance program is focused and aligned to support the priorities and direction of the business.
Example: Retail
For this business capability map, download Info-Tech’s Industry Reference Architecture for Retail.
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.
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
Output
Materials
Participants
Download Info-Tech’s Data Governance Planning and Roadmapping Workbook
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
For this strategy map, download Info-Tech’s Industry Reference Architecture for Retail.
Activities
1.2.1 Build High-Value Use Cases
This step will guide you through the following activities:
Outcomes of this step
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.
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.
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
Output
Materials
Participants
Download Info-Tech’s Data Use Case Framework Template
Leveraging your business capability map, build use cases that align with the organization’s key business capabilities.
Consider:
Info-Tech’s Data Requirements and Mapping Methodology for Creating Use Cases
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
This phase will guide you through the following activities:
This phase involves the following participants:
This step will guide you through the following activities:
Outcomes of this step
A well-defined data governance program will deliver:
The key components of establishing sustainable enterprise data governance, taken from Info-Tech’s Data Governance Framework:
The office of the chief data officer (CDO):
“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
“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
Who are best suited to be data owners?
Data owners are typically senior business leaders with the following characteristics:
Data governance working groups:
Traditionally, data stewards:
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
“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:
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.
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.
“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
Examples of focus areas for your operating model (continued):
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.
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.
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.
“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
Examples of data policies:
“Organizational culture can accelerate the application of analytics, amplify its power, and steer companies away from risky outcomes.” – Petzold, et al., 2020
What does a healthy data culture look like?
Building a culture of data excellence.
Leverage Info-Tech’s Data Culture Diagnostic to understand your organization’s culture around data.
Contact your Info-Tech Account Representative for more information on the Data Culture Diagnostic
“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
“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
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.
Data governance will support your organization’s ethical use and handling of data by facilitating definition around important factors, such as:
Activities
2.2.1 Gauge Your Organization’s Current Data Culture
This step will guide you through the following activities:
Outcomes of this step
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:
Input
Output
Materials
Participants
Contact your Info-Tech Account Representative for details on launching a Data Culture Diagnostic.
“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:
This phase involves the following participants:
This step will guide you through the following activities:
Outcomes of this step
Key considerations:
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).
Define key roles for getting started.
Start small and then scale – deliver early wins.
Start understanding data knowledge gaps, building the program, and delivering.
Make the available data governance tools and technology work for you.
Sample data governance roadmap milestones:
Key Considerations:
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.
These are some of the data governance tools and technology players. Check out SoftwareReviews for help making better software decisions.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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. |
Most organizations have problems with policy management. These include:
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:
myPolicies
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.
Trust
Availability
Security
Compliance
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:
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.
Although they can be highly subjective, metrics are extremely important to data governance success.
Policies are great to have from a legal perspective, but unless they are followed, they will not benefit the organization.
Review metrics on an ongoing basis with those data owners/stewards who are accountable, the data governance steering committee, and the executive sponsors.
Examples include:
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.
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.
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.
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:
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.
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.
Key to building and fostering a data-driven culture.
Streamline your data management program with our simplified framework.
Be the voice of data in a time of transformation.
| 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 |
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.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Assess whether you’re ready to optimize the service desk with a shift-left strategy, get buy-in for the initiative, and define metrics to measure success.
Build strategy and identify specific opportunities to shift service support left to Level 1 through knowledge sharing and other methods, to the end-user through self-service, and to automation and AI.
Identify, track, and implement specific shift-left opportunities and document a communications plan to increase adoption.
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.
Define how shift left would apply in your organization, get buy-in for the initiative, and define metrics to measure success.
Defined scope and objectives for the shift-left initiative
Buy-in for the program
Metrics to keep the project on track and evaluate success
1.1 Review current service desk structure
1.2 Discuss challenges
1.3 Review shift-left model and discuss how it would apply in your organization
1.4 Complete the Shift-Left Prerequisites Assessment
1.5 Complete a RACI chart for the project
1.6 Define and document objectives
1.7 Review the stakeholder buy-in presentation
1.8 Document critical success factors
1.9 Define KPIs and metrics
Shift-left scope
Completed shift-left prerequisites assessment
RACI chart
Defined objectives
Stakeholder buy-in presentation
Critical success factors
Metrics to measure success
Build strategy and identify specific opportunities to shift service support left to Level 1 through knowledge sharing and other methods.
Identified initiatives to shift work to Level 1
Documented knowledge management process workflows and strategy
2.1 Identify barriers to Level 1 resolution
2.2 Discuss knowledgebase challenges and areas for improvement
2.3 Optimize KB input process
2.4 Optimize KB usage process
2.5 Optimize KB review process
2.6 Discuss and document KCS strategy and roles
2.7 Document knowledge success metrics
2.8 Brainstorm additional methods of increasing FLR
KB input workflow
KB usage workflow
KB review workflow
KCS strategy and roles
Knowledge management metrics
Identified opportunities to shift to Level 1
Build strategy and identify specific opportunities to shift service support left to the end user through self-service and to automation and AI.
Identified initiatives to shift work to self-service and automation
Evaluation of self-service portal and identified opportunities for improvement
3.1 Review existing self-service portal and discuss vision
3.2 Identify opportunities to improve portal accessibility, UI, and features
3.3 Evaluate the user-facing knowledgebase
3.4 Optimize the ticket intake form
3.5 Document plan to improve, communicate, and evaluate portal
3.6 Map the user experience with a workflow
3.7 Document your AI strategy
3.8 Identify candidates for automation
Identified opportunities to improve portal
Improvements to knowledgebase
Improved ticket intake form
Strategy to communicate and measure success of portal
Self-service resolution workflow
Strategy to apply AI and automation
Identified opportunities to shift tasks to automation
Build an action plan to implement shift left, including a communications strategy.
Action plan to track and implement shift-left opportunities
Communications plan to increase adoption
4.1 Examine process workflows for shift-left opportunities
4.2 Document shift-left-specific responsibilities for each role
4.3 Identify and track shift-left opportunities in the action plan
4.4 Brainstorm objections and responses
4.5 Document communications plan
Incident management workflow with shift-left opportunities
Shift left responsibilities for key roles
Shift-left action plan
Objection handling responses
Communications plan
Access to information about companies is more available to consumers than ever. Organizations must implement mechanisms to monitor and manage how information is perceived to avoid potentially disastrous consequences to their brand reputation.
A negative event could impact your organization's reputation at any given time. Make sure you understand where such events may come from and have a plan to manage the inevitable consequences.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Use this research to identify and quantify the potential reputational impacts caused by vendors. Use Info-Tech's approach to look at the reputational impact from various perspectives to better prepare for issues that may arise.
By playing the “what if” game and asking probing questions to draw out – or eliminate - possible negative outcomes, everyone involved adds their insight into parts of the organization to gather a comprehensive picture of potential impacts.
Social media, unprecedented access to good and bad information, and consumer reliance on others’ online opinions force organizations to dedicate more resources to protecting their brand reputation than ever before. Perceptions matter, and you should monitor and protect the perception of your organization with as much rigor as possible to ensure your brand remains recognizable and trusted.
![]() |
Frank Sewell
|
| Your Challenge
Access to information about companies is more available to consumers than ever. A negative event could impact your organizational reputation at any time. As a result, organizations must implement mechanisms to monitor and manage how information is perceived to avoid potentially disastrous consequences to their brand reputation. Make sure you understand where negative events may come from and have a plan to manage the inevitable consequences. |
Common Obstacles
Identifying and managing a vendor’s potential impact on your organization’s reputation requires efforts from multiple people in the organization across several functions. Those people all need coaching on the potential changes in the market and how social media can affect your brand. Organizational leadership is often caught unaware during crises, and their response plans lack the flexibility to adjust to significant market upheavals. |
Info-Tech’s Approach
Vendor management practices educate organizations on the different potential risks to vendors in your market and suggest creative and alternative ways to avoid and help manage them. Prioritize and classify your vendors with quantifiable, standardized rankings. Prioritize focus on your high-risk vendors. Standardize your processes for identifying and monitoring vendor risks to manage potential impacts on your reputation and brand with our Reputational Risk Impact Tool. |
Organizations must evolve their risk assessments to be more adaptive to respond to rapid changes in online media. Ongoing monitoring of social media and the vendors tied to their company is imperative to achieving success and avoiding reputational disasters.

This series will focus on the individual components of vendor risk and how vendor management practices can facilitate organizations’ understanding of those risks.
Out of scope:
This series will not tackle risk governance, determining overall risk tolerance and appetite, or quantifying inherent risk.
In this blueprint, we’ll explore reputational risks (risks to the brand reputation of the organization) and their impacts.
Identify potentially negative events to assess the overall impact on your organization and implement adaptive measures to respond and correct.

25%of a company’s market value is due to reputation (Transmission Private, 2021) |
94%of consumers say that a bad review has convinced them to avoid a business (ReviewTrackers, 2022) |
14 hoursis the average time it takes for a false claim to be corrected on social media (Risk Analysis, 2018) |
![]() |
||
| And the cost of rebranding
“Brand recognition is the ability of consumers to recognize an identifying characteristic of one company versus a competitor.” (Investopedia) “Most trademark valuation is based directly on its projected future earning power, based on income history. For a new brand with no history, evaluators must apply experience and common sense to predict the brand's earning potential. They can also use feedback from industry experts, market surveys, and other studies.” (UpCounsel) The cost of rebranding for small to medium businesses is about 10 to 20% of the recommended overall marketing budget and can take six to eight months (Ignyte). |
"All we are at our core is our reputation and our brand, and they are intertwined." (Phil Bode, Principal Research Director, Info-Tech Research Group) |
![]() |
Bad Customer Reviews Breach of Data Poor Security Posture Negative News Articles Public Lawsuits Poor Performance |
An ideal state
|
Brand Protection
|
Never underestimate the power of local media on your profitsInfo-Tech InsightKeep in mind that too much exposure to media can be a negative in that it heightens the awareness of your organization to outside actors. If you do go through a period of increased exposure, make sure to advance your monitoring practices and vigilance. | Story: Restaurant data breachLosing customer faithA popular local restaurant’s point of service (POS) machines were breached and the credit card data of their customers over a two-week period was stolen. The restaurant did the right thing: they privately notified the affected people, helped them set up credit monitoring services, and replaced their compromised POS system. Unfortunately, the local newspaper got wind of the breach. It published the story, leaving out that the restaurant had already notified affected customers and had replaced their POS machines. In response, the restaurant launched a campaign in the local paper and on social media to repair their reputation in the community and reassure people that they could safely transact at their business. For at least a month, the restaurant experienced a drastic decrease in revenue as customers either refused to come in to eat or paid only in cash. During this same period the restaurant was spending outside their budget on the advertising.
|
| Trust but verify
A successful general contractor with a reputation for fairness in their dealings needed a specialist to perform some expert carpentry work for a few of their clients. The contractor gave the specialist the clients’ contact information and trusted them to arrange the work. Weeks later, the contractor checked in with the clients and received a ton of negative feedback:
As a result, the contractor took extreme measures to regain the clients’ confidence and trust and lost other opportunities in the process. |
You work hard for your reputation. Don’t let others ruin it. |
Don’t forget to look within as well as without
|
Story: Internal reputation is vitalTrust works both waysAn organization’s relatively new IT and InfoSec department leadership have been upgrading the organization's systems and policies as fast as resources allow when the organization encounters a major breach of security. Trust in the developing IT and InfoSec departments' leadership wanes throughout the organization as people search for the root cause and blame the systems. This degradation of trust limits the effectiveness of the newly implemented process, procedures, and tools of the departments. The new leaders' abilities are called into question, and they must now rigorously defend and justify their decisions and positions to the executives and board. It will be some time before the two departments gain their prior trust and respect, and the new leaders face some tough times ahead regaining the organization's confidence. How could the new leaders approach the situation to mend their reputations in the wake of this (perhaps unfair) reputational hit? |
It is not enough to identify the potential risks; there must also be adequate controls in place to monitor and manage them
|
Identify, manage, and monitor reputational risksGlobal markets
Social media
Global shortages
|

Identifying and understanding potential risks is essential to adapting to the ever-changing online landscapeInfo-Tech InsightFew organizations are good at identifying risks. As a result, almost none realistically plan to monitor, manage, and adapt their plans to mitigate those risks. | Reputational risksNot protecting your brand can have disastrous consequences to your organization
|
Identify potential reputational risk impacts
|
![]() |
Review Organizational Strategy
Understand the organizational strategy to prepare for the “what if” game exercise. |
|
| Identify & Understand Potential Risks
Play the “what if” game with the right people at the table. |
||
| Create a Risk Profile Packet for Leadership
Pull all the information together in a presentation document. |
||
| Validate the Risks
Work with leadership to ensure that the proposed risks are in line with their thoughts. |
||
| Plan to Manage the Risks
Lower the overall risk potential by putting mitigations in place. |
||
| Communicate the Plan
It is important not only to have a plan but also to socialize it in the organization for awareness. |
||
| Enact the Plan
Once the plan is finalized and socialized put it in place with continued monitoring for success. |
||
| (Adapted from Harvard Law School Forum on Corporate Governance) |
Insight SummaryReputational risk impacts are often unanticipated, causing catastrophic downstream effects. Continuously monitoring your vendors’ actions in the market can help organizations head off brand disasters before they occur. |
Insight 1Understanding how to monitor social media activity and online content will give you an edge in the current environment. Do you have dedicated individuals or teams to monitor your organization's online presence? Most organizations review and approve the online content, but many forget the need to have analysts reviewing what others are saying about them. Insight 2Organizations need to learn how to assess the likelihood of potential risks in the rapidly changing online environments and recognize how their partnerships and subcontractors’ actions can affect their brand. For example, do you understand how a simple news article raises your profile for short-term and long-term adverse events? Insight 3Socialize the risk management process throughout the organization to heighten awareness and enable employees to help protect the company’s reputation. Do you include a social media and brand protection policy in your annual education? |
Who should be included in the discussion?
|
Keep in mind: (R=L*I) Risk = Likelihood x Impact Impact tends to remain the same, while likelihood is a very flexible variable.
|
What can we realistically do about the risks?
|
Social media is driving the need for perpetual diligence. Organizations need to monitor their brand reputation considering the pace of incidents in the modern age.
|
Input: List of identified potential risk scenarios scored by likelihood and financial impact, List of potential management of the scenarios to reduce the risk
Output: Comprehensive reputational risk profile on the specific vendor solution
Materials: Whiteboard/flip charts, Reputational Risk Impact Tool to help drive discussion
Participants: Vendor Management Coordinator, Organizational Leadership, Operations Experts (SMEs), Legal/Compliance/Risk Manager, Marketing
Vendor management professionals are in an excellent position to help senior leadership identify and pull together resources across the organization to determine potential risks. By playing the "what if" game and asking probing questions to draw out – or eliminate – possible negative outcomes, everyone involved adds their insight into parts of the organization to gather a comprehensive picture of potential impacts.
Download the Reputational Risk Impact Tool
Example: Low reputational riskWe can see clearly in this example that the contractor suffered minimal impact from the specialist's behavior. Though they did take a hit to their overall reputation with a few customers, they should be able to course-correct with a minimal outlay of effort and almost no loss of revenue. |
![]() |

Example: High reputational riskNote in the example how the tool can represent different weights for each of the criteria depending on your needs. |
![]() |

Be vigilant and adaptable to change
|
Organizations must evolve their risk assessments to be more adaptive to respond to global factors in the market. Ongoing monitoring of online media and the vendors tied to company visibility is imperative to avoiding disaster. |
"The CEO Reputation Premium: Gaining Advantage in the Engagement Era." Weber Shandwick, March 2015. Accessed June 2022.
Glidden, Donna. "Don't Underestimate the Need to Protect Your Brand in Publicity Clauses." Info-Tech Research Group, June 2022.
Greenaway, Jordan. "Managing Reputation Risk: A start-to-finish guide." Transmission Private, July 2020. Accessed June 2022.
Jagiello, Robert D., and Thomas T. Hills. “Bad News Has Wings: Dread Risk Mediates Social Amplification in Risk Communication.” Risk Analysis, vol. 38, no. 10, 2018, pp. 2193-2207.
Kenton, Will. "Brand Recognition.” Investopedia, Aug. 2021. Accessed June 2022.
Lischer, Brian. "How Much Does it Cost to Rebrand Your Company?" Ignyte, October 2017. Accessed June 2022.
"Powerful Examples of How to Respond to Negative Reviews." ReviewTrackers, 16 Feb. 2022. Accessed June 2022.
Tonello, Matteo. “Strategic Risk Management: A Primer for Directors.” Harvard Law School Forum on Corporate Governance, 23 Aug. 2012. Web.
"Valuation of Trademarks: Everything You Need to Know." UpCounsel, 2022. Accessed June 2022.
![]() |
Identify and Manage Financial Risk Impacts on Your Organization
|
![]() |
Identify and Manage Strategic Risk Impacts on Your Organization
|
![]() |
Jump Start Your Vendor Management Initiative
|
| Frank Sewell
Research Director
|
Donna Glidden
Research Director
|
|
| Steven Jeffery
Principal Research Director
|
Mark Roman
Managing Partner
|
|
| Phil Bode
Principal Research Director
|
Sarah Pletcher
Executive Advisor
|
|
| Scott Bickley
Practice Lead
|
Organizations wishing to mature their IT financial management (ITFM) maturity often face the following obstacles:
No matter where you currently stand in your ITFM practice, there is always room for improvement. Hence, a maturity assessment should be viewed as a self-improvement tool that is only valuable if you are willing to act on it.
A mature ITFM practice leads to many benefits.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
This research seeks to support IT leaders and ITFM practitioners in evaluating and improving their current maturity. It will help document both current and target states as well as prioritize focus areas for improvement.
This Excel workbook guides IT finance practitioners to effectively assess their IT financial management practice. Incorporate the visual outputs into your final executive presentation document. Key activities include context setting, completing the assessment, and prioritizing focus areas based on results.
Use this template to document your final ITFM maturity outputs, including the current and target states and your identified priorities.
Technology has been evolving throughout the years, increasing complexity and investments, while putting more stress on operations and people involved. As an IT leader, you are now entrusted to run your outfit as a business, sit at the executive table as a true partner, and be involved in making decisions that best suit your organization. Therefore, you have an obligation to fulfill the needs of your end customers and live up to their expectations, which is not an easy task.
IT financial management (ITFM) helps you generate value to your organization’s clientele by bringing necessary trade-offs to light, while driving effective dialogues with your business partners and leadership team.
This research will focus on Info-Tech’s approach to ITFM maturity, aiming for a state of continuous improvement, where an organization can learn and grow as it adapts to change. As the ITFM practice matures, IT and business leaders will be able to better understand one another and together make better business decisions, driven by data.
This client advisory presentation and accompanying tool seek to support IT leaders and ITFM practitioners in evaluating and improving their current maturity. It will help document both current and target states as well as prioritize focus areas for improvement.
|
Bilal Alberto Saab
Research Director, IT Financial Management Info-Tech Research Group |
ITFM is often discarded and not given enough importance and relevance due to the operational nature of IT, and the specialized skillset of its people, leading to several problems and challenges, such as:
Business-driven conversations around financials (spending, cost, revenue) are a rarity in IT due to several factors, including:
Mature your ITFM practice by activating the means to make informed business decisions.
Info-Tech’s methodology helps you move the dial by focusing on three maturity focus areas:
Influence your organization’s strategic direction by maturing your ITFM practice.
“ITFM embeds technology in financial management practices. Through cost, demand, and value, ITFM brings technology and business together, forging the necessary relationships and starting the right conversations to enable the best decisions for the organization.”
– Monica Braun, Research Director, Info-Tech Research Group
“Value is not the numbers you visualize on a chart, it’s the dialogue this data generates with your business partners and leadership team.”
– Dave Kish, Practice Lead, Info-Tech Research Group
In a technology-driven world, advances come at a price. With greater spending required, more complex and difficult conversations arise.
79% of respondents believe that decisions taking too long to make is either a significant or somewhat of a challenge (Flexera 2022 Tech Spend Pulse; N=501).
81% of respondents believe that ensuring spend efficiency (avoiding waste) is either a challenge or somewhat of a challenge (Flexera 2022 Tech Spend Pulse; N=501).
In today’s world, where organizations are driving customer experience through technology investments, having a seat at the table means IT leaders must be well versed in business language and practice, including solid financial management skills.
However, IT staff across all industries aren’t very confident in how well IT is doing in managing its finances. This becomes evident after looking at three core processes:
Recent data from 4,137 respondents to Info-Tech’s IT Management & Governance Diagnostic shows that while most IT staff feel that these three financial management processes are important, notably fewer feel that IT management is effective at executing on them.
IT leadership’s capabilities around fundamental cost data capture appear to be lagging, not to mention the essential value-added capabilities around optimizing costs and demonstrating IT’s contribution to business value.

Source: Info-Tech Research Group, IT Management & Governance Diagnostic, 2023.
Note: See Appendix A for maturity level definitions and descriptions.
Info-Tech identified three maturity focus areas, each containing three levers.
Identify where you stand across the nine maturity levers, detect the gaps, and determine your priorities as a first step to develop an improvement plan.
Note: See Appendix B for maturity level definitions and descriptions per lever.
Each step of this activity is accompanied by supporting deliverables to help you accomplish your goals.
Build your improvement plan and implement your initiatives to move the dial and climb the maturity ladder.
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 |
|||
3 hours
Input: Understanding your context, objectives, and methodology
Output: ITFM maturity assessment stakeholders and their objectives, ITFM maturity assessment methodology, ITFM maturity assessment takers
Materials: 1a. Prepare for Assessment tab in the ITFM Maturity Assessment Tool
Participants: CIO/IT director, CFO/finance director, IT finance lead, IT audit lead, Other IT management
Download the IT Financial Management Maturity Assessment Tool
Refer to the example and guidelines below on how to document stakeholders, objectives, and methodology (table range: columns B to G and rows 8 to 15).
| Column ID | Input Type | Guidelines |
| B | Formula | Automatic calculation, no entry required. |
| C | Text | Enter the full name of each stakeholder on a separate row. |
| D | Text | Enter the job title related to each stakeholder. |
| E | Text | Enter the objective(s) related to each stakeholder. |
| F | Text | Enter the agreed upon methodology. |
| G | Text | Enter any notes or comments per stakeholder (optional). |
Download the IT Financial Management Maturity Assessment Tool
Refer to the example and guidelines below on how to document assessment takers (table range: columns B to E and rows 18 to 25).
| Column ID | Input Type | Guidelines |
| B | Formula | Automatic calculation, no entry required. |
| C | Text | Enter the full name of each assessment taker on a separate row. |
| D | Text | Enter the job title related to each stakeholder to identify which party is being represented per assessment taker. |
| E | Text | Enter any notes or comments per stakeholder (optional). |
Download the IT Financial Management Maturity Assessment Tool
3 hours
Input: Understanding of your ITFM current state and 12-month target state, ITFM maturity assessment results
Output: ITFM current- and target-state maturity levels, average scores, and variance, ITFM current- and target-state average scores, variance, and priority by maturity focus area and maturity lever
Materials: 1b. Glossary, 2a. Assess ITFM Foundation, 2b. Assess Mngt. & Monitoring, 2c. Assess Language, and 3. Assessment Summary tabs in the ITFM Maturity Assessment Tool
Participants: CIO/IT director, CFO/finance director, IT finance lead, IT audit lead, Other IT management
Download the IT Financial Management Maturity Assessment Tool
Refer to the example and guidelines below on how to complete the survey.
| Column ID | Input Type | Guidelines |
| B | Formula | Automatic calculation, no entry required. |
| C | Formula | Automatic calculation, no entry required: ITFM maturity statement to assess. |
| D, E | Dropdown | Select the maturity levels of your current and target states. One of five maturity levels for each statement, from “1. Nonexistent” (lowest maturity) to “5. Advanced” (highest maturity). |
| F, G, H | Formula | Automatic calculation, no entry required: scores associated with your current and target state selection, along with related variance (column G – column F). |
| I | Text | Enter any notes or comments per ITFM maturity statement (optional). |
Download the IT Financial Management Maturity Assessment Tool
Refer to the example and guidelines below on how to review your results.
| Column ID | Input Type | Guidelines |
| K | Formula | Automatic calculation, no entry required. |
| L | Formula | Automatic calculation, no entry required: Current State, Target State, and Variance entries. Please ignore the current state benchmark, it’s a placeholder for future reference. |
| M | Formula | Automatic calculation, no entry required: average overall maturity score for your Current State and Target State entries, along with related Variance. |
| N, O | Formula | Automatic calculation, no entry required: maturity level and related name based on the overall average score (column M), where level 1 corresponds to an average score less than or equal to 1.49, level 2 corresponds to an average score between 1.5 and 2.49 (inclusive), level 3 corresponds to an average score between 2.5 and 3.49 (inclusive), level 4 corresponds to an average score between 3.5 and 4.49 (inclusive), and level 5 corresponds to an average score between 4.5 and 5 (inclusive). |
| P, Q | Formula | Automatic calculation, no entry required: maturity definition and related description based on the maturity level (column N). |
Download the IT Financial Management Maturity Assessment Tool
Refer to the example and guidelines below on how to review your results per maturity focus area and maturity lever, then prioritize accordingly.
| Column ID | Input Type | Guidelines |
| B | Formula | Automatic calculation, no entry required. |
| C | Formula | Automatic calculation, no entry required: ITFM maturity focus area or lever, depending on the table. |
| D | Placeholder | Ignore this column because it’s a placeholder for future reference. |
| E, F, G | Formula | Automatic calculation, no entry required: average score related to the current state and target state, along with the corresponding variance per maturity focus area or lever (depending on the table). |
| H | Formula | Automatic calculation, no entry required: preliminary priority based on the average variance (column G), where Low corresponds to an average variance between 0 and 0.5 (inclusive), Medium corresponds to an average variance between 0.51 and 0.99 (inclusive), and High corresponds to an average variance greater than or equal to 1. |
| J | Dropdown | Select your final priority (Low, Medium, or High) per ITFM maturity focus area or lever, depending on the table. |
| K | Whole Number | Enter the appropriate rank based on your priorities; do not use the same number more than once. A whole number between 1 and 3 to rank ITFM maturity focus areas, and between 1 and 9 to rank ITFM maturity levers, depending on the table. |
Download the IT Financial Management Maturity Assessment Tool
3 hours
Input: ITFM maturity assessment results
Output: Customized ITFM maturity assessment report
Materials: 3. Assessment Summary tab in the ITFM Maturity Assessment Tool, ITFM Maturity Assessment Report Template
Participants: CIO/IT director, CFO/finance director, IT finance lead, IT audit lead, Other IT management
Download the IT Financial Management Maturity Assessment Tool
Refer to the example below on charts depicting different views of the maturity assessment results across the three focus areas and nine levers.
Download the IT Financial Management Maturity Assessment Tool
Refer to the example below on slides depicting different views of the maturity assessment results across the three maturity focus areas and nine maturity levers.
Slide 6: Edit levels based on your assessment results. Copy and paste the appropriate maturity level definition and description from slide 4.
Slide 7: Copy related charts from the assessment summary tab in the Excel workbook and remove the chart title. You can use the “Outer Offset: Bottom” shadow under shape effects on the chart.
Slide 8: Copy related charts from the assessment summary tab in the Excel workbook and remove the chart title and legend. You can use the “Outer Offset: Center” shadow under shape effects on the chart.
Download the IT Financial Management Maturity Assessment Report Template
Communicate your maturity results with stakeholders and develop an actionable ITFM improvement plan.
And remember, having informed discussions with your business partners and stakeholders, where technology helps propel your organization forward, is priceless!
|
Dave Kish
Practice Lead, ITFM Practice Info-Tech Research Group |
|
Jennifer Perrier
Principal Research Director, ITFM Practice Info-Tech Research Group |
|
Angie Reynolds
Principal Research Director, ITFM Practice Info-Tech Research Group |
|
Monica Braun
Research Director, ITFM Practice Info-Tech Research Group |
|
Rex Ding
Research Specialist, ITFM Practice Info-Tech Research Group |
|
Aman Kumari
Research Specialist, ITFM Practice Info-Tech Research Group |
|
Amy Byalick
Vice President, IT Finance Info-Tech Research Group |
Amy Byalick is an IT Finance practitioner with 15 years of experience supporting CIOs and IT leaders elevating the IT financial storytelling and unlocking insights. Amy is currently working at Johnson Controls as the VP, IT Finance, previously working at PepsiCo, AmerisourceBergen, and Jacobs. |
|
Carol Carr
Technical Counselor, Executive Services Info-Tech Research Group |
|
|
Scott Fairholm
Executive Counselor, Executive Services Info-Tech Research Group |
|
|
Gokul Rajan
Executive Counselor, Executive Services Info-Tech Research Group |
|
|
Allison Kinnaird
Practice Lead, Infrastructure & Operations Info-Tech Research Group |
|
|
Isabelle Hertanto
Practice Lead, Security & Privacy Info-Tech Research Group |
|
Achieve IT Spending Transparency
Mature your ITFM practice by activating the means to make informed business decisions. |
|
Build Your IT Cost Optimization Roadmap
Develop an IT cost optimization strategy based on your specific circumstances and timeline. |
Eby, Kate. “The Complete Guide to Organizational Maturity: Models, Levels, and Assessments.” Smartsheet, 8 June 2022. Web.
“Financial Management Maturity Model.” National Audit Office, n.d. Accessed 28 Apr. 2023.
“ITFM/TBM Program Maturity Guide.” Nicus Software, n.d. Accessed 28 Apr. 2023.
Jouravlev, Roman. "Service Financial Management: ITIL 4 Practice Guide." Axelos, 2020.
McCarthy, Seamus. “Financial Management Maturity Model: A Good Practice Guide.” Office of the Comptroller & Auditor General, 26 June 2018. Web.
“Principles for Effective Risk Data Aggregation and Risk Reporting.“ Bank for International Settlements, Jan. 2013. Web.
“Role & Influence of the Technology Decision-Maker 2022.” Foundry, 2022. Web.
Stackpole, Beth. “State of the CIO, 2022: Focus turns to IT fundamentals.” CIO, 21 March 2022. Web.
“Tech Spend Pulse.” Flexera, 2022. Web.
Maturity Level |
Definition |
Description |
| Nascent Level 1 |
Inability to consistently deliver financial planning services | ITFM practices are almost inexistent. Only the most basic financial tasks and activities are being performed on an ad hoc basis to fulfill the Finance department’s requests. |
| Cost Operator Level 2 |
Rudimentary financial planning capabilities. | ITFM activities revolve around minimizing the IT budget as much as possible. ITFM practices are not well defined, and IT’s financial view is limited to day-to-day technical operations.
IT is only involved in low complexity decision making, where financial conversations center on general ledger items and IT spending. |
| Trusted Coordinator Level 3 |
Enablement of business through cost-effective supply of technology. | ITFM activities revolve around becoming a proficient and cost-effective technology supplier to business partners.
ITFM practices are in place, with moderate coordination and adherence to execution. Various IT business units coordinate to produce a consolidated financial view focused on business services. IT is involved in moderate complexity decision making, as a technology subject matter expert, where financial conversations center on IT spending in relation to technology services or solutions provided to business partners. |
| Value Optimizer Level 4 |
Effective impact on business performance. | ITFM activities revolve around optimizing existing technology investments to improve both IT and business performance.
ITFM practices are well managed, established, documented, repeatable, and integrated as necessary across the organization. IT’s financial view tie technology investments to lines of business, business products, and business capabilities. Business partners are well informed on the technology mix and drive related discussion. IT is trusted to contribute to complex decision making around existing investments to cost-effectively plan initiatives, as well as enhance business performance. |
| Strategic Partner Level 5 |
Influence on the organization’s strategic direction. | ITFM activities revolve around predicting the outcome of new or potential technology investments to continuously optimize business performance.
ITFM practices are fully optimized, reviewed, and improved in a continuous and sustainable manner, and related execution is tracked by gathering qualitative and quantitative feedback. IT’s financial view is holistic and fully integrated with the business, with an outlook on innovation, growth, and strategic transformation. Business and IT leaders know the financial ramifications of every business and technology investment decision. IT is trusted to contribute to strategic decision making around potential and future investments to grow and transform the business. |
Maturity Level | Definition | Description |
| Nascent Level 1 | Inability to provide any type of financial insight. | ITFM tasks, activities, and functions are not being met in any way, shape, or form. |
| Cost Operator Level 2 | Ability to provide basic financial insights. | There is no dedicated ITFM team.
|
| Trusted Coordinator Level 3 | Ability to provide basic business insights. | A dedicated team is fulfilling essential ITFM tasks, activities, and functions.
|
| Value Optimizer Level 4 | Ability to provide valuable business driven insights. | A dedicated ITFM team with well-defined roles and responsibilities can provide effective advice to IT leaders, in a timely fashion, and positively influence IT decisions. |
| Strategic Partner Level 5 | Ability to influence both technology and business decisions. | A dedicated and highly specialized ITFM team is trusted and valued by both IT and Business leaders.
|
Maturity Level | Definition | Description |
| Nascent Level 1 | Inability to ensure any adherence to rules and regulations. | ITFM frameworks, guidelines, policies, and procedures are not developed nor documented. |
| Cost Operator Level 2 | Ability to ensure basic adherence to rules and regulations. | Basic ITFM frameworks, guidelines, policies, and procedures are in place, developed on an ad hoc basis, with no apparent coherence or complete documentation. |
| Trusted Coordinator Level 3 | Ability to ensure compliance to rules and regulations, as well as accountability across ITFM processes. | Essential ITFM frameworks, guidelines, policies, and procedures are in place, coherent, and documented, aiming to (a) comply with rules and regulations, and (b) provide clear accountability. |
| Value Optimizer Level 4 | Ability to ensure compliance to rules and regulations, as well as structure, transparency, and business alignment across ITFM processes. | ITFM frameworks, guidelines, policies, and procedures are well defined, coherent, documented, and regularly reviewed, aiming to (a) comply with rules and regulations, (b) provide clear accountability, and (c) maintain business alignment. |
| Strategic Partner Level 5 | Ability to:
| ITFM frameworks, guidelines, policies, and procedures are complete, well defined, coherent, documented, continuously reviewed, and improved, aiming to (a) comply with rules and regulations, (b) provide clear accountability, (c) maintain business alignment, and (d) facilitate the decision-making process.
|
Maturity Level | Definition | Description |
| Nascent Level 1 | Inability to deliver IT financial planning and performance output. | ITFM processes and tools are not developed nor documented. |
| Cost Operator Level 2 | Ability to deliver basic IT financial planning output. | Basic ITFM processes and tools are in place, developed on an ad hoc basis, with no apparent coherence or complete documentation. |
| Trusted Coordinator Level 3 | Ability to deliver accurate IT financial output and basic IT performance output in a consistent cadence. | Essential ITFM processes and tools are in place, coherent, and documented, aiming to (a) maintain integrity across activities, tasks, methodologies, data, and reports; (b) deliver IT financial planning and performance output needed by stakeholders; and (c) provide clear accountability. ITFM tools and processes are adopted by the ITFM team and some IT business units but are not fully integrated. |
| Value Optimizer Level 4 | Ability to deliver accurate IT financial planning and performance output at the needed level of detail to stakeholders in a consistent cadence. | ITFM processes and tools are complete, well defined, coherent, documented, continuously reviewed, and improved, aiming to (a) maintain integrity across activities, tasks, methodologies, data, and reports; (b) deliver IT financial planning and performance output needed by stakeholders; (c) provide clear accountability; and (d) facilitate decision-making. ITFM tools and processes are adopted by IT and business partners but are not fully integrated. |
| Strategic Partner Level 5 | Ability to:
| ITFM processes and tools are complete, well defined, coherent, documented, continuously reviewed, and improved, aiming to (a) maintain integrity across activities, tasks, methodologies, data, and reports; (b) deliver IT financial planning and performance output needed by stakeholders; (c) provide clear accountability; and (d) facilitate decision making.
|
Maturity Level | Definition | Description |
| Nascent Level 1 | Inability to provide transparency across technology spending. | ITFM taxonomy and data model are not developed nor documented. |
| Cost Operator Level 2 | Ability to provide transparency and support IT financial planning data, analysis, and reporting needs of finance stakeholders. | ITFM taxonomy and data model are in place, developed on an ad hoc basis, with no apparent coherence or complete documentation, to comply with, and meet the needs of finance stakeholders. |
| Trusted Coordinator Level 3 | Ability to provide transparency and support IT financial planning and performance data, analysis, and reporting needs of IT and finance stakeholders. | ITFM taxonomy and data model are in place, coherent, and documented to meet the needs of IT and finance stakeholders. |
| Value Optimizer Level 4 | Ability to provide transparency and support IT financial planning and performance data, analysis, and reporting needs of IT, finance, business, and executive stakeholders. | ITFM taxonomy and data model are complete, well defined, coherent, documented, continuously reviewed, and improved, aiming to provide (a) a holistic view of IT spending and IT performance, (b) visibility and transparency, (c) flexibility, and (d) valuable insights to facilitate data driven decision making.
|
| Strategic Partner Level 5 | Ability to:
| ITFM taxonomy and data model are complete, well defined, coherent, documented, continuously reviewed, and improved, aiming to provide (a) a holistic view of IT spending and IT performance, (b) visibility and transparency, (c) flexibility, and (d) valuable insights to facilitate data driven decision making.
|
Maturity Level | Definition | Description |
| Nascent Level 1 | Inability to provide accurate and complete across technology spending. | ITFM data needs and requirements are not understood. |
| Cost Operator Level 2 | Ability to provide accurate, but incomplete IT financial planning data to meet the needs of finance stakeholders. | Technology spending data is extracted, transformed, and loaded on an ad hoc basis to meet the needs of finance stakeholders. |
| Trusted Coordinator Level 3 | Ability to provide accurate and complete IT financial planning data to meet the needs of IT and finance stakeholders, but IT performance data remain incomplete. | IT financial planning data is extracted, transformed, and loaded in a regular cadence to meet the needs of IT and finance stakeholders.
|
| Value Optimizer Level 4 | Ability to provide accurate and complete IT financial planning and performance data to meet the needs of IT, finance, business, and executive stakeholders. | ITFM data needs and requirements are understood.
|
| Strategic Partner Level 5 | Ability to provide accurate and complete IT financial planning and performance data real time and when needed by IT, finance, business, and executive stakeholders. | ITFM data needs and requirements are understood.
|
Maturity Level | Definition | Description |
| Nascent Level 1 | Inability to provide any type of financial insight. | ITFM analysis and reports are not developed nor documented. |
| Cost Operator Level 2 | Ability to provide basic financial insights. | IT financial planning analysis is conducted on an ad hoc basis to meet the needs of finance stakeholders. |
| Trusted Coordinator Level 3 | Ability to provide basic financial planning and performance insights to meet the needs of IT and finance stakeholders. | IT financial planning and performance analysis are methodical and rigorous, as defined in related control documents (guideline, policies, procedures, etc.).
|
| Value Optimizer Level 4 | Ability to provide practical insights and useful recommendations as needed by IT, finance, business, and executive stakeholders to facilitate business decision making around technology investments. | ITFM analysis and reports support business decision making around technology investments.
|
| Strategic Partner Level 5 | Ability to provide practical insights and useful recommendations as needed by IT, finance, business, and executive stakeholders to facilitate strategic decision making. | ITFM analysis and reports support strategic decision making.
|
Maturity Level | Definition | Description |
| Nascent Level 1 | Inability of organization stakeholders to communicate and understand each other. | The organization stakeholders including IT, finance, business, and executives do not understand one another, and cannot speak the same language. |
| Cost Operator Level 2 | Ability to understand business and finance requirements. | IT understands and meets business and financial planning requirements but does not communicate in a similar language.
|
| Trusted Coordinator Level 3 | Ability to understand the needs of different stakeholders including IT, finance, business, and executives and take part in decision making around technology spending. | The organization stakeholders including IT, finance, business, and executives understand each other’s needs, but do not communicate in a common language.
|
| Value Optimizer Level 4 | Ability to communicate in a common vocabulary across the organization and take part in business decision making around technology investments. | The organization stakeholders including IT, finance, business, and executives communicate in a common vocabulary and understand one another.
|
| Strategic Partner Level 5 | Ability to communicate in a common vocabulary across the organization and take part in strategic decision making. | The organization stakeholders including IT, finance, business, and executives communicate in a common vocabulary and understand one another.
|
Maturity Level | Definition | Description |
| Nascent Level 1 | Inability of organization stakeholders to acquire knowledge. | Educational resources are inexistent. |
| Cost Operator Level 2 | Ability to acquire financial knowledge and understand financial concepts. | IT leaders have access to educational resources to gain the financial knowledge necessary to perform their duties. |
| Trusted Coordinator Level 3 | Ability to acquire financial and business knowledge and understand related concepts. | IT leaders and their respective teams have access to educational resources to gain the financial and business knowledge necessary to perform their duties.
|
| Value Optimizer Level 4 | Ability to acquire knowledge, across technology, business, and finance as needed by different organization stakeholders, and the leadership understand concepts across these various domains. | Stakeholders including IT, finance, business, and executives have access to various educational resources to gain knowledge in different domains as needed.
|
| Strategic Partner Level 5 | Ability to acquire knowledge, and understand concepts across technology, business, and finance as needed by different organization stakeholders. | The organization promotes continuous learning through well designed programs including training, mentorship, and academic courses. Thus, stakeholders including IT, finance, business, and executives have access to various educational resources to gain knowledge in different domains as needed.
|
Maturity Level | Definition | Description |
| Nascent Level 1 | Inability to provide and foster an environment of collaboration and continuous improvement. | Stakeholders including IT, finance, business, and executives operate in silos, and collaboration between different teams is inexistent. |
| Cost Operator Level 2 | Ability to provide an environment of cooperation to meet the needs of IT, finance, and business leaders. | IT, finance, and business leaders cooperate to meet financial planning requirements as necessary to perform their duties. |
| Trusted Coordinator Level 3 | Ability to provide and foster an environment of collaboration across the organization. | IT, finance, and business collaborate on various initiatives. ITFM employees are trusted and supported by their stakeholders (IT, finance, and business). |
| Value Optimizer Level 4 | Ability to provide and foster an environment of collaboration and continuous improvement, where employees across the organization feel trusted, supported, empowered, and valued. | Stakeholders including IT, finance, business, and executives support and promote continuous improvement, transparency practices, and collaboration across the organization.
|
| Strategic Partner Level 5 | Ability to provide and foster an environment of collaboration and continuous improvement, where leaders are willing to change, and employees across the organization feel trusted, supported, empowered, and valued. | Stakeholders including IT, finance, business, and executives support and promote continuous improvement, transparency practices, and collaboration across the organization.
|
The challenge
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Our concise executive brief shows you why you should develop a sound business continuity practice in your company. We'll show you our methodology and the ways we can help you in completing this.
Choose a medium-sized department and build a team. Identify that department's processes, dependencies, and alternatives.
Define an objective impact scoring scale for your company. Have the business estimate the impact of downtime and set your recovery targets.
The need for clarity is critical. In times when you need the plans, people will be under much higher stress. Build the workflow for the steps necessary to rebuild. Identify gaps and brainstorm on how to close them. Prioritize solutions that mitigate the remaining risks.
Present the results of the pilot and propose the next steps. Assign BCM teams or people within each department. Update and maintain the overall BCMS documentation.
These can help with the creation of your BCP.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Read our executive brief to understand why you should develop a PPM strategy and understand how our methodology can help you. We show you how we can support you.
Ensure your strategy is a cultural fit or cultural-add for your company.
Use the advice and tools in this stage to align the PPM processes.
Use the inputs from the previous stages and add a cost-benefit analysis and tool recommendation.
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.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Analyze the scope of the IoT and the three most prominent enterprise use cases.
Develop and prioritize use cases for the IoT using Info-Tech’s IoT Initiative Framework.
Present the IoT initiative to stakeholders and understand the way forward for the IoT initiative.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
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.
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.
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.
Choose the right mobile platform.
Shortlist your mobile delivery solution and desired features and services.
A chosen mobile platform that meets user and enterprise needs.
Candidate mobile delivery solutions that meet your delivery needs and capacity of your teams.
1.1 Select your platform approach.
1.2 Shortlist your mobile delivery solution.
1.3 Build your feature and service lists.
Desired mobile platform approach.
Shortlisted mobile delivery solutions.
Desired list of vendor features and services.
Design the mobile application minimal viable product (MVP).
Create your mobile roadmap.
An achievable and valuable mobile application that is scalable for future growth.
Clear intent of business outcome delivery and completing mobile delivery activities.
2.1 Define your MVP release.
2.2 Build your roadmap.
MVP design.
Mobile delivery roadmap.
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.
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.
3.1 Generate user personas with empathy maps.
3.2 Build your mobile application canvas.
3.3 Build your mobile backlog.
User personas.
Mobile objectives and metrics.
Mobile opportunity backlog.
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.
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.
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.
List of mobile features to enable the desired mobile experience.
System current assessment.
Mobile application quality definition.
Verification to proceed with mobile delivery.
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.
Andrew Kum-Seun
Senior Research Analyst,
Application Delivery and Application Management
Info-Tech Research Group
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.
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
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
Source: Broadridge, 2022
To learn more, visit Info-Tech's Define Your Digital Business Strategy blueprint.
|
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. |
|
|
Roaming Worker |
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. |
|
|
Roaming Worker |
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. |
|
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 want sophisticated mobile applications like what they see their peers and competitors use.
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
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.
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.
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.
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.
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.
First, deliver the experience end users want and expect by designing the application against digital application principles.
Business Value |
|
|---|---|
|
Continuous modernization |
|
|
|
|
|
|
|
|
|
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.
To learn more, visit Info-Tech's Make the Case for Product Delivery blueprint.
|
WORKFLOW |
|
|---|---|
| 1. Capture Your User Personas and Journey |
|
| 2. Select Your Platform |
|
| 3. Shortlist Your Solutions |
|
Strategic Perspective
|
|||
|---|---|---|---|
|
1. End-User Perspective |
End User Needs |
||
|
|
|
|
|
Native User Experience |
|||
|
|||
|
2. Platform Perspective |
Technical Requirements |
||
|
Security |
Performance |
Integration |
|
|
Mobile Platform |
|||
|
3. Solution Perspective |
Vendor Support |
||
|
Services |
Stack Mgmt. |
Quality & Risk |
|
|
Mobile Delivery Solutions |
|||
For a mobile application to be meaningful, the functions, aesthetics and content must be:
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.
Source: Marky Roden, Xomino, 2018
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.
"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.
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:
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 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 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 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.
|
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. |
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 |
|
|
Hybrid / Cross-Platform |
|
|
Native |
|
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 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.
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:
To learn more, visit Info-Tech's Modernize Your SDLC blueprint.
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:
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.
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.
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.
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.
| 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.
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.
Communicate the justification of your approach to mobile applications with Info-Tech's Mobile Application Delivery Communication Template:
|
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 |
|
|
"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."
| 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.
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 |
|
|
|
|
|
Choose Your Mobile Platform and Tools
1.1.1 Generate user personas with empathy maps
1.1.2 Build your mobile application canvas
1.1.3 Build your mobile backlog
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.
For a mobile application to be a meaningful experience, the functions, aesthetics and content must be:
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.
Source: Marky Roden, Xomino, 2018
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.
An application's UI and function both contribute to UX, but they do so in different ways.
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.
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 Relevance & Modern UI Design Content Layout |
|---|---|
|
Critical Areas of Mobile UX That Are Often Ignored |
Web Infrastructure Human Behavior Coding Language Cross-Platform Compatibility Application Quality Adoption & Retention Application Support |
Personas are detailed descriptions of the targeted audience of your mobile application. It represents a type of user in a particular scenario. Effective personas:
They are important because they help:
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:
To learn more, visit Info-Tech's Use Experience Design to Drive Empathy with the Business blueprint.
|
Input |
Output |
|---|---|
|
|
| Materials | Participants |
|
|
When refining your mobile problem statement, attempt to answer the following four questions:
There are many ways of writing problem statements, a clear approach follows the format:
Adapted from: "Design Problem Statements – What and How to Frame Them"
When thinking about a vision statement, think about:
There are different statement templates available to help form your vision statements. Some include:
(Numbers 2-4 from: How to define a product vision)
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.
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:
See our Build a Value Measurement Framework blueprint for more information about business value definition.
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:
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
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.
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.
USE THE PROGRAM DIAGNOSTIC TO:
INTEGRATE DIAGNOSTIC RESULTS TO:
|
Mobile Application Initiative Name |
Owner: |
NAME |
|---|---|---|
|
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.
Download the Mobile Application Delivery Communication Template
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Mobile Application Initiative Name | Owner: | NAME |
|---|---|---|
Problem Statement | Vision | |
[Problem Statement] | [Vision] | |
Business Goals & Metrics | Capabilities, Processes & Application Systems | |
[Business Goal 1, Metric] | [Business Capability] | |
Personas/Customers/Users | Stakeholders | |
[User 1] | [Stakeholder 1] | |
Your backlog gives you a holistic understanding of the demand for mobile applications across your organization.
|
Opportunities |
|
|---|---|
|
External Sources |
Internal Sources |
|
|
|
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. |
|
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
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
(Source Perforce, 2018)
See our Deliver on Your Digital Product Vision for more information on backlog practices.
1.2.1 Discuss your mobile needs
1.2.2 Conduct a technical assessment
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.
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.
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. |
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.
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
|
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 |
|
|
|
|
|
|
Legend:
Bold – Touchpoint
* – Activities or Touchpoints That Can Benefit with Mobile
Download the Mobile Application Delivery Communication Template
Workflow | Trigger | Step 1 | Step 2 | Step 3 | Step 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.
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:
See our Enhance Your Solution Architecture for more information.
Download the Mobile Application Delivery Communication Template
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
| 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) |
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) |
1.3.1 Define mobile application quality
1.3.2 Verify your decision to deliver mobile applications
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.
See our Build a Software Quality Assurance Program for more information.
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.
Mobile attacks can come from various vectors:
|
Attack Surface: Mobile Device |
Attack Surface: Network |
Attack Surface: Data Center |
|---|---|---|
|
Browser: System: Phone: Apps: |
|
Web Server: Database: |
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 |
|
|
|
|
Roaming Worker (Engineer) |
|
|
|
Fine tune your enterprise mobile applications using optimization techniques to improve performance across the full mobile stack.
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).
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.
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:
See our Build Effective Enterprise Integration on the Back of Business Process for more information.
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
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.
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
| 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:
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. |
Download the Mobile Application Delivery Communication Template
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
| Quality Attribute | Developer | Operations & Support Team | End Users |
|---|---|---|---|
Usability |
|
|
|
Security |
|
|
|
| Availability |
|
|
|
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
| 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) |
2.1.1 Select your platform approach
"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:
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:
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:
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.
| Web | Hybrid | Cross-Platform | Native | ||||
|---|---|---|---|---|---|---|---|
Pros | Cons | Pros | Cons | Pros | Cons | Pros | Cons |
|
|
|
|
|
|
|
|
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.
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.
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.
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. |
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.
See our Enhance Your Solution Architecture for more information.
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.
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:
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:
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.
Drive your mobile platform selection against user-centric needs (e.g. device access, aesthetics) and enterprise-centric needs (e.g. security, system performance).
Web
Hybrid / Cross-Platform
Native
Download the Mobile Application Delivery Communication Template
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
| 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) |
| 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) |
| 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) |
| 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) |
| 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 |
2.2.1 Shortlist your mobile delivery solution
2.2.2 Build your feature and service lists
| 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
|
Cons
|
Pros
|
Cons
|
|
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
|
Cons
|
Pros
|
Cons
|
|
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. |
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 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.
React Native, NativeScript, Xamarin Forms, .NET MAUI, Flutter, Kotlin Multiplatform Mobile, jQuery Mobile, Telerik, Temenos Quantum
Cordova Project, Sencha Touch, Electron, Ionic, Capacitor, Monaca, Voltbuilder
Web Development Frameworks (React, Angular, Vue, Express, Django, Rails, Spring, Ember, Backbone, Bulma, Bootstrap, Tailwind CSS, Blade)
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.
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.
The various services needed to support mobile delivery and enable continuous delivery, such as:
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.
Source: "HCL Volt MX", HCL.
Download the Mobile Application Delivery Communication Template
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
| 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) |
| 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 |
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.
To learn more, visit Info-Tech's Modernize Your SDLC blueprint.
|
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 |
Overcome the Common Challenges Faced with Building Mobile Applications
|
Common Challenges with Digital Applications |
Suggested Solutions |
|---|---|
|
|
Source: DronaHQ, 2021
| 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 |
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.
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 |
|---|---|
|
|
| Materials | Participants |
|
|
| 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.
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.
2.3.1 Define your MVP release
2.3.2 Build your roadmap
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.
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
MVP Name | Owner: | NAME |
|---|---|---|
| MVP Theme/Goals | ||
[Theme / Goal] | ||
Use Cases | Value | Costs |
[Use Case 1] | [Business Value 1] | [Cost Item 1] |
Impacted Personas | Impacted Workflows | Stakeholders |
[Persona 1] | [Workflow 1] | [Stakeholder 1] |
To learn more, visit Info-Tech's Deliver on Your Digital Product Vision blueprint.
Explains the overarching goal of work being done to a specific audience.
Categorizes the different groups delivering the work on the product.
Explains the artifacts, or items of work, that will be delivered.
Explains when the work will be delivered within your timeline.
To learn more, visit Info-Tech's Deliver on Your Digital Product Vision blueprint.
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?
Adapted From: "Tips for Agile product roadmaps & product roadmap examples," Scrum.org, 2017
Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
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 |
|
Sign off on cost and benefit projections |
|
Executives and decision makers |
|
Revisions, edits, and approval |
|
IT teams |
|
Clarity of vision and direction and readiness for delivery |
|
Business workers |
|
Verification on proposed changes and feedback |
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:
See our Build a Value Measurement Framework blueprint for more information about business value definition.
| 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. |
| 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
Performance Optimization
API Development
|
|
Contact your account representative for more information
workshops@infotech.com
1-888-670-8889
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.
"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.
Source: MaLavolta, Ivono, 2012.
Source: Sahay, Apurvanand et al., 2020
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
The focus on diversity, equity, and inclusion (DEI) initiatives spans the entire organization beyond just HR. Learn which DEI efforts are underway with IT.
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.
When the pandemic hit, organizations were significantly concerned about how employees were doing. Learn more about wellbeing.
Upskilling and finding sought after skills were challenging before the pandemic. How has it changed since? Learn more about skills priorities.
The pandemic and remote work has affected performance. Learn about how uncertainty has impacted performance management.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Learn about machine biases, how and where they arise in AI systems, and how they relate to human cognitive and societal biases.
Learn about data biases and how to mitigate them.
Learn about model biases and how to mitigate them.
Learn about approaches for proactive and effective bias prevention and mitigation.
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.
Understand your organization’s maturity with respect to data and analytics in order to maximize workshop value.
Workshop content aligned to your organization’s level of maturity and business objectives.
1.1 Execute Data Culture Diagnostic.
1.2 Review current analytics strategy.
1.3 Review organization's business and IT strategy.
1.4 Review other supporting documentation.
1.5 Confirm participant list for workshop.
Data Culture Diagnostic report.
Develop a good understanding of machine biases and how they emerge from human cognitive and societal biases. Learn about the machine learning process and how it relates to machine bias.
Select an ML/AI project and complete a bias risk assessment.
A solid understanding of algorithmic biases and the need to mitigate them.
Increased insight into how new technologies such as ML and AI impact organizational risk.
Customized bias risk assessment template.
Completed bias risk assessment for selected project.
2.1 Review primer on AI and machine learning (ML).
2.2 Review primer on human and machine biases.
2.3 Understand business context and objective for AI in your organization.
2.4 Discuss selected AI/ML/data science project or use case.
2.5 Review and modify bias risk assessment.
2.6 Complete bias risk assessment for selected project.
Bias risk assessment template customized for your organization.
Completed bias risk assessment for selected project.
Learn about data biases: what they are and where they originate.
Learn how to address or mitigate data biases.
Identify data biases in selected project.
A solid understanding of data biases and how to mitigate them.
Customized Datasheets for Data Sets Template.
Completed datasheet for data sets for selected project.
3.1 Review machine learning process.
3.2 Review examples of data biases and why and how they happen.
3.3 Identify possible data biases in selected project.
3.4 Discuss “Datasheets for Datasets” framework.
3.5 Modify Datasheets for Data Sets Template for your organization.
3.6 Complete datasheet for data sets for selected project.
Datasheets for Data Sets Template customized for your organization.
Completed datasheet for data sets for selected project.
Learn about model biases: what they are and where they originate.
Learn how to address or mitigate model biases.
Identify model biases in selected project.
A solid understanding of model biases and how to mitigate them.
Customized Model Cards for Model Reporting Template.
Completed model card for selected project.
4.1 Review machine learning process.
4.2 Review examples of model biases and why and how they happen.
4.3 Identify potential model biases in selected project.
4.4 Discuss Model Cards For Model Reporting framework.
4.5 Modify Model Cards for Model Reporting Template for your organization.
4.6 Complete model card for selected project.
Model Cards for Model Reporting Template customized for your organization.
Completed model card for selected project.
Review mitigation approach and best practices to control machine bias.
Create mitigation plan to address machine biases in selected project. Align with enterprise risk management (ERM).
A solid understanding of the cultural dimension of algorithmic bias prevention and mitigation and best practices.
Drafted plan to mitigate machine biases in selected project.
5.1 Review and discuss lessons learned.
5.2 Create mitigation plan to address machine biases in selected project.
5.3 Review mitigation approach and best practices to control machine bias.
5.4 Identify gaps and discuss remediation.
Summary of challenges and recommendations to systematically identify and mitigate machine biases.
Plan to mitigate machine biases in selected project.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Understand how the basic operational framework of CLM will ensure cost savings, improved collaboration, and constant CLM improvement.
Understand the two phases of CLM and the ten stages that make up the entire 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.
Identify current CLM processes.
Learn the CLM operational framework.
Documented overview of current processes and stakeholders.
1.1 Review and capture your current process.
1.2 Identify current stakeholders.
1.3 Learn the operational framework of CLM.
1.4 Identify current process gaps.
Existing CLM Process Worksheet
Dive into the two phases of CLM and the ten stages of a robust system.
A deep understanding of the required components/stages of a CLM system.
2.1 Understand the two phases of CLM.
2.2 Learn the ten stages of CLM.
2.3 Assess your CLM maturity state.
2.4 Identify and assign stakeholders.
CLM Maturity Assessment
CLM RASCI Diagram
"Contract lifecycle management (CLM) is a vital process for small and enterprise organizations alike. Research shows that all organizations can benefit from a contract management process, whether they have as few as 25 contracts or especially if they have contracts numbering in the hundreds.
A CLM system will:
If you’re not managing your contracts, you aren’t capitalizing on your investment with your vendors and are potentially exposing your organization to contract and monetary risk."
- Ted Walker
Principal Research Advisor, Vendor Management Practice
Info-Tech Research Group
FIS’ business groups were isolated across the organization and used different agreements, making contract creation a long, difficult, and manual process.
The Solution: Automating and Streamlining the Contract Management Process
A robust CLM system solved FIS’ various contract management needs while also providing a solution that could expand into full quote-to cash in the future.
Dollars Saved |
Upfront dollars saved
|
|---|---|
Time Saved |
Time saved, which can be done in several areas
|
Pitfalls Avoided |
Number of pitfalls found and avoided, such as
|
of companies can’t locate up to 10% of their contracts.
Source: TechnologyAdvice, 2019
of companies’ annual revenue is lost because of poor contract management practices.
Source: IACCM, 2019
still track contracts in shared drives or email folders.
Source: “State of Contract Management,” SpringCM, 2018
"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."
1. Master the Operational Framework |
2. Understand the Ten Stages of CLM |
|
|---|---|---|
| Best-Practice Toolkit |
1.1 Understand the operational framework components. 1.2 Review your current framework. 1.3 Create a plan to implement or enhance existing processes. |
2.1 Understand the ten stages of CLM. 2.2 Review and document your current processes. 2.3 Review RASCI chart and assign internal ownership. 2.4 Create an improvement plan. 2.5 Track changes for measurable ROI. |
| Guided Implementations |
|
|
| Onsite Workshop | Module 1: Review and Learn the Basics
|
Module 2 Results:
|
Phase 1 Outcome:
|
Phase 2 Outcome:
|
Contact your account representative or email Workshops@InfoTech.com for more information.
| Workshop Day 1 | Workshop Day 2 | |
|---|---|---|
| Activities | Task – Review and Learn the Basics |
Task – Learn More and Plan |
1.1 Review and capture your current process. 1.2 Identify current stakeholders. 1.3 Learn the operational framework of contract lifecycle management. 1.4 Identify current process gaps. |
2.1 Understand the two phases of CLM. 2.2 Learn the ten stages of CLM. 2.3 Assess your CLM maturity. 2.4 Identify and assign stakeholders. 2.5 Discuss ROI. 2.6 Summarize and next steps. |
|
| Deliverables |
|
|
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: Master the Operational Framework of Contract Lifecycle Management |
||
|---|---|---|
Step 1.1: Document your Current CLM Process |
Step 1.2: Read and Understand the Operational Framework |
Step 1.3: Review Solution Options |
Start with an analyst kick-off call:
|
Review findings with analyst:
|
Finalize phase deliverable:
|
Then complete these activities…
|
||
With these tools & templates:
|
||
Phase 1 Results:
|
||
That’s where contract lifecycle management (CLM) comes in.
Putting a contract manager in place to manage the CLM project will accelerate the improvements and provide faster returns to the organizations. Reference Info-Tech’s Contract Manager Job Description template as needed.
Paper is still alive and doing very well at slowing down the many stages of the contract process.
Most organizations analyze their contracts in two ways:
This is the ultimate goal of a robust contract management system!
Goal: Document your existing CLM processes (if any) and who owns them, who manages them, etc.
Interview internal business unit decision makers, stakeholders, Finance, Legal, CIO, VMO, Sales, and/or Procurement to understand what’s currently in place.
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: Understand the Ten Stages of Contract Lifecycle Management Proposed Time to Completion: 1-10 weeks | |
|---|---|
Step 2.1: Assess CLM Maturity | Step 2.2: Complete a RASCI Diagram |
Start with an analyst kick-off call:
| Review findings with analyst:
|
Then complete these activities…
| Then complete these activities…
|
With these tools & templates:
| With these tools & templates:
|
Phase 2 Results & Insights:
| |
The steps are divided into two phases, pre-execution and post-execution.
Contract lifecycle management begins with the contract requesting process, where one party requests for or initiates the contracting process and subsequently uses that information for drafting or authoring the contract document. This is usually the first step in CLM.
Requests for contracts can come from various sources:
At this stage, you need to validate if a non-disclosure agreement (NDA) is currently in place with the other party or is required before moving forward. At times, adequate NDA components could be included within the contract or agreement to satisfy corporate confidentiality requirements.
For a comprehensive list of terms and conditions, see our Software Terms & Conditions Evaluation Tool within Master Contract Review and Negotiation for Software Agreements.
The importance of risk review can not be understated. The contract or agreement must be reviewed by several stakeholders who can identify risks to the organization within the contract.
Collectively, this is known as contract visibility.
The approval stage can be a short process if policies and procedures are already in place. Most organizations will have defined delegation of authority or approval authority depending on risk, value of the contract, and other corporate considerations.
Saving the different versions of a contract during negotiations will save time, provide reassurance of agreed terms as you move through the process, and provide reference for future negotiations with the vendor.
Process flow provisions should made for potential rejection of the contract by signatories, looping the contract back to the appropriate stage for rework or revision.
Most repositories are some type of database:
Several important features of an electronic repository should be considered:
Establishing an effective repository will be key to providing measurable value to the organization and saving large amounts of time for the business unit.
Planning for future needs by investing a little more money into a better, more robust repository could pay bigger dividends to the VMO and organization while providing a higher ROI over time as advanced functionality is deployed.
Additional optimization tactics:
Use the CLM Maturity Assessment Tool to outline where your organization is at each stage of the process.
Goal: Identify and measure your existing CLM processes, if any, and provide a maturity value to each stage. The resulting scores will provide a maturity assessment of your CLM.
Goal: Identify who in your organization is primarily accountable and involved in each stage of the CLM process.
Engage internal business unit decision makers, stakeholders, Finance, Legal, CIO, VMO, Sales, and Procurement as required to validate who should be involved in each stage.
Decision-maker concerns arise from a common misunderstanding – that is, a fundamental failure to appreciate the true source of contract management value. This misunderstanding goes back many years to the time when analysts first started to take an interest in contract management and its automation. Their limited experience (primarily in retail and manufacturing sectors) led them to think of contract management as essentially an administrative function, primarily focused on procurement of goods. In such environments, the purpose of automation is focused on internal efficiency, augmented by the possibility of savings from reduced errors (e.g. failing to spot a renewal or expiry date) or compliance (ensuring use of standard terms).
Today’s CLM systems and processes can provide ROI in several areas in the business.
Research on ROI of CLM software shows significant hard cost savings to an organization. For example, a $10 million company with 300 contracts valued at $3 million could realize savings of $83,400 and avoid up to $460,000 in lost revenues. (Derived from: ACCDocket, 2018)
This is an often-discussed question. Research suggests that there is no definitive answer, as there are several variables.
Organizations needs to review what makes the best business sense for them based on several considerations and then decide where CLM belongs.
35% of law professionals feel contract management is a legal responsibility, while 45% feel it’s a business responsibility and a final 20% are unsure where it belongs. (Source: “10 Eye-Popping Contract Management Statistics,” Apttus, 2018)
This too is a difficult question to answer definitively. Again, there are several variables to consider. As well, several solutions are available, and this is not a one-size-fits-all scenario.
As with who should own the CLM process, organizations must review the various CLM software solutions available that will meet their current and future needs and then ask, “What do we need the system to do?”
When considering what type of solution to choose, prioritize what needs to been done or improved. Sometimes solutions can be deployed in phases as an “add-on” type modules.
This project can fit your organization’s schedule:
Master Contract Review and Negotiation
Optimize spend with significant cost savings and negotiate from a position of strength.
Manage Your Vendors Before They Manage You
Maximize the value of vendor relationships.
Burla, Daniel. “The Must Know Of Transition to Dynamics 365 on Premise.” Sherweb, 14 April 2017. Web.
Anand, Vishal, “Strategic Considerations in Implementing an End-to-End Contract Lifecycle Management Solution.” DWF Mindcrest, 20 Aug. 2016. Web.
Alspaugh, Zach. “10 Eye-Popping Contract Management Statistics from the General Counsel’s Technology Report.” Apttus, 23 Nov. 2018. Web.
Bishop, Randy. “Contract Management is not just a cost center.” ContractSafe, 9 Sept. 2019. Web.
Bryce, Ian. “Contract Management KPIs - Measuring What Matters.” Gatekeeper, 2 May 2019. Web.
Busch, Jason. “Contract Lifecycle Management 101.” Determine. 4 Jan. 2018. Web.
“Contract Management Software Buyer's Guide.” TechnologyAdvice, 5 Aug. 2019. Web.
Dunne, Michael. “Analysts Predict that 2019 will be a Big Year for Contract Lifecycle Management.” Apttus, 19 Nov. 2018. Web.
“FIS Case Study.” Apttus, n.d. Web.
Gutwein, Katie. “3 Takeaways from the 2018 State of Contract Management Report.” SpringCM, 2018. Web.
“IACCM 2019 Benchmark Report.” IAACM, 4 Sept. 2019. Web.
Linsley, Rod. “How Proverbial Wisdom Can Help Improve Contract Risk Mitigation.” Gatekeeper, 2 Aug. 2019. Web.
Mars, Scott. “Contract Management Data Extraction.” Exari, 20 June 2017. Web.
Rodriquez, Elizabeth. “Global Contract Life-Cycle Management Market Statistics and Trends 2019.” Business Tech Hub, 17 June 2017. Web.
“State of Contract Management Report.” SpringCM, 2018. Web.
Teninbaum, Gabriel, and Arthur Raguette. “Realizing ROI from Contract Management Technology.” ACCDocket.com, 29 Jan. 2018. Web.
Wagner, Thomas. “Strategic Report on Contract Life cycle Management Software Market with Top Key Players- IBM Emptoris, Icertis, SAP, Apttus, CLM Matrix, Oracle, Infor, Newgen Software, Zycus, Symfact, Contract Logix, Coupa Software.” Market Research, 21 June 2019. Web.
“What is Your Contract Lifecycle Management (CLM) Persona?” Spend Matters, 19 Oct. 2017. Web.
Asset Management, Configuration Management, Lifecycle Management
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Assess the organization’s readiness for change and evaluate the PMO’s OCM capabilities.
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.
Ensure stakeholders are engaged and ready for change by developing effective communication, transition, and training plans.
Determine accountabilities and establish a process for tracking business outcomes after the project team has packed up and moved onto the next project.
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.
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.
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.
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.
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.
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
Analyze the impact of the change across various dimensions of the business.
Develop a strategy to manage change impacts to best ensure stakeholder adoption.
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.
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.
Sponsorship Action Plan
Organizational Change Management Capabilities Assessment
Risk and Opportunity Assessment
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.
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.
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.
RACI table
Stakeholder Analysis
Engagement Plan
Communications plan requirements
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.
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.
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.
Training Plan
Resistance Plan
Communications Plan
Transition Plan
Establish post-project benefits tracking timeline and commitment plans.
Institute a playbook for managing organizational change, including:
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.
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.
Lessons learned
Organizational Change Capability Assessment
Organizational Change Management Playbook
PMOs, if you don't know who is responsible for org change, it's you.
"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
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.
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…
…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)
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:
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.
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.
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
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)
IT Processes Ranked by Effectiveness:
IT Processes Ranked by Importance:
Based on 3,884 responses to Info-Tech’s Management and Governance Diagnostic, June 2016
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)
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
#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)
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.
"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.
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.
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.
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.
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.
| 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.
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 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.
15% - The average costs for effective OCM are 10%–15% of the overall project budget. (AMR Research)
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)
Industry Manufacturing
Source Info-Tech Client
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.
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.
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.
“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
| 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 |
|
|
|
|
|
| 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 |
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
|
Assess OCM Capabilities
|
Analyze Impact of the Change
|
Develop Engagement & Transition Plans
|
Institute an OCM Playbook
|
| Deliverables |
|
|
|
|
|
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.
Proposed Time to Completion (in weeks): 1 week
Start with an analyst kick off call:
Then complete these activities…
With these tools & templates:
Work with an analyst to:
Then complete these activities…
With these tools & templates:
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.
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.
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:
Download Info-Tech’s 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.
Tab 3 of the Assessment tool shows your capabilities graph.
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 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.
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.
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:
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.
|
Strengths
|
Weaknesses
|
|
Opportunities
|
Threats
|
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.
| What conditions are necessary for OCM to succeed? | How will success be defined? |
|---|---|
|
|
|
|
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 |
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.
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.
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:
|
Organizational change management is required for projects that require people to:
|
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.
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 |
|
|
|
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.
What is the project changing?
How will it work?
What are the implications of doing nothing?
What are the phases in execution?
What is the desired outcome?
What can be measured? How?
When should it be measured?
List the goals.
Align with business and IT goals.
List the costs:
Software costs
Hardware costs
Implementation costs
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 |
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.
| 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.
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.
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)
Medium-Large (e.g. business process initiative)
Complex Transformational (e.g. business model initiative, company reorg)
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 |
Use Info-Tech’s Transition Team Communications Template to help communicate the outcomes of this step.
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
Industry Natural Resources
Source Interview
"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
Take Info-Tech’s OCM capabilities questionnaire and receive custom analyst recommendations concerning next steps.
Work with a seasoned analyst to assess your PMO’s strengths, weaknesses, opportunities, and threats to becoming 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.
Receive custom analyst insights on rightsizing your OCM planning efforts based on project size, timeline, and resource availability.
Harness analyst experience to develop a project-specific timeline for the PMO’s change management activities to better plan your efforts and resources.
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.
Proposed Time to Completion (in weeks): 1 week
Discuss these issues with an analyst:
Then complete these activities…
With these tools & templates:
Work with an analyst to:
Then complete these activities…
With these tools & templates:
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.
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.”
Are your sponsors:
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.
| 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
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.
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:
"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.
Using a whiteboard to capture the discussion, address the 5 levels of change impact covered on the previous slide.
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
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.
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
| 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
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)
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:
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.
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.
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.
Download Info-Tech’s Organizational Change Impact Analysis Tool.
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.
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:
Stakeholder management covers:
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
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.
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
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. |
See the next slide for an accompanying screenshot of a change impact table from tab 4 of the Analysis Tool.
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.
Based upon your assessment of each individual impact, the Analysis Tool will provide you with an “Overall Impact Rating” in tab 5.
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
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).
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
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.
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.
| 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 |
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.
Work with an analyst to exercise your storytelling muscles, building out a process to help make the case for change throughout the organization.
Utilize analyst experience to help develop a sponsorship action plan to help facilitate more engaged change project sponsors.
Get an analyst perspective on how each impact may affect different stakeholders in order to assist with the project and OCM planning process.
Rightsize your response to change impacts by developing a game plan to mitigate each one according to adoption likelihood.
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.
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.
Proposed Time to Completion (in weeks): 4 to 6 weeks
Discuss these issues with analyst:
Then complete these activities…
With these tools & templates:
Discuss these issues with analyst:
Then complete these activities…
With these tools & templates:
Discuss these issues with analyst:
Then complete these activities…
With these tools & templates:
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.
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."
How to manage change in organizations of today and the future:
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.
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.
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.
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)
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.
Download Info-Tech’s Stakeholder Engagement Workbook.
The engagement plan is a structured and documented approach for:
Download Info-Tech’s Stakeholder Engagement Workbook.
Refer to your project level assessment from 1.2.2:
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.
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.
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.
Define key stakeholders (or stakeholder groups) who are affected by the project or are in positions to enable or block change.
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:
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.
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.
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.
| 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.
| 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.
| 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).
| 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
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.
| 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.
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.
This is a screenshot of the “Stakeholder Analysis” from tab 5 of the Workbook. The four quadrants of the map are:
Top Quadrants: Supporters
Bottom Quadrant: Blockers
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).
After completing this section you will have a realistic, effective, and adaptable transition plan that includes:
These activities will enable you to:
"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."
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.
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.
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 |
|
|||
| Pilot Go-Live |
|
|||
| Full Rollout Approval |
|
|||
| Full Rollout |
|
|||
| Benefits Assessment |
|
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)
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.
Based on Don Kelley and Daryl Conner’s Emotional Cycle of Change.
Identify critical points in the change curve:
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
|
Incentivize
|
Empathize
|
Educate
|
Inspire
|
| 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. |
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.
"Instead of resisting any emotion, the best way to dispel it is to enter it fully, embrace it and see through your resistance."
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:
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.
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.
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 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. |
| 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. |
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."
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.
"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."
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.
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? | |||
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.
1=Strongly Disagree, 2=Disagree, 3=Somewhat Disagree, 4=Somewhat Agree, 5=Agree, 6=Strongly Agree
1=Very Negative, 2=Negative, 3=Somewhat Negative, 4=Somewhat Positive, 5=Positive, 6=Very Positive
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:
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.)
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.
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 |
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. |
| 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.
| 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.
Highlighting quick wins or “bright spots” helps you go from communicating change to more persuasively demonstrating change.
Specifically, quick wins help:
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."
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.
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:
Going forward, successful change will require that many responsibilities be delegated beyond the PMO and core transition team.
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
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.
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.
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)
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 |
|
|||
| Pilot Go-Live |
|
|||
| Full Rollout Approval |
|
|||
| Full Rollout |
|
|||
| Benefits Assessment |
|
"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
Use the final tab in the Stakeholder Engagement Workbook, “7. Training Requirements,” to begin fleshing out a training plan for project stakeholders.
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.
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.
“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.
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. |
|
|
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. |
|
|
Q3 2014 |
| Options: | Benefits: | Drawbacks: |
|---|---|---|
| Redeploy staff internally |
|
|
| Outsource |
|
|
| Contract |
|
|
| Hire externally |
|
|
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.
Industry Manufacturing
Source Info-Tech Client
"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
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.
Work with the analyst to fine-tune the stakeholder messaging across various stakeholder responses to change.
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.
Utilize analyst experience and perspective in order to develop an objections handling strategy to deal with resistance, objections, and fatigue.
Receive custom analyst insights on rightsizing training content and timing your training sessions effectively.
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.
Proposed Time to Completion (in weeks): 1 to 2 weeks
Discuss these issues with analyst:
Then complete these activities…
With these tools & templates:
Organizations rarely close the loop on project benefits once a project has been completed.
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.
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.
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 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
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 |
|
| Assess Quality |
|
| Discuss Ongoing Issues |
|
| Discuss Training |
|
| Assess Ongoing Costs |
|
| Assess Customer Satisfaction |
|
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.
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.
"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
Download Info-Tech’s Portfolio Benefits Tracking Tool to help solidify the process from the previous step.
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.
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.
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.
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.
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.
Proposed Time to Completion (in weeks): 1 to 2 weeks
Discuss these issues with an analyst:
Then complete these activities…
With these tools & templates:
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.
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.
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.
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.
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.
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... |
|---|---|---|
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.
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.
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.
Download Info-Tech’s Organizational Change Management Playbook.
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:
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.
Formalize a programmatic process for organizational change management in Info-Tech’s playbook template.
Develop a Project Portfolio Management Strategy
Optimize Project Intake, Approval, and Prioritization
Develop a Resource Management Strategy for the New Reality
Establish the Benefits Realization Process
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.
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.
Windows is no longer the only option. MacBooks and Chromebooks are justified, but now you have to manage them.
Managing end-user devices may be accomplished with a variety of solutions, but many of those solutions advocate integration with a Microsoft-friendly solution to take advantage of features such as conditional access, security functionality, and data governance.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Explore options, guidance and some best practices related to the management of Chromebooks and MacBooks in the enterprise environment and educational institutions. Our guidance will help you understand features and options available in a variety of solutions. We also provide guidance on selecting the best endpoint management solution for your own environment.
This tool will help you determine the features and options you want or need in an endpoint management solution.
Until recently, Windows devices dominated the workplace globally. Computing devices were also rare in many industries such as education. Administrators and administrative staff may have used Windows-based devices, but Chromebooks were not yet in use. Most universities and colleges were Windows-based in offices with some flavor of Unix in other areas, and Apple devices were gaining some popularity in certain circles.
That is a stark contrast compared to today, where Chromebooks dominate the classrooms and MacBooks and Chromebooks are making significant inroads into the enterprise environment. MacBooks are also a common sight on many university campuses. There is no doubt that while Windows may still be the dominant player, it is far from the only one in town.
Now that Chromebooks and MacBooks are a notable, if not significant, part of the education and enterprise environments, they must be afforded the same considerations as Windows devices in those environments when it comes to management. The good news is that there is no lack of available solutions for managing these devices, and the endpoint management landscape is continually evolving and improving.
P.J. Ryan
Research Director, Infrastructure & Operations
Info-Tech Research Group
Managing end-user devices may be accomplished with a variety of solutions, but many of those solutions advocate integration with a Microsoft-friendly solution to take advantage of features such as conditional access, security functionality, and data governance.
Google Admin Console is necessary to manage Chromebooks, but it can be paired with other tools. Implementation partnerships provide solutions to track the device lifecycle, track the repair lifecycle, sync with Google Admin Console as well as PowerSchool to provide a more complete picture of the user and device, and facilitate reminders to return the device, pay fees if necessary, pick up a device when a repair is complete, and more.
The Google Admin Console allows admins to follow an organizational unit (OU) structure very similar to what they may have used in Microsoft's Active Directory environment. This familiarity makes the task of administering Chromebooks easier for admins.
Chromebook management goes beyond securing and manipulating the device. Controls to protect the students while online, such as Safe Search and Safe Browsing, should also be implemented.
Most companies choose to use a dedicated MacBook management tool. Many unified endpoint management (UEM) tools can manage MacBooks to some extent, but admins tend to agree that a MacBook-focused endpoint management tool is best for MacBooks while a Windows-based endpoint management tool is best for Windows devices.
Some MacBook management solutions advocate integration with Windows UEM solutions to take advantage of Microsoft features such as conditional access, security functionality, and data governance. This approach can also be applied to Chromebooks.
"In 2018, Chromebooks represented an incredible 60 percent of all laptop or tablet devices in K-12 -- up from zero percent when the first Chromebook launched during the summer break in 2011."
– "Will Chromebooks Rule the Enterprise?" Computerworld
"Chromebooks were the best performing PC products in Q3 2020, with shipment volume increasing to a record-high 9.4 million units, up a whopping 122% year-on-year."
– Android Police
"Until the pandemic, Chrome OS' success was largely limited to U.S. schools. Demand in 2020 appears to have expanded beyond that small but critical part of the U.S. PC market."
– Geekwire
"In addition to running a huge number of Chrome Extensions and Apps at once, Chromebooks also run Android, Linux and Windows apps."
– "Will Chromebooks Rule the Enterprise?" Computerworld
GAC gives you a centralized console that will allow you to:
GAC can facilitate device management with features such as:
Device and user addition, group and organizational unit creation and administration, applying policies to devices and users – does all this remind you of your Active Directory environment?
GAC lets you administer users and devices with a similar approach.
Source: Google
You must be running the Chrome Enterprise Upgrade and have any licenses required by the approved partner to take advantage of this management option. The partner admin policies supersede GAC.
If you stop using the approved partner admin console to manage your devices, the polices and settings in GAC will immediately take over the devices.
Chromebook deployment becomes a challenge when device quantities grow. The enrollment process can be time consuming, and every device must be enrolled before it can be used by an employee or a student. Many admins enlist their full IT teams to assist in the short term. Some vendor partners may assist with distribution options if staffing levels permit. Recent developments from Google have opened additional options for device enrollment beyond the manual enrollment approach.
Most of the settings and features previously mentioned are also available for Education-licensed devices and users. Enterprise-specific features will not be available to Education licenses. (Active Directory integration with Education licenses, for example, is accomplished using a different approach)
An online search for Chromebook management solutions will reveal several software solutions that augment the capabilities of the Google Admin Console. Many of these solutions are focused on the education sector and classroom and student options, although the features would be beneficial to enterprises and educational organizations alike.
"There are many components to managing Chromebooks. Schools need to know which student has which device, which school has which device, and costs relating to repairs. Chromebook Management Software … facilitates these processes."
– VIZOR
"Macs now make up 23% of endpoints in enterprises."
– ComputerWeekly.com
"When given the choice, no less than 72% of employees choose Macs over PCs."
– "5 Reasons Mac is a must," Jamf
"IBM says it is 3X more expensive to manage PCs than Macs."
– Computerworld
"74% of those who previously used a PC for work experienced fewer issues now that they use a Mac"
– "Global Survey: Mac in the Enterprise," Jamf
"When enterprise moves to Mac, staff retention rates improve by 20%. That's quite a boost! "
– "5 Reasons Mac is a must," Jamf
Most Windows UEM tools are constantly improving, and it is only a matter of time before they rival many of the dedicated MacBook management tools out there.
Dedicated solutions advocate integration with UEM solutions to take advantage of conditional access, security functionality, and data governance features.
Jamf and Microsoft entered into a collaboration several years ago with the intention of making the MacBook management process easier and more secure.
Microsoft Intune and Jamf Pro: Better together to manage and secure Macs
Microsoft Conditional Access with Jamf Pro ensures that company data is only accessed by trusted users, on trusted devices, using trusted apps. Jamf extends this Enterprise Mobile + Security (EMS) functionality to Mac, iPhone and iPad.
– "Microsoft Intune and Jamf Pro," Jamf
There are many solutions available to manage end-user devices, and they come with a long list of options and features. Clarify your needs and define your requirements before you purchase another endpoint management tool. Don't purchase capabilities that you may never use.
Use the Endpoint Management Selection Tool to identify your desired endpoint solution features and compare vendor solution functionality based on your desired features.
|
Endpoint Management Selection Tool |
|||
|---|---|---|---|
|
In the first column, list out the desired features you want in an endpoint solution for your devices. Use the features provided if desired, or add your own and edit or delete the existing ones if necessary. As you look into various endpoint management solution vendors, list them in the columns in place of "Vendor 1," "Vendor 2," etc. Use the "Desired Feature" list as a checklist and change the values to "yes" or "no" in the corresponding box under the vendors' names. When complete, you will be able to look at all the features and compare vendors in a single table. |
|||
| Desired Feature | Vendor 1 | Vendor 2 | Vendor 3 |
| Organizational unit creation | Yes | No | Yes |
| Group creation | Yes | Yes | Yes |
| Ability to assign users to devices | No | Yes | Yes |
| Control of administrative permissions | Yes | Yes | Yes |
| Conditional access | No | Yes | Yes |
| Security policies enforced | Yes | No | Yes |
| Asset management | No | Yes | No |
| Single sign-on | Yes | Yes | Yes |
| Auto-deployment | No | Yes | No |
| Repair lifecycle tracking | No | Yes | No |
| Application deployment | Yes | Yes | No |
| Device tracking | Yes | Yes | Yes |
| Ability to enable encryption | Yes | No | Yes |
| Device wipe | Yes | No | Yes |
| Ability to enable/disable device tracking | No | No | Yes |
| User activity audit | No | No | No |
Modernize and Transform Your End-User Computing Strategy
This project helps support the workforce of the future by answering the following questions: What types of computing devices, provisioning models, and operating systems should be offered to end users? How will IT support devices? What are the policies and governance surrounding how devices are used? What actions are we taking and when? How do end-user devices support larger corporate priorities and strategies?
Best Unified Endpoint Management (UEM) Software 2022 | SoftwareReviews
Compare and evaluate unified endpoint management vendors using the most in-depth and unbiased buyer reports available. Download free comprehensive 40+ page reports to select the best unified endpoint management software for your organization.
Best Enterprise Mobile Management (EMM) Software 2022 | (softwarereviews.com)
Compare and evaluate enterprise mobile management vendors using the most in-depth and unbiased buyer reports available. Download free comprehensive 40+ page reports to select the best enterprise mobile management software for your organization.
Bridge, Tom. "Macs in the enterprise – what you need to know". Computerweekly.com, TechTarget. 27 May 2022. Accessed 12 Aug. 2022.
Copley-Woods, Haddayr. "5 reasons Mac is a must in the enterprise". Jamf.com, Jamf. 28 June 2022. Accessed 16 Aug. 2022.
Duke, Kent. "Chromebook sales skyrocketed in Q3 2020 with online education fueling demand." androidpolice.com, Android Police. 16 Nov 2020. Accessed 10 Aug. 2022.
Elgin, Mike. "Will Chromebooks Rule the Enterprise? (5 Reasons They May)". Computerworld.com, Computerworld. 30 Aug 2019. Accessed 10 Aug. 2022.
Evans, Jonny. "IBM says it is 3X more expensive to manage PCs than Macs". Computerworld.com, Computerworld. 19 Oct 2016. Accessed 23 Aug. 2022.
"Global Survey: Mac in the Enterprise". Jamf.com, Jamf. Accessed 16 Aug. 2022.
"How to Manage Chromebooks Like a Pro." Vizor.cloud, VIZOR. Accessed 10 Aug. 2022.
"Manage Chrome OS Devices with EMM Console". support.google.com, Google. Accessed 16 Aug. 2022.
Protalinski, Emil. "Chromebooks outsold Macs worldwide in 2020, cutting into Windows market share". Geekwire.com, Geekwire. 16 Feb 2021. Accessed 22 Aug. 2022.
Smith, Sean. "Microsoft Intune and Jamf Pro: Better together to manage and secure Macs". Jamf.com, Jamf. 20 April 2022. Accessed 16 Aug. 2022.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Understand Workday’s business model, competitive options, and what to know when conducting due diligence and requirements gathering.
Review product options and licensing rules. Determine negotiation points. Evaluate and finalize the contract.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Scope an affordable, adoptable, and effective PPM solution with Info-Tech's Portfolio Manager 2017 workbook.
Learn how to use Info-Tech's Portfolio Manager 2017 workbook and create powerful reports.
Plan and implement an affordable, adoptable, and effective PPM solution with Info-Tech's Portfolio Manager 2017 workbook.
Develop an exit strategy from your home-grown solution to a commercial PPM toolset. In this video, we show a rapid transition from the Excel dataset shown on this page to a commercial solution from Meisterplan. Christoph Hirnle of Meisterplan is interviewed starting at 9 minutes.
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.
Assess the current state of project portfolio management capability at your organization. The activities in this module will inform the next modules by exploring your organization’s current strengths and weaknesses and identifying areas that require improvement.
Set up the workbook to generate a fully functional project portfolio workbook that will give you a high-level view into your portfolio.
A high-level review of your current project portfolio capability is used to decide whether a homegrown PPM solution is an appropriate choice
Cost-benefit analysis is done to build a business case for supporting this choice
1.1 Review existing PPM strategy and processes.
1.2 Perform a cost-benefit analysis.
Confirmation of homegrown PPM solution as the right choice
Expected benefits for the PPM solution
Define a list of requirements for your PPM solution that meets the needs of all stakeholders.
A fully customized PPM solution in your chosen platform
2.1 Introduction to Info-Tech's Portfolio Manager 2017: inputs, outputs, and the data model.
2.2 Gather requirements for enhancements and customizations.
Trained project/resource managers on the homegrown solution
A wish list of enhancements and customizations
Determine an action plan regarding next steps for implementation.
Implement your homegrown PPM solution. The activities outlined in this step will help to promote adoption of the tool throughout your organization.
A set of processes to integrate the new homegrown PPM solution into existing PPM activities
Plans for piloting the new processes, process improvement, and stakeholder communication
3.1 Plan to integrate your new solution into your PPM processes.
3.2 Plan to pilot the new processes.
3.3 Manage stakeholder communications.
Portfolio Manager 2017 operating manual, which documents how Portfolio Manager 2017 is used to augment the PPM processes
Plan for a pilot run and post-pilot evaluation for a wider rollout
Communication plan for impacted PPM stakeholders
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Our concise executive brief shows you why you should rationalize your application portfolio using a tailored framework for your company. We'll show you our methodology and the ways we can help you in handling this.
Define why you want to rationalize your application portfolio. Define the end state and scope. Build your action plan.
Understand what the core assessments are that you perform in these rationalizations. Define your framework and how rigorous you want to apply the reviews based on your business context.
Our tool allows you to test the elements of your ARF. Then do a retrospective and adapt based on your experience and desired outcomes.
Review your dispositions to ensure they align with your goals.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Manage organizational risk and viability during the first 30 days of a crisis.
Do you experience any of the following challenges:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Ask the right questions and pressure test the workflow so the documentation is as helpful as possible to all who consult it.
Use this workflow as an example of the output of an onboarding workflow-improvement activity.
Emily Sugerman 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:
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. |
Your Challenge |
Common Obstacles |
Info-Tech’s Approach |
|---|---|---|
|
|
Use this material to help
|
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.

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.
Risks of inadequate workflows |
Benefits of documented workflows |
|---|---|
|
|
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.”
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:

Download the Process Mapping Guide
Good candidates include:
Application Development Process
Application Maintenance Process
Business Continuity Plan Business Process
Business Continuity Plan Recovery Process
Commitment Purchasing Workflow
Coordinated Vulnerability Disclosure Process
Data Protection Recovery Workflow
Disaster Recovery Plan/Business Continuity Plan Review Workflow
End-User Device Management Workflow Library
Incident Management and Service Desk Workflows
Security Policy Exception Process
Self-Service Resolution Process
Service Desk Ticket Intake by Channel
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
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:
Facilitator
Tasks:
Notetaker
Tasks:
Lack of communication/expectation setting with users: |
Messy process, poor coordination among task owners: |
User experience affected: |
|---|---|---|
|
|
|
![]() |
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. |

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:
Facilitator
Tasks:
Notetaker
Tasks:

Solicit feedback from the group.
"
Be complete.
The workflow should surface tacit knowledge, so make it explicit (Haddadpoor et al.):
Identify task ownership.
The flow chart will be more useful if it clearly identifies who does what in the process.

“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.”
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.
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
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.
Use Info-Tech’s Take Action on Service Desk Customer Feedback for more guidance on creating these surveys.
For onboarding, approvals can be the main roadblock to fulfilling requests
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:
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.
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).
Avoid reinforcing manual processes, which make it even harder for departmental silos to work together.
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?
How does the group feel about the revised workflow?
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.

Decide how often this workflow will be revised.
Share the flowchart and set up a review meeting.
Don’t waste time building shelfware.
Establish a review cadence to ensure the flowchart is a living document that people actually use.
“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.”
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...
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
A product owner is the CEO for their product. Successful product management starts with empowerment and accountability. Product owners own the vision, roadmap, and value realization for their product or family aligned to enterprise goals and priorities.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Strengthen the product owner role in your organization by focusing on core capabilities and proper alignment.
Using Info-Tech’s CLAIM model, quickly determine your organization’s strengths and weaknesses preparing for a product culture. Use the heat map to identify key areas.
Use the blueprint exercises to build your personal product owner playbook. You can also use the workbook to capture exercise outcomes.
Use this workbook to capture exercise outcomes and transfer them to your Mature and Scale Product Ownership Playbook (optional).
Product owners need to improve their core capabilities and real Agile skills. The assessment radar will help identify current proficiency and growth opportunities.
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.
Establish the foundation for product ownership.
Product owner playbook with role clarity and RACI.
1.1 Define enablers and blockers of product management.
1.2 Define your product management roles and names.
1.3 Assess your product management readiness.
1.4 Identify your primary product owner perspective.
1.5 Define your product owner RACI.
Enablers and blockers
Role definitions.
Product culture readiness
Product owner perspective mapping
Product owner RACI
Align product owners to products.
Assignment of resources to open products.
A stakeholder management strategy.
2.1 Assign resources to your products and families.
2.2 Visualize relationships to identify key influencers.
2.3 Group stakeholders into categories.
2.4 Prioritize your stakeholders.
Product resource assignment
Stakeholder management strategy
Stakeholder management strategy
Stakeholder management strategy
Mature product owner capabilities.
Assess your Agile product owner readiness
Assess and mature product owner capabilities
3.1 Assess your real Agile skill proficiency.
3.2 Assess your vison capability proficiency.
3.3 Assess your leadership capability proficiency.
3.4 Assess your PLM capability proficiency.
3.5 Assess your value realization capability proficiency.
3.6 Identify your business value drivers and sources of value.
Real Agile skill proficiency assessment
Info-Tech’s product owner capability model proficiency assessment
Info-Tech’s product owner capability model proficiency assessment
Info-Tech’s product owner capability model proficiency assessment
Info-Tech’s product owner capability model proficiency assessment
Business value drivers and sources of value
Strengthen the product owner’s role in your organization by focusing on core capabilities and proper alignment.
Whether you manage a product or service, the fundamentals of good product ownership are the same. Organizations need to focus on three key elements of product ownership in order to be successful.
By focusing the attention of the teammates serving in product owner or service owner roles, your organization will deliver value sooner and respond to change more effectively.
Principal Research Director – Application Delivery and Management
Info-Tech Research Group
Your ChallengeProduct owners must bridge the gap between the customers, operations, and delivery to ensure products continuously deliver increasing value. Product owners are often assigned to projects or product delivery without proper support, guidance, or alignment. In many organizations the product owner role is not well-defined, serves as a proxy for stakeholder ownership, and lacks reinforcement of the key skills needed to be successful. |
Common ObstaclesOrganizations have poor alignment or missing product owners between lines of business, IT, and operations. Product owners are aligned to projects and demand management rather than long-term strategic product ownership. Product families are not properly defined, scaled, and supported within organizations. Individuals in product owner roles have an incomplete understanding of needed capabilities and lack a development path. |
Info-Tech's ApproachCreate a culture of product management trust and empowerment with product owners aligned to your operational structure and product needs. Promote and develop true Agile skills among your product owners and family managers. Implement Info-Tech’s product owner capability model to define the role expectations and provide a development path for product owners. Extend product management success using Deliver on Your Digital Product Vision and Deliver Digital Products at Scale. |
There is no single correct approach to product ownership. Product ownership must be tuned and structured to meet the delivery needs of your organization and the teams it serves.
Successful product management starts with empowerment and accountability. Product owners own the vision, roadmap, and value realization for their product or family aligned to enterprise goals and priorities.
Product owners represent three primary perspectives: business (external-facing), technical (systems and tools), or operational (manual processes). Although all share the same capabilities, how they approach their responsibilities is influenced by their primary perspective.
Start with your operational grouping of products and families, identifying where an owner is needed. Then, assign people to the products and families. The owner does not define the product or family.
Product owners are operating under an incomplete understanding of the capabilities needed to succeed. Most product/service owners lack a complete picture of the needed capabilities, skills, and activities to successfully perform their roles.
The underlying capabilities and best practices to own and improve a product or service are identical for both roles. Use the terms that make the most sense for your culture.
Identify where product management is needed and align expectations with existing roles. Successful product management does not require a dedicated job family.
Regardless of whether you recognize yourself as a product-based or project-based shop, the same basic principles should apply.
You go through a period or periods of project-like development to build a version of an application or product.
You also have parallel services along with your project development, which encompass the more product-based view. These may range from basic support and maintenance to full-fledged strategy teams or services like sales and marketing.
For the purpose of this blueprint, product/service and product owner/service owner are used interchangeably. The term “product” is used for consistency but would apply to services, as well.
Common foundations: Focus on continuous improvement, ROI, and value realization. Clear vision, goals, roadmap, and backlog.
“Product” and “service” are terms that each organization needs to define to fit its culture and customers (internal and external). The most important aspect is consistent use and understanding of:
Product owners represent one of three primary perspectives. Although all share the same capabilities, how they approach their responsibilities is influenced by their primary perspective.
Product owners must translate needs and constraints from their perspective into the language of their audience. Kathy Borneman, Digital Product Owner at SunTrust Bank, noted the challenges of finding a common language between lines of business and IT (e.g. what is a unit?).
Groups of product families within an overall value stream or capability grouping.
A collection of related products. Products can be grouped along architectural, functional, operational, or experiential patterns.
Single product composed of one or more applications and services.
Define the current roles that will perform the product management function or define consistent role names to product owners and managers.
Your product owner map defines the influence landscape your product operates. It is every bit as important as the teams who enhance, support and operate your product directly.
Combine your product owner map with your stakeholder map to create a comprehensive view of influencers.
The product owner owns the direction of the product.
Roadmaps for your product family are, by design, less detailed. This does not mean they aren’t actionable! Your product family roadmap should be able to communicate clear intentions around the future delivery of value in both the near and long term.
Stakeholders are a critical cornerstone to product ownership. They provide the context, alignment, and constraints that influence or control what a product owner can accomplish.
Product owners operate within a network of stakeholders who represent different perspectives within the organization.
First, product owners must identify members of their stakeholder network. Next, they should devise a strategy for managing stakeholders.
Without a stakeholder strategy, product owners will encounter obstacles, resistance, or unexpected changes.
Your stakeholder map defines the influence landscape your product operates. It is every bit as important as the teams who enhance, support and operate your product directly.
Use “connectors” to determine who may be influencing your direct stakeholders. They may not have any formal authority within the organization, but they may have informal yet substantive relationships with your stakeholders.
While these are important, they are not the whole story. To effectively deliver software, we believe in the importance of being Agile over simply doing Agile.
Adapted from: “Doing Agile” Is Only Part of the Software Delivery Pie
The right skills development is only possible with proper assessment and alignment against outcomes.
It is easy to lose sight of what matters when we look at a product from a single point of view. Despite what "The Agile Manifesto" says, working software is not valuable without the knowledge and support that people need in order to adopt, use, and maintain it. If you build it, they will not come. Product owners must consider the needs of all stakeholders when designing and building products.
Source: Pulse Survey (N=18)
Unfortunately, most product owners operate with incomplete knowledge of the skills and capabilities needed to perform the role. Common gaps include focusing only on product backlogs, acting as a proxy for product decisions, and ignoring the need for key performance indicators (KPIs) and analytics in both planning and value realization.
Your vision informs and aligns what goals and capabilities are needed to fulfill your product or product family vision and align with enterprise goals and priorities. Each item on your roadmap should have corresponding KPIs or OKRs to know how far you moved the value needle. Value realization measures how well you met your target, as well as the impacts on your business value canvas and cost model.
Your leadership skills improve collaborations and decisions when working with your stakeholders and product delivery teams. This builds trust and improves continued improvements to the entire product lifecycle. A product owner’s focus should always be on finding ways to improve value delivery.
Adapted from: Crossing the Chasm
A product vision shouldn’t be so far out that it doesn’t feel real or so short-term that it gets bogged down in minutiae and implementation details. Finding the right balance will take some trial and error and will be different for each organization.
Your value drivers and impact helps estimate the expected value of roadmap items, prioritize roadmap and backlog items, and identify KPIs and OKRs to measure value realization and actual impact.
Value is best created by self-managing teams who deliver in frequent, short increments supported by leaders who coach them through challenges.
Product-centric delivery and Agile are a radical change in how people work and think. Structured, facilitated learning is required throughout the transformation to help leaders and practitioners make the shift.
Product management, Agile, and DevOps have inspired SDLC tools that have become a key part of delivery practices and work management.
Self-organizing teams that cross business, delivery, and operations are essential to gain the full benefits of product-centric delivery.
Successful implementations require the disciplined use of metrics that support developing better teams
Leaders of successful change spend considerable time developing a powerful change message; that is, a compelling narrative that articulates the desired end state, and that makes the change concrete and meaningful to staff.
The organizational change message should:
Phase steps |
1. Establish the foundation for product ownershipStep 1.1 Establish an environment for product owner success Step 1.2 Establish your product ownership model |
2. Align product owners to productsStep 2.1 Assign product owners to products Step 2.2 Manage stakeholder influence |
3. Mature product owner capabilitiesStep 3.1 Assess your Agile product owner readiness Step 3.2 Mature product owner capabilities |
Phase outcomes |
1.1.1 Define enablers and blockers of product management 1.1.2 Define your product management roles and names 1.2.1 Identify your primary product owner perspective 1.2.2 Define your product owner RACI |
2.1.1 Assign resources to your products and families 2.2.1 Visualize relationships to identify key influencers 2.2.2 Group stakeholders into categories 2.2.3 Prioritize your stakeholders |
3.1.1 Assess your real Agile skill proficiency 3.2 Mature product owner capabilities 3.2.1 Assess your vision capability proficiency 3.2.2 Assess your leadership capability proficiency 3.2.3 Assess your PLM capability proficiency 3.2.4 Identify your business value drivers and sources of value 3.2.5 Assess your value realization capability proficiency |
Capture and organize the outcomes of the activities in the workbook.
The workbook helps organize and communicate the outcomes of each activity.
Determine your level of mastery of real Agile skills and product owner capabilities.
Member outcome |
Suggested Metric |
Estimated impact |
| Increase business application satisfaction | Satisfaction of business applications (CIO BV Diagnostic) | 20% increase within one year after implementation |
| Increase effectiveness of application portfolio management | Effectiveness of application portfolio management (M&G Diagnostic) | 20% increase within one year after implementation |
| Increase importance and effectiveness of application portfolio | Importance and effectiveness to business (APA Diagnostic) | 20% increase within one year after implementation |
| Increase satisfaction of support of business operations | Support to business (CIO BV Diagnostic) | 20% increase within one year after implementation |
| Successfully deliver committed work (productivity) | Number of successful deliveries; burndown | Reduction in project implementation overrun by 20% |
"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"
Phase 1 Establish the Foundation for Product Ownership |
Phase 2 Align Product Owners to Products |
Phase 3 Mature Product Owner Capabilities |
|
|
|
Contact your account representative for more information.
workshops@infotech.com 1-888-670-8889
Phase 1 | Phase 2 | Phase 3 | |
Activities | Establish the Foundation for Product OwnershipStep 1.1 Establish an environment for product owner success 1.1.1 Define enablers and blockers of product management 1.1.2 Define your product management roles and names 1.1.3 Assess your product management readiness Step 1.2 Establish your product ownership model 1.2.1 Identify your primary product owner perspective 1.2.2 Define your product owner RACI | Align Product Owners to ProductsStep 2.1 Assign product owners to products 2.1.1 Assign resources to your products and families Step 2.2 Manage stakeholder influence 2.2.1 Visualize relationships to identify key influencers 2.2.2 Group stakeholders into categories 2.2.3 Prioritize your stakeholders | Mature Product Owner CapabilitiesStep 3.1 Assess your Agile product owner readiness 3.1.1 Assess your real Agile skill proficiency Step 3.2 Mature product owner capabilities= 3.2.1 Assess your Vision capability proficiency 3.2.2 Assess your Leadership capability proficiency 3.2.3 Assess your PLM capability proficiency 3.2.4 Identify your business value drivers and sources of value 3.2.5 Assess your Value Realization capability proficiency |
Deliverables |
|
|
|
Build a product vision your organization can take from strategy through execution.
Deliver value at the scale of your organization through defining enterprise product families.
Quickly assess the state of your Agile readiness and plan your path forward to higher value realization.
Understand Agile fundamentals, principles, and practices so you can apply them effectively in your organization.
Streamline business value delivery through the strategic adoption of DevOps practices.
Further the benefits of Agile by extending a scaled Agile framework to the business.
Embrace a team sport culture built around continuous business-IT collaboration to deliver great products.
Shift security left to get into DevSecOps.
Facilitate ongoing alignment between Agile teams and the business with a set of targeted service offerings.
Execute a disciplined approach to rolling out Agile methods in the organization.
See an overview of the APM journey and how we can support the pieces in this journey.
Ensure your application portfolio delivers the best possible return on investment.
Effective maintenance ensures the long-term value of your applications.
Move beyond maintenance to ensuring exceptional value from your apps.
Delivering value starts with embracing what your department can do.
Empower the business to implement its own applications with a trusted business-IT relationship.
Facilitate ongoing alignment between Agile teams and the business with a set of targeted service offerings.
Focus product delivery on business value-driven outcomes.
Be careful what you ask for, because you will probably get it.
Develop data-driven insights to help you decide which applications to retire, upgrade, re-train on, or maintain to meet the demands of the business.
Mature your IT department by measuring what matters.
Don’t let bad estimates ruin good work.
Commit to achievable software releases by grounding realistic expectations.
Expand on the financial model to give your initiative momentum.
Deliver more projects by giving yourself the voice to say “no” or “not yet” to new projects.
Facilitate ongoing alignment between Agile teams and the business with a set of targeted service offerings.
Focus product delivery on business value-driven outcomes.
Have the right people in the right place, at the right time.
Reorganizations are inherently disruptive. Implement your new structure with minimal pain for staff while maintaining IT performance throughout the change.
Don’t just measure engagement, act on it.
Set holistic measures to inspire employee performance.
1.1.1 Define enablers and blockers of product management
1.1.2 Define your product management roles and names
1.1.3 Assess your product management readiness
1.2.1 Identify your primary product owner perspective
1.2.2 Define your product owner RACI
1.1.1 Define enablers and blockers of product management
1.1.2 Define your product management roles and names
1.1.3 Assess your product management readiness
– Robbin Schuurman,
“Tips for Starting Technical Product Managers”
Implement Info-Tech’s Product Owner Capability Model to help empower and hold product owners accountable for the maturity and success of their product. The product owner must understand how their product fits into the organization’s mission and strategy in order to align to enterprise value.
Common foundations: Focus on continuous improvement, ROI, and value realization. Clear vision, goals, roadmap, and backlog.
“Product” and “service” are terms that each organization needs to define to fit its culture and customers (internal and external). The most important aspect is consistent use and understanding of:
Need help defining your products or services? Download our blueprint Deliver Digital Products at Scale.
" loading="lazy">
Every roadmap item should have an expected realized value once it is implemented. The associate KPIs or OKRs determine if our goal was met. Any gap in value feedback back into the roadmap and backlog refinement.
Product delivery requires significant shifts in the way you complete development work and deliver value to your users. Make the changes that support improving end-user value and enterprise alignment.
Regardless of whether you recognize yourself as a product-based or project-based shop, the same basic principles should apply.
You go through a period or periods of project-like development to build a version of an application or product.
You also have parallel services along with your project development, which encompasses a more product-based view. These may range from basic support and maintenance to full-fledged strategy teams or services like sales and marketing.
Source: “The Agile Manifesto”
Capture in the Mature and Scale Product Ownership Playbook.
Groups of product families within an overall value stream or capability grouping.
A collection of related products. Products can be grouped along architectural, functional, operational, or experiential patterns.
Single product composed of one or more applications and services.
Define the current roles that will perform the product management function or define consistent role names to product owners and managers.
Capture in the Mature and Scale Product Ownership Playbook.
Value is best created by self-managing teams who deliver in frequent, short increments supported by leaders who coach them through challenges.
Product-centric delivery and Agile are a radical change in how people work and think. Structured, facilitated learning is required throughout the transformation to help leaders and practitioners make the shift.
Product management, Agile, and DevOps have inspired SDLC tools that have become a key part of delivery practices and work management.
Self-organizing teams that cross business, delivery, and operations are essential to gain the full benefits of product-centric delivery.
Successful implementations require the disciplined use of metrics that support developing better teams
Capture in the Mature and Scale Product Ownership Readiness Assessment.
Leaders of successful change spend considerable time developing a powerful change message; that is, a compelling narrative that articulates the desired end state, and that makes the change concrete and meaningful to staff.
The organizational change message should:
1.2.1 Identify your primary product owner perspective
1.2.2 Define your product owner RACI
Product owners represent one of three primary perspectives. Although all share the same capabilities, how they approach their responsibilities is influenced by their primary perspective.
Product owners must translate needs and constraints from their perspective into the language of their audience. Kathy Borneman, Digital Product Owner at SunTrust Bank, noted the challenges of finding a common language between lines of business and IT (e.g. what is a unit?).
LOB product owners focus on the products and services consumed by the organization’s external consumers and users. The role centers on the market needs, competitive landscape, and operational support to deliver products and services.
Capture in the Mature and Scale Product Ownership Playbook.
Product ownership isn’t just about managing the product backlog and development cycles. Teams need to manage key milestones such as learning milestones, test releases, product releases, phase gates, and other organizational checkpoints.
Key milestones must be proactively managed. If a project manager is not available, those responsibilities need to be managed by the product owner or Scrum Master. Start with responsibility mapping to decide which role will be responsible.
*Scrum Master, Delivery Manager, Team Lead
Capture in the Mature and Scale Product Ownership Playbook.
2.1.1 Assign resources to your products and families
2.2.1 Visualize relationships to identify key influencers
2.2.2 Group stakeholders into categories
2.2.3 Prioritize your stakeholders
2.1.1 Assign resources to your products and families
Groups of product families within an overall value stream or capability grouping.
A collection of related products. Products can be grouped along architectural, functional, operational, or experiential patterns.
Single product composed of one or more applications and services.
Define the current roles that will perform the product management function or define consistent role names to product owners and managers.
In Deliver Digital Products at Scale , products were grouped into families using Info-Tech’s five scaling patterns. Assigning owners to Enterprise Applications and Shared Services requires special consideration.
A division or group delivers enabling capabilities and the team’s operational alignment maps directly to the modules/components of an enterprise application and other applications that support the specific business function.
For additional information about HRMS, please download Get the Most Out of Your HRMS.
Assign owners by service type, knowledge area, or technology to provide alignment of shared business capabilities and common solutions.
Use the stakeholder analysis to define the key stakeholders and sources of demand for enterprise applications and shared services. Extend your mapping to include their stakeholders and influencers to uncover additional sources of demand and prioritization.
Your product owner map defines the influence landscape your product operates. It is every bit as important as the teams who enhance, support, and operate your product directly.
Combine your product owner map with your stakeholder map to create a comprehensive view of influencers.
Capture in the Mature and Scale Product Ownership Playbook.
2.2.1 Visualize relationships to identify key influencers
2.2.2 Group stakeholders into categories
2.2.3 Prioritize your stakeholders
Stakeholders are a critical cornerstone to product ownership. They provide the context, alignment, and constraints that influence or control what a product owner can accomplish.
Product owners operate within a network of stakeholders who represent different perspectives within the organization.
First, product owners must identify members of their stakeholder network. Next, they should devise a strategy for managing stakeholders.
Without a stakeholder strategy, product owners will encounter obstacles, resistance, or unexpected changes.
Your stakeholder map defines the influence landscape your product operates. It is every bit as important as the teams who enhance, support, and operate your product directly.
Use connectors to determine who may be influencing your direct stakeholders. They may not have any formal authority within the organization, but they may have informal yet substantive relationships with your stakeholders.
Capture in the Mature and Scale Product Ownership Playbook.
There are four areas on the map, and the stakeholders within each area should be treated differently.
Capture in the Mature and Scale Product Ownership Playbook.
Consider the three dimensions of stakeholder prioritization: influence, interest, and support. Support can be determined by rating the following question: How likely is it that your stakeholder would recommend your product? These parameters are used to prioritize which stakeholders are most important and should receive your focused attention. The table to the right indicates how stakeholders are ranked.
Capture in the Mature and Scale Product Ownership Playbook.
Type |
Quadrant |
Actions |
Players |
High influence, high interest – actively engage | Keep them updated on the progress of the project. Continuously involve players in the process and maintain their engagement and interest by demonstrating their value to its success. |
Mediators |
High influence, low interest – keep satisfied | They can be the game changers in groups of stakeholders. Turn them into supporters by gaining their confidence and trust and including them in important decision-making steps. In turn, they can help you influence other stakeholders. |
Noisemakers |
Low influence, high interest – keep informed | Try to increase their influence (or decrease it if they are detractors) by providing them with key information, supporting them in meetings, and using mediators to help them. |
Spectators |
Low influence, low interest – monitor | They are followers. Keep them in the loop by providing clarity on objectives and status updates. |
Each group of stakeholders draws attention and resources away from critical tasks. By properly identifying your stakeholder groups, the product owner can develop corresponding actions to manage stakeholders in each group. This can dramatically reduce wasted effort trying to satisfy spectators and noisemakers while ensuring the needs of mediators and players are met.
3.1.1 Assess your real Agile skill proficiency
3.2.1 Assess your vision capability proficiency
3.2.2 Assess your leadership capability proficiency
3.2.3 Assess your PLM capability proficiency
3.2.4 Identify your business value drivers and sources of value
3.2.5 Assess your value realization capability proficiency
3.1.1 Assess your real Agile skill proficiency
The right skills development is only possible with proper assessment and alignment against outcomes.
While these are important, they are not the whole story. To effectively deliver software, we believe in the importance of being Agile over simply doing Agile.
Adapted from: “Doing Agile” Is Only Part of the Software Delivery Pie
Skill Name |
Description |
Accountability |
Refers to the state of being accountable. In an Agile context, it implies transparency, dedication, acting responsibly, and doing what is necessary to get the job done. |
Collaboration |
Values diverse perspectives and working with others to achieve the best output possible. Effective at working toward individual, team, department, and organizational goals. |
Comfort with ambiguity |
Allows you to confidently take the next steps when presented with a problem without having all the necessary information present. |
Communication |
Uses different techniques to share information, concerns, or emotions when a situation arises, and it allows you to vary your approach depending on the current phase of development. |
Empathy |
Is the ability to understand and share the feelings of another to better serve your team and your stakeholders. |
Facilitation |
Refers to guiding and directing people through a set of conversations and events to learn and achieve a shared understanding. |
Functional decomposition |
Is being able to break down requirements into constituent epics and stories. |
Initiative |
Is being able to anticipate challenges and then act on opportunities that lead to better business outcomes. |
Process discipline |
Refers to the focus of following the right steps for a given activity at the right time to achieve the right outcomes. |
Resilience |
Refers to the behaviors, thoughts, and actions that allow a person to recover from stress and adversity. |
All components of the employee empowerment driver have a strong, positive correlation with engagement.
Source: McLean & Company Engagement Database, 2018; N=71,794
1 - Foundational: Transitioning and Growing |
2 - Capable/Competent: Core Contributor |
3 - Influential: Gifted Improver |
4 - Transformational: Towering Strength |
|
|
|
|
Effective collaboration supports Agile behaviors, including embracing change and the ability to work iteratively.
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
Even though many organizations recognize its importance, communication is one of the root causes of project failure.
56% of the resources spent on a project are at risk due to ineffective communications.
PMI, 2013.
In 29% of projects started in the past 12 months, poor communication was identified as being one of the primary causes of failure.
PMI, 2013.
Adapted From: Agile Modeling
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
Empathy is the ability to understand and share the feelings of another in order to better serve your team and your stakeholders. There are three kinds:
Empathy enables you to serve your team, your customers, and your organization
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
“Facilitation is the skill of moderating discussions within a group in order to enable all participants to effectively articulate their views on a topic under discussion, and to ensure that participants in the discussion are able to recognize and appreciate the differing points of view that are articulated.” (IIBA, 2015)
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
“Functional decomposition helps manage complexity and reduce uncertainty by breaking down processes, systems, functional areas, or deliverables into their simpler constituent parts and allowing each part to be analyzed independently."
(IIBA, 2015)
In our research, we refer to these items as epics, capabilities, features, and user stories. How you develop your guiding principles and structure your backlog should be based on the terminology and artifact types commonly used in your organization.
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
| N/A -- Maximum level is '3 |
Adapted from: Why Innovation, 2019.
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
Capture in the Mature and Scale Product Owner Proficiency Assessment.
3.2.1 Assess your vision capability proficiency
3.2.2 Assess your leadership capability proficiency
3.2.3 Assess your PLM capability proficiency
3.2.4 Identify your business value drivers and sources of value
3.2.5 Assess your value realization capability proficiency
It is easy to lose sight of what matters when we look at a product from a single point of view . Despite what "The Agile Manifesto" says, working software is not valuable without the knowledge and support that people need in order to adopt, use, and maintain it. If you build it, they will not come. Product owners must consider the needs of all stakeholders when designing and building products.
Source: Pulse Survey (N=18)
Unfortunately, most product owners operate with incomplete knowledge of the skills and capabilities needed to perform the role. Common gaps include focusing only on product backlogs, acting as a proxy for product decisions, and ignoring the need for key performance indicators (KPIs) and analytics in both planning and value realization.
Your vision informs and aligns what goals and capabilities are needed to fulfill your product or product family vision and align with enterprise goals and priorities. Each item on your roadmap should have corresponding KPIs or OKRs to know how far you moved the value needle. Value realization measures how well you met your target, as well as the impacts on your business value canvas and cost model.
Your leadership skills improve collaborations and decisions when working with your stakeholders and product delivery teams. This builds trust and improves continued improvements to the entire product lifecycle. A product owner’s focus should always be on finding ways to improve value delivery.
Data comes from many places and may still not tell the complete story.
Supporting workbook that captures the interim results from a number of exercises that will contribute to your overall digital product vision.
An optional tool to help you capture your product backlog and prioritize based on your given criteria
An optional tool to help you build out and visualize your first roadmap.
Record the results from the exercises to help you define, detail, and make real your digital product vision.
Adapted from: Geoffrey Moore, 2014.
A product vision shouldn’t be so far out that it doesn’t feel real or so short-term that it gets bogged down in minutiae and implementation details. Finding the right balance will take some trial and error and will be different for each organization.
Info-Tech Best Practice Product delivery requires a comprehensive set of business and technical competencies to effectively roadmap, plan, deliver, support, and validate your product portfolio. Product delivery is a “multi-faceted, complex discipline that can be difficult to grasp and hard to master.” It will take time to learn and adopt methods and become a competent product manager or owner (“What Is Product Management?”, Pichler Consulting Limited).
Ultimately, you want products to be able to respond faster to changes and deliver value sooner. The level of detail in the roadmap and backlog is a tool to help the product owner plan for change. The duration of your product roadmap is all directly related to the tier of product owner in the product family.
In our research, we refer to these items as epics, capabilities, features, and user stories. How you develop your guiding principles and structure your backlog should be based on the terminology and artifact types commonly used in your organization.
Product ownership isn’t just about managing the product backlog and development cycles! Teams need to manage key milestones such as learning milestones, test releases, product releases, phase gates, and other organizational checkpoints!
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
Capture in the Mature and Scale Product Owner Proficiency Assessment.
Product owners cannot be just a proxy for stakeholder decisions. The product owner owns product decisions and management of all stakeholders.
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
Capture in the Mature and Scale Product Owner Proficiency Assessment.
Product owners must actively manage the full lifecycle of the product.
A well-formed backlog can be thought of as a DEEP backlog:
Detailed Appropriately: PBIs are broken down and refined, as necessary.
Emergent: The backlog grows and evolves over time as PBIs are added and removed.
Estimated: The effort a PBI requires is estimated at each tier.
Prioritized: The PBI’s value and priority are determined at each tier.
(Perforce, 2018)
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
Capture in the Mature and Scale Product Owner Proficiency Assessment.
Most organizations stop with on-time and on-budget. True financial alignment needs to define and manage the full lifecycle P&L.
Your value drivers and impact helps estimate the expected value of roadmap items, prioritize roadmap and backlog items, and identify KPIs and OKRs to measure value realization and actual impact.
Your balanced value is just one of many criteria needed to align your product goals and sequence roadmap items. Feasibility, delivery pipeline capacity, shared services, and other factors may impact the prioritization of backlog items.
Competent organizations know that value cannot always be represented by revenue or reduced expenses. However, it is not always apparent how to envision the full spectrum of sources of value. Dissecting value by benefit type and the value source’s orientation allows you to see the many ways in which a product or service brings value to the organization.
Financial benefits refer to the degree to which the value source can be measured through monetary metrics and is often quite tangible.
Human benefits refer to how a product or service can deliver value through a user’s experience.
Inward refers to value sources that have an internal impact and improve your organization’s effectiveness and efficiency in performing its operations.
Outward refers to value sources that come from your interaction with external factors, such as the market or your customers.
Capture in the Mature and Scale Product Ownership Workbook.
1 - Foundational: Transitioning and Growing | 2 - Capable/Competent: Core Contributor | 3 - Influential: Gifted Improver | 4 - Transformational: Towering Strength |
|
|
|
|
Capture in the Mature and Scale Product Owner Proficiency Assessment.
Product ownership can be one of the most difficult challenges facing delivery and operations teams. By focusing on operational grouping and alignment of goals, organizations can improve their value realization at all levels in the organization.
The foundation for delivering and enhancing products and services is rooted in the same capability model. Traditionally, product owners have focused on only a subset of skills and capabilities needed to properly manage and grow their products. The product owner capability model is a useful tool to ensure optimal performance from product owners and assess the right level of detail for each product within the product families.
Congratulations. You’ve completed a significant step toward higher-value products and services.
Contact your account representative for more information
workshops@infotech.com
1-888-670-8889
Contact your account representative for more information
workshops@infotech.com 1-888-670-8889
Assess your skills and capabilities against the real Agile skills inventory
Build a stakeholder management strategy.
Emily Archer is a consultant currently working with Fortune 500 clients to ensure the delivery of successful projects, products, and processes. She helps increase the business value returned for organizations’ investments in designing and implementing enterprise content hubs and content operations, custom web applications, digital marketing, and e-commerce platforms.
David Berg is a product commercialization expert who has spent the last 20 years delivering product management and business development services across a broad range of industries. Early in his career, David worked with product management and engineering teams to build core network infrastructure products that secure and power the internet we benefit from today. David’s experience also includes working with clean technologies in the area of clean power generation, agritech, and Internet of Things infrastructure. Over the last five years, David has been focused on his latest venture, Strainprint Technologies, a data and analytics company focused on the medical cannabis industry. Strainprint has built the largest longitudinal medical cannabis dataset in the world, with a goal to develop an understanding of treatment behavior, interactions, and chemical drivers to guide future product development.
Kathy Borneman is a senior product owner who helps people enjoy their jobs again by engaging others in end-to-end decision making to deliver software and operational solutions that enhance the client experience and allow people to think and act strategically.
Charlie Campbell is an experienced problem solver with the ability to quickly dissect situations and recommend immediate actions to achieve resolution, liaise between technical and functional personnel to bridge the technology and communication gap, and work with diverse teams and resources to reach a common goal.
Yarrow Diamond is an experienced professional with expertise in enterprise strategy development, project portfolio management, and business process reengineering across financial services, healthcare and insurance, hospitality, and real estate environments. She has a master’s in Enterprise Architecture from Penn State University, LSSMBB, PMP, CSM, ITILv3.
Cari J. Faanes-Blakey has a history in software development and implementation as a Business Analyst and Project Manager for financial and taxation software vendors. Active in the International Institute of Business Analysis (IIBA), Cari participated on the writing team for the BA Body of Knowledge 3.0 and the certification exam.
Kieran Gobey is an IT professional with 24 years of experience, focused on business, technology, and systems analysis. He has split his career between external and internal customer-facing roles, and this has resulted in a true understanding of what is required to be a Professional Services Consultant. His problem-solving skills and ability to mentor others have resulted in successful software implementations.
Kieran’s specialties include deep system troubleshooting and analysis skills, facilitating communications to bring together participants effectively, mentoring, leadership, and organizational skills.
Rupert Kainzbauer is an experienced senior leader with a passion for defining and delivering products that deliver real customer and commercial benefit. With a team of highly experienced and motivated product managers, he has successfully led highly complex, multi-stakeholder payments initiatives, from proposition development and solution design through to market delivery. Their domain experience is in building online payment products in high-risk and emerging markets, remittance, prepaid cards, and mobile applications.
Saeed Khan has been working in high tech for 30 years in Canada and the US and has held several leadership roles in Product Management in that time. He speaks regularly at conferences and has been writing publicly about technology product management since 2005.
Through Transformation Labs, Saeed helps companies accelerate product success by working with product teams to improve their skills, practices, and processes. He is a cofounder of ProductCamp Toronto and currently runs a Meetup group and global Slack community called Product Leaders; the only global community of senior level product executives.
Hoi Kun Lo is an experienced change agent who can be found actively participating within the IIBA and WITI groups in Tampa, FL and a champion for Agile, architecture, diversity, and inclusion programs at Nielsen. She is currently a Product Owner in the Digital Strategy team within Nielsen Global Watch Technology.
Abhishek Mathur is a product management leader, an artificial intelligence practitioner, and an educator. He has led product management and engineering teams at Clarifai, IBM, and Kasisto to build a variety of artificial intelligence applications within the space of computer vision, natural language processing, and recommendation systems. Abhishek enjoys having deep conversations about the future of technology and helping aspiring product managers enter and accelerate their careers.
Jeff Meister is a technology advisor and product leader. He has more than 20 years of experience building and operating software products and the teams that build them. He has built products across a wide range of industries and has built and led large engineering, design, and product organizations.
Jeff most recently served as Senior Director of Product Management at Avanade, where he built and led the product management practice. This involved hiring and leading product managers, defining product management processes, solution shaping and engagement execution, and evangelizing the discipline through pitches, presentations, and speaking engagements.
Jeff holds a Bachelor of Applied Science (Electrical Engineering) and a Bachelor of Arts from the University of Waterloo, an MBA from INSEAD (Strategy), and certifications in product management, project management, and design thinking.
With over 10 years of experience in both the private and public sectors, Vincent Mirabelli possesses an impressive track record of improving, informing, and transforming business strategy and operations through process improvement, design and re-engineering, and the application of quality to business analysis, project management, and process improvement standards.
Oz Nazili is a product leader with a decade of experience in both building products and product teams. Having spent time at funded startups and large enterprises, he thinks often about the most effective way to deliver value to users. His core areas of interest include Lean MVP development and data-driven product growth.
Mike Starkey is a Director of Engineering at W.W. Grainger, currently focusing on operating model development, digital architecture, and building enterprise software. Prior to joining W.W. Grainger, Mike held a variety of technology consulting roles throughout the system delivery lifecycle spanning multiple industries such as healthcare, retail, manufacturing, and utilities with Fortune 500 companies.
Anant Tailor is a cofounder at Dream Payments where he currently serves as the COO and Head of Product, having responsibility for Product Strategy & Development, Client Delivery, Compliance, and Operations. He has 20+ years of experience building and operating organizations that deliver software products and solutions for consumers and businesses of varying sizes.
Prior to founding Dream Payments, Anant was the COO and Director of Client Services at DonRiver Inc, a technology strategy and software consultancy that he helped to build and scale into a global company with 100+ employees operating in seven countries.
Anant is a Professional Engineer with a Bachelor degree in Electrical Engineering from McMaster University and a certificate in Product Strategy & Management from the Kellogg School of Management at Northwestern University.
Angela Weller is an experienced Agile business analyst who collaborates with key stakeholders to attain their goals and contributes to the achievement of the company’s strategic objectives to ensure a competitive advantage. She excels when mediating or facilitating teams.
Build a product vision your organization can take from strategy through execution.
Deliver value at the scale of your organization through defining enterprise product families.
Quickly assess the state of your Agile readiness and plan your path forward to higher value realization.
Improve collaboration and transparency with the business to minimize project failure.
Streamline business value delivery through the strategic adoption of DevOps practices.
Further the benefits of Agile by extending a scaled Agile framework to the business.
Embrace a team sport culture built around continuous business-IT collaboration to deliver great products.
Shift security left to get into DevSecOps.
Facilitate ongoing alignment between Agile teams and the business with a set of targeted service offerings.
Execute a disciplined approach to rolling out Agile methods in the organization.
See an overview of the APM journey and how we can support the pieces in this journey.
Ensure your application portfolio delivers the best possible return on investment.
Effective maintenance ensures the long-term value of your applications.
Move beyond maintenance to ensuring exceptional value from your apps.
Delivering value starts with embracing what your department can do.
Empower the business to implement their own applications with a trusted business-IT relationship
Facilitate ongoing alignment between Agile teams and the business with a set of targeted service offerings.
Focus product delivery on business value–driven outcomes.
Be careful what you ask for, because you will probably get it.
Develop data-driven insights to help you decide which applications to retire, upgrade, re-train on, or maintain to meet the demands of the business.
Mature your IT department by measuring what matters.
Don’t let bad estimates ruin good work.
Commit to achievable software releases by grounding realistic expectations.
Expand on the financial model to give your initiative momentum.
Deliver more projects by giving yourself the voice to say “no” or “not yet” to new projects.
Facilitate ongoing alignment between Agile teams and the business with a set of targeted service offerings.
Focus product delivery on business value-driven outcomes.
Have the right people, in the right place, at the right time.
Reorganizations are inherently disruptive. Implement your new structure with minimal pain for staff while maintaining IT performance throughout the change.
Don’t just measure engagement, act on it
Set holistic measures to inspire employee performance.
“12th Annual State of Agile Report.” VersionOne, 9 April 2018. Web.
A, Karen. “20 Mental Models for Product Managers.” Product Management Insider, Medium, 2 Aug. 2018. Web.
Adams, Paul. “Product Teams: How to Build & Structure Product Teams for Growth.” Inside Intercom, 30 Oct. 2019. Web.
Aghina, Handscomb, Ludolph, West, and Abby Yip, “How to select and develop individuals for successful agile teams: A practical guide” McKinsey & Company 20 Dec. 2018. Web.
Agile Alliance. “Product Owner.” Agile Alliance. n.d. Web.
Ambler, Scott W. "Communication on Agile Software Teams“, Agile Modeling. 2001-2022. Web.
Ambysoft. “2018 IT Project Success Rates Survey Results.” Ambysoft. 2018. Web.
Banfield, Richard, et al. “On-Demand Webinar: Strategies for Scaling Your (Growing) Enterprise Product Team.” Pluralsight, 31 Jan. 2018. Web.
Beck, Beedle, van Bennekum, Cockburn, Cunningham, Fowler, Grenning, Highsmith, Hunt, Jeffries, Kern, Marick, Martin, Mellor, Schwaber, Sutherland, Thomas, "Manifesto for Agile Software Development." agilemanifesto.org. 2001
Berez, Steve, et al. “How to Plan and budget for Agile at Scale.” Bain & Company, 08 Oct 2019. Web
Blueprint. “10 Ways Requirements Can Sabotage Your Projects Right From the Start.” Blueprint. 2012. Web.
Breddels, Dajo, and Paul Kuijten. “Product Owner Value Game.” Agile2015 Conference, Agile Alliance 2015. Web.
Cagan, Martin. “Behind Every Great Product.” Silicon Valley Product Group. 2005. Web.
Cohn, Mike. “What Is a Product?” Mountain Goat Software. 6 Sept. 2016. Web.
Connellan, Thomas K. Inside the Magic Kingdom, Bard Press, 1997.
Curphey, Mark. “Product Definition.” SlideShare, 25 Feb. 2007. Web.
“Delegation Poker Product Image.” Management 3.0, n.d. Web.
Distel, Dominic, et al. “Finding the sweet spot in product-portfolio management.’ McKinsey, 4 Dec. 2020. Web
Eringa, Ron. “Evolution of the Product Owner.” RonEringa.com, 12 June 2016. Web.
Fernandes, Thaisa. “Spotify Squad Framework - Part I.” PM101, Medium, 6 Mar. 2017. Web.
Galen, Robert. “Measuring Product Ownership – What Does ‘Good’ Look Like?” RGalen Consulting, 5 Aug. 2015. Web.
Grenny, Joseph. “The Best Teams Hold Themselves Accountable.” Harvard Business Review, 30 May 2014. Web.
Halisky, Merland, and Luke Lackrone. “The Product Owner’s Universe.” Agile2016 Conference, Agile Alliance, 2016. Web.
IIBA "A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) v3" IIBA. 15 APR 2015
Kamer, Jurriaan. “How to Build Your Own ‘Spotify Model’.” The Ready, Medium, 9 Feb. 2018. Web.
Kendis Team. “Exploring Key Elements of Spotify’s Agile Scaling Model.” Scaled Agile Framework, Medium, 23 Jul. 2018. Web.
Lindstrom, Lowell. “7 Skills You Need to Be a Great Product Owner.” Scrum Alliance, n.d. Web.
Lukassen, Chris. “The Five Belts Of The Product Owner.” Xebia.com, 20 Sept. 2016. Web.
Mankins, Michael. “The Defining Elements of a Winning Culture.” Bain, 19 Dec. 2013. Web.
McCloskey, Heather. “Scaling Product Management: Secrets to Defeating Common Challenges.” ProductPlan, 12 July 2019. Web.
McCloskey, Heather. “When and How to Scale Your Product Team.” UserVoice, 21 Feb. 2017. Web. Mironov, Rich. “Scaling Up Product Manager/Owner Teams.” Rich Mironov's Product Bytes, Mironov Consulting, 12 Apr. 2014. Web.
Moore, Geoffrey A. “Crossing the Chasm, 3rd Edition.” Collins Business Essentials, 28 Jan 2014
Oh, Paul. “How Mastering Resilience Can Help Drive Agile Transformations.” Why Innovation!, 10 Oct. 2019.
Overeem, Barry. “A Product Owner Self-Assessment.” Barry Overeem, 6 Mar. 2017. Web.
Overeem, Barry. “Retrospective: Using the Team Radar.” Barry Overeem, 27 Feb. 2017. Web.
Pichler, Roman. “How to Scale the Scrum Product Owner.” Roman Pichler, 28 June 2016 . Web.
Pichler, Roman. “Product Management Framework.” Pichler Consulting Limited, 2014. Web.
Pichler, Roman. “Sprint Planning Tips for Product Owners.” LinkedIn, 4 Sept. 2018. Web.
Pichler, Roman. “What Is Product Management?” Pichler Consulting Limited, 26 Nov. 2014. Web.
PMI "The high cost of low performance: the essential role of communications“. PMI Pulse of Profession, May 2013.
Radigan,Dan. “Putting the ‘Flow' Back in Workflow With WIP Limits.” Atlassian, n.d. Web.
Rouse, Margaret. “Definition: product.” TechTarget, Sept. 2005. Web.
Schuurman, Robbin. “10 Tips for Product Owners on (Business) Value.” Scrum.org, 30 Nov. 2017. Web.
Schuurman, Robbin. “10 Tips for Product Owners on Agile Product Management.” Scrum.org, 28 Nov. 2017. Web.
Schuurman, Robbin. “10 Tips for Product Owners on Product Backlog Management.” Scrum.org, 5 Dec. 2017. Web.
Schuurman, Robbin. “10 Tips for Product Owners on the Product Vision.” Scrum.org, 29 Nov. 2017. Web.
Schuurman, Robbin. “Tips for Starting Product Owners.” Scrum.org, 27 Nov. 2017. Web.
Sharma, Rohit. “Scaling Product Teams the Structured Way.” Monetary Musings, 28 Nov. 2016. Web.
Shirazi, Reza. “Betsy Stockdale of Seilevel: Product Managers Are Not Afraid To Be Wrong.” Austin Voice of Product, 2 Oct. 2018. Web.
Spitz, Enid R. “The Three Kinds of Empathy: Emotional, Cognitive, Compassionate.” The Three Kinds of Empathy: Emotional, Cognitive, Compassionate. Heartmanity. Web.
Steiner, Anne. “Start to Scale Your Product Management: Multiple Teams Working on Single Product.” Cprime, 6 Aug. 2019. Web.
“The Qualities of Leadership: Leading Change.” Cornelius & Associates, 2016. Web.
“The Standish Group 2015 Chaos Report.” The Standish Group. 2015. Web.
Theus, Andre. “When Should You Scale the Product Management Team?” ProductPlan, 7 May 2019. Web.
Tolonen, Arto. “Scaling Product Management in a Single Product Company.” Smartly.io, 26 Apr. 2018. Web.
Ulrich, Catherine. “The 6 Types of Product Managers. Which One Do You Need?” Medium, 19 Dec. 2017. Web.
Verwijs, Christiaan. “Retrospective: Do The Team Radar.” The Liberators, Medium, 10 Feb. 2017. Web.
Vlaanderen, Kevin. “Towards Agile Product and Portfolio Management”. Academia.edu. 2010. Web.
2009 Business Analysis Benchmark Study.” IAG Consulting, 2009. Web.
Armel, Kate. “Data-driven Estimation, Management Lead to High Quality.” Quantitative Software Management Inc, 2015. Web.
Bradley, Marty. “Agile Estimation Guidance.” Leading Agile, 30 Aug. 2016. Web. Feb. 2019.
CollabNet and VersionOne. “12th Annual State of Agile Report.” VersionOne, 9 April 2018. Web.
Craveiro, João. “Marty meets Martin: connecting the two triads of Product Management.” Product Coalition, 18 Nov. 2017. Accessed Feb. 2019.
“Enablers.” Scaled Agile, n.d. Web.
“Epic.” Scaled Agile, n.d. Web.
Fischer, Christian. “Scrum Compact.” Itemis, n.d. Web. Feb. 2019.
Hackshall, Robin. “Product Backlog Refinement.” Scrum Alliance, 9 Oct. 2014. Accessed Feb. 2019.
Hartman, Bob. “New to agile? INVEST in good user stories.” Agile For All, 14 May 2009. Web.
Huether, Derek. “Cheat Sheet for Product Backlog Refinement (Grooming).” Leading Agile, 2 Nov. 2013. Accessed Feb. 2019.
Karlsson, Johan. “Backlog Grooming: Must-Know Tips for High-Value Products.” Perforce, 18 May 2018. Accessed Feb. 2019.
Khan, Saeed. “Good Bye ‘Product Owner’, Hello ‘Backlog Manager.’” On Product Management, 27 June 2011. Accessed Feb. 2019.
Khan, Saeed. “Let’s End the Confusion: A Product Owner is NOT a Product Manager.” On Product Management, 14 July 2017. Accessed Feb. 2019.
Lawrence, Richard. “New Story Splitting Resource.” Agile For All. 27 Jan. 2012. Web. Feb. 2019.
Leffingwell, Dean. “SAFe 4.0.” Scaled Agile Inc, 2017. Accessed Feb. 2019.
Lucero, Mario. “Product Backlog – Deep Model.” Agilelucero, 8 Oct. 2014. Web.
“PI Planning.” Scaled Agile, n.d. Web.
Pichler, Roman. “The Product Roadmap and the Product Backlog.” Roman Pichler, 9 Sept. 2014. Accessed Feb. 2019.
Rubin, Kenneth S. Essential Scrum: A Practical Guide to the Most Popular Agile Process. Pearson Education, 2012.
Schuurman, Robbin. “10 Tips for Product Owners on Product Backlog Management.” Burozeven, 20 Nov. 2017. Accessed Feb. 2019.
Srinivasan, Vibhu. “Product Backlog Management: Tips from a Seasoned Product Owner.” Agile Alliance, n.d. Accessed Feb. 2019.
Todaro, Dave. “Splitting Epics and User Stories.” Ascendle, n.d. Accessed Feb. 2019.
“What Characteristics Make Good Agile Acceptance Criteria?” Segue Technologies, 3 Sept. 2015. Web. Feb. 2019.
Bastow, Janna. “Creating Agile Product roadmaps Everyone Understands.” ProdPad, 22 Mar. 2017. Accessed Sept. 2018.
Bastow, Janna. “The Product Tree Game: Our Favorite Way To Prioritize Features.” ProdPad, 21 Feb. 2016. Accessed Sept. 2018.
Chernak, Yuri. “Requirements Reuse: The State of the Practice.” 2012 IEEE International Conference, 12 June 2012, Herzliya, Israel. Web.
Fowler, Martin. “Application Boundary.” MartinFowler.com, 11 Sept. 2003. Accessed 20 Nov. 2017.
Harrin, Elizabeth. “Learn What a Project Milestone Is.” The Balance Careers, 10 May 2018. Accessed Sept. 2018.
“How to create a product roadmap.” Roadmunk, n.d. Accessed Sept. 2018.
Johnson, Steve. “How to Master the 3 Horizons of Product Strategy.” Aha!, 24 Sept. 2015. Accessed Sept. 2018.
Johnson, Steve. “The Product Roadmap vs. the Technology Roadmap.” Aha!, 23 June 2016. Accessed Sept. 2018
Juncal, Shaun. “How Should You Set Your Product Roadmap Timeframes?” ProductPlan, Web. Sept. 2018.
Leffingwell, Dean. “SAFe 4.0.” Scaled Agile, 2017. Web.
Maurya, Ash. “What is a Minimum Viable Product (MVP).” Leanstack, 12 June 2017. Accessed Sept. 2018.
Pichler, Roman. “10 Tips for Creating an Agile Product Roadmap.” Roman Pichler, 20 July 2016. Accessed Sept. 2018.
Pichler, Roman. Strategize: Product Strategy and Product Roadmap Practices for the Digital Age. Pichler Consulting, 2016.
“Product Roadmap Contents: What Should You Include?” ProductPlan, n.d. Accessed 20 Nov. 2017.
Saez, Andrea. “Why Your Roadmap Is Not a Release Plan.” ProdPad, 23 October 2015. Accessed Sept. 2018.
Schuurman, Robbin. “Tips for Agile product roadmaps & product roadmap examples.” Scrum.org, 7 Dec. 2017. Accessed Sept. 2018.
Adams, Paul. “The Future Product Canvas.” Inside Intercom, 10 Jan. 2014. Web.
“Aligning IT Funding Models to the Pace of Technology Change.” EDUCAUSE, 14 Dec. 2015. Web.
Altman, Igor. “Metrics: Gone Bad.” OpenView, 10 Nov. 2009. Web.
Barry, Richard. “The Product Vision Canvas – a Strategic Tool in Developing a Successful Business.” Polymorph, 2019. Web.
“Business Canvas – Business Models & Value Propositions.” Strategyzer, 2019. Web.
“Business Model Canvas.” Wikipedia: The Free Encyclopedia, 4 Aug. 2019. Web.
Charak, Dinker. “Idea to Product: The Working Model.” ThoughtWorks, 13 July 2017. Web.
Charak, Dinker. “Product Management Canvas - Product in a Snapshot.” Dinker Charak, 29 May 2017. Web.
Chudley, James. “Practical Steps in Determining Your Product Vision (Product Tank Bristol, Oct. 2018).” LinkedIn SlideShare. Uploaded by cxpartners, 2 Nov. 2018. Web.
Cowan, Alex. “The 20 Minute Business Plan: Business Model Canvas Made Easy.” COWAN+, 2019. Web.
Craig, Desiree. “So You've Decided To Become A Product Manager.” Start it up, Medium, 2 June 2019. Web.
“Create an Aha! Business Model Canvas Strategic Model.” Aha! Support, 2019. Web.
Eick, Stephen. “Does Code Decay? Assessing the Evidence from Change Management Data.” IEEE Transactions on Software Engineering, vol. 27, no. 1, Jan. 2001, pp. 1-12. Web.
Eriksson, Martin. “The next Product Canvas.” Mind the Product, 22 Nov. 2013. Web.
“Experience Canvas: a Lean Approach: Atlassian Team Playbook.” Atlassian, 2019. Web.
Freeman, James. “How to Make a Product Canvas – Visualize Your Product Plan.” Edraw, 23 Dec. 2019. Web.
Fuchs, Danny. “Measure What Matters: 5 Best Practices from Performance Management Leaders.” OpenGov, 8 Aug. 2018. Web.
Gorisse, Willem. “A Practical Guide to the Product Canvas.” Mendix, 28 Mar. 2017. Web.
Gothelf, Jeff. “The Lean UX Canvas.” Jeff Gothelf, 15 Dec. 2016. Web.
Gottesdiener, Ellen. “Using the Product Canvas to Define Your Product: Getting Started.” EBG Consulting, 15 Jan. 2019. Web.
Gottesdiener, Ellen. “Using the Product Canvas to Define Your Product's Core Requirements.” EBG Consulting, 4 Feb. 2019. Web.
Gray, Mark Krishan. “Should I Use the Business Model Canvas or the Lean Canvas?” Blog, Medium.com, 2019. Web.
Hanby, Jeff. "Software Maintenance: Understanding and Estimating Costs." LookFar, 21 Oct. 2016. Web.
“How do you define a product?” Scrum.org, 4 Apr 2017, Web
Juncal, Shaun. “How to Build a Product Roadmap Based on a Business Model Canvas.” ProductPlan, 19 June 2019. Web.
“Lean Canvas Intro - Uber Example.” YouTube, uploaded by Railsware Product Academy, 12 Oct. 2018. Web.
“Lesson 6: Product Canvas.” ProdPad Help Center, 2019. Web.
Lucero, Mario. “The Product Canvas.” Agilelucero.com, 22 June 2015. Web.
Maurya, Ash. “Create a New Lean Canvas.” Canvanizer, 2019. Web.
Maurya, Ash. “Don't Write a Business Plan. Create a Lean Canvas Instead.” LEANSTACK, 2019. Web.
Maurya, Ash. “Why Lean Canvas vs Business Model Canvas?” Medium, 27 Feb. 2012. Web.
Mirabelli, Vincent. “The Project Value Canvas.” Vincent Mirabelli, 2019. Web.
Mishra, LN. “Business Analysis Canvas – The Ultimate Enterprise Architecture.” BA Times, 19 June 2019. Web.
Muller. Jerry Z. “Why performance metrics isn’t always the best way to judge performance.” Fast Company, 3 April 2019. Web.
Perri, Melissa. “What Is Good Product Strategy?” Melissa Perri, 14 July 2016. Web.
Pichler, Roman. “A Product Canvas for Agile Product Management, Lean UX, Lean Startup.” Roman Pichler, 16 July 2012. Web.
Pichler, Roman. “Introducing the Product Canvas.” JAXenter, 15 Jan. 2013. Web.
Pichler, Roman. “Roman's Product Canvas: Introduction.” YouTube, uploaded by Roman Pichler, 3 Mar. 2017. Web.
Pichler, Roman. “The Agile Vision Board: Vision and Product Strategy.” Roman Pichler, 10 May 2011. Web.
Pichler, Roman. “The Product Canvas – Template.” Roman Pichler, 11 Oct. 2016. Web.
Pichler, Roman. “The Product Canvas Tutorial V1.0.” LinkedIn SlideShare. Uploaded by Roman Pichler, 14 Feb. 2013. Web.
Pichler, Roman. “The Product Vision Board: Introduction.” YouTube uploaded by Roman Pichler, 3 Mar. 2017. Web.
“Product Canvas PowerPoint Template.” SlideModel, 2019. Web.
“Product Canvas.” SketchBubble, 2019, Web.
“Product Canvas.” YouTube, uploaded by Wojciech Szramowski, 18 May 2016. Web.
“Product Roadmap Software to Help You Plan, Visualize, and Share Your Product Roadmap.” Productboard, 2019. Web.
Roggero, Giulio. “Product Canvas Step-by-Step.” LinkedIn SlideShare, uploaded by Giulio Roggero, 18 May 2013. Web.
Royce, Dr. Winston W. “Managing the Development of Large Software Systems.” Scf.usc.edu, 1970. Web.
Ryan, Dustin. “The Product Canvas.” Qdivision, Medium, 20 June 2017. Web.
Snow, Darryl. “Product Vision Board.” Medium, 6 May 2017. Web.
Stanislav, Shymansky. “Lean Canvas – a Tool Your Startup Needs Instead of a Business Plan.” Railsware, 12 Oct. 2018. Web.
Stanislav, Shymansky. “Lean Canvas Examples of Multi-Billion Startups.” Railsware, 20 Feb. 2019. Web.
“The Product Vision Canvas.” YouTube, Uploaded by Tom Miskin, 20 May 2019. Web.
Tranter, Leon. “Agile Metrics: the Ultimate Guide.” Extreme Uncertainty, n.d. Web.
“Using Business Model Canvas to Launch a Technology Startup or Improve Established Operating Model.” AltexSoft, 27 July 2018. Web.
Veyrat, Pierre. “Lean Business Model Canvas: Examples + 3 Pillars + MVP + Agile.” HEFLO BPM, 10 Mar. 2017. Web.
“What Are Software Metrics and How Can You Track Them?” Stackify, 16 Sept. 2017. Web
“What Is a Product Vision?” Aha!, 2019. Web.
Success depends on IT initiatives clearly aligned to business goals, IT excellence, and driving technology innovation.
Includes a "Strategy on a page" template
Governance isn't optional, so keep it simple and make it flexible.
Unlock the full value of your service catalog with technical components.
Ensure your application portfolio delivers the best possible return on investment.
Tools and advice you need to be successful with Agile.
Understand Agile fundamentals, principles, and practices so you can apply them effectively in your organization.
Streamline business value delivery through the strategic adoption of DevOps practices.
Being Agile isn't about processes, it's about people.
Projects and products are not mutually exclusive.
Align your organization on the practices to deliver what matters most.
Build a product vision your organization can take from strategy through execution.
Deliver value at the scale of your organization through defining enterprise product families.
Strengthen the product owner's role in your organization by focusing on core capabilities and proper alignment.
Focus product delivery on business value-driven outcomes.
Mature your IT department by measuring what matters.
Be careful what you ask for because you will probably get it.
Expand on the financial model to give your initiative momentum.
Governance isn't optional, so keep it simple and make it flexible.
Embed benefits realization into your governance process to prioritize IT spending and confirm the value of IT.
Innovate and transform your business models with digital platforms.
Building a digital strategy is only half the battle: create a systematic roadmap of technology initiatives to execute the strategy and drive digital transformation.
Focus product delivery on business value-driven outcomes.
Mature your IT department by measuring what matters.
Right-size the guidelines of your requirements gathering process.
Back to basics: great products are built on great requirements.
Build quality into every step of your SDLC.
Drive software delivery throughput and quality confidence by extending your automation test coverage.
Make the case to manage technical debt in terms of business impact.
Avoid project failure by keeping the "B" in BPM.
Optimize and automate your business processes with a user-centric approach.
Don't waste your time focusing on the "as is." Focus on the improvements and the "to be."
Build trust by right-sizing your process using appropriate governance.
Effective maintenance ensures the long-term value of your applications.
Move beyond maintenance to ensure exceptional value from your apps.
Right-size your change management process.
Make the case to manage technical debt in terms of business impact.
Drive down your delivery time by eliminating development inefficiencies and bottlenecks while maintaining high quality.
Leverage knowledge of the business to become a strategic IT partner.
Create value by aligning your strategy to business goals and business risks.
Enhance your overall security posture with a defensible and prescriptive policy suite.
Leverage risk- and role-based access control to quantify and simplify the IAM process.
Empower the business to implement their own applications with a trusted business-IT relationship.
Ensure your software systems solution is architected to reflect stakeholders’ short-and long-term needs.
Extend IT, automation, and digital capabilities to the business with the right tools, good governance, and trusted organizational relationships.
Support RPA delivery with strong collaboration and management foundations.
Embrace the symbiotic relationship between the human and digital workforce.
Enable the business to achieve operational excellence, client intimacy, and product leadership with an innovative, Agile, and fit-for-purpose data architecture practice.
Deliver actionable business insights by creating a business-aligned reporting and analytics strategy.
Quality data drives quality business decisions.
Journey to the data marketplace ecosystems.
Key to building and fostering a data-driven culture.
Level the table before assembling the application integration puzzle or risk losing pieces.
Other choices entered by respondents:
During peak business hours, I witnessed a straightforward database field addition bring down a whole e-commerce platform. It was meant to be standard procedure, the type of “standard change” that is automatically approved because we have performed it innumerable times.
Adding a field to the end of a table and having applications retrieve data by field name instead of position made the change itself textbook low-impact. There is no need to alter the application or the functional flow. This could have been problematic in the past if you added a field in the middle of the list and it affected the values of other fields, but adding it at the end? That ought to have been impenetrable.
However, it wasn't.
Before I tell you what went wrong, let me explain why this is important to all of the IT professionals who are reading this.
Over the past three decades, industry data has repeatedly supported what this incident taught me: our presumptions about “safe” changes are frequently our greatest weakness. Upon reviewing the ITIL research, I was not surprised to learn that failed changes, many of which were categorized as “standard” or “low-risk,” are responsible for about 80% of unplanned outages.
When you look more closely, the numbers become even more concerning. Since I've been following the Ponemon Institute's work for years, I wasn't surprised to learn that companies with well-established change management procedures have 65% fewer unscheduled outages. The paradox surprised me: many of these “mature” procedures still operate under the premise that safety correlates with repetition.
What I had been observing in the field for decades was confirmed when Gartner released their research showing that standard changes are responsible for almost 40% of change-related incidents. The very changes we consider safe enough to avoid thorough review subtly create some of our greatest risks. IBM's analysis supports the pattern I've seen in innumerable organizations: standard changes cause three times as much business disruption due to their volume and our decreased vigilance around them, whereas emergency changes receive all the attention and scrutiny.
Aberdeen Group data indicates that the average cost of an unplanned outage has increased to $300,000 per hour, with change-related failures accounting for the largest category of preventable incidents. This data makes the financial reality stark.
What precisely went wrong with the addition of that database field that caused our e-commerce platform to crash?
We were unaware that the addition of this one field would cause the database to surpass an internal threshold, necessitating a thorough examination of its execution strategy. In its algorithmic wisdom, the database engine determined that the table structure had changed enough to necessitate rebuilding its access and retrieval mechanisms. Our applications relied on high-speed requests, and the new execution plan was terribly unoptimized for them.
Instead of completing quotes or purchases, customers were spending minutes viewing error pages. All applications began to time out while they awaited data that just wasn't showing up in the anticipated amounts of time. Thousands of transactions were impacted by a single extra field that should have been invisible to the application layer.
The field addition itself was not the primary cause. We assumed that since we had made similar adjustments dozens of times previously, this one would also act in the same way. Without taking into account the hidden complexities of database optimization thresholds, we had categorized it as a standard change based on superficial similarities.
My approach to standard changes was completely altered by this experience, and it is now even more applicable in DevOps-driven environments. Many organizations use pipeline deployments, which produce a standard change at runtime. It's great for speed and reliability, but it can easily fall into the same trap.
However, I have witnessed pipeline deployments result in significant incidents for non-code-related reasons. Due to timing, resource contention, or environmental differences that weren't noticeable in earlier runs, a deployment that performed flawlessly in development and staging abruptly fails in production. Although the automation boosts our confidence, it may also reveal blind spots.
Over the course of thirty years, I have come to the unsettling realization that there is no such thing as a truly routine change in complex systems. Every modification takes place in a slightly different setting, with varying environmental factors, data states, and system loads. What we refer to as “standard changes” are actually merely modifications with comparable processes rather than risk profiles.
For this reason, I support contextual change management. We must consider the system state, timing, dependencies, and cumulative effect of recent changes rather than just categorizing them based on their technical features. After three other changes have changed the system's behavior patterns, a change made at two in the morning on a Sunday with little system load is actually different from the same change made during peak business hours.
Effective change advisory boards must therefore go beyond assessing individual changes separately. I've worked with organizations where the change board carefully considered and approved each modification on its own merits, only to find that the cumulative effect of seemingly unrelated changes led to unexpected interactions and stress on the system. The most developed change management procedures I've come across mandate that their advisory boards take a step back and look at the whole change portfolio over a specified period of time. They inquire whether we are altering the database too frequently during a single maintenance window. Could there be unanticipated interactions between these three different application updates? What is the total resource impact of this week's approved changes?
It's the distinction between forest management and tree management. While each change may seem logical individually, when combined, they can create situations beyond the scope of any single change assessment.
Having worked in this field for thirty years, I've come to the conclusion that our greatest confidences frequently conceal our greatest vulnerabilities. Our primary blind spots frequently arise from the changes we've made a hundred times before, the procedures we've automated and standardized, and the adjustments we've labeled as “routine.”
Whether we should slow down our deployment pipelines or stop using standard changes is not the question. In the current competitive environment, speed and efficiency are crucial. The issue is whether we are posing the appropriate queries before carrying them out. Are we taking into account not only what the change accomplishes but also when it occurs, what else is changing at the same time, and how our systems actually look right now?
I've discovered that the phrase “we've done this before” is more dangerous in IT operations than “what could go wrong?” Because, despite what we may believe, we never actually perform the same action twice in complex systems.
Here is what I would like you to think about: which everyday modifications are subtly putting your surroundings at risk? Which procedures have you standardized or automated to the extent that you no longer challenge their presumptions? Most importantly, when was the last time your change advisory board examined your changes as a cohesive portfolio of system modifications rather than as discrete items on a checklist?
Remember that simple addition to a database field the next time you're tempted to accept a standard change. The most unexpected outcomes can occasionally result from the most routine adjustments.
I'm always up for a conversation if you want to talk about your difficulties with change management.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
See if a custom-of-the-shelf process optimization makes sense.
Determine the right (level of) governance for your implementation.
Prepare for the overall implementation journey and gather your requirements. Then conduct a stage-gate assessment of this phase.
Conduct a stage-gate assessment after every step below.
Review your dispositions to ensure they align with your goals.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Discover Info-Tech's six priorities for Infrastructure & Operations leaders.
|
Over the last several years, successful CEOs turned to their Infrastructure and Operations (I&O) departments to survive the effects of the pandemic. It was I&O leaders who were able to reconfigure critical infrastructure on the fly to support remote work, adapt to critical supply chain shortages, and work with lines of business managers to innovate operational workflows. 2023 promises to bring a new set of challenges. Building on the credibility established during the pandemic, I&O is in a unique position to influence the direction a business will take to be successful in a time of austerity. I&O members are going to be asked to mitigate the threats of volatility from recession pressures, new cybersecurity attacks, and operational process and litigation from regulatory mandates. At the same time, I&O members are being asked for fundamental digital transformation items to realize long-term opportunities to their organizations in 2023. Seemingly counter-intuitive in a time of economic slowdown, organizations in 2023 will want to start the groundwork to realizing the I&O opportunities that unstructured data and artificial intelligence have promised, while prepping for what has been mislabeled as the Metaverse. |
If you are in a traditionally risk adverse industry, you’re more likely to be impacted by the threat mitigation. Opportunistic I&O members will use 2023 to proactively jumpstart digital transformation. |
|
If I&O members learned anything from the last few years, it’s how to tactically respond to the disruptive waves often arising from sources external to the organization. The good news is that Info-Tech’s I&O priorities report provides forward-looking insights to help members become more proactive to the tsunami of change predicted in our Trends Report to happen over the next three to five years. Info-Tech I&O priorities are generated through a phased approach. The first phase senses and identifies mega and macro tends in the digital landscape to formulate hypotheses about the trends for the next three to five years. These hypotheses are validated by sending out a survey to Info-Tech members. The responses from 813 members was used to produce an Info-Tech Trends Report focused on major long-term trends. The I&O Priorities were determined by combining the I&O member responses within the Info-tech Trends Survey with insightful signals from secondary research, economic markets, regulatory bodies, industry organizations, and vendors. The six I&O priorities identified in this report are presented in a framework that highlight the impacts of an economic slowdown, growing regulatory reporting requirements, cybersecurity threats, smart governance of AI, embracing stewardship of data, and the looming explosion of augmented reality and Web 3.0 technologies. We also have a challenge exercise to help you communicate which priorities to focus your I&O organization on. Additionally, we linked some Info-tech research and tools related to the priorities that help your I&O organization formulate actionable plans for each area. |
Priorities Six forward-looking priorities for the next year. Focus Activity to help select which priorities are relevant for you. Actions Actionable Info-tech research and tools to help you deliver. |
|
Threats signals Enhance I&O Cybersecurity Produce ESG Reporting Recession Readiness |
Get out of your silo. Forget your job description and start doing what needs to be done. Infrastructure rarely has authority in these areas, but somehow it ends up with many of the responsibilities. You can't afford to be reactive. Forget about your traditional silo and get out in front of these topics. Not in your job description? Find out whose job it is and make them aware. Better yet – take charge! If you're going to be responsible you might as well be in control. |
|
Opportunities signals AI Governance: Watching the Watchers Prep for A Brave New Metaverse Data Governance: Cornerstone of Value |
Proper stewardship of data is an I&O must. If thought you had problems with your unstructured data, wait until you see the data sprawl coming from the metaverse. I&O needs to be so much more than just an order taker for the dev teams and lines of business. The sprawl of unstructured data in Word, Excel, PDF and PowerPoint was bad historically; imagine those same problems at metaverse scale! Simple storage and connectivity is no longer enough – I&O must move upstream with more sophisticated service and product offerings generated through proper governance and stewardship. |
|
The hidden message in this report is that I&O priorities extend beyond the traditional scope of I&O functions. I&O members need to collaborate across functional areas to successfully address the priorities presented in this report. Info-Tech can help! Align your priorities with our material on how to Build a Business-Aligned IT Strategy. Use a modified version of the Strategy Initiative Template (next slide) to convey your strong opinion on the priorities you need your stakeholders to know about. And do so in a way that is familiar so they will easily understand. |
Info-Tech 2023 Trends Survey Results |
|
Call your Executive Advisor or Counselor to help identify the one or two key messages you want to bring forward for success in 2023! |
Info-Tech IT Strategy Initiative Template, from the IT Strategy Presentation Template & Priorities Report Initiative Template . |
Enhance I&O Cybersecurity
Produce ESG Reporting
Recession Readiness
SIGNALS
|
Cybersecurity incidents are |
Cybersecurity incidents have |
Related Info-Tech Research |
|---|---|---|
|
Of the surveyed I&O members, 53% identified cybersecurity incidents as the number one threat disrupting their operations in 2023. It’s understandable, as over 18% of surveyed I&O members experienced a cybersecurity incident in 2022. Alarmingly, 10% of surveyed I&O members didn’t know if they had a cybersecurity incident. The impact to the organization was with 14% of those incidents directly impacting their organizations for anywhere from 6 to 60 days. |
The 2022 report “Cost of a Data Breach” was conducted by IBM and the Ponemon Institute using data from 550 companies (across 17 countries) that experienced a security incident during a 12-month period ending in March 2022. It highlighted that the average total organizational cost of a security breach globally was USD 4.35M (locally these numbers expand to USA at USD 9.44M, Canada at USD 5.64, UK at USD 5.05M, Germany at USD 4.85M). (Source: IBM, 2022) |
Organizations' exposure comes from internal and external sources. | The right tools and process can reduce the impact of a cybersecurity incident. | Related Info-Tech Research |
|---|---|---|
The IBM/Ponemon Institute report highlighted the following:
(Source: IBM, 2022) | The IBM/Ponemon Institute report also identified technologies and procedures to reduce the fiscal impacts of cybersecurity breaches. Having a dedicated security incident response team with a regularly tested plan reduced the incident cost by an average of USD 2.66M. A fully implemented AI security deduction and response automation system can provide average incident savings of 27.6%. |
|
Cybersecurity spending is a major and expanding expenditure for our members. |
Cybersecurity is going |
|
|---|---|---|
|
For 36% of surveyed I&O members, cybersecurity consumed between 10-20% of their total budget in 2022. Moreover, cybersecurity defense funding is expected to increase for 57% of I&O members. |
A third of surveyed I&O members viewed misinformation as a major risk to their organization for 2023 and 2024. Only 38% of the I&O members reported that they will have software in place to monitor and manage social media posts. |
Increasing environment and regulatory complexity demands more sophisticated cybersecurity operations. Infrastructure teams must be expected to work alongside and integrate with cybersecurity operations. |
Get out of your I&O silo and form cross-functional cybersecurity teams.
I&O priority actions
Establish a cross-functional security steering committee to coordinate security processes and technologies. The complexity of managing security across modern applications, cloud, IoT, and network infrastructure that members operate is greater than ever before and requires coordinated teamwork.
Contain the cyber threat with zero trust (ZT) architecture. Extend ZT to network and critical infrastructure to limit exposure.
Leverage AI to build vigilant security intelligence. Smart I&O operators will make use of AI automation to augment their security technologies to help detect threats and contain security incidents on critical infrastructure.
Build specialized cybersecurity incident management protocols with your service desk. Build integrated security focused teams within service desk operations that continually test and improve security incident response protocols internally and with specialized security vendors. In some organizations, security incident response teams extend beyond traditional infrastructure into social media. Work cross-functionally to determine the risk exposure to misinformation and incident response procedures.
Treat lost or stolen equipment as a security incident. Develop hardware asset management protocols for tracking and reporting on these incidents and keep a record of equipment disposal. Implement tools that allow for remote deletion of data and report on lost or stolen equipment.
SIGNALS
Government mandates present an operational risk to I&O members. | ESG reporting is | Related Info-Tech Research |
|---|---|---|
Surveyed members identified government-enacted policy changes to be a top risk to disrupting to their business operations in 2023. One of the trends identified by Info-Tech is that the impact of regulations on environmental, social, and governance (ESG) reporting are being rolled out by governments worldwide. | Alarmingly, only 7% of surveyed members responded that they could very accurately report on their carbon footprint and 23% said they were not able to report accurately at all. |
SIGNALS
ESG reporting has greatly expanded since a 2017 report by Task Force on Climate-Related Financial Disclosures (TCFD, 2017) which recommended that organizations disclose climate-related financial metrics for investors to appropriately price climate-related risks to share price. In 2021, the Swiss Finance Institute research paper (Sautner, 2021) identified 29 countries that require ESG reporting, primarily for larger public companies, financial institutions, and state-owned corporations.
Global ESG mandates
29 nations with ESG mandates identified by the Swiss Finance Institute
SIGNALS
|
ESG mandates are being rolled out globally. |
|
|
The EU has mandated ESG reporting for approximately 11,700 large public companies with more than 500 employees under the Non-Financial Reporting Directive (NFRD), since 2014. The EU is going to replace the NFRD with the Corporate Sustainability Reporting Directive (European Council, 2022), which has set a 3-year timetable for escalating the ESG reporting level to what is estimated to be about 75% of EU total turnover (WorldFavor, 2022).
|
It's been a long time since most enterprises had to report on things like power efficiency factors. But don't think that being in the cloud will insulate you from a renewed interest in ESG reporting. |
CALL TO ACTION
Being unprepared for new ESG reporting mandates without a clear and validated ESG reporting process puts your organization at risk.
I&O priority actions
Understand ESG risk exposure. Define the gap between what ESG reporting is required in your jurisdiction and current reporting capabilities to meet them. Build the I&O role with responsibility for ESG reporting.
Include vendors in ESG reporting. Review infrastructure facilities with landlords, utilities, and hosting providers to see if they can provide ESG reporting on sustainable power generation, then map it to I&O power consumption as part of their contractual obligations. Ask equipment vendors to provide ESG reporting on manufacturing materials and energy consumption to boot-strap data collection.
Implement a HAM process to track asset disposal and other types of e-waste. Update agreements with disposal vendors to get reporting on waste and recycle volumes.
Implement an ESG reporting framework. There are five major ESG reporting frameworks being used globally. Select one of the frameworks below that makes sense for your organization, and implement it.
ISO 14001 Environmental Management: Part of the ISO Technical Committee family of standards that allows your organization to understand its legal requirements to become certified in ESG.
Global Reporting Initiative (GRI) Sustainability Reporting Standards: GRI has been developing ESG reporting standards since 1997. GRI provides a modular ESG framework applicable to all sizes and sectors of organizations worldwide.
Principles for Responsible Investment: UN-developed framework for ESG reporting framework for disclosure in responsible investments.
Sustainability Accounting Standards Board (SASB): ESG report framework to be used by investors.
UN Global Compact: ESG reporting framework based on 10 principles that organizations can voluntarily contribute data to.
Implement a HAM process to track asset disposal and other types of e-waste. Update agreements with disposal vendors to get reports on waste and recycle volumes.
SIGNALS
|
Managing accelerated technical debt. |
Recessionary pressures. |
Related Info-Tech Research |
|
I&O members experienced a spike in technical debt following the global pandemic economic shutdown, workforce displacement, and highly disrupted supply chains. 2023 presents a clear opportunity to work on these projects. |
The shortages in workforce and supply chain have accelerated inflation post pandemic. Central banks have started to slow down inflation in 2022 by raising interest rates. However, the World Bank has forecast a potential 2% rise in interest rates as the battle with inflation continues into 2023 and beyond, which could set off a global slowdown in GDP growth to 0.5%, qualifying as a recession. If interest rates continue to climb, I&O members may struggle with the higher cost of capital for their investments. (Source: World Bank Organization, 2022) |
SIGNALS
|
I&O budgets expected to increase. |
Focused budgetary increases. |
|
|
Despite economists’ prediction of a looming recession and inflationary pressures, only 11% of I&O members surveyed indicated that they anticipated any reduction in IT budgets for 2023. In fact, 44% of I&O members expected an increase of IT budgets of between 6% and 30%. |
These increases in budget are not uniform across all investments. Surveyed I&O members indicated that the largest anticipated budget increases (compared to 2022) were in the areas of:
|
"2022 has been the first true opportunity to start getting caught up on technical debt stemming from the post pandemic supply chain and resource shortages. That catch-up is going to continue for some time. Unfortunately, the world isn't sitting still while doing that. In fact, we see new challenges around inflationary pressures. 2023 planning is going to be a balancing act between old and new projects." Paul Sparks, |
SIGNALS
The responses indicated that I&O members expect decreased reinvestment for 2023 for the following:
Make sure you can clearly measure the value of all budgeted I&O activities.
Anything that can't demonstrate clear value to leadership is potentially on the chopping block.
CALL TO ACTION
Get ahead of inflationary pressures with early budgetary planning, and identify the gap between the catch-up projects and required critical net new investments.
II&O priority actions
Hedge against inflation on infrastructure projects. Develop and communicate value-based strategies to lock in pricing and mitigate inflationary risk with vendors.
Communicate value-add on all I&O budgeted items. Define an infrastructure roadmap to highlight which projects are technical debt and which are new strategic investments, and note their value to the organization.
Look for cost saving technologies. Focus on I&O projects that automate services to increase productivity and optimize head count.
AI governance: Watching the watchers
Data stewardship: Cornerstone of value
Prep for a brave new metaverse
SIGNALS
Continued investment | AI technology is permeating diverse I&O functional areas. | Related Info-Tech Research |
About 32% of survey respondents who work in I&O said that they already invest in AI, and 40% intend to invest in 2023. | I&O members have identified the following areas as the top five focal points for AI uses within their organizations.
|
SIGNALS
|
Consequences for misbehaving AI. |
|
|
I&O leaders can expect to have silos of AI in pockets scattered across the enterprise. Without oversight on the learning model and the data used for training and analytics there is a risk of overprovisioning, which could reduce the efficiency and effectiveness of AI models and results. This scale advantage of AI could result in operational inefficiencies without oversight. For example, bad governance means garbage in / garbage out. Which is worse: getting 100 outputs from a system with a 1% error rate, or getting 10,000 outputs from a system with an 1% error rate? These are just the operational issues; legally you can be on the hook, as well. The EU Parliament has issued a civil liability regime for AI (European Parliament, n.d.) which imposes liability to operators of AI systems, regardless of whether they acted with operational due diligence. Additionally, the IEEE (IEEE, 2019) is advocating for legal frameworks and accountability for AI that violates human rights and privacy laws and causes legal harm. |
Who is going to instill standards for AI Operations? Who is going to put in the mechanisms to validate and explain the output of AI black boxes? If you said it’s going to end up |
CALL TO ACTION
Establish I&O within an AI governance program to build trust in AI results and behaviors and limit legal exposure.
I&O priority actions
Define who has overall AI accountability for AI governance within I&O. This role is responsible for establishing strategic governance metrics over AI use and results, and identifying liability risks.
Maintain an inventory of AI use. Conduct an audit of where AI is used within I&O, and identify gaps in documentation and alignment with I&O processes and organizational values.
Define an I&O success map. Provide transparency of AI use by generating pseudo code of AI models, and scorecard AI decision making with expected predictions and behavioral actions taken.
Manage bias in AI decision making. Work with AI technology vendors to identify how unethical bias can enter the results, using operational data sets for validation prior to rollout.
Protect AI data sets from manipulation. Generate new secure storage for AI technology audit trails on AI design making and results. Work with your security team to ensure data sets used by AI for training can’t be corrupted.
SIGNALS
Data volumes grow | Data is seen as a source for generating new value. | Related Info-Tech Research |
Of surveyed I&O members, 63% expected to see the data storage grow by at least 10% in 2023, and 15% expected a 30% or more growth in data storage volumes. | I&O members identified the top three ways data brings value to the organization:
|
SIGNALS
Approach to data analysis is primarily done in-house.
85% of surveyed I&O members are doing data analysis with custom-made or external tools. Interestingly, 10% of I&O members do not conduct any data analysis.
Members are missing a formal data governance process.
81% of surveyed I&O members do not have a formal or automated process for data governance. Ironically, 24% of members responded that they aim to have publicly accessible data-as-a-service or information repositories.
Despite investment in data initiatives, organizations carry high levels of data debt.
Info-Tech research, Establish Data Governance, points out that data debt, the accumulated cost associated with sub-optimal governance of data assets, is a problem for 78% of organizations.
What the enterprise expects out of enterprise storage is much more complicated in 2023.
Data protection and governance are non-negotiable aspects of enterprise storage, even when it’s unstructured.
SIGNALS
Data quality is the primary driver for data governance. | The data governance market | Related Info-Tech Research |
In the 2022 Zaloni survey of data governance professionals, 71% indicated that consistent data quality was the top metric for data governance, followed by reduced time to insight and regulatory compliance. (Source: Zaloni DATAVERSITY, 2022) | The Business Research Company determined that the global data governance market is expected to grow from $3.28 billion in 2022 to $7.42 billion in 2026 at a CAGR of 22.7% in response to 74 zettabytes of data in 2021, with a growth rate of 1.145 trillion MB of new data being created every day. (Source: Business Research Company, 2022) |
CALL TO ACTION
Develop a data governance program that includes an I&O data steward for oversight.
I&O priority actions
Establish an I&O data steward. Make data governance by establishing a data steward role with accountability for governance. The steward works collaboratively with DataOPs to control access to I&O data, enforce policies, and reduce the time to make use of the data.
Define a comprehensive storage architecture. If you thought you had a data sprawl problem before, wait until you see the volume of data generated from IoT and Web 3.0 applications. Get ahead of the problem by creating an infrastructure roadmap for structured and unstructured data storage.
Build a solid backbone for AI Operations using data quality best practices. Data quality is the foundation for generation of operational value from the data and artificial intelligence efforts. Focus on using a methodology to build a culture of data quality within I&O systems and applications that generate data rather than reactive fixes.
Look to partner with third-party vendors for your master data management (MDM) efforts. Modern MDM vendors can work with your existing data fabrics/lake and help leverage your data governance policies into the cloud.
SIGNALS
From science fiction to science fact.
The term metaverse was coined in 1992 by Neal Stephenson and is a common theme in science fiction. For most I&O surveyed professionals, the term metaverse conjures up more confusion than clarity, as it’s not one place, but multiple metaverse worlds. The primordial metaverse was focused on multiplayer gaming and some educational experiences. It wasn’t until recently that it gained a critical mass in the fashion and entertainment industries with the use of non-fungible tokens (NFT). The pandemic created a unique opportunity for metaverse-related technologies to expand Web 3.0.
Related Info-Tech Research
SIGNALS
Collaboration and beyond.
On one hand, metaverse technologies virtual reality(VR)/augmented reality (AR) headsets can be a method of collaborating internally within a single organization. About 10% of our surveyed I&O members engaged this type of collaborative metaverse in 2022, with another 24% looking to run proof of concept projects in 2023. However, there is a much larger terrain for metaverse projects outside of workforce collaboration, which 17% of surveyed I&O members are planning to engage with in 2023.
These are sophisticated new metaverse worlds, and digital twins of production environments are being created for B2B collaboration, operations, engineering, healthcare, architecture, and education that include the use of block chain, NFTs, smart contracts, and other Web 3.0 technologies
“They are the audiovisual bodies that people use to communicate with each other in the Metaverse.”
Neal Stephenson,
Snow Crash 1992
SIGNALS
Security in the context of the metaverse presents new challenges to I&O. The infrastructure that runs the metaverse is still vulnerable to “traditional” security threats. New attack vectors include financial and identity fraud, privacy and data loss, along with new cyber-physical threats which are predicted to occur as the metaverse begins to integrate with IoT and other 3D objects in the physical world.
The ultimate in "not a product" – the metaverse promises to be a hodgepodge of badly standardized technologies for the near future.
Be prepared to take care of pets and not cattle for the foreseeable future, but keep putting the fencing around the ranch.
SIGNALS
Generating new wave of sophisticated engineering coming. | Economics boom around metaverse set to explode. | Related Info-Tech Research |
Beyond the current online educational resources, there are reputable universities around the world, including Stanford University, that are offering courses on metaverse and Web 3.0 concepts. (Source: Arti, 2022) | So, what’s providing the impetus for all this activity and investment? Economics. In their 2022 report, Metaverse and Money, Citi estimated that the economic value of the metaverse(s) will have 900M to 1B VR/AR users and 5 billion Web 3.0 users with market sizes of $1-2T and $8-$13T, respectively. Yes, that’s a “T” for Trillions. (Source: Ghose, 2022) |
CALL TO ACTION
Ready or not, the metaverse is coming to an infrastructure near you. Start expanding I&O technologies and processes to support a metaverse infrastructure.
Develop a plan for network upgrades.
A truly immersive VR/AR experience requires very low latency. Identify gaps and develop a plan to enhance your network infrastructure surrounding your metaverse space(s) and end users.
Extend security posture into the metaverse.
Securing the infrastructure that runs your metaverse is going to extend the end-user equipment used to navigate it. More importantly, security policies need to encompass the avatars that navigate it and the spatial web that they interact with, which can include physical world items like IoT.
Metaverse theft prevention
Leverage existing strategies to identify management in the metaverse. Privacy policies need to extend their focus to data loss prevention within the metaverse.
Collaborate
The skill set required to build, deploy, manage, and support the metaverse is complex. Develop a metaverse support organization that extends beyond I&O functions into security, DevOps, and end-user experiences.
Educate
Web 3.0 technologies and business models are complex. Education of I&O technical- and commerce-focused team members is going to help prevent you from getting blindsided. Seek out specialized training programs for technical staff and strategic education for executives, like the Wharton School of Business certification program.
![]() |
| |
|---|---|---|
John Annand Principal Research Director | Theo Antoniadis Principal Research Director | Contributors Paul Sparks, 2 Anonymous Contributors |
Figuring out the true nature of the “Turbo” button of his 486DX100 launched John on a 20-year career in managed services and solution architecture, exploring the secrets of HPC, virtualization, and DIY WANs built with banks of USR TotalControl modems. Today he focuses his research and advisory on software-defined infrastructure technologies, strategy, organization, and service design in an increasingly Agile and DevOps world. | Theo has decades of operational and project management experience with start-ups and multinationals across North America and Europe. He has held various consulting, IT management and operations leadership positions within telecommunications, SaaS, and software companies. |
“3 Cybersecurity Trends that are Changing Financial Data Management." FIMA US. Accessed August 2022.
Arti. “While much of the world is just discovering the Metaverse, a number of universities have already established centers for studying Web 3." Analytics Insight. 10 July 2022.
“Artificial intelligence (AI) for cybersecurity." IBM. Accessed September 2022
“Business in the Metaverse Economy." Wharton School of University of Pennsylvania. Accessed October 2022.
“Cost of a data breach 2022: A million-dollar race to detect and respond." IBM. Accessed September 2022.
“Countries affected by mandatory ESG reporting – here’s the list." New Zealand Ministry of Business, Innovation & Employment. Accessed September 2022.
“Countries affected by mandatory ESG reporting – here’s the list.” WorldFavor. Accessed September 2022.
Crenshaw, Caroline A. “SEC Proposes to Enhance Disclosures by Certain Investment Advisers and Investment Companies About ESG Investment Practices." U.S. Securities and Exchange Commission. May 2022.
“Cutting through the metaverse hype: Practical guidance and use cases for business." Avanade. Accessed October 2022.
“Data Governance Global Market Sees Growth Rate Of 25% Through 2022." The Business Research Company. August 2022.
“DIRECTIVE 2014/95/EU OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 22 October 2014 amending Directive 2013/34/EU as regards disclosure of non-financial and diversity information by certain large undertakings and groups." UER-Lex. Accessed September 2022.
"Ethically Aligned Design: A Vision for Prioritizing Human Well-being with Autonomous and Intelligent Systems." IEEE. March 2019.
“European Parliament resolution of 20 October 2020 with recommendations to the Commission on a civil liability regime for artificial intelligence." European Parliament. Accessed October 2022.
Ghose, Ronit et al. "Metaverse and Money." Citi GPS. March 2022.
Hernandez, Roberto, et al. “Demystifying the metaverse." PWC. Accessed August 2022.
Info-Tech Trends Report Survey, 2023; N=813.
“ISO 14000 Family: Environmental Management." ISO. Accessed October 2022.
Knight, Michelle & Bishop, Annie, ”The 2022 State of Cloud Data Governance.“ Zaloni DATAVERSITY. 2022.
Kompella, Kashyap, “What is AI governance and why do you need it?“ TechTarget. March 2022.
“Management of electronic waste worldwide in 2019, by method." Statista. 2022.
“Model Artificial Intelligence Governance Framework and Assessment Guide.“ World Economic Forum. Accessed September 2022.
“Model Artificial Intelligence Governance Framework." PDPC Singapore. Accessed October 2022.
“New rules on corporate sustainability reporting: provisional political agreement between the Council and the European Parliament.“ European Council. June 2022.
"OECD Economic Outlook Volume 2022." OECD iLibrary. June 2022.
"Recommendations of the Task Force on Climate-related Financial Disclosures." TCFD. Accessed August 2022.
“Risk of Global Recession in 2023 Rises Amid Simultaneous Rate Hikes.” World Bank Organization. September 2022.
Sautner, Zacharias, et al. “The Effects of Mandatory ESG Disclosure around the World.” SSRN. November 2021.
Sondergaard, Peter. “AI GOVERNANCE – WHAT ARE THE KPIS? AND WHO IS ACCOUNTABLE?“ The Sondergaard Group. November 2019.
Srivastavam Sudeep, “How can your business enter the Metaverse?." Appinventiv.
September 2022.
“Standards Overview." SASB. Accessed October 2022.
Stephenson, Neal. Snow Crash. Bantam Books, 1992.
“Sustainability Reporting Standards." Global Reporting Initiative. Accessed October 2022.
“The Ten Principles of the UN Global Compact." UN Global Compact. Accessed October 2022.
Tian Tong Lee, Sheryl. "China Unveils ESG Reporting Guidelines to Catch Peers.” Bloomberg. May 2022.
“What are the Principles for Responsible Investment?" UNPRI. Accessed October 2022.
"What is the EU's Corporate Sustainability Reporting Directive (CSRD)?" WorldFavor.
June 2022.
West, Darrell M. “Six Steps to Responsible AI in the Federal Government.“ Brookings Institution. March 2022. Web.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Acquire a holistic perspective of the development team, process, and tools to identify the bottlenecks and inefficiency points that are significantly delaying releases.
Identify the development guiding principles and artifact management practices and build automation and continuous integration processes and tools that best fit the context and address the organization’s needs.
Prioritize lean implementation initiatives in a gradual, phased approach and map the critical stakeholders in the lean transformation.
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.
Assess the current state of your development environment.
Select a pilot project to demonstrate the value of your optimization.
Realization of the root causes behind the bottlenecks and inefficiencies in your current development process.
Valuation of your current development tools.
Selection of a pilot project that will be used to gather the metrics in order obtain buy-in for wider optimization initiatives.
1.1 Assess your readiness to transition to lean development.
1.2 Conduct a SWOT analysis and value-stream assessment of your current development process.
1.3 Evaluate your development tools.
1.4 Select a pilot project.
Lean development readiness assessment
Current state analysis of development process
Value assessment of existing development tools
Pilot project selection
Establish your development guiding principles.
Enhance the versioning and management of your development artifacts.
Automatically build and continuously integrate your code.
Grounded and well-understood set of guiding principles that are mapped to development tasks and initiatives.
Version control strategy of development artifacts, including source code, adapted to support lean development.
A tailored approach to establish the right environment to support automated build, testing, and continuous integration tools.
2.1 Assess your alignment to the lean principles.
2.2 Define your lean development guiding principles.
2.3 Define your source code branching approach.
2.4 Define your build automation approach.
2.5 Define your continuous integration approach.
Level of alignment to lean principles
Development guiding principles
Source code branching approach
Build automation approach.
Continuous integration approach
Prioritize your optimization initiatives to build an implementation roadmap.
Identify the stakeholders of your lean transformation.
Phased implementation roadmap that accommodates your current priorities, constraints, and enablers.
Stakeholder engagement strategy to effectively demonstrate the value of the optimized development environment.
3.1 Identify metrics to gauge the success of your lean transformation.
3.2 List and prioritize your implementation steps.
3.3 Identify the stakeholders of your lean transformation.
List of product, process, and tool metrics
Prioritized list of tasks to optimize your development environment
Identification of key stakeholders
This 2023-Q1 research agenda slide deck provides you with a comprehensive overview of our most up-to-date published research. Each piece offers you valuable insights, allowing you to take effective decisions and informed actions. All TY|Info-tech research is backed by our team of expert analysts who share decades of IT and industry experience.
Agile and Service Management are not necessarily at odds; find the integration points to solve specific problems.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Understand how service management integrates with Agile software development practices, and how to solve the most common challenges to work efficiently and deliver business value.
Use this tool to identify your stakeholders to engage when working on the service management integration.
Use this tool to identify which of your current practices might already be aligned with Agile mindset and which might need adjustment. Identify integration challenges with the current service management practices.
Many organizations believe that once they have implemented Agile that they no longer need any service management framework, like ITIL. They see service management as "old" and a roadblock to deliver products and services quickly. The culture clash is obvious, and it is the most common challenge people face when trying to integrate Agile and service management. However, it is not the only challenge. Agile methodologies are focused on optimized delivery. However, what happens after delivery is often overlooked. Operations may not receive proper communication or documentation, and processes are cumbersome or non-existent. This is a huge paradox if an organization is trying to become nimbler. You need to find ways to integrate your Agile practices with your existing Service Management processes.

Renata Lopes
Senior Research Analyst
Organizational Transformation Practice
Info-Tech Research Group
Agile and Service Management are not necessarily at odds Find the integration points to solve specific problems.
46% of respondents identified inconsistent processes and practices across teams as a challenge.
Source: Digital.ai, 2021
43% of respondents identified Culture clashes as a challenge.
Source: Digital.ai, 2021
Agile development is an umbrella term for several iterative and incremental development methodologies to develop products.
In order to achieve Agile development, organizations will adopt frameworks and methodologies like Scaled Agile Framework (SAFe), Scrum, Large Scaled Scrum (LeSS), DevOps, Spotify Way of Working (WoW), etc.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Analyze the four key benefits of blockchain as they relate to the transportation and logistics industry to understand how the technology can resolve issues being experienced by industry incumbents.
Brainstorm a set of blockchain use cases for your organization and apply design thinking tactics to evaluate and select the optimal one to pitch to your executives for prototyping.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Consistently meet project goals through enhanced PM knowledge and awareness.
Take action and mitigate a pitfall before it becomes a problem.
Learn from issues encountered to help map PM strategies for future projects.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Improve employee engagement and ultimately the organization’s bottom line.
Have a productive engagement feedback discussion with teams.
Facilitate effective team engagement action planning.
Solicit employee pain points that could potentially hinder their engagement.
Develop a stronger relationship with employees to drive engagement.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Plan out your employee engagement program and launch the Employee Experience Monitor survey for your team.
Interpret your Employee Experience Monitor results, understand what they mean in the context of your team, and involve your staff in brainstorming engagement initiatives.
Select engagement initiatives for maximal impact, create an action plan, and establish open and ongoing communication about engagement with your team.
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.
Set up the EXM and collect a few months of data to build on during the workshop.
Arm yourself with an index of employee experience and candid feedback from your team to use as a starting point for your engagement program.
1.1 Identify EXM use case.
1.2 Identify engagement program goals and obstacles.
1.3 Launch EXM.
Defined engagement goals.
EXM online dashboard with three months of results.
To understand the current state of engagement and prepare to discuss the drivers behind it with your staff.
Empower your leadership team to take charge of their own team's engagement.
2.1 Review EXM results to understand employee experience.
2.2 Finalize focus group agendas.
2.3 Train managers.
Customized focus group agendas.
Establish an open dialogue with your staff to understand what drives their engagement.
Understand where in your team’s experience you can make the most impact as an IT leader.
3.1 Identify priority drivers.
3.2 Identify engagement KPIs.
3.3 Brainstorm engagement initiatives.
3.4 Vote on initiatives within teams.
Summary of focus groups results
Identified engagement initiatives.
Learn the characteristics of successful engagement initiatives and build execution plans for each.
Choose initiatives with the greatest impact on your team’s engagement, and ensure you have the necessary resources for success.
4.1 Select engagement initiatives with IT leadership.
4.2 Discuss and decide on the top five engagement initiatives.
4.3 Create initiative project plans.
4.4 Build detailed project plans.
4.5 Present project plans.
Engagement project plans.
There are four key scenarios or entry points for IT as the selling/divesting organization in M&As:
Consider the ideal scenario for your IT organization.
Divestitures are inevitable in modern business, and IT’s involvement in the process should be too. This progression is inspired by:
Prepare for a sale/divestiture transaction by:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Be an innovative IT leader by suggesting how and why the business should engage in an acquisition or divestiture.
Create a standardized approach for how your IT organization should address divestitures or sales.
Comply with due diligence, prepare the IT environment for carve-out possibilities, and establish the separation project plan.
Deliver on the separation project plan successfully and communicate IT’s transaction value to 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.
Establish the transaction foundation.
Discover the motivation for divesting or selling.
Formalize the program plan.
Create the valuation framework.
Strategize the transaction and finalize the M&A strategy and approach.
All major stakeholders are on the same page.
Set up crucial elements to facilitate the success of the transaction.
Have a repeatable transaction strategy that can be reused for multiple organizations.
1.1 Conduct the CIO Business Vision and CEO-CIO Alignment diagnostics.
1.2 Identify key stakeholders and outline their relationship to the M&A process.
1.3 Understand the rationale for the company's decision to pursue a divestiture or sale.
1.4 Assess the IT/digital strategy.
1.5 Identify pain points and opportunities tied to the divestiture/sale.
1.6 Create the IT vision statement and mission statement and identify IT guiding principles and the transition team.
1.7 Document the M&A governance.
1.8 Establish program metrics.
1.9 Create the valuation framework.
1.10 Establish the separation strategy.
1.11 Conduct a RACI.
1.12 Create the communication plan.
1.13 Prepare to assess target organizations.
Business perspectives of IT
Stakeholder network map for M&A transactions
Business context implications for IT
IT’s divestiture/sale strategic direction
Governance structure
M&A program metrics
IT valuation framework
Separation strategy
RACI
Communication plan
Prepared to assess target organization(s)
Establish the foundation.
Discover the motivation for separation.
Identify expectations and create the carve-out roadmap.
Prepare and manage employees.
Plan the separation roadmap.
All major stakeholders are on the same page.
Methodology identified to enable compliance during due diligence.
Employees are set up for a smooth and successful transition.
Separation activities are planned and assigned.
2.1 Gather and evaluate the stakeholders involved, M&A strategy, future-state operating model, and governance.
2.2 Review the business rationale for the divestiture/sale.
2.3 Establish the separation strategy.
2.4 Create the due diligence charter.
2.5 Create a list of IT artifacts to be reviewed in the data room.
2.6 Create a carve-out roadmap.
2.7 Create a service/technical transaction agreement.
2.8 Measure staff engagement.
2.9 Assess the current culture and identify the goal culture.
2.10 Create employee transition and functional workplans.
2.11 Establish the separation roadmap.
2.12 Establish and align project metrics with identified tasks.
2.13 Estimate integration costs.
Stakeholder map
IT strategy assessed
IT operating model and IT governance structure defined
Business context implications for IT
Separation strategy
Due diligence charter
Data room artifacts
Carve-out roadmap
Service/technical transaction agreement
Engagement assessment
Culture assessment
Employee transition and functional workplans
Integration roadmap and associated resourcing
Establish the transaction foundation.
Discover the motivation for separation.
Plan the separation roadmap.
Prepare employees for the transition.
Engage in separation.
Assess the transaction outcomes.
All major stakeholders are on the same page.
Separation activities are planned and assigned.
Employees are set up for a smooth and successful transition.
Separation strategy and roadmap are executed to benefit the organization.
Review what went well and identify improvements to be made in future transactions.
3.1 Identify key stakeholders and outline their relationship to the M&A process.
3.2 Gather and evaluate the M&A strategy, future-state operating model, and governance.
3.3 Review the business rationale for the divestiture/sale.
3.4 Establish the separation strategy.
3.5 Prioritize separation tasks.
3.6 Establish the separation roadmap.
3.7 Establish and align project metrics with identified tasks.
3.8 Estimate separation costs.
3.9 Measure staff engagement.
3.10 Assess the current culture and identify the goal culture.
3.11 Create employee transition and functional workplans.
3.12 Complete the separation by regularly updating the project plan.
3.13 Assess the service/technical transaction agreement.
3.14 Confirm separation costs.
3.15 Review IT’s transaction value.
3.16 Conduct a transaction and separation SWOT.
3.17 Review the playbook and prepare for future transactions.
M&A transaction team
Stakeholder map
IT strategy assessed
IT operating model and IT governance structure defined
Business context implications for IT
Separation strategy
Separation roadmap and associated resourcing
Engagement assessment
Culture assessment
Employee transition and functional workplans
Updated separation project plan
Evaluated service/technical transaction agreement
SWOT of transaction
M&A Sell Playbook refined for future transactions
IT has always been an afterthought in the M&A process, often brought in last minute once the deal is nearly, if not completely, solidified. This is a mistake. When IT is brought into the process late, the business misses opportunities to generate value related to the transaction and has less awareness of critical risks or inaccuracies.
To prevent this mistake, IT leadership needs to develop strong business relationships and gain respect for their innovative suggestions. In fact, when it comes to modern M&A activity, IT should be the ones suggesting potential transactions to meet business needs, specifically when it comes to modernizing the business or adopting digital capabilities.
IT needs to stop waiting to be invited to the acquisition or divestiture table. IT needs to suggest that the table be constructed and actively work toward achieving the strategic objectives of the business.
There are four key scenarios or entry points for IT as the selling/divesting organization in M&As:
Consider the ideal scenario for your IT organization.
Some of the obstacles IT faces include:
These obstacles often arise when IT waits to be invited into the transaction process and misses critical opportunities.
Prepare for a sale/divestiture transaction by:
As the number of merger, acquisition, and divestiture transactions continues to increase, so too does IT’s opportunity to leverage the growing digital nature of these transactions and get involved at the onset.
The total value of transactions in the year after the pandemic started was $1.3 billion – a 93% increase in value compared to before the pandemic. (Nasdaq)
71% of technology companies anticipate that divestitures will take place as a result of the COVID-19 pandemic. (EY, 2020)
Only half of M&A deals involve IT (Source: IMAA Institute, 2017)
In hindsight, it’s clear to see: Involving IT is just good business.
47% of senior leaders wish they would have spent more time on IT due diligence to prevent value erosion. (Source: IMAA Institute, 2017)
“Solutions exist that can save well above 50 percent on divestiture costs, while ensuring on-time delivery.” (Source: SNP)
Acquisitions and divestitures are inevitable in modern business, and IT’s involvement in the process should be too. This progression is inspired by:
A merger looks at the equal combination of two entities or organizations. Mergers are rare in the M&A space, as the organizations will combine assets and services in a completely equal 50/50 split. Two organizations may also choose to divest business entities and merge as a new company.
The most common transaction in the M&A space, where an organization will acquire or purchase another organization or entities of another organization. This type of transaction has a clear owner who will be able to make legal decisions regarding the acquired organization.
An organization may decide to sell partial elements of a business to an acquiring organization. They will separate this business entity from the rest of the organization and continue to operate the other components of the business.
A true merger does not exist, as there is always someone initiating the discussion. As a result, most M&A activity falls into acquisition or divestiture categories.
This blueprint is only focused on the sell side:
The buy side is focused on:
For more information on acquisitions or purchases, check out Info-Tech’s Mergers & Acquisitions: The Buy Blueprint.
1. Proactive |
2. Discovery & Strategy |
3. Due Diligence & Preparation |
4. Execution & Value Realization |
|
Phase Steps |
|
|
|
|
Phase Outcomes |
Be an innovative IT leader by suggesting how and why the business should engage in an acquisition or divestiture. |
Create a standardized approach for how your IT organization should address divestitures or sales. |
Comply with due diligence, prepare the IT environment for carve-out possibilities, and establish the separation project plan. |
Deliver on the separation project plan successfully and communicate IT’s transaction value to the business. |
1. Proactive | 2. Discovery & Strategy | 3. Valuation & Due Diligence | 4. Execution & Value Realization |
|
|
|
|
IT controls if and when it gets invited to support the business through a purchasing growth transaction. Take control of the process, demonstrate the value of IT, and ensure that separation of IT environments does not lead to unnecessary and costly decisions.
CIOs on the forefront of digital transformation need to actively look for and suggest opportunities to acquire or partner on new digital capabilities to respond to rapidly changing business needs.
IT organizations that have an effective M&A program plan are more prepared for the transaction, enabling a successful outcome. A structured strategy is particularly necessary for organizations expected to deliver M&As rapidly and frequently.
IT often faces unnecessary separation challenges because of a lack of preparation. Secure the IT environment and establish how IT will retain employees early in the transaction process.
IT needs to demonstrate value and cost savings within 100 days of the transaction. The most successful transactions are when IT continuously realizes synergies a year after the transaction and beyond.
The M&A Sell Playbook should be a reusable document that enables your IT organization to successfully deliver on any divestiture transaction.
See a one-page overview of each phase of the transaction.
Read a one-page case study for each phase of the transaction.
Manage the separation process of the divestiture/sale using this SharePoint template.
Manage the separation process of the divestiture/sale using this Excel tool if you can’t or don’t want to use SharePoint.
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." |
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 10 calls over the course of 2 to 4 months.
Phase 1 |
Phase 2 | Phase 3 | Phase 4 |
|
|
|
|
As the number of merger, acquisition, or divestiture transactions driven by digital means continues to increase, IT has an opportunity to not just be involved in a transaction but actively seek out potential deals.
In the Proactive phase, the business is not currently considering a transaction. However, the business could consider one to reach its strategic goals. IT organizations that have developed respected relationships with the business leaders can suggest these potential transactions.
Understand the business’ perspective of IT, determine who the critical M&A stakeholders are, valuate the IT environment, and examine how it supports the business goals in order to suggest an M&A transaction.
In doing so, IT isn’t waiting to be invited to the transaction table – it’s creating it.
Goal: To support the organization in reaching its strategic goals by suggesting M&A activities that will enable the organization to reach its objectives faster and with greater-value outcomes.
Before coming into the Proactive phase, you should have addressed the following:
Review the Executive Brief for more information on mergers, acquisitions, and divestitures for selling organizations.
Understand how the business perceives IT and establish strong relationships with critical M&A stakeholders.
Misalignment in target state requires further communication between the CIO and CEO to ensure IT is striving toward an agreed-upon direction.
The core services of IT are important when determining what IT should focus on. The most important services with the lowest satisfaction offer the largest area of improvement for IT to drive business value.
Input: IT organization expertise and the CEO-CIO Alignment diagnostic
Output: An understanding of an executive business stakeholder’s perception of IT
Materials: M&A Sell Playbook, CEO-CIO Alignment diagnostic
Participants: IT executive/CIO, Business executive/CEO
Download the sample report.
Record the results in the M&A Sell Playbook.
2 weeks
Input: IT organization expertise, CIO BV diagnostic
Output: An understanding of business stakeholder perception of certain IT capabilities and services
Materials: M&A Buy Playbook, CIO Business Vision diagnostic
Participants: IT executive/CIO, Senior business leaders
Download the sample report.
Record the results in the M&A Sell Playbook.
Example:
Your stakeholder map defines the influence landscape that the M&A transaction will occur within. This will identify who holds various levels of accountability and decision-making authority when a transaction does take place.
Use connectors to determine who may be influencing your direct stakeholders. They may not have any formal authority within the organization, but they may have informal yet substantial relationships with your stakeholders.
1-3 hours
Input: List of M&A stakeholders
Output: Relationships among M&A stakeholders and influencers
Materials: Flip charts, Markers, Sticky notes, M&A Sell Playbook
Participants: IT executive leadership
Record the results in the M&A Sell Playbook.
There are four areas in the map, and the stakeholders within each area should be treated differently.
Players – players have a high interest in the initiative and the influence to effect change over the initiative. Their support is critical, and a lack of support can cause significant impediment to the objectives.
Mediators – mediators have a low interest but significant influence over the initiative. They can help to provide balance and objective opinions to issues that arise.
Noisemakers – noisemakers have low influence but high interest. They tend to be very vocal and engaged, either positively or negatively, but have little ability to enact their wishes.
Spectators – generally, spectators are apathetic and have little influence over or interest in the initiative.
30 minutes
Input: Stakeholder map, Stakeholder list
Output: Categorization of stakeholders and influencers
Materials: Flip charts, Markers, Sticky notes, M&A Sell Playbook
Participants: IT executive leadership, Stakeholders
How much are the stakeholder’s individual performance and goals directly tied to the success or failure of the product?
Record the results in the M&A Sell Playbook.
| Level of Support | |||||
Supporter |
Evangelist |
Neutral |
Blocker |
||
| Stakeholder Category | Player | Critical | High | High | Critical |
| Mediator | Medium | Low | Low | Medium | |
| Noisemaker | High | Medium | Medium | High | |
| Spectator | Low | Irrelevant | Irrelevant | Low |
Consider the three dimensions for stakeholder prioritization: influence, interest, and support. Support can be determined by answering the following question: How significant is that stakeholder to the M&A or divestiture process?
These parameters are used to prioritize which stakeholders are most important and should receive your focused attention.
30 minutes
Input: Stakeholder matrix
Output: Stakeholder and influencer prioritization
Materials: Flip charts, Markers, Sticky notes, M&A Sell Playbook
Participants: IT executive leadership, M&A/divestiture stakeholders
Stakeholder |
Category |
Level of Support |
Prioritization |
| CMO | Spectator | Neutral | Irrelevant |
| CIO | Player | Supporter | Critical |
Record the results in the M&A Sell Playbook.
Type |
Quadrant |
Actions |
| Players | High influence, high interest – actively engage | Keep them updated on the progress of the project. Continuously involve Players in the process and maintain their engagement and interest by demonstrating their value to its success. |
| Mediators | High influence, low interest – keep satisfied | They can be the game changers in groups of stakeholders. Turn them into supporters by gaining their confidence and trust and including them in important decision-making steps. In turn, they can help you influence other stakeholders. |
| Noisemakers | Low influence, high interest – keep informed | Try to increase their influence (or decrease it if they are detractors) by providing them with key information, supporting them in meetings, and using Mediators to help them. |
| Spectators | Low influence, low interest – monitor | They are followers. Keep them in the loop by providing clarity on objectives and status updates. |
Each group of stakeholders draws attention and resources away from critical tasks. By properly identifying stakeholder groups, the IT executive leader can develop corresponding actions to manage stakeholders in each group. This can dramatically reduce wasted effort trying to satisfy Spectators and Noisemakers while ensuring the needs of Mediators and Players are met.
30 minutes
Input: Stakeholder priority, Stakeholder categorization, Stakeholder influence
Output: Stakeholder communication plan
Materials: Flip charts, Markers, Sticky notes, M&A Sell Playbook
Participants: IT executive leadership, M&A/divestiture stakeholders
The purpose of this activity is to make a communication plan for each of the stakeholders identified in the previous activities, especially those who will have a critical role in the M&A transaction process.
Record the results in the M&A Sell Playbook.
Identify critical opportunities to optimize IT and meet strategic business goals through a merger, acquisition, or divestiture.
Four ways to create value through digital
1 day
Input: Valuation of data, Valuation of applications, Valuation of infrastructure and operations, Valuation of security and risk
Output: Valuation of IT
Materials: Relevant templates/tools listed on the following slides, Capital budget, Operating budget, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership
The purpose of this activity is to demonstrate that IT is not simply an operational functional area that diminishes business resources. Rather, IT contributes significant value to the business.
Consistency is key when valuating your IT organization as well as other IT organizations throughout the transaction process.
Record the results in the M&A Sell Playbook.
Data valuation identifies how you monetize the information that your organization owns.
When valuating the information and data that exists in an organization, there are many things to consider.
Info-Tech has two tools that can support this process:
Data Collection |
Insight Creation |
Value Creation |
Data Valuation |
| 01 Data Source
02 Data Collection Method 03 Data |
04 Data Analysis
05 Insight 06 Insight Delivery |
07 Consumer
08 Value in Data |
09 Value Dimension
10 Value Metrics Group 11 Value Metrics |
When valuating the applications and their users in an organization, consider using a business process map. This shows how business is transacted in the company by identifying which IT applications support these processes and which business groups have access to them. Info-Tech has a business process mapping tool that can support this process:
User Costs |
Total User Costs |
Derived Productivity Ratio (DPR) |
Total DPR |
Application Value |
|||
| # of users | % time spent using IT | Fully burdened salary | Multiply values from the 3 user costs columns | Revenue per employee | Average cost per employee | (Revenue P.E) ÷ (Average cost P.E) | (User costs) X (DPR) |
IT and Business Costs |
Total IT and Business Costs |
Net Value of Applications |
|||
| Application maintenance | Downtime costs (include disaster exposure) | Common costs allocated to applications | Fully loaded costs of active (FTE) users | Sum of values from the four IT and business costs columns | (Application value) – (IT and business costs) |
(Source: CSO)
The purpose of this exercise is to provide a high-level infrastructure valuation that will contribute to valuating your IT environment.
Calculating the value of the infrastructure will require different methods depending on the environment. For example, a fully cloud-hosted organization will have different costs than a fully on-premises IT environment.
Item |
Costs/Value |
| Hardware Assets Total Value | +$3.2 million |
| Hardware Leased/Service Agreement | -$ |
| Software Purchased | +$ |
| Software Leased/Service Agreement | -$ |
| Operational Tools | |
| Network | |
| Disaster Recovery | |
| Antivirus | |
| Data Centers | |
| Service Desk | |
| Other Licenses | |
| Total: |
For additional support, download the M&A Runbook for Infrastructure and Operations.
The purpose of this exercise is to provide a high-level risk assessment that will contribute to valuating your IT environment. For a more in-depth risk assessment, please refer to the Info-Tech tools below:
Probability of Risk Occurrence |
Occurrence Criteria
|
| Negligible | Very Unlikely; ‹20% |
| Very Low | Unlikely; 20 to 40% |
| Low | Possible; 40 to 60% |
| Moderately Low | Likely; 60 to 80% |
| Moderate | Almost Certain; ›80% |
Note: If needed, you can customize this scale with the severity designations that you prefer. However, make sure you are always consistent with it when conducting a risk assessment.
Financial & Reputational Impact |
Budgetary and Reputational Implications
|
| Negligible | (‹$10,000; Internal IT stakeholders aware of risk event occurrence) |
| Very Low | ($10,000 to $25,000; Business customers aware of risk event occurrence) |
| Low | ($25,000 to $50,000; Board of directors aware of risk event occurrence) |
| Moderately Low | ($50,000 to $100,000; External customers aware of risk event occurrence) |
| Moderate | (›$100,000; Media coverage or regulatory body aware of risk event occurrence) |
Risk Category Details |
Probability of Occurrence |
Estimated Financial Impact |
Estimated Severity (Probability X Impact) |
| Capacity Planning | |||
| Enterprise Architecture | |||
| Externally Originated Attack | |||
| Hardware Configuration Errors | |||
| Hardware Performance | |||
| Internally Originated Attack | |||
| IT Staffing | |||
| Project Scoping | |||
| Software Implementation Errors | |||
| Technology Evaluation and Selection | |||
| Physical Threats | |||
| Resource Threats | |||
| Personnel Threats | |||
| Technical Threats | |||
| Total: |
4 hours
Input: IT strategy, Digital strategy, Business strategy
Output: An understanding of an executive business stakeholder’s perception of IT, Alignment of IT/digital strategy and overall organization strategy
Materials: Computer, Whiteboard and markers, M&A Sell Playbook
Participants: IT executive/CIO, Business executive/CEO
The purpose of this activity is to review the business and IT strategies that exist to determine if there are critical capabilities that are not being supported.
Ideally, the IT and digital strategies would have been created following development of the business strategy. However, sometimes the business strategy does not directly call out the capabilities it requires IT to support.
For additional support, see Build a Business-Aligned IT Strategy.
Record the results in the M&A Sell Playbook.
Establish strong relationships with critical M&A stakeholders and position IT as an innovative business partner that can suggest reduction opportunities.
1-2 hours
Input: CEO-CIO Alignment diagnostic, CIO Business Vision diagnostic, Valuation of IT environment, IT-business goals cascade
Output: List of pain points or opportunities that IT can address
Materials: Computer, Whiteboard and markers, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Business stakeholders
The purpose of this activity is to determine the pain points and opportunities that exist for the organization. These can be external or internal to the organization.
Opportunities and pain points can be trends, other departments’ initiatives, business perspectives of IT, etc.
Record the results in the M&A Sell Playbook.
1-2 hours
Input: CEO-CIO Alignment diagnostic, CIO Business Vision diagnostic, Valuation of IT environment, IT-business goals cascade, List of pain points and opportunities
Output: An understanding of an executive business stakeholder’s perception of IT, Foundations for reduction strategy
Materials: Computer, Whiteboard and markers, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Business stakeholders
The purpose of this activity is to determine whether a growth or separation strategy might be a good suggestion to the business in order to meet its business objectives.
Record the results in the M&A Sell Playbook.
1-2 hours
Input: Growth or separation strategy opportunities to support business goals, Stakeholder communication plan, Rationale for the suggestion
Output: M&A transaction opportunities suggested
Materials: M&A Sell Playbook
Participants: IT executive/CIO, Business executive/CEO
The purpose of this activity is to recommend a merger, acquisition, or divestiture to the business.
With technology and digital driving many transactions, leverage your organizations’ IT environment as an asset and reason why the divestiture or sale should happen, suggesting the opportunity yourself.
Record the results in the M&A Sell Playbook.
Develop progressive relationships and strong communication with key stakeholders to suggest or be aware of transformational opportunities that can be achieved through sale or divestiture strategies.
| Phase 1 | Phase 2 | Phase 3 | Phase 4 |
|
|
|
|
Pre-Work | Day 1 | Day 2 | Day 3 | Day 4 | Day 5 | |
| Establish the Transaction Foundation | Discover the Motivation for Divesting or Selling | Formalize the Program Plan | Create the Valuation Framework | Strategize the Transaction | Next Steps and Wrap-Up (offsite) | |
Activities |
|
|
|
|
|
|
Deliverables |
|
|
|
|
|
|
The Discovery & Strategy phase during a sale or divestiture is a unique opportunity for many IT organizations. IT organizations that can participate in the transaction at this stage are likely considered a strategic partner of the business.
For one-off sales/divestitures, IT being invited during this stage of the process is rare. However, for organizations that are preparing to engage in many divestitures over the coming years, this type of strategy will greatly benefit from IT involvement. Again, the likelihood of participating in an M&A transaction is increasing, making it a smart IT leadership decision to, at the very least, loosely prepare a program plan that can act as a strategic pillar throughout the transaction.
During this phase of the pre-transaction state, IT may be asked to participate in ensuring that the IT environment is able to quickly and easily carve out components/business lines and deliver on service-level agreements (SLAs).
Goal: To identify a repeatable program plan that IT can leverage when selling or divesting all or parts of the current IT environment, ensuring customer satisfaction and business continuity
Before coming into the Discovery & Strategy phase, you should have addressed the following:
Establish an M&A program plan that can be repeated across sales/divestitures.
Vision Statements |
Mission Statements |
|
Characteristics |
|
|
Samples |
To be a trusted advisor and partner in enabling business innovation and growth through an engaged IT workforce. (Source: Business News Daily) | IT is a cohesive, proactive, and disciplined team that delivers innovative technology solutions while demonstrating a strong customer-oriented mindset. (Source: Forbes, 2013) |
2 hours
Input: Business objectives, IT capabilities, Rationale for the transaction
Output: IT’s mission and vision statements for reduction strategies tied to mergers, acquisitions, and divestitures
Materials: Flip charts/whiteboard, Markers, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to create mission and vision statements that reflect IT’s intent and method to support the organization as it pursues a reduction strategy.
Record the results in the M&A Sell Playbook.
IT guiding principles are shared, long-lasting beliefs that guide the use of IT in constructing, transforming, and operating the enterprise by informing and restricting IT investment portfolio management, solution development, and procurement decisions.
Info-Tech has identified a set of characteristics that IT principles should possess. These characteristics ensure the IT principles are relevant and followed in the organization.
Approach focused. IT principles should be focused on the approach – how the organization is built, transformed, and operated – as opposed to what needs to be built, which is defined by both functional and non-functional requirements.
Business relevant. Create IT principles that are specific to the organization. Tie IT principles to the organization’s priorities and strategic aspirations.
Long lasting. Build IT principles that will withstand the test of time.
Prescriptive. Inform and direct decision making with actionable IT principles. Avoid truisms, general statements, and observations.
Verifiable. If compliance can’t be verified, people are less likely to follow the principle.
Easily Digestible. IT principles must be clearly understood by everyone in IT and by business stakeholders. IT principles aren’t a secret manuscript of the IT team. IT principles should be succinct; wordy principles are hard to understand and remember.
Followed. Successful IT principles represent a collection of beliefs shared among enterprise stakeholders. IT principles must be continuously communicated to all stakeholders to achieve and maintain buy-in.
In organizations where formal policy enforcement works well, IT principles should be enforced through appropriate governance processes.
IT Principle Name |
IT Principle Statement |
| 1. Risk Management | We will ensure that the organization’s IT Risk Management Register is properly updated to reflect all potential risks and that a plan of action against those risks has been identified. |
| 2. Transparent Communication | We will ensure employees are spoken to with respect and transparency throughout the transaction process. |
| 3. Separation for Success | We will create a carve-out strategy that enables the organization and clearly communicates the resources required to succeed. |
| 4. Managed Data | We will handle data creation, modification, separation, and use across the enterprise in compliance with our data governance policy. |
| 5.Deliver Better Customer Service | We will reduce the number of products offered by IT, enabling a stronger focus on specific products or elements to increase customer service delivery. |
| 6. Compliance With Laws and Regulations | We will operate in compliance with all applicable laws and regulations for both our organization and the potentially purchasing organization. |
| 7. Defined Value | We will create a plan of action that aligns with the organization’s defined value expectations. |
| 8. Network Readiness | We will ensure that employees and customers have immediate access to the network with minimal or no outages. |
| 9. Value Generator | We will leverage the current IT people, processes, and technology to turn the IT organization into a value generator by developing and selling our services to purchasing organizations. |
2 hours
Input: Business objectives, IT capabilities, Rationale for the transaction, Mission and vision statements
Output: IT’s guiding principles for reduction strategies tied to mergers, acquisitions, and divestitures
Materials: Flip charts/whiteboard, Markers, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to create the guiding principles that will direct the IT organization throughout the reduction strategy process.
Record the results in the M&A Sell Playbook.
Consider the following capabilities when looking at who should be a part of the IT Transaction Team.
Employees who have a significant role in ensuring that these capabilities are being delivered will be a top priority.
An operating model is an abstract visualization, used like an architect’s blueprint, that depicts how structures and resources are aligned and integrated to deliver on the organization’s strategy.
It ensures consistency of all elements in the organizational structure through a clear and coherent blueprint before embarking on detailed organizational design.
The visual should highlight which capabilities are critical to attaining strategic goals and clearly show the flow of work so that key stakeholders can understand where inputs flow in and outputs flow out of the IT organization.
As you assess the current operating model, consider the following:
Info-Tech Insight
Investing time up-front getting the operating model right is critical. This will give you a framework to rationalize future organizational changes, allowing you to be more iterative and allowing your model to change as the business changes.
4 hours
Input: Current operating model, IT strategy, IT capabilities, M&A-specific IT capabilities, Business objectives, Rationale for the transaction, Mission and vision statements
Output: Future-state operating model for divesting organizations
Materials: Operating model, Capability overlay, Flip charts/whiteboard, Markers, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to establish what the future-state operating model will be if your organization needs to adjust to support a divestiture transaction. If your organization plans to sell in its entirety, you may choose to skip this activity.
An example operating model is included in the M&A Sell Playbook. This process benefits from strong reference architecture and capability mapping ahead of time.
Record the results in the M&A Sell Playbook.
Input: IT capabilities, Future-state operating model, M&A-specific IT capabilities, Business objectives, Rationale for the transaction, Mission and vision statements
Output: Transition team
Materials: Reference architecture, Organizational structure, Flip charts/whiteboard, Markers
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to create a team that will support your IT organization throughout the transaction. Determining which capabilities and therefore which roles will be required ensures that the business will continue to get the operational support it needs.
For more information, see Redesign Your Organizational Structure
1-2 hours
Input: List of governing bodies, Governing body committee profiles, Governance structure
Output: Documented method on how decisions are made as it relates to the M&A transaction
Materials: Flip charts/whiteboard, Markers, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to determine the method in which decisions are made throughout the M&A transaction as it relates to IT. This will require understanding both governing bodies internal to IT and those external to IT.
Record the results in the M&A Sell Playbook.
Strategy: These groups will focus on decisions that directly connect to the strategic direction of the organization.
Design & Build: The second tier of groups will oversee prioritization of a certain area of governance as well as design and build decisions that feed into strategic decisions.
Run: The lowest level of governance will be oversight of more-specific initiatives and capabilities within IT.
Expect tier overlap. Some committees will operate in areas that cover two or three of these governance tiers.
Upper management will measure IT’s success based on your ability to support the underlying reasons for the M&A. Using business metrics will help assure business stakeholders that IT understands their needs and is working with the business to achieve them.
| S pecific | Make sure the objective is clear and detailed. |
| M easurable | Objectives are measurable if there are specific metrics assigned to measure success. Metrics should be objective. |
| A ctionable | Objectives become actionable when specific initiatives designed to achieve the objective are identified. |
| R ealistic | Objectives must be achievable given your current resources or known available resources. |
| T ime-Bound | An objective without a timeline can be put off indefinitely. Furthermore, measuring success is challenging without a timeline. |
1. Proactive | 2. Discovery & Strategy | 3. Valuation & Due Diligence | 4. Execution & Value Realization |
|
|
|
|
1-2 hours
Input: IT capabilities, Mission, vision, and guiding principles, Rationale for the acquisition
Output: Program metrics to support IT throughout the M&A process
Materials: Flip charts/whiteboard, Markers, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to determine how IT’s success throughout a growth transaction will be measured and determined.
Record the results in the M&A Sell Playbook.
Identify IT’s plan of action when it comes to the separation/sale and align IT’s separation/sale strategy with the business’ M&A strategy.
The approach IT takes will depend on the business objectives for the M&A.
Key considerations when choosing an IT separation strategy include:
1-2 hours
Input: Business separation strategy, Guiding principles, M&A governance
Output: IT’s separation strategy
Materials: Flip charts/whiteboard, Markers, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to determine IT’s approach to separating or selling. This approach might differ slightly from transaction to transaction. However, the businesses approach to transactions should give insight into the general separation strategy IT should adopt.
Record the results in the M&A Sell Playbook.
Business M&A Strategy |
Resultant Technology Strategy |
M&A Magnitude (% of Seller Assets, Income, or Market Value) |
IT Separation Posture |
| A. Horizontal | Adopt One Model | ‹100% | Divest |
| ›99% | Sell | ||
| B. Vertical | Create Links Between Critical Systems | Any | Divest |
| C. Conglomerate | Independent Model | Any | Joint Venture Divest |
| D. Hybrid: Horizontal & Conglomerate | Create Links Between Critical Systems | Any | Divest Joint Venture |
| Business M&A Strategy | Resultant Technology Strategy | M&A Magnitude (% of Seller Assets, Income, or Market Value) | IT Separation Posture |
M&A objectives may not affect all IT domains and business functions in the same way. Therefore, the separation requirements for each business function may differ. Organizations will often choose to select and implement a hybrid separation posture to realize the technology end state.
Each business division may have specific IT domain and capability needs that require an alternative separation strategy.
1-2 hours
Input: IT capabilities, Transition team, Separation strategy
Output: Completed RACI for Transition team
Materials: Reference architecture, Organizational structure, Flip charts/whiteboard, Markers, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to identify the core accountabilities and responsibilities for the roles identified as critical to your transition team. While there might be slight variation from transaction to transaction, ideally each role should be performing certain tasks.
Record the results in the M&A Sell Playbook.
Three key dimensions determine the appetite for cultural change:
1-2 hours
Input: IT’s M&A mission, vision, and guiding principles, M&A transition team, IT separation strategy, RACI
Output: IT’s M&A communication plan
Materials: Flip charts/whiteboard, Markers, RACI, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to create a communication plan that IT can leverage throughout the initiative.
Record the results in the M&A Sell Playbook.
As soon as you have identified organizations to consider, it’s imperative to assess critical risks. Most IT leaders can attest that they will receive little to no notice when the business is pursuing a sale and IT has to assess the IT organization. As a result, having a standardized template to quickly assess the potential acquiring organization is important.
Assessing potential organizations is not just for the purchaser. The seller should also know what the purchasing organization’s history with M&As is and what potential risks could occur if remaining connected through ongoing SLAs.
Input: Publicized historical risk events, Solutions and vendor contracts likely in the works, Trends
Output: IT’s valuation of the potential organization(s) for selling or divesting
Materials: M&A Sell Playbook
Participants: IT executive/CIO
The purpose of this activity is to assess the organization(s) that your organization is considering selling or divesting to.
Record the results in the M&A Sell Playbook.
| Phase 1 | Phase 2 | Phase 3 | Phase 4 |
|
|
|
|
Pre-Work | Day 1 | Day 2 | Day 3 | Day 4 | Day 5 | |
| Establish the Transaction Foundation | Discover the Motivation for Separation | Identify Expectations and Create the Carve-Out Roadmap | Prepare and Manage Employees | Plan the Separation Roadmap | Next Steps and Wrap-Up (offsite) | |
Activities |
|
|
|
|
|
|
Deliverables |
|
|
|
|
|
|
The Due Diligence & Preparation phase during a sale or divestiture is a critical time for IT. If IT fails to proactively participate in this phase, IT will have to merely react to separation expectations set by the business.
If your organization is being sold in its entirety, staff will have major concerns about their future in the new organization. Making this transition as smooth as possible and being transparent could go a long way in ensuring their success in the new organization.
In a divestiture, this is the time to determine where it’s possible for the organization to divide or separate from itself. A lack of IT involvement in these conversations could lead to an overcommitment by the business and under-delivery by IT.
Goal: To ensure that, as the selling or divesting organization, you comply with regulations, prepare staff for potential changes, and identify a separation strategy if necessary
Before coming into the Due Diligence & Preparation phase, you must have addressed the following:
Before coming into the Due Diligence & Preparation phase, we recommend addressing the following:
All three elements of the Technology Value Trinity work in harmony to deliver business value and achieve strategic needs. As one changes, the others need to change as well.
Too often strategy, operating model and organizational design, and governance are considered separate practices. As a result, “strategic documents” end up being wish lists, and projects continue to be prioritized based on who shouts the loudest – not based on what is in the best interest of the organization.
This step of the process is when IT should prepare and support the business in due diligence and gather the necessary information about staff changes.
1-2 hours
Input: Key roles for the transaction team, M&A governance, Target metrics, Selected separation strategy framework, RACI of key transaction tasks for the transaction team
Output: IT Due Diligence Charter
Materials: M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to create a charter leveraging the items completed in the previous phase, as listed on the Due Diligence Prerequisite Checklist slide, to gain executive sign-off.
Record the results in the M&A Sell Playbook.
4 hours
Input: Future-state operating model, M&A governance, Target metrics, Selected separation strategy framework, RACI of key transaction tasks for the transaction team
Output: List of items to acquire and verify can be provided to the purchasing organization while in the data room
Materials: Critical domain lists on following slides, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team, Transition team, Legal team, Compliance/privacy officers
The purpose of this activity is to create a list of the key artifacts that you could be asked for during the due diligence process.
**Note that if your organization is not leading/initiating the data room, then you can ignore this activity.
Record the results in the M&A Sell Playbook.
Domain |
Stakeholders |
Key Artifacts |
Key Information to request |
| Business |
|
|
|
| Leadership/IT Executive |
|
|
|
| Data & Analytics |
|
|
|
| Applications |
|
|
|
| Infrastructure |
|
|
|
| Products and Services |
|
|
|
Domain | Stakeholders | Key Artifacts | Key Information to request |
| Operations |
|
|
|
| IT Processes |
|
|
|
| IT People |
|
|
|
| Security |
|
|
|
| Projects |
|
|
|
| Vendors |
|
|
|
3-4 hours
Input: Engagement survey
Output: Baseline engagement scores
Materials: Build an IT Employee Engagement Program
Participants: IT executive/CIO, IT senior leadership, IT employees of current organization
The purpose of this activity is to measure current staff engagement to have a baseline to measure against in the future state. This is a good activity to complete if you will be divesting or selling in entirety.
The results from the survey should act as a baseline to determine what the organization is doing well in terms of employee engagement and what drivers could be improved upon.
Record the results in the M&A Sell Playbook.
Target Organization's Culture. The culture that the target organization is currently embracing. Their established and undefined governance practices will lend insight into this.
Your Organization’s Culture. The culture that your organization is currently embracing. Examine people’s attitudes and behaviors within IT toward their jobs and the organization.
Ideal Culture. What will the future culture of the IT organization be once separation is complete? Are there aspects that your current organization and the target organization embrace that are worth considering?
Competitive
|
Innovative
|
Traditional
|
Cooperative
|
3-4 hours
Input: Cultural assessments for current IT organization, Cultural assessment for target IT organization
Output: Goal for IT culture
Materials: IT Culture Diagnostic
Participants: IT executive/CIO, IT senior leadership, IT employees of current organization, IT employees of target organization, Company M&A team
The purpose of this activity is to assess the different cultures that might exist within the IT environments of the organizations involved. By understanding the culture that exists in the purchasing organization, you can identify the fit and prepare impacted staff for potential changes.
Record the results in the M&A Sell Playbook.
Have an established plan of action toward separation across all domains and a strategy toward resources.
Testing the carve capabilities of the IT organization often takes 3 months. (Source: Cognizant, 2014)
Daimler-Benz lost nearly $19 billion following its purchase of Chrysler by failing to recognize the cultural differences that existed between the two car companies. (Source: Deal Room)
Separating the IT organization requires more time and effort than business leaders will know. Frequently communicate challenges and lost opportunities when carving the IT environment out.
Set up a meeting with your IT due diligence team to:
Use this opportunity to:
The approach IT takes will depend on the business objectives for the M&A.
Key considerations when choosing an IT separation strategy include:
6 hours
Input: Items included in the carve-out, Dependencies, Whether testing is completed, If the carve-out will pass audit, If the carve-out item is prepared to be separated
Output: Carve-out roadmap
Materials: Business’ divestiture plan, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Business leaders, Transition team
The purpose of this activity is to prepare the IT environment by identifying a carve-out roadmap, specifically looking at data, infrastructure, and applications. Feel free to expand the roadmap to include other categories as your organization sees fit.
Record the results in the M&A Sell Playbook.
2 hours
Input: Separation tasks, Transition team, M&A RACI
Output: Prioritized separation list
Materials: Separation task checklist, Separation roadmap
Participants: IT executive/CIO, IT senior leadership, Company M&A team
The purpose of this activity is to prioritize the different separation tasks that your organization has identified as necessary to this transaction. Some tasks might not be relevant for this particular transaction, and others might be critical.
Record the updates in the M&A Separation Project Management Tool (SharePoint).
Record the updates in the M&A Separation Project Management Tool (Excel).
Input: Prioritized separation tasks, Carve-out roadmap, Employee transition plan, Separation RACI, Costs for activities, Activity owners
Output: Separation roadmap
Materials: M&A Separation Project Plan Tool (SharePoint), M&A Separation Project Plan Tool (Excel), SharePoint Template: Step-by-Step Deployment Guide
Participants: IT executive/CIO, IT senior leadership, Transition team, Company M&A team
The purpose of this activity is to create a roadmap to support IT throughout the separation process. Using the information gathered in previous activities, you can create a roadmap that will ensure a smooth separation.
Record the updates in the M&A Separation Project Management Tool (SharePoint).
Record the updates in the M&A Separation Project Management Tool (Excel).
For more information, check out the SharePoint Template: Step-by-Step Deployment Guide.
Input: Carve-out roadmap, Separation roadmap, Up-to-date version of the agreement
Output: Buyer’s IT expectations
Materials: Questions for meeting
Participants: IT executive/CIO, IT senior leadership, Company M&A team, Purchasing company M&A team, Purchasing company IT leadership
The purpose of this activity is to determine if the buyer has specific service expectations for your IT organization. By identifying, documenting, and agreeing on what services your IT organization will be responsible for, you can obtain a final agreement to protect you as the selling organization.
6 hours
Input: Buyer's expectations, Separation roadmap
Output: SLA for the purchasing organization
Materials: Service Catalog Internal Service Level Agreement Template, M&A Separation Project Plan Tool (SharePoint), M&A Separation Project Plan Tool (Excel)
Participants: IT executive/CIO, IT senior leadership, Company M&A team, Purchasing company M&A team, Purchasing company IT leadership
The purpose of this activity is to determine if the buyer has specific service expectations for your IT organization post-transaction that your IT organization is agreeing to provide.
*For organizations being purchased in their entirety, this activity may not be relevant.
Modify the Service Catalog Internal Service Level Agreement with the agreed-upon terms of the SLA.
Separation costs are more related to the degree of change required than the size of the transaction.
3-4 hours
Input: Separation tasks, Transition team, Valuation of current IT environment, Valuation of target IT environment, Outputs from data room, Technical debt, Employees
Output: List of anticipated costs required to support IT separation
Materials: Separation task checklist, Separation roadmap, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company M&A team, Transition team
The purpose of this activity is to estimate the costs that will be associated with the separation. Identify and communicate a realistic figure to the larger M&A team within your company as early in the process as possible. This ensures that the funding required for the transaction is secured and budgeted for in the overarching transaction.
Record the results in the M&A Sell Playbook.
Being transparent throughout the process is critical. Do not hesitate to tell employees the likelihood that their job may be made redundant. This will ensure a high level of trust and credibility for those who remain with the organization after the transaction.
3-4 hours
Input: IT strategy, IT organizational design
Output: Employee transition plans
Materials: M&A Sell Playbook, Whiteboard, Sticky notes, Markers
Participants: IT executive/CIO, IT senior leadership, Company M&A team, Transition team
The purpose of this activity is to create a transition plan for employees.
**Note that if someone’s future role is a layoff, then there is no need to record anything for skills needed or method for skill development.
Record the results in the M&A Sell Playbook.
3-4 hours
Input: Prioritized separation tasks, Employee transition plan, Separation RACI, Costs for activities, Activity owners
Output: Employee functional workplans
Materials: M&A Sell Playbook, Learning and development tools
Participants: IT executive/CIO, IT senior leadership, IT management team, Company M&A team, Transition team
The purpose of this activity is to create a functional workplan for the different employees so that they know what their key role and responsibilities are once the transaction occurs.
It is recommended that each employee have a functional workplan. Leverage the IT managers to support this task.
Record the results in the M&A Sell Playbook.
3-4 hours
Input: Prioritized separation tasks, Employee transition plan, Separation RACI, Costs for activities, Activity owners, M&A goals
Output: Separation-specific metrics to measure success
Materials: Separation roadmap, M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Transition team
The purpose of this activity is to understand how to measure the success of the separation project by aligning metrics to each identified task.
Record the results in the M&A Sell Playbook.
| Phase 1 | Phase 2 | Phase 3 | Phase 4 |
|
|
|
|
Pre-Work | Day 1 | Day 2 | Day 3 | Engage in Separation | Day 4 | |
| Establish the Transaction Foundation | Discover the Motivation for Integration | Plan the Separation Roadmap | Prepare Employees for the Transition | Engage in Separation | Assess the Transaction Outcomes (Must be within 30 days of transaction date) | |
Activities |
|
|
|
|
|
|
Deliverables |
|
|
|
|
|
|
Once the transaction comes to a close, it’s time for IT to deliver on the critical separation tasks. As the selling organization in this transaction, you need to ensure you have a roadmap that properly enables the ongoing delivery of your IT environment while simultaneously delivering the necessary services to the purchasing organization.
Throughout the separation transaction, some of the most common obstacles IT should prepare for include difficulty separating the IT environment, loss of key personnel, disengaged employees, and security/compliance issues.
Post-transaction, the business needs to understands the value they received by engaging in the transaction and the ongoing revenue they might obtain as a result of the sale. You also need to ensure that the IT environment is functioning and mitigating any high-risk outcomes.
Goal: To carry out the planned separation activities and deliver the intended value to the business.
Before coming into the Execution & Value Realization phase, you must have addressed the following:
Before coming into the Execution & Value Realization phase, we recommend addressing the following:
Successfully execute the separation of the IT environments and update the project plan, strategizing against any roadblocks as they come.
If you are entering the transaction at this point, consider and monitor the following three items above all else.
Your IT environment, reputation as an IT leader, and impact on key staff will depend on monitoring these aspects.
For more information, review:
Input: Original service agreement, Risk register
Output: Service agreement confirmed
Materials: Original service agreement
Participants: IT executive/CIO, IT senior leadership, External organization IT senior leadership
The purpose of this activity is to monitor the established service agreements on an ongoing basis. Your organization is most at risk during the initial months following the transaction.
For additional information and support for this activity, see the blueprint Build an IT Risk Management Program.
Input: Prioritized separation tasks, Separation RACI, Activity owners
Output: Updated separation project plan
Materials: M&A Separation Project Plan Tool (SharePoint), M&A Separation Project Plan Tool (Excel)
Participants: IT executive/CIO, IT senior leadership, IT transaction team, Company M&A team
The purpose of this activity is to ensure that the project plan is continuously updated as your transaction team continues to execute on the various components outlined in the project plan.
Record the updates in the M&A Separation Project Management Tool (SharePoint).
Record the updates in the M&A Separation Project Management Tool (Excel).
Review the value that IT was able to generate around the transaction and strategize about how to improve future selling or separating transactions.
3-4 hours
Input: Separation tasks, Carve-out roadmap, Transition team, Previous RACI, Estimated separation costs
Output: Actual separation costs
Materials: M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Transaction team, Company M&A team
The purpose of this activity is to confirm the associated costs around separation. While the separation costs would have been estimated previously, it’s important to confirm the costs that were associated with the separation in order to provide an accurate and up-to-date report to the company’s M&A team.
Record the results in the M&A Sell Playbook.
Throughout the transaction, the business would have communicated its goals, rationales, and expectations for the transaction. Sometimes this is done explicitly, and other times the information is implicit. Either way, IT needs to ensure that metrics have been defined and are measuring the intended value that the business expects. Ensure that the benefits realized to the organization are being communicated regularly and frequently.
3-4 hours
Input: Prioritized separation tasks, Separation RACI, Activity owners, M&A company goals
Output: Transaction value
Materials: M&A Sell Playbook
Participants: IT executive/CIO, IT senior leadership, Company's M&A team
The purpose of this activity is to track how your IT organization performed against the originally identified metrics.
Record the results in the M&A Sell Playbook.
2 hours
Input: Separation costs, Retention rates, Value that IT contributed to the transaction
Output: Strengths, weaknesses, opportunities, and threats
Materials: Flip charts, Markers, Sticky notes
Participants: IT executive/CIO, IT senior leadership, Business transaction team
The purpose of this activity is to assess the positive and negative elements of the transaction.
Record the results in the M&A Sell Playbook.
4 hours
Input: Transaction and separation SWOT
Output: Refined M&A playbook
Materials: M&A Sell Playbook
Participants: IT executive/CIO
The purpose of this activity is to revise the playbook and ensure it is ready to go for future transactions.
Record the results in the M&A Sell Playbook.
Congratulations, you have completed the M&A Sell Blueprint!
Rather than reacting to a transaction, you have been proactive in tackling this initiative. You now have a process to fall back on in which you can be an innovative IT leader by suggesting how and why the business should engage in a separation or sale transaction. You have:
Now that you have done all of this, reflect on what went well and what can be improved if you were to engage in a similar divestiture or sale again.
| Ibrahim Abdel-Kader
Research Analyst | CIO Info-Tech Research Group |
Brittany Lutes
Senior Research Analyst | CIO Info-Tech Research Group |
|
| John Annand
Principal Research Director | Infrastructure Info-Tech Research Group |
Scott Bickley
Principal Research Director | Vendor Management Info-Tech Research Group |
|
| Cole Cioran
Practice Lead | Applications Info-Tech Research Group |
Dana Daher
Research Analyst | Strategy & Innovation Info-Tech Research Group |
|
| Eric Dolinar
Manager | M&A Consulting Deloitte Canada |
Christoph Egel
Director, Solution Design & Deliver Cooper Tire & Rubber Company |
|
| Nora Fisher
Vice President | Executive Services Advisory Info-Tech Research Group |
Larry Fretz
Vice President | Industry Info-Tech Research Group |
| David Glazer
Vice President of Analytics Kroll |
Jack Hakimian
Senior Vice President | Workshops and Delivery Info-Tech Research Group |
|
| Gord Harrison
Senior Vice President | Research & Advisory Info-Tech Research Group |
Valence Howden
Principal Research Director | CIO Info-Tech Research Group |
|
| Jennifer Jones
Research Director | Industry Info-Tech Research Group |
Nancy McCuaig
Senior Vice President | Chief Technology and Data Office IGM Financial Inc. |
|
| Carlene McCubbin
Practice Lead | CIO Info-Tech Research Group |
Kenneth McGee
Research Fellow | Strategy & Innovation Info-Tech Research Group |
|
| Nayma Naser
Associate Deloitte |
Andy Neill
Practice Lead | Data & Analytics, Enterprise Architecture Info-Tech Research Group |
| Rick Pittman
Vice President | Research Info-Tech Research Group |
Rocco Rao
Research Director | Industry Info-Tech Research Group |
|
| Mark Rosa
Senior Vice President & Chief Information Officer Mohegan Gaming and Entertainment |
Tracy-Lynn Reid
Research Lead | People & Leadership Info-Tech Research Group |
|
| Jim Robson
Senior Vice President | Shared Enterprise Services (retired) Great-West Life |
Steven Schmidt
Senior Managing Partner Advisory | Executive Services Info-Tech Research Group |
|
| Nikki Seventikidis
Senior Manager | Finance Initiative & Continuous Improvement CST Consultants Inc. |
Allison Straker
Research Director | CIO Info-Tech Research Group |
|
| Justin Waelz
Senior Network & Systems Administrator Info-Tech Research Group |
Sallie Wright
Executive Counselor Info-Tech Research Group |
“5 Ways for CIOs to Accelerate Value During Mergers and Acquisitions.” Okta, n.d. Web.
Altintepe, Hakan. “Mergers and acquisitions speed up digital transformation.” CIO.com, 27 July 2018. Web.
“America’s elite law firms are booming.” The Economist, 15 July 2021. Web.
Barbaglia, Pamela, and Joshua Franklin. “Global M&A sets Q1 record as dealmakers shape post-COVID world.” Nasdaq, 1 April 2021. Web.
Boyce, Paul. “Mergers and Acquisitions Definition: Types, Advantages, and Disadvantages.” BoyceWire, 8 Oct. 2020. Web.
Bradt, George. “83% Of Mergers Fail -- Leverage A 100-Day Action Plan For Success Instead.” Forbes, 27 Jan. 2015. Web.
Capgemini. “Mergers and Acquisitions: Get CIOs, IT Leaders Involved Early.” Channel e2e, 19 June 2020. Web.
Chandra, Sumit, et al. “Make Or Break: The Critical Role Of IT In Post-Merger Integration.” IMAA Institute, 2016. Web.
Deloitte. “How to Calculate Technical Debt.” The Wall Street Journal, 21 Jan. 2015. Web.
Ernst & Young. “IT As A Driver Of M&A Success.” IMAA Institute, 2017. Web.
Fernandes, Nuno. “M&As In 2021: How To Improve The Odds Of A Successful Deal.” Forbes, 23 March 2021. Web.
“Five steps to a better 'technology fit' in mergers and acquisitions.” BCS, 7 Nov. 2019. Web.
Fricke, Pierre. “The Biggest Opportunity You’re Missing During an M&Aamp; IT Integration.” Rackspace, 4 Nov. 2020. Web.
Garrison, David W. “Most Mergers Fail Because People Aren't Boxes.” Forbes, 24 June 2019. Web.
Harroch, Richard. “What You Need To Know About Mergers & Acquisitions: 12 Key Considerations When Selling Your Company.” Forbes, 27 Aug. 2018. Web.
Hope, Michele. “M&A Integration: New Ways To Contain The IT Cost Of Mergers, Acquisitions And Migrations.” Iron Mountain, n.d. Web.
“How Agile Project Management Principles Can Modernize M&A.” Business.com, 13 April 2020. Web.
Hull, Patrick. “Answer 4 Questions to Get a Great Mission Statement.” Forbes, 10 Jan. 2013. Web.
Kanter, Rosabeth Moss. “What We Can Learn About Unity from Hostile Takeovers.” Harvard Business Review, 12 Nov. 2020. Web.
Koller, Tim, et al. “Valuation: Measuring and Managing the Value of Companies, 7th edition.” McKinsey & Company, 2020. Web.
Labate, John. “M&A Alternatives Take Center Stage: Survey.” The Wall Street Journal, 30 Oct. 2020. Web.
Lerner, Maya Ber. “How to Calculate ROI on Infrastructure Automation.” DevOps.com, 1 July 2020. Web.
Loten, Angus. “Companies Without a Tech Plan in M&A Deals Face Higher IT Costs.” The Wall Street Journal, 18 June 2019. Web.
Low, Jia Jen. “Tackling the tech integration challenge of mergers today” Tech HQ, 6 Jan. 2020. Web.
Lucas, Suzanne. “5 Reasons Turnover Should Scare You.” Inc. 22 March 2013. Web.
“M&A Trends Survey: The future of M&A. Deal trends in a changing world.” Deloitte, Oct. 2020. Web.
Maheshwari, Adi, and Manish Dabas. “Six strategies tech companies are using for successful divesting.” EY, 1 Aug. 2020. Web.
Majaski, Christina. “Mergers and Acquisitions: What's the Difference?” Investopedia, 30 Apr. 2021.
“Mergers & Acquisitions: Top 5 Technology Considerations.” Teksetra, 21 Jul. 2020. Web.
“Mergers Acquisitions M&A Process.” Corporate Finance Institute, n.d. Web.
“Mergers and acquisitions: A means to gain technology and expertise.” DLA Piper, 2020. Web.
Nash, Kim S. “CIOs Take Larger Role in Pre-IPO Prep Work.” The Wall Street Journal, 5 March 2015. Web.
O'Connell, Sean, et al. “Divestitures: How to Invest for Success.” McKinsey, 1 Aug. 2015. Web
Paszti, Laila. “Canada: Emerging Trends In Information Technology (IT) Mergers And Acquisitions.” Mondaq, 24 Oct. 2019. Web.
Patel, Kiison. “The 8 Biggest M&A Failures of All Time” Deal Room, 9 Sept. 2021. Web.
Peek, Sean, and Paula Fernandes. “What Is a Vision Statement?” Business News Daily, 7 May 2020. Web.
Ravid, Barak. “How divestments can re-energize the technology growth story.” EY, 14 July 2021. Web.
Ravid, Barak. “Tech execs focus on growth amid increasingly competitive M&A market.” EY, 28 April 2021. Web.
Resch, Scott. “5 Questions with a Mergers & Acquisitions Expert.” CIO, 25 June 2019. Web.
Salsberg, Brian. “Four tips for estimating one-time M&A integration costs.” EY, 17 Oct. 2019. Web.
Samuels, Mark. “Mergers and acquisitions: Five ways tech can smooth the way.” ZDNet, 15 Aug. 2018. Web.
“SAP Divestiture Projects: Options, Approach and Challenges.” Cognizant, May, 2014. Web.
Steeves, Dave. “7 Rules for Surviving a Merger & Acquisition Technology Integration.” Steeves and Associates, 5 Feb. 2020. Web.
Tanaszi, Margaret. “Calculating IT Value in Business Terms.” CSO, 27 May 2004. Web.
“The CIO Playbook. Nine Steps CIOs Must Take For Successful Divestitures.” SNP, 2016. Web.
“The Role of IT in Supporting Mergers and Acquisitions.” Cognizant, Feb. 2015. Web.
Torres, Roberto. “M&A playbook: How to prepare for the cost, staff and tech hurdles.” CIO Dive, 14 Nov. 2019. Web.
“Valuation Methods.” Corporate Finance Institute, n.d. Web.
Weller, Joe. “The Ultimate Guide to the M&A Process for Buyers and Sellers.” Smartsheet, 16 May 2019. Web.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Make the case for a web experience management suite and structure the WEM strategy project.
Identify the target state WEM strategy, assess current state, and identify gaps.
Build the WEM technology stack and create a web strategy initiatives 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.
Discuss the general project overview for the WEM selection.
Launch of your WEM selection project.
Development of your organization’s WEM requirements.
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.
WEM Procurement Project Charter
WEM Use-Case Fit Assessment
Plan the procurement and the implementation of the WEM solution.
Selection of a WEM solution.
A plan for implementing the selected WEM solution.
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.
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
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Gain insight on the various factors that influence software satisfaction.
Reduce the size of your RFPs or skip them entirely to limit time spent watching vendor dog and pony shows.
Narrow the field to four contenders prior to in-depth comparison and engage in accelerated enterprise architecture oversight.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Standardize your product quality definition and your QA roles, processes, and guidelines according to your business and IT priorities.
Build a solid set of good practices to define your defect tolerances, recognize the appropriate test coverage, and communicate your test results.
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.
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.
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.
1.1 List your QA objectives and metrics.
1.2 Adopt your foundational QA process.
Quality definition and QA objectives and metrics.
QA guiding principles, process, and roles and responsibilities.
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.
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.
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.
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.
You may be experiencing one or more of the following:
To have a successful information security strategy, take these three factors into account:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Read up on why you should build your customized information security strategy. Review our methodology and understand the four ways we can support you.
It all starts with risk appetite, yes, but security is something you want to get right. Determine your organizations' security pressures and business goals, and then determine your security program's goals.
Our best-of-breed security framework makes you perform a gap analysis between where you are and where you want to be (your target state). Once you know that, you can define your goals and duties.
With your design at this level, it is time to plan your roadmap.
Learn to use our methodology to manage security initiatives as you go. Identify the resources you need to execute the evolving strategy successfully.
Continuous assessment and optimization of your Workday enterprise resource planning (ERP) is critical to the success of your organization.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Enterprise resource planning (ERP) is a core tool that the business leverages to accomplish its goals. Take a proactive approach to optimize your enterprise applications. Strategically re-align business goals, identify business application capabilities, complete a process assessment, evaluate user satisfaction, measure module satisfaction, and vendor relations to create an optimization plan that will drive a cohesive technology strategy that delivers results.
The Get the Most out of Workday Workbook serves as the holding document for the different elements of the Get the Most out Workday blueprint. Use each assigned tab to input the relevant information for the process of optimizing Workday.
Use this tool provide Info-Tech with information surrounding your ERP application(s). This inventory will be used to create a custom Application Portfolio Assessment (APA) for your ERP. The template includes demographics, application inventory, departments to be surveyed and data quality inclusion.
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.
Define your workday application vision.
Set the foundation for optimizing Workday by building a cross-functional team, aligning with organizational strategy, inventorying current system state, defining your timeframe, and exploring current costs.
1.1 Identify stakeholders and build your optimization team.
1.2 Build an ERP strategy model.
1.3 Inventory current system state.
1.4 Define optimization timeframe.
1.5 Understand Workday costs.
Workday optimization team
Workday business model
Workday optimization goals
System inventory and data flow
Application and business capabilities list
Workday optimization timeline
Map current-state capabilities.
Measure the state of your current Workday system to understand where it is not performing well.
2.1 Assess Workday capabilities.
2.2 Review your satisfaction with the vendor/product and willingness for change.
Workday capability gap analysis
Workday user satisfaction (application portfolio assessment)
Workday SoftwareReviews survey results
Workday current costs
Assess Workday.
Explore underperforming areas to:
Uncover where user satisfaction is lacking and possible root causes.
Identify process and workflows that are creating issues for end users and identify improvement options.
Understand where data issues are occurring and explore how you can improve these.
Identify integration points and explore if there are any areas of improvement.
Investigate your relationship with the vendor and product, including that relative to others.
Identify any areas for cost optimization (optional).
3.1 Prioritize optimization opportunities.
3.2 Discover optimization initiatives.
Product and vendor satisfaction opportunities
Capability and feature optimization opportunities
Process optimization opportunities
Integration optimization opportunities
Data optimization opportunities
Workday cost-saving opportunities
Build the optimization roadmap.
Understanding where you need to improve is the first step, now understand where to focus your optimization efforts, build out next steps and put a timeframe in place.
4.1 Build your optimization roadmap.
Workday optimization roadmap
HR, finance, and planning systems are the core foundation of enterprise resource systems (ERP) systems. These are core tools 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.
Workday is expensive, benefits can be difficult to quantify, and optimization can be difficult to navigate. Over time, technology evolves, organizational goals change, and the health of these systems is often 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 health of their systems. We can do better than this.
IT leaders need to take a proactive approach to continually monitor and optimize their enterprise applications. Strategically realign business goals, identify business application capabilities, complete a process assessment, evaluate user satisfaction, measure module satisfaction, and improve vendor relations to create an optimization plan that will drive a cohesive technology strategy that delivers results.
Lisa Highfield
Research Director, Enterprise Applications
Info-Tech Research Group
Your Workday systems are critical to supporting the organization’s business processes. They are expensive. Direct benefits and ROI can be hard to measure.
Workday application portfolios are often behemoths to support. With complex integration points and unique business processes, stabilization is the norm.
Application optimization is essential to staying competitive and productive in today’s digital environment.
Balancing optimization with stabilization is one of the most difficult decisions for Workday application leaders.
Competing priorities and often unclear enterprise application strategies make it difficult to make decisions about what, how, and when to optimize.
Enterprise applications involve large numbers of processes, users, and evolving vendor roadmaps.
Teams do not have a framework to illustrate, communicate, and justify the optimization effort in the language your stakeholders understand.
In today’s changing world, it is imperative to evaluate your applications for optimization and to look for opportunities to capitalize on rapidly expanding technologies, integrated data, and employee solutions that meet the needs of your organization.
Assess your Workday applications and the environment in which they exist. Take a business-first strategy to prioritize optimization efforts.
Validate capabilities, user satisfaction, and issues around data, vendor management, and costs to build out an overall roadmap and optimization strategy.
Pull this all together to prioritize optimization efforts and develop a concrete roadmap.
Info-Tech Insight
Workday is investing heavily in expanding and deepening its finance and expanded product offerings, but we cannot stand still on our optimization efforts. Understand your product(s), processes, user satisfaction, integration points, and the availability of data to business decision makers. Examine these areas to develop a personalized Workday optimization roadmap that fits the needs of your organization. Incorporate these methodologies into an ongoing optimization strategy aimed at enabling the business, increasing productivity, and reducing costs.

Workday enterprise resource planning (ERP) facilitates the flow of information across business units. It allows for the seamless integration of data across financial and people systems to create a holistic view of the enterprise to support decision making.
In many organizations, Workday is considered the core people systems and is becoming more widely adopted for finance and a full ERP system.
ERP systems are considered the lifeblood of organizations. Problems with this key operational system will have a dramatic impact on the ability of the enterprise to survive and grow.
ERP implementation should not be a one-and-done exercise. There needs to be ongoing optimization to enable business processes and optimal organizational results.
Workday
Workday has many modules that work together to facilitate the flow of information across the business. Workday’s unique data platform allows for 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.
Workday operates in many industry verticals and performs well in service organizations.
An ERP system:
Product Description
Evolution of Workday
Workday HCM 2006
Workday Financial Management 2007
Workday 10 (Finance & HCM) 2010
Workday Student (Higher Education) 2011
Workday Cloud (PAAS) 2017
Acquisition of Adaptive Insights 2018
Acquisition of VNDLY 2021
Vendor Description
Employees: 12,500
Headquarters: Pleasanton, CA
Website: workday.com
Founded: 2005
Presence: Global, Publicly Traded
77% of clients were satisfied with the product’s business value created. 78% of clients were satisfied that the cost is fair relative to value, and 95% plan to renew. (SoftwareReviews, 2022)
Workday has seen steady growth working with over 50% of Fortune 500 companies. 4,100 of those are HCM and finance customers. It has seen great success in service industries and has a 95% gross retention rate. (Diginomica)
Workday reported a 40% year-over-year increase in Workday Financial Management deployments for both new and existing customers, as accelerated demand for Workday cloud-based continues. (Workday, June 2021)
Workday continues to invest in Workday Finance
Recent Finance-Related Acquisitions
Workday challenges and dissatisfaction
Organizational
People and teams
Technology
Data
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.
Enterprise Application Optimization - 124%
Product - 65%
Enterprise Application Selection - 76%
Agile - 79%
(Info-Tech case data, 2022; N=3,293)
We are seeing Applications leaders’ priorities change year over year, driven by a shift in their approach to problem solving. Leaders are moving from a process-centric approach to a collaborative approach that breaks down boundaries and brings teams together.
Application Portfolio Management - 13%
Business Process Management - 4%
Software Development Lifecycle -25%
(Info-Tech case data, 2022; N=3,293)
Software development lifecycle topics are tactical point solutions. Organizations have been “shifting left” to tackle the strategic issues such as product vision and Agile mindset to optimize the whole organization.
“A successful application optimization strategy starts with the business need in mind and not from a technological point of view. No matter from which angle you look at it, modernizing a legacy application is a considerable undertaking that can’t be taken lightly. Your best approach is to begin the journey with baby steps.” – Norelus, Pamidala, and Senti, 2020
| 1. Map Current-State Capabilities | 2. Assess Your Current State | 3. Identify Key Optimization Areas | 4. Build Your Optimization Roadmap | |
|---|---|---|---|---|
| Phase Steps |
|
|
|
|
| Phase Outcomes |
|
|
|
|
Identify and prioritize your Workday optimization goals.
Assess IT-enabled user satisfaction across your Workday portfolio.
Complete an assessment of processes, user satisfaction, data quality, and vendor management.
MANAGED AP AUTOMATION with OneSource Virtual
TripAdvisor + OneSource
INDUSTRY: Travel
SOURCE: OneSource Virtual, 2017
TripAdvisor needed a solution that would decrease administrative labor from its accounting department.
“We needed something that was already compatible with our Workday tenant, that didn’t require a lot of customizations and would be an enhancement to our processes.” – Director of Accounting Operations, Scott Garner
Requirements included:
TripAdvisor chose to outsource its accounts payable services to OneSource Virtual (OSV).
OneSource Virtual offers the comprehensive finance and accounting outsourcing solutions needed to improve efficiency, eliminate paper processes, reduce errors, and improve cash flow.
Managed AP services include scanning and auditing all extracted invoice data for accuracy, transmitting AP files with line-item details from invoices, and creating full invoice images in Workday.
“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
A Guided Implementation (GI) is series of calls with an Info-Tech analyst to help implement our best practices in your organization.
A typical GI is between 8 to 12 calls over the course of 4 to 6 months.
Phase 1
Call #1: Scope requirements, objectives, and your specific challenge.
Phase 2
Call #2:
Call #3:
Phase 3
Call #4: Understand product satisfaction and vendor management.
Call #5: Review APA results.
Call #6: Understand Workday optimization opportunities.
Call #7: Determine the right Workday path for your organization.
Phase 4
Call #8: Build out optimization roadmap and next steps.
Contact your account representative for more information.
workshops@infotech.com 1-888-670-8889
| Day 1 | Day 2 | Day 3 | Day 4 | Day 5 | |
|---|---|---|---|---|---|
| Define Your Workday Application Vision | Map Current State | Assess Workday | Build Your Optimization Roadmap | Next Steps and Wrap-Up (offsite) | |
| Activities | 1.1 Identify Stakeholders and Build Your Optimization Team 1.2 Build an ERP Strategy Model 1.3 Inventory Current System State 1.4 Define Optimization Timeframe 1.5 Understand Workday Costs | 2.1 Assess Workday Capabilities 2.2 Review Your Satisfaction With the Vendor/Product and Willingness for Change | 3.1 Prioritize Optimization Opportunities 3.2 Discover Optimization Initiatives | 4.1 Build Your Optimization 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 |
|
|
|
|
Phase 1
1.1 Identify Stakeholders and Build Your Optimization Team
1.2 Build an ERP Strategy Model
1.3 Inventory Current System State
1.4 Define Optimization Timeframe
1.5 Understand Workday Costs
Phase 2
2.1 Assess Workday Capabilities
2.2 Review Your Satisfaction With the Vendor/Product and Willingness for Change
Phase 3
3.1 Prioritize Optimization Opportunities
3.2 Discover Optimization Initiatives
Phase 4
4.1 Build Your Optimization Roadmap
This phase will guide you through the following activities:
This phase involves the following participants:
1.1.1 Identify Stakeholders Critical to Success
1.1.2 Map Your Workday Optimization Stakeholders
1.1.3 Determine Your Workday Optimization Team
Map Current State Capabilities
Step 1.1
Step 1.2
Step 1.3
Step 1.4
Step 1.5
This step will guide you through the following activities:
This step involves the following participants:
Outcomes of this step
| Title | Role Within the Project Structure |
|---|---|
| Organizational Sponsor |
|
| Project Manager |
|
| Business Unit Leaders |
|
| Optimization Team |
|
| Steering Committee |
|
Info-Tech Insight
Do not limit project input or participation. Include subject-matter experts and internal stakeholders at stages within the project. Such inputs can be solicited on a one-off basis as needed. This ensures you take a holistic approach to create your ERP optimization strategy.
1 hour
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
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 |
|
|
|
|
| Values | 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.
1 hour
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
Consider the core team functions when putting together the project team. Form a cross-functional team (i.e. across IT, Marketing, Sales, Service, and Operations) to create a well-aligned ERP optimization strategy.
Don’t let your project team become too large 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 such as Human Resources, Operations, Manufacturing, Marketing, Sales, Service, and Finance as well as IT.
| Required Skills/Knowledge | Suggested Project Team Members |
|---|---|
|
|
|
|
|
|
1 hour
Note: Depending on your initiative and size of your organization, the size of this team will vary.
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
1.2.1 Explore Organizational Goals and Business Needs
1.2.2 Discover Environmental Factors and Technology Drivers
1.2.3 Consider Potential Barriers to Achieving Workday Optimization
1.2.4 Set the Foundation for Success
1.2.5 Discuss Workday Strategy and Develop Your ERP Optimization Goals
Map Current State Capabilities
Step 1.1
Step 1.2
Step 1.3
Step 1.4
Step 1.5
This step will guide you through the following activities:
This step involves the following participants:
Outcomes of this step
Your corporate strategy:
Your IT strategy:
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 need to occur at the executive level but at each level of the organization.
Begin by conducting interviews of your executive team. Interview the following leaders:
INTERVIEWS MUST UNCOVER:
| Business Needs | Business Drivers | |
|---|---|---|
| Definition | A business need is a requirement associated with a particular business process. | A business need is a requirement associated with a particular business process. |
| Examples |
|
|
Info-Tech Insight
One of the biggest drivers for ERP adoption is the ability to make quicker decisions from timely information. This driver is a result of external considerations. Many industries today are highly competitive, uncertain, and rapidly changing. To succeed under these pressures, there needs to be timely information and visibility into all components of the organization.
60 minutes
Record this information in the Get the Most Out of Your Workday Workbook.
Organizational Goals
Business Needs
Download the Get the Most Out of Your Workday Workbook
Organizational Goals
Business Needs
| Technology Drivers | Environmental Factors | |
|---|---|---|
| Definition | Technology drivers are technological changes that have created the need for a new ERP enablement strategy. Many organizations turn to technology systems to help them obtain a competitive edge. | These external considerations are factors that take place outside of the organization and impact the way business is conducted inside the organization. These are often outside the control of the business. Look three to five years ahead, what challenges will the business face? Where will you have to adapt and pivot? How can we prepare for this? |
| Examples |
|
|
Info-Tech Insight
A comprehensive plan that takes into consideration organizational goals, departmental needs, technology drivers, and environmental factors will allow for a collaborative approach to defining your Workday strategy.
30 minutes
Record this information in the Get the Most Out of Your Workday Workbook.
External Considerations
Technology Considerations
Functional Requirements
Download the Get the Most Out of Your Workday Workbook
There are several different factors that may stifle the success of an ERP implementation. Organizations that are creating an ERP foundation must scan their current environment to identify internal barriers and challenges.
Common Internal Barriers
| Management Support | Organizational Culture | Organizational Structure | IT Readiness | |
|---|---|---|---|---|
| Definition | The degree of understanding and acceptance toward ERP systems. | The collective shared values and beliefs. | The functional relationships between people and departments in an organization. | The degree to which the organization’s people and processes are prepared for a new ERP system. |
| Questions |
|
|
|
|
| Impact |
|
|
|
|
1-3 hours
Record this information in the Get the Most Out of Your Workday Workbook.
Functional Gaps
Technical Gaps
Process Gaps
Barriers to Success
Download the Get the Most Out of Your Workday Workbook
Organizational Goals
Barriers
(Epizitone and Olugbara, 2019; CC BY 4.0)
Info-Tech Insight
Complement your ability to deliver on your critical success factors with the capabilities of your implementation partner to drive a successful ERP implementation.
“Implementation partners can play an important role in successful ERP implementations. They can work across the organizational departments and layers creating a synergy and a communications mechanism.” – Ayogeboh Epizitone, Durban University of Technology
1-3 hours
Record this information in the Get the Most Out of Your Workday Workbook.
Business Benefits
IT Benefits
Organizational Benefits
Enablers of Success
Download the Get the Most Out of Your Workday Workbook
Benefits can be realized internally and externally to the organization or department and have different drivers of value.
Organizational Goals
Increased Revenue
Application functions that are specifically related to the impact on your organization’s ability to generate revenue and deliver value to your customers.
Reduced Costs
Reduction of overhead. The ways in which an application limits the operational costs of business functions.
Enhanced Services
Functions that enable business capabilities that improve the organization’s ability to perform its internal operations.
Reach Customers
Application functions that enable and improve the interaction with customers or produce market information and insights.
Business Value Matrix
30 minutes
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
1.3.1 Inventory Workday Applications and Interactions
1.3.2 Draw Your Workday System Diagram
1.3.3 Inventory Your Workday Modules and Business Capabilities (or Business Processes)
1.3.4 Define Your Key Workday Optimization Modules and Business Capabilities
Map Current-State Capabilities
Step 1.1
Step 1.2
Step 1.3
Step 1.4
Step 1.5
This step will guide you through the following activities:
This step involves the following participants:
Outcomes of this step
1-3+ hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
When assessing the current application portfolio that supports your ERP, the tendency will be to focus on the applications under the ERP umbrella. These relate mostly to marketing, sales, and customer service. Be sure to include systems that act as input to, or benefit due to outputs from, ERP or similar applications.
1-3+ hours
Download the Get the Most Out of Your Workday Workbook
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:
A business capability map provides details that help the business architecture practitioner direct attention to a specific area of the business for further assessment.
Value stream defined:
Value Streams:
Design Product
Produce Product
Sell Product
Customer Service
Value streams connect business goals to the organization’s value realization activities in the marketplace. Those activities are dependent on the specific industry segment in which an organization operates. There are two types of value streams: core value streams and support value streams.
Taking a value stream approach to process mapping allows you to move across departmental and system boundaries to understand the underlying business capability.
Some mistakes organizations make are over-customizing processes, or conversely, not customizing when required. Workday provides good baseline process that work for most organizations. However, if a process is broken or not working efficiently take the time to investigate it, including underlying policies, roles, workflows, and integrations.
| Operating Processes | ||||
|---|---|---|---|---|
| 1. Develop vision and strategy | 2. Develop and manage products and services | 3. Market and sell products and services | 4. Deliver physical products | 5. Deliver services |
| Management and Support Processes | ||||
| 6. Manage customer service | ||||
| 7. Develop and manage human capital | ||||
| 8. Manage IT | ||||
| 9. Manage financial resources | ||||
| 10. Acquire, construct, and manage assets | ||||
| 11. Manage enterprise risk, compliance, remediation, and resiliency | ||||
| 12. Manage external relationships | ||||
| 13. Develop and manage business capabilities | ||||
(APQC)
If you do not have a documented process model, you can use the APQC Framework to help define your inventory of sales 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.
A process classification framework is helpful for organizations to effectively define their processes and manage them appropriately.
Use Info-Tech’s related industry resources or publicly available process frameworks (such as APQC) to develop and map your business processes.
These processes can then be mapped to supporting applications and modules. Policies, roles, and workflows also play a role and should be considered in the overall functioning.
APQC’s Process Classification Framework
(APQC)
| Level 1 | Level 2 | Level 3 | Level 4 |
|---|---|---|---|
| Market and sell products and services | Understand markets, customers, and capabilities | Perform customer and market intelligence analysis | Conduct customer and market research |
| Market and sell products and services | Develop a sales strategy | Develop a sales forecast | Gather current and historic order information |
| Deliver services | Manage service delivery resources | Manage service delivery resource demand | Develop baseline forecasts |
| ? | ? | ? | ? |
Info-Tech Insight
Focus your initial assessment on the level-1 processes that matter to your organization. This allows you to target your scant resources on the areas of optimization that matter most to the organization and minimize the effort required from your business partners.
You may need to iterate the assessment as challenges are identified. This allows you to be adaptive and deal with emerging issues more readily and become a more responsive partner to the business.
An operating model is a framework that drives operating decisions. It helps to set the parameters for the scope of ERP and the processes that will be supported. The operating model will serve to group core operational processes. These groupings represent a set of interrelated, consecutive processes aimed at generating a common output.
From your developed processes and your Workday license agreements you will be able to pinpoint the scope for investigation, including the processes and modules.
1-3+ hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
1-3+ hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
1.4.1 Define Workday Key Dates, and Workday Optimization Roadmap Timeframe and Structure
Step 1.1
Step 1.2
Step 1.3
Step 1.4
Step 1.5
This step will guide you through the following activities:
This step involves the following participants:
Outcomes of this step
1-3+ hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
1.5.1 Document Costs Associated With Workday
Step 1.1
Step 1.2
Step 1.3
Step 1.4
Step 1.5
This step will walk you through the following activities:
This step involves the following participants:
Outcomes of this step
1-3 hours
Before you can make changes and optimization decisions, you need to understand the high-level costs associated with your current application architecture. This activity will help you identify the types of technology and people costs associated with your current systems.
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
Phase 1
1.1 Identify Stakeholders and Build Your Optimization Team
1.2 Build an ERP Strategy Model
1.3 Inventory Current System State
1.4 Define Optimization Timeframe
1.5 Understand Workday Costs
Phase 2
2.1 Assess Workday Capabilities
2.2 Review Your Satisfaction With the Vendor/Product and Willingness for Change
Phase 3
3.1 Prioritize Optimization Opportunities
3.2 Discover Optimization Initiatives
Phase 4
4.1 Build Your Optimization Roadmap
This phase will guide you through the following activities:
This phase involves the following participants:
2.1.1 Rate Capability Relevance to Organizational Goals
2.1.2 Complete a Workday Application Portfolio Assessment
2.1.3 (Optional) Assess Workday Process Maturity
Step 2.1
Step 2.2
This step will guide you through the following activities:
This step involves the following participants:
Outcomes of this step
3 hours
Option 1: Use Info-Tech’s Application Portfolio Assessment to generate your user satisfaction score. This tool not only measures application satisfaction but also elicits great feedback from users regarding the support they receive from the IT team around Workday.
Option 2: Create a survey manually.
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook

3 hours
Option 1: Use Info-Tech’s Application Portfolio Assessment to generate your user satisfaction score. This tool not only measures application satisfaction but also elicits great feedback from users regarding the support they receive from the IT team around Workday.
Option 2: Create a survey manually.
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
Process Assessment
Strong
Moderate
Weak
1.1 Financial Planning and Analysis
1.2 Accounting and Financial Close
1.3 Treasury Management
1.4 Financial Operations
1.5 Governance, Risk & Compliance
2.1 Core HR
| Description | All aspects related to financial operations | ||
|---|---|---|---|
| Key Success Indicators | Month-end reporting in 5 days | AR at risk managing down (zero over 90 days) | Weekly operating cash flow updates |
| Timely liquidity for claims payments | Payroll audit reporting and insights reporting | 90% of workflow tasks captured in ERP | |
| EFT uptake | Automated reconciliations | Reduce audit hours required | |
| Current Pain Points | A lot of voided and re-issued checks | NIDPP | Integration with banks; can’t get the information back into existing ERP |
| There is no payroll integration | No payroll automation and other processes | Lack of integration with HUB | |
| Not one true source of data | Incentive payment processing | Rewards program management | |
| Audit process is onerous | Reconcile AP and AR for dealers | ||
The process is formalized, documented, optimized, and audited.
The process is poorly documented. More than one person knows how to do it. Inefficient and error-prone.
The process is not documented. One person knows how to do it. The process is ad hoc, not formalized, inconsistent.
General Ledger
Accounts Receivable
Incentives Management
Accounts Payable
General Ledger Consolidation
Treasury Management
Cash Management
Subscription / recurring payments
Treasury Transactions
2.2.1 Rate Your Vendor and Product Satisfaction
2.2.2 Review Workday Product Scores (if applicable)
2.2.3 Evaluate Your Product Satisfaction
2.2.4 Check Your Business Process Change Tolerance
Step 2.1
Step 2.2
This step will guide you through the following activities:
This step involves the following participants:
Outcomes of this step
30 minutes
Use Info-Tech’s vendor satisfaction survey to identify optimization areas with your ERP product(s) and vendor(s).
Record this information in the Get the Most Out of Your Workday Workbook
SoftwareReviews’ Enterprise Resource Planning Category
Download the Get the Most Out of Your Workday Workbook
30 minutes
Record this information in the Get the Most Out of Your Workday Workbook.
SoftwareReviews’ Enterprise Resource Planning Category
Download the Get the Most Out of Your Workday Workbook
(SoftwareReviews ERP Mid-Market, 2022; SoftwareReviews ERP Enterprise, 2022)
1 hours
Record this information in the Get the Most Out of Your Workday Workbook
Legend:
Willing to follow best practice
May be challenging or unique business model
Low tolerance for change
Out of Scope
| Product-Centric Capabilities | ||||
|---|---|---|---|---|
| R&D | Production | Supply Chain | Distribution | Asset Mgmt |
| Idea to Offering | Plan to Produce | Procure to Pay | Forecast to Delivery | Acquire to Dispose |
| Add/Remove | Shop Floor Scheduling | Add/Remove | Add/Remove | Add/Remove |
| Add/Remove | Product Costing | Add/Remove | Add/Remove | Add/Remove |
| Service-Centric Capabilities | ||||
|---|---|---|---|---|
| Finance | HR | Marketing | Sales | Service |
| Record to Report | Hire to Retire | Market to Order | Quote to Cash | Issue to Resolution |
| Add/Remove | Add/Remove | Add/Remove | Add/Remove | Add/Remove |
| Add/Remove | Add/Remove | Add/Remove | Add/Remove | Add/Remove |
Determine the areas of risk to conform to best practice and minimize customization. These will be areas needing focus from the vendor, supporting change and guiding best practice.
For example: Must be able to support our unique process manufacturing capabilities and enhance planning and visibility to detailed costing.
Phase 1
1.1 Identify Stakeholders and Build Your Optimization Team
1.2 Build an ERP Strategy Model
1.3 Inventory Current System State
1.4 Define Optimization Timeframe
1.5 Understand Workday Costs
Phase 2
2.1 Assess Workday Capabilities
2.2 Review Your Satisfaction With the Vendor/Product and Willingness for Change
Phase 3
3.1 Prioritize Optimization Opportunities
3.2 Discover Optimization Initiatives
Phase 4
4.1 Build Your Optimization Roadmap
This phase will walk you through the following activities:
This phase involves the following participants:
3.1.1 Prioritize Optimization Capability Areas
Build Your Optimization Roadmap
Step 3.1
Step 3.2
This step will guide you through the following activities:
This step involves the following participants:
Outcomes of this step
Info-Tech Insight
Enabling a high-performing organization requires excellent management practices and continuous optimization efforts. Your technology portfolio and architecture are important, but we must go deeper. Taking a holistic view of ERP technologies in the environments in which they operate allows for the inclusion of people and process improvements – this is key to maximizing business results. Using a formal ERP optimization initiative will drive business-IT alignment, identify IT automation priorities, and dig deep into continuous process improvement.
Address process gaps:
Support user satisfaction:
Improve data quality:
Proactively manage vendors:
The Business
Keepers of the organization’s mission, vision, and value statements that define IT success. The business maintains the overall ownership and evaluation of the applications.
Business Value of Applications
IT
Technical subject matter experts of the applications they deliver and maintain. Each IT function works together to ensure quality applications are delivered to stakeholder expectations.
First, the authorities on business value need to define and weigh their value drivers that describe the priorities of the organization. This will allow the applications team to apply a consistent, objective, and strategically aligned evaluation of applications across the organization.
In this context…
business value is
the value of the business outcome that the application produces. Additionally, it is how effective the application is at producing that outcome.
Business value IS NOT
the user’s experience or satisfaction with the application.
Create or Improve:
Capabilities are what the system and business do that creates value for the organization.
Optimization initiatives are projects with a definitive start and end date, and they enhance, create, maintain, or remove capabilities with the goal of increasing value.
Brainstorm ERP optimization initiatives in each area. Ensure you are looking for all-encompassing opportunities within the context of IT, the business, and Workday systems.
Financial vs. Human Benefits
Financial benefits refer to the degree to which the value source can be measured through monetary metrics and are often quite tangible.
Human benefits refer to how an application can deliver value through a user’s experience.
Inward vs. Outward Orientation
Inward refers to value sources that have an internal impact and improve your organization’s effectiveness and efficiency in performing its operations.
Outward refers to value sources that come from your interaction with external factors, such as the market or your customers.
Increased Revenue
Application functions that are specifically related to the impact on your organization’s ability to generate revenue and deliver value to your customers.
Reduced Costs
Reduction of overhead. The ways in which an application limits the operational costs of business functions.
Enhanced Services
Functions that enable business capabilities that improve the organization’s ability to perform its internal operations.
Reach Customers
Application functions that enable and improve the interaction with customers or produce market information and insights.
Review your ERP capability areas and rate them according to relevance to organizational goals. This will allow you to eliminate optimization ideas that may not bring value to the organization.
| How important is it? | How Difficult is it? |
|---|---|
|
What is the value?
What is the benefit?
What is the impact?
|
What is the cost?
What is the level of effort?
What is the risk of implementing/not implementing? What is the complexity? |
(Roadmunk)
| Reach | Impact | Confidence | Effort |
|---|---|---|---|
|
How many people will this improvement impact? Internal: # of users OR # of transactions per period External: # of customers OR # of transactions per period |
What is the scale of impact? How much will the improvement affect satisfaction? Example Weighting: 1 = Massive Impact 2 = High Impact 1 = Medium Impact 0.5 = Low Impact 0.25 = Very Low Impact |
How confident are we that the improvements are achievable and that they will meet the impact estimates? Example Weighting: 1 = High Confidence 0.80 = Medium Confidence 0.50 = Low Confidence |
How much investment will be required to implement the improvement initiative? FTE hours x cost per hour |
(Intercom)
1-3 hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
Activities
3.2.1 Discover Product and Vendor Satisfaction Opportunities
3.2.2 Discover Capability and Feature Optimization Opportunities
3.2.3 Discover Process Optimization Opportunities
3.2.4 Discover Integration Optimization Opportunities
3.2.5 Discover Data Optimization Opportunities
3.2.6 Discover Workday Cost-Saving Opportunities
Build Your Optimization Roadmap
Step 3.1
Step 3.2
This step will guide you through the following activities:
This step involves the following participants:
Outcomes of this step


Workday Advisory Partners have in-depth knowledge to help customers determine what’s best for their needs and how to maximize business value. They guide you through digital acceleration strategy and planning, product selection, change management, and more.
Workday Services Partners represent a curated community of global systems integrators and regional firms that help companies deploy Workday and continually adopt new capabilities.
Workday Software Partners are a global ecosystem of application, content, and technology software companies that design, build, and deploy solution extensions to help customers enhance the capabilities of Workday.
Workday’s Global Payroll Cloud (GPC) program makes it easy to expand payroll (outside of the US, Canada, the UK, and France) to third-party payroll providers around the world using certified, prebuilt integrations from Workday Partners. Payroll partners provide solutions in more than 100 countries.
Adaptive planning partners guide you through all aspects of everything from integration to deployment.
With large-scale ERP and HCM systems, the success of the system can be as much about the SI (Systems Integrator) or vendor partners as it is about the core product.
In evaluating your Workday system, think about Workday’s extensive partner network to understand how you can capitalize on your installation.
You do not need to reinvent the system; you may just need an additional service partner or bolt-on solution to round out your product functionality.
Info-Tech Insight
A vendor management initiative is an organization’s formalized process for evaluating, selecting, managing, and optimizing third-party providers of goods and services.
The amount of resources you assign to managing vendors depends on the number and value of your organization’s relationships. Before optimizing your vendor management program around the best practices presented in Info-Tech’s Jump Start Your Vendor Management Initiative blueprint, assess your current maturity and build the process around a model that reflects the needs of your organization.
Note: Info-Tech uses VMI interchangeably with the terms “vendor management office (VMO),” “vendor management function,” “vendor management process,” and “vendor management program.”
1-2 hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook

1-2 hours
Record this information in the Get the Most Out of Your Workday Workbook
Download the Get the Most Out of Your Workday Workbook
| Goals of Process Improvement | Process Improvement Sample Areas | Improvement Possibilities |
|---|---|---|
|
|
|
1-2 hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
The benefits of integration
The challenges of integration
| Financial Consolidation | Data Backup | Synchronization Across Sites | Legacy Consolidation |
|---|---|---|---|
|
|
|
|
For more information: Implement a Multi-site ERP
1-2 hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
IT has several concerns around ERP data and wide dissemination of that data across sites. Large organizations can benefit from building a data warehouse or at least adopting some of the principles of data warehousing. The optimal way to deal with the issue of integration is to design a metadata-driven data warehouse that acts as a central repository for all ERP data. This serves as the storage facility for millions of transactions, formatted to allow analysis and comparison.
Key considerations:
Info-Tech Insight
Data warehouse solutions can be expensive. See Info-Tech’s Build a Data Warehouse on a Solid Foundation for guidance on what options are available to meet your budget and data needs.
| Data Quality Management | Effective Data Governance | Data-Centric Integration Strategy | Extensible Data Warehousing |
|---|---|---|---|
|
|
|
|
1-2 hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook

Info-Tech Insight
The number one reason organizations leave Workday is because of cost. Do not be strong-armed into a contract you do not feel comfortable with. Do your homework, know your leverage points, be fully prepared for cost negotiations, use their competition to your advantage, and get support – such as Info-Tech’s vendor management resources and team.
Since 2007, Workday has been steadily growing its market share and footprint in human capital management, finance, and student information systems.
Organizations considering additional modules or undergoing contract renewal need to gain insight into areas of leverage and other relevant vendor information.
Key issues that occur include pricing transparency and contractual flexibility on terms and conditions. Adequate planning and communication need to be taken into consideration before entering into any agreement.
1-2 hours
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
Phase 1
1.1 Identify Stakeholders and Build Your Optimization Team
1.2 Build an ERP Strategy Model
1.3 Inventory Current System State
1.4 Define Optimization Timeframe
1.5 Understand Workday Costs
Phase 2
2.1 Assess Workday Capabilities
2.2 Review Your Satisfaction With the Vendor/Product and Willingness for Change
Phase 3
3.1 Prioritize Optimization Opportunities
3.2 Discover Optimization Initiatives
Phase 4
4.1 Build Your Optimization Roadmap
This phase will walk you through the following activities:
This phase involves the following participants:
Get the Most Out of Your Workday
4.1.1 Evaluate Optimization Initiatives
4.1.2 Prioritize Your Workday Initiatives
4.1.3 Build a Roadmap
4.1.4 Build a Visual Roadmap
Next steps
Step 4.1
This step will walk you through the following activities:
This step involves the following participants:
Outcomes of this step
1 hour
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
1 hour
Optimization initiatives: Determine which if any to proceed with.
Record this information in the Get the Most Out of Your Workday Workbook.
Note: Your roadmap should be treated as a living document that is updated and shared with the stakeholders on a regular schedule.
Download the Get the Most Out of Your Workday Workbook
1 hour
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 roadmap.
Record this information in the Get the Most Out of Your Workday Workbook.
Download the Get the Most Out of Your Workday Workbook
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 ongoing optimization to enable business processes and optimal organizational results.
Get the Most Out of Your Workday allows organizations to proactively implement continuous assessment and optimization of their enterprise resource planning system, including:
This formal Workday 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
Ben Dickie
Research Practice Lead
Info-Tech Research Group
Ben Dickie is a Research Practice Lead at Info-Tech Research Group. His areas of expertise include customer experience management, CRM platforms, and digital marketing. He has also led projects pertaining to enterprise collaboration and unified communications.
Scott Bickley
Practice Lead and Principal Research
Director Info-Tech Research Group
Scott Bickley is a Practice Lead and Principal Research Director at Info-Tech Research Group focused on vendor management and contract review. He also has experience in the areas of IT asset management (ITAM), software asset management (SAM), and technology procurement along with a deep background in operations, engineering, and quality systems management.
Andy Neil
Practice Lead, Applications
Info-Tech Research Group
Andy is a Senior Research Director, Data Management and BI, at Info-Tech Research Group. He has over 15 years of experience in managing technical teams, information architecture, data modeling, and enterprise data strategy. He is an expert in enterprise data architecture, data integration, data standards, data strategy, big data, and the development of industry standard data models.
“9 product prioritization frameworks for product managers.” Roadmunk, n.d. Accessed 15 May 2022.
Armel, Kate. "New Article: Data-Driven Estimation, Management Lead to High Quality." QSM: Quantitative Software Management, 14 May 2013. Accessed 4 Feb. 2021.
Collins, George, et al., “Connecting Small Businesses in the US.” Deloitte Commissioned by Google, 2017. Web.
Epizitone, Ayogeboh, and Oludayo O. Olugbara. "Critical Success Factors for ERP System Implementation to Support Financial Functions." Academy of Accounting and Financial Studies Journal, vol. 23, no. 6, 2019. Accessed 12 Oct. 2021
Gheorghiu, Gabriel. "The ERP Buyer’s Profile for Growing Companies." Selecthub, 2018. Accessed 21 Feb. 2021.
Karlsson, Johan. "Product Backlog Grooming Examples and Best Practices." Perforce, 18 May 2018. Accessed 4 Feb. 2021.
Lauchlan, Stuart. “Workday accelerates into fiscal 2023 with a strong year end as cloud adoption gets a COVID-bounce.” diginomica, 1 March 2022. Web.
"Maximizing the Emotional Economy: Behavioral Economics." Gallup, n.d. Accessed 21 Feb. 2021.
Noble, Simon-Peter. “Workday: A High-Quality Business That's Fairly Valued.” Seeking Alpha, 8 Apr. 2019. Web.
Norelus, Ernese, Sreeni Pamidala, and Oliver Senti. "An Approach to Application Modernization: Discovery and Assessment Phase," Medium, 24 Feb. 2020. Accessed 21 Feb. 2021.
"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, vol. 22, no. 1, 2019, pp. 29-37. Accessed 21 Feb. 2021.
“Workday Enterprise Management Cloud Product Scorecard.” SoftwareReviews, May 2022. Web.
“Workday Meets Growing Customer Demand with Record Number of Deployments and Industry-Leading Customer Satisfaction Score.” Workday, Inc., 7 June 2021. Web.
Establish and design a tabletop exercise capability to support and test the efficiency of the core prevention, detection, analysis, and response functions that consist of an organization's threat intelligence, security operations, vulnerability management, and incident response functions.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Evaluate the need for a tabletop exercise.
Determine the topics, scope, objectives, and participant roles and responsibilities.
Create briefings, guides, reports, and exercise injects.
Host the exercise in a conference or classroom setting.
Plan to ensure measurement and continued improvement.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
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.
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.
The focus of this phase is to:
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.
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.
An intimate understanding of the design thinking
An assessment of design-centricity of your organization and identification of areas for improvement
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
Report from Info-Tech’s diagnostic: ‘How design-centric is your organization?’ with identified areas for improvement.
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.
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
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
Trends that impact your organization.
Taxonomy of critical customer journeys and a baseline of customers’ satisfaction with those.
The focus of this module is to define an approach for a design program that suits your organization’s specific goals and culture.
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.
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
An approach for your design thinking program: objectives and key measures; structure of the program, etc.
We may not be able to show you this just yet.
Our deeper, more detailed content is reserved for Tymans Group clients.
If you are interested in retaining our services or would really like access, please contact us.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
This blueprint will help you build a business case for selecting the right MMS platform, define key requirements, and conduct a thorough analysis and scan of the current state of the ever-evolving MMS market space.
Modern marketing management suites (MMS) are imperative given today's complex, multitiered, and often non-standardized marketing processes. Relying on isolated methods such as lead generation or email marketing techniques for executing key cross-channel and multichannel marketing initiatives is not enough to handle the complexity of contemporary marketing management activities.
Organizations need to invest in highly customizable and functionally extensive MMS platforms to provide value alongside the marketing value chain and a 360-degree view of the consumer's marketing journey. IT needs to be rigorously involved with the sourcing and implementation of the new MMS tool, and the necessary business units also need to own the requirements and be involved from the initial stages of software selection.
To succeed with MMS implementation, consider drafting a detailed roadmap that outlines milestone activities for configuration, security, points of integration, and data migration capabilities and provides for ongoing application maintenance and support.
Yaz Palanichamy
Senior Research Analyst, Customer Experience Strategy
Info-Tech Research Group
IT must collaborate with marketing professionals and other key stakeholder groups to define a unified vision and holistic outlook for a right-sized MMS platform.
| 1. Understand Core MMS Features |
2. Build the Business Case & Streamline Requirements |
3. Discover the MMS Market Space & Prepare for Implementation |
|
|---|---|---|---|
|
Phase Steps |
|
|
|
|
Phase Outcomes |
|
|
|
| Phase 1 | Phase 2 | Phase 3 |
|---|---|---|
|
Call #1: Understand what a marketing management suite is. Discuss core capabilities and key trends. |
Call #2: Build the business case Call #3: Define your core Call #4: Build and sustain procurement vehicle best practices. |
Call #5: Evaluate the MMS vendor landscape and short-list viable options.
|
A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization.
The MMS procurement process should be broken into segments:
“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.”
Our Definition: Marketing management suite (MMS) platforms are core enterprise applications that provide a unified set of marketing processes for a given organization and, typically, the capability to coordinate key cross-channel marketing initiatives.
Key product capabilities for sophisticated MMS platforms include but are not limited to:
Using a robust and comprehensive MMS platform equips marketers with the appropriate tools needed to make more informed decisions around campaign execution, resulting in better targeting, acquisition, and customer retention initiatives. Moreover, such tools can help bolster effective revenue generation and ensure more viable growth initiatives for future marketing growth enablement strategies.
Feature sets are rapidly evolving over time as MMS offerings continue to proliferate in this market space. Ensure that you focus on core components such as customer conversion rates and new lead captures through maintaining well- integrated multichannel campaigns.
A right-sized MMS software selection and procurement decision should involve comprehensive requirements and needs analysis by not just Marketing but also other organizational units such as IT, in conjunction with input suppled from the internal vendor procurement team.
Phase 1 |
Phase 2 |
Phase 3 |
|---|---|---|
|
1.1 Define MMS Platforms 1.2 Classify Table Stakes & Differentiating Capabilities 1.3 Explore Trends |
2.1 Build the Business Case 2.2 Streamline Requirements Elicitation 2.3 Develop an Inclusive RFP Approach |
3.1 Discover Key Players in the Vendor Landscape 3.2 Engage the Shortlist & Select Finalist 3.3 Prepare for Implementation |
This phase will walk you through the following activities:
This phase involves the following participants:
Our Definition: Marketing management suite (MMS) platforms are core enterprise applications that provide a unified set of marketing processes for a given organization and, typically, the capability to coordinate key cross-channel marketing initiatives.
Key product capabilities for sophisticated MMS platforms include but are not limited to:
Using a robust and comprehensive MMS platform equips marketers with the appropriate tools needed to make more informed decisions around campaign execution, resulting in better targeting, acquisition, and customer retention initiatives. Moreover, such tools can help bolster effective revenue generation and ensure more viable growth initiatives for future marketing growth enablement strategies.
Feature sets are rapidly evolving over time as MMS offerings continue to proliferate in this market space. Ensure that you focus on core components such as customer conversion rates and new lead captures through maintaining well- integrated multichannel campaigns.
Initial traction for marketing management strategies began with the need to holistically understand the effects of advertising efforts and how the media mix could be best optimized.
|
1902 |
1920s-1930s |
1942 |
1952-1964 |
1970s-1990s |
|---|---|---|---|---|
|
Recognizing the increasing need for focused and professional marketing efforts, the University of Pennsylvania offers the first marketing course, dubbed "The Marketing of Products." |
As broadcast media began to peak, marketers needed to manage a greater number of complex and interspersed marketing channels. |
The introduction of television ads in 1942 offered new opportunities for brands to reach consumers across a growing media landscape. To generate the highest ROI, marketers sought to understand the consumer and focus on more tailored messaging and product personalization. Thus, modern marketing practices were born. |
Following the introduction of broadcast media, marketers had to develop strategies beyond traditional spray-and-pray methods. The first modern marketing measurement concept, "marketing mix," was conceptualized in 1952 and popularized in 1964 by Neil Borden. |
This period marked the digital revolution and the new era of marketing. With the advent of new communications technology and the modern internet, marketing management strategies reached new heights of sophistication. During the early 1990s, search engines emerged to help users navigate the web, leading to early forms of search engine optimization and advertising. |
|
6% |
As a continuously growing discipline, marketing management roles are predicted to grow faster than average, at a rate of 6% over the next decade. Source: U.S. Bureau of Labor Statistics, 2021 |
|---|---|
|
17% |
While many marketing management vendors offer A/B testing, only 17% of marketers are actively using A/B testing on landing pages to increase conversion rates. Source: Oracle, 2022 |
|
70% |
It is imperative that technology and SaaS companies begin to use marketing automation as a core component of their martech strategy to remain competitive. About 70% of technology and SaaS companies are employing integrated martech tools. Source: American Marketing Association, 2021 |
|
Email Marketing |
Lead Nurturing |
Reporting, Analytics, and Marketing KPIs |
Marketing Campaign Management |
Integrational Catalog |
|---|---|---|---|---|
|
The use of email alongside marketing efforts to promote a business' products and services. Email marketing can be a powerful tool to maintain connections with your audience and ensure sustained brand promotion. |
The process of developing and nurturing relationships with key customer contacts at every major touchpoint in their customer journey. MMS platforms can use automated lead-nurturing functions that are triggered by customer behavior. |
The use of well-defined metrics to help curate, gather, and analyze marketing data to help track performance and improve the marketing department's future marketing decisions and strategies. |
Tools needed for the planning, execution, tracking, and analysis of direct marketing campaigns. Such tools are needed to help gauge your buyers' sentiments toward your company's product offerings and services. |
MMS platforms should generally have a comprehensive open API/integration catalog. Most MMS platforms should have dedicated integration points to interface with various tools across the marketing landscape (e.g. social media, email, SEO, CRM, CMS tools, etc.). |
|
Digital Asset Management (DAM) |
A DAM can help manage digital media asset files (e.g. photos, audio files, video). |
|---|---|
|
Customer Data Management |
Customer data management modules help your organization track essential customer information to maximize your marketing results. |
|
Text-Based Marketing |
Text-based marketing strategy is ideal for any organization primarily focused on coordinating structured and efficient marketing campaigns. |
|
Customer |
Customer journey orchestration enables users to orchestrate customer conversations and journeys across the entire marketing value chain. |
|
AI-Driven Workflows |
AI-powered workflows can help eliminate complexities and allow marketers to automate and optimize tasks across the marketing spectrum. |
|
Dynamic Segmentation |
Dynamic segmentation to target audience cohorts based on recent actions and stated preferences. |
|
Advanced Email Marketing |
These include capabilities such as A/B testing, spam filter testing, and detailed performance reporting. |
|
Data-Driven |
Adapt innovative techniques such as conversational marketing to help collect, analyze, and synthesize crucial audience information to improve the customer marketing experience and pre-screen prospects in a more conscientious manner. |
|---|---|
|
Next Best Action Marketing |
Next best action marketing (NBAM) is a customer-centric paradigm/marketing technique designed to capture specific information about customers and their individual preferences. Predicting customers' future actions by understanding their intent during their purchasing decisions stage will help improve conversion rates. |
|
AI-Driven Customer |
The use of inclusive and innovative AI-based forecast modeling techniques can help more accurately analyze customer data to create more targeted segments. As such, marketing messages will be more accurately tailored to the customer that is reading them. |
Are you curious about the measures needed to boost engagement among your client base and other primary target audience groups? Conversational marketing intelligence metrics can help collect and disseminate key descriptive data points across a broader range of audience information.
Certain social media channels (e.g. LinkedIn and Facebook) like to take advantage of click-to-Messenger-style applications to help drive meaningful conversations with customers and learn more about their buying preferences. In addition, AI-driven chatbot applications can help the organization glean important information about the customer's persona by asking probing questions about their marketing purchase behaviors and preferences.
One of the newest phenomena in data-driven marketing technology and digital advertising techniques is the metaverse, where users can represent themselves and their brand via virtual avatars to further gamify their marketing strategies. Moreover, brands can create immersive experiences and engage with influencers and established communities and collect a wealth of information about their audience that can help drive customer retention and loyalty.
Metaverse marketing extends the potential for commercial brand development and representation: a deep dive into Gucci's metaverse practice
INDUSTRY: Luxury Goods Apparel
SOURCE: Vogue Business
Beginning with a small, family-owned leather shop known as House of Gucci in Florence, Italy, businessman and fashion designer Guccio Gucci sold saddles, leather bags, and other accessories to horsemen during the 1920s. Over the years, Gucci's offerings have grown to include various other personal luxury goods.
As consumer preferences have evolved over time, particularly with the younger generation, Gucci's professional marketing teams looked to invest in virtual technology environments to help build and sustain better brand awareness among younger consumer audiences.
In response to the increasing presence of metaverse-savvy gamers on the internet, Gucci began investing in developing its online metaverse presence to bolster its commercial marketing brand there.
A recent collaboration with Roblox, an online gaming platform that offers virtual experiences, provided Gucci the means to showcase its fashion items using the Gucci Garden – a virtual art installation project for Generation Z consumers, powered by Roblox's VR technology. The Gucci Garden virtual system featured a French-styled garden environment where players could try on and buy Gucci virtual fashion items to dress up their blank avatars.
Gucci's disruptive, innovative metaverse marketing campaign project with Roblox is proof of its commitment to tapping new marketing growth channels to showcase the brand to engage new and prospective consumers (e.g. Roblox's player base) across more unique sandboxed/simulation environments.
The freedom and flexibility in the metaverse environments allows brands such as Gucci to execute a more flexible digital marketing approach and enables them to take advantage of innovative metaverse-driven technologies in the market to further drive their data-driven digital marketing campaigns.
To improve conversion propensity, next best action techniques can use predictive modeling methods to help build a dynamic overview of the customer journey. With information sourced from actionable marketing intelligence data, MMS platforms can use NBAM techniques to identify customer needs based on their buying behavior, social media interactions, and other insights to determine what unique set of actions should be taken for each customer.
Rules-based recommender systems can help assign probabilities of purchasing behaviors based on the patterns in touchpoints of a customer's journey and interaction with your brand. For instance, a large grocery chain company such as Walmart or Whole Foods will use ML-based recommender systems to decide what coupons they should offer to their customers based on their purchasing history.
The inclusion of AI in data analytics helps make customer targeting more accurate
and meaningful. Organizations can analyze customer data more thoroughly and generate in-depth contextual and descriptive information about the targeted segments. In addition, they can use this information to automate the personalization of marketing campaigns for a specific target audience group.
To greatly benefit from AI-powered customer segmentation, organizations must deploy specialized custom AI solutions to help organize qualitative comments into quantitative data. This approach requires companies to use custom AI models and tools that will analyze customer sentiments and experiences based on data extracted from various touchpoints (e.g. CRM systems, emails, chatbot logs).
Phase 1 | Phase 2 | Phase 3 |
|---|---|---|
1.1 Define MMS Platforms 1.2 Classify Table Stakes & Differentiating Capabilities 1.3 Explore Trends | 2.1 Build the Business Case 2.2 Streamline Requirements Elicitation 2.3 Develop an Inclusive RFP Approach | 3.1 Discover Key Players in the Vendor Landscape 3.2 Engage the Shortlist & Select Finalist 3.3 Prepare for Implementation |
This phase will walk you through the following activities:
This phase involves the following participants:
Expert analyst guidance over 5 weeks on average to select software and negotiate with the vendor.
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 your membership.
CLICK HERE to book your Selection Engagement
Understanding business needs through requirements gathering is the key to defining everything you need from your software. However, it is an area where people often make critical mistakes.
|
Poorly scoped requirements |
Best practices |
|---|---|
|
|
Info-Tech Insight
Poor requirements are the number one reason projects fail. Review Info-Tech's Improve Requirements Gathering blueprint to learn how to improve your requirements analysis and get results that truly satisfy stakeholder needs.
Develop an inclusive and thorough approach to the RFP process
Review Info-Tech's process and understand how you can prevent your organization from leaking negotiation leverage while preventing vendors from taking control of your RFP.
You may be faced with multiple products, services, master service agreements, licensing models, service agreements, and more.
Use Info-Tech's Contract Review Service to gain insights on your agreements:
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.
CLICK to BOOK The Contract Review Service
CLICK to DOWNLOAD Master Contract Review and Negotiation for Software Agreements
Phase 1 | Phase 2 | Phase 3 |
|---|---|---|
1.1 Define MMS Platforms 1.2 Classify Table Stakes & Differentiating Capabilities 1.3 Explore Trends | 2.1 Build the Business Case 2.2 Streamline Requirements Elicitation 2.3 Develop an Inclusive RFP Approach | 3.1 Discover Key Players in the Vendor Landscape 3.2 Engage the Shortlist & Select Finalist 3.3 Prepare for Implementation |
This phase will walk you through the following activities:
This phase involves the following participants:
The following slides provide a top-level overview of the popular players you will encounter in your MMS shortlisting process.
|
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. |
CLICK HERE to ACCESS |
|---|
|
Comprehensive software reviews
|
|
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. |
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.

"Adobe Experience Cloud (AEC), formerly Adobe Marketing Cloud (AMC), provides a host of innovative multichannel analytics, social, advertising, media optimization, and content management products (just to name a few). The Adobe Marketing Cloud package allows users with valid subscriptions to download the entire collection and use it directly on their computer with open access to online updates. Organizations that have a deeply ingrained Adobe footprint and have already reaped the benefits of Adobe's existing portfolio of cloud services products (e.g. Adobe Creative Cloud) will find the AEC suite a functionally robust and scalable fit for their marketing management and marketing automation needs.
However, it is important to note that AEC's pricing model is expensive when compared to other competitors in the space (e.g. Sugar Market) and, therefore, is not as affordable for smaller or mid-sized organizations. Moreover, there is the expectation of a learning curve with the AEC platform. Newly onboarded users will need to spend some time learning how to navigate and work comfortably with AEC's marketing automaton modules. "
-
Yaz Palanichamy
Senior Research Analyst, Info-Tech Research Group
Adobe Experience Cloud Platform pricing is opaque.
Request a demo.*
*Info-Tech recommends reaching out to the vendor's internal sales management team for explicit details on individual pricing plans for the Adobe Marketing Cloud suite.
| 2021 |
Adobe Experience Platform Launch is integrated into the Adobe Experience Platform as a suite of data collection technologies (Experience League, Adobe). |
|---|---|
| November 2020 |
Adobe announces that it will spend $1.5 billion to acquire Workfront, a provider of marketing collaboration software (TechTarget, 2020). |
|
September 2018 |
Adobe acquires marketing automation software company Marketo (CNBC, 2018). |
| June 2018 |
Adobe buys e-commerce services provider Magento Commerce from private equity firm Permira for $1.68 billion (TechCrunch, 2018). |
| 2011 |
Adobe acquires DemDex, Inc. with the intention of adding DemDex's audience-optimization software to the Adobe Online Marketing Suite (Adobe News, 2011). |
| 2009 |
Adobe acquires online marketing and web analytics company Omniture for $1.8 billion and integrates its products into the Adobe Marketing Cloud (Zippia, 2022). |
|
Adobe platform launches in December 1982. |
|
Strengths:
Areas to Improve:
| 2021 |
Microsoft Dynamics 365 suite adds customer journey orchestration as a viable key feature (Tech Target, 2021) |
|---|---|
| 2019 |
Microsoft begins adding to its Dynamics 365 suite in April 2019 with new functionalities such as virtual agents, fraud detection, new mixed reality (Microsoft Dynamics 365 Blog, 2019). |
|
2017 |
Adobe and Microsoft expand key partnership between Adobe Experience Manager and Dynamics 365 integration (TechCrunch, 2017). |
|
2016 |
Microsoft Dynamics CRM paid seats begin growing steadily at more than 2.5x year-over-year (TechCrunch, 2016). |
|
2016 |
On-premises application, called Dynamics 365 Customer Engagement, contains the Dynamics 365 Marketing Management platform (Learn Microsoft, 2023). |
|
Microsoft Dynamics 365 product suite is released on November 1, 2016. |
|
"Microsoft Dynamics 365 for Marketing remains a viable option for organizations that require a range of innovative MMS tools that can provide a wealth of functional capabilities (e.g. AI-powered analytics to create targeted segments, A/B testing, personalizing engagement for each customer). Moreover, Microsoft Dynamics 365 for Marketing offers trial options to sandbox their platform for free for 30 days to help users familiarize themselves with the software before buying into the product suite.
However, ensure that you have the time to effectively train users on implementing the MS Dynamics 365 platform. The platform does not score high on customizability in SoftwareReviews reports. Developers have only a limited ability to modify the core UI, so organizations need to be fully equipped with the knowledge needed to successfully navigate MS-based applications to take full advantage of the platform. For organizations deep in the Microsoft stack, D365 Marketing is a compelling option."
Yaz Palanichamy
Senior Research Analyst, Info-Tech Research Group
|
Dynamics 365 |
Dynamics 365 |
|---|---|
|
|
* Pricing correct as of October 2022. Listed in USD and absent discounts. See pricing on vendor's website for latest information.
Strengths:
Areas to Improve:
|
2022 |
HubSpot Marketing Hub releases Campaigns 2.0 module for its Marketing Hub platform (HubSpot, 2022). |
|---|---|
|
2018 |
|
|
2014 |
HubSpot celebrates its first initial public offering on the NYSE market (HubSpot Company News, 2014). |
|
2013 |
HubSpot opens its first international office location in Dublin, Ireland |
|
2010 |
Brian Halligan and Dharmesh Shah write "Inbound Marketing," a seminal book that focuses on inbound marketing principles (HubSpot, n.d.). |
|
HubSpot opens for business in Cambridge, MA, USA, in 2005. |
|
"HubSpot's Marketing Hub software ranks consistently high in scores across SoftwareReviews reports and remains a strong choice for organizations that want to run successful inbound marketing campaigns that make customers interested and engaged with their business. HubSpot Marketing Hub employs comprehensive feature sets, including the option to streamline ad tracking and management, perform various audience segmentation techniques, and build personalized and automated marketing campaigns.
However, SoftwareReviews reports indicate end users are concerned that HubSpot Marketing Hub's platform may be slightly overpriced in recent years and not cost effective for smaller and mid-sized companies that are working with a limited budget. Moreover, when it comes to mobile user accessibility reports, HubSpot's Marketing Hub does not directly offer data usage reports in relation to how mobile users navigate various web pages on the customer's website."
Yaz Palanichamy
Senior Research Analyst, Info-Tech Research Group
|
HubSpot Marketing Hub (Starter Package) |
HubSpot Marketing Hub (Professional Package) |
HubSpot Marketing Hub (Enterprise Package) |
|---|---|---|
|
|
|
*Pricing correct as of October 2022. Listed in USD and absent discounts.
See pricing on vendor's website for latest information.
Strengths:
Areas to Improve:
2022 | Maropost acquires Retail Express, leading retail POS software in Australia for $55M (PRWire, 2022). |
2018 |
|
2015 | US-based communications organization Success selects Maropost Marketing Cloud for marketing automation use cases (Apps Run The World, 2015). |
2017 | Maropost is on track to become one of Toronto's fastest-growing companies, generating $30M in annual revenue (MarTech Series, 2017). |
2015 | Maropost is ranked as a "High Performer" in the Email Marketing category in a G2 Crowd Grid Report (VentureBeat, 2015). |
Maropost is founded in 2011 as a customer-centric ESP platform. | |
|
Maropost Marketing Cloud – Essential |
Maropost |
Maropost |
|---|---|---|
|
|
|
*Pricing correct as of October 2022. Listed in USD and absent discounts.
See pricing on vendor's website for latest information.
Strengths:
Areas to Improve:
2021 | New advanced intelligence capabilities within Oracle Eloqua Marketing Automation help deliver more targeted and personalized messages (Oracle, Marketing Automation documentation). |
2015 |
|
2014 | Oracle announces the launch of the Oracle Marketing Cloud (TechCrunch, 2014). |
2005 | Oracle acquires PeopleSoft, a company that produces human resource management systems, in 2005 for $10.3B (The Economic Times, 2016). |
1982 | Oracle becomes the first company to sell relational database management software (RDBMS). In 1982 it has revenue of $2.5M (Encyclopedia.com). |
Relational Software, Inc (RSI) – later renamed Oracle Corporation – is founded in 1977. | |
"Oracle Marketing Cloud offers a comprehensive interwoven and integrated marketing management solution that can help end users launch cross-channel marketing programs and unify all prospect and customer marketing signals within one singular view. Oracle Marketing Cloud ranks consistently high across our SoftwareReviews reports and sustains top scores in overall customer experience rankings at a factor of 9.0. The emotional sentiment of users interacting with Oracle Marketing Cloud is also highly favorable, with Oracle's Emotional Footprint score at +93.
Users should be aware that some of the reporting mechanisms and report-generation capabilities may not be as mature as those of some of its competitors in the MMS space (e.g. Salesforce, Adobe). Data exportability also presents a challenge in Oracle Marketing Cloud and requires a lot of internal tweaking between end users of the system to function properly. Finally, pricing sensitivity may be a concern for small and mid-sized organizations who may find Oracle's higher-tiered pricing plans to be out of reach. "
Yaz Palanichamy
Senior Research Analyst, Info-Tech Research Group
| Oracle Marketing Cloud pricing is opaque. Request a demo.* |
*Info-Tech recommends reaching out to the vendor's internal sales management team for explicit details on individual pricing plans for the Adobe Marketing Cloud suite.
Strengths:
Areas to Improve:
2022 | Salesforce announces sustainability as a core company value (Forbes, 2022). |
2012 |
|
2009 | Salesforce launches Service Cloud, bringing customer service and support automation features to the market (TechCrunch, 2009). |
2003 |
|
2001 |
|
Salesforce is founded in 1999. | |
"Salesforce Marketing Cloud is a long-term juggernaut of the marketing management software space and is the subject of many Info-Tech member inquiries. It retains strong composite and customer experience (CX) scores in our SoftwareReviews reports. Some standout features of the platform include marketing analytics, advanced campaign management functionalities, email marketing automation, and customer journey management capabilities. In recent years Salesforce has made great strides in improving the overall user experience by investing in new product functionalities such as the Einstein What-If Analyzer, which helps test how your next email campaign will impact overall customer engagement, triggers personalized campaign messages based on an individual user's behavior, and uses powerful real-time segmentation and sophisticated AI to deliver contextually relevant experiences that inspire customers to act.
On the downside, we commonly see Salesforce's solutions as costlier than competitors' offerings, and its commercial/sales teams tend to be overly aggressive in marketing its solutions without a distinct link to overarching business requirements. "
Yaz Palanichamy
Senior Research Analyst, Info-Tech Research Group
|
Marketing Cloud Basics |
Marketing Cloud Pro |
Marketing Cloud Corporate |
Marketing Cloud Enterprise |
|---|---|---|---|
|
|
|
"Request a Quote" |
*Pricing correct as of October 2022. Listed in USD and absent discounts. See pricing on vendor's website for latest information.
Strengths:
Areas to Improve:

2022 | SAP announces the second cycle of the 2022 SAP Customer Engagement Initiative. (SAP Community Blog, 2022). |
2020 | SAP acquires Austrian cloud marketing company Emarsys (TechCrunch, 2020). |
2015 | SAP Digital for Customer Engagement launches in May 2015 (SAP News, 2015). |
2009 | SAP begins branching out into three markets of the future (mobile technology, database technology, and cloud). SAP acquires some of its competitors (e.g. Ariba, SuccessFactors, Business Objects) to quickly establish itself as a key player in those areas (SAP, n.d.). |
1999 | SAP responds to the internet and new economy by launching its mysap.com strategy (SAP, n.d.). |
SAP is founded In 1972. | |
"Over the years, SAP has positioned itself as one of the usual suspects across the enterprise applications market. While SAP has a broad range of capabilities within the CRM and customer experience space, it consistently underperforms in many of our user-driven SoftwareReviews reports for MMS and adjacent areas, ranking lower in MMS product feature capabilities such as email marketing automation and advanced campaign management than other mainstream MMS vendors, including Salesforce Marketing Cloud and Adobe Experience Cloud. The SAP Customer Engagement Marketing platform seems decidedly a secondary focus for SAP, behind its more compelling presence across the enterprise resource planning space.
If you are approaching an MMS selection from a greenfield lens and with no legacy vendor baggage for SAP elsewhere, experience suggests that your needs will be better served by a vendor that places greater primacy on the MMS aspect of their portfolio."
Yaz Palanichamy
Senior Research Analyst, Info-Tech Research Group
|
SAP Customer Engagement Marketing pricing is opaque: |
|---|
*Info-Tech recommends reaching out to the vendor's internal sales management team for explicit details on individual pricing plans for the Adobe Marketing Cloud suite.
Strengths:
Areas to Improve:
Strengths:
Areas to Improve:
|
2021 |
Zoho announces CRM-Campaigns sync (Zoho Campaigns Community Learning, 2021). |
|
2020 |
Zoho reaches more than 50M customers in January ( Zippia, n.d.). |
|
2017 |
Zoho launches Zoho One, a comprehensive suite of 40+ applications (Zoho Blog, 2017). |
|
2012 |
Zoho releases Zoho Campaigns (Business Wire, 2012). |
|
2007 |
Zoho expands into the collaboration space with the release of Zoho Docs and Zoho Meetings (Zoho, n.d.). |
|
2005 |
Zoho CRM is released (Zoho, n.d.). |
|
Zoho platform is founded in 1996. |
|
"Zoho maintains a long-running repertoire of end-to-end software solutions for business development purposes. In addition to its flagship CRM product, the company also offers Zoho Campaigns, which is an email marketing software platform that enables contextually driven marketing techniques via dynamic personalization, email interactivity, A/B testing, etc. For organizations that already maintain a deep imprint of Zoho solutions, Zoho Campaigns will be a natural extension to their immediate software environment.
Zoho Campaigns is a great ecosystem play in environments that have a material Zoho footprint. In the absence of an existing Zoho environment, it's prudent to consider other affordable products as well."
Yaz Palanichamy
Senior Research Analyst, Info-Tech Research Group
|
Free Version |
Standard |
Professional |
|---|---|---|
|
|
|
*Pricing correct as of October 2022. Listed in USD and absent discounts.
See pricing on vendor's website for latest information.
|
1. Assess |
|---|
|
2. Prepare |
|
3. Govern & Course Correct |
Download Info-Tech's Governance and Management of Enterprise Software Implementation
Establish and execute an end-to-end, agile framework to succeed with the implementation of a major enterprise application.
Teams must have some type of communication strategy. This can be broken into:
Distributed teams create complexity as communication can break down. This can be mitigated by:
Members should trust other members are contributing to the project and completing their required tasks on time. Trust can be developed and maintained by:
This selection guide allows organizations to execute a structured methodology for picking an MMS platform that aligns with their needs. This includes:
This formal MMS selection initiative will drive business-IT alignment, identify pivotal sales and marketing automation priorities, and thereby allow for the rollout of a streamlined MMS platform that is 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
Knowledge Gained
Processes Optimized
Marketing Management
Vendors Analyzed
Select a Marketing Management Suite
Many organizations struggle with taking a systematic approach to selection that pairs functional requirements with specific marketing workflows, and as a result they choose a marketing management suite (MMS) that is not well aligned to their needs, wasting resources and causing end-user frustration.
Customer relationship management (CRM) application portfolios are often messy,
with multiple integration points, distributed data, and limited ongoing end-user training. A properly optimized CRM ecosystem will reduce costs and increase productivity.
Customer Relationship Management Platform Selection Guide
Speed up the process to build your business case and select your CRM solution. 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.
"16 Biggest Tech Acquisitions in History." The Economic Times, 28 July 2016. Web.
"Adobe Acquires Demdex – Brings Audience Optimization to $109 Billion Global Online Ad Market." Adobe News, 18 Jan 2011. Accessed Nov 2022.
"Adobe Company History Timeline." Zippia, 9 Sept 2022. Accessed Nov 2022.
"Adobe to acquire Magento for $1.68B." TechCrunch, 21 May 2018. Accessed Dec 2022.
Anderson, Meghan Keaney. "HubSpot Launches European Headquarters." HubSpot Company News, 3 Mar 2013.
Arenas-Gaitán, Jorge, et al. "Complexity of Understanding Consumer Behavior from the Marketing Perspective." Journal of Complexity, vol. 2019, 8 Jan 2019. Accessed Sept 2022.
Bureau of Labor Statistics. "Advertising, Promotions, and Marketing Managers." Occupational Outlook Handbook. U.S. Department of Labor, 8 Sept 2022. Accessed 1 Nov 2022.
"Campaigns." Marketing Hub, HubSpot, n.d. Web.
Conklin, Bob. "Adobe report reveals best marketing practices for B2B growth in 2023 and beyond." Adobe Experience Cloud Blog, 23 Sept 2022. Web.
"Consumer Behavior Stats 2021: The Post-Pandemic Shift in Online Shopping Habit" Nosto.com, 7 April 2022. Accessed Oct 2022.
"Data Collection Overview." Experience League, Adobe.com, n.d. Accessed Dec 2022.
Duduskar, Avinash. "Interview with Tony Chen, CEO at Channel Factory." MarTech Series, 16 June 2017. Accessed Nov 2022.
"Enhanced Release of SAP Digital for Customer Engagement Helps Anyone Go Beyond CRM." SAP News, 8 Dec. 2015. Press release.
Fang, Mingyu. "A Deep Dive into Gucci's Metaverse Practice." Medium.com, 27 Feb 2022. Accessed Oct 2022.
Flanagan, Ellie. "HubSpot Launches Marketing Hub Starter to Give Growing Businesses the Tools They Need to Start Marketing Right." HubSpot Company News, 17 July 2018. Web.
Fleishman, Hannah. "HubStop Announces Pricing of Initial Public Offering." HubSpot Company News, 8 Oct. 204. Web.
Fluckinger, Don. "Adobe to acquire Workfront for $1.5 billion." TechTarget, 10 Nov 2020. Accessed Nov 2022.
Fluckinger, Don. "Microsoft Dynamics 365 adds customer journey orchestration." TechTarget, 2 March 2021. Accessed Nov 2022.
Green Marketing: Explore the Strategy of Green Marketing." Marketing Schools, 19 Nov 2020. Accessed Oct 2022.
Ha, Anthony. "Oracle Announces Its Cross-Platform Marketing Cloud." TechCrunch, 30 April 2014. Web.
Heyd, Kathrin. "Partners Welcome – SAP Customer Engagement Initiative 2022-2 is open for your registration(s)!" SAP Community Blog, 21 June 2022. Accessed Nov 2022.
HubSpot. "Our Story." HubSpot, n.d. Web.
Jackson, Felicia. "Salesforce Tackles Net Zero Credibility As It Adds Sustainability As A Fifth Core Value." Forbes, 16 Feb. 2022. Web.
Kolakowski, Nick. "Salesforce CEO Marc Benioff Talks Social Future." Dice, 19 Sept. 2012. Web.
Lardinois, Frederic. "Microsoft's Q4 earnings beat Street with $22.6B in revenue, $0.69 EPS." TechCrunch, 19 July 2016. Web.
Levine, Barry. "G2 Crowd report finds the two email marketing tools with the highest user satisfaction." Venture Beat, 30 July 2015. Accessed Nov 2022.
Looking Back, Moving Forward: The Evolution of Maropost for Marketing." Maropost Blog, 21 May 2019. Accessed Oct 2022.
Maher, Sarah. "What's new with HubSpot? Inbound 2022 Feature Releases." Six & Flow, 9 July 2022. Accessed Oct 2022.
Marketing Automation Provider, Salesfusion, Continues to Help Marketers Achieve Their Goals With Enhanced User Interface and Powerful Email Designer Updates." Yahoo Finance, 10 Dec 2013. Accessed Oct 2022.
"Maropost Acquires Retail Express for $55 Million+ as it Continues to Dominate the Global Commerce Space." Marapost Newsroom, PRWire.com, 19 Jan 2022. Accessed Nov 2022.
McDowell, Maghan. "Inside Gucci and Roblox's new virtual world." Vogue Business, 17 May 2021. Web.
Miller, Ron. "Adobe and Microsoft expand partnership with Adobe Experience Manager and Dynamics 265 Integration." TechCrunch, 3 Nov 2017. Accessed Nov 2022.
Miller, Ron. "Adobe to acquire Magento for $1.68B" TechCrunch, 21 May 2018. Accessed Nov 2022.
Miller, Ron. "SAP continues to build out customer experience business with Emarys acquisition." TechCrunch, 1 Oct. 2020. Web.
Miller, Ron. "SugarCRM moves into marketing automation with Salesfusion acquisition." TechCrunch, 16 May 2019.
Novet, Jordan. "Adobe confirms it's buying Marketo for $4.75 billion." CNBC, 20 Sept 2018. Accessed Dec 2022.
"Oracle Corp." Encyclopedia.com, n.d. Web.
Phillips, James. "April 2019 Release launches with new AI, mixed reality, and 350+ feature updates." Microsoft Dynamics 365 Blog. Microsoft, 2 April 2019. Web.
S., Aravindhan. "Announcing an important update to Zoho CRM-Zoho Campaigns integration." Zoho Campaigns Community Learning, Zoho, 1 Dec. 2021. Web.
Salesforce. "The History of Salesforce." Salesforce, 19 March 2020. Web.
"Salesfusion Integrates With NetSuite CRM to Simplify Sales and Marketing Alignment" GlobeNewswire, 6 May 2016. Accessed Oct 2022. Press release.
"Salesfusion Integrates With NetSuite CRM to Simplify Sales and Marketing Alignment." Marketwired, 6 May 2016. Web.
"Salesfusion is Now Sugar Market: The Customer FAQ." SugarCRM Blog, 31 July 2019. Web.
"Salesfusion's Marketing Automation Platform Drives Awareness and ROI for Education Technology Provider" GlobeNewswire, 25 June 2015. Accessed Nov 2022. Press release.
SAP. "SAP History." SAP, n.d. Web.
"State of Marketing." 5th Edition, Salesforce, 15 Jan 2019. Accessed Oct 2022.
"Success selects Maropost Marketing Cloud for Marketing Automation." Apps Run The World, 10 Jan 2015. Accessed Nov 2022.
"SugarCRM Acquires SaaS Marketing Automation Innovator Salesfusion." SugarCRM, 16 May 2019. Press release.
Sundaram, Vijay. "Introducing Zoho One." Zoho Blog, 25 July 2017. Web.
"The State of MarTech: Is you MarTech stack working for you?" American Marketing Association, 29 Nov 2021. Accessed Oct 2022.
"Top Marketing Automation Statistics for 2022." Oracle, 15 Jan 2022. Accessed Oct 2022.
Trefis Team. "Oracle Energizes Its Marketing Cloud With New Features." Forbes, 7 April 2015. Accessed Oct 2022.
Vivek, Kumar, et al. "Microsoft Dynamics 365 Customer Engagement (on-premises) Help, version 9.x." Learn Dynamics 365, Microsoft, 9 Jan 2023. Web.
"What's new with HubSpot? Inbound 2022 feature releases" Six and Flow, 9 July 2022. Accessed Nov 2022.
Widman, Jeff. "Salesforce.com Launches The Service Cloud,, A Customer Service SaaS Application." TechCrunch, 15 Jan. 2009. Web.
"Zoho History." Zippia, n.d. Web.
"Zoho Launches Zoho Campaigns." Business Wire, 14 Aug. 2012. Press release.
Zoho. "About Us." Zoho, n.d. Web.
40 Hours of Advisory Assistance Delivered On-Line or In-Person
Select Better Software, Faster.
40 Hours of Expert Analyst Guidance
Project & Stakeholder Management Assistance
Save money, align stakeholders, Speed up the process & make better decisions.
Better, faster results, guaranteed, $25K standard engagement fee
CLICK HERE to book your Workshop Engagement
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Equip managers to become more effective with managing remote teams.
The workbook serves as a reference guide participants will use to support formal training.
Many organizations are developing plans to allow employees more flexible work options, including remote work. Use these resources to help managers and employees make the most of remote work arrangements.
Describe the benefits of virtual teams.
Create a plan for adopting effective management practices and setting clear expectations with virtual teams.
Identify potential solutions to the challenges of managing performance and developing members of virtual teams.
Create an action plan to increase effectiveness in managing virtual teams.
People managers who manage or plan to manage virtual teams.
Two three-hour sessions
|
Section 1 |
Section 2 |
||
|---|---|---|---|
| 10 min |
Welcome: Overview & Introductions
|
10 min |
Welcome: Overview & Introductions
|
| 50 min |
1.1 Introduction to virtual teams
|
55 min |
2.1 Managing wellbeing in a virtual team context
|
| 5 min |
Break |
5 min | Break |
| 45 min |
1.2 Laying the foundation for a virtual team
|
60 min |
2.2 Managing performance in a virtual team context
|
| 10 min |
Break |
10 min | Break |
| 55 min |
1.2 Laying the foundation for a virtual team
|
40 min |
Action planning & conclusion
|
| 5 min |
Session 1 Wrap-Up |
||
Review all slides and adjust the language or content as needed to suit your organizational context and culture.
The pencil icon to the left denotes slides requiring customization of the slide and/or the speaker’s notes, e.g. adding in an organization-specific process.
Customization instructions are found in the notes pane.
Practical foundations for managing teams in a remote environment
Most organizations are planning some combination of remote and onsite work in 2022.
Source: IT Talent Trends, 2022; n=199
Most organizations are planning some combination of remote and onsite work in 2022 – the highest reported plans for WFH were hybrid, balanced, and partial work-from-home. This builds on our findings in the IT Talent Trends 2022 report.
What percentage of roles in IT are capable of being performed remotely permanently?
IT Talent Trends, 2022; n=207
80% of respondents estimated that 50 to 100% of IT roles can be performed remotely.
A virtual team is any team that has members that are not colocated and relies on technology for communications.
Before we start, it will be useful to review what we mean by the term “virtual team.” For our purposes we will be defining a virtual team as any team that has members that are not colocated and relies on technology for communications.
There are a wide variety of virtual work arrangements and a variety of terms used to describe them. For example, some common terms include:
Our definition of virtual work covers all of these terms. It is also distance neutral, meaning that it applies equally to teams that are dispersed globally or regionally or even those working in the same cities but dispersed throughout different buildings. Our definition also applies whether virtual employees work full time or part time.
The challenges facing managers arise as soon as some team members are not colocated and have to rely on technology to communicate and coordinate work. Greater distances between employees can complicate challenges (e.g. time zone coordination), but the core challenges of managing virtual teams are the same whether those workers are merely located in different buildings in the same city or in different buildings on different continents.
Working on your own, take five minutes to figure out what kind of virtual team you lead.
Download the Workbook: Equip Managers to Effectively Manage Virtual Teams
|
Benefits to the organization |
Benefits to employees |
|---|---|
|
Operational continuity in disaster situations that prevent employees from coming into the office. |
Cost savings: Employees who WFH half the time can save $2,500 to $4,000 per year (Global Workplace Analytics, 2021). |
|
Cost savings: Organizations save ~$11,000 annually per employee working from home half the time (Global Workplace Analytics, 2021). |
Time savings: Employees who WFH half the time save on average 11 workdays per year (Global Workplace Analytics, 2021). |
|
Increased attraction: 71% of employees would likely choose one employer over another based on WFH offerings (Owl Labs, 2021). |
Improved wellbeing: 83% employees agree that WFH would make them happier. 80% agree that WFH would decrease their stress. 81% agree that WFH would improve their ability to manage their work-life balance. (Owl Labs, 2021) |
|
Increased retention: 74% of employees would be less likely to leave their employer if they could WFH (Owl Labs, 2021). |
Increased flexibility: 32% of employees rated the “ability to have a flexible schedule” as the biggest benefit of WFH (OWL Labs, 2021). |
|
Increased productivity: 50% of employees report they would maintain or increase their productivity while working from home (Glassdoor Team, 2020). |
|
|
Increased engagement: Offsite employees tend to have higher overall engagement than onsite employees (McLean & Company Engagement Survey, 2020). |
Remote work arrangements are becoming more and more common, and for good reason: there are a lot of benefits to the organization – and to employees.
Perhaps one of the most common reasons for opting for remote-work arrangements is the potential cost savings. One study found that organizations could save about $11,000 per employee working from home half the time (Global Workplace Analytics, 2021).
In addition, supporting remote-work arrangements can attract employees. One study found that 71% of employees would likely choose one employer over another based on WFH offerings (Owl Labs, 2019).
There are also improvements to productivity. Fifty percent of employees report they would maintain or increase their productivity while working from home (Glassdoor Team, 2020).
Remote work also has benefits to employees.
As with organizations, employees also benefit financially from remote work arrangements, saving between $2,500 and $4,000 and on average 11 working days while working from home half of the time.
Most employees agree that working from home makes them happier, reduces stress, and provides an improved work-life balance through increased flexibility.
Many of these barriers can be addressed by changing traditional mindsets and finding alternative ways of working, but the traditional approach to work is so entrenched that it has been hard to make the shift.
Many organizations are still grappling with the challenges of remote work. Some are just perceived challenges, while others are quite real.
Limited innovation and a lack of informal interaction are a potential consequence of failing to properly adapt to the remote-work environment.
Leaders also face challenges with remote work. Losing in-person supervision has led to the lack of trust and a perceived drop in productivity.
A study conducted 2021 asked remote workers to identify their biggest struggle with working remotely. The top three struggles remote workers report facing are unplugging after work, loneliness, and collaborating and/or communicating.
Seeing the struggles remote workers identify is a good reminder that these employees have a unique set of challenges. They need their managers to help them set boundaries around their work; create feelings of connectedness to the organization, culture, and team; and be expert communicators.
Download the Workbook: Equip Managers to Effectively Manage Virtual Teams
Laying the foundations for a virtual team
|
Inform |
Interact | Involve |
|---|---|---|
|
↓ Down |
Connect |
↑ Up |
|
Tell employees the whys |
Get to know employees |
Solicit input from employees |
Effectively managing a virtual team really comes down to adopting management approaches that will engage virtual employees.
Managing a virtual team does not actually require a new management style. The basics of effective management are the same in both colocated and virtual teams; however, the emphasis on certain behaviors and actions we take often differs. Managing a virtual team requires much more thoughtfulness and planning in our everyday interactions with our teams as we cannot rely on the relative ease of face-to-face interactions available to colocated teams.
The 3i’s Engaging Management Model is useful when interacting with all employees and provides a handy framework for more planful interactions with virtual employees.
Think of your management responsibilities in these three buckets – they are the most important components of being an effective manager. We’re first going to look at inform and involve before moving on to interact.
Inform: Relay information down from senior management and leaders to employees. Communicate the rationale behind decisions and priorities, and always explain how they will directly affect employees.
Why is this important? According to McLean & Company’s Engagement Survey data, employees who say their managers keep them well informed about decisions that affect them are 3.4 times more likely to be engaged (Source: McLean & Company, 2020; N=77,363). Your first reaction to this might be “I already do this,” which may very well be the case. Keep in mind, though, we sometimes tend to communicate on a “need-to-know basis,” especially when we are stressed or short on time. Engaging employees takes more. Always focus on explaining the “why?” or the rationale behind business decisions.
It might seem like this domain should be the least affected, since important company announcements probably continue in a remote environment. But remember that information like that also flows informally. And even in formal settings, there are question-and-answer opportunities. Or maybe your employee might come to your office to ask for more details. Virtual team members can’t gather around the watercooler. They don’t have the same opportunities to hear information in passing as people who are colocated do, so managers need to make a concerted effort to share information with virtual team members in a clear and timely way.
Swinging over to the other end, we have involve: Involve your employees. Solicit information and feedback from employees and collaborate with them.
However, it’s not enough to just solicit their feedback and input; you also need to act on it.
Make sure you involve your employees in a meaningful way. Such collaboration makes employees feel like a valued part of the team. Not to mention that they often have information and perspectives that can help make your decisions stronger!
Employees who say their department leaders act on feedback from them are 3.9 times more likely to be engaged than those whose leaders don’t. (Source: McLean & Company, 2020; N=59,779). That is a huge difference!
Keeping virtual employees engaged and feeling connected and committed to the organization requires planful and regular application of the 3i’s model.
Finally, Interact: Connect with employees on a personal level; get to know them and understand who they are on a personal and professional level.
Why? Well, over and above the fact that it can be rewarding for you to build stronger relationships with your team, our data shows that human connection makes a significant difference with employees. Employees who believe their managers care about them as a person are 3.8 times more likely to be engaged than those who do not (Source: McLean & Company, 2017; N=70,927).
And you might find that in a remote environment, this is the area that suffers the most, since a lot of these interactions tend to be unscripted, unscheduled, and face to face.
Typically, if we weren’t in the midst of a pandemic, we’d emphasize the importance of allocating some budget to travel and get some face-to-face time with your staff. Meeting and interacting with team members face to face is crucial to building trusting relationships, and ultimately, an effective team, so given the context of our current circumstances, we recommend the use of video when interacting with your employees who are remote.
Relay information down from senior management to employees.
Ensure they’ve seen and understand any organization-wide communication.
Share any updates in a timely manner.
Connect with employees on a personal level.
Ask how they’re doing with the new work arrangement.
Express empathy for challenges (sick family member, COVID-19 diagnosis, etc.).
Ask how you can support them.
Schedule informal virtual coffee breaks a couple of times a week and talk about non-work topics.
Get information from employees and collaborate with them.
Invite their input (e.g. have a “winning remotely” brainstorming session).
Escalate any challenges you can’t address to your VP.
Give them as much autonomy over their work as possible – don’t micromanage.
Download the Workbook: Equip Managers to Effectively Manage Virtual Teams
Clear expectations are important in any environment, remote or not. But it is much harder to do in a remote environment. The barrier to seeking clarification is so much higher (For example, email vs. catching someone in hallway, or you can’t notice that a colleague is struggling without them asking).
Communication – This is one area where the importance actually changes in a remote context. We’ve been talking about a lot of practices that are the same in importance whether you’re in an office or remote, and maybe you just enact them differently. But clarity around communication processes is actually tremendously more important in a remote environment.
Suggested best practices: Hold daily team check-ins and hold separate individual check-ins. Increase frequency of these.
With organizational expectations set, we need to establish team expectations around how we collaborate and communicate.
Today there is no lack of technology available to support our virtual communication. We can use the phone, conference calls, videoconferencing, Skype, instant messaging, [insert organization-specific technological tools.], etc.
However, it is important to have a common understanding of which tools are most appropriate when and for what.
What are some of the communication channel techniques you’ve found useful in your informal interactions with employees or that you’ve seen work well between employees?
[Have participants share any technological tools they find useful and why.]
Whenever we interact, we make the following kinds of social exchanges. We exchange:
We need to make sure that these exchanges are happening as each team member intends. To do this, we have to be sensitive to what information is being conveyed, what emotions are involved in the interaction, and how we are motivating each other to act through the interaction. Every interaction will have intended and unintended effects on others. No one can pay attention to all of these aspects of communication all the time, but if we develop habits that are conducive to successful exchanges in all three areas, we can become more effective.
In addition to being mindful of the exchange in our communication, as managers it is critical to build trusting relationships and rapport with employees as we saw in the 3i's model. However, in virtual teams we cannot rely on running into someone in the kitchen or hallway to have an informal conversation. We need to be thoughtful and deliberate in our interactions with employees. We need to find alternative ways to build these relationships with and between employees that are both easy and accepted by ourselves and employees. Because of that, it is important to set communication norms and really understand each other’s preferences. For example:
Download the Workbook: Equip Managers to Effectively Manage Virtual Teams
Section 2.1
Balancing wellbeing and performance in a virtual team context
44% of employees reported declined mental wellbeing since the start of the pandemic.
"If one of our colleagues were to fall, break their leg, and get a cast, colleagues would probably rally around that person signing their cast. But, really, we don’t view the health of our brain the same as we do the health of our body."
– Centre for Addiction and Mental Health (CAMH) Employee
Despite being over two years into the pandemic, we are still seeing its effect on the physical and mental health of employees.
The mental health aspect has been often overlooked by organizations, but in order to have a safe, happy, and productive team, you need to give mental health the same level of focus as physical heath. This requires a change in mindset in order for you as a leader to support your team's mental wellbeing during the pandemic and beyond.
Employees report increasingly high levels of stress from the onset of COVID-19, stating that it has been the most stressful time in their careers.
(Qualtrics, 2020)
Similarly, employees’ anxiety levels have peaked because of the pandemic and the uncertainty it brings.
(Qualtrics, 2020)
The stress and uncertainty about the future caused by the pandemic and its fallout are posing the biggest challenges to employees.
Organizations shutting down operations, moving to fully remote, or requiring some of their employees to be on site based on the current situation causes a lot of anxiety as employees are not able to plan for what is coming next.
Adding in the loss of social networks and in-person interactions exacerbates the problem employees are facing. As leaders, it is your job to understand and mitigate these challenges wherever possible.
|
New Barriers |
Old Barriers |
|---|---|
|
|
Organizational barriers to mental wellbeing are sadly not new. Workloads, stigma around mental health, lack of sick days, and limits to benefits for mental health supports were challenges before the pandemic. Adding in the new barriers can very easily result in a tipping point for many employees who are simply not equipped to deal with or supported in dealing with the added burden of remote work in a post-pandemic world.
To provide the needed support to your employees, it’s important to be mindful of the key considerations.
The physical body; ensuring a person has the freedom, opportunities, and resources needed to sustainably maintain bodily health.
The psychological ability to cope with information, emotions, desires, and stressors (e.g. change, threats, etc.) in a healthy and balanced way. Essential for day-to-day living and functioning.
The state of personal and professional relationships, including personal and community engagement. The capability for genuine, authentic, and mutually affirming interactions with others.
The state of a person’s finances; ensuring that a person feels capable to handle their financial situation and behaviors. The ability to live productively without the weight of financial stress.
As a manager, you need to be mindful of all of these. Create an atmosphere where people are able to come to you for help if they are struggling in one of these areas. For example, some people might be more comfortable raising physical safety or comfort concerns (personal protective equipment, ergonomics) than concerns about mental health. Or they might feel like their feelings of loneliness are not appropriate to bring into their professional life.
Wellbeing is a delicate subject, and most of the time, people are reluctant to talk about it. It requires vulnerability. And here’s the thing about it: Your staff will not drive a change in your team around making these topics more acceptable. It has to be the manager. You have to be the one to not just tell but show them that it’s OK to talk about this
As a leader, your focus should be on encouraging the right behaviors on your team and in yourself.
Show empathy; allowing room for emotion and showing you are willing and able to listen goes a long way to establishing trust.
A growth mindset applies to resilience too. A person with a growth mindset is more likely to believe that even though they’re struggling now, they will get through it.
Infuse fun – schedule social check-ins. This is not wasted time, or time off work – it is an integral part of the workday. We have less of it now organically, so you must bring it back deliberately. Remember that theme? We are deliberately reinfusing important organic elements into the workday.
The last item, empowerment, is interesting – being clear on accountability. Have clear performance expectations. It might sound like telling people what to do would be disempowering, but it’s the opposite. By clarifying the goals of what they need to achieve, you empower them to invent their own “how,” because you and they are both sure they will arrive at the place that you agreed on. We will talk more about this in performance management.
Emphasize the importance of wellbeing with what you do. If you do not model self-care behavior, people will follow what you do, not what you say.
Lead by example – Live the behaviors you want to see in your employees. If you show confidence, positivity, and resiliency, it will filter down to your team.
Encourage open communication – Have regular meetings where your team is able to set the agenda, or allow one-on-ones to be guided by the employee. Make sure these are scheduled and keep them a priority.
Acknowledge the situation – Pretending things are normal doesn’t help the situation. Talk about the stress that the team is facing and express confidence that you will get through it together.
Promote wellbeing – Take time off, don’t work when you’re sick, and you will be better able to support your team!
Reduce stigma – Call it out when you see it and be sure to remind people of and provide access to any supports that the organization has.
Going back to the idea of a growth mindset – this may be uncomfortable for you as a manager. So here’s a step-by-step guide that over time you can morph into your own style.
With your team – be prepared to share first and to show it is OK to be vulnerable and address wellbeing seriously.

As a leader, it is important to be on the lookout for warning signs of burnout and know when to step in and direct individuals to professional help.
Poor work performance – They struggle to maintain work performance, even after you’ve worked with them to create coping strategies.
Overwhelmed – They repeatedly tell you that they feel overwhelmed, very stressed, or physically unwell.
Frequent personal disclosure – They want to discuss their personal struggles at length on a regular basis.
Trouble sleeping and focusing – They tell you that they are not sleeping properly and are unable to focus on work.
Frequent time off – They feel the need to take time off more frequently.
Strained relationships – They have difficulty communicating effectively with coworkers; relationships are strained.
Substance abuse – They show signs of substance abuse (e.g. drunk/high while working, social media posts about drinking during the day).
Keeping an eye out for these signs and being able to step in before they become unmanageable can mean the difference between keeping and losing an employee experiencing burnout.
If you’ve got managers under you, be mindful of their unique stressors. Don’t forget to check in with them, too.
If you are a manager, remember to take care of yourself and check in with your own manager about your own wellbeing.
Download the Workbook: Equip Managers to Effectively Manage Virtual Teams
A survey indicated that, overall, remote employees showed less satisfaction with manager interactions compared to other non-remote employees.
In many cases, we have put people into virtual roles because they are self-directed and self-motivated workers who can thrive with the kind of autonomy and flexibility that comes with virtual work. As managers, we should expect many of these workers to be proactively interested in how they are performing and in developing their careers.
It would be a mistake to take a hands-off approach when managing virtual workers. A recent survey indicated that, overall, remote employees showed less satisfaction with manager interactions compared to other non-remote employees. It was also one of the aspects of their work experience they were least satisfied with overall (Gallup, State of the American Workplace, 2017). Simply put, virtual employees are craving more meaningful conversations with their managers.
While conversations about performance and development are important for all employees (virtual or non-virtual), managers of remote teams can have a significant positive impact on their virtual employees’ experience and engagement at work by making efforts to improve their involvement and support in these areas.
During this module we will work together to identify ways that each of us can improve how we manage the performance of our virtual employees. At the end of the module everyone will create an action plan that they can put in place with their own teams. In the next module, we go through a similar set of activities to create an action plan for our interactions with employees about their development.
[Include a visualization of your existing performance management process in the slide. Walk the participants through the process to remind them of what is expected. While the managers participating in the training should know this, there may be different understandings of it, or it might just be the case that it’s been a while since people looked at the official process. The intention here is merely to ensure everyone is on the same page for the purposes of the activities that follow.]
Now that we’ve reviewed performance management at a high level, let’s dive into what is currently happening with the performance management of virtual teams.
I know that you have some fairly extensive material at your organization around how to manage performance. This is fantastic. And we’re going to focus mainly on how things change in a virtual context.
When measuring progress, how do you as a manager make sure that you are comfortable not seeing your team physically at their desks? This is the biggest challenge for remote managers.
Download the Workbook: Equip Managers to Effectively Manage Virtual Teams
When assisting your employees with their goals, think about the organization’s overall mission and goals to help you determine team and individual goals.
Sometimes it’s difficult to get employees thinking about goals and they need assistance from managers. It’s also important to be clear on team goals to help guide employees in setting individual ones.
The basic idea is to show people how their individual day-to-day work contributes to the overall success of the organization. It gives them a sense of purpose and a rationale, which translates to motivation. And also helps them problem solve with more autonomy.
You’re giving people a sense of the importance of their own contribution.
Tailor performance goals to address any root causes of poor performance.
For example:
Focus on results: Be flexible about how and when work gets done, as long as team members are hitting their targets.
Encourage your team members to unplug: If they’re sending you emails late at night and they haven’t made an alternate work hours agreement with you, encourage them to take time away from work.
How well tasks are accomplished
Related to specific employee actions, skills, or attitudes
How much work gets done
Holistic measures demonstrate all the components required for optimal performance. This is the biggest driver in having comfort as a manager of a remote team and avoiding micromanagement. Typically these are set at the organizational level. You may need to adjust for individual roles, etc.
Metrics come in different types. One way to ensure your metrics capture the full picture is to use a mix of different kinds of metrics.
Some metrics are quantitative: they describe quantifiable or numerical aspects of the goal. This includes timeliness. On the other hand, qualitative metrics have to do with the final outcome or product. And behavioral metrics have to do with employees' actions, skills, or attitudes. Using different kinds of metrics together helps you set holistic measures, which capture all the components of optimal performance toward your goal and prevent gaming the system.
Let's take an example:
A courier might have an objective to do a good job delivering packages. An example of a quantitative measure might be that the courier is required to deliver X number of packages per day on time. The accompanying metrics would be the number of packages delivered per day and the ratio of packages delivered on time vs. late.
Can you see a problem if we use only these quantitative measures to evaluate the courier's performance?
Wait to see if anyone volunteers an answer. Discuss suggestions.
That's right, if the courier's only goal is to deliver more packages, they might start to rush, may ruin the packages, and may offer poor customer service. We can help to guard against this by implementing qualitative and behavioral measures as well. For example, a qualitative measure might be that the courier is required to deliver the packages in mint condition. And the metric would be the number of customer complaints about damaged packages or ratings on a satisfaction survey related to package condition.
For the behavioral aspect, the courier might be required to provide customer-centric service with a positive attitude. The metrics could be ratings on customer satisfaction surveys related to the courier's demeanor or observations by the manager.
It’s crucial to acknowledge that an employee might have an “off week” or need time to balance work and life – things that can be addressed with performance management (PM) techniques. Managers should move into the process for performance improvement when:
Always use video calls instead of phone calls when possible so that you don’t lose physical cues and body language.
Adding HR/your leader to a meeting invite about performance may cause undue stress. Think through who needs to participate and whether they need to be included in the invite itself.
Ensure there are no misunderstandings by setting context for each discussion and having the employee reiterate the takeaways back to you.
Don’t assume the intent behind the behavior(s) being discussed. Instead, just focus on the behavior itself.
Be sure to adhere to any relevant HR policies and support systems. Working with HR throughout the process will ensure none are overlooked.
There are a few best practices you should follow when having performance conversations:
Download the Workbook: Equip Managers to Effectively Manage Virtual Teams
As we have seen, our virtual employees crave more meaningful interactions with their managers. In addition to performance conversations, managers should also be having regular discussions with their employees about their employee development plans. One key component of these discussions is career planning. Whether you are thinking shorter term – how to become better at their current role – or longer term – how to advance beyond their current role – discussions about employee development are a great way to engage employees. Employees are ultimately responsible for creating and executing their own development plans, but managers are responsible for making sure that employees have thought through these plans and helping employees identify opportunities for executing those plans.
To help us think about our own employee development practices, identify challenges they pose when working with virtual employees, and create solutions to these challenges, it is useful to think about employee development opportunities according to three types:
According to McLean & Company, organizations should use the “70-20-10” rule as a rough guideline when working with employees to create their development plans: 10% of the plan should be dedicated to formal training opportunities, 20% to relational learning, and 70% to experiential learning. Managers should work with employees to identify their performance and career goals, ensure that their development plans are aligned with these goals, and include an appropriate mixture of all three kinds of development opportunities.
To help identify challenges and solutions, think about how virtual work arrangements will impact the employee’s ability to leverage each type of opportunity at our organization.
Here are some examples that can help us start thinking about the kinds of challenges virtual employees on our team face:
Now that we have considered some general examples of challenges and solutions, let’s look at our own employee development practices and think about the practical steps we can take as managers to improve employee development for our virtual employees.
[Customize this slide according to your organization’s own policies and processes for employee development. Provide useful images that outline this on the slide, and in these notes describe the processes/policies that are in place. Note: In some cases policies or processes may not be designed with virtual employees or virtual teams in mind. That is okay for the purposes of this training module. In the following activities participants will discuss how they apply these policies and processes with their virtual teams. If your organization is interested in adapting its policies/processes to better support virtual workers, it may be useful to record those conversations to supplement existing policies later.]
Now that we have considered some general examples of challenges and solutions, let’s look at our own employee development practices and think about the practical steps we can take as managers to improve employee development for our virtual employees.
Download the Workbook: Equip Managers to Effectively Manage Virtual Teams
Download the Workbook: Equip Managers to Effectively Manage Virtual Teams
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
First, let’s take a moment to summarize the key things we have learned today:
Is there anything that anyone has learned that is not on this list and that they would like to share with the group?
Finally, were there any challenges identified today that were not addressed?
[Note to facilitator: Take note of any challenges not addressed and commit to getting back to the participants with some suggested solutions.]
Train managers to navigate the interpersonal challenges associated with change management and develop their communication and leadership skills. Upload this LMS module into your learning management system to enable online training.
Management skills training is needed, but organizations are struggling to provide training that makes a long-term difference in the skills managers use in their day to day.
Many training programs are ineffective because they offer the wrong content, deliver it in a way that is not memorable, and are not aligned with the IT department’s business objectives.
Assess and improve remote work performance with our ready-to-use tools.
April, Richard. “10 KPIs Every Sales Manager Should Measure in 2019.” HubSpot, 24 June 2019. Web.
Banerjea, Peter. “5 Powerful Strategies for Managing a Remote Sales Team.” Badger - Maps for field sales, n.d. Web.
Bibby, Adrianne. “5 Employers’ Awesome Quotes about Work Flexibility.” FlexJobs, 9 January 2017. Web.
Brogie, Frank. “The 14 KPIs every field sales rep should strive to improve.” Repsly, 2018. Web.
Dunn, Julie. “5 smart tips for leading field sales teams.” LevelEleven, March 2015. Web.
Edinger, Scott. “How great sales leaders coach.” Forbes, 2013. Web.
“Employee Outlook: Employee Views on Working Life.” CIPD, April 2016. Web.
Hall, Becki. “The 5 biggest challenges facing remote workers (and how to solve them).” interact, 7 July 2017. Web.
Hofstede, Geert. “National Cultural Dimensions.” Hofstede Insights, 2012. Web.
“Inventory of U.S. Greenhouse Gas Emissions and Sinks: 1990-2014 (EPA 430-R-16-002).” Environmental Protection Agency (EPA), 15 April 2016.
“Latest Telecommuting Statistics.” Global Workplace Analytics, June 2021. Web.
Knight, Rebecca. “How to manage remote direct reports.” Harvard Business Review, 2015. Web.
“Rewards and Recognition: 5 ways to show remote worker appreciation.” FurstPerson, 2019. Web.
Palay, Jonathan. "How to build your sales management cadence." CommercialTribe, 22 March 2018. Web.
“Sales Activity Management Matrix.” Asian Sales Guru, 2019. Web.
Smith, Simone. “9 Things to Consider When Recognizing Remote Employees.” hppy, 2018. Web.
“State of Remote Work 2017.” OWL Labs, 2021. Web.
“State of the American Workplace.” Gallup, 2017. Web.
“Telework Savings Potential.” Global Workplace Analytics, June 2021. Web.
“The Future of Jobs Employment Trends.” World Economic Forum, 2016. Web.
“The other COVID-19 crisis: Mental health.” Qualtrics, 14 April 2020. Web.
Thompson, Dan. “The straightforward truth about effective sales leadership.” Sales Hacker, 2017. Web.
Tsipursky, Gleb. “Remote Work Can Be Better for Innovation Than In-Person Meetings.” Scientific American, 14 Oct. 2021. Web.
Walsh, Kim. “New sales manager? Follow this guide to crush your first quarter.” HubSpot, May 2019. Web.
“What Leaders Need to Know about Remote Workers: Surprising Differences in Workplace Happiness and Relationships.” TINYpulse, 2016.
Zenger, Jack, and Joe Folkman. “Feedback: The Leadership Conundrum.” Talent Quarterly: The Feedback Issue, 2015.
Anonymous CAMH Employee
Seventy-four percent of organizations do not have a formal process for capturing and retaining knowledge - which, when lost, results in decreased productivity, increased risk, and money out the door.
Successful completion of the IT knowledge transfer project will result in the following outcomes:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Minimize risk and IT costs resulting from attrition through effective knowledge transfer.
Use this template to document the knowledge transfer stakeholder power map by identifying the stakeholder’s name and role, and identifying their position on the power map.
Use this template to communicate the value and rationale for knowledge transfer to key stakeholders.
Use this tool to identify and assess the knowledge and individual risk of key knowledge holders.
Use this template to track knowledge activities, intended recipients of knowledge, and appropriate transfer tactics for each knowledge source.
Use this template as a starting point for managers to interview knowledge sources to extract information about the type of knowledge the source has.
Use this template as a starting point to build your proposed IT knowledge transfer roadmap presentation to management to obtain formal sign-off and initiate the next steps in the 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.
EXECUTIVE BRIEF
Your Challenge |
Common Obstacles |
Info-Tech’s Approach |
|---|---|---|
Seventy-four percent of organizations do not have a formal process for capturing and retaining knowledge1 which, when lost, results in decreased productivity, increased risk, and money out the door. You need to:
|
|
Our client-tested methodology and project steps allow you to tailor your knowledge transfer plan to any size of organization, across industries. Successful completion of the IT knowledge transfer project will result in the following outcomes:
|
Seventy-four percent of organizations do not have a formal process for capturing and retaining knowledge which, when lost, results in decreased productivity, increased risk, and money out the door.1
Today, the value of an organization has less to do with its fixed assets and more to do with its intangible assets. Intangible assets include patents, research and development, business processes and software, employee training, and employee knowledge and capability.
People (and their knowledge and capabilities) are an organization’s competitive advantage and with the baby boomer retirement looming, organizations need to invest in capturing employee knowledge before the employees leave. Losing employees in key roles without adequate preparation for their departure has a direct impact on the bottom line in terms of disrupted productivity, severed relationships, and missed opportunities.
Knowledge Transfer (KT) is the process and tactics by which intangible assets – expertise, knowledge, and capabilities – are transferred from one stakeholder to another. A well-devised knowledge transfer plan will mitigate the risk of knowledge loss, yet as many as 74%2 of organizations have no formal approach to KT – and it’s costing them money, reputation, and time.
84%of all enterprise value on the S&P 500 is intangibles.3
$31.5 billion lost annually by Fortune 500 companies failing to share knowledge. 1
74% of organizations have no formal process for facilitating knowledge transfer. 2
1 Shedding Light on Knowledge Management, 2004, p. 46
| 1 | Inefficiency due to “reinvention of the wheel.” When older workers leave and don’t effectively transfer their knowledge, younger generations duplicate effort to solve problems and find solutions. |
|---|---|
| 2 | Loss of competitive advantage. What and who you know is a tremendous source of competitive edge. Losing knowledge and/or established client relationships hurts your asset base and stifles growth, especially in terms of proprietary or unique knowledge. |
| 3 | Reduced capacity to innovate. Older workers know what works and what doesn’t, as well as what’s new and what’s not. They can identify the status quo faster, to make way for novel thinking. |
| 4 | Increased vulnerability. One thing that comes with knowledge is a deeper understanding of risk. Losing knowledge can impede your organizational ability to identify, understand, and mitigate risks. You’ll have to learn through experience all over again. |
55-60 |
67% |
78% |
$14k / minute |
|---|---|---|---|
the average age of mainframe workers – making close to 50% of workers over 60.2 |
of Fortune 100 companies still use mainframes3 requiring. specialized skills and knowledge |
of CIOs report mainframe applications will remain a key asset in the next decade.1 |
is the cost of mainframe outages for an average enterprise.1 |
A system failure to a mainframe could be disastrous for organizations that haven’t effectively transferred key knowledge. Now think past the mainframe to key processes, customer/vendor relationships, legal requirements, home grown solutions etc. in your organization.
What would knowledge loss cost you in terms of financial and reputational loss?
Source: 1 Big Tech Problem as Mainframes Outlast Workforce
Source: 2 IT's most wanted: Mainframe programmers
Source: 3The State of the Mainframe, 2022
Insurance organization fails to mitigate risk of employee departure and incurs costly consequences – in the millions
INDUSTRY: Insurance
SOURCE: ITRG Member
Challenge |
Solution |
Results |
|---|---|---|
|
|
|
IT knowledge transfer is a process that, at its most basic level, ensures that essential IT knowledge and capabilities don’t leave the organization – and at its most sophisticated level, drives innovation and customer service by leveraging knowledge assets.
Knowledge Transfer Risks: |
Knowledge Transfer Opportunities: |
|---|---|
|
✗ Increased training and development costs when key stakeholders leave the organization. ✗ Decreased efficiency through long development cycles. ✗ Late projects that tie up IT resources longer than planned, and cost overruns that come out of the IT budget. ✗ Lost relationships with key stakeholders within and outside the organization. ✗ Inconsistent project/task execution, leading to inconsistent outcomes. ✗ IT losing its credibility due to system or project failure from lost information. ✗ Customer dissatisfaction from inconsistent service. |
✓ Mitigated risks and costs from talent leaving the organization. ✓ Business continuity through redundancies preventing service interruptions and project delays. ✓ Operational efficiency through increased productivity by never having to start projects from scratch. ✓ Increased engagement from junior staff through development planning. ✓ Innovation by capitalizing on collective knowledge. ✓ Increased ability to adapt to change and save time-to-market. ✓ IT teams that drive process improvement and improved execution. |
How you build your knowledge transfer roadmap will not change drastically based on the size of your organization; however, the scope of your initiative, tactics you employ, and your communication plan for knowledge transfer may change.
How knowledge transfer projects vary by organization size:
Small Organization |
Medium Organization |
Large Organization |
|
|---|---|---|---|
Project Opportunities |
✓ Project scope is much more manageable. ✓ Communication and planning can be more manageable. ✓ Fewer knowledge sources and receivers can clarify prioritization needs. |
✓ Project scope is more manageable. ✓ Moderate budget for knowledge transfer activities. ✓ Communication and enforcement is easier. |
✓ Budget available to knowledge transfer initiatives. ✓ In-house expertise may be available. |
Project Risks |
✗ Limited resources for the project. ✗ In-house expertise is unlikely. ✗ Knowledge transfer may be informal and not documented. ✗ Limited overlap in responsibilities, resulting in fewer redundancies. |
✗ Limited staff with knowledge transfer experience for the project. ✗ Knowledge assets are less likely to be documented. ✗ Knowledge transfer may be a lower priority and difficult to generate buy-in. |
✗ More staff to manage knowledge transfer for, and much larger scope for the project. ✗ Impact of poor knowledge transfer can result in much higher costs. ✗Geographically dispersed business units make collaboration and communication difficult. ✗ Vast amounts of historical knowledge to capture. |
Explicit |
Tacit |
||
|
|
||
Types of explicit knowledge |
Types of tacit knowledge |
||
Information
|
Process
|
Skills
|
Expertise
|
Examples: reading music, building a bike, knowing the alphabet, watching a YouTube video on karate. |
Examples: playing the piano, riding a bike, reading or speaking a language, earning a black belt in karate. |
||
![]() |
No formal knowledge transfer program exists; knowledge transfer is ad hoc, or may be conducted through an exit interview only. 74% of organizations are at level 0.1 |
At level one, knowledge transfer is focused around ensuring that high risk, explicit knowledge is covered for all high-risk stakeholders. |
|
Organizations have knowledge transfer plans for all high-risk knowledge to ensure redundancies exist and leverage this to drive process improvements, effectiveness, and employee engagement. |
|
Increase end-user satisfaction and create a knowledge value center by leveraging the collective knowledge to solve repeat customer issues and drive new product innovation. |
I’m an IT Leader who…
Stabilize |
…has witnessed that new employees have recently left or are preparing to leave the organization, and worries that we don’t have their knowledge captured anywhere. …previously had to cut down our IT department, and as a result there is a lack of redundancy for tasks. If someone leaves, we don’t have the information we need to continue operating effectively. …is worried that the IT department has no succession planning in place and that we’re opening ourselves up to risk. |
|---|---|
Proactive |
…feels like we are losing productivity because the same problems are being solved differently multiple times. …worries that different employees have unique knowledge which is critical to performance and that they are the only ones who know about it. …has noticed that the processes people are using are different from the ones that are written down. …feels like the IT department is constantly starting projects from scratch, and employees aren’t leveraging each other’s information, which is causing inefficiencies. …feels like new employees take too long to get up to speed. …knows that we have undocumented systems and more are being built each day. |
Knowledge Culture |
…feels like we’re losing out on opportunities to innovate because we’re not sharing information, learning from others’ mistakes, or capitalizing on their successes. …notices that staff don’t have a platform to share information on a regular basis, and believes if we brought that information together, we would be able to improve customer service and drive product innovation. …wants to create a culture where employees are valued for their competencies and motivated to learn. …values knowledge and the contributions of my team. |
This blueprint can help you build a roadmap to resolve each of these pain points. However, not all organizations need to have a knowledge culture. In the next section, we will walk you through the steps of selecting your target maturity model based on your knowledge goals.
INDUSTRY: Electronics Engineering
SOURCE: KM Best Practices
Challenge | Solution | Results |
|---|---|---|
|
|
|
The Info-Tech difference:
Project outcomes |
1. Approval for IT knowledge transfer project obtained |
2. Knowledge and stakeholder risks identified |
3. Tactics for individuals’ knowledge transfer identified |
4. Knowledge transfer roadmap built |
5. Knowledge transfer roadmap approved |
|---|---|---|---|---|---|
Info-Tech tools and templates to help you complete your project deliverables |
Project Stakeholder Register Template |
IT Knowledge Transfer Risk Assessment Tool |
IT Knowledge Identification Interview Guide Template |
Project Planning and Monitoring Tool |
IT Knowledge Transfer Roadmap Presentation Template |
IT Knowledge Transfer Project Charter Template |
IT Knowledge Transfer Plan Template |
||||
Your completed project deliverables |
IT Knowledge Transfer Plans |
IT Knowledge Transfer Roadmap Presentation |
|||
IT Knowledge Transfer Roadmap |
|||||
1. Initiate |
2. Design |
3. Implement |
|
|---|---|---|---|
Phase Steps |
|
|
|
Phase Outcomes |
|
|
|
Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:
IT Knowledge Transfer Project Charter Establish a clear project scope, decision rights, and executive sponsorship for the project. |
![]() |
IT Knowledge Transfer Risk Assessment Tool Identify and assess the knowledge and individual risk of key knowledge holders. |
![]() |
IT Knowledge Identification Interview Guide Extract information about the type of knowledge sources have. |
![]() |
IT Knowledge Transfer Roadmap Presentation Communicate IT knowledge transfer recommendations to stakeholders to gain buy-in. |
![]() |
IT Knowledge Transfer Plan
Track knowledge activities, intended recipients, and appropriate transfer tactics for each knowledge source.
IT Benefits |
Business Benefits |
|
|
“ 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.”
| Phase 1 | Phase 2 | Phase 3 |
|---|---|---|
Call #1: Structure the project. Discuss transfer maturity goal and metrics. |
Call #2: Build knowledge transfer plans. Call #3: Identify priorities & review risk assessment tool. |
Call #4: Build knowledge transfer roadmap. Determine logistics of implementation. Call #5: Determine logistics of implementation. |
A Guided Implementation (GI) is a series of calls with an Info-Tech analyst to help implement our best practices in your organization. A typical GI is five to six calls.
Contact your account representative for more information.
workshops@infotech.com 1-888-670-8889
Day 1 |
Day 2 |
Day 3 |
Day 4 |
Day 5 |
|
|---|---|---|---|---|---|
Define the Current and Target State |
Identify Knowledge Priorities |
Build Knowledge Transfer Plans |
Define the Knowledge Transfer Roadmap |
Next Steps and |
|
Activities |
1.1 Have knowledge transfer fireside chat. 1.2 Identify current and target maturity. 1.3 Identify knowledge transfer metrics 1.4 Identify knowledge transfer project stakeholders |
2.1 Identify your knowledge sources. 2.2 Complete a knowledge risk assessment. 2.3 Identify knowledge sources’ level of knowledge risk. |
3.1 Build an interview guide. 3.2 Interview knowledge holders. |
4.1 Prioritize the sequence of initiatives. 4.2 Complete the project roadmap. 4.3 Prepare communication 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 |
|
|
|
|
Phase 1 |
Phase 2 |
Phase 3 |
|---|---|---|
1.1 Obtain approval for project 1.2 Identify knowledge and stakeholder risks |
2.1 Build knowledge transfer plans 2.2 Build knowledge transfer roadmap |
3.1 Communicate your roadmap |
This phase will walk you through the following activities:
This phase involves the following participants:
Activities
1.1.1 Hold a Working Session With Key Stakeholders
1.1.2 Conduct a Current and Target State Analysis.
1.1.3 Identify Key Metrics
1.1.4 Identify Your Project Team
1.1.5 Populate an RACI
1.1.6 Build the Project Charter and Obtain Approval
Initiate Your IT Knowledge Transfer Project
The primary goal of this section is to gain a thorough understanding of the reasons why your organization should invest in knowledge transfer and to identify the specific challenges to address.
Outcomes of this step
Organizational benefits and current pain points of knowledge transfer
Don’t build your project charter in a vacuum. Involve key stakeholders to determine the desired knowledge transfer goals, target maturity and KPIs, and ultimately build the project charter.
Building the project charter as a group will help you to clarify your key messages and help secure buy-in from critical stakeholders up-front, which is key.
In order to execute on the knowledge transfer project, you will need significant involvement from your IT leadership team. The trouble is that knowledge transfer can be inherently stressful for employees as it can cause concerns around job security. Members of your IT leadership team will also be individuals who need to participate in knowledge transfer, so get them involved upfront. The working session will help stakeholders feel more engaged in the project, which is pivotal for success.
You may feel like a full project charter isn’t necessary, and depending on your organizational size, it might not be. However, the exercise of building the charter is important regardless. No matter your current climate, some level of socializing the value and plans for knowledge transfer will be necessary.
Meeting Agenda
Led by: Project Sponsor
Led by: Project Manager
Led by: Project Manager
Led by: Project Manager
Led by: Project Manager
Identify the pain points you’re experiencing with knowledge transfer and some of the benefits which you’d like to see from a program to determine the key objectives By doing so, you’ll get a holistic view of what you need to achieve.
Collect this information by:
| Input | Output |
|
|
| Materials | Participants |
|
|
|
|
|
How to determine your current and target state of maturity:
| Input | Output |
|
|
| Materials | Participants |
|
|
Depending on the level of maturity you are trying to achieve, a knowledge transfer project could take weeks, months, or even years. Your maturity level depends on the business goal you would like to achieve, and impacts who and what your roadmap targets.

The maturity levels build on one another; if you start with a project, it is possible to move from a level 0 to a level 1, and once the project is complete, you can advance to a level 2 or 3. However, it’s important to set clear boundaries upfront to limit scope creep, and it’s important to set appropriate expectations for what the project will deliver.
Goal |
Description |
Time to implement |
Benefits |
|
|---|---|---|---|---|
Level 0: Accidental |
Not Prioritized |
|
N/A |
|
Level 1: Stabilize |
Risk Mitigation |
At level one, knowledge transfer is focused around ensuring that redundancies exist for explicit knowledge for:
Your high-risk knowledge is any information which is proprietary, unique, or specialized. High risk stakeholders are those individuals who are at a higher likelihood of departing the organization due to retirement or disengagement. |
0 – 6 months |
|
Goal | Description | Time to implement | Benefits | |
|---|---|---|---|---|
Level 2: Proactive | Operational Efficiency | Level 2 extends Level 1. Once stabilized, you can work on KT initiatives that allow you to be more proactive and cover high risk knowledge that may not be held by those see as high risk individuals. Knowledge transfer plans must exist for ALL high risk knowledge. | 3m – 1yr |
|
Level 3: Knowledge Culture | Drive Innovation Through Knowledge | Level 3 extends Level 2.
| 1-2 years |
|
You need to ensure your knowledge transfer initiatives are having the desired effect and adjust course when necessary. Establishing an upfront list of key performance indicators that will be benchmarked and tracked is a crucial step.
Many organizations overlook the creation of KPIs for knowledge transfer because the benefits are often one step removed from the knowledge transfer itself. However, there are several metrics you can use to measure success.
Hint: Metrics will vary based on your knowledge transfer maturity goals.
Creating KPIs for knowledge transfer is a crucial step that many organizations overlook because the benefits are often one step removed from the knowledge transfer itself. However, there are several qualitative and quantitative metrics you can use to measure success depending on your maturity level goals.
Stabilize
Be Proactive
Promote Knowledge Culture
How to determine knowledge transfer metrics:
| Input | Output |
|
|
| Materials | Participants |
|
|
Determine Project Participants |
Pick a Project Sponsor |
|
|
The project sponsor is the main catalyst for the creation of the roadmap. They will be the one who signs off on the project roadmap. The Project Participants are the key stakeholders in your organization whose input will be pivotal to the creation of the roadmap. The project stakeholders are the senior executives who have a vested interest in knowledge transfer. Following completion of this workshop, you will present your roadmap to these individuals for approval. |
|
How to define the knowledge transfer project team:
Project Stakeholder Register Template
| Input | Output |
|
|
| Materials | Participants |
|
|
If your IT leadership team isn’t on board, you’re in serious trouble! IT leaders will not only be highly involved in the knowledge transfer project, but they also may be participants, so it’s essential that you get their buy-in for the project upfront.
Document the results in the Project Stakeholder Register Template; use this as a guide to help structure your communication with stakeholders based on where they fall on the grid.
How to Manage: |
Focus on increasing these stakeholders’ level of support!
|
![]() |
Capitalize on champions to drive the project/change.
|
How to Manage: |
How to Manage: |
Pick your battles – focus on your noise makers first, and then move on to your blockers.
|
Leverage this group where possible to help socialize the program and to help encourage dissenters to support.
|
How to Manage: |
Role |
Project Role |
|
|---|---|---|
Required |
CIO |
Will often play the role of project sponsor and should be involved in key decision points. |
IT Managers Directors |
Assist in the identification of high-risk stakeholders and knowledge and will be heavily involved in the development of each transfer plan. |
|
Project Manager |
Should be in charge of leading the development and execution of the project. |
|
Business Analysts |
Responsible for knowledge transfer elicitation analysis and validation for the knowledge transfer project. |
|
Situational |
Technical Lead |
Responsible for solution design where required for knowledge transfer tactics. |
HR |
Will aid in the identification of high-risk stakeholders or help with communication and stakeholder management. |
|
Legal |
Organizations that are subject to knowledge confidentiality, Sarbanes-Oxley, federal rules, etc. may need legal to participate in planning. |
Apps MGR |
Dev. MGR |
Infra MGR |
|
|---|---|---|---|
Build the project charter |
R |
R |
I |
Identify IT stakeholders |
R |
R |
I |
Identify high risk stakeholders |
R |
A | R |
Identify high risk knowledge |
I | C | C |
Validate prioritized stakeholders |
I | C | R |
Interview key stakeholders |
R | R | A |
Identify knowledge transfer tactics for individuals |
C | C | A |
Communicate knowledge transfer goals |
C | R | A |
Build the knowledge transfer roadmap |
C | R | A |
Approve knowledge transfer roadmap |
C | R | C |
How to define RACI for the project team:
Responsible: The one responsible for getting the job done.
Accountable: Only one person can be accountable for each task.
Consulted: Involvement through input of knowledge and information.
Informed: Receiving information about process execution and quality.
| Input | Output |
|
|
| Materials | Participants |
|
|
Build the project charter and obtain sign-off from your project sponsor. Use your organization’s project charter if one exists. If not, customize Info-Tech’s IT Knowledge Transfer Project Charter Template to suit your needs.
Activities
1.2.1 Identify Knowledge Sources
1.2.2 Complete a Knowledge Risk Assessment
1.2.3 Review the Prioritized List of Knowledge Sources
The primary goal of this section is to identify who your primary risk targets are for knowledge transfer.
Outcomes of this step
Throughout this section, we will walk through the following 3 activities in the tool to determine where you need to focus attention for your knowledge transfer roadmap based on knowledge value and likelihood of departure.
1. Identify Knowledge Sources
Create a list of knowledge sources for whom you will be conducting the analysis, and identify which sources currently have a transfer plan in place.
2. Value of Knowledge
Consider the type of knowledge held by each identified knowledge source and determine the level of risk based on the knowledge:
3. Likelihood of Departure
Identify the knowledge source’s risk of leaving the organization based on their:
This tool contains sensitive information. Do not share this tool with knowledge sources. The BA and Project Manager, and potentially the project sponsor, should be the only ones who see the completed tool.
Identify Key Roles
Hold a meeting with your IT Leadership team, or meet with members individually, and ask these questions to identify key roles:
Key roles include:
This step is meant to help speed up and simplify the process for large IT organizations. IT organizations with fewer than 30 people, or organizations looking to build a knowledge culture, can opt to skip this step and include all members of the IT team. This way, everyone is considered and you can prioritize accordingly.
| Input | Output |
|
|
| Materials | Participants |
|
|
Legend:
1. Document knowledge source information (name, department, and manager).
2. Select the current state of knowledge transfer plans for each knowledge source.
Once you have identified key roles, conduct a sanity check and ask – “did we miss anybody?” For example:
Municipal government learns the importance of thorough knowledge source identification after losing key stakeholder
INDUSTRY: Government
Challenge |
Solution |
Results |
|
|
|
Risk Parameter | Description | How to Collect this Data: |
Age Cohort |
| For those people on your shortlist, pull some hard demographic data. Compile a report that breaks down employees into age-based demographic groups. Flag those over the age of 50 – they’re in the “retirement zone” and could decide to leave at any time. Check to see which stakeholders identified fall into the “over 50” age demographic. Document this information in the IT Knowledge Transfer Risk Assessment Tool. |
150% of an employee’s base salary and benefits is the estimated cost of turnover according to The Society of Human Resource Professionals.1
1McLean & Company, Make the Case for Employee Engagement
Risk Parameter | Description | How to Collect this Data: |
Engagement | An engaged stakeholder is energized and passionate about their work, leading them to exert discretionary effort to drive organizational performance (lowest risk). An almost engaged stakeholder is generally passionate about their work. At times they exert discretionary effort to help achieve organizational goals. Indifferent employees are satisfied, comfortable, and generally able to meet minimum expectations. They see their work as “just a job,” prioritizing their needs before organizational goals. Disengaged employees have little interest in their job and the organization and often display negative attitudes (highest risk). | Option 1: The optimal approach for determining employee engagement is through an engagement survey. See McLean & Company for more details. Option 2: Ask the identified stakeholder’s manager to provide an assessment of their engagement either independently or via a meeting. |
Engaged employees are five times more likely than disengaged employees to agree that they are committed to their organization.1
1Source: McLean & Company, N = 13683
Risk Parameter | Description | How to Collect this Data: |
Criticality | Roles that are critical to the continuation of business and cannot be left vacant without risking business operations. Would the role, if vacant, create system, function, or process failure for the organization? | Option 1: (preferred) Meet with IT managers/directors over the phone or directly and review each of the identified reports to determine the risk. Option 2: Send the IT mangers/directors the list of their direct reports, and ask them to evaluate their knowledge type risk independently and return the information to you. Option 3: (if necessary) Review individual job descriptions independently, and use your judgment to come up with a rating for each. Send the assessment to the stakeholders’ managers for validation. |
Availability | Refers to level of redundancy both within and outside of the organization. Information which is highly available is considered lower risk. Key questions to consider include: does this individual have specialized, unique, or proprietary expertise? Are there internal redundancies? |
Complete a Tab 3 assessment for each of your identified Knowledge Sources. The Knowledge Source tab will pre-populate with information from Tab 2 of the tool. For each knowledge source, you will determine their likelihood of departure and degree of knowledge risk.
Likelihood of departure:
Degree of knowledge risk is based on:
| Input | Output |
|
|
| Materials | Participants |
|
|
Knowledge sources have been separated into the three maturity levels (Stabilize, Proactive, and Knowledge Culture) and prioritized within each level.
Focus first on your stabilize groups, and based on your target maturity goal, move on to your proactive and knowledge culture groups respectively.
Sequential Prioritization Orange line Level 1: Stabilize Blue Line Level 2: Proactive Green Line Level 3: Knowledge Culture |
Each pie chart indicates which of the stakeholders in that risk column currently has knowledge transfer plans. |
Each individual also has their own status ball on whether they currently have a knowledge transfer plan. |
Identify knowledge sources to focus on for the knowledge transfer roadmap. Review the IT Knowledge Transfer Map on Tab 5 to determine where to focus your knowledge transfer efforts
| Input | Output |
|
|
| Materials | Participants |
|
|
Phase 1 |
Phase 2 |
Phase 3 |
|---|---|---|
1.1 Obtain approval for project 1.2 Identify knowledge and stakeholder risks |
2.1 Build knowledge transfer plans 2.2 Build knowledge transfer roadmap |
3.1 Communicate your roadmap |
This phase will walk you through the following activities:
This phase involves the following participants:
Define what knowledge needs to be transferred |
Each knowledge source has unique information which needs to be transferred. Chances are you don’t know what you don’t know. The first step is therefore to interview knowledge sources to find out. |
Identify the knowledge receiver |
Depending on who the information is going to, the knowledge transfer tactic you employ will differ. Before deciding on the knowledge receiver and tactic, consider three key factors:
|
Identify which knowledge transfer tactics you will use for each knowledge asset |
Not all tactics are good in every situation. Always keep the “knowledge type” (information, process, skills, and expertise), knowledge sources’ engagement level, and the knowledge receiver in mind as you select tactics. |
This tool is built to accommodate up to 30 knowledge items; Info-Tech recommends focusing on the top 10-15 items.
These steps should be completed by the BA or IT Manager. The BA is helpful to have around because they can learn about the tactics and answer any questions about the tactics that the managers might have when completing the template.
Activities
2.1.1 Interview Knowledge Sources to Uncover Key Knowledge Items
2.1.2 Identify When to use Knowledge Transfer Tactics
2.1.3 Build Individual Knowledge Transfer Plans
The primary goal of this section is to build an interview guide and interview knowledge sources to identify key knowledge assets.
Outcomes of this step
The first step is for managers to interview knowledge sources in order to extract information about the type of knowledge the source has.
Meet with the knowledge sources and work with them to identify essential knowledge. Use the following questions as guidance:
| Input | Output |
|
|
| Materials | Participants |
|
|
| Input | Output |
|
|
| Materials | Participants |
|
|
Interviews provide an opportunity to meet one-on-one with key stakeholders to document key knowledge assets. Interviews can be used for explicit and tacit information, and in particular, capture processes, rules, coding information, best practices, etc.
Knowledge Types Information Process Skills Expertise | Dependencies Training: Minimal Technology Support: N/A Process Development: Minimal Duration: Annual | Participants Business analysts Knowledge source | Materials Interview guide Notepad Pen |
Business process mapping refers to building a flow chart diagram of the sequence of actions which defines what a business does. The flow chart defines exactly what a process does and the specific succession of steps including all inputs, outputs, flows, and linkages. Process maps are a powerful tool to frame requirements in the context of the complete solution.
Benefits:
How to get started:
Knowledge Types Information Process Skills Expertise | Dependencies Training: Minimal Technology Support: N/A Process Development: Minimal Duration: Annual | Participants Business analysts Knowledge source | Materials Whiteboard / flip-chart paper Marker |
Use case diagrams are a common transfer tactic where the BA maps out step-by-step how an employee completes a project or uses a system. Use cases show what a system or project does rather than how it does it. Use cases are frequently used by product managers and developers.
Benefits:
How to get started:
Knowledge Types Information Process Skills Expertise | Dependencies Training: Minimal Technology Support: N/A Process Development: Minimal Duration: Annual | Participants Business analysts Knowledge source | Materials Whiteboard / flip-chart paper Marker |
Job shadowing is a working arrangement where the “knowledge receiver” learns how to do a job by observing an experienced employee complete key tasks throughout their normal workday.
Benefits:
How to get started:
Knowledge Types Information Process Skills Expertise | Dependencies Training: Required Technology Support: N/A Process Development:Required Duration:Ongoing | Participants BA IT manager Knowledge source and receiver | Materials N/A |
Meeting or workshop where peers from different teams share their experiences and knowledge with individuals or teams that require help with a specific challenge or problem.
Benefits:
How to get started:
Knowledge Types Information Process Skills Expertise | Dependencies Training: Minimal Technology Support: N/A Process Development:Required Duration:Ongoing | Participants Knowledge sources Knowledge receiver BA to build a skill repository | Materials Intranet |
A half- to full-day exercise where an outgoing leader facilitates a knowledge transfer of key insights they have learned along the way and any high-profile knowledge they may have.
Benefits:
How to get started:
Knowledge Types Information Process Skills Expertise | Dependencies Training: Required Technology Support: Some Process Development: Some Duration:Ongoing | Participants IT leader Incoming IT team Key stakeholders | Materials Meeting space Video conferencing (as needed) |
Action Review is a team-based discussion at the end of a project or step to review how the activity went and what can be done differently next time. It is ideal for transferring expertise and skills.
Benefits:
How to get started:
Knowledge Types Information Process Skills Expertise | Dependencies Training:Minimal Technology Support: Minimal Process Development: Some Duration:Ongoing | Participants IT unit/group Any related IT stakeholder impacted by or involved in a project. | Materials Meeting space Video conferencing (as needed) |
Mentoring can be a formal program where management sets schedules and expectations. It can also be informal through an environment for open dialogue where staff is encouraged to seek advice and guidance, and to share their knowledge with more novice members of the organization.
Benefits:
How to get started:
Creating a mentorship program is a full project in itself. For full details on how to set up a mentorship program, see McLean & Company’s Build a Mentoring Program.
Knowledge Types Information Process Skills Expertise | Dependencies Training: Required Technology Support: N/a Process Development:Required Duration:Ongoing | Participants IT unit/group | Materials Meeting space Video conferencing (as needed) Documentation |
Knowledge sources use anecdotal examples to highlight a specific point and pass on information, experience, and ideas through narrative.
Benefits:
How to get started:
Knowledge Types Information Process Skills Expertise | Dependencies Training: Required Technology Support: Some Process Development:Required Duration:Ongoing | Participants Knowledge source Knowledge receiver Videographer (where applicable) | Materials Meeting space Video conferencing (as needed) Documentation |
Job share exists when at least two people share the knowledge and responsibilities of two job roles.
Benefits:
How to get started:
Knowledge Types Information Process Skills Expertise | Dependencies Training: Some Technology Support: Minimal Process Development:Required Duration:Ongoing | Participants IT manager HR Employees | Materials Job descriptions |
Communities of practice are working groups of individuals who engage in a process of regularly sharing information with each other across different parts of the organization by focusing on common purpose and working practices. These groups meet on a regular basis to work together on problem solving, to gain information, ask for help and assets, and share opinions and best practices.
Benefits:
How to get started:
Knowledge Types Information Process Skills Expertise | Dependencies Training:Required Technology Support: Required Process Development:Required Duration:Ongoing | Participants Employees BA (to assist in establishing) IT managers (rewards and recognition) | Materials TBD |
This table shows the relative strengths and weaknesses of each knowledge transfer tactic compared to four different knowledge types.
Not all techniques are effective for types of knowledge; it is important to use a healthy mixture of techniques to optimize effectiveness.
Very strong = Very effective
Strong = Effective
Medium = Somewhat effective
Weak = Minimally effective
Very weak = Not effective
Knowledge Type | ||||
Tactic | Explicit | Tacit | ||
Information | Process | Skills | Expertise | |
Interviews | Very strong | Strong | Strong | Strong |
Process mapping | Medium | Very strong | Very weak | Very weak |
Use cases | Medium | Very strong | Very weak | Very weak |
Job shadow | Very weak | Medium | Very strong | Very strong |
Peer assist | Strong | Medium | Very strong | Very strong |
Action review | Medium | Medium | Strong | Weak |
Mentoring | Weak | Weak | Strong | Very strong |
Transition workshop | Strong | Strong | Strong | Strong |
Story telling | Weak | Weak | Strong | Very strong |
Job share | Weak | Weak | Very strong | Very strong |
Communities of practice | Strong | Weak | Very strong | Very strong |
Level of Engagement | ||
Tactic | Disengaged/ Indifferent | Almost Engaged - Engaged |
Interviews | Yes | Yes |
Process mapping | Yes | Yes |
Use cases | Yes | Yes |
Job shadow | No | Yes |
Peer assist | Yes | Yes |
Action review | Yes | Yes |
Mentoring | No | Yes |
Transition workshop | Yes | Yes |
Story telling | No | Yes |
Job share | Maybe | Yes |
Communities of practice | Maybe | Yes |
When considering which tactics to employ, it’s important to consider the knowledge holder’s level of engagement. Employees whom you would identify as being disengaged may not make good candidates for job shadowing, mentoring, or other tactics where they are required to do additional work or are asked to influence others.
Knowledge transfer can be controversial for all employees as it can cause feelings of job insecurity. It’s essential that motivations for knowledge transfer are communicated effectively.
Pay particular attention to your communication style with disengaged and indifferent employees, communicate frequently, and tie communication back to what’s in it for them.
Putting disengaged employees in a position where they are mentoring others can be a risk. Their negativity could influence others not to participate as well or negate the work you’re doing to create a positive knowledge sharing culture.
There is a wide variety of different collaboration tools available to enable interpersonal and team connections for work-related purposes. Familiarize yourself with all types of collaboration tools to understand what is available to help facilitate knowledge transfer.
Collaboration Tools |
|||
Content Management |
Real Time Communication |
Community Collaboration |
Social Collaboration |
Tools for collaborating around documents. They store content and allow for easy sharing and editing, e.g. content repositories and version control. Can be used for:
|
Tools that enable real-time employee interactions. They permit “on-demand” workplace communication, e.g. IM, video and web conferencing. Can be used for:
|
Tools that allow teams and communities to come together and share ideas or collaborate on projects, e.g. team portals, discussion boards, and ideation tools. Can be used for:
|
Social tools borrow concepts from consumer social media and apply them to the employee-centric context, e.g. employee profiles, activity streams, and microblogging. Can be used for:
|
For more information on Collaboration Tools and how to use them, see Info-Tech’s Establish a Communication and Collaboration System Strategy.
Wherever possible, ask employees about their personal learning styles. It’s likely that a collaborative compromise will have to be struck for knowledge transfer to work well.
We will use the IT Knowledge Transfer Plans as the foundation for building your knowledge transfer roadmap.
The Strength Level column will indicate how well matched the tactic is to the type of knowledge.
| Input | Output |
|
|
| Materials | Participants |
|
|
Activities
2.2.1 Merge Your Knowledge Transfer Plans
2.2.2 Define Knowledge Transfer Initiatives’ Timeframes
The goal of this step is to build the logistics of the knowledge transfer roadmap to prepare to communicate it to key stakeholders.
Outcomes of this step
Depending on the desired state of maturity, the number of initiatives your organization has will vary and there could be a lengthy number of tasks and subtasks required to reach your organization knowledge transfer target state. The best way to plan, organize, and manage all of them is with a project roadmap.


Populate the task column of the Project Planning and Monitoring Tool. See the following slides for more details on how to do this.
Effort by Stakeholder | |||||
Tactic | Business Analyst | IT Manager | Knowledge Holder | Knowledge Receiver | |
| Interviews | Medium | N/A | Low | Low | These tactics require the least amount of effort, especially for organizations that are already using these tactics for a traditional requirements gathering process. |
Process Mapping | Medium | N/A | Low | Low | |
Use Cases | Medium | N/A | Low | Low | |
Job Shadow | Medium | Medium | Medium | Medium | These tactics generally require more involvement from IT management and the BA in tandem for preparation. They will also require ongoing effort for all stakeholders. Stakeholder buy-in is key for success. |
Peer Assist | Medium | Medium | Medium | Medium | |
Action Review | Low | Medium | Medium | Low | |
Mentoring | Medium | High | High | Medium | |
Transition Workshop | Medium | Low | Medium | Low | |
Story Telling | Medium | Medium | Low | Low | |
Job Share | Medium | High | Medium | Medium | |
Communities of Practice | High | Medium | Medium | Medium | |
Implementation Dependencies | |||||
Tactic | Training | Technology Support | Process Development | Duration | |
| Interviews | Minimal | N/A | Minimal | Annual | Start your knowledge transfer project here to get quick wins for explicit knowledge. |
Process Mapping | Minimal | N/A | Minimal | Annual | |
Use Cases | Minimal | N/A | Minimal | Annual | |
Job Shadow | Required | N/A | Required | Ongoing | Don’t change too much too quickly or try to introduce all of the tactics at once. Focus on 1-2 key tactics and spend a significant amount of time upfront building an effective process and rolling it out. Leverage the effectiveness of the initial tactics to push these initiatives forward. |
| Peer Assist | Minimal | N/A | Required | Ongoing | |
| Action Review | Minimal | Minimal | Some | Ongoing | |
| Mentoring | Required | N/A | Required | Ongoing | |
| Transition Workshop | Required | Some | Some | Ongoing | |
| Story Telling | Some | Required | Required | Ongoing | |
| Job Share | Some | Minimal | Required | Ongoing | |
| Communities of Practice | Required | Required | Required | Ongoing | |
| Input | Output |
| |
| Materials | Participants |
|
|
| Input | Output |
|
|
| Materials | Participants |
|
|
Phase 1 | Phase 2 | Phase 3 |
|---|---|---|
1.1 Obtain approval for project 1.2 Identify knowledge and stakeholder risks | 2.1 Build knowledge transfer plans 2.2 Build knowledge transfer roadmap | 3.1 Communicate your roadmap |
This phase will walk you through the following activities:
This phase involves the following participants:
Activities
3.1.1 Prepare IT Knowledge Transfer Roadmap Presentation
The goal of this step is to be ready to communicate the roadmap with the project team, project sponsor, and other key stakeholders.
Outcomes of this step
Obtain approval for the IT Knowledge Transfer Roadmap by customizing Info-Tech’s IT Knowledge Transfer Roadmap Presentation Template designed to effectively convey your key messages. Tailor the template to suit your needs.
It includes:
The support of IT leadership is critical to the success of your roadmap roll-out. Remind them of the project benefits and impact them hard with the risks/pain points.
Know your audience:
| Input | Output |
|
|
| Materials | Participants |
|
|
Babcock, Pamela. “Shedding Light on Knowledge Management.” HR Magazine, 1 May 2004.
King, Rachael. "Big Tech Problem as Mainframes Outlast Workforce." Bloomberg, 3 Aug. 2010. Web.
Krill, Paul. “IT’s Most Wanted: Mainframe Programmers.” IDG Communications, Inc. 1 December 2011.
McLean & Company. “Mitigate the Risk of Baby Boomer Retirement with Scalable Succession Planning.” 7 March 2016.
McLean & Company. “Make the Case For Employee Engagement.” McLean and Company. 27 March 2014.
PwC. “15th Annual Global CEO Survey: Delivering Results Growth and Value in a Volatile World.” PwC, 2012.
Rocket Software, Inc. “Rocket Software 2022 Survey Report: The State of the Mainframe.” Rocket Software, Inc. January 2022. Accessed 30 April 2022.
Ross, Jenna. “Intangible Assets: A Hidden but Crucial Driver of Company Value.” Visual Capitalist, 11 February 2020. Accessed 2 May 2022.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
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.
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.
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.
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).
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.
Use this tool to specifically record assumptions made about who and what are impacted by system downtime and record assumptions made about impact severity.
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.
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.
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.
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).
The following tools and templates are also included as part of this blueprint to use as needed to supplement the core steps above:
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.
Identify key applications and dependencies based on business needs.
Understand the entire IT “footprint” that needs to be recovered for key applications.
1.1 Assess current DR maturity.
1.2 Determine critical business operations.
1.3 Identify key applications and dependencies.
Current challenges identified through a DRP Maturity Scorecard.
Key applications and dependencies documented in the Business Impact Analysis (BIA) Tool.
Quantify application criticality based on business impact.
Appropriate recovery time and recovery point objectives defined (RTOs/RPOs).
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.
Business impact analysis scoring criteria defined.
Application criticality validated.
RTOs/RPOs defined for applications and dependencies.
Determine your baseline DR capabilities (your current state).
Gaps between current and desired DR capability are quantified.
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.
Current achievable recovery timeline defined (i.e. the current state).
RTO/RPO gaps identified.
Critical single points of failure identified.
Identify and prioritize projects to close DR gaps.
DRP project roadmap defined that will reduce downtime and data loss to acceptable levels.
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.
Potential DR projects identified.
DRP project roadmap defined.
Desired-state incident response plan defined, and project roadmap validated.
Outline how to create concise, usable DRP documentation.
Summarize workshop results.
A realistic and practical approach to documenting your DRP.
Next steps documented.
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.
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.
"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
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
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
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. |
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.
Source: Info-Tech Research Group; N=92
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.
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.
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:
Sources: Kyle York, 2016; Shaun Nichols, 2017; Stephen Burke, 2017
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:
"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
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.
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:
|
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).
"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.”
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).
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.
Contact your account representative or email Workshops@InfoTech.com for more information.
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:
Tabletop Testing and Recovery Capabilities
Reviewing the organization’s current systems recovery workflow identified the following capabilities:
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.
Identify DR Maturity and System Dependencies
Conduct a BIA
Outline Incident Response and Recovery Workflow With Tabletop Exercises
Mitigate Gaps and Risks
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
Find and review existing documentation
Set specific, realistic objectives
Estimated Time: 30 minutes
Identify the drivers and challenges to completing a functional DRP plan with the core DR team.
DRP Drivers
DRP Challenges
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).
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.
Note: Identify the initial team roles and responsibilities first so they can assist in defining the project charter.
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.
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.
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.
| Application | Notes |
|---|---|
| CRM |
|
| Dialer |
|
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:
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.
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.
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.
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.
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.
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.
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.
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.
Use the suggestions below as a guide as you modify scoring criteria in the DRP Business Impact Analysis Tool:
Estimated Time: 3 hours
On tab 3 of the DRP Business Impact Analysis Tool indicate the costs of downtime, as described below:
For example, if a core call center phone system was down:
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:
Use Info-Tech’s DRP BIA Scoring Context Example as a note-taking template.
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.
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.
Example: Highest total score is 12
The business must validate acceptable and appropriate RTOs and RPOs, but IT can use the guidelines below to set an initial estimate.
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?
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.
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.
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:
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.
Estimated the business impact of downtime
Set recovery targets
Up Next:Conduct a tabletop planning exercise to establish current recovery capabilities
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.
*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:
Why is tabletop planning so effective?
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.
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.
Estimated Time: 2-3 hours
Why use flowcharts?
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
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.
What’s my RPA? Consider the following case:
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.
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.
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.
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).
Estimated Time: 1 hour
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.
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 |
|
| Power outage or network outage |
|
| Local hazard (e.g. chemical leak, police incident) |
|
| Equipment/building damage (e.g. fire, roof collapse) |
|
| Regional natural disasters |
|
Estimated Time: 1.5 hours
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.
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.
Approach site selection as a project. Leverage Select an Optimal Disaster Recovery Deployment Model to structure your own site-selection project.
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.
Estimated Time: 30 minutes
Outline your expected future state recovery flow to demonstrate improvements once projects and action items have been completed.
Estimated Time: time required will vary
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:
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.
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.
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.
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.
Outlined the DRP response and risks to recovery
Brainstormed risk mitigation measures
Up Next: Leverage the core deliverables to complete, extend, and maintain your DRP
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.
Use the completed, updated DRP Maturity Scorecard to demonstrate the value of your continuity program, and to help you decide where to focus next.
Estimated Time: 2 hours
| 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. |
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.
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 |
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.
| 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. |
Use this example of a complete, practical, right-size DR plan to drive and guide your efforts.
| 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. |
Use this example of a complete, practical, right-size DR plan to drive and guide your efforts.
| Sample Outputs |
|---|
| Application assessment for cloud DR. |
| TCO tool for different environments. |
| Solution decision and executive presentation. |
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.
Risks and Challenges Mitigated
| 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. |
Use Info-Tech’s blueprint, Develop a Business Continuity Plan, to develop and deploy a repeatable BCP methodology.
| Sample Outputs |
|---|
| DR testing readiness assessment. |
| Testing handbooks. |
| Test plan summary template. |
| DR test issue log and analysis tool. |
Uncover deficiencies in your recovery procedures by using Info-Tech’s blueprint Reduce Costly Downtime Through DR Testing.
| Sample Outputs |
|---|
| Reviewed and updated change, project, and performance management processes. |
| Reviewed and updated internal SLAs. |
| Reviewed and updated data protection and backup procedures. |
| Sample Outputs |
|---|
| A customized vendor DRP questionnaire. |
| Reviewed vendor SLAs. |
| Choose to keep or change service levels or vendor offerings based on findings. |
Identified progress against targets
Prioritized further initiatives
Added initiatives to the roadmap
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.
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.
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)
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.
Having shifted operations almost overnight to a remote work environment, and with the crisis management phase of the COVID-19 pandemic winding down, IT leaders and organizations are faced with the following issues:
An organization’s shift back toward the pre-pandemic state cannot be carried out in isolation. Things have changed. Budgets, resource availability, priorities, etc., will not be the same as they were in early March. Organizations must ensure that all departments work collaboratively to support office repatriation. IT must quickly identify the must-dos to allow safe return to the office, while prioritizing tasks relating to the repopulation of employees, technical assets, and operational workloads via an informed and streamlined roadmap.
As employees return to the office, PMO and portfolio leaders must sift through unclear requirements and come up with a game plan to resume project activities mid-pandemic. You need to develop an approach, and fast.
Responsibly resume IT operations in the office:
Quickly restart the engine of your PPM:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Identify the new risk landscape and risk tolerance for your organization post-pandemic. Determine how this may impact the second wave of pandemic transition tasks.
Prepare to return your employees to the office. Ensure that IT takes into account the health and safety of employees, while creating an efficient and sustainable working environment
Prepare the organization's assets for return to the office. Ensure that IT takes into account the off-license purchases and new additions to the hardware family that took place during the pandemic response and facilitates a secure reintegration to the workplace.
Prepare and position IT to support workloads in order to streamline office reintegration. This may include leveraging pre-existing solutions in different ways and providing additional workstreams to support employee processes.
Once you've identified IT's supporting tasks, it's time to prioritize. This phase walks through the activity of prioritizing based on cost/effort, alignment to business, and security risk reduction weightings. The result is an operational action plan for resuming office life.
Restarting the engine of the project portfolio mid-pandemic won’t be as simple as turning a key and hitting the gas. Use this concise research to find the right path forward for your organization.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
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.
Your Challenge
|
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:
|
Info-Tech’s Approach
|
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.
1Know Your DataDo 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. |
2Protect Your DataDo 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. |
3Prevent Data LossAre 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. |
4Govern Your DataAre 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. |
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 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.

(Source: Microsoft, “Microsoft Purview compliance portal”)
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.
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 residesData types that require classification. |
|
| M365 Workload Containers | |||
Email
|
Site Collections, Sites | Sites | Project Databases |
| Contacts | Teams and Group Site Collections, Sites | Libraries and Lists | Sites |
| Metadata | Libraries and Lists | Documents
|
Libraries and Lists |
| Teams Conversations | Documents
|
Metadata | Documents
|
| Teams Chats | Metadata | Permissions
|
Metadata |
Permissions
|
Files Shared via Teams Chats | Permissions
|
|
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.
AIP helps you manage sensitive data prior to migrating to Office 365:
|
|
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. |
Any asset deployed to the cloud must have approved data classification. Enforcing this policy is a must to control your data.
Information Governance
|
Records Management
|
| 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. |
Info-Tech InsightRetention 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). |
|
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:
“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)
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.
Internal Personal, Employment, and Job Performance Data
|
Confidential Information
|
Internal Data
|
Public Data
|
| Public | Private | |
| Privacy |
|
|
| Allowed | Not Allowed | |
| External guest policy |
|
|
What users will see when they create or label a Team/Group/Site

(Source: Microsoft, “Microsoft Purview compliance portal”)
| 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). |
Security MFA or SSO to access from anywhere, any device Banned password list BYOD sync with corporate network |
Users Sign out inactive users automatically Enable guest users External sharing Block client forwarding rules |
Resources Account lockout threshold OneDrive SharePoint |
Controls Sensitivity labels, retention labels and policies, DLP Mobile application management policy |
Sensitivity Profiles: Public, Internal, Confidential; Subcategory: Highly Confidential
| 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 |
|
|
|
|
| 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”)
| 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. |
||
| PRIMARY ACTIVITIES | Define Your Governance
| CATEGORIZATION
CLASSIFICATION | MVP | ||||
| Data Discovery and Management
| |||||||
| Baseline Setup
| |||||||
| Default M365 settings
| |||||||
| SUPPORT ACTIVITIES | Retention Policy
| Sensitivity Labels
| Workload Containers
| Unforced Policies
| Forced Policies
| ||
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.
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.
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 practicesIT 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.
“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.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Identify what skills will be needed in your future state.
Align role requirements with future initiative skill needs.
Acquire skills based on the impact of the five key factors.
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.
Determine the skills needed in your workforce and align them to your organization’s security roadmap.
Insight on what skills your organization will need in the future.
1.1 Understand the importance of aligning security initiatives skill needs with workforce requirements.
1.2 Identify needed skills for future initiatives.
1.3 Prioritize the initiative skill gaps.
Security Initiative Skills Guide
Skills Gap Prioritization Tool
Identify and create technical skill requirements for key work roles that are needed to successfully execute future initiatives.
Increased understanding of the NICE Cybersecurity Workforce Framework.
Standardization of technical skill requirements of current and future work roles.
2.1 Assign work roles to the needs of your future environment.
2.2 Discuss the NICE Cybersecurity Workforce Framework.
2.3 Develop technical skill requirements for current and future work roles.
Skills Gap Prioritization Tool
Technical Skills Workbook
Current Workforce Skills Assessment
Assess your current workforce against their role’s skill requirements.
Discuss five key factors that aid acquiring skills.
A method to acquire skills in future roles.
3.1 Continue developing technical skill requirements for current and future work roles.
3.2 Conduct Current Workforce Skills Assessment.
3.3 Discuss methods of acquiring skills.
3.4 Develop a plan to acquire skills.
Technical Skills Workbook
Current Workforce Skills Assessment
Current Workforce Skills Assessment
Technical Skills Workbook
Current Workforce Skills Assessment
Technical Skills Workbook
Current Workforce Skills Assessment
Assist with communicating the state of the skill gap in your organization.
Strategy on how to acquire skills needs of the organization.
4.1 Review skills acquisition plan.
4.2 Discuss training and certification opportunities for staff.
4.3 Discuss next steps for closing the skills gap.
4.4 Debrief.
Technical Skills Workbook
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Whether you have no Service Desk customer feedback program in place or you need to improve your existing process for gathering and responding to feedback, this deck will help you design your surveys and act on their results to improve CSAT scores.
This template provides a sample transactional (ticket) satisfaction survey. If your ITSM tool or other survey mechanism allows you to design or write your own survey, use this template as a starting point.
Use the Sample Size Calculator to calculate your ideal sample size for your relationship surveys.
This template will help you map out the step-by-step process to review collected feedback from your end-user satisfaction surveys, analyze the data, and act on it.
EXECUTIVE BRIEF
Natalie Sansone, PhD
Info-Tech Research Group |
Often when we ask service desk leaders where they need to improve and if they’re measuring customer satisfaction, they either aren’t measuring it at all, or their ticket surveys are turned on but they get very few responses (or only positive responses). They fail to see the value of collecting feedback when this is their experience with it. Feedback is important because traditional service desk metrics can only tell us so much. We often see what’s called the “watermelon effect”: metrics appear “green”, but under the surface they’re “red” because customers are in fact dissatisfied for reasons unmeasured by standard internal IT metrics. Customer satisfaction should always be the goal of service delivery, and directly measuring satisfaction in addition to traditional metrics will help you get a clearer picture of your strengths and weaknesses, and where to prioritize improvements. It’s not as simple as asking customers if they were satisfied with their ticket, however. There are two steps necessary for success. The first is collecting feedback, which should be done purposefully, with clear goals in mind in order to maximize the response rate and value of responses received. The second – and most critical – is acting on that feedback. Use it to inform improvements and communicate those improvements. Doing so will not only make your service desk better, increasing satisfaction through better service delivery, but also will make your customers feel heard and valued, which alone increases satisfaction. |
Emily Sugerman, PhD
Info-Tech Research Group |
Your Challenge |
Common Obstacles |
Info-Tech’s Approach |
|---|---|---|
|
|
|
Asking your customers for feedback then doing nothing with it is worse than not asking for feedback at all. Your customers may end up more dissatisfied than they were before, if their opinion is sought out and then ignored. It’s valuable to collect feedback, but the true value for both IT and its customers comes from acting on that feedback and communicating those actions back to your users.
The watermelon effect
When a service desk appears to hit all its targets according to the metrics it tracks, but service delivery is poor and customer satisfaction is low, this is known as the “watermelon effect”. Service metrics appear green on the outside, but under the surface (unmeasured), they’re red because customers are dissatisfied.
Traditional SLAs and service desk metrics (such as time to respond, average resolution time, percentage of SLAs met) can help you understand service desk performance internally to prioritize your work and identify process improvements. However, they don’t tell you how customers perceive the service or how satisfied they are.
Providing good service to your customers should be your end goal. Failing to measure, monitor, and act on customer feedback means you don’t have the whole picture of how your service desk is performing and whether or where improvements are needed to maximize satisfaction.
The Service Desk Institute (SDI) suggests that customer satisfaction is the most important indicator of service desk success, and that traditional metrics around SLA targets – currently the most common way to measure service desk performance – may become less valuable or even obsolete in the future as customer experience-focused targets become more popular. (Service Desk Institute, 2021)
SDI conducted a Customer Experience survey of service desk professionals from a range of organizations, both public and private, from January to March 2018. The majority of respondents said that customer experience is more important than other metrics such as speed of service or adherence to SLAs, and that customer satisfaction is more valuable than traditional metrics. (SDI, 2018).

Obstacles to collecting feedback |
Obstacles to acting on collected feedback |
|---|---|
|
|
Insight into customer experience |
Gather insight into both the overall customer relationship with the service desk and individual transactions to get a holistic picture of the customer experience. |
|---|---|
Data to inform decisions |
Collect data to inform decisions about where to spend limited resources or time on improvement, rather than guessing or wasting effort on the wrong thing. |
Identification of areas for improvement |
Better understand your strengths and weaknesses from the customer’s point of view to help you identify gaps and priorities for improvement. |
Customers feel valued |
Make customers feel heard and valued; this will improve your relationship and their satisfaction. |
Ability to monitor trends over time |
Use the same annual relationship survey to be able to monitor trends and progress in making improvements by comparing data year over year. |
Foresight to prevent problems from occurring |
Understand where potential problems may occur so you can address and prevent them, or who is at risk of becoming a detractor so you can repair the relationship. |
IT staff coaching and engagement opportunities |
Turn negative survey feedback into coaching and improvement opportunities and use positive feedback to boost morale and engagement. |

Phase |
1. Understand how to measure customer satisfaction |
2. Design and implement transactional surveys |
3. Design and implement relationship surveys |
4. Analyze and act on feedback |
|---|---|---|---|---|
Phase outcomes |
Understand the main types of customer satisfaction surveys, principles for survey design, and best practices for surveying your users. |
Learn why and how to design a simple survey to assess satisfaction with individual service desk transactions (tickets) and a methodology for survey delivery that will improve response rates. |
Understand why and how to design a survey to assess overall satisfaction with the service desk across your organization, or use Info-Tech’s diagnostic. |
Measure and analyze the results of both surveys and build a plan to act on both positive and negative feedback and communicate the results with the organization. |
Key Insight:
Asking your customers for feedback then doing nothing with it is worse than not asking for feedback at all. Your customers may end up more dissatisfied than they were before if they’re asked for their opinion then see nothing done with it. It’s valuable to collect feedback, but the true value for both IT and its customers comes from acting on that feedback and communicating those actions back to your users.
Additional insights:
Insight 1 |
Take the time to define the goals of your transactional survey program before launching it – it’s not as simple as just deploying the default survey of your ITSM tool out of the box. The objectives of the survey – including whether you want to keep a pulse on average satisfaction or immediately act on any negative experiences – will influence a range of key decisions about the survey configuration. |
|---|---|
Insight 2 |
While transactional surveys provide useful indicators of customer satisfaction with specific tickets and interactions, they tend to have low response rates and can leave out many users who may rarely or never contact the service desk, but still have helpful feedback. Include a relationship survey in your customer feedback program to capture a more holistic picture of what your overall user base thinks about the service desk and where you most need to improve. |
Insight 3 |
Satisfaction scores provide valuable data about how your customers feel, but don’t tell you why they feel that way. Don’t neglect the qualitative data you can gather from open-ended comments and questions in both types of satisfaction surveys. Take the time to read through these responses and categorize them in at least a basic way to gain deeper insight and determine where to prioritize your efforts. |
Understand the main types of customer satisfaction surveys, principles for survey design, and best practices for surveying your users.
Phase 1: |
Phase 2: |
Phase 3: |
Phase 4: |
|---|---|---|---|
Understand how to measure customer satisfaction |
Design and implement transactional surveys |
Design and implement relationship surveys |
Analyze and act on feedback |
Transactional |
Relationship |
One-off |
|
|---|---|---|---|
Also known as |
Ticket surveys, incident follow-up surveys, on-going surveys |
Annual, semi-annual, periodic, comprehensive, relational |
One-time, single, targeted |
Definition |
|
|
|
Transactional | Relationship | One-off | |
|---|---|---|---|
Pros |
|
|
|
Cons |
|
|
|
Only relying on one type of survey will leave gaps in your understanding of customer satisfaction. Include both transactional and relationship surveys to provide a holistic picture of customer satisfaction with the service desk.
If you can only start with one type, choose the type that best aligns with your goals and priorities:
If your priority is to identify larger improvement initiatives the service desk can take to improve overall customer satisfaction and trust in the service desk: |
If your priority is to provide customers with the opportunity to let you know when transactions do not go well so you can take immediate action to make improvements: |
| ↓ | ↓ |
Start with a relationship survey |
Start with a transactional survey |

Info-Tech Insight
One-off surveys can be useful to assess whether a specific change has impacted satisfaction, or to inform a planned change/initiative. However, as they aren’t typically part of an on-going customer feedback program, the focus of this research will be on transactional and relationship surveys.
| CSAT | CES | NPS | |
|---|---|---|---|
| Name | Customer Satisfaction | Customer Effort Score | Net Promoter score |
| What it measures | Customer happiness | Customer effort | Customer loyalty |
| Description | Measures satisfaction with a company overall, or a specific offering or interaction | Measures how much effort a customer feels they need to put forth in order to accomplish what they wanted | Single question that asks consumers how likely they are to recommend your product, service, or company to other people |
| Survey question | How satisfied are/were you with [company/service/interaction/product]? | How easy was it to [solve your problem/interact with company/handle my issue]? Or: The [company] made it easy for me to handle my issue | How likely are you to recommend [company/service/product] to a friend? |
| Scale | 5, 7, or 10 pt scale, or using images/emojis | 5, 7, or 10 pt scale | 10-pt scale from highly unlikely to highly likely |
| Scoring | Result is usually expressed as a percentage of satisfaction | Result usually expressed as an average | Responses are divided into 3 groups where 0-6 are detractors, 7-8 are passives, 9-10 are promoters |
| Pros |
|
|
|
| Cons |
|
|
|

While we focus mainly on traditional survey-based approaches to measuring customer satisfaction in this blueprint, there’s no need to limit yourselves to surveys as your only method. Consider multiple techniques to capture a wider audience, including:
Don’t include unnecessary questions that won’t give you actionable information; it will only waste respondents’ time.
Keep each question as short as possible and limit the total number of survey questions to avoid survey fatigue.
Most of your measures will be close-ended, but include at least one comment box to allow for qualitative feedback.
Ensure that question wording is clear and specific so that all respondents interpret it the same way.
You won’t get accurate results if your question leads respondents into thinking or answering a certain way.
Don’t ask about two different things in the same question – it will confuse respondents and make your data hard to interpret.
Response options should include all possible opinions (including “don’t know”) to avoid frustrating respondents.
Pre-populate information where possible (e.g. name, department) and ensure the survey is responsive on mobile devices.
If every question is mandatory, respondents may leave the survey altogether if they can’t or don’t want to answer one question.
Test your survey with your target audience before launching, and incorporate feedback - they may catch issues you didn’t notice.
There are two types of survey fatigue:
Occurs when users are overwhelmed by too many requests for feedback and stop responding.
Occurs when the survey is too long or irrelevant to users, so they grow tired and abandon the survey.
Fight survey fatigue:
Learn why and how to design a simple survey to assess satisfaction with individual service desk transactions (tickets) and a methodology for survey delivery that will improve response rates.
Phase 1: | Phase 2: | Phase 3: | Phase 4: |
|---|---|---|---|
Understand how to measure customer satisfaction | Design and implement transactional surveys | Design and implement relationship surveys | Analyze and act on feedback |
While feedback on transactional surveys is specific to a single transaction, even one negative experience can impact the overall perception of the service desk. Pair your transactional surveys with an annual relationship survey to capture broader sentiment toward the service desk.
Transactional surveys serve several purposes:
| Decision | Considerations | For more guidance, see |
| What are the goals of your survey? | Are you hoping to get an accurate pulse of customer sentiment (if so, you may want to randomly send surveys) or give customers the ability to provide feedback any time they have some (if so, send a survey after every ticket)? | Slide 25 |
| How many questions will you ask? | Keep the survey as short as possible – ideally only one mandatory question. | Slide 26 |
| What questions will you ask? | Do you want a measure of NPS, CES, or CSAT? Do you want to measure overall satisfaction with the interaction or something more specific about the interaction? | Slide 27 |
| What will be the response options/scale? | Keep it simple and think about how you will use the data after. | Slide 28 |
| How often will you send the survey? | Will it be sent after every ticket, every third ticket, or randomly to a select percentage of tickets, etc.? | Slide 29 |
| What conditions would apply? | For example, is there a subset of users who you never want to receive a survey or who you always want to receive a survey? | Slide 30 |
| What mechanism/tool will you use to send the survey? | Will your ITSM tool allow you to make all the configurations you need, or will you need to use a separate survey tool? If so, can it integrate to your ITSM solution? | Slide 30 |
| Decision | Considerations | For more guidance, see |
| What will trigger the survey? | Typically, marking the ticket as either ‘resolved’ or ‘closed’ will trigger the survey. | Slide 31 |
| How long after the ticket is closed will you send the survey? | You’ll want to leave enough time for the user to respond if the ticket wasn’t resolved properly before completing a survey, but not so much time that they don’t remember the ticket. | Slide 31 |
| Will the survey be sent in a separate email or as part of the ticket resolution email? | A separate email might feel like too many emails for the user, but a link within the ticket closure email may be less noticeable. | Slide 32 |
| Will the survey be embedded in email or accessed through a link? | If the survey can be embedded into the email, users will be more likely to respond. | Slide 32 |
| How long will the survey link remain active, and will you send any reminders? | Leave enough time for the user to respond if they are busy or away, but not so much time that the data would be irrelevant. Balance the need to remind busy end users with the possibility of overwhelming them with survey fatigue. | Slide 32 |
| What other text will be in the main body of the survey email and/or thank you page? | Keep messaging short and straightforward and remind users of the benefit to them. | Slide 33 |
| Where will completed surveys be sent/who will have access? | Will the technician assigned to the ticket have access or only the manager? What email address/DL will surveys be sent to? | Slide 33 |
If your objective is: |
|
Keep a continual pulse on average customer satisfaction |
Gain the opportunity to act on negative feedback for any poor experience |
Then: |
|
Send survey randomly |
Send survey after every ticket |
Rationale: |
|
Sending a survey less often will help avoid survey fatigue and increase the chances of users responding whether they have good, bad, or neutral feedback |
Always having a survey available means users can provide feedback every time they want to, including for any poor experience – giving you the chance to act on it. |
Service Managers often get caught up in running a transactional survey program because they think it’s standard practice, or they need to report a satisfaction metric. If that’s your only objective, you will fail to derive value from the data and will only turn customers away from responding.
As you design your survey, keep in mind the following principles:
Q: How many questions should the survey contain?
A: Ideally, your survey will have only one mandatory question that captures overall satisfaction with the interaction.
This question can be followed up with an optional open-ended question prompting the respondent for more details. This will provide a lot more context to the overall rating.
If there are additional questions you need to ask based on your goals, clearly make these questions optional so they don’t deter respondents from completing the survey. For example, they can appear only after the respondent has submitted their overall satisfaction response (i.e. on a separate, thank you page).
Additional (optional) measures may include:
Tips for writing survey questions:
Sample question wording:
How satisfied are you with this support experience?
How would you rate your support experience?
Please rate your overall satisfaction with the way your issue was handled.
Instead of this…. |
Ask this…. |
|---|---|
“We strive to provide excellent service with every interaction. Please rate how satisfied you are with this interaction.” |
“How satisfied were you with this interaction?” |
“How satisfied were you with the customer service skills, knowledge, and responsiveness of the technicians?” |
Choose only one to ask about. |
“How much do you agree that the service you received was excellent?” |
“Please rate the service you received.” |
“On a scale of 1-10, thinking about your most recent experience, how satisfied would you say that you were overall with the way that your ticket was resolved?” |
“How satisfied were you with your ticket resolution?” |
When planning your response options, remember to keep the survey as easy to respond to as possible – this means allowing a one-click response and a scale that’s intuitive and simple to interpret. |
Think about how you will use the responses and interpret the data. If you choose a 10-point scale, for example, what would you classify as a negative vs positive response? Would a 5-point scale suffice to get the same data? |
Again, use your goals to inform your response options. If you need a satisfaction metric, you may need a numerical scale. If your goal is just to capture negative responses, you may only need two response options: good vs bad. |
Common response options:
|
Investigate the capabilities of your ITSM tool. It may only allow one built-in response option style. But if you have the choice, choose the simplest option that aligns with your goals. |
There are two common choices for when to send ticket satisfaction surveys:
After random tickets |
After every ticket |
|
Pros |
|
|
Cons |
|
|
SDI’s 2018 Customer Experience in ITSM survey of service desk professionals found:
Almost two-thirds (65%) send surveys after every ticket.
One-third (33%) send surveys after randomly selected tickets are closed.
Send a survey after every ticket so that anyone who has feedback gets the opportunity to provide it – and you always get the chance to act on negative feedback. But, limit how often any one customer receives a ticket to avoid over-surveying them – restrict to anywhere between one survey a week to one per month per customer.
Decision #1 |
Decision #2 |
|---|---|
What tool will you use to deliver the survey? |
What (if any) conditions apply to your survey? |
Considerations
|
Considerations Is there a subset of users who you never want to receive a survey (e.g. a specific department, location, role, or title)? Is there a subset of users who you always want to receive a survey, no matter how often they contact the service desk (e.g. VIP users, a department that scored low on the annual satisfaction survey, etc.)? Are there certain times of the year that you don’t want surveys to go out (e.g. fiscal year end, holidays)? Are there times of the day that you don’t want surveys to be sent (e.g. only during business hours; not at the end of the day)? |
Recommendations The built-in functionality of your ITSM tool’s surveys will be easiest to send and track; use it if possible. However, if your tool’s survey module is limited and won’t give you the value you need, consider a third-party solution or survey tool that integrates with your ITSM solution and won’t require significant manual effort to send or review the surveys. |
Recommendations If your survey module allows you to apply conditions, think about whether any are necessary to apply to either maximize your response rate (e.g. don’t send a survey on a holiday), avoid annoying certain users, or seek extra feedback from dissatisfied users. |
Decision #2 | Decision #1 |
|---|---|
What will trigger the survey? | When will the survey be sent? |
Considerations
| Considerations
|
Recommendations Only send the survey once you’re sure the issue has actually been resolved; you could further upset the customer if you ask them how happy they are with the resolution if resolution wasn’t achieved. This means sending the survey once the user confirms resolution (which closes ticket) or the agent closes the ticket. | Recommendations If you are sending the survey upon ticket status moving to ‘resolved’, wait at least 24 hours before sending the survey in case the user responds that their issue wasn’t actually resolved. However, if you are sending the survey after the ticket has been verified resolved and closed, you can send the survey immediately while the experience is still fresh in their memory. |
Decision #1 | Decision #2 |
|---|---|
How will the survey appear in email? | How long will the survey remain active? |
Considerations
| Considerations
|
Recommendations Send the survey separately from the ticket resolution email or users will never notice it. However, if possible, have the entire survey embedded within the email so users can click to respond directly from their email without having to open a separate link. Reduce effort, to make users more likely to respond. | Recommendations Leave enough time for the user to respond if they are busy or away, but not so much time that the data will be irrelevant. Balance the need to remind busy end users, with the possibility of overwhelming them with survey fatigue. About a week is typical. |
Decision #1 | Decision #2 |
|---|---|
What will the body of the email/messaging say? | Where will completed surveys be sent? |
Considerations
| Considerations
|
Recommendations Most users won’t read a long message, especially if they see it multiple times, so keep the email short and simple. Tell users you value their feedback, indicate which interaction you’re asking about, and say how long the survey should take. Thank them after they submit and tell them you will act on their feedback. | Recommendations Survey results should be sent to the Service Manager, Customer Experience Lead, or whoever is the person responsible for managing the survey feedback. They can choose how to share feedback with specific agents and the service desk team. |
Most IT organizations see transactional survey response rates of less than 20%.
Source: SDI, 2018SDI’s 2018 Customer Experience in ITSM survey of service desk professionals found that 69% of respondents had survey response rates of 20% or less. However, they did not distinguish between transactional and relationship surveys. |
Reasons for low response rates:
|
“In my experience, single digits are a sign of a problem. And a downward trend in response rate is also a sign of a problem. World-class survey response rates for brands with highly engaged customers can be as high as 60%. But I’ve never seen it that high for internal support teams. In my experience, if you get a response rate of 15-20% from your internal customers then you’re doing okay. That’s not to say you should be content with the status quo, you should always be looking for ways to increase it.” – David O’Reardon, Founder & CEO of Silversix |
Don’t over-survey any one user or they will start to ignore the surveys.
Ask for feedback soon after the ticket was resolved so it’s fresh in the user’s memory.
Keep the survey short, concise, and simple to respond to.
Minimize effort involved as much as possible. Allow users to respond directly from email and from any device.
Experiment with your subject line or email messaging to draw more attention.
Respond to customers who provide feedback – especially negative – so they know you’re listening.
Demonstrate that you are acting on feedback so users see the value in responding.
Once you’ve worked through all the decisions in this step, you’re ready to configure your transactional survey in your ITSM solution or survey tool.
As a starting point, you can leverage Info-Tech’s Transactional Service Desk Survey Templatee to design your templates and wording.
Make adjustments to match your decisions or your configuration limitations as needed.
Refer to the key decisions tables on slides 24 and 25 to ensure you’ve made all the configurations necessary as you set up your survey.

Understand why and how to design a survey to assess overall satisfaction with the service desk across your organization, or use Info-Tech’s diagnostic.
Phase 1: | Phase 2: | Phase 3: | Phase 4: |
|---|---|---|---|
Understand how to measure customer satisfaction | Design and implement transactional surveys | Design and implement relationship surveys | Analyze and act on feedback |
Evaluating service quality in any industry is challenging for both those seeking feedback and those consuming the service: “service quality is more difficult for the consumer to evaluate than goods quality.”
You are in the position of trying to measure something intangible: customer perception, which “result[s] from a comparison of consumer expectations with actual service performance,” which includes both the service outcome and also “the process of service delivery”
(Source: Parasuraman et al, 1985, 42).
Your mission is to design a relationship survey that is:
Annual relationship surveys provide great value in the form of year-over-year internal benchmarking data, which you can use to track improvements and validate the impact of your service improvement efforts.
The Service Quality Model (Parasuraman, Zeithaml and Berry, 1985) shows how perceived service quality is negatively impacted by the gap between expectations for quality service and the perceptions of actual service delivery: Gap 1: Consumer expectation – Management perception gap: Are there differences between your assumptions about what users want from a service and what those users expect? Gap 2: Management perception – Service quality specification gap: Do you have challenges translating user expectations for service into standardized processes and guidelines that can meet those expectations? Gap 3: Service quality specifications – Service delivery gap: Do staff members struggle to carry out the service quality processes when delivering service? Gap 4: Service delivery – External communications gap: Have users been led to expect more than you can deliver? Alternatively, are users unaware of how the organization ensures quality service, and therefore unable to appreciate the quality of service they receive? Gap 5: Expected service – Perceived service gap: Is there a discrepancy between users’ expectations and their perception of the service they received (regardless of any user misunderstanding)? |
![]() |
|---|
Your survey questions about service and support should provide insight into where these gaps exist in your organization
| Decision/step | Considerations |
| Align the relationship survey with your goals | Align what is motivating you to launch the survey at this time and the outcomes it is intended to feed into. |
| Identify what you’re measuring | Clarify the purpose of the questions. Are you measuring feedback on your service desk, specifically? On all of IT? Are you trying to capture user effort? User satisfaction? These decisions will affect how you word your questions. |
| Determine a framework for your survey | Reporting on results and tracking year-over-year changes will be easier if you design a basic framework that your survey questions fall into. Consider drawing on an existing service quality framework to match best practices in other industries. |
| Cover logistical details | Designing a relationship survey requires attention to many details that may initially be overlooked: the survey’s length and timing, who it should be sent to and how, what demographic info you need to collect to slice and dice the results, and if it will be possible to conduct the survey anonymously. |
| Design question wording | It is important to keep questions clear and concise and to avoid overly lengthy surveys. |
| Select answer scales | The answer scales you select will depend on how you have worded the questions. There is a wide range of answer scales available to you; decide which ones will produce the most meaningful data. |
| Test the survey | Testing the survey before widely distributing it is key. When collecting feedback, conduct at least a few in person observations of someone taking the survey to get their unvarnished first impressions. |
| Monitor and maximize your response rate | Ensure success by staying on top of the survey during the period it is open. |
What is motivating you to launch the survey at this time?
Is there a renewed focus on customer service satisfaction? If so, this survey will track the initiative’s success, so its questions must align with the sponsors’ expectations.
Are you surveying customer satisfaction in order to comply with legislation, or directives to measure customer service quality?
What objectives/outcomes will this survey feed into?
What do you need to report on to your stakeholders? Have they communicated any expectations regarding the data they expect to see?
Does the CIO want the annual survey to measure end-user satisfaction with all of IT?
In 1993 the U.S. president issued an Executive Order requiring executive agencies to “survey customers to determine the kind and quality of services they want and their level of satisfaction with existing services” and “post service standards and measure results against them.” (Clinton, 1993)
Examples of Measures |
||
Clarify the purpose of the questions Each question should measure something specific you want to track and be phrased accordingly. |
Are you measuring feedback on the service desk? | Service desk professionalism |
Are you measuring user satisfaction? |
Service desk timeliness |
|
Your customers’ happiness with aspects of IT’s service offerings and customer service |
Trust in agents’ knowledge |
|
Users’ preferred ticket intake channel (e.g. portal vs phone) |
||
Satisfaction with self-serve features |
||
Are you measuring user effort? |
Are you measuring feedback on IT overall? |
Satisfaction with IT’s ability to enable the business |
How much effort your customer needs to put forth to accomplish what they wanted/how much friction your service causes or alleviates |
Satisfaction with company-issued devices |
|
| Satisfaction with network/Wi-Fi | ||
Satisfaction with applications |
As you compose survey questions, decide whether they are intended to capture user satisfaction or effort: this will influence how the question is worded. Include a mix of both.
If your relationship survey covers satisfaction with service support, ensure the questions cover the major aspects of service quality. You may wish to align your questions on support with existing frameworks: for example, the SERVQUAL service quality measurement instrument identifies 5 dimensions of service quality: Reliability, Assurance, Tangibles, Empathy, and Responsiveness (see below). As you design the survey, consider if the questions relate to these five dimensions. If you have overlooked any of the dimensions, consider if you need to revise or add questions.
Service dimension |
Definition |
Sample questions |
|---|---|---|
Reliability |
“Ability to perform the promised service dependably and accurately”1 |
|
Assurance |
“Knowledge and courtesy of employees and their ability to convey trust and confidence”2 |
|
Tangibles |
“Appearance of physical facilities, equipment, personnel, and communication materials”3 |
|
Empathy |
“Caring, individualized attention the firm provides its customers”4 |
|
Responsiveness |
“Willingness to help customers and provide prompt service”5 |
|
Identify who you will send it to Will you survey your entire user base or a specific subsection? For example, a higher education institution may choose to survey students separately from staff and faculty. If you are gathering data on customer satisfaction with a specific implementation, only survey the affected stakeholders. Determine timing Avoid sending out the survey during known periods of time pressure or absence (e.g. financial year-end, summer vacation). Decide upon its length Consider what survey length your users can tolerate. Configure the survey to show the respondents’ progression or their percentage complete. Clearly introduce the survey The survey should begin with an introduction that thanks users for completing the survey, indicates its length and anonymity status, and conveys how the data will be used, along with who the participants should contact with any questions about the survey. Decide upon incentives Will you incentivize participation (e.g. by entering the participants in a draw or rewarding highest-participating department)? |
Collect demographic information Ensure your data can be “sliced and diced” to give you more granular insights into the results. Ask respondents for information such as department, location, seniority, and tenure to help with your trend analysis later. Clarify if anonymous Users may be more comfortable participating if they can do so anonymously (Quantisoft, n.d.). If you promise anonymity, ensure your survey software/ partner can support this claim. Note the difference between anonymity (identity of participant is not collected) and confidentiality (identifying data is collected but removed from the reported results). Decide how to deliver the survey Will you be distributing the survey yourself through your own licensed software (e.g. through Microsoft Forms if you are an MS shop)? Or, will you be partnering with a third-party provider? Is the survey optimized for mobile? Some find up to 1/3 of participants use mobile devices for their surveys (O’Reardon, 2018). |
Use Info-Tech’s Sample Size Calculator to calculate the number of people you need to complete your survey to have statistically representative results.
In the example above, the service desk supports 1000 total users (and sent the survey to each one). To be 95% confident that the survey results fall within 5% of the true value (if every user responded), they would need 278 respondents to complete their survey. In other words, to have a sample that is representative of the whole population, they would need 278 completed surveys. |
Explanation of terms: Confidence Level: A measure of how reliable your survey is. It represents the probability that your sample accurately reflects the true population (e.g. your entire user base). The industry standard is typically 95%. This means that 95 times out of 100, the true data value that you would get if you surveyed the entire population would fall within the margin of error. Margin of Error: A measure of how accurate the data is, also known as the confidence interval. It represents the degree of error around the data point, or the range of values above and below the actual results from a survey. A typical margin of error is 5%. This means that if your survey sample had a score of 70%, the true value if you sampled the entire population would be between 65% and 75%. To narrow the margin of error, you would need a bigger sample size. Population Size: The total set of people you want to study with your survey. For example, the total number of users you support. Sample Size: The number of people who participate in your survey (i.e. complete the survey) out of the total population. |
I need to measure and report customer satisfaction with all of IT:
|
Both products measure end-user satisfaction One is more general to IT One is more specific to service desk |
I need to measure and report more granularly on Service Desk customer satisfaction:
|
Choose Info-Tech's End User Satisfaction Survey |
Choose Info-Tech’s Service Desk Satisfaction Survey |
Write accessible questions: | Instead of this…. | Ask this…. |
48% of US adults meet or exceed PIACC literacy level 3 and thus able to deal with texts that are “often dense or lengthy.” 52% of US adults meet level 2 or lower. Keep questions clear and concise. Avoid overly lengthy surveys. Source: Highlights of the 2017 U.S. PIAAC Results Web Report |
Users will have difficulty perceiving the difference between these two questions. |
|
Tips for writing survey questions: | “How satisfied are you with the customer service skills, knowledge, and responsiveness of the technicians?” This question measures too many things and the data will not be useful. | Choose only one to ask about. |
| “On a scale of 1-10, thinking about the past year, how satisfied would you say that you were overall with the way that your tickets were resolved?” This question is too wordy. | “How satisfied were you with your ticket resolution?” |
Likert scale
Respondents select from a range of statements the position with which they most agree:
E.g. How satisfied are you with how long it generally takes to resolve your issue completely?
Frequency scale
How often does the respondent have to do something, or how often do they encounter something?
E.g. How frequently do you need to re-open tickets that have been closed without being satisfactorily resolved?
Numeric scale
By asking users to rate their satisfaction on a numeric scale (e.g., 1-5, 1-10), you can facilitate reporting on averages:
E.g. How satisfied are you with IS’s ability to provide services to allow the organization to meet its goals?
Forced ranking
Learn more about your users’ priorities by asking them to rank answers from most to least important, or selecting their top choices (Sauro, 2018):
E.g. From the following list, drag and drop the 3 aspects of our service that are most important to you into the box on the right.
Always include an optional open-ended question, which allows customers to provide more feedback or suggestions.
Test the survey with different stakeholder groups:
Testing methodology:
In the survey testing phase, try to capture at least a few real-time responses to the survey. If you collect survey feedback only once the test is over, you may miss some key insights into the user experience of navigating the survey.
“Follow the golden rule: think of your audience and what they may or may not know. Think about what kinds of outside pressures they may bring to the work you’re giving them. What time constraints do they have?”
– Sally Colwell, Project Officer, Government of Canada Pension Centre
“[Send] one reminder to those who haven’t completed the survey after a few days. Don’t use the word ‘reminder’ because that’ll go straight in the bin, better to say something like, ‘Another chance to provide your feedback’”
– David O’Reardon, Founder & CEO of Silversix
Measure and analyze the results of both surveys and build a plan to act on both positive and negative feedback and communicate the results with the organization.
Phase 1: | Phase 2: | Phase 3: | Phase 4: |
|---|---|---|---|
Understand how to measure customer satisfaction | Design and implement transactional surveys | Design and implement relationship surveys | Analyze and act on feedback |

A service failure or a poor experience isn’t what determines customer satisfaction – it’s how you respond to the issue and take steps to fix it that really matters.
This means one poor experience with the service desk doesn’t necessarily lead to an unhappy user; if you quickly and effectively respond to negative feedback to repair the relationship, the customer may be even happier afterwards because you demonstrated that you value them.
“Every complaint becomes an opportunity to turn a bad IT customer experience into a great one.”
– David O’Reardon, Founder & CEO of Silversix
|
![]() |
“Your IT service desk’s CSAT survey should be the means of improving your service (and the employee experience), and something that encourages people to provide even more feedback, not just the means for understanding how well it’s doing” – Joe the IT Guy, SysAid |
If collecting and analyzing customer feedback is something that happens off the side of your desk, it either won’t get done or won’t get done well.
Assign accountability for the customer feedback program to one person (i.e. Service Desk Manager, Service Manager, Infrastructure & Operations Lead, IT Director), who may take on or assign responsibilities such as:
Info-Tech Insight
While feedback can feed into internal coaching and training, the goal should never be to place blame or use metrics to punish agents with poor results. The focus should always be on improving the experience for end users.
Calculating NPS Scores
Categorize respondents into 3 groups:
Calculate overall NPS score:
Calculating CSAT Scores
Why analyze qualitative data |
How to analyze qualitative data |
||||||
|---|---|---|---|---|---|---|---|
|
Methods range in sophistication; choose a technique depending on your tools available and goals of your program.
|
Successful customer satisfaction programs respond effectively to both positive and negative outcomes. Late or lack of responses to negative comments may increase customer frustration, while not responding at all to the positive comments may give the perception of indifference.
E.g. Scores of 1 to 2 out of 5 are negative, scores of 4 to 5 out of 5 are positive.
1. Who should receive communication? |
Each audience will require different messaging, so start by identifying who those audiences are. At a minimum, you should communicate to your end users who provided feedback, your service desk/IT team, and business leaders or stakeholders. |
|---|---|
2. What information do they need? |
End users: Thank them for providing feedback. Demonstrate what you will do with that feedback. IT team: Share results and what you need them to do differently as a result. Business leaders: Share results, highlight successes, share action plan for improvement. |
3. Who is responsible for communication? |
Typically, this will be the person who is accountable for the customer feedback program, but you may have different people responsible for communicating to different audiences. |
4. When will you communicate? |
Frequency of communication will depend on the survey type – relationship or transactional – as well as the audience, with internal communication being much more frequent than end-user communication. |
5. How will you communicate? |
Again, cater your approach to the audience and choose a method that will resonate with them. End users may view an email, an update on the portal, a video, or update in a company meeting; your internal IT team can view results on a dashboard and have regular meetings. |
Based on the Customer Communication Cycle by David O’Reardon, 2018 |
|
|---|
Focus your communications to users around them, not you. Demonstrate that you need feedback to improve their experience, not just for you to collect data.
Prioritize improvements |
Prioritize improvements based on low scores and most commonly received feedback, then build into an action plan. |
|---|---|
Take immediate action on negative feedback |
Investigate the issue, diagnose the root cause, and repair both the relationship and issue – just like you would an incident. |
Apply lessons learned from positive feedback |
Don’t neglect actions you can take from positive feedback – identify how you can expand upon or leverage the things you’re doing well. |
Use feedback in coaching and training |
Share positive experiences with the team as lessons learned, and use negative feedback as an input to coaching and training. |
Make the change stick |
After making a change, train and communicate it to your team to ensure the change sticks and any negative experiences don’t happen again. |
“Without converting feedback into actions, surveys can become just a pointless exercise in number watching.”
Outline exactly what you plan to do to address customer feedback in an action plan, and regularly review that action plan to select and prioritize initiatives and monitor progress.
For more guidance on tracking and prioritizing ongoing improvement initiatives, see the blueprints Optimize the Service Desk with a Shift Left Strategy and Build a Continual Improvement Plan for the Service Desk.
Improve service desk processes: |
Improve end-user self-service options: |
Assess and optimize service desk staffing: |
Improve ease of contacting the service desk: |
|---|---|---|---|
| Standardize the Service Desk | Optimize the Service Desk With a Shift-Left Strategy | Staff the Service Desk to Meet Demand | Improve Service Desk Ticket Intake |
Improve service desk processes: |
Improve end-user self-service options: |
Assess and optimize service desk staffing: |
Improve ease of contacting the service desk:: |
| Improve Incident and Problem Management | Improve Incident and Problem Management | Deliver a Customer Service Training Program to Your IT Department | Modernize and Transform Your End-User Computing Strategy |


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.
Amaresan, Swetha. “The best time to send a survey, according to 5 studies.” Hubspot. 15 Jun 2021. Accessed October 2022.
Arlen, Chris. “The 5 Service Dimensions All Customers Care About.” Service Performance Inc. n.d. Accessed October 2022.
Clinton, William Jefferson. “Setting Customer Service Standards.” (1993). Federal Register, 58(176).
“Understanding Confidentiality and Anonymity.” The Evergreen State College. 2022. Accessed October 2022.
"Highlights of the 2017 U.S. PIAAC Results Web Report" (NCES 2020-777). U.S. Department of Education. Institute of Education Sciences, National Center for Education Statistics.
Joe the IT Guy. “Are IT Support’s Customer Satisfaction Surveys Their Own Worst Enemy?” Joe the IT Guy. 29 August 2018. Accessed October 2022.
O’Reardon, David. “10 Ways to Get the Most out of your ITSM Ticket Surveys.” LinkedIn. 2 July 2019. Accessed October 2022.
O'Reardon, David. "13 Ways to increase the response rate of your Service Desk surveys".LinkedIn. 8 June 2016. Accessed October 2022.
O’Reardon, David. “IT Customer Feedback Management – A Why & How Q&A with an Expert.” LinkedIn. 13 March 2018. Accessed October 2022.
Parasuraman, A., Zeithaml, V. A., & Berry, L. L. (1985). "A Conceptual Model of Service Quality and Its Implications for Future Research." Journal of Marketing, 49(4), 41–50.
Quantisoft. "How to Increase IT Help Desk Customer Satisfaction and IT Help Desk Performance.“ Quantisoft. n.d. Accessed November 2022.
Rumberg, Jeff. “Metric of the Month: Customer Effort.” HDI. 26 Mar 2020. Accessed September 2022.
Sauro, Jeff. “15 Common Rating Scales Explained.” MeasuringU. 15 August 2018. Accessed October 2022.
SDI. “Customer Experience in ITSM.” SDI. 2018. Accessed October 2022.
SDI. “CX: Delivering Happiness – The Series, Part 1.” SDI. 12 January 2021. Accessed October 2022.
Wronski, Laura. “Who responds to online surveys at each hour of the day?” SurveyMonkey. n.d. Accessed October 2022.
Sally Colwell
Project Officer
Government of Canada Pension Centre
There is no one-size-fits-all approach to product delivery. For many organizations product delivery requires detailed project management practices, while for others it requires much less. Taking an outcome-first approach when planning your product transformation is critical to make the right decision on the balance between project and product management.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
The activities in this research will guide you through clarifying how you want to talk about projects and products, aligning project management and agility, specifying the different activities for project management, and identifying key differences with funding of products instead of projects.
7 Step 1.1: Clarify How You Want to Talk About Projects and Products
13 Step 1.2: Align Project Management and Agility
16 Step 1.3: Specify the Different Activities for Project Management
20 Step 1.4: Identify Key Differences in Funding of Products Instead of Projects
26 Bibliography
When moving to more product-centric delivery practices, many assume that projects are no longer necessary. That isn’t necessarily the case!
Product delivery can mean different things to different organizations, and in many cases it can involve the need to maintain both projects and project delivery.
Projects are a necessary vehicle in many organizations to drive value delivery, and the activities performed by project managers still need to be done by someone. It is the form and who is involved that will change the most.
|
Ari Glaizel
|
Your Challenge
|
Common Obstacles
|
Info-Tech’s Approach
|
There is no one-size-fits-all approach to product delivery. For many organizations product delivery requires detailed project management practices, while for others it requires much less. Taking an outcome-first approach when planning your product transformation is critical to make the right decision on the balance between project and product management.
Project“A temporary endeavor undertaken to create a unique product, service, or result. The temporary nature of projects indicates a beginning and an end to the project work or a phase of the project work. Projects can stand alone or be part of a program or portfolio.” (PMBOK, PMI) |
|
Product“A tangible solution, tool, or service (physical or digital) that enables the long-term and evolving delivery of value to customers and stakeholders based on business and user requirements.” (Deliver on Your Digital Product Vision, Info-Tech Research Group) |
Output: Your enterprise/organizational definition of products and projects
Participants: Executives, Product/project managers, Applications teams
Regardless of whether you recognize yourself as a “product-based” or “project-based” shop, the same basic principles should apply.
You go through a period or periods of project-like development to build or implement a version of an application or product.
You also have parallel services along with your project development that encompass the more product-based view. These may range from basic support and maintenance to full-fledged strategy teams or services like sales and marketing.
As your product transformation continues, projects can become optional and needed only as part of your organization’s overall delivery processes
| Project | Product | |
| Fund projects | — Funding –› | Fund teams |
| Line-of-business sponsor | — Prioritization –› | Product owner |
| Project owner | — Accountability –› | Product owner |
| Makes specific changes to a product | —Product management –› | Improves product maturity and support of the product |
| Assignment of people to work | — Work allocation –› | Assignment of work to product teams |
| Project manager manages | — Capacity management –› | Team manages |
Product delivery requires significant shifts in the way you complete development and implementation work and deliver value to your users. Make the changes that support improving end-user value and enterprise alignment.
5-10 minutes
Output: Increased appreciation of the relationship between project and product delivery
Participants: Executives, Product/project managers, Applications teams
In product-centric, Agile teams, many roles that a project manager previously performed are now taken care of to different degrees by the product owner, delivery team, and process manager.
The overall change alters the role of project management from one that orchestrates all activities to one that supports, monitors, and escalates.
5-10 minutes
Output: An assessment of what is in the way to effectively deliver on Agile and product-focused projects
Participants: Executives, Product/project managers, Applications teams
|
|
||||
|
|
5-10 minutes
Output: Current understanding of the role of project management in Agile/product delivery
Participants: Executives, Product/project managers, Applications teams
Project managers still have a role to play in Agile projects and products. Agreeing to what they should be doing is critical to successfully moving to a product-centric approach to delivery.
| Autonomy
Fund what delivers value Fund long-lived delivery of value through products (not projects). Give autonomy to the team to decide exactly what to build. | Flexibility
Allocate iteratively Allocate to a pool based on higher-level business case. Provide funds in smaller amounts to different product teams and initiatives based on need. |
| Accountability
Measure and adjust Product teams define metrics that contribute to given outcomes. Track progress and allocate more (or less) funds as appropriate. | ![]() Info-Tech InsightChanges to funding require changes to product and Agile practices to ensure product ownership and accountability. |
(Adapted from Bain & Company)
| TRADITIONAL PROJECTS WITH WATERFALL DELIVERY | TRADITIONAL PROJECTS WITH AGILE DELIVERY | PRODUCTS WITH AGILE PROJECT DELIVERY | PRODUCTS WITH AGILE DELIVERY | |
WHEN IS THE BUDGET TRACKED? |
Budget tracked by major phases | Budget tracked by sprint and project | Budget tracked by sprint and project | Budget tracked by sprint and release |
HOW ARE CHANGES HANDLED? |
All change is by exception | Scope change is routine; budget change is by exception | Scope change is routine; budget change is by exception | Budget change is expected on roadmap cadence |
WHEN ARE BENEFITS REALIZED? |
Benefits realization post project completion | Benefits realization ongoing throughout the life of the project | Benefits realization ongoing throughout the life of the product | Benefits realization ongoing throughout life of the product |
WHO DRIVES? |
Project Manager
|
Product Owner
|
Product Manager
|
Product Manager
|
| ˆ ˆ
Hybrid Operating Environments |
||||
As you evolve your approach to product delivery, you will be decoupling the expected benefits, forecast, and budget. Managing them independently will improve your ability adapt to change and drive the right outcomes!
Output: Understanding of funding principles and challenges
Participants: Executives, Product owners, Product managers, Project managers, Delivery managers
| Global Digital Financial Services Company
This financial services company looked to drive better results by adopting more product-centric practices.
Results
|
|
|
Deliver on Your Digital Product Vision
Implement Agile Practices That Work
Implement DevOps Practices That Work
Prepare an Actionable Roadmap for Your PMO
|
Deliver Digital Products at Scale
Extend Agile Practices Beyond IT
Spread Best Practices With an Agile Center of Excellence
Tailor IT Project Management Processes to Fit Your Projects
|
Cobb, Chuck. “Are there Project Managers in Agile?” High Impact Project Management, n.d. Web.
Cohn, Mike. “What Is a Product?” Mountain Goat Software, 6 Sept. 2016. Web.
Cobb, Chuck. “Agile Project Manager Job Description.” High Impact Project Management, n.d. Web.
“How do you define a product?” Scrum.org, 4 April 2017. Web.
Johnson, Darren, et al. “How to Plan and Budget for Agile at Scale.” Bain & Company, 8 Oct. 2019. Web.
“Product Definition.” SlideShare, uploaded by Mark Curphey, 25 Feb. 2007. Web.
Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide). 7th ed., Project Management Institute, 2021.
Schuurman, Robbin. “Scrum Master vs Project Manager – An Overview of the Differences.” Scrum.org, 11 Feb 2020. Web.
Schuurman, Robbin. “Product Owner vs Project Manager.” Scrum.org, 12 March 2020. Web.
Vlaanderen, Kevin. “Towards Agile Product and Portfolio Management.” Academia.edu, 2010. Web.
“What is a Developer in Scrum?” Scrum.org, n.d. Web.
“What is a Scrum Master?” Scrum.org, n.d. Web.
“What is a Product Owner?” Scrum.org, n.d. Web.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Use our three-step approach of Organize, Design, and Execute an IT Category Plan to get the most out of your IT budget while proactively planning your vendor negotiations.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
A step-by-step approach to walk you through understanding your current state related to accessibility maturity, identifying your desired future state, and building your business case to seek buy-in. This storyboard will help you figure out what’s right for your organization and build the accessibility business case for IT.
The business case for accessibility is strong. Use this template to communicate to senior leaders the benefits, challenges, and risks of inaction.
This tool uses a capability maturity model framework to evaluate your current state of accessibility. Maturity level is assessed on three interconnected aspects (people, process, and technology) across six dimensions proven to impact accessibility. Complete the assessment to get recommendations based on where you’re at.
Accessibility is important for individuals, businesses, and society. Diverse populations need diverse access, and it’s essential to provide access and opportunity to everyone, including people with diverse abilities. In fact, access to information and communications technologies (ICT) is a basic human right according to the United Nations.
The benefits of ICT accessibility go beyond compliance. Many innovations that we use in everyday life, such as voice activation, began as accessibility initiatives and ended up creating a better lived experience for everyone. Accessibility can improve user experience and satisfaction, and it can enhance your brand, drive innovation, and extend your market reach (WAI, 2022).
Although your organization might be required by law to ensure accessibility, understanding your users’ needs and incorporating them into your processes early will determine success beyond just compliance.
Heather Leier-Murray
Senior Research Analyst, People and Leadership
Info-Tech Research Group
| Your Challenge | Common Obstacles | Info-Tech’s Approach |
|
Global IT and business leaders are challenged to make digital products and services accessible because inaccessibility comes with increasing risk to brand reputation, legal ramifications, and constrained market reach.
|
Understanding where to start, where accessibility lives, and if or when you’re done can be overwhelmingly difficult.
Conventional approaches to accessibility often fail because users are expected to do the hard work. You have to be doing 80% of the hard work.1 |
Use Info-Tech’s research and resources to do what’s right for your organization. This framework takes away the overwhelm that many feel when they hear “accessibility” and makes the steps for your organization approachable.
|
1. Harvard Business Review, 2021
Info-Tech Insight
The longer you put off accessibility, the more tech debt you accumulate and the more you risk losing access to new and existing markets. The longer you wait to adopt standards and best practices, the more interest you’ll accumulate on accessibility barriers and costs for remediation.
The cost of inaction related to accessibility is rising. Preparing for accessibility earlier helps prevent tech debt; the longer you wait to address your accessibility obligations, the more costly it gets.
More than 3,500 digital accessibility lawsuits were filed in the US in 2020, up more than 50% from 2018.
Source: UsableNet. Inc.
These barriers make accessibility difficult to address for many organizations:
1. Smashing Magazine
2. Harvard Business Review, 2021
90% of companies claim to prioritize diversity.
Source: Harvard Business Review, 2020
Only 4% of those that claim to prioritize diversity consider disability in those initiatives.
Source: Harvard Business Review, 2020
WCAG (Web Content Accessibility Guidelines) identifies four principles of accessibility. WCAG is the most referenced standard in website accessibility lawsuits.
Source: eSSENTIAL Accessibility, 2022
Top three reasons:
| 61% | 62% | 78% |
|---|---|---|
| To comply with laws | To provide the best UX | To include people with disabilities |
Source: Level Access
Still, most businesses aren’t meeting compliance standards. Even though legislation has been in place for over 30 years, a 2022 study by WebAIM of 1,000,000 homepages returned a 96.8% WCAG 2.0 failure rate.
Source: Institute for Disability Research, Policy, and Practice
43% rated it as a top priority.
36% rated it as important.
Fewer than 5% rated as either low priority or not even on the radar.
More than 65% agreed or strongly agreed it’s a higher priority than last year.
Source: Angel Business Communications
Source: Statistics Canada
Merriam-Webster defines disability as a “physical, mental, cognitive, or developmental condition that impairs, interferes with, or limits a person’s ability to engage in certain tasks or actions or participate in typical daily activities and interactions.”1
The World Health Organization (WHO) points out that a crucial part of the definition of disability is that it’s not just a health problem, but the environment impacts the experience and extent of disability. Inaccessibility creates barriers for full participation in society.2
The likelihood of you experiencing a disability at some point in your life is very high, whether a physical or mental disability, seen or unseen, temporary or permanent, severe or mild.2
Many people acquire disabilities as they age yet may not identify as “a person with a disability.”3 Where life expectancies are over 70 years of age, 11.5% of life is spent living with a disability. 4
“Extreme personalization is becoming the primary difference in business success, and everyone wants to be a stakeholder in a company that provides processes, products, and services to employees and customers with equitable, person-centered experiences and allows for full participation where no one is left out.”
– Paudie Healy, CEO, Universal Access
1. Merriam-Webster
2. World Health Organization
3. Digital Leaders, as cited in WAI, 2018
4. Disabled World, as cited in WAI, 2018
Common myths about people with disabilities:
These assumptions prevent organizations from hiring valuable people into the workforce and retaining them.
Source: Forbes
50% to 70% of people with disabilities are unemployed in industrialized countries. In the US alone, 61 million adults have a disability.
Source: United Nations, as cited in Forbes
| 1. Understand Current State | 2. Plan for Buy-in | 3. Prepare Your Business Case | |
| Phase Steps |
|
|
|
| Phase Outcomes |
|
|
|
| Insight 1 | The longer you put off accessibility, the more tech debt you accumulate and the more you risk losing access to new and existing markets. The longer you wait to adopt standards and best practices, the more interest you’ll accumulate on accessibility barriers and costs for remediation. | |
| Insight 2 | Implementing accessibility feels counterintuitive to IT departments. IT always wants to optimize and move forward, but with accessibility you may stay at one level for what feels like an uncomfortably long period. Don’t worry; building consistency and shifting culture takes time. | |
| Insight 3 | Accessibility goes beyond compliance, which should be an outcome, not the objective. With 1 billion people worldwide with some form of disability, nearly everyone likely has a connection to disability, whether it be in themselves, family, or colleagues. The market of people with disabilities has a spending power of more than $6 trillion.1 |
1. WAI, 2018
This blueprint is accompanied by supporting deliverables to help you accomplish your goals.
Accessibility Business Case Template
The business case for accessibility is strong. Use this template to communicate to senior leaders the benefits and challenges of accessibility and the risks of inaction.
Accessibility Maturity Assessment
Use this assessment to understand your current accessibility maturity.
| Business Benefits | IT Benefits |
|---|---|
|
|
In phase 2 of this blueprint, we will help you establish current-state and target-state metrics for your organization.
Suggested Metrics
Overall end-customer satisfaction
Monies saved through cost optimization efforts
Employee engagement
Monies save through application rationalization and standardization
For more metrics ideas, see the Info-Tech IT Metrics Library.
INDUSTRY
Technology
SOURCE
W3C Web Accessibility Initiative (WAI), 2018
Investing in accessibility
With an innovative edge, Google invests in accessibility with the objective of making life easier for everyone. Google has created a broad array of accessibility innovations in its products and services so that people with disabilities get as much out of them as anyone else.
Part of Google’s core mission, accessibility means more to Google than implementing fixes. It is viewed positively by the organization and drives it to be more innovative to make information available to everyone. Google approaches accessibility problems not as barriers but as ways to innovate and discover breakthroughs that will become mainstream in the future.
Results
Among Google’s innovations are contrast minimums, auto-complete, voice-control, AI advances, and machine learning auto-captioning. All of these were created for accessibility purposes but have positively impacted the user experience in general for Google.
| 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 are used throughout all four options.
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 4 to 6 calls over the course of 2 to 4 months.
| Phase 1 | Phase 2 | Phase 3 |
|---|---|---|
|
Call #1: Discuss motivation for the initiative and foundational knowledge requirements. Call #2: Discuss next steps to assess current accessibility maturity. |
Call #3: Discuss stakeholder engagement and future-state analysis. Call #4: Discuss defining goals and objectives, along with roles and responsibilities. |
Call #5: Review draft business case presentation. Call #6: Discuss post-approval steps and timelines. |
Phase 1
1.1 Understand standards and legislation
1.2 Build awareness
1.3 Understand maturity level
Phase 2
2.1 Define desired future state
2.2 Define goals and objectives
2.3 Document roles and responsibilities
Phase 3
3.1 Prepare business case template for presentation and approval
3.2 Validate post-approval steps and establish timelines
The Accessibility Business Case for IT
This phase will walk you through the following activities:
Activities
1.1.1 Make a list of the legislation you need to comply with
1.1.2 Seek legal and/or professional services’ input on compliance
1.1.3 Detail the risks of inaction for your organization
Understand Your Current State
Outcomes of this step
You will gain foundational understanding of the breadth of the regulation requirements for your organization. You will have reviewed and understand what is applicable to your organization.
Canada
Europe
United States
New Zealand
Australia
Regulatory systems are moving toward an international standard.
| a) | Start by looking at your local legislation. |
| b) | Then consider any other regions you conduct business in. |
| c) | Also account for the various industries you are in. |
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
Beyond the costs resulting from a claim, noncompliance can damage your organization in several ways.
|
Financial Impact ADA Warning Shot: A complaint often indicates pending legal action to come. Addressing issues on a reactive, ad hoc basis can be quite expensive. It can cost almost $10,000 to address a single complaint, and chances are if you have one complaint, you have many. Lawsuit Costs: In the US, 265,000 demand letters were sent in 2020 under the ADA for inaccessible websites. On average, a demand letter could cost the company $25,000 (conservatively). These are low-end numbers; another estimate is that a small, quickly settled digital accessibility lawsuit could cost upwards of $350,000 for the defendant. |
Non-Financial Impact Reputational Impact: Claims brought upon a company can bring negative publicity with them. In contrast, having a clear commitment to accessibility demonstrates inclusion and can enhance brand image and reputation. Stakeholder expectations are changing, and consumers, investors, and employees alike want to support businesses with a purpose. Technology Resource Strains: Costly workarounds and ad hoc accommodation processes take away from efficiency and effectiveness. Updates and redesigns for accessibility and best practices will reduce costs associated with maintenance and service, including overall stakeholder satisfaction improvements. Access to Talent: 2022 saw a record high number of job openings, over 11.4 million in the US alone. Ongoing labor shortages require eliminating bias and keeping an open mind about who is qualified. |
Source: May Hopewell
In the last four years, 83% of the retail 500 have been sued. Since 2018, 417 of the top 500 have received ADA-based digital lawsuits.
Source: UsableNet
| a) | Consider legal risks, consumer risks, brand risks, and employee risks. (Remember, risks aren’t just monetary.) |
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
Activities
1.2.1 Identify gaps in understanding
1.2.2 Brainstorm how to reframe accessibility positively
Understand Your Current State
Outcomes of this step
You’ll have a better understanding of accessibility so that you can effectively implement and promote it.
First-hand experience of how people with disabilities interact with your organization is often eye-opening. It will help you understand the benefits and value of accessibility.
Where to look for understanding
Source: WAI, 2016
* Remember, people with disabilities aren't obligated to discuss or explain their disabilities and may not be comfortable sharing. If you're asking for their time, be respectful, only ask if appropriate, and accept a "no" answer if the person doesn't wish to assist.
Find out what accessibility is and why it is important. Learn the basics.
| a) | What is accessibility? Why is it important? |
| b) | From the legislation and standards identified in step 1.1, what gaps exist? |
| c) | What is the definition of disability? |
| d) | How does your organization currently address accessibility? |
| e) | What are your risks? |
| f) | Do you have any current employees who have disabilities? |
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
A clear understanding of accessibility and the related standards and regulations can turn accessibility from something big and scary to an achievable part of the business.
The benefits of accessibility are:
| Market Reach | Minimized Legal Risks | Innovation | Retention |
|---|---|---|---|
| Over 1 billion people with a spending power of $6 trillion make up the global market of people with disabilities.1 Accessibility improves the experience for all users. In addition, many organizations require you to provide proof you meet accessibility standards during the RFP process. | Accessibility regulations are changing, and claims are rising. Costs associated with legal proceedings can be more than just financial. Many countries have laws you need to follow. | People with disabilities bring diversity of thought, have different lived experiences, and benefit inclusivity, which helps drive engagement. Plus accessibility features often solve unanticipated problems. | Employing and supporting people with disabilities can reduce turnover and improve retention, reliability, company image, employee loyalty, ability awareness, and more. |
Source 1: WAI, 2018
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
A first step to disability and accessibility awareness is to talk about it. When it is talked about as freely as other things are in the workplace, this can create a more welcoming workplace.
Accessibility goes beyond physical access and includes technological access and support as well as our attitudes.
Accessibility is making sure everyone (disabled or abled) can access the workplace equally.
Adjustments in the workplace are necessary to create an accessible and welcoming environment. Understanding the three dimensions of accessibility in the workplace is a good place to start.
Source: May Hopewell
Three dimensions of accessibility in the workplace
INDUSTRY
Professional Services
SOURCE
Accenture
Accenture takes an inclusive approach to increase accessibility.
|
Accessibility is more than tools Employee experience was the focus of embarking on the accessibility journey, ensuring inclusivity was built in and every employee was able to use the tools they needed and could achieve their goals. "We are removing barriers in technology to make all of our employees, regardless of their ability, more productive.” |
Accessibility is inclusive The journey began with formalizing a Global IT Accessibility practice and defining an accessibility program charter. This provided direction and underpinned the strategy used to create a virtual Accessibility Center of Excellence and map out a multiyear plan of initiatives. The team then identified all the technologies they wanted to enhance by prioritizing ones that were high use and high impact. Involving disability champions gave insight into focus areas. |
Accessibility is innovation Working with partners like Microsoft and over 100 employees, Accenture continues toward the goal of 75% accessibility for all its global high-traffic internal platforms. Achievements thus far include:
|
Activities
1.3.1 Complete the Accessibility Maturity Assessment
Understand Your Current State
Outcomes of this step
Completed Accessibility Maturity Assessment to inform planning for and building your business case in Phases 2 and 3.
Accessibility Maturity
People
Process
Technology
| INITIAL | DEVELOPING | DEFINED | MANAGED | OPTIMIZE |
|---|---|---|---|---|
| At this level, accessibility processes are mostly undocumented, if they exist. Accessibility is most likely happening on a reactive, ad hoc basis. No one understands who is responsible for accessibility or what their role is. At this stage the organization is driven by the need for compliance. | At the developing level, the organization is taking steps to increase accessibility but still has a lot of opportunity for improvements. The organization is defining and refining processes and is working toward building a library of assistive tools. | At this level, processes related to accessibility are repeatable. However, there’s a tendency to resort to old habits under stress. The organization has tools in place to facilitate accommodation requests and technology is compatible with assistive technologies. Accessibility initiatives are driven by the desire to make the user experience better. | The managed level is defined by its effective accessibility controls, processes, and metrics. The organization can mostly anticipate preferences of customers, employees, and users. The roles and responsibilities are defined, and disability is included as part of the organization’s diversity, equity, and inclusion (DEI) initiatives. | This level is not the goal for all organizations. At this level there is a shift in the organization’s culture to a feeling of belonging. The organization also demonstrates ongoing process improvements. Everyone can experience a seamless interaction with the organization. The focus is on continuous improvement and using feedback to inform future initiatives. |
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
Phase 1
1.1 Understand standards and legislation
1.2 Build awareness
1.3 Understand maturity level
Phase 2
2.1 Define desired future state
2.2 Define goals and objectives
2.3 Document roles and responsibilities
Phase 3
3.1 Prepare business case template for presentation and approval
3.2 Validate post-approval steps and establish timelines
The Accessibility Business Case for IT
This phase will walk you through the following activities:
This phase involves the following participants:
Activities
2.1.1 Identify key stakeholders
2.1.2 Hold a key stakeholder focus group
2.1.3 Conduct a future-state analysis
Outcomes of this step
Following this step, you will have identified your aspirational maturity level and what your accessibility future state looks like for your organization.
Plan for Senior Leader Buy-In
Ask stakeholders, “Who else should I be talking to?” to discover additional stakeholders and ensure you don’t miss anyone.
| Identify stakeholders through the following questions: |
|---|
|
| Take a 360-degree view of potential internal and external stakeholders who might be impacted by the initiative. |
|---|
|
A stakeholder prioritization map helps teams categorize their stakeholders by their level of influence and ownership.
There are four areas in the map, and the stakeholders within each area should be treated differently.
Players – Players have a high interest in the initiative and the influence to effect change over the initiative. Their support is critical, and a lack of support can cause significant impediment to the objectives.
Mediators – Mediators have a low interest but significant influence over the initiative. They can help to provide balance and objective opinions to issues that arise.
Noisemakers – Noisemakers have low influence but high interest. They tend to be very vocal and engaged, either positively or negatively, but have little ability to enact their wishes.
Spectators – Generally, spectators are apathetic and have little influence over or interest in the initiative.
Each group of stakeholders draws attention and resources away from critical tasks.
By properly identifying your stakeholder groups, you can develop corresponding actions to manage stakeholders in each group. This can dramatically reduce wasted effort trying to satisfy Spectators and Noisemakers while ensuring the needs of the Mediators and Players are met.
| Type | Quadrant | Actions |
|---|---|---|
| Players | High influence, high interest | Actively Engage Keep them engaged through continuous involvement. Maintain their interest by demonstrating their value to its success. |
| Mediators | High influence, low interest | Keep Satisfied They can be the game changers in groups of stakeholders. Turn them into supporters by gaining their confidence and trust, and include them in important decision-making steps. In turn, they can help you influence other stakeholders. |
| Noisemakers | Low influence, high interest | Keep Informed Try to increase their influence (or decrease it if they are detractors) by providing them with key information, supporting them in meetings, and using Mediators to help them. |
| Spectators | Low influence, low interest | Monitor They are followers. Keep them in the loop by providing clarity on objectives and status updates. |
Collect this information by:
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Involve key stakeholders to determine the organizational drivers of accessibility, identify target maturity and key performance indicators (KPIs), and ultimately build the project charter.
Building the project charter as a group will help you to clarify your key messages and secure buy-in from critical stakeholders up-front, which is key.
Executing the business case for accessibility requires significant involvement from your IT leadership team. The challenge is that accessibility can be overwhelming because of inherent bias. Members of your IT leadership team will also need to participate in knowledge transfer, so get them involved up-front. The focus group will help stakeholders feel more engaged in the project, which is pivotal for success.
You may feel like a full project charter isn’t necessary, and depending on your organizational size, it might not be. However, the exercise of building the charter is important regardless. No matter your current climate, some level of socializing the value of and plans for accessibility will be necessary.
Meeting Agenda
Identify the pain points you want to resolve and some of the benefits that you’d like to see from a program. By doing so, you’ll get a holistic view of what you need to achieve and what your drivers are.
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
The Info-Tech Accessibility Maturity Framework identifies three key strategic drivers: compliance, experience, and incorporation.
Even though 90% of companies claim to prioritize diversity,1 over 30% are focused on compliance.2
1. Harvard Business Review, 2020
2. Harvard Business Review, 2022
31.6% of companies remain in the Compliant stage, where they are focused on DEI compliance and not on integrating DEI throughout the organization or on creating continual improvement.
Source: Harvard Business Review, 2022
Although there will be various motivating factors, aligning the drivers of your accessibility program provides direction to the program. Connecting the advantages of program drivers to organizational goals builds the confidence of senior leaders and decision makers, increasing the continued commitment to invest in accessibility programming.
| Drivers | Compliance | Experience | Incorporation | ||
|---|---|---|---|---|---|
| Maturity level | Initial | Developing | Defined | Managed | Optimized |
| Description | Any accessibility initiative is to comply with the minimum legislated requirement. Desire to avoid/decrease legal risk. | Accessibility initiatives are focused on improving the experience of everyone from the start. Most organizations will be experience driven. Desire to increase accessibility and engagement. | Accessibility is a seamless part of the whole organization and initiatives are focused on impacting social issues. | ||
| Advantages | Compliance is a good starting place for accessibility. It will reduce legal risk. | Being people focused from the start of processes enables the organization to reduce tech debt, provide the best user experience, and realize other benefits of accessibility. | There is a sense of belonging in the organization. The entire organization experiences the benefits of accessibility. | ||
| Disadvantages | Accessibility is about more than just compliance. Being compliance driven won’t give you the full benefits of accessibility. | This can mean a culture change for the organization, which can take a long time. IT is used to moving quickly – it might feel counterintuitive to slow down and take time. | It takes much longer to reach the associated level of maturity. Not possible for all organizations. | ||
After initially ensuring your organization is compliant with regulations and standards, you will progress to building disciplined process and consistent standardized processes. Eventually you will build the ability for predictable process, and lastly, you’ll optimize by continuously improving.
Depending on the level of maturity you are trying to achieve, it could take months or even years to implement. The important thing to understand, however, is that accessibility work is never done.
At all levels of the maturity framework, you must consider the interconnected aspects of people, process, and technology. However, as the organization progresses, the impact will shift from largely being focused on process and technology improvement to being focused on people.
Info-Tech Insight
IT typically works through maturity frameworks from the bottom to the top, progressing at each level until they reach the end. When it comes to digital accessibility initiatives, being especially thorough, thoughtful, and collaborative is critical to success. This will mean spending more time in the Developing, Defined, and Managed levels of maturity rather than trying to reach Optimized as quickly as you can. This may feel contrary to what IT historically considers as a successful implementation.
| Driver | Description | Benefits | |
|---|---|---|---|
| Initial | Compliance |
|
|
| Developing | Experience |
|
|
| Defined | Experience |
|
|
| Managed | Experience |
|
|
| Optimized | Incorporation |
|
|
Identify your target state of maturity
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
Accessibility as a differentiator
INDUSTRY
Financial
SOURCE
WAI-Engage
|
Accessibility inside and out As a financial provider, Barclays embarked on the accessibility journey to engage customers and employees with the goal of equal access for all. One key statement that provided focus was “Essential for some, easier for all. ” “It's about helping everyone to work, bank and live their lives regardless of their age, situation, abilities or circumstances.” |
Embedding into experiences “The Barclays Accessibility team [supports] digital teams to embed accessibility into our services and culture through effective governance, partnering, training and tools. Establishing an enterprise-wide accessibility strategy, standards and programmes coupled with senior sponsorship helps support our publicly stated ambition of becoming the most accessible and inclusive FTSE company.” – Paul Smyth, Head of Digital Accessibility, Barclays |
It’s a circle, not a roadmap
|
Activities
2.2.1 Create a list of goals and objectives
2.2.2 Finalize key metrics
Plan for Senior Leader Buy-In
Outcomes of this step
You will have clear measurable goals and objectives to respond to identified accessibility issues and organizational goals.
Use the SMART framework to build effective goals.
| S | Specific: Is the goal clear, concrete, and well defined? |
| M | Measurable: How will you know when the goal is met? |
| A | Achievable: Is the goal possible to achieve in a reasonable time? |
| R | Relevant: Does this goal align with your responsibilities and with departmental and organizational goals? |
| T | Time-based: Have you specified a time frame in which you aim to achieve the goal? |
SMART is a common framework for setting effective goals. Make sure your goals satisfy these criteria to ensure you can achieve real results.
Use the outcomes from activity 2.1.2.
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
Use the outcomes from activity 2.1.2.
Baseline metrics will be improved through:
| Metric | Current | Goal |
| Overall end-customer satisfaction | 90 | 120 |
| Monies saved through cost optimization efforts | ||
| Employee engagement | ||
| Monies save through application rationalization and standardization |
For more metrics ideas, see the Info-Tech IT Metrics Library.
Finalize key metrics the organization will use to measure accessibility success
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
Activities
2.3.1 Populate a RACI chart
Plan for Senior Leader Buy-In
Outcomes of this step
At the end of this step, you will have a completed RACI chart documenting the roles and responsibilities related to accessibility for your accessibility business case.
Populate a RACI chart to identify who should be responsible, accountable, consulted, and informed for each key activity.
Define who is responsible, accountable, consulted, and informed for the project team:
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
Phase 1
1.1 Understand standards and legislation
1.2 Build awareness
1.3 Understand maturity level
Phase 2
2.1 Define desired future state
2.2 Define goals and objectives
2.3 Document roles and responsibilities
Phase 3
3.1 Prepare business case template for presentation and approval
3.2 Validate post-approval steps and establish timelines
The Accessibility Business Case for IT
This phase will walk you through the following activities:
This phase involves the following participants:
Source: WAI, 2018
“Many organizations are waking up to the fact that embracing accessibility leads to multiple benefits – reducing legal risks, strengthening brand presence, improving customer experience and colleague productivity.”
– Paul Smyth, Head of Digital Accessibility, Barclays
Source: WAI, 2018
Activities
3.1.1 Prepare your business case template for presentation and approval
Build Your Business Case
Outcomes of this step
Following this step, you will have a customized business case presentation that you can present to senior leaders.
Obtain approval for your accessibility program by customizing Info-Tech’s Accessibility Business Case Template, which is designed to effectively convey your key messages. Tailor the template to suit your needs.
It includes:
Info-Tech Insight
The support of senior leaders is critical to the success of your accessibility program development. Remind them of the benefits and impact and the risks associated with inaction.
Download the Accessibility Business Case Template
Now that you understand your current and desired accessibility maturity, the next step is to get sign-off to begin planning your initiatives.
Know your audience:
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Download the Accessibility Business Case Template
Activities
3.2.1 Prepare for implementation: Complete the implementation prep to-do list and assign proposed timelines
Build Your Business Case
Outcomes of this step
This step will help you gain leadership’s approval to move forward with building and implementing the accessibility program.
Complete the to-do list to ensure you are ready to move your accessibility program forward.
| To Do | Proposed Timeline |
| Reach out to your change management team for assistance. | |
| Discuss your plan with HR. | |
| Build a project team. | |
| Incorporate any necessary changes from senior leaders into your business case. | |
| [insert your own addition here] | |
| [insert your own addition here] | |
| [insert your own addition here] | |
| [insert your own addition here] |
Use the implementation prep to-do list to make sure you have gathered relevant information and completed critical steps to be ready for success.
Use the list on the previous slide to make sure you are set up for implementation success and that you’re ready to move your accessibility program forward.
| Input | Output |
|---|---|
|
|
| Materials | Participants |
|
|
Implement and Mature Your User Experience Design Practice
Modernize Your Corporate Website to Drive Business Value
IT Diversity & Inclusion Tactics
“2021 State of Digital Accessibility.” Level Access, n.d. Accessed 10 Aug. 2022
”2022 Midyear Report: ADA Digital Accessibility Lawsuits.” UsableNet, 2022. Accessed 9 Nov. 2022
“Barclay’s Bank Case Study.” WAI-Engage, 12 Sept. 2018. Accessed 7 Nov. 2022.
Bilodeau, Howard, et al. “StatCan COVID-19 Data to Insights for a Better Canada.” Statistics Canada, 24 June 2021. Accessed 10 Aug. 2022.
Casey, Caroline. “Do Your D&I Efforts Include People With Disabilities?” Harvard Business Review, 19 March 2020. Accessed 28 July 2022.
Digitalisation World. “Organisations failing to meet digital accessibility standards.” Angel Business Communications, 19 May 2022. Accessed Oct. 2022.
“disability.” Merriam-Webster.com Dictionary, Merriam-Webster, https://www.merriam-webster.com/dictionary/disability. Accessed 10 Aug. 2022.
“Disability.” World Health Organization, 2022. Accessed 10 Aug 2022.
“Driving the Accessibility Advantage at Accenture.” Accenture, 2022. Accessed 7 Oct. 2022.
eSSENTIAL Accessibility. The Must-Have WCAG 2.1 Checklist. 2022
Hopewell, May. Accessibility in the Workplace. 2022.
“Initiate.” W3C Web Accessibility Initiative (WAI), 31 March 2016. Accessed 18 Aug. 2022.
Kalcevich, Kate, and Mike Gifford. “How to Bake Layers of Accessibility Testing Into Your Process.” Smashing Magazine, 26 April 2021. Accessed 31 Aug. 2022.
Noone, Cat. “4 Common Ways Companies Alienate People with Disabilities.” Harvard Business Review, 29 Nov. 2021. Accessed Jul. 2022.
Taylor, Jason. “A Record-Breaking Year for ADA Digital Accessibility Lawsuits.” UsableNet, 21 December 2020. Accessed Jul. 2022.
“The Business Case for Digital Accessibility.” W3C Web Accessibility Initiative (WAI), 9 Nov. 2018. Accessed 4 Aug. 2022.
“The WebAIM Million.” Web AIM, 31 March 2022. Accessed 28 Jul. 2022.
Washington, Ella F. “The Five Stages of DEI Maturity.” Harvard Business Review, November - December 2022. Accessed 7 Nov. 2022.
Wyman, Nicholas. “An Untapped Talent Resource: People With Disabilities.” Forbes, 25 Feb. 2021. Accessed 14 Sep. 2022.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Create your minimum viable business architecture.
If there are a handful of capabilities that your business needs to focus on right now, what are they?
Identify business opportunities.
Enrich your capability model.
There are many challenges for I&O when it comes to digital transformation, including:
These and many more will hinder your progress, which demonstrates the need to invest in modernizing your infrastructure, investing in training and hiring talent, and cultivating a culture that supports digital transformation.
By using the framework of culture, competencies, collaboration and capabilities, organizations can create dimensions in their I&O structure in order to shift from traditional infrastructure management to becoming a strategic enabler, driving agility, innovation, and operational excellence though the effective integration of people, process, and technology.
By driving a customer-centric approach, delivering a successful transformation can be tailored to the business goals and drive adoption and engagement. Refining your roadmap through data and analytics will drive this change. Use third-party expertise to guide your transformation and help build that vision of the future.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Unlock the full potential of your infrastructure with a digital transformation strategy and clear the barriers to success.
Many businesses fail in their endeavors to complete a digital transformation, but the reasons are complex, and there are many ways to fail, whether it is people, process, or technology. In fact, according to many surveys, 70% of digital transformations fail, and it’s mainly down to strategy – or the lack thereof.
A lot of organizations think of digital transformation as just an investment in technology, with no vision of what they are trying to achieve or transform. So, out of the gate, many organizations fail to undergo a meaningful transformation, change their business model, or bring about a culture of digital transformation needed to be seriously competitive in their given market.
When it comes to I&O leaders who have been given a mandate to drive digital transformation projects, they still must align to the vision and mission of the organization; they must still train and hire staff that will be experts in their field; they must still drive process improvements and align the right technology to meet the needs of a digital transformation.
Principal Research Director, I&O
Info-Tech Research Group
Digital transformation requires I&O teams to shift from traditional infrastructure management to becoming a strategic enabler, driving agility, innovation, and operational excellence through effective integration of people, process, and technology.
Collaboration is a key component of I&O – Promote strong collaboration between I&O and other business functions. When doing a digital transformation, it is clear that this is a cross-functional effort. Business leaders and IT teams need to align their objectives, prioritize initiatives, and ensure that you are seamlessly integrating technologies with the new business functions.
Embrace agility and adaptability as core principles – As the digital landscape continues to evolve, it is paramount that I&O leaders are agile and adaptable to changing business needs, adopting new technology and implementing new innovative solutions. The culture of continuous improvement and openness to experimentation and learning will assist the I&O leaders in their journey.
Future-proof your infrastructure and operations – By anticipating emerging technologies and trends, you can proactively plan and organize your team for future needs. By investing in scalable, flexible infrastructure such as cloud services, automation, AI technologies, and continuously upskilling the IT staff, you can stay relevant and forward-looking in the digital space.
An IT infrastructure maturity assessment is a foundational step in the journey of digital transformation. The demand will be on performance, resilience, and scalability. IT infrastructure must be able to support innovation and rapid deployment of services.
Having a clear strategy, with leadership commitment along with hiring and training the right people, monitoring and measuring your progress, and ensuring it is a business-led journey will increase your chances of success.
Your ChallengeThere are a lot of challenges for I&O when it comes to digital transformation, including:
These and many more will hinder your progress, which demonstrates the need to invest in modernizing your infrastructure, investing in training and hiring talent, and cultivating a culture that supports digital transformation. |
Common ObstaclesMany obstacles to digital transformation begin with non-I&O activities, including:
By addressing these obstacles, I&O will have a better chance of a successful transformation and delivering the full potential of digital technologies. |
Info-Tech's ApproachBuilding a culture of innovation by developing clear goals and creating a vision will be key.
By completing the Info-Tech digital readiness questionnaire, you will see where you are in terms of maturity and areas you need to concentrate on. |
By driving a customer-centric approach, delivering a successful transformation can be tailored to the business goals and drive adoption and engagement. Refining your roadmap through data and analytics will drive this change. Use third-party expertise to guide your transformation and help build that vision of the future.
The challenges that stand in the way of your success, and what is needed to reverse the risk
26% of those CIOs surveyed cite resistance to change, with entrenched viewpoints demonstrating a real need for a cultural shift to enhance the digital transformation journey.
Source: Prophet, 2019.
70% of digital transformation projects fall short of their objectives – even when their leadership is aligned, often with serious consequences.
Source: BCG, 2020.
Having a clear strategy and commitment from leadership, hiring and training the right people, monitoring and measuring your progress, and ensuring it is a business-led journey will increase your chances of success.
Info-Tech InsightCultural change, business alignment, skills training, and setting a clear strategy with KPIs to demonstrate success are all key to being successful in your digital journey.
57% of small business owners feel they must improve their IT infrastructure to optimize their operations.
Source: SMB Story, 2023.
64% of CEOs believe driving digital transformation at a rapid pace is critical to attracting and retaining talent and customers.
Source: KPMG, 2022.
An IT infrastructure maturity assessment is a foundational step in the journey of digital transformation. The demand will be on performance, resilience, and scalability. IT infrastructure must be able to support innovation and rapid deployments.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Assess the organization’s fit for MMS technology and structure the MMS selection project.
Produce a vendor shortlist for your MMS.
Evaluate RFPs, conduct vendor demonstrations, and select an MMS.
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.
Determine a “right-size” approach to marketing enablement applications.
Confirmation of the goals, objectives, and direction of the organization is marketing application strategy.
1.1 Assess the value and identify the organization’s fit for MMS technology.
1.2 Understand the art of the possible.
1.3 Understand CXM strategy and identify your fit for MMS technology.
1.4 Build procurement team and project customer experience management (CXM) strategy.
1.5 Identify your MMS requirements.
Project team list.
Preliminary requirements list.
Enumerate relevant marketing management suites and point solutions.
List of marketing enablement applications based on requirements articulated in the preliminary requirements list strategy.
2.1 Identify relevant use cases.
2.2 Discuss the vendor landscape.
Vendor shortlist.
Develop a rationale for selecting a specific MMS vendor.
MMS Vendor decision.
A template to communicate the decision to executives.
3.1 Create a procurement strategy.
3.2 Discuss the executive presentation.
3.3 Plan the procurement process.
Executive/stakeholder PowerPoint presentation.
Selection of an MMS.
“Marketing applications are in high demand, but it is difficult to select a suite that is right for your organization. Market offerings have grown from 50 vendors to over 800 in the past five years. Much of the process of identifying an appropriate vendor is not about the vendor at all, but rather about having a comprehensive understanding of internal needs. There are instances where a smaller-point solution is necessary to satisfy requirements and a full marketing management suite is an overinvestment.
Likewise, a partner with differentiating features such as AI-driven workflows and a mobile software development kit can act as a powerful extension of an overall customer experience management strategy. It is crucial to make the right decision; missing the mark on an MMS selection will have a direct impact on the business’ bottom line.”
Ben Dickie
Research Director, Enterprise Applications
Info-Tech Research Group
This Research Is Designed For:
|
This Research Will Help You:
|
This Research Will Also Assist:
|
This Research Will Help Them
|
The MMS market is a landscape of vendors offering campaign management, multichannel support, analytics, and publishing tools. Many vendors specialize in some of these areas but not all. Sometimes multiple products are necessary – but determining which feature sets the organization truly needs can be a challenging task. The right technology stack is critical in order to bring automation to marketing initiatives.
| “When it comes to marketing automation capabilities, using CRM is like building a car from a kit. All the parts are there, but you need the time and skill to put it all together. Using marketing automation is like buying the car you want or need, with all the features you want already installed and some gas in the tank, ready to drive. In either case, you still need to know how to drive and where you want to go.” (Mac McIntosh, Marketo Inc.) | ![]() |
A master database – the central place where all up-to-the-minute data on a customer profile is stored – is essential for MMS success. This is particularly true for real-time capability effectiveness and to minimize customer fatigue. |
MMS helps marketers in two primary ways:
|
“A marketing automation solution delivers essentially all the benefits of an email marketing solution along with integrated capabilities that would otherwise need to be cobbled together using various standalone technologies.” (Marketo Inc.) |

1 |
2 |
3 |
4 |
5 |
| Establish Resources | Gather Requirements | Write and Assemble RFP | Exercise Due Diligence | Evaluate Candidate Solutions |
|
|
|
|
|
Contact your account representative or email Workshops@InfoTech.com for more information.
CASE STUDY |
Industry: Professional Services | Source: Info-Tech Consulting |
ChallengeA large professional services firm specializing in knowledge development was looking to modernize an outdated marketing services stack. Previous investments in marketing tools ranging from email automation to marketing analytics led to system fragmentation. As a result, there was no 360-degree overview of marketing operations and no way to run campaigns at scale. To satisfy the organization’s aspirations, a comprehensive marketing management suite had to be selected that met needs for the foreseeable future. |
SolutionThe Info-Tech consulting team was brought in to assist in the MMS selection process. After meeting with several stakeholders, MMS requirements were developed and weighted. An RFP was then created from these requirements. Following a market scan, four vendors were selected to complete the organization’s RFP. Demonstration scripts were then developed as the RFPs were completed by vendors. Shortlisted vendors progressed to the demonstration phase. |
ResultsVendor scorecards were utilized during the two-day demonstrations with the core project team to score each vendor. During the scoring process the team also identified the need to replace the organization’s core customer repository (a legacy CRM). The decision was made to select a CRM before finalizing the MMS selection. Doing so ensured uniform system architecture and strong interoperability between the firm’s MMS and its CRM. |
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 |
|||
| 1. Launch the MMS Project and Collect Requirements | 2. Shortlist Marketing Management Suites | 3. Select Vendor and Communicate Decision to Stakeholders | |
![]() Best-Practice Toolkit |
1.1 Assess the value and identify your organization’s fit for MMS technology. 1.2 Build your procurement team and project customer experience management (CXM) strategy. 1.3 Identify your MMS requirements. |
2.1 Produce your shortlist |
3.1 Select your MMS 3.2 Present selection |
Guided Implementations |
|
|
|
![]() Onsite Workshop |
Module 1:
Launch Your MMS Selection Project |
Module 2:
Analyze MMS Requirements and Shortlist Vendors |
Module 3:
Plan Your Procurement Process |
Phase 1 Outcome:
|
Phase 2 Outcome:
|
Phase 3 Outcome:
|
Use these icons to help guide you through each step of the blueprint and direct you to content related to the recommended activities.
![]() |
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. |
![]() |
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. |
![]() |
This icon denotes a slide that pertains directly to the Info-Tech vendor profiles on marketing management technology. Use these slides to support and guide your evaluation of the MMS vendors included in the research. |
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.
| Step 1.2: Structure the Project | Step 1.3: Gather Requirements |
Start with an analyst kick-off call:
|
Review findings with analyst:
|
Then complete these activities…
|
Then complete these activities…
|
With these tools & templates:
|
With these tools & templates:
|
Phase 1 Results:
|
|
1.1 |
1.2 |
1.3 |
||
| Understand the MMS Market | Structure the Project | Gather MMS Requirements |
| Analytics | The practice of measuring marketing performance to improve return on investment (ROI). It is often carried out through the visualization of meaningful patterns in data as a result of marketing initiatives. |
| Channels | The different places where marketers can reach customers (e.g. social media, print mail, television). |
| Click-through rate | The percentage of individuals who proceed (click-through) from one part of a marketing campaign to the next. |
| Content management | Curating, creating, editing, and keeping track of content and client-facing assets. |
| Customer relationship management (CRM) | A core enterprise application that provides a broad feature set for supporting customer interaction processes. The CRM frequently serves as a core customer data repository. |
| Customer experience management (CXM) | The holistic management of customer interaction processes across marketing, sales, and customer service to create valuable, mutually beneficial customer experiences. |
| Engagement rate | A social media metric used to describe the amount of likes, comments, shares, etc., that a piece of content receives. |
| Lead | An individual or organization who has shown interest in the product or service being marketed. |
| Omnichannel | The portfolio of interaction channels you use. |
A master database – the central place where all up-to-the-minute data on a customer profile is stored – is essential for MMS success. This is particularly true for real-time capability effectiveness and to minimize customer fatigue. If you have customer records in multiple places, you risk missing customer opportunities and potentially upsetting clients. For example, if a client has communicated preferences or disinterest through one channel, and this is not effectively recorded throughout the organization, another representative is likely to contact them in the same method again – possibly alienating the customer for good. A master database requires automatic synchronization with all point solutions, POS, billing systems, agencies, etc. If you don’t have up-to-the-minute information, you can’t score prospects effectively and you lose out on the benefits of the MMS. |
![]() |
| Focus on the fundamentals before proceeding. | Secure organizational readiness to reduce project risk using Info-Tech’s Build a Strong Technology Foundation for CXM and Select and Implement a CRM Platform blueprints. |
| The world of marketing technology changes rapidly! Understand how modern marketing management suites are used in most organizations. An MMS helps marketers in two primary ways:
Marketing suites accomplish these tasks by:
A strong MMS provides marketers with the data they need for actionable insights about their customers. “A marketing automation solution delivers essentially all the benefits of an email marketing solution along with integrated capabilities that would otherwise need to be cobbled together using various standalone technologies.” (Marketo Inc.) | Inform your way of thinking by understanding the capabilities of modern marketing applications.
|
(Source: Info-Tech Research Group; N=23)
The key drivers for MMS are business-related, not IT-related. However, this does not mean that there are no benefits to IT. In fact, the IT department will see numerous benefits, including time and resource savings. Further, not having an MMS creates more work for your IT department. IT must serve as a valued partner for selection and implementation.
Marketing management suites are ideal for large organizations with multiple product lines in complex marketing environments. IT is often more centralized than its counterparts in the business, making it uniquely positioned to encourage greater coordination by helping the business units understand the shared goals and the benefits of working together to roll out suites for marketing workflow management, intelligence, and channel management.
| Cross-Segmentation | Additional Revenue Generation | Real-Time Capabilities | Lead Growth/ Conversion Rate | |
| Business Value |
|
|
|
|
| IT Value |
|
|
|
|
Don’t forget that MMS technologies deliver on the overarching suite value proposition: a robust solution within one integrated offering. Without an MMS in play, organizations in need of this functionality are forced to piece together point solutions (or ad hoc management). This not only increases costs but also is an integration nightmare for IT.
1.1 | 1.2 | 1.3 | ||
| Understand the MMS Market | Structure the Project | Gather MMS Requirements |
Sample Project Overview[Organization] plans to select and implement a marketing management suite in order to introduce better campaign management to the business’ processes. This procurement and implementation of an MMS tool will enable the business to improve the efficiency and effectiveness of marketing campaign execution. This project will oversee the assessment and shortlisting of MMS vendors, selection of an MMS tool, the configuration of the solution, and the implementation of the technology into the business environment. Rationale Behind the ProjectConsider the business drivers behind the interest in MMS technology. Be specific to business units impacted and identify key considerations (both opportunities and risks). |
Business Drivers
|
Creating repeatable and streamlined marketing processes is a common overarching business objective that is driven by multiple factors. To ensure this objective is achieved, confirm that the primary drivers are following the implementation of the first automated marketing channels.
INPUT: Stakeholder user stories
OUTPUT: Understanding of ideal outcomes from MMS implementation
MATERIALS: Whiteboard and marker or sticky notes
PARTICIPANTS: Project sponsor, Project stakeholders, Business analysts, Business unit reps
| Improve | Reduce/Eliminate | KPIs |
| Multichannel marketing | Duplication of effort | Number of customer interaction channels supported |
| Social integration | Process inefficiencies | Number of social signals received (likes, shares, etc.) |
| … | … | … |
If you do not have a well-defined CXM strategy, leverage Info-Tech’s research to Build a Strong Technology Foundation for Customer Experience Management.
This blueprint focuses on complete, integrated marketing management suitesAn integrated suite is a single product that is designed to assist with multiple marketing processes. Information from these suites is deeply connected to the core CRM. Changing a piece of information for one process will update all affected. |
![]() |
A point solution typically interfaces with a single customer interaction channel with minimal CRM integration. Why use a marketing point solution?
Refer to Phase 2 for a bird’s-eye view of the point solution marketplace. |
Marketing Point Solutions
|
![]()
Adopt an MMS if:
|
Bypass an MMS if:
|
Using an MMS is ideal for organizations with multiple brands and product portfolios (e.g. consumer packaged goods). Ad hoc management and email marketing services are best for small organizations with a client base that requires only bare bones engagement.
Use Info-Tech’s MMS Readiness Assessment Checklist to determine if your organization has sufficient process and campaign maturity to warrant the investment in a consolidated marketing management suite.
Sections of the Tool:
|
INFO-TECH DELIVERABLE
Complete the MMS Readiness Assessment Checklist by following the instructions in Activity 1.2.3. |
1.2.3 30 minutes
INPUT: MMS foundation, MMS strategy
OUTPUT: Readiness remediation approach, Validation of MMS project readiness
MATERIALS: Info-Tech’s MMS Readiness Assessment Checklist
PARTICIPANTS: Project sponsor, Core project team
1.1 | 1.2 | 1.3 | ||
| Understand the MMS Market | Structure the Project | Gather MMS Requirements |
USE CASES |
While an organization may be product- or service-centric, most fall into one of the three use cases described on this slide. |
1) Marketing AutomationWorkflow ManagementManaging complex marketing campaigns and building and tracking marketing workflows are the mainstay responsibilities of brand managers and other senior marketing professionals. In this category, we evaluated vendors that provide marketers with comprehensive tools for marketing campaign automation, workflow building and tracking, lead management, and marketing resource planning for campaigns that need to reach a large segment of customers. Omnichannel ManagementThe proliferation of marketing channels has created significant challenges for many organizations. In this use case, we executed a special evaluation of vendors that are well suited for the intricacies of juggling multiple channels, particularly mobile, social, and email marketing. |
2) Marketing IntelligenceSifting through data from a myriad of sources and coming up with actionable intelligence and insights remains a critical activity for marketing departments, particularly for market researchers. In this category, we evaluated solutions that aggregate, analyze, and visualize complex marketing data from multiple sources to allow decision makers to execute informed decisions. 3) Social MarketingThe proliferation of social networks, customer data, and use cases has made ad hoc social media management challenging. In this category we evaluated vendors that bring uniformity to an organization’s social media capabilities and contribute to a 360-degree customer view. |
1.3.1 30 minutes
INPUT: Use-case breakdown
OUTPUT: Project use-case alignments
Materials: Whiteboard, markers
Participants: Project manager, Core project team (optional)
The use-case view of vendor and product performance provides multiple opportunities for vendors to fit into your application architecture depending on their product and market performance. The use cases selected are based on market research and client demand.
Determining your use case is crucial for:
The following slides illustrate how the three most common use cases (marketing automation, marketing intelligence, and social marketing) align with business needs. As shown by the case studies, the right MMS can result in great benefits to your organization.
| Marketing Need | Manage customer experience across multiple channels | Manage multiple campaigns simultaneously | Integrate web-enabled devices (IoT) into marketing campaigns | Run and track email marketing campaigns |
![]() |
||||
| Corresponding Feature | End-to-end management of email marketing | Visual workflow editor | Customer journey mapping | Business rules engine | A/B tracking |
CASE STUDY | Industry: Entertainment | Source: Marketo |
ChallengeThe Portland Trail Blazers, an NBA franchise, were looking to expand their appeal beyond the city of Portland and into the greater Pacific Northwest Region. The team’s management group also wanted to showcase the full range of events that were hosted in the team’s multipurpose stadium. The Trail Blazers were looking to engage fans in a more targeted fashion than their CRM allowed for. Ultimately, they hoped to move from “batch and blast” email campaigns to an automated and targeted approach. | SolutionThe Trail Blazers implemented an MMS that allowed it to rapidly build different types of campaigns. These campaigns could be executed across a variety of channels and target multiple demographics at various points in the fan journey. Contextual ads were implemented using the marketing suite’s automated customer journey mapping feature. Targeted ads were served based on a fan’s location in the journey and interactions with the Trail Blazers’ online collateral. | ResultsThe automated campaigns led to a 75% email open rate, which contributed to a 96% renewal rate for season ticket holders – a franchise record. Other benefits resulting from the improved conversion rate included an increased cohesion between the Trail Blazers’ marketing, analytics, and ticket sales operations. |
![]()
| Marketing Need | Capture marketing- and customer-related data from multiple sources | Analyze large quantities of marketing data | Visualize marketing-related data in a manner that is easy for decision makers to consume | Perform trend and predictive analysis |
![]() |
||||
| Corresponding Feature | Integrate data across customer segments | Analysis through machine learning | Assign attributers to unstructured data | Displays featuring data from external sources | Create complex customer data visualizations |
CASE STUDY | Industry: Retail | Source: SAS |
ChallengeWomen’s apparel retailer Chico’s FAS was looking to capitalize on customer data from in-store and online experiences. Chico’s hoped to consolidate customer data from multiple online and brick-and-mortar retail channels to get a complete view of the customer. Doing so would satisfy Chico’s need to create more highly segmented, cost-effective marketing campaigns | SolutionChico’s selected an MMS with strong marketing intelligence, analysis, and data visualization capability. The MMS could consolidate and analyze customer and transactional information. The suite’s functionality enabled Chico’s marketing team to work directly with the data, without help from statisticians or IT staff. | ResultsThe approach to marketing indigence led to customers getting deals on products that were actually relevant to them, increasing sales and brand loyalty. Moreover, the time it took to perform data consolidation decreased dramatically, from 17 hours to two hours, allowing the process to be performed daily instead of weekly. |
![]()
| Marketing Need | Understand customers' likes and dislikes | Manage and analyze social media channels like Facebook and Twitter | Foster a conversation around specific products | Engage international audiences through regional messaging apps |
![]() |
||||
| Corresponding Feature | Social listening capabilities | Tools for curating customer community content | Ability to aggregate social data | Integration with popular social networks | Ability to conduct trend reporting |
CASE STUDY | Industry: Life Sciences | Source: Adobe |
ChallengeBayer, a Fortune 500 health and life sciences company, was looking for a new way to communicate its complex medical breakthroughs to the general public. The decision was made to share the science behind its products via social channels in order to generate excitement. Bayer needed tools to publish content across a variety of social media platforms while fostering conversations that were more focused on the science behind products. | SolutionBased on the requirements, Bayer decided that an MMS would be the best fit. After conducting a market scan, the company selected an MMS with a comprehensive social media suite. The suite included tools for social listening and moderation and tools to guide conversations initiated by both marketers and customers. | ResultsThe MMS provided Bayer with the toolkit to engage its audience. Bayer took control of the conversation about its products by serving potential customers with relevant video content on social media. Its social strategy coupled with advanced engagement tools resulted in new business opportunities and more than 65,000 views on YouTube and more than 87,000 Facebook views in a single month. |
| REQUIREMENTS GATHERING
Info-Tech’s requirements gathering framework is a comprehensive approach to requirements management that can be scaled to any size of project or organization. This framework ensures that the application created will capture the needs of all stakeholders and deliver business value. Develop and right-size a proven standard operating procedure for requirements gathering with Info-Tech’s blueprint Build a Strong Approach to Business Requirements Gathering. |
![]() |
| Requirements Gathering Methodology
Requirements Gathering Blueprint Slide 25: Understand the best-practice framework for requirements gathering for enterprise applications projects. |
Requirements Gathering SOP
Requirements Gathering Blueprint Activities 1.2.2-1.2.5, 2.1.1, 2.1.2, 3.1.1, 3.2.1, 4.1.1-4.1.3, 4.2.2: Consolidate outputs to right-size a best-practice SOP for your organization. |
Project Level Selection Tool
Requirements Gathering Blueprint Activity 1.2.4: Determine project-level selection guidelines to inform the due diligence required in your MMS requirements gathering. |
1.3.2 Varies
INPUT: MMS tool user expertise, MMS Requirements Picklist Tool
OUTPUT: A list of needs from the MMS tool user perspective
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: MMS users in the organization, MMS selection committee
Download the MMS Requirements Picklist Tool to help with completing this activity.
The return on investment (ROI) and perceived value of the organization’s marketing solution will be a critical indication of the likelihood of success of the suite’s selection and implementation.
| EXAMPLE METRICS |
MMS and Technology AdoptionMarketing Performance Metrics |
|
| Average revenue gain per campaign | Quantity and quality of marketing insights | |
| Average time to execute a campaign | Customer acquisition rates | |
| Savings from automated processes | Marketing cycle times | |
User Adoption and Business Feedback Metrics |
||
| User satisfaction feedback | User satisfaction survey with the technology | |
| Business adoption rates | Application overhead cost reduction | |
Even if marketing metrics are difficult to track right now, the implementation of an MMS brings access to valuable customer intelligence from data that was once kept in silos.
![]() |
|
1.2.1 |
![]() |
Align the CXM strategy value proposition to MMS capabilities
Our facilitator will help your team identify the IT CXM strategy and marketing goals. The analyst will then work with the team to map the strategy to technological drivers available in the MMS market. |
1.3.2 |
![]() |
Define the needs of MMS users
Our facilitator will work with your team to identify user requirements for the MMS Requirements Picklist Tool. The analyst will facilitate a discussion with your team to prioritize identified requirements. |
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.
| Step 2.1: Analyze and Shortlist MMS Vendors | |
Start with an analyst kick-off call:
|
|
Then complete these activities…
|
|
With these tools & templates:
|
|
Phase 2 Results:
|
|
2.1 |
| Analyze and Shortlist MMS Vendors |
![]()
Loosely Tied TogetherOriginally the sales and marketing enterprise application space was highly fragmented, with disparate best-of-breed point solutions patched together. Soon after, vendors in the late 1990s started bundling automation technologies into a single suite offering. Marketing capabilities of CRM suites were minimal at best and often restricted to web and email only. Limited to Large EnterprisesMany vendors started to combine all marketing tools into a single, comprehensive marketing suite, but cost and complexity limited them to large enterprises and marketing agencies. Best-of-breed solutions targeting new channels and new goals, like closed-loop sales and marketing, continued driving new marketing software genres, like dedicated lead management suites. |
“In today’s volatile business environment, judgment built from past experience is increasingly unreliable. With consumer behaviors in flux, once-valid assumptions (e.g. ‘older consumers don’t use Facebook or send text messages’) can quickly become outdated.” (SAS Magazine) |
As the market evolves, capabilities that were once cutting edge become default and new functionality becomes differentiating. Some features, like basic CRM integration, have become table stakes capabilities. Focus on advanced analytics features and omnichannel integration capabilities to get the best fit for your requirements.
AI and Machine LearningVendors are beginning to offer AI capabilities across MMS for data-driven customer engagement scoring and social listening insights. Machine learning capability is being leveraged to determine optimal customer journey and suggest next steps to users. Marketplace FragmentationThe number of players in the marketing application space has grown exponentially. The majority of these new vendors offer point solutions rather than full-blown marketing suites. Fragmentation is leading to tougher choices when looking to augment an existing platform with specific functionality. Improving Application IntegrationMMS vendors are fostering deeper integrations between their marketing products and core CRM products, leading to improved data hygiene. At the same time, vendors are improving flexibility in the marketing suite so that new channels can be added easily. Greater Self-ServiceVendors have an increased emphasis on application usability. Their goal is to enable marketers to execute campaigns without relying on specialists. |
“There’s a firehose of customer data coming at marketers today, and with more interconnected devices emerging (wearables, smart watches, etc.), cultivating a seamless customer experience is likely to grow even more challenging. Building out a data-driven marketing strategy and technology stack that enables you to capture behaviors across channels is key.” (IBM, Ideas for Exceeding Customer Expectations) |

VENDOR PROFILESReview the MMS Vendor Evaluation |
![]() |
![]()
TABLE STAKES
| What does this mean?The products assessed in these vendor profiles meet, at the very least, the requirements outlined as table stakes. Many of the vendors go above and beyond the outlined table stakes; some even do so in multiple categories. This section aims to highlight the products’ capabilities in excess of the criteria listed here. Info-Tech InsightIf table stakes are all you need from your MMS, determine whether your existing CRM platform already satisfies your requirements. Otherwise, dig deeper to find the best price-to-value ratio for your needs. |
Almost – or equally – as important as evaluating vendor feature capabilities is the need to evaluate vendor viability and non-functional aspects of the MMS. Include an evaluation of the following criteria in your vendor scoring methodology:
| Vendor Attribute | Description |
| Vendor Stability and Variability | The vendor’s proven ability to execute on constant product improvement, deliberate strategic direction, and overall commitment to research and development efforts in responding to emerging trends. |
| Security Model | The potential to integrate the application to existing security models and the vendor's approach to handling customer data. |
| Deployment Style | The choice to deploy a single or multi-tenant SaaS environment via a perpetual license. |
| Ease of Customization | The relative ease with which a system can be customized to accommodate niche or industry-specific business or functional needs. |
| Vendor Support Options | The availability of vendor support options, including selection consulting, application development resources, implementation assistance, and ongoing support resources. |
| Size of Partner Ecosystem | The quantity of enterprise applications and third-party add-ons that can be linked to the MMS, as well as the number of system integrators available. |
| Ease of Data Integration | The relative ease with which the system can be integrated with an organization’s existing application environment, including legacy systems, point solutions, and other large enterprise applications. |
Evaluate vendor capabilities, not just product capabilities. An MMS is typically a long-term commitment; ensure that your organization is teaming up with a vendor or provider that you feel you can work well with and depend on.
Evaluation MethodologyThese product features were assessed as part of the classification of vendors into use cases. In determining use-case leaders and players, select features were considered based on best alignment with the use case. |
|
![]()
Evaluation MethodologyThese product features were assessed as part of the classification of vendors into use cases. In determining use-case leaders and players, select features were considered based on best alignment with the use case. |
|
Review the use-case scenarios relevant to your organization’s use case to identify a vendor’s fit to your organization’s MMS needs.
|
![]() |
Understand your organization’s size and whether it falls within the product’s market focus.
|
![]() |
| Review the differentiating features to identify where the application performs best. | ![]() |
| Colors signify a feature’s performance. | ![]() |
![]() |
FUNCTIONAL SPOTLIGHT
Creative Cloud Integration: To make for a more seamless cross-product experience, projects can be sent between Marketing Cloud and Creative Cloud apps such as Photoshop and After Effects. Sensei: Adobe has revamped its machine learning and AI platform in an effort to integrate AI into all of its marketing applications. Sensei includes data from Microsoft in a new partnership program. Anomaly Detection: Adobe’s Anomaly Detection contextualizes data and provides a statistical method to determine how a given metric has changed in relation to previous metrics. |
||||||||||
USE-CASE PERFORMANCE
|
MARKET FOCUS
|
||||||||||
| Adobe’s goal with Marketing Cloud is to help businesses provide customers with cohesive, seamless experiences by surfacing customer profiles in relevant situations quickly. Adobe Marketing Cloud has traditionally been used in the B2C space but has seen an increase in B2C use cases driven by the finance and technology sectors. | FEATURES
![]() |
| Employees (2018): 17,000 | Presence: Global | Founded: 1982 | NASDAQ: ADBE |
![]()
![]() | FUNCTIONAL SPOTLIGHT Content Optimization System (COS): The fully integrated system stores assets and serves them to their designated channels at relevant times. The COS is integrated into HubSpot's marketing platform. Email Automation: HubSpot provides basic email that can be linked to a specific part of an organization’s marketing funnel. These emails can also be added to pre-existing automated workflows. Email Deliverability Tool: HubSpot identifies HTML or content that will be flagged by spam filters. It also validates links and minimizes email load times. | ||||||||||
USE-CASE PERFORMANCE
| MARKET FOCUS
| ||||||||||
| Hubspot’s primary focus has been on email marketing campaigns. It has put effort into developing solid “click not code” email marketing capabilities. Also, Hubspot has an official integration with Salesforce for expanded operations management and analytics capabilities. | FEATURES
![]() |
| Employees (2018): 1,400 | Presence: Global | Founded: 2006 | NYSE: HUBS |
![]()
![]() | FUNCTIONAL SPOTLIGHT Watson: IBM is leveraging its popular Watson AI brand to generate marketing insights for automated campaigns. Weather Effects: Set campaign rules based on connections between weather conditions and customer behavior relative to zip code made by Watson. Real-Time Personalization: IBM has made efforts to remove campaign interaction latency and optimize live customer engagement by acting on information about what customers are doing in the current moment. | ||||||||||
USE-CASE PERFORMANCE
| MARKET FOCUS
| ||||||||||
| IBM has remained ahead of the curve by incorporating its well-known AI technology throughout Marketing Cloud. The application’s integration with the wide array of IBM products makes it a powerful tool for users already in the IBM ecosystem. | FEATURES
![]() |
| Employees (2018): 380,000 | Presence: Global | Founded: 1911 | NYSE: IBM |
![]()
![]() | FUNCTIONAL SPOTLIGHT Content AI: Marketo has leveraged its investments in machine learning to intelligently fetch marketing assets and serve them to customers based on their interactions with a campaign. Email A/B Testing: To improve lead generation from email campaigns, Marketo features the ability to execute A/B testing for customized campaigns. Partnership with Google: Marketo is now hosted on Google’s cloud platform, enabling it to provide support for larger enterprise clients and improve GDPR compliance. | ||||||||||
USE-CASE PERFORMANCE
| MARKET FOCUS
| ||||||||||
| Marketo has strong capabilities for lead management but has recently bolstered its analytics capabilities. Marketo is hoping to capture some of the analytics application market share by offering tools with varying complexity and to cater to firms with a wide range of analytics needs. | FEATURES
![]() |
| Employees (2018): 1,000 | Presence: Global | Founded: 2006 | Private Corporation |
![]()
![]() | FUNCTIONAL SPOTLIGHT Data Visualization: To make for a more seamless cross-product experience, marketing projects can be sent between Marketing Cloud and Creative Cloud apps such as Dreamweaver. ID Graph: Use ID Graph to unite disparate data sources to form a singular profile of leads, making the personalization and contextualization of campaigns more efficient. Interest-Based Messaging: Pause a campaign to update a segment or content based on aggregated customer activity and interaction data. | ||||||||||
USE-CASE PERFORMANCE
| MARKET FOCUS
| ||||||||||
| Oracle Marketing Cloud is known for its balance between campaigns and analytics products. Oracle has taken the lead on expanding its marketing channel mix to include international options such as WeChat. Users already using Oracle’s CRM/CEM products will derive the most value from Marketing Cloud. | FEATURES
![]() |
| Employees (2018): 138,000 | Presence: Global | Founded: 1977 | NYSE: ORCL |
![]()
![]() | FUNCTIONAL SPOTLIGHT Einstein: Salesforce is putting effort into integrating AI into all of its applications. The Einstein AI platform provides marketers with predictive analytics and insights into customer behavior. Mobile Studio: Salesforce has a robust mobile marketing offering that encompasses SMS/MMS, in-app engagement, and group messaging platforms. Journey Builder: Salesforce created Journey Builder, which is a workflow automation tool. Its user-friendly drag-and-drop interface makes it easy to automate responses to customer actions. | ||||||||||
USE-CASE PERFORMANCE
| MARKET FOCUS
| ||||||||||
| Salesforce Marketing Cloud is primarily used by organizations in the B2C space. It has strong Sales Cloud CRM integration. Pardot is positioning itself as a tool for sales teams in addition to marketers. | FEATURES
![]() |
| Employees (2018): 1,800 | Presence: Global | Founded: 2000 | NYSE: CRM |
![]()
![]() | FUNCTIONAL SPOTLIGHT Engagement Studio: Salesforce is putting marketing capabilities in the hands of sales reps by giving them access to a team email engagement platform. Einstein: Salesforce’s Einstein AI platform helps marketers and sales reps identify the right accounts to target with predictive lead scoring. Program Steps: Salesforce developed a distinct own workflow building tool for Pardot. Workflows are made of “Program Steps” that have the functionality to initiate campaigns based on insights from Einstein. | ||||||||||
USE-CASE PERFORMANCE
| MARKET FOCUS
| ||||||||||
| Pardot is Salesforce’s B2B marketing solution. Pardot has focused on developing tools that enable sales teams and marketers to work in lockstep in order to achieve lead-generation goals. Pardot has deep integration with Salesforce’s CRM and customer service management products. | FEATURES
![]() |
| Employees (2018): 1,800 | Presence: Global | Founded: 2000 | NYSE: CRM |
![]()
![]() | FUNCTIONAL SPOTLIGHT CMO Dashboard: The specialized dashboard is aimed at providing overviews for the executive level. It includes the ability to coordinate marketing activities and project budgets, KPIs, and timelines. Loyalty Management: SAP features in-app tools to manage campaigns specifically geared toward customer loyalty with digital coupons and iBeacons. Customer Segmentation: SAP’s predictive capabilities dynamically suggest relevant customer profiles for new campaigns. | ||||||||||
USE-CASE PERFORMANCE
| MARKET FOCUS
| ||||||||||
| SAP Hybris Marketing Cloud optimizes marketing strategies in real time with accurate attribution and measurements. SAP’s operations management capabilities are robust, including the ability to view consolidated data streams from ongoing marketing plans, performance targets, and budgets. | FEATURES
![]() |
| Employees (2018): 84,000 | Presence: Global | Founded: 1972 | NYSE: SAP |
![]()
![]() | FUNCTIONAL SPOTLIGHT Activity Map: A user-friendly workflow builder that can be used to execute campaigns. Multiple activities can be simultaneously A/B tested within the Activity Map UI. The outcome of the test can automatically adjust the workflow. Spots: A native digital asset manager that can store property that is part of existing and future campaigns. Viya: A framework for fully integrating third-party data sources into SAS Marketing Intelligence. Viya assists with pairing on-premises databases with a cloud platform for use with the SAS suite. | ||||||||||
USE-CASE PERFORMANCE
| MARKET FOCUS
| ||||||||||
| SAS has been a leading BI and analytics provider for more than 35 years. Rooted in statistical analysis of data, SAS products provide forward-looking strategic insights. Organizations that require extensive customer intelligence capabilities and the ability to “slice and dice” segments should have SAS on their shortlist. | FEATURES
![]() |
| Employees (2018): 14,000 | Presence: Global | Founded: 1976 | Private Corporation |
Additional vendors in the MMS market: |
|
![]() |
![]() |
See the next slides for suggested point solutions. |
|
Web experience management (WXM) and social media management platforms (SMMP) act in concert with your MMS to execute complex campaigns.
| Social Media Management
Info-Tech’s SMMP selection guide enables you to find a solution that satisfies your objectives across marketing, sales, public relations, HR, and customer service. Create a unified framework for driving successful implementation and adoption of your SMMP that fully addresses CRM and marketing automation integration, end-user adoption, and social analytics with Info-Tech’s blueprint Select and Implement a Social Media Management Platform. |
![]() |
| Web Experience Management
Info-Tech’s approach to WXM ensures you have the right suite of tools for web content management, experience design, and web analytics. Put your best foot forward by conducting due diligence as the selection project advances. Ensure that your organization will see quick results with Info-Tech’s blueprint Select and Implement a Web Experience Management Solution. |
![]() |
POINT SOLUTION PROFILESReview this cursory list of point solutions by use caseConsider point solutions if a full suite is not required |
![]() |




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.
| Step 3.1: Select Your MMS | Step 3.2: Communicate the Decision to Stakeholders |
Start with an analyst kick-off call:
|
Review findings with analyst:
|
Then complete these activities…
|
Then complete these activities…
|
With these tools & templates:
|
With these tools & templates:
|
Phase 3 Results
|
|
3.1 |
3.2 |
|
| Select Your MMS | Communicate Decision to Stakeholders |
3.1.1 30 minutes
INPUT: Organizational use-case fit
OUTPUT: MMS vendor shortlist
Materials: Info-Tech’s MMS use cases, Info-Tech’s vendor profiles, Whiteboard, markers
Participants: Core project team
3.1.2 MMS Request for Proposal Template
| Use the MMS Request for Proposal Template as a step-by-step guide on how to request interested vendors to submit written proposals that meet your set of requirements. If interested in bidding for your project, vendors will respond with a description of the techniques they would employ to address your organizational challenges and meet your requirements, along with a plan of work and detailed budget for the project. The RFP is an important piece of setting and aligning your expectations with the vendors’ product offerings. Make sure to address the following elements in the RFP: Sections of the Tool:
| INFO-TECH DELIVERABLE Complete the MMS Request for Proposal Template by following the instructions in Activity 3.1.3. |
3.1.3 1-2 hours
INPUT: Business requirements document, Procurement procedures
OUTPUT: MMS RFP
Materials: Internal RFP tools or templates (if available), Info-Tech’s MMS Request for Proposal Template (optional)
Participants: Procurement SMEs, Project manager, Core project team (optional)
Vendor demonstrations are an integral part of the selection process. Having clearly defined selection criteria will help with setting up relevant demos as well as inform the vendor scorecards.
| EXAMPLE EVALUATION CRITERIA | ![]() | |
Functionality (30%)
| Ease of Use (25%)
| |
Cost (15%)
| Vendor (15%)
| |
Technology (15%)
| Info-Tech InsightBase your vendor evaluations not on the capabilities of the solutions but instead on how the solutions align with your organization’s process automation requirements and considerations. | |
Examine how the vendor’s solution performs against your evaluation framework.
Vendor demonstrations create a valuable opportunity for your organization to confirm that the vendor’s claims in the RFP are actually true.
A display of the vendor’s functional capabilities and its execution of the scenarios given in your demo script will help to support your assessment of whether a vendor aligns with your MMS requirements.
3.1.4 1-2 hours
INPUT: Business requirements document, Logistical considerations, Usage scenarios by functional area
OUTPUT: MMS demo script
Materials: Info-Tech’s MMS Vendor Demo Script
Participants: Procurement SMEs, Core project team
Challenge vendor project teams during product demonstrations. Asking the vendor to make adjustments or customizations on the fly will allow you to get an authentic feel of product capability and flexibility, as well as of the degree of adaptability of the vendor project team. Ask the vendor to demonstrate how to do things not listed in your user scenarios, such as change system visualizations or design, change underlying data, add additional datasets, demonstrate analytics capabilities, or channel specific automation.
MMS Vendor Demo Script
| Customize and use Info-Tech’s MMS Vendor Demo Script to help identify how a vendor’s solution will fit your organization’s particular business capability needs. This tool assists with outlining logistical considerations for the demo itself and the scenarios with which the vendors should script their demonstration. Sections of the Tool:
Info-Tech Best PracticeAvoid providing vendors with a rigid script for product demonstration; instead, provide user scenarios. Part of the value of a vendor demonstration is the opportunity to assess whether or not the vendor project team has a solid understanding of your organization’s MMS challenges and requirements and can work with your team to determine the best solution possible. A rigid script may result in your inability to assess whether the vendor will adjust for and scale with your project and organization as a technology partner. | INFO-TECH DELIVERABLE Use the MMS Vendor Demo Script by following the instructions in Activity 3.1.4. |
Design a procurement process that is robust, ruthless, and reasonable. Rooting out bias during negotiation is vital to making unbiased vendor selections.
| Vendor Selection
Info-Tech’s approach to vendor selection gets you to design a procurement process that is robust, ruthless, and reasonable. This approach enables you to take control of vendor communications. Implement formal processes with an engaged team to achieve the right price, the right functionality, and the right fit for the organization with Info-Tech's blueprint Implement a Proactive and Consistent Vendor Selection Process. |
![]() |
| Vendor Negotiation
Info-Tech’s SaaS negotiation strategy focuses on taking control of implementation from the beginning. The strategy allows you to work with your internal stakeholders to make sure they do not team up with the vendor instead of you. Reach an agreement with your vendor that takes into account both parties’ best interests with Info-Tech’s blueprint Negotiate SaaS Agreements That Are Built to Last. |
![]() |
3.1 |
3.2 |
|
| Select Your MMS | Communicate Decision to Stakeholders |
Ensure traceability from the selected tool to the needs identified in the first phase. Internal stakeholders must understand the reasoning behind the final selection and see the alignment to their defined requirements and needs.
| Document the selection process to show how the selected tool aligns to stakeholder needs:
|
Documentation will assist with:
|
3.2.1 1 week
INPUT: MMS tool selection committee expertise
OUTPUT: Decision to invest or not invest in an MMS tool
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: MMS tool selection committee
Documenting the process of how the selection decision was made will avoid major headaches down the road. Without a documented process, internal stakeholders and even vendors can challenge and discredit the selection process.

Adobe Systems Incorporated. “Bayer builds understanding, socially.” Adobe.com, 2017. Web.
IBM Corporation, “10 Key Marketing Trends for 2017.” IBM.com, 2017. Web.
Marketo, Inc. “The Definitive Guide to Marketing Automation.” Marketo.com, 2013. Web.
Marketo, Inc. “NBA franchise amplifies its message with help from Marketo’s marketing automation technology.” Marketo.com, 2017. Web.
Salesforce Pardot. “Marketing Automation & Your CRM: The Dynamic Duo.” Pardot.com, 2017. Web.
SAS Institute Inc. “Marketing Analytics: How, why and what’s next.” SAS Magazine, 2013. Web.
SAS Institute Inc. “Give shoppers offers they’ll love.” SAS.com, 2017. Web.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Map the current onboarding process and identify the challenges to a virtual approach.
Determine how existing onboarding activities can be modified for a virtual environment.
Finalize the virtual onboarding process and create an action plan. Continue to re-assess and iterate over time.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Use the information in this blueprint and Info-Tech’s Agile Contract Playbook-Checklist to review and assess your Agile contracts, ensuring that the provisions and protections are suitable for Agile contracts specifically.
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.
To understand Agile-specific contract clauses, to improve risk identification, and to be more effective at negotiating Agile contract terms.
Increased awareness of how Agile contract provisions are different from traditional or waterfall contracts in 12 key areas.
Understanding available options.
Understanding the impact of being too prescriptive.
1.1 Review the Agile Contract Playbook-Checklist.
1.2 Review 12 contract provisions and reinforce key learnings with exercises.
Configured Playbook-Checklist as applicable
Exercise results and debrief
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Get value early by piloting a scorecard for objectively determining project value, and then examine your current state of project intake to set realistic goals for optimizing the process.
Take a deeper dive into each of the three processes – intake, approval, and prioritization – to ensure that the portfolio of projects is best aligned to stakeholder needs, strategic objectives, and resource capacity.
Plan a course of action to pilot, refine, and communicate the new optimized process using Info-Tech’s expertise in organizational change management.
Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.
Set the course of action for optimizing project intake, approval, and prioritization by examining the current state of the process, the team, the stakeholders, and the organization as a whole.
The overarching goal of optimizing project intake, approval, and prioritization process is to maximize the throughput of the best projects. To achieve this goal, one must have a clear way to determine what are “the best” projects.
1.1 Define the criteria with which to determine project value.
1.2 Envision your target state for your optimized project intake, approval, and prioritization process.
Draft project valuation criteria
Examination of current process, definition of process success criteria
Drill down into, and optimize, each of the project intake, approval, and prioritization process.
Info-Tech’s methodology systemically fits the project portfolio into its triple constraint of stakeholder needs, strategic objectives, and resource capacity, to effectively address the challenges of establishing organizational discipline for project intake.
2.1 Conduct retrospectives of each process against Info-Tech’s best practice methodology for project intake, approval, and prioritization process.
2.2 Pilot and customize a toolbox of deliverables that effectively captures the right amount of data developed for informing the appropriate decision makers for approval.
Documentation of new project intake, approval, and prioritization process
Tools and templates to aid the process
Reduce the risks of prematurely implementing an untested process.
Methodically manage the risks associated with organizational change and maximize the likelihood of adoption for the new process.
Engagement paves the way for smoother adoption. An “engagement” approach (rather than simply “communication”) turns stakeholders into advocates who can help boost your message, sustain the change, and realize benefits without constant intervention or process command-and-control.
3.1 Create a plan to pilot your intake, approval, and prioritization process to refine it before rollout.
3.2 Analyze the impact of organizational change through the eyes of PPM stakeholders to gain their buy-in.
Process pilot plan
Organizational change communication plan
Capacity-constrained intake is the only sustainable path forward.
"For years, the goal of project intake was to select the best projects. It makes sense and most people take it on faith without argument. But if you end up with too many projects, it’s a bad strategy. Don’t be afraid to say NO or NOT YET if you don’t have the capacity to deliver. People might give you a hard time in the near term, but you’re not helping by saying YES to things you can’t deliver."
Barry Cousins,
Senior Director, PMO Practice
Info-Tech Research Group
Most organizations approve more projects than they can finish. In fact, many approve more than they can even start, leading to an ever-growing backlog where project ideas – often good ones – are never heard from again.
The appetite to approve more runs directly counter to the shortage of resources that plagues most IT departments. This tension of wanting more from less suggests that IT departments need to be more disciplined in choosing what to take on.
“There is a minimal list of pending projects”
“Last year we delivered the number of projects we anticipated at the start of the year”
What is fiduciary duty?
Officers and directors owe their corporation the duty of acting in the corporation’s best interests over their own. They may delegate the responsibility of implementing the actions, but accountability can't be delegated; that is, they have the authority to make choices and are ultimately answerable for them.
No question is more important to the organization’s bottom line. Projects directly impact the bottom line because they require investment of resource time and money for the purposes of realizing benefits. The scarcity of resources requires that choices be made by those who have the right authority.
Who approves your projects?
Historically, the answer would have been the executive layer of the organization. However, in the 1990s management largely abdicated its obligation to control resources and expenditures via “employee empowerment.”
Controls on approvals became less rigid, and accountability for choosing what to do (and not do) shifted onto the shoulders of the individual worker. This creates a current paradigm where no one is accountable for the malinvestment…
…of resources that comes from approving too many projects. Instead, it’s up to individual workers to sink or swim as they attempt to reconcile, day after day, seemingly infinite organizational demand with their finite supply of working hours.
“Squeaky wheel”: Projects with the most vocal stakeholders behind them are worked on first.
“First in, first out”: Projects are approved and executed in the order they are requested.
80% of organizations feel that their portfolios are dominated by low-value initiatives that do not deliver value to the business (Source: Cooper).
Project intake is a key process of project portfolio management (PPM). The Project Management Institute (PMI) describes PPM as:
"Interrelated organizational processes by which an organization evaluates, selects, prioritizes, and allocates its limited internal resources to best accomplish organizational strategies consistent with its vision, mission, and values."
(PMI, Standard for Portfolio Management, 3rd ed.)
Triple Constraint Model of the Project Portfolio
Project Intake:
All three components are required for the Project Portfolio
Organizations practicing PPM recognize available resource capacity as a constraint and aim to select projects – and commit the said capacity – to projects that:
92% vs. 74%: 92% of high-performing organizations in PPM report that projects are well aligned to strategic initiatives vs. 74% of low performers (PMI, 2015).
82% vs. 55%: 82% of high-performing organizations in PPM report that resources are effectively reallocated across projects vs. 55% of low performers (PMI, 2015)
CEOs today perceive IT to be poorly aligned to business’ strategic goals:
43% of CEOs believe that business goals are going unsupported by IT (Source: Info-Tech’s CEO-CIO Alignment Survey (N=124)).
60% of CEOs believe that improvement is required around IT’s understanding of business goals (Source: Info-Tech’s CEO-CIO Alignment Survey (N=124)).
Business leaders today are generally dissatisfied with IT:
30% of business stakeholders are supporters of their IT departments (Source: Info-Tech’s CIO Business Vision Survey (N=21,367)).
The key to improving business satisfaction with IT is to deliver on projects that help the business achieve its strategic goals:
Optimized project intake not only improves the project portfolio’s alignment to business goals, but provides the most effective way to improve relationships with IT’s key stakeholders.
Benchmark your own current state with overall & industry-specific data using Info-Tech’s Diagnostic Program.
Many IT departments struggle to realistically estimate available project capacity in a credible way. Stakeholders question the validity of your endeavor to install capacity-constrained intake process, and mistake it for unwillingness to cooperate instead.
Project intake, approval, and prioritization involve the coordination of various departments. Therefore, they require a great deal of buy-in and compliance from multiple stakeholders and senior executives.
Many PMOs and IT departments simply lack the ability to decline or defer new projects.
Defining the project value is difficult because there are so many different and conflicting ways that are all valid in their own right. However, without it, it's impossible to fairly compare among projects to select what's "best."
Establishing intake discipline requires a great degree of cooperation and conformity among stakeholders that can be cultivated through strong processes.
| Info-Tech’s Methodology | ||
|---|---|---|
| Project Intake | Project Approval | Project Prioritization |
| Project requests are submitted, received, triaged, and scoped in preparation for approval and prioritization. | Business cases are developed, evaluated, and selected (or declined) for investment, based on estimated value and feasibility. | Work is scheduled to begin, based on relative value, urgency, and availability of resources. |
| Stakeholder Needs | Strategic Objectives | Resource Capacity |
| Project Portfolio Triple Constraint | ||
Our methodology is designed to tackle your hardest challenge first to deliver the highest-value part of the deliverable. Since the overarching goal of optimizing project intake, approval, and prioritization process is to maximize the throughput of the best projects, one must define how “the best projects” are determined.
In nearly all instances…a key challenge for the PPM team is reaching agreement over how projects should rank.
– Merkhofer
A Project Value Scorecard will help you:
The Project Value Scorecard Development Tool is designed to help you develop the project valuation scheme iteratively. Download the pre-filled tool with content that represents a common case, and then, customize it with your data.
Organizational change and stakeholder management are critical elements of optimizing project intake, approval, and prioritization processes because they require a great degree of cooperation and conformity among stakeholders, and the list of key stakeholders are long and far-reaching.
This blueprint will provide a clear path to not only optimize the processes themselves, but also for the optimization effort itself. This research is organized into three phases, each requiring a few weeks of work at your team’s own pace – or all in one week, through a workshop facilitated by Info-Tech analysts.
Tools and Templates:
Tools and Templates:
Tools and Templates:
Info-Tech uses PMI and ISACA frameworks for areas of this research.
PMI’s Standard for Portfolio Management, 3rd ed. is the leading industry framework, proving project portfolio management best practices and process guidelines.
COBIT 5 is the leading framework for the governance and management of enterprise IT.
In addition to industry-leading frameworks, our best-practice approach is enhanced by the insights and guidance from our analysts, industry experts, and our clients.
33,000+
Our peer network of over 33,000 happy clients proves the effectiveness of our research.
1,000+
Our team conducts 1,000+ hours of primary and secondary research to ensure that our approach is enhanced by best practices.
Optimized project intake, approval, and prioritization processes lead to a high PPM maturity, which will improve the successful delivery and throughput of your projects, resource utilization, business alignment, and stakeholder satisfaction ((Source: BCG/PMI).
Measure your success through the following metrics:
$44,700: In the past 12 months, Info-Tech clients have reported an average measured value of $44,700 from undertaking a guided implementation of this research.
Add your own organization-specific goals, success criteria, and metrics by following the steps in the blueprint.
Industry: Financial Services
Source: Info-Tech Client
Challenge
PMO plays a diverse set of roles, including project management for enterprise projects (i.e. PMI’s “Directive” PMO), standards management for department-level projects (i.e. PMI’s “Supportive” PMO), process governance of strategic projects (i.e. PMI’s “Controlling” PMO), and facilitation / planning / reporting for the corporate business strategy efforts (i.e. Enterprise PMO).
To facilitate the annual planning process, the PMO needed to develop a more data-driven and objective project intake process that implicitly aligned with the corporate strategy.
Solution
Info-Tech’s Project Value Scorecard tool was incorporated into the strategic planning process.
Results
The scorecard provided a simple way to list the competing strategic initiatives, objectively score them, and re-sort the results on demand as the leadership chooses to switch between ranking by overall score, project value, ability to execute, strategic alignment, operational alignment, and feasibility.
The Project Value Scorecard provided early value with multiple options for prioritized rankings.
“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.”
| 1. Set Realistic Goals for Optimizing Process | 2. Build New Optimized Processes | 3. Integrate the New Processes into Practice | |
|---|---|---|---|
| Best-Practice Toolkit |
1.1 Define the criteria with which to determine project value.
|
2.1 Streamline intake to manage stakeholder expectations. 2.2 Set up steps of project approval to maximize strategic alignment while right-sizing the required effort. 2.3 Prioritize projects to maximize the value of the project portfolio within the constraint of resource capacity. |
3.1 Pilot your intake, approval, and prioritization process to refine it before rollout. 3.2 Analyze the impact of organizational change through the eyes of PPM stakeholders to gain their buy-in. |
| Guided Implementations |
|
|
|
| Onsite Workshop |
Module 1: Refocus on Project Value to Set Realistic Goals for Optimizing Project Intake, Approval, and Prioritization Process |
Module 2: Examine, Optimize, and Document the New Project Intake, Approval, and Prioritization Process |
Module 3: Pilot, Plan, and Communicate the New Process and Its Required Organizational Changes |
Phase 1 Outcome:
|
Phase 2 Outcome:
|
Phase 3 Outcome:
|
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 |
Benefits of optimizing project intake and project value definition 1.1 Complete and review PPM Current State Scorecard Assessment 1.2 Define project value for the organization 1.3 Engage key PPM stakeholders to iterate on the scorecard prototype |
Set realistic goals for process optimization 2.1 Map current intake, approval, and prioritization workflow 2.2 Enumerate and prioritize process stakeholders 2.3 Determine the current and target capability levels 2.4 Define the process success criteria and KPIs |
Optimize project intake and approval processes 3.1 Conduct focused retrospectives for project intake and approval 3.2 Define project levels 3.3 Optimize project intake processes 3.4 Optimize project approval processes 3.5 Compose SOP for intake and approval 3.6 Document the new intake and approval workflow |
Optimize project prioritization process plan for a process pilot 4.1 Conduct focused retrospective for project prioritization 4.2 Estimate available resource capacity 4.3 Pilot Project Intake and Prioritization Tool with your project backlog 4.4 Compose SOP for prioritization 4.5 Document the new prioritization workflow 4.6 Discuss process pilot |
Analyze stakeholder impact and create communication strategy 5.1 Analyze stakeholder impact and responses to impending organization change 5.2 Create message canvas for at-risk change impacts and stakeholders 5.3 Set course of action for communicating change |
| Deliverables |
|
|
|
|
|
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: Set Realistic Goals for Project Intake, Approval, and Prioritization Process Proposed Time to Completion: 1-2 weeks |
|---|
|
Step 1.1: Define the project valuation criteria Start with an analyst kick-off call:
Then complete these activities…
With these tools & templates: Project Value Scorecard Development Tool |
Step 1.2: Envision your process target state Start with an analyst kick-off call:
Then complete these activities…
With these tools & templates: Project Intake Workflow Template Project Intake, Approval, and Prioritization SOP Template |
Phase 1 Results & Insights:
|
|
Where traditional models of consulting can take considerable amounts of time before delivering value to clients, Info-Tech’s methodology for optimizing project intake, approval, and prioritization process gets you to value fast.
The overarching goal of optimizing project intake, approval, and prioritization process is to maximize the throughput of the best projects. To achieve this goal, one must have a clear way to determine what are “the best” projects.
In the first step of this blueprint, you will pilot a multiple-criteria scorecard for determining project value that will help answer that question. Info-Tech’s Project Value Scorecard Development Tool is pre-populated with a ready-to-use, real-life example that you can leverage as a starting point for tailoring it to your organization – or adopt as is.
Introduce objectivity and clarity to your discussion of maximizing the value of your project portfolio with Info-Tech’s practical IT research that drives measurable results.
Download Info-Tech’s Project Value Scorecard Development Tool.
| PHASE 1 | PHASE 2 | PHASE 3 | ||||
|
1.1 Define project valuation criteria |
1.2 Envision process target state |
2.1 Streamline intake |
2.2 Right-size approval steps |
2.3 Prioritize projects to fit resource capacity |
3.1 Pilot your optimized process |
3.2 Communicate organizational change |
PPM’s goal is to maximize the throughput of projects that provide strategic and operational value to the organization. To do this, a PPM strategy must help to:
| Info-Tech's Project Portfolio Management Process Model |
| 3. Status & Progress Reporting |
| 1. Intake, Approval & Prioritization | 2. Resource Management | 3. Project Management | 4. Project Closure | 5. Benefits Tracking |
| Intake | Execution | Closure |
If you don’t yet have a PPM strategy in place, or would like to revisit your existing PPM strategy before optimizing your project intake, approval, and prioritization practices, see Info-Tech’s blueprint, Develop a Project Portfolio Management Strategy.
In today’s organizations, the desires of business units for new products and enhancements, and the appetites of senior leadership to approve more and more projects for those products and services, far outstrip IT’s ability to realistically deliver on everything.
The vast majority of IT departments lack the resourcing to meet project demand – especially given the fact that day-to-day operational demands frequently trump project work.
As a result, project throughput suffers – and with it, IT’s reputation within the organization.
Where does the time go? The portfolio manager (or equivalent) should function as the accounting department for time, showing what’s available in IT’s human resources budget for projects and providing ongoing visibility into how that budget of time is being spent.
Most of the problems that arise during the lifecycle of a project can be traced back to issues that could have been mitigated during the initiation phase.
More than simply a means of early problem detection at the project level, optimizing your initiation processes is also the best way to ensure the success of your portfolio. With optimized intake processes you can better guarantee:
80% of organizations feel their portfolios are dominated by low-value initiatives that do not deliver value to the business (Source: Cooper).
"(S)uccessful organizations select projects on the basis of desirability and their capability to deliver them, not just desirability" (Source: John Ward, Delivering Value from Information Systems and Technology Investments).
Every organization needs to explicitly define how to determine project value that will fairly represent all projects and provide a basis of comparison among them during approval and prioritization. Without it, any discussions on reducing “low-value initiatives” from the previous slide cannot yield any actionable plan.
However, defining the project value is difficult, because there are so many different and conflicting ways that are all valid in their own right and worth considering. For example:
This challenge is further complicated by the difficulty of identifying the right criteria for determining project value:
Managers fail to identify around 50% of the important criteria when making decisions (Source: Transparent Choice).
Sometimes it can be challenging to show the value of IT-centric, operational-type projects that maintain critical infrastructure since they don’t yield net-new benefits. Remember that benefits are only half the equation; you must also consider the costs of not undertaking the said project.
Scorecard-driven approach is an easy-to-understand, time-tested solution to a multiple-criteria decision-making problem, such as project valuation.
This approach is effective for capturing benefits and costs that are not directly quantifiable in financial terms. Projects are evaluated on multiple specific questions, or criteria, that each yield a score on a point scale. The overall score is calculated as a weighted sum of the scores.
Info-Tech’s Project Value Scorecard is pre-populated with a best-practice example of eight criteria, two for each category (see box at bottom right). This example helps your effort to develop your own project scorecard by providing a solid starting point:
60%: On their own, decision makers could only identify around 6 of their 10 most important criteria for making decisions (Source: Transparent Choice).
Finally, in addition, the overall scores of approved projects can be used as a metric on which success of the process can be measured over time.
Download Info-Tech’s Project Value Scorecard Development Tool.
This tab lists eight criteria that cover strategic alignment, operational alignment, feasibility, and financial benefits/risks. Each criteria is accompanied by a qualitative score description to standardize the analysis across all projects and analysts. While this tool supports up to 15 different criteria, it’s better to minimize the number of criteria and introduce additional ones as the organization grows in PPM maturity.
Type: It is useful to break down projects with similar overall scores by their proposed values versus ease of execution.
Scale: Five-point scale is not required for this tool. Use more or less granularity of description as appropriate for each criteria.
Blank Criteria: Rows with blank criteria are greyed out. Enter a new criteria to turn on the row.
In this tab, you can see how projects are prioritized when they are scored according to the criteria from the previous tab. You can enter the scores of up to 30 projects in the scorecard table (see screenshot to the right).
Value (V) or Execution (E) & Relative Weight: Change the relative weights of each criteria and review any changes to the prioritized list of projects change, whose rankings are updated automatically. This helps you iterate on the weights to find the right mix.
Feasibility: Custom criteria category labels will be automatically updated.
Overall: Choose the groupings of criteria by which you want to see the prioritized list. Available groupings are:
Ranks and weighted scores for each project is shown.
For example, click on the drop-down and choose “Execution.”
Project ranks are based only on execution criteria.
Follow the steps below to test Info-Tech’s example Project Value Scorecard and examine the prioritized list of projects.
INPUT
OUTPUT
Materials
Participants
Conduct a retrospective of the previous activity by asking these questions:
Iterate on the project valuation criteria:
INPUT
OUTPUT
Materials
Participants
In this step, you’ve begun improving the definition of project value. Getting it right will require several more iterations and will require a series of discussions with your key stakeholders.
The optimized intake process built around the new definition of project value will help evolve a conceptual discussion about project value into a more practical one. The new process will paint a picture of what the future state will look like for your stakeholders’ requested projects getting approved and prioritized for execution, so that they can provide feedback that’s concrete and actionable. To help you with that process, you will be taken through a series of activities to analyze the impact of change on your stakeholders and create a communication plan in the last phase of the blueprint.
For now, in the next step of this blueprint, you will undergo a series of activities to assess your current state to identify the specific areas for process optimization.
"To find the right intersection of someone’s personal interest with the company’s interest on projects isn’t always easy. I always try to look for the basic premise that you can get everybody to agree on it and build from there… But it’s sometimes hard to make sure that things stick. You may have to go back three or four times to the core agreement."
| PHASE 1 | PHASE 2 | PHASE 3 | ||||
1.1 Define project valuation criteria | 1.2 Envision process target state | 2.1 Streamline intake | 2.2 Right-size approval steps | 2.3 Prioritize projects to fit resource capacity | 3.1 Pilot your optimized process | 3.2 Communicate organizational change |
This step is highly recommended but not required. Call 1-888-670-8889 to inquire about or request the PPM Diagnostics.
Info-Tech's Project Portfolio Management Assessmentprovides you with a data-driven view of the current state of your portfolio, including your intake processes. Our PPM Assessment measures and communicates success in terms of Info-Tech’s best practices for PPM.
Use the diagnostic program to:
* Steps denote the place in the blueprint where the steps are discussed in more detail.
Use this workflow as a baseline to examine your current state of the process in the next slide.
Conduct a table-top planning exercise to map out the processes currently in place for project intake, approval, and prioritization.
INPUT
OUTPUT
Materials
Participants
Document the results of the previous table-top exercise (Activity 1.1.1) into a flow chart. Flowcharts provide a bird’s-eye view of process steps that highlight the decision points and deliverables. In addition, swim lanes can be used to indicate process stages, task ownership, or responsibilities (example below).
Review and customize section 1.2, “Overall Process Workflow” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
"Flowcharts are more effective when you have to explain status and next steps to upper management."
– Assistant Director-IT Operations, Healthcare Industry
Browser-based flowchart tool examples
INPUT
OUTPUT
Materials
Participants
Download Info-Tech’s Project Intake Workflow Template (Visio and PDF)
In the previous activity, accountable and responsible stakeholders for each of the steps in the current intake, approval, and prioritization process were identified.
INPUT
OUTPUT
Materials
Participants
There are three dimensions for stakeholder prioritization: influence, interest, and support.
These parameters will inform how to prioritize your stakeholders according to the stakeholder priority heatmap (bottom right). This priority should inform how to focus your attention during the subsequent optimization efforts.
| Level of Support | |||||
|---|---|---|---|---|---|
| Stakeholder Category | Supporter | Evangelist | Neutral | Blocker | |
| Engage | Critical | High | High | Critical | |
| High | Medium | Low | Low | Medium | |
| Low | High | Medium | Medium | High | |
| Passive | Low | Irrelevant | Irrelevant | Low | |
There may be too many stakeholders to be able to achieve complete satisfaction. Focus your attention on the stakeholders that matter the most.
Use Info-Tech’s Intake Capability Framework to help define your current and target states for intake, approval, and prioritization.
| Capability Level | Capability Level Description |
|---|---|
| Capability Level 5: Optimized | Our department has effective intake processes with right-sized administrative overhead. Work is continuously prioritized to keep up with emerging challenges and opportunities. |
| Capability Level 4: Aligned | Our department has very strong intake processes. Project approvals are based on business cases and aligned with future resource capacity. |
| Capability Level 3: Engaged | Our department has processes in place to track project requests and follow up on them. Priorities are periodically re-evaluated, based largely on the best judgment of one or several executives. |
| Capability Level 2: Defined | Our department has some processes in place but no capacity to say no to new projects. There is a formal backlog, but little or no method for grooming it. |
| Capability Level 1: Unmanaged | Our department has no formal intake processes in place. Most work is done reactively, with little ability to prioritize proactive project work. |
Refer to the subsequent slides for more detail on these capability levels.
Use these descriptions to place your organization at the appropriate level of intake capability.
| Intake | Projects are requested through personal conversations and emails, with minimal documentation and oversight. |
|---|---|
| Approval | Projects are approved by default and rarely (if ever) declined. There is no definitive list of projects in the pipeline or backlog. |
| Prioritization | Most work is done reactively, with little ability to prioritize proactive project work. |
PMOs at this level should work to have all requests funneled through a proper request form within six months. Decision rights for approval should be defined, and a scorecard should be in place within the year.
To get a handle on your backlog, start tracking all project requests using the “Project Data” tab in Info-Tech’s Project Intake and Prioritization Tool.
Use these descriptions to place your organization at the appropriate level of intake capability.
| Intake | Requests are formally documented in a request form before they’re assigned, elaborated, and executed as projects. |
|---|---|
| Approval | Projects are approved by default and rarely (if ever) declined. There is a formal backlog, but little or no method for grooming it. |
| Prioritization | There is a list of priorities but no process for updating it more than annually or quarterly. |
PMOs at this level should strive for greater visibility into the portfolio to help make the case for declining (or at least deferring) requests. Within the year, have a formal PPM strategy up and running.
Something PMOs at this level can accomplish quickly without any formal approval is to spend more time with stakeholders during the ideation phase to better define scope and requirements.
Use these descriptions to place your organization at the appropriate level of intake capability.
| Intake | Processes and skills are in place to follow up on requests to clarify project scope before going forward with approval and prioritization. |
|---|---|
| Approval | Projects are occasionally declined based on exceptionally low feasibility or value. |
| Prioritization | Priorities are periodically re-evaluated based largely on the best judgment of one or several executives. |
PMOs at this level should advocate for a more formal cadence for prioritization and, within the year, establish a formal steering committee that will be responsible for prioritizing and re-prioritizing quarterly or monthly.
At the PMO level, employ Info-Tech’s Project Intake and Prioritization Tool to start re-evaluating projects in the backlog. Make this data available to senior executives when prioritization occurs.
Use these descriptions to place your organization at the appropriate level of intake capability.
| Intake | Occurs through a centralized process. Processes and skills are in place for follow-up. |
|---|---|
| Approval | Project approvals are based on business cases and aligned with future resource capacity. |
| Prioritization | Project prioritization is visibly aligned with business goals. |
PMOs at this level can strive for more accurate and frequent resource forecasting, establishing a more accurate picture of project vs. non-project work within the year.
PMOs at this level can start using Info-Tech’s Business Case Template (Comprehensive or Fast Track) to help simplify the business case process.
Use these descriptions to place your organization at the appropriate level of intake capability.
| Intake | Occurs through a centralized portal. Processes and skills are in place for thorough follow-up. |
|---|---|
| Approval | Project approvals are based on business cases and aligned with future resource capacity. |
| Prioritization | Work is continuously prioritized to keep up with emerging challenges and opportunities. |
PMOs at this level should look at Info-Tech’s Manage an Agile Portfolio for comprehensive tools and guidance on maintaining greater visibility at the portfolio level into work in progress and committed work.
| Current State: | |
|---|---|
| Target State: | |
| Timeline for meeting target |
INPUT
OUTPUT
Materials
Participants
To frame the discussion on deciding what intake success will look like, review Info-Tech’s PPM strategic expectations:
For a more detailed discussion and insight on PPM strategic expectations see Info-Tech’s blueprint, Develop a Project Portfolio Management Strategy.
While assessing your current state, it is important to discuss and determine as a team how success will be defined.
| Optimization Benefit | Objective | Timeline | Success Factor |
|---|---|---|---|
| Facilitate project intake, prioritization, and communication with stakeholders to maximize time spent on the most valuable or critical projects. | Look at pipeline as part of project intake approach and adjust priorities as required. | July 1st | Consistently updated portfolio data. Dashboards to show back capacity to customers. SharePoint development resources. |
Review and customize section 1.5, “Process Success Criteria” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
Establish realistic short-term goals. Even with optimized intake procedures, you may not be able to eliminate underground project economies immediately. Make your initial goals realistic, leaving room for those walk-up requests that may still appear via informal channels.
The current state explored and documented in this step will serve as a starting point for each step of the next phase of the blueprint. The next phase will take a deeper dive into each of the three components of Info-Tech’s project intake methodology, so that they can achieve the success criteria you’ve defined in the previous activity.
Info-Tech’s Project Intake, Approval, and Prioritization SOP Template is intended to capture the outcome of your process optimization efforts. This blueprint guides you through numerous activities designed for your core project portfolio management team to customize each section.
To maximize the chances of success, it is important that the team makes a concerted effort to participate. Schedule a series of working sessions over the course of several weeks for your team to work through it – or get through it in one week, with onsite Info-Tech analyst-facilitated workshops.
Download Info-Tech’s Project Intake, Approval, and Prioritization SOP.
Contact your account representative or email Workshops@InfoTech.com for more information.
Industry: Not-for-Profit
Source: Info-Tech Interview
Prioritization was a challenge. Initially, the organization had ad hoc prioritization practices, but they had developed a scoring criteria to give more formality and direction to the portfolio. However, the activity of formally prioritizing proved to be too time consuming.
Off-the-grid projects were a common problem, with initiatives consuming resources with no portfolio oversight.
After trying “heavy” prioritization, the PMO loosened up the process. PMO staff now go through and quickly rank projects, with two senior managers making the final decisions. They re-prioritize quarterly to have discussions around resource availability and to make sure stakeholders are in tune to what IT is doing on a daily basis. IT has a monthly meeting to go over projects consuming resources and to catch anything that has fallen between the cracks.
"Everything isn't a number one, which is what we were dealing with initially. We went through a formal prioritization period, where we painstakingly scored everything. Now we have evolved: a couple of senior managers have stepped up to make decisions, which was a natural evolution from us being able to assign a formal ranking. Now we are able to prioritize more easily and effectively without having to painstakingly score everything."
– PMO Director, Benefits Provider
1.1.1-2
Pilot Info-Tech’s Project Value Scorecard-driven prioritization method
Use Info-Tech’s example to prioritize your current project backlog to pilot a project value-driven prioritization, which will be used to guide the entire optimization process.
1.2.1-3
Map out and document current project intake, approval, and prioritization process, and the involved key stakeholders
A table-top planning exercise helps you visualize the current process in place and identify opportunities for optimization.
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: Build an Optimized Project Intake, Approval, and Prioritization Process Proposed Time to Completion: 3-6 weeks | ||
|---|---|---|
Step 2.1: Streamline Intake Start with an analyst kick-off call:
Then complete these activities…
With these tools & templates:
| Step 2.2: Right-Size Approval Start with an analyst call:
Then complete these activities…
With these tools & templates:
| Step 3.3: Prioritize Realistically Start with an analyst call:
Then complete these activities…
With these tools & templates:
|
Phase 2 Results & Insights:
| ||
| PHASE 1 | PHASE 2 | PHASE 3 | ||||
1.1 Define project valuation criteria | 1.2 Envision process target state | 2.1 Streamline intake | 2.2 Right-size approval steps | 2.3 Prioritize projects to fit resource capacity | 3.1 Pilot your optimized process | 3.2 Communicate organizational change |
Off-the-grid projects, i.e. projects that circumvent formal intake processes, lead to underground economies that can deplete resource capacity and hijack your portfolio.
These underground economies are typically the result of too much intake red tape. When the request process is made too complex or cumbersome, project sponsors may unsurprisingly seek alternative means to get their projects done.
While the most obvious line of defence against the appearance of underground economies is an easy-to-use and access request form, one must be cautious. Too little intake formality could lead to a Wild West of project intake where everyone gets their initiatives approved regardless of their business merit and feasibility.
| Benefits of optimized intake | Risks of poor intake |
|---|---|
| Alignment of portfolio with business goals | Portfolio overrun by off-the-grid projects |
| Resources assigned to high-value projects | Resources assigned to low-value projects |
| Better throughput of projects in the portfolio | Ever-growing project backlog |
| Strong stakeholder relations | Stakeholders lose faith in value of PMO |
Intake is intimately bound to stakeholder management. Finding the right balance of friction for your team is the key to successfully walking the line between asking for too much and not asking for enough. If your intake process is strong, stakeholders will no longer have any reason to circumvent formal process.
If you relate to the graphic below in any way, your first priority needs to be limiting the means by which projects get requested. A single, centralized channel with review and approval done in batches is the goal. Otherwise, with IT’s limited capacity, most requests will simply get added to the backlog.
The PMO needs to have the authority – and needs to exercise the authority – to enforce discipline on stakeholders. Organizations that solicit in verbal requests (by phone, in person, or during scrum) lack the orderliness required for PPM success. In these cases, it needs to be the mission of the PMO to demand proper documentation and accountability from stakeholders before proceeding with requests.
"The golden rule for the project documentation is that if anything during the project life cycle is not documented, it is the same as if it does not exist or never happened…since management or clients will never remember their undocumented requests or their consent to do something."
– Dan Epstein, “Project Initiation Process: Part Two”
1. Requestor fills out form and submits the request.
Project Request Form Templates
2. Requests are triaged into the proper queue.
Project Intake Classification Matrix
3. BA or PM prepares to develop requests into a project proposal.
Benefits Commitment Form Template
4. Requestor is given realistic expectations for approval process.
Optimizing project intake may not require a complete overhaul of your existing processes. You may only need to tweak certain templates or policies. Perhaps you started out with a strong process and simply lost resolve over time – in which case you will need to focus on establishing motivation and discipline, rather than rework your entire process.
Perform a start-stop-continue exercise with your team to help determine what should be salvaged, what should be abandoned, and what should be introduced:
| 1. On a whiteboard or equivalent, write “Start,” “Stop,” and “Continue” in three separate columns. | 3. As a group, discuss the responses and come to an agreement as to which are most valid. |
| 2. Equip your team with sticky notes or markers and have them populate the columns with ideas and suggestions surrounding your current processes. | 4. Document the responses to help structure your game plan for intake optimization. |
| Start | Stop | Continue |
|
|
|
INPUT
OUTPUT
Materials
Participants
It is important to identify all of the ways through which projects currently get requested and initiated, especially if you have various streams of intake competing with each other for resources and a place in the portfolio. Directing multiple channels into a single, centralized funnel is step number one in optimizing intake.
To help you identify project sources within your organization, we’ve broken project requests into three archetypes: the good, the bad, and the ugly.
1. The Good – Proper Requests: written formal requests that come in through one appropriate channel.
The Bad – Walk-Ups: requests that do not follow the appropriate intake channel(s), but nevertheless make an effort to get into the proper queue. The most common instance of this is a portfolio manager or CIO filling out the proper project request form on behalf of, and under direction from, a senior executive.
The Ugly – Guerilla Tactics: initiatives that make their way into the portfolio through informal methods or that consume portfolio resources without formal approval, authority, or oversight. This typically involves a key resource getting ambushed to work on a stakeholder’s “side project” without any formal approval from, or knowledge of, the PMO.
Decide how you would funnel project requests on a single portal for submitting project requests. Determining the right portal for your organization will depend on your current infrastructure options, as well as your current and target state capability levels.
Below are examples of a platform for your project request portal.
| Platform | Template document, saved in a repository or shared drive | Email-based form (Outlook forms) | Intranet form (SharePoint, internal CMS) | Dedicated intake solution (PPM tool, idea/innovation tool) |
|---|---|---|---|---|
| Pros | Can be deployed very easily | Consolidates requests into a single receiver | Users have one place to go from any device | All-in-one solution that includes scoring and prioritization |
| Cons | Manual submission and intake process consumes extra effort | Can pose problems in managing requests across multiple people and platforms | Requires existing intranet infrastructure and some development effort | Solution is costly; requires adoption across all lines of business |
Increasing intake capability and infrastructure availability
The key to an effective intake process is determining the right amount of friction to include for your organization. In this context, friction comes from the level of granularity within your project request form and the demands or level of accountability your intake processes place on requestors. You will want to have more or less friction on your intake form, depending on your current intake pain points.
If you are inundated with a high volume of requests:
If you want to encourage the use of a formal channel:
Download Info-Tech’s Detailed Project Request Form.
Download Info-Tech’s Light Project Request Form.
Optimizing a process should not automatically mean reducing friction. Blindly reducing friction could generate a tidal wave of poorly thought-out requests, which only drives up unrealistic expectations. Mitigate the risk of unrealistic stakeholder expectations by carefully managing the message: optimize friction.
Review and customize section 2.2, “Receive project requests” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
The goal of optimizing this process is to consolidate multiple intake channels into a single funnel with the right amount of friction to improve visibility and manageability of incoming project requests.
The important decisions to document for this step include:
INPUT
OUTPUT
Materials
Participants
Whatever method of request collection you choose, ensure there is no doubt about how requesters can access the intake form.
Once a request has been submitted, it will need to be triaged. Triage begins as soon as the request is received. The end goal of the triage process is to set appropriate expectations for stakeholders and to ensure that all requests going forward for approval are valid requests.
PPM Triage Process
The PMO Triage Team
“Request Liaison” Role
The BAs and PMs who follow up on requests play an especially important role in the triage process. They serve as the main point of contact to the requestor as the request evolves into a business case. In this capacity they perform a valuable stakeholder management function, helping to increase confidence and enhance trust in IT.
What constitutes a project?
Another way of asking this question that gets more to the point for this blueprint – for what types of initiatives is project intake, approval, and prioritization rigor required?
This is especially true in IT where, for some smaller initiatives, there can be uncertainty in many organizations during the intake and initiation phase about what should be included on the formal project list and what should go to help desk’s queue.
As the definitions in the table below show, formal project management frameworks each have similar definitions of “a project.”
| Source | Definition |
|---|---|
| PMI | A temporary endeavor undertaken to create a unique product, service, or result.” (553) |
| COBIT | A structured set of activities concerned with delivering a defined capability (that is necessary but not sufficient to achieve a required business outcome) to the enterprise based on an agreed‐on schedule and budget.” (74) |
| PRINCE2 | A temporary organization that is created for the purpose of delivering one or more business products according to an agreed business case. |
For each, a project is a temporary endeavor planned around producing a specific organizational/business outcome. The challenge of those small initiatives in IT is knowing when those endeavors require a business case, formal resource tracking, and project management rigor, and when they don’t.
In the next step, we will define a suggested minimum threshold for a small “level 1” project. While these level thresholds are good and necessary for a number of reasons – including triaging your project requests – you may still often need to exercise some critical judgment in separating the tickets from the projects. In addition to the level criteria that we will develop in this step, use the checklist below to help with your differentiating.
| Service Desk Ticket | Small Project |
|---|---|
|
|
Guard the value of the portfolio. Because tickets carry with them an implicit approval, you need to be wary at the portfolio level of those that might possess a larger scope than their status of ticket implies. Sponsors that, for whatever reason, resist the formal intake process may use the ticketing process to sneak projects in through the backdoor. When assessing tickets and small projects at the portfolio level, you need to ask: is it possible that someone at an executive level might want to get updates on this because of its duration, scope, risk, cost, etc.? Could someone at the management level get upset that the initiative came in as a ticket and is burning up time and driving costs without any visibility?
| Non-Project | Small Project | |
|---|---|---|
| e.g. Time required | e.g. < 40 hours | e.g. 40 > hours |
| e.g. Complexity | e.g. Very low | e.g. Moderate – Low Difficulty: Does not require highly developed or specialized skill sets |
| e.g. Collaboration | e.g. None required | e.g. Limited coordination and collaboration between resources and departments |
| e.g. Repeatability of work | e.g. Fully repeatable | e.g. Less predictable |
| e.g. Frequency of request type | e.g. Hourly to daily | e.g. Weekly to monthly |
"If you worked for the help desk, over time you would begin to master your job since there is a certain rhythm and pattern to the work…On the other hand, projects are unique. This characteristic makes them hard to estimate and hard to manage. Even if the project is similar to one you have done before, new events and circumstances will occur. Each project typically holds its own challenges and opportunities"
– Jeffrey and Thomas Mochal
Follow the steps below to define the specifics of a “level 1” project for your organization.
INPUT
OUTPUT
Materials
Participants
During triaging, requestors should be notified as quickly as possible (a) that their request has been received and (b) what to expect next for the request. Make this forum as productive and informative as possible, providing clear direction and structure for the future of the request. Be sure to include the following:
The logistic of this follow-up will depend on a number of different factors.
Assign an official request number or project ID to all requests during this initial response. An official request number anchors the request to a specific and traceable dataset that will accompany the project throughout its lifecycle.
If you receive a high volume of requests or need a quick win for improving stakeholder relations:
Sample #1: Less detailed, automatic response
Hello Emma,
Thank you. Your project request has been received. Requests are reviewed and assigned every Monday. A business analyst will follow up with you in the next 5-10 business days. Should you have any questions in the meantime, please reply to this email.
Best regards,
Information Technology Services
If stakeholder management is a priority, and you want to emphasize the customer-facing focus:
Sample #2: More detailed, tailored response
Hi Darren,
Your project request has been received and reviewed. Your project ID number is #556. Business analyst Alpertti Attar has been assigned to follow up on your request. You can expect to hear from him in the next 5-10 business days to set up a meeting for preliminary requirements gathering.
If you have any questions in the meantime, please contact Alpertti at aattar@projectco.com. Please include the Project ID provided in this email in all future correspondences regarding this request.
Thank you for your request. We look forward to helping you bring this initiative to fruition.
Sincerely,
Jim Fraser
PMO Director, Information Technology Services
A simple request response will go a long way in terms of stakeholder management. It will not only help assure stakeholders that their requests are in progress but the request confirmation will also help to set expectations and take some of the mystery out of IT’s processes.
Review and customize section 2.3, “Triage project requests” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
The goal of optimizing this process is to divert non-project requests and set an appropriate initial set of stakeholder expectations for next steps. The important decisions to document for this step include:
INPUT
OUTPUT
Materials
Participants
Whatever method of request collection you choose, ensure there is no doubt about how requesters can access the intake form.
The purpose of this follow-up is to foster communication among the requestor, IT, and the sponsor to scope the project at a high level. The follow-up should:
Once a Request Liaison (RL) has been assigned to a request, it is their responsibility to schedule time (if necessary) with the requestor to perform a scoping exercise that will help define preliminary requirements. Ideally, this follow-up should occur no later than a week of the initial request.
Structure the follow-up for each request based on your preliminary estimates of project size (next slide). Use the “Key Pieces of Scope” to the left as a guide.
It may also be helpful for RLs and stakeholders to work together to produce a rough diagram or mock-up of the final deliverable. This will ensure that the stakeholder’s idea has been properly communicated, and it could also help refine or broaden this idea based on IT’s capabilities.
After the scoping exercise, it is the RL’s responsibility to inform the requestor of next steps.
More time spent with stakeholders defining high-level requirements during the ideation phase is key to project success. It will not only improve the throughput of projects, but it will enhance the transparency of IT’s capacity and enable IT to more effectively support business processes.
Project estimation is a common pain point felt by many organizations. At this stage, a range-of-magnitude (ROM) estimate is sufficient for the purposes of sizing the effort required for developing project proposals with appropriate detail.
A way to structure ROM estimates is to define a set of standard project levels. It will help you estimate 80% of projects with sufficient accuracy over time with little effort. The remaining 20% of projects that don’t meet their standard target dates can be managed as exceptions.
The increased consistency of most projects will enable you to focus more on managing the exceptions.
Example of standard project sizes:
| Level | Primary unit of estimation | Target completion date* |
|---|---|---|
| 1 | Weeks | 3 weeks – 3 months |
| 2 | Months | 3 months – 6 months |
| 3 | Quarters | 2 – 4 quarters |
| 3+ | Years | 1 year or more |
* Target completion date is simply that – a target, not a service level agreement (SLA). Some exceptions will far exceed the target date, e.g. projects that depend heavily on external or uncontrollable factors.
Project levelling is useful for right-sizing many downstream processes; it sets appropriate levels of detail and scrutiny expected for project approval and prioritization steps, as well as the appropriate extent of requirements gathering, project management, and reporting requirements afterwards.
Now that the minimum threshold for your smallest projects has been identified, it’s time to identify the maximum threshold in order to better apply project intake, approval, and prioritization rigor where it’s needed.
INPUT
OUTPUT
Materials
Participants
| Project Level | Level 1 | Level 2 | Level 3 |
|---|---|---|---|
| Work Effort | 40-100 hours | 100-500 hours | 500+ hours |
| Budget | $100,000 and under | $100,000 to $500,000 | $500,000 and over |
| Technology | In-house expertise | Familiar | New or requires system-wide change/training |
| Complexity | Well-defined solution; no problems expected | Solution is known; some problems expected | Solution is unknown or not clearly defined |
| Cross-Functional Workgroups/Teams | 1-2 | 3-5 | > 6 |
Capture the project levels in Info-Tech’s Project Intake Classification Matrix Tool to benchmark your levelling criteria and to determine project levels for proposed projects.
Download Info-Tech’s Project Intake Classification Matrix tool.
In most organizations a project requires sponsorship from the executive layer, especially for strategic initiatives. The executive sponsor provides several vital factors for projects:
Sometimes a project request may be made directly by a sponsor; in other times, the Request Liaison may need to connect the project request to a project sponsor.
In either case, project request has a tentative buy-in and support of an executive sponsor before a project request is developed into a proposal and examined for approval – the subject of this blueprint’s next step.
PMs and Sponsors: The Disconnect
A study in project sponsorship revealed a large gap between the perception of the project managers and the perception of sponsors relative to the sponsor capability. The widest gaps appear in the areas of:
Source: Boston Consulting Group/PMI, 2014
Actively engaged executive sponsors continue to be the top driver of whether projects meet their original goals and business intent.
– PMI Pulse of the Profession, 2017
76% of respondents [organizations] agree that the role of the executive sponsor has grown in importance over the past five years.
– Boston Consulting Group/PMI, 2014
Review and customize section 2.4, “Follow up on project requests” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
The goal of optimizing this process is to initiate communication among the requestor, IT, and the sponsor to scope the project requests at a high level. The important decisions to document for this step include:
INPUT
OUTPUT
Materials
Participants
Review and customize section 2.1, “Project Intake Workflow” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
In Step 1.2 of the blueprint, you mapped out the current project intake, approval, and prioritization workflow and documented it in a flow chart. In this step, take the time to examine the new project intake process as a whole, and document the new workflow in the form of a flow chart.
Consider the following points:
INPUT
OUTPUT
Materials
Participants
Industry: Municipal Government
Source: Info-Tech Client
| PHASE 1 | PHASE 2 | PHASE 3 | ||||
1.1 Define project valuation criteria | 1.2 Envision process target state | 2.1 Streamline intake | 2.2 Right-size approval steps | 2.3 Prioritize projects to fit resource capacity | 3.1 Pilot your optimized process | 3.2 Communicate organizational change |
| Challenges | Info-Tech’s Advice |
|---|---|
| Project sponsors receive funding from their business unit or other source (possibly external, such as a grant), and assume this means their project is “approved” without any regard to IT costs or resource constraints. | Clearly define a series of approval steps, and communicate requirements for passing them. |
| Business case documentation is rarely updated to reflect unforeseen costs, emerging opportunities, and changing priorities. As a result, time and money is spent finishing diminished priority projects while the value of more recent projects erodes in the backlog. | Approve projects in smaller pieces, with early test/pilot phases focused on demonstrating the value of later phases. |
| Project business cases often focus on implementation and overlook ongoing operating costs imposed on IT after the project is finished. These costs further diminish IT’s capacity for new projects, unless investment in more capacity (such as hiring) is included in business cases. | Make ongoing support and maintenance costs a key element in business case templates and evaluations. |
| Organizations approve new projects without regard to the availability of resource capacity (or lack thereof). Project lead times grow and stakeholders become more dissatisfied because IT is unable to show how the business is competing with itself for IT’s time. | Increase visibility into what IT is already working on and committed to, and for whom. |
Clearly define a series of approval steps, and communicate requirements for passing them. “Approval” can be a dangerous word in project and portfolio management, so it is important to clarify what is required to pass each step, and how long the process will take.
| 1 | 2 | 3 | 4 | |
|---|---|---|---|---|
| Approval step | Concept Approval | Feasibility Approval | Business Case Approval | Resource Allocation (Prioritization) |
| Alignment Focus | Business need / Project sponsorship | Technology | Organization-wide business need | Resource capacity |
| Possible dispositions at each gate |
|
|
|
|
| Accountability | e.g. Project Sponsor | e.g. CIO | e.g. Steering Committee | e.g. CIO |
| Deliverable | Benefits Commitment Form Template | Proposed Project Technology Assessment Tool | Business Case (Fast Track, Comprehensive) | Intake and Prioritization Tool |
In general, there are three different, mutually exclusive decision-making paradigms for approving projects:
| Paradigm | Description | Benefits | Challenges | Recommendation |
|---|---|---|---|---|
| Unilateral authority | One individual makes decisions. | Decisions tend to be made efficiently and unambiguously. Consistency of agenda is easier to preserve. | Decisions are subject to one person’s biases and unseen areas. | Decision maker should solicit and consider input from others and seek objective rigor. |
| Ad hoc deliberation | Stakeholders informally negotiate and communicate decisions between themselves. | Deliberation helps ensure different perspectives are considered to counterbalance individual biases and unseen areas. | Ad hoc decisions tend to lack documentation and objective rationale, which can perpetuate disagreement. | Use where unilateral decisions are unfeasible (due to complexity, speed of change, culture, etc.), and stakeholders are very well aligned or highly skilled negotiators and communicators. |
| Formal steering committee | A select group that represent various parts of the organization is formally empowered to make decisions for the organization. | Formal committees can ensure oversight into decisions, with levers available to help resolve uncertainty or disagreement. | Formal committees introduce administrative overhead and effort that might not be warranted by the risks involved. | Formal steering committees are best where formality is warranted by the risks and costs involved, and the organizational culture has an appetite for administrative oversight. |
The individual or party who has the authority to make choices, and who is ultimately answerable for those decisions, is said to be accountable. Understanding the needs of the accountable party is critical to the success of the project approval process optimization efforts.
Optimizing project approval may not require a complete overhaul of your existing processes. You may only need to tweak certain templates or policies. Perhaps you started out with a strong process and simply lost resolve over time – in which case you will need to focus on establishing motivation and discipline, rather than rework your entire process.
Perform a start-stop-continue exercise with your team to help determine what should be salvaged, what should be abandoned, and what should be introduced:
| 1.On a whiteboard or equivalent, write “Start,” “Stop,” and “Continue” in three separate columns. | 3.As a group, discuss the responses and come to an agreement as to which are most valid. |
| 2.Equip your team with sticky notes or markers and have them populate the columns with ideas and suggestions surrounding your current processes. | 4.;Document the responses to help structure your game plan for intake optimization. |
| Start | Stop | Continue |
|---|---|---|
|
|
|
INPUT
OUTPUT
Materials
Participants
Review and customize section 3.2, “Project Approval Steps” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
The goal of this activity is to customize the definition of the approval steps for your organization, so that it makes sense for the existing organizational governance structure, culture, and need. Use the results of the start-stop-continue to inform what to customize. Consider the following factors:
INPUT
OUTPUT
Materials
Participants
Review and customize section 3.2, “Project Approval Steps” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
In the old reality, projects were approved and never heard back from again, which effectively gave your stakeholders a blanket default expectation of “declined.” With the new approval process, manage your stakeholder expectations more explicitly by refining your vocabulary around approval.
Within this, decision makers should view their role in approval as approving that which can and should be done. When a project is approved and slated to backlog, the intention should be to allocate resources to it within the current intake cycle.
Customize the table to the right with organizationally appropriate definitions, and update your SOP.
| “No” | Declined. |
|---|---|
| “Not Now” | “It’s a good idea, but the time isn’t right. Try resubmitting next intake cycle.” |
| “Concept Approval” | Approval to add the item to the backlog with the intention of starting it this intake cycle. |
| “Preliminary Approval” | Approval for consumption of PMO resources to develop a business case. |
| “Full Approval” | Project is greenlighted and project resources are being allocated to it. |
Refine the nomenclature. Add context to “approved” and “declined.” Speak in terms of “not now” or “you can have it when these conditions are met.” With clear expectations of the resources required to support each request, you can place accountability for keeping the request alive back on the sponsors.
Estimates that form the basis of business cases are often based on flawed assumptions. Use early project phases or sprints to build working prototypes to test the assumptions on which business cases are built, rather than investing time improving precision of estimates without improving accuracy.
The next several slides will take you through a series of tools and templates that help guide the production of deliverables. Each deliverable wireframes the required analysis of the proposed project for one step of the approval process, and captures that information in a document. This breaks down the overall work for proposal development into digestible chunks.
As previously discussed, aim to right-size the approval process rigor for project levels. Not all project levels may call for all steps of approval, or the extent of required analysis within an approval step may differ. This section will conclude by customizing the requirement for deliverables for each project level.
Tools and Templates for the Project Approval Toolbox
Project sponsors are accountable for the realization of project benefits. Therefore, for a project to be approved by a project sponsor, they must buy-in and commit to the proposed benefits.
Defining project benefits and obtaining project sponsor commitment has been demonstrated to improve the project outcome by providing the focal point of the project up-front. This will help reduce wasted efforts to develop parts of the proposals that are not ultimately needed.
Download Info-Tech’s Benefits Commitment Form Template.
Contents of a Benefits Commitment Form
For further discussion on benefits realization, use Info-Tech’s blueprint, Establish the Benefits Realization Process.
In some projects, there needs to be an initial idea of what the project might look like. Develop a high-level solution for projects that:
IT should advise and provide subject matter expertise on the technology requirements to those that ultimately approve the proposed projects, so that they can take into account additional costs or risks that may be borne from it.
Info-Tech’s Proposed Project Technology Assessment Tool has a series of questions to address eight categories of considerations to determine the project’s technological readiness for adoption. Use this tool to ensure that you cover all the bases, and help you devise alternate solutions if necessary – which will factor into the overall business case development.
Download Info-Tech’s Proposed Project Technology Assessment Tool.
Traditionally, a business case is centered around financial metrics. While monetary benefits and costs are matters of bottom line and important, financial metrics are only part of a project’s value. As the project approval decisions must be based on the holistic comparison of project value, the business case document must capture all the necessary – and only those that are necessary – information to enable it.
However, completeness of information does not always require comprehensiveness. Allow for flexibility to speed up the process of developing business plan by making a “fast-track” business case template available. This enables the application of the project valuation criteria with all other projects, with right-sized effort.
Alarming business case statistics
(Source: Wrike)
Download Info-Tech’s Comprehensive Business Case Template.
Download Info-Tech’s Fast Track Business Case Template.
Pass on that which is known. Valuable information about projects is lost due to a disconnect between project intake and project initiation, as project managers are typically not brought on board until project is actually approved. This will be discussed more in Phase 3 of this blueprint.
Review and customize section 3.3, “Project Proposal Deliverables” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
The goal of this activity is to customize the requirements for project proposal deliverables, so that it properly informs each of the approval steps discussed in the previous activity. The deliverables will also shape the work effort required for projects of various levels. Consider the following factors:
INPUT
OUTPUT
Materials
Participants
Review and customize section 3.1, “Project Approval Workflow” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
In Step 1.2 of the blueprint, you mapped out the current project intake, approval, and prioritization workflow and documented it in a flow chart. In this step, take the time to examine the new project intake process as a whole, and document the new workflow in the form of a flow chart.
| 1 | 2 | 3 | 4 | |
|---|---|---|---|---|
| Approval Step | Concept Approval | Feasibility Approval | Business Case Approval | Resource Allocation (Prioritization) |
| Alignment Focus | Business need/ Project Sponsorship | Technology |
Organization-wide Business need |
Resource capacity |
Consider the following points:
INPUT
OUTPUT
Materials
Participants
| PHASE 1 | PHASE 2 | PHASE 3 | ||||
1.1 Define project valuation criteria | 1.2 Envision process target state | 2.1 Streamline intake | 2.2 Right-size approval steps | 2.3 Prioritize projects to fit resource capacity | 3.1 Pilot your optimized process | 3.2 Communicate organizational change |
Organizations tend to bite off more than they can chew when it comes to project and service delivery commitments involving IT resources.
While the need for businesses to make an excess of IT commitments is understandable, the impacts of systemically over-allocating IT are clearly negative:
76%: 76% of organizations say they have too many projects on the go and an unmanageable and ever-growing backlog of things to get to.
– Cooper, 2014
70%: Almost 70% of workers feel as though they have too much work on their plates and not enough time to do it.
– Reynolds, 2016
Today, many IT departments use matrix organization. In this system, demands on a resource’s time come from many directions. While resources are expected to prioritize their work, they lack the authority to formally reject any demand. As a result, unconstrained, unmanaged demand frequently outstrips the supply of work-hours the resource can deliver.
When this happens, the resource has three options:
The result is an unsustainable system for all those involved:
| Project Prioritization |
Capacity awareness Many IT departments struggle to realistically estimate available project capacity in a credible way. Stakeholders question the validity of your endeavor to install capacity-constrained intake process, and mistake it for unwillingness to cooperate instead. |
Lack of authority Many PMOs and IT departments simply lack the ability to decline or defer new projects. |
Many moving parts Project intake, approval, and prioritization involve the coordination of various departments. Therefore, they require a great deal of buy-in and compliance from multiple stakeholders and senior executives. |
Project Approval |
|
Unclear definition of value Defining the project value is difficult, because there are so many different and conflicting ways that are all valid in their own right. However, without it, it's impossible to fairly compare among projects to select what's "best." |
Unclear definition of value
In Step 1.1 of the blueprint, we took the first step toward resolving this challenge by prototyping a project valuation scorecard.
"Prioritization is a huge issue for us. We face the simultaneous challenges of not having enough resources but also not having a good way to say no. "
– CIO, governmental health agency
Intake and Prioritization Tool
Optimizing project prioritization may not require a complete overhaul of your existing processes. You may only need to tweak certain templates or policies. Perhaps you started out with a strong process and simply lost resolve over time – in which case you will need to focus on establishing motivation and discipline, rather than rework your entire process.
Perform a start-stop-continue exercise with your team to help determine what should be salvaged, what should be abandoned, and what should be introduced:
| 1. On a whiteboard or equivalent, write “Start,” “Stop,” and “Continue” in three separate columns. | 3. As a group, discuss the responses and come to an agreement as to which are most valid. |
| 2. Equip your team with sticky notes or markers and have them populate the columns with ideas and suggestions surrounding your current processes. | 4. Document the responses to help structure your game plan for intake optimization. |
| Start | Stop | Continue |
|---|---|---|
|
|
|
INPUT
OUTPUT
Materials
Participants
This tool builds on the Project Valuation Scorecard Tool to address the challenges in project prioritization:
Using standard project sizing, quickly estimate the size of the demand for proposed and ongoing projects and produce a report that recommends the list of projects to greenlight – and highlight the projects within that list that are at risk of being short-charged of resources – that will aim to help you tackle:
The next several slides will walk you through the tool and present activities to facilitate its use for your organization.
Download Info-Tech’s Project Intake and Prioritization Tool.
Estimate how many work-hours are at your disposal for projects using Info-Tech’s resource calculator.
1. Compile a list of each role within your department, the number of staff, and the hours in a typical work week.
2. Enter the foreseeable out-of-office time (vacation, sick time, etc.). Typically, this value is 12-16% depending on the region.
3. Enter how much working time is spent on non-projects for each role: administrative duties and “keep the lights on” work.
4. Select a period of time for breaking down available resource capacity in hours.
Project Work (%): Percentage of your working time that goes toward project work is calculated as what’s left after your non-project working time allocations have been subtracted.
Project (h) Total Percentage: Take a note of this percentage as your project capacity. This number will put the estimated project demand in context for the rest of the tool.
Example for a five-day work week:
Result: 7.4/52 weeks’ absence = 14%
Discover how many work-hours are at your disposal for project work.
INPUT
OUTPUT
Materials
Participants
Info-Tech’s PPM Current State Scorecard diagnostic provides a comprehensive view of your portfolio management strengths and weaknesses, including project portfolio management, project management, customer management, and resource utilization.
Use the wisdom of the crowd to estimate resource waste in:
Analyzing, fixing, and redeploying
50% of PPM resource is wasted on average, effectively halving your available project capacity.
Source: Info-Tech PPM Current State Scorecard
The resource capacity calculator in the previous tab yields a likely optimistic estimate for how much project capacity is available. Based on this estimate as a guide, enter your optimistic (maximum) and pessimistic (minimum) estimates of project capacity as a percentage of total capacity:
Info-Tech’s data shows that only about 50% of time spent on project work is wasted: cancelled projects, inefficiency, rework, etc. As a general rule, enter half of your maximum estimate of your project capacity.
Capacity in work hours is shown here from the previous tab, to put the percentages in context. This example shows a quarterly breakdown (Step 4 from the previous slide; cell N5 in Tab 2.).
Next, estimate the percentage of your maximum estimated project capacity that a single project would typically consume in the given period for prioritization.
These project sizes might not line up with the standard project levels from Step 2.1 of the blueprint: for example, an urgent mid-sized project that requires all hands on deck may need to consume almost 100% of maximum available project capacity.
Refine your estimates of project capacity supply and demand as it applies to a prioritization period.
Dedicated work needs dedicated break time
In a study conducted by the Draugiem Group, the ideal work-to-break ratio for maximizing focus and productivity was 52 minutes of work, followed by 17 minutes of rest (Evans). This translates to 75% of resource capacity yielding productive work, which could inform your optimistic estimate of project capacity.
INPUT
OUTPUT
Materials
Participants
Enter the scoring criteria, which was worked out from Step 1.1 of the blueprint. This workbook supports up to ten scoring criteria; use of more than ten may make the prioritization step unwieldy.
Leave unused criteria rows blank.
Choose “value” or “execution” from a drop-down.
Score does not need to add up to 100.
Finally, set up the rest of the drop-downs used in the next tab, Project Data. These can be customized to fit your unique project portfolio needs.
Ensure that each project has a unique name.
Completed (or cancelled) projects will not be included in prioritization.
Choose the standard project size defined in the previous tab.
Change the heading when you customize the workbook.
Days in Backlog is calculated from the Date Added column.
Overall weighted project prioritization score is calculated as a sum of value and execution scores.
Weighted value and execution scores are calculated according to the scoring criteria table in the 2. Settings tab.
Enter the raw scores. Weights will be taken into calculation behind the scenes.
Spaces for unused intake scores will be greyed out. You can enter data, but they will not affect the calculated scores.
Review and customize section 4.2, “Maintain Supply and Demand Data” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
The goal of this activity is to document the process with which the supply and demand information will be updated for projects. Consider the following factors:
INPUT
OUTPUT
Materials
Participants
The output of the Project Intake and Prioritization Tool is a prioritized list of projects with indicators to show that their demand on project capacity will fit within the estimated available project capacity for the prioritization period.
Status indicates whether the project is proposed or ongoing; completed projects are excluded.
Disposition indicates the course of recommended action based on prioritization.
Proposed projects display how long they have been sitting in the backlog.
Projects highlighted yellow are marked as “deliberate” for their dispositions. These projects pose risks of not getting properly resourced. One must proceed with caution if they are to be initiated or continued.
The prioritized list of proposed and ongoing projects, and an approximate indication for how they fill out the estimated available resource capacity, provide a meaningful starting ground for discussion on which projects to continue or initiate, to hold, or to proceed with caution.
However, it is important to recognize the limitation of the prioritization methodology. There may be legitimate reasons why some projects should be prioritized over another that the project valuation method does not successfully capture. At the end of the day, it’s the prerogative of the portfolio owners who carry on the accountabilities to steer the portfolio.
The portfolio manager has a responsibility to be prepared for reconciling the said steering with the unchanged available resource capacity for project work. What comes off the list of projects to continue or initiate? Or, will we outsource capacity if we must meet irreconcilable demand? The next slide will show how Info-Tech’s tool helps you with this process.
Strive to become the best co-pilot. Constantly iterate on the scoring criteria to better adapt to the portfolio owners’ preference in steering the project portfolio.
The Force Disposition list enables you to inject subjective judgment in project prioritization. Force include and outsource override project prioritization scores and include the projects for approval:
Choose a project name and a disposition using a drop-down.
Use this list to test out various scenarios, useful for what-if analysis.
Review and customize section 4.3, “Approve projects for initiation or continuation” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
The goal of this activity is to formalize the process of presenting the prioritized list of projects for review, modify the list based on steering decisions, and obtain the portfolio owners’ approval for projects to initiate or continue, hold, or terminate. Consider the following factors:
INPUT
OUTPUT
Materials
Participants
Once the proposed project is given a green light, the project enters an initiation phase.
No matter what project management methodology is employed, it is absolutely vital to pass on the knowledge gained and insights developed through the intake, approval, and prioritization processes. This ensures that the project managers and team are informed of the project’s purpose, business benefits, rationale for the project approval, etc. and be able to focus their efforts in realizing the project’s business goals.
Recognize that this does not aim to create any new artifacts. It is simply a procedural safeguard against the loss of important and costly information assets for your organization.
Information from the intake process directly feeds into, for example, developing a project charter.
Source: PMBOK, 6th edition
"If the project manager can connect strategy to the project they are leading (and therefore the value that the organization desires by sanctioning the project), they can ensure that the project is appropriately planned and managed to realize those benefits."
– Randall T. Black, P.Eng., PMP; source: PMI Today
Review and customize section 4.1, “Project Prioritization Workflow” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template.
In Step 1.2 of the blueprint, you mapped out the current project intake, approval, and prioritization workflow and documented it in a flow chart. In this step, take the time to examine the new project intake process as a whole, and document the new workflow in the form of a flow chart.
Consider the following points:
INPUT
OUTPUT
Materials
Participants
|
The project capacity estimates overlook a critical piece of the resourcing puzzle for the sake of simplicity: skills. You need the right skills at the right time for the right project. Use Info-Tech’s Balance Supply and Demand with Realistic Resource Management Practices blueprint to enhance the quality of information on your project supply.
|
There is more to organizing your project portfolio than a strict prioritization by project value. For example, as with a financial investment portfolio, project portfolio must achieve the right investment mix to balance your risks and leverage opportunities. Use Info-Tech’s Maintain an Organized Portfolio blueprint to refine the makeup of your project portfolio.
|
|
Continuous prioritization of projects allow organizations to achieve portfolio responsiveness. Use Info-Tech’s Manage an Agile Portfolio blueprint to take prioritization of your project portfolio to the next level.
|
46% of organizations use a homegrown PPM solution. Info-Tech’s Grow Your Own PPM Solution blueprint debuts a spreadsheet-based Portfolio Manager tool that provides key functionalities that integrates those of the Intake and Prioritization Tool with resource management, allocation and portfolio reporting capabilities.
|
2.1.2-6
Optimize your process to receive, triage, and follow up on project requests
Discussion on decision points and topics of consideration will be facilitated to leverage the diverse viewpoints amongst the workshop participants.
2.3.2-5
Set up a capacity-informed project prioritization process using Info-Tech’s Project Intake and Prioritization Tool
A table-top planning exercise helps you visualize the current process in place and identify opportunities for optimization.
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: Integrate the New Optimized Processes into Practice Proposed Time to Completion: 6-12 weeks | |
Step 3.1: Pilot your process to refine it prior to rollout Start with an analyst kick-off call:
Then complete these activities…
With these tools & templates:
| Step 3.2: Analyze the impact of organizational change Review findings with analyst:
Then complete these activities…
With these tools & templates:
|
Phase 3 Results & Insights:
| |
| PHASE 1 | PHASE 2 | PHASE 3 | ||||
1.1 Define project valuation criteria | 1.2 Envision process target state | 2.1 Streamline intake | 2.2 Right-size approval steps | 2.3 Prioritize projects to fit resource capacity | 3.1 Pilot your optimized process | 3.2 Communicate organizational change |
Rome wasn’t built in a day. Similarly, benefits of optimized project intake, approval, and prioritization process will not be realized overnight.
Resist the urge to deploy a big-bang roll out of your new intake practices. The approach is ill advised for two main reasons:
Start with a pilot phase. Identify receptive lines of business and IT resources to work with, and leverage their insights to help iron out the kinks in your process before unveiling your practices to IT and all business users at large.
This step will help you to:
Engagement paves the way for smoother adoption. An “engagement” approach (rather than simply “communication”) turns stakeholders into advocates who can help boost your message, sustain the change, and realize benefits without constant intervention or process command-and-control.
A process pilot is a limited scope of an implementation (constrained by time and resources involved) in order to test the viability and effectiveness of the process as it has been designed.
Download Info-Tech’s Process Pilot Plan Template
"The advantages to a pilot are several. First, risk is constrained. Pilots are closely monitored so if a problem does occur, it can be fixed immediately. Second, the people working in the pilot can become trainers as you roll the process out to the rest of the organization. Third, the pilot is another opportunity for skeptics to visit the pilot process and learn from those working in it. There’s nothing like seeing a new process working for people to change their minds."
Info-Tech recommends selecting PPM stakeholders who are aware of your role and some of the challenges in project intake, approval, and prioritization to assist in the implementation process.
INPUT
OUTPUT
Materials
Participants
Document the PPM stakeholders involved in your pilot in Section 3 of Info-Tech’s Process Pilot Plan Template.
Use Info-Tech’s Process Pilot Plan Template to design the details of your pilot.
Investing time into planning your pilot phase strategically will ensure a clear scope, better communications for those piloting the processes, and – overall – better, more actionable results for the pilot phase. The Pilot Plan Template is broken into five sections to assist in these goals:
The duration of your pilot should go at least one prioritization period, e.g. one to two quarters.
Estimates of time commitments should be captured for each stakeholder. During the retrospective at the end of the pilot you should capture actuals to help determine the time-cost of the process itself and measure its sustainability.
Once the Plan Template is completed, schedule time to share and communicate it with the pilot team and executive sponsors of the process.
While you should invest time in this planning document, continue to lean on the Intake, Approval, and Prioritization SOP throughout the pilot phase.
INPUT
OUTPUT
Materials
Participants
Some things to keep in mind during the pilot include:
Pilot projects allow you to validate your assumptions and leverage lessons learned. During the planning of the pilot, you should have scheduled a retrospective meeting with the pilot team to formally assess strengths and weaknesses in the process you have drafted.
An example of how to structure a Stop/Start/Continue activity on a whiteboard using sticky notes.
INPUT
OUTPUT
Materials
Participants
See the following slide for additional instructions.
As a group, discuss everyone’s responses and organize according to top priority (mark with a 1) and lower priority/next steps (mark with a 2). At this point, you can also remove any sticky notes that are repetitive or no longer relevant.
Once you have organized based on priority, be sure to come to a consensus with the group regarding which actions to take. For example, if the group agrees that they should “stop holding meetings weekly,” come to a consensus regarding how often meetings will be held, i.e. monthly.
| Priority | Action Required | Who is Responsible | Implementation Date |
|---|---|---|---|
| Stop: Holding meetings weekly | Hold meetings monthly | Jane Doe, PMO | Next Meeting: August 1, 2017 |
| Start: Discussing backlog during meetings | Ensure that backlog data is up to date for discussion on date of next meeting. | John Doe, Portfolio Manager | August 1, 2017 |
Create an action plan for the top priority items that require changes (the Stops and Starts). Record in this slide, or your preferred medium. Be sure to include who is responsible for the action and the date that it will be implemented.
Document the outcomes of the start/stop/continue and your action plan in Section 6 of Info-Tech’s Process Pilot Plan Template.
You will need to determine responsibilities and accountabilities for portfolio management functions within your team.
If you do not have a clearly identifiable portfolio manager at this time, you will need to clarify who will wear which hats in terms of facilitating intake and prioritization, high-level capacity awareness, and portfolio reporting.
Download Info-Tech’s Project Backlog Manager job description template.

Update section 1.2, “Overall Process Workflow” in Info-Tech’s Project Intake, Approval, and Prioritization SOP Template with the new process flow.
Revisit your SOP from Phase 2 and ensure it has been updated to reflect the process changes that were identified in activity 3.1.4.
Download Info-Tech’s Project Intake, Approval, and Prioritization SOP template.
Make your SOP high impact. SOPs are often at risk of being left unmaintained and languishing in disuse. Improve the SOP’s succinctness and usability by making it visual; consult Info-Tech’s blueprint, Create Visual SOP Documents that Drive Process Optimization, Not Just Peace of Mind.
| PHASE 1 | PHASE 2 | PHASE 3 | ||||
1.1 Define project valuation criteria | 1.2 Envision process target state | 2.1 Streamline intake | 2.2 Right-size approval steps | 2.3 Prioritize projects to fit resource capacity | 3.1 Pilot your optimized process | 3.2 Communicate organizational change |
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. |
Info-Tech’s Drive Organizational Change from the PMO blueprint offers the OCM Impact Analysis Tool to helps document the change impact across multiple dimensions, enabling the project team to review the analysis with others to ensure that the most important impacts are captured.
This tool has been customized for optimizing project intake, approval, and prioritization process to deliver the same result in a more streamlined way. The next several slides will take you through the activities to ultimately create an OCM message canvas and a communication plan for your key stakeholders.
Download Info-Tech’s Intake and Prioritization Impact Analysis Tool.
"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
In Tab 2, enter your stakeholders’ names. Represent stakeholders as a group if you expect the impact of change on them to be reasonably uniform, as well as their anticipated responses. Otherwise, consider adding them as individuals or subgroups.
In Tab 3, enter whether you agree or disagree with each statement that represents an element of organizational change that be introduced as the newly optimized intake process is implemented.
As a result of the change initiative in question:
Each change statement that you agreed with in Tab 3 are listed here in Tab 4 of the Intake and Prioritization Impact Analysis Tool. For each stakeholder, estimate and enter the following data:
Divide and conquer. Leverage the group to get through the seemingly daunting amount of work involved with impact analysis.
Suggested ways to divide up the impact analysis include:
Tip: use a spreadsheet tool that supports multi-user editing (e.g. Google Sheets, Excel Online).
INPUT
OUTPUT
Materials
Participants
Beware of bias. Groups are just as susceptible to producing overly optimistic or pessimistic analysis as individuals, just in different ways. Unrealistic change impact analysis will compromise your chances of arriving at a reasonable, tactful stakeholder communication plan.
These outputs are based on the impacts you analyzed in Tab 4 of the tool (Activity 3.2.1). They are organized in seven sections:
Use Info-Tech’s Message Canvas on this tab to help rationalize and elaborate the change vision for each group.
Elements of a Message Canvas
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.
Remember these guidelines to help your messages resonate:
– Info-Tech Blueprint, Drive Organizational Change from the PMO
INPUT
OUTPUT
Materials
Participants
The communication plan creates an action plan around the message canvases to coordinate the responsibilities of delivering them, so the risks of “dropping the ball” on your stakeholders are minimized.
1. Choose a change impact from a drop-down menu.
2. Choose an intended audience...
… and the message canvas to reference.
3. Choose the method of delivery. It will influence how to craft the message for the stakeholder.
4. Indicate who is responsible for creating and communicating the message.
5. Briefly indicate goal of the communication and the likelihood of success.
6. Record the dates to plan and track the communications that take place.
Identify critical points in the change curve:
Based on Don Kelley and Daryl Conner’s Emotional Cycle of Change.
INPUT
OUTPUT
Materials
Participants
There will be challenges to watch for in evaluating the effectiveness of your intake processes. These may include circumvention of process by key stakeholders, re-emergence of off-the-grid projects and low-value initiatives.
As a quick and easy way to periodically assess your processes, consider the following questions:
If you answer “no” to any of these questions after a sufficient post-implementation period (approximately six to nine months, depending on the scope of your optimizing), you may need to tweak certain aspects of your processes or seek to align your optimization with a lower capability level in the short term.
Industry: Government
Source: Info-Tech Client
Challenge
There is an IT department for a large municipal government. Possessing a relatively low level of PPM maturity, IT is in the process of establishing more formal intake practices in order to better track, and respond to, project requests. New processes include a minimalist request form (sent via email) coupled with more thorough follow-up from BAs and PMs to determine business value, ROI, and timeframes.
Solution
Even with new user-friendly processes in place, IT struggles to get stakeholders to adopt, especially with smaller initiatives. These smaller requests frequently continue to come in outside of the formal process and, because of this, are often executed outside of portfolio oversight. Without good, reliable data around where staff time is spent, IT lacks the authority to decline new requests.
Results
IT is seeking further optimization through better communication. They are enforcing discipline on stakeholders and reiterating that all initiatives, regardless of size, need to be directed through the process. IT is also training its staff to be more critical. “Don’t just start working on an initiative because a stakeholder asks.” With staff being more critical and directing requests through the proper queues, IT is getting better at tracking and prioritizing requests.
"The biggest challenge when implementing the intake process was change management. We needed to shift our focus from responding to requests to strategically thinking about how requests should be managed. The intake process allows the IT Department to be transparent to customers and enables decision makers."
3.1.1
Select receptive stakeholders to work with during your pilot
Identify the right team of supportive PPM stakeholders to carry out the process pilot. Strategies to recruit the right people outside the workshop will be discussed if appropriate.
3.2.1
Analyze the stakeholder impact and responses to impending organizational change
Carry out a thorough analysis of change impact in order to maximize the effectiveness of the communication strategy in support of the implementation of the optimized process.
Kiron D. Bondale, PMP, PMI - RMP
Senior Project Portfolio & Change Management Professional
Scot Ganshert, Portfolio Group Manager
Larimer County, CO
Garrett McDaniel, Business Analyst II – Information Technology
City of Boulder, CO
Joanne Pandya, IT Project Manager
New York Property Insurance Underwriters
Jim Tom, CIO
Public Health Ontario
Develop a Project Portfolio Management Strategy blueprint"
Balance Supply and Demand with Realistic Resource Management Practices
Maintain an Organized Portfolio
Establish the Benefits Realization Process
Tailor Project Management Processes to Fit Your Projects
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 to understand where you stand and how you can improve.
Boston Consulting Group. “Executive Sponsor Engagement: Top Driver of Project and Program Success.” PMI, 2014. Web.
Boston Consulting Group. “Winning Through Project Portfolio Management: the Practitioners’ Perspective.” PMI, 2015. Web.
Bradberry, Travis. “Why The 8-Hour workday Doesn’t Work.” Forbes, 7 Jun 2016. Web.
Cook, Scott. Playbook: Best Practices. Business Week
Cooper, Robert, G. “Effective Gating: Make product innovation more productive by using gates with teeth.” Stage-Gate International and Product Development Institute. March/April 2009. Web.
Epstein, Dan. “Project Initiation Process: Part Two.” PM World Journal. Vol. IV, Issue III. March 2015. Web.
Evans, Lisa. “The Exact Amount of Time You Should Work Every Day.” Fast Company, 15 Sep. 2014. Web.
Madison, Daniel. “The Five Implementation Options to Manage the Risk in a New Process.” BPMInstitute.org. n.d. Web.
Merkhofer, Lee. “Improve the Prioritization Process.” Priority Systems, n.d. Web.
Miller, David, and Mike Oliver. “Engaging Stakeholder for Project Success.” PMI, 2015. Web.
Mind Tools. “Kelley and Conner’s Emotional Cycle of Change.” Mind Tools, n.d. Web.
Mochal, Jeffrey and Thomas Mochal. Lessons in Project Management. Appress: September 2011. Page 6.
Newcomer, Eric. “Getting Decisions to Stick.” Standish Group PM2go, 20 Oct 2017. Web.
“PMI Today.” Newtown Square, PA: PMI, Oct 2017. Web.
Project Management Institute. “Standard for Portfolio Management, 3rd ed.” Newtown Square, PA: PMI, 2013.
Project Management Institute. “Pulse of the Profession 2017: Success Rates Rise.” PMI, 2017. Web.
Transparent Choice. “Criteria for Project Prioritization.” n.p., n.d. Web.
University of New Hampshire (UNH) Project Management Office. “University of New Hampshire IT Intake and Selection Process Map.” UNH, n.d. Web.
Ward, John. “Delivering Value from Information Systems and Technology Investments: Learning from Success.” Information Systems Research Centre. August 2006. Web.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Evaluate what software maintenance you are spending money.
Establish your software M&S requirements and coverage.
Optimize your M&S spend, reduce or eliminate, where applicable.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Identify the KPIs that matter to your organization’s goals.
Use the IT Management Dashboard on the Info-Tech website to display your chosen KPIs.
Use the review of your KPIs to build an action plan to drive performance.
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.
Determine the KPIs that matter to your organization.
Identify organizational goals
Identify IT goals and their organizational goal alignment
Identify business pain points
1.1 Identify organizational goals.
1.2 Identify IT goals and organizational alignment.
1.3 Identify business pain points.
List of goals and pain points to create KPIs for
Learn how to configure and use the IT Management Dashboard.
Configured IT dashboard
Initial IT scorecard report
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.
Definition of KPIs to be used, data sources, and ownership
Configured IT dashboard
Learn how to review and plan actions based on the KPIs.
Lead KPI review to actions to improve performance
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.
Initial IT scorecard report
Action plan with initial actions
Use your KPIs to drive performance.
Improve your metrics program to drive effectiveness
4.1 Develop your action plan.
4.2 Execute the plan and tracking progress.
4.3 Develop new KPIs as your practice matures.
Understanding of how to develop new KPIs using the IT Metrics Library
Ensure all documentation and plans are complete.
Documented next steps
5.1 Complete IT Metrics Library documentation.
5.2 Document decisions and next steps.
IT Metrics Library
Action plan
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
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.
Build your dashboard quickly using the toolset in this research and move to improvement actions as soon as possible.

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)
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.
35% - Only 35% of governing bodies review data at each meeting. (Committee of University Chairs, 2008)
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.
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.
| 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.

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.

| 1. Choose the KPIs | 2. Build the Dashboard | 3. Create the Action Plan | |
|---|---|---|---|
| Phase Steps |
|
|
|
| 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 |
Don’t just measure things because you can. Change what you measure as your organization becomes more mature.
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.
Ease of use will determine the success of your metrics program, so keep it simple to create and review the indicators.
If indicators are showing suboptimal performance, develop an action plan to drive the indicator in the right direction.
Act early and often.
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.
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.
Customize the KPIs for your organization using the IT Metrics Library
Keep track of the actions that are generated from your KPI review
The IT Overall Scorecard gives a holistic view of the performance of each IT function
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.

Industry: Government Services
Source: Info-Tech analyst experience
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.
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.
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.
"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."
Call #1: Scope dashboard and reporting needs.
Call #2: Learn how to use the IT Metrics Library to select your metrics.
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.
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
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:
1.1.1 Download the IT Metrics Library and review the KPIs for each practice area.
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:
Downloaded tool ready to select the KPIs for your organization
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.

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.2.1 Select the KPIs that will drive your organization forward
1.2.2 Remove unwanted KPIs from the IT Metrics Library
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:
This step involves the following participants:
A shortlist of selected KPIs
1.3.1 Document the data source
1.3.2 Document the owner
1.3.3 Document baseline and target
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:
A list of KPIs for your organization with appropriate attributes documented
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:
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
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:
Understanding of how to administer the IT Management Dashboard

2.2.1 Entering the KPI descriptions
2.2.2 Entering the KPI actuals
2.2.3 Producing the IT Overall Scorecard
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:
An overall scorecard indicating the selected KPI performance
Example of a custom metric

Example of a standard metric


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:
3.1.1 Determine criteria for prioritization
3.1.2 Identify low-performing indicators
3.1.3 Prioritize low-performing indicators
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:
A prioritized list of low-performing indicators that need remediation
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.2.1 Review suggested actions in the IT Metrics Library
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:
An idea of possible suggested actions
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
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:
An action plan to invoke improved performance
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.
Info-Tech Insight
Assigning clear ownership can promote accountability for progress.
Info-Tech Insight
If the target completion date is too far in the future, break the task into manageable chunks.
Info-Tech Insight
Seek to understand the reasons that tasks are not being completed and problem solve for creative solutions to improve 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.

| 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 |
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
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.
Principal Research Director, CIO – Service Management Info-Tech Research Group
Practice Lead, CIO – People & Leadership Info-Tech Research Group
Practice Lead, Infrastructure & Operations Info-Tech Research Group
Practice Lead, Security, Risk & Compliance Info-Tech Research Group
Practice Lead, Applications and Agile Development Info-Tech Research Group
Practice Lead, Applications – Project and Portfolio Mgmt. Info-Tech Research Group
Vice President, Applications Info-Tech Research Group
Research Director, CIO Info-Tech Research Group
Practice Lead, Enterprise Applications Info-Tech Research Group
Practice Lead, Enterprise Architecture, Data & BI Info-Tech Research Group
Executive Counselor Info-Tech Research Group
Develop Meaningful Service Metrics to Ensure Business and User Satisfaction
Use Applications Metrics That Matter
Take Control of Infrastructure Metrics
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.
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.
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.
This research will help you:
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
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.
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.
“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. |
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:
|
Good Luck.
![]() |
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. |
Darin Stahl |
Thinking of modernizing your mainframe can cause you angst so grab a fidget spinner and relax because we have you covered!
External Business Pressures:
Internal Considerations:
With multiple control points to be addressed, care must be taken to simplify your options while addressing all concerns to ease operational load.
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. |
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*:
|
Below is a summary of concerns regarding core mainframe skills:
|
The Challenge An aging workforce, specialized skills, and high salary expectations
The In-House Solution: Build your mentorship program to create a viable succession plan
|
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 |
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. |
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.
|
*3 of the top 4 challenges related to shortfalls of alternative platforms
|
*Source: Maximize the Value of IBM Mainframes in My Business |
Potential for reduced costs
Reliable infrastructure and experienced staff
So, what are the risks?
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. |
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
Azure Cloud
Micro Focus COBOL (Visual 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)
ModernSystems (or ModSys) has relevant experience.
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: |
*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) |
![]() |
![]() |
| 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. |
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.
|
|
✓ Advanced Systems Concepts ✓ BMC ✓ Broadcom ✓ HCL ✓ Fortra |
✓ Redwood ✓ SMA Technologies ✓ StoneBranch ✓ Tidal Software ✓ Vinzant Software |
Creating vendor profiles will help quickly filter the solution providers that directly meet your z/Series needs.
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 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.
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
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 |
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 |
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 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 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 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 |
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) |
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 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 |
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 |
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 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 |
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 Coverage: Global | Windows Linux Unix iSeries SAP R/3 & SAP S/4HANA Oracle, SQL/Server |
Activities:
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:
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.
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:
| ![]() |
Info-Tech InsightWatch 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. |
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.
Make the most of cloud for your organization.
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.
Improve your RFPs to gain leverage and get better results.
![]() |
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, 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. |
“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.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Understand blockchain’s unique feature, benefits, and business use cases.
Envision blockchain’s transformative potential for your organization by brainstorming and validating a use case.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Use this research to identify and quantify the potential financial impacts of vendors’ poor performance. Use Info-Tech’s approach to look at the financial impact from various perspectives to better prepare for issues that may arise.
By playing the “what if” game and asking probing questions to draw out – or eliminate – possible negative outcomes, everyone involved adds their insight into parts of the organization to gather a comprehensive picture of potential impacts.

Vendors are becoming more influential and essential to the operation of organizations. Often the sole risk consideration of a business is whether the vendor meets a security standard, but vendors can negatively impact organizations’ budgets in various ways. Fortunately, though inherent risk is always present, organizations can offset the financial impacts of high-risk vendors by employing due diligence in their vendor management practices to help manage the overall risks.
Frank Sewell
Research Director, Vendor Management
Info-Tech Research Group
| Your Challenge
As vendors become more prevalent in organizations, organizations increasingly need to understand and manage the potential financial impacts of vendors’ actions. It is only a matter of time until a vendor mistake impacts your organization. Make sure you are prepared to manage the adverse financial consequences. |
Common Obstacles
Identifying and managing a vendor’s potential financial impact requires multiple people in the organization across several functions – and those people all need educating on the potential risks. Organizational leadership is often unaware of decisions on organizational risk appetite and tolerance, and they assume there are more protections in place against risk impact than there truly are. |
Info-Tech’s Approach
Vendor management practices educate organizations on the different potential financial impacts that vendors may incur and suggest systems to help manage them. Prioritize and classify your vendors with quantifiable, standardized rankings. Prioritize focus on your high-risk vendors. Standardize your processes for identifying and monitoring vendor risks to manage financial impacts with our Financial Risk Impact Tool. |
Companies without good vendor management risk initiatives will take on more risk than they should. Solid vendor management practices are imperative –organizations must evolve to ensure that vendors deliver services according to performance objectives and that risks are managed accordingly.

This series will focus on the individual components of vendor risk and how vendor management practices can facilitate organizations’ understanding of those risks.
Out of scope:
This series will not tackle risk governance, determining overall risk tolerance and appetite, or quantifying inherent risk.
In this blueprint, we’ll explore financial risks and their impacts.
Identifying negative actions is paramount to assessing the overall financial impact on your organization, starting in the due diligence phase of the vendor assessment and continuing throughout the vendor lifecycle.

Loss of business represents the largest share of the breach
38%Avg. $1.59M |
Global average cost of a vendor breach
$4.2M |
Percentage of breaches in 2020 caused by business associates
40.2%23.2% YoY(year over year) |
| (Source: “Cost of a Data Breach Report 2021,” IBM, 2021) | (Source: “Vendor Risk Management – A Growing Concern,” Stern Security, 2021) | |
Hospitals often rely on vendors to manage their data center environments but rarely understand the downstream financial impacts if that vendor fails to perform.
For example, a vendor implements a patch out of cycle with no notice to the IT group. Suddenly all IT systems are down. It takes 12 hours for the IT teams to return systems to normal. The downstream impacts are substantial.
Assessing financial impacts is an ongoing, educative, and collaborative multidisciplinary process that vendor management initiatives are uniquely designed to coordinate and manage for organizations.
| Insight 1 | Vendors are becoming more and more crucial to organizations’ overall operations, and most organizations have a poor understanding of the potential impacts they represent.
Is your vendor solvent? Do they have enough staff to accommodate your needs? Has their long-term planning been affected by changes in the market? Are they unique in their space? |
| Insight 2 | Financial impacts from other risk types deserve just as much focus as security alone, if not more.
Examples include penalties and fines, loss of revenue due to operational impacts, vendor replacement costs, hidden costs in poorly understood contracts, and lack of contractual protections. |
| Insight 3 | There is always an inherent risk in working with a vendor, but organizations should financially quantify how much each risk may impact their budget.
A significant concern for organizations is quantifying different types of risks. When a risk occurs, the financial losses are often poorly understood, with unbudgeted financial impacts. |
Inherent risks from negative actions are pervasive throughout the entire vendor lifecycle. Collaboratively understanding those risks and working together to put proper management in place enables organizations to get the most value out of the relationship with the least amount of risk.

|
Visit Info-Tech’s VMO ROI Calculator and Tracker |
Input: List of identified potential risk scenarios scored by likelihood and financial impact, List of potential management of the scenarios to reduce the risk
Output: Comprehensive financial risk profile on the specific vendor solution
Materials: Whiteboard/flip charts, Financial Risk Impact Tool to help drive discussion
Participants: Vendor Management – Coordinator, IT Operations, Legal/Compliance/Risk Manager, Finance/Procurement
Vendor management professionals are in an excellent position to collaboratively pull together resources across the organization to determine potential risks. By playing the “what if” game and asking probing questions to draw out – or eliminate – possible negative outcomes, everyone involved adds their insight into parts of the organization to gather a comprehensive picture of potential impacts.
Download the Financial Risk Impact Tool
Never underestimate the value of keeping the relationship moving forward.Examples of items and activities to monitor include; | ![]() | |
|
| |
Info-Tech InsightMany organizations do not have the resources to dedicate to annual risk assessments of all vendors. Consider timing ongoing risk assessments to align with contract renewal, when you have the most leverage with the vendor. | Visit Info-Tech’s Risk Register Tool | |
|
![]() |
|
![]() |
![]() |
Design and Build an Effective Contract Lifecycle Management Process
|
![]() |
Identify and Reduce Agile Contract Risk
|
![]() |
Jump Start Your Vendor Management Initiative
|
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Read our concise Executive Brief to find out how you can reduce your IT cost in the short term while establishing a foundation for long-term sustainment of IT cost containment.
In early April, I already wrote about exit plans and how they are the latest burning platform.
As of the end of May 2025, we have both Microsoft and Google reassuring European clients about their sovereign cloud solutions. There are even air-gapped options for military applications. These messages come as a result of the trade war between the US and the rest of the world.
There is also the other, more mundane example of over-reliance on a single vendor: the Bloomberg-terminal outage of May 21st, 2025. That global outage severely disrupted financial markets. It caused traders to lose access to real-time data, analytics, and pricing information for approximately 90 minutes. This widespread system failure delayed critical government bond auctions in the UK, Portugal, Sweden, and the EU.
It serves as a reminder of the heavy reliance on the Bloomberg Terminal, which is considered an industry standard despite its high annual cost. While some Bloomberg services like instant messaging remained functional, allowing limited communication among traders, the core disruption led to significant frustration and slowed down trading activities.
You want to think about this for a moment. Bloomberg is, just like Google and Microsoft are, cornerstones in their respective industries. MS, Google, and Amazon even in many more industries.
So the issue goes beyond the “panic of the day.” Every day, there will be some announcement that sends markets reeling and companies fearing. Granted, the period we go through today can have grave consequences, but at the same time, it may be over in the coming months or years.
Let's take a step back and see if we can locate the larger issue at stake. I dare to say that the underlying issue is trust. We are losing trust in one another at a fast pace. Not between business partners, meaning companies who are, in a transaction or relationship, are more or less equal. Regardless of their geolocation, people are keen to do business together in a predictable, mutually beneficial way. And as long as that situation is stable, there is little need, beyond compliance and normal sound practices, to start to distrust each other.
Trouble brews when other factors come into play. I want to focus on two of them in this article.
The past few years have seen a large increase in power of the cloud computing platforms. The pandemic of 2019 through to 2023 changed our way of working and gave a big boost to these platforms. Of course, they were already establishing their dominance in the early 2010s.
Amazon launched SQS in 2004 with S3 (storage) and EC2 (compute) in 2006. Azure launched in 2008 as a PaaS platform for .NET developers, and became really available in 2010. Since then, it grew into the IaaS (infrastructure as a service) platform we know today. Google's Cloud Platform (GCP) launched in 2008 and added components such as BigQuery, Compute Engine and Storage in the 2010s.
Since the pandemic, we've seen another boost to their popularity. These platforms solidified their lead through several vectors:
Companies made decisions on these premises. A prime example is the use of native cloud functions. These make life easier for developers. Native functions allow for serverless functionality to be made available to clients, and to do so in a non-infra-based way. It gives the impression of less complexity to the management. They are also easily scalable.
This comes at a cost, however. The cost is vendor lock-in. And with vendor lock-in, comes increased pricing power for the vendor.
For a long time, it seems EU companies' attitude was: “It won't be such an issue, after all, there are multiple cloud vendors and if all else fails, we just go back.” The reality is much starker, I suspect that cloud providers with this level of market power will increase their pricing significantly.
in come two elements:
The latest push to their market power came as an unintended consequence of EU Law: DORA. That EU law requires companies to have testable exit plans in place. But it goes well beyond this. The EU has increased the regulatory burden on companies significantly. BusinessEurope, a supranational organization, estimates that in the past five years, the Eu managed to release over 13,000 legislative acts. This is compared to 3,500 in the US.
Coming back to DORA, this law requires EU companies to actually test their exit plans and show proof of it to the EU ESAs (European Supervisory Agency). The reaction I have seen in industry representative organizations is complacency.
The cost of compliance is significant; hence, companies try to limit their exposure to the law as much as possible. They typically do this by limiting the applicability scope of the law to their business, based on the wording of the law. And herein lies the trap. This is not lost on the IT providers. They see that companies do the heavy lifting for them. What do I mean by that? Several large providers are looked at by the EU as systemic providers. They fall under direct supervision by the ESAs.
For local EU providers, it is what it is, but for non-EU providers, they get to show their goodwill, using sovereign IT services. I will come back to this in the next point, US unpredictability and laws. But the main point is: we are giving them more market power, and we have less contractual power. Why? Because we are showing them that we will go to great lengths to keep using their services.
US companies must comply with US law. So far, so good. Current US legislation also already requires US companies to share data on non-US citizens.
This last one is of particular concern. Not so much because of its contents, but because it is an Executive Order.
We know that the current (May 2025) US government mostly works through executive orders. Let's not forget that executive orders are a legitimate way to implement policy, This means that the US government could use access to cloud services as a lever to obtain more favorable trade rules.
The EU responds to this (the laws and executive order) by implementing several sovereignty countermeasures like GDPR, DORA, Digital markets Act (DMA), Data Governance Act (DGA), Cybersecurity Act and the upcoming European Health Data Act (EHDS). This is called the “Brussels Effect.”
Europe is also investing in several strategic initiatives such as
This points to a new dynamic between the EU and the US, EU-based companies simply cannot trust their US counterparts anymore to the degree they could before. The sad thing is, that there is no difference on the interpersonal level. It is just that companies must comply with their respective laws.
Hence, Microsoft, Google, and AWS and any other US provider cannot legally provide sovereign cloud services. In a strict legal sense, Microsoft and Google cannot absolutely guarantee that they can completely insulate EU companies and citizens from all US law enforcement requests for data, despite their robust efforts and sovereign cloud offerings. This is because they are US companies, subject to US law and US jurisdiction. The CLOUD act and FISA section 702 compel US companies to comply.
Moreover, there is the nature of sovereign cloud offerings:
And lastly, there are the legal challenges to the EU data privacy Framework (DPF)
This all means that while the cloud providers are doing everything they can, and I'm assuming they are acting in good faith. The fact that they are US entities means however that they are subject to all US legislation and executive orders. And we cannot trust this last part. Again, this is why the EU is pursuing its digital sovereignty initiatives and why some highly sensitive EU public sector entities are gravitating towards truly EU-owned and operated cloud solutions.
If your provider goes bankrupt, you do not have a leg to stand on. Most jurisdictions, including the EU and US, have the following elements regarding bankruptcy:
Automatic Stay: Upon a bankruptcy filing (in most jurisdictions, including the US and EU), an “automatic stay” is immediately imposed. This is a court order that stops most collection activities against the debtor. For you as a customer, this can mean you might be prevented from:
Debtor's Estate and Creditor Priority
So, while I understand the wait and see stance in regard to exit plans, given where we are, it is in my opinion the wrong thing to do. Companies must make actionable exit plans and prepare beforehand for the exit. That means that you have to:
If you want more detailed steps on how to get there, feel free to contact me.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Determining SAP’s fit within your organization is critical. Start off by building a business case to assess overarching drivers and justification for change, any net new business benefits and long-term sustainability. Oftentimes the ROI is negative, but the investment sets the stage for long-term growth.
Your deployment model is more important than you think. Selecting a deployment model will dictate your licensing options followed by your contractual pathways forward.
Know what’s in the contract. Each customer agreement is different and there may be existing terms that are beneficial. Depending on how much is spent, anything can be up for negation.
Take the time to understand the various data storage formats, disk types, and associated technology, as well as the cloud-based and on-premises options. This will help you select the right tool for your needs.
Look to existing use cases based on actual Info-Tech analyst calls to help in your decision-making process.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Explore the building blocks of enterprise storage so you can select the best solution, narrow your focus with the correct product type, explore the features that should be considered when evaluating enterprise storage offerings, and examine use cases based on actual Info-Tech analyst calls to find a storage solution for your situation.
The first step in solving your enterprise storage challenge is identifying your data sources, data volumes, and growth rates. This information will give you insight into what data sources could be stored on premises or in the cloud, how much storage you will require for the coming five to ten years, and what to consider when exploring enterprise storage solutions. This tool can be a valuable asset for determining your current storage drivers and future storage needs, structuring a plan for future storage purchases, and determining timelines and total cost of ownership.
|
To say that the current enterprise storage landscape looks interesting would be an understatement. The solutions offered by vendors continue to grow and evolve. Flash and NVMe are increasing the speed of storage media and reducing latency. Software-defined storage is finding the most efficient use of media to store data where it is best served while managing a variety of vendor storage and older storage area networks and network-attached storage devices. Storage as a service is taking on a new meaning with creative solutions that let you keep the storage appliance on premises or in a colocated data center while administration, management, and support are performed by the vendor for a nominal monthly fee. We cannot discuss enterprise storage without mentioning the cloud. Bring a thermometer because you must understand the difference between hot, warm, and cold storage when discussing the cloud options. Very hot and very cold may also come into play. Storage hardware can assume a higher total cost of ownership with support options that replace the controllers on a regular basis. The options with this type of service are also varied, but the concept of not having to replace all disks and chassis nor go through a data migration is very appealing to many companies. The cloud is growing in popularity when it comes to enterprise storage, but on-premises solutions are still in demand, and whether you choose cloud or on premises, you can be guaranteed an array of features and options to add stability, security, and efficiency to your enterprise storage. P.J. Ryan |
|
The vendor landscape is continually evolving, as are the solutions they offer. |
Storage providers are getting acquired by bigger players, “outside the box” thinking is disrupting the storage support marketplace, “as a service” storage offerings are evolving, and what is a data lake and do I need one? The traditional storage vendors are not alone in the market, and the solutions they offer are no longer traditional either. Explore the landscape and understand your options before you make any enterprise storage solution purchases. |
|---|---|
|
Understand the building blocks of storage so you can select the best solution. |
There are multiple storage formats for data, along with multiple hardware form factors and disk types to hold those various data formats. Software plays a significant role in many of these storage solutions, and cloud offerings take advantage of all the various formats, form factors, and disks. The challenge is matching your data type with the correct storage format and solution. |
|
Look to existing use cases to help in your decision-making process. |
Explore previous experiences from others by reading use cases to determine what the best solution is for your challenge. You’re probably not the first to encounter the challenge you’re facing. Another organization may have previously reached out for assistance and found a viable solution that may be just what you also need. |
“By 2025, it’s estimated that 463 exabytes of data will be created each day globally – that’s the equivalent of 212,765,957 DVDs per day!” (Visual Capitalist)
“Modern criminal groups target not only endpoints and servers, but also central storage systems and their backup infrastructure.” (Continuity Software)
Cloud or on premises? Maybe a hybrid approach with both cloud and on premises is best for you. Do you want to remove the headaches of storage administration, management, and support with a fully managed storage-as-a-service solution? Would you like to upgrade your controllers every three or four years without a major service interruption? The options are increasing and appealing.
1. Understand Your Data
Understand how much data you have and where it is located. This will be crucial when evaluating enterprise storage solutions.
2. Plan for Growth
Your enterprise storage considerations should include your data needs now and in the future.
3. Understand the Mechanics
Take the time to understand the various data storage formats, disk types, and associated technology, as well as the cloud-based and on-premises options. This will help you select the right tool for your needs.
|
Format |
What it is |
Disk Drives and Technology |
|
|---|---|---|---|
|
File Storage |
File storage is hierarchical storage that uses files, folders, subfolders, and directories. You enter a specific filename and path to access the file, such as P:\users\johndoe\strategy\cloud.doc. If you ever saved a file on a server, you used file storage. File storage is usually managed by some type of file manager, such as File Explorer in Windows. Network-attached storage (NAS) devices use file storage. |
Hard Disk Drives (HDD) |
HDD use a platter of spinning disks to magnetically store data. The disks are thick enough to make them rigid and are referred to as hard disks. HDD is older technology but is still in demand and offered by vendors. |
|
Object Storage |
Object storage is when data is broken into distinct units, called objects. These objects are stored in a flat, non-hierarchical structure in a single location or repository. Each object is identified by its associated ID and metadata. Objects are accessed by an application programming interface (API). |
Flash |
Flash storage uses flash memory chips to store data. The flash memory chips are written with electricity and contain no moving parts. Flash storage is very fast, which is how the technology got its name (“Flash vs. SSD Storage,” Enterprise Storage Forum, 2018). |
|
Block Storage |
Block storage is when data is divided up into fixed-size blocks and stored with a unique identifier. Blocks can be stored in different environments, such as Windows or Linux. Storage area networks (SANs) use block storage. |
Solid-State Drive (SSD) |
SSD is a storage mechanism that also does not use any moving parts. Most SSD drives use flash storage, but other options are available for SSD. |
|
Nonvolatile Memory Express (NVMe) |
NVMe is a communications standard developed specially for SSDs by a consortium of vendors including Intel, Samsung, SanDisk, Dell, and Seagate. It operates across the PCIe bus (hence the “Express” in the name), which allows the drives to act more like the fast memory that they are rather than the hard disks they imitate (PCWorld). |
|
Network-Attached Storage |
Storage Area Network |
Software-Defined Storage |
Hyperconverged Infrastructure |
|---|---|---|---|
|
NAS refers to a storage device that is connected directly to your network. Any user or device with access to your network can access the available storage provided by the NAS. NAS storage is easily scalable and can add data redundancy through RAID technology. NAS uses the file storage format. NAS storage may or may not be the first choice in terms of enterprise storage, but it does have a solid market appeal as an on-premises primary backup storage solution. |
A SAN is a dedicated network of pooled storage devices. The dedicated network, separate from the regular network, provides high speed and scalability without concern for the regular network traffic. SANs use block storage format and can be divided into logical units that can be shared between servers or segregated from other servers. SANs can be accessed by multiple servers and systems at the same time. SANs are scalable and offer high availability and redundancy through RAID technology. SANs can use a variety of disk types and sizes and are quite common among on-premises storage solutions. |
“Software-defined storage (SDS) is a storage architecture that separates storage software from its hardware. Unlike traditional network-attached storage (NAS) or storage area network (SAN) systems, SDS is generally designed to perform on any industry-standard or x86 system, removing the software’s dependence on proprietary hardware.” (RedHat) SDS uses software-based policies and rules to grow and protect storage attached to applications. SDS allows you to use server-based storage products to add management, protection, and better usage. |
Hyperconverged storage uses virtualization and software-defined storage to combine the storage, compute, and network resources along with a hypervisor into one appliance. Hyperconverged storage can scale out by adding more nodes or appliances, but scaling up, or adding more resources to each appliance, can have limitations. There is flexibility as hyperconverged storage can work with most network and compute manufacturers. |
“Enterprise cloud storage offers nearly unlimited scalability. Enterprises can add storage quickly and easily as it is needed, eliminating the risk and cost of over-provisioning.”
– Spectrum Enterprise
“Hot data will operate on fresh data. Cold data will operate on less frequent data and [is] used mainly for reporting and planning. Warm data is a balance between the two.”
– TechBlost
|
|
“Because data lakes mostly consist of raw unprocessed data, a data scientist with specialized expertise is typically needed to manipulate and translate the data.”
– DevIQ
“A Lakehouse is also a type of centralized data repository, integrated from heterogeneous sources. As can be expected from its name, It shares features with both datawarehouses and data lakes.”
– Cesare
“Storage as a service (STaaS) eliminates Capex, simplifies management and offers extensive flexibility.”
– TechTarget
The current vendor landscape for enterprise storage solutions represents a range of industry veterans and the brands they’ve aggregated along the way, as well as some relative newcomers who have come to the forefront within the past ten years.
Vendors like Dell EMC and HPE are longstanding veterans of storage appliances with established offerings and a back catalogue of acquisitions fueling their growth. Others such as Pure Storage offer creative solutions like all-flash arrays, which are becoming more and more appealing as flash storage becomes more commoditized.
Cloud-based vendors have become popular options in recent years. Cloud storage provides many options and has attracted many other vendors to provide a cloud option in addition to their on-premises solutions. Some software and hardware vendors also partner with cloud vendors to offer a complete solution that includes storage.
Explore your current vendor’s solutions as a starting point, then use that understanding as a reference point to dive into other players in the market
Key Players
Block, object, or file storage? NAS, SAN, SDS, or HCI? Cloud or on prem? Hot, warm, or cold?
Which one do you choose?
The following use cases based on actual Info-Tech analyst calls may help you decide.
“Offsite” may make you think of geographical separation or even cloud-based storage, but what is the best option and why?
“Data retrieval from cold storage is harder and slower than it is from hot storage. … Because of the longer retrieval time, online cold storage plans are often much cheaper. … The downside is that you’d incur additional costs when retrieving the data.”
– Ben Stockton, Cloudwards
Hyperconverged infrastructure combines storage, virtual infrastructure, and associated management into one piece of equipment.
“HCI environments use a hypervisor, usually running on a server that uses direct-attached storage (DAS), to create a data center pool of systems and resources.”
– Samuel Greengard, Datamation
SAN providers offer a varied range of options for their products, and those options are constantly evolving.
“SAN-to-SAN replication is a low-cost, highly efficient way to manage mounting quantities of stored data.”
– Secure Infrastructure & Services
That old storage area network may still have some useful life left in it.
“Often enterprises have added storage on an ad hoc basis as they needed it for various applications. That can result in a mishmash of heterogenous storage hardware from a wide variety of vendors. SDS offers the ability to unify management of these different storage devices, allowing IT to be more efficient.”
– Cynthia Harvey, Enterprise Storage Forum (“What Is Software Defined Storage?”, 2018)
Many backup software solutions can provide backups to multiple locations, making two-location backups simple.
“Data protection demands that enterprises have multiple methods of keeping data safe and replicating it in case of disaster or loss.”
– Drew Robb, Enterprise Storage Forum, 2021
SAN solutions have come a long way with improvements in how data is stored and what is used to store the data.
“A rapidly growing portion of SAN deployments leverages all-flash storage to gain its high performance, consistent low latency, and lower total cost when compared to spinning disk.”
– NetApp
Cloud storage would not be sufficient if you were using a dial up connection, just as on-premises storage solutions would not suffice if they were using floppy disks.
“The captured video is stored for days, weeks, months and sometimes years and consumes a lot of space. Data storage plays a new and important role in these systems. Object storage is ideal to store the video data.”
– Object-Storage.Info
Some software products have storage options available as a result of agreements with other storage vendors. Several backup and archive software products fall into this category.
“Cold storage is perfect for archiving your data. Online backup providers offer low-cost, off-site data backups at the expense of fast speeds and easy access, even though data retrieval often comes at an added cost. If you need to keep your data long-term, but don’t need to access it often, this is the kind of storage you need.”
– Ben Stockton, Cloudwards
Activity
The first step in solving your enterprise storage challenge is identifying your data sources or drivers, data volume size, and growth rates. This information will give you insight into what data sources could be stored on premises or in the cloud, how much storage you will require for the coming five to ten years, and what to consider when exploring enterprise storage solutions.
Download the Modernize Enterprise Storage Workbook and take the first step toward understanding your data requirements.
Download the Modernize Enterprise Storage Workbook
Current and emerging storage technologies are disrupting the status quo – prepare your infrastructure for the exponential rise in data and its storage requirements.
Modernize Enterprise Storage Workbook
This workbook will complement the discussions and activities found in the Modernize Enterprise Storage blueprint. Use this workbook in conjunction with the blueprint to develop a strategy for storage modernization.
Bakkianathan, Raghunathan. “What is the difference between Hot Warm and Cold data storage?” TechBlost, n.d.. Accessed 14 July 2022.
Cesare. “Data warehouse vs Data lake vs Lakehouse… and DeltaLake?“ Medium, 14 June 2021. Accessed 26 July 2022.
Davison, Shawn and Ryan Sappenfield. “Data Lake Vs Lakehouse Vs Data Mesh: The Evolution of Data Transformation.” DevIQ, May 2022. Accessed 23 July 2022.
Desjardins, Jeff. “Infographic: How Much Data is Generated Each Day?” Visual Capitalist, 15 April 2019. Accessed 26 July 2022.
Greengard, Samuel. “Top 10 Hyperconverged Infrastructure (HCI) Solutions.” Datamation, 22 December 2020. Accessed 23 July 2022.
Harvey, Cynthia. “Flash vs. SSD Storage: Is there a Difference?” Enterprise Storage Forum, 10 July 2018. Accessed 23 July 2022.
Harvey, Cynthia. “What Is Software Defined Storage? Features & Benefits.” Enterprise Storage Forum, 22 February 2018. Accessed 23 July 2022.
Hecht, Gil. “4 Predictions for storage and backup security in 2022.” Continuity Software, 09 January 2022. Accessed 22 July 2022.
Jacobi, Jonl. “NVMe SSDs: Everything you need to know about this insanely fast storage.” PCWorld, 10 March 2019. Accessed 22 July 2022
Pritchard, Stephen. “Briefing: Cloud storage performance metrics.” Computer Weekly, 16 July 2021. Accessed 23 July 2022
Robb, Drew. “Best Enterprise Backup Software & Solutions 2022.” Enterprise Storage Forum, 09 April 2021. Accessed 23 July 2022.
Sheldon, Robert. “On-premises STaaS shifts storage buying to Opex model.” TechTarget, 10 August 2020. Accessed 22 July 2022.
“Simplify Your Storage Ownership, Forever.” PureStorage. Accessed 20 July 2022.
Stockton, Ben. “Hot Storage vs Cold Storage in 2022: Instant Access vs Long-Term Archives.” Cloudwards, 29 September 2021. Accessed 22 July 2022.
“The Cost Savings of SAN-to-SAN Replication.” Secure Infrastructure and Services, 31 March 2016. Accessed 16 July 2022.
“Video Surveillance.” Object-Storage.Info, 18 December 2019. Accessed 25 July 2022.
“What is a Data Lake?” Amazon Web Services, n.d. Accessed 17 July 2022.
“What is enterprise cloud storage?” Spectrum Enterprise, n.d. Accessed 28 July 2022.
“What is SAN (Storage Area Network).” NetApp, n.d. Accessed 25 July 2022.
“What is software-defined storage?” RedHat, 08 March 2018. Accessed 16 July 2022.
The new security leader must be strategic, striking a balance between being tactical and taking a proactive security stance. They must incorporate security into business practices from day one and enable secure adoption of new technologies and business practices.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Use this blueprint to hire or develop a world-class Chief Information Security Officer (CISO) with the competencies that suit your specific organizational needs. Once you have identified the right candidate, create a plan to develop your CISO.
This tool will help you determine which competencies are a priority for your organizational needs and which competencies your CISO needs to develop.
Use this template to identify stakeholders who are key to your security initiatives and to understand your relationships with them.
Create a strategy to cultivate your stakeholder relationships and manage each relationship in the most effective way.
This tool will help you create and implement a plan to remediate competency gaps.
The days are gone when the security leader can stay at a desk and watch the perimeter. The rapidly increasing sophistication of technology, and of attackers, has changed the landscape so that a successful information security program must be elastic, nimble, and tailored to the organization’s specific needs.
The Chief Information Security Officer (CISO) is tasked with leading this modern security program, and this individual must truly be a Chief Officer, with a finger on the pulses of the business and security processes at the same time. The modern, strategic CISO must be a master of all trades.
A world-class CISO is a business enabler who finds creative ways for the business to take on innovative processes that provide a competitive advantage and, most importantly, to do so securely.
Cameron Smith
Research Lead, Security & Privacy
Info-Tech Research Group
|
Your Challenge
|
Common Obstacles
|
Info-Tech’s Approach
|
Info-Tech Insight
The new security leader must be strategic, striking a balance between being tactical and taking a proactive security stance. They must incorporate security into business practices from day one and enable secure adoption of new technologies and business practices.
Around one in five organizations don’t have an individual with the sole responsibility for security1
1 Navisite
Info-Tech Insight
Assigning security responsibilities to departments other than security can lead to conflicts of interest.
Source: Navisite
Only 36% of small businesses have a CISO (or equivalent position).
48% of mid-sized businesses have a CISO.
90% of large organizations have a CISO.
Source: Navisite
| Strategic CISO | Tactical CISO |
|---|---|
|
Proactive Focus is on protecting hyperdistributed business processes and data Elastic, flexible, and nimble Engaged in business design decisions Speaks the language of the audience (e.g. business, financial, technical) |
Reactive Focus is on protecting current state Perimeter and IT-centric approach Communicates with technical jargon |
1 Journal of Computer Science and Information Technology
To determine what is required from tomorrow’s security leader, Info-Tech examined the core behaviors that make a world-class CISO. These are the three areas that a CISO engages with and excels in.
Later in this blueprint, we will review the competencies and skills that are required for your CISO to perform these behaviors at a high level.
Align
Aligning security enablement with business requirements
Enable
Enabling a culture of risk management
Manage
Managing talent and change
Info-Tech Insight
Through these three overarching behaviors, you can enable a security culture that is aligned to the business and make security elastic, flexible, and nimble to maintain the business processes.

| 1. Launch | 2. Assess | 3. Plan | 4. Execute | |
|---|---|---|---|---|
| Phase Steps |
|
|
|
|
| Phase Outcomes |
At the end of this phase, you will have:
|
At the end of this phase, you will have:
|
At the end of this phase, you will have:
|
At the end of this phase, you will have:
|
Each step of this blueprint is accompanied by supporting deliverables to help you accomplish your goals:
CISO Core Competency Evaluation Tool
Assess the competency levels of a current or prospective CISO and identify areas for improvement.
Stakeholder Power Map Template
Visualize the importance of various stakeholders and their concerns.
Stakeholder Management Strategy Template
Document a plan to manage stakeholders and track actions.
Key deliverable:
CISO Development Plan Template
The CISO Development Plan Template is used to map specific activities and time frames for competency development to address gaps and achieve your goal.
Career development should not be seen as an individual effort. By understanding the personal core competencies that Info-Tech has identified, the individual wins by developing relevant new skills and the organization wins because the CISO provides increased value.
| Organizational Benefits | Individual Benefits |
|---|---|
|
|
Organizations with a CISO saw an average of $145,000 less in data breach costs.1
However, we aren’t talking about hiring just any CISO. This blueprint seeks to develop your CISO’s competencies and reach a new level of effectiveness.
Organizations invest a median of around $375,000 annually in their CISO.2 The CISO would have to be only 4% more effective to represent $15,000 more value from this position. This would offset the cost of an Info-Tech workshop, and this conservative estimate pales in comparison to the tangible and intangible savings as shown below.
Your specific benefits will depend on many factors, but the value of protecting your reputation, adopting new and secure revenue opportunities, and preventing breaches cannot be overstated. There is a reason that investment in information security is on the rise: Organizations are realizing that the payoff is immense and the effort is worthwhile.
| Tangible cost savings from having a world-class CISO | Intangible cost savings from having a world-class CISO |
|---|---|
|
|
1 IBM Security
2 Heidrick & Struggles International, Inc.
SOURCE
Kyle Kennedy
CISO, CyberSN.com
|
Challenge The decision was made to move to a new vendor. There were multiple options, but the best option in the CISO’s opinion was a substantially more expensive service that provided more robust protection and more control features. The CISO faced the challenge of convincing the board to make a financial investment in his IT security initiative to implement this new software. |
Solution He identified that the business has $100 million in revenue that would move through this data stream. This new software would help to ensure the security of all these transactions, which they would lose in the event of a breach. Furthermore, the CISO identified new business plans in the planning stage that could be protected under this initiative. |
Results This approach is the opposite of the cautionary tales that make news headlines, where new revenue streams are created before systems are put in place to secure them. This proactive approach is the core of the world-class CISO. |
| Launch | Assess | Plan | Execute |
|---|---|---|---|
|
Call #1: Review and discuss CISO core competencies. Call #2: Discuss Security Business Satisfaction and Alignment diagnostic results. |
Call #3: Discuss the CISO Stakeholder Power Map Template and the importance of relationships. Call #4: Discuss the CISO Core Competency Evaluation Tool. |
Call #5: Discuss results of the CISO Core Competency Evaluation and identify resources to close gaps. Call #6: Review organizational structure and key stakeholder relationships. |
Call #7: Discuss and create your CISO development plan and track your development |
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 10 calls over the course of 3 to 6 months.
Phase 1
1.1 Understand Core Competencies
1.2 Measure Security and Business Satisfaction and Alignment
Phase 2
2.1 Assess Stakeholder Relationships
2.2 Assess the Core Competencies
Phase 3
3.1 Identify Resources to Address Competency Gaps
3.2 Plan Approach to Improve Stakeholder Relationships
Phase 4
4.1 Decide Next Actions and Support Your CISO Moving Forward
4.2 Regularly Reassess to Measure Development and Progress
This phase will walk you through the following activities:
Hire or Develop a World-Class CISO
Mark Lester
InfoSec Manager, SC Ports Authority
An organization hires a new Information Security Manager into a static and well-established IT department.
Situation: The organization acknowledges the need for improved information security, but there is no framework for the Security Manager to make successful changes.
| Challenges | Next Steps |
|---|---|
|
|
Follow this case study throughout the deck to see this organization’s results
Activities
Review core competencies the security leader must develop to become a strategic business partner
This step involves the following participants:
or
Outcomes of this step
Analysis and understanding of the eight strategic CISO competencies required to become a business partner
Launch
Info-Tech has identified eight core competencies affecting the CISO’s progression to becoming a strategic business partner.
|
Business Acumen Leadership Communication Technical Knowledge |
Innovative Problem Solving Vendor Management Change Management Collaboration |
< 1 hour
Over the next few slides, review each world-class CISO core competency. In Step 1.2, you will determine which competencies are a priority for your organization.
| CISO Competencies | Description |
|---|---|
| Business Acumen |
A CISO must focus primarily on the needs of the business and how the business works, then determine how to align IT security initiatives to support business initiatives. This includes:
|
| Leadership |
A CISO must be a security leader, and not simply a practitioner. This requires:
|
| CISO Competencies | Description |
|---|---|
| Communication |
Many CISOs believe that using technical jargon impresses their business stakeholders – in fact, it only makes business stakeholders become confused and disinterested. A CISO must have executive communication skills. This involves:
|
| Technical Knowledge |
A CISO must have a broad technical understanding of IT security to oversee a successful security program. This includes:
|
| CISO Competencies | Description |
|---|---|
| Innovative Problem Solving |
A good CISO doesn’t just say “no,” but rather finds creative ways to say “yes.” This can include:
|
| Vendor Management |
With the growing use of “anything as a service,” negotiation, vendor, and financial management skills are critical to becoming a strategic CISO.
|
| CISO Competencies | Description |
|---|---|
| Change Management |
A world-class CISO improves security processes by being an agent of change for the organization. This involves:
|
| Collaboration |
A CISO must be able to use alliances and partnerships strategically to benefit both the business and themselves. This includes:
|
Activities
This step involves the following participants:
or
Outcomes of this step
Determine current gaps in satisfaction and alignment between information security and your organization.
If seeking to hire/develop a CISO: Your diagnostic results will help develop a profile of the ideal CISO candidate to use as a hiring and interview guide.
If developing a current CISO, use your diagnostic results to identify existing competency gaps and target them for improvement.
For the CISO seeking to upgrade capabilities: Use the core competencies guide to self-assess and identify competencies that require improvement.
Launch
| Suggested Time: | One week for distribution, completion, and collection of surveys One-hour follow-up with an Info-Tech analyst |
The primary goal of IT security is to protect the organization from threats. This does not simply mean bolting everything down, but it means enabling business processes securely. To do this effectively requires alignment between IT security and the overall business.
Call an analyst to review your results and provide you with recommendations.
Info-Tech Insight
Focus on the high-priority competencies for your organization. You may find a candidate with perfect 10s across the board, but a more pragmatic strategy is to find someone with strengths that align with your needs. If there are other areas of weakness, then target those areas for development.
After completing the Info-Tech diagnostic, use the CISO Core Competency Evaluation Tool to determine which CISO competencies are a priority for your organization.
Download the CISO Core Competency Evaluation Tool
After completing the Info-Tech diagnostic, use the CISO Core Competency Evaluation Tool to determine which CISO competencies are a priority for your organization.
Download the CISO Core Competency Evaluation Tool
After completing the Info-Tech diagnostic, use the CISO Core Competency Evaluation Tool to determine which CISO competencies are a priority for your organization.
Download the CISO Core Competency Evaluation Tool
Phase 1
1.1 Understand Core Competencies
1.2 Measure Security and Business Satisfaction and Alignment
Phase 2
2.1 Assess Stakeholder Relationships
2.2 Assess the Core Competencies
Phase 3
3.2 Plan Approach to Improve Stakeholder Relationships
Phase 4
4.1 Decide Next Actions and Support Your CISO Moving Forward
4.2 Regularly Reassess to Measure Development and Progress
This phase will walk you through the following activities:
Hire or Develop a World-Class CISO
Mark Lester
InfoSec Manager, SC Ports Authority
The new Security Manager engages with employees to learn the culture.
Outcome: Understand what is important to individuals in order to create effective collaboration. People will engage with a project if they can relate it to something they value.
| Actions | Next Steps |
|---|---|
|
|
Follow this case study throughout the deck to see this organization’s results
Activities
Evaluate the power, impact, and support of key stakeholders
This step involves the following participants:
or
Outcomes of this step
Assess
Info-Tech Insight
Most organizations don’t exist for the sole purpose of doing information security. For example, if your organization is in the business of selling pencils, then information security is in business to enable the selling of pencils. All the security in the world is meaningless if it doesn’t enable your primary business processes. The CISO must always remember the fundamental goals of the business.
The above insight has two implications:
When people are not receptive to the CISO, it’s usually because the CISO has not been part of the discussion when plans were being made. This is the heart of proactivity.
You need to be involved from the start … from the earliest part of planning.
The job is not to come in late and say “No” ... the job is to be involved early and find creative and intelligent ways to say “Yes.”
The CISO needs to be the enabling security asset that drives business.
– Elliot Lewis, CEO at Keyavi Data
The CISO Stakeholder Power Map Template is meant to provide a visualization of the CISO’s relationships within the organization. This should be a living document that can be updated throughout the year as relationships develop and the structure of an organization changes.
At a glance, this tool should show:
Once this tool has been created, it provides a good reference as the CISO works to develop lagging relationships. It shows the landscape of influence and impact within the organization, which may help to guide the CISO’s strategy in the future.
Download the CISO Stakeholder Power Map Template
Info-Tech Insight
Some stakeholders must work closely with your incoming CISO. It is worth consideration to include these individuals in the interview process to ensure you will have partners that can work well together. This small piece of involvement early on can save a lot of headache in the future.
Once you know which competencies are a priority in your new CISO, the next step is to decide where to start looking. This person may already exist in your company.
|
Internal Take some time to review your current top information security employees or managers. It may be immediately clear that certain people will or will not be suitable for the CISO role. For those that have potential, proceed to Step 2.2 to map their competencies. |
Recruitment If you do not have any current employees that will fit your new CISO profile, or you have other reasons for wanting to bring in an outside individual, you can begin the recruitment process. This could start by posting the position for applications or by identifying and targeting specific candidates. |
Ready to start looking for your ideal candidate? You can use Info-Tech’s Chief Information Security Officer job description template.
|
Technical Counselor Seat In addition to having access to our research and consulting services, you can acquire a Technical Counselor Seat from our Security & Risk practice, where one of our senior analysts would serve with you on a retainer. You may find that this option saves you the expense of having to hire a new CISO altogether. |
Virtual CISO A virtual CISO, or vCISO, is essentially a “CISO as a service.” A vCISO provides an organization with an experienced individual that can, on a part-time basis, lead the organization’s security program through policy and strategy development. |
Why would an organization consider a vCISO?
Source: InfoSec Insights by Sectigo Store
Why would an organization not consider a vCISO?
Source: Georgia State University
Activities
Assess CISO candidates in terms of desired core competencies
or
Self-assess your personal core competencies
This step involves the following participants:
or
and
Outcomes of this step
Assess
Download the CISO Core Competency Evaluation Tool
Info-Tech Insight
The most important competencies should be your focus. Unless you are lucky enough to find a candidate that is perfect across the board, you will see some areas that are not ideal. Don’t forget the importance you assigned to each competency. If a candidate is ideal in the most critical areas, you may not mind that some development is needed in a less important area.
After deciding the importance of and requirements for each competency in Phase 1, assess your CISO candidates.
Your first pass on this tool will be to look at internal candidates. This is the develop a CISO option.
Download the CISO Core Competency Evaluation Tool
Download the CISO Core Competency Evaluation Tool
Phase 1
1.1 Understand Core Competencies
1.2 Measure Security and Business Satisfaction and Alignment
Phase 2
2.1 Assess Stakeholder Relationships
2.2 Assess the Core Competencies
Phase 3
3.1 Identify Resources to Address Competency Gaps
3.2 Plan Approach to Improve Stakeholder Relationships
Phase 4
4.1 Decide Next Actions and Support Your CISO Moving Forward
4.2 Regularly Reassess to Measure Development and Progress
This phase will walk you through the following activities:
Hire or Develop a World-Class CISO
Mark Lester
InfoSec Manager, SC Ports Authority
The new Security Manager changes the security culture by understanding what is meaningful to employees.
Outcome: Engage with people on their terms. The CISO must speak the audience’s language and express security terms in a way that is meaningful to the audience.
| Actions | Next Steps |
|---|---|
|
|
Follow this case study throughout the deck to see this organization’s results
Activities
Create a plan to remediate competency gaps
This step involves the following participants:
or
Outcomes of this step
Plan
Info-Tech’s Cybersecurity Workforce Training develops critical cybersecurity skills missing within your team and organization. The leadership track provides the same deep coverage of technical knowledge as the analyst track but adds hands-on support and has a focus on strategic business alignment, program management, and governance.
The program builds critical skills through:
Info-Tech Insight
Investing in a current employee that has the potential to be a world-class CISO may take less time, effort, and money than finding a unicorn.
Learn more on the Cybersecurity Workforce Development webpage
< 2 hours
| CISO Competencies | Description |
|---|---|
| Business Acumen |
Info-Tech Workshops & Blueprints
Actions/Activities
|
< 2 hours
| CISO Competencies | Description |
|---|---|
| Leadership |
Info-Tech Training and Blueprints
Action/Activities
|
Info-Tech Insight
Surround yourself with great people. Insecure leaders surround themselves with mediocre employees that aren’t perceived as a threat. Great leaders are supported by great teams, but you must choose that great team first.
< 2 hours
| CISO Competencies | Description |
|---|---|
| Communication |
Info-Tech Workshops & Blueprints Build and Deliver an Optimized IT Update Presentation: Show IT’s value and relevance by dropping the technical jargon and speaking to the business in their terms. Master Your Security Incident Response Communications Program: Learn how to talk to your stakeholders about what’s going on when things go wrong. Develop a Security Awareness and Training Program That Empowers End Users: Your weakest link is between the keyboard and the chair, so use engaging communication to create positive behavior change. Actions/Activities Learn to communicate in the language of your audience (whether business, finance, or social), and frame security solutions in terms that are meaningful to your listener. |
| Technical Knowledge |
Actions/Activities
|
< 2 hours
| CISO Competencies | Description |
|---|---|
| Innovative Problem Solving |
Info-Tech Workshops & Blueprints
Actions/Activities
|
| Vendor Management |
Info-Tech Blueprints & Resources
Actions/Activities
|
< 2 hours
| CISO Competencies | Description |
|---|---|
| Change Management |
Info-Tech Blueprints
Actions/Activities
|
| Collaboration |
Info-Tech Blueprints
Actions/Activities
|
What you will need to complete this exercise
Activities
This step involves the following participants:
or
Outcomes of this step
Plan
A formalized security organizational structure assigns and defines the roles and responsibilities of different members around security. Use Info-Tech’s blueprint Implement a Security Governance and Management Program to determine the best structure for your organization.
Who the CISO reports to, by percentage of organizations3
Download the Implement a Security Governance and Management Program blueprint
1. Journal of Computer Science and Information
2. Proofpoint
3. Heidrick & Struggles International, Inc
Managing stakeholders requires engagement, communication, and relationship management. To effectively collaborate and gain support for your initiatives, you will need to build relationships with your stakeholders. Take some time to review the stakeholder engagement strategies for different stakeholder types.
| Influence | Mediators (Satisfy) |
Key Players (Engage) |
| Spectators (Monitor) |
Noisemakers (Inform) |
|
| Support for you | ||
When building relationships, I find that what people care about most is getting their job done. We need to help them do this in the most secure way possible.
I don’t want to be the “No” guy, I want to enable the business. I want to find to secure options and say, “Here is how we can do this.”
– James Miller, Information Security Director, Xavier University
Download the CISO Stakeholder Management Strategy Template
| Goal | Action |
|---|---|
| Get key players to help champion your initiative and turn your detractors into supporters. | Actively involve key players to take ownership. |
| Keep It Positive | Maintain a Close Relationship |
|
|
Info-Tech Insight
Listen to your key players. They understand what is important to other business stakeholders, and they can provide valuable insight to guide your future strategy.
| Goal | Action |
|---|---|
| Turn mediators into key players | Increase their support level. |
| Keep It Positive | Maintain a Close Relationship |
|
|
Info-Tech Insight
Don’t dictate to stakeholders. Make them feel like valued contributors by including them in development and decision making. You don’t have to incorporate all their input, but it is essential that they feel respected and heard.
| Goal | Action |
|---|---|
| Have noisemakers spread the word to increase their influence. | Encourage noisemakers to influence key stakeholders. |
| Keep It Positive | Maintain a Close Relationship |
|
|
| Goal | Action |
|---|---|
| Keep spectators content and avoid turning them into detractors. | Keep them well informed. |
| Keep It Positive | Maintain a Close Relationship |
|
|
Develop a strategy to manage key stakeholders in order to drive your personal development plan initiatives.
What you will need to complete this exercise
Download the CISO Stakeholder Management Strategy Template
Phase 1
1.1 Understand Core Competencies
1.2 Measure Security and Business Satisfaction and Alignment
Phase 2
2.1 Assess Stakeholder Relationships
2.2 Assess the Core Competencies
Phase 3
3.1 Identify Resources to Address Competency Gaps
3.2 Plan Approach to Improve Stakeholder Relationships
Phase 4
4.1 Decide Next Actions and Support Your CISO Moving Forward
4.2 Regularly Reassess to Measure Development and Progress
This phase will walk you through the following activities:
Hire or Develop a World-Class CISO
Mark Lester
InfoSec Manager, SC Ports Authority
The new Security Manager leverages successful cultural change to gain support for new security investments.
Outcome: Integrating with the business on a small level and building on small successes will lead to bigger wins and bigger change.
| Actions | Next Steps |
|---|---|
|
|
Activities
This step involves the following participants:
or
Outcomes of this step
Next actions for each of your development initiatives
Execute
The CISO Development Plan Template provides a simple but powerful way to focus on what really matters to execute your plan.
| Item to Develop (competency/process/tech) |
|---|
| First Action Toward Development |
| Desired Outcome, Including a Measurable Indicator |
Download the CISO Development Plan Template
Use Info-Tech’s CISO Development Plan Template to create a quick and simple yet powerful tool that you can refer to and update throughout your personal and professional development initiatives. As instructed in the template, you will document the following:
| Your Item to Develop | The Next Action Required | The Target Outcome |
|---|---|---|
| This could be a CISO competency, a security process item, a security technology item, or an important relationship (or something else that is a priority). | This could be as simple as “schedule lunch with a stakeholder” or “email Info-Tech to schedule a Guided Implementation call.” This part of the tool is meant to be continually updated as you progress through your projects. The strength of this approach is that it focuses your project into simple actionable steps that are easily achieved, rather than looking too far down the road and seeing an overwhelming task ahead. | This will be something measurable like “reduce spending by 10%” or “have informal meeting with leaders from each department.” |
Info-Tech Insight
A good plan doesn’t require anything that is outside of your control. Good measurable outcomes are behavior based rather than state based.
“Increase the budget by 10%” is a bad goal because it is ultimately reliant on someone else and can be derailed by an unsupportive executive. A better goal is “reduce spending by 10%.” This is something more within the CISO’s control and is thus a better performance indicator and a more achievable goal.
Below you will find sample content to populate your CISO Development Plan Template. Using this template will guide your CISO in achieving the goals identified here.
The template itself is a metric for assessing the development of the CISO. The number of targets achieved by the due date will help to quantify the CISO’s progress.
You may also want to include improvements to the organization’s security program as part of the CISO development plan.
| Area for Development | Item for Development | Next Action Required | Key Stakeholders/ Owners | Target Outcome | Due Date | Completed | |
|---|---|---|---|---|---|---|---|
| Core Competencies: Communication |
Executive communication |
Take economics course to learn business language | Course completed | [Insert date] | [Y/N] | ||
| Core Competencies: Communication |
Improve stakeholder relationships |
Email Bryce from finance to arrange lunch | Improved relationship with finance department | [Insert date] | [Y/N] | ||
| Technology Maturity: Security Prevention | Identity and access management (IAM) system | Call Info-Tech to arrange call on IAM solutions | 90% of employees entered into IAM system | [Insert date] | [Y/N] | ||
| Process Maturity: Response & Recovery | Disaster recovery | Read Info-Tech blueprint on disaster recovery | Disaster recovery and backup policies in place | [Insert date] | [Y/N] |
Check out the First 100 Days as CISO blueprint for guidance on bringing improvements to the security program
| Area for Development | Item for Development | Next Action Required | Key Stakeholders/ Owners | Target Outcome | Due Date | Completed |
|---|---|---|---|---|---|---|
| Core Competencies: Communication |
Executive communication |
Take economics course to learn business language | Course completed | [Insert date] | [Y/N] | |
| Core Competencies: Communication |
Improve stakeholder relationships |
Email Bryce from finance to arrange lunch | Improved relationship with finance department | [Insert date] | [Y/N] | |
| Technology Maturity: Security Prevention | Identity and access management (IAM) system | Call Info-Tech to arrange call on IAM solutions | 90% of employees entered into IAM system | [Insert date] | [Y/N] | |
| Process Maturity: Response & Recovery | Disaster recovery | Read Info-Tech blueprint on disaster recovery | Disaster recovery and backup policies in place | [Insert date] | [Y/N] |
Activities
Create a calendar event for you and your CISO, including which items you will reassess and when
This step involves the following participants:
or
Outcomes of this step
Scheduled reassessment of the CISO’s competencies
Execute
< 1 day
As previously mentioned, your CISO development plan is meant to be a living document. Your CISO will use this as a companion tool throughout project implementation, but periodically it will be necessary to re-evaluate the entire program to assess your progress and ensure that your actions are still in alignment with personal and organizational goals.
Info-Tech recommends performing the following assessments quarterly or twice yearly with the help of our executive advisors (either over the phone or onsite).
| Materials |
|---|
|
| Participants |
|
| Output |
|
If you would like additional support, have our analysts guide you through an Info-Tech workshop or Guided Implementation
Contact your account representative for more information
workshop@infotech.com
1-888-670-8889
Build an Information Security Strategy
Your security strategy should not be based on trying to blindly follow best practices but on a holistic risk-based assessment that is risk aware and aligns with your business context.
The First 100 Days as CISO
Every CISO needs to follow Info-Tech’s five-step approach to truly succeed in their new position. The meaning and expectations of a CISO role will differ from organization to organization and person to person, but the approach to the new position will be relatively the same.
Implement a Security Governance and Management Program
Business and security goals should be the same. Businesses cannot operate without security, and security's goal is to enable safe business operations.
Dicker, William. "An Examination of the Role of vCISO in SMBs: An Information Security Governance Exploration." Dissertation, Georgia State University, May 2, 2021. Accessed 30 Sep. 2022.
Heidrick & Struggles. "2022 Global Chief Information Security Officer (CISO) Survey" Heidrick & Struggles International, Inc. September 6, 2022. Accessed 30 Sep. 2022.
IBM Security. "Cost of a Data Breach Report 2022" IBM. August 1, 2022. Accessed 9 Nov. 2022.
Mehta, Medha. "What Is a vCISO? Are vCISO Services Worth It?" Infosec Insights by Sectigo, June 23, 2021. Accessed Nov 22. 2022.
Milica, Lucia. “Proofpoint 2022 Voice of the CISO Report” Proofpoint. May 2022. Accessed 6 Oct. 2022.
Navisite. "The State of Cybersecurity Leadership and Readiness" Navisite. November 9, 2021. Accessed 9 Nov. 2022.
Shayo, Conrad, and Frank Lin. “An Exploration of the Evolving Reporting Organizational Structure for the Chief Information Security Officer (CISO) Function” Journal of Computer Science and Information Technology, vol. 7, no. 1, June 2019. Accessed 28 Sep. 2022.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Understand the importance of customer service training, then deliver Info-Tech's training program to your IT team.
Tailor your security program according to what makes your organization unique.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
This storyboard will help you lay foundations for your security program that will inform future security program decisions and give your leadership team the information they need to support your success. You will evaluate design factors that make your organization unique, prioritize the security capabilities to suit, and assess the maturity of key security program components including security governance, security strategy, security architecture, service design, and service metrics.
Use this Excel workbook to evaluate your security program against ten key design factors. The tool will produce a goals cascade that shows the relationship between business and security goals, a prioritized list of security capabilities that align to business requirements, and a list of program accountabilities.
This second Excel workbook will help you conduct a gap analysis on key security program components and identify improvement initiatives. You can then use the Security Program Design and Implementation Plan to collect results from the design and implementation tools and draft a communication deck.
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.
Determine the initial design of your security program.
An initial prioritized list of security capabilities that aligns with enterprise strategy and goals.
1.1 Review Info-Tech diagnostic results.
1.2 Identify project context.
1.3 Identify enterprise strategy.
1.4 Identify enterprise goals.
1.5 Build a goal cascade.
1.6 Assess the risk profile.
1.7 Identify IT-related issues.
1.8 Evaluate initial program design.
Stakeholder satisfaction with program
Situation, challenges, opportunities
Initial set of prioritized security capabilities
Initial set of prioritized security capabilities
Initial set of prioritized security capabilities
Initial set of prioritized security capabilities
Initial set of prioritized security capabilities
Initial set of prioritized security capabilities
Refine the design of your security program.
A refined, prioritized list of security capabilities that reflects what makes your organization unique.
2.1 Gauge threat landscape.
2.2 Identify compliance requirements.
2.3 Categorize the role of IT.
2.4 Identify the sourcing model.
2.5 Identify the IT implementation model.
2.6 Identify the tech adoption strategy.
2.7 Refine the scope of the program.
Refined set of prioritized security capabilities
Refined set of prioritized security capabilities
Refined set of prioritized security capabilities
Refined set of prioritized security capabilities
Refined set of prioritized security capabilities
Refined set of prioritized security capabilities
Refined set of prioritized security capabilities
Finalize security program design.
Key accountabilities to support the security program
Gap analysis to produce an improvement plan
3.1 Identify program accountabilities.
3.2 Conduct program gap analysis.
3.3 Prioritize initiatives.
Documented program accountabilities.
Security program gap analysis
Security program gap analysis
Create and communicate an improvement roadmap for the security program.
Security program design and implementation plan to organize and communicate program improvements.
4.1 Build program roadmap
4.2 Finalize implementation plan
4.3 Sponsor check-in
Roadmap of program improvement initiatives
Roadmap of program improvement initiatives
Communication deck for program design and implementation
EXECUTIVE BRIEF
![]() |
Security leaders often tout their choice of technical security framework as the first and most important program decision they make. While the right framework can help you take a snapshot of the maturity of your program and produce a quick strategy and roadmap, it won’t help you align, modernize, or transform your program to meet emerging business requirements. Common technical security frameworks focus on operational controls rather than business services and value creation. They are difficult to convey to business stakeholders and provide little program management or implementation guidance. Focus on business value first, and the security services that enable it. Your organization has its own distinct character and profile. Understand what makes your organization unique, then design and refine the design of your security program to ensure it supports the right capabilities. Next, collaborate with stakeholders to ensure the right accountabilities, roles, and responsibilities are in place to support the implementation of the security program. |
Michel Hébert |
Your Challenge |
Common Obstacles |
Info-Tech’s Approach |
|---|---|---|
|
|
Tailor your security program according to what makes your organization unique.
|
Info-Tech Insight
You are a business leader who supports business goals and mitigates risk. Focus first on business value and the security services that enable it, not security controls.
Cybercriminals deploying ransomware are evolving into a growing and sophisticated criminal ecosystem that will continue to adapt to maximize its profits.
Malicious agents continue to target critical infrastructure to harm industrial processes and the customers they serve State-sponsored actors are expected to continue to target critical infrastructure to collect information through espionage, pre-position in case of future hostilities, and project state power.
Malicious actors increasingly deceive or exploit cryptocurrencies, machine learning, and artificial intelligence technologies to support their activities.
50% Only half of leaders are framing the impact of security threats as a business risk.
49% Less than half of leaders align security program cost and risk reduction targets with the business.
57% Most leaders still don’t regularly review security program performance of the business.
Organizations with misaligned security programs have 48% more security incidents...
…and the cost of their data breaches are 40% higher than those with aligned programs.
37% of stakeholders still lack confidence in their security program.
54% of senior leaders still doubt security gets the goals of the organization.
“There's so much focus on better risk management that every leadership team in every organization wants to be part of the solution.
If you can give them good data about what things they really need to do, they will work to understand it and help you solve the problem.”

1. New CISO
“I need to understand the business, prioritize core security capabilities, and identify program accountabilities quickly.”
2. Program Renewal
“The business is changing, and the threat landscape is shifting. I am concerned the program is getting stale.”
Use this blueprint to understand what makes your organization unique:
If you need a deep dive into governance, move on to a security governance and management initiative.
3. Program Update
“I am happy with the fundamentals of my security program. I need to assess and improve our security posture.”
Move on to our guidance on how to Build an Information Security Strategy instead.
Define Scope of |
Refine Scope of |
Finalize Security |
|
|---|---|---|---|
Phase steps |
1.1 Identify enterprise strategy 1.2 Identify enterprise goals 1.3 Assess the risk profile 1.4 Identify IT-related issues 1.5 Define initial program design |
2.1 Gage threats and compliance 2.2 Assess IT role and sourcing 2.3 Assess IT implementation model 2.4 Assess tech adoption strategy 2.5 Refine program design |
3.1 Identify program accountabilities 3.2 Define program target state 3.3 Build program roadmap |
Phase outcomes |
|
|
|
Tools |
You are a business leader first and a security leader second
Technical security frameworks are static and focused on operational controls and standards. They belong in your program’s solar system but not at its center. Design your security program with business value and the security services that enable it in mind, not security controls.
There is no one-size-fits-all security program
Tailor your security program to your organization’s distinct profile to ensure the program generates value.
Lay the right foundations to increase engagement
Map out accountabilities, roles, and responsibilities to ensure the components of your security program work together over time to secure and enable business services.
If you build it, they will come
Your executive team wants to be part of the solution. If you give them reliable data for the things they really need to do, they will work to understand and help you solve the problem.
Security Program Design Tool
Tailor the security program to what makes your organization unique to ensure alignment.

Security Program Implementation Tool
Assess the current state of different security program components and plan next steps.
SecurityProgram Design and Implementation Plan
Communicate capabilities, accountabilities, and implementation initiatives.

Key deliverable
Security Program Design and Implementation Plan
The design and implementation plan captures the key insights your work will generate, including:
IT Benefits |
Business Benefits |
|---|---|
|
|
Deliverable |
Challenge |
|
|---|---|---|
Security Program Design |
|
|
Program Assessment and Implementation Plan |
|
|
Measured Value |
|
Governance & Management Maturity Scorecard
Understand the maturity of your security program across eight domains.
Audience: Security Manager
Security Business Satisfaction and Alignment Report
Assess the organization’s satisfaction with the security program.
Audience: Business Leaders
CIO Business Vision
Assess the organization’s satisfaction with IT services and identify relevant challenges.
Audience: Business Leaders
INDUSTRY: Higher Education
SOURCE: Interview
Building a business-aligned security program
Portland Community College (PCC) is the largest post-secondary institution in Oregon and serves more than 50,000 students each year. The college has a well-established information technology program, which supports its education mission in four main campuses and several smaller centers.
PCC launched a security program modernization effort to deal with the evolving threat landscape in higher education. The CISO studied the enterprise strategy and goals and reviewed the college’s risk profile and compliance requirements. The exercise helped the organization prioritize security capabilities for the renewal effort and informed the careful assessment of technical controls in the current security program.
Results
Laying the right foundations for the security program helped the security function understand how to provide the organization with a clear report of its security posture. The CISO now reports directly to the board of directors and works with stakeholders to align cost, performance, and risk reduction objectives with the needs of the college.
The security program modernization effort prioritized several critical design factors
“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.”
| Phase 1 | Phase 2 | Phase 3 |
|---|---|---|
Call #1: Call #2: |
Call #3: Call #4: |
Call #5: Call #6: |
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 4 to 6 calls over the course of 6 months.
Contact your account representative for more information.
workshops@infotech.com 1-888-670-8889
| Day 1 | Day 2 | Day 3 | Day 4 | Day 5 | |
|---|---|---|---|---|---|
Initial Security |
Refine Security |
Security Program |
Roadmap and Implementation Plan |
Next Steps and |
|
Activities |
1.1.0 Review Info-Tech diagnostic results 1.1.1 Identify project context 1.1.2 Identify enterprise strategy 1.2.1 Identify enterprise goals 1.2.2 Build a goals cascade 1.3 Assess the risk profile 1.4 Identify IT-related issues 1.5 Evaluate initial program design |
2.1.1 Gauge threat landscape 2.1.2 Identify compliance requirements 2.2.1 Categorize the role of IT 2.2.2 Identify the sourcing model 2.3.1 Identify the IT implementation model 2.4.1 Identify the tech adoption strategy 2.5.1 Refine the design of the program |
3.1 Identify program accountabilities 3.2.1 Conduct program gap analysis 3.2.2 Prioritize initiatives |
3.3.1 Build program roadmap 3.3.2 Finalize implementation plan 3.3.3 Sponsor check-in |
4.1 Complete in-progress deliverables from previous four days 4.2 Set up review time for workshop deliverables and to discuss next steps |
Deliverables |
|
|
|
|
|
Workshop |
Workshop |
|---|---|
Security Program Design Factors |
Security Program Gap Analysis or |
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Valence Howden Principal Research Director, CIO Practice |
Petar Hristov Research Director, Security, Privacy, Risk & Compliance |
Ian Mulholland Research Director, Security, Risk & Compliance |
Brittany Lutes Senior Research Analyst, CIO Practice |
Ibrahim Abdel-Kader Research Analyst, CIO Practice |
Every organization has a threshold for risk that should not be exceeded, whether that threshold is defined or not.
In the age of digital, information and technology will undoubtedly continue to expand beyond the confines of the IT department. As such, different areas of the organization cannot address these risks in silos. A siloed approach will produce different ways of identifying, assessing, responding to, and reporting on risk events. Integrated risk management is about embedding IT uncertainty to inform good decision making across the organization.
When risk is integrated into the organization's enterprise risk management program, it enables a single view of all risks and the potential impact of each risk event. More importantly, it provides a consistent view of the risk event in relation to uncertainty that might have once been seemingly unrelated to IT.
And all this can be achieved while remaining within the enterprise’s clearly defined risk appetite.
Most organizations fail to integrate IT risks into enterprise risks:
IT leaders have to overcome these obstacles when it comes to integrating risk:
By leveraging the Info-Tech Integrated Risk approach, your business can better address and embed risk by:
Stop avoiding risk – integrate it. This provides a holistic view of uncertainty for the organization to drive innovative new approaches to optimize its ability to respond to risk.
Enterprise risk management is the practice of identifying and addressing risks to your organization and using risk information to drive better decisions and better opportunities.
|
IT risks have a direct and often aggregated impact on enterprise risks and opportunities in the same way other business risks can. This relationship must be understood and addressed through integrated risk management to ensure a consistent approach to risk. |
Risk-mature organizations have a unique benefit in that they often have established an overarching governance framework and embedded risk awareness into the culture.
35% — Only 35% of organizations had embraced ERM in 2020. (Source: AICPA and NC State Poole College of Management)
12% — Only 12% of organizations are leveraging risk as a tool to their strategic advantage. (Source: AICPA and NC State Poole College of Management)
62% — Accessing and disseminating information is the main challenge for 62% of organizations maturing their organizational risk management. (Source: OECD)
20-28% — Organizations with access to machine learning and analytics to address future risk events have 20 to 28% more satisfaction. (Source: Accenture)
Accelerate and optimize your organization by leveraging meaningful risk data to make intelligent enterprise risk decisions.
Risk Drivers
|
Only 7% of organizations are in a “leading” or “aspirational” level of risk maturity. (OECD, 2021) | 63% of organizations struggle when it comes to defining their appetite toward strategy related risks. (“Global Risk Management Survey,” Deloitte, 2021) | Late adopters of risk management were 70% more likely to use instinct over data or facts to inform an efficient process. (Clear Risk, 2020) | 55% of organizations have little to no training on ERM to properly implement such practices. (AICPA, NC State Poole College of Management, 2021) | |
| 1. Assess Enterprise Risk Maturity | 3. Build a Risk Management Program Plan | 4. Establish Risk Management Processes | 5. Implement a Risk Management Program | ||
| 2. Determine Authority with Governance
Unfortunately, less than 50% of those in risk focused roles are also in a governance role where they have the authority to provide risk oversight. (Governance Institute of Australia, 2020) |
|||||
| IT can improve the maturity of the organization’s risk governance and help identify risk owners who have authority and accountability.
Governance and related decision making is optimized with integrated and aligned risk data. |
|
ERM incorporates the different types of risk, including IT, security, digital, vendor, and other risk types. The program plan is meant to consider all the major risk types in a unified approach. |
|
Implementation of an integrated risk management program requires ongoing access to risk data by those with decision making authority who can take action. | |
Stop fearing risk – integrate it. Integration leads to opportunities for organizations to embrace innovation and new digital technologies as well as reducing operational costs and simplifying reporting.
Governance of risk management for information- and technology-related events is often misplaced. Just because it's classified as an IT risk does not mean it shouldn’t be owned by the board or business executive.
Integrating risk requires a baseline of risk maturity at the enterprise level. IT can push integrating risks, but only if the enterprise is willing to adopt the attitudes and behaviors that will drive the integrated risk approach.
It is not a strategic decision to have different areas of the organization manage the risks perceived to be in their department. It’s the easy choice, but not the strategic one.
Different areas of an enterprise apply risk management processes differently. Determining a single method for identification, assessment, response, and monitoring can ensure successful implementation of enterprise risk management.
Good risk management will consider both the positives and negatives associated with a risk management program by recognizing both the upside and downside of risk event impact and likelihood.
IT Benefits
|
Business Benefits
|
“31% of CIO’s expected their role to expand and include risk management responsibilities.” (IDG “2021 State of the CIO,” 2021)
58%Focus not just on the preventive risk management but also the value-creating opportunities. With 58% of organizations concerned about disruptive technology, it’s an opportunity to take the concern and transform it into innovation. (Accenture) |
70%Invest in tools that have data and analytics features. Currently, “gut feelings” or “experience” inform the risk management decisions for 70% of late adopters. (Clear Risk) |
54%Align to the strategic vision of the board and CEO, given that these two roles account for 54% of the accountability associated with extended enterprise risk management. (Extended Enterprise Risk Management Survey, 2020,” Deloitte) |
63%Include IT leaders in the risk committee to help informed decision making. Currently 63% of chief technology officers are included in the C‑suite risk committee. (AICPA & NC State Poole College of Management) |
| Successful adoption of integrated risk management is often associated with these key elements. | |||
Mature or not, integrated risk management should be a consideration for all organizationsThe first step to integrating risk management within the enterprise is to understand the organization’s readiness to adopt practices that will enable it to successfully integrate information. In 2021, we saw enterprise risk management assessments become one of the most common trends, particularly as a method by which the organization can consolidate the potential impacts of uncertainties or threats (Lawton, 2021). A major driver for this initiative was the recognition that information and technology not only have enterprise-wide impacts on the organization’s risk management but that IT has a critical role in supporting processes that enable effective access to data/information. A maturity assessment has several benefits for an organization: It ensures there is alignment throughout the organization on why integrated risk is the right approach to take, it recognizes the organization’s current risk maturity, and it supports the organization in defining where it would like to go. |
|
Integrated Risk Maturity Categories |
|
1 |
Context & Strategic Direction | Understand the organization’s main objectives and how risk can support or enhance those objectives. |
2 |
Risk Culture and Authority | Examine if risk-based decisions are being made by those with the right level of authority and if the organization’s risk appetite is embedded in the culture. | ||
3 |
Risk Management Process | Determine if the current process to identify, assess, respond to, monitor, and report on risks is benefitting the organization. | ||
4 |
Risk Program Optimization | Consider opportunities where risk-related data is being gathered, reported, and used to make informed decisions across the enterprise. |
For organizations with a low maturity, remaining superficial with risk will offer more benefits and align to the enterprise’s risk tolerance and appetite. This might mean no integrated risk is taking place.
However, organizations that have higher risk maturity should begin to integrate risk information. These organizations can identify the nuances that would affect the severity and impact of risk events.
The purpose of the Integrated Risk Maturity Assessment is to assess the organization's current maturity and readiness for integrated risk management (IRM).
Frequently and continually assessing your organization’s maturity toward integrated risk ensures the right risk management program can be adopted by your organization.
| Integrated Risk Maturity Assessment
A simple tool to understand if your organization is ready to embrace integrated risk management by measuring maturity across four key categories: Context & Strategic Direction, Risk Culture & Authority, Risk Management Process, and Risk Program Optimization |
|
Use the results from this integrated risk maturity assessment to determine the type of risk management program that can and should be adopted by your organization.
Some organizations will need to remain siloed and focused on IT risk management only, while others will be able to integrate risk-related information to start enabling automatic controls that respond to this data.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Determine your organization’s rationale for cloud adoption and what that means for your security obligations.
Use the Cloud Security CAGI Tool to perform four unique assessments that will be used to identify secure cloud vendors.
Learn how to assess and communicate with cloud vendors with security in mind.
Turn your security requirements into specific tasks and develop your implementation roadmap.
Build the organizational structure of your cloud security governance program.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Review previous communications to prepare for your first day.
Understand how the business operates and develop meaningful relationships with your sphere of influence.
Inventory company assets to know what to protect.
Evaluate the security posture of the organization by leveraging Info-Tech’s IT Security diagnostic program.
Communicate your security vision to business stakeholders.
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Identify gaps, establish a list of dashboards and reports to enhance, and set out a roadmap for your dashboard and reporting enhancement project.
Gain an understanding of how to design effective dashboards and reports.
Officially close and evaluate the PPM dashboard and reporting enhancement project and transition to an ongoing and sustainable PPM dashboard and reporting 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.
PPM dashboards and reports will only be effective and valuable if they are designed to meet your organization’s specific needs and priorities.
Conduct a decision-support review and a thorough dashboard and report audit to identify the gaps your project will address.
Take advantage of the planning stage to secure sponsor and stakeholder buy-in.
Current-state assessment of satisfaction with PPM decision-making support.
Current-state assessment of all existing dashboards and reports: effort, usage, and satisfaction.
A shortlist of dashboards and reports to improve that is informed by actual needs and priorities.
A shortlist of dashboards and reports to create that is informed by actual needs and priorities.
The foundation for a purposeful and focused PPM dashboard and reporting program that is sustainable in the long term.
1.1 Engage in PPM decision-making review.
1.2 Perform a PPM dashboard and reporting audit and gap analysis.
1.3 Identify dashboards and/or reports needed.
1.4 Plan the PPM dashboard and reporting project.
PPM Decision-Making Review
PPM Dashboard and Reporting Audit
Prioritized list of dashboards and reports to be improved and created
Roadmap for the PPM dashboard and reporting project
Once the purpose of each PPM dashboard and report has been identified (based on needs and priorities) it is important to establish what exactly will be required to produce the desired outputs.
Gathering stakeholder and technical requirements will ensure that the proposed and finalized designs are realistic and sustainable in the long term.
Dashboard and report designs that are informed by a thorough analysis of stakeholder and technical requirements.
Dashboard and report designs that are realistically sustainable in the long term.
2.1 Review the best practices and science behind effective dashboards and reporting.
2.2 Gather stakeholder requirements.
2.3 Gather technical requirements.
2.4 Build wireframe options for each dashboard or report.
2.5 Review options: requirements, feasibility, and usability.
2.6 Finalize initial designs.
2.7 Design and record the input, production, and consumption workflows and processes.
List of stakeholder requirements for dashboards and reports
Wireframe design options
Record of the assessment of each wireframe design: requirements, feasibility, and usability
A set of finalized initial designs for dashboards and reports.
Process workflows for each initial design
Ensure that enhanced dashboards and reports are actually adopted in the long term by carefully planning their roll-out to inputters, producers, and consumers.
Plan to train all stakeholders, including report consumers, to ensure that the reports generate the decision support and PPM value they were designed to.
An informed, focused, and scheduled plan for rolling out dashboards and reports and for training the various stakeholders involved.
3.1 Plan for external resourcing (if necessary): vendors, consultants, contractors, etc.
3.2 Conduct impact analysis: risks and opportunities.
3.3 Create an implementation and training plan.
3.4 Determine PPM dashboard and reporting project success metrics.
External resourcing plan
Impact analysis and risk mitigation plan
Record of the PPM dashboard and reporting project success metrics
Besides the small introduction, subscribers and consulting clients within this management domain have access to:
Establish an effective EA function that will realize value for the organization with an EA strategy.
Use this template to document the outputs of the EA strategy and to communicate the EA strategy for approval by stakeholders.
Identify and prioritize the stakeholders that are important to your IT strategy development effort.
Use this template to analyze the effect of external factors on IT.
Use this template to create an EA value proposition that explicitly communicates to stakeholders how an EA function can contribute to addressing their needs.
Use this template to help set goals for your EA function based on the EA value proposition and identify objectives to measure the progression towards those EA goals.
Use this template to define relevant universal EA principles and create new EA principles to guide and inform IT investment decisions.
Use this template to identify the EA services relevant to your organization and then define how those services will be accessed.
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.
Show an example of traceability.
Members have a real-world example of traceability between business goals and EA contributions.
1.1 Start from the business goals of the organization.
1.2 Document business and IT drivers.
1.3 Identify EA contributions that help achieve the business goals.
Business goals documented.
Business and IT drivers documented.
Identified EA contributions and traced them to business goals.
Create an understanding about role of architect in Agile ceremonies.
Understanding of the role of the EA architect in Agile ceremonies.
2.1 Document the Agile ceremony used in the organization (based on SAFe or other Agile approaches).
2.2 Determine which ceremonies the system architect will participate in.
2.3 Determine which ceremonies the solution architect will participate in.
2.4 Determine which ceremonies the enterprise architect will participate in.
2.5 Determine architect syncs, etc.
Documented the Agile ceremonial used in the organization (based on SAFe or other Agile approaches).
Determined which ceremonies the system architect will participate in.
Determined which ceremonies the solution architect will participate in.
Determined which ceremonies the enterprise architect will participate in.
Determined architect syncs, etc.
Enterprise Architecture Strategy |
|||
Business & IT Strategy
|
|
|
Unlock the Value of Architecture
|
Current Environment
|
|||
Enterprise architecture is NOT a one-size-fits-all endeavor. It needs to be right-sized to the needs of the organization.
Enterprise architects are boots on the ground and part of the solution; in addition, they need to have a good understanding of the corporate strategy, vision, and goals and have a vested interest on the optimization of the outcomes for the enterprise. They also need to anticipate the moves ahead, to be able to determine future trends and how they will impact the enterprise.
Milena Litoiu
Principal/Senior Director, Enterprise Architecture
Info-Tech Research Group
“Enterprise architects need to think about and consider different areas of expertise when formulating potential business options. By understanding the context, the puzzle pieces can combine to create a positive business outcome that aligns with the organization’s strategies. Sometimes there will be missing pieces; leveraging what you know to create an outline of the pieces and collaborating with others can provide a general direction.”
Jean Bujold
Senior Workshop Delivery Director
Info-Tech Research Group
“The role of enterprise architecture is to eliminate misalignment between the business and IT and create value for the organization.”
Reddy Doddipalli
Senior Workshop Director, Research
Info-Tech Research Group
“Every transformation journey is an opportunity to learn: ‘Tell me and I forget. Teach me and I remember. Involve me and I learn.’ Benjamin Franklin.”
Graham Smith
Senior Lead Enterprise Architect and Independent Consultant
We need to make decisions today for an unknown future. Decisions are influenced by:
Decisions are often made:
The more complex an organization, the more players involved, the more difficult it is to overcome these obstacles.
There is no “right architecture” for organizations of all sizes, maturities, and cultural contexts. The value of enterprise architecture can only be measured against the business goals of a single organization. Enterprise architecture needs to be right-sized for your organization.
| Business engagement
It is important to trace architectural decisions to business goals. As business goals evolve, architecture should evolve as well. As new business input is provided during Agile cycles, architecture is continuously evolving. |
EA fundamentals
EA fundamentals will shape how enterprise architects think and act, how they engage with the organization, what decisions they make, etc. Start small and lean and evolve as needed. Continuously align strategy with delivery and operations. Architects should establish themselves as business partners as well as implementation/delivery leaders. |
Enterprise services
Definitions of enterprise services should start from the business goals of the organization and the capabilities IT needs to perform for the organization to survive in the marketplace. Continuous delivery and continuous innovation are the two facets of architecture. |
| Tactical insight
Your current maturity should be reflected as a baseline in the strategy. |
Tactical insight
Take Agile/opportunistic steps toward your strategic North star. |
Tactical insight
EA services differ based on goals, maturity, and the Agile appetite of the enterprise. |
Jeanne W. Ross, MIT CISR
Co-author of Enterprise Architecture as Strategy: Creating a Foundation for Business Execution,
Harvard Business Press, 2006.
|
|
There is no “absolute maturity” for organizations of all sizes, maturities, and cultural contexts. The maturity of enterprise architecture can only be measured against the business goals of the organization.
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." |
Contact your account representative for more information.
workshops@infotech.com1-888-670-8889
| Session 1 | Session 2 | Session 3 | Session 4 | Session 5 | |
| Activities |
Identify organizational needs and landscape1.0 Interview stakeholders to identify business and technology needs 1.1 Review organization perspective, including business needs, challenges, and strategic directions 1.2 Conduct PESTLE analysis to identify business and technology trends 1.3 Conduct SWOT analysis to identify business and technology internal perspective |
Create the EA value proposition2.1 Identify and prioritize EA stakeholders 2.2 Create business and technology drivers from needs 2.3 Define the EA value proposition 2.4 Identify EA maturity and target |
Define the EA fundamentals3.1 Define the EA goals and objectives 3.2 Determine EA scope 3.3 Create a set of EA principles 3.4. Define the need of a methodology/agility 3.5 Create the EA vision and mission statement |
Identify the EA framework and communicate the EA strategy4.1 Define initial EA operating model and governance mechanism 4.2 Define the activities and services the EA function will provide, derived from business goals 4.3 Determine effectiveness measures 4.4 Create EA roadmap and next steps 4.5 Build communication plan for stakeholders |
Next Steps and Wrap-Up (offsite)5.1 Generate workshop report 5.2 Set up review time for workshop report and to discuss next steps |
| Outcomes |
|
|
|
|
|
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.
While variations depend on the maturity of the organization as well as its aspirations, these are some typical steps:
Phase 1
|
Phase 2
|
||
Phase 3
|
Phase 4
|
Define the role of the group and different roles inside the enterprise architecture competency.
Enterprise architecture needs to have input from the corporate strategy of the organization. Similarly, EA governance needs to be informed by corporate governance. If this is not the case, it is like planning and governing with your eyes closed.
| EA Functions |
Operationalized
|
–––› | Common EA value | |
| Decreased cost | Reduced risk | |||
Emerging
|
–x–› | Cut through complexity | Increased agility | |
| External Factors | –› | Layers of a Business Model (Organization) |
–› | Architecture Supported Transformation |
| Industry Changes | Business Strategy | |||
| Competition | Value Streams
(Business Outcomes) |
|||
| Regulatory Impacts | Business Capability Maps
|
|||
| Workforce Impacts | Execution
|
External forces can affect the organization as a whole; they need to be included as part of the holistic approach for enterprise architecture.
Business and Technology Drivers – A set of statements created from business and technology needs. Gathered from information sources, it communicates improvements needed.
Enterprise architecture needs to create and be part of a culture where decisions are made through collaboration while focusing on enterprise-wide efficiencies (e.g. reduced duplication, reusability, enterprise-wide cost minimization, overall security, comprehensive risk mitigation, and any other cross-cutting concerns) to optimize corporate business goals.
Establish the EA function scope by using the EA value proposition and EA fundamentals that have already been developed. After defining the EA function scope, refer back to these statements to ensure it accurately reflects the EA value proposition and EA fundamentals.
|
EA value proposition +EA vision statement
|
—› Influences |
Organizational coverage Architectural domains Depth Time horizon |
—› Defines |
EA function scope |
The team assembled to create the EA strategy will be defined as the “EA strategy creation team” in this blueprint.
Using an enterprise architecture methodology is a good starting point to achieving a common understanding of what that is. Often, organizations agree to "tailor" methodologies to their needs.
The use of lean/Agile approaches will increase efficiency beyond traditional methodologies.
| Corporate Strategy “Why does our enterprise exist in the market?” |
|
| EA Strategy
“What does EA need to be and do to support the enterprise’s ability to meet its goals? What is EA’s value proposition?” |
Business & IT Operating Culture
“How does the organization’s culture and structure influence the EA operating model?” |
| EA Operating Model
How does EA need to operate on a daily basis to deliver the value proposition?” |
|
(Source: The Center for Organizational Design)
| Vision, goals, and aspirations as well internal and external pressures | ||
|
Business current state
|
Enterprise Architecture |
IT current state
|
|
Business target state
|
IT target state
|
|
| Complex, overlapping, contradictory world of humans vs. logical binary world of IT | ||
| EA is a planning tool to help achieve the corporate business goals | ||
Business architecture is the cornerstone that sets the foundation for all other architectural domains: security, data, application, and technology.
“An enterprise architecture practice is both difficult and costly to set up. It is normally built around a process of peer review and involves the time and talent of the strategic technical leadership of an enterprise.” (The Open Group Architecture Framework, 2018)
The primary question during the design of the EA operating model is how to integrate the EA function with the rest of the business.
If the EA practice functions on its own, you end up with ivory tower syndrome and a dictatorship.
If you totally embed the EA function within business units it will become siloed with no enterprise value.
Organizations need to balance consistency at the enterprise level with creativity from the grass roots.
Decisions at the enterprise level apply across multiple programs/portfolios/solutions and represent the guardrails set for all to play within.
Larger organizations with multiple domains/divisions or business units will need to decide which architecture functions will be centralized and which, if any, will be decentralized as they plan to scope their EA program. What are the core functions to be centralized for the EA to deliver the greatest benefits?
Typically, we see a need to have a centralized repository of reusable assets and standards across the organization, while other approaches/standards can operate locally.
Being able to answer the deceptively simple question “How am I doing?” requires traceability to and from the business goals to be achieved all the way to applications, to infrastructure, and ultimately, to the funded initiatives (portfolios, programs, projects, etc.).
Corporate Business Goals
|
EA Contributions
|
Measurements
|
Organizations must create clear and smart KPIs (key performance indicators) across the board.
In the absence of a corporate strategy, enterprise architecture is missing its North Star.
However, enterprise architects can partner with the business strategists to build the needed vision.
According to the Scaled Agile Framework, three of the most applicable principles for the architectural professions refer to the following:
|
Common DomainsBusiness Architecture Information Architecture Application Architecture Technical Architecture Integration Architecture Security Architecture Others |
All architects are boots on the ground and play in the solutioning space. What differs is their decisions’ impact (the enterprise architect’s decisions affects all domains and solutions).
SAFe definitions of the Enterprise/Solution and System Architect roles can be found here.
The role of the Enterprise Architect is detailed here.
(Adapted from Disciplined Agile)
There are both formal and informal collaborations between enterprise architects and solution architects across the enterprise.
Enterprise architects should collaborate with solutions architects to create the best solutions at the enterprise level and to provide guidance across the board.
According to Scale Agile Framework 5 for Lean Enterprises:
Please check the SAFe Scaled Agile site for detailed information on the approach.
A clear commitment for architects to achieve and support agility is needed. Architects should not be in an ivory tower; they should be hands on and engaged in all relevant Agile ceremonies, like the pre- and post-program increment (PI) planning, etc.
Architect syncs are also required to ensure the needed collaboration.
Architect participation in Agile ceremonies, according to SAFe:
Architecting for scale, modularity, and extensibility is key for the architecture to adapt to changing conditions and evolve.
Proactively address NFRs; architect for performance and security.
Continuously refine the solution intent.
For large solutions, longer foundational architectural runways are needed.
Having an intentional continuous improvement/continuous development (CI/CD) pipeline to continuously release, test, and monitor is key to evolving large and complex systems.
Architects need to help make some fundamental decisions, e.g. help define the environment that best supports continuous innovation or exploration and continuous integration, deployment, and delivery.
The enterprise architecture statement relative to agility specifies the architects’ responsibilities as well as the Agile protocols they will participate in. This statement will guide every architect’s participation in planning meetings, pre- and post-PI, various syncs, etc. Use simple and concise terminology; speak loudly and clearly.
Strong EA statement relative to agility has the following characteristics:
Sample EA statement relative to agility
Below is a sample of connecting keywords to form an enterprise architect role statement, relative to agility.
Optimize – We collaborate with the business to analyze and optimize business capabilities and business processes to enable the agile and efficient attainment of [Company name] business objectives.
Transform – We support IT-enabled business transformation programs by building and maintaining a shared vision of the future-state enterprise and consistently communicating it to stakeholders.
Innovate – We identify and develop new and creative opportunities for IT to enable the business. We communicate the art of the possible to the business.
Defining and implementing – We engage with project teams early and guide solution design and selection to ensure alignment to the target-state enterprise architecture and provide guidance and accelerators.
Target enterprise structure in an agile way – We analyze business needs and priorities and assess the current state of the enterprise. We build and maintain the target enterprise architecture blueprints that define:
| Traditional Enterprise Architecture | Next-Generation Enterprise Architecture |
| Scope: Technology focused | Business transformation (scope includes both business and technology) |
| Bottom up | Top down |
| Inside out | Outside In |
| Point to point; difficult to change | Expandable, extensible, evolvable |
| Control-based: Governance intensive; often over-centralized | Guidance-based: Collaboration and partnership-driven based on accepted guardrails |
| Big up-front planning | Incremental/dynamic planning; frequent changes |
| Functional siloes and isolated projects, programs, and portfolios | Enterprise-driven outcome optimization (across value streams) |
The role of the architecture in Lean (Agile) approaches is to set up the needed guardrails and ensure a safe environment where everyone can be effective and creative.
Phase 1
| Phase 2
| ||
Phase 3
| Phase 4
|
An understanding of your organization’s EA needs.
Create the Value Proposition
| Step 2.1 | Step 2.2 |
Creating an EA value proposition should be the first step to realizing a healthy EA function. The EA value proposition demonstrates to organizational stakeholders the importance of EA in helping to realize their needs.
Five steps towards the successful articulation of EA value proposition:
EA can deliver many benefits to an organization. To increase the likelihood of success, each EA group needs to commit to delivering value to their organization based on the current operating environment and the desired direction of the enterprise. An EA value proposition will articulate the group’s promises of value to the enterprise.
All stakeholders need to know how the EA function can help them. Provide the stakeholders with an understanding of the EA strategy’s impact on the business by involving them.
A stakeholder map can be a powerful tool to help identify and prioritize stakeholders. A stakeholder map is a visual sketch of how various stakeholders interact with your organization, with each other, and with external audience segments.
“Stakeholder management is critical to the success of every project in every organization I have ever worked with. By engaging the right people in the right way in your project, you can make a big difference to its success…and to your career.” (Rachel Thompson, MindTools)
Input: Expertise from the EA strategy creation team
Output: An identified and prioritized set of stakeholders for the EA function to target
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Download the Stakeholder Power Map Template for more detailed instructions on completing this activity.
All stakeholders will have a set of needs they would like to address. Take those needs and translate them into business and technology drivers. Drivers help clearly articulate to stakeholders, and the EA function, the stakeholder needs to be addressed.
Business DriverBusiness drivers are internal or external business conditions, changing business capabilities, and changing market trends that impact the way EA operates and provides value to the enterprise. Examples:Ensure corporate compliance with legislation pertaining to data and security (e.g. regulated oil fields). Enable the automation and digitization of internal processes and services to business stakeholders. |
Technology DriverTechnology drivers are internal or external technology conditions or factors that are not within the control of the EA group that impact the way that the EA group operates and provides value to the enterprise. Examples:Establish standards and policies for enabling the organization to take advantage of cloud and mobile technologies. Reduce the frequency of shadow IT by lowering the propensity to make business–technology decisions in isolation. |
Review information sources, then analyze them to derive business and technology drivers. Information sources are not targeted towards EA stakeholders. Analyze the information sources to create drivers that are relevant to EA stakeholders.
| Information Sources | Drivers (Examples) | |||
|
PESTLE Analysis Strategy Documents Stakeholder Interviews SWOT Analysis |
—› |
Analysis |
—› |
Help the organization align technology investments with corporate strategy Ensure corporate compliance with legislation. Increase the organization’s speed to market. |
| Business and Technology Needs
By examining information sources, the EA team will come across a set of business and technology needs. Through analysis, these needs can be synthesized into drivers. |
||||
PESTLE examines six perspectives for external factors that may impact business and technology needs. Below are prompting questions to facilitate a PESTLE analysis working session.
| Political |
|
|
Economic |
| Social |
|
|
Technological |
| Legal |
|
|
Environmental |
2 hours
Input: Expertise from EA strategy creation team
Output: Identified set of business and technology needs from PESTLE
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Download the PESTLE Analysis Template to assist with completing this activity.
Some organizations (and business units) create an authoritative strategy document. These documents contain corporate aspirations and outline initiatives, reorganizations, and shifts in strategy. From these documents, a set of business and technology needs can be generated.
Overt Statements
|
Turn these statements to business and technology needs by:Asking the following:
|
Covert Statements
|
2 hours
Input: Strategic documents in the organization
Output: Identified set of business and technology needs from documents
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Begin the identification process of business and technology needs from strategic documents with the following steps:
In this interview process, you will be asking EA stakeholders questions that uncover their business and technology needs. You will also be able to ask follow-up questions to get a better understanding of abstract or complex concepts from the strategy document review and PESTLE analysis.
4-8 hours
Input: Expertise from the EA stakeholders
Output: Business and technology needs for EA stakeholders
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team, Identified EA stakeholders
A value proposition document that ties the value of the EA function to stakeholder needs.
Create the EA Value Proposition
| Step 2.1 | Step 2.2 |
|
There are several key attributes that a driver should have. Driver Key Attributes
|
“The greatest impact of enterprise architecture is the strategic impact. Put the mission and the needs of the organization first.” (Matthew Kern, Clear Government Solutions)
3 hours
Input: Expertise from EA strategy creation team
Output: A set of business and technology drivers
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team, EA stakeholders
Meet with the EA strategy creation team and follow the steps below to begin the process of synthesizing the business and technology needs into drivers.
Download the EA Value Proposition Template to record your findings in this activity.
A pain is an obstacle that business stakeholders will face when attempting to address business and technology drivers. Identify the pains associated with each driver so that EA’s contributions can be linked to resolving obstacles to address business needs.
Business and Technology Drivers |
› |
Pains |
| Created by assessing information sources. | A sentence that states the nature of the pain and how the pain stops the organization from addressing the drivers. | |
Examples:
|
Examples:
|
2 hours
Input: Expertise from EA strategy creation team and EA stakeholders
Output: An associated pain that obstructs each identified driver
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team, EA stakeholders
Call a meeting with the EA strategy creation team and any available stakeholders to identify the pains that obstruct addressing the business and technology drivers.
Take each driver and ask the questions below to the EA strategy creation team and to any EA stakeholders who are available. Record the answers to identify the pains when realizing the drivers.
Take the recorded answers and follow the steps below to create the pain statements:
Download the EA Value Proposition Template to record your findings in this activity.
Set the foundations for the value proposition by brainstorming the EA contributions that can alleviate the pains.
Business and technology drivers produce:Pains |
—› |
EA contributions produce:Value by alleviating pains |
PainsObstructions to addressing business and technology drivers. Stakeholders will face these pains. Examples
|
EA contributionsActivities the EA function can perform to help alleviate the pains. Demonstrates the contributions the EA function can make to business value. Examples:
|
| EA contribution category | EA contribution details |
| Define business capabilities and processes | As-is and target business capabilities and processes are documented and understood by both IT and the business. |
| Design information flows and services | Information flows and services effectively support business capabilities and processes. |
| Analyze gaps and identify project opportunities | Create informed project identification, scope definition, and project portfolio management. |
| Optimize technology assets | Greater homogeneity and interoperability between tangible and intangible technology assets. |
| Create and maintain technology standards | Decrease development, integration, and support efforts. Reduce complexity and improve interoperability. |
| Rationalize technology assets | Tangible and intangible technology assets are rationalized to adequately and efficiently support information flows and services. |
2 hours
Input: Expertise from EA strategy creation team
Output: EA contributions that addresses the pains that were identified
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Gather with the EA strategy creation team, take each pain, then ask and record the answers to the questions below to identify the EA contributions that would solve the pains:
Answers to the questions above will generate a list of activities EA can do to help alleviate the pains. Use the following steps to complete this activity:
Download the EA Value Proposition Template to record your findings in this activity.
2 hours
Input: Expertise from EA strategy creation team and EA stakeholders
Output: Promises of value for each business and technology driver
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team, EA stakeholders
Now that the EA contributions have been identified, identify the promises of value to articulate the value proposition.
Take each driver, then ask and record the answers to the questions below to identify the promises of value when realizing the drivers:
Take the recorded answers and follow the steps below to create the promises of value.
Download the EA Value Proposition Template to record your findings in this activity.
Phase 1
| Phase 2
| ||
Phase 3
| Phase 4
|
| Step 3.1 | Step 3.2 |
EA fundamentals include a vision statement, a mission statement, goals and objectives, and principles. They are a set of documented statements that guide the EA function. The fundamentals guide the EA function in terms of its strategy and decision making.
| EA vision statement | EA mission statement |
EA fundamentals |
|
| EA goals and objectives | EA principles |
Treat the critical elements of the EA group the same way as you would a business. Create a directional foundation for EA and define the vision, mission, goals, principles, and scope necessary to deliver on the established value proposition.
The enterprise architecture vision statement communicates a desired future state of the EA function. The statement is expressed in the present tense. It seeks to articulate the desired role of the EA function and how the EA function will be perceived.
The enterprise architecture mission statement specifies the team’s purpose or “reason of being.” The mission should guide each day’s activities and decisions. The mission statements use simple and concise terminology, speak loudly and clearly, and generate enthusiasm for the organization.
The process for constructing the enterprise architecture vision statement and enterprise architecture mission statement is articulated below.
| Promises of value | Derive keywords | Construct draft statements | Reference test criteria | Finalize statements |
| Derive the a set of keywords from the promises of value to accurately capture their essence. | Create the initial statement using the keywords. | Check the initial statement against a set of test criteria to ensure their quality. | Finalize the statement after referencing the initial statement against the test criteria. |
Develop keywords by summarizing the promises of value that were derived from drivers into one word that will take on the essence of the promise. See examples below:
| Business and technology drivers | Promises of value | Keywords |
| Help the organization align investments with the corporate strategy and departmental priorities. | Increase the number of investments that have a direct tie to corporate strategy. | Business |
| Support the rapid growth and development of the company through fiscal planning, project planning, and technology sustainability. | Ensure budgets and projects are delivered on time with the assistance of technology. | IT-Enabled |
| Reduce the duplication and work effort to build and deploy technology solutions across the entire organization. | Aim to reduce the number of redundant applications in the organization to streamline processes and save costs. | Catalyst |
| Improve the organization’s technology responsiveness and increase speed to market. | Reduce the number of days required in the SDLC for all core business support projects. | Value delivery |
Ensure the sentence is cohesive and captures additional value outside of the keywords. The statement as a whole should be greater than the sum of the parts. Expand upon the meaning of the words, if necessary, to communicate the value. Below is an example of a finished vision statement.
SampleCatalyst – We will continuously interact with the business and IT to accelerate and improve results.
IT-enabled – We will ensure the optimal use of technology in enabling business capabilities to achieve business objectives.
Business – We will be perceived as a business-focused unit that understands [Company name]’s business priorities and required business capabilities.
Value delivery – EA’s value will be recognized by both business and IT stakeholders. We will track and market EA’s contribution to business value organization-wide.
Likewise, below is a sample of connecting keywords together to form an EA mission statement:
Optimize – We collaborate with the business to analyze and optimize business capabilities and business processes to enable the agile and efficient attainment of [Company name] business objectives.
Transform – We support IT-enabled business transformation programs by building and maintaining a shared vision of the future-state enterprise and consistently communicating it to stakeholders.
Innovate – We identify and develop new and creative opportunities for IT to enable the business. We communicate the art of the possible to the business.
Defining and implementing – We engage with project teams early and guide solution design and selection to ensure alignment to the target-state enterprise architecture.
Target enterprise structure – We analyze business needs and priorities and assess the current state of the enterprise. We build and maintain the target enterprise architecture blueprints that define:
1 hour
Input: Identified promises of value, Vision statement test criteria
Output: EA function vision statement
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Begin the creation of the EA vision statement by following the steps below:
1 hour
Input: Identified promises of value, Mission statement test criteria
Output: EA function mission statement
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Begin the creation of the EA mission statement by following the steps below:
Enterprise architecture goals define specific desired outcomes of an EA function. EA goals are important because they establish the milestones the EA function can strive toward to deliver their promises of value.
Inform EA goals by examining:Promises of value |
—› |
EA goals produce:Targets and milestones |
Promises of valueProduce EA strategic outcomes that can be classified into four categories. The four categories are:
|
EA goalsSupport the strategic outcomes. EA goals can be strategic or operational:
|
2 hours
Input: Identified promises of value
Output: EA goals
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Begin the creation of EA goals by following the steps below:
Download the EA Goals and Objectives Template to assist with completing this activity.
Below are examples of EA goals and the objectives that track their performance:
| IT performance-oriented goals | Objectives |
| Alignment of IT and business strategy |
|
| Increase in IT agility |
|
| Optimization of IT assets, resources, and capabilities |
|
2 hours
Input: Defined EA goals
Output: EA objectives linked to EA goals
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Begin the process of defining EA objectives and linking them to EA goals using the following steps:
Download the EA Goals and Objectives Template to assist with completing this activity.
Add details to the enterprise architecture objectives previously defined to increase their clarity to stakeholders.
| EA objective detail category | Description |
| Unit of measure |
|
| Calculation formula |
|
| Objective baseline, status, and target |
|
| Data collection |
|
| Reporting |
|
2 hours
Input: Defined list of EA objectives
Output: Increased detail into each defined EA objective
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Record the details of each EA objective. Use the following steps below to assist with recording the details:
Download the EA Goals and Objectives Template to assist with completing this activity.
Build the EA Fundamentals
| Step 3.1 | Step 3.2 |
The EA function scope constrains the promises of value the EA function will deliver on by taking into account factors across four dimensions. The EA function scope ensures that the EA function is not stretched beyond its current/planned means and capabilities when delivering the promised value. The four dimensions are illustrated below:
| Organizational coverage
Determine the focus of the enterprise architecture effort in terms of specific business units, functions, departments, capabilities, or geographical areas. |
Depth
Determine the appropriate level of detail to be captured, based on the intended use of the enterprise architecture and the contingent decisions to be made. |
EA Scope |
|
| Architectural Domains
Determine the EA domains (business, data, application, infrastructure, security) that are appropriate to address stakeholder concerns and architecture requirements. |
Time horizon
Determine the target-state architecture’s objective time period. |
Establish the EA function scope by using the EA value proposition and EA fundamentals that have been developed. After defining the EA function scope, refer back to these statements to ensure the EA function scope accurately reflects the EA value proposition and EA fundamentals.
|
EA value proposition +EA vision statement
|
—› Influences |
Organizational coverage Architectural domains Depth Time horizon |
—› Defines |
EA function scope |
The organizational coverage dimension of EA scope determines the focus of enterprise architecture effort in the organization. Coverage can be determined by specific business units, functions, departments, capabilities, or geographic areas. Info-Tech has typically seen two types of coverage based on the size of the organization.
Indicators: Full-time employees dedicated to manage its data and IT infrastructure. Individuals are IT generalists and may have multiple roles.
Recommended coverage: Typically, for small and medium-size businesses, the organizational coverage of architecture work is the entire enterprise. (Source: The Open Group, 2018)
Indicators: Dedicated full-time IT staff with expertise to manage specific applications or parts of the IT infrastructure.
Recommended coverage: For large enterprises, it is often necessary to develop a number of architectures focused on specific business segments and/or geographies. In this federated model, an overarching enterprise architecture should be established to ensure interoperability and conformance to overarching EA principles. (Source: DCIG, 2011)
Enterprise architecture objectives are specific metrics that help measure and monitor progress towards achieving an EA goal. Objectives are SMART.
| EA goals | —› | EA objectives |
|
|
Download the EA Goals and Objectives Template to see examples between the relationship of EA goals to objectives.
| Corporate Business Goals | Measurements | |
|
|
2 hours
Input: EA value proposition, Previously defined EA fundamentals
Output: Organizational coverage dimension of EA scope defined
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Define the organizational coverage of the EA function scope using the following steps below:
A complete enterprise architecture should address all five architectural domains. The five architectural domains are business, data, application, infrastructure, and security.
| Enterprise Architecture | ||||
| —› | Data Architecture | |||
| Business Architecture | —› | Infrastructure Architecture | ||
| Security Architecture | ||||
| —› | Application Architecture | |||
“The realities of resource and time constraints often mean there is not enough time, funding, or resources to build a top-down, all-inclusive architecture encompassing all four architecture domains. Build architecture domains with a specific purpose in mind.” (The Open Group, 2018)
Below are the definitions of different domains of enterprise architecture (Info-Tech perspective; others can be identified as well, e.g. Integration Architecture).
Business ArchitectureBusiness architecture is a means of demonstrating the business value of subsequent architecture work to key stakeholders and the return on investment to those stakeholders from supporting and participating in the subsequent work. Business architecture defines the business strategy, governance, organization, and key business processes. |
|
Data ArchitectureDescribes the structure of an organization’s logical and physical data assets and data management resources. |
Application ArchitectureProvides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization. |
Infrastructure ArchitectureRepresents the sum of hardware, software, and telecommunications-related IT capability associated with a particular enterprise. It is concerned with the synergistic operations and management of the devices in the organization. |
Security ArchitectureProvides an unified security design that addresses the necessities and potential risks involved in a certain scenario or environment. It also specifies when and where to apply security controls. |
EA scope depth defines the architectural detail for each EA domain that the organization has selected to pursue. The level of depth is broken down into four levels. The level of depth the organization decides to pursue should be consistent across the domains.
| Contextual |
|
||||
| Conceptual |
|
||||
| Logical |
|
||||
| Physical |
|
||||
| (Source: Zachman International, 2011) | Business Architecture | Data Architecture | Application Architecture | Infrastructure Architecture | Security Architecture |
The graphic below depicts examples of the key artifacts that each domain of architecture would produce at each depth level.
| Contextual | Enterprise Governance | ||||
| Conceptual | Business strategy | Business objects | Use-case models | Technology landscaping | Security policy |
| Logical | Business capabilities | Data attribution | Application integration | Network/ hardware topology | Security standards |
| Physical | Business process | Database design | Application design | Configuration management | Security configuration |
| Business Architecture | Data Architecture | Application Architecture | Infrastructure Architecture | Security Architecture | |
2 hours
Input: EA value proposition, Previously defined EA fundamentals
Output: Architectural domain and depth dimensions of EA scope defined
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Define the EA function scope for your organization using the following steps below:
It is important that the EA team’s work has an appropriate planning horizon while avoiding two extremes:
| Planning Horizon: | 1 year | 2-3 years | 5 years |
| Recommended under the following conditions: |
|
|
|
2 hours
Input: EA value proposition, Previously defined EA fundamentals
Output: Time horizon dimension of EA scope defined
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Define the EA function scope for your organization using the following steps below:
EA principles are shared, long-lasting beliefs that guide the use of IT in constructing, transforming, and operating the enterprise by informing and restricting target-state enterprise architecture design, IT investment portfolio management, solution development, and procurement decisions.
| EA value proposition | Influences —› |
EA Principles | Guide and inform —› |
Decisions on the Use of IT | Direct and control ‹— |
Specific Domain Policies |
| ‹——————— What decisions should be made? |
————— | ————— | —————
How should decisions be made? |
————— | ————— | —————————›
Who has the accountability and authority to make decisions? |
Info-Tech has identified a set of characteristics that EA principles should possess. Having these characteristics ensures the EA principles are relevant and followed in the organization.
| Approach focused | EA principles are focused on the approach, i.e. how the enterprise is built, transformed, and operated, as apposed to what needs to be built, which is defined by both functional and non-functional requirements. |
| Business relevant | Create EA principles specific to the organization. Tie EA principles to the organization’s priorities and strategic aspirations. |
| Long lasting | Build EA principles that will withstand the test of time. |
| Prescriptive | Inform and direct decision making with EA principles that are actionable. Avoid truisms, general statements, and observations. |
| Verifiable | If compliance can’t be verified, the principle is less likely to be followed. |
| Easily digestible | EA principles must be clearly understood by everyone in IT and by business stakeholders. EA principles aren’t a secret manuscript of the EA team. EA principles should be succinct; wordy principles are hard to understand and remember. |
| Followed | Successful EA principles represent a collection of beliefs shared among enterprise stakeholders. EA principles must be continuously “preached” to all stakeholders to achieve and maintain buy-in.
In organizations where formal policy enforcement works well, EA principles should be enforced through appropriate governance processes. |
| 1. Enterprise value focus | We aim to provide maximum long-term benefits to the enterprise as a whole while optimizing total costs of ownership and risks. |
| 2. Fit for purpose | We maintain capability levels and create solutions that are fit for purpose without over-engineering them. |
| 3. Simplicity | We choose the simplest solutions and aim to reduce operational complexity of the enterprise. |
| 4. Reuse › buy › build | We maximize reuse of existing assets. If we can’t reuse, we procure externally. As a last resort, we build custom solutions. |
| 5. Managed data | We handle data creation, modification, and use enterprise-wide in compliance with our data governance policy. |
| 6. Controlled technical diversity | We control the variety of technology platforms we use. |
| 7. Managed security | We manage security enterprise-wide in compliance with our security governance policy. |
| 8. Compliance to laws and regulations | We operate in compliance with all applicable laws and regulations. |
| 9. Innovation | We seek innovative ways to use technology for business advantage. |
| 10. Customer centricity | We deliver best experiences to our customers with our services and products. |
2 hours
Input: Info-Tech’s ten universal EA principles, Identified promises of value
Output: A defined set of EA principles for your organization
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Create a set of EA principles for your organization using the steps below:
Download the EA Principles Template – EA Strategy to document this step.
After defining the set of EA principles, ensure they are all expanded upon with a rationale and implications. The rationale and implications ensure principles are more likely to be followed because they communicate why the principles are important and how they are to be used.
| Name |
|
| Statement |
|
| Rationale |
|
| Implications |
|
2 hours
Input: Identified set of EA principles
Output: EA principles that have rationale and implications
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Add the rationale and implication of each EA principle that your organization has selected using the following steps:
Download the EA Principles Template – EA Strategy to document this step.
1-2 hours
Input: Defined set of EA principles
Output: EA principles are successfully operationalized
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Begin to operationalize the EA principles by reviewing the proposed principles with business and technology leadership to secure their approval.
After operationalizing the EA principles for your organization, the organization can now use those principles to guide and inform its IT investment decisions. Below is an example of a scenario where EA principles were used to guide and inform an IT investment decision.
Organization wants to provision an application but it needs to decide how to do so, and it considers the relevant EA principles:
The organization has decided to go with a specialized vendor, even though it normally prefers to reuse existing components. The vendor has experience in this domain, understands the data security implications, and can help the organization mitigate risk. Lastly, the vendor is known for providing new solutions on a regular basis and is a market leader, making it more likely to provide the organization with innovative solutions.
As an enterprise architecture function starting from ground zero, the organization did not have the EA fundamentals in place to guide the EA function. Further, the organization also did not possess an EA function scope to define the boundaries of the EA function.
Due to the lack of EA scope, the EA function did not know which part of the organization to provide contributions toward. A lack of EA fundamentals caused confusion regarding the future direction of the EA function.
Info-Tech worked with the EA team to define the different components of the EA fundamentals. This included EA vision and mission statements, EA goals and objectives, and EA principles.
Additionally, Info-Tech worked with the EA team to define the EA function scope.
These EA strategy components were created by examining the needs of the business. The components were aligned with the identified needs of the EA stakeholders.
The defined EA function scope helped set out the responsibilities of the enterprise architecture function to the organization.
The EA vision and mission statements and EA goals and objectives were used to guide the direction of the EA function. These fundamentals helped the EA function improve its maturity and deliver on its promises.
The EA principles were used in IT review boards to guide the decisions on IT investments in the organization.
1 hour
Input: Existing methodologies
Output: Decisions about need of agility, ceremonies, and protocols to be used
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Add the rationale and implication of adopting an Agile methodology and/or a combination with a traditional methodology.
Phase 1
| Phase 2
| ||
Phase 3
| Phase 4
|
Design the EA Services
| Step 3.1 | Step 3.2 |
Enterprise architecture services are a set of activities the enterprise architecture function provides for the organization. EA services are important because the services themselves provide a set of benefits for the organization.
Viewing the EA function from a service perspective resolves the following pains:
Previously identified EA contributions can be linked to EA services, which helps the EA function identify a set of EA services that are important to business stakeholders. Further, linking the EA contributions to EA services can define for the EA function the services they need to provide.
2 hours
Input: Previously identified EA contributions from the EA value proposition
Output: A set of EA services selected for the organization from Info-Tech’s defined set of EA services
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Begin the selection of EA services relevant to your organization by following the steps below:
Download the EA Service Planning Tool to assist with this activity.
2 hours
Input: Expertise from the EA strategy creation team, Previously defined EA contributions
Output: A defined set of EA services outside the list Info-Tech has recommended
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Identify if services outside of the recommended list in the EA Service Planning Tool are relevant to your organization by using the steps below:
Download the EA Service Planning Tool to assist with this activity.
The EA service catalog is an important communicator to the business. It shifts the technology-oriented view of EA to services that show direct benefit to the business. It is a tool that communicates and provides clarity to the business about the EA services that are available and how those services can assist them.
| Define the services to show value | Define the service catalog to show how to use those services |
Already defined
|
Need to define
|
The EA group must provide the organization with a list of services it will provide to demonstrate value. This will help the team manage expectations and the workload while giving organizational stakeholders a clear understanding of how to engage EA and what lies outside of EA’s involvement.
4 hours
Input: Expertise from the EA strategy creation team
Output: Service details for each EA service in your organization
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Complete the details for each relevant EA service in the EA Service Planning Tool by using the following steps:
Download the EA Service Planning Tool to assist with this activity.
Design the EA Services
| Step 4.1 | Step 4.2 |
For the EA strategy to be successfully executed, it must be approved by the EA stakeholders. Securing their approval will increase the likelihood of success in the execution of the EA operating model.
| Outputs that make up the EA strategy | —› | Present outputs to EA strategy stakeholders |
|
|
1 hour
Input: Completed EA Function Strategy Template, Expertise from EA strategy creation team
Output: Approval of the EA strategy
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team, Key EA stakeholders
Use the following steps to assist with securing approval for your organization’s EA strategy:
Use the EA Function Strategy Template to assist with this activity.
3 hours
Input: Expertise from EA strategy creation team
Output: Service details for each EA service in your organization
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Map EA contributions/services to the goals of the organization.
Download the EA Service Planning Tool to assist with this activity.
1 hour
Input: Expertise from EA strategy creation team
Output: Defined KPIs (SMART)
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Use SMART key performance indicators (KPIs) to measure EA contributions vis-à-vis business goals.
| Corporate Business Goals | EA Contributions | Measurements |
|
|
|
The oil and gas corporation faced a great challenge in communicating the role of enterprise architecture to the organization. Although it has the mandate from the CIO to create the EA function, there was no function in existence. Thus, few people in the organization understood EA.
Because of this lack of understanding, the EA function was often undermined. The EA function was seen as an order taker that provided some services to the organization.
First, Info-Tech worked with the enterprise architecture team to define the EA stakeholders in the organization.
Second, Info-Tech interviewed those stakeholders to identify their needs. The needs were analyzed and pains that would obstruct addressing those needs were identified.
Lastly, Info-Tech worked with the team to identify common EA contributions that would solve those pains.
Through this process, Info-Tech helped the team at the oil and gas company create a document that could communicate the value of EA. Specifically, the document could articulate the issues obstructing each stakeholder from achieving their needs and how enterprise architecture could solve them.
With this value proposition, EA was able to demonstrate value to important stakeholders and set itself up for success in its future endeavors.
As a brand new enterprise architecture function, the EA function at the oil and gas corporation did not have a set of defined EA services. Because of this lack of EA services, the organization did not know what contributions EA could provide.
Further, without the definition of EA services, the EA function did not set out explicit expectations to the business. This caused expectations from the business to be different from those of the EA function, resulting in friction.
Info-Tech worked with the EA function at the oil and gas corporation to define a set of EA services the function could provide.
The Info-Tech team, along with the organization, assessed the business and technology needs of the stakeholder. Those needs acted as the basis for the EA function to create their initial services.
Additionally, Info-Tech worked with the team to define the service details (e.g. service benefits, service requestor, service provider) to communicate how to provide services to the business.
The defined EA services led the EA function to communicate what it could provide for the business. As well, the defined services clarified the level of expectation for the business.
The EA team was able to successfully service the business on future projects, adding value through their expertise and knowledge of the organization’s systems. Because of the demonstrated value, EA has been given greater responsibility throughout the organization.
1 hour
Input: Expertise from EA strategy creation team
Output: Participation in Agile Pre- and Post-PI, Architect Syncs, etc.
Materials: Note-taking materials, Whiteboard or flip chart, markers
Participants: EA strategy creation team
Document the involvement of the enterprise architect in your organization’s Agile ceremonies.
Note: Roles and responsibilities can be further defined as part of the Agile Enterprise Operating Model.
The enterprise architecture role relative to agility specifies the architecture roles as well as the agile protocols they will participate in.
This statement will guide every architect’s participation in planning meetings, pre- and post-PI, syncs, etc. Use simple and concise terminology; speak loudly and clearly.
A strong EA role statement relative to agility has the following characteristics:
Sample EA mission relative to agility
Likewise, below is a sample of connecting keywords together to form an enterprise architect role statement, relative to agility.
Optimize – We collaborate with the business to analyze and optimize business capabilities and business processes to enable the agile and efficient attainment of [Company name] business objectives.
Transform – We support IT-enabled business transformation programs by building and maintaining a shared vision of the future-state enterprise and consistently communicating it to stakeholders.
Innovate – We identify and develop new and creative opportunities for IT to enable the business. We communicate the art of the possible to the business.
Defining and implementing – We engage with project teams early and guide solution design and selection to ensure alignment to the target-state enterprise architecture and provide guidance as well as accelerators.
Target enterprise structure in an agile way – We analyze business needs and priorities and assess the current state of the enterprise. We build and maintain the target enterprise architecture blueprints that define:
Once approved, move on to Info-Tech’s Define an EA Operating Model blueprint to begin executing on the EA strategy.
This blueprint focuses on setting up an enterprise architecture function, with the goal of maximizing the likelihood of EA success. The blueprint puts into place the components that will align the EA function with the needs of the stakeholders, guide the decision making of the EA function, and define the services EA can provide to the organization.
An EA operating model helps you design and organize the EA function, ensuring adherence to architectural standards and delivery of EA services. This blueprint acts on the EA strategy by creating methods to engage, govern, and develop architecture as a part of the larger organization.
|
Milena Litoiu
Senior Director Research and Advisory, Enterprise Architecture
|
|
Lan Nguyen
IT Executive, Mentor, Managing Partner at CIOs Beyond Borders Group
|
|
Dirk Coetsee
Director Research and Advisory, Enterprise Architecture, Data & Analytics
|
|
Andy Neill
AVP, Enterprise Architecture, Data and Analytics
|
|
Wayne Filin-Matthews
Chief Enterprise Architect, ICMG Winner of Global Chief Enterprise Architect of the Year 2019
|
|
Graham Smith
Experienced lead Enterprise Architect and Independent Consultant
|
Thanks also go to all experts who contributed to previous versions of this document:
Additional interviews were conducted but are not listed due to privacy and confidentiality requirements.
“Agile Manifesto for Software Development,” Ward Cunningham, 2001. Accessed July 2021.
“ArchiMate 3.1 Specification.” The Open Group, n.d. Accessed July 2021.
“Are Your IT Strategy and Business Strategy Aligned?” 5Q Partners, 8 Jan. 2015. Accessed Oct. 2016.
Bowen, Fillmore. “How agile companies create and sustain high ROI.” IBM. Accessed Oct. 2016.
Burns, Peter, et al. Building Value through Enterprise Architecture: A Global Study. Booz & Co. 2009. Web. Nov. 2016.
“Demonstrating the Value of Enterprise Architecture in Delivering Business Capabilities.” Cisco, 2008. Web. Oct. 2016.
“Disciplined Agile.” Disciplined Agile Consortium, n.d. Web.
Fowler, Martin. “Building Effective software.” MartinFowler.com. Accessed July 2021.
Fowler, Martin. “Agile Software Guide.” MartinFowler.com, 1 Aug. 2019.
Accessed July 2021.Haughey, Duncan. “SMART Goals.” Project Smart, 2014. Accessed July 2021.
Kern, Matthew. “20 Enterprise Architecture Practices.” LinkedIn, 3 March 2016. Accessed Nov. 2016.
Lahanas, Stephen. “Infrastructure Architecture, Defined.” IT Architecture Journal, Sept. 2014. Accessed July 2021.
Lean IX website, Accessed July 2021.
Litoiu, Milena. Course material from Information Technology 2690: Foundations of Enterprise Architecture, 2021, University of Toronto.
Mocker, M., J.W. Ross, and C.M. Beath. “How Companies Use Digital Technologies to Enhance Customer Findings.” MIT CISR Working Paper No. 434, Feb. 2019. Qtd in Mayor, Tracy. “MIT expert recaps 30-plus years of enterprise architecture.” MIT Sloan, 10 Aug. 2020. Web.
“Open Agile ArchitectureTM.” The Open Group, 2020. Accessed July 2021.
“Organizational Design Framework – The Transformation Model.” The Center for Organizational Design, n.d. Accessed 1 Aug. 2020.
Ross, Jeanne W. et al. Enterprise Architecture as Strategy: Creating a Foundation for Business Execution. Harvard Business School Press, 2006.
Rouse, Margaret. “Enterprise Architecture (EA).” SearchCIO, June 2007. Accessed Nov. 2016.
“SAFe 5 for Lean Enterprises.” Scaled Agile Framework, Scaled Agile, Inc. Accessed 2021.
“Security Architecture.” Technopedia, updated 20 Dec. 2016. Accessed July 2021.
“Software Engineering Institute.” Carnegie Mellon University, n.d. Web.
“TOGAF 9.1.” The Open Group, 2011. Accessed Oct. 2016.
“TOGAF 9.2.” The Open Group, 2018. Accessed July 2021.
Thompson, Rachel. “Stakeholder Analysis: Winning Support for Your Projects.” MindTools, n.d. Accessed July 2021.
Wendt, Jerome M. “Redefining ‘SMB’, ‘SME’ and ‘Large Enterprise.’” DCIG, 25 Mar. 2011. Accessed July 2021.
Wilkinson, Jim. “Business Drivers.” The Strategic CFO, 23 July 2013. Accessed July 2021.
Zachman, John. “Conceptual, Logical, Physical: It is Simple.” Zachman International, 2011. Accessed July 2021.