People, Planet, Profits & Projects

Project managers and aficionados of quality tools know the fishbone diagram.  They also may know it by other names; the Ishikawa diagram after Kaoru Ishikawa, and the Cause and Effect diagram after what it is meant to show, namely the cause(s) of some sort of ill effect.

We use this to help troubleshoot problems by placing the ill effect at the “head” of the fish, drawing a ‘backbone’ from that head, and using ‘ribs’ –representing potential types of causes that could yield the ill-effect.  Then we ‘animate the diagram by ‘asking why’ over and over again, thus building out the rib and eventually leading to a 'eureka moment' as we discover a possible cause.  My favorite example of this is illustrated below, and is timely in that we have just crowned our USA National Champion in college basketball – the University of North Carolina.

In this case, the ill-effect is the deadly ‘missed free throw”, something basketball coaches absolutely despise… a golden opportunity to score, wasted.  So, what contributes to this?

http://www.medicine.wisc.edu/sites/default/files/domfiles/housestaff/Fishbone%20Diagram.pdf

Amongst the fishbone “ribs” in this example are (for example) the “Machine” (the hoop and backboard), the Shooter, and the Environment (the weather).

And that’s the segue to the topic that also looks for a cause-effect relationship that involves the weather; this time the sought after connection is that between extreme weather and climate change.

As you should know, weather and climate are very different.  We’ll let NASA tell you about this difference.

The difference between weather and climate is a measure of time. Weather is what conditions of the atmosphere are over a short period of time, and climate is how the atmosphere "behaves" over relatively long periods of time.

When we talk about climate change, we talk about changes in long-term averages of daily weather. Today, children always hear stories from their parents and grandparents about how snow was always piled up to their waists as they trudged off to school. Children today in most areas of the country haven't experienced those kinds of dreadful snow-packed winters, except for the Northeastern U.S. in January 2005. The change in recent winter snows indicate that the climate has changed since their parents were young.

Read more here: https://www.nasa.gov/mission_pages/noaa-n/climate/climate_weather.html

So they’re different.  But what we notice is the weather.  Is there any connection between weather, say, extreme weather (an ill-effect) and climate change?  Until now, there has been no definitive link.  But a recent article by respected climate scientist Michael Mann of Penn State University and several colleagues.  Their findings were published in Scientific Reports (reference below).

That finding, released just a few days ago, is best summed up by this article from Science Daily:

Unprecedented summer warmth and flooding, forest fires, drought and torrential rain -- extreme weather events are occurring more and more often, but now an international team of climate scientists has found a connection between many extreme weather events and the impact climate change is having on the jet stream.

"We came as close as one can to demonstrating a direct link between climate change and a large family of extreme recent weather events," said Michael Mann, distinguished professor of atmospheric science and director, Earth System Science Center, Penn State. "

"We are now able to connect the dots when it comes to human-caused global warming and an array of extreme recent weather events," said Mann.

While the models do not reliably track individual extreme weather events, they do reproduce the jet stream patterns and temperature scenarios that in the real world lead to torrential rain for days, weeks of broiling sun and absence of precipitation.

"Currently we have only looked at historical simulations," said Mann. "What's up next is to examine the model projections of the future and see what they imply about what might be in store as far as further increases in extreme weather are concerned."

We realize that as project managers we don’t often have to make these ‘huge’ connections as did the team under Michael Mann.  We do need to be good ‘troubleshooters’, and the Fishbone Diagram is an excellent thinking tool for us and our project teams.  And even though the connection of effect to cause related to extreme weather and climate change is not directly applicable to PMs, I do assert that this helps reiterate the value of the Fishbone diagram, and, it can’t hurt to learn the science of climate and weather, either.  After all, extreme weather is definitely an ill-effect that can threaten your project objectives – and maybe much more.

Reference to original article:

Michael E. Mann, Stefan Rahmstorf, Kai Kornhuber, Byron A. Steinman, Sonya K. Miller, Dim Coumou. Influence of Anthropogenic Climate Change on Planetary Wave Resonance and Extreme Weather Events. Scientific Reports, 2017; 7: 45242 DOI: 10.1038/srep45242

The reference?  An old song by REM (with the help of Kate Pierson of the B-52s).  I may even provide the official music video below.  If you're good, that is.  If you read the post, it will appear.

