Manu's Vault

Management Map of Content

10 min readStatus:Seedling

Management - Map of Content

This domain explores management and leadership as practiced in technology organisations. Management here is not treated as an abstract discipline—it is the applied craft of building and sustaining high-performing teams, running effective delivery, and navigating organisational complexity in real software environments.

The content builds from foundational questions (what management is, how it differs from leadership) through the practical daily work (people development, goal-setting, delivery) to the structural and strategic concerns (organisational design, influence, engineering-specific challenges). Throughout, the focus is on evidence-based practice and the hard-won lessons that distinguish management as a skill from management as a title.

This domain connects closely to Architecture (technical leadership, Conway’s Law), Psychology (team dynamics, behaviour change), and Business (systems thinking, organisational learning).

🎯 Management Fundamentals

The conceptual foundations: what management is, how it differs from leadership, and why both matter in complex organisations.

  • The-Rands-Test — A diagnostic checklist for evaluating management quality within an engineering organisation
  • Three-Managerial-Superpowers — The three capabilities that distinguish effective managers: information gathering, decision-making under uncertainty, and context provision
  • Manager-as-Communication-Hub — The manager as the critical node that translates, filters, and routes information across team boundaries

From Larson — An Elegant Puzzle:

  • Four-States-of-a-Team — The four stages a team moves through (Falling Behind, Treading Water, Repaying Debt, Innovating) and how managers diagnose and intervene at each stage
  • Six-Degrees-of-Managerial-Control — Larson’s six levers available to managers when addressing team problems: organisation, headcount, scope, process, technology, and tactics
  • Close-Out-Solve-or-Delegate — A triage framework for managing a backlog of obligations: close out what you can, solve what requires action, and delegate the rest
  • Work-the-Policy-Not-the-Exception — The principle that sustainable management requires building and enforcing consistent policies rather than making individual exceptions
  • Exception-Debt — The accumulated cost of unresolved exceptions to policy that creates unpredictability, inconsistency, and managerial overhead over time

👥 People Management

The core of management work: building relationships with individuals, developing their careers, and creating the conditions for sustained performance.

Hiring & Onboarding

  • Bellwether-Interviewers — Using trusted, consistent interviewers as calibration anchors to maintain hiring quality at scale

From Larson — An Elegant Puzzle:

  • Three-Candidate-Sources — Larson’s three channels for sourcing candidates: referrals, inbound applications, and outbound (cold) sourcing—each with distinct yield and effort profiles
  • Cold-Sourcing-Technique — A structured approach to reaching out to passive candidates who have not applied, including how to write effective outreach and personalise at scale
  • Hiring-Funnel — The staged pipeline from sourcing through offer, with metrics for diagnosing bottlenecks and improving conversion at each stage
  • Extended-Hiring-Funnel — An expanded view of the hiring funnel that includes pre-offer relationship-building and post-offer onboarding as integral stages
  • Humane-Interview-Process — Design principles for interview processes that respect candidates’ time, reduce bias, and accurately predict on-the-job performance

Performance & Career Development

From Larson — An Elegant Puzzle:

  • Performance-Management-System — A structured approach to evaluating and improving individual performance: setting expectations, gathering evidence, calibrating ratings, and delivering feedback
  • Calibration-System-for-Performance — The organisational process of normalising performance ratings across managers to reduce bias and ensure fairness at scale
  • Designation-Momentum — The tendency for performance designations to persist across cycles due to anchoring and social dynamics, and how to counteract it
  • Career-Level-Dynamics — The mechanics of how engineers progress through career levels, including the role of sponsorship, visibility, and scope expansion
  • Creating-Specialized-Roles — The design and justification of specialist or principal roles that serve organisational needs without requiring management track advancement
  • Floor-vs-Ceiling-Career-Model — A model distinguishing careers defined by minimum performance expectations (floor) from those defined by maximum potential (ceiling), with implications for development conversations
  • Career-Narrative-Framework — A structured approach to helping engineers construct a coherent narrative about their career trajectory and contribution for promotion cases and self-advocacy

