Tag Archive for 'entrepreneur'

Interview with Chris Redlitz from KickLabs and Transmedia Capital (part 1)

26675v2 max 250x250 e1280192038754 Interview with Chris Redlitz from KickLabs and Transmedia Capital (part 1)I recently sat down with Chris Redlitz from Transmedia Capital to talk about his new startup incubator KickLabs and founding teams from his perspective as an entrepreneur (AdAuction, Get Relevant, Aptimus, and On Village), executive (Skyrider, Feedster, Reebok), and now venture capitalist. We discussed what makes a founding team work, potential conflicts of interest between investors and entrepreneurs, and what KickLabs looks for in a company. Chris is also going to be a judge at the Lean Deck Clinic on August 2nd.

T: In your experience, is there a distinct advantage to having a founding team as opposed to being a sole entrepreneur?

C: Yeah, I think so. Especially in technology it’s good to have breadth so to speak. You can obviously take an idea and have it outsourced but from a development point of view, it’s good to be able to collaborate. Collaboration is really the most important thing when you’re doing something. I have an idea but I need to actually have some sort of way to vet that idea as it morphs along the way. Having someone that has a little bit more of a technology capability with someone that is more of a business or marketing person… it’s kind of the ideal situation if you can make that work.

T: So what do you think doesn’t make that work?

C: I don’t think it’s a showstopper if you don’t because there are resources to develop. I think it’s more just, the ability to vet, collaborate, you know, brainstorm. It’s tough to do by yourself. In the short time we’ve been doing this [KickLabs] and looking at companies over the last six months, we’re not seeing too many single people come in. Or if we do, they definitely had the desire to find a team to round out what they’re doing. It’s rare to find somebody that’s doing it by themselves.

T: What are, generally, the types of things they’re looking for?

C: It depends on what their core competency is. So it’s to be able to sort of leverage what they’re doing with a very complimentary core competency.

T: When you say “core competency”, are you talking primarily in terms of skills or roles or do you find that they’re very much the same thing in this context?

C: Yeah, as a founder, it’s less about title or role. It’s more about what my skills are to bring that idea to more of a real tangible product. If someone is a little more business-oriented and methodical about their approach and someone is a little more of an idea person that’s probably a good match, right? If you get too many people that are idea people, nothing ever gets done. So I think you really need to have that sort of very complimentary skill set.

T: So would you say that the primary qualities you look for in terms of finding people both for KickLabs and teams to invest in is complimentary skill sets or are there other qualities such personality types or shared vision that you think are also critical?

C: If you’re looking to accept a company [into KickLabs] or do an investment, what are we looking for? Is that your question, yes?

T: Yes.

C: Ok. It’s a little bit different here, because we’ve got an open environment. As opposed to looking at strictly a company to invest in from a business model point of view and an entrepreneur and stopping there, we have to take that a step further. Because now we want a personality that would fit in, not to sound trite, but people either they want to work in an open collaborative environment or they don’t, and they either add value or they don’t. It’s kind of binary in that sense.

It goes beyond the normal evaluation of doing investment because you have to “live” with the people, You made the chicken reference: [note: Chris and I discussed his interest in chicken farming before I turned on the recorder] every time you enter a new hen into the coop or to the flock, they have to all get along, and they go through this pecking order process until they figure out.

T: Who’s the alpha hen?

C: Who’s the alpha hen. It may not always be the same one as you enter new ones into the flock. So that’s kind of the same thing here. When I look at a company here, I look at the business opportunity, but it’s almost as important to look at the people or person. I’m very much into investing in the founders or founder primarily.

T: Do you think that’s more important than the idea?

C: No, not necessarily, but we’ve seen this over and over and over. Twitter is a great example, Evan Williams had a great success with Blogger right? Odeo was going nowhere and Twitter was a new idea that the same investors ponied up again for because they believed in him [Evan] and his team. Because frankly, Twitter, if I looked at it in a vacuum, it probably wouldn’t have made a lot of sense. But it came from those guys who had success and they believed in him so they invested in him and the rest is history

T: I’m curious as to why you differentiated.  You said in a team that you’re looking solely to invest in you look more at the business case and less at the personality…

C: Uh, no, no, no. I look at the personality as how they would potentially fit into an environment, so I want to qualify that. If we look at just an investment, we’re certainly looking at the people and…

T: People within their own environment as opposed to…

C: Within their own environment, yeah. I don’t have to worry about them getting along with someone next to them and that whole sort of ecosystem. We’re building an ecosystem here at Kicklabs that, just as a standalone investment, we wouldn’t really consider.

T: But you still have to worry about the co-founders getting along with each other?

C: Yes and that doesn’t always work. I’ve been in a few that haven’t worked for me.

T: What are some of the warning signs of that?

C: Sometimes there aren’t any. I don’t want to get too personal, but I’ve been in situations where I never saw it coming and all of a sudden… 180º on how this person acted. Never saw it coming, and I think part of it is that as things change, whether it’s stress, success, failure… in this particular case, there was a tremendous amount of success early on and this person wasn’t able to handle it. It’s almost like you shouldn’t read your own press clippings, and if you do, then it creates issues.

So I don’t think you’d ever see it coming. It is a marriage and you kind of have to treat it like that. I mean, I actually lived with this person for a while. When you start a company, it is truly living with someone, spending more time with that person than you would with your family and no matter how well you know that person, when they say a lot of times “don’t take money and do business with your friends” there’s a lot of truth to that too, so.

