47 Dashboards, Zero Decisions
I walked into a services firm last year and asked the CEO to show me how he tracked the business. He opened his laptop. Forty-seven separate dashboards. Power BI, Google Sheets, his CRM reports, QuickBooks exports, a custom tool one of his ops guys built in Notion.
I asked him how many of those he looked at every week. He said, "Honestly? Zero. I scan a couple on Monday but I don't trust any of them."
That's not a data problem. That's a signal problem. And it's the problem the Pulse was built to solve.
The Pulse is between 5 and 15 numbers. Reviewed every week. Red, yellow, or green. No narrative. No "let me explain why it's red this week." Just the number, the target, and the color. If you can't run your business on something that tight, you don't have a measurement problem — you have too much noise and not enough signal.
What Makes a Number a Signal
Not every metric belongs on the Pulse. Most don't. A number earns a spot on the Pulse only if it meets four criteria.
→ It's weekly-rhythmic. It can be measured every week, not just monthly or quarterly.
→ It's leading, not lagging. Revenue is lagging. Qualified demos booked is leading.
→ It has a target. A number without a target is just data. A number with a target is a signal.
→ It has an owner. One human being is responsible for that signal hitting green.
A signal that fails any one of those four criteria is a dashboard metric, not a Pulse signal. Keep the dashboard. But keep it off the Pulse.
The 5 to 15 Rule
I've built Pulses with as few as 5 signals and as many as 15. Below 5, you're missing visibility. Above 15, no human can hold them all in working memory. The sweet spot for a leadership team at $5M-$30M is usually 9 to 12.
Here's what a typical Pulse looks like for a services company:
→ New qualified leads this week (target: 25)
→ Sales calls completed (target: 40)
→ Proposals delivered (target: 8)
→ New contracts signed (target: 3)
→ Active projects on-time (target: 95%)
→ Customer NPS (target: 60+)
→ Cash on hand in days of operation (target: 60+)
→ Collections over 45 days (target: under $50K)
→ Open roles (target: under 3)
→ Unplanned employee departures (target: 0)
Ten signals. Covers pipeline, delivery, customer health, cash, and people. A leadership team can review this Pulse in 8 minutes flat at the top of every Huddle.
Red Is a Feature, Not a Bug
A Pulse that's all green every week is not actually a Pulse. It's a trophy. It means your targets are too soft, or your team is gaming the numbers, or you're measuring the wrong things.
I tell leadership teams to expect 20-30% red/yellow on any given week. That's the healthy range. Fewer reds means targets aren't stretching. More reds, consistently, means something structural is broken.
When a signal goes red, one thing happens: it goes to the Dock as an issue. Not "let me explain why it's red." Not "we'll work on it this week." It goes to the Dock. The team runs the Build Loop on it in the same Huddle or the next one. The number either comes back to green, gets its target adjusted with a conscious decision, or triggers a bigger conversation about whether the underlying process is broken.
That's the discipline. Red doesn't get explained. Red gets addressed.
The Owner Line
Every signal on the Pulse has exactly one owner. Not a team. Not a department. One human.
This is the line I see violated most often in early Pulse builds. "Sales pipeline" gets owned by "sales." Nobody actually owns it. When the number goes red, nobody's accountable. The Pulse review becomes a diffusion of responsibility — which is worse than no Pulse at all.
The fix is uncomfortable but simple. Every signal gets a named owner. When that signal goes red, the owner is the one who either explains the fix or takes the Build Loop seat for it. No passing the baton mid-Huddle. No "well, Sarah really handles that part." If Sarah handles it, Sarah owns the signal. Full stop.
A Client Story
A construction client I worked with in 2023 had a "scorecard" that was 34 metrics long. They reviewed it monthly. It had been yellow for 18 straight months. Nobody on the leadership team believed in it.
We spent 3 hours at a Recalibration rebuilding it. We cut from 34 to 11 signals. We assigned a single owner to each. We set real targets, not aspirations. We shifted the review from monthly to weekly.
Week one: four reds. Week three: six reds. Week six: two reds. The reds didn't go away because we ignored them — they went away because each red, every week, became a single Dock item that got the Build Loop treatment. Within six months, the company had its first on-time project delivery quarter in 27 months. Not because the team worked harder. Because the team could see.
The Meeting After the Pulse
Here's what I love most about a working Pulse. It kills the "how are we doing?" meeting.
The 90-minute status meeting, where each department head narrates their week while everyone else checks email, dies on the day the Pulse starts working. You don't need to listen to sales narrate when the number tells the story in 15 seconds. You don't need to hear operations explain when the delivery signal is green.
You spend your leadership time on the reds. On the issues. On the Build Loop. The Pulse isn't the scoreboard at the end of the game. It's the radar that tells you where to aim your attention.
A final note that I can't skip. The Pulse gets better over time, which means the first version will feel wrong. Signals you picked in month one will get replaced by month three. Targets that felt right at the start will turn out to be too soft or too aggressive. That evolution is the point — a Pulse you revise every quarter is a Pulse that's being used. A Pulse that looks identical a year later probably isn't informing decisions at all.
Build yours. Build it tight. Trust it. And watch your leadership meetings stop being reports and start being decisions.