top of page

Singapore’s AI edge depends on slack, not speed

  • Writer: Zoe Wyatt
    Zoe Wyatt
  • Feb 17
  • 4 min read

Lately, I have noticed a quiet shift in how people talk about work.


Not the obvious stuff, like bigger workloads or tighter deadlines. I mean the subtler recalibration of what “reasonable” now looks like. Drafts appear in minutes. Summaries land instantly. Edits happen in real time. And without anyone formally announcing it, the expectation moves from “tomorrow” to “before lunch”.


On paper, that sounds like progress. In real life, it can feel like living inside a permanently loading screen.


I wrote about this recently for e27, because what I keep seeing in high-pressure teams is not a lack of talent or effort. It is the cognitive cost of speed without slack.


Slack, in this context, is not a messaging platform. It is the breathing room that protects judgment, quality, and the ability to do work that actually holds together.



What I mean by slack

Slack is the margin in your day where your brain can complete a thought.


It is the five minutes you do not book. The stretch of time where you are not toggling between five threads, three tabs, and a meeting that should have been an email. It is the buffer that lets you notice, “Hang on, this doesn’t make sense,” before you hit send.


This matters because most meaningful work is not produced in a single burst. It is built through attention, sequencing, checking, revising, and sometimes sitting with uncertainty long enough for the better answer to show up.


When slack disappears, quality becomes fragile. You can still produce output, often a lot of it, but it takes more effort to hold the same standard. And the risk is that people interpret the strain as personal, instead of structural.



The brain cost of constant switching

One of the most reliable findings in cognitive psychology is the switching cost. When you change tasks, performance tends to slow and error rates can rise, even when the switch feels small.


In the workplace, those switches rarely look like clean “task A” to “task B”. They look like this:

  • deep work interrupted by a ping

  • a quick reply that becomes a longer thread

  • a meeting that spawns five follow-ups

  • returning to the original task with the uneasy feeling that you have lost the plot


Research on interruptions shows something else that is important. People often compensate by working faster, but that speed can come with higher stress, frustration, and time pressure.


So when teams say, “We’re moving faster than ever,” it is worth asking: faster at what, and at what cost?


Why this is showing up now

Tools are improving. Workflows are compressing. And many organisations are pushing for efficiency, not because they are cruel, but because the market rewards it.


At the same time, large-scale data on modern work has been pointing to fragmentation and overload as a defining feature of the current era.


So yes, AI can help. It can reduce friction and remove some busywork. But it can also quietly raise the baseline speed of everything around it, including expectations, responsiveness, and the number of parallel demands placed on a human brain.


If you want sustainable performance, the “AI era” question is not only “What can we automate?” It is also “What do we protect so people can think?”


Slack as quality control

When I work with clients in high-demand roles, the pattern is familiar: the day feels full, the message stream is relentless, and the tasks that require sustained thinking get pushed to the edges.


The most helpful reframe is this: slack is not a wellness perk. It is quality control.

It is what prevents avoidable rework.It is what keeps decisions coherent across multiple stakeholders. It is what allows people to spot risk early rather than apologise late.


If you remove slack, you do not get rid of the need for recovery. You just push it downstream, often into mistakes, delays, irritability, insomnia, and that particular flavour of burnout where someone is “busy all day” but feels like nothing is actually finished.


Practical ways to rebuild slack in real teams

This is the part people always ask for, because nobody wants an article that ends with “be less stressed” and a deep sigh.

A few practical options that do not require a total workflow redesign:

  • Protect one block of time per day for uninterrupted work, even 45 minutes

  • Batch communication windows rather than responding continuously

  • Set expectations for response times that match the real urgency

  • Use AI to draft, but schedule human time to review, challenge, and refine

  • Build buffer between meetings, even 5 to 10 minutes

  • Agree on what deserves a meeting and what can be handled asynchronously


None of this is revolutionary. The point is consistency. Slack is not one big holiday. It is small, repeated, protected pockets of room for your nervous system and your cognition to do their job.


Closing thought

If you want a durable edge, individual brilliance is not enough. The system has to support attention.

In a faster workplace, slack becomes a competitive advantage because it protects judgment, reduces rework, and lets people produce thinking, not just output.


If this topic resonates, the full article is on e27:

 
 
 
bottom of page