A vacation is a curated collection of still frames that excludes the flight delay. When we recall a week in Langkawi, the mind preserves the precise gradient of the sunset over the Andaman Sea; it deletes the forty-eight minutes spent arguing with a rental car agent about a missing spare tire or the grit of sand that remained in the hotel bedsheets for three nights.

We do not experience the past as a chronological sequence; we experience it as a highlight reel. This neurological efficiency is a survival mechanism for the soul, but it is a catastrophe for the spreadsheet.

It is the act of projecting a future based on a version of the past that never actually happened.

01

The Whiteboard Ritual

Daniel stands at the whiteboard in a glass-walled room in Kuala Lumpur, a dry-erase marker poised like a conductor’s baton. His manager, Sarah, stands with her arms crossed, her eyes tracking the rough rectangles he is drawing to represent data sources. They are discussing the new sales dashboard.

“How long to get the schema mapped and the first draft of the visuals?”

– Sarah asks.

Daniel pauses. He mentally scans the task. He sees the SQL joins; he sees the DAX measures for Year-to-Date growth; he sees the final publishing to the workspace.

Sarah nods. “Two days. Let’s aim for Wednesday morning.”

Both of them are lying, though neither of them knows it. They are both looking at a “clean” version of the task-a platonic ideal of work where the data is clean, the server is responsive, and no one interrupts with a high-priority “quick question” about a different report.

They have both forgotten that the last time they did this exact task, it took nine days. They did not record those nine days as a failure of estimation; they recorded them as two days of “real work” plagued by seven days of “annoyances.” Because the annoyances do not feel like the work, they are evicted from the memory of the work.

Effort is the calories burned while the gears are turning. It does not account for the time the machine spends idling in the cold, waiting for a key.

The Anatomy of a Blur

Last quarter, Daniel spent three days waiting for the database administrator to grant him read-access to the new sales tables. He spent another two days rebuilding the semantic model because the initial requirements from the marketing team were as vague as a Rorschach test. Finally, he spent a full afternoon troubleshooting a circular dependency in his DAX code that only appeared because he was trying to work too fast to meet a deadline that was based on a two-day estimate.

In his memory, that week is a blur of frustration that he labels “administrative overhead.” When Sarah asks for a new estimate, Daniel’s brain pulls up the file for “Building a Dashboard” and finds only the forty-eight hours where he was actually writing code and designing layouts.

The “administrative overhead” is stored in a different drawer, one labeled “Things That Shouldn’t Have Happened.” Because they shouldn’t have happened, he assumes they won’t happen again. To plan without them is like a pilot planning a flight and assuming there will be no wind.

I recently hung up on my boss by accident. It was one of those clumsy moments where you try to adjust your headset, and your thumb finds the exact millimeter of plastic that terminates a connection. For three minutes, I sat in the silence of my room, staring at the phone.

In my memory of that day, I will remember the productive conversation we had before the cutoff. I will likely delete the three minutes of paralyzed staring and the subsequent five minutes of drafting an apologetic text that sounded slightly too desperate. If someone asks me how long that call took, I will say “twenty minutes,” not “twenty-eight.” We are constantly shaving the edges off our reality to make it fit a more pleasant narrative of competence.

In the world of data analytics, this “shaving of edges” leads to a compounding debt. When a two-day estimate turns into a nine-day delivery, the analyst feels a sense of personal failure. The manager feels a sense of betrayed trust. The organization feels a sense of unpredictability. Yet, the next time a dashboard is requested, they will stand at the same whiteboard and agree on “two days” again. They are trapped in a loop of optimistic amnesia.

Converting “Annoyances” into “Steps”

This is why structured training and standardized credentials matter more than most people realize. They aren’t just about learning where to click; they are about reducing the surface area of the “unremembered” friction.

When a team undergoes

power bi certification,

they aren’t just gaining a badge for their LinkedIn profiles. They are adopting a shared language and a standardized workflow that converts “annoyances” into “steps.”

If Daniel knows how to properly prepare data in Power Query using a repeatable pattern, the time spent “fixing the messy data” becomes a predictable three-hour block rather than a nebulous two-day nightmare.

If the organization understands the governance of Power BI workspaces, the wait for permissions becomes a standard ticket rather than a week-long chase through the corporate hierarchy. Professionalization is the process of making the invisible work visible so it can finally be accounted for in the schedule.

Trainocate Malaysia sees this play out across South East Asia. In Kuala Lumpur and Penang, analysts are being sent to classrooms not because they don’t know how to use a computer, but because their current “self-taught” methods are magnets for unrecorded friction. A self-taught analyst might spend four hours googling a DAX formula that a trained professional can write in four minutes.

To the self-taught analyst, those four hours felt like “the struggle of learning,” so they don’t count it in their next estimate. They think, “Now that I know it, it will be fast.” But they don’t account for the next thing they won’t know.

The official Microsoft learning path for the Power BI Data Analyst Associate is designed to replace this ad-hoc struggle with a governed process. It moves the work from the realm of “individual heroism”-where Daniel tries to save the day through sheer force of will-to the realm of “systemic reliability.”

There is a certain categorical weight to a three-day training program. It is a confession that the tool is complex enough to require dedicated study. It is an acknowledgement that “just winging it” is the most expensive way to operate.

When a team in Singapore or Vietnam adopts the same standards as a team in Malaysia, the regional standardization reduces the “noise” of collaboration. Everyone is using the same semantic modeling patterns. Everyone is following the same security protocols. The “ghost days” begin to dissipate because the path from raw data to a published report has been paved.

We must stop blaming “optimism” for our bad estimates. We are not being too hopeful; we are being too selective. We treat our past self as a high-performance athlete who only ever ran on a perfect track, ignoring the fact that our past self spent half the race tying their shoelaces and the other half lost in the woods.

If you look at last quarter’s calendar, really look at it, you will see the gaps. The Wednesday where nothing was pushed to production. The Thursday spent in “emergency meetings” about a broken refresh. These are not interruptions to the work. They are the texture of the work.

Until we begin to include the “waiting, chasing, and rebuilding” as core components of the task, we will continue to disappoint ourselves. We will continue to stand at whiteboards and nod at numbers that have no basis in reality. We will continue to feel like we are falling behind a schedule that was never possible to begin with.

Daniel eventually finished the dashboard. It took eleven days, not nine, because this time the sales lead decided they wanted the colors changed to a specific shade of teal that matched a PowerPoint deck they had seen three years ago.

When Sarah asked why it was late, Daniel talked about the teal. He didn’t talk about the three days he spent fixing a broken data relationship that he should have caught in the first hour if he had followed a standard modeling framework.

The Next Request

Next month, there will be another request. There will be another whiteboard session. Daniel will look at the marker in his hand, and Sarah will look at the rectangles on the board.

“How long for this one, Daniel?”

Daniel will feel the familiar tug of his edited memory. He will see the clean version of the code. He will see the successful refresh. He will forget the teal, and he will forget the circular dependencies.

“Two days,” he will say.

And the cycle will begin again, fueled by the beautiful, treacherous efficiency of a human brain that refuses to remember how much of life is spent just waiting for the world to catch up.