Smarter Add Member Flow for RiserNest Multi-Community Users
We needed to ensure no duplicate users and to make the process faster and clearer.


The Problem
With the introduction of multi-community functionality in RiserNest, users could belong to multiple communities under a single account. However, the existing Add Member flow for admins did not support this change.
Admins were required to enter first name, last name, and email for every new member, even if the user already existed in RiserNest. This led to unnecessary data entry, the risk of creating duplicate users, and a confusing experience for admins trying to manage their communities efficiently.
Problem Statement
Sarah is a community admin who needs a smooth way to add members by email, with smart suggestions for existing RiserNest users, to avoid unnecessary data entry and duplication.


Research & Discovery
After identifying the main problem, I brainstormed with the team and spoke with several admins. In addition to the challenge of preventing duplicate users, I discovered that the current Add Member drawer, opening from the right side of the screen, made data entry difficult.
The narrow layout and its position made it harder for admins to focus and disrupted their workflow. These insights led to designing a cleaner, more efficient solution.

The Solution
Step 1. Member's Email
We designed a full-width, two-step drawer that opens from the bottom of the screen. In the first step, the admin enters the member’s email.

Step 2. Existing User
If the user already exists in RiserNest, a card with their details is shown, allowing quick addition to the community.

Step 2. New User
If the user doesn’t exist, the drawer reveals first name and last name fields so the admin can add them for the first time.

The ability to assign the member to a team immediately remained unchanged.
The old user flow allowed admins to directly enter the first name, last name, and email to invite and add members. The main issue with this approach was that it could trigger duplicate errors if the user already existed.
Moreover, if the user was already on RiserNest, entering their basic information again was unnecessary and added friction to the process.
Old User Flow

Updated User Flow
The user flow was updated to a two-step member addition form, effectively addressing the possibility of existing users on the platform and preventing unnecessary data entry.

The Outcome
What is achieved?
During this case study and the subsequent actions, my team and I achieved the following:
- Context-aware member addition system
- Clean and clear user flow
- Faster, more efficient member onboarding
- Minimized errors for admins
- Prevention of duplicates and double entries
What is learned?
The key lesson I learned was to always listen to users. Their feedback reveals ways to improve features and flows. It’s also essential to design scalable solutions that can adapt to future updates without disrupting familiar user habits.