Get Instant Access
to This Blueprint

Infrastructure Operations icon

Document Your Cloud Strategy

Get ready for the cloudy future with a consistent, proven strategy.

Despite the universally agreed-upon benefit of formulating a coherent strategy, several obstacles make execution difficult:

  • Inconsistent understanding of what the cloud means
  • Inability to come to a consensus on key decisions
  • Ungoverned decision-making
  • Unclear understanding of cloud roles and responsibilities

Our Advice

Critical Insight

A cloud strategy might seem like a big project, but it’s just a series of smaller conversations. The methodology presented here is designed to facilitate those conversations, using a curated list of topics, prompts, participant lists, and sample outcomes. We have divided the strategy into four key areas:

  • Vision and alignment
  • People
  • Governance
  • Technology

Impact and Result

  • A shared understanding of what is necessary to succeed in the cloud
  • An end to ad hoc deployments that solve small problems and create larger ones
  • A unified approach and set of principles that apply to governance, architecture, integration, skills, and roles (and much, much more).

Document Your Cloud Strategy Research & Tools

1. Document Your Cloud Strategy – a phased guide to identifying, validating, and recording the steps you’ll take, the processes you’ll leverage, and the governance you’ll deploy to succeed in the cloud.

This storyboard comprises four phases, covering mission and vision, people, governance, and technology, and how each of these areas requires forethought when migrating to the cloud.

2. Cloud Strategy Document Template – a template that allows you to record the results of the cloud strategy exercise in a clear, readable way.

Each section of Document Your Cloud Strategy corresponds to a section in the document template. Once you’ve completed each exercise, you can record your results in the document template, leaving you with an artifact you can share with stakeholders.

Member Testimonials

After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve. See our top member experiences for this blueprint and what our clients have to say.


Overall Impact


Average $ Saved


Average Days Saved




$ Saved

Days Saved

State of Kansas Human Services





Clarity of presenter (Jeremy), knowledge of presenter and InfoTech Counselors (Jerry and Basem). Ability to present the content, manage the overal... Read More

State of South Dakota Bureau of Information and Telecommunications

Guided Implementation




Good technical and process grounding was provided. The only thing that would have helped was to slow down in the first few minutes to do a check i... Read More

The Foundation for Innovative New Diagnostics

Guided Implementation




Nabeel is very experienced and takes his time to take me through the steps of the process with real-life examples. Beyond the engagement, his insig... Read More

Community Health Choice, Inc.





The overall experience was valuable. Jeremy did a great job of providing the team guidance, keeping us on track, redirecting to keep on track etc.... Read More

Fidelity Investments Canada ULC





Jeremy was an excellent moderator, and tactfully navigated fine line between enabling conversations and input from all of our team members, and sha... Read More

Langara College

Guided Implementation




There is always useful information to be found but it takes a lot of time to sieve through the information to make it your work for the organization.

Synergi Partners

Guided Implementation




University of Kansas Hospital Authority

Guided Implementation




Great insight and optimism that the workshop discussed can help us.

Spark Therapeutics, Inc.





USAble Mutual Insurance Co. dba Arkansas Blue Cross and Blue Shield





The team said Day 4 session was very good, good facilitation for discussions, very engaging and created interaction. On breakouts the teams felt r... Read More

Renown Health

Guided Implementation




Trinidad and Tobago Unit Trust Corporation





The workshop was excellent. A bit more details/ guidance was expected to be be included in the Strategy Document, and there were some challenges in... Read More

Deltec Bank & Trust Limited





I would the resources provided from InfoTech were very knowledgeable and I thoroughly enjoyed and appreciated the sessions and information shared.

Workshop: Document Your Cloud 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.

Module 1: Document Your Vision and Alignment

The Purpose

  • Understand and document your cloud vision and its alignment with your other strategic priorities.

Key Benefits Achieved

  • A complete understanding of your strategy, vision, alignment, and a list of success metrics that will help you find your way.




Record your cloud mission and vision.


Document your cloud strategy’s alignment with other strategic plans.


Record your cloud guiding principles.

  • Documented strategy, vision, and alignment.
  • Defined success metrics.

Module 2: Record Your People Strategy

The Purpose

  • Define how people, skills, and roles will contribute to the broader cloud strategy.

Key Benefits Achieved

  • Sections of the strategy that highlight skills, roles, culture, adoption, and the creation of a governance body.




Outline your skills and roles strategy.


Document your approach to culture and adoption


Create a cloud governing body.

  • Documented people strategy.

Module 3: Document Governance Principles

The Purpose

  • This section facilitates governance in the cloud, developing principles that apply to architecture, integration, finance management, and more.

Key Benefits Achieved

  • Sections of the strategy that define governance principles.




Conduct discussion on architecture.


Conduct discussion on integration and interoperability.


Conduct discussion on operations management.


Conduct discussion on cloud portfolio management.


Conduct discussion on cloud vendor management.


Conduct discussion on finance management.


Conduct discussion on security.


Conduct discussion on data controls.

  • Documented cloud governance strategy.

Module 4: Formalize Your Technology Strategy

The Purpose

  • Creation of a formal cloud strategy relating to technology around provisioning, monitoring, and migration.

Key Benefits Achieved

  • Completed strategy sections of the document that cover technology areas.




Formalize organizational approach to monitoring.


Document provisioning process.


Outline migration processes and procedures.

  • Documented cloud technology strategy.

Document Your Cloud Strategy

Get ready for the cloudy future with a consistent, proven strategy.

Analyst perspective

Any approach is better than no approach

The image contains a picture of Jeremy Roberts

Moving to the cloud is a big, scary transition, like moving from gas-powered to electric cars, or from cable to streaming, or even from the office to working from home. There are some undeniable benefits, but we must reorient our lives a bit to accommodate those changes, and the results aren’t always one-for-one. A strategy helps you make decisions about your future direction and how you should respond to changes and challenges. In Document Your Cloud Strategy we hope to help you accomplish just that: clarifying your overall mission and vision (as it relates to the cloud) and helping you develop an approach to changes in technology, people management, and, of course, governance. The cloud is not a panacea. Taken on its own, it will not solve your problems. But it can be an important tool in your IT toolkit, and you should aim to make the best use of it – whatever “best” happens to mean for you.

Jeremy Roberts

Research Director, Infrastructure and Operations

Info-Tech Research Group

Executive Summary

Your Challenge

The cloud is multifaceted. It can be complicated. It can be expensive. Everyone has an opinion on the best way to proceed – and in many cases has already begun the process without bothering to get clearance from IT. The core challenge is creating a coherent strategy to facilitate your overall goals while making the best use of cloud technology, your financial resources, and your people.

Common Obstacles

Despite the universally agreed-upon benefit of formulating a coherent strategy, several obstacles make execution difficult:

  • Inconsistent understanding of what the cloud means
  • Inability to come to a consensus on key decisions
  • Ungoverned decision making
  • Unclear understanding of cloud roles and responsibilities

Info-Tech’s Approach

A cloud strategy might seem like a big project, but it’s just a series of smaller conversations. The methodology presented here is designed to facilitate those conversations, using a curated list of topics, prompts, participant lists, and sample outcomes. We have divided the strategy into four key areas:

  1. Vision and alignment
  2. People
  3. Governance
  4. Technology

The answers might be different, but the questions are the same

Every organization will approach the cloud differently, but they all need to ask the same questions: When will we use the cloud? What forms will our cloud usage take? How will we manage governance? What will we do about people? How will we incorporate new technology into our environment? The answers to these questions are as numerous as there are people to answer them, but the questions must be asked.

Your challenge

This research is designed to help organizations that are facing these challenges or looking to:

  • Ensure that the cloud strategy is complete and accurately reflects organizational goals and priorities.
  • Develop a consistent and coherent approach to adopting cloud services.
  • Design an approach to mitigate risks and challenges associated with adopting cloud services.
  • Create a shared understanding of the expected benefits of cloud services and the steps required to realize those benefits.

Grappling with a cloud strategy is a top initiative: 43% of respondents report progressing on a cloud-first strategy as a top cloud initiative.

Source: Flexera, 2021.

Definition: Cloud strategy

A document providing a systematic overview of cloud services, their appropriate use, and the steps that an organization will take to maximize value and minimize risk.

Common obstacles

These barriers make this challenge difficult to address for many organizations:

  • The cloud means different things to different people, and creating a strategy that is comprehensive enough to cover a multitude of use cases while also being written to be consumable by all stakeholders is difficult.
  • The incentives to adopt the cloud differ based on the expected benefit for the individual customer. User-led decision making and historically ungoverned deployments can make it difficult to reset expectation and align with a formal strategy.
  • Getting all the right people in a room together to agree on the key components of the strategy and the direction undertaken for each one is often difficult.

