Defines diagnostic intent
The methodology defines what TDF is trying to understand, how evidence should be treated, and the boundaries around interpretation.
Delivery organisations have more metrics than ever, but often less shared understanding. TDF was created to make operational evidence useful, explainable, and safe for teams.
Measurement should create curiosity, not fear; understanding, not judgement; improvement, not theatre.
TDF emerged from a recurring problem: organisations often hold large amounts of workflow data but still struggle to explain why delivery feels slow, unpredictable, or under pressure.
The framework is designed to connect operational evidence to bounded interpretation, useful questions, and system-level improvement without pretending that one number explains complex delivery work.
These principles shape the framework, the services, the Jira product, and every diagnostic presented.
The subject is how work flows and what conditions surround it, not who appears busiest.
Every diagnostic should show the evidence and measurement context that supports it.
Configuration, history, and the nature of the work matter more than universal benchmarks.
The goal is to improve the delivery system, not decorate status reports or create league tables.
TDF is a methodology first. Services apply it with people; software implements selected diagnostics where teams work.
The methodology defines what TDF is trying to understand, how evidence should be treated, and the boundaries around interpretation.
Human-led diagnostics help teams and leaders investigate delivery behaviour in a real organisational context.
Delivery Diagnostics for Jira makes selected TDF diagnostics available inside the Atlassian ecosystem.
The Jira application is one way to apply TDF. The methodology and diagnostic principles stand independently of any single implementation.
Start a conversation →