I just finished reading two engaging books by Mihaly Csikszentmihalyi, “Flow”, and “Good Business”.  Both books talk to the definition of – and importance of – happiness.  I’m going to focus on Good Business in this post, since it sits (I believe) squarely on the intersection of project management and sustainability.

Csikszentmihalyi starts this book by making the case that the torch of leadership - those responsible for societal development - has, in effect, been passed the centuries from ‘nobility’ to ‘clergy’ to ‘business’. 

The author discusses “how leaders who have impressed their peers with their business success and their commitment to broader social goals go about their jobs … what ambitions motivate them, and what kind of organizations they try to develop in pursuit of those ideals.”

If you agree with me that project managers are executers of business ideas (profit or non-profit), if you believe that project managers are those who make things happen, the ones who turn dreams into reality, read on.  If not, go back to your humdrum job.

The book is summarized well at this site: https://thekeypoint.org/2014/05/28/good-business/

Here is a summary of what brings happiness at work.  I would extrapolate this to mean happiness in projects.

1. Clear Goals – “True enjoyment comes from the steps one takes toward attaining a goal, not from actually reaching it.”
2. Immediate Feedback – “The sense of total involvement of the flow experience derives in large part from knowing that what one does matters, that it has consequences.”
3. Balance Between Opportunity and Capacity – “If it appears to be beyond our capacity we tend to respond to it by feeling anxious; if the task is too easy we get bored.”
4. Deep Concentration – Flow happens when “the distinction between self and activity disappears… a pleasant feeling of total involvement.”
5. Present Moment – “Because in flow the task at hand demands complete attention, the worries and problems that are so nagging in everyday life have no chance to register in the mind.”
6. Control – “A worker who feels micromanaged soon loses interest in her job.”
7. Sense of Altered Time – “Quite often, this means that time is perceived as flying by.”
8. Loss of Ego – “While one forgets the self during the flow experience, after the event a person’s self-esteem reappears in a stronger form than it had been before… Similarly, people who have more flow experiences also have higher self-esteem overall.”

From a project manager’s viewpoint, moving further up and to the right on this chart is a good thing, since in a project, team members who are happy “are more productive, have a higher morale, and have a lower turnover… An ideal organization is one in which each worker’s potentialities find room for expression.”

Some of the messages will be clear and present in terms of general best PM practice:

“To summarize briefly the essential conditions for flow to occur, they are: clear goals that can be adapted to meet changing conditions; immediate feedback to one’s actions; and a matching of the challenges of the job with the worker’s skills.”

Much of this you may recognize from Herzberg’s Hygiene Theory of Motivation.  However there is a connection to sustainability here as well – and this is exemplified in the book by the examples the author uses from (for instance) Patagonia.  He quotes Yvon Chouinard,

“We are not in the business to make a profit.  We are not in the business to make a product.  We are in the business to really change the way other companies operate”.  Extracted today from Patagonia’s web page, their mission statement is:

Build the best product, cause no unnecessary harm, use business to inspire and implement solutions to the environmental crisis.

Part of this, of course is due to Patagonia’s long-term view.  “We really do try to act like this company is going to be here a hundred years from now”.  That changes the way people behave, and I would argue, it significantly changes the way projects are chartered – and how their success is measured.

This is something that really could motivate workers, and project team members.

The author continues, “today, business leaders cannot begin to foster a climate of positive order if their sole concern is making a profit.  They must also have a vision that gives life meaning, that offers people hope for their own future and those of their children.  We have learned how to develop five-minute and even one-minute managers.  But we would do better to ask ourselves what it takes to be an executive who helps build a better future.  More than anything else, we need hundred—year managers at the helm of corporations."

I know – this is talking about people at the helm of organizations and we are “only” project managers.  But what is a project manager if not the “CEO” of a temporary organization, accomplishing specific objectives tied to the organization’s strategic goals?  So we should be paying attention to books like this because we are at the helm, and perhaps just as leaders need to be hundred-year-managers, as the 'executors' of business ideas, we need to be hundred-year project managers.

It will make you and your team happier!  And who doesn’t want that?

Oh wait. You wanted to see that video?  Here it is:

In a prior post, I promised to provide more detail and some examples from the outstanding book by Kris Kohl, "Becoming a Sustainable Organization".

