How Do You Know Your Work Helped?

A contribution can feel generous from the inside. That feeling tells us something about our intention. It cannot, by itself, tell us what happened for the people we hoped to serve.

Imagine publishing a guide, running a workshop, or taking on a task for a community. You may be proud of the care that went into it. You may also hear thanks. Neither effort nor praise settles the practical question: was the work useful, to whom, and in what way?

Ask for the experience, not a verdict

A direct question makes room for information that our own account cannot supply: What was useful? What was confusing? What did this help you do, if anything? What would have made it more useful? Those questions leave the other person free to describe their experience rather than reward our intention.

The answer may be specific, mixed, or disappointing. Someone may value the conversation but never use the guide. Someone else may use one small part we considered incidental. A person may be too polite, busy, or dependent on us to criticize freely. So one response is a clue, not a final measure. Look for patterns, invite candid feedback through more than one channel, and pay attention to what people can actually do with the work.

Let the reply change the work

Asking matters most when a reply can lead to a revision. We can clarify a step, change the format, make access easier, or recognize that the work served a different need than we imagined. We may also learn that it did not help. That knowledge is uncomfortable and valuable.

There is room to enjoy making and sharing something. There is also a responsibility in calling it a contribution. The first is an account of why we acted. The second asks us to listen to the people affected, then let their experience inform what we do next.