The specifics of how you deliver really doesn't matter (to your executives)
From the Easy in theory, difficult in practice Blog
by Kiron Bondale
My musings on project management, project portfolio management and change management.
I'm a firm believer that a pragmatic approach to organizational change that addresses process & technology, but primarily, people will maximize chances for success.
This blog contains articles which I've previously written and published as well as new content.
Recent Posts
Leading Through Crisis Means Leading Through Context
"It's the end. But the moment has been prepared for." - retirement lessons from the Doctor
Just because they are non-critical, doesn't mean they are not risky!
Just because they are non-critical, doesn't mean they are not risky!
How will YOU avoid these AI-related cognitive biases?
Categories
Agile,
Artificial Intelligence,
Career Development,
Change Management,
Communications Management,
Decision Making,
Governance,
Hiring,
Kanban,
Lessons Learned,
Personal Development,
PMO,
Portfolio Management,
Project Management,
Resource Management,
Risk Management,
Risk Management,
Schedule Management,
Scheduling,
Tools
Date
I've worked in the delivery space for thirty years.
Over that time, I've seen delivery approaches rise and fall and wars about ways of working rage on. Frameworks, tooling, nomenclature, roles and rituals have changed, but one thing hasn't. Most executives don't care how you deliver as long as business objectives are met. The question they want answered is not which framework to pick but rather what they need to do to get their business results.
Anything else is just mechanics.
I'm not suggesting that executives shouldn't want to know anything about how those results are produced. Such an "end justifies the means" mindset might encourage a command and control approach from delivery leaders. It is one thing to not know how your car engine works when you take it to a mechanic to be fixed but your car is not part of complex adaptive system the way your business processes and supporting applications are.
Leaders should understand why teams are organized in a certain way, how the members of those teams are feeling, how the decisions they make will affect business outcomes as well as the upstream and downstream implications of those decisions. They should know what technical debt is and how the decisions they make can affect that. They should also understand that they shouldn't create walls between delivery and operations.
They should understand if the delivery targets they've set or the constraints they are imposing on teams are realistic. They need to understand what could go wrong but also how they could prevent those risks from being realized. And they must know how they can best use their power and influence to get their projects to succeed.
But whether you use framework A or B, call a delivery role X or Y, or follow a P or Q life cycle is really not that important to them. If they've come up through the ranks from delivery positions they might have some nostalgic interest in this but beyond that it really doesn't matter to them.
So have your "my Kung Fu is better than your Kung Fu" arguments on social media platforms if that makes you happy. Just don't expect your executive team to pick a side or to cheer from the sidelines.
Posted on: September 12, 2021 07:00 AM |
Permalink
Comments (10)
Please login or join to subscribe to this item
Luis Branco
CEO| Business Insight, Consultores de Gestão, Ldª
Carcavelos, Lisboa, Portugal
Dear Kiron
Very interesting theme that brought to our reflection and debate
Thanks for sharing and your opinions.
We agree that what matters, from the perspective of executives, is what they need to do to achieve their business results.
I think the shape is also important :-)
George Freeman
Thought Leader | Author | Architect|
Florida, United States
Hi Kiron,
I agree that most executives have an “I don’t care” attitude towards delivery approaches when one asks them for their thoughts on the subject. However, in my experience, that’s predicated on them knowing that ample “accountability structures” have been put in place from governance, financial and functional perspectives.
At the same time, if there have been financial overruns and objective failures on projects, the delivery approach used or portrayed to the executive will be under their scrutiny, regardless of whether or not the method used bore any responsibility for the failure.
I’ve seen executives “ban projects from formally using a given approach” simply for the correlative association they have made to the delivery method. However, in my opinion, the given delivery approach is not the issue, but the fact that the necessary accountability structures needed for that organization “to feel comfortable” were not accommodated.
George
Hi Kiron, very apt, resonates with everyone.
Thanks Luis!
Thanks George - definitely would agree with you. It is almost never the people but most often the system (including the governance structures and performance measures) which are the cause of most delivery issues.
Kiron, it's hard to fathom that most project executives do not care how the project is delivered. You have outlined many of the significant reasons why they should care in your statement.
Michael, they should care about the important aspects of delivery which they can influence but so much of the rhetoric I witness daily online relates to tactics which are of no importance to them.
George Freeman
Thought Leader | Author | Architect|
Florida, United States
Michael,
Nomenclature and context might be in play here, as “Project Executives” (for the larger part) do care, as their scope of concern either directly or indirectly includes the delivery approach.
However, executives in the business domain (e.g., an executive business owner, C-Suite executive, etc.) often fit into what Kiron described, depending on the size of the enterprise.
Thanks for sharing and your opinions
This is so true. Thanks for posting this article.
Thanks Abdelfattah and Maria!
Kiron
Please Login/Register to leave a comment.
|
"A nod's as good as a wink to a blind bat"
- Eric Idle, Monty Python's Flying Circus
|