All Posts

We often use precision as a shield. We believe that if we show a number down to the second decimal point—$10,243,118.42—we prove we did the work. We think it makes us look like experts who have mastered the details. In reality, over-precision is a sign of fear. It is a Security Blanket we huddle under because we are afraid of being challenged on the strategy. If we give them enough math, maybe they won't ask about the mission. The Mute Factor In a high-stakes presentation, ev

Every year, brilliant technology initiatives, enterprise software migrations, and critical infrastructure plays die a quiet death in the boardroom. They do not fail because the engineering is flawed or the research is poor. They fail because technical leaders cannot bridge the gap between architectural complexity and executive execution. They walk into high-stakes meetings carrying too much technical weight, acting as transmitters of data rather than mentors of change. When y

I spent some time over the past few weeks vibe-coding two more domain-specific applications. Because they all live within the same golf ecosystem, they share common foundational elements: players, handicaps, and courses. I expected to more more quickly with common items already complete and functional. Unfortunately, that was not the case. As the builds grew more complex, even with prompts that asked to reuse where possible, it was obvious, things were beginning to drift. At

You have been there before. A prospect or a stakeholder says, "This sounds great, BZ, just send over the deck and I will socialize it with the team." It feels like progress. It feels like a win because you have gotten past the initial gatekeeper. In reality, it is a trap. When you send a high signal deck (one designed with intentionality and a specific narrative arc) you are sending a script. A script is a beautiful piece of architecture, but it is not a play. It requires a p

We spend weeks tweaking the hex codes on our charts and debating the placement of our logos. We build eighty-slide decks because we think completeness equals conviction. But the most important moment of your presentation doesn't happen while you are talking. It happens after you leave the room. The success of your mission depends entirely on whether your champion can retell your story to their boss without you there to help. If your narrative isn't sticky enough to survive a

Most business presentations suffer from a "Resume Dump." The presenter walks in, drops twenty years of history on the first slide, and expects the audience to care. It is an immediate spike of ego that usually results in an immediate drop in attention. When you lead with your pedigree, you aren't providing a reason to listen; you are providing a reason to check email. High-signal communication requires a different volume knob. You don’t start at a ten. You start with a nod an

There is a common fear that haunts high-stakes presentations: "If I do not show them everything I know, they will not think I am an expert." This fear is the primary driver of the Kitchen Sink deck. It is the 60-slide monster filled with every technical spec, every edge-case study, and every sub-bullet point imaginable. The presenter thinks they are being thorough. The audience thinks they are being buried. Authority is not the ability to show everything you know. It is havin

Business jargon is a fog. It settles over a conference room, making it impossible for your audience to see the Signal in your story. We use words like leverage, synergy, and optimization because they feel safe. They sound professional. But in high-stakes storytelling, "safe" is the enemy of the Sacred Contract of attention. If you lead with a cloud of corporate-speak, you aren't an Architect of a mission; you are a Transmitter of static. To clear the fog, you have to stop des

My journey with code began in 1984, squinting at a VIC-20 and teaching myself BASIC. Later that school year, I was handling physical punch cards in my first formal computer class. From there, the path was a classic tour of the era: Pascal and Fortran in college, followed by a deep dive into COBOL during my time at Andersen Consulting. The logic of programming always came to me naturally; the syntax was simply the hurdle to be cleared. As I progressed, the complexity increased

Most business updates fail because they treat numbers as the conclusion. We stand in front of a room, point to a green arrow on a bar chart, and announce a 20 percent increase in efficiency. We expect applause. Instead, we get a room full of people checking their watches. The problem is that a percentage, on its own, has no pulse. It is a static observation of a result. To move an audience, you have to stop reporting the number and start architecting the story of how it got t

If you walk into a boardroom and spend the first five minutes hunting for a dongle, wrestling with a power cord, or asking if anyone has a specific adapter, you have already told your first story. That story is about friction. Too many leaders treat the physical setup as a chore to be ignored until the formal meeting starts. They view it as a separate act from the presentation itself. But in high-stakes environments, the way you handle the environment is a proxy for how you h

In the world of high-stakes enterprise software, we spend hundreds of hours refining our slides, checking our metrics, and practicing our delivery. But we often ignore the most important three minutes of the entire engagement: the soundcheck. I am not talking about checking the microphones or the Wi-Fi. I am talking about the unscripted conversation that happens while the room is filling up and the last few people are joining the bridge. This is the narrative soundcheck. It i

A leader stands up and says, "Our company is built on transparency and simplicity." They then proceed to show a 75-slide deck filled with dense spreadsheets and opaque jargon. In that moment, the delivery is a failure. They have just proven, through their actions, that they are neither transparent nor simple. The moment of delivery is where your Foundational Why and your Urgent Mission must shake hands. If they do not, you are not just losing the deal; you are losing your bra

You have delivered the vision. Your Why? was vivid, your What If? was aspirational, and your Now What? was a model of clarity. The room nods. They agree with your logic. They appreciate your strategy. Then they do nothing. This is the momentum gap. In a high-stakes room, agreement is not the same as action. Most leaders fail to move the needle because they present the future as an optional destination. To create a mandate, you have to define the friction of the status quo. Yo

The trip is over. The villain won. If you read the first trip post, you know the mission: escape the Ohio winter for seventy degree fairways on Hilton Head Island, finishing the week at Harbor Town where the PGA just played (photo from the 18th tee box). The contrast was vivid. The stakes were clear. The story had everything it needed. Except the golf. The Scorecard Does Not Lie Let me be direct: the scoring was bad. Not a rough patch in the middle of the round bad. Consiste

The day this post lands I'll be in Hilton Head wrapping up the annual "Winter Sucks" golf trip, playing the final round of the trip at Harbor Town Golf links at the Sea Pines Resort. The trip name isn't just a clever bit of branding; it’s a mission statement. It identifies the villain (a brutal Ohio winter) and proposes a high-contrast solution (seventy-degree fairways where the PGA just played). In business storytelling, we often try to sell the "Golf Trip" without acknowled

Most business messaging is a list of what a company does, dressed up in the Sunday best of industry jargon. When you ask an executive for their Why, they often point to a mission statement on a lobby wall or a list of product features that they have mistaken for a purpose. They aren't lying: they are just looking at the tools of their trade rather than the friction those tools are meant to solve. The transition to a high-stakes narrative requires a pivot away from the comfort

It is the universal executive nightmare: the flight was delayed, the adapter is missing, the WiFi is down, and the projector is a relic that refuses to recognize your laptop. Most presenters in this scenario melt. They apologize profusely, they faff with cables for ten minutes, and they eventually deliver a hollow, distracted version of their pitch while staring at a blank wall. But for the practitioner who truly knows their material, that blank wall isn't a crisis. It is a c

We have all been in the meeting that should have been an email. These occur because the presenter has confused a topic with a purpose. Reviewing the Q3 Budget is a line item on a calendar. It lacks urgency, tension, and a clear "Now What." When you invite people into a room, you are entering into a Sacred Contract. You are borrowing their most expensive asset: time. To honor that contract, you must move beyond the logistics and define the mission of the room. The Diagnostic:

Most founders and technical leaders suffer from the Expert’s Blind Spot. They spend years perfecting architecture, reducing latency, and ensuring scalability. Naturally, when they stand in front of an audience, they want to talk about the things that were hardest to build. They build a fortress of specifications to prove their competence. However, your customers do not buy your architecture. They buy the version of themselves that your architecture makes possible. If you ar