blogs
The Quilyx one-pager. Control change at a glance
In our earlier blogs about the Quilyx VERDER method, we already wrote that predictability requires more than just a plan or a monthly report. That is exactly why, at Quilyx and with our clients, we work with the Quilyx one-pager.
With this overview, the client gets a complete picture of the change initiative at a glance. Not in the form of a long report or a collection of separate documents, but in one compact view that shows where the project stands, where it came from, and where it is going.
That brings several benefits. It creates calm and confidence for the client, makes steering committee meetings sharper and more effective, and helps the project manager think more clearly about what truly matters at that moment.
Why a one-pager works
The one-pager is valuable first of all for the client.
A client wants to see whether a project is in good hands. Not by following every detail, but by quickly understanding how the initiative is doing, where the risks are, and whether any action is needed from their side. A good overview supports exactly that. It builds confidence when things are going well and shows early when intervention may be needed.
It also helps keep steering committee meetings compact and effective. We generally believe that a small steering committee is more effective than a large one. In a later blog, we will go deeper into the ideal composition, roles, and responsibilities of the steering committee. The one-pager already supports that principle because only one page is on the screen during the meeting. That page is reviewed in a disciplined way. As a result, a steering committee meeting can often be held within thirty minutes. Only the core topics that truly matter to the steering committee are discussed.
Of course, this only works when the project manager has been given enough mandate and trust. That is another reason why this report is so useful. It quickly makes visible when that mandate or trust is still not strong enough and when the steering committee needs to act.
Perhaps even more importantly, the project manager is really writing this overview for themselves as well.
It is a moment of reflection.
Where am I now. Where did I come from. Where am I going.
We often see reports that run for pages and turn into long narratives. By forcing everything onto one page, with limited space for each section, the project manager is pushed to think sharply. What do I really want to say. What matters now. Are these truly the key risks and issues. What were the highlights of the past period. Which results have we achieved. And what is planned for the next period.
How the one-pager is structured
At the top of the one-pager is the name of the project or program. Below that are the key players, such as the name of the program manager, project manager, or lead architect. We deliberately do not show the full team there. In large programs, that would not be practical anyway. This section is only for the key role holders relevant to the steering committee and those who may need to join the meeting.
The dashboard in the top left
In the top left is the dashboard. This dashboard consists of the following dimensions:
- cost
- schedule
- scope
- quality
- resources
- value
- transition
The first four are familiar from classic project control. Traditionally, the well-known triangle focused mainly on time, cost, and quality. Later, in many models, quality was partly replaced by scope, almost as if quality were simply the result of the balance between the other forces. We deliberately choose to show scope and quality as two separate dimensions. If schedule, cost, or scope come under pressure, that does not automatically mean quality is affected. And the other way around, quality may be threatened by factors other than time, money, or scope.
The resources dimension covers both human and non-human resources. Does the program have enough people and enough knowledge in place to support the objective. Has the required hardware been delivered on time and is it functioning properly. Are the necessary conditions in place to do the work.
The value dimension goes one step further than just objective and result. In addition to delivering results and supporting the objective, a project should ultimately create value. Are we still getting the value we expected. Or are there new insights that put that expected value into question.
The final dimension is transition. This concerns the status of the change itself. In a later stage, especially in IT projects, this may also refer to the transition from the project into the standing organization and the embedding of the change into operations.
Together, these dimensions provide a complete view of how the project is doing.
The link to risks and issues
But we go further than just the dashboard.
Risks and issues are linked to these dimensions. That happens in a separate RAID log, which we will cover in a later blog. This makes it possible to see quickly which risks or issues are causing a specific dimension to be amber or red.
The RAG method
For the dashboard, we use the RAG method: Red, Amber, Green.
Green means that everything for that dimension is in order and the project is in good shape in that area.
Amber means that there are signs that something may not be going well. This is mainly the point where the project manager starts to have concerns. For example, when the program organization is not yet fully staffed, or when a newly identified risk could affect time or cost.
Red means that there is a real problem. At that point, the steering committee must take a decision about that dimension.
Ideally, red is preceded by an amber warning in a previous meeting. However, due to the dynamic nature of projects and change initiatives, it can happen that something moves unexpectedly from green to red. In that case, there is genuinely something serious going on. The project manager can no longer resolve the situation within their own mandate or tolerance. The steering committee needs to step in and decide how the situation should be handled.
The financial line
Below the dashboard is the financial line.
This shows the budget, the amount spent, and the forecast for the remainder of the project. These numbers may differ, as long as they stay within the tolerance buffer given to the project manager.
During the project, the budget may be increased. In that case, the new budget should be shown as such in the overview. That keeps the financial picture accurate and transparent.
Objective and highlights in the top right
The top right starts with the objective in one sentence.
In an earlier blog, we wrote that it is important to keep the objective top of mind. This is one of the ways to do that. By giving the objective a fixed and visible place, it remains clear to everyone why this project or program exists.
Below that are three or four highlights. These are the most important facts or observations the project manager wants to share with the steering committee about the past period. These can be positive or negative points.
If you ask us how to structure them, our advice is always the same: start with the positive points and end with the negative ones. That creates the right communication flow and prevents positive signals from being immediately overshadowed by negative developments.
Risks and issues in the bottom left
In the bottom left, we include three or four of the most important risks.
A clear distinction matters here.
A risk is something that has not happened yet. It is a possible event that could cause one or more dimensions to become amber or red. Once the event actually happens, it becomes an issue.
An issue should therefore ideally be preceded by an earlier identified risk.
Here too, we deliberately limit the number. By keeping the number of risks and issues small, the project manager is forced to think carefully about what really matters. And if there are more important topics than can reasonably fit, it is often better to organize a separate risk management session with relevant steering committee members and other stakeholders than to try to force everything into one steering committee meeting.
For each risk, the project manager explains what the risk is, how likely it is, what the impact would be, and which mitigating actions are being taken. The project manager can also explicitly ask the steering committee for help in reducing the risk.
Issues are acute or ongoing situations that threaten the results and the objective of the project. Here too, we ideally name no more than three or four.
Critical deadlines
At the bottom of this block, we show the critical deadlines.
Usually this is one, sometimes two, and at most three. These are dates that need to be repeated consistently, such as the date on which vendor support ends, a contractual deadline, or the date of a key event for which specific results need to be delivered.
By keeping these deadlines visible, they remain part of the management conversation.
Recovery date, results, and look-ahead on the right
On the right-hand side, the one-pager starts with the date on which the project manager expects the project or program to be back on green.
That is the date by which the mitigating actions are expected to have been implemented and the risks and issues sufficiently resolved. If everything is green, this date remains empty. If not everything is green and the project manager cannot give a date, that is an important signal to the steering committee. It means there are issues in play for which no concrete recovery plan yet exists.
Below that come the results. Again, we typically list three or four. These are the most important results achieved in the past period.
Finally, there is the look-ahead to the coming period. These may be milestones, but also important events, mitigating actions that will be implemented, or problems that need to be resolved.
Why this one-pager is so powerful
With this one-pager, the project manager, the steering committee, the sponsor, and other stakeholders can see at a glance how the project is doing, where it came from, and where it is going.
That is exactly the strength of the one-pager.
It creates calm. It forces clarity. It supports better decisions. And it helps focus management attention on what truly matters.
Within the Quilyx VERDER method, it is therefore not just a reporting instrument, but a key tool to support predictability, ownership, and calm.
Gerelateerde blogs
Calm in IT projects. Why calm is essential to project success
In the previous blogs in this series, we explored predictability and ownership. With that, we covered two important foundations of the Quilyx VERDER method. In this blog, the third element takes center stage: calm. Calm may sound less tangible than a roadmap, a plan, or a governance structure. Yet calm is of enormous value to […]
Objective in IT projects. Why the why matters more than the what
In the previous blogs in this series, we explored predictability, ownership, and calm. With that, we covered the first three foundations of the Quilyx VERDER method. In this blog, the fourth element takes center stage: objective. We begin with a distinction that is often not made sharply enough in projects and programs, namely the difference […]
The Quilyx VERDER method for successful IT change
At Quilyx, we believe IT projects and programs can succeed more often than they do today. That is our mission. We want to create more project success, more control over change, and above all more calm, clarity, and results inside organizations. We already deliver that value for our clients every day. We also support the […]
Results in IT projects. What should you deliver and why
In the previous blog in this series, we focused on objective. There, we explained the difference between the why of the change and the what that a project or program must concretely deliver. In this blog, the fifth element of the Quilyx VERDER method takes center stage: result. If the objective gives direction to the […]
Ownership in IT projects, the key to successful change
In the previous blog in this series, we looked at predictability. With a clear roadmap, we make sure a project or program has direction and that stakeholders can see where the change is heading. But a good roadmap alone is not enough. Many projects have a plan, reports, and governance structures, yet still get stuck. […]
Origin of Quilyx
Where does a name come from? In our case, the origin of Quilyx began with a simple phrase. Not from a brand agency or a naming session but from an honest client need. Quilyx comes from the Dutch words ik wil iets, which means “I want something.” When spoken quickly, it becomes ikwiliets, which naturally […]
Predictability as the foundation of successful IT change
In our previous blog, we introduced the Quilyx VERDER method. This method is built on five elements: Predictability, Ownership, Calm, Objective, and Result. Together, they form the foundation of how we approach successful IT change. In this blog, the first element of the method takes center stage: predictability. That is no coincidence. In our view, […]
Project, program, or portfolio. And Waterfall or Agile. What is the real difference
In the previous blogs, we covered the five elements of the Quilyx VERDER method: predictability, ownership, calm, objective, and result. Now that the method itself has been outlined, it is time to step back and look at a set of concepts that are often mixed up in practice. Many discussions about approach, governance, and roles […]







