IT Project Governance

💡 𝗦𝗰𝗮𝗹𝗶𝗻𝗴 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝗴𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 𝗱𝗼𝗲𝘀𝗻’𝘁 𝗺𝗲𝗮𝗻 𝘀𝗸𝗶𝗽𝗽𝗶𝗻𝗴 𝘁𝗵𝗲 𝗳𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀. Not every project needs the same level of documentation, oversight, or ceremony—but every project needs to meet a minimum bar. 🔸 If a project isn’t strategically aligned, why do it at all? 🔸 If it hasn’t gone through intake and prioritization, how do we know it’s the right work at the right time? 🔸 If no one is accountable for outcomes, are we really delivering value—or just activity? Overall, we must ensure to right-size governance that never abandons the essentials. 🔹 What should be true for all projects—regardless of size or complexity ✔️ Clear strategic alignment to an organizational goal or priority ✔️ Entry through a consistent intake and prioritization process ✔️ Visibility into effort and capacity (because small projects add up fast) ✔️ Defined outcomes and ownership for value and benefits realization Without these, a portfolio full of “small” projects can quietly overwhelm teams and dilute strategy. 🧩 From there, governance should scale based on risk, impact, and complexity. 🔹 Small / lower-complexity projects Governance should be streamlined—but not absent. ✔️ Strategic alignment confirmed during intake ✔️ Lightweight scope, effort, and timeline definition ✔️ Clear owner and success measures ✔️ Inclusion in portfolio prioritization to manage capacity Fast doesn’t mean unmanaged. 🔷 Medium-sized or moderately complex projects These require more front-end clarity to avoid downstream friction. ✔️ Clear outcomes tied to strategic objectives ✔️ Prioritization decisions that account for trade-offs ✔️ Cross-functional alignment and dependency awareness ✔️ Resource, risk, and change impact considerations Here, governance helps leaders choose intentionally. 💎 Large, high-complexity, or high-risk initiatives These projects demand rigorous front-end loading because the cost of getting it wrong is high. ✔️ Explicit strategic intent and value hypothesis ✔️ Formal intake, prioritization, and funding decisions ✔️ Robust business case and financial analysis ✔️ Strong sponsorship and decision forums ✔️ Integrated delivery, risk, and change management ✔️ Focus on strategic realization and benefits delivery The bigger the initiative, the more governance exists to protect value—not slow delivery. When orgs scale governance correctly, something powerful happens: ✨ Teams stay focused ✨ Leaders gain confidence in trade-offs ✨ Strategy moves from slides into execution ✨ PMOs become engines of strategy realization—not compliance 🤔 Where does your org struggle today—missing fundamentals or over-engineering governance? ♻️ Repost if this resonated with you! _________________ 🔔 Ring the bell to follow me on LinkedIn for topics on #ProjectManagement, #ProgramManagement, #PMO, #BusinessTransformation, #CareerTips, and #Leadership. #Prioritization #StrategyExecution #ProjectIntake #Governance #PortfolioManagement

Projects get completed. Transformation stays invisible. A CEO said this to me: "Rob, our projects are being delivered. Our teams are celebrating, which I love to see. But nothing is actually moving our bottom line." That pattern is everywhere. High activity. Strong delivery. Limited enterprise impact. Projects matter. They always have. Strong delivery matters too. Transformation fails without both. It's like a football team at the World Cup celebrating possession stats, while losing the match. Projects are designed to deliver: • scope and milestones • timelines and outputs • predictable delivery That discipline matters. Projects rarely govern things like: • decision rights and escalation authority • cross-functional orchestration • enterprise value realisation • executive sponsorship alignment • institutional learning and transformation memory • behavioural and cultural standards Those are enterprise governance problems. Not project management problems. And they need an owner. Value realisation can't sit with whoever delivered the project. It has to sit with someone accountable long after the project closes. Enterprise transformation requires a different governing logic. Not a replacement for projects. A layer above them. Projects stay the engine. Governance decides what the engine is building towards. Because transformation isn't about completing work. It's about changing how the enterprise creates and captures value. When governance becomes too project-led: • Teams defend scope • Learning is treated as deviation • Delivery replaces value • Projects close while capability fails to develop So dashboards stay green. Presentations look impressive. Recognition follows. But the business barely moves. Projects are essential delivery vehicles. So are programmes. But transformation requires enterprise-level governance, led by leaders who stay accountable for value, not just for delivery. That means governing: • value realisation • operational change • strategic adaptation • capability creation • ownership beyond project close This isn't a template to apply regardless of context. It's a governing logic, applied with judgement. Because the goal isn't to simply complete projects. The goal is to build an organisation that operates and performs differently over time. Get The Boardroom Brief Insights for leaders shaping transformation https://cxo.fm/news

