The Alinement Brief · Issue #14
Installing the Rhythm in a Team That's Never Had One
By Terry Smith, CPA/CITP · August 25, 2026
Years ago, we made a scoreboard out of poster board. One for each department. Every week, we updated the boards by hand with progress toward each department’s priorities. And our teams were fully engaged.
Since then, I’ve installed far more sophisticated systems. Software, dashboards, automated everything. I have never seen one work better than that poster board. Not because paper is magic, but because those boards had the two things that matter: everyone could see them, and they came back every week.
Printing the Pages Is the Easy Part
Last week’s issue summarized the entire operating rhythm on a single page. It covered five tools, a weekly schedule, and eighty-five minutes per week for the busiest role. If you went through it and printed the pages, you’re already ahead of many owners.
You are positioned precisely where rollouts end.
The rhythm holds steady at the start, but falters by week three. That is when the scoreboard first exposes someone’s shortcomings.
The Week Someone Looks Bad
This is how the week unfolds. A department head enters the weekly meeting, and their line on the Priority Scoreboard shows as at risk. This happens in front of their colleagues. It might be the first time in the company’s history that a delayed priority is openly visible to everyone at once.
How the room responds in that moment determines whether you establish a functional rhythm or end up with just wall decoration.
When the initial at-risk label is seen as a judgment on the individual, all subsequent statuses simply indicate being on track. People quickly grasp the true lesson: the scoreboard functions like a courtroom. Within a month, the entire board shows on track, even though none of it reflects reality, rendering the scoreboard useless. It didn’t fail; people discarded it as a means of self-protection.
The solution is determined ahead of the rollout, not spontaneously. A status reflects the progress of the work, not the individual. When something is marked as at risk, it signals that this priority requires a decision from those present. It does not imply that anyone is underperforming. No one is quitting, and no one is being negligent. The scoreboard’s purpose is to direct issues to those who can resolve them while there is still an opportunity to intervene.
Installing Without the Shock
Five rules that make the difference.
Introduce habits in sequence, focusing on one at a time. The sequence designed in the series is effective: start with the Snapshot, follow with the scoreboard, and then the meeting. Maintain these three for a month before incorporating the cash forecast, and later the AI card. Over two months and five pages, each habit builds upon the last. Trying to implement all five in a single week feels like a crackdown and prompts teams to resist.
Brief every owner in private first. Nobody should learn the rules of the scoreboard in public. Before the first board goes up, sit with each priority owner alone: here is what at-risk means, here is what happens when you post one, here is what will never happen when you post one.
Designate the initial two weeks as a calibration phase. Although an at-risk status will be reviewed and factored into decisions, it must not negatively impact the individual who posted it during these two weeks. Make this clear before the first board is published, and honor this commitment the first time it is challenged.
Start by placing your own at-risk status on the board. When you, as the owner, are the first to acknowledge being at risk, you demonstrate that the scoreboard is trustworthy at the one level that truly matters. If your updates consistently show you’re on track while you encourage the group to be honest, the group will get mixed messages.
Avoid redesigning the form the first few weeks. Maintain consistent columns, statuses, and timing for at least three months. If the form changes weekly, it signals to the team that the system is still experimental, and no one commits to an experiment.
If the Business Is Not Yours
Some of you support other business owners. You are fractional CFOs, consultants, or accountants tasked with bringing structure to a client’s Monday. Having spent years in that role myself, I’ve noticed you need three distinct approaches when the business isn’t your own.
You can control the schedule, but not the flow. If a meeting occurs solely because you arranged it, the momentum disappears once you’re gone. During the first eight weeks, your role is to manage the schedule: set the time, prepare the materials, maintain the structure. After that, your goal should be to make yourself redundant, so the meeting can continue without you.
The owner’s at-risk status goes up first, but you don’t have the authority to assign it yourself; you can only request it. If the owner refuses to present the team with a truthful at-risk status, pause the rollout and address the issue directly, since the team will quickly see nothing has changed and every status will be moved to on track and their voices will be silenced.
And your success has exactly one test: the meeting runs the same in the weeks you are not in the room.
The Test
Three questions before your rollout, or in the middle of a struggling one:
- Has every priority owner heard, in private and before their first status went up, what at-risk does and does not mean?
- When the first bad week came, did the at-risk status turn into a decision, or into a defense?
- If the person who started the rollout missed two weeks, would the meeting still happen on time, with the pages updated?
If any answer is no, the tools are not the problem. The install is.
That poster board worked because nobody feared it. The teams were engaged because the board asked about the progress of the work, never of anyone’s standing in the room. Paper, a weekly habit, and safety. That is the whole process.
You can find the one-page rhythm sheet that combines all five tools into a single weekly plan at alinement.com/brief/tools/operating-rhythm.
If you’ve seen a scoreboard rollout fail, what do you think was the cause: the tool itself or just a rough first week? Share your thoughts.
P.S. Next week is the fall kickoff. September works like a second New Year in an owner-led business. We will run a symptom check across the whole toolbox: which of the five tools your team needs first, based on the symptoms you can already see.