How to Run Effective Problem-Solving Meetings That Get Results in 25 Minutes
I’ve been running problem-solving sessions with construction companies for over two decades. I thought I understood why they worked.
Last week, a guy named James taught me something I’d never considered.
We were in a session with eight construction leaders — different divisions, different project types, different levels of experience. I had a blank piece of paper with one question at the top: “In what specific ways can we improve the productivity of the projects we are building?”
Twenty-five minutes later, we had unanimous agreement on exactly what to focus on and a clear plan to make it happen.
When I asked them how long this normally takes, here’s what they said:
“Three days.”
“I was gonna say days.”
“Seven years.”
“Several meetings.”
I’ve seen this result hundreds of times. But I’d never heard anyone articulate why until James said this:
“There wasn’t a feeling of competition. Didn’t feel like I had to come up with the best idea. It was just my idea.”
That hit me. I’ve been doing this for twenty years, and I’d never thought about it that way.
Why Most Construction Meetings Fail
When meetings go sideways, we blame two things: “I suck at facilitating meetings” or “My people suck.”
I’ve heard this from project managers, superintendents, VPs, and CEOs. They walk out of another circular, pointless meeting and think the problem is them or their team.
It’s not.
Meetings are not a waste of time because you suck and your people suck. They’re a waste of time because you don’t have the right structure.
That’s liberating. Structure is fixable. Structure doesn’t require you to become a different person or fire your team. It just requires you to run the meeting differently.
What “Chaos” Really Means
When I asked these leaders to describe their worst meeting ever in one word, I got: Chaos. Unorganized. Unproductive. “Circles with catch-22 after catch-22.”
One of them — Michael — gave me the real story: “There were two alphas with opposing viewpoints, and neither one would back down.”
I’d bet money you’ve seen this play out.
When you let a meeting become an open forum before you’ve created the conditions for productive discussion, you get ego battles. Whoever speaks first shapes everyone’s thinking. People conform to the loudest voice. Strong personalities hijack everything.
The structure prevents that. And the psychology behind it is fascinating.
The Independence Paradox
Mark noticed something I’d never had articulated so clearly: “You kept us independent. You asked for our input without having a discussion about it. And then directed us to a vote, again without having a discussion about it.”
We think collaboration means discussion. It doesn’t — at least not at first.
Premature discussion introduces three problems:
Anchoring bias. Whoever speaks first shapes how everyone else thinks about the problem. Once an idea is out there, people unconsciously orient around it — even if it’s not the best idea in the room.
Social pressure. People conform to the loudest voice or the highest-ranking person. Your quietest engineer might have the best solution, but she’s not going to contradict the VP who just spoke with confidence.
Ego battles. Those “two alphas with opposing viewpoints” that derail everything. Once people stake out positions publicly, they defend them. The meeting becomes about winning, not solving.
When you have people write ideas privately before anyone shares, you bypass groupthink entirely. Everyone’s thinking independently. The ideas that emerge represent actual diversity of thought, not one person’s idea that everyone else feels pressure to agree with.
Eliminating Competition in Meetings
That’s what James was getting at with his comment. Let me say it again because it’s that important:
“There wasn’t a feeling of competition. Didn’t feel like I had to come up with the best idea. It was just my idea.”
Think about what happens in typical meetings. People are performing. They’re calculating: Will this idea make me look smart or stupid? What will the boss think? What will my peers think?
That calculation consumes mental energy that should go toward solving the problem.
The structure removes performance anxiety. Contribution is the standard, not brilliance.
Everyone shares two ideas. Nobody’s idea is “better” until the group votes. And by then, the ideas are on the board — they belong to the group, not to individuals protecting their egos.
When there’s no competition, people offer their actual thinking instead of their safest thinking. That’s where the good ideas come from.
Engagement Through Anticipation
Chris noticed something else: “You kept us engaged. I was thinking, am I going to come up with another answer, because you’re asking the questions.”
Mark connected it to reality: “Human psychology. Short attention span. But you kept us engaged.”
I have a house full of kids. I know about short attention spans.
The two-minute brainstorming bursts. Rapid-fire rotation around the room. Asking for one idea at a time. It all keeps people in “ready mode.”
The moment someone checks out mentally, you’ve lost their contribution. And in construction leadership, the person who checks out might be the one with the insight that saves the project.
When you know you might be called on at any moment, you stay present. When you know you only have to contribute one short idea at a time, the barrier to participation drops. The combination keeps everyone mentally in the room — even the introverts who normally fade into the background.
The Ownership Transfer
There’s an old truth in leadership: People work harder for their ideas than they do for yours.
Mark put it perfectly: “It puts the confidence on the team that it’s their idea, and they’re gonna execute on their idea. Instead of your idea, and you’re trying to push a rope instead of pulling a chain.”
When the leader dominates the meeting with their own solutions, the team’s job becomes compliance, not commitment. They’ll nod along, then drag their feet on execution because they never bought in.
If you’re running the meeting, go last with your ideas. Or don’t share them at all if they’re already on the board.
You may even wait until all the ideas are up, look at the list, and realize your ideas are already there — articulated by your team. That’s the goal. Let them build the solution. They’ll fight for it because it’s theirs.
This is why, when I asked for final commitment — “Would you support these priorities?” — I got unanimous agreement. Not because I convinced anyone of anything. Because the process led them to conclusions they arrived at together.
The Problem-Solving Meeting Structure
This is what happened in those 25 minutes:
Frame the problem as a specific question. Not “Let’s talk about productivity.” We started with the question already written: “In what specific ways can we improve the productivity of the projects we are building?”
The word specific does the work. As Aaron said: “If you nail down the specific ways instead of the generalized ways, it’s gonna help narrow down what you’re actually working on.”
Vague problems generate vague solutions that never get implemented.
Individual brainstorm for 2 minutes. Everyone writes — privately — as many ideas as they can. No sharing yet. No filtering. The time pressure forces focus. And because no one’s sharing yet, there’s no social pressure influencing what people write.
Select your top two. Each person marks their two best ideas. The first filter happens individually, before anyone speaks. By the time anyone opens their mouth, they’ve already prioritized their own thinking.
Go around the room, one idea at a time. First idea from each person going one direction. Then reverse for the second idea. The person who went last gets to go first on round two.
One idea at a time keeps things moving. And here’s an important facilitation point: people will want to share two ideas at once. Stop them. “Just give me your first idea.” You control the pace.
Clarify and consolidate. Ask clarifying questions: “Tell me more about that.” Reword when needed, but ask permission. Blend duplicates. The goal is a clean list, not a bloated one.
Vote. Each person gets votes equal to one-third the total ideas. Fifteen ideas means five votes each. Votes must be distributed — no stacking on one idea.
One participant, Matt, noticed something interesting: “I think if everyone only had one vote, we’d have a different result. I kind of like having five tokens because if I had one, I’d panic-pick the wrong one.”
Multiple votes reduce the randomness and let real patterns emerge.
Confirm commitment. Ask directly: “If we focus on these priorities, would you support that? Yes or no.”
One question to full commitment in 25 minutes.
Why You’ll Get Buy-In Almost Every Time
I’ve run this process for two decades. Ninety-nine percent of the time, I get unanimous agreement at the end.
The agreement isn’t imposed — it emerges.
Everyone contributed. Everyone voted. The priorities that rise to the top represent genuine group consensus, not one person’s agenda that everyone else reluctantly accepts.
The only times I don’t get agreement are when someone’s unclear on what we’re deciding, or occasionally when there’s a genuine, principled disagreement. Both are rare.
From Decision to Action: The One-Page Plan
Getting agreement is half the battle. The other half is making sure it actually happens.
I come from the simple school of planning. I don’t like dusty binder planning — where you bring in a high-paid consultant, spend hours putting together a plan, get a binder, put it on your shelf, and it collects dust. You do nothing with it.
I use a one-page format:
Rally Cry — A phrase everyone remembers. If I woke you at 3:30am and asked what you’re focused on, you could say it. When the Allies invaded Normandy, everyone from the generals to the guys dying on the beach knew the rally cry: “Beat Germany.” For a construction company I work with, it was “Own the cost.” For this session, we landed on “Great production.”
Areas of Fierce Focus — Two to four priorities that support the rally cry. These come directly from your top-voted ideas.
Critical Numbers — The vital few metrics that tell you if you’re winning. Not twenty KPIs. Just the ones that matter. In our session, the group debated whether “160 feet of pipe per day” or “cost per unit” was the right metric. That debate itself was valuable — it forced clarity about what actually matters.
Single Owners — One person accountable for each focus area. Not a committee. One name.
As Michael said: “So you don’t have to go to multiple people to get an answer.”
Eisenhower was the supreme commander of D-Day. On June 5th, 1944, he wrote a letter taking complete responsibility for the failure of the invasion — before it even happened. He put it in his desk drawer. One person, ultimately accountable. That’s what you need for each area of fierce focus.
The Real Lesson
I walked into that session thinking I was there to teach. I walked out realizing James had given me language for something I’d been doing for twenty years without fully understanding.
No competition. Just contribution.
That’s what removes the performance anxiety. That’s what gets people’s actual best thinking instead of their safest thinking. That’s what makes the difference between a meeting that wastes everyone’s time and one that produces real commitment in 25 minutes.
Structure creates the conditions where people can actually think.
Get the structure right, and your people will surprise you.
Get the Full Framework
The step-by-step process and facilitation techniques I used in that session are detailed in my free ebook, Kick-Ass Meetings.
It’s 21 pages. No fluff. You can read it in one sitting and use it in your next meeting.
Download Kick-Ass Meetings free here →
Meetings are the lifeblood of effective construction companies. There’s no reason yours have to suck.
