Questions to Ask for a Balanced Scorecard
For a manager, strategy lead or consultant building or reviewing a balanced scorecard with a leadership team. The questions follow the order of a workshop: the financial, customer, internal process and learning and growth perspectives first, then measures and targets, then owners and reviews, ending with a few that check whether the scorecard is being used or only reported.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Financial
What does financial success look like for us in three years, in numbers?
Why ask it
A good answer picks a few figures, such as revenue, margin or cash, and says which one wins when they pull against each other. If the room offers only 'growth', ask growth of what and at what cost. In a business the other three perspectives exist to deliver these figures, so do not move on until the room agrees on them.
Is this strategy mainly about growing revenue, improving productivity, or both, and in what balance?
Why ask it
Growth shows up in measures of new customers, products and markets, productivity in cost per unit and how hard the assets work. A team that answers 'both equally' has usually not chosen, so ask which one they would protect in a bad quarter.
Where will the growth come from: new customers, current customers buying more, new products or higher prices?
Why ask it
Each source points to a different customer objective: winning new accounts, keeping the ones you have, or taking a larger share of what they spend. Worry when the growth target is firm and its source is 'all of the above'. Have them split the target across the sources, even roughly, and see whether the pieces add up.
Which costs or assets do we need to use better, and by how much?
Why ask it
'Reduce costs' with no object tends to become an across-the-board cut that hurts the very processes the strategy relies on. Hold out for something specific, such as inventory days, the cost to serve a customer or how full the plant runs, and expect it to reappear as an objective under internal processes.
Which financial number would show us earliest that the strategy is not working?
Why ask it
Annual profit arrives too late to act on. Look for something that moves monthly, such as order intake, average selling price or revenue from recently launched products. If the room has no candidate, the financial perspective is a history report and the early warning has to come from the other three.
Which financial results do owners, lenders or funders hold us to, and are they on the draft?
Why ask it
A loan condition, a grant requirement or a budget ceiling can outrank any target the team chooses, and what applies differs by organization and by agreement, so ask the finance lead what binds you here. A figure like that left off the draft will overrule the scorecard the first time the two disagree.
What sits at the top of our scorecard: a financial result or the mission?
Why ask it
One for nonprofits, public bodies and other organizations that exist for a mission, which often put the people they serve at the top and treat money as the means or the limit. A worrying answer puts the budget on top because the template did. A company run for profit can skip it.
Customer
Which customers is this strategy built for, and which will we stop chasing?
Why ask it
Customer measures mean most when they are taken on the target group, since an average across everyone hides whether the chosen customers are happy. Silence on the second half means the segment has not really been picked. Ask sales which accounts they would turn away, and note how the room reacts.
Why would those customers pick us over the alternative: price, quality, speed, service, or something else?
Why ask it
This is the promise the internal processes will have to keep, so it needs to be one or two things and not five. A team that claims the lowest price and the best service at once tends to write objectives that contradict each other.
What do we want those customers to say about us that they would not say today?
Why ask it
Write the answers on the wall as quotes: the gap between today's sentence and the wanted one is the customer objective, in the customer's words. If every quote is something customers already say, the strategy asks nothing new of this perspective.
How do we find out what customers think today, and how often?
Why ask it
Before choosing a satisfaction or loyalty measure, learn what already exists: a survey, complaint logs, renewal data, account reviews. A once-a-year survey can sit on a scorecard, but it cannot guide a quarterly review. 'Sales tells us' is the answer to worry about, because that view comes filtered through people paid on the sale.
Which customers do we make money on, and which cost more to serve than they bring in?
Why ask it
Finance may only know profit by product, not by customer, and in that case a rough estimate for the ten largest accounts is enough to start. A prized account that loses money once discounts, special handling and support are counted changes who the target customer is. It is also the check that stops a satisfaction score from being bought with margin.
What do customers complain about most, and does anything on the scorecard so far deal with it?
Why ask it
Bring the actual complaint categories if you can get them. When the top complaint is late delivery and nothing on the scorecard touches delivery, it was written from the inside looking out. A team that does not know its top complaint has found its first data gap.
If customer satisfaction rose and revenue stayed flat, what would we conclude?
Why ask it
It tests whether the team believes its own chain of cause and effect. Good answers name what might be wrong: the wrong customers surveyed, satisfaction with something they will not pay for, or a lag that needs another year. A shrug suggests the customer measures are there because scorecards have them.
Who else counts as a customer here: distributors, internal departments, regulators, the community?
Why ask it
Support functions, public agencies and companies that sell through partners often have more than one group to satisfy, and the perspective can be split or renamed to fit. Settle it before measures are chosen, because a score that blends an end user with a reseller means nothing to either.
Internal processes
Which three or four processes have to be excellent for us to keep the promise we just made to customers?
Why ask it
The discipline is in the small number. Every department will argue that its process is critical, and a list of twelve is an operations dashboard, not a strategy. Hold each candidate against the customer answers: if it does not deliver the price, quality, speed or service that was promised, it stays off.
Between an order coming in and the customer being satisfied, where do we lose the most time, money or quality?
Why ask it
Have someone sketch the steps on a whiteboard and mark where work waits, which is often at a point no single manager owns. Where the leaders' account differs from that of the people doing the work, measure it for a month before writing an objective.
Which process would customers notice first if it failed tomorrow?
Why ask it
A quick way to rank when the group cannot agree on what is critical. It tends to bring up dull, essential things such as billing accuracy or order status that nobody thought strategic. Those may belong on the scorecard, or on a separate operational report that the scorecard assumes is under control.
What does the strategy need us to do that we do not do at all today?
Why ask it
Scorecards built from existing reports only measure existing work. If the strategy calls for a new channel, a new service or a new market, some process for it has to appear here, even if the first measure is just a milestone date. No answer at all suggests the strategy is this year's operations with a new title.
How does a new product or service get from an idea to a paying customer here, and how long does it take?
Why ask it
If growth was said to come from new products or services, this is the process the financial answer rests on, and the room should be able to describe the path and roughly time it. When it cannot, start by timing the next launch from approval to first sale.
Where do handoffs between departments slow things down or drop things?
Why ask it
Each unit can hit its own target while the customer waits, and a measure that spans departments, such as total time from quote to delivery, is what shows it. If the talk turns to whose fault a delay is, name a joint owner now and save the argument at the first review.
Which safety, compliance or regulatory processes belong on the scorecard, and which belong on a separate dashboard?
Why ask it
What has to be monitored and reported depends on the industry, the regulator and the country, so ask the compliance or legal lead how it works here instead of guessing. One common approach keeps the scorecard for what the strategy changes and tracks the must-not-fail items elsewhere. Put one on the scorecard only if the strategy depends on being better at it than others are.
Learning and growth
What do our people, systems and culture have to be capable of for those processes to work?
Why ask it
The answers tend to fall into three piles: skills, information and the way people work together. A room that offers only training courses has covered the first pile, so ask what staff would need to see on a screen, and which habit would have to change, before moving on.
Which jobs are critical to this strategy, and how many of the people in them are ready?
Why ask it
A handful of roles usually carry the strategy, such as account managers in a retention push or engineers in a product one. Counting who in those roles has the skills needed gives a readiness measure far more useful than training hours for everyone. If the team cannot name the roles, go back to the process list and ask who does that work.
What do people need to know or see that our systems do not give them today?
Why ask it
A frontline employee asked to improve retention needs to see which customers are at risk. Listen for concrete missing things: a customer history on one screen, cost by product, a daily quality figure. The answer becomes a technology objective with a date, and it often turns out to be what is holding up a process measure.
Which habit or part of the culture would have to change for the process objectives to be met?
Why ask it
Ask for behavior people could see, such as sharing bad news early or passing a customer to another division, and not a value word. Culture is hard to measure, so the group may settle for a survey item or a count of the behavior. If the room goes quiet, ask why the process problems have lasted this long.
How would we know whether people understand the strategy well enough to act on it?
Why ask it
A survey item or a manager's guess is the usual answer. A stronger test is to ask a sample of staff to name the top priorities and compare their words with the scorecard, starting with the leaders who are sure everyone already knows.
What do we reward and promote people for now, and does it match what the scorecard asks for?
Why ask it
If bonuses follow volume and the scorecard asks for retention, people will follow the bonus. Ask HR for the real criteria, not the stated values. Treat this as a check on alignment and not a recommendation to change pay, which depends on contracts and local rules the workshop cannot settle.
What do we know about morale and turnover in the teams this strategy leans on?
Why ask it
A company-wide engagement score can look healthy while the one team the strategy depends on is leaving. Ask for the figures by team or role, where the groups are large enough to keep answers anonymous, and find out whether the data exists at all before a target is written against it.
How much time and money goes into training today, and on what?
Why ask it
Training hours are the easiest learning measure to collect and one of the weakest, since they count effort and not ability. Use the answer to see whether spending lines up with the critical jobs named earlier. When most of it goes to mandatory courses, the strategy's skills are being built with whatever is left.
Measures and targets
For each objective, what is the one measure that would tell us we are getting there?
Why ask it
Agree on the objective in words before anyone proposes a number, or the group will bend the objective to fit data it already has. One measure per objective is a starting discipline; allow a second only when the first can be met in a way that misses the point. An objective no one can measure may be a slogan.
Can we draw a line from every measure up to a financial or mission result, and say the reasoning out loud?
Why ask it
This is the strategy map: skills support processes, processes deliver for customers, customers produce the result. Have one person talk through each chain as 'if this improves, then that should'. A measure that links to nothing above it is either operational housekeeping or a sign that an objective is missing.
Which measures tell us what already happened, which tell us what is coming, and do we have both in each perspective?
Why ask it
Lagging measures such as revenue or retention confirm a result after the fact. Leading ones such as on-time delivery or proposals sent move earlier, while there is still time to act. A draft made only of the first kind cannot steer anything, and one made only of the second cannot show whether the theory was right.
How exactly is each measure defined, so two people working it out would get the same number?
Why ask it
'Customer retention' can mean accounts or revenue, over a year or a quarter, and the difference can turn a green into a red. Write down the formula, the data source, how often it is taken and who produces it, so the review meeting argues about the result and not the arithmetic.
Do we already collect the data for this measure, and if not, what would it take to get it?
Why ask it
Sort the draft into three piles: reported today, obtainable with some work, and not available. A few in the last pile are healthy, because they show the strategy is asking for something new. Give each a named person and a date, and show it as 'not yet measured' in the meantime so it is not forgotten.
How could someone hit this number while making things worse?
Why ask it
Call time can be cut by hanging up, and on-time delivery can be met by quoting longer dates. When the group finds an easy way to game a measure, pair it with a second one that catches the side effect, or choose another.
If we could keep only half of the measures on the draft, which would stay?
Why ask it
Give each person a few votes and see what survives. What falls away is not deleted; it goes back to departmental reports. Push back if the group refuses to cut, because a long scorecard gets reported and a short one gets discussed.
How many measures sit under each perspective, and which one is thin?
Why ask it
Count them on the wall. Drafts often come out heavy on financial and process measures, where the data already exists, and light on learning and growth, where it does not. The four do not need equal numbers, but a perspective holding one vague measure is the part of the strategy nobody has worked out yet.
What is on the draft because we already report it, and not because the strategy needs it?
Why ask it
Familiar measures feel safe and arrive on time, so they creep in. Go down the list asking which objective each one serves, and be suspicious of a draft that looks like the current monthly pack under four new headings.
Where does each target come from: last year plus a bit, a benchmark, or what the strategy needs?
Why ask it
Work backward from the financial goal: if revenue must reach a certain level, what retention does that require, and what delivery performance does that retention require? Targets set that way hang together. Targets set one by one from last year's figures often add up to less than the goal at the top.
Which project will move each measure, and is it funded and staffed?
Why ask it
A target with no initiative behind it is a hope. List current projects next to the measures and look both ways: measures with no project, and projects that support no measure. The second group is where the budget for the first can often be found.
Owners and reviews
Who owns each measure by name, and can that person actually move it?
Why ask it
A name, not a department. Then check authority: an owner who needs three other functions to act must have their agreement on record, or the measure needs a different owner. Be wary when the person who compiles the figure is listed, since reporting a number and being answerable for it are two jobs.
Who pulls the numbers together each period, and how soon after it closes will we see them?
Why ask it
A scorecard that lands six weeks after the month it covers gets reviewed as history. Name one person to assemble it and ask which figure holds up the rest, since one measure waiting on a manual count can delay the whole page. A plain spreadsheet is enough to find that out before anyone prices software.
How often will the leadership team review the scorecard, and in which meeting?
Why ask it
It needs a standing slot, with the scorecard as the agenda and not an appendix after the budget review. Monthly or quarterly can both work, depending on how fast the measures move. If the answer is 'we will circulate it', expect it to be read by its author and nobody else.
When a measure turns red, what happens next and who decides?
Why ask it
Settle this before the first red appears. A workable rule is that the owner brings a cause and a proposed action, and the group decides whether to help, wait or change the target. Watch for a habit of punishing red: owners soon learn to set easy targets or redefine the measure.
How will department and team scorecards connect to this one?
Why ask it
Each unit should be able to point to the top-level objectives it contributes to and pick its own measures for them, not copy the ones above. Go one level at a time, and treat a support function with nothing to connect to as a sign the top scorecard skipped something.
Will scorecard results be tied to pay or bonuses, and if so, when?
Why ask it
That is a decision for the employer, shaped by contracts, pay policy and local rules, so ask HR how it works here before promising anything. One cautious route is to run the scorecard for a cycle or two first and find the measures that are badly defined or easy to game. Money tied to an untested measure turns every review into a negotiation.
When did a number on this scorecard last change a decision or move money?
Why ask it
The plainest test of whether a scorecard is used or only reported, and one to ask at a review six or twelve months in. A good answer is a specific case: a project stopped, a budget shifted, a hire brought forward. If nobody can recall one, watch whether the meeting discusses the numbers or only reads them.
Which measures have been green all year while the result they were meant to drive has not moved?
Why ask it
Either the target was too easy or the link between the two was wrong, and both are worth knowing. A scorecard is a set of guesses about cause and effect, and a year of data is the first chance to check them. Treat a broken link as a finding about the strategy and not as someone's failure.
What has changed in the strategy since the scorecard was built, and has the scorecard changed with it?
Why ask it
Set a yearly point to revisit objectives and measures, and a rule for changes in between so they are not made quietly. Measures that never change while the business does are being kept for the trend line. Constant mid-year changes are the opposite problem, usually owners escaping a red.
Who outside the leadership team has seen the scorecard, and could they say what it means for their job?
Why ask it
Ask a few managers two levels down and compare what they say. Sharing the objectives and the map does not mean sharing every figure, so one confidential number need not keep the rest hidden. When the honest answer is 'nobody', the scorecard is a board report.
How to run the balanced scorecard conversation
Practical guidance for the conversation itself
Before the workshop
Start from the strategy, not the template
A balanced scorecard, the framework Robert Kaplan and David Norton set out in the early 1990s, translates a strategy into objectives and measures under four perspectives. It cannot supply the strategy. If the leadership team has not agreed on what it is trying to do and for whom, spend the first session on that and bring these questions to the second.
Bring the numbers people already look at
Collect the current monthly reports, the complaint log, any survey results and the list of live projects. The questions under Measures and targets go faster with the paper on the table, and the gaps in the pile are a finding in themselves.
Get the owners in the room
The people who will own the measures have to be there when they are chosen. A scorecard drafted by a strategy lead or a consultant and presented for approval tends to be agreed to politely and then ignored. Finance, sales, operations and HR each hold most of the data for one perspective, so a missing function leaves a thin column.
Ask yourself the questions first
Go through the list alone and write your own answers. Where you cannot answer, you know what to listen for. Where you are sure, treat your answer as a guess to be tested, since the point of the workshop is to hear where the leaders disagree with one another.
In the workshop
Work down the perspectives in order
Financial or mission results first, then customers, then internal processes, then learning and growth. Each group of questions takes its starting point from the answers above it: the processes that matter are the ones that keep the customer promise, and the skills that matter are the ones those processes need. Starting at the bottom produces a list of things people wanted to improve anyway.
Collect answers separately before discussing
For questions such as which customers the strategy is built for, have each person write an answer before anyone speaks. If seven leaders write seven things, that disagreement is the work of the session. Discussing first lets the most senior voice set the answer.
Objectives in words before measures in numbers
Finish the four perspective groups and agree on a short objective for each answer before opening Measures and targets. Groups that jump to measures early argue about data sources and lose the thread of what they were trying to achieve.
Park operational measures without throwing them away
Someone will defend a measure that matters to running the business and has nothing to do with the strategy. Keep a visible second list for those and say where they will be reported. People let go of a favorite measure more easily when it has somewhere else to live.
Spread the work over more than one session
Four perspectives, measures, targets and owners are too much for one afternoon. One workable split is perspectives and objectives in the first session, measures and targets in a second once people have checked what data exists, and owners and review rules in a short third.
Keeping it in use
Run the first reviews as tests of the scorecard
In the first few cycles, expect measures that cannot be produced on time, definitions that turn out to be ambiguous and targets that were guesses. Fix them openly. A team that treats early problems as flaws in the tool, and not in the people, keeps reporting honestly.
Talk about the links, not each number in turn
Reading down the scorecard line by line takes the whole meeting and decides nothing. Pick the two or three objectives that are off track, follow each up and down its chain on the strategy map, and spend the time on what to do about them.
Return to the last group on a schedule
The final four questions under Owners and reviews are written for a scorecard that is already running. Put them on the agenda once or twice a year: whether a number changed a decision, which greens did not produce results, whether the strategy has moved, and who beyond the leadership team has seen it. If you have been asked to review a scorecard someone else built, start with those four and go back through the perspectives only where the answers show a break.
Mistakes to avoid
Filling in four boxes
A scorecard with five measures neatly under each heading and no links between them is a sorted list of indicators. The value is in the argument that connects the perspectives, so a draft that cannot be told as a story from bottom to top is not finished.
Too many measures
Every extra measure thins out attention and adds a data chore. When the list grows, ask which half the team would keep if it had to choose. What comes off goes to departmental reporting, where it probably was already.
Only measures that look backward
Financial results and annual surveys tell you how the last period went. Without measures that move earlier, the review meeting can only explain the past.
Using it only to hold people to account
Used purely as a control, a scorecard teaches owners to manage the number. Used to test whether the strategy is working, it invites bad news early. How the leaders respond to the first red measure sets which of the two it becomes.
Copying another organization's scorecard
Published examples are useful for seeing the format. Their objectives belong to someone else's strategy, customers and constraints. Borrow the layout and answer the questions yourself.