Connections and dependencies

Which work supports each Objective, and what depends on what?

Link work to the Objectives it supports, record what must finish first, and waytrk checks the dates.

InsightsConnections: what supports and depends on what

In three steps

  1. Link work to what it should move

    Above the work: the Key Result, Objective and priority it is meant to help.

  2. Record what must finish first

    Arrows run from the work needed first to the work that waits. One Owner proposes, the other confirms.

  3. waytrk checks the dates

    Every time a date changes. A conflict goes to both Owners; waytrk never moves a date.

Start with one team, free

Free for good, with no card. Rather see it first? Try the example plan in your browser.

Larger view

Scroll to see all of it; Escape closes it.

Help

Connections and dependencies

What am I looking at?

How work is linked to what it supports, how you record what must finish first, and how waytrk checks the dates. The picture builds in three steps. The examples come from one invented 80-person engineering firm, the same on every page.

Words on this page

Company priority
One of the few themes your strategy focuses on.
Objective
Something the strategy sets out to change.
Key Result
A dated target that shows an Objective's progress.
Initiative
A piece of planned work.
Function
A team, department or service, with its own plan.
Dependency
One piece of work needs another to finish first.
Timing conflict
Work planned to start, or finish, before the work it needs has finished.
Plan alternative
A copy of a plan with different dates or costs, to compare before choosing.
Change impact
How much a piece of work changes people's jobs, rated from 0, no change, to 5, fundamental.
Owner
Keeps a Function's plan current and decides on suggested changes.