In a skip-level meeting you should write down four things, dated and specific: themes about how the team is actually working, blockers the person cannot fix from where they sit, signals about their manager and their own growth, and anything you explicitly committed to follow up on. Write what you heard, not your interpretation of it, and note who said it, not to build a file on anyone, but so that two weeks later you can notice the third person to raise the same concern. The single most useful move is to keep these notes per person, because the value of skip-levels is not any one conversation; it is the pattern you only see by reading across several of them.
That is the part most managers of managers get wrong. They run good skip-levels and then keep the takeaways in their head, where the vivid complaint from this morning crowds out the quieter concern three people mentioned last month. Memory is a terrible aggregator. A dated, per-person note is not bureaucracy; it is the only way the third mention of a blocker ever registers as a pattern instead of disappearing into the noise.
What to capture in a skip-level
You do not need a script. You need four buckets, kept per person, each entry dated and in the person's own framing rather than yours. Copy the layout below and keep one of these per skip-level conversation.
SKIP-LEVEL - @[Name] - [Date] THEMES (how the team is working; what's recurring) - - BLOCKERS (things they can't fix from where they sit) - - MANAGER + GROWTH SIGNALS (how their manager is doing; where they want to go) - - I COMMITTED TO (the follow-ups I owe; close every one) - - PATTERNS TO WATCH (#topic to read across people later) -
Here is what each bucket looks like once it holds real entries. Specific and dated beats tidy and vague every time, and it is what lets you compare one skip-level to the next.
- Theme. "Mar 9: @Priya says planning meetings run long and nothing gets decided; estimates feel like commitments. Third person this month to say it." A theme is a way of working, not a single event, and the date stamp is what turns three of them into a pattern you can act on.
- Blocker. "Mar 9: the staging environment is shared and flaky; costs the team roughly a day a week. They've raised it twice and it stalled." This is the kind of thing a skip-level exists to surface: a fixable problem the person cannot fix from where they sit.
- Manager & growth signal. "Mar 9: speaks well of @Dan's support; wants a clearer path to tech-lead and isn't sure what's expected. Worth nudging Dan to make the bar explicit." Note both how their manager is doing and where the person wants to go, framed as something to help with.
- I committed to. "Mar 9: said I'd find out whether the staging budget is approved and report back by next Friday." If you write down nothing else, write this. Nothing erodes a skip-level faster than a follow-up the person never hears about again.
See what a private, per-person log looks like across a whole org.
Reading across people: where the value actually is
A single skip-level tells you how one person feels on one day. That is useful, but it is not why you run them. The reason a manager of managers does this is to see what no single 1:1 reveals: the same blocker mentioned by three different teams, the manager whose reports all light up about growth except on one specific topic, the concern that keeps surfacing two levels down and never makes it up. You cannot hold six conversations in your head and reliably notice the third person to say the same thing. You need them written down, dated, and readable side by side.
This is exactly what per-person plus per-topic organization gives you. Tag each note with the person, and tag the recurring concern with a topic. Then, before you decide anything, read across the topic instead of across the week. When "estimates feel like commitments" shows up from @Priya on Mar 9, from @Marco on Mar 14, and from @Lena on Mar 20, that is not three grumbles; it is a planning problem, and the three dates are the evidence that it is real and not just the loudest voice this morning. Patterns you can defend with dates are the ones a manager will actually act on.
The same reading-across protects you from the opposite error. One person's strong opinion can feel like a crisis in the room. When you check it against the other five skip-levels and no one else has raised it, you have learned something too: it is one person's experience, worth following up on directly, not a team-wide fire to escalate.
Notice the third mention of the same blocker, instead of forgetting the first two.
Keep skip-level notes private, and frame them fairly
People are candid in a skip-level only if they trust it will not come back with their name on it. That trust is the entire value of the meeting, and your notes are where it is most easily broken. So treat skip-level notes as private to you, keep them framed as behavior and theme rather than verdict, and never write the kind of line you would not want quoted. "Frustrated that staging keeps breaking" is something you observed and can help fix. "Negative, always complaining" is a label that would poison the room if it ever leaked.
The honest read you keep for yourself and the message you carry upward are two different documents. "@Priya is quietly burned out by the on-call rotation" is private. "The on-call load is coming up across the team and we should look at the rotation" is what you say to her manager, the same concern, stripped of attribution. Keeping the two apart is what lets you be both honest in your own notes and safe for the people who trusted you.
How to follow up after a skip-level
A skip-level without follow-up trains people not to bother next time. Closing the loop is what makes the next round honest, and it runs in two directions.
- Back to the person. Tell them what you did with what they shared, even when the answer is no. "I looked into the staging budget; it's not approved this quarter, here's why, and here's the workaround we landed on." People can live with a no. What they cannot live with is silence, because silence tells them honesty was pointless.
- Up to their manager, as a theme. Feed patterns back without quotes and without names. "I'm hearing that planning runs long and estimates feel like commitments; worth tightening together," not "three of your reports said your planning is broken." You are trying to help the manager get better, not put their team at risk.
- Against your own commitments. Every "I committed to" line is a debt. Put it somewhere dated that you actually return to, and clear it. Reading your last skip-level note before the next one means you walk in having already closed last time's loop, which is the single biggest trust-builder available to you.
If something serious and specific comes up, a real conduct concern, not a theme, that is the moment to step out of the skip-level frame. Ask the person how they want it handled, and route it through your organization's proper process. Your notes inform that judgment; they are not the process itself.
Where Notivo fits
This is the kind of work Notivo was built to make effortless: a private, per-person running log that you can also read by topic. After a skip-level you write a couple of quick notes and tag the person with @ and their name, and tag the recurring concern with # and a topic. It files into that person's dated timeline. Type @Priya later and her whole history is there; pull up a #planning topic and you see every person who has raised it, in date order, across the org. That is what turns a stack of separate conversations into the pattern you actually needed to see.
You can capture from wherever the thought lands: the web app right after the meeting, WhatsApp on the walk back, or the ChatGPT and Claude connectors. When you are getting ready for a staff meeting or your own skip-up, an AI assistant can draft a recap or answer a question, but only from your own notes: it reads what you wrote, never trains on your data, and never invents anything you did not capture. And for the most sensitive line, a serious concern someone shared in confidence, there is a Black Box vault you unlock with a PIN; that, and only that, is end-to-end encrypted.
On storage for everything else, the honest answer: your notes are private by default and scoped to your own account, and they are stored on secured infrastructure. That is platform-level security, the protections that come with reputable cloud storage. It is not a claim that your regular note content is encrypted end-to-end, and we are not going to pretend otherwise. So use the same judgment you would use with any cloud notes app: this is the right home for your working memory of who said what, and the Black Box is there for the few lines that need more.
Read across every skip-level by person and by topic, so the recurring concern finally lands.