Skip to main content

Posts

Showing posts with the label Product Management

The two-ear Product Manager: Why balanced listening is your superpower

As a software architect I've worked with multiple product managers over the years. Most of them position themselves as the "voice of the customer" or the "bridge between business and technology." Recently, while listening to the Software Captains podcast interview with Peter Janssens(in Dutch) about Product Management, Peter shared a quote that perfectly crystallized what effective product management really should look like in practice: A product manager has two ears and should use them equally—one ear to listen to the business and customers, one ear to listen to the product and development team. This simple metaphor aligns with my experience when my collaboration with a product manager resulted in the best possible products. I unfortunately worked with some product managers that only used one ear, resulting in a mediocre product, budget overruns and lack of innovation.  The two ear product manager really makes all the difference. So if you are a produ...

Your first application version will s*ck

Pardon my French, but I cannot state it in any other way; the first version of your application will s*ck. Allow me to explain... In the beginning of a software project a lot of things are unclear. You don't know the business, requirements are vague (and in fact there is not such a thing as a requirement ), the architectural qualities need to be defined, and so on… And let us not even start talking about the ‘unknown unknowns’. If you use all this vague information to create a project plan, a signed of requirements list, detailed use cases, your solution architecture and I probably forgot some other things, it should not be a surprise that the first release of your application will have room for improvement. In a traditional project based waterfall approach, you are in big trouble because there is only one application version typically delivered at the end. So users end with a sub-optimal solution. Let the change requests come to arrive at something that is at least usabl...

Red pill vs Blue pill -Outcome not output

After more than 15 years in the IT industry, working on both small and large projects in multiple industries and companies, I  have to make the following (unfortunate) observation: Although the raise of Agile and Product thinking, most organisations still operate in a project mindset not product mindset. To explain the difference between the two, I have to talk about outputs vs outcomes . What are outputs? Outputs can be seen as deliverables, something like a feature or a new product release. The succes of a project oriented team  is measured in output(e.g. Velocity; how much story points did we deliver in this sprint?). Did the team succeed in delivering features according specification and on time? A consequence of this mindset is that the team is not focussed on whether a delivered features got used or if the feature really solved the business problem. We may assume that the delivered features will lead to specific outcomes. We may even share those assu...