Marcus Andrey Study
Ler em português Library

Framework · Presence & career · 2 min read

Leadership log

Five minutes every Friday to write 3 wins, one leadership moment, where you held back, next week's proposal and what you learned, so slow leadership impact becomes visible.

3Wins

Three things that went well this week. Small wins count.

"What moved forward?"
1Leadership moment

Feedback given, a decision influenced, someone helped.

"Where did I lead this week?"
1Held back

Where you stayed quiet or avoided something, and what you'll do next time.

"What would I do differently?"
1Proposal

One proactive proposal you will make next week.

"What will I propose?"
1Learned

One thing you learned about leading or the organisation.

"What do I know now?"

5 minutes every Friday → reviews, promotion cases, stakeholder updates

Five prompts for a weekly leadership log that makes slow leadership impact visible.

Use it when

  • You feel unproductive because your work no longer shows up in design files.
  • A performance review, promotion case or stakeholder update is coming and you can't remember what you did in spring.
  • You are working on presence or confidence and want to see your own progress.

How to use it

  1. Block 5 minutes every Friday. Put a recurring slot in your calendar and keep the log in one place, such as a single doc with the newest week on top. Output: a recurring habit and one log file.
  2. Write 3 wins. Small is fine: a decision unblocked, a good critique, a designer who presented on their own. Output: three short lines.
  3. Write one leadership moment. Feedback you gave, a decision you influenced, someone you helped. Output: one specific moment.
  4. Write where you held back, and one proposal. Note where you stayed quiet or avoided something, and what you will do next time. Then write one proactive proposal for next week. Output: one honest line and one proposal.
  5. Write what you learned, then use the log. Add one learning. Re-read the log before big moments: reviews, promotion conversations, hard meetings. Turn the best entries into STAR stories. Output: a growing record that feeds reviews, promotion cases and stakeholder updates.

Worked example

A UX lead on an internal operations platform with 6 product teams writes this on a Friday.

Prompt Entry
Wins (3) Intake board went live; two domains used it in the first week. Designer 2 ran critique alone for the first time. Got agreement on one table pattern.
Leadership moment Gave a designer direct feedback on unclear handoff notes, with an example and a next step.
Where I held back Didn't challenge a deadline in the planning meeting. Next time: ask "what happens if this moves two weeks?"
Proposal for next week Propose a shared Definition of Done to the frontend lead.
Learned Product managers use intake more when they can see the queue.

Six months later, the "table pattern" and "Designer 2 ran critique" entries become two STAR stories in her promotion case.

Watch out for

  • Skipping quiet weeks. The weeks that feel empty are the ones you most need to record. Even small wins count.
  • Only the team's wins. Also write your own part, or you won't be able to tell your story later.
  • Never re-reading it. The log only helps if you use it before reviews and big conversations.
  • Making it long. If it takes 30 minutes, you will stop. Five minutes, short lines.

Template

Copy this into one doc and add a new block every Friday.

## Week of YYYY-MM-DD
Wins (3):
-
Leadership moment (feedback given, decision influenced, someone helped):
-
Where I held back, and what I'll do next time:
-
One proactive proposal for next week:
-
Learned:
-
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close