Skip to main content

Strategy and Pragmatic Marketing's Framework

Pragmatic Marketing has a framework for creating and marketing successful, market-driven products. A grid familiar to many product managers and marketers depicts an overview of the framework:

The left side of the grid shows the more strategic marketing activities, while the right side of the grid shows the more tactical marketing activities. On the far left side of the grid, we find research activities such as understanding market problems, the competitive landscape, and distinctive competence. On the far right side of the grid, we find presentations and demos, sales or other "special" calls, and event and channel support.

The grid is an enormously useful tool for finding the gaps in your company's marketing efforts. Most of us who have taken Pragmatic Marketing classes know that most companies are severely deficient in the left side of the grid. They either have no coherent strategy or have developed strategies without a thorough understanding of the market.

Does your company have a marketing "strategy gap"? Here are some questions to ponder:
  • Has anyone at your company interviewed (not on a sales call) a broad cross-section of prospective customers one-on-one about the challenges they face?
  • Is there a shared understanding in your company of the top three problems your product solves in the marketplace?
  • Has anyone at your company conducted win/loss analysis, with someone other than a sales person interviewing prospects who opted to buy or not to buy your product?
  • Is there a shared understanding of the strengths and weaknesses of each competing product as they are perceived by prospective customers in the market?
  • Has someone identified, and is there a shared understanding of, a competency that sets your company apart from all of the competition and gives your company a unique and sustainable ability to deliver value to prospects in the market?
If you answered "no" to any of these questions, then you have gaps in the most fundamental strategic aspects of your product development and marketing efforts.

Comments

Unknown said…
The absence of strategy becomes even more apparent in agile organizations when the product owner attempts to use opinion instead of market facts to prioritize the work.

When people talk about titles, I point them to the framework and ask, "who owns these activities?" In too many cases, the answer is "nobody."

Use the Pragmatic Marketing Framework to identify all the tasks for defining and delivering products to market. Then assign those tasks to titles.
Tue Aug 25, 02:01:00 PM 2009
Post a Comment

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos
32 comments
Read more

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware
8 comments
Read more