The Morning Starts Before the Office Does
Encik Razif arrives at his desk at 7:55am, five minutes early as usual. He sets down his coffee, opens his laptop, and immediately faces what has become a daily ritual: three separate inboxes, two WhatsApp groups with unread messages from last night, and a shared drive folder that nobody seems to update consistently.
He manages a mid-sized unit within a government agency — procurement, vendor coordination, staff reporting, compliance documentation. On paper, it sounds manageable. In practice, every single one of those functions lives in a different place, owned by a different person, and tracked in a different format.
By 9am, he has already spent the better part of an hour just locating information — not acting on it. Locating it.
The Mid-Morning Paper Chase
A department head calls. She needs the status update on a vendor payment that was supposed to be processed last week. Razif knows it was submitted — he remembers the email — but finding that email means scrolling through a thread of 47 replies, two of which include attachments with different version numbers of the same form.
Meanwhile, a staff member knocks on his door. She needs approval for a procurement request. The approval form is a Word document. It needs to be printed, signed, scanned, and emailed. The printer is on the other side of the office. The scanner is temperamental.
It is 10:30am. Razif has not yet started the actual work he planned for today.
This is not a story about an incompetent manager. Razif is experienced, organised, and genuinely committed to doing his job well. The problem is not the person. The problem is the system — or rather, the absence of one.
Lunchtime: A Break That Isn’t Really a Break
At 1pm, Razif eats at his desk. He is building a manual report in Excel — compiling data from three different spreadsheets maintained by three different colleagues, each using slightly different column headers. The monthly compliance report is due to the oversight body by Friday. It takes him roughly six hours every month to produce something that, with a proper system, could largely generate itself.
Public sector digitalisation in Malaysia is not a new conversation. The government has pushed for it through various initiatives and policies. But the gap between policy direction and what actually happens inside a unit manager’s daily workflow is, in many agencies, still very wide. The tools exist. The intent exists. The joined-up implementation, however, often does not.
Razif knows this. He has attended the briefings. He has seen the presentations. But today, at 1:15pm, he is still manually copying figures from one tab to another.
The Afternoon Approval Bottleneck
After lunch, three approval requests are waiting. Each one involves a different process:
- One requires sign-off from a superior who is attending an offsite meeting until 4pm.
- One requires a supporting document from a colleague who is on leave — and nobody else knows exactly where the file is saved.
- One has already been approved verbally in a meeting two days ago, but nothing has been formally recorded, so the process has to restart.
Without a central system where approvals are logged, tracked, and visible to relevant parties, every request essentially resets to zero the moment there is any ambiguity. Government compliance systems — the kind that create proper audit trails and accountability records — exist precisely to prevent this kind of rework. But many units are still operating on a patchwork of emails, phone calls, and shared drives that were never designed to carry this load.
Razif follows up via WhatsApp. He marks his own notes in a notebook. He sends a reminder email and copies the relevant parties. He does this not because it is efficient, but because it is the only way he has found to create some semblance of accountability in a system that was not built for it.
End of Day: The Work That Carries Over
At 5:30pm, Razif has a list. Not a list of things he completed today — a list of things that carried over from today into tomorrow. Roughly half of his intended tasks remain unfinished, not because he lacked the time in hours, but because so much of that time was absorbed by coordination overhead: searching, chasing, duplicating effort, and re-explaining context that should already be visible to everyone involved.
He sends a final round of messages, saves his Excel file with a new version number, and closes his laptop.
Tomorrow, the process starts again.
For many managers in the public sector, this is not an unusual day. It is a typical one. And the cumulative weight of it — the slow drain of energy, the missed deadlines, the compliance risks that build quietly in the background — is what makes the case for a proper operational system not a luxury, but a practical necessity.
What Changes When There Is a Central System
The shift is not dramatic or instant, but it is real. When approvals happen within a single platform, they do not depend on who is physically present. When documents are stored and versioned centrally, nobody loses an hour searching. When reports pull from live data instead of manually assembled spreadsheets, a six-hour task becomes a fraction of that.
For a unit manager like Razif, that means fewer late lunches at his desk. For an agency, it means better audit readiness, cleaner compliance records, and staff who spend more time on meaningful work and less time on administrative friction.
None of this requires a complete overhaul of how government units operate. It requires the right operational foundation — one that connects the moving parts that are already there.
If you are managing a government or public sector unit and you recognise any part of Razif’s day, Kunos was built for exactly this kind of environment. See how Kunos works in practice — book a walkthrough with the team and explore what a more connected operational day could look like for your unit.