The Effective Executive, by Peter Drucker, outlines 4 challenges that effective executives have to overcome. Your time is not your own, drive an agenda to avoid busy work, align with organizational goals and customer requirements are usually murky.
This podcast covers these 4 challenges at a high level, and future casts will talk in detail about each of these categories.
This podcast is part of a book review series, covering Peter Drucker's "The Effective Executive".
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
Check out the Technical Leadership youtube channel by searching for TechnicalLeadership or go to https://www.youtube.com/channel/UC_FvZUXWAxjYyMWj99T5qRA
Doing the right things is an essential element of being an effective leader.
The Effective Executive, by Peter Drucker, is a book written for listeners of the technical leadership podcast. "Knowledge Workers", as Peter Drucker says, need to do the right thing to help the organization move forward. Essentially all knowledge workers are executives, and the skills of effectiveness can be learned by anybody.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
Check out the Technical Leadership youtube channel by searching for TechnicalLeadership or go to https://www.youtube.com/channel/UC_FvZUXWAxjYyMWj99T5qRA
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
In this episode we wrap up our series on negotiation, as well as the first season of this podcast. We will continue with original content in January 2021.
The easy way to say 'No' is by using non-confrontational 'what' or 'how' questions. There are some useful side-effects to this approach as well, that will help you build trust while saying 'No'.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
We're often told to compromise with others to get things done. For an FBI hostage negotiator, there can be no compromise. In this episode we learn how tactical empathy can get results without compromise.
This episode is part 4 of our negotiating series, inspired by the book "Never Split the Difference" by Chris Voss.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
I'm agreeable by nature, and getting folks to tell me 'no' is uncomfortable. But it yields results. In this episode, we discuss the 3 flavors of 'yes', and how to make your counterpart feel in control by getting them to say 'no'.
This episode is part 3 of our negotiating series, inspired by the book "Never Split the Difference" by Chris Voss.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
Labeling negative emotions defuses them. This episodes is part 2 of our negotiating series, inspired by the book "Never Split the Difference" by Chris Voss.
Labeling is an important tactical tool to remove obstacles. Often, its negative emotions about a situation, that prevent a positive outcome. To be successful, a negotiator needs to deal with fears, concerns, anger and other fight-or-flight emotions to establish a rapport, so that the negotiation can continue. Labeling is valuable in work and home situations and can be practiced in virtually every conversation.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
A team that is divided, requires good leadership to repair. The first steps are to be curious about what is going on, listen to people's perspectives and ask questions. Don't push your agenda. First seek to understand.
Listening and understanding others doesn't put an obligation on you to take an action. You don't need to compromise your values by listening to others. Once you can fully understand and appreciate the opposing perspectives, you'll be in a better position to align on an action. Taking action too soon can lead to more division.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
The saying goes that "the best time to plan a tree was 10 years ago. The second best time is today".
Sometimes we don't start an activity because we feel that we should already have achieved the result. Our judgmental attitude to our starting point stymies action. But without action, there is no progress.
In these situations, we need a mindset shift, to measure the improvement and not the end result. Judging the fact that we didn't plant a tree 10 years ago will not help the earth have more trees. But looking foorward to having a seed in the ground, will get us to plant more trees. This simple change in mindset will have extraordinary long term consequences.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
Welcome to the technical leadership podcast. thank you for joining me on a journey, to discover and distil the technical skills that successful leaders have used to lead others forwards towards the future.
In this podcast we search for practical leadership skills to help us lead ourselves and others towards a brighter future. Together, we will learn to be better leaders, by evaluating leadership skills and behaviors, learning from the experiences of others and practically applying those techniques to our lives.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
Knowing yourself, your goals and desires, is the first step to taking a decision to lead yourself towards your goals. In this episode I discuss a turning point in my life, where I decided to pursue avenues to becoming a leader, rather than wait for the opportunities to be handed to me.
twitter: @nico_gevers
email: hello@nicogevers.com
support this podcast on patreon: https://www.patreon.com/technicalleadership
As a leader, you will receive reasonable and unreasonable requests. In this episode we discuss identifying and dealing with unreasonable requests by diving to the core of the challenge and asking the question "how am I supposed to do that"
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
This episode talks about the importance of defining and articulating the definition of done, to avoid surprises. You can use 2 communication tools: 1) Have the other person tell you the definition of done and 2) explain the test you will use to measure 'done'. Don't be embarrassed asking questions to which you know the answer.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
Uncommunicated expectations can lead to frustration. In this podcast, we consider 2 frustrating situations and how each requires a different approach to see it resolved.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
Frustration can be an early warning indicator, like a check engine light. This part 1 (of 5) of this miniseries, we will talk briefly about frustration.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
When reporting information to your leadership, you need to be precise, concise and give advise.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
Decisiveness is a foundational trait of a good leader. In this episode, I talk about my first manager, who wasn't decisive. I mention 4 areas in business that require decisiveness: Work-life harmony, priorities, standards and feedback.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
Where do you start when you want to be a leader?
Start with taking responsibility for your own life, and lead yourself towards your goals. Then use those skills to start leading others. In this episode, I tell the anonymized story of Joe, who changed his career from being a pirate hunter off the west coast of Africa to a software developer in a global company.
We explore 4 leadership traits he possessed: Vision, planning, humility and learning.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership
There's a constant tension between delivery and quality. In this episode we discuss why deadlines and quality standard exist, and give you an understanding of how to use deadlines effectively, and when you should move a deadline for the sake of quality.
Join the conversation on twitter by using #TechnicalLeadership, or including @techleadrship in your tweet.
You can also practically support this podcast, by joining our patreon community https://www.patreon.com/technicalleadership