Built for your context
Sessions use your organization's real situations, not generic case studies from another sector.
Consulting solves a problem. Training builds the capability to solve the next one. CAMPBELL delivers interactive virtual workshops for boards, staff, and leadership teams on strategic planning, trauma-informed care, artificial intelligence, board governance, project management, and performance measurement.
A workshop is not a presentation. It is structured practice, built around the decisions the participants will actually have to make.
Sessions use your organization's real situations, not generic case studies from another sector.
Participants work through the material and leave having applied it at least once.
Board governance, staff execution, and executive strategy are different sessions with different designs.
Templates, frameworks, and job aids that participants keep using after the workshop ends.
Six workshops, delivered virtually and built around your organization’s own situations. Single sessions run as one working block; series run as multiple sessions so teams can apply the material between them.
Four 90-minute sessions, one a week, taking a team from clarifying purpose through assessing conditions and choosing priorities, to an implementation plan and scorecard. Two optional sessions address the moments before and after, where plans most often fail.
Four 90-minute working sessions, one a week, building a measurement system a small team can sustain: an indicator set you chose, definitions two people would count the same way, a view leaders will open, and a review where the numbers change a decision.
Four 60-minute working sessions, one a week, taking a team from whether it is fundable at all, through choosing what to chase and writing what reviewers score, to managing the award once it lands. Teams work on their own documents throughout.
Three 90-minute sessions, one a week, moving a team from understanding trauma and how it shows up, through the six trauma-informed principles in daily practice, to de-escalation skills, staff safety, and the systems that make the whole thing hold.
A practical look at where these tools genuinely help a nonprofit and where they do not. Staff test real tasks against what the tools can actually do, draw the lines around client information, and leave with a one-page acceptable use position a board can adopt.
Ninety interactive minutes on the three questions every board member should be able to answer: what is my role, what am I responsible for, and why am I here. Includes a board skills gap analysis, so the board leaves knowing what it is missing and what to recruit for next.
The discipline that turns an approved idea into finished work, scaled for nonprofit teams and requiring no new software. The team breaks down a real initiative of its own and leaves with a one-page charter and a check-in cadence it has agreed to.
A plain-language introduction for people who have never been taught the words. The first hour is entirely vocabulary: input, output, outcome, indicator, baseline. No prior knowledge, no software, and no framework assumed.
Every workshop is adapted before it is delivered. Session length, depth, and examples are shaped around who is in the room and what they need to be able to do afterward, and any of these can be combined into a recurring board and staff curriculum. If the capability you need built is not listed here, it is still worth the conversation.
Most strategic plans do not fail in the writing. They fail in the deciding. Organizations arrive at planning with a mission everyone can recite, a board that approves the document, and no shared method for choosing between good options. A year later the plan sits unopened, and each new opportunity is argued from scratch. This series is built to change that.
What must we clarify before we begin planning?
Working takeawayPlanning charter and initial stakeholder map
What is happening inside and around us, and what requires a strategic response?
Working takeawayPreliminary SWOT and two or three draft strategic issue statements
What will we focus on, and how will we choose our approach?
Working takeawayDraft priority framework, one developed goal and strategy, and an approval pathway
How will we organize the work and know whether we are making progress?
Working takeawayInitial 90-day action plan, draft performance scorecard, and review schedule
The core series builds a plan. These address the two moments where plans most often fail: before, when an organization already has one that is not working, and after, when a new plan is finished and everyone moves on. Either can be taken with the series or on its own.
For organizations that already have a plan that was written carefully, approved by the board, and has not informed a decision since. Diagnoses why, and hands leaders two tools they can use on the plan they already have: the Decision Criteria Matrix, and the “So what?” test run against their own SWOT.
The risk is highest right after adoption, when the document is finished and the planning energy is spent. Deliberately scheduled once reality has tested the plan, to turn it from a document into a working decision system.
The templates are the spine of the series. Each session fills one in, and by the final session they assemble into a working planning foundation.
A working strategic planning foundation, draft priorities, and an initial implementation roadmap.
Completing and adopting a full organizational strategic plan will require additional stakeholder input and leadership decisions beyond these workshops. We say this plainly at the outset so the expectations set with boards and funders are accurate.
Our strategic planning engagements →Every session, its topics, what participants will be able to do, and the 90-minute agenda, in a single document you can share with your team, board, or funder.
Volume is what the system already captures, so volume is what gets reported. People served, sessions delivered, meals distributed. All true, and none of it answers the question a funder is actually asking. This series builds the other thing across four sessions: an indicator set the team chose, definitions two people would count the same way, a view leaders will actually open, and a standing meeting where the numbers change a decision.
What change do we say we create, and for whom?
You leave withA drafted indicator set for one program, already cut to what you can sustain
Read first: Outputs vs. Outcomes
Would two people in this organization produce the same number?
You leave withOne measure defined end to end: definition, baseline, owner, instrument
Read first: Data Tracking 101 for Small Nonprofits
What does a leader need to see, and what should they do about it?
You leave withA one-page board view and a working team view, both drafted
What happens in the meeting where these numbers get looked at?
You leave withA review agenda, a date in the calendar, and an owner against every measure
Read first: From Strategic Plan to Action
The same shape every week, so teams know what to bring. Instruction is kept short because the value is in the forty minutes where a team builds that week's artifact from its own program.
Each team reports what changed since last week. Short and specific, and the reason the work happens between sessions rather than only inside them.
The concepts for that week in plain language, with examples drawn from real nonprofit reporting. Nothing theoretical that does not change what a team does on Monday.
The part that makes it a working session. Teams apply the material to their own program and produce that week's artifact, with the facilitator moving between them.
One concrete piece of work, sized to a busy week, named out loud so the group holds each other to it.
Every template is provided in editable form, so the remaining programs can be worked through after the series ends.
An indicator set for one program that the team chose and can sustain, every measure defined with a baseline, an owner and an instrument, a one-page view for the board alongside a working view for the team, and a standing review with a date and a chair. Templates are provided in editable form, so the remaining programs can be worked through without us.
Our performance measurement engagements →Every session, what it covers, what to bring, what you leave with, and how each session is structured, in a single document you can share with your team or board.
Most declined proposals are not rejected because the program was weak. They are rejected because the organization could not document, on deadline, what it was already doing well. Grant readiness is the work done before an opportunity is posted, and this series builds it in four hours across four weeks. Teams bring their own documents and finish each week with one piece of the foundation actually done.
What has to exist before an opportunity is worth answering?
You leave withA completed readiness audit and a ranked list of what to fix first
Read first: Are You Grant-Ready?
Which opportunities deserve the sixty to a hundred hours applying will cost?
You leave withA go or no-go decision on a real opportunity, and a written rule for the next one
Read first: Should You Apply for This Grant?
How is this read, by whom, and against what?
You leave withOne program narrative rewritten against a rubric, with the evidence named
What starts on the day the award arrives?
You leave withA reporting calendar and a first-week checklist for the next award
Read first: What Happens After You Win the Grant
The same shape every week, so teams know what to bring and what will be asked of them. Instruction is kept short, because the value is in the twenty-five minutes where a team works on the thing it actually has to produce.
Each team reports what changed since the last session. Short, specific, and the reason the work gets done between sessions rather than in the session.
The concepts for that week, in plain language and with examples from real nonprofit proposals. No theory that does not change what a team does on Monday.
The part that makes it a working session. Teams apply the material to what they brought, with the facilitator moving between them.
One concrete piece of homework, sized to fit a busy week, and named out loud so the group holds each other to it.
Every template is provided in editable form, so the work continues after the series ends and the next proposal starts from something rather than nothing.
A scored readiness audit with ranked gaps, one program described precisely enough to survive review, a full-cost budget for that program, a written rule for which opportunities the organization will pursue, one narrative rewritten against a rubric, and a reporting calendar ready for the next award. Every template is provided in editable form so the work continues after the series ends.
Our grants engagements →Every session, what it covers, what to bring, what you leave with, and how each hour is structured, in a single document you can share with your team or board.
The shift from “what is wrong with you?” to “what might be happening to you?” is the foundation of trauma-informed care. Trauma is common among the people nonprofits serve, and it shapes behavior, engagement, and trust even when it is never disclosed. Many challenges in community programs are trauma-driven rather than motivation-driven.
Building a shared language and foundation.
Key takeawayBehavior in high-stress moments is driven by the nervous system, not intent.
Converting knowledge into everyday practice.
Key takeawayWhen trauma-informed care is built into systems, the organization itself becomes a source of safety.
Practical tools, staff safety, and the systems that make it last.
Key takeawayIf staff safety depends on individuals being good at de-escalation, the system has failed. Lasting trauma-informed care is a leadership and policy commitment.
Thirty questions that ask whether the practice is built into how you run, or is being carried by particular people. The scale is deliberately a maturity scale: an item marked informal is a finding, because that practice leaves the day the person carrying it does. Complete it as a group, with direct-service staff in the room.
Every session, its learning objectives, what it covers, and how participants engage, in a single document you can share with your team or board.
Nonprofits hold some of the most sensitive information anyone holds: client records, immigration status, health and safety details, the circumstances that brought a family through the door. Staff under time pressure are already pasting work into free chatbots, usually with good intentions and no guidance, because no one has said what is allowed. This session is practical rather than speculative, and assumes no technical background.
Each participant names one way someone at the organization is already using these tools. The answers are usually more varied than leadership expects, and set up the session.
Plain language, no jargon, and the specific failure modes that follow from how they work. Confident wrong answers, invented sources, and why checking is not optional.
A sorting exercise using twelve real nonprofit tasks. The group places each one, then argues the cases where it disagrees, which is where the useful line gets drawn.
Confidentiality, consent, and what free tools do with what you give them. The group lists, by category, the information that must never be entered.
Training, retention, deletion, and location. The question set is applied to a product someone in the room is actually considering.
The pieces assemble into a position the organization can take to its board, with a named owner and a date for review.
Organizations tend to answer this in one of two ways, and both fail. A blanket ban, which staff quietly ignore while the work still has to get done. Or silence, which is a blanket permission nobody wrote down and nobody can be held to. The position is the middle path: short enough to read in a board meeting, specific enough that a program manager knows on a Tuesday whether something is allowed.
The tasks where staff may use them, written in your words rather than a vendor's. Specific permission is what makes a red line credible.
The categories of information that must never be entered into a general tool, listed explicitly enough that nobody has to interpret them.
Any output reaching a client, a funder, or the public is reviewed by a person who is accountable for it. The tool is never the last step.
What you tell the people you serve, your funders, and your board. Deciding this now is far easier than explaining it later.
Each part exists because a specific failure happens without it. Together they are the shortest document that a board can adopt and a staff member can actually follow.
The position template ready to complete, a red line checklist by information type, and twelve questions to ask any vendor with what to listen for in the answers. Written as a starting point for your counsel to confirm, not as legal advice.
The session, its learning objectives, the ninety-minute agenda, and what participants take away, in a single document you can share with your team or funder. For the ongoing engagement behind this workshop, see Our process improvement engagements.
Most people join a nonprofit board because someone they respect asked them. Very few are ever told what the role requires, where it ends, or what they are legally responsible for. They learn by watching, which means they learn whatever habits the board already has. This session fixes that in ninety minutes, and it is built around doing rather than listening.
Each participant answers in one line. Responses are read back, surfacing the range of reasons people serve and the expectations nobody ever stated.
What a board owns and what staff own. The boundary is drawn, then tested immediately in a sorting exercise using fourteen real decisions.
The three fiduciary duties in plain language, what each looks like in a meeting, and the financial oversight that follows. Includes reading a real statement together.
The handful of questions that separate oversight from operational drift, practiced against a scenario where the answer is genuinely unclear.
The skills matrix completed before the session is rolled up and read out. The board sees its own depth by competency and sets recruitment priorities.
Each member writes what they bring, what they will ask about, and why they serve. They keep it; the chair gets an anonymous summary.
Most boards recruit from the networks of the people already sitting on them, which quietly reproduces the skills already in the room. A skills gap analysis replaces that instinct with evidence: what this board needs, who actually has it, and where the bench is thin enough to be a risk. The matrix is completed before the session, and part four reads the result out loud.
Before anyone scores themselves, the board marks each of eighteen competencies essential, desirable, or not required for this organization.
Privately, in about ten minutes, on a four-point scale from no exposure through to able to lead the board’s thinking on it.
One grid places every competency against every seat and counts how many members have working knowledge of each. That count is the board’s depth.
Depth is compared against need level, every gap is classified, and the board leaves with a ranked list of what to recruit for and what to develop.
Every essential competency lands in one of four states. The state sets the action, which is what turns a scored grid into a recruitment plan a board can defend to anyone who asks how its members are chosen.
Essential to the mission, and nobody on the board has working knowledge of it.
What the board doesRecruit for this first.
One member carries it alone. The capability leaves the day that member rotates off.
What the board doesRecruit a second, or develop one.
Two or more members can hold a real conversation about it and challenge an answer.
What the board doesHold it, and protect it through turnover.
More than half the board shares one strength, which usually means one recruiting network.
What the board doesWiden where you look for members.
The Board Skills Matrix and Gap Analysis Worksheet: the self-assessment, the board-wide roll-up grid, the gap classification and recruitment priorities, and a composition snapshot. Yours to keep and reuse whenever a seat opens.
The session, its learning objectives, the ninety-minute agenda, and the skills gap analysis in full, in a single document you can share with your board or chair.
Nonprofit teams run projects constantly and almost never call them that. A new program launches, a site opens, a system gets replaced, a grant requires something delivered by a date. The work is real and the stakes are real, but it is managed in meetings and inbox threads, and the discipline that would carry it to a finish is missing. This session supplies that discipline in ninety minutes.
Each participant names an initiative that lost momentum and the point at which it did. The pattern in the answers sets up everything that follows.
Scope statements, stated exclusions, and acceptance criteria. The group writes the finish line for the initiative it brought, then tests whether an outsider could verify it.
How small a piece of work needs to be before it can be owned and estimated. The team builds a work breakdown structure for its own project, live.
Every deliverable gets one name. Dependencies are mapped, and the exercise usually reveals that the schedule is driven by something nobody was tracking.
A risk and decision log simple enough to maintain, and a standing agenda that surfaces trouble while there is still time to act on it.
The pieces are assembled into a charter the team takes with them, and the first check-in is scheduled before anyone leaves the session.
Most nonprofit projects have no project document at all. The ones that do usually have a twelve page plan written to satisfy a funder, filed once, and never opened again. Neither helps the person deciding on a Tuesday whether something is on track. The charter is one page, written in the room, and short enough that the team will keep it current.
What is delivered, what is explicitly not, and how anyone will know it is done. Exclusions are what make a later change a decision rather than an argument.
Into pieces small enough that one person can own one and estimate it honestly. If a task cannot be estimated, it is still too big.
A name, not a department and not a committee. Owners can delegate the work; they cannot delegate the answer to how it is going.
A standing check-in with a fixed agenda, and one place where risks, issues, and decisions are written down as they happen.
Each field exists because a specific failure happens without it. Together they are the shortest document that still answers the questions that matter mid-project.
The template the session is built around: a worked example, deliverable, owner and dependency columns, the one-page charter, and a check-in agenda your team can adopt as it stands.
The session, its learning objectives, the ninety-minute agenda, and what participants take away, in a single document you can share with your team or funder. For the ongoing engagement behind this workshop, see The Project Management Engagement.
Measurement has a vocabulary, and almost nobody working in a small nonprofit was ever taught it. Funders write outcomes, baseline and indicator as though everyone agrees what they mean, staff nod because asking feels like admitting something, and the confusion gets built into the report. This course is the plain-language fix. The first session is entirely vocabulary.
If we are going to talk about this, what are we saying?
You leave withA one-page glossary in plain English that you keep and can hand to anyone
Read first: Outputs vs. Outcomes
What is the difference everything else rests on?
You leave withYour own current reporting, sorted, with the gaps visible
If we started on Monday, what would we actually do?
You leave withThe first three measures your organization would start with, and the first step
Read first: What a Nonprofit Dashboard Should Actually Show
Taught slowly, one term at a time, each with an example from a real nonprofit. Questions are welcome at any point, including the ones that feel obvious, and five minutes at the top of every session is protected for exactly that.
Anything that did not land, asked openly. This is the most useful five minutes in the course and it is protected deliberately.
Taught slowly, one term at a time, each with an example from a real nonprofit. Nothing assumed and no jargon used before it is defined.
The group applies what was just defined to documents they brought. This is where the vocabulary stops being abstract.
Something small and specific, usually a document you already have rather than work you have to do.
Everything is plain English and free of jargon. The glossary is one page and is meant to be handed to the next person who joins.
A vocabulary the whole team shares and uses correctly, your own current reporting sorted into outputs and outcomes with the gaps visible, the first three measures your organization would start with, and a glossary you can hand to the next person who joins. This course deliberately stops before building a system.
The four-part series builds what this introduces →This course deliberately stops once a team can use the vocabulary and name what it would measure. It does not build anything. That is the right place to stop for an introduction, and it is also where most organizations stall, because the next step needs time and tools that a small team does not have spare. That part is what CAMPBELL builds. A dashboard designed around the decisions your leadership actually makes, connected to the data you actually hold, that updates itself and still works a year later. Where your website is also carrying the job of explaining your impact publicly, the two get built together.
A measurement system and the view that carries it, designed around decisions rather than around whatever data happens to exist.
A site that reflects the organization you are, including the impact story the measurement finally lets you tell honestly.
Documented, owned by a named person on your team, and maintainable without us.
The next conversation is a short one: what does your leadership need to see, and how often. Those two answers shape everything after them.
Every session, what it covers, what to bring, what you leave with, and how each session is structured, in a single document you can share with your team or board.
Workshop engagements address the capability gaps that make every other initiative harder than it needs to be.
Governance and management responsibilities blur, and meetings drift into operational detail.
Staff cannot connect their daily work to the organization's strategic priorities.
Teams avoid performance conversations because the measures feel unfamiliar or punitive.
Projects are run differently by each person, with no shared planning or accountability language.
The organization has the deliverable but not the internal capability to repeat the work.
New board members and staff learn the organization informally and unevenly.
Internal capability that stays with your organization, and a shared language that makes the next initiative easier.
Participants leave having used the material on a real organizational situation.
Board, staff, and leadership describe strategy, performance, and execution the same way.
Templates, frameworks, and job aids the organization keeps and continues to use.
Capability built internally rather than repurchased for every new initiative.
Every engagement begins the same way, with a conversation. There is no cost and no obligation to schedule one.
Tell us the audience, the group size, and the capability gap you want closed.
We confirm which sessions fit, the right audience for each, and whether a single session or a series is the better format.
Session length, depth, and the real organizational situations each session will be built around.
Dates, materials, and participant preparation are confirmed.
Participant roles and group size, any organizational materials you want used as real-world examples, and confirmed scheduling. Final scope is confirmed through discovery.
Training builds the skill. These engagements are where organizations usually put it to work.
Boards and leadership teams that share a planning vocabulary get far more out of a planning process.
Learn More →Teams comfortable with outputs, outcomes, and indicators adopt a measurement system rather than avoiding it.
Learn More →A shared delivery language is what makes project discipline stick after the engagement ends.
Learn More →A consultation is a conversation, not a sales call. We will discuss where you are, what you are trying to resolve, and whether this engagement is the right fit.
Schedule a ConsultationStrategy, program design, performance measurement, grants, operations, and more, delivered virtually to organizations across all 50 states.
View All Services