The training ground for people who open doors.

The First Ten Minutes

How you open decides whether you get the real story.

People in crisis have usually told their story to five people already. The first ten minutes decide whether you hear the version they tell everyone, or the one that actually explains what is going on.

Motivational Interviewing: four tasks and OARS

• Engaging: build a working relationship before you fix anything
• Focusing: agree on what this conversation is about
• Evoking: draw out their own reasons and ideas
• Planning: shape next steps together
• OARS skills: Open questions, Affirmations, Reflections, Summaries

How to run it

1. Start concrete: "Where did you sleep last night?" sets the facts without judgment.
2. Reflect before you fix. Say back what you heard in one sentence before offering anything.
3. Ask one open question at a time, then wait longer than feels comfortable.
4. Ask permission before advice: "Can I share what's worked for other families?"
5. Close with a summary and one next step they chose, written down.

From the field

• Say the rules at intake, then mention them again at every meeting. A notice should never be the first time someone hears a rule.
• Tell people where they are on the clock every time you meet: "You're on day 40 of 90." It keeps time real without sounding like a threat.
• Lead with the hard part. Cover expectations before anything else in a group, so they do not surface in front of a guest.
• Introduce the front desk and overnight staff as part of the same team. Clients should know from day one that those staff carry the same authority.

Drill: Take five closed questions from your intake form and rewrite each as an open question. Practice the reflection that follows each one out loud.

Sources

• Motivational Interviewing: Helping People Change and Grow, 4th ed. (Miller & Rollnick, Guilford Press, 2023)

Trauma-Informed Practice

Assume the person has been through more than they will tell you today.

Many of the people you serve have learned that systems surprise them, judge them and take things away. Trauma-informed practice removes the surprises and gives back control wherever you can.

SAMHSA's six principles and the 4 Rs

• Safety
• Trustworthiness and transparency
• Peer support
• Collaboration and mutuality
• Empowerment, voice and choice
• Cultural, historical and gender issues
• The 4 Rs: realize, recognize, respond, resist re-traumatization

How to run it

1. Explain what happens next before it happens, including the parts they will not like.
2. Offer real choices, even small ones: which chair, which day, call or text.
3. Remove surprises. If a room check, search or deadline is coming, say so early.
4. Ask "What would make this easier for you?" and act on at least one answer.
5. Notice your setting: noise, crowding, who can overhear.

From the field

• Talk the way a friend would explain what comes next, not the way a policy reads. "Room checks are Thursday, here's what that looks like" lands better than a citation.
• Ask consent for a search respectfully: "Can you step out for a minute, it'll be quick." Treating a refusal as an automatic exit escalates for no gain.
• Room cleanliness alone should almost never put a family on the street. Coach it with storage bins and time, not notices.

Drill: Script how you would explain a weekly room check to a new family using all six principles. Then cut it to four sentences.

Sources

• SAMHSA's Concept of Trauma and Guidance for a Trauma-Informed Approach (SAMHSA, HHS Pub. No. (SMA) 14-4884, 2014)

De-escalation

Change the room before you change the person.

Escalation follows a predictable arc. If you know where someone is on it, you know which tools work and which make it worse. Safety for you and for everyone in the lobby comes first.

Project BETA's ten domains, mapped to the escalation curve

• Respect personal space
• Do not be provocative
• Establish verbal contact (one person talks)
• Be concise
• Identify wants and feelings
• Listen closely
• Agree, or agree to disagree
• Lay down the law and set clear limits
• Offer choices and optimism
• Debrief the person and the staff

How to run it

1. Change the physical setup first: move away from the audience, sit down if you are standing over them, lower your voice.
2. One staff member talks. Everyone else gives space and watches.
3. Name the want: "You need your stuff back tonight. Let's figure out how."
4. Set the limit with a choice attached: "I can't do that here, I can do this in the office."
5. If it reaches the peak, stop talking about the issue and focus on safety and exits.
6. Debrief within the shift, with the person when calm and with staff.

From the field

• Most grievances end when you move the conversation away from the crowd and sit down.
• For roommate disputes, hear each side separately, then point both back to their own goals instead of judging who is right.
• When someone disrespects front desk staff, there should be a visible consequence, and the front desk should hear what you did. Otherwise they stop reporting.
• Some volatility is normal in shelter. Coach staff who overuse new authority to issue notices, rather than taking the authority away.

Drill: Partner role-play: one person escalates over a lost locker key. Practice three limit-plus-choice sentences.

Sources

• Verbal De-escalation of the Agitated Patient: Project BETA Consensus Statement (Richmond et al., Western Journal of Emergency Medicine, 2012)
• Managing the Cycle of Acting-Out Behavior in the Classroom, 2nd ed. (Colvin & Scott, Corwin, 2015)
• Guidelines for Preventing Workplace Violence for Healthcare and Social Service Workers (OSHA 3148) (OSHA, 2016)

Diversion and Problem-Solving Conversations

Find the smallest fix that actually works.

A shelter bed is expensive, scarce and hard on families. A short, creative conversation often finds a safer option: a relative, a deposit, a bus ticket, one month of rent.

The smallest-fix conversation

• Establish where they slept last night
• Ask about every person in their network, not just family
• Ask what would solve tonight and what would solve this month
• Price the smallest fix and verify it
• Pay vendors directly and keep the paper trail
• Document the outcome and the reason

How to run it

1. Open with "Where did you sleep last night?" to establish the facts first.
2. Walk through people they know one by one. "Who has helped you before?"
3. Ask what the fix would be if money were not the issue, then price it.
4. Verify the arrangement directly with the landlord or host.
5. Pay the landlord or carrier directly. Never hand cash.

From the field

• Call the waitlist again. A second conversation weeks later often finds a relative or resource that was not there at first contact.
• More money will not divert a household that cannot be diverted. Watch for staff reaching for funds before the conversation is done.
• Diversion from inside a shelter is much harder than diversion at the front door. Work as far upstream as you can.
• Count each household once. Diversion numbers that add up overlapping stages overstate results.

Drill: Run a ten-minute diversion conversation with a partner playing a parent whose sister has a spare room 300 miles away.

Finding the Right Door

Sent is not served.

