Easy Agile Podcast Ep.8 Gerald Cadden Strategic Advisor & SAFe Program Consultant at Scaled Agile Inc.

Gerald shared that companies often face the same challenges over & over again when it comes to implementing agile, but the real challenge and most crucial is overcoming a fixed mindset.
"Gerald helps massive companies work better together while keeping teams focused on people and on the customer. I'll be revisiting this episode."
Gerald also highlights the difference between consultants & coaches, and the value of having good mentors + more
I loved this episode and know you will too!
Be sure to subscribe, enjoy the episode 🎧
Transcript
Sean Blake:
Hello, and welcome to this episode of the Easy Agile Podcast. Sean Blake here with you today. And we've got a great guest for you it's Gerald Cadden a Strategic Advisor and SAFe Program Consultant Trainer at Scaled Agile, Inc. Gerald is an experienced business, an IT professional, Strategic Advisor and Scaled Agile Program Consultant Trainer SPCT at Scaled Agile. Thanks, Gerald. Welcome to the Easy Agile Podcast. It's really great to have you on as a guest today, and thank you for spending a bit of time with us and sharing your expertise with our audience on the Easy Agile Podcast.
Sean Blake:
So I'm really interested and I'm interested in this story that... For all the guests that we have at the podcast, but can you tell me a little bit about your career today? I find that people find their way to these Agile roles or the Agile industry through so many diverse types of jobs in the past. Some people used to be plumbers or tradies, or they worked in finance or in banking. How did you find your way into working at somewhere like Scaled Agile?
Gerald Cadden:
Good morning, Sean. Thanks for having me here guys. I'm very happy to be here with you guys today. Career things are always an interesting question. I'm 53 and so when I look back I wonder how do I get to where I am? And you can often look at just a series of fortunate events. And I worked in retail shoe stores and then I decided to do something in my life. Did an IT diploma then did a degree and I started working in the IT side. I pretty much started as a developer because that was where the money was and so that's where you wanted to go. I didn't stay as a developer long. Okay. All right. I was a terrible developer so I wasn't good at it. It was frustrating.
Gerald Cadden:
I moved into some pre-sales work and that led me to doing business analysis and I really liked the BA work because I got to work with people and see changes. I could work with the developers, still got to work really directly with the customer which was much more interesting for me. So I spent a lot of time in BA doing the development work, doing business process reengineering my transitioned over to rational unified process. When it was around spent countless hours writing use cases doing your mail diagrams, convincing people on how to make the changes on those. And then Agile came along and I had to make a complete brain switch. So all of this stuff that I'd learned and depended on as a BA suddenly disappeared because Agile didn't require that as an upfront way of working. It required that to be in the background if you wanted it and it was more a collaboration.
Gerald Cadden:
So about 2004, 2005 started working with Agile a lot more by this time I was living in the U.S. So that's where I got my agile experience, stayed there for a long time. Got great experience and then I moved over to working with SAFe around 2011. The catalyst for that as I was working for the large financial firm in New York with a team there. And we were redesigning a large methodology for them to implement Agile at scale. Went to a seminar in 2011 at an Agile conference saw Dean Leffingwell presentation on SAFe and just looked up and went, "Well we can stop working on our methodology. It's done."
Gerald Cadden:
So hardly after that meeting I ran outside and tackled Dean Leffingwell because I wanted him to look at my diagrams and everything and give me some affirmation that I was doing the right thing. Dean is got a very frank face and he pulled his frank face and he looked at me and just said, "You know what? Just use SAFe?" And I'm like, "Yeah, we will." And so I started my SAFe journey around that time and we implemented that financial company and I've been on that journey ever since.
Sean Blake:
So take us back 10 years ago to 2011. And you're working at this financial company, you've heard of this concept of SAFe really for the first time you started to implement it. How did the people at that company respond to you bringing in this new way of thinking this new framework? It sounded you already had the diagrams on the frameworks and the concepts forming in your mind did you find that an easy process? I think I already know the answer, but how complex was that to try and introduce SAFe for the first time into an organization of that magnitude?
Gerald Cadden:
Yeah, this is a very large financial firm, a very old financial firm so very traditional ways of working. So what's interesting is the same challenges SAFe comes up against today they're present before SAFe even began. And so the same challenges of the past management approaches trying to move to faster ways of working was still there. So as we were furiously drawing diagrams in Visio, trying to create models for people to understand it was hard to create a continuum of knowledge and education that would get people to move from the mindset they had to the mindset we wanted them to have. And it was an evolving journey for myself and the team that I was working with. I work with a really great guy and his name is Algona, a very, very smart man.
Gerald Cadden:
And so the two of us we're always scratching our heads as to how to get the management to change their minds. And we focused on education, but it was still a big challenge. I finished on the project as they started with SAFe. I moved to different management role in the company that we continued the work there. Michael Stump he used to work for Scaled Agile I think he works now at a different company, but he continued a lot of that work and did a really good job and they did implement SAFe. They made changes, but they faced all the same challenges. The management mindset overcoming moving away from the silos to a more network structured organization. Just the tooling, just the simple things was still a challenge and there's still a challenge today. So the nature of the organization is still evolving even in the modern day Agile world.
Sean Blake:
You mentioned there that part of the challenge is around mindset and education. Have you found any shortcuts into how you change a team's mindset? The way they approach their work, the way that they approach working with other teams in that organization? I assume the factor of success has a lot to do with, has the team changed their mindset on the way they were working before and now committed to this new way of working? And can you talk to us a little bit about how do you go about changing a team's mindset?
Gerald Cadden:
Maybe I'll change the direction of your question here, because what I've found is usually you don't have to work too hard to change the mindset of a team. Most of the teams are really eager to try new things and be innovative. You only come across some people in teams who may be their career path has got them to a certain point where they're happy with the way the world is and they don't want to change. The mindset you really need to change is around that leadership space and that's still true today. So the teams will readily adapt if management can create the environment that allows them to do it and if they can be empowered. But it's really... If you want to enable the team it's getting the leadership around them to change their mindset, to change the structures that are constraining the teams from doing the best job they can.
Gerald Cadden:
And so that for me was the big discovery as you went along and it's still true today. As Agile has been evolving I've noticed that people don't always put leadership at the top of the list of challenges but for me it's always been at that top of the list. A lot of people want to look at leadership and say things about them unflattering things, but you have to remember these are human beings. And the best way to come to leadership is to really begin with a conversation, help them understand. They know the challenges, but we need to help them understand what's causing the issues that are creating those challenges.
Gerald Cadden:
As you work with them and educate them you can to open their minds up a little more. Does that mean they'll actually change? Not necessarily. Political motivations, ideologies other things constrained leadership from moving. But conversations and education I think are the way to really approach leadership. And getting to know them as a person, take an interest in their challenges, take an interest in them as an individual. So create that social bond is an important thing. As a consultant that was always hard to do because as a consultant you're always seen as an external force and it's hard to build that somewhat social relationship with that leadership and build that trust.
Sean Blake:
Yeah, that's so true. Isn't it. I remember on an Agile transformation that I was on previously, how Agile coach really would spend just as much time with the leadership team as they would with us the Agile team. And it seems strange that the coach was spending so much time trying to really coach the leadership team on how they should think about this new way of working, but you put it in the right context there it's so important that they create that environment for their people and for their teams to feel safe in trying something new. Yeah, that's really important.
Gerald Cadden:
I think if you looked at how Agile evolves, when you look at the creation of the Agile manifesto and its principles and then the following frameworks like ScrumXP, et cetera it evolved from a team perspective. So everybody made the assumption that we needed to create these things for the teams to follow, but as people worked with teams they found that it wasn't the teams at all the teams adapt, but the management and the structures of the organizations are not adapting. And so that's really where it went.
Gerald Cadden:
I can't recall the number of countless Scrum implementations you worked on and you just hit that ceiling of organizational challenges. And it was always very frustrating for the teams. I think there's a an opposite side to that too is that too many in the Agile world just look at the teams as the center of the world and you can't approach it from that way either the teams are very important to delivering value to the customers, but it's the organization as a whole that delivers value. And I think you really have to sit back and just say, "The teams are part of that how do we change the organization inclusive of the teams?"
Sean Blake:
Okay. That's really interesting. Gerald, you've spoken a bit about teams and mindset, when you go into an organization, a big auto manufacturer or a big airline or a financial services company and they're asking for your help, or they're asking for your training, how do you assess where that organization is up to? What's their level of maturity from an Agile point of view? Do you have organizations that are coming to you who have in their mind that they're ready to go SAFe and then you turn up on day one and it turns out no one has any real idea about what that type of commitment looks like?
Gerald Cadden:
Yeah, it's a good question. Because I think as I look back at the history of this, in 2011, 2012 when SAFe really got going, as you went forward I mean, there was no concept of where to begin. Consultants were just figuring it out for themselves and like most consulting or most methodologies they got engaged in an IT space and at the team level. And people would try to grow from the team level upwards. And at some point we need to know I've struggled a lot with this because I was just trying to figure out where it is that. So my consulting hat was always on to sit down, talk to people about their challenges, find a way to help figure out how to solve the challenges whether it was going to be Scrum or SAFe or whatever is going to be right.
Gerald Cadden:
Those are just tools in the toolbox. But when Scaled Agile as I was working with... Excuse me, as I was working with SAFe, Scaled Agile brought out the implementation roadmap. It produced so much more clarity that came later in my time with SAFe and I wish it had come earlier because it really began to help me clarify that initial thing that we call getting over the tipping point. How to work with the organization you're talking to, work with the right people, understand their challenges, help them understand what causes those problems, which is the more traditional ways of working the traditional management mindset, help them connect SAFe as a way to overcome those challenges and begin to show them. If you looked at the roadmap it's this contiguous step-by-step thing, but what you find in reality is there are gaps between those steps and in those gaps is the time you as a transitional team are having lots of conversation with the management.
Gerald Cadden:
If you put them through a training class they're not going to come out of the class going, "Oh, wow that's it. We know what to do." It takes follow-up conversation. You have to have one-on-ones one on many conversations, cover topics of gains so you can remove the assumptions or sorry the misassumptions. So it's a lot of that kind of work that the roadmap its there for those who are implementing SAFe today use it. It is one of the most helpful tools you'll have.
Sean Blake:
Awesome. Yeah. I think just acknowledging the difference between the tools in the toolbox and then the other fact that you're dealing with humans and you're dealing with attitudes and motivations and behaviors and habits there's two very different things there really. It sounds you need to take them all together on that journey.
Gerald Cadden:
Yeah. A side to that we train so many SPCs like SAFe program consultants. We train them, training them out of classes all the time with us and our partners. The thing that you can, you can teach them about the framework, but you can't necessarily teach them how to be a good consultant or a good... I want to say I use the term consultant and coach, right?
Sean Blake:
Yes.
Gerald Cadden:
Sometimes I like to say a good consultant can be a good coach, but a good coach can't necessarily be a good consultant because there's another world of knowledge you need to have like how do you sit down and talk to executives? How do you learn the patients and the kinds of questions you need to ask, how do you learn to build those relationships and understand how to work the politics? So there are things outside the knowledge of an SPC that they need to gain. So young people coming in and running to do this SPC course I want to prepare you for everything, but it gives you the foundations.
Sean Blake:
So when you're in a organization or you're coaching people to go back to their organization how do you teach them those coaching skills so that when they come in and they've got to learn the politics, they've got to identify the red flags, they've got to manage the dependencies, they've got to bring new teams onto the train. How do you go about equipping that more human and communications of the toolbox really?
Gerald Cadden:
I think you can obviously teach the fundamentals of the framework by running through the training courses. But mentoring for me is the way to go. Every time I teach a training class I make it very clear to people when they go back and they're starting a transformation don't go this alone. Find experienced people that have done this and the experience shouldn't just be with SAFe their experience should be having worked with large organizations having experience with the portfolio level if necessary. Simply because there are skills that people develop over years of their career if they don't have at the beginning.
Gerald Cadden:
I mean, if I look back at some of the horrific things I had said in meetings and in front of executives my boss would put his hands up in front of his face because I was young and impulsive and immature and I see that today. So when I first came to the U.S I worked with some younger BAs and they would say things in a meetings and you quickly have to dance around some things to, "We didn't really want to say that right now." So I think mentoring is the skill. We can teach you the tactical skills, but teaching you the political skills, the human skills is something that takes mentoring and time.
Sean Blake:
Mentoring so important in that context. Isn't it?
Gerald Cadden:
Yeah.
Sean Blake:
Okay. So let's rewind 12 months ago to March 2020, a month that's probably burned into a lot of people's mind is the month that COVID changed our lives for the foreseeable future. I know that Easy Agile had a lot of content out there, articles about how to do remote PI Planning, how to help your virtual teams work better together and we didn't know that COVID was coming we just saw this trend happening in the workforce and we had this content available.
Sean Blake:
And then I was checking out our website analytics and we had this huge spike in what I assume were people in these companies trying to work out for the first time, how to do PI Planning virtually, how to keep very literally their release trains on the tracks in a time where people were either leaving the state, working from home for the first time, it's really like someone dropped the bomb in the middle of these release trains and people scrambling on how we are we going to do this virtually now? Did you have a lot of questions at the time on how are we going to do this? And how have you seen companies respond to those challenges?
Gerald Cadden:
Yeah. I remember being in Boulder, Colorado in January of 2020 and I just come back from vacation in Australia and that's when COVID was coming around and you were hearing about things in January, 2020. I was talking with my colleagues and we were wondering how bad this is going to be within two months the world was falling apart. And for us I think a good way to tell that story is to look at what Scaled Agile did. We knew our business that it was very reliant on our partner success and it still is today. And so as we began to see the physical world of PI Planning and training, as we began to see that completely falling apart the company had to quickly adapt.
Gerald Cadden:
We already had a set of priorities set for the PI and we implement Scaled Agile internally in the company. At the time we're running the company as a train itself because it's 170 all people. So they had to reprioritize the different epics, we pushed a new features and it was all about what do we need to change now to keep our partners afloat by getting them online and a really good team at Scaled Agile in a really cross-company effort to get short-term online materials created to keep the partners upright so they could keep teaching. They could find ways to do this, to do PI Planning, to do they're inspecting adapts all online. And so we pushed out a lot of material just simply in the form of PowerPoint slides that they could then incorporate into tools like Mural, Al tool. SAFe collaborate we went about developing this and we've been maturing that over time.
Gerald Cadden:
And so now we're in a world where we have a lot more stability. We saw a big dip like everybody else, but the question is, are you going to come out of that dip? And so what we did notice within probably even the second quarter of that year where the tail end of it we saw it starting to come up again, which our partners starting to teach more online. So the numbers told us that the materials we're producing were working. So for us it was just a great affirmation that organizing yourself the way we did organize yourself, the quick way we could adapt saved us. So Scaled Agile could have gone the way of a lot of companies and not being able to survive because our partners wouldn't have survived. We had the ability to adapt. So it's a great success story from my perspective.
Sean Blake:
Well, that's great. We're all glad you're still around to tell the story.
Gerald Cadden:
Yes we are.
Sean Blake:
And Gerald, whether you're reflecting on companies you've worked with in the past, or maybe even that internal Scaled Agile example you just touched on. Are there specific meetings or ceremonies or checking points that are really important as part of the Agile release train process? What are the things that really for you are mandatory or the most important elements that company should really hold onto during that really set up stage of trying to move towards the Scaled Agile approach?
Gerald Cadden:
So I interpret your question correctly. I think for me when you're implementing the really important things to focus on as a team first of all is the PI Planning. That is the number one thing. It's the first one people want to change because it's two days long and everybody has to come and it can cost companies a quite a significant sum of money to run that every 10 to 12 weeks. And so you will run very quickly as I had in the past in the car company you run very quickly into the financial controller who wants to understand why you're spending $40,000 a quarter on a big two-day meeting. And so they lie, they start questioning every item on the bill, but that's the most significant one.
Gerald Cadden:
PI Planning is significant. The inspect and adapt is the other one simply because at the end if you remove that feedback cycle, what we call closing the loop if you remove that then we have no opportunities to improve. So those two events themselves create the bookends what we get started with and how we close the loop, but there are smaller events that happen in between the team events are obviously all important. But more significant for me is the constant, the event for the product management team or program management team how are you going to filter them, excuse me.
Gerald Cadden:
Who are going to need to get together on a regular basis to ensure that then we call this the Sync. So this is the ART Sync or the POPM Sync. You need to make sure those are happening because those are these more dynamic feedback loops and ensure the progress of good architectural requirements or good features coming through so that when you get to PI Planning the teams have significant things to work on. So if you had to give me my top three events, PI Planning, inspect and adapt, and the ART Sync and product POPM Sync.
Sean Blake:
Awesome. I know there's always that temptation for teams to find the shortcuts and define the workarounds where they don't have to do certain meetings or certain check-ins, but in terms of communication it must be terribly important for these teams to make sure they're still communicating and they don't use the framework as an excuse to stop meeting together and to stop collaborating.
Gerald Cadden:
Yeah. I mean, I went through when I started implementing at the large car company in the U.S I decided to rip the bandaid off. They had several teams working on projects and they weren't doing well, when I looked at the challenges and decided we're going to implement SAFe some of the management they were, "Are you crazy? Why would you do this?" But they trusted me. And so we did rip the bandaid off and we formed them all into a not. We launched set up. And I remember at the end of the PIs some of the management have had a lot of doubts that were coming up after they sat through the PI and they said they just couldn't believe how great that was.
Gerald Cadden:
Even though the first PI was a little chaotic they understood the work and the collaboration, the alignment, just the discussions that took place were far more powerful for them. And teams were happier, they were walking out to a different environment. So it changed the mood a great deal. So I think the teams their ability to be heard in one of the most significant places is during PI Planning, they get that chance to be heard. They get that chance to participate rather than just be at the end where they're told what to do.
Sean Blake:
Mm-hmm (affirmative). So it really empowers the team.
Gerald Cadden:
Yeah. Absolutely.
Sean Blake:
That's great. So as a company moves out of the implementation phase and becomes a little bit more used to the way of doing things what's the best way for them to go about communicating that progress to the wider organization and then really evangelizing this way of working to try and get more teams on board and more Agile release trains set up so that it's really a whole company approach.
Gerald Cadden:
Yeah. A good question. So I think first of all the system demo that we do. So the regular system demos that take place, this is an event where you can invite people to. So when you get to the end of the program increment, the 10, 12, or the eight, 10 or 12 weeks and you're doing your PI system demo that's a chance for you to invite people that may be in the organization who are next on the list and they're going to be doing this, or they're curious, or if you have external suppliers who you're trying to get on board as part of the training have them come. Have them come to these events so they can just participate. They can see what goes on and it takes away some of the fear of what that stuff is. It gives them work much.
Gerald Cadden:
So the system demo whether you do it during the PI, but definitely the PI system demo and you want that one. So more ad hoc things and one of the things that I've seen organizations really fail to do is when they're having success the leadership around the train need to go out and I hate the term evangelize, but go out and show the successes. Get out and talk about this at the next company meeting present where they were and where they are now. But as part of that don't share just the metrics that show greater delivery of value show the human metrics, show how the team went from maybe a certain level of disgruntlement to maybe feeling happier and getting better feedback, show with how the business and technology have come closer together because they're able to collaborate and actually produce value together rather than being at odds because the system makes them at odds.
Sean Blake:
Awesome. Gerald is there anything else you'd like to share with our audience before we wrap up the episode? Any tips or words of encouragement, or perhaps some advice for those who are considering scaling up their Agile teams.
Gerald Cadden:
I think that the one piece of advice again, I'll reiterate back to the earlier point I made is as you are going through the implementation process and you're starting to launch your train and train your teams figure out how you're going to support them when you launch. Putting people through an SPC class or through all the other classes they won't come out safe geniuses. They'll have knowledge and they'll have the enthusiasm and have some trepidation as well, but you need good coaching. So figure out as you're beginning the implementation pattern where you're designing the teams et cetera, figure out what your coaching pattern is going to be. Hire the people with the knowledge and the experience work with a partner for the knowledge and experience. They shouldn't stay there forever if you work with consultants.
Gerald Cadden:
Their job should be to come in and empower you not to stay there permanently, but without that coaching and coaching over a couple of PIs your teams tend to run into problems and go backwards. So to keep that momentum moving forward for me it's figure out the coaching pattern. The only other one I would say too is make sure that you get good collaboration between product and the people who are going to be the product management role on architecture, get rid of the grievances, have them work together because those can stifle you. Get in and talk about the environments before you launch. You don't want funny problems when you, "Oh, the architecture is terrible." Okay. Let's talk about that before we launch." So just a couple of things that I think are really important things to focus on before you launch the train.
Sean Blake:
Awesome. I really appreciate that Gerald. I've actually learned a lot in our chat around. It's the same challenges that you had 10 years ago it's the same challenges that we have today. The really the COVID is the challenge of how do you focus on the mindset change. We've talked about the teams are eager to change. There might be a few grumbly voices along the way, but really it's about leadership providing a welcoming and safe environment to foster that change and the difference between being a coach and a consultant, the importance of mentoring. Wow we actually covered a lot of ground didn't we?
Gerald Cadden:
I may get some hate mail for that comment, but...
Sean Blake:
Oh, we'll see. Time will tell. Thanks so much Gerald for joining us on the Easy Agile Podcast. And we appreciate you sharing your expertise with us and the audience for the podcast. Thanks for having you.
Gerald Cadden:
Happy to do it anytime. Thanks for having me here today.
Sean Blake:
Thanks Gerald.
Related Episodes
- Podcast
Easy Agile Podcast Ep.14 Rocking the Docs
"I loved having the space to talk about common interests - all things technical documentation & information architecture" - Henri Seymour
On this episode of The Easy Agile Podcast, tune in to hear Henri Seymour - Developer at Easy Agile speak with Matt Reiner - Customer Advocate at K15t.
Henri & Matt are talking all things technical documentation (we promise this episode is way more interesting than it sounds! 😉)
✏️ Considering technical documentation as a product
✏️ The value of well written documentation
✏️ Why you should be digitally decluttering often
✏️ Information architecture
So many golden nuggets in this episode!Be sure to subscribe, enjoy the episode 🎧
Transcript
Henri Seymour:
Hi, everyone. This is the Easy Agile Podcast. We've got an episode today with Matt Reiner. I'm your host for today, Henri Seymour, developer at Easy Agile. And just before we start the podcast, I'd like to acknowledge the traditional Australians of the land on which I'm recording today, the Watiwati people of the Dharawal nation. Pay respect to elders past, present, and emerging, and extend that respect to any Aboriginal or Torres Strait Islander people listening to this episode.
Matt is an experienced content strategist with a history of working in the computer software industry, skilled in agile scrum framework, related tools, communication, technical writing, video production, customer interaction, strategic planning. And he's here today to talk with us about writing and specifically technical writing and documentation. Hi, Matt.
Matt Reiner:
Hi. It's great to be here. Yeah, I'm Matt. I'm into all sorts of content things. And one of those is technical writing, which is, I think more interesting than it sounds. I guess you'll have to decide by the end of the podcast, if you think so.
Henri Seymour:
Technical documentation experts. So when you talk about technical documentation specifically, what do you mean by that?
Matt Reiner:
Well, I feel like that term is actually in the middle of a big change right now. In the past, technical documentation was very strictly like, "Okay, we're a team, we're making a thing, a product." Maybe it's an app, maybe it's, I don't know, a go-kart and we need to have a user manual for that. Technical documentation was someone sitting down and writing down, "Okay, here are all the knobs and switches and here's what they do. Here are all the features. Here's maybe why you would use them."
So putting together that user guide, which traditionally was printed material that you would get with the product. But it's become a lot more over time, partially with the internet, because we can just constantly iterate on content like many of us do with the products that our teams make. And then also we are seeing it in new forms. Maybe it's not a printed piece, in fact, most people do not want printed technical documentation anymore, they want it online. Or even better, they want it right in context in your app when they're using it, they can just get the info they need, and then get on with it.
That's what technical documentation is. It's supposed to be there to help you do the thing that you really care about and then get out of the way so that you can do it.
Henri Seymour:
Do you have a description of why good technical documentation? Not just having it, but having it at a good quality in a way that really helps your users, is so important to product users.
Matt Reiner:
Well, I suppose we all find those points in our day or in our journey that we find ourselves in where we want to accomplish something, but we don't know how to do it. So a lot of us have really gotten very used to jumping on Google and saying, "Okay, here's this thing I want to do, how do I do it?" And good technical documentation is there with the answer you need, the explanation you need. Because really ultimately all of us are smart people who should be empowered to do the thing we're passionate about.
And technical writers and communicators who are really all members of our team. People who sit down to create good technical documentation uses few words as possible to get a person on the way they're going. And that's like, when it happens its just like, "Glorious," not to the user. They don't even know that it happened, they didn't even know that they read your writing. But to the writer, it's like, "Yeah, I did it, I did it. They don't even care what I did, but I did it." And now they're doing the thing that really matters.
Henri Seymour:
That's great understanding one of the major differences of like, I've written something and I don't want my user to be spending time on it. I want as little time spent reading this as possible.
Matt Reiner:
Yeah, yeah, yeah. You can have great pride in your work, but one of those metrics that a lot of people look at for websites is time spent on page. So sometimes you can fool yourself into thinking, "Oh wow, they spent 10 minutes on my page. That means my documentation's really good." But also that might mean that it's not very good and they're having to reread it over and over again. So the true metric is, did they get to the thing they really cared about? And unfortunately, it's hard to measure.
Henri Seymour:
You mentioned now that with the advent of the internet and giving you the opportunity to iterate on those docs in a way that you wouldn't be able to with printed documentation. That iterative thing brings the agile process of iterate on something that you already put out and improve it in the same way that as a developer I do for products. Can you tell us more about that iterative agile sort of process?
Matt Reiner:
Oh yeah. Yeah, it's so true. Documentation used to be back in the waterfall standard, more typical product project management days, documentation was a major part of it. You'd start this project by writing these massive documents of, "Here's what we're going to set out to do. And here's all the considerations, and here's how everything's going to connect up." And that did work really well for a lot of hardware. Which was the thing that we made for a long time. Just everything that humankind made was hardware often, as groups anyway.
And then all of a sudden this whole software thing comes along and we're trying to build that like it's a physical thing. And we get to the end of this two-year software project and people are like, "Yeah, that's not the thing that I wanted." But we're like, "Oh, but we go back to the beginning and look at that documentation, and that's what you said you wanted." But now with the internet and with just agile development, we really need to move away from this place where we start with a pile of documents. And then we develop another pile of documents as our, I don't know, development guidelines.
And then our test plans, and then finally we end up with user documentation. Instead, these days, documentation should really just grow from a very small piece of content throughout that whole agile development cycle into that final user documentation. Because it doesn't matter what we set out to make, it matters what we make. Nobody he wants to read about what we thought we would make, that's straight up fiction. And it's probably not an interesting read. It's really that final user guide that comes out of the agile process, but that's a big change, but it's a good one.
Henri Seymour:
I love that idea of just like, this is gradually growing. There is no specific start block and end block. It's a process. And you mentioned the opportunity to iterate on those documents. Do you have any advice for after you've published digitally your technical documentation from iterating on what you've already got there, improving that over time?
Matt Reiner:
Oh yeah. I know every agile framework is different, but they all have that feedback phase, where... And really that's throughout the whole process, but we do need to dedicate some time. So, there's a lot of different things we can look at. For example, I don't want to say basic, a standard one that we should be looking at is, you should have a help center, where you can implement something like Google Analytics so you can see just, what are people looking at? How long are they looking at it?
Another really good one is, you have to set it up separately in Google Analytics. What are people searching for on your site? You can also use Google... used to be Webmaster Tools. I think it's called Site Tools now, but you can see what were people searching for on Google before they came to your pages. That's all really, really valuable stuff. Then you can get more advanced. You can look at pointer tracking, apps that you can embed on there, which you get some pretty wild stuff.
But then you also, you want to consider having a forum at the bottom of each page like, "Was this helpful? Was it not helpful? Oh, it wasn't helpful? Tell me why. Oh, it was helpful? Tell me why." Just like a YouTube creator, they look for that feedback. That feedback is essential, the thumbs up. In fact, it's very controversial, YouTube just announced that they're going to hide the thumbs down numbers, but a lot of creators are like, "No, no, no don't do that because that communicates the value of this video that is out there."
So there's a lot of those signals. And then there's just really soft signals that, it's hard to know if people are using the content or not. Because you may never hear. Especially, if it is one of those things that they just get in and get out, you're not going to hear anything about that. But the feedback phase, it's really great to... Anytime you're getting feedback on your product that you're making, try to get your documentation out there as well. Because that's the time where people are open to exploring your product and giving feedback.
So why not explore that same documentation, the related documentation to see, "Okay, is this actually helping these people do the thing that they want to do? Or should we improve it just like we do with the product?"
Henri Seymour:
No, that's a really good, comparing the, we've just released a product. Give us feedback with doing the same thing with the documentation. Because that's when it's going to reach its peak use before everyone's got the hang of it. We've just done this feature release, let us know how you go using it, and the documentation is in a sense part of it, especially for more complex products.
Matt Reiner:
Exactly.Henri Seymour:
Do you have any background in the customer support side of things? We do customer support in-house as well as their documentation. So we're trying to improve the documentation to lower the support load on our team. Do you have any background in that... Can you solve it?
Matt Reiner:
Yeah. Well, yes and no. It's interesting. I work at K15t now, I used to be a customer of K15t's, so that's actually how I met the team. And that was also how I met documentation in the first place. At my last job, they brought me in to administrate this system called Jira. And I was like, "I don't know what that is." I told them, "I thought I could do it." And I figured it out, it was this little thing called Jira On-Demand, which is now Jira Cloud. And I introduced Confluence On-Demand to the company as well. And wow, I broke Jira a lot of times.
Luckily it wasn't like mission critical at the time, we were still really figuring it out. But it was through Atlassian's documentation on Jira that I really learned like, "Wow, there is tremendous value to this content here." And then I discovered, "Okay, how is Atlassian creating their documentation? Oh, they're doing it in Confluence. They're writing it in Confluence. They're using these apps from K15t." And so I started using those apps, and then I talked a lot to K15t customer support, just questions and how do I get this started?
And we also do our support in-house, so it's really great. So maybe as a customer, I overused it, I don't know. I should ask some of my colleagues if they got sick of me. But the benefit was very clear because they would send me, "Oh, here's documentation on this. And here's the answer to this question or here are the considerations you should keep in mind." And actually several of our teams now, we're really looking at, especially, for those features that are very robust, people have questions.
So it's like, how can we enable them to help them help themselves? And putting those resources out there is one thing, making sure that Google can find them, well, is another. But that is a really important thing, especially, since as a product team, when your user base grows, so does your need for support. It's just... I don't want to say it's exponential, but it's in line with each other. And so, one of the ways you can mitigate that is, making sure you have good design so that your product is easy to use. And then another is you need to have good content all around that entire experience so that you don't have to keep hiring more and more support people.
Or your support people can specialize and really focus on those deep entrenched issues, and then the documentation should help with the rest. But the secret sauce there is tricky. It's hard to write the perfect content to deflect the cases. That's everybody's dream.
Henri Seymour:
Even if it is just not all of them, but some of the common use cases start to get deflected away from support because people can self service. It does make a difference. And I really understand the idea of Jira documentation as well. Easy Agile works on Jira and it's... Jira is an incredibly complicated product at this point, and I imagine it probably was also complicated when it was Jira On-Demand. Because it's so complicated and so detailed, there's no way to make that easy to understand for a user without that documentation. There's no getting around that one.
Matt Reiner:Yeah. I think there should be a club for the people who have broken workflows too many times in Jira. But yeah, I mean the documentation saved me many times and I would have to put out a... Well, it was a HipChat message at the time. May it rest in peace and I'd have to say, "I broke Jira, give me a minute. I got to go read something." Not the way you want to learn Jira, but it's an option.
Henri Seymour:
It is. Sometimes you learn things by breaking things. That's-
Matt Reiner:
That's right.
Henri Seymour:
Really seems like my experience in software so far. You try to break the things that people aren't currently using and that's about all you can do.
Matt Reiner:
Exactly.
Henri Seymour:
So K15t has recently published Rock the Docs. Can you tell us a bit more about this project?
Matt Reiner:
Yeah. Rock the Docs, actually, it came out of a lot of that information that I got from K15t. Customer support, I got from K15t documentation, I got from Atlassian documentation. And then some of the stuff I figured out on my own, or some of my colleagues at K15t did. Essentially like, what are the best practices for creating really good content in Confluence? And it really started with a collection of guides on how to create technical documentation content. It's geared toward like making a public help center, but really it's for any kind of content that you want to be like evergreen, longstanding content to be able to help people.
So we initially talked about all sorts of things like structuring your content, content reuse, managing multiple languages, which can be tricky in Confluence. Collaboration, publishing your content outside of Confluence in one way or another, managing versions of that content. So, that's the start of it. And then we saw a lot of positive response with that and we had more general questions like, "Okay, but what are the best ways to get feedback in Confluence?" Or, "How do I make a template or a good template or how do I make a good diagram in Confluence?"
And so we've grown that content to focus on just all sorts of general Confluence things. Because we found that there's a lot of information out there on how to do something. Atlassian documentation really helpful, but there wasn't as much, I'm like, "Why would you do it? And why would you do it this specific way?" And we've been working with Confluence for over 10 years now. Like I said, I've been with Confluence since the crashy early cloud days. It's grown up so fast, it's beautiful.
But we just know we've done a lot of stuff with Confluence, so it's been a real privilege to share that both in like these written guides. And then actually recently we've started publishing a series to our YouTube channel as well, all about Confluence best practices.Henri Seymour:
That's great. It's real interesting to hear how that started as a smaller project than it turned out to be, because you could see the value in it and the use in it. We've discussed Confluence a few times now and K15t builds apps that use Confluence as a documentation source. Can you tell us more about what makes Confluence useful for building technical documentation? What sort of tools and approaches that make it useful in this context?
Matt Reiner:
Yeah. Confluence is by nature open, which is not the way technical writing tools are built. In fact, I remember the first time I went to a technical writing conference and someone asked me, "Oh, what tool do you use?" Which is like, what technical communications people talk about, because we're all nerds in that way. And I was like, "Oh, I'm doing it in Confluence." And they didn't really want to talk to me after that because they didn't think I was a serious tech writer. And I was like, "Oh no, no, no, no, this is all happening."
At that point, Rock the Docs didn't exist. So I couldn't be like, "Go over there and see how it works." But the biggest difference is most tech writing tools are just totally locked down. You have two licenses for your two people who are trained professional tech graders, and then everybody else, there's no access. You don't touch it. Maybe your tech writers will send you a PDF and you have to go through the God awful process of marking up a PDF to tell them like what to correct. Or, I've heard of teams printing out the content and people penciling in what needs to be changed.
The review processes are just out of this world insane. And those tools don't fit terribly well with agile processes because it's like, you build the thing over here, and then here's the two tech writers over here in their separate tool. And at some point we'll be like, "Okay, this thing's done. Would you write about it?" So with Confluence, the benefit of using Confluence is, it's accessible to everyone on the team and even people outside the team. And that's incredibly by an official because we've seen with agile, but we're also seeing in this technical communication and in information design field, that teams are less and less looking for those specialized individuals who are trained tech writers.
Which that's an oxymoron because half of us, we don't have degrees in tech writing, we fell into it for one reason or another. But now teams are starting to see, "Hey, I can be a code developer and an information developer. I might not write the final piece of written content that is seen by our customers, but I might write the first draft." Confluence really opens that up for everyone. And especially with like at mentioning and inline comments, review processes are just so fast.
Actually, the reason that I switched to Confluence at my last job, was my product manager threatened me and said, "I will not mark up another PDF. Go and find a good tool that we all want to work in." And that's where we landed on Confluence. It's about bringing the whole team into the writing process instead of having it be this separate thing. Because when it's a separate thing, we lose track of it. And content, we forget how important it is to our product, to the customer life cycle, to... God bless customer support, who really, really need that content to be good and accurate.
And it needs to be seen by the real experts who validate, "Yeah, okay, this is correct. This will actually show people how our product works." And Confluence is like the heart of that.
Henri Seymour:No, it's great to hear how that all comes together to build the documentation as a team. Can you speak more to the different roles in, specifically in software development and the different roles you're looking to get involved in your documentation process? We are working on building our specific app teams here at Easy Agile as we're growing at the moment.
Matt Reiner:
Yeah. That's such a good question. Well, what-
Henri Seymour:
And how do you incorporate... Sorry, this is more specific to my question. How do you incorporate that technical writing process as part of the work of an agile software development team?
Matt Reiner:
Well, first, it starts by rethinking priorities because most teams are like, "Documentation down here, testing and then everything else above." So generally, those two things should be moved up. And actually, the content around our product is... I don't want to sound over traumatic, but if we don't have information, we don't have a product. I don't care how much code you write. If we're not explaining it to people, if we don't have good UI text, if we don't have good in-app help, it doesn't exist. It's not a useful tool, it's just a set of mathematics that humans can't interact with.
So content is essential, so it's really important that we elevate it to the position where everyone on the team recognizes that the content experience that our users have is the product experience they have. So it needs to be part of the product development process. So then the next step, which I know you're talking about team structure, but the next step is really everyone on the team needs to know they're a writer, and they're a good writer. And that's important because a lot of people have never heard that. They've never heard that they're a good writer, and they probably have never heard that they're a writer.
I remember going through university, my writing classes were the things that I didn't pay attention to. I was doing mathematics, and Java programming, and statistics. Even that seemed more important to me, not the writing classes. And then sure enough, it turns out everyone has to write. We all write. So knowing that that is a role that everyone fills is really important. And then when it comes to actually team structure, you need to have individuals who are willing to cross the streams, so to speak. If you're bringing in someone who's focusing on test engineering, they need to realize that the test plans they're writing are very similar to a lot of user documentation that needs to be written.
They're writing task topics, or task instructions, do this, do this, do this over and over again. That's documentation. They could be contributing in that way. Engineers, as I mentioned, they could be drafting the first copy of a lot of what are called concept topics. So areas of documentation where you explain concepts, because they already know what those concepts are. In fact, if you look at the root of a lot of agile development teams, they're using epics and user stories and acceptance criteria. And all those map perfectly into the documentation you needed to create for that new feature you're working on or feature you're improving.
So really, it's essential to have everybody recognize, we are all already creating documentation, so we can contribute. And then of course, you really do want to have at least one probably native English speaker. Maybe not native, but someone who feels confident in their English or whatever language you're authoring in. English is typically the cheapest one to translate to other languages, so that's what people go for often. But that person's the person who takes everything everybody's written, gets it to the right style and tone. And then gets it out there. That's what we are seeing be successful.
Like our teams right now, we don't have any legit tech writers. We have product managers writing. We have product marketers writing. We have engineers writing. Some of the best documentation I've ever read was from one of our German-speaking engineers. I was like, "Peter, this is an amazing guide. You got to get out of this Java and get into English, man. It's great. It's great." So he's done a few, which I really love. But yeah, it's about jumping out of your typical roles and realizing, we're all documenting this stuff, anyway.
Henri Seymour:
I love the focus, especially with your German-speaking colleague. The focus on, it's not just that you must write the documentation because you know how the product works and we need that written down. It's, you are capable of writing the documentation, you can do this. You have that added barrier of safety with somebody who's got the language proficiency that they're going to massage it and edit it at the end.
So, before it gets anywhere, anything that you do is going to get filtered out if it's not working. But you don't need a specific tech-writing background to write the docs.
Matt Reiner:
No, absolutely not. In fact, there's an entire community of what... They call themselves documentarians called Write the Docs. And that whole community, that whole group is focused on, it doesn't matter what you do, it matters that you care about writing the docs, contributing to the content. And that's been a big shift, I think in the industry, where people thought we're separate. But now it's like, "No, no, no, we are all able to do this." And once we can respect the contributions that each of us can make.
And then also, I have that protection of somebody else is going to have their eyes on this, which even my writing, I'm like, "I don't like to send it out until someone else has seen it." Because I make spelling mistakes and typos all the time. I really want to have another colleague look at it. Even if they're not native English speakers, because they catch my typos pretty often. That feeling of togetherness, it's the same way that we feel when we ship out a project or a product.
Whether you did the testing for it, or you wrote the code for it, or you did the product marketing for it. It's like, "It's our baby. Let's send it out and see what happens." Content's the same way.
Henri Seymour:
Yeah, part of my daily role and [inaudible 00:28:03]... We don't have QA team separate from developers. Our developers also review our code and it's that sense of, "I wrote this thing, but I have one or two other people who've refined it, who've made sure that it's good enough quality. They've got that fresh eye, so they'll see the spelling mistakes, they'll see the minor little errors that I've just been looking at it too long to notice anymore."
I found the documentation writing process has some parallels in there like, "Here's my thing. I'd like some feedback on it before it goes out into the real world."
Matt Reiner:
Yeah.
Henri Seymour:
That's great.
Matt Reiner:
Yeah, absolutely. Yeah.
Henri Seymour:
All right. Can you talk a bit about the difference between the customer-facing documentation that we've mostly discussed so far and internal documentation?
Matt Reiner:
Yeah. There are some differences and there are some major similarities. So this very... It sounds very technical and ugly. The term information architecture, it's really important with any kind of content, internally and externally. And really that's like, if you're a developer you're familiar with XML, you're familiar with structuring things in that way. Our content needs to work the same way. And that goes for internal and external documentation. So, many of the things that they use, writers, when they write a page or an article in the newspaper, they'll use that Pyramid approach, where they put the broad bits of information at the top. And then they slowly focus in on the topic and give more and more information about it.
But you want to make sure that if somebody only reads the first paragraph, they're getting a rough idea of what the information is. And that's really important for successful Confluence pages and spaces. People should be able to start at the top level of the space, understand what the space is about, and then be able to navigate down into the thing that they really want to learn about into the page itself. Which should then be using headings and subheadings and bullet points to get, again, just disseminate that information and break it down. Because everybody skims.
We need our content to be skimmable, our spaces need to be skimmable. And that kind of content also makes Confluence search happy, especially the new Confluence Cloud search, which has been greatly improved. There's a whole new elastic search base to that that's being optimized. But it's happy, it's just like with Google when we structure our content like that. So when you have a page that is just a wall of text, no headings, you're not breaking it up into pages or even spaces, nobody's going to be happy with that.
The bots aren't going to be happy with it, the people reading aren't going to be happy with it. So it takes a bit of work to structure, break up the structure of our content. It's probably all good as long as it's up-to-date, but it's really essential that we think about, how do we structure that in Confluence so that people can find it and people can skim it? And that is what seems to plague a lot of internal Confluence instances, because a lot of... Maybe the team isn't so focused on that.
It's like, "Oh, our external help center that's come coming from this space over here, that's fine. Our team space, hot mess, total tire fire." And nobody cares because they think they know where everything is. But then you start to think about, "Okay, but what about the new team member? How do they find something?" Or, "What about the team member who's been away for Paternity leave for six weeks? Are they going to remember where everything is or know where all the new stuff is?
What about folks with disabilities? Is it going to be much harder for them to navigate to the information they need? Because they're working with a screen reader and they're trying to go through a wall of text. They need headings, a screen reader relies on those headings and titles." So there's just so many considerations that really leadership of companies needs to understand, just because you have a process to do something or the information is somewhere, doesn't mean you don't have a major information problem. And maintaining all of your content in Confluence and then maintaining it well.That is what enables people to avoid the frustrations of searching for information, losing information, having to relearn or rewrite information. I have worked at too many companies that just information sieves everywhere. I don't even want to call them silos because nobody knows where stuff is anymore either. That's what Confluence brings to things, and that's what matters with internal content pretty much as well as external.
Henri Seymour:
That's a great perspective on it. And I can see the silos, it's a really more... Just a one big pile, you can't find anything. I've been-
Matt Reiner:
Exactly.
Henri Seymour:
... at Easy Agile for more than half of its life now and I've got that sense of like, "Oh, I know I wrote this down somewhere. I know I've seen this written down somewhere." And we are making a habit, especially as we're hiring more and more people. Every time somebody's going through onboarding, they're going to be looking at all of this documentation with no previous background on it. And we want to hear their feedback on it specifically. Because if it works for them, then that's the documentation that we need for them and for everyone after them, and for everyone who's already here.
Especially, I've been at Easy Agile for almost three years now, and I've seen it grow from eight people to now we're up to high 20s, I think. We're going to cross over into the 30s by the end of the year.
Matt Reiner:
Wow.
Henri Seymour:
The growth of information that we have in our internal documentation, and I'm sure it would parallel the growth of the product documentation for a product that's been expanding for three to five years. How do you manage the documentation and the Confluence spaces as the team and the company grow and you just develop more and more pages out of it?
Matt Reiner:
That is the question since the dawn of the universe or at least the dawn of Confluence, which, what's the difference? The biggest thing is team responsibility, so knowing this is our space, this is our content. And not like in a territorial way, but this is our responsibility. Much the way we should think about our planet, we should also think about our content, keeping it groomed and taken care of, and up-to-date and accurate. And then as things change.
For example, we have a product called Scroll Viewport, which is actually what enables you to publish content from Confluence to a public health center, which is really, really cool. So with that, we had a server and data center version. We've had that for quite some time. That's what I was a user of. And then we set off to develop a cloud version, and cloud requires a whole bunch of new infrastructure, which is a lot of fun and very challenging, but it's a totally different beast.
It's not like you can just lift the server code and just drop it into cloud, which is what as a user I asked them to do for years, "why isn't this on cloud?" Now I know why. So we created a new team that started off this Scroll Viewport on cloud effort. And it was just a very scrappy project at first. And I remember the first page we got up there, it's like, "Whoa, look at this page we published." And then it progressed from there. But then at some point, we needed to bring the two teams back together. And what we could have just said, "Oh, this old Viewport space, whatever. We're just going to leave it there and then just go on with the new one."
But instead the team took time and brought the two spaces together and really went through the old content in the Viewport Server and data center space to say, "Is this all still relevant? Do we still need this?" So it's been reordered in such an amazing way. Several of our teams have gotten really good at making these spaces so that I can come in. Because I work with all of our teams, just get in and find what I need, even though I'm not working their day-to-day. I'm just so glad, I'm so proud of the team for not just letting that space languish somewhere or being afraid to delete or archive content, which a lot of people are.
It's like, "No, what if we lose something?" It's like, "No, no, no, we've moved past this. We really do need to delete it." So that's the kind of attitude it takes is, our teams to split and expand and grow, and we need conscious of that content. Because again, think of the new person, think of the person who's learning something new. Think of the person who maybe does have disabilities and is trying to get the content they need. They just don't have the background that you do. Having been with the company for half its life, you know how to dig through the thought pile to pull out just the thing you want, but they don't.
Henri Seymour:
Yeah, and I don't want to be the person that they have to ask every time they need information, "Hey, can you find this for me?" No, no. I want to build a system that means that I don't have to answer the same questions all the time. That's one of the reasons I've been doing internal documentation so much since [inaudible 00:37:36]. I've answered this question once, that will do.
Matt Reiner:
Yes. That's a really good way to motivate any contributors to documentation. "Hey, you know how you wrote that piece of our app that one time and then everybody's asked you about how it works ever since? Just document it once and I promise you can never answer it again." That's good motivation right there.
Henri Seymour:
It is. As well, we've got a team on support models, so I'm working on the store maps and personas, product development team. And that's the same team that gets all of the support requests about story maps and personas. So yeah, the better we make the product, the better we make the documentation, the less of our time every morning we spend doing that. And the more we can get back to our regular jobs.
Matt Reiner:
Exactly.
Henri Seymour:
It's been great for helping us keep in contact with the customers and what they're doing and what information they need when they're using our product. You mentioned that like it's necessary, it's valuable to be deleting an archive-based stuff, pages in Confluence from time to time. When you're looking at a page and wondering whether or not it's time to go, what sort of questions are you asking yourself?
Matt Reiner:
Well, a great one is like, look at the last modified date on that page. That's general a pretty good sign of like, "Are people even looking at it?" In fact, if you're on cloud premium and above, you can look at some great metrics on every page to see like who's looking at this thing? Is this valuable? What are the views like? Just the same way that you would look at your external website to see if your content is valuable or effective. But typically, we have a lot of debris left over from product development or team activities.
Like if you're in marketing and you have a campaign from three years ago, do you really need all of those detailed pages? Maybe keep the overall campaign page, maybe that's useful, but do you really need everything? If you're into testing, do you really need every test plan you ever created? If you're in the legal team, do you really want your legal terms from 10 years ago? Maybe, maybe, I'm not in legal. But often we have this fear of, it's like fear of missing content.
It's like, "Oh no, if I get rid of that, then I won't have it." But information, just like language, just like the way we think, just like the way our teams grow, it changes. And so we need to be aware of that. As we are changing as a team, you should expect our content to change. And part of that is shedding that old stuff. So it's always worth it, like if you're questioning it, ask another subject matter expert and be like, "Hey, I'm pretty sure we don't need this anymore, or we should revise this. What do you think?" But if nobody has any qualms, you should probably delete it.
Henri Seymour:
No, that's great. I am a big fan of decluttering, even digital decluttering. It's, I want people to find stuff and the less pile there is, the easier it's going to be.
Matt Reiner:
Yes. Because somehow bad information is less helpful than no information.
Henri Seymour:
Yes. It's like coming across a question and they're like, "Oh, I tried doing it this way." I'm like, "Oh, that way doesn't work anymore. You're going to have to do... Where did you find that written down? I'll go update out." It's-
Matt Reiner:
Yeah.
Henri Seymour:
... new people doing stuff. The best way to understand where your documentation is falling over. It's the same as you're never going to understand how your product documentation and that your product itself is failing your users until they come to you and tell you, "Why can't I do this thing?"
Matt Reiner:
Yeah. Yeah. In fact that that power of bringing in someone new on your team is so amazing. And it's almost hard to impart like first day of onboarding like, "You have fresh eyes, please use them. This is called an inline comment, please put it everywhere." I remember going through our human resources employee handbook, which we had just created not too long before I joined. And I remember them telling me, "If there's any questions, at mentioned us." And I was really afraid to do that. But we corrected a lot of things.
For example, we mentioned do these things on... What was it called after HipChat? The product that lived and died so quickly.
Henri Seymour:
I think I missed that one.
Matt Reiner:
Oh, the one that Atlassian made and then they sold it to Slack.
Henri Seymour:
Now, where do I even start on that?
Matt Reiner:
How am I... It was a great app, I really liked it. But we mentioned in the employee handbook to use that. And I'm like, "Oh, I think we're using Slack now, we should update this content." That's stuff that HR is never going to go through and catch, but your new employees can do that. New people are the best way to tell you if your processes are bad, if your content is better. Maybe not bad, but they're bringing in something new. That's why we added them to the team. And they should not be afraid from day one to ask questions, or poke holes in our already messed up or failing process.
Henri Seymour:
Yeah. And I can really see the benefit of the tools in Confluence, like that inline comment. Even if you don't know how you need that page updated or what the new version's supposed to be. It's just coming in fresh, you can go, "Oh, this is weird, or incomplete, or it might be wrong." It's just a little comment. You don't have to change it yourself, just say something. Here's a way to speak up without changing it yourself. And somebody who does know is going to be able to change it for you.
I was excited to hear you talk about information architecture. That's something I only got introduced to last year also. Do you have a general explanation of what information architecture is and why it's relevant to documentation?
Matt Reiner:
Oh, information architecture is, there are whole, people, professionals whose entire career is coming in and helping you. So I'm not one of those professionals, I just play one on TV. Really in essence, information architecture is breaking down what would be a wall of text into a pattern of information that anyone's mind can connect to. That's the real and ultimate goal, and that starts by just breaking up logical chunks. In fact, in a lot of pure technical writing, you break the content into tiny, tiny pieces, chunks or some technical communicators talk about atoms of information, really tiny pieces.
And then once you've broken that down and said, "These are separate pieces," then you assemble them together in an order that makes sense. In fact, you can also do really cool stuff with content reuse in Confluence, using include macros and the new Excerpt Include Macro is very cool in cloud, because you can do new stuff with that. But it's really about breaking apart all your content, figuring out what's the order of all of this? What's most important? What's more specific? What is important for everyone? What's important for just a few people?
And then just going down like you would with an XML structure or any other sort of hierarchy and tier that information using your spaces, your pages, your headings. And then finally bullets and paragraphs and that kind of thing.
Henri Seymour:
Thanks for getting that generally explained. Is there anything you want to mention in your work at the moment that you would be interested in getting readers onto?
Matt Reiner:
Yeah, totally. A major new effort for me, because I'm just this content explorer, I guess. I've done like technical content, I've written some marketing content. I started speaking, which I enjoy speaking. I got to speak in front of one live audience before... No, I guess a few, and then, the world's shut down for good reason. Because when you're breathing out on a bunch of people, you want to make sure that you're not potentially putting them at risk. So been doing a lot of virtual speaking.
But recently, I mentioned, we've worked on all these best practices on Rock the Docs. And so we've started this video series about Confluence best practices and it's been very exciting to figure out, "Okay, so I know how to create fairly good in Confluence, how to structure that content. Now, can we make a good video?" And it turns out, no, not at first. Made some pretty poor ones or ones that just took way too much time to make. And finally, as you do with any kind of content, we finally got a good structure, a good rhythm. And we also found what are those things people really want to hear about?
And so we've developed 16 of these now on our YouTube channel that are just out there for administrators to share with your users who are asking these questions. Or maybe these are for users directly who just want to subscribe and get these things. But it's like eight minutes of just as much information as we can pack and still speak fairly legible English. And then show just like how do you do this in Confluence? Why would you do this in Confluence? What are the things you should consider in Confluence? What are the best ways to do things in Confluence?
We've actually just started a series of live streams as well, where we're trying to look at those more in depth and then have people live listening in, asking questions and directing the whole thing. So far those have been really great and we're looking to do more of that. So the more people who pile into those, the more direction y'all get to give that content. But it's been new types of content that it's exciting to see, okay, our good written content in Confluence is coming to the real world in a new format. Which has been cool and challenging and fun and scary all at the same time.Henri Seymour:
Yeah. That's sounds like a really exciting project. Rock the Docs is going audio-visual. And I can-
Matt Reiner:
That's right.
Henri Seymour:
... figure what... Get users on there to give you that iterative feedback that we talked about at the beginning. And so is this worth the thumbs up? Do you have comments? What else can we do? And especially in that sort of live stream webinar format, you get that direct contact with your users so you can find out what they're needing. That's that's fantastic. Probably see if I can come along with those. Easy Agile started using Scroll Viewport for cloud specifically earlier this year.
Matt Reiner:
Oh, cool. Oh, cool.
Henri Seymour:
So that's been a major improvement for us actually.
Matt Reiner:
Oh, good. Yeah. I'm just loving what the cloud team is putting out. It's so exciting and so polished and it's just like every team has that documentation space, and Viewport, it lets you put it out there and you're like, "Ah, looks so great. We're so proud of it." You can read it on any device. It's just like it's the magic that everybody wants, but no team has time. Our very few teams have time to make it look that good, so it's nice to have Viewport just do the heavy lifting.
Henri Seymour:
We've got the Confluence space, we've got the documentation. We don't have to make a website about it. It's just, "Go ahead, please make this website happen. Here's what we need on it. Here's the structure." And golly, it looks a lot better now, even just aesthetically, it looks a lot nice in the house.
Matt Reiner:
Yes. And it's nice to know that like some designer peered over the spacing between navigation items to decide how spaced out they should be. And as a writer, I can just like, I don't have to care. I don't have to care. I can throw in Confluence macros and stuff, and they just look really great when they're published. And I don't know how or why, but I'm happy. I can just keep writing. Yeah.
Henri Seymour:
Yeah.
Matt Reiner:
It would be great to have someone from Easy Agile join us for one of those live streams. Because what we're really focusing on is just like great way to do things in Confluence. We haven't jumped into Jira yet. I'm not as much of an expert in Jira, but I have thought about it because that content doesn't really exist yet. But it's not necessarily app-focused or K15t app-focused. It's just like one of the best ways you've found to do certain things in Confluence, and we're just sharing those with people alive, and it's a lot of fun.
Henri Seymour:
Yeah, that sounds great. I've got the parallel of get really into Jira and making Jira apps and Confluence is, "Yeah, we've got a Wiki. This is where we write stuff down." And it is great to have stuff like "There's the visuals on our docs page." But I don't do those. I'm busy making visuals in a Jira app. I don't want to think about that spacing. I've got my own spacing to do.
Matt Reiner:
Yeah. Yeah.
Henri Seymour:
And it really is that, I can just do the writing, I can just do product. I can do my job more because this other stuff taken care of because the experts at K15t have made that happen. And I hope that our apps can do a similar thing for their users of, this is the thing we need, we don't have to think about this. Bring in this app and it will solve a problem for us. It'll help us see what we need to and organize our information in Jira. Which is a different type of information again, but.
Matt Reiner:
Yeah, yeah. It's funny. I've talked with some people who have actually described that whole app part of Confluence in Jira as App Hell. That's a term that I've seen and I can't help but love the community because we all come up with this stuff. But app hell is, it really comes out of not understanding what a platform is partially. For example, if you're using the Salesforce platform, yeah, that's going to be app hell if you really want Salesforce to be a marketing platform. Because Salesforce is a sales platform. But then there's apps, and Salesforce happens to a sell big one. And then all of a sudden it's a marketing platform.
So that is a really interesting perspective shift for people who are used to a tool that just does one thing. Everybody thinks Excel does everything. It doesn't, we really should just use it for spreadsheets, everybody. It's not a platform for other things. Confluence is really good at these core things, Jira is really good at these core things. And then these apps, they come in to answer the questions that don't have answers and do the things that can't be done. And that's why. So is it App Hell or is it App Heaven? That's the real question. Or maybe it's maybe it's App Purgatory, I don't know. I guess the listeners gets to decide.
Henri Seymour:
The constant stream of, and yet another app needs to update. Which to be fair, I think is not a problem on cloud at this point. That's an exclusively an on-premise problem, the constant app update cycle. But we are hopefully moving towards the end of the purgatory perhaps.
Matt Reiner:
Yes. Yes. I think we're all ascending together. We're just reaching new heights all at the same time.
Henri Seymour:
Is there anything else you'd like to bring up while we talking tech docs?
Matt Reiner:
I guess, I typically go back to when I was in university, I had a manager there who told us in this on campus job that I had, "Our job is to connect people with the resources that are already around them. You're not a teacher, you're just here to connect people." And that has really stuck with me. And that is essentially what we all do. Whether we're building a product that connects people with resources or that is the resource or we're contributing to documentation or some kind of content.
We're really trying to enable people to do that greater thing, that higher level thing that is above our content, it's above our product. It's that thing that they truly care about and any part we get to play and that greater thing, that better thing. That's what it's all about.
Henri Seymour:
Yeah, that's really great perspective. That's probably also a really great thing to round off the end of the podcast with.
Matt Reiner:
I guess so.
Henri Seymour:
Yeah. Thank you very much for joining us, Matt, and for talking all things technical documentation with us on the Easy Agile Podcast.
- Podcast
Easy Agile Podcast Ep.16 Enabling high performing agile teams with Adaptavist
"Really enjoyed my conversation with William and Riz, I'm looking forward to implementing their recommendations with our team" - Angad Sethi
In this epsiode I spoke with William Rojas and Rizwan Hasan from Adaptavist about the ways we can enable high performing agile teams:
- The significance of team alignment
- When and where you should be using tools to assist with your team objectives
- Prioritizing what conversations you need to be apart of
- Advice for remote teams
Subscribe/Listen on your favorite podcasting app.
Thanks William & Rizwan!
Transcript
Angad Sethi:
Good afternoon/evening/morning everyone. How you guys going?
Rizwan Hasan:
Oh, good. Thanks Angad.
William Rojas:
Yeah. How are you?
Angad Sethi:
Yeah, really good. Really, really stoked to be having a chat with you guys. Should we start by introducing ourselves? Riz, would you like to take it?
Rizwan Hasan:
Sure. My name's Riz Hasan, I'm based in Brussels, Belgium. Very newly based here, actually used to be based in New York, not too far from William. We usually used to work together on the same team. My role here at Adaptavist is I'm a team lead for our consulting group in EMEA. So in the European region and in the UK. So day to day for me is a lot of internal management, but also working with customers and my consultants on how our customers are scaling agile and helping them with tool problems, process problems, people problems, all the above.
Angad Sethi:
Yeah. Yeah. Sounds awesome.
William Rojas:
As for myself, William Rojas. I'm actually based out of a little suburban town called Trumble in Connecticut, which is about an hour plus northeast of New York, basically. And as Rez mentioned, yeah, we've worked for a number of years we've worked together, we were running a agile transformation and scaling adoption team for Adaptavist. My new role now is actually I took on a presales principle, basically a presale principle consultant these days. It's actually a new role within Adaptavist, and what we do is we have, actually all of us, I think most of us are all like ex-consultants that support the pre-sales process, and work in between the sales team, and the delivery team, and all the other teams that support our clients at Adaptavist.
Angad Sethi:
Awesome, awesome.
William Rojas:
I help find to solutions for clients and make the proposals and support them through, get them on through delivery.
Angad Sethi:
I'm Angad, I'm a software developer and I'm working on Easy Agile programs and Easy Agile roadmaps, two of the products we offer for the Atlassian marketplace. We're super excited to speak to you guys about how your teams are operating in, like what's a day to day. Riz, would you like to answer that?Rizwan Hasan:
Sure. Yeah. So apart from like the internal management stuff, I think what's particular to this conversation is how we walk clients through how to navigate planning at scale, right?
Angad Sethi:
Yeah.
Rizwan Hasan:
I'm working with a client right now who's based in the states, but they're acquiring other software companies left and right. Which I think is also a trend that's happening within this SaaS ecosystem. And when that happens, they're trying to bring all that work in together. So we're talking through ways of how to visualize all that in an easy way that isn't really too much upfront heavy with identifying requirements or understanding what systems we want to pull in, but more so what do you want to pull in? So really right now, in this phase of the data that I'm working with this client, it's really just those initial conversations about what are you planning? What are you doing? What's important to you? So it's a lot of these conversations about that.
Angad Sethi:
And so you mentioned it's a lot of internal management. Are some of your clients fellow workmates, or are they external clients?
Rizwan Hasan:
They're mostly internal because I manage a team, so I have different people who are working on different types of projects where they might be doing cloud migrations. They might be doing some scripting work. In terms of services, we cover everything within the Atlassian ecosystem, whether it be business related, process related, tool related. So it's a big mix of stuff at all times.
Angad Sethi:
Cool. And is it usually like you're speaking to all the team leads, and giving them advice on agile ceremonies, and pushing work through pipelines and stuff?
Rizwan Hasan:
Yeah, actually, so a story of when I first moved to Brussels, because we've... So professional services started at Adaptavist in the UK, and this was maybe like seven-eight years ago, and it's expanded and myself and William were part of like the first group of consultants who were in North America. That expanded really quickly, and now that we're in EMEA, it's almost like a different entity. It's a different way of working, and a lot of leadership has moved over to North America, so there's new systems and processes and ceremonies and then all that's happening. But because of time zones there's a conflict.
So what I started to do when we got here was to reintroduce some of those habits and consistent conversations to have, to really be much more on a better planning cadence. So interacting with people who would be, say, bringing work to delivery in presale. So folks who are, who work similar to William's capacity over here in this region, and then also project managers who would be responsible for managing that work. Right? So on the equivalent of like a scrum master on an engagement or like an RTE on a big engagement. Right?Angad Sethi:
Yep. Yep. That's awesome. Just one thing I really liked was your terminology. You used conversations over ceremonies or speaks about the agile mindset in that sense, where you're not just pushing ceremonies on teams, where you actually embody being agile. Well, I'm assuming you are from your conversation, but I guess we'll unpack that. What about you, William? What's your [crosstalk 00:06:32]
William Rojas:
I was going to say, one of the things that's interesting challenge that we face, because Adaptavist has an entire branch that does product development and there are product developers, and product managers, and product marketing, and all sorts of things like that. And they set plans and they focus, deliver and so forth, as you would expect a normal product organization to do. On the consulting side, one of the things that's very interesting is that a lot of our, like we have to answer to two bosses, right? Like our clients come in and say, "Hey, we need this," and we have to support them. In the meantime, we have a lot of internal projects, internal procedures and processes and things that we want do as a company, as a practice, but at the same time, we still need to answer to our clients.
Angad Sethi:
I see.
William Rojas:
So that's actually one of the interesting challenges that from an agile perspective, we're constantly facing having to balance out between sometimes conflicting priorities. And that is definitely something that, and although consulting teams at different levels face this challenge. Right?
Angad Sethi:
Yeah.
William Rojas:
So as Riz mentioned, we're constantly bringing in more work and like, "Okay, we need you to now adjust and re-plan to do something different, then manage." Yes. It's an ongoing problem that's just part of this part of this world kind of thing.
Angad Sethi:
Yeah. Okay. I see. And so if I heard that correctly, so it's, I guess you're constantly recommending agile processes, but you may not necessarily get to practice it?
William Rojas:
But more so we're both practicing for ourselves as well as trying to tell our clients to practice it or trying to adjust.Angad Sethi:
I see, yeah.
William Rojas:
You know, a client comes in with needs and says, "Okay, now we have to re-plan or teach them how to do it, or re-accommodate their new emerging priorities as well." So we ultimately end up having to practice agile with and for our clients, as well as for ourselves. It's that constant rebalancing of having to weave in client needs into internal needs, and then the constant re-priority that may come as a result of that.
Angad Sethi:
Yeah.
William Rojas:
And then we're constantly looking for like, how do we make this thing more efficient, more effective? How do we really be lean about how we do the work and so forth? That is definitely one thing that we practice. We try to practice that on a daily basis.
Angad Sethi:
Yeah. And I guess that's a very, a tricky space to be... not a tricky space. It can be tricky, I guess, but adding to the trickiness is remote work. Do you guys have a lot of clients who have transitioned to remote work? And I don't know, has it, has it bought to light problems, which can be a good thing, or like what's your experience been?
William Rojas:
So that's interesting because so I've been doing consulting for over a couple decades, and traditionally, so I've done a lot of that, that travel warrior, every week you go travel to the client to do your work, you travel back and you do that again next week, and you do that month after month. In coming to Adaptavist, Adaptavist has historically always been a remote consulting company. So five years ago it was like, wow, we would go to clients saying like, "Okay, we need you to do this." And we're like, "Yeah, we can deliver that. And no, we don't need to, you know. We may come in and do a onsite visit to introduce ourselves, but we can deliver all this work remotely." So we've always had that history.
Angad Sethi:
Okay.
William Rojas:
But nonetheless, when COVID hit and everybody went remote, we definitely experienced a whole new set of companies were now suddenly having to work remotely, and having to establish new processes and practices that basically forced them to be remote. And I think we've had the fortune of in a sense, having always been-
Angad Sethi:
Yep, remote start.
William Rojas:
... S8's.
Angad Sethi:
Yeah.
William Rojas:
I know whenever we bring on people into the company, into consulting particular, that's one of the things we always point out. Remote work is not the same as being in the office. It has its ups and downs. But we've always had that benefit. I think we've been able to assist some of our clients, like, This is how this is how it's done, this is how we do it." So we've been able to teach by example type of thing for some of the clients.
Angad Sethi:
There you go.
William Rojas:
Yeah.
Angad Sethi:
Awesome. That was actually going to be my next question is what's the working structure at Adaptavist and what sort of processes? I'm sure that it's a big company and therefore there'd be tools and processes particular to teams in themselves. Just from your experiences, what are some of the processes or tools you guys are using?
Rizwan Hasan:
So, in terms of planning and work management, because we started off as a remote first company, and since COVID, business is good. I'll be frank there, it's been good for us because we specialize in this market. We've had a huge hiring spurt in all these different areas, and one thing that I noticed internally, as well as problems that... I wouldn't say problems, but a trend that we're seeing with a lot of other clients is that because of this remote push, and the need for an enterprise to be able to give the teams the tools they need to do their work, there's a lot more flexibility in what they can use, which has pros and cons.
On the pro side, there's flexibility, the teams can work the way they want. On the con side, administration might be difficult, alignment might be difficult. So we're seeing a lot of that with customers and ours. So we're almost going on this journey with customers as we're scaling ourselves, and learning how to navigate this new reality of working in a hybrid environment.
William Rojas:I think in terms of some of the tooling and so forth that we get to do. So we obviously internally we have, we're pretty, pretty much in Atlassian. Atlassian stack, that is very much how we work every day. All our work is using Atlassian tools. All our work is tracked, all our client work is tracked in JIRA, all our sales work, basically everything we do, we use JIRA and Confluence, we're really big on Confluence. We have a lot of customizations we've done to our instance over the years, things that we just have developed, and so that's internal.
I think the other aspect is often, depending on the client that comes to us and the type of work that we're doing for that client, then the types of tools that we use can pretty much run the full gamut. We have a lot of Atlassians, we do a lot of work in JIRA with our clients, like work in Confluence. Sometimes we're working on helping them scale, so we bring on some of the add-on to support some of the scaling practices within to support JIRA. We'll do a lot of JSM work. We do often DevOps work, and then we'll bring on a lot of the DevOps tool sets that you would expect to find, so things to support delivery pipelines.
So it really depends quite a bit on the client. We even do some agile transformation work. And then there, we do some a lot of custom build things, practices and so forth. And we bring in surveys and tools that we've been able to develop over the years to support that particularly. So a lot of the tools often are dictated by what the client and the specific engagement call for.
Angad Sethi:
In my personal experience recently with COVID, I find myself in a lot of meetings, we are experimenting with, with Async decision making. Have you experimented with Async decision making processes yet?
Rizwan Hasan:
I'll start by saying I hate meetings. I think most meetings are a waste of time, and I tell my team this. And I'm like, "If we don't need to meet, like we're not going to meet."
Angad Sethi:
Yeah. Awesome.
Rizwan Hasan:
And I think that really comes. Yeah, awesome, for sure. Awesome.
Angad Sethi:
I love it.
Rizwan Hasan:
But it comes down to really is when you do meet, are you having the right conversation? And I think a key component being like an agile team, quote-unquote, is you have an understanding of what we all are doing collectively and what the priorities are. Which is tough to actually get. So when we talk about like asynchronous decision making, with a team that has some degree of understanding of what priorities are, what goals are, it gets easier. And you can have more low impact interactions with people.
So we use Slack a lot and we have a lot of internal bots on our Slack to be able to present information and collect feedback at asynchronous times, because there's voting features, there's places where you can comment. And I think when we talk about teams that are growing across the globe and also time zones and flexible working, that's a real thing now. There's a practical way of how to do that, that we're starting to dig into what does that look like?Angad Sethi:
Do you find yourself in a million Slack groups?
Rizwan Hasan:
Yep.
Angad Sethi:
Yep. You do. Do you see any extra hurdles you've got to skip because of that? Because you maybe, do you find yourself hopping from conversation to conversation, whereas it would just be easier if everyone was in the same conversation? Does that happen a bit?
Rizwan Hasan:
Yeah. Yeah. All the time.
Angad Sethi:
I hear you, yeah, there you go. Okay. Cool.
William Rojas:
But I would say we have a lot of impromptu. I think we do have a lot of impromptu meetings. And sometimes we may be in a Slack typing away. It says, you know what? [crosstalk 00:17:29]
Angad Sethi:
Just jump in a huddle.
William Rojas:
Into Zoom and then let's chat or Slack conversation, and then just face to face conversation, and then just address it then and there. But I think we have been looking at, it's almost like I think a balance between the time spent on the meeting, and the amount of people that need to be in the meeting, and the benefit and value that comes out of that meeting. And a daily meeting where work was people would pick up work or support from a sales perspective. And it was very, very much necessary as per part of the work coming into the consulting pipeline. But it felt very inefficient.
So that's one of the means, for example, we did away with, and it's now a completely asynchronous process, by which work comes in and it gets allocated, people pick it up, people support it, we deliver things, we track where things are and so forth. And we now use all of that is basically all done through Slack. So we did away with all the meetings around, "Hey, who can help with this?" But meantime, we have another meeting where we're trying to get people on projects. And that is very much a, we need to negotiate on that often. So that's a meeting that's still very much done.
Angad Sethi:Yep.
William Rojas:
Everybody comes in, we all talk, we decide what we need to get done. People balance back and forth. So that trade off I think is really important to really understand what, there are meetings that are necessary, very valuable, and they should remain. And there's ones that really a Slack is a much better mechanism to be able to make those kind of decisions
Angad Sethi:
Yeah. Very true. Yeah. And does it well, sorry, firstly, pardon the location change. I'm sitting right next to the router now, so hopefully the iPhone holds. What sort of a scale are we speaking about here in your Slack? The reason I ask is with larger organizations, it can be harder to scale. Therefore I'm just trying to get a gauge of what scale your Slack is at.
Rizwan Hasan:
So we just hit, we are just over the 500 mark, that'd be in terms of employees. With basically our general, which seems to be, I think, I don't want to say universal, but the standard across any organization that has Slack general as the best indicator of how many people you have logged on. So we're just about the 500 mark, which I would say is probably around mid-size, but it's definitely getting to the point where we're starting to see, it's almost a little bit too much in order to disseminate information, find their information, etc.
We're actually partners with Slack also. So we work with them pretty closely on some opportunities. [crosstalk 00:20:39] Yeah, exactly. And we're starting to talk with customers also about the same problem, about how much is too much, and when do you start to form communities around people that are delivering the same type of value. So those conversations are more aligned and there's not just a whole lot of chatter and people get confused, like when they read Slack and like, "Oh, is this the priority now? Or am I supposed to be doing this or change in process?" That communication is harder now, I think, really. And this is where a lot of folks, I think, who are moving to this remote environment are struggling with, is that alignment communication.
Angad Sethi:
Yeah. Very true.
William Rojas:
And it is, I would say fairly organic, like our channel proliferation. We do have, I would think even for company of our size, we're pretty loose about how channels get proliferated, who gets to create them, what they're for and so forth. But then it gives the flexibility of based upon your interests or the context of what you need to communicate on, then you can either join a channel that supports it or create a channel if necessary to support it. So it is, in that sense, pretty organic. But it is true that there are hundreds, if not thousands of Slack channels that we have, and so kind of staying like which one should you be on, is definitely one of our biggest challenges.
Angad Sethi:Yeah. Well, that just blows my mind just because like 500 people on a Slack. Our whole company is 35 people and I'm pulling my hair out being in too many Slacks. So well A, that blows my mind.
William Rojas:
It does allow us, for example, to have client specific Slack channels. So anybody, if you need to talk about, if you're working on a particular account, you're working for a client, then there's a channel for that. And if you're working on another client, there's another channel. The thing I find helpful about it is that it gives you that context of if I want to communicate with so and so, if I communicate with Riz on a particular account, I will go to the account channel. If I want to talk to Riz one-on-one, I go to a one-on-one chat.
Angad Sethi:
I see, yep, the flexibility.
William Rojas:
So we do have that benefit of where to put the information. But it does mean that I have probably over a hundred channels in my roster of things that I follow, and I'm always behind.
Angad Sethi:
Yeah.
William Rojas:
Well, yeah. So the next level of it is, then you begin to prioritize which channels should I really be notified about, and which ones are most important. I want to track those. And I try to keep that list to a minimum in terms of unread messages, and the stuff that I try to get to, and I'm bored and I have nothing else to do so, but yeah.
Rizwan Hasan:
I've been leaving a lot of channels too. I've been just really cutting the cord with some channels. You know, I had some motivation to really help out here, but I just can't and it's just too much noise. And just got to cut the cord and be like, if it's empty, there's no conversation happening or if it's slow, then move on.
Angad Sethi:
Yep.
William Rojas:
We also have the ability to, you can get added back in. So sometimes you leave and then somebody will put you back in, like, "I need you to talk about this." But it is pretty organic. I know we do leave it up to the individual to decide how best to manage that.
Rizwan Hasan:Yeah.
Angad Sethi:
That's awesome.
Rizwan Hasan:
We had a instance today, actually, where there was an old, it was basically a sales opportunity, a customer who had reached out to us for a certain ask, and we hadn't heard from them for months, like eight-nine months. And someone posted, someone who I'm pretty close with on our sales team posted, "Hey, this is kicking back up again, but I don't have the capacity." And I just left immediately as I saw that message. I was like, "I can't help out. Sorry."
Angad Sethi:
Yeah. The old so-and-so has left the group is a bit of a stab in the heart, but yeah.
Rizwan Hasan:
Yeah.
Angad Sethi:
We will get over it. Just coming back to a point you mentioned, Riz, you said you used the words, alignment and communication. Both of you when consulting with clients, are those the two main themes you guys like to base your recommendations around?
Rizwan Hasan:
I'll give you a very consulting answer and say it depends.
Angad Sethi:
Yeah.
Rizwan Hasan:
But when we engage with a customer, one of the toughest parts of our job is understanding if there is even alignment in the group of people that we're talking to as well, because at the scale of projects that sometimes we work with, we have like 20 to 25 people on a call. And of all of those people, they may have different motivations or objectives of what they're wanting with their engagement with us. So I would say, that's primarily what's driving what we're trying to find out, what we're trying to do with them is get some alignment between the group and ourselves, and communicating that is not always easy.
Angad Sethi:
Yeah.
William Rojas:Let's say, adding on what Riz, that also depends quite a bit on the specific engagement with that client. So in particular, if the engagement, because if an engagement is like, "Get me onto the cloud." Okay. You know, come in. Often there's much better alignment for something like that. If the engagements are more about, "Hey, help us scale agile, help us get better at how we deliver." Then the need for alignment, the need to make sure that we're all communicating correctly, we all understand, we all come to the meeting with the same objectives and so forth, is so much more critical.
Angad Sethi:
Yeah.
William Rojas:
So in those kind of engagements, we're constantly realigning. Because it's not even like we had the alignment. It's like yeah. Okay. We have it, next week it's gone. We got to go back and get it again. So that keeping, making sure that everybody's marching towards the same set of objectives, defining what those objectives are, letting them evolve as appropriate and so forth, all that becomes so much more critical.
Angad Sethi:
Yeah.
William Rojas:
And that's where the tools, that's where things like JIRA and then again, like how do we scale? How do we show what everybody's doing? And so forth, that's where it becomes that much more important. And in those kind of engagements, the tooling becomes essential. Not that the tooling's going to answer it, but the tooling becomes a way by which it helps us communicate, yeah. This is what we all agree we're going to do. Okay. The tool says so because that's the decision we've made.
Angad Sethi:
Yeah.
Rizwan Hasan:
It's really interesting that you say cloud migration, William, like when you say, "Okay, I'm moving to cloud, we know what the alignment is," but even then, I'm finding is that, especially within the Atlassian ecosystem, because that's what we're exposed to all the time, but when we're moving data from a completely old infrastructure to something brand new, it's not going to be the same. And you have folks who are thinking that, "Oh, we're just going to be taking all this stuff from here and putting it over there." But what usually doesn't come along with it is that you're going to have to also change the way you work slightly. There's going to be changes that you're not accounting for.
And that's where the alignment conversation really is important because we work with small companies who understand, okay, moving to the cloud will be completely different. We also work with legacy organizations like financial institutions that have a lot of red tape, and process, and security concerns, and getting that alignment and understanding with them first of what this means to move to a completely different way of working, is also part of that conversation. So it's a constant push and pull with that.
Angad Sethi:
Yeah, yeah. It's really heartwarming to hear the two of you deal with the JCMA, which is the geo cloud migration system.
Rizwan Hasan:
Quite a bit, yeah.
Angad Sethi:
That's awesome, because yeah, that's something we are working on currently as well. So I'll end with a super hard question and I'll challenge you guys to not use the word depends in there. And the question is the number one piece of advice for remote teams practicing agile. Start with you, Riz.
Rizwan Hasan:
Get to know each other.
Angad Sethi:
Yeah, okay.
Rizwan Hasan:
Keep it personal. I think one of the hardest things about this new reality is making that connection with someone, and when you have that, that builds trust, and when you have trust, everything's a lot easier. So I'd say that. People really aren't... The enemy. That's not the right word, but work shouldn't be a conflict. It should be more of like a negotiation, and if you trust each other, it's a lot easier to do that.
Angad Sethi:
Yeah.
Rizwan Hasan:
So yeah.
Angad Sethi:
That's awesome.
William Rojas:
It really is.
Angad Sethi:
I'm going to definitely take that back with me.
William Rojas:
Yeah. And just if I could quickly add to that. That's like looking for ways how to replace the standing around by the, having a cup of coffee. How do you replace that in a remote setting?Rizwan Hasan:
Yeah.
Angad Sethi:
Yeah.
William Rojas:
How do you still have that personal interaction that maybe there's an electronic medium in between, but there's still sort of that personal setting. I think that's one of the things you're looking for. Because yeah, it is very much about trust. And I think to that, I would also add, back to the alignment. Right? Because in some ways that strong interaction helps build and maintain the alignment, because often it's not so much that you get alignment is that you stay aligned.
So it is this constant, and having those interactions, having that trust and so forth, is what in a sense allows us to stay aligned. Because we know each other, we know how to help each other, we support each other, so we stay in alignment. So the trust and so forth are a good way to help build and maintain the alignment itself that you're looking for. That's absolutely. In remote world, you don't have the benefit of seeing each other, the whiteboard, all those things are not the same.
Angad Sethi:
Very true. Getting cup a coffee, yep.
William Rojas:
But we still need to stay in sync with what needs to get done. That's so important.
Angad Sethi:
Very true. And so would you guys want to drop any names of tools you're using to facilitate that trust between team members in a remote setting?
William Rojas:
So I would say, like I mentioned from my role, one of the things that we do is in the presales area, we support some of our larger accounts, almost as more of like a solution account manager, per se. So we come in and help make sure that the client is getting the solution that is meant to be delivered. So we work with the delivery teams, we work with the client, we sit in between.
There's one large client that we've been working on for years now, and we basically, to the point that they're moving towards some flavor of safe. That I wouldn't call it fully safe, but they do have a lot of safe practices, but they do PI planning, and so we come in and join the PI planning. That's actually one of the, like I said, how do you stay alive?
Angad Sethi:
That circle. Yeah. [crosstalk 00:33:15]
William Rojas:You pull up your program definition, you look at what features you want to deliver in the PI, who's going to deliver that feature in the PI, and then in your readout, go back to the tool and say, "Look, this is what we've agreed to." Others can ask questions and so forth, and constantly going back to... For example, just last week, we're doing now sprint planning and saying, "Actually, okay, this feature's going to drag on another sprint. Let me go back and readjust in," this client is using the Easy Agile programs. The original plan of saying this features not going to be, not two sprints, but the three sprints instead, for example.
So that habit of getting into using the tool to communicate what we decided and what we just had to make changes to. So it becomes this, a communication vehicle, it's really important. Yeah, they use programs, they use the roadmap piece of programs to help them do their PI planning, and stay in sync with what it is that ultimately gets communicated out at the end of PI. And then during the sprints of the PI itself, and it's very helpful for them. Again, there's I think they have seven trainings, and they all use that to help stay in sync, stay aligned.
Angad Sethi:
Awesome. Awesome.
William Rojas:
One other quick thing I'll say is, I think there will be, some of where we've gone will now become status quo, become permanent. So I think that this has been as shift across the market, across the industry, across company, how people work. So the idea of remote work, the idea of using tooling to really establish communication, and help facilitate communication, all that, while it's been around, I think the big difference is now everybody, like you have no choice. Everybody has to do it.
Angad Sethi:
Has to. Yeah.
William Rojas:
And I think we've definitely seen a big shift across the entire industry because of that. That will now solidify and let's see what the next level brings. But I definitely think that we've reached a new stage of maturity and so forth pretty much globally, which is pretty cool.
Angad Sethi:
Yeah.
Rizwan Hasan:
Yeah.
Angad Sethi:
Yeah, it is. Thank you guys. I won't keep you too long. I think, has the sun set there, Riz? I can see the reflection going dark.
Rizwan Hasan:Yeah. It is getting there. Yeah, for sure.
Angad Sethi:
Yeah. Yeah. I won't hold you guys for too long.
Rizwan Hasan:
All good.
Angad Sethi:
But thank you so much for the conversation. I honestly, I took a lot away from that. And yeah, I hope I can add you guys to my LinkedIn. I would love to be in touch still.
William Rojas:
Definitely.
Rizwan Hasan:
Yeah, sure.
Angad Sethi:
Yeah. Trying to establish a point of contact, not to add to one of your Slack channels, but yeah. Just so that we can be in conversation regarding the product and improving it.
Rizwan Hasan:
Yeah, sure. And we have a partner management channel. I know we've been talking to Haley a little bit.
Angad Sethi:
Awesome.
Rizwan Hasan:
She was reaching out, that's about some other stuff.
Angad Sethi:
Beautiful.
Rizwan Hasan:
Yeah, happy to. We engage with your product and it's in our white papers too, and we're going to put out another white paper this year where we're going to talk about Easy Agile too. So yeah. We'll stay in touch.
Angad Sethi:
Cool.
William Rojas:
I just gave you, so my LinkedIn is under a different, my LinkedIn is not with my work email. Because that way I can keep the same account place to place.
Angad Sethi:
Sounds good.
William Rojas:
Yeah. You can look me up on LinkedIn with that.
Angad Sethi:
Wicked awesome. Thanks guys.
William Rojas:
Awesome. All right.
Angad Sethi:
Have a good day.
- Podcast
Easy Agile Podcast Ep.30 Aligned and thriving: The power of team alignment
"Every time I meet with Tony, I'm always amazed by his energy and authenticity. In this conversation, that really shone through."
In this episode Hayley Rodd - Head of Partnerships at Easy Agile, is joined by Tony Camacho - Technical Director Enterprise Agility at Adaptavist. They are delving into the highly discussed subject of team alignment, discussing what it means to have synchronized goals, cross-functional collaboration, and a shared agile mindset.
They also cover the fundamental building blocks to get right on your journey to team alignment, like the power of listening and embracing mistakes as learning opportunities, stressing the importance of following through on retrospective action items + so much more.
We hope you enjoy the episode!
Share your thoughts and questions on Twitter using the #easyagilepodcast and make sure to tag @EasyAgile.
Transcript:
Hayley Rodd:
Here at Easy Agile, we would like to say an acknowledgement of country. This is part of our ongoing commitment to reconciliation. Easy Agile would like to acknowledge the traditional custodians of the land from which we broadcast and meet you today. The people of the Darova-speaking country. We pay our respects to elders past, present, and emerging, and extend the same respect to all Aboriginal, Torres State Islander and First Nations people listening in today. Hi all and welcome to the Easy Agile Podcast. My name is Hayley. Here's a little about us here at Easy Agile. So we make apps for Atlassian's Jira. Our applications are available on Atlassian's marketplace and are trusted by more than 160,000 users from leading companies worldwide. Our products help turn teams flat Jira backlog into something more visually meaningful and easy to understand.
From sprint planning, retrospectives and PI planning our ups are great for team alignment. Speaking of team alignment, this is what this episode is all about. Today I'm joined by Tony Camacho. Tony is the technical director of Enterprise Agility for Aligned Agility, which is part of the Adaptiveness group. I've met Tony a few times during my time here at Easy Agile and have learned that he's one of the most generous people along with being funny and a clever human being who is incredibly knowledgeable about Jira and a bunch of other agile related topics. It's really wonderful to have Tony on the podcast today.
Hey, everyone, we've got the wonderful Tony Camacho on the podcast today. This is our first time recording from our Easy Agile Sydney office, which is super cool. Tony, I'm not sure if you know, but Easy Agile is based out of a place called Wollongong, which is just south of Sydney. But we've got a Sydney office because we've hired a bunch of Sydney team members recently who wanted a place to come and hang out with each other. So we created this space, but it's 7:00 AM in the morning, so I'm all alone right now. That's how much I love you. So Tony, let's get started on the questions. Team alignment. What does it mean for a team to actually be aligned?
Tony Camacho:
So for us in an agile space that we're having, it's a collective understanding, a synchronization of your team members towards goals, principles, your practices that you're going in. Even more so I would even go down to the point of cadence, you would have those synchronizes. So it's a matter to be consistent with your agile principles and values, your mindset, your shared goals and vision, your synchronized work practices, DevOps, [inaudible 00:02:44], how we're going to put this out. Cross-functional collaboration between the teams, getting your tea shaped partners/teammates shining at that moment, learning from each other, roles, responsibilities things of that type. That's what it means to me. It really means.
It's all about human beings and at that point, having everybody aligning and working to our common goal, that objective that we want to do for the business partner. There's the gold that we're all after as a team. Does that make sense for you guys? We have the same objectives for this initiative and our practices. And finally for me, which I know this is not typically is we're coming to an agreement on the tools we're going to use and how we're going to use them and have a system source record where we know where we can get our troops, our dependencies, find out which teams do have capacity and move forward from there. That would be my overall definition of an agile team.
Hayley Rodd:
Wow.
Tony Camacho:
And teams.
Hayley Rodd:
You've had lots of experience over the years. I guess where my mind goes when you say all those really wonderful things about team alignment is that in my experience when team alignment is when people get it right, it's super great. When people get it wrong, it's really hard. And I actually think it's pretty hard to get team alignment right. You got to really work at it. What's your experience in that?
Tony Camacho:
To me it's like it can be a bad marriage or a great marriage, but it needs work. As we know, all relationships need work. We're human beings, we're not the same. Each one of us brings something to the table of value. So let me give you one example that I've lived with on a team. I'm an extrovert by nature, and I'm a developer, an engineer and typically that is not two skill sets that you hear together. So I've had to learn that when I'm working with my teammates that happen to be sometimes introverts slow down, listen, wait. They've also had to try to learn to respond faster because as an extrovert, if I ask you a question, all of a sudden I'm looking at you, I'm not getting a response, I'm thinking you're not understanding the question. I rephrase the question and now you're in a deficit to two questions.
And now I'm even worse because now I'm like, "Hayley isn't understanding me. What's happening here? Let me rephrase it again." And it can easily fall apart. What I have seen when teams aren't in alignment is that the team isn't a team any longer. It's miserable to go to the team. It's miserable to come into work, when the team is truly aligned, you're rocking and rolling. It's a feeling like you've never had. It's hard to explain to people that when you see the team, because you know it when it's working and you obviously know when it's not working, you're starting to miss deadlines. Integrations aren't happening on time. You don't have a single source of truth. You start having people explaining the same thing in two, three different matters, different priorities. We're not working from the same hymnal. The thing that I took from my... I'm an SPC, so as an instructor, the one thing I always try to explain to everybody, you may have the best of everything out there, but that's not necessarily mean it's going to work together.
So you have to have that type of understanding, how we're going to work together, what is our priorities, what's the tool sets we're going to have and what is our values as a human beings to this team if that... I'm hoping that helps describe some of the things that I've seen that have gone really bad. I have seen it at, I can share a customer that I have seen it gone, but we started off with good intentions. It's a financial institution in the United States and they were trying to make the jump to mobile applications. And at first we were on the same page as a team, but they decided that they didn't believe that cadence was required to be the same across the board. They didn't believe that we could use the same one tool set, we could use multiple different tool sets.
They had spreadsheets flowing all over the place. And what was happening was we lost trust. We were redoing work, there was ambiguity everywhere. We were misaligned and we started paying for it because our customers started complaining. They could see it in the quality of the work. One team had one schema, one background, one type of... You could see the difference when they integrated, it seemed like it was two applications being put out there mashed together. And when you're misaligned, that comes through very, very quickly in your work. There's a saying that we have here. There's a scrum master, I know her name was Sophia Chaley, one of the best I ever met. And what she will always tell people is what a team delivers is what the team is doing is learning. It's building knowledge, it's expressed as code. When we're misaligned, we're learning different things and we're expressing it differently in the code, if that makes sense.
Hayley Rodd:
Like thinking about the fundamental building blocks of team alignment, is there something that a team really needs to get right to be successful at alignment? And what is that in your mind?
Tony Camacho:
Oh, that is for sure. They had to get that right. First of all, the size of the team.
Hayley Rodd:
Yeah, okay.
Tony Camacho:
Human beings, and I'm not referring back... Going back to say for our scrum practices, I am a CSM. I do know they recommend 8 to 13 people. My best teams have been typically a little bit larger than that. But we had to have the same agreed to the size of the team where it didn't became, didn't become too large where we were over running each other and we weren't listening to each other. We had to understand our goals. We all had the same goals. We used to practice this by, when I worked at Microsoft, we used to have what we used to call our elevator speech. And we would stop somebody and I would go, we're working on this. Watch your elevator speech for this. And if your elevator speech wasn't... It wasn't meant that it had to be in sync with mines, but if I didn't understand it, we had a problem.
Or if it was a different goal where I'm looking at you going, but we're building a Volkswagen, but you're describing to me a Lamborghini, we have a problem. And those were the type of things that we also had to have to make sure that we had the right... Same practices and the tools. That's where I find Easy Agile exceeds. I mean it just exceeds, it meets above the market. It's transparent and it shows everything in front of you right there for me. So when we had the same tool and we were having the same cadence and we could see our dependencies and we could see what I had to deliver for somebody else or somebody had to deliver it for me, that was the types of things we had. We had to have respect. Somebody seems to always forget that we always had to have respect for each other.
We had to embrace the same values of collaboration, adaptability, transparency. The practices that we all know, but somehow we seem to forget when we get into a place where we are not aligned and if you respect my ideas and I respect yours and we're working together, we do not have to agree. But that respect will drive us a long way towards getting to that project vision that we want. And we're trying to meet the customer's needs. And those are the type of things that we needed. We needed leadership. Leadership, I can't say, and if you notice I'm not using the word management, leadership is where you're putting yourself out there in a situation where it can go bad for you as a person, as that leader, trying to make sure that we're making the right choices empowering the people and making them very clear what they can make decisions on and they can't. And it sounds so simple when I talk to you like this, but every time I've had to do some type of transformation, the baggage that sometimes we bring as human beings, the fears, the lack of trust that we have, that's where the scrum masters of product owners come in. And then you need something to make sure that you're having that vision to communicate that vision across. As I mentioned before, some of the tool sets that we have out there. Is that making sense for you at all?
Hayley Rodd:
Yeah, it really does. It's really resonating with me. I think when you talk about coming together as a team and putting together a set of values and a vision, it seems so much like a a "duh" moment. It's like, of course you would do that as a team, but I think at the end of the day as teams, we get in the daily business as usual and we think, I don't have time to get together as a team and set that vision because I've got to do X, Y, and Z, that's due next week. But I think it's one of those fundamental building blocks that really sets you up for success to do X, Y, Z quicker down the track. So that's what I've taken away from that.
Tony Camacho:
And I would agree with you. And you came up with a perfect example because a lot of people do that. I have ABC to do for next week, daily. I don't have time. And the problem is that if they would suddenly realize, and it does become apparent to your practices. So once you agree on your practices, your daily standups, if you're doing that, your retros at the end of your sprints and moving forward, once the person feels that they have that respect for you and they're not fearful, they can share that with you, "Hayley, I'm having a problem. I'm having way too much work. I don't know if I am going to be of value here. Or Do you really need me?" "Yes Tony, I do need you, we're going to discuss this and let's discuss your A, B, C and see how I can help you." And they suddenly realized they're not on an island alone. Developers by nature being introverted, we have to break that habit. We have to be able to share. And it's funny, I'm not saying share my lunch, fine, sure, let's share our lunch, but share the workload.
The one thing that I always try to mention to teams, and again that's... I'm sorry, but I do believe in Easy Agile, using this tool. That's where easy Agile also to me makes it apparent. A story belongs to a team, not to a person. And once you know that you suddenly realize, I'm not alone. I'm here working as part of a bigger thing. And most human beings want to be part of a bigger thing. You suddenly realize that it's almost like the baseball metaphor that I use for teams. And I know the market is not baseball, but I think it would apply for other sports, be cricket or sports like that. When I'm batting, it's me against everybody. When I'm on the field, it's us against... I prefer being with the us. And generally that's where things like that, let's do that.
Also, when you're working with more people as a team, there's things that happened there. You minimize the project risk, which I hate using the word project. It should be initiative. It's long living. You're usually a much more adaptable. I don't know all the answers. So when I worked with you, Hayley, and you showed with me some things there, you're one of the most humble people I've met, and I loved it. But when you walked through, you walked me through the tool, it became very apparent, you know it, you feel it, you love it, it's part of you. And that to me is invigorating. It's energy. Who wouldn't want to work with somebody like you? Why not? Let's do this. Right?
Hayley Rodd:
Thank you Tony. I guess one of the things that I wanted to touch on is when you're in a team and you're coming together as a team, you're working on something, how does an individual who seeks recognition for what they're doing, how do they get that? Or how do you leave that? How do you put that ego aside and say, "I'm doing something as a team to the better of the team?" Have you ever come across that or considered that? I'm interested in your thoughts.
Tony Camacho:
So the people that I felt that needed to have that typically how I... Yes, that's a great question because I'm thinking specifically. There was one, a scrum master that I thought that did it the most amazing way ever. Basically she would call out the ideas even if it wasn't that person's, yeah. I feel that Hayley is... You're not having a good day, Hayley. You're not having a good day. And I know you are not getting used to doing, working in the scrum team. It's new to you and everything else. And what she did typically was in front of everybody would be, and it wasn't even your idea sometimes. And she would just say, and Hayley came up with this wonderful idea that's going to save us something, move us forward. Hayley said this to me, it made us think as a team. And we went around it, we talked and we did it.
And that person always usually would be like, "Wow, I got credit for something. Good scrum-masters will see that. Or good product owners will point that out." The other way that I've done it was using something like Easy Agile. It's a great tool to use, believe it or not. I would back off, I'm a developer, but I also played the role of Scrum masters for years. I would step back and I would let one of my teammates run it, hear their voice, feel empowered. It's amazing when you can have people feel empowered because what you're all talking about, there really is about a lack of trust, a lack of psychological safety. And it's for us to be an aligned team, you have to have trust there and you have to break down the fear of judgment. So the other thing that one time happened with a scrum master that I thought was wonderful was is that again against Sophia Chaley, chief stood in front of her room when there was this a bad sprint.
The sprint didn't end well. And she stood up in front of everybody and she basically went, "Sometimes you win, sometimes you learn. This was a learning sprint." She pulled up Easy Agile, she was using at a time, pulled it up, showed the things that didn't work out the way they thought they were going to work out. And she said, these are the actions we're going to take to improve this. And then when somebody who was in management, again not using the term leadership, now I'm using the term management on purpose, was looking to assign blame. Her response was, not screaming, not raising her voice. Her response was, if we need to get rid of somebody or blame somebody, blame me. But I'm here to solve the problem. Let's move forward.
Hayley Rodd:
Wow.
Tony Camacho:
She wouldn't tell. And that was to me was one of the most outstanding moments I've ever seen. And she was at that point actually using Easy Agile that wasn't a financial institution in the United States. I would let you know that teachers use it, figure it out. And she basically showed the board and just went through everything and did that. That was leadership. That was leadership. And generally your teams will follow leadership and they will suddenly step up and you'll see that that's what people who want to stand up. Now, not everybody wants to do that. Some people want to just be team members and that's okay. That is perfectly okay, but the thing that's not okay is that if they don't have trust, right? And to me, that's the biggest thing. When you have people who are resisting change or siloed in their world, they suddenly realize if you can get them to open up it's really, they're just telling you, I don't feel safe.
I've been doing this all my life. I'm great at it and now you're asking me to do this. And you need to somehow get them to get the feel that they are bringing something of value. They are helping you move forward. And you're meeting them halfway if you have to. But yeah, that's the biggest problem I've ever seen that we've always, it always comes down to the human being in that. The rest of it, you can always come, you can always change that. But there's some of the things that you also have to do. I think that some people run into Hayley that I think me and you live in our world as we're moving up is sometimes we are, there's an ambiguity of the things that we have to do. And I've seen you do that, people in our roles will have suddenly, even if it isn't part of our role, will take it on and we have to learn. That's it. But yes.
Hayley Rodd:
Yeah, I think that, yeah, it's so true that the [inaudible 00:19:23] the psychological safety needs to be there. And I think back to so many teams that I've been a part of that it isn't there. So you have to feel like you got to lay your mark or put your mark on something and show your value. Because if you're not showing your value, then you get questioned. And so I think that that's such a common thing that I see in teams and it actually creates, not a camaraderie, but a competition between teammates and it breeds the wrong environment. So it's just really interesting. One thing that I did want to touch on that you spoke a lot about a couple of questions ago was respect and making sure that teams have respect for each other. How does a team member show respect for their teammates? What are some really good examples of respect and how can we display it or embody it or enact on it as team members?
Tony Camacho:
So let me show you a lack of respect right now. Yeah. Hayley, we're talking about this.
Hayley Rodd:
Looking off camera, avoiding me. Yeah.
Tony Camacho:
One of the main things was to really to learn to listen. Sit down, believe it or not, I found the best thing is sometimes taking a deep breath, listening, not responding, recognizing what that person may be feeling and going through at that moment because it's hard what we do. It's half art and it's half science. Let them learn that making a mistake is not a failure, it's a learning moment. Have that discussion there. Take their concerns real. So it's funny because you just made me think of something. That's one thing where I could show respect to my teammates would be as a scrum master, if I was a scrum master, hold effective retros. Really listen to what they're saying in the retros, report back on the things that you said you're going to improve in the retros. So we said these are the three things we're going to improve on or these are things that are assigned to me.
Make it real. Make it a story. Show it on the board and say, "This is where we're going. This is what's happening. This is what I'm blocked by. Can somebody help me?" But I am working this for you. Get them, really be sincere. I don't mean buying pizza or bring a lot of scrum masters will bring pizza and donuts to the office. No, it's make their lives really better. Be that advocate up for them. And if you're a teammate, be an advocate for each other and be sincere. Have the bravery to stand up and say that's not a fair assessment. But the biggest thing is to really listen. Because a lot of times when somebody's saying something to me, I'll make it personal. Me, I have sometimes have, I know I'm feeling uncomfortable, but I cannot explain why. And just having you there, looking at me and talking and going through it, I suddenly realize it may have been something different and I want to hear your ideas.
But I would have to, if I wanted to show myself to help that teammate, I also got to make myself vulnerable. If you're coming to me, I should share, but I should active listen, right? And really I respect your different perspective. It's okay. We all have different perspectives. Problem I find is that in ourworld, that we're moving so fast sometimes we don't stop to listen. We lack patience. We're moving too fast. So I'll share one for you that I'll be sincere. I had something medically came up and I was being a little abrasive with the team. So finally I called a meeting with our team and they saw me cry. I was okay with it. I was like, "I had no reason to be like this. You guys were showing me love, you were showing me respect, you're backing me up, helping me with my work. And I was still being utterly terrible."
And it hurt me. It hurt that I was doing that, but I needed them to see me and I needed them to listen to me, give me that second to get it off my chest. And in the end I started crying. A 60-year-old man crying in a meeting going, "I shouldn't have done that to you. That was wrong." And it wasn't contrived. Some of the people there were 20 year old people on my team and they were in tears. And it was because they felt, they told me after this, they felt my pain that I was in, because I wanted to help. It's the most frustrating thing. To your point before, how do I feel? I wanted to help. I wanted to be there and I couldn't. Physically, I wasn't there. My mind was all over the place and I was being rude, being blunt, and I could use some other terms. Please don't. But that's really the main thing for me was it's really simple what we do. I just listen and just show respect for other people. And sometimes we forget.
Hayley Rodd:
I think that so many of the messages that you are talking about are not just for developer teams, they're for every team, every team in every walk of life. I think that they're just so fundamental to successful human relationships, whether it be personal or professional, I think so. I think there's just so many good messages. One thing that I wanted to touch on was that you're talking about active listening and when you think back on your career, and maybe this is totally off script, but when you think back on your career, how have you become a better active listener over the years? How have you improved that skill? As you said, you're an extrovert, you want to get in there, you want to fix the problem. How do you get better at that?
Tony Camacho:
I had some very, very smart people that put up with me, listened to me, and then had the courage to approach me after and teach me and teach me and didn't embarrass me in front of anybody. Did it in a manner that they said, "Do you think maybe this could have been better Tony?" As I said, I'm 61 and still I'm an extrovert and I still have high energy and I still make mistakes. As I tell everybody, every day I wake up, I make a mistake, I just got up. But I could have stayed in bed longer. But also the thing that I've learned, and it's just by the nature of getting older, it's not the age part of it. It was watching people come up trying to do the same thing I did that I failed at and I was an instructor for Microsoft for a long time.
And seeing how, because to me seeing how a person's minds works is amazing. So what happens is I'll just... You know what I tried that, it didn't work for me, but I will say after class with you to show it to me again because maybe you solved it. I'm not that arrogant. And the nature of our business is that I find this, that the more you learn, the more you realize how little you know. That was the biggest thing that opened my eyes. Now it's like, oh my Lord. You meet somebody like John Kern, you meet somebody like Sophia Chaley who come from different perspectives, brilliant people, and you suddenly see that they happen to do things slightly different and you just watch them and you're like, "Wow." And the thing that I love about our job, which I guess you must love, everywhere we go, every team we work with, it's different. It's different.
Everybody always asks me, how do you do that. And I'll tell them, "Look, I will share with you the ways I did it. I have a varied background. I've always been consulting." I've done the ATM space, I did for space enabled warfare, I've done for health industry, everyone's been different. Someone from government regulation, but most of the time different human beings. So I have a saying, I've earned every scar in my back, their minds. I've learned people, you have to give people the chance to have their scars. Yes, it may be pain, I'm not saying fail, I won't let them fail. But sometimes people want to do something. So that's the way I would do it. Let them do it. And I just watched and learned that what happened was as I went in and the more I learned and I suddenly realized how little I know, I was like, I started with FORTRAN, I used to work in the dead 28.
And then you start working your way up and you start realizing, "Wow, I don't know as much as I thought I know." And I had the luck of running into working at Microsoft and having the pleasure of meeting Bill Gates. Now, no matter what you say about Bill Gates, because a lot of people do say some crazy things and some of them may be true or may not. But the one thing you can't take away from him is you go into a room with him and you suddenly see how he puts all these ideas together and comes up with a bigger picture. You suddenly realize, "Wow, people tell me I'm really smart, not that smart." And then you learn, humility is a good thing.
Hayley Rodd:
Yeah, I think humility is just such an important asset to have and to try and grow on because leaving your ego at the door and being open to learn from other people and not think that everything is definitely a life lesson that sometimes you need to go through. And some people go through it and still don't take away the life lesson. So yeah, I think it's so interesting. I guess we don't have too much longer left, but I wanted to touch on thinking about it from an ROI perspective. How important is team alignment from a return on investment? What do you gain from a business perspective when you have an aligned team?
Tony Camacho:
So I'm going to use a term that I dislike and Hayley, you can smack me the next time we meet. But I'm trying to use it as, I don't because it's effective resource utilization, right? But I'm not referring to human beings to that point because it may be human beings. The problem is that's a large market. But as Agile people I won't refer to you as a resource, I refer to you as a fellow human being, you are a partner on my team. You're my teammate. You're not a piece of wood. But that is unfortunately a term that is used. And we will have effective utilization, we'll have common goals across our organization. If you're using any of the message less, bad, safe, pick it, you start focusing on your value streams. You should have improved product quality because we have the same cadence. We're putting things out there and we're having the same views there.
You'll have I think better customer satisfaction and loyalty. They start seeing your product quality going up, being consistent, look and feel and hopefully you are delivering what they want. When you have your teams aligned, you're much more adaptable. Hayley, your team's got capacity? I don't. We don't have capacity to do this. Do you have capacity? Yes I do. Or we find someone or we break it down together and we present an idea to our partners. That's the things I like and I think in the end you have reduced risks at that point.
Also, I think that the thing that they have in is that it's indirect, but nobody knows about. Nobody really talks about it is that if I was upper management C-suite, when we start doing this and we're having the teams aligned, first of all, your teams become safer, your teams feel more comfortable, they're working with the same people. They start becoming very effective and they start producing ideas. They're the knowledge workers. They know this better than anybody else and then they feel empowered to share ideas. The places that I thought that I had the best teams was once they asked... Well, and I got it, I don't know how, I was running a train and they asked to talk to the CTO and all they wanted to do was to talk to the CTO and make that person human. They asked her what she did in a previous job. Amazing. She worked as a factory worker and she also worked in construction. She used to drive, one of the things, nobody would've believed this. And what happened was they started sharing ideas with her and she embraced them. You know what that did to the team, the teams all, they were like, now that's out there, that's ours. Look at that. That was ours. I mean ownership, it's unbelievable.
And unfortunately we are working on a capitalist market, which is fine, that's who we are. I mean we're in IT, it's a return on investment. Return on investment in the end, you start seeing much more efficient use of your money, much more efficient use of your dollars. Also, I would also imagine for the people above who are in the C-suite, they suddenly realize that the organization is going in the same direction. I think psychologically they feel that we now I have this team behind me pushing towards the same goal where a lot of times, every time I do an agile transformation, the first thing we always hear is we know they're working. We don't know what they're working on. And that's where something like Easy Agile bridges that and then you can use that information to go further. And that's wonderful because then at that point, everybody's on the same page. So you're a team now all the way from top to bottom. As opposed to I'm going to my team at work and that's it. So it's just really about return on investment, making sure that we are hitting our customers with everything we got. And I don't mean in a bad way, but we're delivering for our customers with everything we got. It's now efficiency, right? And that's it. That's about it.
Hayley Rodd:
Yeah, that's so powerful. I think it sort of nicely ties everything together because we've talked about a lot of things in the last half hour or so. And I think that at the end of the day, if you can get team alignment, just as you said, there's this ROI that can really shine through and it's a powerful thing for the whole organization to get right and to see the fruits of that work. So one last thing. Can you share your perspective on PI planning? I know you just mentioned safe a little bit for being the initial launchpad for team alignment.
Tony Camacho:
I love it. You have everybody in the room, you get to meet the people, you start making those connections to people. You start seeing them as human beings, not as this email or this text that you're sending across that you're going through there. So could I share one real experience from that? That's a PI planning house.
Hayley Rodd:
Please
Tony Camacho:
Do. So when I was working at Microsoft, I work for product quality online, which I know right now, considering the problems Microsoft is having, you're pretty much going now, "You suck Tony."
Hayley Rodd:
Never.
Tony Camacho:
No, we had our people distributed all over the world. And what was happening was that when I would talk to my short teams, I would ask them, and I was being facetious at a point because I just couldn't get the true answer was I would ask him, can you build the Twin Towers by tomorrow? And the answer would inadvertently be yes. Next day would come. Obviously you can't do the twin towers overnight. Ask them again, will you get it by next week? The answer would be yes. And they were feel for all of that. So when we had the PI planning, we did.
Microsoft went, got a hotel room in Seattle, a hotel room, a hotel in Seattle, rang our offshore teams. And then when they got to see me in person, they suddenly realized that I wasn't telling them I need the twin towers by tomorrow. I really wanted them to tell me when they could get me the twin towers. And I would defend it because they saw me right there in PI planning, defending, saying, "No, this is not possible." And when they saw me doing that, suddenly it was like the sky's open, sun's came through and now I was getting true answers. And what happened was it gave him an opportunity. And I realized that guys, you keep hearing me as sermon. It's always about the human beings, it's about those connections. It's about seeing the people. It's hard. It's two days of a lot of work. But once you get that work done, you come out of there a line, sharp direction. We know what our north is, now, do we know exactly where our true north is? As an agile team, we shouldn't, right? We should be refining it as we get there.
Find out exactly. But we know more or less where the direction is. We more or less know we're all on the same page. We all know that what we have to deliver to make this work out what other people have to deliver for us or we have to deliver for other people. So we suddenly feel part of something bigger. Bigger, right? We are now talking to the, if you're a developer or an engineer, software engineer, you're starting to see the power brokers and why they're doing this. You get the chance to ask them questions. What more could you ask for, right? I finally get to see the people who are making the decisions and I can ask them why. And they can tell me what the business value is and I can make the argument to them that maybe I don't think that's as much business value or we need to fix these things first before we can get that right and move our way on. What more could I ask for? I have an opportunity to make my case and I get to see the other people I'm working with. It becomes, when you're dealing with 125 people and you're on a train, you will become family.
We spend more hours sometimes with these people than we do with our family members at times. And it also gives you a sense of... Besides trust, a sense of a safety. You know it's not just you, it's all of us. So the saying that usually I see that the better executive say, I heard that in one PI planning, you fail, I fail. I fail, you fail. My job is to keep you employed. Your job is to keep me employed and to keep this company together. It's synergy, right? So it's amazing.
Hayley Rodd:
Beautiful.
Tony Camacho:
Yeah, I know. I'm all about the human. Sorry.
Hayley Rodd:
No, I am right there with you. I'm so glad that we got to have this conversation. We've talked a lot over the little while and every time we meet, I'm flabbergasted by your energy and your authenticity. And I think that this conversation that really shown true, so thank you Tony for taking the time to be with us. I'm going to say goodbye to all our listeners. I'm going to say another big thank you to Tony. So Tony is part of aligned agility and that is part of The Adaptivist Group. And yeah, thanks Tony for being here with us and thank you for everyone who has tuned in and listened to this episode of the Easy Agile Podcast. Thank you.