Go with your gut — cautiously

On the popular TV show NCIS, the team leader (Mark Harmon) is frequently heard exhorting his staff to “go with your gut” (for the women readers I guess you call this female intuition!). The lesson he is sharing with the team is that your intuition, as opposed to decisions based solely on analytics, may give you the best answer when you need to make a decision quickly.

Experts in neuroscience talk about intuition as a type of pattern matching. A new situation reminds you of a previous situation and its outcome. For example, given enough experience in selecting subcontractors, hiring coders, picking a winning stock or getting burned in a relationship, you develop a sense of when to move forward and when to walk away. Learning to listen to your instincts can save you time and trouble. Have you had the experience of meeting someone and knowing in the first few minutes that they were an expert in their field—or that they were “trouble”?

Let me call your attention to a recent Harvard Business Review Blog titled, “Learn to Trust Your Gut”. This is a well-written, if somewhat simplistic, view of listening to your inner voice when you believe a poor or even dangerous course of action is proposed.  When your inner voice speaks, the author suggests that, “If you think that doing things another way would make a material difference, talk to your boss (or customer or client). Why do we do it this way? Would you be open to different ways? What would be the payoff and the risk? Can we experiment with an alternative? Would it be worth doing some further analysis?” I agree this is an internal conversation worth having.

However …

Equally interesting to me in the blog post is comparing the author’s suggestions with comments from readers. Many commenters said — in different words and ways — “hogwash”. The gist of their negative reaction is that authority figures do not want to be questioned. They believe that following your gut, applying the principle that it is easier to get forgiveness than permission, or arguing for a different course of action than the one proposed by senior management is career limiting.  (If this is true, Steve Jobs should have not been very successful!)

So, why the disconnect?

I suggest that first you should ask yourself, “Whose decision is it?” As a project or team manager, if the final decision is yours, collect data and also tune in to your instinct. You will make a better decision when you take advantage of analytical and intuitive analysis.

In an alternate case, when your opinion is solicited before an action is taken by senior decision makers, I think you should give the questioner both facts and your intuitive assessment. For example, “I believe that XYZ Corporation brings useful skills and contacts to our proposal team. However, in conference with them, they only presented their approach and did not ask questions about our solution or the customer’s needs. I am concerned that they will have difficulty working in our cooperative environment.”

Finally, consider the situation, when as a project manager or team member you are told the decision and given your tasking. You “know” that the proposed activity is doomed to failure and you have an idea of a different, and more likely successful, way to achieve the stated goal. Here is where the situation becomes a bit sticky. What is the most effective way to share your insight and impact the action plan?

  • Before saying anything, reflect on your motives. Are you often the first person in any meeting who points out problems? Is your intuition telling you to avoid any change or only the proposed one? Are you reacting to the proposal or to the person making it?
  • Assuming, after your self-assessment, you conclude that your motives are pure and untainted by cognitive biases, then organize your thoughts and recommendations as talking points that demonstrate your appreciation of the decision maker’s priorities.
  • Unless asked directly for your opinion, it will be more effective to offer your comments and suggestions in a private face-to-face meeting than to confront the presenter publically.
  • If you are having difficulty putting words to your intuitive feelings, try talking it over with someone you trust and respect. Listen to their questions and feedback and allow it to help you organize your thoughts before talking with the decision maker.
  • Wait a day to let your cognitive analytical and intuitive thoughts coalesce before presenting your thoughts. Sleeping-on-it, like your grandmother said, helps. (Got a tough decision to make? Research suggests you’re best off just sleeping on it and Research: You make better decisions using intuition and Incubating Decisions).

If you have complementary or contradictory thoughts, please share.

Learning Scrum – Staying up with the latest project techniques

The more I work within the Scrum project framework, the more I appreciate its practical and simple concepts. I am also interested in the expertise required to be a Scrum master. Like any skill you seek to master, the path may be harder than you want and take longer than you want. I am convinced however that applying a Scrum framework during project execution saves time, more actively engages the development team and helps avoid the problems that come from inevitable requirements changes.  Many of you project managers have probably been exposed to or are working with agile methodologies in your organizations.  Some of you may be like myself and are seeking to become a scrum master.

Gaining skill at any task, whether making cheese, playing golf or using Scrum requires learning basic principles and developing judgment based on experience. In the olden days, people learned a profession through three levels of increasing competence — apprentice, journeyman and master. To be accepted as an apprentice, a person needed to demonstrate basic understanding and possess a willingness to work hard to improve their skills. Apprentices worked on many types of tasks and projects under the supervision of journeyman. Projects were managed by masters. The masters provided a vision of the final product, developed plans to achieve goals and offered mentoring and training to the team.

Becoming a Scrum master requires the same type of disciplined learning and practice. So, how can you learn Scrum? My advice is to first become familiar with Scrum principles. Scrum.org provides an excellent, short overview called, The Scrum Guide, to get you started.

The Scrum Guide introduces you to the three pillars of the Scrum framework — transparency, inspection and adaptation. You will also be introduced to the titles or roles of the Scrum team. For example, there is the product owner who managers the product backlog such as setting task priorities, the development team and the scrum master. The Scrum world operates within very short time frames — usually two weeks to no more than one month to complete tasks. These one month windows are called Sprints.

After scanning the Scrum Guide, I suggest reading about the experiences of Scrum practitioners. There are many good books and articles about the process, including “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle and “Agile Project Management with Scrum” by Ken Schwaber. The series of Agile/Scrum books by Mike Cohn has received favorable reviews.

After you have developed general familiarity with the Scrum terminology and philosophy, I recommend talking or listening to professionals with real world experience. A local professional organization or university may offer invited talks on Scrum. Alternatively, conferences often have workshops or presentations about Scrum. You can also use the social interaction during these professional meetings to talk with masters and project managers about their experiences.

The next thing you should do is to look for opportunities within your organization to become part of a Scrum team. After a couple projects, I think you will appreciate the flexibility and freedom of working within a Scrum framework.  Identify and work under a Scrum master. Use your training experience to ask questions about how and why.

As part of your apprenticeship, I suggest you take a class taught by a Scrum master and certified trainer— usually a two day class that focuses on fundamentals, theory and practical examples of applying Scrum across a variety of development endeavors.  I have just completed the Professional Scrum Master Training course myself which was led by an excellent coach/trainer, Don McGreal.

Continue to work on skills and practice techniques. Over time, I have found that experienced Scrum teams are some of the most productive professionals I have had the opportunity to work with.

If you have worked in a Scrum environment, sharing your experience and observations will help newbies become contributors more quickly.

The Lazy Project Manager's Blog

The Home of Productive Laziness Thoughts

ProjectManagement.com

Thoughts, experience, tips and tricks on issues affecting managers and project management

A Girl's Guide to Project Management

Project Management musings for one and all

LeadingAnswers: Leadership and Agile Project Management Blog

Thoughts, experience, tips and tricks on issues affecting managers and project management

Project Management Hut

Thoughts, experience, tips and tricks on issues affecting managers and project management

Herding Cats

Thoughts, experience, tips and tricks on issues affecting managers and project management

beyondcenter

Pushing the Edges Out ...

projectxpert

Just another WordPress.com site