Defining Clear Objectives, KPIs, and Projects in X-Matrix
Many organizations begin strategy discussions with broad pillars such as customer centricity, innovation, or digital transformation. These themes are useful for communicating direction to investors and employees. However, for strategy execution and deployment purpose they need to be translated into operational priorities. When teams attempt to put these pillars directly into objectives without clear mapping and translation, the result often remains abstract. Statements such as “improve customer experience” or “strengthen innovation capability” sound directionally correct but offer little guidance for execution as an objective. At the end of the year it becomes difficult to determine whether the objective was achieved or simply pursued.
A useful discipline is therefore straightforward: a good objective should allow a clear answer to whether it was achieved or not. Whenever possible, objectives should be expressed in measurable terms or framed in a way that makes success observable. This does not mean every objective must be purely numeric, but it should be concrete enough that interpretation is limited.
KPI - Real-time progress report
KPIs play a different role. They are not the objective itself but the signal that indicates whether progress is occurring. Effective KPIs track outcomes rather than activity. Measuring the number of initiatives launched or meetings held may indicate effort, but it rarely reveals whether strategic progress is being made. KPIs in the X-matrix should therefore connect strategic intent to observable results, allowing leaders and teams to detect early whether the organization is moving in the intended direction.
Project charter
Projects represent the deliberate work undertaken to influence those outcomes. A useful way to think about projects in the X-matrix is to ask whether they materially advance the strategy. Some initiatives accelerate the current direction, such as scaling a successful product line or improving a pricing model to strengthen margins. Others enable a shift in direction by creating new capabilities, such as implementing a digital platform, building a new distribution channel, or redesigning a key operating process. What these initiatives have in common is that they change something meaningful about the organization’s trajectory.
A defining characteristic of a good project in the X-matrix is that it has a clear deliverable. Completion should correspond to a tangible outcome: a system implemented, a capability established, a product launched, or a process redesigned. This clarity prevents initiatives from becoming open-ended activities and allows teams to understand when strategic work has actually been completed.
What belongs to X-matrix?
At the same time, not every activity within the organization belongs in the X-matrix. Routine operational work, ongoing maintenance, and standard processes remain essential but are better managed through normal operational systems. A simple test is whether delaying or cancelling an initiative would materially slow strategic progress. If the answer is yes, it likely belongs in the X-matrix. If not, it is probably part of business-as-usual operations.
Another common misconception is that every KPI or initiative must connect directly to a top-level strategic objective. In reality, organizations operate across multiple layers, and some department-level improvements may not have a direct link to corporate strategy. A finance team may focus on improving the closing cycle, an IT function may modernize internal infrastructure, or procurement may pursue supplier consolidation. These initiatives can still appear in the X-matrix because they support departmental performance, even if the connection to strategic objectives is indirect.
The purpose of the X-matrix is therefore not to force every activity into the strategy narrative. Its role is to make the most important strategic objectives, measurable signals, and transformative initiatives visible in one coherent structure while allowing necessary operational work to coexist around them.
Conclusion
The effectiveness of an X-matrix ultimately depends on clarity. Objectives should be specific enough that success can be judged. KPIs should measure outcomes rather than activity. Projects should deliver tangible changes that accelerate or enable strategic progress. When these elements are defined with discipline, the X-matrix becomes more than a planning tool. It becomes a practical system that connects strategic intent with concrete action across the organization.
When these relationships are managed in slides and spreadsheets, they quickly decay. A KPI might improve, but the linked objective has already shifted; a project still reports green, yet contributes to an obsolete goal. The result is an illusion of control, accurate reports on disconnected efforts.
We’ve been using the Amplon X-matrix tool for our 500-person organization over the past two years. It has significantly enhanced clarity. Now, we have an easily accessible clear view for everyone of our long-term goals, annual objectives, and development topics both at the organizational level and within each activity.
Moreover, the Amplon team’s responsiveness and support have been outstanding. Overall, Amplon X-matrix has been an invaluable asset for our organization.
Ari Hyvärinen,
ABB Drives Oy
