I gave a workshop yesterday at the SD State Arts Conference. It was titled Building Creativity Into the System: Designing Foundations That Scale. The whole hour was about a single idea — that the same structural pattern runs a concert, a fundraising campaign, a workshop, and a festival, and that you only have to find the pattern once to apply it everywhere.
Afterwards, an attendee came up and asked me the question I should have answered in the talk:
"How do you know you've actually found a pattern? What makes those things the same pattern, and not just things that happen to look alike?"
It was the best question of the day. The talk gestured at patterns existing. It didn't teach the diagnostic. So this post is the answer — and there's a worksheet at the bottom so you can run the test on your own operations.
The five tests
A pattern is real when it passes all five of these. Fail one, and you've found something that looks like a pattern but isn't actually the same shape.
1. The Domain-Strip Test. Describe both things in a sentence with one word swapped. Strip the domain language. Replace "concert" or "fundraiser" or "exhibit" with abstract verbs and nouns: gathering, coordination, curation, audience, output.
"A concert is a scheduled gathering of people for a curated experience requiring multi-party coordination."
Swap "concert" for "fundraiser" — sentence still works. Swap for "workshop" — still works. Swap for "board meeting" — no. A board meeting has no audience experience to curate. Different shape. Most candidate patterns fall apart at this test, and that's a feature.
2. The Lifecycle Test. Do they go through the same stages in the same order? A concert and a fundraiser both go: Idea → Plan → Confirm → Promote → Execute → Wrap. A festival is the same with more parallel tracks. A workshop is the same compressed.
If the verbs at each stage rhyme, the pattern rhymes.
3. The Artifact Test. What does each stage produce? A budget. A run sheet. A roster of who's helping. A marketing plan. A debrief. If both things produce the same kinds of artifacts at the same points — that's not coincidence. That's the same machine running different content.
4. The Failure-Mode Test. What breaks them? Missed deadlines, missing partners, blown budget, no debrief. Things that fail the same way share structure. This is usually the test that closes the case — because nobody fakes their failures, and failure modes don't lie.
5. The Substitution Test (the proof). This is the one that tells you for sure. Take an existing template — your concert tracker, your event planner, whatever you already use. Rename the fields. Can you run the new thing through the same template without adding or removing fields?
If yes, pattern confirmed.
If no — if you have to add or remove fields — you found two things that look alike but aren't actually the same shape. Most people stop at "they look alike." The substitution test is where you prove it.
The meta-answer: the part you can't shortcut
Here's the thing nobody tells you in the workshop. Patterns reveal themselves to people who are in the work long enough to notice the same conversations repeating.
When you catch yourself thinking "I'm having the exact same conversation about this fundraiser that I had about last month's concert" — that recognition is the signal. It doesn't come from theory. It comes from volume. The eye gets trained by doing the thing fifty times.
Which means the practical move isn't to sit down with a notebook and try to think your way to patterns. The practical move is to start noticing your own conversations. What's the question you keep asking? What's the spreadsheet you keep rebuilding? What's the email you keep retyping?
Those repetitions are the pattern, surfacing.
Why this matters for arts orgs
I run a small performing and visual arts nonprofit. Three staff. Over 200 events a year. The thing that almost broke me in my first six months wasn't any single project — it was the feeling that every project was new, that I was solving fresh problems every time.
That feeling was wrong. I wasn't solving fresh problems. I was solving the same problem with different content, over and over, and rebuilding the system in my head every time because I'd never named the pattern.
The day I named the first pattern — the day I built one event tracker that could hold a concert, a workshop, and a fundraiser without modification — was the day I got my Sundays back. Not because I did less work. Because the work stopped requiring me to reconstruct the structure every time.
That's the prize. Not faster. Not fancier. Less reconstruction. More time for the part of the work that actually requires you — the judgment, the creative calls, the relationships.
The worksheet
I built a worksheet that walks you through all five tests on two things in your own operations. It's the same exercise I use when I'm working with a client to find the patterns underneath their daily firefight.
It takes about 15 minutes. Pick two things that feel like they might share a structure — a concert and a fundraiser, an exhibit opening and a workshop, a grant report and a board report — and run them through.
If both pass, you found a pattern. Build it once, use it everywhere.
If they fail at Test 4 (failure modes don't rhyme), they were never actually the same pattern — and trying to force one template to hold both would have made your operations worse, not better.
Either answer is useful.
Get the worksheet (and the Master Pattern worksheet too) →
If you were at the SD State Arts Conference workshop and this was useful, I'd love to hear what you found. Reply to my email or reach me at heath@heathjohnson.co.
If you weren't there but you're working through patterns in your own operations and want to talk it through, I do free 30-minute consults — heathjohnson.co.
And if you want the full toolkit from the talk — partner tracker, event planner, dashboard, all in Google Sheets, Excel, and Notion — it's at heathjohnson.co/toolkit. Free, no signup.