Skip to main content

Strategies or Tactics

A lot of military and political pundits have recently criticized President Bush's "surge" in Iraq as not being a new strategy, but merely a tactic. A strategy is a plan for achieving end goals. Tactics are the details that execute the plan.

Execution is important. But tactics don't matter much if the strategy is flawed or doesn't achieve worthwhile goals.

Are your marketing efforts heavy on tactics and light on strategy? If your company is like most organizations, then chances are you are wasting a lot of time and effort on tactics and paying short shrift to strategy.

Instead of asking tactical questions such as:
  • Who is going to write the next white paper?
  • Who is going to man the booth at the next trade show?
  • Who is going to design our web site?
  • Who is going to design our brochure?
You should first be asking strategic questions such as:
  • What types of people will buy our product?
  • How is our product different from our competitors' products?
  • What are our customers most pressing problems that our product can solve?
  • What are the key themes that all of our marketing campaigns should stress?
Has your company authoritatively answered these strategic questions? Has it even asked them?


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

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