...random thoughts on Coaching for Leaders & Teams

Category: leadership

You’re Just in the Middle of Everything

black hanging bridge surrounded by green forest trees
Photo by Kaique Rocha on Pexels.com

So you’ve just become a line manager.

You were probably good at your job. Maybe even great. Then suddenly, you were “promoted” to manage people—some of them in different time zones, with different personalities, and different priorities. On top of that, your senior leaders now expect you to deliver faster, smoother, and better. Sometimes, they don’t even tell you what “better” means.

If you feel like you’re constantly navigating conflict, confusion, and crossed wires, you’re not alone.

And you’re not failing.

You’re just… in the middle.
And the middle is hard.


You’re Now the Bridge

Being a new manager means you’re suddenly the bridge between people who don’t always understand each other.

One day, your team member in Bangalore tells you she’s overwhelmed with the current workload. The next day, your VP casually mentions, “Can we also add that new feature by next Friday?”

You feel stuck. Torn between protecting your team and not disappointing your sponsor.
You freeze, thinking: Is it even okay to push back? What do I say?

Here’s the truth no one tells you in your on-boarding: being a manager isn’t about having the answers. It’s about helping people understand each other better.


Don’t Translate Pressure — Translate Priorities

When you’re caught between conflicting demands, don’t just pass messages back and forth. Translate intent.

Try something like this:

“I hear that delivering this quickly is really important to the business. Here’s what our current capacity allows. Would you like us to ship a smaller version faster—or keep the scope and take a little more time?”

You’re not saying no. You’re showing them the path ahead.

That’s influence. That’s leadership.


Remote Teams Don’t Need More Meetings—They Need More Meaning

If you’re managing a distributed team, it can feel like everything has to be over Zoom or Slack. But more meetings don’t always mean more clarity.

Let’s say your developer in Berlin keeps missing the 9 AM stand-up. Your instinct might be to enforce attendance. But what they might really need is a rhythm that respects their time zone and energy.

What if, instead, your team posts async updates on Slack every Monday? You could then reserve your live time for real conversation. This includes decision-making, problem-solving, and emotional check-ins.

Don’t be afraid to ask your team what’s working and what’s not. It’s not weakness. It’s wisdom.


When Conflict Shows Up, Don’t Panic

Eventually, someone on your team will clash with someone else. It might be about code reviews, tone, ownership, or even who gets credit.

Your first instinct might be to fix it. But your real job is to coach them through it, not carry it on your back.

You can say something like:

“It sounds like there’s some tension here. Can we talk together about what’s going on? My role isn’t to take sides—I just want to help us all work better together.”

That moment might feel awkward. But it’s also the moment your team learns what kind of leader you are.


You’re Allowed to Push Back

Just because someone is more senior doesn’t mean they see the full picture. You do. That’s why you were put in this role.

When a sponsor asks for something unrealistic, breathe. You can respond with facts and kindness.

Try this:

“We’d love to deliver that, and I want to make sure we do it well. Based on current scope and bandwidth, we’d need to either reduce the feature set or extend the timeline. Which feels more important to you?”

You’re not being difficult. You’re being clear.

And clarity is one of the greatest gifts you can give.


The Quiet Practice of Reflection

If all of this feels like a lot—it is.
Being a manager isn’t just about managing others. It’s about managing yourself.

Take time each week to pause and ask:

  • What felt hard this week?
  • What conversation am I avoiding?
  • What’s one thing I could say more clearly?
  • Where did I lead with curiosity, not control?

Growth doesn’t come from being perfect. It comes from paying attention.


Final Word

If you’re a new manager, you’re probably tired. Maybe a little lonely. Maybe wondering, “Am I even good at this?”

Yes. You are.
You’re learning how to lead in a complex, messy, human world. And that’s brave.

Keep listening. Keep asking. Keep translating.
Because your calm presence, your clarity, your questions—that’s what your team will remember.

Let’ chat ! I offer coaching sessions. They are designed to help team leaders create high-performing teams. Feel free to Book a 30 minutes FREE Discovery session.

