analytics

It’s every portfolio manager’s nightmare.

The annual portfolio review is about to kick off. Hundreds of hours of preparation have gone into the main presentation’s PowerPoint deck, and hundreds more into each of the backup decks, readied in case management asks about the details of any of the projects under discussion. Information encompassing over a hundred different initiatives has been painstakingly compiled and distilled into slide after slide.
The portfolio team is ready to review the current budget and the changes in the portfolio since the last review, and to make recommendations for adjustments to keep R&D activities aligned with strategic goals. Everything is in place. Or so the manager thinks.

Then, the first slide goes up on the wall, summarizing spending since the last review meeting and listing the estimated total value of each division’s initiatives. The manager highlights key milestones each division has met, and heads all around the room nod.

Except one.
 The leader of one products division is clearly not happy. His expression sours as he looks at the slide. “You’ve understated the value of our projects by at least $400 million,” he complains.

“But we took these figures directly from your product team summary spreadsheet,” says the portfolio manager.

“Which one?” the exec demands. “We updated that spreadsheet last week based on the market research report from last quarter.”

“Oh that explains it,” the manager says, relieved. “We began building this deck four weeks ago, and we took the latest spreadsheet available at that point.”

The exec is not mollified. “I don’t think this meeting is an effective use of my time, or anyone else’s for that matter, if we don’t have current information.” He begins gathering up his things. “Let’s postpone until you can get all your ducks in a row.” The meeting is over before it has begun.
(more…)