Project Management Roles

Project management isn’t a supporting role. A COO once said, “Project managers are there to support the real work.” I almost laughed. Then realized they were serious. Let’s get this straight... Project managers don’t just schedule meetings and send reminders. We lead. We align. We deliver. We don’t support the work. We drive it forward. We create clarity when there’s chaos. We bring people together who don’t usually speak. We protect the team from distractions so they can focus. We turn vision into outcomes, and outcomes into impact. Think about the biggest wins in your organization. If a project manager was involved, chances are high that success wasn’t an accident. Instead, it was: → Intentional → Coordinated → Tracked → Delivered We’re not behind the scenes. We’re at the center of it all. What’s the most common misconception you’ve heard about project managers? 𝐄𝐱𝐜𝐢𝐭𝐢𝐧𝐠 𝐧𝐞𝐰𝐬: We’re launching a new podcast called 2 Disgruntled PMs.

"I'll delegate when I find good people." Translation: "I'll trust them after they prove themselves." Plot twist: They can't prove themselves until you trust them. Break the loop. Delegate to develop. Here's how: 1️⃣ What should you delegate? Everything. Not a joke. You need to design yourself completely out of your old job. Set your sights lower and you'll delegate WAY less than you should. But don't freak out: Responsibly delegating this way will take months. 2️⃣ Set Expectations w/ Your Boss The biggest wild card when delegating: Your boss.  Perfection isn't the target. Command is.  - Must-dos: handled  - Who you're stretching   - Mistakes you anticipate   - How you'll address Remember: You're actually managing your boss. 3️⃣ Set Expectations w/ Yourself  Your team will not do it your way.  So you have a choice: - Waste a ton of time trying to make them you?   - Empower them to creatively do it better?  Remember: 5 people at 80% = 400%. 4️⃣ Triage Your Reality - If you have to hang onto something -> do it.  - If you feel guilty delegating a miserable task -> delete it.  - If you can't delegate them anything -> you have a bigger problem. 5️⃣ Delegate for Your Development  You must create space to grow. Start here:   1) Anything partially delegated -> Completion achieves clarity.  2) Where you add the least value -> Your grind is their growth.  3) The routine -> Ripe for a runbook or automation. 6️⃣ Delegate for Their Development Start with the stretch each employee needs to excel. Easiest place to start: ask them how they want to grow. People usually know. And they'll feel agency over their own mastery. Bonus: Challenge them to find & take that work. Virtuous cycle. 7️⃣ Set Expectations w/ Your Team  Good delegation is more than assigning tasks:  - It's goal-oriented  - It's written down  - It's intentional When you assign "Whys" instead of "Whats", You get Results instead of "Buts". 8️⃣ Climb The Ladder Aim for the step that makes you uncomfortable:     - Steps over Tasks  - Processes over Steps  - Responsibilities over Processes  - Goals over Responsibilities   - Jobs over Goals  Each rung is higher leverage. 9️⃣ Don't Undo Good Work Delegating & walking away - You need to trust. But you also need to verify. - Metrics & surveys are a good starting point. Micromanaging - That's your insecurity, not their effort. - Your new job is to enable, motivate & assess, not step in. ✅ Remember: You're not just delegating tasks. - You're delegating goals. - You're delegating growth. - You're delegating greatness. The best time to start was months ago.  The next best time is today. 🔔 Follow Dave Kline for more posts like this. ♻️ And repost to help those leaders who need to delegate more.

