Retro Webinar: Stop Talking, Start Doing

Learn how to take action from your retrospectives.

Easy Agile Podcast Ep.1 Dominic Price, Work Futurist at Atlassian

Listen on
Subscribe to our newsletter
"I had the pleasure of sitting down to chat with Dominic Price from Atlassian. It was so enjoyable to reflect on my time working at Atlassian and to hear Dom's perspective on what makes a great team, how to build an authentic culture and prioritising the things that matter."

- Nick Muldoon, Co-CEO Easy Agile

Transcript:

Nick Muldoon:

What I was keen to touch on and what I was keen to explore, Dom, was really this evolution of thinking at Atlassian. I remember when we first crossed paths, and correct me if I'm wrong, but I recall it was like late 2014, I think.

Dom Price:

Yeah, it was.

Nick Muldoon:

Scrum Australia was on at the time, and you're at the George Street offices above Westpac there, wherever, and we had Slady in the room, there was yourself. I think Mairead might have been there, I'm not too sure.

Dom Price:

No, probably not. I think it was JML's engineering meeting, engineering relationship meeting.

Nick Muldoon:

Right.

Dom Price:

Involved in the

Nick Muldoon:

Hall of Justice, right? Not Hall of Justice.

Dom Price:

Not Hall of Justice. Avengers.

Nick Muldoon:

Avengers. When was the last time you were in Avengers?

Dom Price:

A long, long time ago. A long, long time ago.

Nick Muldoon:

You've been working from home full-time since March, right?

Dom Price:

Yeah. Although, actually for me I can work from anywhere for three and a half years.

Nick Muldoon:

Yeah, fair enough. Okay.

Dom Price:

The shift for me was missing the work element. I'm missing the in-person work element because being on the road a lot, having that one day or two days week in the office, there's connective tissue, I didn't realize how valuable that was. Going five days work from home is not a great mix to me.

Nick Muldoon:

No, not a great mix for me either, Mate. I was the one that was coming into the office during lockdown. I was like, "Oh." It was basically an extension of my house, I guess, because I was the only one that was coming in. But I could turn up the music and I could get some work done without-

Nick Muldoon:

Yeah. All right. Back in late 2014 when we first crossed paths, we're at JML's engineering meeting, and that was before JML had gone to Shopify.

Dom Price:

Yes.

Nick Muldoon:

We were talking about all things. I remember talking about OKRs, which was the Objective Key Result framework that we were using at Twitter that I think Atlassian was looking at for the first time.

Dom Price:

Yeah, we'd been flirting with for a while.

Nick Muldoon:

Flirting with for a while. What was Atlassian using at the time? What was VTFM?

Dom Price:

There was two things we had at the time. VTFM which was Vision, Focus Areas, Themes, and Measures, which was our way of communicating our strategy, our rolling problem strategy. But then off the back of that we had what I would call old school KPIs. Right? We'd pick goals, right, we'd pick ways of measuring those goals, but very KPI-focused and very red, amber, green scoring focused. When we were small, it worked okay. It didn't scale particularly well because it became punitive. If you were green and you hit your score, you got ignored because you were always meant to, and if you were amber or red and you missed by anything, you got punished. Right? It's like, "Please explain." You got the invite to the head master's office.

Dom Price:

We wanted a way of getting stretched into there and also be more outcome-focused, because I think when we scaled KPIs, we got very output-focused like, "What did you do this week? What's the thing that you shipped?" Actually, the thing that we forgot about, and I think it was by accident, it wasn't bad intent, but we forgot about what's the outcome or impact we're trying to have on the customer, because that happens after the event. OKRs were a way of putting stretch in there and building the idea of moonshots and big ambition. But then also, refocusing us on, what is the impact we're trying to have on the end customer, not just what's happening in the sausage factory?

Nick Muldoon:

With that end customer perspective though, did you get that with the VTFM?

Dom Price:

No. Actually, the first year we rolled that OKR, that was part of the problem. We had the VTFM because that stayed, right? That was like the sacred cow for the first year. That stayed, and we just had OKRs underneath. Yeah, and we're like, "Well-

Nick Muldoon:

So you're mixing them together.

Dom Price:

... which ones do we report? The measures in the VTFM because that's our Atlassian level plan, or the OKRs, which is the things we're actually doing and the impact that we're having. You're like, "Well, both," and you're like, "Well, they don't meet. There's no cascade up or down, left or right, that had them aligned properly." The year after we actually phrased ... we got rid of the VTFM, and we now have our rolling 12-month strategy phrased as OKRs.

Nick Muldoon:

Right. Okay. At that time, Dom, back in 2014, when you were flirting with OKRs, as you said, was the VTFM that you were working to replace, was that company, department, team, individual, or did it just stop at the team?

Dom Price:

Yeah. That's where it didn't really scale, right? The organizational one made sense, and again, when you're smaller, it's a lot easier to draw the linkage between your team or your department and the company one. As we scaled, what happened was we'd have a company level VTFM, and then each department would go and build its own. The weird thing is, and again, this works for a phase, and then you realize it doesn't, is we don't create value up and down the org. We create value across the organization, and so building these VTFMs in departments was honing our craft. But it was doing it at the detriment of how you work across teams.

Dom Price:

I think that it's one of those things that at the time, we didn't realize. If I had a crystal ball, it would have been great. But it seemed like the right thing to do. Engineering had a VTFM. So did Design, so did Product Management, and you're like, "You know we only ship one experience, right?" I don't care if engineering's perfect and design's not because that's letting the customer down because this one experience that we shipped. There was this whole sort of arbitration where we'd build them vertically, and then try and glue them together horizontally, but they'd all been built in isolation.

Dom Price:

Then When it comes to trade offs, and every business has trade offs, whether you admit it or not, when you're like the best laid plans literally stay on paper, right? That's where they exist, then reality kicks in one day after you've built the plan. When reality kicks in, what trade off are you going to make? Are you going to do the trade off that delights the customer, maybe compromises you? Right? then how do you do that internally? Are you going to help Design and Product Management and load balance that way, or say, "Well, yeah, I'm an engineer and we're fine. It's Design's fault. How we'd adapt everyone is Design's fault." We quickly realized that a vertical model brought about some unintended consequences and some odd behaviors that weren't really the kind of behaviors we wanted as Atlassian.

Nick Muldoon:

Back in that time, Dom, in 2014, 2015, did you have the triad then with the product design and later for each of those groups?

Dom Price:

In physical people, yes.

Nick Muldoon:

But in-

Dom Price:

... modeling, no.

Nick Muldoon:

No. Okay. How did that come to fruition, that triad where they were working as one in harmony to deliver that customer experience?

Dom Price:

I think essentially, it's one of those brilliant mistakes when you look back. We're really good at reflecting, and you do a few reflections, and you suddenly see the pattern, and you like, "Hey, our teams that are nailing it are the ones where we've got cognitive diversity and the balance of skillsets." Not where we got one expert or one amazing anything, but actually, you're like, "Yeah, actually -

Nick Muldoon:

If look at some of these patterns-

Dom Price:

Yeah. You're like, "Hey, I just saw that design." They get the product manager in a headlock and have a valid argument at a whiteboard. You're like, "I actually like that. That's what I like, the meeting where there's consensus and violent agreement." Maybe that's the wrong signal, right, that the right signal is this cognitive diversity, this respectful dissent. You see that, and we're like, "Hang on, we have the realization that engineers build great usable products, and product managers are thinking about the whole sort of usability and along with the designers. Viability, you're like, "Oh, we need all three. All three of those need to be apparent for a great experience." You're like, "Cool. Let's double down on that." Right?

Dom Price:

We started to hone in a lot more on how do we get the balance across those? How do we understand the different roles? Because we didn't want to become homogenous. You don't want those three roles to get on so well they all agree. You also don't want to violently disagree all the time, right? A little bit of disagreeing commits great. If they're always in disagreement, then that comes out in the product. How do you find the things that they stand for, and how they bring their true and best selves to each phase? Right? If you think about any given product or project, there are natural phases where their skillsets are more honed, right? In the phases for us, part of managing design is often a lot better with the ambiguous and a whole lot of stuff. When it comes to building, I'm probably going to listen to the engineer more, right?

Nick Muldoon:

And you're handing it over to delivery.

Dom Price:

Yeah. But then also, it's like, well, it's not the ... If you think about delivery time, I think we'd sometimes think of it as the relay race. I think that's incorrect, because everyone's still going to see the relay race. Once I've run my lap, I'm done, right? But in product development, it's not because when I hand over the baton, I still have a role. Even if it's in build phase, the product manager and the designer still have a massive role. It's just that they're co-pilots and the engineer's the pilot, right? You don't disappear, your role changes. I think that was one of the nuances that we got as we started to bring in the right skills, the right level of leadership, the right level of reflection to go, "How do we balance this across those phases, and how do we be explicit on what role we're playing in those different phases?

Nick Muldoon:

Okay, that's interesting. I'm going to want to come back to that when we turn our attention to the customers in the Agile transformation landscape more broadly. But one thing that has got me thinking about with respect to this balance is the fact that Atlassian had the discipline to hire for a triad, right? If I think about, I think this was around 2013 at Twitter, and in one of our groups, we had pick a number, but there would have been 200 people, and there would have been less than 10 product managers. I think we actually had a ratio of like 20. It was something silly like 26 engineers to a product manager. It wasn't even a design counterpart necessarily for each of the product managers. The balance was way off, and it wasn't very effective. Was there a time at Atlassian where there was this reflection? Because I'm just trying to think, in my time at Atlassian, I don't think we had maybe a great balance. I think there was a much heavier in engineering than there was in design and product.

Dom Price:

Yeah, it's one of those things that if it's not there, you don't miss it. Right? It's weird, right? It was a lot of it before my time, but when I listened to the story, it's like even design as a discipline when I started in 2013 was a very small discipline. I think even then, it was kind of like a hack to the notion where it was like, "Oh, yeah, we got some designers. They do the pixels, right? They make stuff look pretty." .

Nick Muldoon:

They do T-shirts and they do like .

Dom Price:

Who knows, right? But it makes us look pretty, right? They drink craft beer, and they sit on milk crates. We had this archetype of a designer, and then you like, "Oh, actually, once you start to understand user experience, the integration points, design languages, design standards, and the experience, once you get your first few designers who say, "Here's how our products fit together," and this is the experience from a customer lens, you're like, "Oh, I'm not sure I'm a fan of that." It wasn't badly designed, but nor was it particularly well-designed. Once you start to make some improvements, then you start to measure customer satisfaction, and you make that experience more seamless, you suddenly see the value.

Dom Price:

I think for Atlassian, I think we started as an engineering company. We added product management, and then begrudgingly added design. Interestingly, in my time there, the most recent thing we've added is research.

Nick Muldoon:

Yeah. Okay.

Dom Price:

Fascinating evolution for us again to go, "What do you mean, research? I'm a product manager. I know everything about the industry in the section of the competition." They're like, "But do you know anything about the customer, and the job to be done at the top tasks, or how they experience, and thinking about things like accessibility, thinking about how our products integrate with other products, thinking about not just from a competitive landscape, but what's the actual job to be done, and what are the ways people are trying to do that, and the drop off points.

Dom Price:

Research has become a new muscle that we had the exact same experience with. First time you roll it out, people are like, "Oh, we don't need that. It's overkill." You're like, "I see, it's really quite good." Hard to integrate because you're giving me findings I wasn't expecting, and then there was a shift both for designers, but also for the product managers to go, "Oh, I can use a resource now because you're this independent group that can help me understand, not just my product and iterating on my products, but a level up, what's the thing that my products trying to do? Who am I competing with, and what does that experience look like end to end?" It's a completely different lens.

Nick Muldoon:

Basically what you're describing there, Dom, is you've still got the triad of the product design and leads. But now you've got this. It's a centralized kind of research team?

Dom Price:

Yeah.

Nick Muldoon:

Do they drop in for particular projects in different areas?

Dom Price:

Yeah. If you think about it, if you strip it back to plain common sense, I think over time, we got really good at explore and build. But maybe we lost a little bit of the muscle around wonder. These researches are great. The blinkers are out and they wonder, right? I'm sure they physically do this as well, but mentally, they stroll, right? They go quite broad, and when they come back with their insights, you're like, "Wow, that's given me a really good broad perspective." I'll give you a quick example where we're working a lot, and we always are on accessibility. It's easy to look at your current products and start adding stuffing. Right? That's the logical way of doing it. Or you look at your competitor's products, and how do you become a pair or a peer? Easy.

Dom Price:

What our research team did was they actually got a whole lot of people with different sight and mobility issues, and said, "We're going to now get you to use our products and go through some key tasks." They're already using it, but it's like maybe they're on a screen reader, or maybe they can't use a mouse, they can only use keyboard shortcuts. You suddenly see the experience through their lens, and we record it, and it's tracking eye sight and line of sight using all the actions. You've got this level of detail there where you're like, "Well, I know we're trying to build empathy, but actually seeing that experience firsthand is completely different than trying to think about it."

Dom Price:

You just seeing it through the lens of this person. The research team did weeks and weeks and weeks of research with different users, different backgrounds, different disabilities, different products and different tasks to give all of our teams the sense of what is it like as the actual person. Here, you can actually walk in that person's shoes, or it feels like you are.

Nick Muldoon:

If you're a product manager and a designer, and you're ... Because it sounds to me, Dom, like that sort of investigation or exploration that you're describing there with respect to mobility-impaired or sight-impaired people, that's something that it might be hard for me to bring that into my OKRs for our product. For that triad, how do I have ... I'm trying to push forward and chase down monthly active users, or cross-flow, or whatever it happens to be, and that's much more long-running. It's like it's a long-running thread that's just going to stay open for 18 months while we think about this stuff and have these conversations. Does that research group, do they actually have their own OKRs, and are those OKRs annually?

Dom Price:

