---
# System prepended metadata

title: Driver Template
tags: [ODIN]

---

## Driver Template

#### Problem statment, or Opportunity?
- 
#### Current Situation
- 
#### Current or Anticipated Effect
- 
#### Relevance for the Organization
- 


## Tips
Aim to create a comprehensive but brief summary in two or three sentences, so that the information is easy to remember and process. If necessary more details about the driver may be recorded below the summary and/or kept in a logbook.

For further guidance on how to describe organizational drivers and requirements in an effective way, check out the following example:

To resolve local issues, teams currently have autonomy to develop their work and decision-making processes in the way they see fit. This often leads to incoherence in how work and decision-making is handled between teams, which impedes effective collaboration on handling dependencies between and across domains.

### 1. Current Situation
“To resolve local issues, teams currently have autonomy to develop their work and decision-making processes in the way they see fit.”

Describe the situation you observe, rather than describing assumptions about what might be missing or lacking. For example, avoid phrases like “teams don’t focus enough on resolving common issues“or “we are lacking coherence between teams”. This way of framing a situation obscures what is actually happening.
Be concise and describe the essentials of what is happening, and, if necessary, the context in which it occurs.
Be specific and avoid vague and ambiguous statements (e.g. use “to resolve local issues” instead of “to resolve some issues”.
Be objective and describe verifiable facts and observations.
Avoid evaluative language (e.g. use “teams have autonomy” instead of “teams have too much autonomy”).

### 2. (Current or Anticipated) Effect
“This often leads to incoherence in how work and decision-making is handled between teams ….”

Explain the consequences that you observe or that you expect could result from the situation.
Be as objective and specific as possible.
Be explicit about whether the effect(s) are occurring already, or if they are anticipated.
If it’s not obvious, explain how you think the effect is a consequence of the situation.

### 3. Relevance for the organization
“… which impedes effective collaboration on handling dependencies between and across domains.”

Explain why responding to the situation is worthwhile for the organization, by describing the benefit of interacting with it, or the cost of not doing so: How would it help the organization to respond to this situation? How would it harm us if we don’t?
Sometimes the relevance of responding to the situation for the organization is already obvious and clear, in which case there is no need to add any further information.