The Temptation of a New Tool
There is a particular mood that appears before an organisation buys a new HR app. People are tired of chasing. Reports are unreliable. Spreadsheets have multiplied. Managers complain that they cannot find what they need. HR feels blamed for problems created by the wider system. Someone eventually says, “We just need a simple app.”
It is a seductive sentence. Simple sounds affordable. App sounds modern. Need sounds urgent.
But what does “simple” mean? Simple for whom? The HR administrator? The line manager? The employee? The finance team? The developer? And what job, precisely, is the app meant to do?
This is where many projects begin to drift. The organisation is certain it wants a solution, but less certain about the problem.
When Software Makes Mess Faster
A new HR app can be a very good investment. It can reduce duplication, improve reporting, support managers and make the employee experience smoother. But only if the underlying process is understood.
If onboarding is unclear, the app will digitise unclear onboarding. If ownership is vague, the app will contain vague ownership. If data is duplicated, the app may become one more place to duplicate it. If culture is not translated into practical behaviours, the app will not make people feel part of the company. It will simply host documents they may not read.
Technology is rarely neutral. It encourages certain behaviours and discourages others. A badly designed system can make the right action difficult and the workaround inevitable. A well-designed system can make the right action almost natural.
The Total Cost of Ownership Iceberg
The visible price of software is never the full cost. Beneath the surface sit hosting, maintenance, permissions, integrations, documentation, user training, support, fixes, security, upgrades, data migration and process redesign. There is also the cost of attention. Who will own the system? Who will test it? Who will answer questions? Who will update workflows when the business changes?
The build quote or licence fee may be only the top of the iceberg.
This is not an argument against software. It is an argument for seriousness. If a tool will shape how people join, work, develop and leave, it deserves more than a vague brief and a hopeful procurement process.
The Problem with “Intuitive”
Leaders often ask for software to be intuitive. It is a reasonable wish, but it can become a hiding place for undefined requirements. Intuitive to a new starter is not the same as intuitive to an HR specialist. Intuitive to a manager who uses the system once a month is not the same as intuitive to a payroll officer using it daily.
Instead of asking only for intuitive software, ask: what should each user be able to do without training? What decisions should the system guide? What information must be visible at the point of action? What should never depend on memory? Where should the mission, vision and values appear in the employee journey?
Those questions turn a preference into a design requirement.
Software and Company Identity
An HR system is not just a database. It is one of the places where employees meet the company. When a new starter logs in, what do they see? A list of forms? Or a clear explanation of the company’s purpose, their first-week plan and the people who will support them?
When a manager opens a probation workflow, does the system merely ask for a rating, or does it prompt a meaningful conversation about role purpose, values and development? When an employee completes training, does it feel like compliance theatre, or is it linked to the organisation’s direction?
If the company wants people to identify with its mission, the mission must be present in the systems people use. Not everywhere, not in a forced way, but at the moments where meaning helps.
Readiness Before Procurement
Before buying or building software, run a readiness test. Can we describe the process in plain English? Do we know the data sources? Have we chosen sources of truth? Are responsibilities named? Have we identified the users and their needs? Do we know what success looks like? Have we removed unnecessary steps? Have we included the company identity layer?
If the answer is no, the organisation may not be ready for software. It may be ready for process mapping.
This is not delay for its own sake. It is a way of preventing expensive disappointment. A few weeks spent clarifying the work can save months of rework later.
The Better Brief
A better software request might sound like this: “We need a tool that helps HR, IT, payroll and managers prepare for new starters. It must show the status of contract, payroll, equipment, access and induction tasks. Each task must have an owner and deadline. The new starter view must explain our mission, vision, values and first-week expectations. Managers must receive prompts for role-purpose conversations and probation dates. Success means every new starter has equipment, access and a clear plan before Day 1.”
That is far more useful than “we need a simple onboarding app”.
The App Is Not the Hero
The hero of a good HR system is not the app. It is the person who can now do their work with less friction. The manager who has the right prompt at the right time. The new starter who feels expected. The HR adviser who can trust the record. The leader who can see reality rather than chase fragments.
So before asking what software to buy, ask what experience you are trying to create. Do you want employees to feel processed, or welcomed? Do you want managers to feel monitored, or supported? Do you want values to sit in a document, or appear in daily decisions?
A good app can help. It simply cannot decide those things for you.
Questions Before the Demo
Before watching product demos, prepare your own questions. Do not let the software’s features define your needs. Ask how the tool supports the moments that matter most: joining, learning, managing, developing and leaving. Ask how easy it is to update mission and values content. Ask whether managers can see prompts at the point of need. Ask how ownership is displayed. Ask how data quality is protected. Ask what happens when someone changes role, location or working pattern.
Also ask what the system will not do. This is a neglected question. Every tool has limits. Knowing them early prevents disappointment later.
When a vendor says the system is flexible, ask for an example. Flexible can mean genuinely adaptable, or it can mean expensive customisation. When a system promises automation, ask what must be true before the automation works. Automation built on poor data is not efficiency. It is risk at speed.
The Employee Experience Lens
A useful test is to walk through the system as a new employee, a busy line manager and an HR administrator. What does each person see? What do they understand? Where might they hesitate? Does the system explain purpose, or merely demand compliance? Does it help people make better decisions, or simply record that something happened?
The best HR software feels like a well-organised colleague. It reminds, guides, stores and clarifies. It does not replace judgement. It supports it.
