Professional & Work

Why: Your manager is almost certainly not thinking about your pay as often as you are. They have a budget, an approval process and probably a cycle, and when you raise it they usually have to go and argue your case to someone else. What they need from you is a case they can carry: evidence of what you've delivered, a figure grounded in the market, a sense of what you'll contribute next, and a sign that you'll stay committed whatever the answer is today. That is why the question that works best is a collaborative one. "What would need to change?" gives them a problem to solve with you rather than a demand to refuse. In a study of Carnegie Mellon master's graduates, reported in Women Don't Ask (2003), Linda Babcock found that those who negotiated their first job offer raised their starting salary by 7.4% on average, and because later rises usually build on that figure, the effect compounds. But later experiments with Hannah Riley Bowles and Lei Lai (2007) found that evaluators were often less keen to work with people who negotiated, and penalised women for it more than men. So how you ask matters as well as whether you ask, which is why the Career Advancement module's VALUE framework treats it as joint problem-solving: validate with market data, articulate your contribution, listen for their constraints, unpack the whole package, and establish what happens next. The dread is normal. David Rock's SCARF model helps explain why a conversation with your boss can feel like a sabre-toothed tiger has walked in, and the Difficult Conversations module tells of a woman who put off a career-defining talk for over a year until a run of small honest acts, starting with sending back the wrong coffee, got her into her boss's office. Voice shaking, she made the case. She got it.

Why: When you challenge a colleague's approach, they don't hear a point about the work. They hear a question about whether they're good at their job, and for most people being good at their job is tied up with who they are. So they defend, fast, and the actual question gets lost. What they need is to be able to explain their thinking without having to protect their standing. Raise it privately, say you see it differently rather than that they're wrong, and ask about the pressures behind their view. That gives them room, and you usually learn something you'd missed. The Difficult Workplace Conversations module separates competence threats from status threats. David Rock's SCARF model (2008) lists five social concerns that can put people on the defensive, status first among them, and comments that shrink someone's standing, especially in front of others, tend to provoke a fight-or-flight kind of reaction. Lee Ross named the fundamental attribution error in 1977: we explain other people's behaviour by their character and our own by our circumstances, which is why "they're just difficult" comes so easily. Curiosity gets you both out of that trap. Amy Edmondson's research on psychological safety, which the Building Workplace Relationships module draws on, suggests treating disagreement as a good sign: a colleague who challenges your idea is trusting you enough to be honest. The same goes the other way.

Why: Chances are they already know something is off. They may not know what, because a hint like "this could be stronger" tells nobody what to change, and what seems obvious to you may not be obvious to them at all. Some people in this position are losing sleep waiting for someone to say it. What they need is the specific thing: what you saw, what it caused, what good looks like, and a sense that you're on their side. Said privately, as something you noticed rather than something they are, it lands as information. And they need you to ask before you tell, because the cause is often something you can't see from your desk. The workplace trust module's FEEDBACK framework uses a behaviour-impact formula, a close cousin of the Situation-Behaviour-Impact model from the Center for Creative Leadership: it names what happened and why it matters without judging the person. A 1996 review of feedback research by Avraham Kluger and Angelo DeNisi found that feedback improved performance on average but made it worse in more than a third of cases, usually when it pulled attention towards the person and away from the task. Elizabeth Newton's 1990 tapping study at Stanford showed the curse of knowledge: tappers predicted listeners would name about half the songs, and they named 3 out of 120. Once you know the tune, it's hard to imagine hearing only the taps. The Difficult Conversations module tells of a manager who put off this talk for months, expecting tears. Her team member said thank you, because nobody would tell him what was wrong. He'd been struggling with a new system and was too embarrassed to ask. One training session later, his work was back to standard.

Why: Being criticised at work hurts more than it should, and your body treats it as a threat before you've had a chance to think: hot face, racing heart, three rebuttals ready. In that state you can't take in what's being said, and anything you say is likely to be a defence of your intention rather than a response to what they saw. The person giving the feedback mostly wants to know it landed. If you ask for a specific example, say back what you heard and ask what better would look like, they get that, and you get something you can use instead of a verdict. If the delivery was blunt, that may say more about where they learned to give feedback than about you. Naomi Eisenberger, Matthew Lieberman and Kipling Williams's 2003 brain-imaging study found that being left out of a trivial online ball game raised activity in a brain region also involved in the distress of physical pain, though later work suggests the overlap is only partial. John Gottman calls the state where your heart races and you stop taking things in "flooding", and recommends a break of at least twenty minutes, roughly how long the body's stress response takes to settle. The Difficult Conversations module's HEAR sequence (halt your defence, engage with curiosity, acknowledge what you heard, respond with thanks and action) is built for exactly this moment. And Erin Meyer's work on feedback across cultures is a reminder that in direct-feedback cultures, "this is wrong" is aimed at the work and says nothing about you.

Why: Your manager probably can't see the pile. They see each new request on its own, and they see you saying yes, so from where they sit it's working. Nothing comes off because nobody has asked them to choose. What they need is the list and a decision to make: this or that, first or later. Handing them the trade-off keeps the call with them and leaves you doing the work they most want done. Setting a limit this way isn't being "not a team player"; it's what lets you keep saying yes to the things that matter. The dread is real. David Rock's SCARF model (set out in 2008) helps explain why "I need to talk to my boss about my workload" can feel like a sabre-toothed tiger wants to eat you: it touches status and certainty. In Give and Take (2013), organisational psychologist Adam Grant found generous people at both the bottom and the top of success measures. The ones who struggled were "selfless" givers who helped at the expense of their own work and burned out; the ones who thrived were "otherish", caring about other people's interests while keeping an eye on their own. Saying yes to everything can also leave colleagues wondering whether you have boundaries, or much judgement about priorities. The Leadership & Influence module adds that certainty and autonomy are two of the things a good manager's language protects: "What approach would work best given your other priorities?" and "I'll update you every Friday with any changes to priorities" are their lines, and you can prompt them.

Why: The colleague who went quiet may be giving your question proper thought. The "yes" may have meant "I'm listening". The feedback that felt brutal may have been meant as help, with the padding left off because padding feels dishonest where they learned to give it. None of them is being odd; they're running on communication rules learned so early that nobody can see them, and so are you. What they need from you is to be asked rather than decoded: about their own experience, not their whole country, with your way offered as one option. And when you get it wrong, which you will, they need you to say so plainly. People are remarkably forgiving when you approach them with humility. Edward T. Hall's distinction between high-context and low-context communication, introduced in Beyond Culture (1976), explains many of these misfires: in some settings much of the meaning sits in the setting, the pause and the tone, and in others the words carry it. Geert Hofstede's country scores are national averages, and he warned against using them to stereotype individuals, so the frameworks give you a first guess and only asking tells you who is in front of you. Melanie Tervalon and Jann Murray-García's idea of cultural humility (1998) treats your way as familiar rather than correct. The module's story of Nkechi's logistics team is a reminder that sometimes it isn't culture at all. One colleague's lateness, which she'd put down to a different attitude to time, turned out to be the school bus timetable. She moved the meeting to 9.30.

Why: The person you're telling has a problem they didn't make and a quieter question underneath it: can I rely on you? That question weighs more than it feels like it should. When Roy Baumeister and his colleagues reviewed the research in 2001 they called their paper "Bad Is Stronger Than Good": one slip can outweigh several good weeks, so how you own it matters more than the size of the mistake. What they need is not remorse on display. The Conversation Repair module's four-part formula is specific action, impact, responsibility with no buts, and an invitation to talk. Harriet Lerner, author of Why Won't You Apologize?, is blunt about the "but": it cancels the apology and turns it into a defence. The over-apology fails for the opposite reason: your shame spiral takes over their experience. The module's balance is to hold both truths: you caused harm, and you're a person who can learn from it. Owning a mistake openly is also how trust gets built in the first place. Amy Edmondson's 1999 study of 51 work teams found that teams with higher psychological safety talked openly about mistakes and performed better, and Google's Project Aristotle came to the same conclusion about its own teams. In the trust model from Roger Mayer, James Davis and David Schoorman (1995), integrity includes admitting when you're wrong. The Leadership module puts it in one line: "I made a mistake here, and here's how I'll handle it differently."

Why: The person talking over you almost certainly doesn't know they're doing it. In their head they're engaged and driving things forward; the Group Dynamics module describes the Dominator who takes 60% of the airtime in an eight-person meeting and would be horrified to hear it. Robert Zajonc's 1965 account of social facilitation helps explain it: an audience strengthens whatever response comes most easily to you, and for a confident speaker that response is "engage more". Status does the rest. Cameron Anderson and Gavin Kilduff found that group members rated their more dominant peers as more competent, even after accounting for how capable those peers actually were. What the room needs is not a confrontation but a format. The module's tools are the gentle redirect, the round, the written warm-up and the long pause, all of which contain the over-talker without shaming them. What you need, when it's you being cut off, is to make the behaviour specific rather than the person: "When you interrupted just then, I lost my train of thought. Can I finish?" comes straight from the Conversation Repair module as the kind of feedback that makes change possible. It's worth doing because the group gets measurably less smart when a few voices take most of the turns. Anita Woolley and colleagues found a group's collective intelligence was only modestly linked to its members' IQ and higher where conversational turns were shared more evenly, though later studies have debated how robust that finding is. And the reason nobody acts is the bystander effect that John Darley and Bibb Latané described: your share of the obligation feels smaller when it's split eight ways. Once one person goes first, others usually follow.

Why: Bad news about work lands hard because it touches more than the work. The Difficult Workplace Conversations module names the common reactions, shock, anger, fear, sadness and anxiety, and the question under most of them: what does this mean for me? David Rock's SCARF model lists the five social concerns a leader's words can threaten, and a restructure hits several at once: certainty about the future, status, and fairness. That's why a room can turn on a messenger who had no part in the decision. What the team needs is honesty about what's known, respect in how it's said, and some say in what happens next. The module's CRISIS framework runs in that order: communicate early and transparently, recognise the emotional response before problem-solving, separate what can and can't be changed, support people practically, involve them in the response, and stay available afterwards. Choice matters because it's one of the basic needs that self-determination theory (Edward Deci and Richard Ryan) describes, alongside connection and competence. "Here's what we know, what we don't know, and what we're doing about both" appears in both the Leadership and Difficult Workplace Conversations modules for a reason. The research on how much delivery matters is blunt. In the 2003 brain-imaging study by Naomi Eisenberger, Matthew Lieberman and Kipling Williams, even being left out of a trivial online ball game raised activity in a region involved in the distress of physical pain, though later work shows the overlap is only partial. A threat to someone's role is not trivial. As the module puts it, people remember feeling respected and supported through difficult times, and how you communicate in a crisis becomes part of your reputation as a leader.

Why: The person across the table is about to lose more than a wage. The Nonviolent Communication module's Aisling guessed at the needs her team members were carrying into the room: security, purpose and respect. Losing a job threatens all three at once, which is why even a well-run redundancy can land with the force the Difficult Workplace Conversations module describes for any threat to someone's role. What they need is for the news to be said plainly by a human being, a clear picture of what happens next, and some say in how it goes. Aisling's conversation followed NVC's four components: an observation ("The company is reducing this team from twelve positions to six. Your role is one of those being removed."), a feeling ("I'm sad about this"), the needs on both sides, and a request ("would you be willing to tell me what you need from me?"). A request works where a demand doesn't because of what Jack Brehm called psychological reactance: people push back when they feel their freedom to choose is under threat, and a request leaves room for "no". Months later one of her six told a former colleague, "They let me go, but they did it with humanity." Delivery matters because people remember it. The Difficult Workplace Conversations module says how you deliver bad news often matters more than the news itself, and that people remember feeling respected through difficult times. It's equally clear that the legal process comes first: work with HR, because consultation, notice and redundancy pay rules differ from country to country, and this app serves seven of them. Nothing on this page is legal advice.

Why: Start with the silence in the room, because it's probably what made you doubt yourself. The Group Dynamics module describes the bystander effect that John Darley and Bibb Latané found: the more people present, the less likely any one of them is to step in, because the obligation feels smaller when it's split eight ways. Solomon Asch's line experiments showed how hard it is to stand alone against a unanimous room even when the room is obviously wrong. Nobody reacting is not evidence that nothing happened. What the situation needs from you is a specific, dated account and the proper channel, not a showdown. The Difficult Workplace Conversations module is unusually direct here: harassment, discrimination, bullying and safety complaints usually have to go through a formal process under your organisation's policy, and often under law as well, so don't try to settle them informally between the people involved. The legal requirements differ between the countries this app serves, which is exactly why it says to bring in HR or the complaints channel early. Its PREPARE framework tells you what to collect: what happened, when, where, who was affected and why it matters. The Building Workplace Relationships module adds the protective habit of following up important conversations in writing. Speaking up is also how a team stays one where honesty is possible. Amy Edmondson's 1999 study of 51 work teams linked psychological safety to teams that raised problems and performed better, and the Group Dynamics module lists what kills that safety: people punished for raising things, questions treated as incompetence, disagreement met with retribution. The Leadership module's advice to anyone receiving a report is to protect the messenger first: "Thank you for bringing this to my attention."

Why: Quiet people usually aren't quiet because they have nothing to say. The Group Dynamics module describes three of them: Sophie, who thinks before she speaks and never gets the pause she needs to come in; Aisha, who grew up where you don't speak until invited and interrupting someone senior is disrespectful; and Liam, new and junior, who has done the risk calculation every newcomer does and decided silence is safer. Add social loafing, the effect Bibb Latané, Kipling Williams and Stephen Harkins named in 1979, where people ease off when their own effort can't be seen, and you have a room where the format is failing the people in it. What they need is a pause, a specific invitation and a way in that isn't an audition. The module's inclusion tools are structural: written warm-ups, rounds, pairs, anonymous cards, and the long wait after a question. In classroom research in the 1970s, Mary Budd Rowe found teachers typically waited about one second for an answer; stretching it to three to five seconds brought longer answers, more ideas, and more answers from the students teachers had seen as slower. Underneath the tools sits safety: Amy Edmondson's 1999 study of 51 work teams found that teams with higher psychological safety asked questions, sought feedback and talked openly about mistakes, and what builds it is predictable: leaders admit mistakes first, questions are welcomed, dissent is explicitly invited. The payoff is a smarter group, not just a politer one. Anita Woolley and colleagues found a group's collective intelligence was only modestly linked to members' IQ and higher where turns were shared more evenly, though later studies have debated how robust that is. Google's Project Aristotle, studying its own teams, put psychological safety first among the dynamics that mattered. The module's Mel changed nothing about the people in her Tuesday meeting; she changed the structure, and the structure did the rest.

Why: Whatever your reason, your manager hears a problem landing on their desk: a vacancy to fill, work in flight, perhaps a team they've already told you're the future of. If they backed you, it can feel personal, and a first reaction like "after everything I've done for you?" says more about the shock than about what you owe them. The Difficult Conversations module uses David Rock's SCARF model to explain the alarm a hard conversation sets off: status, certainty, autonomy, relatedness and fairness, and when several are threatened at once it's as if someone has pulled the fire alarm for the whole building. Being told a good person is leaving pulls several of them. What they need from you is the news, clearly and first, a reason they can repeat to their own boss, and a plan. The Career Advancement module's NOTICE framework is built around exactly that: nail down the decision before you walk in, tell your manager before anyone else, put the news in the first sentence, invite the handover conversation, confirm it in writing the same day and exit with care. Priya, in the module's story, rehearses it in the shower, the car and the lift, and apologises in her head so many times that the apology is the first thing out of her mouth. Rehearsing in the shower is the avoidance path; the courage path is having the conversation this week, voice shaking, in five minutes. In 2016 Anthony Klotz and Mark Bolino, writing in the Journal of Applied Psychology, identified seven resignation styles across four studies. Three are the kind you'd want to receive (by the book, perfunctory and grateful goodbye), one keeps the manager in the loop before the decision is final, and three are the ones managers remember for the wrong reasons: avoidant, bridge burning and impulsive quitting. Employees who felt fairly treated and respected by their manager were more likely to resign in the considerate styles, and when managers were shown accounts of each style, the bridge-burning, avoidant and perfunctory resignations drew the most negative reactions. The manner matters more than the reason. Abbie Shipp and colleagues (2014) studied "boomerang" employees at a large professional services firm, people who quit and were later rehired: compared with those who never came back, they were more likely to have left because of a specific event in their lives rather than dissatisfaction with the job. People go back to places that treated them well, and that take them back, and how you resign is part of that record. Two things the module can't decide for you. The research on counteroffers is thin, so it won't tell you whether to take one, only to decide before you walk in. And your notice period, unused leave and what you can say publicly afterwards are set by your contract and local law, which differ between the countries this app serves; read the contract first, and if anything in it surprises you, get advice from the relevant government service or a union before you hand in notice.