Skip-level meetings -- where you meet with people who report to your direct reports -- are one of the most powerful leadership tools available. They're also one of the most commonly wasted.

The typical skip-level goes like this: you schedule thirty minutes with someone two levels down. You ask how things are going. They give you a polished, safe answer. You nod. You both leave. Nothing changes. Three months later, you do it again with equally little impact.

The problem isn't the meeting format. It's the lack of continuity. Without context from previous conversations, every skip-level starts from zero. Without a system for tracking themes across multiple skip-levels, patterns stay invisible. And without follow-through on what you hear, people learn that these meetings don't matter.

AI-powered notes fix all three problems.

Before the Meeting: Context in Ten Seconds

If you've met with this person before, open Mem Chat before the meeting and ask:

"What did I discuss with [person] in our last skip-level? Any open items?"

If you haven't met with them before, ask:

"What do I know about [person] from other meetings and notes?"

Mem searches across every note where this person has been mentioned -- team meetings, 1:1 notes with their manager, project updates, even offhand comments in other conversations. You walk in knowing their recent work, what challenges their team has flagged, and what context exists from prior interactions.

This is the difference between a skip-level that feels perfunctory and one that feels genuinely attentive. When you reference something from their last conversation or acknowledge a challenge their team is facing, people recognize that you're actually listening -- and they start sharing real information instead of rehearsed answers.

During the Meeting: Capture Everything

Record the conversation using Voice Mode. This is critical for skip-levels because the most valuable insights often come casually -- a throwaway comment about a process that's broken, a hesitation before answering a question about team morale, a suggestion buried in the middle of a longer answer.

If you're typing notes while someone is telling you something important, you're splitting attention at the worst possible moment. Record it, be fully present, and let the AI extract the key points afterward.

After the meeting, Mem generates a structured note with discussion topics, key insights, and any action items. File it to that person's collection and to a general "Skip-Levels" collection if you maintain one.

After the Meeting: The Follow-Through That Builds Trust

Here's where most leaders fail: they hear something in a skip-level, nod thoughtfully, and then do nothing about it. The information goes into the void. The next time that person meets with you, they remember that nothing happened. So they share less. The meeting becomes pure theater.

Follow-through is what makes skip-levels valuable, and AI notes make follow-through automatic. In your weekly review, when you ask Mem "What should I follow up on from this week?", skip-level action items surface alongside everything else. They don't get lost in the shuffle of your daily priorities.

If someone raised a concern about tooling, you can check in with their manager. If someone mentioned a process bottleneck, you can investigate. If someone had an idea worth exploring, you can make sure it gets to the right person. And in your next skip-level with that person, you can say "Last time you mentioned the deployment pipeline was slowing your team down. I talked to your manager about it and we're looking into X." That sentence transforms the entire relationship.

Patterns Across Skip-Levels

The real power of skip-level notes emerges when you've done a dozen of them across an organization. Individual conversations are valuable. Cross-conversation patterns are transformative.

After a round of skip-levels, ask Mem Chat:

"What themes have come up across my recent skip-level meetings?"

"Are there any issues that multiple people have raised?"

"What's the general sentiment about [specific topic] across my skip-levels?"

When three different people in three different teams mention that the planning process feels disconnected from execution, that's a signal. When several people express confusion about a recent organizational change, that's a communication gap. When everyone in one group says morale is high but everyone in another says it's low, that's a management delta worth investigating.

These patterns are invisible without notes. No leader can hold the themes from fifteen conversations in their head and synthesize them accurately. The AI can.

The Skip-Level Question Bank

The questions you ask determine the quality of what you learn. Here are some that consistently surface real insight:

• "What's working well on your team right now?"

• "If you could change one thing about how we work, what would it be?"

• "What's something your manager does that helps you most?"

• "Is there anything you think leadership doesn't see?"

• "What would make your day-to-day work easier?"

Keep your best questions in a note so you can iterate on them over time. After each round of skip-levels, review what produced the most useful responses and refine your approach.

The Relationship With Your Direct Reports

A common concern about skip-levels: won't my direct reports feel threatened? They might, if you handle it poorly. The best practice is transparency. Tell your directs that you're doing skip-levels, that the purpose is to get a broader perspective on team health, and that you'll share relevant themes (without attributing specific comments) in your regular 1:1s.

Having notes from both your skip-levels and your 1:1s with the manager in the same system lets you connect dots responsibly. If someone in a skip-level raises a concern that their manager should address, you can bring it up in your next 1:1 in a way that's constructive rather than accusatory: "I've heard from a few people that the sprint planning process feels rushed. What's your take?"

Heads Up helps here too -- before your 1:1 with a direct report, Mem can surface themes from your recent skip-levels with their team, giving you a natural way to bring up what you've learned.

Frequency and Scale

Skip-levels don't need to be frequent to be effective. Quarterly is plenty for most organizations. What matters is consistency and follow-through.

For a manager with thirty to fifty people in their organization, that's maybe ten to fifteen skip-levels per quarter -- a manageable cadence. The AI notes make each one productive by providing context going in, capturing everything during, and ensuring follow-through after.

Getting Started

1. Schedule skip-levels with three to five people from different parts of your organization

2. Before each one, ask Mem Chat for any relevant context about that person

3. Record the conversation with Voice Mode -- be present, not note-taking

4. After each meeting, file the note to that person's collection

5. In your weekly review, follow up on anything you committed to or learned

6. After completing a round, ask Mem for cross-conversation themes

Skip-level meetings are only as good as what happens between them. AI notes close the gap between "I heard you" and "I acted on what I heard."

Try Mem free →