Hidden Stuff in Your Halo
I love the concept of the product halo. Essentially, a “halo” consists of all the items that actually go into making sure your product is a product / complete solution as opposed to just code, or some widget. In my mind, widgets are not products — the “product” is the widget + all the other stuff that goes around it. But, I digress.
Anyway — I was just working on a product strategy document, and realized something. Your halo does not only consist of things that are right in the customers face. A good example would be documentation - it’s key to the halo, and pretty up-front in terms of customer interaction.
There are plenty of little things that flesh out a halo, like the feedback loop.
If you truly are market driven, the halo must consist with ways in which your market segments can get their feedback to you so it can be taken into account, and ultimately acted upon when key things reach a critical mass.
I just wanted to get this thought down; it might not make any sense, but hey - what else are blogs for if not writing down thoughts that don’t make any sense.
