I was thirsty

An outreach mission putting safe water in the hands of vulnerable people

THE REPLICATION PLAYBOOK

HOW TO DO IT

I WAS THIRSTY - THE PLAYBOOK - VERSION 1.0

How to Build, Launch and Run a Community Water Outreach Mission

The Guide tells you what the model is.

The Playbook tells you what to do.

BEFORE WE BEGIN

If you are reading this book, you have probably already made the decision.

You have seen a need.

You have talked about it.

You have wondered whether somebody should do something.

And eventually someone said:

"Why don't we?"

Good.

That's where this book begins.

You don't need a warehouse.

You don't need a fleet of trucks.

You don't need fifty volunteers.

You don't need a million-dollar budget.

You need enough people to make the first trip, enough water to make the first delivery, a safe way to get there, and a willingness to come back.

The original I Was Thirsty mission began with three volunteers, a personal vehicle, donated and purchased water, a relationship with a local church and less than $250 in initial funding. The first 40 days produced approximately 9,000 bottles delivered.

That is important.

Because the first mistake a new organization can make is believing that it needs to become an organization before it can become a mission.

It doesn't.

Start the mission. BE FLEXIBLE. Build the organization around what the mission teaches you.

HOW TO USE THIS BOOK

Don't read this like a textbook.

Use it like a field manual.

If you're six weeks away from launching, go to the launch section.

If you're doing your first deployment tomorrow, go to the deployment checklist.

If you're having trouble getting water, go to the water chapter.

If you're dealing with a difficult incident, go to the incident section.

If you're thinking about expanding, read the scaling section before you buy another truck.

The Playbook is deliberately practical.

Throughout the book you'll see four recurring boxes:

DO THIS

The action you should take.

WATCH FOR THIS

Things that commonly go wrong.

SAY THIS

Suggested language you can actually use.

LEARN FROM THIS

Lessons from the Thunder Bay experience.

The objective is not to create perfect operations.

The objective is to help you avoid unnecessary mistakes.

PART I

BEFORE YOU START

CHAPTER 1

SOMEONE IS THIRSTY

Every mission starts with a problem.

Not a grant application.

Not a logo.

Not a website.

A problem.

Someone is thirsty.

The first question is therefore not:

"How much water can we distribute?"

It is:

"Is there a real unmet need here?"

That distinction matters.

If a community already has abundant, accessible drinking water available to the population you intend to serve, bottled-water outreach may not be the right intervention.

Your job is to identify the gap.

CHAPTER 2

PROVE THE NEED

Before you spend money, spend a few hours talking to people.

Start with organizations already working in the community.

Call:

shelters;
outreach workers;
food banks;
Indigenous organizations;
public health;
churches;
community agencies;
municipal staff;
people with lived experience.

Don't arrive with the answer.

Arrive with a question.

SAY THIS

"We're looking at establishing a volunteer water-outreach mission in the community. Before we do anything, we'd like to understand whether there's actually a need and whether we're duplicating something that's already being done."

Then listen.

Ask:

Where are people getting drinking water now?
When is water difficult to obtain?
Are there particular locations where access is poor?
Does extreme heat create additional problems?
Are there populations that are particularly isolated?
What services already exist?
What is missing?
Would a mobile water-delivery service actually help?

Write down what people tell you.

Don't rely on memory.

CHAPTER 3 FIND THE GAP

You are looking for a specific problem.

For example:

"People living in several outdoor locations have limited access to drinking water during summer afternoons, when existing services are closed or difficult to reach."

That's a useful problem statement.

This isn't:

"Homelessness is a problem."

That's true, but it's too broad.

Your mission isn't going to solve homelessness.

It may solve one small piece of the problem.

That's enough.

CHAPTER 4 DRAW THE MAP

You don't need sophisticated mapping software.

Start with a piece of paper.

Mark:

shelters;
encampments;
parks;
outreach locations;
cooling centres;
water sources;
community centres;
public washrooms;
food programs;
known service locations.

Then identify where the gaps appear.

