Culture Change: Where it started

Where it Started

In my last blog post, I shared that over the past 6 months,  the organization I am in along with a couple of other organizations (over 300 people) have been working through a major shift requiring a significant change in culture. But to be honest the culture change started at least 6 months prior with a culture change within my organization and our sister systems organization. Let me explain.

Over the next several posts, my plan is to document the lead up to the bigger organizational change. It should give you an idea of how much change, and not just over a 6 month time period. So instead of digging into what has been happening over the past 6 months, I will get out the time machine and go back another 6 months.  In November of 2019, myself and my IT partner, Kelly, started working together for the first time. Leading up to November our two organizations had worked together, but they acted as two separate entities. Work would happen but independent of each other. But as Kelly and I started to work together, we knew that over the next year we would be transforming into a product ownership model and we needed to get our leaders and our organization to work together in a more seamless manner to make that transformation easier.

To be honest, we knew that we needed our leaders to act as if they were one team, instead of two but before we could do that, Kelly and I needed to work together in a more seamless manner. While I can't say we realized the following priorities before starting our journey, we both knew our teams to work as one. 

Priority #1 - Get on the same page. To be honest, the very first thing that Kelly and I realized was that we had to be on the same page. 

Priority #2 - We needed to model the behavior we wanted and since we were the joint leaders of this change, we needed to set the tone of what we hoped for from our direct reports.  

Priority #3 - Share with our directs that we were on the same page and to remind them periodically.

Priority #4 - have fun working together 

Priority #1 came about fairly quickly as Kelly and I met often through regularly scheduled weekly meetings, ad hoc, impromptu, between other meeting conversations, early mornings conversations and late evening conversations.  We compared notes on what we heard, we shared what we were thinking.  We did not hold back.  We agreed on lots but not everything but when we did not agree we talked it out and came to an agreement that we both stood behind. And critically, we both agreed that we needed a team that collaborated well and had each other's back.

Priority #2 we showed our team that we collaborated together. We had meetings and conversations with the entire team and showed them we collaborated together.  We had  small group meetings or 2 on 1 meetings where we showed that we could disagree but come to agreement. And across all of them, we showed that we were dedicated to working together and working well together. And it wasn't just a show, it was real.  It was what we wanted them to do, but also what we naturally ended up doing because it was the right thing to do. It wasn't one person had more power than the other, we were in it together.

Priority #3 came about as we met with our teams. We were transparent with our leadership team and told them and reminded them that we met all the time and that while we disagreed, we always worked it out. We slowly got to the point where one of us could anticipate what the other was about to say and that they could see we had each other's back.  And by verbally talking about the close connection that we had built, we were confirming what they were seeing. 

Priority #4 is important.  Always have fun doing what you do.  That is critical, and having someone there to share in the fun with is equally important.  But more on that in a future post.

Sounds magical, right?  This did not come by snapping our fingers together. But required lots of dedicated time from the two of us over many months. How many?  3 months? 6 months? Nope, I would say we are we still working on it and refining it.  The big muscle movements are done, but there is always areas for improvement or refinement. We spent and continue to spend a lot of time working through the nuances of the relationship that we are building.  We didn't agree on some things and we still don't agree on everything (which is critical). And to be honest, sometimes when we do just agree, I have learned that it might have been better to not have agreed so quickly, but that is for another post.

Building a Team - a lesson from ETSY

Photo by Eric Ziegler

As I was reading the blog post from the retired CTO, Kellan Elliot-McCrea, from Etsy, I became interested in more about who he was and what made him so special.  So I did some research and came across this awesome article.

How Etsy grew their number of female engineers by 500 % in one year

Yes, you read that title correct. Etsy grew the number of female engineers by 500% in one year. As part of their efforts, Etsy launched "Etsy Hacker Grants" to provide need-based scholarships to talented women engineers enrolling in Hacker School (a three-month hands-on course designed to teach people how to become better engineers).

