Most engineering managers I know became managers because they wrote good code. Then, somewhere in the first three months of the new role, they realized the job had quietly transformed. The keyboard is still in front of them, but they barely write code anymore. Instead they write 1:1 notes, performance reviews, decision logs, project updates, hiring rubrics, calibration prep, Slack threads, postmortems, and roughly four hundred quick replies a day.
The math gets uncomfortable when you actually count the words. A senior EM with eight reports is producing somewhere between five and ten thousand words a week, mostly in short bursts across a dozen tools. Typing all of that, while also context-switching between meetings every thirty minutes, is what burns people out faster than the meetings themselves.
Voice typing is one of the few productivity upgrades that actually moves the needle for this role, because it attacks the bottleneck that hurts the most: composing the same kinds of structured prose, over and over, in narrow time windows.
Where the Time Actually Goes
Before talking about the fix, it is worth being precise about what an EM is actually doing all day. The writing falls into a few buckets.
- 1:1 notes. Five to ten minutes of writing per direct report per week, sometimes more. Often happens in the awkward five-minute window between meetings.
- Decisions and rationale. Architecture choices, hiring decisions, project go or no-go calls. Each one needs a written record because future-you will not remember why you said yes.
- Performance reviews. Twice a year, two to four pages per direct report, with examples and citations.
- Project status updates. Weekly, pulled together from standups, design reviews, and your own observations.
- Slack and email triage. Continuous. Hundreds of small replies, each one requiring just enough context to be useful.
- Hiring artifacts. Interview debriefs, feedback for candidates, calibration notes for hiring committees.
Two patterns jump out. First, the writing is highly structured but not formal. You are not writing a paper; you are filling in a known shape with the specifics of this week. Second, the writing happens in fragments throughout the day, which means typing speed is not the bottleneck so much as activation cost. Every time you sit down to write a paragraph, there is a setup tax of getting your brain into typing mode.
Why Voice Solves This Better Than Templates
Most EMs try to solve the writing volume problem with templates. Templates help, but they cap out quickly because the value of a 1:1 note is the specific, contextual thinking you bring to it, not the headers. Once you have your bullet structure, the actual content still has to come out of your head and onto the page.
Voice typing changes the activation cost. When you can hold a key, speak two sentences of context, and release, your fragment of thinking is captured before the next meeting starts. The text appears wherever the cursor is, including inside Notion, Linear, Lattice, your performance review tool, your wiki, Slack, or the markdown file in your engineering org's GitHub repo where decisions are logged.
1:1 Notes: The Highest-ROI Use Case
The 1:1 is where voice typing pays off fastest for an EM. The flow looks like this. You finish the meeting at 9:55. Your next meeting is at 10:00. In those five minutes, you used to either write nothing or write a single rushed sentence that you would not be able to interpret a week later.
With voice typing, those same five minutes look different. You hold a hotkey and speak the three things that mattered: the topic the report wanted to discuss, what you committed to follow up on, and the impression you formed about how they are doing. The notes go straight into your 1:1 doc. By 9:58 you are done, and you have two minutes to drink water before the next meeting.
Multiplied across eight directs, this single habit easily saves an EM two hours a week, and the resulting notes are more substantive than what they used to type, not less.
Performance Reviews Without the Weekend
Performance review season is when most EMs lose entire weekends. The work is essentially compositional: you have a year of observations, and you need to weave them into a narrative for each report that touches their wins, their growth areas, and concrete examples.
The bottleneck during review writing is rarely the thinking. You already know what you want to say after spending months working with the person. The bottleneck is the energy required to type three pages, eight times. Voice typing turns that into a much shorter exercise of speaking the narrative aloud, paragraph by paragraph, then editing for tone. A four-hour writing session compresses to under an hour and a half, with a much smaller cognitive tax.
One technique worth trying: open the review form, look at the prompts, then close your eyes for a minute and just speak the answer to a friend in your head. Hold the hotkey and dictate exactly what you would have told that friend. The first draft will be rougher than your usual writing, but it will contain everything that matters. Cleaning it up is easy work compared to generating it.
Decision Logs and ADRs
Architecture Decision Records and decision logs are the other place voice typing shines. These documents have a known shape: context, options considered, decision, consequences. They do not need to be beautiful prose. They need to exist and to be specific enough that someone reading in six months can reconstruct why you made the call.
If you have ever skipped writing an ADR because you did not have the energy to type it after the meeting, voice typing removes that friction. You can dictate the entire ADR while it is still fresh, in less time than the meeting itself took, and your future engineers will thank you.
Setting Up the Mac for This Workflow
The technical setup is simple. Steno runs as a menu bar app on macOS. You hold a hotkey, speak, release, and the text appears at your cursor. There is no separate window, no transcript file, no copy and paste. Because it is system-wide, the same shortcut works in Notion, Linear, Slack, your terminal, your code editor, and your performance review tool.
For an EM, the small details matter. Steno's transcription engine handles technical vocabulary cleanly, including service names, programming language terms, and the kind of cross-functional jargon that fills your week. You can also feed it a short list of teammate names and project names so they get capitalized and spelled correctly the first time.
What Actually Changes After a Month
The interesting effect of voice typing is not just that you save time on writing. It is that you start writing things you used to skip. The 1:1 you used to leave undocumented now has notes. The decision you used to make in your head now has a paragraph in the team wiki. The review feedback you used to delay now lands the same week.
Engineering managers are fundamentally a writing job that pretends to be a coding job. Whichever tool reduces the cost of writing is the tool that lets you do the rest of the work better. You can install Steno from voicekeyboardpro.com, set a hotkey, and have it running before your next 1:1 starts.
The bottleneck for most engineering managers is not thinking. It is the energy required to type the same kinds of structured notes thirty times a week. Voice typing removes that tax.