Should software leaders try to shield their teams from stress and unpredictability, or is it better to be fully transparent about unknowns? What’s your reasoning behind your approach?
Sort by:
As leaders, we need to shield our teams, but also be transparent and honest. Regular updates are important, explaining the reasons behind changes and how they impact the team. For instance, with changes in flexible work hours, it is important to explain why these changes are happening and what is going on behind the scenes. Showing empathy and considering flexibility is key. Transparency is essential, but leaders also need to shield their teams when necessary.
The answer depends on the situation and the type of information being conveyed. While full transparency and honesty are important, giving too much information, especially in large organizations, can cause confusion and chaos, leading to unnecessary meetings. Sometimes, leaders must shield their teams. For example, if something goes wrong and you take ownership in front of senior management, it is important not to involve the team in blame. Conversely, when critical issues arise, the team should be made aware, as this builds resilience.
I believe leaders need to provide some level of stability. It is not effective to let everything pour through unfiltered. While transparency in the decision-making process is important, and we should not pretend to have everything figured out, it is equally important to provide clarity. I support transparency and honesty, as this helps build a proper culture and a resilient team. Teams should be informed that our plans are based on the best current information, but may change in the future. This approach prepares teams to be agile and adaptable. However, as a leader, it is also necessary to weather chaos and filter information, condensing or properly messaging it so teams are not overwhelmed.
Leaders need to absorb chaos and provide clarity. Sometimes it is necessary to hide certain things to avoid chaos within the team, but transparency should be maintained wherever possible. This approach saves a lot of stress for everyone involved.