How 58 Cloud Disk Redefined Enterprise Service Design: A Case Study

Project Background

In March 2019 I joined the enterprise service design team, responsible for OA and the "Meishi" internal services. These products differ from my previous design work: they iterate quickly, involve many versions and teams, and face issues such as inconsistent toolsets, low focus on service flow, difficult cross‑department resource coordination, and a user base of internal employees who provide direct feedback.

Why "58 Cloud Disk"?

"58 Cloud Disk" is a typical internal storage service I led. The design team initiated the project to meet internal demand and to provide the company with a stable, professional, and reliable enterprise storage solution, motivating multiple partners to collaborate.

Current Situation and Problems

The legacy cloud disk, used for several years, no longer meets functional needs and its interface looks outdated.

Redesign Goals

After extensive discussion, four goals were set:

Lightweight : Remove unnecessary elements, adopt an OS‑like design language, use whitespace and background colors to focus user attention.

Usability : Emphasize fast upload/download and quick content discovery, integrate entry points, prioritize high‑frequency functions, and streamline navigation.

Consistency : Establish a unified color system, 8‑pixel rounded corners, 45° shadow, and design icons for 23 common file types that retain familiar shapes while matching the new visual style.

Branding : Create a new brand identity, naming the product "58 Cloud Disk" and designing a logo that conveys speed and cloud service concepts.

Implementation Highlights

Lightweight design reduced learning costs; usability improvements reorganized information layout and highlighted key functions; consistency was achieved through a comprehensive icon set and unified visual language; branding introduced a new logo and visual identity.

Challenges Encountered

Icon scaling issues required adjusting sizes without changing component dimensions, deepening line colors, and refining details to improve recognizability. Data migration was hampered by legacy servers lacking APIs, necessitating manual transfer and extensive testing, resulting in hundreds of identified issues.

Post‑Launch Activities

After releasing version 2.0, new features such as external access, resumable uploads, and personal space were added. User feedback was collected, categorized, and prioritized for future iterations, while ongoing coordination among departments continued to be a key focus.

Conclusion

The design phase marked a milestone, but the product’s success depends on continuous feature discovery, resource coordination, testing, and iterative improvement. Designers must expand beyond visual work, adopt a product‑manager mindset, and drive the overall experience forward.