Your first route will probably be imperfect.

That's okay.

Your first route is a hypothesis.

You will eventually engage in some reconnaissance and mapping.

Well before beginning regular operations, conduct a simple reconnaissance of the community.

In Thunder Bay we asked where people experiencing being unhoused and vulnerability and are, and then went there. We counted the number of shelters and tents, calculated approximately how many people may be present, and how the team can safely reach them.

For each location, we recorded:

the general location;
a map pin;
approximate number of tents or shelters;
estimated number of people;
how the location can be accessed;
any obvious safety concerns; and
anything else that would be useful to a future outreach team.

Then we created a map.

A simple mapping application such as Google Maps can be used.

Drop a pin at each location and give it a simple identifier, such as Site 01, Site 02, Site 03., or by use of common names. We recorded the same identifier in the reconnaissance notes.

The map does not need to be complicated. Its purpose is simply to help the team know where to go and what to expect.

Estimating Numbers

Population figures should be treated as estimates.

For example:

Approximately 15–20 people; 10 tents or shelters observed.

There is no need to identify individuals or conduct a formal census.

Safety and Privacy

Reconnaissance teams should remain together and should not enter a location simply to obtain better information. Observe from a safe position and respect private property and personal boundaries.

The reconnaissance map is an operational document. It should not be publicly shared or used to identify where vulnerable people are living.

***Map the locations. Don't map the people***

PEOPLE WILL NOT TRUST YOU IF THEY BELIEVE YOU ARE COLLECTING INTELLIGENCE INFORMATION ABOUT THEM.

Finally, remember that the first map will not be perfect. People move, circumstances change and new locations appear. Update the map as the team learns.

The first reconnaissance tells you where to start. The mission will tell you where you really need to go.

Your volunteers will teach you what the real practical routes need to be.

CHAPTER 5 DECIDE WHAT YOU ARE ACTUALLY GOING TO DO

Write one paragraph.

If you cannot explain the mission in one paragraph, you're probably trying to do too much.

Use this formula:

[Mission Name] provides [what] to [who] in [where] through [how], with the objective of [why].

For example:

The Riverside Water Mission provides bottled drinking water directly to people experiencing homelessness and vulnerability throughout Riverside through volunteer mobile outreach, with the objective of improving access to safe drinking water during the summer months.

That's enough.

Don't write twenty pages.

Not yet.

PART II

BUILD THE TEAM

CHAPTER 6

FIND THREE PEOPLE

Forget fifty volunteers.

Find three good people.

Ideally:

One organizer.

One driver.

One outreach person.

They don't necessarily have to be three different people.

The original mission demonstrated that a small team can begin the work.

Your first objective is not recruitment.

It is reliability.

Three people who show up are more valuable than thirty people who said they would.

CHAPTER 7 APPOINT ONE PERSON IN CHARGE

Someone needs to be responsible.

Not because the mission is hierarchical.

Because someone needs to answer:

"Who's making the decision?"

Call the position whatever you want:

Mission Coordinator;
Project Lead;
Director;
Operations Coordinator.

The title doesn't matter.

The responsibility does.

That person should know:

where the water is;
where the team is;
what the schedule is;
what money is available;
what problems exist;
who needs to be contacted.

CHAPTER 8 BUILD THE TEAM AROUND THE WORK

As you grow, establish four functions:

OPERATIONS

Deployments, routes, vehicles and field activity.

LOGISTICS

Water, equipment, storage and inventory.

PEOPLE

Volunteers, training and wellness.

ADMINISTRATION

Money, records, partnerships and reporting.

At the beginning, one person may do all four.

That's normal.

The important thing is to recognize when one person is doing too much.

PART III

GET THE WATER

CHAPTER 9

HOW MUCH WATER DO YOU NEED?

This is where many new missions get themselves into trouble.

They think:

"We need lots of water."

No.

You need to know:

How much water do we need for one deployment?

Start with:

Number of locations × estimated people × bottles per person

Then add a reasonable operational reserve.

Don't try to stock six months of water before your first deployment.

Your first objective is to learn your actual consumption.

CHAPTER 10 ASK FOR WATER

The easiest first donation may be a business donation.

Make the request concrete.

Don't say:

"Would you like to support our charity?"

Say:

"We're conducting a water-outreach deployment on Saturday and we're looking for 20 cases of bottled water. Would your company be willing to donate those cases?"

That's much easier to understand.

SAY THIS

"We're not asking you to fund an unknown program. We're asking you to help us put water directly into the hands of people who need it."

CHAPTER 11 WHEN THEY SAY YES

Excellent.

Now make it easy for them.

Ask:

When can we pick it up?
Where do we go?
Who should we speak with?
How many cases are available?
Is this a one-time or recurring donation?

Then document it.

A verbal promise is not inventory.

Don't count donated water until you have it.

CHAPTER 12 WHEN THEY SAY NO

Thank them.

Do not argue.

Do not guilt them.

Do not burn the relationship.

Say:

"Thank you for considering it. If circumstances change, we'd be grateful to speak with you again."

Then call the next organization.

A sustainable mission needs relationships, not victories.

PART IV

BUILD THE FIRST OPERATION

CHAPTER 13

THE VEHICLE

Your first vehicle may be somebody's car.

That's okay.

But water is heavy.

A case containing 24 × 500 mL bottles contains 12 litres of water alone, before packaging.

Know your vehicle's payload.

Know how much you're carrying.

Secure the load.

Don't put water where it obstructs the driver's vision.

Don't overload the vehicle because you're trying to impress yourself with how much you can deliver.

Safety beats volume.

CHAPTER 14 BUILD THE FIRST ROUTE

Your first route should be boring.

That's a compliment.

You want:

Start point → Location 1 → Location 2 → Location 3 → Location 4 → return.

Don't zigzag across town.

Group locations geographically.

Record:

departure time;
arrival time;
departure from each location;
kilometres;
water distributed.

After several deployments, compare the numbers.

You may discover that one location takes five minutes and another takes forty.

That's valuable information.

CHAPTER 15 THE TWO-PERSON RULE

Never make the first deployment a solo experiment.

Two people provide:

safety;
assistance;
observation;
accountability;
support.

The Guide already establishes this as a fundamental operational principle.

And here's the practical rule:

If your partner doesn't feel safe, you're done.

You don't debate it.

You don't say:

"We've only got three more stops."

You leave.

PART V

THE FIRST DEPLOYMENT

CHAPTER 16

THE NIGHT BEFORE

The Team Leader checks:

PEOPLE

☐ Two-person teams
☐ Driver confirmed
☐ Everyone knows meeting time

WATER

☐ Water available
☐ Quantity counted
☐ Load plan established

VEHICLE

☐ Fuel
☐ Tires
☐ Lights
☐ Load capacity
☐ Water secured

ROUTE

☐ Locations confirmed
☐ Access checked
☐ Alternate locations identified

COMMUNICATIONS

☐ Phones charged
☐ Emergency contacts available

WEATHER

☐ Forecast checked
☐ Appropriate clothing
☐ Heat/cold considerations

Then stop.

You've done enough.

CHAPTER 17 THE MORNING OF THE FIRST DEPLOYMENT

Arrive early.

Don't start with chaos.

The Team Leader conducts a five-minute briefing.

SAY THIS

"We're here to provide water. That's our job.
Stay together.
Don't enter tents or private structures.
Don't get involved in arguments.
If something doesn't feel right, tell me.
If we need to leave, we leave.
Nobody has to prove anything today.
We're going to treat everyone respectfully.
And when we get back, we'll talk about what we learned."

Then go.

CHAPTER 18 ARRIVING

Park somewhere safe and legal.

Before anybody gets out:

Look.

Don't immediately open the doors.

Observe:

people;
vehicles;
animals;
traffic;
fires;
debris;
unusual activity;
environmental hazards.

Then decide whether it is safe to approach.

This should become automatic.

Stop. Look. Think. Then act.

CHAPTER 19 THE FIRST APPROACH

Keep it simple.

SAY THIS

"Hi. We're with [Mission Name]. Would you like some water?"

That's it.

You don't need an introduction to the organization.

You don't need a speech.

You don't need to explain homelessness.

You don't need to ask questions.

Offer the water.

CHAPTER 20 IF THEY SAY YES

Give them the water.

If they want more and you have enough:

Give them more.

If you don't:

"I'm sorry, that's all I have with me today. We'll be back."

Don't promise a specific time unless you're certain.

CHAPTER 21 IF THEY SAY NO

Say:

"No problem. Take care."

And move on.

Don't persuade.

Don't say:

"Are you sure?"

Don't take rejection personally.

The water is an offer.

It is not a transaction.

CHAPTER 22 IF THEY WANT TO TALK

This will happen.

Sometimes the water will be gone in thirty seconds and the conversation will last twenty minutes.

You don't have to run away.

Listen.

But remember your role.

You are not a counsellor.

You are not a social worker.

You are not an addictions worker.

You are there to provide water.

If they want assistance beyond that, connect them with appropriate services when you can.

CHAPTER 23 IF SOMEONE ASKS FOR SOMETHING ELSE

This is one of the most important chapters in the book.

Someone may say:

"Can you give me money?"

"Can you take me somewhere?"

"Can you get me food?"

"Can you help me find housing?"

"Can you call my family?"

The answer doesn't have to be cold.

SAY THIS

"I'm sorry, that's not something we're set up to provide. We're here today to provide water."

Then, where appropriate:

"But I can tell you about [service/organization]."

Boundaries are not a lack of compassion.

They are what allow the mission to continue.

PART VI

WHEN THINGS GO WRONG

CHAPTER 24

THE GOLDEN RULE

There is one operational principle that should sit above everything else:

You cannot help someone if you become the person who needs help.

If the situation becomes unsafe:

Leave.

No argument.

No heroics.

No exceptions because you're almost finished.

CHAPTER 25 SOMEONE BECOMES AGGRESSIVE

Don't match aggression with aggression.

Create distance.

Use a calm voice.

SAY THIS

"We're going to head out now. We'll come back another time."

Then leave.

Do not:

argue;
threaten;
insult;
challenge;
physically intervene unless necessary to protect yourself from immediate harm.

Report the incident afterward.

CHAPTER 26 MEDICAL EMERGENCY

If someone appears to require emergency medical assistance:

Call 911.

Give:

location;
nature of emergency;
relevant observations.

Follow the dispatcher's instructions.

If volunteers are appropriately trained, they may provide appropriate first aid within their training and when safe to do so.

Otherwise:

Get out of the way and wait safely.

Your job isn't to become EMS.

CHAPTER 27 SUSPECTED OVERDOSE

Treat this as a medical emergency.

Call 911.

If the team has appropriate training and equipment, follow its approved overdose-response procedure.

Don't improvise.

Don't experiment.

Don't delay emergency assistance while trying to figure out what's happening.

CHAPTER 28 FIRE

Do not enter an encampment or structure to fight a fire.

Move away.

Call emergency services.

Provide the location.

If necessary, warn others from a safe position.

Then stay out of the way.

CHAPTER 29 UNKNOWN OBJECTS

You may encounter:

needles;
weapons;
drug paraphernalia;
chemicals;
unknown containers;
abandoned belongings.

Don't touch them.

Don't move them.

Don't investigate them.

Create distance and notify the appropriate person or service when necessary.

CHAPTER 30 POLICE ARRIVE

Your relationship with police should be professional.

You are not there to provide intelligence about people receiving water.

You are not there to enforce municipal bylaws.

You are not there to identify people.

But if police attend an emergency or operational incident, cooperate appropriately.

The mission's relationship with police should be based on coordination, safety and mutual understanding, not on turning outreach into policing.

PART VII

THE PEOPLE

CHAPTER 31

YOUR VOLUNTEERS ARE THE MISSION

The public will remember your volunteers.

Not your spreadsheet.

Not your logo.

Not your annual report.

The person who walked up and said:

"Would you like some water?"

is the mission.

Choose those people carefully.

CHAPTER 32 THE FIRST SHIFT

Never throw a new volunteer into the field without preparation.

Their first deployment should include:

orientation;
safety briefing;
experienced partner;
observation;
participation;
debrief.

Don't make the new person the Team Leader.

Let them watch.

Then participate.

Then lead when ready.

CHAPTER 33 WHAT MAKES A GOOD TEAM LEADER?

A good Team Leader isn't necessarily the loudest person.

They are the person who notices:

"Something has changed."

They know when to:

approach;
wait;
leave;
call for help;
change the route;
support a volunteer.

The best Team Leaders are usually calm people.

CHAPTER 34 VOLUNTEER WELLNESS

This deserves more attention than most organizations give it.

Your volunteers may see difficult things.

At the end of the shift, don't just say:

"Good job."

Ask:

"Are you doing okay?"

Then listen.

Don't force someone to talk.

Don't diagnose them.

Don't minimize what they experienced.

Just make sure they know the organization recognizes that outreach can affect people.

CHAPTER 35 CULTURAL HUMILITY

Do not arrive in another community believing that the Thunder Bay experience tells you everything you need to know.

It doesn't.

Especially when working in communities with significant Indigenous populations, establish relationships with local Indigenous organizations and seek local guidance.

The Guide appropriately frames this as relationship and humility rather than assuming that one Indigenous community represents another.

The rule is:

Listen before you lead.

PART VIII

THE DAILY BUSINESS

CHAPTER 36

COUNT EVERYTHING

At the end of every deployment, record:

bottles;
cases;
kilometres;
volunteers;
hours;
locations;
incidents.

Don't think:

"We'll remember."

You won't.

Record it immediately.

CHAPTER 37 THE DAILY SHEET

One sheet.

That's all you need.

DATE

TEAM LEADER

VOLUNTEERS

START KM

END KM

WATER LOADED

WATER DISTRIBUTED

WATER REMAINING

LOCATIONS VISITED

INCIDENTS

NOTES

VOLUNTEER WELLNESS CONCERNS

The simpler the form, the more likely it will actually be completed.

CHAPTER 38 INVENTORY

Use this equation:

Beginning inventory + received − distributed = ending inventory

If the numbers don't match:

Stop and find out why.

Don't carry unexplained discrepancies forward.

Small discrepancies become large ones surprisingly quickly.

CHAPTER 39 MONEY

From day one:

Keep mission money separate from personal money wherever practical.

Record:

donation;
date;
donor;
amount;
purpose if restricted;
expenditure;
receipt.

Never rely on:

"I think I spent about $200."

You should be able to answer:

"We received $4,200 and spent $3,870. Here's where every dollar went."

That's accountability.

CHAPTER 40 YOUR MOST IMPORTANT NUMBER

You will eventually have lots of statistics.

But one of the simplest is:

COST PER BOTTLE

Total mission expenditure ÷ bottles distributed

The Thunder Bay experience produced a very low cost per bottle, but the Guide correctly warns that another community should measure its own costs rather than treating Thunder Bay's result as a required benchmark.

The goal isn't:

"Can we beat Thunder Bay?"

The goal is:

"Are we using resources responsibly?"

PART IX

PARTNERS

CHAPTER 41 YOUR FIRST CORPORATE PARTNER

Don't begin by asking for $100,000.

Ask for something achievable.

For example:

"Would you consider donating 20 cases of bottled water for our first month's deployments?"

Then prove yourselves.

Deliver.

Report.

Thank them.

Come back.

CHAPTER 42 THE PARTNERSHIP CYCLE

A good partnership follows a simple cycle:

ASK → DELIVER → REPORT → THANK → RETURN

Don't disappear after receiving a donation.

Tell the partner what happened.

"The water you donated supported four deployments and 620 bottles were distributed."

That's much more powerful than:

"Thanks for your donation."

CHAPTER 43 CHURCHES AND FAITH COMMUNITIES

Faith communities can provide:

volunteers;
storage;
financial administration;
transportation;
water;
meeting space.

But don't assume that a faith-based partner means the outreach itself becomes faith-based.

Water should remain unconditional.

If someone wants to talk about faith, that's different.

The recipient should never feel that water comes with a sermon attached.

CHAPTER 44 MUNICIPAL GOVERNMENT

Tell them what you're doing.

Don't necessarily ask them to run it.

A useful first conversation is:

"We're establishing a volunteer water-outreach mission and wanted to make sure the municipality understands what we're doing and to learn whether there are any local considerations we should be aware of."

You may discover:

useful information;
access concerns;
safety issues;
existing resources;
potential partners.

PART X

TELLING THE STORY

CHAPTER 45 DON'T TURN PEOPLE INTO CONTENT

This is one of the most important rules in the entire Playbook.

The people you serve are not your marketing campaign.

The Guide establishes a strong default position: don't photograph recipients unless they voluntarily consent, and never make assistance conditional on photography or storytelling.

You can tell the story using:

volunteers;
vehicles;
water;
statistics;
partnerships;
equipment;
routes;
landscapes.

You don't need someone's worst day to prove your mission matters.

CHAPTER 46 IF THE MEDIA CALLS

Designate one spokesperson.

Volunteers should know:

"Please speak with our Mission Coordinator."

That prevents inconsistent messages.

Your central message should be simple:

"We identified a gap in access to drinking water and built a volunteer operation to address it."

Don't claim to have solved homelessness.

You haven't.

You have provided water.

Own exactly what you accomplished.

PART XI

THE FIRST 30 DAYS

CHAPTER 47 WEEK ONE

Objective:

Learn.

Do your assessment.

Talk to organizations.

Map locations.

Recruit the first people.

Don't worry about the website.

Don't worry about the logo.

CHAPTER 48 WEEK TWO

Objective:

Build.

Secure:

water;
vehicle;
volunteers;
route;
basic records;
insurance/legal requirements;
emergency contacts.

CHAPTER 49 WEEK THREE

Objective:

Test.

Run a small deployment.

Don't advertise 5,000 bottles.

Deliver 100.

See what happens.

CHAPTER 50 WEEK FOUR

Objective:

Learn and adjust.

Ask:

Did we have enough water?
Was the route right?
Did people understand us?
Were volunteers comfortable?
What hazards did we miss?
What did people ask for?
Who should we partner with?
What should change?

Then change it.

PART XII

GROWING UP

CHAPTER 51 THREE BECOMES TEN

This is when the operation starts changing.

You now need:

schedules;
training;
team leaders;
volunteer records;
communications;
inventory management.

Don't keep operating like a three-person group when you're a ten-person group.

The structure needs to grow with the mission.

CHAPTER 52 ONE VEHICLE BECOMES TWO

Before adding a vehicle, ask:

Do we actually need it?

Then ask:

Who will operate it?

Then:

Who will pay for it?

Then:

Who will maintain it?

Then:

Who will insure it?

The answer should never simply be:

"Because we're growing."

CHAPTER 53 DON'T GROW FASTER THAN YOUR SYSTEMS

The Guide identifies scaling as a progression from pilot, to regular outreach, to community mission, to regional activity and ultimately independent replication.

That's sensible.

Use the same discipline internally.

First make it work.

Then make it reliable.

Then make it efficient.

Then make it bigger.

Not the other way around.

PART XIII

WHEN SOMEONE ELSE WANTS TO DO IT

CHAPTER 54 LET THEM

This is perhaps the most important philosophical chapter.

If another volunteer says:

"I want to do what you're doing."

Let them.

If another community says:

"We want to do what you're doing."

The correct response isn't:

"How much are you going to pay us?"

It's:

"Great. Let's help you figure it out."

The objective of replication is not to create branches controlled from Thunder Bay.

The Guide explicitly establishes that principle.

The test of the model is whether someone else can eventually operate it without you.

CHAPTER 55 WHAT THEY GET FROM YOU

A new community should receive:

the Guide;
the Playbook;
templates;
lessons learned;
practical advice;
mentoring;
encouragement.

What they don't get is your community.

They have to build their own relationships.

Their own volunteers.

Their own partnerships.

Their own operation.

CHAPTER 56 THE REPLICATION CONVERSATION

When another group approaches, don't immediately send them 100 documents.

Have a conversation.

Ask:

What need have you identified?
Who are you trying to serve?
What already exists?
Who is on your team?
Where will your water come from?
How will you transport it?
What geographic area are you considering?
What safety concerns have you identified?
Who are your community partners?
What will your first deployment look like?

If they can answer those questions, they're probably ready to start.

PART XIV

THE OPERATING STANDARD

CHAPTER 57 BEFORE EVERY DEPLOYMENT

PEOPLE

☐ Two-person teams
☐ Team Leader
☐ Contact information

VEHICLE

☐ Safe
☐ Fuel
☐ Load secure
☐ Capacity confirmed

WATER

☐ Loaded
☐ Counted

ROUTE

☐ Confirmed
☐ Alternatives known

SAFETY

☐ Weather checked
☐ Hazards reviewed
☐ Emergency contacts available

CHAPTER 58 DURING EVERY DEPLOYMENT

Remember:

OBSERVE

APPROACH

OFFER

RESPECT

LEAVE

And if necessary:

WITHDRAW

CHAPTER 59 AFTER EVERY DEPLOYMENT

Before anyone goes home:

☐ Count remaining water
☐ Record bottles distributed
☐ Record kilometres
☐ Record volunteer hours
☐ Record incidents
☐ Record observations
☐ Secure equipment
☐ Check vehicle
☐ Ask volunteers: "Are you doing okay?"

Then ask one final question:

"What should we do differently next time?"

PART XV

THE REAL PLAYBOOK

The forms at the back of this book are important.

But they're not the most important part.

The real Playbook is the accumulated judgment behind them.

It is knowing that:

you don't need to start big;
the route will change;
your water supply will occasionally fail;
volunteers will cancel;
people will surprise you;
some days will be easy;
some days will be difficult;
something will eventually go wrong;
your first plan will not be your best plan.

That's normal.

The objective isn't to eliminate uncertainty.

It's to build an organization capable of responding to it.

THE TEN RULES

If somebody remembers nothing else from this book, remember these ten things:

1. Start with the need.

Don't start with the solution.

2. Start small.

Your first deployment doesn't need to be impressive.

3. Keep people safe.

Nothing is more important.

4. Work in pairs.

Nobody needs to be a hero.

5. Treat everyone with dignity.

Every time.

6. Stay within your role.

You provide water. You aren't responsible for fixing someone's life.

7. Record what you do.

If you don't record it, you won't really know what happened.

8. Look after your volunteers.

Ask:

"Are you doing okay?"

9. Learn after every deployment.

Your first plan is only your first plan.

10. Come back.

This may be the most important one.

Because the person who receives a bottle of water today may not remember exactly what you said.

But they may remember:

"They came back."

THE LAST LESSON

The temptation, once a mission becomes successful, is to measure success by how big it has become.

More bottles.

More volunteers.

More vehicles.

More money.

More communities.

Those numbers matter.

But they're not the mission.

The mission is the person standing in front of you.

Someone is thirsty.

You have water.

You offer it.

You treat them with dignity.

You keep your volunteers safe.

You record what you did.

You learn.

And you come back.

That is the playbook.

Everything else is infrastructure.

THE I WAS THIRSTY FIELD TEST

Before you launch, stand in front of your team and ask:

"If we had to deploy tomorrow morning, could we do it safely?"

If the answer is no, don't panic.

Write down what is missing.

Then fix it.

When the answer becomes yes:

Go.

Not when everything is perfect.

When you are ready.

Because the original idea was never complicated.

Someone is thirsty.
Give them water.