Most digital transformations don't fail because of the tech. They fail because of the 'silent resistance.' Here is how we solved for that at a 20,000 FTE multinational. I used to Chair the Infrastructure Change Control Board (ICCB), a brainchild of their visionary MD. It was a perfect governance measure at a time when GRC practices were still maturing in the Indian corporate scene. ICCB did the following things right : ✅ Cross-Functional Representation : Including members from Sales, Transitions, HR, Security, Finance and Legal in addition to IT & Infra, it ensured that enterprise interdependencies were deliberated ✅ Risk based Tiered Ranking : Change requests mapped to the operational risk rating framework, thereby following a standard tiering methodology (eg Significant, Minor, Emergency) with associated actions, implementation schedules, controls ✅ Post Implementation Reviews : Regular status review of approved changes to ensure adherence to schedule, sign-offs, dependency checks and also analysis of delayed / failed projects. It was a classic case on how governance, done right, doesn't slow things down, but enhances efficiency by advance planning and analysis of the required steps and cross-dependencies, thereby reducing "rework" caused by failed changes. Why are the above important? Most of us have seen enthusiastically designed automation or transformational programs - technically sound, strategically aligned, having the governance structure in place and budget allocated - failing to execute.   The Real Barrier? The Human Element. It’s rarely a lack of skill. It’s often 'Silent Resistance' born from: ▪️Communication Gap : Often the leadership fail to communicate or explain the link of the 'why' of #automation to the broader business vision ▪️ Anxiety : There's angst of a probable downsizing due to automation, specially with AI projects, that stall adoption ▪️Exclusionary Engagement : When the support functions feel detached, they (quietly) deter implementation. Board & executive level success factors for transformation / automation programs include : ✔️ Communication Plan - customized to, but covering all stakeholders ✔️ Training - as a capability builder where people learn to improve through continuous usage, rather than passing an one-time assessment test ✔️ Accountability - Identify champions within each business function to guide, monitor, provide feedback and ensure successful adoption ✔️ Support - Set up a team to act on feedback and regularly report back improvements to the relevant governance council. ✨ An effective change management process is the bridge that can shift a departmental initiative into an 'Institutional Process'. What's your biggest hurdle in driving cultural acceptance for large-scale automation? Let's discuss in the comments.   #ChangeManagement #StakeholderEngagement #technology #DigitalTransformation #BoardGovernance

If your IT roadmap resets every time leadership changes, you don’t have governance. One day, everything’s running smoothly.  A new leader comes in, and suddenly your IT projects feel stuck. In regulated industries, every pause extends risk exposure. Most governance frameworks are tied to personalities instead of formally defined decision-making authority. When leadership changes, so does IT’s direction, because the strategy lived in a person, not a structure. UNLESS the structure is designed to withstand it. - Clear roles and responsibilities. - Clear documented decisions. - Accountability mechanisms that survive leadership turnover. All of these ensure continuity. No matter who’s in charge. Here’s how to get it right: 1️⃣ Map decisions clearly. Everyone knows the path forward. 2️⃣ Assign project owners. Accountability doesn’t vanish with a new leader. 3️⃣ Set visible priorities. Teams stay focused on what matters most. Implement these, and you won’t have to hit pause every time a new leader arrives. Would your IT roadmap survive a leadership transition tomorrow?

