Life of a Business Principal in Consulting

Context The current typical model of starting a large program is to have a discovery workshop for the program followed by detailed project inceptions. The project inceptions are spaced and detailed. There are not a lot of discovery workshops we do that is mutual discovery. It is more of sense making of an earlier discovery process. The Pitfalls and some thoughts With the discovery process feeding into the project Inceptions was great. it gave direction. However, validation of the direction based on feedback from projects seems to be missing. The reason the feedback is missing is 2-fold: #1 - The discovery workshops don't seem to have a cadence with the project Inceptions #2 - The team that does discovery workshops is to involved with the project inceptions and vice versa,

Before I jump into the topic, I will start with some context. We were working on a very complex product - Complexity in multiple dimensions. As a team, We needed a simple way for us to understand how we manage complexity as team scales and use it as a simple communication tool.  To generalise: Context: A complex project A fairly large team High Volatility Product Engineering team Challenges A way to manage complexity as a team Tool for communication on progress  A mechanism to calibrate progress with the bigger roadmap Crystal Ball Crystal Ball is a simple tool for visualising progress on a granular scale. It helps in tracking progress and for teams to look at what they can achieve going forward.  It helps in internalising the progress that the team made in the past few weeks and then relate to it as they plan forward. How we used it Our team was fairly big - a 7 pair dev team with 3 Was , 1 BA and a PM. We also had an XD and a UI develope