Tag Archives: leadership

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
Digital Transformation

IT Reset: How to Re-Prioritize IT Initiatives During COVID-19

Leave a comment
Share twitterlinkedinmail

CIOs have had their work cut out for them over the last few months. The sudden shift to remote work has put pressure on IT to create solutions for remote workers using technology that perhaps was older or less capable, support overworked and stressed out IT technicians, and, in general, keep the business moving through the use of technology.

The priority at this time must be ensuring that technology supports essential business processes. But that doesn’t mean IT leaders should freeze any other initiatives until after COVID-19 has passed.

In fact, the worst thing any leader can do right now is “freeze” and wait until life “returns to normal.” There will be no return to the normal as businesses knew it before the pandemic. Even after the immediate threat has passed and businesses can resume working in offices, the way we work will be forever changed because of this situation.

There will be an expectation for the business to provide flexible work environments, more self-service options, tighter security, and better contingency plans for addressing future disruptions like this one.

All of these shifts provide IT with a rare opportunity to hit pause, take a step back, and reassess priorities. Adobe’s CIO Cynthia Stoddard advises, “CIOs now have to rethink priorities, or at least reorder them, and we must reinvent ourselves now as virtual leaders.”

Here are a few ways you can reset your priorities and identify what initiatives you should take on right now.

Cybersecurity

One of the first priorities should be your level of protection against cyber threats. Security is imperative for continuing essential business operations but this unique situation has increased the risk of cyber threats. “Zoom bombing” became a trend over the last few weeks as uninvited guests crashed virtual meetings and get-togethers, often disrupting the session with violent rhetoric. While Zoom quickly adapted to protect its users, this may be just the beginning of more frequent cyber-attacks and threats. As more of the world moves online, hackers will most likely increase the intensity and sophistication of their attacks. CIOs should review their cybersecurity protocols and ensure the proper procedures are being followed.

Productive Remote Work Environments

In addition to cybersecurity, CIOs need to make sure that every person in the organization is equipped to do their job remotely. This might mean you need to more heavily invest or leverage self-service technology or AI. Large investments or initiatives around new technology may have been on the back burner but now is an ideal time to reassess whether you need to make those investments now.

It’s also not just about providing technology. You may need to equip your team to handle and manage it. Are your knowledge bases relevant and up to date? Knowledge bases may not be seen as high priority, but techs will no longer be able to just walk down to an office to troubleshoot a problem. More of the organization could be turning to knowledge bases to navigate technology while they work from home.

Service Delivery

Another area to review is your service delivery processes. There are many facets of connectivity that are out of your team’s hands right now, including different hardware and software being used by team members with different levels of connectivity. Like I mentioned earlier, a service technician can’t simply walk down to an office to troubleshoot an issue. If there were any gaps in your service delivery processes before COVID-19, they are likely more apparent and problematic now. Take this time now to address those important issues.

Refocusing priorities will allow you to emerge from this situation more efficient and capable than you were. This will enable you to refocus on those more urgent tasks.

I mentioned in a previous blog post that CIOs and IT leaders need to focus on enabling outcomes instead of simply delivering outputs. Even though the way we work is rapidly shifting, this is a perfect time to reassess how IT can drive outcomes. We’ll never go back to work as before. So, instead of looking at this situation as a blow to current initiatives, look at it as the perfect time to re-prioritize and prepare for the new future.

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

ITSM is More Than Just Numbers on a Spreadsheet

Leave a comment
Share twitterlinkedinmail

This article was inspired by Mel Kerner, whose insightful comments on a recent LinkedIn post of mine started my wheels turning about the heart of service delivery.

Measuring and demonstrating the business value of IT is one of the biggest struggles for CIOs and IT leaders. There are thousands of articles, webinars, and commentary on how to demonstrate the business value of IT (I’ve even written quite a few of those articles!).

There are endless equations of metrics, KPIs, budgets, and technology that one can put together to demonstrate the value of ITSM. CIOs are hyper-focused on that bottom line. What does the IT line on the spreadsheet say about you and your organization?

That’s always the question, isn’t it? I’m not here to argue that CIOs don’t have to prove the financial sense behind their decisions on investments and projects, but I am going to pose another question:

What is at the heart of your service delivery?

I can see some of you rolling your eyes at this vague question that can’t be answered with metrics or financial projections. But I think we need to ask it because there is a goal of ITSM that can’t be measured with specific metrics or financial projections.

People, processes, technology… every IT leader has strategized over these 3 words. They are the 3 parts of every ITSM initiative.

We can measure how much technology is costing or saving the business. We can create baselines from which to measure the improvement of the effectiveness of our processes.

We can’t effectively measure the importance of people. We can capture metrics like call volumes and incident response times, but that doesn’t measure the service being provided. It doesn’t accurately demonstrate the importance of that service to the end-user – or to the organization.

This is important because sometimes everything adds up on paper, but IT is still struggling. Sometimes all of the financial plans make sense and the team is hitting its goals for all of its metrics, but users are still unhappy and service is still poor.

This is a very real disconnect occurring in organizations today. According to PWC, 90% of C-suite executives say their technology choices deliver what employees need. But 50% of employees disagree.

Is IT really delivering services if half of the organization don’t believe they have the technology for what they need? Even when the numbers on the spreadsheet are adding up, if the people in the organization are not satisfied and able to do their jobs, IT is not doing its job.

Impeccable service delivery starts with understanding how much that service delivery means to the most important part of service management: the people.

Do service desk agents understand the true value of solving a user’s technology problem? Do they fully grasp the frustration that arises when a piece of technology is getting in the way of someone doing their job?

Studies have shown that there is a direct correlation between employee experience and company performance. It’s no wonder why employee experience has become one of the hottest topics in business today. For IT leaders, this is an opportunity. They can use this focus on employee experience to remind their teams what is at the heart of service delivery.

Consider author Simon Sinek’s famous quote: “People don’t buy what you do, they buy why you do it.”

Does your IT team understand the “why” behind their metrics?

For example, why is response time important?

Is it important because it’s a box to check off? Or is it important because a service desk agent providing a timely response is able to return a user to their job faster so that they can complete their own work faster. And completing their work faster may mean they are responding to a client faster, closing a sales deal faster, or they’re able to start another project. A timely response time helps a user be better, faster, and more efficient at their job.

Or why is recurring incidents an important metric?

Is it important because it’s annoying for the service desk agent to have to solve recurring incidents? Or is it important because recurring incidents damage the reputation of the IT organization and are a frustration for the user? It can cause their mood and productivity to plummet which can then impact their interactions with customers and colleagues. It can even impact their interactions outside of the office. If you’ve had a frustrating day at work, you may end up bringing that home. The service desk can impact that!

IT leaders must talk with end-users about their experiences with IT. They should investigate the pain points users experience when their service calls are poor and the satisfaction they feel when their work is uninterrupted and technology actually makes their jobs easier.

There needs to be a bigger “why” for IT beyond just collecting metrics and impacting bottom lines. There needs to be a heart to your service delivery and it may be as simple as this: Better service delivery improves the day to day lives of your end-users.

Why does all this even matter if you can’t measure it?

The work IT does is often misunderstood and unappreciated. Most service desk agents won’t be thanked by end-users. Feeling unappreciated and inefficient will lead to burned-out agents who deliver subpar service and that can create a ripple effect. Service management is directly related to employee experience, which is directly related to company performance.

The IT leader must constantly remind the IT team why good service delivery matters. IT leaders need to take the steps to dig into the true “can’t-be-measured” heart of service delivery and communicate that to their teams. Ask the hard questions, dig into how users use services and technology to enable business outcomes, and start capturing and pointing out those immeasurable wins, just as often as you count the measurable wins.

At the end of the day, the numbers at the bottom of the spreadsheet will still matter. But the real story of IT goes far beyond the numbers on the spreadsheet. The real story is the one that’s told and heard throughout the floors away from the C-suite. It’s the story that really matters- the story of the employee’s experience.

Share twitterlinkedinmail
Leadership

Are You Prepared to Meet Customer Expectations in 2020?

Leave a comment
Share twitterlinkedinmail

In November 2018, I examined a few ways customer expectations have changed due to technology and what organizations, especially IT, need to know to stay competitive. Today, we reflect on how those expectations have changed in a short amount of time.

Customers, technology, new expectations. Let’s start off talking about a company that failed to pay attention to any of those things.

