Your top performer just handed in their resignation. “I wasn’t growing here,” they said. And the painful part? You thought the annual training budget was enough.
Building strong teams through development starts with understanding what the team actually needs — not just what looks good in a training budget.
This happens more often than most managers admit. You invest in courses, workshops, and lunch-and-learns, but your best people still leave because they don’t feel like they’re developing. The gap isn’t in your intentions. It’s in the activities you’re choosing.
After coaching hundreds of managers through this exact scenario, one pattern stands out: the development activities that actually work don’t look like “training.” They look like work, with a coaching layer on top.
Why do most employee development efforts fail?
They fail because they’re disconnected from the actual job. A three-day leadership workshop feels productive in the moment. Six weeks later, nothing has changed because there was no bridge between what someone learned and what they do on Monday morning.
The second problem is treating development as an event rather than a habit. You wouldn’t expect someone to get fit from a single gym session. Skill-building works the same way. It needs repetition, feedback, and small adjustments over weeks and months.
Here’s what separates managers who build strong teams from those who watch talent walk out the door: they weave development into existing work rhythms. They don’t add to the to-do list. They change how the to-do list gets done.
Activity 1: Stretch assignments with a safety net
Giving someone a project slightly beyond their current skill level is the oldest development trick in the book. But most managers get it wrong in one of two ways: they assign something too far beyond the person’s ability (which creates anxiety), or they hover so closely that the person never actually stretches.
How to do it well:
Pick a task that requires one new skill, not five. If someone has never led a client presentation, don’t hand them the biggest account. Start with an internal stakeholder meeting where the stakes are lower.
Then set up what I call a “safety net conversation” before the stretch begins. Cover three things:
- What success looks like (be specific)
- What support is available (and when to ask for it)
- What happens if it doesn’t go perfectly (spoiler: nothing catastrophic)
The safety net conversation matters because most people won’t take genuine risks unless they believe failure won’t damage their standing. One manager I coached started every stretch assignment by saying, “I’m giving you this because I think you can do it, and I’ll be here if you hit a wall.” His team’s internal promotion rate doubled in 18 months.
Coaching moment: After the assignment wraps, don’t just celebrate or correct. Ask: “What did you learn about yourself?” That question turns a project into a development experience.
Activity 2: Reverse mentoring across experience levels
Traditional mentoring pairs a senior person with a junior one. That’s fine, but it misses half the value. Reverse mentoring flips it: a newer team member teaches something to a more experienced colleague.
Your Gen Z hire probably understands emerging social platforms, data visualization tools, or communication preferences that your senior team doesn’t. Your senior people have institutional knowledge, political awareness, and pattern recognition that takes years to build.
A structure that works:
| Element | Details |
|---|---|
| Pairing | Match based on complementary skills, not hierarchy |
| Cadence | Biweekly 30-minute sessions for 3 months |
| Format | Each person teaches one thing per session |
| Accountability | Both share a one-sentence takeaway with the team monthly |
This activity does double duty. The junior person develops communication and teaching skills. The senior person stays current and practices intellectual humility. Both build a relationship that makes future collaboration easier.
One thing to watch: don’t force pairings based on demographic diversity alone. Match on genuine skill gaps. The learning has to feel real for both people, or it becomes performative.
Activity 3: Real-time coaching in one-on-ones
Most one-on-ones are status updates. “Here’s what I’m working on. Here’s what’s blocked.” That’s useful, but it’s project management, not development.
Reserve the last 10 minutes of every one-on-one for a coaching question. Not advice. A question. The difference matters. Advice tells someone what to do. A coaching question helps them figure it out themselves, which builds the skill permanently.
Five coaching questions that work in one-on-ones:
- “What’s the hardest decision you’re facing this week?”
- “If you could redo that conversation, what would you change?”
- “What skill do you wish you were better at for the project you’re in right now?”
- “Where are you playing it safe when you could be pushing?”
- “What did you try this week that didn’t work?”
You don’t need all five. One good question per session is enough. The point is shifting from telling to asking, which is harder than it sounds. Most managers default to solving problems because it feels efficient. But every time you solve a problem your team member could solve themselves, you’ve stolen a development opportunity.
A coaching observation from working with managers on this: the ones who struggle most with coaching questions are the ones who were promoted for being the best individual contributor. They’re used to having answers. Learning to hold back and ask instead of tell is their own development edge.
Activity 4: Cross-functional project exposure
People get stale when they only see problems through one lens. A developer who never talks to customers builds features nobody wants. A marketer who never sees the operations side promises things that can’t be delivered.
Cross-functional exposure doesn’t mean permanent role swaps. It means giving someone a window into how another part of the business works.
Three ways to do this without disrupting workflows:
-
Shadow days. One day per quarter, a team member shadows someone in a different function — and structured job shadowing programs turn these informal observations into deliberate learning experiences. No prep required. They just observe, ask questions, and report back on what they learned.
-
Cross-team project contributions. When another team needs help on a short-term project, volunteer one of your people. Two weeks working on a product launch with the sales team teaches more about customer needs than any training module.
-
Invite a guest to your team meeting. Once a month, bring someone from another department to your standup or team meeting. Let them share what they’re working on and where the overlaps are.
The development payoff here is perspective. People who understand how other functions operate make better decisions in their own roles. They also build relationships across the organization, which matters for their career and for cross-functional collaboration in general.
Activity 5: Structured feedback loops (not just annual reviews)
Annual performance reviews are too infrequent to drive development. By the time you discuss a behavior from March in a December review, neither of you remembers the context well enough to make it useful.
Build a lightweight feedback habit instead. The simplest version: after any significant piece of work (a presentation, a project milestone, a difficult conversation), spend five minutes on three questions.
- What went well?
- What would you do differently?
- What’s one thing to practice for next time?
This works better than formal reviews for development because the feedback is immediate, specific, and actionable. There’s no “meets expectations” checkbox. Just a conversation about getting better.
For peer feedback, try a monthly “feedback round” in your team meeting. Each person shares one thing they appreciated about a colleague’s work that month and one suggestion. Keep it tight: 60 seconds per person. The format forces specificity, and the public setting normalizes feedback as something that happens all the time, not just when something goes wrong.
One manager I worked with resisted this activity because she worried it would feel forced. She tried it for one quarter as an experiment. By month two, her team started giving each other unsolicited feedback between the formal rounds. The structure created the permission people needed to be honest with each other.
Activity 6: Encourage risk-taking with failure debriefs
The fastest learning happens at the edge of someone’s ability, and that edge always involves the possibility of failure. But most workplace cultures punish failure, even subtly. A raised eyebrow in a meeting, a shift in tone during a review, a project getting quietly reassigned. People notice, and they stop taking risks.
If you want your team to develop, you need to make failure safe. Not celebrated (that feels fake), but genuinely safe.
The failure debrief process:
When something doesn’t work, run a 15-minute debrief with two rules: no blame, and no vague lessons. Every takeaway has to be specific enough to act on.
Ask three questions:
- “What was the hypothesis? What did we think would happen?”
- “What actually happened, and why was it different?”
- “What will we do differently next time?”
The tone matters more than the format. If you, as the manager, share your own recent failure first, you set the standard. “I tried X this week and it didn’t work because Y. Next time I’ll do Z.” That’s it. No drama. Just learning.
Coaching observation: Teams where the manager openly discusses their own mistakes develop faster. It’s not complicated psychology. When the person with the most power shows vulnerability, everyone else feels permission to be honest about where they’re struggling.
How to make development stick without adding more to your plate
You might be reading this and thinking, “Great, six more things to manage.” But that’s the wrong frame. These activities replace what you’re already doing, not add to it.
Your one-on-ones already happen. Add a coaching question. Your team meetings already happen. Add a feedback round. Your projects already involve stretch. Add a safety net conversation. None of these require new calendar blocks. They require a different approach to the time you’re already spending.
A practical starting plan:
| Week | Action |
|---|---|
| Week 1 | Add one coaching question to each one-on-one |
| Week 2 | Identify one stretch assignment for one team member |
| Week 3 | Set up one reverse mentoring pair |
| Week 4 | Run your first failure debrief |
Start with whichever activity feels most natural to you. Get comfortable with one before adding the next. The managers who try to overhaul everything at once burn out and revert within a month.
What actually drives people to grow at work?
It’s not courses. It’s not budgets. It’s a manager who notices what someone’s good at, challenges them just beyond their comfort zone, and creates space for them to figure things out.
That’s what all six of these activities share. They trust the person to develop themselves, with you providing the structure and support. The days of top-down development plans are over. Your team members know what they need. Your job is to create the conditions where they can go get it.
If you want to take this further, training and development strategy works best when it combines structured programs with the kind of daily coaching moments we’ve covered here. And for managers looking to build a growth mindset across their team, these activities create the foundation.
Self-directed learning is where development ultimately leads. When your team members start seeking out their own growth, driven by the habits you’ve built together, that’s when you know the activities are working. Tools like Risely’s AI coach Merlin can support this shift by giving team members a private space to practice conversations, work through challenges, and build skills between your coaching sessions.
For teams ready to get intentional about learning needs at work, start with one activity this week. Just one. The compound effect will surprise you.
FAQs
What are the 4 approaches to employee development?
The four main approaches are training and education, on-the-job learning (stretch assignments, job rotation), coaching and mentoring, and self-directed development. The most effective programs combine all four rather than relying on any single approach.
What is an example of a development activity for employees?
A practical example is a stretch assignment with coaching support. A team member takes on a project slightly beyond their current skill level while their manager provides regular coaching check-ins. This builds real capability because the learning is tied to actual work outcomes, not theoretical knowledge.
What are organizational development activities?
Organizational development activities are initiatives designed to improve how a company functions overall. These include strategic planning, change management, team building, and performance systems. They work at the system level rather than the individual level, though the best approaches connect individual growth to organizational goals.