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
Leaderboards, Not Cameras [89]
The episode examines why AI adoption dashboards and leaderboards often fail to drive behavior change, and proposes an alternative approach: publicly sharing AI workflows that actually shipped on real deals, ranked by peer reuse rather than usage metrics.
Your SEs Just Inherited the Customer's Bill [88]
Solution engineers must own usage estimation and sizing in consumption-based pricing models, even though they don't set prices. When SEs fail to accurately estimate how often workflows trigger, customers face billing surprises that damage relationships and renewals.
Rebrand or Real Role? The FDE Test [86]
The episode examines whether Forward Deployed Engineers (FDEs) represent a genuinely different role from Solution Engineers or merely a rebranding strategy. Through analysis of real job postings and market trends, the hosts present a three-question test to distinguish authentic FDE positions from SE roles with inflated titles.
No Quota, Still Commercial [85]
Forward Deployed Engineers (FDEs) should be measured on time-to-first-value and usage ramp rather than traditional sales quotas, with compensation tied to commercial outcomes that directly correlate to revenue under consumption pricing models. Success requires a disciplined 10x cost-recovery model, a defined pilot-to-contract path, and mandatory product feedback loops to prevent FDE teams from becoming expensive consulting operations.
Engineering Is the Entry Ticket [84]
Forward-deployed engineering engagements often fail due to poor discovery, scoping, and stakeholder management rather than technical deficiencies. Engineering skills are necessary to enter the room, but success depends on identifying success criteria, mapping stakeholders (especially those who lose if the project succeeds), and having leadership cover to push back on misguided requests.