In this post I would like to start at the beginning - with the Project Charter.  Kris has done what I have proposed to PMI in 18 proposed changes to the PMBOK® Guide, 6th Edition.  I'm not sure how many (if any) made it into that new edition, expected in the third quarter of this year, but whether or not they did, they share the exact same "DNA" as Kris' template for a "Sustainability Project Charter", or as I would like to call it, "The Project Charter".  So that's one of my points - there is no need to have a 'special-interest' charter.  All project charters should have this long-term consideration built in.

Yes, sustainability, like quality, should be 'built in', not 'bolted on'.  The documents and methods we use to manage projects should, in and of themselves, contain the long-term thinking, the focus on benefits realization, the considerations of the triple bottom line.

In her Table 5-1, Kris, for example, adds to the section on "Project Goals and Desired Outcome":

Consider:

• Long-term impacts
• Internal  & external impacts
• Environmental & social impacts
• Behavior change
• Policy & process change

Under "Benefits",

• Outline the goals of the project and alignment with business & sustainable strategy.

These very simple changes appear minor, but they enable a sea-change in mindset.   Later in this same section about the project charter, Kohl says:

Following are some questions to consider when integrating sustainability into projects:

1. How are sustainability issues integrated into strategic planning?
2. What areas of sustainability are being addressed through project selection
3. How can sustainability be incorporated into project concept formulation?

Now, because this part of the book is about launching a 'sustainability project', what could get lost in context is the fact that a so-called Sustainability Project Charter can and should apply to all projects.

Let's take an example.  Let's say you are the PM for a project to build a new, fairly long stretch of interstate highway.  That project can, and should, consider not only the objective of building the highway but also the objective of improving the safety and fuel efficiency of vehicles driving on that highway.  The drivers on the highway are clearly key stakeholders.  So, if for example, a choice must be made between two materials to use for paving the highway, one of which is more costly - for argument's sake, 40% more expensive - but provides better grip for tires, and improved mileage, the decision to select the pricier material becomes (correctly) the better choice - for the very reason that the charter (the guiding document) advises the project team to consider long-term impacts.

I know if I was a taxpayer/driver stakeholder in a project like this, I would want the highway project to serve me in the long-term by keeping me alive (through the better-gripping surface) and providing me with lasting savings (through greater fuel efficiency) as well as lowering the ecological impact, even if the 40% higher price for paving drives the project cost to be 10% higher. 

Again: it's about long-term thinking...  and benefits realization.  And it starts with the project charter building in sustainability, not trying to bolt it on later as an afterthought.

“Owl Aboard”– Part 2 of 2

As I said in Part 1, Project Managers need to be wise, and that it’s true for decision making, including those very large decisions, in which we (for example) are choosing which Corporate Social Responsibility goals link up to our project objectives.  Those decisions must be good quality decisions, which means that they should be wise.  And in the first post we brought you the DIKW model which considers that data (miscellaneous tidbits of info) can be advanced into Information (connected data) and then into Knowledge (applied info) and finally into Wisdom (understanding). 

In case you missed it, please go back to Part 1 to learn how we as project managers are in the business of advancing data into wisdom.  One of the most important areas in which we do this is in our assessment of stakeholders.  Stakeholders – anyone who cares about the project while it is underway, or after it is implemented – bring both threat and opportunity to the table.  Attributes of power, interest, and attitude (support or opposition to your project or its objectives) will modulate your decision making and your dealings with each of your stakeholders, be they individuals or organizations.

One set of stakeholders that project managers cannot ignore is the public.  As users, consumers, voters, laborers, legislators, team members, even colleague project managers, the population at large is a stakeholder in your project, especially if you think of your project as we coach you to: with the long-term in mind and thus with the project’s outcome and use in mind.  To that end, it make sense for us to be wise about the public as a stakeholder, which means understanding the data, information, and knowledge that we have about their perceptions of important issues.

One such important issue is climate change.  And it turns out, there is a great source of data, information, and knowledge about the public (at least the USA’s public) opinion on this subject.

For example, one of the questions on the issue of climate change is “do humans have a role”?  Well, here’s an example of data: the national average of US adults who think global warming is mostly caused by human activities is 53%, according to Yale University.  But that’s data.  Remember: we’re owls.  We’re not satisfied with data.  We want context, trends, surrounding information and knowledge to propel that data into wisdom.  So rather than that single data point, how about if we were able to understand our stakeholder by posing all sorts of questions about their beliefs surrounding climate change by using some simple drop-down menus and letting the data paint maps of the US in various colors right before our eyes?

It’s possible, thanks to the Yale Program on Climate Change Communication.

For example, that 53% is a rather ‘grey’ statistic.  It just tells us that about half the country thinks that humans ‘mostly’ cause climate change.  It doesn’t tell us about striking differences between, for example, about Rich County, UT, where the number is 39%, or Almeida County, CA, where the number is 68%.  Or, quite interestingly, two neighboring Texas counties where there is a 21% swing, with McMullen County being 11% more cynical about human-caused climate change than the national average, and Duval County which is 10% more convinced that climate change is mostly caused by humans.  See?  We’ve become owls, simply by looking at context and gaining an understanding and awareness. 

Below is an example of one of the maps I generated to provide the stakeholder analysis above.

There are other questions answered on this site, for example, trust in scientists about their information on global warming.  Moving to the State level from the County level gives us the interesting finding that, for example, neighboring states Maryland and West Virginia have a 12% swing, with Maryland trusting scientists 5% more than the national average (of 71%) and West Virginia trusting scientists 7% less than the national average.

My plea to project managers is not about this climate change data alone.  It’s a great example to use, and I of course encourage project managers to be longer-term thinkers and to consider the facts when it comes to ecological sustainability and issues related to helping to preserve the environment.  But the coaching here is to – in general – better understand your stakeholders and to always seek to advance data into information into knowledge and finally into wisdom.  Get your owl on. 

Get your owl … aboard.

Yep.  An owl.  The symbol of wisdom.

Project managers need to be wise.  Why?  When you get out your magnifying glass and look at what projects are all about, what do you see?  Look closer.  No, even closer.  What’s coming into focus? Decisions. Daunting decisions.  A cacophony of choices.  A plethora of preferences. Some are small (what color should this user entry screen feature?) and some are very large (to which Corporate Social Responsibility goals does our project link?).  Those decisions must be good quality decisions, which means that they should be wise.

What does that mean?  And...what is a wise decision, anyway?

There’s a system called the DIKW model which considers that Data (miscellaneous tidbits of info) can be advanced into Information (connected data) and then into Knowledge (applied info) and finally into Wisdom (understanding).  Below are my own short definitions and illustrations of these terms (although there is quite a bit of debate about these definitions).

• Data: raw observations and measurements
  • Answers to ‘smaller’ questions, like “how many Oscar nominations did Moonlight receive?”
• Information: data enhanced with appropriate connections and relationships
  • Answers contextual questions, like “how did Moonlight rank compared to other films in terms of Oscar nominations?”
• Knowledge: applying the information for action, for establishing a practice, a method, a trend
  • Answers ‘larger’ questions, like “is there a movement to recognize more diverse-themed films by the Motion Picture Academy”?
• Wisdom: the application of knowledge, understanding why the practice or method is right
  • Answers ‘reasoning’ and ‘ethics’ questions, like ‘why is this trend taking place now, and do we think it will continue? Is it the right thing to do?’

The PMBOK® Guide, although it does not mention the DIKW model by name, does implement the idea quite formally.  You’ll notice a theme in the PMBOK® Guide.  Below are the three terms PMI uses and their glossary definitions: 

• Work Performance Data
  • Raw observations and measurements identified during activities being performed to carry out the project work
• Work Performance Information
  • The performance data collected from various controlling processes, analyzed in context and integrated based on relationships across areas
• Work Performance Reports
  • The physical or electronic representation of work performance information compiled in project documents, intended to generate decision, actions, or awareness

The key word here is understanding, or perhaps as PMI puts it, awareness.  As project managers, we can be very tempted to process data and let our projects go on “autopilot”.  This can actually work well for a number of project attributes and to help manage day-to-day ‘smaller’ scope, cost, time, quality, risk, and other decisions.

However, when it comes to the ‘larger’ questions – the ones that will truly determine whether your project is a success., as measured by benefits realization – we need to be wise guys.  We need that extended sense of understanding and awareness that is wisdom - that owl-like comprehension of all around us. That is, we need to climb up that DIKW pyramid - and stay there.

Reference and credit for this image: https://www.climate-eval.org/blog/answer-42-data-information-and-knowledge

In Part 2 of Owl Aboard, I will apply this important project management concept to how we as PMs can better understand our relationship to the effects of climate change – not on the planet, but on our stakeholders.  If you want to do a little pre-reading on that subject, have a look at this article and its associate maps of the USA.

http://www.cnn.com/2017/02/28/us/sutter-climate-opinion-maps/