Median Time to Market (TTM) measures how long an idea takes to go from task creation to production release. It's the broadest delivery metric in the flow set, capturing planning, queuing, coding, review, QA, and release together.
What it measures
The elapsed time between when a task is created (in Jira, Linear, ClickUp, etc.) and when its associated work actually reaches production.
How Leanmote calculates it
ttm = production_release_at - task_created_at
Reported as median by default to avoid outlier distortion. Mean and P90 are also exposed.
Production release is detected from your CI/CD or deployment events tied to the task (commonly via PR-to-issue link).
Tasks without a successful production deployment don't contribute.
How to interpret it
TTM is always longer than Lead Time for Changes — it adds the planning and queuing time before code is written.
TTM much larger than Cycle Time means tasks sit in the backlog or "to do" for a long time before work starts. Investigate intake and prioritization.
Stable TTM with rising Cycle Time usually means planning got faster but execution slowed.
What to do about it
Reduce backlog age before adding new ideas. The fastest TTM win is usually pruning, not coding faster.
Slice work earlier so tasks are started sooner after creation.
Pair with Lead Time decomposition (coding, review, release wait) to see whether TTM is dominated by pre-work or post-work delays.
Related metrics
Lead Time for Changes
Cycle Time
Flow Efficiency