A growing business can identify a long list of people priorities in a single meeting. Managers need development, onboarding feels inconsistent, roles overlap, and employee information is difficult to trust. The list is accurate, but trying to solve everything at once can produce several unfinished initiatives and little visible improvement.

Modern office workplace with greenery

A 90 day HR and learning plan gives the organization a focused period to diagnose one important problem, test a practical response, and decide what to do next. It is a planning framework, not a promise that complex people issues can be resolved within a fixed number of days.

For a UAE business, the strongest plan connects a real operational need with clear ownership, manageable learning, and evidence that can guide the following quarter.

Choose a problem worth the attention

Start with a recurring difficulty that affects useful work. It might be slow onboarding, unclear delegation, inconsistent performance conversations, or a process that depends on the founder’s memory.

Describe the problem through a recent example. Who was involved, what happened, and what consequence followed? Avoid beginning with a solution such as buying an LMS or scheduling leadership training.

Agree why this problem takes priority. Consider its significance, frequency, the organization’s ability to influence it, and the attention available from the responsible leaders.

Keep other needs visible without adding them all to the first plan. Focus is not a claim that the remaining issues do not matter. It is a decision to create enough capacity to learn from one intervention before expanding the work.

Days 1 to 15: establish a usable picture

Gather evidence from the people involved and from relevant records. Trace the workflow, review the instructions, and ask where decisions become unclear.

Use a small, representative set of examples rather than collecting information without a question. The evidence should help distinguish a capability gap from a process, capacity, or authority problem.

Record the starting point using definitions the team can maintain. If the concern is slow onboarding, specify the role and the useful task you are measuring. If the concern is approvals, define when the request is complete and when the decision is made.

State uncertainties openly. The first stage may reveal that records are incomplete or that teams interpret the same measure differently. Resolving those definitions can be a valuable part of the work rather than an inconvenience to hide.

Days 16 to 30: agree the response and ownership

Use the findings to choose a proportionate intervention. The response may involve clearer responsibilities, a revised instruction, a manager practice session, or a combination.

Name the sponsor, the operational owner, and the people responsible for learning and measurement. Explain who can make decisions when the pilot reveals a problem.

Define the intended result. What should people be able to do differently, and what evidence would show that the change is useful? Keep the objective close enough to the intervention to examine realistically.

Agree boundaries. State what the first cycle will not attempt, which dependencies must be resolved, and what would make the team pause or change direction. A clear scope helps protect the plan from becoming a container for every related request.

Build a short action record

Keep the working plan simple enough to use. For each action, record the owner, expected output, due date, dependency, and review evidence.

A useful action might be to define the information required for a complete request and test it with two managers. A vague action such as improve accountability is difficult to complete or assess.

Include the commitments made by leaders. If employees need time to practise, record who will arrange coverage. If the sponsor must clarify authority, make that decision visible in the plan.

Review the action record briefly and regularly. The purpose is to identify obstacles and make decisions, not to create another reporting burden. An action that repeatedly slips may need a change in scope or resources rather than another reminder.

Days 31 to 45: prepare the learning and the work

Create the material and support needed for the pilot. This may include a task guide, a revised workflow, a practice scenario, or a manager conversation structure.

Test whether the intended users understand it. Ask them to explain or demonstrate the task rather than simply confirm that the document looks clear.

Resolve access and practical arrangements. A learning activity needs a place in the working schedule, and a revised process needs the right information and decision owner available.

UmmeSyed Advisory can be relevant to the diagnosis and operating design. UmmeSyed Learning Academy may be relevant to the capability element. The value of combining them depends on the evidence; the business should not assume that every plan requires both or a large programme.

Days 46 to 60: run a bounded pilot

Choose a group or workflow that can provide useful evidence without exposing the whole business to an untested approach. Include realistic conditions and likely exceptions.

Explain the pilot’s purpose to participants. They should know what is changing, what support is available, and how to report a difficulty.