👉 Follow me for more insights and actionable team leadership tips and team building strategies!

5 Collaboration Hacks Every Team Leader Must Try!

people doing group hand cheer
Photo by Dio Hasbi Saniskoro on Pexels.com

Are you a leader looking for fresh ways to boost teamwork and collaboration in your team? Gone are the days of sticking to the basics. These simple yet creative strategies can bring your team closer, high-performing and make collaboration effortless.


1. Role-Swap Days: Build Empathy

Want your team to understand each other better? Let them switch roles for a day. It’s a powerful way to build empathy and uncover fresh ideas.

Example: A UX designer worked with customer support for a day. They gained real insight into customer pain points, which inspired better product design.


2. Silent Meetings: Inclusive and Efficient

Tired of loud meetings where only a few people talk? Try “silent meetings.” Team members share their thoughts by typing them into a shared document or chat. It’s perfect for capturing input from everyone, especially introverts.

Example: A tech team used silent brainstorming for new feature ideas. The result? Creative ideas and a more inclusive discussion.


3. Random Collaboration Days: Break Silos

Teams often get stuck in their bubbles. A “random collaboration day” pairs employees from different departments to solve challenges together. It encourages creativity and cross-functional learning.

Example: A software developer teamed up with marketing to simplify technical jargon in user guides, improving customer satisfaction.


4. Walking One-on-Ones: Natural Conversations

Swap office chairs for walking shoes during one-on-one meetings. Walking reduces stress, sparks creativity, and leads to more open discussions.

Example: A tech lead noticed walking meetings helped their team open up about challenges, leading to better solutions and trust.


5. Gamify Problem-Solving: Add Fun to Work

Turn problem-solving into a fun competition. Gamification can energize the team and make work exciting.

Example: A team organized a “Bug Bash” challenge where developers competed to fix the most bugs. The outcome? A better codebase and energized developers.


Conclusion

Collaboration doesn’t have to be complicated. Small changes, like role swaps or silent meetings, can create a huge impact on teamwork.

What is your favorite collaboration hack ? Have you tried any ?

Ready to empower your team? Let’s chat! I specialize in helping leaders like you create high-performing, connected teams.

👉 Follow me for more insights and actionable team leadership tips!

Tribal maintaineance or Sprint Retrospectives : just another tribal ceremony?

Do you think that your sprint retrospective transitions the team to their cause ? or is it just another tribal ceremony?

The authors of Tribal Leadership talk about people forming tribes, which range from stages 1 to stage 5 (most evolved at stage 5). The tribal leaders in Stage 4/5 perform regular “tribal maintaineance”. But do you know that this tribal maintaineance ritual matches the sprint retrospectives feedback loop (which agile teams perform after every sprint)?

Stage 4/5 tribal leaders, who regularly perform these “tribal maintaineance” or “oil changes” (as the authors speak), ask these BIG questions –
1. what’s working well ?
2. what’s not working ?
3. what can we do to make the things that aren’t working, work ?

This indeed sounds familiar to the Agile Sprint Retrospective questions –
1. What worked well last Sprint that we should continue doing?
2. What didn’t work well last Sprint that we should stop doing?
3. What should we start doing?

But what’s the difference in these stage 4/5 tribes and agile sprint retrospectives ? Do agile sprint retrospectives miss anything?

I think that the major difference in these tribes vs the sprint team answering these similar questions, is that the tribe is indirectly answering more key questions – ” what’s our cause ?” and “what are we proud of ?”.

This tribal maintaineance activity provides the tribe a deeper understanding of their shared values. Once a tribe understands these shared values, the tribe members are united and therefore transition to a “we are great” tribe !! (stage 4), from a “I am great” (stage 3) !!

Thus this stage 4 melts all individual boundaries and the tribe members work collectively towards their noble cause. Surely Avatar’s on Pandora were a united tribe with a noble and heroic cause !!

But what about your sprint teams ? do they see their cause from a sprint retrospective or is it just another tribal ceremony?

© 2025 agile journeys

Theme by Anders NorénUp ↑