Management & Leadership curriculum

One framing holds that management aims at efficiency, predictability and order, while leadership aims to bring about change. Some scholars add that management is about efficiency and leadership about effectiveness. The labels describe tasks, not people: a leader's job usually includes both, and how much each matters depends on the case.

A leader's responsibilities usually cover both kinds of task, and leadership scholars describe leadership skills as complemented by management. Mintzberg's model goes further and treats leading as one of ten managerial roles, alongside others such as monitoring and passing on information, so the two overlap in real work.

Research on nurses moving into management shows the pattern: people are often chosen for expertise in the work rather than for leadership ability, then meet changes in the work, in relationships and in responsibilities, and many report role ambiguity, self-doubt and emotional exhaustion.

Prioritizing management tasks takes different skills from prioritizing hands-on tasks. In an interview study of Italian nurse managers, lack of experience made prioritizing harder and raised the risk of essential management work being overlooked, excessive individualism was named as a contributing attitude, and the authors called for more support during the move from clinical to management roles.

When time runs short, urgent operational work such as covering staffing gaps crowds out the rest of the role. Nurse managers in one qualitative study kept resource management and problem solving going because the unit could not run without them, while supervision, coordination and staff development were missed or postponed.

Counting direct reports understates the load; an integrative review of nurse-manager studies reports work arguing the measure should also reflect how complex the unit is. Wider spans were linked to lower manager job satisfaction and to managers seen as distant, and one included study found no leadership style offset the effects of a wide span.

Middle managers sit between senior executives and frontline managers, and their work is interpreting strategy, coordinating operations and guiding the managers who report to them. In one qualitative study of health care managers in Bahrain and Saudi Arabia, senior managers prized strategic agility in this layer while frontline managers stressed interaction and communication.

Most physicians, one paper reports, prefer leaders from their own profession, and many earlier physician leaders reached their posts through clinical or research achievement. The trap is treating that depth as enough: nurse managers are often chosen for clinical expertise rather than management ability, and many report feeling inadequately prepared.

Legitimate, reward and coercive power are called positional because they come from occupying a role. Personal power, built from expertise and from respect and appreciation, adds influence a role cannot supply, and one paper reads the evidence as favoring person-based power. Flatter hierarchies shrink positional power further.

The bases differ in where they come from. Legitimate power is the formal authority of a position, reward and coercive power are the perceived ability to grant benefits or impose costs, expert power rests on knowledge, and referent power on an emotional bond with followers. Only the last two come from the person rather than the post.

Path-goal theory names four: directive, supportive, participative and achievement-oriented. Participative and supportive styles are often linked to staff well-being and engagement, yet in a survey of 337 Jordanian hospital nurses directive leadership was seen as dominant. A cross-sectional survey like that cannot show which style caused what.

The theory reinforced the field's move from traits to behavior by stressing that the right style depends on the situation. Its support is thin: critics argued that more than one behavior can work in the same situation, and interest in situational theories faded because empirical support was lacking, partly through weak measures and weak study designs.

A review of people management says leaders who adjust directive and supportive behavior to context get better results, though the situational theories behind that idea drew weak empirical support. Critics also argued that several behaviors can succeed in the same circumstances, so flexibility need not mean finding one correct style.

Its defining feature is service to followers and other stakeholders, which separates it from transformational leadership, where followers are mobilized toward the leader's vision. Its benefits are not uniform: an online experiment and a field study found leader gender changed how servant behavior was judged, mainly through perceived competence.

Its four behaviors are idealized influence, inspirational motivation, intellectual stimulation and individualized consideration, often measured with the Multifactor Leadership Questionnaire. Critics point to construct proliferation: new leadership styles keep appearing without being tested against older ones, and many overlap, so it is hard to tell what any one label adds.

It rests on contingent reward, clarifying expectations and rewarding goals met, and on active management by exception, which monitors performance for problems. One paper argues this exchange thrives in stable, structured settings and loses force as work changes quickly and hierarchies flatten, which is an argument rather than a settled finding.

In the full range model it belongs to the passive-avoidant style, marked by absent or delayed leadership action. Autonomy gives someone real choice over how to reach a goal; laissez-faire withholds needed guidance, and the authors of a meta-analysis on workplace safety argue that this creates dangerous role ambiguity.

Inaction is not neutral. In a paper combining an experiment with two multi-wave surveys, employees who felt their manager had failed to act on an aversive event they experienced, despite a duty to do so, rated that manager less trustworthy, pulled back support for them and reported lower well-being themselves.

One paper on workplace trust says managers foster it by making decisions openly, treating staff with respect and acting with consistent integrity. Trust research separates ability, benevolence and integrity as grounds for trust, and notes that trust is fragile: once damaged, it is difficult to repair.

OPM's guidance holds that involving employees in planning helps them understand the goals, what needs doing, why and how well. Its measurement handbook tells of a beekeeper who counted the flowers each bee visited but never shared the hive's honey goal, set against one who shared it and measured nectar and honey.

OPM treats leader onboarding as a process that can last up to a year or more, for promoted and transferred staff as well as new hires, and presents it as a way to prevent executive derailment. Early changes carry costs: in one study of local-government department heads, policy and culture change were named sources of anxiety during a change of leader.

A change of leader can be unsettling in itself. Interviews with 26 department heads in Indonesian local government traced their anxiety to policy change, culture change and fear of loss, and found it shaped whether people moved closer to the new leader, kept their distance or stayed ambivalent.

Promotion from within changes the work, the relationships and the scope of responsibility at once. Studies of nurses promoted from clinical posts report role ambiguity and role conflict as common early problems. Those studies describe the shift rather than test a way to handle it, so treat advice on resetting relationships as practice wisdom, not a finding.

The usual reasoning is that people get promoted for success in their current role rather than for the skills of the next one. A three-wave study of promoted employees read its findings as possible evidence for the principle, since the promoted may lack managerial skills. One medical-school chair's advice is to treat a new role as a learning curve, not one more success.

