Methodology : What's in a name?

 

Before I begin, let me explain that the following should be taken lightly.  I'm not going to argue with anyone who takes this too seriously.

I've been a participant in many a conversation about project management "methodologies."  I always twitch- hopefully not noticeably- because I'm a slight bit of a word nerd and this is one of those terms that's often used incorrectly.

Before I argue my point, let me explain why I'm wrong.  The word "methodology" has- depending on your dictionary- evolved to a fancy way to describe a system used to accomplish a specific type of work.  In scientific circles, this is understood as a set of principles used to design a test for a hypothesis.  In other words, the methodology determines the method.  The business world, including project management, has latched on to this term, often incorrectly.  One could argue (and many have) that the PMBOK represents a project management methodology because it describes a set of management tools that, if used correctly, can increase the chance of project success. 

I will grant the use of this term in this unconventional form may be acceptable, even if only borderline correct.  I'll still twitch when I hear it, though.  Here's why.

In the most literal definitions, a "methodology" is a study of methods.  It's an academic exercise.  Most project managers don't actively study project management methods, we practice them.  Sure, we'll read about various methods as a way to sharpen our skills, but we rarely perform actual research (which would require a scientific methodology in order to define how to conduct that research).  

Is "methodology" correct?  Is it pretentious?  Is it cringe-worthy?  Am I just being a jerk?  I don't know.  Leave your thoughts below.