Serious.Games
The Training Budget Portal
ManagementFormationFree

The Training Budget Portal

Decide, finance, and defend a training portfolio with imperfect data.

Duration · 90–120 min
Participants · 6–20
Level · Intermediate

In short. The Training Budget Portal is a serious game (management) for 6–20 participants, lasting 90–120 min. Created by serious-games.com. Use it for: prise de décision, priorisation, alignement.

Card by serious-games.com, updated 22 November 2026. Original game by serious-games.com.

Participants take on the role of an L&D committee tasked with allocating a limited budget to competing training requests. Each team analyses request sheets, learning indicators, and strategic objectives, then builds a well-argued portfolio. Events reveal new data and force teams to arbitrate, cut, or strengthen certain initiatives. The game fosters decision-making, prioritisation, and communication in the face of demanding stakeholders.

Walkthrough

  1. 1

    Game Framework and Decision Criteria

    12 min

    The facilitator welcomes the group, forms teams of 3 to 5, and announces: "You are the committee that opens or closes the training budget portal. Your role is to fund what creates the most value with incomplete data." They present the 4 criteria rated from 0 to 3: strategic alignment, data-driven evidence, expected impact, feasibility. Participants receive the scoring grid and ask their questions. This step establishes a common language to avoid purely intuitive decisions.

    Tip : Display the criteria on the wall or in a shared document. Emphasise that a good choice can be defendable even if the data is not perfect.

  2. 2

    Reading Requests and Initial Sorting

    18 min

    The facilitator distributes 10 Training Request cards and 10 associated Data cards to each team. They say: "You have 20 budget tokens, each request costs between 2 and 7 tokens, and you cannot fund everything. Your first objective is to separate promising, risky, and to-be-rejected requests." Teams read, match data to requests, and sort the cards into three piles. The goal is to quickly surface hypotheses, areas of uncertainty, and implicit preferences.

    Tip : Prepare cards with generic titles: compliance, managerial skills development, internal tool, client relations, safety, onboarding, quality, innovation, etc.

  3. 3

    Numerical Scoring and Initial Portfolio

    22 min

    The facilitator starts the timer and reminds: "Score each request from 0 to 3 on the 4 criteria, then calculate Total Score = sum of criteria minus cost in tokens." Teams fill in their grid and choose a portfolio whose total cost does not exceed 20 tokens. They must fund at least 3 requests and at most 6, then keep 0 to 4 tokens in reserve if they wish. This constraint forces prioritisation, comparison of relative value, and makes trade-offs visible.

    Tip : If a team gets stuck, ask: "Which request would you be able to defend in front of a sceptical director?" instead of giving the answer.

  4. 4

    Transition to the Budget Portal

    15 min

    Each team has 3 minutes to present their portfolio. The facilitator plays the role of the budget portal and asks: "What decision have you made, what data supports it, and what risk are you accepting?" Other participants each award 1 Trust token to the team whose argumentation seems the strongest, without voting for themselves. The Trust tokens do not yet change the budget, but they reveal perceived credibility. This step works on clarity of communication and defending a data-driven decision.

    Tip : Time strictly. An average decision well explained should be able to beat a brilliant but incomprehensible decision.

  5. 5

    Data Shock and Reallocation

    18 min

    The facilitator draws 3 Event cards visible to all: new strategic priority, budget cut, contradictory data, regulatory urgency, departure of a sponsor, or pilot results. They announce: "The context has changed: remove 4 budget tokens, then you can abandon, reduce, or replace requests. A reduced request costs 1 token less but loses 2 points of score." Teams have 12 minutes to adapt their portfolio and note the reasons for the changes. This sequence simulates the reality of L&D decisions where data evolves after the initial commitment.

    Tip : Choose events that create real tension. Avoid purely punitive events: they should force a trade-off, not make the game impossible.

  6. 6

    Stakeholder Advisory

    15 min

    The facilitator designates, for each presentation, two participants from other teams as stakeholders: finance, business, HR, field manager, or learner. They say: "You have 4 minutes to defend your revised portfolio, followed by 2 minutes of tough questions." Teams must cite at least two data points, one assumed compromise, and one follow-up indicator post-deployment. Stakeholders raise objections, then award up to 3 points for Robustness. This step trains anticipation of objections and translating data into an acceptable decision.

    Tip : Give stakeholders role cards with a simple concern: cost, timeline, risk, fairness, adoption, proof of impact.

  7. 7

    Score Calculation and Quick Learnings

    10 min

    The facilitator calculates the final score: total scores of funded requests, minus unused budget tokens, plus received Trust tokens, plus Robustness points. They announce: "The score does not designate the truth; it measures the coherence between data, strategy, budget, and narrative." Teams compare their portfolios and identify one decision they would change. The aim is to transition from the playful result to transferable learnings. The facilitator then prepares the debrief by noting the most significant trade-offs.

    Tip : Do not let the ranking overshadow the learning. Value a team that changed their mind based on relevant data.

Variants

  • Short version 60 minutes: use 6 requests instead of 10, remove the first transition to the portal, and draw only 2 Event cards.
  • Expert version: add a column for 'data quality' rated from 0 to 2. A request with low-quality data cannot score more than 2 in data-driven evidence.
  • Cooperative version: all teams represent different departments and must collaboratively build a final unique portfolio of 30 tokens after their separate work.
  • Remote version: use a collaborative board with digital cards, budget tokens as icons, and virtual rooms by team. Presentations are done in plenary with voting via polls or reactions.

Debrief guide

  • What criteria truly influenced your decisions: data, cost, strategy, risks, or ease of implementation?
  • At what point did you make an assumption due to insufficient data, and how did you make it explicit?
  • Which training request seemed appealing at first but lost credibility after scoring or an event?
  • How did your argumentation evolve between the first budget portal and the stakeholder advisory?
  • What missing data would have changed your decision, and how could you obtain it in real life?
  • What follow-up indicator would you choose to verify that a training investment produces the expected effect?
  • What do you take away about how to say no to a training request without demotivating the requester?

Facilitator reviews

No review yet. Have you run this game? Your feedback will help the next facilitators.

Same objectives or same category, to vary or follow up.