A program existing is not the same as a person getting in. Hours change, intake pauses, requirements shift. A referral only counts when someone receives it, contacts the person and accepts them.

The referral state ladder

• Sent: you made the referral
• Received: the program has it
• Contacted: they reached the person
• Accepted: the person is in
• Served: help actually happened
• Closed: outcome recorded, or redirected with a reason
• Warm handoff: introduce in person, in front of the client, so they can correct what is said

How to run it

1. Check the door before you send: current hours, intake method, what to bring, last verified date.
2. Give the person a plan B before they leave your office.
3. Do a warm handoff whenever possible: call together, introduce, let the client hear and correct.
4. Follow up at a set time: "I'll check in Thursday at 2."
5. Record why a referral closed, especially when it failed.

From the field

• Map every step of the housing pipeline and know who owns each one. A stall at any step adds weeks.
• Partners have quiet limits, like how many households one case manager can bring to a briefing. Ask before a big push.
• Write down why someone leaves a waitlist. Otherwise the next worker cannot tell what happened.
• A resource across town only helps if transportation comes with it.

Drill: Pick three programs you refer to most. Verify their current intake steps today and write a plan B for each.

Sources

• Warm Handoff: Intervention Guide (Agency for Healthcare Research and Quality)
• Randomized Trial of Critical Time Intervention to Prevent Homelessness (Herman, Conover et al., Psychiatric Services, 2011)

Housing First and Critical Time Intervention

Housing is the platform, not the reward.

Requiring people to be treatment-ready before housing keeps them on the street longer. Housing First puts housing first and offers support by choice. Critical Time Intervention covers the fragile months after a move.

Housing First plus CTI

• No readiness requirements for housing
• Consumer choice in services
• Harm reduction rather than abstinence as a condition
• CTI Phase 1, transition: intensive support right after the move
• CTI Phase 2, try-out: the person leads, you watch the supports
• CTI Phase 3, transfer of care: hand off to lasting community supports

How to run it

1. Separate the housing decision from treatment decisions.
2. Plan the first 30 days after move-in in detail: utilities, furniture, food, transportation, landlord contact.
3. Agree on what support looks like during try-out, and step back on purpose.
4. Name the community supports that will remain after you leave.
5. Be honest about limits: housing stability improves; symptoms and income often need other help.

From the field

• Before exiting someone from housing support, ask whether a short extension or small payment prevents a return to homelessness. Usually it is the better decision.

Drill: Write a move-in week plan for a family of four moving into an unfurnished apartment in August.

Sources

• Housing First, Consumer Choice, and Harm Reduction for Homeless Individuals With a Dual Diagnosis (Tsemberis, Gulcur & Nakae, American Journal of Public Health, 2004)
• Effectiveness of permanent supportive housing and income assistance interventions: a systematic review (Aubry et al., Lancet Public Health, 2020)
• Randomized Trial of Critical Time Intervention to Prevent Homelessness (Herman, Conover et al., Psychiatric Services, 2011)

Documentation That Holds Up

Write every note so a stranger could pick up the case tomorrow.

Documentation is how you advocate for someone when you are not in the room. Thin notes are the most common reason a later review cannot reconstruct what happened, and they leave the client without a defense.

Notes that hold up

• Timely: same day
• Objective: what you saw and heard, not your conclusions
• Specific: who, what, when, where
• Complete: what you did and what comes next
• Two-tier notices: a light notice for routine lapses, a formal violation for serious ones

How to run it

1. Write the note the same day, before the shift ends.
2. Use quotes for what the person said, plain description for what you saw.
3. Separate facts from your assessment, and label the assessment.
4. End each note with the next step, the owner and the date.

From the field

• Every file is a case for or against the person. Good notes are what let you advocate for them in a staffing.
• If a formal violation takes 30 minutes and a signature hunt, staff will give verbal warnings instead and the record will be empty. Keep a light tier.
• A refusal to sign does not void a notice. Record "declined to sign" and move on.
• Tie a corrective condition to the specific rule broken. Unrelated demands feel like collecting grievances.
• Keep separate counts for separate rule types. Three missed meetings are not three messy rooms.

Drill: Rewrite this note so it holds up: "Client was rude and refused to cooperate with staff."

Sources

• HMIS Data and Technical Standards Final Notice (HUD, 69 FR 45888, 2004)

Rules, Notices, Exits and Appeals

Decide in advance what you would tolerate nine times, three times, or once.

Rules protect everyone in a shared space, and exits change lives. Fair process, proportional responses and clean separation of roles keep both safety and trust.

Proportional response

• Routine lapse: conversation and coaching
• Repeated lapse: light notice, discussed at the next meeting
• Serious violation: formal notice with a specific condition
• Safety threat: immediate action, then full review
• Separation of roles: whoever gave the warning does not review the exit
• Written appeal, written decision, named reviewers

How to run it

1. Know your policy's tiers before you need them.
2. Deliver notices without a confrontation: upload, copy to their folder, discuss at the next meeting.
3. Rescind a notice when the person brings proof, and note that you did.
4. Time a non-immediate exit for when staff are on shift, usually the next morning.
5. Explain the appeal route in writing at the same time as the decision.

From the field

• A weapon, a credible threat or drug sales once may justify an exit. An unclean room nine times might never.
• For absences, call daily, including hospitals, jails and emergency contacts, before treating someone as gone.
• Handle grievances at the lowest level that can resolve them. Most close with a conversation and a note.
• Anyone named in a grievance hands it to a peer or the next level up.
• Be careful who you copy. Copying senior leaders early makes them parties, and they can no longer review neutrally.
• When leadership overrules a rule for a good reason, explain it to staff, or they will ask why the rule exists.

Drill: A parent has missed curfew three times in two weeks. Walk through your response at each tier, and what you would check first.

Sources

• SAMHSA's Concept of Trauma and Guidance for a Trauma-Informed Approach (SAMHSA, HHS Pub. No. (SMA) 14-4884, 2014)

Mandated Reporting and Confidentiality in Arizona

Know the duty before the moment arrives.

In Arizona, social workers and others responsible for a child's or vulnerable adult's care must report suspected abuse or neglect immediately. At the same time, several privacy rules decide who can see what you write. Both matter every week.

Report and protect

