{"id":3053,"date":"2021-07-29T07:33:19","date_gmt":"2021-07-29T05:33:19","guid":{"rendered":"https:\/\/trellisterium.de\/?p=3053"},"modified":"2022-11-28T15:49:58","modified_gmt":"2022-11-28T13:49:58","slug":"was-koennen-fuehrungskraefte-dazu-beitragen-dass-die-mitarbeiter-agiler-arbeiten","status":"publish","type":"post","link":"https:\/\/trellisterium.de\/en\/was-koennen-fuehrungskraefte-dazu-beitragen-dass-die-mitarbeiter-agiler-arbeiten\/","title":{"rendered":"What Can Managers Do to Help Employees Work More Agile?"},"content":{"rendered":"

<\/p>\n

\n

You’ve been ordered to work Agile? You even want it yourself? However, you still have a few questions? You’re not alone. For example, I was recently asked:<\/strong><\/p>\n

\n

What can managers do to help employees work more Agile?”<\/h1>\n
\"\"<\/div>\n
<\/div>\n
\n

The first thing needed is that management realises with conviction<\/h2>\n
that managers don’t manage people. They manage a system. A system of which they are a part themselves. That is:<\/div>\n
\n
It’s not the employees who work more agile. EVERYONE is working more agile: Employees AND managers. Because we are all in this together!\u00a0<\/strong><\/div>\n<\/blockquote>\n
And because leaders are particularly influential in shaping the culture with the way they act, leaders in particular should lead by example. Meaning: Start with working Agile first.<\/div>\n
\n
And this not only in speaking. But above all also: in DOING.<\/strong><\/div>\n<\/blockquote>\n
\n
\n<\/div>\n

So being helpful would be<\/h2>\n
to get into Agile routines as quickly as possible (with everything that goes with it, so e.g. transparency…) and to conduct retrospectives, for example. Not as a one-time event, but consistently over and over again!<\/div>\n
\"\"<\/div>\n
\n
\n<\/div>\n

In addition, consider<\/h2>\n
to establish a company backlog. Or at least compiling a comprehensible, well-founded, reliable, descriptive project list. With ALL projects, which are currently being worked on in the company, what is expected from these projects and what is the investment risk (the real one and not the estimated or under- or overestimated one).<\/div>\n
<\/div>\n
Just as an idea.\u00a0In my experience, that is a good start. ( However, lacking of this information or having no backlog is very quickly noticed when holding retrospectives anyway)<\/div>\n
\n

A fundamental task of all Agile leaders at all levels (!)<\/h2>\n
is exclusively to set goals and frameworks in such a way that the results of the operationally working teams can be produced as quickly and as value-adding as possible. Meaning: This needs to be done VERY customer-centric and in a profitable manner.<\/div>\n
\n
This does NOT include blaming teams for their perceived shortcomings or putting pressure on them. It also does NOT include know-it-all attitude or status buzz. Because that is VERY HARMFUL for ALL business goals.\u00a0<\/strong><\/div>\n<\/blockquote>\n
\n

The responsibility of agile management is<\/h2>\n
to explain what exactly is to be done (projects\/tasks) and, most importantly, why and with what objectives and expectations.<\/div>\n
<\/div>\n
Also, part of this is to say exactly WHAT is HOW IMPORTANT, so that the operational teams know to tackle exactly what in which order. (First things first.)<\/div>\n
\"\"<\/div>\n
\n
\n<\/div>\n

Agile leaders trust<\/h2>\n
the expertise of their teams – for which they pay a VERY large amount of money, not incidentally – and thus “only” set the organizational, structural framework. Which is a really challenging job.<\/div>\n
\n
Thus, the employees in the teams can work as freely and undisturbed as possible in their expert roles to produce the results that customers, owners and management expect. <\/strong><\/div>\n<\/blockquote>\n
Without switching costs. Without costs of delay. Without stress or other mental distress.<\/div>\n
\n
\n<\/div>\n

Disruptions and other impediments for teams<\/h2>\n
that they can’t clear on their own MUST be removed by leaders. What might that be? Well, such as canceling meetings or hosting them in a way that makes them effective.<\/div>\n
\n
Once again, meetings that are called or even extended for habit or status reasons DESTROY ADDING VALUE and put company success at risk. And that’s why we simply don’t do it!<\/strong><\/div>\n<\/blockquote>\n
\n
\n<\/div>\n

\"\"Managing and leading in an Agile way is totally different<\/h2>\n
\n
to what we commonly think of as classical management. On the other hand, many so-called classical managers I deal with are also often not classical managers at all.<\/strong><\/div>\n
<\/div>\n
On the contrary, they are happy that in an Agile transition they can become an “Agile” or “Servant” leader and – FINALLY! – be able to do what they have always wanted to do: Contribute to the company’s success.<\/strong><\/div>\n<\/blockquote>\n
\n

Read more?<\/h2>\n