The federal government offers one model. Scientific and Professional positions sit above GS-15 for people doing research and development, and Senior-Level positions above GS-15 are classified on non-executive duties. A specialist can reach that level without taking on executive management.

Self-determination theory treats it as the most self-determined form of motivation, and one analysis found that satisfying basic needs worked as a necessary condition for it. The theory points managers away from installing interest and toward protecting the autonomy, competence and relatedness it grows from.

Self-determination theory places motivation on a continuum from amotivation, through behavior regulated by external or internal rewards and pressures, to reasons a person has internalized as their own. The more fully an extrinsic reason is internalized, the more it works like autonomous motivation.

Autonomy is acting by choice, competence is experiencing mastery, and relatedness is close, supportive connection. Satisfying the needs is linked to well-being and better motivation, while frustrating them is linked to controlled motivation and ill-being, which the theory calls its bright and dark pathways.

In self-determination theory, autonomy is met when people feel free to choose and see their behavior as self-endorsed rather than pressured. Autonomy differs from being left alone; OPM's planning guidance pairs clear goals with involving employees in co-creating their own performance plans.

The closest match in self-determination theory is the competence need, met when people feel capable and are building skills. OPM's guidance makes the practical link: recognize improvement and new skills, not only results, and celebrate progress as well as high performance.

A review of meaningful-work definitions separates broader purpose, work that serves a greater good, from self-realization, work that expresses who you are. In a study of 528 employees in Greece and Canada, perceived positive impact on others went with creativity and innovative behavior, partly through autonomy and competence.

It describes a reward weakening intrinsic motivation by loosening the link between an activity and its own goal. The finding is contested: one account holds that rewards undermine interest, another that the undermining can be avoided. Timing is a separate question: three experiments found an extra reward right after a task left interest stronger than a delayed one, comparing timing rather than reward against none.

Frederick Taylor's 1911 system, now a historical view, paired a defined task with a large bonus for meeting it. A recent review of people management is more guarded: well-calibrated incentives that fit social norms and individual differences can sustain engagement, while crowding out is most concerning in prosocial or creative tasks.

Poorly designed incentives can crowd out intrinsic motivation, especially in prosocial or creative work, where paying for an act can change what it means to the person. They also invite strategy: under the ratchet effect, workers hold back so that a strong result does not become next period's expectation.

OPM's summary of Locke and Latham's research reports that people given specific, hard goals outperformed people told to do their best. Goals direct attention, let people scale effort to the difficulty of a goal they have accepted and raise persistence, and in one study a goal set on one of five dimensions of the work improved that dimension only.

OPM's guidance stresses goals that are difficult but possible, and notes such goals can give people a sense of purpose. Groups can miss the mark both ways: rivalry with other groups can push members to set unrealistically high goals, and groups afraid of failing tend to pick very easy or very hard goals.

Built from interviews with engineers and accountants, it treats satisfaction and dissatisfaction as separate dimensions: hygiene factors such as salary and job security breed dissatisfaction when they fall short, while motivators build satisfaction. It is contested; one Saudi public-sector survey found extrinsic motivation predicted satisfaction more strongly than intrinsic, the reverse of the prediction.

Inadequate pay is a classic dissatisfier in this model, which remains contested. In a qualitative study of primary care physicians in Kazakhstan, salary was the dominant source of dissatisfaction and had to be fixed before other changes could be judged, while patient care, supportive colleagues and recognition sustained engagement.

The hierarchy says lower needs must be met before higher ones motivate. Maslow drew his picture of self-actualizers from friends, associates and historical figures he chose, and later research suggests people can be moved by higher needs before lower ones are met, and that which need comes first varies across cultures.

Vroom built the model on rational choice: people decide whether to act by judging how effort, performance and outcomes connect, through expectancy, instrumentality and valence. By that logic, a valued bonus does little for someone who thinks the target is out of reach, and a reachable target does little if nobody values the reward.

Adams proposed in the early 1960s that employees weigh what they put in, such as skill, effort and experience, against what they get, and compare that ratio with peers. People who perceive inequity may cut their effort, disengage or look for another job.

OPM advises recognizing people close to the time of the achievement, tailoring it to the individual and making the link to the accomplishment clear. Public praise suits some people and private thanks others, so OPM suggests asking what each person prefers; recognition also signals what the organization values.

One review defines meaningfulness as judging work significant and worth doing, with two parts: serving a broader purpose beyond yourself and realizing yourself through the work. Earlier definitions usually captured only one or two of these elements, and that ambiguity has slowed research.

Crafting is self-initiated rather than directed by management and takes three forms: changing tasks, changing relationships and reframing what the work means. In a study of South African small-business employees, cognitive crafting most consistently separated groups with different levels of need satisfaction.

The World Health Organization classifies it as an occupational phenomenon caused by chronic workplace stress that has not been managed. Theories trace it to a lasting imbalance of high demands with too few resources and too little recovery, and one review of intensive programs suggests cynicism may need organizational change or follow-up support, not just time away.

In this model, excessive demands drive an energy-depletion process seen mainly as emotional exhaustion, while missing resources drive a motivational withdrawal seen as depersonalization. Cutting demands targets the first and adding resources targets the second. Both sit inside burnout: the WHO lists disengagement among its dimensions, so these are not two separate conditions.

Burnout models trace exhaustion to job demands that chronically exceed the resources available to meet them. Managers shape that balance through what they assign and what they let wait, and OPM's goal-setting guidance asks that several goals be ranked so employees know which matters most.

GAO's 2015 review of the federal engagement index found that a government-wide decline hid the fact that most agencies held steady or improved, because a few large agencies pulled the average down. GAO also faulted OPM for not reporting whether yearly changes were statistically significant or random.

In GAO's analysis of federal survey data, career development and training was the second-strongest driver of engagement after constructive performance conversations. In interviews with nine female engineers in South Africa, views of pay fairness and career growth were tied to thoughts of staying or leaving.

They are commonly viewed as a tool for finding the causes of turnover, yet one paper on clinical training in England and Wales calls them far from commonplace. Named barriers are the time they take and the power gradient between interviewer and leaver, and by design they hear only from people already on their way out.

