Friday, November 18, 2011

Gladwell on intuition

“A tremendous amount of expertise lies in the unconscious mind ….. Anyone juggling many different variables, dealing with incredibly new and complex issues, … has to, at some point, rely on this body of submerged knowledge to make sense of their tasks”

Malcolm Gladwell

Wednesday, November 16, 2011

Complexity

Some problems are so complex that you have to be highly intelligent and well informed just to be undecided about them
Laurence J. Peter


I'll think I'll just let this one stand, but if you want to read more, browse through this explanation of the "wicked problem".


Monday, November 14, 2011

Option management

I often hesitate to import risk management ideas from the financial sector into the project management domain--afterall, the risk management results in the financial sector have not been swell of late, and projects are not casino's--but the idea of "options" does port well to projects.

And an option is:
An option is a "right" that you buy for a small fee; then, you have the option to exercise your right at a later time. You can buy the right to buy a security at a specific price not later than a specific date, or you can buy the right to sell a security at a specific time at a specific price.

If you don't exercise the right you paid for, you lose the money you paid for the option. Obviously, you would only exercise your option if the transaction is profitable for you.

Option risk management features:
There are a couple of interesting features embedded in the option transaction that are attractive from a risk management perspective:
  • Time displacement (the distance between present and future) is usually a risk nemesis, but in options, time is on your side.  Lemons become lemonade, as it where.  In order for an option to become profitable, some time must pass during which the security changes value, hopefully in your favor. (Most securities trading works this way)
  • Downside risk is protected.  The most you can lose (if you act rationally) is your fee for the right to the option, thus protecting you from the actual loss of the value of the security
  • Upside opportunity is amplified. Options leverage the value of the fee you paid.  For your small fee, you may be able to participate in a very large gain, which on a percentage basis, is far greater than just trading the security.
Options in projects (and portfolios)
Let's say you anticipate a make/buy juncture in the project 2-4 months out (we never use single point estimates here at Musings).  Two chains of project activities radiate from this decision event: one chain supports a 'buy' decision (essentially, outsource to a supplier) and one chain supports a 'make' decision (do all the work in-house). 

An option scenario is that you do something now to protect your right to go either way at the decision event.  You make a small investment now in order that 'no options are off the table'.

Done right, you make a friend of time: time can be used to set up the conditions for a decision that might not otherwise be available.  By protecting both eventualities, you protect agains the downside of poor alternative, or an alternative foregone because of no preparation.  And, of course, your small investment may be highly leveraged: a great outcome made more likely by a small fee for preparation.

Investment possibilities
So, what are some things you might do? A few prototypes to test your in house capability; some training of staff in skills that might be needed; some due-diligence and benchmarking on the supply chain; and some research into the various vehicles for outsourcing, like incentive contracts, etc.

If you are portfolio manager, then options in the form of independent R&D (IR&D, or IRaD) is a good way to invest a small amount now in order to have project options in the future. And, of course, investing in your customer (things you know your customer wants to do is perhaps the best use of internal investment)

Oh, and how big is "small" in the investment we are talking about?  No right answer of course, but a few percent of the value of the opportunity you are protecting is not a bad figure.

To learn more
If you want to see some numerical examples worked through, go to the Khan Academy and search for the short videos on options.



Are you on LinkedIn?    Share this article with your network by clicking on the link.

Saturday, November 12, 2011

Hold a meeting

How many "how to hold a meeting" guides are there? More than enough!

So it caught my eye that no less an eminence than Donald Rumsfeld is giving his ideas on how to hold a meeting. He's on slide 8 of Bloomberg Businessweek's How To issue for September 2011.

He has four points, and three of the four are mundane: start on time/end on time, speak without jargon, and be inclusive (more on this later).

But he has one point that seems less obvious: no matter the subject, start with assumptions.

Why? Well, according to Don (can I address him as Don?) assumptions let's everyone know if they are likely to be in agreement with the topic. If so, it shortcuts the discussion of the unncessary so that the presenter can move directly to the punch line. Perhaps so. I'll be giving it a try.

On the other thing, being inclusive: not in Rumsfeld's written missive, but attributed to him by those in the know (as heard on "Morning Joe" on MSNBC), Rumy would often 'dis-invite' those that he knew did not speak up, did not offer critical thinking, and thus were unlikely to add value. So, inclusive yes; but only if likely to add something to the discussion. At the risk of group-think, which is not necessarily implied, I like this one also.

So, two good points!

Photo


Are you on LinkedIn?    Share this article with your network by clicking on the link.

Thursday, November 10, 2011

Project balance sheet

If you follow this blog you've read several references to the project balance sheet. So, is this about accounting? Yes, and no: Yes, it's about a double entry tool to keep track of "mine" and "yours", but no, it's not the accountant's tool used in your father's accounting office.

Take a look at this figure:


What have we got here?

First, 'mine' and 'yours'.

On the left side of the balance sheet is the sponsor's investment in the project. Investment need not be all monetized. It's the 'your's side of the balance sheet, somewhat akin to the right side of the financial balance sheet (money owed to creditors and money invested by owners). 'Yours' simply means it's resources owned by others and provided to the project.

On the right side is the 'mine' side of the project balance sheet, akin to the left side of the financial accounting sheet (assets owned by the business). The right side is the project side, and the right side shows the estimates and evaluations of the project manager.

And, take note: the left side, the sponsor's side, is the fact-free zone: it's a top down allocation of resources to the vision. It is the ultimate utility expression of the sponsors: what's valuable, and how valuable, even if not entirely objective. And on the right side, it's all about facts (benchmarks) and estimates (benchmarks applied to project circumstances). It's bottom up.

Of course, there's the inevitable gap where utility collides with facts and fact-based estimates. The gap is the risk between expectations and capacity-capability. And how large is the gap (risk): only as large as needed to create a balance--that is, a deal with the devil--so that the project can go forward.

 In other words, the gap (risk), shown on the project side, is only as large as it needs to be to close the gap. Usually, it's a matter of negotiation, but once the PMB is set, the risk is the PM's responsibility to manage.

In other words, the PM is the ultimate risk manager.

In a real world example, I had this situation:
  • We bid a job competitively in a firm fixed price environment. 
  • We offered a price that was equal to our cost; in other words, no fee (profit).  We just wanted to keep the lights on and keep barriers to competition with our customer as high as possible. 
  • We won! 
  • And, in  the next moment, my general manager said: "Your bonus depends on making 4% net margin".  I had my gap!  (oh yes, I made the margin and the customer was satisfied)


Are you on LinkedIn?    Share this article with your network by clicking on the link.

Tuesday, November 8, 2011

The human element

The one element that can change every element is the human element
Dow Chemical tag line

People are our most valuable resource--correct?  Well, that's always the line, but is it the reality? Lest we all forget,  the 'facts' are that on the financial balance sheet, the one executives look at, people are a liability (accrued benefits and compensation), and on the expense statement, they are a cost. 

But, fortunately on the project balance sheet, they're assets.   Recall: the project balance sheet and the financial balance sheet are not the same animal.  The former is a view of the top down/bottom up balance in the project, and the latter is a view of the distribution of monetary ownership between the business and it's benefactors.

Bottom line: there's a natural tension between business and projects, and the human resource is a part of that tension.


 Bookmark this on Delicious  

Sunday, November 6, 2011

Risk waterfall, or not

Waterfall is a four letter word in the project management space.

Everyone will tell you they understand the hazards and seek a more effective paradigm. Actually, the synonym is sequential process (sounds better, and more sophisticated) and the better idea, practiced by most, is sequences with iteration and feedback.

Most understand the idea of feedback as a control device (for those that want to brush up, a good read is Donella Meadows' book "Thinking in Systems"). So, when you combine a control device with the opportunity to do over or correct, you've got a sequence under control, and a sequence that is responsive to outcome demand.

Nice.

Now, the agilists call an iterative sequence under control just common sense, or complex adaptive (perhaps so, in some cases) or emergent (closer to what actually happens). But, usually the discussion on this topic is all about the vision, the requirements backlog, and the intended product or process outcome. The risk register--indeed, the whole RM process--is often ignored, or just not in the discussion.

Where does the classic RM sequence fit in? Recall the sequence: set the context; identify risks; qualitatively and quantitatively assess the risks; plan responses; do, monitor, and control the response and its impact.

Now, how does the risk sequence fit into an agile emergent paradigm, or a iterative sequential baseline process?

I posit that the right strategy is to distribute the sequence: the first two steps, set the context and identify the risks, and be done as part of the project business case and the original envisioning.  The latter steps can be allocated to the execution teams.  As such, every time the backlog is reevaluated, so also is the risk register reevaluated (thus, iteration to the project charter) and the assessment, response planning, and monitor/control are incorporated into the team work of each time box or other scope segment.

So, in effect, the sequential process, with feedback, is made iterative by time box or scope segment as matter of methodology design and management policy.

Are you on LinkedIn?    Share this article with your network by clicking on the link.