Most leaders don't have a delegation problem. They have a trust problem. Here's the 3-Tier Delegation Matrix that helped me scale teams from 5 to 70: 1. Comfort Zone Tasks The Trap: You're hoarding quick wins, stunting your team's growth. Reality Check: Those tasks you do in your sleep? They're holding you back. Action: List 3 tasks you excel at but need to let go. Today. 2. Growth Zone Tasks The Gap: Your team's potential is bottlenecked by your hesitation. The Truth: Controlled failure builds stronger teams than constant success. Action: Assign one ambitious project this week. Be their safety net, not their ceiling. 3. High-Stakes Tasks The Fear: "Nobody can handle this but me." The Irony: You learned through trial by fire. Why deny others the same growth? Action: Pick your most guarded responsibility. Transfer complete ownership. The Simple Framework: • Routine tasks → Delegate immediately • Growth tasks → Support actively • Critical tasks → Trust completely This isn't theory. This matrix helped me run autonomous vehicle operations across 5 countries. When ex-nurses crushed PR roles and engineers became operations leads, I learned: Trust doesn't just delegate work. It unlocks potential. Your team is more capable than you think. The question is: are you brave enough to prove it? (P.S. What's the hardest task you've delegated, and how did it go?)

Project Managers are not reminder machines Yes, we follow up Yes, we ask for updates Yes, sometimes we politely chase people like it is an Olympic sport But the real job is not to remind everyone about everything forever The real job is to build a system where work does not disappear. - Where owners are clear. - Where deadlines are visible. - Where dependencies are tracked. - Where risks are discussed early. - Where decisions do not live only in someone’s memory. - Where “I thought someone else was doing it” happens less often. Because if a project only moves when the PM sends another reminder, that is not project management That is babysitting with a dashboard. A good PM does not just ask: “Any updates?” A good PM asks: “Why do we need so many reminders in the first place?”

Project managers are still wildly misunderstood. Here are 9 myths about PMs that need to stay in 2026. And what reality actually looks like on real projects. Anyone can be a PM. → Anyone can try, but not everyone can manage risk under pressure. PMs just pass messages. → Good PMs stop messages from turning into fires. PMs are replaceable once things are running. → Running projects still need constant steering. PMs are just meeting organisers. → Meetings are the surface; risk management is the real work. If nothing is wrong, PMs are not needed. → That silence usually means they are doing their best work. Good tools replace PMs. → Tools do not resolve conflicts or make decisions. PMs exist to protect management. → PMs protect outcomes, timelines, and teams. A good PM never misses a deadline. → A good PM tells you early why it might slip. PMs are optional. → Until deadlines slip, budgets bleed, and blame starts flying. Strong PMs are invisible when things go well. And painfully obvious when they are missing.

💡 When a Project Manager Becomes Just a Meeting Scheduler & Note Taker… Too often, PMs are reduced to glorified coordinators—scheduling calls, sending minutes, chasing updates. While these tasks are part of the role, that’s not project management. 👉 The Impact: • Strategic Blind Spot: Time is spent on admin instead of risk management, planning, and decision-making. • Demotivated PMs: Talented professionals feel undervalued when their role is limited to clerical work. • Weakened Delivery: Projects lose the benefit of having someone who can see across silos, align stakeholders, and drive execution. • Stakeholder Drift: Without a PM leading strategy, teams fall into “task mode” instead of achieving outcomes. ⚠️ A Project Manager is not just a note taker. They are: • The bridge between vision and execution. • The voice of reason in chaos. • The guardian of timelines, budgets, and risks. • The strategist who ensures delivery creates value. 🔑 The reminder: If your PM is spending 80% of their time on scheduling, you’re underutilizing one of your most valuable assets. Empower them to lead, not just to log.

Most managers can't delegate... Because they never learned the difference between giving orders and giving ownership. I spent years micromanaging. Checking every detail. Reviewing every decision. Controlling every outcome. I thought I was being thorough. Really, I was being a bottleneck. The shift happened when I stopped delegating tasks... And started delegating outcomes. Here's the difference: Task delegation sounds like: "Send this email by 3pm with these exact words." Outcome delegation sounds like: "We need the client to understand the delay. Handle it." One creates robots. The other creates leaders. If you want a team that runs without you, master these fundamentals: 1/ Give clarity on three things ↳ The role (who owns what) ↳ The goal (what success looks like) ↳ The deadline (when it needs to happen) Everything else? Let them figure it out. 2/ Set standards, not steps ↳ Define quality expectations ↳ Share the non-negotiables ↳ Then get out of the way 3/ Create feedback loops, not surveillance ↳ Weekly check-ins beat daily hovering ↳ Ask "What obstacles can I remove?" ↳ Not "Show me everything you did" 4/ Match tasks to strengths ↳ Give analytical work to analytical minds ↳ Give creative projects to creative people ↳ Stop forcing square pegs into round holes 5/ Start with the outcome ↳ "Here's what we need to achieve" ↳ Not "Here's 20 steps to follow" ↳ Let them own the how 6/ Give context, not just commands ↳ Explain why it matters ↳ Show how it fits the bigger picture ↳ People work harder when they understand impact 7/ Coach through mistakes ↳ Don't jump in to fix everything ↳ Ask "What would you do differently?" ↳ Build their judgment, not dependency The formula is simple: Clarity + Trust + Feedback = A team that runs without you. Most managers think delegation means less work. It doesn't. It means different work. Better work. The work only you can do. Stop managing tasks. Start developing people. 👊 What’s one task you’re delegating this week? 💬👇 --- ♻️ Repost to help a manager stop being a bottleneck ✚ Follow Cory Blumenfeld for more entrepreneurial insights and motivation. I'm on a mission to inspire 1M everyday people to start their own business and find their voice in the process.

Behind the Scenes with Project Managers: What We Really Do! Understanding Project Managers: Clearing Up Common Misconceptions Being a Project Manager often means wearing many hats, yet our role is frequently misunderstood. Let’s clarify some of these misconceptions with real-world examples that reflect the human side of our work. 1. "Project Managers Just Tell People What to Do." Truth: We’re facilitators who bring people together. During a critical digital transformation project, my role wasn’t about assigning tasks—it was about empowering teams, resolving conflicts, and ensuring everyone felt supported. The outcome? A solution everyone could be proud of. 2. "Anyone Can Be a Project Manager." Truth: It’s a role that requires empathy, foresight, and resilience. When a vendor backed out of a project unexpectedly, I had to step up, calm anxious stakeholders, and guide the team toward a creative solution. This isn’t a job—it’s a responsibility. 3. "Project Managers Don’t Need to Understand Technology." Truth: We’re the bridge between technical and non-technical worlds. In a FinTech project, understanding the challenges developers faced helped me advocate for their needs while ensuring client satisfaction. Project management isn’t just about plans and deadlines—it’s about people, collaboration, and making a positive impact. Have you had similar experiences? Let’s connect and share stories. #ProjectManagement #Leadership #Collaboration

🔥 79 % of tech projects that crashed had one thing in common— 💻 their PM never left the spreadsheet. After 15 years rescuing stalled roll-outs, I’ve learned a blunt truth: Project managers who stay “hands-off” become bottlenecks. ☑ Myth PMs are there to facilitate, not “do the work.” ↳ Reality When blockers hit at 3 a.m., your team needs a problem-solver, not a meeting scheduler. → Actionable insight A PM who understands the codebase, supply chain, or CAD file can spot risk before it ambushes the Gantt chart. ✗ Mistake #1 – Hiding behind admin ↳ Correction: Spend one hour a week pairing with the dev, designer, or analyst. → Benefit: You speak their language—and earn instant credibility. ✗ Mistake #2 – “That’s not my job” ↳ Correction: Jump in when urgency calls (even if it’s QA testing or data cleanup). → Benefit: Momentum stays unbroken; trust skyrockets. ✗ Mistake #3 – Planning in a vacuum ↳ Correction: Validate every estimate with the person who’ll execute it. → Benefit: Fewer sandbagged timelines, smoother delivery. ➟ Key takeaways ☑ Shadow the work ↳ insights > assumptions. ☑ Learn the basics of your team’s tooling → anticipate blockers early. ☑ Model accountability—roll up sleeves when it matters. ☑ Speak value, not tasks—align hands-on action with business outcomes. What surprised me most? The moment I joined a late-night log-file dive, the dev team stopped calling me “the admin guy” and started calling me backup. Your turn: How hands-on should a PM be? Share one moment you stepped in—or wished someone had—below. 👇 #ProjectManagement #HandsOnLeadership #TechDelivery #PMO #TeamTrust