People management is a writing-heavy job that nobody warns you about. One-on-ones, feedback, status updates, alignment docs. All words.
You're an engineering manager with 8 direct reports. You spend half your day in 1:1s and the other half writing about what happened in them.
You have four back-to-back 1:1s starting in thirty minutes. You open Notion and scan last week's notes for each person. Two of them have action items you need to follow up on, one has a career growth conversation you promised to continue, and one just joined three weeks ago and you're still learning what motivates them. You hold the hotkey and talk through your notes for each meeting. "For Priya, follow up on the oncall rotation concern. For James, check in on the tech lead track conversation we started." Thirty seconds per person instead of typing bullet points into four different docs.
You're on your second 1:1 and Priya just told you she's frustrated with the oncall rotation being unfair. This is the kind of thing you need to write down with nuance, not just "oncall bad." You have Google Docs open next to the call. You hold the hotkey and quietly narrate what matters. "Priya feels the oncall burden is falling disproportionately on her and two other senior engineers. She wants a formal rotation policy. She's not upset but she's been sitting on this for a month." You just captured the context, the emotion, and the ask in ten seconds. Typing that mid-conversation would have meant missing what she said next.
"Priya feels the oncall burden is falling disproportionately on her and two other senior engineers. She wants a formal rotation policy. She's not upset but she's been sitting on this for a month. Action item: draft a fair oncall schedule by next Friday and share with the team."
Priya feels the oncall burden is falling disproportionately on her and two other senior engineers. She wants a formal rotation policy. She's not upset but she's been sitting on this for a month. Action item: draft a fair oncall schedule by next Friday and share with the team.
Review cycle is open in Lattice and you owe feedback for three people by end of week. This is the part of management that eats entire evenings. You know what you want to say about James, you just hate the process of turning it into polished paragraphs. So you talk instead. You hold the hotkey and speak like you're explaining James's performance to a peer. The words come out natural and specific. You dictate the whole review in about three minutes of speaking, then spend five minutes editing for tone. That's one down. Two more tomorrow.
"James has grown significantly this quarter. He led the migration to the new auth service with minimal guidance and handled the production incident on March 3rd with clear communication to stakeholders. His area for growth is delegating more to junior engineers instead of picking up their tasks himself. I'd recommend him for the senior track and want to discuss timeline in our next calibration."
James has grown significantly this quarter. He led the migration to the new auth service with minimal guidance and handled the production incident on March 3rd with clear communication to stakeholders. His area for growth is delegating more to junior engineers instead of picking up their tasks himself. I'd recommend him for the senior track and want to discuss timeline in our next calibration.
Your director wants a weekly update by noon every Tuesday. It needs to cover what shipped, what's at risk, and what you need from her. You used to spend twenty minutes crafting this email, carefully choosing words so nothing sounds alarming but nothing gets buried either. Now you hold the hotkey and talk through it like you're giving a verbal update in a hallway. "We shipped the notification preferences page on Monday. The payments integration is a week behind because of the third-party API issues I flagged last week. I need a decision on whether to extend the timeline or cut scope on the admin dashboard." Two minutes of speaking. Five minutes of light editing. Send.
Two engineers on your team disagree about an architectural decision and it's spilling into a Slack thread that's getting tense. You need to step in, but the way you write this matters. Too casual and it gets ignored. Too formal and it escalates. You hold the hotkey and speak the way you would in person, measured but direct. "I've read through the thread and I think you're both making valid points. Let's not resolve this in Slack. I'm going to set up a thirty-minute design review for Thursday where we can look at both approaches side by side with the tradeoffs written out. Alex, can you prep a one-page summary of Option A? Riya, same for Option B." You read it back, adjust one sentence, and send. The thread calms down.
You're putting together a promotion packet for Priya. This is the document that will determine whether she gets promoted, and it needs to be thorough. Impact, scope, examples, peer feedback, growth trajectory. Normally this takes you an entire afternoon of staring at a Google Doc. Instead you open the template and start dictating section by section. You talk through her impact on the platform reliability project. You talk through the mentorship she's done. You talk through the specific metrics. Fifteen minutes of speaking gives you a solid first draft that would have taken two hours to type from scratch. You'll polish it tomorrow with fresh eyes.
Every Friday you post a team update in the engineering Slack channel. What your team shipped, what's coming next week, and any shoutouts. Your team does good work and you want to make sure people outside the team know about it. You hold the hotkey and run through the highlights. "This week the team shipped notification preferences, closed 14 bugs from the backlog sprint, and started the payments integration. Next week we're focused on the admin dashboard and the API rate limiting work. Shoutout to James for handling the Wednesday incident response and to Riya for shipping the preferences page solo." Paste it into Slack, add a few line breaks, done.
Don't wait until end of day. The moment the call ends, hold the hotkey and spend thirty seconds capturing what matters. The details are sharpest in the first minute.
You know what you want to say about each person. The bottleneck is turning it into written paragraphs. Just say it out loud like you're explaining it to a peer. Edit after.
Your leadership update doesn't need to be literary. Talk through what shipped, what's at risk, and what you need. Two minutes of speaking, five minutes of editing, done.