#projectfail

[finishlinepds]

Top 10 Reasons Why Product Development Projects Fail

[shevonne]

Projects can fail due to numerous reasons. These are six reasons that I have found that projects usually fail. Go to the link in the bio to watch the full video. Let me know if there are others that I missed. #projectmanagement #leadershiptips #projectfail #projectmanager #programmanager https://www.instagram.com/p/CZ2KZwYvPkX/?utm_medium=tumblr

[elmetalpaquienlotrabaja]

-¿A que no hay huevos a entregar el proyecto sin hacer una sola prueba?

-Sujétame el cubata

[sparklemepink8]

Sometimes I try to be crafty ... most of the time I fail 🤣 this is my attempt at water marbling a plastic tray I got for $.75, spray painted white and then water marbled. I suppose it’s not terrible ... but it definitely didn’t turn out the way I had pictured it in my head. I wanted to make a cute Instagram worthy flat lay tray. Are you working on any crafts this weekend ? . . . . #craftcorner #crafty #projectfail #watermarble #flatlay #cheapprojects

[urbangypz]

Maybe it is more of a Where's Waldo look? #knittersofinstagram #urbangypzstudioq #projectfail #fiberartist

[urbangypz]

No. Just no. #urbangypzstudioq #fiberartist #yarn #projectfail

[cal-idad]

Why do projects fail, or why do organizations feel they don't get yield from their projects?

Item 2.  Projects were not data-driven, but "my boss thinks this is a good idea", or we need a "showcase"

Advice is like snow - the softer it falls, thelonger it dwells upon, and the deeper in sinks into the mind. Samuel Coleridge Taylor

While there is likely a wealth of experience to pull from, one person may have a particular view of the world (and how success occurs) versus another.  Any idea , whether it comes from team brainstorming, or individually from your boss, has merit and should be considered.  However, these ideas  /theories have to stand up to what the data tell you.

Multifunctional teams , analyzing data, take the individual "personality" out of this.  Showcase lines are wonderful in that they are advertisements to the employees and managers in your divisions (and others), that change can be a good thing (and this is how you do it!).  However, a showcase, just for the sake of having it (or your next eval), does more harm then good.  It gives a negative experience to the employees or leaders that have to live with it everyday....ie they lose faith, and won't be contributors in the next go around of project work

[cal-idad]

Why do projects fail, or why do organizations feel they don't get yield from their projects?

Apparently I'm getting bored or pissed again....so it's time for me to vent.  In looking back at a few successes (and more than a fewfailures), and more than a few BS sessions with peers past and present, I'vecollected a few observations, as well reviewed similar thoughts from people like Pyzdek. Irregardless of whatever secret society you tend to hang out with (aka LEAN, Six Sigma, LSS, TOC, CPI, etc).  I share a few thoughts and may be some realted quotes

Item1.  Your  project scope may be too big...ie "World Hunger"

All the world is birthday cake, so take a piece, but not too much. George Harrison

Let the gentle bush dig its root deep and spread upward to split the boulder.

Carl Sandburg

Narrowly focused projects will be the most frequently successful (as well as be the most manageable).  They set the stage for Continuous Improvement,  They are also a good springboard to start a process, providing a better understanding of what works (or not), which can lead to something bigger yields later.  They are a training ground for your teams, and can show the "immediate impact" which helps further buy-in from critical persons like your employees (or leadership)..

This is where Pareto analysis does it's magic. Put your money, time, and effort into the "vital few" first,  then understand what can be done next, or if further work is worth the cost in this area versus other opportunities.  Not only is this important for giving your team achievable goals and success, but also lets them prove out what works (and how well ) before you start follow-on projects with the initial prework they successfully built.  Very important when you are talking about limited resources to attack problems

Time is a major part of scoping and planning your goals, and related projects.  Project work often times have short-term "steps" to reach along a long term "path" towards your ultimate "destination".  Your business /operation should map out the points and the path (short term/long term goals) before they plan any projects.....AND they should revisit these goals periodically.