1:1s & Feedback

  • 1on1-Meeting-Formats — A typology of one-on-one meeting structures matched to different managerial contexts and goals
  • The-Twinge — The manager’s intuitive signal that something is wrong, and how to act on it productively
  • Feedback-Orientation-Model — A model for understanding how individuals differ in their capacity to receive and use feedback

🏗️ Team Building & Organisational Design

How teams are structured, how culture forms, and how the design of an organisation shapes the work it produces.

  • Free-Electrons — High-autonomy engineers who operate outside normal team structures and must be managed differently
  • Incrementalists-and-Completionists — Two fundamental cognitive styles that produce predictable tensions and complementary strengths in engineering teams
  • Organics-and-Mechanics — A personality typology distinguishing intuition-driven from process-driven engineers, with implications for team composition
  • Reorg-Navigation-Principles — How to survive and capitalise on organisational restructuring as a manager or individual contributor
  • DNA-Meeting — The Design and Architecture meeting as a structured forum for technical decision-making and architectural governance

From Larson — An Elegant Puzzle:

  • Organizational-Debt — The accumulated structural and process obligations that slow a growing organisation, analogous to technical debt but at the human-systems level
  • Peanut-Buttering-Anti-Pattern — The failure mode where headcount and responsibilities are spread too thinly across too many teams, diluting impact and slowing delivery
  • Growth-Plates — The organisational equivalent of biological growth plates: the points at which a growing team transitions through structurally distinct phases requiring different management approaches
  • Hero-Programmer-Anti-Pattern — The dysfunctional pattern where a single indispensable individual becomes a bottleneck and dependency risk for the entire team

📊 Systems Thinking & Measurement

Using systems models and metrics to understand, diagnose, and improve engineering organisations.

  • Systems-Thinking-Stocks-Flows-Feedback — The foundational language of systems thinking—stocks, flows, and feedback loops—applied to engineering team dynamics
  • DORA-Four-Metrics — The four research-backed engineering performance metrics: deployment frequency, lead time for changes, change failure rate, and time to restore service
  • Team-Snippets-and-Directional-Metrics — Lightweight transparency practices (team snippets and directional metrics) that provide visibility into team health and momentum without bureaucratic overhead
  • Sprint-Process-Criteria — The conditions under which adopting a sprint-based process adds genuine value versus imposing unnecessary process overhead on a team

🎯 Goal Setting & Strategy Execution

Frameworks for aligning individuals, teams, and organisations around shared direction and measurable outcomes.

  • Hacker-Culture-Growth-Paradox — The tension between the informal, autonomous culture that attracts engineers and the structure required as organisations scale
  • Rands-1.0-Hierarchy — Lopp’s articulation of the values and priorities that define effective engineering leadership

From Larson — An Elegant Puzzle:

  • Strategy-vs-Vision — The distinction between strategy (how to navigate the current constraints and reach a goal) and vision (the aspirational long-term state), and why conflating them causes alignment failures
  • Good-Strategy-Structure — Larson’s framework for what makes a strategy good: a diagnosis, guiding policies, and coherent actions that together address the core challenge
  • Presenting-to-Senior-Leadership — Techniques for structuring presentations to executive audiences: lead with the conclusion, support with evidence, and anticipate the questions that matter most

📋 Delivery & Process Management

Running the work: agile practices, prioritisation, estimation, and managing the gap between plan and reality.

  • Trickle-Theory — The principle that small, consistent actions compound over time to produce significant organisational change
  • Malcolm-Events — Pivotal, often unplanned moments that irreversibly alter a team member’s trajectory or commitment
  • Context-Capture — The systematic practice of documenting situational context to preserve institutional memory and enable better decisions
  • The-Soak — The deliberate practice of allowing ambiguous decisions to incubate before forcing resolution

