IT system rollout

HRjects was built for HR software rollouts. The structure underneath, phases with gates, a board, process maps, an issue log and a readiness score, suits other system rollouts too. This page explains what an IT team gets and what it does not.

What you would use

Create a project from the General project template. It has four phases: Plan, Design, Build, Launch. Each ends in a gate with exit criteria you can change. The template's workstreams are Planning, Design, Delivery and Communications, and its teams are Project lead, Team, Stakeholders and Vendor.

What carries over from the HR product

• Business case. Yearly cost today against each option, with saving per year, payback in months, three-year net and a sponsor decision of Pending, Approved or Not approved.
• Roadmap and gates. Ticking an exit criterion records who ticked it and when. Useful for a security review or an architecture sign-off.
• Tasks. A board with To do, In progress, Blocked and Done, filtered by workstream and team.
• Process maps. Current-state steps beside future-state steps for each process the system changes, with pain points and gaps. One click turns a gap into a task.
• Issues. A light log for testing and the weeks after launch, with severity, owner and status.
• Go-live readiness. A weighted checklist that gives a percentage and a Go or No-go. Go needs 90% and no open critical issues.
• Overview and activity log. What needs attention, and who changed what.

What is not relevant

The HR-specific pieces are left out of the General template: the parallel payroll tracker, the HR workstreams and teams, and the starter HR process library. You start with one blank process map and add your own.

An example

Say you are replacing a service desk tool.

1. Plan. Enter today's subscription and coordination costs in the business case and compare two vendors. Exit criteria: goals, scope and owner agreed; budget approved.
2. Design. Map request intake and incident handling as they work now and as they should work. Log gaps, such as an approval step for large requests. Exit criterion: design reviewed by stakeholders.
3. Build. Configure, migrate open tickets and test. Log defects in Issues. Exit criterion: work complete and tested.
4. Launch. Tick readiness items: tested by the people who will use it, stakeholders signed off, communications sent, support owner named.

Where a general tool is the better choice

Be clear-eyed about this. HRjects is new and narrow. It has no Gantt chart, no task dependencies and no integrations today. Jira and ServiceNow issue sync, Slack and Teams alerts and company single sign-on (SAML) are planned and not built. If your rollout depends on linking tasks to tickets, on dependencies across many teams, or on SAML, use a general project tool. The comparison pages describe several fairly.

HRjects fits when the hard part of your rollout is agreement and readiness: getting sign-offs on record, closing the gaps between the old process and the new one, and making a go or no-go call people will stand behind.

Try it

Start a free project with the General template and the example-data option to see a small rollout under way. The template guide compares all three templates.