Weekly reflection for managers
A weekly reflection is a short, deliberate look back across your whole team rather than one person at a time. It is the one part of the week that is about your own leadership rather than anyone else's work: who you have not really spoken to in a month, which commitments keep sliding, whether the same problem is showing up in three places, and where your attention actually went as opposed to where you assumed. Emily assembles the week's material so it is a read-and-decide exercise rather than a research project.
What is a weekly reflection for a manager?
A short recurring review: ten to fifteen minutes: where you look at your team as a whole instead of as a series of individual conversations.
The unit of management is usually the 1:1, which is good for depth and bad for pattern recognition. A weekly pass over everything at once is what surfaces the cross-cutting stuff: three people mentioning the same blocker, a person who has quietly dropped off your calendar, a commitment you have now carried for a month.
Why does this matter for your own development as a manager?
Because it is the only place in a manager's week where the subject is how you are leading rather than how the work is going, and you cannot improve at something you never look at.
Almost all management advice assumes you can see your own patterns. You mostly cannot, from inside a week made of thirty meetings. You will remember the conversations that went badly and forget the person you have been avoiding; you will believe your attention was evenly spread when it went overwhelmingly to whoever was loudest. A weekly pass over what actually happened is the correction.
The useful output is never a verdict. It is a fact and a prompt: you have not had a real conversation with Sam in three weeks; three people raised the same blocker; you have carried this commitment since April. What that means, and what to do about it, is yours, but you cannot decide anything about a pattern you never saw.
What should you look at in a weekly review?
Coverage, commitments, and changes. Coverage means who you have and have not spoken to. Commitments means what is still open. Changes means what is different from last week.
Resist turning it into planning. The reflection is for noticing; the deciding it prompts belongs in your calendar for next week. Managers who merge the two end up doing neither, because planning always expands to fill the slot.
- Who have I not had a real conversation with recently?
- What did I commit to that is still open?
- What changed for someone this week that I should follow up on?
- Is the same issue showing up with more than one person?
- What did I say I would change last week: did I?
How does Emily support a weekly reflection?
Emily produces a weekly reflection from the context she gathered during the week, the meetings that happened, the notes you captured, and the follow-ups still open, so you are reviewing an assembled picture rather than reconstructing one. Previous reflections are kept, so a week can be read against the ones before it rather than in isolation.
For Pro, Emily adds a layer on top: how your attention has been distributed across your team, which relationships have momentum and which have gone quiet, and what has been consistently slipping. Over a few months that turns individual weeks into something you can actually learn from.
None of it is scored. Emily does not rate your week, grade your leadership, or tell you whether you are doing well: she shows you what happened and trusts you to know what it means.
When is the best time to do it?
Whenever you will actually do it, but the two defensible slots are late Friday and early Monday.
Friday captures the week while it is still vivid and lets you close it out mentally. Monday is better if Fridays reliably collapse, and it feeds directly into the week you are about to plan. The wrong answer is "when I have time," which resolves to never.