Mentorship Platform - Design Lead, 3 Years

That was the situation when I joined. A mentorship platform meant to help people in their most vulnerable moments (mentees, parents, young adults) build real connections with someone who could guide them. The kind of product that makes you want to get it right.

The founder had been carrying this vision for over a decade. The team had tried before. But without a clear design structure, an intuitive UX, or a cohesive identity, the product never made it off paper.

In 2022, the founder rebuilt the team from scratch and bet on people who could finally ship it. I came in as design lead.

Three years later, the platform is live across three continents.

This is the story of how we got there, and what I learned along the way.

Self-funded. Tight timeline. A legacy tech structure nobody wanted to touch. A long, tangled set of business rules. And an old app that users had emotional attachment to, even though it barely worked.

There was no room for a slow ramp-up. We had to move fast and get it right at the same time.

I owned the design system architecture, the UX, and the processes that carried the team from concept to developer handoff. My job was to keep the product coherent across three layers at once: visual design, user experience, and business logic.

But the single reframe that changed everything was simple: ask more, understand more.

Stop assuming. Stop designing from your own mental model. Listen longer than feels comfortable, then listen a little more.

Four decisions shaped the rest of the project.

We spent four months on an onboarding flow. Research-backed. Tested with mentors and mentees. The team was proud of it.

Real users rejected it.

They didn't want what we built. They wanted something we hadn't considered. The flow made sense to us because we understood the whole system. They didn't, and we'd designed for our understanding, not theirs.

The save: we'd validated everything with high-fidelity prototypes before writing a single line of code. Engineering time lost? Almost zero.

The lesson that stuck: what a user asks for and what they actually need are often two different things. And the only way to find out is to put something real in front of them before you commit.

We had test partners in Zimbabwe waiting for a beta. The roadmap forced trade-offs that made me uncomfortable: compromises on consistency, on usability, on things I'd normally fight to protect.

I couldn't eliminate the constraint. But I could make sure nothing about the workaround was accidental.

I pushed to improve what already delivered value, then documented every single compromise as a known issue with a scheduled fix in the next round. The team knew exactly what we were shipping, what was temporary, and what the plan was to make it right.

Sometimes shipping something imperfect on time matters more than shipping something perfect too late. The key is knowing the difference and being honest about it.

Some requests from stakeholders would have weakened the product's structure down the line. Not immediately, not obviously, but in ways that would compound.

Early on, I would have just pushed back. By year two, I'd learned something better: bring an alternative, walk everyone through the reasoning, and show the downstream impact before anyone has to take a position.

We'd align on a path that kept the foundation solid without making anyone feel steamrolled. Put the trade-offs on the table early, and the hard conversations get surprisingly easy.

A few users hinted it would help to see their progress, not just track it. The signal was thin. No clear data to back it up. Just a feeling from a handful of conversations.

I believed in it anyway.

I designed the intention dashboard, a simple, clear way for users to see how far they've come. Built it, pitched it with almost no proof to point to.

It got approved. Users adopted it. Sometimes the best features come from listening to what people almost say.

A mobile-first ecosystem that pulled fragmented workflows into one coherent platform. Redesigned core flows. A community layer anchored by the intention dashboard. And a design system built to scale without dropping accessibility.

40% → 90% task success rate

3x faster navigation

60% fewer onboarding steps

40% fewer QA bugs

Validated through co-design sessions and real-world testing with 20+ beta users in the U.S. and Zimbabwe, backed by 100+ survey responses.

120+ active users across 3+ organizations. 92% positive feedback from mentors and mentees.

The mobile-first success opened the door to a web platform, now in development with early partner commitments.

The biggest shift wasn't about design. It was about me.

I learned to listen without already building my rebuttal. To sit with ambiguity longer than feels productive. Communication turned out to matter more than anything on screen.

The quiet trap of this kind of work is being so close to the product that you start designing for yourself. We understand the whole system; the user sees one screen at a time. Staying humble about that gap was the real job.

What I'd do differently: build a more solid, scalable foundation from the start. Think more globally instead of solving in closed pockets. Trust the process earlier.

Due to NDA I cannot show the project here, but I will be happy to talk about my learnings and process.