Role clarity comes before commitment
68 of 76 respondents rated clear role information quite important or crucial. I made time, location, requirements, and responsibilities part of the decision to apply, rather than information to discover later.
Giving.sg · NVPC · Volunteer product design · 2025
Connect the whole volunteering journey.
People want to volunteer, but unclear role commitments and sign-up steps can stop them from completing an application.
My role: Volunteer product designer for NVPC, covering research synthesis, product priorities, interaction design, prototyping and the design system.
Key decision: Treat discovery, application and participation as one connected journey. I focused on clearer role commitments, return-to-opportunity sign-in, and a “My Events” area for status and participation history.
What happened: In a five-person study, reported average task completion time went from 8 minutes on the original flow to 3 minutes in the redesigned prototype.
The product challenge
Help people understand the commitment and complete the next step.
The redesign needed to answer practical questions: Is this role suitable? What am I committing to? How do I apply? Where do I check what happens next? I used those questions to define the scope, rather than treating browsing, account entry and participation as separate flows.
49/81survey respondents selected opportunities that match their interests as a motivator.
48/81selected insufficient role detail as a barrier to volunteering.
37/81selected unclear application or sign-up steps as a barrier.
Survey: 81 responses; multiple selections allowed. Counts describe this research sample.
Research → product priorities
Resolve uncertainty at the points where people make decisions.
Keep the chosen opportunity in view
Eight interviews exposed uncertainty beyond discovery. One participant lost the selected opportunity after sign-in and could not tell whether the application was complete. I translated that evidence into continuity and status requirements.
Connect the handoffs
The journey audit showed that browsing, role details, and account entry needed to work as one task. I connected those handoffs in the prototype and introduced a clear destination for participation status.
01 / Find a relevant opportunity
Make the commitment visible before asking someone to apply.
I organised discovery around interests, skills, schedule and location. Role details bring time, responsibilities, requirements and location into the decision. The aim is to help people judge fit before investing time in an application.
- Evidence
- 49/81 selected interest fit as a motivator; 48/81 flagged missing role details.
- Design decision
- Bring interests, skills, and filters into discovery; keep commitments and requirements visible in role details.
- Product rationale
- People can judge fit using visible criteria before investing time in an application.
Trade-off: Make relevance explainable. Interest and skill cues support the choice; the role details let people verify it.
02 / Preserve the volunteer’s intent
Sign-in should continue the task.
I defined return-to-opportunity sign-in as a requirement: after authentication, the volunteer should return to the role they selected. Preference setup supports discovery, but account creation should not erase the reason someone came. Authentication continuity remains an engineering requirement to validate before rollout.
- Evidence
- 37/81 flagged unclear sign-up steps. Interview feedback also exposed lost context after authentication.
- Design decision
- Design preference setup to support discovery, and define a return-to-opportunity requirement for authentication.
- Product rationale
- Account setup should move the current task forward. Login-state persistence is an implementation dependency.
03 / Apply with confidence
Connect the role, application and confirmation.
I linked role details, the application form, confirmation and the next destination as one flow. The confirmation needs to make completion clear and explain where the volunteer can check progress.
- Evidence
- The survey and journey audit linked application uncertainty to scattered role details and unclear steps.
- Design decision
- Connect role details, the application form, confirmation, and “My Events” as one flow.
- Product rationale
- A clear completion state closes the immediate task and gives the volunteer a place to return.
04 / Know what happens next
Give participation a place to live.
I designed “My Events” for application status, upcoming activity and participation history, with an optional completion-record flow. Reliable status and verified records depend on organiser confirmation and platform operations. Those responsibilities need to be defined alongside the interface.
- Evidence
- Interviews surfaced needs for follow-up and participation records, especially among volunteers who wanted recognition.
- Design decision
- Create “My Events” for status and event history, with an optional completion-record flow.
- Product rationale
- Status gives return visits a purpose. Verified records depend on organiser confirmation and platform operations.
Design system and delivery readiness
Use one interaction language across the journey.
I translated NVPC’s brand guidance into reusable foundations, forms, navigation and component states.
I incorporated the design-system rules into my AI workflow and reviewed generated screens against the intended interactions. Delivery priorities include form validation, responsive states, authentication continuity and organiser-owned status updates.
Validation and measurement
Test whether the connected journey is easier to complete.
8 → 3 min
Reported average task completion time for the original flow and redesigned prototype, tested with five participants.
What to validate in a live rollout
Leading signals
Role comprehension, task completion, form drop-off and confidence after applying.
Longer-term signals
Completed applications, confirmed participation, return use and support contacts about status.
Reflection
The interface depends on the service behind it.
The central decision was to preserve the volunteer’s intent across every handoff. A rollout would need product, engineering and organisers to align on listing quality, authentication continuity and reliable participation status.
What I would test next: live sign-up completion and return-visit rate with real NVPC listings.
Not yet measured: live conversion, since this was a five-person prototype test.