How I Walk Into Technical Meetings Outside My Core Expertise (With a Little Help from Copilot)
Notes by SDG ·
If I’m honest, technical meetings still make me pause sometimes.
Not because I don’t enjoy them — but because the depth can get real, real fast. Architecture discussions, security patterns, incident history. And while I’ve spent years working closely with engineering teams, I’m not pretending to be the deepest technical expert in the room.
Recently, I had one of those meetings coming up. The kind where you know the conversation will be layered, nuanced, and full of history — much of it buried across emails, support cases, and side discussions.
So instead of cramming documentation or chasing every thread myself, I started with a simple question to Copilot:
“Can you help me prepare for this meeting?”
That one prompt completely changed how I showed up.
Letting Copilot do the heavy lifting
Because Copilot has access to my past support emails, ongoing discussions, and relevant context, it didn’t give me a generic summary.
It surfaced:
- Related support cases I hadn’t revisited in months
- Previous discussions tied to the same underlying concerns
- Patterns that kept reappearing — and just as importantly, things that didn’t matter
What usually feels like scattered noise suddenly looked like a story.
And for the first time, I wasn’t reacting to information — I was understanding it.
Separating what matters from what doesn’t
One thing I’ve learned over time: the hardest part of prep isn’t lack of data — it’s too much data.
Copilot helped me step back and ask:
- What are the recurring themes here?
- Which issues are structural vs one‑off?
- Why do these same questions keep coming up?
That clarity alone made me more confident. I wasn’t memorizing details — I was anchoring on what actually mattered.
Building a mental model, not a perfect answer
I didn’t ask Copilot for a perfect design or definitive explanation.
I asked it to help me envision a plausible scenario — the kind that would explain the questions and concerns I was seeing.
That gave me a mental model I could work with.
Was it perfect? No.
Was it useful? Absolutely.
And in a meeting, useful beats perfect every time.
Understanding the why behind the questions
The biggest personal breakthrough for me wasn’t technical at all.
Copilot helped me think about why people were asking what they were asking. What risks they might be worried about. What outcome they were trying to protect.
Once I framed the conversation around intent rather than implementation, everything felt more natural — and honestly, more human.
Walking into the meeting feeling calm (not performative)
Because I’d done this kind of prep:
- I didn’t feel the need to prove technical depth
- I could ask thoughtful, grounded questions
- I could steer the conversation when it drifted
I was open about what I didn’t know — and confident about what I did understand.
And that balance felt right.
What this changed for me
Copilot didn’t turn me into a technical expert.
What it did was:
- Help me make sense of context that already existed
- Save hours of manual prep
- Let me show up present, curious, and focused
At this point, I don’t think of Copilot as a shortcut.
I think of it as a thinking partner — one that helps me prepare in a way that feels thoughtful, real, and aligned with how I actually work.