As part of their hiring, they setup the parameters for success:

• Be serious but inviting
• look for balance
• optimize for building together
• optimize for data gathering
• normalize within your organization
• conduct your experiment publicly

What I found interesting was that these ideals and principals can be applied to people of all cultures and teams. You can apply this to engineering teams or teams doing operations work. And you can apply these principals to not only hiring and helping others, but you can apply these principals to how you team should and could work together. 

What I also found interesting was their philosphy that a team should either have 0 women on it, or 2+ women on the team. One woman on the team ends up making her a woman engineer vs just being an engineer.

Visions - what are they and what to do with them

As you read my blog, I think everyone might be figuring out that I do a lot of reading and I like to highlight the things that I find most interesting. Mostly this writing is to help me synthesize my thoughts and to write down concepts I want to reference again later.  By posting them publicly, and sharing the blog posts openly, my hope is that others will gain something from it. Not only do I read a lot, I also listen to podcasts

One series of podcasts that I listen to is specific to leadership. While there are several very good podcasts, I like listening to Andy Stanley and his podcast,  Andy Stanley's Leadership Podcast. He has a perspective that is not unique but what I find to be very insightful. In a recently episode of his podcast, he talked with the former CEO of Home Depot, Frank Blake. In this episode they get into a deep conversation about visions of companies and what it means to the company and the employees.

A conversation with Frank Blake on Vision.

They did not get into what a vision is or how to create one, but rather, how to make a vision stick. how to get people to understand the vision and to make the vision the rallying call for the company. Andy has an entire book on how to create a vision, live the vision, and celebrate the vision. You can find his book, Making Vision Stick, on Amazon. I have not read the book yet, but if you do, please share your thoughts back here.

Becoming a more effective team

Best Friend
Photo by Eric Ziegler

Are you part of a team? I am guessing you might answer this question in the positive. Are you part of a great team? If not, why not? No matter how you answer that question, most likely your team become even more effective

3 Ways to Encourage Smarter Teamwork is great article from Harvard Business Review. The article shares 3 characteristics that that all individuals should embrace to ensure the entire team is more effective.

• Active listening - pausing and listening to your peers and allow them to share their ideas and their perspectives. in addition, pausing to listen to understand, taking notes so you don't forget, etc. All good skills to embrace
• Giving and receiving honest feedback - if you are going to truly collaborate with your peers, you need to be willing to share where you think their ideas are good and bad, and be open to receiving that feedback. And you know that idea of being "recognized" that often means getting a pat on the back or a thank you from a colleague, because recognition can come from anywhere.
• Valuing team contributions, not stroking egos - you should be giving and serving your peers, on the team and in the community. if you do this, you will be recognized that you have influence and you will be seen as a leader.Remember my preivous post? you don't need to know all of the answers, and you should not expect others to have all of the answers. and if that is the case, then as a upstanding member of the community and the team, you should share and contirubte to the whole.

Leaders make mistakes - really

Tree
Photo by Eric Ziegler

3 Common Mistakes GOOD Leaders Make

Everyone makes mistakes. Managers, leaders, school teachers, police officers, clergy, etc. If you were to ask the question, what mistakes do you make, what would you say? In the blog post from "leader chat", they asked coaches and leaders, what mistakes do good leaders make. Based on the responses, they recognized three themes of mistakes. And the interesting part is that these are mistakes that anyone could make, not just a "leader" or not just a "manager".

What are the 3 most common misakes?

• An over-focus on the people aspect and avoiding difficult conversations.
• Trying to solve all of the problems of the people they work with or who work from them.
• Neglecting your own personal growth - if you don't keep on growing you

While these on the surface might appear to be manager specific, they are not. These are great things to avoid if you are a leader or an aspiring leader. If you are not currently a manager but lead others and aspire to manage people, and if you avoid these pitfalls, you will end doing things that will enhance your ability to become the next great leader.

Successful Coaching Conversations

Bright Star at Sunset
Photo by Eric ziegler

