Thread by @SteveElsewhere

If you're excited to leverage #WardleyMapping, #DDD, #ValueStreamManagement, and #TeamTopologies, order of execution can help smooth the journey.

One should launch you into the other well prepared to create value. Here's a flow that sets you up for success: 🧵

First, clarify needs, objectives, obstacles, and a vision for your future state. You can use Outcome Mapping or a press release formula for this (ideally both).

Working backwards always helps you avoid wandering or drift from working forwards, and brings a team into alignment.

Wardley Mapping helps understand your current ecosystem and what the future could look like if you change things. This is a great place to start to discover current work streams and focus your efforts.

DDD helps you define your focus and connect dots within current architecture. It provides a starting point to measuring current state flow and customer centric thinking.

Value Stream Management starts with understanding of value and working backwards from a customer outcome via a Value Stream Map. You can follow that map with a future state map. Where a Wardley Map shows the network of capabilities, a Value Stream Map shows how they're delivered.

With an understanding of your value stream(s) and current performance, you can start to design team topologies that enable optimal flow - which likely brings you to addressing dependencies and establishing platforms.

To drill deeper here you can use Dependency Mapping and Capability Mapping to evaluate and prioritize the most critical risk areas in your ecosystem.

This can bring you back to DDD as your new team(s) can define architecture based on this learning that delivers optimal outcomes.

You may also consider Customer Journey Mapping to connect customer experiences with your delivered capabilities.

Armed with all this insight and definition your team(s) will have not only clarity to execute autonomously based on qualified hypotheses, but also effectively communicate what they know and plan to amongst themselves, peer teams, leadership, and even customers.

The insight, hypotheses, and next steps can be run through a prioritization framework (like WSJF) and into a Flow Roadmap of Now / Next / Later to be effectively communicated.

A Flow Roadmap isn't for features, it's for capability and workflow changes. It's People and Process.

To ensure you continue to operate at peak performance and improve over time, you can instrument your workflow with Value Stream Management tooling to track and reveal the ROI of efforts and the evidence of your tested hypotheses.

This may seem like a lot, but it all happens in 2 hour collaborative workshop sessions with clear artifact results, and each session catapults you into the next. You finish with a visual, measured, and dots-connected navigation plan for your path from here to your target.

Even if you know exactly how to get there, this serves as GPS nav for everyone else: The exec who needs to be convinced, the penny pincher, the hesitater, the contrarian, the new kid, the board, your nemesis, and on and on.

Beyond a plan it's a recipe for powerful conversations.

If you're interested in chatting about this or have a challenge this approach may fit, I'd love to hear from you!

This was inspired by an excellent talk and case from @suksr and @matthewpskelton in @InfoQ

Check it out here! infoq.com/presentations/…