When to celebrate publicly and when to coach in private: a decision framework

Public celebration and private feedback are not interchangeable. The wrong one at the wrong moment breaks trust, sometimes permanently. Here's the decision framework used by experienced coaches and teachers inside Bitir.

The two channels and what they are for

Inside Bitir you have two channels for feedback to any member:

• Public celebrations. The whole group sees them. They are permanent. They contribute to the group's sense of shared progress.
• Private feedback. Only the manager and the member see it. It is the channel for anything that is directional, corrective, or personal.

These are not equivalent tools. Treating them as interchangeable — celebrating a struggle publicly, or burying a win in a private DM — is the single most common mistake new managers make.

The rule

Celebrate effort and outcomes publicly. Coach on technique, struggle, and patterns privately.

That is the whole rule. Almost every decision you need to make about feedback in a coaching group collapses into this sentence. What follows is how to apply it in practice.

What belongs in a public celebration

• A finished assignment. Every completion is worth naming, even a small one.
• A personal best — a run time, a weight, a grade, a performance.
• A streak milestone — four weeks of showing up, ten sessions attended, first 30 days of habit.
• Visible effort. "X has posted a reflection every week for six weeks." Effort is visible, reproducible, and celebration-worthy even without outcome.
• A group contribution. When a member helps another member, name it publicly.

Celebrations should be specific ("you ran 5k under 30 minutes for the first time"), not vague ("well done everyone"). Vague celebrations are received as background noise. Specific celebrations are received as recognition.

What belongs in private feedback

• Technique corrections. How a member is approaching a skill, a habit, a piece of work.
• Patterns you are noticing over multiple weeks. "I've seen you miss the Wednesday check-in three weeks in a row — is something making it hard?"
• Struggles — physical, emotional, financial, situational. Never put these in a public space, even if the member has mentioned them openly, unless they explicitly ask you to.
• Mistakes. A mistake named in public becomes permanent. A mistake named in private becomes a lesson.
• Anything sensitive about the member's body, money, family, or health.

The four edge cases where the rule breaks

Edge case 1: Consented public vulnerability

Sometimes a member wants their struggle to be visible. They might say so, or they might post something openly into a group visible channel. When that happens, the private rule no longer applies — the member has chosen public. Your job is then to honour that choice by responding publicly, carefully, and without turning it into a lesson for other members.

Edge case 2: The aggregated celebration of effort

When half your group has had a hard week, private feedback to each of them is right. But there is room for a single group-wide message that names the collective difficulty without naming names: "A lot of us had a hard week. Here is what I saw." This is public, but it is aggregated — it is a celebration of the effort the group as a whole made.

Edge case 3: The celebration of a shared lesson

Occasionally a private lesson is worth sharing with the group because many members would benefit. In that case, with explicit permission from the original member, you can rewrite the lesson in generalised terms and post it publicly. Ask permission every time. "I'd like to use what you taught me this week with the whole group — without your name — is that OK?" If the answer is anything other than an unambiguous yes, don't.

Edge case 4: The public correction that the group needs

There is one specific case where public feedback is unavoidable: when a member is behaving in a way that damages the group itself. A public intervention is sometimes necessary to reset norms. When that happens, be brief, be principled (correct the behaviour, not the person), and be clear that the group rules apply to everyone, including you.

How to actually use this inside Bitir

Bitir's design helps you do this by default. Member posts are private by default — members can submit work and you decide whether to publish it. Celebrations are a separate feature specifically designed for public recognition. Direct threads let you coach 1:1 without breaking into the group's main feed.

The concrete practices we see experienced managers use:

1. Post at least one public celebration every week. Not "celebrations as needed" — every week, on schedule. A group that sees celebrations only occasionally does not register them as a ritual.
2. Reply privately to every check-in response from a member who is struggling, within 24 hours. Even three sentences is enough.
3. When in doubt, default to private. It is almost always recoverable. A premature public comment is not.

A real example

In Nadia Patel's metabolic reset cohorts, the "private submit, public celebrate" pattern is the core mechanic. Members log their food privately; she aggregates and celebrates publicly without naming names. Completion went from 61% to 94% when she adopted this pattern. Full story: Nadia Patel — Type 2 diabetes reset on Bitir.