We discuss facilitating effective collaborative mapping workshops and creating Wardley maps for strategic planning in businesses. We look at the importance of creating a safe environment, effective facilitation techniques, and involving all stakeholders in the mapping process.
We also highlight the benefits of embracing diversity and respecting different opinions. And we share various approaches to creating and utilising Wardley maps, including Miro and Lucid, and learning more about the technique through Ben Mosior LearnWardleyMapping.com resources.

Wardley Mapping techniques and anti-patterns.
Dave Anderson and Mark McCann discussed anti-patterns in Wardley mapping, including "gaming the system" (Dave Anderson).
The speakers shared their experiences and insights on how to avoid common mistakes in Wardley Mapping (Dave Anderson, Michael O'Reilly).
Collaboration is key in mapping exercises, as it helps to identify blind spots and improve the overall quality of the map.
It's important to strike a balance between mapping by yourself and collaborating with others to ensure a richer feedback loop and improved map quality.
Michael O'Reilly suggests mapping a subject matter to identify blind spots and derive questions to ask (0:05:10)
Dave Anderson advises against re-creating architecture diagrams and instead focuses on higher-level abstraction (0:06:27)

Software development, components, and abstraction.
Dave Anderson and Mark McCann discuss the challenges of defining and understanding components in software development.
Experience and wisdom are key to summarising complex conversations and determining the appropriate level of abstraction for components.
Dave Anderson and Michael O'Reilly discuss the importance of context in understanding a Wardley map, with examples from their own experiences.
They emphasize the need to introduce new people to a shared conversation gradually, rather than expecting them to pick it up quickly.

Facilitating workshops, mapping, and collaboration.
Michael O'Reilly and Dave Anderson discuss the importance of mapping in strategy development, highlighting its ability to shake out key elements and dependencies.
Mark McCann emphasises the value of psychological safety in a top-down environment, where managers must create a safe space for team members to share their thoughts and ideas.
Dave Anderson and Mark McCann emphasise the importance of creating a safe environment where participants feel comfortable sharing their opinions and asking questions.
Facilitators should be open and non-forced in their approach, allowing participants to take the lead and challenge each other's perspectives.

Using Wardley mapping to understand user needs and dependencies.
Dave Anderson and Mark McCann discuss the importance of identifying the user and their needs in the mapping process.
They use specific examples and exercises to help the group understand and clarify their thinking.
Dave Anderson and Mark McCann discuss the importance of collaboration in product development, using sticky notes and online tools like Miro and Lucid to facilitate brainstorming sessions.
They emphasise the need to keep the collaboration process simple and focused, with clear goals and a structured approach to ensure everyone's voice is heard.
O'Reilly and McCann discuss using Wardley mapping to structure innovation sessi

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Dave, Michael, and Mark discussed the application of Wardley Mapping in understanding movement and making strategic decisions. They share their experiences with the method, emphasising its ability to visualise and track changes in tech stacks and capabilities.
They also discussed the importance of context, user needs, and facilitating meaningful conversations through mapping.
Additionally, they highlighted the benefits of mapping for challenging each other's thinking and fostering creative dialogue.
Later, they discussed the importance of understanding user needs during agile transformations, including the value of having a shared representation of collective experiences and strategies for removing barriers to change in an organization.

Outline
Using Wardley mapping to improve understanding of complex systems and software development.
Dave Anderson and Mark McCann discuss the history of Wardley mapping, including when they first learned about it and how it has evolved over time.
The hosts emphasise the importance of mapping movement and tracking progress in the context of technology and capability, citing examples from their own experiences.
Mark McCann: Focusing on user needs in Agile transformations helped teams understand why they were delivering code.
Michael O'Reilly: Participating in mapping sessions helped him understand technical nuances and communicate with non-technical stakeholders.
Mark McCann: Identified value chain visibility as key to success
Dave Anderson: Custom skill sets and implementations were hindering progress

Challenging inertia points in team decision-making.
Dave Anderson and Mark McCann discussed the importance of mapping out problems and inviting team members to contribute their perspectives.
The team used a structured approach to thinking deeply about problems and coming up with solutions, which helped to challenge assumptions and identify areas for improvement.
Identifying and addressing inertia points is crucial for strategic maneuvering.

Leadership principles, including courage, collaboration, empathy, and narrative.
Dave Anderson and Michael O'Reilly discussed the importance of courage and collaboration in tackling complex problems.
They emphasised the need for shared understanding and mapping with other teams to make better decisions.
The importance of context in mapping: Understanding the user's needs and perspective is crucial for effective mapping.
Empathy and narrative: Mapping can facilitate empathy and storytelling, but it's important to show the map to the right audience.

Principles of Wardley mapping for strategic planning.
Michael O'Reilly and Mark McCann discuss the importance of simplifying complex systems through Wardley mapping, focusing on the principles of abstraction and dialogue.
Dave Anderson emphasises the importance of not overcomplicating the model, and using it as a facilitation for meaningful conversations.
Dave Anderson and Michael O'Reilly discuss the importance of mapping in facilitating creative conversations.
They outline the eight principles of Wardley mapping and its benefits in understanding a company's value chain.

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

The Value Flywheel Effect is a pattern seen in organisations where business strategy and technology strategy align, leading to more sales and growth.
The hosts discuss the concept of the value flywheel effect, its origins, and how it applies to creating software for customers.

Dave Anderson and Mark McCann discuss the four phases of the value flywheel process, with three principles for each phase, aimed at building momentum and sustainability in organizations and teams.
Clarity of purpose is the first principle, visualised as a data-informed Northstar, helping teams understand their core user needs and improve situational awareness.
Software development principles, including focus, clarity, and understanding the market.
Michael O'Reilly and Dave Anderson discuss the importance of aligning individual and team goals with the overall organisational Northstar.
They emphasise the need for a clear problem statement and direction to focus attention and achieve success.
Michael O'Reilly and Dave Anderson discuss the importance of focusing on time to value in product discovery, rather than just time to market.
They emphasise the need to map the market and clarify the business's purpose, rather than just focusing on individual silos or software pieces.
Dave Anderson looks at the importance of understanding a company's strategy and market position, even for software engineering teams.
Mark McCann suggests that junior engineers can gain valuable insights by analysing a company's website, LinkedIn, job postings, and press releases to understand their competitors and industry landscape.

Engineering team structure, process, and enablement.
Michael O'Reilly: Embrace diverse teams for success, learn from failures.
Mark McCann: Socio-technical systems crucial for successful teams.
Michael O'Reilly and Dave Anderson discuss the importance of enabling and empowering engineers in High Performance Engineering, including creating a generative environment and mapping the organisation for enablement.
Mark McCann adds that removing friction points and impediments is crucial, including developer enablement, handoffs, and carving off certain things to encourage smaller approaches.

Prioritising tech stack, offloading non-differentiating tasks, and mapping solutions to customer needs.
Focus on delivering value, not just building code.
Dave Anderson emphasises the importance of prioritizing tech stack and deciding what to move to the right, while Michael O'Reilly and Mark McCann discuss the benefits of mapping out the tech stack and identifying key differentiators for the business.
Modernising software development and delivery using AWS Well-Architected Framework.
Dave Anderson looks at the importance of preventing problems before they occur in software development.
Mark McCann highlights the need to understand the ecosystem and constraints when implementing continuous delivery.
Mark McCann: Celebrate successes in fraud prevention, reward employees for going above and beyond.
Dave Anderson: Keep a low carbon footprint, measure efficiency and sustainability in cloud workloads.
Mark McCann and Dave Anderson discuss the importance of well-architected frameworks for cloud migration and sustainability.
They highlight the 12 pillars of well-architected, including map emerging value and spot inertia, to help organizations identify areas for

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube