Showing posts with label collaborate. Show all posts
Showing posts with label collaborate. Show all posts

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.

Working Out Loud can not be Automated

Working Out Loud
Photo by Eric ziegler
Not sure how I ended reading an old post by +Bertrand Duperrin but I did.  Maybe something was calling to me.  Maybe it is just purely coincidence that I re-read his blog post. Either way, it has triggered me to write a blog post for the first time in several months. Let's dig in.  

Bertrand Duperrin, posted a blog post back in August of 2012 called Employees don't have time to waste narrating their work. What caught my eye originally was the title. First reaction, huh? You have to be kidding me. Bertand might be just trying to be sensationalistic with his title, I am not sure.  But it did catch my eye and cause me to read his blog post. While the title is interesting, I have to say that the blog post hits a nerve. Bertrand starts his blog post with a concept that I agree with ...

It’s impossible to think about emergent collaboration and self-organized structures without visibility on others’ work. 

This first sentence makes me think of +Change Agents Worldwide (@chagww, #CAWW). Why?  #CAWW is a self organized emergent collaboration organization that is about helping individuals, teams, companies, employees, etc. be more effective.  #CAWW works as a network of individuals that interact, share, and cooperate and collaborate on different topics and ideas, always trying to improve upon ideas that will help organizations be more effective. It is almost like he wrote this sentence with the concept of #CAWW in mind. 

In Bertrand's 3rd paragraph he continues down the same path by stating ....

collaboration, cooperation, problem solving and even innovation requires something to be shared so trigger the dynamic. Moreover, people often don’t realize they can be helped : sometimes we believe we’re doing right while we’re doing wrong, we’re doing right while we could do better, differently.

While the first sentence could be interrupted several ways, this statement does not align with the title at all. Only after you get more than half way through the blog post do you start to see where the title becomes relevant.  I believe this statement best summarizes the rest of the blog ... 

if people’s work’s worth being narrated, people should not always be the narrator. Their time is too precious to ask them to play the role of transponders. 

So now I get it.  People's time are too important to waste on working out loud (#WOL).  Bertrand continues and discusses the idea of having systems do the narrating by automatically creating activities in an activity stream - weekly reports, updates to profiles, etc.    I understand where he is going, but I think this concept misses the importance of working out loud (#WOL).

What do I believe? The idea of working out loud is not about the automated interactions? There is some value, but the biggest value is sharing information in a way a system can never do. Sharing information includes asking questions or putting a thought out that could trigger a thought by someone else. Automatic system updates are too prescribed to cause an emotional reaction by the receiver and bacause of that, the value it just not as high.  

I will say though, I do agree with his concept of having people jump out of their every day work systems to work out loud is not effective. To get people to be most effective, the system to work out loud needs to be integrated into the systems they work in every day.

Automatic system updates are the antithesis of what social networks are about. While an automatic update might provide value, they do not deliver come anywhere close to providing the same amount of value as working out loud.