TTC Analysis
TTC methodology is not defined in the founder brief. Possible meanings include Time-To-Close (lead or ticket), Time-To-Convert, or Total-Cost-to-Company. OrionStats will not invent a methodology. The data below supports the time-based interpretations; the project will be completed once the founder confirms the definition, unit, start/end events and business use.
The scenario and data are provided, but tasks that depend on the undefined business rule are marked and must not be assumed.
Business scenario
Placeholder scenario pending definition. Candidate data: leads.created_at → converted_at (time to convert) and support_tickets.opened_at → resolved_at (time to close).
Problem statement
To be defined by the founder: which process is measured, which events start and stop the clock, and which decisions the metric supports.
Learning objectives
- (Pending) Measure a process duration correctly once defined
- (Pending) Analyse its distribution and drivers
Instructions
Do not start this project until the definition is published. Questions to resolve: What does TTC stand for in your organisation? Start and end events? Calendar or business days? Are open (unfinished) cases included? Which target or SLA applies?
Tasks
- Awaiting definition.
Deliverables
- Awaiting definition.
Evaluation rubric
| Criterion | Weight | Excellent | Proficient | Developing | Insufficient |
|---|---|---|---|---|---|
| Awaiting definition | 100% | Rubric will be defined with the methodology. | Correct and complete with minor gaps in rigour or presentation. | Partly correct; important steps missing, unvalidated or unclear. | Missing, incorrect, or not supported by the data. |