This week we held a successful show and tell. We learned a number of lessons along the way and this weeks blog is our attempt to share our learning.
The first point is an obvious one but worth a gentle reminder and that is making ‘design’ choices to meet the different needs, learning styles and interests of the different stakeholders.
To this end we created 5 personas. These helped us to think through and then ‘design-in’ key insights and learning-points, so that they could make a meaningful connection to the session.
- The first was the senior manager ‘Lucy’. She was very busy working across the portfolio and wanted to understand and appreciate the strategic ‘big picture’ and then the ways by which this particular project stage (as expressed in the Show and Tell or Demo) neatly weaved together in the overall project’s narrative. For ‘Lucy’ we created a colourful and metaphoric visual poster. The poster expressed the narrative of an exploration ‘discovery ship’ taking their journey; and whilst doing so stopping-off at various ‘treasure’ islands before reaching ‘The New World’ that signified the project end date in December. Lucy would also want to understand the ways by which the functions and services shape the product.
- The next persona was ‘Keith’. Keith understands his professional world from diagrams and work-flows as well as appreciating the logical parts between the key sequences. Keith is an Agile Architect. To meet his needs we had a ten minute slot from our Architect that provided first-class diagrams and an excellent explanation alongside.
- Next, we imagined that Jack ‘saw’ the project from the customer’s functional and experiential perspectives. Examples came to mind from marketing, customer insight, sales and other external or customer facing departments. For ‘Jack’ we had a ten minute slot from our UX team member. She very neatly weaved the functionality with the User Interface screens with the end-to-end clicks. She also provided evidence from her applied research with Users and the ways by which UX insights are shaping and have shaped the iterative product development in exciting, fresh and innovative ways.
- ‘Tony’ was interested in the detailed technical side of things. We saw Tony as a .net developer with interests in BDD and UX. We hoped that his needs would be met by a blend or combination of all the ten minute slots; but perhaps more especially by the UX and Architectual slots.
- Lastly, was imagined that ‘Tom’ was an analyst. For his needs we shared the insights from our team leader BA. She also included what we had delivered to date, as well as highlighting the work that was out of the current scope. Her upbeat and engaging report noted what work packages would be picked-up in the portfolio/programme at some future point. To bring a sense of ‘wholeness’ or Gestalt to the Show and Tell, our final speaker was our Product Owner. He deliberately selected a simple, clear but very poignant and powerful message that clarified the ways by which the project’s capability enabled transformation in two important ways. Firstly, for customer centricity and lastly, for enabling the changes needed for the businesses operating model.
The next lesson is the need to practice and gain feedback. We did this in three ways. Firstly, as a team we filmed ourselves and gave each other candid feedback. Next, we did a second ‘dry-run’ in the same room that we were using for the Show and Tell. We did this as we wanted to test the IT equipment to ensure that everything was working as we hoped. Of course, if there were any last-minute glitches then these could be resolved in a timely manner. Lastly, after we finished the Show and Tell we also invited participant feedback using ‘post-it’ notes.
It is fair to say that this has been our most successful Show and Tell to date. The team have received life-affirming feedback both formal and informal; which is reassuring as we made a short film by way of dissemination for those stakeholders that could not make the date/time. It is our team’s hope that by sharing what worked for us that this may give rise to questions for you, and perhaps your team, in terms of the ‘design features’ that might work for you and your various stakeholders.
Take care, Jason