A new hire becomes productive faster when they can do real work before they have memorised every screen, menu and internal procedure. Most onboarding struggles not from a lack of goodwill but from load: a long list of systems to learn, procedures that live in people's heads, access that arrives late and a fear of breaking something. The fix starts with basics any company can apply: a checklist for each role, a buddy, written procedures, a safe place to practise and the right permissions from the first day. When your systems also understand plain language, a new team member can ask for what they need in Arabic or English instead of hunting through screens, while permissions and approvals keep any mistake small. Below we cover what research says about onboarding and time to productivity, what early turnover costs, a practical first week and where Amrak fits in.
How long does it take a new hire to become fully productive?
Longer than most plans allow. Gallup's experience is that new employees typically take around 12 months to reach their peak performance potential, yet many onboarding programmes end after a few days of paperwork and introductions. In the same Gallup analysis, only 12% of U.S. employees said their company does a good job of onboarding, and only 29% of new hires said they felt fully prepared and supported to excel in their role afterwards.
These figures come from the United States, but the pattern will be familiar to many managers in Egypt and the Gulf: a laptop on the first day, a stream of logins over the following week and a new hire who learns the systems by asking whoever sits nearest.
The aim is not to squeeze a year of learning into one week. It is to make the first week count: real tasks done safely, with help close by, so the climb to full performance starts straight away.
What does slow onboarding cost a company?
The direct cost is salary paid while the new hire cannot yet work alone, plus the time of the colleagues who answer their questions. The larger cost comes when the person leaves. Gallup estimates that the cost of replacing an individual employee can range from one-half to two times the employee's annual salary.
In the Gulf, a new hire who struggles has options. In Gallup's State of the Global Workplace 2026 report, 77% of employees in Saudi Arabia and 76% in the UAE said it is currently a good time to find a job, against a global average of 52%. A confusing first month is an easy reason to accept another offer.
There is also a quieter cost: errors. A new hire who guesses their way through an unfamiliar admin panel can publish the wrong price, message the wrong client or delete something they should not. Many companies respond by withholding access for weeks, which keeps the person safe but idle.
Why is learning the company's systems the hardest part?
Because there are so many of them. Okta's Businesses at Work 2025 report, based on anonymised data from thousands of its customers, found that the average number of apps each company uses has reached 101, and its regional figures put the average for Europe, the Middle East and Africa at 74. A new hire will not touch all of them, but even a sales coordinator may need the CRM, the ERP, the website admin, a dashboard, a shared drive and the team chat in the first week.
Each system has its own screens, names and habits, and each company adds its own rules on top: which fields are required, who approves a discount, how a purchase order is raised, which client gets which price list. Much of this lives only in experienced people's heads. We looked at the time experienced staff lose clicking through these screens in our article on the hidden time cost of dashboard clicks. For a new hire the cost is higher, because every click is also a question.
What should a new hire's first week look like?
A good first week mixes access, learning and real work, with a clear owner for each part.
| Day | Focus | By the end of the day |
|---|---|---|
| Day 1 | Welcome, accounts ready, meet the manager and the buddy | Can sign in to every system the role needs, with the right access |
| Day 2 | Walk through the role checklist and the main procedures | Knows the core tasks of the role and where each procedure is written |
| Day 3 | Practise in a sandbox or on test records | Has completed each core task once, without risk |
| Day 4 | First real tasks, reviewed by the buddy | Has delivered real work, checked by someone experienced |
| Day 5 | Review with the manager: what was hard, what was missing | Has a plan for the coming weeks, and gaps in the procedures are noted |
Write the plan down once and reuse it for every hire in the same role. The first time you run it, note every question the new hire asks. Most of them point to a missing procedure or a confusing screen, and fixing those helps the next person too.
Which onboarding steps work in any company?
- A checklist for each role. List the systems, tasks and people a role needs in its first month, in the order they are needed. A checklist turns onboarding from a favour someone does into a process someone owns.
- A buddy and an involved manager. A buddy answers the small questions a new hire is embarrassed to ask the manager. The manager still matters most: Gallup found that when the manager takes an active role in onboarding, employees are 3.4 times as likely to feel the process was successful.
- Written procedures. Short, task-based notes such as "how to raise a purchase order" or "how to add a product to the website", stored where people actually look for them. One page per task is better than one long manual nobody opens.
- A safe sandbox. A test environment, test records or a demo account where the new hire can try every core task without real consequences. Confidence comes from doing, not from watching.
- Permissions by role from day one. Access should be ready before the first morning, set by role and not negotiated person by person. More on this below.
- Training on the tools, including AI. If your team uses AI tools, teach them as part of onboarding, not as an afterthought. Our practical AI literacy training plan shows how to structure it.
How should you set permissions for a new hire?
Most companies get this wrong in one of two ways: full access on the first day because it is easier, or almost none for weeks because it feels safer. Both are costly. A better pattern:
- Define access by role, not by person, so every new sales coordinator starts with the same set.
- Give view access broadly and edit access narrowly. A new hire can read product data long before they can change prices.
- Require approval for sensitive actions, such as messages to clients, deletions and price changes, whoever does them.
- Keep a log of who changed what, so mistakes can be traced and fixed without blame.
- Review access at the end of probation and widen it as confidence grows.
The same principles apply when AI is involved, as we explain in AI governance for SMBs: permissions, data and approvals.
How does Amrak help new staff work from week one?
Amrak is HBS Group's AI assistant that works inside a company's existing systems. It can connect to website and content publishing, dashboards and analytics, the CRM, the ERP, calendar and scheduling, the client portal and design tools. Staff type a request in plain Arabic or English and Amrak carries it out through a connector HBS builds for that company's own sections and rules. For a new hire, that changes the first weeks in four ways:
- Ask instead of learning every screen. A new marketing coordinator can ask Amrak to publish a post on a set date with an image. A new operations hire can ask it to flag low stock and draft a purchase order. Neither has to learn where every option lives before getting work done.
- Permissions limit what they can reach. Amrak checks the person's permissions before it prepares anything. A new hire who may edit products but not prices cannot change a price through Amrak.
- Sensitive actions wait for approval. Messages to clients, deleting anything and changing prices always wait for approval, so a beginner's mistake is caught before it reaches a client.
- Logs let managers review. Every action records who asked, when and what changed. A manager can look back over a new hire's first weeks, or simply ask Amrak to summarise yesterday's work.
There is nothing to replace: Amrak works with the systems you already have, with no data migration, as we explain in adding AI without replacing your ERP. The commands are agreed with you in a command map before the build, and each project includes testing with your team, then handover and training. You can see how a request moves through Amrak's five steps in how Amrak works, browse ready-made commands by department and read how approvals and logs protect you in letting AI act safely in your systems. Website and content roles have their own guides: updating your website without a developer and content operations at scale.
Amrak does not replace your procedures or your buddy. A new hire still needs to know why a discount needs approval and who the key clients are. What changes is the mechanical part: they no longer have to memorise menus before they can contribute.
How do you know your onboarding is working?
Pick a few measures and track them for every new hire:
- Time to first independent task: the day the new hire completes a core task without help.
- Questions per week: they should fall steadily. A question that keeps coming back points to a missing procedure.
- Errors caught in review or approval during the first month, and what caused them.
- Self-rated readiness at the end of the first week and the first month.
- Retention after probation: whether the person is still with you, and why if not.
Compare these before and after any change to your onboarding, including new tools, as we describe in how to measure AI ROI.
If your new hires spend their first weeks learning screens instead of doing the job, book a free discovery session with our team. We will map the systems your staff use and show what a new team member could ask for in plain Arabic or English, with permissions and approvals in place. See how Amrak works and book your session.
