Project Management

Please login or join to subscribe to this thread

How can we market PMO?

linkedin twitter facebook   Governance   PMO  
avatar
Wai Mun Koo PMO Director| Intergraph PP&M Singapore, Singapore
We know we need to justify the value of PMO. At the same time, creating awareness of PMO and marketing its value externally is equally important. How can we effectively market PMO then? Do note that as much as we would like to market PMO aggressively, we also need to be cautious not to over doing it. The question here is then what are the approaches or tools you would use to market PMO and how to do it effectively?
Sort By:
< 1 2 3 >
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
Mark,

I am oversimplifying marketing with the following statement but, at its core, marketing is understanding what your target market needs, then planning and communicating how you can meet the needs. Are you saying that this should never be done for a PMO?

I read Mark Newton's posting a little differently than you do. Based on his recommendations for engaging Business Units, I assumed that his question, "Why should you have to market the PMO?," was not meant to say don't do it, but to take an analytical approach to discovering your marketing needs. Demand for a PMO cannot be satisfied if nobody knows about the PMO or understands what it does. In my opinion, a PMO should be a service organization that strives to meet the needs of its clients, but it can't be all things to everyone and the clients need to know what services are available. An effective PMO does not just happen. Those involved with the PMO need to understand what is needed and how to meet the needs to be effective. Again, an oversimplification.

I can't fault you if you are speaking to your own experience, but some of us have not worked in the same types of organizations that it sounds like you may have. There are times that I called one of the organizations I worked for pathetic and ridiculous, but it was not because of having to market the PMO; it was because of leaderships attitude toward the PMO and how their lack of support influenced the rest of the organization - call it "negative marketing", if you will.

I think that you make some valid points, especially about the role that executives SHOULD play and the need for objectives. But your statement, "Run the PMO like a business and your problem is solved," seems contradictory. What would happen to a business that did no marketing? PMOs may not need a marketing team to manage campaigns, but every organization, especially service organizations, will benefit from marketing.

Aaron
avatar
Mark Price Perry Business Driven PMO Evangelist| BOT International Orlando, Fl, United States
Aaron, great post and point. I quite like and agree with your context. And no, the comparison to "running the PMO like a business" was not meant to mean running it like a company, rather the comparison was meant to mean running the PMO like any other business department or unit in the company must do. For example, does the Sales VP have to "market/sell or justify the existence" of the sales organization? Typically no, rather they have to meet their business objectives such as sales, profit, customer sat, etc. The same can be said of just about every other business unit in an organization such as HR, Legal, Customer Support, Engineering, Accounting, Finance, Marketing, R&D, etc.

So, if the PMO is established to solve a problem (as advised by the OGC P3O Guidance and others) and the problem(s) to be solved and purpose of the PMO is determined by the leadership team; then solve the problem. In such a case, you don't need to sell them on the PMO, they have already made the decision to have a PMO and told you exactly what they want. Hence, much like the sales organization that is seeking to make their annual objective (as established by upper management), the PMO should seek to achieve its annual objectives (how much by when) related to the mandate of the PMO and the PMO objectives that serve as control measurements against that mandate.


It is when the PMO is set up with no real mandate and supporting Vision, Mission, Goals, Objectives (how much by when), Strategy, Needs, Critical Success Factors, etc, that we then (often) end up having to "sell" the PMO. And to make matters worse, we often end up talking the language of project management - not the language of business. So my point is, if you have the above mandate, then all you need to do (simplification of the work effort of course) is to fulfill the mandate - "run the PMO like any other business unit."


Now if an organization does not have the mandate, if given the choice of "selling the PMO" or "managing the PMO like any other business unit" vis a vie proper business planning, I would prefer the latter. And as a caution to all those that give or follow the advice of "selling or marketing the PMO", I would ask what Sales and Marketing experience and best practice do you intend to utilize - Radar, SPIN, COS, MDM, TAS, Miller Heiman, etc..? If the answer is that you have very little to no sales and marketing experience and you are not familiar with, or even aware of, the various sales and marketing best practices, then all the more reason to NOT engage in selling.


But at the heart of this are some very interesting questions and perspectives. Does a service organization have to sell itself? And, what do we mean by "selling"..? Do we mean reporting progress against the mandate/objectives of the PMO and periodically validating the mandate..? I would agree with that, if that is what we mean by selling or marketing the PMO, though I would strongly prefer to not us those terms.


Or, in the context of a service organization having to sell itself, do we mean trying to justify the existence of the PMO by telling people what a PMO is, what a PMO does, and why they should want a PMO - without first asking what problems the business has for which a PMO of some kind can be address..? It is that approach, often called "selling the PMO", that I would not advocate.


Not to beat the horse dead (especially since there is always a context to such high level discussions in which after lengthy discussions we often arrive at a point of violent agreement), in research that we have conducted over the years, we have seen very consistent findings and perspectives on this "selling the PMO" mind-set:



  • First, those PMOs that are run like other business units in the organization and that have such things as constituent determined Mandate, Vision, Mission, Goals, and Measurable Objectives are typically viewed as highly successful PMOs by the leadership team and in these PMOs there is typically no marketing/selling of the PMO - only reporting progress against objectives and continual validating of the PMO mandate and business plan.

  • Second, those PMOs that are NOT run like other business units in the organization and that do NOT have such things as constituent determined Mandate, Vision, Mission, Goals, and Measurable Objectives are typically viewed as marginal PMOs by the leadership team and in these PMOs there is typically a mind-set by the PMO that the PMO needs to engage in marketing/selling of the PMO in order to demonstrate that it is more than marginal (value) or keep it from getting shut down.


Naturally, there is a context to be considered. At a high level starting point, many folks advocate, and I agree with, a business-driven approach to setting up PMOs in which the constituents of the PMO determine the mandate of the PMO, the Vision, and Mission, and Goals and Objectives of the PMO (their PMO). From that construct, the PMO manager as the servant-leader and subject matter expert develops and executes a constituent approved strategy that fulfills the mandate and achieves the measurable objectives of the PMO. In such a case, the PMO need not engage in selling and marketing of itself. That would not only be unnecessary but likely irritating to the execs as they have already told the PMO what they want and have expressed it in measurable objectives.


It is in this context that I am not a big fan of "marketing/selling" the PMO or even using those terms to describe the work effort involved in setting up and managing a PMO. I suppose this is a subtle distinct to some, but over the years I have seen so many PMOs that have engaged in some form of selling/marketing themselves in lieu of proper business planning that the term "selling the PMO" has become loathsome to me.


Note: if the executives do not want to take the time to discuss what the mandate of the PMO (their PMO) is and all of those things that I mentioned above, I would advocate not bothering with it all. Don't have it to begin with or shut it down.


Again, that context thing, I suspect if and as we continue this discussion further, we will end up in a "kum-bay-a" moment. Great post and replies - I hope we hear and learn from others on this topic..!

avatar
Anne Barks Dallas, Tx, United States
I would throw my two cents into this and agree with the business driven approach to PMO setup and management. If selling and marketing the PMO works, then by all means do it. I would prefer to use the same kind of business planning and acumen that the executives and other line of business heads use.

Also, we in the PM community actually care and make a distinction when referring to PM things such as the distinction between a project charter, a project plan, and a project schedule. When others use these terms interchangeably or incorrectly, we correct them.

So, by the same token, we should be careful to use the correct "business" terms and exhibit good business acumen. Saying things like "selling the PMO" or "marketing the PMO" or in the context of PPM "manage your portfolio of projects like you do a portfolio of stocks and bonds", etc. These are all inaccurate uses of the terms.

As a PMO manager, do you really sell your PMO? Does it have a price? Are you following a sales process? You get the idea, so let's not beat a dead cow.

IMHO, selling/marketing the PMO is the wrong approach (for most organizations). But again, if it works for you, then keep at it..!
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
I am enjoying this conversation and apologize if I come across otherwise.

As a PMO manager, when your resources work on a project do they charge time against another department's cost center? Does the other department need to find value in what they are paying for? Is there a process that other departments need to follow to engage (buy) the PMOs services?

Call it marketing, call it selling, refuse to call it either... Whatever you call it and however you do it, business needs have to be understood and people in the business need to know about the PMO. They need to follow a process to engage the PMO; they won't come just because you build it.

The original question relates to how to build awareness of the PMO and help potential users of the PMO understand the value it brings; whether or not this should be done does not answer the question. If you think Wai Mun Koo is doing it wrong because he wants insight into "marketing" his PMO, ask for clarification. Telling him he shouldn't market his PMO doesn't help solve his problem.
avatar
Anne Barks Dallas, Tx, United States
Perhaps my point was missed, but we are not speaking the same language anyway. What you are describing below, I simply don't agree with. By way of advice to Wai Mun on "Marketing the PMO", my advice is "Don't do it."