T: So, speaking of marriages, one of the things I’ve talked about with a lot of people is “how you date your co-founders?” So, what would be your ideal first date when vetting somebody to join a company? How would you sort of determine if they have the right qualities, the right skill to fit in with what you were doing?

C: I was going to say go play golf with them, but that’s not necessarily the right answer.

T: It might be.

C: I like to get out of a business environment, understand that person more. So, I was half joking about the golf. I do a lot of networking on the bike… I just did a bike ride with a bunch of guys that are in and around social media on Friday. We went up in the mountains of Mt. Tam. So I think it really is like dating. I think that you have to know someone beyond business because you spend so much time with them.

I think it’s really important to understand peoples’ expectations because you’ve got to stay really aligned and you may not always agree with how the business is going or you may have to… the favorite term today is pivoting, changing business models or “morphing things”.

You have to be aligned in sort of macro vision of what you want to do, but also when you take money the founders have to stay aligned. It’s really important because if not, that can really fracture a business really quickly.

To be continued next week where we discuss how VC and entrepreneur aims can diverge…

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email

When Should You Find a Co-founder? Before your idea is even half-baked.

When Should You Find a Co-founder? I’m going to go with my gut here and say: Before your idea is even half-baked.baked.potato 300x229 When Should You Find a Co founder? Before your idea is even half baked.

I’ve had a couple discussions recently about when is the right time to look for a co-founder. As soon as you have an idea? Once you’ve tested some of your core assumptions? Before you have an idea? There’s no rule and I haven’t seen anything written on the subject.

The Perfect Idea

The goal of your startup is to find a business model that works. If you think you’ve come up with the greatest idea ever, everything is worked out in your head, and you just need to execute, well…you’re probably wrong about everything (or at least most things) and you won’t get the one thing out of a co-founder than you really need: a second opinion.

If there is anything I’ve learned during my own startup journey, it’s that I know nothing and I need to learn as much as possible. I need to learn about my target market, my business model, coding, design, where the best sandwiches downtown are sold, etc.

If your idea is permanently fixed in your head, you’re not really trying to learn, you’re trying to prove to everyone else that you’re right. So why do you need a co-founder at that point? Just to do your bidding? Then you should be hiring someone.

If you want someone to join you in a partnership, it will probably work a lot better if it is actually a partnership. You should both be learning from each other and questioning each others assumptions so you can learn faster. If your co-founder asks you uncomfortable questions, that’s a good thing. Your co-founder should be helping you answer those hard questions. Embrace it.

Half-baked

I think the best time to find a co-founder is when you’re tossing around crazy ideas about changing the world with duct tape and a Swiss army knife. I want to hear more bizarre ideas that might not have occurred to me. I want to be able to throw my idea and my ego under the bridge if my co-founder has a better one.

I also want to make sure that my co-founder has an idea of their own. Preferably more than one. Creative solutions are often a numbers game.

It’s not that some people come up with the top 10% of all ideas. It’s just that there are some people that come up with a lot of ideas. Some are good, many are bad. If you don’t have a lot of them, you won’t be able to sift through and cherry pick the brilliant concept that will drive your business to the next level.

2 Cents

I’m sure many entrepreneurs will ignore this gladly. Some will say, “Determination is the single most important factor in success.”  That’s true…sort of.

An entrepreneur driven by pure determination with a preconceived notion and no desire to learn is a bit like a fool wandering around in the dark with map he drew himself twenty minutes ago who refuses to turn on his flashlight. Would you rather invest your life savings in someone who was stubbornly determined to succeed along a single preconceived notion? Or perhaps invest in someone who was determined to learn how to succeed?

To learn as fast as possible, find a study buddy.

Cheers,
Tristan

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email

Why Get Married on the First Date?…Co-Founder Dating

casual sex 199x300 Why Get Married on the First Date?...Co Founder DatingIn our customer development interviews with entrepreneurs looking for co-founders I’ve found many pitches follow this general course:

1) My idea is amazing, but I can’t tell you about it.
2) It’s a 100% surefire billion dollar idea, if only I had someone to do __________.
3) I will only tell you about my idea if you commit to indentured servitude for at least one year if not longer.

I find this a bit loopy.

Of course, not all are that bad. Still, many have one of the following three flaws, including the insistence of getting married on the first date.

Stealth Mode

If you can’t tell me what you’re working on, why are you bothering to pitch me? Ok, your resume is weighty and I love the fact that you’re capable of great things, but if you’re working on the latest massage oil targeted at the highly lucrative leper market, I’m not so excited. What can I say? I’m just not that into lepers. It’s not you, it’s me.

When someone asks you to commit to some vague concept based on their resume, it’s almost the equivalent of saying, “You should go down on me because I’ve had a lot of hot girlfriends.” Having a lot of experience doesn’t necessarily mean you’re great in bed, it just makes you more likely to have picked up an unpleasant disease.

The skills you excelled at in a big company will not necessarily do you any good in a startup. It’s a different set of skills that includes being stubbornly determined without being too stubborn, being able to juggle a variety of tasks as well as people, and most importantly the ability to admit what you don’t know and quickly learn to make up for it. Those things are not listed on your resume.

Last comment on this subject, we’ve all heard the excuses and know you don’t want someone to steal your brilliant idea. Let’s face it, if Jeff Bezos came to you ten years ago and told you he was going to sell books on-line, could you have “stolen” his idea? Probably not. It is always possible to give a high level overview without giving away your special sauce and the value for most ideas is in the execution.

Lack of Resources

I know you’re missing resources, every entrepreneur is. I’m working with two great co-founders who have complementary skill sets and there is always something that none of us know how to do. Whether it’s programming, marketing, manufacturing, doesn’t matter. What matters is whether or not you are just sitting on your hands until the the perfect someone comes along.

How hard is it to create a landing page? Not that hard. There’s tons of open source stuff that you can copy and just change a few variables. I’m technically weak, but I’ll do what needs to be done. Need a marketing person? If you’re not at least writing a blog and tweeting, why would I want to work with you?

As an entrepreneur, you can not fall back on the “that’s not in my job description” excuse. Because you will always be short of resources. If you’re not rolling up your sleeves and trying, it’s a sure signal that you don’t have what it takes to make a business work.

Commitment and Co-Founder Dating

These days, no one expects to get married after the first date. Why should your co-founder commit to anything other than dinner and a movie for starters?

Working with someone on a startup is a painful procedure. There are lots of ups and downs that will drain your coffers and leave you asking, “Why on earth did I do this?” At worst entrepreneurship is a lottery ticket. At best, it’s a bingo card.

You need someone who you can work in close proximity with for an extended period of time and it makes sense to try out that relationship on some small projects before committing to the big one. (Seth Cohen has one of the nicer metaphors for this. He says he wants to work with someone he could live on a submarine with. There won’t be a lot of shore leave.)

I’ll make a second post this week on good co-founder first dates. If you’ve got any good suggestions, I’d love to hear them.

Cheers,
Tristan

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email

Top Takeaway – Startup Lessons Learned

On April 23rd I was able to go to the Startup Lessons Learned Conference and had my world rocked. I thought I was lean, I could be leaner. I thought I had a minimum viable product, I could have built less. Although Steve Blank, Eric Ries, Dave McClure, David Weekly etc. etc. all have written and spoken prolifically about their methods and thoughts, there is a powerful feeling to being the the same room as a thousand other people drinking the same kool-aid.

Sponsorship Helps

First off, I should mention that I wouldn’t of been able to go at all without the sponsorship of the Microsoft Bizspark program. Usually I’m not one to thank MS except sarcastically for bricking my hard drive, but there’s no way a bootstrapped company like ours could have gone. So special thanks to Adrian Perez, Joel Franusic, and Bizspark!

Top Takeaway

There are a number of great summaries, videos, and more like Steve Blank’s Keynote. I don’t think I can add much to that and plenty of people like Sean Murphy are already on the job so I’ll skip that and talk about teams.

We’re a team of three people. We agree on somethings and disagree on others. Fortunately most of our disagreements are the productive kind where we come up with a third, forth, and fifth solution  through discussion and brainstorming. Still it takes us time to get in sync.

We’ve been talking about being a lean startup and customer development for months, reading and talking about Four Steps to the Epiphany. So I thought we were on the same page. Still, I was struck when Marcel turned to me in the middle of the conference and said, “So that’s what you’ve been talking about for months.”

Reasoning via Social Proof

Now, let’s be fair, there is a significant portion of the time where I’d describe myself as unintelligible. That’s my failing. However, I think there is always an element of social proof to reason. No matter how many times you might hear a cogent argument, it’s only when another guy chimes in with “I heard 2+2=4 as well” that we’re prepared to believe it. It’s true with facts and it’s more true with a paradigm shift.

Customer Development is a serious paradigm shift, especially for people who have been slugging away at product development in a big company like Manuel, Marcel, and myself. I may have gotten off the easiest since my last company was largely run like a startup (in the chaotic sense) and it has still taken me months to get into the spirit of lean. It takes a serious amount of un-indoctrination for us to even consider something as radical as questioning our own assumptions.

There is a value to sitting in a room with 1000 of your colleagues and realizing that you’re not the only one nodding in agreement. It’s a powerful reinforcement that is programmed into us by thousands and thousands of years of evolution. That’s a genetic trick that we need to take advantage of.

Of course we have to be careful that we’re not just monkey-see monkey-doing the latest business jargon and saying “out of pocket” like it not an incredibly idiotic phrase. We have to approach these things carefully and with thought. Still, we can take advantage of the great resources like the Startup Lessons Learned Conference and use our wired biology to our advantage.

We’re charged up. We thought of several ways we can chop functionality out of our product. We can test hypotheses that we thought we untouchable. We can explore revenue options months before we even considered it.

So my top takeaway from Startup Lessons Learned? Be a team.

A team working and thinking together under the same methodology can be efficient, learn faster, and achieve more.

We can make more value by building less. You can too.

Cheers,
Tristan

P.S.: Go buy Four Steps to The Epiphany if you haven’t read it yet.

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email

Clever Hans and Photoshop Iteration

It’s been over two weeks since we released a bare bones alpha of our site and started letting people in one at a time. Since then we’ve been through approximately:

  • 10 iterations of our “view idea” page
  • 6 iterations of “browse ideas” page and 3 of “browse people” page
  • 10 “profile” pages
  • 8 of our “p-home” page (this is the page you see when you log in)
  • 3 “search result” versions
  • and a whopping 14 basic template revisions