Long before we could access almost any TV show and movie from the simple click of a remote, Blockbuster reigned supreme. Anyone born before the mid-1990s probably has memories of heading down to the video store in hopes of finding a new release or a beloved classic. Of course, you never knew what would be checked out so you had to hope for the best. After you picked out and paid for your movies, you’d head home and watch it almost immediately. Because you had to return the thing a few days later to avoid those late fees!

But then in 1997, Netflix came along. And remember, before you could instantly stream thousands of movies to your TV, you could request certain DVDs online and Netflix would send them to you. And then you could send them back whenever you wanted. No late fees! This was revolutionary and it upended the video rental industry.

But Blockbuster failed to catch on. They failed to innovate. They failed to use the technology that was becoming available to them and they failed to meet the expectations their customers now had for their products.

Today, Netflix is booming and Blockbuster is long gone.

It’s easy to look back in retrospect and point out where Blockbuster failed. It’s easy to wonder how they failed to pay attention to the writing on the wall. But, of course, we enjoy the benefit of knowing how the future unfolded. Blockbuster didn’t recognize the impact of technology and, when I think about it, I can actually understand how they failed. At its peak in the mid-90s, Blockbuster had 65 million registered customers and was valued as a $3 billion company. They probably thought that they had happy customers, millions of them, in fact. They might have assumed that if they could just keep most of those millions of customers happy the same way they had been for over a decade, then they could endure some flashy competition.

The problem was not the competition, though. It was their customer’s expectations and their failure was marked because they refused to pay attention to the changing expectations of the marketplace.

While every industry is different, there are several overarching customer expectations that every organization should know.

Instant Response & Seamless Communication

Consumers don’t contact brands like they used to. They won’t call a hotline or sit on hold for hours. Now, they interact with brands just as they would interact with friends or family, through texting, social media, email or messenger. And no matter how they communicate, customers want an instant response. 40% of consumers expect a customer service response within an hour. (And yes, this means on the weekend too!)

Organizations must have the technology for instant response and seamless communication with their customers. Whether it’s incorporating chatbots, creating auto-response tools or using AI, you can’t afford to keep your customers waiting.

Easy Access to All Their Data

A decade ago, consumers understood if they had to be put on hold while you transferred them to another department or waited while you found their file in the filing cabinet.

But things have changed. Fitness trackers provide consumers with a wealth of data about their bodies just by glancing at their watch. Customers can open up Google, type in a word or two and have answers in seconds. Consumers have almost instant access to data these days. They expect your organization to do the same. They simply don’t have the patience for you to transfer them to the right department, dig for their info or wait for access from a superior to their data. Furthermore, you can’t afford to be relying on manual methods of data entry or note-taking inside a customer’s file. Every interaction needs to be automatically tracked. Your organization must have the ability to easily, securely and quickly access every customer data.

Delivery Times

Amazon changed expectations regarding delivery times. In 2015, 63% of consumers surveyed felt that 3-4 day shipping was fast. In 2018, that number dropped to 25%. And while many small businesses would love to gripe that it’s hard to compete with the biggest retailer in the world, griping will do very little to change the situation. Customers don’t care if they are ordering from a billion-dollar company or from a small shop made up of 10 employees. They expect faster delivery time.

This means organizations have to improve efficiency for every piece of the process that leads up to the actual delivery. From processing the order to packaging, organizations need to improve their process, optimize their technology and push themselves to be as fast and efficient as possible to meet demand.

Device-hopping

Consumers go from browsing on their phones to their tablets to their computers and back again. The experience with your brand needs to be consistent no matter what device someone is on. This means a mobile-friendly website, ordering system and contact forms. Everything you publish and promote needs to be accessible and easy to understand from any screen size.

These expectations are not easy to meet. The pressure is intense for every organization but I encourage organizations to look at more than the expectation but the need behind the trend to stay ahead.

Netflix didn’t succeed because they used technology to mail out DVDs. They succeeded because they understood their customers wanted convenience. Customer expectations are born because organizations pay attention to what customers want and need. Whether its speed, convenience, comfort, customer service or quality, there is a need or a want behind every new customer expectations.

Organizations, especially the IT department, should be listening to their consumers and identifying their underlying needs. If they can do this, then they can identify the best services, create better processes and find the right technology to deliver those services, meeting not only these customer expectations but any expectations that might arise in the future.

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