Trybe Talent Hub

Certainties, Suppositions and Doubts

What we knew, assumed and needed to explore

We knew the platform needed to support multiple roles and workflows — and that operational clarity was just as critical as user experience. We assumed students and instructors would benefit from guided journeys and contextual feedback. What we didn’t know: how much visibility each user needed, and how the service layer could adapt without bloating the interface.

This led to key decisions about structure, content hierarchy, and how to prioritize what’s seen (and by whom).

Hypothesis Mapping and Prioritization

Shaping decisions around what matters

We mapped hypotheses around flow clarity, user autonomy, and operational needs. We prioritized those that balanced high impact with low test effort — such as:

• Will contract visibility reduce support friction?
• Does onboarding in steps improve retention?
• Will separate dashboards for instructors and students improve task completion?

This helped focus design sprints around what was most likely to reduce confusion and increase autonomy.

User Research and Interviews

Testing what clarity means for each user

We validated our hypotheses through interviews with platform users — especially student groups and program coordinators.  Key insights: 

• Students needed clear expectations and task tracking
• Instructors needed performance overviews to adjust mentoring strategies
• Admins needed less micromanagement and more system-level visibility 

These shaped how we structured roles, access, and dashboards.

Strategic Benchmarking

Understanding what the market delivers — and what it still doesn’t solve

To redesign Trybe’s Tech Talent Hub, I conducted a strategic benchmark of learning platforms, educational management tools, and internal operational systems. 

This exploration revealed three key patterns: 

• Most platforms focus heavily on content and learning tracks, but neglect operational journeys 
• There is low differentiation between user roles, which clutters navigation and responsibilities 
• Few platforms offer visual guidance or autonomy features to reduce friction with support 

These gaps revealed a clear opportunity for Trybe to differentiate with a platform aligned with educational operations at scale, focusing on: 

• Action-oriented navigation 
• Operational clarity 
• Role-specific autonomy 
• Seamless integration between learning, career, and internal teams

User-Centered Design Canvas

A system designed around reality, not assumptions

The platform had to support asynchronous usage, fast decision-making, and clear separation of responsibilities.  User goals: progress visibility, guided feedback, task completion

• Tasks: viewing deadlines, giving or receiving feedback, tracking contract status
• Pain points: unclear flows, fragmented tools, support overload
• Emotional drivers: confidence, autonomy, clarity 

The UCDC kept the experience rooted in what each user needed — not just what the system could deliver.

Approach & Strategy

Designing for clarity in operational complexity  

The focus wasn’t on adding more features — it was on making the existing structure understandable, actionable, and scalable.

I prioritized structure over surface: clear journeys by role, simplified actions, and visual patterns that made daily decisions easier. Every interface was built to reduce operational friction and guide users toward their next step.

 The strategy: reveal what’s relevant, hide what’s noise, and make complexity feel manageable.

Key Learnings

Structure is what makes autonomy possible

• Users don’t want more control — they want the right level of visibility
• When roles are respected in the UI, support requests drop
• Autonomy is a result of design, not user training
• A clear system saves time for everyone, from students to leadership