Spot the Super-IC Before the Numbers Do [61]
The episode discusses three diagnostic signals to identify managers who are individual contributors rather than developing leaders: closed-door one-on-ones only, rhetorical patterns of blame or over-ownership, and escalation emails with excessive CC'd recipients. The hosts emphasize that these behavioral patterns appear months before performance numbers decline, allowing early intervention.
Summary
Tim introduces Leading Pre-Sales, a show for solution engineering leaders, noting that all content is based on real coaching situations. The episode focuses on identifying first-line managers who function as super individual contributors (ICs) rather than team developers.
The hosts present three diagnostic signals. First, the forecast call format reveals whether a manager is developing the team or centralizing control. Leaders who develop teams invite SEs and cross-functional partners, creating group learning opportunities. Managers who only conduct individual one-on-ones signal they believe deals are theirs to own and prevent team learning. While one-on-ones serve a purpose for safety, relying exclusively on private channels indicates the manager fears correction in front of the team rather than protecting vulnerable employees.
Second, the rhetoric pattern shows two concerning behaviors: either blaming everyone else (procurement, marketing, AEs) or taking every problem personally, claiming ownership. The latter appears heroic but is corrosive—when a manager solves nine problems in 90 minutes without delegating, the team learns nothing. This habit is sustainable at small team sizes (12 SEs) but becomes destructive when scaled to 25+ people.
Third, escalation emails with excessive CC'd recipients (two levels up, peer VPs, regional leads) signal performative urgency rather than genuine leadership. These emails communicate "look how hard I'm working" and assign blame, and such patterns are readable from two organizational levels away without direct inquiry.
The hosts distinguish between management (inspect, control, direct) and leadership (agree measurable outcomes, watch progression, leave accountability with the person). The question of whether to coach or restructure depends on whether the person can genuinely develop into a leader. The "holiday test" assesses this: if a manager can disappear for three to four weeks and operations continue running smoothly, they've built something sustainable. Conversely, if teams are fear-based and cover up problems to protect themselves, the diagnostics become unreliable.
The recommended action is to observe one forecast call monthly (camera off), note who was invited and what they were asked to solve, then ask what happens to the team without the manager present.
About this episode
Nate shares the behavioural signals that expose a first-line SE manager who's really just a super-IC with a title — visible in how they design their forecast call and how they write email under pressure. Ava pushes on whether that's coachable or structural.
Key Insights
- Managers who only conduct individual one-on-ones and avoid group forums reveal they believe deals are theirs to own and fear being corrected in front of the team, which prevents organizational learning.
- When a manager takes personal ownership of every problem raised in meetings (nine problems, nine solutions), the team gains zero development over the entire interaction, even though the behavior appears heroic.
- Behavioral diagnostics of poor management—closed-door calls, blame rhetoric, excessive-recipient escalation emails—are visible months before attainment numbers decline, providing a free early warning system to leadership.
Topics
Transcript
Hey there and welcome to Leading Pre-Sales, the show for solution engineering leaders who want to build teams that drive revenue and not just demos. My name is Tim and I'm the co-founder of SE Rockstars and together with Jan, we've coached over 350 solution engineers and their leaders across several dozens of companies. Every conversation you hear on this show is based on real coaching situations, real challenges, real problems that as leaders like you are dealing with right now, none of this is made up. We use AI to bring these stories to life through our two hosts, Nate and Ava, but the insights come straight from the trenches. Each episode gives you one actionable takeaway you can…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Leading PreSales | The Solution Engineering Leadership Show
Fifty Leaders, One Borrowed Office [60]
SE Rockstars hosts in-person leadership events across European cities featuring keynotes, breakout sessions voted on by attendees, and networking dinners. The community uses a member portal with recordings, directories, and event management tools to connect 250+ solutions engineering leaders who face similar challenges.
The Loneliest Job in the Building [59]
The episode explores the SE Rockstars Pre-Sales Leadership Community, a peer network of ~250 solution engineering leaders across Europe that addresses the isolation of SE leadership roles. The community operates through monthly online sessions with breakout discussions and an optional WhatsApp group for rapid problem-solving, with strict governance to prevent vendor infiltration.
The Seven-Figure Promotion [58]
The episode examines why promoting high-performing individual contributors into first-line manager roles without proper preparation fails, costing organizations seven figures through lost productivity, departing talent, and compromised pipeline coverage. The hosts argue that training budgets and readiness gates must precede promotions, and that candidates should understand expectations before accepting the role.
Your SEs Don't Need the Price List. They Need the Metric. [57]
Solution engineers should understand the metric behind pricing (seats, transactions, credits) rather than memorize price lists, as this enables them to design solutions aligned with customer budgets and identify expansion opportunities. The episode emphasizes teaching SEs to estimate volume math and recognize when customer questions are actually about financial impact, not just technical capacity.
One Sentence: The Pricing Guardrail Every SE Team Needs [56]
SE leaders should implement a single scripted sentence when customers ask about pricing to prevent misstated numbers from anchoring negotiations. The sentence should deflect to the AE while offering value, reference published pricing when available, and be rehearsed by the team rather than just distributed in writing.