home
0%
Product Design — Hesai Technology — 2022–2023

A 0-to-1 internal platform that turns employee ideas into tracked, implemented action

Timeframe
2022–2023
Role
Product Designer (Solo)
Scope
Internal Platform · 0→1
Impact
234 suggestions · 65% adoption
Suggestion system overview

Good ideas existed everywhere — but had no place to go

01

Hesai Technology's 800+ employees had no formal channel to surface process improvements. Ideas were shared informally via chat, then lost or forgotten.

02

Management had no visibility into which suggestions were submitted, under review, or implemented — leading to duplicated effort and missed opportunities.

03

Without a system, there was no accountability. Employees stopped suggesting because nothing seemed to happen.

Understanding the suggestion lifecycle

All Employees

Submit ideas, track status

Frustrated by the black-box — ideas submitted but no feedback received

Admins

Triage, assign, manage workflow

No tools to manage volume; relied on spreadsheets and memory

Implementers

Execute approved suggestions

No clear handoff — unclear scope, priority, or deadlines

Suggestion Flow
Suggestion lifecycle flow
01

Transparency is the core need

Users didn't need a fancy interface — they needed to know their idea was received, reviewed, and acted on.

02

Admins are the bottleneck

Without clear tooling, admin workload scales linearly with submission volume. The system needed to reduce their cognitive load.

03

Implementers are forgotten

Existing processes skipped directly from approval to completion — implementers had no dedicated workflow.

A platform for the full suggestion lifecycle

Three distinct interfaces — one for each role — unified under a single system. Every suggestion has a traceable journey from submission to resolution.

Five-Stage Lifecycle
01
Submit

Employee fills a structured form with problem description, category, and supporting details

02
Accept

Admin reviews, accepts or rejects with reasoning, then assigns to the relevant department lead

03
Implement

Department lead confirms the issue, creates an action plan, and tracks weekly progress

04
Evaluate

Admin reviews the implementation report and submits a completion assessment

05
Complete

Submitter receives the final result; suggestion is published to the company feed

Plan A — Role SwitchingNot chosen
Plan A

Users manually switch between roles to see different views. Tested with 12 users — felt confusing and context-switching was disruptive.

Plan B — Status-BasedChosen
Plan B

Interface adapts to the suggestion's current status. Users always see what action is relevant — no switching required. Preferred by 10 of 12 testers.

Two interface approaches, one clear winner

We debated between manual role-switching and a workflow-driven interface. Testing with 12 employees showed status-based views were more intuitive for tracking suggestion progress.

12
Users tested
10/12
Preferred Plan B
5 min
Avg. task completion (Plan B)
11 min
Avg. task completion (Plan A)
Feature
All Employees
Admin Team
Department Leads
Submit
Structured form with category & attachments
Track
Real-time status, timeline, notifications
All submissions dashboard
Assigned tasks view
Review
Accept / reject with reasoning
Completion report + score
Execute
Assign to department, forward out-of-scope
Action plan, weekly updates

Three roles, three purpose-built views

All Employees
Browse → Submit → Track → Celebrate

A public feed surfaces implemented suggestions for company-wide learning. Every employee can see their idea move from submission to resolution.

Public feed showing evaluated and implemented suggestions
Personal dashboard for tracking each suggestion's live status
Category-based browsing to reduce duplicate submissions
Employee homepage
Submitters
Describe → Categorize → Submit → Monitor

A structured form captures the problem, proposed improvement, and supporting details. After submission, real-time status updates replace the previous black box.

Guided form with problem description, category, and evidence fields
Live status tracking from submission through implementation
Notification when suggestion is accepted, rejected, or completed
New suggestion form
Admins
Review → Accept / Reject → Assign → Evaluate

Admins see only their department's queue. Every decision is documented — rejections require reasoning, acceptances trigger automatic assignment.

Department-scoped queue to prevent cross-team confusion
One-tap accept with implementer assignment, or reject with required reason
Out-of-scope suggestions can be forwarded to the correct department
Admin review screen
Implementers
Confirm → Plan → Update weekly → Submit report

Assigned implementers get a dedicated workflow that didn't exist before — a structured handoff with scope, timeline, and a weekly check-in cadence.

Issue confirmation step with the original submitter
Action plan with milestone tracking and weekly progress updates
Completion report submitted for admin evaluation before marking done
Implementation screen
Suggestion Center
Company-wide overview & analytics

Leadership gets aggregate visibility — submission volume, implementation rates, and department breakdown — without touching individual entries.

Suggestion center overview
234
Suggestions Submitted
152
Implemented
65%
Employee Adoption
500+
Hours Saved / Month

"The platform replaced what used to be a black box. Now every employee can see their idea move through the system — from submission to implementation."

Internal feedback — Operations team · Sep 2023
Scope

Start with the admin, not the employee

The admin experience determines the system's health. A well-designed triage flow prevented the bottleneck that killed the previous informal process.

Trust

Transparency builds participation

The #1 driver of engagement was status visibility. Once employees could see their ideas move, submission rates increased consistently.

Research

Three roles, three mental models

What admins needed (volume at a glance) was the opposite of what submitters needed (personal context and detail). Splitting the views was the right call.

Craft

Simplicity at scale is a design problem

With 500+ employees on day one, information architecture mattered more than visual polish. The list-first design held up under real load.