That feeling of aimlessly churning out software is one that grates my nerves. If I don’t understand the business value, and I don’t feel like I’m doing something worthwhile, I don’t take fulfillment from my job. These projects also tend to be the ones that don’t end very well.
Impact mapping is a practice that aims to prevent failed projects - and lack of motivation - by focusing delivery of software projects on the business impacts that they will make.
Many times throughout my career I’ve had to unwind requirements documents to understand the business objectives, and then tell the business there are far better ways of achieving what they want than the fully-specced out requirements document they’ve given me. Impact mapping is a tool that I will now use to streamline and massively enhance this process.
The book itself is a no-frills, to-the-point blend of theory, case studies, and practical examples of building impact maps. I enjoyed reading it, learned a massive amount from it, and recommend it to any developer who doesn’t just see their job as a jira-ticket production line.