Snapshot

Challenge

Core operations, quality control, and moderation had to be handled manually across disconnected channels. At the same time, clients lacked a single place to request work, review progress, and access their brand and website context.

Objective

Build a centralized dashboard system that handles backend control and quality workflows while also giving clients a dedicated hub to request, analyze, preview, and access website and brand information.

Product Direction

• Designed a dual-surface system: internal control operations plus a client collaboration hub.
• Centralized moderation, quality checks, and execution controls that were previously manual.
• Structured clear client lanes for:
  • Website requests and service changes
  • Request analysis and status visibility
  • Website previews and review states
  • Brand asset access and organization

Design Constraints

• Needed to serve two different audiences (operators and clients) without leaking operational complexity into client views.
• Required consistent request semantics so moderation and quality control remain predictable.
• Kept interaction depth low so both sides can complete high-frequency tasks quickly.

Key UX Decisions

• Separated internal control surfaces from client-facing surfaces while keeping one shared workflow model.
• Standardized request intake templates to improve first-pass quality and reduce back-and-forth.
• Kept preview and handoff states highly visible so clients can validate work without extra communication loops.

System Decisions

• Built a centralized request pipeline with explicit moderation and quality checkpoints.
• Connected website operations and brand asset access under one role-aware dashboard model.
• Structured status transitions so backend operations are trackable instead of manually coordinated.

Outcome Signals

• Replaced scattered manual handling with one centralized control layer.
• Improved quality consistency through explicit moderation and QA states.
• Gave clients a self-serve hub to request, review, and access core website and brand resources.

V1 Scope Decisions

• Focused v1 on request lifecycle, moderation, quality control, and asset access workflows.
• Deferred deeper automation and secondary modules until the control model was proven.

Build Notes

• Built shared status and request primitives used by both internal and client-facing surfaces.
• Implemented role-aware UI patterns so each user type sees only the context needed to act quickly.

Next Phase

• Add deeper request analytics and richer approval history for better operational visibility.
• Expand client self-service preview and approval flows across more service types.