DF
Feldman AdvisoryFounder Operating Platform
Weekly operating intelligence

Know which numbers need a conversation.

Build a balanced scorecard from drivers to outcomes, enter weekly actuals, and turn exceptions into Issues your leadership team can solve.

Scorecard healthNot ready
0/100
Add metrics across all four dimensions.
Weekly metrics0
5–12 is usually enough
On track0
Green this week
Exceptions0
Need a decision
Issues created0
Ready for L10

Balance check

A scorecard is only balanced when it connects activity, execution, customers, and financial outcomes.

This week at a glance

The exceptions are the agenda—not every number.

MetricOwnerTargetActualStatusTrend
Feldman coaching: A scorecard is not a reporting archive. If a number cannot change a decision, trigger a conversation, or reveal a problem early, it does not belong here.
Scorecard architecture

Choose the vital few.

Start with outcomes, then identify the weekly behaviors and operating signals that predict them. Keep one accountable owner per number.

Add a custom metric

Use a metric the library does not include.

KPI library

Select metrics, then assign owners and targets in the scorecard below.

0 selected
Upstream → downstream: Activity predicts Operations. Operations shapes Customer outcomes. Customer outcomes produce Financial results.

Your scorecard

One owner, one target, one weekly definition.

MetricDimensionOwner initialsTargetDirection
Weekly scorecard run

Week ending

Enter the facts first. Explain only the exceptions.

The operating rule: Green numbers are acknowledged and left alone. Red numbers are clarified, owned, and either corrected immediately or elevated as an Issue.
MetricOwnerTargetThis weekStatusAction
L10 connection

Exceptions become Issues.

Not every miss deserves a debate. Elevate repeated misses, unclear ownership, broken assumptions, and constraints the team must solve.

Ready for IDS

Scorecard Issues queued for the next L10.

Issue quality check

Identify the real issue before discussing solutions.

What changed?State the observable fact, not the story around it.
Why does it matter?Connect the miss to customers, cash, capacity, or strategic execution.
What is the root constraint?Process, person, priority, capability, or assumption?
What decision is required?A strong Issue ends with a decision, owner, or next experiment.
Leadership brief

Your weekly operating signal.

A decision-oriented summary for the leadership team—not another data dump.

Executive readout

Build your scorecard to generate the brief.

Once weekly actuals are entered, this page will summarize balance, exceptions, priorities, and the conversation the team needs to have.

Operating confidence
0/100
Insufficient operating signal

What the numbers say

Recommended leadership agenda

Next operating move: Take the red metrics and unresolved Issues into the L10. Leave with decisions, owners, and dates—then see whether the numbers respond next week.
Saved
Feldman Advisory Free tool from Danny Feldman. Want help putting this to work in your business? More free tools Talk with Danny →