The Illizeo Pulse method: how we deploy your HRIS

Illizeo Pulse is the method our consultants use to deploy Illizeo for our customers. It has five phases — Prepare, Unify on the standard, Launch in iterations, Secure, Evolve — and rests on a simple idea: start from what the software already does, and show you the result early and often rather than at the end.

PPrepare #

Goal: agree on what we deploy, for whom, and in which order.

• Scope: the modules selected, the populations and entities involved.
• What exists today: your current HR processes, files and tools, the data to migrate.
• Interfaces with your information system: each one gets a scoping workshop, usually half a day to one day per interface, so it can be quoted.
• The team: a lead project manager on Illizeo’s side, technical configuration under our CTO’s responsibility; on your side, a project manager and business key users.

Output: a scoping note, the split into batches and a shared plan. The number of implementation days is set at this point, based on the actual scope.

UUnify on the standard #

Goal: answer each need with what already exists before considering anything custom. The closer your configuration stays to the standard, the easier it is to maintain and the more directly you benefit from new versions.

• We walk through your processes with you, module by module, in the software.
• For each gap, we first look for the answer in the standard, then in configuration.
• Specific development is only proposed when nothing else covers the need; it is then quoted and decided separately.

Output: the list of approved configuration choices, and the list of remaining gaps with how each is handled.

LLaunch in iterations #

Goal: show you a concrete result at every step, to correct early rather than discover gaps at the end.

• The project moves forward in functional batches (for example: employee record, then absences, then an additional module).
• Each batch is configured in your environment, then demonstrated to your key users.
• Your feedback is applied before moving on to the next batch.

Output: batches configured and approved by your key users as the project goes.

SSecure #

Goal: put everything in place for a go-live without bad surprises.

• Data: your data is migrated by import, then checked by your key users.
• Access: roles and permissions for each profile, segregation of duties where needed.
• Testing: your key users test the processes end to end on their real cases.
• Training: administrators and key users are trained before opening.

Output: an explicit go-live decision, made together with you.

EEvolve #

Goal: support the go-live, then evolve your solution over time.

• Opening to users and support during the first weeks.
• Support Monday to Friday, 9 am to 7 pm, with an on-call line at weekends.
• New versions released regularly throughout the year.
• Each new module or new entity goes through the same Pulse cycle, at its own scale.

In short #

Want to see how Pulse would apply to your project? Book a meeting with us.