Tag Archives: culture

Consultancy

How IT Can Enable Organizations to Make Data-Driven Decisions

Leave a comment
Share twitterlinkedinmail

Technology is one of the biggest and most important investments that any organization can make. In the past, many decisions about technology investments were made within the C-suite or demanded by other departments and IT simply complied with those requests.

But as the world has become more dependent on technology, IT has started to play a larger role in influencing technology investments and decisions. I would actually argue that IT should play a major role in helping the organization make good decisions, not just about IT and technology, but also the overall organization. Why?  

Organizations need data to make decisions.  Having the right data at the right time enables the organization to make good decisions.   And who manages the systems and services that produce most of that data?  The IT organization.  Therefore, it only stands to reason that IT should be involved in most organizational decisions.  But for some organizations, this means a mind shift change about the role of IT in decision-making.

The good news is that this shift doesn’t require a bigger budget, more staff, or even the encouragement of upper management. Every IT organization can start making these changes and begin to play a larger role in helping the business make data-driven decisions.

  1. Shift the perception about the value of IT 

This first step is easier said than done, but this needs to be a consistent effort for IT leaders. IT does much more than troubleshooting computer problems and keep everyone connected to WiFi.

But to shift this perception, you must be measuring outcomes not just outputs. Outputs are the actions or activities that an IT organization completes. Outcomes are the results that the business wants or needs to achieve. Outputs contribute to outcomes. They are the activities that IT has accomplished, such as the number of calls to the service desk or number of influencer records. 

The context of driving business value and influencing business decisions, it’s outcomes that matter more than anything. IT has to start thinking and talking in terms of business not in terms of IT. For example, if you were to say “98% availability” this doesn’t mean anything to your business colleagues. But instead, if you shifted your message to say “Provided system available to produce 10,000 products,” they can understand how IT’s work contributes to the bottom line. Look in terms of outcomes then document every outcome that IT helps achieve. Report on those outcomes and share these wins regularly with IT and the rest of the organization.

2. Follow the Value Streams

Following the value streams means understanding how value flows through an organization and identifying where there may be improvements.  IT has to map the value streams.  A value stream map, as defined by the Lean Enterprise Institute, is a simple diagram of every step involved in the material and information flows needed to bring a product from order to delivery.

A value stream map is a holistic view of a process so it requires everyone’s input – from IT and other departments. What is should do is identify show where there are steps in the process that don’t add value to the end goal. The objective of a value stream map is a smoother, more efficient process that the entire organization agrees on.

Mapping value streams, not just within IT, but also including other departments will help IT (and the rest of the organization) gain a clear picture of where value is created and how it reaches the end customer — and perhaps just as importantly, where it’s not reaching the customer.

3. Identify services 

With value stream maps in place and a clear understanding of the business outcomes you’re working to achieve, you can then identify IT services and how those services influence and drive those business outcomes.

A service is a means of delivering value for a customer by facilitating outcomes or results that the business wants to achieve. For example, providing someone a tablet without software or network connectivity doesn’t contribute to an outcome. It’s just giving a piece of technology. But, if the tablet is part of the value chain and can help someone perform their job remotely so value continues flowing the organization, you now have completed service.

IT services should align with organizational value stream maps so that the IT contribution to co-creating value is clear. Look at the map and identify where technology enables the value stream. You need to define services that support and enable the technology or process that drives business value.

4. Experiment from ‘knowing’, not ‘guessing’

Once you start doing these first three things, you’ll begin to gather meaningful, business-relevant data. But be prepared! The data might be good. You might see where all that value is being created and clearly how value reaches the end customer. You might see that technology is doing exactly what it’s supposed to do. 

Or the data might be bad. You could see that value is leaking within the organization or that IT services aren’t effectively driving desired outcomes. More likely, you’ll see a combination of the two.

It’s important to be open to whatever data you find. The data will point you in the right direction. If the data is telling you that IT services aren’t driving the desired outcomes, it’s not a bad thing. It just presents a bigger opportunity.

This is the place of knowledge from which you can start experimenting with services, technology, and workflows. In these uncertain times as businesses continue to pivot, experimentation is going to become more mainstream, but experimentation will work best if you start from a place of knowledge. 

