An employee can complete several courses and still feel that their career is standing still. They have more certificates, but no greater opportunity to make decisions, apply a skill, or take responsibility for meaningful work. Their manager may believe the company has invested in development. The employee may reasonably wonder what that investment was meant to change.

Human development at work means building a person’s capability, judgement, confidence, and ability to contribute. Courses can support it, but development also depends on the assignments people receive, the feedback they hear, and the space they have to practise.
For UAE employers, a practical development plan should connect the organization’s needs with the individual’s goals. Neither side should have to guess how the learning relates to work.
Define the capability before choosing the activity
Start with something the person needs to do more effectively. That might be managing a difficult client conversation, interpreting operational information, coordinating a project, or supervising a small team.
Make the goal observable. Becoming more strategic is difficult to assess. Comparing options, explaining assumptions, and recommending a course of action gives both the employee and manager a clearer target.
Discuss the situations in which the capability matters. A person may communicate confidently with colleagues yet struggle when presenting a recommendation to a senior leader. Another may understand a technical process but need help explaining it to a new employee.
This level of detail makes development more relevant. It also prevents the business from sending everyone on the same programme because a broad competency appears on an annual form. The chosen activity should follow the need, rather than the need being rewritten to justify an available course.
Have a conversation about ambition and context
Employees do not all want the same next step. Some want management responsibility. Others want deeper technical expertise, broader experience, or greater confidence in their current role. A useful conversation explores those preferences without making promises the business cannot keep.
Ask what work gives the person energy, where they feel uncertain, and what they would like to understand better. Discuss the opportunities that realistically exist in the organization and the capabilities those opportunities require.
Be careful with assumptions. Age, nationality, family circumstances, or communication style do not tell a manager what someone wants from their career. In a diverse workplace, asking directly is more respectful and more accurate than filling in the answer.
The conversation should also examine capacity. An employee carrying an unusually heavy workload may not be able to take on a substantial assignment immediately. Development becomes credible when the manager is willing to adjust work, provide support, and agree priorities.
Use work as a place to learn
A development assignment should give the employee a chance to practise something specific while contributing to a genuine need. It should stretch their capability without leaving them unsupported in a role they are not ready to perform.
Consider an illustrative Sharjah business where an experienced administrator wants to move into operations coordination. The manager might ask the employee to organize a small internal handover project, define its milestones, and report on obstacles. This provides practice in coordination and judgement without transferring responsibility for a major client delivery immediately.
Agree the boundaries. What can the employee decide? When should they seek help? Who will review the work? What would make the assignment unsafe or too demanding?
The quality of the support matters as much as the assignment itself. Giving someone extra work and calling it development can damage trust. A genuine learning opportunity includes feedback, time to reflect, and recognition of the effort involved.
Combine learning methods with a clear purpose
Different needs call for different methods. A short course may introduce a concept. A demonstration may show how a task is performed. Coaching may help someone examine their assumptions. Mentoring may provide perspective from a person with relevant experience.
The methods work best when they connect. An employee could learn a conversation structure, practise it with a colleague, use it in a real meeting, and discuss the experience with their manager. Each step has a purpose.
Avoid treating variety as a goal in itself. Adding more formats can make a programme complicated without making it more useful. Choose the simplest combination that gives the person enough understanding, practice, and support.
UmmeSyed Learning Academy provides a natural starting point for a discussion about structured learning needs. Where development is blocked by unclear roles or inconsistent opportunities, UmmeSyed Advisory may be relevant to the broader diagnosis. The individual plan should still reflect the employee’s actual work and ambitions.
Make feedback specific enough to use
Feedback helps development when it describes an observed action and its effect. Telling someone to be more confident offers little guidance. Explaining that their recommendation was clear but the supporting evidence was difficult to follow gives them something to work on.
Ask the employee to reflect first. What felt effective? Where did they hesitate? What would they try differently? Their account may reveal a misunderstanding or an obstacle the manager did not see.
Choose a manageable next step. If every conversation produces a long list of weaknesses, the employee may struggle to decide where to focus. One useful adjustment, practised repeatedly, can be more valuable than a detailed catalogue of deficiencies.
Feedback should not arrive only after failure. Notice improvement and explain what made it effective. This helps the employee repeat a good approach with intention rather than assuming the result was luck.
Protect fair access to development
Development opportunities can become uneven when they depend on visibility or informal relationships. Employees who work near senior leaders may hear about projects first. People on different shifts may miss learning sessions. Quiet employees may be overlooked despite strong work.
Make selection criteria clear. Explain why an assignment requires a particular level of readiness and what someone can do to become eligible. Invite expressions of interest where appropriate instead of relying solely on managers to nominate familiar names.
Review who receives opportunities over time. Look at role, location, work pattern, and other relevant factors without exposing unnecessary personal information. A pattern of exclusion may reveal a scheduling problem or an assumption that needs attention.
Fair access does not mean identical development for everyone. It means that differences have a defensible reason and people can understand the route available to them. A transparent process can make limited resources feel more credible.
Measure growth without turning people into scores
Development needs evidence, but no single number captures a person’s progress. Use a combination of work examples, observation, reflection, and feedback from people who have seen the relevant behaviour.
For a coordination goal, evidence might include clearer milestones, earlier escalation of delays, and more complete handovers. For a communication goal, it might include a recommendation that another person can understand and act on without repeated clarification.
Compare the evidence with the starting point and the agreed expectation. Avoid comparing employees who had very different opportunities to practise. Someone who has handled several real situations has a different evidence base from someone who has only completed a simulation.
Keep the discussion developmental. A score can support a conversation, but it should not replace one. Ask what the evidence suggests, where confidence remains limited, and what experience would help the person take the next step.
What if there is no promotion available?
A development plan should not imply that every improvement leads to an immediate title change. Organizations have limits, and misleading promises can undermine otherwise useful work.
Be honest about the difference between building capability and securing a vacancy. An employee may gain broader responsibilities, deeper expertise, or a stronger foundation for a future move even when the structure cannot support promotion today.
At the same time, do not ask people to perform a permanently larger role under the label of development without reviewing the arrangement. Responsibilities, support, recognition, and reward need to remain coherent.
Discuss progress and opportunities regularly enough that the employee does not have to infer their prospects from silence. A candid conversation may be uncomfortable, but it respects the person’s ability to make informed decisions about their career.
Give the employee a usable record of progress
Ask the employee to keep a few brief examples of work that show their development. Each example can describe the situation, the action taken, the feedback received, and what they would do differently next time. This is more useful than a long list of courses completed without context.
Review the examples together and look for patterns. The person may be applying a skill independently in familiar situations while still needing help when the task becomes more complex. That distinction helps choose the next assignment. The record should belong to a constructive development conversation, with appropriate privacy and access, rather than become an undisclosed file of judgements about the employee.
Start with one meaningful development cycle
Choose one capability, one relevant assignment, and one source of feedback. Agree when the employee will practise, what support they can expect, and when the two of you will review the experience.
Write the plan simply. The document should help the conversation rather than become the main product. If the employee cannot explain what they are practising and why it matters, the plan needs clarification.
After the first cycle, decide whether to repeat, increase the challenge, or change direction. Development is rarely a straight path. New experience can reveal interests or needs that were not visible at the start.
The employer’s role is to create a fair and useful environment for that growth. The employee brings effort, reflection, and agency. When both sides understand their part, human development becomes a practical feature of working life rather than an annual promise.
Related reading: Internal Mobility: Grow Capability Before Opening Another Vacancy, Can Employee Development Improve Retention in UAE Companies?. To explore relevant support, visit UmmeSyed Learning Academy.
Discuss a practical development path for your people. Contact Us

Comments
No comments yet — be the first to share your thoughts.