Feedback That Works

The reality

A senior team member's work has been slipping for three months. The founder has noticed and has not said anything because the senior team member is loyal, has been with the business since year one, and the conversation feels heavy. Three months becomes six months. The senior team member is now coasting and the rest of the team has noticed. By month nine the senior team member resigns, citing "lack of growth". In the exit conversation the founder finally says what should have been said in month two. The senior team member is genuinely confused. "I never knew this was a problem. If you had told me, I would have changed." The cost was not the difficult conversation that was avoided. The cost was nine months of avoidance, the team's loss of confidence in the founder, and the eventual exit of a senior person who could have been recovered with one calm conversation in week six. Service founders are usually not bad at giving feedback. They simply avoid it until the conversation is bigger than it ever needed to be.

Read this if

• A team member's performance has slipped recently and the founder has not had the conversation
• The founder catches themselves giving feedback in the exit interview that should have been given six months earlier
• Performance reviews are an annual event with no monthly or quarterly check-ins between
• Feedback in the business runs from the founder down, with no upward channel
• A team member resigned in the last year and the founder learned things in the exit conversation that were never raised while they were employed
• The founder cannot point to a feedback rhythm that runs in the business

What dysfunction costs

Hold the feedback for the exit interview and the cost arrives in four ways, all of them after the team member has already decided to leave.

Senior departures from delayed feedback. When feedback is held until exit rather than delivered in week six, senior team members exit who would have stayed. A senior departure on a 25-person service business costs AED 150K to AED 300K (USD 41K to 82K) in replacement, lost productivity during the 90-day handoff, and the client-relationship continuity gap that follows.

Performance drift left in place. A team member whose work has slipped and is not told typically stays at the reduced performance level for 6 to 12 months. Lost output across that window on a 30-person service business is typically AED 80K to AED 250K (USD 22K to 68K) per person per year, multiplied by however many team members are sitting in the same state without knowing it.

Standard erosion across the team. When the team sees performance drift go unaddressed, the team's standard drops to the lowest tolerated level. Net output across a 30-person firm typically drops 5 to 10 percent over 12 months. On AED 8M (USD 2.18M) revenue that is AED 400K to AED 800K (USD 109K to 218K) of effective annual output gone, without a single firing or visible incident.

Wrong hires kept too long. Without a feedback rhythm, the founder cannot tell the difference between a hire who is in a bad season and one who is in the wrong role. Wrong hires kept 9 to 12 months beyond when honest feedback would have surfaced the misfit typically cost AED 60K to AED 150K (USD 16K to 41K) per case in salary paid against weak output, opportunity cost, and the standard erosion above.

What success looks like

When feedback is a discipline:

• Every team member has a weekly or biweekly 1:1 with their manager (or the founder for direct reports) with a defined structure
• Performance feedback is given within 7 days of the event that prompted it, not 7 weeks
• A monthly written check-in covers what is working, what is not, and one specific change for the next month
• A quarterly structured review covers progress against the role's outputs and standards
• An upward feedback channel exists where team members can give feedback to the founder and the senior team
• The founder can name three specific feedback conversations they have had in the last 30 days

The framework

Feedback as a discipline runs as four layers. Each layer addresses a different pace and shape of feedback.

Layer 1: The 1:1 cadence

Every direct report has a weekly or biweekly 1:1 with the founder. 30 minutes. A defined structure: what is working, what is not, what do you need from me, what do I need from you. The 1:1 is the place where small concerns surface before they become big.

When the 1:1 is missing or skipped: feedback only happens when something has gone visibly wrong. The team member gets feedback as a correction rather than as a conversation.

The behaviour to adopt this week: schedule the 1:1s. Block the calendar. Hold them weekly or biweekly without exception. The first three are awkward. The fourth one becomes the most useful conversation in the week.

Layer 2: Real-time feedback

When something happens that needs feedback (a missed deadline, a strong piece of client work, a misjudged decision, a positive contribution in a meeting), the feedback gets delivered within 7 days. Not at the next quarterly review. Not at the annual one. Within the week.

The format is simple. "I noticed [specific behaviour] in [specific situation]. The impact was [specific consequence]. Going forward, [specific request or acknowledgement]." Two minutes for a positive piece of feedback. Five to ten minutes for a corrective one.

When real-time feedback is delayed: the team member cannot connect the feedback to the moment, and the feedback feels like a reckoning rather than a coaching conversation.

The behaviour to adopt this week: identify one piece of feedback the founder has been holding for more than two weeks. Deliver it within the next three days using the format.

Layer 3: The monthly written check-in

Once a month, a written exchange between the founder and each direct report. The team member writes three lines: what is working, what is not, one change they want to make. The founder writes back with a paragraph of acknowledgement and one specific request for the next month.

