Project Management

Please login or join to subscribe to this thread

What makes more sense, "Project in a box" or "Project Pathways"?

linkedin twitter facebook   Agile   Healthcare   Information Technology  
avatar
Vivek Bhatia Principal| The Bhatia Group Oakland, Ca, United States
Hey all. I'm a mgmt consultant, got sick of clients only doing half of what is needed and me having to explain to the C-level about the impact and loss of not doing the final half. To correct that, I decided to take a few months off between clients and write both a methodology and a full example of artifacts populated with data from a fictitious project, but using a real life example of something recently invented that healthcare companies will be doing in the next several years. (Details once I publish it, that's just the teaser :-) )

This is far more than just a framework, methodology, or case study. It's all of those put together, 80% of what a company needs to succeed (no one thing is ever 100%), with a real life set of information to follow.

I know the PM types would "get" it, but what would make more sense to the C-level? "Project in a box"? "Project Pathway"? Something else?

Thx for any feedback. This thing has taken me weeks to write, I think i'm going batty :-)
Sort By:
< 1 2 >
avatar
Eric Simms Senior Program Manager Baltimore, Maryland, United States
I prefer 'Project Pathways'. Too many PMs believe all that's needed to guarantee a successful project is find the right schedule template, or create all the standard documentation (whether or not they understand its significance). To me, 'Project in a Box' implies a guarantee of easy success, and I believe people will blame your product when their project fails due to their inattention. In contrast, 'Project Pathways' suggests you're providing them the path to a successful project, but they still have to walk it (i. e. do the necessary work) to arrive at their goal.
...
1 reply by Vivek Bhatia
Jul 24, 2018 11:18 AM
Vivek Bhatia
...
great point Eric
avatar
Vivek Bhatia Principal| The Bhatia Group Oakland, Ca, United States
Jul 24, 2018 7:08 AM
Replying to Eric Simms
...
I prefer 'Project Pathways'. Too many PMs believe all that's needed to guarantee a successful project is find the right schedule template, or create all the standard documentation (whether or not they understand its significance). To me, 'Project in a Box' implies a guarantee of easy success, and I believe people will blame your product when their project fails due to their inattention. In contrast, 'Project Pathways' suggests you're providing them the path to a successful project, but they still have to walk it (i. e. do the necessary work) to arrive at their goal.
great point Eric
avatar
Michael Delaney Partner| Delaney Management LLC West Chester, Pa, United States
Projects in Practice sounds good reflects that you are showing how to project manage not just what it is.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Life is a great big canvas; throw all the paint you can at it."

- Danny Kaye

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters