Event
What happened, when, where, and with whom? Record direct evidence before interpretation.
Resource Hub · Iterative Learning Module
Reflection and Pivot Log
Capture what happened, how the team’s interpretation changed, and what should continue, adapt, reframe, pause, or stop.
Entries stay in the Brief working canvas when you change views. Use short, labeled notes or a partner to capture ideas. Print before leaving; reloading clears entries.
Complete meeting sequence
Brief working canvas
Reflection and Pivot Log
Purpose: Capture a learning moment and choose the smallest responsible adjustment with evidence and accountability.
Use this when: A test, interaction, surprise, stalled period, or changed condition may alter the team’s thinking.
Scope: One-event log. The Full guide retains the separate pattern review across several logs.
Start with: One consequential event, direct notes, current assumption, and relevant participants; use de-identified records.
Time: 15–20 minutes for a recurring event review; the steps allocate 15. Reviewing patterns across several logs takes a separate 20–30 minutes. These are planning estimates; allow additional processing and participation time.
Participation: Think individually before discussion. Use bullets, a labeled diagram, or spoken ideas captured and checked by a partner. You may pass and return. Keep the required information and reasoning visible in your chosen format.
1. Pause and record the event
3 minutesWrite independently: what happened, when and where, decision or learning need, who participated or was affected, and whose account is absent.
Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.
Include: Date / event / context / people · Decision / learning question · Direct heard / observed / measured evidence / source · Missing perspective
2. Update meaning and assumptions
4 minutesCompare what strengthened, contradicted, or unsettled thinking; distinguish interpretation from direct evidence and retain an alternative. Note variation by role or setting and the organizational cue or support implicated.
Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.
Include: Interpretation / alternative / limits · Confirmation / contradiction / surprise · Assumption or causal link changed · Difference / context / condition / uncertain link · New question / missing evidence
3. Check consequence and repair
3 minutesRecord benefits or agency, burden and exclusion, hidden work, changed access or risk, unintended effects, and who should help interpret before deciding.
Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.
Include: Benefit / agency · Burden / hidden work / risk / exclusion · Access or participation changed · Repair / immediate response · Who should interpret / support required
4. Choose the pivot level and assign
5 minutesChoose continue/monitor, adapt delivery, revise an assumption, reframe, change ownership/support, or pause/stop. Explain evidence, what remains stable, commitments to handle, and the next learning move.
Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.
Include: Decision / evidence / rationale · What remains stable / commitments to handle · Action / owner / date · Partner / authority / support / communication · Evidence next / tool to update · Review date / participants
Done when
Event, meaning, consequence, and decision remain distinct; dissent, limits and harm response are recorded; a proportionate pivot updates the relevant plan with ownership and review.
One next move
When several logs or a consequential decision need synthesis, use the Evidence-to-Decision Canvas.
This retains the reflective, sensemaking, and developmental-learning log and the Collaboratory’s privacy and handoff extensions. The brief is a Collaboratory presentation adaptation of this tool; its established sources and local contributions remain attributed in Optional support. CAST UDL Guidelines 3.0 informs the navigation and participation supports.
Complete instructions and working materials
Full guide
Reflection and Pivot Log
Work through the visible activity below. Use the Brief working canvas tab to enter or revisit your notes.
Plan the chosen activity, preparation, fieldwork, and review separately. The brief gives revised meeting estimates; allow more time to complete the full working materials or resolve missing evidence and commitments.
A lightweight learning record
Keep sensemaking visible between major decisions.
Teams need a short way to record surprises, stalled movement, test results, responses across roles, and changing conditions before those details disappear or become a simplified success story.
Use this log between larger Evidence-to-Decision reviews. Use the log after individual events and milestones; use the larger canvas when several sources must be synthesized for a consequential decision.
Four logging moves
Event → Meaning → Consequence → Decision
Keep observation and interpretation adjacent but distinct. A concise record should show how the team moved from evidence to action.
Sensemaking
What might it mean? How did perspectives differ? What assumption was strengthened, weakened, or unsettled?
Consequence
Who benefited, participated, encountered burden, or remained missing? What changed in risk or feasibility?
Decision
What will continue, adapt, reframe, pause, stop, or move to a larger evidence review—and who owns it?
The current direction remains appropriate; capture an indicator or unanswered question.
Change timing, format, language, access, roles, sequence, or operational detail while preserving the core assumption.
The intended mechanism, response from affected people or implementation partners, necessary condition, or theory of change needs updating.
Evidence suggests the team is addressing the wrong condition, population, scale, or material barrier.
Authority, workload, partnership, infrastructure, coaching, or resources must shift before continuing.
Evidence, harm, burden, low value, loss of consent, or changed context makes continuation inappropriate.
Cultures of Growth facilitation check
Read the cues participants receive
Use the check when a difficult result, mistake, feedback exchange, or another team’s success shapes the reflection. Document the organizational cue and the support required for the next learning move.
- DevelopmentAre participants being asked to prove competence or supported in developing it?
- DifficultyCan difficulty and uncertainty be discussed without status loss?
- FeedbackIs feedback specific, reciprocal, actionable, and connected to support?
- LearningAre mistakes and unsuccessful tests documented as sources of learning?
- SharingAre effective practices shared, adapted, and credited?
- SupportDo expectations for growth come with adequate time, strategies, mentoring, resources, and institutional support?
Examine organizational messages, practices, resources, and responses to difficulty. Keep the focus on the culture surrounding participants and the support available to them.
15-minute reflection cycle
Pause → Compare → Update → Decide
Begin with silent notes so everyone can think before the first speaker or highest-status participant shapes the interpretation.
2 min
Pause individually
Record the event and immediate observation before the group settles on one interpretation.
3 min
Compare evidence
Share what was heard, observed, or measured and note differences in position or access.
3 min
Update meaning
Identify what changed in the team’s understanding, assumption, or confidence.
2 min
Check consequence
Examine participation, burden, benefit, risk, and missing perspectives.
3 min
Choose the pivot level
Make the smallest revision proportionate to the evidence—or escalate to fuller review.
2 min
Assign and schedule
Name the next action, owner, communication need, evidence to gather, and review date.
Participant canvas
Reflection and Pivot Log
Use one log for each consequential moment. Review several logs together when patterns begin to accumulate.
Context
Identify the learning moment
Date, milestone, test, interaction, or change
Decision or learning question connected to it
Who participated or was affected
Whose perspective is absent from this log
Record
Separate evidence from meaning
What happened, was heard, or was observedSource and contextPossible interpretationAlternative explanationConfidence or limitation
Update
Name what changed in the team’s understanding
What confirmed or strengthened our understanding
What surprised, contradicted, or weakened it
Assumption or causal link to update
Question that became more important
Difference across roles, groups, or settings
Evidence or perspective still needed
Consequence
Check benefit, burden, participation, and risk
Who benefited or gained agency
Who encountered burden, delay, exclusion, or risk
Hidden labor or workaround revealed
Access or participation condition that changed
Unintended effect requiring response or repair
Who should interpret this with us before deciding
Pivot
Select the smallest responsible adjustment
Continue and monitorThe current direction remains appropriate; capture an indicator or unanswered question.
Adapt deliveryChange timing, format, language, access, roles, sequence, or operational detail while preserving the core assumption.
Revise an assumptionThe intended mechanism, response from affected people or implementation partners, necessary condition, or theory of change needs updating.
Reframe the challengeEvidence suggests the team is addressing the wrong condition, population, scale, or material barrier.
Change ownership or supportAuthority, workload, partnership, infrastructure, coaching, or resources must shift before continuing.
Pause or stopEvidence, harm, burden, low value, loss of consent, or changed context makes continuation inappropriate.
Decision and evidence supporting it
What stays stable while we adjust
Act and carry forward
Assign the next move and preserve the learning
Next action, owner, and date
Partner, authorization, or support needed
Who should hear what changed—and how
Evidence to gather next
Tool or plan that must be updated
Review date and decision participants
Handoff: Update the Theory of Change, Success Indicators, Frictions Scan, or Sustainability Map when the log changes an assumption, scope, indicator, risk, owner, or support condition. Use Evidence-to-Decision to decide the next move when the choice is consequential.
Pattern review
Review several logs across time
Pattern repeated across logs
Difference by role, group, setting, or time
Pivot that improved learning or access
Issue repeatedly deferred or normalized
Support or structural condition now visible
Larger decision required
Before turning reflection into a pivot, escalation, pause, or stop decision
Experience, Conditions, and Power Thread
Carry situated evidence into the next decision.
1Relevant conditionSelect only what is genuinely connected to this decision.
2People, role, and contextLocate whose experience is being considered and where it occurs.
3Institutional cue or structureName the practice, message, relationship, resource, rule, or expectation shaping it.
4Evidence and differencesRecord direct evidence, variation across groups or settings, and what remains uncertain.
5Implication for the next decisionState what this evidence means for continuing, revising, inquiring, pausing, or stopping.
- Select only the Conditions for Thriving that are genuinely relevant.
- Do not infer another group’s experience without direct or appropriately situated evidence.
Learning, privacy, and power
Document enough to learn while limiting exposure.
A useful record preserves evidence and accountability. Keep participant details to the minimum required for the learning decision, and use direct conversation and repair when needed.
Keep the log focused on learning.Use the tool for team learning decisions and keep individual compliance, gossip, and personnel matters outside it. Record only what the learning decision requires.
Write for the appropriate audience.Avoid unnecessary names, health information, protected data, or identifiable quotations. Clarify storage, access, retention, and sharing.
Preserve disagreement in reflection.Record consequential differences and who holds them. A single team summary can hide role, status, or experience-based variation.
Match the pivot to the evidence.A single account can reveal a real experience; a pattern requires broader evidence. Match the decision to the strength and relevance of the evidence.
Respond to harm directly.When a test creates avoidable burden or risk, respond and repair. Treat participant harm as a reason to respond, repair, and reconsider the work.
Stopping is a legitimate decision.Base continuation on current evidence and responsibility. Document how obligations and communication will be handled when the work ends.
How this tool connects
Carry the work forward.
Use these handoffs flexibly. New evidence may send a team back to an earlier tool.
Return to this tool
after each test, consequential interaction, milestone, surprise, or stalled period.
Optional support
Preparation, pacing, and participationPrepare the starting information and access supports; allow time for the activity and its follow-through.
One consequential event, direct notes, current assumption, and relevant participants; use de-identified records.
15–20 minutes for a recurring event review; the steps allocate 15. Reviewing patterns across several logs takes a separate 20–30 minutes.
Share purpose and prompts in advance when possible. Offer private preparation, accessible formats, and a recorder or partner. Plan how outputs will be returned, stored, and reviewed.
Worked examples and applicationsUse illustrations to understand the prompts, then return to your own context and evidence.
Generic example
Learning from a scheduling test
This composite example was created for illustration and draws on no specific Collaboratory team or prototype.
EventA limited evening appointment test was used less than expected, but follow-up conversations showed that several participants learned about it after the available dates.
MeaningThe result weakens the assumption that low use demonstrates low demand. Awareness timing and transportation remain alternative explanations.
PivotThe team adapts delivery and retests with earlier notice, phone access, and transportation questions while keeping the core learning question stable.
BoundaryThe team reserves permanent staffing decisions for a broader evidence review. The log moves into a broader evidence review after the second round.
Sources, adaptations, and attributionReview the intellectual foundations, local contributions, and suggested citation.
Source and attribution
Reflective practice, organizational sensemaking, and developmental learning
This log combines recurring moves from reflective practice, after-action review, organizational sensemaking, and developmental evaluation: notice events, compare interpretations, update assumptions, act, and continue learning as conditions change.
The Resource Hub contributed this synthesis, its equity and privacy safeguards, and the handoff structure. Reflection and iterative-learning methods come from established traditions. The log was created after the documented 2025 sequence, and private participant material remains outside it.
Authorship, foundations, and suggested citation
Synthesized and developed by Jessica A. Leveto, Ph.D.
Intellectual foundations: Reflective practice, organizational sensemaking, after-action review, developmental evaluation, and iterative learning.
Suggested citation: Leveto, Jessica A. 2026. “Reflection and Pivot Log.” Sensemaking Collaboratory Resource Library. https://sensemakingcollaboratory.org/resources/tools/reflection-pivot-log.