PMO Best Practices

𝗜 𝘀𝗽𝗲𝗻𝘁 𝟲 𝗺𝗼𝗻𝘁𝗵𝘀 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗮 𝗣𝗠𝗢 𝘁𝗵𝗮𝘁 𝗻𝗼𝗯𝗼𝗱𝘆 𝘂𝘀𝗲𝗱. 🥴 Beautiful governance framework ✅ Fancy project templates ✅ Weekly status meetings ✅ Zero actual adoption. Teams kept working around us. Leaders stopped showing up. And I was basically running a compliance theatre that added zero value. That's when I realized: I was building for perfection, not for people. 𝗛𝗲𝗿𝗲'𝘀 𝘄𝗵𝗮𝘁 𝗜 𝗹𝗲𝗮𝗿𝗻𝗲𝗱 𝘁𝗵𝗲 𝗵𝗮𝗿𝗱 𝘄𝗮𝘆: Most PMOs fail because we start with process instead of problems. We design the "perfect" intake form before we know what decisions we're supporting. We build dashboards before we understand what questions leaders actually need answered. (Look at me 🥹 spending months on a framework nobody asked for) 𝗦𝗼 𝗜 𝘁𝗵𝗿𝗲𝘄 𝗶𝘁 𝗮𝗹𝗹 𝗼𝘂𝘁 𝗮𝗻𝗱 𝘀𝘁𝗮𝗿𝘁𝗲𝗱 𝗼𝘃𝗲𝗿. This time? I led with questions: ↳ What decision is keeping you up at night? ↳ What's the biggest bottleneck in delivery right now? ↳ If this PMO could solve ONE thing, what would change everything? And I listened. Like, really listened. 𝗧𝗵𝗲𝗻 𝗜 𝗿𝗲𝗯𝘂𝗶𝗹𝘁 𝘁𝗵𝗲 𝗣𝗠𝗢 𝗮𝗿𝗼𝘂𝗻𝗱 𝟯 𝗰𝗼𝗿𝗲 𝗳𝗼𝘂𝗻𝗱𝗮𝘁𝗶𝗼𝗻𝘀: ☝🏼 𝟭/ 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗰𝗹𝗮𝗿𝗶𝘁𝘆 𝗯𝗲𝗳𝗼𝗿𝗲 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 Your PMO can't prioritize work if the organization hasn't defined what matters. I stopped building intake processes and started facilitating priority conversations. We defined criteria. We killed projects that didn't fit. We said no with evidence. Turns out, a simple scoring model beats a 47-field intake form every single time. ✌🏼 𝟮/ 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻-𝗳𝗼𝗰𝘂𝘀𝗲𝗱 𝗴𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 Nobody wants another status meeting. I replaced weekly reporting theatre with monthly decision sessions. One agenda item: What choice do we need to make today? Attendance went from 40% to 95%. Because we were finally making decisions instead of just talking about work. 🤟🏼 𝟯/ 𝗣𝗲𝗼𝗽𝗹𝗲 𝗼𝘃𝗲𝗿 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 The best PMO framework is the one that actually gets used. I stopped designing for perfection and started designing for adoption. Simple templates. Clear accountabilities. Just enough structure to add value without adding friction. 𝗥𝗲𝗮𝗹 𝘁𝗮𝗹𝗸: The last time you built something in your PMO that people actually wanted to use? That's usually the moment things start working. 𝗥𝗲𝗮𝗱𝘆 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝗮 𝗣𝗠𝗢 𝘁𝗵𝗮𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘂𝘀𝗲? Drop "GUIDE" in the comments, and I'll send you the Ultimate PMO Setup Guide. It's the exact roadmap I use to help organizations build value-driven PMOs from scratch. 𝗣.𝗦. What's the ONE thing your PMO could do differently that would actually change how work gets done? --- Found this helpful? Repost ♻️ to help another PMO leader who's building process when they should be building trust.

