A Product Vision "can never be a collective enterprise" — it must be authored and filtered by the single most senior product leader (CPO/CTO/VP Product), with input from the CTO and CFO. The CEO is the #1 stakeholder and, ideally, the vision's heaviest user — reviewing and challenging it, not co-authoring it by committee.
This mirrors why Product Strategy resists committee-drafting: a vision built by consensus loses the point of view needed to actually constrain choices.
Authorship sits with the most senior product leader in the room — CPO, CTO, or VP Product, whichever exists at a given company — not a committee. The CEO is the #1 stakeholder, and ideally the vision's heaviest user: someone who returns to it constantly when making calls, not someone who signs off once. CTO/VP Engineering and the CFO are the key sources of input (feasibility and revenue path, respectively) without being co-authors.
"The number one stakeholder in my opinion for a vision is the CEO."