I think it's at least £6,000 Euros, it might have gone up to £8,000 - it's hard to find, here's one random link i found - Workshopper Master by Aj&Smart (Overview & Pricing) (facilitator.school)

Hey @Ricardo Luiz I'd start with their vision and whether it's bold enough to achieve what they are setting out to do...bit vague and often they're not clear, so i'd help them by discussing: - What's the market like they are in, is it in maturity, decline (ref: life maturity model) - Do they want to penetrate a new or existing market with a new or existing product - What are the key success factors in the market, e.g. customers want low cost, digital experience, etc - What is the market like? (ref: VUCA) - is it volatile, uncertain etc.. - Then look internally - what are their strengths, weaknesses - To determine how they can achieve competitive advantage from what they offer as strengths in to the market, dependent on all the above bullet points - Talk about their customers - do they truly understand their customers behaviours? that customer journey from awareness - interest - contact - purchase - loyalty - All of the above is classic design thinking discovery and will lead to customer surveys, personas, market analysis to frame opportunities to then ideate some hypotheses to go run experiments to test And all of that Ricardo is a 1 on 1 at strategy level discussing market, product, service, customers and all that fundamental up front key topics

Hey Kimberley, quick brain dump of ideas for you: - Start with a retro, looking back over 2024 with just 2 titles; what needs to be improved and then move on to what worked well on post it notes (i love magic whiteboards so you can take up lots of space on a wall or Miro if online). - After clustering the post it notes into categories, vote on the highest priority ones you want to tackle, using prioritisation methods such as importance / urgency matrix or MoSCoW for those real must haves - Root cause on the priority ones to prevent recurrence, some will be harder as cultural and of course you don't want it to be anti-management or getting personal, but what you can do is get the team to frame a few problems. - It's surprising how long the above will take. - Day 2, get everyone to stand up, imagine a line on the ground going from left to right. To the left is the past ... that's done, can't be changed, it's gone. Look to the right into the future, the to-be, the tomorrow and ask everyone to take a step to the right. Then say, this is us now closing off the past and starting afresh, creating a new and better future. - Naturally you want to address how to make lives better, so Team Canvas for purpose, likes, team agreement. A few big ones - (1) building an operating rhythm, a predictable heart beat and this is where Scrum is great, e.g. 10-day chunks of time, day 1 plan out what we're doing as a team, who, when, how + daily 15min stand ups + review on day 10 and a team retro. For this team, a regular retro is key. (2) Kanban for visibiltiy of the work and creating a flow including decision making. - I could go on...lol...but will pause there as a quick brain dump :)

Hey @David Marin okay, so this is user experience discovery stage, which is the first stage in the Design Thinking methodology, to lead to framing some clear problem statements and then ideate, create hypotheses and run experiments to test those hypotheses. So you're discovering the problems (that become challenges and opportunities) and with Stakeholders + team members, you are wanting to know the as-is pains, problems, issues, thorns, moans, groans. Therefore, I would recommend: - Collecting the pains, so you could literally have an open whiteboard and post it note all issues. Now, that could become chaotic, so if you can focus in on whether it's process, product or system or policy and then get them to free their minds and add lots of post it pains. Naturally, facilitating by throwing out open, probing questions, 5 whys, what, why, etc. Then clustering the post its under categories (usually process, system, data, etc) - You might do some follow up empathy map interviews to get more detail on the pains / problems to frame them. - You might create a customer journey map to prompt pains, inefficiencies. Or you might create a user story map with a backbone of activities that an end user carries out and again add pain points. - If you can vote on and agree top pains using priority matrix on importance / urgency or prioritise using WSJF etc - And get to a place to turn those problems into How Might we (HMW) challenge statements in a follow up workshop, then happy days.

Hey @Harkiran Brar I'd say "no". I would move into similar roles that include more facilitation, like Scrum Master, Delivery Lead, Agile Coach roles, looking at methods such as Scrum, SAFe, Kanban, Design Thinking and build up more exposure into facilitation within those roles ))