A library digital-card Product Vision is 'get a working card in the resident's hand the same day.' Marketing wants a social-feed feature that polls show people like but that does not advance same-day issuance. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Vision is a bouncer, not a suggestion box. A popular social feed can still be the wrong nightclub. If it does not move same-day cards into residents' hands, it waits — no matter how shiny the poll looks.
Full Explanation
Product Vision filters opportunities for a library digital-card product. When the vision is same-day issuance of a working card into a resident's hand, a popular social-feed feature that does not advance that outcome should be declined even if polls score well. Popularity alone is not a Product Vision. Adding the feed at the top of the Product Backlog because survey scores are treated as vision confuses preference with strategic direction. Creating a second current Product Goal for engagement so both ideas stay active dilutes focus and pretends two primary goals can both be current without cost. Asking Developers to squeeze the feed into the current Sprint as stretch work undermines the Sprint Goal and Done. Exam caveat: vision is a filter—say no to attractive work that does not advance the stated outcome. Operational check: map the feed to same-day issuance; if it does not move that outcome, park or reject it, and keep Sprint capacity on issuance path items that residents can complete the same day. Same-day library card issuance as vision means popular engagement features that do not advance issuance lose; that is the filter working. Keep Sprint capacity on issuance-path items and park the social feed until it has a causal link to the outcome.