Most weekly business reviews are performed and then forgotten, according to Dr. Connor Robertson, founder of Elixir Consulting Group and host of The Prospecting Show. Numbers get discussed, the meeting ends, and nothing changes. In his framing, a well-designed weekly review is the mechanism by which a business course-corrects on a seven-day cycle, fast enough to prevent drift, slow enough to avoid creating noise.
The One Job a Weekly Review Has
Robertson argues a weekly review has exactly one job: to surface the gap between where a business planned to be and where it actually is, and to generate a specific decision about that gap. If, in his assessment, the review does not consistently produce at least one changed priority, one shifted resource, or one new decision every week, it is not a review; it is a meeting that costs an hour.
The Five Numbers That Matter
Robertson recommends against tracking 20 metrics, suggesting five instead: one revenue or pipeline number, one operational performance number, one client satisfaction signal, one team capacity indicator, and one forward-looking leading indicator. In his view, everything else is a distraction from acting on what matters, and the discipline should go toward removing metrics from a review rather than adding them.
The Four-Question Structure
Robertson’s structure runs every review through four questions: What was planned for the week? What actually happened? What is the gap between those two things, and what caused it? What is changing next week as a direct result? He recommends documenting the answers every week and reading the prior week’s answers before looking at the current numbers, building the accountability loop into the questions themselves.
How Long Should It Take
A well-run weekly business review for a growing company should take 30 to 45 minutes, not two hours, according to Robertson. When it runs longer, he attributes the most common causes to too many metrics that no one will cut, too many attendees turning the review into a status meeting, or insufficient preparation, where the dashboard is being built during the review rather than before it.
Making the Data Automatic
Robertson describes the ideal weekly reviews as ones where data pulls automatically before anyone sits down: a CRM populating pipeline numbers overnight, an accounting tool feeding revenue figures in real time, a project management tool calculating completion rates and updating the dashboard. Participants arrive at a pre-populated view of the business, in his framing, and spend the meeting making decisions about what they see rather than building the picture from scratch.
The Difference Between a Review and a Status Update
Robertson draws a sharp line between the two. A status update, in his framing, is a recitation of what happened; a review is a decision-making process that uses what happened as its input. The distinction matters because most businesses already have the numbers, pipeline reports, and revenue dashboards, and task completion rates exist in nearly every company past a certain size. What’s missing, he argues, is the discipline to convert those numbers into a specific change of plan every single week, rather than nodding at them and returning to whatever was already in motion.
About Dr. Connor Robertson
Dr. Connor Robertson is an entrepreneur, author, and strategic advisor based in Pittsburgh. He is the founder of Elixir Consulting Group, host of The Prospecting Show, publisher of The Pittsburgh Wire, and founder of The Grant Finder. He is also a six-time published author, with titles including Built to Run, available at
drconnorrobertsonbooks.com. More on his work is available at drconnorrobertson.com.
