This is a great 45-min video of Steve Ballmer talking about some of his life lessons to the CS50 class. If you can handle his antics, there’s a lot of great entrepreneurial nuggets in here.
This is a great 45-min video of Steve Ballmer talking about some of his life lessons to the CS50 class. If you can handle his antics, there’s a lot of great entrepreneurial nuggets in here.
Would you ever consider marrying someone after the first date?
Since we are on the topic of Founder Sins (you can read my first one here) let’s talk about the second one real quick. Another very common thread I see fraying from the rookie founder sweater is how quickly they are considering whom to choose as their cofounders.
“I met this developer at a networking event and I think we’re going to build something together.”
“Do you know anyone who codes? Do you think they could help me with my idea?”
“The six of us started a company at a Startup Weekend!”
Just as dating the right person takes time for the relationship to develop into a marriage, so does a business partnership. I am not saying you need to “court” the person for years on end, but I am saying it takes more than one event, one week or a few short meetings to grant a random person a large stake in your future company, basically legally binding the both of you.
Here’s why I know. I have lost a cofounder myself.
In the fall of 2011 I was approached by an awesome developer – whom I didn’t know at the time – about joining the founding team of his newly forming startup. He read an article I had written, emailed me and said we should meet. When we met for coffee he showed me the prototype of the mobile ordering/payment stystem he was building and said he was looking for a CEO. I was impressed and intrigued. We booked another meeting or two and within 2 weeks we were talking “marriage”, better known as personal responsibilities, founder equity and company formation. Before I knew it I was CEO of a tech startup (Seconds) and diving into leading a founding team I did not know two weeks ago.
But unfortunately, 6 months after that initial meeting he was on a plane moving down to SF to do contract work, leaving me to find another CTO.
I am forever grateful for Jacques to have sought me out and single-handedly placing me on this path I am today. Yet, in hindsight it’s clear we jumped in too quickly. We were excited, thought time was of the essence and needed to get to work today! Within a week or two of knowing each other we were having the “how much percentage of the company do you get and how much do I get” conversation. I was immediately in charge of estimating product timelines, leading a team of developers, laying out our fundraising strategy, talking with the media and figuring out how we’ll make it to the next phase of the company.
All this and I didn’t even know who these people were!
I didn’t know how they handled stress (although I found out pretty quickly!) I didn’t know how they had performed in the past on other teams and projects. Did they run from challenges quickly or where they the ones to stick it out and find a solution? I was not aware of their tell-tale signs of when things weren’t going right. And I hadn’t learned how to best approach them to talk over difficult situations and touchy subjects.
In the end, I didn’t know them at all.
And now I know why investors ask about the backgrounds of the founders and how long they have known each other. It’s very important you take the time to get to know people you want to work with in the future. If you have a long view on your career – your entrepreneurial journey – you will see there’s decades of time for you to work on various projects and many different people you will work well with.
The thing is it’s very hard to determine that after one or two meetings.
Take it from me, it’s best to start laying the foundation for your future cofounder relationships now so that when the time comes for you to form your dream team you will already know who you will pick.
That, or get used to signing divorce papers…
I have noticed a trend recently as I help founders wrap their arms around their ideas and how to best get started.
They come to me with an idea – a problem they have observed in the world – and are devising a unique solution and hopefully in the process attach a kick ass growing business to it. The problem starts when they try to get too tricky – maybe even too complex – and add all these extra functions and features to their solution.
They create Product Bloat.
This is not good. It’s the number #1 founder sin. Yet it’s so easily avoidable.
It’s the number 1 sin because people think too deeply about what they are trying to do. Thinking to deeply is not actually the problem; implementing too much and attacking the entire vision right out of gate is. They also want to be different than others in the market, so they think “well, what if we put this into the app?” Or “such and such is doing X so we’ll just do Y so we can be different.”
The issue with that type of thinking is it takes you farther and farther away from “problem solving” thinking and puts you closer to “creating something new” thinking. This is wrong because trying to launch a successful product without solving a clear problem in the world is very difficult, if not impossible.
But back to simplicity. As a founder you need to think about your entire vision as a large iceberg. The challenge is to find the tip of the iceberg and only release that as the first version. The rest of the iceberg is under water and very large, just as your entire vision is in your head and not visible to the rest of the world. Some think of this as an MVP (minimum viable product) and I concur, I just like the illustration better.
Most founders make the mistake of not finding (or determining) the tip of the iceberg and thus end up building the whole iceberg, resulting in lost time, a bloated product and a lost value proposition.
For every Uber – a very simple and easy to use app – there’s thousands of apps that get it wrong and initially build a too complex product. They end up confusing users and not even getting to the point of an exponential user growth curve.
Twitter was simply a status update and following what others were updating. That’s it and people could easily talk about it and share it with their friends. YO was absurdly simple, yet at least it was simple enough where millions of people got it and downloaded the app to mess with friends.
The key is to break down your complex problem into its essence. Know the end game and the large vision but find the simple starting point where millions of people will understand what to do with the app. Find the least amount of features and code possible to solve your initial problem.
And then release it and gain users.
Once you have your users you can then figure out the next few things to place in the app experience. But take it from me, don’t commit the number 1 founder sin right out of the gate.
What does it mean? And is it a good thing?
Some may have a negative connotation to the word since it can be used to describe a shady character. To me, being a hustler is a good thing since I think about it in terms of action, of doing things each day and of getting results.
To fully understand what a hustler is and why it’s important, I’ll quickly describe a well rounded startup founding team:
First – and especially if you are starting something in tech – you’ll need a technical person. This individual is the one who architects the product and who writes the code. This is the engineer.
Second, you’ll need someone who makes the code look pretty, readable to the layman allowing for a great user experience. This is the designer.
Lastly you’ll need someone who can sell your product, or the one who understands how to get it in the market and found by people. This is generally the business person, the CEO, and the Hustler.
All three are important in their own way but today I want to address what it takes to be an authentic Hustler.
Hustlers simply get things done. They are not satisfied with just sitting around, they must be moving – and moving forward. They get up each day knowing that they have things to accomplish, fights to win and deals to close. They subscribe to the JFDI mentality. (go ahead, click it and read all about it!)
They also are very social and tend to “know a lot of people”. This important because at its core, business is simply a collection of random people interacting and transacting with each other (hopefully) for benefit of all parties involved. Given that, it’s important a Hustler knows a lot of people in a number of different industries so they can sell their product or service to them, or conversely, so they can buy from others. It’s also important a Hustler understands how to treat people right, meaning they are genuine in their dealings with them and unequivocally treat them fairly.
If you know a Hustler, you’ll find they are confident in their dealings with people. They understand Alpha is the one who generally leads the team and determines the outcomes of meetings and thus, for better or for worse, they tend to take control of the situation.
Hustlers are never satisfied. Although that statement can be taken as “I never have enough” I tend to think about it more as “never rest on your laurels.” The pursuit of perfection for the sake of working to get better each day is what being a Hustler is all about.
Although the above comes naturally to me, I am intent on working to become a better Hustler. Why? Well, I am not a coder. And trust me, I can’t design websites or apps. But I am pretty damn good with people, business and product markets, and intuitively understand my future success will be determined by how much better I can be in those areas.
But good is not Great! I want to be great at these things and I am now paying close attention to improving my skills with people, business intelligence, leadership and how to market a company.
If you are non-technical I hope you are paying attention to those areas as well.
A few months ago my friend Kyle announced he was moving himself and his company to Las Vegas. It was a sad day for us here in Seattle – since we were losing a staple of the Seattle startup community – but he received a huge outpouring of support for his decision and ultimately made the move down in September.
Kyle recently sent out a message saying he was going to be in town this weekend and was planning a brunch gathering, and of course I jumped right on it. It was great. Here we are as a group…
Although I could write much more on this topic, I want to touch on what I have observed (learned) from Kyle and his approach with the people in his life.
Friendship is not simply treating people the way you would want to be treated, it’s also being genuinely interested in them and present when you are around them. Kyle does an amazing job of treating each and everyone in his life with authenticity and respect. It isn’t fake or half-hearted. He is genuinely interested in you, your life, your company and the people you are sharing your life with. I admire this about Kyle and actively try to live this way in my life as well.
Do yourself and your friends a favor and treat them with the love and respect you would wish to be treated, and genuinely work towards being present when with them.
Creating awesome experiences is Kyle’s Modus Operandi. He isn’t just concerned with seeing you, he’s all about experiencing life WITH you. Earlier this year, Kyle started sending emails to a large group of his friends simply stating “Brunch this Sunday at such-and-such diner, first 12 that respond get a seat!” How cool is that? Things as simple as organizing a group brunch on a Sunday takes an average drizzly November Sunday morning and creates long-lasting memories for everyone involved.
Do yourself and your friends a favor and start creating unique experiences to share with others. It’s better than sitting on a sofa by yourself!
Rose Colored Lenses
If you follow Kyle on any social media, you will see he has an incredible eye for photography and uses a lens to capture life’s beauty to share with his network of friends. I admire this quality and talent since I am not the most creative and talented in the world of visual art. But what I can do is start to view the world like Kyle does, keenly observing its uniqueness and beauty from every angle imaginable. Ya know, it’s kind of our generations “stop and smell the roses” perspective, except the difference is today we pretty much don’t ever stop for anything anymore, and just snap it and send it off to our friends without blinking an eye. Kyle’s approach is a lot more meaningful, introspective and thought provoking. I like that.
Do yourself and your friends a favor by taking a breath, looking at the world’s details from a slightly different viewpoint, and fully appreciate its beauty.
Sometimes it takes a good friend visiting from out of town to remind you how to (better) live your life each day.
This year has been a turning point in mobile payments, as Square, Paypal, along with Apple and others like SoftCard (formerly ISIS) have all made strides in their digital payment offerings, finally achieving top of mind with tech executives and media coverage. Yet for all these updates and enhancements, these companies are barely cracking the shell on everyday mobile payments, and most have not built a scalable system to reach the millions of small businesses in the U.S.
In the fall of 2011, I cofounded a mobile payments startup originally targeting local businesses so they could easily accept mobile payments. Here we are three years later – and after ultimately failing to crack the code myself — I now stare at three big issues that still apply today, and are the main reasons we will not be paying with our phone in everyday retail stores for a long time to come.
Merchant Hardware Challenges
The first issue has to do with the point-of-sale and hardware challenge that the average SMB faces. Mostly running outdated Windows terminals, Verifone or other proprietary card-swiping hardware virtually impossible to integrate with, these local merchants are constantly operating behind the technological curve. Their machines are difficult to update with new software and are expensive to replace, meaning the update/replacement cycles tend to be measured in decades, not years. And when they do update to new and enhanced hardware, it still ends up being closed and proprietary (Square, et al) meaning it works only with that specific company’s app, but of course no one else’s. Simply put, the current POS market is fragmented, expensive, outdated and local merchants are offered little help in getting things up to date and working together.
Also, once the updated hardware is implemented and mobile payments are available within an SMB’s operations, there is the issue of employee education on how a mobile transaction actually works and how the merchant verifies the payment. Let’s remember, the concept of someone walking in and paying with their smartphone — not cash or physical card — is still foreign and hard to comprehend for most people.
What I found is that merchants just want to get paid, and anything getting in the way of that is discarded — fast. Their business is not technology, it’s servicing their customers in a timely manner so any employer struggling to educate their staff will simply revert to what they know best, which is cash and credit card swiping.
Until a majority of US local merchants are running 21st century POS systems with mobile payment capabilities, we will not be paying with our mobile device.
“I’m sorry, you have an Android phone…. We only accept Apple phones!”
Imagine hearing those words Monday morning when you just want to pay for your latte and get on with your day. Sounds ridiculous – yes – but it also looks to be a possible result of the ever growing war between Apple and Android operating systems. Looking at currentglobal mobile shipment numbers reinforces the issue, as Android continues to dominate the global smartphone market, with over 255 million units shipped and nearly 85% of the market share (shipments) in the second quarter of 2014.
iOS experienced a slight drop in market share, down to just 11.7% from 13.0% in the same quarter last year. As for general marketshare, Android hovers at more than half of all mobile devices operating in the world.
What happens to Apple Pay when that number gets even higher as the years go on?
Fragmentation and lack of interoperability cuts like a knife in the back of the mobile payments market. Our mobile payment utopia is being threatened by operating system lock-in, where both Apple and Android hope to give merchants “the best deal possible” for exclusivity and end up elbowing each other for mobile dominance.
More likely, Android will release its own version of Apple Pay and most of the market will be covered with some sort of mobile payment option. Awesome! Yet, aren’t we now back to the issue above, where the merchant must purchase multiple hardware systems so they are compatible with both Apple and Android?
And how are we – the end consumers – supposed to know what to do, what to use, when to use it, where to use it and where it’s accepted within this exclusivity war?
It’s all a big mess right now and it’s getting frustrating for all involved. Things will not move forward until something or someone finds a way for these separate platforms to work together in some sort of local cloud.
User Experience Issues
Assuming the first two issues can be addressed and both the hardware and OS compatibility issues are taken care of, there’s always the user experience challenge to overcome.
What user experience issue? Well, it takes only a few seconds to pull out a credit card, hand to the cashier, have them swipe it through the reader and hand it back to you. Simple as 1-2-3.
Humans are lazy. Unless the time it takes to pay using a mobile device in the retail store isequal to or less than the time it takes to pay with cash or credit card, it’s game over. Plain and simple. People will not put up with fumbling on their phone in line, opening an app, needing to input security pins and other codes – all of which take many seconds to complete. And that’s assuming everything works correctly.
From early research of Apple Pay, it looks like they are really attacking the challenge of minimizing the amount of time from grabbing the phone to completion of transaction – especially with Touch ID – which is encouraging. But again, since we are only now seeing it live in the wild one can only expect a bumpy road while early bugs are worked out of the system. Until then, I am not a believer retail mobile payments will save any time for the merchant or the customer.
These issues may seem obvious but they are the exact reasons we are not using our mobile device to pay for everyday things at the register of our local merchants, and should not be overlooked. Because of these and the slowness at which local merchants adopt new technologies, it will sadly be years before we see any significant uptick in retail mobile transactions.
Here’s to hoping I am wrong!