@Sarky_de If you are concerned about efficiency
with some of your team members, there are better ways:
Make the impact of the non-efficency transparent, don't judge, just state facts
(e.g. time it took to build a feature, which equals money spent).
A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
@Sarky_de If you are concerned about efficiency
with some of your team members, there are better ways:
Make the impact of the non-efficency transparent, don't judge, just state facts
(e.g. time it took to build a feature, which equals money spent).
@Sarky_de And then explain why you think this
needs to be improved (please no bullshit reasons like we need to save 20%).
Then LISTEN to what they will tell you and try to figure out from that
information the underlying reasons for inefficiency.
Ask WHY a lot: https://en.wikipedia.org/wiki/5_Whys
@Sarky_de Again, be very careful to never make
the appearance that you are blaming someone. It is always (except for willful
wrongdoing) the whole team that let a certain problem come to existence.
A great technique for these kinds of "investigations" is
https://en.wikipedia.org/wiki/Nonviolent_Communication