Run Manager Check-ins and Feedback

Flow · 7 controlled steps

1. 01

   Prepare from current evidence

   Focus the conversation on material work and decisions.

   • — Review the current agreement, prior commitments, outcome and guardrail evidence, exceptions, feedback, and context changes.
   • — Invite the role holder to add topics and evidence.
   • — Separate urgent matters and route them immediately.
   • — Choose the few items that need shared attention or decision.

   Responsible

   Manager and role holder

   Output

   Check-in Agenda

2. 02

   Understand the state of the work

   Build a shared view before evaluating or solving.

   • — Review intended outcomes, progress, quality, flow, learning, exceptions, guardrails, and changed assumptions.
   • — Ask what is working, stuck, surprising, or no longer relevant.
   • — Distinguish observed evidence from interpretation and missing information.
   • — Examine dependencies, process conditions, systems, workload, and manager commitments.

   Responsible

   Manager and role holder

   Output

   Shared Situation Record

   Decision

   Where does the current state require a decision, support, learning, or expectation change?

3. 03

   Exchange specific feedback

   Make useful information available in both directions.

   • — Describe timely observed behavior, work, context, and effect without inventing motive.
   • — Connect feedback to the outcome agreement, operating expectations, customers, or process.
   • — Invite the recipient’s perspective, correction, and intended response.
   • — Ask for feedback on manager behavior, clarity, support, decisions, workload, and surrounding systems.

   Responsible

   Manager and role holder

   Output

   Reciprocal Feedback Record

4. 04

   Decide actions and support

   Convert insight into owned operating change.

   • — Choose what to continue, stop, change, investigate, learn, or escalate.
   • — Agree manager support, resources, access, collaboration, and role-holder actions.
   • — Name owners, timing, evidence, dependencies, and follow-up.
   • — Keep development actions connected to real work and opportunity to practice.

   Responsible

   Manager

   Output

   Check-in Decisions and Commitments

   Decision

   What is the smallest sufficient response within current authority?

5. 05

   Control changes and specialist routing

   Keep the check-in from silently becoming another decision process.

   • — Classify expectation, role, process, resource, development, performance, conduct, safety, quality, accessibility, or employment implications.
   • — Route material outcome changes to outcome alignment and governed concerns to qualified client processes.
   • — Document only the minimum necessary information and restrict access appropriately.
   • — Do not promise a rating, reward, promotion, corrective outcome, or employment action.

   Responsible

   Manager

   Output

   Controlled Handoff

   Decision

   Which authoritative process and owner must accept this matter?

6. 06

   Record proportionately and follow through

   Preserve continuity and accountability without turning dialogue into surveillance.

   • — Record agreed evidence, feedback themes, decisions, commitments, owners, due points, and routed matters.
   • — Allow correction of factual errors and visible disagreement.
   • — Complete support and action commitments between meetings.
   • — Surface overdue or blocked items before the next cadence.

   Responsible

   Manager

   Output

   Check-in Record · Updated Action Record

7. 07

   Review patterns and improve

   Use accumulated conversations to improve work, management, and connected processes.

   • — Review outcomes, feedback, completed support, recurring obstacles, expectation changes, and guardrails over time.
   • — Identify process, manager, role, resource, capability, or system patterns without converting anecdotes into unsupported conclusions.
   • — Route improvements and prepare an evidence summary for the appropriate formal process.
   • — Adjust cadence or check-in design when it no longer serves the work.

   Responsible

   Manager

   Output

   Check-in Pattern Review · Formal Process Evidence Summary

   Decision

   What does the accumulated evidence justify changing?

Connections

Seams · 13 hops within 2 steps

Upstream and downstream neighbourhood over public reference processes only. Each hop shows the trigger, carried objects, and what the receiving process loses if the producing step is skipped.

Roles

Systems + Data

Measures

Evidence + judgment

Draft reference standard. Requires client context and qualified employment, labor, accessibility, privacy, safety, quality, ethics, regulatory, and jurisdiction-specific review before deployment.