Design Brief: Marketplace & Driver Compliance UX

🔎 Problem Statement

Customers need a streamlined way to:

• Use the Marketplace for add-ons and integrations (currently incomplete and inconsistent).

• Distinguish between warnings vs enforcement when compliance issues arise.

• View and compare driver credentials, certifications, and capabilities quickly and easily.

Today, these workflows are fragmented, hard to understand, and create uncertainty for both dispatchers and drivers.

🎯 Goals & Outcomes

• Marketplace: Deliver a polished, intuitive, self-service Marketplace (browse, search, enable/disable).

• Compliance: Provide a clear warning → enforcement system that’s transparent and consistent.

• Driver View: Give dispatchers an easy-to-read dashboard of driver credentials & capabilities.

Success Metrics

• ≥80% of pilot users find the Marketplace “easy to use” in testing.

• Dispatchers can identify compliance issues in <10 seconds.

• Fewer support tickets related to integrations or compliance confusion.

⚡ Key Design Challenges

1. Marketplace Experience

   • Consistent Marketplace card layout (icon, title, description, pricing).

   • Clean detail page template for each item (screenshots, enable toggle, docs link).

   • Install/enable flow must feel seamless.

2. Warning vs Enforcement UX

   • Visual differentiation: warning (yellow banner, informational icon) vs enforcement (red banner, blocking action).

   • Example: expired insurance = enforcement; license expiring soon = warning.

   • Dispatcher view + optional driver-facing notifications.

3. Driver Profile & Capabilities View

   • Profile layout with:

     • Core info (name, photo, contact, status).

     • Credentials (with badges for valid / expiring / expired).

     • Capabilities & certifications (vehicle type, temperature handling, hazmat, etc.).

   • Comparison mode (multiple drivers side-by-side).

   • Integrate warnings/enforcements directly into this view.

    

⛓ Constraints

• Must align with CXT Design System (components, spacing, typography).

• Responsive: dispatcher desktop + mobile driver-facing warnings.

• MVP scope: Marketplace polish + compliance dashboard.

📦 Deliverables & Artifacts

• Marketplace: Wireframes + hi-fi mockups (Figma).

• Compliance Flows: Warning & enforcement UX flows (dispatcher + driver).

• Driver View: Driver profile dashboard designs.

• Prototype: Interactive Figma prototype for usability testing (5–8 users).

• Handoff Package: Final mockups linked in Jira + Confluence PRD.

🗓 Next Steps

• Gather relevant feedback from Productboard & Jira.

• Run a Design Sprint → wireframes → hi-fi mockups.

• Validate with dispatchers (driver workflows) & internal Marketplace users.

• Iterate, finalize, and attach to PRD for engineering.