Technology Conference Keynote Speaker Brian Dickinson

Technology conference keynote speaker Brian Dickinson presenting on leadership, resilience, and performing under pressure.

In This Industry, the Plan Always Changes

Every industry says it is changing fast. Technology is the one where it’s simply true: the platform gets replaced, the roadmap gets rewritten, a new capability lands and rearranges the market mid-quarter, and the team that shipped last year’s product is asked to become a different team by next year. Change fatigue in a technology room isn’t an attitude problem. It’s arithmetic — too many pivots, each one announced as the last.

Brian Dickinson speaks to that room from two directions at once. Before the Navy, he worked in technology himself, in senior systems engineering roles — he knows this industry’s working life from the inside. Since then, he has spoken for organizations including Microsoft, Cisco, and Dell. And his material comes from the other half of his record: six years as a U.S. Navy Aviation Rescue Swimmer, and an Everest climb that became a test of exactly what a technology team faces — performing when the environment changes faster than the plan.

When the Instruments Went Dark

On May 15, 2011, Brian’s climbing partner turned back ill roughly 1,000 feet below the summit of Everest. Brian continued alone and reached the top at 29,035 feet — where snow blindness took his vision. The seven-hour descent that followed — alone, low on oxygen, by feel along the fixed ropes — is the highest solo blind descent ever recorded.

A climber’s eyes are his primary instrument: route, weather, footing, distance — all of it arrives through them. Losing them at the top of Everest is the extreme version of something technology people know well: the moment the tools and information the plan was built around stop being available, and the work still has to get done. What carried Brian down was not a backup instrument. It was the layer underneath — training, judgment, and decision discipline, built before he needed them and not dependent on conditions cooperating.

Four Rules for Working Through Constant Change

These rules come from Navy rescue missions and the Everest descent. Stated here for an industry where the environment changes faster than the plan — as the disciplines that hold underneath the technology.

1. Trust your training. Tools get replaced; fundamentals don’t. Every technology career is a stack of platforms that will eventually be deprecated — what carries a professional from one to the next is the layer underneath: preparation, craft, and judgment, built before they were needed. On the descent, Brian’s hands worked climbing hardware by feel because the motions had been trained years earlier, in calm conditions, until they held without the instrument he had lost. Teams work the same way. When the new platform, the new model, the new strategy arrives half-documented, people fall back on whatever was actually built beforehand. That is what this keynote points a tired room back to: the capability is real, and it was earned.

2. Control what you can. A technology team’s uncontrollable list is long: the market, the competitor’s launch, the platform shift, the reorganization decided three floors up. The actionable list is shorter and entirely theirs — their craft, their preparation, and how they respond in the first week after the announcement. Change fatigue is what happens when a team’s energy goes to the first list: arguing with decisions already made while the work it can still move waits. The rescue discipline is sorting, done fast and honestly — name what’s actionable, work that list, and stop feeding the rest.

3. Don’t let panic make the decision. Panic in a technology organization has a recognizable shape: roadmap whiplash, a strategy reversed every time a competitor ships; a pivot announced to calm a bad quarter rather than to win the next one; cuts made to look decisive. Each is a decision made to relieve anxiety instead of to solve the problem — and each one costs the team more change, which is the thing it was already tired of. The standard from rescue work is plain: assess the situation honestly, decide with what’s known, commit, and keep moving. In an industry built on iteration, that discipline is familiar. This keynote gives the room a language for applying it to itself.

4. When the plan changes, adapt and keep moving. In technology the plan doesn’t change once; it changes as a standing condition — the pivot, the deprecation, the strategy shift, the team redrawn around a new priority. The descent drew the only line that matters: the route changed completely, more than once; the objective never did. Teams stall when they treat each change as a verdict on the last plan — or on themselves. The alternative is plainer: say what has changed, re-route, and put the next effort on the new route. The objective is still the objective.

What a Technology Audience Takes Away

  • A frame for change as the standing condition. Not change as an interruption of the real work — in this industry, adapting is the real work, and the keynote treats it that way.
  • The layer that doesn’t get deprecated. Judgment, preparation, and decision discipline — what a team falls back on when the tools and the plan change at the same time.
  • Sorting for tired teams. Change fatigue answered with focus, not pep: the actionable list named, the rest let go.
  • A standard for the first week after the announcement. Assess honestly. Decide with what’s known. Commit. Keep moving — agreed before the next pivot arrives.
  • An honest word for rooms after a hard stretch. Reductions and reorganizations are addressed as what they are. The material meets the room where it is — including the people who remain, and the work still in front of them.

Every keynote is customized to your audience after a pre-event call with Brian.

See Brian in Action

Watch the reel to see how the rescue missions and the descent play to a room that lives on ship dates — and the framework the room keeps for the next change.

Programs for Technology Audiences

