Service Engagement

Design Programs on
Purpose, Not by Accident.

Most programs are not designed. They accumulate. CAMPBELL works through a deliberate sequence — problem, community, outcome, theory of change, model, measurement, resources, pilot — so the program you launch is the program you intended.

Schedule a Consultation Send Us a Message

The Basics

The Core Concepts.

Program design is not a document exercise. It is a sequence of decisions, each of which constrains the next. Skipping a decision does not remove it — it just means someone makes it later, under pressure, without evidence.

The problem comes first

Define the problem with evidence before naming a program. If you cannot complete that step, that is the finding — do not design past it.

Outcomes are not activities

An outcome describes change in people or conditions. Counting participants and sessions describes effort, not effect.

Assumptions must be written down

A logic chain can look sound while resting on an untested belief. Naming assumptions is what makes them testable.

Design for the margin, not the middle

A model built for the average participant excludes the people with the highest need — the ones the program exists to reach.

Common Pitfalls

The Five Most Common Design Mistakes.

These are the patterns we see most often, and the ones a disciplined design sequence is built to prevent.

Designing to the funding

The grant shapes the program rather than the problem, and the program ends when the grant does.

Confusing activity with outcome

Reporting counts what was easy to gather, and no one can say whether anything changed.

Skipping the assumptions

The logic looks sound but rests on an untested belief about how people will behave.

Designing for the average participant

The model works for the person in the middle and excludes those with the highest need.

Launching at full scale

With no pilot, the first cohort absorbs every design flaw.

Problems We Solve

Problems We Solve.

Program development engagements address the gap between what an organization intends to accomplish and what its programs are actually built to deliver.

Programs that accumulated

A funder asked for something, a board member suggested something, and the program became the sum of those requests.

Limited evidence behind the need

The problem statement reflects assumption rather than data, and funders can tell.

Activity reporting only

The organization can report what it did, but not whether it made a difference.

Undefined program model

Dosage, sequence, staffing, and setting vary by whoever is delivering the service that week.

Measurement designed after launch

There is no baseline, so improvement cannot be demonstrated.

Key-person dependency

The program cannot survive the departure of the staff member who built it.

Underfunded true cost

The budget omits supervision, reporting, and overhead, and the program runs at a structural loss.

Undefined decision point

The program continues indefinitely because no one is responsible for deciding whether it should.

The Benefits

What You Gain.

A program you can explain to a funder, deliver consistently, measure honestly, and decide about with evidence.

A defensible case for support

An evidence-based problem statement, theory of change, and logic model that hold up in a competitive proposal.

A model that can be delivered consistently

Dosage, sequence, staffing, setting, and intake specified clearly enough for any qualified staff member to run.

Measurement that exists before launch

Indicators, owners, instruments, intervals, and a baseline — so results can actually be demonstrated.

An honest resourcing picture

Fully loaded cost and a staffing model that does not depend on any single person.

The Methodology

The Design Sequence.

Eight steps, in order. Each one constrains the next, which is why the order matters more than the pace.

Define the problem, not the program

A problem statement that names who, what, where, and what it costs — supported by evidence rather than assumption.

Understand the community you intend to serve

Listening sessions and lived-experience input that test the design before it is built, not after.

Name the outcome before the activity

One primary outcome and no more than three supporting outcomes, each describing change in people or conditions.

Build the theory of change

Inputs, activities, outputs, and short, medium, and long-term outcomes — with the assumptions behind each link written down.

Design the program model

Dosage, sequence, staffing, setting, referral and intake, and which elements are essential versus locally adaptable.

Decide how you will measure, before you launch

Indicators for outputs and outcomes, each with an owner, an instrument, an interval, and a baseline.

Resource it honestly

Fully loaded cost including supervision and reporting, and a staffing model that survives any one person's departure.

Pilot, learn, adjust

A pilot with a written question, an end date, and a named decision-maker who can continue, adapt, or stop it.

Phases & Deliverables

Phases and Deliverables.

Engagement depth scales with the number of programs, the maturity of existing data, and whether you are designing a new program or redesigning an existing one. The sequence does not change.

Discovery & Definition

Evidence-based problem statement
Needs assessment and data review
Community and stakeholder engagement summary
Existing-services and gap analysis

Design

Outcome statement and supporting outcomes
Theory of change with written assumptions
Logic model
Program model specification — dosage, sequence, staffing, setting
Eligibility, referral, and intake pathway

Measurement

Indicator set for outputs and outcomes
Measurement plan with owners, instruments, and intervals
Baseline plan and data collection tools
Reporting and review cadence

Resourcing & Launch

Fully loaded program budget
Staffing model and role descriptions
Pilot design with decision criteria and end date
Implementation plan and launch readiness review

Next Steps

How to Get Started.

Every engagement begins the same way — with a conversation. There is no cost and no obligation to schedule one.

Schedule a consultation

Tell us about the program you are building — or the one that is no longer working.

Complete the fit and scope assessment

We confirm program count, available data, community access, and your funding timeline.

Confirm the design scope

New program design, redesign of an existing program, or a portfolio review across several.

Finalize the agreement and schedule kickoff

Scope, schedule, project team, and norms are confirmed, and the design work begins.

What We Need From You

Access to program staff, existing data and reporting, and — critically — the people with lived experience of the problem. Final scope is confirmed through discovery.

Schedule a Consultation

Let’s talk about what your organization needs.

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.