GullyHR runs HR change as one sequenced programme instead of as a set of unconnected initiatives. We assess how the function works today, agree a target operating model with you, decide the order in which processes, structure and systems change, and stay with the work until the old way is switched off on a stated date. Your leadership team owns the decisions, structure, roles, budget and timing, and your managers carry the change into their teams, because a change nobody senior has visibly backed does not survive its first busy week. It runs as a defined programme with named phases, an internal owner for each, and a review after go-live.
The change starts from a business decision, not from an HR wish list.
We begin with what the business needs to be able to do: open a second site, serve larger customers, run without the founder in every approval, and work back to the HR changes that make that possible. The rest stays out of scope.
How the HR function will run is settled before anything is redrawn.
The operating model states what HR owns, what managers own and what the owner keeps: who approves a hire, who signs a salary revision, who closes a grievance. Decision rights are written down first, because every process below them depends on the answer.
Processes are rebuilt in the order the business can absorb.
Each process in scope is redesigned to the new operating model, covering steps, forms, approvals, records and the manager's part in it. One workstream runs at a time, and the next starts only when the previous one is genuinely in use.
Reporting lines and approval limits move on the same day.
Where the structure changes, reporting lines, approval limits and role definitions are revised as one change with a single effective date, rather than announcing a new chart while the old approvals keep running underneath it.
What HR will run on is decided before anything is configured.
We map what is actually in use, including spreadsheets, the biometric device, payroll software and the accounting system, and agree what stays, what is replaced and what data moves where. The migration format and the data owner are fixed first.
Employees hear about the change from you rather than from each other.
We draft the announcement, the manager briefing and the employee question sheet, and set the order in which people are told. What is changing, what is not, what it means for pay and leave, and where to raise a concern are all stated plainly.
The old way is switched off on a date everybody knows.
System modules go live one at a time, with a parallel-run period where the old record is still kept. A cut-over checklist confirms the data is right, and only then does the old sheet or register stop being maintained.
Managers commit in the room where the change is decided.
Reporting managers and function heads review each redesigned process before it is issued, raise what will not work in their team, and agree the version that goes out. Their names sit against the parts they own on the roadmap.
Nothing is scheduled during payroll week or appraisal season.
The roadmap sets workstreams, dependencies, internal owners, review points and the freeze windows when nothing changes: payroll dates, statutory filing, appraisal cycle and your peak business months. Leadership reviews it at fixed points rather than on request.
We come back and check what is actually being used.
After go-live we look at the new process in operation: which approvals run through the system, which still go by message, where records are incomplete and which managers need another round of support. Corrections are agreed with you.