Surviving the Impossible — The Everest story told for technology audiences: a plan overtaken by conditions at the worst possible moment, and the disciplines that replaced it. Built for technology conferences and company-wide events — rooms that need one shared story about performing when the environment won’t sit still.

Calm in the Chaos: Leadership & Resilience Under Pressure — Drawn from Navy rescue missions, where preparation, communication, and composure are crew disciplines. For technology leadership teams and summits: how leaders get a team ready before the pressure arrives, and keep it functioning through a pivot, a launch, or a reorganization.

Brian’s individual keynotes can also be delivered as live virtual presentations for remote and hybrid events.

Running a sales kickoff? See Brian’s sales kickoff speaker page. Leadership programs in depth are on his leadership keynote speaker page, and the resilience material in depth on his resilience keynote speaker page. For the full program list — including Faith, Resilience & Healing, presented with his wife JoAnna Dickinson for churches and faith-based audiences — see the main Everest keynote speaker page.

Who Books a Technology Keynote

Technology conferences and industry summits programming a general-session keynote. Technology company events that need one message for a mixed room — engineering, product, and the business side together. Technology leadership summits setting direction for a year of change. Organizations working through a pivot, a platform shift, an AI-driven reorganization, or the stretch after a reduction — rooms that don’t need to be told change is exciting, and need something sturdier than that.

What Event Planners Say

“That was one of the best keynotes we’ve ever had!”

Brian Blair, SVP, Linde

“The best keynote we’ve had for this event! People traveled from 8 states to see you.”

Derek Borkholder, Event Coordinator, Midwest Classic

“Your message was exactly what our team needed. You impacted lives today, Brian!”

Bob Toney, SVP, American Family Insurance

“An incredible story!”

Anderson Cooper, CNN

Booking Brian: What to Expect

  • Dates are confirmed on a first-come basis, and popular seasons fill early. Technology conference seasons and internal-event calendars fill early too — if your event is soon, ask anyway; availability changes, and virtual dates are often possible on shorter notice.
  • Customization starts with a pre-event call: Brian aligns the message with your theme and with where your organization actually is in its change — a launch, a pivot, a reorganization — and builds the application from that conversation.
  • Virtual delivery is available for Brian’s individual keynotes, for distributed technology teams and hybrid conferences.
  • Fees are quoted per event, based on the event, audience, format, and location — contact Brian’s team to discuss availability and receive a personalized proposal.

Frequently Asked Questions

What does a technology conference keynote speaker do?

A technology conference keynote speaker gives a mixed technology room — engineering, product, leadership, the business side — one shared framework for performing through constant change. Brian’s keynotes draw on Navy rescue operations and his solo Everest summit and blind descent, and turn them into four working rules: trust your training, control what you can, don’t let panic make the decision, and adapt when the plan changes.

Brian’s record is the Navy and Everest. Why book him for a technology audience?

Because he came from this industry first. Brian worked in technology, in senior systems engineering roles, before his Navy service — and he has since spoken for Microsoft, Cisco, and Dell. The keynote isn’t about technology; it’s about the layer underneath it that every technology team runs on: preparation, judgment, and decisions made while the environment changes faster than the plan. That material was tested where a wrong decision had immediate consequences, which is why it holds up in rooms that discount outside speakers quickly.

Does Brian give an AI talk or a technology-trends keynote?

No — and planners should know that up front. Brian doesn’t present trend forecasts or product content, and he doesn’t speak as an analyst on where the technology is going. What he speaks to is the human side of working through technological change: what a team does when the platform shifts, the strategy pivots, or the reorganization lands. If your program includes trend and product sessions, this keynote sits alongside them as the shared-experience session — the one about the people doing the changing.

Can Brian speak to a team that has been through layoffs or a reorganization?

Yes — that is one of the rooms this material was built for. A team that has lost people and is being asked to take on the next thing anyway does not need to be told the change is exciting. The pre-event call covers where your team actually is, and the keynote meets the room there: honest about what changed, focused on what’s still actionable, and respectful of the people who remain and the work in front of them.

Does Brian offer virtual or hybrid keynotes for technology events?

Yes — Brian’s individual keynote programs are available as live virtual presentations for distributed technology teams and hybrid conferences, and virtual dates are often possible on shorter notice than in-person dates.

How far in advance should we book?

As early as you can — dates are confirmed first-come and popular seasons fill early. But if your event is close, ask anyway. Availability changes, and a virtual keynote can often be arranged on a shorter timeline.

Book a Technology Conference Keynote

Tell us about your event using the form below and you’ll receive a personal reply. You don’t need a confirmed date or a final budget to start the conversation — send what you have.

Optional — helps us tailor a proposal

Brian Dickinson is the bestselling author of Blind Descent and Calm in the Chaos, and host of the Calm in the Chaos podcast. Full bio, speaker reel, and all programs: Everest Keynote Speaker — Brian Dickinson

Scroll to Top