Act as an expert in customer needs identification and prioritization based Outcome-Driven Innovation (ODI) or models directly derivative of it. In ODI there is a type of customer need called a Desired Outcome Statement. There is a mirror concept to this called a Predictive Metric.

### Goal

Your goal is to generative a matrix that aligns desired outcomes statements with predictive metrics. In order to build the matrix, you will need to process the list of desired outcome statements and generate an associated predictive metric for it as described below. Once that is done, you will be able to create the matrix

### Definitions

A desired outcome statement is associated with a Job Step, and a Job Step is a sub-objective of a Job-to-be-Done (a primary goal or objective). This is very important context to consider when constructing a Predictive Metric.

### Construction Rules

When designed for a specific desired outcome statement, a predictive metric must meet the following criteria. It is a single statement that is

- One hundred percent predictive of satisfying the desired outcome for which it was created
- Capable of measuring the degree to which the desired outcome is satisfied
- Controllable in the design of the strategy or solution
- Measurable before the event, e.g., not an after-the-event indicator.
- Appropriate for competitive benchmarking
- Descriptive of an activity that can be addressed to create value
- Free from solutions or any references to technology or time-dependent solutions.
- Free from vague words such as easy, reliable, high-quality, or comfortable.
- Stable over time

A predictive metric is directly associated with a single desired outcome (as a Strong relationship). However, it can have an association with other desired outcomes as well. These associations are categorized as strong, medium, weak, or none; strong being the primary relationship. These are depicted in a matrix where the desired outcome statement is the row, and the predictive metric is the column header. That is the output format that you will generate.

### Strength of Relationship

**The strong relationship is indicated by a solid circle**. This is the metric designed for the specific desired outcome**The medium relationship is indicated by a hollow circle**. The represents a metric that complements, reinforces, and optimizes other activities. This concept is grounded in the fact that the satisfaction of some desired outcomes will predict the satisfaction of other desired outcomes. It could predict, to some degree, the satisfaction of one or more other desired outcomes.**The weak relationship is indicated by a hollow triangle**. There is some relationship with the desired outcome for that row but less so than medium. It is slightly more than none.**The None relationship is indicated by a blank.**There is no direct or indirect relationship for that row

### ###Execution 1

First, generate a side-by-side list of the desired outcomes and their primary predictive metric using the following list of desired outcomes. The side-by-side list should be in a table. There is no need to output any content before or after the table. The list of desired outcomes is related to a(n) {{end user}} trying to {{step}} while {{job}} {{context}}.

{{list}}

### ###Execution 2

**Example Output Format**

In a second table, output each desired outcome statement as a row. Output each predictive metric as a column header. The relationships (strong, medium, weak, and none) are indicated in the matrix cells.

Predictive Metric 1 | Predictive Metric 2 | Predictive Metric n | |

Desired Outcome Statement 1 | ● | ◯ | △ |

Desired Outcome Statement 2 | ◯ | ● | ◯ |

Desired Outcome Statement n | △ | ● |

If formatted correctly, there should be a 45 degree angle of solid circles where it begins at row 1, col 1 and ends with row n, col n.

### Output Instruction

- Generate the matrix
- Output a legend of the relationship strength

### Input Variables

end user: DevOps Engineer

job: **Building an Operationally Efficient and Secure Enterprise Application**

context:

step: **Configure development environment**

list: