1. Selected result
Target, current state, dates, owner, scope, and customer, project, revenue, or strategic consequence.
Data readiness
Useful analysis starts with a measurable result, current work, accountable owners, meaningful states, visible waiting, and a leader who can act on the finding.
Readiness check
Perfect records are unnecessary. Missing fields must be visible so leadership understands which conclusions remain weak.
Target, current state, dates, owner, scope, and customer, project, revenue, or strategic consequence.
Relevant teams, managers, shared specialists, approval roles, and legitimate access.
Contributing work, owners, states, dates, dependencies, and clear scope boundaries.
Owners or queues, meaningful states, blockers, dependencies, start, completion, cancellation, and enough history.
Named waiting point, queue count, wait rule, aging threshold, rework, and input quality.
Affected customers, deals, projects, dates, or costs with clear estimate and weighting rules.
At least two plausible causes and recorded evidence that favors or weakens each one.
A leader can change priority, release, policy, sequence, ownership, training, or capacity.
Baseline, matching measure, suitable review period, outside changes, and maintained work states.
Identity, access, privacy, retention, data flow, security, and procurement requirements.
Readiness result
The label should state what the current record can support and what must happen before a stronger conclusion.
The result, current work, owners, waiting, and authority are sufficient. Record remaining gaps.
The product can compare causes, while history or exposure limits confidence.
Missing or stale records would make the recommendation misleading.
No measurable result, current record, authority to act, or verified product scope.
We will use the current records, name the missing evidence, and decide whether self-service, repair, a pilot, or no fit is appropriate.