Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/latticecut/Wardley_Chapter2_Finding_a_path
Figures 8 and 11 from the book by S Wardley to demonstrate drawing Wardley Maps in LaTeX
https://github.com/latticecut/Wardley_Chapter2_Finding_a_path
Last synced: 6 days ago
JSON representation
Figures 8 and 11 from the book by S Wardley to demonstrate drawing Wardley Maps in LaTeX
- Host: GitHub
- URL: https://github.com/latticecut/Wardley_Chapter2_Finding_a_path
- Owner: latticecut
- License: other
- Created: 2019-06-02T18:59:11.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2019-06-10T14:18:49.000Z (over 5 years ago)
- Last Synced: 2024-01-25T02:09:06.681Z (10 months ago)
- Language: TeX
- Homepage:
- Size: 963 KB
- Stars: 4
- Watchers: 3
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
- awesome-wardley-maps - Wardley Maps in LaTeX - Figures 8 and 11 from the book by Simon Wardley to demonstrate drawing Wardley maps in LaTeX. (Templates / Mapping)
README
# Wardley Map for Chapter 2 "Finding a path"
> "it has always been standardisation of components that has enabled creations of greater complexity" - Simon Wardley
This is a Wardley Map for Chapter 2 of Simon Wardley's [online book](https://medium.com/wardleymaps/on-being-lost-2ef5f05eb1ec) on topographical intelligence for business strategy [Wardley2016][1]. Full details can be found here (reading time ~24 mins): https://bit.ly/2zI1tpY# The first map
Wardley Mapping has proved a useful tool for that can serve as a basis for framing the analysis of technology maturity and helping develop business strategy.
This is an example of visualizing Wardley Maps and Value Chain dependency networks in LaTeX. It aims to provide a simple and easy method to create, visualize and modify Wardley Maps that is consistent with best practise in collaboration, document management and version control. My main motivation is to create a mapping workflow that can work well across teams and document versions etc. In this reagard working with GitHub and the [Overleaf](https://www.overleaf.com/) hosted LaTeX editor has proved successful.
The example is based on the PGF/Ti*k*Z languages for producing vector graphics from a geometric/algebraic description. PGF is a lower-level language, while Ti*k*Z is a set of higher-level macros that use PGF and an interpreter written in TeX by Till Tantau.
You can find an introductory video to get started using Ti*k*Z here: [Basic Drawing Using Ti*k*Z](https://www.youtube.com/watch?v=pcIzeN46ETc)
Particular focus is made on the software usability and interoperability with other tools. Simple maps can be directly created in LaTeX, while more complex networks can be imported from external sources (e.g. NetworkX, QGIS, ...) although I don't go that far in simple example.
The map is simply a collection of different `.tex` files that allow you to build up the representation of a business. Whilst this is a simple example I have kept the file structure similar to a more complicated project, decomposing the final Map into different Layers, Plates and Strata and separating Vertices and Edges into different `.tex` files. As the practice of mapping matures it is likely that this decomposition will evolve to a standard form.
This example makes use of tikz-network.sty from Juergen Hackl but it is entirely possible use plain Ti*k*Z. The Ti*k*Z manual can be found [here](https://arxiv.org/pdf/1709.06005.pdf)
You can see an example of the final figure Figure 11 downloaded as a [pdf](pdf/Wardely_Chapter2_Finding_a_path.pdf) in the folder structure.
## Figure 8
Figure 8 is what a map of a single line of business should look like. Simon created the first map in 2005 and it was for an online photo service.
This has been split out into a single stratum, the Application Layer with two `.tex` files for nodes (V) and edges (E) respectively.
![alt text](https://github.com/latticecut/Wardley_Chapter2_Finding_a_path/blob/master/images/Fig8.png "Chapter 2, Figure 8")
## Figure 11
Here we add example annotations using the `Fig11_Annotation.tex` file over the top of the Map from Figure 8. Comment out as desired.
In practice a lot of the code in this file is just about styling, for example the formatting of the Key, and can be ignored during the normal mapping process. However, I have tried remain faithful to Simon's original style/rendering.
![alt text](https://github.com/latticecut/Wardley_Chapter2_Finding_a_path/blob/master/images/Fig11.png "Chapter 2, Figure 11")
# Further Reading
Simon Wardley's [online book](https://medium.com/wardleymaps/on-being-lost-2ef5f05eb1ec) on topographical intelligence for business strategy.
# References
[1]: Simon Wardley. Wardley maps: topographical intelligence in business. 2016.
License: [CC-SA](LICENSE.md)