Yeah. Yes and no. We do mostly OKRs across design, research. We now have a ways of working team. They tend to be shared OKRs or more cross-functional, are cross-functional to shared. The cross-function as in we have the same objective, but different key results.

Nick Muldoon:

Yeah, okay.

Dom Price:

If you think about accessibility as an objective, the research team, their key result is about having the latest greatest research and insight so that we can learn and understand. You're like, "Cool, that's your task." Right? The design team, your OKR is to take that insight and turn it into some designs, usability, and then you can actually go along the value chain, and each different person in that value chain has a different OKR.

Nick Muldoon:

Okay. Still today though, there's no OKRs at an individual level, right? It's all team, group-based?

Dom Price:

We have odds and sods. I've dabbled with it a little bit. Sometimes I think I've always got individual OKRs. The question is whether I share them or not. I think if you think about the majority of knowledge workers, they will have individual goals, "I want to learn a new skill, I want to acquire a new "

Nick Muldoon:

Honing the craft.

Dom Price:

Yeah, right? Whether you write that down and it benefits you or not is not up for debate. When it came to writing them down in a collective, having a single storage of them, any kind of laddering, I think the cost of that is higher than the benefit. Right?

Nick Muldoon:

Okay.

Dom Price:

We strayed away from saying everyone then must have individual OKRs, and then ladder, whatever, because it ends up getting very, very cumbersome, and actually very command and control. What we've done instead is really say to our leaders, and this is leadership by capability, not by title, but saying to our leaders, "This is part of a conversation you should be having on a regular basis with your people around growth, and how you're inspiring them, and how you're motivating them. How are they developing and evolving? What are the experiments they're running on themselves? Right? How are they with other people? What are their challenges, and how can you help them never get those challenges? What are their points of amplification that you should be calling out with them to turn the dial on that? Right? What are their superpowers that we should be really encompassing, right, and nailing?" That's part of a leadership conversation. Does that need to be written down and centralized? No. To me, it becomes a zero benefit to documenting that.

Nick Muldoon:

It's interesting hearing you describe that. That's very much learning and development-focus. If I think back to Andy Grove's High Output Management, my understanding of that at an individual ... of OKRs and an individual level was always with respect to your customers. What am I going to do for my customers? But you've actually framed it, what am I going to do for myself that's going to allow me to be in better service to my customers, maybe next financial year?

Dom Price:

Yeah. It's a secret. I'm guessing this is shared by Atlassian, but this is definitely my view of the world, and I've shared this with enough people now where they understand. You can't be a great teammate if you're not turning up your true best self. You got to take a step back. There's this whole weird narrative around the humility of being a teammate where you're like, "I'm a martyr, and I'll take one for the team." It's BS, because if you're not in the right zone for that team activity, you're not giving your best, right? You're actually the anchor that brings the team down. You step back from that and you say, "Well, how do you be the best?" Because not all work is teamwork. There's a lot of deep work and individual tasks and stuff that needs to be done. You're like, "Right, I need to be the best version of me. Well, what's that mean?"

Dom Price:

It means that before any meeting, I need to have done my tasks, or before any meeting, I need to have done my pre-meeting, right? If we're meeting as a team and we have this synchronous activity, what are the things I need to do to be best prepared for that synchronous activity to deliver the most value? How can I get the most out of that teamwork? How do I turn up and be present? How do I turn up with respectful dissent and challenge, right, and provocation? That requires me first to be an individual. Right? I think one of the dangers in a lot of work environments right now is people have lost the understanding of what it is to be an individual, what your key leadership style, your learning style, how do you turn up? Right? How do you critique? How do you take feedback? All these things that make you you, you need to know those and be aware of them before you can be great in a team environment.

Dom Price:

It's not just the tasks. You need to know you. If you're a great individual, and you've honed that, you can then be a great teammate, and if you're a great teammate, you can deliver great outcomes for your customers. Anything else is an accident, right? We've all been in accidental teams, which has delighting a customer, and we've sat there and gone, "Really not sure what I did to that guy. I'll take it. I'll take the pat on the back. I'll take the kudos, and the bottle of wine, and the congratulations. Not really sure I amplify that. I don't know. If you don't know, you probably didn't. Right? That's not humility. You're probably just a passenger. I think the danger in growth environments is there's lots of passengers who they're a passenger to lots of success, and after a while, they're like, "I'm amazing." You're like, "You're not. You've just been in the right place at the right time repeatedly."

Nick Muldoon:

I got to process that.

Dom Price:

Let me give you an example. Right? A couple years ago, I was in New York with a mate of mine, Sophie. She's unofficially mentored me and helped me a lot of the years, right? I'm talking to her about trying to scale me, and I was really angry about some stuff, and thankfully, it was late afternoon in New York. She bought me [inaudible 00:25:30]. We smashed a drink and we chatted away, and she's one of those people that just calls BS on you, right? I'm like, whinge, whinge, whinge, whinge, whinge. She's like, "Oh, cool." She's English as well. She's like, "So I'm guessing you're just going to whinge about it and hope it goes away." I'm like, "All right, fair point. Little bit, my English came out. I actually hoped that maybe even if I did whinge long enough, it would actually disappear." She's like, "That never happens, does it? What are you going to do about it?"

Dom Price:

We chatted when she gave me this challenge, and she's like, "You're not evolving." She's like, "You're adding stuff in, but you're full." She's like, "Cognitively, Dom, you're full." My challenge was I was reading all these business books at the time, and I knew lots of stuff, but I didn't feel any smarter. I wasn't doing anything with it, and it's creating this frustration spiral. She gave me the exercise, and you've probably seen this, the four Ls. She got a bit of paper, and she's like, "All right, write the four Ls down. Reflect on you as a leader. This is selfishly purely about you as a leader. Last 90 days, what have you loved? What have you done personally?"

Dom Price:

I'm like, "Oh, no, no, no, no." She's like, "Not like, because we're not doing likes here, right? We're not being soft. Loved, and own it. Actually, superpower, do more of it." We did that, very uncomfortable few sips of wine. Then she's like, "What's your loathe and what's your longed for?" I had lots of long fors, long list of those, but no loathed. She's like, 'All right, here's the problem. The long for, you're sprinkling in in the 25th hour of every day. No wonder you're not doing well at it, because you never giving it the ... You're not giving yourself any space, or time, or freedom to actually experiment. You're not growing. You're not getting better. You're just adding stuff in." I'm like, "Fair point."

Dom Price:

We went through, found some loathe. She's like, "Right, you're going to remove those. Who are you going to tell those habits, or rituals, or whatever, who are you going to tell that you're removing those because they need to hold you accountable? Because they'll slip back in really easily." I found someone, pinged them. She's like, "Right, the longed." She's like, "I need to let you know that when you add them in, you're going to be crap at them." I was like, "I don't want to be rubbish at anything. I'm a leader. I need to be a superhero. I need a cape, and I need to fly in, and everything must be perfect first time." She's like, "No, the first time you added a longed for, the chances are you'll be rubbish at it. Find someone who has that muscle and let them help you practice it, and you'll get better at it over time."

Dom Price:

Then the fourth L was what have you learned? What experiment did you learn yourself last quarter? What did you learn about yourself?" She's like, "Right, go and tell as many people as you can. That'll build a place where you're learning and networking environment for you." I did it, and then I did it again 90 days later. There's a few times when the power of rationalization kicks in, and I just BSed myself because really easy to do. Then other times where I've got really deep and analyzed on it, and it's enabled me every 90 days to evolve, right? Now, the moral of the story, and this is where we tie individual to team, the number of leaders I know in big businesses driving transformations, but they're not changing themselves. What behavior are they rolling with? They're rolling with the behavior of, "I'm fine. You're not. You all need to change," which is-

Nick Muldoon:

Yeah, role modeling status quo.

Dom Price:

Yeah.

Nick Muldoon:

Yeah. That's interesting. I've certainly heard of the love versus loathed exercise. I like that you, or that Sophie extended it to longed for and learned. I think that's really beautiful, and I'll take that. With the loathe in particular, were there things on that list that you had to delegate or you had to hire someone to do? Because there's things that I think about that I loathe with respect to the business, and typically, they're things about orchestrating, paying suppliers, or whatever it happens to be. How do I address that? I bring the bookkeeper into the business that-

Dom Price:

Yeah. The little game that we played is you're not allowed to outsource it until you drop it. Right? The idea is, you're going to find a way of dropping it first, because maybe it doesn't need to exist, right?

Nick Muldoon:

Okay.

Dom Price:

Because you've worked at big companies, and you walk around a big company, and you're like, "That person there, they only exist to do a task that someone probably could have automated or got rid of," but they didn't have the time. Also, they put a warm body in the way. Then you add another warm body, another warm body, and you suddenly realize you've got thousands of warm bodies keeping this deck of cards stacked together, and if one card falls, the entire thing comes tumbling down. I removed stuff that I was really uncomfortable removing stuff. I was like, "This is so important." It wasn't. My blinkers were just off, right? Then she's like, "We'll stop doing." She's like, "It's not life or death." She's like, "No, thanks, Dom. Well, you're not a surgeon, so stop doing something, and listen, and see what happens when you stop doing it." I'm like, "Oh, no, but these are really important. People will be angry. I'm a very important person." You remove something and no one bloody notices. You're like, "Why have I been doing this?"

Nick Muldoon:

Why was I doing it? Yeah.

Dom Price:

Yeah. Then I-

Nick Muldoon:

Can you-

Dom Price:

One of the big examples for me was meetings. This wasn't a delegate or [inaudible 00:30:24]. This was me just being a control freak, and turning up in meetings where I wanted to be there just in case. We looked at my condo, just a sea, I use Gmail, right, the sea of blue of all these meetings, double booked, triple booked. She's like, "Right." She's like, "Imagine you've got to set yourself a goal of getting rid of 15 hours." I'm like, "What? It'd be easy to create a time machine that adds 15 hours a week. I can't remove 15 hours of meetings. I'm a very, very important person." Then we played this game called Boomerang or Stick. I declined every single meeting, and I sent a note saying, "This is either a boomerang," in which case it comes back, or if it's a stick. When you throw a stick, it doesn't come back. The boomerangs, I want to know what the purpose of the meeting is, what my role is in the meeting, and what you're going to hold me accountable for.

Dom Price:

Two thirds of the meetings didn't come back. Right? The ones that did, I honestly admit to you, I was playing the exact wrong role in virtually all of them. It was funny because I get these emails back and they're like, so one of this meeting I was in, they were like, "Your role is the decision maker." In the next meeting I was like, "I need to apologize. I thought I was the protagonist." Every time they were suggesting something, I'm like, "Well, you could do that, or these three things." I was sending them into a complete spiral, and they were like, "You're a terrible decision maker." I'm like, "No, I'm a good decision maker when I know that's my job because this isn't your title. Your title stays-

Nick Muldoon:

Ah, Dom.

Dom Price:

... the same, right? Your title stays the same, but your role's different in every environment, every engagement, your role is different. We don't call it out, we just assume. Once we clarified those assumptions and realized I've got them all wrong, the meetings I was in, I was way more effective in. Two thirds of them didn't come back. Either the meeting [inaudible 00:32:09], or it didn't need me in that. If you think about it, and me and you know this, our most precious resources are time.

Nick Muldoon:

Time. Yeah.

Dom Price:

Why are we giving it away for free or for negative cost? Right? I'm like, "No, I'm growing all that stuff back."

Nick Muldoon:

Liz and I have been having this conversation for a while now about statistically speaking, I've probably got 50 years left on earth, based on how long a Caucasian Australian male lives. But I've probably only got 40 good, usable years left, because then you kind of like atrophy and all that.

Dom Price:

Yeah.

Nick Muldoon:

Yeah. Liz and I have been going, "Well, if we've only got 40 summers left, what are we going to do with 40 summers?" It's a really good exercise to bring you think real quick, what do you want to be spending your time on?

Dom Price:

Yeah. Absolutely. It's the same thing. You can do that at a meta, macro level for life, and I think you can do it on a annual quarterly basis. With work, there's so many things that we just presume we need to do, and both the four Ls and just my attitude has enabled me to challenge those and go, "Well, I just say why an awful lot right now." So it's like, "I'd like you to come to this meeting." I'm like, "Oh, cool. Why?" They're like, "I don't know. I'd like you there." I'm like, "But why? Because if you can't explain to me what you want me to do, then you probably don't need me there."

Nick Muldoon:

Five whys, right? Five whys.

Dom Price:

But also the reason I'm often asking them why is I'm like, "You do know I'm a pain in the ass when I do come to the meeting, so just I want to double check to you, you really want me there. Because if you converged on an idea and you want to ship it, don't invite me. All right, I'm the wrong person." Just challenging on that and getting that time back, and then using it for things that are way more valuable. I rebalanced my portfolio just like a financial advisor or a market trader rebalances a financial portfolio every quarter, I did the same thing with me. If I don't, then what I'm saying is when I don't do that, I'm saying the version of me last quarter is more than good enough for them for next quarter. What I'm saying is-

Nick Muldoon:

Yeah, which is never the case, is it?

Dom Price:

Yeah, I'm saying the world's not changed. The world stayed flat, right, and everything's going on a flat line. That's not the case. If I'm not evolving myself at the same pace as Atlassian or our customers, then I've become the anchor by default. I'm the anchor that slows us down.

Nick Muldoon:

Tell me, what portion of your time today are you spending with customers? Because I know over the years in our conversations, I think about a lunch we had at Pendolino, you, Dave, and I, probably two and a half, three years ago now, but we were talking a lot about Agile transformations at the large end of the spectrum. How much time are you spending with customers today, and what are those conversations like?

Dom Price:

Yeah. I'm probably over the 50, 60% mark right now, but mainly a rebalance again. When COVID hit, the conference scene disappeared, and so I'm like, "Cool, I get to reinvest that time. I could reinvest it internally at Atlassian, and I did do it where we're evolving our ways of working internally and driving some change there. I got involved in that, made sense. But I was like, "Hey, our customers are struggling." First of all, we need to understand how and why they're struggling, and then if we can help them, find a way of helping them. It's funny how the conversation really changed from quite tactical, yeah, 18-month plans and presumed levels of certainty, to going, "Hey, the world's changed. The table flip moments just happened. Our business model has been challenged, our employees are challenged. We're having these conversations about people, wellness, and actually, we've said for years we care about our people, but now we actually have to. What does that mean? All the leaders just trying to understand the shift from peacetime to wartime-

Nick Muldoon:

To wartime.

Dom Price:

... to time peacetime. I think that it's funny that the transition from peace to wartime, I think the shared burning platform, the shared sense of urgency, I think a lot of these transition, they're okay. I wouldn't say they're amazing, but they weren't awful given that mostly the Sydney in Australia haven't manage through wartime. Right? We've had an amazing economic success for a long time. The harder bit, the way more complex bit is going from war to new peace, because new doesn't look the same as old peace. Right? It's a very different mindset to go-

Nick Muldoon:

Who is-

Dom Price:

... about managing in wartime is I don't need approvals because it's a burning platform. We just drive change, just do it, just do it. New peace is different because we're like, "Well, how long's this going to last for? What are the principles I want to apply? How do I build almost from a blank piece of paper?" Very different mindset.

Nick Muldoon:

Was that Ben Horowitz with the hard thing about hard things where he talked about war versus peacetime leaders?

Dom Price:

I've read it in a few things. The most recent one I read-

Nick Muldoon:

Hear different places.

Dom Price:

... in was General Stanley McChrystal. He wrote Team of Teams.

Nick Muldoon:

Okay.

Dom Price:

He did one on demystifying leaders and how we've often put the wrong leaders on a pedestal, and there's some great leaders out there that just didn't get the credit because they were way more balanced. But yeah, there's a few different narratives out there on it.

Nick Muldoon:

With the latest that you're meeting with, I guess, well, one, are they using something like the four Ls that Sophie shared with you?

Dom Price:

Yeah, that's become a lot more popular, I mean, certainly with C-suite and the level down, even board members, actually. When I share that, there's this kind of moment of reflection of going, "Yeah." It's because I get them with the irony of going, "Question one, are you driving a transformation?" They're like, "Yes." You're like, "Cool. Are you transforming yourself?" "No." By the way, reading a Harvard Business Review article on Agile doesn't mean you're evolving yourself. That means you're educating yourself. That's subtly different. We've all read the article. It doesn't make you an expert, so sit yourself down. That is the first moment of getting them bought in.

Dom Price:

Then the second one is just saying to them, "Just be honest right now, what are the things you're struggling with?" For a lot of leaders, it's this desire that they get the need for empathy, vulnerability and authenticity, they get it because they've read it. They understand it, they comprehend it, they find it really hard to do. Right? A lot of them are leaving as a superhero leading through power and control. They've led through success, but they're not led through a downturn and a challenging time, and they're just questioning their own abilities. There's a lot of, I don't even want to call it imposter syndrome, I think there's a lot of people just saying, "I think my role as a leader's just changed, and I don't know that I understand the new version." That's quite demoralizing for a lot of people. It's quite challenging.

Dom Price:

The irony being is that the minute they look to that and talk about it, they've done the empathy, vulnerability, and authenticity. They've done the thing they're grasping for. But instead, they're trying to put this brave face on it. In a lot of organizations, I've seen a lot of ruinous empathy. A lot of people buffering from their team, like, "Nick, I don't want to tell you that bad things are happening in the company, because I don't want you ... I think you're already worried, because I won't tell you that," without realizing that you fill in the gaps, and you think way worse things than I could ever tell you. The information flow's changed, and then for a lot of leaders, the mistake I've seen on mass is they have confused communication and broadcast. Right? Communication is what I hear and how I feel when you speak. Broadcast is the thing that you said. Because of this virtual world, there's lots of loom, and zoom, and videos, and yeah, we're going to broadcast out.

Nick Muldoon:

Broadcast a lot. Yeah.

Dom Price:

But we're getting to listen for the response.

Nick Muldoon:

This has to be a very challenging time for a number of leaders today, but 2018 or 2008, there were a lot of leaders back then that probably, I presume, picked up a lot of scar tissue around GFC. How many of the leaders that you're chatting with today would have picked up scar tissue through the GFC, and they're still finding this kind of a feeling, at least, like it's uncharted territory?

Dom Price:

Well, and that's, I think, the byproduct. I was going to say problem. The byproduct of the Australian system is we've dodged the bullet in 2008. Economically, we did not get the same hit that the rest. The stock markets got a little hit, and a whole lot of other things took a little bit of a dip, but nowhere near that the size or magnitude of the rest of the world. Both through the mining boom, yeah, the banking sector, a whole of other tertiary markets around tourism doing well at that time, you're like it was a blip, but it wasn't a scar. I think that's where there's a lot of countries have got that recent experience to draw upon, like, "Here's how we do this. Right? Here's how we bunker down. Here's how we get more conservative. Here's the playbook for it." I think a lot of countries haven't got that playbook, so they're getting at it, right? They're doing it on the fly. I think there's that.

Dom Price:

But also I think this one's just different. The global financial crisis was a financial and market-caused issue, right? This is a health pandemic-caused market downturn. I don't think we've got a playbook for that, because we don't know the longevity of it. -

Nick Muldoon:

If you-

Dom Price:

Go on.

Nick Muldoon:

Yeah. No, sorry, Dom, I was just going to ask, if you cast your mind back to GFC, were you anxious going through GFC? Have you been anxious this year?

Dom Price:

No. I wasn't anxious at all through GFC because it felt like ... I did a recession in the UK a long, long time ago, and so I've been through that downturn. I've worked in companies that had downturns, even if the general economy was fine, and industries that had shrunk, where at the end of each quarter you're like, "Right, we talk about the books. Who are we letting go? What projects are stopping?" It was always the taking away, not the adding. I've been through that. The thing that made me anxious about 2020 was, this is the first time I think we've had this level of uncertainty. It's funny because a lot of people talk about change fatigue. I actually think humans are quite good at change. I think we actually do that quite well. But uncertainty, we are terrible with.

Dom Price:

It's weird how when we get uncertainty, how different people respond in different ways. Some like to create a blanket of certainty and wrap it around them like, "Now, here's what I know, and this will come true." You're like, "Maybe [inaudible 00:42:16]." I like your blanket, it's comfortable. But it's not necessarily real, right? It's not going to shelter you from the things that we genuinely don't know about. This is where agility has become key, or nimbleness has become key because if I look at the leaders in the companies that are listening, they're actually attentive to their customers and listening, they're the ones that are evolving really quickly, because they've got ... not only have they got the nimbleness as the muscle, but they're listening to cause correct. The ones that have ... think they've rolled out agility in the last few years, but never added the customer bit, they've got small, fast, nimble teams just running around in circles.

Nick Muldoon:

They're not heading in a particular direction. Yeah.

Dom Price:

Yeah. They are clueless, right, because without that overarching like, "Why are we doing this? And that customer that we care for, we still care for, how's that customer's world changed? Right? Because if that customer has changed, how can we change with them?" A lot of companies haven't done that yet, and I think it's some are holding the breath and hoping for the best. Some are just too fixated on, "But we have a plan, and if we stick to that plan," I read a book somewhere that said, "If you stick to a plan, you'll be fine." You're like, yeah, the world just shifted around you. Your plan might not be as relevant.

Nick Muldoon:

It's making me think, Dom, about the Salesforce transformation, Agile transformation in 2006. That was one of the big bang, I think it was one of the early big bang Agile transformations that took place. I don't know if it was Parker Harris or how it actually played out, but the leaders of Salesforce basically said, "You're going to change to Agile. You're going to give this thing a go. Otherwise, all is lost." There's been other examples. I think shortly after, LinkedIn did their IPO. They pulled the end on call, they stopped everything to rework how they work. Is 2020 one of those years? Are the best companies going to take advantage of this as an opportunity to retool how they work? Then the other companies are just going to kind of atrophy and slowly decline over the next five?

Dom Price:

I think the best ones probably built some of the muscle already, the ones that are now reacting, right? I think if you are aware of the market, all COVID's done is put an accelerant on the stuff that was changing anyway. Right? Yes, it's not ideal, but it's stuff that was happening regardless, right? I think we really had five or 10 years to equip ourselves, and we got given three months instead. I think a whole lot of companies that saw those patterns emerging, changing people habits, technology, practices, ways of working, customer demand, experience demands, you put all those together, that's why Agile transformation has been a massive hit for the last three, four, five years, right? The ones that were prepared for that are awesome. The ones that responded quickly, that are like, "Brilliant, don't let a crisis go to waste. What can we do?" They'll do well. The ones that have dug their heels in and are being stubborn ,saying the world will return to normal and it's just a matter of time, they're the ones that I fear for, because that atrophy that may have been a slow decline, I think that becomes a cliff. Right? Because in a consumer-

Nick Muldoon:

Slow decline, and then they just fall off the edge at some point.

Dom Price:

consumer world, consumers spending goes down, sentiment goes down, and relevance suddenly becomes really important. Is your product relevant to your customers? The people that understand that, and then have agility in how they deliver it, that's a winning combination. I think the interesting, I was talking to a friend about this on the weekend because they were like, "What's the difference between the successful ones and the not successful ones?" It's hard to pinpoint a single reason. But the one that stands out for me is the Agile transformations that have been people-centric are the best. A whole load of them were tool-centric or process-centric. I will send all my people on a training course. I'm going to make you agile, I'm going to give you some agile tools. Go. You're like, "Did you change their mindset? Did you change their heart? Did you change the things that they're recognized for, their intrinsic motivations? Did you change those things?" Because if you didn't, their inner workings are still the same, right? You've just giving them some new terminology.

Nick Muldoon:

I think that's a really, really, really good point. I go back to if I cast my mind back to the first Agile conference that I went to over a decade ago, the conversation back then was very much around training the practices, teaching the practices to your people, and then it evolved into a tooling conversation. But again, teaching the practices and software are just tools, and it was probably 2013, 2014, I guess, when the modern Agile movement came out, and they were talking a lot about psychological safety. Go back to where we started the conversation, right?

Dom Price:

Yeah.

Nick Muldoon:

Psychological safety, bring your whole self to work, and that will free you and enable you to do something tremendous for your customers. Give me a sense of the customer conversations that you've had throughout 2020. What percentage do you think have psychological safety, truly have that psychological safety?

Dom Price:

Yeah. I have to remind myself that psychological safety isn't an all or one, right? It's a sliding scale. I would say it's improved, where it's done with authenticity. The danger is, it becomes a topic where people are like, "I was working from home. There's an increased chance of stress, it's a whole of a change. Things are going wrong. Oh, I know what, let's just talk about psychological safety a lot." You're like-

Nick Muldoon:

That's not it.

Dom Price:

... "There's no correlation between talking about and doing." Right? It becomes the topic, right, the fashion, right? Just like wellness and mindfulness have become fashionable to talk about, doesn't mean we've got any better at it. And so that-

Nick Muldoon:

But isn't that the thing, Dom? Agile was the fashionable thing to talk about, and so we talked about it, but nothing really changed in a lot of these organizations.

Dom Price:

Yeah. It's not dissimilar with psychological safety. What has happened though is over time, the leaders that are truly authentic, vulnerable, build that environment where you can bring your best self, and they appreciate the respectful dissent, but they will still, at the right time, disagree and commit. They're like, "Nick, I heard your view. Thank you for sharing. Our only decision at this point, we're going down Path A. I know that you're in Path B. We're going down Path A. When we leave this room, we commit to A." I hear you. You want me when we're coming to A, and here's the signals we'll assess to make sure it's the right path. If it's not, we'll course-correct. Those people are thriving in this environment, and more people want to work with them. What this environment has done is it's shone a massive light on the difference between managers and leaders. Managers manage process and they like control. Right? Leaders are about influence and people.

Nick Muldoon:

Do you think, so the fact that people are working remote and working from home, that's made it easier to see who the leaders are.

Dom Price:

Yeah, it's shone a light on-

Nick Muldoon:

Because the managers are just trying to count time.

Dom Price:

Yeah, count time, but they're also thrashing around busy work, because they're like, "I'm the manager. I need to show that I'm doing something. I would manage tasks in and around the office, and what I meant some people to do. If we're autonomous, and they just do it, then what's my role?" You suddenly start seeing business. This noise comes out of them, which isn't, "Here's an outcome I achieved, or here's how the team's doing on team cohesion or bonding." They're not talking about about big meta level things. They're sharing these transactions with you, and you're like, "I assumed you're always doing the transactions. Now, you're showing me them all. It's a bit weird." Right? It's just a behavior, right? We must have a process for that. Well, what's the process? You're like, "Actually, what about the process of common sense?" Right?

Dom Price:

If you think about pre-COVID, most organizations that would allow people to work from home once or twice a week had a giant process and policy about how you apply to work from home that one day a week and everything, and then suddenly they're like, "Well, actually, we can do that. Everyone's going to go work from home." But now things have settled down a bit, the process police and the policy police are coming back again going, "But what about, what about? We pay Nick to do 40 hours a week, and what if he didn't do 40 hours?"

Nick Muldoon:

40 hours a week.

Dom Price:

Who cares? Nick delivered his outcomes and his customers are over the moon. As long as he's not doing 80 hours and he's not burning out, doesn't matter? Right? The idea of 9:00 to 5:00, Monday to Friday as a construct is being challenged. The idea of you needing to sit at a physical desk for eight hours a day to do your work, when actually at least half of your tasks you can do asynchronously, that's been challenged. But for the managers who want manage process and control, they're like, "But if Nick can work from anywhere, and we trust him to do the right work, what do I do? I'm his manager. You're like, "You could inspire him. You could coach him, mentor him. You can lead him, you can help him grow, you can do a whole lot of stuff. Just don't manage his tasks for him. He's quite capable of managing a to-do list." It's challenging that construct again. For a lot of people, that's uncomfortable because that's a concept that we've just stuck with for years.