Info-Tech’s approach

Define Your Cloud Vision

Vision and alignment

  • Mission and vision
  • Alignment to other strategic plans
  • Guiding principles
  • Measuring success


  • Monitoring
  • Provisioning
  • Migration


  • Architecture
  • Integration and interoperability
  • Operations management
  • Cloud portfolio management
  • Cloud vendor management
  • Finance management
  • Security
  • Data controls


  • Skills and roles
  • Culture and adoption
  • Governing bodies

Info-Tech’s approach

Your cloud strategy will comprise the elements listed under “vision and alignment,” “technology,” “governance,” and “people.” The Info-Tech methodology involves breaking the strategy down into subcomponents and going through a three-step process for each one. Start by reviewing a standard set of questions and understanding the goal of the exercise: What do we need to know? What are some common considerations and best practices? Once you’ve had a chance to review, discuss your current state and any gaps: What has been done? What still needs to be done? Finally, outline how you plan to go forward: What are your next steps? Who needs to be involved?


  • What questions do we need to answer to complete the discussion of this strategy component? What does the decision look like?
  • What are some key terms and best practices we must understand before deciding?


  • What steps have we already taken to address this component?
  • Does anything still need to be done?
  • Is there anything we’re not sure about or need further guidance on?

Go forward

  • What are the next steps?
  • Who needs to be involved?
  • What questions still need to be asked/answered?
  • What should the document’s wording look like?

Info-Tech’s methodology for documenting your cloud strategy

1. Document your vision and alignment

2. Record your people strategy

3. Document governance principles

4. Formalize your technology strategy

Phase Steps

  1. Record your cloud mission and vision
  2. Document your cloud strategy’s alignment with other strategic plans
  3. Record your cloud guiding principles
  4. Define success
  1. Outline your skills and roles strategy
  2. Document your approach to culture and adoption
  3. Create a cloud governing body

Document official organizational positions in these governance areas:

  1. Architecture
  2. Integration and interoperability
  3. Operations management
  4. Cloud portfolio management
  5. Cloud vendor management
  6. Finance management
  7. Security
  8. Data controls
  1. Formalize organizational approach to monitoring
  2. Document provisioning process
  3. Outline migration processes and procedures

Phase Outcomes

Documented strategy: vision and alignment

Documented people strategy

Documented cloud governance strategy

Documented cloud technology strategy

Insight summary

Separate strategy from tactics

Separate strategy from tactics! A strategy requires building out the framework for ongoing decision making. It is meant to be high level and achieve a large goal. The outcome of a strategy is often a sense of commitment to the goal and better communication on the topic.

The cloud does not exist in a vacuum

Your cloud strategy flows from your cloud vision and should align with the broader IT strategy. It is also part of a pantheon of strategies and should exist harmoniously with other strategies – data, security, etc.

People problems needn’t preponderate

The cloud doesn’t have to be a great disruptor. If you handle the transition well, you can focus your people on doing more valuable work – and this is generally engaging.

Governance is a means to an end

Governing your deployment for its own sake will only frustrate your end users. Articulate the benefits users and the organization can expect to see and you’re more likely to receive the necessary buy-in.

Technology isn’t a panacea

Technology won’t solve all your problems. Technology is a force multiplier, but you will still have to design processes and train your people to fully leverage it.

Key deliverable

Cloud Strategy Document template

Inconsistency and informality are the enemies of efficiency. Capture the results of the cloud strategy generation exercises in the Cloud Strategy Document template.

The image contains a screenshot of the Cloud Strategy Document Template.
  • Record the results of the exercises undertaken as part of this blueprint in the Cloud Strategy Document template.
  • It is important to remember that not every cloud strategy will look exactly the same, but this template represents an amalgamation of best practices and cloud strategy creation honed over several years of advisory service in the space.
  • You know your audience better than anyone. If you would prefer a strategy delivered in a different way (e.g. presentation format) feel free to adapt the Cloud Vision Executive Presentation into a longer strategy presentation.
  • Emphasis is an area where you should exercise discretion as well. A cost-oriented cloud strategy, or one that prioritizes one type of cloud (e.g. SaaS) at the exclusion of others, may benefit from more focus on some areas than others, or the introduction of relevant subcategories. Include as many of these as you think will be relevant.
  • Parsimony is king – if you can distill a concept to its essence, start there. Include additional detail only as needed. You want your cloud strategy document to be read. If it’s too long or overly detailed, you’ll encounter readability issues.

