Skip to main content

Are you a Predator?

While searching for a metaphor for "Entrepreneur", I came across this very interesting blog by Tom Evslin:

Entrepreneurs Are Predators

Predators are smarter than prey. Hare-brained is an insult; sharp as a fox is a compliment.

I have an evolutionary theory to explain this (full disclosure: except for reading voraciously on the subject, I am totally unqualified to have evolutionary theories). 

A leopard chasing an impala can make a mistake, lose the quarry, learn from the mistake, and hunt more wisely on another day. If the impala makes a mistake, it becomes the leopard’s lunch. 

Predators fail often; 
Prey fail only once.

So it would be a waste of energy for prey to have a large analytical brain or to divert any resources into learning while running away. Better just to have long legs, good ears, and a healthy paranoia. 

Thinking could be fatal. 
It also doesn’t take a lot of smarts to eat grass.

On the other hand:

Predators learn terrain; 
they can learn the habits of prey they’ve never seen before. 
They learn where to wait patiently and when to pounce. 

The play of kittens and cubs is as important to the development of their brains as it is to their muscles and their reflexes. And the play is full of stumbles and pratfalls – learning experiences, in other words.

I’ll bet tyrannosaurus rex was a genius compared to brontosaurus.

If you’re starting a new company, especially a new company that’s going to do something new, you have no idea what you’re getting into. 

OK, you’re prepared for the long hours, the lack of a steady salary, the need to raise capital; 

but are you ready for all the mistakes you’re going to make?

Comments

Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint: Manage Unfinished Work - Split user stories ( new link ) Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):   This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying accept...

Agile Entrepreneurs Manifesto

The  Agile Manifesto  defines the 4 core Values that define "Agile":  " Individuals and interactions",  " Working software",  " Customer collaboration", and  " Responding to change" As I applied Agile requirements (user stories), engineering (XP), and process & project management (Scrum & Kanban) to my startups  (RideStation, and Agile Entrepreneurs)  starting from 2005 to now in 2018, I learned numerous lessons and shared them with my fellow entrepreneurs for the next dozen years. These lessons I have incorporated by "extending" the Agile Manifesto with two additional values pertaining to  Product (5th) and Startup/Business (6th)  -  that the services consultants who wrote it in 2001 probably didn't have to contend with as most (all?) of them were not founders of product startups:  "User Validation, Customer Traction, and Business Milestones" Agile Entrepreneurs Manifesto Us...

User Stories for Product Managers

I've previously said that User Stories are the most powerful construct in Agile methods, more than TDD, in my view. The challenge in using User Stories though lies in the fact that they shift the responsibility of getting things right - and quite fairly I might add - from the Engineering team onto the Product Owner/Product Manager. And unless you have strong buy-in from management, it's difficult to make it to the end of the Product Management process and to a point where you're cranking out iterations one by one. The key lies in efficiency in creating and managing User Stories, and tying them effectively to an evolving User Interface even as the product starts coming alive. I'm planning to share some of my experiences and thoughts on this soon. Meanwhile, I found this interesting article while searching the net for splitting stories along CRUD capabilities. Ways to split user stories .