Case study

Discord Sourcing Tracker

Turning recruiting activity into a decision system

SeekOut ↗

Choose your depth

The problem, my contribution, outcomes, and strongest screens.

My role

Product design · Analytics strategy · Enterprise workflows

Product focus

A sourcing operations system that links portfolio health to requisition and candidate evidence.

Overview

I designed a sourcing tracker that connects portfolio progress, requisition health, funnel conversion, rejection patterns, people insights, and candidate evidence in one operational view.

The problem

Recruiting teams could report what happened, but struggled to trace performance back to the requisition, activity, person, or decision that caused it.

What I drove

Created a layered information architecture from executive health to candidate evidence.
Paired headline metrics with conversion, rejection, and people insights.
Structured activity around time, event type, actor, and volume for traceability.

What changed

Created a path from executive-level health to the activity and evidence behind a result.
Kept filters, time ranges, actors, and funnel context attached to every metric and drill-down.

Impact

What the work was designed to move

Business impact

Connected executive health, requisition performance, team activity, and candidate evidence in one operating view.

Customer impact

Recruiting teams can move from a headline result to its cause without reconstructing context across disconnected reports.

Revenue impact

Makes product value more visible through measurable recruiting outcomes, supporting adoption and account retention.

Highlights evidence

3 essential screens from the final experience.