From Larson — An Elegant Puzzle:

💬 Communication & Influence

Managing up, across, and outward. Stakeholder alignment, difficult conversations, and the mechanics of organisational influence without authority.

  • Information-Starvation — The organisational dysfunction that emerges when teams lack the context and transparency they need to function effectively
  • Managementese — The use of vague, jargon-heavy language that managers employ to avoid commitment or uncomfortable specificity
  • Alignment-vs-Informational-Meetings — Distinguishing meetings that seek to create consensus from those that seek only to transmit information
  • Players-vs-Pawns — A framework for understanding team members’ agency, investment, and willingness to influence outcomes
  • Crisis-Management-War-Room — The structure and dynamics of high-stakes, cross-functional crisis response in engineering organisations

From Larson — An Elegant Puzzle:

  • Positive-and-Negative-Freedoms — The distinction between positive freedoms (freedoms to act) and negative freedoms (freedoms from constraint), and how engineering managers must balance both for their teams
  • Opportunity-and-Membership — The two dimensions of inclusion in engineering organisations: access to meaningful opportunities and genuine sense of belonging
  • Communities-of-Learning — Internal learning communities—guilds, practice groups, reading circles—as a mechanism for spreading knowledge and building shared professional identity across teams

💻 Engineering Management

Management as practiced specifically in software engineering contexts: the engineer-to-manager transition, staff engineering, technical leadership, and the relationship between management and architecture.

Structure Notes

  • Managing-Engineers-Framework — A synthesised framework for understanding and managing the cognitive and motivational patterns of software engineers
  • Engineering-Manager-Toolkit — An integrated set of tools and practices for engineering managers drawn from Lopp’s accumulated experience

From Larson — An Elegant Puzzle:

Atomic Notes

  • NADD — Nerd Attention Deficiency Disorder: the pattern of rapid context-switching that characterises how many engineers process information
  • Nerd-Cave-and-Deep-Work — The physical and temporal conditions under which engineers achieve their most productive, creative states

📚 Literature

Source material for this domain.

  • Managing Humans - Lopp - 2019 — Michael Lopp’s collection of management essays drawn from engineering leadership at Apple, Pinterest, Slack, and Palantir
  • Larson-2019-An-Elegant-Puzzle — Will Larson’s systems-oriented guide to engineering management: team health, organisational design, strategy, hiring, and career development

For new managers: Start with Management Fundamentals to orient the role, then move to People Management—the 1:1 and feedback work is where most impact lives early on.

For experienced managers: Focus on Organisational Design, Strategy Execution, and the cross-domain connections to Business and Architecture. Larson’s Four-States-of-a-Team and Six-Degrees-of-Managerial-Control are particularly high-leverage.

For architects and technical leads: Engineering Management and the cross-domain Architecture connections are most directly relevant. See also Knowledge-Flow-in-Software-Architecture and Conway’s-Law. Larson’s Technical-Migrations-De-risk-Enable-Finish is essential for large-scale platform work.

Source navigation: Notes marked From Larson — An Elegant Puzzle draw from Will Larson’s systems-oriented management framework (2019). Notes without a source tag are drawn primarily from Michael Lopp’s Managing Humans (2019). See the Literature section for full source notes.

Cross-Domain Connections

Management knowledge compounds when connected across domains:

  • Architecture: Organisational design and Conway’s Law; technical leadership; the architect-as-leader role; knowledge flow in software organisations; Bus-Factor (knowledge concentration as measurable org risk — directly relevant to career stagnation and team resilience)
  • Psychology: Psychological safety; feedback models; team dynamics; behaviour change as the mechanism behind performance
  • Business: Systems thinking applied to organisational behaviour; the five disciplines of the learning organisation; mental models

Sources

This is a navigation/organisation note. For sources, see individual linked notes.

Note

This content was drafted with assistance from AI tools for research, organisation, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.

Graph View

Backlinks