Facts-to-Feelings Support Loop
Convert workplace frustration into evidence, diagnosis, and an actionable change
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 6
- Confidence
- 91%
The loop begins by taking an employee's feeling seriously without treating the feeling itself as a complete diagnosis. The manager asks for specific events, tasks, hours, decisions, or communication failures and reviews available documentation. If the concern involves workload, a time audit shows where effort is actually going and whether the issue is excessive volume, inefficient systems, unclear priorities, or a mismatch with the defined role. The manager then changes an actionable fact—such as a broken process, missing detail, resource allocation, or expectation—or clearly restates a legitimate role requirement. This approach avoids dismissing emotions while preventing an unstructured feeling from becoming the endpoint of the conversation. Follow-up determines whether the factual intervention improved the employee's experience.
Origin
Jasmine Star described using documentation and time audits to turn reports of overwhelm into operational changes. Extracted from The Jasmine Star Show.
Core principles
- 01Feelings deserve care but cannot diagnose an operating problem alone
- 02Documentation turns frustration into something leaders can change
- 03Observable facts separate workload from workflow and role issues
- 04Changing relevant facts can improve the experience behind a feeling
How to run it
- 1
Receive the feeling
Listen to the concern and acknowledge that the employee's experience matters. Avoid debating whether the person is entitled to feel that way.
Pro tip Reflect the concern briefly before moving into diagnosis.
Watch out Do not use a request for evidence as a way to dismiss the person.
- 2
Ask for specifics
Request concrete examples of the tasks, events, omissions, or interactions behind the concern. Translate broad language such as unsupported or overwhelmed into observable situations.
Pro tip Ask what happened, when it happened, and what work was affected.
Watch out Leading questions can pressure the employee toward the manager's preferred explanation.
- 3
Collect evidence
Review notes, project records, communication history, deadlines, and relevant metrics. Use a time audit when the central concern is excessive work.
Pro tip Keep receipts on recurring process failures so patterns become visible.
Watch out A single metric may miss interruptions, emotional labor, or poorly recorded work.
- 4
Identify the responsible fact
Determine whether the evidence points to workload, an inefficient system, missing information, unclear ownership, or a defined role expectation. Agree on the diagnosis where possible.
Pro tip Separate the volume of work from the friction involved in completing it.
Watch out Do not assume that recorded hours alone prove the employee's experience is invalid.
- 5
Change or clarify
Repair the process, redistribute work, supply missing information, or clarify the requirement indicated by the evidence. State what will be different and who owns the change.
Pro tip Choose an intervention that can be observed and reviewed later.
Watch out Vague reassurance leaves the underlying conditions untouched.
- 6
Reassess the experience
Follow up after the intervention and ask whether the concern improved. If it did not, gather new evidence and repeat the loop.
Pro tip Set the follow-up date during the original conversation.
Watch out Closing the issue immediately after making a change can conceal an incorrect diagnosis.
In the wild
An employee says she feels unsupported because she is working too much. Her manager asks which work is consuming the time and conducts a time audit. The audit records 37 hours, prompting a deeper discussion about whether the problem is inefficient tasks, disliked responsibilities, unclear priorities, or the role itself rather than raw hours alone.
→ The conversation moves from a broad feeling to a specific issue the manager and employee can address.
A project coordinator repeatedly receives incomplete briefs. Instead of reporting only frustration, she records which fields are absent, the delays they cause, and the projects affected. Her manager adds mandatory fields and ownership checks to the intake system.
→ The factual record produces a process correction that reduces repeat frustration.
Common mistakes
Treating feelings as the diagnosis
A feeling identifies a real experience but may not reveal whether the cause is workload, process friction, communication, or role fit.
Using data to invalidate emotion
Evidence should guide support and operational change, not be used to prove that an employee should not feel distressed.
Gathering facts without acting
Documentation builds trust only when leaders use it to repair a condition or clarify an expectation.
Is it for you?
Best for
It is best for recurring workplace concerns where the employee and manager need to identify an actionable operational cause.
Not ideal for
It is not ideal for emergencies, harassment reports, or health crises that require immediate protective or specialist support.
From the transcript
“That's a feeling. Give me facts. I can change the facts to get a different feeling.”
“I care so much about your feelings that if I don't change the facts, you're never going to change your feelings. So help me with…”
“Great. Let's move into a time audit.”
From the episode
How to Get Your Team to Buy Into Your Vision