Join UsCEO MastermindAI Leadership MastermindExecutive AI ProgramFractional AI Executive1:1 Coaching5-Minute Leader
BooksPower Without PermissionAI Leadership Mastermind
PodcastMeet the Team
ResourcesBlogFree AssessmentsResearch and DataTeaching PackagesTestimonialsCEO Coaching ReportJoin UsAdd us on Google

All free teaching packages

Leaders ADAPT teaching package

Teaching saying no: a free session plan for students, new managers and team leaders

A ready to run class or workshop on saying no at work, free to use under CC BY 4.0. Participants take a three minute focus test, practise the Pivot on four scenario cards, and leave with their first Monday List written and one real ask answered on paper.
20, 45 or 90 minutesFree focus test includedFour scenario cardsPrintable Monday ListWorks without direct reportsCC BY 4.0

Who this is for

Instructors of university career and professional skills courses, MBA and executive education modules on personal effectiveness, graduate and early career programmes, learning and development leads running new manager training, and team leaders who want to run one practical session with their own people. Nobody in the room needs direct reports. The session argues the opposite: the tools matter more when you have no authority to lean on, because the person asking cannot see your workload unless you show it to them.

What participants leave with

  • A focus score from the free test, and the one wall of their Focus Fortress (physical, digital or mental) that is missing.
  • Their own Monday List: five commitments for this week, ranked by impact, with the four rules for using it printed underneath.
  • One Pivot sentence written for a real ask they are facing, said out loud to a partner once and scored on whether they actually said no.

Pre-work (optional, 10 minutes)

Ask each participant to bring one ask they said yes to in the last 30 days and regretted, written as one line: what was asked, who asked (a role, not a name), and what it pushed out. That line becomes their raw material in the practice round. For the 20 minute version, also ask them to take the free focus test before they arrive.

No Is a Leadership Skill: the model in seven parts

This is Andreas Pettersson's model, taken from his workshop of the same name, with the Focus Fortress from his personal productivity protocols added to protect what you do say yes to. It starts from one claim: most of the pressure to overextend is internal. So it begins with what happens in your head and ends with a sentence you say out loud. It does not teach refusing. It teaches making the cost of a yes visible so the person asking can decide.

The Mind Trap
Someone asks you for something. Before they finish the sentence you have imagined them disappointed, rehearsed how they will react, and decided yes is easier. They have not said a word yet. You negotiated against yourself and lost. "You built a courtroom in your head, played both lawyers, and convicted yourself before the trial started." Teach this slowly. It is the part people recognise, and recognition is the whole first half of the session.
Guilt, Fear, Habit
The three defaults behind an automatic yes, written the way people say them to themselves. Guilt: "They need my help and I have the ability, so I should." Fear: "If I say no, they will think I am not committed or not capable." Habit: "I have always said yes. It is just what I do." None of them is a strategy. They feel like professionalism in the moment and cost you three weeks later. Ask people to pick which one drove their own regretted yes.
The CEO Test, and the manager's half of the deal
When someone senior says "what about this?", most people hear "do this now". In practice most of what comes down from above is an idea being floated, and only a minority is a real directive. Treating all of it as a mandate is how calendars fill. Asking why something matters, and showing what is already on your plate, is not pushing back. It is managing upwards: your boss cannot see your calendar, and a silent yes robs them of information they need to decide well. The deal runs both ways, and this is the half managers in the room need to hear: when you add something to the top of someone's list, you accept that something else sinks. If one of your people answers you with the Pivot, that is not resistance. It is the information you need, so thank them for it and decide.
The Four Questions, ending in the Pivot
Run them silently before you answer any ask. About 30 seconds once it is a habit. 1. Was the why explained? If nobody can say why it matters, it probably does not, and asking "help me understand what this connects to" is professional, not rude. 2. Do I have a ranked list of current commitments? You need a list before you can use a list. 3. What moves down if I say yes? If you cannot name it, you are pretending you have infinite capacity. 4. The Pivot, said out loud: "Yes, and here is what that means for my list. Which one matters more to you?" You are not refusing. You are making the trade visible and handing the decision back. Usually one of three things comes back: the ask goes to someone else, the timeline moves, or you are told which existing commitment can wait.
The Monday List
Every Monday morning, write your top five commitments ranked by impact. Not by urgency, not by who is asking loudest. Four rules sit under the list: rank by impact; measure every new ask against the list before you respond; if the new ask does not rank higher than what is already there, the answer is "not yet"; if it does, something else moves down and you name what. One sheet, five lines, five minutes. Without it every request feels equally important. It is what makes question two answerable.
The Vacation Test
Think about the last time you were away for a week. Did anything actually burn down? For most people the answer is no: they came back, sorted their inbox and were caught up by lunch. If the building does not collapse when you disappear, then the things filling your calendar are not all as critical as they feel at the moment you say yes to them. For students, use the last time you were ill for a week.
Focus Fortress
Saying no protects your time. The Fortress protects the work you said yes to. Three walls around a 90 minute block. Physical: make interrupting you more effort than solving the problem alone (a closed door with the finish time on it, headphones, a booked room). Digital: email shut down rather than hidden, chat paused until a set time, phone out of reach. Mental: a scrap sheet next to you, so a stray reminder gets written down and you carry on. One question guards the block: would waiting an hour and a half hurt a person, cost serious money or break a relationship that matters? If none of the three, it waits.

The Law of Two Feet used in the 90 minute opening comes from Harrison Owen's Open Space Technology. SCQA, mentioned under question one, is Barbara Minto's, from The Pyramid Principle. Everything else on this page is Andreas Pettersson's own, including the manager's half of the deal from his No Is a Leadership Skill workshop; the Focus Fortress comes from his personal productivity protocols.

Want the whole system? The 5-Minute Leader

This page teaches the inner work of saying no and the tools that make each trade visible. The 5-Minute Leader works on the other side of the same habit, step by step: the belief that only you can do it properly drives the automatic yes and stops you handing work off, and the book takes that belief apart.

  • The 70% Test for deciding what to hand off, and how to match each piece of work to the right person
  • The Delegation Protocol, with the three minute delegation conversation and the 25% Rule for check ins, so work you hand off stays handed off
  • The Rhythm Protocol: a short daily stand-up and a weekly team meeting that replace a steady stream of ad hoc asks
  • The 1:1 Protocol, where priorities and capacity get checked every week instead of discovered when a deadline slips
Get the full 5-Minute Leader system

Session plans

Pick the length that fits your slot. Every version uses the same test, framework and worksheet.

45 minute version

MinutesWhat happens
0 to 5Hand raise cascade, three questions, hands stay up: regretted a yes in the last 30 days; still regretted it a month later; doubted it even had value. Then: "Look around. Whose fault is that?" Disown the harshness straight after, not before. Say the guardrail from the facilitator notes.
5 to 9Everyone takes the free focus test. They note the score and the weakest of the four areas, and keep it to themselves for now.
9 to 17The Mind Trap (slowly), Guilt, Fear, Habit (each person circles theirs on Part 1 of the handout and writes the sentence they told themselves), then the CEO Test.
17 to 25The Four Questions and the Pivot. Read the fictional case aloud. Small groups take discussion questions 1 to 3 and draft the Pivot Jonas should have used.
25 to 37Practice round. Pairs, two scenario cards, three minutes per round, swap roles. The asker scores the strip. Walk the room with the micro feedback lines from the facilitator notes. Pull back and ask what was hardest.
37 to 43Monday List, written now for this week. Then Part 6: one move for the weakest Focus Fortress wall the test named, and the urgency question copied out where they will see it.
43 to 45The Vacation Test as two questions and a silence. Set the 30 day challenge: write the list every Monday, check it before every yes.

The free test participants take

Participants take the free focus test on their own phone or laptop. It takes a few minutes. It asks for a name and email to send the full result, so tell participants that in advance. Results go only to the person who took it, so nobody has to share a score unless they choose to.

Link to give participants (paste it into your slides or learning platform):

https://www.leadersadapt.com/assessments/focus/?utm_source=teaching-package&utm_medium=referral&utm_campaign=teach-saying-no

The case: the analyst who said yes to everything

Fictional case, written for teaching. Names, companies and numbers are invented.

Jonas Lind is a second year analyst at Brightwater Freight, a fictional logistics company of 300 people. He has no direct reports. His manager, Sofie, gave him two priorities this quarter: the monthly carrier cost report, due on the 5th, and cleaning the shipment data for a pricing review in six weeks.

In the last month Jonas also said yes to four other things. He joined a new cross team working group on reporting tools that meets every other week, because the invite came from HR and saying no felt rude. He covered a colleague's customer reporting for two weeks while she dealt with a family situation. He took on a "quick" dashboard for the sales team that turned into eleven hours. And when the operations director said in a corridor, "Someone should look at why our Friday shipments cost more", Jonas said "I can take a look" and has been taking a look every evening since.

The carrier cost report went out on the 9th, four days late, with two errors a finance colleague caught. Sofie was surprised. Nobody had told her Jonas's month had doubled. When she asked what happened, Jonas said, "I can make it work, it was just a busy month."

This morning the operations director stops him again: "Great start on the Friday shipments. What if you also looked at weekend returns?" Jonas has not written anything down this week. He can feel the yes forming. A Pivot he could use: "I can do that. Right now I am on the carrier report and the pricing data for Sofie. If I take this on, the pricing data slips about a week. Which one matters more to you?"

The handout

Print one per participant, or paste it into a shared document. Parts 1 to 3 are for the session, Part 2 goes on the wall at home or work. Download the Word version

Discussion questions

  1. Which of Guilt, Fear or Habit drove each of Jonas's four extra yeses? What in the case tells you?
  2. Sofie was surprised by the late report. Whose information failure was that, and what would have prevented it?
  3. Apply the CEO Test to the operations director's corridor comments. Idea or directive? How could Jonas find out without sounding difficult?
  4. Read Jonas's Pivot aloud. What three answers might the director give, and is any of them worse than the situation Jonas is in now?
  5. When is the Pivot the wrong tool, and a plain no the right one? Think about the committee invite.
  6. If someone used the Pivot on you, how would you want to respond? What is the manager's half of the deal, and what would you have to do to make them keep using it?
  7. What is on your calendar this week that would pass the Vacation Test, meaning nothing would burn down if it never happened?

Facilitator notes

  • Say the guardrail out loud before the Mind Trap, in these words: "These are addressed to yourself. Used on yourself they are a discipline. Used on somebody else, several of them become a weapon. You may use them on you. That includes me." Some overload is imposed, and the session is about the share you control. Without the guardrail a manager in the room can walk out with a script for telling an overloaded report it is their own fault.
  • Micro feedback while you walk the practice round. Caved too fast: "You just said yes without checking your list. Try again." Too blunt: "You do not have to refuse. Make the trade visible." Nailed it: say so out loud so the room hears what good sounds like. If someone says "but I am paid to do this": "You are paid to deliver results, not to say yes to everything."
  • Predict the debrief answer and let the room say it: most pairs will report "I felt guilty." That is the finding. The discomfort does not go away; people get better at acting through it. Set the honest timeline: awareness today, practice this month, habit in about three months.
  • Students and individual contributors: swap the asker for a module leader, group project partner, society president or shift supervisor. Make the inversion explicit once: with no authority, the list and the Pivot matter more, because the other person cannot see your workload unless you show it.
  • The focus test asks for a name and email before it shows the result. Tell people before they start. Anyone who prefers not to can read the twelve statements on the test page and self score: count how many are true for them in each of the four areas.
  • If nobody volunteers for the 90 minute demo, use Jonas from the case and play him yourself, letting the room coach you through the four questions. It works almost as well and nobody has to expose a real situation.

Use, adapt and cite

This package is licensed under Creative Commons Attribution 4.0. You may copy, print, adapt and share it in any course, workshop or internal training, including paid ones, as long as you credit the source with a link.

Citation

Pettersson, A. (2026). Teaching saying no: a session plan. Leaders ADAPT. https://www.leadersadapt.com/teach-saying-no/

Link for your course page or syllabus

<a href="https://www.leadersadapt.com/teach-saying-no/">Teaching saying no: a free session plan for students, new managers and team leaders</a> by Andreas Pettersson, Leaders ADAPT (CC BY 4.0)

Using the package does not imply any endorsement of Leaders ADAPT by your institution, and none is claimed. Teaching with it? Tell us at andreas@leadersadapt.com and we will list your course on the teaching packages page.

Keep going after the session

The Monday List protects your week. The 5-Minute Leader builds a team that needs fewer of your yeses in the first place, installed one protocol at a time.

Get the full 5-Minute Leader system

Further reading for participants