IT Communication/ Translation

Most meetings fail before they even start.Not because of bad ideas. Not because of the wrong people in the room. Because the person running it didn't do the work beforehand.Ever had a hard time getting a decision out of a meeting? Ever watched stakeholders glaze over somewhere around slide 14 — knowing full well your actual idea is on slide 25?That's not an attention problem. That's a preparation problem. Here's the uncomfortable truth:If you walk into a meeting trying to convince people of something — you've already lost and end in an  discussion about what the actual problem is rather then talking about the solution. Convincing is not a meeting activity. Convincing is homework.The meeting is where you collect the signature on work that was already done in the hallway, the Slack thread, the quick call on Tuesday, and the coffee you had with the one stakeholder you knew was going to push back.Align before the meeting. Use the meeting to decide.That's the whole playbook.And when you do it right, something almost magical happens:👉 The meeting ends early 👉 Decisions happen fast 👉 Nobody fights you in the roomBecause the resistance didn't disappear. You just dealt with it before anyone opened a calendar invite.For decision meetings, my rule is simple:3–5 slides. No more.Structure:Outcome → "We are going to do this."How → The approach, the solution, the planDecision → What needs approval, right now, in this roomThree lines per slide. Visuals over text walls.If your slide needs more than three lines to explain — you haven't finished thinking yet.And if you're on slide 25 before you get to the point — you haven't respected the room.But the real work happened before slide one.You talked to the key stakeholders earlyYou understood their concerns before they became objectionsYou incorporated their input so they already see themselves in the solutionYou gave them time to digest — so they're not processing and deciding at the same timeThat last part matters more than people realize.Nobody makes good decisions cold. When someone hears an idea for the first time in a meeting, their first instinct is protection, not progress. They poke holes. They ask for more time. They "want to take it offline."But when they've already had the conversation? When they've already raised their concern and seen it addressed?They walk in ready. The meeting becomes a formality — in the best possible way.This is also how you respect everyone in that room.Your developers, your consultants, your strategy leads, your junior team members — they're not there to watch a 45-minute presentation. They're there because their judgment matters.Pre-alignment means when they arrive, the context is already shared. Their energy goes toward the decision — not catching up, not sitting politely through slides that don't concern them.Great presenters inform. Great leaders close.The debate, the brainstorming, the messy back-and-forth — that belongs in the channels you already have.Do the work before the meeting. Keep it to 5 slides. Walk out with a decision.That's the difference between people who run meetings and people who actually get things done.The slide 25 line is the funniest and most relatable moment in this version — everyone has lived that meeting. Want me to now write the short series intro lines for all three posts so they feel like a cohesive LinkedIn series?

Let me disappoint you:Your meetings are not fixing your delivery problem.They're often making it worse.The biggest issue isn't the tools. It isn't the framework. It isn't even the team.It's the calendar.Instead of clarity, we get:1-hour discussions that needed 10 minutesCircular updates where everyone nods and nothing movesRooms full of people waiting for a decision that never comesBlockers are "raised." Concerns are "noted." Actions are "taken offline."You have Slack. You have Teams. You have email, shared docs, and approximately 14 other ways to communicate before anyone opens a calendar invite.The brainstorming, the context, the messy back-and-forth — that belongs there. Not in a room with 10 people on the clock. By the time you're in the meeting, everyone should already know the problem. The meeting exists for one thing only: the decision.That's it. Walk in prepared. Walk out with an answer.In fast-paced environments — manufacturing floors, large enterprise IT, high-stakes portfolios — I learned something brutally simple:👉 A good update is 3 sentences.What happenedWhat we're doing about itHow we prevent it next time  / What do we learn from itIf I need more detail, I pull the right person into a follow-up. Everyone else goes back to work.Because here's what nobody talks about enough:The people most hurt by bad meetings aren't the managers sitting in them.It's the developers. The consultants. The strategy leads. The junior team members who came in with a sharp idea, waited 55 minutes for their moment, and then watched the meeting end without a single decision being made.That's not just a time problem. That's a talent problem.You hired experienced people. You brought in consultants. You have junior developers who are closer to the actual code than anyone in that room. And then you trap them in a loop of alignment theater — pulling them away from the exact work they were hired to do, and the exact thinking they were hired to bring.Great meetings don't just save time. They signal respect for the people in the room.Modern IT has normalized:Endless alignment before any actionBrainstorming that should have been a Slack threadOwnership so shared it belongs to nobodyThe truth is uncomfortable:Meetings have become the work, instead of enabling the work.Come prepared. Decide fast. Let people go build things.Execution doesn't need more discussion. It needs clarity, a decision, and one person responsible for it.Everything else is just a very organized way of going nowhere.