Blueprint benefits

IT benefits

Business benefits

  • A consistent, well-defined approach to the cloud
  • Consensus on key strategy components, including security, architecture, and integration
  • A clear path forward on skill development and talent acquisition/retention
  • A comprehensive resource for information about the organization’s approach to key strategy components
  • Predictable access to cloud services
  • A business-aligned approach to leveraging the resources available in the cloud
  • Efficient and secure consumption of cloud resources where appropriate to do so
  • Answers to questions about the cloud and how it will be leveraged in the environment

Measure the value of this blueprint

Don’t take our word for it:

  • Document Your Cloud Strategy has been available for several years in various forms as both a workshop and as an analyst-led guided implementation.
  • After each engagement, we send a survey that asks members how they benefited from the experience. Those who have worked through Info-Tech’s cloud strategy material have given overwhelmingly positive feedback.
  • Additionally, members reported saving between 10 and 20 days and an average of $46,499.
  • Measure the value by calculating the time saved as a result of using Info-Tech’s framework vs. a home-brewed cloud strategy alternative and by comparing the overall cost of a guided implementation or workshop with the equivalent offering from another firm. We’re confident you’ll come out ahead.

8.8/10 Average reported satisfaction

13 Days Average reported time savings

$46,499 Average cost savings

Executive Brief Case Study

INDUSTRY: Pharmaceuticals

SOURCE: Info-Tech workshop

Pharmaceutical company

The unnamed pharmaceutical company that is the subject of this case study was looking to make the transition to the cloud. In the absence of a coherent strategy, the organization had a few cloud deployments with no easily discernable overall approach. Representatives of several distinct functions (legal, infrastructure, data, etc.) all had opinions on the uses and abuses of cloud services, but it had been difficult to round everyone up and have the necessary conversations. As a result, the strategy exercise had not proceeded in a speedy or well-governed way. This lack of strategic readiness presented a roadblock to moving forward with the cloud strategy and to work with the cloud implementation partner, tasked with execution.


The company engaged Info-Tech for a four-day workshop on cloud strategy documentation. Over the course of four days, participants drawn from across the organization discussed the strategic components and generated consensus statements and next steps. The team was able to formalize the cloud strategy and described the experience as saving 10 days.

Example output: Document your cloud strategy workshop exercise

The image contains an example of Document your cloud streatgy workshop exercise.

Anything in green, the team was reasonably sure they had good alignment and next steps. Those yellow flags warranted more discussion and were not ready for documentation.

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

DIY Toolkit

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

Guided Implementation

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


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

Guided Implementation

What does a typical GI on this topic look like?

Document your vision and alignment

Record your people strategy

Document governance principles

Formalize your technology strategy

Call #1: Review existing vision/strategy documentation.

Call #2: Review progress on skills, roles, and governance bodies.

Call #3: Work through integration, architecture, finance management, etc. based on reqs. (May be more than one call.)

Call #4: Discuss challenges with monitoring, provisioning, and migration as-needed.

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 1 to 3 months

Workshop Overview

Contact your account representative for more information. 1-888-670-8889

Day 1

Day 2

Day 3

Day 4

Day 5

“so what?”

Define the
IT target state

Assess the IT
current state

Bridge the gap and
create the strategy

Next steps and
wrap-up (offsite)


1.1 Introduction

1.2 Discuss cloud mission and vision

1.3 Discuss alignment with other strategic plans

1.4 Discuss guiding principles

1.5 Define success metrics

2.1 Discuss skills and roles

2.2 Review culture and adoption

2.3 Discuss a cloud governing body

2.4 Review architecture position

2.5 Discuss integration and interoperability

3.1 Discuss cloud operations management

3.2 Review cloud portfolio management

3.3 Discuss cloud vendor management

3.4 Discuss cloud finance management

3.5 Discuss cloud security

4.1 Review and formalize data controls

4.2 Design a monitoring approach

4.3 Document the workload provisioning process

4.4 Outline migration processes and procedures

5.1 Populate the Cloud Strategy Document


