Project Management for the Unofficial Project Manager summary

Author: Kory Kogon
Mindset & Habits Business & Startup Leadership & Management Business & Startups Productivity & Habits Personal Growth
ISBN: 9781941631102
Project Management for the Unofficial Project Manager

Book Summary & Synopsis

What's it about?

This book presents project management as both a technical process and a leadership challenge. It explains how unofficial project managers can lead through informal authority, manage stakeholders and risks, execute with accountability, control scope creep, and close projects by learning from results.

Who is it for?

  • People who manage projects without formally identifying as project managers.
  • Anyone who wants practical guidance on leading teams, planning deliverables, managing risks, maintaining accountability, controlling changes, and learning from completed projects.

Meet the author

Kory Kogon is the author named in the supplied audiobook source.

From the Introduction & First Chapter

Introduction

Project Management for the Unofficial Project Manager by Kory Kogon Mastering projects requires leadership, not just technical skill. We live in a project-based world. Projects have a beginning and an end, and they create something new. In the knowledge economy, they consume a significant amount of workers' time, yet few people identify as project managers.

Most become unofficial project managers instead, often without formal training. The result can be missed deadlines, budget overruns, and a great deal of stress. Research shows that many projects fail to meet their goals. This book offers a five-step process for project success.

But project management is about more than technical know-how. Your ability to lead people is crucial. Without leadership, even a well-designed project can fail. You need to radiate informal authority.

That authority comes from character, not job title. Nelson Mandela and Martin Luther King Jr. inspired millions without relying on formal power. To inspire your own team, you need to act like a leader.

The authors identify four fundamental behaviors essential to effective leadership. First, demonstrate respect. This is non-negotiable for project managers. In fact, the more stressful things become, the more respectful a leader should become.

Bringing lunch for the team during crunch time may seem like a small gesture, but small gestures matter. Second, listen first, then talk. This becomes especially important when time is short. You may think you don't have time to listen, but slowing down long enough to hear people can actually speed things up.

Impatience is often experienced as disrespect, and disrespect hurts productivity. Third, clarify expectations. Many unofficial project managers are too brief. They tell people what to do without explaining why.

Team members can begin to feel their contribution doesn't matter. Show them how their work fits into the bigger picture. When people understand the value of what they're doing, they're more likely to stay engaged. Finally, practice accountability.

Follow the golden rule. Treat others as you wish to be treated. If you're always late for meetings, others will start arriving late too. And if you don't hold yourself to the standard, how can you hold anyone else accountable?

These four behaviors build informal leadership authority. They help inspire others to do their best. Now let's tackle the technical side.

initiating with stakeholders

Initiating with Stakeholders. Every project has to begin somewhere. Unfortunately, many begin on the wrong foot. A plane that starts only one degree off course can end up far from its intended destination.

Consider Eve's project to save lives. Eve is a nurse at a hospital where patients have been developing infections. Instead of getting better after arriving, some are getting sicker. Eve notices an increase in hospital-acquired infections and raises the issue with her administrator.

Together, they decide to launch a project to reduce them. Eve agrees to lead it. The first step is pinpointing stakeholders. Identify everyone involved in the project or affected by its outcome.

For Eve, that includes doctors, analysts, and other hospital staff. Next, interview your stakeholders. Explain the project, then ask for their responses. Gather their opinions, concerns, knowledge, and expectations.

Eve holds a group stakeholder interview. She asks about infection rates and costs, and the group discusses possible root causes. One doctor points out that the hospital's infection rate is about average. Eve doesn't dismiss him.

She shows respect and thanks him for the contribution. The conversation increases everyone's understanding of the problem. Many of the stakeholders didn't know that the infection rate had been rising. Eve, meanwhile, hadn't understood the financial cost of those infections.

By the end of the meeting, they are working from the same information. Eve now has what she needs for the next step.

Table of Contents

Total duration: 12:19 · 6 chapters

  1. 1 Introduction 2:53
  2. 2 initiating with stakeholders 1:50
  3. 3 planning risks and deliverables 1:43
  4. 4 executing with accountability 1:25
  5. 5 monitoring scope creep 2:13
  6. 6 closing and learning 2:15