In nursing, delegation lets nurses focus on complex tasks while others take work matched to their competence, and one Turkish study linked strong delegation and supervision skills to higher job satisfaction and lower stress. OPM also counts assignments that bring new skills or more responsibility as a way to develop people.

In nursing's definition, delegation transfers responsibility for doing a task while the delegator keeps accountability for the outcome. OPM's playbook makes both agency leaders and supervisors responsible for swift action on poor performance, with a set sequence: communicate the expectations and the problem, give a chance to improve, then act.

Delegation is not one thing. One measure of empowering leadership lists delegation of authority and self-directed decision making as separate behaviors, and in nursing's definition the person delegating stays answerable for the outcome, so it helps to say exactly what you are handing over.

Nursing delegation is meant to follow competence, with supervisors assessing the skills of the people they delegate to. More autonomy is not always welcome: a study of Generation Z knowledge workers found empowering leadership raised perceived support but also emotional exhaustion, especially for people with an avoidance goal orientation.

OPM's measurement handbook says the difference between activities and accomplishments may be its most important idea: activities are what people do, while accomplishments are the products or services that result. Framing a delegated task as an accomplishment leaves the person room to choose the method.

A narrative review from health care defines it as overly detailed supervision that shrinks room for independent professional judgment. Reported consequences include occupational stress, lower productivity, poorer care quality and higher turnover, though the authors note most studies examined related ideas rather than micromanagement itself.

Delegation passes on the doing, not the accountability, so a manager who hands off a task and disappears still owns the outcome. A scoping review of nursing supervision in Africa treats support, guidance and available supervisors as fundamental to delegated work going well.

OPM recommends check-ins at least quarterly, and preferably monthly, to track goals and catch problems early. The form matters too: in a survey of 299 remote employees, conversation-based monitoring went with higher engagement and less deviant behavior, while electronic monitoring went with more deviant behavior.

A RACI matrix is one way: for each task it records who has authority and who must be consulted, which streamlines decisions by settling those questions up front. In one survey of research teams, setting clear expectations and holding each other to tasks and deadlines were named as common struggles.

Responsible people help do the work, one person owns completion, consulted people provide input, and informed people hear about progress without contributing. Building a matrix starts from a list of specific tasks, and making ownership explicit task by task avoids role confusion.

RACI guidance limits the “A” label to one person per task, the one ultimately responsible for seeing it completed, to avoid confusion. Others can share the doing as responsible contributors; what should not be split is the question of who makes sure the task finishes.

Philosophers writing on collective responsibility separate backward-looking responsibility, about blameworthiness for harm, from forward-looking or remedial responsibility, about what someone can be expected to do to fix a harm and prevent it recurring. Just culture, from patient safety, balances accountability with learning, separating human mistakes, at-risk behavior and reckless acts.

Edmondson crosses the two in a grid: high safety with high accountability is the learning zone, high safety with low accountability the comfort zone, low safety with high accountability the anxiety zone, and low on both the apathy zone. One recent paper extends the model, arguing that low accountability weakens the self-regulation that being evaluated normally provides.

One strategy paper lists objectives and key results, like the balanced scorecard, among tools that turn intentions into measurable objectives and keep goals aligned. In an interview study at one private hospital, a frontline nurse manager described setting OKRs with colleagues at the start of each year so the goals felt like their own.

OPM's supervisor roadmap describes KPIs as indicators that reflect success, tracked against benchmarks or past data and mixing quantitative measures with qualitative ones such as customer satisfaction. Objectives and key results, by contrast, pair a stated goal with results that show progress, and are used to align goals and make execution measurable.

OPM's example turns a goal to improve reporting accuracy into a goal to cut reporting errors by a set percentage within a set number of months. OPM pairs SMART with revisiting goals at check-ins and adjusting them when needs change, so a well-formed goal is not frozen.

OPM's handbook defines outputs as the products or services of work, such as a complete and accurate report, and outcomes as the final results, which outside factors can also affect. Because annual plans cover a single year, their goals tend to be output-oriented steps toward longer-term outcome goals.

OPM recommends cascading goals from executives to frontline staff so each objective ties to the mission, the strategic plan and operational priorities, with clarity about how success is measured. Cascading is not the same as dictating: OPM also asks managers to collaborate with employees when setting goals and to promote shared ownership of outcomes.

Campbell, a social scientist, saw people exploit metrics once the metrics were in use, and Goodhart, an economist, saw inference about a system break down when its rules changed. One remedy is several imperfect measures that pull in different directions, which makes gaming any one of them harder.

In a 1911 account now read as history, Frederick Taylor claimed workers deliberately worked slowly to keep employers from learning how fast work could be done, especially after piece rates had been cut. The modern ratchet effect describes a similar move, and metric designers recommend diverse, disaggregated measures to blunt it.

OPM's supervisor roadmap tells managers to distinguish predictive, leading indicators from result-based, lagging ones when they set KPIs. Lagging figures confirm what happened. The roadmap separately asks managers to use monitoring data to catch early warning signs of underperformance while there is time to act.

OPM's goal-setting guidance asks that several goals be ranked by importance and that employees know and agree to the ranking. Without an explicit order, urgency decides by default: nurse managers short of time in one study finished urgent daily tasks while other duties went undone.

OPM wants performance plans to be working documents discussed often, not paperwork filed away until ratings are due. Its supervisor roadmap pairs that with dashboards and analytics meant to surface trends, gaps and outliers, so that tracking gives a manager something to act on.

Research teams surveyed at one university named holding each other accountable to tasks and deadlines among their main struggles. Managers are judged the same way: employees who saw a manager fail to act when the manager had a duty to were less likely to see that manager as trustworthy.

In one study summarized by OPM, feedback alone during appraisals did not improve performance, while feedback followed by goal setting did. Feedback earns its keep by ending in a next step; one model frames it as three questions: where am I going, how am I going and where to next.