Formalized cloud mission and vision, along with alignment with strategic plans, guiding principles, and success metrics

Position statement on skills and roles, culture and adoption, governing bodies, architecture, and integration/interoperability

Position statements on cloud operations management, portfolio management, vendor management, finance management, and cloud security

Position statements on data controls, monitoring, provisioning, and migration

Completed Cloud Strategy Document

Phase 1

Document Your Vision and Alignment

Phase 1

Phase 2

Phase 3

Phase 4

1.1 Document your mission and vision

1.2 Document alignment to other strategic plans

1.3 Document guiding principles

1.4 Document success metrics

2.1 Define approach to skills and roles

2.2 Define approach to culture and adoption

2.3 Define cloud governing bodies

3.1 Define architecture direction

3.2 Define integration approach

3.3 Define operations management process

3.4 Define portfolio management direction

3.5 Define vendor management direction

3.6 Document finance management tactics

3.7 Define approach to cloud security

3.8 Define data controls in the cloud

4.1 Define cloud monitoring strategy

4.2 Define cloud provisioning strategy

4.3 Define cloud migration strategy

This phase will walk you through the following activities:

  1. Record your cloud mission and vision
  2. Document your cloud strategy’s alignment with other strategic plans
  3. Record your cloud guiding principles
  4. Define success

This phase has the following outcome:

  • Documented strategy: vision and alignment

Record your mission and vision

Build on the work you’ve already done

Before formally documenting your cloud strategy, you should ensure that you have a good understanding of your overall cloud vision. How do you plan to leverage the cloud? What goals are you looking to accomplish? How will you distribute your workloads between different cloud service models (SaaS, PaaS, IaaS)? What will your preferred delivery model be (public, private, hybrid)? Will you support your cloud deployment internally or use the services of various consultants or managed service providers?

The answers to these questions will inform the first section of your cloud strategy. If you haven’t put much thought into this or think you could use a deep dive on the fundamentals of your cloud vision and cloud archetypes, consider reviewing Define Your Cloud Vision, the companion blueprint to this one.

Once you understand your cloud vision and what you’re trying to accomplish with your cloud strategy, this phase will walk you through aligning the strategy with other strategic initiatives. What decisions have others made that will impact the cloud strategy (or that the cloud strategy will impact)? Who must be involved/informed? What callouts must be involved at what point? Do users have access to the appropriate strategic documentation (and would they understand it if they did)?

You must also capture some guiding principles. A strategy by its nature provides direction, helping readers understand the decisions they should make and why those decisions align with organizational interests. Creating some top-level principles is a useful exercise because those principles facilitate comprehension and ensure the strategy’s applicability.

Finally, this phase will walk you through the process of measuring success. Once you know where you’d like to go, the principles that underpin your direction, and how your cloud strategy figures into the broader strategic pantheon, you should record what success actually means. If you’re looking to save money, overall cost should be a metric you track. If the cloud is all about productivity, generate appropriate productivity metrics. If you’re looking to expand into new technology or close a datacenter, you will need to track output specific to those overall goals.

Review: mission and vision

The overall organizational mission is a key foundational element of the cloud strategy. If you don’t understand where you’re going, how can you begin the journey to get there? This section of the strategy has four key parts that you should understand and incorporate into the beginning of the strategy document. If you haven’t already, review Define Your Cloud Vision for instructions on how to generate these elements.

1. Cloud vision statement: This is a succinct encapsulation of your overall perspective on the suitability of cloud services for your environment – what you hope to accomplish. The ideal statement includes a scope (who/what does the strategy impact?), a goal (what will it accomplish?), and a key differentiator (what will make it happen?). This is an example: “[Organization] will leverage public cloud solutions and retire existing datacenter and colocation facilities. This transition will simplify infrastructure administration, support and security, while modernizing legacy infrastructure and reducing the need for additional capital expenditure.” You might also consider reviewing your overall cloud archetype (next slide) and including the output of that exercise in the document

2. Service model decision framework: Services can be provided as software as a service (SaaS), platform as a service (PaaS), infrastructure as a service (IaaS), or they can be colocated or remain on premises. Not all cloud service models serve the same purpose or provide equal value in all circumstances. Understanding how you plan to take advantage of these distinct service models is an important component of the cloud strategy. In this section of the strategy, a rubric that captures the characteristics of the ideal workload for each of the named service models, along with some justification for the selection, is essential. This is a core component of Define Your Cloud Vision, and if you would like to analyze individual workloads, you can use the Cloud Vision Workbook for that purpose.