Autonomy is often wrongly confused with independence. This mistake negatively affects accountability. People sometimes mistakenly think that giving people autonomy means leaving them completely to their own devices (this is independence). In the organizational sense, autonomy is not the opposite of structure—it’s the freedom to operate WITHIN a structure that supports continuous improvement and accountability. A Lean mindset and approach helps leaders to understand how to foster BOTH accountability and autonomy. Lean leaders do this by intentionally moving away from making people feel like they are "being held accountable" (which feels imposed) and inspiring them to "take accountability" (a sense of ownership that naturally fosters autonomy). Here’s how you can adopt this approach in YOUR team: 🟢 Be clear about goals, roles, and responsibilities: Use tools like RACI charts or visual management boards to clarify who does what. 🔴 Define success together: Involve the team in setting performance standards or KPIs so they have a say in what they’re working toward. 🟣 Encourage regular 1:1 check-ins and team huddles: create spaces for discussing challenges without fear. 🟡 Engage people in problem-solving: Use structured techniques and Kaizen to involve the team in addressing inefficiencies. 🔵 Ask for their ideas first: Instead of directing what needs to change, coach them with powerful questions like, “What do you think is the best next step?” 🟤 Use visual management: Team dashboards or Kanban boards make progress visible, reduce micromanagement and highlight areas needing attention. 🟠 Review metrics as a team: Make this part of regular meetings, so progress and accountability are a collective effort. ⚫ Own your commitments: If you make a mistake or miss a deadline, acknowledge it openly. ⚪ Model humility: Admit when you don’t have all the answers and seek input from the team. (This makes people feel valued!!) 🤔Reflection time for leaders... Are you balancing structure and flexibility in your team? Which of the above could you act on to shape a culture of autonomy?

𝑳𝒆𝒂𝒅 𝒘𝒊𝒕𝒉 𝒄𝒍𝒂𝒓𝒊𝒕𝒚, 𝒏𝒐𝒕 𝒄𝒉𝒂𝒐𝒔… As a leader, it's tempting to try to track every detail, but this approach can create bottlenecks and stifle team autonomy. Instead, focus on building systems that enable informed decision-making while empowering your team to work independently. 🎯 Identify Key Issues: Determine the few critical issues that require your direct attention, such as: ✅ - Revenue targets ✅ - Client retention ✅ - Compliance risks 🎯 Set Clear Escalation Guidelines: Establish clear guidelines for when issues should be escalated to you, such as: ✅ 1. New expenses over a certain threshold ✅ 2. Significant changes in project scope or timeline ✅ 3. Potential reputational risks 🎯 Use Dashboards and Written Updates: Implement dashboards and written updates to stay informed without creating unnecessary meetings or micromanaging. This could include: ✅ 1. Bi-weekly or monthly progress reports ✅ 2.Key performance indicators (KPIs) tracked on a dashboard ✅ 3.Regular check-ins with team leads 🎯 Enable Autonomy: By building systems and setting clear guidelines, you enable your team to work autonomously while still maintaining visibility and control. This approach: ✅ Fosters trust and accountability ✅ Encourages decision-making at the team level ✅ Frees up your time to focus on strategic priorities 🎯 Stay Informed, Not Overwhelmed: By focusing on key issues and using systems to stay informed, you can make better decisions and drive business outcomes without getting bogged down in details. Curious to know…What's your approach to building systems and enabling autonomy in your team?

Lack of Oversight ≠ Autonomy It’s easy to mistake a hands-off approach from product leaders as “autonomy.” And when leaders step in to provide guidance, it can feel like autonomy is being taken away. But the truth is that Autonomy isn’t the absence of leadership. It’s the ability to make informed, impactful decisions within a framework of clarity and trust. This distinction is what builds great product teams. What Great Product Teams Do Differently ✅ Context over control: Product leaders provide the "why"—clarity on vision, strategy, and problems to solve. This enables teams to focus on discovering and delivering impactful solutions. ✅ Coaching over micromanaging: Leaders act as thought partners, helping teams navigate risks (value, usability, feasibility, and business viability) while encouraging ownership. ✅ Focus on outcomes, not outputs: Empowered teams aim to solve real customer problems and deliver business results, not just tick boxes on a roadmap. What Autonomy Is Not ❌ Isolation from strategy: Teams need alignment with broader goals to make meaningful progress. ❌ Freedom from collaboration: Success is built on diverse perspectives, not siloed decision-making. ❌ Lack of accountability: True autonomy involves ownership, not operating without guardrails. When product leaders invest in context and coaching, teams transcend misunderstood autonomy to become empowered, high-performing teams that deliver real impact.

