Leadership

now browsing by category

 

4 Things To Know About Teamwork

Here are the four things to know about teamwork: When the situation is tense, call a timeout, it’s the only thing that will work Information needs to be as close as possible to the team members that can make use of it Be aware of the message you’re sending asRead More

Quoted in “The Secrets Behind Great One-on-One Meetings”

I was recently quoted in the free ebook from O’Reilly, “The Secrets Behind Great One-on-One Meetings”. As an aspiring interview coach for software developers, it feels great to offer advice especially on the subject of one-on-one meetings. It’s a great short ebook and very useful for those wanting to see theRead More

Episode #1 – Team Lead As Coach

In the first episode of the NeverFriday Leadership Podcast, I talk about the fixer vs the coach way of thinking when leading a team and about the team lead as coach. Download the “Team Lead As Coach” episode of the NeverFriday Leadership Podcast In this episode I mention Jill Geisler’sRead More

The 90 Day Rule: From “The Team” to “Your Team”

Dave Kellogg has written a solid article about the 90-day rule. This is the rule where it takes 90 days for the team you’re leading to become your team. As a new team leader, it can take some time to get used to your team and to figure out whoRead More

Top 3 Reasons You Need to Hire a Tech Career Coach

In your software development or IT career, you’re going to eventually get to a point where you don’t quite know what to do next, or how to get to the next stage of your career. It can be hard to figure out what sorts of projects you want to workRead More

Setting Clear Priorities

To be a tech leader, rather than just a manager, you have to set clear priorities. There are two ways to do this and they apply in different situations.

5 reasons managers are addicted to “fixing” – and how to recover

This is an excellent article on why a fixer mentality is common among new managers. A fixer goes over the work of someone else and fixes it to match their standards, or they take on the work themselves entirely. This is bad because it isn’t delegation and shows a lowerRead More

How to apply cause and effect diagrams in IT and Software Development

Cause and effect diagrams, also known as Ishikawa diagrams, are one of 7 basic tools of quality. You won’t see them used very often in software development or IT projects though they should be. So today we’re going through what cause and effect diagrams are, why they’re useful, an exampleRead More

Slides for Open Source, Open Allocation talk given at 2015 Software Freedom Day

I just posted the slides for the talk I did at Software Freedom Day on 19 September 2015. The topic was open source and open allocation and how the two relate and how the future of companies is to mirror the open source development methodology. Open allocation allows workers toRead More

Leadership Influence Techniques From The Army

The United States Army has a field manual on leadership. In it, they describe multiple techniques for influencing your team/squad to accomplish tasks and fulfill mission objectives. Influence Techniques It has a great list of leadership influence techniques that would benefit platoon and squad leaders in the game and wouldRead More