Applying Wardley Maps to YOUR domain

Wardley Maps can be used in almost any domain. But this does not mean that the method can automatically be used meaningfully in every context without prior considerations. The basic mechanics of a map remain the same, but patterns and influences on the landscape being mapped depend on the domain. Using software architecture as an example, I will show in the session what challenges exist to apply Wardley Mapping to a specific domain and give practical tips on how to overcome the first hurdles.

Transcript

1. Bild:[December 21, 1944], HQ Twelfth Army Group situation map https://www.loc.gov/item/2004630293
 @Tom_Asel
 Applying Wardley Maps …
 
 … to YOUR domain!
 Battle of Antietam, Md., LoC https://www.loc.gov/item/gvhs01.vhs00259/

2. What is YOUR domain?
3. https://www.uml-diagrams.org My domain: Software Architecture https://www.uml-diagrams.org https://jaxenter.de/domain-driven-design-2 https://alistair.cockburn.us/hexagonal-architecture475 https://twitter.com/NathanLee/status/890136808109027328
4. ? 
 Considerations
 In my domain...
 • … which capabilities are of strategic importance?
 • … what are the characteristics of evolution?
 • … what forces drive evolution?
 • … what types of capabilities are relevant?
 • … what patterns do apply?
 ? 

5. ? 
 Considerations
 In my domain ...
 • … which capabilities are of strategic importance?
 • … what are the characteristics of evolution?
 • … what forces drive evolution?
 • … which types of capabilities are relevant?
 • … what patterns do apply?
 ? 

6. • Don't get bogged down in the complexity of your domain. • Start with a schema that helps to identify Users and needs in your context. Explore your domain!
 Focus on the essentials!
 Purpose
 Scope
 User (Anchors)
 Needs
 Moral imperative “Why of Purpose” What is on scope, What not? Find Focus! Who are The Users within Scope? “Know your Users” What are their needs?
7. Purpose
 Scope
 User (Possible Anchors)
 Needs

8. ! 
 Purpose
 Scope
 User
 Needs
 We produce high quality software products by providing just enough architecture to get the Job done in Time! Always! IN: Development Operations Project Mngmt OUT: Marketing Customer Care Sales Developer Functioning Workspace Quality culture Start small
 ! 

9. Anchor
 Foo
 Bar
 Baz
 Boo
 Visibility
 Start small
 Need
 • Start with a single user and only few needs. • You can always add more to the map later on. • Do so, if the map proofs to be valuable only. • Collect potentially useful capabilities • Keep in mind: There is no such thing as a perfect map. • Don’t waste too much time on trying to create on
10. A clean start ...
 … simplifies further mapping
 Visibility
 Novel
 Best
 Evolution
 Emerging
 Good
 Dev-Team
 Foo
 Bar
 Baz
 
 
 
 Boo
 Modifiability
 Time behaviour

11. ? 
 Considerations
 In my domain...
 • … which capabilities are of strategic importance?
 • … what are the characteristics of evolution?
 • … what forces drive evolution?
 • … what types of capabilities are relevant?
 • … what patterns do apply?
 ? 

12. Evolution & Movement
 Evolution
 Uncharted Domain
 Industrialised Domain
 Chaotic
 Uncertain
 Unpredictable
 Changing
 Different
 Exciting
 Future Worth
 Unusual
 Rare
 Poorly Understood
 Experimentation
 Differential
 Competitive Advantage
 
 
 Ordered Known Measured Stable Standard Obvious Low Margin Essential Ubiquitous Defined Volume Operations Operational Efficiency Cost of Doing Business Past
 Future

13. What is the state of evolution for this?
 Evolution
 Uncharted Domain
 Industrialised Domain
 Chaotic
 Uncertain
 Unpredictable
 Changing
 Different
 Exciting
 Future Worth
 Unusual
 Rare
 Poorly Understood
 Experimentation
 Differential
 Competitive Advantage
 
 
 Ordered Known Measured Stable Standard Obvious Low Margin Essential Ubiquitous Defined Volume Operations Operational Efficiency Cost of Doing Business Architectural component

14. Characterize evolution!
 Architectural component
 Our understanding of code
 Testability
 Robustness
 Available Support
 Stability
 Code Quality
 Maturity of technologies used
 Available Resources
 Knowledge of technologies used
 • Find the characteristics of the components of your domain • Collect, map, brainstorm, … them!
15. Visibility
 Experimental
 Sustainable Planning
 Evolution
 Usable
 Efficient
 • Characteristics change as capabilities evolve • Find appropriate names for the stages of evolution Characterize evolution!

