They Raised Their Hands. The Follow-Up Took Six Days.

At first, it looked like an intake problem.

Eleven forms across four platforms, supporting seven programs.

One place for participants. Another for volunteers. Another for donors. Event registrations. Parent information. Youth records.

Each form had a reason to exist.

But once we started following the information, a bigger question surfaced:

What happened after someone raised their hand?

That is where this edition of Behind the System begins.

At Kiarts, we started with the forms. The work underneath them took us somewhere more important.

One person, several disconnected stories

A parent might register for an event, ask about a youth program, and later offer to volunteer.

That is one relationship growing.

But across disconnected tools, it can become three records that never meet.

The event team sees a registration.

The program team sees an inquiry.

Someone else sees a potential volunteer.

Same person. Different records. Different platforms. Different stories.

To understand the whole story, somebody has to connect it.

Ask a colleague. Check another platform. Search a spreadsheet. Bring it up at the next meeting.

At Kiarts, people cared enough to do that work.

Staff followed up. Leadership checked in. People remembered conversations and helped each other fill in the gaps.

But every gap required someone’s attention.

The organization had information. Understanding it required people to reconstruct the story.

That can work for a while.

Then someone gets busy. A meeting gets skipped. The person who remembers the conversation is unavailable.

Now the next step depends on finding the context before anyone can act.

We started following the raised hand

Before redesigning the workspace, we looked at how information moved.

Where did an inquiry enter?

Who saw it?

Who owned the response?

Could that person find the context without asking around?

How long could it sit before someone noticed?

Those questions changed the design.

We began organizing around the person and their relationship with the organization: the programs they were interested in, the events they registered for, and the family connections that needed to be documented.

The workspace brought incoming information together, tagged it, and routed it to the person responsible.

The contact record became the place to build that history.

Each new interaction should add context, so the next staff member has enough information to move the relationship forward.

That does not mean everyone needs access to everything.

It means the person responsible can find what they need to take the next step.

Then we added a clock.

Good intentions needed a visible expectation

The follow-up standard was straightforward:

• Make contact within 48 hours.
• Alert the program director after 72 hours without recorded contact.
• Make unresolved follow-up more visible at four days.

That gave the team a shared expectation and a way to see when work needed attention.

A parent asking about a program may be ready to act today.

A volunteer may have time available this week.

Someone interested in participating may still be deciding whether to take the next step.

We cannot assume every delay loses that opportunity.

But we should be able to see how long we are asking people to wait.

Then the book bag drive gave us a real test.

The event revealed more than attendance

The event reached its registration limit two hours before it began.

Families came. Children received supplies. The community was served.

Some attendees also expressed interest in other programs.

That interest created work beyond the event.

Someone needed to receive it, understand it, and follow up.

The follow-up took six days.

Longer than the expectation we had established.

The team was still transitioning into the new system. No-shows were not yet being tracked. Staff were learning a different way to manage the work while continuing to serve the community.

They were caught between the old way of working and the new one being introduced.

That context matters.

So does the delay.

I actually think this makes the story more useful.

Building a system does not mean everything becomes perfect by Friday.

Its first real test can show you where the process still needs work.

The first win was visibility

A system can create visibility before it creates consistent behavior.

Building the workspace does not mean everyone immediately knows how to use it.

Assigning an owner does not guarantee they understand the responsibility.

An alert still needs someone who knows what to do when it arrives.

In this case, the six-day delay became something specific we could examine.

Did the right person receive the inquiry?

Did they know the next step belonged to them?

Were they working from the new workspace?

Was the expectation clear?

Was the escalation reaching someone who could act?

Did the design fit the team’s actual workload?

The delay alone could not answer those questions.

It showed us where to look.

Before, follow-up could disappear into scattered updates and individual memory.

Now there was a visible gap between the agreed expectation and what happened.

That gave leadership a concrete starting point for training, clarifying ownership, and adjusting the process.

Software by itself does not create accountability.

But a shared record gives people something they can examine together.

The missing story continues after the event

A book bag drive can tell an immediate story.

Families came. Children received supplies. People contributed. The community was served.

The longer story takes more work to see.

A parent attends an event.

They learn about another program.

They express interest.

From there, the organization needs to know what happens next.

Was contact made?

Did the family find the right program?

Did their child enroll?

Did they participate?

Those are questions to follow, not outcomes we can assume.

Each step needs a record. Each handoff needs an owner.

Without those connections, an organization may be able to count individual activities while struggling to explain how its work connects over time.

The missing story is how a person moves through the mission.

That matters when leadership plans the next event.

It matters when staff coordinate support across programs.

And it matters when donors and sponsors ask what their contribution helped make possible.

Attendance is part of that evidence.

Following the relationship helps build the rest.

What this build has taught us so far

Kiarts was already doing meaningful work.

The build gave that work a more connected place to be recorded and moved forward. Its first test also showed where adoption and follow-through still needed attention.

We are not at the end of that story.

The next stage is helping staff use the workspace consistently, tightening the handoffs, and checking whether follow-up improves.

That is how the system becomes part of daily operations.

The work started with eleven intake forms and four platforms.

Underneath them was a person waiting for the next step.

When someone raises their hand, following through becomes part of the promise.

— Touré

P.S. Think about the last person who asked about your services or programs.

Could you see who owned the next step and what happened afterward or would you have to ask around? That is a useful place to start looking behind your own system.