Convert Obsidian into a Workbench for Strategic Planning with Wardley Maps and Excalidraw

Wardley mapping is presented as a practical workbench for strategic planning: it turns a messy business landscape into a shared, visual blueprint of how a system delivers value—and then guides choices about what to do next. The core idea is to sketch a work system (a business, market, or service) by placing customer-facing needs and the people who benefit at the top, then tracing the value chain down to the underlying chain of needs that makes those offerings possible. That structure matters because it forces teams to align on a common understanding of the landscape before debating strategy, and it anchors decisions to what customers can actually see.

The framework also links strategy to two organizing principles. First, the “true north” is the customer: what sits higher in the value chain is more visible to end users, while deeper components are less visible and therefore require different management approaches. Second, the horizontal placement signals evolutionary stage—how far a component has progressed from rare and uncertain beginnings to industrialized, standardized commodity. Simon Wardley’s evolution is described in four stages (genesis, custom-built, product, and commodity), with the message that there is no universal playbook. Instead, different stages call for different tactics: in-house agile development fits genesis work, lean practices support product development by emphasizing learning and waste reduction, and six sigma or outsourcing is suited to commodity components.

To make the planning cycle actionable, the transcript ties Wardley mapping to broader strategic thinking. It distinguishes “why” as purpose (winning the game) versus movement (advancing a piece on the chessboard), and it references a strategy cycle associated with John Boyd’s OODA loop and Sun Tzu’s art of war. The map is then extended with three layers of analysis—landscape, climate, and doctrine. “Climatic patterns” are the forces that change the map regardless of actions; the transcript highlights two: everything evolves and no one size fits all, noting that Wardley introduces 30 such patterns. “Doctrine” consists of universal principles that tend to remain useful across contexts; the transcript cites 38 doctrines, including focusing on user needs, using common language, and challenging assumptions through the act of mapping.

Finally, the transcript argues that strategy isn’t only about choosing the right doctrine—it’s about selecting the right “gameplay.” Examples include using open approaches like open source or open data to accelerate evolution, or using patents to ring-fence technology and slow its progression. While pen-and-paper and Post-it notes can work, the practical emphasis shifts to turning maps into living knowledge in Obsidian using Excalidraw. The workflow allows components to become clickable links, supports layered maps, and connects drawings to stored background notes. The transcript recommends starting with a simple map, then using linked resources (including “Wardlepedia”) and importing frequently used patterns, doctrines, and gameplay into a vault for later reference and sharing.