There is a productivity tension emerging inside Indonesian businesses.
Microsoft’s 2025 Work Trend Index found that 63% of business leaders in Indonesia believe productivity needs to increase. At the same time, 88% of the workforce—including employees and leaders—say they lack enough time or energy to complete their work.
That creates an uncomfortable management question: if organizations need more productivity, but people have less capacity to give, where should the additional performance come from?
For workforce-intensive businesses, part of the answer may lie not in asking people to do more, but in making better decisions about how existing workforce capacity is deployed.
Workforce capacity is not simply a question of how many people an organization employs. It is also a question of which capabilities are available, where they are deployed, when they are needed, and whether that deployment reflects actual business demand.
For businesses built around shifts—from manufacturing plants and retail networks to hotels and other service operations—that makes employee scheduling more than a calendar-management exercise.
It makes scheduling a workforce allocation decision.
And that requires us to reconsider where the scheduling decision should actually begin.
We May Be Starting the Scheduling Decision Too Late
Most workforce scheduling begins with a practical question:
Who should work which shift?
Managers look at the employees available, the roles that need to be covered, and the shifts that need to be filled. The objective is then to arrange those resources into a workable roster.
There is nothing inherently wrong with that question. The problem is that it may be the last question we should ask, rather than the first.
Before deciding who should work a shift, management needs to understand what created the workforce requirement in the first place:
- How much demand are we expecting?
- What workforce capacity does that demand require?
- Which roles do we need, and when?
Consider two locations that each schedule 20 people for Monday. One expects normal demand, while the other expects demand to rise significantly.
Both locations may successfully fill every position on the roster. From an administrative perspective, both schedules are complete.
But they cannot automatically be considered equally well planned.
One may have exactly the workforce capacity it needs. The other may be understaffed despite having a completely filled roster—or may be carrying more labor capacity than the expected demand requires.
The distinction is important:
A completed schedule tells management who is working. It does not necessarily tell management whether the right workforce capacity has been scheduled.
That is where workforce scheduling begins to move beyond administration.
A Full Roster Is Not Necessarily the Right Roster
When workforce allocation and business demand are planned separately, the consequences often appear somewhere else in the operation.
Too little workforce capacity can surface as overtime, service gaps, workload pressure, production bottlenecks, or missed output. Too much capacity creates a different problem: labor hours are being committed without a corresponding operational requirement.
In either case, the roster itself can still appear perfectly complete.
Evidence from the Stable Scheduling Study illustrates why scheduling decisions can matter beyond HR administration. Conducted across 28 Gap stores in the United States, the randomized controlled trial found that stores implementing more stable scheduling practices experienced a 7% increase in median sales and a 5% increase in labor productivity during the intervention, while generating an additional $6.20 in revenue per labor hour relative to control stores.
These figures should not be interpreted as expected outcomes for another company, industry, or scheduling approach. The study examined a specific intervention in a specific retail environment.
What it demonstrates is more fundamental: how labor is scheduled can have consequences beyond producing a workable roster.
Another finding makes the distinction even more relevant. Only 30% of week-to-week variation in payroll hours was explained by changes in store traffic; shipment variability, promotional changes, and corporate visits also contributed to instability.
In other words, workforce volatility does not always originate from genuine changes in customer demand. Organizations can create part of that volatility themselves.
For management, the question therefore becomes more precise:
How can we deploy workforce capacity in response to genuine business demand without introducing unnecessary operational instability of our own?
Answering that requires moving the starting point of scheduling further upstream.
Demand Should Come Before the Roster
Traditional scheduling tends to begin with the resources already available:
Available People → Fill Shifts → Publish Roster
A demand-driven approach reverses the logic:
Understand Demand → Determine Workforce Requirement → Identify Required Roles → Allocate People → Publish Roster
The difference is not simply a new scheduling workflow. It changes what the schedule represents.
Historical demand can provide evidence of how the business has operated previously. Forecasting can turn those patterns into an expectation of what may happen next, while managers can apply information that historical patterns alone cannot see.
Only after expected demand has been translated into workforce requirements does individual employee assignment begin.
Consider a manufacturer preparing workforce requirements for the coming weeks. Historical production demand may reveal recurring patterns, but management may already know that a production line will undergo maintenance, a large order has been confirmed, or operating conditions will temporarily change.
The historical pattern remains useful. It simply does not have the final word.
The same principle applies across workforce-intensive operations. Historical occupancy does not know everything a hotel manager knows about upcoming events. Historical store traffic does not necessarily anticipate a new promotion. Historical workload does not automatically understand an operational disruption beginning tomorrow.
The objective, therefore, is not to replace operational knowledge with forecasting.
It is to give management a stronger analytical starting point for applying that knowledge.
Technology can make this process more systematic. Historical patterns can be processed at a scale that would be difficult to manage manually, forecasts can provide an initial view of expected demand, and workforce requirements can be connected more consistently to that expectation.
But the management principle comes before the technology:
The schedule should not be the planning process. It should be the output of the planning process.
Forecasting Should Inform the Decision, Not Make It
Forecasting becomes valuable when it helps management see patterns that would otherwise be difficult to process consistently.
But a forecast is still an estimate.
Historical information may indicate what usually happens, while managers may know what is about to happen: a confirmed order, a promotion, maintenance activity, a local event, a temporary closure, or another operational change that historical data cannot anticipate on its own.
This creates an important distinction between forecasting and decision-making.
A forecast can establish an analytical starting point. Management still needs to review whether that expectation reflects operational reality before translating it into workforce requirements.
The same principle applies as more sophisticated technology enters workforce planning. Automation—and, where relevant, AI—can help process information and support recommendations, but the objective should not be to remove management from the decision.
Human oversight remains important because the quality of a workforce plan depends not only on what historical data shows, but also on what the organization knows about what comes next.
The goal is therefore not autonomous scheduling.
It is better-informed scheduling.
Workforce Complexity Makes the Question More Important
The need for this approach becomes more visible as organizations expand.
Workforce complexity does not grow neatly with employee count. A business can add factories, stores, hotels, branches, business units, or legal entities, each with different roles, operating hours, demand patterns, and workforce requirements.
Two companies with 5,000 employees can therefore have dramatically different scheduling challenges.
One may operate primarily from a centralized location with relatively consistent working patterns. Another may distribute those employees across dozens of operational sites, multiple shifts, different roles, seasonal demand patterns, and several legal entities.
We have discussed a similar distinction in our perspective on multi-company HR. Organizational complexity is not simply a question of size; the structures through which people, policies, payroll, and responsibilities are organized also matter.
Scheduling introduces another layer to that complexity.
At enterprise scale, the question is no longer only:
How many employees do we have?
It becomes:
Where are they needed, in which roles, at what times, against what level of demand?
That is why workforce scheduling should increasingly be understood as a capacity-allocation problem rather than a calendar-management problem.
From Principle to Practice: Smart Scheduler
Rather than treating roster generation as the beginning of workforce planning, Smart Scheduler is designed around a sequence in which historical demand informs forecasting, managers can review the demand plan, workforce requirements are established, and employee scheduling follows.
The important idea is not simply that technology can generate a schedule faster.
It is that the roster comes after the workforce requirement has been considered—not before it.
For a closer look at how that workflow works in practice, readers can explore our dedicated article on Smart Scheduler in SunFish HR.
The Bigger Opportunity Is Not a Faster Roster
Workforce scheduling has traditionally sat close to the administrative end of HR. Someone has to build the roster, make sure shifts are covered, respond to changes, and publish the final schedule.
Technology can certainly make that work faster. But speed is probably not the most interesting opportunity.
For enterprise management, the bigger opportunity is to connect workforce deployment more closely with the demand the workforce exists to serve.
That changes the questions management can ask.
Not simply:
Who is available for this shift?
But:
- What demand are we expecting?
- What workforce does that demand require?
- Which roles need to be present?
- What does the forecast suggest?
- And what does management know that historical data does not?
Those questions put demand, forecasting, workforce requirements, and human judgment in the right sequence.
The schedule remains important. Employees still need to know when they work, managers still need coverage, and the business still needs a roster it can execute.
But the roster becomes something different.
It becomes the output of workforce planning rather than the starting point.
And for organizations trying to improve productivity without simply asking their people to do more, that may be the more important evolution in workforce scheduling.
