Last updated: April 24, 2026
GLOSSARY
The management terms, defined.
Plain-English definitions of the words first-time managers run into at work, written by a senior manager with more than a decade leading teams. For longer reading on each topic, follow the links to related letters.
CONCEPTS FROM NO SELF LIMITS
CONCEPT FROM NO SELF LIMITS
The Sunday Inbox Problem
The recurring symptom of working for a micromanaging boss, surfacing on Sunday night as a volume of oversight questions that could have waited until Monday but did not. The Sunday Inbox Problem is the leading indicator of the specific bind between a micromanaging boss above you and a team below you expecting direction.
Named and described in How to Manage Your Team When Your Boss Micromanages You.
CONCEPT FROM NO SELF LIMITS
The Pre-Dread Window
The stretch of time between deciding to have a hard conversation at work and actually having it, during which avoidance compounds the problem. The Pre-Dread Window is almost always worse than the conversation itself. The practical response is not to make the conversation easier but to shorten the window: schedule the meeting the moment you decide to have it, within 24 hours.
Named and described in Your First Difficult Conversation as a New Manager.
CONCEPT FROM NO SELF LIMITS
The Month-Two Dip
The predictable peak of new-manager imposter syndrome, occurring roughly between weeks six and ten of a new management role. The Month-Two Dip arrives when the adrenaline and novelty of the first weeks fade and the actual shape of the job becomes visible: management is judgment-work with insufficient information, done in public, while the team watches. The feeling is not a distortion. It is accurate feedback that the job is harder than its external description suggested.
Named and described in Imposter Syndrome as a New Manager.
CONCEPT FROM NO SELF LIMITS
The Management Middle
The flat stretch of a management career, typically hitting between month eight and month eighteen, defined by three specific markers: motivation that stays low regardless of output, weekends and weekdays blurring into the same gray, and the loss of novelty as the fuel that carried the first half of the role. The Management Middle is survivable but not by waiting it out.
Named and described in Manager Burnout: How to Keep Going When the Motivation Dies.
CONCEPT FROM NO SELF LIMITS
The Override Moment
The first time a new boss makes a decision that disregards your specific input on something you have direct experience with. The Override Moment is when you find out whether the new boss is rewriting the work in ways you can absorb, or in ways you can’t. How you respond to it sets the pattern for the next twelve months.
Named and described in When Your New Boss Won’t Listen and Changes Everything.
CONCEPT FROM NO SELF LIMITS
The Compression Check
Information traveling up a management chain compresses at every layer. Your direct reports’ managers summarize, prioritize, and sometimes filter what they pass to you, which is mostly necessary, occasionally biased, and always partial. The skip-level meeting is the audit on that compression. Done well, it tells you what was lost in translation. Done poorly, it just makes everyone wary.
Named and described in Skip-Level Meeting Questions: 25 That Surface Real Issues.
CONCEPT FROM NO SELF LIMITS
The Contagion Tax
The gradual cost paid by managers who report to chronically negative leaders, where the boss’s pattern of criticism, pessimism, or complaint becomes the manager’s own operating mode within six to twelve months. The tax compounds quietly: small affect drift, then language drift, then framing drift, until the manager runs their own team in a junior version of the same energy that’s been wearing them down.
Named and described in When Your Boss Is Always Negative.
CONCEPT FROM NO SELF LIMITS
The Survivor Read
The 30 to 60 day window after a leadership change in which the surviving members of a team with high turnover actively evaluate whether the conditions that drove their colleagues out are still present in the new manager. The read is constant, granular, and mostly silent. Decisions to stay or follow are made during this window, not announced afterward.
Named and described in When You Inherit a Team With High Turnover.
STANDARD MANAGEMENT VOCABULARY
Managing up
The practice of handling the relationship with your own manager or senior leader to make your work possible. It is not flattery or strategic compliance. It is the specific communication and expectation-setting moves that prevent your boss from becoming the obstacle to your team’s output. Managing up well usually means preempting your manager’s concerns, giving them information in the format and cadence they prefer, and pushing back clearly when their direction conflicts with what the work actually needs.
Difficult conversation
Any work conversation the participants are reluctant to have because the content is unpleasant, the stakes are high, or the emotional risk is real. Common examples include delivering underperformance feedback, informing someone their role is changing, negotiating conflict between team members, or telling a peer their work is not meeting the bar. The most consistent failure mode is not saying the wrong thing but avoiding the conversation entirely until the problem compounds.
1-on-1
A recurring private meeting between a manager and a direct report, typically 30 minutes weekly or biweekly. The purpose is not status update (that belongs in standups or written reports). The purpose is surfacing issues early, developing the report’s career, maintaining trust, and catching problems before they calcify. A 1-on-1 that produces only a task list is a misused meeting.
Direct report
An employee who reports to a specific manager in the organizational hierarchy, distinct from matrixed or dotted-line relationships. The manager is formally responsible for the direct report’s performance evaluation, compensation recommendations, career development, and day-to-day work assignment. The number of direct reports a manager has is called their span of control.
Skip-level meeting
A meeting between a senior manager and an individual contributor or junior manager who does not report directly to them, usually their direct report’s direct report. The purpose is to build relationships two levels deep, catch information that would otherwise filter through the middle layer, and signal that senior leadership is accessible. Skip-levels work when they are not used to bypass or undermine the middle manager.
Performance improvement plan (PIP)
A formal documented plan that outlines specific performance gaps, concrete objectives, measurable success criteria, and a timeline (typically 30 to 90 days) for an underperforming employee. A PIP is a legal and HR instrument as much as a management one; it creates the documentation trail required before termination. Most employees placed on a PIP do not recover, but the ones who do usually had a specific correctable issue rather than a fundamental fit problem.
Performance review
A periodic formal evaluation of an employee’s work, typically annual or semi-annual, resulting in a written assessment and usually a compensation decision. Good performance reviews should contain zero surprises for the employee because the feedback should have already been delivered in real time during 1-on-1s. A performance review that reveals new information about a manager’s opinion is a failure of ongoing management, not a success of the review process.
Imposter syndrome (manager context)
The persistent internal sense of being unqualified for a management role, frequently despite external evidence of competence. Manager imposter syndrome is different from individual contributor imposter syndrome because the job shape actually does change faster than identity does, and the feeling often contains accurate signal about the difficulty of the work rather than a distorted self-image. Most new managers experience acute imposter feelings between months two and nine.
Micromanagement
A management pattern characterized by excessive oversight of work that could be handled at the level of the person doing it, low trust in direct reports to make decisions, and process-focus rather than outcome-focus. Micromanagement is usually a symptom (of the manager’s anxiety, of new team formation, of structural unclarity) rather than a personality trait, which is why it often responds to better weekly communication from reports more than to direct feedback from above.
Delegation
Transferring ownership of a piece of work to a direct report, including the decision authority to do it their way, not just the task execution. Delegation done poorly is assigning tasks and retaining decision-making. Delegation done well is agreeing on the desired outcome and relinquishing the how. The difference determines whether a manager scales or becomes the bottleneck.
First 90 days
The initial three months in a new management role, treated as a distinct phase in management literature because the decisions made in this window disproportionately shape the next year or more. Classic advice focuses on learning the team, diagnosing the work, building credibility, and earning the right to change things. The most common mistake is making large changes in the first 30 days before the diagnosis is complete.
Feedback sandwich
A feedback technique that places critical feedback between two pieces of praise, on the theory that it softens the blow. Widely taught, widely criticized. The pattern produces predictable outcomes: the employee hears only the praise, the manager feels relieved to have delivered the criticism technically, and nothing changes. Most management research in the last decade recommends direct feedback without the sandwich, tied to specific observed behavior and a concrete next action.
Manager burnout
Chronic exhaustion specific to management roles, characterized by diminished emotional bandwidth for team members, cynicism about the work, and reduced sense of accomplishment despite maintained output. Different from individual-contributor burnout because managers cannot log off: the emotional labor of absorbing team anxiety, filtering bad news, and performing confidence on demand accumulates in ways that rest alone does not resolve. Usually requires a structural change (delegation, role scope, team composition) to actually repair.
Individual contributor (IC)
An employee who does their own work rather than managing others. The term distinguishes between the two main career tracks in most modern companies: the IC track (where promotion means increasingly autonomous technical or creative work) and the management track (where promotion means increasingly broad team responsibility). Senior ICs in technology, finance, and design now often out-earn mid-level managers, which has changed the decision of whether to pursue management at all.
Span of control
The number of direct reports under a single manager, a structural factor that determines how much time any one report can actually get. Spans of 4 to 6 allow for deep individual attention; spans of 8 to 12 force managers into coordination mode; spans above 15 turn the manager into a dispatcher. The right span depends on the work (more independent work tolerates larger spans) and the manager’s experience.
360 review
A performance feedback process that gathers input from an employee’s manager, peers, direct reports, and sometimes internal customers, rather than from the manager alone. The 360 review is designed to surface blind spots a single perspective misses. It is most useful as a developmental tool and least useful when the results drive compensation decisions directly, because anonymous peer feedback combined with financial consequence often produces political theater rather than honest data.
OKR (Objectives and Key Results)
A goal-setting framework that pairs an aspirational qualitative Objective with a small number of specific quantitative Key Results that measure progress toward it. Originated at Intel, popularized by Google. Good OKRs are ambitious enough that hitting 70 percent counts as success. Bad OKRs are restated tasks with dates attached. The most common mistake is confusing OKRs with operational KPIs: OKRs are for stretch goals, KPIs are for keeping the business running.
MBO (Management by Objectives)
A management approach coined by Peter Drucker in 1954, in which employees and managers agree on specific objectives and are evaluated against achievement of those objectives. MBO predates OKRs by decades and is philosophically similar but less aspirational in its structure. Many modern performance review systems are MBO in spirit even when they do not use the term. The critique of pure MBO is that it rewards goal-setting politicking over actual progress.
Psychological safety
The shared belief within a team that members can take interpersonal risks (asking questions, admitting mistakes, raising concerns) without being punished or humiliated. Studied extensively by Amy Edmondson at Harvard Business School and popularized by Google’s Project Aristotle which identified it as the single biggest differentiator between high-performing and low-performing teams. Managers build psychological safety through specific behaviors: responding to failure with curiosity rather than blame, modeling admission of uncertainty, and punishing silence more than disagreement.
RACI matrix
A project responsibility framework that assigns each task a Responsible (does the work), Accountable (owns the outcome), Consulted (input before decision), and Informed (told after decision) role. RACI is useful when a project spans multiple teams and the assignment of ownership is not obvious. It is overkill for teams of fewer than five people and for work where the responsibility is already clear.
Dotted-line report
An informal reporting relationship between an employee and a second manager, in addition to their primary (solid-line) manager. Dotted-line relationships are common in matrix organizations where work spans functions. They cause conflict when the two managers disagree about priorities, which is the normal state. Managing a dotted-line report well requires coordinating with the solid-line manager on expectations and explicitly naming the hierarchy when it matters.
Stretch assignment
A project or responsibility given to an employee that is meaningfully beyond their current skill level or experience, used as a development tool. Stretch assignments are the primary way high-performing employees grow faster than their peers. The risk is mismatch: if the stretch is too large, the employee fails publicly, and if the stretch is too small, it is just an assignment. Good stretch assignments include explicit coaching support and defined failure criteria.
Matrix management
An organizational structure where employees report to multiple managers simultaneously, typically one functional manager (by skill area) and one project or business manager (by outcome). Matrix organizations are common in large enterprises, consulting firms, and product companies. They are notorious for creating conflict over priorities, resources, and accountability. Managing in a matrix requires explicit communication about whose decision carries weight when the two managers disagree.
Stay interview
A structured conversation with a current employee (not one leaving) about what makes them want to stay at the company, what would make them leave, and what could be improved. Stay interviews are the proactive complement to exit interviews. They work best when framed as information-gathering rather than retention pitches, and when the manager actually follows up on what the employee shares. Done annually, they surface problems while they are still fixable.
Exit interview
A structured conversation with a departing employee about their reasons for leaving. Exit interviews are universally conducted and widely ignored by the companies that conduct them. The data is only useful if patterns are tracked over time and surfaced to the decision-makers who can change them. Most employees do not tell the full truth in an exit interview because they are protecting references, which limits the signal value.
eNPS (Employee Net Promoter Score)
A survey metric that asks employees how likely they are to recommend the company as a place to work on a 0-to-10 scale, then subtracts the percentage of detractors (0-6) from the percentage of promoters (9-10). Borrowed from customer Net Promoter Score. Easy to measure, contested as a leading indicator of business outcomes. Useful mostly for tracking change over time within a company rather than benchmarking against other companies.
Flight risk
An employee who managers believe is likely to quit in the near term. Flight risk is usually assessed informally through signals: decreased engagement, reduced advocacy for the team, increased visibility to recruiters. Formal flight-risk programs exist at some large companies but are often performative. The practical use of the concept is triggering retention conversations before resignation, which is almost always harder than preventing the need for them.
Stack ranking
A performance review system that forces managers to rank employees relative to each other and typically terminate a fixed bottom percentage each year. Associated with early-2000s Microsoft, Enron, and General Electric under Jack Welch. Widely abandoned in the 2010s after research showed it destroys collaboration, rewards politicking, and produces worse long-term performance than calibrated rating systems. Still found at some consulting firms and investment banks.
Blameless post-mortem
A retrospective analysis of a failure, outage, or incident that deliberately focuses on systemic causes rather than individual blame. Originated in aviation safety and site reliability engineering. The blameless framing is not about avoiding accountability but about surfacing the honest truth of what happened: people will not report their own errors in a culture that punishes them. Managers who run blameless post-mortems well learn more about their systems than managers who run blame sessions.
DACI decision framework
A decision-making framework that assigns each decision a Driver (runs the process), Approver (makes the final call), Contributors (provide input), and Informed (told the outcome). DACI separates the role of driving a decision from the role of making it, which reduces the common failure mode where the person running the meeting accidentally becomes the decision-maker. Used at Intuit and elsewhere. Lighter-weight than RACI for pure decision work.
Decision log
A written record of significant decisions made by a team or organization, capturing what was decided, who made the call, the reasoning, and the alternatives rejected. Decision logs compound in value over time because new team members can read them to understand why the current state exists, and future teams can revisit decisions when context changes. Underused because they require one person to maintain them against the short-term pressure to ship rather than document.
Retrospective (retro)
A meeting held at the end of a project phase, sprint, or quarter to reflect on what went well, what went poorly, and what to change next time. Borrowed from agile software development. Good retros produce specific commitments with owners and deadlines. Bad retros produce generic lists of grievances that nobody owns and nothing changes. The difference is almost entirely in how the meeting is facilitated.
Disagree and commit
A decision-making principle attributed to Intel’s Andy Grove and popularized by Amazon’s Jeff Bezos, stating that once a decision has been made through legitimate process, team members who disagreed should commit to executing it as if they had agreed. The principle resolves the tension between open debate and coordinated action. Misused, it becomes a way to shut down dissent before a decision is made. Used correctly, it lets disagreements surface without paralyzing the team.
Skip-level 1-on-1
A recurring private meeting between a senior manager and an individual who reports to one of their direct reports, typically monthly or quarterly. Similar to a skip-level meeting but specifically dyadic and recurring. The purpose is building relationship, catching signal, and demonstrating accessibility. Works when the middle manager is informed and not bypassed; fails when it becomes a vehicle for the senior to undermine their reports.
Standup meeting
A short (typically 15-minute) daily meeting where team members share what they did yesterday, what they plan to do today, and what is blocking them. Borrowed from agile software methodology. The value is not in the status update itself but in surfacing blockers while they are still solvable. Standups degrade when they become for-the-manager reporting sessions rather than for-the-team coordination.
All-hands meeting
A company-wide or large-team meeting where leadership shares updates and takes questions. All-hands are valued by leadership more than by attendees on average because leadership sees them as cultural touchpoints while attendees often see them as one-way broadcasts. The most effective all-hands include genuine Q&A, visible follow-through on questions from prior meetings, and recognition of specific individual contributions.
Town hall meeting
A subset of all-hands meetings focused specifically on two-way dialogue between leadership and the broader organization. The term emphasizes the Q&A component. Well-run town halls have pre-submitted questions to ensure the hard ones get asked, explicit time for follow-up questions, and named commitments by leaders to specific issues. Poorly run town halls have softball pre-screened questions and vague promises.
Kickoff meeting
The initial meeting that launches a new project, phase, or team effort, typically used to align on goals, roles, timeline, and success criteria. Good kickoffs produce a shared understanding that survives the first unexpected setback. Bad kickoffs produce enthusiasm without alignment, which degrades into confusion by week three. The best kickoffs include a visible artifact (written charter, one-page brief) that the team can point back to when decisions need to be made.
Working backwards
A planning approach originated at Amazon where teams begin a project by drafting the press release and FAQ for the finished product, then work backwards to the steps required to make the press release true. Forces clarity about what success actually looks like before resources are committed. Effective for consumer-facing product work; awkward for infrastructure or research work where the end state cannot be described concretely in advance.
BATNA (Best Alternative to a Negotiated Agreement)
The best outcome a party can achieve if negotiation fails, used as the floor below which no agreement makes sense. Coined in the book Getting to Yes. Knowing your BATNA before entering a negotiation (salary, contract, promotion, vendor terms) is the single most important preparation step. Managers who help their reports identify their BATNA before difficult internal conversations give them leverage they did not know they had.
Player-coach
A manager who still performs significant individual-contributor work alongside managing the team, rather than managing exclusively. Common in small teams, startups, and technical domains where the manager cannot afford to stop contributing. The risk is split attention: player-coach managers frequently underinvest in management because the IC work is more familiar and produces more immediate feedback.
Middle management
Managers who manage other managers, occupying the organizational layer between executives and frontline managers. Middle management absorbs most of the translation work in a company: executive strategy becomes team OKRs, team reality becomes executive updates. Chronically underrated in management literature. High-functioning middle managers are the biggest invisible differentiator between companies that scale cleanly and companies that stall.
Executive coaching
A paid professional relationship in which a trained coach works with a leader on specific developmental goals, typically over 3 to 12 months. Distinct from mentoring (less structured) and therapy (different scope). Most common at director level and above at companies that invest in leadership development. Effectiveness varies widely with the coach; companies vetting coaches should prioritize those with actual operating experience over those with only coaching credentials.
Talent calibration
A structured meeting where managers compare their performance assessments of their reports to ensure relative consistency across teams. Calibration is how companies prevent one manager’s lenient grading from inflating their team’s bonuses relative to a peer team with a stricter manager. Well-run calibrations surface disagreement constructively. Poorly run calibrations become politics where managers trade votes on each other’s employees.
High-potential employee (HiPo)
An employee formally identified as likely to grow into a significantly larger role. Companies use HiPo designations to allocate development investment, stretch assignments, and retention effort. HiPo programs are contested: they accelerate growth for the designated, risk stagnation for the non-designated, and frequently reflect manager preference more than objective potential. Communicating HiPo status to the employee is a debated practice; hiding it is usually worse.
Constructive feedback
Feedback delivered with the explicit intent of improving the recipient’s work or behavior, as opposed to venting, criticizing, or demonstrating expertise. Constructive feedback is specific (tied to a behavior, not a character), timely (delivered close to the event), and actionable (the recipient could do something different next time). Most workplace feedback fails one of these three tests. The distinction between ‘constructive’ and other feedback is whether the recipient has a clear next action after hearing it.
THE WEEKLY
One letter every Tuesday on the situations these terms actually appear in at work.
