Sunday, December 5, 2010
Do you Survive like a Cockroach or Thrive with the Best?
Seeing this statement made me think about Charlene Li's latest book, "Open Leadership", where she discusses leaders who, instead of sticking their heads in the sand when times get tough, take risks, innovate, and basically try something new to move their companies forward. While what she discusses makes sense and all employees should advocate for the company good, I'll contrast that attitude with other companies I've worked at. I've seen senior managers instruct subordinates to "just do your job" and "don't take any risks", when in fact, it was the fear of getting fired and a blind adherence to tradition that insured that the company couldn't keep a leadership position even if it fell into one. One company I know was a leader in small router technology, but the founder had a policy of locking up all source code each night for IP protection. No one stole source code, but no development happened after hours or when the founder wasn't there, and, most importantly, no engineer dared to experiment with new ideas w/o the CEO's express approval. While that company is still in business today with decent technology, it's no longer considered a technology leader and rarely mentioned in discussions in SME router RFPs.
Maybe it's not the individuals at fault who want to survive, maybe it's the culture of the company that ushers employees into that mindset. If the company has a culture of fear stemming from firing anyone who takes risks or suggests products or services that might push the corporate comfort zone, then a culture of risk averse employees will be the ones who are hired and stay at the company - surviving until the a better competitor puts them out of business. On the other hand, if the company is willing to consider risks and learning from potential failings, then employees will feel comfortable pushing envelopes and boundaries where the next great product or service might be found. At one company I worked for, the 3D Avatar with stereo sound technology the company had was held at arms length, with most of the company not acknowledging it or its potential. I had a soft spot for it since it was used by the Klingon Language Institute. Fortunately, my CEO, Larry Samuels, and a customer both saw the value in the technology, which allowed me to manage a business development OEM deal that not only generated $1M+ in revenue, but also led to a $5M+ round of financing. Some people told me that if we hadn't made that deal, the company would have shut down. I prefer to think of the opportunity, and how taking that risk gave us more opportunities and learning that would never have happened if we had killed the 3D avatar and audio technology.
So you might see some optimism bias in my discussion, and yes I prefer to see the glass half-full. I also prefer to believe that businesses are not built on cockroaches who just survive, but on smart risk takers who find ways to thrive.
Friday, September 3, 2010
Smarter Executive Hiring for Startups
While Michael and other executives I know definitely earn their salaries, those same salaries are hard to justify for small or growing startups. Startups are then faced with a dilemma - hire an expensive senior exec who brings the strategy, planning, and wisdom you likely need, or hire a cheaper, more junior exec with some of what you likely need, but fits in your budget. Of course, the real answer lies in what you need, but there’s the rub. Do startups really know what they need? Early stage startups are almost always defined by a market vision that a group of customers want a product or service. They have an idea or early prototype, and they’re trying to make sure the product fits their intended customer or they are working to really define the customer that will buy and use that product. Sure, field research of 5 to 20 people may have helped, but does that really scale into the enterprise, retail, or massively deployed Internet presence?
Tuesday, February 23, 2010
Startups and 'It's not my job'
Let me explain, with some background first. In well run startups, there's one phrase you rarely hear "That's not my job". On the rare occasion it pops up, it's usually followed by "well whose job is it and why aren't they in this conversation." In most startups, the team is well focused and aligned, everyone is/should be working toward the same goal. If an important job isn't getting it done, the team rallies, offloading, reassigning, or sharing responsibilities to ensure that the important things get done. When something needs to happen and resources aren't available, someone should, and usually does, step up to execute, even if it means night and weekend hours. It is important, after all. There's usually plenty of work to do, so people routinely step up, taking on tasks above and beyond their normal skill-set or training, even crossing functional boundaries.
In larger companies, operations are often broken down into more discrete tasks, where employees are hired as specialists in one functional area. This can lead to departmental and functional optimization where employees do a few tasks and are expected to do them well. If a task comes up that a specialist is not trained to do - they often have little interest and/or knowledge about how to execute on that task. Literally, it's not his/her job, and the task can be accomplished by someone more experienced with the proper skill-set.
Herein lies the potential conflict for startup types in larger organizations. When a startup type joins a large company and finds an important task not being addressed, they find a way to make it happen. They might do it themselves or try to acquire resource to quickly move forward. Unfortunately, trying to get it done and making it happen have different processes in a larger company. "Trying to get it done" may mean identifying the related projects, the required resource, the managers, and the chain of command that would normally get the task done. The startup person's task is one tiny priority among dozens of others, and when pushing his/her agenda, they often get the "I won't have resource until Y days/weeks in the future" response. In frustration, the startup person may do it himself, imperfectly, w/o the resources and w/o the blessing of the other managers, but doing it in a day or two instead of waiting two weeks before resource became available. This is how egos get crossed, walls get built, and turf wars begin against the startup person.
It doesn't have to be this way, and no one is really at fault, but this same cycle happens over and over again when the mindset and culture of the startup person is implicitly applied in the larger company environment. Often the manager who hired the startup person feels like he/she hired a rogue who doesn't fit, but in reality, a gap in communication and alignment has been exposed. It's really a learning moment and opportunity for the startup person and the larger company to operate more efficiently and effectively.
The solution is communication and goal alignment. When urgency, priority, resource, corporate advancement and opportunity can be weighed, managers and resources can be highlighted to allow a project to be executed in a more scrappy and nimble fashion, or the project urgency can corrected to more realistically reflect the priorities and goals of the company, focusing the startup person on higher priorities. I have seen communication and clarification work well, pushing a larger organization to new levels, but I've also seen the reverse, where the larger company manager is intimidated and insecure or the startup person can't adapt to the new structure.
Have you been involved either way? Successfully or not? Feel free to comment or contact me with your feedback.