Be willing to make changes to the defined services, the workflows in a value stream, or even the technology you use to enable these services and workflows. Continue to measure the data as you go so that you can see what actually creates a more efficient, cost-effective value stream.

You and the rest of the organization need that place of knowledge from which to start innovating. With this data, plus the understanding of how IT works with the organization, everyone can make better decisions around the use of technology, where to make investments, and how to grow the business. 

When you are ready to tap into your data, I recommend downloading the CIO’s Guide to Navigating Shifting Priorities. It includes 3 of my most recent webinars (both the video and audio versions) designed to help CIOs lean into innovation, leverage what is working, and pivot along with the rest of the business. Download the guide here. 

Share twitterlinkedinmail
ITSM

Why IT Organizations Stay Broken

Leave a comment
Share twitterlinkedinmail

They say that “change is hard”. Organizational change is probably the most difficult kind of change. And for some reason, IT struggles with its own organizational change. Sure, IT knows that organizational change may be needed for business colleagues so that they can fully take advantage of a new IT product or service. But when it comes to organizational change within IT- IT often strikes out. Rather than be a model of good organizational change for the rest of the business, IT will often position itself as a support team, or as a service provider, continually at odds with the rest of the organization.

Time is running out on this old, broken model of IT organizations though. The IT organizations who fail to transform themselves beyond a support organization or a service provider will fail to exist. This sounds harsh, but it is the reality. IT organizations must understand why they are broken and they must commit to making the change if they want to continue to exist in this new normal.

Why do IT organizations stay broken?

The short answer is they’re afraid.

Now, I know that answer probably just lost me a few readers right off the bat. But if you’re still with me, a tip of the hat to you. Why is IT afraid to change? I have broken it down into two groups of IT organizations who don’t change. They’re both afraid for different reasons but fear is the leading factor for both.

The first is the IT organization that is afraid of what they don’t know.

Popping open the hood of IT to see what’s actually happening can be enlightening, but also terrifying. Because you might be able to see how hard the motor is working to keep the car running. Or you’ll find that you’re missing parts, parts have been long broken and you’re lucky that the car runs at all.

If the latter happens, the amount of work has just quadrupled to fix what’s missing or broken. Worse than that, the C-suite now has a picture perfect view of how much IT is underperforming.

This kind of discovery is scary to this type of IT organization. At least in their current reality, they understand it and they know how to explain it, defend it, and even work with it. It feels safer to distract themselves with putting out daily fires and accepting that they’re never going to hit their highest performance goals. But hey, at least they’re not making it harder on themselves by spotlighting their gaps and putting more work on their plates.

The second group of IT organizations who won’t change is the group that’s afraid to start. This group often knows they need to make a change, but the fear of starting down the wrong path or starting with the wrong initiative has them paralyzed. .

This group has probably popped open that hood of IT and they see all the broken parts – but every broken part seems to be the most important one to fix. They don’t know how anything under the hood works together so they don’t know where and how to get started.

And the longer they wait to make a change, the harder it is to justify doing that work required for that change. They continue accepting the status quo because they don’t know what else to do.

The fear of finding out what’s wrong, or working on the wrong thing, is very real for many organizations and the truth is, I understand it. Sometimes sitting in the dark is easier because you won’t have to see the monster.

But we can’t live in fear, especially right now in this current climate.

The business world is changing. Actually, the entire world is changing. When everything is uncertain, the most innovative leaders are the ones who know they can capitalize on this opportunity.

But it requires a level of courage, willingness to take on the responsibility, and committing to doing the work and to dig into the data they already have.

The Data is The Road Out

Both of the groups of organizations I described above lack one thing: data.

They don’t have the data to understand where and how they can make improvements. Or they think they don’t have the data.

Whether they’re too afraid to face it or feel too overwhelmed to dig into it, every IT organization has the data they need to make lasting change in their organization. It exists all around them — within their team, their end-users, their partners, their vendors, their processes and services. They just have to tap into it.

This mess of data may seem overwhelming at first but there is a way to take the next step. The hot topic right now is “experimentation.” Difficult times in business require innovation, and innovations require experimentation. But I’m adding an addendum. Instead of just simply experimenting, you should “Experiment from a position of knowledge.” Use your data. What is your data telling you? Where is it leading you?

