How PMs Say No to Feature Requests

𝗨𝗻𝗹𝗲𝗮𝘀𝗵 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗵𝗲𝗹𝗹


👉Do you want to write a user story for it?
👉Why don’t you add it as an agenda item to the next QPS meeting? I’m sorry your topic got bumped. We can always discuss it next quarter.
👉If you could get the engineering resources, I’ll gladly PM it for you.

𝗣𝗿𝗲𝘁𝗲𝗻𝗱 𝘁𝗼 𝗲𝗺𝗯𝗿𝗮𝗰𝗲 𝘀𝗰𝗶𝗲𝗻𝗰𝗲


👉What does the data say? No data? No feature for you.

𝗕𝗮𝗻𝗶𝘀𝗵 𝗶𝗻𝘁𝗼 𝘁𝗵𝗲 𝗯𝗹𝗮𝗰𝗸𝗵𝗼𝗹𝗲


👉Sure, I’ll add it to the product roadmap.
👉Ok, I’ll create a JIRA ticket.

𝗨𝘀𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀 𝗮 𝘀𝗵𝗶𝗲𝗹𝗱


👉Did you talk to any customers?
👉Let’s discuss it at the annual customer advisory board meeting.

𝗜𝗻𝘃𝗼𝗸𝗲 𝗮𝘂𝘁𝗵𝗼𝗿𝗶𝘁𝘆


👉Let me ask the CEO.
👉I need to consult with engineering.

𝗕𝗹𝗮𝗺𝗲 𝗶𝘁 𝗼𝗻 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴


👉I asked to engineer, and they said it wasn’t doable.
👉I asked to engineer. They want to do it, but they’re backlogged.
👉The next handful of sprints are earmarked for tech debt.
👉Next year is the soonest we’re doing new feature work.
👉We could build it, but privacy and compliance would block the launch.

LinkedIn
WhatsApp
Twitter
Pinterest
Facebook
Scroll to Top