When a project ends before the next assignment begins, the discussion about people can quickly divide into two positions. One treats employees without an immediate project allocation as an avoidable cost. The other treats the loss of experience as so serious that retention should be beyond question. I find neither position sufficient. Management needs to make a specific decision about a particular group, a particular interval and a business whose next commitments may still be uncertain.
The value of experience is not imaginary. People may understand the company’s decisions, know how its teams work together and carry knowledge that takes time to develop. But naming those benefits does not remove the need to explain the expenditure. A people proposal becomes stronger when it can describe the capability being preserved and the alternatives considered. It should be open to financial challenge without reducing every question to a short-term saving.
Describe what is being preserved
In our fictional 2023 decision, 38 experienced employees faced a gap between major assignments. Several potential projects could use their capability, but the dates were not sufficiently firm to promise specific postings. We examined the group’s experience, the work available during the interval and the consequences of losing particular combinations of knowledge. That was more useful than presenting the population as a single undifferentiated headcount or assuming every employee had the same likely next role.
The proposal needed to distinguish committed work from a plausible opportunity. A positive pipeline discussion can easily become a confident employment message as it passes through an organisation. I wanted employees and finance to hear the same degree of uncertainty. We could commit to the temporary arrangement and its review date. We could describe likely uses of capability. We could not responsibly turn an unconfirmed project into a definite future posting simply because that would make the decision easier to communicate.
The alternatives also deserved a fair account. Immediate reduction might lower expenditure while creating later recruitment and continuity problems. Retaining everyone without defined work could preserve availability but weaken engagement and obscure the real cost. Partial retention, different assignments or a shorter review period might suit another situation. A serious proposal should show why the chosen approach fits the current circumstances, rather than use a general belief in people as a substitute for examining the options.
I would also separate the direct employee population from contractors and other partners. A development project can involve many people whose employment relationship sits elsewhere. Their continuity matters, but the company’s authority and obligations differ. Combining them into one impressive workforce number can conceal that distinction. The decision should identify which people the employer can assign directly and which dependencies require a commercial or operational arrangement with another organisation.
Give the interval a real working form
We funded a five-month capability pool at a cost of SGD 1.12 million. The arrangement included defined internal assignments, peer contribution and preparation for likely operating requirements. It was not an instruction to remain available and wait. Each employee needed to understand the work expected, the manager responsible and how the contribution would be assessed during a period that did not resemble a normal project posting.
Interim work should be useful in its own right. There is a risk of creating activity merely to make retained capacity appear occupied. A report that nobody needs or a training calendar without a clear purpose does not strengthen the case. I would ask the receiving manager to explain the value of the assignment and the support required. If the work is preparation for a possible project, its provisional nature should remain clear, including what happens if that project does not proceed.
The review point is equally important. It should be a genuine opportunity to reconsider the decision, not a date added to make an open-ended commitment look bounded. Management needs to know which evidence will be examined: the pipeline, the work completed, the employee’s preferences and the financial position. A changed conclusion is possible. Stating that possibility honestly is more respectful than allowing people to infer certainty from a programme name or a reassuring message.
There are individual considerations that a group proposal cannot settle. Some colleagues may prefer an available operating role; others may want a different kind of project or choose to leave. The employment arrangements need appropriate advice and private discussion. A public account can explain the categories and the support without presenting personal decisions as simple administrative outcomes. The organisation’s interest in preserving capability should not erase the fact that employees also have choices about their own next chapter.
Follow the decision to its actual outcome
At the end of our five-month period, 24 employees entered new project roles, nine moved into asset operations and five left by agreement. Those figures reconcile the original group. They do not show that the decision paid for itself through a measurable project saving, or that every person received a preferred outcome. The account is useful because it follows the employment decision to a point where the temporary categories have been resolved rather than left indefinitely in a positive programme report.
I would examine what the company learned from the interval. Did the proposed internal work prove useful? Were managers able to release and receive people as expected? Which capabilities were harder to place than the original proposal suggested? These questions can improve the next decision without assuming that the same arrangement should be repeated. Project cycles differ, and a choice that was sensible once may be unaffordable or unnecessary in another period.
For a board, the relevant question is whether management has made the investment and uncertainty visible. Directors should be able to understand why capability was retained, the cost accepted and the conditions that could change the conclusion. They need not assign individuals to projects. They should expect a coherent account that connects the people decision with the business plan and follows material consequences beyond the initial approval.
I believe an organisation can value experience while still asking difficult questions about its cost. The more specific the proposal, the less it needs to rely on sentiment. Retention between projects can preserve options that matter, but those options should be described honestly. The decision becomes credible when employees know what they are being asked to do, management knows what it has funded and the later review is prepared to report the outcome that actually occurred.