top of page

Chapter 1: Initiation

Geek leaders are challenged to deliver results in a complex domain that is prone to failed projects.  I explore this challenge in Chapter 1 and provide an overview of the book. 

Chapter 2: Why Geek Leadership is Different


In this chapter, we examine the definition of a leader and the challenges geeks face in leadership roles.  We explore the Information Technology industry, taking a look at failed IT projects.  We expound on the leadership potential that is intrinsic to geek leaders.  A sample graphic from this chapter is at the right.

Chapter 3: Emotionally Intelligent Communications

Good communications is essential to effective leadership.  Helping geek leaders to communicate with emotional intelligence enables them to connect with their team members, their management, and their customers.  In this chapter, I introduce the “Missed Signals” use case, which is based on a couple of actual events.  Then, we describe three building blocks: 1) emotional intelligence, 2) the Communications Cycle, and 3) the basics of reading body language.  A sample graphic from this chapter is at the right.

Chapter 4: Self-Leadership

I begin this chapter with a use case that describes a challenging self-leadership situation.  I then provide tools to help the geek leader discover himself or herself and to define the type of leader he or she would like to be.  Then, I explain how the geek leader can “rewrite their code” and take incremental steps to become the leader he or she needs and desires to be over time. 

Chapter 5: Followership

Followers must accept being led.  In Chapter 5, “Followership,” I present a use case describing a situation where a geek leader has trouble obtaining support from her followers.  I describe what it means to be an effective follower and the relationship between effective leadership and effective followership.  We will discuss the leader’s responsibility for resolving conflicts among followers and for creating synergistic solutions. 

Chapter 6: Personal Credibility


A geek leader without personal credibility will be frustrated and ineffective.  In Chapter 6, “Personal Credibility,” we discuss the importance of being an organized leader.  We discuss the meaning of acting in a proactive manner.  I will introduce techniques for prioritizing initiatives.  We discuss keeping commitments as an essential element of leadership is accountability – accountable geek leaders prevent IT project failures.  A sample graphic from this chapter is at the right.

Chapter 7:  Project Leadership Systems Integration

In this chapter, we bring it all together with an overview of the CompTIA Project+ project management life cycle and product life cycles.  Systems integration in this context means integrating IT leadership into the project management life cycle.

Chapter 8: Closeout

In this chapter, we finish our examination of geek project leadership, where I present a business fable about a CEO facing the challenge of injecting leadership into the project management practices within his company.

bottom of page