Every HR system arrives with decisions already made: which fields a hiring form has, how long the rating scale is, how many roles can be marked critical for succession. A team that cannot change those settings changes its own practice instead. It trims a hiring profile to fit the form, or reshapes a rating scale so two systems can share data, or names one critical role because the system will not take more. Each choice is small and keeps work moving, and after a few years the software's design is the company's talent policy.
The same happens wherever software holds records. A shop's till decides which categories it can sell by, and a school's records system decides what a student's progress can look like. Whatever holds your records decides what your records can say.
The vendor's rules are reaching further
That reach is growing. Workday has announced that its assistant will work inside Claude, Teams and Slack and carry a company's policies and approvals with it, which means a rule configured in the HR system, default or not, will soon answer employees' questions in the chat tools they already use. We wrote about Workday's rulebook for chat apps when it was announced. The less a company has examined its settings, the more of them it will be handing out.
A small tool on top of the system
Take the HR manager of a hospital group with 600 staff who wants a succession plan for twelve critical roles, in a system that takes one. Until now her choices were a change request to the vendor that waits for a future release, or a spreadsheet she updates by hand. Now she can describe the plan to an AI assistant: a table of twelve roles, a named successor and a readiness level for each, and a flag on any role with no successor ready within a year. The tool reads an export of the employee records and never writes back to the system. That is an afternoon to build and test, and about an hour a month to keep current.
The clearest first target is the glue work. Companies that run many systems have people who copy data between them every week. If one person spends a day a week on that, it is about a fifth of a working year, and a small tool that does the copying is the easiest case for building. Many teams that build with AI have already replaced at least one software subscription with something of their own.
What the owner takes on
The spreadsheet years show the price. People gained independence from the IT department, then needed support, then demanded access to the central data, and that started a new round of budget arguments. A tool built by an HR manager follows the same course. It breaks when the export changes, and it holds names and readiness ratings that must stay behind the company's login. So it works best where the logic is the company's own and the records stay in the vendor's system as read-only copies.
Start with a list. Ask every manager for the last five times someone said the system would not let them do something, and write down what they did instead. Each workaround is a policy that someone made without choosing it. For each one, decide whether to keep it, ask the vendor to change it, or build your own rule on top.