How to Roll Out Strategy Execution Software Across Your Organization

How to move from 1–3 strategy users to broader adoption across departments.

A Quick Answer

Start with a prototype, find an internal strategy champion, validate the strategy execution process, and then involve the people who own objectives, KPIs, initiatives, and data inputs.

The goal is to move from performance reporting to performance management.

Why Organizations Often Start With One User

The short answer is: to test the waters.

Even if a platform like BSC Designer has a free plan, there are usually limits. Free accounts require some activity to stay alive in the platform, while a paid account, even with one user, gives the organization a more stable environment for testing.

At this stage, one person is usually:

• Exploring the platform,
• Building a prototype,
• Migrating existing spreadsheets, and
• Checking if the software fits the organization’s strategy process.

What Is the Problem With a One-User Implementation?

With one user, it is usually not strategy execution. It is strategy reporting.

One person cannot realistically manage all inputs, validate all hypotheses, decompose complex objectives, define local goals, track initiatives, update KPIs, and facilitate learning across the organization.

So what does this person actually do?

Usually, they gather data, prepare reports, and present updates to colleagues.

That may be useful, but it is still reporting.

Strategy execution starts when the people responsible for execution are also involved in defining, updating, and reviewing their part of the strategy.

There is also a compliance issue, especially in regulated industries. If one user does all strategy reporting, the same name will appear as responsible for many goals, initiatives, KPIs, their targets, updates. Involving real users as active participants creates a more valid audit trail and better reflects who actually owns the work.

When Is Your Organization Ready to Expand Access?

Almost any organization can benefit from broader strategy participation, but not every organization is ready to expand immediately.

For me, the main readiness factor is the presence of a strategy execution culture: visible habits that show how the team works with strategy.

The two most important habits are:

• The habit of splitting complex ideas into smaller parts — value-based decomposition;
• The habit of “talking numbers” — moving from abstract and vague ideas to something specific, usually through quantification.

Without these habits, adding more users will not help much. The software will remain another reporting tool.

How to Develop These Habits

There is a quote (simplified) attributed to Antoine de Saint-Exupéry:

“If you want to build a ship, don’t start by assigning people tasks and collecting wood; teach them to long for the sea.”

The same applies to strategy execution.

You cannot build a strategy execution culture simply by explaining the desired outcome. People need to experience how a vague strategic idea becomes specific, actionable, measurable, and connected to the overall strategy.

Practical exercises work better than abstract explanations.

For example, a strategy execution workshop (see guidelines for facilitators) can help the team practice decomposition, quantification, KPI design, initiative mapping, and review logic before expanding the platform to more users.

The Role of the Internal Strategy Champion

A successful rollout usually needs an internal strategy champion. This is often the person who built the prototype and learned the key functionality of the platform.

Yes, the software vendor can answer product questions. But every organization has internal context: politics, terminology, existing reports, informal processes, data ownership, and decision-making habits.

Those things are solved much better from inside the organization.

The internal champion does not need to do everything. But they need to understand both the platform and the organization well enough to guide the rollout.

What a Typical Strategy Execution Process Looks Like

To decide who should be involved, it helps to define the strategy execution process.

It will vary by organization, but usually includes:

1. Initial formulation of strategic objectives;
2. Cascading objectives into scorecards;
3. Decomposition into sub-goals, initiatives, and KPIs;
4. Assignment of owners;
5. Regular performance reporting;
6. Review, discussion, approval, and learning loops.

The more mature the process becomes, the harder it is to manage with only one user.

Who Should Be Involved in Strategy Execution?

Start from the end: who will execute the strategy in practice?

Most of these people need to be involved at some level.

This does not mean everyone needs full access. But if a part of the strategy is simply “cascaded” from the strategy office, people often see it as someone else’s strategy.

When they participate in defining their part of the strategy, the attitude changes from “their strategy” to “our strategy.”

The logic of involvement is similar to value-based decomposition: if an objective still feels too broad and needs to be split into smaller parts, involve the people from the level where that decomposition should happen.

