📎 Webclip
You need to talk with real users in order to build good software | Joca on stuff
The post argues that Product Management and Experience Design are as critical to successful software projects as DevOps, Continuous Delivery, Testing, Agile, and Lean. Product Management defines what needs to be done and in what order, while Experience Design defines how it should be done from the user experience perspective.
It says Product Management should talk with real users, understand the pain the system is meant to solve, and bring that information back to developers and experience designers. The post also says requirement gathering is incomplete if the team listens only to the system owner and not to the real users, since the owner may know business goals but not what is valuable for their own customers.
Reading notes#
- Product Management and Experience Design are presented as key techniques for successful software projects.
- Product Management tells what needs to be done and in what order.
- Experience Design tells how the work should be done from the user experience perspective.
- Product Management is described as the link between system users and the team that will build the system.
- The role is distinguished from Business Analysis, which is said to focus more on the business and system owners.
- Requirement gathering is said to be incomplete without listening to the real users of the system.
- The post says a company may ask for features to reach a business goal, but that is not enough on its own.
- The team should define the minimal set of features that creates value for the customer in the first release.
- The post cites MVP and MMF as terms for that minimal set of features.
- It says the Agile Manifesto values customer collaboration and early delivery, but the customer may still not know what is valuable for their own customers.
- Product Managers are responsible for understanding users, the problems they have, and sharing that with developers and experience designers.
