On Remind’s growth team, we looked for high impact, low investment opportunities to expand Remind’s reach and bring the value to more teachers and students.
What is Remind?
Remind is a communication platform that brings teachers, parents, students closer together and improve student outcomes. It improves their ability to collaborate, communicate and stay in the loop.
Think: Slack for Education or the 21st century version of handouts, phone calls home and sticky notes on returned work all rolled into one.
The People Tab was an experiment to simplify how teachers interact with specific students and parents and leverage the school connections buried in teacher’s phonebooks.
In the minimum viable product, a teacher could:
- Add new people to a class from their phone’s address book.
- View who they were connected to on Remind
- Start a direct message conversation with a Remind connection
- Number of Invites Sent from People Tab
- Number of Invites Sent to new contact points
- New Activations (Member’s who joined at least one class)
Baseline with Stake Holders
In a weekly growth team session, we came up with the idea of creating a unified list of members leveraging a teacher’s contact book. Because it was the first time we would show all the
Flows and New Components
After framing up the initial brief, we set out our initial assumptions to paper, asked our user’s their concerns about mixing personal and school contacts, then iterated accordingly.
Through the creation of this tab, we realized we would need to update our pop-up modal component and the full screen takeover.
Pop-up Modal: As the smaller of two dismisable actions in the Remind design system, we wanted the action to feel as lightweight as possible but still give context. For this purpose, we decided to add an image representing the class to this modal component.
Full Screen Takeover: Prior to the People Tab, we had not added complex interactions to a full screen takeover. For this project, we created a custom list view with text CTA’s and used the full screen takeover component at its base to make sure the experience felt consistent.
Through rounds of user research, we gleaned that teacher’s believe in a sort of division of church and state between their work lives and their personal lives. With an aggressive growth lean and an understanding of these concerns, we designed the list view to gracefully push the phone book contacts out of view as a user’s Remind community grows!
A there were a number of design decisions that contextualized the experience for teachers:
- If a teacher had a number of participants that was less than the screen height, they would see their phone’s contacts. This decision was a bet that teachers with address book permissions were more likely to add participants they already had stored contact information for.
- Reduce the number of decisions that an onboarding teacher needed to make. Because all parents and students need to be associated with Remind class, A teacher has to select which class to put a participant in. If the teacher only had a single class, we skipped this decision point.
- Leverage system UI when possible. When a user had to choose one of many contact points (ie phone or email) we used an action sheet to lean on an existing UI convention and make it seem like a lightweight task.
What I learned…
Shape Research with Data.
Use data to frame up how a users interact with your product. Use research to understand why. Use your brain to avoid assumptions.
Peek over the edges.
The fuller the picture, the better the results. Look for the corner cases, understand the parts of existing product it will impact and follow known conventions.
Everything is an experiment.
Approach every design problem with scrutiny. Believe in its validity as you design it, but set key metrics that will determine if a design is successful.
Impact — Big and small.
Changing a typeface may impact all of your users in small, tangible ways. Acquiring one new user gives them every benefit your product has to offer.