Where Is Your HR Stuck Right Now? How to Read the Transition Signals

The trap in saying "it's somehow working for now"

In a growing organization, there comes a point when HR is the first to cry out. Some companies get by with Excel and Google Sheets; others rely on a payroll program adopted long ago or an outdated HR system. The tools differ, but the symptoms are the same. One day, all at once, attendance, payroll, and evaluation reach a scale and complexity that a single person can no longer handle.

People often cite "around 100 employees" as the benchmark, but headcount is not the essence — it is the signal. The true tipping point is the moment policies start to differentiate. Job types split from a single full-time category into contract, intern, and outsourced workers; a single work schedule divides into shift, flexible, remote, and on-site work; and evaluation that once ended with a team leader's word begins to require a structure that spans job levels and multiple raters. With even 80 employees, if this differentiation is fast, the tipping point arrives early; with 150 but a simple structure, it comes late.

Yet many organizations do not change their systems at this point, because there is no immediate fire to put out. Payroll goes out somehow, attendance can be compiled by hand, and evaluation got through another year. While they hold on, costs accumulate invisibly. Payroll closing runs late every month-end, disputes over remaining annual leave repeat, and every evaluation season the HR team can do nothing else for two weeks or more. This is the typical picture of an organization where people, not systems, are holding the line.

The bottleneck always erupts in three places at once

Supporting HR transitions for growing organizations, HCG has repeatedly observed one pattern: the bottleneck erupts almost simultaneously across payroll, attendance, and evaluation. It is rare that fixing only one of the three is enough.

The reason is simple. These three areas are not separate problems but three branches that diverge from a single cause — the organization is differentiating. As job types grow, payroll items grow; as work arrangements diversify, attendance rules grow complex; as teams multiply, evaluation criteria fragment. Because they grow simultaneously from the same root, when the complexity of one area rises, the other two rise with it.

• Payroll — When job types are simple, an Excel payroll ledger is enough. Once full-time, contract, intern, and outsourced workers are mixed and allowance items multiply, new exception cases and retroactive adjustments arise every month. The moment what was one or two exceptions becomes 10 or 20, Excel can no longer serve as a verification tool.
• Attendance — With a single work schedule, you can compile clock-in and clock-out records by hand. Once shift work, flexible work, remote work, and on-site work are mixed and attendance rules differ by department, calculating annual-leave usage promotion, compensatory leave, and overtime allowances becomes impossible to verify in Excel at all. In industries with a high share of shift and on-site work, such as manufacturing and distribution, this point arrives earlier and more complex.
• Evaluation — When management can judge directly, no separate structure is needed. As teams grow, evaluation criteria by job level become necessary, demands for 360-degree and multi-rater evaluation emerge, and the work of handling appeals follows. When criteria differ by department, disputes over fairness are inevitable.

The problem is that these three areas are connected by data. To process a payroll exception, you have to re-check the attendance data; while organizing attendance, you find that evaluation criteria differ by department, which blocks variable-pay calculation. Running each on a separate tool generates manual work at every connection point, and once that accumulation crosses a threshold, it erupts as accuracy problems — payroll errors, annual-leave disputes, and evaluation appeals.

It is not just complexity that grows — external expectations rise too

What grows as an organization scales is not only internal complexity. The external legal expectations placed on the company rise as well.

Things that were not much of an issue at 50 employees become clearly defined obligations under labor law as the company grows. Managing the 52-hour weekly overtime limit, lawful notification of annual-leave usage promotion procedures, issuing wage statements, granting rest breaks, accurately calculating various statutory allowances — all of these are not simply matters of "just comply," but matters of "you must be able to prove with records that you complied."

A labor inspection can begin not only as a pre-announced regular review but also from a single employee complaint. At that moment, what the company must produce is not the statement "we are complying well," but data showing who worked when and how much, how annual leave was promoted, and on what basis allowances were calculated. An organization whose attendance and payroll are scattered across Excel and handwritten records cannot pull this material out immediately. This gap, invisible in normal times, materializes at the moment of inspection as the cost of fines and corrective orders.

If internal policy differentiation is the reason to move the transition up, external regulatory expectations are the reason it grows dangerous to delay. Both pressures demand the same thing — gather scattered records into one and connect them to each other.

If you are already stuck, it is not too late — it is the right time to transition

