No proprietary methodology to sell you. A way of working proven on more than fifty projects, which we adapt to your size and your HRIS maturity.
An HRIS is not configured from a generic catalogue. It is built from your sector, your business and the way your teams actually work.
What we add are the good practices that fifteen years of projects have validated: the ones that keep you out of dead ends. They feed the configuration, they do not dictate it. Our role is to remain facilitators for the business, not guardians of a method.
Eric Boileau, JOY TalentsEvery sector has its own constraints: a construction site is not run like a branch office, and one collective agreement looks much like another on paper but not in practice. We take the time to get to know your activity before we talk configuration.
An HRIS project is not an end in itself. If it makes life harder for the teams or slows the business down, it has missed its purpose. We look for what moves the company forward, not what ticks the boxes of a methodology.
Employees and managers are the platform's first users. If the screen they open is confusing, adoption will not follow, however good the configuration behind it.
Before proposing a third-party solution, we look at what the platform can already do. That is what years of projects are for: knowing how to work around a limit intelligently rather than adding one more tool to maintain.
Rigour on commitments, deadlines and deliverables. Good humour in the way we work together. The two are not mutually exclusive, and a long project holds up better when the meetings are not a chore.
Including when the answer is not the convenient one. If a request is a bad idea, we say so. If we do not know, we say that too. It is the only basis on which a consulting relationship lasts.
Four things we do not compromise on.
We meet the people who keep HR running day to day before we talk about tools: payroll officers, training and recruitment officers, line managers, IT.
What we look for: the workaround spreadsheets, the double entries, the questions that keep coming back. They are the best indicators of what an HRIS needs to solve.
We turn that material into a trajectory: what is handled now, what is postponed, what is explicitly dropped.
We would rather announce a constraint early than a delay late. Framing ends with a file ready for the executive committee: stakes, scenarios, budget, timeline, risks.
Running the workshops, configuration, vendor follow-up, data migration, acceptance testing, go-live rehearsal. We work alongside your internal project manager, never in their place.
At every steering committee, a factual progress update: what is done, what is blocked, what needs a decision.
A successful engagement is one you can step out of. We document the configuration, train the administrators and leave behind an adoption follow-up plan.
Our success is measured by your autonomy six months after we leave, not by the length of the engagement.
A value that does not translate into a commitment we can keep is worthless. Here are ours, and what they entitle you to demand.
You work directly with the expert. No juniors on your projects, no hand-off between pre-sales and delivery.
Concrete solutions, suited to your reality on the ground. We look first to remove steps, not to tool up more of them.
A detailed quote, described deliverables, dated milestones. Any scope change is flagged and decided before it is committed.
At your side until you are fully autonomous, including after go-live. A tool that is not adopted is not a delivered project.
A first 30-minute conversation is usually enough to see clearly: scope, a realistic timeline, the things to watch out for. No commitment.