Nick Muldoon:

This is going to lead to a lot of change. I guess I've been thinking with respect to remote, Dom, I've been thinking much more about the mechanics of remote work and logistics around pay scales, and geographic location, and pay, and all this sort of stuff. But you're really opening my eyes to a whole different aspect. There are, in many large organizations, there are a lot of middle managers, and if these roles are no longer valuable, what do all these people do, and how do we help them find something that they love and that they long for? Because presumably they've not longing for-

Dom Price:

Yeah, that's the thing.

Nick Muldoon:

... task management.

Dom Price:

Yeah, yeah. They're probably not deeply entrenched in that as being something they're passionate about, right? It's just like they found themselves in this role. This is the interesting thing. If you look at rescaling, I've been looking at rescaling for a few years as a trend, right? How do we look at the rate of change in both technology, people practice, whatever else? That means that we're all going to have to rescale, right? The idea of education being up until the age of 21, and then you're working 45 years doesn't exist, right? So lifelong learning. You look at that, and you go ... Amazon did a great example last year. Bezos and Amazon put aside a billion dollars to retrench a thousand people that they were going to dispose. Right?

Nick Muldoon:

Yeah, yeah, yeah.

From their warehouses, right?

Dom Price:

Yeah, yeah. They're on automation to displace those people. What was came out recently and said, there's I think, it's like 1,500 people who will be displaced because they're going for fully autonomous distribution centers. They're looking to retrain those people and redeploy them elsewhere. You're like, "Cool, how are we doing that?" The reason I mentioned it is I think we assume it for low skilled, high volume tasks, because that's associate what we've associated with technology disruption in the past. But if you think about it, there was I think about a year and a half ago, McKinsey had a report called The Frozen Middle Layer. It was about how this frozen middle layer was going to thaw and be exposed, right, as these middle managers. There's thousands of them. That phrase, the middle layer, COVID just poured the icing on that. Right? [inaudible 00:53:26]. They're all going, "What? Me? No, no, I've only got 10 years left in my career. Let me sit here, manage a few tasks. I'll take inflationary pay rise every year. I won't cause any trouble." You're like, "I don't know. You can retrain here."

Dom Price:

These people haven't been engineered to think about retraining before. They've been engineered to think about comfort and conservatism and safety. I think we need to appreciate that they still have value in the workplace. I just don't think it's the old value. For them, the four Ls-

Nick Muldoon:

This is going to be a huge shock to this frozen middle layer, as McKinsey called it. I think about so we're Wollongong, Port Kembla. We're in a working class, steel town, and over the course of, pick a number, over the course of 25, 30 years, 20,000, 22,000 people have been let go from the steelworks and they're been told to retrain. I'm sure a portion of them do, but a lot of them that are older, like you're talking about someone that's in their 50s that's got 10 years on their career, right, they probably just took early retirement, and maybe they found something else to do in the community, whatever it happens to be. What are the structures that we provide for this huge crew of people to get them re-skilled in our businesses so that we don't lose the tacit knowledge and get on to the next thing? How's Atlassian thinking about this?

Dom Price:

It's also about front-loading it, right? We have to hold our head in shame as a general society, how light we leave it. When I hear stories about those steelworks closing down, and you're like, "Why are we surprised by that? Why are we surprised when Holden stopped developing cars in Australia? Really? But really, you're surprised?

Nick Muldoon:

We saw it coming.

Dom Price:

Yeah.

Nick Muldoon:

We propped up the car industry in Australia for 35 years.

Dom Price:

Yeah. You put tariffs on anyone importing to make your own industry look good, and then those tariffs go away, people are looking for cheaper. Unfortunately, we signed up for a global economy, right? It's a borderless business model that we're in, and whether you like that or not, it's what we signed up for. The reality is instead of reacting each time this happens when it's normally too late, how can we respond? How can we use these brilliant algorithms and data managing to go, "Here are world economic forum future skills, here are large employers, here are other skillsets about people." You try and give that out, and you're like, "These are the ones most at risk, and they're at risk over the next 18 months." Cool. Start retraining them now, but not when they're out of the job when they go, "Well, now, I'm out of my job. Now, what do we do?" You're like, "I don't know. Buddings? I don't know."

Dom Price:

We've got way more data and insights than we probably give ourselves credit for. I think one element is front-loading it, and the next one is saying, "How do we not recreate this problem again?" If you look in the US right now, the largest employer, not by company, but by job type is driver.

Nick Muldoon:

Okay. Yeah, by role. Yeah, yeah, yeah.

Dom Price:

By role, right? So Uber driver, truck drivers, manual drivers, people behind the wheel driving a vehicle. Where's billions of dollars worth of investment going in, Google, Amazon and every other? Right? Autonomous vehicles. You're like, "Cool."

Nick Muldoon:

Autonomous vehicles. Get rid of all those people?

Dom Price:

If I-

Nick Muldoon:

What are we doing to reskill those people?

Dom Price:

Yeah. Or even better, what are we doing in our education system to say, "How do we help people coming through the education system be more resilient with their future skills? I don't like the idea of being able to future-proof people. I don't think we've got a crystal ball, so let's part that. But how do we make people more resilient in their skills, well, all the skills we think will be required? World Economic Forum do great research every few years and publish it, and then I look at the education system, and I'm like, "That was built in 1960. We're tuning kids out that if you talk to.

Nick Muldoon:

Hey, hey, hey, Dom, okay, okay. I'm getting anxious at the moment. Let's end on a high note. What are things that make you optimistic for the next decade? All right? In 10 years time, how old are you going to be in 10 years time? Like 45 or something?"

Dom Price:

52.

Nick Muldoon:

52?

Dom Price:

Yeah.

Nick Muldoon:

Okay. Oh, yes.

Dom Price:

Getting old.

Nick Muldoon:

Yeah, okay. Yeah, okay. Okay, so when you're 52, what are you looking forward to over the next decade? What's exciting?

Dom Price:

There's a couple of things we need to realize, right? Very first thing we need to accept is our future is not predetermined, it's not written, and it's not waiting for us. Right? We design it and define it every single day with our actions and inactions. As soon as we have that acknowledgement, we don't sit here as a victim anymore and wait for it to happen to us. We go, "Oh, oh, yeah." Then like, "We have to decide on the future. No one else does. We collectively do." That's the first step. You're like, "Oh, I've got way more say in this than I ever realized." The second one is, we need to drop a whole load of stuff around productivity, and GDP, and all these things that we've been taught are great measures of success, and just be happy and content in life. If you've got four years left, I've probably got 30 something years left, I want to enjoy those 30 years. I have no vision of being buried in a gravestone somewhere with, "Dom was productive."

Nick Muldoon:

Dom, this is great. What we've got to do for society over the next 10 years is get society out of KPIs and into OKRs.

Dom Price:

Yeah.

Nick Muldoon:

Right?

Dom Price:

And get a balance out of going, "How ... This is what I've learned from COVID, right? You know this, I did 100 flights last year. I did a few at the start of the year and trip to the UK in the middle of COVID. But I've not traveled since June. Now, admittedly, the whole work from home thing, I'm going insane a little bit, but the balance of life, like sleeping in my bed every night, hanging out with friends, meaningful connections, right, actual community. I've lived in the same apartment for three years, and it took COVID for me to meet any of my neighbors, and it took COVID for me to meet the lovely ladies in the coffee shop downstairs. I'm like, "I've lived above you for three years, and it's only now you've become a person." Right?

Dom Price:

There's so much community and society aspects we can get out of this. The blank piece of paper, if you imagine this as a disruption that's happened to us, and there's no choice, and we can fight against it, that the options we have to actually make life better afterwards. Whether it be four-day working week experiments, or actually working from anywhere means that a whole other disabled, or working parents can get access to the workforce. Funny, if you get more done. Unemployment in the disabled community is 50% above that of the able-bodied community, not because of any mental ability, just because it's hard for them to fit .

Nick Muldoon:

Logistically. Yeah.

Dom Price:

You've just changed that, right, with this crazy experiment called COVID. If we start to tap into these pockets of goodness, and actually, we sees this as an opportunity to innovate, right, and I hate the P word of pivot, but forget pivoting, to genuinely innovate, what might the world look like, and how can we lean into that? How do we get balance between profit, and planet, and people, and climate, and all those things? If we do that, we've got a chance to build this now and build a future we want that we're actually proud of. I think the time is now for us to all stand up because it's not going to happen to us ... Or it will happen to us. If we choose to do nothing, it'll happen to us. It doesn't need to. I'm really excited because I think we're going to make some fundamental changes and challenges to old ways of working and old ways of living, and we'll end up happier because of it.

Nick Muldoon:

Don, I'm super jazzed, man. Thank you. I really appreciate your time today. That's a great place to finish it up.

Dom Price:

I hope some of those things come true.

Nick Muldoon:

Okay. I hope some of those things come true, right? I feel like the things that are in our power, the things that we can directly affect, takeaways for me, I've got extending the love and loathe into the love, loathe, long for and learned. I think that's great. I also like the boomerang versus the stick with respect to your time and what's on the calendar, and just jettison the stuff that is, well, it's not helping you, or the teams, or anyone else. Yeah.

Dom Price:

You could do it like [inaudible 01:01:33]. If it ends up being important, you can add it back.

Nick Muldoon:

Sure.

Dom Price:

[inaudible 01:01:38].

Nick Muldoon:

The big takeaway from this conversation for me is that it's in our hands. The choice, we make the decisions. It's in our hands. I think about, was Mark Twain, whether you think you can or whether you think you can't, you're right.

Dom Price:

Yeah. Yeah.

Nick Muldoon:

You might as well think you can and get on with it.

Dom Price:

Yeah, yeah, give it a red-hot stab and see what happens.

Nick Muldoon:

All right, cool. Don, thanks so much for your time this morning. Really appreciate it.

Dom Price:

It was great chatting.

