The scope
- Every change request is costed before it is accepted
- Anything out of scope is written down, dated and deferred, never forgotten
Back
HRIS project management assistance
Your project is under way, the vendor or integrator has been chosen, and you are missing someone on the client side who knows your processes as well as the solution. We take that seat.
What we take on
One person, from framing to run
Your project is under way, the vendor or integrator has been chosen, and you are missing someone on the client side who knows your processes as well as the solution. Pick a step to see what it covers.
- A few days a month alongside an in-house team, or a continuous presence
- On Cornerstone as on the other solutions on the market
- We know the solution from the inside, not just the method
Step 01
Study and framing
Set up how the project will run before it gets improvised along the way.
- Governance, milestones and gate criteria
- Risk and decision register
- Progress indicators that management can read
Step 02
Design
Get the business teams talking about their real work, then turn what they say into business rules the integrator can apply.
- Preparing and running the design workshops
- Decisions recorded, with the reasons behind them
- Specifications reviewed with the people who will live with them
Step 03
Oversight and acceptance testing
We know the solution from the inside. A "that is not possible" does not get through without being checked.
- Checking compliance with the stated need
- Managing gaps and change requests
- Test cases built on your own scenarios, defects qualified with you
Step 04
Training and change management
An HRIS project rarely fails on the technology. It fails when nobody has prepared the people who will have to use it.
- Mapping stakeholders and resistance
- Communication plan and information milestones
- Training for administrators, HR staff and managers
Step 05
Go-live
Cutover is prepared weeks in advance, and it is rehearsed.
- Dress rehearsal and pre-cutover checks
- Rollback plan, written and tested
- Consistency checks on the first data produced
Step 06
After go-live
The first weeks decide adoption. We stay as long as it takes for your teams to genuinely take over.
- On call during the first campaigns
- Fixing the irritants reported by users
- Handover to in-house teams and version upgrades
What we hold on your behalf
The timeline
- Slippage shows at the next milestone, not at go-live
- A delay announced early always costs less than a delay discovered late
Acceptance testing
- Test cases built on your own scenarios, not on the ones from the demo
- Defects qualified and prioritised with you, not by the integrator alone
The relationship
- A single point of contact from start to finish, who knows the file
- Openness about difficulties, including when they come from us
The format adapts: a few days a month alongside an in-house team, or a continuous presence for the whole duration of the project.
What you receive, and when
Documents your teams pick up after we leave, not presentation decks. All of them belong to you and are handed over in an editable format.
The project frame
- Framing note: scope, assumptions, what is out of bounds
- Milestone plan: criteria for moving from one milestone to the next
- Risk register: likelihood, impact, mitigation, owner
- Governance: who decides what, and how often
What will be built
- Design document: target processes, screen by screen
- Business rules: decided, dated, with the reasons behind them
- Permissions matrix: who sees what, who does what
- Interface specifications: flows, frequency, format, error recovery
Proof that it works
- Test strategy: what is tested, by whom, how far
- Test cases: built on your real scenarios, not on the demo
- Defect tracking: qualified, prioritised, followed through to closure
- Acceptance report: what is accepted, what remains open
So the teams follow
- Communication plan: messages, channels, timetable
- Training materials: by profile: administrator, HR staff, manager
- User guides: short, illustrated with your own screens
- Support arrangements: who to call in the first weeks
The big day
- Cutover plan: the sequence, hour by hour
- Rollback plan: written, tested, with its point of no return
- Post-cutover checks: what we verify before opening to users
To carry on without us
- Operations manual: the configuration and the reasons behind it
- Decision log: why it is this way and not another
- Points to watch: what breaks at version upgrades
- Roadmap: what was deferred, and when to pick it up again
Let's talk about your project.
A first 30-minute conversation is usually enough to see clearly: scope, a realistic timeline, the things to watch out for. No commitment.