Contenu connexe
Similaire à Mike Speiser Tiecon2008 (20)
Mike Speiser Tiecon2008
- 14. In most startups, there is some key IP that is usually delivered through a set of
algorithms. Yet, most of the effort of a startup is focused on everything but the
algorithm. Take a 20 person company and you probably have 1 or 2 people working
on the core algorithm. Innocen,ve spun out of a pharmaceu,cal firm that wanted to
tap into (now 155,000) scien,sts around the world. Chemists can apply knowledge
about they have learned in their craf to help other scien,sts. Mathema,cians can
help companies solve energy problems. There is a huge amount of untapped
knowledge in great minds around the planet. Let’s tap that knowledge.
So take that Innocen,ve model, but make it self‐service. And make it objec,ve.
Focus only on algorithms. Build a A/B tes,ng plamorm to find the winners. Allow the
atomiza,on of your site so that algorithms can be delivered in a very granular way
(e.g., open up ad targe,ng and let anyone build their own behavioral targe,ng
model). Or use this approach to build a web‐based email product that is spam‐proof.
How about a news site that like Google News, but which delivers an order of
magnitude improvement in relevance.
14
- 19. Why do sites require registra,on? 1. to authen,cate that you are a human, not a bot
(catcha, email confirma,on, etc), and; 2. to collect data about me to garget content,
offers, and marke,ng. Most sites on the web does a terrible job at both.
Personalizer will bring the personaliza,on func,onality of Amazon to the en,re web
with NO REGISTRATION requirements. We will do this by using your data which has
been passively and ac,vely collected – which you have full transparency into – and
leveraging the fact that compute cycles and storage costs are approaching zero.
We could also have quality of service levels triggered by authen,ca,on. For example,
we could have a base level registra,on which would use captcha and email
confirma,on and a second level that ads SMS confirma,on. We could add an
electronic two factor authen,ca,on token, which would remove phishing aGacks.
Taken together, you would get a massively personal and safe web experience with NO
EXTRA WORK!
19
- 30. Once you launch a product to the world, it’s hard to un‐ring the bell. Conven,onal
wisdom says that you should launch to the world as quickly as possible, because that
is the only way you can learn. But what if you learn that your hypothesis is wrong?
What do you do?
Get your product to a state where you believe that it’s at the minimum level required
to see if your hypothesis if right. Launch it to a small group (100?) of friends and
family and let them know that you need their help to test your product. Whatever
they do will likely be lost. Giving your product team the flexibility to toss everything
and start over, or even giving engineering the flexibility to build the next version
without having to be backward compa,ble with the last version if a massive
advantage. Do this over and over un,l you feel like you’re ready. Then launch the
product to the world and understand that you need to support your customers as you
evolve your product.
Big companies wait to long to launch, launch to a huge audience, and then give up
before the product team can learn from the experience and iterate. This is
par,cularly true with community products which take ,me to evolve. Startups launch
to the world too quickly and then lose some of their natural advantage of flexibility by
inheri,ng backward compa,bility.
30