Showing posts with label judgment. Show all posts
Showing posts with label judgment. Show all posts

Sep 17, 2012

A rant. Do you, or don't you? Founder Institute. How to approach resources.

Okay, so this entry is a bit of a rant.  Topic: "Do you, or don't you?"  Or how do you know or decide what's next for you?  Or reflections on using resources.  Basically, you got in.  Now what?

Here's something I often don't hear ... "Congratulations!"  An acceptance letter from Founder Institute inviting me to join its Fall 2012 SV semester class.  And they are asking me to make up my mind by tomorrow - 9/18/12 [1].


Usually, it's the "I'm sorry" letter.  Like the one after our Y Combinator interview Summer '12.  'You're good, but no dice!'  (So it goes - learning to take rejections gracefully is part of the journey - enjoy it!)


This feels a lot like B-school apps a few years ago. Got into the Darden School, rejected by others.  Now what?  And I imagine this is a common dilemma shared by other (inexperienced) entrepreneurs.  You got something (a resource), but how do you know if it's worth your investment?  And we generally suck at answering these kinds of questions about how something will pan out based on today's decision.


From Nassim's Taleb's Black Swan, Part 2 - "You would expect our record of prediction to be horrible: the world is far, far more complicated than we think, which is not a problem, except when most of us don't know it."  So we suffer from the '(wo)man who knew too little' problem.  And I know this to be true of my life.  Now and then, I catch myself wondering if my life could be better optimized.  How come I can't seem to go in one direction - up and up?


Since no one knows the future, I'm going to frame this as using resources in life.  What is a resource?  In my case, it is that which will help (our company) grow, answer questions, get users, connect to mentors, etc.  So, the useful evaluation is to determine whether FI will be useful or not for (our company).  I'm going to think about it and discuss it with my co-founder.  As a starting point, I have a few hunches about major pluses and minuses.  But, the problem with hunches is that they are almost always wrong.  And what's really needed is a more empirical data to predict the outcome.  More to come.


Some concluding thoughts to a random rant:
  1. Find/create resources.  FI is a resource.  If you don't apply or don't know about it, you don't have it.  Having a resource is the first step.  This mentality is key to creating your own luck in life.
  2. Consider the goal.  Does the resource help you achieve your goal - whether it's power, knowledge, growth, peace, whatever.
  3. Learn to reason with data.  Heuristics are easy, but unreliable.  What you want is data.  For example, I will look to FI alums to see how successful they have been ... an imperfect data point, but better than a hunch.
  4. Action trumps reasoning.  Attend info events or talk to alums to get more data points.  And will FI help me be more active or simply be an academic exercise?  For startups, key is talk less, do more.
-----
[1] By the way, if you don't know this yet, you can always change dates or rules like this one.  If you want things to work for you in life, you need to learn to change the rules to benefit you.  One useful insight to keep in mind is that whoever comes up with a rule is just another human being.  Just like you.  You can talk to them, reason with them, ask them.

May 5, 2010

Groundswell revisited - WSJ article by Jeff Zaslow

"Surviving the Age of Humiliation" WSJ 5/5/10 - Jeff Zaslow.

Interesting article that highlights some of the dangers of social media and not being in control of the groundswell.

I was actually very skeptical about the groundswell reading, but these are some intriguing examples of what is happening in the world. My main skepticism was that only the rich, powerful, and famous are liable for the risks outlined in the reading, and that no one would care to read, let alone write about me.

That said, the masses are just as subject to be the laughingstock of the world.

Case in point: PeopleofWalmart.com

Another point made in the article by one Jonathan Bernstein: "There have always been people whose aim in life was to cause pain to others."

So true.

Apr 16, 2010

Leadership lesson - Case of guest speaker organization

I was part of a 3-person committee for the a Darden student club that organized a speaker event for the entire school. I took on a lot of the leg work, but I had not volunteered to be the lead coordinator. Here were a few of the expected results and actual outcomes (there are not comprehensive).

Attendance goal - 60+; actual - app. 25
Audience diversity goal - diverse groups; actual - narrowly defined group of interested students and faculty

What happened? Few things. One was team leader's fault. But, for me, the more instructive lesson is my own complicity in that failure.

First, the team leader never really outlined all the tasks and timeline very clearly. Often, I would have to fill in and send out tasks to the group and get the thing moving. Questions I have:

- Why did the leader never step up? In that light, what was my responsibility?
- What should I have done? Should I have expended additional efforts to grow the leader to energize and encourage him? Or should I have simply taken over the show? I think in this case, he was my peer, so it was up to me to have said something. I failed to fix the issue.

Next, my complicity. Here are the things that most stick in my mind.

- I was asked to reach out to this speaker. I spoke to him and landed the invitation. But, during the conversation, I was not at all impressed with the guy. I should have said something, but when the team leader seemed satisfied with the speaker, I just held my peace. I think part of the failure of the event was because of this speaker's shortcomings. I ought to have stood up if I really cared and wanted to make this event better.
- As with the team leader's shortcomings, perhaps I ought to have been clearer in my expectations and should have engaged the speaker more directly to ensure the program went well by preparing ahead of the event.

These observations bring me to some troubling questions:
- If you want something done well, do you have to do it yourself? But, if you do, you're taking all the blame.
- In reality, you want your team to perform better - both your leaders and your followers - so that outcome will be better than if you organized on your own. But, energizing your peers who 'don't get it' can be draining. What's the solution? Is there some magic bullet for energizing your peers? How do you do this without losing your own energy?
- According to the GE model, you 1) hire right, 2) then differentiate talent & fire under-performers and grow top performers. Would I have fired someone in this case?
- What if I'm not in a position to fire anyone? So, does it always come back to me?
- Perhaps what was missing was incentive structure and accountability structure. How would one build this amongst a peer group?
- Part of what failed was lack of institutional knowledge. SYs didn't really involve themselves much and they didn't show up. Why? Were they merely testing us or were they genuinely indifferent?

Lessons: There are broader lessons to draw beyond those questions:
1. Don't ignore institutional knowledge. Figure out a away to leverage it and transfer it.
2. Inclusiveness and performance. You want to get others involved and make them perform? Figure out a way to (a) get their skin in the game and (b) make performances clear so that you can differentiate.
3. Judgment. This is a tough one. When your gut tells you something is going wrong. Stop, think, talk about it, and make sure you're going in the right direction.
4. Courage. Failure to choose comes from fear. When a tough choice needs to be made, choose and move forward.

Or perhaps I could have applied a different framework. For example:
1. Planning - create the right venue and select the right speaker; perform stakeholder analysis
2. Design - stay ahead of the marketing plan and get folks involved
3. Execute - lead team and coordinate tasks; delegate