UAE / Living
UAE Codes Names Three Banking AI Winners, With Staff Learning and Workplace Practice in Focus
Newly reported results from UAE Codes 2026 put personalised learning, professional practice and difficult workplace conversations at the centre of a banking hackathon. The UAE AI Office and Emirates NBD’s 3 November account describes 100 Emirati participants; the bank’s event agenda places the two-day activity on 27–28 October.
Three projects, three different workplace needs
WAM’s 3 November report names Project Ready as the first-place platform for personalised learning and career development. Career Lab, which enables practice of professional scenarios, placed second; Mashoura, designed to help employees navigate challenging conversations, placed third. The participants came from Emirates NBD Group and other regional banks and worked in cross-functional teams. These details make the result more specific than a general celebration of coding. The selected problems concern how people prepare for work and communicate within it. The announcement describes the projects’ purposes and competition positions, not independently measured improvements in employee performance or confirmed rollout across banks.
The dates separate the event from its reporting
The bank’s official agenda lists sessions on Tuesday 27 October and Wednesday 28 October 2026. It moves from introductions, data and AI discussion into build sprints, demonstration preparation and judging. The outcomes were reported on 3 November. Maintaining that sequence avoids telling readers that a completed two-day event began on the date its results appeared in the news. The agenda is also a planning document, with some entries marked provisional. Its team-planning figures should not be substituted for the reported attendance count. For this article, the news is the newly published outcome, with the earlier agenda used to explain the activity’s structure.
Personalisation has to explain its reasoning
Project Ready’s learning focus raises a practical question: what makes one recommendation appropriate for a particular employee? Our analysis is that useful personalisation connects an identified task, an evidenced skills gap and a learning opportunity. Simply generating a longer list of courses can increase work without improving direction. A staff member should be able to understand why a resource was suggested and correct a mistaken assumption about their experience. That matters particularly when learning feeds into a career conversation. The announcement does not establish that the winning platform makes promotion decisions, and it would be misleading to attach such a role to it.
Practice creates value when feedback is usable
Career Lab’s scenario-based approach has a different mechanism. Rehearsal can give an employee a place to attempt a response before facing a real interaction. The quality of the feedback then becomes more important than the fluency of the simulation. A useful exercise identifies what the learner did, what could be improved and which policy or professional expectation informs the feedback. That is an analytical description of effective practice, not a claim about features already verified in Career Lab. In a bank, examples should also reflect the actual work: a polished conversation that teaches the wrong escalation route would be less useful than a simpler exercise with accurate boundaries.
Difficult conversations cannot be reduced to a perfect script
Mashoura’s workplace-conversation focus is distinct from customer-service automation. An employee might need help structuring a concern, clarifying a misunderstanding or preparing a respectful question. A tool can offer possible wording while leaving responsibility with the people involved. Our view is that the valuable design problem is preserving context: who is speaking, what is uncertain and which issue needs a human decision. A generated script should not be treated as an official HR ruling or evidence about another person’s intentions. Nothing in the announcement establishes those powers. Clear boundaries can make conversational assistance more useful precisely because it does not pretend to resolve every relationship problem.
Cross-functional work can expose missing assumptions
The reported team format brings people with different responsibilities into one build process. A technically convenient idea can look different to someone who understands a workflow, a control or the question an employee actually asks. That exchange is one reason a short hackathon can be educational even before any product is deployed. The learning opportunity is not only writing code; it is discovering which assumptions need to be clarified. A participant who can explain why a proposal should be narrowed has made a useful contribution. The article does not infer a qualification, job placement or certification from attendance. Those outcomes would require separate evidence and clearly stated conditions.
The evidence pack matters after the demonstration
The bank’s agenda includes work on architecture, data logic, demonstration preparation and a responsible-AI checklist. Those references show a programme interested in more than an attractive final presentation, although the agenda alone cannot prove each control was implemented in every project. For a team continuing development, a concise record of inputs, test cases, known limitations and review responsibilities would make the prototype easier to assess. Use examples that can legitimately be shared; confidential workplace records are not automatically suitable demonstration material. That is our suggested continuation discipline, not a newly announced bank rule or a claim that participants mishandled information.
What the reported result contributes
The immediate result is a named set of winning projects and a documented learning exercise involving Emirati banking professionals. Emirates NBD’s Eman Abdulrazzaq, its group chief operating and human resources officer, presents the initiative as investment in people who can develop and apply AI, rather than only use it. The distinctive story is the choice of employee development and communication problems, not an unsupported claim that banking has been transformed in two days. Follow-up reporting can examine whether teams continue testing and whether staff find the tools useful. For now, recognising the specific ideas and the limits of the published evidence gives the results their proper scale.
Gabriel Nicolaev – CyGuru