Back

Turning fragmented data into skill visibility

TL;DR

I designed t centralized skill and project platform "StackTrack" that helps Public Cloud Group GmbH's managers staff projects faster while giving employees a clear way to document and validate their growth.

Role
Lead Designer · Research, strategy, UX, design system
Timeline
8 weeks · Discovery to pilot
Team
3 designers · 1 PM · 4 engineers
Prototype
Display sample of the webpage stacktrack
Problem

Fragmented data made staffing slow and growth invisible

Inconsistent management systems meant there was no reliable view of employee skills or availability. Managers spent days searching for talent, while employees struggled to receive recognition for growth and sales struggled to judge project fit.

Disconnected workflows
No clarity
Opportunity

Solve staffing and recognition together

Create one platform that connects employee skills, availability, peer feedback, and active projects instead of treating each need as a separate product.

How might we make skills credible, visible, and immediately useful for project staffing?
At a glance

A shared source of truth for organizational skills

The work covered research, product strategy, interaction design, prototyping, design systems, and sprint planning.

Surface
Responsive web app
Audience
Project Managers, Engineers
Stage
In Development
Methods
Research, strategy, UI/UX, systems
"

"I know we have someone with this skill. I just don't have the whole day to look for them."

Project Manager
Research participant
Research Insights

Managers and employees exposed one connected problem

Conversations across management and non-management roles revealed how fragmented systems harmed both staffing speed and employee growth.

8 interviews
Workflow mapping
Product demo
01
Availability was difficult to verify
Managers lacked one reliable view of any employees capacity.
02
Skill evidence was inconsistent
Self-reported proficiency needed peer context to feel credible and useful.
03
Growth lacked visibility
Employees needed a clearer path to show progress and receive recognition.
Jwt user journey map
Staffing Journey

Flipping the script

Taking the user journey for project staffing and flipping the order in which a project is created resolves a lot of uncertainty.

01
Create
Create a new project in StackTrack
02
Select required skills
From the central database of available skills
03
Select people
Chose from the aggregated list of available people with your selected skill
04
Stay updated
Trigger regular feedback cycles during the project lifecycle
Key Screens

Three views that connect the system

Skill Explorer supports talent discovery, Peer Feedback builds credible proficiency, and Project creation adds staffing context.

01 - Discover
stacktrack dashboard v2
02 - Validate
stacktrack skill explorer view v2
03 - Plan
stacktrack feedback cycle view v2
Accessible UI System

The rules behind the polish

Darkmode compatibility, a clean, simple look, a color space that supports concentration, accessible contrast values.

01
02
03
04
05
Button Text
Search for xyz...
Dark mode

From guided steps to one efficient pageThe bare minimum for developers

Having a dark mode ready from day one was a foregone conclusion considering the target audience.

Usability testing

Testing the riskiest assumptions first

I had 5 participants (3 PMs, 2 Engineers) test the prototype by giving them 3 tasks each to complete and having them fill out a questionnaire afterwards.

5 testers
3 tasks
Moderated remote
Users did not understand the state of feedback cycle participation.
High · 4/5
Users had difficulty reading the text on the skill level markers.
High · 4/5
The dashboard did not give users the information they were expecting.
Medium · 3/5
Project creation was clear and error-free.
Validated · 5/5
Users had no problems finding and adding skills.
Validated · 5/5
Task completion
84%
+34% after iteration
Confidence score
4.7/5
Rated by testers
Time on task
-38%
Median over iterations
Critical Errors
0
Down from 3 in V1
Learnings

What I'd carry into the next Project

While no real data exists for a post-launch review, the feedback after the demo showcase was overwhelmingly positive. The project reinforced that testing, accessibility, and content design all need to shape the system

01
Design the decision, not just the screen
The highest-leverage work was clarifying process logic before refining interface details.
02
Prototype with real complexity earlier
Representative edge cases exposed interaction debt that happy paths concealed
03
Microcopy defines product tone
Replacing “Master” with “Expert” made the proficiency model feel more inclusive and current.

Want to see more case studies?

  • JWT Ticket Portal

    Taking support ticket creation from manual to digital

    link to cook&go app store page

  • Alpaca Operator

    Modernizing a near-20 year old SAP System Manager

    link to cook&go app store page

  • Caparol App

    Optimizing UX by reducing navigation redundancy

    link to freenet.tv website

User Centered

Every product decision is made to inform, support and enable users. This is what ultimately generates revenue.

Structured

I make sure that interactions feel natural and visual hierarchy is clear. I test my ideas and base decisions in data.

Accessible

The products I create are designed with accessibility in mind. This also means my solutions are robust and scalable.

Have a project in mind?

Say Hi 👋
‍

dier.quinn@gmail.com

Design & content by Quinn Dier. Made with WebFlow.