Case Response: What Now – Deal or No Deal?
May 13, 2012 § 1 Comment
It’s been over a month since I wrote my last case response. Since then, 3 new case scenarios have been released, but I’ve been too busy working and coding that I haven’t been able to get around to them. After working and coding all day, my brain is shot, but I don’t want to sleep yet so I figure I’ll try and catch up on the case responses.
As a critical note, I would not be making any of these decisions right now when I’m exhausted and tired. Each of the scenarios Peter is presenting us with require key decisions that will make or break your company. While these decisions need to be made promptly, they shouldn’t be rushed. If a viable solution isn’t clear to you (they usually aren’t, but these situations are particularly complex) for situations like these, my suggestion is this – go sleep on it. Your subconscious will help you process everything as you sleep, and you’ll have a clearer mind in the morning to make your decision.
On another note, the situation may not be as clear in real life. Case studies present a nice summary of events, but when you’re actually going through the events things may not seem as obvious. You may not have all the information you have in case study.
Issue
In addition to the Freemium + upsell model that SpiderNet has implemented, you have also decided to pursue a strategic partnering/OEM model. You’ve brought on a world-class Business Development executive with the objective of getting major ecosystem players to adopt your free, base software into their distribution and enable them to upsell above that base. The model will enable additional deployments of your free software, providing additional opportunity to monetize the user base.
The new BD executive has been active for several months, targeting large players with massive distribution capabilities and $100+ billion market caps. A deal with any one of the “elephants” would be a game changer for SpiderNet.
Recently, one of the “elephants” finishes their evaluation of the SpiderNet product and wants to do a deal. After several rounds of negotiation, the terms they offer are:
- 50/50 net revenue split on all products upsold from the integrated free base;
- Pay SpiderNet $5 million in up-front cash;
- Five-year contract length;
- All current and future products;
- Exclusive distribution rights;
- First right of refusal if SpiderNet gets an offer to be purchased;
- Rights to source code if SpiderNet gets acquired by a competitor
You realize that some of these terms are not very favorable to SpiderNet, but this deal has the ability to fundamentally change the future for you. Having one of the largest ecosystem vendors in the market bundle and upsell SpiderNet products will be a huge win. Do you agree to these terms and quickly move to lock down a deal, or do you negotiate further, possibly losing the deal to a competitor? And if you do negotiate further, what would you propose to change?
Solution
Gut reaction is don’t take the deal as is. The terms are too erroneous. While the deal does have the ability to fundamentally change your company, your gain is short-term and you severely compromise your long-term future. I would negotiate further because there are a few terms that can really hurt the future of SpiderNet.
- Rights to source code if SpiderNet gets acquired by a competitor
- All current and future products;
These terms can really hurt the future of SpiderNet. Giving up the rights to the source code upon acquisition by a competitor is a definite no. Agreeing to this term will make it very difficult for you to become an acquisition target in the first place. Three big reasons why you’re acquired: 1) Talent; 2) Market; 3) Product. Usually it’s a combination, but by giving up the source code, you’re giving up a reason to be acquired in the future. What’s even worse is that you’re giving up something that defines your company. Even if you’re acquired, you may be left to continue operating independently. However, you won’t be able to since you’ve given up your product to the “elephant.” They now have your product, and they can sell it as their own. Your “benefactor” is now your competitor with your exact product.
Including all current and future products is bad. All current products is a maybe, but all future products is a no. The reason why all current products is a maybe is because you only have one product right now (as far as I know) so nothing changes. By including all future products, however, you’re severely limiting the potential growth of SpiderNet. Let’s say you develop a new product 9 months from now that really compliments your current product and generates nearly double the sales of the previous product. Guess what? “Elephant” gets 50% of your sales. Another 9 months down the road, you release a new product that generates 4x the revenue of the previous product. Still within in the 5 year contract, so “elephant” still gets 50%. For the next 5 years, anything you build will have 50% of its sales go to the “elephant.” Those terms are not good for your growth. Only include current products, and (maybe) the soon-to-be-released product. Let’s put it this way, if Apple had agreed to this with AT&T, then AT&T would be taking 50% of all the revenue Apple received from the iPhone 3G, iPhone 3GS, iPhone 4, iPhone4S, iPad, iPad 2, all computer sales as well as App Store sales. I think that makes it pretty obvious why you should say no to this term.
This is what I would probably do. Definitely get rid of the two terms above. They are non-negotiable. Next, I would change the right to first refusal to right to first offer. Finally, I would accept the term to grant them exclusive distribution rights. However, for that I would negotiate to reduce the contract length to 2-3 years instead of 5, change revenue split from 50/50 to 70/30 in our favor, and ask for more money up front (say… $10-15 million). Chances are they’ll be pretty surprised by your counter-terms, but it’s all a part of the plan. Let the negotiations begin :).
Case Response: What Now – Freemium of Paid?
April 9, 2012 § Leave a comment
I was beginning to wonder when the next part of the case study series would appear on Peter Levine’s site. During my daily reading of news, I came across the next part for SpiderNet on PandoDaily. I’m sure this will help both Peter and Sarah because this 1) promotes the case study series, which is really beneficial to entrepreneurs and business people, 2) further promotes the value Andreessen & Horowitz bring to entrepreneurs and the ecosystem, and 3) promotes visits to PandoDaily. If the case study is going to show up first on PandoDaily from now on, then you can be sure I’ll be keeping an eye out for it on PandoDaily.
Anyways, let’s look at the issue we’re faced with in this next part of the series.
Issue
Your company SpiderNet is in the final stages of defining the go-to-market model and pricing for the product. The company has spent a great deal of time debating the benefits of doing a freemium model versus paid. The product has the capability to be split along a free/paid feature set, but there are differing opinions in the company on what to do.
On the one hand, several people in the company want to charge $99 for the complete product, arguing that every installation will result in some revenue to the company. Even though the base of users will be smaller, every user is a real customer. Furthermore, if the number of users doesn’t materialize, then the company can always change to a freemium model later.
Others in the company argue that getting to a large number of users right out of the gate will help to establish the company as a leader in the space. Give the product away for free, build a large user base, and then charge $99 for additional features or capacity. They further argue that the sales and marketing costs will be much lower since the free product effectively “markets itself” through viral use. Of course, once the company gives something away for free, there’s no going back to charging for that functionality.
Both arguments make sense to you, but the company needs to decide on one model or the other. You do a quick assessment of the situation and make the determination that the proposed free product is useful to your customers, the market for your product is very large, and you have a pretty clear view of how to monetize the additional features. Given this, do you choose freemium or paid, and how do you think about the trade-offs?
Solution
The initial gut feeling I have is torn between the two options.
Paid
On one hand, I can understand charging customers for the full product from the start. While the number of users can be an indicator of success and growth, in my mind the number of paying customers is a significantly better indicator of success and growth. Context matters in determining the value of indicators, but getting people to use your product isn’t easy even if it’s free, so if you’re able to get people to actually pay to use your product then I think that can be a better indicator of success. I know this is pretty obvious, but you know right away that you have something people are willing to pay for. People are willing to part with their hard earned cash to use your product instead of spending that money on something else. To me, that means they think your product has real value, and they would rather spend that money on your product than other things because your product can address a serious need they have or deliver real value.
That doesn’t mean the paid option doesn’t have its drawbacks. Although I said it can be a better indicator, I also said it’s much harder to get people to actually pay for your product. The cost will become a barrier for people, and you’re going to need to really consider your customer acquisition strategy. I understand the logic behind switching to a freemium model if the paid model doesn’t work out, but if I was a paying customer and this switch happened, I’d honestly be a little upset. Having paid for the product, I expect to be able to receive a certain value as a paying customer. If the exact same product I paid for is now free, I’ll be upset. Sure, it’s nice that I can now have access to the same product for free. However, even if I was given more features on top of the free product, I’d still feel like the money I had spent on the product was wasted. In order to make up for it, I would want to be compensated. I’m not much of a gamer, but I remember Steam experiencing the same backlash from paying customers when they made Team Fortress free. Yes, you do make it easier for new users to try out your product, but you risk alienating your customers who actually paid for your product in the first place.
Free
On the other hand, the freemium model allows you to eliminate cost as being a barrier to entry. People will be more willing to try your product if it doesn’t cost them anything but their time and energy. In that sense, you have a channel for customer acquisition because you have a growing number of users (hopefully) who you can try and convert to paying customers. They will have a chance to use your product, determine if it’s valuable to them, and then decide if paying for additional features will deliver even more value. Freemium allows you to try and gain some traction through user growth.
However, freemium does have its drawbacks as well. One is the fact that it’s free. Sales and marketing costs may be lower, but you make up for it in terms of cost and operations because the free users will still use up your limited resources like cash to support servers, technical support, etc. Users may also sign up, play around with your product a bit, then leave never to return again. You’re going to need clear metrics to show that your user growth isn’t filled with zombies. Another potential drawback is that it may take the same amount of time and resources to acquire a paying customer despite already having that potential customer as a current user. The free product can sufficiently address the needs of some, and their pain or the value of the features may not be significant enough to make them want to pay.
Decision
It’s really hard for me to say which option I’d choose. On the one hand, getting paid customers is a great way of legitimizing your business, but it can take longer to acquire paying customers. On the other hand, user adoption can help your startup gain traction and go viral, but user growth isn’t the best indicator of success. You have to consider a lot of things like what your product is, what your market is like, the state of your company, etc. Doing this case study really helps me consider the trade-offs, and make a more informed decision if I’m ever faced with making this decision. I will learn a lot more once I read the rest of the post as well.
For now, my opinion is you need to understand who your primary target users are. There is a group of users you know who find your product useful. Approach them, give them access to a beta, gain their feedback, and determine if it’s something they’re willing to pay for. Figure out the price point. Since it’s a beta, there’s some understanding that it could eventually become a product you pay for. After gaining feedback, you can determine if the freemium option is the better route to go, or the paid option. However, figure out what your business needs to do in order to make your product something people are willing to pay for. If not a lot of people are willing to pay for it, then you may need to re-evaluate your product and/or business.
Case Response: What Now? Product Release
March 3, 2012 § Leave a comment
As you can tell from the title, the next case study from Peter Levine focuses on a product release dilemma. Similar to his last post, Peter has already posted his response. In order to avoid reading ahead, I’m trying to only read the posts on my phone, which is easier since the Reader app is what notifies me when a new post is up :).
Issue
SpiderNet has been planning to release version 1.0 of its product in Q2 of this year. However, after the new VP of Engineering looks into the schedule and deliverables, he informs you that the product will be delayed, possibly by six to nine months, due to stability and feature completeness.
In your discussion with the team, you determine that there are two options: release on time with reduced features or delay by six to nine months with the full 1.0 feature set. The company co-founder/CTO is adamant that eliminating any of the v1.0 features will result in an uncompetitive product and releasing “a piece of crap” will undermine the credibility of the company.
Product management advocates releasing something in Q2 provided that the next release follows within nine months. Prior to now, everyone agreed that product management is responsible for release decisions. Your CTO team wants to make an exception to the rule, claiming that this is a strategic decision and can’t possibly be left solely to product management.
According to product management, while the first release will fall short of what was promised, the three most important customer-facing features are able to be released on time. In his view, the minimum viable feature set has been met and getting something out sooner is the best approach.
SpiderNet still has about a year of cash in the bank, so could theoretically weather the delay, but getting any sort of customer traction before requiring additional funding will be very difficult. Do you side with your co-founder/CTO and wait six months or do you press the company to release a minimally viable product by the end of Q2?
Response
Gut response is to release on time with reduced features. There are two key things mentioned that make me strongly feel this way: 1) SpiderNet only has about a year of cash in the bank; 2) Minimum viable feature set has been met.
18 months
As co-founder and CEO of SpiderNet, you need to be concerned with how much runway you have left. The rule of thumb is to always have at least 18 months of cash in the bank. To summarize, it takes roughly 3 months to raise capital and it’s safe to assume things will take 3 months longer than expected thus leaving you with only 12 months to execute your plan. You’re already down to 12 months. Subtract 3 months for fundraising and at most you have 9 months assuming no hiccups occur along the way. The estimated delay for product release is 6-9 months. Just by looking at the numbers you should know that delaying the product for the full v1.0 has a high chance of ruining your company because you won’t have enough cash to continue operating.
I’m having a difficult time remembering exactly where I read this, but one of the key reasons a startup fails is because it runs out of cash. Yes, it comes across as obvious and stupid, but there’s much more to it. Every action you take consumes finite resources (time, money, energy). While time is always constant, certain actions you take can require more time than necessary (efficiency). Furthermore, certain actions can have significantly greater impacts on the money and energy consumed. For example, the time and energy spent in hiring the first VP of Engineering wasn’t that much, but the impact it had on the time, money, and energy required to identify, address, and recover from the dilemma it caused was significantly greater – something that could have been avoided if you had invested the necessary time and energy in the first place.
Back to the main issue. Even in the best case scenario of no hiccups and a 6 month delay until product launch, you’re still left with only 3 months to raise the additional capital you desperately need. A sub-issue will arise as a result of this action: You’ll be trying to raise capital while trying to gain customer traction at the exact same time. Not only will you risk not having enough traction to satisfy existing and potential investors, you will also have less than ideal terms in the event that you do get another round of funding.
MVP (Minimum Viable Product)
Seed funding is all about the people. Angels are taking a bet on you and your team being capable of accomplishing something. The idea isn’t the most important thing at this stage. The original idea goes to show that you have something that might succeed, and proves you aren’t crazy, in a sense. Many successful startups have been created because the entrepreneurs had to do something else because their original idea wasn’t working well (i.e. pivot).
Depending on what you’re doing, seed funding can lead to a prototype or a minimum viable product (MVP). Accomplishing this can show investors that you’re capable and lead to your next round of funding. Ideally, you want a MVP and use that to start gaining some traction with customers. Doing this will allow you to negotiate more favorable terms in your next round of funding, and can help in making it easier to raise funds.
In the case of SpiderNet, you already have a MVP. Yes, your co-founder and CTO wants to wait and release the full v1.0. Yes, he says reducing features will make it uncompetitive and you’ll be releasing “a piece of crap” that will undermine the credibility of your company. Is this true? From his perspective, definitely. This is his baby. He wants it to be perfect. This is true for everyone in the same position. However, he needs to understand that this has become a part of something bigger than him. He is the co-founder and CTO so he has a lot of merit, but he needs to understand that he also has responsibilities towards the investors, employees, and you as co-founder, CEO, and friend (hopefully). He should also be aware that he can either get over the disappointment and continue working towards achieving that perfection, or risk having the company and his baby die. Harsh, but it’s the unfortunate truth.
The product may not be exactly what you promised, but as long as it does what customers need then they will use it. The “nice to have” features can wait until the next release. If things work out, you will have released your product with 12 months of cash left. If it takes you roughly 9 months until your next release, then you’ll have those 9 months to gain some traction with a 3 month buffer. You may even be able to achieve your next release before or during your fundraising process, which should allow you to negotiate better terms. The key thing to remember is that the journey is far from over, and that with these decisions, you, your co-founder, and your company can continue working towards achieving your vision.
Update: My response seems to be more in line with what Peter thinks should have been done :).
Case Response: What Now? Hiring
February 2, 2012 § Leave a comment
The next case is focusing on what you do now that you’ve fired the VP in the previous case study. With this case, Peter has already posted his response, but luckily I was reading it on my phone and was able to stop myself from reading too far ahead.
Issue
Last month, as CEO of SpiderNet, you were faced with the issue of firing your VP of Engineering, who initially seemed like a rock star but proved to lack motivation, didn’t gain his team’s respect, and was ultimately ineffective. You talked with your board and everyone unanimously agreed that you should terminate the VP immediately and ask your co-founder to manage the Engineering team in the interim. It was also agreed that the company would search for a new VP of Engineering after the new year.
It is now the new year, the old VP is gone and you are faced with the rather undesirable task of hiring a new VP. Upon reflection, you realize that the SpiderNet hiring process failed. Clearly, the issues surrounding the VP you just fired had to do with laziness and you realize now that the SpiderNet process (or lack thereof) did not exist to properly vet out a prospective job candidate.
Before you move on to hiring again, you take an inventory of the current process in an effort to better understand how to correct things in the future. Here’s what you find:
- You identified the requirements of the position and developed a comprehensive job specification. You feel pretty good about the list, which you developed on your own. Given that this position reported to you, you did not see the need to ask for other input.
- You hired a search firm and saw a number of good candidates, so you felt that the candidate pool was adequate but not exceptional.
- The interview meetings were always with you, your co-founder and then one or two other people from the executive team. Everyone exchanged emails on the candidate after their meetings.
- The search firm did the bulk of the reference checks, which significantly helped your schedule and time.
Most hiring mistakes occur when the interview process does not effectively assess candidate fit, motivation, and expectation. You don’t want to make the mistake again and you need to figure out what to do next. What mistakes do you think you made and how can you better go about interviewing future candidates? You are very nervous about screwing up again.
Response
The conclusion I developed for the last case study was not correct, but I did get one critical thing correct – re-evaluate your hiring process. Having done that, you realized 4 things that are laid out in Peter’s post. I’m going to give my response for each one.
- Feedback is critical. As CEO and the lead behind the hiring process, you may feel like everything is your responsibility as leader thus not something you turn to others for. However, you need input from other people to see if your description of the job is comprehensive and accurate. In the previous case study I stated two things: 1) this is your fault since you were in charge of the hiring process and put together the job specification; 2) the search firm found the candidates based on your job specification, and the VP you hired could very well have thought he was doing the job well based upon the job specification, which is, again, your fault.
Chances are the job specification needs to be revised in order to be a more comprehensive and accurate description of what the job is and who you need. Providing this will help the search firm in finding better candidates, and also help the candidates have a clearer understanding of what is expected from them. Ask your board and executive team for feedback on your job specification. The board is there to help you succeed. Each board member has a network they can refer to in order to help you, and most likely has experience with hiring people at the executive level. Operating on your own without relying on those around you that can help will lead to ruin. As a founder it feels like a solo ordeal, but even the most famous leaders and founders achieved what they did because of the team that supported them.
- Hiring a search firm can be a good way of finding candidates, but in order to find the exceptional candidates you need to work closely with the search firm to help them better understand what you’re looking for. This will help them find better candidates. Also, don’t settle for just “good.” As a startup each hire is critical to the success of your company – especially at the executive level. You need a VP, but you’re not desperate for one since your co-founder is temporarily fulfilling that need in order to give you that time to find a candidate you deem to be “exceptional.” Also, be aware of what I mentioned earlier regarding Mark Suster’s post on punching above his weight class. You want someone who has the skills you currently need, but also someone who’ll be challenged by this position so you want to look for growth potential as well.
- I get the feeling it would be good to have your engineering team involved in the interview process. You’re hiring a VP of Engineering. You want people he’ll be working with to be involved in the interview process. While your co-founder is an engineer, having a few more involved in the process could help in gauging the VP’s capabilities and your engineering team is relatively small. It’s a more close-knit group because of how small it is. The previous VP didn’t have the respect of the engineering team. Exposing the potential VP to the team can help with establishing the relationship early on.
Have team meetings after the interviews. Don’t have email be your only means of communicating because a lot of context and discussion will be lost. Exchanging feedback in person will help everyone gain a more conclusive understanding of the candidate since you can build on each other’s feedback and further develop your opinions.
- DO THE REFERENCE CHECKS. Don’t let the search firm do the reference checking for you. It may help your time and schedule, but if you’re not willing to put in your time and energy into finding the VP you want then it’s either not important enough to you or you’re not taking it seriously enough. It’s probably both. So put in the time and do the reference checks yourself. Had you done that before, you might have heard the feedback from your business associate before you hired him rather than after the fact at the dinner gathering you had (where you’re left to think, “Oh crap!”). If the VP you’re looking at is someone you consider “exceptional,” then chances are someone within your network has heard about him before or knows someone who does know about him. Probe your network.
Although the search firm is trying to help you find the best candidate for their own reputation as well as the hiring fee they receive, keep in mind that they’re not you. They only have a job specification to go on. It’s harder for them to gauge whether or not someone has the personality traits you’re looking for, if the candidate will fit in culturally, if the candidate has the potential you’re looking for, etc. They only have the job specification you provided them and they look for whether or not the candidates have the relevant skills and experience you’re looking for. You need to be highly involved in the hiring process because you’re the only one who can really check for candidate fit, motivation, and expectations. Having a refined job specification will definitely help with assessing some parts of candidate fit and expectations, but only you can really assess everything. Don’t outsource it.
Case Response: What Now? Firing a Key Executive
December 16, 2011 § Leave a comment
Peter Levine has started a fictional case study series focusing on key management and startup issues that he has seen and experienced over the years. Over the next 12 months, Peter is going to present a key issue you’re facing as the CEO. If you’re interested in learning more about this, read this post. I think this is a great idea and it goes to show how Andreessen & Horowitz are focusing on delivering value to entrepreneurs. After reading about this, I thought it would be a great exercise to think and write about how I would go about solving the issue. I could be spot on, a little off, or so far off that you’ll never wish to see me in a management position. What I hope is that I’ll seriously think through these issues, present my thought process, but, more importantly, continue to reflect and push my own learning. I’ve already read the first issue and his solution so I will not write my solution for that one (I was a little off). Peter has already posted his solutions to the problem, but I have avoided reading that until after I have written my own response. Doing this should be fun, and a good exercise for everyone.
Issue
In the previous vignette, you (as the CEO of SpiderNet) were trying to decide on how to organize the engineering organization. Your decision was to hire a new VP of Engineering and your co-founder, who previously oversaw Engineering, agrees to become the CTO and chief architect. Everything seemed to have worked out with the transition and your new VP has been on the job for a few months. When he joined, you were certain you had a “rock star” on the team. References from the recruiter came back great and the person had exactly the right profile against your hiring objectives.
A few weeks later, at a dinner meeting with a close business associate and CEO of another company, you mention that you’ve hired an incredible new engineering VP. Your dinner friend tells you that he knows this person and you’ve made a big mistake. “I know this person and he’s really lazy. Little real domain knowledge despite the pedigree. You should have called me.” Crap.
Several months later, the laziness starts to show. Your “rock star” now becomes a “project” and you have to manage his weekly performance and deliverables. He is just not working very hard and does not have the strategic insight into the nuances of your business. He also does not have the respect from the team. They don’t think he is a total lost cause, but they also don’t pay much attention to him. That said, he’s certainly ok and he’s better than nobody. He puts together decent schedules, brings much needed process to the team and always says the right things when you have your 1:1s. However, you don’t feel good about him and the engineering team is not delivering at the level you’d like. You talk with your board and have a few options: find a different job for this person and re-hire the VP; put him on a plan and re-assess in three months; or fire and re-hire.
What now?
Response
I’m going to go through each of the three options presented by the board.
Option 1: The first option is hiring a new VP of Engineering and giving your current one a new position in the company. Choosing this option can seem like the easiest choice because 1) you don’t lose a VP of Engineering that you really needed, 2) you still have someone filling that position until you find a replacement, and 3) you keep someone you thought was a “rock star” because he may very well live up to that expectation in a different role, and everyone doesn’t seem to think he’s a lost cause. The reason why your current VP is being lazy could be because there’s another role he wants to be in. Moving him into a different role can help him if that’s what he wants, but there are few positions that a VP can move into without feeling like he’s being demoted (and being interpreted that way), and it’s hard to promote him into a higher position. You needed him as a VP of Engineering and that’s what he’s there for, but he’s not performing like you want him to. Moving him into a different role now is brushing aside and ignoring the problem, which will come back to hurt you in the future. You need to really understand what the problem is (why is he lazy?) in order to conclude that moving him into a new role is the solution.
Option 2: The second option is letting him know that he has three months to achieve certain goals and working with him to achieve it. This can involve setting performance milestones, assigning him a personal/professional coach, etc. and then re-assessing to see if that helped him improve, which helps you and everyone else. Choosing this option allows you to 1) potentially get that “rock star” VP of Engineering, 2) have someone filling the role without significantly increasing workload for others, and 3) keep someone who’s already integrated into your company. Another key point with this option is that you need to try and understand the root of the problem in order to develop performance milestones, determine if a personal/professional coach is necessary, etc. The dilemma with this option is that it requires you to invest time and resources, which is something that is extremely valuable because you’re still a startup. Without trying to understand what is causing your VP of Engineering to be lazy it is difficult to assess if this investment will be worthwhile.
Option 3: The third option is to fire your current VP of Engineering and hire a new one. If your VP has committed an act that seriously violates ethical or moral values then this is a no-brainer. If he continues to repeat mistakes despite being told about them then this is a no-brainer. However, as far as we can tell he hasn’t done any of these. No one seems to have any serious issues with him and they don’t think he’s a lost cause. Firing him now will allow you to look for another VP who can deliver the performance you’re looking for. However, even though you’re a startup and you might be able to fire him without cause, you’re going to need to really understand and convey why you’re firing him. Also, finding a new VP of Engineering is going to take precious time and resources.
Conclusion: Given these options, my choice would be option 2. Option 3 is the least favorable because 1) the VP of Engineering hasn’t done anything that clearly requires you to fire and re-hire (as far as we know), 2) it requires time and resources to find another VP of Engineering, and in the meantime you’ll need others to shoulder his responsibilities until you find a new VP thus increasing their workload, and 3) you still don’t understand the root cause. By talking with him you may realize that he really isn’t a fit for your company and/or his role. He may be letting the “rock star” mentality get the better of him, but the only way you’ll figure that out is by talking to him in order to figure out what the root cause is. However, if he is a causing a negative impact then it is better to fire him and hire someone else. A negative person causes more destruction than the benefits created by a positive person. You need someone you can work with. Option 1 is plausible if it turns out that the VP of Engineering really wanted to be a Director of R&D or some other role, but the chances are higher that he’ll want a position you can’t grant him (for various reasons) and any other position you need him in might look like a demotion for him, which will lead to problems.
The critical thing to remember is to not focus on what has happened in the past, but on what needs to be done from now on. As CEO, you were responsible for selecting and hiring your current VP of Engineering so it is imperative that you talk with him to see where the problem is coming from – because ultimately this is your fault and responsibility. He could be under the impression that he is doing a great job (even going beyond the call of duty) based upon the roles and responsibilities he was given when you hired him. The recruiter could have tried to “fit” someone into your hiring objectives. You really need to re-evaluate your hiring process because even if you fire him and find another, you may run into the exact same issue because the fault could lie with you, not the person you hired.
I would spend the next few days re-evaluating the process used to hire your current VP of Engineering, talking to your dinner friend to understand how he came to view your current VP that way, and talking directly with your VP in order to try and gain a better understanding of him to figure out why he’s being perceived as lazy. Communication is key. It is possible that it’s an issue of managing expectations. Instead of looking to get a new VP, it would be better to challenge the VP to grow into his position. Figure out his goals and aspirations and see how they can be aligned with what you want him to do. Get him to punch above his weight class as Mark Suster would say.
Update: Totally off. I wanted to grow the person, but the suggestion is to not waste those few days and move on. At the executive-level you expect a certain level of performance, and if they aren’t delivering then you let them go. It’s your fault as CEO so you need to have that difficult conversation with him about letting him go as soon as you can. Be sure to re-evaluate your hiring process and do a better job next time. Tough, but a lesson learned.
Can’t wait for the next one.
Management: Change or Die
December 3, 2010 § Leave a comment
A few weeks ago a guest lecturer in a class I TA for brought up the topic of Digital Natives and their implications. Much of the discussion came down to discussing values and stereotypes. I’ll state this ahead of time – I do not believe “Digital Natives” or “Generation Y” (or however you wish to classify things) introduce anything fundamentally new. Throughout history changes have occurred in culture as time has progressed and introduced new factors that have influenced our lives. When the automobile was first introduced, I’m pretty sure there were people who scoffed at the idea of not using a horse, or when the telephone was first introduced that there were people who were frustrated or worried about people becoming less “social” because of the absence of face-to-face conversation or in-person interaction. Each new pivotal technology has been met with both praise and disdain. Everything in our world has its pros and cons. We are constantly dealing with change. So when I see articles discussing that Gen. Y needs to do X, Y & Z or how each researcher tends to have a different year of birth range for classifying “Gen. Y,” it gets a little frustrating, to say the least, because everything is written from their own perspectives that are based on their own expectations that are shaped by their experiences and values.
Change is Inevitable, and Occurring Rapidly
As stated earlier, changes have occurred throughout history that have introduced new factors that have influenced our lives. The society/environment someone has grown up in will be different from the one someone else grew up in decades ago. However, the Industrial Age is when periods of rapid change started to occur because the human population, which was relatively stable, started seeing exponential growth. Mass and personal transportation became available and allowed us to expand the areas in which we live along with our capabilities to live. Diseases and epidemics like the Black Plague, which caused dramatic reductions in human population, were eliminated or minimized due to advancements in medicine and our understanding of the human body. Larry Brilliant presented a TED talk that explained how he rallied together a group of doctors to eliminate malaria by rapidly responding and addressing the pandemic as early as possible at the source. His last name really matches well because it was a brilliant and amazing act. Also, it was achieved because of their ability to communicate, coordinate, and respond due to the rapid sharing of information – something that would have been impossible a decade or so earlier. The introduction of the personal computer and Internet further spurred massive changes in our society, and has arguably resulted in more changes than ever before (for better and worse). The reason why I say change is arguably occurring more rapidly than ever before is because of the speed at which things (both information and physical objects) change is incredibly fast due to our advancements in technology. Before the invention of personal and mass transportation, people used horses, carriages pulled by horses or oxen, and/or their own two feet. Messages were delivered verbally or by mail (physical, handwritten postal mail). That was our means of communication. After something occurred, it would take days, if not months (or even years), for that information to disseminate. As a result, adoption and change was slower. If your canned food enterprise shipped off spoiled goods during the past year, there was pretty much no way you could do a recall or warn people of the dangers. With the invention of the telegraph and the telephone, that all changed. With the Internet, it’s changed even more because vast amounts of information can not only be transmitted, but also created, stored, and manipulated almost instantaneously. Thinking back on the past 20 years, or even the last decade, we can see just how much of our world has changed. I still remember the days when the cell phone was not widely available to kids, so getting together took some planning and communicating well in advance. Now even elementary school kids have cell phones so updating people on what’s going on is pretty easy and instantaneous. The Internet back then wasn’t widely available either, and even then I still remember dealing with search engines like Altavista or Yahoo that didn’t produce what you were looking for at all, and access was slow and relatively expensive. Before that, we had to use libraries and rent books in order to get any information. The librarians couldn’t really help you find most of what you were really looking for. Now we can do that on our own through Google and Wikipedia. Whether for better or worse, it is undeniable that our world has changed drastically in a relatively short span of time.
We Don’t Really Like Change (Honestly)
The issue we face is that the majority of us fear change. We like stability and being able to predict events or, at the very least, understand things. When we drive home everyday from school or from work, don’t we all expect the usual routes we use to be available? Have you ever had the experience where you arrive at home or another destination and then come to the realization that you don’t really remember how you actually got there? Our brains go on autopilot basically because we’ve conducted those actions numerous times, and it relieves the cognitive load on our brains (i.e. less stress). It’s when we have to think about something new that we tax our brains and increase stress levels. For many of the older generation, there can be a disconnect in logic because they’re seeing developments in modern youth that didn’t occur during their youth – even if they went through a similar situation. For example, look at the recent news about Google having to offer significant compensation packages to keep their employees. Even despite of that, some employees have still left to work at other companies. Why? Isn’t much of what we’ve learned that cash is king? In certain contexts, yes. Dan Pink gave a TED talk about the interesting science of motivation, and explained that for mundane tasks that required less cognitive activity (e.g. assembling parts for a motherboard), cash was a great motivator in increasing productivity and achieving the output. However, when tackling tasks that required creative thinking (i.e. more cognitive thinking), the effects of cash as a motivator were less and even detrimental to productivity and achieving the desired output. If you consider the Industrial Age when organization management was born it makes sense because it was a very top down approach. The upper management engaged in the creative thinking, delegated work to managers to do things right, who then delegated the work amongst employees to achieve those tasks. Workers were engaged in rather straight-forward tasks. With the Information Age and the knowledge economy, people are more engaged in problem solving. Much of the straight-forward tasks have become automated by computers. Yet, as we have shifted into a knowledge economy, the role of the organization and management hasn’t. As previously stated, our understandings are shaped by the environments we are raised in. People raised in different environments (i.e. other “generations”) are seeing things that they did not see when they were growing up, thus, introducing complications. I’m sure if you ask their parents (and even their grandparents), they will share similar sentiments about them and say that they didn’t understand the youth in their days. Things like paying your dues, company loyalty, shooting for the highest paying job, etc. are less prominent in the newer generation. The latest generation will face the same complications when they have children as well. Just like how our understanding of motivation is changing, so is our understanding in individuals. The critical thing to remember is that every individual is unique, and that for everything that is true the opposite is true as well (i.e. yin and yang).
The Challenge We’re Facing
The difficulty that we are really facing is that organizations are having to deal with a workforce that is composed of individuals from three different generations – Baby Boomers, Generation X, and Generation Y. Each group has grown up in a totally different environment that has shaped different values, expectations, and understandings of the world. You can’t ignore the Baby Boomers because although they’re retiring, they also have an incredibly amount of experience and tacit knowledge that the organization may need. Generation X is taking over the senior manager and executive roles, so you can’t ignore them. Generation Y is the new workforce, so like it or not we need to figure out a way to make things work.
The Wall Street Journal posted a very interesting article called The End of Management, which is the article that really got me thinking more about all this. Management and the organization was all about reducing transaction costs. It was all designed to address the complexity of getting a large group of people together to accomplish tasks. This all occurred during the Industrial Age. So with us being in the 21st Century and the Information Age, what is to become of management? How do we address this issue we’re facing today with three different generations being in the workforce because, yes, it is a management issue? The article discusses the Innovator’s Dilemma as being the most influential book amongst chief executives, and how it applies not only to products and services, but to management and organizational operation as well. With that point, the question is raised: What is the 21st century organization?
My belief is that while organization’s still need to reduce transaction costs, it is no longer a complex task. Reducing production costs, time to market, etc. are all important challenges organizations need to continue to address, but achieving these no longer provides organizations with a competitive advantage as it did in the past. With the shift into the knowledge economy, innovation has become the critical component in achieving not only a competitive advantage, but in also making the organization sustainable. What I believe is key in achieving innovation, and what the 21st century organization is, is no longer reducing transaction costs, but optimizing relationships. If organizations do not understand this and shift to this, they will not only lose the upcoming workforce, but also a critical competitive edge – ultimately leading to their extinction.
The research I am pursuing is related to concretely looking at how we can create the 21st century organization, and how we can achieve innovation. Much of this will revolve around my belief that it is about optimizing relationships, and I will explain that in much more detail at some point. I know that there are some who say that the more they study innovation the more they think a real solution doesn’t exist. I believe there’s merit to that, I honestly do. However, people also didn’t believe we could go beyond the sound barrier or put a man on the moon – but we did. Lets see if I can do the same.
Research Idea: Japan, United States, and Innovation/Entrepreneurship
November 20, 2010 § Leave a comment
How does innovation and entrepreneurship differ between the United States and Japan? At one point, Japan was considered to be the country that would overtake the US and become the largest economy in the world. The “Japanese Miracle” was the period of rapid economic growth postwar Japan experienced until the bursting of the Japanese asset price bubble in 1991. During this period, we saw innovations such as lean manufacturing in Toyota that helped them surpass Ford and General Motors (GM) in producing quality automobiles.
However, the type of innovations that have occurred are different. It seems to be that while Japan was able to rapidly grow their economy and create innovations like lean manufacturing, much of the innovation that has occurred has been predominantly incremental while the United States has been radical. Toyota optimized the manufacturing process and its outputs, but Ford created the automobile. Is it true that much of the innovation is incremental in Japan? Also, how do entrepreneurs fit in all this? How has the culture affected the innovation that occurs, and the entrepreneurial activity/environment?
Idea: Washington State’s Entrepreneur Ecosystem
November 4, 2010 § Leave a comment
Another idea I have related to my research focus on innovation and entrepreneurship is an analysis of the entrepreneur ecosystem in WA state. Silicon Valley is the hub of entrepreneurial activity in the United States, particularly in the technology and engineering field. Recent activity, however, shows that New York is starting to attract a lot of talent from Silicon Valley, making NYC a growing magnet for startups because of the amount of creativity being exhibited by startups such as Tumblr, Etsy, and Foursquare.
With the amount of startup activity that occurs in Silicon Valley and, more recently, New York City, I wonder where Seattle appears in all of this? We have some of the largest and most successful technology companies in Seattle like Microsoft, Amazon and Expedia, and we have other companies like Google and Facebook decide to open offices in Seattle. Incubators like TechStars have even decided to open a branch in Seattle. With all the technology talent that seems to exist in Seattle, why is it that we hear very little about startup activity in Seattle? The Kauffman Foundation’s Index of Entrepreneurial Activity for 2009 lists WA State at 0.24%, with California State at 0.41%, and even our neighbors of Oregon State at 0.38% and Idaho State at 0.45%.
With this idea, I would like to explore the current state of technology entrepreneurs in Seattle, WA, compare the environment to Silicon Valley & NYC, identify the challenges, and provide insight as to how Seattle can create a better ecosystem for technology entrepreneurial activity.
Waiting For Superman
October 7, 2010 § Leave a comment
Waiting For Superman is the first documentary I have been anticipating since I saw the trailer a few months back on Apple’s movie trailers page. This past Monday it became the first documentary that I have paid to watch in a theater. For anyone interested in taking a (frustrating) look at our education system, I highly recommend that you watch this documentary because it offers a compelling perspective.
In a nutshell: It’s a great documentary.
The truth is that our education system is in (serious) trouble, and we have been struggling (and failing) to do anything about it. The thing that makes the education problem something that is so difficult to address is because of how complex and interconnected it is. The education problem is not just about schools and teachers, but it also ties into communities, families, individuals, etc. The list goes on. It’s a really wicked problem.
The complexity of the problem is what prevents a solution. Now, that comes across as an obvious point, but the challenge we really face is in trying to identify the various aspects that make up the larger problem and narrowing our focus to those while also understanding how they affect the other aspects. Again, another obvious point, but that’s why it’s a wicked problem. That is also what makes Waiting For Superman a great documentary. Instead of trying to cover all the aspects of the problem and compress it into one documentary, it focuses on one very real (and critical) aspect of the education system – teachers.
TechCrunch does a nice summary of the movie, and has a great title, “Why Our Schools Suck, The Movie.” What the documentary does is focus on the teachers because at the end of the day they are the ones who we view as responsible for the (majority) of the education our children receive. They are a critical part of how education works, and that’s why they’re also a critical part of the problem. Now, that makes it sound like the teachers are being blamed as the reason why our education system sucks, but that’s not what the documentary does. Yes, there are horrible and great teachers, but the documentary puts an emphasis not on the teachers, but the things that impede our ability to fix issues with teachers – the teacher unions.
The following paragraph in the TechCrunch article highlights this well:
But the brilliance of “Waiting for Superman” is in how it breaks the problem with education down into mostly one simple problem: Bad teachers can’t be fired, good teachers can’t get rewarded for being good, whether that’s promotions or merit-based raises. Two of the most shocking scenes depict both sides of this coin. One showed a “rubber room” where teachers awaiting disciplinary hearings– accused of crimes as extreme as sexual assault– get paid a full salary to do nothing for as long as eight months. Another told the story of Michelle Rhee
, who proposed that teachers in DC could double their incomes if they swapped to a merit-based rather than tenure system. It was so threatening that the labor unions wouldn’t allow the issue to come to a vote. Equally shocking was something called “the Lemon Dance” where public schools in one district just swapped their horrible teachers they couldn’t fire in hopes of getting a less-worse lemon.
The reason why I’m interested in this is because I’ve had the chance to get involved (to a degree) with people who are tackling these very issues. In particular, creating a XPrize for Education. For anyone involved in this effort, I believe this is a great documentary to watch to see one perspective. Without being able to look at and deep dive the various aspects that make up the education problem, we will have (extreme) difficulty in not only creating a solution, but in also framing a competition that is meant to help find a solution. It’s our future that’s at stake.
Note: Something important I forgot to mention was the big message I felt the director wanted to convey. He mentioned that his last documentary was focused on teachers and the work they do, and felt the real focus needed to be on the children. During the film he mentions a key thing – we, the adults, are the ones that tend to forget that it’s really about the children, and instead make it about us.
Ideas and Questions for Research Projects
October 5, 2010 § Leave a comment
Before the start of my PhD program, my professor gave me some great advice and asked me to try and brainstorm an idea a week. The purpose of this is to not only brainstorm ideas for research projects, but to also use this process to help me figure out exactly what I want to do in the PhD program. The goal is to be able to narrow down my focus into 3 specific areas of interest (give or take a few) for my own work. Below is a work-in-progress list that I will edit and build upon over time.
- Explore the Changing State of Management and Organizations
Question: What is the future role of management and organizations?
Since its inception, the purpose of organizations and management has stayed relatively the same. Organizations were an answer to the challenge of organizing large amounts of people in different places with different skill sets to perform large and complex tasks. With it being too complicated and costly to search for and find the right worker at the right time for any given task, or renegotiate prices in an open market, the organization focused on reducing “transaction costs” since they were not as good at allocating labor and capital as the marketplace. Yet in today’s world of rapid globalization, accelerating innovation, and relentless competition, decades-old institutions like Lehman Brothers and Bear Stearns can disappear overnight, and people have come to seriously ponder the weakness of managed corporations in dealing with accelerating change along with the erosion of the fundamental justification for corporations. So if optimizing transaction costs is the ‘dead’ model, what is the new model? Distributed teams have begin to serve as evidence along with cultures like Google’s 70/20/10 rule – it is about optimizing relationships. - Importance of User-Experience Over Intellectual Property
The premise of this idea is looking at how the user-experience(UX)/-interaction(UI) is becoming more of a determining factor as opposed to intellectual property in the high-tech industry. The barrier of entry and the cost of starting a company was relatively high over a little over a decade ago. Any technology company would require expensive equipment such as servers, facilities, broadband internet, etc. However, these costs have become relatively inexpensive as technology has rapidly advanced, effectively reducing barriers of entry. It is no longer the IP and barriers of entry, but more the UX and the functionality that end up determining success. (e.g. iPhone as smartphone game changer, YouTube vs Google Video, MySpace vs Facebook) - Comparison of Priorities of Startups & Incumbents
This idea is to look at the difference in how startups and incumbents operate, with a focus on the CEOs. For the most part, startup CEOs start from nothing and build and scale high-value companies. On the contrary, incumbent CEOs are more concerned about not losing value, while slowly trying to increase shareholder value. The difference for startup CEOs is that, for the most part, they are already starting from negative value, so their focus is entirely on creating value through an innovative product and scaling a great company. Almost all of the great technology companies have started this way (e.g. Microsoft, Sun Microsystems, Adobe, Oracle, etc.), and the successful companies of recent time have also started this way (e.g. Google, Facebook, Twitter, etc.). Yet, although Microsoft and Google were considered opposites in the past, they are both facing the same issue after becoming successful and growing into large companies – continually producing innovative products and increasing their own value. There is one exception to this – Apple. After reaching their “success” point (i.e. IPO), all other companies have peaked in value and slowly dropped while struggling to break out of their core product(s), while Apple has continued to increase in value and deliver innovative products. Looking at those in charge of the companies, the sole difference between Apple’s CEO, Steve Jobs, and the rest is that Jobs has started other successful startups outside of Apple (NeXT, Pixar). This will look at how Apple has seemed to overcome the innovator’s dilemma. - Leveraging Six Sigma & Design Thinking
Many would argue that these two cannot exist in the same environment. However, I believe they are supportive entities that are a critical component to the lifecycle of a successful product and the innovation process. Design thinking is focused on creating something new (thinking outside the box) or radical. Six Sigma is focused on optimizing and takes a systematic approach. People have argued that a six sigma culture is too restricting for design thinking, which requires freedom and ‘controlled chaos.’ However, it is a two phase process with design thinking seeking to create something new (e.g. products, services) or solving challenging problems, and six sigma being the next phase to optimize the creation (i.e. invention). - A Case for ROWE in Japan
This is an idea I briefly worked on during my Masters, but something I never quite finished. As a result, I would like to try and revisit this and try to get it published or funded. The purpose of this was to try to show that we are now more than ever in the knowledge economy, particularly in the high-tech industry. As a country that places an emphasis on time and hours, I wanted to show that putting more of a focus on results and giving people freedom to achieve those results will provide organizations with greater value.
