wm-atlas-evolution-mismatch

Wardley Map mismatch analysis detects components where the execution strategy conflicts with the evolution stage, such as building commodities or outsourcing genesis. It flags over-investing, under-investing, and missing decorators to produce a mismatch-annotated map and detailed report.

Strategic execution fails to align with component evolution stages when deliberate choices or accidental misalignments cause inefficiencies. Mismatch analysis differentiates between intentional strategy plays and unintentional errors where execution strategies conflict with the current evolution stage.

To detect components lacking an execution strategy on your Wardley Map, perform a decorator analysis to scan for missing build, buy, or outsource decorators. The analysis highlights these gaps alongside over-investing and under-investing mismatches in a detailed report.

Yes, you need Node.js to render mismatch-annotated Wardley Maps. The analysis process requires Node.js for OWM rendering via cli-owm to generate the visual mismatch-annotated map and the accompanying detailed analysis report.

The best way to analyze over-investing in commodity components on a Wardley Map is to evaluate execution strategies against evolution stages. This analysis flags components built in-house that have become commodities, suggesting outsourcing as a more efficient strategy.