@@ -63,7 +63,7 @@ Clearly, there are examples out there where an organization started as a softwar
The message in this post should not be taken negatively. In fact, what I'm suggesting here is that we should all take a great deal of pride in what we're doing rather than wishing or pretending that it is something else. So here are a few reflective questions and actions that I'm talking about with folks in my organization.
* If you work at a technology company, build the most air-tight, broadly used technology imaginable. If you're a service, consider all of the *abilities and make sure that I as your customer have visibility into all of those measures (preferably through a programmatic interface). Craft an operational model that takes into account how large companies do things like purchasing, support contracts, etc.
* If you're a business software company, be obsessed with that end user. You know, the one that spends have of their day wishing that they could just go back to using Excel. Don't give them any room for those thoughts.
* If you're a business software company, be obsessed with that end user. You know, the one that spends half of their day wishing that they could just go back to using Excel. Don't give them any room for those thoughts.
* If you want to work on a pure technology project and you work for a product company, either a) find an open-source project to work on (I hear there are a few looking for good contributors) or consider trying to move to a technology company. Don't risk your customers' happiness for your own personal ambitions.
* If you want to work on a product but you're working on more of a pure technology, I've found that working on internal process optimization projects can sometimes help scratch that itch. Otherwise, consider moving to a product company.