Most firms suffer from having far too many projects in their product development pipelines, for the limited resources available. "Gates with teeth" help to prune the development portfolio of weak projects and deal with a gridlocked pipeline. Also, a robust innovation strategy, coupled with strategic buckets, refocuses resources on high value development initiatives. Note that gates are not merely project review points, status reports or information updates. Rather, they are tough decision meetings, where the critical go/kill and prioritization decisions are made on projects. Thus the gates become the quality control check points in the process ensuring that the right projects move forward and are completed correctly.
Acceptance criteria Gates must have clear and visible criteria so that senior managers can make go/kill and prioritization decisions objectively. Most importantly, these criteria must be effective—that is, they must be operational (easy to use), realistic (make use of available information) and discriminating (differentiate the good projects from the mediocre ones). These criteria can be: •
Must meet: Knock-out questions in a check list, designed to kill poor projects outright •
Should meet: Highly desirable characteristics which are rated and added in a point-count scheme
Example A sample list of criteria is shown below, from which a scorecard can be developed that can then be used to score projects at a gate meeting. •
Must meet (checklist - yes/no) • Strategic alignment (fits
business unit strategy) • Reasonable likelihood of technical feasibility • Meet
EH&S policies • Positive return versus risk •
Should meet (scored on 0-10 scale) • Strategic • Degree to which projects aligns with
business unit strategy • Strategic importance • Product advantage • Unique benefits • Meets customer needs better than existing or competing product • Value for money • Market attractiveness • Market size • Market growth • Competitive situation • Synergies (leverages core competencies) • Marketing synergies • Technological synergies • Manufacturing / processing synergies • Technical feasibility • Technical gap • Complexity • Technical uncertainty • Operational viability • Go to market • Sales, marketing, and billing • Support and operation • Risk versus return • Expected profitability (e.g.,
net present value) • Return (e.g.,
internal rate of return) • Payback period • Certainty of return If the answers are "no" or "low" to many of these questions, the decision should be to send the project back for reconsideration, (such as, to adjust the scope, timelines, funding, or solution) or to kill it off altogether. == Advantages and disadvantages ==