Instead of allowing this uncertainty to freeze you in fear, try leveraging this uncertainty to propel you into something bigger, better, and different. Everything is already different in 2020 – so why can’t IT be different in a better way?

I predict we will start to hear IT success stories: the ones that innovated instead of standing still (or even worse, receded), the ones that pivoted rather than just turned in circles, the ones that leaned into the uncertainty and transformed into something better. I’m hopeful that the right leaders are in place in many places and they are already beginning to use data to drive change, learning from mistakes, and leveraging the capabilities they already have in place.

Don’t stay “broken”

My challenge to you reading this is: how will you transform your organization? How are you going to push through whatever fears that are holding you back? There might not be an opportunity quite like this one again. Leaders are made for these moments. Are you going to accept being broken? Or are you going to step up and pop open that car hood?

Share twitterlinkedinmail
ITSM

Your Continuity Plan Still Isn’t Good Enough

Leave a comment
Share twitterlinkedinmail

Continuity plans have been in the spotlight for businesses across the globe over the last few months. If your continuity plan wasn’t done or hadn’t been reviewed in months, then you probably felt that pain over the last few weeks. Even those with up-to-date continuity plans are refreshing theirs with their lessons learned from COVID-19.

“Continuity planning” has been topping lists of must-do’s for CIOs and IT leaders. But someone has to ask the question: even with a 2020 update, is your continuity plan good enough?

From what I’ve been reading and seeing, probably not. The good news is that you can still shore up your continuity plan so that it actually helps your business in the event of another disaster.

The Problem With Continuity Plans

For CIOs, continuity plans mean including the obvious things:

  • How many laptops does our team need to work remotely?
  • What needs to be moved into the cloud or onto a collaboration platform?
  • What cybersecurity systems need to be set into place?

These are important items to address. They will help your business continue in the event of an emergency. But they’re not the solutions to the real concerns. They are band-aids. These things only address the symptom but not what causes the symptoms.

A continuity plan needs to address what your business needs to do to stay running most effectively and how vital business functions can continue operating during a disaster.

On their own, none of the above components reflect how they connect to vital business functions or business needs. They’re just a list of outputs. They don’t tie it back to the business need or driver or requirement. They’re not outcomes. Our continuity plans should focus on the outcomes we must deliver to support vital business functions. Then we’ll know what outputs we need to produce in order to provide the outcomes that are needed.

I’ll use one of my favorite metaphors to explain the difference between outputs and outcomes. This one might feel familiar to you if you’ve been ordering takeout food recently. You probably have a favorite pizza delivery place that you choose over any other. What is it that makes that pizza delivery your favorite? Because the output from every delivery service is the same. The output is the pizza that you receive. But the outcome of pizza delivery is that the pizza was delivered warm, the driver was friendly, it was delicious and you enjoyed every second of eating it. The output is simply what you expect because it’s what you paid for. The outcome is the entire experience and value that was delivered.

To have a good continuity plan, you need to identify the outcomes that are necessary, not just the outputs that simply keep the lights on.

We need to start with the business impact analysis which quantifies the impact of the loss of service. A business impact analysis collects relevant data and analyzes the operational and financial impact of a disruption of business functions and processes. These can be as detailed as we need it to be. The more detail, the better because we’ll be able to make better business decisions.

The business impact analysis starts us down the path of identifying those outcomes because it assumes that every part of the business is dependent on the continued operations of the other parts of the business (which it is).

Is this starting to sound familiar? When we think of business impact, in particular the holistic approach to end-to-end value, we’re really identifying the value streams.

If you read my previous article this month, you know that I’m a proponent of Value Stream Management, which is the holistic approach that applies lean thinking – optimizing the flow of products and services through entire value streams across technologies, assets, and departments – across an organization’s value streams. Instead of just looking at functions and features, value stream management looks at and manages value streams from end-to-end.

In terms of continuity plans, if we reflect on the value streams, our plan has to become more than the technology that supports the value stream. It will encompass the entire end-to-end lifecycle of business value and the outcomes of each value stream.