The check-in takes 15 minutes per person. It produces a written record of progress and friction. It also gives the team member space to surface things that are harder to say in person.

When the monthly check-in is missing: feedback runs entirely in real-time, which catches behaviours but misses patterns. The check-in is where patterns become visible.

The behaviour to adopt this week: send the first month's prompt to each direct report. Three lines. Reply with a paragraph and one request. Hold the cadence for three months before evaluating.

Layer 4: The quarterly structured review

Once a quarter, a 60 minute structured review per direct report. The review covers progress against the role's outputs and standards (the document from Role Architecture), strengths and growth areas, the team member's development, and a written summary signed by both.

The quarterly review is the structured pause where the founder and the team member step back from the week-to-week and look at the trajectory. It is not a corporate-style performance review.

When the quarterly review is missing: development conversations get crowded out by operational ones. A team member can have a year of strong real-time feedback and still feel they are not being developed.

The behaviour to adopt this week: schedule the quarterly reviews. 60 minutes each. Calendar entry. Standing template.

AI can draft the agenda, summarise patterns across the monthly check-ins, and prepare the founder for the harder conversations. It cannot read whether the person in front of the founder is hearing the message or nodding through it. A feedback rhythm that lets AI deliver the message itself, a "performance summary" pasted into Slack or an AI-drafted exit conversation, accelerates exactly the costs above.

A founder you might recognise

A founder runs a 26 person creative agency in Al Wasl. AED 8M (USD 2.2M) last year. Through 2024 and 2025 her feedback rhythm was: an annual review every December, occasional praise in WhatsApp, and avoided difficult conversations. By Q4 2025 she had lost three senior team members to resignation, each of whom said in their exit conversations that they had felt unclear about how their work was being received.

In Q1 2026 she installed the four layer rhythm. Weekly 1:1s with each direct report (six people, six 30 minute slots across the week). A real-time feedback rule: any feedback held for more than two weeks gets delivered. A monthly written check-in. Quarterly structured reviews.

The first six weeks were uncomfortable. Three of the six direct reports surfaced concerns that had been sitting for months. Two of the concerns required structural change (workload rebalancing, decision rights clarity). One required a hard conversation about performance that the founder had been avoiding for nine months.

Six months later the senior team was reporting feeling clearer about how their work was being received. The two performance concerns that had been festering were both resolved (one through structural support, one through a transition out). The founder reported feeling lighter, with significantly less unspoken weight carried into the weekend. The cost had been roughly four hours per week of feedback time. The output had been a team that no longer ran on guesswork about how the founder saw their work.

Working through it

1. Schedule the weekly or biweekly 1:1s. 30 minutes per direct report. Standing structure: working, not working, what do you need, what do I need.

2. Identify any held feedback and deliver it within 7 days. Use the format: specific behaviour, specific situation, specific impact, specific request.

3. Set up the monthly written check-in. Three lines from the team member. A paragraph and one request from the founder. 15 minutes per person.

4. Schedule the quarterly structured reviews. 60 minutes per direct report. Standing template covering outputs, strengths, growth, development, and a written summary.

5. Open the upward feedback channel. A quarterly anonymous form, a regular skip-level conversation, or a quarterly leadership team review of "what does the founder need to hear that nobody is telling them?"

Common mistakes

• Avoiding the difficult conversation in the hope it resolves itself. It rarely resolves. It usually gets worse. The 1:1 is the cheap version of the conversation. The exit interview is the expensive one.
• Saving real-time feedback for the quarterly review. A two month gap between the moment and the feedback breaks the connection. Within 7 days is the standard.
• Running 1:1s as status updates. A 1:1 that recaps the week is a status meeting. A 1:1 that surfaces what is working and what is not is a feedback meeting.
• Skipping the upward channel. Feedback that runs only top-down trains the team that the founder is the only voice that matters. The upward channel makes the system honest.
• Treating the quarterly review as paperwork. A review that is treated as paperwork produces paperwork. A review that is treated as a 60 minute trajectory conversation produces growth.

Self-assessment

Y or N for each.

1. Does every direct report have a weekly or biweekly 1:1 with a defined structure?
2. Is corrective feedback delivered within 7 days of the event that prompted it?
3. Is there a monthly written check-in between the founder and each direct report?
4. Are quarterly structured reviews scheduled and held against role outputs and standards?
5. Does an upward feedback channel exist for the founder and senior team?
6. Has the founder delivered at least three specific pieces of feedback in the last 30 days that they can name?
7. Has the founder surfaced and acted on at least one piece of upward feedback in the last quarter?

Five or more "yes" answers means feedback is doing the work it is supposed to do. Three or four is the band where the rhythm exists in part but the discipline has not held. Two or fewer means a senior team member's exit interview is going to surface things that should have been raised six months earlier.