Sunday, 04 March 2012 00:00

Technologists Are Never the Problem

Rate this item
(0 votes)

I sent a note to professional organization's program director the other day asking if their group would be interested in hearing about methods to increase project success. The organization was for a technical group that worked with data transformation—a skill set used in every IT project I have ever been on. The reply came in a prompt, succinct, and sarcastic reply:

"We [sic] you please tell me just how this would ever relate to the members of our group. You obviously do not understand that we are not responsible for running the project."

I was taken aback. He failed to even proof his note properly. I was about to delete the email and move on when I decided that I should explore this a little further. I crafted the reply:

"Projects fail for a variety of reasons. Customer requirements, management support, too many defects, scope creep, etc. The technical team certainly has their part in that. Don't you think your members would want to know how to minimize their contribution. It would increase their longevity at their employers."

He never replied.

Inculpability's Safe Harbor

Therein lies the problem—if someone else is more culpable than him, it is not his problem. He is probably the same guy who, a few months later, will pout as his project is canceled, maligning management for doing a poor job of controlling the project (i.e., him) and now his vision has vaporized. This selfish, myopic view of responsibility kills hundreds of projects every month. It is never "my" responsibility. Programmers can add dozens of neat little features, architects can design bleeding-edge systems, customers can refuse to compromise, and quality analysts can test for every imaginable and remote situation, all remaining devoid of guilt, since the project's collapse was someone else's responsibility. Management tolerates, while leaders revile, this attitude.

Doing The Right Thing

Albeit, leadership should come from the top, in reality, anyone can step up to that position. They simply need to develop a few guiding principles for how they work with others. Thousands, if not millions, of these lists have been generated and I have seen only a few that I have disliked. I have found, though, that instilling the following principles in my teams are the most helpful.

    • The project's goal is value. Above everything else on the project, everyone must focus on the project's value. The value does not come from a great project plan, state-of-the-art technology, a bug free product, or delivering the project within scope, schedule, and budget. It comes from delivering a product that meets the customer's needs.
    • Understand how jobs interrelate. The project is not about you, it is about a product that a team is creating. Any member of that team can make or break a project. Adding the simplest of features, such as a print function (see the earlier Case Study in Will We Ever Learn? Lessons from The Mythical Man-Month), can drastically increase scope for the entire project and detract from the customer's value. Any change, addition or deletion, affects everyone associated with the project. What may seem like a simple addition for one group of the customers may be a bane for another.
    • Communicate With Teammates. No one can understand the complexity and conflicts of the desires, wants, and needs of a customer. It requires relentless communication with all the stakeholders. It is incumbent on every team member to assiduously communicate and question his or her assignments and activities. Success is a world devoid of dictatorial management and hierarchical communication. It requires leadership that trusts and allows people and teams to master their duties and work autonomously. This requires teams composed of the right individuals—people that comprehend the greater good and derive motivation from excellence—not perfection.
    • Do The Right Thing. Back in the days of old, I worked with the Digital Equipment Corporation where a stated value, looming larger than life, was "Do the right thing." This was at the core of their innovative spirit. The project team is morally bound to translate what the customer wants to what they need. This lies on the project team, since they are intimate with the details of building the project's product. They are the ones that can foresee the impact of a decision. This cannot, however, be performed in the project team's vacuum. There are conflicts between the wants and the needs and the customer must be part of every decision. This requires fluid and frequent interaction between the customer and the team. They must look at all the requested features and derive innovative and cost effective solutions for delivery. Although sounding like an Agile tenet, it is not exclusive to that methodology. It is at the foundation of any successful project.

The Right Answer

The subject of my opening example may be quite capable of working in the environment described above. Given a change in venue and allowing time for de-programming the accusative and blame-oriented style of management philosophies that he probably works in today, I will wager his work ethics would morph and he would be a valuable team member concerned and contributing to the success of the project. He simply needs the right leader. That leader could be you. It does not need to be your boss.

