Tech Leadership Lessons from Canadian Tire's SVP of AI: Keran McGuire on Culture, Cloud, and the Full-Stack Thinker

A recurring production issue was burning through engineering hours at a financial institution. The incident retros were piling up. The runbooks were updated. Nothing changed. Then Keran McGuire did something that no one else had tried — she walked down the hall and introduced two teams who'd been solving the same problem independently for months. A 30-minute conversation fixed what six months of post-mortems couldn't.

That story tells you everything about how Keran McGuire leads. She's the SVP of AI and Technology Platforms at Canadian Tire, with 20+ years of tech leadership across startups, CIBC, Microsoft, and one of Canada's largest retailers. On this episode of the Code To Cloud podcast, she shared the playbook that carried her from an accidental IT enrollment to the C-suite — and the lessons apply whether you're a technical professional navigating your career, a leader managing cloud transformation, or a business owner trying to make sense of AI.

From Accidental IT Student to SVP: A Tech Leadership Journey

Keran's career started with a scheduling mistake. She enrolled in information technology management at university thinking it was a business course. But something clicked. Network architecture, logical problem-solving, the way systems connect — it drew her in. She never looked back.

Her first role was at a small startup funded by BlackBerry, where she experienced insourcing technology before that concept had a name. That scrappy environment taught her something enterprise roles rarely do: when there's no one else to call, you learn everything. You become the network admin, the help desk, the architect, and the project manager — all before lunch. That breadth would become her superpower. From there, she moved to CIBC, then Microsoft, and eventually Canadian Tire — each transition requiring a fundamentally different kind of leadership.

The pattern across Keran's career is clear: embrace the uncomfortable. The roles that felt too big, the projects that seemed too complex — those are the ones that compounded into real leadership capability. It's a lesson I see validated constantly in my work as a fractional CTO: the leaders who grow fastest are the ones who volunteer for the hardest problems.

How to Translate Tech into Business Value (The Skill That Gets You Promoted)

Working in highly regulated industries like finance taught Keran the skill that separates senior individual contributors from executives: translation. Not between programming languages — between people.

Here's the scene she described. You're in a boardroom. On one side, the architect is explaining microservices decomposition and P99 latency budgets. On the other, the CFO wants one number: will this migration reduce cost-to-serve by Q3? Same project. Completely different languages. Most technologists present to impress their peers. The ones who get promoted present to move the business forward.

Keran's method is deceptively simple: reverse-engineer from the business outcome. Start from what the stakeholder cares about — cost, risk, timeline, revenue — and work backward to the technical requirement. Then communicate in their language, not yours. This sounds obvious. Almost nobody does it consistently.

The hallway story I opened with? That was Keran at a financial institution. The fix wasn't a new tool or a better runbook. It was identifying that the root cause was organizational, not technical — two teams duplicating effort because no one had connected them. She's applied the same principle to cloud migrations: moving entire data centers over a weekend is achievable with modern automation and AI-assisted tooling, but only when the stakeholder alignment work has been done first. The technology is rarely the bottleneck. The bottleneck is communication. If you're planning a migration and haven't mapped your stakeholder communication plan yet, our guide on 5 cloud strategy mistakes that kill startups covers the same anti-patterns at every scale.

Building High-Trust Tech Culture: The "Pizza Approach"

I asked Keran what separates the best-performing teams she's led from the rest. Her answer wasn't a framework, a process, or a tool. It was pizza.

Her "pizza approach" is disarmingly simple: share a meal, have a real conversation, build trust before you need it. The teams that eat together — metaphorically or literally — are the teams that solve problems together when everything is on fire at 2 AM. Simple acts of breaking bread build empathy, and empathy is the foundation of psychological safety. Without psychological safety, people hide problems. Hidden problems become outages.

This isn't soft leadership. It's strategic. Google's Project Aristotle research confirmed that psychological safety is the #1 predictor of high-performing teams — and Keran figured that out from experience across four organizations before the study was published. When people trust each other, they escalate faster, collaborate more freely, and take intelligent risks.

One practice she shared: when facing a complex challenge, she openly asks her team for ideas — regardless of complexity or seniority. This isn't brainstorming theater. She acts on the input. A junior engineer's suggestion once saved weeks of rework on a platform migration because they saw a dependency that the senior architects had missed. That feedback loop builds team confidence and surfaces solutions that top-down directives never will.

If you're building or leading a team, Keran's advice maps directly to what we see in our training and support engagements: the teams that invest in culture and cross-functional understanding adopt new technology faster and with fewer missteps.

AI Strategy for Leaders: Simplification, Not Replacement

Every AI conversation in 2026 seems to start with "will it replace my team?" Keran reframes the question entirely. She's not excited about AI replacing people. She's excited about AI simplifying legacy systems and eliminating the operational toil that traps your best people in firefighting mode.

At Canadian Tire, she's seen AI measurably reduce incident volume, cut operational costs, and free up engineering talent to focus on strategic work. The pattern is repeatable: identify the repetitive, high-volume operational tasks that drain your senior people — alerting, log triage, change validation — and let AI handle them. Then redeploy those engineers toward the work that actually moves the business forward.

But she cautions that AI success depends on something most organizations haven't addressed: breaking down silos. AI doesn't fix organizational dysfunction — it amplifies it. If your data is siloed, your AI will be siloed. If your teams don't talk to each other, your AI models won't connect either. For Alberta businesses exploring how to get started with AI, this is the first principle to internalize — get your people aligned before you get your models deployed.

This resonates with a trend we're seeing across every advisory engagement at Code To Cloud: the companies that extract the most value from AI aren't the ones with the biggest budgets or the fanciest models. They're the ones with the clearest communication between business and technology teams. AI is a force multiplier — and it multiplies whatever you already have, including dysfunction.

Why "Full-Stack Thinkers" Are the Most Valuable Tech Professionals in 2026

Perhaps Keran's most forward-looking insight is about the evolution of tech roles. The traditional specialist — deep in one domain, narrow everywhere else — is giving way to what she calls the "full-stack thinker."

This doesn't mean everyone needs to be an expert in infrastructure, networking, security, tooling, and application development simultaneously. It means professionals who can connect those domains — who understand enough about each layer to see how a decision in one area ripples through the entire stack — are becoming disproportionately valuable. They're the ones who get pulled into architecture reviews, incident bridges, and strategy meetings, because they can see the whole picture and explain it to anyone in the room.

Keran calls them "rockstar technologists" — not because they're showboats, but because they can shift between infrastructure and app-layer conversations in the same meeting, instantly grasp the security implications of an architecture decision, and then translate all of it for a business stakeholder in language they actually understand. They're not the loudest person on the team. They're the one everyone calls when something breaks across boundaries.

This maps directly to the shift we see in the cloud career landscape: hiring managers are increasingly looking for T-shaped (or even π-shaped) candidates who combine deep expertise in one area with working knowledge across the full stack. Whether you're building your career or planning your skill development for 2026, the message is clear — breadth matters more than ever, and the people who can bridge domains will lead the next era of technology.

5 Tech Leadership Lessons You Can Apply This Week

Keran's advice isn't theoretical — these are practices she's refined across 20+ years and four organizations. Here's what you can start doing immediately:

• Learn the full stack — not to be an expert in every layer, but to understand how the layers interact. When a crisis hits, the person who can trace the problem across infrastructure, networking, and application layers is the one who solves it.
• Invest in communication — learn to translate. Use analogies. Keran compares explaining AI to non-technical audiences to describing everyday tasks: "It's like having someone clear your driveway before you wake up." Simple language wins.
• Build trust before you need it — the pizza approach. Informal problem-solving sessions, shared meals, hallway conversations. These aren't "nice to haves" — they're the infrastructure of a high-performing team.
• Embrace discomfort — take the role that feels too big. Volunteer for the project no one wants. These stretches compound into leadership capability faster than any course or certification.
• Be a translator, not a gatekeeper — the best leaders bridge the gap between technical and business teams. They don't protect their domain — they open it up.

Listen to the Full Conversation with Keran McGuire

This post captures the key themes, but the full 45-minute conversation goes deeper — including Keran's specific stories from her time at Microsoft, how she approaches mentoring rising leaders, her take on whether certifications still matter, and what she thinks the next wave of AI will actually change about how we work.

Catch the full episode on the Code To Cloud podcast — wherever you listen:

• Listen on Spotify
• Listen on Apple Podcasts
• Watch on YouTube

If this episode resonated, you might also enjoy our conversation with Tim Warner on the future of IT certifications — another deep dive on career strategy in the AI era.

FAQ: Tech Leadership, Communication, and Career Growth

How can I improve my communication skills as a tech leader?

The single highest-leverage communication skill in technology is translation — reframing technical concepts in the language your audience already speaks. Don't describe the architecture; describe the business outcome. Use analogies: Keran compares explaining AI to non-technical audiences to describing someone clearing your driveway before you wake up. Practice the problem → approach → outcome storytelling framework in every status update, email, and presentation. If the CFO asks about cost, lead with cost — not microservices. The goal isn't to impress; it's to move decisions forward.

What are the most valuable tech skills in 2026?

The most in-demand tech professionals in 2026 are full-stack thinkers — people with deep expertise in one area (infrastructure, security, application development) combined with working knowledge across the entire stack. This T-shaped or π-shaped profile is what hiring managers are actively seeking. Beyond technical breadth, the skills that differentiate are stakeholder management, storytelling, empathy, and the ability to trace a problem across infrastructure, networking, and application layers when a crisis hits. Pure specialists are being replaced by connectors.

How do you build a high-performance culture in a technology organization?

High-performance culture starts with trust built before it's needed. Keran McGuire's "pizza approach" — sharing meals, informal conversations, and off-site interactions — creates the psychological safety that Google's Project Aristotle research identified as the #1 predictor of team performance. Specifically: create an environment where anyone can contribute ideas regardless of seniority, act on that input visibly, and be transparent about challenges. Culture isn't a mission statement on the wall — it's the accumulated result of how people treat each other under pressure, every day.

Why is cross-disciplinary knowledge important for tech careers?

As organizations adopt AI, cloud-native architectures, and integrated platforms, the problems that matter most span multiple teams and systems. Cross-disciplinary technologists can trace an incident from the application layer through networking to infrastructure, communicate the business impact to a non-technical stakeholder, and propose a fix that accounts for security implications — all in the same meeting. These "rockstar technologists," as Keran McGuire calls them, become the most valuable people on any team because they bridge the gaps that specialists cannot.