Flow Engineering

When to use Flow Engineering with an Outcome Map?

Collaborative mapping is an underrated capability in organizations. It can be used to create clarity across complex domains and many individuals.

It brings separate perspectives and individuals together to create a common understanding.

This process of mapping the business landscape, choosing a direction, and navigating is called flow engineering. The ultimate goal of these efforts is to sustainably improve the flow of value to customers.

The Process

1. The Outcome

Start with the end in mind. Starting from that point, let facilitators guide the team through breaking down what the outcome actually looks like and what stands between the team and the outcome in the next steps.

2. The Whys

After defining the target and guardrails, the outcome map defines the larger context that it serves. It captures the 'whys' of the outcome. The 'whys' should consider at least three audiences:

• customers

• the organization

• individual contributors

Try to connect the outcome to critical targets like OKRs, external factors, guiding principles, and values, which anchor the outcome in the team. They should make it very real, tangible, and powerful as motivation for moving forward.

3. The Obstacles

The next thing to explore is what is going to get in the way of the desired outcomes. Looking at obstacles - the things that could hinder our progress - brings all the potential fears and challenges into the open. Chance to talk about concerns or pessimistic views early before it's more costly to address.

4. Investigations

Now consider investigations that will improve your understanding and provide insights on the best approach forward.

5. Measures

Define key measurements that will provide you with a sense of progress so that you and others know they're headed in the right direction. The measures can change over time while new information and understanding surfaces.

Source: Blog Post by ITrevolution.com