4 ms·
Totally agree. But isn't finding out clear priorities from sales and other teams, with the context behind it as well, useful as a PM?
by this2shallPass 7y ago
Totally agree. But isn't finding out clear priorities from sales and other teams, with the context behind it as well, useful as a PM?
- kareemm 7y ago> But isn't finding out clear priorities from sales and other teams, with the context behind it as well, useful as a PM? Absolutely. But: 1. How are they defining clear priorities? With inexperienced support teams it's "here's the most common / last requests I've heard". With inexperienced sales teams it's "here's the feature that 'prevented' me from closing my last deal". I'd rather understand how many people asked for a feature and who they are (enterprise vs SMB plan? active customer vs current prospect vs lost deal?) 2. As a PM I'd prefer to get as much of the context from the requester's own words (e.g. what did they actually write to support? or say to sales?) This is where capturing that snippet and sharing it with Product comes in handy... but this is hard to do at scale with an e.g. spreadsheet.