Interesting reads

This is some stuff I’ve read recently and thought of sharing.

The spat between IRDA and SEBI on ULIPs has been ugly and the only victim is the common investor. This article by Jeff Gerth on Propublica shows how such spats are more common (than at least I thought) and lead to sub-optimal outcomes for the common man.

A lot of people get very confused on legal aspects of software licensing. Here is a checklist for buyers which would be useful for entrepreneurs too. Do note its a good starting point but isn’t exhaustive.

We all have had our own frustrating experiences with Corporate IT and most of the time we have just given up for the sake of  “reliability, scalability and security”.  Here is a very comprehensive and pithy rant/counterpoint against the Corporate IT. I like it because it covers it all and makes a persuasive case. Also because James is a CTO with Dept of Works and pensions in UK. He’s arguing for change from inside the heart of the beast!

James is also sharing his learnings from his experiments to monetise his online book. I’ve reproduced below what hit me the hardest but do read the entire article.

Retweets are excellent predictors of Google’s pace at recognising content

Here’s the top line, though: “Pay What its Worth” works less well than the Tip scheme, and I think its because people don’t like having to make a decision on value AND tell me what they think it is. When I told them what the fixed amount was, they were far easier with it.

This is a description of a Facebook based phishing attack conducted by a security consultant for its client as a penetration test. While the consultant makes his points about remedies, I think a crucial point is missed

Another interesting finding is that targeted users will often provide more than one login and password when a displayed page indicates “Under Construction.” Frequently, a respondent will enter a relatively hard password, but with a numerical sequence like Summer1, Summer2, and so on

Isn’t this behavior a result of the security policy of password reset every 3 weeks and it can’t be any of past 5 passwords etc coupled with no single sign on? I think most people have many passwords to remember and to make it easy they end up making up passwords that a computer thinks as “strong” but really is weak for a human mind.

Here are some interesting insights and data from the Mobile world:

  1. Chris Skinner has a very interesting round up of three case studies on Mobile Banking across US, Africa and Japan. India does not figure here but my guess is that in account count though not in deposits or transaction value, India will figure in top 3 within a year. This would be largely be driven by the Financial Inclusion drive by RBI.
  2. Smaato published the March metrics for click through rates (CTR) for different mobile operating systems and the fill rate for the different mobile ad networks. An intriguing statistic is that Android languishes at the bottom on the Global CTR index but zooms to top when it comes to South East Asia. I wonder why?
  3. Some insightful statistics on Location based mobile advertisement from McDonalds in Finland reveal a fairly high CTR on both the advertisement (7%) and the navigation option (39%). While these numbers look good, I’m not sure that location based advertisement would work across categories.
  4. Some insights into the Apps usage for the Middle East Market. My guess is that the users have higher ability to pay than the US users and hence the higher price. Also, messaging’s popularity reminds me of a bluetooth based messaging app which was wildly popular as it was a way of blind dating in a restricted society. Maybe this is an extension

How to Demo your Product

I wrote this originally for folks who were doing demos at Headstart 2009. Cross posted from Headstart.

Headstart is a tremendous opportunity to connect with early users who can give you feedback and also buy. In order to make the most of this opportunity, its important to be ready with a very good demo. Also, the way of doing the demo differs when you’re in a presentation mode vs a stall talk mode. We’ve put together a few pointers below to help you with these. These are based on our own experiences of making demos and of being on the receiving end of hundreds of demos.

Before we get started, some links to great stuff on the web:

Guy Kawasaki

Jason Calacanis

Luc Richard

Irrespective of whether you’re doing a stall demo or on stage demo, these hold true
  1. NO slides, NO co intro: People will ask these stuff if the product hits the right notes for them. This includes co background, founder info etc.
  2. Just start with the best part: Best part is whatever looks the best or is the key feature. Don’t bother too much with login etc. You don’t have to completely reproduce all the steps that the user has to make. The faster you get to an “Aha” moment, the better it is. The idea is to hook the audience.
  3. Canned vs Live: Canned demo is absolutely fine. Keeps things predictable and under control. Canned demo essentially means a local copy of the web software or a movie of the software in use. Live demo has its advantage when you’re very confident of software’s capabilities; just make it interactive. If you’re on stage, use someone who’s recognized by the audience to be the lead user for the crowd. Can even be the announcer if he/she fits the bill for your average user. In a stall, it can be just about anyone. Do make sure that you do the things for the user instead of them doing it since they are unfamiliar with your system – keyboard, mouse etc
  4. Persistent questioner: On stage, the stage manager will usually pass them “so that others get a chance too”. In the case they don’t, it means that they think that the questions have a lot of merit. In such a case take the follow up question. At any point where there is discomfort, ask if it can be taken off line. If you feel that its getting too deep for a public forum, point it out. At the stall, see if others around are interested as well. If yes, engage. If no, take “off line” escape hatch.
  5. Stupid question: Others in audience too know its a stupid question. However, do provide a short polite answer and move on.
  6. Be enthusiastic: A cheery good morning/good afternoon is enough to make the audience come alive for you. Remember Munna Bhai 2 – “Good morning Mumbai”? Its simple and very effective. Similarly show energy throughout the demo through your body language.
  7. Practice, practice, practice: Catch someone from outside your team and do a rehearsal with them. Higher the no of iterations, the better prepared you are. Practice all steps – including exchange of business cards/stage entry
Stall demos: 
  1. Customize: Get the person’s card and see where the interest is coming from. Just ask them. Then modify the pitch accordingly by emphasizing or deemphasizing the features. Be ready to shorten to a few sentences if the visitor is not relevant. 
  2. Collect info: Ask a lot of questions when you meet someone from your target profile. See if you can sign them up as a user. Find what excites them and what’s a turn off. See if they can refer you to someone relevant.
  3. Build redundancy: If one person gets busy in post demo discussions, there should be someone else to take over and continue for the next visitor. Also be ready for simultaneous demos.
  4. Follow up using the cards collected. Be sure to respond to Unsubscribe requests.
Stage Demos:
  1. Stage roles: Only one person presents. Yes, you’ve two or more founders and all have made equal contributions but ONLY one presents. Change overs are discontinuities where you can loose your audience. There should be another person managing the system for the demo. The presenter needs to engage the audience while the other person needs to make sure that the screen is in sync with the talk. Q&A can be by the entire team if needed. For example, only CTO can answer the question.
  2. Double check the set up: Make sure that you do a dry run in the same order as the schedule and using the same equipment as would be used for the demo. If you loose time, it comes from your time.
  3. Feedback: Provide presenter’s email ID on a slide for feedback. People like that instead of “feedback @”