As an individual contributor, Joe was praised by his management for his speed in delivering results. His management was so enamored with his ability to get things done quickly that he was promoted to a leader role over a team of ten. Joe’s speed in taking action carried over into his decision making. He saw making decisions fast as a sign of getting “real work done,” versus sitting around talking about things. “Great leaders don’t have all the facts,” he would say to his team, as justification for moving forward without a good understanding of a decision’s implications. Joe’s team learned to just say, “Yes, Sir,” and do their best to execute what Joe wanted done by the time expected. His impulsive decision making came to a head with a new hire named Greg.

On the 1980s HBO show Not Necessarily the News, comedian Rich Hall created Sniglets, which dictionary.com defines as “any word coined for something that has no specific name. Words like Jokesult (When someone insults you, you call them on it, and they say, "It was just a joke.”) and Chwads (discarded gum found beneath tables and countertops) were born to humorously explain commonplace things or actions. I’ve created 20 of my own project management and leadership sniglets; some made up words, others repurposed words or phrases. I hope they resonate with you and put a bit of humor in your day.

In a recent phone call I told the CEO of my insurance brokerage that after being a loyal customer for 15 years I had moved all my business to other providers. Given our long-standing relationship, I felt I owed him an explanation; not because I wanted to see someone fired, but because I wanted him to know my reasons for leaving so he could put any lessons learned to use.

It started about seven years ago when the person assigned to my business insurance seemed to lose interest in me. He wasn’t on top of my renewals, made me do work that he could have done for me, and didn’t competitively bid my insurance. I moved all of my business insurance to another agency. A similar issue happened in the past year with my personal insurance; I simply didn’t feel that I was important to my agent. The final nail in the coffin came when my bank notified me that my homeowners’ insurance had lapsed two months earlier without any notification from my insurance agent. I then reached out to another agency, who quickly bound coverage for me at 10 p.m. on a Saturday evening.

Some time back I wrote about 4 Ways Your PM Career Sustainability Can Go Wrong. In the article, I introduce the concept of career sustainability and the importance of running as if you were in a marathon versus a sprint. The article focused on four fictional but realistic characters:

1. The Staunch Waterfall Advocate (Stan)
2. The 24/7 PM (Trish)
3. The CEO (Jerry)
4. The Shrewd Salesperson (Alex)

Each of the characters had some successes, but also had some blind spots that impacted their sustainability in their respective jobs:

• Stan with sustainable skills
• Trish with sustainable lifestyle
• Jerry with sustainable relationships
• Alex with sustainable stewardship

I’m a strong advocate of career sustainability. I believe that skills, lifestyle, relationships, and stewardship are key drivers to help you as a professional be more consistently effective and content in your work and play lives. To that end, what follows is a four-part series focused on each driver:

1. Sustainable Skills
2. Sustainable Lifestyle
3. Sustainable Relationships
4. Sustainable Stewardship

Let’s kick things off with the first driver.

Read more at ProjectManagement.com. 

Some time back I was in a meeting with a project manager who presented the status on his troubled project to the project sponsor and other executive stakeholders. This project was of high interest to the sponsor and stakeholders as they were depending on its successful completion to make some major changes in their respective organizations. The project sponsor asked the project manager a very straightforward question:

Why is the project slipping?

The project manager went into a long, meandering monologue. The sponsor interrupted and asked the question again. More meandering from the project manager. Seeing the sponsor and other stakeholders’ growing frustration, the project manager’s boss stepped in and said they needed to do more homework and would come back the next day better prepared. The next day, the project manager’s boss presented the status and answered questions--along with a new project manager.

In 2004, my wife Patty and I decided to team homeschool our autistic son because we knew he would need more help as he entered middle school. I had spent 20 years in corporate America, working for both Accenture and Microsoft, but in the Fall of 2004, I became his part-time math and science teacher, spending the remainder of my time doing business consulting and writing books.

Up to that time I always had either a client or office to go to. With the change to homeschool teacher/author/consultant, I now had no place to go each day. My office was either our playroom where we homeschooled, our home office, or local coffee shops. It was definitely an adjustment and I learned a lot about how to be effective without going to a workplace. Now I can’t imagine it any other way.

A pretty nifty feature in Microsoft Project is the ability to define a project through the use of the project guide.  The project guide is a cool little wizard that walks you through setting up a project, assigning resources to the project, tracking progress, and reporting on progress.  What I like about this wizard is not only the help it gives newbie project managers, but also is a great reminder of the cool MS Project capabilities for more seasoned MS Project project managers.  

To get started with this cool project management software tool do the following:

Talk about your character-building experience...

I was a young hot-shot project manager on an engagement that I had sold to a client.  I had it all planned out and had delusions of completely delighting my client with an issue-free project.  It all seemed so simple, then the project started...and never finished.

I'll spare you the gory details of my harrowing experience but what I can tell you is that I put more focus on selling and planning the project than I did on its execution.  I took a naive attitude of the project being able to pretty much run itself with some junior analysts running the day-to-day aspects of the work.  It blew up in my face and I got booted from the client never to return again.  It was my inaugural visit to the project management guillotine. 

Several years ago, I consulted with a large IT organization working for the VP of program management. This VP and I have a long history of delivering results for more than 25 years. His organization was comprised of program directors with varying levels of project managers working in each program director’s organization. The program management VP had a peer VP accountable for product management. The product management VP also had directors, which included product managers and product owners.

The product management and program management organizations didn’t get along well. There was confusion on role clarity, and a chronic “that’s not my job” mentality. The product managers didn’t think they should be accountable to the program managers, and the program managers had difficulty pinning down what the product managers were—and were not—accountable to deliver.

Shortly after I started my consulting gig, the VP of product management hired a new product management director. In one of his first meetings, which included the program management VP, the product management director referred to himself as “CEO of the Product.”

Read more at ProjectManagement.com.