The Monday Page That Replaced a Week of Firefighting
A one-page weekly look at pipeline, delivery, cash and people, and why a growing consulting firm needs one.
For a while I thought I was running the company because I was in every emergency. A client was upset, so I joined the call. A deal felt shaky, so I rewrote the proposal after dinner. An engineer was drowning, so I moved them at the last minute. By Friday I was tired enough to believe the week had been well led. It had only been noisy.
Earlier in my career, as a partner, I helped grow a software consulting company from about $6M to $60M in under three years, and later I founded and ran a fully remote consultancy. As the firm got bigger, managing by surprise stopped working. The thing that helped was almost embarrassingly simple: one page, reviewed every week, covering the same four areas. Pipeline. Delivery. Cash. People.
That consulting firm weekly operating rhythm did not make the work easy. It made the important facts show up on time, in one place, before they turned into a scramble.
The Problem Is Not Effort. It Is Delayed Information.
In a growing services firm, the facts already exist. They just live in four different homes. Sales knows what is in the pipeline, or at least what is in their inbox. Delivery leads know which projects are drifting. Someone in finance knows which invoices are late. A manager knows who is close to burning out. Leadership often sees none of it until it is loud.
Ad-hoc meetings feel responsible because they are tied to a crisis. The cost is that quiet problems get no calendar time. A thin pipeline two months out does not ping you. A slow invoice does not interrupt lunch. A strong person who is unhappy rarely puts it in a group chat. Those are the issues that become expensive when you finally notice them.
A weekly page will not prevent every surprise. It gives the non-urgent, high-importance items a regular time to be seen.
Keep the Page Small Enough That It Actually Gets Updated
I have watched firms try to solve this with a dashboard that takes a day to maintain. They use it for two weeks and then go back to Slack. The version that stuck for me was a short document with four headings and an owner for each section. If updating a section takes more than a few minutes, the section is too heavy.
Pipeline should answer whether work is really coming, which deals moved or stalled, and whether we are selling things we cannot staff. It should not be a replay of every sales call.
Delivery should name the engagements that are on track, the ones at risk, and the decision needed this week. A color with no explanation is not a status.
Cash should cover what came in, what is overdue, what is going out and whether a timing gap is forming. This is not a full finance close. It is a weekly check that money problems do not hide behind delivery optimism.
People should cover load, bench, hiring gaps and anyone who may be at risk of leaving. Skip this section and you will eventually ask how you missed a resignation or a burnout that had been visible for weeks.
If an item does not belong in one of those four, park it. The page is not a parking lot for every idea in the company.
Use the Review to Decide, Then Write the Decision Down
The document is the point. The meeting, if you have one, should be short and should happen at the same time every week. In a remote team, people can update the page in writing first and use a brief call only for open decisions. A topic that needs an hour of debate should get its own meeting. This review is not a strategy offsite.
The quality test I use is simple. Can we act? "This account is at risk" is a report. "This account is at risk because the change request is unsigned, and we need a Thursday decision on whether to pause the extra work" is a request for leadership. Bring the second kind.
Then write down who will do what, and start the next week by checking those items first. That follow-through is what slowly replaces firefighting. People stop broadcasting the same warning in three channels once they trust that the item has a home and a close date.
Leave Out the Theater
The rhythm dies when it becomes a tour of everyone's week. Do not walk through every ticket or every lead. Do not add new sections because a function wants airtime. Do not spend most of the review on a single account. Do not track numbers that never change a decision.
And do not skip a week because the page is incomplete. If a section is hard to update, shrink it. A stale page is worse than a plain one, because it creates the feeling of control you do not have.
Begin With a Document, Not a Tool Search
You can start this week. Open a shared page, write the four headings, add what you already know, and book thirty minutes with the people who own sales, delivery, cash and the team. Leave with a short list of decisions. Repeat next week and cut whatever felt like performance.
When this is working, leadership spends less of the week in reactive meetings. True emergencies still get handled the day they happen. Everything else has a place. You also start seeing the connections sooner: a deal that would overload a team, a delivery risk that should change a billing conversation, a people problem that should change what you are willing to sell.
A one-page weekly operating rhythm will not run the firm for you. It will keep pipeline, delivery, cash and people in the same conversation, on a cadence a growing consulting firm can actually keep. That is often enough to move from chaos to something you can steer.
About the Creator
Enjoyed the story? Support the Creator.
Subscribe for free to receive all their stories in your feed.
Comments
There are no comments for this story
Be the first to respond and start the conversation.