IT Governance

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?

Disclaimer: This is a high-level PM management experience on the view of agile projects in a strategic portfolio management situation. I'm a full agile believer------------------------------------------------------------------------------------------------------------------------------------There are few things more ironic than watching Agile turn back into Waterfall.After managing ~90 projects and programs per year in an IT portfolio, I've seen almost every "Agile transformation" playbook.Same pattern every time:New frameworksNew rolesMore ceremoniesMore alignment layersAnd yet… delivery slows down.Why?Because somewhere above your beautiful two-week sprints, a CFO is sitting at a spreadsheet doing a very Waterfall thing: approving an annual budget.Your team ships in quarters. Finance plans in fiscal years. And somewhere in a risk register nobody reads, a contingency budget is quietly held back "just in case", which means the money only flows when the year (or the deadline) is almost over.But it's not just the money.It's the deadlines too.In portfolio planning, every project gets a delivery window, because projects don't exist in a vacuum and resources have to be aligned on a multi year project roadmap. They exist to support something. A product launch. A market entry. A regulatory deadline.The new product goes live in October? Then the cybersecurity project must be done by September. Not "done enough." Done.Suddenly your "Agile" cybersecurity team isn't prioritizing based on risk or value anymore. They're prioritizing based on a date that was set in a portfolio spreadsheet eight months ago — before anyone wrote a single user story.The budget flows down like a waterfall. The deadline flows down like a waterfall. The scope follows quietly behind.Congrats. Your Agile project just became a Waterfall project in a hoodie.Real agility isn't a framework. It's what happens when funding, decisions, and delivery all move at the same speed.Everything else is just stand-ups with extra steps.