Move One Gathering Workflow, Not Every Piece of Paper

Take a regular community discussion as a planning example. Some replies arrive by phone, others on paper. A coordinator records them, a volunteer prepares the room and a host welcomes arrivals. Trouble starts when a cancellation reaches only the coordinator: a seat is still counted, and the host expects someone who has already withdrawn. A small break between tasks has created work for three people.

Start digitalisation at that break. Moving every notice, file and conversation online is a much larger undertaking than helping one accepted reply reach the people who need it. A limited change can be observed, corrected and understood by volunteers who have other responsibilities too.

Follow a reply before choosing a tool

For the next gathering, observe what actually happens to a response. Who receives it? What do they do with it? Who needs the information next? Include corrections and cancellations, because those expose the places where a neat plan becomes complicated.

The aim is not to document the whole community. Follow one ordinary reply and one change to it. A participant might initially accept and later withdraw. If the withdrawal requires a telephone message, an altered spreadsheet and a separate correction to the host, the same change is being handled several times.

Distinguish necessary decisions from avoidable copying. An organiser may genuinely need to check whether a place can be offered. Moving the information into a digital system does not remove that responsibility. Re-entering an already accepted response in a second list, however, may contribute nothing beyond keeping the lists aligned.

A message and a record do different jobs. A message draws attention to something. A record explains its current state. The experiment succeeds when the people arranging places and welcoming arrivals can use the same accepted response, rather than recreating it from messages.

Change the journey at its narrowest point

The pilot needs a specific promise: a response accepted by the coordinator will not need to be typed again before the host can use it. That is small enough to test and important enough to matter.

Choose an available tool that can support that promise. It might be a straightforward shared list or a suitable existing participation system. The important capability is not how impressive the screen looks. It is whether the information can move through the agreed process without another person rebuilding it.

In this example, the coordinator maintains the accepted replies, the room volunteer uses the resulting count and the host receives the information needed for arrival. A request awaiting a decision stays separate from an accepted place. Contact details need not be visible to everyone simply because several people use the same working record.

A cancellation should travel through the same route. It should not leave the room organiser working from an old count while the coordinator knows that a place is available. Test that ordinary change before asking the group to rely on the new arrangement.

Test an available tool against the job rather than choosing it from a feature list. Can a correction reach the host? Can a volunteer distinguish an enquiry from a confirmed place? Can access be limited to what each role needs? Samajya's wider purpose includes easier community coordination, but the website itself does not run this attendance process.

Remove work rather than hiding it elsewhere

A digital response can appear efficient while shifting the burden to the participant. Someone who previously made a short phone call may now be asked to complete an unfamiliar process or provide details that do not affect this gathering.

Keep the request proportionate. Explain what the person needs to do once, and avoid asking them to repeat information solely because different organisers prefer different lists. Where a telephone or paper response remains useful, let the coordinator enter it into the same working process. An alternative way to respond does not require a permanently separate administration system.

This also makes the experience easier for someone helping at the gathering. The host should not have to interrogate a participant because their name appears in one place but not another. Resolving a process mismatch at the door turns an internal problem into the visitor's first impression.

Organisers need an adjustment period too. Trying a new process while maintaining every old list can be a sensible short check, but it is not a permanent improvement. Identify which duplicate will stop once the pilot works. Otherwise the digital change simply becomes an additional task carried by the most conscientious person.

Compare a full cycle, including the inconvenient parts

Compare one complete cycle with the previous arrangement. Note how many answers were copied twice, how many corrections needed separate messages and how often a participant was asked again. Separate the initial setup effort from tasks that recur every time. A tool can feel unfamiliar at first while still reducing repeated work; it can also look modern without reducing anything.

Ask the participant and the host about their experience, not only the person who selected the tool. Did anyone have to give the same answer twice? Could the host recognise an accepted response? Did a cancellation create extra chasing? A smooth demonstration cannot answer those questions.

Include the awkward possibility that the tool is unavailable when needed. Decide how the host can obtain the essential arrival information without rebuilding the process under pressure. A prepared fallback is part of the experiment, not evidence that digitalisation has failed.

Then decide whether to keep, adjust or stop the pilot. If repeated copying has disappeared but one response route remains difficult, improve that route. If the group is now maintaining more lists than before, reconsider the design rather than declaring success because the gathering used a website.

At the end of the pilot, name one task that has disappeared and one difficulty that still needs attention. If no task has disappeared, pause before extending the process. The point is to give volunteers more time for the discussion and the people attending it, not to add another list that someone must maintain.