All about writing and prioritising requirements: commercial, market, technical, functional, non-functional. Whatever you call them, this is the place for you
» A PM’s vibe coded prototype is just another way to dictate requirements to the team
» Just because you can build features more quickly doesn’t mean you should build them
» Greater strategic discipline than ever is needed to build worthwhile products
How can product management fit into an agency business model? Spoiler alert: _not easily_
I was recently asked this question:
Can you make suggestions of how best to distil users’ wish lists of requirements/outcomes to a core handful that will encompass most people’s problems?
Here’s my answer:
Last time I published an article explaining why I thought roadmaps were a little like DVD box sets. DonorDrive product manager Kasey Marcum (@kaseymarcum) asked in the comments:
“Always enjoy your posts, Jock! I really love the high level idea of this. What does this actually look like in the wild?”
Imagine your roadmap and sprints being as engaging as a hit movie – just think how much easier they’d be to “sell” to your stakeholders and customers! Let’s see how you can do this.
An intriguing and nonintuitive aspect of customer satisfaction is that sometimes the feature that provides the most satisfaction is one that customers didn’t know they wanted until they saw it. – Mike Cohn For how long have you been prioritising …
Link of the Day: Kano tutorial via Mountain Goat Software Read more
We product managers are a surprisingly upbeat bunch considering that we seem to spend a good proportion of our time making compromises. We very rarely get the opportunity to deliver everything we need in a product in the best possible way.
When we start thinking about the requirements for a new product version, I bet we all make the same mistake when deciding what goes in: we guess solutions rather than find problems.
I was discussing recently the importance of getting a product installation or upgrade process right for customers. Here are some guiding principles from a usability perspective that you may wish to consider when defining your product’s requirements.
I strongly believe that all software companies should have a manifesto or a set of guidelines for usability.
If you want to succeed in global markets with a ‘one size fits all’ approach, you may want to reconsider that strategy. Pay as much attention, if not more, to getting the local details right.