Clinical-education guidance asks for feedback based on direct observation, given in a timely way and specific enough to act on. OPM's playbook says the same to supervisors: give immediate, actionable feedback when a task is done, whether something went wrong or beat expectations.

The structure keeps feedback to what was actually observed. Medical-education guidance describes effective delivery the same way: describe a specific observed behavior, name its impact and suggest how to improve, which leaves little room for judgments about character.

Guidance on constructive feedback asks that it be descriptive, non-judgmental and based on observed behavior. Criticism heard as an attack on self-worth is a known barrier to feedback being taken in, while a described behavior is something the person can actually change.

Praise first and last is meant to make criticism easier to hear and protect self-esteem. A review of feedback models calls it one-way and educator-centered, yet one randomized comparison with 69 dental students found no overall difference from an ask-tell-ask approach, with three rating items favoring the sandwich.

Work on clinical training suggests that feedback is shaped by shared goals and the quality of the relationship, not by information delivery alone. One medical-education review also lists suspected bias or ill intent and inconsistent standards among the barriers to taking feedback in.

Tone carries its own message. In one vignette experiment with 148 undergraduates, disrespectful feedback from a professor produced stronger negative emotions, lower trust and less willingness to take part in class, and the authors note people may comply outwardly while withdrawing.

OPM guidance calls for recognition with a clear connection between the accomplishment and the praise, and for acknowledging effort, improvement and collaboration, not just outcomes. Naming exactly what worked tells the person what to do again and shows what the organization values.

OPM's roadmap tells supervisors not to rely on annual reviews alone and to hold check-ins monthly or at least quarterly, with reinforcing as well as corrective feedback. In GAO's analysis of federal survey data, constructive performance conversations were the strongest driver of employee engagement.

Whether feedback changes anything depends partly on feedback literacy, the recipient's skill at turning it into action. Defensiveness and emotion are natural reactions to criticism; suggested counters include noticing those reactions and reframing feedback by its intent instead of taking it personally.

One-way, top-down feedback is a known barrier, and OPM's roadmap tells supervisors to encourage two-way feedback and include input from subordinates. Safety is the condition: a case study of a Saudi multinational traced how retaliation through appraisals made speaking up feel unsafe, so concerns went unspoken.

Directive coaching does more of the leading, while non-directive coaching helps the other person lead. Non-directive practice is widely treated as the standard, but the question is debated: one study of a goal-focused coaching chatbot found tentative evidence for the directive version, in what its authors call a very specific context.

Handing over control is not always welcome. One study notes empowering leadership can backfire where employees prefer directive leadership, raising emotional exhaustion for some, and a coaching-chatbot study found that structure, clarity and supplied ideas made coaching more useful to its participants, at least in that setting.

Developed by Whitmore, it asks the person to set a goal, assess the current situation, generate options and commit to action. In a study that added GROW-based coaching to new nurses' orientation, performance scores rose, but turnover intention and organizational commitment did not differ from the control group.

OPM's guidance on performance talks suggests asking what someone has accomplished, how they measured it, what they want to achieve next and how you can help. Open questions like these draw people into assessing their own performance instead of receiving a verdict.

OPM's roadmap tells supervisors to schedule regular one-on-ones and to hold development-focused check-ins apart from performance reviews. OPM also advises that these talks look ahead to what could be, not only back at what happened, with the employee taking part in assessing and planning.

OPM's roadmap schedules development-focused check-ins separately from performance reviews, so growth gets its own time. At one agency studied by GAO, supervisors and employees developed a set of topics for quarterly conversations, to make feedback and coaching consistent and regular rather than left to chance.

OPM's roadmap suggests using planning time to discuss career aspirations and scheduling development-focused check-ins separately from performance reviews. It ties those aspirations to individual development plans that cover both short-term skills and long-term career goals.

OPM ties individual development plans to observed performance and asks managers to link feedback to a specific action, such as leading a given meeting to build presentation skills, instead of generic advice. It counts stretch assignments, coaching and on-the-job learning alongside formal courses.

OPM's sequence for poor performance starts by stating the expectations and the specific problem before offering a chance to improve. Expect a reaction: defensiveness and emotion are natural responses to corrective feedback, so the facts should be observed behavior and its impact, not conclusions about the person.

OPM tells supervisors to document key discussion points for transparency and keep records of goals, feedback and coaching, so ratings reflect earlier feedback and bring no surprises. Appraisal can also be misused: a case study of a Saudi multinational described performance appraisal used as a tool of control, which made employees afraid to speak.

OPM guidance starts with root causes, such as skill gaps, motivation or a poor fit with the role, then offers support through training, mentoring or reassignment. It warns against passing struggling employees from job to job and expects administrative action if performance stays unacceptable.

In OPM's guidance for federal agencies, a plan addresses unacceptable performance on one or more critical elements, with clear goals and timelines, inside a three-step sequence: state the expectations and the problem, give an opportunity to improve, then act. Other employers follow their own rules.

Mentorship emphasizes guidance and support, while sponsorship means active advocacy, brokering opportunities and promoting someone's career. Evidence links sponsorship to faster promotion and visibility, but one commentary notes it is not essential to success and may pass over people who differ from the dominant culture.

A job analysis comes first: it lists the tasks and responsibilities, the competencies needed to perform them, and which of those must be present on day one rather than learned on the job. Interviewers who skip this and do not really know the job tend to form a private opinion of the best candidate and judge everyone against it.

A scorecard fixes, before anyone meets a candidate, the few competencies the interview will measure and what weak, adequate and strong answers look like for each. A structured interview usually covers four to six competencies. Interviewers who do not understand what the job requires tend to judge every candidate against a private impression of the ideal hire instead.

Three things make an interview structured: every candidate gets the same questions in the same order, every answer is scored on a common rating scale, and interviewers agree in advance on what an acceptable answer looks like. A conversation that only reuses a question list but never rates the answers sits somewhere between structured and unstructured.

Unstructured interviews show low reliability, meaning two interviewers often rate the same candidate differently, and only low to moderate validity for predicting job performance. Their loose, conversational format is what makes them look attractive, and it is also what makes them subjective and harder to defend if a hiring decision is challenged.