Coaching is a technique to improve. You can improve in sports from good coaching. You can improve at school from good coaching (or teaching as they like to call it). You can improve at work from good coaching. And coaching can come from anyone. You can be coached by your kids. You can be coached by your peers. You can be coached by your manager or your managers manager. In fact, you can even coach others. Are you a developer? System Tester? BSA? Have you been asked to help others with their +1 skill? Have you helped others with their +1 skill? Then you are coaching.

For me, coaching is one of the most rewarding experiences. And for any person that is a coach or is being coached, there are some things you should keep in mind to ensure you each get the most out of the experience being shared. In this article, they highlight 12 things you should always do, and then some things you should avoid.

12 Secrets for Successful Coaching Conversations

For me, some of the items that struck a chord most include:

• Relax. Lower defenses. Be your curious self.
• Embrace silence. Don’t feel pressure to fill the silence. Wait a bit longer than feels comfortable. Allow coachees to fill the silence.
• Develop next steps. Always identify next steps in behavioral terms. •What will you do? • How will you know you’re taking a next step? • How will colleagues know?

And then things to avoid:

• Fixing and helping. Control your inner fixer. Successful coaches give responsibility and ownership. They don’t take it.
• Interrupting.
• Asking two questions at once (I do this one all the time, note to self, stop doing that)

You don't have all the Answers - deal with it

In San Diego
Photo by Eric Ziegler

A friend recently passed along a blog post from Harvard Business Review ( +Harvard Business Review @harvardbiz) along with a note where he said:

"I seem to recall back when I took the ABC role that you said something along the lines of "you don't need to have all of the answers - you just need to know where to go to find them" - this article helps crystallize that advice a bit more for me"

No matter your role, your job is not to know everything. Your job is to help others in a way that provides business value. And to deliver that software, you need to take one step at a time with the goal that you complete each task in the most efficient way possible. Sometimes we make it hard on ourselves, because we hold ourselves accountable to know all of the answers. More often than not, we are most effective when we know what we are good at and what we know and are honest with ourselves when we admit to what we are not good at and what we don't know. 

When you are able to recognize both, the next step is to incorporate others into providing that business value.  So sometimes it takes more than one person to accomplish your goal.

Check out this article leading people when they know more than you do

(btw, you are all leaders in your own right, leading is not about just managing people)

Winning

Gettysburg Day 1 Battlefield
Photo by Eric Ziegler

The question that I have heard several times is, how do I know that I am successful, or asked in a different way, how do you know that you have won? This question is particularly intriguing to me.  If you only look at the surface, the answer can appear quite easy to answer.  I win when I beat the other team.  I win when I am faster than other people.  I win when I have completed the task that was requested of me. But if you dig deeper than just giving a surface level answer, you can learn much more about yourself and learn more about what drives you.

I work in IT and provide tools and technologies to the entire enterprise.  I am responsible for delivering these tools and technologies to people in the globally.  At the surface, I can declare success or that I have won by stating that I implemented the technology and tool.  But that is much too easy of an answer, and while I could be happy, in the long run, I know that if I just deliver the tools and technologies I really have not won, and I am not as happy as I could be.

Success in my job is about delivering the tools and technologies but is much deeper than that. It includes helping people learn how to use the tools and technologies to enhance how they do their job.  I am successful when I am able to talk with business areas, listen to what they do today and provide ideas on how they could use a technology to improve how they work.  I am successful when a business area uses the technology and incorporates it into their business processes.   I win when a business area uses a technology and they are much more effective in working with each other and their customers / clients.

The definition of success changes with each implementation.  A win from implementing one tool looks completely different than a win when implementing another technology.  The one constant between each implementation? Success is much deeper than just what is at the surface.  Success and winning only really occurs when you have thought through why you are doing the implementation.  If success is defined without the full picture, than almost guaranteed something is being left on the table and a win didn't actually occur. 

How do you define success?  What does winning look like to you?