A few days ago I posted this question over my Twitter stream, syndicated to my Facebook account. I got a few responses:
Recently, we had made an internal release at my current company of a new version of our flagship product. The version introduced some prominent user interface related improvements, along with other core improvements. The usual way we introduce a new version is by sending an e-mail to all internal users, highlighting important, and enlisting other changes introduced. The e-mail ends with a link to the internal Wiki, that has more detailed information as well as further links to the setup / update builds. Being a small group, we also arrange a subsequent demo / one-to-one meeting with each internal user to explain the new features and take 'instant' feedbacks.
Time and again, I have observed a few things:
All these observations are either solitary or statistically in-significant to make any far-reaching conclusions. But they are definitely pointers to me to curate the way I work in product development. I would definitely love to hear from more experienced people of their thoughts on the same.
Obligatory Note: Although the current post directly relates to my day job, this post and its contents is in no way endorsed by my current employer and is solely my personal view point.
Recently, we had made an internal release at my current company of a new version of our flagship product. The version introduced some prominent user interface related improvements, along with other core improvements. The usual way we introduce a new version is by sending an e-mail to all internal users, highlighting important, and enlisting other changes introduced. The e-mail ends with a link to the internal Wiki, that has more detailed information as well as further links to the setup / update builds. Being a small group, we also arrange a subsequent demo / one-to-one meeting with each internal user to explain the new features and take 'instant' feedbacks.
Time and again, I have observed a few things:
- People almost always do not read the e-mails properly. At-most this is what they do:
- The e-mail has come from me
- The subject line says 'updating ... ' or 'new ...' (don't even care to read the version number, and sometimes even don't care whether 'update' or 'new' is mentioned)
- Skip the mail straight to the Wiki link
- And click straight on to the Update / Setup link
- Continue using the product as usual, oblivious of the fact that there are tons of improvements we added (and which I meticulously mentioned about in the e-mail!) to make your life easier
- Shout at me if something goes missing (OK, I made that up ;-))
- In the subsequent demo / one-to-one meeting
- 'Oh that's a cool feature..', 'That's very useful..', 'You removed this feature??!!', 'Oh this way is better!', 'You suck, how can you change the way I work?'
- And, at the back of my mind, I am always thinking : I listed all this in the e-mail I sent you before. Sure, a demo is more engaging, but I thought people always read my e-mails, as obediently as I read theirs!
All these observations are either solitary or statistically in-significant to make any far-reaching conclusions. But they are definitely pointers to me to curate the way I work in product development. I would definitely love to hear from more experienced people of their thoughts on the same.
Obligatory Note: Although the current post directly relates to my day job, this post and its contents is in no way endorsed by my current employer and is solely my personal view point.