Force of Good

Management Risk

Dec 04, 07 in Startups   6 Comments

Over the weekend about 20 co-founders of Atlanta Startup Weekend, the creators of Skribit, got together to move the product to the point where we could extend the number of beta users in the wild. 

My biggest task during the day was to give a presentation over lunch about the state of the corporation and what I termed "Startup 101".  This included a discussion of the four generic categories of venture risk.   I thought it would be good for the team to think about these risks in relation to Skribit to understand what it might take to make the company successful.

One of the risk factors that we discussed was management risk.  When I told the group that I felt like the company's management risk was extremely high people were aghast.  The comment that stuck in my head was "we have more then 20 people here, we have more then enough to handle any situation that may come up."  True enough. 

But more people is not necessarily a good thing.  Management risk might be defined as the probability of the venture failing to meet its business objectives due to not having the people with the appropriate skills in leadership positions or due to poor teamwork.  Management risk is about both skill and teamwork.  You have to have both to reduce it.

As an example, when Fred Nixon, Vince Zappa, and I were working on the Alele concept, we were perceived as having relatively low management risk.   We had worked together at a successful startup for a number of years and our skill sets were rather complimentary, containing what is needed to get a startup off the ground.  The feedback we heard from investors was "We like the team."

Conversely (not to pick on all the good folks that helped bring Skribit to life, they have done great work), 49 co-founders who have never worked together as a team, regardless of the amassed skill set, has a high degree of management risk.  The teamwork aspect is a high hurdle.  Coordinating the effort of that many people is difficult.  The 20 we had over the weekend is much more efficient than 49 but still too many.  Don't get me wrong.  Having 20 people that want to stay actively involved in the project is fantastic, I have achieved the goal of bringing together a segment of the Atlanta startup community.  But as the concept moves forward a core team is going to form in some manner to remove the management risk.  The founders are smart, they will figure this out.

Before the holidays hit us I intend to do a brief writeup on the other categories of venture risk.

Comments

Lance,
I think my confusion with the ranking was the timeframe we were talking about. I think I was looking at only the next 6 months since I personally believe that if we can prove some of the market/business model assumptions then the rest of it can be figured out.
I know its early but I haven't seen any significant ego/management problems that would suggest that the skribit founders would have a problem with putting together a low-risk management team. At least for me all I want is the opportunity to learn from (and possibly help) the process of Skribit growing up.
But in light of your discussion I do agree that to get to success we have to figure out how to turn a collaborative, loosey-goosey, fun weekend project into something structured and run like a real startup.

Michael Mealling  |  Dec 04, 07 at 09:31 AM

Just to be clear, I haven't seen any significant management problems either and have all the confidence in the world that the founders will figure this out.

Lance  |  Dec 04, 07 at 10:14 AM

I agree. Too many cooks spoils the brain surgery. I think the problem you face in limiting the size of the group is that no one wants to be left out. Especially in light of the fact that there was talk of diluting shares of future non participants. One problem is lingering confusion about the separation of the two entities, ASW and Skribit. I think to accomplish your goal of continued community while reducing the size of the skribit team is to emphasize the fact that one can remain an active member of ASW without working on Skribit exclusively. ASW could work like an angel group that invests sweat equity instead of money. That way there can be a ready pool of resources when needed without the expectation of all attending parties to participate equally.

I propose a regular weekend meeting time where we all can discuss topics of interest to the community. During this meeting the Skribit management team could ask for volunteers to help with certain aspects of the project. Also, we may consider a long term project that may be more community based and not profit driven to combine the experience of actually working on something(instead of just talking) without the pressure of everyone trying to get a cut.


Ray Abram  |  Dec 04, 07 at 10:31 AM

How is managment risk calculated? What sort of elements are involved? Can you recommend some reading on this?? I am in the process of starting a company with a partner and this is something I have thought about.

thanks!

Mike W  |  Dec 04, 07 at 05:01 PM

I have never seen much written on this or anyone actually calculate it. I believe that the things folks typically take into consideration are:

1. Individual domain expertise
2. Individual startup experience
3. Individual industry experience
4. Individual capability and intellect
5. Combined team experience in all of the above
6. Team dynamics
7. Previously shared team experiences

Any VCs out there want to jump in on this one?

Lance  |  Dec 04, 07 at 05:15 PM

Management risk is what I work to reduce. My whole business model is built around the people aspect of early stage growing companies. I'd be happy to sit down with anyone at anytime to discuss all the aspects and opportunities.

Peter Rosen  |  Apr 21, 08 at 12:37 PM

Post a comment

Name:

Email Address:

URL:

  Remember me?
Comments: