Omg I’m just planning a metrics workshop. Great minds @Jonathan Courtney j

Awesome to see everyone. Really enjoyed the collaboration and respect for within the group. Looking forward to the next ones.

@Bente Steffensen I use sailboat (dev retro), then HMW (epics) and then action plan to create a backlog for prioritisation (features). The additional trick I’ve learnt is talk in dev language and the repour of the facilitator builds quickly.

@Kevin Devine I only used it because there were silos and egos in the room, and nobody was working with each other, they were competing against each other and hurting company profits. This approach worked as when I said "it's failed, and in the news", immediately everyone commented and grouped together. This was the goal I wanted to achieve, as I needed to remove blame from the start. I would only advise using this approach if there is politics and teams not communicating with each other where its hurting the company and affecting the brand.

@Chris Bradshaw

Looks like we have a majority forming, I’ll book a table for 630 - 9. It is a school night after all. 😂

@David Richardson thanks for sharing. This sounds to me like you need to map out the customer/business journey in its current state, and then map out the data sources + gauge the data quality (this will be their governance process) and then identify HMW release a better customer experience/business automation and increase CapX / reduce OpX. I called such engagements - AI Ideation sessions. They are effectively an LDJ as to @Rebecca Courtney suggested, but with a 'data twist'. Here's my 'Workshop Receipt'. - Time: 2-3 hours - Tools: all the toys from this list - https://www.linkedin.com/feed/update/urn:li:activity:7108085233710682112/ - Expert interviews - 30 mins of what the problems are and why they think AI could solve this. Start Strong: - Ice breaker - I used lego and ask participants to use the lego to express how they think the world would look like with AI working with Humans (don't talk about it) Collect: (where are the problems) - Sailboat - whats working, not working, why do we think AI could solve this. Collate: (what problem should we focus on) - Capture the problems voted on in sailboat and run a HMW using 'data' to do this. - Vote on the HMW to focus on. - Create a process map and capture a high level journey of people, process, data and tech. (see attached example of a template I created) - Solution Analytics opportunities using the template, identifying who the customer is and what data source should be used. Choose: (Find opportunities with data and AI) - Prioritise solutions using dot voting. - Decide and prioritise what to execute using the Eisenhower matrix split across important for business growth, research for business, change something now, do later. Commit: (Data Discovery and User behaviour discovery) - Make the solutions actionable for what needs to be tested i.e. what data needs further investigation, what user behaviours need further investigation, what business processes need further understanding (Roadmap maybe, its more action plan to find evidence and then map out a roadmap).

Just one more point on this @David Richardson . I've worked with many clients in the past who fall into the 'shiny object trap', this often leads to disappointment that AI will solve their problem. This workshop helps with this. Make sure your clients walk away with knowing what pain point they are solving for - (HMW is so crucial here), and then dive into problem and solution to identify how to implement it.