16. Visibility
 Evolution
 Uncharted Domain
 Industrialised Domain
 Efficient
 Usable
 Experimental
 A map of a systems architectural building blocks
 + testing + robustness Web-UI
 Contract Handling
 Authorization
 Message Broker 
 lack of knowledge of modern technologies AI-Advisor
 Contract-System Adapter
 Maintenance-Team
 REST API
 Sustainable Planning

17. ? 
 Considerations
 In my domain...
 • … which capabilities are of strategic importance?
 • … what are the characteristics of evolution?
 • … what forces drive evolution?
 • … what types of capabilities are relevant?
 • … what patterns do apply?
 ? 

18. “Everything evolves through supply and demand competition”
 
 - Simon Wardley

19. Advice: 
 Investigate domain-specific effects on evolution
 • What enables or hinders movement? De-Accelerators
 Accelerators
 + Movement
20. Visibility
 Evolution
 Uncharted Domain
 Industrialised Domain
 Product
 Custom
 Genesis
 What forces affect evolution?
 Commodity
 Platform
 + Competition
21. Visibility
 Evolution
 Uncharted Domain
 Industrialised Domain
 Efficient
 Usable
 Experimental
 What forces affect evolution?
 Sustainable Planning
 Platform
 + Competition Architectural component
 Software Aging
 Past success with legacy infrastructure

22. ? 
 Considerations
 In my domain...
 • … which capabilities are of strategic importance?
 • … what are the characteristics of evolution?
 • … what forces drive evolution?
 • … what types of capabilities are relevant?
 • … what patterns do apply?
 ? 

23. Map your understanding!
 • Anchor: Yourself / Team / …
 
 • Visibility: Relevance for you / Team / …
 
 • Evolution: Degree of your understanding
 
 • Choose appropriate names for the stages of evolution (e.g. Practice)
 
 • Movement: What can be done to improve your understanding
 Visibility
 Novel
 Best
 Evolution
 Emerging
 Good

24. Visibility
 Evolution
 Uncharted Domain
 Industrialised Domain
 Good
 Emerging
 Novel
 How well is our understanding of the building blocks of a system?
 Dev-Team
 Best
 Web UI
 AI-Advisor
 (experimental)
 Authorization
 
 
 
 
 
 Contracting Module
 
 
 
 
 
 
 Messaging-System
 Adapter
 
 
 
 
 
 
 Message Broker
 (COTS, Standards)
 REST API

25. Use symbols for different types of capabilities
 Visibility
 Genesis
 Commodity
 Evolution
 Custom
 Product
 Novel
 Best
 Emerging
 Good
 Experimental
 Sustainable Planning
 Usable
 Efficient
 • For example: • Products: What we use • Understanding: What we know • Artifacts: What we create • Name the stages of evolution to fit the capability types characteristics • Provide a visual legend Artifacts:
 Understanding:
 Products:

26. Visibility
 Evolution
 Uncharted Domain
 Industrialised Domain
 Good
 Product
 Emerging
 Custom
 Novel
 Genesis
 Map: Intended strategy to improve our knowledge
 Contracting Module
 Dev-Team
 Best
 Commodity
 Process
 Know-How
 Understanding of Contract Platform Platform Documentation
 Contracting-
 Platform (Commercial product)
 Missing knowledge of contracting platform
 Expert knowledge on processes not yet established
 + Training, Onboarding
 + Workshop with Platform Provider
 + Demand adequate
 documentation
 + Cross-Functional Team 
 with Domain Experts
 Efficient
 Usable
 Experimental
 Sustainable Planning

27. ? 
 Considerations
 In my domain...
 • … which capabilities are of strategic importance?
 • … what are the characteristics of evolution?
 • … what forces drive evolution?
 • … what types of capabilities are relevant?
 • … what patterns do apply?
 ? 

28. Patterns of YOUR domain!

29. Patterns of YOUR domain!
 !! ! ! ! ! ! !!! ! ! !!! ! ! !!! ! ! ! !! !!! !!!
30. Create a library of patterns for your domain!
 • Find the patterns that can be of value in your domain • Enhance them with existing domain knowledge. • Define new patterns specific to your domain • Don't be afraid to leave out things that don't apply to your domain. • Ditch what is not of use but challenge your assumptions!
31. ? 
 Considerations
 In my domain...
 • … which capabilities are of strategic importance?
 • … what are the characteristics of evolution?
 • … what forces drive evolution?
 • … what types of capabilities are relevant?
 • … what patterns do apply?
 ? 

32. ! 
 Don’t explain the method beforehand.
 Just use it. 
 • “Nobody cares about your precious framework”
 - Ben Mosior
 
 • Let the other person decide if they want to dive deeper.

33. TOM ASEL
 @Tom-Asel
 Tom Asel
 Tom Asel
 mail@tom-asel.de
 +49 6252 6033 536
 www.tom-asel.de
 Q & A