Observe the work and capture issues by cause. A missing skill, unclear instruction, unavailable system, and conflicting priority need different responses. Do not group all problems under low adoption.

Allow practical adjustments while keeping a record of what changed. The pilot should help the organization improve its understanding, not merely demonstrate that the original idea can be defended. A useful finding may be that the intervention needs to be smaller, clearer, or different.

Days 61 to 75: examine application

Review whether people are using the new approach and whether they can demonstrate the intended capability. Ask what has become easier and what remains difficult.

Look beyond completion. A manager may attend a delegation session but continue taking decisions back. An employee may follow a new form while still lacking information needed to complete the task.

Discuss barriers with the operational owner. Decide which require learning, which require a process change, and which need a sponsor decision.

Compare with the starting point carefully. Demand, staffing, or other changes may affect the result. Keep the evidence and limitations visible so that the organization does not attribute every improvement or setback to the pilot.

Days 76 to 90: decide what happens next

Bring the evidence together and choose whether to continue, adapt, expand, or stop the intervention. Explain the reasoning in terms of the original problem and the experience of the people using the change.

If expanding, identify the conditions that must be in place. Another team may have different access, workload, or capability needs. Reuse the learning without assuming the exact arrangement will fit everywhere.

If stopping or changing direction, record what was learned. A pilot that prevents a larger unsuitable investment can still have been useful.

Set the next review point and hand ownership into normal operations where appropriate. The improvement should not disappear when the 90 day project ends or depend indefinitely on the person who coordinated the pilot.

An illustrative plan in practice

Imagine a UAE SME where new employees take inconsistent routes to learning a routine service process. The founder repeatedly answers questions, and experienced staff provide different instructions.

The first stage compares recent onboarding experiences and traces the task. The team finds that the process itself is unclear and that no one owns the learning material.

The response assigns a process owner, creates a short demonstration, and gives new employees a supported practice task. Managers review readiness using a shared standard. The pilot then examines whether employees can complete the task with fewer avoidable questions and whether the support effort is manageable.

This plan does not need to solve every onboarding issue. It creates a coherent improvement that the business can test and use as a basis for the next decision.

Keep the measures small and useful

Choose a few indicators that relate directly to the problem. These might include the quality of completed work, time to a defined decision, repeated clarification requests, or evidence of manager behaviour.

Add a short account from participants. Numbers can show a pattern, while experience can explain why it occurred. Both need careful interpretation.

Avoid selecting measures only because they are easy to collect. Attendance is simple to count, but it may tell you little about the problem the plan is meant to address.

Use the review to ask whether the intervention is worth maintaining and what support it needs. The purpose of measurement is to guide action, not to produce a report that declares success because the calendar reached day 90.

Protect the review from becoming a presentation exercise

Ask the team to bring one example of improved work, one unresolved difficulty, and one assumption that changed. These three items can make the discussion more useful than a long account of completed activities.

Invite the operational owner to explain what they can maintain after the project ends. If the improvement depends on temporary attention or resources that will disappear, decide how to address that dependency before declaring the work complete. The closing review should leave the business with a sustainable arrangement and a clear next decision.

Make the first quarter a foundation

A focused plan gives the business a repeatable way to improve: identify a meaningful problem, examine evidence, agree ownership, test a response, and review the result.

The sequence matters because it prevents learning from becoming disconnected from work and prevents process changes from ignoring the people who must use them.

Begin with one issue that leaders and employees recognize. Give it enough attention to produce a clear decision about what works and what should happen next.

Over time, these cycles can strengthen the organization’s HR foundation and development capability. The first 90 days are valuable when they leave behind a useful improvement, a responsible owner, and a better understanding of how to make the next people decision.

Related reading: HR Advisory in the UAE: What to Fix Before Your Next Growth Stage, How to Build an L&D Strategy Around Business Priorities. To explore relevant support, visit UmmeSyed Advisory services.

Start your next 90 days with a clear people and learning priority. Contact Us