A behavioral question asks what a candidate actually did in a past situation, on the premise that past behavior under similar circumstances predicts future behavior. Words like most, last or worst push the answer toward one specific incident, so you hear the situation, the actions taken and the result rather than a general self-description.

A situational question describes a realistic job scenario or dilemma and asks how the candidate would handle it, on the premise that intentions are closely tied to behavior. Scenarios are typically built from critical incidents that people in the job have actually faced, and answers are scored against sample responses agreed for each proficiency level.

A work sample has candidates perform tasks that mirror the job, so it shows both strong content validity and a strong link to later job performance, and applicants tend to see it as fair. It is costly to build and run, so it pays most when a competency is critical at entry; if the skill can be learned on the job, the return drops sharply.

On a panel, each interviewer reviews notes and rates the candidate alone, before any discussion, so every rating is an independent evaluation. Only then do panelists compare ratings, explore the reasons for discrepancies and settle on a consensus score backed by what the candidate said. Using a panel this way also reduces the risk of bias in ratings.

Calibration means interviewers share the same picture of what each rating level looks like. Subject matter experts write example answers for every level, interviewers are trained on them, and the same interviewers rate all candidates where possible. Without that shared anchor, a 4 from a lenient rater and a 4 from a strict one mean different things.

Interviewers tend to make up their minds about a candidate within the first few minutes, on very little information. The remedy is procedural: reserve judgment until enough has been gathered, rate from your notes, and keep resumes out of the interview itself, since a strong resume can tilt how the same answers are rated.

Similar-to-me bias gives higher ratings to candidates who seem like the interviewer in background, manner or interests. People naturally prefer others who resemble them, so it rarely feels like bias. Scoring the answers against defined anchors rather than outward characteristics counters it, and a panel with a range of interviewers also reduces the risk.

The halo effect lets a rating on one competency spill into the others, so a polished speaker also gets credit for problem solving the answers never showed. It is the same error in performance reviews, where expertise in one area is assumed to carry to another. Rating each competency separately against its own anchors is the check.

Validated personality measures can predict job performance, though less well than work samples or cognitive tests, and work best as several trait scales. Type instruments are criticized for forcing continuous traits into either-or categories and for weak retest stability: in one older study only 47% kept the same type over five weeks. Defenders point to other studies with acceptable reliability.

A reference check verifies what a candidate claimed and asks former supervisors and peers how they actually performed. It predicts performance better than years of education or experience, though not as well as cognitive tests, and adding structure (job-based questions, the same set for every candidate) improves it. It is usually done late, on a short list.

Candidates judge an organization by how its process treats them. Giving a realistic picture of both the good and bad parts of the job, a clear timeline and a definite date to hear back helps applicants decide whether they fit. Honest previews are linked to fewer surprises on the job and to seeing the employer as honest, and they can reduce turnover.

Who gets hired depends on who applied, so a narrow sourcing channel limits every later step. Relying on word-of-mouth referrals from a workforce that is largely one group can reproduce that group, and the EEOC gives this as an example of recruitment that may violate the law. Widening where you advertise changes the pool before any interview. This is general US information, not legal advice.

Pre-employment questions should stick to what shows whether someone is qualified. Asking about disability before an offer is explicitly prohibited. Questions that reveal race, religion, national origin, age or sex are not always outright banned, but they can be used as evidence of intent to discriminate. This describes general US rules for study, not legal advice.

Federal guidance treats onboarding as a sequence that starts before the first day: paperwork and equipment ready in advance, a sponsor assigned, a meaningful first assignment in the first week, and a talk about performance standards with feedback by day 30. The plan continues through the first year, with an informal review after about 90 days and a decision at the end of probation.

A probationary period is the final stage of the hiring assessment, because it tests actual performance on the job. In a federal survey reported in 2005, more than half of supervisors who would not select their probationer again still expected to keep that person. Restarting a long hiring process is an unwelcome prospect, but a poor performer kept past probation is likely to stay for years.

A performance system is often asked to do three jobs: give candid feedback to help someone grow, inform rewards for top performers, and document poor performance so it can be addressed. Because those jobs pull in different directions, federal guidance suggests holding development-focused check-ins separately from performance reviews.

Recency bias lets the most recent weeks dominate a rating that should cover the whole period, so a strong spring vanishes behind a rough autumn. Federal guidance names it alongside the halo effect and favoritism as a bias managers should be trained to catch. The practical defense is keeping records of accomplishments and feedback throughout the year.

Central tendency is rating everyone in the middle of the scale. A high rating does not mean perfection, only more of the competency than usual, and a low one does not mean its absence. Some managers also rate a whole team the same to spare conflict or spread awards; that blurs the line between average and better than average, so the signal is lost.

Forced ranking caps how many people may receive each rating. It does push managers to make distinctions, but a 2006 federal review argued that real performance rarely follows a bell curve: when many people excel, supervisors make arbitrary cuts or rotate top ratings, and colleagues ranked against each other may cooperate less. That is not current policy: OPM's July 2026 manual plans governmentwide rating distribution caps.

In a calibration session, managers review preliminary ratings side by side against shared standards, so a strict rater and a lenient one apply the same yardstick. Federal guidance lists consistency, equitable treatment and reducing unintended inflation among its aims, and says it does not replace the supervisor's judgment. Every adjustment should rest on documented evidence.

Pay transparency has three layers: how the pay system works, what each person must do to earn a reward, and how open the organization is about actual outcomes. Understanding the basis for pay decisions supports perceptions of fairness. Some organizations publish anonymous aggregate results; naming individual amounts is far rarer and can breed jealousy when peers cannot judge each other's work.

Psychological safety is a team's shared belief that it is safe to take interpersonal risks: to ask a question, admit a mistake or challenge the status quo. It belongs to the group rather than to one person's confidence, and it tends to grow as members first trust the leader and then extend that trust to one another. How much it helps performance is debated and may depend on conditions.