Here is an example of involvement according to the user group:

User Group	When to Involve Them	Access Type
Internal strategy champion	From the prototype stage	Admin / power user
Leadership team	When the model is ready for review	View-only user
Department heads	When objectives need decomposition	Power user
KPI and initiative owners	When metrics need regular updates	Power user
Data contributors	When manual updates are required	Power user / data input user
Senior management	When dashboards are reliable	View-only user
Auditors	When evidence is needed	View-only user

For the conceptual model of involvement (awareness, contribution, and collaboration/ownership) see the strategic planning involvement article. In this rollout article, we apply that model to software adoption.

What a Prototype Implementation Looks Like

When an organization is testing strategy execution software, the initial formulation of strategic objectives often happens outside the software.

A typical first attempt is to automate the core part of the strategy process without getting into too much detail.

We often see this led by a CFO, HR leader, strategy office, PMO, or transformation manager. The work may start with creating a simple cascade of scorecards and migrating existing spreadsheets.

The purpose of prototype stage is to find a workable model and identify the internal strategy champion who can lead the next stage.

In some cases, this process is accelerated by an external consultant who is independent from the software vendor.

Who to Involve Next

The step that requires the most intellectual effort is decomposition: turning broad objectives into goals, initiatives, KPIs, risks, and assumptions. This is not a one-time exercise. The team will need to do it continuously.

That is why the next users should usually be the people responsible for decomposing and owning parts of the strategy:

• Department heads;
• Goal owners;
• KPI owners;
• Initiative owners;
• PMO or transformation leaders;
• People responsible for regular strategy reviews.

These users help turn the strategy model into a living system.

Who Should Update the Data?

It depends…

Ideally, data should be automated by connecting directly to databases or business systems. In other cases, it can be semi-automated through Excel imports.

But in many organizations, data is not available in one clean, aggregated format. It still needs to be entered or validated manually.

Those people may need access as well.

They are not always strategy decision-makers, but they are critical to keeping the system updated.

What About Senior Management?

This may sound counterintuitive, but senior managers are rarely power users of strategy execution software. They usually prefer view-only access with full visibility.

Of course, C-level managers are involved in discussions and decisions. But they typically rely on their teams to maintain the structure, update the data, and prepare the details.

For senior management, the most important thing is not editing rights. It is reliable visibility into goals, performance, initiatives, risks, and decisions.

What About Auditors?

Auditors are similar to senior management in terms of access.

If you work in a regulated industry and need to show that controls are implemented and tracked continuously, you will usually do this through reporting functionality or view-only access.

Auditors rarely need to participate in the strategy execution process itself. They need evidence that the process exists, is followed, and can be reviewed.

A Practical Rollout Path

A simple rollout path looks like this:

1. Start with one internal strategy champion.
2. Build a prototype based on existing strategy materials.
3. Validate the structure/logic of objectives, KPIs, initiatives, and ownership.
4. Add department heads and goal owners.
5. Add KPI and initiative owners.
6. Add data contributors where manual input is needed.
7. Involve the leadership or strategy review team.

How Do We Know It Is Working?

Technically, you can see the change in platform usage patterns. People will likely spend more time in the platform, initiating more changes and discussions.

You will also see more “aha” moments within the team. People will become more active in suggesting new goals, or in making existing goals more specific and ready for execution.

Final Thought

Rolling out strategy execution software is about deciding who needs to participate in the strategy process.

If one person uses the platform, the organization is usually reporting (not managing) strategy. To move to strategy management and execution, involve the people responsible for converting vague aspirations into a living system where objectives are decomposed into goals, initiatives, and KPIs.

For the criteria used to evaluate platforms in this category, see our strategy execution software comparison.

Alexis Savkín

Alexis Savkin is a Strategy Architect and founder of BSC Designer, a strategy execution software platform with the Balanced Scorecard at its core. He helps organizations translate strategy into measurable objectives, KPIs, and initiatives. Alexis is the creator of the Strategy Execution Canvas, the author of 100+ articles on strategy and performance measurement, and a regular speaker.