Influences

The default relationship: the source has some effect on the target.

Definition

An influences arrow says that the source has some effect on the target: it contributes to it, leads to it, causes it, or makes it worse. It is the default relationship, and every other relationship is a refinement of it.

Direction

From the source of influence to what it influences. In a well-formed tree, most arrows flow from the roots toward the outcomes.

When to use it

Always, during construction. Every connection starts as an influences arrow, and the group does not debate what kind of influence it is.

Keep the arrow generic during refinement too, unless the group agrees that a more specific relationship changes the analysis. Some groups say "leads to" or "causes" for a direct, strong link. That is fine in conversation, but it is drawn the same way.

How to draw it

A solid line with a filled arrowhead. It is the only arrow style that does not need a legend entry, because it is the default. See arrow styles.

Examples

• "Insufficient automated test coverage" → "Developers afraid to refactor"
• "Lack of technical leadership" → "Inconsistent architectural decisions"
• "Deployment complexity" → "Slow delivery cycle"

Required or optional

Required. Directional influence is what makes a set of sticky notes a Tree of Influence. A tree that uses only this relationship is complete.