• Children: A.R.S. 13-3620, report immediately to a peace officer, DCS, or a tribal law enforcement or social services agency
• Vulnerable adults: A.R.S. 46-454, report immediately to a peace officer or Adult Protective Services
• HMIS: baseline privacy and security standards, privacy notice posted
• Domestic violence: victim service providers keep identifying data out of HMIS (VAWA)
• Substance use treatment records: 42 CFR Part 2, more closely aligned with HIPAA since 2024

How to run it

1. If someone is in danger now, call 911 first.
2. Report what you observed or were told. You do not need proof, and you do not investigate.
3. Tell your supervisor, and follow your agency's internal steps.
4. Document the facts, the time you reported, who you spoke with and any reference number.
5. Share client information only on a need-to-know basis and with the consent your program requires.

From the field

• In a sensitive incident, gather facts before acting. Frontline staff keep providing normal care but do not question the person about the incident.

Drill: List the three phone numbers and one website you would need for a report, and where you would document it. Know them before your next shift.

Sources

• A.R.S. 13-3620: Duty to report abuse, physical injury, neglect and denial of care to minors (Arizona Revised Statutes)
• A.R.S. 46-454: Duty to report abuse, neglect and exploitation of vulnerable adults (Arizona Revised Statutes)
• Adult Protective Services: Mandated Reporters (Arizona Department of Economic Security)
• HMIS Data and Technical Standards Final Notice (HUD, 69 FR 45888, 2004)
• HMIS Comparable Database Manual (HUD Exchange, updated 2026)
• Confidentiality of Substance Use Disorder Patient Records (42 CFR Part 2) Final Rule (HHS, 89 FR 12472, 2024)

Incidents: Report It Right

It is never too late, or too far off-site, to file.

Incident reports protect clients, staff and the program. They are also how leaders learn what is actually happening. Most reports go wrong because they are late, thin, or mix several people together.

The clean incident report

• Each witness writes their own report
• One primary person per report; others by role or room only
• At least three full sentences of narrative
• Same shift, or as soon as possible
• A supervisor, not frontline staff, flags escalation to executives
• A lead compiles reports into one timeline

How to run it

1. Make the scene safe and get help first.
2. Notify your supervisor during the shift.
3. Write your own account. Do not co-write with others.
4. Describe what you saw and did, in order, with times.
5. Close the loop: who followed up, and when.

From the field

• Field staff who work alone, like housing staff on home visits, are the least likely to file. That creates risk for them personally.
• Have a ready template for escalations: entry date, case manager, interventions, days in program, outside agencies. It saves hours in a crisis.
• Make the narrative box large. Late-night reports get shorter as the box gets smaller.

Drill: Write an incident report for a fictional scenario in under ten minutes, then trade with a partner to check it against the six points above.

Sources

• Guidelines for Preventing Workplace Violence for Healthcare and Social Service Workers (OSHA 3148) (OSHA, 2016)

Heat Season Operations

In Phoenix, summer is an emergency that comes every year.

Maricopa County recorded 430 heat-related deaths in 2025, and 49 percent were people experiencing homelessness. About a quarter died indoors. Heat changes intake, overflow, outreach and safety for months.

Run it like an operation

• Two-stage notice: an early heads-up, then the full order
• Brief in a fixed order: situation, mission, execution, stakes, logistics, command
• Overflow steps down in a planned sequence
• Headcounts several times a day in shared space
• Receipts from day one for billing
• Track burn rate daily and report the run-out date early

How to run it

1. Send the early heads-up as soon as you know a surge is coming.
2. Read the mission word for word in the briefing so everyone hears the same thing.
3. Keep a staff member present in shared overflow space at all times.
4. Update the room roster with every move.
5. Know your cooling and water options for every person you see outdoors.

From the field

• Expect more families as summer starts. Heat and school breaks strain doubled-up households.
• City and county billing is slow and specific. Keep every receipt from the first day.

Drill: It is 9 p.m. during an extreme heat warning. Dedicated units are full and a family arrives. Walk through your options in order.

Sources

• 2025 Heat-Related Deaths Report (Maricopa County Department of Public Health, April 2026)

Staying in It

You cannot pour from an empty cup, and the work drains it daily.

Burnout and secondary traumatic stress are occupational hazards in this field, not personal weakness. Naming them early keeps good people in the work.

Professional quality of life (ProQOL)

• Compassion satisfaction: the good feeling of doing the work well
• Burnout: exhaustion, frustration, feeling ineffective
• Secondary traumatic stress: absorbing the trauma you witness
• Burnout plus secondary traumatic stress together make up compassion fatigue

How to run it

1. Take a self-check like the ProQOL every few months and watch your own trend.
2. Protect one admin block a week for notes and catch-up.
3. Debrief hard cases with someone, not alone in the car.
4. Know your agency's employee assistance options before you need them.

From the field

• New workers do better with one protected admin day a week for notes. Without it, documentation leaks into nights.

Drill: List three signs that you are moving from tired to burned out, and what you will do when you see each one.

Sources

• Professional Quality of Life Scale (ProQOL 5) (B. Hudnall Stamm, 2010)
• The Secondary Traumatic Stress-Informed Organization Assessment (Sprang et al., 2014 (hosted by the Office for Victims of Crime))

The One-on-One

The most important meeting a supervisor runs, and the one most often cancelled.

Managers account for most of the difference in how engaged a team is. The one-on-one is where coaching, feedback, priorities and trust happen in private, every week, before small problems get big.

Four schools of the one-on-one

• Grove: it is their meeting, their agenda; meet more often with people newer to the work
• Manager Tools: 30 minutes weekly, ten for them, ten for you, ten for the future
• Kadushin: every supervision session touches administrative, educational and supportive work
• Field model: a fixed running order (below) so nothing important gets skipped when time is short
• Google's research: being a good coach tops the list of manager behaviors

How to run it

1. Cadence by level: line staff weekly, coordinators every other week, managers and directors about monthly once aligned.
2. Book them yourself, early in the week, so you can watch the week's goals play out.
3. Ask them to bring their own agenda first.
4. Ask before you tell on strengths and areas to improve. How well they see their own gaps tells you how much you need to realign.
5. Close loops out loud: name what you own and write it down in front of them.
6. Send a short recap after.

From the field