Safety lowers the social cost of speaking, but it does not lower the bar for the work. A recent theoretical model proposes that very high safety, where accountability is weak, can bring process losses, and it cites one study in which moderate levels performed best on routine tasks. These ideas are still being tested; the pairing they argue for is candor plus clear standards and follow-through.

Leaders build safety through visible behavior. In interviews, research-team leaders described modeling humility, asking for input from junior members, and responding to a missed deadline by asking what led to it rather than assigning blame. Leaders who share their own missteps make risk-taking easier for others, while status and hierarchy that go unexamined can silence people.

A lack of bad news is weak evidence that nothing is wrong. Raising a concern carries an interpersonal cost, especially when pressing it upward, and status, hierarchy and power can silence people who do have a problem to report. Research also treats silence and speaking up as separate behaviors, so treat a meeting with no objections as a question to investigate, not as agreement.

One company's internal study of its own teams named five features its successful teams shared: psychological safety, dependability, structure and clarity, meaning, and impact, with safety ranked first. It describes that company's teams rather than proving a recipe, so use it as a checklist of things to look at, not as a formula that guarantees results.

Tuckman's model gives names to the stages a team passes through as it develops, from first assembling, through a period of conflict over roles, to working cohesively toward its goals. It is a descriptive model rather than a timetable, and friction over roles can return even in a team that is performing well. Its practical value is giving a team shared words for where it is.

Storming is the stage when members sort out roles, and it can bring conflict and competition for roles and attention. That is an expected part of team development, not proof the team is failing. Recognizing each member's strengths and assigning roles to fit them, with a leader stepping in if competition starts to block the work, helps a team move toward cohesion.

Norms are explicit agreements on how the team works: how discussions run and decisions get made, what behavior is expected in meetings, and when to send a message versus when to call. Agreeing on them early and writing them down gives everyone the same reference point when friction appears, instead of each person arguing from private preference.

Groupthink, as Janis described it, is thinking in a cohesive group where the drive for unanimity overrides realistic appraisal of alternatives. He linked it to strong loyalty, stress, insulation from outside experts and the absence of methods for testing critical information. Cohesion is the precondition, so a close, friendly team is not automatically immune.

The counters are structural rather than exhortations to think harder. Designate someone to build the strongest case against the prevailing view, bring in an outsider who does not share the group's background, and collect ideas before the discussion converges. A long-settled consensus is exactly when a deliberate challenge is most worth the effort.

Social loafing is the drop in individual effort when people work as a group rather than alone. It is strongest when individual contributions cannot be identified or evaluated, when the task seems low in value, when a partner is performing well and when members' inputs are redundant. It shows up even in pairs, not only in large groups.

Because loafing grows when no one can see who did what, the remedies make contribution visible: give each person a distinct, identifiable piece of the work, make clear that individual contributions will be evaluated, and avoid splitting work so that members' inputs are redundant. Each of these targets one of the conditions under which effort drops.

In classic bystander research, people were less likely to help when others were present, partly because responsibility felt spread across everyone. The same pattern is described in organizations when many people see a problem and each assumes someone else will act. Later work finds the effect of others' presence varies by situation and is less clear-cut, so treat it as a tendency.

Unclear roles are a common and fixable source of friction. When responsibilities are left undefined, members may end up vying for roles and attention, and that competition can become a barrier to the team's work. Giving each person a distinct role with clear expectations and purpose, and returning to roles when new ambiguity appears, removes the cause rather than the symptom.

Diversity's effect on a team is not fixed; it depends on how differences play out. One account holds that visible differences lead people to sort into in-groups and out-groups, which can breed friction. In one study of hospital teams, more diverse teams reported more task conflict, and trust among members weakened that link, so building trust is part of making diversity work.

Diversity describes who is present; inclusion describes whether each person belongs and can actually contribute. The term has no single agreed definition, but one framework pairs a sense of belonging with the opportunity to participate and contribute meaningfully. That is why counting heads alone cannot show it: a varied team can still leave some members unheard.

Remote teams communicate with fewer face-to-face interactions, which makes reactions and body language harder to read, and trust develops more slowly on purely virtual teams. The replacement is deliberate: agreed rules for when to write and when to call, regular meetings with set agendas, cameras on where possible, and some chances to connect in person.

When writing carries the coordination, its weaknesses matter. Electronic messages lose tone, recipients tend to read them more negatively than intended, and writers overestimate how clear their priorities are. State your intention up front, highlight the key point and reread for tone. Agree as a team when a message should be written and when a call is better.

Proximity bias treats physical presence as evidence of output. A 2011 federal telework guide, since replaced, warned managers against handing out work by who is physically there and against assuming that someone present and looking busy accomplishes more than someone off-site. Current federal guidance still requires the same performance standards for remote and in-person staff in the same job.

Short recurring structures carry information a team would otherwise lose. A brief before work shares the plan, roles and likely contingencies; a huddle mid-stream rechecks the plan; a debrief afterward asks whether communication was clear, workload fair and errors avoided. Because they recur, they keep reinforcing shared goals and make review a habit, not an event.

A newcomer joins a team, not only an organization. Telling current staff about the person's role before they arrive, introducing them on day one, pairing them with a sponsor, and making time for them to talk with colleagues about how they will work together turns belonging into a planned step instead of something left to chance.

Healthy teams are not free of conflict. Members offer alternative views openly and respectfully while a question is open, raise concerns directly instead of letting them grow, then commit to an outcome they can live with and follow through on it consistently. A team where nobody ever disagrees may be staying silent rather than agreeing.

Before deciding a person is the problem, look for the root cause. Federal guidance on poor performance names skill gaps, motivation and a mismatch with the role, and team-level causes such as undefined roles can leave members competing for position. Training fixes a skill gap but not an unclear role, so the diagnosis decides the response.

Before a discussion starts, settle who decides and by what rule: the leader alone, the leader after consultation, a vote, or consensus, and if consensus, what counts as agreement. Groups that agree on these rules first, and then apply them, can spend their energy on the substance instead of arguing about the process midway.

