...rants by Asheesh Mehdiratta on Coaching, Transformation and Change

Category: learning

Trust: Your Teams Superpower !

Imagine a team where ideas flow freely, challenges are tackled head-on, and success feels like a collective win. That’s the power of Trust.

Trust isn’t just the foundation of a successful team—it’s the magic ingredient that transforms ordinary teams into extraordinary ones. Imagine a team where ideas flow freely, challenges are tackled head-on, and success feels like a collective win. That’s the power of Trust.

In today’s dynamic tech landscape, innovation is the name of the game. Trust is the superpower that can set your team apart. Your team is coding the next big app. They are ensuring seamless IT support. In both scenarios, Trust will be the force that propels you to new heights. Let’s explore why Trust matters. We’ll also look at how to build it to create a WOW factor for your team.


Why Trust is Your Team’s Superpower

  • Ignites Innovation: Trust cultivates a dynamic environment where bold ideas and experimentation thrive, driving the advancement of breakthrough technologies.
  • Turbocharges Collaboration: When Trust is high, teamwork feels effortless. Ideas, feedback, and support flow naturally, boosting productivity.
  • Builds Resilience: Teams with Trust bounce back faster from setbacks, viewing challenges as opportunities for growth.

Example: Picture a tech team at a game-changing startup. Without Trust, they might hesitate to share that “crazy idea” that could revolutionize the user experience. With Trust, they bring it forth, and suddenly, they’re the company everyone’s talking about.


How to Build Trust That WOWs

  1. Lead by Example
    • Action: Embody the values of integrity and reliability. Let your actions speak louder than words.
    • WOW Example: A CTO not only leads product discussions. They also sit in on customer support calls to understand pain points firsthand. This commitment to every aspect of the company builds immense Trust.
  2. Encourage Radical Transparency
    • Action: Share everything from successes to challenges with the team.
    • WOW Example: A CEO of a cloud services firm sends out a “State of the Startup” weekly email. The email details wins, losses, and lessons learned. This openness creates a culture where Trust is the norm, not the exception.
  3. Supercharge Team-Building
    • Action: Design experiences that are memorable and meaningful.
    • WOW Example: A tech company organizes an annual innovation hackathon. Teams not only build products but also bond over challenges. The event becomes a legend, with every participant feeling a deeper connection to their peers and the mission.
  4. Celebrate with Impact
    • Action: Recognition should feel authentic and impactful.
    • WOW Example: A team leader at a software company avoids sending a generic “Great job” email. Instead, they create a custom video montage. This montage showcases each team member’s contribution to a major release. The personal touch makes everyone feel seen and valued.
  5. Create Psychological Safety Zones
    • Action: Make every meeting a judgment-free zone where ideas and feedback are welcomed.
    • WOW Example: A product manager introduces a “Fail Fast, Learn Faster” session. In this session, the team shares what didn’t work. They also discuss what they learned. The result? A culture that celebrates growth and continuous improvement.

Conclusion: The WOW Factor of Trust

Building Trust is like planting seeds for a flourishing garden.

With care and dedication, it grows into something beautiful and powerful—a team that’s unstoppable. When Trust is at the core, teams don’t just meet goals; they exceed them, delivering WOW moments at every turn.


Let’s Create WOW Moments Together!

Ready to transform your team and unlock the superpower of Trust?

Follow me for more insights on building high-performing tech teams and creating a WOW factor in everything you do.

👉 Contact me for tailored coaching sessions or workshops designed to build Trust and drive extraordinary team success! Let’s make your team the one everyone talks about!

Are you learning from your failures?

failureIf you are a Star Wars fan, and have watched the latest movie The Last Jedi, you would have been struck by the sudden appearance of Yoda, the ‘Grandmaster’ of the Jedi order, and talking to Luke Skywalker about failures.

Yoda explains to Luke, the Last Jedi, that failure is a good teacher, and we must learn from our mistakes!

“The greatest teacher, failure is.”  – Yoda

In the real world,  some teams will fail at various stages in their transformation journey, and others may falter multiples times, before they finally succeed. It is never an easy straight line from point A to point B.

But as a Leader of teams, how do you treat these failures?

Do you reflect on the failures with the team and have an open discussion without any blame?

or Do you punish them for the failure?

Do you ask the question – What have we learnt from this failure?”

If you are aiming to build self managed teams, who can truly recognize their weaknesses and strengths, then it is important to let them fail and learn from their mistakes. It is important that they can do safe experiments, and design a better outcome, and solutions that delights the users.

To help, it would be good to look at Etsy’s culture of running ‘Blameless postmortems’, which talk about “what” happened? and how we can systematically remove the constraints so that human error can be reduced, instead of ‘blaming’ the person.  This is a powerful shift in the mindset and triggers a behavioral change in your teams.

But if as a Leader, you continue down the path of measuring failures, and then punishing the team, the organization culture becomes risk-averse. Teams will then not be ready to take risks, think outside the box, or have crazy ideas, and it would dampen the innovative mindset and creativity that we all humans possess.  You will never learn from your failures.