Related Episodes

  • Podcast

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

    Sean Blake

    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.

  • Podcast

    Easy Agile Podcast Ep.12 Observations on Observability

    On this episode of The Easy Agile Podcast, tune in to hear developers Angad, Jared, Jess and Jordan, as they share their thoughts on observability.  

    Wollongong has a thriving and supportive tech community and in this episode we have brought together some of our locally based Developers from Siligong Valley for a round table chat on all things observability.

    💥 What is observability?
    💥 How can you improve observability?
    💥 What's the end goal?

    Angad Sethi

    "This was a great episode to be a part of! Jess and Jordan shared some really interesting points on the newest tech buzzword - observability""

    Be sure to subscribe, enjoy the episode 🎧

    Transcript

    Jared Kells:

    Welcome everybody to the Easy Agile podcast. My name's Jared Kells, and I'm a developer here at Easy Agile. Before we begin, Easy Agile would like to acknowledge the traditional custodians of the land from which we broadcast today, the Wodiwodi people of the Dharawal nation, and pay our respects to elders past, present and emerging, and extend that same respect to any aboriginal people listening with us today.

    Jared Kells:

    So today's podcast is a bit of a technical one. It says on my run sheet here that we're here to talk about some hot topics for engineers in the IT sector. How exciting that we've got a couple of primarily front end engineers and Angad and I are going to share some front end technical stuff and Jess and Jordan are going to be talking a bit about observability. So we'll start by introductions. So I'll pass it over to Jess.

    Jess Belliveau:

    Cool. Thanks Jared. Thanks for having me one as well. So yeah, my name's Jess Belliveau. I work for Apptio as an infrastructure engineer. Yeah, Jordan?

    Jordan Simonovski:

    I'm Jordan Simonovski. I work as a systems engineer in the observability team at Atlassian. I'm a bit of a jack of all trades, tech wise. But yeah, working on building out some pretty beefy systems to handle all of our data at Atlassian at the moment. So, that's fun.

    Angad Sethi:

    Hello everyone. I'm Angad. I'm working for Easy Agile as a software dev. Nothing fancy like you guys.

    Jared Kells:

    Nothing fancy!

    Jess Belliveau:

    Don't sell yourself short.

    Jared Kells:

    Yeah, I'll say. Yeah, so my name's Jared, and yeah, senior developer at Easy Agile, working on our apps. So mainly, I work on programs and road maps. And yeah, they're front end JavaScript heavy apps. So that's where our experience is. I've heard about this thing called observability, which I think is just logs and stuff, right?

    Jess Belliveau:

    Yeah, yeah. That's it, we'll wrap up!

    Jared Kells:

    Podcast over! Tell us about observability.

    Jess Belliveau:

    Yeah okay, I'll, yeah. Well, I thought first I'd do a little thing of why observability, why we talk about this and sort of for people listening, how we got here. We had a little chat before we started recording to try and feel out something that might interest a broader audience that maybe people don't know a lot about. And there's a lot of movements in the broad IT scope, I guess, that you could talk about. There's so many different things now that are just blowing up. Observability is something that's been a hot topic for a couple of years now. And it's something that's a core part of my job and Jordan's job as well. So it's something easy for us to talk about and it's something that you can give an introduction to without getting too technical. So we don't want to get down. This is something that you can go really deep into the weeds, so we picked it as something that hopefully we can explain to you both at a level that might interest the people at home listening as well.

    Jess Belliveau:

    Jordan and I figured out these four bullet points that we wanted to cover, and maybe I can do the little overview of that, and then I can make Jordan cover the first bullet point, just throw him straight under the bus.

    Jordan Simonovski:

    Okay!

    Jess Belliveau:

    So we thought we'd try and describe to you, first of all, what is observability. Because that's a pretty, the term doesn't give you much of what it is. It gives you a little hint, but it'll be good to base line set what are we talking about when we say what is observability. And then why would a development team want observability? Why would a company want observability? Sort of high level, what sort of benefits you get out of it and who may need it, which is a big thing. You can get caught up in these industry hot buzz words and commit to stuff that you might not need, or that sort of stuff.

    Jared Kells:

    Yep.

    Jordan Simonovski:

    Yep.

    Jess Belliveau:

    We thought we'd talk about some easy wins that you get with observability. So some of the real basic stuff you can try and get, and what advantages you get from it. And then we just thought because we're no going to try and get too deep, we could just give a few pointers to some websites and some YouTube talks for further reading that people want to do, and go from there. So yeah, Jordan you want to-

    Jared Kells:

    Sounds good.

    Jess Belliveau:

    Yeah. I hopefully, hopefully. We'll see how this goes! And I guess if you guys have questions as well, that's something we should, if there's stuff that you think we don't cover or that you want to know more, ask away.

    Jordan Simonovski:

    I guess to start with observability, it's a topic I get really excited about, because as someone that's been involved in the dev ops and SRE space for so long, observability's come along and promises to close the loop or close a feedback loop on software delivery. And it feels like it's something we don't really have at the moment. And I get that observability maybe sounds new and shiny, but I think the term itself exists to maybe differentiate itself from what's currently out there. A lot of us working in tech know about monitoring and the loading and things like that. And I think they serve their own purpose and they're not in any way obsolete either. Things like traditional monitoring tools. But observability's come along as a way to understand, I think, the overwhelmingly complex systems that we're building at the moment. A lot of companies are probably moving towards some kind of complicated distributed systems architecture, microservices, other buzz words.

    Jordan Simonovski:

    But even for things like a traditional kind of monolith. Observability really serves to help us ask new questions from our systems. So the way it tends to get explained is monitoring exits for our known unknowns. With seniority comes the ability to predict, almost, in what way your systems will fail. So you'll know. The longer you're in the industry, you know this, like a Java server fails in x, y, z amount of ways, so we should probably monitor our JVM heap, or whatever it is.

    Jared Kells:

    I was going to say that!

    Jordan Simonovski:

    I'll try not to get too much into-

    Jared Kells:

    Runs out of memory!

    Jordan Simonovski:

    Yeah. So that's something that you're expecting to fail at some point. And that's something that you can consider a known unknown. But then, the promise of observability is that we should be shipping enough data to be able to ask new questions. So the way it tends to get talked about, you see, it's an unknown unknown of our system, that we want to find out about and ask new questions from. And that's where I think observability gets introduced, to answer these questions. Is that a good enough answer? You want me to go any further into detail about this stuff? I can talk all day about this.

    Jared Kells:

    Is it like a [crosstalk 00:08:05]. So just to repeat it back to you, see if I've understood. Is it kind of like if I've got a, traditionally with a Java app, I might log memories. It's because I know JVM's run out of memory and that's a thing that I monitor, but observability is more broad, like going almost over the top with what you monitor and log so that you can-

    Jordan Simonovski:

    Yeah. And I wouldn't necessarily say it's going over the top. I think it's maybe adding a bit more context to your data. So if any of you have worked with traces before, observability is very similar to the way traces work and just builds on top of the premise of traces, I guess. So you're creating these events, and these events are different transactions that could be happening in your applications, usually submitting some kind of request. And with that request, you can add a whole bunch of context to it. You can add which server this might be running on, which time zone. All of these additional and all the exciters. You can throw in user agency into there if you want to. The idea of observability is that you're not necessarily constrained by high cardinality data. High cardinality data being data sets that can change quite largely, in terms of the kinds of data they represent, or the combinations of data sets that you could have.

    Jordan Simonovski:

    So if you want shipping metrics on something, on a per user basis and you want to look at how different users are affected by things, that would be considered a high cardinality metric. And a lot of the time it's not something that traditional monitoring companies or metric providers can really give you as a service. That's where you'll start paying insanely huge bills on things like Datadog or whatever it is, because they're now being considered new metrics. Whereas observability, we try and store our data and query it in a way that we can store pretty vast data sets and say, "Cool. We have errors coming from these kinds of users." And you can start to build up correlations on certain things there. You can find out that users from a particular time zone or a particular device would only be experiencing that error. And from there, you can start building up, I think, better ways of understanding how a particular change might have broken things. Or some particular edge cases that you otherwise couldn't pick up on with something like CPU or memory monitoring.

    Angad Sethi:

    Would it be fair to say-

    Jared Kells:

    Yeah. It's [crosstalk 00:11:02].

    Angad Sethi:

    Oh, sorry Jared.

    Jared Kells:

    No you can-

    Angad Sethi:

    Would it be fair to say that, so, observability is basically a set of principles or a way to find the unknown unknowns?

    Jordan Simonovski:

    Yeah.

    Angad Sethi:

    Oh.

    Jess Belliveau:

    And better equip you to find, one of the things I find is a lot of people think, you get caught up in thinking observability is a thing that you can deploy and have and tick a box, but I like your choice of word of it being a set of principles or best practices. It's sort of giving you some guidance around these, having good logging coming out of your application. So structured logs. So you're always getting the same log format that you can look at. Tracing, which Jordan talked a little bit about. So giving you that ability to follow how a user is interacting with all the different microservices and possibly seeing where things are going wrong, and metrics as well. So the good thing with metrics is we're turning things a bit around and trying to make an application, instead of doing, and I don't want to get too technical, black box monitoring, where we're on the outside, trying to peer in with probes and checks like that. But the idea with metrics is the application is actually emitting these metrics to inform us what state it is in, thereby making it more observable.

    Jess Belliveau:

    Yeah, I like your choice of words there, Angad, that it's like these practices, this sort of guide of where to go, which probably leads into this next point of why would a team want to implement it. If you want to start again, Jordan?

    Jordan Simonovski:

    Yeah, I can start. And I'll give you a bit more time to speak as well, Jess in this one. I won't rant as much.

    Jess Belliveau:

    Oh, I didn't sign up for that!

    Jordan Simonovski:

    I think why teams would want it is because, it really depends on your organization and, I guess, the size of the teams you're working in. Most of the time, I would probably say you don't want to build observability yourself in house. It is something that you can, observability capabilities themselves, you won't achieve it just by buying a thing, like you can't buy dev ops, you can't buy Agile, you can't buy observability either.

    Jared Kells:

    Hang on, hang on. It says on my run sheet to promote Easy Agile, so that sounds like a good segue-

    Jess Belliveau:

    Unless you want to buy it. If you do want to buy Agile, the [crosstalk 00:13:55] in the marketplace.

    Jared Kells:

    Yeah, sorry, sorry, yeah! Go on.

    Jordan Simonovski:

    You can buy tools that make your life a lot easier, and there are a lot of things out there already which do stuff for people and do surface really interesting data that people might want to look at. I think there are a couple of start ups like LightStep and Honeycomb, which give you a really intuitive way of understanding your data in production. But why you would need this kind of stuff is that you want to know the state of your systems at any given point in time, and to build, I guess, good operational hygiene and good production excellence, I guess as Liz Fong-Jones would put it, is you need to be able to close that feedback loop. We have a whole bunch of tools already. So we have CICD systems in place. We have feature flags now, which help us, I guess, decouple deployments from releases. You can deploy code without actually releasing code, and you can actually give that power to your PM's now if you want to, with feature flags, which is great.

    Jordan Simonovski:

    But what you can also do now is completely close this loop, and as you're deploying an application, you can say, "I want to canary this deployment. I want to deploy this to 10% of my users, maybe users who are opted in for Beta releases or something of our application, and you can actually look at how that's performing before you release it to a wider audience. So it does make deployments a lot safer. It does give you a better understanding of how you're affecting users as well. And there are a whole bunch of tools that you can use to determine this stuff as well. So if you're looking at how a lot of companies are doing SRE at the moment, or understanding what reliable looks like for their applications, you have things like SLO's in place as well. And SLO's-

    Jared Kells:

    What's an SLO?

    Jordan Simonovski:

    They're all tied to user experiences. So you're saying, "Can my user perform this particular interaction?" And if you can effectively measure that and know how users are being affected by the changes you're making, you can easily make decisions around whether or not you continue shipping features or if you drop everything and work on reliability to make sure your users aren't affected. So it's this very user centric approach to doing things. I think in terms of closing the loop, observability gives us that data to say, "Yes, this is how users are being affected. This is how, I guess the 99th percentile of our users are fine, but we have 1% who are having adverse issues with our application." And you can really pinpoint stuff from there and say, "Cool. Users with this particular browser or this particular, or where we've deployed this app to," let's say if you have a global deployment of some kind, you've deployed to an island first, because you don't really care what happens to them. You can say, "Oh, we've actually broken stuff for them." And you can roll it back before you impact 100% of your users.

    Jared Kells:

    Yeah. I liked what you said about the test. I forgot the acronym, but actually testing the end user behavior. That's kind of exciting to me, because we have all these metrics that are a bit useless. They're cool, "Oh, it's using 1% CPU like it always is, now I don't really care," but can a user open up the app and drag an issue around? It's like-

    Jess Belliveau:

    Yeah, that's a really great example, right?

    Jared Kells:

    That's what I really care about.

    Jess Belliveau:

    The 1% CPU thing, you could look at a CPU usage graph and see a deployment, and the CPU usage doesn't change. Is everything healthy or not? You don't know, whereas if you're getting that deeper level info of the user interactions, you could be using 1% CPU to serve HTTP500 errors to the 80% of the customer base, sort of thing.

    Angad Sethi:

    How do you do that? The SLO's bit, how do you know a user can log in and drag an issue?

    Jordan Simonovski:

    Yeah. I think that would come with good instrumenting-

    Angad Sethi:

    Good question?

    Jordan Simonovski:

    Yeah, it comes down to actually keeping observability in mind when you are developing new features, the same way you would think about logging a particular thing in your code as you're writing, or writing test for your code, as you're writing code as well. You want to think about how you can instrument something and how you can understand how this particular feature is working in production. Because I think as a lot of Agile and dev ops principles are telling us now is that we do want our applications in production. And as developers, our responsibilities don't end when we deploy something. Our responsibility as a developer ends when we've provided value to the business. And you need a way of understanding that you're actually doing that. And that's where, I guess, you do nee do think about observability with a lot of this stuff, and actually measuring your success metrics. So if you do know that your application is successful if your user can log in and drag stuff around, then that's exactly what you want to measure.

    Jared Kells:

    I think that we have to build-

    Jordan Simonovski:

    Yeah?

    Jared Kells:

    Oh, sorry Jordan.

    Jordan Simonovski:

    No, you go.

    Jared Kells:

    I was just going to say we have to build our apps with integration testing in mind already. So doing browser based tests around new features. So it would be about building features with that and the same thing in mind but for testing and production.

    Jess Belliveau:

    Yeah and the actual how, the actual writing code part, there's this really great project, the open telemetry project, which provides all these sort of API's and SDK's that developers can consume, and it's vendor agnostic. So when you talk about the how, like, "How do I do this? How do I instrument things?" Or, "How do I emit metrics?" They provide all these helpful libraries and includes that you can have, because the last thing you want to do is have to roll this custom solution, because you're then just adding to your technical debt. You're trying to make things easier, but you're then relying on, "Well I need to keep Jared Kells employed, because he wrote our log in engine and no one else knows how it works.

    Jess Belliveau:

    And then the other thing that comes to mind with something like open telemetry as well, and we talked a bit about Datadog. So Datadog is a SaaS vendor that specializes in observability. And you would push your metrics and your logs and your traces to them and they give you a UI to display. If you choose something that's vendor agnostic, let's just use the example of Easy Agile. Let's say they start Datadog and then in six months time, we don't want to use Datadog anymore, we want to use SignalFx or whatever the Splunk one is now.

    Jordan Simonovski:

    I think NorthX.

    Jess Belliveau:

    Yeah. You can change your end point, push your same metrics and all that sort of stuff, maybe with a few little tweaks, but the idea is you don't want to tie in to a single thing.

    Jordan Simonovski:

    Your data structures remain the same.

    Jess Belliveau:

    Yeah. So that you could almost do it seamlessly without the developers knowing. There's even companies in the past that I think have pushed to multiple vendors. So you could be consuming vendor A and then you want to do a proof of concept with vendor B to see what the experience is like and you just push your data there as well.

    Jared Kells:

    Yeah. I think our coupling to Datadog will be I all the dashboards and stuff that we've made. It's not so much the data.

    Jess Belliveau:

    Yeah. That's sort of the big up sell, right. It's how you interact. That's where they want to get their hooks in, is making it easier for you to interpret that data and manipulate it to meet your needs and that sort of stuff.

    Jordan Simonovski:

    Observability suggests dashboards, right?

    Jess Belliveau:

    Yeah, perhaps. You used this term as well, Jordan, "production excellence." And when we talk about who needs observability, I was thinking a bit about that while you were talking. And for me, production excellence, or in Apptio we call it production readiness, operational readiness and that sort of stuff is like we want to deploy something to production like what sort of best practices do we want to have in place before we do that? And I think observability is a real great idea, because it's helping you in the future. You don't know what problems you're going to have down the line, but you're equipping your teams to be able to respond to those problems easily. Whereas, we've all probably been there, we've deployed code of production and we have no observability, we have a huge outage. What went wrong? Well, no one knows, but we know this is the fix, and it's hard to learn from that, or you have to learn from that I guess, and protect the user against future stuff, yeah.

    Jess Belliveau:

    When I think easy wins for observability, the first thing that really comes to mind is this whole idea of structured logging, which is really this idea that your application is you're logging, first of all. Quite important as a baseline starting point, but then you have a structured log format which lets you programmatically pass the logs as well. If you go back in time, maybe logging just looked like plain text with a line, with a timestamp, an error message. Whatever the developer decided to write to the standard out, or to the error file or something like that. Now I think there's a general move to having JSON, an actual formatted blob with that known structure so you can look into it. Tracing's probably not an easy win. That's a little bit harder. You can implement it with open telemetry and libraries and stuff. Requires a bit more understanding of your code base, I guess, and where you want tracing to fire, and that sort of stuff, parsing context through, things like that.

    Jordan Simonovski:

    I think Atlassian, when you probably just want to know that everything is okay. At a fairly superficial level. Maybe you just want to do some kind of up time on a trend. And then as, I guess, your code might get more complex or your product gets a bit more complex, you can start adding things in there. But I think actually knowing or surfacing the things you know might break. Those would probably be your quickest wins.

    Jess Belliveau:

    Well, let's mention some things for further reading. If you want to go get the whole picture of the whole, real observability started to get a lot of movement out of the Google SRE book from a few years ago. The Google SRE stuff covers the whole gamut of their soak reliability engineering practice, and observability is a portion of that, there's some great chapters on that. O'Reilly has an observability book, I think, just dedicated to observability now.

    Jordan Simonovski:

    I think that's still in early release, if people want to google chapters.

    Jess Belliveau:

    The open telemetry stuff, we'll drop a link to that I think that's really handy to know.

    Angad Sethi:

    From [inaudible 00:26:12], which is my perspective, as a developer, say I wanted to introduce cornflake use Datadog at Easy Agile. Not very familiar, I'm not very comfortable with it. I know how to navigate, but what's a quick way for me to get started on introducing observability? Sorry to lock my direct job or at my workplace.

    Jordan Simonovski:

    I would lean, I could be biased here. Jess correct me or give your opinion on this, I would lean heavily towards SLO's for this. And you can have a quick read in the SRE-

    Jess Belliveau:

    What does SLO stand for, Jordan?

    Jordan Simonovski:

    Okay, sorry. Buzz words! SLO is a service level objective, not to be confused with service level agreement. An agreement itself is contractual and you can pay people money if you do breach those. An SLO is something you set in your team and you have a target of reliability, because we are getting to the point where we understand that all systems at any point in time are in some kind of degraded state. And yeah, reliability isn't necessarily binary, it's not unreliable or reliable. Most of the time, it's mostly reliable and this gives us a better shared language, I guess. And you can have a read in the SRE handbook by Google, which is free online, which gives you a pretty good understanding of Datadog.

    Jordan Simonovski:

    I think the last time I used it had a SLO offering. But I think like I was mentioning earlier, you set an SLO on particular functionalities or features of your application. You're saying, "My user can do this 99% of the time," or whatever other reliability target you might want to set. I wouldn't recommend five nines of reliability. You'll probably burn yourself out trying to get there. And you have this target set for yourself. And you know exactly what you're measuring, you're measuring particular types of functionality. And you know when you do breach these, users are being affected. And that's where you can actually start thinking about observability. You can think about, "What other features are we implementing that we can start to measure?" Or, "What user facing things are we implementing that we can start to measure?"

    Jordan Simonovski:

    Other things you could probably look at are, I think they're all covered in the book anyway, data freshness in a way. You want to make sure the data users are being displayed is relatively fresh. You don't want them looking at stale data, so you can look at measuring things like that as well. But you can pretty much break it down into most functionalities of a website. It's no longer like a ping check, that you're just saying, "Yes, HTTP, okay. My application is fine." You're saying, "My users are actually being affected by things not working." And you can start measuring things from there. And that should give you a better understanding, or a better idea, at least, of where to start with what you want to measure and ow you want to measure it. That would be my opinion on where to get started with this if you do want to introduce it.

    Jared Kells:

    We're going to talk a little bit about state and how with some of these, like our very front end heavy applications that we're building, so the applications we build just basically run inside the browser and the traditional state as you would think about it, is just pulling a very simple API that writes some things into the database with some authentication, and that sort of stuff. So in terms of reliability of the services, it's really reliable. Those tiny API's just never have problems, because it's just so simple. And well, they've got plenty of monitoring around it. But all our state is actually, when you say, "Observe the state of the system," for the most part, that's state in a browser. And how do we get observability into that?

    Jess Belliveau:

    A big thing is really, there's not one thing fits all as well. When we talk about the SLO stuff as well, it's understanding what is important to not so much maybe your company but your team as well. If you're delivering this product, what's important to you specifically? So one SLO that might work for me at Apptio probably isn't going to work for Easy Agile. This is really pushing my knowledge, as well, of front end stuff, but when we say we want to observe the state as well, we don't necessarily mean specifically just the state. You could want to understand with each one of those API's when it's firing, what the request response time is for that API firing. So that might be an important metric. So you can start to see if one of those APIs is introducing latency, and so your user experience is degraded. Like, "Hey when we were on release three, when users were interacting with our service here, it would respond in this percentile latency. We've done a release and since then, now we're seeing it's now in this percentile. Have we degraded performance performance?" Users might not be complaining, but that could be something that the team then can look into, add to a sprint. Hey, I'm using Agile terms now. Watch out!

    Jared Kells:

    That's a really good example, Jess. Performance issues for us are typically not an API that's performing poorly. It's something in this very complicated front end application is not running in the same order as it used to, or there's some complex interaction we didn't think of, so it's requesting more data than expected. The APIs are returning. They're never slow, for the most part, but we have performance regressions that we may not know about without seeing them or investigating them. The observability is really at the individual user's browser level. That makes sense? I want to know how long did it take for this particular interaction to happen.

    Jess Belliveau:

    Yeah. I've never done that sort of side of things. As well, the other thing I guess, you could potentially be impacted in as well as then, you're dealing with end user manifestations as well. You could perceive-

    Jared Kells:

    Yeah sure.

    Jess Belliveau:

    ... Greater performance on their laptop or something, or their ISP or that sort of stuff. It'd be really hard to make sure you're not getting noise from that sort of thing as well.

    Jordan Simonovski:

    Yeah. There are tools like Sentry, I guess, which do exist to give you a bit more of an understanding what's happening on your front end. The way Sentry tends to work with JavaScript, is you'll upload a minified map of your JS to Sentry, deploy your code and then if something does break or work in a fairly unexpected way, that tends to get surfaced with Sentry will tell you exactly which line this kind of stuff is happening on, and it's a really cool tool for that company stuff. I don't know if it'd give you the right type of insights, I think, in terms of performance or-

    Jared Kells:

    Yeah, we use a similar tool and it does work for crashes and that sort of thing. And on the observability front, we log actions like state mutations in side the front end, not the actual state change, but just labels that represent that you updated an issue summary or you clicked this button, that sort of thing, and we send those with our crash reports. And it's super helpful having that sort of observability. So I think I know what you guys are talking about. But I'm just [crosstalk 00:35:25], yeah.

    Jess Belliveau:

    Yeah, that's almost like, I guess, a form of tracing. For me and Jordan, when we talk about tracing, we might be thinking about 12 different microservices sitting in AWS that are all interacting, whereas you're more shifting that. That's sort of all stuff in the browser interacting and just having that history of this is what the user did and how they've ended up-

    Jared Kells:

    In that state.

    Jess Belliveau:

    In that state, yeah.

    Jordan Simonovski:

    I guess even if you don't have a lot of microservices, if you're talking about particular, like you're saying for the most part your API requests are fine but sometimes you have particularly large payloads-

    Jared Kells:

    We actually have to monitor, I don't know, maybe you can help with this, we actually should be monitoring maybe who we're integrating with. It's actually much more likely that we'll have a performance issue on a Xero API rather than... We don't see it, the browser sees it as well, which is-

    Jordan Simonovski:

    Yeah, and tracing does solve all of those regressions for you. Most tracing libraries, like if you're running Node apps or whatever on your backend. I can just tell you about Node, because I probably have the most experience writing Node stuff. You pretty much just drop in Didi trace, which is a Datadog library for tracing into your backend and your hook itself into all of, I think, the common libraries that you'll tend to work with, I think. Like if you're working for express or for a lot of just HADP libraries, as well as a few AWS services, it will kind of hook itself into that. And you can actually pinpoint. It will kind of show you on this pretty cool service map exactly which services you're interacting with and where you might be experiencing a regression. And I think traces do serve to surface that information, which is cool. So that could be something worth investigating.

    Jess Belliveau:

    It's funny. This is a little bit unrelated to observability, but you've just made me think a bit more about how you're saying you're reliant on third party providers as well. And something I think that's really important that sometimes gets missed is so many of us today are relying on third party providers, like AWS is a huge thing. A lot of people writing apps that require AWS services. And I think a lot of the time, people just assume AWS or Jira or whatever, is 100% up time, always available. And they don't write their code in such a way that deals with failures. And I think it's super important. So many times now I've seen people using the AWS API and they don't implement exponential back off. And so they're basically trying to hit the AWS API, it fails or they might get throttled, for example, and then they just go into a fail state and throw an error to the user. But you could potentially improve that user experience, have a retry mechanism automatically built in and that sort of stuff. It doesn't really tie into the observability thing, but it's something.

    Jared Kells:

    And the users don't care, right? No one cares if it's an AWS problem. It's your problem, right, your app is too slow.

    Jess Belliveau:

    Well, they're using your app. Exactly right. It reflects on you sort of thing, so it's in your interest to guard against an upstream failure, or at least inform the user when it's that case. Yeah.

    Jared Kells:

    Well, I think we're going to have to call it, this podcast, because it was an hour ago. We had instructed max 45 minutes.

    Jess Belliveau:

    We could just keep going. We might need a part two! Maybe we can request [cross talk 00:39:21].

    Jared Kells:

    Maybe! Yeah.

    Jess Belliveau:

    Or we'll just start our own podcast! Yeah.

    Angad Sethi:

    So what were your biggest learnings today, given it's been Angad and I are just learning about observability, Angad what was your biggest learning today about observability? My biggest learning was that observability does not equal Datadog. No, sorry! It was just very fascinating to learn about quantifying the known unknowns. I don't know if that's a good takeaway, but...

    Jess Belliveau:

    Any takeaway is a good takeaway! What about you, Jared?

    Jared Kells:

    I think, because I we were going to talk about state management, and part of it was how we have this ability, at the moment to, the way our front ends are architected, we can capture the state of the app and get a customer to send us their state, basically. And we can load it into our app and just see exactly how it was, just the way our state's designed. But what might be even cooler is to build maybe some observability into that front end for support. I'm thinking instead of just having, we have this button to send us out your support information that sends us a bunch of the state, but instead of console logging to the browser log, we could be console logging, logging in our front end somewhere that when they click, "send support information," our customers should be sending us the actions that they performed.

    Jared Kells:

    Like, "Hey there's a bug, send us your support information." It doesn't have to be a third party service collecting this observability stuff. We could just build into our... So that's what I'm thinking about.

    Jess Belliveau:

    Yeah, for sure. It'll probably be a lot less intrusive, as well, as some of the third party stuff that I've seen around.

    Jared Kells:

    Yeah. It's pretty hard with some of these integrations, especially if you're developing apps that get run behind a firewall.

    Jess Belliveau:

    Yeah

    Jared Kells:

    You can't just talk to some of these third parties. So yeah, it's cool though. It's really interesting.

    Jess Belliveau:

    Well, I hope someone out there listening has learned something, and Jordan and I will send some links through, and we can add them, hopefully, to the show notes or something so people can do some more reading and...

    Jared Kells:

    All thanks!

    Jess Belliveau:

    Thanks for having us, yeah.

    Jared Kells:

    Thanks all for your time, and thanks everybody for listening.

    Jordan Simonovski:

    Thanks everyone.

    Angad Sethi:

    That was [inaudible 00:41:55].

    Jess Belliveau:

    Tune in next week!

  • Podcast

    Easy Agile Podcast Ep.28 Team23! + the world of work

    Dave Elkan, Co-Founder and Co-CEO of Easy Agile is joined by Jean-Philippe Comeau Principal Customer Success Advocate at Adaptavist.

    "Hearing from JP is a sure-fire way to get excited about Atlassian Team '23. We spoke about where we are hoping to see conversations focus + more."

    JP is passionate about teamwork, meeting new people, presentations of all kinds - loves a microphone and a captive audience, new technologies and most of all problem-solving.

    In this episode, JP and Dave are talking about one of the most anticipated events in the tech calendar - Atlassian’s Team23! They’re talking about what to expect, tips for first timers and what they’re hoping to take away from the event.

    They also dive into the future of work and the significance of coming together as a team.

    We hope you enjoy the episode!

    Transcript:

    Dave Elkan:

    Hi, all, and welcome to the Easy Agile Podcast. My name is Dave Elkan and I'm co-founder and co-CEO here at Easy Agile. Before we begin, Easy Agile would like to acknowledge the traditional custodians of the land from which we broadcast today, the people of the Dharawal speaking country. We pay our respects to elders past, present, and emerging, and extend that same respect to all Aboriginal, Torres State Islander and First Nations people joining us today. Today I am joined by Jean-Philippe Comeau or JP. JP is the principal customer success advocate at Adaptavist and is passionate about teamwork, meeting new people, presentations of all kinds, loves a microphone and a captive audience, this podcast definitely fits that mold, new technologies, and most of all, problem-solving. JP, thanks so much for being with us today.

    Jean-Philippe Comeau:

    Thanks for inviting me.

    Dave Elkan:

    Hey, no worries. It's great to have you on. We want to take some time today just to talk through Atlassian Team '23. The ecosystem is gearing up for one of the biggest events of the calendar and the ultimate event for modern teamwork. You've been to a few Atlassian Team events before and last year being the first one back in a while. Quebec to Las Vegas is quiet a gear change. What are your tips for people attending Team for the first time?

    Jean-Philippe Comeau:

    Ooh, yeah, that's a good question. I mean, yeah, Teams to me is a massive event. It's a beautiful moment to actually take in everything that has happened in last year for Atlassian. What I mean by that is actually more and more what's happening with Atlassian is actually what's happening in the world of work. So I think it's just a great time to reassess where you're at. So for me, it's about planning out the main things you want to hit and don't overcrowd your schedule. That's a mistake I made the first time was just I wanted to see the most of everything and I was like, "Yeah, I can absolutely do back to back to back. It's going to be fine. I'll be walking from one thing to another." Truth is after talk, you'll have some questions. Some things will popped-up. "Oh, that's interesting. I could maybe explore that."

    You're going to want to do maybe some floor hunting, which is like, hey, looking through the partners. Maybe you've heard about something like an app that you really want to go look at or something like that. So, that's always going to happen and then you're going to miss that next talk. So make sure that what you highlight is really things you want to see and plan according to that. That to me is the number one thing. Don't try to do it all. Do what you feel is really, really important than the rest. Try to make it work because it's going to be a lot of walking, a lot of listening, a lot of talking. The second thing which I remind everybody is to hydrate, get a bottle of water. There's going to be plenty over there, but everybody's going to have their own branded bottle of water, so don't worry about having one or not, but get one and just hydrate. I mean, we all get very busy during the day and we all know how the nights can go, so keep drinking some water. Yeah, those are my two tips.

    Dave Elkan:

    That's great advice. I think hydration is certainly something to consider. I remember particularly a wall of donuts at one point distracting me from good habits like that. So yeah, it's really important to make sure you've got the basics in line. What are you most looking forward to from the lineup at Team '23?

    Jean-Philippe Comeau:

    Yeah. I mean, every year the keynotes are what's going to hit the most. Obviously, getting a chance to hear James Cameron talk is going to be very, very interesting. I think especially in the year of Avatar 2 is just great timing, obviously probably planned. He's probably on a tour, but it's going to be really great to hear some stories of how that movie came about. It's been a long time in the making, probably the closest thing we got to really long development on a film. It feels like a long software development cycle thing. That's a very long time. And then hearing Van talk about some of the things that he's seeing in today's world. Van Joseph, I believe, is the name of the second talker, and remember seeing him a lot on the CNN broadcast and stuff during the elections and the impact that he brought to the whole broadcast was quite something. It'd be very interesting to hear them talk.

    And then as far as maybe not the big ticket items, really interested to... I think this is the year where the practices on the different tracks that Atlassian usually promotes, I think this is the year what they really start to hit. What I mean by that is I think before this year, so when you look at last year's Team and then before that, tracks were kind of like wishy-washy. Now, they actually have the products to back them. I think JSM's in a very, very good spot. I think their agile tooling is in a very good spot. I think their DevOps, which is what I expect, is going to be pushed the most, or DevOps tooling with the Jira product discovery and all their Point A stuff is got to be where it's at. So I think you're going to get really good talks on those practices. I think that's going to be the year where the tracks actually make a ton of sense and are very valuable to people.

    Dave Elkan:

    Absolutely. Thanks for sharing. It's really interesting. Yourself, you're a Canadian and James Cameron is a Canadian and he's talking about creating the impossible, and I think that's a theme that's coming through and what Atlassian is promoting and bringing that through. It's really interesting to see or hear you talk about the both building movies and media and CNN, the reference there, and how that can apply with a strongly software development-based audience. It's really interesting to see that building a movie is a very much a waterfall process in that you have this huge deliverable at the end, but I know that there are Pixar, for example, use this concept of Demo Trusts, we call them, or the Pixar Demo Trust. Yeah. So essentially you can test along the way as you go before you deliver this huge thing. It's really intriguing to think what we're going to hear from James in regards to how he builds these amazing projects.

    Jean-Philippe Comeau:

    Yeah, I think you're spot on. So I'm actually a huge Marvel fan. I don't have my book with me, but the Creativity, Inc. is a book that I love by Ed Catmull and how they built Pixar as a business, as a delivery team, not just about the movie side of it, the creative side of it, but how do you bring creativity into a more structured world that is the corporate world kind of thing, which they're now a part of? So, very interesting that you bring that up because I'm very fascinated by their process as well. I think they were the pioneers in the movie-making business or industry into bringing the agile methodologies or thinking to movie-making.

    Now, what would happen historically in movies? Okay. So you don't know this, but my background is actually enacting. So when I started, when I studied, when I was a young lad, young adult, let's put it that way, I wanted to be an actor and then things changed. Obviously, I am not a prolific actor. So I'm very, very passionate about the movie-making industry. Movies historically has always been about you shoot, you shoot, you shoot, to develop, develop, develop, and then at the end, you cut it. So you make mistakes. So like we said, very, very waterfally. I think now that technology is almost like 50 to 60% of a movie now more days... If you look at Marvel movies and all that, you could argue it's 50 to 60% is going to be computer-generated, which can be a bad or good thing. Now, that I'm not going to get into that debate.

    The nature of previz and all the animation work that goes behind it makes the process more agile, meaning that what they're going to do is they're going to build for a week and then they're going to review the film that's been made and then they're going to correct and do it again, right? So already you got your feedback loop going. You got your process. You got your sprints going. I can map all that out to some agile processes and I wouldn't be surprised that you're looking at something that are looking to scale up. You could even argue what are you guys going to do for your scaling methodologies? There's a lot of things that are very interesting.

    I think going back to our first point, sorry, I really went on a tangent here, but going back to Avatar, when you have such a long cycle and you have a movie that's built, that one is heavily computer-generated. I mean, every actor has stuff on their face and they're acting in a blank studio. Now you're talking about agile processes because if you're building hours and hours and hours of work and you're just building and building and building and never review, I can't... Maybe James will say that's how they did it, and I'll be like, "Well, you guys were... It's very difficult. You made your life very, very difficult." But it'd be very interesting to hear because I cannot imagine them not going into some type of an agile way of building this movie.

    Dave Elkan:

    Oh, of course. I think that if you imagine the cutting room floor, it's an old adage and literally they used to cut the film and they'd leave it on the floor as that's something we're not doing anymore. And so, I dare say that there's a vast amount of film which is thrown away and redone. I feel that if we could see past that to this beautiful thing that they're doing behind the scenes, which is testing and iterating on their shots, it's actually quite a simple concept to apply these agile processes to filmmaking. It's just at the end you have got this big bang, same in game production. When you produce a game, you cut back. People do early access, which is fantastic. You can't early access a movie.

    Jean-Philippe Comeau:

    No, exactly. Yeah.

    Dave Elkan:

    Yeah. Going back to Pixar, that reference, I actually made the mistake. It's not actually the Demo Trust. So this is the Playbook by Atlassian. There's a play called Demo Trust, but it's the Brains Trust and it's bringing together the team to talk through does this fulfill the vision of Pixar? Does this make Pixar Pixar? And helping the team understand, so directors get that ingrained Pixarness through that process. So yeah, there's a whole team behind the scenes here. There's not one person who's just driving this at the director level. There's actually a whole team of people collaborating on this movie. So I'm really intrigued to hear that from James to hear how the teamwork comes out.

    Jean-Philippe Comeau:

    Yeah. I think when you look at a movie like Avatar, again, another thing that we don't think about is the connecting remote teams, which is a big, big part of what we do in 2023 is connecting remote teams so that they feel they're working on one project. When you have a movie like Avatar, your VFX is going to be somewhere. Your actors are going to be another place. And then you're going to have music and sound's going to be somewhere else. Your editors are probably going to be somewhere else. And so, there's a lot of remote work that you do. How do you bring all that together?

    I remember watching the old documentaries around the Lord of the Rings movies, and they were literally flying people in and out with the actual roll of films because they were so afraid that people would steal them and so that they wouldn't put it on the internet and they would actually carry them around. So they had to fly from London to New Zealand to... It's kind of nuts when you think about it in 2023. Really, you had to take a 10-hour flight just to get your film across? It's probably easier also with the data, just the bandwidth and everything. So I think that's also going to be an interesting part is how did you connect teams?

    You brought up a great point around the Pixar way or that's how they call it, the Pixar way. When you think about that, there's some really, really cool ideas behind bringing a team together and rallying them around one project. I think as teams get more remote and distanced from products and things that they're working on, and I do it myself at work. Things become generic. At some point, you're just doing the same thing over and over again. You lose touch a little bit with the work that you do. I think it's a beautiful thing to be able to rally a team around a project and say like, "Do you believe in this project? I believe in this project. Do you believe in this project?" And making sure the team does and if they don't, why don't you? What's preventing you from that? I think there's a lot of good conversations, sorry, that can come from that. Yeah.

    Dave Elkan:

    Absolutely. So yeah, you talk about going more remote. Is that a trend you're seeing, that we're continuing to see more and more teams go remote, or are we seeing a reversal of that to some extent?

    Jean-Philippe Comeau:

    It depends on what sphere you're working with, or in my position, I get to touch everything. I tend to gravitate towards the more creative teams of gaming and software development and stuff. I do work with banks. I do work with, well, corporate America, the classic suit and tie kind of places, everything. I see everything. There is absolutely out right now a battle of old versus new, old ways of working, new ways of working. There's a huge clash happening. I to this day do not know who's going to win, because even the big Silicon Valleys, I mean, we are all seeing what's happening with Apple and them putting mandatory office dates and stuff like that. You see that from an executive that is leading maybe one of the more bleeding edge companies in the world, but he's still an old school vibe of creativity.

    I hate bringing it back to Pixar. I'm going to bring it back to Pixar. They have such a great office. So like I said, I'm very fascinated about what they do. They call it unplanned creativity. They truly believe that unplanned creativity happens in the office, and when you have unplanned meetings, unplanned interactions. So one of the things that they did, it's now very common, but when I was 14 years old and I was reading about them, I was like, "Oh my God, these are such cool things to do," they were doing those ping-pong places and activities and games to get people to play together and start talking about what they were doing.

    And then all of a sudden you got an engineer talking to a VFX artist that's talking to a 3D or conceptual artist, that's like they would never meet in a meeting or anything like that. But because they're playing ping-pong and throwing ideas around and all of a sudden they're like, "Hey, maybe we could build this thing. That'd be amazing." Because the artist saying, "Well, now I could do clouds this way. Yeah. Nuts, I could create clouds that look like this." Then the engineer goes, "Well, you can just tweak a little bit of things."

    Anyways, so I think there's this old school mentality at this. It's a question I've asked myself in our Slacks and where we talk about work. I don't know what the future is for unplanned creativity. I don't know how you recreate that in a virtual world. I think it's a big problem that some software companies have tackled with some tools. I don't know how you force someone to sit behind a computer and do something that's unplanned. How do I stumble across some... I don't know. But yeah, I think there's a bit of that in the old school mentality. I need people in an office so that they can meet and they can interact together. I still struggle to find where they're wrong, let's put it that way. I don't know where they're wrong about that theory of when you're with someone, when you're with people things happen in a different way.

    Dave Elkan:

    I can't agree more. I think that if I have any perspective on this, it's that there is not... Often, it's not a black and white or a zero sum kind of game. It's a combination of things that will occur and that will move forward for better or for worse. You can look back in history to Bell Labs and the creation of the semiconductor and the way that the building was designed essentially to allow people to walk past and have cross-collaboration and cross-functional conversations. Have you ever considered that the unplanned creativity that Pixar was talking about was actually planned-unplanned creativity, so they made these spaces on purpose? How can we make things on purpose to have things unknown to us happen?

    Jean-Philippe Comeau:

    Yeah. Yeah. Actually, you're absolutely right. I mean, yeah, they built the Pixar offices this way because of that. To me, that is the secret. If someone finds it, it's like the caramel milk or whatever, just bottle it up and sell it to people, I guess. I don't know. I have no idea what the answer is. I've looked and it's... There's an app out there. I can't remember the name of the app, but you're like a 2D sprite and it looks like an NES game and you're moving around from places to places. You can decorate your office. It's got this vibe of Animal Crossing, which is a game by Nintendo where you can just create stuff and people can visit your island and all that.

    You can do that with your office space and then you can create a common area where people walking. When you look at it in a video, it's brilliant. Great, I can actually be in the office without being in the office. It has this whole technology of proximity. So if you're having a conversation with someone in an open area, people could walk by and hear what you're saying and join in. Beautiful technology, doesn't work with the humans when you really think about it. Why would I go online to walk around an office to go talk? I'll ping you on Slack, it'll be easier. All right. I don't need to walk through your office. So it's like I don't know what the secret is.

    Yeah, you're right, it is planned in a way. I think we do that. I don't know for you guys at Easy Agile, how you do it. In Adaptavist, we do like to travel with teams. So whenever we do things, even if it's customer work or if we're going for an event or something, we try to make it a point to make it about also us and what we do. So we rarely traveled alone. If I'm going to a customer, we're trying to get two consultants in there, or what I'm trying to say is bring more people. It's a point, I think, Adaptavist is trying to make and I think that's what Simon, our CEO, is trying to make is use these opportunities to be with people. I think it's a beautiful thing, but it's one of the myriad of solutions. I don't know. I really don't know. What do you think? What are your thoughts on this?

    Dave Elkan:

    Oh, I can share how we work at Easy Agile. So here I am today in the office. This is a great place for me to do this recording. We have a room for about 50 people here in the office in Wollongong, south of Sydney. We have about 10 to 15 who usually arrive on a daily basis, and that's great. We don't mind. We love people working from home and working away, which is more convenient and relaxing for them. At the same time, we do have quarterly plan, like planning sessions that we go to. We have Advanced Easy Agile every quarter. We come together in person. We've strategically ensured that we hire in a way so that's possible, so people aren't flying across vast sways of ocean to get to this conversation. In a way, it's planned-unplanned. So we do our planning ahead of time.

    When we come for Advanced Easy Agile, we'll have something that we want to either upskill the team with or whatever, and then we'll have some team bonding where people can choose from a range of different activities they want to do together. And so, for us, it's more about getting together in person because we know that's really valuable to both build an understanding of each other as a team and to build that rapport. It can't be done over Zoom to an extent. So, absolutely, our business runs entirely in a remote-friendly way and we don't rely on people to be in person, in sync in person to move forward. However, we do see there's a great value there. So we try to live in both worlds and we get the benefit from both of them. Yeah. And so, that's one thing that can work. It's not for everybody. If you have a truly distributed global business, it's not exactly easy or affordable to bring everybody together on a quarterly basis.

    Jean-Philippe Comeau:

    Yeah. I think it's beautiful though. So I've been in Adaptavist for close to six... I'm on my sixth year now and we used to be able to do... We didn't do quarterly. We did a yearly thing at the end of the year where everybody would get together. We called it Winter Con for the last two years, which I actually loved the idea, which was very much we could pitch ideas of what we wanted to talk about. It could be about work, could be about customers, could be about last year, whatever you wanted to talk about, could be about yourself, could be about a cool thing you did this year, whatever. We had a voting system, but really pretty much anyone that said any, you could get in.

    You could just walk around and it was literally a conference center. We'd set up some rooms and you could walk in, look at a presentation, literally like Teams or whatever. It was the best experience every time that we did that. I love these because there's value. There's an ROI in having everybody learning and upskilling and breaking down these silos of, "Hey, I never worked with marketing, but here's an hour talk around something we did in marketing. I really want to join," and all these things. That's great. There was also the unplanned ROI, where you were coming out of there with multiple ideas of like, "Oh, I could explore this. We could explore that. I got this meeting set in Jan now that whenever I come back in January, we're going to be talking about this thing that we talked about for cloud migrations." All that was happening at Winter Con.

    Now, we grew exponentially post-COVID, well, during and post. So while COVID was happening and all of a sudden everybody wanted work. And then as companies that were remote, I think a lot of the companies that were remote grew during COVID versus because companies that were local or anything, they slowly diluted down a little bit, let's put it that way. As we grew, we can't support that anymore as a one-time thing where you'd have... We're close to a thousand now. There's a lot of people to move and a lot of conferences, a lot of conference rooms and presentations and stuff that we just can't accommodate. So, I miss it a lot. We've been doing it remotely, but like you said, it's not the same to go on a Zoom call.

    I remember sitting down in these presentations and you're sitting down next to people that someone from Arkansas, someone from Cambridge, and you start talking. Yeah, you're listening to conference, but we all know what happens when you're listening to a presentation. You start talking like, "Yeah, that's an interesting idea. What did you do last weekend?" You start talking. Those are things you can't do on Zoom. You can't really reproduce that on Zoom. It's not going to happen really and I miss that dearly. I don't know what the solution is when you have these kind of global distribution. I mean, I guess you do in a smaller way, maybe all of North America meet up or things like that, but it's just not the same, not the same at all. I think it's beautiful that you guys can still do these because everybody's close by. I think it's really nice.

    Dave Elkan:

    Oh, thanks. Yeah, it's something we're hoping to hold onto as long as we can. We understand that these things don't scale. At one point, we'll have to break it into different events so that people can have, I think, a higher level of involvement in that. If you have too many people at the same time, it can be just a bit read only, the way I see it. It's as if to seek participant.

    Jean-Philippe Comeau:

    That's nice. Yeah. Yeah, I like that. Yeah. Yeah, you're right.

    Dave Elkan:

    So I'd love to just quickly touch back on Atlassian Team '23.

    Jean-Philippe Comeau:

    I'm sorry.

    Dave Elkan:

    You did mention at the beginning... That's all right. We'll get there. There's these new apps, especially in the DevOps tooling space that Atlassian's working on, so Discovery. Can you just talk to me a little bit more about what you see there and why that's coming to fruition now?

    Jean-Philippe Comeau:

    Yeah, I think it's all about cloud. I'll be the first to say that big fan of data center, big fan of on-prem. That's how I learned the Atlassian tool set. So, a little skeptical when cloud came about. As it grew and it got better, it got better, that was great. I think it's now at a mature spot where the Point A program, which is where all of these tools are coming out of, so the product Discovery, Atlas and all that, those are the fruits of cloud. That's because now that we have cloud, they can churn out products and try things and see if they stick or not. I think that's why I think this year is the year where I think the program is mature enough. Migration's ready. I mean, we're one year out of server end-of-life. I think we're finally in a place where we can actually talk about all these opportunities. Most of the people at the conference will be able to get value from it.

    I remember last year where talks were heavily around JSM and all the cool things it would do, but you still had a lot of people on server, still had a lot of people on data center. So it fell a little bit on deaf ears. A lot of people in the crowd were just like, "Yeah, it's not for me." Both keynotes were about that. So anyways, I think this year it's going to be better because of that, because everybody's bought in. I think it's right now because yeah, it's cloud. You can ship easier, faster. You can ship better. You can iterate better. You can get a product ready much, much quicker than if you're on-prem, and I think that's why you're seeing this blow up. I also think they're great ideas. Big fan of Atlas specifically. Big, big fan of Atlas.

    Dave Elkan:

    Yeah. Fantastic. So, how are your customers seeing the migration to cloud? On the larger end, is that something that they're open to? Is that something that they support?

    Jean-Philippe Comeau:

    Everybody is intrigued, I'll start there. Everybody's intrigued. Now, the level of interest depends on the industry and the size. When you have a massive... I'll use banks because to me, banks are kind of like countries. So if you look at a massive bank where you have 30, 40,000 users, usually they have solid infrastructures. They have solid administrators. They have teams that are kind of living off this. It's built its own economy, basically. It runs itself. When you go in there and you try to teach them about cloud and all the great things it'll do, they start asking questions that are very technical and they're very good. There's not really an answer in cloud for yet, and so it gets skittish. Whereas if I go to a 500,000 people organization and they start asking questions about cloud, and usually we have more answers for that. It's just easy, an easier conversation. They don't have the same worries or the same thing troubles on their mind than the admin of 40,000 people. It's just not the same reality that they're seeing.

    So I think for now, and I know Atlassian's making a big push into that enterprise space, I think for now you're going to see that growth. But as long as we don't have full autonomy of where our data is and how accessible that data is, it's going to be a problem, as long as FedRAMP isn't available to all, as long as all these different SOCs and compliances aren't available to all. These are very difficult because you've built an ecosystem around a lot of integrations and Easy Agile being to me, one of those integrations because their third-party app, however you want to look at it. Adaptavist has their own third-party app. So you have script runner and all that. We all have third-party apps. So Atlassian can't be like, "Oh, yeah, I'll make a blanket statement. We can do all these things." It's not really true. I'm like, "Hold up, you got to take into account all these different app partners out there that are doing their things and you can't put us all into one roof."I think they're victims of their success. What still making Atlassian great is the partner ecosystem, apps, solutions, sorry, everything, but it's also what's causing the adoption and the speed to which adoption of cloud is happening. It's making it slower than they would want to. I think that was maybe the misstep a little bit when everything got announced was like, "Oh, you guys do rely on these apps a lot." Yeah. A lot of our customers actually would say that the apps are even more important to them than the core. It's just a thing that you're seeing. So to go back to your question, depends on the complexity of the instance. The bigger the instance, usually the more complex it is. So if I go to over 10,000 users, it's going to be a very long conversation. Very, very long conversation.

    Dave Elkan:

    Yes, it is. It's funny that Atlassian did ship this and say, "Hey." Well, actually, there was a presumption that the apps were covered by SOC 2 or the like as well, and that was a missing... But it was this misunderstanding. But I say as a business owner going through SOC 2, it's a very rewarding and good process to go through. It's hard. We are doing it far earlier than Atlassian did in their own journey, but the sooner you do it, the easier it is. Ideally that as a smaller company, you have less things to worry about and the processes you put in place will be easier to maintain and monitor. So we're excited to really go down the SOC 2 path and to provide that peace of mind to our enterprise customers. So yeah, very good process to go through.

    Jean-Philippe Comeau:

    Yeah, you guys are going through it right now. Have you acquired it yet? Did you get your compliance yet or you're on your way to getting that?

    Dave Elkan:

    No, we're on the way to SOC 2 type 1 at the moment.

    Jean-Philippe Comeau:

    Wow. Nice.

    Dave Elkan:

    Yeah.

    Jean-Philippe Comeau:

    Yeah. Yeah. We got security group now in and they're handling all that. I'm not good with the compliances. I'll say it right now, right off the bat, I don't know them very well. I know they're like letters I would like to see next to every apps. That's what I know. I don't know how in depth the processes, but I know it's very involved to the point where you need to have a team dedicated to making that happen. So what have you guys seen so far? It's coming along great. What are some of the challenges that you've seen maybe? I'm just intrigued.

    Dave Elkan:

    Yeah. Oh, look, so our cloud apps are all architected in the same way, so they all use the same code base to an extent, like the deployment methodology. We haven't done any acquisitions which have bolted on to make that more complicated, so we're making the most of that situation. We've done a fair bit of work over the last quarter or so to put in all the checks and the controls around that deployment. The next thing is to really put in place the processes to ensure that our team understands how to deal with different situations and the like. So, that's something we're going to tackle in the next quarter. I'm excited to go through that and do a bit of a sprint with Nick, my co-founder and co-CEO, to really see how much we can get done in a period of time and really focus on that. I think that the benefit will be that we have a much more understood and clear way of running our business, which is obvious to our customers as well, which is a very good thing. I'm all in favor of it. Yeah.

    Jean-Philippe Comeau:

    Yeah, that's awesome. Yeah, I think we're seeing some of the similar things, but we did acquire a bunch of stuff and so that is making everything a bit more difficult, for sure.

    Dave Elkan:

    I can understand. That would be very tricky to try and bridge those gaps and to homogenize enough to be able to have a really clear statement going forward. Yeah. Okay. So we touched quickly on the Atlassian apps that they're bringing. Are there any apps in the marketplace that you have got an eye on that you'd love to go and talk to, of course, Easy Agile aside?

    Jean-Philippe Comeau:

    I mean, of course. Yeah. A big need that I'm noticing now in the market... I don't know if it's a secret or something, I should wait because I know Team '23, they're going to be doing some stuff and I'm really excited for them. So one of the things that we're noticing is... So backups, so enterprise support, basically. Right now, when you're on the cloud, most companies, again, in the 40,000 and plus have strong backup needs and they actually have requirements, laws, things that they need to abide by as far as how long they maintain data, how long they have backups of data and all that. Right now, the way that it's done in cloud isn't nice at all. You actually have to go into the UI. You get a backup. If your backup is large, it's going to take multiple days to process and you got to remember to... It's all manual. There's nothing that really automated.

    So, there is a growing market for these kinds of apps. I've been talking all that to these people at Revyz, R-E-V-Y-Z. What they do is they basically automate that process for you and they host your data. Right now, they only do it for a year, but it's still much better than what we're seeing out there. There's a lot of need for services like that, where they... Because I mean, part of the appeal of cloud is obviously hands off, don't have to worry about things anymore and Atlassian only guarantees backups for 21 days. So if you're an enterprise and you're looking for six months at least of data recovery, at least you're not going to get that. So by having a partner like Revyz or all these, there are other apps out there, I'm talking about Revyz specifically because I talk to them a bunch, but a lot of interesting things are happening.

    Also, what's amazing about these apps, what these developers have found, and once they've have that process, they now get access to the structure of the data and they've started building tools around that structure. So for instance, that app can actually restore projects and issues and custom fields and configurations. So you don't need to do a full restore. You can actually pick what you want to restore, which is brilliant. It's something that even in data center wasn't easy to do. You couldn't just say like, "Hey, give me that issue." You'd have to restore the snapshot, go into the system, find your stuff. Now being able to go into my UI and Jira, go into my backup app, go and look the issued I deleted by mistake, find it, restore it the same day, it has comments saying, "This was restored by revisits, so make sure blah, blah, blah, yada, yada, yada." It's just brilliant and I'm really excited to see that grow this year.

    Dave Elkan:

    That's amazing. Yeah, it's a really intriguing part of this piece that I've never really thought through that that's actually a really important part of running an enterprise, that you have those continuous backups. Yeah. Cool. Yeah, that's a great insight.

    Jean-Philippe Comeau:

    Yeah, it's going to be an interesting market to dive into because we've been asked, even as a service partner, "Can you deliver on this?" The truth is without an app, you can't. There's no real way for me to get a backup. I'd have to go into your instance every day. I don't think you want a consultant going into every day your instance, downloading a backup and throwing it. I'd rather spend my money elsewhere. So these apps are going to be very... I think they're going to be big and I'm really interested to see what happens with all these different ventures.

    Dave Elkan:

    Well, certainly, a booth I'll be popping by to see if we can include the Easy Agile data in that backup as well.

    Jean-Philippe Comeau:

    Yes, exactly. So they are looking at other app partners and seeing what they can do. So I think, yeah, absolutely, if you want to have a chat, they're great people.

    Dave Elkan:

    Beautiful. Thank you so much for your time today, JP. That's a wrap. Hey, is there anything else you wanted to touch on before we wrap up? Is there anything you are hoping to get away from the event, to take away from the event? Anything on the sidelines you're going to see when you're there?

    Jean-Philippe Comeau:

    I mean, obviously, App Day is going to be a big thing. Really excited to meet y'all in person, see everybody. So App Day is the time where I get really technical, get my hands dirty. I don't do that a lot these days. I miss it sometimes just sitting down and doing some good old admin work. So anyway, the App Days are usually when I really get back to the nitty-gritty of let's talk about script runner, where we're at now, and let's meet with Easy Agile, with Temple, with all these different app vendors and talk about what's coming up and what they're seeing. So really looking forward to that. But other than that, no, just looking to have a good time. I'll hopefully get some good social time as well at the evening. Like I said, we won't get ourselves half the fun is also after the events every day, so really looking forward to that, for sure, and meeting all my fellow ecosystem partners and talking to everybody and seeing what they've seen in the past year.

    Dave Elkan:

    Likewise. I'm at least 1,000% more excited now having talked to you about it. So thank you so much for taking the time today, JP, to talk through that and I can't wait to see you there.

    Jean-Philippe Comeau:

    Yeah, I can't wait to see you. Thanks for having me.

    Dave Elkan:

    No probs. Thanks, mate.