• Predictability is the point. Staff should know the flow by heart. The test: anyone on the team can explain their goals, the department's goals and how they connect.
• Save minor corrections for the one-on-one so they happen in private. Anything serious, address the same day.
• Use a template that forces strengths and areas to improve every time. When problems come later, they are already on record.
• Keep a shared running notebook with a marker showing where new updates start.
• Treat metrics as joint work. "I'm thinking out loud, not talking at you." The metric is not there to nail people.
• Before reacting to a bad number, check how it was defined.

Drill: Run a 30-minute mock one-on-one using the field running order. The partner playing staff brings one hidden issue that only surfaces if you ask the whole-person question.

Sources

• High Output Management (Andrew S. Grove, 1983 (2nd ed. 1995))
• How to Run Effective One-On-Ones (Manager Tools)
• Supervision in Social Work, 5th ed. (Kadushin & Harkness, Columbia University Press, 2014)
• Following the data: the research behind great managers (Project Oxygen) (Google re:Work)
• Employees Want a Lot More From Their Managers (Harter & Adkins, Gallup, 2015)

Supervision's Three Jobs

Every supervisor does three jobs. Most only notice the first.

Social work supervision has administrative, educational and supportive functions. A supervisor who only checks compliance gets compliance and turnover. One who only supports gets warmth and drift.

Kadushin's three functions

• Administrative: assignments, policy, quality, workload
• Educational: building skill and judgment
• Supportive: morale, stress, meaning in the work
• Reflective supervision: thinking about cases together, not just checking them

How to run it

1. Audit your last four one-on-ones: which function took the time?
2. Add one educational question to every meeting: "What would you do differently on that case?"
3. Ask one supportive question and actually wait for the answer.
4. Keep administrative items short and written down.

From the field

• Teaching is the fastest way to learn your own program. Coordinators should go home tired from explaining.
• You know your coaching has worked when staff can finish your sentences.

Drill: Map your last week of supervision time across the three functions. Pick one change for next week.

Sources

• Supervision in Social Work, 5th ed. (Kadushin & Harkness, Columbia University Press, 2014)

Feedback That Lands

Same day, private, specific.

Feedback delayed a week loses its meaning, and feedback without specifics gets argued with. A simple structure makes hard feedback easier to give and easier to hear.

SBI and SBII

• Situation: when and where
• Behavior: what you observed, not your interpretation
• Impact: what it caused
• Intent: ask what they were trying to do
• Pink flag before red flag: reward people who raise problems early

How to run it

1. Give it the same day, or record it that day for the one-on-one.
2. Describe behavior you could film, not character.
3. State the impact on clients, team or program.
4. Ask about intent and listen.
5. Agree on what happens next time.

From the field

• Timing is everything. Waiting a week loses the moment, and later the person does not know why they were let go.
• If you let things slide, people will like you but not respect you. Expect a few days of resentment, then respect.
• Raise attendance patterns at a calm moment, not right after a hardship.
• Separate a lone low performer from someone who pulls others into bad behavior. The second needs faster action.

Drill: Turn three vague comments ("be more professional", "you're not a team player", "great job") into SBI statements.

Sources

• Use Situation-Behavior-Impact (SBI) to Understand Intent (Center for Creative Leadership)

Coaching with GROW

Ask more than you tell.

Telling solves today's problem. Coaching builds the judgment that solves next month's problem without you. The best managers in Google's research were good coaches first.

GROW

• Goal: what do you want out of this?
• Reality: what is actually happening?
• Options: what could you do?
• Will: what will you do, and when?

How to run it

1. Use GROW when someone brings you a problem they can solve.
2. Stay in Reality longer than feels natural. Most bad plans skip it.
3. Get at least three options before discussing any of them.
4. End with a specific commitment and a date.

From the field

• Tell people how many miles. They cope with a hard march if they know the distance. Explain the math behind targets.
• "I don't know, I'll find out" builds credibility.
• Give coordinators a short daily routine before the day goes live: budget, KPIs, caseloads, pacing. "It's the 15th and we're at 30 of 75" is a mid-month alarm, not a month-end surprise.

Drill: Coach a partner through a real problem using only questions for ten minutes.

Sources

• The GROW Model (John Whitmore, Coaching for Performance (Performance Consultants))
• Following the data: the research behind great managers (Project Oxygen) (Google re:Work)

Situational Leadership and Delegation

Same person, different task, different leadership.

New staff need direction; experienced staff need room. The mistake is using one style for everyone, or one style for one person across every task.

Situational leadership

• Directing: high direction, low support, for new and eager
• Coaching: high direction, high support, for learning and discouraged
• Supporting: low direction, high support, for capable but unsure
• Delegating: low direction, low support, for capable and confident

How to run it

1. Diagnose by task, not by person.
2. Say which style you are using and why.
3. Delegate the outcome, not the steps, once someone is ready.
4. Check in at agreed points, not randomly.

From the field

• Use a potential and performance grid, and keep re-checking your labels. High potential with low performance is the quadrant most worth developing.
• Be careful of wanting it for someone more than they want it.
• Promotions should be asked for. Test readiness with extra duties first.

Drill: List your team and three tasks each. Mark which style each person needs on each task.

Sources

• Situational Leadership After 25 Years: A Retrospective (Blanchard, Zigarmi & Nelson, 1993 (model by Hersey & Blanchard, 1969))

Accountability and Corrective Action

Fair, documented, and never a surprise.

Corrective action protects clients, the team and the employee when it is fair and consistent. Done badly, it damages trust and creates risk. This module is general practice guidance; follow your agency's policy and HR.

Fair accountability

• Expectations were clear and written
• Problems were raised early, in one-on-ones
• Facts gathered calmly, not while angry
• One issue per document
• Direct supervisor builds or co-signs the plan
• HR involved in serious steps
• Accommodation requests go through the interactive process

How to run it

1. Confirm the expectation was clear and in writing.
2. Raise it privately and early; document the conversation.
3. Separate conduct findings from development plans.
4. Involve HR before any formal step.
5. If health or disability comes up, route it through the accommodation process.

From the field

