Leadership Development FAQ: Your Most Common Questions, Answered

This is the hardest transition in management. The skills that made them excellent individual contributors — technical expertise, personal output, problem-solving — are now less important than their ability to develop and direct other people. Redefine success clearly: their job is now to make their team successful, not to do the work themselves. Give them a manager they can learn from and create regular coaching conversations so they have somewhere to process what they're figuring out. I go deeper on this in Why Founders Struggle to Share Leadership.

Give them stretch assignments with a safety net. Put them in situations that require them to lead before they feel ready, while making it clear you're available to coach them through it. The goal is to build confidence through experience, not through training programs alone. Pay attention to what they're naturally good at. Putting someone in a role that aligns with their strengths makes development faster and more sustainable.

Give them a clear picture of what better looks like in your organization. Most managers never receive a direct assessment of how they're doing. Build a regular one-on-one cadence with each manager. Ask coaching questions instead of always providing answers. And invest in management training that builds practical skills. Running a meeting, delivering feedback, managing a performance issue. Those skills matter more than most managers realize.

Directly, specifically, and soon. The longer a hard conversation waits, the more it costs — in the employee's ability to improve, your credibility, and the team's trust that issues get addressed. Prepare what you want to say, name the specific behavior or result rather than your interpretation of the person's intent, and deliver it privately. Tips from Management Training to Help With Employee Conflict covers this in more depth.

An effective coaching conversation starts with a question, not an answer. The goal is to help the person think through a problem and reach their own conclusion, not hand them a solution. Ask what they've already tried, what they think is getting in the way, and what they would do if they knew the answer. The more you talk, the less coaching is happening.

Be specific about what happened, when it happened, and what the impact was. Avoid generalizations like 'you always' or 'you never.' State what you need to see differently going forward, confirm they understand, and document it. Corrective conversations work better when the employee doesn't feel ambushed and when there's a clear record that the issue was addressed.

Some people are genuinely uncomfortable with public recognition. If that's the case, private and specific praise works better than a shout-out in a team meeting. What matters most is that the praise names what the person did and why it mattered, not just 'great job.' Specific recognition reinforces the behavior you want to see more of and tells the employee you're paying attention.

Create a context where feedback is normal and ongoing rather than a special event. Employees who receive regular check-ins and honest feedback are less defensive when a harder message comes. When you do deliver criticism, keep it focused on behavior and results, not personality. Ask what might be getting in their way. Follow up. A single conversation rarely changes behavior on its own.

You build systems by documenting how work gets done when it's done right, then training people to follow and improve those systems. The longer answer involves separating your role as owner from your role as operator and being willing to let go of things you've always controlled. The E-Myth's 7-Step Business Development Program is a useful framework for that process.