That’s a total of 51 revisions in 18 days, almost all of which are iterations based on feedback from users without writing a single line of code.

Photoshop Development

We’d been very slow to engage in real customer development. Despite getting a number of signups to our alpha, we made some early choices in platform which slowed our development down to some degree and made it difficult to get to our minimum viable product (MVP). To compensate for that, we searched for ways to get customer feedback without actually having a product.

As an interim fix, we created a number of photoshop mockups detailing exactly what information would be shown on what screen with REAL text (none of that “Lorem ipsum dolor sit” stuff). The mockups were heavily layered such that we could demo the “prototype” via screen sharing and demonstrate mouseovers, ajax calls, and other effects by showing/hiding a single group layer. (For those not photoshop savvy, this just means we could show on screen actions with one click.)

Alpha Hordes

We then took those photoshop mockups and put them in front of real users as often as possible (trying for twice a day) mostly via screen share and let the users look/play with them. In doing so, we got a ton of great feedback that led to so many revisions, but have certain difficulties:

  • Mockups are not clickable and must be controlled by the presenter

This has turned out to be a bit of a blessing in disguise. Our initial supposition was that not having a working prototype would reduce the quality of feedback. Instead, we’ve found that when the user can’t control the action directly, they’re forced to talk to us in order to get the mouse to move, scroll down, and click on things. This helps encourage the user to speak out loud. This includes exclamations such as “This page is overwhelming”, “I have no idea what this button is supposed to do”, and “I’m lost.” All of which is useful information for knowing what’s wrong with our site.

  • The feedback is confusing

As Dr. House says, people lie and they sometimes don’t know it. They’ll say they want more information. Then when you give it to them, they’ll want less information. Then you’ll revert to the original and they’ll say “perfect!” I write down every idea a user has, but I’m trying to listen more for what they’re talking about rather than what they’re saying. If they’re talking about the “post idea” button, it means they’re seeing the button. That’s good if you want them to post an idea and bad if the intended Call-to-Action is elsewhere.

  • Risk of asking leading questions

As I’ve written before, I have the habit of asking leading questions about items I think should be in the foreground, thus bringing them to the user’s focus. That leads to me feeling perfectly satisfied that the user is talking about the items I think they should be looking at, when they wouldn’t have even noticed them if I hadn’t brought it up.

Screen shares have been helpful here since people seem to ramble on and on when talking on the phone. Awkward silence just encourages them more. Even when they stop, all you have to do is ask “What are you thinking now?” and they’ll keep talking. The lack of physical presence also eliminates the possibility that the user looks to your body language for the “right” answer to a question. (See Clever Hans for a great example of this.)

Live Demos

We’ve also done a number of live demos which present a different type of information.

  • Body language and eye motion of the user is available

An obvious advantage of the live demo is that we can directly observe where on the screen the user is looking and in what order. This is perfect to observe the “F” pattern and if your intended focal point is accurate. It’s also great to see user body language and if they’re getting uncomfortable or frustrated it’s quickly evident in their seating posture or how they’re holding the mouse.

  • Users can “click” on things

Even though the photoshop images are not clickable, you can give the users the mouse and watch where they move it. If they’re getting into it, they’ll click on the image a couple times before remembering that it won’t work and then you’ll get the added bonus of seeing what the gut reaction of the person is.

No Substitute

Although I’m very happy with the results and think our designs have improved tremendously, this is no replacement for real development. It could easily be argued that the time spent on photoshop could have been better spent on writing code. Fortunately, as I have two partners who are far more technically savvy than I am, they’ve been able to develop the site in parallel while I focus on the user interface. This may have slowed us down in the short run, but it’s saved us a dozen coding iterations and allowed us to build up a more robust back end.

Even as a solo developer I think this approach has some benefits, particularly if your site will depend more heavily on user experience than any particular feature. My only qualm is that I cannot interview enough people to have a statistically relevant sample size and therefore need to take it to the next level in order to tie our results to actionable metrics. So this week and next, we’ll be putting our new knowledge on-line and seeing if our new user experience drives the behavior that we want.

Cheers,
Tristan

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email

Team/Market Fit is more important than Product/Market Fit

This New Year’s Eve, I’m resolving to work on the most important part of my own startup, the team. Specifically, I’m going to try as hard as possible to deserve to work with my co-founders, who are both more experienced and have a better understanding of technology than I can aspire to. But although I’ve heard a lot of common sense arguments about the importance of a good team, I find that a good deal of literature on the subject is easily misunderstood. I’m sure many people have read and agree with the most famous example of this. Marc Andreessen’s blog post is a fantastic discussion on the importance of a good market to the success of a startup. Marc correctly posits that a good team with a good product in a bad market will fail. He goes on to say explicitly that:

  • When a great team meets a lousy market, market wins.
  • When a lousy team meets a great market, market wins.
  • When a great team meets a great market, something special happens.

I certainly don’t want to disagree with someone who is both smarter and more successful in business than I am. However, I would like to point out thought that this is not an excuse to hire poorly or devote anything less than 100% of your attention in the early months into developing a great team. After all, Marc’s analysis is based upon his definition of a team:

The caliber of a startup team can be defined as the suitability of the CEO, senior staff, engineers, and other key staff relative to the opportunity in front of them.

