Run a Friday Reflection

Each Friday, review what you accomplished, what you learned, and what you would do differently.

Why it works

Reflection closes the iterative loop that makes improvement possible. Without structured review, each week’s lessons — what worked, what blocked, what should change — evaporate by Monday. Friday Reflection internalizes those lessons in real time, so the next Monday Vision is informed by actual experience rather than hopeful repetition of the same plan.

How to do it

1. Set aside 15–20 minutes on Friday to review the week’s three outcomes: which were achieved, which were not?
2. For each unachieved outcome, write one honest sentence on why.
3. Write one or two things you learned this week about how you work or what matters.
4. Note one specific change you will make next week as a result.

Evidence

Reflective practice is supported by learning-from-experience research: deliberate review of recent performance improves subsequent performance more than experience alone. The Friday cadence mirrors agile retrospectives, which are used in software teams specifically because reflection accelerates learning. (observational)

The evidence is for structured reflection generally; the specific Friday timing and outcome-review format are practitioner design choices, not independently studied.

Sources

• Ellis & Davidi (2005), after-event reviews, Journal of Applied Psychology (structured reflection improves subsequent performance)

Common mistake

Turning Friday Reflection into a guilt inventory ("I didn’t finish X, Y, Z") rather than a learning exercise, which produces demotivation rather than insight.