I heard a story of an octogenarian who drove himself to the hospital for his eye cataracts operation. (Just let that sink in a bit.) On his surprisingly safe return home, his relatives queried the sense of his actions. He replied that what he lacked in sight, he made up for in driving experience.
I was recently asked this question:
During the problem exploration phase, what kind of questions should I be asking and how do I go from 1000 problems to the core problems that will unlock the solution?
Here’s my answer:
If one were to heft a half-brick down Old Street in London, there would be high probability of hitting someone currently engaged in building a minimum viable product (MVP) of some sort or another. There’s also almost as high a probability that they’re doing it wrong. Allow me to explain.
Despite relying on each other for the success of their products, the Sales and Product teams often have a jarring relationship. This is far from ideal. By looking at where things go wrong we can identify a better way of working with each other. The prizes on offer: shorter sales cycles, more easily achieved targets and customers who are always happy to hear from you.
People value something most when they’ve just lost it or come close to doing so. If your product prevents this happening, you need to save your client the heartache of loss by helping them remember how much they value what they have now.
Do you spend more time writing documents about your product than actually managing it?
Many companies with some kind of product management function become all caught up in the process, drowning themselves in increasing numbers of documents. These rapidly become overwhelming to manage, contain duplicated detail and ultimately obscure the real objective of product management, namely to create successful products.