THE STRUCTURAL FRICTION NOBODY COULD SEE

I led structured stakeholder interviews with founders, HR leaders, and operational managers. Each session explored the same territory, where execution breaks down, how performance is actually tracked, and which signals remain invisible to leadership. What surfaced wasn't one problem. It was five, stacked on top of each other.

A PERFORMANCE OPERATING SYSTEM, NOT ANOTHER SURVEY TOOL

The solution couldn't be a feature list. It had to be a system. Rolekick was designed around five interconnected pillars, each addressing a real failure point uncovered in research, each designed to work as part of the whole.

REDEFINING THE PRODUCT BEFORE OPENING FIGMA

When I joined, the company already had WeThrive, a subsidiary application focused on engagement surveys and sentiment tracking. It was working. But leadership was feeling a ceiling. Engagement data was useful, yet it wasn't driving performance conversations. It wasn't connecting to goals. It wasn't showing executives how daily work tied back to strategy. The kickoff phase wasn't about designing screens. It was about redefining what the product actually was.

Step 1, Clarifying What This Product Is Not

Through Zoom workshops and ongoing Slack sessions, we aligned on one non negotiable: this could not be just another engagement tool. WeThrive measured sentiment well. What was missing was performance visibility and strategy alignment. We agreed the new platform needed to go beyond surveys entirely and become a structured performance system.

Step 2, Defining the Real Problem

Through internal conversations with stakeholders and product leads, we identified the core tension. Engagement data existed but wasn't connected to goals. Managers lacked structured visibility into performance. Leadership couldn't see what teams were actually working on. The issue wasn't collecting more data, it was connecting execution to strategy.

Step 3, Mapping the Employee Lifecycle

Instead of listing features, we mapped the actual employee journey end to end: Onboard, Set Goals, Run Touchpoints, Give Feedback, Measure Engagement, Develop Skills. That map exposed the fragmentation immediately. Engagement was only one stage in a broader performance loop, and every other stage was completely unaddressed. That lifecycle became the backbone of the product architecture, the navigation, and every role definition that followed.

WHAT THE RESEARCH KEPT SAYING

Research was primarily internal, supported by the team's existing product context from WeThrive and ongoing stakeholder input. We ran competitive analysis sessions with stakeholders, workflow mapping focused on HR and manager pain points, and MVP scoping against real development constraints. Three findings kept coming up across every session.

REDUCING COMPLEXITY WHILE INCREASING CLARITY

Ideation centred on one principle: complexity for the user is a design failure. Every decision in this phase was about reducing what the user had to think about while giving them more power to act. Four key decisions shaped everything that followed.

ONE PLATFORM, THREE COMPLETELY DIFFERENT USERS

Defining user roles wasn't a permissions exercise, it was a product design decision. Each role needed its own mental model, its own entry points, and its own logic for what success looked like. Designing them as one unified experience would have been the wrong call.

DESIGNING THE AI COACH

The AI coach was designed to support managers and HR teams with contextual insight across the full employee lifecycle. The key design constraint was trust, if it felt like a gimmick or added noise, it would never get used. So I designed it to feel less like a product feature and more like a colleague who always has the right context.

It Enables Users to Ask

WEB AND MOBILE, INTENTIONALLY NOT IDENTICAL

Rolekick was designed for both web and mobile, but with a deliberate split in capability. A complex platform forced into full mobile parity becomes friction, not flexibility. So I made the call early: web and mobile serve different moments in the user's day, and the design should reflect that.

WHAT DEVELOPMENT FEEDBACK CHANGED

As development progressed, internal feedback highlighted two areas that needed more clarity and structure than the initial design provided. Both changes were significant, not cosmetic refinements, but architectural additions that changed how users moved through the platform.

Dedicated Feedback Section

Feedback had been embedded within the broader workflow. Development testing showed it was hard to find, and harder to track historically. I separated it into its own module, giving it dedicated navigation, a clear history view, and a more discoverable request flow.

Skill Matrix Module

A full competency matrix was added to track individual and team strengths and development gaps. It connects performance data to growth planning, giving HR and managers a shared language for talent decisions instead of relying on gut feel.

IMPACT, OUTCOMES & WHAT THIS TAUGHT ME

Rolekick is currently in active development. The product matured from an engagement focused toolset into a scalable performance and strategy alignment system. Four outcomes define where it landed.

This project strengthened my ability to design complex multi role platforms, balance business strategy with UX clarity, and integrate AI responsibly into real workflow tools. The biggest lesson it reinforced: the best internal tools don't add more features. They remove uncertainty and give teams the clarity to act.