Transformation Initiatives require changes to people, processes and systems. But it can be all too easy to get fixated on technology, especially if it’s new, shiny and expensive. This week Joe and Jason discuss the importance of collecting a broad range of ‘capability requirements’ that describe the culture that we seek to build, how people will work in the future, and the processes and systems they will use to deliver to their customers. We discuss the benefits of engaging multi-functional teams in gathering requirements, and consider the decisions you need to make about accepting requirements into scope. Not all requirements are equal, or even valid. Capability requirements should be the living, breathing bedrock of your transformation and used throughout design, testing and eventually to measure the benefits you’ve delivered. It can be all too easy to easy for your requirements documents to get forgotten and gather dust in a drawer. For more on this and other practical hints and tips, please take a listen.