# How to Use Consumer Electronics Innovation to Create Meaningful Success Metrics in Manufacturing Platform
A manufacturing platform family business running Scrum with a team of six to fifteen people has a success metrics problem. The company runs a platform that connects manufacturers with raw material suppliers. It handles sourcing, ordering, quality tracking, and logistics coordination. (1/29)
The success metrics are unclear. Shipping features without knowing if they matter means the team measures the wrong things. Measuring the wrong things means the team thinks it is succeeding when it is not. That gap is costing the company sixty-seven thousand dollars per quarter. Twenty-four percent of quarterly revenue.
The success metrics must be made meaningful. (3/29)
Akio Morita built Sony on a consumer electronics innovation. The model was simple. Morita recognized that the biggest problem in business is measuring what is easy instead of what matters. Companies track vanity metrics and think they are succeeding when they are not. Missing real problems kills companies.
Morita attacked the vanity metrics. His principle was straightforward: measure what the customer experiences, not what the company produces. (4/29)
When Morita launched the Walkman, he did not measure units shipped. He measured hours of listening. That told him how customers used the product. He applied the same thinking to the PlayStation. He did not measure consoles sold. He measured games played.
This approach to consumer electronics innovation told Morita whether customers were genuinely engaging. It built Sony. (5/29)
For this manufacturing platform family business, the problem is identical. Unclear metrics mean measuring the wrong things. Measuring the wrong things costs sixty-seven thousand dollars. Morita's model says: measure what the customer experiences. Do not measure what the company produces. Consumer electronics innovation creates meaningful metrics. Meaningful metrics eliminate the loss.
## The Core Principle (6/29)
Morita's approach rested on one insight. Stop measuring what is easy to count. Stop tracking features shipped, stories completed, and bugs closed. Start measuring what the customer actually experiences. Time saved. Problems solved. Value received.
Every metric should connect directly to the customer's reality. That is how the team knows whether shipped features are making a difference. (7/29)
For this manufacturing platform family business, the situation is the same. Unclear metrics mean measuring the wrong things. Measuring the wrong things costs sixty-seven thousand dollars. The fix is the same principle. Measure customer experience. Do not measure company output. That creates meaningful metrics. Meaningful metrics eliminate the loss.
## Four Steps to Apply Consumer Electronics Innovation to Creating Meaningful Success Metrics (9/29)
### 1. Replace Output Metrics with Outcome Metrics
Morita replaced output metrics with outcome metrics at Sony. Tracking customer experience created meaningful metrics. Meaningful metrics built Sony.
Do the same thing. Map every feature to a customer experience. Measure the change in that experience. (10/29)
Here is what this looks like for a manufacturing platform family business. The product owner replaces output metrics with outcome metrics in a two-hour workshop. The workshop has two steps.
Step one is listing the current output metrics. That creates awareness of what the team is actually tracking. Last quarter, the product owner listed five metrics. (11/29)
. Six releases per quarter. None of these five metrics tell the team whether the features mattered.
Step two is mapping each feature to a customer experience. That creates a connection between what was built and what the customer experienced. (13/29)
Last quarter, the product owner replaced five output metrics with five outcome metrics. The team finally saw whether features mattered. The team stopped shipping features that did not matter. That saved nineteen thousand dollars.
For a Scrum team of six to fifteen, run this as a two-hour workshop. Map every feature to a customer experience. Make it part of the sprint retrospective.
### 2. Define a Single North Star Metric (15/29)
Morita defined a single North Star metric at Sony. Hours of listening. It represented the core value. Every product decision aligned to it. That focus built Sony.
The same approach works here. Define a single North Star metric that represents the core value. Align every sprint goal to it.
Start with a one-hour discussion. Identify the core value first. Last quarter, the team landed on this statement: We help manufacturers find the right materials faster. Speed is the core value. (16/29)
Last quarter, the target was to reduce that time from seventy-two hours to forty-eight hours. Aligning every sprint goal to that single North Star metric meant every shipped feature contributed to reducing the time. The metric improved from seventy-two hours to fifty-one. That saved twenty-eight thousand dollars. That was the value of the time manufacturers saved.
Keep it to one metric for a team of six to fifteen. Make it part of sprint planning. (18/29)
### 3. Create a Customer Experience Score
Morita reduced multiple data points into a single number. Hours of listening. That simplicity meant the team could track progress easily. Easy tracking built Sony.
Create a customer experience score. Combine multiple outcome metrics into one number. Track it sprint over sprint. (19/29)
For this manufacturing platform, the calculation is a weighted average of three outcome metrics. Average time from sourcing request to confirmed supplier at forty percent weight. Defect rate reduction at thirty percent. On-time delivery rate at thirty percent.
The score runs from zero to one hundred. Zero is worst. One hundred is best. Calculate it every sprint. (20/29)
Last quarter, the score started at fifty-eight. Below the target of seventy. The team improved it from fifty-eight to seventy-three over three sprints. A twenty-six percent improvement. That saved twenty thousand dollars.
For a Scrum team of six to fifteen, combine at least three outcome metrics into one number. Calculate it per sprint. Make it part of the sprint review.
### 4. Run a Sprint Feedback Loop (21/29)
Morita ran a feedback loop that reviewed data and drove decisions. Deciding based on data built Sony.
Run the same loop at the end of every sprint. Review the customer experience score. Decide whether to continue or pivot the current feature. (22/29)
Last sprint, the score came in at sixty-five. Below the target of seventy. The team pivoted away from a supplier rating system that was not moving the needle. Switched to a supplier verification system. The score jumped from sixty-five to seventy-one. That saved fourteen thousand dollars.
For a Scrum team of six to fifteen, hold this at every sprint end. Review the score. Make a data-driven continue-or-pivot decision. Make it part of the sprint review. (24/29)
## Closing on Outcomes Over Outputs
Akio Morita did not build Sony by measuring units shipped and story points completed and bug counts while hoping those numbers told him whether customers were happy. He replaced output metrics with outcome metrics. He mapped the automated sourcing feature to supplier search time. He mapped quality tracking to defect rates. He mapped logistics coordination to on-time delivery rates. (25/29)
agile