---
title: Announce, don't assign
author: IBEAR Toolkit
cohort: Classes 40-49
language: en
date: 2026-08-20
paths: [stayer, returner, pivoteer, climber]
---

# Announce, Don't Assign

**The principle:** Post what needs doing. Let people opt in. People follow through 3× more on what they picked than what they were told.

## Why It Works

When you say "I need someone to coordinate the regional trip," half your cohort tunes out (they didn't choose it). When you say "We need a regional trip coordinator. Here's what it involves. Let me know if you're in," the people who *actually want to do it* volunteer. They're intrinsically motivated. They show up.

This is not a personality thing. It's structural. When you assign, you create an obligation (resentment). When you announce, you create a choice (ownership).

## Where It Breaks

Doesn't work for things that *must* happen (required coursework, mandatory check-ins). Use for discretionary work: events, clusters, deep dives, projects.

## How to Do It

Template:

```
WHAT: [The thing]
WHY: [Why it matters in 1-2 sentences]
IF YOU'RE IN: [How to commit — reply, react, sign up]
BY WHEN: [Deadline]
```

Example:

```
WHAT: Coordinate the regional trip (São Paulo group, September)
WHY: We want a shared memory with people in the same region
IF YOU'RE IN: Reply in Slack #regional-trips + we'll plan async
BY WHEN: Friday by 5pm
```

That's it. Now the people who actually want this trip are in charge, not resentful.

## Cross-Cultural Notes

- **Direct cultures** (US, Northern Europe): Announcement method works immediately.
- **Hierarchical cultures** (Asia, Latin America): May need explicit permission ("This is genuinely optional, not a disguised ask").
- **Relational cultures**: Follow up 1:1 with people you think will care.

The method is universal; the framing changes.

---

**Tested by:** IBEAR Toolkit analysis of Fall cohort communication patterns.
**Continues to:** rotating-leadership, small-commitments