The "What Should I Do Next?" Engine: Why Business Leaders Are Asking the Wrong Question About Data
Beyond Dashboards: A New Operating Logic for Commercial Decision-Making
There is a quiet crisis playing out inside commercial organizations right now. It does not show up on a P&L. It does not trigger an alarm in your BI tool. But it is costing companies millions in missed opportunities, delayed responses, and frontline paralysis every single quarter.
The crisis is this: we have built the most sophisticated data collection infrastructure in the history of commerce, and yet the most common question asked in sales meetings, category reviews, and operations calls remains the same as it was twenty years ago.
“So... what do we do now?”
We have more data than ever. We have less clarity than ever. And the gap between the two is not a data problem. It is an architecture problem.
The Dashboard Trap
The conventional response to commercial complexity has been to build better dashboards. More granular. More real-time. More visually compelling. The assumption is that if leaders can just see the data clearly enough, the right decisions will follow naturally.
This assumption is wrong.
What dashboards produce is not clarity. They produce awareness without direction. A well-built dashboard tells you that SKU velocity dropped 12% in a key account last week. It does not tell you whether that is a pricing problem, a distribution problem, a promotional timing issue, or a competitor move. It gives you a signal and then leaves you standing in front of it, waiting for insight to arrive on its own.
The result is analysis paralysis. Teams spend hours in meetings reviewing the same charts, debating interpretations, and circling back to questions that should have been answered in minutes. The data is present. The decision is absent. And by the time consensus forms around an action, the window to act has often already closed.
Raw data, without a system to translate it into directed action, is not an asset. It is a liability. It consumes attention, generates noise, and creates the illusion of informed management while the real work of decision-making gets deferred, delegated, or avoided entirely.
The Real Problem: Closing the Loop
Most commercial organizations have invested heavily in the input side of the intelligence equation. They track sell-out data. They monitor inventory levels. They capture promotional performance. They receive competitive pricing alerts. The infrastructure for collecting signals is, in many cases, genuinely impressive.
What they have not built is the output side. The part that takes a signal, runs it through a decision logic, and delivers a clear directive to the person or system that needs to act.
This is the real challenge. Not data collection. Not visualization. Not even analysis.
The challenge is architecting a decision system that closes the loop between insight and action, consistently, at scale, without requiring a senior leader to be in the room every time a commercial condition change.
Until that loop is closed, organizations will continue to drown in insights they cannot act on. Frontline teams will continue to improvise responses to market dynamics that should have been pre-solved. And leadership will continue to confuse being data-rich with being decision-ready.
They are not the same thing.
Introducing the NBA Decision Framework
Over the course of working with commercial teams across FMCG, consumer electronics, and retail environments, I developed a framework for thinking about this problem in a way that is both structurally sound and practically implementable.
I call it the NBA Decision Framework. Not because it has anything to do with basketball, but because it maps the three components that any functioning commercial decision system must have: Next Best Action.
The framework operates on three layers, each dependent on the one before it.
Layer One: Inputs
The inputs layer is where most organizations already live. It includes the real-time and near-real-time data streams that describe current commercial conditions: sales velocity by SKU and account, inventory levels across distribution points, promotional uptake rates, competitor pricing shifts, shelf compliance data, and demand signals from digital and physical channels.
These are granular, transactional metrics. They are the language the market speaks moment to moment. The mistake most organizations make is treating the collection of these inputs as the end goal, when it is actually just the beginning.
Inputs without logic are noise. The value of inputs is entirely dependent on what happens next.
Layer Two: Logic Gates
This is the layer that most commercial organizations have not built, and it is where the real leverage lives.
Logic gates are predefined decision rules that connect specific input conditions to specific output actions. They are the “if this, then that” architecture of commercial intelligence. They are built by leaders who understand the business deeply enough to pre-solve the most common decision scenarios the organization will face.
A simple example: IF sales velocity for SKU X drops 15% over a rolling seven-day window AND competitor Y reduces shelf price by 5% or more in the same category, THEN trigger a price adjustment review for SKU X AND send an automated alert to the relevant sales team AND flag the account for priority review in the next commercial meeting.
That rule did not require a manager to be watching a dashboard. It did not require a weekly review meeting to surface the issue. It did not require a chain of emails to establish what happened, why it happened, and what should happen next. The logic gate handled all of that automatically the moment the conditions were met.
The power of logic gates is not that they eliminate judgment. It is that they eliminate the need for judgment on decisions that have already been made. The hard thinking happens upfront, when the rules are being designed. What follows is consistent, rapid execution.
This is the difference between a reactive organization and a responsive one. A reactive organization sees what happened and debates what to do. A responsive organization pre-decides what to do when specific things happen, and executes without friction.
Layer Three: Outputs
Outputs are the prescriptive actions that the framework delivers to the relevant team, system, or decision-maker once a logic gate is triggered. They are not reports. They are not alerts. They are directives.
A dynamic pricing update sent directly to the commercial system. A targeted promotional campaign triggered in response to a competitor move. A stock reallocation order generated when inventory levels fall below a threshold in a high-velocity account. A task assigned to a field team to investigate a compliance deviation on a key planogram.
Outputs should be specific, assignable, and time-bound. They should tell the recipient not just what happened, but exactly what action is required, by whom, and by when. The goal is to eliminate the cognitive load of “what now?” entirely for frontline and mid-level commercial teams, so that their energy goes into execution rather than interpretation.
Why This Matters More Than You Think
The organizations that will win the next decade of commercial competition will not be the ones with the most data. That race is already over, and the gap between leaders and laggards is narrowing quickly as AI technology becomes more accessible.
The organizations that will win are the ones that can translate commercial intelligence into consistent frontline action faster than their competitors. Speed of decision and quality of execution, not sophistication of reporting, will be the defining competitive variable.
The NBA Decision Framework is not a technology solution. It is an operating architecture. It can be implemented with sophisticated AI and machine learning systems. It can also be implemented with well-designed spreadsheet logic and clear process rules. The tool matters less than the thinking behind it.
What it requires is leaders who are willing to do the hard work of pre-solving decisions, committing to decision rules in advance, and building the systems to enforce them consistently. That is harder than building a dashboard. It requires genuine commercial expertise, not just data access. And it produces something that no dashboard can produce: an organization where the answer to “what do we do now?” is already built into the system.
The Question Worth Asking
I want to close with the question I find most clarifying when working with commercial teams on this kind of transformation.
It is not “what data do we need?” Most teams already have more data than they are using.
It is not “how do we improve our dashboards?” Better visualization does not solve the decision architecture problem.
The question worth asking is this: in your organization right now, which commercial decisions are being made repeatedly, causing friction, consuming leadership time, and producing inconsistent outcomes, that could and should be pre-solved?
Start there. Map the decision. Define the inputs that should trigger it. Design the logic that should govern it. Specify the output that should result from it. Then build the system to execute it without requiring human intervention every time.
That is what the “What Should I Do Next?” engine actually is. Not a product. Not a platform. An operating logic that transforms commercial intelligence from a reporting function into a decision function.
The leaders who figure that out first will not just have better data. They will have a better organization.
