Readout
EX app analytics review
A four-week reading of one employee experience app: who still answers, which teams have gone quiet, and what the comments actually cluster around.
This is the main piece of work we do. It is for a people lead, EX programme owner, or internal communications manager in Malaysia who already has an employee experience app in place and a sense that the vendor’s standard report is not answering the questions managers actually ask.
Who it is for
You are responsible for a pulse app, a recognition feed, a wellbeing check-in, or another employee experience app used across offices, plants, or mixed shift patterns. You can export or share the last ninety days of participation, question-level answers, and comments under your own access rules. You want a person to sit with that record and tell you, in writing, what it shows.
It is a poor fit if you are still choosing an app, if you want someone to run the programme for you, or if you need counselling for individual employees.
What you receive
You receive a written briefing on one primary app and one ninety-day window. The briefing names:
- which sites, shifts, or functions still answer, and which have thinned out
- which questions or prompts carry almost all of the traffic
- where comments cluster, and where they stop
- a short list of manager conversations the numbers support, and a shorter list they do not support
The packet includes the briefing itself, a one-page map of the ninety days, and notes from the two working sessions. You also get one follow-up conversation of up to forty-five minutes within two weeks of delivery.
What is not included
We do not build charts inside the vendor product, sell licences, administer the next survey round, or speak to employees on your behalf. We do not translate the entire comment archive; we read samples you select and the volume patterns around them. Legal discovery, disciplinary files, and medical information stay out of scope.
Who does the work
A Toolcabinbase reviewer in Johor Bahru leads the engagement. Sessions can be in the office at Office 10, 54 Demo Street, Johor Bahru 00000, or on a call if your people team sits in another state. Bahasa Malaysia and English source material can both be used; say which language the briefing should be written in when you enquire.
How the four weeks usually run
Week one is a kickoff and a data request list. You point us at the exports or screens you can share, and you name the sites and shifts that matter. Week two is the first working session: we walk the participation picture together and mark gaps that are artefacts of how the app was rolled out, such as a missing language pack or a login that never reached contractors. Week three is the second session, usually on comments and on the questions that everyone answers because they are easy. Week four is the written briefing and a short check that names and site labels are correct before it is final.
If a plant shutdown or a festive period sits inside the ninety days, we mark that on the map rather than treating a dip as a people-problem by default.
Preparation on your side
You will need a person who can export or screenshot the app’s own records, a named owner for the programme, and agreement on which employee groups may appear in the briefing. We work from counts and sampled comments, not from raw identity files, unless you expressly ask us to sit with identifiable rows in a supervised session.
Constraints
One primary app per review. A second app can be named as context, but it is not scored in the same packet. Coverage is Malaysia-based organisations; travel beyond Johor Bahru is quoted separately. We will not brief a board using numbers we have not seen.
Price and next step
Reviews are quoted from MYR 8,400 for a single app and a standard ninety-day window. Mixed shift patterns, dual-language comment sets, or more than six sites usually raise the fee. If you want this work, write to us with the app name, how long it has been live, and the period you care about.