Participant Signup: Designing Trust Before Data Collection
The form was not the whole problem. Participants arriving through invite links needed to recognise who invited them, what they were joining and how quickly they could reach a live session.
Signup was a trust-and-access problem before it was a form problem.
The generic flow dropped the identity, purpose and urgency carried by an invite. The redesign keeps that context visible while preserving data the platform needs.
The product should answer who invited me, what I am joining and whether I can reach it before requesting detailed profile data.
- 01
Carry identity forwardKeep organisation and program context visible.
- 02
Respond to urgencyPrioritise a clear join-first state near session time.
- 03
Reduce mobile effortUse one-question screens, suggested values and plain language.
Participants wanted fast, trusted access. The platform still needed useful data.
Three themes explained why the form felt difficult.
People could lose who invited them and what they were joining
The entry experience needed to carry organisation and program identity forward.
Personal information arrived before reassurance
The interface needed to establish legitimacy and explain why information was required.
Mobile signup could compete with a live session
The flow needed lighter pacing, clearer verification and a time-aware access state.
Direct participant signals, stakeholder observations and research plans were kept separate; an isolated comment was not treated as a universal behaviour.
Each theme became an explicit interaction rule.
A generic page weakened orientation and trust.
Keep organisation identity and “Registering for…” program context visible.
Headers must stay compact and handle missing logos or long names.
Signup could block someone arriving close to a live session.
Show a countdown and an explicit join-first action when the session is near.
Deferred profile completion needs clear status and operational rules.
Dense forms and long role lists increased effort on mobile.
Ask one thing at a time, suggest known roles and explain required fields in plain language.
More screens require visible progress and preserved session context.
The redesigned journey keeps purpose visible from invite to access.
What is your role?
The contribution is structural; performance remains to be measured.
Context now shapes the journey
The model carries organisation, program, timing and suggested-role information into signup.
“Lengthy form” became a broader access problem
I reframed the work around trust, urgency and data timing instead of treating field removal as the only answer.
No unapproved conversion lift
The public version does not present intended improvements as measured user impact.
After launch I would measure: signup completion, OTP failure, mobile completion and registration-related support requests.
Two lessons I would carry forward.
What I learned: field count alone does not define friction; lost context can make even a short form feel unsafe or irrelevant.
What I would validate next: the time-aware access model, mobile pacing and where profile completion can safely resume.
Depth for the interview conversation.
Research inputs and evidence separation
The work combined generative-research planning, prototype-evaluation planning, participant interview signals and stakeholder discussion about OTP, browser, mobile, reporting and support. These evidence types were not treated as interchangeable.
Expanded synthesis themes
The original synthesis covered trust at entry, program context, session urgency, mobile confidence, verification friction and structured reporting. For the main case, these were consolidated into Context, Trust, and Urgency + effort.
Confidentiality and outcome limits
Descriptions and interfaces are anonymised or reconstructed. Raw recordings, participant identities, internal dashboards, production screens and unapproved metrics are not published.