When should a leader step in with an authoritative decision—and when should they step back to let the team take ownership? It’s one of the hardest balancing acts in leadership. A) If you have too much control? You kill autonomy. B) If you keep your distance? You risk misalignment & poor execution. The key isn’t about choosing one over the other, but balance out how when to step in or step back. But who to do it practically?   Here’s how: 𝟭. 𝗙𝗶𝗿𝘀𝘁, 𝗰𝗹𝗮𝗿𝗶𝘁𝘆 𝗶𝘀 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴. If the team doesn’t fully understand their mission, why they exist, and what they are driving forward, they will default to hesitation or misalignment. 𝟮. 𝗦𝗲𝘁 𝗰𝗹𝗲𝗮𝗿 𝗮𝗰𝗰𝗼𝘂𝗻𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆. Who owns what? What’s the expected outcome? Do we share the same definition of a high-quality output? What requires leadership input vs. what should be entirely autonomous? These should be set before stepping back. 𝟯. 𝗞𝗻𝗼𝘄 𝘄𝗵𝗲𝗻 𝘁𝗼 𝘀𝘁𝗲𝗽 𝗶𝗻. Authority should be reserved for high-risk calls. This is where investment, strategy, or major business impact is at stake. Everything else you let the team experiment and iterate first. 𝟰. 𝗖𝗿𝗲𝗮𝘁𝗲 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝗱 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗹𝗼𝗼𝗽𝘀. Teams need timely insights to course-correct, through structured debriefs, post-mortems, and transparent discussions. Independence works best when there’s a rhythm of learning, feedback, and iteration. --- At its core, leadership isn’t about control. It’s about smart autonomy, helping aligning teams to the bigger picture while enabling them to execute rapidly. How do you manage this balance in your teams? Curious to hear your take, comment below 👇 or repost ♻️ --- I’m Hugo Pereira, co-founder of Ritmoo and fractional growth operator. I’ve led businesses from €1M to €100M+ while building purpose-driven, resilient teams. Follow me for insights on growth, leadership, and teamwork. My book, Teamwork Transformed, launches early 2025.

Everyone says PMOs should be lean. I say: most PMOs are too lean to function. They’re flat, fragile, and frustrating. No structure. No clarity. Just chaos in disguise. I’ve worked with PMOs of all shapes and sizes. Here’s what I see far too often: - A single PMO lead juggling strategy, planning, reporting, and governance - No separation between delivery support and portfolio oversight - Everyone’s a firefighter, no one’s a planner - Tools are underused. Templates sit untouched. Progress reports are late—or skipped And the worst part? Executives don’t see the value. Because value delivery needs structure—not just effort. Whether you’re a team of 2 or 20, the best structure divides ownership across three clear layers: 1. Strategic Layer - Focus: Aligning projects to business goals - Roles: PMO Director, Portfolio Manager Why it matters: This layer ensures your PMO isn’t just delivering—it’s delivering what matters. 2. Tactical Layer - Focus: Converting strategy into coordinated execution - Roles: Program Manager, PMO Analyst Why it matters: This is your engine room. It keeps work prioritized, resourced, and on track. 3. ️ Operational Layer - Focus: Enabling tools, processes, and reporting -Roles: PMO Coordinator, PPM Admin, Reporting Lead Why it matters: They keep the lights on, the data flowing, and the dashboards credible. This structure isn’t just for big teams. Even if you’re small, the layers still apply—just with shared roles and part-time hats. Here’s how to apply the three-layer model—even if you’re a 3-person team: 1. Sketch your PMO tasks across the Strategic, Tactical, and Operational layers 2. Assign owners—even if someone wears two hats 3. Communicate the model to sponsors and project teams 4. Use it to identify gaps—so you can build a stronger business case for support It’s not about job titles. It’s about visibility, focus, and balance. Why This Matters Without structure: - Governance dies - Prioritization drifts - You become the admin desk instead of the value driver But with structure: - Your PMO is seen - Your PMO is trusted - Your PMO delivers If your PMO feels chaotic, the solution might not be more people. It might be better structure. 🔁 Follow me for more practical PMO frameworks. And if this sparked an idea, repost it so more PMOs stop flying blind. #PMO #ProjectManagement #JBFConsulting

