Skip to main content

Agile Entrepreneurs do it by Osmosis

Entrepreneurs learn best by Osmosis


We need role models we can emulate.
Entrepreneurs we can relate to - in Scale, Time, and Context.

Scale

  • We need people who have succeeded at what we're attempting, but not to such an extent that there's a daunting chasm between us.
  • It's easier to see how we can emulate the success of a peer than that of Steve Jobs.

Time

  • The success has to be recent for it to be relevant. - because everything changes: technology, market, consumers, investors, the economy.
  • Many of my advisors who were successful entrepreneurs over a decade ago are now relearning these lessons themselves, - the hard way, while pursuing their next startups.

Context

  • If the success is derived from a context foreign to us, it's hard to see how we can emulate that.
  • Factors contributing to success are often either downplayed or exaggerated, for effect. You need to know the story behind the story.
Don't get me wrong- I'm sure some of you will figure out the right lessons to learn at the right time, and eventually succeed.

But for many of us, it's really about the hard grind - day to day, week to week, month after month, for years together. Before you know, it's been 2 years since you started - with not much to show for it.

Persistence is good, but it means nothing if you're not making reasonable progress. I speak from the experience of spending a decade amongst bootstrapping entrepreneurs in the Silicon Valley:

And that's why Agile Entrepreneurs was created - to help entrepreneurs learn from each other. Osmosis formalizes & facilitates this learning process in a structured way.

Each week
  1. We pick a Topic that's narrowly scoped
  2. Invite a Role Model (AE member or outside entrepreneur) to speak
  3. Entrepreneur shares their experience
  4. We discuss the relevance of their experience to our situation
This last part is what makes Osmosis - and Agile Entrepreneurs - really stand out as an effective tool to minimize the risk of failure and increase the probability of your success.

Sample Topics:
  • Selling your company
  • Getting a Co-Founder
  • Product Management - Going from Requirements to Launch
  • User Acquisition
  • User Growth
  • Monetizing your users
  • Getting your first reference customer
  • Getting money out of closing your first major customer deal
  • Managing cash flow - staying positive
  • Marketing - SEO
  • .. the list is endless

Comments

Post a Comment

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 acceptance criteria, in response to t…

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is.

Allow me to explain.

The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with.

Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria.

Describing all the requirements as User Stories for a decent sized product is rigoro…

To dream or not to dream? How about keeping your mouth shut?

Here's a really nice quote from one of my dear friends in response to one of my dreams.
Between the bigger things you cannot do,and the smaller things you don't want to do,you may end up doing nothing The problem with quotes and analogies is that they are almost always approximately appropriate, but rarely if ever exactly applicable . A quote is by definition a generalization. Also, we are by nature biased with our prejudices, biased by our own very personal and unique experiences, and biased, by nature, against those who are near and dear to us. While we want them to succeed and would eventually be happy if they succeed big, our natural instinct is to "help" them "stay grounded".

I disagree with this helping nature, of course. I can - and will- expound on the virtue of dreaming big and having a big mouth. But that will be another day.

Today I'm going to present a few quotes on the flip-side of my friend's quote. Feel free to add yours to the list…