Hunter Milligan

Staying Sharp in the Chaos

two sessions

9:00 AM MDT

The scope keeps expanding. The team still needs direction. Leadership wants more output. And the AI landscape is moving faster than anyone can fully keep up with. For a lot of technical leaders, somewhere along the way the job quietly shifted from leading to just keeping up. Decisions get made from whatever state you happen to be in when the next thing lands — and it's been costing you focus, clarity, and probably sleep.

Most leadership training addresses what to do. Less often does it address the skill of staying clear-headed while you're doing it — under real pressure, in real time, with a team and boss looking to you for answers. This full-day workshop is built around that gap. You'll work through real pressure situations — the kind you actually face — and develop practical skills for staying grounded when they spike, so you can lead with steadiness instead of reaction. You'll learn as much from the honest conversations in the room as from the content itself.

You'll leave with skills you can use in those moments — the ones you already know need them. More of your best thinking available when it matters most. The kind of leader you already know you can be, more of the time. Getting more done with less of the grind that's been wearing you down

Delegation Without Guilt: How to Hand Off Work and Actually Let It Go

10:30 AM MDT

AI has increased what your team can produce. Which means more output to review, more decisions to make, more places where everything runs through you. The leverage is real — and so is the growing pile of work that was supposed to be off your plate. Part of that is systems. But a bigger part is the pull to just do it yourself — because it's faster, because it's easier than explaining it, because if something goes wrong you want to have been the one who touched it last. That pull is costing you. Not just time — the kind of work you actually want to be doing, and the headspace to do it well.

This is a working session — you'll work through real delegation situations, yours or someone else's, and learn as much from the people in the room as from the content. You'll leave with the skills to hand off work with trust, clarity, and accountability — one concrete delegation you've been avoiding, with a plan to execute in upcoming week, and the foundation to keep building on it. Less bouncing back to your desk. More of your time on the work that only you can do. The kind of leader whose team actually runs without them in every conversation.

Who's Accountable When AI Wrote the Code?

Staying grounded when you're responsible for what you can't fully audit

1:00 PM MDT

You've basically stopped writing significant amounts of code. AI does it — you check it, direct it, and sign off on it. The leverage is real and so is the uneasy feeling that comes with it. You're now responsible for output you didn't fully produce, at a volume you can't fully review, while leadership pushes for more speed. And nobody — not your org, not the industry — has figured out yet who's actually on the hook when something goes wrong.

Here's the honest truth: nobody has a clean answer yet — not your organization, not the industry, not the people writing the frameworks. So this session doesn't pretend to have one either. Instead, we'll pool what's actually working for people in the room, surface what's already helping teams stay more on top of it, and build something more useful than a handed-down answer. You'll also develop the skill to become calmer and more clearheaded when you're buried in pull requests and competing demands — and when something does go wrong. You'll leave with concrete approaches for navigating the gray zone and more practical ways to handle the pressure of leading when the rules are still being written.

The Tech Leader's Guide to Difficult Talks That Actually Work

Including the AI conversations nobody wants to have

3:00 PM MDT

Leadership is publicly pushing hard on AI — and your team is feeling it differently. Some are vocal about it, others aren't saying what's really on their mind. Meanwhile the classic hard conversations haven't gone away: missed deadlines, underperforming teammates, stakeholders pushing too hard. You're probably avoiding at least one conversation right now — not because you don't know it needs to happen, but because the last time you tried something like it, logic didn't land the way you expected — and the situation got harder, not easier.

This session gives you a practical framework for debugging communication the same way you'd debug code — and the skill to manage what makes these talks hard in the first place. The anxiety before, the rumination after, the pull to over-explain or go silent. You'll work through real situations in the room — yours or someone else's — and leave with more than you expected from the people around you. You'll leave with the skills to walk into difficult conversations with steadier confidence — and walk out with more clarity and less conflict. The conversation you've been avoiding becomes the one you're ready to have.

Who Am I If I'm Not the One Writing the Code?

Making sense of the shift nobody warned you about

9:00 AM MDT

You got into this because you loved building things. With your own hands, your own mind, your own code. There was a craftsman feel to it — wrestling a hard problem to the ground, the satisfaction of elegant code, the identity that came with being the person who could figure it out. That identity took years to build. And here's the part that stings: being technically savvy didn't protect you from this one. If anything, it meant you understood exactly what was happening — and couldn't stop it. In the last few months, quietly and quickly, the ground shifted. You're still here. You're still valuable. But something about how you relate to the work has changed — and nobody's really talking about it.

This session names what's actually happening — because naming it is the first step to working through it. Some in the room are energized by the shift. Others have fear about it. Most are somewhere in between and haven't had a safe place to say so. Through honest conversation with the people around you, you'll start to separate what's actually changing from what's staying true about who you are — and leave with a clearer sense of where you stand, and what to build on, while the ground keeps moving

Leading When You Don't Have the Answers

How to stay calm and credible in an AI-accelerated world

11:00 AM MDT

A few months ago you had a decent handle on what your team was building — or you were building it yourself. Knowing things is how you got here, and it still matters. But everything your team touches is moving faster than your ability to fully audit it, and the output is coming faster than anyone can fully evaluate. Some days that's exhilarating. Other days your team looks to you for answers — and you're not sure you're the right person to ask anymore.
This session gives you practical skills to stay functional and credible when the answer isn't there yet — not as a workaround, but as something you can build and rely on. You can use them in the 90 seconds before you walk into a conversation, or in the moment someone asks you something you can't answer yet.

Through real scenarios and honest conversation with the people around you, you'll leave with something steadier than certainty — the ability to lead clearly in the moment, even when the answer comes later.