Technology is rarely the hard part. Most IT initiatives do not fail because the platform could not work. They fail because the organization around the platform was not ready to make it work. The tool gets approved. The vendor gets selected. The roadmap gets built. The architecture gets drawn. The funding gets secured. Then the real work begins. Who owns the outcome? Who makes the decision? Who manages the change? Who defines success? Who handles exceptions? Who keeps the process from drifting after launch? That is where many initiatives lose the race. Not in the technology. In the handoffs. In the unclear ownership. In the weak governance. In the missed adoption plan. In the gap between “go live” and “value realized.” Technology can be bought. Alignment has to be built. Strong IT organizations understand this: ✔️ They do not treat governance as paperwork; they treat it as the system that keeps decisions moving. ✔️ They do not treat change management as communication; they treat it as adoption architecture. ✔️ They do not treat ownership as a name on a slide; they make it operational. That is where Enterprise Architecture should show up. Not to slow the initiative down, but to make sure the technology, people, process, and decisions are aligned before the business is depending on the outcome. Because technology may launch the initiative, but people and governance determine whether it lands. What is the biggest non-technical hurdle you see in IT transformations today? Let me know below. 👇 #EnterpriseArchitecture #CIO #ChangeManagement

A common myth in transformation work: “Governance slows us down.” While PMing large transformations, I’ve heard this so many times. It’s usually said with a sigh in a steering committee meeting. People think governance means red tape, change control meeting, more meetings, gathering and critically challenging status updates, and layers of approvals. But here’s the thing: when it’s done right, governance is the opposite of slow. At the program level, it connects the dots. It makes sure the big bets actually tie back to strategy, budgets line up, and priorities don’t fight each other. At the project level, it sets the rules of the road. Who makes what decisions, how risks get escalated, and what success actually looks like. That clarity keeps teams from spinning their wheels or re-doing work. The result? Faster decisions. Less confusion. Fewer “do-overs.” And honestly, way more confidence from everyone involved. So no, governance isn’t about control for control’s sake. It’s about giving people enough structure so they can move without chaos. I want to hear from you. Have you seen governance speed things up or slow things down? Is it a necessary evil, or do you see the merit?

“Just make the call from the top” sounds efficient…until it isn’t. Early in my IT career, I thought strong governance meant central control. More alignment, more consistency, fewer mistakes. But I’ve since learned that centralized governance works only when a leader knows where to draw the line. You need a hybrid model: centralized where it matters, decentralized where it counts. With hybrid models, leaders say what needs to be built - but the “how” comes from the product team. They have the freedom to make decisions in real time, based on real user feedback. In practice, the best IT governance I’ve seen has three things: • Clear ownership of responsibilities • Alignment between business goals and tech execution • Documented decisions that avoid confusion down the line You keep architecture, security, and budget decisions at the org-wide level. Those impact everything. But execution belongs closer to the front lines because that’s where the context lives. That’s how companies move fast and build the right thing. For example, my team recently helped a homebuilder digitize the entire post-sale warranty experience AC units, appliances, everything - into a searchable, shareable digital folder. If you’ve ever been stuck reworking something because someone too far removed made a call based on guesswork, you know what I mean. Clarity without bureaucracy means governance that accelerates, not obstructs.

AI is already inside project delivery. Many teams still have not been told how to govern it. It is drafting status reports. Summarizing meetings. Shaping stakeholder messages. Helping project managers build risk registers, decision notes, and project communications. In many organizations, the governance has not caught up. That is the gap I set out to address in this independent practitioner white paper: Closing the AI Governance Gap in Project Delivery A Practical Playbook for PMs and PMOs Applying PMI's AI Standard My core argument is simple: AI should accelerate project delivery without weakening judgment, trust, or accountability. The tool can draft. The project manager decides. The PMO standardizes. Leadership governs. The paper lays out a practical six-step AI Governance Playbook: Select safe use cases Protect sensitive information Provide project context Review and challenge AI output Document human decisions Standardize repeatable workflows This is not about slowing teams down with bureaucracy. It is about extending the controls project managers already use for scope, risk, and decisions to a new kind of contributor. The paper also looks at where this is genuinely hard — and grounds the stakes in real cases, including the Replit production-database deletion and the Moffatt v. Air Canada ruling, where a company was held accountable for what its AI told a customer. After teaching these tools to hundreds of project managers, my takeaway is this: AI does not repair weak project management. It runs faster on whatever is already there. The full paper is attached. I welcome feedback from project professionals, PMO leaders, and AI governance practitioners. #ProjectManagement #AIGovernance #PMO #ArtificialIntelligence #PMI