Daily Reflection Journal

A director at a mid-size tech company returns from six months of parental leave to find her team restructured, her peer group changed, and her own professional identity feeling slightly foreign. She says she used to know who she was at work, and now she is not sure that person exists anymore. She has been back for three weeks and is still waiting to feel like herself again.

Frame this as a re-entry tool, not a journaling practice. 'You're describing a gap between who you were before leave and who you're finding now - let's use this to start collecting data on what's actually there.' The three prompts - today's intention, today's stressor, what you want - function as a daily calibration. The stressor field is particularly useful here: it externalizes the noise so she can see it rather than swim in it. Clients returning from extended leave often resist any tool that looks like self-help. Present this as intelligence gathering.

Watch the stressor field across multiple days. If the same item appears repeatedly with no variation in how it is described, she is recording not processing - the stressor has become a complaint. If the 'what I want' field stays vague (peace, balance, to feel normal) week after week, she has not yet located what she is actually missing. The intention field is diagnostic too: if she writes task-based intentions every day (send the report, prep for the meeting) rather than anything relational or identity-based, the re-entry problem is deeper than adjustment.

Start with the stressor column. 'What keeps appearing here?' - the frequency tells you more than any single entry. Then move to 'what I want': look for distance between what she writes on Monday versus Friday of the same week. If the want shifts across the week, she is still locating herself. If it stays identical, it may be a surface-level answer. The question that tends to open this up: 'What would it mean to feel like yourself again at work - what would be different?' Then let her answer against what she has been writing.

A principal engineer promoted to engineering manager eight months ago still spends most of his days in the code. His team has noticed he reviews PRs at the line-by-line level and jumps into technical decisions that are nominally his reports' to make. He frames this as 'helping' and says the team moves faster when he is in the work. His skip-level flagged the behavior.

Frame this as a decision log, not a feelings journal. 'Each morning you name one intention for the day. Let's make that intention specifically about how you want to show up as a manager - not what you want to accomplish technically. Then at day's end, you'll note your stressor and what you want more of.' The stressor field will likely fill with team and organizational friction rather than technical problems - that shift in language is itself useful data. He may resist the word 'journal'; call it a daily diagnostic.

Watch what he names as the intention. If it stays technical (ship the release, review the architecture doc), he is not yet operating from a manager identity. If stressors are consistently about people (my report didn't communicate clearly, I had to redo what someone else started), he may be generating the friction through over-involvement. If 'what I want' is consistently about technical outcomes rather than team outcomes, the promotion has not registered at the level of identity yet.

Start with intentions versus actuals. 'What did you write here Monday morning, and how did Monday actually go?' The gap between intention and behavior is the coaching conversation. Then look at the stressor column: count how many entries are about the work versus about the people. Ask him to do that count himself - 'what's the ratio?' The question that typically opens the identity piece: 'When the day goes well, what did you do that only a manager could do?'

A founder who has run her company for eleven years has hired a CEO and is transitioning to a board chair role over the next six months. She says intellectually she knows this is the right move. Emotionally she is cycling between relief and something she describes as grief. She does not have language for what she is losing, which makes it hard to talk about.

Frame this as a documentation practice, not a processing exercise. 'Six months from now you'll want a record of what this period actually felt like - not a curated version. This tool gives you that.' The three fields - intention, stressor, what I want - create a longitudinal record without requiring her to be analytical about it in real time. The stressor field will surface what she is mourning as operations are handed off. Some founders resist anything that looks emotionally oriented; the daily brevity (five minutes) removes that barrier.

Watch the 'what I want' field for specificity versus vagueness. If she is writing 'I want to trust him' or 'I want to let go' week after week with no change in the phrasing, she has a wish but not a target. Watch the stressor field for a pattern: if stressors are consistently about things the new CEO is doing differently, she may be experiencing competence anxiety (he is doing it wrong) when the real issue is loss of identity (I am no longer the one doing it). The shift from 'he made a bad call' to 'I wasn't involved' is significant.

Start with changes across time. 'Look at the stressor column from week one and week four - what's the same and what's different?' The evolution of what stresses her is the story. Then focus on 'what I want': look for entries where what she wants is about influence versus entries where it is about belonging or contribution. Ask: 'What do you want that only board chair can give you - that CEO couldn't have given you?' That question often surfaces what she is actually building toward.