TL;DR
A wins-and-learnings update is the conversation that shapes whether leadership trusts your team’s read on the work. In service businesses, that conversation lives or dies on three numbers: margin, backlog, and utilisation. This guide covers the five-step structure that works, the metrics that matter, the mistakes that weaken every update, and what the conversation looks like when your tools, time, and financials live in one place.
Why Communicating Wins and Learnings Matters in a Service Business
Picture the quarterly review. The agency principal sits down across from the founder and the CFO. They have twenty minutes. They want three things: which clients made money, which ones are at risk, and what calls need to be made before the next quarter starts.
That is the leadership update. Not a status report. Not a list of campaigns shipped. A short, honest read on whether the business is in a healthy place and where the principal needs help.
In service businesses, the stakes are sharper than in product companies. Every hour your team logs is either earning revenue against a contract or eating into margin. Every client either trends profitable or trends underwater. A weak update hides that picture. A strong one surfaces it cleanly enough that leadership can act on the same day.
Done well, the update earns trust, speeds decisions, prevents repeat mistakes, and removes surprises. Done badly, it delivers task lists to people who needed a P&L. The difference is structural, not stylistic.
💡 Pro Tip: The fastest way to test whether your update is leadership-grade is to ask a simple question: if a leader read only the first three sentences, would they know what call to make? If the answer is no, the structure is wrong.
There is a closely related discipline at play here the quarterly execution rhythm that ties weekly work back to leadership priorities. The wins-and-learnings update is the surface where that rhythm becomes visible.
What Leaders Actually Want to Know (Not What Most Teams Send)
A leader running a service business does not need to know how many tasks moved across columns. They need answers to four questions, in this order.
1. What happened?
The outcome, not the process. The campaign launched. The client renewed. The deliverable shipped. State it as a fact, not a story arc. Leaders do not need the meeting count or the tooling backstory.
2. What did it cost or earn?
This is where service-business updates differ from every generic leadership report you have read. A marketing team might celebrate a campaign. An agency has to answer whether the campaign earned revenue against a fixed-fee contract or burned through retainer hours. The financial signal is the win or the hidden loss.
3. What is the risk?
Risk in a service business is not abstract. It is backlog. It is scope drift. It is a client whose margin has dropped to 12% over the last six weeks. It is utilisation slipping below 70% across the team. These are signals leaders can act on if they hear them in time.
4. What is the next call?
The decision needed. The approval requested. The strategic shift on the table. Vague asks get vague responses. “We are noticing pressure on the Sandberg account” does nothing. “Margin on Sandberg has dropped to 14% we need a 30-minute call this week to decide whether to renegotiate scope or accept the lower margin through Q3” gives the leader something to act on.
❓ What is the difference between a status report and a leadership update?
A status report tells leadership what the team did. A leadership update tells leadership what changed in the business and what decision is now in play. Status reports are activity-focused, written for visibility. Leadership updates are outcome-focused, written for decisions. In service businesses, the distinction is sharper because outcomes are financial every status update should be readable as a P&L conversation, not a project log.
The structure below builds every update around those four questions.
How to Communicate Wins and Learnings to Leadership A 5-Step Structure
Most guides teach a six- or seven-step framework that splits closely related ideas across multiple headings. The five steps below cover the same ground without padding.
Step 1: Identify the real win and ground it in the financial signal
A win is not “we shipped the campaign.” A win is “the campaign drove 14% activation, lifting earned revenue against the contracted scope by roughly $42K this quarter.” The first version is an activity. The second is the outcome a leader can use.
The signal to look for is the moment progress became financially or operationally visible. A metric stabilised. A scope-drift pattern resolved. A client who was trending toward unprofitable moved back into healthy margin. A delivery dependency cleared and unblocked downstream work.
If you cannot tie the win to one of those financial, operational, strategic it is not yet a leadership-grade win. It is internal team news.
A common pattern in agencies and consulting firms: the team celebrates a delivery, but the financial story behind it is a quiet scope creep that has eaten into margin. The win is real but partial. Leaders need both halves.
Step 2: Frame the win with outcome, impact, and context together
A leader skims before they read. The opening sentence has to do three things at once: name the outcome, signal why it matters, and gesture at what shifts because of it.
A reliable single-sentence frame:
“Onboarding completion rose 14% in Q1, strengthening early conversion for the Sandberg retainer and supporting the upcoming acquisition push.”
That sentence carries the outcome (14% lift), the financial relevance (retainer health), and the strategic context (the next initiative it supports). A leader can act on it without reading another word. The body of the update then earns the right to add detail.
Step 3: Bring in the metrics that prove it
Three numbers do most of the work in a service-business leadership update.
Margin. Per client, per project. Not just total margin the per-client breakdown is where leadership sees which relationships are funding the business and which are draining it.
Backlog. Signed revenue minus earned revenue. The work you have committed to deliver but have not yet billed against. High backlog is not always bad it can mean a healthy pipeline of committed work but rapidly growing backlog with no delivery plan is a delivery risk a leader needs to see.
Utilisation. Billable utilisation across the team. Below 70% sustained means undercharging or underallocation. Above 90% sustained means burnout risk and quality slippage.
This is where the update either lands or stays generic. Most teams cannot pull these three numbers in one place because their tools sit in silos project management in one tool, time tracking in another, financials in a spreadsheet. The update becomes a manual reconciliation exercise, which is why it gets watered down to activity reporting.
The shift comes when the data lives in the same surface as the work. In Skarya, the CFO Dashboard pulls signed revenue, earned revenue, cost, margin, backlog, and risk per client into one live view populated automatically from board contract values, approved timesheets, and resource hourly rates. The leadership update stops being a report-writing task and becomes a screenshot conversation.
Activity-based reporting versus outcome-based reporting
| Activity-based update | Outcome-based update |
|---|---|
| “Team completed 47 tasks this quarter” | “Earned revenue rose 12% on the Sandberg retainer” |
| “Three campaigns launched in March” | “Campaign work brought retainer margin from 18% to 26%” |
| “Sprint velocity stable at 32 points” | “Delivery pace held backlog reduced by $48K against signed scope” |
| “Five new clients onboarded” | “New client revenue: $180K signed, $42K earned, $138K backlog to deliver in Q2” |
The activity column is what most teams send. The outcome column is what leadership actually needed.
Step 4: Share learnings in a forward-looking frame
Wins are useful. Learnings change strategy. Leaders pay attention to insights that influence how the next quarter is planned.
A useful learning has three parts: what the team tried, what shifted, and what changes in how the team will work next. The pattern matters more than the incident. One missed deadline is a risk. Three missed deadlines on the same kind of project is a learning that should change estimation discipline.
Frame learnings forward, not backward. Not “the redesign took longer than expected” but “the redesign revealed that our discovery phase under-budgets time on integration mapping by roughly 30% we are adjusting our scoping template for retainer renewals starting in May.”
This is also where AI assistance earns its place. Pulling learnings out of a quarter’s worth of board comments, retrospective notes, and timesheet entries is mechanical work. In Skarya, Kobi can generate a board summary or a project report in seconds what moved, what stalled, what patterns repeated. The team’s job is to read the output, validate it, and shape the strategic frame around it. The drafting time disappears.
Step 5: End with the call, not the recap
A weak update ends with a summary. A strong update ends with what happens next.
Three things belong in the closing block: two or three actions the team plans to take, decisions leadership needs to weigh in on, and any timing or dependencies that matter. Each decision phrased as a concrete ask, not a hope. “Approve scope renegotiation for Sandberg by 5 May” not “we should probably revisit Sandberg scope soon.”
The call is the difference between an update leadership reads and an update leadership acts on.
Best Practices and Common Mistakes That Weaken Leadership Updates
Most reporting failures come from a small set of repeating patterns. Naming them directly is more useful than another five bullet best-practices list.
Reporting activity instead of outcomes. The most common mistake. The fix is structural open every update with what changed in the business, then move into the work that drove it. Activity belongs in supporting views, not the headline.
Burying the ask. A decision request hidden in paragraph four gets missed. Put it near the top. If leadership needs to act, that information should sit in the first 200 words.
Hiding risk until it lands. Risk surfaced early gets help. Risk surfaced late gets damage control. Service businesses live or die on this discipline a margin issue caught at week three is a conversation; the same issue caught at month three is a write-off.
Inconsistent cadence. Weekly updates that arrive every two or three weeks lose more credibility than no updates at all. Predictability beats polish. A short, reliable Monday update earns more leadership trust than an excellent monthly report that slips its deadline twice a year.
Too many metrics, no story. A dashboard with 14 KPIs reads as noise. Three numbers with a story around them margin, backlog, utilisation, and what they mean this week reads as judgement. Leaders are buying judgement, not data.
❓ How do you share a missed target without sounding negative?
Frame the miss as a learning, not a failure. State what was attempted, what shifted, what the team has changed in response, and what leadership input is now needed. Honest reporting on a miss builds more trust than a glossed win — leaders remember the teams who flagged trouble early and adapted, not the teams who hid it until the next quarter. The structure is: outcome, cause, response, ask.
💡 Pro Tip: Once a quarter, read your last six leadership updates back to back. Patterns leap out the same risk surfacing repeatedly without resolution, the same client showing up in every “needs attention” section, the same metric drifting. That five-minute review usually surfaces the next strategic conversation worth having.
What This Looks Like in Practice A Service Business Update Example
A 22-person digital agency in Sydney. Quarterly review at 10am Tuesday. The principal has 15 minutes to prepare and 20 minutes in the room.
Before Skarya, the prep ran like this. Pull margin numbers from the spreadsheet the ops manager updates on Fridays. Cross-reference utilisation with the team’s submitted timesheets. Manually check which clients had unsigned scope changes. Try to remember which projects had slipped against original schedule. Three hours of reconciliation, finishing at 1am the night before.
In Skarya, the same prep runs differently. The principal opens the CFO Dashboard. Margin per client is live. Backlog per client is live three clients with healthy backlogs, one with backlog growing faster than delivery capacity. Risk Alerts has flagged two: one with margin trending under 20%, one with utilisation overrun. The Client Performance section shows which relationships are strengthening and which are softening over the last 90 days.
In ten minutes the principal has the picture. The 5 minutes after that, they use Kobi to generate a board summary on the at-risk client, naming what shifted and when. The leadership update writes itself: three numbers, two risks flagged, one decision requested. Total prep time, 15 minutes.
The shift is not better writing. It is the data living where the work already lives including the schedule signals that turn quietly into financial signals when scope drifts. When that integration is missing, leadership updates degrade to activity reports because the financial reality is too slow to surface.
How Often Should You Report Wins and Learnings?
Cadence by audience.
Weekly for internal team syncs short, structured, focused on what shifted and what is now blocked. Monthly for leadership updates fuller picture, financial signals, learnings from the period. Quarterly for board-level conversations strategic patterns, multi-quarter trends, capital decisions.
The discipline that matters more than the frequency: hold the rhythm. A monthly update delivered the same day every month for a year teaches leadership to expect, prepare, and engage. A monthly update that drifts into “whenever I get to it” teaches them to chase you for information which slowly erodes the credibility of every report you do send.
Pick a cadence you can hold for twelve months. Then hold it.
Bring Your Wins Into Focus
The leadership update is not a writing exercise. It is the surface where the team’s read on the business meets the leader’s need to make decisions. Service businesses have a sharper version of this conversation than most every update is implicitly a P&L conversation, even when it is dressed as a project status.
The teams who do this well are not better writers. They are working from a tool stack where the data already aligns. Where boards carry contract values, timesheets carry billable signals, and the financial picture updates itself as work moves. The update becomes a 15-minute synthesis of a live picture, not a three-hour reconciliation of disconnected systems.
That is the shift worth aiming for. Not a better template. A surface where the next leadership update is already half-written by the time you sit down to write it.
Frequently Asked Questions
How do you communicate wins to leadership effectively?
Lead with the outcome, ground it in financial or operational impact, prove it with two or three relevant metrics, and end with the decision or action you need from leadership. Keep the message short 200 to 400 words for most weekly updates, no more than a single page for monthly. Specifics beat adjectives every time. “Margin lifted from 18% to 26% on Sandberg this quarter” carries more weight than “great progress on Sandberg.”
What metrics belong in a leadership update for a service business?
Three matter most. Margin per client and overall, the live read on whether work is profitable. Backlog the gap between signed revenue and earned revenue, which tells leadership how much committed work is still to be delivered. Utilisation the percentage of available team capacity being used on billable work. These three together paint the financial health of a service business in a single glance, which is what leadership needs from an update.
How do you share learnings honestly without sounding negative?
Frame learnings as forward-looking insights, not retrospective failures. Name what the team attempted, what shifted as a result, and what changes in how the team will work next. The pattern matters more than the incident one missed deadline is a risk, three on the same kind of project is a learning that changes estimation discipline. Honest reporting on what did not work builds more trust than glossing over it.
How often should service teams report to leadership?
Weekly for internal team syncs, monthly for leadership updates, quarterly for board-level conversations. The discipline that matters is consistency pick a cadence you can hold for twelve months and hold it. A monthly update delivered the same day every month earns more leadership trust than an excellent quarterly report that slips its deadline. Predictability is what teaches leadership to engage with the work
Leave a Reply