• Do not fold separate issues into one document.
• A plan issued without the direct supervisor badly damages trust between them.
• When closing the loop with someone who made a complaint, share the finding on their allegation, not what happened to other people.
• Quietly cutting someone's hours instead of making a clean decision looks like retaliation.
• "The director said" should not be the authority. The policy is.

Drill: A staff member is late eight times in a month. Write the first documented conversation using SBI.

Sources

• Enforcement Guidance on Reasonable Accommodation and Undue Hardship under the ADA (U.S. EEOC, 2002)
• Use Situation-Behavior-Impact (SBI) to Understand Intent (Center for Creative Leadership)

Trust, Friction and Team Conflict

Earn the right to challenge in the other 39 hours.

Teams learn when people feel safe to speak up and are held to high standards. Without safety, problems hide. Without standards, comfort replaces performance.

Psychological safety

• Teams with psychological safety show more learning behavior, which predicts performance
• Safety plus high standards is the learning zone (Edmondson's later framing)
• Friction: questioning that still trusts the other person
• Conflict: adversarial, about winning
• Emotional bank account: people forgive those who made deposits

How to run it

1. Agree as a team that feedback goes directly to the person, never sideways.
2. Name friction and conflict as different things.
3. In readouts, keep questions two or three levels deep; take the rest offline.
4. Start hard group sessions with easy, concrete requests.
5. After a falling-out, ease back in slowly.

From the field

• Earn the right to challenge someone in a meeting by investing in the relationship between meetings.
• "We're fine" while venting elsewhere is not resolution.
• Use an anonymous poll to name the gap between vision and today.
• Before carrying a decision down, ask yourself whether you can deliver it honestly. If not, object now.

Drill: Write the team agreement you would propose on how disagreements get raised.

Sources

• Psychological Safety and Learning Behavior in Work Teams (Amy Edmondson, Administrative Science Quarterly, 1999)

Coverage and Continuity

If results depend on one hero, they collapse when the hero takes a vacation.

People take leave, get sick and move on. Coverage that is planned keeps clients safe and lets people actually rest.

Coverage that works

• Weekly huddle opens with who is out and who is in
• Role-based backup named in the auto-reply
• Written handoff with the boss copied
• Never one leader alone on a site
• How-to guides for every recurring task

How to run it

1. Open every huddle with this week's and next month's absences.
2. Before leave, send who covers what and the staffing plan, boss copied.
3. Set an auto-reply naming your backup and supervisor.
4. Be fully out. A half-present leader slows on-site decisions.
5. Review each role's duties quarterly and write how-tos.

From the field

• Log call-outs as unscheduled leave so patterns show over time.
• Results that depend on individual heroics collapse when that person is out.

Drill: Write the coverage handoff you would send if you left tomorrow for a week.

Onboarding: The First 100 Days

Retention is decided in the first 100 days.

New case managers learn on real clients if you let them. Planned onboarding with practice, spacing and feedback gets them competent faster and keeps them longer.

30-60-90 with practice built in

• Days 1-30: shadow, learn systems, practice in simulation
• Days 31-60: carry a partial caseload with daily check-ins
• Days 61-90: full caseload, weekly one-on-ones, first file review
• Spaced practice beats one long orientation
• Practice testing beats rereading

How to run it

1. Schedule practice scenarios in week one, not after the first mistake.
2. Revisit key skills at days 7, 30 and 60.
3. Give new staff one protected admin day a week.
4. Adapt to how each person learns: some hands-on, some visual.
5. Run a short AAR at day 30, 60 and 90.

From the field

• Onboarding, orientation and culture rarely make the strategic plan, but they are the blocking and tackling.
• Training works best on a set rhythm, with operations skills and career development mixed together.

Drill: Draft a 30-60-90 plan for a new case manager starting Monday.

Sources

• Test-Enhanced Learning (Roediger & Karpicke, Psychological Science, 2006)
• Distributed Practice in Verbal Recall Tasks (Cepeda et al., Psychological Bulletin, 2006)
• Simulation in Social Work Education: A Scoping Review (Kourgiantakis et al., Research on Social Work Practice, 2020)

Case Conferencing and File Review

Bring the hard case early, with the whole story.

File review and case conferencing catch problems before clients pay for them. They also teach judgment across the team.

Review rhythm

• Monthly: five random files per worker
• Weekly: hard cases to staffing, with full background
• Cross-check data between systems
• Refresher on report pulls every six months
• Average numbers can hide individual clients

How to run it

1. Pull five random files per worker each month.
2. Check that notes match the data system.
3. Look at weekly detail by client, not only monthly averages.
4. Turn findings into coaching, not punishment.
5. Bring hard cases to staffing before they become crises.

From the field

• A monthly contact average can look great while two clients have not been seen in 25 days.
• Before believing something is a funder requirement, find it in the actual contract.

Drill: Review a fictional file and list three things you would coach.

Sources

• PDSA Cycle (The W. Edwards Deming Institute)

Secondary Trauma and Retention

Turnover is a safety issue for clients, not just a staffing one.

Every departure breaks relationships clients depended on. Organizations can measure and reduce secondary traumatic stress instead of leaving it to individuals.

STS-informed organization

• Resilience-building activities
• Promotion of safety
• STS-informed policies
• STS-informed leadership practices
• Routine organizational practices
• Evaluation and monitoring

How to run it

1. Assess your program with a tool like the STSI-OA once a year.
2. Build debriefs into the schedule after critical incidents.
3. Watch caseloads and admin time, not just morale.
4. Ask in one-on-ones what is wearing on people.

From the field

• Treat a staff safety concern as urgent from the first report. Waiting until an incident proves it right damages trust for a long time.

Drill: Score your program on the six domains from 1 to 5. Pick the lowest and one fix.

Sources

• The Secondary Traumatic Stress-Informed Organization Assessment (Sprang et al., 2014 (hosted by the Office for Victims of Crime))
• Professional Quality of Life Scale (ProQOL 5) (B. Hudnall Stamm, 2010)

Running the After-Action Review

Learn from every shift, not just the bad ones.

The Army built its learning culture on the after-action review. It is short, blame-free and focused on what to sustain and improve. It works just as well after an intake, an incident or a hard week.

The AAR

• Start with what was supposed to happen
• Then what actually happened
• Why it happened
• What to sustain and what to improve
• Everyone speaks, rank does not decide what is true

How to run it

1. Hold it soon, while memory is fresh.
2. Set the rule: facts, not blame.
3. Have the most junior person speak first.
4. Write down two sustains and two improves.
5. Assign one improvement an owner and date.

From the field

• Every scenario in The Box ends with an AAR in this format.

Drill: Run a ten-minute AAR on your last team meeting.

Sources

• TC 25-20: A Leader's Guide to After-Action Reviews (Department of the Army, 1993)

Present an Idea So It Gets Decided

Lead with the answer. Then earn it.

Good ideas die in bad presentations. Boards, funders and executives decide fast and remember little, so the structure of your ask matters as much as the evidence behind it.

Pyramid, SCQA and stickiness

• Lead with the answer, then the three reasons, then the evidence (Minto)
• Open with Situation, Complication, Question, Answer
• Cut everything extraneous; signal what matters (Mayer)
• Simple, unexpected, concrete, credible, emotional, stories (Heath)
• Ask in terms of impact, never grievance

How to run it

1. Write the one sentence you want them to repeat after the meeting.
2. Build SCQA: what is true now, what changed, the question it raises, your answer.
3. Give three reasons, each with one piece of evidence.
4. Name one specific ask: amount, decision, date.
5. Check every number matches across every slide.

From the field

• Rotate presenters and rehearse with a friendly audience first.
• Expert shorthand loses a lay audience. Pick presenters for whether they can teach.
• Build two decks: a standard one and a deeper one for returning audiences.
• People light up at "where do I fit in?" before program detail.
• "We spent X and it moved Y, so sustain it" beats "we're running out of money."

Drill: Rewrite a budget request you have seen into SCQA in five sentences.

Sources

• The Minto Pyramid Principle (Barbara Minto)
• Principles for Reducing Extraneous Processing in Multimedia Learning (Mayer & Fiorella, Cambridge Handbook of Multimedia Learning, 2014)
• Made to Stick (Chip Heath & Dan Heath, 2007)

Metrics That Mean Something

Before any percentage goes out, ask: out of what?

A wrong denominator can make a struggling program look great or a strong one look broken. Leaders make funding and staffing decisions from these numbers, so their meaning has to be checked before they travel.

Out of what?

• Enrollments are not people: 120 enrollments can be 100 people
• Persons are not households: say which you counted
• Small samples swing: a rate on ten exits is a story, not a trend
• Accurate can still mislead: a rate can rise while people served falls
• Numbers settle over time: date every number you share
• Measure what you mean: a note is not a face-to-face visit

How to run it

1. Write a one-line definition for every headline number: what is counted, out of what, over what period.
2. Report persons and households side by side when both matter.
3. Show volume next to every rate.
4. Check a surprising number against a second source before reacting.
5. Look first at controllable inputs under a bad outcome: timeliness, contacts, data completeness.

From the field

• The most common reporting error is the wrong denominator, like dividing one worker's positive exits by all program exits.
• Missing fields pull outcome numbers down and make good work look bad. Give teams a short regular list of their data errors.
• Quarterly rates swing early in the quarter. Do not react to a week-three number.
• Income recorded only at exit erases evidence of progress. Update it when it changes.

Drill: A program reports 92 percent placed: 46 of 50. Fourteen people enrolled twice. Recalculate on unique people and write the two-sentence correction for the board.

Sources

• PDSA Cycle (The W. Edwards Deming Institute)
• Leverage Points: Places to Intervene in a System (Donella Meadows, 1999)

The Monthly Rhythm

No surprises at the monthly meeting.

A steady reporting rhythm turns numbers into decisions. Without it, every monthly meeting becomes a debate about whose number is right.

Number, why, action

• Weekly written update to your boss
• Monthly: state the number, why it moved, the action and its date
• Process measures first: timeliness, contacts, data completeness
• One census source and one time to read it
• Staffing math adds up: start, plus hires, minus departures

How to run it

1. Send a short weekly written update every Friday.
2. Pick the Monday census as the number for the week.
3. In the monthly report, compare to last month and explain changes.
4. Name the levers you control when reporting bad news.

From the field

• Open every one-on-one with the numbers until staff know them before you ask.
• If a ninth grader could not follow your report, rewrite it.
• A highlights list is not a narrative.

Drill: Write a monthly update for a fictional program with one number up and one down.

Sources

• PDSA Cycle (The W. Edwards Deming Institute)

Grant Compliance and Spend Pacing

A gap found five months out is a request. Found two months out, it is a crisis.

Restricted funds come with rules, timelines and reporting. Under-spending can mean fewer people served and money returned; over-spending can mean costs you cannot recover. Pacing is a program skill, not just a finance one.

Pace it from the start

• Monthly target: budget divided by average cost per household, divided by months
• Recalculate average cost every cycle from actual payments
• Set an escalation threshold in advance
• Programs own implementation; finance owns compliance; both watch
• Know how each funder defines success
• Federal awards: 2 CFR 200 thresholds (2024 revision; confirm current figures)

How to run it

1. Turn every rental budget into a monthly lease-up target.
2. Review actual against target in every grant meeting.
3. Agree on the threshold that triggers escalation.
4. Name one owner per grant.
5. Flag reimbursement lag before a reviewer misreads it.

From the field

• An assumed cost that is too high makes you under-enroll and under-spend. Family size moves rent a lot.
• When the one person who held a grant's details leaves without cross-training, the risk can stay hidden for months.
• Get "probably fine" from a funder confirmed in writing.

Drill: A $900,000 grant assumed $15,000 per household. Actual is $11,000. Recalculate the monthly target for the remaining six months.

Sources

• Guidance for Federal Financial Assistance (2 CFR 200 revision) (OMB, 89 FR 30046, 2024)

Budget Literacy for Program Leaders

A variance is a question, not a verdict.

Program leaders who can read a budget make better decisions and better requests. Most variance panics are timing, coding or inventory, not real overspending.

Read it in order

• Check the report date first
• Total budget by line
• Year-to-date budget: annual ÷ 12 × months elapsed
• Year-to-date actual against it
• Parentheses mean over
• Ask why before you act

How to run it

1. Keep a real-time ledger of your three to seven riskiest lines.
2. Handle receipts weekly, kept in two or three places.
3. Raise miscoding or missing items early.
4. When you need funds, go through the finance lead.

From the field

• An annual software purchase looks like overspending in month one.
• A funded line you never use weakens next year's request.
• Teach the myths: a nonprofit can run a surplus; low overhead is not the same as good management; a government award is a right to be reimbursed, not cash in the bank.

Drill: Transportation is $6,400 over year to date. List the three things you would check before freezing anything.

Working with a Board

Most board friction starts with unclear roles.

Boards govern; staff manage. When either side drifts, trust erodes and decisions slow. Clear roles, steady education and clean conflict-of-interest practice keep the relationship productive.

Three duties

• Care: act as an ordinarily prudent person would
• Loyalty: the organization's interest first
• Obedience: follow the law, the bylaws and the mission
• Board provides oversight, not unpaid staffing
• Committees as task forces with end dates

How to run it

1. Spell out what belongs to the board, committees and staff.
2. Educate in small pieces each meeting.
3. Send packets in advance; print the agenda and financials in large type.
4. Anchor on the mission; do not debut unadopted strategy language.
5. State plainly that board service carries no vendor preference.

From the field

• When a new board leader struggles, ask whether anyone trained them on the role.
• In a quiet campaign, give a near-term milestone or a range, not a total you know will change.

Drill: Draft a one-page role chart: board, finance committee, executive, program director.

Sources

• What are the Legal Duties of Nonprofit Board Members? (BoardSource)

Leading Change

Organizations change one person at a time.

New systems, new rules and new funders all require people to work differently. Most change fails at the human level, not the plan.

Kotter and ADKAR

• Kotter: urgency, coalition, vision, volunteer army, remove barriers, short-term wins, sustain, institute
• ADKAR: Awareness, Desire, Knowledge, Ability, Reinforcement
• Diagnose which ADKAR step a person is stuck on

How to run it

1. Explain why before what.
2. Find early adopters on the frontline, not only managers.
3. Train after desire, not before.
4. Celebrate a visible early win.
5. Write policy changes down; verbal changes drift.

From the field

• A verbal policy change can leave two sites enforcing different rules.

Drill: Pick a change you need. Name where each team member sits on ADKAR.

Sources

• The 8-Step Process for Leading Change (Kotter Inc.)
• The Prosci ADKAR Model (Prosci)

Transitions and Continuity

"Can she?" and "will she?" are different questions.

Leaders leave, go on duty, get sick. Planned continuity keeps payroll, purchasing, supervision and reporting moving without heroics.

Continuity checklist

• Line-by-line coverage check: time cards, PTO, check requests, card access, reports, supervision
• Interim coverage is a request, then confirmed with HR
• Each interim has a written success measure
• Sequence announcements: closest funders, internal, public
• Grow successors on purpose

How to run it

1. Run the coverage check before any planned absence.
2. Grant system access before it is needed.
3. Reduce the interim's existing load before adding scope.
4. Write the success measure for each inherited program.

From the field

• Gaps usually show up in finance and system access.
• Judge senior people on decisions, not hours.

Drill: Run the coverage check on your own role.

Meetings That Decide

If nobody wrote down the decision, it was not made.

Meetings consume leadership time. A meeting without a recorded decision and owner is a conversation that will happen again.

Decide, record, own

• Pre-reads and agenda sent ahead
• Decision packages your team prepares
• Decisions recorded with an owner and date
• Discrepancies resolved before the meeting
• A fixed briefing order for operations

How to run it

1. Send pre-reads 48 hours ahead.
2. Open with the decisions needed today.
3. End by reading back decisions and owners.
4. Post the decision log where everyone can see it.

From the field

• An approved hire can go unfilled for months because nobody was sure it was decided.
• Do not argue with the dashboard in front of the executive. Check discrepancies with the data team first.
• When replies to routine updates fall off, morale usually is too.

Drill: Take your next meeting's agenda and rewrite each item as a decision to be made.

Sources

• TC 25-20: A Leader's Guide to After-Action Reviews (Department of the Army, 1993)

Safety, Staffing and Risk

Design for the program at full staff, not this month's shortage.

Social service settings carry real workplace violence risk. Safety programs, drills and staffing decisions are leadership decisions, made before an incident forces them.

OSHA's five building blocks

• Management commitment and worker participation
• Worksite analysis and hazard identification
• Hazard prevention and control
• Safety and health training
• Recordkeeping and program evaluation

How to run it

1. Run drills and write down every gap they expose.
2. Assign muster areas and a headcount method in advance.
3. Stage overflow plans with clear triggers.
4. Revisit structural changes made during shortages after two months at full staff.

From the field

• Drills commonly expose accessible rooms on upper floors, inconsistent muster points and no headcount method.
• Give every rule a safety valve: a same-week makeup beats "come back in two weeks" when the alternative is the street.

Drill: Walk your site and list five hazards using the worksite analysis lens.

Sources

• Guidelines for Preventing Workplace Violence for Healthcare and Social Service Workers (OSHA 3148) (OSHA, 2016)

Systems Thinking and Leverage Points

The weakest lever is the one everyone pulls first.

Most fixes adjust numbers: more beds, more funding, a higher target. Meadows showed that information flows, rules, goals and mindsets move systems far more. Human services is a system of systems.

Leverage points (selected)

• Parameters: numbers like budgets and targets (weakest)
• Delays and buffers: how fast information and help move
• Information flows: who sees what, when
• Rules: incentives, eligibility, policies
• Goals: what the system is trying to do
• Paradigms: the beliefs the system runs on (strongest)

How to run it

1. Map one client journey across agencies, step by step.
2. Mark every delay and every place information is lost.
3. Ask which rule or information flow would change behavior most.
4. Test the smallest change at the highest lever.

From the field

• A referral that disappears between agencies is an information-flow problem, not a funding problem.

Drill: Map how a family gets from first call to housed in your area. Circle the three biggest delays.

Sources

• Leverage Points: Places to Intervene in a System (Donella Meadows, 1999)

Program Design: Logic Models

If you cannot draw it, you cannot fund it or fix it.

A logic model makes your theory of change visible: what you put in, what you do, what it produces and what changes because of it. Funders ask for it, and it keeps teams honest about what activities actually cause.

Kellogg logic model

• Inputs: staff, money, partners
• Activities: what you do
• Outputs: counts of what you did
• Outcomes: changes in people, short and long term
• Impact: the lasting change in the community

How to run it

1. Start from the outcome and work backward.
2. Separate outputs (classes held) from outcomes (jobs kept).
3. Name the assumption behind each arrow.
4. Pick one measure per outcome and define it fully.

From the field

• Programs often report outputs as if they were outcomes.

Drill: Draw a logic model for a 90-day job readiness program.

Sources

• Logic Model Development Guide (W.K. Kellogg Foundation, 2004)

Run a Pilot Like a Scientist

Predict first, then test.

New ideas are cheap; knowing whether they work is not. Small, fast test cycles let you learn before you scale.

PDSA

• Plan: what you will change and what you predict
• Do: run it small
• Study: compare results with your prediction
• Act: adopt, adapt or abandon

How to run it

1. Write the prediction down before you start.
2. Test with one team for two weeks, not everyone for a year.
3. Decide in advance what result would make you stop.
4. Share what failed as openly as what worked.

From the field

• Collect a few weeks of no-show and attrition data before changing intake rules.

Drill: Design a two-week PDSA to reduce intake no-shows.

Sources

• PDSA Cycle (The W. Edwards Deming Institute)

Ethics Under Pressure

The hard calls are between two good things.

Most ethical dilemmas in this work are not right versus wrong. They are safety versus autonomy, fairness to one versus fairness to many, honesty versus harm. A shared method makes these calls more consistent.

A decision method

• Name the values in tension
• Gather facts and who is affected
• Check law, policy and professional codes
• Consider options, including ones not offered
• Decide, document the reasoning, review later

How to run it

1. Say the dilemma out loud as two values.
2. Consult a supervisor or peer before deciding alone.
3. Write down why, not just what.
4. Revisit the decision in your next AAR.

From the field

• Treating someone's refusal as an automatic exit escalates for no gain. Look for the option that keeps both safety and dignity.

Drill: A client asks you not to record their part-time income. Work through the method.

Sources

• NASW Code of Ethics (National Association of Social Workers)

Crisis Leadership: The First 24 Hours

Facts first. Care continues. One voice.

Serious incidents test every system at once: safety, documentation, legal duties, staff wellbeing and public trust. What leaders do in the first day shapes everything after.

First-day sequence

• Safety and care for the people involved
• Required reports made immediately
• Fact sheet built before decisions
• Legal and insurance guidance
• Frontline continues normal care, does not investigate
• One designated voice for communication
• Staff debrief and support

How to run it

1. Confirm everyone is safe and receiving care.
2. Confirm mandated reports were made.
3. Build a fact sheet from the incident reports.
4. Brief the board chair and key funders before they hear elsewhere.
5. Schedule the staff debrief and the AAR.

From the field

• A pre-built escalation template cuts hours off a crisis.
• A supervisor, not frontline staff, flags a report for executive escalation.

Drill: Draft the first three messages you would send after a serious incident: to staff, to the board chair, to a funder.

Sources

• Guidelines for Preventing Workplace Violence for Healthcare and Social Service Workers (OSHA 3148) (OSHA, 2016)
• TC 25-20: A Leader's Guide to After-Action Reviews (Department of the Army, 1993)

Responsible AI in Human Services

Human-led. AI-assisted. Evidence attached.

Nonprofit staff are already using AI, often without guidance. Used well, it drafts, summarizes, translates and checks. Used carelessly, it leaks client data or invents facts.

Risk ladder for AI use

• Low: drafting public content, summarizing public sources
• Medium: internal templates, training scenarios with fictional data
• High: anything touching client information
• Humans own eligibility, safety, placement and publication decisions
• Never put identifying client data in a public AI tool

How to run it

1. Write a one-page AI guidance for your team.
2. Use fictional or de-identified examples only.
3. Verify every fact and citation AI gives you.
4. Disclose AI assistance where it matters.

From the field

• Only about 18 percent of nonprofits in a 2026 survey train staff on AI tools, while 45 percent use AI daily or more.

Drill: Sort ten common tasks on your team onto the risk ladder.

Sources

• State of Nonprofit AI Adoption and Governance (NTEN & The Bridgespan Group, 2026)

Designing Training That Sticks

People forget most of a training within days unless they practice.

Slides and shadowing do not build skill on their own. Retrieval practice, spacing and simulation do. This academy is built on those principles.

The science of practice

• Forgetting is fast without review
• Practice testing beats rereading
• Spacing beats cramming
• Simulation lets people practice before real clients
• The AAR turns practice into learning

How to run it

1. Replace one lecture with a scenario.
2. Schedule reviews at 1, 7 and 30 days.
3. End every drill with an AAR.
4. Track skills practiced, not hours attended.

From the field

• Training runs best on a set rhythm, with operations skills and career development mixed.

Drill: Turn your next team training into three scenarios and a ten-minute AAR.

Sources

• Replication and Analysis of Ebbinghaus' Forgetting Curve (Murre & Dros, PLOS ONE, 2015)
• Test-Enhanced Learning (Roediger & Karpicke, Psychological Science, 2006)
• Distributed Practice in Verbal Recall Tasks (Cepeda et al., Psychological Bulletin, 2006)
• Simulation in Social Work Education: A Scoping Review (Kourgiantakis et al., Research on Social Work Practice, 2020)

Reading Data for Who Is Missing

Your data shows who you served. Ask who it does not show.

Access gaps hide in the difference between who calls, who enters and who exits successfully. Comparing those stages reveals barriers no one reports.

Stage comparison

• Compare who calls, who is screened, who enters, who exits well
• Look for drop-offs by language, age, household type and location
• Check whether eligibility screens or hours exclude groups
• Ask people who did not come back why

How to run it

1. Pull counts at each stage for one quarter.
2. Break them down by two or three groups.
3. Find the stage with the biggest gap between groups.
4. Talk to five people who dropped off there.

From the field

• Differing eligibility screens across shelters can make a list look unfair when the real driver is volume. Explain screens openly.

Drill: Sketch a funnel for your program from memory, then check it against real counts.

Sources

• Leverage Points: Places to Intervene in a System (Donella Meadows, 1999)