Your premise that people need to know what the PMO is and does is a premise that I disagree with, quite strongly I might add. Far more important is understanding the business needs for which a PMO of some kind can address and for which a PMO can be held accountable to meet.

Your comment, "whether or not this should be done does not answer the question" misses the point that I (and I beleive Perry) was trying to make and the answer to Wai Mun's question in terms of an alternative approach to "How can we effectively market the PMO?" Rather than repeat, I think Perry's post clearly states this.

But I would disagree with Perry about whether or not after a long discussion we would arrive at a kumbaya moment of agreement. I think that at a high level there are two distinct PMO mindsets - business driven vs driven by some other rationale. Perhaps this is because I don't view the PMO as a staff-style organization, but rather an accountable business unit with the sames kind of management applied to it as other busines units.
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
Some of us have worked in failing PMOs and have had to borrow principles and practices from marketing as part of the effort to turn around a failing PMO. Some of us have worked for a company where previous attempts at a PMO failed and there is considerable negative opinion about it. Some of us have worked for PMOs with weak leadership from executive sponsors. Some of us have worked for PMOs that were IT centered and are expanding to the business. If this was a perfect world or a hypothetical discussion about starting a PMO from scratch I might agree, but there is no 'one size fits all' PMO. There is no cookie cutter. The world is not black-and-white.

This may sound like I am contradicting myself, but if someone were to say that you should never start a PMO with the expectation that you will have to do a lot of marketing to be successful, I would completely agree. Part of the problem is that there are companies that started a PMO because someone thought it would be a good idea. Or they didn't apply any of the many good suggestions posted by our fellow ganttheads. Sometimes you reach a point where it is too late for the textbook and you can't start over from scratch and do it right.

I don't have anything else to add to this topic, except that I look forward to reading advice from other ganttheads regarding options Wai Mun Koo can pursue to solve his problem. I'm sure there are many other perspectives on courses of action that could benefit hom and the rest of us.
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
Some of us have worked in failing PMOs and have had to borrow principles and practices from marketing as part of the effort to turn around a failing PMO. Some of us have worked for a company where previous attempts at a PMO failed and there is considerable negative opinion about it. Some of us have worked for PMOs with weak leadership from executive sponsors. Some of us have worked for PMOs that were IT centered and are expanding to the business. If this was a perfect world or a hypothetical discussion about starting a PMO from scratch I might agree, but there is no 'one size fits all' PMO. There is no cookie cutter. The world is not black-and-white.

This may sound like I am contradicting myself, but if someone were to say that you should never start a PMO with the expectation that you will have to do a lot of marketing to be successful, I would completely agree. Part of the problem is that there are companies that started a PMO because someone thought it would be a good idea. Or they didn't apply any of the many good suggestions posted by our fellow ganttheads. Sometimes you reach a point where it is too late for the textbook and you can't start over from scratch and do it right.

I don't have anything else to add to this topic, except that I look forward to reading advice from other ganttheads regarding options Wai Mun Koo can pursue to solve his problem. I'm sure there are many other perspectives on courses of action that could benefit him and the rest of us.
avatar
Wai Mun Koo PMO Director| Intergraph PP&M Singapore, Singapore
Everyone,

Appreciate this constructive discussion going on and there are indeed some wonderful points mentioned. I also apologize for not stating clearly what do I mean by 'market PMO'. Thanks Aaron for sharing much of your thoughts and helping to clarify the point which is exactly what I have in my mind. So let me take this opportunity to summarize it a bit.

1. We all agree that the PMO must exist for a purpose and it should has its value. There is no doubt about this.

2. When I said 'market', I was actually talking about creating awareness and helping others to understand what PMO does. This is not about justifying the existence or forming the PMO as this should be done before the PMO is being formed. However, we cannot assume everyone in the organization understands what are the values and objectives of PMO even if these are well understood by the folks on top.

Although I agree with Mark Perry's suggestion to run PMO like any other departments (good point on that Mark) and I also think that this should be the way PMO should operate, I don't think this is sufficient. PMO is not like any other departments like HR, Sales, Marketing and Finance. Not because PMO is different, but because I would consider the term 'PMO' is rather new compare with HR, Sales and Marketing etc. This is a real problem we are facing. People asking what is PMO and what you guys are doing. Do not be confused that the PMO does not have value or no objectives. Yes, we do; just that we do not belong to the traditional business groups like the HR/Finance etc. which are ingrained in people's mind. I believe in most cases, PMO are sponsored by executive management that see the value of having a PMO. But the story shouldn't have just ended there. Like what Aaron has pointed out, many executive managements formed PMO out of the genuine needs to have a PMO to solve some of the existing problems in the organization. What is done poorly is helping the rest of the people below to understand their objectives of setting up a PMO. We can't just force it down people's throat, it just won't work. We should help them understand and realize how PMO can benefit them and the organization (again I am saying we can't assume everyone understand this readily since the term 'PMO' is still quite alien to many people out there).

I believe PMO is not an isolated example; other newer departments like EHS, Operation Excellence, Whatever Council, etc. probably will face the same issue. We have to know that an organization is formed by a widely diversified group of people around the world. Again, the key point here is we should not assume that everyone in the organization thinks the same or able to understand what is 'PMO'. We need to help them to understand and this is a real life problem we are facing.

This reminded me of the time when the term 'IT department' started to come into the corporate scene. In those days, IT departments usually resided under other bigger departments e.g. Finance (yes, those were the days where IT department usually reported to Finance since most of the system used by finance group required the support of IT). It wasn't that the IT team needed to justify for their existence, but rather that most most people at that time really had no clue what IT was all about.

I have written a blog post 'What the Cocks Want?' that describe, in essence, the problem we are facing here. It says that - 'A Cock, scratching the ground for something to eat, turned up a Jewel that had by chance been dropped there. "Ho!" said he, "a fine thing you are, no doubt, and, had your owner found you, great would his joy have been. But for me, give me a single grain of corn before all the jewels in the world."'

It states that the cock pays no attention to anything that it perceives of no immediate value. Here, we can treat PMO as the jewel where its value is meaningful to other people (the executive management) but not to the cock (perhaps the cock has yet to realize what a jewel can do for him). Below is a short paragraph extracted from the blog that pretty tells it all on the problem that I am trying to bring it up here and what most of the discussions below are all about.

"In most global projects, the grand strategies and audacious goals are usually defined by the top management sitting in the ivory towers. However, when all these are cascaded down, they are repeated verbatim to the folks below without considering issues related to cultural differences, process deviations, legislative requirements, as well as local business priorities. This oversight created a gap in stakeholders’ expectation. It is not that the strategies and goals are too elusive and difficult to understand. In fact, the stakeholders do understand but just that they are not able to appreciate the associated value easily. It is like selling ‘jewel’ to the ‘cock’. People are stuck in their tunnel vision limited by culture, position, job scope, knowledge, experience, responsibility and authority etc. Do you really know what the cocks want? If not, what can you do to close this gap?"
avatar
Anne Barks Dallas, Tx, United States
Great insights and posts. Kudos to Wai Mun. This is why I like gantthead. Apologies to anyone I have annoyed... So often a thought becomes a sentence which becomes something much longer. This is why I like these discussion forums, so you can have an online and somewhat immediate and spirited dialog. There is always a context, so seldom is it ever a matter of right and wrong - just idea exchange. And almost always the differing perspectives are far more beneficial than when everyone agrees en masse.
avatar
Harlan Bridges Consultant, Coach, Trainer, Speaker, Program Manager, Project Manager| Entrepreneur Seguin, Tx, United States
As I have stated in my blog, I truly don't believe in selling the PMO. I do however believe in COMMUNICATING to the entire organization. Though the executive leadership knows the value and reason for the existence of the PMO it may be that the remainder of the organization does not. Relying on management to "push the message down" is not always effective

I have found that frequent communication and transparency have replaced selling/marketing effectively in the situations in which I found myself. So I suggest developing an effective communication strategy.

Introduce the PMO to the organization. It is important to communicate the initial goals and areas of focus for the PMO. Inform everyone within the organization of the PMO objectives and explain that achievement of these objectives will be measures of success for the PMO. Use this period of introduction to explain the reasons and impacts of changes to organizations and individuals.

Some of the communication vehicles I have used include:
- forums
- newsletters
- RSS feeds
- Webinars
- Intranet web sites
- Communities of Practice groups
- Internal seminars
- and lots and lots of walking around

Just some suggestions of things that have worked for me in the past. But I found communication to be much more effective than selling/marketing in all my situations.

Good luck!
< 1 2 3 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"I may not agree with what you say, but I will defend to the death your right to say it."

- Voltaire

ADVERTISEMENT

Sponsors