In other words, you can have a team well qualified to exploit pet robotic whales in the US, but still fail because the market for robo-pets is fairly poor in the US and robo-whales just aren’t that fun to play with. Marc is essentially arguing that the caliber of the team is context sensitive. A great team for a new electric car company is not the same as a great team for a media company. The skills sets are largely, if not entirely, distinct from one another. However, there is one skill that is necessary for every founding team, regardless of what industry they are in: HR. That is to say, every team needs to be able to strategically hire individuals well suited to the market opportunities and when the market opportunity is unclear, hire individuals well suited to discovering market opportunity.

Strategic Market Choice

There are entrepreneurs out there that hatch a genius idea fully formed like Aphrodite stepping out of her shell or Athena springing from Zeus’ head whole. Sadly, I’m not one of them and like many entrepreneurs out there, I work in a process of continual improvement and refinement. This might include subtle pivots or radically different strategies / products. Either way, I rely heavily on my co-founders to note when something isn’t working if I fail to realize it myself.

When I was a musician, I was always impressed by the number of go-it-alone musicians who managed to pack up their instruments and head out on the road by themselves with a beat up hatchback and no support whatsoever. They’d play coffee shops, clubs, and street corners equally. Never passing up a chance to pick up a fan at a subway stop. To go it alone is an admirable aspiration, and some greats like Ani DiFranco can take this path to success. I certainly can not. I’m more like the other 99.99% of people who need a helping hand of a bass player, drummer, or even just someone offering a place to crash every night. Those are the people who will be able to see into your own blind spot and point out when you’re wasting your time in glam rock when grunge is taking off. Other people are a critical part to every business, and even in the extreme go-it-alone movement you need to know who you can count on for a quick reality check and who you can’t.

In business, I’m similarly limited by the scope of my experience and learning, and in that, it’s rare for me to be in a position where I can explore a market opportunity single handed. I’m much more likely to get to the point of product / market fit if I have a small team of entrepreneurs with complimentary skill sets than if I just pick an opportunity and blindly try and build a team around it. I’d call this market / team fit.

Drafting the Market

Marc Andreesson has a significant advantage over the rest of us when it comes to his strategy. He is famous enough to attract the right people for whatever market he chooses to enter and he is wealthy enough to pay them. To anyone with such an advantage, it’s easy to see why market would trump team in importance. It’s also easy to see that a bad team in a good market ought to be able to use some of the market growth to start hiring a better team. Even more to the point, you could simply adopt a market drafter position, let someone else develop the market, and simple coast along with them. I should emphasize that in any of these cases, having a market as your primary driver is a very good strategy. It’s only when your resources are constrained that this strategy will fail every time.

It doesn’t matter one bit that the market for solar cells or innovative battery technology is booming in terms of my success in that market. I simply don’t have the resources to enter that market, no matter how good the market is or how prescient my market forecasts are. So here is one of Marc’s examples again:

  • When a lousy team meets a great market, market wins.

Does this ring true? If what you mean by “lousy” is “barely competent” than it probably is true. Barely competent is enough to get a product out the door and a barely competent product is worth 1% of the market. If you’ve got a trillion dollar market, you can retire on 1% or even 0.01%. But if by “lousy” you mean “can’t tie their shoelaces incompetent,” well… the market can’t win when the team fails.

As an entrepreneur he has a vast amount of experience in this and his opinion should be taken very seriously. However, Marc’s personal experience gives him a sample of startups which succeeded enough to be noticed by him. That is to say, they got out of the door and to the races. His perception of lousy teams is skewed to exclude those teams which were incapable of entering the market in the first place. In other words, his “lousy” team is still pretty decent. In the big world of 750,000 entrepreneurial ventures started each year in the US, a great number of them fail before they’re able to even get to market due to an inability to put together a sufficient team.

Build a Team of Explorers

I would argue that having a great team of entrepreneurs is a necessary, but not sufficient, condition for success. Furthermore, a great team will actively explore market opportunities and self select themselves out of the wrong market. Put another way, the right team in the wrong market will change markets. The wrong team in the right market may just bludgeon itself with a bad strategy and be dominated by a stronger competitor.

As someone who needs teammates with complimentary skills sets, I can only tell you that I have to build or join a great team to find success. I simply have no other option. I try and find other entrepreneurs who I can learn from, respect, and support. Given a team of those individuals, I feel assured of success. Perhaps not success in the same market I originally planned on, but a success I can be proud to be a part of.

So I’m left with the final editors comment from Marc’s post:

why can’t you count on on a great team to build the right product and find the right market?

I’m still waiting for the answer to this question. I haven’t read everything out there so it may very well be in another of Marc’s posts, or perhaps another blog, but I think it’s a valuable question to pursue.

Happy New Year!
Tristan

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email

Merry Xmas!…now shut up and start coding.

Just about every entrepreneur I’ve met in Silicon Valley knows how to write more than a few lines of code. The ones that don’t are constantly looking for a partner to build their dream product. You know, the one that will make them a billion dollars. I’d guess you’d have to count me among them. But waiting around for a dream co-founder doesn’t cut it around here. That’s why this Christmas I’m writing code.

I haven’t written a line since high school when the two languages I knew were Pascal and MACOS. In case your wondering, MACOS wasn’t even a proper language, only worked on my Apple II series, and stood for More of A Crappy Operating System. I don’t even know what it was, but it sure wasn’t Mac OS X. I used it for my bulletin board system (BBS for those that remember pre-www). I never saw an instruction book, not sure there was one, but I was able to understand the basic syntax easily enough and hack code from different available sources into something vaguely resembling what I wanted. But that was over 16 years ago. I have no business writing code professionally, but sometimes business requires you to do something unprofessional.

The lack of a critical skills is something that we all have to deal with at some point. Whether it’s the ability to program, an understanding of supply chain flow, or just market knowledge. The difference between a successful entrepreneur and one who goes from one idea to the next is more than likely a function of how they deal with those missing resources. In the startup world, you’re always out of resources, so it makes sense to develop some coping strategies.

No Excuses – Do It Yourself

The biggest problem I usually have in getting things done is usually myself. There’s a ton of things I’d rather be doing than writing code. (Hell, there’s a lot of things I’d rather be doing than writing this blog.) Among them? Cookies, guitar, and Avatar came out this weekend. None of those things can be an excuse, but motivation is an easier hurdle to overcome.  Even worse is the excuse of “I don’t know how.” As in, “I don’t know HTML, CSS, Javascript, Java, or PHP.” Worse still is “That’s not my job.”

When I started my last job at Secude, I didn’t know a thing about IT security and couldn’t for the life of me understand cryptography, let alone what a Diffie-Hellman was supposed to be. It was daunting beyond belief, especially when asked to go and learn about a new P2P encryption technology and report back to our engineering staff on the technical details. I cannot imagine a job I was less qualified to do. The fact that my technical partner for the assignment spoke halting English to match my halting German was no help. Could I have given up? Sure. Could I have assigned the work to someone else? Probably. But I wouldn’t have gotten the information and perspective I needed to do my job for the next four years.

Learn or Die

The business of business is learning. If you’re not learning, you’re probably losing money. Knowing how your business works from the bottom to the top is the only way you’re going to understand your value chain. Do you have to sweep the floors on the factory to be a good CEO? Well, maybe not. But you do need to know how important it is that the factory floors are clean, something that a lot of big-shot CEOs probably don’t know. When machines get dirty, they break. When the floor gets slick, your company loses big in workers comp. Even five minutes sweeping the floor in the factory could give a lot of CEOs a bit more appreciation for the janitor and make them realize that cutting the janitor’s salary and having a disgruntled employee doing a half-assed job is probably more expensive in the long run than paying a decent wage for decent work.

Little gears push the big gears and every aspect of the value chain can be critical. That thinking and the drive to reduce muda (waste) came out of lean production thinking when Toyota discover that they could improve productivity radically by just shifting some machines around. Chihiro Nakao, the great lean production thought leader, was no stranger to getting his hands dirty. In Lean Thinking, Womack and Jones related how Nakao and Takenaka worked over the lunch hour with crowbars to move Wiremold’s massive machines into the proper sequence for single-piece flow while the local engineers, workers, and managers just stared at them with their mouths wide open. That’s no excuse thinking.

Knowing isn’t Understanding

For those that think you can learn something without doing it yourself, good luck. There are a lot of people far smarter than I that can, but I can’t. I need to learn by getting my hands dirty, and I learn up to three times as fast when I’m actively engaged in a task than when I observe someone else doing it from afar. Observation will lead you to know facts, doing will lead you to understand processes. I need to know processes. Even if we bring on two more engineers tomorrow, I’ll greatly benefit from the experience.

Why not outsource?

Why go through this exercise? Surely it would be better to just outsource a task like front end coding and it’s probably more cost effective than me doing it. Well, sometimes, and in fact we’re exploring several outsourcing options for our front end web development for startupSQUARE.com. But sometimes managing outsourcing can be just as time consuming as doing it yourself. The ability to communicate effectively with outsourcers and reduce communication overhead is directly related to your own understanding of the process.

An example: a new CEO outsources his fabulous idea for a new website to a team of four engineers but development falls behind schedule. Solution? Of course! Add more engineers! This would be laughable if it didn’t happen so often. I’m sure every engineer in the world by now has had to explain patiently to their boss that nine women cannot have a baby in one month. If the CEO had spent a decent weekend locked in a room pouring over source code, that would be well understood. You can’t have four people editing the same line of code.

My Just Deserts

So here’s what I hope to get out of this exercise:

  1. Comparative Advantage – I won’t go into the economic theory of this, but in a nutshell: it’s better for my skilled engineers to work on the important back-end stuff. I can waste my time with the “Follow me” button you see on the side of the screen.
  2. Understanding – Knowing the rough difficulty level of a task allows me to plan resources and our hiring strategy better. It also allows me to set more realistic expectations and goals.
  3. Sympathy – You’ll never catch me yelling at someone for being late on a technical issue again. Instead, I’ll roll up my sleeves and try to help by doing research and finding sample code.
  4. Respect – Aside from a better understanding of the tasks my technical co-founders suffer through, I we also develop some respect for each other with the fact that I’m willing to dig into things if necessary. After all, I started a company at least partly because I didn’t like the environment of my last job. Mutual respect among co-workers is the only environment I really want to work in.
  5. Get things done – At the end of the day…our product needs to get out of alpha and it’s going to take no excuses hands on deck to do it.

So this Christmas, send me a link to your favorite PHP resource or your resume if you’re an engineer. But in the meantime, I’ll keep coding. Merry Christmas, Happy Holidays, Seasons Greetings and all that! Hope it’s a good one, and I hope I’ll be able to post about a snazzy new startupSQUARE.com website in the coming New Year.

