Most HR managers and business owners agree that developing employees is important. In practice, however, it is one of the first things that gets deprioritised when the workload picks up. Development conversations get pushed to "when things settle down" — and things rarely do.
This two-part series examines the most significant obstacles organisations face when trying to implement effective employee development plans. Part 1 focuses on two challenges that tend to surface earliest and most visibly: the bandwidth problem for managers, and the participation problem caused by employee stress and overload.
Understanding why these challenges exist — and where they specifically show up in Singapore's work environment — is the starting point for doing something meaningful about them.
Challenge 1: Managers Do Not Have Enough Time
Here is a figure that should give any HR leader pause: research suggests that managers spend between 40% and 87% of their weekly working hours on communications and administrative tasks — emails, meetings, status updates, approvals, and coordination. That leaves a remarkably small window for the work that actually develops people: one-on-ones with meaningful substance, coaching conversations, identifying growth opportunities, and following through on development commitments.
The result is not that managers do not care about their people's development. Most do. The result is that development conversations become shallow, infrequent, or largely reactive — happening only when a performance issue forces the issue, or during the annual appraisal cycle when both parties are going through the motions.
Why This Hits Singapore SMEs Especially Hard
In larger organisations, managers are often purely focused on managing. In Singapore's SME landscape, which makes up over 99% of all enterprises here, that separation rarely exists. Managers are frequently "player-coaches" — they carry a full individual contributor workload while also being responsible for a team. A sales manager who is also the top-performing salesperson. A finance manager who is also doing the accounts. An operations manager who is also handling client escalations.
For these individuals, carving out time for structured development conversations is genuinely difficult, not just a matter of prioritisation. They are stretched across two roles simultaneously, and the team management side — including development — tends to lose out to the work that has the most immediate urgency.
What This Looks Like in Practice
When managers are too stretched to drive development properly, a few patterns emerge:
- Development plans get created during appraisal season and then quietly ignored for the rest of the year
- Coaching conversations become operational check-ins — focused on what needs to get done this week rather than where the employee is heading over the next year
- High-potential employees, who need the most investment, receive the least attention because they are low-maintenance
- Employees who need performance support receive reactive feedback instead of structured guidance with clear milestones
Practical Ways to Address This
The goal is not to eliminate the time constraint — that is rarely possible — but to make development conversations happen within the time that does exist.
- Separate development from performance reviews. When development conversations only happen during appraisals, they get loaded with too many competing agendas — ratings, salary discussions, past performance. A lighter, separate touchpoint focused purely on growth is far more productive, even if it is only 30 minutes per quarter.
- Give managers templates and prompts. A blank page is harder to fill than a structured question. Providing managers with a simple framework — "What is this person good at? What do they want to develop? What one thing would make the biggest difference?" — lowers the barrier to having a meaningful conversation.
- Move accountability upward. If senior leadership treats development conversations as optional, managers will too. When development is tracked, reported on, and discussed in leadership meetings, it signals that the organisation treats it as real work — not extra work.
- Use your HRMS to reduce administrative load. Every hour saved on payroll processing, leave approvals, and manual reporting is an hour a manager can redirect to their team. Automating administrative HR tasks does not directly solve the development problem, but it creates the breathing room for managers to actually show up for their people.
Challenge 2: Employees Are Too Stressed to Participate Meaningfully
The second challenge sits on the other side of the equation. Even when managers find the time to invest in development, employees may not have the capacity to absorb it. Research consistently shows that around 94% of employees report experiencing workplace stress. Stress is not just an abstract HR concern — it has a direct, measurable impact on an employee's ability to engage with learning, retain new information, and apply new skills back on the job.
When someone is running on empty — managing a heavy workload, dealing with unclear expectations, or anxious about job security — asking them to take on development activities feels like adding to the pile, not investing in their future. The response is often compliance without engagement: they attend the training, tick the box, and go back to firefighting.
The Singapore Working Culture Context
Singapore workers consistently rank among the most overworked in Asia. MOM's Labour Force surveys show that a significant proportion of full-time employees here regularly work beyond contractual hours. The culture of long hours is deeply embedded in many industries — especially in finance, logistics, F&B, and retail — and is often tied to a sense of what it means to be a committed, hardworking employee.
In this context, development activities — particularly those scheduled outside regular working hours, or added on top of existing workloads — face real resistance, even if employees genuinely want to grow. They are not unwilling. They are stretched.
There is also the perception issue. In some workplace cultures here, taking time for training or development can feel like a signal that you are "not busy enough" — the opposite of what many employees want to project to their managers and peers.
Why This Undermines Development Plans
A development plan that looks good on paper collapses in practice when employees do not have the mental space to engage with it properly. Specific failure patterns include:
- Training sessions that employees attend physically but are mentally elsewhere — thinking about the inbox they left behind
- Development goals that employees agreed to but privately have no intention of pursuing because they cannot see when they would find the time
- Learning activities that get indefinitely rescheduled as operational demands take precedence
- Employees who are disengaged enough to go through the motions of a development conversation without any real commitment to what is discussed
Practical Ways to Address This
Reducing stress entirely is not within any single employer's control. But there are practical adjustments that make development more accessible to employees who are operating under pressure.
- Integrate development into existing work. Job rotation, stretch assignments, mentoring, and cross-functional projects build skills without requiring separate time allocations. When development is part of the job rather than in addition to it, participation improves significantly.
- Protect time for learning explicitly. If learning time is not protected in the schedule, it will not happen. Blocking calendar time — even one hour per fortnight — signals that the organisation means it and removes the decision fatigue of employees trying to find a slot on their own.
- Keep individual development goals focused and realistic. A plan with three specific goals is more likely to be followed through than one with eight ambitious targets. Fewer, better goals reduce the feeling of overwhelm and increase the likelihood that real progress will be made.
- Address the workload question directly. If a key reason employees cannot engage with development is that they are genuinely overloaded, the answer is not better development planning — it is a workload conversation. Development initiatives built on top of an unsustainable pace will always struggle to take hold.
- Make it normal to develop during work hours. Normalising the idea that attending a training session, having a coaching conversation, or working on a development goal is legitimate work time — not something extra — matters culturally. Leadership needs to model this visibly.
Looking Ahead
Manager bandwidth and employee stress are the two most immediate bottlenecks in employee development planning. They are also, in some ways, the most addressable — because they are largely about how work is structured and how development is positioned within the organisation, rather than about resources or capability.
Part 2 of this series covers three additional challenges that tend to surface once the foundational pieces are in place: the effectiveness of training delivery, the difficulty of measuring impact, and the tension between what employees want to develop and what the business actually needs. These are challenges that even organisations with dedicated L&D resources regularly struggle with — and they deserve their own examination.
Read Part 2: Biggest Challenges in Employee Development Planning →