Personality Patterns of Problematic Projects

48 personalities that cause software development projects to fail.

Product Managers

  • The People Pleaser – A Product Manager who believes their core job responsibility is to seek concessions and compromises between the development teams and stakeholders.
  • The Scope Wiggler – A Product Manager who bypasses change control and impact analysis by presenting a big requirements change as a series of small changes distributed over time.
  • The Patent Author – A Product Manager who produces such a high volume of requirements documentation that it creates a barrier to adapting to change, as the documentation must be kept up to date.
  • The Napkin Sketcher – A Product Manager whose requirements are so vague that the development team must fill in the gaps, only to be told their decisions were incorrect.
  • The Executive Assistant – A Product Manager who only documents what the stakeholders have asked for, but denies access to the stakeholders, such that requirements cannot be negotiated.
  • The Sales Liaison – A Product Manager who is only concerned with meeting the demands of the sales team, giving no thought to a holistic product vision.
  • The Dictator – A Product Manager that rejects any idea that did not come from them.
  • The Scope Creeper – A Product Manager who increases the scope of a project while keeping the delivery date the same.

Designers

  • The Note Taker – A Designer who is relegated to doing nothing more than documenting the ideas of others.
  • The Disenfranchised – A Designer who feels they are powerless to influence the design of the project, and therefore are not providing design direction.
  • The Artist – A Designer who is more concerned with how the product looks and feels than if it does anything useful for the end user.
  • The Professor – A Designer so committed to the science and theory of user interface design, that they ignore the UI requirements coming from the stakeholders.
  • The Distrusted – A Designer who has lost all credibility with the project team, leading to their UI requirements being ignored as they are deemed to be not in the products’ best interest.
  • The Blueprinter – A Designer who specifies every detail of the UI to such a fine level of specification that there is no leeway for developers to choose alternative implementations that can reduce development time.

Project Managers

  • The Meeting Scheduler – A Project Manager who believes all project problems are caused through a lack of communication and coordination, and that copious amounts of meetings are the solution.
  • The Statistician – A Project Manager who is only concerned with establishing lists and checking items off, regardless of what those items are.
  • The Delusional – A Project Manager so out of touch with the realities of the project, that they are representing falsehoods to the stakeholders.
  • The Pessimist – A Project Manager that has concluded that the project will fail, cannot be convinced otherwise, and is vocal about their belief.
  • The Optimist – A Project Manager that has convinced themselves of project success regardless of evidence to the contrary.
  • The Cheerleader – A Project Manager who focuses on making sure everyone on the project is happy, rather than if the project will be successful.
  • The Tyrant – A Project Manager that treats project members with contempt in the name of motivating them to work harder.
  • The Process Obsessed – A Project Manager so obsessed with process, they forget their job is to help the project be successful.
  • The Hoverer – A Project Manager who believes that constantly asking for status keeps people focused on completing their tasks.

Development Managers

  • The Formerly Technical – A Development Manager who was a software developer as some point in their past, leading them to believe their technical opinion in still relevant with today’s technology.
  • The Non-Technical – A Development Manager with no technical knowledge, and are therefore out of their depth when managing developers.
  • The Ladder Climber – A Development Manager with ambitions to advance their career, and sees their development team only as a means to do so.
  • The Peacemaker – A Development Manager who believes arguments are counterproductive, and therefore works to suppress debate of any kind.
  • The Wants-to-be-Technical – A Development Manager who wishes to return to the life of coding, after discovering that the life of a development manager is not for them.

Developers

  • The Diva – A Developer so convinced of their irreplaceability that they adopt an attitude of arrogance that makes them impossible to manage.
  • The Idealist – A Developer is so obsessed with achieving architectural elegance and code perfection that they forget their job is to add business value.
  • The Rock Star – A Developer so talented, so productive, so essential that if they were to leave, the entire project would collapse.
  • The Aspiring Manager – A Developer who has decided that to escape the difficulties having to code, their career path should be one of management.
  • The Hostage Taker – A Developer who has written a piece of mission-critical software, and refuses to let any other developer work on it so that they may remain indispensable.
  • The Bull in the China Shop – A Developer so focused on getting the work done, that they completely forgo any notion of quality.
  • The Incompetent – A Developer who lacks the intelligence or skill to do the job of writing software.
  • The Extreme Underestimator – A Developer who consistently massively underestimates the amount of time needed to complete a task.
  • The Extreme Overestimator – A Developer who has become so afraid of missing their deadlines that they ask for as much additional time as they can get away with.
  • The Soldier – A Developer who does exactly what they are told without questions, regardless if it is the right thing to do.
  • The Technology Enamored – A Developer that is so excited to try new technologies that they will introduce them into the project regardless of if they are appropriate.
  • The Legacy Maintainer – A Developer whose only capability is the maintenance of legacy software, and therefore is incapable of taking on new work.

Quality Assurance

  • The Firehose – A QA who floods the developers with so many bug reports so quickly that they overwhelm the development team with a backlog of bugs they will never finishing working through.
  • The Blamer – A QA who accuses the developers of not testing their work whenever they find a bug.
  • The Alarmist – A QA who has declared that the entire product is of an unacceptable level of quality based only on their first impressions.
  • The Scientist – A QA who spends the majority of time documenting bugs, rather than finding new bugs.
  • The Misleader – A QA who often reports bugs inaccurately, leading the developer down the wrong path as they attempt to reproduce and fix the problem.
  • The Downtrodden – A QA who has been beaten down by developers to the point that they hardly report any bugs for fear of developer bullying.
  • The Random Clicker – A QA who looks for bugs by simply clicking on whatever they feel like.
  • The Flippant – A QA whose bug reports are so passive aggressive that developers interpret them as being rude.

Having a problem with a Problem Personality? I offer Coaching for you or for them!

9 thoughts on “Personality Patterns of Problematic Projects

  1. Hi Neil,

    I ran across your site, and subsequently this book after watching your talk on CoffeeScript vs TypeScript vs ES6. Super good talk by the way! Since this post didn’t have a date on it, I was curious to see if you had a time frame in mind that your book may be available. I am eager to grab a copy to share with the folks at work. Thanks.

    CD

    Like

  2. Enjoyed reflecting upon the ideas of these personality patterns. Something to keep in mind, for one’s self as well as the people working for them.

    Like

  3. Very insightful. Thank you.

    It would be nice to have a final description in each section that represents your ‘ideal’ for the role, but maybe it’s too situationally dependent.

    Like

    • I’m glad you liked it. I’m toying with the idea of wrapping this content in an actual book (Kindle & Audiobook). Talking about the ideal characteristics for each role could go in there. Then again, *this* was supposed to be an eBook, and I decided to release it on my blog for free. I’ll keep it in mind…and try to think of what my ideal would look like for each role. FWIW, my thought is that it’s not very situationally dependent.

      Like

    • Thank you! Generally, I have been influenced by Robert Greene’s works, but it was a pure coincidence when I tallied them all up that there were 48 personalities. My biggest influence for Personality Patterns were the Jungian archetypes as expressed in Myers-Briggs tests.

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s