← Selected work
CASE 04 / WHAT HAPPENED NEXT?
HR OPERATIONS · EMPLOYEE FOLLOW-THROUGH

A conversation is not follow-through.

Organizations routinely track what they promise customers: the request, the owner, and the due date. Promises made to employees can be harder to see. I built a fictional commitment ledger that asks whether the organization—not the employee—completed the next step.

Open the follow-through review ↓Self-directed project · fictional records · browser-based review
The problemA concern can be acknowledged without being assigned, resolved, or confirmed
What the review shows7 of 18 commitments remain open; 5 are overdue and 2 have no owner
Recommended responseAssign missing owners, update overdue responses, and check receipt of completed responses
CONNECTION TO MY EXPERIENCE

Supported HR with various projects. Alongside my customer retention experience, that work shaped this question: how can an organization distinguish acknowledging a concern from completing its promised response?

ONE COMMITMENT · FT-003

The guidance was recorded. Was the response received?

A Customer Support employee asked who owned after-hours escalations. The Support Manager’s guidance is recorded and the response is marked completed, but employee confirmation is not. I would check receipt and record any remaining question, keeping the completed response and the confirmation gap as separate facts.

Assignment identifies who owes the response; it does not show that work has begun. I track response completion separately from whether employee confirmation is recorded.

How the four checkpoints are countedAssignment, start evidence, completion, and confirmation

Four checkpoints—not one status.

Response status: 7 open + 11 completed = 18 commitments. Open means the promised response is not complete. An open record with no owner is unassigned; an assigned open record is awaiting a response. Assignment alone is not evidence that work started.

Work beginning: the dataset has no separate start timestamp or verified start-status field. For open records, I would ask for dated evidence of the first action rather than infer progress from the owner field.

Confirmation status: 8 of the 11 completed responses have confirmation recorded; 3 do not. Use “Confirmation gaps” to review those three separately. The source CSV retains “Closed” for response completion and “No” for confirmation not recorded.

Counting rule: overdue means an open response with a due date before October 19. The 2 ownerless records are included in the 5 overdue records; these groups must not be added together.

NEXT ACTIONS

Resolve the open promises and check receipt.

Assign owners to the two ownerless responses, request an updated response date for the five overdue commitments, and check receipt for the 3 completed responses without confirmation. The ownerless records are already included in the overdue group.

LIMITS + METHOD

A prompt for a better conversation—not an answer about someone’s intent.

This is a comparison of follow-through, not about treating employees like customers. The ledger holds only work-related commitments, owners, dates, and response evidence. It excludes private messages, health information, demographics, attendance, and performance scoring.

Missing confirmation does not prove the response failed; recorded confirmation does not establish understanding, acceptance, or satisfaction. The data does not measure retention and should not be turned into a personal flight-risk score. Reminders can be automated; the follow-up conversation remains with the responsible person.

This project shows how I would structure and review follow-through. It does not measure retention, diagnose employee sentiment, establish causation, or provide employment-law guidance.