Leadership without a management title is still leadership. This theme is for architects, staff and principal engineers, and tech leads who need to set direction, earn trust, and get things done without a manager’s formal authority.

Contents

Influence and persuasion

  • Leading without authority โ€” the foundational principle for the whole theme
  • Building technical credibility as a source of influence
  • Influence through teaching and pairing, not orders
  • Framing technical arguments for non-technical stakeholders
  • “Disagree and commit” โ€” dissent without hierarchy
  • Negotiation basics for non-managers

Technical direction and decision-making

  • Setting technical vision without a title for it
  • Writing effective RFCs / ADRs / design docs
  • Running design reviews that actually decide something
  • Saying no to a bad idea, with data, not with power
  • Pragmatism vs. purism (technical debt trade-offs)
  • Staff engineer archetypes: Tech Lead, Architect, Solver, Right Hand (the Will Larson model)
  • Second-order thinking in architecture decisions

Communication and visibility

  • Writing for a technical audience (internal papers, design docs, blog posts)
  • Presenting technical work to non-technical leadership
  • Cross-team alignment without formal authority over those teams
  • “Managing up” without being a manager
  • Building a leadership reputation as an IC

Mentoring and growing others

  • Mentoring vs. coaching vs. managing โ€” the important distinction
  • Pairing and knowledge-sharing as a leadership tool
  • Growing juniors without HR authority
  • Giving feedback without formal power behind it

Personal practice

  • Career growth as an IC (the staff+/principal ladder)
  • Avoiding the “shadow manager” trap (informally doing a manager’s job without the title or pay)
  • Protecting focus time and saying no to distractions
  • Office politics as a non-manager
  • Impostor syndrome at senior IC level