Conclusion:

To learn from failures is a key trait for successful teams. Even the famed Luke Skywalker had to be reminded by the Yoda, that failure is the greatest teacher!

So, if you can change your behaviors and are ready to take risks, with known constraints, then you will start looking at failures as learning opportunities and of course Yoda would be really proud of you!

So go ahead and ask your teams to share – what has been their biggest learning opportunity in the projects/products that you develop and support? go ahead and conduct the ‘Blameless postmortems’ and you would be surprised pleasantly.

You can subscribe to this blog , and would encourage you to share your stories and your feedback here.

 

Are you increasing your Organizational Learnings?

As part of the DevOps transformation, one of the main challenges is building bridges across Dev and Ops and start to build TRUST.

But TRUST cannot be built by simply flipping a switch !! It is never easy.  So how do you start ?

Sometimes, the trust starts to build between teams when they start to share their internal  success and  failure stories .  Trust starts to build when  they start to create Transparency across the walls. But this requires them to  start to share and start to speak a Common Language .

Today if you ask any Development or an Operations teams, they have conflicting goals, and their languages are  poles apart. The language manifests in the form of different process, different artifacts and different formats which they share with their management and teams. There is a BIG GAP!

So how do you reconcile this GAP ? Ask if you can – 

  1. Can you codify your team  processes?  
  2. Can you automate these process steps ? 
  3. Can you codify the creation of your teams artifacts?
  4. Can you automate the creation of these artifacts?

Benefits of Common Language

The benefits are huge, if you start to codify this implicit and explicit knowledge across teams. As you start to codify, you can start to automate and the benefits will  further increase, as this knowledge can now be shared across teams, repeatedly, and improved,  and in the end will lead to increased organisational learning.

So if you are able to codify, automate and share your knowledge across development and operations, you will be on your way to  maximize your organizational learning!

Go ahead and share how you increased your organizational learning?

You can subscribe via RSS to this blog , and would encourage you to share your stories and your feedback in the Comments below.

Are you Learning and sharpening your Axe?

learning As you run your daily grind, do you reflect and think about your Own Development? Or do you let your circumstances dictate your agenda? and drown your Development needs? As the famous woodcutters story goes, do you sharpen your Axe? Or do you keep on doing the same thing, same process, same boring steps everyday? Or Do you Take a step back, and Reflect? do you LEARN? and really ask yourself if I have sharpened my Axe or not?

Sharpening my Axe – My 2017 Learning’s

For me, I personally learnt quite a lot during 2017, and build up on my knowledge base, and interacted with peers across the industry.

1. LeSS is more!

It was a pleasure to listen and learn the thinking behind LeSS (Large Scale Scrum), straight from the creators (Bas Vodde) himself, and become one of the LeSS converts ‘officially’  [Certified LeSS Practitioner]. The discussions and the learning’s from Bas, were extremely valuable and opened the realm of Systems Thinking and the organisational inertia’s and how “DeScaling” your organization makes the real difference.

If you have not heard of Larman’s Laws of Organizational Behavior, then you have missed something…..

My desire for LeSS is now more than ever !! 

2. FLOW rules !

The most amazing experience this year was listening to Don Reinertsen, author of FLOW, 2nd Generation Lean Product Development.

I regard Don R as the final frontier in the WHY? Scrum works and what are the pitfalls, and it was great to be able to survive the intense class (face to face) with Don early this year. Don is an inspiration to many of the agile gurus and when you have the grand master himself talking within 2 feet, it is an exhilarating experience!

The jam packed master class answered many of my misconceptions, on Cost of Delay, Cycle Time and simply opened my eyes to the science behind the various agile methodologies.

In the end FLOW has been on top of my mind ever since that class ?

3. Local Meetups

The local meet ups in Bangalore have a very vibrant buzz, and I could make myself join few AWS and Docker meet ups, which really showed how the tooling is miles ahead, while the corporate honchos are still debating – What is the definition of DevOps ?

?  Sad but true!

The community showed that the younger generation has not seen the archaic desktop based applications and are pleasantly exposed to only the continuous delivery model, with continuous deployments on the cloud in matter of seconds. Microservices, MicroApps, Microbots are ensuring the death of monolith Architecture.

Breath of fresh air I must say!

 

My Community Contributions: using my Axe

To contribute back to the community, I had to push myself by signing up to present at 2 different forums this year, which I thoroughly enjoyed.

1. Global DevOps Summit as a Speaker

The exciting trip to Pune took me to the Global DevOps Summit as a Speaker, and allowed me to share my DevOps experiences. It was a pleasure to also learn and understand from the various speakers, how they were moving forward in their journeys.

You can find my presentation and summary notes, if you wish to know what I had presented and learned.

2. Self organizing Gamestorm as a Speaker

As a LeSS practitioner myself,  the self organisation principles always bring great joy to me.

The speaker forum from Scaling Agile Institute offered me a platform to show the ‘self designing’ team formation, as a game. It was an fun filled experience for the attendees and you could feel the high energy, and the belief in them that self organisation is indeed a reality.

