01PUBLIC WEBSITE + DASHBOARD↗
09Impact
IMPACT / WEB + DASHBOARDProjectKix — Turning contribution into impact
A public-facing sneaker-reuse experience paired with an operational dashboard for managing contributors, bags and impact workflows.
PRODUCT / EXPERIENCESELECTED CASE STUDY
01Approved product mockup / presentation visualScroll to explore ↓
INTERFACE STUDY
ProjectKix interface system
The supplied public website and operational dashboard are kept as desktop experiences rather than forced into mobile frames.
THE CONTEXT
Start with the why.
The supplied ProjectKix material includes a public website and an administrative dashboard. The public experience explains the contribution journey and impact story, while the dashboard organizes operational areas such as contributors, bags, associations, affiliates and transactions.
01 / DISCOVERY
What the experience revealed.
Before shaping the interface, the work is framed around the user's mental model, moments of friction and the opportunities that can change the journey.
KEY OBSERVATIONS
01
The public site needs a clear reason to participate before introducing operational detail.
02
The contribution journey benefits from a small number of understandable steps.
03
The dashboard needs entity-based navigation because operational work spans several connected records.
PAIN POINTS
×
Public impact story competing with calls to action
×
Multiple operational entities to manage
×
OPPORTUNITIESDense dashboard data can become difficult to scan
↗
Make the contribution journey visually sequential
↗
Use impact and process storytelling to build confidence
↗
Organize dashboard navigation around operational entities and tasks
02 / INFORMATION ARCHITECTURE
Structure before surface.
The interface follows a clear information hierarchy so visual polish supports the product model rather than hiding it.
01Public: Why / How it works / Contact→
02Dashboard: Overview / Reports / Bags / Contributors / Associations / Affiliates / Agents / ACH / Settings
THE PROBLEM
An impact initiative needs two experiences to work together: the public journey must make participation feel simple and meaningful, while the operational side must make the resulting activity manageable.
DESIGN HYPOTHESIS
If the public story reduces the contribution journey to clear steps and the dashboard organizes operational data around recognizable entities and tasks, the system can feel approachable on both sides.
WHO IT SERVESPeople learning about ProjectKix and contributing used sneakers, alongside operational users managing contributors, bags, associations and related transactions.
03 / USER JOURNEYFrom first intent
From first intent
to useful outcome.
The journey is intentionally expressed as a sequence of decisions, not a list of screens. This keeps the case study about behavior and product thinking.
01Understand the missionentry
02Learn how contribution worksdecision
03Choose to participatedecision
04Operational team receives and manages the contributiondecision
05Track activity and related recordsoutcome
04 / PROCESS
How the work moved forward.
01
01 — Public journey
Create a clear narrative from the mission to the action required from a contributor.
Landing hierarchyImpact storyContribution steps
02
02 — Operations
Translate the administrative workload into recognizable dashboard areas and a scannable overview.
Dashboard IAEntity navigationOverview patterns
03
03 — Connect data
Make operational states understandable through consistent tables, cards, reports and transaction surfaces.
Data patternsStatus statesReporting structure
04
04 — Refine
Use a strong red, black and white visual identity consistently across public and operational surfaces.
Visual systemResponsive rulesUI polish
05 / DESIGN DECISIONS
Small choices create the experience.
These are the decisions that make the final interface feel coherent rather than merely polished.
01
Keep the public story human and action-oriented.
02
Use clear step sequencing for contribution.
03
Group operational navigation by the entities teams actually manage.
04
Use status and hierarchy to make dense dashboard information scannable.
06 / UI SYSTEM
A visual language that scales.
Instead of designing each screen independently, repeated behavior becomes a system. That gives future screens the same rhythm and makes implementation more predictable.
COMPONENTS
01Impact sections↗
02Process cards↗
03Dashboard navigation↗
04Overview cards↗
05Operational data patterns↗
Designed around the decision.
07 / OUTCOME
A paired case study demonstrating how a public-facing impact story and an internal operational product can share one coherent experience.
Narrative is based on the supplied ProjectKix website/dashboard screens and public project context; no unsupported impact metrics are claimed.