Five practical rules on strategy and execution

I am often asked about strategy, execution and the relationship between them, and I ended up explaining the issue in an e-mail today. After reading the e-mail again, I figured it was generic enough to be widely shared, so here goes…

Rule # 1- No need for “VP of Strategy”: strategy is so well embedded in the organization operating system that outsourcing it to a VP of strategy is hardly ever a good idea. The rationale is clear: when you are not making/selling/marketing anything, your strategic ideas will dwindle or become disconnected from the company reality. Say you promoted your bright director of product marketing to be the VP of strategy—sooner or later she will lose the source of inspiration she had, which was the constant work with customers and partners and the actual creation of the product and will not be able to impact strategy as she did before.

Rule # 2- Strategy is the business of the CEO:

Is SaaS For Me? (Part 2)

Last week I wrote the first part of the Is SaaS for me post. It talked about two important distinctions of the SaaS model: It changes the power play between the customer and the vendor and assures that the vendors work for the customers every day. This part will cover some more distinctions like simplicity, security and maintenance.

Is SaaS for me? (Part One)

People write a lot about SaaS and focus on the famous “no-software” phrase that Marc Benioff coined. What many people fail to discuss is that the SaaS model, even if one ignores the products themselves, brings real value to customers and puts them in the driver’s seat for the first time. So for once, let’s not talk about technology or delivery mechanisms, but rather focus on the change in the most basic rules of the game that the SaaS revolution is creating, with or without a planning hand from the SaaS companies side. Most of this change is affecting my favorite segment, the Small and medium businesses (SMBs), so let’s talk about how SaaS impacts the way SMBs treat IT.