End-to-end example
How does an idea on the floor become verified value?
An example in six steps, each with the product screen for that step. Steps, approvals and timings are set per company; this flow is one example running on the product.
Example flow
From the shop floor to the boardroom: one idea's path
Steps and timings are set per company; this is one example that runs on the product.
- 01
Spotted on the floor
An operator takes a photo from a phone or shared tablet, marks the problem on it; signs in with ID + PIN.
Sample company · demo data - 02
Pre-check and assignment
The process owner reviews, adds it to the reward pool and assigns the unit and person.
- 03
Root cause and action
Solved with fishbone and 5 Whys; before / after evidence photos are uploaded, the action closes.
Sample company · demo data - 04
Committee and reward
Committee members score without seeing each other; score and reward are recorded.
- 05
Value verification
The gain is tied to an indicator and measured; finance verifies; retention is tracked at 30 / 90 / 180 / 365 days.
Sample company · demo data - 06
Spread and memory
The successful case is proposed to other units or plants and becomes searchable in company memory.
Example flow: each company sets its own steps, approvals and timings.
Verified value
Forecast, measurement and verification stay apart
A Kaizen's gain is three separate numbers; the system never adds them up. Cash, time and avoided cost are reported separately too.
- 1 Forecast
12,000 TL / yr
Estimated by the person opening the case; stays labelled as a forecast.
- 2 Measured
9,800 TL
Measured from the linked indicator over 90 days; the baseline is frozen at link time.
- 3 Verified by finance
9,400 TL
Submitter and verifier are different people; returns and rejections carry a reason. Retention is tracked up to 365 days.
Figures are a fictional example, not a customer result.
Frequently asked
Our employees don't have e-mail. How do they sign in?
With their employee number and a 6-digit PIN. Print PIN cards as PDF from the admin panel; a shared-tablet (kiosk) mode is available too.
Can we build our own approval flow?
Yes. Steps, approvers, durations and conditions are configured in the admin panel; 'Try it' shows the outcome before publishing.
Is there a ready starting point?
Factory and Office/Service packages include layers, titles, roles, record types and flows; you can change everything afterwards.