Decision modes sit on a range of shared power. At one end the leader decides alone; next comes consultation, where people are asked for ideas before the leader decides; then shared decision-making; and at the far end, delegation to the team. Consulting can strengthen people's sense of control over their work, but only if their input is genuinely heard.

No mode is best everywhere. In a scenario experiment and a field survey, both with firefighters, followers trusted a leader more when the leader decided alone during urgent action, and more when the leader shared decisions in the calmer phases between actions. The findings come from emergency teams, but they suggest the right mode can change within one team as conditions change.

Consensus does not have to mean everyone enthusiastically agrees. A group can set its bar as everyone being able to live with the outcome, as everyone actively supporting it, or somewhere in between. Agreeing on that bar in advance means everyone knows in advance what their assent commits them to.

Disagree and commit means you argue fully while a decision is open and then carry it out once it is made, even if your view lost. The bar is whether you can live with the outcome, not whether you would have chosen it. It works best when the group agreed in advance that being able to live with a decision counts as agreeing to it.

When a choice can be undone cheaply, a quick decision followed by feedback can teach you more than extended deliberation. Delivery in small steps applies the same idea: federal digital-service guidance calls for getting a working version to users early and adjusting based on their feedback, to reduce the risk of failure. Save heavy deliberation for choices you cannot walk back.

Some choices cannot be walked back, and for those the cost of being wrong is worth extra time. That is where deliberate challenge earns its effort: assigning someone to build the best case against the prevailing view or testing key assumptions. These methods are aimed at issues a group cannot afford to get wrong, not at every routine call.

A useful decision record captures not only what was decided but why, including which views were weighed and how they were combined. Keeping it in a shared place everyone can reach makes the reasoning visible and retrievable later, so a future team can judge whether the original grounds still hold before reopening the question.

Decide in advance how an unresolved concern moves up. Patient-safety team training uses a two-challenge rule: voice a serious concern at least twice so it is clearly heard, and the person challenged must acknowledge it; if it still is not addressed, take stronger action or go to a supervisor or the chain of command. A route agreed beforehand does not have to be invented under pressure.

In a premortem, the team assumes the project has already failed badly and generates plausible reasons why, before committing. Members typically write their reasons separately before the leader collects them, which keeps one view from shaping the rest. It focuses on risks to avoid; it does not by itself pick a strategy.

Two related checks are often blurred. Devil's advocacy builds the strongest case against a group's consensus to expose weak logic or untested assumptions. Red teaming instead models how an opponent would think, to avoid assuming others share your values and reasoning. Both aim to break a settled mindset, and a manager can assign someone to the role.

Anchoring is adjusting only in small steps from a starting point, even when new information calls for a bigger move. Judgments can also stay anchored to weak information long after the caveats are forgotten. In a group, collecting each person's estimate or proposal before discussion keeps a single opening figure from becoming everyone's starting point.

A group discussion lets people build on each other's ideas, but individuals working alone can produce a wider range of ideas, free of others' egos and objections. Asking each person to write down views first, then pooling them, keeps both benefits. Group decisions tend to work best when the group is diverse and people can express views anonymously.

Team conflict is often split into three kinds. Task conflict is disagreement about the work itself; process conflict is about who should do what, and how and when; relationship conflict is personal irritation or hostility. They behave differently: studies tie process and relationship conflict to weaker performance or creativity, while findings on task conflict are mixed, so name the kind first.

Disagreement about how to do the work can help a team under some conditions, by making people see the task from more than one angle. The evidence is mixed, though: meta-analyses have linked both task and relationship conflict to lower team effectiveness, and task conflict can turn into relationship conflict over time. Keeping debate on the work, not the person, protects the benefit.

Relationship conflict, the personal friction of resentment, annoyance and animosity, is more strongly tied than task conflict to lower team effectiveness in meta-analyses. It can lead members to withhold effort or distance themselves from the team. Because disagreements about the work can harden into personal conflict over time, the aim is early attention, before positions become personal.

Positions are what people say they want; interests are the needs behind them. An interest-based approach asks what each side actually needs and looks for a mutually acceptable solution that meets the interests that matter most, rather than splitting the difference between stated demands. Two people demanding the same resource may each be satisfied once the real need is clear.

When two of your reports clash, a facilitative stance borrows from mediation: you offer no verdict on whose position is stronger and instead help them communicate clearly, listen carefully and work out an agreement both can accept. Unlike a true mediator, you also hold authority over the work, so they should know when you will step in and decide.

Mediation relies on parties who take part voluntarily and can withdraw at any time, and a mediator has no power to decide. A manager is different. When a dispute turns on something only you control, such as who owns a resource or a role, or when the people involved cannot reach an agreement, the decision falls to you, and it should come with stated reasons.

A meeting can share information, report status, coordinate, plan, solve a problem, generate ideas, make a decision or assign follow-up. Naming which one in advance tells people how to prepare. A standing meeting whose purpose the team cannot state tends to slide into passive reporting rather than the active problem solving meetings are best at.

An agenda circulated in advance does more than organize time: it tells people what to think about and signals why they are there. Vague agendas, poor timekeeping and off-topic digressions can actively erode trust. Phrasing items as questions to answer, not topics to cover, shifts a meeting from passive reporting toward problem solving.

Facilitation manages who speaks so expertise surfaces instead of rank or volume. Calling on people who have not yet spoken, including remote members in a hybrid meeting, makes participation more even, and even participation helps people feel safe to contribute. Equal airtime is not always the goal, though; when expertise is unevenly spread, the right person needs room.

Before a meeting ends, confirm what was decided, who owns each follow-up and by when. Recording why a decision was made, not only what it was, keeps the outcome usable for people who were not there and makes the reasoning easy to find later. Assigning follow-up is itself one of the core jobs a meeting does.

Ask what each standing meeting is specifically for; if the team cannot answer, the meeting is a candidate to cut, merge or redesign. A poorly designed meeting is not neutral: vague agendas, poor timekeeping and off-topic digressions can actively erode trust, so a recurring meeting that has lost its reason costs more than the hours it takes.

Large changes often stumble on people and culture rather than on the plan. A federal report drawing on a forum about major mergers noted that many mergers fail because the cultures of the combining groups were not fully understood, and that productivity tends to dip right after a merger. It puts people at the center of any serious change effort, not structure alone.

People cooperate with a change more readily when they understand why it is needed. A clear, consistent rationale also helps them see the expected outcomes and take ownership of them. Framing the goal as success rather than mere survival matters: a picture of what will be better is more motivating than a warning about what will go wrong.

A change needs visible backing from top leaders, but they cannot run it alone. A dedicated implementation team, staffed with high performers and supported by networks across the organization, manages the day-to-day work of the transformation. Leaders supply the authority, a consistent message and attention; the team supplies the capacity.

A transformation needs a coherent mission and a short set of priorities that guide decisions, plus a clear picture of how the future will be different from and better than the past. Defining what will count as success after the change gives people something to aim for and a way to judge whether trade-offs along the way serve that goal.

Communicate early and often, keep the message consistent and make it two-way, so concerns reach leaders and answers come back. Even when details cannot be shared, say when they will be and respond to rumors. Communication takes more time than planned; one participant in a federal forum put it at twice the original estimate.

If performance plans, ratings and rewards still measure the former priorities, they work against a new direction. A performance system can instead be aligned with the change, setting expectations for each person's role in it and rewarding competencies such as collaboration and information sharing, so the incentives and the announcement point the same way.

A long change needs visible progress early. Publishing implementation goals and a timeline, then reporting results against them, builds momentum and keeps people engaged when the full payoff is years away. Tracking goals also exposes shortfalls in time to correct course, which matters as much as celebrating what went right.

A change holds when it is built into how the organization runs: core values embedded in every part of operations, and a performance system that sets expectations for each person's role in the change and rewards the competencies it needs. Cultural change takes time, so these mechanisms have to keep working through leadership transitions.

A review of nursing studies traced resistance partly to organizational causes: too little support and resources, no involvement in the change, poor training and guidance, the speed of change and weak communication. Treating every objection as attitude misses those signals, and asking what lies behind it is often how a plan gets fixed. A small group, though, may resist any change.

Change fatigue comes from frequent, continuous change rather than from ordinary workload. As changes keep coming, people's capacity and enthusiasm for adapting declines, and the result can look like disengagement or burnout. How often change arrives, how it is communicated and how much support people get all affect whether fatigue sets in.

Even a welcome change costs people something: a familiar place in the organization, or confidence that their skills will still be valued. Employees unsure of their place may be unsure how to do their daily work, and productivity can dip. Surveys, focus groups and interviews can surface those fears early, so leaders can answer them directly.

Trying a change with a small group first exposes problems while they are cheap to fix. In one federal example, a new executive compensation plan ran for a year with the top executives before it was extended to all senior executives. Delivering in small steps follows the same logic: a working first version that real users can react to reduces the risk of a costly failure at full scale.

Organizing by profession or function keeps specialists in their own lines, which supports profession-specific standards and oversight. The cost appears in work that crosses functions, which then has to be integrated across those separate lines. Studies of hospital governance describe this tension, integration against profession-specific oversight, as a recurring design trade-off.

Organizing around a product, service or region gives one unit ownership of an outcome and lets it respond locally. The cost is that specialists end up spread across units, where they can feel isolated, and without explicit arrangements professional oversight and standards can erode. The trade-off mirrors the functional structure's, and matrix designs try to combine the two.

A matrix gives people two reporting lines, often a professional line and a unit or project line, to combine expertise with integrated delivery. It is chosen for flexibility and cross-discipline coordination, but dual reporting can blur accountability, budget control and roles, and some groups end up isolated or overlooked unless governance is explicit.

Centralizing decisions buys consistency, control and shared standards; decentralizing buys local responsiveness. Neither is free: moving decisions down to regions or units can erode common oversight unless explicit governance mechanisms keep it in place. Any structure picks a point on this trade-off, and the costs show up where it was not designed for.

A reorganization costs output before it returns anything. Productivity and effectiveness tend to decline right after a merger, as attention shifts to integration and people worry about their place. So the expected gain has to justify that dip, and leaders need to keep core services running while the change is underway.

Research on influence tactics separates soft ones, such as rational persuasion, consultation, collaboration and inspirational appeals, from hard ones such as pressure; in studies of school leaders, hard tactics won short-term compliance but often cost morale. Without rank, your leverage is what others depend on you for, and even staff hold some over their own managers.

A common stakeholder map places each party by power (ability to influence the decision) and interest (how much they care). High-power, high-interest parties need the closest engagement. The map is a snapshot: positions shift as roles change, and the same party can move quadrants when it takes on a new role, so revisit it as the work goes on.

Influence runs upward too. One theoretical framework argues that managers depend on their staff for knowledge, skills and results, so the dependence is two-way and gives employees real leverage. Managing up means supplying what your manager depends on, including information only you hold, rather than assuming influence flows only downward.

Credibility rests on delivery. In one study of supervisor and employee pairs, employees' political skill built stronger relationships with their supervisors when their task performance was high, and the authors argue that skill without results gets read as manipulation. Reliably meeting commitments is what gives persuasion its weight.

Political skill means reading people accurately, adapting how you influence them, building networks and coming across as sincere. It is not the same as manipulation, though researchers argue it can be read that way when it is not backed by solid work. Understanding who wants what lets you navigate an organization without either ignoring interests or exploiting them.

Ethical leadership is commonly defined as appropriate conduct in your own behavior and relationships, reinforced through communication. In interviews with health and social care leaders, trust and respect supported consistent ethical action, while top-down structures that left leaders out of decisions made it harder to act on shared values. Consistency between words and decisions is the test.

Some popular ideas about performance and leadership are actively debated. Critics argue grit is largely conscientiousness under a new name; one facet-level study found its perseverance facet nearly interchangeable with an existing trait, while its consistency-of-interest facet was distinct. Leadership styles such as transformational overlap heavily in measurement, so treat such claims as open questions.