Text size

A little more comfortable

Make room
to read.

A little more room. A little less effort. Find the size that feels right for you.

Default

David Zerbe (Raiken), founder of RAIKEN.io 6 min read Management

TL;DR ⚡ Leading purely by explaining and giving orders leaves your team behind and creates frustration over time. Your real goal should always be encouraging team members and colleagues to think for themselves. Clarifying ownership and asking the right questions make all the difference.

Sketch of a large figure pointing a raised finger at a small figure, with a crossed-out symbol above them.

I have spent more than 15 years working as a design manager in Design Operations (Design Ops), learning and growing alongside my clients and teams. My journey as a team lead and coach started at Jung von Matt Spree/Alster as an Art Director, followed a few years later by roles as Design Manager and Creative Director at Spread.net AG (Spreadshirt), before I decided to start my own company with a close friend. This article brings together my personal experiences and the lessons I have taken from books along the way. I will touch on several core ideas here and dive deeper into specific topics in future posts based on your feedback.

Why do my team members not act independently?

Is that really true? And if so, is it down to them, or to your own leadership style? Over the past 15 years, I have watched plenty of leads try to manage purely through their title, often lacking experience or empathy. Not everyone is naturally self-driven or steps up on their own when things get tough. Often, though, we as leads or role models are part of the problem: because we want to help our people succeed and prepare them for what lies ahead, we step in too quickly.

What actually motivates people at work?

Without motivation, performance drops. Research has shown for decades that we learn and work best when we are positively engaged. What motivates one person differs from the next, and we can roughly distinguish between Motivation 1.0, Motivation 2.0, and Motivation 3.0.

Motivation 1.0

Describes motivation driven by basic survival needs such as food, water, and physical safety. In modern knowledge work, those baseline needs rarely drive day-to-day motivation, so we can skip past them here.

Motivation 2.0

Describes motivation through external rewards and status, above all money. Ten or twenty years ago, Motivation 2.0 still carried a lot of weight, and since then its pull has faded noticeably. More and more people realize that salary alone is not the measure of everything. Having a good income helps, of course, but what comes after that? Does it make us happy on its own? Only up to a point. Skilled people are in high demand today. If money is the only thing keeping someone at your company, why should they stay when another offer matches their current pay and gives them meaningful, fulfilling work on top?

Motivation 3.0

Centers on self-realization and purpose. People want to feel that their work contributes to something meaningful and that their contribution is genuinely valued. When you are not valued, there is very little reason to keep giving your best. Even as children, we loved doing the things we were recognized for, and that does not change in adulthood. Add work that is enjoyable and an environment where people feel respected, and you notice how closely these three stages mirror Maslow's hierarchy of needs.

How do you encourage people to think for themselves?

Do you find yourself explaining the same tasks to your team over and over, only to feel like they forgot everything by the next week? Before blaming your team, take a look at the pattern. In my coaching work, I regularly meet dedicated team leads and project owners who want only the best for their colleagues and stand ready to help at every turn. We naturally slip into a caregiver role because we feel responsible for the outcome. And that is where the trap lies: if your team members learn in hindsight that they can bring every obstacle straight to your desk and get a ready-made answer, they eventually stop thinking the problem through themselves. Next time, hold back the urge to explain the solution right away. Instead, ask what they plan to do to solve the challenge. The one prerequisite is that they actually have the domain knowledge needed to solve it. If they do not, help them build that foundation first, not through a monologue, but by asking guiding questions so they arrive at the insight themselves.

The self-generation effect

Psychology describes this as the "spoken benefit" or self-generation effect: when you formulate and speak the insight out loud yourself, you internalize and retain it far better than when someone lectures you. And if they still get stuck, you can always step in and support them.

What do I do when a team member comes to me with a question?

First, resist the reflex to hand them the finished answer on a silver platter. Handing out answers feels fast in the moment, so people will gladly keep coming back to your desk, and over time they stop thinking independently while your own workload keeps growing. When someone comes to you with a question, pause and diagnose where the question comes from: do they already have the knowledge to solve this in theory, or is a piece of foundation missing?

1. They do not have the required knowledge yet and do not see why it matters

Start by walking through the fundamentals together. Once the basics click, ask them why they think this step matters for the project. If they do not spot the connection right away, build small bridges with questions so they can work their way toward the answer step by step.

2. They have the required knowledge, but do not see why it matters

Build bridges with questions so they connect the dots themselves. As they work their way toward the answer, acknowledge their progress so they see they are on the right track. That builds confidence and makes the conversation more rewarding for both sides.

3. They understand both the topic and why it matters

Now comes the decisive step: clarify ownership and the concrete next action. Ask: "What can you do now to solve this challenge?" or "How do you want to tackle this problem, and by when?" Sticking to this sequence changes the dynamic quickly. Early in my career, I tried to get to a solution as fast as possible, which either put unnecessary pressure on my team or made me take the problem off their plate altogether. Today I know it is completely fine if someone takes a little longer to work through a solution on their own. Give them that space, because that is how people grow into motivated, independent teammates. And in the rare case where someone abuses that leeway or refuses to engage, you can still set a clear boundary: "I expect you to change the following by [date]."

No magic, just patience

I hope this look into coaching conversations gave you a few practical impulses for your own day-to-day leadership. I would love to hear about your experiences with this approach in the comments.

Related Articles

Continue reading about design, UX, and creative tools