Let us be clear about one thing. If the symptoms above are already happening in your organization, that is not a sign of falling behind but the most precise signal to begin the transition.

"You should have prepared before getting stuck" is true, but in reality most organizations move only after they get stuck. That is normal. What matters is not "when you realized it" but what you do first after you realize it. If all three areas are already creaking at once, it also means your organization's policies have become concrete enough to be systematized. In fact, now may be the best time to organize your policies and put them into a system.

What separates the organizations that are behind from those that are not is not the moment of realization but the way they begin the transition.

What is harder than changing the system

The failure growing companies most often experience in HR transition is not a failure of tool selection. It is starting the adoption without clearly defining the organization's HR policies before the transition.

An HR system is a vessel that holds attendance, payroll, and evaluation data. Yet in growing organizations, the criteria for how this data should be generated and connected are often not yet established. Annual-leave grant criteria differ by team, allowance items vary by the person in charge's judgment, and evaluation grades are assigned by different standards depending on the department head. Adopting a system in this state does not let the system organize the chaos — it simply pours the chaos in as is.

Growing companies usually take one of three paths to set up a system — and each path has its own typical failure.

1. Build it via SI or in-house development — "tailored to us" becomes "trapped in us"

Developing it to fit your current policies exactly is convenient for now. But policies keep changing. Every time a law is amended, a new job type appears, or the evaluation method changes, a development task arises and incurs cost and time. In the end, the "fit" becomes a "shackle," trapping you in a structure where you must pay to fix it with every change.

2. Force yourselves into the system's fixed features — exceptions leak outside the system

SaaS lets you start quickly and cheaply. The problem is the moment your policies deviate from the standard the system assumes. "Our own exceptions" — such as composite assignments, special allowances, and variable work schedules — cannot be accommodated by the system, so that part ends up back in Excel. With data existing in duplicate inside and outside the system, the verification burden grows greater than before adoption.

3. Leave the outdated system as is — people fill the system's limits

Unable to replace a system adopted long ago, you fill the added complexity with the person-in-charge's manual work. The system looks fine, but in reality the core logic lives in one person's head and personal Excel files. The moment that person is away or leaves, the organization can no longer explain its own payroll and attendance.

The common thread across the three paths is clear. In every case, before the system was chosen, there was no definition of "what policies our organization currently runs on, and how they must change going forward." Without that definition, development gets trapped in the present, policies and system diverge so exceptions cannot be held, and the outdated system depends on people. Policy definition comes first; the system comes second.

When choosing an HR system, you have to change the question

The criterion growing companies use most often when selecting a system is "does it fit our current scale?" But this very question is the trap that triggers another transition one or two years later. A system optimized for 100 people reveals its limits again the moment you reach 300.

You have to change the question like this.

What these questions have in common is that they look not at "now" but at "going forward," and not at "the number of features" but at "a structure that absorbs change through configuration."

How JaDE answers

There is a reason JaDE's major clients are rapidly grown companies such as Kurly, Woowa Brothers, RIDI, Bucketplace, and APR. What these companies commonly needed was not "a system that works right now" but a structure that could keep accommodating their policies as they grew more complex with growth.

JaDE's roughly 590 configuration features are the answer to this question. From the payroll exception handling, composite assignments, diverse work schedules, to multi-rater evaluation that growing companies face — JaDE implements all of this through configuration alone, with no additional development. Whether it is shift work in manufacturing and distribution, flexible work at a tech company, or an old seniority-based pay system with a complex allowance structure, JaDE absorbs it through configuration rather than tearing the system apart. It is a way to simultaneously avoid the three failures seen earlier — being trapped in development, being blocked by the limits of a system that does not match your policies, and depending on people. Because attendance and payroll are recorded as one connected whole, the evidence materials a labor inspection requires are produced immediately, with no separate work.

On top of this, the JIC (JaDE Implementation Consultant) — an expert with hands-on HR experience — completes the setup directly at the adoption stage. Rather than just handing over a tool, it blocks the failure of "adopting without knowing your policies" at the starting point. As a result, the build period is also shortened by more than 40% compared with typical build-type implementations. (As of 2026)

The success or failure of an HR system transition is decided not by the tool but by preparation. Whether you are already stuck or on the verge of it, what you must do now is the same: define your policies first, then choose a structure that can absorb them through configuration. For an organization that is so prepared, an HR system transition becomes not a halt but an infrastructure for growth.