4 ms·
Extremely important advice. Add to that: push upper management for change details, keep timelines and punctuality, define delivery, be up front on status and re
by tomrod 5y ago
Extremely important advice. Add to that: push upper management for change details, keep timelines and punctuality, define delivery, be up front on status and results, go home at a reasonable hour, take people to lunch or otherwise spend time with them, make your team appointments your number one priority, and praise publicly/coach privately.
- perpetualpatzer 5y agoCan you elaborate more on what you mean by "define delivery"?
- tomrod 5y agoIf you're leading a software team, championing a clear definition of "done" for the team and business partners (usually collaboratively). Other teams have analogous targets. There are some teams where the "work" resists completion.
- michaelt 5y agoIf I tell a guy to make me a table, and he puts his heart and soul into making me a beautiful wooden dining table, then when he shows it to me I tell him I actually wanted a glass coffee table and would he please start over from scratch, throwing his work away will be very bad for his morale. That's not to say requirements can't change - of course they can. But they shouldn't change just because I forgot to make myself clear the first time.
- fighterpilot 5y agoWhat do you mean by "change details"?
- tomrod 5y agoOften policies get set in place and in motion before they filter down, and impact is not understood. Either communicating the course, or if upper management fails in their duties, charting the course and communicating, is essential. For example, "we will deprecate this technology by XX date, and we have cleared the path to enable this" is often essential to success. In a healthy org, telling people what you're doing, how you're doing it, and why you're doing it is as necessary as when you're doing it. Just like you don't want to release every feature all at once, you similarly don't want to muck up your infrastructure (physical or business).