Stakeholder Telephone
ELI5 - The Vibe Check
The client tells the account manager they want a 'quick tweak.' The account manager tells the product manager it's a 'small feature.' The product manager tells engineering it's a 'simple flag.' By the time it reaches you, the requirements have mutated three times and nobody left in the chain actually knows what the client originally asked for. That's stakeholder telephone, the same distortion as the childhood game, played with your sprint.
Real Talk
Stakeholder telephone describes the progressive distortion of requirements as they pass through multiple layers of people relaying information secondhand, each paraphrasing based on their own understanding and priorities. The fix is reducing the number of intermediary layers between the requester and the implementer, or getting requirements in writing at the source rather than relayed verbally.
When You'll Hear This
"Can we get the client on the call directly? I don't trust another round of stakeholder telephone." / "By the time the ticket reached me it had been through so much stakeholder telephone it barely resembled the original ask."
Related Terms
Backlog
The backlog is the master to-do list for a product — every feature, bug, and idea that hasn't been built yet, prioritised by importance.
Epic
An epic is a big chunk of work that's too large to finish in one sprint, so it gets broken down into smaller user stories.
Scope Creep
Scope creep is when a simple feature request slowly grows into rebuilding the entire application.
Ticket
A ticket is a single unit of work in a project management tool — it could be a bug to fix, a feature to build, or a task to complete.
User Story
A user story is a tiny description of a feature from the user's perspective, written in plain English: 'As a user, I want to reset my password, so that I c...