Some of my favorite books for entrepreneurs
Since it’s the Christmas season, you may want to treat yourself to some great reading. I put together a list of some of my favorite books for entrepreneurs. Get inspired, learn practical things, or expand your reference library. Happy reading!
It doesn’t make sense to make healthcare the responsibility of the entrepreneur
Without health reform, entrepreneurs will continue to take the wrong risks. Starting a company is the art of making do without resources. This often means limiting your own compensation and forgoing health insurance at the start. When recruiting employees, its difficult in the early stages of a company to offer health benefits that comparable let alone competitive with those of larger companies.
[From Ross Mayfield's Weblog]
I couldn’t agree more. I’ve been looking at how startups operate in other countries with more “socialized” medicine such as Spain, and while they are broadly disadvantaged on many aspects compared to US companies, when it comes to healthcare, the US is one of the toughest environments.
For me, at the core of the issue is that the burden for healthcare is put on the entrepreneur. We can argue all we want about whether this should be an individual responsibility of the citizen or a collective responsibility of society expressed through a government program, but whatever the alternative, most people agree it should not be the responsibility of the employer.
9 steps to design a mobile application
If you’re considering building a mobile app, there isn’t a lot of advice out there about how best to do it. There’s a ton of web design advice, but it ports rather poorly to the small screen. Mostly by trial and error, I’ve been able to come up with a simple method to determine whether a design will work, so here it is.
The biggest difference between a mobile app and a web app, from the designer’s point of view, is the need to cater to a different pointing device: the finger. It’s fatter, and there is a lot less real estate. If you try to design a mobile app using paper prototyping and static photoshopped screenshots, you are going to end up with an app that is hard to use, hard to navigate, and too small on the eyes.
Instead:
Create the flow. Start by breaking down the flow that supports your use cases into small chunks. These will be the screens. Focus on the content, and the operations will naturally follow. Then, make a map which describes how to get from one screen to the other. Just remember that there are established navigation guidelines for some platforms like the iPhone, and no guidelines for some other platforms, like Android.- Make mock screens. Design each screen with a program like OmniGraffle… or anything that allows you to layer and reuse UI elements.
- Look at the screens on the smartphone. Cut each screenshot into an image, then save all the images to the device you want to support. Use a gallery / image viewer software on the device’s screen to view the artwork. How do things look? Do you think you could fit a finger in that widget? Are the fonts too small (generally, yes)? Did you try to fit too much information (generally, yes)? Are there too many rows of data? (generally, yes)… Iterate over steps 2 and 3 until you’re comfortable with the answers to these questions. Also, don’t forget about landscape view.
- Make a very simple static app to test the navigation. Implement the home screen of the app with real widgets. Don’t implement any behaviors for the widgets. If you touch a widget, all it does is open up the image of the corresponding screen. Touching the image takes you back to the home screen, or progresses you through another image until you finish the sequence. The idea is to figure out if the navigation will work. Are there too many steps? (probably yes) Is it obvious how to accomplish the task? Did I get the sequence right?
- Determine if you picked the right widgets. Take some time to replace the most important screen images with actual widgets. Use mock data, just try to reproduce the most important states based on some representative samples. Did you pick a drop down/button/slider/menu that is appropriate for this function? Wherever there are lists of choices, did you have the right choices? Did you name the actions correctly?
- Screen the app with a developer. At this point, you should have large chunks of the GUI elements of the application implemented in a static manner. Show it to a developer who will be in charge of implementing the application. What does he think? Are there areas of the design that will be hard to implement? Are there potential performance issues in some screens (e.g. the widgets can’t be reused when you scroll, they need to be redrawn so the response time sucks). If the developer gives you a go ahead…
- Test the mock application with users. This would be no different than mock application prototyping. If the users like it…
- Apply the visual styling. Things like colors for buttons, backgrounds, shades, etc… Don’t get too cutesy, there’s only downside.
- Implement. Take all the design artifacts, the visual assets, and hand them over to the developer, the app is ready to be implemented.
What have you found that works best to design a mobile app?
What biking has taught me about business
I took up biking over the summer, largely as a way to lose some weight and get in shape. I learnt a few lessons that apply to business and I share them below.
In bike-speak, I’m what they call a clydesdale, an overweight dude who picks up biking to get fit. I’m glad to see that it’s a trend among techies. Our 100% sedentary jobs and our natural inclination for things intellectual makes it possible to go through life without making any physical efforts. I’ve met fit techies too, but the ratio definitely favors the well-built kind.
Here it goes.
Like Mark Suster says, be persistent. When I started biking I was in a lot of pain. Even a 4 mile commute would be major. But I kept on going, every day, and my body started getting used to the effort and (very) slowly rewarded me with added stamina. In business, getting to a goal is much more likely if you have a chance to iterate many times over the idea. For example, when it comes to product ideas, following the minimum viable product approach.- Be prepared. I remember the beginning of my bike commuting was an unmitigated disaster. I forgot my shoes, or some clothes, or the bike lock, or … you name it, I’ve probably forgotten it or kept it at the wrong location. My task at hand (to bike from A to B), seemingly simple, got way overcomplicated because I didn’t have a supporting system. In business, you have to invest in the process to make the outcomes happen in a predictable way.
- Don’t be a loner. Every weekend I would go on these rides by myself. It was fun and everything, but I only made so much progress. Then I joined a biking club, the Potomac Pedalers. Going on rides with other people challenged me and helped me learn about how others, ahead in their cycling prowess, solved the little challenges. In business, you can operate solo, but then every problem is your own problem. You slow down your learning, and it’s harder to spot opportunities. It’s much better to be part of a team. And much more enjoyable.
- Don’t be afraid to ask. There’s so much to learn about biking, and it makes a difference too. Why do they wear those tights? Why do they walk in those funny shoes? Why are those saddles so thin? etc etc… So I’ve driven my friend Steve crazy, and every shop employee at all the local bike shops in herndon and reston… to get the advice. This has helped me so much in all the other goals. In business, you can do it the hard way, or you can ask somebody who’s been there before. But that requires work too. Work to build the relationships with mentors and advisors. And it also requires humility to realize how much you don’t know. And vulnerability to ask a potentially stupid question.
(This post is for my friend Steve)
Engineers making fun of marketing people
This video is brilliant. It captures so well how engineers feel about marketing.
For every marketing person who knows how to connect an audience with problems to a product with the benefits they need using a simple, compelling message, there are many who simply can’t. But that won’t prevent them from using words like marketecture and sounding hollow.
(Found via Steve Johnson’s blog)
Intrapreneur or Entrepreneur?
[Upd. 12/10/09] This is the story of how I became an entrepreneur through intrapreneurship. I wasn’t born an entrepreneur. I have yet much to prove. But I’m on the road, trying not to take the detours and enjoying it all the way. Lately I’ve been reflecting on how I got where I am and whether I would advise somebody 10 years younger to take the same path. If you’re a recent college grad, if you work in a large tech company and are wondering if you should take the plunge or if you’re a young entrepreneur asking yourself about the path you’ve followed, this may be useful for you.
I went to college in Manchester, England. When I graduated, I had a choice. I could start a business or get a job. Unlike many grads from US colleges, I didn’t have any debt, thanks to the EU and the public university system. It was clear that I wanted to work in the software industry. Investment banking was a strong temptation, but after a summer at Barclays, I saw way too many alcoholics to crave the life, and frankly, getting a limo back home at night didn’t do much for me.
So I had a real choice. I saw two classmate friends (hello Roland and Su
, who I respected for their intellect and their attitude, plunge into the dotcom bubble. I remember Roland’s words “Sam, this is a very special time, it may never come again.” They moved to San Francisco and kicked off their careers the startup way.
But I felt very strongly that the chances of succeeding with 100% stamina and 0% knowledge of how to run a business were significantly lower than with 60% stamina and 60% knowledge.
So I decided to wait. I tried to find the most entrepreneurial company hiring engineers in the software industry, with the most exciting technology and the most charismatic leader from whom to learn. In 1998 that was Microstrategy, without a doubt.
Hot off an IPO, MSTR was seeing explosive growth. It was racking up customers left and right, and its leader, Michael Saylor, was electrifying. I remember devouring his interviews, articles and speeches and stand in awe of him. This was the general that I could follow. So I joined his army.
You can get a taste of Michael in his Charlie Rose interview from 2000. He starts slow, but as Charlie asks him about the future and what’s the next big idea, you can get a glimpse of Michael at his best. He was able to articulate why technology mattered and how it could make lives better. Not only that, he could fire up his troops, line them up and execute.
Microstrategy was a company that attracted incredible talent, especially for an East Coast company. They had this mantra of finding the best young grads they could find and put them in positions of real responsibility. They also believed everybody needed to know the products and the philosophy inside out. So they put together a 3 month bootcamp that every employee went through. I remember those three months as grueling and challenging. At the end of bootcamp, depending on your grades, you got more opportunities to join different efforts in the company.
I wanted to join a team that had all its challenges ahead. I wanted an opportunity where, if I figured things out, there would be tremendous growth. I wanted to work with brilliant people. Finally, I wanted to be part of a small team. I found all those things at Angel.com. When I joined the Angel project, it had been up and running for 6 months. It was called Project X. Some marketing people had written a white paper explaining how Saylor’s vision could be translated into a product. Some techies had explored different ways of building it. But not a lot else.
For the first 2 years I worked as a software engineer. I stayed out of a lot of decisions, wasn’t even aware of many being made, and simply put my head down and tried to learn professional software engineering. My contributions weren’t particularly good — I’m an OK programmer, but not great. But thanks to a couple of brilliant developers, Ben and Josh, I learnt a lot: design patterns, agile programming, test driven development, UML, enterprise Java…
Two years into the project I had an opportunity to change roles. I became a technical product manager. In this job, I learnt how to write specs, how to design software, how to release, how to run a beta program, how to get feedback from customers, how to research competitors. I learnt how to prioritize and how to solve the tension between business people and technical folk.
It was 4 years into the project that things started to get interesting. We had finally struck a chord in the marketplace. We had changed the business model a couple of times and finally there was an audience. As I delivered my projects I kept on getting bigger assignments. I built very strong relationships with 5 folks who ran sales, engineering, marketing and operations. These were years where I started getting a team. First, one guy, then another. For a long time, not much more.
In 2005 I got my first VP-level position. It’s at this point that I think I finally became an intrapreneur. From 05 till I moved on in 09, I was part of one of the most exhilarating rides of my career. Incredible challenges, fantastic solutions, great growth. At the end, we were 25 technologists and a high performance team.
An intrapreneur is somebody who runs a business unit inside of a bigger organization, as if it were a startup. You make your pitch, you get the funds, you hustle, you get something out in the marketplace, you grow it, break some rules, and hopefully you turn it into a success for the organization, which in turn, rewards you with the gifts big organizations can give: bigger salaries, plusher jobs, more resources, fame within the building.
As an intrapreneur you’re navigating the organization trying to make things happen. On paper, it sounds great. After all, large organizations have potentially very complementary aspects to startups:
- The company wants new revenue — the intra-startup has ideas
- The company has money — the intra-startup can put it most effectively to work
- The company has expertise — the intra-startup has passionate people
- The company has channels / distribution — the intra-startup has product to sell
- The company has the ear of influencers — the intra-startup has a story to tell
- The company has a well-run back office — the intra-startup can focus on R&D and marketing
- The company has powerful executives — the intra-startup needs doors opened
It turns out that intrapreneurship is fraught with peril for both incubating companies and intra-startups. You’re simply catching two organizations at two very different spots in their life-cycle, and they’re hard to reconcile. The company didn’t get to be big and stay big without processes. Processes keep the company from collapsing. But startups die with processes. Startup people and corporate people add value in radically different ways. And they’re suspicious of each other.
There is good advice out there for successful intrapreneurship, for example, in Ben Casnocha’s blog, and in this Fast Company article by Robert Wolcott and Michael Lippitz. I would summarize it like this: Be a rebel who focuses on what can practically be accomplished and know when to shut up. The first part came very naturally to me. I am a rebel. The second part took years of honing. I still struggle with the last part.
When you are an entrepreneur, of any kind, you assume that –if it is within reach– the optimal, most rational solution to a problem wins. In a large company, though, there are many more interests and agendas at play. In the best run organizations, executives go through a process of aligning units and empowering people who help them discover the best ways to achieve the desired outcomes. In the rest of organizations you find a patchwork of well-run and well-intentioned people intermixed with much darker forces at play.
This makes the job of the intrapreneur that much harder. Like a boat trying to get from the Atlantic to the Pacific through the North East Passage, it’s the shortest route, as long as you don’t get sunk by a chunk of ice.
Ultimately, this is the main reason that drove me to become a mainstream entrepreneur. I had learnt an incredible amount and I was ready to put it towards creating value in a way that would cause the least friction and lead to the least wasted effort. It’s difficult enough to have market success. I traded an enviable amount of resources for the simplicity of the startup execution model.
My advice for someone out of college who wants to start a business. Should you set out on your own, right now? I would take a hard look at yourself. Are you beyond class? Do you have it in you to be the next Bill Gates, Steve Jobs, Sergey Brin, Larry Page or Mark Zuckerberg? If so, nothing should stop you. You’ve probably been wasting your time in college already. Are you good but within the average of your wannabe entrepreneur peer group? Then, intrapreneurship can be very fruitful.
You might be tempted to go ahead and join an early stage startup. It’s a possibility, but you must beware of the Earn or Learn conundrum, as Mark Suster puts it. You might not get either the earning that you hope or the learning that you need.
In any case, intrapreneurship does not equal corporate job. If, while you’re learning a profession you become soft (kids and mortgages can do that very quickly), stop being curious or learning and get addicted to the paycheck, the more likely outcome is that you will waste valuable years. Scott Gatz is an example of an intrapreneur with the right attitude.
My advice for someone in a corporate job who wonders about entrepreneurship. The most important question to ask of yourself is: how much learning that is applicable to entrepreneurship are you likely to accumulate in the next cycle? Have you been responsible for trying to make a buck for the company already? As the years go by, a corporate job offers diminishing returns. Especially if you are not getting promoted fast, or getting exposed to different companies by switching jobs. If the learning opportunity is not good, you may be better off starting on your own. (Before you do, please read this.).
My advice for someone who enterprised early on and is now wondering about the path they chose. Are you prepared to make the opportunity before you a success? Are you serious and committed? Do you have partners who are trustworthy and complementary to you? Are you willing to fail many times over your first decade of startups and not be discouraged? If so, stay the course. If not, you can learn very valuable skills in a forward thinking company. Whatever the corporate environment, pick a company with leaders you admire and who you can learn from, pick an opportunity that will put you in the line of fire, and don’t let anything quell your entrepreneurial spirit. Patience pays off.
(This post is for my fellow entrepreneur Juan Mateu of Solaiemes, who asked for it)
Is there a subject that you would like me to blog about? Submit your topic

The Threaded view as a visual design pattern
If you are designing some software product with a social aspect, sooner or later you’re going to face the challenge of representing conversations visually. The conversation metaphor has risen meteorically to the pantheon of top ideas in software due to its power of bringing people together. In this post I take you through a visual tour of the Threaded View, one of the visual design patterns to represent conversation.
WordPress comment system. Strikes a good balance between expressiveness and complexity. Indenting helps track the progress of a conversation. It is limited to three levels, though, to ensure users don’t get lost.
Gmail. The grandaddy of threaded email, Gmail is a power user UI. While complex, it fully explores the widgets needed to manage the different gestures that threads elicit.
Facebook. Facebook’s Wall tries to walk a fine line between the river of conciousness metaphor and threaded view. In this case, the thread is two-levelled, the original item takes the leftmost justification and all the other comments have the same indentation level. This seems mosts appropriate for short lived conversations. It’s a tradeoff we see also in blog comments.
Rebelvox. When you move to the mobile realm there is the added challenge of dealing with the small form factor. Rebelvox’s cartoon bubble centric UI is an evolution of the iPhone / iChat threaded IM and SMS view with the added twist of multiple media (text and voice) and their secret time shifting audio recipe. More on Rebelvox on their blog.
Slashdot. It has been around since ‘97, had to very quickly come to grips with managing conversation, and their UI is an attempt at highlighting the interesting bits in a flood of messages. They currently have a couple of interesting UI elements, the notion of scoring, which controls the degree of folding, and a double draggable slider bar that changes the viewable items and gives a count of what’s hidden
Threadsy. Threadsy brings together email, facebook, twitter.. in what it calls your “Bound” and “Unbound” communication. It also makes it possible to cut across media to create context
Some key takeaways: