The 'Highly Requested' Feature... by the CEO
Description
This meme uses the popular three-panel format featuring Victoria Beckham and David Beckham. In each panel, Victoria is on the left and David is on the right, peeking suspiciously from behind a door. The dialogue progresses as follows: Panel 1 - Victoria: 'USERS REALLY WANT THIS FEATURE', David: 'BE HONEST'. Panel 2 - Victoria: 'IT'S HIGHLY REQUESTED', David: 'BY WHOM?'. Panel 3 - Victoria, conceding: 'THE CEO', David, knowingly: 'THANK YOU'. This meme format originates from a documentary clip where David calls out Victoria for claiming a 'working class' background. The humor here is adapted to a common tech workplace scenario. It satirizes how product managers or stakeholders sometimes present executive mandates as broad user demand. The skeptical developer, represented by David, sees through the corporate jargon to uncover the true source of the 'request' - the Highest Paid Person's Opinion (HiPPO), rather than genuine, data-backed user feedback. This resonates with any developer who has had to build a 'pet feature' for an executive
Comments
13Comment deleted
The fastest way to get a feature to the top of the backlog is to have it requested by the user who signs the paychecks
Great news - after a ‘data-driven’ strategy meeting of exactly one very important person, our quarterly OKR is now to ship the CEO’s weekend epiphany… yesterday
After 20 years in tech, I've learned that 'data-driven decision making' actually means the CEO had a dream about a feature last night, and now we're A/B testing whether to implement it in Q3 or Q4
Every engineer knows the hierarchy of feature requests: 'Users want this' translates to 'I want this,' 'highly requested' means 'asked twice in Slack,' and 'the CEO wants it' is the only honest answer that actually explains why you're about to refactor your entire architecture to add a button that changes color on Tuesdays. At least when it's executive-driven, you know exactly whose demo will break in production and whose calendar you'll be interrupting at 2 AM
Prioritization MoSCoW method: Must-have if CEO whispered it, Should-have if users voted, Could-have never, Won't-have forever
Our data‑driven roadmap runs WSJF on a dataset with one record: user_id='ceo'; cost of delay equals your weekend
In enterprise, “users asked for it” is just the HiPPO’s accent - cue an OKR for a feature with zero DAU in telemetry
If CEO is the [main] target audience, then why not? Comment deleted
If CEO is the [main] target audience then why? Comment deleted
If CEO is the [main] target audience then? Comment deleted
If CEO is the [main] target audience? Comment deleted
If Comment deleted
just return true, goddamit! Comment deleted