Posts From February, 2020

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.

3 Tips to Tame Microsoft Project!

Make Project easy to learn and easy to use!

Putting the classic project management techniques to work is near impossible without a scheduling application. We all value ease of use with our tools, yet too often that comes at the price of functionality. At Versatile, we are happy to support Microsoft Project because of its powerful feature set. The good news is that most users can tame Project with a few simple tips.

“We Only Manage a Schedule – Not Costs!”

The majority of Project users want to build a schedule, not manage costs or resource level their team. These users should set their Default task type to Fixed Duration. That means they estimate duration for a task and can add as many resources as they want without changing the duration. This is a powerful way to simplify your use of Project. To set the Default Task Type, under the File tab, choose Options. The Options dialog box below shows where the Default task type is set. 

Link Your Schedule to a Project Start Date

Leverage Project’s scheduling engine by “linking” tasks, that is, creating finish-to-start relationships between tasks. Avoid entering Start Date or Finish Date for any task. Instead, use the Predecessor column to show which tasks must be done before others. This is actually pretty intuitive, and many users quickly figure this out. But when does the first task start? The one(s) without a predecessor? Set the Project Start date, and Project will schedule forward from there. On the Project tab, select Project Information. In the dialog, choose the Start date.

Measure Schedule Performance Against a Baseline

Build your schedule. Get your team, sponsor, and key stakeholders to agree. Then save the Baseline. Project tab, Set Baseline.

Switch your View from Gantt to Tracking Gantt.

Every day or week, as tasks are started and finished, enter the date in the Actual Start and Actual Finish columns for each task. The Tracking Gantt will generate a clear picture of the planned and actual schedule.

Nobody will say that Microsoft Project is the easiest tool to use, but it remains the most popular project scheduling application because it is powerful.

Use these simple tips to Tame Microsoft Project. Learn more about Microsoft Project at one of our classes. Bring them onsite and have your team learn together! Questions? Contact: