Engineering Manager Notes on iPhone: Capturing the Context Behind Every Decision

Engineering management is one of the most note-intensive jobs that generates the fewest notes. You spend most of your day in conversations — 1:1s, sprint planning, architecture debates, incident reviews — but you're rarely at a desk with a keyboard when the important things are said.

The result: institutional memory lives in your head, decays over time, and vanishes when you transition teams or get promoted.

Voice notes fix this. Specifically, Nemos on iPhone gives engineering managers a way to capture the context behind decisions — not just the decisions themselves — without breaking conversational flow.

What Engineering Managers Actually Need to Remember

Not everything deserves a note. The things that do:

People context: what's going on with each direct report — motivations, frustrations, growth edges, blockers, things said off-the-record. This context is what makes you a good manager. Lose it and you're starting from zero every 1:1.

Decision rationale: why was this architectural decision made? Why did we choose vendor X over vendor Y? Why did we staff this team this way? The what is in your wiki. The why disappears.

Commitments made: what did you promise in that planning meeting? What did your manager ask you to follow up on? What did you say you'd investigate? These live in your head until a meeting two weeks later reveals you forgot.

Escalation history: what happened leading up to the incident? What conversations preceded the performance issue? What context matters for the promotion case? You need this when the stakes are high and your memory is unreliable.

Patterns across 1:1s: is this engineer saying the same thing about team dynamics for the third month running? Have you been promising the same infrastructure investment for six weeks? Patterns only emerge when you have a record.

The Post-Meeting Voice Note Protocol

After every significant meeting — not during, after — walk to a private space and record a 90-second to 3-minute voice note. Don't transcribe the meeting. Capture the parts that won't be in the meeting notes:

What was actually said vs. what was written. Meeting notes capture decisions. They rarely capture the dissent, the hesitation, the "I'll go along with it but I don't love it." Say that.

Your read on the people in the room. Who seemed energized? Who's burning out? Who surprised you? This is the intelligence you need for your 1:1s.

Your own reaction. Were you anxious about something? Did a concern surface that you didn't voice in the meeting? Say it now before the meeting's social context suppresses your honest assessment.

What needs to happen next. Not the formal action items — those are in the meeting notes. Your action items. The things you're personally tracking.

A 2-minute voice note after a 45-minute planning meeting is a 4% time investment that doubles the durability of everything learned.

1:1 Voice Note System

Your 1:1s are your most important meetings. They deserve the most deliberate note-taking.

Before the 1:1 (2 min): Record a brief note the day before. What do you want to cover? What did they mention last time that you want to follow up on? What's the thing you've been meaning to bring up but keep deprioritizing? Speaking it out loud forces you to crystallize it.

After the 1:1 (3-5 min): Record a more detailed note covering: - What they said about their work, team, and wellbeing - Any tension, frustration, or enthusiasm that came through - What you committed to - What you're worried about (even if you didn't say it) - What the theme of this conversation was relative to recent ones

Over 4-6 weeks, these recordings give you something better than perfect memory — a searchable record of the arc of each person's experience on the team.

When it matters most: Before a performance review, a promotion case, or a difficult conversation, listen back to 3-4 months of 1:1 notes. The pattern that emerges is almost always clearer than anything you could reconstruct from memory.

Incident and Postmortem Voice Notes

Incidents are the worst time to take good notes and the highest-stakes situation where notes matter later.

During an incident, don't take notes — focus on resolution. But immediately after — even before the Slack thread is fully resolved — record a voice note while the experience is fresh:

• What you were doing when you first heard about it
• Your initial read on severity and cause
• Who you looped in and why
• The timeline as you experienced it
• Any near-misses or judgment calls that won't make it into the postmortem
• What you wish you'd had in place

This raw incident note is different from the polished postmortem. It captures your actual experience, including the uncertainty and the decisions made under pressure. It's invaluable for root cause analysis and for your own learning.

Architecture Decision Notes

Engineering managers often sit in or facilitate architecture discussions but rarely generate the artifact that captures the decision context. Voice notes fill this gap.

After any significant architecture conversation, record: - The core options that were on the table - The strongest arguments for each - The deciding factors - What was explicitly ruled out and why - Who owns the decision

This is the "Architecture Decision Record" (ADR) as a voice note — fast to create, honest about the actual decision process, and searchable months later when someone asks "why didn't we use X?"

Nemos Features That Matter for Engineering Managers

Transcription: spoken notes become searchable text. When you're preparing for a promotion conversation and need to find everything you captured about that engineer's work over the past year, search works.

Voice-first capture: no typing in meetings, no visible note-taking that changes conversational dynamics. Capture happens after, in private, without friction.

Organization by topic or person: tag notes by name or project. Six months of 1:1 notes for a specific direct report become retrievable as a cohesive set.

iOS integration: notes you capture in a 5-minute walk between meetings sync instantly. Nothing falls through the gap between "important conversation" and "I should write that down."

Comparison: Voice Notes vs. Written Notes for Engineering Managers

The Promotion Case Problem

The most painful moment in engineering management: sitting down to write a promotion case and realizing you can reconstruct the outputs but not the growth.

"She took on the on-call rotation" is in the ticket system. "She started proactively flagging edge cases that used to require prompting — that shift happened in February" is not in any system unless you captured it.

Voice notes build the evidence base for promotion cases as a byproduct of good management. If you've been capturing 1:1 notes, incident notes, and project observations over 6-12 months, writing a promotion case becomes assembly, not reconstruction.

Getting Started: First Week

Day 1: After your first 1:1, record a 3-minute voice note about the conversation. Don't over-structure — just speak honestly about what was said, what you noticed, and what you're going to follow up on.

Day 3: After your next planning or architecture meeting, record a 90-second note capturing the decisions and the context behind them.

Day 5: Before the week ends, record a brief weekly summary — what moved, what's stuck, what needs your attention next week.

After two weeks, you'll have a lightweight record of your management context that took less than 20 minutes total to create. After a month, the pattern value starts to emerge.

FAQ

Should I tell my direct reports I'm taking voice notes after 1:1s? You don't need to announce it, but you're not hiding anything. You're capturing meeting notes — the same thing you'd do in written form. If you work in a context with strong privacy norms, a brief mention ("I take notes after our 1:1s to track commitments and context") is a good practice.

What about performance management — is it okay to keep voice notes about performance issues? Yes. Voice notes for your own planning and recall are private work notes — not official HR records. Maintain any required documentation in your company's official systems. Your voice notes are your thinking tool, not the HR file.

How do I organize notes for 12 direct reports without them getting chaotic? Use a simple naming convention: "[name] 1:1 [date]" for post-1:1 notes. Nemos search makes retrieval reliable even without perfect organization.

What's the minimum viable version of this system? One voice note after every 1:1. That's it. If you do nothing else, post-1:1 capture gives you the most leverage for the least effort.

How do I use older notes without spending hours reviewing them? Before significant conversations (performance reviews, promotion cases, escalations), do a 10-minute review of notes from the past 3-4 months. The pattern that matters will surface quickly.

Related Reading

• Work Journal iPhone App for Professionals
• Meeting Notes App iPhone: Capture Decisions That Actually Matter
• Daily Planning with iPhone Voice Notes
• Using iPhone Notes as a Habit Tracking Journal

Sources

• Will Larson, *An Elegant Puzzle*, 2019 — engineering management systems and 1:1 best practices
• Michael Lopp (Rands), *Managing Humans*, 2016 — people management context and judgment
• Google re:Work, "Manager Research" — evidence base for high-impact management behaviors
• Michael Nygard, "Documenting Architecture Decisions" (cognitect.com), 2011 — ADR methodology