No items found.

Easy Agile Podcast Ep.33 How to Align Teams Through Strategic Goal Setting

Listen on
Subscribe to our newsletter

In this episode, we dive deep into the challenges of aligning teams with strategic goals across organisations of all sizes. From fast-growing startups to large enterprises, teams everywhere struggle with the same fundamental issue: translating high-level objectives into actionable work that drives real value.

Our guest Andreas Wengenmayer, Practice Lead for Enterprise Strategy and Planning at catworkx (the #2 Atlassian partner worldwide and #1 in EMEA), shares his 11 years of experience helping organisations bridge the gap between strategic vision and team execution.

Want to see these concepts in action? Andreas and Hayley hosted an interactive webinar where they demonstrated practical techniques for strategic goal alignment using Easy Agile Programs. Watch the recording here→

About Our Guest

Andreas Wengenmayer is the Practice Lead for Enterprise Strategy and Planning at catworkx, one of the leading Atlassian Platinum Solution Partners globally and the #1 in EMEA. With over a decade of hands-on experience helping enterprise teams scale agile effectively, Andreas specialises in bridging the gap between strategy and execution. His work focuses on guiding organisations through complex transformation programs, optimising portfolio planning practices, and helping teams adopt frameworks like SAFe with clarity and purpose. Known for blending pragmatic insight with systems thinking, Andreas brings stories from the field - ranging from fast-moving startups to complex, multinational enterprises.

Transcript

Note: This transcript has been lightly edited for clarity, readability, and flow while preserving the authentic conversation and insights shared.

Recognising the signs - when teams aren't aligned

Hayley Rodd: Awesome to have you here. So I'm going to start with a bit of a reality check. We've worked in organisations across the spectrum from really fast-growing startups to really big enterprises. From your experience, when you walk into a PI planning or quarterly planning session, and I'm sure they're pretty hectic, what are the telltale signs that teams aren't truly aligned on what success looks like?

Andreas Wengenmayer: That's a great question - one I hear frequently. You can imagine, especially post-COVID when teams returned to in-person planning sessions. Back in 2017, we'd have huge arenas with hundreds of people in one place. People are happy to see each other, excited to chat with colleagues from different locations. This became even more pronounced after COVID, when everyone was working from home more frequently. That's a good sign - the mood is positive.

But you also notice some teams under pressure. They'd rather be working on actual deliverables. They know they have to be there, and it takes two full days to complete all the planning. Meanwhile, they're carrying a mental backlog - technical debt, unfinished work from the previous PI, catching up on delayed items.

This is what I often observe: teams get bogged down discussing minor details. People debate specifics, and you can see they're frustrated about something deeper - but they're not addressing the root cause. This creates its own negative momentum and can derail otherwise solid planning sessions.

Teams get bogged down discussing minor details. People debate specifics, and you can see they're frustrated about something deeper - but they're not addressing the root cause. This creates its own negative momentum and can derail otherwise solid planning sessions.

Sometimes you have to step in and ask what's really underneath. What's the actual cause? People say, "Yeah, I have to be here because that's the format, but I'm not engaged." Maybe it didn't work well in the past and there's lingering skepticism.

The prevailing attitude then becomes: "This isn't really collaborative. Leadership plans from the top anyway. The outcomes are predetermined - here's the plan, just make it work and update your boards." When people feel they can't meaningfully contribute or influence direction, they simply go through the motions.

My favourite example happens at the end when teams must formulate their objectives. It becomes a box-checking exercise - create something that satisfies the coach or Release Train Engineer so everyone can "get back to real work."

What good alignment actually looks like

Hayley Rodd: You've touched on so many things there. I can imagine walking into that room and feeling the pressure. People getting caught up in minor details rather than talking about root causes, or not asking the five whys to get to that root cause. You also touched on getting buy-in across the organisation. When people are really nailing it, when alignment is really there, what does that room feel like?

Andreas Wengenmayer: Yes, I've fortunately experienced those environments, and they're actually more common than you might think. When companies genuinely commit to grassroots planning, truly investing the time it requires, and ensure teams aren't overwhelmed from the start with everything marked "priority zero," you create the foundation for successful planning.

When companies genuinely commit to grassroots planning, truly investing the time it requires, and ensure teams aren't overwhelmed from the start with everything marked "priority zero," you create the foundation for successful planning.

You can see it immediately in people's body language and interactions. The energy in the room is palpable. If people appear resigned or intimidated, afraid to speak up, that's typically a red flag. The opposite creates magic.

Think about high-performing teams, like being a Scrum Master with an exceptional group. The best teams aren't just collections of highly skilled individuals in specific roles.

The best teams are those who communicate openly, genuinely enjoy each other's company, maintain positive energy, and actively support one another. This dynamic enables remarkable achievements. Maybe someone knows a contact in another tribe, release train, or department who can provide crucial answers and facilitate communication. Communication is absolutely fundamental.

That collaborative spirit is the hallmark of truly effective teams.

Hayley Rodd: Absolutely. We would know it in our day-to-day work, right? If your teams aren't communicating, if they're too overburdened as you said, it's not a good place to start. But if you can get that starting point right, if you can get that communication right, so many things will flow after that.

Andreas Wengenmayer: Absolutely. Looking back at any planning cycle, the real test is: did you plan the right things? You only know at the quarter's end whether you estimated capacity accurately.

Here's the crucial question: How does your organisation respond when goals aren't met? Do stakeholders focus on finding solutions? Do team members feel safe asking probing questions and seeking answers? Or does the blame game begin, searching for scapegoats?

How does your organisation respond when goals aren't met? Do stakeholders focus on finding solutions? Do team members feel safe asking probing questions and seeking answers? Or does the blame game begin, searching for scapegoats?

When you're permitted, encouraged, even, to be genuinely open and honest, you become much better at assessing realistic capacity. What makes stakeholders universally happy is predictability. You want confidence that your plans will actually materialise, that your commitments will be fulfilled.

Success breeds success, creating a positive foundation for the next PI. It's a continuous cycle that can spiral upward toward excellence or downward toward dysfunction.

The startup vs. enterprise spectrum

Hayley Rodd: Let's talk about the two ends of the spectrum. You've got a lot of experience, so I love hearing about this. Small companies will often say, "We're agile, we can pivot quickly, we don't need formal goal setting." Then enterprises are going all out on OKRs, cascading objectives, saying they're aligned because they've got those things in place. Yet both struggle with the same core problem. What's really going on?

Andreas Wengenmayer: You're absolutely right. I've been in agile projects since 2014, 11 years now, and I've seen a lot of companies pre-COVID, post-COVID, different sizes.

Starting with the really small ones, startup companies - what's really astonishing is that some very small startup companies tend to become overly complex, which is amazing. Some want solutions that are way too overblown. Basically, they need a sailing boat, but they're thinking about ordering an aircraft carrier.

Some startups want solutions that are way too overblown. Basically, they need a sailing boat, but they're thinking about ordering an aircraft carrier.

Maybe that's part of startup CEO culture - where everyone's a CEO on LinkedIn, and they think, "We're corporate, we have to be like that." They mostly get to their senses in the end, but small companies tend to be overly complex and overblown when it comes to technology, tooling, and organisation.

On the other end, large corporations sometimes seem to try their best to become truly agile - living the values everywhere. Still, it's a challenge. In most cases, there's some kind of hybrid planning going on. There's still a roadmap, which is good, but at some level, some people still stick to classical approaches, have some waterfall going on in the back.

I personally have never seen, for example, a full SAFe organisation where it's done truly at every level. There's a good balance and it should be healthy, but it all comes down to execution.

I feel like mid-sized companies are often the healthiest when it comes to that.

There's a balance of method and tooling, but you still need a solid understanding of goal setting and tracking. This includes pivoting when goals aren't right and learning from how you did things in the past. The gap between management and teams isn't that huge, and it's easier to bridge.

Avoiding death by KPI

Hayley Rodd: You've touched on so many fundamental things around getting the method and tooling right, but also that cultural aspect. I love the insight around mid-size organisations often striking that balance well. When we're thinking about the enterprise risk - which could be "death by KPI" or OKR, do you agree? Can you paint a picture of what that looks like and how it actually makes teams less focused?

Andreas Wengenmayer: Absolutely. There is such a thing as "death by KPI." KPIs are important to get a clear picture - you do need metrics, and there's merit to it. But as always, it's about choosing the right KPIs, the right metrics.

My favourite example is comparing story points across teams or ARTs. You measure velocity, and I have to repeat again and again: it's only individual to one team. You shouldn't compare it to another team or across tribes or ARTs - that doesn't work because you're creating the wrong incentives.

You see what will happen: "Well, okay, my stakeholders want higher amounts of story points. Let's estimate the stories bigger." Of course, that's a continuous loop, but it doesn't give you anything. Story points as a metric are just guidance for a team to get a better feeling for estimations.

You see what will happen: "Well, okay, my stakeholders want higher amounts of story points. Let's estimate the stories bigger." Of course, that's a continuous loop, but it doesn't give you anything. Story points as a metric are just guidance for a team to get a better feeling for estimations.

You want predictability - you want to meet a certain range. So it's not a great KPI when it comes to monitoring progress across teams. They have better KPIs in place.

Other metrics tend to create what I call bureaucracy. If you spend too much time creating reports, you have less time to create anything of value.

Hayley Rodd: I think there's so much in what you're saying about people being realistic and honest, open to pivoting or changing a goal if it's not the right one. Admitting to that is really difficult because no one wants to admit that what they set out to do is failing. But understanding that failure can sometimes be a benefit - you can learn from that. There's so much in that cultural aspect, right?

Andreas Wengenmayer: Absolutely. Coming back to goals rather than KPIs - KPIs are like being on a boat in your control room. You see what the engine is doing, the temperature - those are KPIs. Goals, on the other hand, are the course that you set.

KPIs are like being on a boat in your control room. You see what the engine is doing, the temperature - those are KPIs. Goals, on the other hand, are the course that you set.

You could be a small company like a startup - you're in a canoe, you're rowing. Or you're a large company - you're like a big freighter. Still, if you don't set the right course, the right goal, you will never reach your destination. Your team can be as proficient and perfectly working as they could be. If the course isn't right, hopefully you have enough provisions on board to survive a long journey.

Where organisations get stuck in goal setting

Hayley Rodd: Where do organisations typically get stuck? Is it defining the goals, communicating the goals, or translating them into action - that execution point you made before?

Andreas Wengenmayer: It could be basically any one of those. If you have a smaller or mid-size company, it's easier to communicate - you don't have to bridge as huge a gap. But still, you have high-level goals that have to be translated into real work. Real value is created in the teams.

If you have a high-level goal that's highly abstract and sounds good on paper - "increase customer satisfaction," "create better products," "make the world a better place" - people still have to understand: What does that mean to my daily work? If I'm a developer, what's my stake in that? How can I contribute?

If you have a high-level goal that's highly abstract and sounds good on paper - "increase customer satisfaction," "create better products," "make the world a better place" - people still have to understand: What does that mean to my daily work? If I'm a developer, what's my stake in that? How can I contribute?

That's when communication and breaking down goals becomes really important. Breaking them down the right way, having them visible and transparent, and creating that feeling of contribution. You make it visible that you're not just working for yourself or your team, but you're really contributing. You understand what you're working on and why you're doing it. Purpose is critical.

Bridging the strategy-to-sprint gap

Hayley Rodd: That's a really good segue into the next question about translating strategic vision into team-level objectives that people can grab onto and execute. Leadership will often say something like "increase customer satisfaction," and teams are left going, "What does that mean for me in my sprint this week?" How does an organisation bridge that gap between the high-level leadership view and what we can do in our sprints as a team?

Andreas Wengenmayer: First of all, you as company management need to take the time. There have been, and still are, a lot of approaches with company values, putting posters on walls, creating marketing. Those are all values - that's what a company is like. Then you link it with your products, services - great services, customer satisfaction. Okay. Then comes the real challenge: we want to succeed and create the next service, software solution, or product.

The goal is clear on a high level, but how do we break it down? That's when the real work comes into play - breaking down the goals into smaller pieces.

It's like building a LEGO space station when I was a kid. You have the picture on the box in the beginning - 'Oh, that's what we're going to build.' Then you have to start putting together all the small pieces. You need a plan, you need the little pictures of the steps. You start with the big picture, then you're breaking it down one piece at a time. You create different parts, and they come together at the end. Same goes for goals.

It's like building a LEGO space station. You have the picture on the box in the beginning - 'Oh, that's what we're going to build.' Then you have to start putting together all the small pieces. You need a plan, you need the little pictures of the steps. You start with the big picture, then you're breaking it down one piece at a time. You create different parts, and they come together at the end. Same goes for goals.

Hayley Rodd: Nice. A colleague of mine often says you eat an elephant one bite at a time - similar thing, right? When you see that big goal, it's really overwhelming. But if you can break it down into those chunks and smaller pieces, it becomes so much more manageable and achievable. People can get behind that vision.

Managing moving targets

Hayley Rodd: In fast-moving environments, goals often shift. We're agile, we're always moving. How do you help teams stay connected to a moving target without either ignoring changes or constantly thrashing around?

Andreas Wengenmayer: Back in the nineties and early 2000s, there was a computer game that wasted a lot of time in offices where you were shooting at geese in Scottish Highlands. It was a big phenomenon because people were trying to get the next high score.

If you think of moving targets, it's a bit like that. Imagine you're doing your work - whether you're a hunter or developer doesn't matter - but you approach, you take aim, and the geese keep flying up. You miss the target. Same thing if you have moving goals.

It's harder to aim and approach them right. What you should avoid as a company or someone in charge is constant interference. Stick to your goals or objectives that were agreed upon during PI planning. Don't change them midterm during a PI.

What you should avoid as a company or someone in charge is constant interference. Stick to your goals or objectives that were agreed upon during PI planning. Don't change them midterm during a PI.

That doesn't mean you can't learn from mistakes or wrong goals. You can adjust them, but you have to adjust them in the right place and time, which is during planning. Of course, if something security-related comes up, you have to act, but it has to be agreed upon, and you still have to communicate it and create understanding.

Keeping goals visible and actionable

Hayley Rodd: Even when goals are well-defined, keeping them visible and actionable throughout a PI is tough. What practices or tools have you found most effective for maintaining connection between daily work and high-level strategic objectives?

Andreas Wengenmayer: Good question. Having the goals present at all times helps a lot. If you just meet for planning, have your goals set, and never look back during the PI, it doesn't do you any good.

That could be a piece of paper on the wall like we had back in the day - and still could be if you're working in the office. Also, choose the right tools to track the goals and create acceptance for tools. Really use them. Look into them - whether it's an OKR tool or some other solution, even PI objectives. Are we still on track?

What really helps is if it's not static but shows progress, and especially shows the link of what you're contributing - like what you achieved in your last sprint and how it plays into the objectives or goals, progress moving ahead. There's always a good feeling - everybody loves a green bar moving ahead or a checklist.

What really helps is if your tool is not static but shows progress, and especially shows the link of what you're contributing - like what you achieved in your last sprint and how it plays into the objectives or goals, progress moving ahead. There's always a good feeling - everybody loves a green bar moving ahead or a checklist.

It helps keep the vision and goals present.

Hayley Rodd: When I was a teenager in my final year of high school here in Australia, I wanted a specific score on my final exams. I had a big poster in front of my desk that I sat at for hours every day studying. Looking back, I didn't know what I was doing - I just wanted to visualise my goal, and I didn't know the psychology behind it. But I'm happy to report I got that mark and above.

I think it was as you were saying - that constant reminder, that piece of paper worked for me. In organisations, we're looking for something a bit more complex sometimes, but I like your "keep it simple" advice. It doesn't always have to be super complex. It can just be a checklist, progress bar, or piece of paper - something that helps you feel connected to the goal and reminds you of it often.

When good work doesn't align with goals

Hayley Rodd: Have you seen situations where teams were delivering lots of work - good work, but it wasn't clearly contributing to company goals? What tends to cause that disconnect?

Andreas Wengenmayer: Yeah, that happens quite a bit. I can think of one example with very technical teams, like in semiconductors. Very smart people - everyone has a PhD in physics, material science. Awesome, smart people who tend to love their job. They're awesome, but they're also perfectionists who can still improve things and want to make them even better.

If you're in the business of producing machines used to produce semiconductors, for example, it's a complex task with a complex supply chain or value chain. You're creating lithography machines to create wafers used by other companies, and in the end, you have a customer planning the release of a new phone.

Your customer waits, the end customer waits, and you have to deliver on time. Sometimes this creates a challenge because teams still want to improve and make it even better. That's when economics come into play - the view of the big picture. You still have to communicate it. You shouldn't discourage such a great team, but you need to get the bigger perspective back to the teams and create acceptance instead of saying, "Hey, stop what you're doing, it's good enough." You don't want that. It all comes back to transparency and communication.

On the other spectrum, what you sometimes have is just too much workload on teams. Time for planning gets cut short, and if you don't take enough time to plan well, no wonder the results don't work out. It's just a lot of busy work - a lot of things getting done, but not necessarily the right things at the right time.

On the other spectrum, what you sometimes have is just too much workload on teams. Time for planning gets cut short, and if you don't take enough time to plan well, no wonder the results don't work out. It's just a lot of busy work - a lot of things getting done, but not necessarily the right things at the right time.

Hayley Rodd: If you don't do that planning at the start, you're setting yourself up for misalignments. If you're not communicating that plan regularly, you're setting yourself up for that busy work and people getting distracted. It's just so common. That planning part is so fundamental to getting it right.

One piece of advice for frustrated leaders

Hayley Rodd: We're on the home stretch now. If you could give one piece of advice to an engineering or product leader who's been frustrated because their teams seem to be going through the motions of PI planning or quarterly planning without real buy-in, what would it be?

Andreas Wengenmayer: I can resonate with that so well, and many can. I'd say: take the time to find out what's really going on. Investigate the root cause. It's like if you have a house and you're trying to fix a crack in the wall - you can look at the crack and do some superficial fixing or use a thick layer of paint, but you still have to find out what's causing that issue. Maybe something deeper.

You mentioned the five whys - that can be one way, but you have to have some understanding of the right way to approach people. You don't want to put anyone on the spot. Looking for a scapegoat doesn't help anybody.

We need to look at what's behind it, what's causing it. It all comes back to investing enough time for planning, but doing it with purpose. Not doing the whole planning like theatre, where everybody acts their part - that doesn't do you any good.

It all comes back to investing enough time for planning, but doing it with purpose. Not doing the whole planning like theatre, where everybody acts their part - that doesn't do you any good.

People have to understand why they're doing it. There has to be purpose and understanding - enough time, no distractions, and a positive atmosphere where everybody can contribute and be open.

You don't want people saying nothing because they don't dare to criticise or say no.

The connection between goal clarity and team motivation

Hayley Rodd: What's one thing you wish more organisations understood about the connection between goal clarity and team motivation?

Andreas Wengenmayer: We could get back to the boats we mentioned before. You want to arrive at your destination. If you're not clear about the destination, or maybe some people in your rowing boat don't want to go there, they might not join the rowing. If your crew is not invested, it will take you longer to reach a destination, or you won't get there as well.

It's the same thing. Motivation is key, and I don't talk about superficial motivation that just annoys everybody. Motivation is a positive environment where people rely on each other. They really like spending time with those people.

"Hey, I really like to go to lunch with you and talk to you" - not "I'd rather be home and not talk to anybody." You're not annoyed if your teammate asks you a question; you're happy to help. You're feeling safe that when you have a problem or question, you will get help.

That creates the right kind of motivation - that positive environment, and that can make a lot of things happen. It comes back to openness and transparency, not as buzzwords, but to get the clear picture. As a stakeholder, you get the correct current state because you get true answers.

I've seen strange situations in major corporations where people really didn't report what they were working on or show the right results. I've seen complete shadow Jira environments - one for internal use and one for external use with customers. There can be huge misalignments because people didn't dare to show real progress. In the long term, it will backfire. If you don't have trust in your environment, in your company, you will have a hard time.

I've seen strange situations in major corporations where people really didn't report what they were working on or show the right results. I've seen complete shadow Jira environments - one for internal use and one for external use with customers. There can be huge misalignments because people didn't dare to show real progress. In the long term, it will backfire. If you don't have trust in your environment, in your company, you will have a hard time.

Wrapping up

Hayley Rodd: There are so many key themes coming up throughout our conversation. You've talked about ongoing communication across teams, really planning with purpose, getting that context and buy-in to help with motivation, and allowing for radical candour - being really open if something's not working and being okay to call it out. So many cultural and communication elements are critical to the success of quarterly planning, PI planning, and organisations generally. Great takeaways.

We're going to end it there, but I want to end with a teaser for our interactive webinar that you and I are doing together on September 4th, which dives deeper and shows how to operationalise the ideas we've chatted about here using Easy Agile Programs and linking back to the fundamental services that catworkx provides organisations.

Andreas, it's been super wonderful to chat with you. I look forward to our webinar coming up on September 4th.

Andreas Wengenmayer: Thank you so much for having me. Looking forward to September 4th and seeing you again, talking more about tooling, boats, duck hunt, and anything in between.

Ready to transform your strategic planning?

The conversation doesn't end here. Andreas and Hayley hosted an interactive webinar where they showed how you can put these strategic alignment concepts into practice.

They spoke about:

  • Practical techniques for breaking down strategic goals into actionable team objectives
  • How to maintain goal visibility throughout your PI cycles
  • Real-world examples of successful alignment transformations

Watch the webinar recording here →

Related Episodes

  • Podcast

    Easy Agile Podcast Ep.15 The Role of Business in Supporting Sustainability Initiatives with TietoEVRY

    Rebecca Griffith

    "It was amazing to talk with Ida and Ulrika from TietoEVRY, they are truly leading the way in sustainability" - Rebecca Griffith

    Rebecca and Caitlin are talking with Ida and Ulrika from TietoEVRY, about big picture sustainability and the role of business in supporting sustainability initiatives.

    🌍 Implementing sustainability in daily business operations
    🌍 The role of technology in advancing sustainability
    🌍 Ensuring your sustainability & DEI report doesn't turn into a stagnant document
    🌍 Framing challenge in a way of opportunity
    🌍 Getting the whole team on board

    An important listen for everyone, enjoy!

    📲 Subscribe/Listen on your favourite podcasting app.

    Transcript

    Caitlin Mackie:

    Hi, everyone. Welcome to the Easy Agile Podcast. I'm Caitlin, marketing coordinator at Easy Agile.

    Rebecca Griffith:

    And I'm Beck, team and operations assistant at Easy Agile, and we'll be your host for this episode. Before we begin, we'd like to acknowledge the traditional custodians of the land from which we broadcast today, the worthy, worthy people of the Tharawal nation and pay our respects to elders past, present and emerging. We extend that same respect to all aboriginal and Torres Strait Islanders people joining us today.

    Caitlin Mackie:

    Today, we're joined by Ida and Ulrika from TietoEVRY. Welcome. Thanks for joining us.

    Ida Bohman Steenberg:

    Thank you so much for having us.

    Ulrika Lagerqvist Von Unge:

    Thank you.

    Rebecca Griffith:

    It would be great if we could start with some introductions. Ida and Ulrika, could you tell our listeners a bit about yourselves and your role at TietoEVRY?

    Ida Bohman Steenberg:

    Yes, of course. I'm Ida and I'm heading up the sustainability team at TietoEVRY since four years back. And Ulrika?

    Ulrika Lagerqvist Von Unge:

    Yeah. I work within the sustainability team as a sustainability manager also here at TietoEVRY.

    Rebecca Griffith:

    Excellent. Thank you. Thanks for the introductions. Let's jump in. For our listeners who might not be familiar with TietoEVRY, can you give us a bit of an overview about what the company does?

    Ida Bohman Steenberg:

    Yes. Sure. We are a company based in the Nordics, like very, very far away from sunny Australia. We are a tech company. We provide different solutions. For instance, in software, cloud and infra and also business consulting. I think nowadays, we are the biggest tech provider in the Nordic, at least.

    Caitlin Mackie:

    Sustainability is a huge part of TietoEVRY. You really have a robust sustainability game plan and your strategy for 2023, which highlights your key priorities for ethical conduct, climate actions and creating an exciting place to work for your employees. Can you elaborate on the sustainability game plan for 2023?

    Ida Bohman Steenberg:

    Yeah, we would love to. The sustainability game plan is our long term plan that we created last year. We were actually two companies merging into one last year. We had different legacies. X Tieto were good at some things and X EVRY were good at some things, but of course, we had lots of challenges too. We had to sit down and really try to find out what should be our focus going forward and not only actually to build upon what we already have, but also look at the major challenges out there to see like, where do we want to be and what role do we want to have? We created a game plan that is two-folded. We have like the responsible operations that is the traditional sustainability work that you would find at any organization that takes sustainability seriously.

    We have the ethical conduct where we have business, ethics, and the corruption, cyber security, privacy, human rights, responsible sourcing, for instance. Then, we have exciting place to work, which is more like HR related because we're people companies, we have to be very good at this in order to attract the right talent and also to keep the talent that we have. We have major challenges when it comes to bringing in and keeping women in our sector, for instance, so we have to be very good at diversity and inclusion and also employee experience, of course, to make this a fun place to work at. Then, of course, climate action may be the one thing that people think about most when they think about sustainability due to the emerging climate crisis. We work a lot with that, of course, and also circular economy and our take on that.

    That is like the foundation for us that we have to be very good at like our license to operate, and we work throughout the value chain with these topics, but then because we are a tech company, we also wanted to see what can we do to not only improve our own sustainability performance, but foremost our customers? What's due, I think, and what really stands out for TietoEVRY now is that we have this really, really strong business focus going forward for this sustainability game plan. I was thinking maybe Ulrika could take over and explain and elaborate a little bit about the upper half of the circle.

    Ulrika Lagerqvist Von Unge:

    Yeah, exactly. What we identified when we were developing this strategy or long term plan was that some of our biggest impacts also actually resides among our customers. We have a lot of capabilities and we have a lot of customers, so why not combine those and see where do we have the biggest opportunity in terms of actually helping our customers to become more sustainable? We developed a methodology where we investigated our capabilities, our customer pain points, our customer opportunities and landed in four broad impact opportunities. That's where we have business opportunities in making our customers sustainable. Those are new focus areas within our sustainability long term plan, where we engage with our own business to drive these areas and develop together with our customers to create positive impact on people, planet and societies.

    Ida Bohman Steenberg:

    I think also if I may add to that, Ulrika, so we set the plan to do that, and we had of course, a lot to build upon. We had lots of good reference cases, but of course, we needed to pin it down to get the buy-in from management. Also, of course, get the resourcing. We started with identifying those areas where we think that other people have, or other customers or stakeholders have impact opportunities, which means a business opportunity for us. We must not forget that, but in order to actually deliver in a good way and at the speed that our customers require, we also had to create a consultancy team that could help in the delivery organization because the customer requirements become... The pressure was so high.

    For our little team group sustainability, we couldn't really handle everything, so we created something that we call the sustainability hit team, which is a consulting team consisting of consultants that knows data and sustainability within business consulting. Ulrika, you have been given also... You have the role of leading this group, perhaps you would like to say something more about that group?

    Ulrika Lagerqvist Von Unge:

    Yeah. Yeah. Sure. Well, this is a group of people that, just as Ida said, they have this kind of expertise, combining sustainability knowledge with IT and technology. We work together to identify both ongoing projects that might be related to sustainability in one way or the other that we perhaps can scale and create synergies, but we also work to identify new opportunities, having our ears towards the ground and listening into what do the customers actually want to have. Then, we take in these opportunities and try to see how we can develop them to actually support our customers. Hopefully, this team will just continue to grow and us with our other efforts, become very integrated in all our business operations. That is at least our aim, so the responsibility lies where the responsibility is sort to say.

    Rebecca Griffith:

    That's wonderful. Now, I think you've kind of touched on this in a broader sense, but in the TietoEVRY annual report, you talk about implementation of sustainability into daily business operations. What are some other key ways that you're doing this?

    Ulrika Lagerqvist Von Unge:

    Yeah. If I can start, Ida?

    Ida Bohman Steenberg:

    Sure.

    Ulrika Lagerqvist Von Unge:

    I think one of the most important things is to involve everyone from the beginning in what we actually should focus on and what are the most important topics in terms of sustainability, both for all our stakeholders, but also for our business, so that we actually give the ownership of sustainability to the organization. Not so that they feel it comes from the side or from above, but it's actually something that is relevant and that the organization owns. That means that each and everyone has the responsibility to also contribute to our joint targets that we also have involved the different business leaders and parts of the organization in setting. I think that ownership is a keyword here to actually enable integration of sustainability in the operations. Ida, do you agree?

    Ida Bohman Steenberg:

    Yeah. No, but the group sustainability, our group, we are a small team consisting of specialists with long experience, but we are only so many, so we have to have a very integrated way of working in order to make this fly. What we've been focusing on a lot since many years back is to get it integrated. For instance, if we look at responsible sourcing, which is crucial how we handle our supply chain. We work closely together with a chief procurement officer. The sustainability goals that we have that are public and that we disclose every year in our annual report is just as much his goals as it is our goals, so we really get some power behind driving it and we get the results that we need in order to move forward. That is one thing. Then, as Ulrika explained earlier in the last question about the sustainability hit team, how we also now have taken this step further to really approach the business in a more structured way that we have done before. As I said, we had very good reference cases and we have a portfolio of sustainability related services, but now we're doing this in a much more structured manner because of the market, the demands that has increased so much.

    Caitlin Mackie:

    Yeah. That's great. I think what you mentioned, having that structure helps with that company buy in and getting everybody on board and realizing that it's everybody's commitment and it's like a journey you're all on together. Yeah. I think that's great. Something that's often talked about is the overlap between business and sustainability and the role of the business in addressing some of the major challenges we face as a society. I think so many look to clearly distinguish their responsibility and draw a line somewhere, but I'm not so sure that's the right approach. TietoEVRY certainly recognizes they have an important role to play and really pave the way towards carbon neutrality. What's your approach to this?

    Ida Bohman Steenberg:

    Okay. First of all, I think there must be an overlap or there must be like, if you are a company like we are, we cannot do things that we don't think also is good for us, like financially long term. That is the beauty of sustainability. If you have good and long term targets, it's also support the growth of the company in financial terms, so we always have both those perspectives in mind, creating strategies going forward. For us, we work both for our own operations when it comes to climate change to decrease our carbon footprint, obviously, so we are changing. We have renewable energy in all our data centers and offices. We are now currently at 80% and approaching 100. It's going to be difficult. The last percent is always the most difficult ones, but we have a good development as for now.Then, of course, we work super hard because this is the, I think number one question that our customers is asking for, ways to manage their own carbon footprints. Here we are strong in data, of course. Do you want to add something around that?

    Caitlin Mackie:

    No, but I think that the first reflection that you had that we have this financial perspective also when developing the sustainability plan, it's important because I think that what we see is that... Our business is doing business. Yes, of course. But if you don't do it right, there will be no business on a dead planet, right? So that you have to have the long term perspective where you take into account all the different aspects. It's not only the financial, because they're also interlinked. I think that also the risks that are connected to, for example, climate change for business operations, so the inbound risks that the surrounding is posing to us are becoming more and more clear. I think that it's also becoming evident that if you don't have sustainability integrated in your operations, you will no longer have a license to operate in 2021 and beyond. I think it's just a smarter way of doing business, to be honest.

    Rebecca Griffith:

    We can all acknowledge that climate action is one of the biggest global challenges for our generation. In recognizing that this is one of your key priorities to address, how do we take these challenges and frame them in a way of opportunity?

    Ida Bohman Steenberg:

    Well, this is the beauty of being a tech company. We have the luxury of not having lots of goods that we need to take care of cotton or food or so, so we can go straight to the point, I think, and start to listen to what our customers need and create services and solutions that support them in their journey to decrease their carbon footprint. It sounds very easy when I say it like this. It's not that easy, of course. It requires a lot of hard work and everything, but that's what we should do. I think that when you look at the crisis that is emerging, the tech industry is also seen by the other industries as the great enablers. I think that we have a key role to play. I think that we have a responsibility to our stakeholders to be there and to be in the forefront.

    I think that's what we've been doing. For instance, for the last year, the guest team has been working on a very interesting solution called the sustainability hub, which actually addresses this spot on. Would you like to...

    Ulrika Lagerqvist Von Unge:

    Yeah. Yeah. Definitely. I totally agree with you, Ida. The tech industry, it's really an enabler and that also means that there's a lot of business opportunities. As you said, the sustainability data hub voice, one of our responses to these kind of business opportunities that we see out there, so what happened was that we were sitting and discussing and realized that one of the biggest obstacles for companies to actually integrate sustainability into decision making, into risk management analysis, et cetera, is the lack of data as you have now produced your own ability report, the big hurdles that comes with actually collecting the data for that report, it sits in shattered data sources.

    The collection is often manual. The data might not be in the right shape. Most companies actually collect the non-financial data once a year for their annual sustainability report. That means that when you have that data, you are actually steering through the rear view mirror because you are not steering proactively by taking fresh data into account when you take your decisions or plan your operations. What we did was that we started to develop a solutions, which builds on automating the data collection of sustainability data by helping customers to identify where does the data sit? How can we actually automate it? Is it via automation, via IoT solution? Who will use the data? Which KPIs and metrics do we want to map it against? How often do we want the data to be updated? Then, visualize it in real time? A modern way of an ERP system for ESG data, you could say, so that it is actually possible to equate non-financial inform and with financial information.

    That should give the opportunity for companies to treat the data in the same manner and actually integrate sustainability into the decisions that they take. For example, let's think about the impact of us going from working at the offices to now working hybrid. What are the actual impacts? Can we see that the sick leave has increased or decreased? How has the carbon emission been impacted by us not traveling back and forth to the offices? If we have that data, we could also use that to decide whether we should continue with hybrid working, or if we should force our employees to come back to the office, or if everybody should be working from home. If you can get hand of that collective view of the activities that you take, you could also make more holistic and informed decisions. That's one response kind of how we try to treat sustainability as a business opportunity and identify which are the pain points that our customers have in terms of co-creating a sustainable future, and where can we tap in into that? That is the kind of beauty, as you said, our industry.

    Ida Bohman Steenberg:

    It is.

    Rebecca Griffith:

    Really interesting looking at it in real time, as you said, as opposed to a retrospective assessment of the data, which really, you can't change.

    Ulrika Lagerqvist Von Unge:

    Exactly. Yeah.

    Ida Bohman Steenberg:

    Yeah.

    Rebecca Griffith:

    What's the point in waiting another 12 months to then look at it again when you have completely done [crosstalk 00:18:32]?

    Ida Bohman Steenberg:

    Yeah. Both sustainability.... Yeah. Sorry. Both sustainability and tech is moving extremely fast. I think we need to work like this. I think customers are going to require... We see more and more before they wanted us to report once a year, but now so many of our customers, they want us to report different types of data related to the solutions or our delivery to them on a quarter basis. The more we can have real time data, I think it's going to be the new normal very soon.

    Ulrika Lagerqvist Von Unge:

    Me too. That will be a huge game changer for companies. When the data is there, you can get it black on white. There is no excuse for taking bad decisions, right?

    Caitlin Mackie:

    Yeah. Yeah.

    Rebecca Griffith:

    Quite exciting.

    Caitlin Mackie:

    Exactly. I don't know about you, Beck, but I'm definitely sitting here being like, "Wow," at all, like this would've been super handy 12 months ago.

    Ulrika Lagerqvist Von Unge:

    Yeah.

    Ida Bohman Steenberg:

    It's out there. Yeah.

    Ulrika Lagerqvist Von Unge:

    Yeah.

    Ida Bohman Steenberg:

    It's on the market, so you're more than welcome.

    Caitlin Mackie:

    All right.

    Ulrika Lagerqvist Von Unge:

    I think that's also typical from sustainability that you have to understand that the solutions to all of these kind of complex problems, they can't be solved by any actor. We need to work in ecosystems and everybody will have to bring their expertise to the table. Then, we can get things to actually be solved. I hope that that logic will also impact other areas so that we more try to cooperate instead of having the cake ourselves, because then there will be no cake left over. That would be sad.

    Caitlin Mackie:

    It's so, so refreshing to hear you say that. I think for so long businesses have always had this idea about, "Oh, competition," and like, "Keep what's yours. Keep it to yourself. We're going to succeed in this area." But moving into this space, it's just not about that anymore. It's about how we can collaborate together to reach those solutions. I think that's so powerful.

    Ida Bohman Steenberg:

    For sure. No. Sustainability is horizontal work. As an organization, as an entity, as a company, we are not stronger than our closest stakeholders anyway. Our performance is very much reliant on their performance.

    Ulrika Lagerqvist Von Unge:

    I think it's so interesting also because since we come from that kind of background, Ida and I also always working across all silos, across all kind of company functions. We also get a special role in our company because we don't have the legacy of working in silos, so we just totally break them all the time because we're not aware of them. That's just what is needed to be able to get the job done. I think that it's really interesting to see how the organization actually appreciates that.

    Ida Bohman Steenberg:

    Yes. Sometimes, they don't.

    Ulrika Lagerqvist Von Unge:

    Sometimes, they don't. Exactly. Sometimes, they don't. Yeah. That's true. Yeah.

    Ida Bohman Steenberg:

    But we have our battles internally. If you're a sustainability professional working in a big organization, you must be very prepared to have those tougher discussions as well, but we all get there, not always on time from our perspective, but that's the way it has to be. Fearless and just...

    Ulrika Lagerqvist Von Unge:

    Stubborn.

    Ida Bohman Steenberg:

    Stubborn, and don't be too bothered about silos or hierarchies or so, because then you will never get anything done.

    Caitlin Mackie:

    I wanted to highlight or expand on the idea of opportunity and the fact that we constantly need to be exploring new and better ways of doing things so that we can move forward. It would be great to get your thoughts on the role of technology in advancing sustainability. I know you've touched on it, but it'd be great to elaborate.

    Ulrika Lagerqvist Von Unge:

    If I start, then you can build on it.

    Ida Bohman Steenberg:

    Sure.

    Ulrika Lagerqvist Von Unge:

    I think that some of the business opportunities or the solutions that we can develop are cross industrial. For example, the need for data and the need to get hold of it and to visualize it and to be able to act on it, is of course, something that all companies in all industries could make use of. But then, I think that for many solution, they are industry specific. For example, logistic. They need certain solutions to be able to optimize their logistic, their rooting, or to better pack their lorries and trains, et cetera. But I think that... There are both this industry specific solution and this cross sectional business opportunities stuff that you have, and also one of the hidden gems within the IT sector is the side effects of digitalizing services or solutions.

    It's also important to understand that even though a solution might not be developed and deployed for the use of mitigating or climate change, for example, the actual impact of its implementation might lead to less carbon emission. Let's think about we have a solution that is called patient engagement. It means that you could engage with your doctors and nurses over your phone, which means that you don't have to take the public transportation or your own car to the hospital or to the medical clinic, which of course saves that transportation and in turn, saves carbon emissions if you travel with something except for an electric car. Many of the digital solutions actually have that positive hand print impact or effect, I would say. Of course, the opportunity of expanding on those is also massive and to identify them, perhaps it's the possibility. If you have a patient engagement app, could you use it for other purposes for other users to increase the impact.

    Rebecca Griffith:

    At Easy Agile, one of our goals was to establish a baseline and publish our very first sustainability and diversity report, which I believe we've shared with you. We'll also share that report as well as the TietoEVRY annual report in the show notes for our listeners. But what advice would you give to organizations to ensure that these kind of documents don't turn into a stagnant document or a mere check of the box exercise? How do we use these reports to encourage conversation and continually seek ways to improve?

    Ida Bohman Steenberg:

    Okay. I get so many thoughts now. First of all, keep up with an upcoming frameworks. Don't get stuck in all the good old GRI for instance. In the European Union, so we are now approaching the taxonomy reporting or TCFD or so on. Go for those new ones. Also, of course, everybody has to do the ground work. You have to do your stakeholder engagement, the dialogues, the materiality analysis in order to know that you focus on the right things and so on, and you have to have really concrete goals and action plans and KPIs and everything, so you can measure your performance against the goals that ultimately what sustainability reporting is about. But then, I think the opportunity with reporting, because reporting can be a little bit boring too, in a sense, and it can feel stagnant in a way. It is that it's such an important tool in the strategy work.

    This is where you get the attention from the leaders like, "What goals are we going to have and how did we do and so on?" That's where you can have the good discussions or you can also raise the ambition level as you go along. That I think is really crucial. Use it as a strategy tool as well, and then never get stuck in like, "Oh, yeah. It's good. We met our targets. We moved 3% forward or whatever." Don't think so much about that. Think about lie what are the major challenges right now? What is your role as an organization? No matter what organization you are, find your way to be part of the solution instead. We have that discussion sometimes internally. People are like, "Oh, but you're doing so good. You have a good results and so on."

    But for me and Ulrika and our sustainability professionals, we're like, "Yeah. Okay. We move forward. That's good." But from a greater perspective where we are reaching the tipping point for the planet, so we feel other pressure in order to move forward faster. Don't end up in like, "Yeah. We move forward. We're keeping the pace." Full on power ahead, and speed is of essence going forward.

    Ulrika Lagerqvist Von Unge:

    Yeah. No, I fully agree. I think that's really good reflections to hook the sustainability reporting up on the challenges to understand. What are the purposes? What are we actually trying to achieve by this report? We are trying to contribute to minimize the negative impact and to increase the positive impact, and the sustainability report is a tool for that. I think another thing that is really important is to actually also engage with the organization to get them define their own targets and their own metrics to report on, so that they feel ownership. For some of the areas that we have in our sustainability report, when we have an engaged partner within the organization that themselves have ideas on targets, we develop their own KPIs.

    They feel that, "I really believe in this. I want to work with this." Then, the follow up and the continuous reporting is much easier than while we have perhaps other parts of the organization where there isn't so much clear targets internally, so that the sustainability report is more felt like something that is done on an annual basis just collecting the data, but not making use of it actually. Just create that commitment and build on the company's own targets and own KPIs that are useful. Then, of course, sometimes if you do report according to a sustainability framework such as the GRI standards, which is commonly used in Europe, then you, of course, need to report according to some of the metrics in that standard, but then add your own key guides, your own metrics, because that will make the organization feel engaged, I could say.

    Ida Bohman Steenberg:

    Yeah. Yeah. Basically to summarize that, so three things, do the groundwork according to the upcoming and fresh frameworks, and then two, use it as a strategic tool to have those important discussions with management and make it a part of the overall strategy, so you don't end up with the sustainability strategy and an overall strategy. Then, three, be bold. Look at the challenges and not only what's doable or keeping the trend or whatever. Those three things, I think is important to have in mind.

    Rebecca Griffith:

    Spot on.

    Caitlin Mackie:

    Yeah. I love that. I think that's great advice, especially the idea of you're mapping out what you're doing internally and what that looks like, but being able to take that step back and say, "Okay. But what does this contribute to in the big picture? What are we actually helping and what are we doing to move in the right direction?" Something that I often think about is things like the UN sustainable development goals and looking at those and being like, "Well, what can we do to of map where we are at and where can we offer? What can we be doing in this space that helps reach those targets?" Yeah. Great advice. I love it. But I think just to wrap us up, our last question for both of you is looking forward, what keeps you hopeful?

    Ida Bohman Steenberg:

    It keeps me hopeful. Well...

    Ulrika Lagerqvist Von Unge:

    For me, I think the younger generation, to be honest. I think that seeing my brothers' daughters that are teenagers, or to see [inaudible 00:31:19] and the commitment that she's able to steer up, I think that gives me hope that things will move faster in the future. I think that's positive.

    Ida Bohman Steenberg:

    Yeah. I also second that. I think I visited the school last week with students like 18, 19 years old, and I've been doing that every year for a couple of years now and I always ask them, "What do you know about sustainable? What do you think about it?" Before, it was like, "Yeah. The environment or recycling maybe," but now they were like, "Yeah. The UN SDGs..." So the level of knowledge has increased so much. There is huge interest and when I gave them, "What can you do on a practical level if you want to live a more sustainable life?" They were like, "Yeah. Don't buy a new party cup for the Friday night. Borrow from your friends, or there are these sites. I can text you these sites where you can borrow dresses and stuff like that." They are doing it in real life in such a good way where they combine technology and sustainability, so they're much more tech savvy than we are. I was very inspired by that.

    Ulrika Lagerqvist Von Unge:

    They're also willing to actually sacrifice stuff. It's like, "No, we don't fly. We don't do this because we would like to have a future to live in." I think that that is something which we are so comfortable and so used to having a certain lifestyle, but they are perhaps not and they are challenging that lifestyle that we have been having, which has also led to where we are today.

    Ida Bohman Steenberg:

    I think also to add to that, I think that finally the leaders of our countries are getting it, at least getting close to getting it. I think things are changing, so that's good, but my hope stands to the young ones still.

    Rebecca Griffith:

    It's nice to feel that it's becoming a normal part of consciousness for the newer generations where it's something that we had to learn to appreciate and respect and to take action on, but it seems to be a part of their upbringing and a way of life now, which is great.

    Caitlin Mackie:

    Well, I think that's great. I think it's great to leave the episode on such a high and leave the audience with a bit of inspiration moving forward. Thank you both for taking the time to chat with us and sharing your expertise with the Easy Agile audience.

    Ida Bohman Steenberg:

    Thank you so much for having us. It was fun to talk to you, and it's nice also to talk about the perspectives from the Nordics and from the tech industry. Thank you very much.

    Rebecca Griffith:

    Thank you.

  • Podcast

    Easy Agile Podcast Ep.21 LIVE from Agile2022!

    "That's a wrap on Agile2022! It was great to be able to catch up with so many of you in the agile community in-person!" - Tenille Hoppo

    This bonus episode was recorded LIVE at Agile2022 in Nashville!

    The Easy Agile team got to speak with so many amazing people in the agile community, reflecting on conference highlights, key learnings, agile ceremonies + more!

    Thanks to everyone who stopped by the booth to say G’Day and enjoyed a Tim Tam or two ;)

    Huge thank you to all of our podcast guests for spending some time with us to create this episode!

    • Cody Wooten
    • Gil Broza
    • Maciek Saganowski
    • Lindy Quick
    • Carey Young
    • Leslie Morse
    • Dan Neumann
    • Joseph Falú
    • Kai Zander
    • Avi Schneier
    • Doug Page
    • Evan Leybourn
    • Jon Kerr
    • Joshua Seckel
    • Rob Duval
    • Andrew Thompson

    Transcript

    Caitlin:

    Hi, everyone. Well, that's a wrap on Agile 2022 in Nashville. The Easy Agile team is back home in Australia, and we spent most of our journey home talking about all of the amazing conversations that we got to have with everyone in the Agile community. It was great catching up with customers, partners, seeing old friends, and making lots of new ones. We managed to record some snippets of those amazing conversations, and we're excited to share them with you, our Easy Agile Podcast audience. So enjoy.

    Maciek:

    [inaudible 00:00:26].

    Tenille:

    Maciek, thanks so much for taking time with us today.

    Maciek:

    No worries.

    Tenille:

    [inaudible 00:00:30], can you let us know what was the best thing you've learned this week?

    Maciek:

    Oh, that was definitely at Melissa Perri's talk. When she talked about... Like, to me, she was talking about slowing down. And what we do in Agile, it's not just delivery, delivery, delivery, but very much learning and changing on things that we already built, and finding out what value we can give to customers. Not just ship features, it's all about value. That's what I learned.

    Tenille:

    That's great. Thank you. So what do you think would be the secret ingredient to a great Agile team?

    Maciek:

    Humility. Somehow, the team culture should embrace humility and mistakes. And people should not be afraid of making mistakes, because without making mistakes, you don't learn. That's what I think.

    Tenille:

    So what would be, I guess, if there's one Agile ceremony that every team should do, what do you think that might be?

    Maciek:

    For sure, retro, and that comes back to the mistakes and learning part.

    Tenille:

    Yeah. Fantastic.


    Maciek:

    No worries.

    Tenille:

    That's great. Thanks so much for taking time.

    Maciek:

    Okay. Thank you.

    Tenille:

    Cheers.

    Gil:

    [inaudible 00:01:42].

    Caitlin:

    Gil:, thank you so much for chatting with us. So we're all at Agile 2022 in Nashville at the moment. There's lots of interesting conversations happening.

    Gil:

    Yes.

    Caitlin:

    If you could give one piece of advice to a new forming Agile team, what would it be?

    Gil:

    It would be to finish small, valuable work together. It has a terrible acronym, FSVWT. So it cannot be remembered that way. Finish small, valuable work together. There's a lot of talk about process, working agreements, tools. This is all important, but sometimes it's too much for a team that's starting out. And so if we just remember to finish small valuable work together, that's a great story.

    Caitlin:

    Yeah, I love that. And you were a speaker at conference?

    Gil:

    Yes.

    Caitlin:

    Can you give our audience a little bit of an insight into what your conversation was about?

    Gil:


    What happens in many situations is that engineering or development doesn't really work collaboratively with product/business. And instead, there is a handoff relationship. But what happens is that in the absence of a collaborative relationship, it's really hard to sustain agility. People make a lot of one-sided assumptions. And over time, how decisions get made causes the cost of change to grow, and the safety to make changes to decrease. And when that happens, everything becomes harder to do and slower to do, so the agility takes a hit. So the essence of the talk was how can we collaboratively, so both product and engineering, work in ways that make it possible for us to control the cost of change and to increase safety? So it's not just collaboration of any kind. There are very specific principles to follow. It's called technical agility, and when we do that, we can have agility long-term.

    Caitlin:

    Great. I love it. Well, thank you so much and I hope you enjoy the rest of your time at the conference.

    Gil:

    Thank you.

    Caitlin:

    Great. Thank you.

    Tenille:

    Hi, Tenille here from Easy Agile, with Josh from Deloitte, and we're going to have a good chat about team retrospectives. So Josh, thank you for taking the time to have a good chat. So you are a bit of an expert on team retrospectives. What are your top tips?

    Josh:

    So my top tips for retrospective is first, actually make a change. Don't do a lessons observed. I've seen lots of them actually make a change, even if it's just a small one at the end. The second, and part of that, is make your change and experiment. Something you can measure, something that you can actually say yes, we did this thing and it had an impact. May not be the impact you wanted, but it did have some kind of impact. The second tip is vary your retrospectives. Having a retrospective that's the same sprint after sprint after sprint will work for about two sprints, and then your productivity, your creativity out of the retrospective will significantly reduce.

    Tenille:

    That's an excellent point. So how do you create [inaudible 00:05:03]?

    Josh:

    Lots and lots of thinking about them and doing research and using websites like TastyCupcakes, but also developing my own retrospectives. I've done retrospective based on the Pixar pitch. There's six sentences that define every Pixar movie. Take the base sentences, apply them to your sprint or to your PI and do a retro, and allow the team that creativity to create an entire movie poster if they want to. Directed by [inaudible 00:05:34], because it happens. People get involved and engaged when you give them alternatives, different ways of doing retrospectives.


    Tenille:

    That's right. So for those teams that aren't doing retrospectives at the moment, what's the one key thing they need to think about that you... What's the one key thing you could tell them to encourage them to start?

    Josh:

    If you're not doing retrospectives, you're not doing [inaudible 00:05:54]. So I shouldn't say that. But if you're not doing retrospectives, if you truly believe that you have absolutely nothing to improve and you are 100% of the best of the best, meaning you're probably working at Google or Amazon or Netflix, although they do retrospectives. So if you truly believe that you are the equivalent of those companies, then maybe you don't need to do them, but I'm pretty sure that every team has something they can improve on. And acknowledging that and then saying, how are we going to do that? Retrospective's a very fast, easy way to start actually making those improvements and making them real.

    Tenille:

    Fantastic. Great. Thanks so much for taking the time to chat to us briefly about retrospectives.

    Josh:

    Thank you.

    Caitlin:

    We're here with Leslie, who is the president of women in Agile. Leslie, there was an amazing event on Sunday.

    Leslie:

    Yes.

    Caitlin:

    Just talk to us a little bit about it. What went into the planning? How was it to all be back together again?

    Leslie:

    It was amazing to have the women in Agile community back together, right? Our first time since 2019, when everyone was together in Washington DC for that event. The better part of six or seven months of planning, we had about almost 200 people in the room. Fortunately, we know the [inaudible 00:07:10] of what these women in Agile sessions that we do, part of the Agile Alliance conferences every year, right? We've got a general opening. We've got a great keynote who is always someone that is adjacent to the Agile space. We don't want to just like... We want to infuse our wisdom and knowledge with people that aren't already one of us, because we get all of the Agile stuff at the big conference when we're there.

    Leslie:

    So that part, we always have launching new voices, which is really probably one of my most favorite women in Agile programs. Three mentees that have been paired with seasoned speakers, taking stage for the first time to share their talent and their perspective. So that's really great. And then some sort of interacting networking event. So that pattern has served us really well since we've been doing this since 2016, which is a little scary to think it's been happening that long. And it's become a flagship opportunity for community to come together in a more global fashion, because the Agile Alliance does draw so many people for their annual event.

    Caitlin:

    Yeah, for sure. Well, it was a great event. I know that we all had a lot of fun being there. What was your one key takeaway from the event?

    Leslie:

    I'm going to go to [inaudible 00:08:14] interactive networking that she did with us, and really challenging us to lean into our courage around boundaries and ending conversations. We don't have to give a reason. If some conversation's not serving us or is not the place that we need to be for whatever reason, you absolutely have that agency within yourself to end that conversation and just move on. I love the tips and tricks she gave us for doing that well.

    Caitlin:

    Yes, yes, I love that too. That's great. Well, thank you so much. Appreciate it.

    Leslie:

    Yeah. Thanks for having me.

    Tenille:

    Hi, Evan. How are you?

    Evan:

    Very good.

    Tenille:

    That's good. Can you please tell me what's the best thing you learned today?

    Evan:

    The best quote I've got, "Politics is the currency of human systems." Right?

    Tenille:

    Wow.

    Evan:

    So if you want to change a human system, you got to play the politics.

    Tenille:


    Fantastic.

    Evan:

    Which feels crappy, but-

    Tenille:

    It's the way it is.

    Evan:

    ... that's the way it is.

    Tenille:

    [inaudible 00:09:07]. Okay, next question. What is the Agile ceremony that you and your team can't live without?

    Evan:

    Retrospective. With the retrospective, you can like create everything else.

    Tenille:

    Fantastic. That's really good. And what do you think is probably the key ingredient to a good retrospective?

    Evan:

    Oh, trust. Trust requires respect. It requires credibility. It requires empathy. So trust is like that underpinning human capability.

    Tenille:

    Yeah. Fantastic. Thanks very much.

    Evan:

    Thank you.

    Tenille:

    Yes.

    Caitlin:

    Right. We're here with Cody from Adfire. So Cody, how you enjoyed the conference so far?

    Cody:

    I'm really loving the conference. It's been awesome. To be honest, when we first got here, it seemed maybe a little bit smaller than we thought, but the people here's been incredible, highly engaged, which was always great. And plus, a lot of people are using Jira and Atlassian. So lot of big points.


    Caitlin:

    Win-win for both, huh?

    Cody:

    Yeah. Always, always, always.

    Caitlin:

    Very good.

    Cody:

    Yeah.

    Caitlin:

    Lots of interesting talks happening. Have you attended any that have really sparked an interest in you? What's [inaudible 00:10:15]-

    Cody:

    Yeah. I can't remember any of the talk names right off the top, but they've all been incredibly insightful. Tons of information. It seems like there's been a topic for everything, which is always a great sign and stuff like that. So my notes, I have pages and pages and pages of notes, which is always a good sign.

    Caitlin:

    Yeah, that's [inaudible 00:10:34].

    Cody:

    So I'm I have to go back and [inaudible 00:10:35] again.

    Caitlin:

    Yes.

    Cody:

    But it's been incredible and the talks have been very plentiful, so yeah.

    Caitlin:

    Good. Good. And what is the one key takeaway that you are looking forward to bringing back and sharing with the team?

    Cody:

    Well, I think one of the key takeaways for us was that... I talked about the engagement that everybody has, but one thing that's been incredible is to hear everybody's stories, to hear everybody's problems, their processes, all of that stuff. So all of that information's going to be a great aggregate for us to take back and create a better experience with our product and all that good stuff. So yeah.


    Caitlin:

    For sure. I love it. Now, I have one last question for you. It's just a fun one. It's a true or false. We're doing Aussie trivia. Are you ready for this one?

    Cody:

    Okay.

    Caitlin:

    Okay.

    Cody:

    Hopefully.

    Caitlin:

    So my true or false is, are Budgy Smugglers a type of bird?

    Cody:

    Are buggy smugglers-

    Caitlin:

    Budgy Smugglers.

    Cody:

    Budgy Smugglers.

    Caitlin:

    A type of bird.

    Cody:

    True.

    Caitlin:

    False. No.

    Cody:

    What are they?

    Caitlin:

    Speedos.

    Cody:


    Yeah. Well, I've got some of those up there in my luggage. So I'll bring the budgys out now.

    Caitlin:

    With your Daisy Dukes.

    Cody:

    Exactly. Exactly.

    Caitlin:

    Yeah. And cowboy boots, right?

    Cody:

    Yeah.

    Caitlin:

    Well, thank you so much.

    Cody:

    Thank you.

    Caitlin:

    Very appreciate it.

    Cody:

    Yeah. Thank you.

    Tenille:

    Doug, how are you?

    Doug:

    I'm great. Thank you.

    Tenille:

    Awesome. Well, tell me about, what's the best thing you've learned today?

    Doug:

    I think learning how our customers are using our products that we didn't even know about is really interesting.

    Tenille:

    That's amazing. Have you had a chance to get out to many of the sessions at all?


    Doug:

    I actually have not. I've been tied to this booth, or I've been in meetings that were already planned before I even came down here.

    Tenille:

    [inaudible 00:12:01].

    Doug:

    Yeah.

    Tenille:

    That's good. So when you're back at work, what do you think is probably the best Agile ceremony that you and your team can't live without?

    Doug:

    I think what I'm bringing back to the office is not so much ceremony. It's really from a product perspective. I work in product management. So for us, it's how we can explain how our product brings value to our customers. So many lessons learned from here that we're really anxious to bring back and kind of build into our value messaging.

    Tenille:

    Fantastic.

    Doug:

    Yeah.

    Tenille:

    Thanks. That's great. Thanks very much.

    Caitlin:

    He was one of the co-authors of the Agile Manifesto. Firstly, how are you doing in conference so far?

    John:

    Well, working hard.

    Caitlin:

    Yeah, good stuff.

    John:

    Enjoying Nashville.

    Caitlin:


    Yeah. It's cool, isn't it? It's so different from the [inaudible 00:12:46] what's happening.

    John:

    Yeah. It's good. Yes. It's nice to see a lot of people I haven't seen in a while.

    Caitlin:

    Yeah. Yeah.

    John:

    And seeing three dimensional.

    Caitlin:

    Yes. Yeah, I know. It's interesting-

    John:

    It's there-

    Caitlin:

    ... [inaudible 00:12:54] and stuff happening.

    John:

    Yeah, IRL.

    Caitlin:

    Lots of interesting [inaudible 00:13:01] that's happening. Any key takeaways for you? What are you going to take after to share with the team?

    John:

    Oh, well, that's a good question. I'm mostly been talking with a lot of friends that I haven't seen in a while. [inaudible 00:13:14].

    Caitlin:

    Yes.

    John:

    And since I've only been here a couple days, I haven't actually gone for much, if anything. To be frank.

    Caitlin:

    I know. Well, we're pretty busy on the boots, aren't we?

    John:


    Yeah. Yeah. But certainly, the kinds of conversations that are going on are... I was a little bit worried about Agile. Like, I don't want to say... Yeah, I don't want to say it. But I don't want to say, Agile's becoming a jump turf.

    Caitlin:

    Yes.

    John:

    But I think there's a lot of people here that are actually really still embracing the ideals and really want to learn, do and practice [inaudible 00:14:00].

    Caitlin:

    Yeah.

    John:

    So I'm frankly surprised and impressed and happy. There's a lot. If you just embrace more of the manifesto, and maybe not all of the prescriptive stuff sometimes, and you get back to basics. [inaudible 00:14:22]-

    Caitlin:

    Yeah. So let's talk about that, the Agile Manifesto that you mentioned. Embracing that. What does embracing mean? Can you elaborate on that a bit more? So we know we've got the principles there. Is there one that really stands out more than another to you?

    John:

    Well, my world of what I was doing at the time, and I'd done a lot of defense department, water haul, and built my own sort of lightweight process, as we call it before Agile. So to me, the real key... This doesn't have the full-

    Caitlin:

    Full manifesto, yeah.

    John:

    But if you go to the website and read at the top, it talks about like we are uncovering ways by doing, and I'm still learning, still uncovering. And I think it's important for people to realize we really did leave our ego at the door. Being humble in our business is super important. So that might not be written anywhere in the principles, but if the whole thing at the preamble at the top, and the fact that we talk about how we value those things on the blog versus the whole... There's a pendulum that you could see both of those things collide. That, in my opinion, one the most important trait that we should exercise is being humble, treating things as a hypothesis. Like, don't just build features [inaudible 00:15:58] bottom up, how do you seek up on the answers, that's what I want people to takeaway.

    Caitlin:


    That's great. That's great advice. Well, thank you so much, John. Appreciate you taking the time to chat with us.

    John:

    You're welcome, Caitlin.

    Caitlin:

    Yeah. Enjoy what's [inaudible 00:16:11].

    John:

    Thank you.

    Caitlin:

    Thank you.

    John:

    [inaudible 00:16:13] tomorrow.

    Caitlin:

    All right.

    Tenille:

    Abukar, thanks for joining us today. Can I ask you both, what do you think is the best thing you've learned today?

    Avi:

    Best thing I've learned?

    Tenille:

    Yeah.

    Avi:

    That's a really interesting one. Because I'm here at the booth a lot, so I'll get to attend a lot of things. So there were two things I learned that were really important. One, which is that the Easy Agile logo is an upside down A, because it means you're from Australia. So it's down under. And then the second most important thing I learned about today was we were in a session talking about sociocracy, and about how to make experiments better with experiments, which sounded a little weird at first, but it was really all about going through like a mini A3 process. For those of you listening, that's something that was done to Toyota. It's a structured problem solving method, but instead of going [inaudible 00:17:02] around it and going through the experiment, going around two or three times and then deciding that's the right experiment you're going forward.

    Tenille:


    Thank you. How about your time?

    Kai:

    I've been at the booth most of the time, but from that you meet a lot of people all over the world. And we really have like one thing in common, which is wanting to help people. And it's really been nice to be in a room of people if they're at the beginning of their journey or their really seasoned, that their motivation is just to really empower others. So it's been really nice to be around that kind of energy.

    Avi:

    We've really learned that our friends from Australia are just as friendly up here as you are on the other side. I feel when you come on this side, you get mean, but it turns out you're just as nice up here too.

    Tenille:

    Well, it depends how long you've been on flight.

    Avi:

    Oh, exactly.

    Tenille:

    [inaudible 00:17:44], we're okay.

    Kai:

    Yeah.

    Avi:Abukar:

    Exactly. Good.

    Tenille:

    All right. One more question here.

    Avi:

    Sure.

    Tenille:

    What do you think is the secret ingredient for a successful team?

    Avi:

    What do I think the secret? Oh, that's a really good question. That's a-

    Kai:

    He's the best one to answer that question.


    Avi:

    That's a little longer than a two-second podcast, but I'll tell you this. It may not be psychological safety,-

    Tenille:

    Okay.

    Avi:

    ... just because Google said that and Project Aristotle show that. I think to have a really, really successful team, you need a really skilled scrum master. Because to say that the team has psychological safety is one ingredient, it's not the only ingredient. A strong scrum master is someone who's really skilled to create that psychological safety, but also help with all the other aspects of getting ready to collaborate and coordinate in the most positive way possible. Plus, searching for... Her name is Cassandra. On Slack, she calls herself Kaizen. You get it? It's a joke. But that's the whole thing is that a really skilled scrum master helps the teams find the kaizens that they need to really get to become high performing. So psychological safety is an enabler of it, but that doesn't mean it creates the performance. It's an ingredient to make it happen.

    Tenille:

    Fantastic.

    Kai:

    There's no better answer than that one. Let's do exclamation.

    Tenille:

    Excellent. Thanks very much for taking the time.

    Avi:

    Thank you so much.

    Kai:

    Of course.

    Hayley:

    We're here with Carey from Path to Agility. Carey, what have you been really loving about this conference?

    Carey:

    I think I've loved the most about this conference so far is the interaction with all the people that are here. It's really nice to get together, meet different folks, network around, have the opportunity to see what else is out there in the marketplace. And then, of course, talk about the product that we have with Path to Agility. It's a wonderful experience to get out here and to see everybody. And it's so nice to be back out in person instead of being in front of a screen all the time.


    Tenille:

    Yeah, absolutely. Have you had a chance to get to many of the sessions?

    Joseph:

    I've tried to as much as I can, but it's also important to take that time to decompress and let everything sink in. So here we are having fun.

    Tenille:

    Yeah, absolutely. So thinking back to work, what do you think is the one Agile ceremony that you take that helps you and your team the most?

    Joseph:

    I think that finding different ways to collaborate, effective ways to collaborate. And in terms of work management, how are we solving some of the problems that we have? There's so many tools that are here to make that easier, which is made pretty special. Speaking to people and finding out how they go about solving problems.

    Tenille:

    And what do you think makes a really great Agile team?

    Joseph:

    Well, you could say something very cliche, like being very adaptive and change and so on and so forth. But I think it really comes down to the interaction between people. Understanding one another, encouraging one another, and just the way you work together.

    Tenille:

    Fantastic. Great. Well, thanks very much for taking the time to chat.

    Joseph:

    Thank you. It was nice chatting with you guys all week long.

    Tenille:

    Cheers.

    Tenille:

    Dan, thanks for taking the time to chat.

    Dan:

    You're welcome.

    Tenille:

    [inaudible 00:22:54] questions. What do you think is the best thing you learned today?


    Dan:

    Oh, the best thing I learned today, the morning products keynote was excellent. Got a couple tips on how to do product management, different strategies, how you have folks about seeing their focus on the tactical and the strategic. So just some nice little nuggets, how to [inaudible 00:23:12].

    Tenille:

    [inaudible 00:23:13], thanks for joining us today. Can I start by asking, what do you think is the best thing you've learned this week?

    Speaker 17:

    The best thing I've learned this week is there's no right way to do Agile. There's a lot of different ways you can do it. And so it's really about figuring out what the right process is for the organization you're in, and then leveraging those success patterns.

    Tenille:

    Well, I guess on that, is there one kind of Agile ceremony that you think your team can't do without?

    Speaker 17:

    The daily standup being daily. I think a lot of our teams, they talk all day long. They don't necessarily need to sync up that frequently. I've had a few teams already, they go down like three days a week and it seems to work for them. The other maybe key takeaway that I've seen folks do is time boxes. So no meetings from 10:00 to 2:00 or whatever it may be, and really driving that from a successful perspective.

    Tenille:

    I guess on that note, what do you think makes a really successful Agile team?

    Speaker 17:

    The ability to talk to each other, that ability to communicate. And so with all of our teams being either hybrid or remote, making sure that we have the tools that let them feel like they can just pick up and talk to somebody anytime they want, I think is key. And a lot of folks still don't have cameras, right, which is baffling to me. But that ability to see facial expressions, being face to face has been so nice because we're able to get that. So that's the other key is just that ability to talk to each other as though I could reach out and touch you.

    Tenille:

    Okay. Fantastic. Well, thanks so much.

    Speaker 17:

    You're welcome. Thank you.

    Tenille:

    Okay. Rob and Andrew, thanks so much for taking a few minutes with us. Can I start by asking you, what do you think is the best thing you learned this week?


    Rob:

    For me, it's definitely fast scaling Agile, we learned about this morning. We're going to try it.

    Andrew:

    For me, I really enjoyed the math programming session and learning kind of different ways to connect engineers and collaborate.

    Tenille:

    Great. Next up, I guess, what do you think makes a great Agile team?

    Rob:

    First and foremost, that they're in control of how they work and what they work on, more than anything else.

    Andrew:

    Yeah. For me, it's a obviously psychological safety and just having a good team dynamic where they can disagree, but still be respectful and come up with great ideas.

    Tenille:

    And is there one Agile ceremony that you think a great team can't live without?

    Rob:

    Probably retrospective. I think the teams need to always be improving, and that's a good way to do it.

    Andrew:

    Agreed. Yeah. Agreed.

    Tenille:

    Okay. That's great. Thanks so much for taking the time.

    Andrew:

    Thank so much. Appreciate it.

  • Podcast

    Easy Agile Podcast Ep.34 Henrik Kniberg on Team Productivity, Code Quality, and the Future of Software Engineering

    TL;DR

    Henrik Kniberg, the agile coach behind Spotify's model, discusses how AI is fundamentally transforming software development. Key takeaways: AI tools like Cursor and Claude are enabling 10x productivity gains; teams should give developers access to paid AI tools and encourage experimentation; coding will largely disappear as a manual task within 3–4 years; teams will shrink to 2 people plus AI; sprints will become obsolete in favour of continuous delivery; product owners can now write code via AI, creating pull requests instead of user stories; the key is treating AI like a brilliant intern – when it fails, the problem is usually your prompt or code structure, not the AI. Bottom line: Learn to use AI now, or risk being left behind in a rapidly changing landscape.

    Introduction

    Artificial intelligence is fundamentally reshaping how software teams work, collaborate, and deliver value. But with this transformation comes questions: How do we maintain team morale when people fear being replaced? What happens to code quality when AI writes most of the code? Do traditional agile practices like sprints still make sense?

    In this episode, I sit down with Henrik Kniberg to tackle these questions head-on. Henrik is uniquely positioned to guide us through this transition – he's the agile coach and entrepreneur who pioneered the famous Spotify model and helped transform how Lego approached agile development. Now, as co-founder of Abundly AI, he's at the forefront of helping teams integrate AI into their product development workflows.

    This conversation goes deep into the practical realities of AI-powered development: from maintaining code review processes when productivity increases 10x, to ethical considerations around AI usage, to what cross-functional teams will look like in just a few years. Henrik doesn't just theorise – he shares real examples from his own team, where their CEO (a non-coder) regularly submits pull requests, and where features that once took a sprint can now be built during a 7-minute subway ride.

    Whether you're a developer wondering if AI will replace you, a product owner looking to leverage these tools, or a leader trying to navigate this transformation, this episode offers concrete, actionable insights for thriving in the AI era.

    About Our Guest

    Henrik Kniberg is an agile coach, author, and entrepreneur whose work has shaped how thousands of organisations approach software development. He's best known for creating the Spotify model – the squad-based organisational structure that revolutionised how large tech companies scale agile practices. His work at Spotify and later at Lego helped demonstrate how agile methodologies could work at enterprise scale whilst maintaining team autonomy and innovation.

    Henrik's educational videos have become legendary in the agile community. His "Agile Product Ownership in a Nutshell" video, created over a decade ago, remains one of the most-watched and shared resources for understanding product ownership, with millions of views. His ability to distil complex concepts into simple, visual explanations has made him one of the most accessible voices in agile education.

    More recently, Henrik has turned his attention to the intersection of AI and product development. As co-founder of Abundly AI, he's moved from teaching about agile transformation to leading AI transformation – helping companies and teams understand how to effectively integrate generative AI tools into their development workflows. His approach combines his deep understanding of team dynamics and agile principles with hands-on experience using cutting-edge AI tools like Claude, Cursor, and GitHub Copilot.

    Henrik codes daily using AI and has been doing so for over two and a half years, giving him practical, lived experience with these tools that goes beyond theoretical understanding. He creates educational content about AI, trains teams on effective AI usage, and consults with organisations navigating their own AI transformations. His perspective is particularly valuable because he views AI through the lens of organisational change management – recognising that successful AI adoption isn't just about the technology, it's about people, culture, and process.

    Based in Stockholm, Sweden, Henrik continues to push the boundaries of what's possible when human creativity and AI capabilities combine, whilst maintaining a pragmatic, human-centred approach to technological change.

    Transcript

    Note: This transcript has been lightly edited for clarity and readability.

    Maintaining Team Morale and Motivation in the AI Era

    Tenille Hoppo: Hi there, team, and welcome to this new episode of the Easy Agile Podcast. My name is Tenille Hoppo, and I'm feeling really quite lucky to have an opportunity to chat today with our guest, Henrik Kniberg.

    Henrik is an agile coach, author, and entrepreneur known for pioneering agile practices at companies like Spotify and Lego, and more recently for his thought leadership in applying AI to product development. Henrik co-founded Abundly AI, and when he isn't making excellent videos to help us all understand AI, he is focused on the practical application of generative AI in product development and training teams to use these technologies effectively.

    Drawing on his extensive experience in agile methodologies and team coaching, Henrik seems the perfect person to learn from when thinking about the intersection of AI, product development, and effective team dynamics. So a very warm welcome to you, Henrik.

    Henrik Kniberg: Thank you very much. It's good to be here.

    Tenille: I think most people would agree that motivated people do better work. So I'd like to start today by touching on the very human element of this discussion and helping people maintain momentum and motivation when they may be feeling some concern or uncertainty about the upheaval that AI might represent for them in their role.

    What would you suggest that leaders do to encourage the use of AI in ways that increase team morale and creativity rather than risking people feeling quite concerned or even potentially replaced?

    Henrik: There are kind of two sides to the coin. There's one side that says, "Oh, AI is gonna take my job, and I'm gonna get fired." And the other side says, "Oh, AI is going to give me superpowers and give us all superpowers, and thereby give us better job security than we had before."

    I think it's important to press on the second point from a leader's perspective. Pitch it as this is a tool, and we are entering a world where this tool is a crucial tool to understand how to use – in a similar way that everyone uses the Internet. We consider it obvious that you need to know how to use the Internet. If you don't know how to use the Internet, it's going to be hard.

    "I encourage people to experiment, give them access to the tools to do so, and encourage sharing. And don't start firing people because they get productive."

    I also find that people tend to get a little bit less scared once they learn to use it. It becomes less scary. It's like if you're worried there's a monster under your bed, maybe look under your bed and turn on the lights. Maybe there wasn't a monster there, or maybe it was there but it was kind of cute and just wanted a hug.

    Creating a Culture of Safe Experimentation

    Tenille: I've read that you encourage experimentation with AI through learning – I agree it's the best way to learn. What would you encourage leaders and team leaders to do to create a strong culture where teams feel safe to experiment?

    Henrik: There are some things. One is pretty basic: just give people access to good AI tools. And that's quite hard in some large organisations because there are all kinds of resistance – compliance issues, data security issues. Are we allowed to use ChatGPT or Claude? Where is our data going? There are all these scary things that make companies either hesitate or outright try to stop people.

    Start at that hygiene level. Address those impediments and solve them. When the Internet came, it was really scary to connect your computer to the Internet. But now we all do it, and you kind of have to, or you don't get any work done. We're at this similar moment now.

    "Ironically, when companies are too strict about restricting people, then what people tend to do is just use shadow AI – they use it on their own in private or in secret, and then you have no control at all."

    Start there. Once people have access to really good AI tools, then it's just a matter of encouraging and creating forums. Encourage people to experiment, create knowledge-sharing forums, share your own experiments. Try to role-model this yourself. Say, "I tried using AI for these different things, and here's what I learned." Also provide paths for support, like training courses.

    The Right Mindset for Working with AI

    Tenille: What would you encourage in team members as far as their mindset or skills go? Certainly a nature of curiosity and a willingness to learn and experiment. Is there anything beyond that that you think would be really key?

    Henrik: It is a bit of a weird technology that's never really existed before. We're used to humans and code. Humans are intelligent and kind of unpredictable. We hallucinate sometimes, but we can do amazing things. Code is dumb – it executes exactly what you told it to do, and it does so every time exactly the same way. But it can't reason, it can't think.

    Now we have AI and AI agents which are somewhere in the middle. They're not quite as predictable as code, but they're a lot more predictable than humans typically. They're a lot smarter than code, but maybe not quite as smart as humans – except for some tasks when they're a million times smarter than humans. So it's weird.

    You need a kind of humble attitude where you come at it with a mindset of curiosity. Part of it is also to realise that a lot of the limitation is in you as a user. If you try to use AI for coding and it wrote something that didn't work, it's probably not the model itself. It's probably your skills or lack of skills because you have to learn how to use these tools. You need to have this attitude of "Oh, it failed. What can I do differently next time?" until you really learn how to use it.

    "There can be some aspect of pride with developers. Like, 'I've been coding for 30 years. Of course this machine can't code better than me.' But if you think of it like 'I want this thing to be good, I want to bring out the best in this tool' – not because it's going to replace me, but because it's going to save me a tonne of time by doing all the boring parts of the coding so I can do the more interesting parts – that kind of mindset really helps."

    Maintaining Code Quality and Shared Understanding

    Tenille: Our team at Easy Agile is taking our steps and trying to figure out how AI is gonna work best for us. I put the question out to some of our teams, and there were various questions around people taking their first steps in using AI as a co-pilot and producing code. There are question marks around consistency of code, maintaining code quality and clean architecture, and even things like maintaining that shared understanding of the code base. What advice do you have for people in that situation?

    Henrik: My first piece of advice when it comes to coding – and this is something I do every day with AI, I've been doing for about two and a half years now – is that the models now, especially Claude, have gotten to the level where it's basically never the AI's fault anymore. If it does anything wrong, it's on you.

    You need to think about: okay, am I using the wrong tool maybe? Or am I not using the tool correctly?

    For example, the current market leader in terms of productivity tools with AI is Cursor. There are other tools that are getting close like GitHub Copilot, but Cursor is way ahead of anything else I've seen. With Cursor, it basically digs through your code base and looks for what it needs.

    But if it fails to find what it needs, you need to think about why. It probably failed for the same reason a human might have failed. Maybe your code structure was very unstructured. Maybe you need to explain to the AI what the high-level structure of your code is.

    "Think of it kind of like a really smart intern who just joined your team. They're brilliant at coding, but now they got confused about something, and it's probably your code – something in it that made it confused. And now you need to clarify that."

    There are ways to do that. In Cursor, for example, you can create something called cursor rules, which are like standing documents that describe certain aspects of your system. In my team, we're always tweaking those rules. Whenever we find that the AI model did something wrong, we're always analysing why. Usually it's our prompt – I just phrased it badly – or I just need to add a cursor rule, or I need to break the problem down a little bit.

    It's exactly the same thing as if you go to a team and give them this massive user story that includes all these assumptions – they'll probably get some things wrong. But if you take that big problem and sit down together and analyse it and split it into smaller steps where each step is verifiable and testable, now your team can do really good work. It's exactly the same thing with AI.

    Addressing the Code Review Bottleneck

    Tenille: One of our senior developers found that he was outputting code at a much greater volume and faster speed, but the handbrake he found was actually their code review processes. They were keeping the same processes they had previously, and that was a bit of a handbrake for them. What kind of advice would you have there?

    Henrik: This reminds me of the general issue with any kind of productivity improvement. If you have a value stream, a process where you do different parts – you do some development, some testing, you have some design – whenever you take one part of the process and make it super optimised, the bottleneck moves to somewhere else.

    If testing is no longer the bottleneck, maybe coding is. And when coding is instant, then maybe customer feedback – or lack of customer feedback – is the bottleneck. The bottleneck just keeps moving. In that particular case, the bottleneck became code review. So I would just start optimising that. That's not an AI problem. It's a process problem.

    Look at it: what exactly are we trying to do when we review? Maybe we could think about changing the way we review things. For example, does all code need to be reviewed? Would it be enough that the human who wrote it and the AI, together with the human, agree that this is fine? Or maybe depending on the criticality of that change, in some cases you might just let it pass or use AI to help in the reviewing process also.

    "I think there's value in code review in terms of knowledge sharing in a large organisation. But maybe the review doesn't necessarily need to be a blocking process either. It could be something you go back and look at – don't let it stop you from shipping, but maybe go back once per week and say, 'Let's look at some highlights of some changes we've made.'"

    We produce 10 times more code than in the past, so reviewing every line is not feasible. But maybe we can at least identify which code is most interesting to look at.

    Ethical Considerations: Balancing Innovation with Responsibility

    Tenille: Agile emphasises people over process and delivering value to customers. Now with AI in the mix, there's potential for raising some ethical considerations. I'm interested in your thoughts on how teams should approach these ethical considerations that come along with AI – things like balancing rapid experimentation against concerns around bias, potential data privacy concerns.

    Henrik: I would treat each ethical question on its own merits. Let me give you an example. When you use AI – let's say facial recognition technology that can process and recognise faces a lot better than any human – I kind of put that in the bucket of: any tool that is really useful can also be used for bad things. A hammer, fire, electricity.

    That doesn't have so much to do with the tool itself. It has much more to do with the rules and regulations and processes around the tool. I can't really separate AI in that sense. Treat it like any other system. Whenever you install a camera somewhere, with or without AI, that camera is going to see stuff. What are you allowed to do with that information? That's an important question. But I don't think it's different for AI really, in that sense, other than that AI is extremely powerful. So you need to really take that seriously, especially when it comes to things like autonomous weapons and the risk of fraud and fake news.

    "An important part of it is just to make it part of the agenda. Let's say you're a recruitment company and you're now going to add some AI help in screening. At least raise the question: we could do this. Do we want to do this? What is the responsible way to do it?"

    It's not that hard to come up with reasonable guidelines. Obviously, we shouldn't let the AI decide who we're going to hire or not. That's a bad idea. But maybe it can look at the pile of candidates that we plan to reject and identify some that we should take a second look at. There's nothing to lose from that because that AI did some extra research and found that this person who had a pretty weak CV actually has done amazing things before.

    We're actually working with a company now where we're helping them build some AI agents. Our AI agents help them classify CVs – not by "should we hire them or not," but more like which region in Sweden is this, which type of job are we talking about here. Just classifying to make it more likely that this job application reaches the right person. That's work that humans did before with pretty bad accuracy.

    The conclusion was that AI, despite having biases like we humans do, seemed to have less biases than the human. Mainly things like it's never going to be in a bad mood because it hasn't had its coffee today. It'll process everybody on the same merits.

    I think of it like a peer-to-peer thing. Imagine going to a doctor – ideally, I want to have both a human doctor and an AI doctor side by side, just because they both have biases, but now they can complement each other. It's like having a second opinion. If the AI says we should do this and the doctor says, "No, wait a second," or vice versa, having those two different opinions is super useful.

    Parallels Between Agile and AI Transformations

    Tenille: You're recognised as one of the leading voices in agile software development. I can see, and I'm interested if you do see, some parallels between the agile transformations that you led at Spotify and Lego with the AI transformations that many businesses are looking at now.

    Henrik: I agree. I find that when we help companies transition towards becoming AI native, a lot of the thinking is similar to agile. But I think we can generalise that agile transformations are not really very special either – it's organisational change.

    There are some patterns involved regardless of whether you're transitioning towards an agile way of working or towards AI. Some general patterns such as: you've got to get buy-in, it's useful to do the change in an incremental way, balance bottom-up with top-down. There are all these techniques that are useful regardless. But as an agilist, if you have some skills and competence in leading and supporting a change process, then that's going to be really useful also when helping companies understand how to use AI.

    Tenille: Are you seeing more top-down or bottom-up when it comes to AI transformations?

    Henrik: So far it's quite new still. The jury's not in yet. But so far it looks very familiar to me. I'm seeing both. I'm seeing situations where it's pure top-down where managers are like "we got to go full-out AI," and they push it out with mixed results. And sometimes just completely bottom-up, also with mixed results.

    Sometimes something can start completely organically and then totally take hold, or it starts organically and then gets squashed because there was no buy-in higher up. I saw all of that with agile as well. My guess is in most cases the most successful will be when you have a bit of both – support and guidance from the top, but maybe driven from the bottom.

    "I think the bottom-up is maybe more important than ever because this technology is so weird and so fast-moving. As a leader, you don't really have a chance if you try to control it – you're going to slow things down to an unacceptable level. People will be learning things that you can't keep up with yourself. So it's better to just enable people to experiment a lot, but then of course provide guidance."

    AI for Product Owners: From Ideation to Pull Requests

    Tenille: You're very well known for your guidance and for your ability to explain quite complex concepts very simply and clearly. I was looking at your video on YouTube today, the Agile Product Ownership in a Nutshell video, which was uploaded about 12 years ago now. Thinking about product owners, there's a big opportunity now with AI for generating ideas, analysing data, and even suggesting new features. What's your advice for product owners and product managers in using AI most effectively?

    Henrik: Use it for everything. Overuse it so you can find the limits. The second thing is: make sure you have access to a good AI model. Don't use the free ones. The difference is really large – like 10x, 100x difference – just in paying like $20 per month or something. At the moment, I can particularly strongly recommend Claude. It's in its own category of awesomeness right now. But that of course changes as they leapfrog each other. But mainly: pay up, use a paid model, and then experiment.

    For product owners, typical things are what you already mentioned – ideation, creating good backlog items, splitting a story – but also writing code. I would say as a PO, there is this traditional view, for example in Scrum, that POs should not be coding. There's a reason for that: because coding takes time, and then as PO you get stuck in details and you lose the big picture.

    Well, that's not true anymore. There are very many things that used to be time-consuming coding that is basically a five-minute job with a good prompt.

    "Instead of wasting the team's time by trying to phrase that as a story, just phrase it as a pull request instead and go to the team and demonstrate your running feature."

    That happened actually today. Just now, our CEO, who's not a coder, came to me with a pull request. In fact, quite often he just pushes directly to a branch because it's small changes. He wants to add some new visualisation for a graph or something in our platform – typically admin stuff that users won't see, so it's quite harmless if he gets it wrong.

    He's vibe coding, just making little changes to the admin, which means he never goes to my team and says, "Hey, can you guys generate this report or this graph for how users use our product?" No, he just puts it in himself if it's simple.

    Today we wanted to make a change with how we handle payments for enterprise customers. Getting that wrong is a little more serious, and the change wasn't that hard, but he just didn't feel completely comfortable pushing it himself. So he just made a PR instead, and then we spent 15 minutes reviewing it. I said it was fine, so we pushed it.

    It's so refreshing that now anybody can code. You just need to learn the basic prompting and these tools. And then that saves time for the developers to do the more heavyweight coding.

    Tenille: It's an interesting world where we can have things set up where anyone could just jump in and with the right guardrails create something. It makes Friday demos quite probably a lot more interesting than maybe they used to be in the past.

    Henrik: I would like to challenge any development team to let their stakeholders push code, and then find out whatever's stopping you from doing that and fix that. Then you get to a very interesting space.

    Closing the Gap Between Makers and Users

    Tenille: A key insight from your work with agile teams in the past has been to really focus on minimising that gap between maker and user. Do you think that AI helps to close that gap, or do you think it potentially risks widening it if teams are focusing too much on AI predictions and stop talking to their customers effectively?

    Henrik: I think that of course depends a lot on the team. But from what I've seen so far, it massively reduces the gap. Because if I don't have to spend a week getting a feature to work, I can spend an hour instead. Then I have so much more time to talk to my users and my customers.

    If the time to make a clickable prototype or something is a few seconds, then I can do it live in real time with my customers, and we can co-create. There are all these opportunities.

    I find that – myself, my teams, and the people I work with – we work a lot more closely with our users and customers because of this fast turnaround time.

    "Just yesterday I was teaching a course, and I was going home sitting on the subway. It was a 15-minute subway ride. I finally got a seat, so I had only 7 minutes left. There's this feature that I wanted to build that involved both front-end and back-end and a database schema change. Well, 5 minutes later it was done and I got off the subway and just pushed it. That's crazy."

    Of course, our system is set up optimised to enable it to be that fast. And of course not everything will work that well. But every time it does, I've been coding for 30 years, and I feel like I wake up in some weird fantasy every day, wondering, "Can I really be this productive?" I never would have thought that was possible.

    Looking Ahead: The Future of Agile Teams

    Tenille: I'd like you to put your futurist hat on for a moment. How do you see the future of agile teamwork in, say, 10 to 15 years time? If we would have this conversation again in 2035, given the exponential growth of AI and improvements over the last two to three years, what do you think would be the biggest change for software development teams in how they operate?

    Henrik: I can't even imagine 10 years. Even 5 years is just beyond imagination. That's like asking someone in the 1920s to imagine smartphones and the Internet. I think that's the level of change we're looking at.

    I would shorten the time a little bit and say maybe 3 or 4 years. My guess there – and I'm already seeing this transfer happen – is that coding will just go away. It just won't be stuff that we humans do because we're too slow and we hallucinate way too much.

    But I think engineering and the developer role will still be there, just that we don't type lines of code – in the same way that we no longer make punch cards or we no longer write machine code and poke values into registers using assembly language. That used to be a big part of it, but no longer.

    "In the future, as developers, a lot of the work will still be the same. You're still designing stuff, you're thinking about architecture, you're interacting with customers, and you're doing all the other stuff. But typing lines of code is something that we're gonna be telling our kids about, and they're not gonna believe that we used to do that."

    The other thing is smaller teams, which I'm already seeing now. I think the idea of a cross-functional team of 5 to 7 people – traditionally that was considered quite necessary in order to have all the different skills needed to deliver a feature in a product. But that's not the case anymore. If you skip ahead 2 or 3 years when this knowledge has spread, I think most teams will be 2 people and an AI, because then you have all the domain knowledge you need, probably.

    As a consequence of that, we'll just have more teams. More and smaller teams. Of course, then you need to collaborate between the teams, so cross-team synchronisation is still going to be an issue.

    Also, I'm already seeing this now, but this concept of sprints – the whole point is to give a team some peace of mind to build something complex, because typically you would need a week or two to build something complex. But now, when it takes a day and some good prompting to do the same thing that would have taken a whole sprint, then the sprint is a day instead. If the sprint is a day, is there any difference between a sprint planning meeting and a daily standup? Not really.

    I think sprints will just kind of shrink into oblivion. What's going to be left instead is something a little bit similar – some kind of synchronisation point or follow-up point. Instead of a sprint where every 2 weeks we sit down and try to make a plan, I think it'll be very much continuous delivery on a day-to-day basis. But then maybe every week or two we take a step back and just reflect a little bit and say, "Okay, what have we been delivering the past couple of weeks? What have we been learning? What's our high-level focus for the next couple of weeks?" A very, very lightweight equivalent of a sprint.

    I feel pretty confident about that guess because personally, we are already there with my team, and I think it'll become a bit of a norm.

    Final Thoughts: Preparing for the Future

    Henrik: No one knows what's gonna happen in the future, and those who say they do are kidding themselves. But there's one fairly safe bet though: no matter what happens in the future with AI, if you understand how to use it, you'll be in a better position to deal with whatever that is. That's why I encourage people to get comfortable with it, get used to using it.

    Tenille: I have a teenage daughter who I'm actually trying to encourage to learn how to use AI, because I feel like when I was her age, the Internet was the thing that was sort of coming mainstream. It completely changed the way we live. Everything is online now. And I feel like AI is that piece for her.

    Henrik: Isn't it weird that the generation of small children growing up now are going to consider this to be normal and obvious? They'll be the AI natives. They'll be like, "Of course I have my AI agent buddy. There's nothing weird about that at all."

    Tenille: I'll still keep being nice to my coffee machine.

    Henrik: Yeah, that's good. Just in case, you know.

    ---

    Thank you to Henrik Kniberg for joining us on this episode of the Easy Agile Podcast. To learn more about Henrik's work, visit Abundly AI or check out his educational videos on AI and agile practices.

    Subscribe to the Easy Agile Podcast on your favourite platform, and join us for more conversations about agile, product development, and the future of work.