Asana

Asana exposes a broad set of object types: tasks, projects, milestones, portfolios, goals, time tracking entries, stories, and teams. This integration focuses on tasks and time tracking entries, which constitute the primary unit of work and the most directly attributable performance signal in any Asana workspace. Projects and goals were examined but excluded: project-level status fields are set manually and attributed to a manager rather than measured from individual contribution; goal metrics are a premium feature with a progress source that is often manual entry. Six KPIs were retained, selected against three criteria: ability to attribute to an owner, resistance to gaming, and balance between leading and lagging indicators.

Throughput and delivery quality

Tasks Completed and On-Time Completion Rate

Tasks Completed counts the number of work units a person delivered in a period. On-Time Completion Rate measures the proportion of tasks with a due date that were closed on or before that date. Neither indicator is meaningful in isolation, and the design of the pair is deliberate: a high Tasks Completed count may result from rushing work to closure before it is genuinely done, while a high On-Time Completion Rate achieved over a very small volume reveals nothing about capacity. Read together, they distinguish between productive throughput and the appearance of productivity. A person with high volume and low on-time rate is likely overloaded or poorly organized; a person with a high on-time rate over low volume may be under-utilized or handling only lightweight tasks. The combination is the actual management signal.

Milestones Completed

Milestones Completed tracks the delivery of phase gates rather than individual work units. Milestones are structurally less gameable than general task counts because they are planned in advance with stakeholder visibility and correspond to meaningful project checkpoints, not administrative subdivisions of work. This makes Milestones Completed a higher-signal outcome indicator than Tasks Completed for project-level performance assessment. Where a general task count rewards granularity of decomposition, milestone count rewards commitment delivery.

Workload risk and execution efficiency

Overdue Open Tasks and Average Task Cycle Time

Overdue Open Tasks counts tasks that are past their due date and remain open. It is the only leading indicator in the task block: it surfaces a deteriorating situation before it becomes a missed delivery. A growing overdue count on a given person is an early warning of workload overload, poor prioritization, or planning failure, and it appears in the data before it affects the On-Time Completion Rate of the current period. The value of Overdue Open Tasks is precisely that it makes risk visible while there is still time to intervene.

Average Task Cycle Time measures how long tasks take from creation to completion, on average. It captures the execution pace of an individual rather than their volume of output. A long cycle time relative to peers, on tasks of similar scope, may indicate execution blockers, unclear ownership, or dependencies that delay progress. The relationship between Average Task Cycle Time and On-Time Completion Rate is a tension worth monitoring: a person can achieve a high on-time rate by consistently working on small tasks with short due dates, while carrying a high average cycle time on more complex work. Reading the two together prevents this blind spot.

Effort investment

Hours Logged measures the total time a person has recorded against tasks in a given period. It is a leading indicator in the sense that it reflects effort allocation — where attention is going — before outcomes materialize. When read alongside Tasks Completed and Average Task Cycle Time, it reveals whether high output comes with proportionate effort (sustainable execution) or whether there is a growing gap between time invested and deliverables produced (inefficiency or scope creep). Hours Logged is only meaningful in workspaces where time tracking is actively used; teams that do not log time will show zero for this indicator, which should be interpreted as a data absence rather than a productivity signal. This KPI requires the Asana Premium, Business, or Enterprise plan and will be omitted for workspaces where the time tracking endpoint is unavailable.

Scope and limits of the integration

Asana records task status transitions and assignments, but does not measure the quality of work delivered. A task marked complete may correspond to a thorough, well-reviewed output or to a minimal closure made under deadline pressure; the API data does not distinguish between the two. Cycle time and on-time rates reflect the mechanics of execution, not the substance of what was produced.

Attribution is singular: each KPI is assigned to the task's single assignee. In collaborative work where multiple people contribute to a single task without it being subdivided, contribution is invisible to the integration. Similarly, work that happens outside Asana, in documents, calls, or informal coordination, generates no signal. The reliability of these KPIs depends directly on team discipline in maintaining accurate assignments, due dates, and completion status: when that discipline is strong, the indicators are a genuine management tool; when it is inconsistent, the data reflects the quality of task hygiene more than the quality of work.