Leveraging your network for strategic learning beats learning alone, because solo grinding wastes hours and keeps your blind spots intact. In this article, Jef Menguin shows how to turn your network into a learning engine—by treating people as teachers, asking better questions, and building a simple system to capture what you learn. Use the shift and share it with your team so learning gets faster, lighter, and more collaborative.
Sometimes the hardest part of learning isn’t the work.
It’s the loneliness of trying to figure it out with no one to sanity-check you.
I’ve seen this in the workplace more times than I can count. Someone gets a new assignment, a new role, or a new tool—and they do what responsible people do: they read. They watch videos. They take notes. They search for templates. They try to “be prepared.”
And yet, when it’s time to act, they hesitate. Not because they don’t know anything, but because they don’t know what matters most.
That’s the quiet frustration: you did the homework… but you still feel unsure.
If you’re there right now, let me say this clearly: you’re not stuck because you lack discipline. You’re stuck because you’re trying to learn without a feedback loop. It’s like practicing a speech alone in your room—technically you’re “working,” but you don’t know how you sound until someone listens.
So yes, keep learning.
But stop learning alone.
Information is everywhere. Context is rare.
The internet gives you answers.
But it doesn’t give you judgment.
It can tell you what a tool is, what a framework says, what experts recommend. It can’t tell you what fits your situation—your team culture, your boss’s expectations, your deadline, your constraints, your politics. And that’s usually the part that makes work hard, di ba?
This is why you can read ten articles and still feel stuck. You’re collecting information, but you’re missing context. You’re trying to solve a real-world problem with generic advice.
A good network fixes that.
Not because your network is smarter than Google, but because people can do something Google can’t: they can look at your messy reality and say, “Start here.” Or, “That’s a distraction.” Or, “Careful—this is where it breaks.”
And if you’re thinking, “I don’t want to bother people,” I get it. Most professionals don’t want to feel makulit or needy. The goal isn’t to message everyone you know. The goal is to ask one person one good question—so you can move.
Your network has 4 teachers.
Here’s a small shift that changes everything: stop treating your network like a list of contacts.
Treat it like a learning system.
Most people reach out with a vague request: “Any tips?” “Can you help?” “Do you have advice?” The intention is good, but the question is wide, so the answer becomes wide too. You end up with more information… and still no direction.
A better move is to match your question to the kind of help you need. In my experience, your network teaches you in four distinct ways. Think of them as four “teachers” you can tap depending on what you’re trying to learn.
Some people are Scouts. They point you to the best starting point and save you from wasting time. They’re the ones who say, “Don’t read five books. Read this one chapter,” or “This is the only tutorial worth watching.”
Some people are Practitioners. They’ve done the work in real life, so they can translate theory into steps. They don’t just explain what should happen—they tell you what actually happened, including the friction and the mistakes.
Some people are Critics. They help you see what you can’t see. They spot weak logic, missing assumptions, or risks you’re ignoring. This is the teacher you need when you already have a plan—but you want to avoid a painful blind spot.
And some people are Connectors. They don’t give you the answer—they bring you to the person or room where the answer lives. Sometimes the fastest learning isn’t a resource. It’s an introduction.
Once you see these four types, asking becomes easier. You stop broadcasting vague questions and start making specific requests that people can actually respond to.
Next, I’ll show you how to map your own four teachers in five minutes—and I’ll give you simple message scripts that don’t feel awkward to send.
If you like this direction, I can write the next sections in the same rhythm:
- the “Network Map” tool (one page, simple)
- the outreach scripts (Scout / Practitioner / Critic / Connector)
- the “don’t extract, trade value” rule (without sounding preachy)
Write the next two sections.
Do a quick Network Map.
Before you send messages, pause.
Because the goal isn’t to “reach out more.” The goal is to reach out better—with a clear need and a clear person in mind.
Here’s a simple exercise I use when I feel stuck: I map my network the way I would map a team. Four roles. One current learning problem. One name per role.
Write one sentence: “Right now, I’m trying to learn ___.” Keep it specific. Not “leadership.” More like “how to run a difficult accountability conversation,” or “how to design a simple KPI dashboard,” or “how to price a half-day workshop without overexplaining.”
Then draw four boxes: Scout, Practitioner, Critic, Connector.
Now fill each box with one name.
Just one.
If you can’t think of anyone for a box, that’s not a failure. That’s a signal. It means you’ve found the exact kind of relationship you need to build next. Maybe you have plenty of Practitioners, but no Critic. Maybe you have Scouts who share links, but no Connector who can open a door.
And if you’re thinking, “My network isn’t that big,” good. You don’t need a big network. You need a usable one. Five helpful people beats five hundred silent connections.
Once you’ve done this, you’re not networking anymore. You’re designing support.
Use these message scripts (so you don’t sound awkward).
Most people don’t reach out because they don’t know what to say. They overthink the wording, then they delay the message, then the learning stays stuck.
So let’s remove the friction.
These scripts are short on purpose. They respect time. They make it easy for the other person to answer. And they don’t feel like you’re trying to “get something.” You’re trying to learn.
To a Scout (direction + resources) “Hey ___, I’m working on ___ this week. If you were me, what should I read/watch first?” Or: “Quick one—what should I ignore so I don’t waste time?”
To a Practitioner (real-world steps) “You’ve done ___ before. What surprised you when you started?” Or: “If I only had one hour to make progress on this, what would you do first?”
To a Critic (feedback + blind spots) “Can I send you a one-page plan? I want you to poke holes in it before I commit.” (Notice the key word: one page. You’re not asking them to carry your entire project.)
To a Connector (access + introductions) “Who’s one person I should talk to about ___? If you’re open to it, an intro would help—but no pressure.” That “no pressure” matters. You’re asking like a professional, not begging like a student.
One more small tip: end with a clear time box when appropriate. “Do you have 10 minutes this week?” makes it easier to say yes than “Can we chat sometime?”
Send one message today. Not four. Not ten.
One message, one clear question, one small win.
Then, the rest
Don’t extract. Trade value.
Here’s the fear people don’t say out loud: “What if I look like I’m just using them?”
Valid. Nobody wants to be that person.
So let’s make the rule simple: when you ask for help, bring something back. Not because you need to “pay” people. But because learning works better when it becomes a loop, not a one-way request.
The good news is you don’t need big value. You just need fair value.
You can offer a clean summary of what you learned. You can share a template you’re building. You can give credit publicly. You can volunteer feedback on their work. You can make a thoughtful intro when you see an overlap. Small trades build trust faster than big promises.
Try this line at the end of your message: “If it helps, I can send you my notes after.” That’s it. You’re not begging. You’re collaborating.
And yes—sometimes you’ll ask someone who’s far ahead of you. What can you trade then? Respect. Preparation. Brevity. Follow-through. Most professionals don’t mind helping. They mind helping someone who wastes the help.
So be the kind of learner people enjoy supporting: clear, grateful, and willing to apply.
Three quick scenarios (so you can see it in action).
A team lead needs to have an accountability conversation. They’ve read articles about feedback, but they’re still nervous. So they go to a Critic—someone who will tell the truth. They send a one-page “what I plan to say” draft. The Critic replies, “Your opening sounds like blame. Start with impact. Also—be specific about the next step.” The conversation doesn’t become perfect, but it becomes doable.
A specialist is building a dashboard for the first time. They keep searching for “best KPIs,” but everything feels generic. They talk to a Practitioner who has built dashboards in messy organizations. The Practitioner says, “Don’t start with metrics. Start with decisions. What decisions will this dashboard support every week?” Suddenly the work stops being design and starts being clarity.
A career shifter wants to enter a new industry. They’re tempted to binge content for weeks. Instead, they message a Scout: “If you were starting over in this field, what should you learn first?” The Scout gives two resources and one warning: “Don’t get trapped in certifications. Build a small project you can show.” That advice saves them months.
Notice what happened in all three stories: nobody asked for “tips.” They asked for a specific kind of help. That’s the difference between networking and learning.
The 24-hour action: one person, one message.
Don’t make this complicated.
Pick one thing you’re trying to learn right now—the thing that’s quietly stressing you out. Write it down in one sentence.
Then choose one teacher type: Scout, Practitioner, Critic, or Connector.
Send one message today. Ten minutes max. Keep it clean. Keep it respectful.
And here’s the last shift to hold onto: a network is not something you have. It’s something you use well.
So don’t chase a bigger network.
Build a usable one.
