1. Purpose of the gate
Opportunity accepted is the gate that decides whether a market signal earns the time of a small concept team. Before it, the work is watching: customer requests, segment trends, standards changes, process and packaging options, and the moves of competitors. After it, named people spend a bounded amount of effort shaping a product concept and a business case. The gate exists so that this effort goes to the opportunities most likely to pay back, rather than to whichever idea has the loudest sponsor.
The decision is deliberately light compared with the gates that follow. Nobody commits development funding here, and no product requirements exist yet. What the gate does commit is attention, which is the scarcest resource in a product organisation. A good opportunity gate therefore asks four things and only four: is the customer need real and stated by customers rather than assumed, does it fit the strategy and the portfolio, does it compare well with the other opportunities competing for the same people, and is there a concept team with a time box. These are the four criteria the product lifecycle sets for this gate.
The gate also protects the portfolio from drift. Every accepted opportunity is a small promise that may grow into a programme; recording why each was accepted, and why others were not, gives later lifecycle and portfolio reviews a trail they can check. No engineering lifecycle has a matching gate here, but engineering leadership contributes the first technology and standards scan, and its view of feasibility starts at this point.
10 more sections for registered members.