Designing a Phase-Based Project Management Platform for Independent UX Designers and Project Managers
Reducing admin overhead, eliminating payment friction, and increasing client transparency through system-level design.
Client
UX Certification Case Study
Role
Product Designer
Duration
8 weeks
Year
2025
01 — Brief
Project Brief
This case study explores how I designed a phase-based project management platform that structurally connects: Deliverables, Approval, Invoice generation, Payment collection; Not just to improve workflow, but to protect revenue, reduce admin overhead, and increase client clarity.
02 — Challenge
The Challenge
As a UX designer who also manages projects, client communication, invoicing, and payments, I've experienced firsthand how fragmented the workflow of independent designers can be. We think in phases: Discovery, Wireframes, UI, Testing, Handoff; but the tools available to us are built around tasks, tickets, and generic project boards. The result? Operational friction. Designers end up stitching together multiple tools to: Track progress, Communicate status, Generate invoices, Collect payments, Prevent scope creep. This fragmentation creates invisible labor, delayed payments, and unnecessary emotional stress. Through research and synthesis, I identified a core misalignment: Project progress, client trust, and revenue flow operate in separate systems.
Key pain points
- 01Project updates, approvals, and billing distributed across tools
- 02Manual follow-through between phase completion and invoicing
- 03Unclear boundaries for additional work
- 04Scope Creep from Phase Ambiguity
- 05Clients lacking a simple view of the current milestone and upcoming payment
- 06Administrative effort required to reconcile progress and payment status
"Independent UX designers don't struggle with task management. They struggle with aligning project progress, client understanding, and revenue flow inside one coherent system."
03 — Solution
The Solution
The proposed platform organizes projects around phases such as discovery, wireframes, interface design, testing, and handoff. Each phase connects its deliverables, client approval, invoice trigger, and payment status. A client-facing dashboard presents the current milestone and upcoming payment schedule. An additional-work flow captures the proposed scope and cost for approval before activation. The concept also explores generating an invoice after phase approval and connecting payment to the start of the next phase. These are proposed product behaviors, not verified payment integrations. Payment-gated progression needs further evaluation against different client agreements, billing schedules, and exceptions before implementation.
04 — Process
Design Process
Problem Framing
Used my experience coordinating design delivery, client communication, and billing to frame the disconnect between project milestones and administrative follow-through.
Core Workflow Concept
Defined the phase as the organizing unit. Connected deliverables, approval, invoice generation, and payment status rather than treating task completion as the end of the workflow.
Information Architecture
Structured the concept around projects, phases, deliverables, and their approval and billing information. Distinguished the client’s milestone view from internal project detail.
Client Visibility & Scope
Outlined a dashboard showing the current phase and upcoming payments, plus an additional-work flow that makes proposed scope and cost explicit before approval.
Payment Dependencies
Proposed approval-triggered invoicing and payment-linked progression. Identified the need to evaluate these dependencies against real billing arrangements and exceptions.
Validation Priorities — Next Step
Evaluate whether designers and clients can identify the current milestone, understand an approval request, and interpret what payment enables. Measure administrative effort and approval-to-payment time before claiming efficiency or revenue improvements.
05 — Impact
Impact & Results
Defined a phase-based product concept connecting deliverables, approval, invoicing, and payment status
Specified a client dashboard centered on milestones and upcoming payments
Outlined an additional-work approval flow for scope changes
Identified time from phase approval to payment as a future evaluation metric
Defined administrative effort and client understanding as outcomes to validate
06 — Artifacts
Visual Artifacts