A shoal is not a network. A network is a collection of people you have met. A shoal is a small group of people who compound your learning — who see your work clearly enough to challenge it, who you would tell your failures to as readily as your successes, and whose development you are actively invested in alongside your own.
The distinction matters because network-building and shoal-building are different activities with different mechanics. Most professional advice about "building your network" optimises for breadth. Shoal-building optimises for depth. Three people who genuinely know your work are worth more than three hundred people who know your name.
Workflow
What Makes It a Shoal
Three things distinguish a shoal from professional acquaintance:
Mutual learning. The exchange is genuinely bidirectional. Both parties learn something from the interaction, not just one. If you are consistently the one receiving and rarely the one giving, it is mentorship, not a shoal. Both are valuable — they are different things.
Honest feedback. You can share unfinished work, early ideas, and things that went wrong. The other person will tell you what they actually think, not what is polite or safe. This requires trust built over time. It cannot be assumed at the start — it has to be earned through reciprocated honesty.
Shared stakes. You care about each other's development, not just your own. A shoal member who gets something right and does not tell you is not behaving like a shoal member. The orientation is toward collective growth.
Finding Your Shoal
Most shoals form by proximity and slow accumulation rather than deliberate construction. You meet someone in a project, a course, or a shared context. You exchange a few real things over time. You notice that the quality of your thinking improves in their company. That is the shoal starting to form.
But proximity is not always available, especially for remote workers, career switchers, or people in isolated roles. When passive accumulation is not working, active initiation is the alternative.
The Cold-Start Approach
The most effective first move when building a shoal from scratch is precise and specific.
Do not ask to "catch up" or "grab a coffee" with someone you barely know. Those requests are vague and easy to defer. Instead, name something specific:
"I am working through [specific problem or question] and I noticed you have dealt with something similar in your work. Would you be willing to share how you approached it? I am happy to return the favour — I have been doing a lot with [relevant area] and could share what I've found."
This works because it is:
- Specific. It explains why you are approaching this person and not someone else.
- Bounded. It is a conversation about one thing, not a general relationship request.
- Reciprocal from the start. It signals that you are not just looking for extraction.
Most practitioners respond to this framing. What they do not respond to is vague requests that require them to supply the purpose and structure themselves.
Remote and Isolated Practitioners
If you are working remotely, in a small team, or in a domain where few others share your specific interests, the shoal can feel like a theoretical concept. It is not. The medium changes; the mechanics do not.
Asynchronous channels first. Shared communities, forums, and professional networks can surface candidates before any direct approach is needed. Watch who shares genuine work — not polished output, but thinking-in-progress. That is a signal.
Write your thinking publicly. Publishing working notes — in a shared Slack, on a professional network, in a community forum — makes you visible to people who share your interests. The shoal often finds you before you find it.
Short-form exchange before long-form commitment. A reply to something someone wrote is lower friction than a meeting request. Engage with their work first. Let the conversation develop at its own pace.
Be honest about your context. "I am a remote practitioner without many colleagues working in this area" is not a weakness to hide — it is context that makes the ask more specific and more relatable. Most practitioners have been there.
Maintaining and Contributing
A shoal that only takes from one member eventually loses that member. The maintenance rule is simple: what you receive, you return.
If someone in your shoal helps you work through a problem, find an opportunity to offer something in return — not as transaction, but as orientation. When you read something relevant to their work, share it. When you make a mistake they would benefit from knowing about, tell them. When their work is good, say so specifically and say why.
The shoal grows stronger through use. The members who contribute most also tend to receive most — not because they are keeping score, but because the relationship has depth.
Warning Signs
A shoal should not feel like performance. If you are consistently curating what you share rather than sharing honestly — showing only successes, hiding failures, managing your image — the relationship is a network contact, not a shoal member.
The test: could you send this person a message that says "I got this wrong and here is what I should have done" without rehearsing it first? If not, you have not yet built the trust that makes it a shoal.
From Chapter 6: Your Shoal — The Practitioner (Phil Rust, 2026). Part of the Practitioner companion resources.