This where you’ll begin to focus on things like the roles of the people involved and how they interact with one another and the end customers to deliver value. Your continuity plan becomes comprehensive and more impactful.

How To Make Your Continuity Plan Valuable

Now that you understand what really needs to be in a continuity plan, there’s a second piece that needs to be addressed.

You can’t just drop this plan into a drawer and cross your fingers that you won’t need it again anytime soon. If COVID-19 has taught us anything, it’s that unthinkable scenarios can occur. We may not see another pandemic in our lifetimes but we will see another disaster of some type.

Your continuity plan cannot be a one and done scenario. It needs to be reviewed, updated, and addressed on a regular basis. Each time you map your value streams or add new value streams, go back to your continuity plan, and evaluate that it’s still up to date.

We can’t know what the next disaster is awaiting businesses but we can be better prepared for any disaster. The best time to prepare for the next disaster is right now.

Share twitterlinkedinmail
ESM

Outcomes vs Outputs: The Real Proof of IT’s Value

1 Comment
Share twitterlinkedinmail

The typical workday looks much different today than it did just a few months ago. Instead of driving to work and walking into the building, employees are going online and signing in to their messaging or collaboration tools.

Instead of physically taking a document to a client for a signature, they’re being sent digitally for electronic signatures.

Instead of popping into an office, managers are checking in with employees via texts, instant messages, and video calls.

As many businesses continue to work remotely amid the COVID-19 pandemic, it has become increasingly clear that technology is keeping the business together. Because of this, IT has to move into a more strategic role. For years, experts have been advising IT leaders to take their seat at the strategy table and be involved in the larger business decisions. Many IT leaders have jumped at this opportunity while others have struggled to figure out how to demonstrate IT’s ability to be more than a support function.

This shift of IT from a support function into a strategic partner can start with a simple shift. The shift from focusing on outputs to outcomes can make a world of difference for IT organizations.

Outcomes vs. Outputs

Let’s begin by addressing the difference between outputs and outcomes.

Outputs are the actions or activities that an IT organization completes. They are quantitative and easily measured.

Outputs could include:

  • Moving files and documents into the cloud
  • Closing tickets in record times
  • Installing new technology

Many IT organizations measure outputs as a way to illustrate their productivity and value. The thinking is that the more outputs they complete, the more the rest of the business will see IT as being valuable.

While outputs are important, outputs only tell part of the story. The real measure of value is the outcomes that are enabled by those outputs. Outcomes are the results that the business wants or needs to achieve.

Outcomes are business objectives such as:

  • Increased market share
  • Higher customer satisfaction scores
  • Increased profits

For example, the outcome of moving computing capability to the cloud is a more mobile and flexible work environment. The output enables the outcome. For every output IT is completing, the CIO must know and communicate what the business is now able to do as a result, or outcome, of that output.

That means before listing an output on a project list, IT managers must ask: “What outcome is this going to enable?”

By doing this, you can cut down on the amount of busywork or projects that are not contributing to the bottom line. It will also show what outputs are ineffective. In some cases, IT delivers an output that doesn’t enable or deliver any real business outcomes. If this is the case, you’ll need to review the output and determine if it is truly needed.

This shift may also show that some of your metrics and KPIs are ineffective ways of measuring IT’s performance. For example, if your team has a high first-contact resolution rate but employees are still reporting poor service, then the first-contact resolution rate isn’t a good indicator of your performance.

How to Make This Shift

What do IT leaders need to do this to make this shift in their organizations?

Build Business Relationships
IT leaders need to understand the outcomes the business wants to achieve. They should seek out key stakeholders and have regular conversations about their technology needs and their goals and objectives. This will allow IT leaders to begin to see the end-to-end value of their outputs and initiatives.

Define and Map Services
Once you know the desired outcomes, you can map IT services to them. Map how the outcomes of your services connect to business objectives.

Measure Outcomes
It’s not enough to simply list off the number of outputs your team completes each month. Engage your stakeholders to identify outcomes and how an output contributes to an outcome.

The Future of IT