3. Delivery model decision framework: Just as there are different cloud service models that have unique value propositions, there are several unique cloud delivery models as well, distinguished by ownership, operation, and customer base. Public clouds are the purview of third-party providers who make them available to paying customers. Private clouds are built for the exclusive use of a designated organization or group of organizations with internal clients to serve. Hybrid clouds involve the use of multiple, interoperable delivery models (interoperability is the key term here), while multi-cloud deployment models incorporate multiple delivery and service models into a single coherent strategy. What will your preferred delivery model be? Why?

4. Support model decision framework: Once you have a service model nailed down and understand how you will execute on the delivery, the question then becomes about how you will support your cloud deployment going forward. Broadly speaking, you can choose to manage your deployment in house using internal resources (e.g. staff), to use managed service providers for ongoing support, or to hire consultants to handle specific projects/tasks. Each approach has its strengths and weaknesses, and many cloud customers will deploy multiple support models across time and different workloads. A foundational perspective on the support model is a key component of the cloud vision and should appear early in the strategy.

Understand key cloud concepts: Archetype

Once you understand the value of the cloud, your workloads’ general suitability for the cloud, and your proposed risks and mitigations, the next step is to define your cloud archetype. Your organization’s cloud archetype is the strategic posture that IT adopts to best support the organization’s goals. Info-Tech’s model recognizes seven archetypes, divided into three high-level archetypes. After consultation with your stakeholders, and based on the results of the suitability and risk assessment activities, define your archetype. The archetype feeds into the overall cloud vision and provides simple insight into the cloud future state for all stakeholders. The cloud vision itself is captured in a “vision statement,” a short summary of the overall approach that includes the overall cloud archetype.

The image contains an arrow facing vertically up. The pointed end of the arrow is labelled more cloud, and the bottom of the arrow is labelled less cloud.

We can best support the organization’s goals by:



Providing all workloads through cloud delivery.


Using the cloud as our default deployment model. For each workload, we should ask “why NOT cloud?”



Enabling the ability to transition seamlessly between on-premises and cloud resources for many workloads.


Combining cloud and traditional infrastructure resources, integrating data and applications through APIs or middleware.


Using the cloud for some workloads and traditional infrastructure resources for others.



Using traditional infrastructure resources and limiting our use of the cloud to when it is absolutely necessary.


Using traditional infrastructure resources and avoiding the use of cloud wherever possible.

About Info-Tech

Info-Tech Research Group is the world’s fastest-growing information technology research and advisory company, proudly serving over 30,000 IT professionals.

We produce unbiased and highly relevant research to help CIOs and IT leaders make strategic, timely, and well-informed decisions. We partner closely with IT teams to provide everything they need, from actionable tools to analyst guidance, ensuring they deliver measurable results for their organizations.


Overall Impact

Average $ Saved

Average Days Saved

After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.

Read what our members are saying

What Is a Blueprint?

A blueprint is designed to be a roadmap, containing a methodology and the tools and templates you need to solve your IT problems.

Each blueprint can be accompanied by a Guided Implementation that provides you access to our world-class analysts to help you get through the project.

Need Extra Help?
Speak With An Analyst

Get the help you need in this 4-phase advisory process. You'll receive 4 touchpoints with our researchers, all included in your membership.

Guided Implementation 1: Document your vision and alignment
  • Call 1: Review existing vision/strategy documentation.

Guided Implementation 2: Record your people strategy
  • Call 1: Review progress on skills, roles, and governance bodies.

Guided Implementation 3: Document governance principles
  • Call 1: Work through integration, architecture, finance management, etc. based on regulations.

Guided Implementation 4: Formalize your technology strategy
  • Call 1: Discuss challenges with monitoring, provisioning, and migration as needed.


Jeremy Roberts

Emily Sugerman


  • Joe Johnson, Director of Cloud Strategy, University of Wisconsin-Madison
  • Glen Cottick, Manager, Business Technology Services, City of Winnipeg
  • Nabeel Yousif, Executive Consultant
  • Norman Neil, IT Director, Westoba Credit Union
Visit our Exponential IT Research Center
Over 100 analysts waiting to take your call right now: 1-519-432-3550 x2019