How Vistage Issue Processing Helps Leaders Make Better Decis

---

I've sat in hundreds of Vistage meetings by now, and I can tell you the exact moment a room goes quiet in the good way. It's not when someone delivers a brilliant piece of advice. It's when a CEO who walked in convinced they had one problem realizes, out loud, in front of eleven peers, that they actually have a different one entirely.

That moment is not an accident. We build it on purpose. We call it issue processing, and it's the single most valuable thing that happens in my groups.

Here's the truth nobody tells struggling leaders: you're probably not stuck because you're lazy, or because you're out of ideas, or because you don't work hard enough. You're stuck because you're too close to it. You've been staring at the same problem from six inches away for so long that you've started mistaking the symptom for the disease. You think it's a sales problem. It's a leadership problem. You think it's a people problem. It's a role-clarity problem. You think the issue is out there, in the market, in your team, in bad luck. Most of the time, it's in how you built the thing, how decisions get made, or how you spend your Tuesdays.

Issue processing exists to close that six-inch gap.

When a member brings something to the table, I don't let them lead with a rant. I make them frame it. Almost always, it starts as a "How do I...?" question, and then they walk us through it: what's really going on, why it matters, what they're aiming for, what they've already tried, and — this is the part people resist — what they're actually afraid of.

That last piece changes the whole exercise. Fear dressed up as strategy is still fear. Getting a leader to name it out loud does more work than any framework I could hand them.

Once the issue is on the table, here's the rule that makes the whole thing work: the group only asks questions. No advice. No "well, what I'd do is..." dressed up as a question with a question mark stapled to the end. Just questions.

I know that sounds almost too simple to matter. It matters enormously. Most leaders walk in already sure they know what the real issue is. Half the time, they're wrong. The questions are what expose the assumption they didn't know they were making, the piece of context they left out because it didn't seem important, the thing they've been avoiding saying even to themselves.

I've watched a CEO walk in asking "How do I improve sales?" and leave the meeting with the real question sitting in front of him: "How do I stop being the bottleneck?" That's not a small shift. That's the whole game.

Only after the questions do we let the room offer a sharper version of the question — and I want to be clear, that is not wordsmithing. That is the work. Attack the wrong problem well and you'll still fail. Frame the right problem clearly and the path forward tends to show up on its own.

The leader can keep their original question or take the new one. Either way, by that point they're seeing the thing with less noise and more accuracy than they walked in with.

Only then — only then — do we let anyone give advice. And even that has a standard. Nobody gets to theorize. Nobody gets to make a speech. The suggestions that actually land sound like, "I hit something close to this. Here's what I did. Here's what worked. Here's what I'd do differently if I had it back." That's it. That's the bar.

This was never a debate club. Nobody's voting on the right answer. The whole point is helping one leader think more clearly and pick their next move — not winning the room.

Every issue processing session ends the same way: a commitment, to a specific action, by a specific date.

I've learned the hard way that this step is where good conversations either become real decisions or quietly die. Leaders are busy. Monday shows up. Something urgent eats the week, and the clarity from Wednesday's meeting gets buried under the fire that's burning today. A clear commitment, said out loud to eleven people who will ask about it next month, is what keeps that from happening. It's the difference between a good talk and an actual decision.

It works because it puts discipline around thinking, which is the one thing almost nobody does on purpose. It separates the presenting issue from the actual issue. It trades reaction for reflection. It brings in perspective from people who've already lived through the exact decision you're standing in front of. And it gives a leader enough structure to move from confused to committed in about sixty minutes.

But there's something underneath all of that, and it's the real reason I've built my whole second career around this room.

Leadership is lonely in a way most people outside of it never quite understand. You can be surrounded by employees, family, a full calendar, and still not have a single place where you can think out loud without managing someone's reaction to it. No place to test an idea before you're sure of it. No place where someone who has actually earned the right to speak will ask you the second and third question instead of just nodding.

Issue processing builds that room.

I've watched leaders walk in certain they had a tactical problem and walk out realizing it was a leadership problem all along. I've watched people ask for help with execution and leave with a clearer picture of their own blind spot than they've had in years. I've watched someone come in overwhelmed and tangled and reactive, and leave with one clean, specific move that changed where their business was headed six months later.

None of that happens because someone in the room was clever. It happens because the process works, and because the room cares enough to do the work with you.

That's the whole job, as far as I'm concerned. Not to impress anybody. To help a leader see clearly enough to make a better call.

If you're a CEO carrying something that's been stuck longer than it should be, I'd bet it's not because you need to try harder. It's because you need better perspective than the inside of your own head can give you.

That's what the room is for.