CASE STUDY · LEAN MINI PROGRAM
For a discrete manufacturing enterprise, we delivered a DingTalk lean mini program and PC admin console—moving shop-floor proposals, task acceptance, verification, and points rewards into the app people already use every day.
WHY IT WAS NEEDED
Many manufacturers already have improvement methods and executive commitment. What they lack is a digital mechanism that runs propose → review → accept → verify → reward—and keeps working as more people join. When Excel, WeChat, and manual tallies carry the process, participation, cycle time, and reusability hit a ceiling fast.
Frontline intake
Issues travel by hallway talk or group messages. Proposals miss photos and standard fields; IE teams chase context before they can review. Slow feedback trains people that reporting does not matter—participation drops just when lean needs to go deeper.
Without one intake path and fast feedback, improvement stays occasional—not daily.
Closed loop
IE reviews in email, managers assign in WeChat, progress is chased by phone. No one sees who owns which stage. Monthly reviews rely on memory—not cycle time, line-level throughput, or overdue tasks you can act on.
Without a shared state machine, improvement cannot be measured, governed, or reviewed.
Rewards & reuse
HR tallies contributions in spreadsheets while staff feel no return. Winner lists go on a wall, but strong proposals never enter a searchable case library. Knowledge does not compound—incentives fade—and the program slips back into campaign mode.
Without automated rewards and case reuse, scale pushes ops back to manual work.
The client did not need a feature checklist—they needed a lean digital solution that scales as more people participate.
OUR APPROACH
Instead of building from a flat feature list, we mapped the primary chain—propose → review → accept → verify → reward—and split responsibilities between mobile and admin.
SOLUTION
Five modules that stand alone yet run together for manufacturing lean operations.
IS THIS YOU?
These situations are common in manufacturing and discrete production.
HOW IT WORKS
Not a screen inventory—a realistic path for one improvement proposal through the system.
TECHNOLOGY
Architecture combines DingTalk with an enterprise admin layer—frontline participation, review governance, and exports embedded in the lean workflow, connected through org sync and notifications.
Architecture
DingTalk mini program + PC admin + DingTalk Open API + business database + messaging
DingTalk mini program (propose / accept / store / culture) · PC web admin (review / voting / stats)
DingTalk OAuth · Org structure sync · Work notifications
Proposal state machine · Points rules · Voting & case library · Redemption flow
Proposal / points / redemption export · Ops stats and trends
Keywords
OUTCOMES
Business outcomes the client can observe after delivery—without unauthorized operating metrics.
Reusable pattern
DingTalk entry + business loop + admin governance + points ops fits many ToB field scenarios—establish the propose-to-reward loop first, then extend modules.
Shop-floor CI, proposal management, cross-team assignment
Hazard reporting, corrective tasks, verification, safety points
Store issues, regional acceptance, inspection improvements, ranks
Idea intake, review voting, project claiming, showcase
Org sync, tiered review, delegated governance, rollup exports
Planning a DingTalk lean mini program or manufacturing platform? The hard part is rarely a single screen—it is wiring propose, accept, verify, and points into one loop. We can start from your org rules and incentive design to shape phase one.
Tell us about your projectA 30-minute intro: share your improvement flow and main loop
Related cases
Other projects delivered by Wavesteam — AI, IoT, platform builds and enterprise software.
An in-vehicle BMS monitoring platform with a full data pipeline and a clean migration from a legacy system to a modern stack.
Read the case study
A CAD-driven AI quotation system that collapses traditional mold pricing from days to minutes for manufacturing teams.
Read the case study
A structured operations engine for badminton communities — dynamic supply-demand matching, a match state machine and an automated ops pipeline lifting per-group monthly events from 8 to 35.
Read the case studyThese projects usually involve business systems, device integration, AI workflows or multi-role back-offices. We assess feasibility against real delivery constraints and give recommendations close to the implementation stage.