At the beginning of this article, I mentioned that IT has no choice but to evolve now. The way we work will be changed forever. Even when businesses return to the office, there will be different expectations around flexibility and how technology enables flexible mobile workforces. The business will want to be prepared for the future, should anything like this happen again and they’ll be looking at IT to help plan and prepare for those possibilities.

CIOs and IT leaders must approach their goals and initiatives differently if they want to rightfully play a leadership role in their organizations. Connecting IT outputs to business outcomes enables IT leaders to help shape the future of their organizations.

Share twitterlinkedinmail
ITSM

What Should Your Customer Experience Look Like & How Do You Get There?

Leave a comment
Share twitterlinkedinmail

Recently, I’ve been sharing about customer expectations and while understanding those expectations is important, you also have to have a plan for how to meet those expectations.

I am referring to the customer experience, of course. The customer experience includes every touchpoint a customer has as they interact with a brand. Customer experience has always been important. But as the world grows increasingly digital, brands are tasked with understanding and mapping the multi-channel experience that customers go through with brands.

And there’s a reason companies spend time, money and effort on mapping and optimizing these experiences. In short: they matter. Forrester found that from 2011 to 2015, revenues for companies that scored near the top of the Forrester CX Index™ outgrew the group of companies that scored poorly by more than 5 to 1.

As brands become focused on the customer experience, they are turning to a new ally, who previously has not been involved in customer experience: the CIO.

The CIO & The Customer Experience

Historically, the CIO has had little to do with the customer experience. The business leaders like sales, marketing and business development would meet to map out the experience and then, they’d ask IT to build what they needed to create that experience. But times have changed.

In a recent KPMG Survey, more than half of the CIOs surveyed reported that enhancing the customer experience is the most important business issue that boards want IT to work on.

The fact is, the CIO needs to be involved with the customer experience these days. CIOs understand the technical limitations of new technologies as well as understand current in-house capabilities. Instead of the business guessing what is possible, IT needs to work with them to create solutions that are achievable.

What A Quality Customer Experience Looks Like?

The question is, of course, what does a quality customer experience look like? If we refer back to the emerging customer expectations that I discussed in this article, a few things become clear.

The first is that customers want a “contextual, intuitive and experiential engagement.” Another way to phrase this is to design a low-effort experience.

What’s a low effort experience? To answer that, let’s first look at a high effort experience.

A customer calls a customer service line. They have the option to wait on hold for an undetermined amount of time or to have the company call them back when it’s their turn. The customer chooses to wait on hold. They wait on hold for 17 minutes when a representative finally gets on the line, asking for the person’s information. The customer then waits another minute while the representative pulls up their information and asks what the problem is. The customer explains their issue. The representative provides a textbook response that doesn’t meet the customer’s needs. The customer asks for another resolution. The representative tells them they have to transfer them to a manager. The customer then waits another few minutes on hold. Once transferred, the manager again asks for the customer’s information and the customer again waits while the manager pulls up their file. The manager tries to provide the same answer the representative does but the customer asks for another resolution. After a few minutes of back and forth, the manager tells them they will try to find another solution and that they’ll email them with a solution within a few days after they have spoken to the appropriate department.

This may sound convoluted but it happens all of the time! I’m sure many of us have encountered similar experiences when dealing with customer service problems. Consider what the customer has to endure during this exchange: multiple wait times, hearing the same information repeated, resolution to be delivered in a different format than the initial exchange. In other words, it’s a high-effort experience for the customers. According to Gartner, 96% of customers who encounter this type of interaction will become disloyal to a company.

The trick to creating low-effort experiences is to lead with the benefits or solutions to customers’ problems over the technology.

For example, if your customers want faster issue resolution, then your organization should turn to real-time text or voice chatbot that is readily accessible for customers at scale.

If customers need more information prior to purchase, consider enhancing your mobile experience or incorporating augmented reality tools so customers can visualize products in their offices or homes.

If your customers want a more personalized experience, focusing on consumer data collection and organization will be your best priority.

There is no one size fits all to delivering exceptional customer experience. It’s about listening to your consumers, paying attention to their needs and then, creating services, incorporating technology and designing processes to fit those needs.

How To Get There?

To point you in the right direction of how to create exceptional customer experiences, I am going to end this article with a question:

How do you think employee experience shapes the customer experience?

Share twitterlinkedinmail
ITSM

Focusing on Technology May Kill Your Business

1 Comment
Share twitterlinkedinmail

I know the technology wishlists of many CEOs. They want newer technology, faster technology and the shiniest, most fully-featured tools. While technology is not a bad thing to have on any wishlist, it shouldn’t be at the top of it and it absolutely shouldn’t be the only thing on that wishlist.

It’s 2020 and there’s no need to explain why organizations need technology. But I think organizations should be cautioned about the hyperfocus of technology that exists today.

I hear a familiar story time and time again when I work with clients. They poured all of their money and effort into a tool hoping it would solve their problems, only to find, months later, that they still have all of their problems…only now they have less money and, now, an expensive tool.

Technology can’t solve all of our problems. If you’re focusing too much on your technology, you just might be killing your business.

My Thoughts on Technology

Before you head to the comment section to tell me I’m wrong, I want to make clear that technology can be a huge asset to an organization. Technology can make an organization more efficient and streamlined. It can decrease overhead costs and enable increased revenue. It can shorten production times, improve customer and employee communication and, in general, help a business run better.

However, that’s only if the technology is managed properly. Technology is a tool. You absolutely need it to grow and scale a business. But if you’re not managing it properly, then it’s going to cause more headaches than ease.

I like to use the simplistic analogy of building a house. If you start hammering the nails into your house using the head (or top) of the hammer, instead of correctly hammering using the face (or front) of the hammer, then you’ll still be using the tool and you still will be building a house. But it’s going to take you longer and it will require more effort to actually complete the process. And it won’t help if you buy a new, fancier, shinier hammer because you’re not managing the hammer the way it should be managed.

The same can be said for the technology in a business. If you have a shiny new tool but you or your team is not using it to its full capacity, you’re still going to struggle with the same problems you had before that shiny new tool.

Instead, CIOs and CEOs need to look at a few other factors before the technology.

Business Strategy

Before you invest any money into technology, you need to ask yourself: what is this technology supposed to do for the business? What is the strategy behind the deployment of this technology? Can you link the impact of this technology to the bottom line of the business?

IT must be a strategic partner with the other members of the C-suite and be invested in how every initiative depending on technology delivers on the bottom line. With this clear view of what’s happening within the organization and how different efforts are contributing to the growth of the business, IT will be in a better position to create a business strategy for the uses of technology.

The People

Technology may help manage a business but it’s people who manage the technology and people often need management themselves. Working in IT can feel like a thankless job and it comes with a large amount of pressure and stress. IT practitioners can become burnt out, jaded and indifferent to their work without proper management.

One of the best things a CIO can do for their IT team is to ensure they are in the right mindset to manage technology. Practitioners should have a solid understanding of why the technology is needed, the contribution of technology to the business, and how it’s benefiting the business as a whole.

In the past, many IT practitioners have simply acted as gatekeepers, saying “no” to requests, and staying firmly in their lane of working only with technology and avoiding any “business.” IT can no longer operate under these old ways.

IT practitioners now must understand the business of the business. It will help them to better manage the technology and make good decisions about technology that will have a better impact on the business.

The Service & Delivery

Finally, the last question you should ask yourself before turning to the technology is how that technology is managed and delivered. Are the processes in place for managing the technology? Is there documentation for the process? Has your team properly identified and defined the services that are delivered based on the use of technology?

When these important questions go unaddressed, your technology will fail to deliver the (unspoken but) expected outcomes. Technology needs to be properly managed with guidelines, defined processes and measurable and repeatable deliverables. With these things in place, your IT organization will be able to communicate and demonstrate to key stakeholders how the technology is delivering on its promise. Without it, everyone will be left wondering what exactly happened to that IT investment.

Your organization will always require technology. It’s a smart business move to evaluate the best and most fully functioning technology on the market to ensure your business is using the best technology that meets the business need. However, it’s important to remember that technology can’t manage itself. Even the most fully featured AI-enabled technology can’t manage itself. If you focus on how to manage the technology more than the technology itself, then you’ll avoid wasted investments and you can keep your business growing.

Share twitterlinkedinmail