Hunliji Case Management Redesign

Haicao Cloud served the merchant side of Hunliji. Any merchant category that needed to upload cases used this workflow to publish work and maintain its case library.

The project was triggered by merchant feedback and product planning. An archived funnel showed a steep drop between starting a case and publishing it, but the number alone did not explain why merchants stopped.

Product and Operations conducted more than 100 phone interviews and shared the findings with me. Merchants described long forms, unclear progress, slow classification, and tables that were difficult to read on small laptops.

I was responsible for the complete redesign across merchant Web and App. Both surfaces used the same case fields and served the same merchants, so I treated them as one system rather than two separate redesigns.

Publishing and browsing were frequent. Sorting and category administration still mattered, but they did not need equal visual weight. I brought category edits into the list, reduced page changes, and kept lower-frequency actions available without letting them dominate the layout.

I made case state, category, and primary actions easier to find. Merchants could see category counts and edit names or order without opening each case.

Small-screen laptops were a real use case, so I defined table rules for density, text and image rows, responsive column widths, horizontal scrolling, and fixed important columns.

Publishing asked for a large amount of information. Instead of extending one continuous form, I grouped the work into three visible steps.

Merchants could see their progress, save a draft, and understand what remained before submission.

I designed the merchant Web and App as one project. Because both platforms served the same merchants and used the same case fields, changing the underlying model between them would have created unnecessary ambiguity.

I kept the information hierarchy and visual rules consistent, then adapted the layout for mobile. Publishing stayed prominent. Category management and sorting became secondary actions, while case cards exposed the information needed for quick browsing.

After launch, the relevant product team validated the Web and App experience. The surviving project record includes the one-month outcome figures below.

The original dashboard, sample definition, and detailed validation method are no longer available, so the results remain historical evidence rather than independently reverified analytics.

The original portfolio records a 30-second reduction in case-filling time, a 48-second reduction in total publishing time, an 18.4% increase in completion, and a 12% reduction in page drop-off one month after launch.

The original dashboard, sample definition, and calculation method are not preserved. These figures can be retained as the product team’s historical record, but they have not been independently reverified.