In our assignments, one scene comes back with troubling regularity. The steering committee opens, the dashboard goes up on the screen, and everyone comments on a progress status the teams do not recognise. The project is moving forward, the reporting tells a different story. Nobody is acting in bad faith: the set-up itself produces the gap.
That observation gave birth to Henry, a planning and project control application published by PM side. We present it here because it answers, point by point, difficulties we have long been describing on this blog.
The great misunderstanding of project control
It all starts with a legitimate request: knowing where projects stand. Management deploys a tool, defines indicators and organises the reporting flow. But that tool is almost always designed from the top, around the needs of those who read the data, far less around the reality of those who have to produce it.
Teams end up facing a system that asks them to report on their work without helping them do it. Real activity keeps flowing through emails, meetings, personal to-do lists and side files. Official information slowly drifts away from the field. The outcome is familiar:
- schedules that are out of date a few weeks after kick-off;
- workload plans kept separately, in a spreadsheet;
- status updates that have to be chased, then pieced together;
- committees spent commenting on figures that are already stale;
- decisions delayed for lack of a reliable view.
"We think top-down, we hope for bottom-up, and we harvest bullshit-up."
When a tool fails, the diagnosis comes quickly: resistance to change, not enough support. We believe the problem lies further upstream. No amount of training will durably turn a reporting tool into a working tool. And a project method reduced to reporting costs the organisation without delivering its real benefits: controlling a sequence, securing a deadline, balancing a workload, spotting a problem early enough to act.
Tackling the problem from the other end
Henry equips first the people who move projects forward. The consolidated view intended for management becomes the consequence of properly structured work, not one more chore.
The schedule gets back its original purpose: stating what needs to be done, in what order, with which resources and which dependencies. Anyone can open a task, break it down into actions, assign themselves those actions, create new ones and discuss them in a thread attached to the task. Work no longer happens next to the schedule, it takes place inside it. Progress is no longer declared after the fact: it becomes the visible result of the work done.
One reality, five ways of looking at it
Rather than stacking tools that each tell a different version of the project, Henry organises a shared body of information, presented according to each person's role:
- the team member structures their activity;
- the project manager controls deadlines and sequences;
- the team lead balances their colleagues' workload;
- the portfolio manager spots tensions between projects;
- the executive gets a consolidated view that comes from the field.
Scheduling and workload planning stop living in two separate worlds: when a timeline moves, its impact on capacity becomes visible. This is exactly the resource management blind spot we see in most organisations.
Henry also builds in the rules needed to construct a realistic schedule and flags inconsistencies as soon as they appear. The quality of the schedule no longer depends solely on the planner's expertise, which echoes a conviction we have long defended: no schedule is better than a bad schedule.
Where Henry comes from
In the interest of transparency: Henry is published by PM side, which Xavier Hovasse, head of IXILA, co-founded with Mathieu Chateau. Since 2009 they have been designing and deploying project management solutions. They were among the first to offer Microsoft Project Server as a SaaS service, then developed More with Project, an add-on that simplifies Microsoft Project and detects anomalies in a schedule.
For years, PM side tried to adapt existing tools to field reality. But their limits came from an initial choice: equipping the reporting flow rather than the work. At the end of 2025, the two partners started again from scratch, with one simple rule: every feature must first be useful to the person who uses it every day. Consolidation comes next.
The name pays tribute to Henry Laurence Gantt, the engineer behind the chart that bears his name. His chart combined two qualities that tools have gradually pulled apart: rigour and readability. The person deciding and the person doing the work looked at the same picture of it. That is the intention Henry aims to recover, with today's possibilities.
Who Henry is for
Henry covers the whole chain: scheduling, collaboration, workload planning, capacity, time tracking, portfolio management and links between projects. It is aimed at project-intensive organisations (industry, technology, energy, public sector), at PMOs, project departments, portfolio managers, project managers and resource managers. And also at organisations that are already equipped but disappointed, or that still run their projects on spreadsheets.
Its promise fits in one line: accurate, robust schedules, without the pain.
Discover Henry
The website presents the application and its screens for each role, and offers a 30-minute demo or a 14-day trial.
Discover Henry