Bring observable evidence
Separate what happened from assumptions about attitude, intent or personality.
← All toolkits
Manager routines
Feedback and Expectation Reset
Describe the observable gap, restate the standard and agree on support and follow-through.
Use this when
Start with a live team problem.
- A recurring performance issue has become frustrating.
- Previous feedback was understood differently by each person.
- The manager has delayed the conversation because it feels personal.
How to use it
Move from context to one usable agreement.
Restate the standard and impact
Explain the expected result, why it matters and where the current outcome differs.
Agree on change and support
Ask for the person’s view, define the next behaviour and set a near-term review.
Worked example
Resetting a missed customer-update standard
Use the example to understand the level of specificity. Replace the content with evidence from your own team.
OBSERVATION The last two Friday customer updates were sent on Monday, after the agreed deadline. EXPECTED STANDARD Active customers receive the update by Friday noon, including progress, risks and decisions required. IMPACT Customers entered the weekend without visibility and the support team handled avoidable questions on Monday. TEAM MEMBER PERSPECTIVE Thursday data arrives late and the owner waits rather than escalating the missing input. AGREED CHANGE Escalate missing data by Thursday 3 pm and publish with a clearly marked exception if it remains unavailable. SUPPORT Manager will confirm the escalation rule with Data Operations. REVIEW Check the next two update cycles.
Blank template
Feedback and Expectation Reset
Copy this into Docs, Notion or your existing workspace, or print it for a team conversation.
FEEDBACK AND EXPECTATION RESET Person: Manager: Date: OBSERVATION What happened? Use specific, observable evidence. EXPECTED STANDARD What result or behaviour was agreed? IMPACT Why does the gap matter? TEAM MEMBER PERSPECTIVE What context, constraint or disagreement needs to be understood? AGREED CHANGE What should happen differently next time? SUPPORT What will the manager or business provide? REVIEW When will progress be discussed? RECORD OF COMMITMENTS -
The System Folks · Free founder resource · thesystemfolks.com/resources/feedback-expectation-reset
Common mistakes
Keep the tool connected to real work.
- 01
Using labels such as careless or uncommitted instead of evidence.
- 02
Talking around the issue without naming the required standard.
- 03
Agreeing on change without removing a real capability or system barrier.
Why this works
Evidence behind the resource
Learning improves when teams can discuss errors and concerns without avoiding interpersonal risk.
Read Psychological safety and learning behaviourNeed help implementing it?
A template can reveal a bigger operating problem.
If feedback conversations keep revealing unclear roles, measures or management standards, we can help build the system behind consistent performance.
Contact us when one costly workflow or team bottleneck needs diagnosis, build support and adoption.
Get implementation support Use another toolkit