Leading without authority a 24 month 5 million USD project
Case study: The leadership challenge
Hey, I’m Gabor and welcome to Agile Admiral weekly newsletter. Your Essential Resource for Project Management Excellence.
Each week I tackle reader questions about PMP preparation, how to implement PMP into real-life projects, and Senior Project manager career
For more: PMP Passing Rate | Power of Lessons Learned | Agile Paradox | What Project Managers and Chefs have in common?
Leading without authority is an ART, here are my personal thoughts.
And it is a project management power skill.
We lead 99% of the time without authority.
I don't have direct reports.
But, together with 10 project managers we navigating 40+ ships to move in the expected direction.
No matter your job title, You have to lead.
We are responsible for:
→ Drive changes
→ Delivering results
→ Keeping Stakeholders "happy"
→ Managing multi-diverse teams
All without formal authority.
Why is this important?
Because Project management is a life-long career path.
Each project will teach you something new.
Career path based on 3 x main pillars:
👉 Soft skills
👉 Project management hard skills
👉 Industry-specific skills/knowledge
Project Overview
Budget: USD 5 million
Duration: 24 months
Team size:
46 core team members
14 cross-functional stakeholders
2 external vendor partners
Project Type: Enterprise-wide digital transformation platform
Technology: Cloud-native architecture
The Leadership Challenge: Delivering Without Direct Authority
Problem Statement 1: Conflicting Stakeholder Priorities
Different departments have competing interests and conflicting expectations. The finance team demanded cost optimization, while the technology team wanted to deliver only the agreed solution. Marketing wants to speed things up, for example, feature deployment, whereas risk management demands extensive security protocols.
Solutions to clear the “mess”:
Collaborative Prioritization Framework
Developed data-driven prioritization matrix - features/requirements
Create a cross-functional governance committee - weekly/monthly governance
Implement a project scorecard “approach” - for a quick “reality check”
Value Mapping Workshops
Conduct quarterly workshops to align stakeholder objectives - this was on top of cross-functional governance
Focused interdependencies and cross-functional impact
Facilitate collaborative decision-making processes
Problem Statement 2: Communication Barriers and Working in“Silo’s”
We knew, from previous project lessons learned that a lack of consistent communication channels will lead to misunderstandings, delayed decision-making, and potential project risks. Different stakeholders have varied communication preferences and information needs that require a solution.
Solution to clear the “blur”:
“Adaptive” Communication Strategy
Sounds fancy but we just simply created a detailed communication plan(using what we learned via PMP certification). Also, we decided to group stakeholders.
Implemented a multi-channel communication approach (formal reports, interactive dashboards, brief video updates).
Created a centralized information repository.
Problem Statement 3: Resistance to Change and Technological Transformation
“Fear in every corner”. The fear of disruption created passive resistance to the digital transformation initiative. Team members(stakeholders) from legacy systems were hesitant about adopting new technologies and methodologies.
Solutions to manage “fear”:
Change Champion Network
Identified and empowered change champions across different organizational levels, which helped to minimize resistance.
Developed “change awareness” training session to gain trust and confidence
Created peer-to-peer knowledge sharing session - very simple, every week we hosted 1-hour open sessions where the Project was answering questions related to transformation
Incremental Value Demonstration
“Show and tell” approach. Sharing success stories to ensure people can relate to the change and outcome. It was a scenario based on showcasing project benefits.
Celebrate and widely communicate any successes.
Implementation Timeline and Approach:
Months 1-3: Foundation Building
Stakeholder interviews
Created a detailed impact-effort matrix
Technical feasibility
Resource requirements
Strategic alignment
Months 4-6: Governance Structure
Established a Cross-Functional Steering Committee
Representation from: Finance, Technology domain, Operations, Marketing/Sales, Risk Management
Created a dynamic prioritization dashboard
Months 7-24: Iterative Refinement
Quarterly recalibration of prioritization criteria
Tracking of project value delivery
Transparent reporting
Communication Strategy:
Month 3: Initial communication framework
Month 6: First iteration of adaptive platforms
Month 12: Advanced analytics integration
Month 18: Machine learning-enhanced personalization
Month 24: Comprehensive communication effectiveness review
Conclusion
Leading without authority is an art of transformation. It's about creating a shared vision, building trust, and demonstrating value beyond positional power.
Leadership is not about controlling people, but about creating an environment where everyone can contribute their best.
Join the next PMP Workshop Tomorrow
