Guide
How to Run Sales Engineer 1:1s That Actually Develop Your Team
Most SE one-on-ones are disguised pipeline reviews. Here's the framework that turns them into your highest-leverage coaching time.
If you lead solution engineers, the 1:1 is the most valuable thirty minutes on your calendar. It's also the most commonly wasted. Ask a room of SE managers what their one-on-ones look like and most will describe the same thing: open the pipeline, go deal by deal, talk through what's happening. That's not a 1:1. That's a forecast call with one attendee.
The fix isn't more meetings or a longer agenda. It's a fixed structure that protects the part of the conversation that actually develops people. We call it the 5/10/15 one-on-one.
Why most SE 1:1s are broken
Deal talk expands to fill whatever time you give it. There's always a live opportunity, always something on fire, always a reason this week's session should be "just a quick pipeline check." So the personal and the developmental get squeezed out — every single week — until the meeting is pure deal status and your SE has quietly concluded that the 1:1 is for you, not for them.
That conclusion is the real cost. The deals get discussed either way, in standups and Slack and deal desks. What doesn't happen anywhere else is the deliberate, repeated investment in the person. Skip it long enough and you're managing a list of opportunities instead of leading a team.
The 5/10/15 framework
Split every session into three fixed blocks. Same structure, every time. The fixedness is the point — when the shape is predictable, the parts that usually get cut are guaranteed their slot.
5 minutes — Personal check-in
Start with the human, not the dashboard. How are they actually doing — energy, workload, anything outside work pressing on them. This isn't filler before the "real" agenda. People who feel seen do harder things, ask for help earlier, and stay longer. Five honest minutes here is worth more than another deal walkthrough.
The trap is making it performative — "How are you? Great, anyway, let's get to the pipeline." Ask, then leave enough silence that a real answer can land.
10 minutes — Skill development
This is the block almost no one protects, and it's where the compounding happens. Pick one capability the SE is working on — discovery questioning, narrative-driven demos, handling a hostile technical stakeholder, writing a tighter business case — and spend ten minutes on it. Review a recording, role-play the next hard conversation, unpack a call that went sideways.
One skill at a time, held for long enough to actually move. A team that improves one real skill per quarter, per person, looks like a different team a year later. Trying to fix everything at once fixes nothing.
15 minutes — Deal work
Now the deals — but go deep on one, not wide across all of them. Pick the riskiest or most strategic and start with the simplest, hardest question: why is this customer actually going to spend money with us? If the SE can't answer that cleanly, the deal isn't qualified yet, and you've just found the real work. From there: who's the economic buyer and have we met them, what has the customer explicitly said they need to see to move forward, and — if this deal went dark tomorrow, why? Leave with one next step the SE owns, with a date on it.
A small technique that does a lot of work here: use open questions to pull insight ("walk me through the pain chain") and closed ones to force commitment ("will the mutual action plan be written by Friday?"). You're coaching judgment, not collecting status.
The one rule that makes it work
The 1:1 is sacred. When a deal is genuinely on fire and needs the full thirty minutes, you handle that fire in a separate meeting. The one-on-one is not your emergency room — it's your coaching gym. The moment you let emergencies routinely take it over, you've taught your team that this time isn't really theirs. Protect the slot and the structure even in the weeks it feels inefficient, especially then.
Making it stick
A framework you abandon under pressure is worse than no framework, because now there's a broken promise attached. A few things that keep it alive:
- Protect the cadence. Weekly for direct reports, every other week at the absolute floor. If something genuinely has to move it, reschedule within 48 hours — don't cancel.
- Let the SE drive. It's their meeting. You hold the structure; they bring what to talk about. A 1:1 the manager fully controls is just a status check with extra steps.
- Both of you prep. Two minutes each: they line up the deal to go deep on and how the skill work went; you review what they committed to last time. A shared running doc means you're not improvising the developmental part on the spot (which is exactly when it gets dropped).
- Pick the skill together, and keep it. Rotating to a new focus every week is just deal talk wearing a costume. Stay on one until it moves.
- Write down what you agreed. The follow-through across sessions is what turns thirty minutes into actual development.
A 1:1 agenda you can copy
SE 1:1 — [name] — [date]
① Personal (5 min)
- How are you, really? Energy / workload / anything off-work
- Anything you need from me this week
② Skill (10 min) — focus this quarter: [skill]
- What we're working on
- Review / role-play / debrief a real moment
- One thing to try before next time
③ Deals (15 min) — only where I can change the outcome
- What's stuck and why
- Where you need my altitude
- Your next move if I weren't here
If you lead managers, not individual SEs
If you run a larger org and your direct reports are SE managers, the 5/10/15 still applies — you just run it one level up. The "skill" block becomes their leadership: how they're coaching their own people, where they're defaulting to control under pressure, which of their SEs needs attention. Don't reach past them to run 1:1s with individual contributors. Model the structure with your managers and let it cascade.
The takeaway
Stop running pipeline reviews and calling them one-on-ones. Give every session the same three blocks — five minutes on the person, ten on a skill, fifteen on the deals only you can move — and defend that structure even when a deal is screaming for the whole half hour. It's a small change you make once and benefit from every week after.
Get the 1:1 Meeting Playbook
The one-page SE leader toolkit — the full agenda plus the exact questions to ask in each section, what to listen for, and the open-vs-closed question rule. Free PDF.
Frequently asked
How often should you have 1:1s with sales engineers?
Weekly is the default for direct reports; every other week is the floor. The cadence matters less than the protection — a 1:1 that gets cancelled the moment a deal heats up teaches your team it was never really for them.
How long should an SE 1:1 be?
Thirty minutes, run as a fixed 5/10/15 split: 5 minutes personal check-in, 10 minutes skill development, 15 minutes deal work. The structure stops the deal talk from eating the whole meeting.
What should you talk about in a sales engineer 1:1?
Three things, in order: how the person is actually doing, one skill they're working on, and the deals that need you. Reverse the order and you get a status meeting with a wellness question bolted on the front.
Should SE 1:1s be about pipeline?
Pipeline is part of it — the last 15 minutes — but if it's the whole meeting you've built a forecast call, not a coaching relationship. Deal reviews tell you what happened; the personal and skill blocks change what happens next.
Hear it on the show
SE Rockstars helps PreSales teams become trusted advisors — the team behind the Trusted Advisor Academy, founded by Tim Brömme & Jan-Erik Jank.