A measure is the smallest trackable unit of work in elyvate. It represents a concrete action - defined by a clear objective, one or two responsible owners, and a fixed due date. Measures are the link between strategy and execution: they translate KPI deviations, risks, or optimization goals into specific steps that teams can plan, track, and complete.
Without measures, targets remain intentions. With measures, every gap has an owner and a deadline.
From work package to measure - understanding the hierarchy
elyvate is built around a clear three-level structure. Understanding where measures fit helps your team work with precision and avoid confusion.
Work package - a defined operational area, such as a specific supplier, process, or function. It groups all related KPIs, targets, and measures under one owner and provides the broader context.
Measure - a concrete action within a work package, defined to close a gap, resolve a deviation, or drive an improvement. Each measure has exactly one or two owners and one due date.
Task (outside elyvate) - sub-steps within a measure that teams may manage internally, but which are not tracked as standalone items in elyvate.
This structure keeps accountability clear and reporting consistent. A work package answers "what area are we managing?" - a measure answers "what are we doing about it, and who is responsible?"
Why are measures defined?
Measures are not created arbitrarily. They are always tied to a specific reason - either a deviation from plan or an identified opportunity. In practice, four types of measures are most common:
Countermeasures - defined reactively when a KPI deviates from its target or a problem is detected on the shop floor. The goal is to correct the deviation and bring performance back on track as quickly as possible. Example: a supplier delivery rate drops below 85% - a countermeasure is defined to stabilize logistics within the next two weeks.
Optimization measures - defined proactively to improve a process or result, even before a critical deviation occurs. These are used when there is headroom for improvement or when upcoming ramp-up phases require early preparation.
Preventive measures - defined based on identified risks - before they materialize. Particularly relevant in supply chain management, where early action prevents escalation. In task force practice, these usually come straight out of the project's risk discussions.
Escalation measures - defined when a deviation or risk exceeds the scope of a single work package and requires cross-functional alignment or management intervention. (This is a reason for creating a measure, not the same as the Escalated status - for that, see Escalation flow.)
What every measure has
Regardless of type, every measure in elyvate follows the same structure. This ensures consistency across the entire project and makes tracking reliable.
Title - a concise, action-oriented description of what needs to be done
Owner - exactly one or two responsible users, not a team or group
Due date - a fixed deadline, not an open-ended timeframe
Status - current state of the measure: Not Started, In Progress, Off Track, Need Support, Escalated, Completed
Priority - reflects urgency and impact by marking as top measure, used to sort and filter across the Board
Problem statement (optional) - a structured description of the root cause or deviation that triggered the measure
Comments and updates - all relevant communication, decisions, and progress notes logged directly on the measure
The combination of an owner and a fixed due date is non-negotiable. A measure without both is not actionable - it is a note. elyvate makes both visible everywhere, so gaps stand out.
How measures connect to KPIs
In elyvate, KPIs and measures work side by side - but their connection is intentionally lightweight. When a KPI signals a deviation - a red or yellow traffic light or a negative trend - the team is prompted to define a measure in response. This makes the relationship visible and actionable, without enforcing a rigid stored link between the two.
The exception is the Glidepath chart type: here, measures are directly wired to a KPI, creating a tracked, data-driven connection between target and action (see Glidepath).
For all other KPI types, the logic stays conceptual. A red KPI is a signal - it's up to the team to define the right measure and manage the response. In the KPI Collection view of each work package, you can see at a glance which KPIs are on track and which require action. From there, measures can be created directly - keeping data and action visible in the same place, even when the link isn't stored automatically.
Measures in the Plan view
All measures across your work packages are accessible in the Plan section. The Board gives your team a consolidated view of every measure - sorted by status, criticality, or due date. You can create new measures, update existing ones, reassign owners, or move cards between columns as work progresses.
Changes made on the Board are reflected immediately in the corresponding work package view. There is no duplication, no manual sync required - everything stays connected.
Good measures - what separates them from weak ones
A well-defined measure is specific, time-bound, and owned. A weak measure is vague, open-ended, or assigned to a team rather than a person.
Good measure: "Implement daily check-call with Tier-2 supplier for critical component X - Owner: J. Müller - Due: 06.06.2025"
Weak measure: "Improve supplier communication - Owner: Procurement team - Due: end of Q2"
The difference matters. Vague measures create ambiguity, delay escalation, and make reporting unreliable. elyvate's structure - combined with Antonella AI's Draft Refiner - helps teams formulate measures that are clear and actionable from the start.
Key principles
One or two owners per measure - no shared accountability
No measure without a due date - urgency must be explicit
Every deviation deserves a countermeasure - problems without a response are risks waiting to grow
Measures are living items - update status and comments as work progresses
Link measures to KPIs - traceability from data to action is what makes reporting credible