What Are Your Thoughts?

Please, share how you lead from within and what makes your projects excel.

Read 8302 times

Related items

  • People vs Process Track Session/Keynote Example

    If you want educational keynote many of our presentations can be keynotes or track sessions. In the example below, the presentation People or Process: Which Impacts Project Success More? is given as a track session.  

    Example People vs Process keynote as a track session

    This session was given at the PMI Sioux Empire Professions Development Day help in Sioux Falls SD on September 9, 2014.

  • Transform Your Project Leadership: For Professionals Leading Projects or Company Initiatives

    Todd Williams contributed Chapter 7, "Leaders Listen." You can buy it on Amazon.

    More coming soon!

  • Filling Execution Gaps: How Executives and Project Managers Turn Corporate Strategy into Successful Projects
    What Filling Execution Gaps Covers

    Filling Execution Gaps

    by Todd C. Williams
    ISBN: 978-1-5015-0640-6
    De G Press (DeGruyter), September 2017

    Project alignment, executive sponsorship, change management, governance, leadership, and common understanding. These six business issues are topics of daily discussions between executives, middle management, and project managers; they are the pivotal problems plaguing transformational leadership. Any one of these six, when improperly addressed, will hex a project's chances for success. And, they do—daily—destroying the ability companies to turn vision into value.

    Check it out on Amazon or the Filling Execution Gaps website

    Without the foundation of a common understanding of goals and core concepts, such as value being critical to success, communication stops and projects fail.

    Without change management, users fail to adopt project deliverables, value is lost, and projects fail.

    Without maintaining alignment between corporate goals and projects, projects miss their value targets and projects fail.

    Without an engaged executive sponsor, scope increases, goals drift, chaos reigns, value is lost, and projects fail.

    Without enough governance, critical connections are not made, steps are ignored, value is overlooked, and projects fail.

    Too much governance slows progress, companies cannot respond to business pressures, value drowns in bureaucracy, and projects fail.

    Without strong leadership defining the vision and value, goals are not set, essential relationships do not form, teams do not develop, essential decisions are not made, and projects fail.

  • Filling Execution Gaps: Building Success-Focused Organizations

    Executives define vision, strategy, and goals to advance the business. Projects enable companies to meet those goals. Between strategy and projects, there is a lot of work to be done—work that lays the foundation for project and operational success. Through experience and research, six common gaps exist in organizations that inhibit project success—an absence of common understanding, disengaged executive sponsors, misalignment with goals, poor change management, ineffective governance, and lackluster leadership.

  • Get Recognized as a Leader: Four Core Leadership Actions

    Leaders make decisions. This requires a core set of actions to gather the best information, hear out the concerns of others, and making a decision that everyone will follow—even if there is not unanimous agreement with the decision. Although there are hundreds of actions leaders must take, there are four core actions that all great leaders do—listening, dialog and discussion, selling a vision, and eliminating blame. This session will discuss those actions in a roundtable format that we call a "What Would You Do?" session. In these sessions, the presenter acts as a moderator spending 10 to 15 minutes per topic working with the audience talking about what the action is, how to best do it, and hearing from the group on how they have carried out the action. This brings significant audience interaction, involvement, and broader education. 

Leave a comment

Filling Execution Gaps

Available Worldwide

Filling Exectution Gaps cover

Filling Execution Gaps is available worldwide. Below are some options.

 

PG DirectLogo
Limited Time Price $20.99
Amazon logo
Book or Kindle
Flag of the United States Canadian Flag Flag of the United Kingdom Irish Flag Deutsche Flagge
Drapeau Français Bandiera Italiana PRC flag
Japanese flag
Bandera de España
Flag of India
Bandera de México
Bandeira do Brasil
Flag of Australia
Vlag van Nederland
DeG Press Logo
Barnes and Noble Logo
Books a Million Logo
Booktopia Logo
Worldwide: Many other
book sellers worldwide.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Sitemap