Blueprint 01
ProposedNonprofit Capacity Blueprint
“We know what our biggest problem is. Can someone help us actually fix it?”
What is the Nonprofit Capacity Blueprint?
One defined constraint, one bounded intervention, built and handed over with the staff trained and the change measured. Solve the highest value organizational bottleneck whether the right intervention is AI, process redesign, documentation, technology, or training.
- For
- A small community organization with one process that is visibly costing it time or capacity, and staff willing to be part of changing it.
- Status
- A defined concept or planned pilot that has not launched. The design is written down and nothing has been delivered. Two kinds sit here and the entry itself tells you which: a proposed pilot names its targets, and any target it names is a plan rather than a result; a proposed concept names none because none have been set.
The sequence
What actually happens, in order.
This is the design. It has not been run yet, and the first real organization will change parts of it.
- 01
Define the constraint
Name one problem precisely enough that everyone would recognize it. Not a theme, a problem.
- 02
Map current state
Draw the process as it actually runs, including the steps nobody documented.
- 03
Prioritize the intervention
Decide what to change, and deliberately decide what not to change. The right answer is often not technology.
- 04
Design future state
Design the process as it should run, with the people, tools, data, and control points in the right places.
- 05
Build or configure
Build the thing. HxDF does the work rather than recommending that the organization find someone who will.
- 06
Test with staff
The people who will use it try it, break it, and say what is wrong while it can still change.
- 07
Train and document
Instructions in the language the staff use, written so a new person could follow them.
- 08
Measure
The same measure taken before and after. If nothing moved, that is the finding.
- 09
Transfer and follow up
Ownership moves to the organization, and HxDF checks back to see whether it survived contact with a normal week.
What you keep
Everything. That is the whole idea.
A Blueprint is finished when the organization owns the result and can change it. Nothing here stays with HxDF.
The working system or redesigned process
A map of how it runs
Plain language instructions
Trained staff who can change it without HxDF
The risk notes: what to watch and what not to automate
A before and after measure that belongs to the organization
Who does what
A Blueprint is not something done to an organization.
It only works if the people who will live with the result are part of building it. Here is the split, agreed before anything starts.
HxDF does
- Maps the process and designs the change
- Builds or configures the solution
- Writes the documentation and runs the training
- Takes the baseline and the followup measure
You do
- Names the constraint and provides access to the process
- Gives staff time to test it and say what is wrong
- Owns the result and keeps running it after HxDF leaves
What this is not
Not an ongoing service contract, not a retainer, and not a software product. It ends with the organization owning something it can maintain.
How you get here
Usually through an audit.
These are the audits that most often identify the kind of constraint this Blueprint is built for. They cost nothing and commit you to nothing.
Start honestly