Is Transparency Really the Answer?

Is Transparency Really the Answer? Is Transparency Really the Answer? We hear it constantly in Agile: “We need more transparency.” But does transparency really mean sharing everything? In Episode 1647 of The Agile Daily Standup, we explore an important leadership lesson: more information does NOT automatically create more understanding. Long status reports, endless project updates, detailed explanations, milestones, metrics, and mountains of data may technically make us transparent—but they can also bury the one thing our audience actually needs to know: Why does this matter? Great communication isn't about proving how much work happened. It's about making the impact impossible to miss. 🎯 What happened? 💡 Why does it matter? 🚨 What needs attention? We'll explore why senior leaders often don't have an information problem—they have a time problem—and why effective Agile leaders learn to lead with outcomes, impact, risk, and opportunity before diving into the details. Because perhaps we've been thinking about transparency all wrong. Transparency isn't sharing everything. Transparency is making what matters easy to understand. 🎙️ Short. Practical. Relevant. Human. Episode 1647 asks one question that could completely change your next status update, presentation, Sprint Review, or leadership conversation: If someone only reads the first sentence, will they understand why it matters? How to connect with AgileDad: - [website] ⁠https://www.agiledad.com/⁠ https://www.agiledad.com/ - [instagram] ⁠https://www.instagram.com/agile_coach/⁠ https://www.instagram.com/agile_coach/ - [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠ https://www.facebook.com/RealAgileDad/ - [Linkedin] ⁠https://www.linkedin.com/in/leehenson/ https://www.linkedin.com/in/leehenson/

• 0:15Speaker 00

  I have a confession. I used to think that transparency meant sharing everything. I eventually learned that good communication is about making the most important things easy to understand and not necessarily about sharing everything. Because honestly, there's sometimes when you send things that no one even reads or cares about. So today, I want to talk a little bit about that differentiation. So, early on, as a leader of one of the world's greatest training companies, I learned that I was spending a lot of time writing updates for other people. Here's where we are with this project. Here's what's happening here. And I wanted to be transparent.

• 0:58Speaker 00

  I wanted people to understand everything that we had delivered, everything we are going to deliver, where things were going. I wanted to clearly demonstrate the amount of work that was happening across my entire company. The result was often a long update that was packed with all kinds of details about each initiative we were doing, where we stood, where a lead was, where a project was, where delivery stands, what the milestones were. Sometimes incidents were included with detailed explanations about what had happened, why it happened, how it happened, what we're going to do to prevent it from happening again. Those were rare, but they did come across. And I believe that for a long time, the more information that I shared would create greater understanding.

• 1:41Speaker 00

  And what I quickly learned was, it actually didn't. I was writing more for completeness instead of communication. Something just didn't click or didn't feel right. Updates were being sent, but I rarely received questions back. I rarely received feedback. Very few conversations seemed to come from the information that I was sharing. Looking back, I realized I was answering one question. What did I really get done? But I wasn't answering the most important one. Why should anyone even care? And here's what I found. The more senior the audience, the more that this mattered. Now, when I teach classes, I know I get a wide variety of people.

• 2:23Speaker 00

  But I often get people who are in leadership positions, senior positions, hiring positions, people who are looking to make their teams better. And some leaders just don't have time to work out the significance of what each piece of an update they receive actually means. If the value isn't obvious upfront, they'll move on to the next most important thing that demands their attention or their time. And that wasn't failure on their part. That was failure on what I was communicating. So, I decided to write down a question that changed the way that I composed my thoughts. I started approaching communication a little bit differently. Before writing any update or creating any type of presentation or report or dashboard,

• 3:07Speaker 00

  I asked myself, does this matter? And why does this matter? If I couldn't answer that question quickly, then neither could the people I was doing it for. Instead of leading with activity, I started by leading with impact. So instead of leading with output, I started leading with outcome. I stopped thinking about communication as a record of work and started thinking about it as a tool for creating a common, shared understanding. And I think when we got to that point, that was when things really started to click. Every update became an exercise in me answering three basic questions, kind of like a daily scrum. Here we go. What happened? Does it matter and why does it matter?

• 3:50Speaker 00

  And what if anything needs attention or what have we addressed? The detail didn't disappear. It was still there for the people who wanted or needed it, but it wasn't what I led with. And I found that by leading with the right cause, that that helped me achieve better communication across all the different groups we worked with across many organizations. That's going to do it for this episode. I hope that you enjoyed it. If you have a topic you want us to discuss, learn more at agiledad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye.