Subscribe to Our Newsletter
Get the latest updates delivered straight to your inbox.
Designing VILT for Shared Services Teams in EgyptPicture a shared services center in Cairo that has just changed how supplier payments are approved. The process owner runs a three-hour VILT session for the accounts payable team: sixty slides and a few minutes for questions at the end. Cameras stay off, and the following week the same incomplete payment requests are still being accepted, or sent back to business units without a clear reason.
The session covered the policy, but nobody handled a request. Shared services work is request work: someone in another department, branch or group company sends something incomplete, urgent, or unusual, and the team member has to check it, decide what to do, and reply in a way the requester understands. If a VILT session never puts a request in front of the team, it trains listening, not handling.
This article shows training teams and facilitators how to design VILT, or virtual instructor-led training, for shared services teams in Egypt around three elements: realistic internal request cases, breakout rooms where small groups practice handling them, and a clear output that every room delivers and the facilitator reviews.
Why Lecture-Style VILT Fails Shared Services TeamsFinance, HR, procurement and IT support teams in a shared services model are judged on accuracy, turnaround time and how often work comes back. Their daily decisions sit between a policy and a person. Is this request complete? Does it need approval, and from whom? Should it go ahead or be returned, and with what explanation?
A policy presentation answers none of these questions at the moment they arise. Even a skilled VILT presenter can only describe the rules; participants still have to turn them into decisions alone, later and under time pressure. Unlike much online training, which is built around content, VILT for these teams should start from the request, not the slide deck. A short briefing on what changed still has a place, but in a well-designed VILT session it takes minutes, and the cases take most of the time.
Build a Bank of Internal Request Cases for Each VILT SessionThe cases are the core of any VILT design for these teams, so build them from real work rather than from the policy document. Good sources inside a shared services center include:
Choose cases that are frequent, costly when mishandled or genuinely ambiguous. If several problems compete for the same session time, rank them first, using an approach such as prioritizing performance gaps before buying courses. Then write each case the way the request actually arrives: an email or ticket from a named role, with its attachments, the system status, and any time pressure. Typical examples are a supplier asking to change bank details, an urgent payment without a purchase order, or a manager requesting system access for a new joiner.
Prepare three levels for each request type: a standard case, a case with one missing element, and a borderline case that needs judgment or escalation. Replace every real name, amount, and account number with invented data, and follow your organization’s data protection requirements, because VILT materials, recordings, and chat logs often travel further than anyone expects.
Designing Breakout Rooms for VILT PracticeBreakout rooms turn a large VILT audience into small working groups, which is where request handling can actually be practiced. In a small-scale, practitioner-led study of online tutorials, Open University associate lecturer Karen Chandler found breakout rooms useful for facilitating collaborative learning and interaction. She also reported that the only significant actual barrier was the tutor’s own skill and confidence with the tool. For a VILT facilitator, the lesson is to design and rehearse the rooms, not to avoid them.
Room Size and RolesThree or four people per room works well for VILT case practice. Give each person a role that mirrors the real process, and rotate the roles with every case:
Rotating roles means every participant handles at least one request during the VILT session, and everyone experiences the requester’s side, which quickly shows why a technically correct reply can still trigger a follow-up email.
Instructions Before the Rooms OpenIn VILT, much breakout time is lost in the first two minutes, when groups are unsure what to do. Before opening the rooms, show a one-slide task card and post the same text in the chat: the case number, the roles, the output required, the time available, and where to deliver it. Ask one participant to repeat the task in their own words. Keep each round to 15 to 20 minutes, with a time warning five minutes before the rooms close.
What the VILT Facilitator Does While Rooms WorkVisit each room briefly, listen before speaking, and resist solving the case for the group. A producer or co-host can handle technical problems and move late joiners, so the facilitator can concentrate on the cases. Note any question that comes up in more than one room; it shows where the rule or the case needs clarifying and becomes material for the plenary review.
Delivering Outputs: What Every Room Hands InAn output is what makes breakout time accountable. Without one, rooms tend to discuss the case in general terms and come back with “we agreed it depends”. Define the output before the VILT session, and make it the same artifact the team produces at work:
Ask every room to deliver its output to one shared place, such as a shared document with a section per room, named by room and case. The facilitator can then put two rooms’ outputs side by side in the plenary review and ask the whole group which one the requester would prefer, and why.
Review outputs against a short checklist agreed with the process owner: the correct decision, complete information, a clear next step for the requester and a correct record in the system. In their review in Review of Educational Research, Hattie and Timperley describe feedback as one of the most powerful influences on learning and achievement, while noting that its impact can be either positive or negative. Feedback that names the missing element in a room’s reply helps; a general “good discussion” does not. For more on looking past attendance figures, see our guide to reviewing group outputs beyond attendance.
A Hypothetical Example: Supplier Data Requests in a Cairo Shared Services CenterThe following example is hypothetical and is included only to illustrate the design.
A shared services center in Cairo processes finance transactions for several companies in a regional group. After a series of rework cases, the process owner wants the accounts payable and supplier data teams to handle change requests consistently. The learning team designs a 90-minute VILT session for 16 participants.
The VILT session opens with a ten-minute briefing on the center’s updated rule: bank detail changes require a callback to a contact already on file, never to the number in the request email. Participants then work in four breakout rooms on a straightforward change request with all documents attached. Each room delivers its decision, the completed request fields, and the reply to the requester into a shared document. In the plenary, the facilitator compares two replies, and the group agrees what a complete one looks like.
The second round uses a harder case: a request that appears to come from a known supplier, sent from a slightly different email domain and marked urgent by a business unit manager. Two rooms approve it. The plenary review becomes the most useful part of the VILT session, because the process owner can show, on a concrete output, which check would have stopped the change. The session closes with a short individual task: each participant drafts the requester reply for a third case, and team leaders review a sample the following week.
Practical Points for VILT in Egyptian Shared Services TeamsLanguage on the RequestsRequests in an Egyptian shared services center may arrive in Arabic, in English, or in a mix of both, while system fields and policy documents are often in English. Write each VILT case in the language requesters actually use, keep system terms exactly as they appear on screen, and agree in advance which language the outputs should use.
Timing Around Closing and Payroll DeadlinesAvoid month-end close, payroll cut-off dates, and audit weeks. Two 90-minute VILT sessions a week apart usually work better than one long session, because participants can apply the first round at work before returning for harder cases.
Testing the VILT PlatformBefore the first live run, test breakout rooms, file sharing, and the shared output space with real participant accounts, including anyone joining from home or another site. A short rehearsal with the producer prevents most lost breakout time.
SummaryVILT for shared services teams works when it looks like the work: requests arriving, decisions being made, and replies going back to the business. Build each VILT session around a bank of internal request cases, use breakout rooms with clear roles and instructions, and ask every room to deliver an output that can be reviewed against an agreed checklist.
Start with one request type that causes rework, run one well-designed VILT session, and use the outputs to see where the rule or the team needs support. The same move from explaining to deciding underpins our guide to turning quality explanations into eLearning decisions in Egyptian factories.
Click here if you want Skillup MENA to help you.




