Most organizations already have more good ideas than they can act on. Strategic priorities, customer needs, operational gaps, market signals, improvement suggestions from the shop floor. The constraint is almost never a shortage of opportunities.
The constraint is turning them into results you can point at.
In the video below, Colin Nelson sets out the seven foundations that decide whether that happens. The written version follows underneath.
Ask a leadership team what's stopping them from delivering and you'll rarely hear "we've run out of ideas." What you hear instead is some version of the same pattern:
None of these are idea problems. They're system problems. And each one has a cost attached: duplicated effort, capital committed to the wrong things, decisions delayed, execution slower than the market.
It doesn't have to work this way. Ricoh New Zealand put a structured process around improvement ideas from front-line staff and ended up implementing more than 3,500 of over 5,000 submissions — a 70% implementation rate. Their finance director's reasoning was simple: the people doing the work with customers are "the ones who are doing the work with customers" and therefore the ones with the best ideas.
The difference isn't idea quality. It's that someone built a system to get them done.
A Business Performance System is a collection of methods, tools and technology, brought together in a platform, to capture opportunities, prioritize them, execute them, and measure results.
It isn't a new software category and it isn't a replacement for how you run projects today. It's the operating discipline that sits around initiative delivery: how work gets in, how it's judged, who decides, who owns it, and how you know whether it worked.
Seven foundations make it function.
Everything starts with what the organization is actually trying to achieve. Not a statement on a wall—specific priorities that people can point initiatives at. Without that alignment, teams make locally sensible decisions that don't add up to anything at the group level.
Ask yourself: could three people in different departments name the same top three priorities?
Someone has to decide what gets funded, what gets stopped, and what gets scaled. That means a group with real authority, clear criteria, and a cadence fast enough to keep up with the work. Governance that meets quarterly to approve things that needed a decision in March isn't governance.
Swisslog is a good illustration of how much this matters. Participation in their innovation program had fallen away after the initial enthusiasm, employees couldn't see what was happening to their ideas, and campaigns were struggling to build credibility. They rebuilt the program around business-relevant challenges and named executive sponsors. Participation rose from 20 ideas per campaign to 180, 1,200 employees engaged, and the program passed its €380K ROI target. Their innovation manager describes securing an executive sponsor for every challenge as "by far the most important improvement we made".
Not a new tool. A named decision-maker attached to each piece of work.
Ask yourself: what did you stop last quarter, and how long did the decision take?
[Read the Swisslog case study →]
A small operational improvement and a business-wide transformation should not follow the same path. Matching the process to the size and risk of the work is what stops small things drowning in bureaucracy and big things skipping the scrutiny they need. Both failure modes are expensive.
Ricoh's starting position was that continuous improvement lacked structured governance and legacy systems limited idea visibility — a common pairing. Without a defined path, ideas either stall in review or bypass review entirely.
Ask yourself: does a €10,000 improvement go through the same gates as a €2 million program?
This is where most organizations discover the gap. A single view of what's running, what it costs, who's on it, and what it's expected to return. Not just active work — the things you've decided to hold as well, so you know what's waiting when capacity frees up.
The portfolio is where the other six foundations become visible. If you can't see it, you can't govern it.
Ask yourself: can you name your three largest initiatives and what they cost?
Systems don't deliver anything on their own. How you engage people, how you communicate decisions, and whether contributing to improvement is recognized or quietly ignored will determine how much of the system actually gets used.
Swisslog's diagnosis is worth repeating here, because it's the most common one we see: participation dropped off not because people ran out of ideas, but because they had no visibility into outcomes or implementation progress. An idea that disappears into a portal teaches everyone watching not to bother next time.
Done well, the scale can be substantial. UC San Diego invited more than 34,000 faculty and staff at launch, drew over 10,000 contributors into strategic planning, and reached more than 65,000 participants across campus-wide campaigns.
Ask yourself: when someone submits an improvement, do they find out what happened to it?
Customer feedback, emerging technologies, competitor moves, regulatory change. Most organizations collect these somewhere. Fewer have a route by which they reach the people making funding decisions, in time to affect them.
Ask yourself: what changed in your market this year, and which initiative changed because of it?
Suppliers, startups, research partners, and customers themselves. Very few organizations have all the capability they need in-house, and co-creation with the people who'll actually use the outcome shortens the distance to something that works.
Ask yourself: which of your current initiatives involves someone outside the organization?
AI is useful here in specific, unglamorous ways. It can flag duplicate initiatives across business units before both get funded. It can summarize a hundred submissions so a review committee reads signal rather than volume. It can surface patterns across the portfolio that nobody would find manually. It can cut the time it takes to prepare a governance pack from days to hours.
What it doesn't do is make the decisions. The governance, the criteria and the accountability still have to exist. AI applied to a system that doesn't work just produces bad decisions faster.
No organization builds all seven at once, and the right sequence depends on where you are. Most start with the portfolio, because you can't govern or prioritize what you can't see. Others start with governance, because decisions are the bottleneck.
The useful question isn't "which of these do we have?" It's "which one is costing us the most right now?"
What is a Business Performance System?
A collection of methods, tools and technology, brought together in a platform, to capture opportunities, prioritize them, execute them, and measure results.
How is it different from project management software?
Project management tools help you run work that's already been approved. A Business Performance System covers what happens before that — how opportunities are captured, evaluated, prioritized and funded — and what happens after, in measuring whether the result matched the business case.
Do we need all seven foundations?
Eventually, but not at once. Most organizations have some in place and one or two that are actively constraining delivery.
Who owns a Business Performance System?
It varies. Commonly innovation, operations, continuous improvement, strategy or transformation leadership. What matters more than the reporting line is whether the owner has the authority to stop and start work.
How do you measure whether it's working?
By implementation rate and realized impact, not by volume of ideas submitted. The question is what proportion of approved initiatives deliver the result they were funded for.
Get a free assessment of your business performance system
Colin Nelson runs a 45-minute session scoring your organization across all seven foundations. You get a written report with your maturity score, the root causes behind the two or three constraints holding you back, and a prioritized action plan for the next 30 days, 90 days and 12 months.
No preparation needed. It isn't a demo.