Torace: Going digital to improve mentorship programs

Mentorship programs in both the K–12 and Higher Education spaces play a critical role in educational development. From student-teachers aspiring to receive their teaching license to experienced educators working towards future leadership positions, these programs are critical to a school district’s success and hiring pipeline. However, the current process was time consuming and cumbersome to work with as the programs were often full of logistical challenges and relied on inefficient tools like multiple spreadsheets, too many emails, and sticky notes.

We built an invitation-based tool, named Torace, that allows educational institutions to efficiently manage the logistics of their various mentorship programs. The platform is highly adaptable to accommodate many different programs such as student teaching, new teacher mentoring, and leadership coaching. Administrators invite participants into Torace and from there, they’re able to organize, match, and track mentors and mentees throughout every stage of the program.

In addition to the cloud-based platform itself, we also designed and built a public-facing marketing website for Torace. Torace wanted the site to not only include an overview of the company and the platform but also have a blog section that the team could regularly update with mentoring resources, tips, and ideas. To keep the site’s maintainability as user-friendly as possible for the Torace team, we built it using Next.js and a headless CMS solution from JAM Stack called Contentful.

Review of existing research and prototype
In addition to the proof of concept that Torace brought to us, they also had a fair amount of market and user research to validate the need for the platform. This research included surveys and user interviews with potential customers as well as some usability testing of a low-fidelity prototype.

Our design process began by reviewing these research findings in order to uncover high-level themes, insights, and pain points. We carried those findings into the definition phase as we began to increase our understanding of the problem space.

Collaboration workshops
We kicked off the project by meeting with the stakeholders for a series of two half-day workshops. The first day consisted of reviewing Torace’s business, product context, and target audience. We also looked at the context of those user roles as well as a demo of the existing Torace prototype.

After fine-tuning those user roles, we defined four main personas that would interact with the system — Event Admins, Approvers, Mentors, and Mentees. In addition to the end-user roles, we also outlined a Superadmin persona who would primarily be responsible for top-level tasks like setting up school districts and managing district profiles.

For each persona, we plotted behaviors and actions, demographics and psychographic traits, and needs and pain points.

We put our newly defined personas to work during our second day’s exercise: Experience Mapping. Our goal with this exercise was to better understand how different roles within the education ecosystem would use and interact with Torace. It gave us a high-level picture of the intended experience while highlighting potential areas of friction.

Funny enough, the experience map began as a bunch of sticky notes on a whiteboard which was the very thing Torace is designed to eliminate.

Requirements definition
After completing the experience mapping exercise, we began to translate the customer journey into specific product requirements and capabilities that were broken down by role. Some of these requirements included creating a profile and managing preferences for Mentors and Mentees. For Event Admins, they needed to be able to set up and manage events, send invites, and match mentors and mentees.

User flows and information architecture
With more detailed product requirements in hand, we began to translate them into user flows that helped describe specific interaction patterns and use cases. A lot of our energy and effort was spent creating the mentor/mentee matching workflow. We then leveraged these user flows to build a site map and define the overall information architecture.

Wireframes
Based on our user flows, we were able to begin wireframing the site. All of the work we’d done up to this point allowed us to build annotated wireframes. Wireframe annotations serve as an extension of our design team to our developers and describe in detail exactly how elements on the screen are intended to function."

Visual concept and production
Since Torace already had a set of brand guidelines and documentation, we were able to begin designing the look and feel of the Torace platform and its accompanying marketing website. We started by creating a simple and clean visual design system. Every design decision we made was evidence-based and backed by our thorough research, journey mapping, and user flows.

Interaction design
To elevate specific features and components within the greater experience, we designed a handful of small micro-interactions. We kept these very subtle and minimal — hence, “micro” — so as not to distract the user from the overall experience. One example of these micro-interactions includes flipping from mentee to mentor when matching and pairing multiple mentors with a mentee.