How To Hold People Accountable for Portfolio Decision-making When Things are Uncertain?
Last updated: November 04, 2023 Read in fullscreen view
Recommended for you
- 01 Oct 2020
Fail fast, learn faster with Agile methodology 867 - 18 Oct 2020 How to use the "Knowns" and "Unknowns" technique to manage assumptions 814
- 14 Oct 2021 Advantages and Disadvantages of Time and Material Contract (T&M) 703
- 19 Oct 2021 Is gold plating good or bad in project management? 672
- 06 Mar 2021 4 things you need to do before getting an accurate quote for your software development 557
- 08 Oct 2022 KPI - The New Leadership 514
- 19 Apr 2021 7 Most Common Time-Wasters For Software Development 513
- 01 Sep 2022 Facts Chart: Why Do Software Projects Fail? 500
- 28 Dec 2021 8 types of pricing models in software development outsourcing 388
- 29 Nov 2021 Memorandum of Understanding (MOU) for Partnership Agreements 359
- 31 Oct 2021 Tips to Fail Fast With Outsourcing 359
- 11 Jan 2024 What are the Benefits and Limitations of Augmented Intelligence? 357
- 16 Apr 2021 Insightful Business Technology Consulting at TIGO 354
- 07 Jul 2021 The 5 Levels of IT Help Desk Support 342
- 23 Sep 2021 INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 338
- 10 Dec 2023 Pain points of User Acceptance Testing (UAT) 322
- 06 Feb 2021 Why fail fast and learn fast? 312
- 13 Dec 2020 Move fast, fail fast, fail-safe 280
- 01 May 2023 CTO Interview Questions 279
- 03 Nov 2022 Top questions and answers you must know before ask for software outsourcing 253
- 20 Dec 2021 What is Hybrid Mobile App Development? 247
- 17 Feb 2022 Prioritizing Software Requirements with Kano Analysis 244
- 18 Aug 2022 What are the consequences of poor requirements with software development projects? 227
- 07 Aug 2022 Things to Consider When Choosing a Technology Partner 226
- 10 Apr 2021 RFP vs POC: Why the proof of concept is replacing the request for proposal 225
- 20 Nov 2022 Software Requirements Are A Communication Problem 219
- 06 Nov 2019 How to Access Software Project Size? 215
- 10 Nov 2022 Poor Code Indicators and How to Improve Your Code? 200
- 08 Nov 2022 4 tips for meeting tough deadlines when outsourcing projects to software vendor 193
- 26 Dec 2023 Improving Meeting Effectiveness Through the Six Thinking Hats 181
- 09 Feb 2023 The Challenge of Fixed-Bid Software Projects 180
- 01 Mar 2023 Bug Prioritization - What are the 5 levels of priority? 171
- 09 Mar 2022 Consultant Implementation Pricing 168
- 07 Oct 2022 Digital Transformation: Become a Technology Powerhouse 164
- 09 Jan 2022 How to Bridge the Gap Between Business and IT? 150
- 16 Feb 2021 Choose Outsourcing for Your Non Disclosure Agreement (NDA) 143
- 01 Mar 2023 How do you deal with disputes and conflicts that may arise during a software consulting project? 137
- 05 Jan 2024 Easy ASANA tips & tricks for you and your team 132
- 07 Nov 2022 Why Design Thinking can save the outsourcing industry 128
- 12 Mar 2024 How do you create FOMO in software prospects? 98
- 06 Dec 2024 Steps For Integrating Sustainable Practices Into Business Operations 89
- 10 Jul 2025 Building AI-Driven Knowledge Graphs from Unstructured Data 89
- 14 Mar 2024 Why should you opt for software localization from a professional agency? 85
- 17 Mar 2025 IT Consultants in Digital Transformation 48
- 15 Aug 2025 Quantum Technology: Global Challenges and Opportunities for Innovators 33
In past ValuePoint articles, Don Creswell has discussed the “R&D Grid” which was introduced in detail in “The Smart Organization” book by David and Jim Matheson. The grid has been renamed the “innovation screen” in Portfolio Navigator® but the function remains the same: displaying projects within a portfolio based on risk vs. reward.
In this article, I will elaborate on the use of the innovation screen as experienced during my work with SmartOrg clients over the past decade, focusing on managerial accountability as part of the portfolio management process.
People working in New Product Development (NPD) or in Research and Development (R&D) have a management problem. How do you hold people accountable for results when there is an immense amount of uncertainty about whether the project (asset) will ever work and, even if it does work, will produce commercial results which, from this vantage point in time, are highly uncertain?
Accountability for managing these projects is certainly important – the near-term and long-term health of the company may well depend on them. However, accountability takes different forms, depending on the type of project.
Take the Innovation display, which divides New Product Development/R&D projects into four types: Bread and Butter, Oysters, Pearls, and White Elephants. Management accountability differs dramatically among these segments.
- Bread and Butter: These are projects which have a high probability of succeeding, but a relatively low value if successful – often product improvement or cost reduction type of applications. Essential to the near-term well-being of the company. Accountability for management of these projects can usually follow a common pattern: does the project come in on time, within budget, and meet its stated goals?
- Oysters: These are hard projects with a low probability of succeeding, but a high value if successful – often products or processes that will create new offerings to the company or revolutionize existing offerings. Essential to the long-term well-being of the company. Traditional accountability for the management of these projects would lead to a reduction in scope (value) of the project which would increase the probability that the project will come in on time, within budget, and meet its stated (reduced) goals, effectively becoming a Bread and Butter project. If this is not possible, managers will flee from this type of project. A more effective type of accountability would encourage the manager to:
- Find out as early and inexpensively as possible if the project is going to fail (“fail early if you are going to fail”).
- Choose among alternatives that increase/decrease the scope/value of the project and its probability of success.
- Steer the project to meet (or enhance) the long-term strategic goals of the company.
- Pearls: These are easy projects with large value – often Oysters that have come close to succeeding and may provide long-term benefits for the company. Bread and Butter type accountability works here, but care must be taken not to burden the project with unreasonable demands or expectations.
- White Elephants: These are projects that are unlikely to succeed, and would not be worth much if they do succeed; low-value expenditure of valuable resources, though sometimes mandated. Much like Oysters, accountability should emphasize “fail early if you are going to fail” and/or “try to improve the scope/value of the project”.
Given a good approach to accountability, the management of projects should become easier and a more attractive career option. However, people have to pay attention to the psychological effects of managing projects that fail. One employee of a major company comes to mind. Over a course of many years and many projects, he had never been on a project that succeeded! Rewarding and recognizing someone who has been on a project that fails may seem strange, but without this reinforcement, people will be reluctant to be part of “Oyster” projects which are the seedbed of products that may represent the future of the company.
In this video, SmartOrg’s CEO David Matheson gives a lecture on portfolio management at Stanford University. In his lecture, he covers key principles of portfolio management, prioritizing your portfolio, framing and better decision-making, as well as his signature portfolio simulation. David will further discuss the four different types of New Product Development/R&D: Bread and Butter, Oysters, Pearls, and White Elephants.
Explore more on these topics
Guest Blogging: The Definitive Guide
Top Trending Topics
Share This
Recently Updated News
