Who’s Steering Your Technology? How Leaders Close the Gap Between Strategy and IT

Part of The Connected Enterprise series 

Technology is supposed to help an organization reach its goals. In many organizations it doesn’t, and not because the tools are wrong. Nobody is steering. At The Connected Enterprise event, Lenny Giller, President of RTS, explained how that gap opens between leadership and technology, and what leaders can do to close it. PJ Sawchuk of Epic Solution Partners added a practical way to keep it closed: a technology committee. 

The disconnect between leadership and IT 

In many organizations, nobody really owns the technology, and leadership and the technology team rarely connect. It isn’t anyone’s fault. Most leaders know they need technology but aren’t sure how to get the most out of it, so they hire people and tell them to “go deal with it” without setting any direction. 

Without that direction, technology doesn’t move the organization toward its goals. It becomes just another expense on the P&L, and the CFO asks how to shrink that number instead of what it delivers: better service, higher profitability, happier employees. 

The gap shows up clearly in the regular technology update. It might happen monthly or quarterly, and in many cases only once a year. Without direction, the technology team does what makes sense and shows its work. 

  • What gets reported: tickets closed, uptime, patches applied, projects completed. 
  • What leadership cares about: growth, better customer service, reduced risk. 

Those numbers show how busy the team is, not what the business is getting. Everyone comes in with their own justification for their salary or their invoice, and managed service providers are often guilty of this too. The better question for leadership is what the technology team should be reporting on instead. 

What’s running in the shadows? 

When there’s no direction, people solve problems on their own. That’s shadow IT and shadow AI: tools and AI services used outside approved systems. 

It usually isn’t malicious. Organizations hire smart people and put them in charge of their departments. When they see a problem, they solve it, often by adding a new tool and new spend, even though another department may already have a solution the organization paid good money for. Nobody owns that piece, there’s no ongoing communication, and the tools keep piling up. That creates three problems: 

  1. Spend. Money goes out the door on tools nobody approved. 
  2. Data security. Client and company data goes places nobody knows about. Security rarely makes anyone’s day better. Think about going through TSA: it isn’t fun, but it’s critically important. The goal isn’t to make people’s lives miserable. It’s to understand what you’re protecting and why, then put protections in place with productivity and people in mind. 
  3. Reports you can’t trust. Work done outside approved systems skews workflows, KPIs and the numbers leadership sees. If the same data is entered several different ways, the reports behind critical decisions are skewed. Can you really trust those numbers? Usually not. 

How to handle shadow AI 

Telling people not to use unapproved tools isn’t enough when those tools are a click away. Here’s what works: 

  • Communicate before you enforce. If you can see usage on company devices, call it out, for example with a notification. But if you haven’t communicated and reinforced the rule, don’t jump to punishment. Use it as a chance to explain what could have gone wrong. 
  • Keep repeating the why. Use newsletters and all-hands meetings to talk about things that were caught or nearly went wrong. Explaining why, over and over, is what changes behavior. Technical controls come next, once that groundwork is in place. 
  • Make approved AI use visible. People often use AI behind the scenes because it feels like cheating at their job. A clear policy lets you talk about AI openly and champion the right way to use it. 

Direction before technology 

The good news: the fix doesn’t need more technology or more money. It needs leaders to be intentional, starting with a foundation of four things: 

  1. What you have. What systems do we currently use? 
  2. Why you have it. What problem is each tool, and each dollar we spend, actually solving? 
  3. Who owns it. This is what stops the cycle of buying more tools. When someone knows what a system can do and shares that across departments, the duplicate purchases stop. 
  4. Is it secure? Can we secure it well enough, and is the information in it worth a deep conversation about protection? Not all information is equal. Data under regulatory compliance needs more attention. For publicly available information, you want the system up and running, but you probably don’t need to spend heavily protecting the data. 

On top of that foundation, leadership sets clear direction: outcomes, priorities, and guardrails. 

How specific should AI guardrails be? 

As specific as possible, and set early, because policies define how you will evaluate every option that follows. 

  • Spell out which AI tools are approved, what to use them for, which tools are off-limits, and when company or client data should never go into an AI tool. Vague guidance leaves room for interpretation. People who want to move fast or prove their value will take shortcuts with tools they’re comfortable with, often without understanding the risk to company data. 
  • Build guardrails into the tools themselves. For instance, an HR team building an AI tool to support performance management (goal setting, feedback and reviews) started with policy, then decided what the tool should not do: make decisions or compare one employee with another. They tested it, built in those guardrails and told users what was built in, so people felt comfortable using it. 
  • Make human oversight part of the policy. Whoever uses AI output owns it and is responsible for reviewing it. 

Clear guardrails protect your people, your clients, and the people you serve. 

Give people permission to move 

Then comes permission to move: freedom to try, learn and move fast inside the guardrails. Many projects drag on because there’s no communication and no permission to fail. People are so afraid of mistakes that they overthink everything, and projects that could move the organization forward go untouched for years because people fear how leadership will react. 

Only once all of that is in place can you look at your processes and decide where AI fits. That’s the subject of Fix the Work Before You Add AI. 

Put it into practice with a technology committee 

Direction needs a home. PJ Sawchuk recommends a technology committee. 

Who should be on it. Don’t make it purely an executive group. It works best one level down, with senior leaders who understand where the organization is going but are close enough to the work to know what will make a difference. They are also the right people to draft and review policies, because they bring a range of perspectives. AI isn’t purely a technology topic, so the committee should include an executive sponsor, the IT lead, operations, finance, HR, and your technology partners. 

What the committee reviews every quarter: 

  • Governance and policies. 
  • Security procedures. The committee is a great group for security tabletop exercises. It’s good to have a document that says what you’ll do when something goes badly wrong, but has anyone actually walked through it to see whether it works? 
  • Data quality. Make data stewardship part of your data governance policy. Name owners for specific systems, because they know better than anyone what the data in that system should look like. 
  • AI and automation use cases. Many workflows cross departments, so the committee is the right place to prioritize them. 
  • Spend versus budget. 
  • The IT roadmap. The roadmap is a movie, not a picture. Revisit it at every meeting and adjust. Even meeting quarterly, AI changes dramatically in three months, and things possible today weren’t possible six months ago. 

Measure with what you already use. Technology isn’t magic. It’s domain expertise, no different from HR, legal or accounting. Rather than inventing new ways to measure technology outcomes, use the processes you already have. If your organization uses OKRs, set clear objectives, agree on how you’ll measure them, and use a shared vocabulary for the numbers. 

Stay involved. Leaders who succeed don’t bark orders from above. They go department by department on a regular cadence and ask: How’s it going? Where are you stuck? What obstacles can I remove? That steady attention shows the organization this isn’t another slogan that will die in two weeks. 

 

Got questions or need help? Contact our speakers. 

Talisha

Talisha Padgett

GM, Global Marketing Technology & AI Transformation, Microsoft; Co-Founder, Humxn Loop Consulting 

Talisha.padgett@outlook.com 

Talisha Padgett leads AI transformation for global marketing technology at Microsoft, where she also leads responsible AI and started an AI center of excellence in 2023. Over 20 years she has helped companies such as Marriott and Under Armour get real value from their technology. She is also co-founder of Humxn Loop Consulting, which focuses on the human side of transformation and change management. 

Carlee Wolfe

Associate Vice President, Integrated Talent & Organizational Effectiveness, Hyatt Hotels Corporation 

carleewolfe@gmail.com 

Carlee Wolfe leads how Hyatt develops and supports its people, with a people-first approach to AI. Her team’s work includes performance management, from goal setting to feedback and reviews. She champions Hyatt’s mission to care for people so they can be their best, and its definition of care as empathy plus action. 

Panelists

Lenny Giller

Lenny Giller

President, Reliable Technology Services (RTS) 

lenny@reliabletechnology.co  

Lenny Giller leads RTS, a managed IT services provider known for elevating technology conversations from the server room to the boardroom. Lenny emphasizes using technology strategically — not just to keep businesses running, but to help them become more efficient, profitable, and competitive. His approach focuses on aligning IT with organizational vision and using modern tools to drive growth. 

Michael B

Michael Bresler

Founder and Managing Member, Broadheights 

michael@broadheights.com 

Michael Bresler founded Broadheights to make work flow so people can do their best work. The firm aligns people and process first, then applies responsible AI to scale what already works, helping nonprofits, schools, foundations, and businesses free up staff time and redirect it toward greater impact. Michael brings more than two decades of experience in business operations, technology, innovation and client success, including executive roles applying AI to drive innovation and streamline operations. 

PJ Sawchuk

Partner, Epic Solution Partners 

pj.sawchuk@epicsolutionpartners.com 

PJ Sawchuk is a partner with Epic Solution Partners, an IT advisory firm that helps organizations align technology strategy with business strategy and guides them through large transformation projects. His background started in technology, and he has since woven operations, large-scale project management and service delivery into his practice. PJ spent 12 years as Director of IT at a mid-Atlantic regional law firm and three years leading the global service team for a CRM software company, and has been consulting since 2020.