Project managers deal more with people and politics than with tech. If I were advising a younger version of myself, these are the ten lessons I’d pass on. 1. Culture decides outcomes before plans do. Ignore posters and slide decks. Watch what gets rewarded and what gets punished. (Edgar Schein wrote about that). 2. Managing people is harder than managing work. Plans are predictable. People are not. Most problems come from people, not tools (remember Jerry Weinberg’s Second Law of consulting?). 3. Build allies long before you need them. Do not wait for a crisis. Work gets done through relationships, not org charts. 4. Make things simple for the people deciding. Your job is to reduce confusion. If people cannot explain it simply, they cannot decide. 5. Focus on what changes, not what ships. Activity feels productive, but only outcomes create value. If nothing changes, the work did not matter (Goldratt would ask this first. Read The Goal if you haven't). 6. Listen longer than feels efficient. People reveal constraints slowly. Good judgement starts with patience (that's classic Weinberg). 7. Choose your battles carefully. You cannot push on everything. Restraint often creates more influence than force (Drucker understood this). 8. Relationships matter more than process. Process works when trust exists. Without trust, process becomes theatre (Patrick Lencioni in Five Dysfunctions. It's a short book, and worth reading). 9. Learn how decisions really get made. Politics are not optional. Notice who influences outcomes and why (Mintzberg mapped this years ago). 10. Manage up with signal, not performance. Leaders need clarity, not volume. What changed, why it matters, what decision is needed (Andy Grove style). It took me years to learn, and a tremendous amount of reading. I hope you get value from these points. If you found this useful, then follow for more hard-earned lessons from the messy side of delivery.

𝗜 𝗱𝗼𝗻’𝘁 𝘁𝗿𝘂𝘀𝘁 𝗮𝗻𝘆𝗼𝗻𝗲 𝘄𝗵𝗼: 👎 Calls their PMO “the center of excellence” 👎 Calls every project “strategic” 👎 Calls project managers “just admin” And yeah…I’ve been guilty of all three. When I first started leading a PMO, I plastered “Center of Excellence” all over our presentations. We claimed every project was “tied to strategy” (even the ones nobody cared about). And I let people diminish my PMs to “note takers” and “meeting schedulers” without pushing back. 𝗧𝗵𝗲𝗻 𝗜 𝗴𝗼𝘁 𝘁𝗵𝗲 𝗰𝗮𝗹𝗹: A critical project delivered exactly on time and on budget…but it had zero business impact. We had executed "perfectly" - on something that didn’t matter. 𝗧𝗵𝗮𝘁’𝘀 𝘄𝗵𝗲𝗻 𝗶𝘁 𝗵𝗶𝘁 𝗺𝗲: 🔹Excellence without alignment is just noise 🔹“Strategic” without business buy in is wishful thinking 🔹And if your PMs aren’t treated as leaders, they’ll never drive change...just track it 𝗛𝗲𝗿𝗲’𝘀 𝘄𝗵𝗮𝘁 𝗜 𝗳𝗼𝗰𝘂𝘀 𝗼𝗻 𝗻𝗼𝘄: 🔹Linking every project to a measurable business priority 🔹Equipping PMs to influence stakeholders, not just update plans 🔹Killing vanity projects before they drain resources 🔹Reporting on business outcomes, not just tasks completed, and letting the business define the value Because the most dangerous PMOs aren’t the ones that fail visibly. They’re the ones that deliver flawlessly…on the wrong work. Your PMO shouldn’t be a “center of excellence.” 𝗜𝘁 𝘀𝗵𝗼𝘂𝗹𝗱 𝗯𝗲 𝗮 𝗰𝗲𝗻𝘁𝗲𝗿 𝗼𝗳 𝗰𝗹𝗮𝗿𝗶𝘁𝘆 𝗮𝗻𝗱 𝗶𝗺𝗽𝗮𝗰𝘁. And if your PMO can’t clearly answer, “Why does this project matter to the business?” It’s not managing projects. It’s managing busywork. If your PMO had to defend its last 5 projects to the CEO, what would the business say about the impact?

📌 Leadership Isn’t About Commanding Attention Most leaders believe their job is to drive performance, make decisions, and push for results. But leadership isn’t about being the loudest voice in the room. Real leadership is about creating the conditions for others to step into their own power. If your team only performs when you’re watching, you haven’t built a strong team. You’ve built a dependency. The best leaders don’t micromanage. They don’t dictate. They listen—not to respond, but to truly hear. Because when leadership is built on control, the system collapses when you step away. When leadership is built on trust, growth becomes inevitable. 📌 Five Leadership Shifts That Build Teams, Not Dependencies 1️⃣ Stop Leading Meetings—Start Leading Conversations ↳ If your team is waiting for you to speak, they’re not thinking for themselves. ↳ Ask better questions. The best leaders guide, they don’t just inform. ↳ Silence is a tool. When you stop filling every gap, others step in. 2️⃣ Replace Control with Clarity ↳ Micromanagement isn’t leadership—it’s a failure of systems and trust. ↳ Define outcomes, not tasks. Direction should be clear, execution should be owned. ↳ Shift from approvals to accountability. Let people own their decisions. 3️⃣ Build Systems That Outlast You ↳ If every problem still lands on your desk, you’re the bottleneck. ↳ Decentralize decision-making. A scalable team moves without constant oversight. ↳ Create principles, not policies. Rules enforce control, principles create autonomy. 4️⃣ Shift from Giving Answers to Guiding Thinking ↳ If your team relies on you for every solution, you haven’t built thinkers—you’ve built followers. ↳ Before answering, ask: “What do you think?” Force independent thought. ↳ Reward good decision-making, not just execution. The goal isn’t compliance—it’s ownership. 5️⃣ Measure Leadership by Absence, Not Presence ↳ The best leaders create environments where things run just as well without them. ↳ If stepping away for a month would collapse your team, you’re not leading—you’re managing. ↳ True leadership isn’t measured by control, but by what happens in your absence. 📌 The Bottom Line Leadership isn’t about attention—it’s about building something bigger than yourself. If your success depends on your constant involvement, you’re not leading—you’re holding things together. The real test of leadership? How well your team functions when you’re not there. What’s the hardest leadership shift you’ve had to make? Drop it below.

Many go-to ways leaders try to motivate people backfire over the long term. It’s a common trap: treating motivation as a matter of 𝘩𝘰𝘸 𝘮𝘶𝘤𝘩 — not 𝘸𝘩𝘢𝘵 𝘬𝘪𝘯𝘥. Deci and Ryan’s Self-Determination Theory (now supported by decades of research) showed that not all motivation helps people flourish. Motivation exists on a continuum: - 𝗔𝗺𝗼𝘁𝗶𝘃𝗮𝘁𝗶𝗼𝗻 – no intention or drive - 𝗘𝘅𝘁𝗲𝗿𝗻𝗮𝗹 – driven by rewards or punishments (e.g. bonuses) - 𝗜𝗻𝘁𝗿𝗼𝗷𝗲𝗰𝘁𝗲𝗱 – internalised pressure (guilt, ego, fear of failure) - 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝗶𝗲𝗱 – the work feels personally important - 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗲𝗱 – the work aligns with values and identity - 𝗜𝗻𝘁𝗿𝗶𝗻𝘀𝗶𝗰 – done for interest, enjoyment, or inherent satisfaction As work aligns more closely with a person’s strengths, values, and interests, motivation becomes more internal — and more powerful. This 𝘲𝘶𝘢𝘭𝘪𝘵𝘺 of motivation is associated with outcomes leaders and teams actually care about: - Higher engagement - Stronger performance - Reduced burnout - Lower turnover Many leaders already know this. Yet day-to-day leadership often tells a different story. Short-term pressures crowd out the slower work of cultivating intrinsic motivation. When motivation dips, the default response is familiar: add more pressure. It’s visible. It’s fast. And it creates a sense of control. But short-termism comes with heavy costs. Introjected motivation is psychologically costly. And decades of research show that poorly applied extrinsic incentives can 𝗲𝗿𝗼𝗱𝗲 𝗶𝗻𝘁𝗿𝗶𝗻𝘀𝗶𝗰 𝗺𝗼𝘁𝗶𝘃𝗮𝘁𝗶𝗼𝗻. Once crowded out, it is difficult — and sometimes impossible — to restore. So what can leaders do instead of defaulting to carrots and sticks? Here are six research-based principles to strengthen intrinsic motivation: 1️⃣ Affirm strengths Build shared understanding of individual interests, values, and strengths — and allocate work accordingly. 2️⃣ Enable job crafting Person–job fit isn’t fixed. Support people to shape aspects of their role around how they work best. 3️⃣ Empower autonomy Share decision-making power wherever possible. Autonomy is a core driver of sustained motivation. 4️⃣ Foster meaningful ownership Give people responsibility for areas they care about — not just tasks they’re assigned. 5️⃣ Nurture development Coaching, learning, and progression fuel motivation through growth and mastery. 6️⃣ Strengthen meaning and belonging Help people feel seen and heard. Show how their contribution matters. Meaning and belonging are built through many small, everyday experiences. When leaders design work around these principles, intrinsic motivation becomes less accidental — and far more likely. What common approaches to motivating teams do you like, or dislike? ——— I'm Reuben Rusk, PhD 💡 I help leaders enable human flourishing. ➕ Follow me + tap 🔔 for regular posts on leadership, well-being, and performance. 💬 Add a comment — or repost if this resonates with your network