Project Management

The Lazy Project Manager

Peter Taylor is the author of two best-selling books on ‘Productive Laziness’ – ‘The Lazy Winner’ and ‘The Lazy Project Manager’. In the last 4 years he has focused on writing and lecturing with over 200 presentations around the world in over 25 countries and has been described as ‘perhaps the most entertaining and inspiring speaker in the project management world today’. His mission is to teach as many people as possible that it is achievable to ‘work smarter and not harder’ and to still gain success in the battle of the work/life balance. More information can be found at – and through his free podcasts in iTunes.

About this Blog


Recent Posts


New Presentations for 2020

The makings of a legend (possibly) ...

Technology Challenges

The Complex World

The Meaningless Blog

Can I borrow you for a sec because I’m stacked? It will be a win-win situation. I have been blue sky thinking and want to keep you in the loop on my thinking outside of the box, as well as picking your brains, I’m just playing devils’ advocate on this teamwork/dreamwork idea. Will it work? Well how long is a piece of string?

Have I lost you? I suspect I have as the above paragraph includes all ten of the most annoying things people say in the office according to a survey of 2,000 people by recruitment website

Rubbish aren’t they – time for a paradigm shift, we can’t boil the ocean with limited bandwidth but there is low hanging fruit out there so let’s tee it up, circle back, take it offline and do more with less. We need to break the silos to move the needle because it is what it is. What we must do at the end of the day is run it up the flagpole, bite the bullet, peel back the layers of the onion and take it, if push comes to shove, to the bleeding edge. Making sure we are not out of pocket, which is par for the course, let’s get one throat to choke whilst opening the kimono, and synergise as we all drink the Kool Aid. Awesome!

Clearer? I think not, you have no idea what I am on about do you and no surprise. That paragraph included twenty five of the most overused phrases from Business Insider UK. The thing is that they were all once a neat and creative way of expressing a thought or an idea but overuse has made them into at first clichés and then just bloody annoying things that some of our work colleagues roll out regularly on calls and at meetings, presumably because they can’t think of anything intelligent to say instead. Clichés appear to make you connected to what is going on without actually having to have any real understanding or anything of value to contribute. It is like a code that just gets you out of a tricky moment.

Question: ‘What do think of this new approach?’

Answer: ‘You have my buy-in on this particular swim lane, I like the core competency and feel empowered as a result’

Yes, I am back at it again, this time looking at the Forbes most annoying business jargon list.

There are lots of moving parts when you put your best practice ducks in a row and leverage the scalable solution from the burning platform. It is imperative that we drill down and smell the coffee in this one-stop shop because today is the day, all 24/7 of it, and tomorrow, like our children, is our future.

Oh my, it is addictive isn’t it?

So please, be a rock star … and stop! 

Posted on: December 04, 2018 07:01 AM | Permalink | Comments (12)

Project Branding

Extract from my book ‘Project Branding’ published by RMC Publications, Inc.

The project name is important in setting the tone and personality of the project, and this name can be a powerful marketing tool, or even a major part of the brand for a significant project. The name should reflect the overall goals and objectives of the project—what the project is about and what it’s meant to deliver. Over time, people will subconsciously start to link the name to a set of associations they make with the project.

Consider, for example, “Project Phoenix” (how many of those have you come across?)—a good enough name and one that is often selected to show the desire to resurrect or improve some system or other. But (yes, there is a “but” in this case) what happens when the project hits issues? Then the jokes about “burning up” or “going to ashes” or “this bird is dead” might come thick and fast, and the project name becomes tainted.

In short, the project name is a valuable aid to communications inside and outside the project team. So it’s worth taking the time to think carefully about a suitable name for the project. Make sure the name conveys the following:

  • The “big idea.” What lies at the heart of the project change?

  • The vision for what this project will accomplish. Where are we going? What will the outcome be?

  • The principles behind the project. What are the key features/characteristics that will be reflected in the project deliverables?

  • The personality of the project. How do you want the project to be perceived?

Typically a name falls into one of the following four types:

Descriptive: These are names that simply say what the company or project actually does. For example, “Move” was used to label an office move, saying all that needed to be said about what was happening.

Evocative: Names in this category suggest associations with the project or company, but they don’t try to describe it precisely. For example, “Advance” is a project name that evokes thoughts of progress, things getting better, and advantage.

Abstract: These names are unusual (in the context in which they’re being used) and therefore stand out from the crowd. They make no clear reference to the nature of the project. For example, “Blue” was a project name that came about because the supplier’s primary color for their marketing material was blue, but the name eventually came to stand for a brighter horizon/future

Acronym (or abbreviation): These are contractions of a title or phrase based on the first letters of each word. The end result should be a name that is easier to say and recall than the full version, but one that still clearly relates to the organization, project, or item. A simple example might be “RED” (Rapid Enterprise Deployment), a memorable acronym with a suggestion of importance and criticality.

Here are some other tips to consider when choosing a project name:

  • First, when you are brainstorming or collecting ideas for a project name, you will need to filter the suggestions. You will need to imagine the name in various potential moments—both positive and negative—of the project’s future. How will the name stand up at these potential points in time? Will the name work in all extremes?

  • Then, ask yourself if the name is politically correct, and not just in your mind. Remember here to consider the full spectrum of stakeholders, too: both those closely related to the project and those more widely associated with the project. In these days of multi-country, multi-cultural projects, just be careful what you end up with when choosing a project name. The clever acronym that you have constructed in Portuguese or English might well be just that at home—a clever acronym. But in another country, it might just mean or translate into something completely different.


  • Make sure your project name is easy to pronounce. If people can’t say it, then they won’t use it. And make sure it isn’t awkward. Don’t, for example, misspell a word to fit an acronym. You will get fed up with people telling you that you have spelled it incorrectly.

Now, you do need to think through your project name carefully, but don’t overthink it either. Too much can be made of a project or product name, but many great names start out with humble and less thought-out origins. In the biography Steve Jobs, Walter Isaacson describes how Apple founders Steve Jobs and Steve Wozniak discussed many options for company names, including “Matrix,” “Personal Computers, Inc.,” and “Executek.” Jobs, however, had just arrived back from working on a fruit farm. He suggested “Apple” and the rest, as they say, is history.

On the other side of the marketing coin, Apple experienced some issues with the pre-Macintosh PC when it was named “Lisa” (allegedly after Jobs’s daughter). The official company line was that it stood for “Local Integrated System Architecture,” and the unofficial one was that it stood for “Lisa: Invented Stupid Acronym.”

There is a wonderful Dilbert cartoon by Scott Adams that starts with the news that the company has run out of acronyms, and so they can’t start any more projects. They can’t create any new acronyms either, because that would then be a project, and they can’t start a new project because . . .they’ve run out of acronyms!

So don’t push that one too far. Be creative, but don’t constrain yourself by trying to be too clever or to force something out as an acronym.


Posted on: May 20, 2016 07:59 AM | Permalink | Comments (6)

"Don't play the saxophone. Let it play you."

- Charlie Parker