Posts From July, 2012

I Love This Book! The Culture Code

Build Your Project Team Culture

The Culture Code Reveals the Power of Safety

“When we talk about courage, we think it’s going against an enemy with a machine gun. The real courage is seeing the truth and speaking the truth to each other.”
         –Dave Cooper, Retired, Commander Master Chief, SEAL Team Six (From The Culture Code, by Daniel Coyle)

Why is it so hard to see the truth and speak the truth to each other? Why does that demand courage? And, can any team reach their potential without this ability?

Safety: The Foundation of High Performance

Daniel Coyle, in his new book, The Culture Code, offers three necessary cultural elements of what he calls “highly successful groups.” These elements are safety, vulnerability, and purpose. After reading the first few chapters, I became convinced that safety should be the primary focus for every leader, especially project leaders

I’ve always thought of safety at the office and in my work group as physical safety. Coyle refocused my attention to that of emotional safety. Frankly, I am surprised I haven’t seen it before. I’ve been reading and writing about project team performance for about twenty years. I’ve always known that trust is crucial to creativity and innovation, but Coyle’s angle brought a fresh light on the foundational role of safety. His theme is that for teams to reach their potential, each member must feel safe enough emotionally to be vulnerable. Vulnerability is critical to giving and receiving authentic feedback, which is the only way a group will improve its performance. Feedback within the group is directed toward serving the purpose. Purpose becomes the North Star. That logic is tough to dispute.

Project teams are temporary, formed to accomplish something unique. These teams solve problems and make decisions every day. Versatile’s high-performance team checklist lists nine characteristics that enable a team to survive the “give and take” of creativity and problem solving while maintaining trust and keeping relationships intact. But I have to admit that emotional safety has always been assumed, rather than explicitly called out.

Coyle’s logic, that safety precedes trust and trust precedes authentic feedback and team learning, lays bare the importance of establishing emotional safety within our teams. The quote at the beginning of this article comes from a key story in the SEAL Team Commander’s evolution as a leader. In Cooper’s early career he advised a superior that a particular course of action was dangerous and should be avoided. That superior ignored his  advice and the result was exactly what Cooper had feared. Cooper took away from that experience a desire to be the kind of leader that invited opposing points of view and encouraged criticism from every member of his team.

The Primary Focus of Every Project Leader

Do you want your team to “see the truth and speak the truth to each other”? What could be more important? From creation of a business case and charter, through risk identification, scheduling, and daily problem-solving, your team is making decisions and working through conflicts.  Every day of every project is affected by team culture. Pick up Daniel Coyle’s Culture Code. He illustrates his theme with stories from a wide range of teams and follows up with specific actions for the reader. I predict his lessons will stick with you and reignite your focus on team culture.

Solving the Information Technology Project Puzzle

What is it about information technology projects?

Since Gartner highlighted project management as a critical success factor for information technology (IT) projects in ’95, we’ve seen a flood of training, methodology, and PMO initiatives that continue today.  Despite this massive investment in better project management, IT projects are a continued source of frustration for many organizations. 

It’s easy for a bystander to throw stones, so I’ll start by saying that things are a lot better in most IT organizations that they were in ’95. But it’s also undeniable that IT projects continue to have a rocky record. Like most puzzles, the better we understand the source of the problem, the closer we’ll be to solving it.

So let’s examine four dimensions of the IT project puzzle, which will lead us to some of the current best practices in IT project management.Information Technology Project Puzzle

1. IT Projects Change Business Processes.  Information technology projects support business goals and frequently change the way people within the organization work. So nearly every IT project includes an element of redefining what work is done, as well as the way it is done. Business process change adds an entire new category of risk.

2. There Is an Endless Demand for IT Projects. Few significant organizational changes are accomplished without an IT dimension. Continuously improving technology creates continuous opportunities for improving productivity and innovating products or services. That contributes to failure by overloading personnel and by taking on the wrong projects.

3. Technology Expertise Ages Quickly. As the capabilities of new technologies continue to grow, our expertise for implementing and supporting the technology must grow, too.  It makes sense that a risk factor for IT projects is that we find them difficult to estimate. How can we forecast the time and effort we’ll require when we are still learning the technology?

4. IT Projects Include Interfaces. As if applying new technology to newly invented business processes isn’t trouble enough, chances are pretty high that the project will include interfaces to one or more existing systems. Interfaces increase complexity and therefore scope. Scope for IT systems can also include hardware and operating systems – factors that may not be apparent during initial analysis.

Notice that addressing these challenges push us outside the boundaries of pure project management. They defy any ‘silver bullet’ methodology or software. Yet understanding these four challenges makes it easier to see the source of what have become proven best practices in IT organizations. Here are six practices you should be looking for in your IT organization.

1. Focus on Solving Business Problems, Not Deploying Technology.  This principle has been present since the first business system was deployed, and it is the drive behind the re-emergence of business analysts as key contributors on our team.

2. Disciplined Project Management, Particularly Risk Management. The good news is that many teams rigorously practice proven project management techniques. Given the risks associated with changing processes and new technology, risk management takes on a greater role.

3. Set Realistic Baselines Using Phased Estimates. Baselining a project too early is a guarantee the schedule and budget won’t be met. Phased estimating provides a realistic approach to balancing the need for cost and schedule targets with the reality of discovery that exists on many IT projects.

4. A Project Management Office Promotes the Discipline and Coordinates the Projects. Disciplined project management does not occur naturally. It is a conscious choice that requires commitment and encouragement. It is even more effective when the mechanics of project management are practiced consistently from one project to the next.  The PMO also keeps an eye on the coordination that needs to happen among projects.

5. Project Portfolio Management Maintains a Realistic and Strategically Aligned Workload. Project Portfolio Management is the process for engaging customers and the IT management team to prioritize projects and to draw the line on how many projects are too many.

6. Choose an Appropriate Development Approach. The rise of Agile software development techniques is a response to the element of discovery that exists in many IT projects.  Some projects will benefit from an Agile approach, others will benefit from a waterfall or other more traditional approach. Projects are not all the same. Understand the distinctions between these methods and choose the one that fits the project.

IT projects rarely have an auto-pilot switch. They take skill and attention to guide effectively. Recognizing the four challenges described here is the first step in solving the IT project puzzle.

*This post is an excerpt from Chapter 17 of The Fast Forward MBA in Project Management, 4th edition, 2012, by Eric Verzuh