You can find my presentation here, and the meetup here.

In the end, 2017 has been an exciting year, full of learning’s and new observations and experiences. I have tried to Sharpen my Axe, and would love to know what have you done to Sharpen your Axe, and feel free to share your learning’s this year.

If you like what you read here, then do subscribe to my blog , and feel free to share your feedback in the comments below.

Fresh Innings !

To my readers, this spot should mark a new beginning, for my rants and opinions on all things active in my world related to agile, lean, devops, change, digital, leadership, and much more,  and (hopefully) frequent than my earlier sputtering’s on blogspot for last 8 years…. Hope to learn and trigger some thoughtful conversations!

5 Step Recipe for building Communities of Practice

As part of organizational transformation journey, CIOs today need to move from hierarchical models to self organizing communities to deliver IT, and there is an even greater need to build and sustain “Communities of Practices” for achieving the same. If you are an internal change agent responsible for building these communities, you can learn about the 5 step recipe to building and nurturing these communities in your organization:

But before we kick-start, let us try to understand what really is a Community of Practice?

Communities of practice (CoP) are groups of people who share a concern or a passion for something they do and learn how to do it better as they interact regularly.

Typically these groups have a shared domain of interest, shared competence, and learn regularly from each other. They engage in joint activities and discussions, help each other, and share information; they are practitioners who share experiences, stories, tools, ways of addressing recurring problems — in short a shared practice

Below is a simple 5 step strategy to kick start and nurture your Community of Practice:

1. Establish a Sense of Urgency and leverage the Strategic objectives

Corporate honchos will typically lay down the current / future areas of focus for the organization. These are typically called as the Strategic Capabilities or future growth areas or similar sounding terms. 

The key to starting a community is to leverage these strategic objectives with an inbuilt sense of urgency, and find a key sponsor (read as TOP DOWN Support), and identify the contributions with this sponsor, as to how the community can add Value, and then focus the discussion and activities around these.

The BOTTOM UP support is always easy to find, once the Sponsor has been identified, who can then help in spreading the message across the enterprise. It is never a question of how to find the bottom up interest, but more a question of ‘how to engage and guide’ the early adopters and steer their passion.


2. Gather ‘early’ Adopters and “Run”

Start with whoever shows up and accept that there will be passionate people (few initially), but always encourage and accept different levels of participation. You will realise that the strength of participation varies from each individual. The ‘core’ (most active members) are those who participate regularly. There are others who follow the discussions or activities but do not take a leading role in making active contributions. 

Then there are those (likely the majority) who are on the periphery of the community but may become more active participants if the activities or discussions start to engage them more fully. All these levels of participation should be accepted and encouraged within the community.

There is never a critical mass required to start a community. So RUN with whoever shows up!


3. Partner with the internal and external Ecosystem

As a community guide, you will/shall/need to partner with the internal and external ecosystem for your organization.

The internal ecosystem would include your Support functions – typically Human Resources – Learning / Training departments, and the internal facilities, who can provide the required logistics, marketing muscle, sometimes manpower too and really make your community endeavours as a key part of their learning offerings. It is best to create this win-win combination to sustain your communities. 

The external ecosystem is key and would include partnership with the industry forums, and speakers, wherein the community members interact, broaden their expertise, and learn and share their stories, new learnings and upcoming trends. The key is to provide an engagement channel with your Community SPONSOR, on how to funnel the participation and share these learnings internally without getting sucked into the legal and compliance partners.  The culture of your organization may aid/resist this step-up.


4. Scale –  Horizontally 

In order to generate initial buy-in across a wider spectrum, it always makes sense to scale horizontally first, so that you can achieve critical mass for your community. This allows the members to contribute and break the ice, and helps in the initial stages in collaboration for the ‘core’ team, as each member brings some additional value to the conversation. We call this strategy as the – Go Wide move

It always helps to create a rhythm for the community with regular schedule of activities that brings the participants together on a regular basis, and combining familiarity and excitement, by focusing both on shared, common concerns and perspectives, but also by introducing radical or challenging perspectives for discussion or action.

5. Scale –  Vertically

Post the initial buy-in, and few first steps, there are always challenges of – What next? Who runs? When? How?

Try Vertical Scaling! – which means going deeper into the sub-topics of interest / work streams within a common umbrella, focusing on multiple aspects: roles/functions/location/on-line/offline medium

As the community needs to be refreshed every few seasons and undergoes an ownership transition, which will happens as you scale vertically now, it is OK to disengage the earlier passionate core and let a new ‘core’ emerge. Other options include introducing Game mechanics in the community, and allowing for non monetary rewards and publicity for the passionate volunteers.

In the end it is the Passion that always rules!

The key to building successful communities is to provide an enabling platform and a safe environment for people to share their stories without any judgement or fear of failure.

I would definitely be interested to hear if you have used these or additional steps to make your communities a success !!


Photo Source: http://bit.ly/2d39F6R

© 2025 agile journeys

Theme by Anders NorénUp ↑