Best regards,
Tristan

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email

Productive Chaos: How to Hurry Without Rushing (p. 1)

As founders, we often tend to work ridiculous hours in the hopes that more hours = more revenue. This is often not the case. Instead, we cause a lot of motion and the dust is well stirred, but little is actually accomplished. I have found that most people get about 4 productive hours out of the day, no matter how many hours they actually put in. Especially since the average “I worked a twenty hour day” usually consists of several meal breaks, watercooler BS, daydreaming, IM, office politics, chain mail, the latest viral video, sexual innuendo, and other nonsense.

I’d rather work productively for 4 hours than unproductively for 20. So I retrained my work habits until I could get a normal days work done in four hours, and then I started increasing my hours from there. Nowadays I can get a genuinely productive 16 hour day if I need to, but generally settle somewhere between 7 and 9 with a healthy amount of time for non-goal oriented learning and creative thinking. Here’s a list of little tips that have helped me, many of which come from Getting Things Done by David Allen. It’s worth a read if you’re not familiar with it. Sometime it’s a bit tedious and you’ll find that you already know 50-80% of it, but the parts you don’t know are extremely valuable.

Avoid Context Switching
If you think you can multi-task between five IM screens, your email, facebook, and an actually productive task, well that’s great. Stop reading this. But every time I switch gears from a phone call to an excel sheet to php code I lose about 15 minutes as my brain reorients. This is true of minor interruptions including emails, IM, the phone, etc. and it’s probably true for everyone.

As a founder I have a ton of things going on and it’s hard to shut everything down to focus, but it really helps. If you honestly can’t shut down extra apps, close your door and put up the do not disturb sign, it’s time to get up two hours earlier so you can have an uninterrupted block of time to work. Two hours is the minimum for me to make progress on a complex task. 30 mins for minor work blocks. I need four hours if I’m going to do any programming or one of my uber complicated spreadsheets. You might want to consider useful apps like Concentrate or Rescue Time which enforce this for you.

Chunk Similar Tasks
Along the same lines, I like to eliminate interruptions by getting a block of similar tasks done at once, like phone calls which are prime procrastination material. (Think: “I’ll just take a quick break and call David Wallace.”). But obviously, you’re setting yourself up for major distractions when you start getting call backs unless you unplug your phone afterwards. I like to walk to work in the morning which takes about 45 minutes. I make calls on the way, generally get any callbacks I need, I get exercise, and it clears my head.

The (Un)Glory of Caffeine
I don’t find this all that helpful as an all purpose solution, but from time to time is a lifesaver. Your body tends to get used to whatever drugs you put into it, and caffeine is no exception. If you have a cup of coffee every day, you’re not actually more awake and aware than if you didn’t have any caffeine at all. It’s only when your caffeine intake has an abnormal spike or dip that there’s any real change in your energy level. So if you normally drink a coffee every day and skip it, yes…you’ll feel awful on that day and receive no real benefit when you have your “normal” dose.

I cut out all caffeine (including sugary sodas) and had a miserable couple of weeks, but then my body re-calibrated and now I get a nice boost on the once a week occasion when I need caffeine to pull me through an all-nighter. In addition if I don’t drink caffeine after 11 or 12 am, I sleep a lot better, which makes me more rested and more productive the next day.

Zzzzzzz……..
Sleep is critical, but difficult. When I have something on my mind, I tend to wake up at 4 am and can’t get back to sleep. If this happens, I’m better off getting out of bed and dealing with it than just laying there stressing out. But then it’s up and at ‘em, cook breakfast, take shower, and make a day out of it. Doing something halfway and then trying to get back to sleep never works well and I’ll probably just dream about it anyway, which isn’t very restful when you’ve got excel tables in your head.

Best of all is clearly to not have something on your mind. For those that can meditate, that’s great. I’ve never been able to, but I clear my mind anyway by making sure that I have a system in place that logs all my To Dos. I can have 100 upcoming tasks, but as long as I’m confident that I won’t forget one (because I wrote it down) then I can sleep through the night. For this reasons I highly recommend having a system that you trust like Getting Things Done. But it doesn’t really matter what system it is so long as you trust it and it works for you. A piece of paper will do.

Time Tracking
I love time tracking software, but you don’t need software. Again, a piece of paper will do. The principle is pretty simple and it is consistent with every productivity guru I’ve ever heard. You can improve what you measure. So measure how much time out of each day is actually productive and you’ll find that you can focus on beating that amount the next day and the next week. Just keep track.

What does ‘actually productive’ mean? If you spend 8 hours researching, but have not managed to put any of that research into effect, you have accomplished nothing. At the minimum, research needs to result in a useful summary or notes, meetings must result in action items, and coding must result in something that runs (even if poorly). If you just held a 4 hour meeting to “motivate” employees with your vision, you probably didn’t accomplish anything except maybe made yourself feel important and useful. But hey, maybe you’re Tim Robbins, so go for it. I’d rather motivate my staff by working hard and helping them directly with issues that they’re facing or problems they might solve. If you explain your killer vision to your staff in the context of the work they do, it’ll be that much more meaningful to them.

If you have any useful tips of your own, please let me know. I’m always looking for ways to work smarter while remaining relaxed. There are some other topics I’d like to cover, but will continue in later posts:

  • Useful breaks
  • Exercise
  • Working with co-workers
  • Food

Cheers,
Tristan

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email

Helping Hand

I’m struck by how open the startup community is in Silicon Valley. There seems to be an unending supply of people who are willing to take time out of their day to give advice, lend a hand, or otherwise be almost unacceptably nice. Beyond the obvious, I think it’s a key component of why Silicon Valley is able to churn out such a high amount of innovation year after year.

One example is Bob Dourandish from Revenzy.com. I met him at the SV New Tech Meetup for all of five minutes before he offered to take a look at our site and offer some advice on how to market it. Since then, he’s spent more of his time discussing our ideas and even wrote a very nice blog post mentioning us. Any benefit to him? Marginal at best. Sure, maybe he gets one more alpha tester for his site and a mention in this blog, but that’s hardly going to line his coffers anytime soon.

So what’s the motivation behind these selfless acts? Cynics, game theorists, or fans of B.F. Skinner would say that every selfless act has at it’s heart some selfish motivation. Pride, a feeling of importance, or perhaps some favor in the future. However I think it’s much simpler. When it comes down to it, people around here want to belong to a community that actually supports them, and that sort of community fosters it’s own behavioral incentives. After all, who wants to belong to a community where people are only out for themselves? Certainly there are many such communities that feed upon themselves until everyone is left with sub-par equilibrium behavior, but they are not communities where anyone actually wants to belong. (A more jargony way to say it? There is a universal benefit to this particular commons, and very little incentive for free-riders to crash the party.)

Another fine example is Jason CalacanisOpen Angel Forum. Jason has taken it upon himself to destroy the pay-to-play system of Angel investment forums, something which has only marginal benefit for exceedingly high costs in his own time and energy. The main benefit to him? Being part of a community that he actually wants to be a part of.

In part, this sort of behavior may be due to the unique nature of the market here. Many entrepreneurs wind up constructing services for other entrepreneurs. In the past two weeks I’ve seen sites which set up an easy alpha user program, sites which offer email integration, chat clients, etc. etc. All pieces which someone else can use to create yet another infrastructure product for someone else. The open source philosophy has morphed into the open API philosophy which has created a stand-alone ecosystem of entrepreneurs. The philosophy of that ecosystem ties everyone together to such a degree, that helping out your neighbor is almost always a win win situation.

In practical terms, let me return to the first example. Bob and I started with a simple conversation, and in a week we’ve been able to toss around ideas for two seemingly unrelated products (startupSQUARE.com and Revenzy.com) and are brainstorming ways to make them work together. With some work, we can figure out someway to integrate his social auctioning system into our site to create a way for entrepreneurs to pool their purchasing power and receive discounts from larger vendors. An integration which could wind up helping the community even more.

It’s a great time to be in San Francisco, and I hope that Manuel, Marcel and I at startupSQUARE.com are able to give as much to the community as it’s giving to us.

Cheers,

Tristan Kromer

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email

StartUp SF v2.2 – "Give Your Ideas Ex-Lax" with David Weekly

On Wednesday I went to see David Weekly speak at StartUp SF v2.2 – “Give Your Ideas Ex-Lax”. I’d heard a shorter version before at Startup Weekend, but I was glad to see it again and hear the full version. I largely agree with the ideas behind it, which David shares with Eric Ries, Steve Blank and others, but it does raise a question I wish I had some statistics on.

Does getting ideas out the door faster increase the overall success rate of ideas? Or do you just have more chances at getting it right?

Although I’m following customer development methodology and I have a gut feeling that my odds of success are better for it, I’m a bit surprised that there aren’t any statistical survey’s backing it up. Perhaps there are, and I just don’t know. (In which case, please send a URL over in the comments.) The anecdotal evidence is very strong, but they’re still just anecdotes. It seems as if the Malcolm Gladwell method of argumentation by quirkiness and common sense has become quite pervasive, or perhaps it’s not a new thing. (After all, I’ve been out of the country for a few years.)

So here’s my rational for pressing on (and here’s hoping it’s not a rationalization.) Even if customer development doesn’t give you a better chance of success, it gives you more chances. So hunt with a shotgun and not a sniper rifle.

If you’ve got an idea for a product and it’ll cost you 6 months of your life to get it out the door with a 50% of success and your time is worth $10k a month in opportunity costs in consulting opportunities. So the return better be at least >$120k to be worth doing (return should be > [10k/month x 6 months] / 50%). If you can do a stripped down version of the same product in one month, it’s much better to do so, even if the likelihood of success decreases to 10% (return should be > [10k/month x 1 months] / 10%). Plus, you’ll have five more chances of hitting a really big idea so you can retire to that private island you’ve been shopping for.

Obviously that equation is unrealistically simple, but the principle is the same. I’d rather have 6 lottery tickets than one, and the if you follow a soft launch methodology, odds are that your early adopters won’t care about a few bugs enough for it to sink your idea and the potential return is still the same. So in the end, customer development methodology ought to win out by virtue of having more chances. But I still wish there were a few more facts available.

You should share this post here:
  • Twitter
  • Facebook
  • LinkedIn
  • FriendFeed
  • del.icio.us
  • Google Bookmarks
  • Digg
  • Tumblr
  • StumbleUpon
  • Posterous
  • Slashdot
  • email