Browse all stories

Small nonprofits aren’t short on ideas. They’re short on Tuesday afternoons.

Paper-cut illustration of a crowded calendar with a hand making room for a task and ideas waiting nearby

Here's a question that belongs in more software demos: when, exactly, is someone going to do all this?

The features look good. The presenter creates an event, adds an image, sends an announcement. A few clicks and it's done.

Ok. Now put that task into a Tuesday afternoon at your organization.

The phone is ringing. Someone needs an answer. The event details changed, and the person who updates the website isn't available. You're trying to finish something before the next meeting.

Somewhere in there, you need to use the new tool.

“It's easy” still takes time

A task can be easy and still be one task too many.

Writing an announcement, finding a photo, checking a date...none of those things sounds unreasonable. But someone has to stop and attend to each of them. If they've already done the work for an email, they're now doing it again.

A presenter can say, “That only took two minutes.” What the demo didn't show was gathering the information, deciding what to say, and checking whether the details were right.

Those minutes belong to somebody too.

The demo starts with everything ready. The day rarely does.

The ideas are already there

Ask what an organization would do with more capacity. Better volunteer follow-up? More updates for donors? Easier access to service information?

People close to the work can often see what would help. They have to fit it around what needs to happen today.

And today keeps happening. 🙂

When a new tool arrives with a long list of possibilities, I wonder how many land as obligations. Another place to check. Another thing to keep current. Something else to feel bad about falling behind on.

That's worth understanding before adding it to anyone's week.

A useful objection

During GrovLink's development, Tracy at Love INC questioned having to manually move information between systems. She was already publishing elsewhere. Why re-enter it for the app?

That's a really good question.

A simpler publishing screen could help. Fewer fields, clearer labels. But she'd still be moving the same information from one place to another.

Her concern helped clarify a product priority: making existing content easier to reuse, while keeping staff in control of what gets published. That remains a direction for the product, rather than a promise that every system already connects.

It gives us a useful question: did we make the task easier, or just give it a nicer screen?

What can come off the list?

Sit with the person who will use the tool and walk through one announcement. Where do the details come from? Who checks them? Where do they go? What happens when the time changes?

Then ask what the new tool changes. Does it save six individual follow-up messages? Can volunteers find the details themselves? Are there fewer places to check for a response?

Or does every step remain, with another added at the end?

Sometimes extra effort is worthwhile. Reaching people you weren't reaching before has value. But the person doing the work should help decide whether it's manageable.

“Worth the time” is a more useful conversation than “only takes two minutes.”

Getting started counts too

Someone has to learn the tool, gather content, and explain it to others. They'll have questions that only appear when they use it for real. That time needs a place in the plan.

I'd rather see an organization start with a few useful things it can comfortably maintain. Get service information right. Establish a workable way to post events. Learn before adding more.

An organization getting real use from a small scope is a better outcome than inheriting features it can't keep up with.

GrovLink handles the underlying technology and app maintenance. Staff still decide what to share. Both sides of that work need attention.

At your next demo, ask the presenter to walk through your actual situation. Start before the information is neatly prepared. Change an event time halfway through. Ask what happens next.

A Tuesday afternoon is a pretty good test of whether a tool will help.